A BIM-based lightweight model data penetration and interaction method
By establishing a dynamic bidirectional data link between the lightweight BIM model and the engineering data package, and monitoring and prioritizing resource scheduling in real time, the problem of the separation between the lightweight model and the engineering data is solved, achieving efficient and intelligent data synchronization and interaction, and improving user experience and operational efficiency.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- ZHEJIANG HUANYU CONSTR GRP CO LTD
- Filing Date
- 2026-02-25
- Publication Date
- 2026-06-05
AI Technical Summary
In existing technologies, lightweight BIM models are separated from full-dimensional engineering data, resulting in low data synchronization efficiency in dynamic and concurrent environments and delays in interactive response caused by resource conflicts.
By establishing a dynamic bidirectional data link between the lightweight model and the structured extracted discrete engineering data package, the model state changes and data operation requests are monitored in real time, the data synchronization degree is calculated, and incremental data synchronization is decided based on this, and resources are prioritized to achieve efficient interaction.
It achieves deep integration and intelligent synchronization of models and engineering data, optimizes network bandwidth and server resource utilization, improves the smoothness and immediacy of human-computer interaction, solves the problems of information fragmentation and lag, and improves user experience and operational efficiency.
Smart Images

Figure CN122152834A_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of building information modeling (BIM) data processing technology, and in particular to a lightweight model data integration and interaction method based on BIM. Background Technology
[0002] Building Information Modeling (BIM) technology has become a core digital tool in the modern engineering and construction industry. It integrates engineering data throughout the entire lifecycle of design, construction, and operation through semantically rich 3D models. As project scale and complexity increase, the original BIM models are enormous, containing millions of geometric primitives and massive amounts of attribute data, making them difficult to load, render, and interact with smoothly in lightweight environments such as personal computers, mobile devices, or web browsers. Therefore, lightweighting the original BIM model has become a necessary prerequisite for its application in scenarios such as collaborative design, construction simulation, and on-site briefings.
[0003] Current mainstream lightweight processing technologies primarily focus on simplifying and compressing geometric data, such as significantly reducing model file size by thinning facets, reducing model precision, and merging similar components. However, this approach often leads to a critical problem: the large amount of multi-dimensional engineering data (such as cost, schedule, materials, and quality inspection information) stripped or simplified to meet visualization performance requirements creates a de facto "data fragmentation" between the lightweight model and the model itself. Lightweight models typically retain only the most basic geometric outlines and a few key attributes, while the vast majority of in-depth, dynamically changing engineering business data remains stored in the backend database or original design files. This fragmentation makes it difficult for users to obtain the associated, complete, and up-to-date engineering background information in real time when operating the lightweight model. The model is reduced to a mere "3D view," and its value as a core carrier of information integration is severely diminished.
[0004] To address the aforementioned data fragmentation issue, existing technologies attempt to re-associate engineering data with lightweight models. Common practices include establishing foreign key relationships between model component identifiers and database records, or performing full or periodic incremental data retrieval during synchronization. However, these methods face significant challenges in dynamic, multi-user real-world project environments. On one hand, model states (such as modifications to component positions and shapes) and backend engineering data (such as status updates and cost changes) may be frequently and asynchronously modified by different roles on different terminals, forming multiple concurrent data change streams. Simple polling or full synchronization mechanisms generate a large amount of unnecessary network transmission, which is inefficient in bandwidth-limited or mobile network environments and is highly prone to causing inconsistencies in information seen by different users due to synchronization delays, leading to decision-making errors. On the other hand, when users interact with the model (such as clicking to query, selecting statistics, and viewing sections), the system needs to handle geometric rendering and backend data retrieval simultaneously. When the model is complex and the data volume is large, system resource competition is intense, often resulting in sluggish interactive responses and interface lag, severely impacting user experience and operational efficiency. Especially in scenarios with multiple concurrent users and large, complex models, how to intelligently allocate limited computing, network, and rendering resources to prioritize the smooth flow of critical data and operations has become a pain point that existing technologies have not been able to solve well.
[0005] Therefore, the field urgently needs a method that can truly achieve efficient and intelligent integration and interaction between lightweight models and full-dimensional engineering data. This method not only needs to establish connections between models and data, but also needs to possess an intelligent decision-making capability that can perceive changing contexts (including model change characteristics, data change patterns, network status, and user operation intentions), thereby dynamically optimizing data synchronization strategies and interactive resource allocation, ensuring data consistency while maximizing the overall system response efficiency and the smoothness of the user experience. Summary of the Invention
[0006] To address the technical problems of the separation between lightweight BIM models and full-dimensional engineering data in existing technologies, as well as the low data synchronization efficiency and sluggish interactive response caused by resource conflicts in dynamic and concurrent environments, this invention provides a method for data integration and interaction of lightweight BIM models.
[0007] The technical solution provided by this invention is as follows: This invention provides a lightweight model data integration and interaction method based on BIM, comprising: S1: Obtain the original BIM model and its associated complete engineering data; S2: The original BIM model is lightweighted to generate a lightweight model containing simplified geometric data and key attribute data, and the complete engineering data is structurally extracted to generate a discrete engineering data package associated with the model components. S3: Establish a dynamic bidirectional data link between the lightweight model and the discrete engineering data package; calculate the current data synchronization degree based on real-time monitoring of model state changes and data operation requests; and make decisions and execute incremental data synchronization based on the data synchronization degree. S4: In response to the result of the incremental data synchronization, drive the geometric state and attribute information of the lightweight model to be matched and updated; S5: Receive user interaction operations on the updated lightweight model at the visualization end, determine the interaction response priority of the interaction operation in real time, and schedule and allocate system resources according to the priority to generate and feed back the corresponding interaction response results.
[0008] The beneficial effects of the technical solution provided by this invention include at least the following: (1) In this invention, a dynamic bidirectional data link is established between the lightweight model and the structured, extracted discrete engineering data packets. Furthermore, a data synchronization index calculated based on multi-dimensional real-time factors (including the complexity of model geometric differences, the temporal concentration of data changes, and current network performance) is innovatively introduced, achieving deep integration and intelligent synchronization between the model and engineering data. This mechanism completely changes the traditional loosely correlated or simply polled synchronization mode between the lightweight model and background data. The system can accurately perceive the "quality" and "quantity" of changes, triggering incremental data synchronization only when necessary and with the optimal priority. This fundamentally ensures that the user's observed geometric state and attribute information are always consistent with the latest engineering data source when operating the lightweight model, solving the problems of information fragmentation and lag, and making the lightweight model a reliable, real-time, and information-complete decision support carrier once again.
[0009] (2) In this invention, a hierarchical decision threshold is set based on the calculated data synchronization degree to guide the execution strategy of incremental synchronization. The system can automatically distinguish between urgent changes and ordinary updates, immediately initiate synchronization for high-urgency changes, perform queued batch transmission for general changes, and only log changes for low-urgency changes. This differentiated synchronization strategy greatly optimizes the utilization efficiency of network bandwidth and server resources. It avoids the resource waste caused by traditional full synchronization or high-frequency polling, and also reduces the crowding of communication channels by low-value data. Especially in scenarios with poor network conditions or concurrent modifications by multiple users, this mechanism can effectively ensure the timely delivery of critical data changes, maintain the stability and overall throughput performance of the system under complex working conditions, and solve the resource conflict and efficiency bottleneck problems caused by rigid synchronization strategies.
[0010] (3) In this invention, by determining the priority of the interaction response in real time during the user interaction phase, and dynamically scheduling and allocating computing, rendering, and network resources based on this priority, the smoothness and immediacy of human-computer interaction are significantly improved. The priority determination comprehensively considers the operation type, the complexity of the model in the area of effect, and the user's historical operating habits, enabling the system to intelligently identify the operation that most needs rapid feedback (such as fine-grained querying of the view focus area). High-priority operations can obtain sufficient resource guarantees to receive immediate responses, while low-priority operations are rationally scheduled to avoid blocking. This intelligent resource scheduling mechanism ensures that even when operating ultra-large, highly complex lightweight models, the user's core interactive intent can receive rapid and accurate visual and data feedback, effectively eliminating interface lag and operational delays, thereby greatly improving the user's operating experience and work efficiency in data-intensive BIM applications. Attached Figure Description
[0011] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.
[0012] Figure 1 This is a flowchart illustrating a lightweight model data integration and interaction method based on BIM, provided in an embodiment of the present invention. Detailed Implementation
[0013] The technical solution of the present invention will now be described with reference to the accompanying drawings.
[0014] In embodiments of the present invention, words such as "exemplarily," "for example," etc., are used to indicate that something is an example, illustration, or description. Any embodiment or design described as "exemplary" in the present invention should not be construed as being more preferred or advantageous than other embodiments or designs. Specifically, the use of the word "exemplary" is intended to present the concept in a concrete manner. Furthermore, in embodiments of the present invention, the meaning expressed by "and / or" can be both, or either one.
[0015] In the embodiments of this invention, the terms "image" and "picture" may sometimes be used interchangeably. It should be noted that, without emphasizing the distinction between them, they convey the same meaning. Similarly, the terms "of," "corresponding (relevant)," and "corresponding" may sometimes be used interchangeably. It should be noted that, without emphasizing the distinction between them, they convey the same meaning.
[0016] In embodiments of the present invention, sometimes the subscript is as follows: It may be a typo for a non-subscript form, such as When the distinction is not emphasized, the meaning they express is the same.
[0017] To make the technical problems, technical solutions and advantages of the present invention clearer, a detailed description will be given below in conjunction with the accompanying drawings and specific embodiments.
[0018] Reference manual attached Figure 1 The diagram illustrates a flowchart of a lightweight model data integration and interaction method based on BIM provided in an embodiment of the present invention.
[0019] This invention provides a method for lightweight model data integration and interaction based on BIM, and the processing flow may include the following steps: S1: Obtain the original BIM model and its associated complete engineering data.
[0020] In practice, the first step is to export the original BIM model files from the various professional design software or platforms involved in the project. These design platforms are typically heterogeneous, so the exported model files must adhere to unified open standards, such as industrial basic standards, to ensure data universality. Simultaneously, comprehensive engineering data associated with the model components needs to be extracted from multiple business systems, including project management systems, material management databases, and construction progress management platforms. This data covers component production information, cost, installation schedule, quality inspection reports, etc., forming a complete set of engineering data deeply bound to the model. This step provides a complete data source for subsequent lightweight processing and data integration.
[0021] S2: Lightweight processing is performed on the original BIM model to generate a lightweight model containing simplified geometric data and key attribute data, and the complete engineering data is extracted in a structured manner to generate discrete engineering data packages associated with the model components.
[0022] In implementing this step, the acquired original BIM model requires both geometric simplification and data reorganization. At the geometric level, by analyzing the model's geometric topology and identifying its engineering semantics, key feature lines and connection points for defining component shapes are extracted. Based on preset simplification rules and accuracy requirements, redundant geometric faces and complex internal structures that do not affect overall recognizability and key engineering information are removed from the model, generating simplified geometric data with smaller storage space and higher rendering efficiency. At the data level, the complete engineering data is structured, non-critical information is removed, core attributes closely related to components are extracted, and the data is reorganized into independent and structured data packages according to component classification and hierarchical relationships. Finally, the simplified geometric data is associated and bound with the corresponding structured data packages, forming an intermediate state where a lightweight model and discrete engineering data packages coexist.
[0023] S3: Establish a dynamic bidirectional data link between the lightweight model and the discrete engineering data package. Based on real-time monitoring of model state changes and data operation requests, calculate the current data synchronization degree, and make decisions and execute incremental data synchronization based on the data synchronization degree.
[0024] In its implementation, this step requires establishing a real-time communication data channel between the lightweight model and the discrete engineering data package. This channel continuously monitors any state changes of the lightweight model on the visualization end, as well as any data operation requests occurring in the background engineering data package. The system uses a built-in evaluation mechanism to calculate the data synchronization degree in real time. This synchronization degree is a comprehensive quantitative indicator that considers the complexity of model changes, the concentration of data changes, and the performance of the current network communication environment. Based on the calculated real-time data synchronization degree, the system automatically determines the optimal data synchronization strategy. The decision logic is hierarchical, choosing to immediately initiate full synchronization, add changes to a queue for orderly batch synchronization, or only log the changes while temporarily suspending network transmission. This process achieves intelligent and on-demand data synchronization.
[0025] S4: In response to the results of incremental data synchronization, drive the matching and updating of the geometric state and attribute information of the lightweight model.
[0026] After the incremental data synchronization in step S3 is completed, this step is responsible for reflecting the synchronization results to the lightweight model in real time. For changes in model geometry, the system does not reload the entire model; instead, it locates the changed local geometric faces, updates them using local redrawing technology, and handles the transition between the old and new geometry with a smooth transition algorithm to ensure a seamless visual experience. For updates to component attribute information, the system clearly indicates the changed data to the user in the visualization interface by dynamically changing component colors, highlighting them, or dynamically popping up attribute labels next to the components. This step ensures that the model's visualization status remains consistent with the backend engineering data, and the update process is efficient and intuitive.
[0027] S5: Receive user interaction operations on the updated lightweight model on the visualization end, determine the interaction response priority in real time, and schedule and allocate system resources according to the priority to generate and feed back the corresponding interaction response results.
[0028] In practical applications, users can perform various interactive operations on the updated lightweight model on the client. Upon receiving an operation command, the system first determines the response priority of the interaction in real time. Priority determination comprehensively considers the type of operation, the complexity of the model involved, and the user's historical operating habits. Based on the calculated priority, the system dynamically schedules and allocates computing resources, network bandwidth, and rendering resources. High-priority operations receive more resources to ensure immediate response, while low-priority operations may be rationally scheduled to optimize overall system performance. Finally, the system uses the allocated resources to generate response data corresponding to the operation, encodes it, and sends it to the client, providing visual feedback in the user interface, thus forming a closed-loop interactive process.
[0029] In one possible implementation, step S3 involves calculating the current data synchronization degree, specifically including: S301: Obtain the model geometric difference feature set since the last complete synchronization. Engineering data change record set ; 302: Geometric feature entropy of computational model differences Dispersion of the operation sequence with data change ; S303: Real-time acquisition of current network channel evaluation parameters, including average latency. With packet loss rate ; S304: Based on geometric feature entropy Operation sequence discreteness Average delay and packet loss rate The data synchronization degree is calculated using the following formula. ; in, , For differences Probability estimate of occurrence; , For change operation timestamp, Average timestamp; The normalized adjustment coefficient satisfies ; Characteristic decay time constant.
[0030] In one specific implementation, the process of calculating the current data synchronization degree in step S3 is precisely completed through the following steps. First, the system retrieves all geometrical differences accumulated by the lightweight model since the last complete data synchronization operation from the internal logs, forming a geometric difference feature set. Simultaneously, it retrieves all operation records executed on discrete engineering data packets within the same time period, forming an engineering data change record set. Next, the system performs quantitative analysis on these two sets, calculating the geometric feature entropy of the model differences to measure the complexity of geometric changes, and calculating the operation sequence dispersion of data changes to measure the temporal concentration of change operations. At the same time, the system obtains the performance evaluation parameters of the current communication channel in real time through the underlying network interface, including the average transmission delay and data packet loss rate. Finally, the system substitutes the calculated geometric feature entropy, operation sequence dispersion, and the real-time acquired network delay and packet loss rate into the data synchronization degree calculation formula, and calculates a quantitative data synchronization degree value that reflects the urgency and efficiency of current real-time synchronization.
[0031] In one possible implementation, step S5, determining the interaction response priority of the interactive operation in real time, specifically includes: S501: Identify the type of interactive operation and map it to the basic type coefficient. ; S502: Analyze the number of detail levels of model components within the interaction region. With the total number of components ; S503: Obtain the average response time of similar historical operations for this user. And the time interval between this operation and the most recent operation on the same view. ; S504: Based on basic type coefficients Detail level hierarchy Total number of components Average response time and time interval The interaction response priority is calculated using the following formula. ; Where e is the natural constant; The time decay factor; A very small positive constant is used to prevent the denominator from being zero.
[0032] In one specific implementation, the process of determining the real-time priority of interactive operation responses in step S5 is achieved through the following steps. First, the system identifies the type of the user's current interactive operation and maps this type to a preset basic type coefficient. Then, the system analyzes the distribution of detail levels of all components within the model space area covered by the interactive operation, counting the number of different detail levels and the total number of components within that area. The system also retrieves the user's historical interaction records, calculates the average system response time for similar operations performed previously, and records the time interval between the current operation and the previous operation within the same view. Finally, the system substitutes the obtained basic type coefficient, number of detail levels, total number of components, historical average response time, and operation time interval into the calculation formula for the interactive response priority to obtain a quantified interactive response priority value, which guides subsequent resource scheduling.
[0033] In one possible implementation, step S2 involves lightweighting the original BIM model, specifically including: S201: Extract the feature contour lines and key connection points of model components through geometric topology analysis and semantic recognition; S202: Based on a preset accuracy threshold, non-feature patches and internal redundant geometric elements are eliminated; S203: Based on component type and engineering attributes, reorganize key attribute data into hierarchical data blocks and bind them to simplified geometric data.
[0034] In one specific implementation, the detailed process of lightweighting the original BIM model in step S2 includes three sequentially executed sub-steps. The first step is feature extraction, which uses computer geometric topology analysis algorithms to process the 3D mesh of the model components, identify their boundaries and connections, and, combined with semantic information from the BIM model, extract feature contour lines that characterize the basic shape of the components and key connection points that identify the connections between components. The second step is redundancy removal, which, based on a preset accuracy threshold, filters all triangular faces in the model, deleting non-feature faces that do not belong to the feature contours, do not affect the shape recognition, and redundant geometric elements that are invisible inside the components or contribute little to the overall expression. The third step is data reorganization, which, based on the engineering type and key attributes of the components, reorganizes the filtered and retained key attribute data from the original loose structure into logically clear hierarchical data blocks, and binds these data blocks to the simplified geometric data obtained in the second step using unique identifiers.
[0035] In one possible implementation, step S3, which involves making a decision and performing incremental data synchronization based on the data synchronization degree, specifically includes: S305: Preset first synchronization threshold With the second synchronization threshold ,in ; S306: If If this happens, a high-priority synchronization thread will be triggered to immediately transmit all the data to be synchronized. S307: Then the data to be synchronized will be added to the queue and transmitted in batches in sequence; S308: If If the data change log is not recorded, network transmission will not be started temporarily, and the process will wait for the next calculation cycle.
[0036] In one specific implementation, step S3, which involves making decisions based on data synchronization and executing incremental synchronization, follows a set of explicit threshold judgment rules. The system internally presets two key data synchronization thresholds: a higher first synchronization threshold and a lower second synchronization threshold. The system compares the real-time calculated data synchronization value with these two thresholds. If the value is greater than or equal to the first threshold, the system determines that the current synchronization need is extremely urgent and immediately triggers a high-priority synchronization thread to transmit all data to be synchronized completely without delay. If the value is between the first and second thresholds, the system determines that the current synchronization need is moderate, packages the data to be synchronized into a transmission queue, and performs asynchronous transmission in batches according to a predetermined order strategy. If the value is less than the second threshold, the system determines that the current synchronization need is very low, temporarily refrains from initiating any network transmission tasks, and only records the details of this data change in a log file, awaiting reassessment in the next system calculation cycle.
[0037] In one possible implementation, step S4 involves matching and updating the geometric state and attribute information of the lightweight model, specifically including: S401: For geometry state updates, a local redrawing algorithm for difference patches and a smooth transition algorithm for adjacent patches are used for rendering. S402: For attribute information updates, highlight them in the visualization interface using dynamic labels and predefined color codes.
[0038] In one specific implementation, the operation of driving the lightweight model to perform matching updates in step S4 is divided into two processing methods depending on the content of the update. For updates to the model's geometry or position caused by data synchronization, the system employs differentiated local rendering technology. The system identifies the local geometric patches that have changed, redraws only these changed patches, and uses a smooth transition algorithm to process the edge areas where the old and new patches meet, in order to eliminate the visual abruptness. For updates to the attribute information associated with components, the system adopts a more prompting interactive method in the visualization interface, displaying the updated attribute values through dynamically attached or pop-up labels, and changing the display color of the relevant components according to a set of predefined color coding rules, thereby intuitively feeding back the data changes to the user.
[0039] In one possible implementation, step S202 involves removing non-feature patches and internal redundant geometric elements based on a preset accuracy threshold, specifically including: S2021: Dynamically adjust the precision threshold of different components based on the default display ratio of the components in the engineering view and the user-defined attention level; S2022: For structural members, priority should be given to preserving their stress characteristic lines and the geometry of the end connection areas; S2023: For equipment and piping components, priority should be given to preserving their center axis, connecting flanges, and valve features.
[0040] In one specific implementation, the elimination process based on accuracy thresholds in step S202 further follows the rules of dynamism and specialization. The system does not apply a uniform accuracy threshold to all components. Instead, it dynamically adjusts the geometric accuracy threshold for different components based on their default display scale in engineering drawings or views, and the user's manually marked level of attention, ensuring that important or prominent components retain more detail. Under this principle, the geometric preservation strategy for different types of engineering components has a professional emphasis. For structural components such as beams, columns, and slabs, the system prioritizes ensuring the integrity of their stress characteristic lines and the geometry of the end areas connecting with other components when eliminating redundancy. For equipment and piping components such as ducts, water pipes, and cable trays, the system prioritizes retaining the central axis expressing their direction, as well as key geometric features such as flanges and valves that identify their connections and functions.
[0041] In one possible implementation, in step S307, batch transmission is performed sequentially, and the specific sorting rule is as follows: S3071: Prioritize the transmission of data to be synchronized that is associated with the current user view focus area; S3072: Next, transmit the data to be synchronized with the most recently modified timestamp; S3073: The last transmitted data packet is less than the preset size.
[0042] In one specific implementation, when adding the data to be synchronized to the queue and transmitting it in batches in step S307, the sorting rules are as follows: First, the queue sorting considers the user's current visual focus, prioritizing the transmission of data associated with model components located in the center or focus area of the user's current view, ensuring that the information within the user's field of vision is up-to-date. Second, based on the first rule, the data is sorted according to its modification timestamp, prioritizing the transmission of the most recently modified data. Finally, for other data to be synchronized, it is sorted according to the size of its data packet, prioritizing the transmission of smaller packets.
[0043] In one possible implementation, step S1 involves acquiring the original BIM model and its associated complete engineering data, specifically including: S101: Export model files conforming to the Industrial Basic Class IFC standard from multiple heterogeneous design platforms; S102: Parse the model file and extract core model information, including geometric entities, attribute sets, and relational networks; S103: Synchronize schedule, cost, bill of materials, and quality inspection report data associated with model components from the project management system database.
[0044] In one specific implementation, step S1, obtaining the original BIM model and its associated complete engineering data, involves the following three sources. First, regarding model data, the system needs to export design results from heterogeneous BIM design platforms used by various disciplines such as architecture, structure, and MEP. To ensure data universality and parsability, these exported model files must conform to the internationally recognized standard format, Industrial Basic Class (ICC). The system then uses the IFC parsing engine to perform deep parsing of the standard format model files, extracting the geometric entity information, attribute set information, and spatial and logical relationship network between entities that constitute the core of the BIM model. Second, regarding engineering data, the system needs to establish a connection with the project management system database, synchronizing and associating various business data related to model components through a data interface, including construction schedules, cost budget information, material procurement lists, and on-site quality inspection reports.
[0045] In one possible implementation, step S5 involves generating and feeding back the corresponding interactive response result, specifically including: S508: Based on interaction response priority The allocated system resources generate a visual data stream with a corresponding level of detail. S509: Encode the visualized data stream and send it to the client requesting interaction; S510: In the client interface, the interactive response results are presented in the form of graphical highlights, data panel pop-ups, or 3D animations.
[0046] In one specific implementation, the terminal process of generating and feeding back the interactive response result in step S5 includes three progressive stages. First, the system dynamically allocates corresponding computing and graphics rendering resources according to the calculated and determined interactive response priority, and generates a set of visualization data streams that match the level of detail allowed by the current resources. Then, the system compresses and encodes this visualization data stream and sends it to the client application that initiated the interaction request via a network transmission protocol. Finally, after receiving and decoding the data stream, the client application presents the final interactive response result in an intuitive form in the user interface. Specific presentation methods include graphically highlighting the component selected by the user, popping up an information panel containing detailed data at a specified location on the screen, or playing a 3D animation showing the component's status.
[0047] The beneficial effects of the technical solutions provided in the embodiments of the present invention include at least the following: (1) In this invention, a dynamic bidirectional data link is established between the lightweight model and the structured, extracted discrete engineering data packets. Furthermore, a data synchronization index calculated based on multi-dimensional real-time factors (including the complexity of model geometric differences, the temporal concentration of data changes, and current network performance) is innovatively introduced, achieving deep integration and intelligent synchronization between the model and engineering data. This mechanism completely changes the traditional loosely correlated or simply polled synchronization mode between the lightweight model and background data. The system can accurately perceive the "quality" and "quantity" of changes, triggering incremental data synchronization only when necessary and with the optimal priority. This fundamentally ensures that the user's observed geometric state and attribute information are always consistent with the latest engineering data source when operating the lightweight model, solving the problems of information fragmentation and lag, and making the lightweight model a reliable, real-time, and information-complete decision support carrier once again.
[0048] (2) In this invention, a hierarchical decision threshold is set based on the calculated data synchronization degree to guide the execution strategy of incremental synchronization. The system can automatically distinguish between urgent changes and ordinary updates, immediately initiate synchronization for high-urgency changes, perform queued batch transmission for general changes, and only log changes for low-urgency changes. This differentiated synchronization strategy greatly optimizes the utilization efficiency of network bandwidth and server resources. It avoids the resource waste caused by traditional full synchronization or high-frequency polling, and also reduces the crowding of communication channels by low-value data. Especially in scenarios with poor network conditions or concurrent modifications by multiple users, this mechanism can effectively ensure the timely delivery of critical data changes, maintain the stability and overall throughput performance of the system under complex working conditions, and solve the resource conflict and efficiency bottleneck problems caused by rigid synchronization strategies.
[0049] (3) In this invention, by determining the priority of the interaction response in real time during the user interaction phase, and dynamically scheduling and allocating computing, rendering, and network resources based on this priority, the smoothness and immediacy of human-computer interaction are significantly improved. The priority determination comprehensively considers the operation type, the complexity of the model in the area of effect, and the user's historical operating habits, enabling the system to intelligently identify the operation that most needs rapid feedback (such as fine-grained querying of the view focus area). High-priority operations can obtain sufficient resource guarantees to receive immediate responses, while low-priority operations are rationally scheduled to avoid blocking. This intelligent resource scheduling mechanism ensures that even when operating ultra-large, highly complex lightweight models, the user's core interactive intent can receive rapid and accurate visual and data feedback, effectively eliminating interface lag and operational delays, thereby greatly improving the user's operating experience and work efficiency in data-intensive BIM applications.
[0050] The above description is merely a specific embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in the present invention should be included within the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.
[0051] The following points need to be explained: (1) The accompanying drawings of the embodiments of the present invention only involve the structures involved in the embodiments of the present invention. Other structures can refer to the general design.
[0052] (2) For clarity, the thickness of layers or regions is enlarged or reduced in the drawings used to describe embodiments of the invention, i.e., these drawings are not drawn to scale. It is understood that when an element such as a layer, film, region or substrate is referred to as being “above” or “below” another element, the element may be “directly” located “above” or “below” the other element or there may be intermediate elements.
[0053] (3) Where there is no conflict, the embodiments of the present invention and the features in the embodiments can be combined with each other to obtain new embodiments.
[0054] The above are merely specific embodiments of the present invention, but the scope of protection of the present invention is not limited thereto. The scope of protection of the present invention should be determined by the scope of the claims.
Claims
1. A lightweight model data integration and interaction method based on BIM, characterized in that, include: S1: Obtain the original BIM model and its associated complete engineering data; S2: The original BIM model is lightweighted to generate a lightweight model containing simplified geometric data and key attribute data, and the complete engineering data is structurally extracted to generate a discrete engineering data package associated with the model components. S3: Establish a dynamic bidirectional data link between the lightweight model and the discrete engineering data package; calculate the current data synchronization degree based on real-time monitoring of model state changes and data operation requests; and make decisions and execute incremental data synchronization based on the data synchronization degree. S4: In response to the result of the incremental data synchronization, drive the geometric state and attribute information of the lightweight model to be matched and updated; S5: Receive user interaction operations on the updated lightweight model at the visualization end, determine the interaction response priority of the interaction operation in real time, and schedule and allocate system resources according to the priority to generate and feed back the corresponding interaction response results.
2. The method for lightweight model data integration and interaction based on BIM according to claim 1, characterized in that, In step S3, calculating the current data synchronization degree specifically includes: S301: Obtain the model geometric difference feature set since the last complete synchronization. Engineering data change record set ; S302: Calculate the geometric entropy of model differences Dispersion of the operation sequence with data change ; S303: Real-time acquisition of current network channel evaluation parameters, including average latency. With packet loss rate ; S304: Based on the geometric feature entropy Operation sequence discreteness Average delay and packet loss rate The data synchronization degree is calculated using the following formula. ; in, For differences Probability estimate of occurrence; , For change operation timestamp, Average timestamp; The normalized adjustment coefficient satisfies ; The characteristic decay time constant is denoted as .
3. The lightweight model data integration and interaction method based on BIM according to claim 1, characterized in that, In step S5, the real-time determination of the interaction response priority of the interactive operation specifically includes: S501: Identify the type of the interaction operation and map it to the basic type coefficient. ; S502: Analyze the number of detail levels of model components within the interaction region. Total number of components ; S503: Obtain the average response time of similar historical operations for this user. And the time interval between this operation and the most recent operation on the same view. ; S504: Based on the aforementioned basic type coefficients Detail level hierarchy Total number of components Average response time and time interval The interaction response priority is calculated using the following formula. ; Where e is the natural constant; The time decay factor; It is a very small positive constant used to prevent the denominator from being zero.
4. The method for lightweight model data integration and interaction based on BIM according to claim 1, characterized in that, In step S2, the lightweighting process of the original BIM model specifically includes: S201: Extract the feature contour lines and key connection points of model components through geometric topology analysis and semantic recognition; S202: Based on a preset accuracy threshold, non-feature patches and internal redundant geometric elements are eliminated; S203: Based on the component type and engineering attributes, the key attribute data is reorganized into hierarchical data blocks and bound to the simplified geometric data.
5. The lightweight model data integration and interaction method based on BIM according to claim 1, characterized in that, In step S3, the step of making a decision and performing incremental data synchronization based on the data synchronization degree specifically includes: S305: Preset first synchronization threshold With the second synchronization threshold ,in ; S306: If If this happens, a high-priority synchronization thread will be triggered to immediately transmit all the data to be synchronized. S307: If Then the data to be synchronized will be added to the queue and transmitted in batches in sequence; S308: If If the data change log is not recorded, network transmission will not be started temporarily, and the process will wait for the next calculation cycle.
6. The lightweight model data integration and interaction method based on BIM according to claim 1, characterized in that, In step S4, the matching and updating of the geometric state and attribute information of the lightweight model specifically includes: S401: For geometry state updates, a local redrawing algorithm for difference patches and a smooth transition algorithm for adjacent patches are used for rendering. S402: For attribute information updates, highlight them in the visualization interface using dynamic labels and predefined color codes.
7. The lightweight model data integration and interaction method based on BIM according to claim 1, characterized in that, In step S202, the process of removing non-feature patches and internal redundant geometric elements based on a preset precision threshold specifically includes: S2021: Based on the default display ratio of the component in the engineering view and the user-defined attention level, dynamically adjust the accuracy threshold of different components; S2022: For structural members, priority should be given to preserving their stress characteristic lines and the geometry of the end connection areas; S2023: For equipment and piping components, priority should be given to preserving their center axis, connecting flanges, and valve features.
8. The method for lightweight model data integration and interaction based on BIM according to claim 1, characterized in that, In step S307, the sequential batch transmission is performed according to the following sorting rules: S3071: Prioritize the transmission of data to be synchronized that is associated with the current user view focus area; S3072: Next, transmit the data to be synchronized with the most recently modified timestamp; S3073: The last transmitted data packet is less than the preset size.
9. A lightweight model data integration and interaction method based on BIM according to claim 1, characterized in that, In step S1, obtaining the original BIM model and its associated complete engineering data specifically includes: S101: Export model files conforming to the Industrial Basic Class IFC standard from multiple heterogeneous design platforms; S102: Parse the model file and extract core model information, including geometric entities, attribute sets, and relational networks; S103: Synchronize schedule, cost, bill of materials, and quality inspection report data associated with model components from the project management system database.
10. A lightweight model data integration and interaction method based on BIM according to claim 1, characterized in that, In step S5, generating and feeding back the corresponding interactive response result specifically includes: S508: Based on the aforementioned interaction response priority The allocated system resources generate a visual data stream with a corresponding level of detail. S509: Encode the visualized data stream and send it to the client requesting interaction; S510: In the client interface, the interactive response results are presented in the form of graphic highlighting, data panel pop-up, or 3D animation.