Patent Application
20230345715
Three-dimensional (3D) NAND (not AND) technologies are commonly used to create nonvolatile (NV) storage devices, such as solid-state drives (SSDs). Reference to 3D NAND can more specifically refer to NAND flash. Unlike convention 2D memory devices, 3D NAND memory devices have one or more decks comprising tiers of circuit elements that are stacked on top of one another. The circuit elements are connected via channels in vertical structures (pillars) having high depth-to-width aspect ratios (AR).
Fabricating 3D memory devices having high AR pillars poses significant challenges. For example, tier expansion (i.e., increasing the height of tiers in a deck) results in higher pillar bending for the boundary pillars and causes yield lost due to upper deck to lower deck pillar misalignment, under punch, punch damage and bitline-to-bitline short.
The foregoing aspects and many of the attendant advantages of this invention will become more readily appreciated as the same becomes better understood by reference to the following detailed description, when taken in conjunction with the accompanying drawings, wherein like reference numerals refer to like parts throughout the various views unless otherwise specified:
Embodiments of methods and apparatus for pillar bending improvement by cut tiers pattern implementation are described herein. In the following description, numerous specific details are set forth to provide a thorough understanding of embodiments of the invention. One skilled in the relevant art will recognize, however, that the invention can be practiced without one or more of the specific details, or with other methods, components, materials, etc. In other instances, well-known structures, materials, or operations are not shown or described in detail to avoid obscuring aspects of the invention.
Reference throughout this specification to “one embodiment” or “an embodiment” means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the present invention. Thus, the appearances of the phrases “in one embodiment” or “in an embodiment” in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.
For clarity, individual components in the Figures herein may also be referred to by their labels in the Figures, rather than by a particular reference number. Additionally, reference numbers referring to a particular type of component (as opposed to a particular component) may be shown with a reference number followed by “(typ)” meaning “typical.” It will be understood that the configuration of these components will be typical of similar components that may exist but are not shown in the drawing Figures for simplicity and clarity or otherwise similar components that are not labeled with separate reference numbers. Conversely, “(typ)” is not to be construed as meaning the component, element, etc. is typically used for its disclosed function, implement, purpose, etc.
Host 110 provides a hardware platform to operate NV device 120. Host 110 includes one or more processors 114 to perform the operations of host 110. Processor 114 executes a host operating system (OS) that provides a software platform for the operation of NV device 120. The hardware platform provides hardware resources to interface with NV device 120 including transceiver hardware to perform access to the device. The software platform includes control software to execute other software elements such as applications or other agents that execute under the OS and create requests to access NV device 120.
I/O 112 and I/O 122 interconnect through one or more signal lines 150. Signal lines 150 typically include multiple separate lines and can be considered one or more buses to connect host 110 to NV device 120. Host 110 can send a host read command over signal line 150 to NV device 120. In response to the read command, NV device 120 services the request out of a transient Vt state, in accordance with any example provided.
In one example, host 110 includes controller 116. Controller 116 represents a memory controller or storage controller. In one example, controller 116 is integrated with processor 114. In one example, controller 116 is separate from processor 114. Controller 116 enables host 110 to manage access to NV device 120. In response to host operations by processor 114 that request access to data on NV device 120, controller 116 provides access to NV device 120. Controller 116 can represent hardware and firmware elements of host 110 to enable interaction with NV device 120.
NV device 120 includes controller 124, which represents a storage controller at the side of the storage device, which is separate from controller 116 of host 110. Controller 116 of host 110 represents components of the host system. Controller 124 represents components of the storage device or memory device into which the NV media is incorporated. Controller 124 receives commands sent from host 110 and determines how to service the command or request from the host. Controller 124 performs operations to access (e.g., read or write) NV media 130 in response to the host command.
NV media 130 represents a nonvolatile storage media of NV device 120. In one example, NV media 130 includes three-dimensional (3D) NAND (not AND) memory cells. In one example, NV media 130 includes 3D NOR memory cells. In one example, NV media 130 includes 3D crosspoint (XPOINT™) memory cells.
NV media 130 includes bitcells or memory cells organized as blocks 132. A block of memory refers to a portion of NV media 130 that is jointly charged or activated for an access operation. In one example, blocks 132 are subdivided as subblocks. In one example, a block refers to bitcells that share a select gate line. In one example, multiple subblocks share a select gate (e.g., a common select gate source (SGS) or a common select gate drain (SGD)) connector.
In one example, a block refers to an erase unit, or a unit size of NV media 130 that is erased together and monitored by controller 124 for number of writes. In one example, NV media 130 includes single level cell (SLC) and multilevel cell (MLC) media. For example, NV media 130 can include SLC and QLC (quad level cell) or SLC and TLC (triple level cell) bitcells. The block size could be different depending on the media type.
In one example, controller 124 is an ASIC (application specific integrated circuit) that controls operation of NV device 120. In one example, controller 124 is a CPU (central processing unit) core or processor device on NV device 120. In one example, NV device 120 represents an SSD and controller 124 controls multiple NV media dies or NV media chips integrated into the SSD. In one example, NV device 120 represents a module or PCB (printed circuit board) that includes multiple NV media dies or NV media chips integrated onto it and controller 124 controls the NV media dies of the module. In one example, controller 124 executes firmware to manage NV device 120. In one example, controller 124 executes firmware to manage NV device 120, including firmware to control the servicing of a read command based on whether the NV media is in thermal equilibrium.
In one example, controller 124 manages Vt state detection and read command servicing based on idle time or delay between consecutive read commands. In one example, controller 124 monitors one or more media states 126. Media state 126 represents a state of a portion of memory (such as a block) and can determine how to access the media based on media state 126. For example, if media state 126 indicates that a target block is in a stable state, controller 124 can first issue a dummy read prior to accessing the target block. In one example NV media devices 120 may include one or more timers 142 and counters 144.
During execution of operations by processor 212, an agent executed by the processor can request data and/or code that is not stored at host 210 (e.g., in a cache or main memory), and therefore should be obtained from memory 220. Storage controller 214 generates and processes memory access commands to memory 220 to perform the memory access. Storage controller 214 represents a circuit or logic or processor that manages access to memory 220. In one example, storage controller 214 is part of host 210. In one example, storage controller 214 is part of processor 212. In one example, storage controller 214 is integrated on a common substrate with processor 212. In one example, storage controller 214 separate chip from processor 212, and can be integrated in a multichip package (MCP) with processor 212.
Memory 220 includes controller 240, which represents a controller at the memory or storage device to process and service commands from storage controller 214. In one example, controller 240 represents a controller for a memory device. In one example, controller 240 represents a controller for a memory module. Memory 220 includes 3D array 222. In one example, 3D array 222 includes NAND memory blocks. In one example, 3D array 222 includes QLC NAND memory blocks.
As illustrated, bitlines (BL) intersect the planes of the tiers of wordlines (WL). As an example, each wordline WL[0:(N−1)] is a tier. There can be P bitlines (BL[0:(P−1)]). In one example, 3D array 222 is also divided into subblocks through SGD[0:(M−1)], which divide each wordline into separate segments within a tier or within a plane of wordlines. Alternatively, SGS can be subdivided to provide subblocks. In such a configuration, whereas SGS is shown to apply to multiple SGD lines, there could be multiple SGS lines to a single SGD line. SRC represents a common source.
Channel 250 represents a vertical channel of the 3D array. The channel refers to a vertical stack of bitcells that can be charged through a channel connector. In one example, the channels couple to the bitline. It will be understood that there can be spatial dependencies in the stable Vt state of a channel. For example, the flow of charge carriers in the channel can be different at the different ends of the channels. Thus, blocks with specific wordlines may show worse degradation than others. The operation of controller 240 to mitigate read disturb due to stable Vt in the channel can be set by thresholds and operation that mitigates the most sensitive of the wordlines.
Each label, WL[0], WL[1], SGD[0], and so forth, indicates a select signal provided by control logic of decode logic 224, or a select signal provided by control logic of sense/output logic 226. In one example, decode logic 224 includes selection logic to select each of the signal lines illustrated. In one example, sense/output logic 226 enables the sensing of the contents of bitcells of 3D array 222, for either a read operation or to write a value back to the array. The output can be for a read operation to send data back to host 210. A write operation would include writing to a buffer to apply the values to the array.
It will be understood that a signal line in 3D array 222 is a wire or trace or other conductor that provides charge from a driver to the various elements or components. A driver circuit decode logic 224 provides the charge to charge up each signal line to the desired voltage for the desired operation. Each signal line can have an associated voltage level associated with certain operations. For example, each wordline can have a select voltage and a deselect voltage to indicate, respectively, wordlines that are selected for an operation and wordlines that are not selected for an operation.
In 3D array 222, it will be understood that the length of the wordlines can be substantial. In one example, the number of tiers of wordlines is on the order of tens or dozens of wordlines (e.g., N=28, 32, 36, 70, or more). In one example, the number of subblocks is on the order of ones or tens (e.g., M=8, 76, or more). Typically, the number of bitlines in 3D array 222 will be on the order of hundreds to thousands (e.g., P=2K). Thus, in one example, each bitline is relatively short compared to the length of the wordlines.
Each memory cell 320a-n in this example can have a charge-storage structure (e.g., that may be a conductive floating gate, a dielectric charge trap, etc.). For example, as shown in
Each memory cell 320 may be a non-volatile memory cell and may have a charge-storage structure 321, such as a floating gate that may be a semiconductor (e.g., polysilicon), a charge trap layer that may be a dielectric film, etc. Non-limiting examples of dielectrics that are suitable for charge traps include nitrides, high-dielectric constant (high-K) dielectrics, such as alumina (Al2O3) having a K of about 10, with embedded conductive particles (e.g., nano-dots), such as embedded metal particles or embedded nano-crystals (e.g., silicon, germanium, or metal crystals), a silicon rich dielectric, or SiON/Si3N4. Embodiments of floating-gate and charge trap cells are described and illustrated below.
With further reference to
In some embodiments, where the charge-storage structure 321 is a charge trap, the tunnel dielectric 322, the charge-storage structure 321, and the dielectric 323 can form a continuous structure that can be shared by (e.g., that may be common to) two or more of the memory cells 320a-n. For example, such a structure can be shared by or common to all of the memory cells 320a-n.
Each of the memory cells 320a-n can have a thickness (e.g., a channel length) 326. For example, the memory cells 320a-n can have the same channel length regardless of where in string 325 the memory cells are located. In some embodiments, at least one channel length of a memory cell can be different from another channel length of another memory cell.
Each memory cell 320a-n of the string 325 can be coupled in series with and can be between a select gate (e.g., a drain select gate) 311 adjacent to (e.g., in contact with) the pillar 310 and a select gate (e.g., a source select gate) 312 adjacent to (e.g., in contact with) the pillar 310. For a functional memory pillar, the pillar 310 is electrically coupled to a data line (e.g., a bit line 316), indicated at 317a and 317b. Thus, the select gate 311 can selectively couple the string 325 to the data line (e.g., the bit line 316). In addition, for a functional memory pillar, the pillar 310 is electrically coupled to a source line 318, indicated at 319a and 319b. Thus, the select gate 312 can selectively couple the string 325 to the source line 318. For example, the select gate 311 can be coupled in series with memory cell 320a, and the select gate 312 can be coupled in series with memory cell 320n. The select gates 311 and 312 can each include a gate dielectric 313 adjacent to (e.g., in contact with) pillar 310 and a control gate 314 adjacent to (e.g., in contact with) a corresponding gate dielectric 313.
In accordance with aspects of one embodiment, the cut tier design is added into the pillar reticle, with the cut tier feature will be formed by a pillar etch process and then filled with cell films. In order to ensure the electrical path between the staircase and pillar array, some breaks are purposely reserved on the cut tier feature, such as shown in plan (top) view of a semiconductor structure design 700 in
As before, semiconductor structure design 700 includes an array 702 of pillars 704 that are adjacent to a staircase region 706, further details of which are shown in
Diagrams 800a and 800b illustrate comparisons of silicon performance (i.e., performance using actual silicon 3D NAND devices) under the current approach and using the cut tiers approach are respectively shown in
As shown in diagram 800a, the pitch distance between the silicon performance circles 808 from the 1st pillar and the 2nd pillar is a distance A, while the pitch difference between the silicon performance circles 808 from the 2nd pillar and the 3rd pillar is distance B. The use of different distances A and B is to show that the amount of bending for adjacent pillars may vary a small amount. Also, while
Diagram 800b depicts a staircase region 802b with a CT 810 and a pillar array 804b. The spacing between the silicon performance circles 808 from the 1st pillar and the 2nd pillar is a distance C, while the spacing between the silicon performance circles 808 from the 2nd pillar and the 3rd pillar is distance D. As before, the use of different distances C and D is to show the amount of bending for adjacent pillars may vary a small amount. A comparison between diagrams 800a and 800b shows distances C and D are less than distances A and B, demonstrating reduced pillar bending when using the CT approach.
The pitch distances (A, B, C, D, . . . ) are measured using a Scanning Electron Microscope (SEM) tool. Under one embodiment, the cut tier pattern approach provides a pillar bending improvement of approximately 90 nm for the 1st tier pillars adjacent to the staircase region using a reticle pillar pitch of 164 nm.
Reference is now made to
As seen in
A subsequent stage, not separately shown, for the formation of interconnections between the word lines and the substrate 922 on the one hand, and bit lines on the other hand, is an etch process that etches the first etch stop layer and therefore has high selectivity to the first etch stop layer, so that it can stop at an underlying second etch stop layer 916, such as an second etch stop layer 916 including an oxide.
The staircase 925 may comprise a stepped structure, such as illustrated in
Next generation 3D NAND memory devices present more tiers (more stacks of word lines and interlayer dielectrics) and therefore more depth compared with those of their predecessors. In one embodiment an oxide-poly-oxide-poly (OPOP) staircase (corresponding alternating dielectric layers 905 and word lines 903) is employed. However, this is merely exemplary and non-limiting, as other materials and structures known in the art may be used.
In addition to the like-numbered structures and components shown in
Circuit 1100 depicts two memory cells, cell 1110 and cell 1120 and three isolation layers 1102, 1104, and 1106 (which may also be called separation layers). Although circuit 1100 is not necessarily to scale, the isolation layers between the cells are generally thinner than the cells themselves. The cells illustrate one example of a memory cell structure, with semiconductor indicated as storage node 1112 and storage node 1122, respectively. Storage node 1112 is separated from control gate poly by one or more IPD (inter-poly dielectric) layers 1114. The conductor layer poly is a layer of conductor to control access to the storage node. The conductor layer poly for storage node 1112 is represented as control gate 1116. Likewise, storage node 1122 is separated from conductor layer poly by one or more IPD layers 1124, represented as control gate 1126. The number of IPD layer and the structure of those layers is not important for circuit 1100, as long as the storage node is electrically isolated from the conductor layer.
In one example, circuit 1100 includes an oxide 1150, and a channel conductor 1130 with a dielectric fill 1132. 3D NAND typically uses polycrystalline (poly) material for channel 1130, such as but not limited to polycrystalline silicon (also referred to as polysilicon). In one example, channel 1130 may be p-type or n-type doped poly. In one example, channel 1130 is a lightly doped (1e17/cm3-5e17/cm3) polysilicon material such as n-type (electron carrier majority) or p-type (hole carrier majority) channel.
3D NAND block 902 may employ other memory cell structures, such as Charge-Trap Flash (CTF) cells. For example,
It is noted that the pillar bending in the Figures herein are exaggerated for illustrative purposes, and the pillars and the degree of pending are not to scale in some Figures. Also, the tops of pillars and the top of an adjacent staircase structure may differ from that shown in some Figures.
Although some embodiments have been described in reference to particular implementations, other implementations are possible according to some embodiments. Additionally, the arrangement and/or order of elements or other features illustrated in the drawings and/or described herein need not be arranged in the particular way illustrated and described. Many other arrangements are possible according to some embodiments.
In each system shown in a figure, the elements in some cases may each have a same reference number or a different reference number to suggest that the elements represented could be different and/or similar. However, an element may be flexible enough to have different implementations and work with some or all of the systems shown or described herein. The various elements shown in the figures may be the same or different. Which one is referred to as a first element and which is called a second element is arbitrary.
In the description and claims, the terms “coupled” and “connected,” along with their derivatives, may be used. It should be understood that these terms are not intended as synonyms for each other. Rather, in particular embodiments, “connected” may be used to indicate that two or more elements are in direct physical or electrical contact with each other. “Coupled” may mean that two or more elements are in direct physical or electrical contact. However, “coupled” may also mean that two or more elements are not in direct contact with each other, but yet still co-operate or interact with each other. Additionally, “communicatively coupled” means that two or more elements that may or may not be in direct contact with each other, are enabled to communicate with each other. For example, if component A is connected to component B, which in turn is connected to component C, component A may be communicatively coupled to component C using component B as an intermediary component.
An embodiment is an implementation or example of the inventions. Reference in the specification to “an embodiment,” “one embodiment,” “some embodiments,” or “other embodiments” means that a particular feature, structure, or characteristic described in connection with the embodiments is included in at least some embodiments, but not necessarily all embodiments, of the inventions. The various appearances “an embodiment,” “one embodiment,” or “some embodiments” are not necessarily all referring to the same embodiments.
Not all components, features, structures, characteristics, etc. described and illustrated herein need be included in a particular embodiment or embodiments. If the specification states a component, feature, structure, or characteristic “may”, “might”, “can” or “could” be included, for example, that particular component, feature, structure, or characteristic is not required to be included. If the specification or claim refers to “a” or “an” element, that does not mean there is only one of the element. If the specification or claims refer to “an additional” element, that does not preclude there being more than one of the additional element.
Italicized letters, such as ‘J’, ‘K’, ‘L’, ‘M’, etc. in the foregoing detailed description are used to depict an integer number, and the use of a particular letter is not limited to particular embodiments. Moreover, the same letter may be used in separate claims to represent separate integer numbers, or different letters may be used. In addition, use of a particular letter in the detailed description may or may not match the letter used in a claim that pertains to the same subject matter in the detailed description.
As used herein, a list of items joined by the term “at least one of” can mean any combination of the listed terms. For example, the phrase “at least one of A, B or C” can mean A; B; C; A and B; A and C; B and C; or A, B and C.
The above description of illustrated embodiments of the invention, including what is described in the Abstract, is not intended to be exhaustive or to limit the invention to the precise forms disclosed. While specific embodiments of, and examples for, the invention are described herein for illustrative purposes, various equivalent modifications are possible within the scope of the invention, as those skilled in the relevant art will recognize.
These modifications can be made to the invention in light of the above detailed description. The terms used in the following claims should not be construed to limit the invention to the specific embodiments disclosed in the specification and the drawings. Rather, the scope of the invention is to be determined entirely by the following claims, which are to be construed in accordance with established doctrines of claim interpretation.
| Number | Date | Country | Kind |
|---|---|---|---|
| PCTCN2023097720 | Jun 2023 | WO | international |
The present application claims the benefit of priority to Patent Cooperation Treaty (PCT) Application No. PCT/CN2023/097720 filed Jun. 1, 2023, the entire content of which is incorporated herein by reference.
