Method and System for Synchronous Update of Power Distribution Network Engineering Model and CAD Graphics
By using a combination of stable engineering semantic identifiers and entity handles to bind records in the synchronous update system of distribution network engineering models and CAD drawings, the problems of unstable entity recognition and insufficient detection of concurrent changes in the synchronous update of distribution network engineering models and CAD drawings are solved, and the consistency of models and drawings and safe rollback in cross-process environment are realized.
Patent Information
- Application Number
- CN202611276342.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-08-21
- Publication Date
- 2026-11-17
AI Technical Summary
In existing technologies, the synchronous update of power distribution network engineering models and CAD drawings suffers from problems such as unstable entity recognition, insufficient detection of concurrent changes, and insecurity of repeated execution and state rollback. In particular, it is difficult to maintain the consistency between the model and the drawings when running across processes or devices.
By combining stable engineering semantic identifiers with entity handles in the binding record, and combining engineering object type and CAD entity geometric fingerprint, multi-layer verification and persistent execution logs are performed before proposal confirmation to ensure the accuracy and idempotency of synchronous updates, and to safely roll back in the event of failure or uncertainty.
It enables accurate location of CAD entities corresponding to engineering objects under cross-process or cross-device conditions, detects concurrent changes, avoids repeated execution, ensures consistency between models and graphics, and avoids overwriting subsequent edits during rollback, thereby improving the reliability and security of synchronous updates.
Smart Images

Figure FT_1 
Figure FT_2 
Figure FT_3
Abstract
Description
Technical Field
[0001] This invention relates to the fields of engineering data processing, computer-aided design, and distributed transaction consistency, and in particular to a method and system for verifiable, idempotent, and recoverable synchronous updates between a power distribution network engineering model and computer-aided design (CAD) drawings. Background Technology
[0002] Distribution network design typically involves maintaining both a structured engineering model and CAD drawings. The engineering model stores information such as poles or pole locations, line sections, spans, material properties, and mechanical calculation results; the CAD drawings store main elements, schematic elements, annotations, and tables for designers to view and edit. The same engineering object in the engineering model often corresponds to multiple entities in the CAD document.
[0003] In current practices, engineering models and CAD drawings are often linked through import / export, coordinate lookup, layer filtering, entity handles, or manual redrawing. Relying solely on coordinates or layers cannot reliably identify engineering objects; relying solely on entity handles cannot detect if entities have been edited, replaced, or moved by others. When engineering services and CAD clients run across processes or devices, changes to the engineering version or drawings may occur after the proposal is generated but before execution.
[0004] Furthermore, native CAD transactions can only guarantee a commit or rollback within a single client transaction, and cannot independently resolve cross-process consistency issues such as network interruptions, client crashes, or failed execution result transmissions. If the server retryes directly due to not receiving a successful result, the same entity may be shifted twice; if the engineering model is directly compensated back to its original state while the CAD client has actually committed, the engineering model and the drawing will contradict each other.
[0005] When rolling back a successful change, the target entity may be modified again by the designer. If the entity's state is restored directly to the old state without verifying the state after the successful change, subsequent manual edits will be overwritten. Therefore, a synchronous update solution is needed that can stably associate engineering objects and CAD entities, identify concurrent changes, avoid duplicate execution, distinguish between explicit failures and uncertain states, and safely roll back. Summary of the Invention
[0006] The present invention aims to solve at least the following technical problems: how to accurately locate one or more CAD entities corresponding to engineering objects under the condition that the engineering model server and CAD client are independent of each other; how to detect concurrent changes of engineering version, CAD document or single entity during proposal confirmation and drawing execution; how to avoid repeated changes caused by communication retries; how to keep the model and drawing verifiable when the execution result is clearly failed or uncertain; and how to roll back successful changes without overwriting subsequent edits.
[0007] To address the aforementioned issues, this invention provides a method for synchronously updating a power distribution network engineering model and CAD drawings, executed by a system comprising an engineering model server and a CAD client. The system establishes a semantic binding record between engineering objects and at least one CAD entity using a stable engineering semantic identifier. The semantic binding record includes at least the engineering project identifier, engineering object type, stable engineering semantic identifier, CAD entity handle, CAD document fingerprint, entity geometric fingerprint, and the conversion relationship between engineering coordinate units and drawing coordinate units.
[0008] Upon receiving an update request for the target project object, the server reads the current active project version and semantic binding record, generating update candidates that are not directly written to the CAD document. These update candidates include the target project object's pre-update parameters, post-update parameters, project cascade recalculation results, and controlled geometric transformation parameters of the corresponding CAD entity. The server then writes a snapshot of the binding of the current active project version, CAD document fingerprint, and semantic binding record to the pending update proposal.
[0009] Upon receiving confirmation of the pending update proposal, the server rereads and verifies the current active project version, the current fingerprint of the CAD document, and the bound snapshot. Only when all items are consistent with the proposal baseline will the server create the updated project version and generate a set of CAD operations according to the conversion relationship between project coordinate units and drawing coordinate units. Each CAD operation carries at least a deterministic operation identifier, an expected entity handle, an expected stable project semantic identifier, an expected entity geometric fingerprint, and controlled geometric transformation parameters.
[0010] Before initiating a native graphic transaction, the CAD client verifies the fingerprint of the current CAD document. Within the native graphic transaction, the CAD client reads the target entity according to the expected entity handle, verifies the stable engineering semantic identifier carried by the entity and the current entity's geometric fingerprint. If verification is successful, it executes geometric transformations from the whitelist and records the state before, after, and the geometric fingerprint after the transformation. The CAD client utilizes persistent execution logs and deterministic operation identifiers outside the native graphic transaction to prevent identical operations from being executed repeatedly.
[0011] The server retrieves the execution results of the CAD operation set. For operations that are clearly failed and confirmed not to have been committed, the server creates a new compensation project version based on the project version before the change. For operations that may have been applied but whose execution status is uncertain, the server disables automatic replay and automatic compensation, and marks the update as pending verification. For successful results, the server updates the semantic binding record with the transformed geometric fingerprint and associates it with the project version and the CAD drawing change set.
[0012] When rolling back a successful geometric change set, the system reads the transformed geometric fingerprint and the state before the transformation for each operation, and uses the transformed geometric fingerprint as a prerequisite for rolling back to generate a reverse geometric transformation. Rollback is only performed if the current geometric fingerprint of the target entity is still equal to the transformed geometric fingerprint; if they are not equal, it indicates that other edits have occurred after the successful change, and the system stops rolling back and reports a conflict.
[0013] This invention also provides a system for synchronously updating power distribution network engineering models and CAD drawings, including an engineering model server, a semantic binding storage unit, an update proposal and operation generation unit, a CAD client, and a result verification and compensation unit. Each unit is configured to execute the aforementioned methods. The units can be deployed in the same electronic device or in different electronic devices via an authenticated network or inter-process communication connection.
[0014] The present invention also provides an electronic device and a non-transitory computer-readable storage medium. When the processor of the electronic device executes a computer program in the memory, or when the computer program in the storage medium is executed by the processor, a system including an engineering model server and a CAD client performs the aforementioned method. Beneficial effects
[0015] Compared to finding entities by coordinates, layers, or single handles alone, the combination of stable engineering semantic identifiers and handles can more accurately identify the CAD entities corresponding to engineering objects and support multiple graphic representations for one engineering object.
[0016] By verifying the project version, CAD document fingerprint, and bound snapshot during proposal confirmation, and continuing to verify the single entity geometric fingerprint in CAD transactions, this invention forms a hierarchical concurrent detection at the document and entity levels, which can prevent expired proposals or manually modified entities from being overwritten before transformation.
[0017] By combining deterministic operation identifiers, persistent execution logs, and native CAD transactions, repeated requests will not apply geometric transformations repeatedly; by distinguishing between explicit failures and uncertain execution states, erroneous replays or incorrect compensation of the engineering model are avoided when the CAD has actually been committed.
[0018] By using the updated geometric fingerprint as a prerequisite for rollback, the system can identify successful manual edits after an update, reducing the risk of rollback overwriting subsequent design deliverables. The engineering version uses an append-only approach to create a compensating version without rewriting historical versions, which facilitates auditing and traceability. Attached Figure Description
[0019] Figure 1 This is a schematic diagram of the overall system structure according to an embodiment of the present invention.
[0020] Figure 2 This is a schematic diagram of a semantic binding record structure according to an embodiment of the present invention.
[0021] Figure 3 This is a flowchart illustrating the overall process of a synchronization update method according to an embodiment of the present invention.
[0022] Figure 4 This is a flowchart illustrating the layered verification process of engineering version, document fingerprint, and entity geometric fingerprint according to an embodiment of the present invention.
[0023] Figure 5 This is a flowchart illustrating the CAD client transaction and idempotent execution process according to an embodiment of the present invention.
[0024] Figure 6 This is a status diagram for checking and compensating the execution results of an embodiment of the present invention.
[0025] Figure 7 This is a flowchart illustrating a safe rollback process according to an embodiment of the present invention.
[0026] Figure 8 This is a schematic diagram of the synchronous movement of a power distribution pole position and its multiple CAD entities according to an embodiment of the present invention. Detailed Implementation
[0027] The embodiments of the present invention will be further described below with reference to the accompanying drawings. These embodiments are used to explain the present invention and are not intended to limit the scope of protection to a particular CAD software, communication protocol, operating system, programming language, or product brand. Those skilled in the art can make equivalent substitutions for deployment methods and data fields without departing from the concept of the present invention.
[0028] "Engineering Object" refers to an object in the engineering model that has an independently identifiable identity, such as distribution network pole positions, towers, line sections, conductors, equipment, corresponding labeled objects, or engineering table entries. "Stable Engineering Semantic Identifier" is an identifier used to represent the same engineering object when the engineering object is moved, the display method changes, or the engineering version is iterated. It does not use the current coordinates as its only component.
[0029] An "entity handle" is an identifier used to locate entities within a CAD document. An "entity geometric fingerprint" is a value obtained by hashing the normalized entity state, used to detect whether the entity has undergone changes that affect synchronous updates. A "document fingerprint" is a value obtained by normalizing the CAD document's identity and the selected baseline state, used to prevent operations from being applied to incorrect documents or incorrect document versions.
[0030] like Figure 1 As shown, the synchronous update system 100 includes an update request unit 110, an engineering model server 120, a semantic binding storage unit 130, an update proposal and operation generation unit 140, a CAD client 150, a result verification and compensation unit 160, and an audit and version storage unit 170. The update request unit 110 receives an update request 300. The update proposal and operation generation unit 140 generates an update proposal 310 and sends it to the update request unit 110 for confirmation. After confirmation and re-verification, it sends a CAD operation set 320 to the CAD client 150. The CAD client 150 returns an execution result 330 to the result verification and compensation unit 160 and can receive a rollback request 340 sent by the result verification and compensation unit 160.
[0031] The engineering model server 120 can be a server process or a local service; the CAD client 150 can run as a plugin within CAD software or as an adapter process with a controlled graphic editing interface. The two can connect via interfaces based on hypertext transfer, remote procedure calls, message queues, or local inter-process communication. The transmission method used by the interface does not alter the semantic binding, layered verification, idempotent execution, and fractal recovery mechanisms of this invention.
[0032] like Figure 2 As shown, the semantic binding record 200 includes a project identifier 210, an engineering object type 220, a stable engineering semantic identifier 230, an entity handle 240, a document fingerprint 250, an entity geometric fingerprint 260, a unit conversion relationship 270, and an operation / change identifier 280. Depending on the needs, the semantic binding record 200 may also include a CAD document identifier, entity type, layer, binding status, creation time, update time, and the most recently successful engineering version.
[0033] For the same engineering object, a binding record group can be stored. Taking a pole position as an example, the binding record group can contain three CAD entities: the pole position main block, the route schematic element, and the text annotation. Each CAD entity has its own entity handle 240 and entity geometric fingerprint 260, but they share the engineering object type 220 and the stable engineering semantic identifier 230. Thus, when the position of the engineering object changes, all related expressions can be moved synchronously without having to guess the entity identity using neighboring coordinates.
[0034] In one embodiment, the CAD client writes the project object type 220 and the stable project semantic identifier 230 into the entity extension data. During an update, the CAD client not only locates the entity by its entity handle 240 but also reads the extension data for semantic verification. Even if the original handle incorrectly points to a different entity, the change will be rejected due to semantic inconsistency.
[0035] The physical geometric fingerprint 260 can be obtained using the following formula: Where S_e represents the entity state, CANONICALIZE indicates normalization according to a fixed field order, fixed numerical precision, and fixed character encoding, and HASH represents anti-collision hashing. Entity state can include handle, entity type, layer, visibility, color or linetype, geometric range, and parameters corresponding to the entity type. During normalization, fields that affect the geometric state or controlled transformation determination of the target entity are retained, while volatile display information that does not affect the geometric state of the target entity is excluded; such volatile display information includes, for example, temporary selection of highlight state, current viewport refresh state, display cache identifier, or display update time. Color, linetype, and visibility can be determined according to preset business rules to determine whether they belong to the state fields that need to be retained, so as to avoid the same entity generating different entity geometric fingerprints simply due to unrelated display state changes. Block entities can include insertion point, rotation angle, and scaling; polylines can include vertices, convexity, and line width; curves can include parameter endpoints or sampling points; text can include insertion point, alignment point, rotation, and style; annotations and viewports can include their unique geometric parameters.
[0036] The document fingerprint 250 can be calculated from at least two of the following: a unique document identifier, a document normalization path or database identifier, selected document attributes, and version status. The document fingerprint answers the question "Is the current operation still targeting the same document state at the time the proposal was generated?", while the entity geometry fingerprint answers the question "Is the located individual entity still in the geometric state at the time of the generation operation?". The two cannot be substituted for each other.
[0037] The unit conversion relationship 270 includes the scaling factor k between engineering coordinate units and drawing coordinate units. When the displacement vector in the engineering model is Δp_e=(Δx_e, Δy_e, Δz_e), the drawing displacement vector is Δp_d=k·Δp_e. For example, when engineering coordinates are expressed in meters and drawing coordinates are expressed in millimeters, k=1000. If the unit type or scaling factor is not supported, the system will refuse to update it before generating the CAD operation set.
[0038] like Figure 3As shown, in step S101, update request unit 110 receives update request 300. The update request includes at least a project identifier, a stable engineering semantic identifier of the target engineering object, and expected update parameters. The expected update parameters may be target coordinates, relative translation, rotation, or constrained engineering parameter changes.
[0039] In step S102, the engineering model server 120 reads the current active project version and queries the binding record group of the target project object. The server verifies whether the project and CAD session match, whether the session is online and writable, whether the client declares support for entity update capability, whether the document fingerprint exists, and whether unit conversion relationships are supported. If any precondition is not met, only an error or pending status is returned, and no executable graphical operation is generated.
[0040] In step S103, the update proposal and operation generation unit 140 generates update candidates. The update candidates retain the parameters of the target engineering object before and after the update, and call the engineering calculation logic to obtain the cascaded recalculation results. For the relocation of distribution network poles, the cascaded recalculation results may include the span on both sides of the target pole, conductor stress, sag, safety distance, material quantity, or other engineering quantities affected by the position change.
[0041] Update proposal 310 only indicates a candidate and is not directly written to the CAD document. Update proposal 310 saves at least the proposal identifier, the base project version, the parameters of the target project object before and after the update, the cascading recalculation results, the document fingerprint 250, the unit conversion relationship 270, and the binding snapshot. The binding snapshot includes the entity handle 240 and the entity geometric fingerprint 260 for each entity in the binding record group.
[0042] In step S104, the system receives explicit confirmation of the update proposal 310. The confirmation information may include a one-time confirmation identifier or authorization information associated with the proposal identifier, to avoid equating the generation of a candidate with approval. The confirmation mechanism can be implemented by a manual interface, an authenticated business interface, or constrained automatic rules, and its function is to trigger a second technical status verification, rather than an abstract administrative approval itself.
[0043] like Figure 4 As shown, the system first compares the current active project version with the baseline project version in the proposal in step S201; then, in step S202, it compares the current fingerprint of the CAD document with document fingerprint 250; subsequently, in step S203, it compares the currently bound record group with the bound snapshot. If any comparison is inconsistent, in step S204, the proposal is marked as expired or conflicting, and an instruction to regenerate the proposal is returned. If all comparisons are consistent, in step S205, the updated project version is created and operation generation begins.
[0044] The updated project version uses an append-only version record, including the updated project objects, cascaded recalculation results, base version identifier, proposal identifier, and creation reason. Existing historical versions are not overwritten in place. This allows for the creation of compensatory versions in case of subsequent confirmed failures, without needing to delete existing audit facts.
[0045] In step S105, the update proposal and operation generation unit 140 converts the displacement in engineering coordinate units to the displacement in drawing coordinate units according to the unit conversion relationship 270, and generates an operation for each transformable entity in the bound record group. The whitelist of operations can include entity translation, rotation around a specified center, and restoration of previous transformations, and can set the maximum translation amount, maximum rotation amount, allowed entity types, and allowed layer range. Any commands or scripts not on the whitelist are not executed by this update method.
[0046] Each operation carries a deterministic operation identifier. The deterministic operation identifier can be generated using the following formula: Wherein, P_id is the project identifier, P_ver is the base or target project version identifier, Q_id is the proposal identifier, O_id is the stable project semantic identifier, and N_op is the operation sequence number within the binding record group. The same proposal, the same project version, and the same target entity generate the same operation identifier; new proposals or new versions generate different operation identifiers.
[0047] like Figure 5 As shown, in step S301, the CAD client 150 receives the CAD operation set 320 and checks whether each operation belongs to an allowed operation type. In step S302, the CAD client compares the current document fingerprint with the expected document fingerprint in the operation set; if they do not match, the entire operation set is rejected.
[0048] In step S303, the CAD client queries the persistent execution log to see if a deterministic operation identifier already exists. If a completion record exists, step S304 returns "Applied" and the transformed status of the record, without performing the geometric transformation again. If there is an execution intent but no reliable completion record, execution is not performed blindly, and the status is changed to pending verification.
[0049] For operations that have not been executed, the CAD client first writes the operation identifier, expected document fingerprint, expected entity handle, expected entity geometry fingerprint, and execution intent to the persistent execution log in step S305. The execution log can employ atomic replacement, write-through storage, or database transactions with equivalent durability, so that the client can still discover the previous execution intent even after abnormal exit.
[0050] The CAD client then initiates a native CAD drawing transaction. In step S306, the entity is read according to the expected entity handle; in step S307, the engineering object type and stable engineering semantic identifier in the entity's extended data are verified; in step S308, the current entity's geometric fingerprint is calculated and compared with the expected entity's geometric fingerprint. If the entity is missing, the semantics are inconsistent, or the geometric fingerprint is inconsistent, the CAD client aborts the native drawing transaction and returns an explicit failure or conflict.
[0051] In step S309, the CAD client records the normalized pre-transformation state, performs a controlled geometric transformation, and calculates the post-transformation state and the post-transformation geometric fingerprint. For forward transformations involving rotation and translation, rotation around a specified center can be performed before translation; the corresponding reverse recovery follows the reverse order, first translating in the opposite direction and then rotating in the opposite direction, to maintain the mathematical inverse relationship. For multiple entities, all operations can be committed in the same native graphical transaction or as a group of operations with atomicity guarantees.
[0052] In step S310, the CAD client writes the drawing change set identifier and deterministic operation identifier into the entity extension data or associated record, commits the native drawing transaction, and writes the pre-transformation state, post-transformation state, and post-transformation geometric fingerprint into the persistent execution log. The client then returns execution result 330 to the server. The native CAD transaction is responsible for the atomicity within the CAD database, while the persistent execution log is responsible for cross-process idempotency and state discovery after anomalies.
[0053] like Figure 6 As shown, a confirmed update can be in one of the following states: "Pending," "In Progress," "Successful," "Explicit Failure," "Possibly Applied but to be Verified," "Status Unknown," "Compensated," "Rolled Back," or "Conflicting." The status names can differ, but at least a clear failure that is definitely not committed must be distinguished from an uncertain result that may have been committed.
[0054] When the CAD client explicitly reports a document fingerprint mismatch, entity non-existence, semantic mismatch, entity geometric fingerprint conflict, or that the original transaction has been rolled back, the result verification and compensation unit 160 identifies the execution result as a clear failure. The server creates a new compensation project version based on the previous project version, sets it as the active project version, and retains the updated project version, the reason for failure, and the drawing operation records. This compensation is a new version, not a deletion or rewriting of a historical version.
[0055] When communication is interrupted near the CAD native transaction commit, the client exits abnormally, or a successful result is not delivered, a server timeout alone cannot determine whether the drawing has been changed. In this case, the result verification and compensation unit 160 sets the status to "possibly applied pending verification" or "status unknown," and does not automatically replay the same geometric transformation, nor does it immediately compensate the engineering model.
[0056] During verification, the system reads persistent execution logs, entity extended data, current document fingerprints, and current entity geometric fingerprints. If the logs or entity records contain the same operation identifier, and the current entity geometric fingerprint is equal to the candidate transformed geometric fingerprint, it can be determined that the operation has been applied; if no operation identifier exists and the current entity geometric fingerprint is still equal to the original geometric fingerprint, it can be determined that the operation has not been applied; if the current state is neither equal to the original state nor equal to the candidate transformed state, it is determined to be a conflict and manual confirmation is requested. The verification conclusion is recorded in the audit and version storage unit 170.
[0057] like Figure 7 As shown, in step S401, a rollback request 340 for a successful graphical change set is received. In step S402, the transformed geometric fingerprint and the state before transformation for each executed operation are read. In step S403, a reverse operation is generated for each entity. The reverse operation has an independent and definite rollback operation identifier, and the original transformed geometric fingerprint is set as the expected entity geometric fingerprint.
[0058] In step S404, the CAD client re-verifies the document fingerprint, entity handle, stable project semantic identifier, and current entity geometric fingerprint. If the current entity geometric fingerprint is not equal to the original transformed geometric fingerprint, the rollback stops in step S405 and a report of subsequent edits is submitted. If the verification matches, a reverse transformation is performed in step S406, and the restored project version is established and the binding record is updated in step S407. This avoids silently overwriting manually edited data after a successful update.
[0059] like Figure 8 As shown, in one embodiment, the engineering model includes a first pole position, a target pole position, and a third pole position arranged along the route. The target pole position is represented by the stable engineering semantic identifier POLE-003, which corresponds to three entities in the CAD document: main primitive, schematic primitive, and text annotation. The three entities each have an entity handle and an entity geometric fingerprint, forming the same binding record group.
[0060] The user requests that the target pole position be moved 2 meters along the positive x-axis. The engineering model server 120 generates an update proposal on the active engineering version V10: the target pole position is updated from (x, y) to (x+2, y), and the two spans between the target pole position and its adjacent pole positions are recalculated. The proposal saves V10, the current document fingerprint, the handles of the three entities, and the geometric fingerprint, but does not modify the CAD document at this time.
[0061] Upon confirming the proposal, the system re-verifies V10, the current document fingerprint, and the three binding records. After successful verification, the system establishes project version V11. Since project coordinates use meters while drawing coordinates use millimeters, the system generates operations for horizontal translation of 2000 drawing units for each of the three entities, with k=1000. Each operation has a different operation sequence number and deterministic operation identifier.
[0062] After verifying the document fingerprint in the CAD client (version 150), a native drawing transaction is initiated. The stable engineering semantic identifiers and geometric fingerprints of the three entities are checked one by one, their pre-transformation states are recorded, and the three entities are jointly translated by 2000 drawing units. If the operation is successful, the server saves the three transformed geometric fingerprints and associates V11 with the drawing change set. If, before submission, it is discovered that one of the entities has been manually moved, resulting in inconsistent geometric fingerprints, the native drawing transaction is rolled back, and the server establishes a compensating engineering version V12 based on the content of V10.
[0063] If the CAD client loses network connection after submitting the original drawing transaction but before returning the result, the server does not immediately resend the translation operation or immediately create a compensation version. Instead, it sets the status to "possibly applied, pending verification." After communication is restored, the client finds that all three operation identifiers exist and the entity fingerprint equals the recorded transformed fingerprint, returns "application complete," and the server then confirms that V11 matches the drawing change set.
[0064] If a subsequent request is made to roll back the corresponding graphic changes in V11, the system generates a reverse translation operation of 2000 drawing units, using the geometric fingerprints of the three entities after the successful V11 rollback as a prerequisite. If the text annotations have been moved by the designer and their current geometric fingerprints are no longer equal to the transformed fingerprints in V11, the system stops the rollback of that group and reports a conflict, without overwriting the subsequent edits.
[0065] Stable project semantic identifiers can be stored in CAD entity extended data, attributes, external binding databases, or a combination thereof; as long as the project semantics and the current state of the entity can be verified simultaneously during execution, the same technical effect can be achieved. The number of entities corresponding to a project object is not limited to three; it can also be bound to only one entity or more derived expressions.
[0066] Controlled geometric transformations, in addition to two-dimensional translation and rotation, can also include three-dimensional translation, scaling, parameterized block attribute updates, or constrained vertex updates that satisfy a whitelist and reversibility conditions. For transformations that cannot form a reliable inverse operation, the complete state before the transformation can be preserved and state restoration can be performed, but the geometric fingerprint of the successfully modified entity should still be verified before restoration.
[0067] Both entity geometric fingerprints and document fingerprints can use SHA-256 or a hash algorithm with equivalent collision resistance. The normalization field can be extended based on the CAD entity type, but the same rules and precision should be used when generating fingerprints before and after to avoid meaningless conflicts caused by differences in floating-point formats.
[0068] Engineering cascade recalculation can be completed synchronously by the engineering model server, or it can be written to the update proposal after the deterministic calculation task is completed. Regardless of the calculation module used, a write operation to the CAD entity is only generated after the technical status verification at the time of proposal confirmation passes.
[0069] This invention can be used in two-dimensional or three-dimensional power distribution network design drawings, and also for synchronizing preview layers or formal design layers between power distribution network engineering objects and CAD drawings. If used for preview layers, further restrictions can be placed on allowed layers, colors, or printable attributes; these security restrictions do not affect the core solutions of this invention regarding semantic binding, two-layer fingerprinting, idempotent execution, indeterminate state verification, and secure rollback. Figure Labels
[0070] 100—Synchronization Update System; 110—Update Request Unit; 120—Engineering Model Server; 130—Semantic Binding Storage Unit; 140—Update Proposal and Operation Generation Unit; 150—CAD Client; 160—Result Verification and Compensation Unit; 170—Audit and Version Storage Unit; 200—Semantic Binding Record; 210—Project Identifier; 220—Engineering Object Type; 230—Stable Engineering Semantic Identifier; 240—Entity Handle; 250—Document Fingerprint; 260—Entity Geometric Fingerprint; 270—Unit Conversion Relationship; 280—Operation / Change Identifier; 300—Update Request; 310—Update Proposal; 320—CAD Operation Set; 330—Execution Result; 340—Rollback Request.
Claims
1. Stable semantic one-to-many binding, proposal snapshot, secondary verification, unit / recalculation, semantic and fingerprint verification within CAD transactions, persistent idempotent logs, and result classification.
2. The same semantic object corresponds to multiple entities of subject / illustration / text and has fingerprints for each.
3. Recalculate the quantities of work, spans / stress, etc. before and after the update.
4. Whitelist translation / rotation, range verification, and unit conversion.
5. Normalize entity state hashes and type-related geometric fields.
6. Deterministic operation identifier and applied return.
7. Intent before the transaction, results after submission, and uncertainties.
8. Verify applied / unapplied / conflicting entries using logs, operation IDs, semantics, and previous / next fingerprints.
9. Additional compensation versions without rewriting history.
10. Upon successful completion, the fingerprint serves as a prerequisite for rollback and for reverse operations.
11. System modules and their mutual configuration.
12. Multi-entity grouping and binding.
13. Scope, project recalculation and unit conversion.
14. Return logs before and after transactions and for repeated operations.
15. Conditional rollback of the fingerprint sensor.
16. Conditional rollback with fingerprint verification.
17. Non-transitory computer-readable storage medium.
