A method, device and electronic equipment for collaborative architectural design

Abstract

The present application discloses a method, device and electronic device for collaborative architectural design. The method is applied to a collaborative architectural design device, and the method includes: storing the latest version of project-level data in a sub-item tag; associating a work unit with the sub-item tag to which it belongs, so as to update the existing version of project-level data according to the latest version of project-level data through the work unit; when the project-level data in any work unit is modified, each work unit belonging to the same sub-item tag synchronously updates the modified project-level data. The technical solution provided by the present application enables synchronous update of project-level data.

Description

Technical Field

[0001] The present invention relates to the field of computer-aided design, and in particular to a method, device and electronic equipment for collaborative architectural design. Background Art

[0002] In related technologies, for example, the design work of construction projects such as residential areas is jointly designed by multiple designers. Designers of different professions design the content in their respective fields, and the design work of the same profession may also require multiple designers to design. During the design process, project-level data such as axis grids, elevations, and building coordinates also need to be continuously increased as the design progresses. Every time a few floors are designed, new project-level data such as axis grids and elevations need to be added. However, in reality, due to the joint design of multiple designers, there may be a situation where the project-level data is not unified, and once the project-level data in the design work of a certain designer is modified, the project-level data associated with it in other designs need to be modified synchronously, which brings a huge workload. Summary of the invention

[0003] In view of this, the embodiments of the present application provide a method, device and electronic device for collaborative building design, which can synchronize and update project-level data.

[0004] An embodiment of the present application provides a method for collaborative architectural design, which is applied to a collaborative architectural design device, and includes: storing the latest version of project-level data in a sub-item tag; associating a work unit with the sub-item tag to which it belongs, so as to update the existing version of the project-level data according to the latest version of the project-level data through the work unit; when the project-level data in any work unit is modified, each work unit belonging to the same sub-item tag synchronously updates the modified project-level data.

[0005] The technical solution provided by the present application, by storing the latest version of the project-level data in the sub-item tag, can synchronously update the existing project-level data in the work unit to the latest version of the project-level data in the sub-item tag after the work unit is associated with the sub-item tag. Even if the project-level data in a certain work unit is modified, the other work units that belong to the same sub-item tag as the work unit with the modified data can also synchronously update the modified project-level data. After the project-level data in a certain work unit is modified, the project-level data of other work units in the same sub-item tag will not be inconsistent. Therefore, the technical solution provided by the present application can synchronize the update of project-level data.

[0006] In one embodiment, when there is no project-level data in the sub-item tag, the method includes: creating project-level data in the work unit; the project-level data includes at least one of elevation, axis grid and positioning coordinates; uploading the created project-level data to the associated sub-item tag and serving as the latest version of the project-level data.

[0007] When there is no project-level data in a sub-item tag, create project-level data such as grids and elevations in a work unit and upload them to the sub-item tag associated with the work unit. This ensures that the latest version of the project-level data exists in the sub-item tag, so that the project-level data in other work units in the sub-item tag can be updated synchronously.

[0008] In one embodiment, the working unit updates the existing version of the project-level data according to the latest version of the project-level data, including: the working unit finds the latest version of the project-level data according to the associated sub-item tags; compares the existing version with the latest version; when the existing version is inconsistent with the latest version, updates the existing version of the project-level data according to the latest version of the project-level data.

[0009] By comparing the latest version in the sub-item tag with the version of the project-level data in the work unit, it can be found whether the two are the same version of the project-level data. When the two versions are different, it can be confirmed that the project-level data in the work unit needs to be updated, and the existing project-level data in the work unit is updated according to the latest version of the project-level data in the sub-item tag.

[0010] In one embodiment, permission to modify project-level data in a work unit is set; when permission is granted, the modified project-level data can be submitted; when permission is not granted, the modified project-level data cannot be submitted.

[0011] By setting permissions to modify project-level data in work units, you can ensure that only designated designers can modify project-level data, avoiding the situation where many designers modify the project-level data in their respective work units, resulting in inconsistent project-level data in the same architectural design project.

[0012] In one embodiment, each work unit belonging to the same sub-item tag synchronously updates the modified project-level data, including: uploading the modified project-level data to the corresponding sub-item tag in the cloud device, so as to update the modified project-level data to the associated work units through the sub-item tag.

[0013] By uploading the modified project-level data to the corresponding sub-item tag in the cloud device, it can be ensured that the project-level data in other work units associated with the modified work unit can be updated synchronously.

[0014] In one embodiment, the method further includes: receiving a data query request, and determining whether there is cache item-level data matching the data query request locally, and if so, feeding back the cache item-level data to the initiator of the data query request.

[0015] By querying the locally cached project-level data, it can be determined whether the locally cached project-level data is the latest version of the project-level data. If it is, it means that the locally cached project-level data is the latest version of the project-level data, which prevents designers from designing based on incorrect project-level data.

[0016] In one embodiment, the method further includes: when there is no cached item-level data matching the data query request, reading the corresponding item-level data from the sub-item tag in the cloud device, and providing the read item-level data to the initiator of the data query request.

[0017] Through the query request, it is determined whether the locally cached project-level data is the correct project-level data. If it does not exist, it means that the locally cached project-level data is not the latest version of the project-level data, that is, the locally cached project-level data is not the correct project-level data. The work unit of the request initiator obtains the corresponding project-level data, that is, the latest version of the project-level data, from the cloud device.

[0018] One embodiment of the present application further provides a building collaborative design device, the device comprising:

[0019] A latest version data storage unit is used to store the latest version of project-level data in a sub-item tag; a data update unit is used to associate a work unit with the sub-item tag to which it belongs, so as to update the existing version of the project-level data according to the latest version of the project-level data through the work unit; a data modification unit is used to synchronously update the modified project-level data in each work unit belonging to the same sub-item tag when the project-level data in any work unit is modified.

[0020] An embodiment of the present application provides an electronic device, which includes a memory and a processor, wherein the memory is used to store a computer program, and when the computer program is executed by the processor, the above-mentioned architectural collaborative design method is implemented.

[0021] One embodiment of the present application provides a computer-readable storage medium, wherein the computer-readable storage medium is used to store a computer program. When the computer program is executed by a processor, the above-mentioned architectural collaborative design method is implemented. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] The features and advantages of the present application will be more clearly understood by referring to the accompanying drawings, which are schematic and should not be construed as limiting the present application in any way. In the accompanying drawings:

[0023] Figure 1 A schematic diagram showing the steps of a building collaborative design method in one embodiment of the present application is shown;

[0024] Figure 2 A schematic diagram of functional modules of a building collaborative design device in one embodiment of the present application is shown;

[0025] Figure 3 A schematic structural diagram of an electronic device in one embodiment of the present application is shown. DETAILED DESCRIPTION

[0026] In order to make the purpose, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application are clearly and completely described below. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative work are within the scope of protection of the present application.

[0027] like Figure 1 As shown, one embodiment of the present application provides a method for collaborative architectural design, which includes the following steps.

[0028] S1: Stores the latest version of item-level data in sub-item tags.

[0029] When designers design a construction project, they first create a sub-item tag in the cloud device. The sub-item tag is a mark determined according to the business division rules of the construction project. For example, a large residential area usually has Building 1, Building 2 to Building 10, etc. Design institutes and other design departments will define the same building as a sub-item. For example, Building 1 and Building 3 are exactly the same, so they can be set as a sub-item "1". All design information attached to this sub-item belongs to this sub-item. The sub-item tag is similar to a folder, for example, the sub-item tag is named "Building 1". In order to update the project-level data of each work unit belonging to the same sub-item tag, the latest version of the project-level data needs to be saved to the sub-item tag in the cloud device. Using cloud devices to store the latest version of project-level data facilitates synchronous updates.

[0030] S3: Associating the work unit with the corresponding sub-item tag, so as to update the existing version of the project-level data according to the latest version of the project-level data through the work unit.

[0031] By associating the work unit with the sub-item tag to which it belongs, the corresponding relationship between each work unit and the sub-item tag can be found. Even if there are many work units, it is possible to determine which work units belong to the same sub-item tag. This also facilitates the unification of project-level data belonging to the same sub-item tag when the project-level data is updated. The design work of designers is carried out in the work unit, which can be regarded as a local editing area, but the drawings or annotations drawn by designers in the local work unit are stored in the cloud. The existing project-level data in the work unit is updated according to the latest version of the project-level data to ensure that the project-level data used for the design work in the work unit is the latest, avoiding errors in the design work based on the project-level data due to the failure to update the project-level data in a timely manner, thereby improving the work efficiency of many people in the design process.

[0032] In practice, project-level data such as elevations, grids, and coordinates play a vital role in architectural design, and the project-level data in the same sub-item, such as the same building, are the same. After creating project-level data such as elevations, grids, and coordinates in a work unit, designers can design buildings based on these project-level data. For example, design individual building components such as walls or columns on the grid.

[0033] In one embodiment, when the project-level data does not exist in the sub-item tag, the method includes: creating project-level data in the work unit; the project-level data includes at least one of elevation, axis grid and positioning coordinates; uploading the created project-level data to the associated sub-item tag and serving as the latest version of the project-level data.

[0034] In practice, when there is no project-level data in the sub-item tag in the cloud device, project-level data such as axis grids, elevations, and coordinates are created in the work unit and uploaded to the sub-item tag associated with the work unit, and the project-level data uploaded to the sub-item tag is used as the latest version of the project-level data. Among them, the elevation is the height of each floor during the design process, and the coordinates include the project origin coordinates and the sub-item coordinates. The project origin coordinates refer to the coordinate origin in the work unit of the general plan sub-item, which is the project base point of the entire construction project. The sub-item coordinates refer to the coordinate origin of each sub-item (single building such as Building 1), which clearly marks the actual coordinate position of each single building in the general plan. In order to ensure that the designed building is within the prescribed land use scope, the project origin coordinates and sub-item coordinates can be associated with the municipal surveying and mapping coordinates.

[0035] In one embodiment, the working unit updates the existing version of the project-level data according to the latest version of the project-level data, including: the working unit finds the latest version of the project-level data according to the associated sub-item tag, compares the existing version with the latest version, and updates the existing version of the project-level data according to the latest version of the project-level data when the existing version is inconsistent with the latest version.

[0036] When updating existing project-level data, the latest version of the project-level data is found in the sub-item tag associated with the work unit to be updated, and the version of the latest version of the project-level data is compared with the version of the existing version of the project-level data in the work unit to be updated. When the two versions are different, the existing project-level data, such as V1.5, is updated to project-level data consistent with the latest version based on the latest version of the project-level data, such as v2.0.

[0037] In actual use, after running the relevant program products in computers and other devices, when it is detected that the version of the existing version of the project-level data in the work unit is inconsistent with the version of the latest version of the project-level data, a message notification will be automatically sent to notify the user of the designer to update the project-level data in the work unit performing the architectural design operation. When the user confirms the update, the existing project-level data in the work unit will be automatically updated to the latest version of the project-level data.

[0038] In one embodiment, the supervision of project-level data is achieved by setting permissions to modify project-level data in a work unit. In actual use, only a few accounts are given permissions to modify project-level data to ensure that project-level data will not be modified at will, resulting in incorrect final project-level data. When permissions are granted, the modified project-level data can be submitted. When permissions are not granted, the modified project-level data cannot be submitted, that is, even if the user of the account modifies the project-level data in his or her work unit, the modified project-level data cannot be uploaded to the cloud device because it cannot be submitted, and the other work units associated with the work unit will not perform synchronous updates of project-level data. When permissions are not granted, the user of the account can only update the project-level data in the work unit according to the latest version of the project-level data stored in the sub-item tag in the cloud device.

[0039] In actual architectural design, design institutes and other design departments generally only need a few designers to create or modify the project-level data in the entire architectural design, to ensure that the project-level data in the design is not frequently modified due to everyone's modification, and to ensure the accuracy of the project-level data. Generally, the account of the designer who creates or modifies the project-level data is configured with the permission to create and modify the project-level data. Designers who do not have the permission only need to be responsible for their own design work in the work unit where the project-level data is updated.

[0040] S5: When the item-level data in any work unit is modified, each work unit belonging to the same sub-item tag synchronously updates the modified item-level data.

[0041] During the architectural design process, when the project-level data in any work unit is modified, that is, when a designer with modification authority modifies the project-level data in the work unit, the project-level data of other work units belonging to the same sub-item tag as the modified work unit are also synchronously updated to the modified project-level data, so that, for example, the project-level data of all designers designing the same building during the design process are unified.

[0042] In one embodiment, the modified project-level data is synchronously updated for each work unit belonging to the same sub-item tag, including: uploading the modified project-level data to the corresponding sub-item tag in the cloud device, so as to update the modified project-level data to the associated work units through the sub-item tag.

[0043] In practice, after the designer who is responsible for the creation and modification of project data uses his account to modify and submit the project-level data such as the axis grid and elevation in the work unit, the computer device or cloud device will upload the modified project-level data to the corresponding sub-item tag in the cloud device, find the sub-item tag to which the modified work unit belongs through the correspondence or application relationship between the modified work unit and the sub-item tag, and update the latest version of the project-level data stored in the found sub-item tag to the modified project-level data, and use the modified project-level data in the sub-item tag as the latest version of the project-level data and name the version, such as version 3.0. When the latest version of the project-level data in the sub-item tag in the cloud device is changed, the program will search for other work units that belong to the same sub-item tag as the work unit of the modified project-level data, and send notifications to each work unit that belongs to the same sub-item tag to update the project-level data, so that the modified project-level data is updated to each associated work unit. If a designer who is doing design work in a certain work unit does not update the project-level data in the work unit he is designing after receiving the notification of updating the project-level data, the design data such as the drawings or annotations he designed cannot be submitted, so that after the project-level data is modified, the project-level data in all related work units are synchronously updated to the same project-level data.

[0044] In one embodiment, the method further includes: receiving a data query request, and determining whether there is cached item-level data matching the data query request locally, and if so, feeding back the cached item-level data to the initiator of the data query request. When there is no cached item-level data matching the data query request, reading the corresponding item-level data from the sub-item tag in the cloud device, and providing the read item-level data to the initiator of the data query request.

[0045] In practice, for example, a designer who uses a certain work unit to perform design work does not know whether the correct project-level data is cached locally, and the designer initiates a data query request locally. After receiving the data query request, the cloud server determines whether there is matching cached project-level data in its local cache through the cached project-level data uploaded by the initiator. If so, the cached project-level data is returned to the initiator of the data query request, that is, the work unit used by the designer. When there is no cached project-level data that matches the data query request, that is, the local cached project-level data of the data requester is not the latest version of the project-level data, the corresponding project-level data is read from the sub-item tag in the cloud device, and the read project-level data is provided to the initiator of the data query request, so that the designer of the request initiator can update the project-level data in the work unit to the correct project-level data, so as to avoid designing based on incorrect project-level data.

[0046] The technical solution provided by the present application, by storing the latest version of the project-level data in the sub-item tag, can synchronously update the existing project-level data in the work unit to the latest version of the project-level data in the sub-item tag after the work unit is associated with the sub-item tag. Even if the project-level data in a certain work unit is modified, the other work units that belong to the same sub-item tag as the work unit with the modified data can also synchronously update the modified project-level data. After the project-level data in a certain work unit is modified, the project-level data of other work units in the same sub-item tag will not be inconsistent. Therefore, the technical solution provided by the present application can synchronize the update of project-level data.

[0047] like Figure 2 As shown, one embodiment of the present application further provides a building collaborative design device, the device comprising:

[0048] The latest version data storage unit is used to store the latest version of the project-level data in the sub-item tag;

[0049] A data updating unit, used for associating a work unit with the sub-item tag to which it belongs, so as to update the existing version of the project-level data according to the latest version of the project-level data through the work unit;

[0050] The data modification unit is used to synchronize the modified project-level data of each work unit belonging to the same sub-item tag when the project-level data in any work unit is modified.

[0051] like Figure 3As shown, one embodiment of the present application provides an electronic device, which includes a memory and a processor, wherein the memory is used to store a computer program, and when the computer program is executed by the processor, the above-mentioned architectural collaborative design method is implemented.

[0052] One embodiment of the present application provides a computer-readable storage medium, wherein the computer-readable storage medium is used to store a computer program. When the computer program is executed by a processor, the method for intelligently identifying entity information in the above-mentioned real estate drawings is implemented.

[0053] The processor may be a central processing unit (CPU). The processor may also be other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or a combination of the above chips.

[0054] As a non-transitory computer-readable storage medium, the memory can be used to store non-transitory software programs, non-transitory computer executable programs and modules, such as program instructions / modules corresponding to the method in the embodiment of the present invention. The processor executes various functional applications and data processing of the processor by running the non-transitory software programs, instructions and modules stored in the memory, that is, implementing the method in the above method embodiment.

[0055] The memory may include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application required for at least one function; the data storage area may store data created by the processor, etc. In addition, the memory may include a high-speed random access memory, and may also include a non-transitory memory, such as at least one disk storage device, a flash memory device, or other non-transitory solid-state storage device. In some embodiments, the memory may optionally include a memory remotely disposed relative to the processor, and these remote memories may be connected to the processor via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0056] Those skilled in the art can understand that all or part of the processes in the above-mentioned implementation methods can be implemented by instructing related hardware through a computer program, and the program can be stored in a computer-readable storage medium. When the program is executed, it can include the processes of the implementation methods of the above-mentioned methods. Among them, the storage medium can be a disk, an optical disk, a read-only memory (ROM), a random access memory (RAM), a flash memory, a hard disk (HDD) or a solid-state drive (SSD), etc.; the storage medium can also include a combination of the above-mentioned types of memory.

[0057] Although the embodiments of the present application have been described in conjunction with the accompanying drawings, those skilled in the art may make various modifications and variations without departing from the spirit and scope of the present application, and such modifications and variations are all within the scope defined by the appended claims.

Claims

1. A method for collaborative architectural design, the method being applied to a collaborative architectural design device, characterized in that: The method comprises: Store the latest version of item-level data in sub-item tags; Associating a work unit with the sub-item tag to which it belongs, so as to update the existing version of the project-level data according to the latest version of the project-level data through the work unit; When the item-level data in any work unit is modified, each work unit belonging to the same sub-item tag will synchronously update the modified item-level data.

2. The method according to claim 1, characterized in that When there is no item-level data in the sub-item tag, the method includes: Creating project-level data in a work unit; the project-level data includes at least one of elevation, axis grid and positioning coordinates; The created project-level data is uploaded to the associated sub-item tag and serves as the latest version of the project-level data.

3. The method according to claim 2, characterized in that The working unit updates the existing version of the project-level data according to the latest version of the project-level data, including: The working unit finds the latest version of the project-level data according to the associated sub-item tag; Compare the existing version with the latest version; When the existing version is inconsistent with the latest version, the project-level data of the existing version is updated according to the project-level data of the latest version.

4. The method according to claim 1, characterized in that: Set permissions to modify project-level data in a work unit; Modified project-level data can be submitted when permission is granted; If you do not have the permission, the modified project-level data cannot be submitted.

5. The method according to claim 1, characterized in that Each work unit belonging to the same sub-item tag synchronously updates the modified project-level data, including: The modified project-level data is uploaded to the corresponding sub-item tag in the cloud device, so as to update the modified project-level data to each associated work unit through the sub-item tag.

6. The method according to claim 1, characterized in that The method further comprises: A data query request is received, and it is determined whether there is cache item-level data matching the data query request locally; if so, the cache item-level data is fed back to the initiator of the data query request.

7. The method according to claim 6, characterized in that The method further comprises: When there is no cached item-level data matching the data query request, the corresponding item-level data is read from the sub-item tag in the cloud device, and the read item-level data is provided to the initiator of the data query request.

8. A building collaborative design device, characterized in that: The device comprises: The latest version data storage unit is used to store the latest version of the project-level data in the sub-item tag; A data updating unit, used for associating a work unit with the sub-item tag to which it belongs, so as to update the existing version of the project-level data according to the latest version of the project-level data through the work unit; The data modification unit is used to synchronize the modified project-level data of each work unit belonging to the same sub-item tag when the project-level data in any work unit is modified.

9. An electronic device, characterized in that: The electronic device comprises a memory and a processor, wherein the memory is used to store a computer program, and when the computer program is executed by the processor, the method according to any one of claims 1 to 7 is implemented.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium is used to store a computer program, and when the computer program is executed by a processor, the method according to any one of claims 1 to 7 is implemented.

Images