File collaboration method

Abstract

The invention provides a file cooperation method. The file cooperation method comprises the following steps: establishing network connection between a server and a client; based on the established network connection, data information communication is performed through a user datagram protocol when the client and the server establish network communication connection, when the network communication connection is maintained and when the client executes collaborative editing operation, and collaborative editing servers are started at the server and the client respectively; the collaboration editing server comprises a collaboration file, the collaboration file is provided with a plurality of pages, part of or all the pages are provided with page release switches, and after the page release switches are set to be released or not released, the server side updates the attribute parameters of the corresponding file; and the client controls a display page of the client according to the information stored and recorded by the server. The problem that in the prior art, an owner cannot control the collaboration client to display part of pages of the collaboration file is solved.

Description

Technical Field

[0001] This invention relates to the field of online collaborative design, and more specifically, to a method for file collaboration. Background Technology

[0002] In existing technologies, in collaborative scenarios, all pages in a file are visible to anyone joining the collaboration in online design software.

[0003] In real-world scenarios, some files require continuous iteration, with different modules being organized and designed on different pages. To facilitate teamwork, it's necessary to share completed content with others before continuing creation; however, content that needs further creation—pages that haven't yet been organized and designed—is often kept private, forcing developers to save the unfinished parts to another file and then copy them to the previous file after completion. This results in low flexibility and inefficiency for developers sharing files. Summary of the Invention

[0004] The main objective of this invention is to provide a file collaboration method in which the file owner can control the display of partial pages of the collaborative file on the collaborative client.

[0005] To achieve the above objectives, a file collaboration method is provided according to the present invention, comprising: establishing a network connection between a server and a client; based on the established network connection, communicating data information via User Datagram Protocol when the client and server establish a network communication connection, when the network communication connection is maintained, and when the client performs collaborative editing operations; and starting collaborative editing servers on both the server and the client.

[0006] The collaborative editing server includes collaborative files with multiple pages. Some or all pages have a "publish page" switch. When the "publish page" switch is set to publish or not publish, the server updates the corresponding file's attribute parameter. The client controls the displayed page based on the information stored on the server.

[0007] As can be seen from the above scheme, multiple pages of collaborative files can be manipulated, so that when the "page publish" switch of some or all pages is set to publish or not publish, the server updates the corresponding file's attribute parameter; the client controls the page displayed on the client based on the information stored in the server's records.

[0008] Furthermore, collaborative files have a "file sharing" switch. When the "file sharing" switch is set, the server updates the corresponding file's attribute parameter; the client controls the displayed page based on the information stored on the server.

[0009] Furthermore, only users who are the file owners have permission to set the "file sharing" switch.

[0010] Furthermore, when the "File Sharing" switch is set to "On", the user who is the file owner has the permission to set the "Page Publishing" switch.

[0011] Furthermore, clients who are not the file owner and join the collaboration can only display pages with the "Publish" switch set to published. Applying the technical solution of this invention, the owner user role has the option to set both the "File Sharing" and "Page Publish" switches for the file, ensuring that non-owners can only see a portion of the collaborative file's pages.

[0012] In another embodiment of the present invention, when the "file sharing" switch is set to on, the user who is an editor or file owner has the permission to set the "page publishing" switch;

[0013] And / or when the "File Sharing" switch is set to off, the user who is the editor or file owner does not have permission to set the "Page Publish" switch.

[0014] Furthermore, when the "File Sharing" switch is turned on, clients with user roles such as readers or commenters, who are not editors or file owners, will only display pages whose "Page Publish" switch is set to be published.

[0015] Therefore, the "File Sharing" switch has general permissions. The owner can control whether to enable or disable this function through the "File Sharing" switch settings. When the "File Sharing" switch is enabled, the owner and editor can further enable the display of the client portion of the page by setting the "Page Publishing" switch.

[0016] Furthermore, when the "File Sharing" switch is set to off, clients with the user role of reader or commenter, or clients with the user role of editor, can see all pages of the collaborative file. In other words, the file is treated the same as files in existing technologies, and collaborators can see all collaborative files.

[0017] Furthermore, after the "File Sharing" or "Page Publishing" settings of the collaborative files are updated, the data is uploaded to the server in real time, and the server updates the corresponding file's attribute parameter. After receiving the change information, the server initiates a communication message to the collaborative client, and the collaborative client refreshes the page content after receiving the change information.

[0018] Furthermore, the client and server maintain communication using WebSocket technology.

[0019] Furthermore, the owner user role can perform any operation on the file content; the editor user role can read and edit the file, and can comment on the file; the commenter user role can read the file, can comment on the file, but cannot edit the file; the reader user role can only read the file.

[0020] By applying the technical solution of this invention, the owner's user role can set the "file sharing" switch for collaborative files, and the owner and editor can set the "page publishing" switch, so that readers or commenters can only see a portion of the collaborative file pages. Attached Figure Description

[0021] Figure 1 This is a collaborative synchronization communication diagram in the file collaboration method of Embodiment 1 of the present invention;

[0022] Figure 2 This is a flowchart of the "file sharing" switch setting process in the file collaboration method of Embodiment 1 of the present invention;

[0023] Figure 3 This is a diagram showing the specific page settings for the "file sharing" switch and the "page publishing" switch in the file collaboration method of Embodiment 1 of the present invention;

[0024] Figure 4 This is a flowchart of the "page publishing" identifier setting process in Embodiment 2 of the present invention.

[0025] Figure 5 This is a flowchart of the client-side file opening control page display process according to Embodiment 2 of the present invention.

[0026] The present invention will be further described below with reference to the accompanying drawings and embodiments. Detailed Implementation

[0027] It should be noted that, unless otherwise specified, the embodiments and features described in the present invention can be combined with each other. The present invention will now be described in detail with reference to the accompanying drawings and embodiments.

[0028] It should be noted that, unless otherwise specified, all technical and scientific terms used in this invention have the same meaning as commonly understood by one of ordinary skill in the art to which this invention pertains.

[0029] Obviously, the embodiments described above are merely some, not all, embodiments of the present invention. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without inventive effort should fall within the scope of protection of the present invention.

[0030] To address the problem in existing technologies where file owners, or those owners, cannot control the display of specific pages of collaborative files on the collaborative client, this invention provides a file collaboration method.

[0031] Example 1:

[0032] like Figure 1 , Figure 2 , Figure 3 As shown, a network connection is established between the server and the client. Based on the established network connection, data communication is conducted through the User Datagram Protocol (UDP) when the client and server establish a network communication connection, maintain the network communication connection, and when the client performs collaborative editing operations. Collaborative editing servers are started on both the server and the client. WebSocket technology is used to maintain communication between the client and the server.

[0033] The collaborative editing server includes collaborative files, which have multiple pages. Some or all of these pages have "Page Publish" switches 2 and 3. When the "Page Publish" switches 2 and 3 of a collaborative file are set to publish or not publish, that is, when the text settings are changed, client A transmits the changed settings to the server. The server then updates the corresponding attribute parameter of the file. Other collaborators, such as client B or client C, obtain the information stored on the server and control the display page on their clients.

[0034] The collaborative files also have a "file sharing" switch 1. When the "file sharing" switch 1 is set, that is, when the text settings are changed, client A transmits the changed settings to the server, and the server updates the corresponding file's attribute parameter; other collaborative clients control the display page according to the information stored on the server.

[0035] Collaborators' (user identities) permissions can be divided into owners, who can perform any operation on the document content; and non-owners, who only have local permissions and cannot perform any operation on the document.

[0036] Only users whose identity is the owner have permission to set the "File Sharing" switch 1.

[0037] like Figure 2 , Figure 3 The "File Sharing" switch 1 shown has general permissions. The setting of "File Sharing" switch 1 controls whether this function is enabled. When "File Sharing" switch 1 is set to off, "Page Publish" switches 2 and 3 cannot be set. "Page Publish" switches 2 and 3 can only be set when "File Sharing" switch 1 is set to on.

[0038] like Figure 2 As shown: The file in step S01 is opened;

[0039] Step S02 determines the user identity of the previous file;

[0040] If the user is determined not to be the owner, then the client frontend of the file in step S03 will not display the "File Sharing" switch 1. Alternatively, the client frontend will display the "File Sharing" switch 1, but the "File Sharing" switch 1 cannot be set.

[0041] When the user's identity is determined to be the owner, step S04 is executed, and the client front end displays "File Sharing" switch 1. At this time, the user can set "File Sharing" switch 1.

[0042] When the "File Sharing" switch 1 is changed, step S06 is executed, and the changed parameters are saved and uploaded to the server.

[0043] like Figure 3 As shown, after the owner enables the "File Sharing" switch 1, all pages have a page switch. The owner can adjust whether a page is open for collaboration at any time by setting the "Page Publish" switch button, such as... Figure 3 As shown, at this point, only pages 1 and 3 have their "Publish" switch set to "On," while the rest are "Off." Pages with the "Publish" switch on will have their "On" button highlighted, while those with the "Publish" switch off will not be highlighted; they can be grayed out or hidden. When the changed data is sent to the server, other non-owner clients, upon receiving the server's instruction and opening the collaborative file, will only display pages with the "Publish" switch set to "Publish." That is, upon receiving the server's change information, the non-owner clients' pages will immediately refresh. Non-owner clients joining the collaboration will only display pages with "Publish" switches 2 and 3 set to "Publish." In other words, only page 1 or page 3 will be displayed.

[0044] Further optimization involves ensuring that when the "File Sharing" switch 1 is set to off, all collaboration pages are open to collaborating clients.

[0045] The server backend monitors whether the "Publish" status page has been adjusted. Once an adjustment is made, the page of the client joining the collaboration will be refreshed immediately to ensure that the client joining the collaboration can only display the page with the "Page Publish" switch 2 and 3 set to the publishing status.

[0046] In other words, through the "File Sharing" switch 1, the file owner can control whether to enable or disable this function; when the function is disabled, collaboration is enabled on all pages; when the function is enabled, collaboration is enabled only on specified pages.

[0047] This allows file owners to control the collaborative file pages in collaborative scenarios and adjust the display pages on other non-owner clients in real time.

[0048] Example 2:

[0049] The difference from Example 1 is as follows: Figure 4 , 5 The permissions for collaborators (user identities) are further subdivided into: Owner: can perform any operation on the document content; Editor: can read and edit the document, and can post comments; Commenter: can read the document, can post comments, but cannot edit; Reader: can only read, and cannot comment or edit.

[0050] When the "File Sharing" switch 1 is set, only the owner has permission to set it. When the "File Sharing" switch 1 is set to "On", the user who is the editor or the owner has permission to set the "Page Publish" switches 2 and 3. When the "File Sharing" switch 1 is set to "Off", the user who is the editor or the file owner does not have permission to set the "Page Publish" switches 2 and 3.

[0051] When "File Sharing" switch 1 is set to "On", clients with the user role of reader or commenter will only display pages that are set to be published by "Page Publishing" switches 2 and 3.

[0052] When "File Sharing" switch 1 is set to off, all collaboration clients will display all pages of the collaborative files.

[0053] like Figure 5 As shown:

[0054] Step S21: Open the file;

[0055] Step S22 determines the user identity of this file;

[0056] When it is determined that the user is the owner or editor, step S23 is executed, and all pages of the file are displayed on the client front end.

[0057] If the user is determined not to be the owner or editor, step S24 is executed to determine whether the current file owner has set the "File Sharing" switch 1; if the "File Sharing" switch 1 is set to off, step S23 is executed, and all pages of the file are displayed on the client front end; if the "File Sharing" switch 1 is set to on, step S25 is executed, and the publishing identifiers of "Page Publishing: Switches 2 and 3" are read.

[0058] Step S26: Depending on whether "Page Publish" switches 2 and 3 are set, the client front-end only displays the pages of the file that have been published with "Page Publish" switches 2 and 3 set.

[0059] It should be noted that the terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the scope of exemplary embodiments according to the invention. As used herein, the singular form is intended to include the plural form as well, unless the context clearly indicates otherwise. Furthermore, it should be understood that when the terms "comprising" and / or "including" are used in this specification, they indicate the presence of features, steps, operations, devices, components, and / or combinations thereof.

[0060] The above are merely preferred embodiments of the present invention and are not intended to limit the present invention. Various modifications and variations can be made to the present invention by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the scope of protection of the present invention.

Claims

1. A file collaboration method, comprising: A network connection is established between the server and the client; Based on the established network connection, data communication is conducted via User Datagram Protocol when the client establishes a network communication connection with the server, when the network communication connection is maintained, and when the client performs collaborative editing operations. Collaborative editing servers are started on both the server and the client. The collaborative editing server includes a collaborative file with multiple pages. Some or all of the pages have a "page publish" switch. When the "page publish" switch is set to publish or not publish, the server updates the corresponding file's attribute parameter. The client controls the displayed page based on the information stored in the server's records.

2. The collaborative method according to claim 1, characterized in that... The collaborative file has a "file sharing" switch set. When the "file sharing" switch is set, the server updates the corresponding file's attribute parameter; the client controls the display page based on the information stored on the server.

3. The collaborative method according to claim 2, characterized in that, Only users who are the file owners have permission to set the "file sharing" switch.

4. The collaborative method according to any one of claims 2 or 3, characterized in that, When the "File Sharing" switch is set to "On", the user who is the owner of the file has the permission to set the "Page Publishing" switch; Alternatively, when the "File Sharing" switch is set to off, the user role is a reader, commenter, or editor client, and all pages of the collaborative file are visible.

5. The collaborative method according to claim 4, characterized in that, Clients that are not file owners and join the collaboration can only display pages whose "Page Publish" switch is set to the published state.

6. The collaborative method according to claim 3, characterized in that, When the "File Sharing" switch is set to "On", the user who is the editor or the file owner has the permission to set the "Page Publish" switch; and / or when the "File Sharing" switch is set to "Off", the user who is the editor or the file owner does not have the permission to set the "Page Publish" switch.

7. The collaborative method according to claim 6, characterized in that... When the "File Sharing" switch is turned on, the client whose user role is a reader or commenter, rather than an editor or file owner, will only display pages whose "Page Publish" switch is set to be published.

8. The collaborative method according to any one of claims 1-7, wherein, After the "File Sharing" switch or the "Page Publishing" switch is updated, the collaborative file data is uploaded to the server in real time, and the server updates the corresponding file attribute parameter. After receiving the change information, the server initiates a communication message to the collaborative client, and the collaborative client refreshes the page content after receiving the change information.

9. The collaborative method according to claim 8, characterized in that, The client and the server maintain communication using WebSocket technology.

10. The collaboration method according to claim 9, wherein the owner's user role can perform any operation on the content of the collaborative file; the editor's user role can read and edit the collaborative file and can comment on the collaborative file; the commenter can read the collaborative file and can post comments, but cannot edit it; the reader's user role can read the collaborative file, but cannot comment on the collaborative file or edit it.

Images