Three-dimensional model visual management method and system, medium and product

Abstract

The embodiment of the invention provides a three-dimensional model visual management method and system, a medium and a product, and relates to the technical field of three-dimensional model management. The method comprises the following steps: performing lightweight processing on an original three-dimensional model to generate a lightweight model file, storing the lightweight model file to a product data management system, and associating a product graph number, a version number and an update timestamp; the product drawing number and the version number form a unique identifier of the model; triggering a visual tool to start through a product data management system, and obtaining an initialization parameter containing a unique identifier, a viewing scene and token information corresponding to a user; determining a model loading strategy of the visualization tool according to the initialization parameters; after the model loading strategy is executed, the visual tool inquires and displays scene matching data from the product data management system, and meanwhile, the background asynchronously executes heartbeat monitoring; heartbeat monitoring is used for maintaining token effectiveness and operation safety. According to the scheme, the problem that efficient management and application of the product-level three-dimensional model cannot be supported in the prior art is solved.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of three-dimensional model management, in particular to a three-dimensional model visualization management method, system, medium and product. BACKGROUND

[0002] At present, although there are many tools on the market that can view three-dimensional models and lightweight files, and there are also software such as Unity3D that support the development of customized visualization viewing tools, which can realize customized model visualization feature display and business data analysis viewing, but the existing technical solutions still have many deficiencies and cannot meet the application requirements of product-level digital twin models.

[0003] Firstly, the functions of the existing model visualization viewing tools are mostly focused on the basic operations and visualization features of three-dimensional models, such as rotation, cutting, zooming in, zooming out, selecting, disassembling, panning, labeling, etc. These functions have become the basic configurations for viewing three-dimensional models, and the industry has also optimized and iterated around these functions. For the viewing of product supporting basic information, the existing tools can only call the pre-set contents in the model file (such as figure number, version, name, etc.), and if new attributes need to be added, the three-dimensional model file must be edited and modified. Even if some tools support batch adding attributes, they can only reduce the amount of manual operation, but cannot avoid direct modification of the model file, which makes it difficult to ensure information accuracy and can only add the same information according to strict classification, which brings great difficulty to the unified management of model files. At the same time, the existing tools generally ignore the business data statistics, viewing and analysis requirements based on the model, and do not handle the coupling of three-dimensional model features and basic information well, resulting in the need for a large amount of additional work for basic attribute statistics, addition and application.

[0004] Secondly, for the visualization viewing of product-level large models, the existing technology has very high requirements for the running environment, and even cannot load. For example, when the product overall model data volume reaches 60G or more and the assembly supporting nodes exceed 50,000, ordinary devices cannot support normal loading and viewing of the model. To solve the problem of hardware resource consumption caused by three-dimensional model rendering, some technologies use camera perspective display scheme to render only the part of the model visible to the human eye, but this scheme will consume a lot of computation and still have high requirements for device performance. With the increase of user operation frequency, it is easy to cause problems such as lag and distortion; another part of the technology uses cloud desktop or remote server rendering, which reduces the dependence on local device performance, but has strict requirements for network bandwidth and server performance. In the scenario of multiple concurrent access, it often causes problems such as lag and server downtime, which seriously affects the user experience.

[0005] In summary, the prior art is difficult to simultaneously meet the three core demands of product matching basic information query analysis, easy expansion, reducing the requirement of large model viewing on device performance, adapting to user business needs and use habits, and cannot support efficient management and application of product-level digital twin model, and a new technical solution is urgently needed to make up for the above defects. SUMMARY

[0006] At least one embodiment of the present application provides a three-dimensional model visualization management method, system, medium and product, which are used to solve the problem that the prior art cannot simultaneously meet the demands of information query expansion, low performance dependence and adaptation to business needs, and cannot support efficient management and application of product-level three-dimensional model.

[0007] To solve the above technical problems, the present application is implemented as follows:

[0008] In a first aspect, the embodiments of the present application provide a three-dimensional model visualization management method, comprising:

[0009] Performing lightweight processing on the original three-dimensional model to generate a lightweight model file, storing the lightweight model file to a product data management system and associating the lightweight model file with a product drawing number, a version number and an update timestamp; the product drawing number and the version number constitute a unique identifier of the model;

[0010] Triggering a visualization tool to start through the product data management system, and obtaining initialization parameters including the unique identifier, a viewing scene and token information corresponding to a user;

[0011] Determining a model loading strategy of the visualization tool according to the initialization parameters;

[0012] After the model loading strategy is executed, the visualization tool queries and displays scene-based matching data from the product data management system, and simultaneously executes heartbeat monitoring in the background; the heartbeat monitoring is used to maintain token validity and operation safety.

[0013] Optionally, performing lightweight processing on the original three-dimensional model to generate a lightweight model file, storing the lightweight model file to a product data management system and associating the lightweight model file with a product drawing number, a version number and an update timestamp, comprises:

[0014] Traversing a model tree of the original three-dimensional model by using the visualization tool, and exporting a first lightweight file corresponding to the complete model tree based on a preset matching node;

[0015] Depth-first traversing the model tree from top to bottom, finding a hierarchical node of the model tree with a leaf node, and determining whether the hierarchical node is a top node;

[0016] If it is not a top-level node, then obtain the parent node of the node above it, call the preset merge function to merge the child nodes corresponding to the node, and export the merged second lightweight file.

[0017] Both the first lightweight file and the second lightweight file are stored in the product data management system, and are associated with the product drawing number, version number, 3D model update time, lightweight model file update timestamp, assembly relationship, and lightweight inspection time identifier.

[0018] Optionally, the visualization tool can be launched by triggering the product data management system to obtain initialization parameters containing the unique identifier, viewing scenario, and token information corresponding to the user, including:

[0019] Using the product data management system, a startup operation is performed based on the deployment form of the visualization plugin to trigger the startup of the visualization tool; the startup operation includes integrating the visualization plugin into the interface of the product data management system, or starting an independently deployed visualization plugin through system communication and program path management;

[0020] Using the product data management system, parameters containing the unique identifier, viewing scenario, and user-corresponding token information are organized into a structured string and passed to the visualization tool;

[0021] Using the visualization tool, after receiving the string, the tool verifies whether the string is in a structured format, whether it contains the unique identifier, and displays the scene and the token information corresponding to the user.

[0022] After successful verification, the visualization tool uses the string as an input parameter to call the product data management system and obtain initialization parameters containing the unique identifier, viewing scenario, and token information corresponding to the user.

[0023] Optionally, based on the initialization parameters, the model loading strategy of the visualization tool is determined, including:

[0024] The scene type of the scene to be viewed is obtained by parsing the initialization parameters.

[0025] If the scenario type is a product scenario, the loading strategy is determined as follows: display the assembly relationship from the top layer of the product to the supporting nodes, and the supporting nodes are associated with the download address of the preprocessed model file;

[0026] If the scenario type is a supporting scenario, the loading strategy is determined to be: obtain the corresponding lightweight model file based on the unique identifier and complete the rendering;

[0027] Based on the matching nodes displayed in the assembly relationship, when a user selects a target matching node, the loading strategy is determined as follows: After the user selects a target matching node, the visualization tool triggers the download and rendering operation of the target model file associated with the target matching node, parses the downloaded target model file to extract the corresponding model tree, and completes the lower-level structure contained in the model tree into the corresponding node of the total model tree of the visualization tool; wherein, the loading strategy also includes multiple model viewing methods. Under each viewing method, the visualization tool, based on the drawing number and version corresponding to the unique identifier, combined with the model type, scene parameters, and token information, sends a message to the product data management system to obtain the model file download address and executes the corresponding loading operation.

[0028] Optionally, during the model loading process in the same scene, the visualization tool counts the total number of nodes in the current model tree. If the total number of nodes exceeds a preset threshold, a prompt is triggered and the unloading of the temporary model is supported.

[0029] When viewing model files in different scenarios, the newly opened scenario is used to return to the initial operation position via a preset one-click return command.

[0030] Optionally, after the model loading strategy is executed, the visualization tool queries and displays contextualized supporting data from the product data management system, including:

[0031] When a user selects a model tree node or a model, the visualization tool automatically collects target information including the model node assembly path, matching drawing number, matching version, and the scene to be viewed, and converts the target information into a structured format request.

[0032] The structured format request is sent to the product data management system via a preset interface;

[0033] After receiving the data returned by the product data management system, the visualization tool parses and displays the data in form or table format according to the data format type.

[0034] Optionally, after the model loading strategy is executed, the visualization tool asynchronously performs heartbeat monitoring in the background, including:

[0035] During the heartbeat monitoring process, the latest user operation time recorded in the visualization tool is read at preset intervals;

[0036] The latest user operation time is compared with the current time. If the time interval exceeds a preset threshold, the visualization tool will time out and exit.

[0037] If the preset threshold is not exceeded, it is determined whether the latest user operation time has been updated. If it has been updated, the token information is refreshed through the product data management system interface. During the heartbeat monitoring process, the last refresh time of the associated token information is synchronized.

[0038] Secondly, embodiments of this application provide a three-dimensional model visualization management system, including:

[0039] The first processing module is used to perform lightweight processing on the original 3D model, generate a lightweight model file, store it in the product data management system, and associate it with the product drawing number, version number, and update timestamp; the product drawing number and the version number constitute the unique identifier of the model.

[0040] The second processing module is used to trigger the start of the visualization tool through the product data management system and obtain initialization parameters containing the unique identifier, the viewing scene, and the token information corresponding to the user.

[0041] The third processing module is used to, based on the initialization parameters, if it is determined that the visualization tool has loaded a model, directly load and render the corresponding lightweight model file according to the unique identifier; if it is determined that the visualization tool has not loaded a model, display the product structure tree in the product data management system, and render it after being triggered by the user.

[0042] The fourth processing module is used to, after the model loading strategy is executed, have the visualization tool query and display the scenario-specific supporting data from the product data management system, while simultaneously performing heartbeat monitoring asynchronously in the background; the heartbeat monitoring is used to maintain token validity and operational security.

[0043] Thirdly, embodiments of this application provide a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the steps of the method as described in any one of the first aspects.

[0044] Fourthly, embodiments of this application provide a computer program product, including computer instructions, which, when executed by a processor, implement the steps of the method as described in any one of the first aspects.

[0045] Compared with existing technologies, the 3D model visualization management method, system, medium, and product provided in this application have the following advantages: First, by lightweighting the original 3D model to generate lightweight files, the performance requirements for viewing large models are directly reduced. Second, a unique identifier for the model is constructed using the product drawing number and version number, which is then associated and stored in the product data management system. Combined with visualization tools, the model is loaded according to scenario-based initialization parameters, and supporting data query and display is achieved, adapting to business needs and usage habits and supporting efficient query and analysis. Third, operational security is maintained through token information and asynchronous heartbeat monitoring, and the modular storage and loading architecture is easily scalable, thereby supporting product-level digital twin model management. Attached Figure Description

[0046] Various other advantages and benefits will become apparent to those skilled in the art upon reading the following detailed description of preferred embodiments. The accompanying drawings are for illustrative purposes only and are not intended to limit the scope of this application. Furthermore, the same reference numerals denote the same parts throughout the drawings. In the drawings:

[0047] Figure 1 A flowchart illustrating the three-dimensional model visualization management method provided in this application embodiment;

[0048] Figure 2 A schematic diagram illustrating the interaction logic between the product data management system and the visualization tool provided in this application embodiment;

[0049] Figure 3 The process for merging model trees and exporting corresponding model files is provided in the embodiments of this application;

[0050] Figure 4 This is one of the schematic diagrams of the model tree nodes provided in the embodiments of this application;

[0051] Figure 5 This is one of the schematic diagrams of the model tree nodes provided in the embodiments of this application;

[0052] Figure 6 This is a schematic diagram of the visual startup process provided in the embodiments of this application;

[0053] Figure 7 This is a schematic diagram of the structure of the three-dimensional model visualization management device provided in the embodiments of this application. Detailed Implementation

[0054] The terms "first," "second," etc., used in this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such terms can be used interchangeably where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same class, without limiting the number of objects; for example, the first object can be one or more. Furthermore, "or" in this application indicates at least one of the connected objects. For example, "A or B" covers three scenarios: Scenario 1: including A but not B; Scenario 2: including B but not A; Scenario 3: including both A and B. The character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0055] The term "instruction" in this application can be either a direct instruction (or explicit instruction) or an indirect instruction (or implicit instruction). A direct instruction can be understood as one in which the sender explicitly informs the receiver of specific information, the operation to be performed, or the requested result, etc.; an indirect instruction can be understood as one in which the receiver determines the corresponding information based on the instruction sent by the sender, or makes a judgment and determines the operation to be performed or the requested result, etc., based on the judgment result.

[0056] To enable those skilled in the art to better understand the embodiments of this application, the following description is provided first:

[0057] With the deep penetration of digital twin technology into industrial manufacturing, enterprises' management needs for the entire product lifecycle—from design and development, production, after-sales maintenance, and disposal—have gradually shifted from traditional data-driven lifecycle management to lifecycle management based on digital twins. Digital twins can more intuitively map the product's entire lifecycle state, and simulation manufacturing based on digital twins has become one of the mainstream manufacturing models of the future, providing core support for enterprises to achieve efficient control and optimization. A digital twin is the process and method of accurately describing and modeling the characteristics, behaviors, and performance of a physical entity using digital technology. As its practical application expands across different industries, digital twins need differentiated management according to different stages, such as theoretical state twins and production stage twins. Theoretical state twins can be directly displayed through theoretical 3D models; while the traditional method for generating production stage twins often involves scanning the already manufactured product and then obtaining it through reverse modeling. While this method makes the twin closer to the physical object, it consumes significant human and material resources. Therefore, the solution of generating digital twins by combining theoretical models with actual production information is gradually becoming an industry consensus.

[0058] However, there is a fundamental difference in the core purpose of digital twin models and 3D design models: digital twin models focus more on the overall product display and viewing, as well as full lifecycle management and maintenance, requiring relevant personnel to intuitively control the product; while 3D design models contain a large amount of design process information, with a massive data volume, and loading and viewing require high-performance equipment, severely restricting the promotion and management of digital twin models. Furthermore, merely achieving the visualization of a 3D model is far from realizing the practical application value of a digital twin. A digital twin must also simultaneously display all supporting basic information and actual production information of the product to achieve true twinning. To fully realize the application value of digital twins, the industry generally believes that it is necessary to start with the product's 3D model, removing non-critical information through lightweight processing, reconstructing the model tree, adding search information, establishing connections with business systems, and simultaneously developing dedicated visualization tools to achieve product-related query and analysis functions.

[0059] As described in the background section, existing technologies primarily focus on the operation of 3D models and the viewing of basic attributes, neglecting the need for statistical viewing and analysis of business data based on the models. Furthermore, the statistical addition and application of basic attributes result in a significant workload, and the coupling between 3D model characteristics and basic information is not properly addressed. Aiming at visual viewing of product-level model files places high demands on the environment, and may even prevent loading and viewing altogether, such as when the overall product model reaches 60GB+ or the assembly and supporting nodes reach 50,000+. Existing technologies cannot simultaneously meet the demands for information query expansion, low performance dependency, and adaptation to business needs, thus failing to support efficient management and application of product-level 3D models. To address at least one of these issues, this application provides a 3D model visualization management method, system, medium, and product that can reduce or avoid the occurrence of the above situations.

[0060] This application provides a method, system, medium, and product for three-dimensional model visualization management. The method and apparatus are based on the same concept, and since the principles by which they solve problems are similar, their implementations can be mutually referenced; repeated details will not be elaborated further.

[0061] Please refer to Figure 1 This application provides a method for visual management of three-dimensional models, including:

[0062] Step 11: Perform lightweight processing on the original 3D model to generate a lightweight model file, store it in the product data management system and associate it with the product drawing number, version number and update timestamp; the product drawing number and the version number constitute the unique identifier of the model.

[0063] It should be noted that 3D model files are a critical output during the product design process. The original 3D model data is large, and direct loading can easily cause device lag. Step 11 first performs lightweight processing on the model to generate a low-consumption, high-efficiency lightweight model file. Then, the file is stored in the Product Data Management System (PDM) and associated with the product drawing number, version number, and update timestamp. The product drawing number and version number constitute a unique identifier, ensuring accurate model traceability and avoiding version confusion; the update timestamp provides a time dimension for full lifecycle management.

[0064] Step 12: Trigger the launch of the visualization tool through the product data management system to obtain initialization parameters containing the unique identifier, viewing scenario, and token information corresponding to the user.

[0065] In step 12, a secure connection link is established, and loading requirements are clarified. The visualization tool is triggered to start through the PDM system to ensure consistency between the tool and the data source; at the same time, initialization parameters are obtained, which contain three types of key information: unique identifier (to locate the target model), viewing scenario (such as design review, production assembly, to clarify business requirements), and user token (to bind user permissions and ensure data security), providing a basis for accurate loading in the future.

[0066] Step 13: Determine the model loading strategy of the visualization tool based on the initialization parameters.

[0067] Here, step 13 involves customized loading, balancing efficiency and requirements. The visualization tool dynamically matches the loading strategy based on the initialization parameters: it locates the model file based on a unique identifier, determines the loading precision by viewing the scene, such as designing high-precision details for scene loading, assembling a simplified core structure for scene loading, verifying user operation permissions through tokens, avoiding resource waste caused by indiscriminate loading, adapting to different business scenarios and device performance, and improving interaction efficiency.

[0068] Step 14: After the model loading strategy is executed, the visualization tool queries and displays the scenario-specific supporting data from the product data management system, while the heartbeat monitoring is executed asynchronously in the background; the heartbeat monitoring is used to maintain the validity of the token and the security of the operation.

[0069] Step 14 of this application adapts to business needs and ensures operational security. After loading, the visualization tool queries the PDM system and displays matching data (such as part parameters and assembly relationships) that match the current scenario, realizing the linkage between the model and data and conforming to the user's business usage habits; at the same time, the background asynchronously executes heartbeat monitoring to verify the validity of the token in real time, preventing illegal operations or session failures, and ensuring the operational security of model data without affecting the front-end interaction.

[0070] Reference Figure 2The diagram illustrates the interaction logic between the product data management system and the visualization tool. The product data management system is a data resource pool responsible for managing supporting basic information, the product BOM (Bill of Material), and model files. Supporting basic information includes drawing number, version (which together constitute the model's unique identifier), name, associated lightweight model files, and additional attributes for different viewing scenarios. The product BOM is used to represent the assembly relationships across different viewing scenarios; key information includes parent drawing number, parent version, drawing number, version, and viewing scenario. These two types of information are linked through drawing number, version, and viewing scenario, forming a relationship system centered on supporting elements and radiating to assembly relationships and model files. Simultaneously, it provides a data access interface, returning corresponding data packages based on the visualization tool's query conditions (viewing scenario, product drawing number, version).

[0071] It should be noted that the supporting information and assembly relationship information can be created directly by the designers in the system, or obtained from the enterprise business system integration.

[0072] Optionally, the visualization tool supports two startup methods: (1) Recommended method: Triggered from the product data management system (select product or accessories), the system automatically outputs the viewing scenario, product drawing number and version corresponding to the trigger module as initialization parameters, and the tool display effect can be flexibly controlled; (2) Alternative method: Directly launch the tool icon, and you need to manually enter the viewing scenario, product drawing number and version to complete the initialization.

[0073] After the visualization tool is launched, it calls the product data management system interface based on the initialization parameters (user token, product image number, version, and viewing scenario). The interface parameters are uniformly parsed by the product data management system. Subsequent changes in business requirements only require adjustments to the system's processing logic, improving the tool's flexibility. After parsing the parameters, the system returns the corresponding data package, which the tool displays in the form of the data package organization. If "Whether to load the model in time" in the data package is "yes", the lightweight model is directly loaded and displayed, supporting interactions such as rotation and selection highlighting. If it is "no", only the product structure tree is displayed, and the model can be selectively loaded by selecting nodes, solving the problems of long loading time and low smoothness of full loading.

[0074] Optionally, the visualization tool supports data querying: it supports automatic querying (selecting a model or structure tree node automatically calls the interface with the node's drawing number, version, and viewing scene as parameters) and active querying (manually entering conditions to trigger the query). The tool automatically displays the data based on the returned data package. After selecting a model node, annotation information can be entered, and combined with the node's drawing number, version, and viewing scene, it is saved to the product data management system via the interface.

[0075] In this application, user tokens are used to manage permissions, and the heartbeat monitoring module of the visualization tool verifies the validity of the tokens in real time: if the user of the business system of the tool is logged out, the tool automatically loses the data viewing permission; if there is no operation for a long time, the login information will automatically expire, thus ensuring data security.

[0076] This application Figure 2 It is a visualization tool developed based on Unity3D. It is divided into modules for lightweight model processing, tool startup, model loading interaction, and supporting data interaction. With heartbeat monitoring, it can realize the integrated and secure viewing and management of product-level models and supporting data.

[0077] Optionally, step 11 above includes:

[0078] Using the visualization tool, traverse the model tree of the original 3D model, and based on the preset matching nodes, export the first lightweight file corresponding to the complete model tree;

[0079] Traverse the model tree from top to bottom depth, find the level node of the model tree with leaf nodes, and determine whether the level node is the top level node.

[0080] If it is not a top-level node, then obtain the parent node of the node above it, call the preset merge function to merge the child nodes corresponding to the node, and export the merged second lightweight file.

[0081] Both the first lightweight file and the second lightweight file are stored in the product data management system, and are associated with the product drawing number, version number, 3D model update time, lightweight model file update timestamp, assembly relationship, and lightweight inspection time identifier.

[0082] In this embodiment, the first lightweight file of the complete model tree is exported: the visualization tool traverses the model tree of the original 3D model, and exports the first lightweight file covering the entire model tree based on the preset matching nodes. This operation not only fully maps the hierarchy and assembly relationship of the original model, but also meets the need for accurate restoration of the product structure in the scenario of viewing the full assembly relationship. The target level node is located by deep traversing the model tree: the model tree is scanned from top to bottom using a deep traversal method, filtering out level nodes containing leaf nodes, and determining whether the level node is the top-level node of the model tree. This operation can accurately locate the node level with merging conditions, avoiding structural loss caused by meaningless merging, and ensuring the integrity of the model's core assembly logic. The second lightweight file is exported by merging child nodes: if the located level node is not the top-level node, its corresponding parent node is obtained upwards, and a preset merging function is called to merge all child nodes under that level node into a unified node. The second lightweight file is exported based on the merged simplified model tree. This operation reduces the redundancy of model nodes, significantly reduces the file size, and effectively solves the problems of long model loading time and operation lag in scenarios of non-full structure viewing. Multi-dimensional linked storage to the product data management system: The first and second lightweight files are stored in the product data management system, and simultaneously linked to the product drawing number, version number (unique model identifier), 3D model update time, lightweight model file update timestamp, assembly relationship, and lightweight inspection time identifier; this operation realizes full lifecycle traceability of lightweight files, and subsequent visualization tools can quickly retrieve the corresponding files according to different viewing scenarios, taking into account both model loading efficiency and full-dimensional manageability.

[0083] In one specific implementation, the product data management system manages 3D models by associating elements such as the product BOM structure, product drawing number and version (which together constitute the model's unique identifier), 3D model update time, and lightweight model file update timestamp. This information is used for the structured management of 3D model files and for rapid identification and conversion in preprocessing programs. (Refer to...) Figure 3 The process shown involves merging model trees and exporting the corresponding model files, including:

[0084] 1. Start the lightweight script and export the first lightweight file. Start the model lightweight script program. The visualization tool traverses the model tree of the original 3D model. Based on the preset matching nodes, export a lightweight file that covers the entire model tree (i.e., the first lightweight file in step 11). Upload this file to the product data management system and associate it with information such as product drawing number, version, and 3D model update time.

[0085] 2. Traverse the model tree and locate the target level node. Traverse the model tree again from top to bottom, searching for level nodes with leaf nodes according to the product structure (e.g., a car is broken down into engine, chassis, etc., down to the smallest design unit of the enterprise plan): The model tree is highly consistent with the product structure tree in the product data management system, and the two are mapped one-to-one through the product drawing number (unique identifier); Leaf node: Referring to the product structure tree, it refers to the level node without a lower-level structure (corresponding to the blue box node in the figure); The level node with leaf node is the parent node of the leaf node (corresponding to the red box node in the figure).

[0086] Reference Figure 4 and Figure 5 The diagram of the model tree nodes shown is as follows: Figure 4 As shown, the product uses a top-down, step-by-step decomposition logic to manage the assembly structure. For example, in the case of an automobile, the first layer is decomposed into four core components (engine, chassis, body, and electrical equipment). The second layer continues to decompose based on these core components, such as the engine being divided into body components, valve train, fuel supply system, lubrication system, cooling system, and ignition system, and so on, until the smallest design unit planned by the enterprise. Depending on the product characteristics and the enterprise's product design plan, there may be different division rules, but ultimately a complete product structure will be generated and saved in the product data management system. This structure is an important dependency for merging model trees. During the product design process, the model tree and the product structure in the product data management system are generally bidirectionally mapped. The model tree can be used to generate / update the product structure in the system, and the product structure can also be used to generate / update the model tree. Of course, the mapping direction also depends on the characteristics of the product and the enterprise. Regardless of how the enterprise designs the product, it has little impact on this application. This application mainly relies on the high consistency between the model tree and the product structure tree in the system.

[0087] like Figure 5 As shown, the model tree is consistent with the hierarchical structure of the product structure tree stored in the system from top to bottom, but there are also some differences. During the design process of the last layer of parts, design process nodes such as surface and extrusion nodes will be generated in the model tree.

[0088] 3. Determine if the hierarchical node is a top-level node. The criteria for determining if the located hierarchical node is a top-level node are: Case 1: The model tree node name matches the top-level product number; Case 2: In cases other than Case 1, the node name is "root". If it is a top-level node, exit the process; if it is not a top-level node, proceed to the child node merging stage.

[0089] Traverse the model tree from top to bottom, numbering it according to the level, such as... Figure 5In this model, root is 0, node 1 is 1, nodes 1.1 and 1.2 are 2, and so on. The rule for determining the last level node is to refer to the product structure stored in the system, from top to bottom until there is no lower-level structure. This level is called a leaf node. The parent of the leaf node is the model tree level node with leaf nodes that needs to be found in this application. The one-to-one mapping relationship between system product structure nodes and model tree nodes uses keywords. In this application, it is recommended to use the matching drawing number. The drawing number can be used as a unique code. Of course, other keywords can be selected for matching and mapping according to the characteristics of the enterprise.

[0090] 4. Merge child nodes and export the second lightweight file. Obtain the parent node of the target level node and call the "mergeByTreeLevel" function to merge child nodes (this function is preferred; the parameters are the selected model tree node array and the target merging level. After merging, the triangles of the lower-level child nodes will be integrated into the upper-level node, and the lower-level nodes will be automatically deleted). After merging: the assembly relationship, product drawing number, and other information of the remaining nodes remain unchanged; the product structure tree does not change with the model tree merging and maintains a complete structure; export the merged lightweight file (i.e., the second lightweight file in step 11), mark it "merge," and upload it to the product data management system, associating it with the product drawing number, version, and lightweight check time identifier (this identifier is used to avoid duplicate checks that have not been updated).

[0091] V. Through the above processing, each component will correspond to two lightweight files: the first lightweight file: a complete model tree structure, adapted for viewing scenarios with full assembly relationships; and the second lightweight file marked "merge": a simplified model tree structure, adapted for scenarios with fast loading. Both types of files are stored in the product data management system, associated with product drawing number, version, assembly relationships, lightweight model file update timestamps, and other elements, providing a data foundation for scenario-based loading of visualization tools.

[0092] It should be noted that the model tree nodes are merged layer by layer upwards, integrating the model feature information of the lower-level nodes into the upper-level nodes; after the merging is completed, the lower-level nodes become invalid nodes and are directly deleted, and the final model tree changes from the state before merging to the simplified state after merging. During the merging process, except for deleting the bottom-level leaf nodes, all other information remains unchanged: (1) Except for the leaf nodes deleted in this merging, the upper-level assembly relationship of the other nodes remains unchanged; (2) The names of the remaining model tree nodes (the mapping keywords with the product structure tree in the product data management system, i.e., the product drawing number) remain unchanged; (3) The product structure tree stored in the product data management system does not change with the model tree merging, maintaining the complete product structure; (4) All model feature information corresponding to the leaf nodes deleted in this merging is integrated into the upper-level nodes, with no information loss, ensuring the integrity of the model; When the node merging function of the visualization tool (such as the PIXYZ tool) performs the merging operation, it will automatically complete the merging of the triangular facets.

[0093] After node merging is complete, the corresponding lightweight model file (i.e., the second lightweight file in step 11) is exported based on the target parent node and marked "merge". Then, the process jumps to the step of "determining whether the current node is a top-level node". Through the above model file processing flow, a single accessory will generate two lightweight files: one is a lightweight file displaying the complete model tree (i.e., the first lightweight file in step 11), and the other is a lightweight file displaying only the next level of structure after the model tree is merged (the second lightweight file). Both types of files need to be uploaded to the product data management system and bound to the corresponding accessory through different associations, providing file data support for visualization tools to view products hierarchically. The accessory data processed by this module includes the following key elements: product drawing number and version (the two constitute the model's unique identifier), name, assembly relationship, 3D model update time, first lightweight model file, second lightweight model file marked "merge", and lightweight check time identifier. The "lightweight check time identifier" improves accessory identification efficiency; for identified accessories that have not been updated, the lightweight check process does not need to be repeated.

[0094] Optionally, step 12 above includes:

[0095] Using the product data management system, a startup operation is performed based on the deployment form of the visualization plugin to trigger the startup of the visualization tool; the startup operation includes integrating the visualization plugin into the interface of the product data management system, or starting an independently deployed visualization plugin through system communication and program path management;

[0096] Using the product data management system, parameters containing the unique identifier, viewing scenario, and user-corresponding token information are organized into a structured string and passed to the visualization tool;

[0097] Using the visualization tool, after receiving the string, the tool verifies whether the string is in a structured format, whether it contains the unique identifier, and displays the scene and the token information corresponding to the user.

[0098] After successful verification, the visualization tool uses the string as an input parameter to call the product data management system and obtain initialization parameters containing the unique identifier, viewing scenario, and token information corresponding to the user.

[0099] In this embodiment, the product data management system performs a startup operation based on the deployment form of the visualization plugin. If the plugin is integrated into the system interface, it is started directly within the interface; if it is deployed independently, it is started through system communication and program path management. This operation can adapt to different deployment scenarios, balancing the integration of the system and the tool, as well as the independence of the tool, and flexibly matching the deployment habits of enterprises. The product data management system organizes the unique identifier (product image number and version number), viewing scenario, and user token information into a structured string and passes it to the visualization tool. This operation unifies the parameter transmission format, avoids parameter fragmentation or format chaos, and ensures that the core information required for initialization is transmitted to the tool completely and orderly. After receiving the string, the visualization tool verifies whether it is in a preset structured format and whether it contains the three core information types: unique identifier, viewing scenario, and user token. This verification operation can filter invalid parameters with incorrect format or missing information, avoiding the failure of subsequent model loading strategy formulation due to parameter problems and ensuring the accuracy of parameter transmission. After the parameter string verification passes, the visualization tool uses the string as an input parameter, calls the interface of the product data management system, and obtains standardized initialization parameters containing the unique identifier, viewing scenario, and user token. This operation not only provides a unified and reliable input basis for the formulation of subsequent model loading strategies, but also improves the flexibility of visualization tools to adapt to changes in business needs by allowing the product data management system to uniformly control the parameter parsing logic.

[0100] Reference Figure 6The visualization startup process is shown. By performing lightweight processing on the 3D model, the data attributes are associated with the product drawing number and version (which constitute the unique identifier of the model) to meet the data source requirements of the visualization tool. The visualization tool supports two startup modes, corresponding to its plugin deployment form: (1) Product data management system triggered startup: The visualization plugin is integrated into the product data management system interface, or the independently deployed plugin is launched through system communication and program path management. This method can automatically pass the unique identifier (product drawing number and version number), viewing scenario, and user token information as initialization parameters to the tool according to different viewing scenarios triggered by the system, and directly enter the corresponding scenario interface for data interaction and viewing; at the same time, it inherits the system login permissions to realize the integrated permission control of the two. This application prefers this method. Although it needs to rely on the product data management system, the system as a data resource pool can weaken the drawbacks. Only the scenario trigger interface needs to be designed, while the second method is reserved for expansion feasibility. (2) Independent startup: Directly click the visualization tool desktop icon to start. It is necessary to manually enter the viewing scenario, product drawing number, version, user login information, etc. This method has a high operation complexity. This application only reserves the expansion interface.

[0101] The product data management system triggers the launch of the visualization tool in two ways: Web-based viewing: The visualization plugin, developed based on Unity3D, is encapsulated into an external frame interface using JS and integrated into the product data management system interface; PC-based viewing: The visualization plugin is packaged into an executable tool, its launch path is managed through the registry, and the product data management system launches the tool and passes parameters via Socket communication.

[0102] This application employs two methods: a web-based interface suitable for viewing small models, and a PC-based interface suitable for viewing both small and large models. The initial startup and interaction parameters remain consistent across both methods, with core elements including: a unique identifier (product drawing number + version number), the viewing scenario (e.g., design / manufacturing / after-sales), whether it is a product, a timeline, and user token information. Through service interaction, the visualization tool will complete the initial display based on the returned data.

[0103] The interaction logic for starting the service is as follows: The product data management system starts the visualization tool via frame embedding or Socket communication. Based on the business scenario of the triggering module, information such as unique identifier, viewing scenario, and user token is organized into a structured JSON string and passed to the visualization tool. Among them, "Whether it is a product", "Viewing scenario", and "User token" are required fields, and the time baseline is the current time by default. This triggering logic is a flexible extension point and can be customized as needed, as long as the required fields are complete.

[0104] After receiving the parameter string, the visualization tool performs the following validations: it checks whether the string is in JSON format; if not, it prompts an error and exits; it checks whether the string contains the required elements "Whether it is a product", "Viewing scenario", and "User token"; if these are missing, it prompts an error and exits.

[0105] After successful validation, the tool does not parse the parameter content; instead, it directly uses the string as input to call the product data management system interface to obtain initialization parameters. This design eliminates the need for the tool to associate triggering logic and query conditions; it only needs to match the parameter format. This avoids tool iterations due to adjustments in data query rules, improving the tool's stability and versatility.

[0106] After parsing the parameters of the product data management system interface, the system enters the corresponding data module based on "Whether it is a product" and "View scenario". "View scenario" determines the business module for data query. "Whether it is a product" determines the returned data format: if it is "product", it needs to return the assembly relationship from the top level of the product to the matching model files, ensuring that the model tree in the tool is a complete product structure; if it is "matching", it returns the corresponding matching model information.

[0107] After receiving the data, the visualization tool renders the interface based on the "View Scene" function and loads the data. If "Is it a product?" is "Matching": the file is cached in the tool according to the model download address, the model is rendered and loaded, and a lower-level assembly structure is created based on the model tree. If "Is it a product?" is "Product": only the product structure tree is built, and the rendering model file is not downloaded.

[0108] This process is fully automated in the background, and users only need to wait for the initialization to complete without manual operation. In product scenarios, the model is not initially loaded, which can reduce local resource consumption, and users can load or unload the model as needed.

[0109] Optionally, step 13 above includes:

[0110] The scene type of the scene to be viewed is obtained by parsing the initialization parameters.

[0111] If the scenario type is a product scenario, the loading strategy is determined as follows: display the assembly relationship from the top layer of the product to the supporting nodes, and the supporting nodes are associated with the download address of the preprocessed model file;

[0112] If the scenario type is a supporting scenario, the loading strategy is determined to be: obtain the corresponding lightweight model file based on the unique identifier and complete the rendering;

[0113] Based on the matching nodes displayed in the assembly relationship, when a user selects a target matching node, the loading strategy is determined as follows: After the user selects a target matching node, the visualization tool triggers the download and rendering operation of the target model file associated with the target matching node, parses the downloaded target model file to extract the corresponding model tree, and completes the lower-level structure contained in the model tree into the corresponding node of the total model tree of the visualization tool; wherein, the loading strategy also includes multiple model viewing methods. Under each viewing method, the visualization tool, based on the drawing number and version corresponding to the unique identifier, combined with the model type, scene parameters, and token information, sends a message to the product data management system to obtain the model file download address and executes the corresponding loading operation.

[0114] In this embodiment, scene type parsing and basic loading strategies determine the initialization parameters of the visualization tool and extract the type of the scene to be viewed. For product-related scenes, the loading strategy displays the complete assembly relationship from the top-level product to the supporting nodes containing model files, with the supporting nodes associated with the download address of the pre-processed lightweight model file. This operation ensures the integrity of the product structure in the model tree of the visualization tool without immediately loading the full model, reducing initial resource consumption. For supporting scenes, the loading strategy uses a unique identifier (product drawing number and version number) as an index to retrieve the corresponding lightweight model file from the product data management system and complete the rendering. This operation enables fast and direct loading of supporting models, adapting to users' needs to focus on viewing a single supporting model.

[0115] The loading strategy after a user selects a target matching node: When a user selects a target matching node in the assembly relationship of a product scenario, the visualization tool automatically triggers the download and rendering of the target model file associated with that node, parses the file to extract the model tree, and completes its substructure to the corresponding nodes in the overall model tree. This operation avoids the resource waste of loading the entire model by loading on demand, while completing the structure tree ensures the coherence of the product structure, balancing loading efficiency and structural integrity.

[0116] The multi-path model viewing loading adaptation strategy supports multiple model viewing methods. For each method, the visualization tool uses a unique identifier based on the corresponding drawing number and version, combined with model type, scene parameters, and user token information, to send a request to the product data management system to obtain the model file download address and execute the loading. This design eliminates the need for the tool to be bound to fixed query logic; it can adapt to different viewing needs simply through parameter matching, improving the tool's versatility and stability.

[0117] Furthermore, during the model loading process in the same scene, the visualization tool counts the total number of nodes in the current model tree. If the total number of nodes exceeds a preset threshold, a prompt is triggered and the unloading of the temporary model is supported.

[0118] When viewing model files in different scenarios, the newly opened scenario is used to return to the initial operation position via a preset one-click return command.

[0119] In this application, the node count exceeding the limit prompt and the uninstallation mechanism are implemented in the same scenario during loading. The visualization tool counts the total number of nodes in the current model tree in real time. If the number exceeds a preset threshold (such as a node limit set according to device performance), a prompt is immediately triggered, and the function to uninstall the temporarily used model is provided. The operation dynamically monitors resource usage to avoid tool lag and crashes caused by too many nodes, ensuring smooth interaction. The uninstallation function allows users to release resources independently, adapting to devices with different performance levels.

[0120] The one-click return feature for cross-scene viewing allows users to directly return to their initial position when switching between different scenes to view models. This simplifies cross-scene interaction, avoids repeated navigation across multiple scenes, and improves ease of use.

[0121] In one specific solution, the model loading interaction function provided in this application covers basic operations such as selection highlighting, rotation, slicing, zooming in, zooming out, centering display, blurring, and hiding, adapting to the general needs of product-type scenarios and supporting scenarios; in response to the technical bottlenecks of product-level models, such as the large model tree and the large number of triangles, which lead to loading difficulties, interaction lag, high device performance requirements, and high resource consumption, a scenario-based on-demand loading optimization solution is designed. The core relies on the preprocessing results (triangle merging and non-critical element removal) of the aforementioned lightweight processing module to realize the hierarchical expansion and viewing of the model tree on demand.

[0122] After initialization in product-related scenarios, the visualization tool automatically displays the complete assembly relationship between the top-level product and its supporting nodes containing lightweight model files. Each supporting node is associated with a corresponding model file download address. This model file has undergone preprocessing, including model tree merging (removing redundant lower-level structures while retaining model element characteristics), reducing the number of model tree nodes from the source. Users select supporting nodes for model files to be loaded using the visualization tool. The system automatically triggers model file download and rendering, while simultaneously parsing the file to extract the model tree. If lower-level structures exist, they are added to the corresponding nodes in the overall model tree. This method supports viewing the entire product model while avoiding issues such as lag and inability to open files caused by full loading. This application provides three scenario-based viewing methods, all of which obtain model file download addresses through interaction with the product data management system. Core request parameters include a unique identifier (product drawing number and version number), model type (complete / merged), viewing scenario, and user token information.

[0123] New scene opens: When the user performs the "View Model" operation, the download address of the model file containing the complete model tree is obtained, the new scene rendering is started, and the complete model tree is displayed;

[0124] Current scene open: When the user performs the "View model in current scene" operation, the download address of the merged model file is obtained, and the model tree is rendered, loaded, and completed in the current scene;

[0125] View complete information in the current scene: When the user performs the "View complete model in the current scene" operation, the download address of the model file containing the complete model tree is obtained, and the model tree is rendered, loaded, and completed in the current scene.

[0126] During node overload control and cross-scene switching, when loading within the same scene, the visualization tool counts the total number of nodes in the model tree in real time. When the number of nodes exceeds 5000 (a preset threshold), a prompt is triggered, allowing users to uninstall models they are not currently viewing to free up memory and reduce the number of nodes. When viewing across scenes, newly opened scenes support one-click return to the initial operation position, enabling flexible switching.

[0127] This application's visualization tool supports integration with both client-server (CS) and browser-server (BS) architectures of product data management systems: CS architecture: Starts by calling a local executable program (EXE) with parameters passed in, using the user's login row ID as a token. BS architecture: Starts by sending parameters via Socket communication, directly reusing the token recorded on the web interface. Both architectures use a unified JSON string format for parameters. Except for the token generation and transmission method, all other core parameters (product drawing number, version, model type, scene) remain consistent. The product data management system must provide a RESTful interface service to support model file downloads. Here, a RESTful interface is a web service design specification based on the HTTP standard method. It abstracts system data into "resources" and identifies and manipulates them through URLs, featuring a clear structure and easy extensibility.

[0128] Optionally, after the model loading strategy is executed, the visualization tool queries and displays contextualized supporting data from the product data management system, including:

[0129] When a user selects a model tree node or a model, the visualization tool automatically collects target information including the model node assembly path, matching drawing number, matching version, and the scene to be viewed, and converts the target information into a structured format request.

[0130] The structured format request is sent to the product data management system via a preset interface;

[0131] After receiving the data returned by the product data management system, the visualization tool parses and displays the data in form or table format according to the data format type.

[0132] In this embodiment, when a user selects a model tree node or model entity, the visualization tool automatically collects target information (model node assembly path, matching drawing number, matching version, and viewing scene), converts it into a structured format request, and sends it to the product data management system through a preset interface. After receiving the returned data, the tool parses and displays it in either a form (adapted to single detail data) or a table (adapted to multiple related data) based on the data format type. This operation achieves automated linkage between model selection, data query, and structured display, ensuring that the matching data obtained by the user accurately matches the currently viewed scene and model node. At the same time, the differentiated display of forms or tables makes the data presentation more intuitive and improves the efficiency of business data reading.

[0133] Optionally, after the model loading strategy is executed, the visualization tool asynchronously performs heartbeat monitoring in the background, including:

[0134] During the heartbeat monitoring process, the latest user operation time recorded in the visualization tool is read at preset intervals;

[0135] The latest user operation time is compared with the current time. If the time interval exceeds a preset threshold, the visualization tool will time out and exit.

[0136] If the preset threshold is not exceeded, it is determined whether the latest user operation time has been updated. If it has been updated, the token information is refreshed through the product data management system interface. During the heartbeat monitoring process, the last refresh time of the associated token information is synchronized.

[0137] In this embodiment, after the visualization tool is started, the background asynchronously executes heartbeat monitoring. The core operations and functions are as follows: Timed Time Verification: Every preset time interval (e.g., 30 seconds), the tool reads the latest user operation time recorded in the tool and compares it with the current time. If the time interval exceeds a preset threshold (e.g., 15 minutes), the tool is triggered to time out, avoiding resource consumption and data leakage risks caused by prolonged inactivity. Token Information Maintenance: If the time interval does not exceed the threshold, it checks whether the latest operation time has been updated (i.e., the user has performed a new operation). If updated, the user token information is refreshed through the product data management system interface, and the last refresh time of the token is recorded simultaneously. Real-time verification of user operation status and token validity ensures data access security and avoids tool interruption caused by token expiration during normal operation, achieving a balance between access control and user experience.

[0138] In one specific implementation, in response to the technical shortcomings of traditional technologies that embed supporting attribute information into model file storage, such as cumbersome modification, support only theoretical state data viewing, and high model file storage complexity, this application designs a product supporting data viewing solution based on interface interaction, which enables comprehensive viewing of supporting information in different scenarios, while reducing the pressure on model file storage.

[0139] The aforementioned lightweight processing module simplifies the theoretical attribute information in the 3D model and stores it in a structured form in the product data management system, reducing the complexity of model file storage. When a user selects a model tree node or model entity, the visualization tool automatically collects core query parameters (assembly path of the model tree's matching node, matching drawing number, matching version, and viewing scene), supports expanding extended fields as needed, and sends them to the product data management system as JSON format strings through a preset interface; the interface address is configured through the visualization tool's local configuration file.

[0140] Establish a standardized data interaction protocol, clearly defining mandatory fixed parameters and flexible extended parameters: Mandatory fixed parameters: Model tree node assembly path, corresponding drawing number, and corresponding version (the visualization tool's data acquisition logic is fixed). Scenario parameters: Passed in during the visualization tool's startup phase, responsible only for transmitting to the product data management system; no tool parsing is required. Extended parameters: Carried through the "Extent" field, supporting input at startup and direct parsing by the product data management system, requiring no secondary tool development.

[0141] During data parsing and visualization, the product data management system retrieves information from the corresponding data modules based on scenario parameters and query conditions, and organizes and returns it according to the protocol. The visualization tool automatically parses and displays the returned data based on its format: if the data is organized in JSONObject format (such as BaseInfo type data), it is displayed in form format; if the data is organized in JSON array format (such as categorized data), it is displayed in table format. Nested data categories are supported (such as tabs containing sub-tabs, forms embedding tables), adapting to enterprise-defined data classification needs.

[0142] It should be noted that the heartbeat monitoring module is used to monitor the validity of user login tokens and long periods of inactivity, ensuring data access security. It runs asynchronously in the background after the visualization tool is initialized. During heartbeat monitoring, the visualization tool collects user interaction operations in real time (such as selecting the model tree, rotating the model, and slicing operations), and records the latest operation time as the core basis for monitoring.

[0143] Periodic monitoring and verification: The latest operation time is read at a preset 30-second interval and compared with the current time. If the time interval exceeds the preset no-operation timeout threshold (5 minutes), a login timeout prompt is triggered and the visualization tool is exited. If the timeout has not occurred, it is determined whether the latest operation time has been updated. If it has been updated, the token is refreshed through the user service interface of the product data management system, and the last refresh time of the token is updated synchronously. If it has not been updated, no additional operation is performed.

[0144] It should be noted that heartbeat monitoring mainly includes three times. The operation time is the last user interaction time recorded by the visualization tool, used to determine the tool's activity status; the heartbeat monitoring operation time is the latest operation time recorded by the heartbeat program, used to verify whether a token refresh is needed; and the token's last refresh time is used by the product data management system and the visualization tool to jointly update, ensuring consistency of login status across multiple interfaces.

[0145] In addition to controlling the validity / invalidity of login information, tokens can also be used to obtain user information during data interaction, thereby acquiring the data permissions of the corresponding account in the data management system. These permissions can then be used to control the access permissions of visualization tools to the data, ensuring the consistency of permission control.

[0146] In one specific embodiment, the implementer of this application completes the deployment of a product data management system, processes product data and model files according to the data source requirements of the visualization tool, and simultaneously develops corresponding interactive service interfaces; the visualization tool achieves the following functions: interactive viewing of product-level 3D models (including basic operations and on-demand loading); contextualized viewing of supporting data, including theoretical state data, actual production data, theoretical process data, and other types of information. Ultimately, it achieves integrated viewing and management of the entire lifecycle of structured product data and digital twins, verifying the feasibility and adaptability of the technical solution of this application.

[0147] In summary, the solution presented in this application, combined with a product data management system, achieves lightweighting of product-level 3D models, model tree merging, and exports multiple versions of model files for storage within the system. The system is modified to embed a visualization tool, which is initiated and initialized by the system control tool. A universal data interaction protocol is defined to enable multi-scenario viewing of supporting data, reducing tool compatibility risks. Regarding the model tree merging process, the visualization tool loads / unloads model files as needed, level by level according to the product structure tree, reducing the number of nodes and adapting to local device performance. Developing tools based on the above two points without permission constitutes infringement.

[0148] Compared to existing technologies, this application, in conjunction with business systems and relying on visualization tools (PIXYZ) and 3D development tools (such as Unity3D), achieves functions such as lightweight modeling and embedded tool initialization, reducing the performance requirements for viewing product-level models and ensuring smooth interaction. It also enables integrated viewing of multi-scene attribute data and heartbeat monitoring to ensure data security. Models are loaded or unloaded on demand, avoiding memory overflow and interaction lag issues caused by large product-level model trees, reducing device configuration requirements and resource consumption, and ensuring smooth model interaction.

[0149] The various methods of the embodiments of this application have been described above. Apparatus for implementing the above methods will now be provided.

[0150] Please refer to Figure 7 This application also provides a 3D model visualization management system, including:

[0151] The first processing module 71 is used to perform lightweight processing on the original 3D model, generate a lightweight model file, store it in the product data management system, and associate it with the product drawing number, version number, and update timestamp; the product drawing number and the version number constitute the unique identifier of the model.

[0152] The second processing module 72 is used to trigger the start of the visualization tool through the product data management system and obtain initialization parameters containing the unique identifier, the viewing scene, and the token information corresponding to the user.

[0153] The third processing module 73 is used to, based on the initialization parameters, if it is determined that the visualization tool has loaded a model, directly load the corresponding lightweight model file and render it according to the unique identifier; if it is determined that the visualization tool has not loaded a model, display the product structure tree in the product data management system and render it after being triggered by the user.

[0154] The fourth processing module 74 is used to, after the model loading strategy is executed, have the visualization tool query and display the scenario-based supporting data from the product data management system, while simultaneously performing heartbeat monitoring asynchronously in the background; the heartbeat monitoring is used to maintain the validity of the token and operational security.

[0155] Optionally, the first processing module 71 described above is specifically used for:

[0156] Using the visualization tool, traverse the model tree of the original 3D model, and based on the preset matching nodes, export the first lightweight file corresponding to the complete model tree;

[0157] Traverse the model tree from top to bottom depth, find the level node of the model tree with leaf nodes, and determine whether the level node is the top level node.

[0158] If it is not a top-level node, then obtain the parent node of the node above it, call the preset merge function to merge the child nodes corresponding to the node, and export the merged second lightweight file.

[0159] Both the first lightweight file and the second lightweight file are stored in the product data management system, and are associated with the product drawing number, version number, 3D model update time, lightweight model file update timestamp, assembly relationship, and lightweight inspection time identifier.

[0160] Optionally, the second processing module 72 described above is specifically used for:

[0161] Using the product data management system, a startup operation is performed based on the deployment form of the visualization plugin to trigger the startup of the visualization tool; the startup operation includes integrating the visualization plugin into the interface of the product data management system, or starting an independently deployed visualization plugin through system communication and program path management;

[0162] Using the product data management system, parameters containing the unique identifier, viewing scenario, and user-corresponding token information are organized into a structured string and passed to the visualization tool;

[0163] Using the visualization tool, after receiving the string, the tool verifies whether the string is in a structured format, whether it contains the unique identifier, and displays the scene and the token information corresponding to the user.

[0164] After successful verification, the visualization tool uses the string as an input parameter to call the product data management system and obtain initialization parameters containing the unique identifier, viewing scenario, and token information corresponding to the user.

[0165] Optionally, the aforementioned third processing module 73 is specifically used for:

[0166] The scene type of the scene to be viewed is obtained by parsing the initialization parameters.

[0167] If the scenario type is a product scenario, the loading strategy is determined as follows: display the assembly relationship from the top layer of the product to the supporting nodes, and the supporting nodes are associated with the download address of the preprocessed model file;

[0168] If the scenario type is a supporting scenario, the loading strategy is determined to be: obtain the corresponding lightweight model file based on the unique identifier and complete the rendering;

[0169] Based on the matching nodes displayed in the assembly relationship, when a user selects a target matching node, the loading strategy is determined as follows: After the user selects a target matching node, the visualization tool triggers the download and rendering operation of the target model file associated with the target matching node, parses the downloaded target model file to extract the corresponding model tree, and completes the lower-level structure contained in the model tree into the corresponding node of the total model tree of the visualization tool; wherein, the loading strategy also includes multiple model viewing methods. Under each viewing method, the visualization tool, based on the drawing number and version corresponding to the unique identifier, combined with the model type, scene parameters, and token information, sends a message to the product data management system to obtain the model file download address and executes the corresponding loading operation.

[0170] Optionally, during the model loading process in the same scene, the visualization tool counts the total number of nodes in the current model tree. If the total number of nodes exceeds a preset threshold, a prompt is triggered and the unloading of the temporary model is supported.

[0171] When viewing model files in different scenarios, the newly opened scenario is used to return to the initial operation position via a preset one-click return command.

[0172] Optionally, the fourth processing module 74 mentioned above is specifically used for:

[0173] When a user selects a model tree node or a model, the visualization tool automatically collects target information including the model node assembly path, matching drawing number, matching version, and the scene to be viewed, and converts the target information into a structured format request.

[0174] The structured format request is sent to the product data management system via a preset interface;

[0175] After receiving the data returned by the product data management system, the visualization tool parses and displays the data in form or table format according to the data format type.

[0176] Optionally, the fourth processing module 74 described above is also specifically used for:

[0177] During the heartbeat monitoring process, the latest user operation time recorded in the visualization tool is read at preset intervals;

[0178] The latest user operation time is compared with the current time. If the time interval exceeds a preset threshold, the visualization tool will time out and exit.

[0179] If the preset threshold is not exceeded, it is determined whether the latest user operation time has been updated. If it has been updated, the token information is refreshed through the product data management system interface. During the heartbeat monitoring process, the last refresh time of the associated token information is synchronized.

[0180] It should be noted that the device in this embodiment corresponds to the method described above, and the implementation methods in each of the above embodiments are applicable to the embodiments of this device, achieving the same technical effect. The device provided in this application embodiment can implement all the method steps implemented in the above method embodiments and achieve the same technical effect. Therefore, the parts and beneficial effects that are the same as those in the method embodiments will not be described in detail here.

[0181] This application also provides a computer-readable storage medium storing a computer program. When executed by a processor, the computer program implements the various processes of the above-described 3D model visualization management embodiments and achieves the same technical effects. To avoid repetition, it will not be described again here. The computer-readable storage medium may be a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0182] This application also provides a computer program product, including computer instructions. When the computer instructions are executed by a processor, they implement the various processes of the above-described three-dimensional model visualization management embodiments and achieve the same technical effects. To avoid repetition, they will not be described again here.

[0183] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element.

[0184] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. The computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal (which may be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0185] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other forms under the guidance of this application without departing from the spirit and scope of the claims, and all of these forms are within the protection scope of this application.

Claims

1. A method for visual management of three-dimensional models, characterized in that, include: The original 3D model is subjected to lightweight processing to generate a lightweight model file, which is then stored in the product data management system and associated with the product drawing number, version number, and update timestamp. The product drawing number and the version number constitute a unique identifier for the model; The visualization tool is launched by triggering the product data management system to obtain initialization parameters containing the unique identifier, the viewing scenario, and the token information corresponding to the user. Based on the initialization parameters, determine the model loading strategy of the visualization tool; After the model loading strategy is executed, the visualization tool queries and displays the scenario-specific supporting data from the product data management system, while the heartbeat monitoring is executed asynchronously in the background; the heartbeat monitoring is used to maintain the validity of the token and the security of the operation.

2. The method according to claim 1, characterized in that, The original 3D model undergoes lightweight processing to generate a lightweight model file, which is then stored in the product data management system and associated with the product drawing number, version number, and update timestamp, including: Using the visualization tool, traverse the model tree of the original 3D model, and based on the preset matching nodes, export the first lightweight file corresponding to the complete model tree; Traverse the model tree from top to bottom depth, find the level node of the model tree with leaf nodes, and determine whether the level node is the top level node. If it is not a top-level node, then obtain the parent node of the node above it, call the preset merge function to merge the child nodes corresponding to the node, and export the merged second lightweight file. Both the first lightweight file and the second lightweight file are stored in the product data management system, and are associated with the product drawing number, version number, 3D model update time, lightweight model file update timestamp, assembly relationship, and lightweight inspection time identifier.

3. The method according to claim 1, characterized in that, The visualization tool is launched by triggering the product data management system, and initialization parameters containing the unique identifier, viewing scenario, and user-corresponding token information are obtained, including: Using the product data management system, a startup operation is performed based on the deployment form of the visualization plugin to trigger the startup of the visualization tool; the startup operation includes integrating the visualization plugin into the interface of the product data management system, or starting an independently deployed visualization plugin through system communication and program path management; Using the product data management system, parameters containing the unique identifier, viewing scenario, and user-corresponding token information are organized into a structured string and passed to the visualization tool; Using the visualization tool, after receiving the string, the tool verifies whether the string is in a structured format, whether it contains the unique identifier, and displays the scene and the token information corresponding to the user. After successful verification, the visualization tool uses the string as an input parameter to call the product data management system and obtain initialization parameters containing the unique identifier, viewing scenario, and token information corresponding to the user.

4. The method according to claim 1, characterized in that, Based on the initialization parameters, the model loading strategy of the visualization tool is determined, including: The scene type of the scene to be viewed is obtained by parsing the initialization parameters. If the scenario type is a product scenario, the loading strategy is determined as follows: display the assembly relationship from the top layer of the product to the supporting nodes, and the supporting nodes are associated with the download address of the preprocessed model file; If the scenario type is a supporting scenario, the loading strategy is determined to be: obtain the corresponding lightweight model file based on the unique identifier and complete the rendering; Based on the matching nodes displayed in the assembly relationship, when a user selects a target matching node, the loading strategy is determined as follows: After the user selects a target matching node, the visualization tool triggers the download and rendering operation of the target model file associated with the target matching node, parses the downloaded target model file to extract the corresponding model tree, and completes the lower-level structure contained in the model tree into the corresponding node of the total model tree of the visualization tool; wherein, the loading strategy also includes multiple model viewing methods. Under each viewing method, the visualization tool, based on the drawing number and version corresponding to the unique identifier, combined with the model type, scene parameters, and token information, sends a message to the product data management system to obtain the model file download address and executes the corresponding loading operation.

5. The method according to claim 4, characterized in that, During the model loading process in the same scene, the visualization tool counts the total number of nodes in the current model tree. If the total number of nodes exceeds a preset threshold, a prompt is triggered and the unloading of the temporary model is supported. When viewing model files in different scenarios, the newly opened scenario is used to return to the initial operation position via a preset one-click return command.

6. The method according to claim 1, characterized in that, After the model loading strategy is executed, the visualization tool queries and displays contextualized supporting data from the product data management system, including: When a user selects a model tree node or a model, the visualization tool automatically collects target information including the model node assembly path, matching drawing number, matching version, and the scene to be viewed, and converts the target information into a structured format request. The structured format request is sent to the product data management system via a preset interface; After receiving the data returned by the product data management system, the visualization tool parses and displays the data in form or table format according to the data format type.

7. The method according to claim 1, characterized in that, After the model loading strategy is executed, the visualization tool asynchronously performs heartbeat monitoring in the background, including: During the heartbeat monitoring process, the latest user operation time recorded in the visualization tool is read at preset intervals; The latest user operation time is compared with the current time. If the time interval exceeds a preset threshold, the visualization tool will time out and exit. If the preset threshold is not exceeded, it is determined whether the latest user operation time has been updated. If it has been updated, the token information is refreshed through the product data management system interface. During the heartbeat monitoring process, the last refresh time of the associated token information is synchronized.

8. A three-dimensional model visualization management system, characterized in that, include: The first processing module is used to perform lightweight processing on the original 3D model, generate a lightweight model file, store it in the product data management system, and associate it with the product drawing number, version number, and update timestamp; the product drawing number and the version number constitute the unique identifier of the model. The second processing module is used to trigger the start of the visualization tool through the product data management system and obtain initialization parameters containing the unique identifier, the viewing scene, and the token information corresponding to the user. The third processing module is used to, based on the initialization parameters, if it is determined that the visualization tool has loaded a model, directly load and render the corresponding lightweight model file according to the unique identifier; if it is determined that the visualization tool has not loaded a model, display the product structure tree in the product data management system, and render it after being triggered by the user. The fourth processing module is used to, after the model loading strategy is executed, have the visualization tool query and display the scenario-specific supporting data from the product data management system, while simultaneously performing heartbeat monitoring asynchronously in the background; the heartbeat monitoring is used to maintain token validity and operational security.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, implements the steps of the method as described in any one of claims 1 to 7.

10. A computer program product, characterized in that, Includes computer instructions that, when executed by a processor, implement the steps of the method as described in any one of claims 1 to 7.

Images