Storage device and method of operation thereof

The described storage device with detachable UFS devices and a multi-channel controller system addresses the need for enhanced performance and capacity in semiconductor memory by enabling flexible expansion through removable UFS devices.

KR103045007B1Active Publication Date: 2026-11-06SAMSUNG ELECTRONICS CO LTD
View PDF 5 Cites 0 Cited by

Patent Information

Application Number
KR1020210089918
Authority / Receiving Office
KR · KR
Patent Type
Patents
Current Assignee / Owner
Filing Date
2021-07-08
Publication Date
2026-11-06
Estimated Expiration
2041-07-08

AI Technical Summary

Technical Problem

Existing semiconductor memory devices, particularly flash memory devices, lack enhanced performance and flexibility in storage capacity expansion.

Method used

A storage device comprising a connector with pins, a controller socket, and a printed circuit board with slots for detachable UFS devices, along with a storage controller that manages multiple channels for communication, allowing for removable UFS devices and non-volatile memory devices, and includes a method for initializing and managing state information upon device insertion.

Benefits of technology

The solution enables increased storage capacity by allowing additional UFS devices to be added, enhancing performance and flexibility in storage space management.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure R1020210089918_ABST
    Figure R1020210089918_ABST
Patent Text Reader

Abstract

A storage device according to an embodiment of the present disclosure comprises a connector having a plurality of pins coupled to an external host device, a controller socket, and a printed circuit board having first to fourth slots, first to fourth UFS devices detachably mounted in each of the first to fourth slots, and a storage controller mounted in the controller socket and configured to control the first to fourth UFS devices, wherein the first and second UFS devices communicate with the storage controller through a first channel, and the third and fourth UFS devices communicate with the storage controller through a second channel.
Need to check novelty before this filing date? Find Prior Art

Description

Technology Field

[0001] The present disclosure relates to a semiconductor memory, and more specifically to a storage device and a method of operating the same. Background Technology

[0002] Semiconductor memory is classified into volatile memory devices, such as SRAM and DRAM, in which stored data is lost when the power supply is cut off, and non-volatile memory devices, such as flash memory devices, PRAM, MRAM, RRAM, and FRAM, which retain stored data even when the power supply is cut off.

[0003] Flash memory devices are widely used as high-capacity storage media in computing systems. Recently, various technologies have been developed to support the high-speed operation of flash memory devices. For example, the Universal Flash Storage (UFS) interface defined by the JEDEC standard can support improved operating speeds compared to conventional flash memory-based storage devices. The problem to be solved

[0004] The object of the present disclosure is to provide a storage device having enhanced performance and a method of operating the same. means of solving the problem

[0005] A storage device according to an embodiment of the present disclosure comprises a connector having a plurality of pins coupled to an external host device, a controller socket, and a printed circuit board having first to fourth slots, first to fourth UFS devices detachably mounted in each of the first to fourth slots, and a storage controller mounted in the controller socket and configured to control the first to fourth UFS devices, wherein the first and second UFS devices communicate with the storage controller through a first channel, and the third and fourth UFS devices communicate with the storage controller through a second channel.

[0006] A method of operation of a storage device comprising a plurality of removable UFS devices and a storage controller according to an embodiment of the present disclosure, wherein when a new UFS device among the plurality of UFS devices is inserted, the storage controller receives a detection signal; the storage controller performs an initialization operation with the new UFS device in response to the detection signal; the storage controller stores state information in memory after performing the initialization operation; and the storage controller transmits the state information to an external host, wherein the state information includes information regarding the plurality of UFS devices and information regarding the size of the storage space.

[0007] A storage device according to an embodiment of the present disclosure comprises a connector having a plurality of pins coupled to an external host device, a controller socket, a first to fourth slots, and a plurality of memory sockets, a first to fourth UFS device detachably mounted in each of the first to fourth slots, a plurality of non-volatile memory devices mounted in each of the plurality of memory sockets, and a storage controller including a UFS interface circuit mounted in the controller socket and configured to control the first to fourth UFS devices and a non-volatile memory interface circuit configured to control the plurality of non-volatile memory devices, wherein the first and second UFS devices communicate with the storage controller through a first channel, and the third and fourth UFS devices communicate with the storage controller through a second channel. Effects of the invention

[0008] A storage device according to an embodiment of the present disclosure may include removable UFS devices instead of an embedded non-volatile memory device. Accordingly, the storage space of the storage device may be increased by inserting additional UFS devices. Thus, a storage device having enhanced performance and a method of operating the same are provided. Brief explanation of the drawing

[0009] FIG. 1 is a block diagram illustrating a host-storage system according to an embodiment of the present disclosure. FIG. 2 is a block diagram illustrating the UFS interface circuit and UFS device of FIG. 1 in more detail. FIG. 3a and FIG. 3b are block diagrams illustrating the storage device of FIG. 1 in more detail. FIG. 4 is a block diagram illustrating the storage device of FIG. 1 in more detail. FIG. 5a and FIG. 5b are diagrams illustrating a method for distinguishing UFS devices sharing a channel with respect to the storage device of FIG. 4. FIG. 6 is a block diagram illustrating the storage device of FIG. 1 in more detail. FIG. 7a is a diagram for explaining the form factor of a UFS card. FIG. 7b and FIG. 7c are diagrams illustrating examples of a storage device according to the present disclosure. FIG. 8 is a diagram illustrating an example of a storage device according to the present disclosure. FIG. 9 is a diagram illustrating an example of a storage device according to the present disclosure. FIG. 10 is a flowchart illustrating an example of the operation of the storage controller of FIG. 1. FIG. 11 is FIG. This is a flowchart showing step S240 of 10 in more detail. Specific details for implementing the invention

[0010] In the following, embodiments of the present disclosure will be described clearly and in detail so that a person skilled in the art can easily practice the present disclosure.

[0011] Components described by reference to terms such as part or unit, module, engine, etc. used in the detailed description and functional blocks illustrated in the drawings may be implemented in the form of software, hardware, or a combination thereof. For example, software may be machine code, firmware, embedded code, and application software. For example, hardware may include electrical circuits, electronic circuits, processors, computers, integrated circuits, integrated circuit cores, pressure sensors, inertial sensors, MEMS (microelectromechanical systems), passive components, or a combination thereof.

[0012] Furthermore, unless otherwise defined, all terms used herein, including those with a technical or scientific meaning, have a meaning that can be understood by a person skilled in the art to which this disclosure pertains. Generally, terms defined in a dictionary are interpreted to have a meaning equivalent to their contextual meaning in the relevant technical field, and are not interpreted to have an ideal or overly formal meaning unless explicitly defined in this text.

[0013] FIG. 1 is a block diagram illustrating a host-storage system (1000) according to one embodiment of the present disclosure. The host-storage system (1000) may include a host (1100) and a storage device (1200). Additionally, the storage device (1200) may include a storage controller (1210) and a plurality of UFS devices (1300). Additionally, according to one embodiment of the present disclosure, the host (1100) may include a host controller (1110) and a host memory (1120). The host memory (1120) may function as a buffer memory for temporarily storing data to be transmitted to the storage device (1200) or data transmitted from the storage device (1200).

[0014] The storage device (1200) may include storage media for storing data in response to a request from the host (1100). As an example, the storage device (1200) may include at least one of a Solid State Drive (SSD), embedded memory, and removable external memory. If the storage device (1200) is an SSD, the storage device (1200) may be a device conforming to the NVMe (non-volatile memory express) standard. If the storage device (1200) is embedded memory or external memory, the storage device (1200) may be a device conforming to the UFS (universal flash storage) or eMMC (embedded multi-media card) standard. The host (1100) and the storage device (1200) may each generate and transmit packets according to the adopted standard protocol.

[0015] The storage device (1200) may include a removable or detachable external memory. In particular, the storage device (1200) may include a plurality of removable UFS devices (1300). When each of the plurality of UFS devices (1300) includes a flash memory, the flash memory may include a 2D NAND memory array or a 3D (or vertical) NAND (VNAND) memory array. As another example, the storage device (1200) may include various other types of non-volatile memory. For example, the storage device (1200) may be equipped with Magnetic RAM (MRAM), Spin-Transfer Torque MRAM, Conductive Bridging RAM (CBRAM), Ferroelectric RAM (FeRAM), Phase RAM (PRAM), Resistive RAM, and various other types of memory.

[0016] According to one embodiment, the host controller (1110) and the host memory (1120) may be implemented as separate semiconductor chips. Alternatively, in some embodiments, the host controller (1110) and the host memory (1120) may be integrated on the same semiconductor chip. As an example, the host controller (1110) may be any one of a plurality of modules provided in an application processor, and the application processor may be implemented as a System on Chip (SoC). Additionally, the host memory (1120) may be an embedded memory provided within the application processor, or a non-volatile memory or memory module placed outside the application processor.

[0017] The host controller (1110) can manage the operation of storing data (e.g., write data) in the buffer area of ​​the host memory (1120) in a plurality of UFS devices (1300), or storing data (e.g., read data) of the plurality of UFS devices (1300) in the buffer area.

[0018] The storage controller (1210) may include a host interface circuit (1211), a UFS interface circuit (1400), and a CPU (central processing unit) (1213). Additionally, the storage controller (1210) may further include a Flash Translation Layer (FTL) (1214), a packet manager (1215), a buffer memory (1216), an ECC (error correction code) (1217) engine, and an AES (advanced encryption standard) engine (1218). The storage controller (1210) may further include a working memory (not shown) on which the Flash Translation Layer (FTL) (1214) is loaded, and data writing and reading operations for a plurality of UFS devices (1300) may be controlled by the CPU (1213) executing the Flash Translation Layer. That is, the storage controller (1210) may be configured to control a plurality of removable UFS devices (1300).

[0019] The CPU (1213) can generate an input-output request (IOR) for input / output to multiple UFS devices (1300). An input-output request (IOR) may mean a data read request (or read request), a write request (or write request), and / or a discard request, but is not necessarily limited thereto. The CPU (1213) can transmit the input-output request (IOR) to the UFS interface circuit (1400).

[0020] The host interface circuit (1211) can transmit and receive packets with the host (1100). The packet transmitted from the host (1100) to the host interface circuit (1211) may include a command or data to be written to a plurality of UFS devices (1300), and the packet transmitted from the host interface circuit (1211) to the host (1100) may include a response to the command or data read from a plurality of UFS devices (1300). The UFS interface circuit (1400) can transmit data to be written to a plurality of UFS devices (1300) to the plurality of UFS devices (1300) or receive data read from a plurality of UFS devices (1300). This UFS memory interface circuit (1400) can be implemented to comply with standard protocols such as universal flash storage (UFS).

[0021] For convenience of explanation, terms such as "command," "request," "packet," and "instruction" are used interchangeably below. Depending on the context of the embodiments, these terms may have the same or different meanings, and the meaning of each term will be understood according to the context of the embodiments described.

[0022] The flash conversion layer (1214) can perform various functions such as address mapping, wear-leveling, and garbage collection. Address mapping is an operation that converts a logical address received from the host (1100) into a physical address used to actually store data within the multiple UFS devices (1300). Wear-leveling is a technique to prevent excessive degradation of a specific block by ensuring that blocks within the multiple UFS devices (1300) are used evenly, and can be implemented, for example, through firmware technology that balances the erase counts of physical blocks. Garbage collection is a technique to secure usable capacity within the multiple UFS devices (1300) by copying the valid data of a block to a new block and then erasing the existing block.

[0023] The packet manager (1215) can generate a packet according to the protocol of the interface agreed upon with the host (1100) or parse various information from a packet received from the host (1100). Additionally, the buffer memory (1216) can temporarily store data to be written to a plurality of UFS devices (1300) or data to be read from a plurality of UFS devices (1300). The buffer memory (1216) may be a configuration provided within the storage controller (1210), but it may be placed outside the storage controller (1210).

[0024] The ECC engine (1217) can perform error detection and correction functions for read data read from multiple UFS devices (1300). More specifically, the ECC engine (1217) can generate parity bits for write data to be written to multiple UFS devices (1300), and the generated parity bits can be stored in the multiple UFS devices (1300) together with the write data. When reading data from multiple UFS devices (1300), the ECC engine (1217) can correct errors in the read data using the parity bits read from the multiple UFS devices (1300) together with the read data, and output the read data with the errors corrected.

[0025] The AES engine (1218) can perform at least one of the encryption and decryption operations on data input to the storage controller (1210) using a symmetric-key algorithm.

[0026] The storage device (1200) may include a plurality of removable UFS devices (1300) instead of embedded or built-in memory. Accordingly, the size of the storage space of the storage device (1200) may vary. For example, if the storage device (1200) does not include any UFS devices (i.e., if all UFS devices are detached from the storage device), the size of the storage space of the storage device (1200) may be minimal. As new UFS devices are installed in the storage device (1200), the size of the storage space of the storage device (1200) may increase. If the storage device (1200) includes the maximum possible number of UFS devices, the size of the storage space of the storage device (1200) may be maximum.

[0027] In one embodiment, the storage device (1200) may notify the host (1100) of an event in which a UFS device is inserted or removed, or an event in which the size of the storage space of the storage device changes. For example, if a new UFS device is inserted, the storage device (1200) may notify the host (1100) of whether a new UFS device has been inserted and the size of the increased storage space. That is, the storage device (1200) may notify the host (1100) of status information through an asynchronous event request.

[0028] For example, status information may include information regarding the status of UFS devices and information regarding the size of storage space. Information regarding the status of UFS devices may include information regarding the number of UFS devices installed in the storage device, information regarding the slots into which the installed UFS devices are inserted, and information regarding newly installed or removed UFS devices. Information regarding the size of storage space may include the size of storage space increased by inserting a UFS device, the size of storage space decreased by removing a UFS device, the total size of storage space, and the size of storage space for each UFS device.

[0029] In one embodiment, the storage device (1200) may transmit status information to the host (1100). For example, the storage device (1200) may update the status information in the log when a new UFS device is installed. The storage device (1200) may transmit an asynchronous event request completion to the host (1100). In response to the asynchronous event request completion, the host (1100) may transmit a Get Log Page command to the storage device (1200). The storage device (1200) may receive the Get Log Page command. In response to the Get Log Page command, the storage device (1200) may transmit log data containing status information and the Get Log Page completion to the host (1100). The configuration and effects according to the embodiments of the present disclosure are described in more detail with reference to the drawings below.

[0030] FIG. 2 is a block diagram showing the UFS interface circuit and UFS device of FIG. 1 in more detail. Each of the UFS interface circuit (1400) and the plurality of UFS devices (1300) can communicate through the UFS standard published by JEDEC (Joint Electron Device Engineering Council). For the sake of brevity of the drawing and convenience of explanation, only the first UFS device (1301) among the plurality of UFS devices (1300) is shown in FIG. 2. Although the remaining UFS devices among the plurality of UFS devices (1300), excluding the first UFS device (1301), are not shown in FIG. 2, the following descriptions may apply to them as well as to the first UFS device (1301).

[0031] Referring to FIG. 2, a UFS interface circuit (1400) and a first UFS device (1301) may be interconnected via a first channel (CH1). The UFS interface circuit (1400) may include a UFS controller (1410) and a UIC (UFS interconnect) layer (1420). The first UFS device (1301) may include a UFS device controller (1310), non-volatile memory (1320), a storage interface (1330), a device memory (1340), a UIC layer (1350), and a regulator (1360). The non-volatile memory (1320) may be composed of a plurality of memory units (1321), and such memory units (1321) may include V-NAND flash memory of a 2D or 3D structure, but may also include other types of non-volatile memory such as PRAM and / or RRAM. The UFS device controller (1310) and the non-volatile memory (1320) can be connected to each other through a storage interface (1330). The storage interface (1330) can be implemented to comply with standard protocols such as Toggle or ONFI.

[0032] The UFS controller (1410) can convert input / output requests into UFS commands defined by the UFS standard. The UFS controller (1410) can transmit the converted UFS commands to the UIC layer (1350) of the first UFS device (1301) through the UIC layer (1420) and the first channel (CH1). In this process, the UFS register (1411) of the UFS controller (1410) can serve as a command queue (CQ).

[0033] The UIC layer (1420) of the UFS interface circuit (1400) may include MIPI M-PHY (1421) and MIPI UniPro (1422), and the UIC layer (1350) on the side of the first UFS device (1301) may also include MIPI M-PHY (1351) and MIPI UniPro (1352).

[0034] The first channel (CH1) may include a line transmitting a reference clock (REF_CLK), a line transmitting a hardware reset signal (RESET_n) for the first UFS device (1301), a pair of lines transmitting a differential input signal pair (DIN_t and DIN_c), and a pair of lines transmitting a differential output signal pair (DOUT_t and DOUT_c).

[0035] The frequency value of the reference clock (REF_CLK) provided from the UFS interface circuit (1400) to the first UFS device (1301) may be one of four values: 19.2 MHz, 26 MHz, 38.4 MHz, and 52 MHz, but is not necessarily limited thereto. The UFS interface circuit (1400) can change the frequency value of the reference clock (REF_CLK) even while in operation, that is, while data transmission and reception is being performed between the UFS interface circuit (1400) and the first UFS device (1301). The first UFS device (1301) can generate clocks of various frequencies from the reference clock (REF_CLK) provided from the UFS interface circuit (1400) using a phase-locked loop (PLL), etc. Additionally, the UFS interface circuit (1400) may set the value of the data rate between the UFS interface circuit (1400) and the first UFS device (1301) through the frequency value of the reference clock (REF_CLK). That is, the value of the data rate may be determined depending on the frequency value of the reference clock (REF_CLK).

[0036] The first channel (CH1) may support multiple lanes, and each lane may be implemented as a differential line pair. For example, the first channel (CH1) may include one or more receive lanes and one or more transmit lanes. In FIG. 2, a pair of lines transmitting a differential input signal pair (DIN_T and DIN_C) may each constitute a receive lane, and a pair of lines transmitting a differential output signal pair (DOUT_T and DOUT_C) may each constitute a transmit lane. Although FIG. 2 illustrates one transmit lane and one receive lane, the number of transmit lanes and receive lanes may be changed.

[0037] The receiving lane and the transmitting lane can transmit data in a serial communication manner, and full-duplex communication between the UFS interface circuit (1400) and the first UFS device (1301) is possible due to the structure in which the receiving lane and the transmitting lane are separated. That is, the first UFS device (1301) can transmit data to the UFS interface circuit (1400) through the transmitting lane even while receiving data from the UFS interface circuit (1400) through the receiving lane. In addition, control data such as commands from the UFS interface circuit (1400) to the first UFS device (1301) and user data that the UFS interface circuit (1400) intends to store in the non-volatile memory (1320) of the first UFS device (1301) or read from the non-volatile memory (1320) can be transmitted through the same lane. Accordingly, there is no need to provide additional lanes for data transmission between the UFS interface circuit (1400) and the first UFS device (1301) in addition to a pair of receiving lanes and a pair of transmitting lanes.

[0038] The UFS device controller (1310) of the first UFS device (1301) can control the overall operation of the first UFS device (1301). The UFS device controller (1310) can manage non-volatile memory (1320) through a logical unit (1311) which is a logical data storage unit. The number of LUs (1311) may be eight, but is not limited thereto. The UFS device controller (1310) may include a flash translation layer (FTL) and can convert a logical data address, such as a logical block address (LBA), transmitted from the UFS interface circuit (1400) into a physical data address, such as a physical block address (PBA), using the address mapping information of the FTL. A logical block for storing user data may have a size within a predetermined range. For example, the minimum size of the logical block may be set to 4 Kbytes.

[0039] When a command from the UFS interface circuit (1400) is input to the first UFS device (1301) through the UIC layer (1350), the UFS device controller (1310) performs an operation according to the input command, and when the operation is completed, it can send a completion response to the UFS interface circuit (1400).

[0040] For example, when the UFS interface circuit (1400) intends to store user data in the first UFS device (1301), the UFS interface circuit (1400) may transmit a data storage command to the first UFS device (1301). When the UFS interface circuit (1400) receives a response from the first UFS device (1301) that the user data is ready to be transferred, the UFS interface circuit (1400) may transfer the user data to the first UFS device (1301). The UFS device controller (1310) may temporarily store the received user data in the device memory (1340) and, based on the address mapping information of the FTL, store the user data temporarily stored in the device memory (1340) in a selected location of the non-volatile memory (1320).

[0041] As another example, when the UFS interface circuit (1400) intends to read user data stored in the first UFS device (1301), the UFS interface circuit (1400) may transmit a data read command to the first UFS device (1301). Upon receiving the command, the UFS device controller (1310) may read user data from the non-volatile memory (1320) based on the data read command and temporarily store the read user data in the device memory (1340). During this read process, the UFS device controller (1310) may use an embedded ECC (error correction code) engine (not shown) to detect and correct errors in the read user data. More specifically, the ECC engine may generate parity bits for the data to be written to the non-volatile memory (1320), and the generated parity bits may be stored in the non-volatile memory (1320) together with the data to be written. When reading data from the non-volatile memory (1320), the ECC engine can correct errors in the read data using parity bits read from the non-volatile memory (1320) along with the read data, and output the read data with the errors corrected.

[0042] Additionally, the UFS device controller (1310) can transmit user data temporarily stored in the device memory (1340) to the UFS interface circuit (1400). Furthermore, the UFS device controller (1310) may further include an AES (advanced encryption standard) engine (not shown). The AES engine can perform at least one of encryption and decryption operations on data input to the UFS device controller (1310) using a symmetric-key algorithm.

[0043] The UFS interface circuit (1400) can store commands to be transmitted to the first UFS device (1301) in order in a UFS register (1411) that can function as a command queue, and can transmit commands to the first UFS device (1301) in the said order. At this time, the UFS interface circuit (1400) can transmit the next command waiting in the command queue to the first UFS device (1301) even if the previously transmitted command is still being processed by the first UFS device (1301), that is, before receiving notification that the previously transmitted command has been processed by the first UFS device (1301), and accordingly, the first UFS device (1301) can also receive the next command from the UFS interface circuit (1400) even while processing the previously transmitted command. The maximum number of commands (queue depth) that can be stored in such a command queue may be, for example, 32. Additionally, the command queue can be implemented as a circular queue type, which indicates the start and end of the column of commands stored in the queue through a head pointer and a tail pointer, respectively.

[0044] Each of the plurality of memory units (1321) may include a memory cell array (not shown) and a control circuit (not shown) that controls the operation of the memory cell array. The memory cell array may include a two-dimensional memory cell array or a three-dimensional memory cell array. The memory cell array includes a plurality of memory cells, and each memory cell may be a cell that stores 1 bit of information (single level cell, SLC), but may also be a cell that stores 2 bits or more of information, such as MLC (multi-level cell), TLC (triple-level cell), or QLC (quadruple-level cell). The three-dimensional memory cell array may include a vertically oriented NAND string such that at least one memory cell is positioned above another memory cell.

[0045] VCC, VCCQ, VCCQ2, etc., may be input as power voltages to the first UFS device (1301). VCC is the main power voltage for the first UFS device (1301) and may have a value of 2.4 to 3.6 V. VCCQ is a power voltage for supplying a low range of voltage, mainly for the UFS device controller (1310), and may have a value of 1.14 to 1.26 V. VCCQ2 is a power voltage for supplying a range of voltage lower than VCC but higher than VCCQ, mainly for an input / output interface such as MIPI M-PHY (1351), and may have a value of 1.7 to 1.95 V. The above power voltages may be supplied to each component of the first UFS device (1301) through a regulator (1360). The regulator (1360) can be implemented as a set of unit regulators each connected to different of the aforementioned power supply voltages.

[0046] As described above, the UFS interface circuit (1400) can communicate with each of the UFS devices (1300) based on the universal flash storage (UFS) interface defined by the JEDEC standard. For example, the UFS interface circuit (1400) and each of the UFS devices (1300) can exchange packets in the form of a UFS protocol information unit (UPIU). The UPIU may contain various information defined by the interface (e.g., the UFS interface) between the UFS interface circuit (1400) and each of the UFS devices (1300). However, the scope of the present disclosure is not limited thereto. For convenience of explanation, the terms command, UPIU, and data are used interchangeably below, and each term may be used with the same or different meanings depending on the embodiments described in the detailed description.

[0047] FIGS. 3a and 3b are block diagrams showing the storage device of FIG. 1 in more detail. Referring to FIGS. 3a and 3b, the storage device (1200a) may include a storage controller (1210) and a plurality of UFS devices (1300). The plurality of UFS devices (1300) may include four UFS devices (1301 to 1304). However, the scope of the present disclosure is not limited thereto, and the number of the plurality of UFS devices (1300) may be increased or decreased depending on the implementation method.

[0048] The storage controller (1210) can transmit and receive signals to and from each of the UFS devices (1300) through multiple channels (CH1 to CH4). For example, the storage controller (1210) can transmit commands, data, or UPIUs, etc., to each of the UFS devices (1300) through the channels (CH1 to CH4), or receive data from each of the UFS devices (1300).

[0049] Referring to FIG. 3a, in one embodiment, each of the plurality of UFS devices (1300) may be connected to the storage controller (1210) through a corresponding channel without sharing a channel. For example, the first UFS device (1301) may be connected to the storage controller (1210) through the first channel (CH1), the second UFS device (1302) may be connected to the storage controller (1210) through the second channel (CH2), the third UFS device (1303) may be connected to the storage controller (1210) through the third channel (CH3), and the fourth UFS device (1304) may be connected to the storage controller (1210) through the fourth channel (CH4).

[0050] Each of the multiple channels (CH1~CH4) may include a line for transmitting a reference clock (REF_CLK), a line for transmitting a hardware reset signal (RESET_n) for each of the UFS devices (1300), a pair of lines for transmitting a differential input signal pair (DIN_t and DIN_c), and a pair of lines for transmitting a differential output signal pair (DOUT_t and DOUT_c).

[0051] As described above, each of the first to fourth UFS devices (1301 to 1304) can receive a corresponding reference clock (REF_CLK) and a corresponding hardware reset signal (RESET_n) through a corresponding line. For example, the first UFS device (1301) can receive a first reference clock through a first line, and the second UFS device (1302) can receive a second reference clock through a second line. The first UFS device (1301) can receive a first hardware reset signal through a third line, and the second UFS device (1302) can receive a second hardware reset signal through a fourth line.

[0052] The storage controller (1210) can control each of the multiple UFS devices (1300) in parallel through different channels. That is, simultaneous communication is possible through the separated structure of the channels connecting the storage controller (1210) and each of the multiple UFS devices (1300). For example, the storage controller (1210) can transmit and receive data with the second UFS device (1302) through the second channel (CH2) even while transmitting and receiving data with the first UFS device (1301) through the first channel (CH1).

[0053] Referring to FIG. 3b, in one embodiment, each of the plurality of UFS devices (1300) may share a line that transmits a reference clock (REF_CLK) and a line that transmits a hardware reset signal (RESET_n).

[0054] Each of the first to fourth UFS devices (1301 to 1304) of FIG. 3b can receive a reference clock (REF_CLK) through the first line. Each of the first to fourth UFS devices (1301 to 1304) can receive a hardware reset signal (RESET_n) through the third line.

[0055] Each of the first to fourth UFS devices (1301 to 1304) can transmit and receive signals other than the reference clock (REF_CLK) and the hardware reset signal (RESET_n) through the corresponding lines. That is, each of the first to fourth UFS devices (1301 to 1304) can be connected to the storage controller (1210) through the corresponding input / output signals.

[0056] For example, a first UFS device (1301) may be connected to a storage controller (1210) via a first input signal (DIN1) and a first output signal (DOUT1), a second UFS device (1302) may be connected to a storage controller (1210) via a second input signal (DIN2) and a second output signal (DOUT2), a third UFS device (1303) may be connected to a storage controller (1210) via a third input signal (DIN3) and a third output signal (DOUT3), and a fourth UFS device (1304) may be connected to a storage controller (1210) via a fourth input signal (DIN2) and a fourth output signal (DOUT4). The first input signals (DINT1) may include a differential input signal pair, and the first output signals (DOUT1) may include a differential output signal pair. The remaining input signals (DIN2~DIN4) and output signals (DOUT2~DOUT4) are similar, so a detailed description is omitted.

[0057] As described above, the plurality of UFS devices (1300) of FIG. 3b may share a hardware reset signal (RESET_n) and a reference clock (REF_CLK), and may not share input and output signals.

[0058] FIG. 4 is a block diagram showing the storage device of FIG. 1 in more detail. Referring to FIG. 4, the storage device (1200b) may include a storage controller (1210) and a plurality of UFS devices (1300). The plurality of UFS devices (1300) may include four UFS devices (1301 to 1304). However, the scope of the present disclosure is not limited thereto, and the number of the plurality of UFS devices (1300) and the number of UFS devices connected to one channel may be increased or decreased depending on the implementation method.

[0059] Referring to FIG. 4, the storage controller (1210) can transmit and receive signals to and from each of the UFS devices (1300) through a plurality of channels (CH1, CH2). For example, the storage controller (1210) can transmit commands, data, or UPIUs, etc. to each of the UFS devices (1300) through the channels (CH1, CH2), or receive data from each of the UFS devices (1300).

[0060] In one embodiment, each of the plurality of UFS devices (1300) may share a channel. For example, the first and second UFS devices (1301, 1302) may be connected to the storage controller (1210) through the first channel (CH1). The third and fourth UFS devices (1303, 1304) may be connected to the storage controller (1210) through the second channel (CH2).

[0061] Each of the first and second channels (CH1, CH2) may include a line transmitting a reference clock (REF_CLK), a line transmitting a hardware reset signal (RESET_n) for the UFS device (1300), a pair of lines transmitting a differential input signal pair (DIN_t and DIN_c), and a pair of lines transmitting a differential output signal pair (DOUT_t and DOUT_c).

[0062] In one embodiment, the storage controller (1210) can select one of the UFS devices connected to the corresponding channel through each channel and transmit and receive signals with the selected UFS device. For example, the storage controller (1210) can select the first UFS device (1301) among the UFS devices (1301, 1302) connected to the first channel (CH1). The storage controller (1210) can transmit commands, data, UPIU, etc. to the selected first UFS device (1301) through the first channel (CH1) or receive data from the selected first UFS device (1301). While the storage controller (1210) communicates with the first UFS device (1301) through the first channel (CH1), it may not be able to communicate with the second UFS device (1302) through the first channel (CH1).

[0063] The storage controller (1210) can transmit and receive signals in parallel to each of the UFS devices (1300) through different channels. For example, while the storage controller (1210) transmits a command to the first UFS device (1301) through the first channel (CH1), it can transmit a command to the third UFS device (1303) through the second channel (CH2). For example, while the storage controller (1210) receives data to the first UFS device (1301) through the first channel (CH1), it can receive data to the third UFS device (1302) through the second channel (CH2).

[0064] Unlike FIGS. 3a and 3b, the storage device (1200b) of FIG. 4 shares a channel, so signals cannot be transmitted and received in parallel for UFS devices that share a channel. For example, while the storage controller (1210) transmits a command to the first UFS device (1301) through the first channel (CH1), it can transmit a command to the second UFS device (1302) through the first channel (CH1). For example, while the storage controller (1210) receives data from the first UFS device (1301) through the first channel (CH1), it cannot receive data from the second UFS device (1302) through the first channel (CH1).

[0065] FIGS. 5A and 5B are diagrams illustrating a method for distinguishing UFS devices sharing a channel with respect to the storage device of FIG. 4. Referring to FIGS. 2, FIG. 4, and FIG. 5A, the storage device (1200b) may include a storage controller (1210) and first to fourth UFS devices (1301 to 1304). The first and second UFS devices (1301, 1302) may communicate with the storage controller (1210) through a first channel (CH1), and the third and fourth UFS devices (1303, 1304) may communicate with the storage controller (1210) through a second channel (CH2). For convenience of explanation, a detailed description of the previously described components is omitted.

[0066] The storage controller (1210) may further transmit chip enable signals (nCE1 to nCE4) corresponding to each of the plurality of UFS devices (1301 to 1304). For example, the storage controller (1210) may transmit the first chip enable signal (nCE1) to the first UFS device (1301) via the first chip enable line. The storage controller (1210) may transmit the second chip enable signal (nCE2) to the second UFS device (1302) via the second chip enable line. The storage controller (1210) may transmit the third chip enable signal (nCE3) ​​to the third UFS device (1303) via the third chip enable line. The storage controller (1210) can transmit a fourth chip enable signal (nCE4) to the fourth UFS device (1304) through the fourth chip enable line.

[0067] In one embodiment, each of the plurality of UFS devices (1301 to 1304) can transmit and receive packets with the storage controller (1210) according to the chip enable signal. For example, when the chip enable signal is activated (e.g., low level), each of the plurality of UFS devices (1301 to 1304) can transmit and receive packets with the storage controller (1210).

[0068] In other words, the storage controller (1210) can select one of the UFS devices sharing a channel via a chip enable signal. For example, the storage controller (1210) can select the first UFS device (1301) among the first and second UFS devices (1301, 1302) sharing the first channel (CH1). The storage controller (1210) can enable the first chip enable signal (e.g., set to a low level), disable the second chip enable signal (e.g., set to a high level), and transmit commands to or from the first UFS device (1301) or transmit and receive data through the first channel (CH1).

[0069] Referring to FIG. 5b, a method of selecting one of the UFS devices sharing a channel via a chip select command instead of a chip enable signal is described. In one embodiment, during the initialization process, the storage controller (1210) may set a chip identifier (ID; identification) for each of the plurality of UFS devices (1300). For example, the storage controller (1210) may set the chip identifier of the first UFS device (1301) to '00', the chip identifier of the second UFS device (1302) to '01', the chip identifier of the third UFS device (1303) to '10', and the chip identifier of the fourth UFS device (1304) to '11'. Each of the plurality of UFS devices (1300) may store the set chip identifier in memory. For example, the first UFS device (1301) may store '00' as its chip identifier. However, the scope of the present disclosure is not limited thereto, and the values ​​of the chip identifiers of each of the plurality of UFS devices (1301 to 1304) may be changed.

[0070] In one embodiment, the host (1100) can transmit a write request and data to the storage device (1200). The storage device (1200) can receive the write request and data. The storage device (1200) can determine a space to store the data in response to the write request. For example, the storage device (1200) can select any one of a plurality of UFS devices (1300) to store the received data. Hereinafter, it is assumed that the storage controller (1210) stores the data in the first UFS device (1301) among the plurality of UFS devices (1300).

[0071] In step S110, the storage controller (1210) may transmit a CMD UPIU containing a Chip Select Command to the first UFS device (1301). In one embodiment, the Chip Select Command may include a chip identifier to be selected. For example, the storage controller (1210) may select the first UFS device (1301) to transmit a write command and data to the first UFS device (1301). The storage controller (1210) may transmit a Chip Select Command containing an operation code field of the Chip Select Command and a chip identifier (e.g., '00') to the first UFS device (1301) via the first channel (CH1).

[0072] In one embodiment, each of the plurality of UFS devices (1300) sharing a channel can determine whether the command and data received through the channel belong to it by comparing the assigned (or stored) chip identifier with the chip identifier included in the chip selection command. For example, if the chip identifier included in the chip selection command is '00', the first UFS device (1301) can compare the assigned chip identifier with the chip identifier included in the chip selection command. Since the assigned chip identifier and the chip identifier included in the chip selection command are the same, the first UFS device (1301) can determine whether the command and data transmitted through the first channel (CH1) belong to it. On the other hand, the second UFS device (1302) can determine whether the command and data transmitted through the first channel (CH1) do not belong to it because the assigned chip identifier (e.g., '01') and the chip identifier included in the chip selection command (e.g., '00') are different.

[0073] In step S120, the storage controller (1210) can transmit a CMD UPIU containing a write command (WR CMD) to the first UFS device (1301).

[0074] In step S130, the storage controller (1210) and the first UFS device (1301) can perform a data transaction. For example, the first UFS device (1301) can send an RTT UPIU (Ready to Transfer UPIU) (or Transfer Ready UPIU) to the storage controller (1210). The RTT UPIU may contain information about the range of data that the first UFS device (1301) can receive. In response to the RTT UPIU, the storage controller (1210) can send a DATA OUT UPIU (or Data Out UPIU) containing write data to the first UFS device (1301). By repeating the above-described operation, write data can be transferred from the storage controller (1210) to the first UFS device (1301).

[0075] After all write data has been received, in step S140, the first UFS device (1301) may send a RESPONSE UPIU (or response UPIU) to the storage controller (1210). The RESPONSE UPIU may include information indicating that the operation for the write command received in step S120 has been completed.

[0076] As described above, the storage controller (1210) may select one of a plurality of UFS devices sharing a channel via a chip select command instead of using a chip enable signal (nCE). After selecting the UFS device to communicate with via the chip select command, the storage controller (1210) may transmit a write command and data.

[0077] Although the above-described embodiment is described based on a write operation, the scope of the present disclosure is not limited thereto. For example, during a read operation, similar to a write operation, the storage controller (1210) may transmit a command UPIU including a chip select command and a chip identifier to the UFS device. After transmitting the chip select command, the storage controller (1210) may transmit a read command to the UFS device and receive data from the UFS device.

[0078] FIG. 6 is a block diagram showing the storage device of FIG. 1 in more detail. Referring to FIG. 1 and FIG. 6, the storage device (1200c) may include a storage controller (1210), a plurality of non-volatile memory devices (1220), and a plurality of UFS devices (1300). For the sake of brevity of the drawings and convenience of explanation, detailed descriptions or reference numbers for components identical or similar to those described in FIG. 1 are omitted.

[0079] In one embodiment, the storage device (1200c) may further include built-in (or embedded) non-volatile memory devices (1220) in addition to a plurality of removable UFS devices (1300) as in FIG. 1. When each of the plurality of non-volatile memory devices (1220) of the storage device (1200c) includes a flash memory, the flash memory may include a 2D NAND memory array or a 3D (or vertical) NAND (VNAND) memory array. As another example, the storage device (1200c) may include various other types of non-volatile memory. For example, the storage device (1200c) may be equipped with Magnetic RAM (MRAM), Spin-Transfer Torque MRAM, Conductive Bridging RAM (CBRAM), Ferroelectric RAM (FeRAM), Phase RAM (PRAM), Resistive RAM, and various other types of memory.

[0080] In one embodiment, the storage controller (1210) may further include a non-volatile memory interface circuit (1212). The non-volatile memory interface circuit (1212) may transmit data to be written to a plurality of non-volatile memories (1220) to the plurality of non-volatile memories (1220), or receive data read from the plurality of non-volatile memories (1220). This non-volatile memory interface circuit (1212) may be implemented to comply with standard protocols such as Toggle or Open NAND Flash Interface (ONFI).

[0081] As described above, a plurality of built-in non-volatile memory devices (1220) can communicate with a storage controller (1210) through a non-volatile memory interface circuit (1212), and a plurality of removable UFS devices (1300) can communicate with a storage controller (1210) through a UFS interface circuit (1400).

[0082] FIG. 7a is a drawing for explaining the form factor of a UFS card. When each of the plurality of UFS devices (1300) of FIG. 1 is implemented in the form of a UFS card (2000), the external appearance of the UFS card (2000) may follow that shown in FIG. 7a.

[0083] Referring to FIG. 7a, a bottom view of a UFS card (2000) is shown as an example. Referring to FIG. 7a, a plurality of pins for electrical contact with a UFS slot may be formed on the bottom of the UFS card (2000), and the function of each pin will be described later.

[0084] A plurality of pins may be formed on the bottom surface of the UFS card (2000) for electrical connection with the storage controller (1210), and according to FIG. 7a, the total number of pins may be 12. Each pin may have a rectangular shape, and the signal name corresponding to the pin is as shown in FIG. 7a. For general information regarding each pin, refer to Table 1 below.

[0085] number Shin Ho-myeong explanation 1 Vss Ground (GND) 2 DIN_C Differential input signal input from the host to the UFS card (4000) (DIN_C is the negative node, DIN_T is the positive node) 3 DIN_T 4 Vss Same as number 1 5 DOUT_C Differential output signal output from UFS card (4000) to host (DOUT_C ​​is negative node, DOUT_T is positive node) 6 DOUT_T 7 Vss Same as number 1 8 REF_CLK Reference clock provided from the host to the UFS card (4000) 9 VCCQ2 A power supply voltage having a relatively lower value compared to Vcc, primarily provided for PHY interfaces or controllers 10 C / D(GND) Card Detection Signal 11 Vss Same as number 1 12 Vcc Main power supply voltage

[0086] FIGS. 7b and 7c are drawings illustrating examples of a storage device according to the present disclosure. For the sake of brevity of the drawings, only a portion of the configuration of the storage device is shown. However, the scope of the present disclosure is not limited thereto, and the storage device (1200d) may further include other components (e.g., buffer memory, additional non-volatile memory device, auxiliary power supply, etc.). Referring to FIGS. 1, 7b and 7c, the storage device (1200d) may include a printed circuit board (PCB1), a storage controller (1210), and a first UFS device (1301). The printed circuit board (PCB1) may include a connector (CN), a controller socket (not shown), and a first slot (SL1). Since the storage controller (1210) and the first UFS device (1301) have been described previously, a detailed description thereof is omitted.

[0087] In one embodiment, the controller socket may be an area, configuration, or device in which the storage controller (1210) is mounted. The first slot (SL1) may be an area, configuration, or device in which the first UFS device (1301) is mounted. The storage controller (1210) and the first UFS device (1301) may be connected to each other by wiring patterns (not shown) provided on a printed circuit board (PCB1).

[0088] A printed circuit board (PCB1) may include a connector (CN) comprising a plurality of pins that are coupled to an external host (1100). The number and arrangement of the plurality of pins in the connector (CN) may vary depending on the communication interface between the storage device (1200) and the external host (1100). For example, the storage device (1200) may communicate with the external host according to any one of the interfaces such as USB (Universal Serial Bus), PCI-Express (Peripheral Component Interconnect Express), SATA (Serial Advanced Technology Attachment), SCSI (Small Computer System Interface), and M-Phy for UFS (Universal Flash Storage). In particular, the SATA standard encompasses all SATA family standards, such as SATA-2, SATA-3, and e-SATA (external SATA), as well as SATA-1. The PCIe standard encompasses all PCIe family standards, such as PCIe 2.0, PCIe 2.1, PCIe 3.0, and PCIe 4.0, as well as PCIe 1.0. The SCSI standard encompasses all SCSI family standards, such as parallel SCSI, serial combined SA-SCSI (SAS), and iSCSI. In some embodiments, the connector (CN) may be a connector configured to support an M.2 interface, an mSATA interface, or a 2.5″ interface.

[0089] For example, the storage device (1200) may be operated by power supplied from an external host (1100) through a connector (CN). The storage device (1200) may further include a Power Management Integrated Circuit (PMIC) that distributes power supplied from the external host (1100) to a storage controller (1200) and a first UFS device (1301).

[0090] The storage controller (1210) may not be removable once mounted or installed in the controller socket. On the other hand, the first UFS device (1301) may be removablely placed in the first slot (SL1).

[0091] For example, the first UFS device (1301) may be mounted in the first slot (SL1) in the first direction (D1). Alternatively, the first UFS device (1301) may be detached from the first slot (SL1) in the opposite direction of the first direction (D1). In one embodiment, the first UFS device (1301) may be physically and electrically connected to the first UFS device (1301) solely by the operation of inserting the first UFS device (1301) into the first slot (SL1).

[0092] As illustrated in FIG. 7a, the UFS card (2000) may include a plurality of pins capable of inputting and outputting power, signals, and / or data. The first slot (SL1) may include slot pins (or slot terminals) electrically connected to the plurality of pins of the UFS card (2000). The storage controller (1210) may control data exchange with the first UFS device (1301) through the first slot (SL1).

[0093] In one embodiment, the first slot (SL1) may be provided to allow the insertion of the first UFS device (1301) and to make contact with the first UFS device (1301). The first slot (SL1) may be configured to be electrically connected to the first UFS device (1301). The first UFS device (1301) may be operated by being inserted into the first slot (SL1) and making contact with the slot pins.

[0094] FIG. 8 is a drawing showing an example of a storage device according to the present disclosure. Referring to FIG. 8, the storage device (1200a) may include a storage controller (1210), a printed circuit board (PCB2), and first to fourth UFS devices (1301 to 1304). The printed circuit board (PCB2) may include a connector (CN), a controller socket (not shown), and first to fourth slots (SL1 to SL4). For convenience of explanation, a detailed description of the components described above is omitted.

[0095] The storage device (1200d) of FIG. 7 includes one slot (SL1), whereas the storage device (1200a) of FIG. 8 may include four slots (SL1 to SL4). Accordingly, the storage device (1200a) can insert first to fourth UFS devices (1301 to 1304).

[0096] In one embodiment, the storage device (1200a) includes first to fourth slots (SL1 to SL4), but only the first UFS device (1301) may be inserted. In this case, the storage device (1200a) may store data received from the host (1100) only in the first UFS device (1301). The size of the storage space of the storage device (1200a) may be the same as the size of the storage space of the first UFS device (1301).

[0097] Subsequently, a second UFS device (1302) may be additionally inserted into the second slot (SL2). The storage device (1200a) may store data received from the host (1100) in the first or second UFS devices (1301, 1302). The size of the storage space of the storage device (1200a) may be equal to the sum of the size of the storage space of the first UFS device (1301) and the size of the storage space of the second UFS device (1302).

[0098] In other words, by additionally inserting UFS devices into the storage device (1200a), the storage space of the storage device (1200a) can be increased. That is, the storage space of the storage device (1200a) is not predetermined but can be variable. The storage space of the storage device (1200a) can be determined according to the number of inserted UFS devices, the size of the storage space of each inserted UFS device, etc.

[0099] FIG. 9 is a drawing showing an example of a storage device according to the present disclosure. Referring to FIG. 9, the storage device (1200c) may include a storage controller (1210), a printed circuit board (PCB3), a plurality of UFS devices (1301 to 1304), and a plurality of non-volatile memory devices (1221 to 1224). For convenience of explanation, a detailed description of the components described above is omitted.

[0100] A printed circuit board (PCB3) may include a connector (CN), a controller socket (not shown), first to fourth slots (SL1 to SL4), and first to fourth memory sockets (not shown). A memory socket may be an area, configuration, or device in which a non-volatile memory device is mounted. For example, a first memory socket may be an area, configuration, or device in which a first non-volatile memory device (1221) is mounted, a second memory socket may be an area, configuration, or device in which a second non-volatile memory device (1222) is mounted, a third memory socket may be an area, configuration, or device in which a third non-volatile memory device (1223) is mounted, and a fourth memory socket may be an area, configuration, or device in which a fourth non-volatile memory device (1224) is mounted.

[0101] The first to fourth non-volatile memory devices (1221 to 1224) may be non-removable, unlike the first to fourth UFS devices (1301 to 1304). That is, the first to fourth non-volatile memory devices (1221 to 1224) may not be removable after being mounted or installed in a corresponding memory socket during manufacturing (or mass production).

[0102] Accordingly, the size of the minimum storage space of the storage device (1200c) can be determined according to the first to fourth non-volatile memory devices (1221 to 1224). For example, if all of the first to fourth UFS devices (1301 to 1304) are not inserted, the storage device (1200c) can store data received from the host (1100) only in the first to fourth non-volatile memory devices (1221 to 1224). The size of the storage space of the storage device (1200c) can be determined according to the storage space of the first to fourth non-volatile memory devices (1221 to 1224).

[0103] Subsequently, the first UFS device (1301) may be inserted into the storage device (1200c). The storage device (1200c) may store data received from the host (1100) in the first UFS device (1301) as well as in the first to fourth non-volatile memory devices (1221 to 1224). As the first UFS device (1301) is inserted, the storage space of the storage device (1200c) may be increased.

[0104] FIG. 10 is a flowchart showing an example of the operation of the storage controller of FIG. 1. With reference to FIG. 10, the operation of the storage controller is described when a UFS device is newly installed in a plurality of slots (SL1 to SL4). Hereinafter, it is assumed that a first UFS device (1301) is newly installed.

[0105] Referring to FIG. 1, FIG. 7a, and FIG. 10, in step S210, the storage controller (1210) can receive a detection signal. For example, the storage controller (1210) can recognize whether a new UFS device is installed through a detection signal input via a GPIO (general purpose input / output) pin. The detection signal may be a signal indicating whether the new UFS device is installed in a corresponding slot and indicating the slot among the plurality of slots (SL1 to SL4) in which the new UFS device is installed.

[0106] In one embodiment, the storage controller (1210) may be connected to a plurality of slots through first to fourth GPIO pins. For example, the first GPIO pin may be connected to the first slot (SL1), the second GPIO pin may be connected to the second slot (SL2), the third GPIO pin may be connected to the third slot (SL3), and the fourth GPIO pin may be connected to the fourth slot (SL4). When the first UFS device (1301) is inserted into the first slot (SL1), a detection signal input through the first GPIO pin will be activated. The remaining slots (SL2 to SL4) are similar, so a detailed description is omitted.

[0107] In one embodiment, a plurality of slots (SL1 to SL4) can determine that a new UFS device has been installed in a slot through the card detection pin (C / D) of Table 1. For example, when a first UFS device (1301) is inserted into a first slot (SL1), the first slot (SL1) can recognize that the first UFS device (1301) has been inserted through the card detection pin (C / D). The first slot (SL1) can output a detection signal to a storage controller (1210) through a first GPIO pin.

[0108] In step S220, the storage controller (1210) can perform an initialization operation with the new UFS device. For example, if the storage controller (1210) receives a detection signal through the first GPIO pin, it can recognize that the first UFS device (1301) is mounted in the first slot (SL1). In response to the detection signal, the storage controller (1210) can perform an initialization operation to control the first UFS device (1301).

[0109] In one embodiment, the storage controller (1210) may set a chip identifier for the new UFS device during an initialization operation. For example, the storage controller (1210) may assign a unique chip identifier to the new UFS device. The storage controller (1210) may transmit the assigned chip identifier to the new UFS device. The new UFS device may receive the assigned chip identifier from the storage controller (1210). The new UFS device may store the assigned chip identifier in memory.

[0110] In step S230, after the storage controller (1210) completes the initialization operation, it may store status information in memory. The status information may refer to information about a plurality of UFS devices (1300) or current status information that can be used for failure analysis. For example, the status information may include information regarding the status of the UFS devices and information regarding the size of the storage space.

[0111] For example, information regarding the status of UFS devices may include the number of UFS devices installed in multiple slots, identifiers of the slots into which UFS devices are inserted, and information about newly inserted UFS devices. Information regarding the size of the storage space may include the size of the storage space of newly inserted UFS devices, the size of the storage space of each UFS device, and the size of the total storage space of the storage device (1200).

[0112] The storage controller (1210) may store the status information in a buffer memory (1216) or in a UFS device that is already in use. Alternatively, the storage controller (1210) may store the status information in at least one of various memory devices such as ROM (Read Only Memory), PROM (Programmable ROM), EPROM (Electrically Programmable ROM), EFuse, EEPROM (Electrically Erasable and Programmable ROM), MASKROM, Serial PROM, Flash Memory, OTP (One Time Programming) Memory, Serial Flash, etc.

[0113] In step S240, the storage controller (1210) can perform a notification operation to the host (1100). The storage controller (1210) can transmit status information to the host (1100) regarding whether a new UFS device has been installed (or whether the size of the storage space has changed). For example, the storage controller (1210) can notify that a new UFS device has been inserted through the completion of an asynchronous event request. Alternatively, the storage controller (1210) can notify that the size of the storage space of the storage device (1200) has changed through the completion of an asynchronous event request. The storage controller (1210) can transmit status information to the host (1100) through the completion of obtaining a log page.

[0114] FIG. 11 is a flowchart showing step S240 of FIG. 10 in more detail. Referring to FIG. 1, FIG. 2, and FIG. 11, in step S205, the host (1100) can send an Asynchronous Event Request command to the storage device (1200). The Asynchronous Event Request command may be a command without a timeout. When the storage device (1200) receives the Asynchronous Event Request command, it may not send a Completion immediately, but may send a Completion when an event occurs.

[0115] In one embodiment, step S205 may be performed prior to step S210. Since the asynchronous event request command is a command without a timeout, the storage device (1200) may receive the asynchronous event request command before the new UFS device is mounted.

[0116] When a new UFS device is installed (i.e., when an event occurs), the storage controller (1210) can perform an initialization operation on the new UFS device to prepare the new UFS device for use. The storage controller (1210) can store state information in memory.

[0117] In step S241, the storage device (1200) can update status information in the log. That is, the storage device (1200) can update status information in the log, including information about UFS devices and information about the size of the storage space. Referring to FIG. 1, the log can be stored in the buffer memory (1216) of the storage controller (1210) and / or in the already mounted UFS devices.

[0118] In step S242, the storage device (1200) may send an asynchronous event request completion to the host (1100) to notify that an event has occurred. For example, the event may indicate that a new UFS device has been installed or that the size of the storage space has changed.

[0119] In one embodiment, the asynchronous event request completion may include a log identifier and event type information. The storage device (1200) may enable the host (1100) to read out the updated log through the asynchronous event request completion. For example, the log identifier and event type information may be newly defined in relation to the detachment of the UFS device (or a change in the size of the storage space).

[0120] In one embodiment, the storage device (1200) may transmit an asynchronous event request completion containing status information to the host (1100). In this case, the process of obtaining a log page described below may not be performed.

[0121] In step S243, the host (1100) may send a Get Log Page Command to the storage device (1200). The Get Log Page Command may include a log identifier, a log data size, and a host memory address where the log data read from the storage device (1200) will be stored.

[0122] In step S244, the storage device (1200) can transmit log page retrieval completion. Log page retrieval completion can be transmitted after log data is written to the host memory address included in the log page retrieval command.

[0123] The storage device (1200) can notify the host (1100) that a new UFS device has been installed or that the size of the storage space has changed. That is, the storage device (1200) can notify the host (1100) of the status of the UFS devices and the changed size of the storage space. Accordingly, the host (1100) can recognize the change in the storage space of the storage device (1200) and receive status information of the storage device (1200).

[0124] As described above, the storage device (1200) according to an embodiment of the present disclosure may include a plurality of removable UFS devices. That is, a UFS card can be mounted in a new form factor of an SSD. Accordingly, the applications of the UFS card can be expanded.

[0125] The above descriptions are specific embodiments for carrying out the present disclosure. The present disclosure will include not only the embodiments described above, but also embodiments that are simply modified or can be easily modified. Furthermore, the present disclosure will include technologies that can be easily modified and implemented using the embodiments. Accordingly, the scope of the present disclosure should not be limited to the embodiments described above, but should be defined by the claims set forth below as well as equivalents to the claims of this invention. Explanation of the symbols

[0126] 1000: Host-Storage System 1100: Host 1200: Storage device 1300: Multiple UFS devices

Claims

Claim 1 A printed circuit board comprising a connector having a plurality of pins coupled to an external host device, a controller socket, and first to fourth slots; first to fourth UFS devices detachably mounted in each of the first to fourth slots; and a storage controller mounted in the controller socket and configured to control the first to fourth UFS devices, wherein the first and second UFS devices communicate with the storage controller through a first channel, and the third and fourth UFS devices communicate with the storage controller through a second channel, and the first UFS device is directly connected to the first channel, the second UFS device is directly connected to the first channel, the third UFS device is directly connected to the second channel, and the fourth UFS device is directly connected to the second channel. Claim 2 A storage device according to claim 1, wherein the storage controller is configured to select the first UFS device through a first chip enable signal, select the second UFS device through a second chip enable signal, select the third UFS device through a third chip enable signal, and select the fourth UFS device through a fourth chip enable signal. Claim 3 In claim 2, the first to fourth UFS devices are storage devices configured to receive commands or data from the storage controller or transmit data to the storage controller through a connected channel when a corresponding chip enable signal is activated. Claim 4 A storage device according to claim 1, wherein the storage controller receives a write command from the external host device, receives data corresponding to the write command from the external host device in response to the received write command, selects one of the first to fourth UFS devices to store the data, and transmits a chip select command, a write command, and the data to the selected UFS device. Claim 5 In claim 4, the chip selection command is a storage device comprising information regarding the chip identifier of the selected UFS device. Claim 6 In claim 4, the storage controller is configured to set a chip identifier for each of the first to fourth UFS devices in an initialization operation for the first to fourth UFS devices, and each of the first to fourth UFS devices is configured to store the set chip identifier. Claim 7 In claim 6, the storage device configured such that the first to fourth UFS devices compare a stored chip identifier with a chip identifier included in the chip selection command to determine whether a command or data received through a channel is their own. Claim 8 A method of operation of a storage device comprising a plurality of removable UFS devices and a storage controller, wherein when a new UFS device among the plurality of UFS devices is inserted, the storage controller receives a detection signal; the storage controller performs an initialization operation with the new UFS device in response to the detection signal; the storage controller stores state information in memory after performing the initialization operation; and the storage controller transmits the state information to an external host, wherein the state information includes information regarding the plurality of UFS devices and information regarding the size of the storage space. Claim 9 In claim 8, the step of transmitting the status information to an external host comprises: transmitting an asynchronous event request completion to the external host; receiving a log page get command to the external host; and transmitting log data including the status information and log page get completion to the external host. Claim 10 In claim 8, the storage device further comprises a printed circuit board including a controller socket on which the storage controller is mounted and a plurality of slots on which the plurality of UFS devices are mounted, and the step of receiving the detection signal comprises: determining that the new UFS device has been inserted through a card detection pin of a slot into which the new UFS device has been inserted; if it is determined that the new UFS device has been inserted, outputting the detection signal through a GPIO pin (general purpose input / output) connected to the slot into which the new UFS device has been inserted; and receiving the detection signal through the GPIO pin by the storage controller.

Citation Information

Patent Citations

  • Memory device and memory system including the same

    KR1020170033124A

  • Method for device requesting in storage device and command issueing method of host

    KR1020170051688A

  • Operating Method of semiconductor device and memory system having multi-connection port and Communication Method of storage system

    KR1020170084537A

  • Apparatus and method for performing data transmission with docking device by using USB interface

    KR1020190069880A

  • Capacitive multidrop bus compensation

    US6745268B1