Three-dimensional design method and system based on centralized and distributed hybrid architecture

Abstract

The invention relates to a three-dimensional design method and system based on a centralized and distributed hybrid architecture, and the method comprises the steps: constructing an integrated three-dimensional design system, and carrying out the integrated design of the three-dimensional design system in a data layer, an application layer and a display layer; data management, version control and authority management functions in the three-dimensional design system are controlled in a centralized management mode, and design task execution and professional internal cooperation functions in the three-dimensional design system are coordinated in a distributed execution mode. Modularized design is carried out on each function in the three-dimensional design system, different modules are communicated by adopting a standardized interface protocol, and dynamic loading and configuration of the modules are carried out based on a plug-in architecture. Compared with the prior art, multiple professional resources are integrated, information barriers are broken, dynamic data sharing is achieved, and the method has the advantages of being high in response speed, flexibility and expandability and the like.

Description

Technical Field

[0001] This invention relates to the field of 3D design technology, and in particular to a 3D design method and system based on a hybrid centralized and distributed architecture. Background Technology

[0002] With the continuous expansion of engineering project scale and the constant improvement of technical requirements, modern engineering design is facing unprecedented challenges of complexity. Taking the power industry as an example, projects such as ultra-high voltage substations, smart grids, and large industrial plants involve multiple professional fields such as civil engineering, structure, electrical engineering, HVAC, and water supply and drainage. There are a large number of interface relationships and data dependencies between these disciplines. In the traditional design model, the drawings are superimposed after each discipline works independently, which often leads to problems such as pipeline collisions, equipment layout conflicts, and deviations in reserved holes. If these problems are only discovered during the construction phase, they will cause significant rework costs and project delays.

[0003] Traditional design models suffer from significant information silos. Different disciplines use different design software and data formats, and design deliverables are provided as two-dimensional drawings or independent three-dimensional models, lacking a unified data exchange standard. Information transfer between disciplines mainly relies on paper or PDF drawings, and data cannot be dynamically synchronized, resulting in lagging design information and prominent problems of redundant modeling.

[0004] Therefore, there is an urgent need for a three-dimensional collaborative design solution that integrates resources from multiple disciplines, breaks down information barriers, achieves dynamic data sharing, and constructs a closed-loop management system covering the entire lifecycle from design to construction to operation and maintenance. Summary of the Invention

[0005] The purpose of this invention is to overcome the shortcomings of the existing technology and provide a three-dimensional design method and system based on a centralized and distributed hybrid architecture that integrates multi-disciplinary resources, breaks down information barriers, and achieves dynamic data sharing.

[0006] The objective of this invention can be achieved through the following technical solutions: A 3D design method based on a centralized and distributed hybrid architecture includes the following steps: An integrated 3D design system is constructed, which integrates design at the data layer, application layer, and presentation layer. The data layer integrates design data from different disciplines and software into a central database as a single data source. The application layer enables interconnection and interoperability between different design software and business systems through standardized API interfaces and service bus architecture. The presentation layer constructs a unified human-computer interaction interface for centralized access and collaborative operation of multiple system functions. A centralized management approach is used to control the data management, version control, and access control functions of the 3D design system, while a distributed execution approach is used to coordinate the execution of design tasks and internal professional collaboration functions within the 3D design system. The various functions in the 3D design system are modularized, and different modules communicate with each other using standardized interface protocols. The modules are dynamically loaded and configured based on a plug-in architecture.

[0007] Furthermore, the method also includes: for heterogeneous data received by the data layer, converting the heterogeneous data into an intermediate data format for data exchange, and using a semantic mapping mechanism to perform semantic interoperability of data in different formats.

[0008] Furthermore, during the access to the heterogeneous data, enterprise service bus or message queues are used through message middleware, and data virtualization technology is used to access the heterogeneous data.

[0009] Furthermore, the method also includes setting up a multi-level access control model in the 3D design system for access control. The multi-level access control model adopts a hybrid model that combines role-based access control and attribute-based access control. The role-based access control assigns corresponding permissions to each role, while the attribute-based access control performs dynamic authorization based on project and time information.

[0010] Furthermore, the method also includes adopting a microservice architecture, deploying each functional module of the 3D design system as an independent service, and using a master-slave mode or cluster deployment to build a fault tolerance mechanism so as to automatically switch to the standby node when the master node fails.

[0011] Furthermore, the implementation process of the aforementioned professional internal collaboration function specifically includes: An information sharing mechanism is adopted to facilitate data interaction among various professional teams. This information sharing mechanism includes: setting up an interface registration center to uniformly register the data submission interfaces and service interfaces defined by each professional team to the interface center, forming an interface directory list, and providing interface descriptions. Configure the interface orchestration engine to orchestrate the interface call flow in a visual way, and monitor and track the interface call status.

[0012] Furthermore, the implementation process of the aforementioned professional internal collaboration function also includes: An incremental synchronization mechanism is constructed to synchronize data from various professional teams. This incremental synchronization mechanism adopts change data capture technology, only synchronizing data that has changed, and sets a synchronization priority strategy according to the importance and timeliness requirements of the data.

[0013] Furthermore, the method also includes treating each design team accessing the 3D design system as an intelligent agent and using a particle swarm optimization algorithm to achieve multi-team collaborative optimization; the particle swarm optimization algorithm models the collaborative design problem as a multi-objective optimization problem, with objective functions including design quality, cost, and schedule, and constraints including specification requirements and resource limitations; In the optimization process of the particle swarm optimization algorithm, the design schemes of each design team are regarded as particles. The position of the particle represents the scheme parameters, and the velocity of the particle represents the scheme adjustment direction. Through iterative search, the schemes of each team gradually move closer to the global optimal solution, and the current optimal solution is shared among the design teams.

[0014] Furthermore, the method also includes dynamically allocating computing tasks and storage resources to the project requirements of the 3D design system based on task characteristics, resource status, and historical performance.

[0015] The present invention also provides a three-dimensional design system based on a centralized and distributed hybrid architecture, including a memory and a processor, wherein the memory stores a computer program, and the processor calls the computer program to execute the steps of the method described above.

[0016] Compared with the prior art, the present invention has the following advantages: (1) This invention proposes a hybrid architecture design combining centralized and distributed approaches, innovatively integrating centralized management with distributed execution. Core functions such as data storage, version control, and access control adopt a centralized architecture to ensure data consistency and management standardization; the execution of specific design tasks and internal professional collaboration adopt a distributed model, giving each professional team a certain degree of autonomy and improving response speed and flexibility. This hybrid architecture overcomes the rigidity of purely centralized architecture and the lack of control of purely distributed architecture, achieving a balance between control and flexibility.

[0017] (2) This invention proposes a modular plug-in extension mechanism, which supports flexible plug-in and expansion of functional modules through the design of standardized module interface specifications. New professional modules and tool plug-ins can be quickly integrated into the platform according to the specifications without modifying the core system. This plug-in architecture significantly reduces the cost of system customization and upgrades, and improves the platform's adaptability and life cycle.

[0018] (3) This invention proposes a multi-layered security protection system that covers the physical layer, network layer, data layer, application layer, and management layer for comprehensive security protection. It employs multiple security mechanisms, including hardware encryption, transmission encryption, access control, and audit logs, to ensure data security. This defense-in-depth strategy significantly improves system security and meets the stringent data security requirements of the power industry.

[0019] (4) This invention proposes an intelligent collaborative decision-making algorithm that applies intelligent algorithms such as particle swarm optimization and reinforcement learning to multi-team collaborative decision-making, thereby achieving intelligent recommendation and dynamic optimization of collaborative strategies. By learning from historical collaborative cases, the system can automatically identify collaborative patterns, predict conflicts, and suggest negotiation strategies, thus improving the level of intelligence in collaboration. Attached Figure Description

[0020] Figure 1 This is a flowchart illustrating a three-dimensional design method based on a hybrid centralized and distributed architecture, as provided in an embodiment of the present invention. Detailed Implementation

[0021] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. The components of the embodiments of the present invention described and shown in the accompanying drawings can generally be arranged and designed in various different configurations.

[0022] Therefore, the following detailed description of the embodiments of the invention provided in the accompanying drawings is not intended to limit the scope of the claimed invention, but merely to illustrate selected embodiments of the invention. All other embodiments obtained by those skilled in the art based on the embodiments of the invention without inventive effort are within the scope of protection of the invention.

[0023] It should be noted that similar labels and letters in the following figures indicate similar items. Therefore, once an item is defined in one figure, it does not need to be further defined and explained in subsequent figures.

[0024] Example 1 like Figure 1 As shown, this embodiment provides a 3D design method based on a centralized and distributed hybrid architecture, including the following steps: S1: Construct an integrated 3D design system. This system integrates design data at the data layer, application layer, and presentation layer. The data layer integrates design data from different disciplines and software into a central database as a single data source. The application layer enables interconnection and interoperability between different design software and business systems through standardized API interfaces and a service bus architecture. The presentation layer constructs a unified human-computer interaction interface for centralized access and collaborative operation of multiple system functions. S2: A centralized management approach is used to control the data management, version control, and access control functions of the 3D design system, while a distributed execution approach is used to coordinate the execution of design tasks and internal professional collaboration functions within the 3D design system. S3: Modular design of each function in the 3D design system, communication between different modules using standardized interface protocols, and dynamic loading and configuration of modules based on a plug-in architecture.

[0025] The following is a detailed description of each part. 1. Integrated 3D Design System In step S1, this solution proposes to combine dispersed functional modules into a collaborative, complete system through standardized interfaces and a unified data management strategy. In a 3D design scenario, the application of system integration theory is reflected in three dimensions: the data layer, the application layer, and the presentation layer.

[0026] In terms of data layer integration, a unified data storage and management architecture is established to integrate design data from different disciplines and software into a central database, realizing the concept of a single data source. Data layer integration needs to solve key issues such as data format conversion, semantic mapping, and version management to ensure data consistency, integrity, and traceability. Application layer integration achieves interconnectivity between different design software and business systems through standardized API interfaces and service bus architecture, focusing on the continuity of business processes, supporting cross-system task flow and data exchange, and avoiding information silos. Presentation layer integration constructs a unified human-computer interaction interface to provide users with a consistent operating experience. This requires shielding the heterogeneity of the underlying systems and achieving centralized access and collaborative operation of multiple system functions through portal technology or an integration workbench. The application of system integration theory in 3D design is essentially about building a system within a system, improving overall efficiency and generating synergistic effects through organic integration.

[0027] 2. Hybrid architecture of centralized and distributed systems In step S2, the centralized-distributed hybrid architecture combines centralized management with distributed execution. Centralized control is used for core functions such as data management, version control, and access control to ensure data security and standardized management. However, teams are given a degree of autonomy in specific task execution and internal collaboration, supporting flexible and efficient collaborative work. This hybrid model ensures both overall control capabilities and system flexibility and scalability.

[0028] 3. Modular design Modular design in step S3 is a crucial method for reducing system complexity and improving maintainability. Its core idea is to decompose a complex system into relatively independent modules with clearly defined interfaces, each capable of independent development, testing, deployment, and upgrades. In the integration of 3D design modules, modular design adheres to the principles of high cohesion and low coupling. Modules have closely related internal functions, minimize inter-module dependencies, and interact through clear interfaces. Substitutability requires defining standard interface specifications to support the interchangeability of similar modules, avoiding dependence on specific software or vendors. Scalability is achieved by reserving extension interfaces, supporting flexible access and functional enhancement of new modules to adapt to changing business needs. Reusability abstracts common functions into basic modules for repeated use in different projects and scenarios, improving development efficiency. Modular implementation mechanisms include interface standardization, defining communication protocols and data exchange formats between modules, such as RESTful APIs, message queues, and data buses. Service-oriented encapsulation encapsulates each design function as an independent service, enabling dynamic invocation through service registration and discovery mechanisms. Configuration-based management allows for flexible combination and adjustment of modules through configuration files or a management console, adapting to different application scenarios without code modification.

[0029] 3.1 Standardized Interface Protocol Design Interface protocols are crucial for enabling interoperability between modules. Designing standardized interface protocols requires comprehensive consideration of factors such as communication protocols, data formats, version management, and security authentication. Regarding communication protocol selection, an appropriate protocol should be chosen based on the application scenario. For synchronous call scenarios, the HTTP / HTTPS protocol is adopted, and the API is designed based on the RESTful style. For asynchronous message passing, message queues such as MQTT and AMQP are used to achieve decoupled communication; for real-time data streams, WebSocket or gRPC protocols are used.

[0030] Regarding data exchange formats, JSON or XML is uniformly adopted as the data exchange format, and standardized data models and field definitions are established. For 3D geometric data, international standard formats such as IFC and CityGML are used to ensure cross-platform compatibility. A version control mechanism is established for interface version management, using version numbers to identify interface changes, supporting backward compatibility, and ensuring a smooth transition for system upgrades. A token-based authentication and access control mechanism is implemented to ensure the security of interface calls, using mature authentication frameworks such as OAuth 2.0 and JWT.

[0031] 3.2 Heterogeneous data format compatibility For heterogeneous data received by the data layer, the heterogeneous data is converted into an intermediate data format for data exchange, and a semantic mapping mechanism is used to perform semantic interoperability between different data formats.

[0032] Specifically, 3D design involves multiple professional software programs, each using different native data formats. Achieving compatibility with these heterogeneous data formats is the core challenge of integration. Data format conversion requires the development or integration of data conversion tools to achieve bidirectional conversion between common formats. The conversion process must ensure geometric accuracy, attribute integrity, and the accuracy of topological relationships. An intermediate format strategy uses intermediate formats such as IFC as a bridge for data exchange. Each professional software program only needs to convert to the intermediate format, avoiding the complexity of many-to-many conversions. A semantic mapping mechanism establishes a unified data dictionary and ontology model, defining common concepts and terminology across different professions to achieve semantic interoperability between different systems. Data quality checks are performed after format conversion to verify data integrity and correctness, including geometric integrity checks, attribute missing detection, and topological relationship verification, ensuring conversion quality.

[0033] Middleware acts as the glue connecting different systems and modules, playing a crucial role in integration solutions. Message middleware uses Enterprise Service Bus or message queues to achieve asynchronous communication and message routing between systems, supporting various communication modes such as publish-subscribe and point-to-point, and providing enhanced features such as message persistence and transaction guarantees. Data middleware, through data virtualization technology, enables unified access to heterogeneous data sources without migrating data, providing a unified query interface and shielding the differences in underlying data storage. Application middleware provides basic services such as distributed transaction management, load balancing, and failover, enhancing system reliability and performance.

[0034] 3.3 Dynamic Module Loading and Configuration To adapt to changing project needs and business scenarios, the system needs to support dynamic loading and configuration of modules. A plug-in architecture employs a plug-in mechanism, encapsulating optional functions as independent plug-ins. Users select and load these plug-ins as needed. Plug-ins adhere to a unified interface specification, allowing for functional expansion without modifying the core system. A centralized configuration management platform is established in the configuration management center. Through a visual interface, it manages module enabling / disabling, parameter configuration, and permission allocation. Configuration changes take effect in real time without requiring a system restart. Hot deployment capabilities support hot-swapping of modules and online upgrades, updating functional modules without service interruption and improving system availability.

[0035] 4. Data Management and Security Mechanisms 4.1 Single Data Source Construction A single data source is the core foundation of collaborative design, ensuring that all participants work on the same data and avoiding errors and rework caused by data inconsistency. Data consistency assurance mechanisms require measures from multiple dimensions. A unified database architecture establishes a central database as the authoritative data source, storing all design data in a unified database. Relational databases are used to manage structured data, while document databases or object storage are used to manage unstructured data such as 3D model files. Regarding data synchronization strategies, for distributed deployment scenarios, master-slave replication or multi-master replication architectures are used to ensure data synchronization across different nodes. A conflict resolution mechanism is designed, employing a last-write-wins-or-wins strategy to handle concurrent update conflicts. For operations involving multiple data objects, transaction mechanisms are used to ensure atomicity—either all succeed or all rollback—avoiding data being in an inconsistent intermediate state.

[0036] Real-time synchronization technology requires that data changes be immediately propagated to all relevant parties. Change detection mechanisms employ technologies such as database triggers and file system monitoring to capture data change events in real time. Push notification technology utilizes WebSocket long connections or server push technology to proactively push change messages to online users, achieving synchronization within seconds. Incremental synchronization strategies transmit only the changed data content, rather than the entire dataset, reducing network bandwidth consumption and synchronization latency.

[0037] Conflict detection and resolution algorithms address the inevitable conflicts encountered during concurrent editing by multiple users. An optimistic locking mechanism uses version numbers or timestamps to identify data versions, checking for version changes upon submission; if a change is found, a conflict is flagged. File-level locking is used for cohesive files such as 3D models, allowing only one user to edit at a time, while other users have read-only access. Object-level locking is used for decomposable models, employing finer-grained object-level locking, allowing different users to edit different parts of the model simultaneously. A three-way merging algorithm is used for text-based configuration files, merging based on a common ancestor version to automatically resolve most conflicts; conflicts that cannot be automatically resolved are handled manually by the user.

[0038] 4.2 Safety Protection Data security is the lifeline of a system, requiring a multi-layered, comprehensive security protection system. In hardware and software encryption schemes, hardware encryption for sensitive data storage utilizes storage devices that support hardware encryption, implementing data encryption at the hardware level to improve security and performance. Software encryption implements data encryption at the application layer, employing strong encryption algorithms such as AES-256 to encrypt and protect stored and transmitted data. Key management utilizes a key management service, rotating keys periodically. Transmission encryption uses TLS / SSL encryption for all network communications to prevent data from being eavesdropped on or tampered with during transmission.

[0039] Preferably, the method further includes setting a multi-level access control model in the 3D design system for access control. The multi-level access control model adopts a hybrid model combining role-based access control and attribute-based access control. The role-based access control assigns corresponding permissions to each role, and the attribute-based access control performs dynamic authorization based on project and time information.

[0040] Specifically, roles are defined based on job responsibilities, such as project manager, professional lead, designer, and reviewer, with corresponding permissions assigned to each role. Permission granularity is refined to specific operations such as read, edit, delete, and approve, and data objects such as projects, models, and files. Dynamic authorization supports dynamic authorization based on attributes such as project and time; for example, only personnel involved in a project can access the data for that project, and permissions for departing employees are automatically invalidated.

[0041] Preferably, the method further includes adopting a microservice architecture, deploying each functional module of the 3D design system as an independent service, and using a master-slave mode or cluster deployment to build a fault tolerance mechanism so as to automatically switch to a standby node when the master node fails.

[0042] This achieves fault isolation and redundancy design, including module isolation and a microservice architecture, deploying different functional modules as independent services so that the failure of one module does not affect the operation of other modules. In the fault tolerance mechanism, critical services adopt a master-slave mode or cluster deployment, automatically switching to a standby node when the master node fails to ensure service continuity. Data backup is performed regularly with full and incremental backups, and backup data is stored off-site to prevent data loss due to catastrophic failures.

[0043] 5. Multi-team collaboration mechanism Preferably, the implementation process of the professional internal collaboration function specifically includes: An information sharing mechanism is adopted to facilitate data interaction among various professional teams. This information sharing mechanism includes: setting up an interface registration center to uniformly register the data submission interfaces and service interfaces defined by each professional team to the interface center, forming an interface directory list, and providing interface descriptions. Configure the interface orchestration engine to orchestrate the interface call flow in a visual way, and monitor and track the interface call status.

[0044] The implementation process of the aforementioned professional internal collaboration function also includes: An incremental synchronization mechanism is constructed to synchronize data from various professional teams. This incremental synchronization mechanism adopts change data capture technology, only synchronizing data that has changed, and sets a synchronization priority strategy according to the importance and timeliness requirements of the data.

[0045] The specific description is as follows: Information sharing is the lifeblood of collaborative design, determining the efficiency and quality of teamwork. A unified interface management platform architecture serves as the central hub for data interaction among various professional teams. The interface registry center registers all data provision interfaces and service interfaces defined by each profession, creating an interface directory list. Interface descriptions include interface name, functional description, input / output parameters, and call frequency limits. The interface orchestration engine orchestrates interface call flows visually, automating cross-professional business processes. For example, after the architectural team completes the floor plan, it automatically triggers the load provision process for the structural team and the point verification process for the MEP (Mechanical, Electrical, and Plumbing) team. Interface monitoring and tracking provide real-time monitoring of interface calls, recording call logs and promptly alerting when calls fail or time out, supporting rapid problem location and resolution.

[0046] The real-time data synchronization protocol is designed to ensure data consistency across multiple teams. The incremental synchronization mechanism employs change data capture technology, synchronizing only changed data, not the entire dataset, significantly reducing network bandwidth consumption and synchronization latency. The synchronization priority strategy sets priorities based on data importance and timeliness requirements; critical data, such as security-related parameters, are synchronized in real-time, while general data can be synchronized in batches at scheduled times. The conflict resolution strategy clearly defines data ownership and modification permissions. In principle, the data provider is responsible for modifying the data, while other parties have read-only access. When cross-disciplinary modifications are necessary, conflicts are resolved through negotiation mechanisms or approval processes.

[0047] A standardized documentation system covers the entire process. Interface protocol documents clearly define the data submission methods, submission timelines, and data depth requirements for each discipline, forming interface protocol documents and incorporating them into contract management. Design standard documents compile industry specifications, enterprise standards, and project-specific requirements, forming a unified design standard library for all disciplines to follow. Collaboration manuals are compiled, detailing collaboration processes, tool usage methods, and solutions to common problems, providing operational guidance for team members.

[0048] Version control and change management mechanisms are strictly implemented. A unified naming convention is established for versions, such as professional code-stage code-version number, for easy identification and traceability. For example, A-SD-V1.0 represents the first version of the architectural construction drawings. The change process is standardized, requiring design changes to be submitted with a change request explaining the reason for the change, its scope of impact, and implementation plan. Implementation is only permitted after review by relevant parties, and major changes require approval from the project manager or technical lead. A change notification mechanism automatically notifies affected professionals and personnel after a design change occurs, ensuring timely information delivery. Change notifications include a summary of the changes, a detailed change list, and an impact analysis.

[0049] 6. Application of intelligent optimization algorithms Preferably, the method further includes treating each design team accessing the 3D design system as an intelligent agent and using a particle swarm optimization algorithm to achieve multi-team collaborative optimization; the particle swarm optimization algorithm models the collaborative design problem as a multi-objective optimization problem, with objective functions including design quality, cost, and schedule, and constraints including specification requirements and resource limitations; In the optimization process of the particle swarm optimization algorithm, the design schemes of each design team are regarded as particles. The position of the particle represents the scheme parameters, and the velocity of the particle represents the scheme adjustment direction. Through iterative search, the schemes of each team gradually move closer to the global optimal solution, and the current optimal solution is shared among the design teams.

[0050] Preferably, the method further includes dynamically allocating computing tasks and storage resources to the project requirements of the 3D design system based on task characteristics, resource status, and historical performance.

[0051] This provides a dynamic load balancing optimization algorithm that intelligently allocates computing tasks and storage resources based on factors such as task characteristics, resource status, and historical performance. The algorithm can dynamically adjust its strategy to adapt to changes in different project stages and load characteristics, maximizing resource utilization.

[0052] The specific description is as follows: Introducing intelligent algorithms enhances the scientific rigor and efficiency of collaborative decision-making. The application of particle swarm optimization (PSO) in multi-agent collaboration treats each design team as an agent, utilizing PSO to achieve collaborative optimization across teams. Problem modeling transforms the collaborative design problem into a multi-objective optimization problem. Objective functions include design quality, cost, and schedule, while constraints include specifications and resource limitations. Algorithm mapping treats each team's design scheme as particles, with particle positions representing scheme parameters and particle velocities representing adjustment directions. Through iterative search, each team's scheme gradually converges towards the global optimum. The collaboration mechanism involves teams sharing the current optimal solution (global optimum) and their respective historical optimal solutions (local optima), learning from and referencing each other to achieve collaborative optimization.

[0053] The internal and external learning mechanisms of evolutionary computation technology employ evolutionary computation techniques such as genetic algorithms to support the iterative evolution of design solutions. Within the internal learning team, crossover and mutation operations are used to explore the solution space, generating new design solutions. Excellent solutions are retained and passed on, while inferior solutions are eliminated. External learning teams exchange solutions and share knowledge, learning from the best practices of other teams to accelerate convergence.

[0054] The adaptive step size adjustment algorithm dynamically adjusts the optimization step size based on the collaborative state. Initially, it uses a large step size to quickly explore the solution space when the design is immature in the early stages of collaboration. Later, as the solution matures, the step size is reduced for fine-tuning and to avoid oscillations. The adaptive mechanism automatically adjusts the step size based on the improvement of the objective function. If there is no improvement after multiple iterations, the step size is increased to escape local optima; if the objective continues to improve, the step size is decreased to deepen the search.

[0055] The reinforcement learning-driven negotiation model utilizes reinforcement learning techniques to train an intelligent negotiation agent. State definition uses the current design state, resource availability, and task progress as state variables. The action space includes negotiation actions such as making negotiation requests, accepting / rejecting requests, and proposing compromise solutions. The reward function is designed to provide positive rewards for behaviors that promote collaboration and resolve conflict, and negative rewards for behaviors that delay progress or escalate conflict. Through learning from numerous collaboration cases, the agent gradually masters effective negotiation strategies and provides decision-making suggestions in new collaboration scenarios.

[0056] Example 2 This embodiment provides a 3D design system based on a centralized and distributed hybrid architecture, including a memory and a processor. The memory stores a computer program, and the processor calls the computer program to execute the steps of the 3D design method based on a centralized and distributed hybrid architecture as described in Embodiment 1.

[0057] The computer program code used to implement the methods of the present invention can be written in any combination of one or more programming languages. This computer program code can be provided to a processor or controller of a general-purpose computer, a special-purpose computer, or other programmable data processing device, such that when executed by the processor or controller, the computer program code causes the functions / operations specified in the flowcharts and / or block diagrams to be implemented. The computer program code can be executed entirely on the machine, partially on the machine, as a standalone software package partially on the machine and partially on a remote machine, or entirely on a remote machine or server.

[0058] The preferred embodiments of the present invention have been described in detail above. It should be understood that those skilled in the art can make numerous modifications and variations based on the concept of the present invention without creative effort. Therefore, all technical solutions that can be obtained by those skilled in the art based on the concept of the present invention through logical analysis, reasoning, or limited experimentation on the basis of existing technology should be within the scope of protection defined by the claims.

Claims

1. A three-dimensional design method based on a centralized and distributed hybrid architecture, characterized in that, Includes the following steps: An integrated 3D design system is constructed, which integrates design at the data layer, application layer, and presentation layer. The data layer integrates design data from different disciplines and software into a central database as a single data source. The application layer enables interconnection and interoperability between different design software and business systems through standardized API interfaces and service bus architecture. The presentation layer constructs a unified human-computer interaction interface for centralized access and collaborative operation of multiple system functions. A centralized management approach is adopted to control the data management, version control, and access control functions of the 3D design system, while a distributed execution approach is adopted to coordinate the execution of design tasks and internal professional collaboration functions in the 3D design system. The various functions in the 3D design system are modularized, and different modules communicate with each other using standardized interface protocols. The modules are dynamically loaded and configured based on a plug-in architecture.

2. The three-dimensional design method based on a centralized and distributed hybrid architecture according to claim 1, characterized in that, The method further includes: for heterogeneous data received by the data layer, converting the heterogeneous data into an intermediate data format for data exchange, and using a semantic mapping mechanism to perform semantic interoperability of data in different formats.

3. The three-dimensional design method based on a centralized and distributed hybrid architecture according to claim 2, characterized in that, During the access to the heterogeneous data, the heterogeneous data is accessed through a message middleware using an enterprise service bus or message queue, and data virtualization technology.

4. The three-dimensional design method based on a centralized and distributed hybrid architecture according to claim 1, characterized in that, The method further includes setting up a multi-level access control model in the 3D design system for access control. The multi-level access control model adopts a hybrid model that combines role-based access control and attribute-based access control. The role-based access control assigns corresponding permissions to each role, while the attribute-based access control performs dynamic authorization based on project and time information.

5. A three-dimensional design method based on a centralized and distributed hybrid architecture according to claim 1, characterized in that, The method also includes adopting a microservice architecture, deploying each functional module of the 3D design system as an independent service, and using a master-slave mode or cluster deployment to build a fault tolerance mechanism so as to automatically switch to the standby node when the master node fails.

6. A three-dimensional design method based on a centralized and distributed hybrid architecture according to claim 1, characterized in that, The implementation process of the aforementioned professional internal collaboration function specifically includes: An information sharing mechanism is adopted to facilitate data interaction among various professional teams. This information sharing mechanism includes: setting up an interface registration center to uniformly register the data submission interfaces and service interfaces defined by each professional team to the interface center, forming an interface directory list, and providing interface descriptions. Configure the interface orchestration engine to orchestrate the interface call flow in a visual way, and monitor and track the interface call status.

7. A three-dimensional design method based on a centralized and distributed hybrid architecture according to claim 6, characterized in that, The implementation process of the aforementioned professional internal collaboration function also includes: An incremental synchronization mechanism is constructed to synchronize data from various professional teams. This incremental synchronization mechanism adopts change data capture technology, only synchronizing data that has changed, and sets a synchronization priority strategy according to the importance and timeliness requirements of the data.

8. A three-dimensional design method based on a centralized and distributed hybrid architecture according to claim 1, characterized in that, The method further includes treating each design team accessing the 3D design system as an intelligent agent and using a particle swarm optimization algorithm to achieve multi-team collaborative optimization; the particle swarm optimization algorithm models the collaborative design problem as a multi-objective optimization problem, with objective functions including design quality, cost and schedule, and constraints including specification requirements and resource limitations. In the optimization process of the particle swarm optimization algorithm, the design schemes of each design team are regarded as particles. The position of the particle represents the scheme parameters, and the velocity of the particle represents the scheme adjustment direction. Through iterative search, the schemes of each team gradually move closer to the global optimal solution, and the current optimal solution is shared among the design teams.

9. A three-dimensional design method based on a centralized and distributed hybrid architecture according to claim 1, characterized in that, The method also includes dynamically allocating computational tasks and storage resources to the project requirements of the 3D design system based on task characteristics, resource status, and historical performance.

10. A three-dimensional design system based on a centralized and distributed hybrid architecture, characterized in that, It includes a memory and a processor, the memory storing a computer program, and the processor calling the computer program to perform the steps of the method as described in any one of claims 1 to 9.

Images