CN110995844B - Multi-person collaborative design method, device, equipment and computer readable storage medium - Google Patents
Multi-person collaborative design method, device, equipment and computer readable storage medium Download PDFInfo
- Publication number
- CN110995844B CN110995844B CN201911243365.6A CN201911243365A CN110995844B CN 110995844 B CN110995844 B CN 110995844B CN 201911243365 A CN201911243365 A CN 201911243365A CN 110995844 B CN110995844 B CN 110995844B
- Authority
- CN
- China
- Prior art keywords
- client
- server
- change information
- project
- instruction
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1095—Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06T—IMAGE DATA PROCESSING OR GENERATION, IN GENERAL
- G06T13/00—Animation
- G06T13/20—3D [Three Dimensional] animation
Abstract
The disclosure provides a method, a device, equipment and a computer readable storage medium for multi-person collaborative design. The method comprises the steps that a server receives a first editing instruction sent by any one first client in an engineering team, and scene change information is determined according to the first editing instruction; and the server synchronizes the scene change information to each client in the project team so that each client synchronizes a 3D picture in the project according to the scene change information. According to the method, the equipment, the device and the computer readable storage medium, the change information is synchronized to all the clients through the server, and all the clients cooperatively work, so that the working efficiency is improved.
Description
Technical Field
The present disclosure relates to data synchronization technologies, and in particular, to a method, an apparatus, a device, and a computer-readable storage medium for multi-user collaborative design.
Background
At present, with the development of technology, 3D pictures are more and more commonly applied in various fields, so that a design method of the 3D picture also needs to be continuously advanced.
In the prior art, a 3D picture is edited by a client, so that the 3D picture is edited.
In the prior art, when a 3D picture is designed, only a single client end is used for engineering editing, so that the problems of low working efficiency and long time consumption for completing the work are caused.
Disclosure of Invention
The disclosure provides a method, a device, equipment and a computer readable storage medium for multi-person collaborative design, which are used for solving the problems of low working efficiency and long time consumption for completing work caused by only a single client end for engineering editing when a 3D picture is designed in the prior art.
A first aspect of the present disclosure is to provide a multi-person collaborative design method, including:
the method comprises the steps that a server receives a first editing instruction sent by any one first client in an engineering team, and scene change information is determined according to the first editing instruction;
and the server synchronizes the scene change information to each client in the project team so that each client synchronizes a 3D picture in the project according to the scene change information.
Specifically, the clients in the engineering team comprise a main creation client and an auxiliary client;
the method further comprises the following steps:
the server receives a project creating instruction sent by the main creation client and creates a project according to the project creating instruction;
and the server receives an invitation instruction sent by the main creation client and grants the auxiliary client the authority to edit the project according to the invitation instruction.
Specifically, if the first editing instruction includes an object identifier existing in the 3D picture, after the server receives the first editing instruction sent by any first client in the engineering team, the method further includes:
the server determines that the object identifier and the first client identifier have a binding relationship.
Specifically, still include:
the server receives a second editing instruction sent by a second client in the engineering team, wherein the second editing instruction comprises the object identifier;
and the server determines that the server has a binding relationship with the first client identifier according to the object identifier, and feeds back a message that the object is being edited to the second client.
Specifically, the objects in the project have a hierarchical relationship;
the method further comprises the following steps:
the server receives a deleting instruction sent by a client in the engineering team, wherein the deleting instruction comprises an object identifier to be deleted;
the server determines whether the hierarchy of the object to be deleted comprises other objects or not according to the identifier of the object to be deleted, and determines whether the identifiers of the other objects are being edited or not;
and if the object to be deleted comprises other objects on the hierarchy and the other objects are being edited, the server feeds back a message of rejecting deletion to the client.
Specifically, still include:
the server responds to a third editing instruction of the user and determines second scene change information according to the third editing instruction;
and the server synchronizes the second scene change information to each client in the engineering team so that each client synchronizes a 3D picture in the engineering according to the second scene change information.
Specifically, still include:
the server responds to a second project creating instruction of the user to create a project;
and the server responds to a second invitation instruction of the user and grants the corresponding client side the authority to edit the project.
Another aspect of the present disclosure is to provide a multi-person collaborative design apparatus, including:
the system comprises a first editing instruction receiving module, a scene change information determining module and a scene change information determining module, wherein the first editing instruction receiving module is used for receiving a first editing instruction sent by any first client in an engineering team and determining scene change information according to the first editing instruction;
and the synchronization module is used for synchronizing the scene change information to each client in the engineering team so that each client synchronizes the 3D picture in the engineering according to the scene change information.
Yet another aspect of the present disclosure is to provide a multi-person collaborative design apparatus, including:
a memory;
a processor; and
a computer program;
wherein the computer program is stored in the memory and configured to be executed by the processor to implement the multi-person co-design method as described in the first aspect above.
Yet another aspect of the present disclosure is to provide a computer-readable storage medium having stored thereon a computer program to be executed by a processor to implement the multi-person co-design method as described in the first aspect above.
The technical effects of the method, the device, the equipment and the computer-readable storage medium for multi-person collaborative design provided by the disclosure are as follows: the method comprises the steps that a server receives a first editing instruction sent by any first client in an engineering team, scene change information is determined according to the first editing instruction, and the server synchronizes the scene change information to each client in the engineering team, so that each client synchronizes a 3D picture in the engineering according to the scene change information. According to the scheme provided by the disclosure, the change information is synchronized to all the clients through the server, and all the clients cooperatively operate, so that the working efficiency is improved.
Drawings
Fig. 1 is a system architecture diagram illustrating a method for multi-person collaborative design according to an exemplary embodiment of the present invention;
FIG. 2 is a flow chart illustrating a method for multi-person collaborative design in accordance with an exemplary embodiment of the present invention;
FIG. 3 is a flow chart illustrating a method for multi-person collaborative design in accordance with another exemplary embodiment of the present invention;
fig. 4 is a structural diagram of a multi-user collaborative design apparatus according to an embodiment of the present invention;
fig. 5 is a block diagram illustrating a multi-person collaborative design apparatus according to another exemplary embodiment of the present invention;
fig. 6 is a block diagram illustrating a multi-person collaborative design apparatus according to an exemplary embodiment of the present invention.
Detailed Description
Fig. 1 is a system architecture diagram illustrating a method for multi-person collaborative design according to an exemplary embodiment of the present invention.
As shown in fig. 1, the system architecture may include a client 101, a server 102.
The connection between the client 101 and the server 102 may be through a network, and may specifically include various connection types, such as wired, wireless communication links, or fiber optic cables, among others. The client 101 may be a computer used by a user, and the server 102 may be, for example, a computer providing a service.
The server may be hardware or software. When the server is hardware, it may be implemented as a distributed server cluster formed by multiple servers, or may be implemented as a single server. When the server is software, it may be implemented as multiple pieces of software or software modules (e.g., to provide distributed services), or as a single piece of software or software module. And is not particularly limited herein.
It should be understood that the number of clients and servers in fig. 1 is merely illustrative. There may be any number of clients and servers, as desired for an implementation.
In one embodiment, the server may be a cloud server, i.e., the server is mainly used for synchronizing scene information. In another embodiment, the server and each client may be in a local area network, in this case, a terminal operated by any user may be used as the server, and the server provides a scene information synchronization function, and at the same time, the user may also operate the server to modify a 3D picture in a project.
Fig. 2 is a flowchart illustrating a method for multi-person collaborative design according to an exemplary embodiment of the present invention.
As shown in fig. 2, the multi-user collaborative design method provided in this embodiment includes:
The method provided by this embodiment may be executed by an electronic device with computing capability, for example, a server in the system architecture shown in fig. 1.
Specifically, the engineering team can comprise a plurality of clients, and users can operate different clients, so that people can simultaneously set a server for one engineering project to receive a first editing instruction sent by any first client in the engineering team, and determine a scene change information meter according to the first editing instruction. The project is, for example, a 3D screen, which team members may design together, for example, member a may add a light to the 3D screen, and member B may add a sofa to the 3D screen.
Specifically, the clients in the engineering team comprise a main creation client and an auxiliary client.
The main creation client sends a project creation instruction to enable the server to create a project, the auxiliary client and the main creation client edit the 3D picture together, change information is sent to the server, and the server receives the change information and synchronizes the change information to all the clients. When a worker edits a 3D picture, a server receives a first editing instruction sent by any first client in an engineering team, and determines scene change information according to the first editing instruction, wherein the first editing instruction can comprise various instructions such as adding, changing, moving, adjusting and deleting the picture, and the instruction can also comprise an identifier of an edited object, a moving position, an adjusting parameter and the like.
After receiving the first editing instruction, the server may determine scene change information according to the instruction. Specifically, parameters such as an object identifier and a position in the first editing instruction may be extracted, and how to modify the 3D picture may be determined according to the parameters, so as to obtain scene change information. For example, a table needs to be added to a 3D picture, any first client sends a first editing instruction to the server, the content of the first editing instruction includes an identifier of the table and an adding position, the server receives the first editing instruction and edits the picture, scene change information is determined according to the editing instruction, and the server synchronizes the scene change information to all clients.
Specifically, if a worker wants to design a 3D screen, the main creation client sends a project creation instruction to the server, the server creates a project, and then all screen edits are performed in the project.
Generally, the workload of creating a 3D screen is large, and multiple workers are needed to complete the screen, so that multiple auxiliary clients are needed to edit the screen. After the creation project is completed, the main creation client can send an invitation instruction to the server, and the server receives the invitation instruction and invites the auxiliary client according to the invitation instruction. The auxiliary client can be granted the editing authority to ensure that the auxiliary client obtains the authority for editing the project.
Many objects may be included in one 3D picture project. These objects may also have a hierarchical relationship between them. For example, a screen is set in the 3D picture, and in the time dimension, the screen needs to show video 1 in sequence for a time period of t1-t2, still picture 2 for a time period of t2-t3, and video 3 for a time period of t3-t 4. In this case, the screen in the 3D screen is an object, and the video 1, the still picture 2, the video 3, and the corresponding presentation times thereof are 3 objects, respectively, and are editable. Among these four objects, the screen is an underlying object, and video 1, still picture 2, and video 3 are objects disposed above this level of the screen.
When a worker wishes to delete any object of the project, the server may receive a delete instruction sent by a client in the project team. The server may determine, according to the deletion instruction, an identifier of the object to be deleted, determine, according to the identifier of the object to be deleted, whether the hierarchy where the object to be deleted is located includes another object, and determine whether the identifier of the other object is being edited, and if the hierarchy of the object to be deleted includes another object and the other object is being edited, the server feeds back a message of rejecting deletion to the client. For example, there are three objects in the hierarchy where the object to be deleted is located, which are object 1, object 2, and object 3, respectively, the auxiliary client 1 needs to delete the object 3, and if the auxiliary client 2 is editing the object 2 at this time, the server sends information of rejecting deletion to the auxiliary client 1 at this time; if the assistant client does not edit the object 1 or the object 2 at this time, the assistant client can perform a deletion operation.
The server synchronizes the scene change information to all clients so that all clients can adjust the 3D picture according to the received information, thereby making the pictures displayed by each client consistent. For example: the number of the clients is 3, a table is added in a picture of the client 1, the position of a chair is moved by the client 2, the brightness of the lamp is adjusted by the client 3, the three clients send corresponding editing instructions to the server, and the server determines corresponding scene change information according to the editing instructions and synchronizes the determined information to each client.
And after receiving the scene change information, the client adjusts the picture according to the change information. For example, if the change information is to delete a table, the object identifier of the table is 1, and the action is to delete, the client deletes the table with the object identifier of 1 based on the change information.
Since the scene change information received by each client is the same, the 3D picture adjusted based on the information is also the same, so that the 3D pictures in each client are kept consistent.
The multi-person collaborative design method provided by the embodiment comprises the following steps: the method comprises the steps that a server receives a first editing instruction sent by any one first client in an engineering team, and scene change information is determined according to the first editing instruction; and the server synchronizes the scene change information to each client in the project team so that each client synchronizes a 3D picture in the project according to the scene change information. The server synchronizes the change information to all the clients, so that all the clients cooperatively operate, and the working efficiency is improved.
Fig. 3 is a flowchart illustrating a method of multi-person collaborative design according to another exemplary embodiment of the present invention.
As shown in fig. 3, the method for multi-person collaborative design provided by this embodiment includes:
step 301, the server receives a project creation instruction sent by the main creation client, and creates a project according to the project creation instruction.
If the staff wants to design a 3D picture, the main creation client sends a project creation instruction to the server, the server creates a project, and all pictures are edited in the project.
Step 302, the server receives an invitation instruction sent by the main creation client, and grants the auxiliary client the authority to edit the project according to the invitation instruction.
The design process of one 3D picture is complex and can be completed only by the cooperation of a plurality of designers, so that the main creation client can send an invitation instruction to the server after the creation project is completed, and the invitation instruction can include identification information corresponding to the invited auxiliary client, specifically, a nickname of a certain designer, an equipment address where the auxiliary client is installed, and the like.
The server invites the auxiliary client according to the invitation instruction, grants the editing permission of the auxiliary client, so that the auxiliary client obtains the permission for editing the project, the auxiliary client and the main creation client edit the project together, and the efficiency is improved. Specifically, the corresponding editing right of the auxiliary client can be granted according to the identification information included in the invitation instruction.
Optionally, the invitation instruction may further include a project identifier, so that the server grants an editing right for the corresponding project to the invited auxiliary client.
Step 303, the server receives a first editing instruction sent by any first client in the engineering team.
And 304, determining scene change information according to the first editing instruction, and synchronizing the scene change information to each client in the engineering team.
The steps 303-304 are similar to the specific principle and implementation manner of the step 201, and are not described herein again.
After step 303, step 305 may also be performed.
If the first editing instruction includes an object identifier already existing in the 3D frame, that is, the first client needs to edit an object already existing in the 3D frame, step 305 may be executed.
When the first client side needs to edit the object in the project, the server can also bind the first client side identification and the object identification needing to be edited, so that the situation that other client sides edit the object at the moment and conflict occurs is avoided. For example, the first editing instruction needs to delete a table whose object identifier is object 1, and at this time, object 1 is bound to the identifier of the first client, and the server may determine that the object identifier has a binding relationship with the identifier of the first client.
The timing for executing steps 304 and 305 is not limited.
Step 306 may also be included after step 305.
When the first client edits the 3D screen, the second client may also process the 3D screen. In one case, it is possible that the object that the second client wishes to edit is the same as the object that the first client is currently editing. That is, the second editing instruction includes the object identifier described in step 305.
The server may also receive a second editing instruction sent by the second client while receiving the first editing instruction of the first client, and if the second editing instruction includes the object identifier in the first editing instruction, step 307 is executed.
The server determines that the object identifier in the second editing instruction is bound with the first client identifier, and then the server feeds back a message that the object is being edited to the second client. For example, if the first editing instruction needs to delete a table, and the object identifier of the table is object 1, the first client identifier is bound to object 1, and if the second editing instruction sent by the second client also contains object 1 at this time, the server feeds back a message that object 1 is being edited to the second client. Therefore, the conflict situation caused by editing the same object in the 3D picture by different clients is avoided.
Optionally, the embodiment may further include step 308, and specifically, after any step 303 and 307, the step 308 may be executed.
Step 308, the server receives a deletion instruction sent by a client in the engineering team, wherein the deletion instruction includes an object identifier to be deleted.
When a designer needs to delete an object, the designer can operate in the client and send a deletion instruction to the server, wherein the deletion instruction comprises an identifier of the object to be deleted. For example, if the designer wishes to delete a sofa in the screen, the delete instruction includes an identification of the sofa.
And the server determines whether the hierarchy of the object to be deleted comprises other objects according to the object identifier in the deletion instruction, and determines whether the identifiers of the other objects are being edited. For example, if there are three objects on a hierarchy, i.e., object 1, object 2, and object 3, and if the object 1 is being edited, when the server receives a delete instruction, the object to be deleted in the delete instruction is identified as object 2, the server determines that there are other objects in the hierarchy of the object to be deleted, and the other objects are being edited, then step 310 is performed, and if none of the three objects in the hierarchy is edited, the delete instruction may perform the operation of deleting object 2. For another example, if only the object 2 exists on the hierarchy, the server may execute the operation of deleting the object 2 when receiving a deletion instruction for deleting the object 2.
In step 310, if the object to be deleted includes other objects on the hierarchy and the other objects are being edited, the server feeds back a message rejecting deletion to the client.
For example, there are three objects on a hierarchy, namely an object 1, an object 2, and an object 3, and at this time, the object 1 is being edited, when the server receives a deletion instruction of the first client, an object to be deleted in the deletion instruction is identified as the object 2, the server determines that there are other objects in the hierarchy of the object to be deleted, and the other objects are being edited, and the server feeds back a message rejecting deletion to the first client.
Optionally, in an implementation manner, the method provided in this embodiment may further include:
the server responds to a third editing instruction of the user and determines second scene change information according to the third editing instruction;
and the server synchronizes the second scene change information to each client in the engineering team so that each client synchronizes a 3D picture in the engineering according to the second scene change information.
That is, in an alternative embodiment, the server may be operated by a user, for example, the server may belong to the same local area network as the other clients in the engineering team. In this embodiment, the user can operate the server to edit the 3D screen in the project, such as adding some objects in the 3D screen, and adjusting the position of the existing objects.
The server may generate a third editing instruction in response to the user operation, and generate corresponding second scene change information based on the third editing instruction, where the information may include, for example, an object identifier, an object location, and the like. The server may also synchronize the generated second scene change information to other clients, so that the other clients synchronize the 3D picture in the project according to the scene change information.
In addition, when the server receives editing instructions sent by other clients, scene change information can be generated according to the editing instructions, and the 3D picture of the server can be synchronized according to the scene change information.
That is, in the method provided in this embodiment, the server may be used to synchronize the scene change information generated when the user operates another client, or may synchronize the scene change information generated when the user operates the server itself to another client, so that the 3D images between the server and the clients are synchronized.
Optionally, before creating the project, the user may further operate a client to create a project. In this case, the client is the server. After receiving a second project creation instruction of the user, the server can create a project in response to the creation instruction.
When the user operates, the project type, the name and the like can be specifically defined.
After the completion project is created, the user may also operate the server, inviting other users to jointly design the project. For example, the user may enter the identifiers of other users, and then the server responds to the second invitation instruction of the user to grant the corresponding client the right to edit the project.
In the scheme provided by the embodiment, a server does not need to be separately arranged, and a terminal operated by a user can be used as the server, so that the cost of the whole system is saved. Fig. 4 is a block diagram illustrating a multi-person collaborative design apparatus according to an exemplary embodiment of the present invention.
As shown in fig. 4, the multi-user collaborative design apparatus provided in this embodiment includes:
a first editing instruction receiving module 41, configured to receive a first editing instruction sent by any first client in an engineering team, and determine scene change information according to the first editing instruction;
a synchronization module 42, configured to synchronize the scene change information to each client in the engineering team, so that each client synchronizes a 3D picture in the engineering according to the scene change information.
The multi-person collaborative design device provided by the embodiment comprises a first editing instruction receiving module and a synchronization module, wherein the first editing instruction receiving module is used for receiving a first editing instruction sent by any first client in an engineering team by a server and determining scene change information according to the first editing instruction; and the synchronization module is used for enabling the server to synchronize the scene change information to each client in the project team so that each client can synchronize the 3D picture in the project according to the scene change information. The working efficiency is improved through the collaborative design of the plurality of clients, and the change information is synchronized to all the clients, so that the editing process is more accurate and efficient.
The specific principle and implementation of the multi-user collaborative design apparatus provided in this embodiment are similar to those of the embodiment shown in fig. 2, and are not described herein again.
Fig. 5 is a block diagram illustrating a multi-person collaborative design apparatus according to another exemplary embodiment of the present invention.
On the basis of the above embodiment, the client in the engineering team includes a main creation client and an auxiliary client;
the device further comprises:
the project creation module 51 is configured to receive a project creation instruction sent by the main creation client, and create a project according to the project creation instruction;
and the authorization module 52 is configured to receive the invitation instruction sent by the primary creation client, and grant the permission for the secondary client to edit the project according to the invitation instruction.
A binding module 53, configured to determine that a binding relationship exists between an object identifier and a first client identifier after the first editing instruction receiving module 41 receives a first editing instruction sent by any first client in an engineering team if the first editing instruction includes the object identifier existing in the 3D picture.
A second editing instruction receiving module 54, configured to receive a second editing instruction sent by a second client in the engineering team, where the second editing instruction includes the object identifier;
and a feedback module 55, configured to determine, according to the object identifier, that there is a binding relationship between the object identifier and the first client identifier, and feed back a message that the object is being edited to the second client.
Optionally, the objects in the project have a hierarchical relationship;
the device further comprises:
a deleting instruction receiving module 56, configured to receive a deleting instruction sent by a client in the engineering team, where the deleting instruction includes an identifier of an object to be deleted;
a judging module 57, configured to determine, according to the identifier of the object to be deleted, whether the hierarchy where the object to be deleted is located includes other objects, and determine whether the identifiers of the other objects are being edited;
a deletion refusing module 58, configured to feed back a deletion refusing message to the client if the object to be deleted includes other objects on the hierarchy and the other objects are being edited.
Optionally, the synchronization module 42 is further configured to:
responding to a third editing instruction of the user, and determining second scene change information according to the third editing instruction;
and synchronizing the second scene change information to each client in the engineering team so that each client synchronizes the 3D picture in the engineering according to the second scene change information.
The project creating module 51 is further configured to create a project in response to a second project creating instruction of the user;
the authorization module 52 is further configured to respond to a second invitation instruction of the user, and grant the corresponding client a right to edit the project.
The specific principle and implementation of the multi-user collaborative design apparatus provided in this embodiment are similar to those of the embodiment shown in fig. 3, and are not described herein again.
Fig. 6 is a block diagram illustrating a multi-person collaborative design apparatus according to an exemplary embodiment of the present invention.
As shown in fig. 6, the multi-person collaborative design apparatus provided by this embodiment includes:
a memory 61;
a processor 62; and
a computer program;
wherein the computer program is stored in the memory 61 and configured to be executed by the processor 62 to implement any of the multi-person co-design methods as described above.
The present embodiments also provide a computer-readable storage medium, having stored thereon a computer program,
the computer program is executed by a processor to implement any of the multi-person co-design methods described above.
The present embodiment also provides a computer program, which includes a program code, and when the computer program is executed by a computer, the program code executes any one of the above-described multi-person collaborative design methods.
Those of ordinary skill in the art will understand that: all or a portion of the steps of implementing the above-described method embodiments may be performed by hardware associated with program instructions. The program may be stored in a computer-readable storage medium. When executed, the program performs steps comprising the method embodiments described above; and the aforementioned storage medium includes: various media that can store program codes, such as ROM, RAM, magnetic or optical disks.
Finally, it should be noted that: the above embodiments are only used to illustrate the technical solution of the present invention, and not to limit the same; while the invention has been described in detail and with reference to the foregoing embodiments, it will be understood by those skilled in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some or all of the technical features may be equivalently replaced; and the modifications or the substitutions do not make the essence of the corresponding technical solutions depart from the scope of the technical solutions of the embodiments of the present invention.
Claims (9)
1. A multi-person collaborative design method is characterized by comprising the following steps:
the method comprises the steps that a server receives a first editing instruction sent by any first client in an engineering team, and scene change information is determined according to the first editing instruction;
the server synchronizes the scene change information to each client in the project team so that each client synchronizes a 3D picture in the project according to the scene change information;
objects in the project have a hierarchical relationship;
the method further comprises the following steps:
the server receives a deleting instruction sent by a client in the engineering team, wherein the deleting instruction comprises an object identifier to be deleted;
the server determines whether the hierarchy of the object to be deleted comprises other objects or not according to the identifier of the object to be deleted, and determines whether the identifiers of the other objects are being edited or not;
and if the object to be deleted comprises other objects on the hierarchy and the other objects are being edited, the server feeds back a message of rejecting deletion to the client.
2. The method of claim 1, wherein the clients in the engineering team comprise a primary client, a secondary client;
the method further comprises the following steps:
the server receives a project creating instruction sent by the main creation client and creates a project according to the project creating instruction;
and the server receives an invitation instruction sent by the main creation client and grants the auxiliary client the authority to edit the project according to the invitation instruction.
3. The method according to claim 1, wherein if the first editing instruction includes an object identifier existing in the 3D screen, after the server receives the first editing instruction sent by any first client in an engineering team, the method further includes:
the server determines that the object identifier and the first client identifier have a binding relationship.
4. The method of claim 3, further comprising:
the server receives a second editing instruction sent by a second client in the engineering team, wherein the second editing instruction comprises the object identifier;
and the server determines that the server has a binding relationship with the first client identifier according to the object identifier, and feeds back a message that the object is being edited to the second client.
5. The method of any one of claims 1, 3, and 4, further comprising:
the server responds to a third editing instruction of the user and determines second scene change information according to the third editing instruction;
and the server synchronizes the second scene change information to each client in the engineering team so that each client synchronizes a 3D picture in the engineering according to the second scene change information.
6. The method of claim 5, further comprising:
the server responds to a second project creating instruction of the user to create a project;
and the server responds to a second invitation instruction of the user and grants the corresponding client side the authority to edit the project.
7. A multi-person collaborative design apparatus, comprising:
the system comprises a first editing instruction receiving module, a scene change information determining module and a scene change information determining module, wherein the first editing instruction receiving module is used for receiving a first editing instruction sent by any first client in an engineering team and determining scene change information according to the first editing instruction;
the synchronization module is used for synchronizing the scene change information to each client in the engineering team so that each client can synchronize a 3D picture in the engineering according to the scene change information;
objects in the project have a hierarchical relationship;
the device further comprises:
the system comprises a deleting instruction receiving module, a deleting instruction receiving module and a deleting module, wherein the deleting instruction receiving module is used for receiving a deleting instruction sent by a client in the engineering team, and the deleting instruction comprises an object identifier to be deleted;
the judging module is used for determining whether the hierarchy of the object to be deleted comprises other objects or not according to the identifier of the object to be deleted and determining whether the identifiers of the other objects are edited or not;
and the deletion refusing module is used for feeding back a deletion refusing message to the client if the object to be deleted comprises other objects on the hierarchy and the other objects are being edited.
8. A multi-person collaborative design apparatus, comprising:
a memory;
a processor; and
a computer program;
wherein the computer program is stored in the memory and configured to be executed by the processor to implement the method of any of claims 1-4.
9. A computer-readable storage medium, having stored thereon a computer program for execution by a processor to perform the method of any one of claims 1-4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911243365.6A CN110995844B (en) | 2019-12-06 | 2019-12-06 | Multi-person collaborative design method, device, equipment and computer readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911243365.6A CN110995844B (en) | 2019-12-06 | 2019-12-06 | Multi-person collaborative design method, device, equipment and computer readable storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110995844A CN110995844A (en) | 2020-04-10 |
| CN110995844B true CN110995844B (en) | 2022-06-21 |
Family
ID=70090993
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911243365.6A Active CN110995844B (en) | 2019-12-06 | 2019-12-06 | Multi-person collaborative design method, device, equipment and computer readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110995844B (en) |
Families Citing this family (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111563727A (en) * | 2020-05-06 | 2020-08-21 | 厦门知本家科技有限公司 | Method and system for multi-person online collaborative editing of 3D house type data |
| CN112699184A (en) * | 2021-01-13 | 2021-04-23 | 广州视源电子科技股份有限公司 | Information cooperation method, device, storage medium and server |
| CN113793133A (en) * | 2021-09-26 | 2021-12-14 | 北京明略昭辉科技有限公司 | Team calendar processing method and system, electronic device and storage medium |
| CN113988801B (en) * | 2021-10-27 | 2023-11-10 | 北京百度网讯科技有限公司 | Office system, work task management method and device |
| CN116016491B (en) * | 2022-12-26 | 2023-09-05 | 山东华方智联科技股份有限公司 | Intelligent building design system and design method |
| CN117113942B (en) * | 2023-10-24 | 2024-02-20 | 杭州百子尖科技股份有限公司 | Model synchronization method and device, electronic equipment and storage medium |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1787443A (en) * | 2005-12-02 | 2006-06-14 | 无锡永中科技有限公司 | Method for realizing file coordination processing |
| CN102866919A (en) * | 2012-07-31 | 2013-01-09 | 电子科技大学 | Cloud drawing-based large-sized three-dimensional scene multi-person collaborative creation method |
| CN103854300A (en) * | 2012-12-07 | 2014-06-11 | 江苏省电力公司 | Method for achieving three-dimensional scene cooperation carrying under networking control of client sides |
| CN107408142A (en) * | 2015-02-25 | 2017-11-28 | 昂沙普公司 | 3D CAD systems based on multi-user's cloud parameter attribute |
Family Cites Families (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP1526457B1 (en) * | 2003-10-22 | 2013-03-13 | Sony Deutschland GmbH | Context-aware automatic service discovery and execution engine in mobile ad-hoc networks |
| US20070174027A1 (en) * | 2006-01-26 | 2007-07-26 | Aleksey Moiseyev | Synchronized architectural and structural CAD models |
| EP2780826B1 (en) * | 2011-11-15 | 2020-08-12 | Trimble Inc. | Browser-based collaborative development of a 3d model |
| CN103279347B (en) * | 2013-05-28 | 2016-03-30 | 复旦大学 | The synchronous method of a kind of general software product line domain model and application model |
| CN103297529B (en) * | 2013-06-06 | 2016-01-20 | 浙江大学 | Based on the tree-type structure data synchronous method of timestamp |
| CN107193545B (en) * | 2017-04-07 | 2020-07-10 | 广东省科技基础条件平台中心 | Component-oriented multi-language collaborative development device, method and system |
-
2019
- 2019-12-06 CN CN201911243365.6A patent/CN110995844B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1787443A (en) * | 2005-12-02 | 2006-06-14 | 无锡永中科技有限公司 | Method for realizing file coordination processing |
| CN102866919A (en) * | 2012-07-31 | 2013-01-09 | 电子科技大学 | Cloud drawing-based large-sized three-dimensional scene multi-person collaborative creation method |
| CN103854300A (en) * | 2012-12-07 | 2014-06-11 | 江苏省电力公司 | Method for achieving three-dimensional scene cooperation carrying under networking control of client sides |
| CN107408142A (en) * | 2015-02-25 | 2017-11-28 | 昂沙普公司 | 3D CAD systems based on multi-user's cloud parameter attribute |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110995844A (en) | 2020-04-10 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110995844B (en) | Multi-person collaborative design method, device, equipment and computer readable storage medium | |
| CN103885788B (en) | Dynamic WEB 3D virtual reality scene construction method and system based on model componentization | |
| CN106850788B (en) | Integrated framework and integrated approach towards multi-source heterogeneous geographic information resources | |
| Buchanan et al. | Scheduling multimedia documents using temporal constraints | |
| US11080941B2 (en) | Intelligent management of content related to objects displayed within communication sessions | |
| US10742434B2 (en) | Event-based content object collaboration | |
| CN108282544A (en) | Based on the existing convergent journalism making of media mysorethorn and dissemination system | |
| CN111401029B (en) | Document version updating system and method based on document partition and collaborative editing | |
| CN115599870B (en) | Data synchronization method based on fusion of stock data and incremental data of message queue | |
| CN105338287A (en) | Video conference control method and video conference control device | |
| CN105787632A (en) | Method and system for managing conference room | |
| CN110321123A (en) | Visual layout's management system and management method | |
| CN113785281A (en) | Messaging implementing operational serialization to achieve consistency of distributed data structures | |
| CN112463005A (en) | Multi-screen interaction method and device, computer equipment and storage medium | |
| CN114500570B (en) | Task processing method, device, electronic equipment and computer readable storage medium | |
| KR101733607B1 (en) | Method and system for managing of production of drama | |
| CN105047210B (en) | A kind of the striding equipment synchronous method and device of shuffle playlist | |
| CN106203967A (en) | Teleconference information exchange method based on BIM and system | |
| WO2023020092A1 (en) | Multi-person collaboration-based resource processing method, apparatus and system | |
| JP2017531879A (en) | Network cooperation method and machine applying the method | |
| CN115935916A (en) | Document auditing method, device, equipment, storage medium and program product | |
| KR20010064246A (en) | Collaborative group editor system using JAVA specific property on internet and method thereof | |
| US8612185B2 (en) | Device, system and method for simulating and saving information of metadata regarding film production | |
| CN108306981A (en) | The dual isomery PaaS redundancy approach of media cloud platform service layer safety can be enhanced | |
| Wang et al. | Research on consistency maintenance of the real-time image editing system based on bitmap |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |