KR20210147566A - Method and system for providing collaborative document editing service - Google Patents

Abstract

Disclosed are a method and a system for providing a collaborative document editing service. According to an embodiment of the present invention, the system comprises a plurality of service nodes, and a managed node. The management node receives editing information on a user for a document to be edited from one of the service nodes to which a client device is connected when the document to be edited is edited by the user connected to one of the service nodes using the client device, and transmits the received editing information to the remaining service nodes among the service nodes, and an owner node for the document to be edited among the service nodes updates the document to be edited based on the editing information. Therefore, service stability can be improved.

Description

Method and system for providing document co-editing service

The disclosed embodiments relate to document co-editing techniques.

In the conventional document joint editing service, a plurality of users who want to edit a document access a specific service node providing an editing service, edit the document, and merge the contents edited by each user in the specific service node.

Accordingly, in the conventional document joint editing service, the document to be edited is dependent on a specific service node, and when the number of users to edit or the number or size of documents to be edited increases, the load on the service node is excessively increased. In order to solve this problem, the prior art restricts the number of users accessing the service or takes a method of limiting the number of documents to be edited, so there is a limit in providing a service to a plurality of documents or a plurality of users.

Republic of Korea Patent Publication No. 10-2005-0038867 (published on April 29, 2005)

The disclosed embodiments are for providing a document collaborative editing service.

An editing service providing system according to an embodiment includes a plurality of service nodes; and a management node, wherein when a document to be edited is edited by a user who has accessed one of the plurality of service nodes using a client device, the management node is configured to determine which of the plurality of service nodes the client device is being accessed. Receives the editing information of the user for the document to be edited from a service node, transmits the received edit information to the remaining service nodes among the plurality of service nodes, and the editing target of the plurality of service nodes An owner node for the document updates the edit target document based on the edit information.

The owner node may be a service node having an update right for the editing target document and the editing target document among the plurality of service nodes.

The management node may obtain status information from each of the plurality of service nodes when the owner node does not exist, and select one of the plurality of service nodes as the owner node based on the obtained status information. have.

When the number of users editing the editing target document exceeds a preset value, the owner node requests the management node to select an auxiliary owner node for the editing target document, and the management node is configured to: When selection of a node is requested, status information is obtained from each of the remaining service nodes except for the owner node among the plurality of service nodes, and the auxiliary service node is selected from among the remaining service nodes that have transmitted the status information based on the obtained status information. An owner node can be selected.

When the auxiliary owner node is selected, the owner node may provide the editing target document to the management node, and the management node may provide the editing target document and the editing target document to the auxiliary owner node.

The owner node updates the editing target document it owns based on editing information of some of the plurality of users who are editing the editing target document, and the auxiliary owner node is configured to: The editing target document owned by the owner node is updated based on the remaining part of the editing information, and the owner node and the auxiliary owner node have the editing target document held by the owner node and the editing target document owned by the auxiliary owner node according to a preset cycle. Documents can be synchronized.

When the number or total capacity of the document being managed as the owner node exceeds a preset value, the owner node requests the management node to change the owner node for some of the documents under management, and the management node is configured to: When an owner node change is requested, status information is obtained from each of the remaining service nodes except for the owner node among the plurality of service nodes, and the part of the remaining service nodes that have transmitted the status information based on the obtained status information You can select the owner node for the document.

The owner node requesting the change of the owner node provides the partial document to a management node when an owner node for the partial document is selected, and the management node provides the partial document as an owner node for the partial document can do.

The owner node divides the editing target document into two or more partial documents, when the size of the editing target document exceeds a preset value, and uses the management node as an owner node for some partial documents among the two or more partial documents request a change, and when the change of the owner node is requested, the management node obtains status information from each of the remaining service nodes except for the owner node among the plurality of service nodes, and based on the obtained status information An owner node for the partial document may be selected from among the remaining service nodes that have transmitted the status information.

When the owner node for the partial document is selected, the owner node provides the partial document as a management node, and the management node provides the partial document as an owner node for the partial document. can

An editing service providing method according to an embodiment is a method performed by an editing service providing system including a plurality of service nodes and a management node, and is performed by a user accessing one of the plurality of service nodes using a client device. receiving, by the management node, the editing information of the user for the editing target document from a service node to which the client device is connected among the plurality of service nodes when the editing target document is edited; transmitting, by the management node, the edited information to the remaining service nodes among the plurality of service nodes; and updating, by an owner node of the editing target document among the plurality of service nodes, the editing target document based on the editing information.

The owner node may be a service node having an update right for the editing target document and the editing target document among the plurality of service nodes.

The method may include, before the receiving step, when the owner node does not exist, the management node obtaining status information from each of the plurality of service nodes; and selecting, by the owner node, one of the plurality of service nodes as the owner node based on the acquired state information.

The method may include, when the number of users editing the editing target document exceeds a preset value, requesting, by the owner node, the management node to select an auxiliary owner node for the editing target document; obtaining, by the management node, status information from each of the remaining service nodes excluding the owner node among the plurality of service nodes, when the selection of the auxiliary owner node is requested; and selecting, by the owner node, the auxiliary owner node from among the remaining service nodes that have transmitted the status information based on the acquired status information.

The method may include, when the auxiliary owner node is selected, providing, by the owner node, the editing target document to the management node; and providing, by the management node, the editing target document and the editing target document to the auxiliary owner node.

The owner node updates the editing target document it owns based on editing information of some of the plurality of users who are editing the editing target document, and the auxiliary owner node is configured to: The editing target document owned by the owner node is updated based on the remaining part of the editing information, and the owner node and the auxiliary owner node have the editing target document held by the owner node and the editing target document owned by the auxiliary owner node according to a preset cycle. Documents can be synchronized.

The method may include: requesting, by the owner node, to change the owner node for some of the documents under management to the management node, when the number or total capacity of the documents being managed as the owner node exceeds a preset value; obtaining, by the management node, status information from each of the remaining service nodes excluding the owner node among the plurality of service nodes, when the change of the owner node is requested; and selecting, by the management node, an owner node for the partial document from among remaining service nodes that have transmitted the status information based on the acquired status information.

The method may include, when an owner node for the partial document is selected, providing, by the owner node requesting the change of the owner node, the partial document to a management node; and providing, by the management node, the partial document as an owner node for the partial document.

The method may include, when the size of the editing target document exceeds a preset value, dividing, by the owner node, the editing target document into two or more partial documents; requesting, by the owner node, to change the owner node for some partial documents among the two or more partial documents to the management node; obtaining, by the management node, status information from each of the remaining service nodes excluding the owner node among the plurality of service nodes, when the change of the owner node is requested; and selecting, by the management node, an owner node for the partial document from among the remaining service nodes that have transmitted the status information based on the acquired status information.

The method may include, when an owner node for the partial document is selected, providing, by the owner node, the partial document to a management node; and providing, by the management node, the partial partial document as an owner node for the partial partial document.

According to the disclosed embodiments, a user can access one of a plurality of service nodes to edit a document to be edited, but each service node shares the user's edit information through the management node and the owner node uses the shared edit information By updating the document to be edited by using it, the dependency between the document to be edited and the service node is resolved, and accordingly, the number of users who can use the service can be improved.

In addition, even if a failure occurs in a specific service node, users of the remaining service nodes are not affected by the failure, so the stability of the service can be improved.

Furthermore, when the load of the owner node increases due to an increase in the number of users editing the same editing target document, an increase in the number of documents managed by a specific node as an owner node, an increase in the size of the editing target document, etc., the owner node is changed Alternatively, more stable service can be provided by selecting an additional owner node and distributing the load.

1 is a block diagram of an editing service providing system according to an embodiment;
2 is a flowchart illustrating an example of a process of delivering a document to be edited according to an embodiment;
3 is a flowchart illustrating another example of a process of delivering a document to be edited according to an embodiment;
4 is a flowchart illustrating an example of an editing process for an editing target document according to an embodiment;
5 is a flowchart illustrating an example of an owner node change process according to an embodiment;
6 is a flowchart illustrating an example of an editing process for a document to be edited when an auxiliary owner node is selected according to the example shown in FIG. 5 ;
7 is a flowchart illustrating an example of an owner node change process according to an embodiment;
8 is a flowchart illustrating another example of an owner node change process according to an embodiment;

Hereinafter, specific embodiments of the present invention will be described with reference to the drawings. The following detailed description is provided to provide a comprehensive understanding of the methods, devices, and/or systems described herein. However, this is merely an example, and the present invention is not limited thereto.

In describing the embodiments of the present invention, if it is determined that the detailed description of the known technology related to the present invention may unnecessarily obscure the gist of the present invention, the detailed description thereof will be omitted. And, the terms to be described later are terms defined in consideration of functions in the present invention, which may vary according to intentions or customs of users and operators. Therefore, the definition should be made based on the content throughout this specification. The terminology used in the detailed description is for the purpose of describing embodiments of the present invention only, and should in no way be limiting. Unless explicitly used otherwise, expressions in the singular include the meaning of the plural. In this description, expressions such as “comprising” or “comprising” are intended to indicate certain features, numbers, steps, acts, elements, some or a combination thereof, one or more other than those described. It should not be construed to exclude the presence or possibility of other features, numbers, steps, acts, elements, or any part or combination thereof.

1 is a block diagram of an editing service providing system according to an exemplary embodiment.

Referring to FIG. 1 , the editing service providing system 100 according to an embodiment is to provide a joint editing service that allows a plurality of users to simultaneously edit the same document online, and a plurality of service nodes 110- 1, 110-2, 110-3) and a management node 120 .

In an embodiment, the plurality of service nodes 110-1, 110-2, 110-3 and the management node 120 may each be implemented as physically separate servers, but according to the embodiment, a plurality of service nodes ( 110) and at least some of the management node 120 may be implemented in the form of a virtual machine in the same server.

The client devices 130-1, 130-2, 130-3, 130-4, and 130-5 are devices used by each of a plurality of users who perform document editing using a joint editing service, respectively. The client device 130 may be, for example, a desktop PC, a laptop PC, a tablet PC, a smart phone, or the like, but is not necessarily limited to a specific type of device.

Meanwhile, in the embodiment shown in FIG. 1 and the following description, the number of service nodes 110-1, 110-2, and 110-3 is three for convenience of description, and the client devices 130-1 and 130-2 , 130-3, 130-4, 130-5) is assumed to be five, but the service nodes 110-1, 110-2, 110-3 and the client devices 130-1, 130-2, 130 -3, 130-4, 130-5) may be changed according to an embodiment.

On the other hand, the user of each client device (130-1, 130-2, 130-3, 130-4, 130-5) is connected to one of the plurality of service nodes (110-1, 110-2, 110-3) The editing target document may be edited, and in this case, the editing target document edited by each user may be the same or different.

For example, the user of the client device 1 130-1 connected to the service node 1 110-1 and the user of the client device 3 130-3 connected to the service node 2 110-2 are the documents 1 can be edited simultaneously. In addition, the user of the client device 2 130-2 connected to the service node 1 110-1, the user of the client device 4 (130-4) connected to the service node 3 110-3, and the client device 5 The user at 130-5 can edit document 2 at the same time.

Meanwhile, at least one of the plurality of service nodes 110-1, 110-2, and 110-3 may be an owner node for one or more editing target documents.

In this case, the owner node means a service node that has the right to update the editing target document and the editing target document, and may be selected for each editing target document. For example, when there are two editing target documents, an owner node may be selected for each editing target document, and the owner node for each editing target document may be the same or different.

On the other hand, the user of each client device (130-1, 130-2, 130-3, 130-4, 130-5) is connected to one of the plurality of service nodes (110-1, 110-2, 110-3) After that, you can select a document to be edited, and each client device 130-1, 130-2, 130-3, 130-4, 130-5 is connected to the currently connected service node 110-1, 110-2, 110. With -3), you can request the editing target document selected by the user.

2 is a flowchart illustrating an example of a process of delivering an editing target document according to an embodiment.

Referring to FIG. 2 , when the user of the client device 1 130 - 1 connected to the service node 1 110 - 1 selects 'document 1' as a document to be edited, the client device 1 130 - 1 provides a service A 'document 1' may be requested from node 1 110 - 1 ( 201 ).

At this time, when the service node 1 110 - 1 is the owner node for the 'document 1', the service node 1 110 - 1 provides the 'document 1' possessed by the service node 1 110 - 1 to the client device 1 130 - 1 . may (202).

On the other hand, when the user of the client device 3 130-3 connected to the service node 2 110 - 2 selects 'document 1' as the document to be edited, the client device 3 130 - 3 is the service node 2 110 -2) to request 'document 1' (203).

Thereafter, the service node 2 110 - 2 requests the 'document 1' from the management node 120 (204), and the management node 120 is the service node 1 110 - 1 which is the owner node for the 'document 1'. ) to request 'document 1' (205).

Meanwhile, the service node 1 110 - 1 having received a request for 'document 1' from the management node 120 may provide the 'document 1' it owns to the management node 120 ( 206 ).

Thereafter, the management node 120 provides the 'document 1' to the service node 2 110-2 (207), and the service node 2 110-2 sends the 'document 1' to the client device 3 130-3. may be provided (208).

3 is a flowchart illustrating another example of a process of delivering a document to be edited according to an embodiment.

Referring to FIG. 3 , when the user of the client device 2 130 - 2 connected to the service node 1 110 - 1 selects 'document 3' as the document to be edited, the client device 2 130 - 2 provides a service A 'document 3' may be requested from node 1 110 - 1 ( 301 ).

In this case, if the service node 1 110 - 1 is not the owner node for the 'document 3', the service node 1 110 - 1 may request the 'document 3' from the management node 120 ( 302 ).

On the other hand, when the owner node for 'document 3' does not exist, the management node 120 may request status information from each service node 110-1, 110-2, 110-3 (303, 304, 305).

Thereafter, each service node 110-1, 110-2, 110-3 that has received the status information transmits its own status information to the management node 120 (306, 307, 308).

At this time, the status information is, for example, CPU usage, memory usage, the number of connected clients, the number of documents with update authority, etc. to evaluate the performance of the service nodes 110-1, 110-2, 110-3. It may include a variety of information that can be used for

Meanwhile, the management node 120 that has received the status information from each of the service nodes 110-1, 110-2, and 110-3 selects an owner node for 'Document 3' based on the received status information (309). ).

In this case, the method of determining the owner node based on the state information is not necessarily limited to a specific embodiment, and various methods may be used depending on the embodiment.

Meanwhile, assuming that the owner node for 'Document 3' is determined as the service node 3 110-3, the management node 120 is selected as the service node 3 110-3 as the owner node for 'Document 3'. Notifies that it has been (310).

Thereafter, the service node 3 110 - 3 acquires 'document 3' (311), and transmits the obtained 'document 3' to the management node 120 (312).

In this case, the service node 3 110 - 3 may acquire 'document 3' from a preset document database. Specifically, the document database is accessible by all service nodes 110-1, 110-2, 110-3, and is a database preconfigured to store documents that can be selected as documents to be edited through a joint editing service. can be

Meanwhile, the management node 120 may transmit the 'document 3' received from the service node 3 110 - 3 to the service node 1 110 - 1 ( 313 ).

Also, the service node 1 110 - 1 may transmit the 'document 3' received from the management node 120 to the client device 2 130 - 2 ( 314 ).

Again, referring to FIG. 1 , when the user of each client device 130-1, 130-2, 130-3, 130-4, 130-5 that has received the editing target document edits the editing target document, each The client devices 130-1, 130-2, 130-3, 130-4, and 130-5 are service nodes 110-1, 110-2, 110-3 that are currently connected, and edit information about the document to be edited can be transmitted.

In this case, the editing information may include, for example, document identification information for identifying an editing target document, user identification information for identifying a user, and information corresponding to changes made by a user in the editing target document.

On the other hand, the service nodes 110-1, 110-2, 110-3 that have received the editing information from the client devices 130-1, 130-2, 130-3, 130-4, and 130-5, The information is transferred to another service node through the management node 120 , and the owner node may update the editing target document based on the received editing information.

Specifically, FIG. 4 is a flowchart illustrating an example of an editing process for an editing target document according to an exemplary embodiment.

In the example shown in FIG. 4 , in the client device 1 130-1 connecting to the service node 1 110-1 and the client device 4 130-4 connecting to the service node 3 110-3, the 'document It is assumed that 1' is being edited, and service node 2 110 - 2 is the owner node for 'document 1'.

Referring to FIG. 4 , when user 1, a user of client device 1 130-1, edits 'document 1', client device 1 130-1 edits 'document 1' according to the contents edited by user 1. User 1's edit information for ' may be transmitted to the service node 1 110 - 1 ( 401 ).

Thereafter, the service node 1 ( 110 - 1 ) may transmit the edit information of the user 1 to the management node ( 120 ) ( 402 ).

Thereafter, the management node 120 may transmit the edit information of the user 1 to the service node 2 110 - 2 and the service node 3 110 - 3 ( 403 and 404 ).

Meanwhile, the service node 3 110 - 3 receiving the edit information of the user 1 may transmit the edit information of the user 1 to the client device 4 130 - 4 ( 405 ).

In addition, the service node 2 110 - 2, which is the owner node of 'Document 1', has a ' Document 1' may be updated (406).

Thereafter, when user 4 who is a user of client device 4 130 - 4 edits 'document 1', client device 4 130 - 4 receives the user for 'document 1' according to the edited content by user 4 The edit information of 4 may be transmitted to the service node 3 110 - 3 ( 407 ).

Thereafter, the service node 3 110 - 3 may transmit the edit information of the user 4 to the management node 120 ( 408 ).

Thereafter, the management node 120 may transmit the edit information of the user 4 to the service node 1 110 - 1 and the service node 2 110 - 2 ( 409 and 410 ).

Meanwhile, the service node 1 110 - 1 that has received the edit information of the user 4 may transmit the edit information of the user 4 to the client device 1 130 - 1 ( 411 ).

In addition, the service node 2 110 - 2, which is the owner node of 'Document 1', is based on the edit information of User 4 received from the management node 120, and the ' Document 1' may be updated (412).

Referring back to FIG. 1 , the owner node for a specific document among the plurality of service nodes 110-1, 110-2, and 110-3 is the owner node for the number or total amount of managed documents, and to edit the specific document. To change the owner node or select one or more auxiliary owner nodes, the management node 120 may request a change of the owner node or selection of one or more auxiliary owner nodes based on at least one of the number of connected users and the size of the specific document. In this case, the management node 120 may change the owner node for a specific document or select one or more auxiliary owner nodes according to the request of the owner node.

5 is a flowchart illustrating an example of an owner node change process according to an embodiment.

In the example shown in FIG. 5 , service node 1 110 - 2 is an owner node for 'document 1', and client device 5 130 - 5 edits 'document 1' to service node 3 110 - 3) is assumed to be connected.

Referring to FIG. 5 , when user 5, who is a user of client device 5 130-5, selects 'document 1' as a document to be edited, client device 5 130-5 goes to service node 3 110-3. 'Document 1' may be requested (501).

Thereafter, the service node 3 110 - 3 requests 'document 1' from the management node 120 ( 502 ), and the management node 120 is the service node 1 110 - 1 which is the owner node for the 'document 1'. ) to request 'document 1' (503).

On the other hand, service node 1 110 - 1 having received a request for 'document 1' from the management node 120 determines whether the number of users editing 'document 1' exceeds a preset value, and if it exceeds, manages The node 120 may request selection of an auxiliary owner node for 'document 1' ( 504 ).

The management node 120 that has been requested to select an auxiliary owner node for 'Document 1' may request status information from each of the service node 2 110 - 2 and the service node 3 110 - 3 ( 505 and 506 ).

In addition, the service node 2 110 - 2 and the service node 3 110 - 3 that have received the status information may transmit their own status information to the management node 120 ( 507 , 508 ), respectively.

Meanwhile, the management node 120 that has received the status information from the service node 2 110 - 2 and the service node 3 110 - 3 is the service node 2 110 - 2 and the service node 3 based on the received status information. From (110-3), an auxiliary owner node for 'document 1' may be selected (509).

On the other hand, assuming that the secondary owner node for 'document 1' is selected as the service node 3 110 - 3 , the management node 120 is the service node 1 110 - 1 and the service node 3 110 - 3 As a result, it can be notified that the service node 3 110 - 3 has been selected as the secondary owner node for the 'document 1' (510, 511).

Thereafter, the service node 1 110 - 1 may transmit 'document 1' to the management node 120 ( 512 ), and the management node may transmit the received 'document 1 ' to the service node 3 110 - 3 . (513).

Thereafter, the service node 3 110 - 3 may transmit the 'document 1' to the client device 5 130 - 5 (514).

FIG. 6 is a flowchart for explaining an example of an editing process for a document to be edited when an auxiliary owner node is selected according to the example shown in FIG. 5 .

Referring to FIG. 6 , when user 1, a user of client device 1 130-1, edits 'document 1', client device 1 130-1 edits 'document 1' based on the contents edited by user 1. Edit information of user 1 for 1' may be transmitted to the service node 1 110 - 1 ( 601 ).

Thereafter, the service node 1 ( 110 - 1 ) may transmit the edit information of the user 1 to the management node ( 120 ) ( 602 ).

Thereafter, the service node 1 110 - 1, which is the owner node of 'Document 1', may update 'Document 1' that it owns to reflect the edit contents of User 1 based on the edit information of User 1 (603).

Meanwhile, the management node 120 may transmit the edit information of user 1 received from the service node 1 110 - 1 to the service node 2 110 - 2 and the service node 3 110 - 3 ( 604 and 605 ). ).

Thereafter, the service node 3 110 - 3 receiving the edit information of the user 1 may transmit the edit information of the user 1 to the client device 5 130 - 5 ( 606 ).

On the other hand, when user 5, a user of client device 5 130-5, edits 'document 1', client device 5 130-5 edits 'document 1' by user 5 according to the contents edited by user 5. The edit information of 5 may be transmitted to the service node 3 110 - 3 ( 607 ).

Thereafter, the service node 3 110 - 3 may transmit the editing information of the user 5 to the management node 120 ( 608 ).

Thereafter, the service node 3 110-3, which is the auxiliary owner node of 'Document 1', can update 'Document 1' it owns to reflect the edit contents of User 5 based on the edit information of User 5. There is (609).

Meanwhile, the management node 120 may transmit the edit information of user 5 received from the service node 3 110 - 3 to the service node 1 110 - 1 and the service node 2 110 - 2 (610 and 611 ). ).

Thereafter, the service node 1 110 - 1 that has received the edit information of the user 1 may transmit the edit information of the user 5 to the client device 1 130 - 1 ( 612 ).

On the other hand, in the example shown in FIG. 6 , the service node 1 110 - 1 which is the owner node for the document 1 and the service node 3 110 - 3 which is the auxiliary owner node for the document 1 respectively update the 'document 1' according to a preset cycle. ' by exchanging and merging through the management node 120 , the 'document 1' held in the service node 1 110 - 1 and the service node 3 110 - 3 can be synchronized.

Meanwhile, according to an embodiment, the plurality of service nodes 110-1, 110-2, and 110-3 each have a preset value for the number of documents being managed as the owner node or the total capacity of the documents being managed as the owner node. If it is exceeded, the management node 120 may request a change of the owner node for some of the documents being managed as the owner node.

In this case, the management node 120 selects an owner node for the requested document from among the plurality of service nodes 110-1, 110-2, and 110-3, except for the service node requesting the change of the owner node. can

7 is a flowchart illustrating an example of an owner node change process according to an embodiment.

In the example shown in FIG. 7 , it is assumed that the service node 1 110 - 2 is the owner node for 'document 1' and 'document 2', and requests to change the owner node for 'document 2'.

Referring to FIG. 7 , the service node 1 110 - 1 may request the management node 120 to change the owner node for 'document 2' ( 701 ).

Thereafter, the management node 120 receiving the owner node change request may request status information from the service node 2 110 - 2 and the service node 3 110 - 3 ( 702 and 703 ).

Thereafter, the service node 2 110 - 2 and the service node 3 110 - 3 from which the status information has been requested may transmit their own status information to the management node 120, respectively (704 and 705).

Meanwhile, the management node 120 that has received the status information from the service node 2 110 - 2 and the service node 3 110 - 3 is the service node 2 110 - 2 and the service node 3 based on the received status information. One of (110-3) may be selected as a new owner node for 'document 2' (706).

At this time, assuming that the new owner node for 'document 2' is determined as service node 3 (110-3), the management node 120 is service node 1 (110-1), which is the existing owner node for 'document 2'. and the new owner node, service node 3 110-3, may notify that the owner node for 'document 2' has been changed to service node 3 110-3 (707, 708).

Thereafter, the service node 1 110-1 transmits 'document 2' to the management node 120 (709), and the management node 120 transmits the received 'document 2' to the service node 3 110-3. It can be delivered (710).

Meanwhile, according to an embodiment, when the size of a document managed as an owner node exceeds a preset value, each of the plurality of service nodes 110-1, 110-2, and 110-3 divides the document into two or more parts. It is possible to request a change of an owner node for one or more of the two or more partial documents divided into documents and divided into the management node 120 .

In this case, the management node 120 selects the owner node for the partial division requested to be changed from among the remaining nodes except for the service node requesting the change of the owner node among the plurality of service nodes 110-1, 110-2, and 110-3. can do.

8 is a flowchart illustrating another example of an owner node change process according to an embodiment.

In the example shown in FIG. 8 , service node 1 110 - 2 is an owner node for 'document 1', and the capacity of 'document 1' exceeds a preset value, so 'document 1' is divided into two partial documents ' It is assumed that it is divided into 'Document 1-1' and 'Document 1-2'.

Referring to FIG. 8 , when the size of 'document 1' exceeds a preset value, service node 1 110-1 divides 'document 1' into two parts 'document 1-1' and 'document 1'. It can be divided by -2' (801).

Thereafter, the management node 120 may request to change the owner node for 'document 1-2' among the divided partial documents ( 802 ).

Thereafter, the management node 120 receiving the owner node change request may request status information from the service node 2 110 - 2 and the service node 3 110 - 3 ( 803 and 804 ).

Thereafter, the service node 2 110 - 2 and the service node 3 110 - 3 that have received the status information may transmit their own status information to the management node 120 ( 805 and 806 ).

Meanwhile, the management node 120 that has received the status information from the service node 2 110 - 2 and the service node 3 110 - 3 is the service node 2 110 - 2 and the service node 3 based on the received status information. One of (110-3) may be selected as a new owner node for 'document 1-2' (807).

At this time, assuming that the new owner node for 'Document 1-2' is determined to be the service node 2 (110-2), the management node 120 controls the service node 1 ( 110-1) and the new owner node, service node 2 110-2, may notify that the owner node for 'document 1-2' is changed to service node 2 (110-2) (808, 809).

Thereafter, the service node 1 110-1 transmits 'document 1-2' to the management node 120 (810), and the management node 120 transmits the received 'document 1-2' to the service node 2 (110). -2) can be transmitted (811).

Although the present invention has been described in detail through representative embodiments above, those of ordinary skill in the art to which the present invention pertains can make various modifications to the above-described embodiments without departing from the scope of the present invention. will understand Therefore, the scope of the present invention should not be limited to the described embodiments, but should be defined by the claims described below as well as the claims and equivalents.

10: Computing Environment
12: computing device
14: Processor
16: computer readable storage medium
18: communication bus
20: Program
22: input/output interface
24: input/output device
26: network communication interface
100: editing service providing system
110-1, 110-2, 110-3: service node
120: managed node
130-1, 130-2, 130-3, 130-4, 130-5: client device

Claims (20)

a plurality of service nodes; and
contains managed nodes;
The management node is configured to, when an editing target document is edited by a user accessing one of the plurality of service nodes using a client device, the editing target document from a service node to which the client device is connected among the plurality of service nodes receiving the edit information of the user for
and an owner node of the editing target document among the plurality of service nodes updates the editing target document based on the editing information.
The method according to claim 1,
and the owner node is a service node having an update right for the editing target document and the editing target document among the plurality of service nodes.
3. The method according to claim 2,
The management node obtains status information from each of the plurality of service nodes when the owner node does not exist, and selects one of the plurality of service nodes as the owner node based on the obtained status information service delivery system.
3. The method according to claim 2,
when the number of users editing the editing target document exceeds a preset value, the owner node requests the management node to select an auxiliary owner node for the editing target document;
When selection of the auxiliary owner node is requested, the management node obtains status information from each of the remaining service nodes except for the owner node among the plurality of service nodes, and provides the status information based on the obtained status information. An editing service providing system for selecting the auxiliary owner node from among the remaining service nodes transmitted.
5. The method according to claim 4,
the owner node provides the editing target document to the management node when the auxiliary owner node is selected;
wherein the management node provides the editing target document and the editing target document to the auxiliary owner node.
6. The method of claim 5,
The owner node updates the editing target document it owns based on editing information of some of the plurality of users who are editing the editing target document;
The auxiliary owner node updates the editing target document possessed by the auxiliary owner node based on the editing information of the remaining part of the plurality of users who are editing the editing target document;
The editing service providing system for the owner node and the auxiliary owner node to synchronize the editing target document held by the owner node with the editing target document holding by the auxiliary owner node according to a preset period.
3. The method according to claim 2,
When the number or total capacity of documents managed as the owner node exceeds a preset value, the owner node requests the management node to change the owner node for some of the documents under management;
When the change of the owner node is requested, the management node acquires status information from each of the remaining service nodes except for the owner node among the plurality of service nodes, and transmits the status information based on the acquired status information. An editing service providing system for selecting an owner node for the partial document from among the remaining service nodes.
8. The method of claim 7,
The owner node requesting the change of the owner node provides the partial document to a management node when an owner node for the partial document is selected;
The management node provides an editing service providing system for providing the partial document as an owner node for the partial document.
3. The method according to claim 2,
The owner node divides the editing target document into two or more partial documents, when the size of the editing target document exceeds a preset value, and uses the management node as an owner node for some partial documents among the two or more partial documents request a change,
When the change of the owner node is requested, the management node acquires status information from each of the remaining service nodes except for the owner node among the plurality of service nodes, and transmits the status information based on the acquired status information. An editing service providing system for selecting an owner node for the partial document from among the remaining service nodes.
10. The method of claim 9,
the owner node, when an owner node for the partial document is selected, provides the partial document as a management node;
wherein the management node provides the partial partial document as an owner node for the partial partial document.
A method performed by an editing service providing system comprising a plurality of service nodes and a management node, the method comprising:
When the editing target document is edited by a user who has accessed one of the plurality of service nodes using the client device, the management node sends the editing target document from the service node to which the client device is connected among the plurality of service nodes receiving the user's editing information for
transmitting, by the management node, the received edit information to the remaining service nodes among the plurality of service nodes; and
and updating, by an owner node of the editing target document among the plurality of service nodes, the editing target document based on the editing information.
12. The method of claim 11,
and the owner node is a service node having an update right for the editing target document and the editing target document among the plurality of service nodes.
13. The method of claim 12,
before the receiving step, when the owner node does not exist, the management node obtaining status information from each of the plurality of service nodes; and
and selecting, by the owner node, one of the plurality of service nodes as the owner node based on the acquired state information.
13. The method of claim 12,
when the number of users editing the editing target document exceeds a preset value, requesting, by the owner node, to select an auxiliary owner node for the editing target document from the management node;
obtaining, by the management node, status information from each of the remaining service nodes excluding the owner node among the plurality of service nodes, when the selection of the auxiliary owner node is requested; and
and selecting, by the owner node, the auxiliary owner node from among the remaining service nodes that have transmitted the status information based on the acquired status information.
15. The method of claim 14,
providing, by the owner node, the editing target document to the management node when the auxiliary owner node is selected; and
and providing, by the management node, the editing target document and the editing target document to the auxiliary owner node.
16. The method of claim 15,
The owner node updates the editing target document it owns based on editing information of some of the plurality of users who are editing the editing target document;
The auxiliary owner node updates the editing target document possessed by the auxiliary owner node based on the editing information of the remaining part of the plurality of users who are editing the editing target document;
The method for providing an editing service in which the owner node and the auxiliary owner node synchronize the editing target document held by the owner node with the editing target document held by the auxiliary owner node according to a preset period.
13. The method of claim 12,
requesting, by the owner node, to change the owner node for some of the documents under management to the management node when the number or total capacity of the documents being managed as the owner node exceeds a preset value;
obtaining, by the management node, status information from each of the remaining service nodes excluding the owner node among the plurality of service nodes, when the change of the owner node is requested; and
and selecting, by the management node, an owner node for the partial document from among remaining service nodes that have transmitted the status information based on the acquired status information.
18. The method of claim 17,
providing, by the owner node requesting the change of the owner node, to a management node when an owner node for the partial document is selected; and
and providing, by the management node, the partial document as an owner node for the partial document.
13. The method of claim 12,
dividing, by the owner node, the editing target document into two or more partial documents when the size of the editing target document exceeds a preset value;
requesting, by the owner node, to change the owner node for some partial documents among the two or more partial documents to the management node;
obtaining, by the management node, status information from each of the remaining service nodes excluding the owner node among the plurality of service nodes, when the change of the owner node is requested; and
and selecting, by the management node, an owner node for the partial document from among remaining service nodes that have transmitted the status information based on the acquired status information.
20. The method of claim 19,
providing, by the owner node, the partial document to a management node when an owner node for the partial document is selected; and
and providing, by the management node, the partial document as an owner node for the partial partial document.

Images