KR102287945B1 - Method and apparatus for providing calendar displaying work history of document - Google Patents

Abstract

A server for managing history information on document work includes: a communication unit configured to receive work history information of a document worked by a user's at least one first device from the at least one first device; and a control unit that reflects the received job history information to a calendar capable of showing schedule information using time information included in the received job history information, wherein the communication unit provides a calendar in which the job history information is reflected It can be provided by 2 devices.

Description

{Method and apparatus for providing calendar displaying work history of document}

A method and apparatus are provided for providing a calendar for displaying a work history of a document.

As document creation programs that provide various functions for document work, such as creation, viewing, and editing of documents, have been developed, document work using a computer has recently been activated.

As document work using a computer is activated, a single user frequently works on a plurality of documents.

However, since the conventional document creation program merely stores the document on which the work has been performed, there is an inconvenience in that the user has to directly manage the work history of the document. Accordingly, there is a need for a function for managing the work history of documents.

An object of the present invention is to provide a method and apparatus for providing a calendar for displaying a work history of a document. Another object of the present invention is to provide a computer-readable recording medium in which a program for executing the method in a computer is recorded. The technical problem to be solved is not limited to the technical problems as described above, and other technical problems may exist.

A server for managing history information on document work includes: a communication unit configured to receive work history information of a document worked by a user's at least one first device from the at least one first device; and a control unit that reflects the received job history information to a calendar capable of showing schedule information using time information included in the received job history information, wherein the communication unit provides a calendar in which the job history information is reflected It can be provided by 2 devices.

In the above-described server, an object indicating the work history information corresponding to the date may be displayed on the date field in the calendar.

In the above-described server, as an object in the calendar is selected, a document corresponding to the selected object may be executed in the second device.

In the above-described server, the document corresponding to the selected object may be provided from the first device to the second device.

In the above-described server, the document corresponding to the selected object may be provided from the server to the second device.

In the above-described server, the received work history information and the database for storing the work document; further comprising, the communication unit may receive the work document from the first device.

In the above-described server, an identification value of a user who worked on the document on the date may be displayed on the date field in the calendar.

In the above-described server, on the date field in the calendar, the identification value of the first device may be displayed on the date.

In the above-described server, the job history information includes a time at which the document job was performed, a name of the working document, a type of the working document, a type of the document job, an identification value of the user, and a value of the first device. It may include at least one of an identification value and a name of a program used for the document operation.

In the above-described server, the type of the document operation may include creation of the document, reading of the document, and editing of the document.

A method of managing history information on a document task, the method comprising: receiving, from the at least one first device, task history information of a document worked by a user's at least one first device; reflecting the received job history information in a calendar capable of showing schedule information using time information included in the received job history information; and providing a calendar reflecting the work history information to a second device.

In the above-described method, an object indicating the work history information corresponding to the date may be displayed on the date field in the calendar.

In the above-described method, as an object in the calendar is selected, a document corresponding to the selected object may be executed in the second device.

In the above-described method, the document corresponding to the selected object may be provided from the first device to the second device.

In the above-described method, the document corresponding to the selected object may be provided to the second device from the server.

In the above-described method, the step of storing the received work history information and the work document; further comprising, the receiving step may receive the work document from the first device.

In the above-described method, an identification value of a user who worked on the document on the date may be displayed on the date field in the calendar.

In the above-described method, the identification value of the first device may be displayed on the date field in the calendar.

In the above-described method, the job history information includes a time at which the document job was performed, a name of the working document, a type of the working document, a type of the document job, an identification value of the user, and a value of the first device. It may include at least one of an identification value and a name of a program used for the document operation.

A server for managing history information on document work includes: a communication unit configured to receive a document work request from at least one first device of a user; and working on the document according to the received job request, generating job history information of the worked document, and displaying schedule information using time information included in the job history information, the generated job and a control unit reflecting the history information, wherein the communication unit may provide the calendar in which the work history information is reflected to the second device.

A server for managing history information on document work includes: a communication unit configured to receive work history information of documents worked by first devices of users from the first devices; and a control unit that reflects the received job history information to a calendar capable of showing schedule information using time information included in the received job history information, wherein the communication unit provides a calendar in which the job history information is reflected It can be provided by 2 devices.

The computer-readable recording medium includes a recording medium in which a program for executing the above-described method in a computer is recorded.

1 is a diagram illustrating an example of a system for linking job history information to a user's calendar, according to some embodiments.
FIG. 2 is a diagram for explaining an example in which a server links work history information to a user's calendar when the devices have the same user and the devices perform a document job, according to some embodiments.
3 is a flowchart illustrating an example in which a server links job history information to a user's calendar, according to some embodiments.
4 is a flowchart illustrating an example in which a server links job history information to a calendar of a first user when a first device and a second device perform a document job, according to some embodiments.
5 is a flowchart illustrating an example in which a server links job history information to a user's calendar when a first device generates a document, according to some embodiments.
6 to 7 are diagrams for explaining an example in which the first device transmits job history information of the document to the server when the document is a text document according to some embodiments.
8 to 9 are diagrams for explaining another example in which the first device transmits job history information of the document to the server when the document is a text document according to some embodiments.
10 to 11 are diagrams for explaining another example in which the first device transmits job history information of the document to the server when the document is a text document according to some embodiments.
12 is a flowchart illustrating an example in which a server links job history information of a document to a calendar, according to some embodiments.
13 to 14 are diagrams illustrating an example of job history information of a document according to some embodiments.
15 is a flowchart illustrating an example in which a server links job history information to a user's calendar, according to some embodiments.
16 is a diagram illustrating an example of a daily calendar displayed on a screen of a device according to some embodiments.
17 is a diagram illustrating another example of a daily calendar displayed on a screen of a device according to some embodiments.
18 is a diagram illustrating another example of a daily calendar displayed on a screen of a device according to some embodiments.
19 is a diagram illustrating an example of a monthly calendar displayed on a screen of a device according to some embodiments.
20 is a diagram illustrating another example of a monthly calendar displayed on a screen of a device according to some embodiments.
21 is a diagram illustrating another example of a monthly calendar displayed on a screen of a device according to some embodiments.
22 to 25 are diagrams illustrating an example of an annual calendar displayed on a screen of a device according to some embodiments.
26A to 26B are flowcharts illustrating an example in which a server links job history information to a user's calendar when a first device creates a document and a second device reads the document, according to some embodiments.
27 is a diagram for describing an example in which a second device requests transmission of a document from a first device and receives a document, according to some embodiments.
28 to 30 are diagrams for explaining examples in which the second device terminates output of a document, according to some embodiments.
FIG. 31 is a diagram for describing an example in which a second device transmits job history information of a document to a server, according to some embodiments.
32A to 32B are flowcharts illustrating another example in which a server links job history information to a user's calendar when a first device creates a document and a second device reads the document, according to some embodiments.
33 is a diagram for describing an example in which a second device requests a server to transmit a document and receives a document, according to some embodiments.
34 is a flowchart illustrating an example in which a server links job history information of a document to a calendar, according to some embodiments.
35 to 36 are diagrams illustrating an example of job history information of a document according to some embodiments.
37 is a flowchart illustrating an example in which a server links job history information to a user's calendar, according to some embodiments.
38 to 40 are diagrams illustrating examples of a daily calendar displayed on a screen of a device according to some embodiments.
41 to 43 are diagrams illustrating examples of monthly calendars displayed on a screen of a device according to some embodiments.
44 to 47 are diagrams illustrating examples of annual calendars displayed on a screen of a device according to some embodiments.
48A to 48B are flowcharts illustrating an example in which a server links job history information to a user's calendar when the first device creates a document and the second device edits the document, according to some embodiments.
49 to 50 are diagrams for explaining examples of editing a document by a second device according to some embodiments.
51 is a diagram for describing an example in which a second device transmits a document and job history information of a document to a server according to some embodiments.
52 is a flowchart illustrating an example in which a server links job history information of a document to a calendar, according to some embodiments.
53 to 54 are diagrams illustrating an example of job history information of a document according to some embodiments.
55 is a flowchart illustrating an example in which a server links job history information to a user's calendar, according to some embodiments.
56 is a diagram illustrating an example of a daily calendar displayed on a screen of a device according to some embodiments.
57 is a diagram illustrating another example of a daily calendar displayed on a screen of a device according to some embodiments.
58 is a diagram illustrating another example of a daily calendar displayed on a screen of a device according to some embodiments.
59 is a diagram illustrating an example of a monthly calendar displayed on a screen of a device according to some embodiments.
60 is a diagram illustrating another example of a monthly calendar displayed on a screen of a device according to some embodiments.
61 is a diagram illustrating another example of a monthly calendar displayed on a screen of a device according to some embodiments.
62 is a diagram illustrating an example of an annual calendar displayed on a screen of a device according to some embodiments.
63 is a diagram illustrating another example of an annual calendar displayed on a screen of a device according to some embodiments.
64 is a diagram illustrating another example of an annual calendar displayed on a screen of a device according to some embodiments.
65 is a diagram illustrating another example of an annual calendar displayed on a screen of a device according to some embodiments.
66A to 66C are flowcharts illustrating another example in which a server links job history information to a user's calendar when the first device creates a document and the second device reads and edits the document, according to some embodiments; am.
67 to 68 are diagrams illustrating an example of job history information of a document according to some embodiments.
69 is a diagram illustrating an example of a daily calendar displayed on a screen of a device according to some embodiments.
70 is a diagram illustrating another example of a daily calendar displayed on a screen of a device according to some embodiments.
71 is a diagram illustrating another example of a daily calendar displayed on a screen of a device according to some embodiments.
72 is a diagram illustrating an example of a monthly calendar displayed on a screen of a device according to some embodiments.
73 is a diagram illustrating another example of a monthly calendar displayed on a screen of a device according to some embodiments.
74 is a diagram illustrating another example of a monthly calendar displayed on a screen of a device according to some embodiments.
75 is a diagram illustrating an example of an annual calendar displayed on a screen of a device according to some embodiments.
76 is a diagram illustrating another example of an annual calendar displayed on a screen of a device according to some embodiments.
77 is a diagram illustrating another example of an annual calendar displayed on a screen of a device according to some embodiments.
78 is a diagram illustrating another example of an annual calendar displayed on a screen of a device according to some embodiments.
79 to 80 are diagrams illustrating examples of calendars output on a screen of a device according to some embodiments.
81 to 82 are diagrams illustrating still other examples of a calendar output on a screen of a device according to some embodiments.
83 is a diagram for describing an example in which a mode of a calendar is switched, according to some embodiments.
84 is a diagram for explaining an example in which the server links work history information to a user's calendar when users of devices are different from each other and devices perform a document job, according to some embodiments.
85 is a flowchart illustrating an example in which a server links job history information to a user's calendar, according to some embodiments.
86 is a flowchart illustrating an example in which a server links job history information to a calendar of a first user when the first device and the second device perform a document job, according to some embodiments.
87 is a diagram for describing an example in which a server links work history information to a user's calendar when devices perform joint authoring of a document according to some embodiments.
88 is a flowchart illustrating an example in which a server links job history information to a user's calendar, according to some embodiments.
89A to 89B are flowcharts illustrating an example in which a server links job history information to a user's calendar when a first device and a second device jointly author a document, according to some embodiments.
90 is a diagram for describing an example of generating a document in a first device and a second device according to some embodiments.
91 is a diagram for explaining an example of transmitting documents generated by the first device and the second device and job history information of the documents to a server, according to some embodiments.
92 is a diagram for explaining an example of a process in which documents are combined by joint authoring of devices according to some embodiments.
93 is a diagram for explaining another example of a process in which documents are combined by joint authoring of devices according to some embodiments.
94A to 94B are flowcharts illustrating another example in which a server links job history information to a user's calendar when a first device and a second device jointly author a document, according to some embodiments.
95 is a diagram for explaining another example of a process in which documents are combined by joint authoring of devices according to some embodiments.
96 is a view for explaining an example of generating a final document by joint authoring of the first device, the second device, and the Nth device according to some embodiments.
97 is a diagram illustrating an example of displaying a history of documents generated by joint authoring in a monthly calendar displayed on a screen of a device according to some embodiments.
98 is a diagram illustrating another example of displaying a history of documents generated by joint authoring in a monthly calendar displayed on a screen of a device according to some embodiments.
99 is for explaining an example in which at least one of a plurality of devices corresponds to a server, and when the devices perform a document job, a device performing a server function links job history information to a user's calendar It is a drawing.
100 is a flowchart illustrating an example in which a first device links work history information to a user's calendar when a second device and a third device perform a document task, according to some embodiments.
101 is a view for explaining an example in which the server links work history information to the user's calendar when the user of the devices is the same and the server performs a document task based on a request of the devices, according to some embodiments am.
102 is a flowchart illustrating an example in which a server links job history information to a user's calendar, according to some embodiments.
103 is a flowchart illustrating an example in which the server links work history information to the calendar of the first user when the server performs a document work in response to a document work request from the first device, according to some embodiments.
104 is a flowchart illustrating an example in which the server links job history information to a user's calendar when the server generates a document according to some embodiments.
105 to 106 are diagrams for explaining an example in which a server executes a program to generate and store a document, and obtain job history information of the document, according to some embodiments.
107 is a flowchart illustrating an example in which a server links job history information of a document to a calendar, according to some embodiments.
108 to 109 are diagrams illustrating an example of job history information of a document according to some embodiments.
110 is a flowchart illustrating an example in which a server links job history information to a user's calendar, according to some embodiments.
111 is a diagram illustrating an example of a daily calendar displayed on a screen of a device according to some embodiments.
112 is a diagram illustrating another example of a daily calendar displayed on a screen of a device according to some embodiments.
113 is a diagram illustrating another example of a daily calendar displayed on a screen of a device according to some embodiments.
114 is a diagram illustrating an example of a monthly calendar displayed on a screen of a device according to some embodiments.
115 is a diagram illustrating another example of a monthly calendar displayed on a screen of a device according to some embodiments.
116 is a diagram illustrating another example of a monthly calendar displayed on a screen of a device according to some embodiments.
117 is a diagram illustrating an example of an annual calendar displayed on a screen of a device according to some embodiments.
118 is a diagram illustrating another example of an annual calendar displayed on a screen of a device according to some embodiments.
119 is a diagram illustrating another example of an annual calendar displayed on a screen of a device according to some exemplary embodiments.
120 is a diagram illustrating another example of an annual calendar displayed on a screen of a device according to some embodiments.
121A to 121C are diagrams illustrating a server performing a document job in response to a document job request from a first device, and a server providing job history information to the calendar of the first user when the second device reads the document, according to some embodiments. It is a flowchart showing an example of interworking.
122 is a diagram for explaining an example in which a second device requests a server to work on a document and receives information about a work screen, according to some embodiments.
123 is a diagram for explaining an example in which the second device terminates output of a work screen, according to some embodiments.
124 is a diagram for explaining an example in which a second device transmits job history information of a document to a server according to some embodiments.
125 is a flowchart illustrating an example in which a server links job history information of a document to a calendar, according to some embodiments.
126 to 127 are diagrams illustrating examples of job history information of a document according to some embodiments.
128 is a flowchart illustrating an example in which a server links job history information to a user's calendar, according to some embodiments.
129 is a diagram illustrating an example of a daily calendar displayed on a screen of a device according to some embodiments.
130 is a diagram illustrating another example of a daily calendar displayed on a screen of a device according to some embodiments.
131A to 131C illustrate a server generating a document according to a request of a first device and editing a document by a server according to a request of a second device, according to some embodiments It is a flowchart showing an example of interworking.
132 to 133 are diagrams for implementing examples in which a server edits a document according to some embodiments.
134 is a diagram for describing an example in which a server obtains job history information of a document, according to some embodiments.
135 is a flowchart illustrating an example in which a server links job history information of a document to a calendar, according to some embodiments.
136 to 137 are diagrams illustrating an example of work history information of a document according to some embodiments.
138 is a flowchart illustrating an example in which a server links job history information to a user's calendar, according to some embodiments.
139 is a diagram illustrating an example of a daily calendar displayed on a screen of a device according to some embodiments.
140 is a diagram illustrating another example of a daily calendar displayed on a screen of a device according to some embodiments.
141A to 141D show that when a server generates a document according to a request of a first device and the server provides a view of a document and edits a document according to a request of a second device, the server is a user It is a flowchart showing another example of linking job history information to the calendar of
142 to 143 are diagrams illustrating examples of calendars output on a screen of a device according to some embodiments.
144 to 145 are diagrams illustrating still other examples of a calendar output on a screen of a device according to some embodiments.
146 is a diagram for explaining an example in which a mode of a calendar is switched, according to some embodiments.
147 is a view for explaining an example in which the server links work history information to the user's calendar when the users of devices are different and the server performs a document task based on a request of the devices, according to some embodiments am.
148 is a flowchart illustrating an example in which a server links job history information to a user's calendar, according to some embodiments.
149 is a flowchart illustrating an example in which the server links work history information to the calendar of the first user when the server performs a document work in response to a document work request from the first device, according to some embodiments.
150 is a diagram for explaining an example in which the server links work history information to a user's calendar when devices perform joint authoring of a document according to some embodiments.
151 is a flowchart illustrating an example in which a server links job history information to a user's calendar, according to some embodiments.
152A to 152C are flowcharts illustrating an example in which a server links job history information to a user's calendar when a first device and a second device jointly author a document, according to some embodiments.
153 is a diagram for explaining an example of generating a document in a server according to some embodiments.
154 is a diagram for explaining an example of documents generated by a server and job history information of documents, according to some embodiments.
155 is a diagram for explaining an example of a process in which documents are combined by joint authoring of devices according to some embodiments.
156 is a diagram for explaining another example of a process in which documents are combined by joint authoring of devices according to some embodiments.
157A to 157C are flowcharts illustrating an example in which a server links job history information to a user's calendar when a first device and a second device jointly author a document, according to some embodiments.
158 is a diagram for explaining another example of a process in which documents are combined by joint authoring of devices according to some embodiments.
159 is a diagram for explaining an example of generating a final document by joint authoring of the first device, the second device, and the Nth device according to some embodiments.
160 is a diagram illustrating an example of displaying a history of documents generated by joint authoring in a monthly calendar displayed on a screen of a device according to some embodiments.
161 is a diagram illustrating another example of displaying the histories of documents generated by joint authoring in a monthly calendar displayed on a screen of a device according to some embodiments.
162 illustrates a device performing a function of a server when at least one of a plurality of devices corresponds to a server, and a device performing a function of a server based on a request of the devices performs a document job, according to some embodiments; A diagram for explaining an example of linking job history information to a user's calendar.
163 is a flowchart illustrating an example in which a first device links work history information to a user's calendar when a second device and a third device perform a document task, according to some embodiments.
164 is a configuration diagram of a server according to some embodiments.
165 to 166 are block diagrams of devices according to some embodiments.

Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings. The following examples of the present invention are only intended to embody the present invention and do not limit or limit the scope of the present invention. In addition, what can be easily inferred by a person of ordinary skill in the art to which the present invention belongs from the detailed description and examples of the present invention is construed as belonging to the scope of the present invention.

Throughout the specification, when a part is "connected" with another part, this includes not only the case of being "directly connected" but also the case of being "electrically connected" with another element interposed therebetween. . In addition, when a part "includes" a certain component, this means that other components may be further included rather than excluding other components unless otherwise stated.

In addition, throughout the specification, "gesture" refers to an action used by a user to control a terminal. For example, gestures described herein include tap, touch and hold, double tap, drag, pan, flick, drag and drop, hand shake, and the like.

In addition, throughout the specification, "output on the screen of the device" means that a specific screen is displayed on the screen of the device. Accordingly, "output on the screen of the device" includes "display on the screen of the device".

In addition, throughout the specification, "database" includes not only a set of data representing predetermined information, but also a storage for storing a set of data.

Hereinafter, some embodiments of the present invention will be described in detail with reference to the accompanying drawings.

1 is a diagram illustrating an example of a system for linking job history information to a user's calendar according to some embodiments of the present disclosure;

Referring to FIG. 1 , a system 1 includes a server 100 and devices 110 . The server 100 and the devices 110 may transmit/receive data based on a wired or wireless communication method.

The server 100 links the job history information to the user's calendar by using time information included in the job history information of the document received from at least one of the devices 110 . Here, the time information means information indicating a time when at least one of the devices 110 worked on a document. The calendar refers to an object that shows the user's schedule information. For example, when the user works on a document using the first device 111 , the first device 111 generates work history information as the document work is performed. The first device 111 transmits the job history information to the server 100 , and the server 100 extracts information indicating the time the document was worked from the job history information received from the first device 111 . Then, the server 100 links the job history information received from the first device 111 to the user's calendar by using the extracted time information.

Examples in which the first device 111 transmits the job history information to the server 100 are as follows. As an example, the first device 111 may transmit the job history information to the server 100 while generating the job history information. As another example, the first device 111 may generate and store job history information in the memory 16580 , and collectively transmit the job history information stored in the memory 16580 to the server 100 . As another example, the first device 111 generates and stores the work history information in the memory 16580, and when a synchronization request is received from the server 100, the work history information stored in the memory 16580 is transferred to the server ( 100) can also be sent.

If the job history information is generated while the user logs in to the server 100 , the first device 111 may immediately transmit the job history information to the server 100 . Meanwhile, when the user performs a document job using the first device 111 in a state where the user does not log in to the server 100 , the first device 111 may first store the job history information in the memory 16580 . When the user later logs in to the server 100 , the first device 111 may transmit job history information previously stored in the memory 16580 to the server 100 . In this case, the first device 111 may automatically transmit the job history information pre-stored in the memory 16580 to the server 100, but after receiving a transmission command from the user, the job history information pre-stored in the memory 16580 may be transmitted to the server 100 .

Also, the user may create a specific folder in the first device 111 and set the created folder to be connected to the server 100 . In this case, job history information of documents included in the folder may be transmitted to the server 100 , but job history information of documents not included in the folder may not be transmitted to the server 100 . However, only when the user logs in to the server 100 , the job history information of the document may be immediately transmitted to the server 100 . The job history information generated when the user does not log in to the server 100 may be transmitted to the server 100 when the user logs in to the server 100 later.

When the server 100 interlocks the job history information with the user's calendar, it means that the server 100 reflects the job history information on the user's calendar. Examples in which the server 100 reflects the work history information in the user's calendar are as follows.

As an example, the server 100 may store the job history information in the database 16430 according to the date the job was made. In other words, when the server 100 stores the job history information 16430 in the database, the server 100 may store the job history information according to the date the device worked on the document. For example, assuming that time information of “2014.05.14 AM 09:04:42” is included in the job history information received from the first device 111, the server 100 may The first job history information may be stored in a field corresponding to 14 . In this case, the database 16430 may be included in the server 100 or may be provided in a device separate from the server 100 . The server 100 may access the database 16430 through a calendar program installed in the server 100 to read, modify, and add job history information.

As another example, the server 100 may store job history information in the database 16430 , read pre-stored job history information through a calendar program installed in the server 100 , and display it on the calendar UI. For example, assuming that the first job history information among the job history information stored in the database 16430 is information on which the document was worked on on May 2014, the server 100 reads the first job history information from the database 16430 and reads the first job history information from the database 16430 on May 2014. It can be displayed on the calendar UI corresponding to . In this case, the server 100 may generate an indicator indicating the first job history information and display the generated indicator on the calendar UI.

As another example, the server 100 may directly reflect the job history information received from at least one of the devices 110 in a calendar through a calendar program installed in the server 100 . For example, assuming that job history information on a job performed on 2014.05.14 from the first device 111 is transmitted to the server 100, the server 100 corresponds to the job history information on 2014.05 through the calendar program. can be reflected in the calendar. In addition, the server 100 may store the calendar in which the job history information is reflected in the database 16430 .

The server 100 may reflect the job history information in the calendar or display the job history information on the calendar UI by generating an indicator indicating the job history information or the worked document. Here, the indicator means an object displayed on the calendar. For example, the indicator may include an icon, a pop-up window, and the like.

As an example, when the user selects an indicator displayed on the calendar output to the first device 111 , the server 100 may transmit job history information corresponding to the indicator to the first device 111 . Accordingly, the first device 111 may output job history information corresponding to the selected indicator on the screen.

As another example, when the user selects an indicator displayed on the calendar output to the first device 111 , the server 100 transmits a document corresponding to the indicator to the first device 111 or screen information indicating the document can be transmitted. Accordingly, the first device 111 may output a document corresponding to the selected indicator on the screen.

The device requests the server 100 to transmit the information to be displayed on the calendar, and the server 100 transmits the information to be displayed on the calendar to the device based on the received transmission request.

The device outputs the user's calendar on the screen based on the information received from the server 100 . Examples in which the device outputs the user's calendar on the screen are as follows.

As an example, a calendar program (or application) for a client (hereinafter, referred to as a first calendar program) is installed in the devices 110 , and a calendar program (or application) for a server (hereinafter, referred to as a first calendar program) is installed in the server 100 . a second calendar program) may be installed. In this case, the first device 111 may generate a calendar UI using the first calendar program and store the generated calendar UI in the memory 16580 . When job history information to be displayed by date in the calendar UI (or an indicator corresponding to the job history information) is received from the server 100, the first device 111 performs the calendar UI stored in the memory 16580 and the server 100 It is possible to output the job history information (or indicator) transmitted from the . For example, when the first device 111 requests the server 100 to transmit information to be displayed on the calendar, the server 100 may transmit the job history information (or indicator) stored in the database 16430 . . In addition, the first device 111 may read the calendar UI stored in the memory 16580 . In addition, the first device 111 may output the calendar on the screen by displaying the job history information (or indicator) transmitted from the server 100 on the read calendar UI. Alternatively, the first device 111 may receive the screen of the second calendar program from the server 100 and output (eg, mirror) the screen of the first device 111 as it is. One device 111 may output a user's own calendar on the screen.

As another example, when the server 100 creates a calendar and stores it in the database 16430, and the first device 111 requests the server 100 to transmit information to be displayed on the calendar, the calendar is converted into a web page. may be transmitted to the first device 111 . Here, the calendar generated by the server 100 includes a calendar UI and an indicator to be displayed on the calendar UI. In this case, the first device 111 may display the calendar on the screen by accessing the web page generated by the server 100 using a web browser. For example, when the first device 111 requests the server 100 to transmit information to be displayed on the calendar and transmits the user account to the server 100 , the server 100 receives the information from the first device 111 . The user can be authenticated using the transmitted user account. Then, the server 100 reads the calendar stored in the database 16430 and generates a web page using the read calendar. In addition, the first device 111 may output the calendar on the screen by accessing the web page generated by the server 100 using a web browser. Accordingly, the first device 111 may output the user's own calendar on the screen.

As described above, when the first device 111 requests the server 100 to transmit information to be displayed on the calendar, the server 100 transmits the information to the first device 111 . In other words, when the first device 111 executes the first calendar program, when the first device 111 executes the first calendar program and a specific year, month, day or hour is selected, or the first device It has been described that the server 100 transmits information to the first device 111 when the 111 transmits the user account to the server 100 . However, the present invention is not limited thereto.

As an example, the first device 111 and the server 100 may periodically synchronize information to be displayed on the calendar. As another example, even if there is no request from the devices 110 , the server 100 may periodically transmit information to be displayed on the calendar to the first device 111 .

As described above, it has been described that the device outputs the user's calendar on the screen. However, it is not limited thereto. In other words, the server 100 may output the user's calendar. For example, if the server 100 includes a display unit, the server 100 may output the user's calendar through the display unit. Also, if the server 100 and the manager's device are connected, the user's calendar may be output through the screen of the manager's device. In this case, the server 100 may output the calendar through the web page or the screen of the second calendar program.

On the other hand, the device may transmit only a part of the job history information. Examples in which the device transmits only a part of the job history information are as follows.

As an example, assuming that the first device 111 worked on the first to third documents, the first device 111 may transmit only the work history information of the first document to the server 100 .

As another example, assuming that the first device 111 creates and edits the first document, the first device 111 may transmit only the job history information generated by editing the first document to the server 100 .

As another example, when the display of the document output on the screen is finished, the first device 111 may display an indicator asking whether to transmit the job history information to the server 100 on the screen. In this case, only when a user input requesting to transmit the job history information to the server 100 is received through the user input unit 16510 , the server 100 may transmit the job history information to the server 100 .

As another example, the first device 111 may transmit only work history information of a document worked in a specific period to the server 100 . For example, the first device 111 may transmit, to the server 100 , only job history information of documents worked from 2014.05.01 AM 00:00:00 to 2014.05.05 PM 11:59:59. Also, the first device 111 may transmit only job history information of a document worked between 09:00:00 AM and 05:59:59 PM to the server 100 .

As another example, the user may designate a device to transmit the job history information to the server 100 among the devices 110 , and only the designated device may transmit the job history information to the server 100 . For example, assuming that the user has designated the first device 111 among the devices 110 , only the first device 111 among the devices 110 may transmit the job history information to the server 100 .

Also, the server 100 may link only a part of the job history information received from the first device 111 to the user's calendar. In other words, the number of work history information transmitted to the server 100 and the number of work history information linked to the user's calendar may be different. Other examples of the number of job history information transmitted to the server 100 and the number of job history information linked to the user's calendar are as follows.

As an example, assuming that the first device 111 transmits the job history information of the first to third documents to the server 100, the server 100 stores only the job history information of the first document in the user's calendar. can also be linked.

As another example, assuming that the first device 111 transmits the job history information generated by generating the first document and the job history information generated by editing the first document to the server 100, the server 100 Only job history information generated by editing the first document may be linked to the calendar.

When a user works on a document using the first device 111 to the Nth device 114 , each device generates work history information as the document is processed. In other words, the first device 111 generates first job history information, and the Nth device 114 generates Nth job history information. The first device 111 to the Nth device 114 transmits job history information to the server 100 , and the server 100 receives the first job from the first device 111 to the Nth device 114 . Information indicating the time the document was worked is extracted from the history information to the Nth job history information. Then, the server 100 links the work history information received from the first device 111 to the Nth device 114 with the user's calendar using the extracted time information.

In this case, as described above, each device may transmit only a part of the job history information or the server 100 may link only a part of the received job history information to the user's calendar.

In the above-described example, a user means a subject who works on a document by using at least one of the devices 110 . For example, the devices 110 may be devices of the same user or devices of different users.

In addition, in the above-described example, when the user works on a document by using at least one of the devices 110 , it may mean that the user works on the document by using a program installed in the devices 110 , but is limited thereto. doesn't happen For example, the user may work on a document by using a program installed in the server 100 through at least one of the devices 110 .

In addition, in the above-described example, it has been described that the user works on a document using at least one of the devices 110 , but the present invention is not limited thereto. For example, the user may perform a content task using at least one of the devices 110 .

The document includes a text document or a multimedia document. For example, the document may include a target on which a task is performed by a word program, an Excel program, a power point program, etc. installed in the devices 110 or the server 100 .

In addition, the content includes photos, images, videos, music, and the like. For example, the content may include a target on which a task is performed by a photo execution program, an image execution program, a video execution program, a music execution program, etc. installed in the devices 110 or the server 100 .

Working with documents means creating, viewing or editing documents. For example, when the first device 111 performs a document operation, the first device 111 generates a document, the first device 111 reads a document, or the first device 111 reads a document This may include editing.

Here, when the first device 111 reads the document, the first device 111 outputs the document on the screen. Also, when the first device 111 edits the document, the first device 111 adds new content to the content of the previously created document or deletes the content included in the previously created document. In addition, document work may include not only creation and viewing of documents, but also transmission, copying, or deletion of documents.

When an indicator is selected according to a user input received through the user input unit 16510 of the device, the device may output job history information on the screen. For example, the indicator may indicate a type or name of a document, an identification value of a user, an identification value of a device, and the like. Here, the identification value of the user may include the name of the user, and the identification value of the device may include the name of the device.

Also, as the indicator is selected, work history information of the document may be output. Also, as the indicator is selected, a document on which an operation is performed may be output.

The job history information means information generated when at least one of the devices 110 performs a document job. For example, the job history information may include a time at which the document job was performed, the name of the document being worked on, the type of the document being worked on, the type of the document job, the user's identification value, the device identification value, and the name of the program used for the document operation. may include.

The server 100 refers to a subject that transmits and receives data to and from the plurality of devices 110 . For example, the server 100 may be a cloud server or a personal server. Here, the personal server may correspond to a device serving as a server among the plurality of devices 110 .

The device transmits and receives data to and from the server 100 . For example, the device may include a desktop PC, a notebook PC, a laptop PC, a smart phone, a tablet PC, a wearable device, and the like.

Hereinafter, examples in which the server 100 generates job history information of a document will be described with reference to FIGS. 2 to 163 . Content to be described later with reference to FIGS. 2 to 163 means examples of the method described above with reference to FIG. 1 . Accordingly, even if omitted below, the contents described above with reference to FIG. 1 may be applied to examples to be described later with reference to FIGS. 2 to 163 .

As an example, with reference to FIGS. 2 to 83 , when the users of the devices 110 are the same and the devices 110 perform a document job, the server 100 stores job history information in the user's calendar. An example of interworking with .

As another example, with reference to FIGS. 84 to 86 , when users of the devices 110 are different and the devices 110 perform a document job, the server 100 stores job history information in the user's calendar. An example of interworking with .

As another example, an example in which the server 100 links job history information to a user's calendar when the devices 110 jointly author a document will be described with reference to FIGS. 87 to 98 .

As another example, referring to FIGS. 99 to 100 , when at least one of the plurality of devices 110 corresponds to the server 100 and the devices 110 perform a document operation, the server 100 ), an example in which the device performing the function links job history information to the user's calendar will be described.

As another example, referring to FIGS. 101 to 146 , when the users of the devices 110 are the same, and the server 100 performs a document operation based on the request of the devices 110 , the server ( 100) will describe an example of linking job history information to a user's calendar.

As another example, with reference to FIGS. 147 to 149 , when the users of the devices 110 are different, and the server 100 performs a document task based on the request of the devices 110, the server ( 100) will describe an example of linking job history information to a user's calendar.

As another example, with reference to FIGS. 150 to 161 , when the server 100 authores a document based on a request from the devices 110 , the server 100 links the job history information to the user's calendar An example will be described.

As another example, with reference to FIGS. 162 to 163 , at least one of the plurality of devices 110 corresponds to the server 100 , and the function of the server 100 is performed based on a request from the devices 110 . An example in which the device performing the function of the server 100 links work history information to the user's calendar when the performing device performs a document task will be described.

FIG. 2 is a diagram for explaining an example in which a server links work history information to a user's calendar when the devices have the same user and the devices perform a document job, according to some embodiments.

Referring to FIG. 2 , a system 1 includes a server 100 and devices 110 . Here, the devices 110 all refer to devices of the first user 120 .

At least one of the devices 110 performs a document job, and transmits the job history information 130 of the document to the server 100 . For example, the first device 111 performs a document job, and transmits the job history information 130 of the document to the server 100 . In the same manner, the second device 112 to the N-th device 114 performs a document job, and transmits the job history information 130 of the document to the server 100 .

The server 100 links the job history information 130 transmitted from the devices 110 to the user's calendar. Then, the server 100 transmits the information 140 to be displayed on the calendar to the devices 110 . Here, the information 140 to be displayed on the calendar means information to be displayed on the output calendar when the calendar is output on the screen of the device. For example, the information 140 to be displayed on the calendar may include job history information to be output on the screen of the device when an indicator to be displayed on the calendar or an indicator displayed on the calendar is selected.

In this case, the server 100 may transmit the information 140 to be displayed on the calendar only to a device that has requested transmission of the information 140 to be displayed on the calendar among the devices 110 . For example, the first device 111 executes a program for outputting a calendar and authenticates that the first user is the first user based on the user account input through the user input unit 16510, thereby providing the server 100 with the It is possible to request transmission of the information 140 to be displayed on the calendar.

Meanwhile, even if there is no request from the first device 111 , the server 100 may automatically transmit (eg, push) the information 140 to be displayed on the calendar to the first device 111 . . For example, if there is a history in which the first device 111 previously requested transmission of the information 140 to be displayed in the calendar of the first user, the server 100 may later request from the first device 111 . Even if there is no information, the information 140 to be displayed on the calendar of the first user may be automatically transmitted.

Hereinafter, an example in which the server 100 links job history information to a user's calendar will be described with reference to FIG. 3 .

3 is a flowchart illustrating an example in which a server links job history information to a user's calendar, according to some embodiments.

In S301, the server 100 receives the work history information of the document worked by the user from at least one device of the user. In other words, at least one device of the same user performs a document job and transmits job history information to the server 100 . In this case, as described above with reference to FIG. 1 , that the device may transmit only a part of the job history information to the server 100 .

In S302, the server 100 links the received job history information to the user's calendar by using the time information included in the received job history information. Here, the time information means information indicating the time the device worked on the document. For example, assuming that the first device 111 of the first user 120 creates a document called 'abc.doc' at 12:28:04 pm on May 12, 2014, the server 100 is the first user ( 120) generates an indicator to be displayed on 2014.05.12 in the calendar, and when the indicator displayed on 2014.05.12 is selected, job history information to be output on the screen of the first device 111 of the first user 120 can be determined. there is. In this case, as described above with reference to FIG. 1 , that the server 100 may link only a part of the job history information received from the device to the user's calendar.

Hereinafter, with reference to FIG. 4 , when the first device 111 of the first user 120 and the second device 112 of the first user 120 work on a document, the server 100 is the first user An example of linking job history information to the calendar of

4 is a flowchart illustrating an example in which a server links job history information to a calendar of a first user when a first device and a second device perform a document job, according to some embodiments.

4 shows that the first device 111 and the second device 112 work on a document for convenience of explanation, but the present invention is not limited thereto. In other words, there is no limit to the number of devices working on documents. If it is assumed that there is only one device for working with a document, all operations of the second device 112 to be described below may be performed by the first device 111 . In addition, assuming that the number of devices for working with a document is N (N is a plurality of 3 or more), the operation of the second device 112 to be described below is performed in at least one of the third device 113 to the Nth device. can be

In S410, the first device 111 works on the document. For example, the first device 111 may execute a program used for working with a document and work with the document using the program. For example, the program used for document work may be an MS OFFICE WORD program for Windows operating system (OS) installed in the first device 111 or a PAGE program of MAC OS.

If it is assumed that the document that the first device 111 works with is 'abc.doc' and the program used to create, view, or edit 'abc.doc' is the first program, the first device 111 is The first program may be executed, and 'abc.doc' may be created, viewed, or edited.

In S411 , the first device 111 transmits the job history information of the document to the server 100 . In this case, it is assumed that the user of the first device 111 is logged in to the server 100 . For example, the first device 111 may transmit work history information of the document to the server 100 when the execution of a program used for document work is terminated or the document is stored. For example, the first device 111 may transmit the job history information of 'abc.doc' to the server 100 when storing 'abc.doc' or ending execution of the first program.

As an example, when the user of the first device 111 logs in to the server 100 , the first device 111 may transmit job history information of the document to the server 100 . For example, a method for the user of the first device 111 to log in to the server 100 may use various methods including a method of inputting an ID/password.

As another example, when the user of the first device 111 logs in to the server 100 and a separate program for transmitting the job history information of the document to the server 100 is executed, the first device 111 is the document job history information of may be transmitted to the server 100 . For example, when the user of the first device 111 logs in to the server 100 , a separate window asking whether to execute the transmission program may be displayed on the screen of the first device 111 . In this case, when the user of the first device 111 requests transmission of the job history information through the output window, the first device 111 may transmit the job history information of the document to the server 100 .

As another example, when the function of the first device 111 to work the document and to transmit the work history information of the document to the server 100 is selected, the first device 111 transmits the work history information of the document to the server ( 100) can be transmitted. For example, when the user of the first device 111 creates or edits a document and selects the save button of the document, a separate window asking whether to transmit the job history information is output on the screen of the first device 111 can be In this case, when the user of the first device 111 requests transmission of the job history information through the output window, the first device 111 may transmit the job history information of the document to the server 100 .

As another example, the type of document to which the job history information is to be transmitted to the server 100 may be pre-registered. For example, the user of the first device 111 may register in advance the type of document to which the job history information is to be transmitted to the server 100 . The user of the first device 111 may register the extension (eg, “.doc”, “.xls”, “.txt”, “.ppt”, etc.) of the document in the server 100, 's executable program (eg, MS Word, MS Excel, MS PowerPoint, etc.) may be registered. Thereafter, when the first device 111 works on a document of a type previously registered in the server 100 , the first device 111 may automatically transmit work history information of the document to the server 100 .

Meanwhile, the type of document to which the job history information is to be transmitted to the server 100 may be initially set. Here, the type of the document may be set in such a way that the extension of the document or the execution program of the document is designated. In addition, the user of the first device 111 may edit the type of document set in the server 100 .

In S412 , the second device 112 works on the document. For example, the first device 111 may execute a program used for working with a document and work with the document using the program. If it is assumed that the document to be worked by the second device 112 is 'abcd.xls' and the program used to create, view, or edit 'abcd.xls' is the second program, the second device 112 is Execute the second program and create, view, or edit 'abcd.xls'.

In S413 , the second device 112 transmits the job history information of the document to the server 100 . For example, the second device 112 may transmit the work history information of the document to the server 100 when the execution of the program used for the document work is finished or the document is stored. For example, the second device 112 may transmit the job history information of 'abcd.xls' to the server 100 at the time of storing 'abcd.xls' or ending execution of the second program.

In S415 , the server 100 links the job history information to the user's calendar by using time information included in the job history information received from the first device and the second device. For example, the first device 111 stores 'abc.doc' on 2014.05.18 at 08:01:42 am, and the second device 112 stores 'abcd.xls' on 2014.05.20 at 14:29 pm. Assuming that it is stored at :00, the server 100 may generate a first indicator to be displayed in a field corresponding to 2014.05.18 in the calendar, and generate a second indicator to be displayed in a field corresponding to 2014.05.20. .

In S416 , the first device 111 requests the server 100 to transmit information to be displayed on the calendar. For example, the first device 111 may request the server 100 to transmit job history information to be output on the screen of the device when an indicator to be displayed on the calendar or an indicator displayed on the calendar is selected. For example, the first device 111 may request transmission of the work history information to be output on the screen of the device when the first indicator, the second indicator, and the first indicator and the second indicator are selected.

In S417 , the server 100 transmits information to be displayed on the calendar to the first device 111 .

In S418, the first device 111 outputs the calendar on the screen. For example, the first device 111 may output a calendar in which the first indicator and the second indicator transmitted from the server 100 are displayed on the screen.

In S419 , the second device 112 requests the server 100 to transmit information to be displayed on the calendar. For example, the second device 112 may request the server 100 to transmit job history information to be output on the screen of the device when an indicator to be displayed on the calendar or an indicator displayed on the calendar is selected. For example, the second device 112 may request transmission of the work history information to be output on the screen of the device when the first indicator, the second indicator, and the first indicator and the second indicator are selected.

In S420 , the server 100 transmits information to be displayed on the calendar to the second device 112 .

In S421, the second device 112 outputs the calendar on the screen. For example, the first device 111 may output a calendar in which the first indicator and the second indicator transmitted from the server 100 are displayed on the screen.

Hereinafter, an example in which the server 100 links job history information to a user's calendar when the first device 111 generates a document will be described with reference to FIGS. 5 to 26B .

5 is a flowchart illustrating an example in which a server links job history information to a user's calendar when a first device generates a document, according to some embodiments.

5 shows that the first device 111 generates a document and the second device 112 outputs a calendar on the screen for convenience of explanation, but the present invention is not limited thereto. For example, the first device 111 may generate a document, and the first device 111 and the second device 112 may output a calendar on the screen.

Also, there is no limit to the number of devices. If it is assumed that the number of devices executing the document is N (N is a plurality of 3 or more), the operation of the first device 111 or the operation of the second device 112, which will be described below, is the operation of the third device 113 . to at least one of the Nth devices.

In S510, the first device 111 executes a program for generating a document. Here, the program for generating a document includes a program for generating a text document or a program for generating a multimedia document. For example, a program that creates a document may be a program included in MS-OFFICE.

In S511, the first device 111 generates a document and stores the generated document.

In S512 , the first device 111 transmits the job history information of the document to the server 100 . In this case, it is assumed that the user of the first device 111 is logged in to the server 100 . In addition, examples in which the first device 111 transmits job history information of a document to the server 100 are the same as described above with reference to step S411 of FIG. 4 .

For example, the first device 111 may transmit job history information of the document to the server 100 at the time the document is stored. The work history information of the document means information generated as the first device 111 creates and stores the document. For example, the job history information may include the title of the document on which the job was performed, the type of the document, the time the document job was performed, the name of the device performing the document job, the user of the device, the program used for the document job, the size of the document, It can include the type of work.

Hereinafter, an example in which the first device 111 executes a program to generate and store a document and transmits job history information of the document to the server 100 will be described with reference to FIGS. 6 to 11 .

6 to 7 are diagrams for explaining an example in which the first device transmits job history information of the document to the server when the document is a text document according to some embodiments.

Referring to FIG. 6A , the first device 111 executes a first program to generate a text document. For example, the first device 111 may select the indicator 610 indicating the first program based on a user input received through the user input unit 16510 . In addition, the first device 111 may execute a program corresponding to the selected indicator 610 .

Referring to FIG. 6B , the first device 111 generates a text document. For example, the first device 111 may write the content 620 included in the text document based on the user input received through the user input unit 16510 .

Referring to FIG. 7 , the first device 111 stores a text document. For example, the first device 111 may select the indicator 710 indicating 'save' of the text document based on the user input received through the user input unit 16510 . In addition, the first device 111 may store a text document.

After storing the text document, the first device 111 transmits job history information of the text document to the server 100 . For example, it is said that the first device 111 stored a document named 'abc.doc' having a size of 54 KB (kilobyte) using the first program at 12:28:04 pm on May 12, 2014. Assume that the first device 111 sends the server 100 to at least one of 'abc.doc, text, first program, first device, May 12, 2014 12:28:04 pm, 54 KB'. can be transmitted.

On the other hand, when a high degree of security is required for the stored document, the first device 111 may additionally perform encryption on the job history information and transmit it to the server 100 .

As an example, if the user selects the 'security' option when storing the document, the first device 111 may additionally perform encryption on the job history information of the document and transmit it to the server 100 .

As another example, a user may create a specific folder in the first device 111 , and a document included in the created folder may be set to have a strong degree of security. When the job history information of the document included in the folder is generated, the first device 111 may additionally perform encryption on the job history information and transmit it to the server 100 .

After the user logs in to the server 100 , the user can access the job history information transmitted to the server 100 . However, separate information may be additionally required to access the encrypted work history information. For example, even after the user logs in to the server 100 by inputting a password/ID, it may be set to require a separate password input in order to access the encrypted work history information.

8 to 9 are diagrams for explaining another example in which the first device transmits job history information of the document to the server when the document is a text document according to some embodiments.

Referring to FIG. 8A , the first device 111 executes a second program to generate a text document. In this case, the second program executed by the first device 111 may be different from the first program described above with reference to FIG. 6A . In other words, programs used by the first device 111 to generate a text document may vary, and a text document type generated by the first device 111 using each program may also vary.

The first device 111 may select the indicator 810 indicating the second program based on the user input received through the user input unit 16510 . In addition, the first device 111 may execute the second program.

Referring to FIG. 8B , the first device 111 generates a text document based on the executed program. For example, the first device 111 may write the content 820 included in the text document based on the user input received through the user input unit 16510 .

Referring to FIG. 9 , the first device 111 stores a text document. For example, the first device 111 may select the indicator 910 indicating 'save' of the text document based on the user input received through the user input unit 16510 . In addition, the first device 111 may store a text document.

After storing the text document, the first device 111 transmits job history information of the text document to the server 100 . For example, it is said that the first device 111 created a document named 'abcd.xls' having a size of 47 KB (kilobyte) using the second program at 02:25:56 pm on April 22, 2014. Assume that the first device 111 sends the server 100 to at least one of 'abcd.xls, text, second program, first device, 02:25:56 pm on April 22, 2014, 47 KB'. can be transmitted.

Meanwhile, as described above with reference to FIG. 7 that encryption may be additionally performed on the job history information of a document requiring a high degree of security and transmitted to the server 100 .

10 to 11 are diagrams for explaining another example in which the first device transmits job history information of the document to the server when the document is a text document according to some embodiments.

Referring to FIG. 10A , the first device 111 executes a third program to generate a text document. In other words, text generated by the first device 111 may vary, and a program used by the first device 111 to generate a text document may also vary according to the type of the text document.

The first device 111 may select the indicator 1010 indicating the third program based on the user input received through the user input unit 16510 . In addition, the first device 111 may execute the third program. Here, an example in which the first device 111 selects the indicator 1010 and executes a program corresponding to the selected indicator 1010 is as described above with reference to FIG. 6A .

Referring to FIG. 10B , the first device 111 generates a text document based on a third program. For example, the first device 111 may write the content 1020 included in the text document based on the user input received through the user input unit 16510 .

Referring to FIG. 11 , the first device 111 stores a text document. For example, the first device 111 may select the indicator 1110 indicating 'save' of the text document based on the user input received through the user input unit 16510 . In addition, the first device 111 may store a text document.

After storing the text document, the first device 111 transmits execution history information of the text document to the server 100 . For example, it is said that the first device 111 created a document named 'kkk.ppt' having a size of 2387 KB (kilobyte) using a third program at 02:21:04 pm on January 1, 2013. Assume that the first device 111 sends the server 100 to at least one of 'kkk.ppt, image, third program, first device, 02:21:04 pm on January 1, 2013, 2387 KB'. can be transmitted.

Meanwhile, as described above with reference to FIG. 7 that encryption may be additionally performed on the job history information of a document requiring a high degree of security and transmitted to the server 100 .

Referring back to FIG. 5 , in S513 , the server 100 links the job history information to the calendar using time information included in the job history information transmitted from the first device.

Hereinafter, an example in which the server 100 links job history information of a document to a calendar will be described with reference to FIGS. 12 to 15 .

12 is a flowchart illustrating an example in which a server links job history information of a document to a calendar, according to some embodiments.

In S1210 , the server 100 acquires information about the creation time of a document included in the job history information received from the first device 111 . For example, according to the example described above with reference to FIG. 7 , the server 100 acquires '2014.05.12, 12:28:04 PM' from the job history information received from the first device 111 .

Hereinafter, an example of the job history information obtained by the server 100 will be described with reference to FIGS. 13 to 14 .

13 to 14 are diagrams illustrating an example of job history information of a document according to some embodiments.

Referring to FIG. 13 , an example of job history information 1310 of a document is illustrated. For example, in the job history information 1310 of the document, the name of the document 1311 , the type of the document 1312 , the name of the job program 1313 , the name of the working device 1314 , the user of the device 1315 , Although illustrated as including a job type 1316 , a job date and time 1317 , and a file size 1318 , it is not limited thereto. In other words, the work history information 1310 of the document may correspond without limitation as long as it is information that can be generated by performing the work of the document.

For example, the server 100 arranges the job history information 1310 received from the first device 111 based on the name 1311 of the document, and stores the arranged job history information 1310 into the database 16430. can be stored in

Referring to FIG. 14 , another example of job history information 1410 of a document is illustrated. The job history information 1310 shown in FIG. 13 and the job history information 1410 shown in FIG. 14 include the same information. In other words, in the job history information 1410 of the document shown in FIG. 14 , the name of the document 1414 , the type of the document 1412 , the name of the job program 1413 , the name of the working device 1411 , and the user of the device 1416 , job type 1415 , job date and time 1417 , and file size 1418 . For example, the server 100 arranges the work history information 1410 received from the first device 111 based on the name of the work device 1411, and stores the arranged work history information 1410 in the database ( 16430) can be stored.

Referring back to FIG. 12 , in S1220 , the server 100 links the job history information to the user's calendar based on the document creation time information. Hereinafter, an example in which the server 100 links job history information to a user's calendar will be described with reference to FIG. 15 .

15 is a flowchart illustrating an example in which a server links job history information to a user's calendar, according to some embodiments.

In S1510, the server 100 acquires the user's calendar. Here, the user's calendar means a frame to which work history information of a document is linked. For example, the server 100 may read the user's calendar stored by matching the user's account from the database 16430 , or may receive the user's calendar from at least one of the devices 110 . For example, the user's calendar may include a calendar displayed in units of days, a calendar displayed in units of weeks, a calendar displayed in units of months, or a calendar displayed in units of years.

In S1520, the server 100 generates an indicator to be displayed on the calendar based on any one of the name of the document included in the work history information, the program used to generate the document, and the name of the device that generated the document. In other words, the server 100 determines any one of the name of the document, the program used to generate the document, and the name of the device that generated the document as the item indicated by the indicator, and generates the indicator based on the determined item.

In S1530, the server 100 determines job history information to be displayed on the calendar based on the generated indicator.

In S1540, the server 100 displays the indicator in the area corresponding to the date or time indicating the time when the document is created in the calendar. Here, the area corresponding to the date or time means a date field or a time field in the calendar.

Referring back to FIG. 5 , in S514 , the second device 112 requests the server 100 to transmit information to be displayed on the calendar. For example, the second device 112 may request the server 100 to transmit information to be displayed on the calendar after executing the calendar output program installed in the second device 112 and authenticating the user. .

In S515 , the server 100 transmits information to be displayed on the calendar to the second device 112 .

In FIG. 5 , when the second device 112 requests the server 100 to transmit the information to be displayed on the calendar in S514, the server 100 transmits the information to be displayed on the calendar in S515. doesn't happen For example, even if there is no transmission request from the second device 112 , the server 100 may transmit (eg, push) information to be displayed on the calendar to the second device 112 .

In S516, the second device 112 outputs the calendar on the screen.

Hereinafter, an example of a calendar output on a screen of a device will be described with reference to FIGS. 16 to 25 . For convenience of explanation, examples of a daily calendar, a monthly calendar, and a yearly calendar are illustrated in FIGS. 16 to 25 , but the present invention is not limited thereto. In other words, various examples such as a calendar displayed in units of weeks, a calendar displayed in units of three days, and a calendar displayed in units of time may exist in the user's calendar.

16 is a diagram illustrating an example of a daily calendar displayed on a screen of a device according to some embodiments.

Referring to FIG. 16 , a daily calendar 1620 is output on the screen of the device 1610 . The calendar 1620 may include an area 1630 indicating dates and an indicator 1640 through which a user can designate a desired date. Also, the calendar 1620 may include an indicator 1650 capable of displaying a calendar corresponding to the date of 'today'. In addition to the above-described indicators, the calendar 1620 may be included without limitation as long as it is an indicator that allows the user to control the display type of the calendar.

An indicator 1660 indicating the name of a document may be displayed on the calendar 1620 . For example, assuming that the first device 111 generates a document named 'abc.doc' on May 12, 2014, the calendar 1620 indicates 'abc.doc' in an area corresponding to May 12, 2014. An indicator 1660 may be displayed.

The device 1610 may select the indicator 1660 indicating 'abc.doc' according to the user input received through the user input unit 16510 . When the indicator 1660 indicating 'abc.doc' is selected, the device 1610 may output the job history information 1670 of the document on the screen. For example, it is said that the first device 111 stored a document named 'abc.doc' having a size of 54 KB (kilobyte) using the first program at 12:28:04 pm on May 12, 2014. Assume that 'abc.doc, text, first program, first device, May 12, 2014 12:28:04 pm, 54 KB' may be output to the work history information 1670 . Meanwhile, the device 1610 may output the job history information 1670 of the document on the screen as a separate pop-up window.

Also, an indicator 1680 capable of outputting a document to the screen of the device 1610 may be displayed in the job history information 1670 of the document. For example, when an indicator 1680 capable of outputting a document according to a user input received through the user input unit 16510 is selected, the device 1610 displays a pop-up window separate from the calendar 1620 to the first device ( 111) can be printed on the screen.

17 is a diagram illustrating another example of a daily calendar displayed on a screen of a device according to some embodiments.

Referring to FIG. 17 , a daily calendar 1720 is output on the screen of the device 1710 . The calendar 1720 shown in FIG. 17 has the same frame as the calendar 1620 shown in FIG. 16 . Accordingly, the contents described above with reference to FIG. 16 with respect to indicators that may be displayed on the calendar 1720 may be equally applied to FIG. 17 .

An indicator 1730 indicating a program used to work on a document may be displayed on the calendar 1720 . For example, if it is assumed that the first device 1710 generates a document using the first program on May 12, 2014, an indicator indicating the 'first program' ( 1730) may be displayed.

The device 1710 may select the indicator 1730 indicating the 'first program' according to the user input received through the user input unit 16510 . When the indicator 1730 indicating the 'first program' is selected, the device 1710 may output the job history information 1740 of the document on the screen. For example, it is said that the first device 111 stored a document named 'abc.doc' having a size of 54 KB (kilobyte) using the first program at 12:28:04 pm on May 12, 2014. Assume that 'abc.doc, text, first program, first device, May 12, 2014 12:28:04 pm, 54 KB' may be output to the work history information 1740 . Meanwhile, the device 1710 may output the job history information 1740 of the document on the screen as a separate pop-up window.

Also, an indicator 1750 capable of outputting a document to the screen of the device 1710 may be displayed in the job history information 1740 of the document. For example, when an indicator 1750 capable of outputting a document according to a user input received through the user input unit 16510 is selected, the device 1710 displays a pop-up window separate from the calendar 1720 to the first device ( 111) can be printed on the screen.

18 is a diagram illustrating another example of a daily calendar displayed on a screen of a device according to some embodiments.

Referring to FIG. 18 , a daily calendar 1820 is output on the screen of the device 1810 . The calendar 1820 shown in FIG. 18 has the same frame as the calendar 1620 shown in FIG. 16 . Accordingly, the contents described above with reference to FIG. 16 with respect to indicators that may be displayed on the calendar 1820 may be equally applied to FIG. 18 .

An indicator 1830 indicating the name of the device may be displayed on the calendar 1820 . For example, assuming that the first device 111 creates a document on May 12, 2014, an indicator 1840 indicating the 'first device' may be displayed in an area corresponding to May 12, 2014 of the calendar 1820. there is.

The device 1810 may select the indicator 1840 indicating the 'first device' according to the user input received through the user input unit 16510 . When the indicator 1840 indicating the 'first device' is selected, the device 1810 may output the job history information 1840 of the document on the screen. For example, it is said that the first device 111 stored a document named 'abc.doc' having a size of 54 KB (kilobyte) using the first program at 12:28:04 pm on May 12, 2014. It is assumed that 'abc.doc, text, first program, first device, May 12, 2014 12:28:04 pm, 54 KB' may be output to the work history information 1840 . Meanwhile, the device 1810 may output the job history information 1840 of the document to the screen as a separate pop-up window.

Also, an indicator 1850 capable of outputting a document to the screen of the device 1810 may be displayed in the job history information 1840 of the document. For example, when an indicator 1850 capable of outputting a document according to a user input received through the user input unit 16510 is selected, the device 1810 displays a pop-up window separate from the calendar 1820 to the first device ( 111) can be printed on the screen.

19 is a diagram illustrating an example of a monthly calendar displayed on a screen of a device according to some embodiments.

Referring to FIG. 19 , a monthly calendar 1920 is output on the screen of the device 1910 . The calendar 1920 may include an area 1930 indicating each of the days included in a month and an indicator 1940 through which a user can designate a desired month. Also, the calendar 1920 may include an indicator 1950 capable of displaying a monthly calendar including the date of 'today'. In addition to the above-described indicators, the calendar 1920 may include without limitation any indicator through which the user can control the display type.

An indicator 1960 indicating the name of a document may be displayed on the calendar 1920 . For example, assuming that the first device 111 generates a document named 'abc.doc' on May 12, 2014, the calendar 1960 indicates 'abc.doc' in the area corresponding to May 12, 2014. An indicator 1960 may be displayed.

The device 1910 may select the indicator 1960 indicating 'abc.doc' according to the user input received through the user input unit 16510 . When the indicator 1960 indicating 'abc.doc' is selected, the device 1910 may output work history information 1970 of the document on the screen.

For example, it is said that the first device 111 stored a document named 'abc.doc' having a size of 54 KB (kilobyte) using the first program at 12:28:04 pm on May 12, 2014. Assume that 'abc.doc, text, first program, first device, May 12, 2014 12:28:04 pm, 54 KB' may be output to the work history information 1970 . Meanwhile, the device 1910 may output the job history information 1970 of the document on the screen as a separate pop-up window.

Also, an indicator 1980 capable of outputting a document to the screen of the device 1910 may be displayed in the work history information 1970 of the document. For example, when an indicator 1980 capable of outputting a document according to a user input received through the user input unit 16510 is selected, the device 1910 displays a pop-up window separate from the calendar 1920 to the first device ( 111) can be printed on the screen.

20 is a diagram illustrating another example of a monthly calendar displayed on a screen of a device according to some embodiments.

Referring to FIG. 20 , a monthly calendar 2020 is output on the screen of the device 2010 . The calendar 2020 shown in FIG. 20 has the same frame as the calendar 1920 shown in FIG. 19 . Accordingly, the contents described above with reference to FIG. 19 with respect to indicators that may be displayed on the calendar 2020 may be equally applied to FIG. 20 .

An indicator 2030 indicating a program used to execute a document may be displayed on the calendar 2020. For example, assuming that the first device 2010 generates a document by using the first program on May 12, 2014, an indicator indicating the 'first program' in the area corresponding to May 12, 2014 of the calendar 2020 ( 2030) may be displayed.

The device 2010 may select the indicator 2030 indicating the 'first program' according to the user input received through the user input unit 16510 . When the indicator 2030 indicating the 'first program' is selected, the device 2010 may output the job history information 2040 of the document on the screen. For example, it is said that the first device 111 stored a document named 'abc.doc' having a size of 54 KB (kilobyte) using the first program at 12:28:04 pm on May 12, 2014. Assume that 'abc.doc, text, first program, first device, May 12, 2014 12:28:04 pm, 54 KB' may be output to the work history information 2040 . Meanwhile, the device 2010 may output the job history information 2040 of the document to the screen as a separate pop-up window.

Also, an indicator 2050 capable of outputting a document to the screen of the device 2010 may be displayed in the work history information 2040 of the document. For example, when an indicator 2050 capable of outputting a document according to a user input received through the user input unit 16510 is selected, the device 2010 displays a pop-up window separate from the calendar 2020 to the first device ( 111) can be printed on the screen.

21 is a diagram illustrating another example of a monthly calendar displayed on a screen of a device according to some embodiments.

Referring to FIG. 21 , a monthly calendar 2120 is output on the screen of the device 2110 . The calendar 2120 illustrated in FIG. 21 has the same frame as the calendar 1910 illustrated in FIG. 19 . Accordingly, the contents described above with reference to FIG. 19 with respect to indicators that may be displayed on the calendar 2120 may be equally applied to FIG. 21 .

An indicator 2130 indicating a device name may be displayed on the calendar 2120 . For example, assuming that the first device 111 generates a document on May 12, 2014, an indicator 2130 indicating the 'first device' may be displayed in an area corresponding to May 12, 2014 of the calendar 2120. there is.

The device 2110 may select the indicator 2130 indicating the 'first device' according to the user input received through the user input unit 16510 . When the indicator 2130 indicating the 'first device' is selected, the device 2110 may output the job history information 2140 of the document on the screen. For example, it is said that the first device 111 stored a document named 'abc.doc' having a size of 54 KB (kilobyte) using the first program at 12:28:04 pm on May 12, 2014. Assume that 'abc.doc, text, first program, first device, May 12, 2014 12:28:04 pm, 54 KB' may be output to the work history information 2140 . Meanwhile, the device 2110 may output the job history information 2140 of the document on the screen as a separate pop-up window.

Also, an indicator 2150 capable of outputting a document to the screen of the device 2110 may be displayed in the work history information 2140 of the document. For example, when the indicator 2150 capable of outputting a document according to a user input received through the user input unit 16510 is selected, the device 2110 displays a pop-up window separate from the calendar 2120 to the first device ( 111) can be printed on the screen.

22 to 25 are diagrams illustrating an example of an annual calendar displayed on a screen of a device according to some embodiments.

Referring to FIG. 22 , an annual calendar 2220 is output on the screen of the device 2210 . The calendar 2220 may include an area 2230 in which months included in a year are displayed and an indicator 2240 through which a user can designate a desired year. Also, the calendar 2220 may include an indicator 2250 capable of displaying a calendar of a year including the date of 'today'. In addition to the above-described indicators, the calendar 2220 may include without limitation any indicator through which the user can control the display type.

Indicators 2260 , 2261 , and 2262 indicating document names may be displayed on the calendar 2220 . For example, assuming that the first device 111 generates a document named 'xyz.doc' on February 12, 2014, an indicator ( 2262) may be displayed.

In addition, assuming that the first device 111 generates a document named 'abcd.xls' on April 22, 2014, an indicator 2261 indicating 'abcd.xls' in an area corresponding to 2014.04 in the calendar 2220 may be displayed. Also, assuming that the first device 111 generates a document named 'abc.doc' on May 12, 2014, an indicator 2260 indicating 'abc.doc' in an area corresponding to May 2014 in the calendar 2220 . may be displayed. In the foregoing, it has been described that all of 'xyz.doc', 'abcd.xls', and 'abc.doc' are generated by the first device 111, but different devices may generate respective documents.

The device 2210 may select the indicators 2260 , 2261 , and 2262 indicating the name of the document according to the user input received through the user input unit 16510 . When the indicators 2260 , 2261 , and 2262 indicating the name of the document are selected, the device 2210 may output the job history information 2270 of the document on the screen.

For example, it is said that the first device 111 stored a document named 'abc.doc' having a size of 54 KB (kilobyte) using the first program at 12:28:04 pm on May 12, 2014. Assume At this time, when the indicator 2260 indicating 'abc.doc' is selected, the job history information 2270 includes 'abc.doc, text, first program, first device, May 12, 2014 12:28 pm: 04, 54 KB' may be output. Meanwhile, the device 2210 may output the job history information 2270 of the document on the screen as a separate pop-up window.

Also, an indicator 2280 capable of outputting a document to the screen of the device 2210 may be displayed in the job history information 2270 of the document. For example, when an indicator 2280 capable of outputting a document according to a user input received through the user input unit 16510 is selected, the device 2210 displays a pop-up window separate from the calendar 2220 to the first device ( 111) can be printed on the screen.

Referring to FIG. 23 , an annual calendar 2320 is output on the screen of the device 2310 . In addition, an indicator 2330 indicating a program used to work on a document is displayed on the calendar 2320 . As described above with reference to FIGS. 17 and 20 , when the indicator 2330 indicating a program used for working on a document is selected, the device 2310 may output job history information 2340 of the document on the screen. . Also, when the indicator 2350 capable of outputting a document is selected on the screen on which the work history information 2340 of the document is displayed, the device 2310 may output the document generated by the first device 111 to the screen. .

Referring to FIG. 24 , an annual calendar 2420 is output on the screen of the device 2410 . In addition, an indicator 2430 indicating a device is displayed on the calendar 2420 . As described above with reference to FIGS. 18 and 21 , when the indicator 2430 indicating the device is selected, the device 2410 may output the execution history information 2440 of the document on the screen. Also, when the indicator 2450 capable of outputting a document is selected on the screen on which the execution history information 2440 of the document is displayed, the device 2410 may output the document generated by the first device 111 to the screen. .

Referring to FIG. 25 , an annual calendar 2520 is output on the screen of the device 2510 . Although the annual calendar shown in FIGS. 22 to 24 includes an area in which months included in a year are displayed, the annual calendar 2520 shown in FIG. 25 includes an area 2530 in which days included in a year are displayed. This is included. In other words, the device 2510 may variously change the format of the annual calendar and output it on the screen.

Indicators 2531 , 2532 , and 2533 may be displayed on the calendar 2520 on the date the document was performed. For example, assuming that the first device 111 generates a document named 'xyz.doc' on February 12, 2014, the calendar 2520 indicates 'xyz.doc' in the area corresponding to February 12, 2014. An indicator 2531 may be displayed. Also, assuming that the first device 111 generates a document named 'abcd.xls' on April 22, 2014, an indicator ( 2532) may be displayed. Also, assuming that the first device 111 generates a document named 'abc.doc' on May 12, 2014, an indicator indicating 'abc.doc' in an area corresponding to May 12, 2014 in the calendar 2520 2533) may be displayed. Although it has been described above that all of 'xyz.doc', 'abcd.xls', and 'abc.doc' are generated by the first device 111, different devices may generate documents.

As described above with reference to FIGS. 16 and 24 , when the indicator 2533 displayed on the calendar 2520 is selected, the device 2510 may output the job history information 2540 of the document on the screen. In addition, when the indicator 2550 capable of outputting a document is selected on the screen on which the work history information 2540 of the document is displayed, the device 2510 may output the document generated by the first device 111 to the screen. .

Hereinafter, with reference to FIGS. 26A to 47 , when the first device 111 creates a document and the second device 112 reads the document, the server links the job history information to the user's calendar An example is explained.

26A to 26B are flowcharts illustrating an example in which a server links job history information to a user's calendar when a first device creates a document and a second device reads the document, according to some embodiments.

26A to 26B illustrate that the first device 111 generates a document and the second device 112 reads the document for convenience of explanation, but the present invention is not limited thereto. For example, the first device 111 may generate a document, and the first device 111 may read the document.

Also, there is no limit to the number of devices. If it is assumed that the number of devices executing the document is N (N is a plurality of 3 or more), the operation of the first device 111 or the operation of the second device 112, which will be described below, is the operation of the third device 113 . to at least one of the Nth devices.

S2610 to S2616 of FIG. 26A correspond to S510 to S516 of FIG. 5 . Accordingly, even if omitted below, the contents described above with reference to FIGS. 5 to 25 may be applied to the contents to be described later with reference to S2610 to S2616 of FIG. 26A.

In S2610, the first device 111 executes a program for generating a document.

In S2611, the first device 111 generates a document and stores the generated document.

In S2612 , the first device 111 transmits the job history information of the document to the server 100 . For example, the first device 111 may transmit job history information of the document to the server 100 at the time the document is stored. In this case, it is assumed that the user of the first device 111 is logged in to the server 100 . In addition, examples in which the first device 111 transmits job history information of a document to the server 100 are the same as described above with reference to step S411 of FIG. 4 .

In S2613 , the server 100 links the job history information to the calendar using time information included in the job history information transmitted from the first device 111 .

In S2614, the second device 112 requests the server 100 to transmit information to be displayed on the calendar. For example, the second device 112 executes the calendar output program installed in the second device 112, authenticates the user using the input user account, and then transmits the information to be displayed on the calendar to the server 100 can request

In S2615 , the server 100 transmits information to be displayed on the calendar to the second device 112 .

In FIG. 26A, when the second device 112 requests the server 100 to transmit information to be displayed on the calendar in S2614, the server 100 transmits information to be displayed on the calendar in S2615. not limited For example, even if there is no transmission request from the second device 112 , information to be displayed on the calendar may be transmitted (eg, pushed) to the second device 112 .

In S2616, the second device 112 outputs the calendar on the screen.

In S2617 , the second device 112 requests the first device 111 to transmit the document. For example, when a predetermined indicator displayed on the calendar is selected according to a user input received by the second device 112 , the second device 112 may request the first device 111 to transmit a document. For example, the predetermined indicator may mean an indicator 1680 capable of outputting a document displayed on the calendar 1620 of FIG. 16 .

In S2618 , the first device 111 transmits the document to the second device 112 according to the request of the second device 112 .

As an example, the second device 112 may request the first device 111 to transmit the document and receive the document from the first device 111 . Alternatively, the second device 112 may request the server 100 to transmit the document and receive the document from the server 100 .

As another example, the second device 112 may receive an image representing a document from the first device 111 or the server 100 by a streaming method.

Hereinafter, an example in which the second device 112 requests the first device 111 to transmit a document and receives the document from the first device 111 will be described with reference to FIG. 27 .

27 is a diagram for describing an example in which a second device requests transmission of a document from a first device and receives a document, according to some embodiments.

Referring to FIG. 27 , a calendar 2710 output on the screen of the second device 112 is shown. Here, the calendar 2710 refers to a calendar output on the screen of the second device 112 according to S2616 of FIG. 26A .

The second device 112 receives a user input for selecting the indicator 2720 displayed on the calendar 2710 through the user input unit 16510 . The second device 112 outputs job history information 2730 of the document on the screen according to the received user input. In this case, an indicator 2740 capable of outputting a document to the screen of the second device 112 may be displayed on the screen on which the work history information 2730 of the document is displayed.

When the indicator 2740 is selected by the user, a preview screen of the document or an execution screen of the document may be output to the second device 112 . As an example, when the user briefly touches the indicator 2740 , a preview screen of the document may be output, and when the user touches the indicator 2740 for a long time, an execution screen of the document may be output. As another example, when the cursor displayed on the screen of the second device 112 is positioned on the indicator 2740, a preview screen of the document may be output, and when the indicator 2740 is clicked by the user, the execution screen of the document This can be output.

The second device 112 receives a user input (eg, a long touch or click) for selecting the indicator 2740 through the user input unit 16510 . The second device 112 requests ( 2750 ) to transmit the document to the first device 111 according to the received user input. Then, the first device 111 transmits ( 2760 ) the document to the second device 112 according to the request of the second device 112 .

Referring back to FIG. 26A , in S2619 , the second device 112 outputs the document transmitted from the first device 111 on the screen.

In S2620, the second device 112 ends the output of the document. Hereinafter, an example in which the second device 112 finishes outputting a document will be described with reference to FIGS. 28 to 30 .

28 to 30 are diagrams for explaining examples in which the second device terminates output of a document, according to some embodiments.

28 to 30 , a document received from the first device 111 is output 2810 on the screen of the second device 112 . The second device 112 receives a user input for terminating the output 2810 of the document through the user input unit 16510 . For example, the user input may be an input 2820 or 2910 for terminating a program that executes a document, or an input 3010 for closing a window for outputting a document while maintaining the execution of the program.

Referring to FIG. 28 , the second device 112 receives a user input for selecting an indicator 2820 displayed on the screen. Then, the second device 112 ends the program executing the document according to the received user input.

Referring to FIG. 29 , the second device 112 receives a user input for selecting an indicator 2910 displayed on the screen. Then, the second device 112 ends the program executing the document according to the received user input.

Referring to FIG. 30 , the second device 112 receives a user input for selecting an indicator 3010 displayed on the screen. Then, the second device 112 closes the window for outputting the document displayed on the screen according to the received user input.

Referring back to FIG. 26B , in S2621 , the second device 112 transmits the job history information of the document to the server 100 . For example, the second device 112 may transmit the job history information of the document to the server 100 at the time when the execution of the document is finished (ie, the time when the output of the document is finished). Hereinafter, an example in which the second device 112 transmits job history information of a document to the server 100 will be described with reference to FIG. 31 .

FIG. 31 is a diagram for describing an example in which a second device transmits job history information of a document to a server, according to some embodiments.

As described above with reference to FIGS. 28 to 30 , the second device 112 may end the output of the document by terminating a program executing the document or closing a window for outputting the document. When the second device 112 terminates the program or closes the window for outputting the document without adding or deleting the contents of the document, the second device 112 determines that the document has been read.

When the program executing the document is terminated or the window in which the document is output is closed, the second device 112 transmits the job history information of the document to the server 100 . In other words, the second device 112 transmits information generated by reading the document to the server 100 .

For example, the second device 112 executes a document named 'abc.doc' having a size of 54 KB (kilobyte) using the first program, and the second device 112 executes a document named 'abc.doc' on May 20, 2014 Assuming that the first program is terminated or the window in which the document is output is closed at 08:46:11 PM, the second device 112 tells the server 100 'abc.doc, text, first program, second The device may transmit at least one of '08:46:11 PM on May 20, 2014, 54 KB'.

Meanwhile, as described above with reference to FIG. 7 that encryption may be additionally performed on the job history information of a document requiring a high degree of security and transmitted to the server 100 .

Referring back to FIG. 26B , in S2622 , the server 100 links the job history information to the calendar using time information included in the job history information transmitted from the second device 112 . For example, the server 100 links the job history information received from the first device 111 to the calendar in S2613, and additionally links the job history information received from the second device 112 to the calendar in S2622 .

In S2623, the first device 111 requests the server 100 to transmit information to be displayed on the calendar. For example, the first device 111 may request the server 100 to transmit job history information to be output on the screen of the device when an indicator to be displayed on the calendar or an indicator displayed on the calendar is selected.

In S2624 , the server 100 transmits information to be displayed on the calendar to the first device 111 .

In S2625, the first device 111 outputs the calendar on the screen.

In FIG. 26B, when the first device 111 requests the server 100 to transmit information to be displayed on the calendar in S2623, the server 100 transmits information to be displayed on the calendar in S2624. , but is not limited thereto. For example, even if there is no transmission request from the first device 111 , the server 100 may transmit (eg, push) information to be displayed on the calendar to the first device 111 .

The contents to be described later with reference to S2626 to S2628 correspond to the contents described above with reference to S2623 to S2625. In other words, the second device 112 requests the server 100 to transmit information to be displayed on the calendar, receives information to be displayed on the calendar from the server 100 , and outputs the calendar on the screen. Accordingly, even if omitted below, the contents described above with reference to S2623 to S2625 may be applied to the contents to be described later with reference to S2626 to S2628.

In S2626, the second device 112 requests the server 100 to transmit information to be displayed on the calendar.

In S2627 , the server 100 transmits information to be displayed on the calendar to the second device 112 .

In S2628, the second device 112 outputs the calendar on the screen.

A specific example of the contents described above with reference to S2622 to S2628 of FIG. 26B will be described later with reference to FIGS. 34 to 47 .

Meanwhile, the second device 112 requests the first device to transmit the document in S2617 and receives the document from the first device 111 in S2618. However, the second device 112 may request the server 100 to transmit the document and receive the document from the server 100 . Hereinafter, an example in which the second device 112 receives a document from a server will be described with reference to FIGS. 32A to 33 .

32A to 32B are flowcharts illustrating another example in which a server links job history information to a user's calendar when a first device creates a document and a second device reads the document, according to some embodiments.

When the flowchart shown in FIGS. 26A to 26B is compared with the flowchart shown in FIGS. 32A to 32B , S3210 to S3211 in FIG. 32A are the same as S2610 to S2611 in FIG. 26A . In addition, S3220 to S3229 of FIGS. 32A to 32B are the same as S2619 to S2628 of FIGS. 26A to 26B . Accordingly, detailed descriptions of S3210 to S3211 and S3220 to S3229 of FIGS. 32A to 32B will be omitted below.

In S3212 , the first device 111 transmits the document and information about the execution of the document to the server 100 . In other words, the first device 111 transmits the document to the server 100 as well as the job history information generated according to the storage of the document. In this case, it is assumed that the user of the first device 111 is logged in to the server 100 . In addition, examples in which the first device 111 transmits job history information of a document to the server 100 are the same as described above with reference to step S411 of FIG. 4 .

In S3213 , the server 100 stores the document received from the first device 111 .

In S3214 , the server 100 links the job history information to the calendar using time information included in the job history information transmitted from the first device 111 .

In S3215 , the second device 112 requests the server 100 to transmit information to be displayed on the calendar. For example, the second device 112 executes a calendar output program installed in the second device 112 , authenticates the user using a user account, and then transmits information to be displayed on the calendar to the server 100 . can request

In S3216 , the server 100 transmits information to be displayed on the calendar to the second device 112 .

In S3217, the second device 112 outputs the calendar on the screen.

In S3218, the second device 112 requests the server 100 to transmit the document. For example, when an indicator requesting execution of a document displayed on the calendar is selected according to a user input of the second device 112 , the second device 112 may request the server 100 to transmit the document. For example, when a predetermined indicator displayed on the calendar is selected according to a user input received by the second device 112 , the second device 112 may request the server 100 to transmit the document. For example, the predetermined indicator may mean an indicator 1680 capable of outputting a document displayed on the calendar 1620 of FIG. 16 .

In S3219 , the server 100 transmits the document to the second device according to the request of the second device 112 .

Hereinafter, an example in which the second device 112 requests the server 100 to transmit a document and receives the document from the server 100 will be described with reference to FIG. 33 .

33 is a diagram for describing an example in which a second device requests a server to transmit a document and receives a document, according to some embodiments.

Referring to FIG. 33 , a calendar 3310 output on the screen of the second device 112 is illustrated. The second device 112 receives a user input for selecting the indicator 3320 displayed on the calendar 3310 through the user input unit 16510 . The second device 112 outputs job history information 3330 of the document on the screen according to the received user input. In this case, the second device 112 may output the job history information 3330 of the document on the screen as a pop-up window separate from the calendar 3310 . Also, an indicator 3340 for outputting a document to the screen of the second device 112 may be displayed on the screen on which the work history information 3330 of the document is displayed.

When the indicator 2740 is selected by the user, a preview screen of the document or an execution screen of the document may be output to the second device 112 . As an example, when the user briefly touches the indicator 2740 , a preview screen of the document may be output, and when the user touches the indicator 2740 for a long time, an execution screen of the document may be output. As another example, when the cursor displayed on the screen of the second device 112 is positioned on the indicator 2740, a preview screen of the document may be output, and when the indicator 2740 is clicked by the user, the execution screen of the document This can be output.

The second device 112 receives a user input (eg, a long touch or click) for selecting the indicator 3340 through the user input unit 16510 . The second device 112 requests 3350 to transmit the document to the first device 111 according to the received user input. Then, the first device 111 transmits the document to the second device 112 according to the request of the second device 112 ( 3360 ).

34 is a flowchart illustrating an example in which a server links job history information of a document to a calendar, according to some embodiments.

The flowchart shown in FIG. 34 corresponds to the detailed flowchart of S2622 of FIG. 26B and S3223 of FIG. 32B.

In S3410, the server 100 acquires the reading time information of the document included in the job history information received from the second device 112. For example, according to the example described above with reference to FIG. 31 , the server 100 acquires '2014.05.20, 08:46:04 PM' from the job history information received from the second device 112 .

Hereinafter, an example of the job history information obtained by the server 100 will be described with reference to FIGS. 35 to 36 .

35 to 36 are diagrams illustrating an example of job history information of a document according to some embodiments.

The job history information 3510 of the document shown in FIG. 35 is an example updated from the job history information 1310 of the document shown in FIG. 13 . In other words, the job history information 1310 of the document shown in FIG. 13 means the job history information 1310 generated when the device generates the document. On the other hand, the job history information 3510 of the document shown in FIG. 35 means that the new job history information 3520 and 3530 is added as the device generates a document and at least one of the devices reads the generated document. do.

Referring to FIG. 35 , the server 100 may arrange the job history information received from the second device 112 based on the document name 3511 .

The job history information 3610 of the document shown in FIG. 36 is an example updated from the job history information 1410 of the document shown in FIG. 14 . In other words, the job history information 1410 of the document shown in FIG. 14 means the job history information 1310 generated when the device generates the document. On the other hand, the job history information 3610 of the document shown in FIG. 36 means that the new job history information 3620 and 3630 are added as the device generates a document and at least one of the devices reads the generated document. do.

Referring to FIG. 36 , the server 100 may arrange the work history information received from the second device 112 based on the name 3611 of the work device.

Referring back to FIG. 34 , in S3420, the server 100 links work history information to the user's calendar based on the reading time information of the document. Hereinafter, an example in which the server 100 links job history information to a user's calendar will be described with reference to FIG. 37 .

37 is a flowchart illustrating an example in which a server links job history information to a user's calendar, according to some embodiments.

In S3710, the server 100 acquires a previously created user's calendar. Here, the pre-generated user's calendar means a calendar created by the server 100 linking the job history information transmitted from the first device to the calendar in S3214 of FIG. 32B .

In S3720, the server 100 generates an indicator to be displayed on the calendar based on any one of the name of the document included in the work history information, the program used to read the document, and the name of the device that has read the document. Here, the job history information means job history information received from the second device 112 . For example, the server 100 may determine any one of the name of the document, the program used for reading the document, and the name of the device that reads the document as the item indicated by the indicator, and generate the indicator based on the determined item. there is.

In S1530, the server 100 determines job history information to be displayed on the calendar based on the generated indicator.

In S1540, the server 100 adds an indicator to the area corresponding to the date or time indicating the time when the document was read in the calendar and displays it.

Hereinafter, an example in which the calendar is output on the screen of the device will be described with reference to FIGS. 38 to 47 . The calendars shown in FIGS. 38 to 47 correspond to the updated calendars shown in FIGS. 16 to 25 . Accordingly, even if omitted below, the above description with reference to FIGS. 16 to 25 is also applied to FIGS. 38 to 47 .

38 to 40 are diagrams illustrating examples of a daily calendar displayed on a screen of a device according to some embodiments.

Referring to FIG. 38 , an example of a daily calendar 3811 is output on the screen of the device 3810 .

In addition to the indicator 3820 displayed on the pre-generated calendar, the indicator 3830 may be additionally displayed on the calendar 3811 by updating the calendar. Here, the indicators 3820 and 3830 may be indicators indicating the name of the document.

For example, assuming that the second device 112 reads a document created by the first device 111 on May 20, 2014, 'abc.doc' is displayed in the area corresponding to May 20, 2014 in the calendar 3811. An indicating indicator 3830 may be further displayed.

The device 3810 may select at least one of the indicators 3820 and 3830 according to a user input received through the user input unit 16510 . In addition, the device 3810 may output job history information 3821 and 3831 corresponding to the selected indicator on the screen. In addition, indicators 3822 and 3832 for outputting a document to the screen of the device 3810 may be displayed on the screen on which the job history information 3821 and 3831 are displayed.

Referring to FIG. 39 , another example of a daily calendar 3911 is output on the screen of the device 3910 .

In the calendar 3911 , not only the indicator 3920 displayed on the previously created calendar, but also the indicator 3930 may be additionally displayed as the calendar is updated. Here, the indicators 3920 and 3930 may be indicators indicating the name of a program used to execute a document.

For example, assuming that the second device 112 reads a document generated by the first device 111 using the first program on May 20, 2014, in the area corresponding to May 20, 2014 in the calendar 3910 An indicator 3930 indicating the 'first program' may be additionally displayed.

In accordance with a user input received through the user input unit 16510 , work history information 3921 , 3931 of a document on the screen of the device 3910 and indicators 3922 and 3932 capable of outputting the document to the screen of the device 3910 . ) may be displayed as described above with reference to FIG. 38 .

Referring to FIG. 40 , another example of a daily calendar 4011 is output on the screen of the device 4010 .

In the calendar 4011 , not only the indicator 4020 displayed on the previously created calendar, but also the indicator 4030 may be additionally displayed as the calendar is updated. Here, the indicators 4020 and 4030 may be indicators indicating the name of the device that executed the document.

For example, assuming that the second device 112 reads a document generated by the first device 111 on May 20, 2014, 'second device' is displayed in the area corresponding to May 20, 2014 in the calendar 4011. An indicating indicator 4030 may be additionally displayed.

In accordance with a user input received through the user input unit 16510 , work history information 4021 , 4031 of a document and indicators 4022 and 4032 capable of outputting the document to the screen of the device 4010 on the screen of the device 4010 . ) may be displayed as described above with reference to FIG. 38 .

41 to 43 are diagrams illustrating examples of monthly calendars displayed on a screen of a device according to some embodiments.

Referring to FIG. 41 , an example of a monthly calendar 4111 is output on the screen of the device 4110 .

In the calendar 4111 , indicators 4130 and 4140 may be additionally displayed as the calendar is updated as well as the indicator 4120 displayed on the previously created calendar. Here, the indicators 4120 , 4130 , and 4140 may be indicators indicating the name of a document.

For example, assuming that the second device 112 reads the document generated by the first device 111 on May 20, 2014, 'abc.doc' is displayed in the area corresponding to May 20, 2014 in the calendar 4111. An indicating indicator 4130 may be additionally displayed. In addition, assuming that the third device 113 reads a document named 'kkk.ppt' on May 28, 2014, an indicator ( 4140) may be additionally displayed.

According to a user input received through the user input unit 16510 , work history information 4151 and 4152 of a document and indicators 4161 and 4162 capable of outputting the document to the screen of the device 4110 on the screen of the device 4110 ) may be displayed as described above with reference to FIG. 38 .

Referring to FIG. 42 , another example of the monthly calendar 4211 is output on the screen of the device 4210 .

In the calendar 4211 , indicators 4230 and 4240 may be additionally displayed as the calendar is updated, as well as indicators displayed on a pre-generated calendar. Here, the indicators 4130 and 4140 may be indicators indicating the name of a program used to execute a document.

For example, assuming that the second device 112 reads a document generated by the first device 111 using the first program on May 20, 2014, in the area corresponding to May 20, 2014 in the calendar 4211 An indicator 4230 indicating the 'first program' may be additionally displayed. Also, assuming that the third device 113 reads a document named 'kkk.ppt' using the third program on May 28, 2014, the 'third An indicator 4240 indicating 'program' may be additionally displayed.

According to a user input received through the user input unit 16510 , work history information 4251 and 4252 of a document and indicators 7261 and 4262 capable of outputting the document to the screen of the device 4210 on the screen of the device 4210 ) may be displayed as described above with reference to FIG. 38 .

Referring to FIG. 43 , another example of the monthly calendar 4311 is output on the screen of the device 4310 .

In the calendar 4311 , indicators 4330 and 4340 may be additionally displayed as the calendar is updated, as well as indicators displayed on a pre-generated calendar. Here, the indicators 4330 and 4340 may be indicators indicating the name of the device that executed the document.

For example, assuming that the second device 112 reads a document generated by the first device 111 on May 20, 2014, 'second device' is displayed in the area corresponding to May 20, 2014 in the calendar 4311. An indicating indicator 4330 may be additionally displayed. Also, assuming that the third device 113 reads a document titled 'kkk.ppt' on May 28, 2014, 'third device 113' is displayed in the area corresponding to May 28, 2014 in the calendar 4311. An indicating indicator 4340 may be additionally displayed.

According to the user input received through the user input unit 16510 , the job history information 4351 and 4352 of the document and an indicator for outputting the document to the screen of the device 4310 may be displayed on the screen of the device 4310 . It is the same as described above with reference to FIG. 38 .

44 to 47 are diagrams illustrating examples of annual calendars displayed on a screen of a device according to some embodiments.

Referring to FIG. 44 , an annual calendar 4411 is output on the screen of the device 4410 .

Indicators 4420 , 4430 , 4440 , and 4450 indicating document names may be displayed on the calendar 4411 . For example, assuming that the first device 111 generates a document named 'xyz.doc' on February 12, 2014, an indicator ( 4420) may be displayed.

Also, assuming that the first device 111 generates a document named 'abcd.xls' on April 22, 2014, an indicator 4430 indicating 'abcd.xls' in an area corresponding to 2014.04 in the calendar 4411 may be displayed.

Also, assuming that the first device 111 generates a document named 'abc.doc' on May 12, 2014, an indicator 4440 indicating 'abc.doc' in an area corresponding to May 2014 in the calendar 4411 may be displayed. Also, assuming that the first device 111 generates a document named 'kkk.ppt' on May 20, 2014, an indicator 4450 indicating 'kkk.ppt' in the area corresponding to May 2014 in the calendar 4411 may be displayed.

Previously, it has been described that 'xyz.doc', 'abcd.xls', 'abc.doc', and 'kkk.ppt' are all generated by the first device 111, but different devices can generate each document. may be

The device 4410 may select the indicators 4420 , 4430 , 4440 , and 4450 indicating the name of the document according to the user input received through the user input unit 16510 . When the indicators 4420 , 4430 , 4440 , and 4450 indicating the name of the document are selected, the device 4410 may output the job history information 4460 of the document on the screen.

For example, it is said that the first device 111 stored a document named 'abc.doc' having a size of 54 KB (kilobyte) using the first program at 12:28:04 pm on May 12, 2014. Assume In addition, the second device 112 reads the stored document named 'abc.doc' having a size of 54 KB (kilobyte) using the first program at 08:46:11 pm on May 20, 2014. Assume

At this time, when the indicator 4440 indicating 'abc.doc' is selected, the job history information 4460 including the first job history information 4462 and the second job history information 4463 may be output. In the first job history information 4462, 'abc.doc, text, first program, first device, May 12, 2014 12:28:04, 54 KB' may be output, and second job history information 'abc.doc, text, first program, second device, May 20, 2014 08:46:11 PM, 54 KB' may be output to 4463 . Meanwhile, the device 4410 may output the job history information 4460 of the document on the screen as a separate pop-up window.

Also, an indicator 4461 capable of outputting a document to the screen of the device 4410 may be displayed in the job history information 4460 of the document. For example, when an indicator 4461 capable of outputting a document according to a user input received through the user input unit 16510 is selected, the device 4410 displays a pop-up window separate from the calendar 4411 to the first device ( 111) can be printed on the screen.

Referring to FIG. 45 , an annual calendar 4511 is output on the screen of the device 4510 . In addition, indicators 4520 , 4530 , 4540 , and 4550 indicating programs used for document work are displayed on the calendar 4511 . As described above with reference to FIG. 44 , when the indicators 4520 , 4530 , 4540 , and 4550 indicating a program used to work on a document are selected, the device 4510 displays the first job history information 4562 and the second job Job history information 4560 of a document including the history information 4563 may be output to the screen. In addition, when the indicator 4561 capable of outputting a document is selected on the screen on which the work history information 4560 of the document is displayed, the device 4510 may output the document generated by the first device 111 to the screen. .

Referring to FIG. 46 , an annual calendar 4611 is output on the screen of the device 4610 . In addition, indicators 4620 , 4630 , 4640 , 4650 , and 4660 indicating devices are displayed on the calendar 4611 . As described above with reference to FIG. 44 , when the indicators 4620 , 4630 , 4640 , 4650 , and 4660 indicating the device are selected, the device 4610 may output the execution history information 4670 of the document on the screen. Also, when the indicator 4671 capable of outputting a document is selected on the screen on which the execution history information 4670 of the document is displayed, the device 4610 may output the document generated by the first device 111 to the screen. .

Referring to FIG. 47 , an annual calendar 4711 is output on the screen of the device 4710 . The annual calendar shown in FIGS. 44 to 46 includes an area in which months included in a year are displayed, but the annual calendar 4711 shown in FIG. 47 includes an area in which days included in a year are displayed. there is. In other words, the device 4710 may variously change the format of the annual calendar and output it on the screen.

Indicators 4720 , 4721 , 4722 , 4730 , and 4731 may be displayed on the calendar 4711 on the date the document was performed. For example, assuming that the first device 111 generates a document named 'xyz.doc' on February 12, 2014, the calendar 4711 indicates 'xyz.doc' in the area corresponding to February 12, 2014. An indicator 4720 may be displayed.

In addition, assuming that the first device 111 generates a document named 'abcd.xls' on April 22, 2014, an indicator ( 4722) may be displayed.

Also, assuming that the first device 111 generates a document named 'abc.doc' on May 12, 2014, an indicator indicating 'abc.doc' in the area corresponding to May 12, 2014 in the calendar 4711 4721) may be displayed. Also, assuming that the first device 111 generates a document named 'kkk.ppt' on May 20, 2014, an indicator ( 4730) may be displayed.

Also, although it has been described above that all of 'xyz.doc', 'abcd.xls', and 'abc.doc' are generated by the first device 111, different devices may generate documents.

The device 4710 may select the indicators 4720 , 4721 , 4722 , 4730 , and 4731 indicating the name of the document according to the user input received through the user input unit 16510 . For example, the third device 113 transmits the stored document named 'kkk.ppt' having a size of 54 KB (kilobyte) using a third program on May 28, 2014 at 08:21:11 PM. Assume that you have read In this case, when the indicator 4731 indicating 'kkk.ppt' is selected, job history information 4750 may be output, and the job history information 4750 includes 'kkk.ppt, text, a third program, and a third device. , May 28, 2014 08:21:11 PM, 2387 KB' may be output. Meanwhile, the device 4710 may output the job history information 4750 of the document to the screen as a separate pop-up window.

In addition, when the indicator 4742 capable of outputting a document is selected on the screen on which the work history information 4750 of the document is displayed, the device 4710 may output the document read by the third device 113 to the screen. .

Hereinafter, with reference to FIGS. 48A to 65 , when the first device 111 creates a document and the second device 112 edits the document, the server 100 stores the job history information in the user's calendar. An example of interworking will be described.

48A to 48B are flowcharts illustrating an example in which a server links job history information to a user's calendar when the first device creates a document and the second device edits the document, according to some embodiments.

48A to 48B illustrate that the first device 111 generates a document and the second device 112 edits the document for convenience of explanation, but the present invention is not limited thereto. For example, the first device 111 may generate a document, and the first device 111 may edit the document.

Also, there is no limit to the number of devices. If it is assumed that the number of devices executing the document is N (N is a plurality of 3 or more), the operation of the first device 111 or the operation of the second device 112, which will be described below, is the operation of the third device 113 . to at least one of the Nth devices.

S4810 to S4816 of FIG. 48A correspond to S510 to S516 of FIG. 5 . Accordingly, even if omitted below, the contents described above with reference to FIGS. 5 to 25 may be applied to the contents to be described later with reference to S4810 to S4816 of FIG. 48A.

In S4810, the first device 111 executes a program for generating a document.

In S4811, the first device 111 generates a document and stores the generated document.

In S4812 , the first device 111 transmits the job history information of the document to the server 100 . For example, the first device 111 may transmit job history information of the document to the server 100 at the time the document is stored. In this case, it is assumed that the user of the first device 111 is logged in to the server 100 . In addition, examples in which the first device 111 transmits job history information of a document to the server 100 are the same as described above with reference to step S411 of FIG. 4 .

In S4813 , the server 100 links the job history information to the calendar using time information included in the job history information transmitted from the first device 111 .

In S4814, the second device 112 requests the server 100 to transmit information to be displayed on the calendar. For example, the second device 112 executes the calendar output program installed in the second device 112, authenticates the user using the input user account, and then transmits the information to be displayed on the calendar to the server 100 can request

In S4815 , the server 100 transmits information to be displayed on the calendar to the second device 112 .

In FIG. 48A, when the second device 112 requests the server 100 to transmit information to be displayed on the calendar in S4814, the server 100 transmits information to be displayed on the calendar in S4815. not limited For example, even if there is no transmission request from the second device 112 , information to be displayed on the calendar may be transmitted (eg, pushed) to the second device 112 .

In S4816, the second device 112 outputs the calendar on the screen.

In S4817, the second device 112 outputs the document to the screen. As an example, the second device 112 may request the first device 111 to transmit the document and output the document received from the first device 111 on the screen. As another example, the second device 112 may request the server 100 to transmit the document and output the document received from the server 100 on the screen.

In S4818, the second device 112 outputs the document received from the first device 111 or the server 100 on the screen.

In S4819, the second device 112 edits the document. Hereinafter, an example in which the second device 112 edits a document will be described with reference to FIGS. 49 to 50 .

49 to 50 are diagrams for explaining examples of editing a document by the second device 112 according to some embodiments.

49 to 50 , a document received from the first device 111 or the server 100 is output 4910 on the screen of the second device 112 . The second device 112 receives a user input for editing a document through the user input unit 16510 . For example, the user input may be for adding ( 4920 ) new content to the document, or for deleting ( 5010 ) some or all of the content of the document. Meanwhile, although not shown in the drawings, the user input may be for changing some or all of the contents of the document.

Referring to FIG. 49 , when the second device 112 receives a user input for adding new content to the document, new content is added to the output document 4910 ( 4920 ).

Referring to FIG. 50 , when the second device 112 receives a user input for deleting part of the content of the document, part of the content included in the output document 4910 is deleted ( 5010 ).

Referring back to FIG. 48B , the second device 112 stores the edited document in S4819.

In S4820 , the second device 112 transmits the edited and stored document and job history information of the document to the server 100 . For example, the second device 112 may transmit the document and work history information of the document to the server 100 at the time when the editing of the document is finished (ie, the time at which the document is stored). Hereinafter, an example in which the second device 112 transmits a document and job history information of the document to the server 100 will be described with reference to FIG. 51 .

FIG. 51 is a diagram for explaining an example in which the second device 112 transmits a document and job history information of the document to the server 100 according to some embodiments.

As described above with reference to FIGS. 49 to 50 , when receiving a user input for editing a document, the second device 112 may add new content to the document, or change or delete some or all of the content of the document. . When the second device 112 stores the document after adding new content to the document or changing or deleting some or all of the content of the document, the second device 112 determines that the document has been edited.

When the document is saved after editing, the second device 112 transmits the document and job history information of the document to the server 100 . In other words, the second device 112 transmits information generated by editing a document to the server 100 .

For example, the second device 112 executes and edits a document named 'abc.doc' using the first program, and stores the edited document at 09:11:43 pm on May 14, 2014 If so, and if the size of the document stored after editing is 1084 KB (kilobyte), the second device 112 tells the server 100 'abc.doc, text, first program, second device, on the afternoon of May 14, 2014. At least one of 09:11:43 and 1084KB' may be transmitted as job history information.

Meanwhile, as described above with reference to FIG. 7 that encryption may be additionally performed on the job history information of a document requiring a high degree of security and transmitted to the server 100 .

Referring again to FIG. 48B , in S4821 , the server 100 stores the document transmitted from the second device 112 .

In S4822 , the server 100 links the job history information to the calendar using time information included in the job history information transmitted from the second device 112 . For example, the server 100 links the job history information received from the first device 111 to the calendar in S4813, and additionally links the job history information received from the second device 112 to the calendar in S4822. .

In S4823, the first device 111 requests the server 100 to transmit information to be displayed on the calendar. For example, the first device 111 may request the server 100 to transmit job history information to be output on the screen of the device when an indicator to be displayed on the calendar or an indicator displayed on the calendar is selected.

In S4824 , the server 100 transmits information to be displayed on the calendar to the first device 111 .

In S4825, the first device 111 outputs the calendar on the screen.

In FIG. 48B, when the first device 111 requests the server 100 to transmit information to be displayed on the calendar in S4823, the server 100 transmits information to be displayed on the calendar in S4824. not limited For example, even if there is no transmission request from the first device 111 , the server 100 may transmit (eg, push) information to be displayed on the calendar to the first device 111 .

The contents to be described later with reference to S4826 to S4828 correspond to the contents described above with reference to S4823 to S4825. In other words, the second device 112 requests the server 100 to transmit information to be displayed on the calendar, receives information to be displayed on the calendar from the server 100 , and outputs the calendar on the screen. Accordingly, even if omitted below, the contents described above with reference to S4823 to S4825 may be applied to the contents to be described later with reference to S4826 to S4828.

In S4826, the second device 112 requests the server 100 to transmit information to be displayed on the calendar.

In S4827 , the server 100 transmits information to be displayed on the calendar to the second device 112 .

In S4828, the second device 112 outputs the calendar on the screen.

A specific example of the contents described above with reference to S4822 to S4828 of FIG. 48B will be described later with reference to FIGS. 52 to 65 .

52 is a flowchart illustrating an example in which the server 100 links job history information of a document to a calendar according to some embodiments.

The flowchart shown in FIG. 52 corresponds to the detailed flowchart of S4822 of FIG. 48B.

In S5210 , the server 100 acquires editing time information of a document included in the job history information received from the second device 112 . For example, according to the example described above with reference to FIG. 51 , the server 100 acquires '2014.05.14, 09:11:43 PM' from the job history information received from the second device 112 .

Hereinafter, an example of the job history information obtained by the server 100 will be described with reference to FIGS. 53 to 54 .

53 to 54 are diagrams illustrating an example of job history information of a document according to some embodiments.

The job history information 5310 of the document shown in FIG. 53 is an example updated from the job history information 1310 of the document shown in FIG. 13 . In other words, the job history information 1310 of the document shown in FIG. 13 means the job history information 1310 generated when the device generates the document. On the other hand, the job history information 5310 of the document shown in FIG. 53 means that the new job history information 5320 and 5330 is added as the device creates a document and at least one of the devices edits the generated document. do.

Referring to FIG. 53 , the server 100 may arrange the job history information received from the second device 112 based on the name 5311 of the document.

The job history information 5410 of the document shown in FIG. 54 is an example updated from the job history information 1410 of the document shown in FIG. 14 . In other words, the job history information 1410 of the document shown in FIG. 14 means the job history information 1410 generated when the device generates the document. On the other hand, the job history information 5410 of the document shown in FIG. 54 means that new job history information 5420 and 5430 are added as the device creates a document and at least one of the devices edits the generated document. do.

Referring to FIG. 54 , the server 100 may arrange the work history information received from the second device 112 based on the name 5411 of the work device.

Referring back to FIG. 52 , in S5220 , the server 100 links the job history information to the user's calendar based on the editing time information of the document. Hereinafter, an example in which the server 100 links job history information to a user's calendar will be described with reference to FIG. 55 .

55 is a flowchart illustrating an example in which the server 100 links job history information to a user's calendar, according to some embodiments.

In S5510, the server 100 acquires a previously created user's calendar. Here, the pre-generated user's calendar refers to a calendar generated by the server 100 linking the job history information transmitted from the first device 111 to the calendar in S4813 of FIG. 48A .

In S5520, the server 100 generates an indicator to be displayed on the calendar based on any one of the name of the document included in the work history information, the program used for editing the document, and the name of the device that edited the document. Here, the job history information means job history information received from the second device 112 . For example, the server 100 may determine any one of the name of the document, the program used for editing the document, and the name of the device that edited the document as the item indicated by the indicator, and generate the indicator based on the determined item. there is.

In S5530, the server 100 determines job history information to be displayed on the calendar based on the generated indicator.

In S5540, the server 100 adds and displays an indicator to an area corresponding to a date or time indicating when a document was edited in the calendar.

56 is a diagram illustrating an example of a daily calendar displayed on a screen of a device according to some embodiments.

Referring to FIG. 56 , a daily calendar 5611 is output on the screen of the device 5610 . The calendar 5611 may include an area 5612 indicating dates and an indicator 5613 through which a user can designate a desired date. Also, the calendar 5611 may include an indicator 5614 capable of displaying a calendar corresponding to the date of 'today'. In addition to the above-described indicators, the calendar 5611 may be included without limitation as long as it is an indicator through which the user can control the display type of the calendar.

An indicator 5620 indicating the name of a document may be displayed on the calendar 5611 . For example, assuming that the first device 111 edits a document named 'abc.doc' on May 14, 2014, the calendar 5611 indicates 'abc.doc' in the area corresponding to May 12, 2014. An indicator 5620 may be displayed.

The device 5610 may select the indicator 5620 indicating 'abc.doc' according to the user input received through the user input unit 16510 . When the indicator 5620 indicating 'abc.doc' is selected, the device 5610 may output the job history information 5621 of the document on the screen. For example, it is said that the second device 112 edited a document named 'abc.doc' having a size of 1084 KB (kilobyte) using the first program at 09:11:43 pm on May 14, 2014. It is assumed that 'abc.doc, text, first program, second device, 09:11:43 pm on May 14, 2014, 1084 KB' may be output to the work history information 5621 . Meanwhile, the device 5610 may output the job history information 5621 of the document to the screen as a separate pop-up window.

In addition, indicators 5622 and 5623 for outputting a document to the screen of the device 5610 may be displayed in the job history information 5621 of the document. The indicator 5622 may be an indicator indicating an original document at the time of document creation or a document prior to the current job, and the indicator 5623 may be an indicator indicating a current edited document.

The indicator 5623 indicating the edited document may be displayed to be distinguished from the indicator 5622 indicating the original document or the document before the current job. For example, in the case of the indicator 5623 of the edited document, a border line may be additionally displayed on the indicator 5622 indicating the original document or the document before the current work. For example, when an indicator 5622 or 5623 capable of outputting a document according to a user input received through the user input unit 16510 is selected, the device 5610 displays the original document as a pop-up window separate from the calendar 5611 . Alternatively, the document edited by the second device may be output to the screen.

Similarly, a plurality of indicators indicating the name of a document may be displayed on one calendar 5611 . For example, assuming that the third device 113 edits a document named 'xyz.doc' on May 12, 2014, the calendar 5611 indicates 'xyz.doc' in the area corresponding to May 12, 2014. An indicator 5630 may be displayed.

The device 5610 may select the indicator 5630 indicating 'xyz.doc' according to the user input received through the user input unit 16510 . When the indicator 5630 indicating 'xyz.doc' is selected, the device 5610 may output the job history information 5631 of the document on the screen. For example, it is said that the third device 113 edited a document named 'xyz.doc' having a size of 2387 KB (kilobyte) using the first program at 09:14:03 am on May 12, 2014. Assume that 'xyz.doc, text, first program, third device 113, May 12, 2014, 09:14:03 am, 2387 KB' may be output to the work history information 5631 . Meanwhile, the device 5610 may output the job history information 5631 of the document to the screen as a separate pop-up window.

In addition, indicators 5632 and 5633 for outputting a document to the screen of the device 5610 may be displayed in the job history information 5631 of the document. The indicator 5632 may be an indicator indicating an original document at the time of document creation or a document prior to the current job, and the indicator 5633 may be an indicator indicating a current edited document.

The indicator 5633 indicating the edited document may be displayed to be distinguished from the indicator 5632 indicating the original document or the document before the current job. For example, in the case of the indicator 5633 of the edited document, a border line may be additionally displayed on the indicator 5632 indicating the original document or the document before the current work. When an indicator 5632 or 5633 capable of outputting a document is selected according to a user input received through the user input unit 16510 , the device 5610 displays an original document or a third device as a pop-up window separate from the calendar 5611 . The document edited by (113) can be output to the screen.

57 is a diagram illustrating another example of a daily calendar displayed on a screen of a device according to some embodiments.

Referring to FIG. 57 , a daily calendar 5711 is output on the screen of the device 5710 . The calendar 5711 shown in FIG. 57 has the same frame as the calendar 5611 shown in FIG. 56 . Accordingly, the contents described above with reference to FIG. 56 with respect to objects that can be displayed on the calendar 5711 may be equally applied to FIG. 57 .

An indicator 5720 indicating a program used to work on a document may be displayed on the calendar 5711 . For example, assuming that the second device edits a document using the first program on May 14, 2014, an indicator 5720 indicating the 'first program' is displayed in the area corresponding to May 12, 2014 of the calendar 5711. can be displayed.

The device 5710 may select the indicator 5720 indicating the 'first program' according to the user input received through the user input unit 16510 . When the indicator 5720 indicating the 'first program' is selected, the device 5710 may output the job history information 5721 of the document on the screen. For example, it is said that the second device 112 edited a document named 'abc.doc' having a size of 1084 KB (kilobyte) using the first program at 09:11:43 pm on May 14, 2014. Assume that 'abc.doc, text, first program, second device, 09:11:43 pm on May 14, 2014, 1084 KB' may be output to the work history information 5721 . Meanwhile, the device 5710 may output the job history information 5721 of the document to the screen as a separate pop-up window.

Also, indicators 5722 and 5723 for outputting a document to the screen of the device 5710 may be displayed in the job history information 5721 of the document. The indicator 5722 may be an indicator indicating an original document at the time of document creation or a document prior to the current job, and the indicator 5723 may be an indicator indicating a current edited document.

The indicator 5723 indicating the edited document may be displayed to be distinguished from the indicator 5722 indicating the original document or the document before the current job. For example, in the case of the indicator 5723 of the edited document, a border line may be displayed on the indicator 5722 indicating the original document or the document before the current work. When an indicator 5722 or 5723 capable of outputting a document is selected according to a user input received through the user input unit 16510 , the device 5710 displays an original document or a second device as a pop-up window separate from the calendar 5711 . The edited document can be printed on the screen.

Similarly, a plurality of indicators indicating programs may be displayed on one calendar 5711 . For example, assuming that the third device 113 edits a document named 'xyz.doc' on May 12, 2014, the calendar 5711 indicates the 'first program' in the area corresponding to May 12, 2014. An indicator 5730 may be displayed.

The device 5710 may select the indicator 5730 indicating the 'first program' according to the user input received through the user input unit 16510 . When the indicator 5730 indicating the 'first program' is selected, the device 5710 may output the job history information 5731 of the document on the screen. For example, it is said that the third device 113 edited a document named 'xyz.doc' having a size of 2384 KB (kilobyte) using the first program at 09:14:03 am on May 12, 2014. Assume that 'xyz.doc, text, first program, third device 113, May 12, 2014, 09:14:03 am, 2387 KB' may be output to the work history information 5731 . Meanwhile, the device 5710 may output the job history information 5731 of the document to the screen as a separate pop-up window.

Also, an indicator 5732 capable of outputting a document to the screen of the device 5710 may be displayed in the job history information 5731 of the document. For example, when an indicator 5733 capable of outputting a document according to a user input received through the user input unit 16510 is selected, the device 5710 displays a pop-up window separate from the calendar 5711 to the third device ( 113) can display the edited document on the screen.

58 is a diagram illustrating another example of a daily calendar displayed on a screen of a device according to some embodiments.

Referring to FIG. 58 , a daily calendar 5811 is output on the screen of the device 5810 . The calendar 5811 shown in FIG. 58 has the same frame as the calendar 5611 shown in FIG. Accordingly, the contents described above with reference to FIG. 56 with respect to indicators that may be displayed on the calendar 5811 may be equally applied to FIG. 58 .

An indicator 5820 indicating a device name may be displayed on the calendar 5811 . For example, assuming that the second device 112 edits a document on May 14, 2014, an indicator 5820 indicating the 'second device' may be displayed in an area corresponding to May 12, 2014 of the calendar 5811. there is.

The device 5810 may select the indicator 5820 indicating the 'second device' according to the user input received through the user input unit 16510 . When the indicator 5820 indicating the 'second device' is selected, the device 5810 may output the job history information 5821 of the document to the screen. For example, it is said that the second device 112 edited a document named 'abc.doc' having a size of 1084 KB (kilobyte) using the first program at 09:11:43 pm on May 14, 2014. Assume that 'abc.doc, text, first program, second device, 09:11:43 pm on May 14, 2014, 1084 KB' may be output to the work history information 5821 . Meanwhile, the device 5810 may output the job history information 5821 of the document to the screen as a separate pop-up window.

In addition, indicators 5822 and 5823 for outputting a document to the screen of the device 5810 may be displayed in the job history information 5821 of the document. The indicator 5822 may be an indicator indicating an original document at the time of document creation or a document prior to the current job, and the indicator 5823 may be an indicator indicating a current edited document.

The indicator 5823 indicating the edited document may be displayed to be distinguished from the indicator 5822 indicating the original document or the document before the current job. For example, in the case of the indicator 5823 of the edited document, a border line may be additionally displayed on the indicator 5822 indicating the original document or the document before the current work. When an indicator 5822 or 5823 capable of outputting a document is selected according to a user input received through the user input unit 16510 , the device 5810 displays the original document or the second device as a pop-up window separate from the calendar 5811 . The edited document can be printed on the screen.

Similarly, a plurality of indicators indicating device names may be displayed on one calendar 5811 . For example, assuming that the third device 113 edits a document named 'xyz.doc' on May 12, 2014, in the area corresponding to May 12, 2014 in the calendar 5811, the 'third device 113' An indicator 5830 indicating ' may be displayed.

The device 5810 may select the indicator 5830 indicating the 'third device 113' according to the user input received through the user input unit 16510 . When the indicator 5830 indicating the 'third device 113' is selected, the device 5810 may output the job history information 5831 of the document on the screen. For example, it is said that the third device 113 reads a document named 'xyz.doc' having a size of 2387 KB (kilobyte) using the first program at 09:14:03 am on May 12, 2014. Assume that 'xyz.doc, text, first program, third device 113, May 12, 2014, 09:14:03 am, 2387 KB' may be output to the work history information 5831 . Meanwhile, the device 5810 may output the job history information 5831 of the document to the screen as a separate pop-up window.

Also, indicators 5832 and 5833 for outputting a document to the screen of the device 5810 may be displayed in the job history information 5831 of the document. The indicator 5832 may be an indicator indicating an original document at the time of document creation or a document prior to the current job, and the indicator 5833 may be an indicator indicating a currently edited document. The indicator 5833 indicating the edited document may be displayed to be distinguished from the indicator 5832 indicating the original document or the document before the current job. For example, in the case of the indicator 5833 of the edited document, a border line may be additionally displayed on the indicator 5832 indicating the original document or the document before the current work. When an indicator 5832 or 5833 capable of outputting a document is selected according to a user input received through the user input unit 16510 , the device 5810 displays the original document or the second device as a pop-up window separate from the calendar 5811 . The edited document can be printed on the screen.

59 is a diagram illustrating an example of a monthly calendar displayed on a screen of a device according to some embodiments.

Referring to FIG. 59 , a monthly calendar 5911 is output on the screen of the device 5910 . The calendar 5911 shown in FIG. 59 has the same frame as the calendar 1920 shown in FIG. 19 . Accordingly, the contents described above with reference to FIG. 19 with respect to objects that can be displayed on the calendar 5911 may be equally applied to FIG. 59 .

An indicator 5930 and an indicator 5940 indicating the name of a document may be displayed on the calendar 5911 . For example, assuming that the second device 112 edits a document named 'abc.doc' on May 14, 2014, the calendar 5911 indicates 'abc.doc' in the area corresponding to May 14, 2014. An indicator 5930 may be displayed. Similarly, assuming that the third device 113 edits a document named 'xyz.doc' on May 14, 2014, an indicator ( 5940) may be displayed.

The device 5910 may select the indicator 5930 indicating 'abc.doc' according to the user input received through the user input unit 16510 . When the indicator 5930 indicating 'abc.doc' is selected, the device 5910 may output job history information 5951 of the document on the screen.

For example, the second device 112 stores a document named 'abc.doc' having a size of 1084 KB (kilobyte) using the first program at 09:11:43 pm on May 14, 2014. Assume that 'abc.doc, text, first program, second device, 09:11:43 pm on May 14, 2014, 1084 KB' may be output to the work history information 5951 . Meanwhile, the device 5910 may output the job history information 5951 of the document to the screen as a separate pop-up window.

Similarly, the device 5910 may select the indicator 5940 indicating 'xyz.doc' according to a user input received through the user input unit 16510 . When the indicator 5940 indicating 'xyz.doc' is selected, the device 5910 may output work history information 5952 of the document on the screen.

For example, it is said that the third device 113 stores a document named 'xyz.doc' having a size of 2387 KB (kilobyte) using the first program at 09:14:03 am on May 14, 2014. Assume that 'xyz.doc', text, first program, third device, May 14, 2014 09:14:03 am, 2387 KB' may be output to the work history information 5952 . Meanwhile, the device 5910 may output the job history information 5952 of the document to the screen as a separate pop-up window.

Also, an indicator 5961 and an indicator 5971 capable of outputting a document to the screen of the device 5910 may be displayed in the job history information 5951 of the document. For example, when an indicator 5961 capable of outputting a document according to a user input received through the user input unit 16510 is selected, the device 5910 displays a pop-up window separate from the calendar 5911 to the second device ( 112) can output the document before editing on the screen. Also, when the indicator 5971 is selected, the device 5910 may output the document edited by the second device 112 to the screen in a pop-up window separate from the calendar 5911 .

Similarly, an indicator 5962 and an indicator 5972 capable of outputting a document to the screen of the device 5910 may be displayed in the job history information 5952 of the document. For example, when an indicator 5962 capable of outputting a document according to a user input received through the user input unit 16510 is selected, the device 5910 displays a pop-up window separate from the calendar 5911 to the third device ( 113) can output the document before editing on the screen. Also, when the indicator 5972 is selected, the device 5910 may output the document edited by the third device 113 to the screen in a pop-up window separate from the calendar 5911 .

60 is a diagram illustrating another example of a monthly calendar displayed on a screen of a device according to some embodiments.

Referring to FIG. 60 , a monthly calendar 6011 is output on the screen of the device 6010 . The calendar 6011 shown in FIG. 60 has the same frame as the calendar 1920 shown in FIG. 19 . Accordingly, the contents described above with reference to FIG. 19 with respect to objects that may be displayed on the calendar 6011 may be equally applied to FIG. 60 .

An indicator 6030 and an indicator 6040 indicating a program used for document work may be displayed on the calendar 6011 . For example, assuming that the second device 6010 edits a document using the first program on May 14, 2014, an indicator indicating the 'first program' in the area corresponding to May 14, 2014 of the calendar 6020 ( 6030) may be displayed. Similarly, assuming that the third device 113 edits the document using the first program on May 14, 2014, an indicator 6040 indicating the 'first program' in the area corresponding to May 14, 2014 in the calendar 6011 may be displayed.

The device 6010 may select the indicator 6030 indicating the 'first program' according to the user input received through the user input unit 16510 . When the indicator 6030 indicating the 'first program' is selected, the device 6010 may output job history information 6051 of the document to the screen. For example, the second device 112 stores a document named 'abc.doc' having a size of 1084 KB (kilobyte) using the first program at 09:11:43 pm on May 14, 2014. Assume that 'abc.doc, text, first program, second device, 09:11:43 pm on May 14, 2014, 1084 KB' may be output to the work history information 6051 . Meanwhile, the device 6010 may output the job history information 6051 of the document to the screen as a separate pop-up window.

Similarly, the device 6010 may select the indicator 6040 indicating the 'first program' according to the user input received through the user input unit 16510 . When the indicator 6040 indicating the 'first program' is selected, the device 6010 may output job history information 6052 of the document to the screen. For example, it is said that the third device 113 stores a document named 'xyz.doc' having a size of 2387 KB (kilobyte) using the first program at 09:14:03 am on May 14, 2014. Assume that 'xyz.doc', text, first program, third device, May 14, 2014 09:14:03 am, 2387 KB' may be output to the work history information 6052 . Meanwhile, the device 6010 may output the job history information 6052 of the document to the screen as a separate pop-up window.

Also, an indicator 6061 and an indicator 6071 capable of outputting a document to the screen of the device 6010 may be displayed in the job history information 6051 of the document. For example, when an indicator 6061 capable of outputting a document according to a user input received through the user input unit 16510 is selected, the device 6010 displays a pop-up window separate from the calendar 6020 to the second device ( 112) can output the document before editing on the screen. Also, when the indicator 6071 is selected, the device 6010 may output the document edited by the second device 112 to the screen in a pop-up window separate from the calendar 6011 .

Similarly, an indicator 6062 and an indicator 6072 capable of outputting a document to the screen of the device 6010 may be displayed in the job history information 6052 of the document. For example, when an indicator 6062 capable of outputting a document according to a user input received through the user input unit 16510 is selected, the device 6010 displays a pop-up window separate from the calendar 6011 to the third device ( 113) can output the document before editing on the screen. Also, when the indicator 6072 is selected, the device 6010 may output the document edited by the third device 113 to the screen in a pop-up window separate from the calendar 6011 .

61 is a diagram illustrating another example of a monthly calendar displayed on a screen of a device according to some embodiments.

Referring to FIG. 61 , a monthly calendar 6111 is output on the screen of the device 6110 . The calendar 6111 shown in FIG. 61 has the same frame as the calendar 1910 shown in FIG. 19 . Accordingly, the contents described above with reference to FIG. 19 with respect to objects that may be displayed on the calendar 6111 may be equally applied to FIG. 61 .

An indicator 6130 and an indicator 6140 indicating a device name may be displayed on the calendar 6111 . For example, assuming that the second device 112 edits a document on May 14, 2014, an indicator 6130 indicating the 'second device' may be displayed in an area corresponding to May 14, 2014 of the calendar 6111. there is. Similarly, assuming that the third device 113 edits a document on May 14, 2014, an indicator 6140 indicating a 'third device' may be displayed in an area corresponding to May 14, 2014 in the calendar 6111 .

The device 6110 may select the indicator 6130 indicating the 'second device' according to the user input received through the user input unit 16510 . When the indicator 6130 indicating the 'second device' is selected, the device 6110 may output the job history information 6151 of the document on the screen. For example, the second device 112 stores a document named 'abc.doc' having a size of 1084 KB (kilobyte) using the first program at 09:11:43 pm on May 14, 2014. It is assumed that 'abc.doc, text, first program, second device, 09:11:43 pm on May 14, 2014, 1084 KB' may be output to the work history information 6151 . Meanwhile, the device 6110 may output the job history information 6151 of the document to the screen as a separate pop-up window.

Similarly, the device 6110 may select the indicator 6140 indicating the 'third device' according to the user input received through the user input unit 16510 . When the indicator 6140 indicating the 'third device' is selected, the device 6110 may output job history information 6152 of the document to the screen. For example, it is said that the third device 113 stores a document named 'xyz.doc' having a size of 2387 KB (kilobyte) using the first program at 09:14:03 am on May 14, 2014. Assume that 'xyz.doc', text, first program, third device, May 14, 2014 09:14:03 am, 2387 KB' may be output to the work history information 6152 . Meanwhile, the device 6110 may output the job history information 6152 of the document to the screen as a separate pop-up window.

Also, an indicator 6161 and an indicator 6171 capable of outputting a document to the screen of the device 6110 may be displayed in the job history information 6151 of the document. For example, when an indicator 6161 capable of outputting a document according to a user input received through the user input unit 16510 is selected, the device 6110 displays a pop-up window separate from the calendar 6120 to the second device ( 112) can output the document before editing on the screen. Also, when the indicator 6171 is selected, the device 6110 may output the document edited by the second device 112 to the screen in a pop-up window separate from the calendar 6111 .

Similarly, an indicator 6162 and an indicator 6172 capable of outputting a document to the screen of the device 6110 may be displayed in the job history information 6152 of the document. For example, when an indicator 6162 capable of outputting a document according to a user input received through the user input unit 16510 is selected, the device 6110 displays a pop-up window separate from the calendar 6111 to the third device ( 113) can output the document before editing on the screen. Also, when the indicator 6172 is selected, the device 6110 may output the document edited by the third device 113 to the screen in a pop-up window separate from the calendar 6111 .

62 is a diagram illustrating an example of an annual calendar displayed on a screen of a device according to some embodiments.

Referring to FIG. 62 , an annual calendar 6211 is output on the screen of the device 6210 . Indicators 6220 , 6230 , 6240 , 6250 , and 6260 indicating document names may be displayed on the calendar 6211 . For example, assuming that the third device 113 edits a document named 'xyz.doc' on May 12, 2014, an indicator indicating 'xyz.doc' in the area corresponding to May 2014 in the calendar 6211 ( 6250) may be displayed. In addition, assuming that the second device 112 edits a document named 'abc.doc' on May 14, 2014, an indicator 6260 indicating 'abc.doc' in the area corresponding to May 2014 in the calendar 6211 may be displayed.

The device 6210 may select the indicators 6220 , 6230 , 6240 , 6250 , and 6260 indicating the name of the document according to the user input received through the user input unit 16510 . When the indicators 6220 , 6230 , 6240 , 6250 , and 6260 indicating the name of the document are selected, the device 6210 may output the job history information 6270 and 6280 of the document on the screen. For example, it is said that the third device 113 edited a document named 'xyz.doc' having a size of 2387 KB (kilobyte) using the first program at 09:14:03 am on May 12, 2014. Assume At this time, when the indicator 6250 indicating 'xyz.doc' is selected, the job history information 6280 includes 'xyz.doc, text, first program, third device, May 12, 2014 09:14 am: 03, 2378 KB' may be output. Also, for example, the second device 112 sends a document named 'abc.doc' having a size of 1084 KB (kilobyte) using the first program on May 14, 2014 at 09:11:43 PM. I'm assuming it's been edited. At this time, when the indicator 6260 indicating 'abc.doc' is selected, the job history information 6270 includes 'abc.doc, text, first program, second device, May 14, 2014 09:11: 43, 1084 KB' can be output. Meanwhile, the device 6210 may output the job history information 6270 and 6280 of the document on the screen as a separate pop-up window.

In addition, indicators 6271 , 6272 , 6281 , and 6282 for outputting a document to the screen of the device 6210 may be displayed in the job history information 6270 and 6280 of the document. The indicator 6271 may be an indicator capable of outputting the original document of 'abc.doc' on the screen of the device. The indicator 6281 may be an indicator capable of outputting the original document of 'xyz.doc' on the screen of the device. The indicator 6272 may be an indicator capable of outputting the edited document of 'abc.doc' on the screen of the device. The indicator 6282 may be an indicator capable of outputting the edited document of 'xyz.doc' on the screen of the device. For example, when an indicator 6272 capable of outputting a document according to a user input received through the user input unit 16510 is selected, the device 6210 displays 'abc.doc' as a pop-up window separate from the calendar 6211 . ', the document edited by the second device 112 may be output to the screen.

63 is a diagram illustrating another example of an annual calendar displayed on a screen of a device according to some embodiments.

Referring to FIG. 63 , an annual calendar 6311 is output on the screen of the device 6310 . In addition, indicators 6320 , 6330 , 6340 , 6350 , and 6360 indicating programs used for document work are displayed on the calendar 6311 . As described above with reference to FIGS. 57 and 60 , when the indicators 6350 and 6360 indicating a program used for working on a document are selected, the device 6310 displays job history information 6370 and 6380 of the document on the screen. can be printed out. Also, when the indicators 6471 , 6472 , 6481 , and 6482 capable of outputting a document are selected on the screen on which the work history information 6370 and 6380 of the document is displayed, the document indicated by the corresponding indicator may be output on the screen. For example, when the indicator 6472 is selected, the device 6310 may output a document edited by the second device 112 with respect to 'abc.doc' on the screen.

64 is a diagram illustrating another example of an annual calendar displayed on a screen of a device according to some embodiments.

Referring to FIG. 64 , an annual calendar 6411 is output on the screen of the device 6410 . In addition, indicators 6420 , 6430 , 6440 , 6450 , and 6460 indicating devices are displayed on the calendar 6411 . As described above with reference to FIG. 62 , when the indicator 6450 indicating the device is selected, the device 6410 may output the execution history information 6480 of the document on the screen. In addition, as described above with reference to FIG. 62 , when the indicator 6471 , 6472 , 6481 , 6482 capable of outputting a document is selected on the screen on which the execution history information 6470 and 6480 of the document is displayed, the device 6410 may output the document generated by the first device 111 to the screen.

65 is a diagram illustrating another example of an annual calendar displayed on a screen of a device according to some embodiments.

Referring to FIG. 65 , an annual calendar 6511 is output on the screen of the device 6510 . The annual calendar shown in FIGS. 62 to 64 includes an area in which months included in a year are displayed, but the annual calendar 6511 shown in FIG. 65 includes an area in which days included in a year are displayed. there is. In other words, the device 6510 may variously change the format of the annual calendar and output it on the screen.

Indicators 6520 to 6525 may be displayed on the calendar 6511 on the date the document was performed. For example, assuming that the second device 112 edits a document named 'abc.doc' on May 14, 2014, the calendar 6511 indicates 'abc.doc' in the area corresponding to May 14, 2014. An indicator 6520 may be displayed. Also, assuming that the third device 113 edits a document named 'xyz.doc' on May 14, 2014, the indicator 6520 may also be displayed as an indicator 6520 indicating editing of 'xyz.doc'. there is.

As described above with reference to FIG. 62 , when the indicator 6520 displayed on the calendar 6511 is selected, the device 6510 may output the job history information 6530 of the document on the screen. The job history information 6530 includes first job history information 6533 indicating job history information on 'abc.doc' and second job history information 6536 indicating job history information on 'xyz.doc'. may include. Also, when the indicators 6531 , 6532 , 6534 , and 6535 for outputting a document are selected on the screen on which the work history information 6530 of the document is displayed, the device 6510 may output the corresponding document on the screen.

66A to 66C are flowcharts illustrating another example in which a server links job history information to a user's calendar when the first device creates a document and the second device reads and edits the document, according to some embodiments; am.

S6610 to S6629 of FIGS. 66A to 66B are processes in which the server 100 links work history information to the user's calendar when reading a document, and are the same as S3210 to S3229 of FIGS. 32A to 32B . Accordingly, detailed descriptions of steps S6610 to S6629 of FIGS. 66A to 66B will be omitted below.

After the reading of the document and the interworking of the work history information are completed, in S6630 , the second device 112 requests the server 100 to transmit the document. In S6631 , the server 100 transmits the document to the second device 112 .

S6632 to S6643 of FIGS. 66B to 66C are processes for the server 100 to link job history information to the user's calendar when editing a document, and are the same as S4817 to S4828 of FIGS. 48A to 48B. Accordingly, detailed descriptions of S6632 to S6643 of FIGS. 66B to 66C will be omitted below.

Hereinafter, an example of job history information obtained by the server 100 will be described with reference to FIGS. 67 to 68 .

67 to 68 are diagrams illustrating an example of job history information of a document according to some embodiments.

The job history information 6710 of the document shown in FIG. 67 is an example updated from the job history information 1310 of the document shown in FIG. 13 . In other words, the job history information 1310 of the document shown in FIG. 13 means the job history information 1310 generated when the device generates the document. On the other hand, the job history information 6710 of the document shown in FIG. 67 is new job history information 6720, 6730, 6740 as the device creates a document, and at least one of the devices reads and edits the generated document. means added.

Referring to FIG. 67 , the server 100 may arrange the job history information received from the second device 112 based on the name 6711 of the document.

The job history information 6810 of the document shown in FIG. 68 is an example updated from the job history information 1410 of the document shown in FIG. 14 . In other words, the job history information 1410 of the document shown in FIG. 14 means the job history information 1410 generated when the device generates the document. On the other hand, the job history information 6810 of the document shown in FIG. 68 is new job history information 6820, 6830, 6840 as the device generates a document, and at least one of the devices reads and edits the generated document. means added.

Referring to FIG. 68 , the server 100 may arrange the work history information received from the second device 112 based on the name 6811 of the work device.

69 is a diagram illustrating an example of a daily calendar displayed on a screen of a device according to some embodiments.

Referring to FIG. 69 , a daily calendar 6911 is output on the screen of the device 6910 . An indicator 6920 indicating the name of a document may be displayed on the calendar 6911 . For example, assuming that the first device 111 generates a document named 'abc.doc' on May 12, 2014, the calendar 6911 indicates 'abc.doc' in an area corresponding to May 12, 2014. An indicator 6920 may be displayed.

The device 6910 may select the indicator 6920 indicating 'abc.doc' according to the user input received through the user input unit 16510 . When the indicator 6920 indicating 'abc.doc' is selected, the device 6910 may output the job history information 6921 of the document on the screen. For example, it is said that the first device 111 stored a document named 'abc.doc' having a size of 54 KB (kilobyte) using the first program at 12:28:04 pm on May 12, 2014. Assume that 'abc.doc, text, first program, first device, May 12, 2014 12:28:04 pm, 54 KB' may be output to the work history information 3821 . Meanwhile, the device 6910 may output the job history information 3821 of the document to the screen as a separate pop-up window.

Also, an indicator 6922 capable of outputting a document to the screen of the device 6910 may be displayed in the job history information 6921 of the document. For example, when an indicator 6922 capable of outputting a document according to a user input received through the user input unit 16510 is selected, the device 6910 displays a pop-up window separate from the calendar 6911 to the first device ( 111) can be printed on the screen.

Similarly, a plurality of indicators indicating the name of a document may be displayed on one calendar 6911 . For example, assuming that the second device 112 reads a document named 'abc.doc' on May 20, 2014, indicating 'abc.doc' in an area corresponding to May 12, 2014 in the calendar 6911 An indicator 6930 may be displayed.

The device 6910 may select the indicator 6930 indicating 'abc.doc' according to the user input received through the user input unit 16510 . When the indicator 6930 indicating 'abc.doc' is selected, the device 6910 may output the job history information 6931 of the document on the screen. For example, the second device 112 reads a document named 'abc.doc' having a size of 54 KB (kilobyte) using the first program at 08:46:11 pm on May 20, 2014. It is assumed that 'abc.doc, text, first program, second device, 08:46:11 pm on May 20, 2014, 54 KB' may be output to the work history information 3831 . Meanwhile, the device 6910 may output the job history information 6931 of the document to the screen as a separate pop-up window.

Also, indicators 6932 and 6933 for outputting a document to the screen of the device 6910 may be displayed in the job history information 6931 of the document. The indicator 6932 may be an indicator indicating an original document at the time of document creation or a document prior to the current job, and the indicator 6933 may be an indicator indicating a current edited document.

The indicator 6933 indicating the edited document may be displayed to be distinguished from the indicator 6932 indicating the original document or the document before the current job. For example, in the case of the indicator 6933 of the edited document, a border line may be additionally displayed on the indicator 6932 indicating the original document or the document before the current job. When an indicator 6932 or 6933 capable of outputting a document is selected according to a user input received through the user input unit 16510 , the device 6910 displays an original document or a second device as a pop-up window separate from the calendar 6911 . The edited document can be printed on the screen.

70 is a diagram illustrating another example of a daily calendar displayed on a screen of a device according to some embodiments.

Referring to FIG. 70 , a daily calendar 7011 is output on the screen of the device 7010 . The calendar 7011 shown in FIG. 70 has the same frame as the calendar 6911 shown in FIG. Accordingly, the contents described above with reference to FIG. 69 with respect to objects that may be displayed on the calendar 3911 may be equally applied to FIG. 70 .

An indicator 7020 indicating a program used to work on a document may be displayed on the calendar 7011 . For example, assuming that the first device 111 generates a document by using the first program on May 12, 2014, an indicator ( 7020) may be displayed.

The device 7010 may select the indicator 7020 indicating the 'first program' according to the user input received through the user input unit 16510 . When the indicator 7020 indicating the 'first program' is selected, the device 7010 may output the job history information 7021 of the document on the screen. For example, it is said that the first device 111 creates a document named 'abc.doc' having a size of 54 KB (kilobyte) using the first program at 12:28:04 pm on May 12, 2014. Assume that 'abc.doc, text, first program, first device, May 12, 2014 12:28:04 pm, 54 KB' may be output to the work history information 7021 . Meanwhile, the device 7010 may output the job history information 7021 of the document to the screen as a separate pop-up window.

Also, an indicator 7022 capable of outputting a document to the screen of the device 7010 may be displayed in the job history information 7021 of the document. For example, when an indicator 7022 capable of outputting a document according to a user input received through the user input unit 16510 is selected, the device 7010 displays a pop-up window separate from the calendar 7011 to the first device ( 111) can be printed on the screen.

Similarly, a plurality of indicators indicating programs may be displayed on one calendar 7011 . For example, assuming that the second device 112 reads a document named 'abc.doc' on May 20, 2014, the calendar 7011 indicates the 'first program' in the area corresponding to May 12, 2014. An indicator 7030 may be displayed.

The device 7010 may select the indicator 7030 indicating the 'first program' according to the user input received through the user input unit 16510 . When the indicator 7030 indicating the 'first program' is selected, the device 7010 may output the job history information 7031 of the document on the screen. For example, the second device 112 reads a document named 'abc.doc' having a size of 54 KB (kilobyte) using the first program at 08:46:11 pm on May 20, 2014. It is assumed that 'abc.doc, text, first program, second device, 08:46:11 pm on May 20, 2014, 54 KB' may be output to the work history information 7031 . Meanwhile, the device 7010 may output the job history information 7031 of the document to the screen as a separate pop-up window.

Also, indicators 7032 and 7033 for outputting a document to the screen of the device 7010 may be displayed in the job history information 7031 of the document. The indicator 7032 may be an indicator indicating an original document at the time of document creation or a document prior to the current job, and the indicator 7033 may be an indicator indicating a current edited document.

The indicator 7033 indicating the edited document may be displayed to be distinguished from the indicator 7032 indicating the original document or the document before the current job. For example, in the case of the indicator 7033 of the edited document, a border line may be additionally displayed on the indicator 7032 indicating the original document or the document before the current work. When the indicator 7032 or 7033 capable of outputting a document according to a user input received through the user input unit 16510 is selected, the device 7010 displays the original document or the second device as a pop-up window separate from the calendar 7011 . The edited document can be printed on the screen.

71 is a diagram illustrating another example of a daily calendar displayed on a screen of a device according to some embodiments.

Referring to FIG. 71 , a daily calendar 7111 is output on the screen of the device 7110 . The calendar 7111 shown in FIG. 71 has the same frame as the calendar 6911 shown in FIG. Accordingly, the contents described above with reference to FIG. 69 with respect to indicators that may be displayed on the calendar 7111 may be equally applied to FIG. 71 .

An indicator 7120 indicating a device name may be displayed on the calendar 7111 . For example, assuming that the first device 111 generates a document on May 12, 2014, an indicator 7120 indicating the 'first device' may be displayed in an area corresponding to May 12, 2014 of the calendar 7111. there is.

The device 7110 may select the indicator 7120 indicating the 'first device' according to the user input received through the user input unit 16510 . When the indicator 7120 indicating the 'first device' is selected, the device 7110 may output the job history information 7121 of the document on the screen. For example, it is said that the first device 111 stored a document named 'abc.doc' having a size of 54 KB (kilobyte) using the first program at 12:28:04 pm on May 12, 2014. Assume that 'abc.doc, text, first program, first device, May 12, 2014 12:28:04 pm, 54 KB' may be output to the work history information 7121 . Meanwhile, the device 7010 may output the job history information 7121 of the document to the screen as a separate pop-up window.

Also, indicators 7122 and 7123 for outputting a document to the screen of the device 7110 may be displayed in the job history information 7121 of the document. The indicator 7122 may be an indicator indicating an original document at the time of document creation or a document prior to a current job, and the indicator 7123 may be an indicator indicating a current edited document.

The indicator 7123 indicating the edited document may be displayed to be distinguished from the indicator 7122 indicating the original document or the document before the current job. For example, in the case of the indicator 7123 of the edited document, a border line may be additionally displayed on the indicator 7122 indicating the original document or the document before the current work. When an indicator 7122 or 7123 capable of outputting a document is selected according to a user input received through the user input unit 16510 , the device 7110 displays an original document or an edited document as a pop-up window separate from the calendar 7111 . can be printed on the screen.

Similarly, a plurality of indicators indicating device names may be displayed on one calendar 7111 . For example, assuming that the second device 112 reads a document named 'abc.doc' on May 20, 2014, the calendar 7111 indicates the 'second device' in the area corresponding to May 12, 2014. An indicator 7130 may be displayed.

The device 7110 may select the indicator 7130 indicating the 'second device' according to the user input received through the user input unit 16510 . When the indicator 7130 indicating the 'second device' is selected, the device 7110 may output the job history information 7131 of the document to the screen. For example, the second device 112 reads a document named 'abc.doc' having a size of 54 KB (kilobyte) using the first program at 08:46:11 pm on May 20, 2014. It is assumed that 'abc.doc, text, first program, second device, 08:46:11 PM on May 20, 2014, 54 KB' may be output to the work history information 7131 . Meanwhile, the device 7110 may output the job history information 7131 of the document to the screen as a separate pop-up window.

In addition, indicators 7132 and 7133 for outputting a document to the screen of the device 7110 may be displayed in the job history information 7131 of the document. The indicator 7132 may be an indicator indicating an original document at the time of document creation or a document prior to the current job, and the indicator 7133 may be an indicator indicating a current edited document.

The indicator 7133 indicating the edited document may be displayed to be distinguished from the indicator 7132 indicating the original document or the document before the current job. For example, in the case of the indicator 7133 of the edited document, a border line may be additionally displayed on the indicator 7132 indicating the original document or the document before the current work. When an indicator 7132 or 7133 capable of outputting a document is selected according to a user input received through the user input unit 16510 , the device 7110 displays an original document or an edited document as a pop-up window separate from the calendar 7111 . can be printed on the screen.

72 is a diagram illustrating an example of a monthly calendar displayed on a screen of a device according to some embodiments.

Referring to FIG. 72 , a monthly calendar 7211 is output on the screen of the device 7210 . The calendar 7211 shown in FIG. 72 has the same frame as the calendar 1920 shown in FIG. 19 . Accordingly, the contents described above with reference to FIG. 19 with respect to indicators that may be displayed on the calendar 7211 may be equally applied to FIG. 72 .

An indicator 7230 indicating the name of a document may be displayed on the calendar 7211 . For example, assuming that the first device 111 generates a document named 'abc.doc' on May 12, 2014, the calendar 7211 indicates 'abc.doc' in an area corresponding to May 12, 2014. An indicator 7230 may be displayed. Similarly, assuming that the second device 112 reads a document named 'abc.doc' on May 20, 2014, an indicator indicating 'abc.doc' in the area corresponding to May 20, 2014 in the calendar 7211 7240) may be displayed.

The device 7210 may select the indicator 7230 indicating 'abc.doc' according to the user input received through the user input unit 16510 . When the indicator 7230 indicating 'abc.doc' is selected, the device 7210 may output job history information 7251 of the document on the screen.

For example, it is said that the first device 111 stored a document named 'abc.doc' having a size of 54 KB (kilobyte) using the first program at 12:28:04 pm on May 12, 2014. Assume that 'abc.doc, text, first program, first device, May 12, 2014 12:28:04 pm, 54 KB' may be output to the work history information 7251 . Meanwhile, the device 7210 may output the job history information 7251 of the document to the screen as a separate pop-up window.

Similarly, the device 7210 may select the indicator 7240 indicating 'abc.doc' according to the user input received through the user input unit 16510 . When the indicator 7240 indicating 'abc.doc' is selected, the device 7210 may output job history information 7252 of the document on the screen.

For example, the second device 112 reads a document named 'abc.doc' having a size of 54 KB (kilobyte) using the first program at 08:46:11 pm on May 20, 2014. Assume that 'abc.doc', text, first program, second device, 08:46:11 PM on May 20, 2014, 54 KB' may be output to the work history information 7252 . Meanwhile, the device 7210 may output the job history information 7252 of the document to the screen as a separate pop-up window.

Also, an indicator 7261 capable of outputting a document to the screen of the device 7210 may be displayed in the job history information 7251 of the document. For example, when an indicator 7261 capable of outputting a document according to a user input received through the user input unit 16510 is selected, the device 7210 displays a pop-up window separate from the calendar 7211 to the first device ( 111) can be printed on the screen.

Similarly, an indicator 7262 and an indicator 7272 capable of outputting a document to the screen of the device 7210 may be displayed in the job history information 7252 of the document. For example, when an indicator 7262 capable of outputting a document according to a user input received through the user input unit 16510 is selected, the device 7210 displays the original document in a pop-up window separate from the calendar 7211 . It can be printed on the screen. Also, when the indicator 7272 is selected, the device 7210 may output the edited document in a pop-up window separate from the calendar 7211 on the screen.

73 is a diagram illustrating another example of a monthly calendar displayed on a screen of a device according to some embodiments.

Referring to FIG. 73 , a monthly calendar 7311 is output on the screen of the device 7310 . The calendar 7311 shown in FIG. 73 has the same frame as the calendar 1920 shown in FIG. 19 . Accordingly, the contents described above with reference to FIG. 19 with respect to objects that may be displayed on the calendar 7311 may be equally applied to FIG. 73 .

An indicator 7330 and an indicator 7340 indicating a program used for document work may be displayed on the calendar 7311 . For example, assuming that the first device 7310 generates a document by using the first program on May 12, 2014, an indicator ( 7330) may be displayed. Similarly, assuming that the second device 112 reads the document using the first program on May 20, 2014, an indicator 7340 indicating the 'first program' in the area corresponding to May 20, 2014 in the calendar 7311 may be displayed.

The device 7310 may select the indicator 7330 indicating the 'first program' according to the user input received through the user input unit 16510 . When the indicator 7330 indicating the 'first program' is selected, the device 7310 may output the job history information 7351 of the document on the screen. For example, it is said that the first device 111 stored a document named 'abc.doc' having a size of 54 KB (kilobyte) using the first program at 12:28:04 pm on May 12, 2014. It is assumed that 'abc.doc, text, first program, first device, May 12, 2014 12:28:04 pm, 54 KB' may be output to the work history information 7351 . Meanwhile, the device 7310 may output the job history information 7351 of the document to the screen as a separate pop-up window.

Similarly, the device 7310 may select the indicator 7340 indicating the 'first program' according to the user input received through the user input unit 16510 . When the indicator 7340 indicating the 'first program' is selected, the device 7310 may output job history information 7352 of the document on the screen. For example, the second device 112 reads a document named 'abc.doc' having a size of 54 KB (kilobyte) using the first program at 08:46:11 pm on May 20, 2014. Assume that 'abc.doc', text, first program, second device, 08:46:11 PM on May 20, 2014, 54 KB' may be output to the work history information 7352 . Meanwhile, the device 7310 may output the job history information 7352 of the document to the screen as a separate pop-up window.

Also, an indicator 7361 capable of outputting a document to the screen of the device 7310 may be displayed in the job history information 7351 of the document. For example, when an indicator 7361 capable of outputting a document according to a user input received through the user input unit 16510 is selected, the device 7310 displays a pop-up window separate from the calendar 7320 to the first device ( 111) can be printed on the screen.

Similarly, an indicator 7362 and an indicator 7372 capable of outputting a document to the screen of the device 7310 may be displayed in the work history information 7352 of the document. For example, when an indicator 7362 capable of outputting a document according to a user input received through the user input unit 16510 is selected, the device 7310 displays the original document in a pop-up window separate from the calendar 7311 . It can be printed on the screen. Also, when the indicator 7372 is selected, the device 7310 may output the edited document as a pop-up window separate from the calendar 7311 on the screen.

74 is a diagram illustrating another example of a monthly calendar displayed on a screen of a device according to some embodiments.

Referring to FIG. 74 , a monthly calendar 7411 is output on the screen of the device 7410 . The calendar 7411 shown in FIG. 74 has the same frame as the calendar 1910 shown in FIG. 19 . Accordingly, the contents described above with reference to FIG. 19 with respect to objects that may be displayed on the calendar 7411 may be equally applied to FIG. 74 .

An indicator 7430 and an indicator 7440 indicating the name of the device may be displayed on the calendar 7411 . For example, assuming that the first device 111 creates a document on May 12, 2014, an indicator 7430 indicating the 'first device' may be displayed in an area corresponding to May 12, 2014 of the calendar 7411. there is. Similarly, assuming that the second device 112 reads the document on May 20, 2014, an indicator 7440 indicating the 'second device' may be displayed in the area corresponding to May 20, 2014 in the calendar 7411.

The device 7410 may select the indicator 7430 indicating the 'first device' according to the user input received through the user input unit 16510 . When the indicator 7430 indicating the 'first device' is selected, the device 7410 may output the job history information 7451 of the document to the screen. For example, it is said that the first device 111 stored a document named 'abc.doc' having a size of 54 KB (kilobyte) using the first program at 12:28:04 pm on May 12, 2014. It is assumed that 'abc.doc, text, first program, first device, May 12, 2014 12:28:04 pm, 54 KB' may be output to the work history information 7451 . Meanwhile, the device 7410 may output the job history information 7451 of the document to the screen as a separate pop-up window.

Similarly, the device 7410 may select the indicator 7440 indicating the 'second device' according to the user input received through the user input unit 16510 . When the indicator 7440 indicating the 'second device' is selected, the device 7410 may output the job history information 7452 of the document to the screen. For example, the second device 112 reads a document named 'abc.doc' having a size of 54 KB (kilobyte) using the first program at 08:46:11 pm on May 20, 2014. Assume that 'abc.doc', text, first program, second device, 08:46:11 PM on May 20, 2014, 54 KB' may be output to the work history information 7452 . Meanwhile, the device 7410 may output the job history information 7452 of the document to the screen as a separate pop-up window.

Also, an indicator 7461 capable of outputting a document to the screen of the device 7410 may be displayed in the job history information 7451 of the document. For example, when an indicator 7461 capable of outputting a document according to a user input received through the user input unit 16510 is selected, the device 7410 displays a pop-up window separate from the calendar 7420 to the first device ( 111) can be printed on the screen.

Similarly, an indicator 7462 and an indicator 7472 capable of outputting a document to the screen of the device 7410 may be displayed in the job history information 7452 of the document. For example, when an indicator 7462 capable of outputting a document according to a user input received through the user input unit 16510 is selected, the device 7410 displays the original document in a pop-up window separate from the calendar 7411. It can be printed on the screen. Also, when the indicator 7472 is selected, the device 7410 may output the edited document in a pop-up window separate from the calendar 7411 on the screen.

75 is a diagram illustrating an example of an annual calendar displayed on a screen of a device according to some embodiments.

Referring to FIG. 75 , an annual calendar 7520 is output on the screen of the device 7510 .

An indicator 7530 indicating the name of a document may be displayed on the calendar 7520 . For example, the first device 111 generates a document named 'abc.doc' on May 12, 2014, and the second device 112 creates a document named 'abc.doc' on May 14, 2014. Assuming that the second device 112 reads the same document on May 20, 2014, an indicator 7530 indicating 'abc.doc' may be displayed in the area corresponding to May 2014 in the calendar 7520. The indicator 7530 may include and display the number of work history information of the document. For example, when the first device 111 and the second device 112 generate and read 'abc.doc' three times in May as in the above example, the indicator 7530 includes the document name. '(3)', which is the number of work history information, may be displayed together with 'abc.doc'.

The device 7510 may select the indicator 7530 indicating the name of the document according to the user input received through the user input unit 16510 . When the indicator 7530 indicating the name of the document is selected, the device 7510 may output job history information 7540 of the document on the screen.

For example, the first device 111 stored a document named 'abc.doc' having a size of 54 KB (kilobyte) using the first program at 12:28:04 pm on May 12, 2014, and , the second device 112 generated a document named 'abc.doc' having a size of 105 KB using the first program at 09:11:43 am on May 14, 2014, and the second device 112 created a document named 'abc. Assume you read the same document at .20 08:46:11 PM.

At this time, when the indicator 7530 indicating 'abc.doc' is selected, the job history information 7540 includes the first job history information 7543, the second job history information 7544, and the third job history information 7545. may include. 'abc.doc, text, first program' may be displayed in the work history information 7540 .

In addition, 'first device, document generation, May 12, 2014 12:28:04 pm, 54 KB' may be output to the first job history information 7543 . In addition, 'second device, document creation, May 14, 2014, 09:11:43, 105KB' may be output to the second job history information 7544 , and the third job history information 7545 includes ' The second device, reading the document, 08:46:11 PM on May 20, 2014, 105KB' may be output. Meanwhile, the device 7510 may output the job history information 7540 of the document on the screen as a separate pop-up window.

In addition, indicators 7541 and 7542 for outputting a document to the screen of the device 7510 may be displayed in the job history information 7540 of the document. The indicator 7541 may be an indicator capable of outputting the original document of 'abc.doc' on the screen of the device. The indicator 7542 may be an indicator capable of outputting the edited document of 'abc.doc' on the screen of the device.

For example, when an indicator 7541 capable of outputting a document according to a user input received through the user input unit 16510 is selected, the device 7510 displays a pop-up window separate from the calendar 7520 to the first device ( 111) can be printed on the screen.

76 is a diagram illustrating another example of an annual calendar displayed on a screen of a device according to some embodiments.

Referring to FIG. 76 , an annual calendar 7620 is output on the screen of the device 7610 . In addition, an indicator 7630 indicating a program used for document work is displayed on the calendar 7620 . As described above with reference to FIG. 75 , the number 7640 of work history information may also be displayed in the indicator 7630 . As described above with reference to FIG. 75 , when the indicator 7630 indicating a program used for working on a document is selected, the device 7610 may output job history information 7650 of the document on the screen. In addition, when the indicator 7651 , 7652 capable of outputting a document is selected on the screen on which the work history information 7650 of the document is displayed, the device 7610 outputs the document indicated by the indicator 7651 , 7652 on the screen. can

77 is a diagram illustrating another example of an annual calendar displayed on a screen of a device according to some embodiments.

Referring to FIG. 77 , an annual calendar 7720 is output on the screen of the device 7710 . In addition, an indicator 7730 indicating a device is displayed on the calendar 7720 . As described above with reference to FIG. 75 , the number 7740 of work history information may also be displayed in the indicator 7730 .

As described above with reference to FIG. 75 , when the indicator 7730 indicating the device is selected, the device 7710 may output the execution history information 7750 of the document on the screen. For example, the second device 112 created a document named 'abc.doc' having a size of 105 KB using the first program at 09:11:43 am on May 14, 2014 and also the second device 112 Assume that , read the same document at 08:46:11 pm on May 20, 2014.

The job history information 7750 may include first job history information 7760 and second job history information 7770 . In the first job history information 7760, 'abc.doc, text, first program, document generation, May 14, 2014, 09:11:43, 105KB' may be output, and second job history information ( 7770), 'abc.doc, text, first program, document reading, May 20, 2014 08:46:11 PM, 105KB' may be output. Meanwhile, the device 7710 may output the job history information 7750 of the document to the screen as a separate pop-up window.

In addition, as described above with reference to FIG. 62 , when the indicators 7761 , 7761 , 7771 , and 7772 for outputting a document are selected on the screen on which the execution history information 7750 of the document is displayed, the device 7710 is the corresponding Documents can be printed on the screen.

78 is a diagram illustrating another example of an annual calendar displayed on a screen of a device according to some embodiments.

Referring to FIG. 78 , an annual calendar 7820 is output on the screen of the device 7810 . The annual calendar shown in FIGS. 75 to 77 includes an area in which months included in a year are displayed, but the annual calendar 7820 shown in FIG. 78 includes an area 7821 in which days included in a year are displayed. This is included. In other words, the device 7810 may variously change the format of the annual calendar and output it on the screen.

Indicators 7830 , 7840 , and 7850 may be displayed on the calendar 7820 on the date the document was performed. For example, assuming that the third device 113 generates a document named 'xyz.doc' on 2014.02.14, the calendar 7820 indicates 'xyz.doc' in an area corresponding to 2014.02.14. An indicator 7830 may be displayed.

Also, assuming that the third device 113 generates a document named 'abc.doc' on May 12, 2014, an indicator indicating 'abc.doc' in the area corresponding to May 12, 2014 in the calendar 7820 ( 7840) may be displayed.

Also, assuming that the third device 113 generates a document named 'kkk.ppt' on May 28, 2014, an indicator indicating 'kkk.ppt' in the area corresponding to May 28, 2014 in the calendar 7820 7850) may be displayed.

In order to distinguish the indicators 7830 , 7840 , and 7850 related to different files from each other, the indicators 7830 , 7840 , and 7850 may have different colors and shapes. Although it has been previously described that the third device 113 generates all of 'xyz.doc', 'abc.doc', and 'kkk.ppt', different devices may generate documents.

As described above with reference to FIG. 75 , when the indicators 7830 , 7840 , and 7850 displayed on the calendar 7820 are selected, the device 7810 outputs the job history information 7860 , 7870 , and 7880 of the document to the screen. can In addition, as described above with reference to FIG. 62 , when the indicator 7861 , 7871 , 7881 capable of outputting a document is selected on the screen on which the work history information 7860 , 7870 , 7880 of the document is displayed, the device 7810 can print the document on the screen.

79 to 80 are diagrams illustrating examples of calendars output on a screen of a device according to some embodiments.

Referring to FIG. 79 , an example of a calendar 7920 output on a screen of a device 7910 is illustrated. In FIG. 79 , it is illustrated that the monthly calendar 7920 is output on the screen of the device 7910 for convenience of explanation, but the present invention is not limited thereto.

If an operation is performed on a plurality of documents on the same date, an indicator 7930 indicating the number of documents on which the operation is performed may be displayed on the calendar 7920 . For example, if it is assumed that at least one of the devices 110 performs an operation on a total of 9 documents on 2014.01.10, the calendar 7920 performs an operation on 9 documents in an area indicating 2014.01.10 An indicator 7930 indicating that this has been performed may be displayed.

The device 7910 may select an indicator 7930 indicating the number of documents on which an operation is performed according to a user input received through the user input unit 16510 . When the indicator 7930 indicating the number of documents on which the operation is performed is selected, the device 7910 may output a list 7940 of documents on which the operation has been performed on the screen.

After the list 7940 of the documents on which the work is performed is output, when any one 7941 of the documents included in the list 7940 is selected, the device 7910 displays the work history information 7950 of the selected document. It can be printed on the screen. In the work history information 7950 of the document, indicators 7951 and 7952 for outputting the document to the screen of the device 7910 may be displayed. Here, the indicator 7951 may be an indicator indicating an original document at the time of document creation or a document prior to the current job, and the indicator 7952 may be an indicator indicating a currently edited document.

Referring to FIG. 80 , another example of the calendar 8020 output on the screen of the device 8010 is illustrated. The document list 8040 in the calendar 8020 illustrated in FIG. 80 may have a different shape from the document list 7940 in the calendar 7920 illustrated in FIG. 79 . For example, the document list 8040 , the document work history information 8050 , and the indicators 8030 , 8051 , and 8052 that can be output on the screen of the device 8010 may be output in various shapes or colors.

81 to 82 are diagrams illustrating still other examples of a calendar output on a screen of a device according to some embodiments.

Referring to FIG. 81 , an example of the calendar 8120 output on the screen of the device 8110 is illustrated. In FIG. 81 , it is illustrated that the monthly calendar 8120 is output on the screen of the device 8110 for convenience of explanation, but the present invention is not limited thereto.

If the same device performs an operation on a plurality of documents on the same date, an indicator 8030 indicating the number of documents on which the operation is performed may be displayed on the calendar 8120 . For example, if it is assumed that the first device 111 performs an operation on a total of three documents on January 11, 2014, the operation is performed on three documents in an area indicating January 11, 2014 in the calendar 8120 An indicator 8130 indicating that this has been done may be displayed.

The device 8110 may select the indicator 8130 according to a user input received through the user input unit 16510 . When the indicator 8130 is selected, the device 8110 may output a list 8140 of documents on which work is performed on the screen.

After the list 8140 of the documents on which the work is performed is output, when any one 8141 of the documents included in the list 8140 is selected, the device 8110 displays the work history information 8150 of the selected document. It can be printed on the screen. Indicators 8151 and 8152 capable of outputting a document to the screen of the device 8110 may be displayed in the work history information 8150 of the document. Here, the indicator 8151 may be an indicator indicating an original document at the time of document creation or a document prior to the current job, and the indicator 8152 may be an indicator indicating a current edited document.

Referring to FIG. 82 , another example of the calendar 8220 output on the screen of the device 8210 is illustrated. The document list 8240 in the calendar 8220 illustrated in FIG. 82 may have a different shape from the document list 8140 in the calendar 8120 illustrated in FIG. 81 . For example, the document list 8240 , the document work history information 8250 , and the indicators 8230 , 8251 , and 8252 that may be output on the screen of the device 8210 may be output in various shapes or colors.

83 is a diagram for describing an example in which a mode of a calendar is switched, according to some embodiments.

Referring to (a) of FIG. 83 , an example of the first mode calendar 8320 output on the screen of the device 8310 is illustrated. Here, the first mode calendar 8320 may be linked with information related to the user's daily life. For example, the first mode calendar 8320 may be linked with information about a user's schedule or plan. Also, the first mode calendar 8320 may be linked with history information in which a user uses a function of the device 8310 . For example, the first mode calendar 8320 includes a history of a user making a call using the device 8310 , a history of taking pictures using a camera provided in the device 8310 , and a memo program installed in the device 8310 . It may be linked to a history of creating a memo using , a history of sending and receiving messages or e-mails using the device 8310, a history of using an SNS service using an SNS program installed in the device 8310, and the like.

Referring to (b) of FIG. 83 , an example of the second mode calendar 8330 output on the screen of the device 8310 is illustrated. Here, the second mode calendar 8330 may be linked with work history information of a document.

Indicators 8340 and 8350 for switching modes of the calendars 8320 and 8330 may be displayed on the calendars 8320 and 8330 output to the device 8310 . For example, an indicator 8340 for requesting output of the first mode calendar 8320 and an indicator 8350 for requesting output of the second mode calendar 8330 may be displayed on the screen of the device 8310 . there is.

Also, schedule information related to job history information displayed on the second mode calendar 8330 may be displayed on the first mode calendar 8320 output to the device 8310 . For example, suppose that a user worked on the document '2013 Performance Report.doc' on December 23, 2013, and a meeting schedule related to the document '2013 Performance Report.doc' exists on January 3, 2014. do. In this case, in the field on January 2, 2014 on the first mode calendar 8320, an indicator indicating that '2013 performance report.doc' is to be reviewed may be displayed.

As described above, since the work history information of the document may be linked to the user's calendar, the user may intuitively understand the work history of the document. In addition, a document can be displayed on the screen of the device through an indicator (eg, an icon) displayed on the calendar, so that the user can easily view or edit the document.

In addition, since it is possible to switch between a calendar displaying a user's personal schedule and the like and a calendar displaying a document work history of the user, user convenience can be improved.

Hereinafter, with reference to FIGS. 84 to 86 , when the users of the devices 110 are different, and the devices 110 perform a document job, the server 100 stores the job history information in the user's calendar. An example of interworking will be described.

84 is a diagram for explaining an example in which the server links work history information to a user's calendar when users of devices are different from each other and devices perform a document job, according to some embodiments.

Referring to FIG. 84 , the system 1 includes a server 100 and devices 110 . Here, the devices 110 refer to devices of different users. For example, the first device 111 is the device of the first user 120 , the second device 112 is the device of the second user 121 , and the N-th device 114 is the device of the M-th user 122 . It may be a device.

At least one of the devices 110 performs a document job, and transmits the job history information 130 of the document to the server 100 . For example, the first device 111 performs a document job, and transmits the job history information 130 of the document to the server 100 . In the same manner, the second device 112 to the N-th device 114 performs a document job, and transmits the job history information 130 of the document to the server 100 .

The server 100 links the job history information 130 transmitted from the devices 110 to the user's calendar. Then, the server 100 transmits the information 140 to be displayed on the calendar to the devices 110 . Here, the information 140 to be displayed on the calendar means information to be displayed on the output calendar when the calendar is output on the screen of the device. For example, the information 140 to be displayed on the calendar may include job history information to be output on the screen of the device when an indicator to be displayed on the calendar or an indicator displayed on the calendar is selected.

In this case, the server 100 may transmit the information 140 to be displayed on the calendar only to a device that has requested transmission of the information 140 to be displayed on the calendar among the devices 110 . For example, the first device 111 executes a program for outputting a calendar and authenticates that the first user is the first user based on the user account input through the user input unit 16510, thereby providing the server 100 with the It is possible to request transmission of the information 140 to be displayed on the calendar.

Meanwhile, even if there is no request from the first device 111 , the server 100 may automatically transmit (eg, push) the information 140 to be displayed on the calendar to the first device 111 . . For example, if there is a history in which the first device 111 previously requested transmission of the information 140 to be displayed in the calendar of the first user, the server 100 may later request from the first device 111 . Even if there is no information, the information 140 to be displayed on the calendar of the first user may be automatically transmitted.

Hereinafter, an example in which the server 100 links job history information to a user's calendar will be described with reference to FIG. 85 .

85 is a flowchart illustrating an example in which a server links job history information to a user's calendar, according to some embodiments.

In S8510, the server 100 receives the work history information of the document worked by the plurality of users from the devices of the plurality of users. In other words, the devices of at least two or more users each perform a document job and transmit job history information to the server 100 . In this case, as described above with reference to FIG. 1 , that devices may transmit only a part of the job history information to the server 100 .

In S8520, the server 100 links the received job history information to at least one calendar among a plurality of users by using time information included in the received job history information. Here, the time information means information indicating the time the device worked on the document. For example, assuming that the first device 111 of the first user 120 creates a document called 'abc.doc' at 12:28:04 pm on May 12, 2014, the server 100 sends the document 'abc.doc' to the second user ( 121) generates an indicator to be displayed on 2014.05.12 in the calendar, and when the indicator displayed on 2014.05.12 is selected, job history information to be output on the screen of the second device 112 of the second user 121 can be determined. there is. In this case, as described above with reference to FIG. 1 , that the server 100 may link only a part of the job history information received from the devices to the user's calendar.

Hereinafter, referring to FIG. 86 , when the first device 111 of the first user 120 and the second device 112 of the second user 121 work on a document, the server 100 is the first user An example of linking job history information to the calendar of

86 is a flowchart illustrating an example in which a server links job history information to a calendar of a first user when the first device and the second device perform a document job, according to some embodiments.

In FIG. 86 , for convenience of explanation, the first device 111 and the second device 112 are illustrated as working on a document, but the present invention is not limited thereto. In other words, there is no limit to the number of devices working on documents. If it is assumed that there is only one device for working with a document, all operations of the second device 112 to be described below may be performed by the first device 111 . In addition, assuming that the number of devices for working with a document is N (N is a plurality of 3 or more), the operation of the second device 112 to be described below is performed in at least one of the third device 113 to the Nth device. can be

In S8610, the first device 111 works on the document. For example, the first device 111 may execute a program used for working with a document and work with the document using the program. For example, the program used for document work may be an MS OFFICE WORD program for Windows operating system (OS) installed in the first device 111 or a PAGE program of MAC OS.

If it is assumed that the document that the first device 111 works with is 'abc.doc' and the program used to create, view, or edit 'abc.doc' is the first program, the first device 111 is The first program may be executed, and 'abc.doc' may be created, viewed, or edited.

In S8611 , the first device 111 transmits the job history information of the document to the server 100 . For example, the first device 111 may transmit work history information of the document to the server 100 when the execution of a program used for document work is terminated or the document is stored. For example, the first device 111 may transmit the job history information of 'abc.doc' to the server 100 when storing 'abc.doc' or ending execution of the first program.

In S8612, the second device 112 works on the document. For example, the first device 111 may execute a program used for working with a document and work with the document using the program. If it is assumed that the document to be worked by the second device 112 is 'abcd.xls' and the program used to create, view, or edit 'abcd.xls' is the second program, the second device 112 is Execute the second program and create, view, or edit 'abcd.xls'.

In S8613 , the second device 112 transmits the job history information of the document to the server 100 . For example, the second device 112 may transmit the work history information of the document to the server 100 when the execution of the program used for the document work is finished or the document is stored. For example, the second device 112 may transmit the job history information of 'abcd.xls' to the server 100 at the time of storing 'abcd.xls' or ending execution of the second program.

In S8615, the server 100 links the work history information to the user's calendar by using the time information included in the work history information received from the first device and the second device. For example, the first device 111 stores 'abc.doc' on 2014.05.18 at 08:01:42 am, and the second device 112 stores 'abcd.xls' on 2014.05.20 at 14:29 pm. Assuming that it is stored at :00, the server 100 may generate a first indicator to be displayed in an area corresponding to 2014.05.18 in the calendar, and generate a second indicator to be displayed in an area corresponding to 2014.05.20. .

In S8616 , the first device 111 requests the server 100 to transmit information to be displayed on the calendar. For example, the first device 111 may request the server 100 to transmit job history information to be output on the screen of the device when an indicator to be displayed on the calendar or an indicator displayed on the calendar is selected. For example, the first device 111 may request transmission of the work history information to be output on the screen of the device when the first indicator, the second indicator, and the first indicator and the second indicator are selected.

In S8617 , the server 100 transmits information to be displayed on the calendar to the first device 111 .

In S8618, the first device 111 outputs the calendar on the screen. For example, the first device 111 may output a calendar in which the first indicator and the second indicator transmitted from the server 100 are displayed on the screen.

In S8619 , the second device 112 requests the server 100 to transmit information to be displayed on the calendar. For example, the second device 112 may request the server 100 to transmit job history information to be output on the screen of the device when an indicator to be displayed on the calendar or an indicator displayed on the calendar is selected. For example, the second device 112 may request transmission of the work history information to be output on the screen of the device when the first indicator, the second indicator, and the first indicator and the second indicator are selected.

In S8620 , the server 100 transmits information to be displayed on the calendar to the second device 112 .

In S8621, the second device 112 outputs the calendar on the screen. For example, the first device 111 may output a calendar in which the first indicator and the second indicator transmitted from the server 100 are displayed on the screen.

Hereinafter, with reference to FIGS. 87 to 98 , when the devices 110 jointly author a document, an example in which the server 100 links job history information to a user's calendar will be described.

87 is a diagram for describing an example in which a server links work history information to a user's calendar when devices perform joint authoring of a document according to some embodiments.

Referring to FIG. 87 , the system 1 includes a server 100 , a first device 111 , a second device 112 , and an Nth device 114 . Here, each of the devices 110 may correspond to devices used by the first user 120 , the second user 121 , and the M-th user 122 . Alternatively, the devices 110 may correspond to devices used by the same user (eg, the first user 120 ). That is, the number of users using the devices 110 is not limited by any one.

The first device 111 generates a first document by using a program installed in the first device 111 . In addition, the second device 112 generates a second document by using a program installed in the second device 112 , and the N-th device 114 uses the program installed in the N-th device 114 to generate an N-th document. create Here, the programs installed in the devices 110 may correspond to a word program, an Excel program, a power point program, and the like.

Each of the devices 110 transmits information 8730 about the generated document to the server 100 . For example, the first device 111 transmits information about the generated first document to the server 100 , and the second device 112 transmits information about the generated second document to the server 100 . and the N-th device 114 transmits information about the generated N-th document to the server 100 .

In this way, the first device 111 to the Nth device 114 may perform cooperative authoring of the document by transmitting the information 8730 about the generated documents to the server 100 .

The joint authoring of a document refers to an act of jointly generating a single document 8701 by several devices 110 . In other words, joint authoring of a document means that contents to be included in a single document 8701 are generated by a plurality of devices 110 .

For example, when joint authoring of a document is performed, some of the contents to be included in the single document 8701 may be contents included in the first document generated by the first device 111 , and the other partial contents may be included in the first document generated by the first device 111 . may be content included in the second document generated by the second device 112 .

The server 100 generates a single document 8701 that is a result of joint authoring by combining the first to Nth documents received from the devices 110 ( 8710 ) ( 8720 ). Accordingly, the contents of the single document 8701 may include the contents of the first document, the contents of the second document, and the contents of the Nth document.

When the single document 8701 is generated, the server 100 may transmit generation history information of the single document 8701 to each of the devices 110 participating in the joint authoring of the single document 8701 . Then, the server 100 transmits information 8740 to be displayed on the calendar to the devices 110 . Here, the information 8740 to be displayed on the calendar means information to be displayed on the output calendar when the calendar is output on the screen of the device. For example, the information 8740 to be displayed on the calendar may include job history information to be output on the screen of the device when an indicator to be displayed on the calendar or an indicator displayed on the calendar is selected. Here, the job history information may include generation history information of a single document 8701 .

In this case, the server 100 may transmit the information 8740 to be displayed on the calendar only to a device that has requested transmission of the information 8740 to be displayed on the calendar among the devices 110 . For example, the first device 111 executes a program for outputting a calendar, and authenticates that it is the first user 120 based on a user account input through the user input unit 16510 , thereby providing the first device to the server 100 . 1 It is possible to request transmission of information 8740 to be displayed on the calendar of the user 120 .

Meanwhile, even if there is no request from the first device 111 , the server 100 may automatically transmit (eg, push) the information 8740 to be displayed on the calendar to the first device 111 . . For example, if there is a history in which the first device 111 previously requested transmission of information 8740 to be displayed on the calendar of the first user 120 , the server 100 may then Even if there is no request from , the information 8740 to be displayed on the calendar of the first user 120 may be automatically transmitted.

88 is a flowchart illustrating an example in which a server links job history information to a user's calendar, according to some embodiments.

In S8801 , the server 100 receives documents generated by each of the plurality of devices 110 and job history information of each of the documents from the plurality of devices 110 . For example, the server 100 may receive a first document, a second document, and an N-th document from each of the devices 110 , and the server 100 may also receive a first document, a second document, and an N-th document from each of the devices 110 . It is possible to receive job history information of each of the document, the second document, and the Nth document. In this case, as described above with reference to FIG. 1 , the devices 100 may transmit only a part of the job history information to the server 100 .

In S8802, the server 100 generates a final document based on the connection relationship of the received documents. Here, the final document may correspond to the single document 8701 described in FIG. 87 . As will be described later, the connection relationship between documents refers to an order in which seed documents to be combined into a final document are linked, and may include, for example, an order of a table of contents and an order of a storage date and time.

In S8803, the server 100 links the received job history information to the user's calendar by using the time information included in the received job history information. Here, the time information means information indicating the time the device worked on the document. For example, the first device 111 reads a document called 'abc.doc' on 2014.05.12. Assume that it is created at 12:28:04 pm, the server 100 generates an indicator to be displayed on 2014.05.12. in the user's calendar of the first device 111, and the indicator displayed on 2014.05.12. is selected. Accordingly, it is possible to determine the job history information to be output on the screen of the first device 111 . In this case, as described above with reference to FIG. 1 , that the server 100 may link only a part of the job history information received from the devices 110 to the user's calendar.

Hereinafter, with reference to FIGS. 89a to 89b, when the first device 111 and the second device 112 perform joint authoring of a document, the server 100 links the work history information to the user's calendar An example is explained.

89A to 89B are flowcharts illustrating an example in which a server links job history information to a user's calendar when a first device and a second device jointly author a document, according to some embodiments.

Although only two of the first device 111 and the second device 112 are illustrated in FIGS. 89A to 89B for convenience of description, the number of devices is not limited. If it is assumed that the number of devices is N (N is a plurality of 3 or more), the operation of the first device 111 or the operation of the second device 112, which will be described below, is the third device 113 to the N-th device. It may be performed in at least one of

In S8910, the first device 111 executes a program for generating a document. Here, the program for generating a document includes a program for generating a text document or a program for generating a multimedia document. For example, a program that creates a document may be a program included in MS-OFFICE.

In S8911, the second device 112 executes a program for generating a document.

In S8912, the first device 111 generates a first document and stores the generated first document.

In S8913, the second device 112 generates a second document and stores the generated second document.

In S8914 , the first device 111 transmits the first document and job history information of the first document to the server 100 . For example, the first device 111 may transmit the job history information of the first document to the server 100 at the time of storing the first document. The work history information of the first document means information generated when the first device 111 generates and stores the first document. For example, the job history information may include the title of the document on which the job was performed, the type of the document, the time the document job was performed, the name of the device performing the document job, the user of the device, the program used for the document job, the size of the document, It can include the type of work. In this case, it is assumed that the user of the first device 111 is logged in to the server 100 . In addition, examples in which the first device 111 transmits job history information of a document to the server 100 are the same as described above with reference to step S411 of FIG. 4 .

In S8915 , the second device 112 transmits the second document and job history information of the second document to the server 100 . For example, the second device 112 may transmit the job history information of the second document to the server 100 at the time of storing the second document. In this case, it is assumed that the user of the second device 112 is logged in to the server 100 . In addition, examples in which the second device 112 transmits the job history information of the document to the server 100 are the same as described above with reference to step S411 of FIG. 4 .

Meanwhile, the order of S8910 to S8915 is only arbitrarily designated for convenience of description, and the order of S8910 to S8915 may be variously changed. For example, after the second device 112 executes a program for generating a document (S8911), the first device 111 may execute a program for generating a document (S8910).

In S8916, the server 100 stores the first document and the second document.

In S8917, the server 100 determines a connection relationship between the first document and the second document. Here, the linking relationship between the first document and the second document means the order in which the first document and the second document are linked to combine them into a final document. For example, the storage date and time of the first document and the storage date and time of the second document precede or follow.

In S8918, the server 100 generates a final document by combining the first document and the second document according to the determined connection relationship.

In S8919, the server 100 stores the final document.

In S8920 , the server 100 links the job history information to the calendar using time information included in the job history information transmitted from the first device 111 and the second device 112 .

In S8921 , the first device 111 requests the server 100 to transmit information to be displayed on the calendar. For example, the first device 111 may request the server 100 to transmit information to be displayed on the calendar after executing the calendar output program installed in the first device 111 and authenticating the user. .

In S8922 , the second device 112 requests the server 100 to transmit information to be displayed on the calendar. For example, the second device 112 may request the server 100 to transmit information to be displayed on the calendar after executing the calendar output program installed in the second device 112 and authenticating the user. .

In S8923 , the server 100 transmits information to be displayed on the calendar to the first device 111 .

In S8924 , the server 100 transmits information to be displayed on the calendar to the second device 112 .

Meanwhile, the order of S8921 to S8924 is only arbitrarily designated for convenience of description, and the order of S8921 to S8924 may be variously changed.

In FIG. 89b, when each of the first device 111 and the second device 112 requests the server 100 to transmit information to be displayed on the calendar in S8921 and S8922, the server 100 sends the information to the calendar in S8923 and S8924. Although it has been illustrated that information to be displayed is transmitted to each of the first device 111 and the second device 112 , the present invention is not limited thereto. For example, even if there is no transmission request from the first device 111 or the second device 112, the server 100 transmits the information to be displayed on the calendar to the first device 111 or the second device 112 ( For example, it may be pushed.

In S8925, the first device 111 outputs the calendar on the screen.

In S8926, the second device 112 outputs the calendar on the screen.

90 is a diagram for describing an example of generating a document in a first device and a second device according to some embodiments.

The first device 111 executes a program 9001 for generating a document. For example, the program 9001 for generating a document may be an MS OFFICE WORD program for a Windows operating system (OS) installed in the first device 111 or a PAGE program of a MAC OS.

The user may write texts by using the program 9001 executed in the first device 111 . For example, the first device 111 may generate some contents of the patent specification having the invention title of “METHOD FOR CONTROLLING APPLICATION” written by the user through the program 9001 . When the generation of the patent specification is completed, the first device 111 may store a document having a file name of “draft specification 1.doc”. Here, the storage date and time of the document of “draft specification 1.doc” is, for example, “2014. 05. 14, 09:11:43 AM”.

Meanwhile, if the second device 112 is described, the second device 112 executes a program 9002 installed in the second device 112 for generating a document. The program 9002 for generating a document may be, for example, an MS OFFICE WORD application for a mobile operating system (OS) installed on the second device 112 . That is, in FIG. 90 , it is assumed that the second device 112 is a mobile device, and the program 9002 installed in the second device 112 corresponds to the mobile version of the program 9001 installed in the first device 112 . can be However, if the second device 112 is a PC, the program 9002 installed in the second device 112 may also be an MS OFFICE WORD program for Windows OS or a PAGE program for MAC OS.

The user may write texts by using the program 9002 executed in the second device 112 . For example, the second device 112 may generate claims in a patent specification written by a user via the program 9002 . When the generation of claims of the patent specification is completed, the second device 112 may store a document having a file name of “draft specification 2.doc”. Here, the storage date and time of the document of “draft specification 2.doc” is, for example, “2014. 05. 20, PM 08:46:11”.

91 is a diagram for explaining an example of transmitting documents generated by a first device and a second device and job history information of documents to a server, according to some embodiments.

As described above with reference to FIG. 90, the first device 111 stores the first document 9101 “draft specification 1.doc” at the storage date “2014. 05. 14, 09:11:43”. Then, the second device 112 stores the second document 9102 “draft specification 2.doc” date and time “2014. 05. 20, PM 08:46:11”.

The first document 9101 “draft specification 1.doc” and the second document 9102 “draft specification 2.doc” are documents generated for joint authoring of the first device 111 and the second device 112 . .

In order to perform joint authoring by combining documents, the first device 111 provides work history information of the first document 9101 “draft specification 1.doc” and the first document 9101 “draft specification 1.doc” 9103 is transmitted to the server 100, and the second device 112 has work history information 9104 of the second document 9102 “draft specification 2.doc”, and the second document “draft specification 2.doc” ) to the server 100 .

Here, the work history information 9103 of the first document 9101 “draft specification 1.doc” is the storage date “2014. 05. 14, AM 09:11:43”, device name, document creator, table of contents information of the document, etc. may be included. And, the work history information 9104 of the second document 9102 “draft specification 2.doc” is the storage date and time “2014. 05. 20, PM 08:46:11”, device name, document creator, and table of contents information of the document may be included.

The server 100 transmits from the first device 111, the first document 9101 “draft specification 1.doc”, and the work history information 9103 of the first document 9101 “draft specification 1.doc” and stores the work history information 9104 of the second document 9102 “draft specification 2.doc”, and the second document “draft specification 2.doc”, transmitted from the second device 112 .

Meanwhile, as described above with reference to FIG. 7 that encryption may be additionally performed on the job history information of a document requiring a high degree of security and transmitted to the server 100 .

92 is a diagram for explaining an example of a process in which documents are combined by joint authoring of devices according to some embodiments.

The first device 111 , the second device 112 , and the Nth device 114 are installed in each of the first device 111 , the second device 112 and the Nth device 114 , a program for generating a document Each of them creates a document for joint authoring using Specifically, the first device 111 stores the date “2014. <2014. saved on 05. 14, AM 09:11:43”. It is possible to create a document 9201 about the contents of 02. 14 sales history>, and the second device 112 stores the storage date “2014. <2014. saved on 05. 12, 12:28:04 PM. It is possible to create a document 9202 related to the contents of the sales history of 05. 12>, and the N-th device 114 stores the storage date “2014. <2014. saved on 05. 28, 08:21:11” A document 9203 relating to the contents of sales details of 05. 28> may be generated.

The first device 111 , the second device 112 , and the N-th device 114 transmit the generated documents 9201 , 9202 , and 9203 to the server 100 , respectively.

The server 100 determines the connection relationship of the documents 9201 , 9202 , and 9203 . In FIG. 92, the connection relationship will be described based on the storage date and time of the documents 9201, 9202, and 9203.

The document 9201 is first compared with the other documents 9202 and 9203, the storage date “2014. Since it is stored in the first device 111 at 05. 14, 09:11:43”, it has the first priority. The document 9202 has a storage date “2014. Since it is stored in the second device 112 at 05. 12, PM 12:28:04”, it has the second priority. Finally, the document 9203 has a storage date “2014. Since it is stored in the N-th device 114 at 05. 28, PM 08:21:11”, it has an n-th priority (n is a natural number). Accordingly, the server 100 may determine that the connection relation between the documents 9201 , 9202 and 9203 is the order of the document 9201 , the document 9202 , and the document 9203 .

The server 100 generates a final document 9210 as a result of joint authoring of the first device 111 , the second device 112 , and the N-th device 114 . Specifically, the server 100 may generate the final document 9210 by combining the documents 9201 , 9202 , and 9203 using the connection relationship determined for the documents 9201 , 9202 , and 9203 . That is, the server 100 processes documents 9201, 9202, and 9203 in the order of a document 9201 having a first priority, a document 9202 having a second priority, and a document 9203 having an n-th priority. By combining the contents of , a final document 9210 can be generated.

After all, the server 100, by joint authoring, <2014. Contents of sales breakdown of 02. 14>, <2014. Contents of sales of 05. 12> and <2014. A final document 9210 in which the contents of 05. 28 sales history> are sequentially combined may be generated.

93 is a diagram for explaining another example of a process in which documents are combined by joint authoring of devices according to some embodiments.

The first device 111 , the second device 112 , and the Nth device 114 are installed in each of the first device 111 , the second device 112 and the Nth device 114 , a program for generating a document Each of them creates a document for joint authoring using In FIG. 93 , a case in which the first device 111 , the second device 112 , and the Nth device 114 jointly author the document of the patent specification will be described as an example. In general, the order of the table of contents is determined in the patent specification. For example, the order of the large table of contents of the patent specification is known to be “BACKGROUND”, “SUMMARY”, ..., “DETAILED DESCRIPTION”, ..., “WHAT IS CLAIMED IS:”, so we assume this .

The first device 111 may generate a document 9301 “draft patent specification 1.doc” regarding the contents of “BACKGROUND” and “SUMMARY” of the patent specification, and the second device 112 may generate a “draft patent specification 1.doc” of the patent specification. DETAILED DESCRIPTION” may generate a document 9302 “draft patent specification 2.doc”, and the N-th device 114 may generate a document 9303 regarding the contents of “WHAT IS CLAIMED IS:” of the patent specification. “draft patent specification 3.doc” can be created.

The first device 111 , the second device 112 , and the Nth device 114 transmit the generated documents 9301 , 9302 , and 9303 to the server 100 , respectively.

The server 100 determines the connection relationship of the documents 9301 , 9302 and 9303 . In FIG. 93 , the connection relationship will be described based on the table of contents included in the documents 9301 , 9302 and 9303 .

The document 9301 has the first priority because it includes the contents of “BACKGROUND” and “SUMMARY”, which are the most advanced table of contents compared to other documents 9302 and 9303 . Since the document 9302 contains the contents of “DETAILED DESCRIPTION”, which is the table of contents of the next order, it has the second priority. Finally, the document 9303 has the nth priority because it includes the contents of “WHAT IS CLAIMED IS:”, which is the table of contents in the next order. Accordingly, the server 100 may determine that the connection relationship of the documents 9301 , 9302 and 9303 is the order of the document 9301 , the document 9302 , and the document 9303 .

The server 100 generates a final document 9310 as a result of joint authoring of the first device 111 , the second device 112 , and the N-th device 114 . Specifically, the server 100 may generate the final document 9310 by combining the documents 9301 , 9302 and 9303 using the connection relationship determined for the documents 9301 , 9302 and 9303 . That is, the server 100 sends the documents 9301, 9302, and 9303 with the first priority to the document 9301, the document 9302 with the second priority, and the document 9303 with the nth priority. By combining the contents of , a final document 9310 can be created.

After all, the server 100 is a patent specification in which the contents of “BACKGROUND”, “SUMMARY”, ..., “DETAILED DESCRIPTION”, ..., “WHAT IS CLAIMED IS:” are sequentially combined by joint authoring. A final document 9210 of .

94A to 94B are flowcharts illustrating another example in which a server links job history information to a user's calendar when a first device and a second device jointly author a document, according to some embodiments.

Although only two of the first device 111 and the second device 112 are illustrated in FIGS. 94A to 94B for convenience of description, the number of devices is not limited. If it is assumed that the number of devices is N (N is a plurality of 3 or more), the operation of the first device 111 or the operation of the second device 112, which will be described below, is the third device 113 to the N-th device. It may be performed in at least one of

In S9400, the first device 111 executes a program for generating a document. Here, the program for generating a document includes a program for generating a text document or a program for generating a multimedia document. For example, a program that creates a document may be a program included in MS-OFFICE.

In S9401, the first device 111 generates a first document and stores the generated first document.

In S9402 , the first device 111 transmits the first document and job history information of the first document to the server 100 . For example, the first device 111 may transmit the job history information of the first document to the server 100 at the time of storing the first document. The work history information of the first document means information generated when the first device 111 generates and stores the first document. For example, the job history information may include the title of the document on which the job was performed, the type of the document, the time the document job was performed, the name of the device performing the document job, the user of the device, the program used for the document job, the size of the document, It can include the type of work. In this case, it is assumed that the user of the first device 111 is logged in to the server 100 . In addition, examples in which the first device 111 transmits job history information of a document to the server 100 are the same as described above with reference to step S411 of FIG. 4 .

In S9403 , the server 100 links the job history information to the calendar using time information included in the job history information transmitted from the first device 111 .

In S9404, the server 100 stores the first document.

In S9405, the second device 112 executes a program for generating a document.

In S9406, the second device 112 requests the server 100 to transmit the first document.

In S9407 , the server 100 transmits the first document to the second device 112 .

In S9408, the second device 112 generates a second document based on the first document, and stores the generated second document.

In S9409 , the second device 112 transmits the second document and job history information of the second document to the server 100 . For example, the second device 112 may transmit the job history information of the second document to the server 100 at the time of storing the second document. The work history information of the second document refers to information generated as the second device 112 creates and stores the second document. In this case, it is assumed that the user of the second device 112 is logged in to the server 100 . In addition, examples in which the second device 112 transmits the job history information of the document to the server 100 are the same as described above with reference to step S411 of FIG. 4 .

In S9410, the server 100 stores the second document.

In S9411 , the server 100 links the job history information to the calendar using time information included in the job history information transmitted from the second device 112 .

In S9412, the server 100 determines a connection relationship between the first document and the second document. Here, the linking relationship between the first document and the second document means the order in which the first document and the second document are linked to combine them into a final document. For example, the storage date and time of the first document and the storage date and time of the second document precede or follow.

In S9413, the server 100 generates a final document by combining the first document and the second document according to the determined connection relationship.

In S9414, the server 100 stores the final document.

In S9415 , the first device 111 requests the server 100 to transmit information to be displayed on the calendar. For example, the first device 111 may request the server 100 to transmit information to be displayed on the calendar after executing the calendar output program installed in the first device 111 and authenticating the user. .

In S9416 , the second device 112 requests the server 100 to transmit information to be displayed on the calendar. For example, the second device 112 may request the server 100 to transmit information to be displayed on the calendar after executing the calendar output program installed in the second device 112 and authenticating the user. .

In S9417 , the server 100 transmits information to be displayed on the calendar to the first device 111 .

In S9418 , the server 100 transmits information to be displayed on the calendar to the second device 112 .

The order of S9415 to S9418 is only arbitrarily designated for convenience of description, and the order of S9415 to S9418 may be variously changed.

In FIG. 94b, when each of the first device 111 and the second device 112 requests the server 100 to transmit information to be displayed on the calendar in S9415 to S9416, the server 100 sends the information to the calendar in S9417 to S9418. Although it has been illustrated that information to be displayed is transmitted to each of the first device 111 and the second device 112 , the present invention is not limited thereto. For example, even if there is no transmission request from the first device 111 or the second device 112, the server 100 transmits the information to be displayed on the calendar to the first device 111 or the second device 112 ( For example, it may be pushed.

In S9419, the first device 111 outputs the calendar on the screen.

In S9420, the second device 112 outputs the calendar on the screen.

95 is a diagram for explaining another example of a process in which documents are combined by joint authoring of devices according to some embodiments.

The first device 111 , the second device 112 , and the Nth device 114 are installed in each of the first device 111 , the second device 112 and the Nth device 114 , a program for generating a document Each of them creates a document for joint authoring using In FIG. 95 , a case in which the first device 111 , the second device 112 , and the N-th device 114 jointly author a meeting will be described as an example. Also, in FIG. 95 , it is assumed that the order of the table of contents of the minutes is designated in the order of <Meeting Purpose>, <Meeting Preparations> 9502, and <Meeting Discussion Contents> 9503. Furthermore, it is assumed that the second device 112 is a device used by the president of the company, the N-th device 114 is a device used by a manager of the company, and the first device 111 is a device used by an employee of the company.

In order to hold a meeting for <meeting purpose> of a specific topic, the president may generate a document 9501 listing the table of contents of the meeting minutes using the second device 112 owned by the president.

The document 9501 generated by the second device 112 may be transmitted to the server 100 . For example, as described above with reference to S9400 to S9407 of FIG. 94A , the document 9501 is transmitted from the second device 112 through the server 100 to the Nth device 114 owned by the manager and the second device owned by the employee. 1 may be transmitted to the device 111 .

If the <meeting purpose> is decided by the president, the contents to be included in the other items of the meeting minutes <meeting preparation> (9502) and <meeting discussion content> (9503) can be prepared by the subordinates of the president.

When the document 9501 is transmitted to the N-th device 114 owned by the manager through the server 100 , the manager uses the N-th device 114 to obtain a document 9504 related to <Preparations for a meeting> 9502 ) can be created. In addition, when the document 9501 is transmitted to the first device 111 owned by the employee through the server 100, the employee uses the first device 111 to use the document ( 9505) can be created.

The first device 111 and the N-th device 114 transmit the generated documents 9504 and 9505 to the server 100 , respectively.

The server 100 determines the connection relationship of the documents 9501 , 9504 and 9505 . In FIG. 95 , the connection relationship will be described based on the table of contents included in the documents 9501 , 9504 and 9505 .

The document 9501 has the first priority because it includes the contents of <Meeting Purpose>, which is the most advanced table of contents compared to other documents 9504 and 9505 . The document 9504 has the second priority because it contains the contents of <Preparation for the meeting> 9502, which is the table of contents of the next order. Finally, the document 9505 has the nth priority because it includes the contents of <Meeting Discussion> 9503, which is a table of contents in the next order. Accordingly, the server 100 may determine that the connection relation of the documents 9501 , 9504 and 9505 is the order of the document 9501 , the document 9504 , and the document 9505 .

The server 100 generates a final document 9510 as a result of joint authoring of the first device 111 , the second device 112 , and the N-th device 114 . Specifically, the server 100 may generate the final document 9510 by combining the documents 9501 , 9504 and 9505 using the connection relationship determined for the documents 9501 , 9504 and 9505 . That is, the server 100 sends documents 9501, 9504, and 9505 with a first priority to a document 9501, a document with a second priority 9504, and a document with an nth priority 9505 in the order. By combining the contents of , a final document 9510 can be created.

After all, the server 100 is, by joint authoring, the final document 9510 of the meeting minutes in which the contents of <Meeting Purpose>, <Meeting Preparations> 9502, and <Meeting Discussion Contents> 9503 are sequentially combined. can create

Meanwhile, the server 100 may determine that the connection relationship between the documents 9501 , 9504 and 9505 is based on the title of the author who generated the documents 9501 , 9504 and 9505 .

Specifically, the document 9501 has the first priority since it was created by the president who is the highest rank compared to the other documents 9504 and 9505 . Since the document 9504 was created by a manager who is the next in rank, it has the second priority. Finally, document 9505 has the nth priority because it was created by the employee who is the next in rank. Accordingly, the server 100 may determine that the connection relation of the documents 9501 , 9504 and 9505 is the order of the document 9501 , the document 9504 , and the document 9505 . Accordingly, the server 100 processes the documents 9501, 9504, and 9505 in the order of the document having the first priority (9501), the document having the second priority (9504), and the document having the nth priority (9505). ), a final document 9510 can be created.

96 is a view for explaining an example of generating a final document by joint authoring of the first device, the second device, and the Nth device according to some embodiments.

In order to perform joint authoring, the first device 111 transmits a first document 9601 “draft 1.doc” to the server 100, and the second device 112 sends a second document 9602 “draft” 2.doc” to the server 100 , and the N-th device 114 transmits an N-th document 9603 “draft N.doc” to the server 100 .

The server 100 determines a connection relationship between the first document 9601 to the Nth document 9603 . Here, the connection relationship between the first document 9601 to the Nth document 9603 means the order in which the first document 9601 to the Nth document 9603 are connected in order to combine them into the final document 9610, It has already been described in the above examples.

The server 100 generates a final document 9610 by combining the first document 9601 to the Nth document 9603 according to the determined connection relationship, and stores the generated final document 9610 .

97 is a diagram illustrating an example of displaying a history of documents generated by joint authoring in a monthly calendar displayed on a screen of a device according to some embodiments.

Referring to FIG. 97 , a monthly calendar 9720 is output on the screen of the device 9710 . The calendar 9720 may display an indicator 9730 in the shape of “Δ” indicating a co-authored document. The number in the indicator 9730 “Δ” shape may indicate how many documents have been combined by co-authoring. For example, the indicator 9730 displayed on 2014.05.04. in the calendar 9720 may indicate that three documents have been combined by joint authoring.

The device 9710 may select the indicator 9730 having a “Δ” shape according to a user input received through the user input unit 16510 . When the indicator 9730 is selected, the device 9710 may output the work history information 9740 of the joint authoring document to the screen.

The work history information 9740 of the co-authored document includes information on the file name “workshop.doc” of the co-authored document, and documents “workshop_1.doc”, “workshop_2.doc” and “workshop_3” combined by co-authoring. It contains information in the list of “.doc”. In addition, the work history information 9740 of the joint authoring document includes information on the creation date and time, creation device, etc. may include For example, in the work history information 9740 of the co-authored document, the creation date and time of “workshop_2.doc” is “2013. 12. 26, 11:40:39 AM,” and the device generating “workshop_2.doc” may include information that is the first device 111 .

The device 9710 may select the item 9750 of “workshop_2.doc” which is a part of the jointly authored document according to the user input received through the user input unit 16510 . When the item 9750 is selected, the device 9710 may output work history information 9760 of the document “workshop_2.doc” corresponding to the item 9750 on the screen.

On the other hand, work history information regarding the joint authoring document may be displayed for other indicators 9770 in the same manner as described above.

98 is a diagram illustrating another example of displaying a history of documents generated by joint authoring in a monthly calendar displayed on a screen of a device according to some embodiments.

Referring to FIG. 98 , a monthly calendar 9820 is output on the screen of the device 9810 .

The device 9810 may select the indicator 9830 having a “Δ” shape displayed on 01.06.2014 according to a user input received through the user input unit 16510 . When the indicator 9830 is selected, the device 9810 displays the indicator 9840 on the date of 2014.01.01. and displays the indicator 9850 on the date of 2014.01.28.

When the indicator 9830 is selected, the indicator 9840 and the indicator 9850 displayed together with the indicator 9830 are those displayed to identify the document designated by the indicator 9830 and documents co-authored. That is, the document specified in the indicator 9830 indicated on 01.06.2014 and the document specified in the indicator 9840 indicated on 01.01.2014 and the document specified in the indicator 9850 indicated on 01.28. document used.

Meanwhile, when the indicator 9830 is selected, the device 9810 may output work history information 9860 of the joint authoring document to the screen.

The work history information 9860 of the co-authored document includes information on the file name “party.doc” of the co-authored document, and documents “party_1.doc”, “party_2.doc” and “party_3” combined by co-authoring. It contains information in the list of “.doc”. In addition, the work history information 9860 of the joint authoring document includes information on the creation date and time, creation device, etc. of each of the documents “party_1.doc”, “party_2.doc” and “party_3.doc” combined by the joint author may include For example, in the work history information 9860 of the joint authoring document, the creation date and time of “party_2.doc” is “2014.01.06., PM 08:14:56”, and the device that generated “party_2.doc” is The third device 113 may include information.

The device 9810 may select the item 9870 of “party_2.doc” that is a part of the jointly authored document according to the user input received through the user input unit 16510 . When the item 9870 is selected, the device 9810 may output job history information 9880 of the document “party_2.doc” corresponding to the item 9870 on the screen.

As described above, when a plurality of users jointly author a document, work history information related to the joint authoring of a document may be linked to the calendar, and thus the document may be effectively managed and utilized.

Hereinafter, with reference to FIGS. 99 to 100 , when at least one of the plurality of devices 110 corresponds to the server 100 and the devices 110 perform a document operation, the An example in which the device performing the function interlocks the job history information with the user's calendar will be described.

99 is for explaining an example in which at least one of a plurality of devices corresponds to a server, and when the devices perform a document job, a device performing a server function links job history information to a user's calendar It is a drawing.

Referring to FIG. 99 , the system 1 includes a first device 111 and a second device 112 to an Nth device 114 . Here, the first device 111 means a device that performs the function of the server 100 of FIG. 2 .

At least one of the second device 112 to the N-th device 114 performs a document job, and transmits the job history information 130 of the document to the first device 111 . For example, the second device 112 performs a document job and transmits job history information of the document to the first device 111 . In the same manner, the third device 113 to the N-th device 114 performs a document job, and transmits the job history information 130 of the document to the first device 111 .

The first device 111 links the job history information transmitted from the device to the user's calendar. In addition, the first device 111 transmits information to be displayed on the calendar to at least one of the second device 112 to the Nth device 114 . Here, the information to be displayed on the calendar means information to be displayed on the output calendar when the calendar is output on the screen of the device. For example, the information to be displayed on the calendar may include job history information to be output on the screen of the device when an indicator to be displayed on the calendar or an indicator displayed on the calendar is selected.

In this case, the first device 111 may transmit the information to be displayed on the calendar only to a device that has requested transmission of the information to be displayed on the calendar among the second device 112 to the Nth device 114 . For example, the second device 112 executes a program for outputting a calendar, and authenticates that the user is a user based on a user account input through the user input unit 16510, thereby providing the first device 111 with the user's calendar. You can request the transmission of the information to be displayed.

Meanwhile, even if there is no request from the second device 112 , the first device 111 may automatically transmit (eg, push) information to be displayed on the calendar to the second device 112 .

Hereinafter, with reference to FIG. 100 , when the second device 112 and the third device 113 perform a document task, an example in which the first device 111 links the work history information to the user's calendar will be described. do.

100 is a flowchart illustrating an example in which the first device links work history information to a user's calendar when the second device and the third device 113 perform a document task, according to some embodiments.

In FIG. 100 , the second device 112 and the third device 113 are illustrated as working on a document for convenience of explanation, but the present invention is not limited thereto. In other words, there is no limit to the number of devices working on documents. If it is assumed that there is only one device for working with a document, all operations of the third device 113 to be described below may be performed by the second device 112 . In addition, assuming that the number of devices for working with a document is N (N is a plurality of 3 or more), the operation of the third device 113 to be described below may be performed by at least one of the fourth to Nth devices. .

In S10010, the second device 112 works on the document. For example, the second device 112 may execute a program used for working with a document, and work with the document using the program. For example, the program used for document work may be an MS OFFICE WORD program for Windows operating system (OS) installed in the second device 112 or a PAGE program of MAC OS.

If it is assumed that the document that the second device 112 works with is 'abc.doc' and the program used to create, view, or edit 'abc.doc' is the second program, the second device 112 is The first program may be executed, and 'abc.doc' may be created, viewed, or edited.

In S10011 , the second device 112 transmits job history information of the document to the first device 111 . For example, the second device 112 may transmit the work history information of the document to the first device 111 when the execution of the program used for the document work is finished or the document is stored. For example, the second device 112 may transmit the job history information of 'abc.doc' to the first device 111 at the time of storing 'abc.doc' or ending the execution of the first program. there is. In this case, it is assumed that the user of the second device 112 is logged in to the first device 111 . In addition, examples in which the second device 112 transmits the job history information of the document to the first device 111 are the same as described above with reference to step S411 of FIG. 4 .

In S10012, the third device 113 works on the document. For example, the third device 113 may execute a program used for document work, and work with the document using the program. For example, the program used for document work may be an MS OFFICE WORD program for the Windows operating system (OS) installed in the third device 111 or a PAGE program of the MAC OS. In this case, it is assumed that the user of the third device 113 is logged in to the first device 111 . In addition, examples in which the third device 113 transmits job history information of a document to the first device 111 are the same as those described above with reference to step S411 of FIG. 4 .

If it is assumed that the document that the third device 113 works is 'abcd.xls' and the program used to create, view, or edit 'abcd.xls' is the second program, the third device 113 is Execute the second program and create, view, or edit 'abcd.xls'.

In S10013 , the third device 113 transmits the job history information of the document to the first device 111 . For example, the third device 113 may transmit the work history information of the document to the first device 111 when the execution of the program used for the document work is finished or the document is stored. For example, the third device 113 may transmit the job history information of 'abcd.xls' to the first device 111 at the time of storing 'abcd.xls' or ending the execution of the second program. there is

In S10015 , the first device links the job history information to the user's calendar using time information included in the job history information received from the second device and the third device 113 . For example, the second device 112 stores 'abc.doc' on 2014.05.18 at 08:01:42 am, and the third device 113 stores 'abcd.xls' on 2014.05.20 at 14:29 pm. Assuming that it is stored at :00, the first device 111 generates a first indicator to be displayed in an area corresponding to 2014.05.18 in the calendar, and generates a second indicator to be displayed in an area corresponding to 2014.05.20. can

In S10016 , the second device 112 requests the first device 111 to transmit information to be displayed on the calendar. For example, the second device 112 may request the first device 111 to transmit job history information to be output on the screen of the device when an indicator to be displayed on the calendar or an indicator displayed on the calendar is selected. For example, the second device 112 may request transmission of the work history information to be output on the screen of the device when the first indicator, the second indicator, and the first indicator and the second indicator are selected.

In S10017 , the first device 111 transmits information to be displayed on the calendar to the second device 112 .

In S10018, the second device 112 outputs the calendar on the screen. For example, the second device 112 may output a calendar in which the first indicator and the second indicator transmitted from the first device 111 are displayed on the screen.

In S10019 , the third device 113 requests the first device 111 to transmit information to be displayed on the calendar. For example, the third device 113 may request the first device 111 to transmit job history information to be output on the screen of the device when an indicator to be displayed on the calendar or an indicator displayed on the calendar is selected. For example, the third device 113 may request transmission of the work history information to be output on the screen of the device when the first indicator, the second indicator, and the first indicator and the second indicator are selected.

In S10020 , the first device 111 transmits information to be displayed on the calendar to the third device 113 .

In S10021, the third device 113 outputs the calendar on the screen. For example, the third device 113 may output a calendar in which the first indicator and the second indicator transmitted from the first device 111 are displayed on the screen.

As described above, since the device can perform the function of a server, a personal network system can be built without the intervention of an external server.

Hereinafter, with reference to FIGS. 101 to 146 , when the users of the devices 110 are the same and the server 100 performs a document task based on a request from the devices 110 , the server 100 An example of linking job history information to a user's calendar will be described.

101 is a view for explaining an example in which the server links work history information to the user's calendar when the user of the devices is the same and the server performs a document task based on a request of the devices, according to some embodiments am.

Referring to FIG. 101 , a system 1 includes a server 100 and devices 110 . Here, the devices 110 all refer to devices of the first user 120 .

Compared with the example described above with reference to FIG. 2 , the difference is that the subject performing the document operation in FIG. 101 is the server 100 , not the devices 110 . In other words, in FIG. 2 , a program used for document work is executed on the devices 110 , but in FIG. 101 , a program used for document work is executed on the server 100 .

The server 100 of FIG. 101 executes a program used for document work installed in the server 100 . therefore. Even if a program used for document work is not installed in the device, the first user 120 may perform document work by accessing the server 100 from the device. Since the subject performing the document work is the server 100 , the server 100 may obtain the work history information of the document from the server 100 without receiving the work history information of the document from the devices 110 .

On the other hand, the devices 110 of FIG. 101 do not perform the document work, but request the server 100 to work on the document. At least one of the devices 110 requests the server 100 to work on the document. For example, the first device 111 requests the server 100 to work on a document. In the same manner, the second device 112 to the Nth device 114 requests the server 100 to work on the document.

The server 100 receives a document work request from at least one of the devices 110 and performs the document work. After the execution of the document job is completed, the server 100 acquires job history information of the document.

The server 100 links the acquired job history information 130 to the user's calendar. Then, the server 100 transmits the information 140 to be displayed on the calendar to the devices 110 . Here, the information 140 to be displayed on the calendar means information to be displayed on the output calendar when the calendar is output on the screen of the device. For example, the information 140 to be displayed on the calendar may include job history information to be output on the screen of the device when an indicator to be displayed on the calendar or an indicator displayed on the calendar is selected.

In this case, the server 100 may transmit the information 140 to be displayed on the calendar only to a device that has requested transmission of the information 140 to be displayed on the calendar among the devices 110 . For example, the first device 111 executes a program for outputting a calendar and authenticates that the first user is the first user based on the user account input through the user input unit 16510, thereby providing the server 100 with the It is possible to request transmission of the information 140 to be displayed on the calendar.

Meanwhile, even if there is no request from the first device 111 , the server 100 may automatically transmit (eg, push) the information 140 to be displayed on the calendar to the first device 111 . . For example, if there is a history in which the first device 111 previously requested transmission of the information 140 to be displayed in the calendar of the first user, the server 100 may later request from the first device 111 . Even if there is no information, the information 140 to be displayed on the calendar of the first user may be automatically transmitted.

102 to 163 , it will be described that the server 100 works on a document using the fourth program. For example, the fourth program may correspond to a cloud-based document work program such as MS OFFICE 365, GOOGLE DOCS, and the like.

In addition, in FIGS. 102 to 163 , it will be described that the device transmits the job request information of the document to the server 100 by executing a server access program (eg, a web access program). In other words, the user of the device accesses a predetermined web page (eg, a web page in which the server 100 accesses a program for working with a document) and logs in. After that, the user of the device works on the document on the web page where the login is performed. In this case, the device may transmit a user input for working with a document to the server 100 , and the server 100 may work with the document based on the user input. The server 100 may transmit the work screen of the document to the device in the form of a web page, and the device may output the received work screen to the screen. However, the device transmitting the job request information of the document to the server 100 is not limited to the above-described example.

For example, the device may transmit work request information of a document to the server 100 by executing a work program (or application) installed in the device. In other words, the user of the device executes the work program installed in the device and works on the document. In this case, the device may transmit a user input for working with a document to the server 100 , and the server 100 may work with the document based on the user input. The server 100 may transmit information about the worked document to the device, and the device may output the received information on the screen.

Hereinafter, an example in which the server 100 links job history information to a user's calendar will be described with reference to FIG. 102 .

102 is a flowchart illustrating an example in which a server links job history information to a user's calendar, according to some embodiments.

In S10210, the server 100 acquires the work history information of the document worked on the server 100 according to the user's request. In other words, the server 100 receives a document work request from at least one device of the same user, performs the document work, and obtains work history information.

In S10220, the server 100 links the acquired job history information to the user's calendar by using the time information included in the acquired job history information. Here, the time information means information indicating the time when the server 100 worked on the document. For example, assuming that the server 100 generates a document called 'abc.doc' at 12:28:04 pm on May 12, 2014 in response to the request of the first device 111 , the server 100 generates the document 'abc.doc' An indicator to be displayed on 2014.05.12 is generated in the user's calendar of 111 , and job history information to be output on the screen of the first device 111 may be determined when the indicator displayed on 2014.05.12 is selected. In this case, as described above with reference to FIG. 1 , that the server 100 may link only a part of the job history information acquired in S10210 to the user's calendar.

Hereinafter, with reference to FIG. 103 , when the server 100 works on a document in response to a document work request from the first device 111 , the server 100 links work history information to the calendar of the first user. explain

103 is a flowchart illustrating an example in which the server links work history information to the calendar of the first user when the server 100 performs a document work in response to a document work request from the first device, according to some embodiments.

In FIG. 103 , it is illustrated that the server 100 works on a document in response to a document work request from the first device 111 for convenience of explanation, but the present invention is not limited thereto. In other words, there is no limit to the number of devices requesting document work. Also, there is no limit to the number of devices that request the server 100 to transmit information to be displayed on the calendar.

In S10310 , the first device 111 transmits information requesting document work to the server 100 . For example, when the user of the first device 111 logs in by executing the fourth program, the first device 111 may transmit information requesting document work to the server 100 . In this case, as a method for the user of the first device 111 to log in to the fourth program, various methods including a method of inputting an ID/password may be used.

In S10311 , the server 100 works on a document based on the information received from the first device 111 . For example, the server 100 may execute a program used for document work in the server 100 , and may work on a document using the program executed in the server 100 . If it is assumed that the document that the server 100 works with is 'abc.doc' and the program used to create, view, or edit 'abc.doc' is the fourth program, the server 100 executes the fourth program. You can run it and create, view or edit 'abc.doc'.

In S10312 , the server 100 transmits information about the work screen of the document to the first device 111 . For example, based on the information received from the first device 111 , the server 100 may transmit information about the work screen of the document to the first device 111 whenever a document is worked. In other words, the server 100 may transmit, to the first device 111 , information on the work screen of the document, which is changed whenever the document is worked, by using the program executed in the server 100 .

In S10313, the first device 111 outputs the work screen of the document. For example, the first device 111 may output a work screen of a document based on information about the work screen of the document transmitted from the server 100 .

In S10314, the server 100 acquires the job history information of the document. For example, the server 100 may acquire work history information of a document at a time when execution of a program used for document work is terminated or a document is stored. For example, the server 100 may acquire job history information of 'abc.doc' at the time of storing 'abc.doc' or ending execution of the fourth program. For example, the server 100 may store the obtained work history information in a storage space corresponding to the user's account of the first device 111 .

In S10315, the server 100 links the acquired job history information to the user's calendar by using the time information included in the acquired job history information. For example, assuming that the server 100 stores 'abc.doc' on 2014.05.12 at 12:28:04 pm, the server 100 generates an indicator to be displayed in the area corresponding to 2014.05.12 on the calendar. can do.

In S10316 , the first device 111 requests the server 100 to transmit information to be displayed on the calendar. For example, the first device 111 may request the server 100 to transmit job history information to be output on the screen of the device when an indicator to be displayed on the calendar or an indicator displayed on the calendar is selected.

In S10317 , the server 100 transmits information to be displayed on the calendar to the first device 111 .

In S10318, the first device 111 outputs the calendar on the screen. For example, the first device 111 may output a calendar in which the indicator transmitted from the server 100 is displayed on the screen.

In S10319 , the second device 112 requests the server 100 to transmit information to be displayed on the calendar. For example, the second device 112 may request the server 100 to transmit job history information to be output on the screen of the device when an indicator to be displayed on the calendar or an indicator displayed on the calendar is selected.

In S10320 , the server 100 transmits information to be displayed on the calendar to the second device 112 .

In S10321, the second device 112 outputs the calendar on the screen. For example, the second device 112 may output a calendar in which the indicator transmitted from the server 100 is displayed on the screen.

Hereinafter, an example in which the server 100 links job history information to a user's calendar when the server 100 generates a document will be described with reference to FIGS. 104 to 120 .

104 is a flowchart illustrating an example in which the server links job history information to a user's calendar when the server generates a document according to some embodiments.

In FIG. 104, for convenience of explanation, it is illustrated that the server 100 generates a document in response to a document work request from the first device 111 and the second device 112 outputs a calendar on the screen, but the present invention is not limited thereto. . For example, the server 100 may generate a document in response to a document work request from the first device 111 , and the first device 111 and the second device 112 may output a calendar on the screen.

Also, there is no limit to the number of devices. If it is assumed that the number of devices requesting a document operation is N (N is a plurality of 3 or more), the operation of the first device 111 or the operation of the second device 112, which will be described below, is the operation of the third device 113 . ) to at least one of the Nth device.

In S10410, the first device 111 executes the server connection program. In order for a user to request a document work from the server 100 , the first device 111 may execute a server access program. For example, the user of the first device 111 may execute a server access program and input his/her ID/password.

In S10411 , the first device 111 transmits information requesting document work to the server 100 .

In S10412, the server 100 generates a document. For example, the server 100 may execute a program used for generating a document in the server 100 , and may generate a document using the program executed in the server 100 . If it is assumed that the document generated by the server 100 is 'abc.doc' and the program used to generate 'abc.doc' is the fourth program, the server 100 executes the fourth program, and ' abc.doc' can be generated.

In S10413 , the server 100 transmits information about the work screen of the document to the first device 111 . For example, when the server 100 generates a document using a program executed in the server 100 , information on a work screen of the generated document may be transmitted to the first device 111 .

In S10414, the first device 111 outputs the work screen of the document. For example, the first device 111 may output a work screen of a document based on information about the work screen of the document transmitted from the server 100 .

In S10415, the server 100 stores the document. For example, the server 100 may receive a document storage request from the user on the work screen of the document output to the first device, and store the generated document.

In S10416, the server 100 acquires the job history information of the document. For example, the server 100 may acquire work history information of the document at the time of storing the document. The work history information of the document means information generated as the server 100 creates and stores the document. For example, the job history information may include the title of the document on which the job was performed, the type of the document, the time the document job was performed, the name of the device performing the document job, the user of the device, the program used for the document job, the size of the document, It can include the type of work. For example, the server 100 may store the acquired work history information in a storage space corresponding to the user's account of the first device 111 .

Hereinafter, an example in which the server 100 executes a program to generate and store a document and obtains work history information of the document will be described with reference to FIGS. 105 to 106 .

105 to 106 are diagrams for explaining an example in which a server executes a program to generate and store a document, and obtain job history information of the document, according to some embodiments.

Referring to FIG. 105 , the first device 111 executes a server connection program. For example, the first device 111 may select an indicator indicating a server access program based on a user input received through the user input unit 16510 . In addition, the first device 111 may execute a server access program corresponding to the selected indicator. The server access program may be a web browser, and an Internet address of the server may be input into an address bar of the web browser.

Referring to FIG. 105 , when the server connection program is executed in the first device 111 , the server 100 transmits information about the server connection program execution screen. The first device 111 transmits information requesting document work to the server 100 through the server access program. In this case, the information for requesting document work may be information for requesting creation of a document.

Referring to FIG. 106 , the first device 111 outputs a work screen of a document based on information about the work screen of a document. The first device 111 may select an indicator for requesting 'save' of the text document based on the user input received through the user input unit 16510. In addition, the first device 111 may request the server 100 to store the text document.

After storing the text document, the server 100 acquires work history information of the text document. For example, assuming that the server 100 stores a document named 'abc.doc' having a size of 54 KB (kilobyte) using the fourth program at 12:28:04 pm on May 12, 2014 , the server 100 may acquire at least one of 'abc.doc, text, fourth program, first device, May 12, 2014 12:28:04 PM, 54 KB'.

On the other hand, when a high degree of security is required for the stored document, the server 100 may additionally perform encryption on the job history information and store it.

As an example, if the user selects the 'security' option when storing the document, the server 100 may additionally perform encryption on the job history information of the document.

As another example, a user may create a specific folder, and a document included in the created folder may be set to have a strong degree of security. When the job history information of the document included in the folder is generated, the server 100 may additionally perform encryption on the job history information.

After the user logs in to the server 100 , the user can access the job history information transmitted to the server 100 . However, separate information may be additionally required to access the encrypted work history information. For example, even after the user logs in to the server 100 by inputting a password/ID, it may be set to require a separate password input in order to access the encrypted work history information.

106 illustrates an example in which the server 100 obtains work history information of a document when the document is a text document according to some embodiments, but the type of the document is not limited thereto.

Referring back to FIG. 104 , in S10417 , the server 100 links the job history information to the calendar by using the time information included in the job history information.

Hereinafter, an example in which the server 100 links job history information of a document to a calendar will be described with reference to FIGS. 107 to 110 .

107 is a flowchart illustrating an example in which a server links job history information of a document to a calendar, according to some embodiments.

In S10710 , the server 100 acquires the creation time information of the document included in the job history information obtained by generating the document based on the job request from the first device 111 . For example, according to the example described above with reference to FIG. 106 , the server 100 determines '2014.05.12, 12 PM in the work history information obtained by generating a document based on the work request from the first device 111 . :28:04'.

Hereinafter, an example of the job history information obtained by the server 100 will be described with reference to FIGS. 108 to 109 .

108 to 109 are diagrams illustrating an example of job history information of a document according to some embodiments.

Referring to FIG. 108 , an example of job history information 10810 of a document is illustrated. For example, in the job history information 10810 of the document, the name of the document 10811 , the type of the document 10812 , the name of the job program 10813 , the name of the job requesting device 10814 , and the user 10815 of the device. , job type 10816 , job date and time 10817 , and file size 10818 , but are not limited thereto. In other words, the work history information 10810 of the document may correspond without limitation as long as it is information that can be generated by performing the work of the document.

For example, the server 100 arranges the job history information 10810 obtained by the server 100 based on the name 10811 of the document, and stores the arranged job history information 10810 in the database 16430. can

Referring to FIG. 109 , another example of job history information 10910 of a document is illustrated. The job history information 10810 shown in FIG. 108 and the job history information 10910 shown in FIG. 109 include the same information. In other words, in the job history information 10910 of the document shown in FIG. 109, the document name 10914, the document type 10912, the job program name 10913, the job request device name 10911, and the device User 10916, job type 10915, job date and time 10917, and file size 10918 are included. For example, the server 100 arranges the job history information 10910 obtained by the server 100 based on the name of the job device 10911, and stores the arranged job history information 10910 into the database 16430. can be stored in

Referring back to FIG. 107 , in S10720, the server 100 links the job history information to the user's calendar based on the creation time information of the document. Hereinafter, an example in which the server 100 links job history information to a user's calendar will be described with reference to FIG. 110 .

110 is a flowchart illustrating an example in which a server links job history information to a user's calendar, according to some embodiments.

In S11010, the server 100 acquires the user's calendar. Here, the user's calendar means a frame to which work history information of a document is linked. For example, the server 100 may read the user's calendar stored by matching the user's account from the database 16430 , or may receive the user's calendar from at least one of the devices 110 . For example, the user's calendar may include a calendar displayed in units of days, a calendar displayed in units of weeks, a calendar displayed in units of months, or a calendar displayed in units of years.

In S11020, the server 100 generates an indicator to be displayed on the calendar based on any one of the name of the document included in the work history information, the program used to generate the document, and the name of the device that requested the creation of the document. In other words, the server 100 determines any one of the name of the document, the program used to generate the document, and the name of the device requesting generation of the document as the item indicated by the indicator, and generates the indicator based on the determined item.

In S11030, the server 100 determines job history information to be displayed on the calendar based on the generated indicator.

In S11040, the server 100 displays the indicator in the area corresponding to the date or time indicating the time when the document is created in the calendar.

Referring back to FIG. 104 , in S10418 , the second device 112 requests the server 100 to transmit information to be displayed on the calendar. For example, the second device 112 may request the server 100 to transmit information to be displayed on the calendar after executing the calendar output program installed in the second device 112 and authenticating the user. .

In S10419 , the server 100 transmits information to be displayed on the calendar to the second device 112 .

In FIG. 104, when the second device 112 requests the server 100 to transmit the information to be displayed on the calendar in S10418, the server 100 transmits the information to be displayed on the calendar in S10419. doesn't happen For example, even if there is no transmission request from the second device 112 , the server 100 may transmit (eg, push) information to be displayed on the calendar to the second device 112 .

In S10420, the second device 112 outputs the calendar on the screen.

111 is a diagram illustrating an example of a daily calendar displayed on a screen of a device according to some embodiments.

Referring to FIG. 111 , a daily calendar 11120 is output on the screen of the device 11110 . An indicator 11160 indicating the name of a document may be displayed on the calendar 11120 . For example, assuming that the server 100 generates a document named 'abc.doc' on May 12, 2014 using the fourth program in response to the request of the first device 111, the calendar 11120 An indicator 11160 indicating 'abc.doc' may be displayed in an area corresponding to 2014.05.12.

The device 11110 may select the indicator 11160 indicating 'abc.doc' according to the user input received through the user input unit 16510 . When the indicator 11160 indicating 'abc.doc' is selected, the device 11110 may output the job history information 11170 of the document on the screen. For example, at the request of the first device 111, the server 100 uses the fourth program to create a document named 'abc.doc' having a size of 54 KB (kilobyte) on May 12, 2014. Assuming that it is stored at 12:28:04 pm, the job history information 1670 includes 'abc.doc, text, fourth program, first device, May 12, 2014 12:28:04 pm, 54 KB'. can be output. Meanwhile, the device 11110 may output the job history information 11170 of the document on the screen as a separate pop-up window.

Also, an indicator 11180 capable of outputting a document to the screen of the device 11110 may be displayed in the job history information 11170 of the document. For example, when the indicator 11180 capable of outputting a document according to a user input received through the user input unit 16510 is selected, the device 11110 outputs the document in a pop-up window separate from the calendar 11120 . can

112 is a diagram illustrating another example of a daily calendar displayed on a screen of a device according to some embodiments.

Referring to FIG. 112 , a daily calendar 11220 is output on the screen of the device 11210 . The calendar 11220 illustrated in FIG. 112 has the same frame as the calendar 11120 illustrated in FIG. 111 . Accordingly, the contents described above with reference to FIG. 111 with respect to indicators that may be displayed on the calendar 11220 may be equally applied to FIG. 112 .

An indicator 11230 indicating a program used to work on a document may be displayed on the calendar 11220 . For example, in response to the request of the first device 11210, assuming that the server 100 creates a document using the fourth program on May 12, 2014, in the area corresponding to May 12, 2014 of the calendar 11220, An indicator 11230 indicating the 'fourth program' may be displayed.

The device 11210 may select the indicator 11230 indicating the 'fourth program' according to the user input received through the user input unit 16510 . When the indicator 11230 indicating the 'fourth program' is selected, the device 11210 may output the job history information 11240 of the document on the screen. For example, at the request of the first device 111, the server 100 uses the fourth program to create a document named 'abc.doc' having a size of 54 KB (kilobyte) on May 12, 2014. Assuming that it is stored at 12:28:04 pm, the job history information 11240 includes 'abc.doc, text, fourth program, first device, May 12, 2014 12:28:04 pm, 54 KB'. can be output. Meanwhile, the device 11210 may output the job history information 11240 of the document to the screen as a separate pop-up window.

Also, an indicator 11250 capable of outputting a document to the screen of the device 11210 may be displayed in the job history information 11240 of the document. For example, when an indicator 11250 capable of outputting a document according to a user input received through the user input unit 16510 is selected, the device 11210 outputs the document in a pop-up window separate from the calendar 11220. can

113 is a diagram illustrating another example of a daily calendar displayed on a screen of a device according to some embodiments.

Referring to FIG. 113 , a daily calendar 11320 is output on the screen of the device 11310 . The calendar 11320 illustrated in FIG. 113 has the same frame as the calendar 11120 illustrated in FIG. 111 . Accordingly, the contents described above with reference to FIG. 111 with respect to indicators that may be displayed on the calendar 11320 may be equally applied to FIG. 113 .

An indicator 11330 indicating the name of the device may be displayed on the calendar 11320 . For example, in response to the request of the first device 111, assuming that the server 100 creates a document on May 12, 2014 using the fourth program, in the area corresponding to May 12, 2014 of the calendar 11320, An indicator 11340 indicating the 'first device' may be displayed.

The device 11310 may select the indicator 11330 indicating the 'first device' according to the user input received through the user input unit 16510 . When the indicator 11330 indicating the 'first device' is selected, the device 11310 may output the job history information 11340 of the document on the screen. For example, at the request of the first device 111, the server 100 uses the fourth program to create a document named 'abc.doc' having a size of 54 KB (kilobyte) on May 12, 2014. Assuming that it is stored at 12:28:04 pm, the job history information 11340 includes 'abc.doc, text, fourth program, first device, May 12, 2014 12:28:04 pm, 54 KB'. can be output. Meanwhile, the device 11310 may output the job history information 11340 of the document to the screen as a separate pop-up window.

Also, an indicator 11350 capable of outputting a document to the screen of the device 11310 may be displayed in the job history information 11340 of the document. For example, when the indicator 11350 capable of outputting a document according to a user input received through the user input unit 16510 is selected, the device 11310 outputs the document in a pop-up window separate from the calendar 11320. can

114 is a diagram illustrating an example of a monthly calendar displayed on a screen of a device according to some embodiments.

Referring to FIG. 114 , a monthly calendar 11420 is output on the screen of the device 11410 . The calendar 11420 illustrated in FIG. 114 has the same frame as the calendar 1920 illustrated in FIG. 19 . Accordingly, the contents described above with reference to FIG. 19 with respect to objects that can be displayed on the calendar 11420 may be equally applied to FIG. 114 . An indicator 11430 indicating the name of the document may be displayed on the calendar 11420 . For example, assuming that the server 100 generates a document named 'abc.doc' on 2014.05.12 according to the request of the first device 111 , the calendar 11420 corresponds to 2014.05.12 An indicator 11430 indicating 'abc.doc' may be displayed in the area.

The device 11410 may select the indicator 11430 indicating 'abc.doc' according to the user input received through the user input unit 16510 . When the indicator 11430 indicating 'abc.doc' is selected, the device 11410 may output job history information 11440 of the document on the screen.

For example, at the request of the first device 111, the server 100 uses the fourth program to create a document named 'abc.doc' having a size of 54 KB (kilobyte) on May 12, 2014. Assuming that it is stored at 12:28:04 PM, the job history information 11440 includes 'abc.doc, text, fourth program, first device, May 12, 2014 12:28:04 PM, 54 KB'. can be output. Meanwhile, the device 11410 may output the job history information 11440 of the document to the screen as a separate pop-up window.

Also, an indicator 11450 capable of outputting a document to the screen of the device 11410 may be displayed in the work history information 11440 of the document. For example, when the indicator 11450 capable of outputting a document according to a user input received through the user input unit 16510 is selected, the device 11410 displays a pop-up window separate from the calendar 11420 to the first device ( 111) can be printed on the screen.

115 is a diagram illustrating another example of a monthly calendar displayed on a screen of a device according to some embodiments.

Referring to FIG. 115 , a monthly calendar 11520 is output on the screen of the device 11510 . The calendar 11520 illustrated in FIG. 115 has the same frame as the calendar 1920 illustrated in FIG. 19 . Accordingly, the contents described above with reference to FIG. 19 with respect to objects that may be displayed on the calendar 11520 may be equally applied to FIG. 115 .

An indicator 11530 indicating a program used for document work may be displayed on the calendar 11520 . For example, assuming that the server 100 generates a document using the fourth program on May 12, 2014 in response to the request of the first device 11510 , in the area corresponding to May 12, 2014 of the calendar 11520, An indicator 11530 indicating the 'fourth program' may be displayed.

The device 11510 may select the indicator 11530 indicating the 'fourth program' according to the user input received through the user input unit 16510 . When the indicator 11530 indicating the 'fourth program' is selected, the device 11510 may output job history information 11540 of the document on the screen. For example, according to the request of the first device 111, the server 100 uses the fourth program to create a document named 'abc.doc' having a size of 54 KB (kilobyte) on the afternoon of May 12, 2014. Assuming that it is stored at 12:28:04, in the job history information 11540, 'abc.doc, text, the fourth program, the first device, 12:28:04 PM on May 12, 2014, 54 KB' can be output. Meanwhile, the device 11510 may output the job history information 11540 of the document on the screen as a separate pop-up window.

Also, an indicator 11550 capable of outputting a document to the screen of the device 11510 may be displayed in the job history information 11540 of the document. For example, when an indicator 11550 capable of outputting a document according to a user input received through the user input unit 16510 is selected, the device 11510 displays a pop-up window separate from the calendar 11520 to the first device ( 111) can be printed on the screen.

116 is a diagram illustrating another example of a monthly calendar displayed on a screen of a device according to some embodiments.

Referring to FIG. 116 , a monthly calendar 11620 is output on the screen of the device 11610 . The calendar 11620 shown in FIG. 116 has the same frame as the calendar 1910 shown in FIG. 19 . Accordingly, the contents described above with reference to FIG. 19 with respect to objects that may be displayed on the calendar 11620 may be equally applied to FIG. 116 .

An indicator 11630 indicating the name of the device may be displayed on the calendar 11620 . For example, assuming that the server 100 creates a document on May 12, 2014 in response to the request of the first device 111 , the 'first device' is set in the area corresponding to May 12, 2014 of the calendar 11620 . An indicating indicator 11630 may be displayed.

The device 11610 may select the indicator 11630 indicating the 'first device' according to the user input received through the user input unit 16510 . When the indicator 11630 indicating the 'first device' is selected, the device 11610 may output job history information 11640 of the document to the screen. For example, at the request of the first device 111, the server 100 uses the fourth program to create a document named 'abc.doc' having a size of 54 KB (kilobyte) on May 12, 2014. Assuming that it is stored at 12:28:04 PM, the job history information 11640 includes 'abc.doc, text, fourth program, first device, May 12, 2014 12:28:04 PM, 54 KB'. can be output. Meanwhile, the device 11610 may output the job history information 11640 of the document to the screen as a separate pop-up window.

Also, an indicator 11650 capable of outputting a document to the screen of the device 11610 may be displayed in the job history information 11640 of the document. For example, when an indicator 11650 capable of outputting a document according to a user input received through the user input unit 16510 is selected, the device 11610 displays a pop-up window separate from the calendar 11620 to the first device ( 111) can be printed on the screen.

117 is a diagram illustrating an example of an annual calendar displayed on a screen of a device according to some embodiments.

Referring to FIG. 117 , an annual calendar 11720 is output on the screen of the device 11710 . As described above with reference to FIG. 22 , the calendar 11720 may include an area 11721 in which months included in a year are displayed and an indicator 11722 in which a user can designate a desired year. Also, the calendar 11720 may include an indicator 11723 capable of displaying a calendar of a year including the date of 'today'. In addition to the above-described indicators, the calendar 11720 may be included without limitation as long as it is an indicator through which the user can control the display type.

Indicators 11730 , 11740 , and 11750 indicating document names may be displayed on the calendar 11720 . For example, assuming that, in response to the request of the first device 111, the server 100 generates a document named 'xyz.doc' on February 12, 2014, in the area corresponding to February 2014 in the calendar 11720 An indicator 11730 indicating 'xyz.doc' may be displayed.

In addition, assuming that, in response to the request of the first device 111, the server 100 generates a document named 'abcd.xls' on April 22, 2014, 'abcd' in the area corresponding to 2014.04 in the calendar 11720 An indicator 11740 indicating .xls' may be displayed.

In addition, assuming that, in response to the request of the first device 111, the server 100 creates a document named 'abc.doc' on May 12, 2014 using the fourth program, in the calendar 11720 on May 2014 An indicator 11750 indicating 'abc.doc' may be displayed in the corresponding area.

In the foregoing, it has been described that all of 'xyz.doc', 'abcd.xls', and 'abc.doc' are generated by the first device 111, but different devices may generate respective documents.

The device 11710 may select the indicators 11730 , 11740 , and 11750 indicating the name of the document according to the user input received through the user input unit 16510 . When the indicators 11730 , 11740 , and 11750 indicating the name of the document are selected, the device 11710 may output the job history information 11760 of the document on the screen.

For example, at the request of the first device 111, the server 100 uses the fourth program to create a document named 'abc.doc' having a size of 54 KB (kilobyte) on May 12, 2014. Assume you saved it at 12:28:04 PM. At this time, when the indicator 11750 indicating 'abc.doc' is selected, the job history information 11760 includes 'abc.doc, text, fourth program, first device, May 12, 2014 12:28 pm: 04, 54 KB' may be output. Meanwhile, the device 11710 may output the job history information 11760 of the document to the screen as a separate pop-up window.

Also, an indicator 11770 capable of outputting a document to the screen of the device 11710 may be displayed in the job history information 11760 of the document. For example, when an indicator 11770 capable of outputting a document according to a user input received through the user input unit 16510 is selected, the device 11710 displays a pop-up window separate from the calendar 11720 to the first device ( 111) can be printed on the screen.

118 is a diagram illustrating another example of an annual calendar displayed on a screen of a device according to some embodiments.

Referring to FIG. 118 , a yearly calendar 11820 is output on the screen of the device 11810 . In addition, an indicator 11830 indicating a program (eg, a fourth program) used for document work is displayed on the calendar 11820 .

As described above with reference to FIG. 117 , when the indicator 11830 indicating a program used for working on a document is selected, the device 11810 may output job history information 11840 of the document on the screen. In addition, when the indicator 11850 capable of outputting a document is selected on the screen on which the work history information 11840 of the document is displayed, the device 11810 may output the document generated by the first device 111 to the screen. .

119 is a diagram illustrating another example of an annual calendar displayed on a screen of a device according to some exemplary embodiments.

Referring to FIG. 119 , an annual calendar 11920 is output on the screen of the device 11910 . In addition, an indicator 11930 indicating a device is displayed on the calendar 11920 . As described above with reference to FIG. 117 , when the indicator 11930 indicating the device is selected, the device 11910 may output the execution history information 11940 of the document to the screen. Also, when an indicator 11950 capable of outputting a document is selected on the screen on which execution history information 11940 of the document is displayed, the device 11910 may output the document generated by the first device 111 to the screen. .

120 is a diagram illustrating another example of an annual calendar displayed on a screen of a device according to some embodiments.

Referring to FIG. 120 , a yearly calendar 12020 is output on the screen of the device 12010 . The annual calendar shown in FIGS. 117 to 119 includes an area in which months included in a year are displayed, but the annual calendar 12020 shown in FIG. 120 includes an area 12030 in which days included in a year are displayed. This is included. In other words, the device 12010 may variously change the format of the annual calendar and output it on the screen.

Indicators 12031 , 12032 , and 12033 may be displayed on the calendar 12020 on the date the document was performed. For example, assuming that, in response to the request of the first device 111, the server 100 generates a document named 'xyz.doc' on 2014.02.12, the calendar 12020 corresponds to 2014.02.12. An indicator 12031 indicating 'xyz.doc' may be displayed in the area.

In addition, assuming that the server 100 creates a document named 'abcd.xls' on April 22, 2014 in response to the request of the first device 111, in the calendar 12020 in the area corresponding to April 22, 2014 An indicator 12032 indicating 'abcd.xls' may be displayed.

In addition, assuming that the server 100 generates a document named 'abc.doc' on May 12, 2014 by using the fourth program in response to the request of the first device 111 , the calendar 12020 displays a document named 'abc.doc'. An indicator 12033 indicating 'abc.doc' may be displayed in the area corresponding to 12 .

Although it has been described above that all of 'xyz.doc', 'abcd.xls', and 'abc.doc' are generated by the first device 111, different devices may generate documents.

As described above with reference to FIG. 117 , when the indicator 12033 displayed on the calendar 12020 is selected, the device 12010 may output the job history information 12040 of the document on the screen. For example, 'abc.doc, text, fourth program, first device, May 12, 2014 12:28:04 pm, 54 KB' may be output to the work history information 12040 . In addition, when the indicator 12050 capable of outputting a document is selected on the screen on which the work history information 12040 of the document is displayed, the device 12010 may output the document generated by the first device 111 to the screen. .

121A to 121C are diagrams illustrating that when a server performs a document work in response to a document work request from a first device and a second device reads a document, the server provides work history information to the calendar of the first user, according to some embodiments. It is a flowchart showing an example of interworking.

121A to 121C illustrate that the server 100 works on a document in response to a document work request from the first device 111 for convenience of explanation, but is not limited thereto. In other words, there is no limit to the number of devices requesting document work. Also, there is no limit to the number of devices that request the server 100 to transmit information to be displayed on the calendar.

In S12110, the first device 111 executes the server connection program. In order for a user to request a document work from the server 100 , the first device 111 may execute a server access program. For example, the user of the first device 111 may execute a server access program and input his/her ID/password.

In S12111 , the first device 111 transmits information requesting document work to the server 100 .

In S12112, the server 100 generates a document. The server 100 generates a document based on the information received from the first device 111 . For example, the server 100 may execute a program used for generating a document in the server 100 , and may generate a document using the program executed in the server 100 .

For example, assuming that the document generated by the server 100 is 'abc.doc' and the program used to generate the 'abc.doc' is the fourth program, the server 100 executes the fourth program and , 'abc.doc' can be created, viewed or edited.

In S12113 , the server 100 transmits information about the work screen of the document to the first device 111 . For example, based on the information received from the first device 111 , the server 100 may transmit information about the work screen of the document to the first device 111 whenever a document is worked. In other words, the server 100 may transmit, to the first device 111 , information on the work screen of the document, which is changed whenever the document is worked, by using the program executed in the server 100 .

In S12114, the first device 111 outputs the work screen of the document. For example, the first device 111 may output a work screen of a document based on information about the work screen of the document transmitted from the server 100 .

In S12115, the server 100 stores the document. When the document operation is completed, the server 100 stores the document.

In S12116, the server 100 acquires the job history information of the document. For example, the server 100 may acquire work history information of a document at a time when execution of a program used for document work is terminated or a document is stored. For example, the server 100 may acquire job history information of 'abc.doc' at the time of storing 'abc.doc' or ending execution of the fourth program. For example, the server 100 may store the obtained work history information in a storage space corresponding to the user's account of the first device 111 .

In S12117, the server 100 links the acquired job history information to the user's calendar by using the time information included in the acquired job history information. For example, assuming that the server 100 stores 'abc.doc' on 2014.05.12 at 12:28:04 pm, the server 100 generates an indicator to be displayed in the area corresponding to 2014.05.12 on the calendar. can do.

In S12118 , the second device 112 requests the server 100 to transmit information to be displayed on the calendar. For example, the second device 112 may request the server 100 to transmit job history information to be output on the screen of the device when an indicator to be displayed on the calendar or an indicator displayed on the calendar is selected. The second device 112 may request the server 100 to transmit information to be displayed on the calendar after executing the calendar output program installed in the second device 112 and authenticating the user using the input user account. .

In S12119 , the server 100 transmits information to be displayed on the calendar to the second device 112 .

In FIG. 121a, when the second device 112 requests the server 100 to transmit the information to be displayed on the calendar in S12118, the server 100 transmits the information to be displayed on the calendar in S12119. not limited For example, even if there is no transmission request from the second device 112 , information to be displayed on the calendar may be transmitted (eg, pushed) to the second device 112 .

In S12120, the second device 112 outputs the calendar on the screen. For example, the second device 112 may output a calendar in which the indicator transmitted from the server 100 is displayed on the screen.

In S12121, the second device 112 executes the server connection program. In order for a user to request a document work from the server 100 , the second device 112 may execute a server access program. For example, the user of the second device 112 may execute a server access program and input his/her ID/password.

In S12122 , the second device 112 transmits information for requesting document work to the server 100 .

In S12123 , the second device 112 receives information about a work screen of a document from the server 100 .

In S12124, the second device 112 outputs the work screen of the document.

In S12125, the second device 112 ends the output of the work screen.

In S12126 , the second device 112 notifies the server 100 that the output of the work screen has ended.

In S12127, the server 100 acquires the job history information of the document. For example, the server 100 may store the obtained work history information in a storage space corresponding to the user's account of the second device 112 .

In S12128, the server 100 links the work history information to the calendar by using the time information included in the obtained work history information.

In S12129 , the first device 111 requests the server 100 to transmit information to be displayed on the calendar. For example, the first device 111 may request the server 100 to transmit job history information to be output on the screen of the device when an indicator to be displayed on the calendar or an indicator displayed on the calendar is selected.

In S12130 , the second device 112 requests the server 100 to transmit information to be displayed on the calendar.

In S12131 , the server 100 transmits information to be displayed on the calendar to the first device 111 .

In S12132, the first device 111 outputs the calendar on the screen. For example, the first device 111 may output a calendar in which the indicator transmitted from the server 100 is displayed on the screen.

In S12133 , the server 100 transmits information to be displayed on the calendar to the second device 112 .

In S12134 , the second device 112 outputs the calendar on the screen. Hereinafter, with reference to FIG. 122 , the second device 112 requests the server 100 to work on a document, and receives a work screen from the server 100 . An example of receiving information on

122 is a diagram for explaining an example in which a second device requests a server to work on a document and receives information about a work screen, according to some embodiments.

Referring to FIG. 122 , a calendar 12210 output on the screen of the second device 112 is shown. Here, the calendar 12210 refers to a calendar output on the screen of the second device 112 according to S12120 of FIG. 121A .

The second device 112 receives a user input for selecting the indicator 12220 displayed on the calendar 12210 through the user input unit 16510 . The second device 112 outputs job history information 12230 of the document on the screen according to the received user input. In this case, an indicator 12240 capable of outputting a document to the screen of the second device 112 may be displayed on the screen on which the work history information 12230 of the document is displayed.

The second device 112 receives a user input for selecting the indicator 12240 through the user input unit 16510 . The second device 112 requests (12250) a document operation from the server 100 according to the received user input. Then, the server 100 transmits ( 12260 ) information about the work screen to the second device 112 according to the request of the second device 112 .

Referring again to FIG. 122 , in S12224 , the second device 112 outputs a work screen of the document transmitted from the server 100 .

In S12225, the second device 112 ends the output of the work screen. Hereinafter, an example in which the second device 112 terminates the output of the work screen will be described with reference to FIG. 123 .

123 is a diagram for explaining an example in which the second device terminates output of a work screen, according to some embodiments.

Referring to FIG. 123 , a work screen received from the server 100 is output 12310 on the screen of the second device 112 . The second device 112 receives a user input for terminating the output 12310 of the work screen through the user input unit 16510 . For example, the user input may be an input 12320 for terminating execution of a program used for document work.

Referring to FIG. 123 , the second device 112 receives a user input for selecting an indicator 12320 displayed on the screen. Then, the second device 112 ends the program used for the document operation according to the received user input.

124 is a diagram for explaining an example in which a second device transmits job history information of a document to a server according to some embodiments.

Referring to FIG. 124 , the second device 112 notifies the server 100 of the end of outputting the document, and the server 100 receives job history information of the document from the second device 112 .

After storing the text document, the server 100 acquires work history information of the text document. For example, the second device 112 stores a document named 'abc.doc' having a size of 54 KB (kilobyte) using the first program at 08:26:11 pm on May 20, 2014. Assume that the server 100 may acquire at least one of 'abc.doc, text, fourth program, second device, 08:46:11 PM on May 20, 2014, 54 KB'.

Meanwhile, as described above with reference to FIG. 106, the job history information of a document requiring a high degree of security may be additionally encrypted and stored.

125 is a flowchart illustrating an example in which a server links job history information of a document to a calendar, according to some embodiments.

In S12510, the server 100 acquires the reading time information of the document included in the job history information obtained by reading the document based on the job request from the second device 112 . For example, according to the example described above with reference to FIG. 124 , the server 100 '2014.05.20, 08 PM in the work history information obtained by reading a document based on a work request from the second device 112 . :46:11'.

126 to 127 are diagrams illustrating an example of job history information of a document according to some embodiments.

Referring to FIG. 126 , an example of job history information 12610 of a document is illustrated. For example, the job history information 12610 of the document includes the name 12611 of the document, the type of the document, the name of the job program, the user who worked, the name of the working device, the job type, the job date and time, and the file size. Although illustrated, the present invention is not limited thereto. In other words, the work history information 12610 of the document may correspond without limitation as long as it is information that can be generated by performing the work of the document.

The job history information 12610 of the document shown in FIG. 126 is an example updated from the job history information 10810 of the document shown in FIG. 108 . In other words, the job history information 10810 of the document shown in FIG. 108 means job history information generated when the device generates the document.

Meanwhile, the job history information 12620 of the document shown in FIG. 126 indicates that the new job history information 12620 is added as the first device 111 creates a document and the second device reads the document. Specifically, in FIG. 126 , the first device 111 generates the abc.doc document at 2014.05.12 PM 12:28:04, and the second device 112 transmits the abc.doc document at 2014.05.20 PM 08:46 An example of a case in which the new job history information 12620 read in :11 is added.

In addition, as the work history information 12630 of the document shown in FIG. 126 generates a document by the N-th device 114 and the third device 113 reads the document, new work history information 12630 is added. indicates that Specifically, in FIG. 126 , the first user creates a kkk.ppt document at 2:21:04 AM on January 1, 2013 using the N-th device 114 , and the first user uses the third device 113 to An example of a case in which new job history information 12630 that reads the kkk.ppt document at 2014.05.28 PM 08:21:11 is added is shown.

Referring to FIG. 127 , another example of job history information 12710 of a document is illustrated. The job history information 12710 shown in FIG. 127 and the job history information 12610 shown in FIG. 126 include the same information. In other words, the job history information 12710 of the document shown in FIG. 127 includes the job device request name 12711, the document type, the job program name, the document name, the job type, the user who worked, the job date and time, and the file size. .

The job history information 12710 of the document shown in FIG. 127 is an example updated from the job history information 10910 of the document shown in FIG. 109 . In other words, the job history information 10910 of the document shown in FIG. 109 means the job history information 10910 generated when the device generates the document. Meanwhile, the job history information 12710 of the document shown in FIG. 127 indicates that new job history information 12720 and 12730 are added as at least one of the devices reads the generated document.

The job history information 12710 of the document shown in FIG. 127 indicates that new job history information 12720 is added as the second device 112 reads the abc.doc document. Specifically, FIG. 127 illustrates an example in which new job history information 12720 in which the second device 112 reads the abc.doc document at 2014.05.20 PM 08:46:11 is added.

In addition, the job history information 12710 of the document shown in FIG. 127 indicates that new job history information 12730 is added as the third device 113 reads the kkk.ppt document. Specifically, FIG. 127 shows an example in which new job history information 12730 that the third device 113 reads the kkk.ppt document at 2014.05.28 PM 08:21:11 is added.

128 is a flowchart illustrating an example in which a server links job history information to a user's calendar, according to some embodiments.

In S12810, the server 100 acquires a previously created user's calendar. Here, the pre-created user's calendar means a frame to which work history information of a document is linked. For example, the server 100 may read the user's calendar stored by matching the user's account from the database 16430 , or may receive the user's calendar from at least one of the devices 110 . For example, the user's calendar may include a calendar displayed in units of days, a calendar displayed in units of weeks, a calendar displayed in units of months, or a calendar displayed in units of years.

In S12820, the server 100 generates an indicator to be displayed on the calendar based on any one of the name of the document included in the work history information, the program used for reading the document, and the name of the device requesting the reading of the document. In other words, the server 100 determines any one of the name of the document, the program used for reading the document, and the name of the device requesting the reading of the document as the item indicated by the indicator, and generates the indicator based on the determined item.

In S12830, the server 100 determines the job history information to be displayed on the calendar based on the read indicator.

In S12840 , the server 100 adds and displays an indicator to an area corresponding to a date or time indicating a point in time at which the document was read in the calendar.

129 is a diagram illustrating an example of a daily calendar displayed on a screen of a device according to some embodiments.

Referring to FIG. 129 , a daily calendar 12911 is output on the screen of the device 12910 . An indicator 12920 indicating the name of a document may be displayed on the calendar 12911 . For example, assuming that the server 100 generates a document named 'abc.doc' on May 12, 2014 in response to the request of the first device 111 , a region corresponding to May 12, 2014 in the calendar 12911 An indicator 12920 indicating 'abc.doc' may be displayed.

The device 12910 may select the indicator 12920 indicating 'abc.doc' according to the user input received through the user input unit 16510 . When the indicator 12920 indicating 'abc.doc' is selected, the device 12910 may output the job history information 12921 of the document on the screen. For example, at the request of the first device 111, the server 100 uses the fourth program to create a document named 'abc.doc' having a size of 54 KB (kilobyte) on May 12, 2014. Assuming that it is stored at 12:28:04 pm, the job history information 12921 includes 'abc.doc, text, fourth program, first device, May 12, 2014 12:28:04 pm, 54 KB'. can be output. Meanwhile, the device 12910 may output the job history information 12921 of the document on the screen as a separate pop-up window.

Also, an indicator 12922 capable of outputting a document to the screen of the device 12910 may be displayed in the job history information 12921 of the document. For example, when the indicator 12922 capable of outputting a document according to a user input received through the user input unit 16510 is selected, the device 12910 displays a pop-up window separate from the calendar 12911 to the first device ( 111) can be printed on the screen.

Similarly, a plurality of indicators indicating the name of a document may be displayed on one calendar 12911 . For example, assuming that the server 100 reads a document named 'abc.doc' on May 20, 2014 in response to the request of the second device 112, the calendar 12911 corresponds to May 12, 2014. An indicator 12930 indicating 'abc.doc' may be displayed in the area.

The device 12910 may select the indicator 12930 indicating 'abc.doc' according to the user input received through the user input unit 16510 . When the indicator 12930 indicating 'abc.doc' is selected, the device 12910 may output the job history information 12931 of the document on the screen. For example, according to the request of the second device 112, the server 100 uses the fourth program to create a document named 'abc.doc' having a size of 54 KB (kilobyte) on May 20, 2014. Assuming that it is viewed at 08:46:11 PM, the job history information 12931 includes 'abc.doc, text, fourth program, second device, May 20, 2014 08:46:11 PM, 54 KB'. can be output. Meanwhile, the device 12910 may output the job history information 12931 of the document to the screen as a separate pop-up window.

Also, an indicator 12932 capable of outputting a document to the screen of the device 12910 may be displayed in the work history information 12931 of the document. For example, when an indicator 12932 capable of outputting a document according to a user input received through the user input unit 16510 is selected, the device 12910 displays a pop-up window separate from the calendar 12911 to the second device ( 112) can output the read document to the screen.

130 is a diagram illustrating another example of a daily calendar displayed on a screen of a device according to some embodiments.

Referring to FIG. 130 , a daily calendar 13011 is output on the screen of the device 13010 . An indicator 13020 indicating a device name may be displayed on the calendar 13011 . For example, assuming that the first device 111 creates a document on May 12, 2014, an indicator 13020 indicating the 'first device' may be displayed in an area corresponding to May 12, 2014 of the calendar 13011. there is.

The device 13010 may select the indicator 13020 indicating the 'first device' according to the user input received through the user input unit 16510 . When the indicator 13020 indicating the 'first device' is selected, the device 13010 may output the job history information 13021 of the document on the screen. For example, at the request of the first device 111, the server 100 uses the fourth program to create a document named 'abc.doc' having a size of 54 KB (kilobyte) on May 12, 2014. Assuming that it is stored at 12:28:04 pm, the job history information 13021 includes 'abc.doc, text, fourth program, first device, May 12, 2014 12:28:04 pm, 54 KB'. can be output. Meanwhile, the device 13010 may output the job history information 13021 of the document to the screen as a separate pop-up window.

Also, an indicator 13022 capable of outputting a document to the screen of the device 13010 may be displayed in the work history information 13021 of the document. For example, when the indicator 13022 capable of outputting a document according to a user input received through the user input unit 16510 is selected, the device 13010 displays a pop-up window separate from the calendar 13011 to the first device ( 111) can be printed on the screen.

Similarly, a plurality of indicators indicating device names may be displayed on one calendar 13011 . For example, assuming that the server 100 reads a document named 'abc.doc' on May 20, 2014 in response to the request of the second device 112 , the calendar 13011 corresponds to May 12, 2014 An indicator 13030 indicating a 'second device' may be displayed in the area.

The device 13010 may select the indicator 13030 indicating the 'second device' according to the user input received through the user input unit 16510 . When the indicator 13030 indicating the 'second device' is selected, the device 13010 may output the job history information 13031 of the document on the screen. For example, according to the request of the second device 112, the server 100 uses the fourth program to create a document named 'abc.doc' having a size of 54 KB (kilobyte) on May 20, 2014. Assuming that it is read at 08:46:11 pm, the job history information 13031 includes 'abc.doc, text, fourth program, second device, May 20, 2014 08:46:11 pm, 54 KB'. can be output. Meanwhile, the device 13010 may output the job history information 13031 of the document to the screen as a separate pop-up window.

In addition, an indicator 13032 capable of outputting a document to the screen of the device 13010 may be displayed in the work history information 13031 of the document. For example, when an indicator 13032 capable of outputting a document according to a user input received through the user input unit 16510 is selected, the device 13010 displays a pop-up window separate from the calendar 13011 to the second device ( 112) can output the read document to the screen.

Hereinafter, with reference to FIGS. 131a to 140 , the server 110 generates a document according to the request of the first device 111 , and the server 110 edits the document according to the request of the second device 112 . In this case, an example in which the server 110 links job history information to the user's calendar will be described.

131A to 131C illustrate a case in which a server creates a document according to a request of a first device and the server edits a document according to a request of a second device, according to some embodiments, the server displays job history information in the user's calendar It is a flowchart showing an example of interworking.

131A to 131C show that the first device 111 requests the server 110 to generate a document, and the second device 112 requests the server 110 to edit the document for convenience of explanation. However, the present invention is not limited thereto. For example, the first device 111 may request the server 110 to generate a document, and the first device 111 may request the server 110 to edit the document.

Also, there is no limit to the number of devices. If it is assumed that the number of devices requesting a document operation is N (N is a plurality of 3 or more), the operation of the first device 111 or the operation of the second device 112, which will be described below, is the operation of the third device 113 . ) to at least one of the Nth device.

S13110 to S13120 of FIG. 131A correspond to S10410 to S10420 of FIG. 104 . Therefore, even if omitted below, the contents described above with reference to FIGS. 104 to 120 may be applied to the contents to be described later with reference to S13110 to S13120 of FIG. 131A .

In S13110, the first device 111 executes the server connection program. In order for a user to request a document work from the server 100 , the first device 111 may execute a server access program. For example, the user of the first device 111 may execute a server access program and input his/her ID/password.

In S13111 , the first device 111 transmits information requesting document work to the server 110 .

In S13112 , the server 110 generates a document according to the request received from the first device 111 .

In S13113 , the server 110 transmits information about the work screen of the document to the first device 111 .

In S13114, the first device 111 outputs the work screen of the received document.

In S13115, the server 110 stores the document.

In S13116, the server 110 acquires the job history information of the document. For example, the server 110 may acquire work history information of the document at the time of storing the document. For example, the server 100 may store the obtained work history information in a storage space corresponding to the user's account of the first device 111 .

In S13117, the server 110 links the work history information to the calendar by using the time information included in the obtained work history information.

In S13118 , the second device 112 requests the server 110 to transmit information to be displayed on the calendar. For example, the second device 112 executes a calendar output program installed in the second device 112 , authenticates the user using the input user account, and then transmits information to be displayed on the calendar to the server 110 . can request

In S13119 , the server 110 transmits information to be displayed on the calendar to the second device 112 .

In FIG. 131A, when the second device 112 requests the server 110 to transmit information to be displayed on the calendar in S13118, the server 110 transmits information to be displayed on the calendar in S13119. not limited For example, even if there is no transmission request from the second device 112 , information to be displayed on the calendar may be transmitted (eg, pushed) to the second device 112 .

In S13120, the second device 112 outputs the calendar on the screen.

In S13121, the second device 112 executes the server connection program. In order for a user to request a document work from the server 100 , the second device 112 may execute a server access program. For example, the user of the second device 112 may execute a server access program and input his/her ID/password.

In S13122 , the second device 112 transmits information for requesting document work to the server 110 .

In S13123, the server 110 executes the document.

In S13124 , the server 110 transmits information about the work screen of the document to the second device 112 .

In S13125, the second device 112 outputs the work screen of the document.

In S13126 , the second device 112 transmits the editing request information of the document to the server 110 . For example, when the second device 112 receives a user input for editing a document through the user input unit 16510, the second device 112 transmits the document editing request information according to the received user input to the server ( 110).

In S13127, the server 110 edits the document.

In S13128 , the server 110 transmits information about the work screen of the edited document to the second device 112 .

In S13129, the server 110 stores the edited document, and in S13130, the second device 112 outputs the edited document to the screen.

Hereinafter, an example in which the server 110 edits a document will be described with reference to FIGS. 132 to 133 .

132 to 133 are diagrams for implementing examples in which the server 110 edits a document according to some embodiments.

132 to 133 , the second device 112 receives the work screens 13210 and 13310 of the document from the server 110 and displays them on the screen. The second device 112 receives a user input for editing a document through the user input unit 16510 . For example, the user input may be for adding ( 13220 ) new content to the document, or for deleting ( 13320 ) some or all of the content of the document. Meanwhile, although not shown in the drawings, the user input may be for changing some or all of the contents of the document.

Referring to FIG. 132 , upon receiving a user input for adding new content to a document from the second device 112 , the second device 112 transmits edit request information of a document requesting addition of new content to the server 110 . , and the server 110 transmits to the second device 112 a work screen 13210 of a document with new content added (13220) according to the received edit request information.

Referring to FIG. 133 , upon receiving a user input for deleting some of the contents of the document from the second device 112 , the second device 112 transmits editing request information of the document requesting deletion of some contents to the server 110 . ), and the server 110 transmits, to the second device 112 , the work screen 13310 of the document in which some contents are deleted (13320) according to the received edit request information.

Referring back to FIG. 131C , in S13131 , the server 110 acquires work history information of the document. For example, the server 110 may acquire the work history information of the document at the time when the editing of the document is finished (ie, the time at which the document is stored). Hereinafter, an example in which the server 110 obtains work history information of a document will be described with reference to FIG. 134 .

134 is a diagram for explaining an example in which the server 110 obtains job history information of a document according to some embodiments.

As described above with reference to FIGS. 132 to 133 , upon receiving the edit request information of the document, the server 110 may add new content to the document, or change or delete some or all of the content of the document. When the server 110 stores the document after adding new content to the document or changing or deleting some or all of the content of the document, the server 110 determines that the document has been edited.

When the document is saved after editing, the server 110 acquires the job history information of the document. In other words, the server 110 acquires information generated as the document is edited.

For example, after the server 110 executes a document named 'abc.doc' using the second program (?), the document is edited according to a document editing request received from the second device 112 . And, if the edited document is stored at 09:11:43 pm on May 14, 2014, and the size of the document stored after editing is 1084 KB (kilobyte), the server 110 is 'abc.doc, text, second At least one of the program, the second device, and May 14, 2014 09:11:43, 1084KB' may be acquired as work history information.

Meanwhile, as described above with reference to FIG. 106, the job history information of a document requiring a high degree of security may be additionally encrypted and stored.

Referring back to FIG. 131C , in S13132 , the server 110 links the job history information to the calendar by using the time information included in the acquired job history information. For example, the server 110 links the job history information acquired in S13116 to the calendar in S13117, and additionally links the job history information acquired in S13131 to the calendar in S13132.

In S13133 , the first device 111 requests the server 110 to transmit information to be displayed on the calendar. For example, the first device 111 may request the server 110 to transmit job history information to be output on the screen of the device when an indicator to be displayed on the calendar or an indicator displayed on the calendar is selected.

In S13134 , the server 110 transmits information to be displayed on the calendar to the first device 111 .

In S13135, the first device 111 outputs the calendar on the screen.

In FIG. 131c , when the first device 111 requests the server 110 to transmit information to be displayed on the calendar in S13133, the server 110 transmits information to be displayed on the calendar in S13134. not limited For example, even if there is no transmission request from the first device 111 , the server 110 may transmit (eg, push) information to be displayed on the calendar to the first device 111 .

The contents to be described later with reference to S13136 to S13138 correspond to the contents described above with reference to S13133 to S13135. In other words, the second device 112 requests the server 110 to transmit information to be displayed on the calendar, receives information to be displayed on the calendar from the server 110 , and outputs the calendar on the screen. Therefore, even if omitted below, the contents described above with reference to S13133 to S13135 may be applied to the contents to be described later with reference to S13136 to S13138.

In S13136 , the second device 112 requests the server 110 to transmit information to be displayed on the calendar.

In S13137 , the server 110 transmits information to be displayed on the calendar to the second device 112 .

In S13138, the second device 112 outputs the calendar on the screen.

A specific example of the contents described above with reference to S13132 to S13138 of FIG. 131C will be described later with reference to FIGS. 135 to 140 .

135 is a flowchart illustrating an example in which the server 110 links job history information of a document to a calendar, according to some embodiments.

The flowchart shown in FIG. 135 corresponds to the detailed flowchart of S13132 of FIG. 131c.

In S13510 , the server 110 acquires editing time information of the document included in the job history information obtained by editing the document based on the job request from the second device 112 . For example, according to the example described above with reference to FIG. 134 , the server 110 acquires '2014.05.14, 09:11:43 PM' from the job history information.

Hereinafter, an example of the job history information obtained by the server 110 will be described with reference to FIGS. 136 to 137 .

136 to 137 are diagrams illustrating an example of work history information of a document according to some embodiments.

The job history information 13610 of the document shown in FIG. 136 is an example updated from the job history information 10810 of the document shown in FIG. 108 . In other words, the job history information 10810 of the document shown in FIG. 108 means the job history information 10810 generated when the server receiving the document job request from the device generates the document. Meanwhile, the job history information 13610 of the document shown in FIG. 136 means that new job history information 13620 and 13630 are added as the server creates and edits the document.

Referring to FIG. 136 , the server 110 may arrange the acquired job history information based on the document name 13611 .

The job history information 13710 of the document shown in FIG. 137 is an example updated from the job history information 10910 of the document shown in FIG. In other words, the job history information 10910 of the document shown in FIG. 109 means the job history information 10910 generated when the server receiving the document job request from the device generates the document. Meanwhile, the job history information 13710 of the document shown in FIG. 137 means that new job history information 13720 and 13730 are added as the server creates and edits the document.

Referring to FIG. 137 , the server 110 may arrange the obtained work history information based on the name 13711 of the work device.

Referring back to FIG. 135 , in S13520 , the server 110 links the job history information to the user's calendar based on the editing time information of the document. Hereinafter, an example in which the server 110 links job history information to a user's calendar will be described with reference to FIG. 138 .

138 is a flowchart illustrating an example in which the server 110 links job history information to a user's calendar, according to some embodiments.

In S13810, the server 110 acquires the previously created user's calendar. Here, the pre-generated user's calendar means a calendar created by linking the work history information obtained by the server 110 to the calendar in S13117 of FIG. 131A .

In S13820, the server 110 generates an indicator to be displayed on the calendar based on any one of the name of the document included in the work history information, the program used for editing the document, and the name of the device that edited the document. Here, the job history information refers to the job history information obtained in S13131 of FIG. 131C . For example, the server 110 may determine any one of the name of the document, the program used for editing the document, and the name of the device that edited the document as the item indicated by the indicator, and generate the indicator based on the determined item. there is.

In S13830, the server 110 determines the job history information to be displayed on the calendar based on the generated indicator.

In S13840 , the server 110 adds and displays an indicator to an area corresponding to a date or time indicating when a document is edited in the calendar.

139 is a diagram illustrating an example of a daily calendar displayed on a screen of a device according to some embodiments.

Referring to FIG. 139 , a daily calendar 13911 is output on the screen of the device 13910 . The calendar 13911 may include an area 13912 indicating dates and an indicator 13913 through which a user can designate a desired date. Also, the calendar 13911 may include an indicator 13914 capable of displaying a calendar corresponding to the date of 'today'. In addition to the above-described indicators, the calendar 13911 may be included without limitation as long as it is an indicator that allows the user to control the display type of the calendar.

An indicator 13920 indicating the name of a document may be displayed on the calendar 13911 . For example, assuming that the server 100 edits a document named 'abc.doc' on May 14, 2014 in response to the request of the first device 111, the calendar 13911 corresponds to May 12, 2014. An indicator 13920 indicating 'abc.doc' may be displayed in the area.

The device 13910 may select the indicator 13920 indicating 'abc.doc' according to the user input received through the user input unit 16510 . When the indicator 13920 indicating 'abc.doc' is selected, the device 13910 may output the job history information 13921 of the document on the screen. For example, according to the request of the second device 112, the server 100 uses the fourth program to create a document named 'abc.doc' having a size of 1084 KB (kilobyte) on May 14, 2014. Assuming that the edit was made at 09:11:43 PM, the job history information 13921 includes 'abc.doc, text, fourth program, second device, May 14, 2014 09:11:43 PM, 1084 KB'. can be output. Meanwhile, the device 13910 may output the job history information 13921 of the document to the screen as a separate pop-up window.

Also, indicators 13922 and 13923 for outputting a document to the screen of the device 13910 may be displayed in the work history information 13921 of the document. The indicator 13922 may be an indicator indicating an original document at the time of document creation or a document prior to the current job, and the indicator 13923 may be an indicator indicating a current edited document.

The indicator 13923 indicating the edited document may be displayed to be distinguished from the indicator 13922 indicating the original document or the document before the current work. For example, in the case of the indicator 13923 of the edited document, a border line may be additionally displayed on the indicator 13922 indicating the original document or the document before the current work. For example, when an indicator 13922 or 13923 capable of outputting a document according to a user input received through the user input unit 16510 is selected, the device 13910 displays the original document as a pop-up window separate from the calendar 13911 . Alternatively, the document edited by the second device may be output to the screen.

Similarly, a plurality of indicators indicating the name of a document may be displayed on one calendar 13911 . For example, assuming that the server 100 edits a document named 'xyz.doc' on May 12, 2014 in response to the request of the third device 113, the calendar 13911 corresponds to May 12, 2014. An indicator 13930 indicating 'xyz.doc' may be displayed in the area.

The device 13910 may select the indicator 13930 indicating 'xyz.doc' according to a user input received through the user input unit 16510 . When the indicator 13930 indicating 'xyz.doc' is selected, the device 13910 may output the job history information 13931 of the document on the screen. For example, according to the request of the third device 113, the server 100 uses the fourth program to create a document named 'xyz.doc' having a size of 2387 KB (kilobyte) on May 12, 2014. Assuming that the edit was made at 09:14:03 AM, the job history information 13931 includes 'xyz.doc, text, fourth program, third device, May 12, 2014 09:14:03 AM, 2387 KB' can be output. Meanwhile, the device 13910 may output the job history information 13931 of the document to the screen as a separate pop-up window.

Also, in the work history information 13931 of the document, indicators 13932 and 13933 for outputting the document to the screen of the device 13910 may be displayed. The indicator 13932 may be an indicator indicating an original document at the time of document creation or a document prior to the current job, and the indicator 13933 may be an indicator indicating a current edited document.

The indicator 13933 indicating the edited document may be displayed to be distinguished from the indicator 13932 indicating the original document or the document before the current work. For example, in the case of the indicator 13933 of the edited document, a border line may be additionally displayed on the indicator 13932 indicating the original document or the document before the current work. When an indicator 13932 or 13933 capable of outputting a document is selected according to a user input received through the user input unit 16510 , the device 13910 displays an original document or a third device as a pop-up window separate from the calendar 13911 . The edited document can be printed on the screen.

140 is a diagram illustrating another example of a daily calendar displayed on a screen of a device according to some embodiments.

Referring to FIG. 140 , a daily calendar 14011 is output on the screen of the device 14010 . The calendar 14011 shown in FIG. 140 has the same frame as the calendar 13911 shown in FIG. 56 . Accordingly, the contents described above with reference to FIG. 139 with respect to indicators that may be displayed on the calendar 14011 may be equally applied to FIG. 140 .

An indicator 14020 indicating a device name may be displayed on the calendar 14011 . For example, assuming that the server 100 edits a document on May 14, 2014 in response to the request of the second device 112 , a 'second device' is added to the area corresponding to May 12, 2014 of the calendar 14011. An indicating indicator 14020 may be displayed.

The device 14010 may select the indicator 14020 indicating the 'second device' according to the user input received through the user input unit 16510 . When the indicator 14020 indicating the 'second device' is selected, the device 14010 may output the job history information 14021 of the document on the screen. For example, according to the request of the second device 112, the server 100 uses the fourth program to create a document named 'abc.doc' having a size of 1084 KB (kilobyte) on May 14, 2014. Assuming that the edit is made at 09:11:43 PM, the job history information 14021 includes 'abc.doc, text, fourth program, second device, May 14, 2014 09:11:43 PM, 1084 KB'. can be output. Meanwhile, the device 14010 may output the job history information 14021 of the document to the screen as a separate pop-up window.

Also, indicators 14022 and 14023 for outputting a document to the screen of the device 14010 may be displayed in the job history information 14021 of the document. The indicator 14022 may be an indicator indicating an original document at the time of document creation or a document prior to the current job, and the indicator 14023 may be an indicator indicating a current edited document.

The indicator 14023 indicating the edited document may be displayed to be distinguished from the indicator 14022 indicating the original document or the document before the current job. For example, in the case of the indicator 14023 of the edited document, a border line may be additionally displayed on the indicator 14022 indicating the original document or the document before the current work. When the indicator 14022 or 14023 capable of outputting a document is selected according to a user input received through the user input unit 16510 , the device 14010 displays the original document or the second device as a pop-up window separate from the calendar 14011 . The edited document can be printed on the screen.

Similarly, a plurality of indicators indicating device names may be displayed on one calendar 14011 . For example, assuming that the server 100 edits a document named 'xyz.doc' on May 12, 2014 in response to the request of the third device 113, the calendar 14011 corresponds to May 12, 2014. An indicator 14030 indicating a 'third device' may be displayed in the area.

The device 14010 may select the indicator 14030 indicating the 'third device' according to the user input received through the user input unit 16510 . When the indicator 14030 indicating the 'third device' is selected, the device 14010 may output the job history information 14031 of the document on the screen. For example, according to the request of the third device 113, the server 100 uses the fourth program to create a document named 'xyz.doc' having a size of 2387 KB (kilobyte) on May 12, 2014 am Assuming that it is viewed at 09:14:03, in the job history information 14031, 'xyz.doc, text, the fourth program, the third device, 09:14:03 am, 2387 KB on May 12, 2014' can be output. Meanwhile, the device 14010 may output the job history information 14031 of the document to the screen as a separate pop-up window.

In addition, indicators 14032 and 14033 for outputting a document to the screen of the device 14010 may be displayed in the work history information 14031 of the document. The indicator 14032 may be an indicator indicating an original document at the time of document creation or a document prior to the current job, and the indicator 14033 may be an indicator indicating a current edited document.

The indicator 14033 indicating the edited document may be displayed to be distinguished from the indicator 14032 indicating the original document or the document before the current job. For example, in the case of the indicator 14033 of the edited document, a border line may be additionally displayed on the indicator 14032 indicating the original document or the document before the current work. When the indicator 14032 or 14033 capable of outputting a document is selected according to a user input received through the user input unit 16510 , the device 14010 displays the original document or the second device as a pop-up window separate from the calendar 14011 . The edited document can be printed on the screen.

141A to 141D show that when a server generates a document according to a request of a first device and the server provides a view of a document and edits a document according to a request of a second device, the server is a user It is a flowchart showing another example of linking job history information to the calendar of

S14110 to S14134 of FIGS. 141a to 141c are a process in which the server 110 links work history information to the user's calendar when the server 110 provides a document reading according to the request of the second device 112 . , which is the same as S12110 to S12134 of FIGS. 121a to 121c. Accordingly, detailed descriptions of S14110 to S14134 of FIGS. 141A to 141C will be omitted below.

On the other hand, S14135 to S14152 of FIGS. 141c to 141d are processes in which the server 110 links the work history information to the user's calendar when the server 110 edits a document according to the request of the second device 112 , which is the same as S13121 to S13138 of FIGS. 131b to 131c. Accordingly, detailed descriptions of S14135 to S14152 of FIGS. 141C to 141D will be omitted below.

142 to 143 are diagrams illustrating examples of calendars output on a screen of a device according to some embodiments.

Referring to FIG. 142 , an example of the calendar 14220 output on the screen of the device 14210 is illustrated. For convenience of explanation, in FIG. 142 , it is illustrated that the monthly calendar 14220 is output on the screen of the device 14210 , but the present invention is not limited thereto.

If the server 100 performs an operation on a plurality of documents on the same date, an indicator 14230 indicating the number of documents on which the operation is performed may be displayed on the calendar 14220 . For example, if it is assumed that the server 100 performs an operation on a total of 9 documents on 2014.01.10, it indicates that the operation is performed on 9 documents in an area indicating 2014.01.10 in the calendar 14220. An indicator 14230 may be displayed.

The device 14210 may select an indicator 14230 indicating the number of documents on which an operation is performed according to a user input received through the user input unit 16510 . When the indicator 14230 indicating the number of documents on which the operation is performed is selected, the device 14210 may output a list 14240 of documents on which the operation has been performed on the screen.

After the list 14240 of the documents on which the work is performed is output, if any one 14241 of the documents included in the list 14240 is selected, the device 14210 displays the work history information 14250 of the selected document. It can be printed on the screen. Indicators 14251 and 14252 capable of outputting a document to the screen of the device 14210 may be displayed in the job history information 14250 of the document. Here, the indicator 14251 may be an indicator indicating an original document at the time of document creation or a document prior to a current job, and the indicator 14252 may be an indicator indicating a current edited document.

Referring to FIG. 143 , another example of a calendar 14320 is output on the screen of the device 14310 . The document list 14340 in the calendar 14320 illustrated in FIG. 143 may have a different shape from the document list 14240 in the calendar 14220 illustrated in FIG. 142 . For example, the document list 14340 , the document work history information 14350 , and the indicators 14330 , 14351 , and 14352 that may be output on the screen of the device 14310 may be output in various shapes or colors.

144 to 145 are diagrams illustrating still other examples of a calendar output on a screen of a device according to some embodiments.

Referring to FIG. 144 , an example of a calendar 14420 output on the screen of the device 14410 is illustrated. In FIG. 144 , for convenience of explanation, it is illustrated that the monthly calendar 14420 is output on the screen of the device 14410 , but the present invention is not limited thereto.

If the server 100 performs an operation on a plurality of documents according to a request by the same device on the same date, an indicator 14430 indicating the number of documents on which the operation is performed is displayed on the calendar 14420 can be For example, in response to the request of the first device 111, assuming that the server 100 performs a task on a total of three documents on January 11, 2014, in the area indicating January 11, 2014 in the calendar 14420 An indicator 14430 indicating that the work has been performed on the three documents may be displayed.

The device 14410 may select the indicator 14430 according to a user input received through the user input unit 16510 . When the indicator 14430 is selected, the device 14410 may output a list 14440 of documents on which work is performed on the screen.

After the list 14440 of the documents on which the work is performed is output, when any one 14441 of the documents included in the list 14440 is selected, the device 14410 displays the work history information 14450 of the selected document. It can be printed on the screen. Indicators 14451 and 14452 for outputting a document to the screen of the device 14410 may be displayed in the work history information 14450 of the document. Here, the indicator 14451 may be an indicator indicating an original document at the time of document creation or a document prior to the current job, and the indicator 14452 may be an indicator indicating a current edited document.

Referring to FIG. 145 , another example of a calendar 14520 is output on the screen of the device 14510 . The document list 14540 in the calendar 14520 illustrated in FIG. 145 may have a different shape from the document list 14440 in the calendar 14420 illustrated in FIG. 144 . For example, the document list 14540 , the document work history information 14550 , and the indicators 14530 , 14551 , and 14552 that may be output on the screen of the device 14510 may be output in various shapes or colors.

146 is a diagram for explaining an example in which a mode of a calendar is switched, according to some embodiments.

Referring to (a) of FIG. 146 , an example of the first mode calendar 14620 output on the screen of the device 14610 is illustrated. Here, the first mode calendar 14620 may be linked with information related to the user's daily life. For example, the first mode calendar 14620 may be linked with information about a user's schedule or plan. Also, the first mode calendar 14620 may be linked with history information in which a user uses a function of the device 14610 . For example, the first mode calendar 14620 includes a history of calls made by the user using the device 14610 , a history of taking pictures using a camera provided in the device 14610 , and a memo program installed in the device 14610 . It may be linked with a history of creating a memo using , a history of sending and receiving messages or e-mails using the device 14610, a history of using an SNS service using an SNS program installed in the device 14610, and the like.

Referring to (b) of FIG. 146 , an example of the second mode calendar 14630 output on the screen of the device 14610 is illustrated. Here, the second mode calendar 14630 may be linked with work history information of a document.

Indicators 14640 and 14650 for switching modes of the calendars 14620 and 14630 may be displayed on the calendars 14620 and 14630 output to the device 14610 . For example, an indicator 14640 for requesting to output the first mode calendar 14620 and an indicator 14650 for requesting to output the second mode calendar 14630 may be displayed on the screen of the device 14610. there is.

Also, schedule information related to job history information displayed on the second mode calendar 14630 may be displayed on the first mode calendar 14620 output to the device 14610 . For example, suppose that a user worked on the document '2013 Performance Report.doc' on December 23, 2013, and a meeting schedule related to the document '2013 Performance Report.doc' exists on January 3, 2014. do. In this case, in the field on January 2, 2014 on the first mode calendar 14620, an indicator indicating that '2013 performance report.doc' should be reviewed may be displayed.

Hereinafter, with reference to FIGS. 147 to 149 , when the users of the devices 110 are different from each other, and the server 100 performs a document task based on a request from the devices 110 , the server 100 An example of linking job history information to a user's calendar will be described.

147 is a view for explaining an example in which the server links work history information to the user's calendar when the users of devices are different and the server performs a document task based on a request of the devices, according to some embodiments am.

Referring to FIG. 147 , the system 1 includes a server 100 and devices 110 . Here, the devices 110 refer to devices of different users. For example, the first device 111 is the device of the first user 120 , the second device 112 is the device of the second user 121 , and the N-th device 114 is the device of the M-th user 122 . It may be a device.

Compared with the example described above with reference to FIG. 84 , the difference is that the subject performing the document operation in FIG. 147 is the server 100 , not the devices 110 . In other words, in FIG. 84 , a program used for document work is executed on the devices 110 , but in FIG. 147 , a program used for document work is executed on the server 100 .

The server 100 of FIG. 147 executes a program used for document work installed in the server 100 . therefore. Even if a program used for document work is not installed in the device, the first user 120 may perform document work by accessing the server 100 from the device. Since the subject performing the document work is the server 100 , the server 100 may obtain the work history information of the document from the server 100 without receiving the work history information of the document from the devices 110 .

On the other hand, the devices 110 of FIG. 101 do not perform the document work, but request the server 100 to work on the document. At least one of the devices 110 requests the server 100 to work on the document. For example, the first device 111 of the first user 120 requests the server 100 to work on a document. In the same manner, the second device 112 of the second user 121 to the Nth device 114 of the third user 122 request the server 100 to work on the document.

The server 100 receives a document work request from at least one of the devices 110 and performs the document work. After the execution of the document job is completed, the server 100 acquires job history information of the document.

The server 100 links the acquired job history information 130 to the user's calendar. Then, the server 100 transmits the information 140 to be displayed on the calendar to the devices 110 . Here, the information 140 to be displayed on the calendar means information to be displayed on the output calendar when the calendar is output on the screen of the device. For example, the information 140 to be displayed on the calendar may include job history information to be output on the screen of the device when an indicator to be displayed on the calendar or an indicator displayed on the calendar is selected.

In this case, the server 100 may transmit the information 140 to be displayed on the calendar only to a device that has requested transmission of the information 140 to be displayed on the calendar among the devices 110 . For example, the first device 111 executes a program for outputting a calendar, and authenticates that the first user is the first user based on the user account input through the user input unit 16510, thereby providing the server 100 with the first user ( The transmission of information 140 to be displayed on the calendar of 120 may be requested.

Meanwhile, even if there is no request from the first device 111 , the server 100 may automatically transmit (eg, push) the information 140 to be displayed on the calendar to the first device 111 . . For example, if there is a history in which the first device 111 previously requested transmission of the information 140 to be displayed on the calendar of the first user 120 , the server 100 may then The information 140 to be displayed on the calendar of the first user 120 may be automatically transmitted even if there is no request from the .

Hereinafter, an example in which the server 100 links job history information to a user's calendar will be described with reference to FIG. 148 .

148 is a flowchart illustrating an example in which a server links job history information to a user's calendar, according to some embodiments.

In S14810, the server 100 acquires the work history information of the document worked in the server 100 according to the request of a plurality of users. In other words, the server 100 receives a document work request from devices of a plurality of users, performs the document work, and obtains work history information.

In S14820, the server 100 links the acquired job history information to at least one calendar among a plurality of users by using time information included in the acquired job history information. Here, the time information means information indicating the time when the server 100 worked on the document. For example, assuming that the server 100 creates a document called 'abc.doc' at 12:28:04 pm on May 12, 2014 at the request of the first device 111 of the first user 120, the server ( 100 ) generates an indicator to be displayed on 2014.05.12 in the calendar of the first user 120 , and determines job history information to be output on the screen of the first device 111 as the indicator displayed on 2014.05.12 is selected can In this case, as described above with reference to FIG. 1 , that the server 100 may link only a part of the job history information acquired in S14810 to the user's calendar.

Hereinafter, with reference to FIG. 149 , when the server 100 works on a document in response to a document work request from the first device 111 , the server 100 performs An example of linking job history information to a calendar will be described.

149 is a flowchart illustrating an example in which the server links work history information to the calendar of the first user when the server performs a document work in response to a document work request from the first device, according to some embodiments.

In FIG. 149, for convenience of explanation, it is illustrated that the server 100 works on a document in response to a document work request from the first device 111, but the present invention is not limited thereto. In other words, there is no limit to the number of devices requesting document work. Also, there is no limit to the number of devices that request the server 100 to transmit information to be displayed on the calendar.

In S14910 , the first device 111 transmits information requesting document work to the server 100 . For example, when the user of the first device 111 executes the fourth program and logs in, the first device 111 may transmit information requesting document work to the server 100 . In this case, as a method for the user of the first device 111 to log in to the fourth program, various methods including a method of inputting an ID/password may be used.

In S14911 , the server 100 works on a document based on the information received from the first device 111 . For example, the server 100 may execute a program used for document work in the server 100 , and may work on a document using the program executed in the server 100 . If it is assumed that the document that the server 100 works with is 'abc.doc' and the program used to create, view, or edit 'abc.doc' is the fourth program, the server 100 executes the fourth program. You can run it and create, view or edit 'abc.doc'.

In S14912 , the server 100 transmits information about the work screen of the document to the first device 111 . For example, the server 100 may transmit information about the work screen of the document to the first device 111 whenever a document is worked based on the information received from the first device. In other words, the server 100 may transmit, to the first device 111 , information on the work screen of the document, which is changed whenever the document is worked, by using the program executed in the server 100 .

In S14913, the first device 111 outputs the work screen of the document. For example, the first device 111 may output a work screen of a document based on information about the work screen of the document transmitted from the server 100 .

In S14914, the server 100 acquires the job history information of the document. For example, the server 100 may acquire work history information of a document at a time when execution of a program used for document work is terminated or a document is stored. For example, the server 100 may acquire job history information of 'abc.doc' at the time of storing 'abc.doc' or ending execution of the fourth program. For example, the server 100 may store the obtained work history information in a storage space corresponding to the user's account of the first device 111 .

In S14915, the server 100 links the acquired job history information to the user's calendar by using the time information included in the acquired job history information. For example, assuming that the server 100 stores 'abc.doc' on 2014.05.12 at 12:28:04 pm, the server 100 generates an indicator to be displayed in the area corresponding to 2014.05.12 on the calendar. can do.

In S14916, the first device 111 requests the server 100 to transmit information to be displayed on the calendar. For example, the first device 111 may request the server 100 to transmit job history information to be output on the screen of the device when an indicator to be displayed on the calendar or an indicator displayed on the calendar is selected.

In S14917 , the server 100 transmits information to be displayed on the calendar to the first device 111 .

In S14918, the first device 111 outputs the calendar on the screen. For example, the first device 111 may output a calendar in which the indicator transmitted from the server 100 is displayed on the screen.

In S14919, the second device 112 requests the server 100 to transmit information to be displayed on the calendar. For example, the second device 112 may request the server 100 to transmit job history information to be output on the screen of the device when an indicator to be displayed on the calendar or an indicator displayed on the calendar is selected.

In S14920 , the server 100 transmits information to be displayed on the calendar to the second device 112 .

In S14921, the second device 112 outputs the calendar on the screen. For example, the first device 111 may output a calendar in which the indicator transmitted from the server 100 is displayed on the screen.

Hereinafter, with reference to FIGS. 150 to 161 , when the server 100 authores a document based on a request from the devices 110 , the server 100 links the job history information to the user's calendar An example is explained.

FIG. 150 is a diagram for describing an example in which a server links work history information to a user's calendar when devices perform joint authoring of a document according to some embodiments.

Compared with the example described above with reference to FIG. 87 , the system 1 of FIG. 87 uses a program installed in the device 111 , 112 or 114 , but the system 1 of FIG. 150 uses the device 111 , 112 or 114 . ) connects to the server 100 and uses the fourth program installed in the server 100 . An example of the fourth program may be a cloud-based document processing program such as MS OFFICE 365, GOOGLE DOCS, and the like.

Referring to FIG. 150 , the system 1 includes a server 100 , a first device 111 , a second device 112 , and an N-th device 114 . Here, each of the devices 110 may correspond to devices used by the first user 120 , the second user 121 , and the M-th user 122 , as illustrated in FIG. 84 . Alternatively, all of the devices 110 may correspond to devices used by one user (eg, the first user 120 ), as in another example illustrated in FIG. 2 . That is, the number of users using the devices 110 is not limited by any one.

The first device 111 transmits a request for generating a first document 15040 to the server 100 by using the fourth program. In addition, the second device 112 transmits a generation request 15040 of the second document to the server 100 using the fourth program, and the N-th device 114 uses the fourth program to generate the N-th document. It transmits a creation request 15040 to the server 100 . Accordingly, the server 100 may perform generation 15010 of the first to Nth documents.

In this way, each of the first device 111 to the Nth device 114 transmits 15040 generation requests for the first to Nth document to the server 100 to perform cooperative authoring of the document. can

The server 100 combines the first to Nth documents received from the devices 110 ( 15020 ), and generates a single document 15001 that is a result of the joint authoring ( 15030 ). Accordingly, the contents of the single document 15001 may include the contents of the first document, the contents of the second document, and the contents of the Nth document.

When the single document 15001 is generated, the server 100 may transmit generation history information of the single document 15001 to each of the devices 110 participating in the joint authoring of the single document 15001 . Then, the server 100 transmits the information 15050 to be displayed on the calendar to the devices 110 . Here, the information 15050 to be displayed on the calendar means information to be displayed on the output calendar when the calendar is output on the screen of the device. For example, the information 15050 to be displayed on the calendar may include job history information to be output on the screen of the device when an indicator to be displayed on the calendar or an indicator displayed on the calendar is selected. Here, the job history information may include generation history information of a single document 15001 .

In this case, the server 100 may transmit the information 15050 to be displayed on the calendar only to a device that has requested transmission of the information 15050 to be displayed on the calendar among the devices 110 . For example, the first device 111 executes a program for outputting a calendar, and authenticates that it is the first user 120 based on a user account input through the user input unit 16510 , thereby providing the first device to the server 100 . 1 It is possible to request transmission of information 15050 to be displayed on the calendar of the user 120 .

Meanwhile, even if there is no request from the first device 111 , the server 100 may automatically transmit (eg, push) the information 15050 to be displayed on the calendar to the first device 111 . . For example, if there is a history in which the first device 111 previously requested transmission of the information 15050 to be displayed on the calendar of the first user 120 , the server 100 may then The information 15050 to be displayed on the calendar of the first user 120 may be automatically transmitted even if there is no request from the .

151 is a flowchart illustrating an example in which a server links job history information to a user's calendar, according to some embodiments.

In S15101, the server 100 generates documents such as, for example, a first document, a second document, and an N-th document according to a request of each of the plurality of devices 110 .

In S15102, the server 100 acquires work history information of each of the documents.

In S15103, the server 100 generates a final document based on the connection relationship between the obtained documents. Here, the final document may correspond to the single document 15001 described with reference to FIG. 150 . The connection relationship between documents means an order in which seed documents to be combined into a final document are linked, and may include, for example, an order of a table of contents, an order of a storage date, and the like.

In S15104, the server 100 links the received work history information to the user's calendar by using the time information included in the obtained work history information. Here, the time information means information indicating the time the device worked on the document. For example, the first device 111 reads a document called 'abc.doc' on 2014.05.12. Assume that it is created at 12:28:04 pm, the server 100 generates an indicator to be displayed on 2014.05.12. in the user's calendar of the first device 111, and the indicator displayed on 2014.05.12. is selected. Accordingly, it is possible to determine the job history information to be output on the screen of the first device 111 .

Hereinafter, with reference to FIGS. 152a to 152c, when the first device 111 and the second device 112 perform joint authoring of a document, the server 100 interlocks the work history information with the user's calendar An example is explained.

152A to 152C are flowcharts illustrating an example in which a server links job history information to a user's calendar when a first device and a second device jointly author a document, according to some embodiments.

In FIGS. 152A to 152C , only two of the first device 111 and the second device 112 are illustrated for convenience of description, but the number of devices is not limited. If it is assumed that the number of devices is N (N is a plurality of 3 or more), the operation of the first device 111 or the operation of the second device 112, which will be described below, is the third device 113 to the N-th device. It may be performed in at least one of

In S15200, the first device 111 executes the server connection program. In order for the user to request the server 100 to generate the first document, the first device 111 may execute a server access program. Here, the server access program may correspond to the fourth program. For example, the user of the first device 111 may execute a server access program and input his/her ID/password.

In S15201, the second device 112 executes the server connection program. In order for the user to request the server 100 to generate the second document, the second device 112 may execute a server access program. Here, the server access program may correspond to the fourth program. For example, the user of the second device 112 may execute a server access program and input his/her ID/password.

In S15202 , the first device 111 transmits a request for generating the first document to the server 100 .

In S15203, the server 100 generates a first document.

In S15204, the server 100 stores the first document.

In S15205 , the server 100 transmits information about the first document to the first device 111 .

In S15206, the first device 111 outputs the first document on the screen.

In S15207, the server 100 generates job history information of the first document. For example, the job history information may include the title of the document on which the job was performed, the type of the document, the time the document job was performed, the name of the device performing the document job, the user of the device, the program used for the document job, the size of the document, It can include the type of work. For example, the server 100 may store the acquired job history information in a storage space corresponding to the user's account of the first device 111 and the storage space corresponding to the user's account of the second device 112 . .

In S15208, the server 100 links the job history information to the user's calendar by using the time information included in the job history information of the first document.

In S15209 , the first device 111 requests the server 100 to transmit information to be displayed on the calendar. For example, the first device 111 may request the server 100 to transmit information to be displayed on the calendar after executing the calendar output program installed in the first device 111 and authenticating the user. .

In S15210, the second device 112 requests the server 100 to transmit information to be displayed on the calendar. For example, the second device 112 may request the server 100 to transmit information to be displayed on the calendar after executing the calendar output program installed in the first device 112 and authenticating the user. .

In S15211 , the server 100 transmits information to be displayed on the calendar to the first device 111 .

In S15212 , the server 100 transmits information to be displayed on the calendar to the second device 112 .

In S15213, the first device 111 outputs the calendar on the screen.

In S15214, the second device 112 outputs the calendar on the screen.

In S15215 , the second device 112 transmits a request for generating a second document to the server 100 .

In S15216, the server 100 generates a second document.

In S15217 , the server 100 transmits information about the second document to the second device 112 .

In S15218, the server 100 stores the second document.

In S15219, the second device 112 outputs the second document on the screen.

In S15220, the server 100 generates job history information of the second document. For example, the server 100 may store the acquired job history information in a storage space corresponding to the user's account of the first device 111 and the storage space corresponding to the user's account of the second device 112 . .

In S15221, the server 100 determines a connection relationship between the first document and the second document. Here, the linking relationship between the first document and the second document means the order in which the first document and the second document are linked to combine them into a final document. For example, the storage date and time of the first document and the storage date and time of the second document precede or follow.

In S15222, the server 100 generates a final document by combining the first document and the second document according to the determined connection relationship.

In S15223, the server 100 stores the final document.

In S15224, the server 100 links the job history information to the user's calendar by using the time information included in the job history information of the second document.

In S15225 , the first device 111 requests the server 100 to transmit information to be displayed on the calendar. For example, the first device 111 may request the server 100 to transmit information to be displayed on the calendar after executing the calendar output program installed in the first device 111 and authenticating the user. .

In S15226, the second device 112 requests the server 100 to transmit information to be displayed on the calendar. For example, the second device 112 may request the server 100 to transmit information to be displayed on the calendar after executing the calendar output program installed in the second device 112 and authenticating the user. .

In S15227 , the server 100 transmits information to be displayed on the calendar to the first device 111 .

In S15228 , the server 100 transmits information to be displayed on the calendar to the second device 112 .

In FIG. 152c, when each of the first device 111 and the second device 112 requests the server 100 to transmit information to be displayed on the calendar in S15225 and S15226, the server 100 sends the information to the calendar in S15227 and S15228. Although it has been illustrated that information to be displayed is transmitted to each of the first device 111 and the second device 112 , the present invention is not limited thereto. For example, even if there is no transmission request from the first device 111 or the second device 112, the server 100 transmits the information to be displayed on the calendar to the first device 111 or the second device 112 ( For example, it may be pushed.

In S15229, the first device 111 outputs the calendar on the screen.

In S15230, the second device 112 outputs the calendar on the screen.

153 is a diagram for explaining an example of generating a document in a server according to some embodiments.

First, the first device 111 will be described. The first device 111 executes the fourth program 15301 by accessing the web page “https://samsung-office.com”.

The user may write texts by using the fourth program 15301 executed in the first device 111 . For example, the first device 111 transmits a request for generation of some contents of the patent specification having the invention title of “METHOD FOR CONTROLLING APPLICATION” written by the user through the fourth program 15301 to the server 100 . can When the generation of the patent specification is completed, the first device 111 may store the first document having a web address of “https://samsung-office.com/draft specification 1.doc” in the server 100 . Here, the storage date and time of the first document of “draft specification 1.doc” is, for example, “2014. 05. 14, 09:11:43 AM”.

Meanwhile, when the second device 112 is described, the second device 112 executes the fourth program 15302 by accessing the web page “https://samsung-office.com”.

The user may write texts using the fourth program 15302 in the second device 112 . For example, the second device 112 may transmit a request for generating claims of the patent specification written by the user to the server 100 through the fourth program 15302 . When the generation of the claims of the patent specification is completed, the second device 112 may store the second document having a web address of “https://samsung-office.com/draft specification 2.doc” in the server 100 . there is. Here, the storage date and time of the second document of “draft specification 2.doc” is, for example, “2014. 05. 20, PM 08:46:11”.

154 is a diagram for explaining an example of documents generated by a server and job history information of documents, according to some embodiments.

The server 100 stores the first document 15401 “draft specification 1.doc” described in FIG. 153 together with meta information of the first document 15401 “draft specification 1.doc”, and the second document ( 15402) "draft specification 2.doc" is stored together with meta information of the second document 15402 "draft specification 2.doc".

The meta information corresponds to work history information, and may include work date and time information, device name, document creator, table of contents information of the document, and the like.

On the other hand, the first document 15401 “draft specification 1.doc” and the second document 15402 “draft specification 2.doc” are generated for joint authoring of the first device 111 and the second device 112 . are documents.

155 is a diagram for explaining an example of a process in which documents are combined by joint authoring of devices according to some embodiments.

The first device 111 , the second device 112 , and the N-th device 114 each transmit a request for generating a document for joint authoring to the server 100 using the fourth program. Specifically, the first device 111 stores the date “2014. 05. 14, AM 09:11:43” to be saved on <2014. A request for generating a document 15501 related to the content of 02. 14 sales history> may be transmitted to the server 100, and the second device 112 may store the storage date “2014. 05. 12, PM 12:28:04” to be saved on <2014. It is possible to transmit a request for creation of a document 15502 regarding the contents of 05. 12 sales history>, and the N-th device 114 stores the storage date “2014. 05. 28, PM 08:21:11” to be saved on <2014. A request for creation of a document 15503 related to the contents of sales details> on 05. 28 may be transmitted.

The server 100 stores the generated documents 15501 , 15502 and 15503 .

The server 100 determines the connection relationship of the documents 15501 , 15502 and 15503 . In FIG. 155, the connection relationship will be described as based on the storage date and time of the documents 15501, 15502, and 15503.

The document 15501 has a storage date “2014. Since it is stored in the server 100 at 05. 14, 09:11:43”, it has the first priority. The document 15502 has a storage date of “2014. 05. 12, PM 12:28:04” is stored in the server 100, so it has the second priority. Finally, the document 15503 has a storage date of “2014. Since it is stored in the server 100 at 05. 28, PM 08:21:11”, it has the nth priority. Accordingly, the server 100 may determine that the connection relation of the documents 15501 , 15502 and 15503 is the order of the document 15501 , the document 15502 , and the document 15503 .

The server 100 generates a final document 15510 as a result of joint authoring of the first device 111 , the second device 112 , and the N-th device 114 . Specifically, the server 100 may generate the final document 15510 by combining the documents 15501 , 15502 and 15503 using the connection relationship determined for the documents 15501 , 15502 , and 15503 . That is, the server 100 sends documents 15501, 15502, and 15503 in the order of a document 15501 having a first priority, a document 15502 having a second priority, and a document 15503 having an nth priority. By combining the contents of , a final document 15510 can be generated.

After all, the server 100, by joint authoring, <2014. Contents of sales breakdown of 02. 14>, <2014. Contents of sales of 05. 12> and <2014. A final document 15510 in which the contents of the sales details of 05. 28> are sequentially combined may be generated.

156 is a diagram for explaining another example of a process in which documents are combined by joint authoring of devices according to some embodiments.

The first device 111 , the second device 112 , and the N-th device 114 each transmit a request for generating a document for joint authoring to the server 100 using the fourth program. In FIG. 156, a case in which the first device 111, the second device 112, and the N-th device 114 jointly author the document of the patent specification will be described as an example. In general, the order of the table of contents is determined in the patent specification. For example, the order of the large table of contents of the patent specification is known to be “BACKGROUND”, “SUMMARY”, ..., “DETAILED DESCRIPTION”, ..., “WHAT IS CLAIMED IS:”, so we assume this .

The first device 111 may transmit a request for generating a document 15601 “draft patent specification 1.doc” regarding the contents of “BACKGROUND” and “SUMMARY” of the patent specification to the server 100, and the second device ( 112) may transmit a request to create a document 15602 “draft patent specification 2.doc” related to the contents of “DETAILED DESCRIPTION” of the patent specification to the server 100, and the N-th device 114 may transmit the “ A request for generating a document 15603 “draft patent specification 3.doc” regarding the contents of “WHAT IS CLAIMED IS:” may be transmitted to the server 100 .

The server 100 stores the generated documents 15601 , 15602 , and 15603 .

The server 100 determines the connection relationship of the documents 15601 , 15602 , and 15603 . In FIG. 156 , the connection relationship will be described based on the table of contents of contents included in documents 15601 , 15602 and 15603 .

The document 15601 has the first priority because it contains the contents of “BACKGROUND” and “SUMMARY”, which are the most advanced table of contents compared to other documents 15602 and 15603 . Since the document 15602 contains the contents of “DETAILED DESCRIPTION”, which is the table of contents of the next order, it has the second priority. Finally, the document 15603 has the nth priority because it contains the contents of “WHAT IS CLAIMED IS:”, which is the table of contents in the next order. Accordingly, the server 100 may determine that the connection relationship of the documents 15601 , 15602 , and 15603 is the order of the document 15601 , the document 15602 , and the document 15603 .

The server 100 generates a final document 15610 as a result of joint authoring of the first device 111 , the second device 112 , and the N-th device 114 . Specifically, the server 100 may generate the final document 15610 by combining the documents 15601 , 15602 , and 15603 using the connection relationship determined for the documents 15601 , 15602 , and 15603 . That is, the server 100 sends documents 15601, 15602, and 15603 in the order of a document 15601 having a first priority, a document 15602 having a second priority, and a document 15603 having an nth priority. By combining the contents of , a final document 15610 can be created.

After all, the server 100 is a patent specification in which the contents of “BACKGROUND”, “SUMMARY”, ..., “DETAILED DESCRIPTION”, ..., “WHAT IS CLAIMED IS:” are sequentially combined by joint authoring. A final document 15610 of

157A to 157C are flowcharts illustrating an example in which a server links job history information to a user's calendar when a first device and a second device jointly author a document, according to some embodiments.

Although only two of the first device 111 and the second device 112 are illustrated in FIGS. 157A to 157C for convenience of description, the number of devices is not limited. If it is assumed that the number of devices is N (N is a plurality of 3 or more), the operation of the first device 111 or the operation of the second device 112, which will be described below, is the third device 113 to the N-th device. It may be performed in at least one of

In S15700, the first device 111 executes the server connection program. In order for the user to request the server 100 to generate the first document, the first device 111 may execute a server access program. Here, the server access program may correspond to the fourth program. For example, the user of the first device 111 may execute a server access program and input his/her ID/password.

In S15701 , the first device 111 transmits a request for generating the first document to the server 100 .

In S15702, the server 100 generates a first document. Here, the first document means a document in which only the table of contents of the final document to be generated by the server 100 is written in S15720 or a document in which only some pages of all pages of the final document are written.

As an example, assuming that the final document is a document composed of the contents of 'Meeting Purpose', 'Meeting Preparations', and 'Meeting Discussion Contents' and the contents of each table of contents, the first document may contain only the above-mentioned contents. This can be a written document.

As another example, assuming that the final document is a document composed of 1 to 10 pages, the first document may be a document in which contents of 1 to 2 pages of the final document are described.

In S15703, the server 100 stores the first document.

In S15704 , the server 100 transmits information about the first document to the first device 111 .

In S15705, the first device 111 outputs the first document to the screen.

In S15706, the server 100 generates job history information of the first document. For example, the job history information may include the title of the document on which the job was performed, the type of the document, the time the document job was performed, the name of the device performing the document job, the user of the device, the program used for the document job, the size of the document, It can include the type of work. For example, the server 100 may store the obtained work history information in a storage space corresponding to the user's account of the first device 111 .

In S15707, the server 100 links the job history information to the user's calendar by using the time information included in the job history information of the first document.

In S15708 , the first device 111 requests the server 100 to transmit information to be displayed on the calendar. For example, the first device 111 may request the server 100 to transmit information to be displayed on the calendar after executing the calendar output program installed in the first device 111 and authenticating the user. .

In S15709 , the second device 112 requests the server 100 to transmit information to be displayed on the calendar. For example, the second device 112 may request the server 100 to transmit information to be displayed on the calendar after executing the calendar output program installed in the first device 112 and authenticating the user. .

In S15710 , the server 100 transmits information to be displayed on the calendar to the first device 111 .

In S15711 , the server 100 transmits information to be displayed on the calendar to the second device 112 .

In S15712, the second device 112 executes the server connection program. In order for the user to request the server 100 to generate the second document, the second device 112 may execute a server access program. Here, the server access program may correspond to the fourth program. For example, the user of the second device 112 may execute a server access program and input his/her ID/password.

In S15713 , the second device 112 transmits a work request for the second document to the server 100 .

Here, the operation of the second document may include creation of the second document, editing of the second document, or reading of the second document.

In S15714, the server 100 works on the second document based on the first document. Here, the second document refers to a document in which the contents of the table of contents included in the final document to be generated by the server 100 in S15720 are written, or a document in which only some pages of all pages of the final document are written.

As an example, assuming that the final document is a document composed of the contents of 'meeting purpose', 'meeting preparations', and 'meeting discussion contents' and the contents of each table of contents, the server 100 may set the 'meeting purpose' ' You can create a document with the contents of the table of contents.

As another example, assuming that the final document is a document composed of 1 to 10 pages, the server 100 may generate a document in which contents of 3 to 5 pages of the final document are described.

Also, the server 100 may edit the first document generated in S15702. For example, if it is assumed in S15702 that the server 100 generates a document in which the contents of pages 1 and 2 are described, in S15714 the server 100 may modify, add, or delete the contents of pages 1 and 2.

In S15715, the server 100 stores the second document.

In S15716 , the server 100 transmits information about the second document to the second device 112 .

In S15717, the server 100 generates job history information of the second document. For example, the job history information may include the title of the document on which the job was performed, the type of the document, the time the document job was performed, the name of the device performing the document job, the user of the device, the program used for the document job, the size of the document, It can include the type of work. For example, the server 100 may store the obtained work history information in a storage space corresponding to the user's account of the second device 112 .

In S15718, the server 100 outputs the second document to the screen.

In S15719, the server 100 determines a connection relationship between the first document and the second document. Here, the linking relationship between the first document and the second document means the order in which the first document and the second document are linked to combine them into a final document. For example, the storage date and time of the first document and the storage date and time of the second document precede or follow.

In S15720, the server 100 generates a final document by combining the first document and the second document according to the determined connection relationship.

In S15721, the server 100 stores the final document.

In S15722, the server 100 links the job history information to the user's calendar by using the time information included in the job history information of the second document.

In S15723 , the first device 111 requests the server 100 to transmit information to be displayed on the calendar. For example, the first device 111 may request the server 100 to transmit information to be displayed on the calendar after executing the calendar output program installed in the first device 111 and authenticating the user. .

In S15724 , the second device 112 requests the server 100 to transmit information to be displayed on the calendar. For example, the second device 112 may request the server 100 to transmit information to be displayed on the calendar after executing the calendar output program installed in the second device 112 and authenticating the user. .

In S15725 , the server 100 transmits information to be displayed on the calendar to the first device 111 .

In S15726 , the server 100 transmits information to be displayed on the calendar to the second device 112 .

In FIG. 157c, when each of the first device 111 and the second device 112 requests the server 100 to transmit information to be displayed on the calendar in S15723 and S15724, the server 100 sends the information to the calendar in S15725 and S15726. Although it has been illustrated that information to be displayed is transmitted to each of the first device 111 and the second device 112 , the present invention is not limited thereto. For example, even if there is no transmission request from the first device 111 or the second device 112, the server 100 transmits the information to be displayed on the calendar to the first device 111 or the second device 112 ( For example, it may be pushed.

In S15727, the first device 111 outputs the calendar on the screen.

In S15728, the second device 112 outputs the calendar on the screen.

158 is a diagram for explaining another example of a process in which documents are combined by joint authoring of devices according to some embodiments.

The first device 111 , the second device 112 , and the N-th device 114 each transmit a request for generating a document for joint authoring to the server 100 using the fourth program. In FIG. 158, a case in which the first device 111, the second device 112, and the Nth device 114 jointly author the meeting will be described as an example. Also, in FIG. 158, it is assumed that the order of the table of contents of the minutes is designated in the order of <Meeting Purpose>, <Meeting Preparations> (15802), and <Meeting Discussion Contents> (15803). Furthermore, it is assumed that the second device 112 is a device used by the president of the company, the N-th device 114 is a device used by a manager of the company, and the first device 111 is a device used by an employee of the company.

In order to hold a meeting for <meeting purpose> of a specific topic, the president may transmit a request for generating a document 15801 listing the table of contents of the meeting minutes to the server 100 using the second device 112 owned by the president.

As described above with reference to FIGS. 157A to 157C , the information about the document 15801 stored in the server 100 may be transmitted to the N-th device 114 owned by the manager and the first device 111 owned by the employee. there is.

If the <meeting purpose> is set by the president, the contents to be included in the other items of the meeting minutes <meeting preparation> (15802) and <meeting discussion content> (15803) can be prepared by the subordinates of the president.

When the information on the document 15801 is transmitted to the N-th device 114 owned by the manager through the server 100, the manager uses the N-th device 114 to A request for creation of the document 15804 may be transmitted to the server 100 . In addition, when information on the document 15801 is transmitted to the first device 111 owned by the employee through the server 100 , the employee uses the first device 111 to access the <Meeting Discussion Contents> 15803 A request for generating a related document 15805 may be generated to be transmitted to the server 100 .

The server 100 determines the connection relationship of the documents 15801 , 15804 and 15805 . In FIG. 158, the connection relationship will be described based on the table of contents of contents included in the documents 15801, 15804, and 15805.

The document 15801 has the first priority because it includes the contents of <Meeting Purpose>, which is the most advanced table of contents compared to other documents 15804 and 15805. Document 15804 has the second priority because it contains the contents of <Preparation for Meeting> (15802), which is a table of contents in the next order. Finally, the document 15805 has the nth priority because it includes the contents of the <Meeting Discussion Contents> 15803, which is a table of contents in the next order. Accordingly, the server 100 may determine that the linked relationship of the documents 15801 , 15804 , and 15805 is the order of the document 15801 , the document 15804 , and the document 15805 .

The server 100 generates a final document 15810 as a result of joint authoring of the first device 111 , the second device 112 , and the N-th device 114 . Specifically, the server 100 may generate the final document 15810 by combining the documents 15801 , 15804 , and 15805 using the linked relationship determined for the documents 15801 , 15804 , and 15805 . That is, the server 100 sends documents 15801, 15804, and 15805 with a first priority to a document 15801, a document 15804 with a second priority, and a document 15805 with an nth priority. By combining the contents of , a final document 15810 can be created.

After all, the server 100, by joint authoring, the <Meeting Purpose>, <Meeting Preparations> (15802), and the <Meeting Discussion Content> (15803) are combined in this order in the final document 15810 of the meeting minutes. can create

Meanwhile, the server 100 may determine that the connection relationship between the documents 15801 , 15804 , and 15805 is based on the title of the author who generated the documents 15801 , 15804 and 15805 .

Specifically, the document 15801 has the first priority since it was created by the president who is the highest rank compared to the other documents 15804 and 15805. Since the document 15804 was created by a manager who is the next in rank, it has the second priority. Finally, document 15805 has the nth priority because it was created by the employee who is the next in rank. Accordingly, the server 100 may determine that the linked relationship of the documents 15801 , 15804 , and 15805 is the order of the document 15801 , the document 15804 , and the document 15805 . Accordingly, the server 100 processes the documents 15801, 15804, and 15805 in the order of the document having the first priority 15801, the document having the second priority 15804, and the document having the nth priority 15805. ), a final document 15810 can be created.

159 is a view for explaining an example of generating a final document by joint authoring of the first device, the second device, and the Nth device according to some embodiments.

In order to perform joint authoring, the first device 111 transmits a request for generating a first document 15901 “draft 1.doc” to the server 100, and the second device 112 sends a second document 15902 ) transmits a request to generate “draft 2.doc” to the server 100 , and the N-th device 114 transmits a request to generate an N-th document 15903 “draft N.doc” to the server 100 .

The server 100 determines a connection relationship between the first document 15901 to the Nth document 15903 . Here, the connection relationship of the first document 15901 to the Nth document 15903 means the order in which the first document 15901 to the Nth document 15903 are connected in order to combine them into the final document 15910, It has already been described in the above examples.

The server 100 generates a final document 15910 by combining the first document 15901 to the Nth document 15903 according to the determined connection relationship, and stores the generated final document 15910 .

160 is a diagram illustrating an example of displaying a history of documents generated by joint authoring in a monthly calendar displayed on a screen of a device according to some embodiments.

Referring to FIG. 160 , a monthly calendar 16020 is output on the screen of the device 16010 . The calendar 16020 may display an indicator 16030 in the shape of “Δ” indicating a jointly authored document. The number in the indicator 16030 “Δ” shape may indicate how many documents have been combined by joint authoring. For example, the indicator 16030 displayed on 2014.05.04. in the calendar 16020 may indicate that three documents have been combined by joint authoring.

The device 9710 may select the indicator 16030 having a “Δ” shape according to a user input received through the user input unit 16510 . When the indicator 16030 is selected, the device 16010 may output the work history information 16040 of the joint authoring document on the screen.

The work history information 16040 of the co-authored document includes information on the file name “workshop.doc” of the co-authored document, and documents “workshop_1.doc”, “workshop_2.doc” and “workshop_3” combined by co-authoring. It contains information in the list of “.doc”. In addition, the work history information 16040 of the joint authoring document includes information on the creation date and time, creation device, etc. may include For example, in the work history information 16040 of the co-authored document, the creation date and time of “workshop_2.doc” is “2013. 12. 26, 11:40:39 AM,” and the device generating “workshop_2.doc” may include information that is the first device 111 .

The device 16010 may select the item 16050 of “workshop_2.doc” which is a part of the jointly authored document according to the user input received through the user input unit 16510 . When the item 16050 is selected, the device 16010 may output work history information 16060 of the document “workshop_2.doc” corresponding to the item 16050 on the screen.

On the other hand, work history information regarding the joint authoring document may be displayed for other indicators 16070 in the same manner as described above.

161 is a diagram illustrating another example of displaying the histories of documents generated by joint authoring in a monthly calendar displayed on a screen of a device according to some embodiments.

Referring to FIG. 161 , a monthly calendar 16120 is output on the screen of the device 16110 .

The device 16110 may select the indicator 16130 in the shape of “Δ” displayed on 01.06.2014 according to the user input received through the user input unit 16510 . When the indicator 16130 is selected, the device 16110 displays the indicator 16140 on the date of 2014.01.01. and displays the indicator 16150 on the date of 2014.01.28.

When the indicator 16130 is selected, the indicator 16140 and the indicator 16150 displayed together with the indicator 16130 are those displayed to identify the document specified in the indicator 16130 and documents co-authored. That is, the document specified in the indicator 16130 indicated on 01.06.2014, together with the document specified in the indicator 16140 indicated on 01.01.2014 and the document specified in the indicator 16150 indicated on 01.28. document used.

Meanwhile, when the indicator 16130 is selected, the device 16110 may output the work history information 16160 of the joint authoring document on the screen.

The work history information 16160 of the jointly authored document includes information on the file name “party.doc” of the jointly authored document, and documents “party_1.doc”, “party_2.doc” and “party_3” combined by joint authoring. It contains information in the list of “.doc”. In addition, the work history information 16160 of the joint authoring document includes information on the creation date and time, creation device, etc. of each of the documents “party_1.doc”, “party_2.doc”, and “party_3.doc” combined by the joint authoring may include For example, in the work history information 16160 of the joint authoring document, the creation date and time of “party_2.doc” is “2014.01.06., PM 08:14:56”, and the device that generated “party_2.doc” The third device 113 may include information.

The device 16110 may select the item 16170 of “party_2.doc” that is a part of the jointly authored document according to the user input received through the user input unit 16510 . When the item 16170 is selected, the device 16110 may output job history information 16180 of the document “party_2.doc” corresponding to the item 16170 on the screen.

Hereinafter, with reference to FIGS. 162 to 163 , at least one of the plurality of devices 110 corresponds to the server 100 , and performs a function of the server 100 based on a request from the devices 110 . An example in which the device performing the function of the server 100 links work history information to the user's calendar when the device performs a document task will be described.

162 illustrates a device performing a function of a server when at least one of a plurality of devices corresponds to a server, and a device performing a function of a server based on a request of the devices performs a document job, according to some embodiments; A diagram for explaining an example of linking job history information to a user's calendar.

Referring to FIG. 162 , the system 1 includes a first device 111 and a second device 112 to an Nth device 114 . Here, the first device 111 means a device that performs the function of the server 100 of FIG. 99 .

At least one of the second device 112 to the N-th device 114 requests the first device 111 to work on the document, and the first device 111 generates the document job history information 130 . For example, the second device 112 requests the first device 111 to work on a document, and the first device 111 generates work history information of the document. In the same manner, the third device 113 to the N-th device 114 requests the first device 111 to work on the document, and the first device 111 generates the work history information 130 of the document. .

The first device 111 links the generated job history information to the user's calendar. In addition, the first device 111 transmits information to be displayed on the calendar to at least one of the second device 112 to the Nth device 114 . Here, the information to be displayed on the calendar means information to be displayed on the output calendar when the calendar is output on the screen of the device. For example, the information to be displayed on the calendar may include job history information to be output on the screen of the device when an indicator to be displayed on the calendar or an indicator displayed on the calendar is selected.

In this case, the first device 111 may transmit the information to be displayed on the calendar only to a device that has requested transmission of the information to be displayed on the calendar among the second device 112 to the Nth device 114 . For example, the second device 112 executes a program for outputting a calendar, and authenticates that the user is a user based on a user account input through the user input unit 16510, thereby providing the first device 111 with the user's calendar. You can request the transmission of the information to be displayed.

Meanwhile, even if there is no request from the second device 112 , the first device 111 may automatically transmit (eg, push) information to be displayed on the calendar to the second device 112 .

Hereinafter, with reference to FIG. 163 , when the second device 112 and the third device 113 perform a document task, an example in which the first device 111 links the work history information to the user's calendar will be described. do.

163 is a flowchart illustrating an example in which the first device links work history information to a user's calendar when the second device and the third device 113 perform a document job, according to some embodiments.

In FIG. 163 , it is illustrated that the first device 100 works on a document in response to a document work request from the second device 112 for convenience of explanation, but the present invention is not limited thereto. In other words, there is no limit to the number of devices requesting document work. Also, there is no limit to the number of devices that request the first device 111 to transmit information to be displayed on the calendar.

In S16310 , the second device 112 transmits information requesting document work to the first device 111 . For example, when the user of the second device 112 logs in by executing the fourth program, the second device 112 may transmit information requesting document work to the first device 111 . In this case, as a method for the user of the second device 112 to log in to the first device 111 , various methods including a method of inputting an ID/password may be used.

In S16311 , the first device 111 works on a document based on the information received from the second device 112 . For example, the first device 111 may execute a program used for working with a document on the first device 111 , and may work with a document using the program executed on the first device 111 . If it is assumed that the document that the first device 111 works with is 'abc.doc' and the program used to create, view, or edit 'abc.doc' is the fourth program, the first device 111 is You can run the fourth program and create, view, or edit 'abc.doc'.

In S16312 , the first device 111 transmits information about the work screen of the document to the second device 112 . For example, the first device 111 may transmit information about the work screen of the document to the second device 112 whenever a document is worked based on information received from the second device. In other words, the first device 111 may transmit, to the second device 112 , information about the work screen of the document, which is changed whenever the document is worked, by using the program executed in the first device 111 . .

In S16313 , the second device 112 outputs the work screen of the document. For example, the second device 112 may output the work screen of the document based on the information about the work screen of the document transmitted from the first device 111 .

In S16314 , the first device 111 obtains job history information of the document. For example, the first device 111 may acquire work history information of a document at a time when execution of a program used for document work is terminated or a document is stored. For example, the first device 111 may acquire job history information of 'abc.doc' at the time of storing 'abc.doc' or ending execution of the fourth program. For example, the first device 111 may store the acquired work history information in a storage space corresponding to the user's account of the second device 112 .

In S16315 , the first device 111 links the acquired job history information to the user's calendar by using time information included in the acquired job history information. For example, if it is assumed that the first device 111 stores 'abc.doc' at 12:28:04 PM on May 12, 2014, the first device 111 displays in the area corresponding to May 12, 2014 on the calendar. You can create directives to be

In S16316 , the second device 111 requests the first device 111 to transmit information to be displayed on the calendar. For example, the second device 111 may request the first device 111 to transmit job history information to be output on the screen of the device when an indicator to be displayed on the calendar or an indicator displayed on the calendar is selected.

In S16317 , the first device 111 transmits information to be displayed on the calendar to the second device 112 .

In S16318, the second device 112 outputs the calendar on the screen. For example, the second device 111 may output a calendar in which the indicator transmitted from the first device 111 is displayed on the screen.

In S16319 , the third device 113 requests the first device 111 to transmit information to be displayed on the calendar. For example, the third device 113 may request the first device 111 to transmit job history information to be output on the screen of the device when an indicator to be displayed on the calendar or an indicator displayed on the calendar is selected.

In S16320 , the first device 111 transmits information to be displayed on the calendar to the third device 113 .

In S16321 , the third device 113 outputs the calendar on the screen. For example, the third device 113 may output a calendar in which the indicator transmitted from the first device 111 is displayed on the screen.

Meanwhile, the above-described method can be written as a program that can be executed on a computer, and can be implemented in a general-purpose digital computer that operates the program using a computer-readable recording medium. In addition, the structure of the data used in the above-described method may be recorded in a computer-readable recording medium through various means. The computer-readable recording medium includes a storage medium such as a magnetic storage medium (eg, ROM, RAM, USB, floppy disk, hard disk, etc.) and an optically readable medium (eg, CD-ROM, DVD, etc.) do.

164 is a configuration diagram of a server according to some embodiments.

The server 16400 shown in FIG. 164 may correspond to the server 100 described above with reference to FIGS. 1 to 163 .

Referring to FIG. 164 , the server 16400 may include a communication unit 16410 , a control unit 16420 , and a database 16430 .

The communication unit 16410 transmits/receives data necessary for linking work history information of a document to the user's calendar with the devices 110 . For example, the communication unit 16410 may transmit and receive job history information of a document, information to be displayed on a calendar, or a document with the devices 110 , but is not limited thereto.

The database 16430 stores information necessary to link the work history of the document to the user's calendar. For example, the database 16430 may store job history information of a document, a document, user account information, a user's calendar, and information to be displayed on the calendar, but is not limited thereto.

The controller 16420 controls the overall operation of the server 16400 . The controller 16420 controls the communication unit 2400 and the database 16430 in order for the server 16400 to link the work history of the document to the user's calendar.

Specifically, the control unit 16420 links the work history information of the document to the user's calendar. For example, the controller 16420 may control the communication unit 16410 so that the communication unit 16410 receives job history information of a document from at least one of the devices 110 . Also, the controller 16420 may link the job history information received in the user's calendar by using time information included in the job history information of the document. Here, the time information means information indicating the time the device worked on the document.

For example, the controller 16420 may obtain the user's calendar from at least one of the database 16430 and the devices 110 . Also, the controller 16420 may generate an indicator to be displayed on the calendar based on any one of the name of the document included in the work history information of the document, and the name of a program and device used to generate the document. Also, the controller 16420 may determine job history information to be displayed on the calendar based on the generated indicator. Also, the controller 16420 may display an indicator in an area corresponding to a date or time indicating a time when a document is created in the calendar.

For example, the control unit 16420 may control the communication unit 16410 such that the communication unit 16410 receives documents generated by each of the devices 110 and work history information of each of the documents from the devices 110 . can Also, the controller 16420 may generate a final document based on a connection relationship between the received documents. Also, the controller 16420 may link the received job history information to the user's calendar by using time information included in the received job history information.

For example, the controller 16420 may work on a document according to a request of at least one of the devices 110 . Also, the control unit 16420 may obtain work history information of the document as the document is worked. Also, the controller 16420 may link the acquired job history information to the user's calendar by using time information included in the acquired job history information.

165 to 166 are configuration diagrams of devices according to some embodiments.

The device 16500 illustrated in FIGS. 165 to 166 may correspond to any one of the devices 110 described above with reference to FIGS. 1 to 164 .

Referring to FIG. 165 , a device 16500 according to some embodiments may include a user input unit 16510 , an output unit 16520 , a control unit 16530 , and a communication unit 16540 . However, not all of the components shown in FIG. 165 are essential components of the first device 16500 . The first device 16500 may be implemented by more components than the components shown in FIG. 165 , and the first device 16500 may be implemented by fewer components than the components shown in FIG. 165 .

For example, referring to FIG. 166 , the first device 16500 according to some embodiments includes a sensing unit 16550 in addition to the user input unit 16510 , the output unit 16520 , the control unit 16530 , and the communication unit 16540 . ), an A/V input unit 16560 , and a memory 16570 may be further included.

The user input unit 16510 refers to a means for a user to input data for controlling the device 16500 . For example, the user input unit 16510 includes a key pad, a dome switch, and a touch pad (contact capacitive method, pressure resistance film method, infrared sensing method, surface ultrasonic conduction method, integral type). There may be a tension measurement method, a piezo effect method, etc.), a jog wheel, a jog switch, and the like, but is not limited thereto.

The user input unit 16510 may receive a user input for selecting an indicator displayed on the calendar. Also, the user input unit 16510 may receive a user input for performing a document task. Here, the work of the document may mean creating a document, reading the document, or editing the document.

The output unit 16520 may output an audio signal, a video signal, or a vibration signal, and the output unit 16520 may include a display unit 16521 , a sound output unit 16522 , and a vibration motor 16523 . there is.

The display unit 16521 displays and outputs information processed by the device 16500 . For example, the display unit 16521 may display a user interface for selecting a virtual image, a user interface for setting an operation of the virtual image, and a user interface for purchasing an item of the virtual image.

Meanwhile, when the display unit 16521 and the touchpad form a layer structure to form a touch screen, the display unit 16521 may be used as an input device in addition to an output device. The display unit 16521 includes a liquid crystal display, a thin film transistor-liquid crystal display, an organic light-emitting diode, a flexible display, a three-dimensional display ( 3D display) and electrophoretic display (electrophoretic display) may include at least one. In addition, the device 16500 may include two or more display units 16521 according to an implementation form of the device 16500 . In this case, two or more display units 16521 may be disposed to face each other using a hinge.

The sound output unit 16522 outputs audio data received from the communication unit 16540 or stored in the memory 16580 . Also, the sound output unit 16522 outputs a sound signal related to a function (eg, a call signal reception sound, a message reception sound, and a notification sound) performed by the device 16500 . The sound output unit 16522 may include a speaker, a buzzer, and the like.

The vibration motor 16523 may output a vibration signal. For example, the vibration motor 16523 may output a vibration signal corresponding to the output of audio data or video data (eg, a call signal reception sound, a message reception sound, etc.). Also, the vibration motor 1230 may output a vibration signal when a touch is input to the touch screen.

The controller 16530 generally controls the overall operation of the device 16500 . For example, the control unit 16500 executes programs stored in the memory 16580 , and thus the user input unit 16510 , the output unit 16520 , the sensing unit 16550 , the communication unit 16540 , and the A/V input unit 16560 . ) can be controlled in general.

Specifically, the controller 16530 performs a document operation according to the received user input. Then, the control unit 16530 generates work history information of the document as the document work is performed.

The sensing unit 16550 may detect a state of the device 16500 or a state around the device 16500 , and transmit the sensed information to the controller 16530 .

The sensing unit 16550 includes a magnetic sensor 16551 , an acceleration sensor 16552 , a temperature/humidity sensor 16553 , an infrared sensor 16554 , a gyroscope sensor 16555 , and a position sensor. (eg, GPS) 16556 , a barometric pressure sensor 16557 , a proximity sensor 16558 , and at least one of an illuminance sensor 16559 , but is not limited thereto. Since a function of each sensor can be intuitively inferred from the name of a person skilled in the art, a detailed description thereof will be omitted.

The communication unit 16540 may include one or more components that enable communication between the device 16500 and another device or between the device 16500 and the server 100 . For example, the communication unit 16540 may include a short-range communication unit 16541 , a mobile communication unit 16542 , and a broadcast receiving unit 16543 .

Short-range wireless communication unit 16541 is a Bluetooth communication unit, BLE (Bluetooth Low Energy) communication unit, short-range wireless communication unit (Near Field Communication unit), WLAN (Wi-Fi) communication unit, Zigbee (Zigbee) communication unit, infrared ( It may include an IrDA, infrared Data Association) communication unit, a Wi-Fi Direct (WFD) communication unit, an ultra wideband (UWB) communication unit, an Ant+ communication unit, and the like, but is not limited thereto.

The mobile communication unit 16542 transmits/receives wireless signals to and from at least one of a base station, an external terminal, and a server on a mobile communication network. Here, the wireless signal may include various types of data according to transmission/reception of a voice call signal, a video call signal, or a text/multimedia message.

The broadcast receiver 16543 receives a broadcast signal and/or broadcast-related information from the outside through a broadcast channel. The broadcast channel may include a satellite channel and a terrestrial channel. According to an implementation example, the device 16500 may not include the broadcast receiver 16543 .

The A/V (Audio/Video) input unit 16560 is for inputting an audio signal or a video signal, and may include a camera 16561 , a microphone 16562 , and the like. The camera 16561 may obtain an image frame such as a still image or a moving image through an image sensor in a video call mode or a shooting mode. The image captured through the image sensor may be processed through the controller 16530 or a separate image processing unit (not shown).

The image frame processed by the camera 16561 may be stored in the memory 16580 or transmitted to the outside through the communication unit 16540 . Two or more cameras 16561 may be provided according to the configuration of the terminal.

The microphone 16562 receives an external sound signal and processes it as electrical voice data. For example, the microphone 16562 may receive an acoustic signal from an external device or a speaker. The microphone 16562 may use various noise removal algorithms for removing noise generated in the process of receiving an external acoustic signal.

The memory 16580 may store a program for processing and control of the controller 16530 , and may store data input to or output from the device 16500 .

The memory 16580 may include a flash memory type, a hard disk type, a multimedia card micro type, a card type memory (eg, SD or XD memory), and a RAM. (RAM, Random Access Memory) SRAM (Static Random Access Memory), ROM (Read-Only Memory), EEPROM (Electrically Erasable Programmable Read-Only Memory), PROM (Programmable Read-Only Memory), magnetic memory, magnetic disk , may include at least one type of storage medium among optical disks.

Programs stored in the memory 16580 may be classified into a plurality of modules according to their functions, for example, may be classified into a UI module 16581 , a touch screen module 16582 , and a notification module 16583 . .

The UI module 16581 may provide a specialized UI, GUI, or the like that interworks with the device 16500 for each application. The touch screen module 16582 may detect a touch gesture on the user's touch screen and transmit information about the touch gesture to the controller 16530 . The touch screen module 16582 according to some embodiments may recognize and analyze a touch code. The touch screen module 16582 may be configured as separate hardware including a controller.

Various sensors may be provided inside or near the touch screen to detect a touch or a proximity touch of the touch screen. A tactile sensor is an example of a sensor for detecting a touch of a touch screen. A tactile sensor refers to a sensor that senses a touch of a specific object to the extent or higher than that felt by a human. The tactile sensor may sense various information such as the roughness of the contact surface, the hardness of the contact object, and the temperature of the contact point.

In addition, as an example of a sensor for detecting a touch of a touch screen, there is a proximity sensor.

The proximity sensor refers to a sensor that detects the presence or absence of an object approaching a predetermined detection surface or an object existing in the vicinity without mechanical contact using the force of an electromagnetic field or infrared rays. Examples of the proximity sensor include a transmission type photoelectric sensor, a direct reflection type photoelectric sensor, a mirror reflection type photoelectric sensor, a high frequency oscillation type proximity sensor, a capacitive type proximity sensor, a magnetic type proximity sensor, an infrared proximity sensor, and the like. The user's touch gesture may include a tap, touch & hold, double tap, drag, pan, flick, drag and drop, swipe, and the like.

The notification module 16583 may generate a signal for notifying the occurrence of an event in the device 16500 . Examples of events generated in the device 16500 include call signal reception, message reception, key signal input, schedule notification, and the like. The notification module 16583 may output a notification signal in the form of a video signal through the display unit 16521 , may output a notification signal in the form of an audio signal through the sound output unit 16522 , and a vibration motor 16523 . It is also possible to output a notification signal in the form of a vibration signal through

A person of ordinary skill in the art related to this embodiment will understand that it can be implemented in a modified form without departing from the essential characteristics of the above description. Therefore, the disclosed methods are to be considered in an illustrative rather than a restrictive sense. The scope of the present invention is indicated in the claims rather than the foregoing description, and all differences within the scope equivalent thereto should be construed as being included in the present invention.

1: system
100: server
110: devices
111: first device
112: second device
113: third device
114: Nth device

Claims (22)

A server for managing history information on document work, the server comprising:
a communication unit configured to receive a document operation request from the user's at least one first device; and
By executing a program according to the received work request, the document is worked on, the work history information of the worked document is obtained, and the schedule information is displayed using the time information included in the work history information. a control unit that reflects the work history information;
including,
The control unit controls the communication unit to transmit the calendar reflecting the work history information to a second device,
The type of the document operation includes generating the document, viewing the document, and editing the document.
The method of claim 1,
A server in which an object indicating the work history information corresponding to the date is displayed on a date field in the calendar. 3. The method of claim 2,
As an object in the calendar is selected, a document corresponding to the selected object is executed in the second device. 4. The method of claim 3,
A server in which a document corresponding to the selected object is provided from the first device to the second device. 4. The method of claim 3,
A server in which the document corresponding to the selected object is provided from the server to the second device. According to claim 1,
a database for storing the work history information and the work document;
further comprising,
The communication unit is a server for receiving the document worked by the first device from the first device.
The method of claim 1,
A server in which an identification value of a user who worked on the document on the date is displayed on a date field in the calendar. The method of claim 1,
A server in which an identification value of the first device is displayed on the date field in the calendar. The method of claim 1,
The job history information includes a time at which the document job was performed, a name of the working document, a type of the working document, a type of the document job, an identification value of the user, an identification value of the first device, and the document job. A server including at least one of the names of the programs used in the . delete In a method for a server to manage history information about document work,
receiving a request to work on a document from at least one first device of a user;
working on the document by executing a program according to the received job request;
obtaining work history information of the worked document;
reflecting the received job history information in a calendar capable of showing schedule information using time information included in the job history information; and
providing a calendar reflecting the work history information to a second device;
including,
The type of document operation includes creating the document, viewing the document, and editing the document.
12. The method of claim 11,
An object indicating the work history information corresponding to the date is displayed on a date field in the calendar. 13. The method of claim 12,
As an object in the calendar is selected, a document corresponding to the selected object is executed in the second device. 14. The method of claim 13,
The document corresponding to the selected object is provided from the first device to the second device. 14. The method of claim 13,
The document corresponding to the selected object is provided from the server to the second device. 12. The method of claim 11,
storing the work history information and the work document;
How to include more.
12. The method of claim 11,
On a date field in the calendar, an identification value of a user who worked on the document on the date is displayed. 12. The method of claim 11,
On a date field in the calendar, an identification value of the first device is displayed on the date. 12. The method of claim 11,
The job history information includes a time at which the document job was performed, a name of the working document, a type of the working document, a type of the document job, an identification value of the user, an identification value of the first device, and the document job. A method comprising at least one of the names of programs used in A computer-readable recording medium in which a program for executing the method of any one of claims 11 to 19 in a computer is recorded. delete delete

Images