Chip design data version acquisition method and device, computer equipment and storage medium

Abstract

The invention relates to a chip design data version obtaining method and device, computer equipment and a storage medium, and belongs to the technical field of data management. Comprising the steps of 1, creating a chip design data management table; the chip design data management table comprises an identification code, a change person, change time, a pre-change extension field and a post-change extension field; the pre-change extension field is used for storing a pre-change extension attribute; the post-change extension field is used for storing a post-change extension attribute; 2, receiving a change instruction of target chip design data; the change instruction comprises an identification code, a change person, change time and change content; 3, generating a target chip design data version record according to the change instruction; 4, receiving a version acquisition instruction of the target chip design data; and 5, returning a target version of the target chip design data according to the version acquisition instruction. According to the acquisition method, the historical version of the chip design data can be quickly and conveniently inquired.

Description

Technical Field

[0001] The present invention relates to a chip design data version acquisition method, device, computer equipment and storage medium, belonging to the technical field of data management. Background Art

[0002] When technical R&D personnel are designing a chip system, they will change the design data many times due to the needs of R&D design and test verification, thus generating a large amount of design data.

[0003] At present, the management of the design data life cycle is mostly done by the information system implementing the design data historical version management. For example, it is common to establish a corresponding historical table for each data model. When the data changes, the data before the change can be backed up. Because each data model needs to establish a corresponding historical table, if the data model deletes the data table fields later, the historical table must also be modified accordingly; and in relational data models, there is often a relationship between the main table and the sub-table. If the sub-table also needs to record the change history, then the sub-table also needs a corresponding historical table; resulting in a large amount of data read when querying the historical version of the design data, which greatly occupies data processing resources. Summary of the invention

[0004] In order to solve the above technical problems, the present invention provides a chip design data version acquisition method, device, computer equipment and storage medium, which can quickly and conveniently query the historical versions of chip design data.

[0005] In one aspect, the present invention provides a method for obtaining a chip design data version, comprising:

[0006] Step 1: Create a chip design data management table; the chip design data management table includes an identification code, a change person, a change time, a pre-change extension field, and a post-change extension field; the pre-change extension field is used to store pre-change extension attributes; the post-change extension field is used to store post-change extension attributes;

[0007] Step 2: receiving a change instruction of the target chip design data; the change instruction includes an identification code, a change person, a change time, and a change content;

[0008] Step 3: Generate a target chip design data version record according to the change instruction;

[0009] Step 4: Receive a version acquisition instruction of the target chip design data;

[0010] Step 5: Return the target version of the target chip design data according to the version acquisition instruction.

[0011] The definition and creation of the "chip design data management table" in the present invention application are the same as the logic of the "master data table" in the Chinese invention patent (patent name: Chip design data version acquisition method, device, computer equipment and storage medium, patent application number: CN202310301822.2). Those skilled in the art can create the "master data version management table" in the present invention according to the text content of the aforementioned Chinese invention patent.

[0012] The extended attribute before change is the previous version of the extended attribute after the change operation is performed according to the change instruction; the extended attribute after change is the extended attribute after the change operation is performed according to the change instruction.

[0013] Specifically, in one embodiment, the change content includes the latest full version extended attributes of the target chip design data; the step three includes:

[0014] Acquire the current full version extended attribute of the target chip design data from the chip design data management table according to the identification code;

[0015] Compare the latest full-version extended attributes with the current full-version extended attributes to obtain the extended attributes before and after the change;

[0016] A target chip design data version record is generated according to the identification code, the change person, the change time, the extension field before the change and the extension field after the change.

[0017] Specifically, in one embodiment, the change content includes the target extended attributes of the target chip design data and the modification instructions thereof; the step three includes:

[0018] Acquire the current full version extended attribute of the target chip design data from the chip design data management table according to the identification code;

[0019] Compare the target extended attribute and its modification instruction with the current full version extended attribute to obtain the extended attribute before change and the extended attribute after change;

[0020] A target chip design data version record is generated according to the identification code, the change person, the change time, the extension field before the change and the extension field after the change.

[0021] Specifically, in one embodiment, the change content includes the target extended attribute of the target chip design data and its deletion instruction; the step three includes:

[0022] According to the target extended attribute and its deletion instruction, the extended attribute before change and the extended attribute after change are obtained; the extended attribute after change is empty;

[0023] A target chip design data version record is generated according to the identification code, the change person, the change time, the extension field before the change and the extension field after the change.

[0024] Specifically, in one embodiment, the change content includes the target extended attributes of the target chip design data and the newly added instructions thereof, and the step three includes:

[0025] According to the target extended attribute and the newly added instruction, the extended attribute before the change and the extended attribute after the change are obtained; the extended attribute before the change is empty;

[0026] A target chip design data version record is generated according to the identification code, the change person, the change time, the extension field before the change and the extension field after the change.

[0027] In another aspect, the present invention provides a device for obtaining chip design data version, comprising:

[0028] A creation unit, used to create a chip design data management table; the chip design data management table includes an identification code, a change person, a change time, a pre-change extension field and a post-change extension field; the pre-change extension field is used to store pre-change extension attributes; the post-change extension field is used to store post-change extension attributes;

[0029] A first receiving unit is used to receive a change instruction of the target chip design data; the change instruction includes an identification code, a change person, a change time and a change content;

[0030] A generating unit, used for generating a target chip design data version record according to the change instruction;

[0031] A second receiving unit, configured to receive a version acquisition instruction for target chip design data;

[0032] The returning unit is used to return the target version of the target chip design data according to the version acquisition instruction.

[0033] On the other hand, the present invention provides a computer device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the chip design data version acquisition method as described above when executing the computer program.

[0034] On the other hand, the present invention provides a computer-readable storage medium, characterized in that the computer-readable storage medium stores one or more computer programs, and the one or more computer programs can be executed by one or more processors to implement the chip design data version acquisition method as described above.

[0035] The beneficial effects of the present invention are: through the master data model, a chip design data management table is defined, and the changes in the master data are stored with the help of the flexibility of the extended field; different types of master data change histories can be stored, which is convenient for analyzing the differences before and after the chip design data changes; after obtaining the content of the execution of the change instruction, it is possible to obtain the historical version information of the specific time point, the change person and the specific chip design data.

[0036] The present invention is further described below in conjunction with the accompanying drawings and specific embodiments. BRIEF DESCRIPTION OF THE DRAWINGS

[0037] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the accompanying drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are some embodiments of the present invention. For ordinary technicians in this field, other accompanying drawings can be obtained based on these accompanying drawings without paying any creative work.

[0038] Figure 1 A schematic flow chart of a method for obtaining chip design data version provided by an embodiment of the present invention;

[0039] Figure 2 This is one of the sub-schematic flow charts of the method for obtaining chip design data version according to an embodiment of the present invention;

[0040] Figure 3 A schematic block diagram of a device for obtaining chip design data version provided by an embodiment of the present invention;

[0041] Figure 4 A schematic diagram of the structural composition of a computer device provided in an embodiment of the present invention. DETAILED DESCRIPTION

[0042] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0043] It should be understood that when used in this specification and the appended claims, the terms "include" and "comprises" indicate the presence of described features, integers, steps, operations, elements and / or components, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components and / or combinations thereof.

[0044] It should also be understood that the terms used in this specification of the present invention are only for the purpose of describing specific embodiments and are not intended to limit the present invention. As used in the specification of the present invention and the appended claims, unless the context clearly indicates otherwise, the singular forms "a", "an" and "the" are intended to include plural forms.

[0045] It should be further understood that the term "and / or" used in the present description and the appended claims refers to any and all possible combinations of one or more of the associated listed items, and includes these combinations.

[0046] Example

[0047] An embodiment of the present application provides a chip design data version acquisition method for managing chip system design data, wherein the database providing data storage may be a mainstream OLTP relational database such as Oracle, Sql Server, Mysql, PostgreSQL, etc.; in addition, the executor of the method may be a computer, server, or other device, which is not limited in this embodiment.

[0048] See also Figure 1 , Figure 1 The following is a schematic flow chart of a method for obtaining a chip design data version according to an embodiment of the present invention. Figure 1 As shown, a method for obtaining chip design data version specifically includes the following steps S1-S5:

[0049] S1, step one: create a chip design data management table; the chip design data management table includes an identification code, a change person, a change time, an extension field before the change, and an extension field after the change; the extension field before the change is used to store extension attributes before the change; the extension field after the change is used to store extension attributes after the change.

[0050] The content of the chip design data management table is specifically set according to the actual application scenario and exists in various forms. For example, the embodiment of the present application creates a chip design data management table as shown in Table 1 below, including an identification code, a change person, a change time, a first extension field, and a second extension field; wherein the first extension field is used to store the extended attributes of the chip design data before the change, and the second extension field is used to store the extended attributes of the chip design data after the change.

[0051] Table 1

[0052] Identification code Change of personnel Change time First extension field Second extension field

[0053] S2, step 2: receiving a change instruction of the target chip design data; the change instruction includes an identification code, a change person, a change time and a change content.

[0054] For example, in combination with the contents of Table 1, in an embodiment of the present application, the change instruction 1 (as shown in Table 2) includes the identification code of the target chip design data, the change person, the change time and the latest full version extended attributes of the target chip design data.

[0055] As shown in Table 2, the specific content of change instruction 1 is: Zhang San changed the target chip design data "A01" at 2023-10-18 16:30:00. After the change, the target chip design data "A01" has four extended attributes, namely: the metadata name is "code 1" and the value is "X"; the metadata name is "code 2" and the value is "Y".

[0056] Table 2

[0057]

[0058] In other embodiments, the change instruction includes the identification code of the target chip design data, the change person, the change time, the target extended attributes of the target chip design data and its modification instructions; or; the change instruction includes the identification code of the target chip design data, the change person, the change time, the target extended attributes of the target chip design data and its deletion instructions; or; the change instruction includes the identification code of the target chip design data, the change person, the change time, the target extended attributes of the target chip design data and its addition instructions.

[0059] S3, step three: generating a target chip design data version record according to the change instruction.

[0060] For the purpose of illustration, and in combination with the contents of Table 1 and Table 2, in an embodiment of the present application, the processor receives change instruction 1; the specific content of change instruction 1 is: Zhang San changed the target chip design data "A01" at 2023-10-18 16:30:00. After the change, the target chip design data "A01" has two extended attributes, namely: the metadata name is "code 1" and the value is "X"; the metadata name is "code 2" and the value is "Y".

[0061] See also Figure 2 , step S3 includes the following specific steps:

[0062] S31 obtains the current full version extended attribute of the target chip design data from the chip design data management table according to the identification code.

[0063] After the processor receives the change instruction 1, it searches the chip design data management table according to the identification code "A01" to see whether the target chip design data "A01" has a change history. If not, it means that the target master data "A01" is created for the first time, that is, the current full version extended attribute is empty.

[0064] S32 compares the latest full version extended attributes with the current full version extended attributes to obtain the extended attributes before and after the change. Since the current full version extended attributes of the target chip design data "A01" are empty, the extended attributes before the change are empty. The extended attributes after the change are the two extended attributes in the change instruction 1:

[0065] [{"fieldName":"Code 1","extra":{"dataValue":"X"}},

[0066] {"fieldName":"Code2","extra":{"dataValue":"Y"}}].

[0067] S33 generates a target chip design data version record according to the identification code, change personnel, change time, pre-change extension field and post-change extension field.

[0068] At this time, the chip design data management table after executing change instruction 1 is as shown in Table 3.

[0069] Table 3

[0070]

[0071] Of course, the execution steps will be adjusted accordingly according to the content of the change instruction. For the purpose of illustration, the following example is given in conjunction with the content of Table 3.

[0072] After executing change instruction 1, the processor receives change instruction 2; the specific content of change instruction 2 is: Zhang San changed the chip design data "A01" at 2023-11-02 15:00:00; the change content is: add a new extended attribute: the metadata name is "code 3" and the value is "Z". See Table 4 below for details.

[0073] Table 4

[0074]

[0075]

[0076] Execute change instruction 2. At this time, the extended attribute before the change is "empty", and the extended attribute after the change is the target extended attribute "{"fieldName":"Code 3","extra":{"dataValue":"Z"}}".

[0077] At this time, the chip design data management table after executing change instruction 2 is as shown in Table 5.

[0078] Table 5

[0079]

[0080] After executing change instruction 2, the processor receives change instruction 3; the specific content of change instruction 3 is: Zhang San changed the master data "A01" at 2023-12-04 18:00:00; the change content is: delete the extended attribute: the metadata name is "code 3" and the value is "Z". See Table 4 below for details.

[0081] Table 6

[0082]

[0083] Execute change instruction 3. At this time, the extended attribute before the change is the target extended attribute "{"fieldName":"Code 3","extra":{"dataValue":"Z"}}", and the extended attribute after the change is "empty".

[0084] At this time, the master data version management table after executing change instruction 3 is as shown in Table 7.

[0085] Table 7

[0086]

[0087] After executing change instruction 3, the processor receives change instruction 4; the specific content of change instruction 4 is: Zhang San changed the chip design data "A01" at 2023-12-23 14:00:00; the change content is: modify the value of the extended attribute metadata name "code 2" to "R". See Table 8 below for details.

[0088] Table 8

[0089]

[0090] Execute change instruction 4. At this time, the extended attribute before the change is the target extended attribute "{"fieldName":"Code 2","extra":{"dataValue":"Y"}}", and the extended attribute after the change is "{"fieldName":"Code 2","extra":{"dataValue":"R"}}".

[0091] At this time, the chip design data version management table after executing change instruction 4 is as shown in Table 9.

[0092] Table 9

[0093]

[0094]

[0095] Afterwards, the processor receives change instruction 5; the specific content of change instruction 5 is: Li Si changed the chip design data "A01" at 2024-01-30 20:00:00; the change content is:

[0096] a) Add a new extended attribute: metadata name is "code4", value is "W";

[0097] b) Modify the extended attribute of the existing metadata named "Code 1" and change the value to "T";

[0098] c) Delete the extended attribute with the metadata name "Code 2". See Table 10 below for details.

[0099] Table 10

[0100]

[0101] After receiving the change instruction 5, the processor still searches for the change record of the target chip design data with the identification code "A01" in the chip design data version management table, sorts the found change records in ascending order by change time, and processes them one by one from early to late to obtain the latest version Vn of the master data. The specific process is as follows:

[0102] 1. Set the extended attribute of the second extended field of the first change record as version V1;

[0103] 2. Take the contents of the first and second extension fields of the second change record, and overwrite the extended attributes of the second extension field with the V1 version according to the metadata name: if the V1 version does not have an extended attribute with the metadata name, then it is a newly added extended attribute, and it is appended; if V1 has an extended attribute with the same metadata name, then the value of the second extension field is updated; if the first extension field already has an extended attribute, but the second extension field does not, it means that the extended attribute was deleted during the second change, then the extended attribute with the same metadata name in the V1 version is removed, and finally the V2 version is obtained;

[0104] 3. Similarly, for the third change record, the contents of the first extension field and the second extension field of the second change record are also taken out, and processed in combination with version V2 to obtain version V3.

[0105] 4. This process is repeated in this way until the change history of the target chip design data "A01" is traversed and the latest version Vn is obtained.

[0106] Compare the extended attributes of the Vn version with those of the change instruction 5 to obtain the extended attributes before and after the change. The specific process is as follows:

[0107] First, from the above example, the target chip design data "A01" has four change histories, so the content of the latest full version extended attribute is:

[0108] [{"fieldName":"Code 1","extra":{"dataValue":"X"}},

[0109] {"fieldName":"Code 2","extra":{"dataValue":"R"}}]

[0110] The extended attributes in change instruction 5 are:

[0111] [{"fieldName":"Code 4","extra":{"dataValue":"W"}},

[0112] {"fieldName":"Code 1","extra":{"dataValue":"T"}}]

[0113] Through comparison, the following conclusions are drawn:

[0114] 1. The extended attribute with the metadata name "Code 4" is present in the change instruction but not in the Vn version, indicating that the extended attribute is newly added in this change, so it is stored in the second extended field of the chip design data version management table; the extended attribute does not exist in the corresponding first extended field.

[0115] 2. The extended attribute with the metadata name "Code 1" exists in both the change instruction and the Vn version, but its value is different, indicating that this change has modified the extended attribute. Therefore, the extended attribute in the Vn version is stored in the first extended field of the chip design data version management table, and the extended attribute in the change instruction is stored in the second extended field of the chip design data version management table.

[0116] 3. The extended attribute with the metadata name "Code 2" is not included in the change instruction but is included in the Vn version, indicating that the extended attribute has been deleted in this change. Therefore, it is stored in the first extended field of the chip design data version management table; the extended attribute does not exist in the corresponding second extended field.

[0117] After comparison, the extended attributes that need to be stored in the first extended field and the second extended field are obtained, and a new change record is created in the chip design data version management table as shown in Table 11.

[0118] Table 11

[0119]

[0120]

[0121] It can be seen from the fifth change record in the chip design data version management table that Li Si only changed the extended attributes corresponding to the three metadata "code 1", deleted "code 2", and added "code 4", and other extended attributes were not changed. Therefore, the historical record only needs to contain the extended attributes related to this change, and other extended attributes do not need to be stored redundantly. If the chip design data has dozens or hundreds of extended attributes, it can greatly save the historical record storage space.

[0122] At the same time, when retrieving a change record, you can intuitively see the difference of this change, such as the content of the fifth change of the target chip design data "A01":

[0123] Metadata for both the first and second extension fields, indicating that the value has changed, "Code 1 Color" from "X" -> "T";

[0124] The metadata of the first extension field exists but the second extension field does not exist indicates that this change has been deleted, "Code 2" -> None

[0125] The metadata of the first extended attribute not existing and the second extended attribute existing indicates that the extended attribute is newly added this time. None -> "Code 4" is "W".

[0126] S4, step four: receiving a version acquisition instruction of the target chip design data.

[0127] The specific content of the version acquisition instruction is set according to specific needs.

[0128] S5, step five: returning the target version of the target chip design data according to the version acquisition instruction.

[0129] According to the specific content of the version acquisition instruction, the query and return of the target version of the target chip design data are realized.

[0130] For example, combined with the above content, if you want to get the change history of the metadata named "code 1" in the target chip design data "A01", you only need to query the chip design data version management table according to the target chip design data code "A01". If there is a change record with the metadata named "code 1" in the first extension field or the metadata named "code 1" in the second extension field, it is all the change history of the metadata. According to the specific content of the version acquisition instruction, you can specify to return a specific version of the target chip design data.

[0131] See also Figure 3Corresponding to the chip design data version acquisition method described above, an embodiment of the present invention further proposes a chip design data version acquisition device 100, the device 100 includes: a creation unit 110, a first receiving unit 120, a generation unit 130, a second receiving unit 140 and a return unit 150.

[0132] The creation unit 110 is used to create a chip design data management table; the chip design data management table includes an identification code, a change person, a change time, a pre-change extension field, and a post-change extension field; the pre-change extension field is used to store pre-change extension attributes; the post-change extension field is used to store post-change extension attributes;

[0133] The first receiving unit 120 is used to receive a change instruction of the target chip design data; the change instruction includes an identification code, a change person, a change time and a change content;

[0134] A generating unit 130, configured to generate a target chip design data version record according to the change instruction;

[0135] The second receiving unit 140 is used to receive a version acquisition instruction of the target chip design data;

[0136] The returning unit 150 is configured to return the target version of the target chip design data according to the version acquisition instruction.

[0137] The above-mentioned chip design data version acquisition device 100 corresponds one-to-one to the above-mentioned chip design data version acquisition method. Its specific principles and processes are the same as those of the method described in the above embodiment, and will not be repeated herein.

[0138] Similarly, in other embodiments, according to different specific application scenarios and corresponding to specific chip design data version acquisition methods, the chip design data acquisition device 100 also includes corresponding units.

[0139] Figure 4 The present invention is a schematic diagram of the structure of a computer device. The device can be a terminal or a server, wherein the terminal can be a smart phone, a tablet computer, a laptop or a desktop computer. The server can be an independent server or a server cluster composed of multiple servers.

[0140] See also Figure 4The computer device 500 includes a processor 502, a non-volatile storage medium 503, an internal memory 504 and a network interface 505 connected via a system bus 501. The non-volatile storage medium 503 of the computer device 500 can store an operating system 5031 and a computer program 5032. When the computer program 5032 is executed, the processor 502 can execute a chip design data version acquisition method. The processor 502 of the computer device 500 is used to provide computing and control capabilities to support the operation of the entire computer device 500. The internal memory 504 provides an environment for the operation of the computer program 5032 in the non-volatile storage medium 503. When the computer program is executed by the processor, the processor 502 can execute a chip design data version acquisition method. The network interface 505 of the computer device 500 is used for network communication. Those skilled in the art can understand that Figure 4 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0141] The processor 502 is used to run the computer program stored in the memory 504 to implement the above-mentioned chip design data version acquisition method.

[0142] It should be understood that in the embodiment of the present application, the processor 502 may be a central processing unit (CPU), and the processor may also be other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc.

[0143] The present invention also provides a computer-readable storage medium, which stores one or more computer programs. The one or more computer programs can be executed by one or more processors to implement the above-mentioned chip design data version acquisition method.

[0144] The aforementioned storage medium of the present invention includes: a magnetic disk, an optical disk, a read-only memory (ROM) and other media that can store program codes.

[0145] The units in all embodiments of the present invention can be implemented by a general purpose integrated circuit, such as a CPU (Central Processing Unit).

[0146] The CPU may be implemented by a central processing unit (CPU), or by an ASIC (Application Specific Integrated Circuit).

[0147] The above is only a specific embodiment of the present invention, but the protection scope of the present invention is not limited thereto. Any technician familiar with the technical field can easily think of various equivalent modifications or replacements within the technical scope disclosed by the present invention, and these modifications or replacements should be included in the protection scope of the present invention. Therefore, the protection scope of the present invention shall be based on the protection scope of the claims.

Claims

1. A method for obtaining a chip design data version, characterized in that: include: Step 1: Create a chip design data management table; The chip design data management table includes an identification code, a changer, a change time, an extension field before the change, and an extension field after the change; The before-change extension field is used to store the before-change extension attribute; The post-change extension field is used to store the post-change extension attribute; Step 2: receiving a change instruction of the target chip design data; the change instruction includes an identification code, a change person, a change time, and a change content; Step 3: Generate a target chip design data version record according to the change instruction; Step 4: Receive a version acquisition instruction of the target chip design data; Step 5: Return the target version of the target chip design data according to the version acquisition instruction.

2. The chip design data version acquisition method according to claim 1, characterized in that: The change content includes the latest full version extended attributes of the target chip design data; The step three comprises: Acquire the current full version extended attribute of the target chip design data from the chip design data management table according to the identification code; Compare the latest full-version extended attributes with the current full-version extended attributes to obtain the extended attributes before and after the change; A target chip design data version record is generated according to the identification code, the change person, the change time, the extension field before the change and the extension field after the change.

3. The chip design data version acquisition method according to claim 1, characterized in that: The change content includes target extended attributes of target chip design data and modification instructions thereof; The step three comprises: Acquire the current full version extended attribute of the target chip design data from the chip design data management table according to the identification code; Compare the target extended attribute and its modification instruction with the current full version extended attribute to obtain the extended attribute before change and the extended attribute after change; A target chip design data version record is generated according to the identification code, the change person, the change time, the extension field before the change and the extension field after the change.

4. The chip design data version acquisition method according to claim 1, characterized in that: The change content includes the target extended attributes of the target chip design data and the deletion instruction thereof; The step three comprises: According to the target extended attribute and its deletion instruction, the extended attribute before change and the extended attribute after change are obtained; the extended attribute after change is empty; A target chip design data version record is generated according to the identification code, the change person, the change time, the extension field before the change and the extension field after the change.

5. The chip design data version acquisition method according to claim 1, characterized in that: The change content includes the target extended attributes of the target chip design data and the newly added instructions thereof. The step three includes: According to the target extended attribute and the newly added instruction, the extended attribute before the change and the extended attribute after the change are obtained; the extended attribute before the change is empty; A target chip design data version record is generated according to the identification code, the change person, the change time, the extension field before the change and the extension field after the change.

6. A device for obtaining chip design data version, characterized in that: include: A creation unit, used for creating a chip design data management table; The chip design data management table includes an identification code, a change person, a change time, an extension field before the change, and an extension field after the change; The before-change extension field is used to store the before-change extension attribute; The post-change extension field is used to store the post-change extension attribute; A first receiving unit is used to receive a change instruction of the target chip design data; the change instruction includes an identification code, a change person, a change time and a change content; A generating unit, used for generating a target chip design data version record according to the change instruction; A second receiving unit, configured to receive a version acquisition instruction for target chip design data; The returning unit is used to return the target version of the target chip design data according to the version acquisition instruction.

7. A computer device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the method for obtaining the chip design data version as described in any one of claims 1 to 5 is implemented.

8. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores one or more computer programs, and the one or more computer programs can be executed by one or more processors to implement the chip design data version acquisition method as described in any one of claims 1-5.

Images