Design collaboration modification method and system based on semantic encapsulation and bcf file transfer

Abstract

This application relates to the field of Building Information Modeling (BIM) technology, and in particular to a design collaborative modification method and system based on semantic encapsulation and BCF file transmission. It transforms ambiguous natural language instructions into structured design modification semantics and transmits them via BCF files, reducing communication costs and misunderstandings and ensuring accurate understanding of instructions. After approval, the system automatically executes model modifications, avoiding the inefficiency and error-proneness of manual operations, especially for modifications involving a large number of components or complex relationships. By updating BCF files and generating XML logs, modification information is fully recorded, facilitating quality traceability, problem review, and knowledge accumulation. Standardized semantics and BCF files provide a common language and communication foundation for designers from different professional backgrounds, simplifying cross-disciplinary coordination processes. Specific modification execution is completed automatically by the system, reducing the reliance of ordinary designers on complex BIM software commands.

Description

Technical Field

[0001] This application relates to the field of Building Information Modeling (BIM) technology, and in particular to a design collaborative modification method and system based on semantic encapsulation and BCF file transfer. Background Technology

[0002] Pumped storage power stations have complex underground powerhouse structures involving multiple disciplines such as hydraulic engineering, electromechanical engineering, structural engineering, and geology. The design process requires frequent cross-disciplinary coordination and design modifications. Traditional two-dimensional design or BIM-based collaborative design suffers from numerous pain points in the transmission and execution of modification instructions.

[0003] First, design modification instructions are often delivered in unstructured text, email, or verbal form, lacking standardization and precision. Recipients need to spend a lot of time understanding the intent of the instructions and repeatedly verifying them against the model, which can easily lead to misunderstandings, resulting in errors or omissions in the modifications.

[0004] Secondly, even when using BIM software, the execution of modification instructions often requires manual operation. For example, if an electromechanical engineer requests an adjustment to the position of a piece of equipment within the main plant, a hydraulic engineer must manually locate the equipment and its related components (such as structural beams, slabs, and walls) in the model and then adjust their position or dimensional parameters one by one. This process is not only inefficient but also prone to human error, leading to unsynchronized modifications of related components and disrupting the model's consistency.

[0005] Secondly, the traceability of the design modification process is poor. Information such as what was modified, why it was modified, who modified it, when it was modified, and the model status before and after the modification is often scattered in different communication records and version models, making it difficult to form a complete and auditable modification history, which is not conducive to the control of design quality and the traceability of problems.

[0006] To address these issues, the industry has begun experimenting with BIM collaboration platforms and Building Collaboration Format (BCF) files. BCF is a standard format for recording and sharing BIM model viewpoints and issues, typically including camera position, orientation, zoom level, and issue description text and screenshots. However, existing BCF applications primarily focus on issue recording and communication; their text descriptions still rely on natural language and lack structured semantic information, failing to directly drive automatic model modifications. Designers need to manually understand modification requirements based on the views and descriptions in the BCF and then manually execute the modifications, failing to truly achieve a closed loop from instruction transmission to automatic model modification.

[0007] Therefore, there is an urgent need for a new method and technology that can structure design modification intentions into identifiable and executable semantics, and transmit them through a standardized file format (such as BCF), ultimately achieving automatic and accurate modification of the model while retaining a complete modification record. Summary of the Invention

[0008] To achieve the above objectives, this application provides the following technical solution:

[0009] According to a first aspect of the present invention, the present invention claims protection for a design collaborative modification method based on semantic encapsulation and BCF file transfer, comprising:

[0010] S1. Construct a semantic enumeration library for modifying the design of the underground powerhouse of a pumped storage power station. Use a user interface to encapsulate the design semantic enumeration library and display it to the reviewers. Then, use a high-dimensional vector algorithm to transform the design modification semantics into high-order vectors and form a vector library.

[0011] S2, the reviewer selects design modification semantics from the user interface based on the modification intent, and binds the design modification semantics to elements of the modification intent model;

[0012] S3, when there is a lack of directly corresponding modification semantics, call the large language model interface to analyze the similarity between the reviewer's semantics and the vectors in the modification semantics library, recommend design modifications, locate the elements in the BIM model based on the elements of the bound modification intention model, and generate a BCF file by integrating the current view information and the design modification semantics.

[0013] S4, the BCF file is uploaded to the collaboration platform, the collaboration platform parses the BCF file to obtain the embedded structured design modification semantics and modification intent model and displays it to the designer;

[0014] S5, the designer reviews the design modification semantics and modification intent model, calls the BIM software API, automatically converts the design modification semantics into the corresponding modification program object, and completes the automatic modification;

[0015] S6. Update the BCF file based on the designer's modification history for subsequent design modifications and update tracking.

[0016] Furthermore, the proposed modification semantic enumeration library for the design of the underground powerhouse of a pumped storage power station also includes:

[0017] Based on the common scenarios and requirements of the underground powerhouse design of the pumped storage power station, multiple atomic operations or combined operations for design modifications are summarized and extracted to form a semantic enumeration library for design modifications.

[0018] Each semantic in the semantic enumeration library is assigned a unique identifier (ID) and a standardized name and description.

[0019] For complex modification scenarios, we define compositional semantics, which are composed of multiple atomic semantics combined according to specific logic.

[0020] The semantics and their encoding are predefined and stored as the basis for subsequent steps.

[0021] Examples include "adjust component position", "modify component size", "replace component type", "add component", "delete component", "modify component material", "widen the upstream of the main plant", "increase the length of the installation room", "move the installation room to the left", and "change the side entrance to the front entrance".

[0022] Furthermore, the step of encapsulating the modified semantic enumeration library using a user interface and presenting it to reviewers includes:

[0023] Develop a user interface (UI) that presents the modified semantic enumeration library to design reviewers.

[0024] Each semantic term is accompanied by an explanation or example image on the user interface (UI) to help users understand its meaning and applicable scenarios.

[0025] Furthermore, the reviewer selects design modification semantics from the user interface based on the modification intent, and binds the design modification semantics to elements of the modification intent model, which also includes:

[0026] When proposing design modifications, the reviewers can use the user interface to browse or search and select one or more design modification semantics that best match their modification intentions.

[0027] Using the model selection tool provided by the user interface, the selected semantics are associated with the specific components or sets of components in the model that need to be modified, and the corresponding model ID is bound.

[0028] Record the list of semantic IDs and bound model IDs selected by the reviewers.

[0029] Furthermore, the step of locating the element in the BIM model based on the bound elements of the modification intent model, and generating a BCF file by integrating the current view information and the design modification semantics, also includes:

[0030] Based on the model ID bound by the reviewer, the element is automatically located in the currently opened BIM model software, and the current camera view information, including camera position, target point, viewing distance, and viewing angle, is obtained.

[0031] The standardized description of the semantics of the design modifications selected by the user is integrated with the model ID and view information;

[0032] The merged information is organized according to the BCF file format specification to generate a BCF file. The BCF file contains standard view information, embedded structured design modification semantics and their associated model IDs.

[0033] Furthermore, uploading the BCF file to the collaborative platform also includes:

[0034] The generated BCF file was uploaded to the BIM collaboration platform used by the project;

[0035] The collaborative platform pushes the BCF file to the next-order designer who needs to execute or review the modification, according to preset rules or designated recipients.

[0036] The notification content pushed includes basic information about the BCF file, including at least the title, the type of component involved, ID, camera location, modification semantics, responsible person, modification time, and version number.

[0037] Furthermore, the collaborative platform parses the BCF file to obtain the embedded structured design modification semantics and modification intent model and displays it to the designer, which also includes:

[0038] After receiving the notification on the collaborative platform, the next designer clicks to view the BCF file;

[0039] Parse the BCF file to identify the embedded structured design modification semantics and model IDs;

[0040] Based on the view information, the corresponding view is automatically opened in the local BIM model software, and the component that needs to be modified is located.

[0041] Furthermore, the designer reviews the design modification semantics and modification intent model, calls the BIM software API, and automatically converts the design modification semantics into corresponding modification program objects to complete the automatic modification. This also includes:

[0042] If the designer approves the changes and confirms their reasonableness, then the approval process will proceed.

[0043] Upon receiving the approval signal, the automatic modification process is initiated;

[0044] Parse the approved design modification semantics and their associated model IDs;

[0045] The API of the BIM modeling software is called to dynamically generate the corresponding modification command object based on the specific semantic meaning.

[0046] Furthermore, the updating of the BCF file based on the designer's modification history for subsequent design modifications and update tracking also includes:

[0047] After the automatic modification is completed, the system will update the modified results, the modification timestamp, and the executor information back into the original BCF file;

[0048] The updated BCF file retains the original modification instructions and view information, and adds the modified status and process records;

[0049] The updated BCF file is then uploaded or updated to the collaboration platform to form a complete closed-loop modification record;

[0050] As needed, key parameters, reasons, involved model IDs, and viewpoint data during the modification process should be saved separately in the form of an XML file as a traceability log.

[0051] According to a second aspect of the present invention, the present invention claims protection for a design collaborative modification system based on semantic encapsulation and BCF file transfer, comprising:

[0052] The semantic library management module is used to store and manage the design modification semantic enumeration library and its encoding.

[0053] The user interface module encapsulates the design modification semantics and provides an interactive interface for users to select semantics, bind model IDs, and input parameters.

[0054] The BCF generation module generates BCF files based on semantics, model ID, and view information.

[0055] The collaboration platform interface module is responsible for uploading BCF files to the collaboration platform and receiving BCF files and approval signals from the collaboration platform.

[0056] The BCF parsing and display module parses the received BCF file, identifies semantics, locates views and components in the model, and displays the modified content for review.

[0057] The automatic modification execution module receives approval signals, parses semantics, and calls the BIM software API to execute automatic modifications.

[0058] The modification record and update module updates the contents of the BCF file, records the modification process, and generates a traceability log.

[0059] The aforementioned design collaborative modification system based on semantic encapsulation and BCF file transfer is used to execute the aforementioned design collaborative modification method based on semantic encapsulation and BCF file transfer.

[0060] This application relates to the field of Building Information Modeling (BIM) technology, and in particular to a design collaborative modification method and system based on semantic encapsulation and BCF file transmission. It transforms ambiguous natural language instructions into structured design modification semantics and transmits them via BCF files, reducing communication costs and misunderstandings and ensuring accurate understanding of instructions. After approval, the system automatically executes model modifications, avoiding the inefficiency and error-proneness of manual operations, especially for modifications involving a large number of components or complex relationships. By updating BCF files and generating XML logs, modification information is fully recorded, facilitating quality traceability, problem review, and knowledge accumulation. Standardized semantics and BCF files provide a common language and communication foundation for designers from different professional backgrounds, simplifying cross-disciplinary coordination processes. Specific modification execution is completed automatically by the system, reducing the reliance of ordinary designers on complex BIM software commands. Attached Figure Description

[0061] Figure 1 A flowchart illustrating a collaborative design modification method based on semantic encapsulation and BCF file transfer, as claimed in an embodiment of this application;

[0062] Figure 2 A schematic diagram of a user interface module for a design collaborative modification method based on semantic encapsulation and BCF file transfer, as claimed in an embodiment of this application;

[0063] Figure 3 A schematic diagram of the structure of a BCF file for a design collaborative modification method based on semantic encapsulation and BCF file transfer, which is claimed in an embodiment of this application;

[0064] Figure 4 This is a structural block diagram of a collaborative modification system based on semantic encapsulation and BCF file transfer, which is claimed in an embodiment of this application. Detailed Implementation

[0065] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of the embodiments. Based on the embodiments of this application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of this application.

[0066] The terms "first," "second," and "third" in this application are for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Therefore, a feature defined as "first," "second," or "third" may explicitly or implicitly include at least one of that feature. In the description of this application, "multiple" means at least two, such as two, three, etc., unless otherwise explicitly specified. All directional indications (such as up, down, left, right, front, back, etc.) in the embodiments of this application are only used to explain the relative positional relationships and movements between components in a specific orientation (as shown in the figures). If the specific orientation changes, the directional indications also change accordingly. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or device that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to these processes, methods, products, or devices.

[0067] In this document, the term "embodiment" means that a particular feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment of this application. The appearance of this phrase in various places throughout the specification does not necessarily refer to the same embodiment, nor is it a mutually exclusive, independent, or alternative embodiment. It will be explicitly and implicitly understood by those skilled in the art that the embodiments described herein can be combined with other embodiments.

[0068] According to a first embodiment of the present invention, the present invention claims protection for a design collaborative modification method based on semantic encapsulation and BCF file transfer, referring to... Figure 1 ,include:

[0069] S1. Construct a semantic enumeration library for modifying the design of the underground powerhouse of a pumped storage power station. Use a user interface to encapsulate the design semantic enumeration library and display it to the reviewers. Then, use a high-dimensional vector algorithm to transform the design modification semantics into high-order vectors and form a vector library.

[0070] S2, the reviewer selects design modification semantics from the user interface based on the modification intent, and binds the design modification semantics to elements of the modification intent model;

[0071] S3, when there is a lack of directly corresponding modification semantics, call the large language model interface to analyze the similarity between the reviewer's semantics and the vectors in the modification semantics library, recommend design modifications, locate the elements in the BIM model based on the elements of the bound modification intention model, and generate a BCF file by integrating the current view information and the design modification semantics.

[0072] S4, the BCF file is uploaded to the collaboration platform, the collaboration platform parses the BCF file to obtain the embedded structured design modification semantics and modification intent model and displays it to the designer;

[0073] S5, the designer reviews the design modification semantics and modification intent model, calls the BIM software API, automatically converts the design modification semantics into the corresponding modification program object, and completes the automatic modification;

[0074] S6. Update the BCF file based on the designer's modification history for subsequent design modifications and update tracking.

[0075] Furthermore, the proposed modification semantic enumeration library for the design of the underground powerhouse of a pumped storage power station also includes:

[0076] Based on the common scenarios and requirements of the underground powerhouse design of the pumped storage power station, multiple atomic operations or combined operations for design modifications are summarized and extracted to form a semantic enumeration library for design modifications.

[0077] Each semantic in the semantic enumeration library is assigned a unique identifier (ID) and a standardized name and description.

[0078] For complex modification scenarios, we define compositional semantics, which are composed of multiple atomic semantics combined according to specific logic.

[0079] The semantics and their encoding are predefined and stored as the basis for subsequent steps.

[0080] In this embodiment, the semantic enumeration library may include at least the following: "adjust component position", "modify component size", "replace component type", "add component", "delete component", "modify component material", "widen the upstream of the main plant", "increase the length of the installation room", "move the installation room to the left", "change the side entrance to the front entrance", etc.

[0081] Referring to Table 1, design and modify the semantic enumeration library example to display the key information fields of the records;

[0082] Table 1: Key Information Fields of Records in Example Design and Modification of Semantic Enumeration Library

[0083]

[0084] Furthermore, the step of encapsulating the modified semantic enumeration library using a user interface and presenting it to reviewers includes:

[0085] Develop a user interface (UI) that presents the modified semantic enumeration library to design reviewers.

[0086] Each semantic term is accompanied by an explanation or example image on the user interface (UI) to help users understand its meaning and applicable scenarios.

[0087] In this embodiment, a tree structure, category tags, search boxes, or similar methods can be used to facilitate users quickly finding the design modification semantics they need. Each semantic may be accompanied by a brief explanation or example image on the interface to help users understand its meaning and applicable scenarios. The interface design should be simple and clear, conforming to the usage habits of underground plant designers.

[0088] Reference Figure 2 A schematic diagram of the user interface module, showing interface elements such as semantic selection, model binding, and parameter input.

[0089] Furthermore, the reviewer selects design modification semantics from the user interface based on the modification intent, and binds the design modification semantics to elements of the modification intent model, which also includes:

[0090] When proposing design modifications, the reviewers can use the user interface to browse or search and select one or more design modification semantics that best match their modification intentions.

[0091] Using the model selection tool provided by the user interface, the selected semantics are associated with the specific components or sets of components in the model that need to be modified, and the corresponding model ID is bound.

[0092] Record the list of semantic IDs and bound model IDs selected by the reviewers.

[0093] In this embodiment, when design reviewers (such as electromechanical engineers) need to propose design modifications, they first browse or search for and select one or more design modification semantics that best match their modification intentions through the aforementioned user interface. Then, using the model selection tools provided by the interface (such as picking, box selection, and inputting IDs), they associate the selected semantics with the specific components or sets of components in the model that need to be modified, i.e., bind the corresponding model IDs. The system records the semantic IDs selected by the user and the list of bound model IDs.

[0094] Furthermore, the step of locating the element in the BIM model based on the bound elements of the modification intent model, and generating a BCF file by integrating the current view information and the design modification semantics, also includes:

[0095] Based on the model ID bound by the reviewer, the element is automatically located in the currently opened BIM model software, and the current camera view information, including camera position, target point, viewing distance, and viewing angle, is obtained.

[0096] The standardized description of the semantics of the design modifications selected by the user is integrated with the model ID and view information;

[0097] The merged information is organized according to the BCF file format specification to generate a BCF file. The BCF file contains standard view information, embedded structured design modification semantics and their associated model IDs.

[0098] In this embodiment, the system automatically locates the components in the currently opened BIM model software (such as Revit) based on the user-bound model ID and obtains the current camera view information, including camera position, target point, viewing distance, and viewing angle. Simultaneously, the system merges the standardized description of the user-selected design modification semantics (which may include parameter placeholders, such as "modify the X-coordinate of component [model ID] to [value to be input]") with the model ID and view information. The merged information is organized according to the BCF file format specification to generate a BCF file. This BCF file not only contains standard view information but also embeds structured design modification semantics and their associated model IDs, making the BCF file not only a communication carrier but also a command for subsequent automatic modifications.

[0099] Reference Figure 3 This is a schematic diagram of the structure of a BCF file according to an embodiment of this application, showing the key information fields of the records.

[0100] Furthermore, uploading the BCF file to the collaborative platform also includes:

[0101] The generated BCF file was uploaded to the BIM collaboration platform used by the project;

[0102] The collaborative platform pushes the BCF file to the next-order designer who needs to execute or review the modification, according to preset rules or designated recipients.

[0103] The notification content pushed includes basic information about the BCF file, including at least the title, the type of component involved, ID, camera location, modification semantics, responsible person, modification time, and version number.

[0104] Furthermore, the collaborative platform parses the BCF file to obtain the embedded structured design modification semantics and modification intent model and displays it to the designer, which also includes:

[0105] After receiving the notification on the collaborative platform, the next designer clicks to view the BCF file;

[0106] Parse the BCF file to identify the embedded structured design modification semantics and model IDs;

[0107] Based on the view information, the corresponding view is automatically opened in the local BIM model software, and the component that needs to be modified is located.

[0108] In this embodiment, the interface can highlight these components and display the modification semantic descriptions contained in the BCF file. Designers can intuitively see the content, location, and reasons for the modifications. Designers then review these modifications to determine their rationality, feasibility, and impact on other disciplines.

[0109] Furthermore, the designer reviews the design modification semantics and modification intent model, calls the BIM software API, and automatically converts the design modification semantics into corresponding modification program objects to complete the automatic modification. This also includes:

[0110] If the designer approves the changes and confirms their reasonableness, then the approval process will proceed.

[0111] Upon receiving the approval signal, the automatic modification process is initiated;

[0112] Parse the approved design modification semantics and their associated model IDs;

[0113] The API of the BIM modeling software is called to dynamically generate the corresponding modification command object based on the specific semantic meaning.

[0114] In this embodiment, if the semantic is "modify the X-coordinate of the component [model ID] to [value]", the system will call the Revit API methods for moving components or modifying component parameters, passing in the model ID and the new X-coordinate value. For more complex semantics, multiple API methods may need to be called in combination. In this way, the system automatically and accurately executes design modifications, avoiding errors and omissions from manual operations.

[0115] Furthermore, the updating of the BCF file based on the designer's modification history for subsequent design modifications and update tracking also includes:

[0116] After the automatic modification is completed, the system will update the modified results, the modification timestamp, and the executor information back into the original BCF file;

[0117] The updated BCF file retains the original modification instructions and view information, and adds the modified status and process records;

[0118] The updated BCF file is then uploaded or updated to the collaboration platform to form a complete closed-loop modification record;

[0119] As needed, key parameters, reasons, involved model IDs, and viewpoint data during the modification process should be saved separately in the form of an XML file as a traceability log.

[0120] According to a second embodiment of the present invention, the present invention claims protection for a design collaborative modification system based on semantic encapsulation and BCF file transfer, referring to... Figure 4 ,include:

[0121] The semantic library management module is used to store and manage the design modification semantic enumeration library and its encoding.

[0122] The user interface module encapsulates the design modification semantics and provides an interactive interface for users to select semantics, bind model IDs, and input parameters.

[0123] The BCF generation module generates BCF files based on semantics, model ID, and view information.

[0124] The collaboration platform interface module is responsible for uploading BCF files to the collaboration platform and receiving BCF files and approval signals from the collaboration platform.

[0125] The BCF parsing and display module parses the received BCF file, identifies semantics, locates views and components in the model, and displays the modified content for review.

[0126] The automatic modification execution module receives approval signals, parses semantics, and calls the BIM software API to execute automatic modifications.

[0127] The modification record and update module updates the contents of the BCF file, records the modification process, and generates a traceability log.

[0128] The aforementioned design collaborative modification system based on semantic encapsulation and BCF file transfer is used to execute the aforementioned design collaborative modification method based on semantic encapsulation and BCF file transfer.

[0129] The following is an illustration using a specific example:

[0130] During the design process, the electromechanical engineers discovered that due to adjustments in equipment dimensions, it was necessary to move the base of a large pump unit in the main plant 500mm in the positive X-axis direction, while ensuring that it maintained a distance of at least 300mm from the adjacent cable tray.

[0131] Establish a semantic library: The system has predefined semantics and their codes such as "adjust component position" and "modify spatial relationship (spacing)".

[0132] Interface Encapsulation: The electromechanical engineer locates and selects the "Adjust Component Position" semantic in the UI, then uses the pick tool to select the pump base model and bind its model ID. Next, they may need to select the "Modify Spatial Relationship" semantic and bind the model IDs of the base and adjacent cable trays.

[0133] Selection and Binding: Engineers input or select the movement distance (500mm) and direction (positive X-axis) in the UI, as well as the required spacing (300mm). The system records the semantic ID, model ID list, and parameters.

[0134] Generate BCF: The system locates the base model, obtains the current view, and integrates the semantics of "Adjust component position (ID: semantic_001)", "Modify spatial relationship (ID: semantic_002)", relevant model IDs, movement parameters, spacing parameters, and view information to generate a BCF file. The text in the BCF file might look something like: "Please move the pump base (model ID=12345) 500mm along the positive X-axis, and ensure a minimum 300mm gap between it and the cable tray (model ID=67890)."

[0135] Upload and push: BCF files are uploaded to the collaborative platform and pushed to hydraulic engineers.

[0136] Identification and Approval: The hydraulic engineer opens BCF (Baidu, Cloud Computing), and the system automatically locates the pump base and cable tray, displaying the modification requirements and views. The engineer checks whether the moved base conflicts with structural beams, walls, etc., and whether the spacing requirements are reasonable. Approval is granted after confirmation.

[0137] Automatic Modification: The system parses the approved semantics (move, spacing check) and calls the Revit API. First, it locates the component with model ID=12345 and modifies its position parameters (X coordinate +500mm). Then, it locates the component with model ID=67890, checks and may fine-tune its own or related component positions to meet the 300mm spacing requirement (this step may require more complex logical judgments).

[0138] Update and Tracking: After the modifications were completed, the BCF file was updated, adding records such as "Model ID=12345 has been moved to a new location, new coordinates (X,Y,Z), confirmed to be 300mm from model ID=67890, modification time: 2025-06-17 14:30, executor: system". Simultaneously, relevant parameters and processes may be written to an XML log file.

[0139] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces, or indirect coupling or communication connection between apparatuses or units, and may be electrical, mechanical, or other forms.

[0140] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated units described above can be implemented in hardware or as software functional units. The above are merely embodiments of this application and do not limit the patent scope of this application. Any equivalent structural or procedural transformations made based on the description and drawings of this application, or direct or indirect applications in other related technical fields, are similarly included within the patent protection scope of this application.

[0141] The specific embodiments of the invention have been described in detail above, but they are only examples, and this application is not limited to the specific embodiments described above. For those skilled in the art, any equivalent modifications or substitutions to the invention are also within the scope of this application. Therefore, all equivalent changes, modifications, and improvements made without departing from the spirit and principles of this application should be covered within the scope of this application.

Claims

1. A method for design collaboration modification based on semantic encapsulation and BCF file transfer, characterized in that, include: S1. Construct a semantic enumeration library for modifying the design of the underground powerhouse of a pumped storage power station. Use a user interface to encapsulate the design semantic enumeration library and display it to the reviewers. Then, use a high-dimensional vector algorithm to transform the design modification semantics into high-order vectors and form a vector library. S2, the reviewer selects design modification semantics from the user interface based on the modification intent, and binds the design modification semantics to elements of the modification intent model; S3, when there is a lack of directly corresponding modification semantics, call the large language model interface to analyze the similarity between the reviewer's semantics and the vectors in the modification semantics enumeration library, recommend design modifications, locate the elements in the BIM model based on the elements of the bound modification intention model, and generate a BCF file by integrating the current view information and the design modification semantics. S4, the BCF file is uploaded to the collaboration platform, the collaboration platform parses the BCF file to obtain the embedded structured design modification semantics and modification intent model and displays it to the designer; S5, the designer reviews the design modification semantics and modification intent model, calls the BIM software API, automatically converts the design modification semantics into the corresponding modification program object, and completes the automatic modification; S6. Update the BCF file based on the designer's modification history for subsequent design modifications and update tracking.

2. The method according to claim 1, wherein, The modified semantic enumeration library for constructing the underground powerhouse design of the pumped storage power station also includes: Based on the common scenarios and requirements of the underground powerhouse design of the pumped storage power station, multiple atomic operations or combined operations for design modifications are summarized and extracted to form a semantic enumeration library for design modifications. Each semantic in the semantic enumeration library is assigned a unique identifier (ID) and a standardized name and description. For complex modification scenarios, we define compositional semantics, which are composed of multiple atomic semantics combined according to specific logic. The semantics and their encoding are predefined and stored as the basis for subsequent steps.

3. The method of claim 1, wherein the method further comprises: The process of encapsulating the modified semantic enumeration library using a user interface and presenting it to reviewers includes: Develop a user interface (UI) that presents the modified semantic enumeration library to design reviewers. Each semantic term is accompanied by an explanation or example image on the user interface (UI) to help users understand its meaning and applicable scenarios.

4. The method of claim 1, wherein the method further comprises: The reviewer selects design modification semantics from the user interface based on the modification intent, and binds the design modification semantics to elements of the modification intent model, further including: When proposing design modifications, the reviewers can use the user interface to browse or search and select one or more design modification semantics that best match their modification intentions. Using the model selection tool provided by the user interface, the selected semantics are associated with the specific components or sets of components in the model that need to be modified, and the corresponding model ID is bound. Record the list of semantic IDs and bound model IDs selected by the reviewers.

5. The method of claim 4, wherein the method further comprises: The step of locating the element in the BIM model based on the bound elements of the modification intent model, and generating a BCF file by integrating the current view information and the design modification semantics, further includes: Based on the model ID bound by the reviewer, the element is automatically located in the currently opened BIM model software, and the current camera view information, including camera position, target point, viewing distance, and viewing angle, is obtained. The standardized description of the semantics of the design modifications selected by the user is integrated with the model ID and view information; The merged information is organized according to the BCF file format specification to generate a BCF file. The BCF file contains standard view information, embedded structured design modification semantics and their associated model IDs.

6. The method of claim 1, wherein the method further comprises: Uploading the BCF file to the collaborative platform further includes: The generated BCF file was uploaded to the BIM collaboration platform used by the project; The collaborative platform pushes the BCF file to the next-order designer who needs to execute or review the modification, according to preset rules or designated recipients. The notification content pushed includes basic information about the BCF file, including at least the title, the type of component involved, ID, camera location, modification semantics, responsible person, modification time, and version number.

7. The method of claim 6, wherein the method further comprises: The collaborative platform parses the BCF file to obtain the embedded structured design modification semantics and modification intent model, and displays it to the designers. It also includes: After receiving the notification on the collaborative platform, the next designer clicks to view the BCF file; Parse the BCF file to identify the embedded structured design modification semantics and model IDs; Based on the view information, the corresponding view is automatically opened in the local BIM model software, and the component that needs to be modified is located.

8. The method of claim 1, wherein the method further comprises: The designer reviews the design modification semantics and modification intent model, calls the BIM software API, automatically converts the design modification semantics into corresponding modification program objects, and completes the automatic modification. This also includes: If the designer approves the changes and confirms their reasonableness, then the approval process will proceed. Upon receiving the approval signal, the automatic modification process is initiated; Parse the approved design modification semantics and their associated model IDs; The API of the BIM modeling software is called to dynamically generate the corresponding modification command object based on the specific semantic meaning.

9. The method of claim 1, wherein the method further comprises: The method of updating the BCF file based on the designer's modification history for subsequent design modifications and update tracking also includes: After the automatic modification is completed, the system will update the modified results, the modification timestamp, and the executor information back into the original BCF file; The updated BCF file retains the original modification instructions and view information, and adds the modified status and process records; The updated BCF file is then uploaded or updated to the collaboration platform to form a complete closed-loop modification record; As needed, key parameters, reasons, involved model IDs, and viewpoint data during the modification process should be saved separately in the form of an XML file as a traceability log.

10. A system for design collaboration modification based on semantic encapsulation and BCF file transfer, characterized in that, include: The semantic library management module is used to store and manage the design modification semantic enumeration library and its encoding. The user interface module encapsulates the design modification semantics and provides an interactive interface for users to select semantics, bind model IDs, and input parameters. The BCF generation module generates BCF files based on semantics, model ID, and view information. The collaboration platform interface module is responsible for uploading BCF files to the collaboration platform and receiving BCF files and approval signals from the collaboration platform. The BCF parsing and display module parses the received BCF file, identifies semantics, locates views and components in the model, and displays the modified content for review. The automatic modification execution module receives approval signals, parses semantics, and calls the BIM software API to execute automatic modifications. The modification record and update module updates the contents of the BCF file, records the modification process, and generates a traceability log. The design collaborative modification system based on semantic encapsulation and BCF file transfer is used to execute the design collaborative modification method based on semantic encapsulation and BCF file transfer as described in any one of claims 1-9.

Images