KR101701110B1 - Method and apparatus for sharing common editing documents - Google Patents

Abstract

The present invention relates to a method and an apparatus for sharing a common editing document, and an apparatus for sharing a common editing document according to an embodiment of the present invention includes a seed document file A command delivery server for receiving an edit command from at least one client and transmitting an edit command to each of the at least one client in response to an order of receiving an edit command, A method for sharing a collaborative editing document that can quickly edit a shared document so that a plurality of clients can edit the same using a small resource, There is an effect that a device can be provided.

Description

[0001] METHOD AND APPARATUS FOR SHARING [0002] COMMON EDITING DOCUMENTS [

The present invention relates to a method and apparatus for sharing collaborative editing documents, and more particularly to a method and apparatus for sharing collaborative editing documents that can efficiently share collaboratively edited documents.

As the communication technology has recently developed, various services are being provided through the Internet. In particular, a large amount of files are moved and a large amount of data is transmitted and received via the Internet. As a result, technologies for sharing various files at anytime and anywhere via the Internet have developed.

Users who use terminals based on various communication technologies (for example, the Internet) can store data or files in a virtual repository, exchange data and files via a virtual repository, called cloud service. Cloud services allow users to freely use data or files. Specifically, the cloud service allows a user to download or upload data or files without restriction of time and space, and to share data or files with other users.

These cloud services are based on a shared server, a repository for storing and sharing data or files. Specifically, users can store and share document files through a shared server, and users can edit document files through their respective terminals.

However, when the users edit the shared document shared by their terminals, the sharing server receives the edited content input from each terminal of the users, reflects the edited contents in the shared document, ). Accordingly, as the number of terminals sharing the shared document increases, the shared server needs more engines required to reflect the contents of editing the shared document, and when many engines use the shared server, Of the load. That is, as the number of terminals sharing the shared document increases, the load for reflecting the edited contents in the shared document increases in the shared server, the performance of the shared server decreases, and the quality of the cloud service deteriorates.

Accordingly, there is a growing need to provide a method of sharing a shared document using a plurality of servers in order to reduce the load of a server providing shared documents for sharing and editing, and to efficiently share and edit shared documents.

[Related Technical Literature]

Document collaboration method (Korean Patent Laid-Open No. 10-2014-0028040)

SUMMARY OF THE INVENTION The present invention provides a method and apparatus for sharing a common editing document that can be quickly edited (hereinafter, referred to as a common editing document) so that a plurality of clients can edit the same using a small resource .

Another problem to be solved by the present invention is to provide a method and system for sharing a collaborative editing document that can quickly provide an updated collaborative editing document to a new client added when a new client shares a co- A method and an apparatus.

The problems of the present invention are not limited to the above-mentioned problems, and other problems not mentioned can be clearly understood by those skilled in the art from the following description.

According to an aspect of the present invention, there is provided an apparatus for sharing a common editing document, the apparatus including: a seed document file generated based on a document file uploaded to a shared server to be transmitted to at least one client; A command delivery server for receiving an editing command from at least one client and transmitting an editing command to each of the at least one client in accordance with the order in which the editing command is received; And a command storage server for storing edit commands.

According to another aspect of the present invention, an engine-pool server may be further included that receives the list of commands including edit commands and generates an update seed document file based on the seed document file and the list of commands .

According to another aspect of the present invention, the instruction storage server stores the edit instruction in the order of reception, generates an instruction list, and transmits the instruction list to the engine-pool server according to a predetermined condition.

According to another aspect of the present invention, the engine-pool server transmits the update seed document file to the seed document server, and the seed document server can store the update seed document file together with the seed document file.

According to another aspect of the present invention, when an additional client is connected to the seed document server to co-edit the document file, the seed document server sends an update seed document file to the additional client, The additional editing command stored after being transmitted to the server is transmitted to the command delivery server, and the command delivery server can send the additional editing command to the additional client.

According to still another aspect of the present invention, there is provided a file sharing apparatus, which can further include a shortcut file server that generates a shortcut file based on a document file when a shared server receives a shared signal to share the document file with at least one client have.

According to another aspect of the present invention, the shortcut file includes information on the location where the seed document file is stored, and each of the at least one client can receive the seed document file from the seed document server through the shortcut file.

According to another aspect of the present invention, each of the at least one client includes an engine for generating an update collaborative edit document file based on a seed document file and an edit command or based on an update seed document file and a further edit command can do.

According to an aspect of the present invention, there is provided a method of sharing a common editing document, the method comprising: transmitting a seed document file generated based on a document file uploaded to a shared server to at least one client; Receiving an edit command from at least one client, transmitting an edit command to each of the at least one client in accordance with the order in which the edit command was received, and storing the edit command in response to the order in which the edit command was received .

According to another aspect of the present invention, there is provided a method of generating an update seed document file, the method comprising: generating an instruction list by storing edit commands in an order of reception; and generating an update seed document file based on the seed document file and the instruction list.

According to another aspect of the present invention, there is provided a method of editing a document file, comprising: sending an update seed document file to an additional client when an additional client is connected to cooperate with the document file; The method may further include the step of transmitting.

According to another aspect of the present invention, transmitting the seed document file to the at least one client may comprise transmitting the seed document file to at least one client connected through a shortcut file generated based on the document file have.

According to an aspect of the present invention, there is provided a computer-readable recording medium storing instructions for providing a method of sharing a common editing document, Receiving an editing command from at least one client; transmitting an editing command to each of the at least one client in response to an order in which an editing command is received; Correspondingly, the editing command is stored.

The details of other embodiments are included in the detailed description and drawings.

The present invention provides a method and apparatus for sharing a common editing document that can quickly edit a shared document so that a plurality of clients can edit it using a small amount of resources.

The present invention provides a method and apparatus for sharing a collaborative editing document that can quickly provide an updated collaborative editing document to a new client added when a new client shares a collaborative editing document while editing the collaborative editing document There is an effect that can be.

The effects according to the present invention are not limited by the contents exemplified above, and more various effects are included in the specification.

FIG. 1 illustrates a relationship between a device sharing a common editing document, a shared file server, a shortcut file server, and a client according to an embodiment of the present invention.
FIG. 2 illustrates a procedure for sharing a common editing document file according to a method of sharing a common editing document according to an embodiment of the present invention.
FIG. 3 illustrates a configuration of a device sharing a common editing document according to an embodiment of the present invention and a relationship between clients.
Figures 4A and 4B illustrate exemplary output screens of a client's engine and client sharing a collaborative edited document by a method of sharing a collaborative editing document in accordance with an embodiment of the present invention.
FIG. 5 illustrates a configuration of a device sharing a common editing document according to another embodiment of the present invention and a relationship between the clients.
6A and 6B illustrate exemplary output screens of a client sharing a collaborative editing document by a method of sharing a collaborative editing document in accordance with another embodiment of the present invention.
FIG. 7 illustrates a configuration of a device sharing a common editing document and a relationship among clients according to another embodiment of the present invention.
8A and 8B illustrate an exemplary output screen of an engine and client of a client sharing a common editing document by a method of sharing a common editing document according to another embodiment of the present invention.

BRIEF DESCRIPTION OF THE DRAWINGS The advantages and features of the present invention, and the manner of achieving them, will be apparent from and elucidated with reference to the embodiments described hereinafter in conjunction with the accompanying drawings. The present invention may, however, be embodied in many different forms and should not be construed as being limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the invention to those skilled in the art. Is provided to fully convey the scope of the invention to those skilled in the art, and the invention is only defined by the scope of the claims.

The shapes, sizes, ratios, angles, numbers, and the like disclosed in the drawings for describing the embodiments of the present invention are illustrative, and thus the present invention is not limited thereto. In the following description, well-known functions or constructions are not described in detail since they would obscure the invention in unnecessary detail. Where the terms "comprises", "having", "done", and the like are used in this specification, other portions may be added unless "only" is used. Unless the context clearly dictates otherwise, including the plural unless the context clearly dictates otherwise.

In interpreting the constituent elements, it is construed to include the error range even if there is no separate description.

Although the first, second, etc. are used to describe various components, these components are not limited by these terms. These terms are used only to distinguish one component from another. Therefore, the first component mentioned below may be the second component within the technical spirit of the present invention.

Like reference numerals refer to like elements throughout the specification unless otherwise specified.

It is to be understood that each of the features of the various embodiments of the present invention may be combined or combined with each other partially or entirely and technically various interlocking and driving is possible as will be appreciated by those skilled in the art, It may be possible to cooperate with each other in association.

Hereinafter, terms used in this specification will be defined.

In the present specification, the seed document file is an editing file corresponding to a document file (hereinafter, collectively edited document file) to be jointly edited by the client, and means an editing document file shared by the client before the editing command is applied do. Such a seed document file is stored in a device sharing a common editing document, and can be transmitted to the client when the client requests sharing of the document file.

In the present specification, an editing command is an instruction for editing a document shared by a client, and includes various commands to be inputted into a common editing document. For example, the edit command may include a delete command for deleting at least some contents of the co-edited document, an insert command for inserting an object such as a picture, and the like. Editing commands entered at any client may be sent to a device that shares a collaborative editing document and then to a client connected to a device sharing the collaborative editing document.

In this specification, the command list is a list storing editing commands received in accordance with a predetermined rule upon receipt of an editing command. For example, the command list may be a list storing edit commands received until the update condition is satisfied.

Herein, the additional client means a client connected to a device sharing a common editing document after at least one editing command for the document file is inputted to the device sharing the common editing document. That is, the additional client means a client connected to a device sharing a common editing document after a client connected to a device that already shares a common editing document edits the seed document file.

FIG. 1 illustrates a relationship between a device sharing a common editing document, a shared file server, a shortcut file server, and a client according to an embodiment of the present invention.

Referring to FIG. 1, a device sharing a common editing document (hereinafter referred to as a common editing document sharing device) 100 includes a seed document server 110, a command delivery server 120, a command storage server 130, and an engine-pool server 140. The co-editing document sharing device 100 may be communicably connected to at least one client 900 and an additional client 910. [ In addition, the co-edited document sharing device 100 may be connected to the shared server 1000 and the shortcut file server 1200 so that they can communicate with each other.

The seed document server 110 may store the seed document file and the update seed document file, and may provide the seed document file to the engine-pool server 140.

The command delivery server 120 receives an edit command from at least one client 900 and transmits the edit command to at least one client 900 again. For example, the command delivery server 120 transmits the edit command received from the second client 902 to all of the at least one client 900. In addition, the command delivery server 120 transmits the edit command received from at least one client 900 to the command storage server 130.

The command storage server 130 stores edit commands sent from the command delivery server 120. [ In particular, the command storage server 130 may store edit commands in the order transmitted by the command delivery server 120. Here, the order transmitted by the command delivery server 120 may be the same as the order in which the command delivery server 120 receives the edit command. Further, the instruction storage server 130 may store the edit instructions in the order in which they were received to generate the instruction list, and may transmit the instruction list to the engine-pool server 140 according to a predetermined condition.

The engine-pool server 140 receives the seed document file from the seed document server 110, receives the instruction list from the instruction storage server 130, and generates an updated seed document file based on the seed document file and the instruction list do. In addition, the engine-pool server 140 transmits the updated seed document file to the seed document server 110 again.

Referring to FIG. 1, at least one client 900 includes a first client 901, a second client 902, and a third client 903. Although at least one client 900 is shown as including three clients in FIG. 1, the number of clients included in at least one client 900 is not limited thereto.

Referring to FIG. 1, at least one client 900 may upload a document file to the shared server 1000. Specifically, any one of the at least one client 900, for example, the first client 901, may upload a document file to be shared with the shared server 1000. [ Hereinafter, a method of sharing a common editing document based on the case where the first client 901 uploads a document file to the shared server 1000 will be described.

Also, each of the at least one client 900 includes an engine that is based on the seed document file and the edit command, or that generates an update common edit document file based on the update seed document file and further edit instructions. Specific functions of the engine included in each of the at least one client 900 will be described later with reference to FIGS. 4 and 8. FIG.

Referring to FIG. 1, a shared server 1000 may provide information about a document file to a collaborative editing document sharing apparatus 100. [0050] Referring to FIG. For example, the shared server 1000 may copy the document file and provide the seed document file to the co-edited document sharing device 100. [

Referring to FIG. 1, a shortcut file server 1200 is communicably connected to a shared server 1000. Specifically, the shortcut file server 1200 generates a shortcut file based on the document file uploaded to the shared server 1000. For example, when the first client 901 receives a shared signal to share a document file with other clients, the short file server 1200 directly Create a top file. A detailed description of the shortcut file will be given later with reference to FIGS. 7 and 8. FIG.

Accordingly, the collaborative editing document sharing device 100 including the command delivery server 120 and the engine-pool server 140, in which commands are transferred and the seed document file is updated, It is possible to reduce the waste of resources of the server, the speed of updating the common document file and the deterioration of the performance, which are caused when the common document file is updated every time the common document file is updated.

Each component of the co-edited document sharing device 100 is shown as an individual component for the sake of convenience of explanation, and may be implemented as one component or separate components into two or more components according to an implementation method.

FIG. 2 illustrates a procedure for sharing a common editing document file according to a method of sharing a common editing document according to an embodiment of the present invention. FIG. 3 illustrates a configuration of a device sharing a common editing document according to an embodiment of the present invention and a relationship between clients. Will be described with reference to Fig. 1 for convenience of explanation.

A method of sharing a collaborative editing document according to the present invention is initiated by a seed document server 110 transmitting a seed document file generated based on a document file uploaded to a shared server 1000 to at least one client 900 (S210).

Referring to FIG. 3, the seed document server 110 stores a seed document file, and is connected to the collaborative editing document sharing apparatus 100 to transmit a seed document file to a client requesting cooperative editing. Specifically, the seed document server 110 may store a plurality of seed document files. For example, when the seed document file is generated by a request from the client, the seed document server 110 stores the generated seed document file.

The seed document server 110 can also store the updated seed document file when the updated seed document file is generated based on the seed document file and the command list. For example, when the first seed document file 111 is generated at the request of the client, the first seed document file 111 is stored in the seed document server 110, and the first seed document file 111 and the instruction list The second seed document file is also stored in the seed document server 110. When the second seed document file is the update seed document file, Accordingly, the seed document server 110 can store at least one seed document file.

Referring to FIG. 3, the seed document server 110 may transmit the stored seed document file to at least one client 900. Specifically, when at least one client 900 wishes to share a document file, the seed document server 110 may send a seed document file corresponding to the document file requested to be shared to the client. A specific process by which the seed document server 110 transmits the seed document file to the client will be described later with reference to FIG. 5 and FIG.

Further, the seed document server 110 may request additional editing in addition to the client connected to the collaborative editing document sharing apparatus 100, so that the additional client 910 connected to the collaborative editing document sharing apparatus 100 may update the seed document file Can be transmitted. A specific process of transmitting the update seed document to the additional client 910 will be described later with reference to FIG. 7 and FIG.

Then, the command delivery server 120 receives an edit command from at least one client 900 (S220). Subsequently, the command delivery server 120 transmits an edit command to each of the at least one client 900 in accordance with the order in which the edit command is received (S230).

3, when the command delivery server 120 receives an edit command from one of the at least one client 900, the command delivery server 120 transmits the edit command received to all the clients included in the at least one client 900 do. For example, when the first client 901 inputs the first edit command 131, the command delivery server 120 receives the first edit command 131 and transmits the first edit command 131 to each of the at least one client 900. When the first client 901 sequentially inputs the second edit command 132 and the third edit command 133, the command delivery server 120 transmits a second edit command 132 to each of the at least one client 900 and then transmits the third edit command 133 to each of the at least one client 900. [ In FIG. 3, an edit command is transmitted from the first client 901, but the present invention is not limited thereto. The edit command may be arbitrarily transmitted from each of the at least one client 900.

In addition, the command delivery server 120 transmits an edit command to the command storage server 130 in the order received. For example, when the command delivery server 120 receives an edit command from the at least one client 900 in the order of the first edit command 131, the second edit command 132, and the third edit command 133 The command delivery server 120 also transmits the edit command to the command storage server 130 in the order of the first edit command 131, the second edit command 132, and the third edit command 133.

Accordingly, each of the at least one client 900 receives the edit command in real time through the command delivery server 120, applies the edit command to the seed document file held by each of the at least one client 900, Update common edit document can be generated. A specific process by which at least one client 900 generates an update common editing document will be described later with reference to FIG.

Then, the command storage server 130 stores the edit command in accordance with the order in which the edit command is received (S240).

Here, the step of the command delivery server 120 transmitting the edit command to the command storage server 130 may be concurrent with the step of the command delivery server 120 transmitting the edit command to the at least one client 900.

In addition, the command storage server 130 may generate an instruction list in the order in which the edit commands are received, and store the edit commands. Further, the instruction storage server 130 may transmit an edit command or a list of commands stored by predetermined conditions to the engine-pool server 140. [ Specific transmission relations of the edit command and the command list between the command storage server 130 and the engine-pool server 140 will be described later with reference to FIG. 7 and FIG.

Accordingly, the co-edited document sharing apparatus 100 can send an editing command to the at least one client 900 directly through the command delivery server 120, thereby efficiently editing the document file with a small processing load and a small resource usage And update it. In addition, the common editing document sharing device 100 stores the received editing command in order in the command storage server 130, so that even if a client to edit the document file is additionally connected, A document may be provided to the additional client 910. [

Figures 4A and 4B illustrate exemplary output screens of a client's engine and client sharing a collaborative edited document by a method of sharing a collaborative editing document in accordance with an embodiment of the present invention.

Referring to FIG. 4A, each of the at least one client 900 includes an engine 940. Engine 940 generates an update common edit document based on the seed document file and the edit command. For example, if each of the at least one client 900 has a first seed document file 111 and co-edits, the engine 940 in each of the at least one client 900 receives the received first edit command 131 ) To the first seed document file 111 to generate an update common edit document. That is, each of the at least one client 900 can generate and output an update common edit document based on the seed document file through the engine 940 each time it receives an edit command.

Referring to FIG. 4B, a joint editing document output screen 400 is output to each of at least one client 900. Specifically, the common editing document output screen 400 may output a seed document file, and output an updated common editing document generated by applying an editing command to the seed document file. For example, the first common editing document output screen 401 outputs the first seed document file 111. [ Thereafter, when each of the at least one client 900 receives the first edit command 431, the second common editing document output screen 402 displays the first seed document file 111 and the first seed document file 111 through the engine 940, And outputs the generated update common edit document based on the edit command 431. [

Accordingly, the edit commands sent from the command delivery server 120 are applied to the seed document file by the engine 940 at each of the at least one client 900, such that each of the at least one client 900 has an update common edit document And output an update common editing document to which editing commands transmitted in real time are applied.

The command delivery server 120 according to an embodiment of the present invention does not include an engine for applying an edit command to a seed document file to generate an update common edit document and transmits the edit command to at least one client 900 upon receiving the edit command . Accordingly, the co-edited document sharing apparatus 100 can reduce the resources and the load for the engine for generating the co-edited document, and can transmit the editing command to each of the at least one client 900 in real time. That is, through the cooperative editing document sharing device 100, each of the at least one client 900 can output the cooperative editing document more quickly.

FIG. 5 illustrates a configuration of a device sharing a common editing document according to another embodiment of the present invention and a relationship between the clients. 5 shows a process in which a seed document file is generated and transmitted to a client, and redundant description of the components already described with reference to FIG. 3 is omitted.

Referring to FIG. 5, at least one client 900 uploads a document file to the shared server 1000. When the shared server 1000 receives the shared signal, the shared server 1000 may transmit the uploaded document file to the shortcut file server 1200. The shared server 1000 may copy the uploaded document file to generate a seed document file and send the seed document file to the seed storage server 110. [ The seed document file is stored in the seed storage server 110, and the shortcut file server 1200 generates a shortcut file based on the uploaded document file. Here, the shortcut file includes information on the position where the seed document file is stored. Specifically, the shortcut file may include an address of the seed storage server 110 in which the seed document file generated based on the corresponding document file is stored, and information on the specific location stored in the seed storage server 110.

Referring to FIG. 5, each of the at least one client 900 receives a seed document file from the seed document server 110 via a shortcut file. Specifically, when at least one client 900 shares a document file uploaded to the shared server 1000, at least one client 900 does not directly share the uploaded document file, Receive the document file. Accordingly, each of the at least one client 900 performs a cooperative edit based on the received seed document file, and transmits the edited command entered for cooperative editing to the command delivery server 120. [ A specific mode in which at least one client 900 shares a seed document file via a shortcut file will be described later with reference to FIG.

The common editing document sharing apparatus 100 according to the embodiment of the present invention stores a seed document file for collaborative editing and transmits the seed document file to at least one client 900, You can save the document file for collaborative editing. That is, the client who uploaded the document file can separately manage the document file for co-editing and the document file of the private ownership.

6A and 6B illustrate exemplary output screens of a client sharing a collaborative editing document by a method of sharing a collaborative editing document in accordance with another embodiment of the present invention.

Referring to FIG. 6A, the common editing document output screen 610 displays a document file output from an arbitrary client. Also, the co-edited document output screen 610 displays the share button 611. [ Accordingly, a user of a certain client can transmit the shared signal to the sharing server 1000 by clicking the sharing button 611 in the currently output document file.

Referring to FIG. 6B, the document file management screen 620 is an exemplary screen of an application for managing a document file output from an arbitrary client. For example, the document file management screen 620 may be an exemplary screen of a file manager capable of storing a document file and managing whether or not to share the document file. Here, the document file management screen 620 displays the share button 621, and displays the document file 631 and the shortcut file 632. The document file management screen 620 may further display a drop-down menu 622 superimposed on the document file 631 or the shortcut file 632. [ Accordingly, a user of a certain client can select 'share' in the sharing button 621 or the drop-down menu 622 in the currently output document file and transmit the shared signal to the sharing server 1000.

Accordingly, the shared server 1000 receiving the shared signal transmits a signal to the shortcut file server 1200 to generate a shortcut file, generates a seed document file, and transmits the seed document file to the seed storage server 110.

FIG. 7 illustrates a configuration of a device sharing a common editing document and a relationship among clients according to another embodiment of the present invention. FIG. 7 shows a process of transmitting an update seed document file and a further edit command to an additional client, and a duplicate description of the elements already described with reference to FIGS. 3 and 5 is omitted.

7, when an additional client 910 is connected to the seed document server 110 for cooperative editing of the document file, the seed document server 110 transmits the update seed document file to the additional client 910. [ Herein, the additional client 910 sends a seed document to the seed document server 110 after the at least one client 900 has generated the update common edit document based on the first seed document file 111 and at least one edit command, It may be a client requesting co-editing of the file.

First, the seed document server 110 transmits the seed document file to the engine-pool server 140 according to a predetermined condition. For example, if at least one client 900 does not receive an edit command for a certain period of time, if more than 200 edit commands are stored in the command storage server 130, or if at least one of the clients 900 When the connection to the co-editing document sharing device 100 is terminated, the seed document server 110 transmits the first seed document file 111 to the engine-pool server 140.

In addition, the command storage server 130 transmits the generated command list 730 to the engine-pool server 140 according to a predetermined condition. Here, the instruction list 730 includes at least one edit instruction. For example, the command list 730 may be generated including a first edit command 131 and a second edit command 132. [

7, the instruction storage server 130 transmits the instruction list 730 generated based on at least one edit instruction to the engine-pool server 140 according to a predetermined condition. For example, if at least one client 900 does not receive an edit command for a certain period of time, if more than 200 edit commands are stored in the command storage server 130, or if at least one of the clients 900 The command storage server 130 may transmit the command list 730 to the engine-pool server 140 when the connection to the co-editing document sharing device 100 is terminated.

Then, the engine-pool server 140 generates an updated seed document file based on the received seed document file and the instruction list 730. [ For example, the engine-pool server 140 receives the first seed document file 111, receives the instruction list 730, and writes the first edit instruction word 131 and the second edit instruction word 132 in the first seed document file 111, 2 edit command 132 to generate a second seed document file 112 that is an updated seed document file.

Subsequently, the engine-pool server 140 transmits the generated update seed document file to the seed document server 110, and the seed document server 110 transmits the updated seed document file together with the first seed document file 111 2 seed document file 112 is stored. Accordingly, the seed document server 110 can transmit the update seed document file to the additional client 910 when the additional client 910 is connected.

7, the instruction storage server 130 transmits to the instruction delivery server 120 a further edit instruction 133 stored after the instruction list 730 is transmitted to the engine-pool server 140. [ After the command list 730 is transmitted to the engine-pool server 140, the edit command received by the command storage server 130 becomes an additional edit command. For example, since the command list 730 is transmitted to the engine-pool server 140, the further received third edit command 133 becomes a further edit command.

Referring to FIG. 7, the command delivery server 120 sends an additional editing command 133 to the additional client 910. Specifically, when an additional client 910 is connected to the seed document server 110, the third editing command 133, which is an additional editing command, is transmitted to the command delivery server 120 and is added through the command delivery server 120 The third editing command 133, which is an editing command, is transmitted to the additional client 910. [

That is, the additional client 910 may receive the updated seed document file from the seed document server 110, receive only the additional editing command from the command delivery server 120, and generate the updated common editing document. An engine for generating an update co-edited document will be described later with reference to Fig.

Receiving all of the first seed document file 111 and at least one edit command, when such an additional client 910 receives a first seed document file 111 that has already been converted into an update common edit document, It can be inefficient for co-editing.

Accordingly, the collaborative editing document sharing apparatus 100 stores editing commands in an instruction list 730 according to a predetermined condition, and generates an updated seed document file using the engine-pool server 140, 910) can receive the update seed document file and the additional editing command alone to more efficiently co-edit the document file.

Further, the command delivery server 120 delivers the individual editing command or the additional editing command directly to at least one client 900 and the additional client 910 in real time, and the engine-pool server 140 sends the seed document file and the command The shared editing document sharing apparatus 100 generates the updated seed document file based only on the list 730 and allows the shared editing document sharing apparatus 100 to execute the transfer of the command and the update of the seed document file in the dual server having different functions, The processing load can be reduced and the additional client 910 can quickly provide a file for collaborative editing. Accordingly, it is possible to execute editing of the document file shared by many clients through the co-edited document sharing device 100 more efficiently and quickly.

8A and 8B illustrate exemplary output screens of an engine and a client of a client sharing a common editing document by a method of sharing a common editing document according to another embodiment of the present invention.

Referring to FIG. 8A, an additional client 910 also includes an engine 940. Such an engine 940 performs the same function as the engine 940 included in each of the at least one client 900 as shown in FIG. 4A. Specifically, the engine 940 generates an update common edit document based on the received update seed document file 112 and the additional edit command 133. [

Referring to FIG. 8B, the common editing document output screen 800 is a screen output to the additional client 910, and outputs an updated common editing document. Specifically, the co-edited document output screen 800 displays an updated co-edited document including an indication 833 to which an additional editing command 133 is applied to the updated seed document file 112. [ For example, if the additional edit command 133 is to delete the 'God Bowser' line, the co-edited document output screen 800 displays an update co-edited document including an indication that the deletion has been applied. In FIG. 8B, the common editing document output screen 800 is displayed as indicating that the deletion is applied. However, according to the embodiment, the portion to which the deletion is applied may not be displayed. Depending on the characteristics of the additional editing command 133, And may or may not be displayed on the output screen 800.

The common editing document sharing apparatus 100 according to the embodiment of the present invention generates an updated seed document file through the engine-pool server 140 so that only the additional editing command is transmitted through the command delivery server 120 to the additional client 910 ) So that the command delivery server 120 does not include an engine for updating the co-edited document. Accordingly, as the client is added, the command delivery server 120 does not need to add an engine for updating the common edit document, and the processing load due to the increase of the engine is not increased. That is, the co-edited document sharing apparatus 100 reduces or minimizes the engine for updating the co-edited document, thereby enabling efficient and quick co-editing of the document even if the number of clients increases.

In this specification, each block or each step may represent a part of a module, segment or code that includes one or more executable instructions for executing the specified logical function (s). It should also be noted that in some alternative embodiments, the functions mentioned in the blocks or steps may occur out of order. For example, two blocks or steps shown in succession may in fact be performed substantially concurrently, or the blocks or steps may sometimes be performed in reverse order according to the corresponding function.

The steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. The software module may reside in a RAM memory, a flash memory, a ROM memory, an EPROM memory, an EEPROM memory, a register, a hard disk, a removable disk, a CD-ROM or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor, which is capable of reading information from, and writing information to, the storage medium. Alternatively, the storage medium may be integral with the processor. The processor and the storage medium may reside within an application specific integrated circuit (ASIC). The ASIC may reside within the user terminal. Alternatively, the processor and the storage medium may reside as discrete components in a user terminal.

Although the embodiments of the present invention have been described in detail with reference to the accompanying drawings, it is to be understood that the present invention is not limited to those embodiments and various changes and modifications may be made without departing from the scope of the present invention. . Therefore, the embodiments disclosed in the present invention are intended to illustrate rather than limit the scope of the present invention, and the scope of the technical idea of the present invention is not limited by these embodiments. Therefore, it should be understood that the above-described embodiments are illustrative in all aspects and not restrictive. The scope of protection of the present invention should be construed according to the following claims, and all technical ideas within the scope of equivalents should be construed as falling within the scope of the present invention.

100 co-editing document sharing device
110 seed document server
111 First Seed Document File
112 Second Seed Document File
113 Third Seed Document File
120 Command delivery server
130 Command storage server
131, 431 1st edit command
132 2nd edit command
133 Third Edit Command
140 Engine - Full Server
400, 610 Common editing document output screen
401 First Common Editing Document Output Screen
402 2nd Common Editing Document Output Screen
611, 621 Share button
620 Document File Management Screen
622 Drop-down menu
631 Document files
632 Shortcut File
730 List of Commands
833 Display with additional editing command applied
900 At least one client
901 First Client
902 Second Client
903 Third Client
910 Additional Clients
940 engine
1000 shared servers
1200 Shortcut File Server

Claims (13)

A seed document server for transmitting a seed document file generated based on a document file uploaded to a shared server to at least one client;
A command delivery server receiving only an edit command for editing the seed document file from the at least one client and transmitting the edit command to each of the at least one client immediately upon receiving the edit command; And
And a command storage server for storing the edit command in accordance with the order in which the edit command is received,
Wherein the command delivery server transmits the edit command in real time to each of the command store server and the at least one client in response to the order in which the edit command was received. The method according to claim 1,
Further comprising an engine-pool server for receiving the list of commands including the edit command and generating an updated seed document file based on the seed document file and the list of commands, Device. 3. The method of claim 2,
Wherein the command storage server stores the edit command in the order of reception and generates the command list, and transmits the command list to the engine-pool server according to a predetermined condition. 3. The method of claim 2,
The engine-pool server transmits the update seed document file to the seed document server,
Wherein the seed document server stores the update seed document file with the seed document file. 5. The method of claim 4,
If an additional client is connected to the seed document server to co-edit the document file,
The seed document server sends the update seed document file to the additional client,
Wherein the command storage server transmits to the command delivery server a further edit command stored after the command list is transmitted to the engine-pool server,
Wherein the command delivery server sends the additional edit command to the additional client. The method according to claim 1,
Further comprising a shortcut file server for generating a shortcut file based on the document file when the share server receives a share signal to share the document file with the at least one client, . The method according to claim 6,
Wherein the shortcut file includes information on a position at which the seed document file is stored,
Wherein each of the at least one client receives the seed document file from the seed document server via the shortcut file. The method according to claim 1,
Wherein each of said at least one client comprises an engine for generating an update common edit document file based on said seed document file and said edit instruction or based on an update seed document file and further edit instructions. A device that shares editing documents. A method of sharing a collaborative editing document, the method being performed in a device sharing a collaborative editing document including a seed document server, a command delivery server, and a command storage server,
Transmitting a seed document file generated based on a document file uploaded to a shared server to at least one client;
Receiving only an edit command for editing the seed document file from the at least one client through the command delivery server;
Transmitting the edit command to each of the at least one client immediately upon receiving the edit command; And
And storing the edit command in the command storage server corresponding to the order in which the edit command is received,
Wherein the command delivery server transmits the edit command in real time to each of the command store server and the at least one client in response to the order in which the edit command was received. 10. The method of claim 9,
Generating a command list by storing the edit commands in a received order; And
Further comprising generating an updated seed document file based on the seed document file and the instruction list. 11. The method of claim 10,
If additional clients are connected to co-edit the document file,
Transmitting the update seed document file to the additional client; And
Further comprising the step of sending a further edit command stored after the update seed document file is created to the additional client. 10. The method of claim 9,
Wherein the step of sending the seed document file to at least one client comprises the step of transmitting the seed document file to the at least one client connected through a shortcut file created based on the document file, How to. A computer-readable medium storing instructions for providing a method for sharing a collaborative editing document, the method comprising: providing a shared document editing server, the shared document editing server including a seed document server, a command delivery server, and a command storage server,
A seed document file generated based on a document file uploaded to a shared server is transmitted to at least one client,
Receiving only an edit command for editing the seed document file from the at least one client through the command delivery server,
Upon receiving the edit command, immediately transmits the edit command to each of the at least one client,
Storing the edit command in the command storage server in accordance with the order in which the edit command is received,
Wherein the command delivery server transmits the edit command in real time to each of the command storage server and the at least one client in accordance with the order in which the edit command is received. Are stored.

Images