A Multi-Level CAD Drawing Version Traceability Management Method and Platform

Abstract

This invention discloses a multi-level CAD drawing version traceability management method and platform, belonging to the field of drawing management technology. The method includes: introducing a four-element code based on stage-software version-purpose-server settings; combining targeted focusing and difference coding in the version update process; introducing feature descriptors to construct a difference knowledge base; and constructing a two-layer state machine based on feature differences and update type. Based on the four-element code and state machine, a microservice architecture is built in the drawing management platform to receive and decouple version traceability tasks, execute code traceability and state-level cascaded traceability, verify the traceability results, and output the final version traceability result. This achieves the technical effect of mining information from both code and state dimensions, improving the accuracy, completeness, and reliability of drawing version traceability.

Description

Technical Field

[0001] This invention relates to the field of drawing management technology, and in particular to a multi-level CAD drawing version traceability management method and platform. Background Technology

[0002] In the design, modification, and management of CAD drawings, version traceability is a crucial aspect. Currently, common CAD drawing version management methods rely heavily on simple file naming rules, timestamp records, or basic version control software. While these methods can differentiate and manage different versions of drawings to some extent, they often fall short when dealing with complex, multi-layered version relationships. Especially when drawings have undergone multiple design stages, are used for different purposes, have been modified under different software versions, and are stored across multiple servers, traditional traceability management methods struggle to efficiently and accurately locate specific versions, easily leading to confusion and affecting the continuity and traceability of the design work.

[0003] Specifically, in existing technologies, drawing identification is not precise enough and lacks a systematic approach, making it difficult to establish a unique and clear mapping relationship between codes and drawing databases. This results in difficulty in quickly and accurately locating target drawings within massive amounts of drawing data. Furthermore, the records of differences during drawing version updates are often incomplete, failing to comprehensively and meticulously construct a complete knowledge system encompassing change characteristics and types. It is also unable to effectively distinguish between different update types, such as ordinary updates and archived updates, and their corresponding status characteristics. Consequently, tracing back to the source can only be done through a simple search from a single dimension, making it difficult to deeply explore the evolution of drawing versions, and compromising the accuracy and completeness of the tracing results. Summary of the Invention

[0004] This invention provides a multi-level CAD drawing version traceability management method and platform to solve the technical problems of the lack of an efficient and accurate identification and management system in the prior art, which affects the accuracy and reliability of drawing traceability. It realizes dual-dimensional information mining of coding and status, and improves the technical effect of drawing version traceability in terms of accuracy, completeness and reliability.

[0005] In a first aspect, the present invention provides a multi-level CAD drawing version traceability management method, wherein the multi-level CAD drawing version traceability management method includes:

[0006] A quaternion encoding is introduced, wherein the quaternion encoding is set according to the stage of the CAD drawing, the software version, the purpose, and the server.

[0007] By focusing on the version update process and using difference encoding, a difference knowledge base is constructed by introducing feature descriptors. The feature difference is used as the first state layer and the update type is used as the second state layer. A state machine is introduced, wherein the update type includes normal update and archive update.

[0008] Based on the quaternion encoding and the state machine, a microservice architecture is constructed within the drawing management platform to receive version tracing tasks, decouple tasks, execute encoding tracing and state layer cascade tracing in parallel, verify the tracing results, and determine the version tracing results.

[0009] In one feasible implementation, quadruple encoding is introduced, including:

[0010] Using the stage of the CAD drawing, software version, purpose, and server as multiple coding elements, a unidirectional coding chain is constructed for each coding element.

[0011] The unidirectional coding chains are integrated in parallel, the association between the unidirectional coding chains and the distributed drawing database is established, and coding rules are set and introduced as quadruple codes.

[0012] In one feasible implementation, a connection is established between a one-way coding chain and a distributed drawing database, including:

[0013] For the distributed drawing database, a virtual mapping layer is established, wherein the virtual mapping layer is a unified data system constructed by introducing coded elements.

[0014] Establish the mapping association between the unidirectional encoding chain, the virtual mapping layer, and the distributed drawing database.

[0015] In one feasible implementation, a difference knowledge base is constructed by introducing feature descriptors based on the targeted focus and difference encoding of the version update process, including:

[0016] With each version update, the upstream and downstream drawing versions are determined.

[0017] The upstream and downstream drawing versions are targeted and focused based on the differences in features to determine the drawing focus point.

[0018] Determine the knowledge base coding rules, perform differential coding on the focal points of the drawing, and determine the feature descriptors of the update nodes.

[0019] The feature descriptors are added to the differential knowledge base.

[0020] In one feasible implementation, a state machine is introduced, with feature differences as the first state layer and update type as the second state layer, including:

[0021] Based on the aforementioned differential knowledge base, a first state layer is constructed using a hierarchical, cascaded classification structure.

[0022] A second state layer is built using regular updates and archived updates as version sources.

[0023] The state machine is determined by cascading the first state layer and the second state layer.

[0024] In one feasible implementation, a mapping association is established between the state machine, the virtual mapping layer, and the distributed drawing database.

[0025] In one feasible implementation, after receiving the version tracing task, the process includes:

[0026] Start the access authentication port within the drawing management platform.

[0027] Receive the version tracing task, perform user permission authentication, and determine the authentication information.

[0028] Based on the authentication information, the virtual mapping layer is temporarily marked with authorized and non-authorized portions.

[0029] In one feasible implementation, task decoupling is performed, and code tracing and state layer cascading tracing are executed in parallel. The tracing results are verified, and the version tracing results are determined, including:

[0030] Based on the microservice architecture, the content layer and meta layer of the version tracing task are decoupled to determine the first tracing dimension and the second tracing dimension.

[0031] For the first traceability dimension, perform encoding location based on quadrature encoding and permission-based location based on the virtual mapping layer to determine the first traceability result.

[0032] For the second traceability dimension, perform hierarchical cascading location based on the state machine and permission-based partial location based on the virtual mapping layer to determine the second traceability result.

[0033] The first traceability result and the second traceability result are compared to determine the version traceability result.

[0034] In one feasible implementation, verifying the first traceability result and the second traceability result to determine the version traceability result includes:

[0035] If the first traceability result is consistent with the second traceability result, the traceability version drawing is retrieved and displayed on the interface according to the mapping of the virtual mapping layer - distributed drawing database.

[0036] If the first traceability result is inconsistent with the second traceability result, a secondary verification node is triggered to execute the verification mapping retrieval and drawing display.

[0037] Secondly, the present invention also provides a multi-level CAD drawing version traceability management platform, wherein the multi-level CAD drawing version traceability management platform includes:

[0038] The quaternion encoding introduction module is used to introduce quaternion encoding, wherein the quaternion encoding is set according to the stage of CAD drawing-software version-purpose-server.

[0039] The feature descriptor and difference knowledge base construction module is used to construct a difference knowledge base by introducing feature descriptors based on the targeted focus and difference encoding of the version update process. It introduces a state machine with feature difference as the first state layer and update type as the second state layer. The update type includes normal update and archived update.

[0040] The architecture construction and traceability execution module is used to build a microservice architecture within the drawing management platform based on the quadrature code and the state machine, receive version traceability tasks, decouple the execution tasks, execute code traceability and state layer cascade traceability in parallel, verify the traceability results, and determine the version traceability results.

[0041] This invention discloses a multi-level CAD drawing version traceability management method and platform, comprising: introducing a four-tuple coding method including four dimensions: stage, software version, purpose, and server, for identifying and managing CAD drawings; constructing a feature description subset through targeted focusing and differentiated coding for the version update process, and then establishing a difference knowledge base, wherein drawing feature differences are used as the first state layer, and update type (including ordinary update and archived update) is used as the second state layer, and a state transition mechanism is constructed; in the drawing management platform, based on the above four-tuple coding and state transition mechanism, a microservice architecture is constructed to receive drawing version traceability tasks, and task decoupling operations are performed during task processing, and parallel traceability is performed on the coding link and the state level link respectively. Through cross-validation of traceability results, the version traceability result of the target drawing is finally determined. The multi-level CAD drawing version traceability management method and platform disclosed in this invention solves the technical problem of lacking an efficient and accurate identification and management system, which affects the accuracy and reliability of drawing traceability, and realizes the technical effect of dual-dimensional information mining of coding and state, improving the accuracy, completeness and reliability of drawing version traceability. Attached Figure Description

[0042] Figure 1 This is a flowchart illustrating a multi-level CAD drawing version traceability management method according to the present invention.

[0043] Figure 2 This is a schematic diagram of the structure of a multi-level CAD drawing version traceability management platform according to the present invention.

[0044] Figure labeling: Quadruple encoding introduction module 11, Feature descriptor and difference knowledge base construction module 12, Architecture construction and traceability execution module 13. Detailed Implementation

[0045] The above technical solutions will now be described in detail with reference to the accompanying drawings and specific embodiments to provide a better understanding of them. Obviously, the described embodiments are only a part of the embodiments of the present invention, and not all of them. It should be understood that the present invention is not limited to the exemplary embodiments used only to explain the present invention. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without creative effort are within the scope of protection of the present invention. Furthermore, it should be noted that, for ease of description, only the parts related to the present invention are shown in the drawings, not all of them.

[0046] Example 1, as Figure 1 This is a flowchart illustrating a multi-level CAD drawing version traceability management method according to the present invention, wherein the multi-level CAD drawing version traceability management method includes:

[0047] S100: Introduce a quaternion encoding, wherein the quaternion encoding is set according to the stage of the CAD drawing, the software version, the purpose, and the server.

[0048] Specifically, a quaternion code refers to a unique identifier composed of four dimensions of information, including:

[0049] Stage: Refers to the different lifecycle stages of the CAD drawing, such as design, review, construction, and archiving. Software Version: Refers to the specific CAD software used to generate or edit the CAD drawing and its version number. Purpose: Refers to the specific application scenario or purpose of the drawing (e.g., construction, review, briefing, filing, etc.). Server-Side Settings: Refers to the server-side identity of the drawing (e.g., construction party, design party, supervision party, etc.).

[0050] By introducing quaternion coding, we can achieve refined and multi-level management of CAD drawings at different lifecycle stages, different software versions, different uses and server configurations, which facilitates subsequent quality traceability, permission allocation and historical record query.

[0051] In some embodiments, quadruple encoding is introduced, including:

[0052] Using the stage, software version, purpose, and server of a CAD drawing as multiple coding elements, a one-way coding chain is constructed for each coding element; the one-way coding chains are then integrated in parallel to establish a connection between the one-way coding chains and the distributed drawing database, and coding rules are set and introduced as a quaternion coding.

[0053] Specifically, a unidirectional coding chain refers to an irreversible chain of coding elements, arranged according to time, version, or business process, to reflect the evolution relationship and traceability path of coding elements. In other words, a unidirectional coding chain includes multiple coding elements that progress along a temporal direction.

[0054] For example, based on the actual business requirements of the CAD drawings, four coded elements are extracted: "Stage," "Software Version," "Purpose," and "Server," and a unique identifier is assigned to each coded element. For example:

[0055] Stage codes: 01 (design), 02 (review), 03 (construction), 04 (archiving); Software version codes: A01, B02; Purpose codes: X1 (construction), X2 (review), X3 (filing); Server codes: S01 (main server), S02 (backup server).

[0056] For example, 03-B02-X1-S01 means "Construction Phase - Using B02 Version Software - For Construction - Main Server".

[0057] Furthermore, the unidirectional coding chains of the above four coding elements are integrated in parallel to form a complete four-element code, which is then used as the primary key to bind to each drawing in the distributed drawing database, achieving unique identification and multi-dimensional traceability of the drawings. Simultaneously, the value range, increment rules, and conflict handling mechanism for each coding element are defined to ensure the standardization and scalability of the coding.

[0058] Through the above process, quaternion coding and unidirectional coding chains are introduced to achieve refined and multi-dimensional management of CAD drawings at different stages, with different software versions, for different purposes, and with different server configurations.

[0059] In some embodiments, establishing the association between a one-way coding chain and a distributed drawing database includes:

[0060] For the distributed drawing database, a virtual mapping layer is established, wherein the virtual mapping layer is a unified data system constructed by introducing coded elements; a mapping association is established between the unidirectional coding chain, the virtual mapping layer, and the distributed drawing database.

[0061] Specifically, a distributed drawing database refers to a database in which drawing data is stored in multiple different locations (such as different servers, different storage devices, etc.). It has the characteristics of discrete storage location and diverse heterogeneity of internal data structure and specifications, which makes management more difficult.

[0062] Specifically, the virtual mapping layer is a virtual, unified data system layer introduced to solve the difficulties in managing distributed drawing databases. This virtual mapping layer acts as the traceability entity for analysis and associates coded elements with the actual storage database through mapping relationships. This allows the drawing in the specific distributed drawing database to be located through the virtual mapping layer via a one-way coding chain.

[0063] Specifically, each coded element in the one-way coding chain is associated with a corresponding part in the virtual mapping layer, which then establishes a mapping relationship with the actual distributed drawing database. For example, for the stage code "S1" in the one-way coding chain, the virtual mapping layer defines it as corresponding to a set of drawings for a specific design stage, which may be stored in different distributed drawing databases. Through pre-defined mapping rules, "S1" is associated with these specific storage locations, thereby achieving precise location from code to drawing.

[0064] For example, for the code 03-B02-X1-S01, the virtual mapping layer can create a corresponding record pointing to the specific physical database and its internal storage path. Thus, in the virtual mapping layer, each drawing data is made to use its unique unidirectional code chain as the primary key, realizing the mapping between the code and the actual data.

[0065] Optionally, the virtual layer may include the following structure fields: one-way coding chain, virtual drawing ID, physical storage location identifier, database type / structure description, and physical data path.

[0066] By establishing a virtual mapping layer, the discreteness of storage locations and the heterogeneity of structure in the distributed drawing database are effectively abstracted and unified. Combined with a unidirectional coding chain, efficient, accurate, and traceable management of distributed drawing data is achieved. This helps improve data management efficiency, retrieval speed, and traceability capabilities, while reducing the complexity of operation and maintenance.

[0067] S200: Based on the directional focus and difference encoding of the version update process, feature descriptors are introduced to construct a difference knowledge base. With feature difference as the first state layer and update type as the second state layer, a state machine is introduced. The update type includes normal update and archived update.

[0068] Specifically, the version update process refers to the entire process of updating CAD drawings from one version to another, including equipment modifications and parameter adjustments. Targeted focusing refers to the purposeful and focused attention on the changed parts of the drawing during the version update. Difference coding is used to encode the differences in the drawing update process to facilitate the identification and management of these differences.

[0069] Specifically, a feature descriptor is a set of attributes described using a structured coding method for the specific elements that differ during the drawing version update process. In other words, feature descriptors represent the change characteristics of upstream and downstream drawing versions at a specific focal point, facilitating difference tracking and knowledge accumulation. The difference knowledge base is a database that stores the difference information generated during the drawing update process and its related feature descriptors.

[0070] In the above process, through targeted focusing and difference coding, the specific changes of the drawing in each update process can be accurately captured and stored in the difference knowledge base in the form of feature descriptors, providing rich information for subsequent drawing traceability; by constructing the first state layer and the second state layer and introducing a state machine, the feature differences and update types of the drawing can be classified and managed, thereby realizing dynamic management and tracking of the drawing update status.

[0071] In some embodiments, a difference knowledge base is constructed by introducing feature descriptors based on the targeted focus and difference encoding of the version update process, including:

[0072] As the version is updated, the upstream and downstream drawing versions are determined; the upstream and downstream drawing versions are targeted and focused based on the differences in elements to determine the drawing focus point; the knowledge base coding rules are determined, the drawing focus point is coded differently, and the feature descriptor of the update node is determined; the feature descriptor is added to the difference knowledge base.

[0073] Specifically, the upstream drawing version refers to the version before the update, while the downstream drawing version refers to the version after the update.

[0074] Specifically, during the CAD drawing version update process, the upstream and downstream drawing versions must first be identified. For example, V1.0 can be considered the upstream version, and V1.1 the downstream version. Then, a targeted focus based on element differences is performed between the upstream and downstream drawing versions. This involves comparing the upstream and downstream drawing versions at the element level (including components, dimensions, symbols, annotations, etc.) and, through automatic algorithms or manual assistance, focusing on the key elements that have changed to determine the "drawing focal point." For example, compared to V1.1, the dimension of a beam changes from 200mm to 250mm.

[0075] Furthermore, the structure and rules of the difference coding are clearly defined, including fields such as difference element type, change content, scope of impact, and reason for change. Then, for each focal point, a unique feature descriptor is generated according to the established coding rules. For example, if the focal point of the drawing is: Difference type: dimensional change; Element location: Beam B1; Before change: 200mm; After change: 250mm; Reason for change: structural optimization, then the feature descriptor after difference coding would be: D-Beam B1-Dimension-200-250-Structural optimization.

[0076] Finally, the aforementioned feature descriptors are added as entries to the difference knowledge base to achieve the accumulation and archiving of differences for each version update.

[0077] Through the above process, targeted focus and structured coding of differences in the drawing version update process were achieved, improving the traceability of version changes and the ability to accumulate knowledge. The establishment of the difference knowledge base provides a solid data foundation for subsequent version management, change tracing, revision reuse, and intelligent assisted design, helping to improve the digital management level and intelligent application capabilities of engineering drawings.

[0078] In some embodiments, a state machine is introduced, using feature differences as the first state layer and update type as the second state layer, including:

[0079] Based on the difference knowledge base, a first state layer is constructed using a hierarchical classification structure; a second state layer is constructed using normal updates and archived updates as version sources; the first state layer and the second state layer are cascaded to determine the state machine.

[0080] Specifically, a state machine is a model that describes behavioral changes under different conditions through a finite number of state nodes and their transition relationships. This state machine is used to hierarchically manage the differences and update types of drawing versions, enabling fine-grained tracking and control of the version lifecycle.

[0081] Specifically, the first state layer is based on feature differences, classifying them according to the difference features in the difference knowledge base to form a state hierarchy. Each node represents a difference feature state (such as size change, component addition, symbol adjustment, etc.). The second state layer is based on version update type, used to distinguish different types of updates such as normal updates and archived updates to form a state hierarchy. Each node represents a version update type state.

[0082] Specifically, firstly, based on the encoded feature descriptors in the difference knowledge base, groups are formed according to difference type (size change, structural change, symbol adjustment, etc.) to create a hierarchical classification structure. For example: size change, component addition, structural optimization, and annotation adjustment. Then, based on the source type of the version update, a second state layer is formed, distinguishing between regular updates and archived updates. For example: regular updates include routine design modifications and local optimizations; archived updates include major version releases and historical archives.

[0083] Furthermore, the first and second state layers are cascaded to form a multi-dimensional state machine. Each state node is uniquely determined by "difference feature + update type". For example: [size change, normal update], [structural optimization, archive update], [component addition, normal update].

[0084] The above process, by introducing a state machine with difference characteristics as the first state layer and update type as the second state layer, achieves structured and hierarchical management of the entire drawing version update process. This state machine can accurately reflect the specific differences of each version update and their attribution type, providing technical support for automated version flow, intelligent archiving, and change tracing, thereby improving management efficiency and intelligence.

[0085] In some embodiments, a mapping association is established between the state machine, the virtual mapping layer, and the distributed drawing database.

[0086] Furthermore, based on the same method and process used to establish the mapping relationship between the virtual mapping layer and the distributed drawing database, a corresponding mapping association can be established between the state machine, the virtual mapping layer, and the distributed drawing database. The virtual mapping layer acts as an intermediary bridge, logically binding each state node in the state machine to the drawing data entries in the database, enabling state-driven data retrieval, updating, and management.

[0087] Specifically, firstly, each state node of the state machine is uniquely identified and indexed in the virtual mapping layer. Then, a one-to-one mapping is established between the state nodes and specific drawing version data entries in the distributed drawing database. For example, each state node corresponds to one or more drawing version records in the database, achieving a logical binding. When the state machine undergoes a state transition (such as a change in difference characteristics or update type), the virtual mapping layer adjusts the corresponding database pointers or indexes in real time, enabling state-driven data access and management.

[0088] By establishing a mapping relationship between the state machine, the virtual mapping layer, and the distributed drawing database, efficient linkage between layers and data consistency management are achieved. This mechanism not only improves the retrieval efficiency and accuracy of drawing version data but also supports automated data flow and distributed management capabilities under complex conditions.

[0089] S300: Based on the quadratic code and the state machine, construct a microservice architecture within the drawing management platform, receive version tracing tasks, perform task decoupling, execute code tracing and state layer cascade tracing in parallel, verify the tracing results, and determine the version tracing results.

[0090] Specifically, the drawing management platform is divided into multiple independently deployed and autonomously operating microservice units according to functional modules, forming a microservice architecture. The services communicate with each other through interfaces to achieve task decoupling and elastic scaling.

[0091] For example, multiple microservice units are deployed within the drawing management platform, including version tracing service, code parsing service, state machine tracing service, and result verification service. These services communicate decoupledly via message queues or APIs. When the platform receives a version tracing request from a user, it can distribute the task to the relevant microservices through the task scheduling module, supporting concurrent processing.

[0092] Specifically, the received version tracing task is structured to obtain the code tracing task and the state-level cascade tracing task. The code tracing task parses and locates the target drawing version based on the input quadruple code and retrieves its historical evolution link. The state-level cascade tracing task is based on a state machine model, tracing the version state transition process along the state-level link and extracting relevant change nodes and their attributes.

[0093] The microservice architecture based on quadrature coding and state machine model described above achieves efficient decoupling and parallel processing of drawing version tracing tasks. This approach not only improves the response speed and accuracy of version tracing but also enhances scalability and fault tolerance, providing a solid technical guarantee for intelligent version management and tracing in large-scale collaborative design environments.

[0094] In some embodiments, after receiving the version retrospective task, the process includes:

[0095] The authorization authentication port is started within the drawing management platform; the version traceability task is received, and user authorization authentication is performed to determine the authentication information; based on the authentication information, the virtual mapping layer is temporarily marked with authorized and non-authorized parts.

[0096] Specifically, the authentication port refers to the interface module in the management platform dedicated to handling user authentication and permission verification, ensuring the security of data access and operations. By authenticating users through the authentication port, the virtual mapping layer can be divided into authorized and non-authorized parts based on the authentication result. That is, within the virtual mapping layer, accessible data or mapping relationships are dynamically divided into authorized (permitted) and non-permitted (non-permitted) parts according to user permissions, achieving fine-grained data access control.

[0097] Specifically, upon receiving a version tracing task, the system first automatically starts or invokes the authentication port to authenticate the requesting user, including identity verification and permission level checks, obtaining authentication information (such as user ID, role, and permission scope). Then, based on this authentication information, the data mapping relationships involved in the virtual mapping layer are temporarily marked. For example, data entries or status nodes that the user has permission to access are marked as "permissioned parts," while those that the user does not have permission to access are marked as "non-permissioned parts." This marking process can be implemented by setting access flags and dynamically filtering mapping indexes to ensure that subsequent tracing operations are limited to data within the user's permission scope.

[0098] Through the above process, pre-verification of permissions and dynamic data partitioning for version tracing tasks are achieved, ensuring the compliance and data security of tracing operations and preventing unauthorized access and data leakage. Furthermore, the permission marking mechanism based on the virtual mapping layer can flexibly support fine-grained access control for multiple users and roles, thereby further enhancing the platform's security and manageability.

[0099] In some embodiments, task decoupling is performed, and code tracing and state layer cascade tracing are executed in parallel. The tracing results are verified, and the version tracing results are determined, including:

[0100] Based on the microservice architecture, the version tracing task is decoupled from the content level and the meta level to determine the first tracing dimension and the second tracing dimension. For the first tracing dimension, encoding location based on quadrature encoding and permission partial location based on the virtual mapping layer are performed to determine the first tracing result. For the second tracing dimension, hierarchical cascading location based on the state machine and permission partial location based on the virtual mapping layer are performed to determine the second tracing result. The first tracing result and the second tracing result are compared to determine the version tracing result.

[0101] Specifically, based on the microservice architecture, the received version tracing task is first decoupled at the content level and the meta level, and the first tracing dimension (content layer tracing based on quadrature encoding) and the second tracing dimension (meta-level cascade tracing based on state machine model) are determined respectively.

[0102] Specifically, for the first traceability dimension, the target drawing version is accurately located using quadruple coding. At the same time, the permission part is located based on the virtual mapping layer to ensure that the traceability operation is limited to the range of drawing data that the user has permission to access. If it falls within the range of permissions, the first traceability result is generated and output.

[0103] Specifically, for the second traceability dimension, the evolution process of the target drawing version and related state nodes in the state chain are located based on the hierarchical cascading mechanism of the state machine. At the same time, the authorized part is located based on the virtual mapping layer to limit the traceability scope. If it belongs to the authorized scope, the second traceability result is generated and output.

[0104] Furthermore, the first and second traceability results are cross-checked to verify their consistency in terms of version information, permission scope, etc. If the check passes, the final version traceability result is output; if the check fails, the exception handling process is triggered, prompting manual review or automatic retry.

[0105] By implementing the above-mentioned parallel decoupling and multi-dimensional tracing, permission restriction and result verification processes, the accuracy, security and response efficiency of drawing version tracing can be significantly improved, meeting the version management needs in a large-scale collaborative environment.

[0106] In some implementations, verifying the first traceability result with the second traceability result to determine the version traceability result includes:

[0107] If the first traceability result is consistent with the second traceability result, the traceability version drawing is retrieved and displayed on the interface according to the mapping of the virtual mapping layer - distributed drawing database; if the first traceability result is inconsistent with the second traceability result, a secondary verification node is triggered to retrieve the verified mapping and display the drawing.

[0108] Specifically, if the first traceability result is consistent with the second traceability result, the drawing data of the target traceability version is automatically retrieved based on the mapping relationship between the virtual mapping layer and the distributed drawing database, and displayed on the user interface to realize the automated presentation of the drawing.

[0109] Specifically, if the first traceability result is inconsistent with the second traceability result, a secondary verification node is automatically triggered. For example, a verification pop-up window is generated to prompt the user to perform manual verification or supplementary confirmation. After the user completes the verification operation, the corresponding mapping data is retrieved based on the verification result. If the secondary verification passes, the traceability version of the drawing is displayed on the interface to ensure the accuracy and compliance of the traceability results.

[0110] Through the above-mentioned automatic verification and secondary verification mechanisms, the reliability and traceability of version tracing results can be achieved. The introduction of an access verification mechanism during the tracing process ensures that users can only access the drawings and update history that they are authorized to access. At the same time, secondary verification is only performed when consistency fails, which ensures the efficiency of automated processing and takes into account the ability to intervene manually in abnormal situations, thereby improving the intelligence and security of the drawing management platform.

[0111] In summary, the multi-level CAD drawing version traceability management method provided by this invention has the following technical effects:

[0112] By introducing a four-tuple coding method encompassing four dimensions—stage, software version, purpose, and server—CAD drawings are identified and managed. Through targeted and differentiated coding oriented towards the version update process, a subset of feature descriptions is constructed, leading to a difference knowledge base. Drawing feature differences serve as the first state layer, and update types (including regular updates and archived updates) as the second state layer, establishing a state transition mechanism. Within the drawing management platform, based on the aforementioned four-tuple coding and state transition mechanism, a microservice architecture is built to receive drawing version tracing tasks. During task processing, task decoupling operations are performed, tracing the coding link and the state-level link in parallel. Through cross-validation of the tracing results, the version tracing result of the target drawing is ultimately determined. This achieves dual-dimensional information mining of coding and state, improving the accuracy, completeness, and reliability of drawing version tracing.

[0113] Example 2, as Figure 2 This is a schematic diagram of the structure of a multi-level CAD drawing version traceability management platform according to the present invention. For example, Figure 1 The flowchart of a multi-level CAD drawing version traceability management method of the present invention can be illustrated as follows: Figure 2 The structure shown is implemented.

[0114] Based on the same concept as the multi-level CAD drawing version traceability management method in the above embodiment, the present invention also provides a multi-level CAD drawing version traceability management platform comprising:

[0115] Quadruple encoding introduction module 11 is used to introduce quadruple encoding, wherein the quadruple encoding is set according to the stage of CAD drawing-software version-purpose-server.

[0116] The feature descriptor and difference knowledge base construction module 12 is used to construct a difference knowledge base by introducing feature descriptors based on the directional focus and difference encoding of the version update process. It introduces a state machine with feature difference as the first state layer and update type as the second state layer. The update type includes normal update and archived update.

[0117] The architecture construction and traceability execution module 13 is used to construct a microservice architecture within the drawing management platform based on the quadrature code and the state machine, receive version traceability tasks, decouple the execution tasks, execute code traceability and state layer cascade traceability in parallel, verify the traceability results, and determine the version traceability results.

[0118] In some embodiments, the quadrature encoding introduction module 11 includes:

[0119] The unidirectional coding chain construction unit is used to construct a unidirectional coding chain for each coding element, with the CAD drawing stage, software version, purpose, and server as multiple coding elements.

[0120] The quadruple coding introduction and integration unit is used to integrate the unidirectional coding chain in parallel, establish the association between the unidirectional coding chain and the distributed drawing database, and set coding rules as quadruple coding introduction.

[0121] In some implementations, the quadrature encoding introduction and integration unit in the quadrature encoding introduction module 11 includes:

[0122] The virtual mapping layer establishment unit is used to establish a virtual mapping layer for the distributed drawing database, wherein the virtual mapping layer is a unified data system constructed by introducing coded elements.

[0123] The mapping association construction unit is used to establish the mapping association between the unidirectional encoding chain, the virtual mapping layer, and the distributed drawing database.

[0124] In some embodiments, the feature descriptor and difference knowledge base construction module 12 includes:

[0125] The version update relationship determination unit is used to determine the upstream drawing version and the downstream drawing version as the version is updated.

[0126] The drawing focus point determination unit is used to perform directional focusing on the upstream drawing version and the downstream drawing version based on the differences in elements, and determine the drawing focus point.

[0127] The feature descriptor determination unit is used to determine the knowledge base encoding rules, perform differential encoding on the focal points of the drawing, and determine the feature descriptor of the update node.

[0128] The difference knowledge base update unit is used to add the feature descriptor into the difference knowledge base.

[0129] In some embodiments, the feature descriptor and difference knowledge base construction module 12 includes:

[0130] The first state layer construction unit is used to construct the first state layer according to the differential knowledge base in a hierarchical classification structure.

[0131] The second state layer building unit is used to build the second state layer using normal updates and archived updates as version sources.

[0132] A state machine determination unit is used to cascade the first state layer and the second state layer to determine the state machine.

[0133] In some embodiments, the architecture construction and traceability execution module 13 includes:

[0134] The authorization port opening unit is used to enable the authorization port within the drawing management platform.

[0135] The user permission authentication and authentication information determination unit is used to receive the version tracing task, perform user permission authentication, and determine authentication information.

[0136] The virtual mapping layer permission marking unit is used to temporarily mark the permission part and the non-permission part of the virtual mapping layer according to the authentication information.

[0137] In some embodiments, the architecture construction and traceability execution module 13 further includes:

[0138] The task decoupling and traceability dimension determination unit is used to decouple the execution content layer and meta layer of the version traceability task according to the microservice architecture, and determine the first traceability dimension and the second traceability dimension.

[0139] The first traceability result determination unit is used to perform encoding location based on quadrature encoding and permission part location based on the virtual mapping layer for the first traceability dimension, and determine the first traceability result.

[0140] The second traceability result determination unit is used to perform hierarchical cascading positioning based on the state machine and permission-based partial positioning based on the virtual mapping layer for the second traceability dimension, and determine the second traceability result.

[0141] The version tracing result determination unit is used to verify the first tracing result and the second tracing result to determine the version tracing result.

[0142] In some implementations, the version tracing result determination unit in the architecture construction and tracing execution module 13 includes:

[0143] A consistency result processing unit is used to retrieve the traced version drawing and display it on the interface if the first traceability result is consistent with the second traceability result, according to the mapping of the virtual mapping layer-distributed drawing database.

[0144] The inconsistent result processing and verification unit is used to trigger a secondary verification node and execute the verified mapping retrieval and drawing display if the first traceability result is inconsistent with the second traceability result.

[0145] It should be understood that the focus of the embodiments mentioned in this specification is their difference from other embodiments. The specific embodiments in the aforementioned Embodiment 1 are also applicable to the multi-level CAD drawing version traceability management platform described in Embodiment 2. For the sake of brevity, they will not be further elaborated here.

[0146] It should be understood that the embodiments disclosed in this invention and the above description enable those skilled in the art to implement this invention. However, this invention is not limited to the embodiments mentioned above. It should be understood that those skilled in the art can still modify the technical solutions described in the foregoing embodiments or make equivalent substitutions for some of the technical features; and these modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this invention, and should all be included within the protection scope of this invention.

Claims

1. A multi-level CAD drawing version traceability management method, characterized in that, include: A quaternion encoding is introduced, wherein the quaternion encoding is set according to the stage of the CAD drawing, the software version, the purpose, and the server. By focusing on the version update process and using difference encoding, feature descriptors are introduced to build a difference knowledge base. With feature difference as the first state layer and update type as the second state layer, a state machine is introduced. The update type includes normal update and archived update. Based on the quadratic code and the state machine, a microservice architecture is constructed within the drawing management platform to receive version tracing tasks, perform task decoupling, execute code tracing and state layer cascade tracing in parallel, verify the tracing results, and determine the version tracing results. The introduction of quadruple encoding includes: Using the stage of CAD drawing, software version, purpose, and server as multiple coding elements, a unidirectional coding chain is constructed for each coding element; The unidirectional coding chains are integrated in parallel, the association between the unidirectional coding chains and the distributed drawing database is established, and coding rules are set and introduced as quadruple codes. The establishment of the association between the unidirectional coding chain and the distributed drawing database includes: For the distributed drawing database, a virtual mapping layer is established, wherein the virtual mapping layer is a unified data system constructed by introducing coded elements; Establish the mapping association between the unidirectional encoding chain, the virtual mapping layer, and the distributed drawing database; The execution tasks are decoupled, and the code tracing and state layer cascade tracing are performed in parallel. The tracing results are verified, and the version tracing results are determined, including: Based on the microservice architecture, the content layer and meta layer of the version tracing task are decoupled to determine the first tracing dimension and the second tracing dimension. For the first traceability dimension, perform encoding location based on quadrature encoding and permission-based location based on the virtual mapping layer to determine the first traceability result; For the second traceability dimension, perform hierarchical cascaded positioning based on the state machine and partial positioning based on the permission of the virtual mapping layer to determine the second traceability result; The first traceability result and the second traceability result are compared to determine the version traceability result.

2. The multi-level CAD drawing version traceability management method as described in claim 1, characterized in that, By focusing on the version update process and using difference encoding, feature descriptors are introduced to construct a difference knowledge base, including: With each version update, the upstream and downstream drawing versions are determined. The upstream drawing version and the downstream drawing version are targeted and focused based on the differences in elements to determine the drawing focus point; Determine the knowledge base coding rules, perform differential coding on the focal points of the drawing, and determine the feature descriptors of the update nodes; The feature descriptors are added to the differential knowledge base.

3. The multi-level CAD drawing version traceability management method as described in claim 2, characterized in that, A state machine is introduced, with feature differences as the first state layer and update type as the second state layer, including: Based on the aforementioned differential knowledge base, a first state layer is constructed using a hierarchical, cascaded classification structure. A second state layer is constructed using regular updates and archived updates as version sources; The state machine is determined by cascading the first state layer and the second state layer.

4. The multi-level CAD drawing version traceability management method as described in claim 3, characterized in that, Establish the mapping association between the state machine, the virtual mapping layer, and the distributed drawing database.

5. The multi-level CAD drawing version traceability management method as described in claim 1, characterized in that, After receiving the version retrospective task, the following is included: Start the access authentication port within the drawing management platform; Receive the version tracing task, perform user authorization authentication, and determine the authentication information; Based on the authentication information, the virtual mapping layer is temporarily marked with authorized and non-authorized portions.

6. The multi-level CAD drawing version traceability management method as described in claim 1, characterized in that, By comparing the first traceability result with the second traceability result, the version traceability result is determined, including: If the first traceability result is consistent with the second traceability result, the traceability version drawing is retrieved and displayed on the interface according to the mapping of the virtual mapping layer-distributed drawing database; If the first traceability result is inconsistent with the second traceability result, a secondary verification node is triggered to execute the verification mapping retrieval and drawing display.

7. A multi-level CAD drawing version traceability management platform, characterized in that, A method for implementing a multi-level CAD drawing version traceability management system as described in any one of claims 1 to 6 includes: The quaternion encoding introduction module is used to introduce quaternion encoding, wherein the quaternion encoding is set according to the stage of CAD drawing-software version-purpose-server setting; The feature descriptor and difference knowledge base construction module is used to construct a difference knowledge base by introducing feature descriptors based on the targeted focus and difference encoding of the version update process. It introduces a state machine with feature difference as the first state layer and update type as the second state layer. The update type includes normal update and archived update. The architecture construction and traceability execution module is used to build a microservice architecture within the drawing management platform based on the quadrature code and the state machine, receive version traceability tasks, decouple the execution tasks, execute code traceability and state layer cascade traceability in parallel, verify the traceability results, and determine the version traceability results.

Images