Design collaborative modification method and system based on semantic packaging and BCF file transfer

Abstract

The invention relates to the technical field of building information models, in particular to a design collaborative modification method and system based on semantic packaging and BCF file transfer, and aims to convert a fuzzy natural language instruction into structured design modification semantics and transfer the design modification semantics through a BCF file, reduce communication cost and misunderstanding and ensure that the instruction is accurately understood; after approval is passed, the system can automatically execute model modification, low efficiency and error-prone performance of manual operation are avoided, and the advantages are more obvious especially for modification involving a large number of components or complex associations; by updating a BCF file and generating an XML log, information such as modification is completely recorded, and quality tracing, problem review and knowledge accumulation are facilitated; standardized semantics and BCF files provide common language and communication basis for designers with different professional backgrounds, and the cross-professional coordination process is simplified; and specific modification execution is automatically completed by the system, so that the dependence of common designers on complex BIM software operation commands is reduced.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of building information modeling (BIM), and in particular to a design collaborative modification method and system based on semantic encapsulation and BCF file transmission. BACKGROUND

[0002] The underground powerhouse structure of a pumped storage power station is complex, involving multiple disciplines such as hydraulic, mechanical and electrical, structure, and geology. Frequent cross-disciplinary coordination and design modification are required during the design process. Traditional two-dimensional design or BIM-based collaborative design has many pain points in terms of modification instruction transmission and execution.

[0003] Firstly, design modification instructions are often transmitted in unstructured text, email or oral form, lacking standardization and accuracy. The recipient needs to spend a lot of time understanding the instruction intent and repeatedly checking with the model, which is prone to misinterpretation, leading to modification errors or omissions.

[0004] Secondly, even if BIM software is used, the execution of modification instructions often requires manual operation. For example, a mechanical and electrical engineer proposes to adjust the position of a certain device in the main powerhouse, and a hydraulic engineer needs to manually find the device and its related components (such as structural beams, plates, and walls) in the model, and then adjust their position or size parameters one by one. This process is not only inefficient, but also prone to human error, causing associated components to be modified, disrupting the coordination of the model.

[0005] Thirdly, the traceability of the design modification process is poor. What was modified, why it was modified, who modified it, when it was modified, and the model state before and after modification are often scattered in different communication records and version models, making it difficult to form a complete and auditable modification history record, which is not conducive to design quality control and problem tracing.

[0006] In order to solve the above problems, the industry has begun to try using BIM collaboration platforms and BCF (Building Collaboration Format) files. BCF is a standard format for recording and sharing BIM model viewpoints (views) and issues, usually including camera position, direction, zoom level, and issue description text and screenshots. However, existing BCF applications mainly focus on issue recording and communication, and the text description is still in natural language, lacking structured semantic information, and cannot directly drive automatic modification of the model. Designers need to manually understand the modification requirements based on the views and descriptions in the BCF, and then manually execute the modification operations, without truly realizing the 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 intent into identifiable and executable semantics and pass it through a standardized file format (such as BCF), ultimately enabling automatic and accurate modification of the model while preserving complete modification records. SUMMARY

[0008] To achieve the above object, the present application provides the following technical solutions. According to the first aspect of the present application, a design collaborative modification method based on semantic encapsulation and BCF file transmission is requested to protect, comprising: S1, a modification semantic enumeration library of a pumped storage power station underground powerhouse design is constructed, the modification semantic enumeration library is encapsulated by a user interface and is displayed to an examiner, and design modification semantics are converted into high-order vectors by a high-dimensional vector algorithm and form a vector library; S2, the examiner selects design modification semantics from the user interface based on modification intent, and binds the design modification semantics with elements of a modification intent model; S3, when there is a lack of directly corresponding modification semantics, a large language model interface is called to analyze the similarity between the examiner's semantics and the vectors in the modification semantic library, recommend design modification, locate the elements in the BIM model according to the bound elements of the modification intent model, and generate a BCF file by fusing current view information and the design modification semantics; S4, the BCF file is uploaded to a collaborative platform, the collaborative platform parses the BCF file to obtain embedded structured design modification semantics and a modification intent model, and displays them to a designer; S5, the designer audits the design modification semantics and the modification intent model, calls a BIM software API, automatically converts the design modification semantics into corresponding modification program objects, and completes automatic modification; S6, the BCF file is updated based on the modification history of the designer, for subsequent design modification and update tracing.

[0009] Further, the construction of the modification semantic enumeration library of the pumped storage power station underground powerhouse design further comprises: According to common scenes and requirements of the pumped storage power station underground powerhouse design, a plurality of design modification atomic operations or combined operations are induced and refined to form a design modification semantic enumeration library; Each semantic of the semantic enumeration library is given a unique identifier ID and a standardized name and description; For complex modification scenes, combined semantics are defined, which are composed of multiple atomic semantics according to specific logic; The semantics and their codes are pre-defined and stored as the basis for subsequent steps.

[0010] For example, "adjust the position of the component", "modify the size of the component", "replace the type of the component", "add a new component", "delete a component", "modify the material of the component", "widen the upstream of the main factory building", "increase the length of the installation room", "replace the installation room to the left", "change the lateral entry to the front entry", etc.

[0011] Further, the user interface encapsulates the modification semantic enumeration library and displays it to the reviewer, including: Develop a user interface (UI) that presents the modification semantic enumeration library to the design reviewer; Each semantic is accompanied by an explanation or example picture on the user interface (UI), helping users understand its meaning and applicable scenarios.

[0012] Further, the reviewer selects design modification semantics from the user interface based on the modification intent and binds the design modification semantics to the elements of the modification intent model, also including: When proposing a design modification, the reviewer uses the user interface to browse or search and select one or more design modification semantics that best match their modification intent; Using the model selection tool provided by the user interface, the selected semantics are associated with specific components or component sets that need to be modified in the model, and the corresponding model ID is bound; Record the semantic ID selected by the reviewer and the list of bound model IDs.

[0013] Further, the elements of the bound modification intent model are located in the BIM model, and the current view information and the design modification semantics are fused to generate a BCF file, also including: According to the model ID bound by the reviewer, automatically locate the element in the currently opened BIM model software, and obtain the current camera view information, including camera position, target point, view distance, view angle, etc. Fuse the standardized description of the design modification semantics selected by the user with the model ID and view information; The fused information is organized according to the BCF file format specification to generate a BCF file, which contains standard view information and embedded structured design modification semantics and associated model IDs.

[0014] Further, the BCF file is uploaded to the collaborative platform, also including: The generated BCF file is uploaded to the BIM collaborative platform used by the project; According to the pre-set rules or designated recipients, the collaborative platform pushes the BCF file to the next designer who needs to perform or review the modification. The pushed notification content contains the basic information of the BCF file, at least including title, involved component type, ID, camera position, modification semantics, responsible person, modification time, and version number.

[0015] Further, the collaborative platform parses the BCF file to obtain embedded structured design modification semantics and modification intention model and displays them to the designer, and further includes: The next designer clicks to view the BCF file after receiving the notification on the collaborative platform; Parsing the BCF file to identify the embedded structured design modification semantics and model ID therein; According to the view information, the corresponding view is automatically opened in the local BIM model software, and the component to be modified is located.

[0016] Further, the designer audits the design modification semantics and modification intention model, calls the BIM software API, automatically converts the design modification semantics into the corresponding modification procedure object, and completes the automatic modification, and further includes: If the designer audits and passes, confirms that the modification is reasonable, and performs the approval operation; After receiving the signal of the approval, the automatic modification process is started; Parsing the design modification semantics and the bound model ID that pass the approval; Calling the API of the BIM model software, dynamically generating the corresponding modification command object according to the specific meaning of the semantics.

[0017] Further, the BCF file is updated based on the modification history of the designer, for subsequent design modification and update tracing, and further includes: After the automatic modification is completed, the system updates the results of the modification, the timestamp of the modification, and the information of the executor back to the original BCF file; The updated BCF file retains the original modification instruction and view information, and adds the state and process record after the modification; The updated BCF file is uploaded or updated to the collaborative platform again, forming a complete modification closed loop record; According to the need, the key parameters, reasons, involved model ID, and perspective data in the modification process are saved in the form of an XML file as a trace log.

[0018] According to the second aspect of the present application, the present application claims to protect a design collaborative modification system based on semantic encapsulation and BCF file transmission, comprising: A semantic library management module for storing and managing a design modification semantics enumeration library and its code; A user interface module encapsulates the design modification semantics, provides an interactive interface for users to select semantics, bind model IDs, and input parameters; A BCF generation module generates a BCF file according to the semantics, model IDs, and view information; A collaborative platform interface module is responsible for uploading the BCF file to the collaborative platform and receiving the BCF file and approval signals from the collaborative platform; A BCF analysis and display module analyzes the received BCF file, identifies the semantics, locates the views and components in the model, and displays the modification content for review; An automatic modification execution module receives the approval signals, analyzes the semantics, and calls the BIM software API to execute the automatic modification; A modification record and update module updates the BCF file content, records the modification process, and generates a traceability log; The design collaborative modification system based on semantic encapsulation and BCF file transmission is used to execute the design collaborative modification method based on semantic encapsulation and BCF file transmission.

[0019] The present application relates to the technical field of building information modeling, and in particular to a design collaborative modification method and system based on semantic encapsulation and BCF file transmission. The method and system convert fuzzy natural language instructions into structured design modification semantics and transmit them through BCF files, reducing communication costs and misunderstandings and ensuring that the instructions are accurately understood. After approval, the system can automatically execute model modification, avoiding the inefficiency and error-prone nature of manual operations, especially for modifications involving a large number of components or complex associations, where the advantages are more obvious. By updating the BCF file and generating an XML log, the modification information is recorded in its entirety, facilitating quality traceability, problem review, and knowledge accumulation. Standardized semantics and BCF files provide a common language and communication foundation for designers with different professional backgrounds, simplifying cross-professional coordination processes. The specific modification execution is automatically completed by the system, reducing the dependence of ordinary designers on complex BIM software operation commands. BRIEF DESCRIPTION OF DRAWINGS

[0020] Figure 1 A workflow diagram of a design collaborative modification method based on semantic encapsulation and BCF file transmission as claimed in the embodiments of the present application; Figure 2 A schematic diagram of a user interface module of a design collaborative modification method based on semantic encapsulation and BCF file transmission as claimed in the embodiments of the present application; Figure 3 A structural schematic diagram of a BCF file of a design collaborative modification method based on semantic encapsulation and BCF file transmission as claimed in the embodiments of the present application; Figure 4A structural module diagram of a design collaborative modification system based on semantic encapsulation and BCF file transmission is requested to be protected in the embodiments of the present application. DETAILED DESCRIPTION

[0021] The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, rather than all the embodiments of the present application. Based on the embodiments in the present application, all other embodiments obtained by a person of ordinary skill in the art without creative work fall within the scope of protection of the present application.

[0022] The terms "first", "second", "third" in the present application are only for descriptive purposes, and cannot be understood as indicating or implying relative importance or implicitly indicating the number of the indicated technical features. Therefore, the features defined with "first", "second", "third" can explicitly or implicitly include at least one of the features. In the description of the present application, the meaning of "a plurality of" is at least two, such as two, three, etc., unless otherwise explicitly and specifically limited. All directional indications (such as up, down, left, right, front, back, etc.) in the embodiments of the present application are only used to explain the relative positional relationship, movement condition, etc. between components in a certain posture (as shown in the drawings), and if the certain posture changes, the directional indications also change accordingly. In addition, the terms "include" and "have" 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 can optionally include steps or units not listed, or can optionally include other steps or units inherent to the process, method, product or device.

[0023] In this document, the term "embodiment" means that the specific features, structures or characteristics described in connection with the embodiment can be included in at least one embodiment of the present application. The appearance of this phrase in various places in the specification does not necessarily mean the same embodiment, nor is it independent or alternative to other embodiments. A person of ordinary skill in the art explicitly and implicitly understands that the embodiments described herein can be combined with other embodiments.

[0024] According to the first embodiment of the present application, the present application requests to protect a design collaborative modification method based on semantic encapsulation and BCF file transmission, with reference to Figure 1 , comprising: S1, constructing a modification semantic enumeration library of the underground powerhouse design of the pumped storage power station, encapsulating the modification semantic enumeration library by using a user interface, displaying the modification semantic enumeration library to an examiner, and converting the design modification semantics into a high-order vector by using a high-dimensional vector algorithm, and forming a vector library; S2, the reviewer selects a design modification semantic from the user interface based on the modification intention, and binds the design modification semantic with the elements of the modification intention model; S3, when there is no directly corresponding modification semantic, a large language model interface is called to analyze the reviewer semantic and the vector similarity in the modification semantic library, a design modification is recommended, the elements in the BIM model are located according to the bound elements of the modification intention model, the current view information and the design modification semantic are fused to generate a BCF file; S4, the BCF file is uploaded to a collaborative platform, and the collaborative platform parses the BCF file to obtain embedded structured design modification semantic and modification intention model and displays them to a designer; S5, the designer audits the design modification semantic and the modification intention model, calls a BIM software API, automatically converts the design modification semantic into a corresponding modification program object, and completes automatic modification; S6, the BCF file is updated based on the modification history of the designer, which is used for subsequent design modification and update tracing.

[0025] Further, the modification semantic enumeration library for constructing the underground powerhouse design of the pumped storage power station further comprises: According to the common scene and demand of the pumped storage power station design, a plurality of design modification atomic operations or combined operations are induced and refined to form a design modification semantic enumeration library; Each semantic of the semantic enumeration library is given a unique identifier ID and a standardized name and description; For complex modification scenes, a combined semantic is defined, which is composed of a plurality of atomic semantics according to a specific logic; The semantics and their codes are pre-defined and stored as the basis for subsequent steps.

[0026] In this embodiment, the content of the semantic enumeration library can at least include: "adjusting the position of the component", "modifying the size of the component", "replacing the type of the component", "adding a component", "deleting a component", "modifying the material of the component", "widening the upstream of the main powerhouse", "increasing the length of the installation room", "changing the installation room to the left", and "changing the lateral entry to the positive entry".

[0027] Referring to Table 1, the key information field of the design modification semantic enumeration library example display record is shown; Table 1: Key information field table of design modification semantic enumeration library example display record

[0028] Further, the user interface encapsulating the design modification semantic enumeration library and displaying it to the reviewer comprises: developing a user interface (UI) that presents the modified semantic enumeration library to a design reviewer; Each semantic is accompanied by a brief description or example picture on the UI to help users understand its meaning and applicable scenarios.

[0029] In this embodiment, tree structure, classification tags, search boxes, etc. can be used to facilitate users to quickly find the required design modification semantics. Each semantic may be accompanied by a brief description or example picture on the interface to help users understand its meaning and applicable scenarios. The interface design should be simple and clear, consistent with the usage habits of underground powerhouse designers.

[0030] Referring to Figure 2 , a schematic diagram of the user interface module, showing semantic selection, model binding, parameter input, etc.

[0031] Further, the reviewer selects a design modification semantic from the user interface based on the modification intent, and binds the design modification semantic with the elements of the modification intent model, further comprising: When the reviewer proposes a design modification, he / she browses or searches and selects one or more design modification semantics that best match his / her modification intent through the user interface; Using the model selection tool provided by the user interface, the selected semantics are associated with the specific components or component sets that need to be modified in the model, and the corresponding model ID is bound; The semantic ID selected by the reviewer and the model ID list bound are recorded.

[0032] In this embodiment, when the design reviewer (such as a mechanical and electrical professional engineer) needs to propose a design modification, he / she first browses or searches and selects one or more design modification semantics that best match his / her modification intent through the above-mentioned user interface. Then, using the model selection tool (such as picking, box selection, input ID, etc.) provided by the interface, the selected semantics are associated with the specific components or component sets that need to be modified in the model, i.e. the corresponding model ID is bound. The system records the semantic ID selected by the user and the model ID list bound.

[0033] Further, the elements of the modification intent model bound are located in the BIM model, and the current view information and the design modification semantic are fused to generate a BCF file, further comprising: According to 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 is obtained, including camera position, target point, view distance, view angle, etc. The standardized description of the design modification semantic selected by the user is fused with the model ID and view information; The fused information is organized according to the BCF file format specification to generate a BCF file, which contains standard view information, embedded structured design modification semantics and associated model IDs.

[0034] In this embodiment, the system automatically locates the components in the currently opened BIM model software (such as Revit) according to the user-bound model IDs, and obtains the current camera view information, including camera position, target point, view distance, view angle, etc. At the same time, the system fuses the standardized description of the user-selected design modification semantics (which may contain parameter placeholders, such as "modify the X coordinate of the component [model ID] to [to-be-input value]") with the model IDs and view information. The fused information is organized according to the BCF file format specification to generate a BCF file. The BCF file not only contains standard view information, but also embeds structured design modification semantics and associated model IDs, so that the BCF file is not only a communication carrier, but also a subsequent automatic modification instruction.

[0035] Referring to Figure 3 The structural diagram of the BCF file of the embodiment of the present application is shown, which shows the recorded key information fields.

[0036] Further, the uploading of the BCF file to the collaborative platform further includes: The generated BCF file is uploaded to the BIM collaborative platform used by the project; The collaborative platform pushes the BCF file to the subsequent design personnel who need to perform or review the modification according to the preset rules or designated recipients; The notification content of the push includes the basic information of the BCF file, including at least the title, the involved component type, ID, camera position, modification semantics, responsible person, modification time, version number.

[0037] Further, the collaborative platform parses the embedded structured design modification semantics and modification intent model from the BCF file and displays them to the design personnel, and further includes: The subsequent design personnel clicks to view the BCF file after receiving the notification on the collaborative platform; Parse the BCF file to identify the embedded structured design modification semantics and model IDs; According to the view information, automatically open the corresponding view in the local BIM model software and locate to the component to be modified.

[0038] In this embodiment, the interface can highlight these components and display the modification semantic description contained in the BCF file. The designer can intuitively see what needs to be modified, the location, and the reason for the modification. The designer reviews this and judges the rationality, feasibility, and impact on other specialties.

[0039] Further, 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 automatic modification, which further includes: If the designer reviews and confirms that the modification is reasonable, the approval operation is performed; After receiving the signal of approval, the automatic modification process is started; The design modification semantics and the bound model ID that pass the approval are parsed; The API of the BIM model software is called, and the corresponding modification command object is dynamically generated according to the specific meaning of the semantics.

[0040] In this embodiment, if the semantics is "modify the X coordinate of the component [model ID] to [value]", the system calls the method of moving the component or modifying the component parameter in the Revit API, and inputs 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 performs the design modification, avoiding errors and omissions in manual operation.

[0041] Further, the design modification history of the designer is used to update the BCF file for subsequent design modification and update tracing, which further includes: After the automatic modification is completed, the system updates the results of the modification, the timestamp of the modification, and the information of the performer back to the original BCF file; The updated BCF file retains the original modification instructions and view information, and adds the state and process record after the modification; The updated BCF file is uploaded or updated to the collaborative platform again to form a complete modification closed loop record; According to the need, the key parameters, reasons, involved model IDs, and perspective data in the modification process are saved in the form of an XML file as a trace log.

[0042] According to the second embodiment of the present application, the present application claims a design collaborative modification system based on semantic encapsulation and BCF file transmission, referring to Figure 4 , which includes: A semantic library management module for storing and managing a design modification semantic enumeration library and its code; A user interface module encapsulates the design modification semantics and provides an interactive interface for users to select semantics, bind model IDs, and input parameters; A BCF generation module generates a BCF file according to the semantics, model IDs, and view information; A collaborative platform interface module is responsible for uploading the BCF file to the collaborative platform and receiving the BCF file and approval signals from the collaborative platform; A BCF analysis and display module analyzes the received BCF file, identifies semantics, locates views and components in the model, and displays modification content for review; An automatic modification execution module receives approval signals, analyzes semantics, and calls BIM software APIs to execute automatic modifications; A modification record and update module updates BCF file content, records modification processes, and generates traceability logs; The design collaborative modification system based on semantic encapsulation and BCF file transmission is used to implement the design collaborative modification method based on semantic encapsulation and BCF file transmission.

[0043] The following is described with a specific embodiment: Mechanical and electrical engineers found in the design that due to the adjustment of equipment size, the base of a certain large pump group in the main plant needs to be moved 500mm in the positive direction of the X axis, and at least 300mm of spacing should be maintained with the adjacent cable bridge.

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

[0045] Interface encapsulation: Mechanical and electrical engineers find and select the "adjust component position" semantics in the UI, and use the pick tool to select the pump group base model to bind its model ID. Then, they may also need to select the "modify spatial relationship" semantics and bind the model IDs of the base and adjacent cable bridge.

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

[0047] Generate BCF: The system locates the base model, acquires the current view, and fuses the "Adjust component position (ID: semantic_001)" semantic, the "Modify spatial relationship (ID: semantic_002)" semantic, the relevant model ID, the movement parameter, the spacing parameter, and the view information to generate a BCF file. The text in the BCF file might be similar to: "Please move the pump base of model ID=12345 along the positive X-axis by 500mm, and ensure at least 300mm spacing with the cable bridge of model ID=67890." Upload and push: The BCF file is uploaded to the collaboration platform and pushed to the hydraulic professional engineer.

[0048] Identification and review: The hydraulic engineer opens the BCF, and the system automatically locates the pump base and the cable bridge, displaying the modification requirements and the view. The engineer checks whether the base conflicts with the structure beam, wall, etc. after moving, and whether the spacing requirement is reasonable. After confirming that there is no error, the engineer approves it.

[0049] Automatic modification: The system analyzes the approved semantics (movement, spacing check) and calls the Revit API. First, find the component of model ID=12345 and modify its position parameter (X coordinate + 500mm). Then, find the component of model ID=67890, check and possibly fine-tune its own or related component positions to meet the 300mm spacing requirement (this step may require more complex logic judgment).

[0050] Update and traceability: After the modification is completed, the BCF file is updated and records such as "Model ID=12345 has been moved to the new position, new coordinates (X, Y, Z), and the spacing with model ID=67890 has been confirmed to be 300mm, modification time: 2025-06-17 14:30, performer: system" are added. At the same time, related parameters and processes may be written into an XML log file.

[0051] In several embodiments provided in the present application, it should be understood that the disclosed system, device and method can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of units is only a logical function division, and actual implementation can have another division manner, for example, a plurality of units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the coupling or direct coupling or communication connection between the displayed or discussed units can be indirect coupling or communication connection through some interfaces, devices or units, which can be electrical, mechanical or other forms.

[0052] In addition, the various functional units in the embodiments of the present application can be integrated in one processing unit, or each can exist as an independent physical unit, or two or more than two of them can be integrated in one physical unit. The above-mentioned integrated unit can be implemented in the form of hardware, or in the form of a software functional unit. The above is only an embodiment of the present application, and does not limit the patent scope of the present application, and any equivalent structure or equivalent process transformation using the content of the present application specification and drawings, or direct or indirect application in other related technical fields, are also included in the patent protection scope of the present application.

[0053] The specific embodiments of the application are described in detail above, but they are only examples. The present application is not limited to the above-described specific embodiments. Any equivalent modification or substitution of the present application made by those skilled in the art is also within the scope of the present application, and therefore, equivalent transformation and modification, improvement, etc. made without departing from the spirit and principle range of the present application should be included in the scope of the present application.

Claims

1. A method for design collaboration modification based on semantic encapsulation and BCF file transfer, characterized in that, The method comprises the following steps: S1, constructing a modification semantic enumeration library for the design of a pumped storage power station underground powerhouse, encapsulating the modification semantic enumeration library by using a user interface, and displaying the modification semantic enumeration library to an examiner and converting the design modification semantics into high-order vectors by using a high-dimensional vector algorithm to form a vector library; S2, the examiner selects design modification semantics from the user interface based on a modification intention, and binds the design modification semantics to elements of a modification intention model; S3, when there is a lack of directly corresponding modification semantics, a large language model interface is called to analyze the similarity between the examiner semantics and the vectors in the modification semantic library, design modifications are recommended, the elements of the bound modification intention model are located in a BIM model, current view information and the design modification semantics are fused to generate a BIM file; S4, the BIM file is uploaded to a collaborative platform, the collaborative platform parses the BIM file to obtain embedded structured design modification semantics and a modification intention model, and displays the design modification semantics and the modification intention model to a designer; S5, the designer audits the design modification semantics and the modification intention model, calls a BIM software API, automatically converts the design modification semantics into corresponding modification program objects, and completes automatic modification; S6, the BIM file is updated based on the modification history of the designer, and is used for subsequent design modification and update tracing.

2. The method according to claim 1, wherein, The method for constructing the modification semantic enumeration library for the design of the pumped storage power station underground powerhouse further comprises the following steps: According to common scenes and requirements of the pumped storage power station underground powerhouse design, a plurality of design modification atomic operations or combined operations are summarized and refined to form a design modification semantic enumeration library; Each semantic of the semantic enumeration library is given a unique identifier ID and a standardized name and description; For complex modification scenes, combined semantics are defined, which are composed of a plurality of atomic semantics according to specific logic; The semantics and their codes are pre-defined and stored as the basis for subsequent steps.

3. The method of claim 1, wherein the method further comprises: The method for encapsulating the modification semantic enumeration library by using a user interface and displaying the modification semantic enumeration library to an examiner comprises the following steps: A user interface UI is developed, which presents the modification semantic enumeration library to a design examiner; Each semantic is accompanied by an explanation or an example picture on the user interface UI to help users understand its meaning and applicable scene.

4. The method of claim 1, wherein the method further comprises: The method for selecting design modification semantics by an examiner from the user interface based on a modification intention and binding the design modification semantics to elements of a modification intention model further comprises the following steps: When proposing a design modification, the examiner browses or searches for and selects one or more design modification semantics that are most consistent with the modification intention through the user interface; The selected semantics are associated with specific components or component sets that need to be modified in the model by using a model selection tool provided by the user interface, and the corresponding model IDs are bound; The semantic IDs selected by the examiner and the bound model ID list are recorded.

5. The method of claim 1, wherein the method further comprises: The method for locating the elements in a BIM model according to the bound modification intention model elements, fusing current view information and the design modification semantics to generate a BIM file further comprises the following steps: According to 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 is obtained, including camera position, target point, view distance, view angle, etc. The standardized description of the design modification semantics selected by the user is fused with the model ID and view information; The fused information is organized according to the BCF file format specification to generate a BCF file, which contains standard view information and embedded structured design modification semantics and associated model ID.

6. The method of claim 1, wherein the method further comprises: The BCF file is uploaded to the collaborative platform, which also includes: The generated BCF file is uploaded to the BIM collaborative platform used by the project; According to the preset rules or designated recipients, the BCF file is pushed to the next designer who needs to perform or review the modification; The notification content of the push includes the basic information of the BCF file, including at least the title, the component type involved, the ID, the modification semantics, the responsible person, the modification time, and the version number.

7. The method of claim 6, wherein the method further comprises: The collaborative platform parses the embedded structured design modification semantics and modification intent model from the BCF file and displays them to the designer, which also includes: The next designer clicks to view the BCF file after receiving the notification on the collaborative platform; Parse the BCF file to identify the embedded structured design modification semantics and model ID; According to the view information, automatically open the corresponding view in the local BIM model software and locate to the component that needs to be modified.

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, and automatically converts the design modification semantics into corresponding modification procedure objects to complete the automatic modification, which also includes: If the designer approves the modification, the modification is reasonable, and the approval operation is performed; After receiving the approval signal, the automatic modification process is started; Parse the design modification semantics and its bound model ID that have passed the approval; Call the API of the BIM model software to dynamically generate corresponding modification command objects according to the specific meaning of the semantics.

9. The method of claim 1, wherein the method further comprises: The BCF file is updated based on the modification history of the designer for subsequent design modification and update tracing, which also includes: After the automatic modification is completed, the system updates the modified results, timestamps, and executor information back to the original BCF file; The updated BCF file retains the original modification instructions and view information and adds the modified state and process record; The updated BCF file is uploaded or updated to the collaborative platform again to form a complete modification closed-loop record; According to the need, the key parameters, reasons, involved model IDs, and view angle data in the modification process are saved in the form of XML files as trace logs.

10. A system for design collaboration modification based on semantic encapsulation and BCF file transfer, characterized in that, It includes: A semantic library management module for storing and managing design modification semantic enumeration library and its code; A user interface module that encapsulates the design modification semantics and provides an interactive interface for users to select semantics, bind model IDs, and input parameters; A BCF generation module that generates a BCF file based on semantics, model ID, and view information; A collaborative platform interface module is responsible for uploading BCF files to the collaborative platform and receiving BCF files and approval signals from the collaborative platform; A BCF analysis and display module analyzes the received BCF files, identifies semantics, locates views and components in the model, and displays the modification content for review; An automatic modification execution module receives the approval signal, analyzes the semantics, and calls the BIM software API to execute the automatic modification; A modification record and update module updates the BCF file content, records the modification process, and generates a trace log; The design collaborative modification system based on semantic encapsulation and BCF file transmission is used to perform the design collaborative modification method based on semantic encapsulation and BCF file transmission as claimed in any one of claims 1-9.

Images