Storage device supporting vehicle state mode, method for operating same, and storage system

Abstract

A memory device supporting a vehicle state mode, a method of operating the same, and a memory system are provided. A storage device receives a vehicle state mode command from a host and executes a background job based on the received vehicle state mode command, the storage device including: a command executor configured to generate a command regarding the background job based on the received vehicle state mode command; a scheduler configured to receive the command on the background job, determine whether a vehicle state is a state in which the background job can be executed, and generate the background job based on a result of the determination; and a background job executor, wherein the background job executor is configured to execute the background job generated by the scheduler.

Description

Technical Field

[0001] Various example embodiments relate to a storage device, an operating method of the storage device, and a memory system supporting a vehicle status mode, and in particular, to a storage device, an operating method of the storage device, and a memory system that execute background jobs for the storage device in a vehicle status mode. Background Art

[0002] Recently developed vehicles have basic functions that require (or optionally include) a storage device, such as an autonomous driving function or a vehicle state storage function. Therefore, the storage device installed in the vehicle must perform background operations such as a garbage collection operation, but the storage device installed in the vehicle may not perform the background operations depending on the vehicle state.

[0003] Therefore, the storage device does not perform the background job at an appropriate time, and the performance of the storage device installed in the vehicle is reduced due to the degradation of the storage unit. Summary of the invention

[0004] The inventive concept provides a storage device that performs a background job according to a vehicle state.

[0005] Furthermore, the present inventive concept provides a memory system which determines an order of background jobs according to a vehicle state and executes the background jobs of a memory device in the determined order.

[0006] Some example embodiments of the present inventive concept provide a storage device, the storage device comprising: a command executor configured to generate a command about a background job based on a received vehicle status mode command; a scheduler configured to receive the command about the background job, determine whether the vehicle status is a state capable of executing the background job, and generate the background job based on the determination result; and a background job executor configured to execute the background job generated by the scheduler. The scheduler is also configured to: when the vehicle status is determined to be a state capable of executing the background job, set the vehicle status to at least one of a start state, a driving state, a stop state, a charging state, and a drive-stop status, and the scheduler is also configured to determine the order of the background jobs based on the set vehicle status, and the storage device is configured to receive the vehicle status mode command from a host, and the storage device is also configured to execute the background job based on the received vehicle status mode command.

[0007] Some example embodiments of the present inventive concept provide an operation method of a storage device, the operation method comprising: receiving a vehicle status mode command from a host; and executing a background job based on the received vehicle status mode command. Executing the background job comprises: generating a command about the background job based on the received vehicle status mode command; receiving a command about the background job; determining whether the vehicle state is a state capable of executing the background job; and generating the background job based on the determination result, and executing the generated background job. When generating the background job, when the vehicle state is determined to be a state capable of executing the background job, the vehicle state is set to at least one of a start state, a driving state, a stop state, a charging state, and a driving stop state, and the order of the background jobs is determined based on the set vehicle state.

[0008] Some example embodiments of the present inventive concept provide a memory system, the memory system comprising: a host configured to generate a vehicle state mode command; and a storage device configured to receive the vehicle state mode command from the host, and execute a background job based on the received vehicle state mode command. The storage device comprises: a command executor configured to receive the vehicle state mode command, and generate a command about the background job based on the received vehicle state mode command; a scheduler configured to receive the command about the background job, determine whether the vehicle state is a state capable of executing the background job, and generate the background job based on the determination result; and a background job executor configured to execute the background job generated by the scheduler. The scheduler is also configured to: when the vehicle state is determined to be a state capable of executing the background job, set the vehicle state to at least one of a start state, a driving state, a stop state, a charging state, and a driving stop state, and the scheduler is also configured to determine the order of the background jobs based on the set vehicle state. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] Some exemplary embodiments of the present inventive concept will be more clearly understood through the following detailed description taken in conjunction with the accompanying drawings, in which:

[0010] Figure 1 is a block diagram of a memory system according to an example embodiment;

[0011] Figure 2 is a block diagram of a memory device according to an example embodiment;

[0012] Figure 3 is a block diagram illustrating a scheduler according to an example embodiment;

[0013] Figure 4 shows a vehicle state mode command according to an example embodiment;

[0014] Figure 5 is a flowchart illustrating a method of operating a memory device according to an example embodiment;

[0015] Figure 6 is a flowchart illustrating a process of executing a background job in an operation method of a storage device according to an example embodiment;

[0016] Figure 7 and Figure 8 is a flowchart illustrating an operation method of a storage device when a vehicle state is a start state according to an example embodiment;

[0017] Fig. 9 is a flowchart illustrating an operation method of a storage device when a vehicle state is a driving state according to an example embodiment;

[0018] Fig.10 is a flowchart illustrating an operation method of a storage device when a vehicle state is a stop state according to an example embodiment;

[0019] Fig.11 is a flowchart illustrating an operation method of a storage device when a vehicle state is a driving stop state according to an example embodiment;

[0020] Fig.12 is a flowchart illustrating a method of operating a memory system according to an example embodiment; and

[0021] Figures 13 to 15 A three-dimensional V-NAND structure that may be applied to a memory device according to example embodiments is illustrated. DETAILED DESCRIPTION

[0022] Hereinafter, various exemplary embodiments of the inventive concept will be described with reference to the accompanying drawings. Hereinafter, details such as configuration and structure are provided to help the reader understand the various exemplary embodiments of the inventive concept. Therefore, the various exemplary embodiments described herein may be changed or modified in various ways without departing from the inventive concept.

[0023] As described herein, an element that is "above" another element may be above or below or adjacent to (e.g., horizontally adjacent to) another element. An element that is on another element may be directly on another element so that the element is in direct contact with the other element. An element that is on another element may be indirectly on another element so that the element is isolated from the other element by one or more intervening spaces and / or structures and is not in direct contact with the other element.

[0024] It will be understood that elements and / or their properties (e.g., structures, surfaces, directions, etc.) that may be referred to as being "perpendicular", "parallel", etc., with respect to other elements and / or their properties (e.g., structures, surfaces, directions, etc.) may be "perpendicular", "parallel", etc., respectively, with respect to the other elements and / or their properties, or may be "substantially perpendicular", "substantially parallel", respectively, with respect to the other elements and / or their properties.

[0025] It will be understood that elements and / or their attributes may be described herein as being "the same" or "equivalent" to other elements, and it will be further understood that elements and / or their attributes described herein as being "the same", "identical" or "equivalent" to other elements may be "the same", "identical" or "equivalent" or "substantially the same", "substantially the same" or "substantially equivalent" to other elements and / or their attributes. Elements and / or their attributes that are "substantially the same", "substantially the same" or "substantially equivalent" to other elements and / or their attributes will be understood to include elements and / or their attributes that are the same, identical or equivalent to other elements and / or their attributes within manufacturing tolerances and / or material tolerances. Elements and / or their attributes that are the same or substantially the same or the same or substantially the same as other elements and / or their attributes may be the same or substantially the same in structure, the same or substantially the same in function, and / or the same or substantially the same in composition.

[0026] Figure 1 is a block diagram of a memory system 10 according to an example embodiment.

[0027] refer to Figure 1 , a memory system 10 according to some example embodiments may include a memory device 100 and a host 200 .

[0028] The storage device 100 according to the example embodiment may receive a vehicle status mode command (VehicleStatus Mode CMD) from the host 200, and execute a background job based on the received vehicle status mode command. The vehicle status mode according to the example embodiment refers to a state in which the host 200 can determine the vehicle status and determine whether to execute a background job. The background job according to the example embodiment may be a job performed by the storage device 100 without a separate individual command from the host 200. For example, the background job may include at least one of a garbage collection operation, a patrol read operation, a refresh operation, a data retention check operation, and a recycling operation of the storage device 100, but is not limited thereto, and may also include a job that the storage device 100 can perform without using a separate command.

[0029] The storage device 100 according to the example embodiment may generate a command about a background job based on a vehicle status mode command (Vehicle Status Mode CMD) received from the host 200, and determine whether the vehicle state is a state in which a background job can be executed. The storage device 100 according to the example embodiment may generate classified background jobs based on the determination result. In addition, when it is determined that the vehicle state is a state in which a background job can be executed, the storage device 100 according to the example embodiment may classify the vehicle state into a start state, a driving state, a stop state, a charging state, and a driving stop state, and determine the order of the background jobs based on the classified vehicle state. The storage device 100 according to the example embodiment may generate a background job based on the determination result, determine the order of the generated background jobs, and execute the background jobs in the determined order. For example, when it is determined that the vehicle state is a state in which a background job can be executed, the storage device 100 may determine the order of the background jobs based on the vehicle state, and perform at least one of a garbage collection operation, a patrol read operation, a refresh operation, a data retention check operation, and a recycling operation in the determined order.

[0030] The memory device 100 according to the example embodiment may include at least one of a volatile memory device and a non-volatile memory device. For example, the volatile memory device includes a static random access memory (RAM) (SRAM), a dynamic RAM (DRAM), and a synchronous DRAM (SDRAM). The non-volatile memory device can retain the stored data even when the power is off. For example, the non-volatile memory device includes a read-only memory (ROM), a programmable ROM (PROM), an electrically programmable ROM (EPROM), and an electrically erasable programmable ROM (EEPROM), a flash memory, a phase change RAM (PRAM), a magnetic RAM (MRAM), a resistive RAM (RRAM), a ferroelectric RAM (FRAM), and the like. The flash memory can be divided into a NOR-type flash memory and a NAND-type flash memory. Reference Figure 2 The configuration of the memory device 100 is described in detail.

[0031] The host 200 according to the example embodiment may generate a vehicle status mode command (Vehicle Status Mode CMD) and send the generated vehicle status mode command (Vehicle Status Mode CMD) to the storage device 100. For example, the host 200 may include a memory controller 210, and the memory controller 210 may generate a vehicle status mode command (Vehicle Status Mode CMD) and send the generated vehicle status mode command (Vehicle Status Mode CMD) to the storage device 100. The host 200 according to the example embodiment may be included in a vehicle to generate a plurality of commands and send the plurality of commands to the storage device 100. For example, a vehicle refers to various devices that move a transportation target such as a person, an object, or an animal from a starting point to a destination. The vehicle may include a vehicle traveling on a road or track, a ship moving on the sea or a river, and an airplane flying in the air, but the example embodiment is not limited thereto.

[0032] Figure 2 is a block diagram of a memory device 100 according to example embodiments.

[0033] refer to Figure 1 and Figure 2 , the storage device 100 according to the example embodiment may include a command executor (also referred to herein as a CMD executor) 110, a scheduler 120, and a background job executor (also referred to herein as a BG executor) 130. The command executor 110, the scheduler 120, and the background job executor 130 may be included in or implemented in a processing circuit, such as hardware including a logic circuit; a hardware / software combination, such as a processor that executes software; or a combination thereof. For example, the processing circuit may more specifically include, but is not limited to, a central processing unit (CPU), an arithmetic logic unit (ALU), a digital signal processor, a microcomputer, a field programmable gate array (FPGA), a system on a chip (SoC), a programmable logic unit, a microprocessor, an application specific integrated circuit (ASIC), and the like.

[0034] The command executor 110 according to the example embodiment may receive a vehicle status mode command (Vehicle Status Mode CMD) from the host 200, and generate a command BG Assign for a background job based on the received vehicle status mode command (Vehicle Status Mode CMD). For example, the command executor 110 may include a vehicle status manager 111, and the vehicle status manager 111 may generate a command BG Assign for a background job based on the vehicle status mode command (Vehicle Status Mode CMD). The command executor 110 according to the example embodiment may send the generated command BG Assign for a background job to the scheduler 120. For example, the command executor 110 may receive a vehicle status mode command (Vehicle Status Mode CMD) from the host 200, determine a background job according to a vehicle status, and generate a command BG Assign for a background job required (or used) by the vehicle.

[0035] The scheduler 120 according to the example embodiment may receive a command BG Assign for a background job, determine whether the vehicle can perform the background job, and generate a classified background job based on the determination result. In addition, when it is determined that the vehicle state is a state in which the background job can be performed, the scheduler 120 according to the example embodiment may classify the vehicle state into a start state, a driving state, a stop state, a charging state, and a driving stop state, and determine the order of the background jobs based on the classified vehicle state. For example, when it is determined that the vehicle state is a state in which the background job can be performed, the storage device 100 may determine the order of the background jobs based on the vehicle state, and perform at least one of a garbage collection operation, a patrol read operation, a refresh operation, a data retention check operation, and a recycling operation in the determined order.

[0036] The scheduler 120 according to the example embodiment may generate necessary (or advantageous) background jobs according to the vehicle status. For example, the command executor 110 may send a command BG Assign for a background job required (or used) by the vehicle to the scheduler 120 according to the vehicle status, and the scheduler 120 may generate the background job according to the vehicle status based on the received command BGAssign for the background job. In addition, when the background job is terminated, the scheduler 120 according to the example embodiment may send a background job success signal BG Done to the command executor 110. The generation of the background job according to the example embodiment may mean that the scheduler 120 generates input data for executing the background job. Reference Figure 3 Detailed Description The scheduler 120 generates descriptions of background jobs.

[0037] For example, when the vehicle state is a startup state, the scheduler 120 may generate a background job for executing a data retention check operation of the storage device 100, and perform the data retention check operation. The startup state according to an example embodiment may be a state in which power is started to be supplied to the vehicle. For example, when power is started to be supplied to the vehicle, the scheduler 120 may perform a data retention check operation of the storage device 100. The data retention check operation according to an example embodiment may include an operation of determining whether the data stored therein must be retained because at least one storage unit included in the storage device 100 is degraded. When there is a storage block of a retention target, the scheduler 120 according to an example embodiment may set the data retention operation of the storage device 100 as an urgent background job. The urgent background job according to an example embodiment may be a job that must be executed with the highest priority (or, with a priority) among the background jobs determined by the scheduler 120.

[0038] In another example, when the vehicle state is the startup state, the scheduler 120 may generate a background job for performing a garbage collection operation of the storage device 100 and cause the garbage collection operation to be performed. When it is determined that the vehicle state is the startup state, the scheduler 120 according to an example embodiment may determine whether invalid data exists in a storage block of the storage device 100, move valid data in the storage block, and obtain a free block by erasing the storage block.

[0039] In another example, when the vehicle state is a driving state, the scheduler 120 may stop the background job. The driving state according to an example embodiment may be a state in which the vehicle moves without stopping when power is supplied to the vehicle. In some example embodiments, when it is determined that the vehicle state is a driving state, the scheduler 120 may stop the background job executed by the vehicle and cause the job executed by the specific command to be executed.

[0040] In another example, when the vehicle state is a stop state, the dispatcher 120 may determine whether the vehicle state is a normal stop state or a signal waiting state. The stop state according to the example embodiment may be a state in which power is supplied to the vehicle and the vehicle is not moving. The normal stop state according to the example embodiment may be a state in which the vehicle stops driving and is not in a signal waiting state when power is being supplied to the vehicle. The signal waiting state according to the example embodiment may be a state in which the vehicle stops driving and stops and waits for a signal based on the detection result of a sensor installed in the vehicle. For example, the dispatcher 120 may determine whether the vehicle state is a normal stop state or a signal waiting state through a sensor installed in the vehicle. When it is determined that the vehicle state is a signal waiting state, the dispatcher 120 according to the example embodiment may determine that a background job can be executed within the signal waiting time, and generate a background job to be executed. For example, when the signal waiting time is determined to be 3 minutes according to the result of sensor detection, the dispatcher 120 may generate a background job to be executed for 3 minutes. However, the signal waiting time is not limited thereto.

[0041] When the vehicle state is a normal stop state, the scheduler 120 according to the example embodiment may execute only the emergency background job (or, the scheduler 120 may execute the emergency background job). The emergency background job according to the example embodiment may be a background job having the highest priority (or, having priority) among the background jobs generated by the scheduler 120. For example, when the vehicle state is a normal stop state, the scheduler 120 may generate only the emergency background job (or, the scheduler 120 may generate the emergency background job). When the generated emergency background job is a data retention operation, the scheduler 120 according to the example embodiment may execute only the data retention operation when the vehicle state is a normal stop state (or, the scheduler 120 may execute the data retention operation when the vehicle state is a normal stop state).

[0042] When the vehicle state is a signal waiting state, the scheduler 120 according to the example embodiment may execute the generated background job. For example, when the vehicle state is a signal waiting state, the scheduler 120 may generate a background job based on a received vehicle status mode command (Vehicle Status Mode CMD) and determine the order of the generated background jobs. When the vehicle state is a signal waiting state, the scheduler 120 according to the example embodiment may generate a background job so that the generated background jobs are executed sequentially.

[0043] When the vehicle state is a charging state, the scheduler 120 according to the example embodiment may execute the generated background job. The charging state according to the example embodiment may be a state in which the vehicle stops and receives power from an external power source to charge the battery in the vehicle. For example, when the vehicle state is a charging state, the scheduler 120 may generate a background job based on a received vehicle status mode command (Vehicle Status Mode CMD) and determine the order of the generated background jobs. When the vehicle state is a charging state, the scheduler 120 according to the example embodiment may generate a background job so that the generated background jobs are executed sequentially.

[0044] When the vehicle state is a driving stop state, the scheduler 120 according to the example embodiment may receive power-off time information about the storage device 100, determine the order of the generated background jobs, and execute the background jobs in priority order based on the power-off time information. The driving stop state according to the example embodiment may be a state in which the vehicle is stopped and the power supply to the vehicle is disconnected. When the vehicle state is a driving stop state, the power supply to the storage device 100 according to the example embodiment may also be disconnected. When the vehicle state is a driving stop state, the scheduler 120 may receive time information until the power supply to the storage device 100 is completely disconnected (or, disconnected), and execute the generated background jobs in priority order.

[0045] The background job executor 130 according to an example embodiment may execute a background job generated by the scheduler 120. For example, the background job executor 130 may receive a background job start command BG Start or a background job resume command BG Resume generated by the scheduler 120, and execute the background job generated by the scheduler 120 in a determined order. When the background job is completed, the background job executor 130 according to an example embodiment may send a background job success signal BGDone or a background job stop signal BG Stop to the scheduler 120.

[0046] Figure 3 is a block diagram illustrating the scheduler 120 according to an example embodiment.

[0047] refer to Figure 3, the scheduler 120 according to the example embodiment may generate a background job by generating a data queue. For example, the scheduler 120 may generate information about the background job to be executed as a data queue based on a command about the background job. For example, the scheduler 120 may determine the order of the background jobs by generating a first data queue Queue1 or a second data queue Queue2. According to the example embodiment, the first data queue Queue1 may include information about an urgent background job, and the second data queue Queue2 may include information about a normal background job. When the information about the urgent background job is stored in the first data queue Queue1, the scheduler 120 according to the example embodiment may execute the background job based on the information about the first data queue Queue1, with a higher priority than the background job based on the information about the second data queue Queue2.

[0048] A first data queue Queue1 according to example embodiments may include a plurality of pieces of data Q1-1, Q1-2, Q1-3, Q1-4, Q1-5, Q1-6, Q1-7, and Q1-8. Figure 3 The first data queue Queue1 is shown to include eight pieces of data, but the number of pieces of data included in the first data queue Queue1 is not limited thereto, and the first data queue Queue1 may also include multiple pieces of data. The second data queue Queue2 according to the example embodiment may also include multiple pieces of data Q2-1, Q2-2, Q2-3, Q2-4, Q2-5, Q2-6, Q2-7, and Q2-8. Although Figure 3 It is shown that the second data queue Queue2 includes eight pieces of data, but the number of pieces of data included in the second data queue Queue2 is not limited thereto, and the second data queue Queue2 may also include a plurality of pieces of data.

[0049] Figure 4 Vehicle state mode commands are shown according to an example embodiment.

[0050] refer to Figure 1 and Figure 4 , the memory device 100 according to an example embodiment may include a nonvolatile memory, and the host 200 may generate a vehicle status mode command (VehicleStatusModeCMD) by using a nonvolatile memory express (NVMe) standard. The NVMe standard according to an example embodiment defines a register-level interface for host software to communicate with a nonvolatile memory subsystem (e.g., a solid state drive (SSD)) through a peripheral component interconnect express (PCIe) bus.

[0051] exist Figure 4In an example embodiment, the vehicle status mode command CMD may include data in units of multiple bytes. For example, the vehicle status mode command (Vehicle Status Mode CMD) may include command start data CDW0 at a position of 03:00 and a command identifier (e.g., namespace identifier) ​​NSID at a position of 08:04. In addition, the vehicle status mode command (Vehicle Status Mode CMD) may include a reserved preliminary data string at a position of 15:08 and command definition data Definition at a position of 39:16. In addition, the vehicle status mode command (VehicleStatus Mode CMD) may include data stripe information (e.g., the number of dwords in data transmission) NDT transmitted at a position of 43:40 and metadata information (e.g., the number of dwords in metadata transmission) NDM transmitted at a position of 47:44.

[0052] The vehicle status mode command (Vehicle Status Mode CMD) according to an example embodiment may include first command information (e.g., command dword 12) CDW12 at position 51:48, second command information (e.g., command dword 13) CDW13 at position 55:52, third command information (e.g., command dword 14) CDW14 at position 59:56, and fourth command information (e.g., command dword 15) CDW15 at position 63:60. The host 200 according to an example embodiment may generate the vehicle status mode command (Vehicle Status Mode CMD) by using the NVMe standard, and change data of the first command information CDW12, the second command information CDW13, the third command information CDW14, or the fourth command information CDW15 to determine a background job to be executed. For example, the host 200 may determine the background information data to be executed for the data of the first command information CDW12, the second command information CDW13, the third command information CDW14, or the fourth command information CDW15, and cause the background job to be executed in the vehicle status mode of the storage device 100. However, the memory system 10 according to the example embodiment using the NVMe standard is merely an example for generating a vehicle status mode command (Vehicle Status Mode CMD), and the vehicle status mode command (Vehicle Status Mode CMD) may be generated by using various methods.

[0053] Figure 5 is a flowchart illustrating an operating method of a memory device according to example embodiments.

[0054] refer to Figure 1 and Figure 5 , the storage device 100 according to the example embodiment may receive a vehicle status mode command (Vehicle Status Mode CMD) from the host 200 ( S510 ).

[0055] The host 200 according to the example embodiment may generate a vehicle status mode command (Vehicle Status Mode CMD) and transmit the generated vehicle status mode command (Vehicle Status Mode CMD) to the storage device 100. The host 200 according to the example embodiment may be included in a vehicle to generate a plurality of commands and transmit the plurality of commands to the storage device 100.

[0056] When the vehicle status mode command (Vehicle Status Mode CMD) is received, the storage device 100 according to the example embodiment may perform a background job based on the received vehicle status mode command (Vehicle Status Mode CMD) (S520).

[0057] A background job according to an example embodiment may be a job performed by the storage device 100 without a separate individual command from the host 200. For example, the background job may include at least one of a garbage collection operation, a patrol read operation, a refresh operation, a data retention check operation, and a reclaim operation of the storage device 100, but is not limited thereto, and may also include a job that the storage device 100 can perform without using a separate command.

[0058] The storage device 100 according to the example embodiment may generate a command about a background job based on a vehicle status mode command (Vehicle Status Mode CMD) received from the host 200, and determine whether the vehicle state is a state in which a background job can be executed. The storage device 100 according to the example embodiment may generate classified background jobs based on the determination result. In addition, when it is determined that the vehicle state is a state in which a background job can be executed, the storage device 100 according to the example embodiment may classify the vehicle state into at least one of a start state, a driving state, a stop state, a charging state, and a driving stop state, and determine the order of the background jobs based on the classified vehicle state. The storage device 100 according to the example embodiment may generate classified background jobs based on the determination result, determine the order of the generated background jobs, and execute the background jobs in the determined order. For example, when it is determined that the vehicle state is a state in which a background job can be executed, the storage device 100 may determine the order of the background jobs based on the vehicle state, and perform at least one of a garbage collection operation, a patrol read operation, a refresh operation, a data retention check operation, and a recycling operation in the determined order.

[0059] Figure 6 is a flowchart illustrating a process of executing a background job in an operation method of a storage device according to example embodiments.

[0060] refer to Figure 1 and Figure 6 , the storage device 100 according to the example embodiment may receive a vehicle status mode command (Vehicle Status Mode CMD) from the host 200 (S610). The vehicle status mode according to the example embodiment refers to a state in which the host 200 can determine a vehicle status and determine whether to execute a background job. The storage device 100 according to the example embodiment may receive a vehicle status mode command (Vehicle Status Mode CMD) from the host 200, and execute a background job based on the received vehicle status mode command (Vehicle Status Mode CMD).

[0061] When the vehicle status mode command (Vehicle Status Mode CMD) is received, the storage device 100 according to the example embodiment may generate a command regarding a background job based on the received vehicle status mode command (Vehicle Status Mode CMD) (S620).

[0062] The storage device 100 according to the example embodiment may receive a vehicle status mode command (VehicleStatus Mode CMD) from the host 200, and perform a background job based on the received vehicle status mode command (Vehicle Status Mode CMD). For example, the storage device 100 may receive a vehicle status mode command (Vehicle StatusMode CMD) from the host 200, determine a background job according to a vehicle status, and generate a command BG Assign for a background job required (or used) by the vehicle.

[0063] The storage device 100 according to the example embodiment may receive a command regarding a background job and determine whether the vehicle state is a state in which the background job can be executed (S630). The storage device 100 according to the example embodiment may receive a command BG Assign regarding a background job and determine whether the vehicle state is a state in which the background job can be executed, and generate a classified background job based on the determination result.

[0064] When it is determined that the vehicle state is a state in which the background job may be executed, the storage device 100 according to the example embodiment may generate classified background jobs ( S640 and S650 ).

[0065] The storage device 100 according to the example embodiment may generate a necessary (or advantageous) background job according to the vehicle state. For example, the storage device 100 may generate a command BG Assign for a background job required (or used) by the vehicle according to the vehicle state, and generate a background job according to the vehicle state based on the command BG Assign for the background job. The generation of a background job according to the example embodiment may mean that the storage device 100 generates input data for executing the background job.

[0066] However, when it is determined that the vehicle state is a state in which the background job may not be executed, the storage device 100 according to an example embodiment may terminate the background job without executing the background job.

[0067] When it is determined that the vehicle state is a state in which the background job can be executed and the classified background job is generated, the storage device 100 according to an example embodiment may execute the background job generated by the scheduler 120 ( S660 ).

[0068] When it is determined that the vehicle state is a state in which a background job can be executed, the storage device 100 according to the example embodiment may classify the vehicle state into at least one of a startup state, a driving state, a stop state, a charging state, and a driving stop state, and determine the order of the background jobs based on the classified vehicle state. For example, when it is determined that the vehicle state is a state in which a background job can be executed, the storage device 100 may determine the order of the background jobs based on the vehicle state, and perform at least one of a garbage collection operation, a patrol read operation, a refresh operation, a data retention check operation, and a recycling operation in the determined order.

[0069] Figure 7 and Figure 8 is a flowchart illustrating an operation method of a storage device when a vehicle state is a start-up state according to an example embodiment.

[0070] Figure 7 is a flow chart illustrating an example embodiment in which a memory device performs a data retention operation in a startup state. Figure 8 is a flow chart illustrating an example embodiment in which a memory device performs a garbage collection operation in a startup state.

[0071] refer to Figure 1 and Figure 7 , the storage device 100 according to the example embodiment may receive a vehicle status mode command (Vehicle Status Mode CMD) from the host 200 (S710). The vehicle status mode according to the example embodiment refers to a state in which the host 200 can determine a vehicle status and determine whether to execute a background job. The storage device 100 according to the example embodiment may receive a vehicle status mode command (Vehicle Status Mode CMD) from the host 200, and execute a background job based on the received vehicle status mode command (Vehicle Status Mode CMD).

[0072] When receiving the vehicle status mode command (Vehicle Status Mode CMD), the storage device 100 according to the example embodiment may determine whether the vehicle status is a startup status (S720). The startup status according to the example embodiment may be a status in which power is started to be supplied to the vehicle.

[0073] When it is determined that the vehicle state is the startup state, the memory device 100 according to the example embodiment may perform a data retention check operation of the memory device 100 (S730). For example, when power starts to be supplied to the vehicle, the scheduler 120 may perform a data retention check operation of the memory device 100. The data retention check operation according to the example embodiment may include an operation of determining whether at least one memory cell included in the memory device 100 is degraded and whether data stored therein must be retained.

[0074] However, when it is determined that the vehicle state is not the startup state, the storage device 100 according to the example embodiment may continuously receive a vehicle status mode command (Vehicle Status Mode CMD).

[0075] When performing the data retention check operation of the storage device 100, the storage device 100 according to the example embodiment may determine whether there is a storage block of the retention target (S740). When it is determined that there is a storage block of the retention target, the storage device 100 according to the example embodiment may classify the data retention operation of the storage device 100 as an urgent background job (S750).

[0076] When it is determined that there is a storage block of the retention target, the scheduler 120 according to an example embodiment may classify the data retention operation of the storage device 100 as an urgent background job. The urgent background job according to an example embodiment may be a job that must be executed with the highest priority (or, with a priority) among the background jobs determined by the scheduler 120.

[0077] However, when it is determined that there is no memory block of the retention target, the memory device 100 according to example embodiments may terminate the background job.

[0078] refer to Figure 1 and Figure 8 , the storage device 100 according to the example embodiment may receive a vehicle status mode command (Vehicle Status Mode CMD) from the host 200 (S810). The vehicle status mode according to the example embodiment refers to a state in which the host 200 can determine a vehicle status and determine whether to execute a background job. The storage device 100 according to the example embodiment may receive a vehicle status mode command (Vehicle Status Mode CMD) from the host 200, and execute a background job based on the received vehicle status mode command (Vehicle Status Mode CMD).

[0079] When receiving the vehicle status mode command (Vehicle Status Mode CMD), the storage device 100 according to the example embodiment may determine whether the vehicle status is a startup status (S820). The startup status according to the example embodiment may be a status in which power is started to be supplied to the vehicle.

[0080] When it is determined that the vehicle state is the startup state, the memory device 100 according to the example embodiment may perform a garbage collection operation of the memory device 100 (S830). For example, when the vehicle state is the startup state, the scheduler 120 may generate a background job for the garbage collection operation of the memory device 100 and perform the garbage collection operation. When it is determined that the vehicle state is the startup state, the memory device 100 according to the example embodiment may determine whether invalid data exists in the memory block, move valid data in the memory block, and erase the memory block to obtain a free block.

[0081] Fig. 9 is a flowchart illustrating an operation method of a storage device when a vehicle state is a driving state according to an example embodiment.

[0082] refer to Figure 1 and Fig. 9 , the storage device 100 according to the example embodiment may receive a vehicle status mode command (Vehicle Status Mode CMD) from the host 200 (S910). The vehicle status mode according to the example embodiment refers to a state in which the host 200 can determine a vehicle status and determine whether to execute a background job. The storage device 100 according to the example embodiment may receive a vehicle status mode command (Vehicle Status Mode CMD) from the host 200, and execute a background job based on the received vehicle status mode command (Vehicle Status Mode CMD).

[0083] When receiving the vehicle status mode command (Vehicle Status Mode CMD), the storage device 100 according to the example embodiment may determine whether the vehicle status is a driving status (S920). The driving status according to the example embodiment may be a status in which the vehicle moves without stopping when power is supplied to the vehicle.

[0084] When it is determined that the vehicle state is the driving state, the storage device 100 according to the example embodiment may stop the background job (S930). When it is determined that the vehicle state is the driving state, the scheduler 120 may stop the background job executed by the vehicle and execute the job according to a specific command.

[0085] However, when it is determined that the vehicle state is not the driving state, the storage device 100 according to the example embodiment may perform a background job ( S940 ).

[0086] Fig.10 is a flowchart illustrating an operation method of a storage device when a vehicle state is a stop state according to an example embodiment.

[0087] refer to Figure 1 and Fig.10, the storage device 100 according to the example embodiment may receive a vehicle status mode command (Vehicle Status Mode CMD) from the host 200 (S1010). The vehicle status mode according to the example embodiment refers to a state in which the host 200 can determine a vehicle status and determine whether to execute a background job. The storage device 100 according to the example embodiment may receive a vehicle status mode command (Vehicle Status Mode CMD) from the host 200, and execute a background job based on the received vehicle status mode command (Vehicle Status Mode CMD).

[0088] When receiving the vehicle status mode command (Vehicle Status Mode CMD), the storage device 100 according to the example embodiment may determine whether the vehicle status is a stop state (S1020). The stop state according to the example embodiment may be a state in which power is supplied to the vehicle and the vehicle does not move.

[0089] When it is determined that the vehicle state is a stop state, the storage device 100 according to the example embodiment may determine whether the vehicle state is a normal stop state or a signal waiting state (S1030). The normal stop state according to the example embodiment may be a state in which the vehicle stops running while being powered and is not in a signal waiting state. The signal waiting state according to the example embodiment may be a state in which the vehicle stops running and stops to wait for a signal based on a detection result of a sensor installed in the vehicle.

[0090] When it is determined that the vehicle state is a normal stop state, the storage device 100 according to example embodiments may perform an emergency background job ( S1040 and S1050 ).

[0091] When the vehicle state is a normal stop state, the scheduler 120 according to the example embodiment may execute only the emergency background job (or, the scheduler 120 may execute the emergency background job). The emergency background job according to the example embodiment may be a background job having the highest priority (or, having priority) among the background jobs generated by the scheduler 120. For example, when the vehicle state is a normal stop state, the scheduler 120 may generate only the emergency background job (or, the scheduler 120 may generate the emergency background job). When the generated emergency background job is a data retention operation, the scheduler 120 according to the example embodiment may execute only the data retention operation when the vehicle state is a normal stop state (or, the scheduler 120 may execute the data retention operation when the vehicle state is a normal stop state).

[0092] However, when it is determined that the vehicle state is not a normal stop state, the storage device 100 according to the example embodiment may determine whether the vehicle state is a signal waiting state or a charging state (S1060). The charging state according to the example embodiment may be a state in which the vehicle stops and receives power from an external power source to charge the battery in the vehicle.

[0093] When it is determined that the vehicle state is the signal waiting state or the charging state, the storage device 100 according to the example embodiment may execute the generated background job ( S1070 ).

[0094] For example, the scheduler 120 may determine whether the vehicle state is a normal stop state or a signal waiting state based on a sensor installed in the vehicle. When it is determined that the vehicle state is a signal waiting state, the scheduler 120 according to the exemplary embodiment may determine that a background job can be executed within the signal waiting time, and generate a background job to be executed. For example, when it is determined that the signal waiting time is 3 minutes according to the result of sensor detection, the scheduler 120 may generate a background job to be executed for 3 minutes. However, the signal waiting time is not limited thereto.

[0095] In another example, when the vehicle state is a charging state, the scheduler 120 may generate background jobs based on the received vehicle state mode command and determine the order of the generated background jobs. When the vehicle state is a charging state, the scheduler 120 according to an example embodiment may generate background jobs so that the generated background jobs are executed sequentially.

[0096] However, when it is determined that the vehicle state is not the signal waiting state or the charging state, the storage device 100 according to the example embodiment may terminate the background job.

[0097] Fig.11 is a flowchart illustrating an operation method of a storage device when a vehicle state is a driving stop state according to an example embodiment.

[0098] refer to Figure 1 and Fig.11 , the storage device 100 according to the example embodiment may receive a vehicle status mode command (Vehicle Status Mode CMD) from the host 200 (S1110). The vehicle status mode according to the example embodiment refers to a state in which the host 200 can determine a vehicle status and determine whether to execute a background job. The storage device 100 according to the example embodiment may receive a vehicle status mode command (Vehicle Status Mode CMD) from the host 200, and execute a background job based on the received vehicle status mode command (Vehicle Status Mode CMD).

[0099] When receiving the vehicle status mode command (Vehicle Status Mode CMD), the storage device 100 according to the example embodiment may determine whether the vehicle status is a driving stop state (S1120). The driving stop state according to the example embodiment may be a state in which the vehicle is stopped and power supply to the vehicle is disconnected.

[0100] When it is determined that the vehicle state is the driving stop state, the storage device 100 according to the example embodiment may receive power-off time information about the storage device 100 (S1130). For example, when the vehicle state is the driving stop state, the power supply to the storage device 100 may also be disconnected. When the vehicle state is the driving stop state, the storage device 100 according to the example embodiment may receive time information until the power supply to the storage device 100 is completely disconnected (or disconnected).

[0101] The storage device 100 according to example embodiments may determine an order of generated background jobs ( S1140 ).

[0102] For example, when the vehicle state is a charging state, the storage device 100 may generate background jobs based on the received vehicle state mode command and determine the order of the generated background jobs. When the vehicle state is a charging state, the storage device 100 according to an example embodiment may generate background jobs so that the generated background jobs are executed sequentially.

[0103] When the power off time information is received and the order of the background jobs is determined, the memory device 100 according to example embodiments may execute the background jobs in a priority order based on the power off time information ( S1150 ).

[0104] For example, when the vehicle state is a driving stop state, the storage device 100 according to example embodiments may receive power-off time information about the storage device 100 , determine the order of generated background jobs, and execute the background jobs in priority order based on the power-off time information.

[0105] Fig.12 is a flowchart illustrating a method of operating a memory system according to an example embodiment.

[0106] refer to Figure 1 and Fig.12 , the storage device 100 according to the example embodiment may be in a normal mode state (S1210). The normal mode state according to the example embodiment may be a state in which the storage device 100 does not perform a background job and performs a preset operation based on an individual command received from the host 200. The background job according to the example embodiment may be a job performed by the storage device 100 without a separate individual command from the host 200.

[0107] The host 200 according to the exemplary embodiment may determine whether the vehicle supports a vehicle state mode (S1220). The vehicle state mode according to the exemplary embodiment refers to a state in which the host 200 may determine a vehicle state and determine whether to execute a background job.

[0108] When it is determined that the vehicle supports the vehicle status mode, the host 200 according to the example embodiment may send a vehicle status mode command (Vehicle Status Mode CMD) to the storage device 100 (S1230). For example, the host 200 may generate a vehicle status mode command (Vehicle Status Mode CMD) and send the generated vehicle status mode command (Vehicle Status Mode CMD) to the storage device 100. The host 200 according to the example embodiment may be included in the vehicle, and generates a plurality of commands and sends the plurality of commands to the storage device 100.

[0109] However, in some example embodiments, when it is determined that the vehicle does not support the vehicle status mode, the host 200 may terminate the execution of the background job without sending the vehicle status mode command (Vehicle Status Mode CMD).

[0110] When a vehicle status mode command (Vehicle Status Mode CMD) is received, the storage device 100 according to the example embodiment may switch to a vehicle status mode (S1240).

[0111] When switching to the vehicle state mode, the storage device 100 according to the example embodiment may perform a background job (S1250). The background job according to the example embodiment may be a job performed by the storage device 100 without a separate individual command from the host 200. For example, the background job may include at least one of a garbage collection operation, a patrol read operation, a refresh operation, a data retention check operation, and a reclaim operation of the storage device 100, but is not limited thereto, and may also include a job that can be performed by the storage device 100 without using a separate command.

[0112] The storage device 100 according to the example embodiment may generate a command about a background job based on a vehicle status mode command (Vehicle Status Mode CMD) received from the host 200, and determine whether the vehicle state is a state in which the background job can be executed. The storage device 100 according to the example embodiment may generate classified background jobs based on the determination result. In addition, when it is determined that the vehicle state is a state in which the background job can be executed, the storage device 100 according to the example embodiment may set the vehicle state to at least one of a start state, a driving state, a stop state, a charging state, and a driving stop state, and determine the order of the background jobs based on the set vehicle state. The storage device 100 according to the example embodiment may generate a background job based on the determination result, determine the order of the generated background jobs, and execute the background jobs in the determined order. For example, when it is determined that the vehicle state is a state in which the background job can be executed, the storage device 100 may determine the order of the background jobs based on the vehicle state, and execute at least one of a garbage collection operation, a patrol read operation, a refresh operation, a data retention check operation, and a recycling operation in the determined order. When executing the background job, the storage device 100 according to the example embodiment may send a report signal Report about the background job result to the host 200.

[0113] When receiving the report signal about the background job result, the host 200 according to the exemplary embodiment may send a normal mode command (Normal Mode CMD) to the storage device 100 (S1260). For example, when receiving the report signal about the background job result, the host 200 may determine that the background job has been successfully executed and switch the vehicle mode back to the normal mode.

[0114] When receiving the normal mode command Normal Mode CMD, the storage device 100 according to the example embodiment may perform a vehicle state mode deactivation operation and a normal mode switching operation (S1270). The storage device 100 according to the example embodiment may perform a preset operation based on an individual command from the host 200 in the normal mode.

[0115] Figures 13 to 15 A three-dimensional V-NAND structure that may be applied to a memory device according to example embodiments is illustrated.

[0116] refer to Figures 13 to 15 , which can be applied to Figure 1 The illustrated first nonvolatile memory 110_1 of the memory device 100 may include a plurality of memory blocks. Fig.13 and Fig.14 shows the structure of a storage block BLKi among the plurality of storage blocks, and Fig.15 It is shown that when the memory device 100 ( Figure 1) is an implementation example when the memory is non-volatile.

[0117] refer to Fig.13 , the memory block BLKi may include a plurality of memory NAND strings NS11 to NS33 connected between the bit lines BL1, BL2, and BL3 and the common source line CSL. The plurality of memory NAND strings NS11 to NS33 may each include a string selection transistor SST, a plurality of memory cells MC1 to MC8, and a ground selection transistor GST. For the sake of simplicity of the drawings, Fig.13 The plurality of memory NAND strings NS11 to NS33 are shown to each include eight memory cells MC1 to MC8 , but are not limited thereto.

[0118] The string selection transistor SST may be connected to a corresponding string selection line among a plurality of string selection lines SSL1, SSL2, and SSL3. A plurality of memory cells MC1 to MC8 may be connected to a plurality of gate lines GTL1 to GTL8, respectively. A plurality of gate lines GTL1 to GTL8 may correspond to a plurality of word lines, and some of the plurality of gate lines GTL1 to GTL8 may correspond to dummy word lines. A ground selection transistor GST may be connected to a corresponding ground selection line among a plurality of ground selection lines GSL1, GSL2, and GSL3. The string selection transistor SST may be connected to a corresponding bit line among bit lines BL1, BL2, and BL3, and the ground selection transistor GST may be connected to a common source line CSL.

[0119] Gate lines (eg, GTL1) of the same height may be connected to each other, and a plurality of ground selection lines GSL1, GSL2, and GSL3 may be selected from a plurality of string selection lines SSL1, SSL2, and SSL3. Fig.13 It is shown that the memory block BLK is connected to eight gate lines GTL1 to GTL8 and three bit lines BL1 , BL2 , and BL3 , but the inventive concept is not limited thereto.

[0120] refer to Fig.14 , the memory block BLKi is formed in a vertical direction with respect to the substrate SUB. The memory cells constituting each of the memory NAND strings NS11 to NS33 are formed by being stacked in a plurality of semiconductor layers.

[0121] A common source line CSL extending in a first direction (Y direction) is located on a substrate SUB. In a region between two adjacent common source lines CSL on the substrate SUB, a plurality of insulating layers IL extending in the first direction (Y direction) are sequentially arranged in a third direction (Z direction), and may be separated from each other by a certain distance in the third direction (Z direction). A plurality of pillars P may be sequentially arranged in a region between two adjacent common source lines CSL on the substrate SUB in the first direction (Y direction), and pass through a plurality of insulating layers IL. The plurality of pillars P may pass through a plurality of insulating layers IL to contact the substrate SUB. A surface layer S of each of the plurality of pillars P may include a silicon material doped with impurities of a first conductive type, and may be used as a channel region.

[0122] The inner layer I of each of the plurality of pillars P may include an insulating material (such as silicon oxide) or an air gap. In the region between two adjacent common source lines CSL, a charge storage layer CS may be provided along the exposed surfaces of the plurality of insulating layers IL, the plurality of pillars P, and the substrate SUB. The charge storage layer CS may include a gate insulating layer (also referred to as a "tunnel insulating layer"), a charge trapping layer, and a blocking insulating layer. In addition, in the region between the two adjacent common source lines CSL, gate electrodes GE such as selection lines GSL and SSL and a plurality of word lines WL1 to WL8 may be provided on the exposed surface of the charge storage layer CS. The drain or drain contact DR may be respectively located on the plurality of pillars p. The bit lines BL1 to BL3 extending in the second direction (X direction) and separated from each other by a certain distance in the first direction (Y direction) may be respectively located on the drain contact DR.

[0123] like Fig.14 As shown, each of the plurality of memory NAND strings NS11 to NS33 may also have a structure in which a first memory stack ST1 and a second memory stack ST2 are stacked. The first memory stack ST1 may be connected to a common source line CSL, the second memory stack ST2 may be connected to bit lines BL1 to BL3, and the first memory stack ST1 and the second memory stack ST2 are stacked to share a channel hole with each other.

[0124] refer to Fig.15, the nonvolatile memory may have a chip-to-chip (C2C) structure. In the C2C structure, an upper chip including a cell region CELL may be located on a first wafer, a lower chip including a peripheral circuit region PERI may be located on a second wafer different from the first wafer, and the upper chip may be connected to the lower chip by bonding. For example, bonding may refer to electrically connecting a bonding metal formed on the uppermost metal layer of the upper chip to a bonding metal formed on the uppermost metal layer of the lower chip. For example, when the bonding metal is copper (Cu), the bonding may be a Cu-Cu bonding, and the bonding metal may also include aluminum (Al) or tungsten (W), but example embodiments are not limited thereto.

[0125] Each of the peripheral circuit region PERI and the cell region CELL of the nonvolatile memory may include an external pad bonding region PA, a word line bonding region WLBA, and a bit line bonding region BLBA.

[0126] The peripheral circuit region PERI may include a first substrate 210, an interlayer insulating layer 215, a plurality of circuit elements 220a, 220b, and 220c formed on the first substrate 210, first metal layers 230a, 230b, and 230c respectively connected to the plurality of circuit elements 220a, 220b, and 220c, and second metal layers 240a, 240b, and 240c respectively formed on the first metal layers 230a, 230b, and 230c. In example embodiments, the first metal layers 230a, 230b, and 230c may be formed of tungsten having a relatively high resistivity, and the second metal layers 240a, 240b, and 240c may be formed of copper having a relatively low resistivity.

[0127] Although only the first metal layers 230a, 230b, and 230c and the second metal layers 240a, 240b, and 240c are shown and described, the inventive concept is not limited thereto, and at least one metal layer may be formed on the second metal layers 240a, 240b, and 240c. At least some of the one or more metal layers formed on the second metal layers 240a, 240b, and 240c may be formed of aluminum or the like, which has a lower resistivity than copper forming the second metal layers 240a, 240b, and 240c.

[0128] The interlayer insulating layer 215 may be located on the first substrate 210 to cover the plurality of circuit elements 220a, 220b, 220c, the first metal layers 230a, 230b and 230c, and the second metal layers 240a, 240b and 240c, and may include an insulating material such as silicon oxide, silicon nitride, or the like.

[0129] The lower bonding metals 271b and 272b may be formed on the second metal layer 240b of the word line bonding area WLBA. In the word line bonding area WLBA, the lower bonding metals 271b and 272b of the peripheral circuit area PERI may be electrically connected to the upper bonding metals 371b and 372b of the cell area CELL by a bonding method, and the lower bonding metals 271b and 272b and the upper bonding metals 371b and 372b may each be formed of aluminum, copper, or tungsten, but example embodiments are not limited thereto.

[0130] The cell region CELL may provide at least one memory block. The cell region CELL may include a second substrate 310 and a common source line 320. A plurality of word lines 331 to 338 (or 330) may be stacked on the second substrate 310 in a direction (Z-axis direction) perpendicular to the upper surface of the second substrate 310. The string selection line and the ground selection line may be arranged above and below the word line 330, respectively, and the plurality of word lines 330 may be located between the string selection line and the ground selection line.

[0131] In the bit line bonding area BLBA, the channel structure CH may extend in a direction (Z-axis direction) perpendicular to the upper surface of the second substrate 310 to pass through a plurality of word lines 330, string selection lines, and ground selection lines. The channel structure CH may include a data storage layer, a channel layer, and a buried insulating layer, and the channel layer may be electrically connected to the first metal layer 350c and the second metal layer 360c. For example, the first metal layer 350c may be a bit line contact, and the second metal layer 360c may be referred to as a bit line 360c. In an example embodiment, the bit line 360c may extend in a first direction (Y-axis direction) parallel to the upper surface of the second substrate 310.

[0132] The region where the channel structure CH and the bit line 360c are arranged may be defined as a bit line bonding region BLBA. In the bit line bonding region BLBA and the peripheral circuit region PERI, the bit line 360c may be electrically connected to the circuit element 220c included in the page buffer 393. For example, the bit line 360c may be connected to the upper bonding metals 371c and 372c, and the upper bonding metals 371c and 372c may be connected to the lower bonding metals 271c and 272c, and the lower bonding metals 271c and 272c are connected to the circuit element 220c of the page buffer 393 in the peripheral circuit region PERI.

[0133] In the word line bonding area WLBA, a plurality of word lines 330 may extend in a second direction (X-axis direction) perpendicular to the first direction and parallel to the upper surface of the second substrate 310, and may be connected to a plurality of cell contact plugs 341 to 347 (or 340). The plurality of word lines 330 may be connected to the plurality of cell contact plugs 340 through pads, respectively, which are formed by at least some of the plurality of word lines 330 extending in different lengths in the second direction. The first metal layer 350b and the second metal layer 360b may be sequentially connected to the upper portion of each of the plurality of cell contact plugs 340 respectively connected to the plurality of word lines 330. The plurality of cell contact plugs 340 in the word line bonding area WLBA may be connected to the lower bonding metals 271b and 272b in the peripheral circuit area PERI through the upper bonding metals 371b and 372b in the cell area CELL.

[0134] The plurality of cell contact plugs 340 may be electrically connected to the circuit element 220 b included in the row decoder 394 in the peripheral circuit region PERI. In example embodiments, an operating voltage of the circuit element 220 b included in the row decoder 394 may be different from an operating voltage of the circuit element 220 c included in the page buffer 393. For example, an operating voltage of the circuit element 220 c included in the page buffer 393 may be greater than an operating voltage of the circuit element 220 b included in the row decoder 394.

[0135] The common source line contact plug 380 may be located in the external pad bonding area PA. The common source line contact plug 380 may be formed of a conductive material such as a metal, a metal compound, or polysilicon, and may be electrically connected to the common source line 320. The first metal layer 350a and the second metal layer 360a may be sequentially stacked on the common source line contact plug 380. For example, a region where the common source line contact plug 380, the first metal layer 350a, and the second metal layer 360a are arranged may be defined as the external pad bonding area PA.

[0136] In addition, the first input / output pad 205 and the second input / output pad 305 may be located in the external pad bonding area PA. A lower insulating layer 201 covering the lower surface of the first substrate 210 may be formed on a lower portion of the first substrate 210, and the first input / output pad 205 may be formed on the lower insulating layer 201. The first input / output pad 205 may be connected to at least one of the plurality of circuit elements 220a, 220b, and 220c in the peripheral circuit region PERI through the first input / output contact plug 203, and may be separated from the first substrate 210 by the lower insulating layer 201. In addition, a side insulating layer may be located between the first input / output contact plug 203 and the first substrate 210 to electrically isolate the first input / output contact plug 203 from the first substrate 210.

[0137] An upper insulating layer 301 covering an upper surface of the second substrate 310 may be formed on the second substrate 310, and a second input / output pad 305 may be located on the upper insulating layer 301. The second input / output pad 305 may be connected to at least one of the plurality of circuit elements 220a, 220b, and 220c in the peripheral circuit region PERI through a second input / output contact plug 303. In example embodiments, the second input / output pad 305 may be electrically connected to the circuit element 220a.

[0138] In some example embodiments, the second substrate 310, the common source line 320, etc. may not be located in the region where the second input / output contact plug 303 is arranged. In addition, the second input / output pad 305 may not overlap with the plurality of word lines 330 in the third direction (Z-axis direction). The second input / output contact plug 303 may be separated from the second substrate 310 in a direction parallel to the upper surface of the second substrate 310, and may pass through the interlayer insulating layer 315 in the cell region CELL to be connected to the second input / output pad 305.

[0139] In some example embodiments, the first input / output pad 205 and the second input / output pad 305 may be selectively formed. For example, the nonvolatile memory 110_1 may include (or, may include only) the first input / output pad 205 located on the upper portion of the first substrate 210, or may include (or, may include only) the second input / output pad 305 located on the upper portion of the second substrate 310. Alternatively, the nonvolatile memory 110_1 may include both the first input / output pad 205 and the second input / output pad 305.

[0140] In the respective external pad bonding area PA and the bit line bonding area BLBA in each of the cell area CELL and the peripheral circuit area PERI, the metal pattern of the uppermost metal layer may be formed as a dummy pattern, or the uppermost metal layer may not be formed.

[0141] In the external pad bonding area PA of the nonvolatile memory 110_1, a lower metal pattern 273a having the same shape as the upper metal pattern 372a of the cell area CELL may be formed on the uppermost metal layer in the peripheral circuit area PERI to correspond to the upper metal pattern 372a formed on the uppermost metal layer in the cell area CELL. The lower metal pattern 273a formed on the uppermost metal layer in the peripheral circuit area PERI may not be connected to a separate contact in the peripheral circuit area PERI. Similarly, in the external pad bonding area PA, an upper metal pattern 373a having the same shape as the lower metal pattern 273a in the peripheral circuit area PERI may also be formed on the upper metal layer in the cell area CELL to correspond to the lower metal pattern 273a formed on the uppermost metal layer in the peripheral circuit area PERI.

[0142] Lower bonding metals 271b and 272b may be formed on the second metal layer 240b in the word line bonding area WLBA. In the word line bonding area WLBA, lower bonding metals 271b and 272b in the peripheral circuit area PERI may be electrically connected to upper bonding metals 371b and 372b in the cell area CELL by a bonding method.

[0143] Furthermore, in the bit line bonding area BLBA, an upper metal pattern 392 having the same shape as the lower metal pattern 252 in the peripheral circuit area PERI may be formed on the uppermost metal layer in the cell area CELL to correspond to the lower metal pattern 252 formed on the uppermost metal layer in the peripheral circuit area PERI. No contact may be formed on the upper metal pattern 392 formed on the uppermost metal layer in the cell area CELL.

[0144] One or more elements disclosed above may be included in a processing circuit or implemented in a processing circuit, such as hardware including a logic circuit; a hardware / software combination, such as a processor that executes software; or a combination thereof. For example, the processing circuit may more specifically include, but is not limited to, a central processing unit (CPU), an arithmetic logic unit (ALU), a digital signal processor, a microcomputer, a field programmable gate array (FPGA), a system on a chip (SoC), a programmable logic unit, a microprocessor, an application specific integrated circuit (ASIC), etc.

[0145] As described above, some inventive concepts are described through various exemplary embodiments, and those skilled in the art to which the inventive concept belongs will be able to make various modifications and changes to the above-mentioned various exemplary embodiments without departing from the basic features of the inventive concept. Therefore, the various exemplary embodiments according to the inventive concept are for illustrative purposes, rather than limiting the technical ideas of the inventive concept, and the scope of the inventive concept is not limited to the various exemplary embodiments. The protection scope of the inventive concept according to the above-mentioned various exemplary embodiments should be interpreted according to the attached claims, and all technical ideas within the equivalent range should be interpreted as included in the scope of the rights of the inventive concept.

[0146] While the inventive concepts have been particularly shown and described with reference to certain example embodiments thereof, it will be understood that various changes in form and details may be made therein without departing from the spirit and scope of the appended claims.

Claims

1. A storage device, comprising: a command executor configured to generate a command regarding a background job based on a received vehicle state mode command; A scheduler, the scheduler being configured to: receiving the command about the background job, determining whether the vehicle state is a state capable of executing the background job, and generating the background job based on the determination result; and a background job executor configured to execute the background job generated by the scheduler, Wherein, the scheduler is further configured to: when the vehicle state is determined to be a state capable of executing the background job, set the vehicle state to at least one of a start state, a driving state, a stop state, a charging state and a driving stop state, and the scheduler is also configured to determine the order of the background jobs based on the set vehicle state.

2. The memory device according to claim 1, wherein: Each of the background jobs includes at least one of a garbage collection operation, a patrol read operation, a refresh operation, a data retention check operation, and a reclaim operation of the storage device.

3. The memory device according to claim 1, wherein: The scheduler is further configured to generate a data retention check operation of the storage device when the vehicle state is the startup state.

4. The memory device according to claim 3, wherein: The scheduler is further configured to: when there is a storage block of a retention target, set the data retention operation of the storage device as an urgent background job.

5. The memory device according to claim 1, wherein: The scheduler is further configured to generate a garbage collection operation of the storage device when the vehicle state is the startup state.

6. The memory device according to claim 1, wherein: The scheduler is further configured to stop executing the background job when the vehicle state is the driving state.

7. The memory device according to claim 1, wherein: The dispatcher is further configured to, when the vehicle state is the stopped state, determine whether the vehicle state is a normal stopped state or a signal waiting state.

8. The memory device according to claim 7, wherein: The background job executor is further configured to execute only emergency background jobs when the vehicle state is the normal stop state.

9. The memory device according to claim 1, wherein: The background job executor is further configured to execute the generated background job when the vehicle state is one of a signal waiting state or a charging state.

10. The memory device according to claim 1, wherein: The dispatcher is further configured to: when the vehicle state is the stopped state, receiving power-off time information about the storage device, and The background jobs are executed in a priority order based on the power outage time information.

11. A method for operating a storage device, the storage device comprising a command executor, a scheduler, and a background job executor, the method comprising: receiving a vehicle status mode command; as well as Execute background tasks based on received vehicle status mode commands, Wherein, executing the background job includes: The command executor generates a command regarding the background job based on the received vehicle status mode command; receiving, by the scheduler, a command regarding the background job, determining whether a vehicle state is a state capable of executing the background job, and generating the background job based on a determination result; and The background job executor executes the generated background job. Wherein, generating the background job includes: When the vehicle state is determined to be a state in which the background job can be executed, setting the vehicle state to at least one of a start state, a driving state, a stop state, a charging state, and a driving stop state, and Wherein, the order of the background operations is determined based on the set vehicle status.

12. The operating method according to claim 11, wherein: When the vehicle state is the startup state, generating the background job further includes generating a data retention check operation of the storage device.

13. The operating method according to claim 12, wherein: When it is determined that there is a storage block of the retention target, generating the background job further includes setting the data retention operation of the storage device as an urgent background job.

14. The operating method according to claim 11, wherein: When the vehicle state is the startup state, generating the background job further includes generating a garbage collection operation of the storage device.

15. The operating method according to claim 11, wherein: When the vehicle state is the driving state, generating the background job further includes stopping execution of the background job.

16. The operating method according to claim 11, wherein: When the vehicle state is the stopped state, generating the background job further includes determining whether the vehicle state is a normal stopped state or a signal waiting state.

17. The operating method according to claim 16, wherein: When the vehicle state is the normal stop state, generating the background job further includes generating only an emergency background job.

18. The operating method according to claim 11, wherein: Executing the generated background job further includes executing the generated background job when the vehicle state is one of a signal waiting state and the charging state.

19. The operating method according to claim 11, wherein: When the vehicle state is the driving stop state, power-off time information about the storage device is received, and the background jobs are executed in a priority order based on the power-off time information.

20. A memory system, the memory system comprising: a host computer configured to generate a vehicle state mode command; and a storage device configured to receive the vehicle state mode command from the host and execute a background job based on the received vehicle state mode command, Wherein, the storage device comprises: a command executor configured to receive the vehicle state mode command and generate a command regarding the background job based on the received vehicle state mode command; a scheduler configured to receive a command regarding the background job, determine whether a vehicle state is a state capable of executing the background job, and generate the background job based on a determination result; and a background job executor configured to execute the background job generated by the scheduler, The scheduler is further configured to: when the vehicle state is determined to be a state capable of executing the background job, set the vehicle state to at least one of a start state, a driving state, a stop state, a charging state, and a driving stop state, and The scheduler is further configured to determine the order of the background jobs based on the set vehicle status.

Images