Collaborative working method and apparatus involving fused space

Abstract

The present invention relates to the technical field of computers. Provided are a collaborative working method and apparatus involving a fused space. The method comprises: a collaborative application receiving an operation instruction for adding information blocks to a shared canvas working space in which the collaborative application has joined, wherein the information blocks comprise a first information block that bears and displays various types of web-end content; in response to the operation instruction, the collaborative application sending a first synchronization message to a server, such that the server sends the first synchronization message to each collaborative application which has joined in the shared canvas working space, wherein the first synchronization message is used for instructing to add an information block to each collaborative application; and when any collaborative application in the shared canvas working space obtains a speaker permission, a collaborative application which serves as a speaker side sends, to a collaborative application which serves as a listener side in the shared canvas working space, operation information with regard to an information block in an interaction interface of the collaborative application which serves as the speaker side, such that the collaborative application which serves as the listener side realizes, by means of the same information block in an interaction interface of the collaborative application which serves as the listener side, angle-of-view following with the collaborative application which serves as the speaker side. The present invention improves the collaboration efficiency in a shared canvas working space.

Description

A collaborative working method and device for integrating space

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to Chinese patent application number 2023112496647, filed with the Patent Office of China on September 25, 2023, entitled “A Collaborative Working Method and Device for Fusion Space”, the entire contents of which are incorporated herein by reference. Technical Field

[0003] The present application relates to the field of computer technology, and in particular to a collaborative working method and device for a fusion space. Background Art

[0004] Existing collaborative applications can support multiple terminal users to edit content and access and view the same workspace within the application. Each terminal user who joins the same workspace can be regarded as a collaborative member. Each collaborative member can create content such as notes, sticky notes, pictures, links, etc. in their respective collaborative applications, and these contents can be shared in the same workspace.

[0005] However, existing collaborative applications can only present linked content through hyperlinks. If you need to view the linked content in the current collaborative application, you must open the specific hyperlink and jump to the browser or call up a third-party application to view the content in a separate browser page or third-party application page.

[0006] Therefore, when end users use existing collaborative applications, they need to switch between multiple different browsers or third-party applications to view linked content, which leads to problems of inefficient collaboration and easy distraction of the attention of collaborative members.

[0007] Summary of the Invention

[0008] The technical problem to be solved by this application is that when end users use existing collaborative applications, they need to switch between multiple different browsers or third-party applications to view link content, which leads to low collaboration efficiency and easy distraction of the attention of collaborative members.

[0009] The technical problem that the present application further aims to solve is to provide a collaborative working method, device and system for a fusion space.

[0010] This application adopts the following technical solutions:

[0011] In a first aspect, the present application provides a collaborative working method for a fusion space, the method comprising:

[0012] The collaborative application receives an operation instruction to add an information block in a shared canvas workspace to which the collaborative application has joined, wherein the information block includes a first information block carrying various types of web-end content, wherein the various types of web-end content can be embedded in the first information block for display;

[0013] The collaborative application responds to the operation instruction and sends a first synchronization message to the server, so that the server sends the first synchronization message to each collaborative application that has joined the shared canvas workspace; the first synchronization message is used to instruct the addition of the information block in each collaborative application;

[0014] When any collaborative application in the shared canvas workspace obtains the speaker permission, the collaborative application on the speaker side sends the operation information in the information block in its own interactive interface to the collaborative application on the audience side in the shared canvas workspace, so that the collaborative application on the audience side can follow the perspective of the collaborative application on the speaker side through the same information block in its own interactive interface;

[0015] Among them, the collaborative application serving as the speaker is a collaborative application that has obtained the speaker permission in the shared canvas workspace, and the collaborative application serving as the audience is one or more collaborative applications in the shared canvas workspace that have not obtained the speaker permission and have confirmed to join the speaker process. The speaker process is initiated by the collaborative application serving as the speaker.

[0016] Preferably, the collaborative application on the speaker side sends the operation information in the information block in its own interactive interface to the collaborative application on the audience side in the shared canvas workspace, so that the collaborative application on the audience side can follow the perspective of the collaborative application on the speaker side through the same information block in its own interactive interface, specifically including:

[0017] When the second information block in the collaborative application serving as the speaker is edited, a follow-up message carrying identification information of the second information block and corresponding edited content is sent to the collaborative applications serving as the audience in the shared canvas workspace, so that the edited content of the speaker is synchronously presented in the same second information block in each collaborative application serving as the audience;

[0018] When the collaborative application on the speaker side switches from editing the second information block to performing operations in the first information block that carries various types of web content, a follow-up message carrying identification information of the first information block and corresponding operation content is sent to the collaborative application on the audience side in the shared canvas workspace; so that the operation content of the speaker side can be synchronously presented in the same first information block in each collaborative application on the audience side.

[0019] Preferably, when a new collaborative application temporarily joins the shared canvas workspace, wherein a first user ID is logged into the new collaborative application, the method further includes:

[0020] The collaborative application serving as the speaker receives a request message carrying the first user ID to join the shared canvas workspace;

[0021] The collaborative application serving as the main speaker returns a response message for confirming joining, wherein the response message for confirming joining is used to establish a perspective following relationship between the new collaborative application and the collaborative application serving as the main speaker.

[0022] Preferably, when the relationship between the speaker and the audience is not established, the operations of the collaborative applications on the same information block belonging to the same shared canvas workspace are in a serial relationship, and the method further includes:

[0023] When the same information block belonging to the same shared canvas workspace is not operated by any collaborative application, each collaborative application can obtain exclusive operation on the same information block belonging to the same shared canvas workspace in its interactive interface;

[0024] When any collaborative application takes an exclusive operation on any information block belonging to the same shared canvas workspace in its interactive interface, other collaborative applications that have not obtained the exclusive operation on the same information block belonging to the same shared canvas workspace will synchronously update the content of the preview area in the same information block they own to the operation content in the preview area of ​​the same information block in the collaborative application that currently obtains the exclusive operation.

[0025] Preferably, when the relationship between the speaker and the audience is not established, the operations of the collaborative applications on the same information block in the same shared canvas workspace are in a parallel relationship, and the method further includes:

[0026] When the same information block belonging to the same shared canvas workspace is the target information block on which each collaborative application can perform parallel operations in its interactive interface, each collaborative application receives the operation information performed on the target information block in its own interactive interface, and presents the operation results in the preview area of ​​the target information block in its own interactive interface.

[0027] Preferably, the collaborative application with review permission sends a request to the server to review the content in the preview area of ​​the same information block in each collaborative application that has been added to the same shared canvas workspace. The method further includes:

[0028] After obtaining the contents of the respective preview areas of the same information block from different collaborative applications in the same shared canvas workspace, the collaborative application with review permission mirrors a corresponding number of information blocks and presents the contents of the respective preview areas in each mirrored information block; or

[0029] After obtaining the contents of the respective preview areas of the same information block from different collaborative applications in the same shared canvas workspace, the collaborative application with review permission generates a corresponding number of switch pages in its own information block toolbar box corresponding to the number of different collaborative applications, where each switch page presents the contents of the preview area of ​​the same information block contained in a collaborative application.

[0030] Preferably, the method further comprises:

[0031] When the collaborative application on the speaker side obtains the information to be shared in the preview area of ​​the specified information block with the specified user ID, the collaborative application on the speaker side sends a request for sharing the specified information block content to the server; wherein the request for sharing the specified information block content carries the speaker side user ID, the specified user ID, the identification information of the specified information block, and the content carried in the preview area of ​​the specified information block.

[0032] Preferably, in each collaborative application, the added information blocks support respective adjustments, and the adjustments include one or more of enlargement, reduction, fading, rotation, and movement.

[0033] In a second aspect, the present application further provides a collaborative working method for a fusion space, the method comprising:

[0034] Other collaborative applications belonging to the same shared canvas workspace as the collaborative application on the speaker side receive a request message initiated by the speaker side for following the perspective of an information block in the interactive interface of the collaborative application on the speaker side;

[0035] After the other collaborative application returns a confirmation response, a perspective following relationship is established with the information block existing in the interactive interface of the collaborative application serving as the main speaker;

[0036] The request message is generated by the server after the collaborative application serving as the speaker sends a speaker request message to the server, and is sent by the server to other collaborative applications maintained by the server and belonging to the same shared canvas workspace as the collaborative application serving as the speaker.

[0037] After establishing a perspective following relationship with the information block existing in the interactive interface of the collaborative application on the speaker side, the collaborative application on the audience side obtains the operation information of the information block existing in the interactive interface of the collaborative application on the speaker side in real time, and uses the same information block existing in the interactive interface of its own collaborative application to achieve perspective following with the collaborative application on the speaker side.

[0038] Preferably, the step of using the operation information to follow the perspective of the collaborative application on the speaker's side through the same information block in the interactive interface of the collaborative application of the speaker specifically includes:

[0039] When the operation information contains operation content for multiple information blocks, the collaborative application on the audience side splits the operation content according to the identification information of the information blocks, and carries the corresponding operation content through the information blocks corresponding to the identification information on the interactive interface of its own collaborative application to complete the synchronous presentation of perspective following.

[0040] Preferably, before other collaborative applications belonging to the same shared canvas workspace as the collaborative application on the speaker side receive a request message initiated by the speaker side for following the perspective of an information block in the interactive interface of the collaborative application on the speaker side, the method further includes:

[0041] The collaborative application receives a synchronization message sent by the server; the synchronization message carries relevant information about the information block to be added and the second user ID that sent the synchronization message; wherein the collaborative application that receives the synchronization message sent by the server and the collaborative application logged in with the second user ID belong to the same shared canvas workspace;

[0042] The collaborative application generates a corresponding information block in its interactive interface according to the relevant information of the information block to be added.

[0043] Preferably, after the other collaborative application returns a confirmation response and establishes a perspective following relationship with the information block existing in the interactive interface of the collaborative application serving as the speaker, the method further includes:

[0044] The collaborative application on the audience side adjusts the display area of ​​the interactive interface of the current collaborative application, as well as the size and layout of each information block, to be consistent with the collaborative application on the speaker side according to the local confirmation full-view follow instruction; or

[0045] The collaborative application on the audience side follows the instructions based on the local confirmed content perspective, adjusts the display area of ​​the current collaborative application's interactive interface to be consistent with that of the collaborative application on the speaker's side, and keeps the size and layout of each information block in the current collaborative application's interactive interface unchanged.

[0046] Preferably, the information block is provided with permission control, and the permission is associated with the user ID for logging into the collaborative application. The method further comprises:

[0047] After the collaborative application is started, it sends the obtained user ID to the server for identity and permission authentication. Specifically:

[0048] After the collaborative application on the audience side meets the permission requirements of the interactive interface of the collaborative application on the speaker side, the collaborative application on the audience side obtains the operation information of the information blocks existing in the interactive interface of its collaborative application on the speaker side in real time, and presents the operation information synchronously through the interactive interface of its own collaborative application and the various information blocks contained in the collaborative application for perspective following.

[0049] In a third aspect, the present application further provides a collaborative working method for a fusion space, the method comprising:

[0050] The server receives a synchronization message for the shared canvas workspace; wherein the synchronization message carries relevant information of the added information block and identification information of the shared canvas workspace;

[0051] The server identifies each collaborative application belonging to the same shared canvas workspace based on the identification information of the shared canvas workspace and sends a request message to add the same information block in the interaction interface of each collaborative application; wherein each collaborative application is identified and authorized by the user ID of the corresponding collaborative application;

[0052] The server receives a request message initiated by the speaker side for perspective following of an information block in the interactive interface of the collaborative application on the speaker side. After verifying that the authority of the collaborative application on the speaker side is passed, the server sends a request message to each collaborative application that belongs to the same shared canvas workspace as the collaborative application on the speaker side, asking whether to participate in the collaborative application on the audience side, and establishes a relationship between the speaker and the audience based on the received response message confirming participation.

[0053] Preferably, the method further comprises:

[0054] The server receives a message sent by the collaborative application serving as the main speaker regarding operation information in an information block in its own interactive interface;

[0055] The server sends the operation information to the collaborative application on the audience side in the shared canvas workspace, so that the collaborative application on the audience side can follow the perspective of the collaborative application on the speaker side through the same information block in its own interactive interface.

[0056] Preferably, when any collaborative application belonging to the same shared canvas workspace adds a new information block in its interactive interface, the method further includes:

[0057] The server receives a synchronization message of a newly added information block sent by the collaborative application; the synchronization message carries relevant information of the newly added information block and the user ID of the user who sent the synchronization message;

[0058] The server forwards the synchronization message to other collaborative applications under its jurisdiction that belong to the same shared canvas workspace as the collaborative application that sent the synchronization message;

[0059] After receiving the synchronization message, other collaborative applications generate corresponding information blocks in their respective interactive interfaces.

[0060] Preferably, the method further comprises:

[0061] The server receives a request for sharing information block content; wherein the request carries a requesting user ID, a designated user ID, and content carried in a preview area of ​​the information block;

[0062] After completing the authority verification of the requesting user ID and the designated user ID, the server forwards the information block content directed sharing request to the collaborative application where the designated user ID is located.

[0063] In a fourth aspect, the present application further provides a collaborative working device for a fusion space, the device comprising:

[0064] a first receiving module, configured for a collaborative application to receive an operation instruction to add an information block to a shared canvas workspace to which the collaborative application has joined, wherein the information block includes a first information block carrying various types of web-end content, wherein the various types of web-end content can be embedded in the first information block for display;

[0065] A first response module is configured for the collaborative application to respond to the operation instruction and send a first synchronization message to the server, so that the server sends the first synchronization message to each collaborative application that has joined the shared canvas workspace; the first synchronization message is used to instruct each collaborative application to add the information block;

[0066] A first perspective following module is configured to, when any collaborative application in the shared canvas workspace obtains the speaker permission, cause the collaborative application on the speaker side to send operation information in an information block in its own interactive interface to the collaborative application on the audience side in the shared canvas workspace, so that the collaborative application on the audience side can follow the perspective of the collaborative application on the speaker side through the same information block in its own interactive interface;

[0067] Among them, the collaborative application serving as the speaker is a collaborative application that has obtained the speaker permission in the shared canvas workspace, and the collaborative application serving as the audience is one or more collaborative applications in the shared canvas workspace that have not obtained the speaker permission and have confirmed to join the speaker process. The speaker process is initiated by the collaborative application serving as the speaker.

[0068] In a fifth aspect, the present application further provides a collaborative working device for a fusion space, the device comprising:

[0069] The second receiving module is configured to receive a view-following request message initiated by the speaker for an information block in an interactive interface of the collaborative application on the speaker side from other collaborative applications belonging to the same shared canvas workspace as the collaborative application on the speaker side;

[0070] The second response module is used to establish a perspective following relationship with the information block existing in the interactive interface of the collaborative application as the main speaker after the other collaborative application returns a confirmation response;

[0071] The request message is generated by the server after the collaborative application serving as the speaker sends a speaker request message to the server, and is sent by the server to other collaborative applications maintained by the server and belonging to the same shared canvas workspace as the collaborative application serving as the speaker.

[0072] The second perspective following module is used to establish a perspective following relationship with the information block existing in the interactive interface of the collaborative application as the speaker side, and the collaborative application as the audience side obtains the operation information of the information block existing in the interactive interface of the collaborative application as the speaker side in real time, and uses the same information block existing in the interactive interface of its own collaborative application to achieve perspective following with the collaborative application on the speaker side.

[0073] In a sixth aspect, the present application further provides a collaborative working device for a fusion space, the device comprising:

[0074] a third receiving module, configured to receive a synchronization message for the shared canvas workspace; wherein the synchronization message carries relevant information of the added information block and identification information of the shared canvas workspace;

[0075] a confirmation module, configured to confirm, based on the identification information of the shared canvas workspace, each collaborative application belonging to the same shared canvas workspace, and send a request message for adding the same information block to the interaction interface of each collaborative application; wherein each collaborative application is individually identified and authorized by the user ID of the corresponding logged-in collaborative application;

[0076] The relationship establishment module is used to receive a request message initiated by the speaker side for perspective following of an information block in the interactive interface of the collaborative application on the speaker side, and after verifying that the authority of the collaborative application on the speaker side is passed, send a request message to each collaborative application that belongs to the same shared canvas workspace as the collaborative application on the speaker side, asking whether to participate in the collaborative application on the audience side, and establish the relationship between the speaker and the audience based on the received response message confirming participation.

[0077] In a seventh aspect, the present application further provides a computer device for implementing the collaborative working method of the fusion space described in the first aspect, the device comprising:

[0078] At least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the processor to execute the collaborative working method of the fusion space described in the first aspect.

[0079] In an eighth aspect, the present application also provides a non-volatile computer storage medium, wherein the computer storage medium stores computer-executable instructions, which are executed by one or more processors to complete the collaborative working method of the fusion space described in the first aspect.

[0080] The embodiment of the present application embeds web content directly into the information block in the shared canvas workspace for display, so that the web content can be directly presented to each terminal user who has joined the same shared canvas workspace in the shared canvas workspace joined by the collaborative application, so that each terminal user can browse the same web content on the local terminal, and for each terminal user of the collaborative application, the terminal user does not need to switch from the current page to other browser windows or jump to a third-party application to browse the web content, thereby improving the collaboration efficiency of each collaborative application joining the same shared canvas workspace for collaborative work, and the embodiment of the present application also provides a perspective following function for the collaborative application as the audience side and the collaborative application as the speaker side, so that when any collaborative application enters the speaker scene, it can efficiently focus the attention of multiple other terminal users of the collaborative application as the audience side, reducing the occurrence of the problem of distraction of collaborative members. BRIEF DESCRIPTION OF THE DRAWINGS

[0081] To more clearly illustrate the technical solutions of the embodiments of the present application, the following briefly introduces the drawings required for use in the embodiments of the present application. Obviously, the drawings described below are only some embodiments of the present application, and those skilled in the art can derive other drawings based on these drawings without inventive effort.

[0082] FIG1 is a schematic diagram of a flow chart of a collaborative working method of a fusion space provided in an embodiment of the present application;

[0083] FIG2 is a schematic diagram of an interactive interface of a first collaborative working method of a fusion space provided in an embodiment of the present application;

[0084] FIG3 is a schematic diagram of an interactive interface of a second collaborative working method of a fusion space provided in an embodiment of the present application;

[0085] FIG4 is a schematic diagram of a link information block in an interactive interface of a third collaborative working method for fusion space provided in an embodiment of the present application;

[0086] FIG5 is a schematic diagram of an interactive interface of a fourth collaborative working method of a fusion space provided in an embodiment of the present application;

[0087] FIG6 is a schematic diagram of an interactive interface of a fifth collaborative working method of a fusion space provided in an embodiment of the present application;

[0088] FIG7 is a schematic diagram of an interactive interface of a sixth collaborative working method of a fusion space provided in an embodiment of the present application;

[0089] FIG8 is a flow chart of a second method for collaborative work in a fusion space provided in an embodiment of the present application;

[0090] FIG9 is a schematic diagram of an interactive interface of a seventh collaborative working method of a fusion space provided in an embodiment of the present application;

[0091] FIG10 is a schematic diagram of an interactive interface of an eighth collaborative working method of a fusion space provided in an embodiment of the present application;

[0092] FIG11 is a schematic diagram of an interactive interface in a grid view of a collaborative working method for a fusion space provided in an embodiment of the present application;

[0093] FIG12 is a schematic diagram of an interactive interface under a tag view of a collaborative working method of a fusion space provided in an embodiment of the present application;

[0094] FIG13 is a schematic diagram of an interactive interface under a detailed view of a collaborative working method of a fusion space provided in an embodiment of the present application;

[0095] FIG14 is a schematic diagram of an interactive interface of a ninth collaborative working method of a fusion space provided in an embodiment of the present application;

[0096] FIG15 is a schematic diagram of an interactive interface in a grid view of another collaborative working method for fusion space provided in an embodiment of the present application;

[0097] FIG16 is a schematic diagram of an interactive interface under a tag view of another collaborative working method of a fusion space provided in an embodiment of the present application;

[0098] FIG17 is a schematic diagram of an interactive interface under a detailed view of another collaborative working method of a fusion space provided in an embodiment of the present application;

[0099] FIG18 is a schematic diagram of an interactive interface of a tenth collaborative working method of a fusion space provided in an embodiment of the present application;

[0100] FIG19 is a schematic diagram of an interactive interface of an eleventh collaborative working method of a fusion space provided in an embodiment of the present application;

[0101] FIG20 is a flowchart of a third collaborative working method for fusion space provided in an embodiment of the present application;

[0102] FIG21 is a schematic diagram of an interactive interface of a twelfth collaborative working method of a fusion space provided in an embodiment of the present application;

[0103] FIG22 is a flowchart of a fourth collaborative working method for fusion space provided in an embodiment of the present application;

[0104] FIG23 is a schematic diagram of an application scenario of a collaborative working method of a fusion space provided in an embodiment of the present application;

[0105] FIG24 is a flow chart of a collaborative working method of a fusion space provided in an embodiment of the present application in an actual application scenario;

[0106] FIG25 is a schematic diagram of a signaling flow of a collaborative working method of a fusion space provided in an embodiment of the present application;

[0107] FIG26 is a flowchart of another collaborative working method of a fusion space provided in an embodiment of the present application in an actual application scenario;

[0108] FIG27 is a schematic diagram of a signaling flow of a collaborative working method of a fusion space provided in an embodiment of the present application;

[0109] FIG28 is a flowchart illustrating another collaborative working method of a fusion space provided in an embodiment of the present application in an actual application scenario;

[0110] FIG29 is a schematic diagram of a signaling flow of a collaborative working method of a fusion space provided in an embodiment of the present application;

[0111] FIG30 is a schematic diagram of the architecture of a collaborative working device for a fusion space provided in an embodiment of the present application;

[0112] FIG31 is a schematic diagram of the architecture of another collaborative working device for fusion space provided in an embodiment of the present application;

[0113] FIG32 is a schematic diagram of the architecture of another collaborative working device for fusion space provided in an embodiment of the present application;

[0114] FIG33 is a schematic diagram of the architecture of a computer device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0115] In order to make the purpose, technical solutions and advantages of this application more clearly understood, the present application is further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain this application and are not intended to limit this application.

[0116] The terms "first," "second," etc., in this application are used for descriptive purposes only and should not be understood to indicate or imply relative importance or implicitly specify the number of the technical features indicated. Thus, a feature qualified as "first," "second," etc. may explicitly or implicitly include one or more of the features. In the description of this application, unless otherwise specified, "plurality" means two or more.

[0117] In addition, the technical features involved in each embodiment of the present application described below can be combined with each other as long as they do not conflict with each other.

[0118] In this field, existing collaborative applications can support multiple terminal users to edit and access shared content in the same workspace on their respective terminal application sides. For example, users with access permissions can access and view shared documents, and users with editing permissions can edit shared documents. Some collaborative applications can even support multiple users to synchronously edit shared content. For example, multiple users can edit different cells in a shared table. However, the synchronous editing operations supported by existing collaborative applications are usually preemptive mechanisms, which do not support multiple people to synchronously edit the same area of ​​shared content. For example, only one user can edit the same cell in a shared table. Furthermore, although each collaborative member who joins the same workspace can freely create link-sharing content in existing collaborative applications, existing collaborative applications can only carry the link-sharing content in the form of a hyperlink or a third-party application card. In this carrying mode, if each collaborative member wants to view the corresponding link-sharing content in the current collaborative application, they need to click on the hyperlink to jump to the page, jump to an independent browser window to view the link-sharing content, or click on the third-party application card to further invoke the third-party application and jump to the third-party application to view the link-sharing content. However, this phenomenon of frequently jumping to multiple different browser windows or third-party applications will distract the attention of collaborative members and lead to inefficient collaborative work.

[0119] To this end, the inventors thought of using information blocks to carry various shared content involved in collaborative work, such as pictures, notes, sticky notes, web content, etc., and then strengthening the control of each collaborative member who joins the same workspace over the content displayed in the workspace by adding information blocks to the shared space of the collaborative application, so that each collaborative member can use the information blocks to view and edit various shared content; and, further, the inventors thought of differentiating the presentation mechanism of web content (such as link content) in the workspace from the hyperlink form of existing collaborative applications, and using information blocks as containers to embed web content in information blocks for display, so that each collaborative member can avoid the need to jump out of the current workspace page to go to the The corresponding web content can be viewed in other window pages; furthermore, considering that the characteristics of collaborative work scenarios generally involve multi-person collaboration / cooperation, when multiple collaborative members need to focus on or pay attention to a certain content in the workspace, the inventor also thought of using the mechanism strategy of preempting the main speaker authority, and the collaborative application that obtains the main speaker authority is used as the main speaker side, and the other collaborative applications that have confirmed to join the main speaker process are used as the audience side, so that the users on the audience side can focus on the content sharing of the users on the main speaker side, so that multiple collaborative members on the audience side can follow the perspective of the main speaker side in real time, and the attention of multiple users can be more efficiently focused on the same main speaker content, thereby overcoming the problems of low efficiency of collaborative work and easy distraction of attention of multiple collaborative members when participating in collaborative work.

[0120] It should be noted that the collaborative applications referred to in the embodiments of this application include: software with various capabilities supporting collaborative work, plug-ins with various capabilities supporting collaborative work, mini-programs with various capabilities supporting collaborative work, applications with various capabilities supporting collaborative work, etc. In actual application scenarios, collaborative applications can be hosted on terminal devices in the form of applications or mini-programs, or in the form of clients or plug-ins; terminal devices include but are not limited to mobile phones, computers, tablets, monitors, wearable devices, vehicle-mounted terminals, and electronic displays.

[0121] Embodiment 1:

[0122] Example 1 of the present application provides a collaborative working method for a fusion space. The collaborative working method for a fusion space described in this embodiment is described from the perspective of collaborative applications. As shown in FIG1 , the method includes:

[0123] In step 201, the collaborative application receives an operation instruction to add an information block in the shared canvas workspace to which it joins, wherein the information block includes a first information block carrying various types of web content, and the various types of web content can be embedded in the first information block for display.

[0124] Among them, the shared canvas workspace is used to provide a workspace that is commonly accessible across devices and applications, allowing users to select elements within the space and place various types of projects into the shared canvas workspace and then pick them up again later using the same or different devices and applications. Using the shared canvas workspace, tasks or projects can be completed from a variety of different applications and devices, and elements can be combined into a single object for sharing with one or more of the user's contacts. It should be further clarified that the workspace refers to a function that allows users to collaborate on shared tasks or allows users to bring together various resources for a specific purpose.

[0125] In actual application scenarios, the shared canvas workspace can be understood as a management component. From the perspective of the front-end interactive interface, the shared canvas workspace is used to manage the layout of information blocks, that is, the shared canvas workspace provides a window (such as a drawing board, etc.) that carries information blocks. The window is a concept in layout. The information blocks carried by the shared canvas workspace are only displayed in this window. The window can also carry an image background or a text background, and each information block can be displayed on top of the image background and text background. From the back-end perspective, the shared canvas workspace is used to manage the resources of each collaborative application added to the shared canvas workspace, such as managing the information blocks of each collaborative application added to the shared canvas workspace.

[0126] The information block can be understood as a form component for carrying web content or local content, and the form component can also provide editing functions for web content or local content. For example, the first information block is used to carry web content, and the web content includes one or more of web pages, documents, online design software, online audio and video streams, shared canvas workspaces, and preview area contents of information blocks of other collaborative applications in the same shared canvas workspace online. Correspondingly, the first information block can be one or more of a link information block, a browser information block, and a software information block (which can be embedded in office software, drawing design software, graphic presentation design software, mind map design software, etc.). The local content includes but is not limited to text, pictures, images, notes, sticky notes, graphic presentations, video content, audio content, and other multimedia content.

[0127] For simplicity and intuitiveness, this and subsequent embodiments use a drawing board as an alternative representation of the shared canvas workspace for illustration, and the accompanying drawings are also presented in the form of a drawing board, as shown in Figure 2. The drawing board supports scalability based on the needs of the terminal where the collaborative application is located or the user using the collaborative application. Its size can be adjusted by the user based on the needs of the corresponding terminal or user. When the drawing board is resized, the size of each information block within the drawing board is also proportionally scaled.

[0128] The operation instruction carries the identification information of the shared canvas workspace and the relevant information of the added information block. As shown in Figure 3, after the collaborative application enters the drawing board added by the collaborative application, it clicks the icon of the added information block in the toolbar to generate the corresponding information block. When the icon of the added link information block is clicked as shown in Figure 3, a new link information block pop-up window pops up. After entering the link address in the new link information block pop-up window and clicking OK, an operation instruction is generated. The information block type carried in the operation instruction is a link information block, and it carries the link address as shown in Figure 3, or when the icon of the added link information block is clicked, a blank link information block is generated. After entering the link address in the blank link information block, the link information block displays the web content of the link address.

[0129] In step 202, the collaborative application responds to the operation instruction and sends a first synchronization message to the server, so that the server sends the first synchronization message to each collaborative application that has joined the shared canvas workspace; the first synchronization message is used to indicate the addition of the information block in each collaborative application. The first synchronization message carries the identification information of the shared canvas workspace and the relevant information of the added information block, and may also carry the identification information of the user who sent the first synchronization message, such as the user's ID. The server sending the first synchronization message to each collaborative application does not absolutely mean that the server sends the first synchronization message as it is to each collaborative application, but refers to the server forwarding the request message for adding the same information block to each collaborative application. The server can be configured in the cloud, remotely, or locally, and this embodiment of the application does not limit this.

[0130] In which, the web content is obtained by the server from the network, and is carried in the first synchronization message and sent to each collaborative application that has joined the shared canvas workspace, so as to carry and display the web content in the first information block. For example, each collaborative application has a built-in first component required for adding the first information block, and the server has a built-in second component required for adding the first information block. The first component provides the display function of the first information block, and provides the first information block with local interactive functions (i.e., functions that do not require network support, such as sliding and turning pages of web pages, etc.) and online interactive entrances (i.e., functions that require network support, such as web page refresh, web page form input, etc.). The second component is used to generate the data required for displaying the first information block according to the interactive actions performed by the collaborative application side, and provide the data to the collaborative application side so that the first component can display the first information block according to the data.

[0131] Taking the link information block shown in Figure 2 as an example, the first component in the collaborative application provides an interactive interface required for displaying the link information block. The interactive interface is shown in Figure 4, including a preview area for carrying web content and function buttons (such as a web content refresh function button provided in the upper right corner of the preview area to provide a web content refresh function, a zoom function button provided in the upper right corner to provide a function of zooming in and out of the information block, a dock function button provided in the upper right corner to provide a function of docking the information block close to the edge of the shared canvas workspace, a share function button provided in the upper right corner to share the information block with other collaborative applications, and a sliding bar provided on the right side of the preview area to provide a sliding up and down function for browsing content in the preview area). It should be noted that the various types of function buttons here are presented schematically. In actual use, those skilled in the art can set the corresponding function buttons based on the needs of the information block. After entering the link address in the collaborative application, the link address is carried in the first synchronization message as one of the relevant information of the added information block, and is sent by the collaborative application to the server. The server receives the first synchronization message, and the second component of the server pulls the web content of the link address from the network and sends the web content to each collaborative application. The first component of each collaborative application displays the web content. When the web content refresh button is clicked in the link information block of any collaborative application, the first component of the collaborative application generates a refresh request and sends the refresh request to the server. The server retrieves the web content and transmits it to all collaborative applications in the shared canvas workspace to which the collaborative application belongs. The first component of each collaborative application in the shared canvas workspace to which the collaborative application belongs then displays the retrieved web content. According to the settings of the operating user, the function button can also be hidden, and only the preview area is displayed in the interactive interface, as shown in Figure 5.

[0132] In step 203, when any collaborative application existing in the shared canvas workspace obtains the speaker permission, the collaborative application on the speaker side will send the operation information in the information block existing in its own interactive interface to the collaborative application on the audience side in the shared canvas workspace, so that the collaborative application on the audience side can follow the perspective of the collaborative application on the speaker side through the same information block existing in its own interactive interface.

[0133] Among them, the collaborative application serving as the speaker is a collaborative application that has obtained the speaker permission in the shared canvas workspace, and the collaborative application serving as the audience is one or more collaborative applications in the shared canvas workspace that have not obtained the speaker permission and have confirmed to join the speaker process. The speaker process is initiated by the collaborative application serving as the speaker.

[0134] The perspective following can be understood as the synchronization of the information blocks of the collaborative application on the audience side with the information blocks of the collaborative application on the speaker side. For example, two collaborative applications added to the same shared canvas workspace are collaborative application 1 and collaborative application 2. The same information block A is set in both collaborative application 1 and collaborative application 2. For example, collaborative application 1 is on the speaker side. The synchronization of the information blocks of the collaborative application on the audience side with the information blocks of the collaborative application on the speaker side can be one or more of the following three situations:

[0135] The first case: When collaborative application 1 obtains the speaker permission, the layout position of information block A in collaborative application 2 (including: the size of the information block and the position of the information block) is the same as the layout position of information block A in collaborative application 1, and in subsequent operations, if the layout position of information block A in collaborative application 1 changes, the information block A in collaborative application 2 will undergo the same layout position change as the information block A in collaborative application 1.

[0136] The second situation: When collaborative application 1 obtains the main speaker permission, the content of information block A in collaborative application 2 is the same as the global content of information block A in collaborative application 1, and in subsequent operations, if the global content of information block A in collaborative application 1 changes, then information block A in collaborative application 2 presents the same global content as information block A in collaborative application 1.

[0137] The global content can be understood as: content that is not affected by operations such as page turning, progress adjustment, or tab switching by the operating user. For example, if the information block A is a video information block, the information block A in the collaborative application 2 and the information block A in the collaborative application 1 display the same video, but the videos in the two information blocks are not played absolutely synchronously, that is, the real-time content presented to the user may be different; and when the video in the information block A of the collaborative application 1 is switched to another video, the information block A in the collaborative application 2 also switches the video to another video.

[0138] The third scenario: When collaborative application 1 obtains the speaker permission, the content of information block A in collaborative application 2 is identical to the real-time content of information block A in collaborative application 1. If the real-time content of information block A in collaborative application 1 changes during subsequent operations, information block A in collaborative application 2 will present the same real-time content as information block A in collaborative application 1. It should be noted that the term "real-time" is a concept relative to the aforementioned global content. Real-time content can be understood as the content presented in real time by the information block, which may change as the user turns pages, adjusts progress, or switches tabs. For example, if the information block A is a browser information block, which contains tabs corresponding to 3 link addresses, and the content of the corresponding link address is presented on each tab, when the information block A of the collaborative application 2 switches from the first tab to the second tab, the information block A of the collaborative application 1 also switches to the second tab, and when the information block A of the collaborative application 1 clicks the up and down sliding page-turning buttons on the current tab to slide the current tab to any position, the current tab of the information block A of the collaborative application 2 also slides to that position, so that the real-time content displayed by the information block A of the collaborative application 2 is consistent with that of the information block A of the collaborative application 1.

[0139] Operation information is generated by user actions on the information block. These actions include one or more of: playing an image, playing a video, mouse events (such as hovering, double-clicking, clicking, and dragging), editing text, dragging a window, drawing, and operating a web application. The operation information includes at least the operation content and the identification information of the shared canvas workspace.

[0140] There are at least two ways to obtain the speaker authority, including:

[0141] The first implementation method: the user who created the shared canvas workspace selects the users who have joined the shared canvas workspace and assigns them the speaker permission. As shown in Figure 6, if drawing board 1, that is, the shared canvas workspace is created by user 1, user 1 expands and displays the users who have joined drawing board 1 in the window where drawing board 1 is located in the collaborative application, and hovers the mouse over the position of any user, such as hovering over the position of user 3 in Figure 6, to expand the detailed window of user 3 for it, and provide a "Set as Speaker" button in the detailed window. When user 1 clicks the button, the collaborative application logged in by user 1 A view following request message is sent to the server, and the view following request message carries the identification information of the party that has obtained the speaker's authority. For example, after clicking the "Set as Speaker" button in the detailed window of user 3 shown in FIG6 , the view following request message sent by the collaborative application to the server carries the identification information of user 3. After receiving the view following request message, the server sends a request message to the collaborative application corresponding to other users of the shared canvas workspace to ask whether to participate in the collaborative application as the audience. The server establishes a view following relationship based on the response message confirming participation received. When any user has been set as the speaker, a "Cancel Speaker" button is provided in the detailed window of the user who has been set as the speaker in the interactive interface for creating users in the shared canvas workspace. For example, in FIG6 , after user 3 is set as the speaker, the "Set as Speaker" button in the detailed window of user 3 is replaced with a "Cancel Speaker" button.

[0142] The second implementation method involves a user proactively requesting speaker permission from the server. As shown in Figure 7, user 1 clicks on their own user location in the collaborative application's canvas 1 window, expanding their detailed window. This detailed window provides a "Request speaker permission for the current canvas" button. When user 1 clicks this button, the collaborative application sends a viewfollowing request message to the server, including their user identification information. After verifying the speaker's permission, the server sends a request message to the other collaborative applications in the shared canvas workspace, requesting participation in the audience's collaborative application. Viewfollowing relationships are established based on the received response messages confirming participation. Once any user has obtained speaker permission, a "Quit speaker" button is provided in that user's detailed window.

[0143] The collaborative application on the speaker side will send the operation information in the information block in its own interactive interface to the collaborative application on the audience side in the shared canvas workspace. Specifically, the collaborative application on the speaker side sends the operation information to the server, and the server sends the operation information to the collaborative application on the audience side according to the perspective following relationship established in the server.

[0144] This embodiment embeds web content directly into the information block in the shared canvas workspace for display, so that the web content can be directly presented to each terminal user who has joined the same shared canvas workspace in the shared canvas workspace joined by the collaborative application, so that each terminal user can browse the same web content on the local terminal, and for each terminal user of the collaborative application, the terminal user does not need to switch from the current page to other browser windows or jump to a third-party application to browse the web content, thereby improving the collaboration efficiency of each collaborative application joining the same shared canvas workspace for collaborative work, and the embodiment of the application also provides a perspective following function for the collaborative application as the audience side and the collaborative application as the speaker side, so that when any collaborative application enters the speaker scene, it can efficiently focus the attention of multiple other terminal users of the collaborative application as the audience side, reducing the occurrence of the problem of distraction of the collaborative members.

[0145] In actual application scenarios, the information block may also include a second information block that carries various types of local content. The second information block may be one or more of a picture information block, a label information block, a notebook information block, a text box information block, and a video information block. Each collaborative application has built-in components required to add a second information block. When the server determines that the information block to be added is a second information block based on the first synchronization message, the server forwards the first synchronization message to each collaborative application, and each collaborative application uses the local built-in components to add the second information block. The collaborative application on the speaker side will send the operation information in the information block in its own interactive interface to the collaborative application on the audience side in the shared canvas workspace, so that the collaborative application on the audience side can follow the perspective of the collaborative application on the speaker side through the same information block in its own interactive interface, as shown in Figure 8, specifically including:

[0146] In step 301, when a second information block in a collaborative application serving as the speaker is edited, a follow-up message carrying identification information of the second information block and the corresponding edited content is sent to the collaborative applications serving as the audience in the shared canvas workspace, so that the edited content of the speaker is synchronously presented in the same second information block in each collaborative application serving as the audience. The identification information may be the identification number of the second information block, where each information block has a unique identification number, and the identification number of the same information block added to different collaborative applications is the same. Depending on the edited second information block, the corresponding edited content may also vary. For example, if the edited information block is a notebook information block, the corresponding edited content may be text within the notebook information block. The sending of the follow-up message carrying the identification information of the second information block and the corresponding edited content to the collaborative applications serving as the audience in the shared canvas workspace may involve the collaborative application serving as the speaker sending a follow-up message to the server, which forwards the follow-up message to each collaborative application serving as the audience based on the established perspective-following relationship.

[0147] In step 302, when the collaborative application serving as the speaker switches from editing the second information block to performing operations in the first information block carrying various types of web-based content, a follow-up message carrying identification information of the first information block and corresponding operation content is sent to the collaborative application serving as the audience in the shared canvas workspace, so that the operation content of the speaker can be synchronously presented in the same first information block in each collaborative application serving as the audience.

[0148] Among them, the switching of information blocks can be perceived by the mouse action in the collaborative application. For example: a collaborative application has a unique information block being edited. When an information block is added, the added information block is designated as the information block being edited. When the mouse moves to the area where other information blocks are located and a click action occurs, the other information blocks are switched to the information block being edited.

[0149] In one embodiment, when a new collaborative application is temporarily added to the shared canvas workspace, wherein a first user ID is logged into the new collaborative application, the method further includes:

[0150] The collaborative application, acting as the speaker, receives a request message carrying the first user ID to join the shared canvas workspace. As shown in Figure 9, a share button is provided in the collaborative application. When the share button is clicked, a share box pops up, displaying a link to the current shared canvas workspace. After obtaining the link, the terminal user of the other collaborative application logs in to the collaborative application, enters the link, clicks to join, generates the request message, and sends the request message to the collaborative application on the speaker's side. The user ID may include an account ID, username, work ID, etc.; if associated with a third-party chat software account, it may also be a third-party chat software account, such as a WeChat account, QQ number, mobile phone number, etc.

[0151] The collaborative application serving as the main speaker returns a response message for confirming joining, wherein the response message for confirming joining is used to establish a perspective following relationship between the new collaborative application and the collaborative application serving as the main speaker.

[0152] In one embodiment, when a speaker-audience relationship is not established, operations of various collaborative applications on the same information block within the same shared canvas workspace may be serial or parallel. These serial and parallel relationships may be specified by the collaborative application that adds the information block. Alternatively, some types of information blocks may be set to serial relationships by default, while other types may be set to parallel relationships by default, depending on the type of information block. For example, image information blocks, notebook information blocks, video information blocks, and link information blocks may be set to serial relationships, while browser information blocks and tag information blocks may be set to parallel relationships. It should be noted that this is merely an example, and whether a particular information block is a serial or parallel relationship is determined by those skilled in the art based on the information block's usage requirements and is not limited in this embodiment. The speaker-audience relationship described herein is also referred to as a perspective-following relationship in subsequent embodiments.

[0153] Wherein, when the relationship between the speaker and the audience is not established, the operations of the collaborative applications on the same information block belonging to the same shared canvas workspace are in a serial relationship, and the method further includes:

[0154] When the same information block belonging to the same shared canvas workspace is not operated by any collaborative application, each collaborative application can obtain exclusive operation on the same information block belonging to the same shared canvas workspace in its interactive interface.

[0155] After the exclusive operation of the same information block belonging to the same shared canvas workspace is released, each collaborative application starts to preempt the exclusive operation of the same information block belonging to the same shared canvas workspace in its interactive interface.

[0156] Among them, the exclusive operation can be released: when it is detected that the mouse moves away from the preview area of ​​the current information block, or the mouse stays in the preview area of ​​the current message block for more than a preset time, such as when the still time exceeds 5s, the exclusive operation is released, and the preset time is obtained by those skilled in the art based on empirical analysis; the exclusive operation can also be released by initiating an exclusive operation application or an interactive button in a collaborative application or an information block, or by releasing an exclusive operation. As shown in Figure 14, clicking "Apply for Exclusive" in the right-click menu of the information block initiates an exclusive operation application for the information block, and clicking "Release Exclusive" in the right-click menu of the information block initiates the release of the exclusive operation of the information block. For example, the terminal user sets an exclusive operation with a corresponding application time for the information block, and the exclusive operation of the information block is released after the application time.

[0157] It should be noted here that the specific application duration is set by the end user based on his or her own needs analysis. The specific actions of the above-mentioned exclusive operation and exclusive release are merely illustrative and are not used to limit this application. In actual use, all actions that can achieve exclusive operation and exclusive release should be included in the scope of protection of this application.

[0158] When any collaborative application takes an exclusive operation on any information block belonging to the same shared canvas workspace in its interactive interface, other collaborative applications that have not obtained the exclusive operation on the same information block belonging to the same shared canvas workspace will synchronously update the content of the preview area in the same information block they own to the operation content in the preview area of ​​the same information block in the collaborative application that currently obtains the exclusive operation.

[0159] When the relationship between the speaker and the audience is not established, the operations of the collaborative applications on the same information block in the same shared canvas workspace are in a parallel relationship. The method further includes:

[0160] When the same information block belonging to the same shared canvas workspace is the target information block on which each collaborative application can perform parallel operations in its interactive interface, each collaborative application receives the operation information performed on the target information block in its own interactive interface, and presents the operation result in the preview area of ​​the target information block in its own interactive interface. The operation result is the operation result brought about by the operation of the target information block in its own interactive interface.

[0161] Among them, both the serial relationship and the parallel relationship of the information blocks can be stored in the server in the form of the identification information of the information block and the serial identification or parallel identification; when the server receives a message from a collaborative application, based on the identification information of the information block carried in the message and combined with the stored data in the server, when it is identified that the information block corresponding to the message is in a serial relationship, a follow-up message carrying the corresponding operation content is sent to each collaborative application belonging to the same shared canvas workspace to achieve synchronous update. For example, a copy of the data corresponding to the first information block can be stored in the server, including: the web-side content required to be carried by the first information block, and the operation information performed on the first information block by the collaborative application that takes exclusive operation on the first information block. When synchronizing the content, the collaborative application that takes exclusive operation sends a corresponding message (such as a follow-up message carrying the corresponding operation content, etc.) to update this data, and the updated data is carried by the server in the follow-up message of the operation content and forwarded to each collaborative application.

[0162] When the server receives a message from any collaborative application and recognizes that the information block corresponding to the message is a serial relationship, the server only returns the corresponding response message to the collaborative application of the message source, so that independent web content and operation results are presented on different collaborative applications.

[0163] In one embodiment, the collaborative application with review permission sends a request to the server to review the content in the preview area of ​​the same information block in each collaborative application that has been added to the same shared canvas workspace. The method further includes:

[0164] After obtaining the content of the respective preview areas of the same information block originating from different collaborative applications in the same shared canvas workspace, the collaborative application with review permission mirrors a corresponding number of information blocks and presents the content of the respective preview areas in each mirrored information block; or, after obtaining the content of the respective preview areas of the same information block originating from different collaborative applications in the same shared canvas workspace, the collaborative application with review permission generates a corresponding number of switch pages in its own information block toolbar corresponding to the number of different collaborative applications, wherein each switch page presents the content of the preview area of ​​the same information block contained in a collaborative application. The number of mirrored information blocks and the number of generated switch pages may be the number of collaborative applications in the same shared canvas workspace.

[0165] The review permission may be owned by the collaborative application that creates the shared canvas workspace, or the collaborative application that creates the shared canvas workspace may assign the review permission of one or more information blocks to other collaborative applications.

[0166] As shown in Figure 10, a view icon is provided in the collaborative application. Click the view icon to pop up a view adjustment drop-down box, which provides multiple views for terminal users to choose from, including: grid view, label view, detailed view and personal view. When the personal view is selected, the information blocks in the current collaborative application are displayed, as shown in Figure 1 or Figure 5 above. When the grid view is selected, the interface shown in Figure 11 is displayed, that is, in the shared canvas workspace of the collaborative application with review permissions, multiple areas are divided, each area corresponds to a collaborative application, and the information blocks in each collaborative application are mirrored to the corresponding area; when the tag view is selected, the interface shown in Figure 12 is displayed, that is, in the shared canvas workspace of the collaborative application with review permissions, multiple tabs are established, each tab corresponds to a collaborative application, and the information blocks under the corresponding collaborative application are presented in the tab; when the detailed view is selected, as shown in Figure 13, the shared canvas workspace of the collaborative application with review permissions is divided into two areas, left and right, and the mirror images of each information block under each collaborative application are arranged and presented in the left area, so that the terminal user can select one of the mirror images, and the information block in the selected collaborative application is presented in the right area.

[0167] If before or after entering the grid view, label view or detailed view (as shown in Figure 14 before entering the grid view, label view or detailed view), you right-click on any information block and select "Display this information block separately" in the right-click menu, the information block will be displayed separately under each collaborative application, such as the interface shown in Figure 15 under the grid view, the interface shown in Figure 16 under the label view, and the interface shown in Figure 17 under the link information block. The tab bars in Figures 12 and 16 are only schematic presentations. In actual use, the tab bar can also be set in the toolbar.

[0168] In some embodiments, the speaker side may only want some users to follow one or more information blocks, rather than all information blocks on the speaker side. In order to meet this requirement, the method also includes: when the collaborative application on the speaker side obtains the content of the preview area of ​​the specified information block to be shared with the specified user ID, the collaborative application on the speaker side sends a targeted sharing request for the content of the specified information block to the server; wherein the targeted sharing request for the content of the specified information block carries the speaker side user ID, the specified user ID, the specified information block identification information, and the content carried in the preview area in the specified information block.

[0169] As shown in Figure 14, when you right-click on any information block and select "Share this information block" from the right-click menu, a sharing pop-up window pops up. Selecting any user in the sharing pop-up window generates a request for sharing the content of the specified information block. The sharing pop-up window can be as shown in Figure 9. Clicking "Invite Enterprise Members" pops up information about users that can be invited. The operating user selects one or more users to share with from the available users, and a request for sharing the content of the specified information block is generated based on the users selected by the operating user.

[0170] In each collaborative application, the added information blocks can be individually adjusted, including one or more of enlargement, reduction, fading, rotation, and movement. Adjustments can also be made to any information block based on other existing information blocks, such as adjusting one or more information blocks to adhere to the edge of another information block, adjusting one or more information blocks to be displayed over another information block with a transparent background, adjusting one or more information blocks to maintain a fixed relative position with another information block, or adjusting one or more information blocks to maintain the same size as another information block.

[0171] In some embodiments, when adding an information block, the added information block is suspended in the interactive interface, as shown in FIG18; or, after being added, it exists in a priority avoidance relationship with the content in the interactive interface of the collaborative application, as shown in FIG19, wherein, when adding an information block, it is displayed in the form of a non-fixed frame until the terminal user double-clicks in an area outside the non-fixed frame in the operation interface, and the non-fixed frame is converted into an information block. An expansion icon is also set around the non-fixed frame. When the terminal user clicks the expansion icon, a non-fixed frame of the same type and size as the existing non-fixed frame is generated in the direction corresponding to the expansion icon, side by side or parallel to the existing non-fixed frame. When the terminal user double-clicks in the non-fixed frame, the non-fixed frame is converted into an information block. After double-clicking the outer area, it is converted into information blocks of the same type and size that are arranged side by side or in parallel; among them, when the non-fixed frame is suspended in the interactive interface, if the distance between the edge of the non-fixed frame in a certain direction and the edge of the interactive interface is greater than the preset distance, an expansion icon is set in that direction, otherwise, no expansion icon is set; when the non-fixed frame avoids the corresponding content in the interactive interface (i.e., other information blocks), if the distance between the edge of the non-fixed frame in a certain direction and the edge of the corresponding content in the interactive interface or the edge of the interactive interface is greater than the preset distance, an expansion icon is set in that direction, otherwise, no expansion icon is set. The preset distance is obtained by those skilled in the art based on empirical analysis. As shown in Figure 19, since the distance between the non-fixed frame and the interactive interface or other information blocks in the left, top, and right directions is less than the preset distance, the expansion icon is only set at the bottom.

[0172] Example 2:

[0173] After providing a collaborative working method for a fusion space as described in Example 1, this application further provides a collaborative working method for a fusion space. This method aims to explain the collaborative working method for a fusion space in Example 1 from the perspective of audience collaboration and to provide an in-depth analysis of its design principles. It should be noted that the method in Example 1 is applicable to this Example 2 and will not be further described in this example.

[0174] This embodiment provides a collaborative working method for a fusion space, as shown in FIG20 , and the method includes:

[0175] In step 401, other collaborative applications that belong to the same shared canvas workspace as the collaborative application on the speaker side receive a request message initiated by the speaker side for perspective following of an information block in the interactive interface of the collaborative application on the speaker side; the perspective following request message carries the identification information of the user on the speaker side and the identification information of the shared canvas workspace. The reception of the perspective following request message initiated by the speaker side for perspective following of an information block in the interactive interface of the collaborative application on the speaker side does not absolutely refer to the reception of the perspective following request message from the speaker side. The speaker side may also send the perspective following request message to the server. Based on the perspective following request message, the server sends a request message to the other collaborative applications that belong to the same shared canvas workspace as the collaborative application on the speaker side, asking them whether to participate in the collaborative application on the audience side, thereby being received by the other collaborative applications that belong to the same shared canvas workspace.

[0176] In step 402, after the other collaborative applications return a confirmation response, a perspective following relationship is established with the information block existing in the interactive interface of the collaborative application as the main speaker; wherein, the request message is generated by the server after the collaborative application as the main speaker sends a main speaker request message to the server, and is sent by the server to other collaborative applications maintained by it that belong to the same shared canvas workspace as the collaborative application as the main speaker.

[0177] In step 403, after establishing a perspective following relationship with the information block existing in the interactive interface of the collaborative application as the speaker side, the collaborative application as the audience side obtains the operation information of the information block existing in the interactive interface of the collaborative application as the speaker side in real time, and uses the same information block existing in the interactive interface of its own collaborative application to achieve perspective following with the collaborative application on the speaker side.

[0178] In actual use, based on the different network conditions of each collaborative application and server, the operation content of the speaker on different information blocks can be carried in different operation information and sent to the audience side; or the operation content of the speaker on different information blocks can be carried in the same operation information and sent to the audience side. In this case, the operation information also carries the identification information of each information block. The operation information is used to follow the perspective of the collaborative application on the speaker side through the same information block in the interactive interface of the collaborative application, which specifically includes:

[0179] When the operation information contains operation content for multiple information blocks, the collaborative application on the audience side splits the operation content according to the identification information of the information blocks, and carries the corresponding operation content through the information blocks corresponding to the identification information on the interactive interface of its own collaborative application to complete the synchronous presentation of perspective following.

[0180] In one embodiment, before other collaborative applications belonging to the same shared canvas workspace as the collaborative application on the speaker side receive a request message initiated by the speaker side to follow the perspective of an information block in the interactive interface of the collaborative application on the speaker side, the method further includes:

[0181] The collaborative application receives a synchronization message sent by the server; the synchronization message carries information about the information block to be added and the ID of the second user who sent the synchronization message; the collaborative application that receives the synchronization message sent by the server and the collaborative application logged in with the second user ID belong to the same shared canvas workspace; the collaborative application generates a corresponding information block in its interactive interface based on the information about the information block to be added. In other words, the information block to be added is generated.

[0182] In one embodiment, after the other collaborative application returns a confirmation response and establishes a perspective-following relationship with the information block in the interactive interface of the collaborative application serving as the speaker, the method further includes:

[0183] The collaborative application on the audience side adjusts the display area of ​​the interactive interface of the current collaborative application, and the size and layout of each information block to be consistent with those in the collaborative application on the speaker side according to the local confirmation full-view follow instruction; or, the collaborative application on the audience side adjusts the display area of ​​the interactive interface of the current collaborative application to be consistent with the collaborative application on the speaker side according to the local confirmation content perspective follow instruction, keeping the size and layout of each information block in the interactive interface of the current collaborative application unchanged.

[0184] In one embodiment, before the audience side adjusts the display area of ​​the interactive interface of the current collaborative application to be consistent with that of the collaborative application on the speaker side, or adjusts the size and layout of each information block to be consistent with that of the collaborative application on the speaker side, the method also includes: locally storing on the audience side the relevant content of the display area of ​​the interactive interface of the current collaborative application (i.e., before the perspective follows), as well as the size and layout of each information block (before the perspective follows); correspondingly, after the perspective following relationship is cancelled, the collaborative application on the audience side can also restore the display area of ​​the interactive interface of the current collaborative application to the display area before following the speaker side according to the local restore perspective instruction before following, and / or restore the size and layout of each information block in the interactive interface of the current collaborative application to the size and layout before following the speaker side. Among them, the instruction to restore the perspective before following can be generated by the terminal user through the interactive interface of the collaborative application. As shown in Figure 21, after the collaborative application on the audience side receives the message of canceling the speaker relationship, a perspective pop-up window as shown in Figure 21 pops up on the interface of the collaborative application. In the perspective pop-up window, the operating user is prompted "The lecture has been cancelled, do you want to restore the content or layout before following the lecture?" and "Restore the content and layout before the lecture", "Restore only the content before the lecture", "Restore only the layout before the lecture" and "Keep current content and layout" buttons are provided. Among them, when the operating user selects "Keep current content and layout" or directly closes the perspective pop-up window, no instruction is generated. Generates an instruction to restore the perspective before following. When the user selects "Restore the content and layout before the main lecture", "Restore only the content before the main lecture", or "Restore only the layout before the main lecture", a corresponding instruction to restore the perspective before following is generated, and the information related to the restoration type is carried in the instruction to restore the perspective before following. Different restoration type-related information is generated depending on the button selected by the operating user. The collaborative application on the audience side uses the locally stored relevant content of the area displayed in the interactive interface of the collaborative application before the perspective follow, and / or the size and layout of each information block before the perspective follow, to restore the content and / or layout before the main lecture according to the instruction to restore the perspective before following.

[0185] In some embodiments, to improve the security of collaborative work among users, the information block is provided with permission control, and the permission is associated with the user ID of the user who logged into the collaborative application. The method further includes:

[0186] After the collaborative application is started, the obtained user ID is sent to the server for identity and authority authentication. Specifically: after the collaborative application on the audience side meets the authority requirements of the interactive interface of the collaborative application on the speaker side, the collaborative application on the audience side obtains the operation information of the information blocks existing in the interactive interface of its collaborative application on the speaker side in real time, and presents the operation information synchronously through the interactive interface of its own collaborative application and the various information blocks contained in the collaborative application for perspective following.

[0187] Example 3:

[0188] After providing a collaborative working method for a fused space as described in Examples 1 and 2, this application further provides a collaborative working method for a fused space. This is to explain the collaborative working method for the fused space in Examples 1 and 2 from a server perspective and to further analyze its design principles. It should be noted that the methods in Examples 1 and 2 are applicable to this embodiment and will not be described in detail in this embodiment.

[0189] A collaborative working method of a fusion space according to this embodiment is shown in FIG22 , and includes:

[0190] In step 501, the server receives a synchronization message for a shared canvas workspace; wherein the synchronization message carries relevant information of the added information block and identification information of the shared canvas workspace.

[0191] In step 502, the server identifies each collaborative application belonging to the same shared canvas workspace based on the identification information of the shared canvas workspace and sends a request message to add the same information block to the interaction interface of each collaborative application. Each collaborative application is identified and authorized using the user ID of the user logged into the collaborative application. For example, if user 1 is logged into collaborative application 1, user 1's user ID is used to identify and authorize collaborative application 1.

[0192] It should be noted that the request message for adding the same information block and the synchronization message received by the collaborative application from the server in Example 2 can be understood as the same message. Different descriptions are used to reflect different forms of expression on different subjects.

[0193] The various collaborative applications belonging to the same shared canvas workspace are obtained by the server based on the relationship between the drawing boards and collaborative applications stored in the server. The relationship between the drawing boards and collaborative applications is established in the server when the collaborative application is added to the drawing board or the collaborative application creates a drawing board.

[0194] In step 503, the server receives a request message from the speaker to follow the view of an information block in the interactive interface of the collaborative application on the speaker side. After verifying the permissions of the collaborative application on the speaker side, the server sends a request message to each collaborative application belonging to the same shared canvas workspace as the collaborative application on the speaker side, requesting whether to participate in the collaborative application on the audience side. The server then establishes a speaker-audience relationship based on the received response messages confirming participation. In other embodiments, the speaker-audience relationship can also be expressed as a view-following relationship.

[0195] In actual application scenarios, one server may be connected to multiple collaborative applications, as shown in FIG23 , or multiple servers may be connected to multiple collaborative applications. For example, in a distributed scenario, multiple servers may be connected to multiple collaborative applications.

[0196] The method further includes: the server receiving a message sent by the collaborative application as the speaker regarding operation information in an information block present in its own interactive interface. The server sends the operation information to the collaborative application as the audience in the shared canvas workspace, so that the collaborative application as the audience follows the perspective of the collaborative application as the speaker using the same information block present in its own interactive interface.

[0197] In some embodiments, when any collaborative application in the same shared canvas workspace adds a new information block to its interactive interface, the method further includes:

[0198] The server receives a synchronization message of a newly added information block sent by a collaborative application; the synchronization message carries relevant information of the newly added information block and the user ID that sends the synchronization message; the server forwards the synchronization message to other collaborative applications under its jurisdiction that belong to the same shared canvas workspace as the collaborative application that sends the synchronization message; wherein, after receiving the synchronization message, the other collaborative applications generate corresponding information blocks in the interactive interface of their respective collaborative applications.

[0199] In some embodiments, the method further includes: the server receiving a request for sharing information block content; wherein the request carries the requesting user ID, the designated user ID, and the content contained in the preview area of ​​the information block; and after the server completes permission verification for the requesting user ID and the designated user ID, forwarding the request to the collaborative application containing the designated user ID. The permission verification here primarily verifies whether the designated user has permission to view the requesting party's corresponding information block content. If the permission is insufficient, the server may also send a reminder to the requesting party indicating that the designated user has insufficient permission, and may even record the content sharing process on the server side to prevent risky operations.

[0200] Embodiment 4:

[0201] This application is based on the collaborative working method of the fusion space described in Examples 1 to 3, combined with specific application scenarios, and uses technical descriptions in related scenarios to illustrate the implementation process in the characteristic scenarios of this application.

[0202] This embodiment will take the actual application scenario shown in FIG23 where collaborative application 1 and collaborative application 2 belong to the same drawing board as an example to illustrate the various key steps.

[0203] When the operating user adds any information block in the collaborative application 1, this embodiment takes adding a link information block as an example, as shown in FIG24 and FIG25 , specifically includes:

[0204] In step 601, the operating user operates the Add Link Information Block button in the toolbar of the interactive interface of the collaborative application under any drawing board to generate an operation instruction. The collaborative application receives the operation instruction to add an information block in the drawing board. The operation instruction includes the identification information of the drawing board and the relevant information of the added link information block. According to the operation instruction, a synchronization message (which can be understood as the first synchronization message in Example 1) is generated. The first synchronization message carries the identification information of the drawing board, the identification information of the collaborative application that sends the synchronization message, and the relevant information of the added link information block, and the synchronization message is sent to the server.

[0205] In step 602, the server receives the synchronization message and forwards it to each collaborative application belonging to the sketchpad, including collaborative application 2. If the added information block is the first information block, the server also retrieves the corresponding web content from the network based on the synchronization message, and forwards the web content to each collaborative application belonging to the sketchpad, including the synchronization message.

[0206] In step 603, the cooperative application 2 receives the synchronization message from the server, and generates a link information block in its interactive interface according to the relevant information of the link information block added in the synchronization message.

[0207] Among them, when the added information blocks are in a serial relationship, each collaborative application operates on the same information block in an exclusive manner. When the added information blocks are in a parallel relationship, the information blocks in each collaborative application can be independently operated by the corresponding operating users and display independent operation results.

[0208] Here, taking the same link information block in collaborative application 1 and collaborative application 2 as an example of a serial relationship, before the link information block is exclusively operated by collaborative application 1, an exclusive operation request is sent to the server. If the server determines that the current link information block is not exclusively operated by other collaborative application 1, an exclusive confirmation message is returned to collaborative application 1. Collaborative application 1 implements exclusive operation on the link information block based on the exclusive confirmation message. During the exclusive operation, if collaborative application 1 refreshes the link information block, collaborative application 1 generates operation information based on the operation of the operating user on the link information block, and sends the operation information to the server. The server forwards the operation information to other collaborative applications under the drawing board (such as collaborative application 2). Other collaborative applications receive the operation information and display the corresponding operation results according to the operation relationship.

[0209] Taking the same link information block in collaborative application 1 and collaborative application 2 as an example of a parallel relationship, each collaborative application can operate the link information block in the corresponding interactive interface. For example, when collaborative application 1 and collaborative application 2 respectively perform refresh operations on the link information block, the server receives the operation information from collaborative application 1 and returns a response message, so that the link information blocks on each collaborative application can display their own web content.

[0210] When collaborative application 1 obtains the speaker permission, as shown in FIG26 and FIG27 , the following steps are specifically performed:

[0211] In step 701, the collaborative application 1 that obtains the speaker authority sends a view-following request message to the server. The view-following request message carries identification information of the speaker's user and identification information of the drawing board.

[0212] In step 702, the server verifies the authority of the source of the perspective following request message (i.e., collaborative application 1). After verifying that the authority of the collaborative application on the speaker side is passed, it sends a request message to other collaborative applications in the drawing board (such as collaborative application 2) to ask whether they participate as the collaborative application on the audience side.

[0213] In step 703, collaborative application 2 receives a request message from the server asking whether to participate as the audience-side collaborative application, and a pop-up window pops up in the interactive interface of collaborative application 2 so that the operating user can choose whether to participate in the pop-up window. When the operating application chooses to participate, a confirmation message is returned to the server.

[0214] In step 704, based on the confirmation message, the server establishes a view-following relationship with the source of the view-following request message (ie, collaborative application 1) as the speaker and the source of the confirmation message (ie, collaborative application 2).

[0215] Among them, when the collaborative application on the audience side returns a confirmation message to the server, the content, size and layout of each information block in the current interactive interface are also saved locally, so that after the relationship with the audience is cancelled, the content, size or layout of each information block on the audience side before the perspective follows can be restored.

[0216] When the perspective-following relationship is established, and collaboration application 1 is the collaboration application on the speaker side, and collaboration application 2 is the collaboration application on the audience side, as shown in FIG28 and FIG29 , the following steps are specifically performed:

[0217] In step 801, the collaborative application 1 sends the operation information in the information block in its own interactive interface to the server, wherein the operation information at least includes the operation content and the identification information of the drawing board.

[0218] In step 802, the server sends the operation information to all listener-side collaborative applications that have established view tracking with collaborative application 1 under the drawing board, such as collaborative application 2, based on the identification information of the drawing board in the operation information.

[0219] In step 803, the collaborative application 2 uses the same information block in the interactive interface of its own collaborative application to follow the perspective of the collaborative application on the speaker's side.

[0220] It should be noted here that this embodiment is only a schematic presentation of the key steps in Examples 1 to 3. In actual use, the collaborative working method of the fusion space described in any of Examples 1 to 3 is applicable in this embodiment.

[0221] Example 5:

[0222] Based on the collaborative working method of a fusion space described in Examples 1 to 4, this embodiment further provides a collaborative working device of a fusion space. In a specific application scenario, the device can be understood as a collaborative application on the speaker side. As shown in FIG30 , the device includes:

[0223] The first receiving module is used for the collaborative application to receive an operation instruction to add an information block in the shared canvas workspace it joins, where the information block includes a first information block that carries various types of web content, and the various types of web content can be embedded in the first information block for display.

[0224] The first response module is used for the collaborative application to respond to the operation instruction and send a first synchronization message to the server, so that the server sends the first synchronization message to each collaborative application that has joined the shared canvas workspace; the first synchronization message is used to instruct the addition of the information block in each collaborative application.

[0225] The first perspective following module is used to, when any collaborative application existing in the shared canvas workspace obtains the speaker permission, the collaborative application on the speaker side will send the operation information in the information block existing in its own interactive interface to the collaborative application on the audience side in the shared canvas workspace, so that the collaborative application on the audience side can achieve perspective following with the collaborative application on the speaker side through the same information block existing in its own interactive interface.

[0226] This embodiment also provides another collaborative working device for a fusion space. In a specific application scenario, the device can be understood as a collaborative application on the audience side. As shown in FIG31 , the device includes:

[0227] The second receiving module is used to receive a view-following request message initiated by the speaker side for information blocks in the interactive interface of the collaborative application on the speaker side from other collaborative applications belonging to the same shared canvas workspace.

[0228] The second response module is configured to establish a perspective-following relationship with an information block in the interactive interface of the collaborative application serving as the speaker after the other collaborative applications return a confirmation response. The request message is generated by the server after the collaborative application serving as the speaker sends a presentation request message to the server, and is sent by the server to other collaborative applications maintained by the server and belonging to the same shared canvas workspace as the collaborative application serving as the speaker.

[0229] The second perspective following module is used to establish a perspective following relationship with the information block existing in the interactive interface of the collaborative application as the speaker side, and the collaborative application as the audience side obtains the operation information of the information block existing in the interactive interface of the collaborative application as the speaker side in real time, and uses the same information block existing in the interactive interface of its own collaborative application to achieve perspective following with the collaborative application on the speaker side.

[0230] This embodiment also provides another collaborative working device for fusion space. In a specific application scenario, the device can be understood as a server. As shown in FIG32 , the device includes:

[0231] The third receiving module is configured to receive a synchronization message for the shared canvas workspace; wherein the synchronization message carries relevant information of the added information block and identification information of the shared canvas workspace.

[0232] A confirmation module is used to confirm the various collaborative applications belonging to the same shared canvas workspace based on the identification information of the shared canvas workspace, and send a request message to add the same information block in the interactive interface of each collaborative application; wherein, each collaborative application is identified and authorized by the user ID of the corresponding login collaborative application.

[0233] The relationship establishment module is used to receive a request message initiated by the speaker side for perspective following of an information block in the interactive interface of the collaborative application on the speaker side, and after verifying that the authority of the collaborative application on the speaker side is passed, send a request message to each collaborative application that belongs to the same shared canvas workspace as the collaborative application on the speaker side, asking whether to participate in the collaborative application on the audience side, and establish the relationship between the speaker and the audience based on the received response message confirming participation.

[0234] This embodiment also provides a computer device comprising: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and wherein the instructions are executed by the processor to perform the collaborative working method for a fused space described in any one of Examples 1 to 3. When performing the collaborative working method for a fused space described in Example 1, the device serves as a collaborative application on the speaker's side; when performing the collaborative working method for a fused space described in Example 2, the device serves as an application on the audience's side; and when performing the collaborative working method for a fused space described in Example 3, the device serves as a server. FIG33 is a schematic diagram of the architecture of a computer device according to an embodiment of the present application. The computer device according to this embodiment comprises one or more processors 21 and a memory 22. FIG33 illustrates a single processor 21 as an example. The processor 21 and the memory 22 may be connected via a bus or other means; FIG33 illustrates a bus connection as an example. The memory 22, as a non-volatile computer-readable storage medium, may be used to store non-volatile software programs and non-volatile computer executable programs, such as the collaborative working method for a fused space described in Example 1. The processor 21 executes the collaborative working method of the fusion space by running the non-volatile software programs and instructions stored in the memory 22. The memory 22 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, or other non-volatile solid-state storage device. In some embodiments, the memory 22 may optionally include a memory remotely located relative to the processor 21, and these remote memories may be connected to the processor 21 via a network. Examples of the above-mentioned network include but are not limited to the Internet, an intranet, a local area network, a mobile communication network, and a combination thereof. The program instructions / modules are stored in the memory 22, and when executed by the one or more processors 21, the collaborative working method of the fusion space described in any of the above-mentioned embodiments 1 to 4 is executed.

[0235] This embodiment also provides a non-volatile computer storage medium, which stores computer execution instructions. The computer execution instructions are executed by one or more processors to complete the collaborative working method of the fusion space described in any one of Examples 1 to 4.

[0236] The computer device of the embodiment of the present application may exist in various forms, including but not limited to:

[0237] (1) Mobile communication devices: These devices are characterized by their mobile communication capabilities and are primarily designed to provide voice and data communications. These terminals include smartphones (e.g., iPhones), multimedia phones, feature phones, and low-end phones.

[0238] (2) Ultra-mobile personal computer devices: These devices fall under the category of personal computers, have computing and processing capabilities, and generally also have mobile Internet access. These terminals include PDAs, MIDs, and UMPCs, such as the iPad.

[0239] (3) Portable entertainment devices: These devices can display and play video content and generally have mobile Internet access. These devices include video players, handheld game consoles, smart toys, and portable car navigation devices.

[0240] (4) Server: A device that provides computing services. The server consists of a processor, hard disk, memory, system bus, etc. The server is similar to a general computer architecture, but because it needs to provide highly reliable services, it has higher requirements in terms of processing power, stability, reliability, security, scalability, and manageability.

[0241] (5) Other electronic devices with video playback function or Internet connection function.

[0242] An embodiment of the present application also provides a non-volatile computer storage medium, which stores computer-executable instructions. The computer-executable instructions are executed by one or more processors, enabling the one or more processors to execute the collaborative working method of the fusion space described in any one of Examples 1 to 4.

[0243] It is worth noting that the information interaction, execution process, etc. between the modules and units within the above-mentioned devices and systems are based on the same concept as the processing method embodiments of the present application. For specific details, please refer to the description in the method embodiments of the present application and will not be repeated here. A person of ordinary skill in the art will understand that all or part of the steps in the various methods of the embodiments can be completed by instructing the relevant hardware through a program, and the program can be stored in a computer-readable storage medium, which can include: a read-only memory (ROM), a random access memory (RAM), a disk or an optical disk, etc.

[0244] The above description is only a preferred embodiment of the present application and is not intended to limit the present application. Any modifications, equivalent replacements and improvements made within the spirit and principles of the present application should be included in the scope of protection of the present application.

Claims

1. A collaborative working method of fusion space, characterized in that: The method comprises: The collaborative application receives an operation instruction to add an information block in the shared canvas workspace to which the collaborative application joins, wherein the information block includes a first information block carrying various types of web-end content, and the various types of web-end content can be embedded in the first information block for display; The collaborative application responds to the operation instruction and sends a first synchronization message to the server, so that the server sends the first synchronization message to each collaborative application that has joined the shared canvas workspace; the first synchronization message is used to instruct to add the information block to each collaborative application; When any collaborative application in the shared canvas workspace obtains the speaker's authority, the collaborative application as the speaker will send the operation information in the information block in its own interactive interface to the collaborative application as the audience in the shared canvas workspace, so that the collaborative application as the audience can follow the perspective of the collaborative application on the speaker through the same information block in its own interactive interface; Among them, the collaborative application serving as the speaker side is a collaborative application that has obtained the speaker authority in the shared canvas workspace, and the collaborative application serving as the audience side is one or more collaborative applications in the shared canvas workspace that have not obtained the speaker authority and have confirmed to join the speaker process, and the speaker process is initiated by the collaborative application serving as the speaker side.

2. The collaborative working method of the fusion space according to claim 1, characterized in that: The collaborative application on the speaker side sends the operation information in the information block in its own interactive interface to the collaborative application on the audience side in the shared canvas workspace, so that the collaborative application on the audience side can follow the perspective of the collaborative application on the speaker side through the same information block in its own interactive interface, specifically including: When the second information block in the collaborative application on the speaker side is edited, a follow-up message carrying identification information of the second information block and corresponding edited content is sent to the collaborative application on the listener side in the shared canvas workspace; so that the edited content on the speaker side is synchronously presented in the same second information block in each collaborative application on the listener side; When the collaborative application on the speaker side switches from editing the second information block to performing operations in the first information block carrying various types of web-side content, a follow-up message carrying identification information of the first information block and corresponding operation content is sent to the collaborative application on the audience side in the shared canvas workspace, so that the operation content of the speaker side can be synchronously presented in the same first information block in each collaborative application on the audience side.

3. The collaborative working method of the fusion space according to claim 1, characterized in that: When a new collaborative application temporarily joins the shared canvas workspace, wherein a first user ID is logged in to the new collaborative application, the method further includes: The collaborative application as the speaker receives a request message carrying the first user ID to join the shared canvas workspace; The collaborative application as the main speaker returns a response message for confirming joining; wherein the response message for confirming joining is used to establish a perspective following relationship between the new collaborative application and the collaborative application as the main speaker.

4. The collaborative working method of the fusion space according to claim 1, characterized in that: When the relationship between the speaker and the audience is not established, the operations of the collaborative applications on the same information block belonging to the same shared canvas workspace are in a serial relationship, and the method further includes: When the same information block belonging to the same shared canvas workspace is not operated by any collaborative application, each collaborative application can obtain exclusive operation on the same information block belonging to the same shared canvas workspace in its interactive interface; When any collaborative application takes an exclusive operation on any information block belonging to the same shared canvas workspace in its interactive interface, other collaborative applications that have not obtained the exclusive operation on the same information block belonging to the same shared canvas workspace shall synchronously update the content of the preview area in the same information block they own to the operation content in the preview area of ​​the same information block in the collaborative application that currently obtains the exclusive operation.

5. The collaborative working method of the fusion space according to claim 1, characterized in that: When the relationship between the speaker and the audience is not established, the operations of the various collaborative applications on the same information block belonging to the same shared canvas workspace are in a parallel relationship, and the method further includes: When the same information block belonging to the same shared canvas workspace is the target information block on which each collaborative application can perform parallel operations in its interactive interface, each collaborative application receives the operation information performed on the target information block in its own interactive interface, and presents the operation result in the preview area of ​​the target information block in its own interactive interface.

6. The collaborative working method of the fusion space according to claim 1, characterized in that: The collaborative application with review permission sends a request to the server to review the content in the preview area of ​​the same information block in each collaborative application that has been added to the same shared canvas workspace. The method further includes: After obtaining the contents of the respective preview areas in the same information block from different collaborative applications in the same shared canvas workspace, the collaborative application with the review permission mirrors a corresponding number of information blocks and presents the contents of the respective preview areas in each mirrored information block; or, After obtaining the contents of the respective preview areas in the same information block from different collaborative applications belonging to the same shared canvas workspace, the collaborative application with review permissions generates a corresponding number of switch pages in its own information block toolbar box corresponding to the number of different collaborative applications, wherein each switch page presents the contents of the preview area of ​​the same information block contained in a collaborative application.

7. The collaborative working method of the fusion space according to any one of claims 1 to 6, characterized in that: The method further comprises: When the collaborative application on the speaker side obtains the sharing of the preview area content of the specified information block to the specified user ID, the collaborative application on the speaker side sends a specified information block content directional sharing request to the server; wherein the specified information block content directional sharing request carries the speaker side user ID, the specified user ID, the specified information block identification information, and the content carried by the preview area in the specified information block.

8. The collaborative working method of the fusion space according to any one of claims 1 to 6, characterized in that: In each collaborative application, the added information blocks support respective adjustments, and the adjustments include one or more of enlargement, reduction, fading, rotation, and movement.

9. A collaborative working method of fusion space, characterized in that: The method comprises: Other collaborative applications belonging to the same shared canvas workspace as the collaborative application on the speaker side receive a request message initiated by the speaker side for view following of an information block in an interactive interface of the collaborative application on the speaker side; After the other collaborative application returns a confirmation response, a view-following relationship is established with the information block existing in the interactive interface of the collaborative application as the main speaker; The request message is generated by the server after the collaborative application as the main speaker sends a main speaker request message to the server, and is sent by the server to other collaborative applications maintained by the server and belonging to the same shared canvas workspace as the collaborative application as the main speaker; After establishing a perspective following relationship with the information block existing in the interactive interface of the collaborative application on the speaker side, the collaborative application on the audience side obtains the operation information of the information block existing in the interactive interface of the collaborative application on the speaker side in real time, and realizes perspective following with the collaborative application on the speaker side through the same information block existing in the interactive interface of its own collaborative application.

10. The collaborative working method of the fusion space according to claim 9, characterized in that: The step of following the perspective of the collaborative application on the speaker side by using the same information block in the interactive interface of the collaborative application of the speaker specifically includes: When the operation information includes operation contents for multiple information blocks, the collaborative application as the audience side splits the operation contents according to the identification information of the information blocks, and respectively carries the corresponding operation contents through the information blocks corresponding to the identification information on the interactive interface of its own collaborative application, so as to complete the synchronous presentation of perspective following.

11. The collaborative working method of the fusion space according to claim 9, characterized in that: Before other collaborative applications belonging to the same shared canvas workspace as the collaborative application on the speaker side receive a request message initiated by the speaker side for viewing a block in the interactive interface of the collaborative application on the speaker side, the method further includes: The collaborative application receives a synchronization message sent by the server; the synchronization message carries relevant information of the information block to be added and the second user ID that sends the synchronization message; wherein the collaborative application that receives the synchronization message sent by the server and the collaborative application logged in with the second user ID belong to the same shared canvas workspace; The collaborative application generates a corresponding information block in its interactive interface according to the relevant information of the information block to be added.

12. The collaborative working method of the fusion space according to any one of claims 9 to 11, characterized in that: After the other collaborative application returns a confirmation response, after establishing a perspective following relationship with the information block existing in the interactive interface of the collaborative application as the main speaker, the method further includes: The collaborative application on the audience side adjusts the display area of ​​the interactive interface of the current collaborative application, as well as the size and layout of each information block, to be consistent with the collaborative application on the speaker side according to the local confirmation full-view follow instruction; or, The collaborative application on the audience side follows the instructions based on the local confirmed content perspective, adjusts the display area of ​​the current collaborative application's interactive interface to be consistent with that of the collaborative application on the speaker's side, and keeps the size and layout of each information block in the interactive interface of the current collaborative application unchanged.

13. The collaborative working method of the fusion space according to any one of claims 9 to 11, characterized in that: The information block is provided with permission control, and the permission is associated with the user ID of logging into the collaborative application. The method further comprises: After the collaborative application is started, it sends the obtained user ID to the server for identity and authority authentication. Specifically: After the collaborative application on the audience side meets the permission requirements of the interactive interface of the collaborative application on the speaker side, the collaborative application on the audience side obtains the operation information of the information blocks existing in the interactive interface of its collaborative application on the speaker side in real time, and presents the operation information synchronously through the interactive interface of its own collaborative application and the various information blocks contained in the collaborative application for perspective following.

14. A collaborative working method of fusion space, characterized in that: The method comprises: The server receives a synchronization message for the shared canvas workspace; wherein the synchronization message carries relevant information of the added information block and identification information of the shared canvas workspace; The server identifies each collaborative application belonging to the same shared canvas workspace according to the identification information of the shared canvas workspace, and sends a request message for adding the same information block in the interaction interface of each collaborative application; wherein each collaborative application performs identity recognition and authority verification by the user ID of the corresponding login collaborative application; The server receives a request message initiated by the speaker for viewing the information block in the interactive interface of the collaborative application of the speaker, and after verifying the permission of the collaborative application of the speaker, sends a request message to the collaborative application of the speaker to the same shared Each collaborative application in the canvas workspace sends a request message to the collaborative application as the audience, and establishes a relationship between the speaker and the audience based on the received response message confirming participation.

15. The collaborative working method of the fusion space according to claim 14, characterized in that: The method further comprises: The server receives a message sent by the collaborative application as the main speaker for the operation information in the information block existing in its own interactive interface; The server sends the operation information to the collaborative application on the audience side in the shared canvas workspace, so that the collaborative application on the audience side can follow the perspective of the collaborative application on the speaker side through the same information block in its own interactive interface.

16. The collaborative working method of the fusion space according to claim 14 or 15, characterized in that: When any collaborative application belonging to the same shared canvas workspace adds a new information block in its interactive interface, the method further includes: The server receives a synchronization message of a newly added information block sent by the collaborative application; the synchronization message carries relevant information of the newly added information block and the user ID that sent the synchronization message; The server forwards the synchronization message to other collaborative applications under its jurisdiction that belong to the same shared canvas workspace as the collaborative application that sends the synchronization message; After receiving the synchronization message, other collaborative applications generate corresponding information blocks in the interactive interface of their respective collaborative applications.

17. The collaborative working method of the fusion space according to claim 14 or 15, characterized in that: The method further comprises: The server receives a request for sharing information block content; wherein the request for sharing information block content carries a requesting user ID, a designated user ID, and content carried in a preview area in the information block; After completing the authority verification of the requesting user ID and the designated user ID, the server forwards the information block content directional sharing request to the collaborative application where the designated user ID is located.

18. A collaborative working device integrating space, characterized in that: The device comprises: A first receiving module, configured for a collaborative application to receive an operation instruction to add an information block in a shared canvas workspace to which the collaborative application has joined, wherein the information block includes a first information block carrying various types of web-end content, and the various types of web-end content can be embedded in the first information block for display; A first response module, configured for the collaborative application to respond to the operation instruction and send a first synchronization message to the server, so that the server sends the first synchronization message to each collaborative application that has joined the shared canvas workspace; the first synchronization message is used to instruct to add the information block to each collaborative application; A first perspective following module is used for, when any collaborative application existing in the shared canvas workspace obtains the speaker authority, the collaborative application as the speaker side will send the operation information in the information block existing in its own interactive interface to the collaborative application as the audience side in the shared canvas workspace, so that the collaborative application as the audience side can achieve perspective following with the collaborative application on the speaker side through the same information block existing in its own interactive interface; Among them, the collaborative application serving as the speaker side is a collaborative application that has obtained the speaker authority in the shared canvas workspace, and the collaborative application serving as the audience side is one or more collaborative applications in the shared canvas workspace that have not obtained the speaker authority and have confirmed to join the speaker process, and the speaker process is initiated by the collaborative application serving as the speaker side.

19. A collaborative working device integrating space, characterized in that: The device comprises: The second receiving module is used to receive a view following request message initiated by the main speaker for an information block in an interactive interface of the collaborative application on the main speaker side, from other collaborative applications belonging to the same shared canvas workspace as the collaborative application on the main speaker side; The second response module is used to establish a perspective following relationship with the information block existing in the interactive interface of the collaborative application as the main speaker after the other collaborative application returns a confirmation response; The request message is generated by the server after the collaborative application as the main speaker sends a main speaker request message to the server, and is sent by the server to other collaborative applications maintained by the server and belonging to the same shared canvas workspace as the collaborative application as the main speaker; The second perspective following module is used for, after establishing a perspective following relationship with an information block existing in the interactive interface of the collaborative application on the speaker side, the collaborative application on the audience side obtains the operation information of the information block existing in the interactive interface of the collaborative application on the speaker side in real time, and realizes perspective following with the collaborative application on the speaker side through the same information block existing in the interactive interface of its own collaborative application.

20. A collaborative working device integrating space, characterized in that: The device comprises: A third receiving module, configured to receive a synchronization message for a shared canvas workspace; wherein the synchronization message carries relevant information of the added information block and identification information of the shared canvas workspace; A confirmation module, used to confirm each collaborative application belonging to the same shared canvas workspace according to the identification information of the shared canvas workspace, and send a request message for adding the same information block in the interaction interface of each collaborative application; wherein each collaborative application is identified and authorized by the user ID of the corresponding login collaborative application; The relationship establishment module is used to receive a request message initiated by the speaker side for perspective following of an information block in an interactive interface of a collaborative application on the speaker side, and after verifying that the authority of the collaborative application on the speaker side is passed, send a request message to each collaborative application that belongs to the same shared canvas workspace as the collaborative application on the speaker side, asking whether to participate in the collaborative application on the audience side, and establish a relationship between the speaker and the audience based on the received response message confirming participation.

21. A computer device, characterized in that: The device comprises: At least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the processor to execute the collaborative working method of the fusion space described in any one of claims 1-17.

22. A non-volatile computer storage medium, characterized in that: The computer storage medium stores computer execution instructions, and the computer execution instructions are executed by one or more processors to complete the collaborative working method of the fusion space described in any one of claims 1-17.

Images