Real-time remote collaboration method and system of three-dimensional factory design collaboration platform

Abstract

The invention discloses a real-time remote collaboration method and system for a three-dimensional factory design collaboration platform, and relates to the technical field of three-dimensional model collaboration design. The method comprises the following steps: responding to a storage operation of a local design user, and writing model data into a local three-dimensional design database; monitoring a write-in request of the three-dimensional design database in real time, and synchronously storing the model data to a platform database; dividing the model data into data blocks, and analyzing the data blocks based on a combined analyzer; comparing the identifier with the incremental updating record, and screening out the unsynchronized data blocks; transmitting the incremental data block to a remote server through a special link; and the remote server writes the incremental data into a remote three-dimensional design database and updates the model view. The method aims at eliminating the forced dependence of a traditional three-dimensional design platform on a business cooperation module, and meanwhile the design collision problem caused by cross-region synchronization delay is solved. And full-process real-time collaboration of three-dimensional design is realized, and a high-reliability collaboration base is provided for energy, chemical engineering and other major projects.

Description

Technical Field

[0001] This invention relates to the field of collaborative design technology for 3D models, and specifically to a real-time remote collaboration method and system for a collaborative 3D factory design platform. Background Technology

[0002] Against the backdrop of the nation's comprehensive promotion of digital transformation, the industrial sector, especially in factory design and construction, urgently needs to embrace digital change to achieve the core objectives of cost reduction and efficiency improvement, shortened cycles, and empowered full lifecycle management. As the source and cornerstone of digital factories, the efficiency and collaborative capabilities of 3D factory design directly impact subsequent links in the entire supply chain.

[0003] However, current mainstream 3D factory design software has significant technical bottlenecks in supporting the key requirement of remote collaborative design. Its implementation is seriously lagging behind the times and still relies on the technical paradigm of decades ago: the core process is to regularly package and transmit the design data to be collaborated to remote teams. This mechanism leads to a series of serious problems: (1) The collaborative process is blocked and inefficient: Before data packaging and synchronization, all users in the database must be forced to log out of the system, which rudely interrupts the designer's continuous workflow, relies heavily on manual coordination and collective "shutdown", which violates the flexibility and continuity requirements of modern digital work; (2) Poor synchronization reliability: The automatic synchronization mechanism provided by the software is not reliable enough, and there are often situations where some data is successfully synchronized while others fail. To solve such problems, the administrator needs to manually clean up the "dead processes" in the database and perform manual synchronization, which consumes a lot of manpower and time; (3) Unable to synchronize in real time, and information is seriously delayed: This mechanism determines that synchronization can only be set at a long fixed time interval (such as several hours or even once a day), resulting in a significant "data time difference" between remote design teams. Particularly serious is that (4) “data time lag” leads to disastrous consequences: designers in many locations cannot see each other’s latest modifications in real time, and the status of the models they see is seriously outdated. Designers are unaware of this or work based on outdated models, which can easily lead to frequent “collisions” between design models from different disciplines or regions in space (such as conflicts between pipes and structures, insufficient space for equipment, etc.). These conflicts that cannot be resolved in the design phase eventually flow to the construction site, forcing design changes, rework, or even demolition and reconstruction, resulting in delays, huge waste of resources, and a surge in additional costs, which seriously hinders the realization of the goal of “digital design guiding physical construction”.

[0004] Existing patent CN115564397A discloses an automated model management method suitable for 3D collaborative design platforms. Through automated model management, the submitted model files are compared with historical versions, and the professional designers receiving the submitted models can quickly display the differences in modifications and model updates between different versions. The platform synchronously uploads the submitted models to the server, and after the 3D models are lightweighted, they are attached to the MBS split model structure.

[0005] Existing patent CN119047013A discloses a three-dimensional collaborative model design method for hydropower engineering projects, which realizes three-dimensional design collaboration based on different three-dimensional design platforms and promotes the development of three-dimensional forward design for hydropower engineering projects.

[0006] In summary, while the two existing patents mentioned above offer optimizations in specific process automation, task management, model lightweighting, and post-process comparison, their technical architecture is still based on an outdated, non-real-time file / packet transmission synchronization model. Therefore, these existing patent solutions cannot effectively address the fundamental challenges of remote, real-time, reliable, and seamless collaborative design currently faced in the field of factory 3D design. Summary of the Invention

[0007] To address the aforementioned technical problems, this invention proposes a real-time remote collaborative method and system for a 3D factory design collaborative platform. This method enables real-time remote 3D design, ensuring designers can promptly view surrounding 3D models, reducing model collisions and conflicts, and truly achieving real-time remote 3D collaborative design. The specific technical solution is as follows:

[0008] A real-time remote collaboration method for a 3D factory design collaborative platform includes the following steps:

[0009] S1. Respond to the save operation of the local design user and write the model data into the local 3D design database;

[0010] S2. Monitor write requests to the 3D design database in real time and synchronously store model data to the platform database.

[0011] S3. Read model data from the platform database, divide it into data blocks, and parse it based on the combined parser;

[0012] S4. Compare the identifier with the incremental update record to filter out unsynchronized data blocks;

[0013] S5. Transmit incremental data blocks to a remote server via a dedicated link;

[0014] S6. The remote server writes incremental data to the remote 3D design database and updates the model view.

[0015] Furthermore, step S3 includes:

[0016] S31. Divide the model data into data blocks of a preset size and generate globally unique identifiers;

[0017] S32. Based on the parser combination paradigm, dynamically combine predefined basic parser units to parse the data block;

[0018] S33. By using multi-threaded concurrent scheduling to parse tasks, the parsed decimal data blocks and identifiers are stored in the platform database.

[0019] Furthermore, in step S32, the basic parser unit includes at least two of the following: an integer parser, a floating-point parser, and a string parser.

[0020] Furthermore, in step S32, when a data anomaly occurs during the parsing process, the process reverts to the most recent valid parsing state and generates an error log.

[0021] Furthermore, step S4 includes:

[0022] S41. Extract the incremental update record corresponding to the target remote node and the data block identifier set generated in step S3 from the platform database; S42. Compare the value of each identifier in the data block identifier set with the maximum identifier value in the incremental update record, and filter out the incremental data blocks that have not been synchronized to the target remote node; S43. Generate a lightweight set containing only the incremental data blocks, synchronously update the incremental state cache in memory, and asynchronously solidify the filtering results to the platform database.

[0023] Furthermore, in step S42, a data block is determined to be an incremental data block if and only if the current data block identifier is greater than the maximum identifier value in the incremental update record.

[0024] Furthermore, step S43 includes:

[0025] S431. Write the lightweight set of incremental data blocks into the memory incremental state cache for use by the real-time synchronization link; S432. Asynchronously trigger the platform database to persistently store the latest filtering results, which include the identifier and timestamp of the largest data block after the target remote node is updated.

[0026] Furthermore, step S5 includes:

[0027] S51. Classify, compress, and then encrypt incremental data blocks using quantum encryption. S52. Dynamically schedule dedicated link transmissions through software-defined networking and monitor link quality. S53. Implement hash verification and adaptive retransmission control. S54. Automatically switch to a backup transmission path when the main link delay exceeds the threshold.

[0028] Furthermore, in step S51, critical structural data blocks are compressed using the Zstandard algorithm, while non-critical data blocks are compressed using LZ4; a key is dynamically generated through the HSM hardware security module to perform post-quantum encryption based on the NTRU algorithm.

[0029] Furthermore, in step S52, when the dedicated link is dynamically scheduled through the software-defined network, if the delay of the main transmission link exceeds 50 milliseconds, it will automatically be diverted to the backup path, and multi-path connectivity will be maintained by relying on the closed-loop network topology constructed by the communication gateway deployed in a remote location.

[0030] Furthermore, in step S53, an SHA-3-512 hash check code is generated for each data packet. When the receiver fails to verify, a retransmission control based on the exponential backoff algorithm is triggered. After three consecutive verification failures, the abnormal link is automatically isolated.

[0031] Furthermore, step S6 includes:

[0032] S61. After decompression on the remote server, use a timing identifier to detect concurrent conflicts and execute an automatic merging or manual intervention conflict arbitration strategy; S62. Write the verified incremental data into the remote 3D design database and partially refresh the associated model view; S63. Update the incremental record metadata of the target node in the platform database and ensure the idempotency of the write operation through a global transaction identifier.

[0033] Furthermore, in step S62, only the model region associated with the changed data block is re-rendered.

[0034] This invention also provides a real-time remote collaboration system for a 3D factory design collaborative platform, used to implement the above-mentioned real-time remote collaboration method for a 3D factory design collaborative platform. The system includes server clusters distributed in different geographical areas. Each server cluster includes a 3D design server, a 3D design database, a platform server, a platform database, and a remote communication gateway. The 3D design server writes model data into the 3D design database. The platform server monitors changes to the database and accesses the platform database. The remote communication gateway interconnects target remote nodes through a cross-domain dedicated link.

[0035] Furthermore, the platform server integrates a monitoring module, an incremental processing module, and a transmission module; the platform server performs the following collaborative control: real-time capture of design changes and encapsulation of transaction messages, parsing and cutting model data blocks to generate unique identifiers and then performing differentiated compression and post-quantum encryption, filtering incremental data based on target remote node records, achieving real-time collaborative transmission through dynamic scheduling of multi-node closed-loop network paths, and arbitrating conflicts and refreshing the model view based on time sequence identifiers after receiving remote data.

[0036] Based on the above technical solution, compared with the prior art, the present invention has at least the following beneficial effects:

[0037] 1. This invention proposes a real-time remote collaboration method and system for a 3D factory design collaborative platform. Through millisecond-level parsing by the incremental processing module and low-latency transmission between remote interaction nodes, it breaks the synchronization interval limitations of traditional collaborative software. After a design user saves their work, the remote environment updates the model view within sub-seconds, enabling designers from multiple disciplines to view and edit the same model in real time, completely resolving collision problems caused by synchronization delays.

[0038] 2. This invention proposes a real-time remote collaboration method and system for a 3D factory design collaboration platform. Based on non-intrusive monitoring technology and a self-developed distributed platform, it does not rely on the paid collaboration modules of the original design software. The system directly reuses existing 3D design software databases, achieving collaboration capabilities through the platform layer, saving significant commercial collaboration module licensing fees, and avoiding the operational complexity caused by multi-system integration.

[0039] 3. This invention proposes a real-time remote collaboration method and system for a 3D factory design collaborative platform. Relying on incremental record metadata and a temporal conflict arbitration mechanism, it ensures that design modifications from multiple locations and disciplines are visible in real time. Mechanical, piping, and electrical designers can view the status of surrounding models at any time, avoiding spatial collisions during the design phase and reducing construction rework losses by more than 30%.

[0040] 4. This invention proposes a real-time remote collaboration method and system for a 3D factory design collaborative platform. The closed-loop transmission architecture features link-level disaster recovery. By integrating a 10Gbps optical module and a customized RUDP protocol, it ensures a cross-domain transmission packet loss rate of less than 0.001%. Combined with intelligent path optimization, it controls latency at the kilometer level to within 15 milliseconds. The underlying distributed database, based on the Raft consensus algorithm, guarantees strong data consistency across the three locations. Model write operations strictly adhere to a 10-millisecond latency limit, fundamentally eliminating version discrepancies. The system achieves dynamic scaling up and down in 30 seconds via API-driven mechanisms, enabling instantaneous response to sudden loads in large-scale factory design projects, forming a collaborative foundation that combines transmission reliability, data consistency, and resource elasticity. Attached Figure Description

[0041] The accompanying drawings, which form part of this specification, are used to provide a further understanding of the invention. The illustrative embodiments of the invention and their descriptions are used to explain the invention and do not constitute an undue limitation of the invention. In the drawings:

[0042] Figure 1 This is a flowchart illustrating a real-time remote collaboration method for a three-dimensional factory design collaboration platform proposed in this invention.

[0043] Figure 2 This is a schematic diagram of the structural framework of a real-time remote collaborative system for a three-dimensional factory design collaborative platform proposed in this invention. Detailed Implementation

[0044] It should be noted that, unless otherwise specified, the embodiments and features described in the present invention can be combined with each other. The present invention will now be described in detail with reference to the accompanying drawings and embodiments.

[0045] The present invention will be further described in detail below with reference to specific embodiments, which should not be construed as limiting the scope of protection claimed by the present invention.

[0046] To address the issues of model conflicts and construction rework arising from existing remote collaboration technologies, this invention provides a real-time remote collaboration method and system for a three-dimensional factory design collaboration platform.

[0047] The present invention will now be described with reference to specific embodiments.

[0048] Example 1

[0049] This embodiment provides a real-time remote collaboration method for a 3D factory design collaborative platform. (See attached document.) Figure 1 As shown, it includes the following steps:

[0050] S1. Respond to the save operation of the local design user and write the model data into the local 3D design database;

[0051] S2. Monitor the write requests of the database in real time and synchronously store the data in the platform database;

[0052] S3. The parser divides the binary model data into blocks and generates identifiers;

[0053] S4. Compare the identifier with the incremental update record to filter out unsynchronized data blocks;

[0054] S5. Transmit incremental data blocks to a remote server via a dedicated link;

[0055] S6. The remote server writes incremental data to the remote 3D design database and updates the model view.

[0056] Specifically, in step S1 above, when a local design user performs a save operation in their 3D design software, the model data is written to a dedicated 3D design database (DB) with read and write permissions for the user's location (e.g., location A). Each remote design point has its own independently operated 3D design database, ensuring that user operations are completed efficiently locally. Simultaneously, the local 3D design server typically adopts a distributed deployment architecture, which can flexibly expand server resources according to the number of users and load requirements, ensuring the response speed of local operations.

[0057] Specifically, in step S2 above, the platform server of the 3D factory design collaboration platform continuously monitors write events to the local 3D design database in real time. Once a new model data storage request or actual data write operation is detected, the platform immediately captures the event and its associated data, not only synchronizing and storing this model data to the local platform database but also triggering subsequent synchronization processes. The platform database receives, temporarily stores, and manages all model data to be synchronized, providing a data exchange foundation for remote collaboration.

[0058] Specifically, in step S3 above, the platform server efficiently processes the raw binary model data obtained from the 3D design database through the underlying parsing engine. To cope with the memory pressure of large industrial models, a block processing mechanism is adopted: firstly, the binary data is directly divided into data blocks of a preset size through zero-copy operations, and a globally unique identifier is generated for each block, completely avoiding memory copying overhead. This process deeply integrates the core capabilities of the Nom parser: based on the parser composition paradigm, predefined basic units (such as integers, floating-point numbers, and string processors) are dynamically combined into customized parsing logic adapted to the complex structure of industrial models, achieving accurate compatibility with multiple versions of heterogeneous data formats; at the same time, a robust error recovery mechanism is built-in, ensuring data integrity in the event of parsing exceptions through context rollback. The parsing engine further utilizes multi-threaded concurrent scheduling to fully utilize multi-core CPU resources to process the block data in parallel, significantly improving the parsing throughput of massive engineering data. Finally, the data blocks of the parsed decimal data and their identifiers are directly written into the platform database.

[0059] Specifically, in step S4 above, the platform server performs data synchronization filtering based on strictly maintained incremental update records. When a synchronization task to a specific target remote node (such as location B or location C) is triggered, the platform first extracts the incremental update record corresponding to the target remote node from the platform database (this record is persistently stored in the platform database, completely recording the latest data block identifier and synchronization timestamp of the last successful synchronization of each target remote node), and simultaneously obtains the full set of data block identifiers generated in step S3; by comparing the current data block identifier with the maximum identifier value in the target node's record item by item—using a strict greater than relationship judgment (i.e., it is determined to be an incremental block if and only if the current block identifier is greater than the record value), the platform accurately filters out all newly added or modified data blocks that have not been synchronized to that node. This dynamic comparison process fully considers the independence of multi-location collaboration in a distributed scenario: each target remote node has its own exclusive incremental record baseline, ensuring that modifications initiated by location A will not interfere with the synchronization filtering logic of location B. After filtering, the platform generates a lightweight set containing only incremental data blocks, providing a minimized dataset for subsequent transmissions and synchronously updating the incremental state cache in memory. This mechanism avoids full data transmission at its source, compressing network load to only the changed portions and reducing cross-regional synchronization latency to the hundreds of milliseconds level. Simultaneously, the platform database asynchronously persists the latest filtering results, establishing a consistent baseline for the next round of incremental synchronization.

[0060] Specifically, in step S5 above, the platform server preprocesses the selected incremental data blocks: During the incremental processing phase, the data block type and priority are first marked using a classification engine; critical structural data is compressed using the highest Zstandard compression level, while non-critical data is compressed using LZ4. Subsequently, the data blocks are encrypted using the NTRU algorithm combined with an HSM dynamic key. The preprocessed data packets are bound to a global transaction ID and transmitted via a dedicated link scheduled by the SDN controller—when the delay on the main link (A→B) exceeds 50ms, traffic is automatically diverted to the backup path (A→C→B). End-to-end verification is implemented during transmission, with each data packet carrying a SHA-3-512 hash value. If the receiver fails to verify, exponential backoff retransmission is triggered. Simultaneously, the platform monitors the transmission status of each block in real time; if a block is not confirmed within a timeout period, automatic routing switching and alarm notifications are triggered.

[0061] Specifically, in step S6 above, after the target remote platform server (e.g., location B or C) receives the transmitted incremental data block, it first performs decryption and decompression operations to restore the data to the original data block and its globally unique identifier. Then, a conflict arbitration process is initiated locally: based on the time sequence identifier, the local and remote versions are compared. When concurrent modification conflicts are detected, preset rules are automatically applied to merge the data; if an engineering conflict cannot be automatically resolved, synchronization is paused and relevant designers are notified for manual intervention. Verified data blocks are submitted to the local 3D design server, which accurately writes the incremental data to a dedicated industrial-grade database instance. After the database update is complete, the platform triggers a model view refresh mechanism: only the local model area associated with the changed data block is re-rendered, ensuring that remote users can observe the updated content through the view interface within 200 milliseconds without reloading the complete model. Simultaneously, the platform database updates the incremental record metadata, recording the identifier of the currently synchronized data block, establishing a consistency baseline for subsequent incremental synchronization. The entire process achieves idempotency of write operations through identifier binding, effectively filtering duplicate writes caused by retransmissions and ensuring the accuracy and reliability of data synchronization.

[0062] Example 2

[0063] See Figure 2 As shown, this embodiment provides a real-time remote collaborative system for a 3D factory design collaborative platform. The system includes server clusters distributed across different geographical regions. Each cluster includes a 3D design server, a 3D design database, a platform server, a platform database, and a remote communication gateway. The output of the 3D design server is connected to the input of the 3D design database, the output of the 3D design database is connected to the input of the platform server, and the output of the platform server is connected to the remote communication gateway. A bidirectional data channel is established between the platform server and the platform database to achieve mutual connection. The remote communication gateway is directly interconnected with gateways in other regions via a dedicated cross-domain link. For example, when deployed in locations A, B, and C, a triangular closed-loop network topology is formed: A↔B, B↔C, C↔A. The platform server integrates three core components: a monitoring module, an incremental processing module, and a transmission module.

[0064] Among them, the 3D design server serves as the underlying support for the design software, directly receiving and storing the original model data generated by the user through the 3D design software.

[0065] The 3D design database adopts an industrial-grade parametric storage architecture, specifically designed to hold the original model data generated by 3D design software, including core data entities such as geometric topology, engineering attribute parameters, and assembly constraints. It supports high-concurrency write operations of more than 500 per second through a distributed dual-active storage engine, ensuring that the local response time of design operations is strictly controlled within 0.5 seconds. Each geographical region deploys a dedicated independent database instance, physically isolating write channels in different regions to avoid cross-domain read / write conflicts at the source.

[0066] The platform server acts as the central nervous system of the cluster, providing three major coordination services: resource scheduling, status monitoring, and conflict arbitration. It monitors the health of the 3D design server, ensuring a local response time of less than or equal to 0.5 seconds; implements dynamic resource scheduling for the listening and incremental processing modules; after receiving data from the target remote node, the local platform server performs conflict arbitration, adjudicating concurrent modifications based on time sequence identifiers; and optimizes routing strategies for remote communication gateways and monitors transmission quality. Specifically, the listening module collects the binary change pipeline generated by the 3D design database in real time through a non-intrusive log parsing interface. This pipeline includes a structured storage of the operation pipeline (recording the modeling operation sequence) and version snapshots (saving feature-level historical states). When an incremental change event is detected, the module extracts the parameterized change body from the operation pipeline within 20 milliseconds, encapsulates it into a transaction message packet with a version signature, and pushes it to the platform database. The incremental processing module performs the core incremental calculation task, first calling the Nom zero-copy parser to cut the binary model into data blocks, and then generating a globally unique identifier containing a timestamp and geohash for each block. By querying the incremental records of target nodes stored in the platform database, this module can filter out unsynchronized blocks with 99.99% accuracy, trigger differentiated compression strategies according to data block type, and finally compress the incremental blocks into Zstandard or LZ4 format and encrypt them. The transmission module is responsible for cross-domain data scheduling, generating global transaction IDs and end-to-end checksums, implementing packet-level transmission status monitoring; dynamically calling compression and encryption algorithms, triggering differentiated processing strategies according to data priority; submitting path calculation requests to the SDN controller, and executing intelligent routing scheduling instructions.

[0067] The platform database stores two types of key data: raw binary model data and incremental record metadata. The raw binary model data fully preserves the unparsed industrial model snapshot received from the monitoring module, while the incremental record metadata records the latest synchronized block identifier and timestamp. This module achieves strong consistency of data across the three locations using the Raft consensus algorithm and strictly controls write latency to within 10 milliseconds.

[0068] As the hardware hub of the transmission system, the remote communication gateway deploys hot-swappable 10Gbps optical modules at the physical layer, supporting bidirectional data transmission over a single fiber. At the protocol layer, packet loss compensation is achieved through forward error correction and sliding window mechanisms, ensuring an effective packet loss rate of less than 0.001%. The routing layer integrates a software-defined network controller, which switches the optimal path in real time based on link quality, ensuring that cross-domain transmission latency remains stable at 15 milliseconds per thousand kilometers.

[0069] The above description is merely a preferred embodiment of the present invention and is not intended to limit the invention. Various modifications and variations can be made to the present invention by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the scope of protection of the present invention.

[0070] It should be noted that, in this document, relational terms such as "first" and "second" are used merely to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes the element.

[0071] The logic and / or steps represented in the flowchart or otherwise described herein, for example, can be considered as a sequenced list of executable instructions for implementing logical functions, and can be embodied in any computer-readable medium for use by, or in conjunction with, an instruction execution system, apparatus or device (such as a computer-based system, a processor-included system or other system that can fetch and execute instructions from, an instruction execution system, apparatus or device).

[0072] It should be understood that various parts of the present invention can be implemented in hardware, software, firmware, or a combination thereof. In the above embodiments, multiple steps or methods can be implemented in software or firmware stored in memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, it can be implemented using any one or a combination of the following techniques known in the art: discrete logic circuits having logic gates for implementing logical functions on data signals, application-specific integrated circuits (ASICs) having suitable combinational logic gates, programmable gate arrays (PGAs), field-programmable gate arrays (FPGAs), etc.

[0073] Furthermore, those skilled in the art can combine and integrate the different embodiments or examples described herein, as well as the features of the different embodiments or examples, without contradiction.

Claims

1. A real-time remote collaboration method of a three-dimensional factory design collaboration platform, characterized in that, The method comprises the following steps: S1, in response to the save operation of the local design user, write the model data into the local three-dimensional design database; S2, real-time monitor the write request of the three-dimensional design database, and synchronize the model data to the platform database; S3, read the model data from the platform database, segment it into data blocks, and parse it based on the combined parser; S4, compare the identifier with the incremental update record, and filter the unsynchronized data block; S5, transmit the incremental data block to the remote server through a special link; S6, the remote server writes the incremental data into the remote three-dimensional design database and updates the model view. 2.The real-time remote collaboration method of the three-dimensional factory design collaboration platform according to claim 1, characterized in that, Step S3 comprises: S31, segment the model data into data blocks of a preset size and generate a globally unique identifier; S32, dynamically combine the pre-defined basic parser unit based on the parser combination paradigm, and parse the data block; S33, through multi-thread concurrent scheduling of parsing tasks, store the parsed decimal data block and identifier into the platform database. 3.The real-time remote collaboration method of the three-dimensional factory design collaboration platform according to claim 2, characterized in that: In step S32, the basic parser unit includes at least two of an integer parser, a floating point number parser and a string parser.

4. The three-dimensional factory design collaborative platform real-time off-site collaboration method according to claim 2, characterized in that: In step S32, when a data exception occurs during the parsing process, fall back to the latest valid parsing state and generate an error log.

5. The real-time off-site collaboration method of the three-dimensional factory design collaboration platform according to claim 2, characterized in that, Step S4 comprises: S41, extract the incremental update record corresponding to the target remote node from the platform database and the data block identifier set generated in step S3; S42, compare the value of each identifier in the data block identifier set with the maximum identifier value in the incremental update record, and filter out the incremental data block that has not been synchronized to the target remote node; S43, generate a lightweight set containing only the incremental data block, and synchronize the incremental state cache in the memory and asynchronously solidify the screening result to the platform database.

6. The three-dimensional factory design collaborative platform real-time off-site collaboration method according to claim 5, characterized in that: In step S42, the incremental data block is determined only when the current data block identifier is greater than the maximum identifier value in the incremental update record.

7. The three-dimensional factory design collaborative platform real-time off-site collaboration method according to claim 5, characterized in that, Step S43 comprises: S431, write the lightweight set of incremental data blocks to the memory incremental state cache for real-time synchronization link calling; S432, asynchronously trigger the platform database to persistently store the latest screening result, which contains the maximum data block identifier and timestamp of the target remote node after updating.

8. The three-dimensional factory design collaborative platform real-time off-site collaboration method according to claim 5, characterized in that, Step S5 comprises: S51, classify, compress and post-quantum encrypt the incremental data block; S52, dynamically schedule the special link transmission through software-defined network, and monitor the link quality; S53, implement hash check and adaptive retransmission control; S54, when the main link delay exceeds the threshold, automatically switch to the backup transmission path. 9.The real-time remote collaboration method of the three-dimensional factory design collaboration platform according to claim 8, characterized in that: In step S51, the key structure data block is compressed by Zstandard algorithm, and the non-key data block is compressed by LZ4; the key is dynamically generated by HSM hardware security module, and post-quantum encryption based on NTRU algorithm is performed.

10. The three-dimensional factory design collaborative platform real-time off-site collaboration method of claim 8, wherein: In step S52, when the main transmission link delay exceeds 50 milliseconds, the software-defined network dynamically schedules the special link, and automatically shunts to the backup path, and relies on the closed-loop network topology maintained by the communication gateway deployed in the remote place to maintain multi-path connectivity.

11. The three-dimensional factory design collaborative platform real-time off-site collaboration method according to claim 8, characterized in that: In step S53, an SHA-3-512 hash check code is generated for each data packet, and the receiving party triggers retransmission control based on an exponential backoff algorithm when the check fails, and automatically isolates the abnormal link after three consecutive check failures.

12. The three-dimensional factory design collaborative platform real-time offsite collaboration method according to claim 8, characterized in that, Step S6 includes: S61, the off-site server detects and resolves conflicts using timing identifiers after decryption and decompression, and executes automatic merging or manual intervention conflict arbitration strategies; S62, write the incremental data that passes the check to the off-site three-dimensional design database, and locally refresh the associated model view; S63, update the incremental record metadata of the target node in the platform database, and ensure the idempotency of the write operation through a global transaction identifier.

13. The three-dimensional factory design collaborative platform real-time off-site collaboration method according to claim 12, characterized in that, In step S62, only the model area associated with the changed data block is re-rendered.

14. A three-dimensional factory design collaborative platform real-time remote collaboration system for implementing the three-dimensional factory design collaborative platform real-time remote collaboration method according to any one of claims 1-13, characterized in that: The system includes server clusters distributed in different geographic regions, and each server cluster includes a three-dimensional design server, a three-dimensional design database, a platform server, a platform database, and an off-site communication gateway; The three-dimensional design server writes model data into the three-dimensional design database; The platform server listens to the database changes and accesses the platform database; the off-site communication gateway interconnects the target off-site node through a cross-domain dedicated link.

15. The three-dimensional factory design collaboration platform real-time offsite collaboration system of claim 14, wherein: The platform server integrates a listening module, an incremental processing module, and a transmission module; The platform server performs the following collaborative control: real-time capture of design changes and packaging of transaction messages, differential compression and post-quantum encryption after generating unique identifiers by analyzing and cutting model data blocks, filtering incremental data based on target off-site node records, realizing real-time collaborative transmission through dynamic scheduling of multi-node closed-loop network paths, arbitrating conflicts based on timing identifiers after receiving off-site data, and refreshing the model view.

Images