Hot updating and hot loading method for digital twin development management platform

Abstract

The invention discloses a hot updating and hot loading method for a digital twin development management platform, and aims to solve the problems that in the prior art, it is difficult to quickly respond to data changes, it is difficult to ensure that a model can reflect the state of a physical entity in real time, and it is difficult to ensure the consistency and real-time performance of data in the collecting, transmitting and processing processes. The method comprises the following steps: in response to a platform hot update instruction, analyzing content needing to be updated and a corresponding hot patch; and updating a platform configuration file, a platform asset file and a project and scene file, and after updating is completed, loading the new project and scene file into the digital twin development management platform to ensure that the platform loads the latest settings, projects and scenes. According to the method, the data change is quickly responded under the condition of not interrupting the service, so that the model can reflect the state of the physical entity in real time, and the overall flexibility, reliability and efficiency of the platform are improved.

Description

Technical Field

[0001] This application relates to the technical field of digital twin development management platforms. Background Art

[0002] The maintenance and upgrade process of digital twin development management platforms is relatively complex. The platform usually consists of a data acquisition layer, a data processing layer, a model construction layer, and an application layer, involving multiple technologies and components, such as sensors, Internet of Things devices, cloud computing, edge computing, AI, and machine learning algorithms. During the maintenance process, common technical challenges include data consistency and real-time issues, model accuracy and complexity, and system stability issues. When upgrading, problems such as compatibility between new and old versions and integration with third-party systems may be encountered.

[0003] Currently, the construction of digital twin cities in China is still in the initial exploration stage, facing problems of insufficient data support and insufficient technological innovation. Moreover, currently, digital projects are mainly project-level development and applications. Since the development process requires the development of digital twin scenarios for specific business scenarios, the digital twin development platform technology is relatively professional and has high requirements for developers. Generally, the owners do not have the ability to maintain digital twin projects sustainably, resulting in unsustainable construction and development.

[0004] In this case, how to quickly respond to data changes, ensure that the model can reflect the state of the physical entity in real time, and ensure the consistency and real-time nature of data during the processes of collection, transmission, and processing has become an issue to be solved. Summary of the Invention

[0005] This application provides a hot update and hot loading method for a digital twin development management platform, aiming to solve the problems in the prior art that it is difficult to quickly respond to data changes, ensure that the model can reflect the state of the physical entity in real time, and ensure the consistency and real-time nature of data during the processes of collection, transmission, and processing.

[0006] In a first aspect, a hot update and hot loading method for a digital twin development management platform includes:

[0007] In response to a platform hot update instruction, parse the content to be updated and the corresponding hot patch;

[0008] Update the platform configuration file, including: obtain the latest configuration file from the server backend program, where the configuration file contains service addresses, rendering parameters, and data service interface addresses; compare the new configuration file with the local configuration file to identify the parts that need to be updated, and only update the changed parts to avoid unnecessary operations on the unchanged parts; after the update is completed, the digital twin development management platform reloads the configuration file to ensure that the new configuration takes effect;

[0009] Update the platform asset files, including: obtaining the MD5 code list of the asset files from the server backend program, comparing whether the MD5 codes provided by the server backend program are the same as those of the local cached files. If they are the same, it means the asset files have not changed, and the local cached files are directly used; otherwise, it means the asset files have been updated. Download the new asset files from the asset library and replace the old asset files in the local cache. After the update is completed, load the new asset files into the digital twin development management platform to ensure that the platform loads the latest asset files and performs rendering;

[0010] Update the project and scene files, including: obtaining the MD5 code list of the project and scene files from the server backend program, comparing whether the MD5 codes provided by the server backend program are the same as those of the local cached files. If they are the same, it means the project and scene files have not changed, and the local cached files are directly used; otherwise, download the new project and scene files from the project scene library and replace the old files in the local cache. After the update is completed, load the new project and scene files into the digital twin development management platform to ensure that the platform loads the latest settings, projects, and scenes.

[0011] In the above solution, optionally, after the asset file update and before the project and scene file update, it also includes the update of the unstructured data interpretation code:

[0012] Obtain the latest unstructured data interpretation code from the server backend program. The unstructured data interpretation code is used to process the parsing and conversion of real-time data. Use bytecode operation tools to generate hot patches and dynamically update the interpretation code without restarting the platform. The updated interpretation code will take effect immediately to ensure that the platform can correctly process new data formats and logics.

[0013] In the above solution, optionally, after the project and scene file update, it also includes static and dynamic data binding:

[0014] Rebind the static and dynamic data according to the updated configuration files and asset files. Among them, the static data is directly loaded from the local cache; the dynamic data is obtained from the server backend program through the data service interface and is updated in real time to the twin model.

[0015] In the above solution, optionally, it also includes:

[0016] After the digital twin development management platform completes all updates, the digital twin development management platform publishes the updated projects and scenes to the project scene library;

[0017] Automatically run a series of verification tests to ensure that the updated project and scenarios can run properly without introducing new problems; if the tests pass, prompt the user that the update is complete; if problems are found during the tests, roll back to the state before the update, record the error information, and notify the developer for repair.

[0018] In the above solution, optionally, it further includes: after the hot update is completed, automatically clean up the old files that are no longer used in the local cache to free up storage space.

[0019] In the above solution, optionally, before starting the hot update, it further includes: back up the configuration files, asset files, project, and scenario files of the current platform to ensure data security during the update process.

[0020] In the above solution, optionally, it further includes:

[0021] The front-end management page performs addition, deletion, and modification operations on the script code through a JavaScript script code update tool;

[0022] The server back-end program loads the updated script code and sends it to the data service program;

[0023] The data service program returns structured data to complete static and dynamic data binding;

[0024] Publish the project to the project and scenario library;

[0025] After the project release is completed, the digital twin development management platform ends.

[0026] In the above solution, optionally, the updated asset files include 3D geometric models, geological model data, reservoir model data, seismic data, wellbore data, animation data, model materials, special effects, and plotting.

[0027] In a second aspect, a digital twin development management platform hot update and hot loading system includes:

[0028] A hot update plugin for responding to the platform hot update instruction and parsing the content to be updated and the corresponding hot patch;

[0029] A configuration file update module for obtaining the latest configuration file from the server back-end program, where the configuration file contains service addresses, rendering parameters, and data service interfaces; comparing the new configuration file with the local configuration file to identify the parts that need to be updated, and only updating the changed parts to avoid unnecessary operations on the unchanged parts; after the update is completed, the digital twin development management platform reloads the configuration file to ensure that the new configuration takes effect;

[0030] Asset file update module, which is used to obtain the MD5 code of the asset file from the server backend program, compare whether the MD5 code provided by the server backend program is the same as the MD5 code of the local cached file. If they are the same, it means the asset file has not changed, and the local cached file is directly used; otherwise, it means the asset file has been updated. A new asset file is downloaded from the asset library and replaces the old asset file in the local cache. After the update is completed, the new asset file is loaded into the digital twin development management platform to ensure that the platform loads the latest asset file and performs rendering.

[0031] Project and scene file update module, which is used to obtain the MD5 code of the project and scene file from the server backend program, compare whether the MD5 code provided by the server backend program is the same as the MD5 code of the local cached file. If they are the same, it means the project and scene file has not changed, and the local cached file is directly used; otherwise, a new project and scene file is downloaded from the project scene library and replaces the old file in the local cache. After the update is completed, the new project and scene file are loaded into the digital twin development management platform to ensure that the platform loads the latest settings, projects, and scenes.

[0032] Thirdly, a digital twin development management platform includes:

[0033] Data lake, as a centralized repository for storing raw data, capable of storing a large amount of unstructured, semi-structured, and structured data;

[0034] Data service program, running on the server, used to obtain unstructured data from the data lake, convert it into structured static and dynamic data, and send it back to the twin editor or twin application.

[0035] Twin editor, a tool for creating, editing, and managing digital twins;

[0036] Digital twin application, running in the cloud, used to receive the updated configuration file, asset file, and project scene file and perform loading and rendering operations.

[0037] Server backend program, responsible for handling the logic of the digital twin application, managing the update, addition, or deletion of the interpreted function code, storing it, managing the MD5 codes of model assets and project scene files, and managing the configuration file.

[0038] Model asset library, used to store model assets;

[0039] Project scene library, used to store project and scene files;

[0040] Local asset cache, a caching mechanism for static resources stored on the user device, used to store configuration files, model asset files, and project scene files.

[0041] Compared with the prior art, the present application has at least the following beneficial effects:

[0042] Based on further analysis and research of the problems in the prior art, it is recognized that the prior art has problems such as difficulty in quickly responding to data changes, ensuring that the model can reflect the state of physical entities in real time, and ensuring the consistency and real-time nature of data during the processes of collection, transmission, and processing. By parsing the content to be updated, accurately updating the configuration and asset files, and synchronizing the engineering and scenario files, only the changed parts are efficiently updated, unnecessary operations are avoided, and the consistency and real-time nature of data during the processes of collection, transmission, and processing are ensured. This method not only improves the stability and data accuracy of the system, but also simplifies the maintenance process, realizes quick response to data changes without interrupting the service, enables the model to reflect the state of physical entities in real time, and thus improves the overall flexibility, reliability, and efficiency of the platform.

[0043] The present application achieves real-time updates of three-dimensional geometric models, geological models, reservoir models, seismic data, and wellbore data, as well as real-time hot updates of animations, special effects, and plotting. Only the changed parts need to be updated, and there is no need to redownload the entire application. Users can hardly feel the update process, and the experience is more fluent. Bugs or updated data in the online application can be quickly fixed, shortening the update cycle. BRIEF DESCRIPTION OF THE DRAWINGS

[0044] Figure 1 It is a schematic flow chart of the hot update and hot loading method of the digital twin development management platform provided by an embodiment of the present application.

[0045] Figure 2 It is a schematic diagram of the hot update and hot loading framework of the digital twin development management platform provided by an embodiment of the present application.

[0046] Figure 3 It is a schematic flow chart of the hot update and hot loading trigger process of the digital twin development management platform provided by an embodiment of the present application. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0047] In order to make the objectives, technical solutions, and advantages of the present application clearer, the present application will be further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0048] In the description of the present application: Unless otherwise specified, expressions such as "including", "comprising", and "having" also mean "not limited to" (certain units, components, materials, steps, etc.).

[0049] In view of the problem that existing technologies are difficult to respond quickly to data changes, ensure that the model can reflect the status of physical entities in real time, and ensure the consistency and real-time of data during collection, transmission, and processing, this application proposes a hot update and hot loading method for a digital twin development management platform.

[0050] Hot update means allowing an application to update some code or resources while it is running without restarting the entire application.

[0051] The realization of the hot update function ensures that after the construction of the digital twin scene is completed, the owner's R&D personnel can continue to build and update the digital twin scene according to the specific needs in the later stage, or on the basis of the hot update framework, other services can carry out the continuous construction of the digital twin scene through service outsourcing to ensure the sustainable development of the digital twin system.

[0052] In one embodiment, a hot update and hot loading method of a digital twin development management platform is provided, including:

[0053] Responding to the platform hot update instruction, parsing the content that needs to be updated and the corresponding hot patch;

[0054] Update the platform configuration file, including: obtaining the latest configuration file from the server backend program, the configuration file includes the service address, rendering parameters and data service interface; comparing the new configuration file with the local configuration file, identifying the part that needs to be updated, and only updating the changed part to avoid unnecessary operations on the unchanged part; after the update is completed, the digital twin development management platform reloads the configuration file to ensure that the new configuration takes effect;

[0055] Update the platform asset file, including: obtaining the MD5 code of the asset file from the server backend program, comparing the MD5 code provided by the server backend program with the MD5 code of the local cache file to see if they are the same. If they are the same, it means that the asset file has not changed, and the local cache file is used directly; otherwise, it means that the asset file has been updated, download the new asset file from the asset library, and replace the old asset file in the local cache; after the update is completed, load the new asset file into the digital twin development management platform to ensure that the platform loads the latest asset file and renders it;

[0056] Update the project and scene files, including: obtaining the MD5 codes of the project and scene files from the server backend program, comparing whether the MD5 codes provided by the server backend program are the same as those of the local cache files. If they are the same, it means that the project and scene files have not changed, and the local cache files can be directly used; otherwise, download the new project and scene files from the project scene library and replace the old files in the local cache. After the update is completed, load the new project and scene files into the digital twin development management platform to ensure that the platform loads the latest settings, projects, and scenes.

[0057] In this embodiment, a method and related device for hot update and hot loading of a digital twin development management platform are provided. The method includes:

[0058] Obtain unstructured static and dynamic interpretation codes in real time. Since the interpretation codes are JS script programs, bytecode operation tools such as ASM and CGLib can be used to generate and apply hot patches.

[0059] Update the platform or project configuration files, including many parameters such as service addresses and rendering parameters.

[0060] Real-time update of asset data, updating the asset files in the application (including assets such as 3D models, geological model data, reservoir model data, wellbore data, seismic data, animation data, model materials, special effects, and plotting).

[0061] Update of project and scene files. The project and scene files are stored in the file server, and the file information and file MD5 codes are stored in the data table of the server backend program. When the twin editor or twin application downloads and loads the local cache files from the file server.

[0062] Through the method steps provided in this embodiment, not only the accurate update of the necessary parts is achieved, but also the consistency and real-time nature of the data are ensured, the stability and flexibility of the system are enhanced, and the maintenance process is simplified at the same time. This method effectively solves the problems such as interrupted services, data inconsistency, and resource waste existing in traditional update methods, and provides a strong guarantee for the continuous and stable operation of the digital twin development management platform.

[0063] In one embodiment, after the asset file update and before the project and scene file update, it also includes the update of unstructured data interpretation codes:

[0064] Obtain the latest unstructured data interpretation codes from the server backend program. The unstructured data interpretation codes are used to process the parsing and conversion of real-time data, generate hot patches using bytecode operation tools, and dynamically update the interpretation codes without restarting the platform. The updated interpretation codes will take effect immediately to ensure that the platform can correctly process new data formats and logics.

[0065] In this embodiment, unstructured static and dynamic interpretation code is obtained in real time. Since the interpretation code is a JS script program, bytecode operation tools such as ASM and CGLib can be used to generate and apply hot patches.

[0066] To further enhance the ability and flexibility of the digital twin development management platform to process real-time data, after the asset file is updated and before the project and scene files are updated, there is also an update step specifically for the unstructured data interpretation code. The specific process is as follows:

[0067] Obtain the latest unstructured data interpretation code from the server backend program: First, the system will automatically download the latest unstructured data interpretation code from the server backend program. This part of the code is mainly responsible for processing the parsing and conversion of real-time data, ensuring that the platform can accurately understand and apply data from various sources.

[0068] Generate hot patches using bytecode operation tools: After obtaining the latest version of the interpretation code, use bytecode operation tools to generate hot patches. This method allows the existing interpretation code to be dynamically updated without restarting the platform, greatly reducing the service interruption time caused by maintenance.

[0069] Dynamically update the interpretation code and take effect immediately: Through the above hot patches, the new interpretation code will be dynamically loaded into the running system and take effect immediately. This means that the platform can seamlessly switch to the new data processing logic without affecting ongoing operations or services.

[0070] Ensure correct handling of new data formats and logics: Finally, the updated interpretation code enables the platform to support new data formats and business logics, ensuring the adaptability and forward-looking of the system. This is particularly important for digital twin applications that need to quickly respond to market changes and technological advancements.

[0071] Through the update of the unstructured data interpretation code, not only the processing ability of the platform for unstructured data is strengthened, but also the overall efficiency is improved by reducing downtime and simplifying the maintenance process. In addition, it also demonstrates how to overcome existing challenges through technical means, such as maintaining data consistency and real-time performance, improving system stability, and addressing compatibility issues between new and old versions, so as to better serve the continuous development and innovation of digital twin projects.

[0072] In one embodiment, after the project and scene files are updated, there is also static and dynamic data binding:

[0073] Rebind static and dynamic data according to the updated configuration file and asset file; among them, static data is directly loaded from the local cache; dynamic data is obtained from the server backend program through the data service interface and updated in real time to the twin model.

[0074] In this embodiment, through the above method of static and dynamic data binding, the digital twin development management platform can effectively handle different types of data requirements without interrupting the service. It not only utilizes the local cache to improve efficiency but also ensures the timeliness and accuracy of information with the help of the real-time data update mechanism. This method not only solves the challenges of data consistency and real-time performance but also provides users with a more reliable and efficient digital twin solution, further promoting the development of digital twin technology in practical applications.

[0075] In one embodiment, it further includes:

[0076] After the digital twin development management platform completes all updates, it publishes the updated projects and scenarios to the project scenario library;

[0077] Automatically runs a series of verification tests to ensure that the updated projects and scenarios can run normally without introducing new problems; if the tests pass, it notifies the user that the update is complete; if problems are found during the tests, it rolls back to the state before the update, records the error information, and notifies the developers for repair.

[0078] In this embodiment, after the digital twin development management platform completes all update steps (including but not limited to responding to hot update instructions, updating configuration files, asset files, project and scenario files, and performing static and dynamic data binding), it also includes a crucial subsequent step: publishing the updated projects and scenarios to the project scenario library and automatically running a series of verification tests to ensure the stability and reliability of the system.

[0079] The specific process is as follows:

[0080] Publishing to the project scenario library: Once all update operations are completed, the digital twin development management platform publishes the updated projects and scenarios to the project scenario library. This step ensures that all users can access the latest version and provides support for subsequent use or further development.

[0081] Automatically running verification tests: The system automatically runs a series of preset verification tests, which are designed to check whether the updated projects and scenarios can run normally and detect whether new problems are introduced. The verification tests cover multiple aspects such as functional testing, performance testing, and compatibility testing to comprehensively evaluate the effect of the update.

[0082] Taking corresponding measures according to the test results:

[0083] If the tests pass: The system will notify the user that the update has been completed successfully, and the user can start using the functions and services of the new version.

[0084] If problems are found during testing: The system will automatically roll back to the state before the update to ensure that the continuity and stability of the service are not affected. At the same time, the system will record detailed error information and notify relevant developers for repair. This approach not only reduces the impact of potential risks on users but also provides a basis for quickly resolving issues.

[0085] Through this series of steps, this method not only ensures the security and reliability of the update process of the digital twin development management platform but also improves the maintenance efficiency of the entire system. It effectively combines automated testing and rollback mechanisms, minimizing the negative impact of update failures and promoting the sustainable development of digital twin technology in practical applications. This rigorous update strategy is crucial for ensuring high-quality service delivery, especially in complex and technically demanding fields such as the construction of digital twin cities.

[0086] In one embodiment, it further includes: After the hot update is completed, automatically clean up the old files that are no longer used in the local cache to free up storage space.

[0087] In this embodiment and by introducing the function of automatically cleaning up the old files that are no longer used in the local cache, the digital twin development management platform in this embodiment can achieve effective management and optimization of resources without affecting normal services, thereby providing a more stable and efficient user experience.

[0088] In one embodiment, before starting the hot update, it further includes: Back up the configuration files, asset files, projects, and scenario files of the current platform to ensure the security of data during the update process.

[0089] By performing a complete backup before starting the hot update, the method in this embodiment not only enhances the security of the update process but also provides an effective solution for dealing with emergencies. This method ensures that even in the worst-case scenario, data integrity can be maximally protected and the stable operation of the system can be maintained, which is particularly important for the digital twin development management platform that requires high reliability and continuous availability.

[0090] In one embodiment, it further includes:

[0091] The front-end management page performs operations of adding, deleting, and modifying script code through the JavaScript script code update tool;

[0092] The server back-end program loads the updated script code and sends it to the data service program;

[0093] The data service program returns structured data to complete static and dynamic data binding;

[0094] Publish the project to the project and scenario library;

[0095] The project release is completed, and the digital twin development management platform ends.

[0096] In this embodiment, the front-end management page performs operations of adding, deleting, and modifying script code through a JavaScript script code update tool. This process allows developers to directly adjust the front-end logic on the management interface without manually modifying each file. This improves development efficiency and simplifies the maintenance process.

[0097] The updated JavaScript script code is uploaded to the server backend. The server backend program is responsible for loading these new script codes into the data service program to ensure synchronization and consistency between the front-end and the back-end.

[0098] The data service program processes requests according to the updated script code and returns corresponding structured data. This data is then used to complete static and dynamic data binding, where static data is directly loaded from the local cache, and dynamic data is obtained from the server in real time through the data service interface and updated into the twin model. This ensures that the platform can promptly reflect the state changes of physical entities.

[0099] After all necessary updates and validations are completed, the updated project and scene are released to the project scene library. This enables all users or relevant parties to access the latest version and provides support for subsequent applications.

[0100] When all update and release work is successfully completed, the digital twin development management platform ends the current update process. At this time, the system usually notifies relevant personnel that the update is completed and simultaneously records relevant information about this update (such as time, version number, etc.) for future maintenance and tracking.

[0101] Through the above steps, this embodiment not only realizes the efficient update of front-end and back-end codes but also ensures data consistency and real-time performance, enhances the flexibility and response speed of the system, and greatly improves the maintainability and scalability of the digital twin development management platform.

[0102] In one embodiment, the updated asset files include 3D geometric models, geological model data, reservoir model data, seismic data, wellbore data, animation data, model materials, special effects, and plotting.

[0103] In one embodiment, a hot update and hot loading system for a digital twin development management platform is also provided, including:

[0104] A hot update plugin for responding to the platform hot update instruction and parsing the content to be updated and the corresponding hot patch;

[0105] A configuration file update module is used to obtain the latest configuration file from the server backend program. The configuration file contains service addresses, rendering parameters, and data service interfaces. It compares the new configuration file with the local configuration file, identifies the parts that need to be updated, and only updates the changed parts to avoid unnecessary operations on the unchanged parts. After the update is completed, the digital twin development management platform reloads the configuration file to ensure that the new configuration takes effect.

[0106] An asset file update module is used to obtain the MD5 code of the asset file from the server backend program. It compares whether the MD5 code provided by the server backend program is the same as the MD5 code of the local cached file. If they are the same, it means the asset file has not changed, and the local cached file is directly used. Otherwise, it means the asset file has been updated, and a new asset file is downloaded from the asset library and replaces the old asset file in the local cache. After the update is completed, the new asset file is loaded into the digital twin development management platform to ensure that the platform loads the latest asset file and performs rendering.

[0107] An engineering and scenario file update module is used to obtain the MD5 code of the engineering and scenario files from the server backend program. It compares whether the MD5 code provided by the server backend program is the same as the MD5 code of the local cached file. If they are the same, it means the engineering and scenario files have not changed, and the local cached file is directly used. Otherwise, new engineering and scenario files are downloaded from the engineering scenario library and replace the old files in the local cache. After the update is completed, the new engineering and scenario files are loaded into the digital twin development management platform to ensure that the platform loads the latest settings, as well as the engineering and scenarios.

[0108] The specific implementation content of each module can be referred to the above definition of a method for hot update and hot loading of a digital twin development management platform, which will not be elaborated here.

[0109] In one embodiment, a digital twin development management platform is further provided, including:

[0110] A data lake, as a centralized repository for storing raw data, can store a large amount of unstructured, semi-structured, and structured data;

[0111] A data service program, which is an independent service program that runs on the server when the server starts. It is used to obtain unstructured data from the data lake and send back the converted structured static and dynamic data to the twin editor or twin application program.

[0112] A twin editor, a tool for creating, editing, and managing digital twins;

[0113] A digital twin application refers to computer software designed to complete an independent digital twin application. Here, it refers to a software program developed using a twin editor, which is used to receive updated configuration files, asset files, and engineering scenario files and perform loading and rendering operations.

[0114] The server backend program is responsible for handling the logic of the digital twin application, providing storage and management for updating, adding, or deleting interpretation function code, managing the MD5 codes of model assets and engineering scenario files, and managing configuration files.

[0115] The model asset library is used to store model assets.

[0116] The engineering scenario library is used to store engineering and scenario files.

[0117] The local asset cache is a caching mechanism for static resources stored on the user device, which is used to store configuration files, model asset files, and engineering scenario files.

[0118] The technical features of the above embodiments can be combined arbitrarily. For the sake of brevity of description, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, it should be considered as the scope recorded in this specification.

Claims

1. A method for hot update and hot loading of a digital twin development management platform, characterized in that, Including: In response to the platform hot update instruction, analyze the content to be updated and the corresponding hot patch; Update the platform configuration file, including: obtain the latest configuration file from the server backend program, where the configuration file contains service addresses, rendering parameters, and data service interface addresses; compare the new configuration file with the local configuration file to identify the parts that need to be updated, and only update the changed parts to avoid unnecessary operations on the unchanged parts; after the update is completed, the digital twin development management platform reloads the configuration file to ensure that the new configuration takes effect; Update the platform asset file, including: obtain the MD5 code of the asset file from the server backend program, and compare whether the MD5 code provided by the server backend program is the same as the MD5 code of the local cached file. If they are the same, it means that the asset file has not changed, and directly use the local cached file; otherwise, it means that the asset file has been updated, download the new asset file from the asset library, and replace the old asset file in the local cache; after the update is completed, load the new asset file into the digital twin development management platform to ensure that the platform loads the latest asset file and performs rendering; Update the project and scene files, including: obtain the MD5 code of the project and scene files from the server backend program, and compare whether the MD5 code provided by the server backend program is the same as the MD5 code of the local cached file. If they are the same, it means that the project and scene files have not changed, and directly use the local cached file; otherwise, download the new project and scene files from the project scene library, and replace the old files in the local cache; after the update is completed, load the new project and scene files into the digital twin development management platform to ensure that the platform loads the latest settings as well as the project and scene.

2. The hot update and hot loading method of the digital twin development management platform according to claim 1, characterized in that, After the asset file is updated and before the project and scene files are updated, it also includes the update of the unstructured data interpretation code: Obtain the latest unstructured data interpretation code from the server backend program. The unstructured data interpretation code is used to process the parsing and conversion of real-time data, generate a hot patch using a bytecode operation tool, and dynamically update the interpretation code without restarting the platform; the updated interpretation code will take effect immediately to ensure that the platform can correctly process the new data format and logic.

3. The hot update and hot loading method for the digital twin development management platform according to claim 1, characterized in that After the project and scene files are updated, it also includes static and dynamic data binding: Rebind the static and dynamic data according to the updated configuration file and asset file; among them, the static data is directly loaded from the local cache; the dynamic data is obtained from the server backend program through the data service interface and is updated in real time to the twin model.

4. The hot update and hot loading method of the digital twin development management platform according to claim 1, characterized in that, It also includes: After the digital twin development management platform completes all updates, the digital twin development management platform publishes the updated project and scene to the project scene library; Automatically run a series of verification tests to ensure that the updated project and scene can run normally without introducing new problems; If the test passes, prompt the user that the update is completed; If the test finds problems, roll back to the state before the update, record the error information, and notify the developer to fix it.

5. The hot update and hot loading method of the digital twin development management platform according to claim 1, characterized in that, It also includes: After the hot update is completed, automatically clean up the old files that are no longer used in the local cache to free up storage space.

6. The hot update and hot loading method for the digital twin development management platform according to claim 1, characterized in that Before starting the hot update, it also includes: backing up the configuration files, asset files, projects, and scene files of the current platform to ensure data security during the update process.

7. The hot update and hot loading method of the digital twin development management platform according to claim 1, characterized in that It also includes: The front-end management page performs addition, deletion, and modification operations on the script code through the JavaScript script code update tool; The server back-end program loads the updated script code into the data service program; The data service program returns structured data to complete static and dynamic data binding; Publish the project to the project and scene library; After completing the project release, the digital twin development management platform ends.

8. The hot update and hot loading method of the digital twin development management platform according to claim 1, characterized in that, The updated asset files include 3D geometric models, geological model data, reservoir model data, seismic data, wellbore data, animation data, model materials, special effects, and plotting.

9. A hot update and hot loading system for a digital twin development management platform, characterized in that, It includes: The hot update plugin is used to respond to the platform hot update instruction, parse the content to be updated and the corresponding hot patch; The configuration file update module is used to obtain the latest configuration file from the server back-end program. The configuration file contains service addresses, rendering parameters, and data service interfaces; compare the new configuration file with the local configuration file to identify the parts that need to be updated, and only update the changed parts to avoid unnecessary operations on the unchanged parts; After the update is completed, the digital twin development management platform reloads the configuration file to ensure that the new configuration takes effect; The asset file update module is used to obtain the MD5 code of the asset file from the server back-end program, and compare whether the MD5 code provided by the server back-end program is the same as the MD5 code of the local cache file. If they are the same, it means that the asset file has not changed, and the local cache file is directly used; otherwise, it means that the asset file has been updated, and the new asset file is downloaded from the asset library and replaces the old asset file in the local cache; After the update is completed, the new asset file is loaded into the digital twin development management platform to ensure that the platform loads the latest asset file and performs rendering; The project and scene file update module is used to obtain the MD5 code of the project and scene files from the server back-end program, and compare whether the MD5 code provided by the server back-end program is the same as the MD5 code of the local cache file. If they are the same, it means that the project and scene files have not changed, and the local cache file is directly used; otherwise, the new project and scene files are downloaded from the project scene library and replace the old files in the local cache; After the update is completed, the new project and scene files are loaded into the digital twin development management platform to ensure that the platform loads the latest settings and projects and scenes.

10. A digital twin development management platform, characterized in that It includes: The data lake, as a centralized repository for storing raw data, can store a large amount of unstructured, semi-structured, and structured data; The data service program runs on the server and is used to obtain unstructured data from the data lake, convert it into structured static and dynamic data, and send it back to the twin editor or twin application; The twin editor is a tool for creating, editing, and managing digital twins; The digital twin application runs in the cloud and is used to receive the updated configuration files, asset files, and project scene files and perform loading and rendering operations; The server backend program is responsible for handling the logic of the digital twin application, managing the update, addition, or deletion of the interpreted function code, storing it, managing the MD5 codes of model assets and engineering scenario files, and managing configuration files; The model asset library is used to store model assets; The engineering scenario library is used to store engineering and scenario files; The local asset cache is a caching mechanism for static resources stored on the user device, used to store configuration files, model asset files, and engineering scenario files.

Images