A security policy-based component packaging model data management method

Abstract

The application belongs to the field of component packaging model data management, and discloses a component packaging model data management method based on a security strategy. The method comprises the following steps: updating the index of the corresponding PCB packaging in the temporary packaging history table according to the modification of the PCB temporary library, wherein the index comprises library information records and library life cycles; uploading the updated temporary packaging history table; updating the original formal packaging history table with the updated temporary packaging history table to obtain a new formal packaging history table; judging whether there is PCB packaging that needs to be added to the PCB formal library or the PCB unverified library in the PCB temporary library according to the library life cycle of the new formal packaging history table; and judging whether there is PCB packaging that needs to be added to the PCB formal library in the PCB unverified library. The application realizes automatic uploading, checking and error reporting output work, reduces manual operation, and greatly improves management efficiency and correctness.

Description

Technical Field

[0001] This invention belongs to the field of component packaging model data management, and discloses a component packaging model data management method based on security strategy. Background Technology

[0002] Packaging is the basic unit of PCB design. All components in a PCB have their own packaging. A single packaging error can cause problems in the entire design or even scrap the product, wasting a lot of costs.

[0003] The industry standard for PCB package model data management is a linear structure, where a single-level index maps to a package library, and the index itself is the library's information record. This management method can lead to unverified packages being used by multiple products, posing significant security risks. Furthermore, the package model data management integrated into the system requires manual input, rather than direct extraction from the physical library, making it susceptible to human error.

[0004] With the development of the electronics industry, components are becoming increasingly integrated and miniaturized, and the types of components are also becoming more and more diverse, resulting in a huge amount of data. The traditional management method of one index plus one package library has greatly increased the probability of errors, and manual management is very difficult. The management method of package model data urgently needs to be improved. Summary of the Invention

[0005] The purpose of this invention is to provide a component packaging model data management method based on security strategies, so as to improve the security of packaging model data and reduce the risk of errors in packaging model data management.

[0006] To achieve the above objectives, the present invention adopts the following implementation scheme:

[0007] This invention provides a method for managing component packaging model data based on a security policy, the method comprising:

[0008] Based on the modifications to the PCB temporary library, update the index of the corresponding PCB package in the temporary package history table. The index includes library information and library lifecycle.

[0009] Upload the updated temporary encapsulation resume;

[0010] Update the original formal packaging history table with the updated temporary packaging history table to obtain the new formal packaging history table.

[0011] Based on the library lifecycle of the new formal package history, determine whether there are PCB packages in the temporary PCB library that need to be added to the formal PCB library or the unverified PCB library, and determine whether there are PCB packages in the unverified PCB library that need to be added to the formal PCB library.

[0012] The original formal packaging history table is updated with the updated temporary packaging history table to obtain the new formal packaging history table, which includes:

[0013] Determine if the indexes of each PCB package in the new formal package history table are correct;

[0014] If any information in the index of a PCB package is incorrect, the error will be added to the error report, indicating that the information of the PCB package is incorrect, and the index of the PCB package in the new formal package history table will be replaced with the index of the PCB package in the original formal package history table.

[0015] If the PCB package is a newly added PCB package, then delete the entry for that PCB package in the new formal package history table.

[0016] The method further includes:

[0017] Received a query command for querying a library information or a lifecycle of a target PCB package; the target PCB package is a PCB package of a formal library or a PCB package of an unverified library.

[0018] Based on the query command, retrieve the relevant information for the target PCB from the latest official packaging history table.

[0019] This security strategy is a results-oriented rather than process-oriented data security strategy.

[0020] The security policy includes two indexing methods: library information and library lifecycle.

[0021] The library information includes records of material codes, data sheets, specifications, models, package names, PCB package names, and manufacturers;

[0022] The library lifecycle includes records of the creation time and the effective time of the encapsulation.

[0023] The security policy includes three types of entity libraries: PCB official library, PCB unverified library, and PCB temporary library;

[0024] The PCB official library is a package model that has been verified to be problem-free. The package history table contains a complete library lifecycle record and a record of the required library information. It is widely used in all products.

[0025] Unverified PCB library: Unverified package models, package history records have no package effective time, complete the required library information records, and use in products during the small-scale verification phase.

[0026] The PCB temporary library contains unverified package models. The temporary package history record does not include the package activation time. It is a mandatory library information record and cannot be used in the product. It is only used in the library creation stage.

[0027] The system sets up a packaging history table and a temporary packaging history table, each containing a library information record section and a library lifecycle record section, respectively. Its key feature is that it includes:

[0028] The specific forms of the packaging history table and the temporary packaging history table are divided into device packaging comparison table and packaging registration table, or other forms.

[0029] The library information also includes packaging library information at different stages in the three entity libraries, packaging model information, including device height, size, number of pins, and PCB package name information.

[0030] Error report output methods include:

[0031] By utilizing the encapsulated model data management device, various possible scenarios can be checked;

[0032] Categorize and output error reports, creating a document;

[0033] Adding and modifying data information for the encapsulated model without issues.

[0034] Beneficial effects:

[0035] The widespread use of defective packages can render products unusable, making PCB package management a top priority in the industry. This invention establishes three libraries at different stages: a temporary PCB library, an unverified PCB library, and a final PCB library. This allows for phased and layered management of PCB packages, significantly reducing the problem of defective packages being used extensively, minimizing cost waste, and resulting in substantial economic benefits.

[0036] The result-oriented data security strategy proposed in this invention retains both the original data and the data to be updated, ensuring that the final output of the new formal packaged resume is correct. It will not cause errors in the final output of the new formal packaged resume due to errors in the temporary packaged resume or human error, thus reducing the security risks of data management.

[0037] Since there are generally thousands of encapsulated libraries, the workload is enormous. The management tool provided by this invention can perform operations such as adding, modifying, deleting, and checking for various different scenarios, reducing human error, saving management time, and saving time costs. Attached Figure Description

[0038] Figure 1 A flowchart for encapsulating model data management for two indexes and three entity libraries.

[0039] Figure 2 This is a diagram illustrating error types. Detailed Implementation

[0040] The present invention will now be described in detail with reference to the accompanying drawings and specific embodiments. It should be understood that the embodiments described below are only for illustration and explanation of the present invention and are not intended to limit the present invention.

[0041] This invention provides a novel encapsulated model data management structure, a two-index plus three-entity database pattern, including:

[0042] Two types of tables are created: a temporary packaging history table and a formal packaging history table. Both tables include two indexing methods: library information and library lifecycle.

[0043] Three types of entity libraries are established: a temporary PCB library, an unverified PCB library, and a formal PCB library, corresponding to the three stages of the package model:

[0044] The PCB official library contains verified and problem-free packaging models. The packaging history table contains complete library lifecycle records and required library information records, which can be used extensively in all products.

[0045] Unverified PCB library contains unverified package models. The package history record has no package effective time in the library lifecycle record. Complete the required library information records. It can be used in products during the small-scale verification stage.

[0046] The PCB temporary library contains unverified package models. The temporary package history record does not have the package effective time in the library lifecycle record. It is a required library information record and cannot be used in the product. It is only used in the library construction stage.

[0047] In a preferred embodiment of the present invention, the encapsulation model data management step includes:

[0048] Complete the modification of the PCB temporary library, including adding and modifying the package model;

[0049] Extract information such as the size, height, and pad size of the package model from the PCB temporary library, and complete the filling of library information and library lifecycle in the temporary package history table;

[0050] Depending on the scenario, move the package model from the temporary PCB library to the unverified PCB library or the official PCB library, and update the official package history information.

[0051] Figure 1 The flowchart of the data management process for the encapsulated model of this invention is shown, including the following steps:

[0052] Step S101 extracts PCB package data information from the temporary PCB library, including PCB package name, size, height, etc. It then compares each extracted PCB package name with the PCB package information in the temporary package history table's library information index to determine if the PCB package name exists in both the temporary PCB library and the temporary package history table's library information index. The result is one of three possible outcomes:

[0053] S101 Result 1: If the PCB package name exists in both the PCB temporary library and the temporary package history table's library information index, it is determined to be a PCB package modification or addition, and proceed to the next level of judgment.

[0054] S101 Result 2: The PCB package name exists only in the library information index of the temporary history table, but does not exist in the PCB temporary library. It is determined that the information needs to be updated. The PCB package has no change, so proceed to the next level of judgment.

[0055] S101 Result 3: The PCB package name exists only in the PCB temporary library and does not exist in the library information index of the temporary history table. The judgment information is incomplete and will not be updated.

[0056] Step S102,

[0057] When S101 result 1 is obtained, check if there is a number in the library information index of the temporary history table, and get the following two results:

[0058] S102 Result 1: There is no number in the library information index of the temporary history table, so it is determined to be a newly added package and proceed to the next level of judgment;

[0059] S102 Result 2: The temporary history table has a number in the library information index, which indicates that the PCB package has been modified. Proceed to the next level of judgment.

[0060] When S101 result 2 is obtained, check whether the encapsulation effective time in the library lifecycle index of the original formal encapsulation history table and the encapsulation effective time in the library lifecycle index of the temporary history table are filled in. The following two operations are to be executed:

[0061] Operation 5 to be executed: If the package effective time is not filled in the library lifecycle index of the original formal package history table, but the package effective time is filled in the library lifecycle index of the temporary history table, the package effective time is determined to be newly added. The PCB package should be moved from the PCB unverified library to the PCB formal library. Check the library information index and other information in the library lifecycle index of the updated temporary package history table. If there are no errors, update the original formal package history table with the updated temporary package history table. If there are errors, replace the index of the PCB package in the new formal package history table with the index of the PCB package in the original formal package history table.

[0062] Operation 6 to be executed: If the effective time of the package in the library lifecycle index of the original formal package history table and the effective time of the package in the library lifecycle index of the temporary history table are both filled in, it is determined that the effective time of the package is not newly added. Check the library information index and other information in the library lifecycle index of the updated temporary package history table. If there are no errors, update the original formal package history table with the updated temporary package history table. If there are errors, replace the index of the PCB package in the new formal package history table with the index of the PCB package in the original formal package history table.

[0063] When S102 result 1 is obtained, check whether the encapsulation effective time is filled in the library lifecycle index of the temporary history table, and obtain the following two operations to be executed:

[0064] Operation 1 to be executed: The effective time of the package has been filled in the library lifecycle index of the temporary package history table. It is determined that the corresponding PCB package is newly added and has been verified. The corresponding PCB package in the temporary PCB library should be moved to the formal PCB library. Check the library information index and other information in the library lifecycle index of the updated temporary package history table. If there are no errors, add the index of the corresponding PCB package in the updated temporary package history table to the new formal package history table. If there are errors, the index of the corresponding PCB package will not be added to the new formal package history table.

[0065] Operation 2 to be executed: The effective time of the package is not filled in the library lifecycle index of the temporary package history table. It is determined that the corresponding PCB package is newly added but not verified. The corresponding PCB package in the temporary PCB library should be entered into the unverified PCB library. Check the library information index and other information in the library lifecycle index of the updated temporary package history table. If there are no errors, add the corresponding PCB package index of the updated temporary package history table to the new formal package history table. If there are errors, the new formal package history table will not add the corresponding PCB package index.

[0066] When S102 result 2 is obtained, check whether the encapsulation effective time is filled in the library lifecycle index of the temporary history table, and obtain the following two operations to be executed:

[0067] Operation 3 to be executed: The effective time of the package has been filled in the library lifecycle index of the temporary package history table. It is determined that the modified PCB package has been verified. Move the corresponding package in the PCB temporary library into the PCB formal library to replace the original package. Check the library information index and other information in the library lifecycle index of the updated temporary package history table. If there are no errors, update the original formal package history table with the updated temporary package history table. If there are errors, replace the index of the PCB package in the new formal package history table with the index of the PCB package in the original formal package history table.

[0068] Operation 4 to be executed: The effective time of the package is not filled in the library lifecycle index of the temporary package history table. It is determined that the PCB package in the unverified PCB library has been modified. Move the corresponding package in the temporary PCB library into the unverified PCB library and replace the original package. Check the library information index and other information in the library lifecycle index of the updated temporary package history table. If there are no errors, update the original formal package history table with the updated temporary package history table. If there are errors, replace the index of the PCB package in the new formal package history table with the index of the PCB package in the original formal package history table.

[0069] Execute the pending operations obtained in the previous step, output the integrated new formal packaging history table, update the PCB formal library and PCB unverified library to obtain the updated PCB formal library and PCB unverified library, perform a second verification check on the integrated new formal packaging history table and the updated PCB formal library and PCB unverified library, and output an error report.

[0070] If there are any errors, update and modify the error information in the PCB temporary library and temporary package history table, and then repeat the above steps until there are no errors.

[0071] Release the integrated new official package history, official PCB library, and unverified PCB library.

[0072] The above operations of extracting entity library encapsulation information, judging, verifying and updating history information are all implemented by the automatic update and inspection device provided by this invention, reducing manual operation;

[0073] The specific process for data verification is as follows:

[0074] Extract the PCB official library and PCB unverified library package model data, check the consistency with the data to be updated using the management device provided by this invention, check the correctness of the library information record and library lifecycle record data in the data to be updated, and output an error report.

[0075] Error report types such as Figure 2 This includes the following scenarios:

[0076] Scenario 1: Formal design library encapsulation consistency check; if there is a mismatch, an error is determined, and a corresponding entry is added to the error report;

[0077] Scenario 2: Unverified design library encapsulation consistency check. If there is a mismatch, an error is judged and a corresponding entry is added to the error report;

[0078] Scenario 3: Material number uniqueness check. If the number is duplicated, an error is judged and a corresponding entry is added to the error report;

[0079] Scenario 4: Specification uniqueness check, duplicate specifications, error judgment, add corresponding entry to error report;

[0080] Scenario 5: Formal encapsulation associated date check, that is, check whether the encapsulation effective time in the library lifecycle record is filled in. If not filled in, it is judged as an error, and the corresponding entry is added to the error report;

[0081] Scenario 6: Unverified encapsulation associated date check, i.e., check whether the encapsulation effective time in the library lifecycle record is filled in. If it is filled in, it is judged as an error, and the corresponding entry is added to the error report.

[0082] The above description is merely a specific embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. All data security strategies using the encapsulation model of the present invention should be covered within the scope of protection of the present invention.

Claims

1. A method for managing component packaging model data based on security policies, characterized in that, The security strategy is implemented through two sets of indexes: library information index and library lifecycle index, as well as three physically isolated entity libraries: PCB temporary library, PCB unverified library, and PCB formal library. The library lifecycle index includes at least the package creation time and package activation time. The method includes the following steps: S1. Create or modify the package model in the PCB temporary library; S2. Based on the modifications to the PCB temporary library, extract the library information and library lifecycle information of the corresponding package model, and update a temporary package history table. S3. The updated temporary packaging history table is compared and merged with an original formal packaging history table to generate a new formal packaging history table; wherein, during the processing, the data information of the updated temporary packaging history table and the original formal packaging history table are retained in the management device. S4. During the comparison and merging process, based on the library lifecycle index of each record in the temporary encapsulation history table, the flow judgment and operation of the encapsulation model between the three entity libraries are automatically executed, including: S41. If the encapsulation effective time is filled in the library lifecycle index of a certain record, then it is determined that the corresponding encapsulation model should be moved from the PCB temporary library or the PCB unverified library to the PCB formal library. S42. If the encapsulation effective time is not filled in the library lifecycle index of a certain record, and it is a newly added record, then it is determined that the corresponding encapsulation model should be moved from the PCB temporary library to the PCB unverified library. S43. If the effective time of the package is not filled in the library lifecycle index of a certain record, and it is a modified record, then it is determined that the corresponding package model should be updated and replaced in the PCB unverified library. S5. Based on the flow judgment, synchronously update the actual packaging model data in the PCB official library and the PCB unverified library, and publish the new official packaging history table.

2. The method according to claim 1, characterized in that, The comparison and merging process in step S3 further includes: S31. Determine whether the index information of each PCB package in the new formal packaging history table is correct; S32. If any index information of a PCB package is incorrect, the error information will be added to the error report, and the index in the new formal package history table will be replaced with the index of the corresponding PCB package in the original formal package history table. S33. If it is determined that a certain PCB package is an entry that should not be added, then delete its record in the new formal package history table.

3. The method according to claim 1 or 2, characterized in that, The method also includes a query step: Receive a query command for library information or library lifecycle of a target PCB package, wherein the target PCB package is located in the official PCB library or the unverified PCB library; Based on the query command, the system queries and returns the information corresponding to the target PCB package in the latest officially released package history table.

4. The method according to claim 1, characterized in that, The library information index includes records of material codes, datasheets, specifications, models, package names, PCB package names, and manufacturers.

5. The method according to claim 1, characterized in that, The definitions of the three entity libraries are as follows: PCB Official Library: A repository of fully indexed and verified package models that can be used in all product designs; Unverified PCB Library: A package model with an empty package effective time in the repository lifecycle index and complete required library information. It can only be used in product designs during a small-scale verification phase. PCB Temporary Library: A package model with an empty effective time in the repository lifecycle index and complete required library information. It is only used in the creation and modification stage of the package model and cannot be used in any product design.

6. The method according to claim 1, characterized in that, The automatic checks performed by the management device include one or more of the following scenarios: consistency check between the physical library and the record in the logbook, uniqueness check of the material number, uniqueness check of the specification, check of the date associated with the formal library packaging, and check of the date associated with the unverified library packaging; and output error reports according to the check results.

Images