Multi-scene adaptive digital twin model dynamic visual interaction management system

Abstract

The invention discloses a multi-scene adaptive dynamic visual interaction management system for a digital twin model. Comprising a scene configuration module used for storing respective configuration information of a plurality of application scenes, the configuration information at least comprising a three-dimensional digital twin model resource identifier, a data mapping rule and a visualization style; the model loading and scene construction module is connected to the scene configuration module and is used for acquiring and loading a corresponding three-dimensional digital twin model according to the target scene identifier so as to construct a three-dimensional visual scene; and the data access and mapping driving module is respectively connected to the scene configuration module and the model loading and scene construction module, and is used for accessing external service data and carrying out dynamic binding and state driving on the service data and corresponding components in the three-dimensional digital twin model according to a data mapping rule. The embodiment of the invention discloses a multi-scene adaptive digital twin model dynamic visual interaction management system. The viewing intuition and efficiency of the digital twinborn model are improved; the cost of understanding complex business data by a user is reduced; the adaptation capability of the system in a multi-model and multi-data scene is improved; visual expression of the entity object state is achieved, and auxiliary decision making and management are facilitated.

Description

Technical Field

[0001] This application relates to the technical field of digital twin models, and in particular to a dynamic visualization and interactive management system for digital twin models that adapts to multiple scenarios. Background Technology

[0002] In the current field of digital management, in order to monitor and display physical entities (such as parks, factories, and equipment), common solutions mainly rely on two types of systems: one is a two-dimensional information management system based on charts, lists, and floor plans; the other is a static three-dimensional model display system that can display three-dimensional appearances but usually does not have real-time data linkage capabilities.

[0003] All of the existing systems mentioned above suffer from a fundamental technical flaw: business data (i.e., the real-time status, alarms, performance parameters, etc. of entity objects) is separated from its corresponding 3D visualization model. In a 2D interface, data is presented in tabular or chart form, requiring users to mentally map the data to the entity's location. In a static 3D display, the model only reflects the object's geometric appearance, with status updates severely lagging or entirely dependent on manual refresh. This separation of data and model means that even after receiving an alarm message indicating a device malfunction, users still need to perform additional searches, location adjustments, or interface switching within the system to find and observe the device's specific condition in 3D space, severely impacting the intuitiveness of status perception and the efficiency of emergency response. Summary of the Invention

[0004] This application aims to at least partially address one of the technical problems in the related art.

[0005] Therefore, one objective of this application is to provide a dynamic visualization and interactive management system for digital twin models that adapts to multiple scenarios. Through configurable scenario templates, it enables the rapid deployment and switching of digital twin applications in multiple business scenarios. By utilizing a data-driven dynamic mapping mechanism, it intuitively reflects the real-time business status on the three-dimensional model, significantly improving the intuitiveness of information perception and decision-making efficiency. At the same time, the unified interaction framework reduces the learning and operation costs for users in different scenarios, enhancing the ease of use and reusability of the system.

[0006] To achieve the above objectives, the first aspect of this application proposes a dynamic visualization and interactive management system for digital twin models that adapts to multiple scenarios, comprising: The scenario configuration module is used to store the configuration information of multiple application scenarios. The configuration information includes at least the three-dimensional digital twin model resource identifier, data mapping rules, and visualization style. The model loading and scene construction module is connected to the scene configuration module and is used to obtain and load the corresponding three-dimensional digital twin model according to the target scene identifier in order to construct a three-dimensional visualization scene. The data access and mapping driving module is connected to the scene configuration module and the model loading and scene construction module, respectively. It is used to access external business data and dynamically bind and state-drive the business data with the corresponding components in the three-dimensional digital twin model according to the data mapping rules. The dynamic visualization rendering module is connected to the scene configuration module and the data access and mapping driver module, respectively, and is used to render and output the three-dimensional visualization scene and its dynamic state according to the visualization style; A unified interaction and control module, connected to the model loading and scene building module and the dynamic visualization rendering module, is used to provide a standardized operation interface to respond to user operations on viewing the 3D visualization scene and switching between application scenes.

[0007] In addition, the multi-scenario adapted digital twin model dynamic visualization interactive management system proposed in this application may also have the following additional technical features: In one embodiment of this application, the data mapping rule includes predefined logical judgment rules; The data access and mapping driver module is configured to trigger a visual status update of the associated model components when the business data meets specific logical conditions.

[0008] In one embodiment of this application, the data access and mapping driver module supports accessing the business data from at least two data sources, including an IoT platform, a database, and an application programming interface.

[0009] In one embodiment of this application, the visualization style includes a configurable visual theme, and the dynamic visualization rendering module is configured to apply a corresponding color scheme, lighting environment, and interface style to the three-dimensional visualization scene according to the selected visual theme.

[0010] In one embodiment of this application, the standardized operation interface provided by the unified interaction and control module is used for the interaction logic of viewpoint rotation, scaling, translation and model selection in the three-dimensional scene, which is independent of the specific three-dimensional digital twin model type currently loaded.

[0011] In one embodiment of this application, in response to a scene switching command input through the unified interaction and control module, the system provides configuration information for a new target scene by the scene configuration module, and the model loading and scene building module, the data access and mapping driving module, and the dynamic visualization rendering module work together to perform scene resource switching, data rebinding, and rendering updates.

[0012] In one embodiment of this application, the model loading and scene construction module includes a model optimization unit, used to perform detail level division or instantiation rendering processing on the loaded 3D digital twin model.

[0013] In one embodiment of this application, the configuration information is stored in the form of a structured configuration file, which defines the correspondence between scene identifiers, model resource paths, data mapping rule sets, and theme style parameters.

[0014] A second aspect of this application provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the program, it implements the functions of the multi-scenario adaptation digital twin model dynamic visualization interactive management system of the first aspect. A third aspect of this application provides a computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements the function of the first aspect's multi-scenario adapted digital twin model dynamic visualization interactive management system.

[0015] Beneficial Effects: The multi-scenario adapted digital twin model dynamic visualization interactive management system of this application, through the above technical solution, has at least the following technical effects: 1. Improved the intuitiveness and efficiency of viewing digital twin models; 2. Reduced the cost for users to understand complex business data; 3. Improved the system's adaptability to multi-model and multi-data scenarios; 4. It enables a visual representation of the state of entity objects, which is beneficial for decision-making and management.

[0016] Additional aspects and advantages of this application will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of this application. Attached Figure Description

[0017] The above and / or additional aspects and advantages of this application will become apparent and readily understood from the following description of the embodiments taken in conjunction with the accompanying drawings, wherein: Figure 1 This is a system block diagram of a dynamic visualization and interactive management system for digital twin models that adapts to multiple scenarios according to this application; Figure 2 A factory model diagram in a dynamic visualization and interactive management system for digital twin models adapted to multiple scenarios according to this application; Figure 3 This application provides a business data diagram for a dynamic, visual, and interactive management system based on a digital twin model adapted for multiple scenarios. Figure 4 This is a rendering model of the factory interior for a dynamic visualization and interactive management system based on a digital twin model adapted to multiple scenarios according to this application. Detailed Implementation

[0018] Embodiments of this application are described in detail below, examples of which are illustrated in the accompanying drawings, wherein the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions throughout. The embodiments described below with reference to the accompanying drawings are exemplary and intended to explain this application, and should not be construed as limiting this application. Rather, embodiments of this application include all variations, modifications, and equivalents falling within the spirit and scope of the appended claims.

[0019] The following describes, with reference to the accompanying drawings, a multi-scenario adapted digital twin model dynamic visualization and interactive management system according to an embodiment of this application.

[0020] like Figures 1-4 As shown in the figure, a multi-scenario adapted digital twin model dynamic visualization and interactive management system according to an embodiment of this application includes: The scenario configuration module is used to store the configuration information for multiple application scenarios. The configuration information includes at least the 3D digital twin model resource identifier, data mapping rules, and visualization style. The model loading and scene building module is connected to the scene configuration module. It is used to obtain and load the corresponding 3D digital twin model based on the target scene identifier in order to build a 3D visualization scene. The data access and mapping driver module is connected to the scene configuration module and the model loading and scene construction module, respectively. It is used to access external business data and dynamically bind and state-drive the business data with the corresponding components in the 3D digital twin model according to the data mapping rules. The dynamic visualization rendering module is connected to the scene configuration module and the data access and mapping driver module, respectively, and is used to render and output the 3D visualization scene and its dynamic state according to the visualization style. The unified interaction and control module, connected to the model loading and scene building module and the dynamic visualization rendering module, provides a standardized operation interface to respond to users' viewing operations of 3D visualization scenes and switching control between application scenes.

[0021] Specifically, the system operation process.

[0022] Step 1: Scene configuration module.

[0023] During the system deployment phase, factory engineers preset multiple "scenario configuration information" for different management responsibilities in the scenario configuration module.

[0024] The "Production Command Center" scenario's configuration information includes: Model resource identifier: A simplified model that links to the entire plant's 3D white model, the outline models of each workshop, and key equipment (such as stamping machine A and welding robot cluster B).

[0025] Data mapping rules: Define a series of business logics. For example, one rule associates the "Overall Equipment Effectiveness (OEE) value" with the "model color", stipulating that when the OEE value is below 85%, the model of the corresponding equipment should be yellow; another rule stipulates that when the equipment reports an "emergency shutdown" status, its model should be red and flashing.

[0026] Visualization style: Set to the theme of "macro situation", using clear high-contrast colors and simple lighting effects to ensure that it is still easy to see when viewed from a distance on the large screen.

[0027] The “Welding Workshop Diagnosis” scenario includes configuration information such as a more refined welding robot model, more detailed current and voltage data mapping rules, and a “high-fidelity” rendering theme that focuses on equipment details.

[0028] Step 2: Model Loading and Scene Building Module - Build the 3D Stage According to the Blueprint. For example, when the production director arrives at the command center in the morning, he selects the "Production Command Center" scenario on the system interface. The model loading and scenario building module then receives the instruction and retrieves the scenario's configuration information from the scenario configuration module. Next, based on the "model resource identifier" in the information, it accurately loads the entire plant's 3D white model and simplified models of each key piece of equipment from the model library, and builds a complete 3D visualization scene of the factory on the screen.

[0029] Step 3: Data access and mapping driver module, connecting reality and virtuality, driving dynamic changes. At the same time, the data access and mapping driver module begins to operate. It continuously receives real-time production data streams from the factory's manufacturing execution system and IoT platform.

[0030] More importantly, it executes the core binding and driving logic based on the "data mapping rules" of the current scene obtained from the scene configuration module: it will determine whether the real-time data (such as "the OEE of welding robot B drops to 82%) meets the conditions of a certain rule ("OEE<85%).

[0031] Once the conditions are met, the module immediately triggers an action, sending a command to the system to update the visualization status of the "Welding Robot B" model component (changing its color to yellow).

[0032] Step 4: Dynamic visualization rendering module, which generates the final visual image.

[0033] The dynamic visualization rendering module is responsible for the final visual presentation. On one hand, it obtains the current scene's "visual style" (such as the "macro-level" theme) from the scene configuration module to determine the overall rendering style, lighting, and color tone. On the other hand, it receives model state update instructions from the data access and mapping driving module.

[0034] Combining these two aspects, the module renders the 3D scene in real time: it renders the entire factory as a macro theme, and specifically renders the abnormal "welding robot B" in yellow.

[0035] Step 5: Unify the interaction and control module to provide a better user experience.

[0036] The production director interacts with the system through standardized operating interfaces (such as mouse and touchscreen) provided by the unified interaction and control module. He can use standardized drag-and-drop and zoom operations to view the 3D factory from any angle. When he spots the yellow welding robot B, he can click to select it, and the system will then display detailed data about the device in the sidebar. If he wants to conduct further analysis, he simply clicks the "Drill Down Diagnostics" button. This button will issue a scene switching control command to the system.

[0037] In response to this command, the unified interaction and control module coordinates with other modules: the scene configuration module provides the configuration for the "welding workshop diagnosis" scene; the model loading and scene building module switches to loading a detailed robot model; the data access and mapping drive module rebinds the robot's detailed sensor data; and the dynamic visualization rendering module applies a new "high-fidelity" theme for rendering.

[0038] In one embodiment of this application, the data mapping rule includes predefined logical decision rules; The data access and mapping driver module is configured to trigger a visual status update of the associated model components when business data meets specific logical conditions.

[0039] The logical judgment rules in the data mapping rules and the triggering mechanism of the data access and mapping driver module do not depend on any specific device or industry background.

[0040] Abstract structure of logical decision rules.

[0041] The "predefined logical decision rules" contained in the "data mapping rules" are essentially an instruction pair with an "IF-THEN" structure.

[0042] The "IF" part (logical condition) is a Boolean expression that represents one or more business data fields and a preset threshold, status value, or the relationship between them. For example, a rule can be defined as: IF (data point A > threshold X) and (data point B == status Y).

[0043] The "THEN" section (trigger action) explicitly specifies what visual state change the system should perform on the specified 3D model component when the condition in the "IF" section is evaluated as "true". For example: THEN sets the color attribute of the target model component to red and activates its blinking animation.

[0044] The general triggering process of the module.

[0045] The data access and mapping driver module is configured as a real-time event handler, and its operation follows the general process below: Input: The module continuously receives structured business data streams from external sources. Each data entry contains a specific identifier (such as "target ID") and a series of numeric or status fields.

[0046] Matching and evaluation: For each piece of input data, the module searches for all "logical decision rules" associated with it based on its identifier.

[0047] It then substitutes the field values ​​from the data into the "IF" part (logical condition) of each rule for calculation and Boolean evaluation.

[0048] Judgment and Trigger: If the calculation result shows that the current business data meets the complete logical condition of a certain rule (that is, the "IF" statement is true), then the module triggers the instruction defined in the "THEN" part of the rule.

[0049] Output Command: The triggered command is a precise operation command, the format of which can be abstractly understood as: {Command: "Update visualization state", Target: [Model component identifier], Parameters: [New color, animation, texture, and other attributes]}. This command is immediately dispatched to the system component responsible for rendering.

[0050] Through this mechanism, any change in business data that conforms to the rules and logic will be automatically and in real time converted into modification instructions for the visual representation of specific objects in the 3D virtual scene. This achieves an automated, rule-driven mapping from the "data domain" to the "visual domain".

[0051] In one embodiment of this application, the data access and mapping driver module supports accessing business data from at least two data sources, including an IoT platform, a database, and an application programming interface.

[0052] Specifically, the data access and mapping driver module supports accessing business data from at least two data sources, including IoT platforms, databases, and application programming interfaces. The implementation steps are as follows: Configuration and Initialization: Configure connection parameters for at least two data sources for the module. For example, configure the real-time data subscription address of the IoT platform (such as an MQTT topic), and the database query statement and polling period.

[0053] Establishing Connections and Subscriptions: Based on the configuration, the module simultaneously establishes connections with various data sources. For example, it establishes a network subscription channel with an IoT platform to receive real-time data streams; and it establishes a connection pool with a database for querying.

[0054] Concurrent access and reception: The module runs data reception tasks in parallel. For example, it continuously listens for and receives sensor data packets from the IoT platform; at the same time, it periodically executes queries on the database to obtain aggregated business data.

[0055] Standardization and Output: The module converts the received heterogeneous data (such as streaming data and query results) into an internal standard format, adds metadata such as timestamps, and then outputs it to the downstream mapping and rendering logic through the internal interface to drive the state update of the 3D model components.

[0056] In one embodiment of this application, the visualization style includes a configurable visual theme, and the dynamic visualization rendering module is configured to apply a corresponding color scheme, lighting environment and interface style to the 3D visualization scene according to the selected visual theme.

[0057] The implementation steps are as follows: Define and store visual themes: In the system configuration, define one or more visual themes. Each theme is a set of preset parameters, specifically including: Color scheme: Defines a set of standard color values ​​such as scene background color, model default material color, highlight color, and warning color.

[0058] Lighting environment: Defines the direction, intensity, and color of the main light source, as well as the parameters of auxiliary light sources such as ambient light and hemispherical light.

[0059] Interface style: Defines the style of two-dimensional user interface controls superimposed on a three-dimensional scene, such as panel background, font, button style, chart color scheme, etc.

[0060] These theme configurations are stored in a structured manner in the scene configuration module and associated with specific application scenarios.

[0061] Loading and applying theme parameters: When a user or system logic selects a target scene, the dynamic visualization rendering module retrieves the visual theme configuration associated with that scene from the scene configuration module. Subsequently, the module performs the following application operations: Set the color scheme parameters in the theme to the global material and post-processing parameters of the 3D rendering engine.

[0062] Based on the lighting environment parameters in the theme, create and configure the corresponding light source objects in the 3D scene.

[0063] Pass the interface style parameters from the theme to the graphical user interface framework to uniformly update the visual appearance of all 2D UI components.

[0064] Driving Scene Rendering: After applying new visual theme parameters, the dynamic visualization rendering module drives the 3D rendering engine and UI framework to recalculate and draw the current 3D scene and all its components based on new color, lighting and interface style parameters, and outputs the final merged visual image.

[0065] Dynamic theme switching: The system supports runtime switching of visual themes. When a switching command is triggered, the dynamic visualization rendering module repeats the steps, instantly loading the parameters of the new theme and re-rendering the scene, thereby achieving dynamic visual style for the entire application.

[0066] In one embodiment of this application, the standardized operation interface provided by the unified interaction and control module is used for the interaction logic of viewpoint rotation, scaling, translation and model selection in the 3D scene, which is independent of the specific 3D digital twin model type currently loaded.

[0067] Specifically, the module first initializes a set of general-purpose interaction controllers to handle raw input events from the mouse, keyboard, or touchscreen. Then, regardless of whether the currently loaded model is a factory equipment model or a park building model, the module uniformly converts these input events (such as mouse dragging, scrolling, and screen clicking) into standard scene operation commands that do not depend on the specific model geometry, such as "rotate the view along the horizontal axis," "zoom in twice," or "fire a selection ray." Finally, these standardized commands are sent to the 3D rendering engine and scene graph system, which execute them based on the general 3D coordinate system and object tree of the current scene, thereby driving changes in the scene perspective or highlighting the selected model components, ensuring the consistency of the user's operating experience when switching between different digital twin application scenarios.

[0068] In one embodiment of this application, in response to a scene switching command input through the unified interaction and control module, the scene configuration module provides configuration information for the new target scene, and the model loading and scene construction module, the data access and mapping driving module, and the dynamic visualization rendering module work together to perform scene resource switching, data rebinding, and rendering updates.

[0069] Specifically, firstly, the unified interaction and control module captures and parses the user's switching command to determine the target scene identifier. Then, the scene configuration module retrieves and provides the corresponding complete configuration information (including model resources, mapping rules, and visual themes) based on the identifier. Subsequently, the system coordinates the various modules to perform the switching in sequence: the model loading and scene construction module loads the target 3D model and constructs the scene according to the new configuration, while releasing the old scene resources. The data access and mapping drive module, based on the new rule set, unbinds the data from the original model and establishes a dynamic binding relationship with the new scene model components. At the same time, the dynamic visualization rendering module applies the new visual theme (color, lighting, etc.) and renders the newly constructed scene and its initial state, thereby completing the entire process of resource switching, data rebinding, and visual updates from the old scene to the new target scene.

[0070] In one embodiment of this application, the model loading and scene construction module includes a model optimization unit, which is used to perform detail level division or instantiation rendering processing on the loaded 3D digital twin model.

[0071] The model loading and scene building module includes a model optimization unit. The specific steps of model processing are as follows: After the module loads the original 3D digital twin model, the optimization unit first performs detail level subdivision processing on the model. That is, based on the distance range where the model may be observed in the scene, it automatically generates multiple versions with different polygon count precisions and establishes mapping relationships. Simultaneously, for a large number of repetitive model components in the scene, the unit performs instantiation rendering processing, storing only one copy of its geometric and material data in video memory, and batch-drawing multiple instances during rendering using transformation matrices. These optimization processes are completed synchronously during the model loading stage, and the processing results are integrated into the constructed scene data structure. This allows the subsequent dynamic visualization rendering module to automatically switch the appropriate level of detail based on the camera distance and perform efficient batch rendering of repetitive objects, ultimately significantly improving the loading speed and real-time rendering performance of large-scale complex 3D scenes.

[0072] In one embodiment of this application, the configuration information is stored in the form of a structured configuration file, which defines the correspondence between scene identifiers, model resource paths, data mapping rule sets, and theme style parameters.

[0073] Specifically, the system creates and uses a structured configuration file in JSON or XML format, which explicitly defines one or more scene entries. Each entry establishes key-value pairs that correspond to "scene identifier," "model resource path," "data mapping rule set," and "theme style parameters." When the system needs to initialize or switch scenes, the scene configuration module reads and parses the corresponding configuration file, retrieves the associated "model resource path" based on the "scene identifier," provides it to the model loading module, parses the "data mapping rule set" into executable logic, provides it to the data mapping driver module, and converts the "theme style parameters" into configuration instructions for the rendering engine, providing them to the dynamic visualization rendering module. Thus, a centralized configuration file drives all core modules to collaboratively complete the construction, binding, and rendering of the specified scene.

[0074] This application proposes an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor. Specifically, when the processor executes the program, it implements the functions of the aforementioned multi-scenario adapted digital twin model dynamic visualization interactive management system.

[0075] This application provides a computer-readable storage medium storing a computer program thereon. Specifically, when the program is executed by a processor, it implements the function of a dynamic, visual, and interactive management system for digital twin models that adapts to multiple scenarios.

[0076] The implementation steps of this system are as follows: Scene configuration: Create a configuration file for each application scene to define its corresponding 3D model, data mapping rules and visual theme.

[0077] Scene building: Based on the scene selected by the user, load the 3D model in the corresponding configuration file to build the initial 3D visualization scene.

[0078] Data binding and driving: Business data is accessed from at least two external data sources, and real-time logical judgments are made based on scenario rules. When the data meets specific conditions, state update instructions for associated 3D model components are automatically triggered.

[0079] Dynamic rendering: The system renders the entire scene based on its visual theme and receives data-driven instructions in real time to update the visualization status of specific model components, thus forming the final dynamic image.

[0080] Interaction and Switching: A unified interaction interface is provided for users to operate the 3D scene. When a user switches scenes, the system coordinates all modules to reload models, bind data, and apply the new theme according to the configuration file of the new scene, completing a seamless switch.

[0081] In summary, the multi-scenario adapted digital twin model dynamic visualization interactive management system of this application, through the above technical solutions, has at least the following technical effects: 1. Improved the intuitiveness and efficiency of viewing digital twin models; 2. Reduced the cost for users to understand complex business data; 3. Improved the system's adaptability to multi-model and multi-data scenarios; 4. It enables a visual representation of the state of entity objects, which is beneficial for decision-making and management.

[0082] In the description of this specification, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of indicated technical features. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one of that feature. In the description of this application, "multiple" means at least two, such as two, three, etc., unless otherwise explicitly specified.

[0083] In the description of this specification, the references to terms such as "one embodiment," "some embodiments," "example," "specific example," or "some examples," etc., refer to specific features, structures, materials, or characteristics described in connection with that embodiment or example, which are included in at least one embodiment or example of this application. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples. Moreover, without contradiction, those skilled in the art can combine and integrate the different embodiments or examples described in this specification, as well as the features of different embodiments or examples.

[0084] Although embodiments of this application have been shown and described above, it is understood that the above embodiments are exemplary and should not be construed as limiting this application. Those skilled in the art can make changes, modifications, substitutions and variations to the above embodiments within the scope of this application.

Claims

1. A dynamic visual interactive management system for digital twin models that adapts to multiple scenarios, characterized in that, include: The scenario configuration module is used to store the configuration information of multiple application scenarios. The configuration information includes at least the three-dimensional digital twin model resource identifier, data mapping rules, and visualization style. The model loading and scene construction module is connected to the scene configuration module and is used to obtain and load the corresponding three-dimensional digital twin model according to the target scene identifier in order to construct a three-dimensional visualization scene. The data access and mapping driving module is connected to the scene configuration module and the model loading and scene construction module, respectively. It is used to access external business data and dynamically bind and state-drive the business data with the corresponding components in the three-dimensional digital twin model according to the data mapping rules. The dynamic visualization rendering module is connected to the scene configuration module and the data access and mapping driver module, respectively, and is used to render and output the three-dimensional visualization scene and its dynamic state according to the visualization style; A unified interaction and control module, connected to the model loading and scene building module and the dynamic visualization rendering module, is used to provide a standardized operation interface to respond to user operations on viewing the 3D visualization scene and switching between application scenes.

2. The system according to claim 1, characterized in that, The data mapping rules include predefined logical decision rules; The data access and mapping driver module is configured to trigger a visual status update of the associated model components when the business data meets specific logical conditions.

3. The system according to claim 1, characterized in that, The data access and mapping driver module supports accessing the business data from at least two data sources, including IoT platforms, databases, and application programming interfaces.

4. The system according to claim 1, characterized in that, The visualization style includes configurable visual themes, and the dynamic visualization rendering module is configured to apply corresponding color schemes, lighting environments, and interface styles to the 3D visualization scene based on the selected visual theme.

5. The system according to claim 1, characterized in that, The standardized operation interface provided by the unified interaction and control module is used for the interaction logic of viewpoint rotation, scaling, translation and model selection in the 3D scene, and is independent of the specific 3D digital twin model type currently loaded.

6. The system according to claim 1, characterized in that, The system responds to the scene switching command input through the unified interaction and control module. The scene configuration module provides configuration information for the new target scene, and the model loading and scene construction module, data access and mapping driving module, and dynamic visualization rendering module work together to perform scene resource switching, data rebinding, and rendering updates.

7. The system according to claim 1, characterized in that, The model loading and scene construction module includes a model optimization unit, which is used to perform detailed level division or instantiation rendering processing on the loaded 3D digital twin model.

8. The system according to claim 1, characterized in that, The configuration information is stored in the form of a structured configuration file, which defines the correspondence between scene identifiers, model resource paths, data mapping rule sets, and theme style parameters.

9. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the program, it implements the functions of the system as described in any one of claims 1 to 8.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the program is executed by the processor, it implements the functions of the system as described in any one of claims 1 to 8.

Images