Management and updating method for optimizing device packaging automation

Abstract

The invention relates to a management and updating method for optimizing device packaging automation. The method comprises the steps of deploying a centralized packaging database, binding packaging information with a packaging file of EDA software, establishing a synchronization mechanism and a notification system, automatically updating a state log record and introducing a third-party auditing mechanism. According to the method, the centralized device packaging database is created, so that a library engineer can quickly write the packaging information into the device packaging database, and the device packaging information is conveniently created and uploaded; a design engineer can obtain the encapsulation updating information in time and synchronously update the design manuscript; the process of each node is recorded in detail, and the process record is convenient to search, so that the problems of low efficiency, high communication cost, difficulty in tracking historical records and lack of auditing in the existing PCB project design stage are solved by optimizing and automation the device packaging management and updating process, and the design efficiency of the PCB project is improved. And a more intelligent, safer and more efficient solution is provided for electronic product design.

Description

Technical Field

[0001] The present invention relates to the field of electronic technology, and in particular to a management and updating method for optimizing device packaging automation. Background Art

[0002] During the PCB project design phase, it is necessary to create a corresponding package for each component, which is usually done manually by library engineers based on the component data sheet. As the complexity of electronic products increases, a project may contain a variety of different components, so a large amount of package information is created. In the current labor model with detailed division of labor, a project includes at least library engineers and design engineers. When the library engineer handles a package information, the design engineer needs to be notified to update the design engineering file in a timely manner, especially when the two work in different locations, such as the library engineer in city A and the design engineer in city B.

[0003] The current operation process is as follows: Stage 1: Library engineers notify design engineers about package updates via email or other communication methods; Stage 2: Design engineers manually integrate new or updated packages into the design; Stage 3: Both parties confirm that the package has been correctly updated.

[0004] It can be seen that the existing working methods have the following problems: both parties are required to be online at the same time and communicate in a timely manner, which has poor timeliness; each library engineer is responsible for multiple projects, retrieving different netlists and updating package information. If each update requires notification, frequent email exchanges and communications take up a lot of working time and work efficiency is low; it is difficult to track the creation and modification history of the package, and whether it has been reviewed by a third party.

[0005] The above problems are worth solving. Summary of the invention

[0006] In order to overcome the problems of the prior art, the present invention provides a management and update method for optimizing device packaging automation, aiming to improve work efficiency, ensure timely transmission of information, and enhance data tracking and auditing capabilities through technical means.

[0007] The technical solution of the present invention is as follows:

[0008] A method for optimizing device packaging automation management and update, comprising the following steps:

[0009] Step 1: Deploy a centralized encapsulation database;

[0010] Deploy a packaging database to store and manage all data related to electronic component packaging;

[0011] Step 2: Bind the packaging information to the packaging file of the EDA software;

[0012] A unique identifier is attached to each packaged file to complete the information bundling with ID information;

[0013] Step 3: Establish synchronization mechanism and notification system;

[0014] The package data of the EDA software is kept synchronized with the package database, and update notifications are sent to relevant design engineers in a timely manner

[0015] Step 4: Automatically update the status log record;

[0016] After the design engineer automatically obtains the latest package file, the system generates a detailed update log record for traceability;

[0017] Step 5: Introduce a third-party audit mechanism;

[0018] Define the review process and integrate it into the packaging database.

[0019] As a preferred technical solution of the present invention, the step 1, building a centralized encapsulation database, specifically includes the following steps:

[0020] Step 101, create a database form;

[0021] Establishing a database form for storing component packaging information, wherein the database form has packaging information in a unified standard format, including fixed field names and types, and also includes editable custom fields to adapt to different project requirements;

[0022] Step 102: define the encapsulation database structure;

[0023] Define standardized data fields for each package information, including: component symbol name, device type, device value, data sheet link or attachment, project, library engineer number, creation time, modification information description, design engineer number, update time, reviewer number, and review date; realize that the data fields can fully describe the key attributes of each package;

[0024] Step 103: deploy and package the database;

[0025] Select multiple geographically dispersed locations to place several servers, forming a remote multi-point star server structure;

[0026] Use private IP addresses or virtual private network connections to limit external access to the server and deploy the encapsulated database to multi-site hub servers in different locations.

[0027] As a preferred technical solution of the present invention, the step 1 further comprises the following steps:

[0028] Step 104: Configure access rights;

[0029] Use public and private key authentication service program / server to complete user identity authentication to ensure that only authorized users can access the system;

[0030] Step 105: Develop a backup strategy.

[0031] Furthermore, the configuration of access rights includes the following specific steps: defining roles and assigning permissions, the roles include: library engineer, design engineer and administrator; the permissions of the library engineer include creating, editing, deleting and uploading packaging information after logging in using public-private key authentication; the permissions of the design engineer include viewing and downloading packaging files after logging in using public-private key authentication, and using them in design drafts; the permissions of the administrator include managing user information, monitoring system activity logs and database backup and recovery.

[0032] Furthermore, the backup strategy is formulated, and the specific steps include:

[0033] Step 1051, setting the backup frequency;

[0034] Set daily, weekly or monthly backup frequency based on business continuity needs;

[0035] Step 1052: Establish a retention period for backup data;

[0036] Step 1053, formulate a backup method;

[0037] Between two consecutive data backups, only the data that has changed since the last backup is backed up.

[0038] As a preferred technical solution of the present invention, the step 2, binding the packaging information with the packaging file of the EDA software, specifically comprises the following steps:

[0039] Step 201: clarify the metadata bound to the encapsulation file in the encapsulation information;

[0040] Metadata includes identifier, version number, library engineer number, creation timestamp, and modification timestamp;

[0041] Step 202: Develop a plug-in tool compatible with EDA software;

[0042] For EDA software, develop a plug-in tool for reading and writing EDA software. The plug-in tool is used to automatically generate a unique identifier when saving or uploading package information, and append it to the package file to form ID information;

[0043] Step 203: testing and verification;

[0044] The plug-in tool is fully tested to ensure that it can correctly generate and attach metadata and does not affect the normal operation of the EDA software.

[0045] Furthermore, comprehensive testing includes: functional testing, compatibility testing, performance testing, and security testing; functional testing is used to verify whether the creation, editing, saving, and uploading of packages work as expected; specifically, follow the normal usage process to confirm that each process is executed smoothly; enter abnormal or illegal data to check whether the plug-in tool recognizes it and gives an error prompt; compatibility testing is used to test whether the plug-in tool on different operating systems runs normally in the EDA software; specifically, install the plug-in tool on different operating systems and test the operation of the plug-in tool; performance testing is used to evaluate the response speed and resource consumption of the plug-in tool under high load; specifically, simulate the situation where multiple concurrent library engineers use the plug-in tool at the same time to observe whether the system remains stable; security testing is used to verify the effectiveness of the permission control mechanism; specifically, verify whether different roles can only perform operations within their respective permission range.

[0046] Furthermore, the plug-in tool includes:

[0047] The identifier generation module is used to generate a unique identifier; the file operation module is used to read the unique identifier of the encapsulated file and encapsulate the unique identifier into the file; the event monitoring module is used to monitor the save event and upload event; the database monitoring module monitors the data changes of the encapsulated database and sends information to the email sending module; the user interface module is used to provide an interactive interface.

[0048] As a preferred technical solution of the present invention, the step 3, establishing a synchronization mechanism and a notification system, specifically includes the following steps:

[0049] Step 301: Developing an API interface;

[0050] Design API interface to enable EDA software to communicate with packaging database, upload packaging information and its metadata, and download packaging files;

[0051] Step 302: Setting real-time synchronization logic;

[0052] On the library engineer side, whenever a new or updated footprint is created or modified, the plug-in tool automatically calls the API interface to upload the footprint and metadata to the footprint database;

[0053] When the package database detects a new or updated package, it immediately sends a notification to the relevant design engineer via email; the notification content includes the package identifier, version number, library engineer number, creation timestamp and modification timestamp;

[0054] On the design engineer side, open the EDA software configured with the plug-in tool. The plug-in tool automatically downloads the latest package file through the download interface of the API interface and synchronizes it directly to the design document.

[0055] Furthermore, the notification system includes:

[0056] A database monitoring module is used to monitor changes in the package database and detect new or updated packages;

[0057] The email sending module sends notification emails to relevant design engineers according to the instructions of the database monitoring module.

[0058] As a preferred technical solution of the present invention, the step 4, automatic update status log recording, specifically includes the following steps: recording each update operation in detail, including the executor of the update, the time point of the update, and the content of the update.

[0059] As a preferred technical solution of the present invention, the step 5, introducing a third-party audit mechanism, specifically includes the following steps:

[0060] Step 501, define the review process;

[0061] Identify the types of changes that require third-party review;

[0062] Specifically include: major changes to existing packages, such as pin layout changes, physical size adjustments, etc.; adding new electronic components and their packaging information;

[0063] Step 502: integration review process;

[0064] Add a review field in the database that allows reviewers to enter comments and approval status.

[0065] Furthermore, the audit fields include:

[0066] The review status field is used to record the current review status of each package change, such as "pending review", "approved", or "rejected";

[0067] The audit comment field is used to allow the auditor to enter detailed audit comments;

[0068] The reviewer information field is used to record the number and contact information of the person responsible for the review;

[0069] Review date field, used to automatically record the timestamp of each review.

[0070] The present invention according to the above scheme has the following beneficial effects:

[0071] The present invention realizes unified management and version control of packaging information by creating a centralized device packaging database. Library engineers can quickly write packaging information into the device packaging database, and conveniently create and upload device packaging information. Design engineers can obtain packaging update information in a timely manner, and the system automatically synchronizes and updates design documents. The automated notification system and status log recording function enhance the transparency of the entire process, allowing team members to maintain efficient collaboration no matter where they are. Configuring access rights and formulating backup strategies ensures data security and business continuity. At the same time, the introduction of a third-party audit mechanism strengthens control over changes, further improving data quality and reliability.

[0072] Furthermore, the processes of each of the above nodes are recorded in detail, which makes it easy to find the process records and ensure that the history of any package creation or modification is clearly visible, which facilitates problem troubleshooting and responsibility definition;

[0073] Therefore, the present invention solves the problems of low efficiency, high communication cost, difficulty in tracking historical records and lack of audit encountered in the existing PCB project design stage by optimizing and automating the device packaging management and update process, providing a more intelligent, safe and efficient solution for electronic product design. BRIEF DESCRIPTION OF THE DRAWINGS

[0074] Figure 1 is a flow chart of the method of the present invention;

[0075] Figure 2 is a method flow chart of step 1 in the present invention;

[0076] Figure 3 is a method flow chart of step 2 in the present invention;

[0077] Figure 4 This is a method flow chart of step 3 in the present invention. DETAILED DESCRIPTION

[0078] In order to better understand the purpose, technical scheme and technical effect of the present invention, the present invention is further explained in conjunction with the accompanying drawings and embodiments. It should be noted that similar numbers and letters represent similar items in the following drawings. Therefore, once an item is defined in one drawing, it does not need to be further defined and explained in the subsequent drawings. At the same time, it is stated that the embodiments described below are only used to explain the present invention and are not used to limit the present invention.

[0079] It should be noted that when an element is referred to as being "fixed to" or "disposed on" another element, it may be directly on the other element or there may be an intermediate element, and when an element is considered to be "connected to" another element, it may be directly connected to the other element or there may be an intermediate element at the same time. The term "several" means two or more, unless otherwise clearly and specifically defined.

[0080] like Figure 1 As shown, a method for optimizing device packaging automation management and update includes the following steps:

[0081] Step 1: Deploy a centralized encapsulation database;

[0082] Deploy a packaging database to store and manage all data related to electronic component packaging;

[0083] Step 2: Bind the packaging information to the packaging file of the EDA software;

[0084] A unique identifier is attached to each packaged file to complete the information bundling with ID information;

[0085] Step 3: Establish synchronization mechanism and notification system;

[0086] The package data of the EDA software is kept synchronized with the package database, and update notifications are sent to relevant design engineers in a timely manner

[0087] Step 4: Automated update and status logging;

[0088] The design engineer automatically obtains the latest package files, and all update operations are recorded in detailed logs for traceability;

[0089] Step 5: Introduce a third-party audit mechanism;

[0090] Define the review process and integrate it into the packaging database.

[0091] The present invention realizes unified management and version control of packaging information by creating a centralized device packaging database. Library engineers can quickly write packaging information into the device packaging database and conveniently create and upload device packaging information; design engineers can obtain packaging update information in a timely manner and synchronously update design documents; the automated notification system and status log recording function enhance the transparency of the entire process, allowing team members to maintain efficient collaboration no matter where they are; configuring access rights and formulating backup strategies ensure data security and business continuity, while introducing a third-party audit mechanism to strengthen control over changes, further improving data quality and reliability.

[0092] like Figure 2As shown, in this embodiment, step 1, building a centralized encapsulation database, specifically includes the following steps:

[0093] Step 101, create a database form;

[0094] A database form is established for storing component packaging information. The database form has packaging information in a unified standard format, including fixed field names and types, and editable custom fields to accommodate different project requirements. Fixed fields ensure that all records follow the same format, facilitating subsequent data processing and analysis; custom fields allow for adjustment based on specific needs to meet the special requirements of specific projects, increasing the applicability and scalability of the system; unified standards reduce the possibility of human error and ensure data consistency and accuracy.

[0095] Step 102: define the encapsulation database structure;

[0096] Standardized data fields are defined for each package information, including: component symbol name, device type, device value, data sheet link or attachment, project, library engineer number, creation time, modification information description, design engineer number, update time, reviewer number, and review date; data fields are implemented to fully describe the key attributes of each package; rich data fields can more comprehensively describe the key attributes of each package, allowing users to quickly and accurately find the required information; creation time and update time fields can help track the history of any changes, which is crucial for maintaining version control and solving potential problems; the personnel numbers involved (such as library engineer number, design engineer number, reviewer number) clarify the responsibilities of each stage, help improve work efficiency and promote collaboration between teams; data sheet link or attachment fields provide a way to directly access related documents, simplify the process of finding information, and improve work efficiency.

[0097] Step 103: deploy and package the database;

[0098] Select multiple geographically dispersed locations to place several servers to form a remote multi-point star server structure; the purpose is to ensure that when there is a server failure, power outage or machine downtime, as long as there is one server in the entire domain working normally, data transmission and update functions can be carried out.

[0099] Use private IP addresses or virtual private network connections to limit external access to the server, and deploy the encapsulated database to a secure and reliable remote multi-point star server. By limiting external access, the risk of unauthorized access is reduced and sensitive data is protected from unauthorized users; choosing a stable and high-performance server environment to deploy the database can ensure service continuity and responsiveness, thereby supporting efficient business operations.

[0100] The centralized packaging database constructed in steps 101 to 103 not only improves the efficiency of component packaging information management, but also enhances data security and reliability, while promoting efficient collaboration between cross-regional teams.

[0101] In a preferred embodiment, step 1 further comprises the following steps:

[0102] Step 104: Configure access rights;

[0103] Public-private key authentication service program / server is used to complete user identity authentication to ensure that only authorized users can access the system. The specific steps for configuring access rights are: defining roles and assigning permissions. The roles include: library engineer, design engineer and administrator, which realizes the refinement of permission management.

[0104] Specifically, library engineers have the authority to create, edit, delete and upload package information after logging in with public-private key authentication; design engineers have the authority to view and download package files and use them in design drafts after logging in with public-private key authentication; administrators are responsible for managing user information, monitoring system activity logs, and high-level tasks such as database backup and recovery to ensure the stable operation of the system and support business continuity. The clear division of roles in this step promotes collaboration among team members, reduces unnecessary communication costs, and also reduces the probability of operational errors due to unclear permissions. By combining the strictness of public-private key authentication with the sophistication of role permission allocation, the security of system data and the standardization of operations are fully guaranteed, unauthorized access and malicious operations are prevented, and users of different roles can only operate the package database and related system functions within their permitted permissions, thereby effectively maintaining the orderliness and stability of the entire device package automation management and update process.

[0105] Step 105: Formulate a backup strategy. The specific steps include:

[0106] Step 1051, setting the backup frequency;

[0107] Set daily, weekly or monthly backup frequency according to business continuity needs to ensure data is always up to date;

[0108] Step 1052: Establish a retention period for backup data;

[0109] By stipulating the retention period of backup data, it not only avoids the waste of storage space caused by indefinite retention, but also ensures that there are enough historical versions for tracing when necessary;

[0110] Step 1053, formulate a backup method;

[0111] Between two consecutive data backups, only the data that has changed since the last backup is backed up. With incremental backup, only the data that has changed since the last backup is backed up between two consecutive full backups. This method significantly reduces the time and storage space required for backup, while speeding up recovery.

[0112] The steps 104 to 105 not only enhance the security of the system, but also improve the data protection level and the ability to support business continuity. In particular, through strict authority management and efficient backup mechanisms, unauthorized data access and loss risks are effectively prevented, ensuring that the electronic component packaging information management system can operate stably and reliably in a complex and changing working environment.

[0113] like Figure 3 As shown, in this embodiment, step 2, binding the packaging information with the packaging file of the EDA software, specifically includes the following steps:

[0114] Step 201: clarify the metadata bound to the encapsulation file in the encapsulation information;

[0115] The metadata includes identifier, version number, library engineer number, creation timestamp, and modification timestamp. The identifier assigns a unique identifier to each package file to ensure that different package versions can be distinguished even if the file name is the same. The version number records different versions of the package, which facilitates tracking historical changes and supports version rollback. The library engineer number associates the engineer responsible for the package, which helps to divide responsibilities and trace problems.

[0116] This step 201 adds detailed metadata so that the history of each package file can be clearly tracked, which is very important for long-term project management and quality assurance. With clear metadata tags, users can quickly find the required package information according to specific conditions, thereby improving work efficiency. The existence of metadata provides a basis for the subsequent introduction of automated tools (such as automatic updates or batch operations), thereby promoting process optimization.

[0117] Step 202: Develop a plug-in tool compatible with EDA software;

[0118] For EDA software, a plug-in tool is developed for reading and writing EDA software. The plug-in tool is used to automatically generate a unique identifier when saving or uploading package information, and attach it to the package file to form ID information; whenever a new record is inserted, the plug-in tool will automatically increment and assign a unique ID value as an identifier to help the system track and manage data changes.

[0119] Plugin tools include:

[0120] An identifier generation module, used to generate a unique identifier;

[0121] A file operation module, used for reading a unique identifier of a packaged file and packaging the unique identifier into a file;

[0122] Event monitoring module, used to monitor save events and upload events;

[0123] Database monitoring module, monitors data changes in the encapsulated database and sends information to the email sending module;

[0124] The user interface module is used to provide an interactive interface.

[0125] Step 203: testing and verification;

[0126] The plug-in tool is fully tested to ensure that it can correctly generate and attach metadata and does not affect the normal operation of the EDA software. The comprehensive test includes: functional testing, compatibility testing, performance testing, and security testing.

[0127] Among them, functional testing is used to verify whether the creation, editing, saving, and uploading of packages work as expected. Specifically, follow the normal usage process to confirm that each process is executed smoothly; enter abnormal or illegal data to check whether the plug-in tool recognizes it and gives an error prompt. Compatibility testing is used to test whether the plug-in tools on different operating systems run normally in EDA software. Specifically, install the plug-in tools on different operating systems and test the operation of the plug-in tools. Performance testing is used to evaluate the response speed and resource consumption of plug-in tools under high load. Specifically, simulate the situation where multiple concurrent library engineers use the plug-in tools at the same time to observe whether the system remains stable. Security testing is used to verify the effectiveness of the permission control mechanism. Specifically, it verifies whether different roles can only perform operations within their respective permissions.

[0128] like Figure 4 As shown, in this embodiment, step 3, establishing a synchronization mechanism and a notification system, specifically includes the following steps:

[0129] Step 301: Developing an API interface;

[0130] Design an API interface to enable the EDA software to communicate with the packaging database to upload packaging information and its metadata and download packaging files.

[0131] Step 302: Setting real-time synchronization logic;

[0132] On the library engineer side, whenever a new or updated package is created or modified, the plug-in tool automatically calls the API interface to upload the package and metadata to the package database; this step satisfies the library engineer to upload the new or updated package information to the package database through the plug-in tool;

[0133] When the package database detects a new or updated package, it immediately sends a notification to the relevant design engineer via email; the notification content includes the package identifier, version number, library engineer number, creation timestamp and modification timestamp;

[0134] On the design engineer side, open the EDA software configured with the plug-in tool. The plug-in tool automatically downloads the latest package file through the download interface of the API interface and synchronizes it directly to the design document.

[0135] Among them, the notification system includes:

[0136] A database monitoring module is used to monitor changes in the package database and detect new or updated packages;

[0137] The email sending module is responsible for assembling the email content and sending it to the relevant design engineer through the SMTP server according to the instructions of the database monitoring module; the email content should contain important information such as the encapsulated identifier, version number, library engineer number, creation timestamp and modification timestamp.

[0138] This step 3 can reduce the time delay of manual intervention and ensure that the latest version of the packaging file can be synchronized with the packaging database as soon as possible; it replaces manual operations with programmed methods to reduce the probability of errors caused by human negligence; it continuously monitors changes in the packaging database and immediately triggers the subsequent notification process once new or updated records are found.

[0139] Step 4: Status log recording. Specific steps: implement status log recording;

[0140] Record every update operation in detail, including who updated it, when it was updated, and what was updated. Accurate logging is essential for tracking potential security threats and can help quickly locate and respond to abnormal behavior. For example, when a problem occurs, relevant personnel can quickly find the root cause by viewing the log, shortening the time required to solve the problem.

[0141] In this embodiment, step 5, introducing a third-party audit mechanism, specifically includes the following steps:

[0142] Step 501, define the review process;

[0143] Identify the types of changes that require third-party review;

[0144] Specifically include: major changes to existing packages, such as pin layout changes, physical size adjustments, etc.; adding new electronic components and their packaging information;

[0145] Step 502: integration review process;

[0146] Add an audit field to the database, which is used to allow auditors to enter opinions and approval status. Among them, the audit field includes an audit status field, an audit opinion field, a reviewer information field, and an audit date field. The audit status field is used to record the current audit status of each package change, such as "pending review", "approved", and "rejected", to help track the progress of each change and provide users with clear status indications; the audit opinion field is used to allow auditors to enter detailed audit opinions; the reviewer information field is used to record the number and contact information of the person responsible for the audit to ensure clear responsibilities and facilitate contact and traceability; the audit date field is used to automatically record the timestamp of each audit and provide an accurate time reference.

[0147] Through step 5, professional third-party audits can be achieved, which can effectively reduce errors and incompatibilities and improve the quality and reliability of changes. Ensuring that all changes follow established standards and specifications helps maintain the consistency and stability of the entire project. Detailed audit records make the history of each change clear at a glance, facilitating future inquiries and audits. Structured audit fields greatly simplify the audit process and improve the efficiency of collaboration between teams. Clear audit status and detailed feedback can drive the project forward more quickly.

[0148] In summary, the present invention optimizes and automates the device package management and update process, and the process of each node is recorded in detail, which facilitates the search of process records and ensures that the history of any package creation or modification is clearly visible, which is convenient for problem troubleshooting and responsibility definition. It solves the problems of low efficiency, high communication costs, difficulty in tracking historical records and lack of audit encountered in the existing PCB project design stage, and provides a more intelligent, safe and efficient solution for electronic product design.

[0149] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0150] The above embodiments only express several implementation methods of the present invention, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the invention patent. It should be pointed out that, for those of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present invention, and these all belong to the protection scope of the present invention. Therefore, the protection scope of the patent of the present invention shall be subject to the attached claims.

Claims

1. A method for optimizing device packaging automation management and update, characterized in that: The following steps are involved: Step 1: Deploy a centralized encapsulation database; Deploy a packaging database to store and manage all data related to electronic component packaging; Step 2: Bind the packaging information to the packaging file of the EDA software; A unique identifier is attached to each packaged file to complete the information bundling with ID information; Step 3: Establish synchronization mechanism and notification system; The package data of the EDA software is kept synchronized with the package database, and update notifications are sent to relevant design engineers in a timely manner; Step 4: Automatically update the status log record; After the design engineer automatically obtains the latest package file, the system generates a detailed update log record for traceability; Step 5: Introduce a third-party audit mechanism; Define the review process and integrate it into the packaging database.

2. The method for optimizing device packaging automation management and update according to claim 1, characterized in that: The step 1, building a centralized encapsulation database, specifically includes the following steps: Step 101, create a database form; Establishing a database form for storing component packaging information, wherein the database form has packaging information in a unified standard format, including fixed field names and types, and also includes editable custom fields to adapt to different project requirements; Step 102: define the encapsulation database structure; Define standardized data fields for each package information, including: component symbol name, device type, device value, data sheet link or attachment, project, library engineer number, creation time, modification information description, design engineer number, update time, reviewer number, and review date; realize that the data fields can fully describe the key attributes of each package; Step 103: deploy and package the database; Select multiple geographically dispersed locations to place several servers, forming a remote multi-point star server structure; Use private IP addresses or virtual private network connections to limit external access to the server and deploy the encapsulated database to multi-site hub servers in different locations.

3. The method for optimizing device packaging automation management and update according to claim 2, characterized in that: The step 1 also includes the following steps: Step 104: Configure access rights; Use public and private key authentication service program / server to complete user identity authentication to ensure that only authorized users can access the system; Step 105: Develop a backup strategy.

4. The method for optimizing device packaging automation management and update according to claim 3, characterized in that: The specific steps of configuring access rights are: defining roles and assigning permissions, the roles include: library engineer, design engineer and administrator; the permissions of the library engineer include creating, editing, deleting and uploading packaging information; the permissions of the design engineer include viewing and downloading packaging files and using them in design drafts; the permissions of the administrator include managing user information, monitoring system activity logs and database backup and recovery.

5. The method for optimizing device packaging automation management and update according to claim 3, characterized in that: The specific steps of formulating the backup strategy include: Step 1051, setting the backup frequency; Set daily, weekly or monthly backup frequency based on business continuity needs; Step 1052: Establish a retention period for backup data; Step 1053, formulate a backup method; Between two consecutive data backups, only the data that has changed since the last backup is backed up.

6. The method for optimizing device packaging automation management and update according to claim 1, characterized in that: The step 2, binding the packaging information with the packaging file of the EDA software, specifically comprises the following steps: Step 201: clarify the metadata bound to the encapsulation file in the encapsulation information; Metadata includes identifier, version number, library engineer number, creation timestamp, and modification timestamp; Step 202: Develop a plug-in tool compatible with EDA software; For EDA software, develop a plug-in tool for reading and writing EDA software. The plug-in tool is used to automatically generate a unique identifier when saving or uploading package information, and append it to the package file to form ID information; Step 203: testing and verification; The plug-in tool is fully tested to ensure that it can correctly generate and attach metadata and does not affect the normal operation of the EDA software.

7. The method for optimizing device packaging automation management and update according to claim 6, characterized in that: The plug-in tools include: An identifier generation module, used to generate a unique identifier; A file operation module, used for reading a unique identifier of a packaged file and packaging the unique identifier into a file; Event monitoring module, used to monitor save events and upload events; Database monitoring module, monitors data changes in the encapsulated database and sends information to the email sending module; The user interface module is used to provide an interactive interface.

8. The method for optimizing device packaging automation management and update according to claim 6, characterized in that: The step 3, establishing a synchronization mechanism and a notification system, specifically includes the following steps: Step 301: Developing an API interface; Design API interface to enable EDA software to communicate with the package database, and upload package information and its metadata as well as download package files; Step 302: Setting real-time synchronization logic; On the library engineer side, whenever a new or updated footprint is created or modified, the plug-in tool automatically calls the API interface to upload the footprint and metadata to the footprint database; When the package database detects a new or updated package, it immediately sends a notification to the relevant design engineer via email; the notification content includes the package identifier, version number, library engineer number, creation timestamp and modification timestamp; On the design engineer side, open the EDA software configured with the plug-in tool. The plug-in tool automatically downloads the latest package file through the download interface of the API interface and synchronizes it directly to the design document.

9. The method for optimizing device packaging automation management and update according to claim 1, characterized in that: The step 4, automatic update status log recording, specifically includes the following steps: recording each update operation in detail, including the update executor, the update time point, and the update content.

10. The method for optimizing device packaging automation management and update according to claim 1, characterized in that: The step 5, introducing a third-party audit mechanism, specifically includes the following steps: Step 501, define the review process; Identify the types of changes that require third-party review; Specifically include: major changes to existing packages, such as pin layout changes, physical size adjustments, etc.; adding new electronic components and their packaging information; Step 502: integration review process; Add a review field in the database that allows reviewers to enter comments and approval status.

Images