Preserving hierarchical structure information within design file

By applying compatibility rules to detect and authenticate design files, the method preserves hierarchical structure, reducing data volume and enhancing processing efficiency in digital lithography.

JP2024156693AInactive Publication Date: 2024-11-06APPLIED MATERIALS INC
View PDF 9 Cites 0 Cited by

Patent Information

Application Number
JP2024111414
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Filing Date
2024-07-11
Publication Date
2024-11-06
Estimated Expiration
Not applicable · inactive patent

AI Technical Summary

Technical Problem

Conventional lithography methods face challenges in transferring large data volumes for digital lithography processing, leading to reduced speed, and existing authentication methods lose hierarchical structure information in design files.

Method used

A method and device that apply compatibility rules to detect non-orthogonal edges, non-conforming overlapping structures, and incompatible interactions in design files, authenticating them by comparing these elements to thresholds, preserving hierarchical structure information.

Benefits of technology

Reduces data volume by up to 90% while maintaining hierarchical structure, minimizing data congestion and errors in digital lithography processes.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2024156693000001_ABST
    Figure 2024156693000001_ABST
Patent Text Reader

Abstract

To provide a method of verifying a design file for digital lithography that maintains the hierarchical structure information of design files while reducing data volume.SOLUTION: A verification device for verifying a design file for digital lithography comprises a memory and a controller. The memory comprises the design file. The controller is configured to access the design file and apply one or more compliance rules to the design file to determine compliance of the design file. The compliance rules comprise at least one of detecting non-orthogonal edges within the design file, detecting non-compliant overlapping structures within the design file, and detecting a non-compliant interaction between a reference layer of the design file and a target layer of the design file. The controller is further configured to verify the design file in response to a comparison of a number of non-orthogonal edges, non-compliant overlapping structures and non-compliant interactions to a threshold.SELECTED DRAWING: Figure 1
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001]

[0001] Embodiments of the present disclosure relate generally to authenticating design files for digital lithography systems. [Background technology]

[0002]

[0002] Lithography is used in the manufacture of semiconductor devices. Traditional lithography involves transferring a design pattern onto a set of photomasks and then onto photoresist. In digital lithography, the design pattern is digitized directly onto the photoresist using image processing. However, the large amount of data transferred to digitize the photoresist limits the speed of the digital lithography process. In addition, current verification methods remove structural information from the design file.

[0003] Therefore, there is a need in the art for a method to reduce the amount of data while still maintaining the hierarchical structure information of design files. Summary of the Invention

[0004] In an exemplary embodiment, a method includes accessing a design file for a digital lithography device and applying one or more compatibility rules to the design file to determine compatibility. Applying the one or more compatibility rules includes detecting non-orthogonal edges in the design file, detecting non-compatible overlapping structures in the design file, and detecting non-compatible interactions between a reference layer of the design file and a target layer of the design file. The method further includes authenticating the design file in response to comparing a number of the non-orthogonal edges, the non-compatible overlapping structures, and the non-compatible interactions to a threshold value.

[0005] In an exemplary embodiment, an authentication device for authenticating a design file for digital lithography comprises a memory and a controller. The memory includes a design file. The controller is configured to access the design file and apply one or more compatibility rules to the design file to determine compatibility of the design file. The compatibility rules include at least one of detecting non-orthogonal edges in the design file, detecting non-compatible overlapping structures in the design file, and detecting non-compatible interactions between a reference layer of the design file and a target layer of the design file. The controller is further configured to authenticate the design file in response to comparing the number of the non-orthogonal edges, the non-compatible overlapping structures, and the non-compatible interactions to a threshold value.

[0006] In an exemplary embodiment, a computer program product for validating a design file for digital lithography includes a computer readable storage medium having computer readable program code embodied thereon. The computer readable program code is executable by one or more processors to access the design file, apply one or more compatibility rules to the design file to determine compatibility of the design file, and validate the design file in response to comparing a number of non-orthogonal edges, non-compatible overlapping structures, and non-compatible interactions to a threshold. Applying the one or more compatibility rules to the design file includes at least one of detecting non-orthogonal edges in the design file, detecting non-compatible overlapping structures in the design file, and detecting non-compatible interactions between a reference layer of the design file and a target layer of the design file.

[0007]

[0007] So that the above-mentioned features of the present disclosure can be understood in detail, a more particular description of the present disclosure briefly summarized above can be had by reference to embodiments, some of which are illustrated in the accompanying drawings. It should be noted, however, that the accompanying drawings show only exemplary embodiments, and therefore should not be considered as limiting the scope of the present disclosure, which may admit of other equally effective embodiments. [Brief description of the drawings]

[0008] [Figure 1] FIG. 1 is a schematic diagram of a digital lithography system according to one or more embodiments. [Diagram 2] 1 is a schematic diagram of an authentication device according to one or more embodiments. [Diagram 3] FIG. 1 is a flow diagram of a method for authenticating a design file according to one or more embodiments. [Figure 4] FIG. 13 is a flow diagram for determining matching design files according to one or more embodiments. [Diagram 5] FIG. 1 is a schematic diagram of a cell structure according to one or more embodiments. [Figure 6] FIG. 1 is a schematic diagram of a cell structure according to one or more embodiments. [Figure 7] FIG. 1 is a schematic diagram of a cell structure according to one or more embodiments. [Figure 8] FIG. 1 is a schematic diagram of a cell structure according to one or more embodiments. [Figure 9] FIG. 1 is a schematic diagram of a cell structure according to one or more embodiments. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009]

[0013] For ease of understanding, the same reference numbers have been used, where possible, to designate identical elements common to the figures. It is intended that elements and features of one embodiment may be beneficially incorporated in other embodiments without further recitation.

[0010]

[0014] The embodiments described herein provide a method for certifying a design file optimized for transformation of a digital pattern while maintaining at least a portion of the hierarchical structure information in the original design file to reduce the total data volume and avoid data congestion. The method includes evaluating the design file against a set of conformance rules to detect non-conforming cells in the design file. A list of non-conforming cells and / or position markers may be presented to a user for corrective action. If the design file is determined to meet a threshold based on a ratio of non-conforming cells and / or position markers, the design file may be certified. The certified design file may be communicated to a controller of a digital lithography system for processing.

[0011]

[0015] FIG. 1 is a perspective view of a digital lithography system 100 according to one or more embodiments. The system 100 includes a digital lithography device 101 and an authentication device 130. The digital lithography device 101 includes a stage 114 and a processing device 104. The stage 114 is supported by a pair of tracks 116 disposed on a slab 102. A substrate 120 is supported by the stage 114. The stage 114 is supported by a pair of tracks 116 disposed on the slab 102. The stage 114 moves in an X-direction along the pair of tracks 116 as illustrated by the coordinate system shown in FIG. 1. In one embodiment, the pair of tracks 116 is a pair of parallel magnetic channels. As illustrated, each track of the pair of tracks 116 extends on a linear path. An encoder 118 is connected to the stage 114 to provide position information of the stage 114 to a controller 122.

[0012]

[0016] The controller 122 is generally designed to facilitate control and automation of the processing techniques described herein. The controller 122 may be coupled to or in communication with the processing device 104, the stage 114, and the encoder 118. The processing device 104 and the encoder 118 may provide information to the controller 122 regarding substrate processing and substrate alignment. For example, the processing device 104 may provide information to the controller 122 to alert the controller 122 that substrate processing is complete. The controller 122 facilitates control and automation of the digital lithography process based on a design file provided by the authentication device 130. A design file (or computer instructions), which may also be referred to as an imaging design file, readable by the controller 122 determines which tasks can be performed on the substrate. The design file (e.g., design file 220 of FIG. 2) includes code and mask pattern data for monitoring and controlling processing time and substrate position. The mask pattern data corresponds to a pattern to be written into the photoresist using electromagnetic radiation.

[0013]

[0017] The substrate 120 includes any suitable material used as part of a flat panel display, such as glass. In other embodiments, the substrate 120 is made of other materials that can be used as part of a flat panel display. The substrate 120 includes a thin film that is patterned, such as by etching a pattern, and a photoresist layer that is sensitive to electromagnetic radiation, such as UV (ultraviolet) or deep UV "light." A positive photoresist includes portions of the photoresist that dissolve in a photoresist developer when exposed to radiation. The photoresist developer is applied to the photoresist after a pattern is written into the photoresist using electromagnetic radiation. A negative photoresist includes portions of the photoresist that do not dissolve in a photoresist developer when exposed to radiation. The photoresist developer is applied to the photoresist after a pattern is written into the photoresist using electromagnetic radiation. The chemical composition of the photoresist determines whether the photoresist is a positive photoresist or a negative photoresist. Examples of photoresists include, but are not limited to, at least one of diazonaphthoquinone, phenol formaldehyde resin, poly(methyl methacrylate), poly(methyl glutarimide), and SU-8. After the photoresist is exposed to electromagnetic radiation, the resist is developed, leaving a patterned photoresist on the underlying film layer. The patterned photoresist is then used to pattern etch the underlying thin film through the openings in the photoresist to form a portion of the electronic circuitry of the display panel.

[0014]

[0018] The processing equipment 104 includes a support 108 and a processing unit 106. The processing equipment 104 straddles a pair of tracks 116 and is positioned above the slab 102, thereby including an opening 112 for the pair of tracks 116 and the stage 114 to pass underneath the processing unit 106. The processing unit 106 is supported above the slab 102 by the support 108. In one embodiment, the processing unit 106 is a pattern generator configured to expose a photoresist in a photolithography process. In some embodiments, the pattern generator is configured to perform a maskless lithography process. The processing unit 106 includes a multiple image projection system.

[0015]

[0019] In operation, the stage 114 moves in the X direction from a loading position shown in FIG. 1 to a processing position, which is one or more positions below the processing units 106. Here, the system 101 is shown in a schematic manner. The system 101 is dimensioned to be able to expose the entire width of the photoresist layer on the substrate 120 in the Y direction, i.e., the substrate 120 is small compared to that of an actual flat panel display substrate. However, in an actual processing system, the processing device 104 is much smaller in the Y direction than the width of the substrate 120 in the Y direction, and the substrate 120 is continuously moved in the −X direction under the processing device 104, moved or stepped in the +Y direction, and scanned back in the +X direction under the processing device 104. The above-mentioned scanning in the X direction and stepping in the Y direction is continued until the entire substrate has passed under the writable area of ​​the processing device 104.

[0016]

[0020] 2 illustrates an authentication device 130 according to one or more embodiments. The authentication device 130 includes a computing device 210 and an input / output (I / O) device 230. The authentication device 130 may be utilized to create, optimize, authenticate, and / or update design files (e.g., design file 220).

[0017]

[0021] Computing device 210 may include a controller 212, a network interface 214, and a memory 216. Controller 212 reads and executes programming data stored in memory 216 and coordinates the operation of other system components. Similarly, controller 212 stores and reads application data residing in memory 216. Controller 212 may be one or more central processing units (CPUs).

[0018]

[0022] The memory 216 may store instructions and logic executed by the controller 212. Furthermore, the memory 216 may be one or more of a random access memory (RAM) and a non-volatile memory (NVM). The NVM may be a hard disk, a network attached storage (NAS), a removable storage device, among others. Furthermore, the memory 216 may include a design application 218 and a design file 220.

[0019]

[0023] The design application 218 generates, optimizes, validates, and / or updates design data in the design file 220. The design application 218 can be controlled by the controller 212 to generate, optimize, and / or update design data in the design file 220.

[0020]

[0024] The design file 220 may be stored in memory and is accessible by the controller 212 and the design application 218. The design file 220 may include design data that may be interpreted by the controller 122 to pattern the substrate 120. For example, the design file 220 represents hierarchical physical design (layout) data. The hierarchical physical design data may consist of core pixels and peripheral logic regions. The core pixel regions may be highly repetitive and represent more than 90% of the design data. Furthermore, by maintaining the hierarchical structure, the amount of data transferred to the controller 122 is reduced. For example, the amount of data may be reduced by about 100 to about 1000 times compared to applying global biasing using a hierarchical geometry engine. Data inflation may result in data transmission failures in the data path. Furthermore, the design application 218 may optimize global sizing in cell level sizing and hierarchical repair. The design file 220 may also be referred to as a design pattern file. The design file 220 may be provided in various formats. For example, the format of the design file 220 may be one of the GDS and OASIS formats, among others. The design data of the design file 220 includes cells that have the structure of a pattern to be generated on a substrate (e.g., substrate 120). A cell may be a grouping of logic elements of a transistor or other elements of a semiconductor device. Additionally, a cell may include geometric objects such as polygons (boundaries, paths, and other cells). The objects within a cell are assigned to a "layer" of the corresponding design. Different layers may represent different processing steps in a lithography process. A cell may be referenced whenever that element is drawn. For example, whenever a transistor is drawn, the cell corresponding to the transistor may be referenced. Additionally, a cell may span one or more layers within the design of the design file. A cell hierarchy may include one or more cells. For example, a top-level cell may include all elements of a corresponding object, and each cell in a lower level of the hierarchy may include elements of a different portion of the object.The design file 220 may be in the form of pixel cells, bitmaps, or similar files. The design file 220 may include target regions corresponding to one or more structures. The structures may be constructed as geometric shapes. Additionally, the target regions may be represented as cells during the validation and / or optimization process.

[0021]

[0025] The I / O devices 230 may include one or more of a keyboard, a display device, a mouse, an audio device, and a touch screen, among others. The I / O devices 230 may be utilized to input information to and / or output data from the authentication device 130. For example, a user may use a keyboard and a pointing device to create and / or adjust elements of the design file 220.

[0022]

[0026] The network interface 214 may transmit data over a communications network. For example, the network interface 214 may transmit a design file to the digital lithography device 101 over the communications network.

[0023]

[0027] Global sizing of design file 220 allows the exposure dose to be set to a higher value so that the structures in design file 220 can be printed at the size indicated by design file 220. Additionally, because data indicating the structures can be represented by either dark or light portions of design file 220, the ends of the structures can be moved inward or outward by a first amount during the sizing process. The first amount can be less than the minimum width of the structure.

[0024]

[0028] The design application 218 can be executed by the controller 212 to perform biasing at a cell level of the design file 220. Each cell can correspond to an area of ​​interest identified in the design file 220. The biasing can include feature sizing of pattern structure data contained in cells of the design file 220. For two overlapping cells, if the corresponding drawing data is sized inwardly, cell level sizing of the design file can be completed such that no gap is formed between the cells. Similarly, if the drawing data is sized upwardly, the spacing between the cells is maintained such that the spacing is resolved during the digital lithography process.

[0025]

[0029] FIG. 3 illustrates a method 300 for preparing a design file (e.g., design file 220) for digital lithography, according to one or more embodiments. In operation 310, one or more compatibility checks of the design file are performed. For example, the one or more compatibility checks may include three compatibility checks of the design file. The compatibility checks may include identifying data where cell-to-cell interactions occur. Additionally, the compatibility checks may include identifying all non-orthogonal edges in cell interaction regions. The non-orthogonal edges are flagged as errors. Additionally, the one or more compatibility checks may include a biasing down check in which the design file 220 is checked for overlap regions. Any overlap regions in one or more cells are compared to a target biasing down threshold. A non-compliant overlap region corresponds to an overlap region that overlaps less than the target biasing threshold. Additionally, for biasing up, the one or more compatibility checks may check cells for spatial violations after biasing up is completed. For selective biasing and graytone, the one or more compatibility checks may include determining whether the reference layer and the target layer produce different results for both cell-level and hierarchical level operations. The design application 218 is executed by the controller 212 to perform one or more compatibility checks of the design file 220. Performing the compatibility check may include identifying one or more areas of interest within a cell of the design file 220 and comparing the cell to one or more compatibility rules. The compatibility check is described in further detail in connection with FIG.

[0026]

[0030] In operation 320, biasing is performed at the cell level of the design file 220. Biasing may include biasing up or biasing down at the cell level without considering the influence of nearby polygons from other cell instances in the hierarchy. Biasing may be applied globally or to selected regions. The results from the biasing process may produce insufficient overlap between the structural elements identified by operation 310, so that the biasing results at the cell level may not match the results produced by the global sizing process from the top-level design cell. Operation 320 may be applied to design data that passes or satisfies the compatibility check of operation 310. For example, some non-compliance errors may not be repaired by operation 330. Design files that contain such errors may be flagged as failing the compatibility check, and biasing may not be performed on such design files. Furthermore, compared to conventional global sizing using a hierarchical geometry engine, the amount of processing time utilized by operation 320 is reduced because operation 320 does not consider cell-to-cell interactions. Additionally, in operation 320, the same hierarchical structure as the input design file 220 is maintained.

[0027]

[0031] In operation 330, a hierarchy level repair of the design file generated in operation 320 is performed. The design application 218 may execute on the controller 212 and perform a hierarchy level repair of the output design file from operation 320. The hierarchy level repair of the design file may be completed based on a determination that the design file is non-conforming. The hierarchy level repair process may be completed when the cell level biasing process is completed during operation 320. For example, the hierarchy level repair process may include filling gaps that are smaller than twice the biasing down amount. The gaps may be introduced by the biasing down operation performed during operation 320 and may be the result of the overlapping areas identified by operation 310 being insufficient. By performing a hierarchy level repair of the output of operation 320, additional data may be added at the common parent cell of the interacting cell instances. However, unlike conventional global biasing, the repair operation may be limited to a smaller scope or area and is less likely to cause large-scale hierarchical flattening. For example, the hierarchy level repair may be applied to about 2% or less of the design file. Thus, the impact on data volume is limited for the hierarchical level repair of operation 330. Furthermore, conventional global resizing may result in hierarchical flattening that may increase the amount of data transferred to controller 122. By utilizing the compatibility rules of operation 310, data volume may be reduced by at least about 90% compared to conventional methods of validating and preparing design files for digital lithography. Furthermore, operation 330 is optional and may be omitted from method 300.

[0028]

[0032] FIG. 4 illustrates a method 400 for validating a design file, according to one or more embodiments. For design files determined to conform to the conformance rules, as described in connection with operation 420 of method 400, the results produced using cell-level biasing and repair are substantially similar to biasing using a conventional hierarchical geometry engine. However, when using the conformance rules described in connection with method 400, the amount of data provided to the digital lithography device 101 for digital lithography is reduced. For example, when using global sizing, there may be gaps between cells for each non-conforming location, and one additional polygon may be required to maintain the accuracy of the corresponding biasing, resulting in an increased amount of data. Furthermore, design files determined to include non-orthogonal interacting edges may be rejected because such errors may not be repairable. The validation process described in connection with method 400 can be used to correlate the amount of data provided to the digital lithography device 101.

[0029]

[0033] In operation 410, a design file is accessed. For example, the design file 220 may be accessed from memory 216. The design application 218 may access the design file 220 from memory 216 to identify one or more regions of interest within the design file 220.

[0030]

[0034] At operation 420, a conformance check of the design file is performed. For example, the design application 218 executing on the controller 212 applies one or more rules to the design file 220 to determine whether the design file is conformant. Determining non-conforming locations may include detecting non-orthogonal structures, insufficient overlapping structures, and / or differences in selective behavior between cells and hierarchical levels, as described above. Operations 422-426 describe the conformance check in further detail.

[0031]

[0035] In operation 422, the design application 218 determines whether a non-orthogonal edge exists within the target region of the cell. Determining the non-orthogonal edge may include determining whether edges of overlapping structures may be at angles other than 0 degrees or 180 degrees. For example, the design application 218 may identify a target region between one or more structures, or polygons, and a cell, identify one or more edges from the structures, and determine whether the identified edges are non-orthogonal with respect to one another. If a non-orthogonal edge is identified, the corresponding target region may be marked as non-conforming and added to an error list.

[0032]

[0036] The interest regions are determined by the design application 218 by analyzing the design file, detecting interactions of structures between adjacent cells, and flagging the detected interactions as interest regions. With reference to FIG. 6, the design application 218 can determine interest regions 616 by detecting cell-to-cell interactions between the structure 614 and structures of other cells in a common hierarchy. Interacting structures are structures that at least partially overlap. Furthermore, the interacting structures are in a common hierarchical layer. The view 610 of the cell 600 includes interest regions 616 (e.g., interest region 616a and interest region 616b) that correspond to interactions between the structure 614 and structures of other adjacent cells. For example, interest region 616a corresponds to a location where the structure 614 interacts with a structure of a first cell, and interest region 616b corresponds to a location where the structure 614 interacts with a structure of a second cell. One or more interest regions may be excluded if it is found that the structure 614 does not interact with a corresponding structure of another cell. Additionally, as shown in view 620, interest area 616a corresponds to an interaction between structure 614 and structure 626 at a hierarchical level.

[0033]

[0037] The design application 218 further generates a marker in the cell. The marker corresponds to the edge of the structure of the cell. The marker can be utilized to detect non-matching target regions and corresponding non-matching cells. As shown in FIG. 6, the cell 600 is tagged with a marker 612 corresponding to the edge of the structure 614. The design application 218 utilizes the markers of the overlapping edges of the overlapping structures to determine whether the target regions are matched. For example, detecting non-matching target regions includes selecting a marker corresponding to an interaction between two structures and determining whether an angle formed between the selected markers is different from 0 degrees or 180 degrees. With reference to FIG. 6 and the view 620, the markers 612a and 624 are selected based on a determination that the markers 612a and 624 correspond to the overlapping edges of the interaction between the structures 614 and 626. In other words, the markers 612a and 624 are selected when the markers 612a and 624 identify a hierarchical interaction of the structures 614 and 626. Thus, the markers 612a and 626 may be used by the design application 218 to determine whether the target region 616a is compatible. For example, as shown by region 636 of view 630, non-orthogonal edges are detected and flagged between structures 614 and 626. Determining the non-orthogonal edges includes determining whether the angle between marker 612a and marker 624 is a value other than 0 degrees or 180 degrees. For example, the design application 218 measures the angle formed between marker 612a and marker 624, and the target region 616a is determined to be non-compatible if the angle is determined to be a value other than 0 degrees or 180 degrees. If the angle formed between the selected marker 612a and marker 624 is determined to be a value other than 0 degrees or 180 degrees, the target region is determined to be non-compatible by the design application 218, and the cell 600 is marked as non-compatible and added to an error list. Alternatively, if it is determined that there are no non-orthogonal edges in the target region, the target region and the corresponding cell are determined to be compatible. Additionally, design files that are determined to contain one or more non-compliant cells may be rejected.

[0034]

[0038] In operation 424, the design application 218 determines whether the overlapping structural elements match. For example, the design application 218 may be executed by the controller 212 to identify overlapping edges within the target region, determine the number of overlapping edges, and determine whether the number of overlapping edges meets an edge threshold. The edge threshold may be set such that a matching target region of cells does not have more than three adjacent edges within the overlapping region. Additionally, a target region that meets the overlap threshold may be a target region that does not have more adjacent edges than defined by the edge threshold. With reference to FIG. 7, a target region 700 may be evaluated by the design application 218 to determine whether the target region 700 meets the overlap threshold. For example, the target region 700 includes structures 702 and 704. The design application 218 compares the number of edges of the structure 704 that overlap with the structure 702 to the overlap threshold. The overlap threshold may have a value of three. Additionally, the overlap threshold may have a value less than or greater than three. As shown in FIG. 7, the number of edges of structure 704 that overlap structure 702 is 5, and the region of interest 700 may be marked as non-conforming and added to an error list.

[0035]

[0039] Further, operation 424 may include identifying one or more edges of at least one of structure 702 and structure 704 and determining whether the distance of the overlap is less than a distance threshold. If the overlap amount is less than the distance threshold, the corresponding target region may be indicated as non-conforming. Referring to FIG. 8 , a target region 800 including structures 802 and 804 is shown. Structure 804 overlaps with structure 802 by a first amount indicated by region 806. This overlap amount is compared by design application 218 to an overlap threshold to determine whether the cell including target region 800 is conforming. The overlap threshold may be at least as large as a target bias amount (e.g., the amount by which a cell is biased during resizing). If the overlap amount indicated by region 806 does not meet the overlap threshold, the cell including target region 800 may be determined to be non-conforming and added to an error list.

[0036]

[0040] In operation 426, the design application 218 determines whether a selective biasing error exists in the cell configuration. For example, the design application 218 may identify one or more structures in the cell and compare the structures to the composite hierarchical data of the design file (e.g., design file 220) to determine whether a mismatch exists during the selection process. An error may be determined to exist when a structure is excluded from the cell. For example, as shown in FIG. 9, a target area 900 includes a reference layer 902 and a target layer 904. However, as shown in the hierarchical configuration view 910, the reference layer 902 passes over another target layer 904 from a different cell instance. Thus, the cell including the target area 900 may be identified as including an error and being non-conforming. Thus, the cell including the target area 900 may be added to an error list.

[0037]

[0041] In operation 430, the user is prompted to address the errors. For example, the user may be prompted to address the errors identified in the error list. The error list may be generated by operation 420. Further, the error list may be evaluated and grouped based on their severity. For example, the non-conformance errors generated by operations 422 and 426 may be grouped and identified for corrective action. Further, the non-conformance errors from operation 424 may be compared to a percentage threshold to determine whether the design file passed the conformance check. For example, if it is determined that 95% of the ends identified during operation 424 meet the overlap threshold, the design file passes the check. However, if it is determined that more than 5% of the ends identified during operation 424 do not meet the overlap threshold, the design file did not pass the check. Further, if the percentage of ends that meet the overlap threshold is greater than about 95%, a reduction in the amount of data transferred to the controller 122 may be achieved. Additionally or alternatively, the design application 218 may be executed by the controller 212 to generate the error list based on the conformance check of operation 420.

[0038]

[0042] The design application 218 executed by the controller 212 can output the error list to the user via the I / O device along with a request for the user to update the design file 220 to correct the identified errors. For example, the error list can be presented to the user via a display device of the authentication device 130. The user can update the design file 220 to correct the identified errors. After the design file is modified, the method 400 can be utilized to evaluate and authenticate the updated design file. Alternatively, the user may choose to ignore the request to correct the identified errors and communicate the design file 220 to the digital lithography device 101. However, using an unauthenticated design file can result in errors during the digital lithography process.

[0039]

[0043] Method 400 may further include an optional operation 440 of repairing the design file. For example, the design file is repaired by filling gaps (or spaces) between cell elements in one or more of the non-matching regions. Operation 440 may be performed in response to detecting or determining non-matching errors of operation 424 for automatic repair of the design file. Alternatively, method 400 may include operation 440 as an alternative or in addition to prompting a user to address the identified errors to reduce the amount of data. Furthermore, a combination of cell-level biasing down and patching of gaps between cells or cell elements may produce comparable results compared to the results of traditional global biasing. Furthermore, the cell-level biasing operation described above does not change the hierarchical structure and therefore does not increase the amount of data transferred to controller 122. Because the amount of data may increase during a design repair operation (e.g., operation 440), a design file with fewer non-matching errors will produce a more compact design file.

[0040]

[0044] In operation 450, the design file is certified. For example, the design file 220 may be certified by the design application 218 as being suitable and ready for the digital lithography process if no errors are identified during the certification process (e.g., method 400). After the design file is certified, the design file 220 may be communicated to the digital lithography device 101. For example, the design file 220 may be communicated to the controller 122 of the digital lithography device 101 via the network interface 214 and a communication network. Alternatively or additionally, the design file 220 may be stored in a removable memory before being transferred to the digital lithography device 101.

[0041]

[0045] Certification of design files used in a digital lithography process helps reduce errors that may occur during the digital lithography process. For example, the certification process can identify errors in the design files before the design files are provided to the digital lithography process. Additionally, the amount of data provided to the digital lithography process can be reduced by performing certification at the cell level, with adjustments to the design files made at a hierarchical level.

[0042]

[0046] 3 and 4 may be stored in a computer program product and executed on a controller (e.g., controller 122 and / or 212). The computer program product may include a computer-readable storage medium having computer-readable program instructions for causing a processor to perform aspects of the present invention.

[0043]

[0047] A computer-readable storage medium may be a tangible device capable of holding and storing instructions used by an instruction execution device. A computer-readable storage medium may include memory 216. A computer-readable storage medium may be, for example, but not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing. A non-exhaustive list of more specific examples of computer-readable storage media includes, among others, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a static random access memory (SRAM), a portable compact disk read-only memory, a portable compact disk read-only memory (CD-ROM), a digital versatile disk, a memory stick, or a floppy disk.

[0044]

[0048] The computer-readable program instructions described herein may be downloaded from a computer-readable storage medium into the respective computing / processing device, or downloaded to an external computer or storage device over a network (e.g., the Internet, a local area network, a wide area network, and / or a wireless network). A network adapter card or network interface in each computing / processing device receives the computer-readable program instructions from the network and transfers the computer-readable program instructions for storage in a computer-readable storage medium in the respective computing / processing device.

[0045]

[0049] The computer readable program instructions for carrying out the operations of the present invention may be either assembler instructions, instruction set architecture (ISA) instructions, machine instructions, machine dependent instructions, microcode, firmware instructions, state-setting data, or source or object code written in any combination of one or more programming languages ​​(including object-oriented programming languages ​​such as Smalltalk, C++, and traditional procedural programming languages ​​such as the "C" programming language or similar programming languages). In some embodiments, electronic circuitry including, for example, programmable logic circuits, field programmable gate arrays (FPGAs), or programmable logic arrays (PLAs) can execute the computer readable program instructions by utilizing state information of the computer readable program instructions to personalize the electronic circuitry to carry out aspects of the present invention.

[0046]

[0050] Aspects of the present invention are described herein with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer readable program instructions.

[0047]

[0051] These computer readable program instructions may be provided to controller 122 and / or controller 212. Further, the computer readable program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, whereby the instructions, executed by the processor of the computer or other programmable data processing apparatus, create means for implementing the functions / acts specified in one or more blocks of the flowcharts and / or block diagrams. These computer readable program instructions may be stored in memory 216.

[0048]

[0052] While the foregoing is directed to embodiments of the disclosure, other and further embodiments of the disclosure may be devised without departing from the basic scope thereof, the scope of which is determined by the claims that follow.

Claims

1. Accessing a design file for the digital lithography device from a memory; applying one or more compatibility rules to the design file; detecting non-orthogonal edges in the design file; detecting non-matching overlapping structures in the design file; and detecting non-compatible interactions between a reference layer of the design file and a target layer of the design file; determining suitability of the design file by at least one of validating the design file in response to comparing a number of non-orthogonal edges, non-matching overlapping structures, and non-matching interactions to a threshold; The method includes:

2. Detecting non-orthogonal edges Detecting an overlap region between a first structure and a second structure; determining whether the first structure forms an orthogonal edge with the second structure; The method of claim 1 , comprising:

3. Detecting the overlapping regions generating a plurality of markers around the first structure and the second structure; selecting a first marker and a second marker from the plurality of markers, the first marker and the second marker identifying an interaction region of the first structure and the second structure; determining whether the first structure forms an orthogonal edge with the second structure comprises: The method of claim 2 , comprising determining whether the first marker is orthogonal to the second marker.

4. Detecting non-matching overlapping structures comparing an amount that the first structure extends into the second structure to a first threshold; identifying one or more edges of at least one of the first structure and the second structure that are non-orthogonal in an overlap region between the first structure and the second structure; comparing a number of adjacent edges of the first structure within the overlap region to an edge threshold; The method of claim 1 , comprising at least one of:

5. The positions corresponding to the first structure and the second structure are an extension of the first structure into the second structure exceeding the first threshold; and identifying at least one non-orthogonal edge within the overlap region; the number of adjacent edges exceeds the edge threshold; and The method of claim 4 , wherein the non-conformity may be determined in response to one or more of:

6. Detecting non-matching overlaps between structures Identifying a first structure that overlaps with a second structure; determining an amount of overlap between the first structure and the second structure; comparing the amount of overlap to a threshold; Including, The method of claim 1 , wherein the location corresponding to the structure may be determined to be non-matching in response to the amount of overlap being less than the threshold.

7. 1. An authentication device for authenticating a design file for digital lithography, comprising: a memory containing the design file; and a controller. The controller: Accessing the design file; applying one or more compatibility rules to the design file; detecting non-orthogonal edges in the design file; detecting non-matching overlapping structures in the design file; and detecting non-compatible interactions between a reference layer of the design file and a target layer of the design file; determining suitability of the design file by at least one of validating the design file in response to comparing a number of non-orthogonal edges, non-matching overlapping structures, and non-matching interactions to a threshold value; An authentication device that is configured to:

8. Detecting non-orthogonal edges Detecting an overlap region between a first structure and a second structure; determining whether the first structure fails to form an orthogonal edge with the second structure; The authentication device of claim 7 , comprising:

9. Detecting the overlapping regions generating a plurality of markers around the first structure and the second structure; selecting a first marker and a second marker from the plurality of markers, the first marker and the second marker identifying an interaction region of the first structure and the second structure; determining whether the first structure fails to form an orthogonal edge with the second structure includes: The authentication device of claim 8 , further comprising determining whether the first marker is orthogonal to the second marker.

10. Detecting non-matching overlapping structures comparing an amount that the first structure extends into the second structure to a first threshold; identifying one or more edges of at least one of the first structure and the second structure that are non-orthogonal in an overlap region between the first structure and the second structure; comparing a number of adjacent edges of the first structure within the overlap region to an edge threshold; The authentication device of claim 7, comprising at least one of:

11. Detecting non-matching overlaps between structures Identifying a first structure that overlaps with a second structure; determining an amount of overlap between the first structure and the second structure; comparing the amount of overlap to a threshold; The authentication device of claim 7 , comprising:

12. 1. A computer program product for authenticating a design file for digital lithography, the computer program product comprising: A computer readable storage medium having computer readable program code embodied therein, the computer readable program code comprising: Accessing the design file from memory; applying one or more compatibility rules to the design file; detecting non-orthogonal edges in the design file; detecting non-matching overlapping structures in the design file; and detecting non-compatible interactions between a reference layer of the design file and a target layer of the design file; determining suitability of the design file by at least one of validating the design file in response to comparing a number of non-orthogonal edges, non-matching overlapping structures, and non-matching interactions to a threshold value; A computer program product executable by one or more processors, such as

13. Detecting non-orthogonal edges detecting an overlap region between a first structure and a second structure in the design file; determining whether the first structure fails to form an orthogonal edge with the second structure; 13. The computer program product of claim 12, comprising:

14. Detecting non-matching overlapping structures comparing an amount that the first structure extends into the second structure to a first threshold; identifying one or more edges of at least one of the first structure and the second structure that are non-orthogonal in an overlap region between the first structure and the second structure; comparing a number of adjacent edges of the first structure within the overlap region to an edge threshold; 13. The computer program product of claim 12, comprising at least one of:

15. Detecting the non-matching overlap between the structures Identifying a first structure that overlaps with a second structure; determining an amount of overlap between the first structure and the second structure; comparing the amount of overlap to a threshold; 15. The computer program product of claim 14, comprising:

Citation Information

Patent Citations

  • Method of inspecting data for forming pattern film for printed wiring board

    JP1988164487A

  • Mask pattern correcting method and photomask manufacturing method

    JP2006276491A

  • Image processing device, image drawing device, and system

    JP2006350013A

  • Verification system of semiconductor device and manufacturing method of semiconductor device

    JP2008015688A

  • Verification method, verification program and verification device

    JP2013156817A