CN113919041A

CN113919041A - Collaborative design method and electronic equipment

Info

Publication number: CN113919041A
Application number: CN202111349266.3A
Authority: CN
Inventors: 张媛琦; 张乃文; 孙中奎; 陈鹏宇; 罗太燕
Original assignee: Glodon Co Ltd
Current assignee: Glodon Co Ltd
Priority date: 2021-11-15
Filing date: 2021-11-15
Publication date: 2022-01-11
Anticipated expiration: 2041-11-15
Also published as: CN113919041B

Abstract

The invention relates to the technical field of design computer aided design, in particular to a collaborative design method and electronic equipment, wherein the method comprises the steps of obtaining a target working unit; responding to the cooperative design of the target component in the target working unit, and sending a cooperative design request to a server to determine whether the target component is locked; when the target component is unlocked, acquiring the associated component of the target component determined by the server based on the collaborative design request; and loading the associated component, performing associated design on the associated component, and determining a collaborative design result. The collaborative design method based on the component level breaks through the gap between the files from the collaborative design, reduces the collaborative granularity to the component level, and is convenient for sharing the design result in real time; by determining the locking condition of the target component, the permission approval process in the cooperative working process can be reduced, and the usability is improved.

Description

Collaborative design method and electronic equipment

Technical Field

The invention relates to the technical field of computer aided design, in particular to a collaborative design method and electronic equipment.

Background

A relatively large number of related specialties are involved in a complete building design project, with the most common specialties including building, construction, plumbing, heating, and electrical. In some complex projects, even some design specialties exist, efficient work output and accuracy of upstream and downstream information transmission need to be achieved among the same project among such multiple specialties, and a work mode which can help designers to design in a multi-person cooperation mode under the project is needed.

Currently, the existing collaborative design software has roughly the following three operating modes: (1) a collaboration mode based on a central file, which mode is a stuck problem in case of large files; (2) in a project multi-person cooperation mode, respective design content needs to be divided in advance; (3) layers are set and users are specified, but model scaling performance has a great influence in large model processing.

Disclosure of Invention

In view of this, embodiments of the present invention provide a collaborative design method, apparatus and electronic device to solve the problem of collaborative design of a model.

According to a first aspect, an embodiment of the present invention provides a collaborative design method, which is applied to a design end, and the method includes:

acquiring a target working unit;

responding to the cooperative design of the target component in the target working unit, and sending a cooperative design request to a server to determine whether the target component is locked;

when the target component is unlocked, acquiring the associated component of the target component determined by the server based on the collaborative design request;

and loading the associated component, performing associated design on the associated component, and determining a collaborative design result.

According to the collaborative design method provided by the embodiment of the invention, only the target working unit is needed to be targeted during collaborative design, and a complete target model is not needed to be loaded, so that the real-time performance of data interaction is ensured; the collaborative design method based on the component level breaks through the gap between the files in the collaborative design, and lowers the collaborative granularity to the component level, so that the connection between the data and the data is not limited in a certain file any more, the real-time sharing of the design result is facilitated, and the related components are also subjected to related design in the collaborative design process, thereby realizing the synchronous update and improving the collaborative design efficiency; by determining the locking condition of the target component, the permission approval process in the cooperative working process can be reduced, and the usability is improved.

With reference to the first aspect, in a first implementation manner of the first aspect, the obtaining a target work unit includes:

displaying a working unit selection interface;

responding to the selection operation of the working unit selection interface, and determining a current working unit and a reference working unit of the current working unit;

and loading the current working unit and the reference working unit, and determining the target working unit.

According to the collaborative design method provided by the embodiment of the invention, the association relationship also exists between the working units, namely the relationship between the reference working unit and the referred working unit, and the corresponding reference working unit is loaded at the same time when the current working unit is loaded, so that the reliability of collaborative design can be ensured while the downloading of a complete model is avoided.

With reference to the first implementation manner of the first aspect, in a second implementation manner of the first aspect, the loading the current work unit and the reference work unit, and determining the target work unit includes:

judging whether the current working unit or the reference working unit is cached locally;

and when the current working unit or the reference working unit is not cached locally, loading the current working unit or the reference working unit from the server to determine the target working unit.

According to the collaborative design method provided by the embodiment of the invention, when the target working unit is loaded, the target working unit is loaded from the cache firstly, namely, the intermediate modeling result is retained, so that the data downloading process when the target working unit is loaded again from the server can be avoided, and the efficiency of collaborative design is improved.

With reference to the first aspect, in a third implementation manner of the first aspect, the loading the association component and performing association design on the association component, and determining a co-design result includes:

acquiring current collaborative design results of the target component and the associated component;

comparing the current collaborative design result with a corresponding historical collaborative design result to determine an incremental design result;

and storing the incremental design result so as to upload the incremental design result to the server under a preset condition.

According to the collaborative design method provided by the embodiment of the invention, the collaborative design result is submitted in an increment mode, namely, only part of changed components are submitted, so that the efficiency of data submission and storage is accelerated.

With reference to the third implementation manner of the first aspect, in a fourth implementation manner of the first aspect, the storing the incremental design result to be uploaded to the server under a preset condition includes:

updating the version numbers of the target component and the working units corresponding to the associated components;

and storing the version number so as to upload the version number to the server under a preset condition.

According to the collaborative design method provided by the embodiment of the invention, when the component is updated, only the version number of the working unit corresponding to the component is updated, and the working unit of the server is not modified, so that the stability of the reference working unit of other design ends can be ensured, and meanwhile, the historical snapshot can be obtained through the version number.

According to a second aspect, an embodiment of the present invention provides a collaborative design method, which is applied to a server, and the method includes:

receiving a collaborative design request of a target component sent by a design end;

determining whether the co-design of the target member is locked based on the co-design request;

when the collaborative design of the target component is unlocked, inquiring related components related to the target component based on the association relationship among the components;

and issuing the associated component so that the design end performs associated design on the associated component to determine a collaborative design result.

The collaborative design method provided by the embodiment of the invention is based on a component-level collaborative design method, breaks through the gap between files in collaborative design, and reduces the collaborative granularity to a component level, so that the connection between data and data is not limited in a certain file any more, the design result is convenient to share in real time, and the associated components are also subjected to associated design in the collaborative design process, thereby realizing synchronous update and improving the collaborative design efficiency; by determining the locking condition of the target component, the permission approval process in the cooperative working process can be reduced, and the usability is improved.

With reference to the second aspect, in a first embodiment of the second aspect, the method further comprises:

receiving a selection request of a current working unit sent by the design end, and determining the current working unit;

inquiring a reference working unit corresponding to the current working unit according to the incidence relation of the working units;

and issuing the current working unit and the reference working unit to the design end.

With reference to the second aspect, in a second embodiment of the second aspect, the method further comprises:

receiving an increment design result uploaded by the design end;

and determining a corresponding storage database based on the incremental design result so as to store the incremental design result.

According to the collaborative design method provided by the embodiment of the invention, the incremental design result is stored in the corresponding storage database, so that the advantages of different types of storage databases are brought into play, and the storage efficiency is ensured.

According to a third aspect, an embodiment of the present invention further provides an electronic device, including:

a memory and a processor, the memory and the processor being communicatively connected to each other, the memory storing therein computer instructions, and the processor executing the computer instructions to perform the co-design method according to the first aspect of the present invention or any of the embodiments of the second aspect of the present invention.

According to a fourth aspect, the present invention provides a computer-readable storage medium, where the computer-readable storage medium stores computer instructions for causing a computer to execute the first aspect of the present invention, or any implementation manner of the first aspect, or the co-design method described in the second aspect of the present invention, or any implementation manner of the second aspect.

According to a fifth aspect, an embodiment of the present invention further provides a collaborative design system, including:

at least one design end for performing the co-design method of the first aspect of the present invention, or any embodiment of the first aspect;

and a server, to which the at least one design end is connected, and which is configured to execute the co-design method according to the second aspect of the present invention or any embodiment of the second aspect.

For the beneficial effects of the electronic device, the computer-readable storage medium and the collaborative design system in the embodiment of the present invention, please refer to the corresponding description in the collaborative design method above, which is not described herein again.

Drawings

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are some embodiments of the present invention, and other drawings can be obtained by those skilled in the art without creative efforts.

FIG. 1 is a schematic structural diagram of a co-design system according to an embodiment of the invention;

FIG. 2 is a schematic structural diagram of an electronic device according to an embodiment of the invention;

FIG. 3 is a schematic diagram of a design architecture of a co-design system according to an embodiment of the invention;

FIG. 4 is a schematic diagram of a data exchange scheme of a co-design system according to an embodiment of the invention;

FIG. 5 is a flow chart of a co-design method according to an embodiment of the invention;

FIG. 6 is a flow chart of a co-design method according to an embodiment of the invention;

FIG. 7 is a flow chart of a co-design method according to an embodiment of the invention;

FIG. 8 is a flow chart of a co-design method according to an embodiment of the invention;

FIG. 9 is a schematic diagram of a distributed storage architecture according to an embodiment of the present invention;

FIG. 10 is a block diagram of a co-design apparatus according to an embodiment of the present invention;

fig. 11 is a block diagram of a co-design apparatus according to an embodiment of the present invention.

Detailed Description

In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, but not all, embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

An embodiment of the present invention provides a collaborative design system, as shown in fig. 1, the system includes at least one design end 10 and a service end 20, and the at least one design end 10 is connected with the service end 20. The design end is used for collaborative design based on component level, and the service end 20 is used for responding to the collaborative design of the design end and storing the result of the collaborative design to ensure that the versions of the working units adopted by the design ends are uniform. The number of the design terminals 10 connected to the service terminal 20 may be set according to actual requirements, and is not limited herein.

The specific functions of the design end 10 and the service end 20 will be described in detail below.

The collaborative design system provided by this embodiment provides a design mode based on component-level multi-user collaboration under the BIM project, and analyzes data from a file document through component-level collaboration, so as to solve the problem of data black holes, and truly circulate and associate the design data of designers in the project, thereby realizing truly seamless collaboration, and enabling designers to share the design data in the project and mutually refer to and collaborate. The component-level collaboration is that under one BIM project, the use permission of a single or a plurality of components can be obtained, and design data of other people under the project can be loaded locally according to needs and kept updated in a related mode, so that the purpose of multi-person collaboration under the project is achieved.

Further, the design end 10 and the service end 20 may be collectively referred to as an electronic device, and fig. 2 is a schematic structural diagram of an electronic device according to an alternative embodiment of the present invention, as shown in fig. 2, the electronic device may include: at least one processor 201, such as a CPU (Central Processing Unit), at least one communication interface 203, memory 204, and at least one communication bus 202. Wherein a communication bus 202 is used to enable the connection communication between these components. The communication interface 203 may include a Display (Display) and a Keyboard (Keyboard), and the optional communication interface 203 may also include a standard wired interface and a standard wireless interface. The Memory 204 may be a high-speed RAM (Random Access Memory) or a non-volatile Memory (non-volatile Memory), such as at least one disk Memory. The memory 204 may optionally be at least one storage device located remotely from the processor 201. Wherein an application program is stored in the memory 204 and the processor 201 invokes the program code stored in the memory 204 for performing any of the above-mentioned method steps.

The communication bus 202 may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus. The communication bus 202 may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown in FIG. 2, but it is not intended that there be only one bus or one type of bus.

The memory 204 may include a volatile memory (RAM), such as a random-access memory (RAM); the memory may also include a non-volatile memory (english: non-volatile memory), such as a flash memory (english: flash memory), a hard disk (english: hard disk drive, abbreviated: HDD) or a solid-state drive (english: SSD); memory 204 may also comprise a combination of the above types of memory.

The processor 201 may be a Central Processing Unit (CPU), a Network Processor (NP), or a combination of a CPU and an NP.

The processor 201 may further include a hardware chip. The hardware chip may be an application-specific integrated circuit (ASIC), a Programmable Logic Device (PLD), or a combination thereof. The PLD may be a Complex Programmable Logic Device (CPLD), a field-programmable gate array (FPGA), a General Array Logic (GAL), or any combination thereof.

Optionally, memory 204 is also used to store program instructions. The processor 201 may invoke program instructions to implement the co-design method as shown in any of the embodiments of the present application.

As described above, the collaborative design system in the embodiment of the present invention includes a design end and a service end, and the service end is deployed in a cloud end, so that the collaborative design system is an end + cloud platform in terms of design architecture. As shown in fig. 3, the server can be divided into 3 layers, i.e. API layer, application layer and data storage layer.

Specifically, the data storage layer expresses a storage structure of cloud data, and the data is stored through various relational tables of a database. For example, a component data table is used to store component data, including: component id, component version, component geometry data, component properties, etc. The work unit table is used for storing work unit data and comprises the following components: work unit id, work unit version, component list, etc.

The application layer comprises a right control module, a cooperation module and a data model, wherein data rights in the right control module are mainly designed aiming at data safety, and whether the data under different scenes are allowed to be accessed or not is defined inside the right control module. The cooperation module effectively controls the order of data modification and data access through a component cooperation lock and a message mechanism, and is also responsible for solving the conflict caused by modifying component data simultaneously. The data model is docked with a data storage structure and manages a memory model of data, comprising: core data objects such as items, building blocks, work units, sub-items, version management, building block relationships, and solicited searches.

The API layer provides data model storage and cooperation capacity through the data model and the calling interface related to the cooperation model, embodies usability and ensures compatibility.

For the design end, it may be a producer of the cooperative data, and may also be a consumer of the cooperative data, which mainly implements its business logic through the data storage and cooperative capability provided by the AP layer. The functions can be divided into design tools, Web platforms, collision detection and the like, wherein the design tools complete complex design through data cooperation and upload design data to the platforms. The Web platform presents 3D scenes and manages engineering data through collaborative data. Collision detection is a typical third party application based on collaborative data, which analyzes whether a component will generate a collision in 3D space by using a collision detection algorithm.

The collaborative design system needs a cloud and related end components to complete a design mode of a multi-user system, and key components of the cloud comprise an authority control center, a message center, component relation search, component attribute search, project level data management and work unit management. Specifically, the authority control center component is responsible for managing the authority of the components in the project, and the user can only apply for the authority of the components to perform further editing or deleting operation. The centralized control of the authority control center ensures that at most one person applies for the modification authority of the component in the project. And after the user finishes the modification, submitting the modified file and releasing the authority.

The message center component is responsible for receiving messages of a design end and carrying out unicast or broadcast according to different message properties; and pushing the state change of the server side, which needs to be sensed by the user. Among the typical messages are: in the cooperation process, a certain design end pushes model modification data, and other design ends can receive model updating information; if the terminal 1 returns the authority of the component, the owner receives the returned message; an administrator or a certain design end modifies the project level configuration, and after the project level configuration is pushed to the cloud end, the server end broadcasts messages to all the design ends.

The message center component is also responsible for managing message circulation states, for example, some design ends are not online when sending messages, and the cloud end is responsible for supplementing the messages generated in the middle to the design ends when the design ends are online next time.

The component relationship search component is responsible for providing an engine for fast searches based on component relationships. The members are nodes, the relationship among the members is edges, and the whole relationship forms a large graph formed by a plurality of non-communicated directed graphs and is stored in the cloud. The component provides services of inquiring whether the relation between the objects exists or not, inquiring nodes related to a certain node and the like; and when the relationship between the components is changed, the relationship can be quickly reestablished.

And the component attribute searching component is responsible for providing services for querying the components meeting the conditions according to certain attributes. These key, generic attributes include, but are not limited to, the id of the component, the unit of work to which it belongs, the class of components, and so forth.

An item level data management component whose responsibility is to manage the common configuration of the item level. These configurations need to be set at project initialization to reference these data when subsequently building a unit of work, or to be loaded into a co-unit of work for use. In response to modification requirements, modification of project level data requires special permissions, and the system is designed so that not every member participating in a project has a permission. Meanwhile, the modifications should be effected within the scope of the project, and the work units on the end should update local references or data as appropriate according to the cloud project configuration data. It is therefore also necessary to set the version of project level data and, according to its intrinsic meaning, the version for all the work units should be the same at the same time in the project. Typically configured with elevations, axle nets, locator sub-items, etc.

A work unit management component, which exists for the purpose of storing and managing relationships between work units outside the component. Between the units of work there are referenced and referenced relationships, and these relationships may also be nested. For example, one work unit may refer to a plurality of other work units, and the next time the user opens the work unit, the referenced work unit is opened at the same time. Each time the user submits, the version of the work unit is increased, and the version has the functions of 1) keeping the reference stable; 2) and acquiring a history snapshot. For example, both the design end a and the design end B refer to the working unit C, and if the working unit C is modified at the design end a, the version number of the working unit C is changed at this time; however, for the design end B, the original working unit C is still maintained during display, and when the design end B needs to modify the working unit C, the working unit C is updated with the version number, so that stability of reference of all the design ends is ensured.

For the design end, the pipe fitting assembly comprises a modeling engine, a cache and data conversion transmission. The modeling engine component is responsible for completing the loading of the working units, the display and the editing of the components, and is a main generation source and a user of design data. The cache component is used for storing the components needing to be submitted next time after modification, and after the interruption and the edition are carried out on the terminal, the working unit is firstly opened next time to load the process model from the cache, so that the intermediate modeling result of the user is reserved, and the data downloading process when the components are loaded again from the cloud is avoided. And the data conversion and transmission component is responsible for converting the model data generated by the modeling engine into a format capable of being stored and transmitted, and uploading the model data to a cloud terminal when the on-terminal calculation and network resources are idle, or waiting for successful uploading in a synchronous mode. When the model is loaded, if the data is not in the local cache, the data is downloaded from the cloud, and is put into the cache after being converted into a format for the modeling engine to use. These formats ensure that the different design ends can be identified with each other, and the modeling tools on the design ends may be of the same or different specialties.

To further illustrate the above described co-design system, it is further described below in connection with a data exchange scheme. For example, FIG. 4 shows an alternative data exchange diagram of a co-design system. The implementation architecture can be divided into five layers: the system comprises a product platform or tool layer, a modeling platform layer, a collaboration platform conversion layer, a collaboration platform SDK layer and a data collaboration platform. The product platform or the tool layer is mainly responsible for production data, the modeling platform layer is responsible for management data, the collaboration platform conversion layer is responsible for conversion among data, the collaboration platform SDK layer is responsible for data caching and data transmission, and the data collaboration platform is responsible for data processing and data storage.

1) And (3) data uploading: after BIM model data generated by a product platform or a tool end are converted into formatted data required by a data platform through a cooperative platform converter mechanism, the formatted data are transmitted to a data cooperative platform through a cooperative platform SDK, and cloud data storage is performed after the BIM data are acquired by the data cooperative platform. In order to realize the acceleration effect, a data caching mechanism is established at a design end, changed data is cached to the local in an increment mode, and the data is uploaded to a collaborative data platform in the increment mode.

2) Data downloading: after the design end initiates and obtains the BIM data through the API, data are extracted from a cloud database according to mechanisms such as collaborative platform data management and the like, the data are transmitted to the design end through a network, then formatted data of the data collaborative platform flow back to form BIM model data which can be identified by the modeling platform through a converter mechanism of the collaborative platform, finally the data are added into the modeling platform model layer, and the design end manages the data mechanism through the modeling platform to achieve the data identification capability.

3) The authority mechanism is as follows: in the cooperative operation mode, in order to prevent data collision, modification of data is solved by a permission scheme. And when the component acquires the modification lock authority, allowing modification, otherwise, not allowing modification. Before data is modified, a design end is required to acquire the locking authority from the data cooperation platform through an API (application programming interface). The lock authority is used for representing whether the current component is locked or not, namely whether other design ends occupy the component or not so as to ensure that only one design end occupies the component at the same time.

Hereinafter, a detailed description will be given of a specific collaborative design method from a design side and a service side, respectively.

In accordance with an embodiment of the present invention, there is provided a co-design method embodiment, it should be noted that the steps illustrated in the flowchart of the figure may be performed in a computer system such as a set of computer-executable instructions, and that while a logical order is illustrated in the flowchart, in some cases the steps illustrated or described may be performed in an order different than here.

In this embodiment, a collaborative design method is provided, which can be used in the design end, and fig. 5 is a flowchart of collaborative design according to an embodiment of the present invention, as shown in fig. 5, the flowchart includes the following steps:

and S11, acquiring the target working unit.

When the design end carries out collaborative design aiming at the target BIM project, only the corresponding target working unit is required to be loaded, and the complete target BIM model is not required to be loaded. The reason is that the server side queries the association relation based on the component co-designed by the design side, and determines the association component having the association relation with the component, so as to implement the association design. Based on this, for the design end, only the target work unit of the relationship needs to be loaded during design.

The target work units may be acquired from the server based on requirements, for example, a selection interface is provided at the design end, and the user selects the selection interface, that is, the corresponding target work units may be loaded. Or, when a user needs a certain target working unit, the user may first perform a search locally to determine whether the target working unit is cached locally, and if the target working unit is cached, the user may directly obtain the target working unit locally.

Details about this step will be described later.

And S12, responding to the co-design of the target component in the target working unit, and sending a co-design request to the server to determine whether the target component is locked.

And the design end provides a man-machine interaction mode, and a user carries out collaborative design on the target component in the target working unit through the man-machine interaction function at the design end. For example, when a user needs to perform collaborative design on a target component a in a target work unit, the design side sends a collaborative design request for the target component to the service side to determine whether the target component is locked.

In particular, as described above, to ensure uniformity of component versions, only one user is allowed to modify the same component at the same time. The server side monitors whether each component is locked or not by adopting the collaborative design lock, and when the component is occupied and modified by a certain design end, the collaborative design lock corresponding to the component is set to be locked at the server side; when a component is released by a design end, the corresponding co-design lock of the component is set to be unlocked at the service end. Based on this, when the server receives the co-design request for the target component sent by the design end, the server can determine whether the target component is locked by searching the co-design lock corresponding to the target component. When the target component is locked, the server side can send a prompt message, the target component is locked and can not be modified, and a user of the design side can be reminded in other modes that the current target component cannot be modified.

And S13, acquiring the related component of the target component determined by the service end based on the collaborative design request when the target component is unlocked.

When the server side determines that the target component is not locked, the server side searches out the related component of the target component. In connection with the description of the design architecture shown in fig. 3, a component data table is stored in the server, and is implemented by a component relation search component in order to be quickly accessed. That is, when data is stored, it is stored as main data and index data. The main data can correspond to each data table, the index data is the main data synchronized to the search engine, and the main data is searched through the search capability provided by the search engine. Corresponding to the search of the associated components, the component relation table is synchronized to a component relation search component, and the component relation search component is utilized to provide an engine for fast search based on component relation so as to realize fast search of the associated components.

When the server side determines the associated component of the target component, the server side issues the associated component, and accordingly, the design side can acquire the associated component.

And S14, loading the associated components and performing associated design on the associated components to determine a collaborative design result.

After the design end acquires the associated component, the associated component is loaded locally, and the associated component is designed in an associated manner while the target component is cooperatively designed. In the collaborative design process, loading as required is realized, and linkage updating of each component in the target BIM project is ensured. The related components can be in other work units, and for the design end, due to the search of the related components at the service end, the related components can be designed together even if a complete BIM model is not loaded.

According to the collaborative design method provided by the embodiment, only the target working unit is needed to be targeted during collaborative design, and a complete target model is not needed to be loaded, so that the real-time performance of data interaction is ensured; the collaborative design method based on the component level breaks through the gap between the files in the collaborative design, and lowers the collaborative granularity to the component level, so that the connection between the data and the data is not limited in a certain file any more, the real-time sharing of the design result is facilitated, and the related components are also subjected to related design in the collaborative design process, thereby realizing the synchronous update and improving the collaborative design efficiency; by determining the locking condition of the target component, the permission approval process in the cooperative working process can be reduced, and the usability is improved.

In this embodiment, a collaborative design method is provided, which can be used in the design end, and fig. 6 is a flowchart of collaborative design according to an embodiment of the present invention, as shown in fig. 6, the flowchart includes the following steps:

and S21, acquiring the target working unit.

Specifically, S21 includes:

and S211, displaying a work unit selection interface.

When a user needs to perform collaborative design on a target BIM project, a collaborative interface is entered, and accordingly, a working unit selection interface is displayed at a design end for the user to select a working unit. Through the working unit selection interface, the corresponding working unit can be loaded on the design end as required, and the complete target BIM model does not need to be loaded from the service end, and then the collaborative design is carried out on the basis.

S212, in response to the selection operation of the work unit selection interface, the current work unit and the reference work unit of the current work unit are determined.

The user selects on the work unit selection interface, for example, the work unit selection interface may filter and refer according to system type, category and other modes, the system type and category and the like define BIM standard data, and the BIM standard data is screened from the collaboration platform database through a BIM standard data mechanism to determine the current work unit and the reference work unit of the current work unit, thereby realizing loading a scene as required. For a certain working unit, it is designed by referring to other working units, and may be referred to by other working units. Therefore, when the current working unit is designed, the reference type or category needs to be selected and sent to the server, and the server performs screening according to the reference type or category to determine the reference working unit of the current working unit.

S213, loading the current working unit and the reference working unit and determining the target working unit.

After the reference unit is determined, the server side issues the reference unit and the current working unit to the corresponding design side, and accordingly, the design side can load the current working unit and the reference working unit. For the design end, the current work unit and the reference work unit are referred to as target work units. The target component may be a component in the current working unit, or may be a component in the reference working unit, which is not limited herein.

In some optional implementations of this embodiment, the S213 may include:

(1) and judging whether the current working unit or the reference working unit is cached locally.

The design end searches the current working unit or the reference working unit in a local cache so as to reduce the process of repeatedly loading the corresponding working unit from the server end. When the current working unit or the reference working unit is not cached locally, executing the step (2); otherwise, executing step (3).

(2) And loading the current working unit or the reference working unit from the server to determine the target working unit.

(3) The current work unit or the reference work unit is loaded locally to determine the target work unit.

That is, the corresponding work unit is preferentially loaded from the local, and the loading or updating is performed from the server only when the work unit does not exist locally or the version of the work unit needs to be updated.

When the target working unit is loaded, the target working unit is loaded from the cache firstly, namely, the intermediate modeling result is reserved, so that the data downloading process when the target working unit is loaded from the server again can be avoided, and the efficiency of collaborative design is improved.

And S22, responding to the co-design of the target component in the target working unit, and sending a co-design request to the server to determine whether the target component is locked.

Please refer to S12 in fig. 5, which is not repeated herein.

S23 acquires the associated component of the target component determined by the server based on the co-design request when the target component is unlocked.

Please refer to S13 in fig. 5, which is not repeated herein.

And S24, loading the associated components and performing associated design on the associated components to determine a collaborative design result.

Specifically, S24 includes:

and S241, acquiring the current collaborative design result of the target component and the associated component.

And S242, comparing the current collaborative design result with the corresponding historical collaborative design result, and determining an incremental design result.

And comparing the current collaborative design result with the historical collaborative design result corresponding to the component at the design end, determining which parts are modified currently, and further determining the changed parts, namely the incremental design result.

And S243, storing the incremental design result to be uploaded to the server under the preset condition.

The design end stores the incremental design result locally and can upload the incremental design result to the service end when the network is idle or in a preset time. The preset condition may be that the network is idle or is scheduled.

In some optional implementations of this embodiment, the foregoing S243 may include:

(1) and updating the version numbers of the working units corresponding to the target component and the associated component.

(2) And storing the version number so as to upload the version number to the server under a preset condition.

And after the design end correspondingly modifies the target component and the associated component, updating the version numbers of the working units corresponding to the target component and the associated component, and saving the version numbers and the modified working units corresponding to the version numbers. Similarly, the design end uploads the stored content to the server end under the preset condition. As described above, the version number is stored instead of directly updating the corresponding work unit, and the purpose of the version number is to ensure stability of the reference work unit of other design ends.

When the component is updated, only the version number of the working unit corresponding to the component is updated, the working unit of the server is not modified, stability of reference working units of other design ends can be guaranteed, and meanwhile, historical snapshots can be obtained through the version number.

In the collaborative design method provided by this embodiment, an association relationship also exists between the working units, that is, a relationship between the reference and the referred to relation exists, and the reliability of the collaborative design can be ensured while avoiding downloading a complete model by loading the corresponding reference working unit at the same time when loading the current working unit. And the collaborative design result is submitted in an increment mode, namely only part of changed components are submitted, so that the efficiency of data submission and storage is improved.

In this embodiment, a collaborative design method is provided, which can be used in the design end, and fig. 7 is a flowchart of collaborative design according to an embodiment of the present invention, as shown in fig. 7, the flowchart includes the following steps:

and S31, receiving the collaborative design request of the target component sent by the design end.

This step corresponds to S12 in the embodiment shown in fig. 5, and when the design end needs to design the target component, the design end sends the co-design request, and accordingly, the server end can receive the co-design request.

S32, determining whether the co-design of the target member is locked based on the co-design request.

As described above, the service end determines whether each component is currently occupied or not by co-designing the lock. After the server receives the collaborative design request, searching is carried out aiming at the identification of the target component, a collaborative design lock corresponding to the target component is determined, and whether the collaborative design of the target component is locked is determined based on the state of the collaborative design lock.

And S33, when the co-design of the target component is unlocked, inquiring the related component of the target component based on the association relationship between the components.

And when the target component is unlocked, the server side searches in the association relation among the components through a search engine to inquire the associated components related to the target component. This step corresponds to S13 in the embodiment shown in fig. 5, please refer to S13 in the embodiment shown in fig. 5 in detail, which is not repeated herein.

And S34, issuing the associated components to enable the design end to carry out associated design on the associated components to determine a collaborative design result.

This step corresponds to S14 in the embodiment shown in fig. 5, please refer to S14 in the embodiment shown in fig. 5 in detail, which is not repeated herein.

The collaborative design method provided by the embodiment is based on a component-level collaborative design method, and breaks through the gap between files in the collaborative design, and lowers the collaborative granularity to a component level, so that the connection between data and data is not limited in a certain file any more, thereby facilitating real-time sharing of design results, and simultaneously performing associated design on associated components in the collaborative design process, thereby realizing synchronous update and improving the collaborative design efficiency; by determining the locking condition of the target component, the permission approval process in the cooperative working process can be reduced, and the usability is improved.

In this embodiment, a collaborative design method is provided, which can be used in the design end, and fig. 8 is a flowchart of collaborative design according to an embodiment of the present invention, as shown in fig. 8, the flowchart includes the following steps:

and S41, receiving a selection request of the current working unit sent by the design end, and determining the current working unit.

Corresponding to S21 in the embodiment shown in fig. 6, the design side sends a selection request of the current work unit to the server side, where the selection request includes not only the identifier of the current work unit but also the screening condition of the reference work unit.

And S42, inquiring the reference working unit corresponding to the current working unit according to the incidence relation of the working units.

After receiving the selection request, the server may query the corresponding reference work unit based on the association relationship of the work units. The association relationship is established based on a corresponding screening manner, for example, the association relationship is established based on a system type, a category, and the like.

And S43, issuing the current working unit and the reference working unit to a design end.

This step corresponds to S213 in the embodiment shown in fig. 6, and please refer to the description of S213 for details, which are not repeated herein.

And S44, receiving the collaborative design request of the target component sent by the design end.

Please refer to S31 in fig. 7 for details, which are not described herein.

S45, determining whether the co-design of the target member is locked based on the co-design request.

Please refer to S32 in fig. 7 for details, which are not described herein.

And S46, when the co-design of the target component is unlocked, inquiring the related component of the target component based on the association relationship between the components.

Please refer to S33 in fig. 7 for details, which are not described herein.

And S47, issuing the associated components to enable the design end to carry out associated design on the associated components to determine a collaborative design result.

Please refer to S34 in fig. 7 for details, which are not described herein.

In the collaborative design method provided by this embodiment, an association relationship also exists between the working units, that is, a relationship between the reference and the referred to relation exists, and the reliability of the collaborative design can be ensured while avoiding downloading a complete model by loading the corresponding reference working unit at the same time when loading the current working unit.

As an optional implementation manner of this embodiment, the collaborative design method may further include:

(1) and receiving an increment design result uploaded by a design end.

(2) And determining a corresponding storage database based on the incremental design result so as to store the incremental design result.

This step corresponds to S24 in the embodiment shown in fig. 6, and the design end determines the incremental design result first, and then uploads the incremental design result to the service end under the preset condition. And when the server receives the increment design result, determining a corresponding storage database to store the increment design result.

In particular, the distributed storage architecture is adopted at the server side to store the related data in the database, and the storage advantage of the database is that the use of the data can be based on smaller granularity and the search query capability can be provided. The design data is mainly divided into two types, one type is main data, and the other type is index data.

As shown in FIG. 9, the master data contains the professional models, units of work, components, and attributes. The main data can store different types of data by using three data storage technologies, mysql stores professional models and work unit data, and the transaction characteristics ensure concurrency consistency; the hbase stores component data, the component data is in hundred million level, and the hbase has great advantages in hundred million level fast access compared with other databases, so that fast access of the data is guaranteed; obs stores file type data, and stores data such as large geometry, mesh, file and the like on obs. The combination of three data storage engines introduces a concurrent consistency problem, technically securing data accesses to meet the transactional nature of ACID through mvcc (multi-version concurrency control) and pessimistic lock techniques.

The database in the main data has the characteristics of high reading speed and high consistency, and has the defect of poor searching capability, in order to make up for the deficiency, two search engines are introduced to support the searching capability, the main data is synchronized to the search engines, the capability of searching components according to component attributes is provided through an elastic search, and the capability of searching the components according to the incidence relation is provided through a graph engine. According to the service characteristics, the main data and the graph engine are designed into a CP system, namely strong consistency, and the CP in a CAP (C-consistency, A-availability and P-partition tolerance) theory is met. The main data and the ES are designed into an AP + BASE system, namely, the final consistency is achieved on the basis of high availability.

The incremental design result is stored in the corresponding storage database, so that the advantages of different types of storage databases are brought into play, and the storage efficiency is ensured.

In this embodiment, a collaborative design apparatus is further provided, and the apparatus is used to implement the foregoing embodiments and preferred embodiments, which have already been described and are not described again. As used below, the term "module" may be a combination of software and/or hardware that implements a predetermined function. Although the means described in the embodiments below are preferably implemented in software, an implementation in hardware, or a combination of software and hardware is also possible and contemplated.

The present embodiment provides a co-design apparatus, as shown in fig. 10, applied to a design end, the co-design apparatus including:

a first obtaining module 51, configured to obtain a target work unit;

a sending module 52, configured to send a co-design request to a server in response to co-design of a target component in the target work unit, so as to determine whether the target component is locked;

a second obtaining module 53, configured to obtain, when the target component is not locked, a related component of the target component that is determined by the server based on the co-design request;

and the loading module 54 is configured to load the associated component, perform associated design on the associated component, and determine a collaborative design result.

The present embodiment further provides a collaborative design apparatus, as shown in fig. 11, which is applied to a server, and the collaborative design apparatus includes:

a receiving module 61, configured to receive a collaborative design request of a target component sent by a design end;

a determination module 62 for determining whether the co-design of the target component is locked based on the co-design request;

the query module 63 is configured to query the related associated components of the target component based on the association relationship between the components when the collaborative design of the target component is unlocked;

and the issuing module 64 is configured to issue the associated component, so that the design end performs associated design on the associated component to determine a collaborative design result.

The co-design means in this embodiment is presented in the form of functional units, where a unit refers to an ASIC circuit, a processor and memory executing one or more software or fixed programs, and/or other devices that may provide the above-described functionality.

Further functional descriptions of the modules are the same as those of the corresponding embodiments, and are not repeated herein.

The embodiment of the invention also provides a non-transitory computer storage medium, wherein the computer storage medium stores computer executable instructions, and the computer executable instructions can execute the collaborative design method in any method embodiment. The storage medium may be a magnetic Disk, an optical Disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a Flash Memory (Flash Memory), a Hard Disk (Hard Disk Drive, abbreviated as HDD), a Solid State Drive (SSD), or the like; the storage medium may also comprise a combination of memories of the kind described above.

Although the embodiments of the present invention 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 invention, and such modifications and variations fall within the scope defined by the appended claims.

Claims

1. A collaborative design method is applied to a design end, and the method comprises the following steps:

acquiring a target working unit;

2. The method of claim 1, wherein the obtaining a target unit of work comprises:

displaying a working unit selection interface;

3. The method of claim 2, wherein said loading said current work cell and said reference work cell, and determining said target work cell, comprises:

4. The method according to claim 1, wherein the loading the associated components and performing associated design on the associated components to determine a co-design result comprises:

5. The method according to claim 4, wherein the storing the incremental design result for uploading to the server under a preset condition comprises:

6. A collaborative design method is applied to a server side, and the method comprises the following steps:

7. The method of claim 6, further comprising:

8. The method of claim 6, further comprising:

receiving an increment design result uploaded by the design end;

9. An electronic device, comprising:

a memory and a processor, the memory and the processor being communicatively coupled to each other, the memory having stored therein computer instructions, the processor executing the computer instructions to perform the co-design method of any of claims 1-5, or any of claims 6-8.

10. A computer-readable storage medium storing computer instructions for causing a computer to perform the co-design method of any one of claims 1-5, or any one of claims 6-8.

11. A co-design system, comprising:

at least one design end for performing the co-design method of any one of claims 1-5; a server, to which the at least one design side is connected, the server being configured to perform the co-design method of any one of claims 6-8.