CN113434174A

CN113434174A - Configuration method and device of collaborative project and electronic equipment

Info

Publication number: CN113434174A
Application number: CN202110721771.XA
Authority: CN
Inventors: 张媛琦; 朱绍能; 韩晓洁
Original assignee: Glodon Co Ltd
Current assignee: Glodon Co Ltd
Priority date: 2021-06-28
Filing date: 2021-06-28
Publication date: 2021-09-24

Abstract

The invention relates to the technical field of computer aided design, in particular to a configuration method, a configuration device and electronic equipment of a collaborative project, wherein the method comprises the steps of receiving a current version of a target collaborative project pushed by a cloud; comparing the current version with a local storage version of the target collaborative project; and updating the configuration data of the stored version by utilizing the configuration data of the current version based on the comparison result, or uploading the configuration data of the stored version to the cloud end to update the configuration data of the current version. By using a combination mode of the cloud and the client, the current version of the cloud is used as a guide, the current version of the cloud needs to be modified no matter whether the cloud or the client modifies the configuration data of the target collaborative project, the consistency of the project configuration data of all users under the target collaborative project is determined, and the modification of the configuration data has real-time performance.

Description

Configuration method and device of collaborative project and electronic equipment

Technical Field

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

Background

The collaborative project is a project processed by multiple persons, wherein, in order to ensure the consistency of the collaborative project configuration data, a professional setting template is generally adopted. The professional-level setting templates are configured according to the classification of the building use functions, namely, the civil buildings, the industrial buildings and the agricultural buildings. Therefore, the professional level setting template can help the user to quickly start the design of the collaborative project, achieve standardized management on related contents and help the data information to be delivered consistently.

Based on the design, a concept of collaborative design is provided, the collaborative design is an important direction for technology updating of the current design industry and is a necessary trend of design technology development, and two technical branches exist, wherein the concept is mainly suitable for large-scale public construction and three-dimensional BIM collaboration of complex structures, and the concept is mainly suitable for two-dimensional CAD collaboration of common buildings and houses. The unified design standard including layers, colors, line types, printing styles and the like is established through collaborative design, on the basis, all design professionals and personnel design on a unified platform, so that mistakes, omissions, collisions and defects caused by unsmooth communication or untimely communication among the current professionals and inside the professionals are reduced, the unicity of all drawing information elements is really realized, other automatic modification is realized, and the design efficiency and the design quality are improved.

However, the professional-level setting template can only achieve the transmission of data information consistency during initialization, and in the collaborative project design process, the designer can only share the design content after actively exporting the design content. Therefore, the configuration method of the collaborative project is difficult to transmit at any time during the project process, and the unification of the project level content is required to be ensured.

Disclosure of Invention

In view of this, embodiments of the present invention provide a configuration method and apparatus for a collaborative project, and an electronic device, so as to solve the problem of uniform content at a project level.

According to a first aspect, an embodiment of the present invention provides a configuration method of a collaborative project, including:

receiving a current version of a target collaborative project pushed by a cloud terminal;

comparing the current version with a local storage version of the target collaborative project;

and updating the configuration data of the stored version by utilizing the configuration data of the current version based on the comparison result, or uploading the configuration data of the stored version to the cloud end to update the configuration data of the current version.

According to the configuration method of the collaborative project, provided by the embodiment of the invention, the current version of the cloud is used as a guide by utilizing the combination mode of the cloud and the client, and the current version of the cloud needs to be modified no matter the cloud or the client modifies the configuration data of the target collaborative project, so that the consistency of the project configuration data of all users under the target collaborative project is ensured, and the modification of the configuration data has real-time performance.

With reference to the first aspect, in a first implementation manner of the first aspect, when the current version is higher than the stored version, the updating the configuration data of the stored version with the configuration data of the cloud based on the comparison result includes:

acquiring the configuration data of the current version from the cloud;

updating the configuration data of the stored version based on the configuration data of the current version.

According to the configuration method of the collaborative project, when the current version of the cloud is higher than the local storage version, the configuration data of the local storage version is updated by the configuration data of the current version of the cloud, so that the local configuration data can be synchronized with the latest version of the cloud in time.

With reference to the first implementation manner of the first aspect, in a second implementation manner of the first aspect, the obtaining the configuration data of the current version from the cloud includes:

determining whether to update the configuration data of the stored version in response to a selection operation on whether the stored version is updated;

when the configuration data of the storage version is not updated, responding to the submission operation of the target collaborative project, and determining that the submission operation is invalid;

and acquiring the configuration data of the current version from the cloud end so as to forcibly update the configuration data of the stored version.

According to the configuration method of the collaborative project provided by the embodiment of the invention, when the latest version of the target collaborative project is updated, if the configuration data of the stored version is not updated locally, the local modification data can not be submitted, because the local modification is not performed under the latest version, the consistency of the configuration data of the target collaborative project operated by multiple parties can be ensured.

With reference to the second implementation manner of the first aspect, in a third implementation manner of the first aspect, the updating the configuration data of the stored version based on the configuration data of the current version includes:

forcibly updating the configuration data of the storage version;

and submitting the forcibly updated configuration data to the cloud so that the cloud updates the current version of configuration data.

According to the configuration method of the collaborative project, provided by the embodiment of the invention, after the configuration data of the storage version is updated, since the configuration data of the storage version is locally updated, the modified data is uploaded again on the basis of consistent version, on one hand, the configuration data of the cloud can be timely modified, and on the other hand, the consistency of the configuration data is ensured.

With reference to the first implementation manner of the first aspect, in a fourth implementation manner of the first aspect, the updating the configuration data of the stored version based on the configuration data of the current version includes:

comparing the configuration data of the current version with the configuration data of the stored version, and determining a modification item and a merging item in the configuration data of the stored version, wherein the merging item is obtained by locally modifying the configuration data of the stored version;

and modifying the corresponding content in the configuration data of the storage version by using the modification item, and newly adding the corresponding content in the configuration data of the storage version by using the merging item to determine the updated configuration data.

According to the configuration method of the collaborative project, provided by the embodiment of the invention, as the storage version comprises the merging item, when the configuration data of the storage version is updated, the content of the merging item is not influenced, the loss of data modification is reduced, and the configuration efficiency is improved.

With reference to the fourth implementation manner of the first aspect, in the fifth implementation manner of the first aspect, the updating the configuration data of the stored version based on the configuration data further includes:

uploading the updated configuration data to the cloud so that the cloud updates the current version.

According to the configuration method of the collaborative project, provided by the embodiment of the invention, as the storage version has the merging item, namely the newly-added content, after the local update, the configuration data after the local update is uploaded to the cloud, so that the cloud can modify the content of the merging item corresponding to the local version of the configuration data of the current version, and the consistency of the configuration data is ensured.

With reference to the first implementation manner of the first aspect, in a sixth implementation manner of the first aspect, the updating the configuration data of the stored version based on the configuration data of the current version includes:

acquiring a current data table corresponding to the storage version;

establishing a target data table by using the current data table;

updating the target data table based on the current version of the configuration data to update the stored version of the configuration data.

According to the configuration method of the collaborative project, provided by the embodiment of the invention, the configuration data is updated in a data table mode when the collaborative project is updated, so that the target data tables are not used by the low version before the upgrade, the data in the target data tables are not influenced, and the target data tables are influenced only when the collaborative project is upgraded.

With reference to the first aspect, in a seventh implementation manner of the first aspect, when the current version is the same as the stored version, the uploading the configuration data of the stored version to the cloud to update the configuration data of the cloud includes:

determining modified configuration data in response to a modification operation on the stored version of configuration data;

and uploading the modified configuration data to the cloud end so as to update the configuration data of the cloud end.

According to the configuration method of the collaborative project, provided by the embodiment of the invention, when the current versions of the local and the cloud are the same, if the local modifies the configuration data, the modified configuration data is uploaded to the cloud so as to update the configuration data of the cloud, and the consistency of the configuration data of the cloud and the local is ensured.

According to a second aspect, an embodiment of the present invention further provides a configuration method of a collaborative project, including:

acquiring modification of configuration data of a target collaborative project;

updating the configuration data of the current version of the target collaborative project based on the modification of the configuration data;

and pushing the current version of the target collaborative project to each desktop end, so that each desktop end updates the configuration data of the storage version of the target collaborative project at the desktop end in real time.

According to the configuration method of the collaborative project, when the configuration data is modified, the cloud terminal not only modifies the configuration data of the current version, but also pushes the modification information to each desktop terminal, so that each desktop terminal updates the configuration data of the corresponding storage version in real time, and the consistency of the configuration data is ensured.

With reference to the second aspect, in a first implementation manner of the second aspect, the modifying of the configuration data is submitted by at least two desktop ends within a preset time interval, and the updating of the configuration data of the current version of the target collaborative project based on the modifying of the configuration data includes:

comparing the time when the submitted contents of the at least two desktop ends are received;

determining the desktop end with the earliest receiving time as a target desktop end;

and modifying the configuration data of the current version based on the submitted content of the target desktop end, and updating the current version of the target collaborative project.

According to the configuration method of the collaborative project, provided by the embodiment of the invention, the plurality of modifications submitted in the preset time interval are subject to the modification received first, and the other modifications are invalid, so that the timeliness of the modification of the configuration data can be ensured on the basis of ensuring the consistency of the configuration data.

According to a third aspect, an embodiment of the present invention further provides a configuration apparatus for a collaborative project, including:

the receiving module is used for receiving the current version of the target collaborative project pushed by the cloud end;

the comparison module is used for comparing the current version with the local storage version of the target collaborative project;

the first updating module is used for updating the configuration data of the storage version by using the configuration data of the current version based on the comparison result, or uploading the configuration data of the storage version to the cloud end to update the configuration data of the current version.

The configuration device for the collaborative project provided by the embodiment of the invention utilizes the combination mode of the cloud and the client, takes the current version of the cloud as the guide, and needs to modify the current version of the cloud no matter whether the cloud or the client modifies the configuration data of the target collaborative project, so as to determine the consistency of the project configuration data of all users under the target collaborative project, and the modification of the configuration data has real-time performance.

According to a fourth aspect, an embodiment of the present invention further provides a configuration apparatus for a collaborative project, including:

the acquisition module is used for acquiring modification of configuration data of the target collaborative project;

a second updating module, configured to update the configuration data of the current version of the target collaborative project based on the modification of the configuration data;

and the pushing module is used for pushing the current version of the target collaborative project to each desktop end so that each desktop end can update the configuration data of the storage version of the target collaborative project at the desktop end in real time.

According to the configuration device of the collaborative project, when the configuration data is modified, the cloud end not only modifies the configuration data of the current version, but also pushes the modification information to each desktop end, so that each desktop end updates the configuration data of the corresponding storage version in real time, and the consistency of the configuration data is ensured.

According to a fifth aspect, an embodiment of the present invention provides an electronic device, including: the device comprises a memory and a processor, wherein the memory and the processor are communicatively connected with each other, the memory stores computer instructions, and the processor executes the computer instructions to execute the configuration method of the collaborative project according to the first aspect or any one of the embodiments of the first aspect, or the second aspect or any one of the embodiments of the second aspect.

According to a sixth aspect, an embodiment of the present invention provides a computer-readable storage medium, which stores computer instructions for causing a computer to execute the method for configuring a collaborative project according to the first aspect or any one of the second aspect.

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 block diagram illustrating a configuration system for collaborative projects in an embodiment of the present invention;

FIG. 2 is a diagram illustrating the design architecture of a configuration system for collaborative projects in an embodiment of the present invention;

3 a-3 b show application scenarios of configuration methods of collaboration items in embodiments of the invention;

FIG. 4 is a flow chart of a configuration method of a collaborative project according to an embodiment of the present invention;

FIG. 5 is a flow chart of a configuration method of a collaborative project according to an embodiment of the present invention;

FIG. 6 is a flow chart of a configuration method of a collaborative project according to an embodiment of the present invention;

FIG. 7 is a schematic illustration of table compatibility according to an embodiment of the invention;

FIG. 8 is a schematic diagram of column compatibility according to an embodiment of the present invention;

FIG. 9 is a process diagram of merging items according to an embodiment of the invention;

FIG. 10 is a flow chart of a configuration method of collaborative projects according to an embodiment of the present invention;

FIG. 11 is a flow chart of a configuration method of collaborative projects according to an embodiment of the present invention;

12 a-12 b are flow diagrams of a configuration method of collaborative projects according to embodiments of the present invention;

FIGS. 13 a-13 d are schematic diagrams of table structures according to embodiments of the present invention;

FIG. 14 is a schematic illustration of a hierarchical representation according to an embodiment of the invention;

fig. 15 is a block diagram of a configuration apparatus of a collaborative project according to an embodiment of the present invention;

fig. 16 is a block diagram of a configuration apparatus of a collaborative project according to an embodiment of the present invention;

fig. 17 is a schematic diagram of a hardware structure of an electronic device 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.

The embodiment of the invention provides a configuration system of a collaborative project, which comprises a cloud end and at least two desktop ends, wherein each desktop end is connected with the cloud end. The desktop end runs a tool end, the tool end is model design software, and a user designs a model through the tool end.

The configuration system shown in fig. 1 includes a cloud and 3 desktop terminals, where the 3 desktop terminals are used to design the collaborative project together, and it is necessary to ensure consistency of configuration data of the collaborative project. Based on this, the desktop and the cloud need to exchange data in real time to ensure the consistency of the configuration data. In the embodiment of the present invention, the configuration data of the cloud is used as guidance, that is, the configuration data of the cloud is the latest configuration data of the collaborative project. In order to distinguish between configuration data updated at different times, versions are used for representation. Specifically, the version of the configuration data of the cloud end is referred to as a current version, and the version of the configuration data of the desktop end is referred to as a storage version.

As described above, for the collaborative project, the cloud end needs to push the current version to the desktop end in real time because the cloud end stores the latest configuration data, so that the desktop end synchronizes the configuration data in time. When the desktop side updates the configuration data of the collaborative project, the updated configuration data is uploaded to the cloud side, so that the cloud side is utilized to synchronize the updated configuration data to other desktop sides.

The configuration method regarding a specific collaborative project will be described in detail below.

As an optional implementation manner of the embodiment of the present invention, for example, the electromechanical professional configuration is adopted, the general design is performed in a cloud + desktop cooperation manner, the VUE is used in general, the C + + language is used in the desktop, the C # language is used in the back end, and the same data is stored in the cloud HBase database. The cloud end firstly performs application template instantiation project level data, then the desktop end and the cloud end can download and edit the data through a background API interface, and a background tracks and merges the data by using a lock.

As shown in fig. 2, the cloud uses vue.js as a front-end framework, ant-design is cooperated to make ui compatibility, axios performs data request communication, and esint performs code constraint. The Structure serves as a component library service and is provided for the cloud end and the desktop end to project and download components. The collaborative bimodel provides project level services, such as user roles, permissions and the like. The GMEP desktop terminal is developed by using c + + language, component level data are stored in a sqlite database, and professional level configuration data are stored in a Qbase database. And C # rear end provides cloud and desktop API to uniformly process and merge professional-level configuration data. The Thirdtable service provides an external API to access data to the Hbase database and uses schema for field security checks. The Hbase database is more convenient for mass data storage and has better performance.

In the configuration system of fig. 2, a component library is also provided, where the component library is a project-level unified management component, and the component-level unification is also achieved by referring to the corresponding component from the component library.

The tool end operated by the desktop end may be GMEP software, or may also be other model design software, and no limitation is imposed on the model design software. As described above, when a collaborative project needs to be designed, a professional-level configuration template needs to be used to initialize the project. The professional configuration templates include a business class, a residential building class, a hospital class, a school class and the like, and the professional configuration templates can be selected according to actual conditions. After the professional configuration template is determined, project initialization is performed using the template. Specifically, a plurality of professional configuration templates are configured at the cloud, and when each tool end initializes a project, the corresponding professional configuration template is selected from the cloud to initialize the collaborative project, and then the collaborative project is designed.

Fig. 3a shows a pipeline rendering of data services and GMEP software for an electromechanical professional-level configuration template, which will serve the GMEP software after project-level professional configuration data is downloaded. Specifically, after a project is initialized by applying a certain template, when a tool end of a desktop end opens the project for the first time, data such as a system type, a pipeline type, a pipe arrangement configuration, a specification list and the like in GMEP software are generated according to the data, and preparation is made for a user to draw a pipeline. When a user draws pipes, ducts, bridges, and conduits, the relevant system types and keys, such as fitting components like elbows, tees, cross-overs, and transitions, are automatically applied. Therefore, professional setting of project level guarantees the consistency of the three-dimensional models after the users draw at the tool end in the same collaborative project.

Further, fig. 3b shows a detailed configuration flow. The initialization of the cloud professional-level configuration device is carried out on the premise that a collaborative project is entered, a user can select a professional-level setting template as a basis to perform content custom addition or modification, and can also select a 'no' sample, namely, the new professional-level setting template is created. The professional-level configuration comprises a series of configuration contents which need to be coordinated and unified in electromechanical design, the contents can be continuously expanded according to needs, and the part of the requirement contents are water supply and drainage, heating and ventilation and electrical parts of the cloud professional-level configuration.

Specifically, a user initiates a project from the collaboration platform, namely the collaboration project, after a tool side enters the project, the tool side selects whether the project to be designed is the collaboration project, when the project is the collaboration project, professional configuration of a cloud end is automatically synchronized to the local, and when the project is not the collaboration project, the local basic configuration content is used. The collaboration platform is an application platform of a Web end.

When a user initiates a project, the collaborative project of a collaborative mode is entered, and at this time, the electromechanical responsible person or the professional responsible person needs to enter professional level setting for electromechanical initialization of electromechanical in the professional level setting. Specifically, a default professional configuration is selected for the collaborative project according to the template, the default professional configuration is a default configuration which is maintained inside the GMEP and is continuously issued according to the business state, a professional-level setting user for GMEP issuance can save the template as equivalent to saving the default professional configuration of the GMEP as a new template, and the content of the default professional-level configuration cannot be influenced by addition and deletion changes performed by the user under the saved professional configuration. The user can modify the content in the GMEP default professional level configuration according to the requirements of the project and save the content for the next project.

Alternatively, the user may customize the professional template. Specifically, the user-defined professional template belongs to the account of the user, and the user creates other projects in cooperation to use the professional template which is saved before.

Furthermore, professional level settings under the project are attached to each individual project according to the fact that the project belongs to the project, the configuration templates under other projects cannot be affected by modification of the initialized templates, and a user selects a default professional level setting for one project and is not allowed to replace the default professional level setting. Wherein, the default professional configuration file is selected to contain the following templates: GMEP-commercial electromechanical setting template, GMEP-residential building (residence) electromechanical setting template, GMEP-office electromechanical setting template, GMEP-school electromechanical setting template, GMEP-hospital electromechanical setting template, GMEP-stadium electromechanical setting template and GMEP-entertainment electromechanical setting template. Wherein, the priority of each setting template is from front to back. The configuration template has strong expansibility, can perform hierarchical management based on enterprise-level and project-level professional configuration templates, and can precipitate the practical experience of a user in each project and reuse the experience in a plurality of projects. Specifically, the user is allowed to save templates, settle project experience and apply the saved templates to templates of different buildings, so that the projects can be reused. According to the customization requirement, after new form data is added, the contents of the template can be expanded in different versions.

Further optionally, the native layer level expression is set at the professional level. As shown in fig. 14, taking the type of the water supply and drainage pipeline system as an example, the existing product pipeline-based system type is managed by taking the pipe series as a first view as a hierarchical structure, and for domestic users, the dimension is very unaccustomed, so that the part is optimized according to the habit of domestic designers. The type of the pipeline system refers to a system where a water supply and drainage designer needs to designate a pipeline when drawing the pipeline, and the current priority of the contents of water supply and drainage in the electromechanical configuration is the type of the pipeline system, the series of pipes and the combination of pipe fittings. The type of pipe system and the series of pipes, pipe fittings, all have a reference and nesting relationship with each other. The piping system type is a system type in which a pipe string and a pipe fitting are assembled into a system type in combination and used, and the piping system type is a system type in which all configurations are collectively placed. The hierarchical structure breaks through the traditional configuration template which needs to be used as the load bearing and the transmission of data based on files or specific formats, and the professional configuration template has no file and is used for pure data transmission.

Further, component configurations are associated with project component libraries in professional-level configurations, i.e., the component library described in FIG. 2. Taking the piping arrangement as an example, all the arranged pipe fittings are added from the project component library when the pipe fitting combination is arranged. The pipe fittings are used for providing a uniform arrangement for the use of some pipe fittings appearing when a water supply and drainage designer draws a pipe, and continuous drawing of a user is guaranteed. The common pipe fittings of the water supply and drainage system comprise an elbow, a tee joint, a four-way joint, a transition piece, a movable joint, a pipe plug and the like. Pipe fittings may have different components depending on the pipe system, and their specifications are also defined in terms of the specifications of the pipe family. Since the series of pipes used for different system types differ, for example, the chemical composition of the fluid in the pipes in the water supply system and the sewage system is different, the pipe fittings of the different series of pipes are intended to meet the requirements for transporting gas or fluid in different system types. The professional level configuration template is communicated with the project component library, the content of resource types in the project is managed uniformly and transmitted in real time in the project design process, and the purposes of consistent source and multi-user application are achieved.

The above description is directed to professional-level configuration templates and system architectures, and the following description is directed to a configuration method in a collaborative project design process.

In accordance with an embodiment of the present invention, there is provided an embodiment of a method for configuring a collaborative project, it should be noted that the steps illustrated in the flowchart of the accompanying drawings 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 configuration method of a collaborative project is provided, which can be used in the desktop terminal, such as a computer, a tablet computer, and the like, fig. 4 is a flowchart of the configuration method of the collaborative project according to the embodiment of the present invention, and as shown in fig. 4, the flowchart includes the following steps:

and S11, receiving the current version of the target collaborative project pushed by the cloud.

As described above, the cloud stores the latest configuration data of the target collaborative project, i.e., the latest configuration data is characterized by the current version. For the desktop, the current version of the target collaborative project pushed by the cloud is received. The desktop receives the current version pushed by the cloud, and the current version can be updated or periodically pushed by the cloud, so that the desktop is synchronized with the cloud in time. The time when the desktop receives the current version pushed by the cloud is not limited at all, and corresponding setting can be specifically carried out according to actual requirements.

For example, a user modifies configuration data of a target collaborative project at a cloud, and a current version of the cloud is updated on an original version, so that the cloud pushes the current version to each desktop end participating in the target collaborative project. If the original version is V1, the updated current version is V2.

Or, the desktop terminal a modifies the configuration data of the target collaborative project, and uploads the modified configuration data to the cloud terminal, so that the current version of the cloud terminal is updated on the original version, and then the cloud terminal pushes the current version to other desktop terminals participating in the target collaborative project.

And S12, comparing the current version with the local storage version of the target collaborative project.

For the desktop end, the stored version of the target collaborative project is referred to as a stored version. And the desktop terminal compares the received current version of the cloud terminal with the local storage version to determine whether the current version of the cloud terminal is different from the local storage version of the cloud terminal.

For example, the current version is V2, and the storage version is V1, which indicates that the local configuration data needs to be updated; the current board is V2, and the storage version is V2, which indicates that the version of the local configuration data is the same as the version of the configuration data in the cloud at this time.

And S13, updating the configuration data of the stored version by using the configuration data of the current version based on the comparison result, or uploading the configuration data of the stored version to the cloud end to update the configuration data of the current version.

If the local storage version is lower than the cloud storage version, updating the configuration data of the storage version by using the configuration data of the current version of the cloud; when the local storage version is consistent with the storage version of the cloud and the configuration data is updated locally on the basis of the storage version, the configuration data of the storage version needs to be uploaded to the cloud so as to update the configuration data of the current version.

This step will be described in detail in the following, and is explained in particular in two parts in the following, namely: the current version is higher than the stored version and the current version is consistent with the stored version.

In the configuration method of the collaborative project provided by this embodiment, a combination mode of the cloud and the client is utilized, and the current version of the cloud is used as a guide, and no matter whether the cloud or the client modifies the configuration data of the target collaborative project, the current version of the cloud needs to be modified, so that the consistency of the project configuration data of all users under the target collaborative project is determined, and the modification of the configuration data has real-time performance.

In this embodiment, a configuration method of a collaborative project is provided, which can be used for the desktop terminal, such as a computer and a tablet computer. Fig. 5 is a flowchart of a configuration method of a collaborative project according to an embodiment of the present invention, and as shown in fig. 5, the flowchart includes the following steps:

and S21, receiving the current version of the target collaborative project pushed by the cloud.

Please refer to S11 in fig. 4 for details, which are not described herein.

And S22, comparing the current version with the local storage version of the target collaborative project.

Please refer to S12 in fig. 4 for details, which are not described herein.

And S23, updating the configuration data of the stored version by using the configuration data of the current version based on the comparison result, or uploading the configuration data of the stored version to the cloud end to update the configuration data of the current version.

Specifically, S23 includes:

s231, obtaining the configuration data of the current version from the cloud.

When the storage version of the desktop end is lower than the current version of the cloud end, the desktop end needs to update the configuration data of the storage version by using the configuration data of the current version. Based on this, the desktop needs to obtain the configuration data of the current version from the cloud. For example, the desktop sends a request for downloading configuration data to the cloud, and after receiving the request, the cloud sends the configuration data of the current version to the desktop. Accordingly, the desktop side acquires the configuration data of the current version from the cloud side.

And S232, updating the configuration data of the stored version based on the configuration data of the current version.

When updating the configuration data, the desktop terminal may compare the configuration data of the current version with the configuration data of the stored version to determine the updated data item, update the updated data item, and keep the rest of the data unchanged; alternatively, the stored version of configuration data may be overwritten with the current version of configuration data.

However, if the stored version is lower than the current version, the desktop modifies and adds new configuration data of the stored version. Then the modified part and the newly added part need to be processed separately. That is, for a modified portion, the modification is not valid because it was not modified under the latest version of configuration data; for the newly added part, since it does not affect other data, the data of the part needs to be merged with the updated configuration data, and the newly added part is referred to as a merge item hereinafter. Based on this, in some optional implementations of this embodiment, the above S232 may include:

(1) and comparing the configuration data of the current version with the configuration data of the stored version, and determining a modification item and a merging item in the configuration data of the stored version, wherein the merging item is obtained by locally modifying the configuration data of the stored version.

When the comparison is performed, the identifiers of the items in the configuration data can be used for comparison, that is, the items corresponding to the items of the configuration data of the stored version are determined in the configuration data of the current version, and then whether the data of the items are consistent or not is compared, so that the modification items can be determined; meanwhile, if the entry corresponding to the entry of the configuration data of the stored version is not matched in the configuration data of the current version, the entry in the configuration data of the stored version is considered as a merging entry.

(2) And modifying the corresponding content in the configuration data of the stored version by using the modification item, and newly adding the corresponding content in the configuration data of the stored version by using the merging item to determine the updated configuration data.

For example, the study A edits 'domestic water supply' at a tool end of a desktop end, modifies description information of 'domestic water supply', and adds a 'domestic water supply-1'. However, at this time, the description information of the "life water supply" in the cloud is changed, so that the current version of the cloud is inconsistent with the storage version of the desktop. Therefore, for the A classmates, the description information of the 'domestic water supply' is a modification item, and the 'domestic water supply-1' is a merging item. Then, for the classmate a, the classmate a needs to synchronize with the configuration data in the cloud first, that is, the description information about "life water supply" submitted by the classmate a at this time is invalid and needs to be updated to the description information about "life water supply" in the cloud, but the newly added "life water supply-1" in the classmate a will be retained.

(3) And uploading the updated configuration data to the cloud so that the cloud updates the current version.

After the desktop terminal updates the modification item by using the configuration data of the current version, since the configuration data of the desktop terminal also contains the merge item, the updated configuration data needs to be uploaded to the cloud terminal as a whole, so that the cloud terminal updates the current version.

That is, when the storage version of the desktop is lower than the current version of the cloud and the merge item exists in the storage version of the desktop, the configuration data of the current version is used for updating the modification item in the configuration data of the desktop, and then the updated configuration data is uploaded to the cloud integrally, so that the cloud updates the current version.

Because the storage version comprises the merging item, when the configuration data of the storage version is updated, the content of the merging item is not influenced, the loss of data modification is reduced, and the configuration efficiency is improved. Because the storage version has the merging item, namely the newly-added content, after the local update, the configuration data after the local update is uploaded to the cloud, so that the cloud can modify the content of the merging item corresponding to the local version of the configuration data of the current version, and the consistency of the configuration data is ensured.

In the configuration method of the collaborative project provided by this embodiment, when the current version of the cloud is higher than the local storage version, the configuration data of the local storage version is updated by using the configuration data of the current version of the cloud, so that the local configuration data can be synchronized with the latest version of the cloud in time.

As a specific application example of the present embodiment, the step S23 may include:

(1) in response to a selection operation of whether the stored version is updated, it is determined whether the configuration data of the stored version is updated.

The cloud end pushes the current version to the desktop end, and a user selects whether to update the stored version at the desktop end so as to determine whether to immediately update the configuration data of the stored version. And when the user selects to update the configuration data of the memory board, the desktop side updates the configuration data of the memory version.

(2) When the configuration data of the storage version is not updated, the submitting operation is determined to be invalid in response to the submitting operation of the target collaborative item.

When the user chooses not to update the configuration data of the stored version, the cloud end can push the current version at a certain interval. If the desktop side updates the configuration data of the stored version within the period of time, for example, operations such as adding, deleting, changing and the like are performed. When the user submits the target collaborative project, the submitting operation is determined to be invalid, because the project processing is not performed on the basis of the current version.

(3) And acquiring the configuration data of the current version from the cloud so as to forcibly update the configuration data of the stored version.

If the configuration data of the storage version needs to be updated if the configuration data of the storage version needs to be successfully submitted, the configuration data of the storage version is updated until the configuration data of the storage version is consistent with the configuration data of the current version of the cloud, and then the configuration data of the storage version is forcibly updated.

(4) The stored version of the configuration data is forcibly updated.

(5) And submitting the forcibly updated configuration data to the cloud so that the cloud updates the configuration data of the current version.

As described above, if the desktop side updates the configuration data of the storage version, if the merge item exists, the configuration data of the cloud side needs to be updated. At this time, the configuration data after the forced update needs to be submitted to the cloud, so that the cloud updates the configuration data of the current version.

When the latest version of the target collaborative project is updated, the local modification data cannot be submitted if the configuration data of the stored version is not locally updated, because the local modification is not performed under the latest version, the consistency of the configuration data of the target collaborative project operated by multiple parties can be ensured. After the configuration data of the storage version is updated, the configuration data of the storage version is locally updated, and the modified data is uploaded again on the basis of consistent version, so that the configuration data of the cloud can be timely modified, and the consistency of the configuration data is ensured.

In other optional embodiments of this embodiment, when updating the configuration data, the data may be stored in a data table. The S232 may further include:

(1) and acquiring a current data table corresponding to the storage version.

The desktop end stores the configuration data of each version in a data table mode, namely, for the stored version, the current data table corresponds to the stored version.

(2) And establishing a target data table by using the current data table.

Before updating, a target data table is established, and subsequent updating is carried out in the target data table without influencing the data content of the current data table.

(3) The target data table is updated based on the current version of the configuration data to update the stored version of the configuration data.

As shown in fig. 7, the tool side stores data tables of various versions, and when data is updated, a certain data item of the data table may be updated, while other data items remain unchanged, so as to implement table compatibility.

As shown in fig. 8, similar to the table-compatible method, each table has columns required by all versions, i.e. the merge entries, and each version uses its own required columns when used. Unlike table compatibility, each version of a column has its own default value, primarily for compatibility with old data.

As shown in fig. 9, when the merged item needs to be processed, for example, the column of code is changed, an alias name called code _ V4 is added to the column, then a column called code _ V4 is added, and new data is stored in the new column, and the column that is not changed. When the data is fetched subsequently, the list of code data is fetched, and when the list of code data is fetched with an alias, the list of alias data is fetched more alias, and finally all the data are integrated and returned to the cloud end or the tool end.

Corresponding to the data table, other types of data tables are maintained at the desktop end or the cloud end so as to maintain the configuration data of the target collaborative project. For example, as shown in FIGS. 13 a-13 d, a version control table, a config table, an item template association table, and a template table are shown, respectively. Specifically, the version control table updates, tracks and merges and is compatible with the overall data update version, the merging and compatibility means that the Web end and the tool end add marks to the data, when the data are handed to the back end, the back end records one version of the overall data once change and stores the version number into the version control table when processing the data, so that when the client accesses the data, the back end tracks the data according to the version of the table and returns the version data required by the client; the item template table refers to a common template which is provided for users by electromechanics, and the template data is stored in the template table; the template association table refers to electromechanical project professional level configuration data which are in a project unit, each project can generate own configuration data, the configuration data come from the initialization of the template, and therefore, the relationship exists between the configuration data and the template, and the relationship is stored in the template association table; the config represents a business table configured in project professional level, most business data, such as system type, pipe series, accessory combination and the like, are stored in the config table, and the business types are distinguished through groupName in the table.

When the configuration data is updated, the configuration data is updated in a data table mode, so that the target data tables are not used by the low version before upgrading, the data in the target data tables are not influenced, and the target data tables are influenced only when upgrading.

In the present embodiment, a configuration method of a collaborative project is provided, which can be used for the desktop terminal, such as a computer and a tablet computer. Fig. 10 is a flowchart of a configuration method of a collaborative project according to an embodiment of the present invention, and as shown in fig. 10, the flowchart includes the following steps:

and S31, receiving the current version of the target collaborative project pushed by the cloud.

Please refer to S11 in fig. 4 for details, which are not described herein.

And S32, comparing the current version with the local storage version of the target collaborative project.

Please refer to S12 in fig. 4 for details, which are not described herein.

And S33, updating the configuration data of the stored version by using the configuration data of the current version based on the comparison result, or uploading the configuration data of the stored version to the cloud end to update the configuration data of the current version.

Specifically, S33 includes:

s331, in response to a modification operation on the stored version of the configuration data, determining modified configuration data.

When the storage version is consistent with the current version, the user obtains the modified configuration data when modifying, for example, adding, deleting, changing and the like, the configuration data of the storage version at the desktop. Accordingly, the version of the current desktop end project configuration template is updated and is inconsistent with the current version of the cloud end.

S332, uploading the modified configuration data to a cloud end to update the configuration data of the cloud end.

And the desktop terminal uploads the modified configuration data to the cloud terminal, so that the cloud terminal updates the configuration data of the current version by using the configuration data.

For example, as shown in fig. 6, the desktop-side item configuration is added, deleted, or changed, it is determined whether the local modification is valid, and when the local modification is valid, the desktop-side item configuration template version +1 in the current work unit is used; when not in effect, the current project configuration version remains unchanged. And after the version of the desktop end project configuration template is updated, prompting that the project configuration is updated and whether the project configuration is immediately synchronized or not at a tool end of the desktop end. At this time, it is shown that whether the configuration data updated by the desktop needs to be synchronized to the cloud is confirmed to the user.

When the user selects immediate synchronization, the current version of the cloud is updated; when the user selects to synchronize later, the user continues to use the project configuration, which can be synchronized later on the collaboration panel. Further, if the user selects a little synchronization, then on the basis of non-synchronization, when the working unit is provided, the tool end continues to send a prompt, the project configuration is updated, whether the working unit is synchronized or not is submitted, if the working unit is selected to be synchronized immediately, the current version of the cloud end is updated, and otherwise, the configuration data of the tool end is stored to the individual.

According to the configuration method of the collaborative project, when the current versions of the local and the cloud are the same, if the configuration data is modified locally, the modified configuration data is uploaded to the cloud so as to update the configuration data of the cloud, and therefore consistency of the cloud and the local configuration data is guaranteed.

Specifically, for the desktop end project configuration submitted to the cloud end, data comparison needs to be performed to determine whether the data comparison conflicts. For the content of the same item, if the content is not considered to be in conflict, the data is integrated by adopting a cloud + end; if the user edits and modifies the existing conflict item content, the user must edit the conflict item content on the basis of the latest cloud version, and the modified content is effective.

In this embodiment, a configuration method of a collaborative project is provided, which can be used in the cloud, such as a computer, a tablet computer, and the like, fig. 11 is a flowchart of the configuration method of the collaborative project according to the embodiment of the present invention, and as shown in fig. 11, the flowchart includes the following steps:

s41, the modification of the configuration data of the target collaborative project is obtained.

For the cloud, the modification of the configuration data of the target collaborative project, which is acquired by the cloud, comes from two aspects, namely the modification performed by the user at the cloud and the modification performed by the user at the tool end are uploaded to the cloud.

S42, updating the configuration data of the current version of the target collaborative project based on the modification of the configuration data.

And after the cloud acquires the modification of the configuration data, updating the configuration data of the current version. For the cloud update method of the configuration data, reference may be made to the description of updating the configuration data at the desktop end, and details are not described herein again.

And S43, pushing the current version of the target collaborative project to each desktop end, so that each desktop end updates the configuration data of the storage version of the target collaborative project at the desktop end in real time.

After the configuration data of the cloud terminal is updated, the current version is pushed to each desktop terminal, so that the configuration data of the cloud terminal can be synchronized in real time by each desktop terminal. For the synchronization of each desktop end, please refer to the description of the configuration method executed by the desktop end, which is not described herein again.

According to the configuration method of the collaborative project, when the configuration data is modified, the cloud end not only modifies the configuration data of the current version, but also pushes the modification information to each desktop end, so that each desktop end updates the configuration data of the corresponding storage version in real time, and the consistency of the configuration data is ensured.

As an application scenario of the configuration method in this embodiment, if the modified configuration data is submitted by the classmates a and B, the time for receiving the modified configuration data by the cloud is different due to objective reasons, such as network speed, and the like, then the cloud uses the configuration data received first as a modification basis according to the principle of first obtaining first. Accordingly, in some optional implementations of this embodiment, the above S43 includes:

(1) and comparing the time when the submitted contents of the at least two desktop ends are received.

When the cloud end receives the submitted content of the desktop end, receiving time is recorded.

(2) And determining the desktop end with the earliest receiving time as a target desktop end.

(3) And modifying the configuration data of the current version based on the submitted content of the target desktop end, and updating the current version of the target collaborative project.

Specifically, the project configuration is submitted by adopting a first-come first-serve principle, and the data submitted to the cloud side is preferentially effective. For example, the classmates a and B submit the update of the project configuration of the tool side at the same time, however, the speed of the classmates a is fast, the submission takes effect preferentially, and the submission of the classmates B is detected by conflict, that is, the submission of the classmates B is invalid.

And if the contents of the same item are considered to be in conflict, the data is subject to the cloud, and the same contents of the tool end are covered by the cloud contents. For example, the classmates A edit 'living water supply' at the tool end, the description information of 'living water supply' is modified, the classmates B edit the description information of 'living water supply' at the cloud, but the submission of the classmates A lags behind the classmates B, namely, the version of the cloud has changed, but the classmates A are not synchronized in time, the classmates A must synchronize the project configuration of the cloud in order to successfully submit the work unit, the description of 'living water supply' edited before the classmates A are synchronized can be covered by the modification of the classmates B at the cloud, namely, the editing of the classmates A is unsuccessful.

According to the submission principle, the information of the external cloud is transmitted to the related reminding of content change of professional-level configuration of the desktop, and the control of the related version of the work file is submitted to help a user to ensure the consistency of the configuration information in the project level.

And the plurality of modifications submitted in the preset time interval are subject to the modification received firstly, and the other modifications are invalid, so that the timeliness of the modification of the configuration data can be ensured on the basis of ensuring the consistency of the configuration data.

Fig. 12a and 12b respectively show that a user logs in the collaboration platform at the desktop end to perform a work unit operation, where fig. 12a shows that the user has opened a work file, at this time, the cloud end has updated configuration content, and fig. 12b shows that the user is opening the work file.

Specifically, as shown in fig. 12a, when the project configuration version in the cloud is updated, the tool end receives a prompt. When the configuration content of the tool end project is changed and submitted to the cloud end, the version of the cloud end is actually promoted, so that other tool end users can be informed. For all instantiations covered as described in FIG. 12a, for the tool side of the desktop side, it implements the process: searching system type data downloaded from a cloud, such as name, classification, code number, available accessory combination and the like, for a system type object of GMEP software, such as C + + class, in a current file according to the GUID of each system type entry: IMepSystemType, which is found to cover its data, such as name, category, code number, available accessory combinations, etc. Similarly, the data of the pipe fitting combination downloaded at the cloud may also find the pipe type object in the current file, such as C + + class: IMepCurveType and covers its data such as name, connection mode, component family, specification list, material, etc.

As shown in fig. 12b, the determination of whether to open the cache is performed, that is, the cache is opened at the tool side, and if the tool side has content that is not submitted to the cloud, the tool side has a flash back and has not yet submitted, the tool side can be opened from the cache when the work unit is opened next time. The cloud open work unit here means that the user has not selected to open from the cache and has opened the submitted version on the cloud.

In this embodiment, a configuration device of a collaborative project is further provided, and the configuration device is used for implementing the foregoing embodiments and preferred embodiments, and the description of which is already given is omitted. 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 configuration apparatus of a collaborative project, as shown in fig. 15, including:

the receiving module 51 is configured to receive a current version of the target collaborative project pushed by the cloud;

a comparison module 52, configured to compare the current version with a local storage version of the target collaborative project;

the first updating module 53 is configured to update the configuration data of the stored version with the configuration data of the current version based on the comparison result, or upload the configuration data of the stored version to the cloud to update the configuration data of the current version.

The configuration device for the collaborative project provided by this embodiment utilizes the combination mode of the cloud and the client, and takes the current version of the cloud as a guide, and no matter whether the cloud or the client modifies the configuration data of the target collaborative project, the current version of the cloud needs to be modified, so as to determine the consistency of the project configuration data of all users under the target collaborative project, and the modification of the configuration data has real-time performance.

The present embodiment provides a configuration apparatus of a collaborative project, as shown in fig. 16, including:

an obtaining module 61, configured to obtain a modification to configuration data of a target collaborative project;

a second updating module 62, configured to update the configuration data of the current version of the target collaborative project based on the modification of the configuration data;

a pushing module 63, configured to push the current version of the target collaborative project to each desktop end, so that each desktop end updates, in real time, configuration data of the stored version of the target collaborative project at the desktop end.

According to the configuration device for the collaborative project, when the configuration data is modified, the cloud end not only modifies the configuration data of the current version, but also pushes modification information to each desktop end, so that each desktop end updates the configuration data of the corresponding storage version in real time, and the consistency of the configuration data is ensured.

The configuration means of the coordination entities in this embodiment are presented in the form of functional units, where a unit refers to an ASIC circuit, a processor and a memory executing one or more software or fixed programs, and/or other devices that can 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.

An embodiment of the present invention further provides an electronic device, which has the configuration apparatus for collaborative items shown in fig. 15 or the configuration apparatus for collaborative items shown in fig. 16.

Referring to fig. 17, fig. 17 is a schematic structural diagram of an electronic device according to an alternative embodiment of the present invention, and as shown in fig. 17, the electronic device may include: at least one processor 71, such as a CPU (Central Processing Unit), at least one communication interface 73, memory 74, at least one communication bus 72. Wherein a communication bus 72 is used to enable the connection communication between these components. The communication interface 73 may include a Display (Display) and a Keyboard (Keyboard), and the optional communication interface 73 may also include a standard wired interface and a standard wireless interface. The Memory 74 may be a high-speed RAM Memory (volatile Random Access Memory) or a non-volatile Memory (non-volatile Memory), such as at least one disk Memory. The memory 74 may alternatively be at least one memory device located remotely from the processor 71. Wherein the processor 71 may be in connection with the apparatus described in fig. 15 or fig. 16, an application program is stored in the memory 74, and the processor 71 calls the program code stored in the memory 74 for performing any of the above-mentioned method steps.

The communication bus 72 may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus. The communication bus 72 may be divided into an address bus, a data bus, a control bus, and the like. For ease of illustration, only one thick line is shown in FIG. 17, but this does not mean only one bus or one type of bus.

The memory 74 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); the memory 74 may also comprise a combination of memories of the kind described above.

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

The processor 71 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, the memory 74 is also used for storing program instructions. The processor 71 may call program instructions to implement the configuration method of the collaborative project as shown in the embodiments of fig. 4-6 and fig. 10-12 b of the present application.

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 configuration method of the collaborative project 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 configuration method of a collaborative project, comprising:

2. The configuration method according to claim 1, wherein when the current version is higher than the stored version, the updating the configuration data of the stored version with the configuration data of the cloud based on the comparison result includes:

acquiring the configuration data of the current version from the cloud;

3. The configuration method according to claim 2, wherein the obtaining the current version of the configuration data from the cloud includes:

4. The configuration method of claim 3, wherein the updating the stored version of configuration data based on the current version of configuration data comprises:

forcibly updating the configuration data of the storage version;

5. The method according to claim 2, wherein the updating the stored version of configuration data based on the current version of configuration data comprises:

6. The configuration method of claim 5, wherein the updating the stored version of configuration data based on the configuration data further comprises:

7. The method according to claim 2, wherein the updating the stored version of configuration data based on the current version of configuration data comprises:

acquiring a current data table corresponding to the storage version;

establishing a target data table by using the current data table;

8. The configuration method according to claim 1, wherein when the current version is the same as the stored version, the uploading the configuration data of the stored version to the cloud to update the configuration data of the cloud comprises:

9. A configuration method of a collaborative project, comprising:

acquiring modification of configuration data of a target collaborative project;

10. The configuration method according to claim 9, wherein the modification of the configuration data is submitted by at least two of the desktop ends within a preset time interval, and the updating of the configuration data of the current version of the target collaborative project based on the modification of the configuration data comprises:

11. An apparatus for configuring a collaborative project, comprising:

12. An apparatus for configuring a collaborative project, comprising:

13. 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 method of configuring a collaborative project according to any one of claims 1-8 or any one of claims 9-10.

14. A computer-readable storage medium storing computer instructions for causing a computer to execute the method of configuring a collaborative project according to any one of claims 1-8 or any one of claims 9-10.