Data processing method based on integrated circuit chip design project

Abstract

The invention discloses a data processing method based on an integrated circuit chip design project. The data processing method comprises the following steps: establishing a connection relationship between a first device and a second device; establishing a project data pool named by a project on a second device; uploading the design data of a certain version completed on the first device to a project data pool of a corresponding project in the second device; the project data pool of the second device reads the design data uploaded by the first device, decomposes the design data into a small-space design data minimum unit and a small-space design data text file, and stores the design data minimum unit and the design data text file respectively; and selecting the design data of a certain version of the corresponding project on the second device on the first device for restoration. According to the method, the uploaded design data is automatically extracted and decomposed into the small-memory data for storage, the storage space of a data pool is saved, and the function of reducing the memory data is achieved.

Description

Technical Field

[0001] The present invention relates to the field of electronic digital data processing, and in particular to a data processing method based on an integrated circuit chip design project. Background Art

[0002] During the integrated circuit chip design process, design teams generate massive amounts of frequently iterated design data. Due to the high complexity and collaborative nature of chip design, project team members frequently access and modify this design data. This places stringent demands on data storage and management systems: they must ensure design data integrity (to prevent data corruption or loss), accuracy (to avoid version confusion or misreferences), and real-time performance (to ensure team members have access to the latest version). Furthermore, to meet industry compliance requirements and design traceability needs, the system must also fully record the history of design changes, for example, enabling full traceability from tapeout results to the original design.

[0003] Traditional file storage methods directly save the complete data for each version. However, when dealing with large layout files or simulation data with high duplication rates, storage space requirements can grow exponentially. This storage model not only wastes expensive server resources but also significantly increases data backup and retrieval time, hindering team collaboration efficiency. Furthermore, decentralized version management can lead to design conflicts and version confusion, increasing project risks. Therefore, intelligent data storage and management solutions are urgently needed to address these issues. Summary of the Invention

[0004] The purpose of the present invention is to overcome the deficiencies of the prior art and provide a data processing method based on an integrated circuit chip design project.

[0005] The object of the present invention is achieved through the following technical solutions: A first aspect of the present invention provides a data processing method based on an integrated circuit chip design project, comprising the following steps: Establishing a connection relationship between a first device and a second device, wherein the first device includes a project design environment for an integrated circuit chip and the second device includes a project data pool; Establishing a project data pool named after the project on the second device for storing and reading various versions of design data generated in the project design of the project integrated circuit chip; Uploading a version of design data completed on the first device to a project data pool of a corresponding project in the second device; The project data pool of the second device reads the design data uploaded by the first device, decomposes the design data into two parts: the smallest design data unit in a small space and the design data text file, and stores the smallest design data unit and the design data text file respectively; Selecting, on the first device, to restore design data of a certain version of a corresponding project on the second device; The project data pool of the second device respectively restores the design data minimum unit and the design data text file of a certain version of the design data to be restored, and after combining, restores the certain version of the design data and sends it to the first device.

[0006] Furthermore, the design data minimum unit includes a set of device minimum units and routing minimum units in the design data; wherein: The minimum unit of the device includes the minimum process size of each device in the design data. The devices include transistors, resistors, capacitors, inductors, and diodes. The minimum routing unit includes the minimum process width of each routing metal layer in the design data.

[0007] Furthermore, the design data text file includes: device type and device size, routing metal layer type, routing metal layer width and routing metal layer length, relative position information between the device and the coordinate origin, relative position information between the routing and the coordinate origin, and size and position information of other process layers.

[0008] Furthermore, the method further comprises the following steps: The project data pool of the second device reads the design data uploaded by the first device, and compares the uploaded design data with the stored design data. If the stored design data is consistent with the uploaded design data, the project data pool indexes the uploaded design data to the consistent stored design data.

[0009] Furthermore, the design data of a certain version completed on the first device is modified based on the design data of the basic version; when the design data of a certain version completed on the first device is uploaded to the project data pool of the corresponding project in the second device, the version number of the design data based on the basic version is also uploaded; The project data pool of the second device reads the design data and version number uploaded by the first device. The project data pool compares the uploaded design data with the design data of the basic version corresponding to the stored version number to obtain the design data difference. The project data pool stores the design data difference, the version number of the design data of the basic version and the version number of the design data uploaded this time.

[0010] Furthermore, when the difference between the design data and the design data of the basic version exceeds a first threshold ratio, the project data pool directly stores the uploaded design data.

[0011] Furthermore, the method further comprises the following steps: When the project is completed, the corresponding project data pool on the second device turns on the data pool closing mode; When the first device captures the design data restored from the project data pool in the data pool closed mode in the second device, operations of modifying the design data and uploading the design data cannot be performed in the project design environment of the first device.

[0012] The beneficial effects of the present invention are: Specifically, in this exemplary embodiment, in order to solve the problem in the prior art that the full-link traceability has large storage space and decentralized version management, which may lead to design conflicts or version confusion and increase project risks, in an exemplary embodiment of the present invention, a unique storage mechanism can automatically extract the uploaded design data and decompose it into small memory data for storage, saving data pool storage space and having the function of reducing memory data; at the same time, it can realize the rapid reading of design data. When it is necessary to read, restore or view a certain design data, the smallest unit of design data and the corresponding parameter text file are directly taken out from the data pool to restore the original detailed design data, and the data is accurate and reliable. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] Figure 1 The present invention provides a flowchart of a data processing method based on an integrated circuit chip design project according to an exemplary embodiment of the present invention. DETAILED DESCRIPTION

[0014] The technical solution of the present invention is described clearly and completely below with reference to the accompanying drawings. It is apparent that the embodiments described are only a portion of the embodiments of the present invention, not all of them. All other embodiments derived by persons of ordinary skill in the art based on the embodiments of the present invention without inventive effort are intended to fall within the scope of protection of the present invention.

[0015] In the description of the present invention, it should be noted that the directions or positional relationships indicated by terms such as "center," "up," "down," "left," "right," "vertical," "horizontal," "inside," and "outside" are based on the directions or positional relationships described in the accompanying drawings and are intended solely to facilitate and simplify the description of the present invention. They are not intended to indicate or imply that the devices or components referred to must have a specific orientation, be constructed, or operate in a specific orientation. Therefore, they should not be construed as limitations on the present invention. Furthermore, terms such as "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance.

[0016] In the description of the present invention, it should be noted that, unless otherwise expressly specified or limited, the terms "mounted," "connected," and "connected" should be understood in a broad sense. For example, they may refer to fixed connections, detachable connections, or integral connections; mechanical connections or electrical connections; direct connections or indirect connections through an intermediate medium; and internal communication between two components. Those skilled in the art will understand the specific meanings of the above terms in the present invention.

[0017] In addition, the technical features involved in the different embodiments of the present invention described below can be combined with each other as long as they do not conflict with each other.

[0018] See also Figure 1 , Figure 1 A flowchart of a data processing method based on an integrated circuit chip design project provided in an exemplary embodiment of the present invention is shown, comprising the following steps: Establishing a connection relationship between a first device and a second device, wherein the first device includes a project design environment for an integrated circuit chip and the second device includes a project data pool; Establishing a project data pool named after the project on the second device for storing and reading various versions of design data generated in the project design of the project integrated circuit chip; Uploading a version of design data completed on the first device to a project data pool of a corresponding project in the second device; The project data pool of the second device reads the design data uploaded by the first device, decomposes the design data into two parts: the smallest design data unit in a small space and the design data text file, and stores the smallest design data unit and the design data text file respectively; Selecting, on the first device, to restore design data of a certain version of a corresponding project on the second device; The project data pool of the second device respectively restores the design data minimum unit and the design data text file of a certain version of the design data to be restored, and after combining, restores the certain version of the design data and sends it to the first device.

[0019] Specifically, in one exemplary embodiment, the first device corresponds to a device containing an integrated circuit chip design environment (a user terminal, such as a PC or other smart device capable of project design using a browser) used by project team members. Integrated circuit chip project team members can complete chip design on the first device. The second device corresponds to a device containing a project data pool (a server terminal, such as a local server or a cloud server). The second device can store the integrated circuit chip project data. Any other possible implementation methods are not detailed here.

[0020] In this exemplary embodiment, first, a connection relationship is established between the first device and the second device, that is, a data connection is established between the user end and the server end; secondly, a project data pool named after the project is established on the second device, which is used to store and read various versions of design data generated in the project design of the project integrated circuit chip, for example, the design data of various versions of all stages of the A integrated circuit chip are stored in the A project data pool; thereafter, the project team members load the project data pool named after the corresponding project through the first device, and upload a certain version of the design data completed on the first device to the corresponding project data pool for storage, for example, the design data of the 31st version of the A integrated circuit chip is uploaded to the A project data pool; then, the second device uses a unique storage mechanism for design data storage, that is, automatic reading and writing. The design data uploaded by the first device is retrieved and decomposed into the smallest units, and a text message storing detailed information of the design data is generated and saved in the same path, thereby completing the efficient real-time storage of each version of the design data and saving data storage space; finally, when the project team members need to read, restore or view the design data (i.e., select a certain version of the design data of the corresponding project on the second device for restoration on the first device), the second device uses a unique reading mechanism to read and restore the data, automatically grabs the stored information, and restores the original detailed design data (i.e., the project data pool of the second device restores the design data smallest unit and the design data text file of a certain version of the design data to be restored, and after combining, restores it to a certain version of the design data and sends it to the first device).

[0021] To sum up, in order to solve the problems in the existing technology of full-link traceability, such as large storage space and decentralized version management, which may lead to design conflicts or version confusion and increase project risks, in an exemplary embodiment of the present invention, a unique storage mechanism can automatically extract the uploaded design data and decompose it into small memory data for storage, saving data pool storage space and having the function of reducing memory data; at the same time, it can realize the rapid reading of design data. When it is necessary to read, restore or view a certain design data, the smallest unit of design data and the corresponding parameter text file are directly taken out from the data pool to restore the original detailed design data, and the data is accurate and reliable.

[0022] It should be noted that during the project process, after the project team members successfully load the project data pool of the second device on the first device, they upload the initial design data to the project data pool for storage. The project data pool immediately completes the storage of the design data version and related information, and simultaneously places the design data in the project design environment for viewing. After refreshing, each project team member can simultaneously select and view the initial design data. The same applies to subsequent design data.

[0023] More preferably, in an exemplary embodiment, the design data minimum unit includes a set of device minimum units and routing minimum units in the design data; wherein: The minimum unit of the device includes the minimum process size of each device in the design data. The devices include transistors, resistors, capacitors, inductors, and diodes. The minimum routing unit includes the minimum process width of each routing metal layer in the design data.

[0024] More preferably, in an exemplary embodiment, the design data text file includes: device type and device size, routing metal layer type, routing metal layer width and routing metal layer length, relative position information between the device and the coordinate origin, relative position information between the routing and the coordinate origin, and size and position information of other process layers.

[0025] Specifically, in the two exemplary embodiments described above, when a project team member uploads design data from a first device to a project data pool on a second device, the project data pool utilizes a unique storage and reading mechanism to automatically read the uploaded design data, decompose the design data into the smallest design unit, and store it. At the same time, it automatically generates a text file that stores the attributes, dimensions, and location information of the corresponding design data and saves it in the same path, effectively storing each version of the design data in real time. The project data pool decomposes the design data into two parts: the smallest design data unit and the design data text file. Among them: The minimum unit of design data is the collection of all device minimum units (device minimum size) and all routing minimum units (routing minimum size) in the design data read from the project data pool. The device minimum unit can include the process minimum size of transistors, resistors, capacitors, inductors, diodes and other devices in the design data. The routing minimum size is the process minimum width of all routing metal layers used in the design data.

[0026] The design data text file includes device type and device size, routing metal layer type, routing metal layer width and routing metal layer length, relative position information between the device and the coordinate origin, relative position information between the routing and the coordinate origin, and size and position information of other process layers.

[0027] By storing the smallest unit of design data in a small space and a text file containing its detailed information, storage space is freed up and data storage space is saved to the maximum extent.

[0028] More preferably, in an exemplary embodiment, the method further comprises the following steps: The project data pool of the second device reads the design data uploaded by the first device, and compares the uploaded design data with the stored design data. If the stored design data is consistent with the uploaded design data, the project data pool indexes the uploaded design data to the consistent stored design data.

[0029] First, it should be noted that in the prior art, for integrated circuit chip design projects, the problem of duplicate storage of design data is also prevalent within the same project, and presents more complex characteristics. This intra-project duplication is mainly reflected in the following situations: (1) First, in each stage of project development (such as architecture design, RTL implementation, physical design, verification, etc.), the design data may return to the previous version state after multiple iterations. For example, when optimizing a functional module, engineers may try multiple modification solutions and finally return to the initial design, resulting in a large number of temporary versions generated in the middle actually containing multiple duplicate data copies. (2) Secondly, different project team members (such as front-end design engineers, verification engineers, and back-end layout engineers) may independently modify the same design data based on their respective work needs but obtain the same results. This situation is particularly common in large-scale team collaboration: multiple engineers may adopt similar modification methods to solve the same problem, but due to the lack of a real-time data comparison mechanism, the system will save all their modifications as independent versions.

[0030] That is to say, the same design data may produce the same situation when modified at different stages, or the same design data may be produced when modified by different project team members; this further leads to the repeated storage of the same design data. When manually managing the design data storage, it is impossible to visually observe whether the design data is consistent with the naked eye, resulting in many identical design data being stored in the storage space, causing a waste of storage space.

[0031] In this exemplary embodiment, an automatic comparison and checking function is provided, and newly uploaded design data that is consistent with existing design data in the project data pool will not be backed up, thereby ensuring the uniqueness of the design data while improving the utilization rate of the storage space of the project data pool.

[0032] It should be noted that as the amount of design data in the project data pool increases, the cost of data comparison also increases. In one exemplary embodiment, the cost of data comparison can be compared with the cost of data storage to select the more valuable method for processing. For example, when there is less design data, the cost of data comparison is lower, so comparison processing is performed; when there is more design data, the cost of data comparison is higher, so direct storage processing is performed. Of course, other valuable costs can also be referenced and calculated, such as the number of processors used for data comparison, the value of the integrated circuit chip itself, etc., which are not limited here.

[0033] More preferably, in an exemplary embodiment, the design data of a certain version completed on the first device is modified based on the design data of the base version; when the design data of a certain version completed on the first device is uploaded to the project data pool of the corresponding project in the second device, the version number of the design data based on the base version is also uploaded; The project data pool of the second device reads the design data and version number uploaded by the first device. The project data pool compares the uploaded design data with the design data of the basic version corresponding to the stored version number to obtain the design data difference. The project data pool stores the design data difference, the version number of the design data of the basic version and the version number of the design data uploaded this time.

[0034] Specifically, it should be noted that in the prior art, as mentioned above, the complete storage method of multiple versions of project design data results in low storage space utilization: during the chip design process, due to changes in design requirements, performance optimization, or bug fixes, the design data will undergo frequent modifications and iterations, thereby generating a large amount of version data. Currently, the industry generally adopts a storage method that completely preserves each version of the design data, that is, after each modification, the entire design data set is re-stored as an independent new version. Although this extensive storage strategy is simple and direct, it takes up a large amount of storage space, resulting in serious space waste and greatly reducing the space utilization of the storage system.

[0035] Specifically, in simple scenarios, two layout files may be completely identical in their core content. However, due to non-essential differences such as generation time, user annotations, or system metadata, they will be treated as separate files and stored in their entirety by the version control system. Secondly, in more complex situations, some consecutive versions of design data may have 99% of the same content, with only minor local modifications (such as parameter adjustments to a functional module or local wiring optimization). However, existing systems will still mechanically store this highly similar data as separate files. This storage method not only leads to linear or even exponential growth in storage capacity, but also increases backup costs and places an unnecessary burden on network bandwidth and computing resources.

[0036] In response to the above situation, in this exemplary embodiment, a certain version of design data completed by a project team member on the first device is modified based on the design data of the base version. For example, the 31st version of design data is modified based on the 30th version of design data (the 30th version of design data is preferably restored from the second device); when a certain version of design data completed on the first device is uploaded to the project data pool of the corresponding project in the second device, the version number of the design data based on the base version is uploaded at the same time. For example, when uploading the 31st version of design data, the 31st version of design data and the 30th version number of design data are uploaded together; the project data pool of the second device reads the design data and version number uploaded by the first device, and the project data pool compares the uploaded design data with the base version of design data corresponding to the stored version number to obtain a design data difference. The project data pool stores the design data difference, the version number of the base version of design data, and the version number of the design data uploaded this time. For example, the project data pool of the second device stores the design data difference obtained by comparing the 31st version of design data with the 30th version of design data, the version number 30 of the base version of design data, and the version number 31 of the design data uploaded this time.

[0037] More preferably, in an exemplary embodiment, when the difference between the design data and the design data of the base version exceeds a first threshold ratio, the project data pool directly stores the uploaded design data.

[0038] Specifically, the storage of design data differences also involves value judgment. In this exemplary embodiment, the primary consideration is the difference between the design data and the base version's design data. When the difference exceeds a first threshold ratio (e.g., 50%), the project data pool directly stores the uploaded design data. This is equivalent to directly storing chip design data with significant differences.

[0039] It should be noted that the specified one-to-one comparison has a low data processing cost and mainly considers the differences; however, if the chip design data itself is large, other parameters can also be compared horizontally.

[0040] More preferably, in an exemplary embodiment, the method further comprises the following steps: When the project is completed, the corresponding project data pool on the second device turns on the data pool closing mode; When the first device captures the design data restored from the project data pool in the data pool closed mode in the second device, operations of modifying the design data and uploading the design data cannot be performed in the project design environment of the first device.

[0041] Specifically, in this exemplary embodiment, adopting the data pool closed mode has the following advantages: (1) Prevent data tampering and ensure data integrity: After a chip design project is completed, the design data is usually archived and used as the final version for tape-out and subsequent verification. If arbitrary modifications are allowed, human error or malicious tampering may occur, undermining the reliability of the data. Disabling write permissions ensures that the data always remains in its original state, avoiding data inconsistencies caused by accidental or intentional modifications.

[0042] (2) Avoid version confusion and improve data traceability: During a project, design data may undergo multiple iterations. Closing the data pool and freezing all modifications can prevent subsequent personnel from mistakenly submitting new versions, which would cause version management confusion. Authorized personnel can only reference or restore based on archived data without generating additional conflicts or redundant data, ensuring that data versions are clear and traceable.

[0043] (3) Optimize storage resource management: When the project data pool is closed, since adding or modifying data is prohibited, the system can perform data backup and storage optimization more efficiently, reduce unnecessary storage growth, and ensure long-term data availability.

[0044] Obviously, the above embodiments are merely examples for clarity of explanation and are not intended to limit the implementation methods. Those skilled in the art will readily appreciate that other variations or modifications can be made based on the above descriptions. It is not necessary and impossible to enumerate all implementation methods here. Obvious variations or modifications derived therefrom remain within the scope of protection of the present invention.

Claims

1. A data processing method based on an integrated circuit chip design project, characterized in that: The following steps are involved: Establishing a connection relationship between a first device and a second device, wherein the first device includes a project design environment for an integrated circuit chip and the second device includes a project data pool; Establishing a project data pool named after the project on the second device for storing and reading various versions of design data generated in the project design of the project integrated circuit chip; Uploading a version of design data completed on the first device to a project data pool of a corresponding project in the second device; The project data pool of the second device reads the design data uploaded by the first device, decomposes the design data into two parts: the smallest design data unit in a small space and the design data text file, and stores the smallest design data unit and the design data text file respectively; Selecting, on the first device, to restore design data of a certain version of a corresponding project on the second device; The project data pool of the second device respectively restores the design data minimum unit and the design data text file of a certain version of the design data to be restored, and after combining, restores the certain version of the design data and sends it to the first device.

2. The data processing method based on an integrated circuit chip design project according to claim 1, characterized in that: The minimum unit of design data includes a set of a minimum device unit and a minimum routing unit in the design data; wherein: The minimum unit of the device includes the minimum process size of each device in the design data. The devices include transistors, resistors, capacitors, inductors, and diodes. The minimum routing unit includes the minimum process width of each routing metal layer in the design data.

3. The data processing method based on an integrated circuit chip design project according to claim 2, characterized in that: The design data text file includes: device type and device size, routing metal layer type, routing metal layer width and routing metal layer length, relative position information between the device and the coordinate origin, relative position information between the routing and the coordinate origin, and size and position information of other process layers.

4. The data processing method based on an integrated circuit chip design project according to claim 1, characterized in that: The method further comprises the following steps: The project data pool of the second device reads the design data uploaded by the first device, and compares the uploaded design data with the stored design data. If the stored design data is consistent with the uploaded design data, the project data pool indexes the uploaded design data to the consistent stored design data.

5. The data processing method based on an integrated circuit chip design project according to claim 1, characterized in that: The design data of a certain version completed on the first device is modified based on the design data of the basic version; when the design data of a certain version completed on the first device is uploaded to the project data pool of the corresponding project in the second device, the version number of the design data based on the basic version is uploaded at the same time; The project data pool of the second device reads the design data and version number uploaded by the first device. The project data pool compares the uploaded design data with the design data of the basic version corresponding to the stored version number to obtain the design data difference. The project data pool stores the design data difference, the version number of the design data of the basic version and the version number of the design data uploaded this time.

6. The data processing method based on an integrated circuit chip design project according to claim 5, characterized in that: When the difference between the design data and the design data of the basic version exceeds a first threshold ratio, the project data pool directly stores the uploaded design data.

7. The data processing method based on an integrated circuit chip design project according to claim 1, characterized in that: The method further comprises the following steps: When the project is completed, the corresponding project data pool on the second device turns on the data pool closing mode; When the first device captures the design data restored from the project data pool in the data pool closed mode in the second device, operations of modifying the design data and uploading the design data cannot be performed in the project design environment of the first device.

Images