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

Abstract

A server managing history information about document work includes: a communications unit which receives work history information of a document written by one or more first devices of a user from the first devices; and a control unit which applies the received work history information to a calendar which can show schedule information by using time information included in the received work history information. The communications unit can provide the calendar with the work history information applied to a second device.

Description

FIELD OF THE INVENTION The present invention relates to a method and apparatus for providing a calendar displaying a work history of a document.

There is provided a method and apparatus for providing a calendar displaying a work history of a document.

As a document creation program that provides various functions for document operations such as document creation, browsing and editing has recently been developed, document processing using a computer is being activated.

With the activation of computer-based document work, a single user frequently works on a plurality of documents.

However, the conventional document creation program simply stores the document on which the operation has been performed, and the user has to manage the operation history of the document directly. Therefore, there is a need for a function of managing the work history of documents.

And to provide a method and an apparatus for providing a calendar displaying a work history of a document. The present invention also provides a computer-readable recording medium on which a program for causing the computer to execute the method is provided. The technical problem to be solved is not limited to the technical problems as described above, and other technical problems may exist.

A server that manages history information on a document job includes a communication unit that receives job history information of a document processed by at least one first device of the user from the at least one first device; And a controller for reflecting the received job history information on a calendar that can display schedule information using the time information included in the received job history information, Two devices can be provided.

In the server described above, an object representing the job history information corresponding to the date may be displayed on a date field in the calendar.

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

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

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

The server may further include a database for storing the received job history information and the processed document, and the communication unit may receive the processed document from the first device.

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

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

In the server, the job history information includes at least one of a time at which the document job was performed, a name of the document to be worked on, a type of the document to be worked on, a type of the document job, An identification value, and a name of a program used in the document operation.

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

A method for managing history information about a document job, comprising: receiving job history information of a document operated by a user's at least one first device from the at least one first device; Reflecting the received job history information on a calendar capable of displaying schedule information using time information included in the received job history information; And providing the second device with a calendar reflecting the operation history information.

In the above-described method, an object representing the job 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 can be executed in the second device.

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

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

The method may further include storing the received job history information and the processed document, wherein the receiving step may receive the processed document from the first device.

In the above-described method, the identification value of the 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 may include at least one of a time at which the document job was performed, a name of the document to be worked on, a type of the document to be worked on, a type of the document job, An identification value, and a name of a program used in the document operation.

A server for managing history information on a document operation includes: a communication unit for receiving a document operation request from at least one first device of the user; And a control unit for controlling the operation of the document in accordance with the received job request, generating job history information of the operated document, displaying the schedule information using the time information included in the job history information, And a control unit that reflects the history information, wherein the communication unit can provide the calendar, on which the operation history information is reflected, to the second device.

A server for managing history information related to a document job includes a communication unit for receiving job history information of documents operated by first devices of each of the users from the first devices; And a controller for reflecting the received job history information on a calendar that can display schedule information using the time information included in the received job history information, 2 < / RTI > devices.

A computer-readable recording medium includes a recording medium on which a program for causing a computer to execute the above-described method is recorded.

1 is a diagram illustrating an example of a system for linking work history information to a calendar of a user according to some embodiments.
FIG. 2 is a diagram for explaining an example in which, when a user of the devices according to some embodiments is the same, and the devices perform document work, the server cooperates with the user's calendar with job history information.
FIG. 3 is a flowchart illustrating an example in which a server according to some embodiments links work history information to a calendar of a user.
4 is a flowchart showing an example in which a server interlinks job history information with a calendar of a first user when a first device and a second device according to some embodiments perform document jobs.
FIG. 5 is a flowchart showing an example in which, when a first device according to some embodiments generates a document, the server cooperates with the user's calendar with job history information.
6 to 7 are diagrams for explaining an example in which a first device transmits job history information of a document to a server when a document according to some embodiments is a text document.
FIGS. 8 to 9 are diagrams for explaining another example in which, when the document according to some embodiments is a text document, the first device transmits job history information of the document to the server.
FIGS. 10 to 11 are diagrams for explaining another example in which, when the document according to some embodiments is a text document, the first device transmits the job history information of the document to the server.
12 is a flowchart showing an example in which a server according to some embodiments links job history information of a document to a calendar.
13 to 14 are diagrams showing an example of job history information of a document according to some embodiments.
FIG. 15 is a flowchart showing an example in which a server according to some embodiments links work history information to a calendar of a user.
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 showing another example of the daily calendar displayed on the screen of the device according to some embodiments.
18 is a diagram showing another example of the daily calendar displayed on the screen of the 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 showing another example of a monthly calendar displayed on a screen of a device according to some embodiments.
21 is a diagram showing another example of a monthly calendar displayed on the screen of the device according to some embodiments.
22 to 25 are diagrams showing an example of an annual calendar displayed on a screen of a device according to some embodiments.
26A to 26B are flowcharts showing an example in which, when a first device according to some embodiments generates a document and a second device reads a document, the server cooperates with the user's calendar with the job history information.
27 is a diagram for explaining an example in which a second device according to some embodiments requests a first device to transmit a document and receives a document.
FIGS. 28 to 30 are diagrams for explaining examples in which a second device according to some embodiments terminates output of a document. FIG.
31 is a diagram for explaining an example in which a second device according to some embodiments transmits job history information of a document to a server.
32A to 32B are flowcharts showing another example in which, when a first device according to some embodiments generates a document and a second device reads a document, the server cooperates with the user's calendar with job history information.
33 is a diagram for explaining an example in which a second device according to some embodiments requests a server to transmit a document and receives a document.
34 is a flowchart showing an example in which a server according to some embodiments links job history information of a document to a calendar.
35 to 36 are diagrams showing an example of job history information of a document according to some embodiments.
37 is a flowchart showing an example in which a server according to some embodiments links work history information to a calendar of a user.
38 to 40 are diagrams showing examples of daily calendars displayed on the screen of the device according to some embodiments.
41 to 43 are diagrams showing examples of monthly calendars displayed on the screen of the device according to some embodiments.
44 to 47 are diagrams showing examples of the annual calendars displayed on the screen of the device according to some embodiments.
48A to 48B are flowcharts showing an example in which, when a first device according to some embodiments generates a document and a second device edits a document, the server cooperates with the user's calendar with job history information.
49 to 50 are diagrams for explaining examples in which a second device according to some embodiments edits a document.
51 is a diagram for explaining an example in which a second device according to some embodiments transmits job history information of documents and documents to a server.
52 is a flowchart showing an example in which a server according to some embodiments links job history information of a document to a calendar.
53 to 54 are views showing an example of job history information of a document according to some embodiments.
55 is a flowchart showing an example in which a server according to some embodiments links work history information to a calendar of a user.
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 showing another example of the daily calendar displayed on the screen of the device according to some embodiments.
58 is a diagram showing another example of the daily calendar displayed on the screen of the 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 showing another example of a monthly calendar displayed on a screen of a device according to some embodiments.
61 is a diagram showing another example of the monthly calendar displayed on the screen of the 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 showing another example of the annual calendar displayed on the screen of the device according to some embodiments.
64 is a diagram showing another example of the annual calendar displayed on the screen of the device according to some embodiments.
65 is a diagram showing another example of an annual calendar displayed on the screen of the device according to some embodiments.
66A to 66C are flowcharts showing another example in which a server associates work history information with a user's calendar in a case where a first device according to some embodiments generates a document and a second device views and edits a document. to be.
67 to 68 are diagrams showing 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 showing another example of the daily calendar displayed on the screen of the device according to some embodiments.
71 is a diagram showing another example of the daily calendar displayed on the screen of the 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 view showing another example of the monthly calendar displayed on the screen of the device according to some embodiments.
74 is a diagram showing another example of the monthly calendar displayed on the screen of the 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 view showing another example of the annual calendar displayed on the screen of the device according to some embodiments.
77 is a view showing another example of the annual calendar displayed on the screen of the device according to some embodiments.
78 is a diagram showing another example of the annual calendar displayed on the screen of the device according to some embodiments.
79 to 80 are diagrams showing examples of calendars output on the screen of the device according to some embodiments.
81 to 82 are diagrams showing still other examples of calendars output on the screen of the device according to some embodiments.
83 is a diagram for explaining an example in which the mode of the calendar is switched according to some embodiments.
84 is a diagram for explaining an example in which the server cooperates with the user's calendar with job history information when the users of the devices according to some embodiments are different from each other and the devices perform document work.
85 is a flowchart showing an example in which a server according to some embodiments links work history information to a calendar of a user.
86 is a flowchart showing an example in which, when a first device and a second device according to some embodiments perform a document operation, the server associates the operation history information with the calendar of the first user.
87 is a diagram for explaining an example in which, when devices according to some embodiments perform co-authoring of a document, the server cooperates with the user's calendar with job history information.
88 is a flowchart showing an example in which a server according to some embodiments links job history information to a calendar of a user.
FIGS. 89A to 89B are flowcharts illustrating an example in which a server cooperates with a user's calendar with job history information when a first device and a second device according to some embodiments perform co-authoring of a document.
90 is a diagram for explaining an example of generating a document in the first device and the second device according to some embodiments.
91 is a diagram for explaining an example of transmitting job history information of documents and documents generated in the first device and the second device to a server according to some embodiments.
92 is a diagram for explaining an example of a process of combining documents by co-authoring devices according to some embodiments.
93 is a diagram for explaining another example of a process of combining documents by co-authoring devices according to some embodiments.
94A to 94B are flowcharts showing another example in which a server cooperates with a user's calendar with job history information when a first device and a second device according to some embodiments perform co-authoring of a document.
95 is a diagram for explaining another example of a process of combining documents by co-authoring devices according to some embodiments.
96 is a diagram for explaining an example of generating a final document by co-authoring of a first device, a second device and an Nth device according to some embodiments.
97 is a view showing an example of displaying the history of documents generated by coauthoring in a monthly calendar displayed on a screen of a device according to some embodiments.
98 is a view showing another example of displaying the history of the documents generated by the co-author in the monthly calendar displayed on the screen of the device according to some embodiments.
99 shows an example in which at least one of a plurality of devices corresponds to a server and a device performing a server function interlocks a job history information with a user's calendar when devices perform document work FIG.
100 is a flowchart illustrating an example in which, when a second device and a third device according to some embodiments perform a document operation, the first device associates the job history information with the user's calendar.
101 is a diagram for explaining an example in which, when a user of devices according to some embodiments is the same and a server performs a document operation based on a request of devices, the server cooperates with the user's calendar with job history information to be.
102 is a flowchart showing an example in which a server according to some embodiments links work history information to a calendar of a user.
103 is a flowchart illustrating an example in which a server interlocks job history information with a calendar of a first user when a server performs a document job according to a document job request of a first device according to some embodiments.
104 is a flowchart showing an example in which, when a server according to some embodiments generates a document, the server cooperates with the user's calendar with the job history information.
105 to 106 are diagrams for explaining an example in which a server according to some embodiments executes a program to generate and store a document, and acquires job history information of the document.
107 is a flowchart showing an example in which a server according to some embodiments links job history information of a document to a calendar.
108 to 109 are views showing an example of job history information of a document according to some embodiments.
110 is a flowchart showing an example in which a server according to some embodiments links work history information to a calendar of a user.
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 showing another example of the daily calendar displayed on the screen of the device according to some embodiments.
113 is a diagram showing another example of the daily calendar displayed on the screen of the 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 showing another example of a monthly calendar displayed on a screen of a device according to some embodiments.
116 is a diagram showing another example of the monthly calendar displayed on the screen of the device according to some embodiments.
117 is a diagram showing an example of an annual calendar displayed on a screen of a device according to some embodiments.
118 is a diagram showing another example of the annual calendar displayed on the screen of the device according to some embodiments.
119 is a diagram showing another example of the annual calendar displayed on the screen of the device according to some embodiments.
120 is a diagram showing another example of the annual calendar displayed on the screen of the device according to some embodiments.
FIGS. 121A to 121C illustrate a case where a server performs a document operation according to a document operation request of a first device according to some embodiments, and a server displays operation history information in a calendar of a first user Fig. 2 is a flowchart showing an example of interworking.
122 is a diagram for explaining an example in which a second device according to some embodiments requests a server to perform a job of a document and receives information about a job screen.
123 is a diagram for explaining an example in which a second device according to some embodiments terminates the output of a job screen.
124 is a diagram for explaining an example in which a second device according to some embodiments transmits job history information of a document to a server.
125 is a flowchart showing an example in which a server according to some embodiments links job history information of a document to a calendar.
126 to 127 are diagrams showing examples of job history information of a document according to some embodiments.
128 is a flowchart showing an example in which a server according to some embodiments links work history information to a calendar of a user.
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 showing another example of the daily calendar displayed on the screen of the device according to some embodiments.
FIGS. 131A to 131C show a case where, when a server generates a document according to a request of a first device according to some embodiments and a server edits a document according to a request of a second device, As shown in Fig.
FIGS. 132 through 133 are diagrams for implementing examples in which a server according to some embodiments edits a document. FIG.
134 is a diagram for explaining an example in which a server according to some embodiments acquires job history information of a document.
135 is a flowchart showing an example in which a server according to some embodiments links job history information of a document to a calendar.
136 through 137 are views showing an example of job history information of a document according to some embodiments.
138 is a flowchart showing an example in which a server according to some embodiments links work history information to a calendar of a user.
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 showing another example of the daily calendar displayed on the screen of the device according to some embodiments.
Figures 141A-141D illustrate a method in which a server generates a document upon request of a first device according to some embodiments, and when the server provides a view of the document and edits the document upon request of the second device, FIG. 7 is a flowchart showing another example of linking the job history information to the calendar of FIG.
142 through 143 are views showing examples of calendars output to the screen of the device according to some embodiments.
144 to 145 are diagrams showing still another example of the calendar displayed on the screen of the device according to some embodiments.
FIG. 146 is a diagram for explaining an example in which a mode of a calendar according to some embodiments is switched. FIG.
147 is a view for explaining an example in which a server cooperates with job history information on a user's calendar in the case where the users of the devices according to some embodiments are different from each other and the server performs the document operation based on the request of the devices to be.
148 is a flowchart showing an example in which a server according to some embodiments links work history information to a calendar of a user.
149 is a flowchart illustrating an example in which a server interlocks job history information with a calendar of a first user when a server performs a document job according to a document job request of a first device according to some embodiments.
150 is a diagram for explaining an example in which a server cooperates with job history information on a user's calendar when devices according to some embodiments perform co-authoring of documents.
151 is a flowchart illustrating an example in which a server according to some embodiments links work history information to a calendar of a user.
FIGS. 152A to 152C are flowcharts illustrating an example in which a server cooperates with a user's calendar with job history information when a first device and a second device according to some embodiments perform co-authoring of a document.
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 job history information of documents and documents generated in the server according to some embodiments.
FIG. 155 is a view for explaining an example of a process of combining documents by co-authoring devices according to some embodiments.
156 is a diagram for explaining another example of a process of combining documents by co-authoring devices according to some embodiments.
FIGS. 157A to 157C are flowcharts illustrating an example in which, when a first device and a second device according to some embodiments perform a co-authoring of a document, the server cooperates with the user's calendar with the job history information.
FIG. 158 is a view for explaining another example of a process of combining documents by co-authoring devices according to some embodiments.
Figure 159 is a diagram for explaining an example of generating a final document by co-authoring of a first device, a second device, and an Nth device according to some embodiments.
160 is a diagram illustrating an example of displaying the history of documents generated by a co-author in a monthly calendar displayed on a screen of a device according to some embodiments.
161 is a diagram showing another example of displaying the history of documents generated by the co-author in the monthly calendar displayed on the screen of the device according to some embodiments.
FIG. 162 is a flowchart illustrating an operation of a server that performs a function of a server when at least one of a plurality of devices according to some embodiments corresponds to a server, Is a diagram for explaining an example of linking job history information to a calendar of a user.
FIG. 163 is a flowchart showing an example in which, when the second device and the third device according to some embodiments perform document work, the first device associates the task history information with the user's calendar.
164 is a configuration diagram of a server according to some embodiments.
165 to 166 are block diagrams of a device 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 intended only to illustrate the present invention and do not limit or limit the scope of the present invention. It will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the invention as defined by the appended claims.

Throughout the specification, when a part is referred to as being "connected" to another part, it includes not only "directly connected" but also "electrically connected" with another part in between . Also, when an element is referred to as "comprising ", it means that it can include other elements as well, without departing from the other elements unless specifically stated otherwise.

Also, throughout the specification, "gesture" means an action that the user uses to control the terminal. For example, the gestures described herein include tabs, touch and hold, double tap, drag, panning, flick, drag and drop, handshaking, and the like.

In the specification, "output to the device screen" means that a specific screen is displayed on the screen of the device. Therefore, "output to the device screen" includes "display on the device screen ".

Further, throughout the specification, the term " 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 block diagram illustrating an example of a system for linking work history information to a calendar of a user according to some embodiments.

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

The server 100 links the job history information to the user's calendar using the 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 the time at which at least one of the devices 110 worked the document. A calendar is an object that shows schedule information of a user. For example, when the user operates the document using the first device 111, the first device 111 generates job history information as the document job is performed. The first device 111 transmits the job history information to the server 100 and the server 100 extracts information indicating the time when the document is operated in 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 calendar of the user using the extracted time information.

Examples in which the first device 111 transmits job history information to the server 100 are as follows. As an example, the first device 111 may transmit job history information to the server 100 at the same time as generating the job history information. As another example, the first device 111 may generate job history information, store the job history information in the memory 16580, and transmit the job history information stored in the memory 16580 to the server 100 in a lump. As another example, the first device 111 may generate job history information and store the job history information in the memory 16580. When the synchronization request is received from the server 100, the first device 111 transmits job history information stored in the memory 16580 to the server 100).

If job history information is generated while the user is logged in to the server 100, the first device 111 can immediately transmit the job history information to the server 100. On the other hand, if the user performs a document operation using the first device 111 without logging in the server 100, the first device 111 may store the job history information in the memory 16580 first. When the user subsequently logs in to the server 100, the first device 111 can transmit the job history information already stored in the memory 16580 to the server 100. [ At this time, the first device 111 may automatically transmit the job history information stored in the memory 16580 to the server 100. However, after receiving the transfer command from the user, the first device 111 may store the job history information previously stored in the memory 16580 To the server (100).

In addition, the user can create a specific folder in the first device 111 and set the created folder to be connected to the server 100. [ In this case, the job history information of the document included in the folder is transmitted to the server 100, but the job history information of the document not included in the folder may not be transmitted to the server 100. However, only when the user is logged in to the server 100, the job history information of the document can be immediately transmitted to the server 100. The job history information generated when the user is not logged in to the server 100 can be transmitted to the server 100 when the user logs in to the server 100 in the future.

The fact that the server 100 links the job history information to the user's calendar means that the server 100 reflects the job history information on the user's calendar. Examples in which the server 100 reflects job history information on 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 when the job was performed. 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 when the device worked on the document. For example, assuming that the job history information received from the first device 111 includes time information of " 2014.05.14 AM 09: 04: 42 " The first task history information may be stored in the field corresponding to the first task history information. At this time, the database 16430 may be included in the server 100 or may be provided in a separate apparatus from the server 100. [ The server 100 can access the database 16430 through a calendar program installed in the server 100, and can read, modify, and add job history information.

As another example, the server 100 may store the job history information in the database 16430, read the previously stored job history information through the calendar program installed in the server 100, and display the read job history information on the calendar UI. For example, assuming that the first job history information among the job history information stored in the database 16430 is the information on which the document is operated in 2014.05, the server 100 reads the first job history information from the database 16430, On the calendar UI corresponding to the user. At this time, the server 100 may generate an indicator indicating the first job history information, and may 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 on the calendar through the calendar program installed in the server 100. [ For example, if it is assumed that the job history information on the job performed on the 2014.05.14 from the first device 111 is transmitted to the server 100, the server 100 transmits the job history information to 2014.05 through the calendar program You can reflect on your calendar. The server 100 may store the calendar reflecting the job history information in the database 16430.

The server 100 may generate job history information or an indicator indicating a document to be processed, thereby reflecting the job history information in the calendar or displaying the job history information in the calendar UI. Here, the indicator indicates 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 can output the job history information corresponding to the selected indicator to 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 the document corresponding to the indicator to the first device 111, Can be transmitted. Thus, the first device 111 can output the document corresponding to the selected indicator to the screen.

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

The device outputs the user's calendar on the screen based on the information received from the server 100. [ Here are some examples where the device prints the user's calendar on the screen:

As an example, a calendar program (or an application) for a client (hereinafter referred to as a first calendar program) is installed in the devices 110 and a server calendar program (or application) Quot; second calendar program ") may be installed. At this time, the first device 111 can generate the calendar UI using the first calendar program, and store the generated calendar UI in the memory 16580. [ When the first device 111 receives the job history information (or an indicator corresponding to the job history information) to be displayed in the calendar UI from the server 100 by the date, the first device 111 stores the calendar UI stored in the memory 16580 and the server 100, The job history information (or the indicator) transmitted from the job history information management apparatus 100 can be output together. 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 an indicator) stored in the database 16430 . Then, the first device 111 can read the calendar UI stored in the memory 16580. Then, the first device 111 can display the calendar on the screen by displaying the job history information (or an 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 directly output (e.g., mirror) the screen of the first device 111 to the screen of the first device 111. Accordingly, 1 device 111 can output the user's own calendar to 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 displayed in the form of a web page 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. At this time, the first device 111 can display the calendar on the screen by accessing the web page created by the server 100 using the web browser. For example, when the first device 111 requests the server 100 to transmit the information to be displayed on the calendar, and transmits the user account to the server 100, the server 100 transmits the user account 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. The first device 111 can output a calendar on the screen by accessing a web page created by the server 100 using a web browser. Therefore, the first device 111 can output a calendar unique to the user to the screen.

The server 100 transmits information to the first device 111 when the first device 111 requests the server 100 to transmit information to be displayed on the calendar. In other words, when the first device 111 executes the first calendar program, when the first device 111 executes the first calendar program and selects a particular year, month, day, or hour, The server 100 transmits information to the first device 111 when the first server 111 transmits the user account to the server 100. [ However, it 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, the server 100 may periodically transmit information to be displayed on the calendar to the first device 111, even though there is no request from the devices 110. [

According to the above description, 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. At this time, the server 100 can output the calendar through the screen of the web page or the second calendar program.

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

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

As another example, assuming that the first device 111 has generated and edited the first document, the first device 111 can transmit only the job history information generated by editing the first document to the server 100. [

As another example, when the first device 111 finishes displaying the document output on the screen, the first device 111 may display an indication on the screen asking whether to transmit the job history information to the server 100. [ At this time, the server 100 may transmit the job history information to the server 100 only when a user input requesting to transmit the job history information to the server 100 through the user input unit 16510 is received.

As another example, the first device 111 may transmit only the job history information of the document, which has been operated in a specific period, to the server 100. For example, the first device 111 may transmit only the job history information of the document that has been operated between 2014.05.01 AM 00:00:00 and 2014.05.05 PM 11:59:59 to the server 100. Also, the first device 111 can transmit only the job history information of the document, which is operated between AM 09:00:00 and PM 05:59:59, to the server 100.

As another example, a user may designate a device from among the devices 110 to transmit job history information to the server 100, and only the designated device may transmit the job history information to the server 100. [ For example, if the user designates the first device 111 among the devices 110, only the first device 111 among the devices 110 can transmit the job history information to the server 100.

In addition, 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 job history information transmitted to the server 100 may be different from the number of job history information linked to the user's calendar. 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.

Assuming, for example, that the first device 111 has transmitted the job history information of the first document to the third document to the server 100, the server 100 determines that only the job history information of the first document is included in the user's calendar It can also work together.

As another example, if it is assumed that the first device 111 has transmitted 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 the job history information generated by editing the first document may be linked to the calendar.

When a user works a document using the first device 111 to the N-th device 114, each device generates job history information as the document is operated. In other words, the first device 111 generates the first job history information, and the Nth device 114 generates the Nth job history information. The first device 111 to the Nth device 114 transmit the job history information to the server 100 and the server 100 transmits the job history information received from the first device 111 to the Nth device 114 Information indicating the time at which the document was operated is extracted from the history information to the N-th job history information. Then, the server 100 links the job history information received from the first device 111 to the Nth device 114 to the user's calendar using the extracted time information.

At this time, each device transmits 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 as described above.

In the above example, a user refers to a principal who works with a document using at least one of the devices 110. For example, the devices 110 may be devices of the same user, or may be devices of different users.

In addition, in the above-described example, the user may use at least one of the devices 110 to work with the document, which may mean that the user works by using the program installed in the devices 110, It does not. For example, a user may work on a document by using a program installed on the server 100 through at least one of the devices 110. [

In addition, in the example described above, the user is described as working a document using at least one of the devices 110, but is not limited thereto. For example, a user may use at least one of the devices 110 to perform content work.

The document includes a text document or a multimedia document. For example, the document may include an object to which an operation is performed by the devices 110 or a word program installed in the server 100, an Excel program, a power point program, or the like.

In addition, the content includes photographs, images, movies, music, and the like. For example, the content may include an object on which operations are performed by the devices 110 or the photo execution program, image execution program, moving image execution program, music execution program, etc. installed in the server 100.

Document work means creation, viewing or editing of a document. For example, the first device 111 performs document processing when the first device 111 generates a document, when the first device 111 browses the document, or when the first device 111 receives a document Editing < / RTI >

Here, the reading of the document by the first device 111 includes that the first device 111 outputs the document on the screen. The editing of the document by the first device 111 also includes the first device 111 adding new content to the content of the pre-created document or deleting the content contained in the pre-created document. In addition, the document work may include not only creating and viewing a document, but also transmitting, copying, or deleting the document.

When an indicator is selected according to the user input received through the user input unit 16510 of the device, the device can output job history information on the screen. For example, the indicator may indicate the type or name of the document, the identification value of the user, the identification value of the device, and the like. Here, the identification value of the user includes 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, the job history information of the document can be output. Also, as the indicator is selected, the document on which the operation has been performed can be output.

The job history information means information generated as at least one of the devices 110 performs a document operation. For example, the job history information includes information such as a time at which a document operation was performed, a name of a document to be processed, a type of a document to be processed, a type of a document operation, . ≪ / RTI >

The server 100 refers to a main body that transmits and receives data to and from a 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 that performs a role of a server among a plurality of devices 110.

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

Hereinafter, examples in which the server 100 generates job history information of a document will be described with reference to FIGS. 2 to 163. The contents to be described later with reference to FIG. 2 to FIG. 163 are examples of the method described above with reference to FIG. Therefore, the contents described above with reference to FIG. 1 can be applied to the examples described later with reference to FIG. 2 to FIG. 163, even if omitted from the following description.

As an example, referring to Figs. 2 to 83, when the users of the devices 110 are the same and the devices 110 perform document operations, the server 100 stores the operation history information Will be described.

84 to 86, when the users of the devices 110 are different from each other and the devices 110 perform document operations, the server 100 stores the operation history information Will be described.

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

99 to 100, at least one of the plurality of devices 110 corresponds to the server 100, and when the devices 110 perform document work, the server 100 Will be described as an example in which a device that performs a function of a task synchronizes work history information with a user's calendar.

As another example, referring to Figs. 101 to 146, when the user of the devices 110 is the same and the server 100 performs a document operation based on a request of the devices 110, 100) interworking the job history information with the user's calendar will be described.

147 to 149, when the users of the devices 110 are different from each other and the server 100 performs the document operation based on the request of the devices 110, the server 110 100) interworking the job history information with the user's calendar will be described.

As another example, referring to FIGS. 150 to 161, when the server 100 authorizes a document based on a request of the devices 110, the server 100 interlocks the operation history information with the user's calendar An example will be described.

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 determined based on the request of the devices 110 An example in which the device performing the function of the server 100 interlocks the job history information with the user's calendar will be described.

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

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

At least one of the devices 110 performs a document operation 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 perform document work and transmit 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 a 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 as an indicator to be displayed on the calendar or an indicator to be displayed on the calendar is selected.

At this time, the server 100 may transmit the information 140 to be displayed on the calendar only to the device 110 that requested the transfer of the information 140 to be displayed on the calendar. For example, the first device 111 executes a program for outputting a calendar, authenticates the first user based on the user account entered through the user input unit 16510, And may request the transmission of information 140 to be displayed on the calendar.

On the other hand, the server 100 may automatically transmit (e. G., Push) the information 140 to be displayed on the calendar to the first device 111, even if there is no request from the first device 111 . For example, if there is a history that the first device 111 has previously requested transmission of the information 140 to be displayed on the calendar of the first user, then the server 100 may subsequently request a request from the first device 111 The information 140 to be displayed on the calendar of the first user can be automatically transmitted.

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

FIG. 3 is a flowchart illustrating an example in which a server according to some embodiments links work history information to a calendar of a user.

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

In S302, the server 100 links the received job history information to the calendar of the user using the time information included in the received job history information. Here, the time information means information indicating the time when the device worked on the document. For example, assuming that the first device 111 of the first user 120 has created a document 'abc.doc' at 12:28:04 pm on May 12, 2014, the server 100 sends a first user 120 and may select the indicator to be displayed on 2014.05.12 to determine the job history information to be output on the screen of the first device 111 of the first user 120 have. At this time, as described above with reference to FIG. 1, only a part of the job history information received from the device by the server 100 can be linked to the user's calendar.

4, when the first device 111 of the first user 120 and the second device 112 of the first user 120 are working on a document, the server 100 determines whether the first user 111 An example in which the job history information is linked to the calendar of FIG.

4 is a flowchart showing an example in which a server interlinks job history information with a calendar of a first user when a first device and a second device according to some embodiments perform document jobs.

In FIG. 4, the first device 111 and the second device 112 are shown as working documents for convenience of explanation, but the present invention is not limited thereto. In other words, there is no limit to the number of devices that work with documents. Assuming that there is only one device to work with the document, the operation of the second device 112, which will be described below, can be all performed in the first device 111. [ Assuming that the number of devices working on the 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 .

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

Assuming that the document to be processed by the first device 111 is 'abc.doc' and that the program used for creating, viewing or editing 'abc.doc' is the first program, the first device 111 You can run the first program and create, view or edit 'abc.doc'.

In S411, the first device 111 transmits the job history information of the document to the server 100. [ At this time, it is assumed that the user of the first device 111 is logged in the server 100. For example, the first device 111 can transmit the job history information of the document to the server 100 at the time when the execution of the program used for the document job ends or the document is stored. For example, the first device 111 may transmit 'abc.doc' job history information to the server 100 at the time of 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 can transmit the job history information of the document to the server 100. [ For example, a method for the user of the first device 111 to log into the server 100 may use various methods including a method of inputting an ID / password.

As another example, when a user of the first device 111 logs into the server 100 and a separate program for transmitting the job history information of the document to the server 100 is executed, The job history information of the server 100 can 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 output to the screen of the first device 111. [ At this time, if the user of the first device 111 requests transmission of the job history information through the window, the first device 111 can 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 a document and to transmit the job history information of the document to the server 100 is selected, the first device 111 transmits the job history information of the document to the server 100). For example, when a user of the first device 111 generates or edits a document and selects a save button of a document, a separate window for inquiring whether or not the job history information is transmitted is output to the first device 111 . At this time, if the user of the first device 111 requests transmission of the job history information through the window, the first device 111 can 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 of the document (e.g., ". Doc", ".xls", ".txt", ".ppt" (For example, MS Word, MS Excel, MS PowerPoint, etc.) of the program. Thereafter, when the first device 111 has worked on the document of the kind registered in the server 100, the first device 111 can automatically transmit the job history information of the document to the server 100.

On the other hand, the type of the 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 can be set in the manner that the extension of the document or the executable program of the document is designated. Then, the user of the first device 111 can edit the type of the document set in the server 100. [

In S412, the second device 112 works on the document. For example, the first device 111 can execute a program used for document operation, and can work on the document using the program. Assuming that the document to be processed by the second device 112 is 'abcd.xls' and that the program used for creating, viewing or editing 'abcd.xls' is a second program, the second device 112 You can run the second program and create, view or edit 'abcd.xls'.

In step S413, the second device 112 transmits the job history information of the document to the server 100. [ For example, the second device 112 can transmit the job history information of the document to the server 100 at the time when the execution of the program used for the document job is ended 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 terminating the execution of the second program

In step S415, the server 100 links the job history information to the user's calendar using the time information included in the job history information received from the first device and the second device. For example, if the first device 111 stores 'abc.doc' at 08:01:42 AM on May 17, 2018, and the second device 112 stores 'abcd.xls' : 00, the server 100 may generate a first indicator to be displayed in the field corresponding to 2014.05.18 on the calendar, and generate a second indicator to be displayed in the 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 displayed on the screen of the device, by selecting an indicator to be displayed on the calendar or an indicator to be displayed on the calendar. For example, the first device 111 may request transmission of job history information to be output to the screen of the device as the first indicator, the second indicator, and the first and second indicators are selected.

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

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

In step 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 the job history information to be displayed on the screen of the device as the indicator to be displayed on the calendar or the indicator displayed on the calendar is selected. For example, the second device 112 may request transmission of job history information to be output to the screen of the device as the first indicator, the second indicator, and the first and second indicators are selected.

In S420, the server 100 transmits the 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 on which the first indicator and the second indicator transmitted from the server 100 are displayed.

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

FIG. 5 is a flowchart showing an example in which, when a first device according to some embodiments generates a document, the server cooperates with the user's calendar with job history information.

In FIG. 5, the first device 111 generates a document and the second device 112 outputs a calendar on the screen for convenience of explanation. However, 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.

There is no limit to the number of devices. Assuming 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, Lt; RTI ID = 0.0 > N-th < / RTI >

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 generates a document can be a program included in MS-OFFICE.

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

In step S512, the first device 111 transmits the job history information of the document to the server 100. [ At this time, it is assumed that the user of the first device 111 is logged in the server 100. The example in which the first device 111 transmits the job history information of the document to the server 100 is as described above with reference to step S411 of FIG.

For example, the first device 111 can transmit the job history information of the document to the server 100 at the time of storing the document. The job history information of the document means information generated as the first device 111 generates and stores the document. For example, the job history information may include at least one of a title of a document on which an operation is performed, a type of the document, a time at which the document operation was performed, a device name for performing the document operation, a user of the device, 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. FIG.

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

6 (a), the first device 111 executes a first program to generate a text document. For example, the first device 111 may select an indicator 610 indicative of the first program based on the user input received via the user input 16510. Then, the first device 111 can execute the 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 create the content 620 contained in the text document based on the user input received via the user input 16510.

Referring to FIG. 7, the first device 111 stores a text document. For example, the first device 111 may select an indicator 710 indicating ' storing ' a text document based on user input received via the user input 16510. [ Then, the first device 111 can store a text document.

After storing the text document, the first device 111 transmits the task history information of the text document to the server 100. For example, if the first device 111 stores a document named 'abc.doc' with a size of 54 KB (kilobytes) at 12:28:04 pm on May 12, 2014 using the first program Assuming that the first device 111 sends at least one of "abc.doc, text, first program, first device, May 12, 2014 12:28:04 PM, 54 KB" to the server 100 Can be transmitted.

On the other hand, if a stored document requires a high level of security, the first device 111 may additionally perform encryption on the job history information and transmit the encrypted job history information to the server 100.

As an example, when the user selects the 'security' option at the time of storing the document, the first device 111 may further transmit the job history information of the document to the server 100 by performing encryption.

As another example, a user can create a specific folder in the first device 111, and set the document included in the generated folder to have a strong security level. When the job history information of the document included in the folder is generated, the first device 111 may further transmit the job history information to the server 100 by performing encryption.

The user can access the job history information transmitted to the server 100 after logging into the server 100. [ However, additional information may be additionally required to access the job history information on which encryption has been performed. For example, even after the user logs in the server 100 by inputting the password / ID, it can be set to input a separate password in order to access the encrypted job history information.

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

Referring to FIG. 8A, the first device 111 executes a second program to generate a text document. At this time, the second program executed by the first device 111 may be different from the first program described above with reference to Fig. 6 (a). In other words, the program used by the first device 111 to generate a text document may be varied, and the form of the text document generated by the first device 111 using each program may vary.

The first device 111 may select an indicator 810 indicating the second program based on the user input received via the user input 16510. [ Then, the first device 111 can execute the second program.

Referring to FIG. 8 (b), the first device 111 generates a text document based on the executed program. For example, the first device 111 may create the content 820 contained in the text document based on the user input received via the user input 16510.

Referring to FIG. 9, the first device 111 stores a text document. For example, the first device 111 may select an indicator 910 indicating " storage " of a text document based on the user input received via the user input 16510. [ Then, the first device 111 can store a text document.

The first device 111 stores the text document and then transmits the task history information of the text document to the server 100. [ For example, if the first device 111 generated a document named 'abcd.xls' with a size of 47 kilobytes using the second program at 2:25:56 pm on April 22, 2014 Assuming that the first device 111 has received at least one of abcd.xls, text, second program, first device, April 22, 2014 at 02:25:56, 47 KB, Can be transmitted.

Meanwhile, as described above with reference to FIG. 7, encryption can be further performed in addition to the job history information of a document requiring high security level and transmitted to the server 100.

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

Referring to FIG. 10A, the first device 111 executes a third program to generate a text document. In other words, the text generated by the first device 111 may vary, and the program used by the first device 111 to generate the 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 via the user input 16510. [ Then, the first device 111 can execute the third program. Here, an example in which the first device 111 selects the indicator 1010 and executes the program corresponding to the selected indicator 1010 is as described above with reference to FIG. 6 (a).

10 (b), the first device 111 generates a text document based on the third program. For example, the first device 111 may create the content 1020 contained in the text document based on the user input received via the user input 16510.

Referring to FIG. 11, the first device 111 stores a text document. For example, the first device 111 may select an indicator 1110 that indicates 'storage' of a text document based on user input received via the user input 16510. Then, the first device 111 can store a text document.

The first device 111 transmits the execution history information of the text document to the server 100 after storing the text document. For example, if the first device 111 has created a document named 'kkk.ppt' having a size of 2387 kilobytes using the third program at 02:21:04 PM on Jan. 1, 2013 Assuming that the first device 111 has received at least one of kkk.ppt, image, third program, first device, January 1, 2013 02:21:04, 2387 KB, Can be transmitted.

Meanwhile, as described above with reference to FIG. 7, encryption can be further performed in addition to the job history information of a document requiring high security level and transmitted to the server 100.

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

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

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

In step S1210, the server 100 acquires the generation time information of the 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 acquired by the server 100 will be described with reference to FIG. 13 to FIG.

13 to 14 are diagrams showing 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 shown. For example, in the job history information 1310 of the document, the name 1311 of the document, the type 1312 of the document, the name 1313 of the work program, the name 1314 of the work device, A job type 1316, a job date and time 1317, and a file size 1318, but the present invention is not limited thereto. In other words, the job history information 1310 of the document may be unlimited if it is information that can be generated by performing the job of the document.

For example, the server 100 arranges the job history information 1310 received from the first device 111 on the basis of the name 1311 of the document, arranges the arranged job history information 1310 in the database 16430, Lt; / RTI >

14, another example of job history information 1410 of a document is shown. 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, the job history information 1410 of the document shown in FIG. 14 includes the name 1414 of the document, the type 1412 of the document, the name 1413 of the work program, the name 1411 of the work device, Job type 1416, job type 1415, job date and time 1417, and file size 1418. For example, the server 100 arranges the job history information 1410 received from the first device 111 on the basis of the name 1411 of the job device and arranges the arranged job history information 1410 in the database 16430).

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

FIG. 15 is a flowchart showing an example in which a server according to some embodiments links work history information to a calendar of a user.

At S1510, the server 100 acquires the user's calendar. Here, the user's calendar means a frame in which the job history information of the document is to be linked. For example, the server 100 may read the calendar of the user, which is matched with the user's account from the database 16430, and may receive the user's calendar from at least one of the devices 110. [ For example, a user's calendar can include a calendar displayed in days, a calendar in week, a calendar in month, or a calendar in year.

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 job history information, the program used for creating the document, and the name of the device that generated the document. In other words, the server 100 determines one of the name of the document, the program used for creating 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 the job history information to be displayed on the calendar based on the generated indicator.

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

Referring again to FIG. 5, at 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 execute a calendar output program installed in the second device 112, and may request the server 100 to transmit information to be displayed on the calendar after performing authentication of the user .

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

5, when the second device 112 requests the server 100 to transmit information to be displayed on the calendar in step S514, the server 100 transmits the information to be displayed on the calendar in step S515. It does not. For example, the server 100 may send (e. G., Push) information to be displayed on the calendar to the second device 112, even if there is no request for transmission of the second device 112. [

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

Hereinafter, an example of a calendar output on the screen of the device will be described with reference to Figs. 16 to 25. Fig. 16 to 25 illustrate examples of daily calendars, monthly calendars, and annual calendars for convenience of explanation, but the present invention is not limited thereto. In other words, a user's calendar can have various examples, such as a calendar displayed in weekly units, a calendar displayed in 3-day increments, and a calendar displayed in time units.

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 indicating a date desired by the user. In addition, the calendar 1620 may include an indicator 1650 capable of displaying a calendar corresponding to the 'today' date. In addition to the above-described indicators, the calendar 1620 may include without limitation any indicator that allows the user to control the display type of the calendar.

In the calendar 1620, an indicator 1660 indicating the name of the document may be displayed. For example, assuming that the first device 111 has generated a document named 'abc.doc' at 2014.05.12, the calendar 1620 indicates 'abc.doc' in the area corresponding to 2014.05.12 An indicator 1660 may be displayed.

Device 1610 may select an indicator 1660 indicating 'abc.doc' according to user input received via user input 16510. When the indicator 1660 indicating 'abc.doc' is selected, the device 1610 can output the job history information 1670 of the document to the screen. For example, if the first device 111 stores a document named 'abc.doc' with a size of 54 KB (kilobytes) at 12:28:04 pm on May 12, 2014 using the first program Assuming that the job history information 1670 includes "abc.doc, text, first program, first device, May 12, 2014 12:28:04 PM, 54 KB" may be output. On the other hand, the device 1610 can output the job history information 1670 of the document as a separate popup window on the screen.

In addition, the job history information 1670 of the document may be provided with an indicator 1680 capable of outputting the document to the screen of the device 1610. [ 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 popup window separate from the calendar 1620, 111) can output the generated document to the screen.

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

Referring to FIG. 17, a daily calendar 1720 is displayed 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. Therefore, the above description with reference to FIG. 16 for the indicators that can be displayed on the calendar 1720 can be similarly applied to FIG.

The calendar 1720 may be displayed with an indicator 1730 indicating a program used for document operation. For example, assuming that the first device 1710 has generated a document using the first program on May 05, 2012, the region corresponding to 2014.05.12 of the calendar 1720 has an indicator (" first program " 1730 may be displayed.

The device 1710 may select an indicator 1730 indicating a 'first program' according to the user input received via the user input unit 16510. When the indicator 1730 indicating 'first program' is selected, the device 1710 can output the job history information 1740 of the document to the screen. For example, if the first device 111 stores a document named 'abc.doc' with a size of 54 KB (kilobytes) at 12:28:04 pm on May 12, 2014 using the first program Assuming that the job history information 1740 includes 'abc.doc, text, first program, first device, May 12, 2014 12:28:04 PM, 54 KB' may be output. On the other hand, the device 1710 can output the job history information 1740 of the document as a separate popup window on the screen.

In addition, in the job history information 1740 of the document, an indicator 1750 capable of outputting the document to the screen of the device 1710 may be displayed. For example, if an indicator 1750 capable of outputting a document is selected in response to a user input received through the user input unit 16510, the device 1710 may display a popup window separate from the calendar 1720, 111) can output the generated document to the screen.

18 is a diagram showing another example of the daily calendar displayed on the screen of the 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. Therefore, the above description with reference to FIG. 16 for the indicators that can be displayed on the calendar 1820 can be similarly applied to FIG.

In the calendar 1820, an indicator 1830 indicating the name of the device may be displayed. For example, if the first device 111 generates a document at 2014.05.12, an indicator 1840 indicating 'first device' may be displayed in an area corresponding to 2014.05.12 of the calendar 1820 have.

The device 1810 may select an indicator 1840 indicating 'first device' according to the user input received via the user input section 16510. When the indicator 1840 indicating 'first device' is selected, the device 1810 can output the job history information 1840 of the document to the screen. For example, if the first device 111 stores a document named 'abc.doc' with a size of 54 KB (kilobytes) at 12:28:04 pm on May 12, 2014 using the first program Assuming that the job history information 1840 includes "abc.doc, text, first program, first device, May 12, 2014 12:28:04 PM, 54 KB" may be output. Meanwhile, the device 1810 can output the job history information 1840 of the document as a separate pop-up window on the screen.

Also, in the job history information 1840 of the document, an indicator 1850 capable of outputting the document to the screen of the device 1810 may be displayed. For example, if an indicator 1850 capable of outputting a document is selected in accordance with a user input received via the user input unit 16510, the device 1810 may display a popup window separate from the calendar 1820, 111) can output the generated document to 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 that indicates each of the dates included in a month and an indicator 1940 that allows the user to specify a desired month. In addition, the calendar 1920 may include an indicator 1950 capable of displaying a monthly calendar including a date of 'today'. In addition to the above-described indicators, the calendar 1920 can include any number of indicators that allow the user to control the display type.

In the calendar 1920, an indicator 1960 indicating the name of the document may be displayed. For example, assuming that the first device 111 has generated a document named 'abc.doc' in 2014.05.12, the calendar 1960 indicates 'abc.doc' in the area corresponding to 2014.05.12 An indicator 1960 may be displayed.

Device 1910 may select an indicator 1960 indicating 'abc.doc' according to user input received via user input 16510. When the indicator 1960 indicating 'abc.doc' is selected, the device 1910 can output the job history information 1970 of the document to the screen.

For example, if the first device 111 stores a document named 'abc.doc' with a size of 54 KB (kilobytes) at 12:28:04 pm on May 12, 2014 using the first program Assuming that the job history information 1970 includes 'abc.doc, text, first program, first device, May 12, 2014 12:28:04, 54 KB' may be output. On the other hand, the device 1910 can output the job history information 1970 of the document as a separate popup window on the screen.

Further, in the job history information 1970 of the document, an indicator 1980 capable of outputting the document to the screen of the device 1910 may be displayed. For example, if an indicator 1980 is selected to output a document according to a user input received through the user input unit 16510, the device 1910 may display a popup window separate from the calendar 1920, 111) can output the generated document to the screen.

20 is a diagram showing 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. FIG. The calendar 2020 shown in Fig. 20 has the same frame as the calendar 1920 shown in Fig. Therefore, the above description with reference to FIG. 19 for the indicators that can be displayed on the calendar 2020 can be similarly applied to FIG.

In the calendar 2020, an indicator 2030 indicating a program used for execution of a document may be displayed. For example, if the first device 2010 generates a document using the first program on May 05, 2012, the region corresponding to 2014.05.12 of the calendar 2020 has an indicator (" first program " 2030 may be displayed.

The device 2010 may select an indicator 2030 indicating 'first program' according to the user input received through the user input unit 16510. When the indicator 2030 indicating 'first program' is selected, the device 2010 can output the job history information 2040 of the document to the screen. For example, if the first device 111 stores a document named 'abc.doc' with a size of 54 KB (kilobytes) at 12:28:04 pm on May 12, 2014 using the first program Assuming that the job history information 2040 includes "abc.doc, text, first program, first device, May 12, 2014 12:28:04 PM, 54 KB" may be output. Meanwhile, the device 2010 can output the job history information 2040 of the document as a separate popup window on the screen.

Further, the job history information 2040 of the document may be provided with an indicator 2050 capable of outputting the document to the screen of the device 2010. [ 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 popup window separate from the calendar 2020, 111) can output the generated document to the screen.

21 is a diagram showing another example of a monthly calendar displayed on the screen of the 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 shown in Fig. 21 has the same frame as the calendar 1910 shown in Fig. Therefore, the above description with reference to FIG. 19 for the indicators that can be displayed on the calendar 2120 can be similarly applied to FIG.

The calendar 2120 may be displayed with an indicator 2130 indicating the name of the device. For example, if the first device 111 generates a document at 2014.05.12, an indicator 2130 indicating 'first device' may be displayed in an area corresponding to 2014.05.12 of the calendar 2120 have.

The device 2110 may select an indicator 2130 indicating 'first device' according to the user input received through the user input unit 16510. When the indicator 2130 indicating 'first device' is selected, the device 2110 can output the job history information 2140 of the document on the screen. For example, if the first device 111 stores a document named 'abc.doc' with a size of 54 KB (kilobytes) at 12:28:04 pm on May 12, 2014 using the first program Assume that "abc.doc, text, first program, first device, May 12, 2014 12:28:04 PM, 54 KB" may be output in the job history information 2140. On the other hand, the device 2110 can output the job history information 2140 of the document as a separate pop-up window on the screen.

In the document operation history information 2140, an indicator 2150 capable of outputting a document to the screen of the device 2110 may be displayed. For example, when an 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 popup window separate from the calendar 2120, 111) can output the generated document to the screen.

22 to 25 are diagrams showing 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 displaying the months included in one year and an indicator 2240 allowing the user to designate the desired year. In addition, the calendar 2220 may include an indicator 2250 capable of displaying a calendar of the year including the date of 'today'. In addition to the above-described indicators, the calendar 2220 may include any number of indicators that allow the user to control the display type.

Indicators 2260, 2261, 2262 indicating the name of the document may be displayed on the calendar 2220. [ For example, assuming that the first device 111 has generated a document named 'xyz.doc' in 2014.02.12, an indicator indicating 'xyz.doc' in the area corresponding to 2014.02 in the calendar 2220 2262 may be displayed.

Assuming that the first device 111 has generated a document named 'abcd.xls' in 2014.04.22, an indicator 2261 indicating 'abcd.xls' in the area corresponding to 2014.04 in the calendar 2220, May be displayed. Assuming that the first device 111 has generated a document named 'abc.doc' in 2014.05.12, the indicator 2260 indicating 'abc.doc' in the area corresponding to 2014.05 in the calendar 2220, May be displayed. In the above description, 'xyz.doc', 'abcd.xls', and 'abc.doc' are all generated by the first device 111, but different devices may generate respective documents.

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

For example, if the first device 111 stores a document named 'abc.doc' with a size of 54 KB (kilobytes) at 12:28:04 pm on May 12, 2014 using the first program I suppose. At this time, if the indicator 2260 indicating 'abc.doc' is selected, 'abc.doc', text, first program, first device, 12:28:28 PM on May 12, 04, 54 KB 'can be output. On the other hand, the device 2210 can output the job history information 2270 of the document as a separate popup window on the screen.

In the document job history information 2270, an indicator 2280 capable of outputting a document to the screen of the device 2210 may be displayed. For example, if 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 may display a popup window separate from the calendar 2220, 111) can output the generated document to the screen.

23, on the screen of the device 2310, an annual calendar 2320 is output. In the calendar 2320, an indicator 2330 indicating a program used for document work is displayed. As described above with reference to Figs. 17 and 20, when the indicator 2330 indicating the program used for the document operation is selected, the device 2310 can output the job history information 2340 of the document to the screen . When an indicator 2350 capable of outputting a document is selected on the screen on which the job history information 2340 of the document is displayed, the device 2310 can 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 the calendar 2420, an indicator 2430 indicating a device is displayed. As described above with reference to Figs. 18 and 21, when the indicator 2430 indicating the device is selected, the device 2410 can output the execution history information 2440 of the document to the screen. The device 2410 can output the document generated by the first device 111 to the screen when an indicator 2450 capable of outputting the document is selected on the screen on which the execution history information 2440 of the document is displayed .

Referring to FIG. 25, an annual calendar 2520 is output on the screen of the device 2510. The annual calendar shown in FIGS. 22 to 24 includes an area in which the months included in the year are displayed. However, in the annual calendar 2520 shown in FIG. 25, . In other words, the device 2510 can change the format of the annual calendar and output it to the screen.

In the calendar 2520, indicators 2531, 2532, and 2533 may be displayed on the date when the operation of the document is performed. For example, assuming that the first device 111 has generated a document named 'xyz.doc' in 2014.02.12, the calendar 2520 indicates 'xyz.doc' in the area corresponding to 2014.02.12 An indicator 2531 may be displayed. Assuming that the first device 111 has generated a document named 'abcd.xls' in 2014.04.22, an indicator (abcd.xls) indicating 'abcd.xls' in the area corresponding to 2014.04.22 in the calendar 2520 2532) may be displayed. Assuming that the first device 111 has generated a document named 'abc.doc' in 2014.05.12, an indicator (abc.doc) indicating 'abc.doc' in the area corresponding to 2014.05.12 in the calendar 2520 2533) may be displayed. In the above description, 'xyz.doc', 'abcd.xls', and 'abc.doc' are all generated by the first device 111, but 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 can output the job history information 2540 of the document on the screen. When an indicator 2550 capable of outputting a document is selected on the screen on which the job history information 2540 of the document is displayed, the device 2510 can output the document generated by the first device 111 to the screen .

26A to 47, when the first device 111 generates a document and the second device 112 browses the document, the server performs a task of linking the job history information to the user's calendar An example is given.

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

26A and 26B, the first device 111 generates a document and the second device 112 browses the document for convenience of explanation. However, the present invention is not limited thereto. For example, the first device 111 may generate a document and the first device 111 may view the document.

There is no limit to the number of devices. Assuming 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, Lt; RTI ID = 0.0 > N-th < / RTI >

S2610 to S2616 in Fig. 26A correspond to S510 to S516 in Fig. Therefore, even if omitted from the following description, the above description with reference to Figs. 5 to 25 can be applied to the contents described later with reference to S2610 to S2616 in 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 can transmit the job history information of the document to the server 100 at the time of storing the document. At this time, it is assumed that the user of the first device 111 is logged in the server 100. The example in which the first device 111 transmits the job history information of the document to the server 100 is as described above with reference to step S411 of FIG.

In step S2613, the server 100 links the job history information to the calendar using the 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 .

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

26A shows that the server 100 transmits information to be displayed on the calendar in S2615 when the second device 112 requests the server 100 to transmit information to be displayed on the calendar in S2614, It is not limited. For example, the second device 112 may transmit (e. G., Push) information to be displayed on the calendar, even if there is no transmission request of the second device 112. [

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

In S2617, the second device 112 requests the first device 111 to transfer the document. For example, if a predetermined indicator displayed on the calendar is selected in response to a user input received at the second device 112, the second device 112 may request the first device 111 to transmit the document. For example, the predetermined indicator may refer to an indicator 1680 that can output the document displayed in the calendar 1620 of FIG.

In S2618, the first device 111 transmits the document to the second device 112 in response to a request from the second device 112. [

As an example, the second device 112 may request the transmission of the document to the first device 111 and receive the document from the first device 111. [ Alternatively, the second device 112 may request the server 100 to transmit the document, and may 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 is a diagram for explaining an example in which a second device according to some embodiments requests a first device to transmit a document and receives a document.

27, a calendar 2710 output on the screen of the second device 112 is shown. Here, the calendar 2710 means a calendar output on the screen of the second device 112 according to S2616 in Fig. 26A.

The second device 112 receives a user input that selects the indicator 2720 displayed on the calendar 2710 via the user input 16510. [ The second device 112 outputs the job history information 2730 of the document on the screen according to the received user input. At this time, on the screen displaying the job history information 2730 of the document, an indicator 2740 capable of outputting the document to the screen of the second device 112 may be displayed.

When the indicator 2740 is selected by the user, a preview screen of the document or an execution screen of the document can be output to the second device 112. [ As an example, if the user touches the indicator 2740 for a short time, a preview screen of the document can be output, and if the user touches the indicator 2740 for a long time, the execution screen of the document can be output. As another example, if the cursor displayed on the screen of the second device 112 is located on the indicator 2740, a preview screen of the document can be output, and if the user clicks the indicator 2740, Can be output.

The second device 112 receives a user input (e.g., a long touch or click) to select the indicator 2740 through the user input 16510. [ The second device 112 requests (2750) the document to be transmitted 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 again to FIG. 26A, in step S2619, the second device 112 outputs the document transmitted from the first device 111 to the screen.

In S2620, the second device 112 ends the output of the document. An example in which the output of the document is terminated by the second device 112 will be described below with reference to Figs. 28 to 30. Fig.

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

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 that terminates the output 2810 of the document through the user input 16510. [ For example, the user input may be input 2820, 2910 for terminating the program executing the document, or may be input 3010 for closing the window for outputting the document while maintaining the execution of the program.

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

29, the second device 112 receives a user input for selecting an indicator 2910 displayed on the screen. Then, the second device 112 terminates 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 again to FIG. 26B, in step S2621, the second device 112 transmits the job history information of the document to the server 100. FIG. For example, the second device 112 may transmit the job history information of the document to the server 100 at the point of time when the execution of the document is terminated (that is, the end of the output of the document). Hereinafter, an example in which the second device 112 transmits the job history information of the document to the server 100 will be described with reference to FIG.

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

As described above with reference to Figs. 28 to 30, the second device 112 can terminate the outputting of the document by closing the window for executing the document or closing the window for outputting the document. The second device 112 judges that the document has been browsed when the second device 112 has terminated the program without adding or deleting the content of the document or closed the window for outputting the document.

When the program executing the document is terminated or the window outputting the document 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 the created information to the server 100 as it browses the document.

For example, if the second device 112 executes a document named 'abc.doc' with a size of 54 kilobytes using the first program and the second device 112 executes the document named 'abc.doc' The second device 112 informs the server 100 of 'abc.doc, text, first program, second program, and so on, assuming that the first program is terminated at 08:46:11 PM or the window where the document is output is closed. Device, May 20, 2014 at 08:46:11 PM, and 54 KB '.

Meanwhile, as described above with reference to FIG. 7, encryption can be further performed in addition to the job history information of a document requiring high security level and transmitted to the server 100.

Referring again to FIG. 26B, in step S2622, the server 100 links the job history information to the calendar using the time information included in the job history information transmitted from the second device 112. FIG. 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 displayed on the screen of the device, by selecting an indicator to be displayed on the calendar or an indicator to be displayed on the calendar.

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

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

26B, in step S2623, when the first device 111 requests the server 100 to transmit the transmission of the information to be displayed on the calendar, the server 100 is shown as transmitting the information to be displayed on the calendar in step S2624 , But is not limited thereto. For example, the server 100 may transmit (e.g., push) information to be displayed on the calendar to the first device 111, even if there is no transmission request of the first device 111. [

The contents to be described later with reference to S2626 to S2628 correspond to the above-described contents with reference to S2623 to S2625. In other words, the second device 112 requests the server 100 to transmit the information to be displayed on the calendar, receives the information to be displayed on the calendar from the server 100, and outputs the calendar to the screen. Therefore, the contents described above with reference to S2623 to S2625 can be applied to the contents 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 the information to be displayed on the calendar to the second device 112. [

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

A specific example of the above-described contents with reference to S2622 to S2628 in Fig. 26B will be described later with reference to Figs. 34 to 47. Fig.

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

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

Comparing the flowchart shown in Figs. 26A to 26B 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. S3220 to S3229 in Figs. 32A to 32B are the same as S2619 to S2628 in Figs. 26A to 26B. Therefore, the detailed description of S3210 to S3211 and S3220 to S3229 in Figs. 32A to 32B will be omitted below.

In step S3212, the first device 111 transmits information about the execution of the document and 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. At this time, it is assumed that the user of the first device 111 is logged in the server 100. The example in which the first device 111 transmits the job history information of the document to the server 100 is as described above with reference to step S411 of FIG.

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

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

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

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

At S3217, the second device 112 outputs the calendar to the screen.

At S3218, the second device 112 requests the server 100 to transfer the document. For example, if an indicator requesting execution of a document displayed on the calendar is selected in response to a user input of the second device 112, the second device 112 may request the server 100 to transmit the document. For example, if a predetermined indicator displayed on the calendar is selected according to the user input received at the second device 112, the second device 112 may request the server 100 to transmit the document. For example, the predetermined indicator may refer to an indicator 1680 that can output the document displayed in the calendar 1620 of FIG.

In step S3219, the server 100 transmits the document to the second device at the request of the second device 112. [

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

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

33, a calendar 3310 output on the screen of the second device 112 is shown. The second device 112 receives a user input for selecting the indicator 3320 displayed on the calendar 3310 via the user input section 16510. [ The second device 112 outputs job history information 3330 of the document on the screen according to the received user input. At this time, the second device 112 can output the job history information 3330 of the document to the screen as a pop-up window separate from the calendar 3310. [ Also, on the screen displaying the job history information 3330 of the document, an indicator 3340 capable of outputting the document to the screen of the second device 112 may be displayed.

When the indicator 2740 is selected by the user, a preview screen of the document or an execution screen of the document can be output to the second device 112. [ As an example, if the user touches the indicator 2740 for a short time, a preview screen of the document can be output, and if the user touches the indicator 2740 for a long time, the execution screen of the document can be output. As another example, if the cursor displayed on the screen of the second device 112 is located on the indicator 2740, a preview screen of the document can be output, and if the user clicks the indicator 2740, Can be output.

The second device 112 receives a user input (e.g., a long touch or click) to select the indicator 3340 through the user input 16510. [ The second device 112 requests (3350) the document to be transmitted to the first device 111 according to the received user input. Then, the first device 111 transmits (3360) the document to the second device 112 according to the request of the second device 112.

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

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

In step S3410, the server 100 acquires browsing 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. 31, the server 100 acquires '2014.05.20, af 08:46:04' from the job history information received from the second device 112.

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

35 to 36 are diagrams showing 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. In other words, the job history information 1310 of the document shown in FIG. 13 means the job history information 1310 generated as the device generates the document. Meanwhile, the job history information 3510 of the document shown in FIG. 35 indicates that the new job history information 3520 and 3530 is added as the device generates the 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 name 3511 of the document.

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. In other words, the job history information 1410 of the document shown in Fig. 14 means the job history information 1310 generated as the device generates the document. Meanwhile, the job history information 3610 of the document shown in FIG. 36 indicates that the new job history information 3620 and 3630 are added as the device generates the document and at least one of the devices reads the generated document do.

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

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

37 is a flowchart showing an example in which a server according to some embodiments links work history information to a calendar of a user.

In S3710, the server 100 acquires the calendar of the created user. Here, the pre-created user calendar means a calendar created by 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 job history information, the program used to browse the document, and the name of the device that viewed the document. Here, the job history information means the job history information received from the second device 112. [ For example, the server 100 can determine any one of the name of the document, the program used to browse the document, and the name of the device that viewed the document, as an item indicated by the indicator, and generate an indicator based on the determined item have.

In S1530, the server 100 determines the 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 is viewed on the calendar, and displays the result.

An example in which the calendar is output to the screen of the device will be described below with reference to Figs. 38 to 47. Fig. The calendars shown in Figs. 38 to 47 correspond to the calendars shown in Figs. 16 to 25 updated. Therefore, the contents described above with reference to Figs. 16 to 25 are also applied to Figs. 38 to 47 even if omitted from the following description.

38 to 40 are diagrams showing examples of daily calendars displayed on the screen of the device according to some embodiments.

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

In the calendar 3811, not only the indicator 3820 displayed on the pre-created calendar, but also the indicator 3830 can be additionally displayed by updating the calendar. Here, the directors 3820 and 3830 may be indicators indicating the name of the document.

For example, if it is assumed that the second device 112 has browsed the document generated by the first device 111 on 2014.05.20, "abc.doc" is added to the area corresponding to 2014.05.20 on the calendar 3811 An indicator 3830 may be additionally displayed.

The device 3810 may select at least one of the indicators 3820, 3830 according to user input received via the user input 16510. Then, the device 3810 can output the job history information 3821, 3831 corresponding to the selected indicator to the screen. Indicators 3822 and 3832 capable of outputting a document to the screen of the device 3810 can be displayed on the screen displaying the job history information 3821 and 3831. [

39, another example of the daily calendar 3911 is output on the screen of the device 3910. [

In the calendar 3911, not only the indicator 3920 displayed on the pre-created calendar but also the indicator 3930 can be additionally displayed by updating the calendar. Here, the directors 3920 and 3930 may be indicators indicating the name of the program used to execute the document.

For example, if it is assumed that the second device 112 browsed the document generated by the first device 111 using the first program on 2014.05.20, then in the area corresponding to 2014.05.20 on the calendar 3910 An indicator 3930 indicating 'first program' may be additionally displayed.

The job history information 3921 and 3931 of the document and the directors 3922 and 3932 capable of outputting the document to the screen of the device 3910 are displayed on the screen of the device 3910 in accordance with the user input received through the user input unit 16510. [ ) Can be displayed as described above with reference to FIG.

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

In the calendar 4011, not only the indicator 4020 displayed on the pre-created calendar but also the indicator 4030 can be additionally displayed by updating the calendar. Here, the directors 4020 and 4030 may be indicators indicating the name of the device that executed the document.

For example, if it is assumed that the second device 112 has browsed the document generated by the first device 111 on 2014.05.20, a 'second device' is displayed in the area corresponding to 2014.05.20 in the calendar 4011 An indicator 4030 indicating an indicator may be additionally displayed.

The job history information 4021 and 4031 of the document and the directors 4022 and 4032 capable of outputting the document to the screen of the device 4010 are displayed on the screen of the device 4010 according to the user input received through the user input unit 16510 ) Can be displayed as described above with reference to FIG.

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

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

In the calendar 4111, not only the indicator 4120 displayed on the pre-created calendar but also the indicators 4130 and 4140 can be additionally displayed by updating the calendar. Here, the directors 4120, 4130, and 4140 may be indicators indicating the name of the document.

For example, if it is assumed that the second device 112 has browsed the document generated by the first device 111 on 2014.05.20, "abc.doc" is added to the area corresponding to 2014.05.20 on the calendar 4111 An indicator 4130 may be additionally displayed. Assuming that the third device 113 has read a document named "kkk.ppt" on 2014.05.28, an indicator ("kkk.ppt") indicating "kkk.ppt" is displayed in the area corresponding to 2014.05.28 in the calendar 4111 4140 may be additionally displayed.

The job history information 4151 and the job history information 4152 of the document and the directors 4161 and 4162 capable of outputting the document to the screen of the device 4110 are displayed on the screen of the device 4110 according to the user input received through the user input unit 16510. [ ) Can be displayed as described above with reference to FIG.

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

In the calendar 4211, the directors 4230 and 4240 can be additionally displayed by updating the calendar as well as the indicators displayed on the pre-created calendar. Here, the directors 4130 and 4140 may be indicators indicating the name of the program used to execute the document.

For example, if it is assumed that the second device 112 has browsed the document generated by the first device 111 using the first program on 2014.05.20, then the calendar 4211 displays an area corresponding to 2014.05.20 An indicator 4230 indicating 'first program' may be additionally displayed. Assuming that the third device 113 reads a document named 'kkk.ppt' on the 2014.05.28 by using the third program, the third device 113 reads '3rd document' in the area corresponding to 2014.05.28 in the calendar 4211 An indicator 4240 indicating a 'program' may be additionally displayed.

The job history information 4251 and the job history information 4252 of the document and the directors 7261 and 4262 capable of outputting the document to the screen of the device 4210 are displayed on the screen of the device 4210 according to the user input received through the user input unit 16510. [ ) Can be displayed as described above with reference to FIG.

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

In the calendar 4311, the directors 4330 and 4340 can be additionally displayed by updating the calendar as well as the indicators displayed on the pre-created calendar. Here, the directors 4330 and 4340 may be indicators indicating the name of the device that executed the document.

For example, if it is assumed that the second device 112 has browsed the document generated by the first device 111 on 2014.05.20, a 'second device' is displayed in the area corresponding to 2014.05.20 on the calendar 4311 An indicator 4330 may be additionally displayed. Assuming that the third device 113 has read the document named 'kkk.ppt' on 2014.05.28, the 'third device 113' is added to the area corresponding to 2014.05.28 in the calendar 4311 An indicator 4340 may be additionally displayed.

According to the user input received through the user input unit 16510, an instruction for outputting the job history information 4351 or 4352 of the document and the document to the screen of the device 4310 can be displayed on the screen of the device 4310 Is as described above with reference to FIG.

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

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

Indicators 4420, 4430, 4440, and 4450 indicating the name of the document may be displayed in the calendar 4411. For example, assuming that the first device 111 has generated a document named 'xyz.doc' in 2014.02.12, an indicator indicating 'xyz.doc' in the area corresponding to 2014.02 in the calendar 4411 ( 4420 may be displayed.

Assuming that the first device 111 has generated a document named 'abcd.xls' in 2014.04.22, an indicator 4430 indicating 'abcd.xls' in the area corresponding to 2014.04 in the calendar 4411, May be displayed.

Assuming that the first device 111 has generated a document named 'abc.doc' in 2014.05.12, an indicator 4440 indicating 'abc.doc' in the area corresponding to 2014.05 in the calendar 4411, May be displayed. Assuming that the first device 111 has generated a document named 'kkk.ppt' on 2014.05.20, an indicator 4450 indicating 'kkk.ppt' in the area corresponding to 2014.05 in the calendar 4411, May be displayed.

Although it has been described in the foregoing that 'xyz.doc', 'abcd.xls', 'abc.doc', and 'kkk.ppt' are both generated by the first device 111, It is possible.

The device 4410 may select an indicator 4420, 4430, 4440, 4450 indicating the name of the document according to the user input received via the user input section 16510. [ When the directors 4420, 4430, 4440, and 4450 indicating the name of the document are selected, the device 4410 can output the job history information 4460 of the document to the screen.

For example, if the first device 111 stores a document named 'abc.doc' with a size of 54 KB (kilobytes) at 12:28:04 pm on May 12, 2014 using the first program I suppose. Also, the second device 112 reads the document named 'abc.doc' with the size of 54 KB (kilobytes) using the first program on May 20, 2014 at 08:46:11 PM I suppose.

At this time, if 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 can be output, 1 abc.doc, text, first program, first device, May 12, 2014 12:28:04 PM, 54 KB 'may be output to the 1 job history information 4462, and the second job history information Quot; abc.doc, text, first program, second device, May 20, 2014 at 08:46:11, 54 KB 'may be output to the application program 4463. On the other hand, the device 4410 can output the job history information 4460 of the document as a separate popup window on the screen.

Further, in the job history information 4460 of the document, an indicator 4461 capable of outputting the document to the screen of the device 4410 may be displayed. 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 popup window separate from the calendar 4411, 111) can output the generated document to the screen.

Referring to FIG. 45, an annual calendar 4511 is output on the screen of the device 4510. In the calendar 4511, indicators 4520, 4530, 4540, and 4550 indicating a program used for document work are displayed. As described above with reference to Fig. 44, when the indicators 4520, 4530, 4540, and 4550 indicating the programs used for the document operation are selected, the device 4510 displays the first operation history information 4562 and the second operation It is possible to output the job history information 4560 of the document including the history information 4563 to the screen. When an indicator 4561 capable of outputting a document is selected on the screen on which the job history information 4560 of the document is displayed, the device 4510 can 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. 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 can output the execution history information 4670 of the document to the screen. When an indicator 4671 capable of outputting a document is selected on the screen in which the execution history information 4670 of the document is displayed, the device 4610 can 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 displaying the months included in one year, but the yearly calendar 4711 shown in FIG. 47 includes an area showing the days included in the year have. In other words, the device 4710 can change the format of the annual calendar and output it to the screen.

In the calendar 4711, indicators 4720, 4721, 4722, 4730 and 4731 may be displayed on the date when the operation of the document is performed. For example, assuming that the first device 111 has generated a document named 'xyz.doc' on 2014.02.12, the calendar 4711 indicates 'xyz.doc' in the area corresponding to 2014.02.12 An indicator 4720 may be displayed.

Assuming that the first device 111 has generated a document named 'abcd.xls' on 2014.04.22, an indicator (abcd.xls) indicating 'abcd.xls' in the area corresponding to 2014.04.22 in the calendar 4711 4722 may be displayed.

Assuming that the first device 111 has generated a document named 'abc.doc' on December 31st, 2014, an indicator (abc.doc) indicating 'abc.doc' in the area corresponding to 2014.05.12 4721) may be displayed. Assuming that the first device 111 has generated a document named 'kkk.ppt' on 2014.05.20, an indicator ('kkk.ppt') indicating 'kkk.ppt' is displayed in the area corresponding to 2014.05.20 in the calendar 4711 4730) may be displayed.

In the above description, 'xyz.doc', 'abcd.xls', and 'abc.doc' are all generated by the first device 111, but different devices may generate documents.

The device 4710 may select the directives 4720, 4721, 4722, 4730, 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 may use the third program to send a document named "kkk.ppt", which has a size of 54 kilobytes (KB), at 08:21:11 PM on May 28, 2014 . At this time, if the indicator 4731 indicating 'kkk.ppt' is selected, the job history information 4750 can be output. In the job history information 4750, 'kkk.ppt', text, , May 28, 2014 at 08:21:11 pm, 2387 KB '. On the other hand, the device 4710 can output the job history information 4750 of the document as a separate popup window on the screen.

When an indicator 4742 capable of outputting a document is selected on the screen on which the job history information 4750 of the document is displayed, the device 4710 can output the document viewed by the third device 113 on the screen .

Hereinafter, with reference to FIGS. 48A to 65, when the first device 111 generates a document and the second device 112 edits a document, the server 100 stores the operation history information in the user's calendar An example of interworking is explained.

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

In FIGS. 48A to 48B, the first device 111 generates a document and the second device 112 edits a document for convenience of explanation. However, 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.

There is no limit to the number of devices. Assuming 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, Lt; RTI ID = 0.0 > N-th < / RTI >

S4810 to S4816 in Fig. 48A correspond to S510 to S516 in Fig. Therefore, even if omitted from the following description, the above description with reference to Figs. 5 to 25 can be applied to the contents described later with reference to S4810 to S4816 in 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 step S4812, the first device 111 transmits the job history information of the document to the server 100. [ For example, the first device 111 can transmit the job history information of the document to the server 100 at the time of storing the document. At this time, it is assumed that the user of the first device 111 is logged in the server 100. The example in which the first device 111 transmits the job history information of the document to the server 100 is as described above with reference to step S411 of FIG.

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

At 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 .

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

48A shows that when the second device 112 requests the server 100 to transmit the information to be displayed on the calendar in step S4814, the server 100 transmits the information to be displayed on the calendar in step S4815, It is not limited. For example, the second device 112 may transmit (e. G., Push) information to be displayed on the calendar, even if there is no transmission request of the second device 112. [

At S4816, the second device 112 outputs the calendar to the screen.

At 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 a document, and output the document received from the first device 111 to the screen. As another example, the second device 112 may request the server 100 to transmit a document, and output the document received from the server 100 to the screen.

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

At 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. FIG.

49 to 50 are diagrams for explaining examples in which a second device 112 according to some embodiments edits a document.

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 via a user input 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. Although not shown in the figure, 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 a document, new content is added 4920 to the output document 4910.

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

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

At S4820, the second device 112 transmits the job history information of the document and the document that have been edited and stored to the server 100. [ For example, the second device 112 may transmit the job history information of the document and the document to the server 100 at the time when the editing of the document ends (that is, at the time when the document is stored). Hereinafter, an example in which the second device 112 transmits job history information of a document and a document to the server 100 will be described with reference to FIG.

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

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

When the document is stored after being edited, the second device 112 transmits the job history information of the document and the document to the server 100. In other words, the second device 112 transmits the created information to the server 100 as the document is edited.

For example, the second device 112 may execute and edit a document named 'abc.doc' using the first program, and store the edited document at 09:11:43 PM on May 14, 2014 And the size of the document stored after editing is 1084 kilobytes, the second device 112 informs the server 100 of 'abc.doc, text, first program, second device, afternoon of May 14, 2014 09:11:43, and 1084 KB 'as job history information.

Meanwhile, as described above with reference to FIG. 7, encryption can be further performed in addition to the job history information of a document requiring high security level and transmitted to the server 100.

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

In step S4822, the server 100 links the job history information to the calendar using the 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 step S4813, and additionally links the job history information received from the second device 112 to the calendar in step 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 displayed on the screen of the device, by selecting an indicator to be displayed on the calendar or an indicator to be displayed on the calendar.

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

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

In Fig. 48B, in step 4823, 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 be displayed on the calendar in step 4824, It is not limited. For example, the server 100 may transmit (e.g., push) information to be displayed on the calendar to the first device 111, even if there is no transmission request of the first device 111. [

The contents to be described later with reference to S4826 to S4828 correspond to those described above with reference to S4823 to S4825. In other words, the second device 112 requests the server 100 to transmit the information to be displayed on the calendar, receives the information to be displayed on the calendar from the server 100, and outputs the calendar to the screen. Therefore, even if the content is omitted in the following description, the above description with reference to S4823 to S4825 can be applied to the contents described later with reference to S4826 to S4828.

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

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

At S4828, the second device 112 outputs a calendar to the screen.

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

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

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

In S5210, the server 100 acquires the edit 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. 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 job history information acquired by the server 100 will be described with reference to FIGS. 53 to 54. FIG.

53 to 54 are views showing 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. In other words, the job history information 1310 of the document shown in FIG. 13 means the job history information 1310 generated as the device generates the document. Meanwhile, the job history information 5310 of the document shown in FIG. 53 indicates that the new job history information 5320 and 5330 are added as the device generates the document and at least one of the devices edits the created 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. In other words, the job history information 1410 of the document shown in Fig. 14 means the job history information 1410 generated as the device generates the document. On the other hand, the job history information 5410 of the document shown in FIG. 54 indicates that the new job history information 5420 and 5430 are added as the device creates the document and at least one of the devices edits the created document do.

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

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

55 is a flowchart showing an example in which the server 100 according to some embodiments links work history information to a calendar of a user.

In S5510, the server 100 acquires the calendar of the created user. Here, the pre-created user's calendar means a calendar created by linking the job history information transmitted from the first device 111 by the server 100 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 job 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 the job history information received from the second device 112. [ For example, the server 100 can determine 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 have.

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

In S5540, the server 100 adds an indicator to the area corresponding to the date or time indicating the time at which the document is edited in the calendar, and displays the result.

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. FIG. The calendar 5611 may include an area 5612 indicating dates and an indicator 5613 allowing the user to specify a desired date. In addition, 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 can be included without limitation as long as it is an indicator that allows the user to control the display type of the calendar.

In the calendar 5611, an indicator 5620 indicating the name of the document may be displayed. For example, if the first device 111 edits a document named 'abc.doc' on 2014.05.14, the calendar 5611 indicates 'abc.doc' in the area corresponding to 2014.05.12 An indicator 5620 may be displayed.

Device 5610 may select an indicator 5620 indicating 'abc.doc' according to user input received via user input 16510. When the indicator 5620 indicating 'abc.doc' is selected, the device 5610 can output the job history information 5621 of the document to the screen. For example, if the second device 112 edited a document named 'abc.doc' with a size of 1084 kilobytes using the first program at 09:11:43 PM on May 14, 2014 Assume that "abc.doc, text, first program, second device, May 14, 2014 09:11:43 PM, 1084 KB" may be output in the job history information 5621. On the other hand, the device 5610 can output the job history information 5621 of the document as a separate pop-up window on the screen.

Indicators 5622 and 5623 capable of 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 original document at the time of document creation or an indicator indicating a document before the current operation, and the indicator 5623 may be an indicator indicating the current editing document.

The indicator 5623 indicating the edited document can be distinguished from the original document or the indicator 5622 indicating the document before the current operation. For example, in the case of the indicator 5623 of the editing document, a border line may be additionally displayed in the indicator 5622 indicating the original document or the document before the current operation. 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 a popup window separate from the calendar 5611, Alternatively, the document edited by the second device can be output to the screen.

Similarly, in one calendar 5611, a plurality of directives indicating the name of the document can be displayed. For example, if the third device 113 edits a document named 'xyz.doc' in 2014.05.12, the calendar 5611 indicates 'xyz.doc' in the area corresponding to 2014.05.12. An indicator 5630 may be displayed.

Device 5610 may select an indicator 5630 indicating 'xyz.doc' according to user input received via user input 16510. When the indicator 5630 indicating 'xyz.doc' is selected, the device 5610 can output the job history information 5631 of the document to the screen. For example, if the third device 113 edited a document titled 'xyz.doc' with a size of 2387 kilobytes by 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, 2387 KB" may be output to the job history information 5631. On the other hand, the device 5610 can output the job history information 5631 of the document as a separate popup window on the screen.

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

The indicator 5633 indicating the editing document can be displayed differently from the original document or the indicator 5632 indicating the document before the current operation. For example, in the case of the indicator 5633 of the edit document, a border line may be additionally displayed in the indicator 5632 indicating the original document or the document before the current operation. When an indicator 5632 or 5633 capable of outputting a document according to a user input received through the user input unit 16510 is selected, the device 5610 displays a popup window separate from the calendar 5611, It is possible to output the edited document on the screen.

57 is a diagram showing another example of the daily calendar displayed on the screen of the 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. Therefore, the above description with reference to FIG. 56 for the objects that can be displayed on the calendar 5711 can be similarly applied to FIG.

The calendar 5711 may be displayed with an indicator 5720 indicating a program used for document operation. For example, if it is assumed that the second device edited the document using the first program on 2014.05.14, an indicator 5720 indicating 'first program' is displayed in the area corresponding to 2014.05.12 of the calendar 5711 Can be displayed.

The device 5710 may select an indicator 5720 indicating a 'first program' according to the user input received via the user input 16510. When the indicator 5720 indicating 'first program' is selected, the device 5710 can output the job history information 5721 of the document to the screen. For example, if the second device 112 edited a document named 'abc.doc' with a size of 1084 kilobytes using the first program at 09:11:43 PM on May 14, 2014 Assume that "abc.doc, text, first program, second device, May 14, 2014 09:11:43 PM, 1084 KB" may be output to the job history information 5721. On the other hand, the device 5710 can output the job history information 5721 of the document as a separate pop-up window on the screen.

In the job history information 5721 of the document, indicators 5722 and 5723 capable of outputting the document to the screen of the device 5710 may be displayed. The indicator 5722 may be an original document at the time of document creation or an indicator indicating a document before the current operation, and the indicator 5723 may be an indicator indicating the current editing document.

The indicator 5723 indicating the editing document can be displayed separately from the original document or the indicator 5722 indicating the document before the current operation. For example, in the case of the indicator 5723 of the editing document, a border line may be displayed in the indicator 5722 indicating the original document or the document before the current operation. When an indicator 5722 or 5723 capable of outputting a document according to a user input received through the user input unit 16510 is selected, the device 5710 displays a popup window separate from the calendar 5711, The edited document can be displayed on the screen.

Similarly, a plurality of indicators indicating a program may be displayed in one calendar 5711. [ For example, if the third device 113 edits a document named 'xyz.doc' in 2014.05.12, the calendar 5711 indicates 'first program' in the area corresponding to 2014.05.12. An indicator 5730 may be displayed.

The device 5710 may select an indicator 5730 indicative of a 'first program' in accordance with the user input received via the user input 16510. When the indicator 5730 indicating 'first program' is selected, the device 5710 can output the job history information 5731 of the document to the screen. For example, if the third device 113 edited a document named 'xyz.doc' having a size of 2384 kilobytes by using the first program at 09:14:03 am on May 12, 2014 Assume that xyz.doc, text, first program, third device 113, 09:14:03 am, May 23, 2014, 2387 KB 'may be output to the job history information 5731. On the other hand, the device 5710 can output the job history information 5731 of the document as a separate popup window on the screen.

In the job history information 5731 of the document, an indicator 5732 capable of outputting the document to the screen of the device 5710 may be displayed. 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 popup window separate from the calendar 5711, 113) can output the edited document to the screen.

58 is a diagram showing another example of the daily calendar displayed on the screen of the 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. Therefore, the above description with reference to FIG. 56 for the indicators that can be displayed on the calendar 5811 can be similarly applied to FIG.

In the calendar 5811, an indicator 5820 indicating the name of the device may be displayed. For example, if the second device 112 has edited the document at 2014.05.14, an indicator 5820 indicating 'second device' may be displayed in the area corresponding to 2014.05.12 of the calendar 5811 have.

Device 5810 may select an indicator 5820 indicating 'second device' in accordance with user input received via user input 16510. When the indicator 5820 indicating 'second device' is selected, the device 5810 can output the job history information 5821 of the document to the screen. For example, if the second device 112 edited a document named 'abc.doc' with a size of 1084 kilobytes using the first program at 09:11:43 PM on May 14, 2014 Assume that "abc.doc, text, first program, second device, May 14, 2014 09:11:43 PM, 1084 KB" may be output to the job history information 5821. On the other hand, the device 5810 can output the job history information 5821 of the document as a separate popup window on the screen.

Further, in the job history information 5821 of the document, indicators 5822 and 5823 capable of outputting the document to the screen of the device 5810 may be displayed. The indicator 5822 may be an original document at the time of document creation or an indicator indicating a document before the current operation, and the indicator 5823 may be an indicator indicating the current editing document.

The indicator 5823 indicating the editing document can be displayed separately from the original document or the indicator 5822 indicating the document before the current operation. For example, in the case of the indicator 5823 of the editing document, a border line may be additionally displayed in the indicator 5822 indicating the original document or the document before the current operation. When an indicator 5822 or 5823 capable of outputting a document according to a user input received through the user input unit 16510 is selected, the device 5810 displays a popup window separate from the calendar 5811, The edited document can be displayed on the screen.

Similarly, in one calendar 5811, a plurality of directives indicating the name of the device can be displayed. For example, if the third device 113 edits a document named 'xyz.doc' in 2014.05.12, the third device 113 is displayed in the area corresponding to 2014.05.12 in the calendar 5811, An indicator 5830 indicating 'can be displayed.

The device 5810 may select an indicator 5830 indicating 'third device 113' in accordance with the user input received via the user input 16510. When the indicator 5830 indicating 'the third device 113' is selected, the device 5810 can output the job history information 5831 of the document to the screen. For example, when the third device 113 reads a document named 'xyz.doc' having a size of 2387 kilobytes by using the first program at 09:14:03 AM on May 12, 2014 Assume that "xyz.doc, text, first program, third device 113, 09:14:03 am, May 23, 2014, 2387 KB" may be output to the job history information 5831. On the other hand, the device 5810 can output the job history information 5831 of the document as a separate popup window on the screen.

In the job history information 5831 of the document, indicators 5832 and 5833 capable of outputting the document to the screen of the device 5810 may be displayed. The indicator 5832 may be an original document at the time of document creation or an indicator indicating a document prior to the current operation, and the indicator 5833 may be an indicator indicating the current editing document. The indicator 5833 indicating the editing document can be displayed separately from the original document or the indicator 5832 indicating the document before the current operation. For example, in the case of the indicator 5833 of the editing document, a border line may be additionally displayed in the indicator 5832 indicating the original document or the document before the current operation. If an indicator 5832 or 5833 capable of outputting a document according to a user input received through the user input unit 16510 is selected, the device 5810 displays a popup window separate from the calendar 5811, The edited document can be displayed 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.

59, on the screen of the device 5910, a monthly calendar 5911 is outputted. The calendar 5911 shown in Fig. 59 has the same frame as the calendar 1920 shown in Fig. Accordingly, the above-described contents with reference to FIG. 19 for the objects that can be displayed on the calendar 5911 can be similarly applied to FIG.

In the calendar 5911, an indicator 5930 indicating the name of the document and an indicator 5940 may be displayed. For example, if the second device 112 edits a document named 'abc.doc' on 2014.05.14, the calendar 5911 indicates 'abc.doc' in the area corresponding to 2014.05.14. An indicator 5930 may be displayed. Likewise, if the third device 113 edits a document named 'xyz.doc' on 2014.05.14, an indicator indicating 'xyz.doc' in the area corresponding to 2014.05.14 in the calendar 5911 5940 may be displayed.

Device 5910 may select an indicator 5930 indicating 'abc.doc' according to user input received via user input 16510. When the indicator 5930 indicating 'abc.doc' is selected, the device 5910 can output the job history information 5951 of the document to the screen.

For example, if the second device 112 stores a document named 'abc.doc' with a size of 1084 kilobytes using the first program at 09:11:43 PM on May 14, 2014 Assume that "abc.doc, text, first program, second device, May 14, 2014 09:11:43 PM, 1084 KB" may be output to the job history information 5951. On the other hand, the device 5910 can output the job history information 5951 of the document as a separate popup window on the screen.

Similarly, the device 5910 may select an indicator 5940 indicating 'xyz.doc' according to the user input received via the user input 16510. When the indicator 5940 indicating 'xyz.doc' is selected, the device 5910 can output the job history information 5952 of the document to the screen.

For example, if the third device 113 stores a document named 'xyz.doc' with a size of 2387 kilobytes 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 at 09:14:03, 2387 KB 'may be output in the job history information 5952. On the other hand, the device 5910 can output the job history information 5952 of the document as a separate pop-up window on the screen.

In the job history information 5951 of the document, an indicator 5961 and an indicator 5971 capable of outputting a document to the screen of the device 5910 may be displayed. 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 popup window separate from the calendar 5911, 112 can output the document before editing on the screen. In addition, when the indicator 5971 is selected, the device 5910 can output a document edited by the second device 112 as a pop-up window separate from the calendar 5911 on the screen.

Similarly, in the job history information 5952 of the document, an indicator 5962 and an indicator 5972 capable of outputting the document to the screen of the device 5910 may be displayed. 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 popup window separate from the calendar 5911, 113 can output the document before editing on the screen. When the indicator 5972 is selected, the device 5910 can output a document edited by the third device 113 to the screen as a pop-up window separate from the calendar 5911. [

60 is a diagram showing 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. Therefore, the above-described contents with reference to FIG. 19 for objects that can be displayed on the calendar 6011 can be similarly applied to FIG.

In the calendar 6011, an indicator 6030 and an indicator 6040 indicating a program used for document operation can be displayed. For example, assuming that the second device 6010 edited the document using the first program on 2014.05.14, the region corresponding to 2014.05.14 of the calendar 6020 has an indicator (" first program " 6030 may be displayed. Similarly, assuming that the third device 113 edited the document using the first program on 2014.05.14, an indicator 6040 indicating 'first program' is displayed in the area corresponding to 2014.05.14 in the calendar 6011, May be displayed.

The device 6010 may select an indicator 6030 indicating 'first program' according to the user input received via the user input unit 16510. When the indicator 6030 indicating 'first program' is selected, the device 6010 can output the job history information 6051 of the document to the screen. For example, if the second device 112 stores a document named 'abc.doc' with a size of 1084 kilobytes using the first program at 09:11:43 PM on May 14, 2014 Assuming that the job history information 6051 includes "abc.doc, text, first program, second device, May 14, 2014 at 09:11:43, 1084 KB" may be output. On the other hand, the device 6010 can output the job history information 6051 of the document as a separate popup window on the screen.

Similarly, the device 6010 may select an indicator 6040 indicating a 'first program' according to user input received via the user input 16510. When the indicator 6040 indicating 'first program' is selected, the device 6010 can output the job history information 6052 of the document to the screen. For example, if the third device 113 stores a document named 'xyz.doc' with a size of 2387 kilobytes using the first program at 09:14:03 am on May 14, 2014 Assume that the job history information 6052 includes' xyz.doc ', text, first program, third device, May 14, 2014 at 09:14:03 and 2387 KB'. On the other hand, the device 6010 can output the job history information 6052 of the document as a separate popup window on the screen.

Further, in the job history information 6051 of the document, an indicator 6061 and an indicator 6071 capable of outputting a document to the screen of the device 6010 may be displayed. For example, if 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 popup window separate from the calendar 6020, 112 can output the document before editing on the screen. When the indicator 6071 is selected, the device 6010 can display a document edited by the second device 112 on a screen as a pop-up window separate from the calendar 6011. [

Similarly, the job history information 6052 of the document can also be displayed with an indicator 6062 and an indicator 6072 that can output a document to the screen of the device 6010. [ 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 popup window separate from the calendar 6011, 113 can output the document before editing on the screen. When the indicator 6072 is selected, the device 6010 can output a document edited by the third device 113 to the screen as a pop-up window separate from the calendar 6011. [

61 is a diagram showing another example of the monthly calendar displayed on the screen of the 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. Accordingly, the above-described contents with reference to FIG. 19 for the objects that can be displayed on the calendar 6111 can be similarly applied to FIG.

The calendar 6111 may display an indicator 6130 and an indicator 6140 indicating the name of the device. For example, if the second device 112 edits the document at 2014.05.14, an indicator 6130 indicating 'second device' may be displayed in the area corresponding to 2014.05.14 of the calendar 6111 have. Likewise, if the third device 113 edits the document at 2014.05.14, an indicator 6140 indicating 'third device' may be displayed in the area corresponding to 2014.05.14 in the calendar 6111. [

The device 6110 may select the indicator 6130 indicating 'second device' according to the user input received through the user input unit 16510. [ When the indicator 6130 indicating 'second device' is selected, the device 6110 can output the job history information 6151 of the document to the screen. For example, if the second device 112 stores a document named 'abc.doc' with a size of 1084 kilobytes using the first program at 09:11:43 PM on May 14, 2014 Assume that "abc.doc, text, first program, second device, May 14, 2014 09:11:43 PM, 1084 KB" may be output in the job history information 6151. On the other hand, the device 6110 can output the job history information 6151 of the document as a separate pop-up window on the screen.

Similarly, the device 6110 may select an indicator 6140 indicating 'third device' according to the user input received via the user input unit 16510. When the indicator 6140 indicating 'third device' is selected, the device 6110 can output the job history information 6152 of the document to the screen. For example, if the third device 113 stores a document named 'xyz.doc' with a size of 2387 kilobytes using the first program at 09:14:03 am on May 14, 2014 Assume that the job history information 6152 includes' xyz.doc ', text, first program, third device, May 14, 2014 at 09:14:03 and 2387 KB'. On the other hand, the device 6110 can output the job history information 6152 of the document as a separate pop-up window on the screen.

Further, in the job history information 6151 of the document, an indicator 6161 and an indicator 6171 capable of outputting the document to the screen of the device 6110 can be displayed. 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 popup window separate from the calendar 6120, 112 can output the document before editing on the screen. Also, when the indicator 6171 is selected, the device 6110 can output a document edited by the second device 112 to a screen as a pop-up window separate from the calendar 6111. [

Similarly, the job history information 6152 of the document can also be provided with an indicator 6162 and an indicator 6172 capable of outputting the document to the screen of the device 6110. [ 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 popup window separate from the calendar 6111, 113 can output the document before editing on the screen. When the indicator 6172 is selected, the device 6110 can output a document edited by the third device 113 as a pop-up window separate from the calendar 6111 on the screen.

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

62, on the screen of the device 6210, an annual calendar 6211 is output. Indicators 6220, 6230, 6240, 6250, and 6260 indicating the name of the document may be displayed in the calendar 6211. [ For example, if the third device 113 edits a document named 'xyz.doc' in 2014.05.12, an indicator ('xyz.doc') indicating 'xyz.doc' in the area corresponding to 2014.05 in the calendar 6211 6250) may be displayed. Assuming that the second device 112 has edited a document named 'abc.doc' on 2014.05.14, an indicator 6260 indicating 'abc.doc' in the area corresponding to 2014.05 in the calendar 6211, May be displayed.

The device 6210 may select the indicators 6220, 6230, 6240, 6250, 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 can output the job history information 6270 and 6280 of the document to the screen. For example, if the third device 113 edited a document titled 'xyz.doc' with a size of 2387 kilobytes by using the first program at 09:14:03 am on May 12, 2014 I suppose. At this time, if the indicator 6250 indicating 'xyz.doc' is selected, 'xyz.doc', text, first program, third device, 09:14:14 am on May 12, 03, 2378 KB 'can be output. Also, for example, if the second device 112 uses the first program to send a document named 'abc.doc' with a size of 1084 kilobytes (KB) to the server on May 14, 2014 at 09:11:43 PM Is edited. At this time, if the indicator 6260 indicating 'abc.doc' is selected, 'abc.doc', text, first program, second device, 09:11:14 PM on May 14, 43, 1084 KB 'can be output. On the other hand, the device 6210 can output the job history information 6270 and 6280 of the document as separate pop-up windows on the screen.

Indicators 6271, 6272, 6281, and 6282 capable of 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 that can output the original document of 'abc.doc' to the screen of the device. The indicator 6281 may be an indicator that can output the original document of 'xyz.doc' to the screen of the device. The indicator 6272 may be an indicator that can output the edited document 'abc.doc' on the screen of the device. The indicator 6282 may be an indicator that can output the edited document of 'xyz.doc' to 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 popup window separate from the calendar 6211 The second device 112 can output a document edited by the second device 112 to the screen.

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

63, on the screen of the device 6310, an annual calendar 6311 is outputted. In the calendar 6311, indicators 6320, 6330, 6340, 6350, and 6360 indicating a program used for document work are displayed. As described above with reference to Figs. 57 and 60, when the indicators 6350 and 6360 indicating the programs used for the document operation are selected, the device 6310 displays the job history information 6370 and 6380 of the document on the screen Can be output. When the directors 6471, 6472, 6481, and 6482 capable of outputting a document are selected on the screen displaying the job history information 6370 and 6380 of the document, the document represented by the directive can be output to the screen. For example, if the indicator 6472 is selected, the device 6310 may output a document edited by the second device 112 to 'abc.doc' on the screen.

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

Referring to Fig. 64, an annual calendar 6411 is output on the screen of the device 6410. Fig. Indicators 6420, 6430, 6440, 6450, and 6460 indicating the device 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 can output the execution history information 6480 of the document to the screen. 64, when the directors 6471, 6472, 6481, and 6482 capable of outputting a document are selected on the screen displaying the execution history information 6470 and 6480 of the document, Can output the document generated by the first device 111 to the screen.

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

65, on the screen of the device 6510, an annual calendar 6511 is outputted. The annual calendar shown in FIG. 62 to FIG. 64 includes an area displaying the months included in one year, but the yearly calendar 6511 shown in FIG. 65 includes an area showing the days included in the year have. In other words, the device 6510 can change the format of the annual calendar and output it to the screen.

In the calendar 6511, indicators 6520 to 6525 may be displayed on the date when the operation of the document is performed. For example, if the second device 112 edits a document titled 'abc.doc' on 2014.05.14, the calendar 6511 indicates 'abc.doc' in the area corresponding to 2014.05.14. An indicator 6520 may be displayed. Assuming that the third device 113 has edited a document named 'xyz.doc' on 2014.05.14, the indicator 6520 may also be displayed as an indicator 6520 indicating the editing of 'xyz.doc' have.

As described above with reference to Fig. 62, when the indicator 6520 displayed on the calendar 6511 is selected, the device 6510 can output the job history information 6530 of the document to 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' . ≪ / RTI > Also, when the directors 6531, 6532, 6534, and 6535 capable of outputting a document are selected on the screen displaying the job history information 6530 of the document, the device 6510 can output the document to the screen.

66A to 66C are flowcharts showing another example in which a server associates work history information with a user's calendar in a case where a first device according to some embodiments generates a document and a second device views and edits a document. to be.

S6610 to S6629 in Figs. 66A to 66B are the same as S3210 to S3229 in Figs. 32A to 32B for the processes in which the server 100 links the job history information to the user's calendar in browsing a document. Therefore, a detailed description of S6610 to S6629 in Figs. 66A to 66B will be omitted below.

After the interlocking of the document viewing and the operation history information is completed, the second device 112 requests the server 100 to transmit the document in step S6630. In S6631, the server 100 transmits the document to the second device 112. [

S6632 to S6643 in Figs. 66B to 66C are the same as S4817 to S4828 in Figs. 48A to 48B for the processes in which the server 100 links the job history information to the user's calendar in editing a document. Therefore, a detailed description of S6632 to S6643 in Figs. 66B to 66C will be omitted below.

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

67 to 68 are diagrams showing 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. In other words, the job history information 1310 of the document shown in FIG. 13 means the job history information 1310 generated as the device generates the document. On the other hand, the job history information 6710 of the document shown in Fig. 67 indicates that the new job history information 6720, 6730, 6740 is generated as the device generates the document and at least one of the devices reads and edits the created document Means added.

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. In other words, the job history information 1410 of the document shown in Fig. 14 means the job history information 1410 generated as the device generates the document. On the other hand, the job history information 6810 of the document shown in FIG. 68 indicates that the new job history information 6820, 6830, and 6840 is generated as the device generates the document and at least one of the devices reads and edits the created document Means added.

68, the server 100 may arrange the job 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. FIG. In the calendar 6911, an indicator 6920 indicating the name of the document may be displayed. For example, if the first device 111 has generated a document named 'abc.doc' in 2014.05.12, the calendar 6911 indicates 'abc.doc' in the area corresponding to 2014.05.12. An indicator 6920 may be displayed.

The device 6910 may select an indicator 6920 indicating 'abc.doc' according to the user input received via the user input unit 16510. When the indicator 6920 indicating 'abc.doc' is selected, the device 6910 can output the job history information 6921 of the document to the screen. For example, if the first device 111 stores a document named 'abc.doc' with a size of 54 KB (kilobytes) at 12:28:04 pm on May 12, 2014 using the first program Assuming that the job history information 3821 includes 'abc.doc, text, first program, first device, May 12, 2014 12:28:04 PM, 54 KB' may be output. On the other hand, the device 6910 can output the job history information 3821 of the document as a separate popup window on the screen.

In the job history information 6921 of the document, an indicator 6922 capable of outputting the document to the screen of the device 6910 may be displayed. 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 popup window as a separate window from the calendar 6911 111) can output the generated document to the screen.

Similarly, in one calendar 6911, a plurality of directives indicating the name of the document can be displayed. For example, if the second device 112 has read a document named 'abc.doc' on 2014.05.20, the calendar 6911 indicates 'abc.doc' in the area corresponding to 2014.05.12 An indicator 6930 may be displayed.

Device 6910 may select an indicator 6930 indicating 'abc.doc' according to user input received via user input 16510. When the indicator 6930 indicating 'abc.doc' is selected, the device 6910 can output the job history information 6931 of the document to the screen. For example, if the second device 112 reads a document named 'abc.doc' with a size of 54 kilobytes using the first program at 20:46:11 PM on May 20, 2014 Assume that "abc.doc, text, first program, second device, May 20, 2014 at 08:46:11, 54 KB" may be output in the job history information 3831. On the other hand, the device 6910 can output the job history information 6931 of the document as a separate popup window on the screen.

In the job history information 6931 of the document, indicators 6932 and 6933 capable of outputting the document to the screen of the device 6910 may be displayed. The indicator 6932 may be an original document at the time of document creation or an indicator indicating a document before the current operation, and the indicator 6933 may be an indicator indicating the current editing document.

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

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

Referring to FIG. 70, a daily calendar 7011 is output on the screen of the device 7010. FIG. The calendar 7011 shown in Fig. 70 has the same frame as the calendar 6911 shown in Fig. Therefore, the above-described contents with reference to FIG. 69 for the objects that can be displayed on the calendar 3911 can be similarly applied to FIG.

In the calendar 7011, an indicator 7020 indicating a program used for document work can be displayed. For example, if the first device 111 generates a document using the first program on May 1, 2014, the region corresponding to 2014.05.12 of the calendar 7011 has an indicator (" first program " 7020 may be displayed.

The device 7010 may select an indicator 7020 indicating 'first program' according to the user input received via the user input unit 16510. When the indicator 7020 indicating 'first program' is selected, the device 7010 can output the job history information 7021 of the document to the screen. For example, if the first device 111 has created a document named 'abc.doc' with a size of 54 KB (kilobytes) at 12:28:04 pm on May 12, 2014 using the first program Assume that "abc.doc, text, first program, first device, May 12, 2014 12:28:04 PM, 54 KB" may be output to the job history information 7021. On the other hand, the device 7010 can output the job history information 7021 of the document as a separate pop-up window on the screen.

In the job history information 7021 of the document, an indicator 7022 capable of outputting the document to the screen of the device 7010 may be displayed. 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 popup window, which is separate from the calendar 7011, 111) can output the generated document to the screen.

Similarly, in one calendar 7011, a plurality of directives indicating a program can be displayed. For example, if the second device 112 reads a document named 'abc.doc' on 2014.05.20, the calendar 7011 displays 'first program' in the area corresponding to 2014.05.12. An indicator 7030 may be displayed.

The device 7010 may select an indicator 7030 indicating 'first program' in accordance with the user input received via the user input section 16510. When the indicator 7030 indicating 'first program' is selected, the device 7010 can output the job history information 7031 of the document to the screen. For example, if the second device 112 reads a document named 'abc.doc' with a size of 54 kilobytes using the first program at 20:46:11 PM on May 20, 2014 Assume that "abc.doc, text, first program, second device, May 20, 2014 at 08:46:11, 54 KB" may be output to the job history information 7031. On the other hand, the device 7010 can output the job history information 7031 of the document as a separate popup window on the screen.

In the job history information 7031 of the document, indicators 7032 and 7033 capable of outputting the document to the screen of the device 7010 may be displayed. The indicator 7032 may be an original document at the time of document creation or an indicator indicating a document before the current operation, and the indicator 7033 may be an indicator indicating the current editing document.

The indicator 7033 indicating the editing document can be displayed differently from the original document or the indicator 7032 indicating the document before the current operation. For example, in the case of the indicator 7033 of the editing document, a border line may be additionally displayed in the indicator 7032 indicating the original document or the document before the current operation. When the indicator 7032 or 7033 capable of outputting a document according to the user input received through the user input unit 16510 is selected, the device 7010 displays a popup window separate from the calendar 7011, The edited document can be displayed on the screen.

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

Referring to Fig. 71, a daily calendar 7111 is output on the screen of the device 7110. Fig. The calendar 7111 shown in Fig. 71 has the same frame as the calendar 6911 shown in Fig. Therefore, the above description with reference to FIG. 69 for the indicators that can be displayed on the calendar 7111 can be similarly applied to FIG.

In the calendar 7111, an indicator 7120 indicating the name of the device can be displayed. For example, if the first device 111 generates a document at 2014.05.12, an indicator 7120 indicating 'first device' may be displayed in an area corresponding to 2014.05.12 of the calendar 7111 have.

The device 7110 may select an indicator 7120 indicating 'first device' according to the user input received through the user input unit 16510. When the indicator 7120 indicating 'first device' is selected, the device 7110 can output the job history information 7121 of the document to the screen. For example, if the first device 111 stores a document named 'abc.doc' with a size of 54 KB (kilobytes) at 12:28:04 pm on May 12, 2014 using the first program Assuming that the job history information 7121 includes "abc.doc, text, first program, first device, May 12, 2014 12:28:04 PM, 54 KB" may be output. On the other hand, the device 7010 can output the job history information 7121 of the document as a separate pop-up window on the screen.

Indicators 7122 and 7123 capable of 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 original document at the time of document creation or an indicator indicating a document prior to the current job, and the indicator 7123 may be an indicator indicating the current edited document.

The indicator 7123 indicating the editing document can be displayed differently from the original document or the indicator 7122 indicating the document before the current operation. For example, in the case of the indicator 7123 of the editing document, a border line may be additionally displayed in the indicator 7122 indicating the original document or the document before the current operation. When an indicator 7122 or 7123 capable of outputting a document according to a user input received through the user input unit 16510 is selected, the device 7110 displays a popup window separate from the calendar 7111, Can be displayed on the screen.

Similarly, in one calendar 7111, a plurality of directors indicating the name of the device can be displayed. For example, if the second device 112 reads a document named 'abc.doc' on 2014.05.20, the calendar 7111 displays 'second device' in the area corresponding to 2014.05.12. An indicator 7130 may be displayed.

The device 7110 may select the indicator 7130 indicating 'second device' according to the user input received through the user input unit 16510. When the indicator 7130 indicating 'second device' is selected, the device 7110 can output the job history information 7131 of the document to the screen. For example, if the second device 112 reads a document named 'abc.doc' with a size of 54 kilobytes using the first program at 20:46:11 PM on May 20, 2014 Assume that "abc.doc, text, first program, second device, May 20, 2014 at 08:46:11, 54 KB" may be output in the job history information 7131. On the other hand, the device 7110 can output the job history information 7131 of the document as a separate pop-up window on the screen.

Further, in the job history information 7131 of the document, indicators 7132 and 7133 capable of outputting the document to the screen of the device 7110 may be displayed. The indicator 7132 may be an original document at the time of document creation or an indicator indicating a document before the current operation, and the indicator 7133 may be an indicator indicating the current editing document.

The indicator 7133 indicating the editing document can be displayed differently from the original document or the indicator 7132 indicating the document before the current operation. For example, in the case of the indicator 7133 of the editing document, a border line may be additionally displayed in the indicator 7132 indicating the original document or the document before the current operation. When an indicator 7132 or 7133 capable of outputting a document according to a user input received through the user input unit 16510 is selected, the device 7110 displays a popup window separate from the calendar 7111, Can be displayed 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. Fig. The calendar 7211 shown in FIG. 72 has the same frame as the calendar 1920 shown in FIG. Therefore, the above description with reference to FIG. 19 for the indicators that can be displayed on the calendar 7211 can be similarly applied to FIG.

In the calendar 7211, an indicator 7230 indicating the name of the document may be displayed. For example, assuming that the first device 111 has generated a document named 'abc.doc' in 2014.05.12, the calendar 7211 indicates 'abc.doc' in the area corresponding to 2014.05.12 An indicator 7230 may be displayed. Likewise, if the second device 112 reads a document named 'abc.doc' on 2014.05.20, an indicator (abc.doc) indicating 'abc.doc' in the area corresponding to 2014.05.20 in the calendar 7211 7240 may be displayed.

Device 7210 may select an indicator 7230 indicating 'abc.doc' according to user input received via user input 16510. When the indicator 7230 indicating 'abc.doc' is selected, the device 7210 can output the job history information 7251 of the document to the screen.

For example, if the first device 111 stores a document named 'abc.doc' with a size of 54 KB (kilobytes) at 12:28:04 pm on May 12, 2014 using the first program Assuming that the job history information 7251 includes "abc.doc, text, first program, first device, May 12, 2014 12:28:04 PM, 54 KB" may be output. On the other hand, the device 7210 can output the job history information 7251 of the document as a separate popup window on the screen.

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

For example, if the second device 112 reads a document named 'abc.doc' with a size of 54 kilobytes using the first program at 20:46:11 PM on May 20, 2014 Assume that the job history information 7252 includes' abc.doc ', text, first program, second device, May 20, 2014 at 08:46:11, 54 KB'. On the other hand, the device 7210 can output the job history information 7252 of the document as a separate popup window on the screen.

In the document job history information 7251, an indicator 7261 capable of outputting a document to the screen of the device 7210 may be displayed. 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 popup window separate from the calendar 7211, 111) can output the generated document to the screen.

Similarly, in the job history information 7252 of the document, an indicator 7262 and an indicator 7272 capable of outputting a document to the screen of the device 7210 may be displayed. 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 popup window separate from the calendar 7211 You can print on the screen. Also, when the indicator 7272 is selected, the device 7210 can output a document edited in a pop-up window separate from the calendar 7211 on the screen.

73 is a view showing another example of the monthly calendar displayed on the screen of the device according to some embodiments.

Referring to Fig. 73, monthly calendar 7311 is output on the screen of device 7310. Fig. The calendar 7311 shown in Fig. 73 has the same frame as the calendar 1920 shown in Fig. Therefore, the above-described contents with reference to FIG. 19 for the objects that can be displayed on the calendar 7311 can be similarly applied to FIG.

In the calendar 7311, an indicator 7330 and an indicator 7340 indicating a program used for document work can be displayed. For example, assuming that the first device 7310 has generated a document using the first program at 2014.05.12, an area (corresponding to 2014.05.12) of the calendar 7320 indicates an indicator 7330) may be displayed. Similarly, if it is assumed that the second device 112 browsed the document using the first program on 2014.05.20, an indicator 7340 indicating 'first program' is displayed in the area corresponding to 2014.05.20 on the calendar 7311, May be displayed.

The device 7310 may select an indicator 7330 indicative of a 'first program' according to the user input received via the user input unit 16510. When the indicator 7330 indicating 'first program' is selected, the device 7310 can output the job history information 7351 of the document to the screen. For example, if the first device 111 stores a document named 'abc.doc' with a size of 54 KB (kilobytes) at 12:28:04 pm on May 12, 2014 using the first program Assume that "abc.doc, text, first program, first device, May 12, 2014 12:28:04 PM, 54 KB" may be output to the job history information 7351. On the other hand, the device 7310 can output the job history information 7351 of the document as a separate popup window on the screen.

Similarly, the device 7310 may select an indicator 7340 indicative of a 'first program' according to the user input received via the user input 16510. When the indicator 7340 indicating 'first program' is selected, the device 7310 can output the job history information 7352 of the document to the screen. For example, if the second device 112 reads a document named 'abc.doc' with a size of 54 kilobytes using the first program at 20:46:11 PM on May 20, 2014 Assume that 'abc.doc', text, first program, second device, May 20, 2014 at 08:46:11, 54 KB 'may be output in the job history information 7352. On the other hand, the device 7310 can output the job history information 7352 of the document as a separate popup window on the screen.

Further, in the job history information 7351 of the document, an indicator 7361 capable of outputting the document to the screen of the device 7310 may be displayed. 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 popup window separate from the calendar 7320, 111) can output the generated document to the screen.

Similarly, the job history information 7352 of the document can also be provided with an indicator 7362 and an indicator 7372 capable of outputting the document to the screen of the device 7310. [ 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 popup window separate from the calendar 7311 You can print on the screen. When the indicator 7372 is selected, the device 7310 can output a document edited in a pop-up window separate from the calendar 7311 on the screen.

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

Referring to Fig. 74, monthly calendar 7411 is output on the screen of device 7410. Fig. The calendar 7411 shown in Fig. 74 has the same frame as the calendar 1910 shown in Fig. Therefore, the above-described contents with reference to FIG. 19 for the objects that can be displayed on the calendar 7411 can be similarly applied to FIG.

In the calendar 7411, an indicator 7430 indicating the name of the device and an indicator 7440 may be displayed. For example, if the first device 111 generates a document at 2014.05.12, an indicator 7430 indicating 'first device' may be displayed in an area corresponding to 2014.05.12 of the calendar 7411 have. Likewise, assuming that the second device 112 browses the document on 2014.05.20, an indicator 7440 indicating 'second device' may be displayed in the area corresponding to 2014.05.20 on the calendar 7411.

The device 7410 may select an indicator 7430 indicating 'first device' according to the user input received via the user input 16510. When the indicator 7430 indicating 'first device' is selected, the device 7410 can output the job history information 7451 of the document to the screen. For example, if the first device 111 stores a document named 'abc.doc' with a size of 54 KB (kilobytes) at 12:28:04 pm on May 12, 2014 using the first program Assuming that the job history information 7451 includes "abc.doc, text, first program, first device, May 12, 2014 12:28:04 PM, 54 KB" may be output. On the other hand, the device 7410 can output the job history information 7451 of the document as a separate popup window on the screen.

Similarly, the device 7410 may select an indicator 7440 indicating a 'second device' according to user input received via the user input 16510. When the indicator 7440 indicating 'second device' is selected, the device 7410 can output the job history information 7452 of the document to the screen. For example, if the second device 112 reads a document named 'abc.doc' with a size of 54 kilobytes using the first program at 20:46:11 PM on May 20, 2014 Assume that the job history information 7452 includes' abc.doc ', text, first program, second device, May 20, 2014 at 08:46:11, 54 KB'. On the other hand, the device 7410 can output the job history information 7452 of the document as a separate popup window on the screen.

Further, in the job history information 7451 of the document, an indicator 7461 capable of outputting the document to the screen of the device 7410 may be displayed. For example, if an indicator 7461 capable of outputting a document according to a user input received via the user input unit 16510 is selected, the device 7410 may display a popup window separate from the calendar 7420, 111) can output the generated document to the screen.

Similarly, the job history information 7452 of the document can also be displayed with an indicator 7462 and an indicator 7472 capable of outputting the document to the screen of the device 7410. [ 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 a document of the original in a pop-up window separate from the calendar 7411 You can print on the screen. Further, when the indicator 7472 is selected, the device 7410 can output a document edited 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.

In the calendar 7520, an indicator 7530 indicating the name of the document may be displayed. For example, if the first device 111 has generated a document named 'abc.doc' at 2014.05.12 and the second device 112 generated a document named 'abc.doc' at 2014.05.14 , And if the second device 112 reads the same document on 2014.05.20, an indicator 7530 indicating 'abc.doc' may be displayed in the area corresponding to 2014.05 in the calendar 7520. The indicator 7530 may include the number of job history information of the document. For example, when the generation and the browsing of the 'abc.doc' by the first device 111 and the second device 112 are performed three times in May as in the above-described example, the indicator 7530 indicates the document name 'abc.doc' together with the number of job history information '(3)' may be displayed together.

The device 7510 may select an indicator 7530 indicating the name of the document according to the user input received via the user input section 16510. [ When the indicator 7530 indicating the name of the document is selected, the device 7510 can output the job history information 7540 of the document to the screen.

For example, the first device 111 stores a document named 'abc.doc' with a size of 54 KB (kilobytes) at 12:28:04 pm on May 12, 2014 using the first program , The second device 112 generates a document named 'abc.doc' having a size of 105 KB at 09:11:43 am on May 1, 2014 using the first program, and the second device 112 generates a document named 'abc.doc' .20 It is assumed that the same document is read at 08:46:11.

When the indicator 7530 indicating 'abc.doc' is selected, the job history information 7540 includes first job history information 7543, second job history information 7544, and third job history information 7545, . ≪ / RTI > 'Abc.doc, text, first program' may be displayed in the job history information 7540.

In addition, 'first device, document generation, 12:28:04 PM, May 12, 2014, 54 KB' may be output in the first job history information 7543. In addition, the second job history information 7544 may output 'second device, document generation, May 14, 2014, 09:11:43, 105KB', and the third job history information 7545 may include ' Second device, document viewing, May 20, 2014 at 08:46:11, 105KB 'may be output. On the other hand, the device 7510 can output the job history information 7540 of the document as a separate popup window on the screen.

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

For example, if an indicator 7541 is selected that can output a document according to a user input received through the user input unit 16510, the device 7510 may display a popup window separate from the calendar 7520, 111) can output the generated document to the screen.

76 is a view showing another example of the annual calendar displayed on the screen of the device according to some embodiments.

Referring to FIG. 76, an annual calendar 7620 is output on the screen of the device 7610. In the calendar 7620, an indicator 7630 indicating a program used for document work is displayed. As described above with reference to FIG. 75, the number of job history information 7640 may be displayed together with the indicator 7630. As described above with reference to Fig. 75, when the indicator 7630 indicating the program used for document operation is selected, the device 7610 can output the job history information 7650 of the document to the screen. When the directories 7651 and 7652 capable of outputting a document are selected on the screen displaying the job history information 7650 of the document, the device 7610 outputs the document represented by the directives 7651 and 7652 to the screen .

77 is a view showing another example of the annual calendar displayed on the screen of the device according to some embodiments.

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

As described above with reference to Fig. 75, when the indicator 7730 indicating the device is selected, the device 7710 can output the execution history information 7750 of the document to the screen. For example, the second device 112 may generate a document named 'abc.doc' with a size of 105 KB at 09:11:43 am on May 1, 2014, using the first program, It is assumed that the same document is read at 2014.05.20.208:46:11.

The job history information 7750 may include first job history information 7760 and second job history information 7770. "Abc.doc, text, first program, document creation, May 14, 2014 at 09:11:43, 105KB" may be output in the first job history information 7760, and the second job history information 7770), 'abc.doc, text, first program, document viewing, May 20, 2014 08:46:11, 105KB' may be output. On the other hand, the device 7710 can output the job history information 7750 of the document as a separate popup window on the screen.

When the directors 7761, 7761, 7771, 7772 capable of outputting a document are selected on the screen in which the execution history information 7750 of the document is displayed, as described above with reference to Fig. 62, The document can be displayed on the screen.

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

Referring to Fig. 78, an annual calendar 7820 is output on the screen of the device 7810. Fig. The annual calendar shown in FIG. 75 to FIG. 77 includes an area in which the months included in the year are displayed. However, the yearly calendar 7820 shown in FIG. 78 includes the area 7821 showing the days included in the year, . In other words, the device 7810 can change the format of the annual calendar and output it to the screen.

In the calendar 7820, indicators 7830, 7840, and 7850 may be displayed on the date when the job of the document was performed. For example, assuming that the third device 113 has generated a document named 'xyz.doc' in 2014.02.14, the calendar 7820 indicates 'xyz.doc' in the region corresponding to 2014.02.14 An indicator 7830 may be displayed.

Assuming that the third device 113 has generated a document with the name "abc.doc" at 2014.05.12, an indicator (abc.doc) indicating "abc.doc" is displayed in the area corresponding to 2014.05.12 in the calendar 7820 7840 may be displayed.

Assuming that the third device 113 has generated a document named 'kkk.ppt' on 2014.05.28, an indicator ('kkk.ppt') indicating 'kkk.ppt' is displayed in the area corresponding to 2014.05.28 on the calendar 7820 7850) may be displayed.

The directors 7830, 7840 and 7850 may have different colors, shapes, etc. in order to distinguish the directives 7830, 7840 and 7850 about the different files from each other. Although it has been described in the foregoing that 'xyz.doc', 'abc.doc', and 'kkk.ppt' are all generated by the third device 113, different devices may generate documents.

As described above with reference to Fig. 75, when the indicators 7830, 7840, 7850 displayed on the calendar 7820 are selected, the device 7810 outputs the job history information 7860, 7870, 7880 of the document to the screen . When the directors 7861, 7871, and 7881 capable of outputting a document are selected on the screen displaying the job history information 7860, 7870, and 7880 of the document, the device 7810, Can output the document to the screen.

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

79, an example of the calendar 7920 output on the screen of the device 7910 is shown. 79, the monthly calendar 7920 is displayed 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 has been performed may be displayed on the calendar 7920. [ For example, suppose at least one of the devices 110 has performed an operation on a total of nine documents in 2014.01.10, then in calendar 7920 an operation is performed on nine documents in the area representing 2014.01.10 An indicator 7930 indicating that the operation has been performed may be displayed.

The device 7910 may select an indicator 7930 indicating the number of documents that have been performed in accordance with the user input received via the user input 16510. If the indicator 7930 indicating the number of documents on which the job has been performed is selected, the device 7910 can output a list 7940 of documents on which the job has been performed.

When one of the documents 7941 included in the list 7940 is selected after the list 7940 of the documents on which the job has been performed, the device 7910 displays the job history information 7950 of the selected document You can print on the screen. In the job history information 7950 of the document, indicators 7951 and 7952 capable of outputting the document to the screen of the device 7910 may be displayed. Here, the indicator 7951 may be an original document at the time of document creation or an indicator indicating a document before the current operation, and the indicator 7952 may be an indicator indicating the current editing document.

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

81 to 82 are diagrams showing still other examples of calendars output on the screen of the device according to some embodiments.

81, an example of the calendar 8120 output on the screen of the device 8110 is shown. 81, the monthly calendar 8120 is displayed on the screen of the device 8110 for convenience of explanation, but the present invention is not limited to this.

If the same device performs an operation on a plurality of documents on the same date, the calendar 8120 may be displayed with an indicator 8030 indicating the number of documents on which the operation has been performed. For example, assuming that the first device 111 has performed operations on a total of three documents at 2014.01.11, an operation is performed on three documents in the area representing 2014.01.11 in the calendar 8120 And an indicator 8130 indicating that it is displayed may be displayed.

The device 8110 may select the indicator 8130 according to the user input received via the user input section 16510. [ When the indicator 8130 is selected, the device 8110 can output a list 8140 of documents on which the job has been performed, on the screen.

When one of the documents 8141 included in the list 8140 is selected after the list of the documents 8140 on which the job has been performed, the device 8110 displays the job history information 8150 of the selected document You can print on the screen. Indicators 8151 and 8152 capable of outputting a document to the screen of the device 8110 may be displayed in the job history information 8150 of the document. Here, the indicator 8151 may be an original document at the time of document creation or an indicator indicating a document before the current operation, and the indicator 8152 may be an indicator indicating the current editing document.

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

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

Referring to Figure 83 (a), an example of the first mode calendar 8320 output on the screen of the device 8310 is shown. Here, the first mode calendar 8320 can be interlocked with information related to the daily life of the user. For example, the first mode calendar 8320 may be interlocked with information about a schedule or schedule of the user. In addition, the first mode calendar 8320 may be associated with history information that the user has used the function of the device 8310. [ For example, the first mode calendar 8320 may include a history of the user making a call using the device 8310, a history of shooting using the camera provided in the device 8310, a memo program installed in the device 8310, A history of generating a memo using the device 8310, a history of sending or receiving a message or an e-mail using the device 8310, a history using the SNS service using the SNS program installed in the device 8310, or the like.

Referring to Figure 83 (b), an example of the second mode calendar 8330 output on the screen of the device 8310 is shown. Here, the second mode calendar 8330 can be interlocked with the job history information of the document.

The calenders 8320 and 8330 output to the device 8310 may be displayed with indicators 8340 and 8350 capable of switching modes of the calendars 8320 and 8330. [ For example, on the screen of the device 8310, an indicator 8340 requesting to output the first mode calendar 8320 and an indicator 8350 requesting to output the second mode calendar 8330 may be displayed have.

The first mode calendar 8320 output to the device 8310 may also display schedule information related to the job history information displayed on the second mode calendar 8330. [ For example, assume that a user has worked on the "2013 Performance Reporting .doc" document on December 23, 2013, and that there is a meeting date associated with the "2013 Performance Reporting .doc" document on January 3, 2014 do. At this time, an indicator informing to review '2013 annual report .doc' may be displayed in the January 2, 2014 field on the first mode calendar 8320.

According to the above description, since the job history information of the document can be linked to the user's calendar, the user can intuitively grasp the job history of the document. Further, the document can be displayed on the screen of the device through an indicator (e.g., an icon) displayed on the calendar, so that the user can easily view or edit the document.

Further, it is possible to switch between a calendar displaying the user's personal schedule and the like and a calendar displaying the user's document working history, thereby enhancing the user's convenience.

84 to 86, when the users of the devices 110 are different from each other and the devices 110 perform document operations, the server 100 transmits the operation history information to the user's calendar An example of interworking is explained.

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

84, the system 1 includes a server 100 and devices 110. [ Here, each of the devices 110 means a device of another user. 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, the Nth device 114 is the device of the M user 122 Device.

At least one of the devices 110 performs a document operation 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 perform document work and transmit 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 a 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 as an indicator to be displayed on the calendar or an indicator to be displayed on the calendar is selected.

At this time, the server 100 may transmit the information 140 to be displayed on the calendar only to the device 110 that requested the transfer of the information 140 to be displayed on the calendar. For example, the first device 111 executes a program for outputting a calendar, authenticates the first user based on the user account entered through the user input unit 16510, And may request the transmission of information 140 to be displayed on the calendar.

On the other hand, the server 100 may automatically transmit (e. G., Push) the information 140 to be displayed on the calendar to the first device 111, even if there is no request from the first device 111 . For example, if there is a history that the first device 111 has previously requested transmission of the information 140 to be displayed on the calendar of the first user, then the server 100 may subsequently request a request from the first device 111 The information 140 to be displayed on the calendar of the first user can be automatically transmitted.

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

85 is a flowchart showing an example in which a server according to some embodiments links work history information to a calendar of a user.

In S8510, the server 100 receives job history information of a document processed by a plurality of users from devices of a plurality of users. In other words, each of the devices of at least two users performs a document operation and transmits job history information to the server 100, respectively. At this time, the devices can transmit only a part of the job history information to the server 100 as described above with reference to FIG.

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

86, when the first device 111 of the first user 120 and the second device 112 of the second user 121 work documents, the server 100 determines whether the first user 111 An example in which the job history information is linked to the calendar of FIG.

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

In FIG. 86, the first device 111 and the second device 112 are shown as working documents for convenience of explanation, but the present invention is not limited thereto. In other words, there is no limit to the number of devices that work with documents. Assuming that there is only one device to work with the document, the operation of the second device 112, which will be described below, can be all performed in the first device 111. [ Assuming that the number of devices working on the 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 .

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

Assuming that the document to be processed by the first device 111 is 'abc.doc' and that the program used for creating, viewing or editing 'abc.doc' is the first program, the first device 111 You can run the first program and create, view or edit 'abc.doc'.

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

At S8612, the second device 112 works on the document. For example, the first device 111 can execute a program used for document operation, and can work on the document using the program. Assuming that the document to be processed by the second device 112 is 'abcd.xls' and that the program used for creating, viewing or editing 'abcd.xls' is a second program, the second device 112 You can run the second program and create, view or edit 'abcd.xls'.

In step S8613, the second device 112 transmits the job history information of the document to the server 100. [ For example, the second device 112 can transmit the job history information of the document to the server 100 at the time when the execution of the program used for the document job is ended 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 terminating the execution of the second program

In S8615, the server 100 links the job history information to the user's calendar by using the time information included in the job history information received from the first device and the second device. For example, if the first device 111 stores 'abc.doc' at 08:01:42 AM on May 17, 2018, and the second device 112 stores 'abcd.xls' : 00, the server 100 may generate a first indicator to be displayed in an area corresponding to 2014.05.18 on a 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 displayed on the screen of the device, by selecting an indicator to be displayed on the calendar or an indicator to be displayed on the calendar. For example, the first device 111 may request transmission of job history information to be output to the screen of the device as the first indicator, the second indicator, and the first and second indicators are selected.

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

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

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 the job history information to be displayed on the screen of the device as the indicator to be displayed on the calendar or the indicator displayed on the calendar is selected. For example, the second device 112 may request transmission of job history information to be output to the screen of the device as the first indicator, the second indicator, and the first and second indicators are selected.

In S8620, the server 100 transmits the 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 on which the first indicator and the second indicator transmitted from the server 100 are displayed.

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

87 is a diagram for explaining an example in which, when devices according to some embodiments perform co-authoring of a document, the server cooperates with the user's calendar with job history information.

87, 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 the 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 (e.g., the first user 120). That is, the number of users of devices 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. [ Also, the second device 112 generates a second document 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, . 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 N-th device 114 can perform cooperation authoring of documents by transmitting the generated information 8730 to the server 100. [

The co-authoring of a document means that several devices 110 jointly generate a single document 8701. [ In other words, the co-authoring of the document means that the contents to be included in the single document 8701 are generated by the plurality of devices 110. [

For example, when the co-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, May be content contained in a second document generated by the second device 112. [

The server 100 combines 8710 the first to Nth documents received from the devices 110 and generates 8720 a single document 8701 that is the result of the co-authoring. Therefore, the contents of the first document, the contents of the second document, and the contents of the Nth document can all be included in the contents of the single document 8701. [

The server 100 may transmit the generation history information of the single document 8701 to each of the devices 110 participating in the co-authoring of the single document 8701 when the single document 8701 is generated. 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 a 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 as an indicator to be displayed on the calendar or an indicator to be displayed on the calendar is selected. Here, the job history information may include the generation history information of the single document 8701. [

At this time, the server 100 may transmit the information 8740 to be displayed on the calendar only to the device 110 that requests the transmission of the information 8740 to be displayed on the calendar. For example, the first device 111 executes a program for outputting calendars, authenticates the first user 120 based on the user account input through the user input unit 16510, 1 user 120 to transmit information 8740 to be displayed on the calendar of the user 120. [

On the other hand, the server 100 may automatically transmit (e. G., Push) the information 8740 to be displayed on the calendar to the first device 111, even if there is no request from the first device 111 . For example, if there is a history that the first device 111 has previously requested transmission of the information 8740 to be displayed on the calendar of the first user 120, The information 8740 to be displayed on the calendar of the first user 120 can be automatically transmitted even if there is no request from the first user 120. [

88 is a flowchart showing an example in which a server according to some embodiments links job history information to a calendar of a user.

In S8801, the server 100 receives job history information of each of the documents and documents generated in each of the plurality of devices 110 from the plurality of devices 110. [ For example, the server 100 may receive a first document, a second document, and a Nth document from each of the devices 110, and also the server 100 may receive, from each of the devices 110, Document, the second document, and the N-th document, respectively. At this time, the devices 100 can transmit only a part of the job history information to the server 100 as described above with reference to FIG.

In S8802, the server 100 generates the 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. The connection relationship of the documents means the order in which the seed documents to be combined into the final document are to be linked, which will be described later, for example, the order of the table of contents, the order of the storing date and time, and the like.

In S8803, the server 100 links the received job history information to the calendar of the user using the time information included in the received job history information. Here, the time information means information indicating the time when the device worked on the document. For example, if the first device 111 sends a document called " abc.doc " The server 100 generates an indicator to be displayed on the calendar of the user of the first device 111 on the calendar of December 4, 2015, and the indicator displayed on the calendar 2014.05.12. Is selected The job history information to be output to the screen of the first device 111 can be determined. At this time, as described above with reference to FIG. 1, only a part of the job history information received from the devices 110 by the server 100 can be linked to the user's calendar.

89A to 89B, when the first device 111 and the second device 112 perform a co-authoring of a document, the server 100 may associate the job history information with the user's calendar An example is given.

FIGS. 89A to 89B are flowcharts illustrating an example in which a server cooperates with a user's calendar with job history information when a first device and a second device according to some embodiments perform co-authoring of a document.

89A to 89B show only the first device 111 and the second device 112 for convenience of explanation, there is no limitation on the number of devices. Assuming 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, Lt; / RTI >

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 generates a document can 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.

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

In S 8914, the first device 111 transmits the job history information of the first document and 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 job history information of the first document means information generated as the first device 111 generates and stores the first document. For example, the job history information may include at least one of a title of a document on which an operation is performed, a type of the document, a time at which the document operation was performed, a device name for performing the document operation, a user of the device, It can include the type of work. At this time, it is assumed that the user of the first device 111 is logged in the server 100. The example in which the first device 111 transmits the job history information of the document to the server 100 is as described above with reference to step S411 of FIG.

In S 8915, the second device 112 transmits the job history information of the second document and 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. At this time, it is assumed that the user of the second device 112 is logged in 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 as described above with reference to step S411 of FIG.

On the other hand, the order of S8910 to S8915 is arbitrarily designated for convenience of explanation, 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 can 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 the connection relationship between the first document and the second document. Here, the connection relationship between the first document and the second document means a sequence in which the first document and the second document are connected to combine to form a final document, and the connection between the table of contents of the first document and the table of contents of the second document, The storage date and time of the first document, and the post-storage date and time of the second document.

In S8918, the server 100 combines the first document and the second document according to the determined connection relationship to generate a final document.

In S8919, the server 100 stores the final document.

In S8920, the server 100 links the job history information to the calendar using the 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 execute the calendar output program installed in the first device 111, and may request the server 100 to transmit information to be displayed on the calendar after performing authentication of 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 execute a calendar output program installed in the second device 112, and may request the server 100 to transmit information to be displayed on the calendar after performing authentication of 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. [

On the other hand, the order of S8921 to S8924 is arbitrarily specified for convenience of explanation, and the order of S8921 to S8924 may be variously changed.

In FIG. 89B, when the first device 111 and the second device 112 respectively request the server 100 to transmit information to be displayed on the calendar in S8921 and S8922, in S8923 and S8924, The information to be displayed is transmitted to each of the first device 111 and the second device 112, but 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, push).

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

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

90 is a diagram for explaining an example of generating a document in the first device and the 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 for a MAC OS.

The user can create texts 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 name "METHOD FOR CONTROLLING APPLICATION" invented by the user through the program 9001. When the generation of the patent specification is completed, the first device 111 can store the document having the 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. May 14, AM 09:11:43 ".

On the other hand, the second device 112 executes the program 9002, which is installed in the second device 112, to generate 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 in the second device 112. [ 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 . However, if the second device 112 is a PC, the program 9002 installed in the second device 112 may be an MS OFFICE WORD program for the WINDOWS OS or a PAGE program for the MAC OS.

The user can create texts using the program 9002 executed in the second device 112. [ For example, the second device 112 may generate claims of a patent specification written by the user via the program 9002. [ When the generation of the claims of the patent specification is completed, the second device 112 can store the document having the 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. May 20, PM 08:46:11 ".

91 is a diagram for explaining an example of transmitting job history information of documents and documents generated in the first device and the second device 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 " 05. 14, AM 09:11:43 ". Then, the second device 112 stores the second document 9102 " draft specification 2.doc " 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 created for the co-authoring of the first device 111 and the second device 112 .

In order to perform co-authoring by combining documents, the first device 111 receives the job history information of the first document 9101 "draft specification 1.doc" and the first document 9101 "draft specification 1.doc" And the second device 112 transmits the job history information 9104 of the second document 9102 "draft specification 2.doc" and the second document "draft specification 2.doc" to the server 100, To the server 100.

Here, the job history information 9103 of the first document 9101 "draft specification 1.doc" is the date and time of storage 2014 of the first document 9101 "draft specification 1.doc". 05. 14, AM 09:11:43 ", the device name, the document creator, the contents information of the document, and the like. The job history information 9104 of the second document 9102 "draft specification 2.doc" is stored in the storage date / time "2014 of the second document 9102" draft specification 1.doc ". 05. 20, PM 08:46:11 ", the device name, the document creator, the contents information of the document, and the like.

The server 100 receives the job history information 9103 of the first document 9101 "draft specification 1.doc" and the first document 9101 "draft specification 1.doc" transmitted from the first device 111, And the job history information 9104 of the second document 9102 "draft specification 2.doc" and the second document "draft specification 2.doc", which are transmitted from the second device 112, are stored.

Meanwhile, as described above with reference to FIG. 7, encryption can be further performed in addition to the job history information of a document requiring high security level and transmitted to the server 100.

92 is a diagram for explaining an example of a process of combining documents by co-authoring devices according to some embodiments.

The first device 111, the second device 112 and the N device 114 are installed in the first device 111, the second device 112 and the N device 114, To create documents for collaborative authoring. Specifically, the first device 111 stores the storage date &quot; 2014. &Lt; 2014. < / RTI > The second device 112 may generate a document 9201 related to the contents of the sales history &quot; 2014 &quot; 05. 12, PM 12:28:04 &quot; And the Nth device 114 may generate a document 9202 related to the contents of the sales history &quot; 2014. &Lt; 2014 &gt; stored on May 28, 08:21:11 PM. (9203) regarding the content of the sales history of &quot; 05. 28 &quot;.

The first device 111, the second device 112 and the N 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 relation is described as being based on the date and time of storage of the documents 9201, 9202, and 9203.

The document 9201 is first compared with the other documents 9202 and 9203, 05. 14, AM 09:11:43 &quot;, and thus has the first priority. The document 9202 includes a storage date &quot; 2014. 05.12, PM 12:28:04 &quot;, it has a second priority. Finally, the document 9203 has a storage date &quot; 2014. 05, 28, PM 08:21:11 &quot;, so that it has the nth priority (n is a natural number). Accordingly, the server 100 can determine that the connection relationships of the documents 9201, 9202, and 9203 are in the order of the document 9201, the document 9202, and the document 9203.

The server 100 creates a final document 9210 as a result of the co-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 relationships determined for the documents 9201, 9202, and 9203. That is, the server 100 transmits the documents 9201, 9202, and 9203 in order of the document 9201 having the first priority, the document 9202 having the second priority, and the document 9203 having the nth priority, The final document 9210 can be generated.

Eventually, the server 100, by co-authoring, 02. 14 Sales Breakdown>, <2014. Revenue Breakdown of 05. 12> and <2014. The sales document of 05. 28 &gt; &lt; 2 &gt;

93 is a diagram for explaining another example of a process of combining documents by co-authoring devices according to some embodiments.

The first device 111, the second device 112 and the N device 114 are installed in the first device 111, the second device 112 and the N device 114, To create documents for collaborative authoring. In FIG. 93, the case where the first device 111, the second device 112 and the N-th device 114 jointly author the document of the patent specification is described as an example. Generally, the order of the contents is defined in the patent specification. For example, the order of a large table of contents in the patent specification is known to be "BACKGROUND", "SUMMARY", ..., "DETAILED DESCRIPTION", ..., "WHAT IS CLAIMED IS:" .

The first device 111 may generate a document 9301 "draft patent specification 1.doc" relating to the contents of the "BACKGROUND" and "SUMMARY" of the patent specification and the second device 112 may generate the document " Draft patent specification 2.doc "relating to the contents of the" DETAILED DESCRIPTION "9302 and the N-th device 114 may generate the document 9303 concerning the content of" WHAT IS CLAIMED IS: "in the patent specification, &Quot; draft patent specification 3.doc &quot;.

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

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

The document 9301 has the first priority because it contains the contents of the "BACKGROUND" and "SUMMARY" which are the most advanced table of contents compared with the other documents 9302 and 9303. The document 9302 has the second priority because it contains the contents of the next order of contents &quot; DETAILED DESCRIPTION &quot;. Finally, the document 9303 has the nth priority because it contains the contents of the next order of contents &quot; WHAT IS CLAIMED IS: &quot;. Accordingly, the server 100 can determine that the connection relationships of the documents 9301, 9302, and 9303 are in the order of the document 9301, the document 9302, and the document 9303.

The server 100 generates the final document 9310 as a result of the co-authoring of the first device 111, the second device 112 and the N-th device 114. Specifically, the server 100 can generate the final document 9310 by combining the documents 9301, 9302, and 9303 using the connection relationships determined for the documents 9301, 9302, and 9303. That is, the server 100 transmits the documents 9301, 9302, and 9303 in the order of the document 9301 having the first priority, the document 9302 having the second priority, and the document 9303 having the nth priority, The final document 9310 can be generated.

In the end, the server 100 creates a patent specification in which contents of "BACKGROUND", "SUMMARY", ..., "DETAILED DESCRIPTION", ..., "WHAT IS CLAIMED IS: Gt; 9210 &lt; / RTI &gt;

94A to 94B are flowcharts showing another example in which a server cooperates with a user's calendar with job history information when a first device and a second device according to some embodiments perform co-authoring of a document.

94A to 94B, only two of the first device 111 and the second device 112 are shown for convenience of explanation, but there is no limitation on the number of devices. Assuming 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, Lt; / RTI &gt;

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 generates a document can 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 job history information of the first document and 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 job history information of the first document means information generated as the first device 111 generates and stores the first document. For example, the job history information may include at least one of a title of a document on which an operation is performed, a type of the document, a time at which the document operation was performed, a device name for performing the document operation, a user of the device, It can include the type of work. At this time, it is assumed that the user of the first device 111 is logged in the server 100. The example in which the first device 111 transmits the job history information of the document to the server 100 is as described above with reference to step S411 of FIG.

In step S9403, the server 100 links the job history information to the calendar using the 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.

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

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

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

In step S9409, the second device 112 transmits the job history information of the second document and 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 job history information of the second document means information generated as the second device 112 generates and stores the second document. At this time, it is assumed that the user of the second device 112 is logged in 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 as described above with reference to step S411 of FIG.

In S9410, the server 100 stores the second document.

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

In S9412, the server 100 determines the connection relationship between the first document and the second document. Here, the connection relationship between the first document and the second document means a sequence in which the first document and the second document are connected to combine to form a final document, and the connection between the table of contents of the first document and the table of contents of the second document, The storage date and time of the first document, and the post-storage date and time of the second document.

In S9413, the server 100 combines the first document and the second document according to the determined connection relationship to generate a final document.

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 execute the calendar output program installed in the first device 111, and may request the server 100 to transmit information to be displayed on the calendar after performing authentication of the user .

At 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 execute a calendar output program installed in the second device 112, and may request the server 100 to transmit information to be displayed on the calendar after performing authentication of the user .

In S9417, the server 100 transmits the 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 arbitrarily specified for convenience of explanation, and the order of S9415 to S9418 may be variously changed.

94B, when the first device 111 and the second device 112 respectively request the server 100 to transmit information to be displayed on the calendar in S9415 to S9416, the server 100 in the step S9417 to S9418 transmits the information to the calendar The information to be displayed is transmitted to each of the first device 111 and the second device 112, but 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, push).

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

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

95 is a diagram for explaining another example of a process of combining documents by co-authoring devices according to some embodiments.

The first device 111, the second device 112 and the N device 114 are installed in the first device 111, the second device 112 and the N device 114, To create documents for collaborative authoring. In FIG. 95, a case where the first device 111, the second device 112, and the N-th device 114 jointly author the minutes is described as an example. In FIG. 95, it is assumed that the order of the table of contents of the minutes is specified in the order of &quot; purpose of meeting &quot;, &quot; preparations for meeting &quot; 9502 and &quot; content of meeting discussion 9503 &quot;. Further, 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 the manager of the company, and the first device 111 is a device used by a company employee.

The president can create a document 9501 listing the table of contents of the minutes by using the second device 112 owned by the president in order to hold a meeting for a meeting purpose for a specific subject.

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 transferred from the second device 112 via the server 100 to the N-th device 114 owned by the general manager 1 &lt; / RTI &gt;

If the purpose of <meeting> is determined by the president, the contents of other items of the minutes <preparation of meeting> (9502) and <meeting content> (9503) may be prepared by the president's subordinates.

When the document 9501 is transmitted to the N-th device 114 owned by the general manager through the server 100, the manager uses the N-th device 114 to acquire the document 9502 Can be generated. In addition, when the document 9501 is transmitted to the first device 111 owned by the employee via the server 100, the employee uses the first device 111 to send the document 9503 9505).

The first device 111 and the Nth 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 is described as being based on the table of contents included in the documents 9501, 9504, and 9505.

The document 9501 has the first priority because it contains the contents of the <meeting purpose> which is the most advanced table in comparison with the other documents 9504 and 9505. The document 9504 has the second priority because it contains the content of the <preparation of meeting> 9502 which is the table of contents of the next order. Finally, the document 9505 has the nth priority because it contains the contents of the <discussion content> 9503, which is the table of contents of the next order. Accordingly, the server 100 can determine that the connection relationship 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 the final document 9510 as a result of the co-authoring of the first device 111, the second device 112 and the N-th device 114. Specifically, the server 100 can generate the final document 9510 by combining the documents 9501, 9504, and 9505 using the connection relationships determined for the documents 9501, 9504, and 9505. That is, the server 100 transmits the documents 9501, 9504, and 9505 in the order of the document 9501 having the first priority, the document 9504 having the second priority, and the document 9505 having the nth priority, , The final document 9510 can be generated.

Eventually, the server 100 generates a final document 9510 of the minutes in which the contents of the <meeting purpose>, <meeting preparation contents> 9502 and <meeting discussion contents> 9503 are combined in order, Lt; / RTI &gt;

On the other hand, the server 100 may determine that the connection relationship of the documents 9501, 9504, and 9505 is based on the level of the creator who created the documents 9501, 9504, and 9505.

Specifically, the document 9501 has the first priority since it was created by the president with the highest rank compared to the other documents 9504 and 9505. The document 9504 has a second priority because it was created by the chief, who is in the next order of rank. Finally, the document 9505 has an nth priority since it was created by an employee in the next order of rank. Accordingly, the server 100 can determine that the connection relationship 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 transmits the documents 9501, 9504, and 9505 in order of the document 9501 having the first priority, the document 9504 having the second priority, and the document 9505 having the nth priority, ), The final document 9510 can be generated.

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

In order to perform the co-authoring, the first device 111 transmits a first document 9601 "draft 1.doc" to the server 100, and the second device 112 transmits a second document 9602 "draft 2.doc "to the server 100, and the N-th device 114 transmits the Nth document 9603" draft N.doc "to the server 100.

The server 100 determines the connection relationship of the first document 9601 to the Nth document 9603. Here, the connection relationships of the first document 9601 to the Nth document 9603 refer to the order in which the first document 9601 to the Nth document 9603 are connected to be combined into the final document 9610, Has already been described in the above examples.

The server 100 combines the first document 9601 to the Nth document 9603 according to the determined connection relationship to generate the final document 9610 and stores the generated final document 9610. [

97 is a view showing an example of displaying the history of documents generated by coauthoring 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. FIG. In the calendar 9720, an indicator 9730 of the shape of &quot;? &Quot; representing the co-authoring document may be displayed. Indicator (9730) "△" The number inside the shape may indicate how many documents were combined by co-authoring. For example, in the calendar 9720, the indicator 9730 displayed on 2014.05.04. May indicate that the three documents were combined by co-authoring.

The device 9710 may select the indicator &quot;? &Quot; shaped indicator 9730 in accordance with the user input received via the user input 16510. When the indicator 9730 is selected, the device 9710 can output the job history information 9740 of the co-authoring document to the screen.

The work history information 9740 of the co-authoring document includes information about the file name "workshop.doc" of the co-authoring document, documents "workshop_1.doc", "workshop_2.doc", and "workshop_3 .doc &quot; The job history information 9740 of the co-authoring document also includes information on the creation date and time of each of the documents "workshop_1.doc", "workshop_2.doc", and "workshop_3.doc" . For example, in the job history information 9740 of the co-authoring document, the creation date and time of &quot; workshop_2.doc &quot; 12. 26, AM 11:40:39 &quot;, and the device that created &quot; workshop_2.doc &quot; may include the information that the first device 111 is.

Device 9710 may select item 9750 of &quot; workshop_2.doc &quot;, which is part of the collaborative authoring document, according to the user input received via user input 16510. [ When the item 9750 is selected, the device 9710 can output the job history information 9760 of the document &quot; workshop_2.doc &quot; corresponding to the item 9750 to the screen.

On the other hand, the operation history information about the co-authoring document can be displayed for other directors 9770 as described above.

98 is a view showing another example of displaying the history of the documents generated by the co-author in the monthly calendar displayed on the screen of the device according to some embodiments.

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

The device 9810 may select the "Δ" shaped indicator 9830 displayed on 2014.01.06. According to the user input received via the user input portion 16510. When the indicator 9830 is selected, the device 9810 displays the indicator 9840 on the date of 2014.01.01. And the indicator 9850 on the date of 2014.01.28.

When the indicator 9830 is selected, the indicator 9840 and indicator 9850 displayed with the indicator 9830 are those marked to identify documents co-authored with the document specified in the indicator 9830. That is, the document specified in the indicator 9830 displayed on 2014.01.06., Together with the document specified in the indicator 9840 indicated in 2014.01.01. And the indicator 9850 indicated in 2014.01.28. It is a used document.

On the other hand, when the indicator 9830 is selected, the device 9810 can output the job history information 9860 of the co-authoring document to the screen.

The job history information 9860 of the co-authoring document includes information about the file name &quot; party.doc &quot; of the co-authoring document, documents "party_1.doc", "party_2.doc" .doc &quot; The job history information 9860 of the co-authoring document also includes information on the generation date and time of each of the documents "party_1.doc", "party_2.doc", and "party_3.doc" . For example, the job history information 9860 of the co-authoring document indicates that the generation date and time of "party_2.doc" is "2014.01.06. PM 08:14:56" and the device that created "party_2.doc" And a third device 113, for example.

Device 9810 may select an item 9870 of &quot; party_2.doc &quot; that is part of the collaborative authoring document in accordance with the user input received via user input 16510. [ When the item 9870 is selected, the device 9810 can output the job history information 9880 of the document &quot; party_2.doc &quot; corresponding to the item 9870 to the screen.

According to the above description, when a plurality of users co-author a document, the work history information related to the co-authoring of the document can be linked to the calendar, so that the document can be effectively managed and utilized.

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

99 shows an example in which at least one of a plurality of devices corresponds to a server and a device performing a server function interlocks a job history information with a user's calendar when devices perform document work FIG.

Referring to FIG. 99, the system 1 includes a first device 111 and a second device 112 to an N-th device 114. Here, the first device 111 refers to a device that performs the function of the server 100 in Fig.

At least one of the second device 112 to the Nth device 114 performs a document operation and transmits the job history information 130 of the document to the first device 111. [ For example, the second device 112 performs a document operation and transmits the 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 perform document work and transmit 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. Then, the first device 111 transmits information to be displayed on the calendar to at least one of the second device 112 to the N-th device 114. Here, the information to be displayed on the calendar means information to be displayed on the output calendar when a 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 as an indicator to be displayed on the calendar or an indicator to be displayed on the calendar is selected.

At this time, the first device 111 can transmit information to be displayed on the calendar only to the device requesting transmission of the information to be displayed on the calendar from the second device 112 to the N-th device 114. For example, the second device 112 executes a program for outputting a calendar and authenticates the first device 111 to the user's calendar by authenticating that the user is a user based on the user account entered through the user input unit 16510 And may request transmission of information to be displayed.

On the other hand, the first device 111 may automatically transmit (e. G., Push) information to be displayed on the calendar to the second device 112, even if there is no request from the second device 112. [

Hereinafter, with reference to FIG. 100, an example in which the first device 111 interlocks the operation history information with the user's calendar in the case where the second device 112 and the third device 113 perform a document operation do.

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

In FIG. 100, the second device 112 and the third device 113 are shown as working documents for convenience of explanation, but the present invention is not limited thereto. In other words, there is no limit to the number of devices that work with documents. Assuming that there is only one device working on the document, the operation of the third device 113, which will be described below, can be performed all in the second device 112. [ Further, if it is assumed that the number of devices working a document is N (N is a plurality of 3 or more), the operation of the third device 113, which will be described below, can be performed in at least one of the fourth device to the Nth device .

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

Assuming that the document to be processed by the second device 112 is 'abc.doc' and that the program used for creating, viewing or editing 'abc.doc' is a second program, the second device 112 You can run the first program and create, view or edit 'abc.doc'.

In step S10011, the second device 112 transmits the job history information of the document to the first device 111. [ For example, the second device 112 may transmit the job history information of the document to the first device 111 at the time when the execution of the program used for the document job ends 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 execution of the first program have. At this time, it is assumed that the user of the second device 112 is logged in the first device 111. In addition, the example in which the second device 112 transmits the job history information of the document to the first device 111 is as described above with reference to the step S411 of FIG.

In S10012, the third device 113 works on the document. For example, the third device 113 can execute the program used for the document operation and can work on the document using the program. For example, the program used for the document operation may be an MS OFFICE WORD program for the WINDOWS operating system (OS) installed in the third device 111, or a PAGE program for the MAC OS. At this time, it is assumed that the user of the third device 113 is logged in the first device 111. Examples of the third device 113 transmitting the job history information of the document to the first device 111 are as described above with reference to step S411 of FIG.

Assuming that the document to be worked on by the third device 113 is 'abcd.xls' and that the program used for creating, viewing or editing 'abcd.xls' is a second program, the third device 113 You can run the second program and create, view or edit 'abcd.xls'.

In step S10013, the third device 113 transmits the job history information of the document to the first device 111. [ For example, the third device 113 can transmit the job history information of the document to the first device 111 at the time when the execution of the program used for the document job ends or the document is stored. For example, the third device 113 can transmit the job history information of 'abcd.xls' to the first device 111 at the time of storing 'abcd.xls' or terminating the execution of the second program have

In step S10015, the first device associates the job history information with the calendar of the user using the time information included in the job history information received by the second device and the third device 113. [ For example, if the second device 112 stores 'abc.doc' at 08:01:42 AM on May 17, 2018, and the third device 113 stores 'abcd.xls' : 00, the first device 111 generates a first indicator to be displayed in an area corresponding to 2014.05.18 on the calendar, and generates a second indicator to be displayed in an area corresponding to 2014.05.20 .

At 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 the job history information to be displayed on the screen of the device as the indicator to be displayed on the calendar or the indicator displayed on the calendar is selected. For example, the second device 112 may request transmission of job history information to be output to the screen of the device as the first indicator, the second indicator, and the first and second indicators are selected.

In step 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 a calendar on the screen. For example, the second device 112 may output to the screen a calendar indicating the first indicator and the second indicator transmitted from the first device 111.

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

In step 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 a calendar on the screen. For example, the third device 113 may output a calendar indicating the first indicator and the second indicator transmitted from the first device 111 to the screen.

According to the above description, since the device can perform the function of the server, the private network system can be constructed without involvement of the external server.

101 to 146, when the user of the devices 110 is the same and the server 100 performs the document operation based on the request of the devices 110, An example of linking the job history information to the user's calendar will be described.

101 is a diagram for explaining an example in which, when a user of devices according to some embodiments is the same and a server performs a document operation based on a request of devices, the server cooperates with the user's calendar with job history information to be.

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

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

The server 100 of FIG. 101 executes a program used for document work installed in the server 100. FIG. therefore. The first user 120 can perform the document operation by accessing the server 100 from the device even if the device is not provided with a program used for document operation. The server 100 can obtain the job history information of the document from the server 100 without receiving the job history information of the document from the devices 110 because the server 100 performs the document job.

On the other hand, the devices 110 in FIG. 101 request the server 100 to perform a document operation without performing a document operation. 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 the document. In the same manner, the second device 112 to the N-th device 114 request the server 100 to perform the operation of the document.

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

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 a 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 as an indicator to be displayed on the calendar or an indicator to be displayed on the calendar is selected.

At this time, the server 100 may transmit the information 140 to be displayed on the calendar only to the device 110 that requested the transfer of the information 140 to be displayed on the calendar. For example, the first device 111 executes a program for outputting a calendar, authenticates the first user based on the user account entered through the user input unit 16510, And may request the transmission of information 140 to be displayed on the calendar.

On the other hand, the server 100 may automatically transmit (e. G., Push) the information 140 to be displayed on the calendar to the first device 111, even if there is no request from the first device 111 . For example, if there is a history that the first device 111 has previously requested transmission of the information 140 to be displayed on the calendar of the first user, then the server 100 may subsequently request a request from the first device 111 The information 140 to be displayed on the calendar of the first user can be automatically transmitted.

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

102 to Fig. 163, it is assumed that the device transmits work request information of a document to the server 100 by executing a server connection program (for example, a web access program). In other words, the user of the device accesses a predetermined web page (for example, a web page to which the server 100 accesses a program for working a document) and performs login. After that, the user of the device works on the web page where the login is performed. At this time, the device transmits user input for working with the document to the server 100, and the server 100 can work on the document based on the user input. The server 100 transmits the work screen of the document to the device in the form of a web page, and the device can output the received work screen to the screen. However, it is not limited to the above-described example that the device transmits the job request information of the document to the server 100. [

For example, the device may send job request information of a document to the server 100 by executing a job program (or application) installed in the device. In other words, the user of the device runs the work program installed on the device and works on the document. At this time, the device transmits user input for working with the document to the server 100, and the server 100 can work on the document based on the user input. The server 100 transmits information about the document to be processed to the device, and the device can output the received information to the screen.

Hereinafter, an example in which the server 100 links work history information to a calendar of a user will be described with reference to FIG.

102 is a flowchart showing an example in which a server according to some embodiments links work history information to a calendar of a user.

In S10210, the server 100 acquires job history information of a document that has been processed in the server 100 at the request of the user. In other words, the server 100 receives a document job request from at least one device of the same user, performs a document job, and obtains job history information.

In S10220, the server 100 links the acquired job history information to the user's calendar 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, if the server 100 generates a document 'abc.doc' at 12:28:04 pm on May 12, 2014 at the request of the first device 111, An indicator to be displayed on the calendar of the user of the first device 111 may be generated on the calendar of the user of the first device 111, and the operation history information to be output on the screen of the first device 111 may be determined by selecting the indicator indicated on 2014.05.12. At this time, as described above with reference to FIG. 1, only a part of the job history information acquired by the server 100 in S10210 can be linked to the user's calendar.

103, when the server 100 operates the document by the document operation request of the first device 111, when the server 100 links the operation history information to the calendar of the first user .

FIG. 103 is a flowchart illustrating an example in which a server interlocks job history information with a calendar of a first user when the server 100 performs a document job according to a document job request of a first device according to some embodiments.

In FIG. 103, for convenience of description, the server 100 has been shown to work on a document by a document work request of 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. There is also 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 to the server 100 information requesting a document operation. For example, the user of the first device 111 executes the fourth program and logs in, so that the first device 111 can transmit information requesting the document operation to the server 100. [ At this time, the user of the first device 111 may log in the fourth program using various methods including a method of inputting an ID / password.

In step S10311, the server 100 operates on the document based on the information received from the first device 111. [ For example, the server 100 can execute a program used for document operation on the server 100, and can work on the document using a program executed on the server 100. [ Assuming that the document to be processed by the server 100 is 'abc.doc' and that the program used for creating, browsing or editing 'abc.doc' is the fourth program, the server 100 transmits the fourth program Run, and create, view, or edit 'abc.doc'.

In step S10312, the server 100 transmits the information on 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 can transmit information on the work screen of the document to the first device 111 every time the document is operated. In other words, the server 100 can use the program executed in the server 100 to transmit to the first device 111 information regarding the work screen of the document to be changed each time the document is operated.

In S10313, the first device 111 outputs the job screen of the document. For example, the first device 111 can output a job screen of a document based on information on a job 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 can acquire job history information of a document at the time when the 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 job history information in the storage space corresponding to the account of the user of the first device 111. [

In S10315, the server 100 links the acquired job history information to the user's calendar using the time information included in the acquired job history information. For example, if the server 100 stores 'abc.doc' at 12:28:04 pm on May 12, 2014, 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 displayed on the screen of the device, by selecting an indicator to be displayed on the calendar or an indicator to be displayed on the calendar.

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 a calendar on the screen. For example, the first device 111 may output a calendar on which an indicator transmitted from the server 100 is displayed.

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 the job history information to be displayed on the screen of the device as the indicator to be displayed on the calendar or the 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 a calendar on the screen. For example, the second device 112 can output a calendar on which the indicator transmitted from the server 100 is displayed.

Hereinafter, an example in which the server 100 links work history information to a calendar of a user in the case where the server 100 generates a document will be described with reference to FIGS. 104 to 120. FIG.

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

In FIG. 104, the server 100 generates a document according to a document work request of the first device 111 and the second device 112 outputs a calendar on the screen for convenience of explanation. However, the present invention is not limited thereto . For example, the server 100 may generate a document by the document operation request of the first device 111, and the first device 111 and the second device 112 may display the calendar on the screen.

There is no limit to the number of devices. Assuming that the number of devices requesting a document job 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, Lt; RTI ID = 0.0 &gt; N) &lt; / RTI &gt;

In S10410, the first device 111 executes a server connection program. The first device 111 can execute the server connection program in order for the user to request the document operation to the server 100. [ For example, the user of the first device 111 can execute a server connection program and input his / her own ID / password.

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

In S10412, the server 100 generates a document. For example, the server 100 can execute a program used for creating a document on the server 100, and can generate a document using a program executed on the server 100. [ If the document generated by the server 100 is 'abc.doc' and the program used for generating 'abc.doc' is the fourth program, the server 100 executes the fourth program, abc.doc '.

In step S10413, the server 100 transmits the information about the job 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, the server 100 may transmit information on the work screen of the generated document to the first device 111. [

In S10414, the first device 111 outputs a job screen of the document. For example, the first device 111 can output a job screen of a document based on information on a job 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 request for storing a document by a user on a work screen of a document output to the first device, and may store the generated document.

In S10416, the server 100 acquires job history information of the document. For example, the server 100 may acquire job history information of a document at the time of storing the document. The job history information of a document means information generated as the server 100 generates and stores a document. For example, the job history information may include at least one of a title of a document on which an operation is performed, a type of the document, a time at which the document operation was performed, a device name for performing the document operation, a user of the device, It can include the type of work. For example, the server 100 may store the obtained job history information in the storage space corresponding to the account of the user of the first device 111. [

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

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

105, the first device 111 executes a server connection program. For example, the first device 111 may select an indicator that indicates a server connection program based on the user input received via the user input 16510. Then, the first device 111 can execute the server connection program corresponding to the selected indicator. The server connection program can be a web browser, and the address of the server can be inputted to the address window of the web browser.

105, when the server connection program is executed in the first device 111, the server 100 transmits information on the server connection program execution screen. The first device 111 transmits information requesting the document operation to the server 100 through the server connection program. At this time, the information requesting the document operation may be information requesting the document creation.

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

After storing the text document, the server 100 acquires job history information of the text document. For example, assuming that the server 100 stores a document named 'abc.doc' with a size of 54 KB (kilobyte) at 12:28:04 PM on May 12, 2014 using the fourth program , 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 high security is required for the stored document, the server 100 may additionally perform encryption and store the job history information.

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

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

The user can access the job history information transmitted to the server 100 after logging into the server 100. [ However, additional information may be additionally required to access the job history information on which encryption has been performed. For example, even after the user logs in the server 100 by inputting the password / ID, it can be set to input a separate password in order to access the encrypted job history information.

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

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

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

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

In S10710, the server 100 acquires the generation time information of the document included in the obtained job history information as the document is generated 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 generates a document based on a job request from the first device 111, : 28: 04 'for the first time.

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

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

108, an example of job history information 10810 of a document is shown. For example, the job history information 10810 of the document includes the name of the document 10811, the type of document 10812, the name of the job program 10813, the name of the job requesting device 10814, A job type 10816, a job date and time 10817, and a file size 10818. However, the present invention is not limited thereto. In other words, the job history information 10810 of the document can be unlimited if it is information that can be generated by performing the operation of the document.

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

Referring to FIG. 109, another example of the job history information 10910 of a document is shown. 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, the job history information 10910 of the document shown in FIG. 109 includes the name of the document 10914, the document type 10912, the name of the job program 10913, the name of the job request device 10911, A user type 10916, a job type 10915, a job date and time 10917, and a file size 10918. [ For example, the server 100 arranges the job history information 10910 acquired by the server 100 on the basis of the name 10911 of the job device, and arranges the arranged job history information 10910 in the database 16430, Lt; / RTI &gt;

Referring again to Fig. 107, in S10720, 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 the job history information to the user's calendar will be described with reference to FIG.

110 is a flowchart showing an example in which a server according to some embodiments links work history information to a calendar of a user.

In S11010, the server 100 acquires the calendar of the user. Here, the user's calendar means a frame in which the job history information of the document is to be linked. For example, the server 100 may read the calendar of the user, which is matched with the user's account from the database 16430, and may receive the user's calendar from at least one of the devices 110. [ For example, a user's calendar can include a calendar displayed in days, a calendar in week, a calendar in month, or a calendar in year.

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 job history information, the program used for creating the document, and the name of the device requesting the generation of the document. In other words, the server 100 determines one of the name of the document, the program used for creating the document, and the name of the device requesting the 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 the job history information to be displayed on the calendar based on the generated indicator.

In S11040, the server 100 displays an indicator in an area corresponding to the date or time indicating the time at which the document was generated in the calendar.

Referring again to Fig. 104, at 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 execute a calendar output program installed in the second device 112, and may request the server 100 to transmit information to be displayed on the calendar after performing authentication of the user .

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

104 shows that the server 100 transmits the information to be displayed on the calendar in step S10419 when the second device 112 requests the server 100 to transmit the information to be displayed on the calendar in step S10418, It does not. For example, the server 100 may send (e. G., Push) information to be displayed on the calendar to the second device 112, even if there is no request for transmission of 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. FIG. In the calendar 11120, an indicator 11160 indicating the name of the document may be displayed. For example, in response to a request from the first device 111, assuming that the server 100 has generated a document named 'abc.doc' on 2014.05.12 using the fourth program, the calendar 11120 An indicator 11160 indicating 'abc.doc' may be displayed in the area corresponding to 2014.05.12.

The device 11110 may select an indicator 11160 indicating 'abc.doc' according to the user input received via the user input unit 16510. When the indicator 11160 indicating 'abc.doc' is selected, the device 11110 can output the job history information 11170 of the document to the screen. For example, in response to a request from the first device 111, the server 100 may use a fourth program to create a document named 'abc.doc' having a size of 54 kilobytes (KB) Quot; abc.doc, text, the fourth program, the first device, 12:28:04 PM on May 12, 2014, 54 KB, &quot; Can be output. On the other hand, the device 11110 can output the job history information 11170 of the document as a separate pop-up window on the screen.

In the document operation history information 11170, an indicator 11180 capable of outputting a document to the screen of the device 11110 may be displayed. For example, when an 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 a document in a pop-up window separate from the calendar 11120 .

112 is a diagram showing another example of the daily calendar displayed on the screen of the device according to some embodiments.

Referring to FIG. 112, a daily calendar 11220 is output on the screen of the device 11210. FIG. The calendar 11220 shown in FIG. 112 has the same frame as the calendar 11120 shown in FIG. Therefore, the above description with reference to FIG. 111 for the indicators that can be displayed on the calendar 11220 can be similarly applied to FIG.

The calendar 11220 may be displayed with an indicator 11230 indicating a program used for document operation. For example, in response to a request from the first device 11210, assuming that the server 100 generated a document using the fourth program on May 1, 2015, the region corresponding to 2014.05.12 of the calendar 11220 An indicator 11230 indicating 'fourth program' may be displayed.

The device 11210 may select the indicator 11230 indicating the 'fourth program' according to the user input received via the user input unit 16510. [ When the indicator 11230 indicating 'fourth program' is selected, the device 11210 can output the job history information 11240 of the document to the screen. For example, in response to a request from the first device 111, the server 100 may use a fourth program to create a document named 'abc.doc' having a size of 54 kilobytes (KB) Quot; abc.doc, text, the fourth program, the first device, 12:28:04 PM on May 12, 2014, and 54 KB, respectively, on the job history information 11240. [ Can be output. On the other hand, the device 11210 can output the job history information 11240 of the document as a separate popup window on the screen.

Also, the job history information 11240 of the document may be provided with an indicator 11250 capable of outputting the document to the screen of the device 11210. [ 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 a document in a pop-up window separate from the calendar 11220 .

113 is a diagram showing another example of the daily calendar displayed on the screen of the device according to some embodiments.

113, a daily calendar 11320 is output on the screen of the device 11310. [ The calendar 11320 shown in FIG. 113 has the same frame as the calendar 11120 shown in FIG. Therefore, the above description with reference to FIG. 111 for the indicators that can be displayed on the calendar 11320 can be similarly applied to FIG.

In the calendar 11320, an indicator 11330 indicating the name of the device may be displayed. For example, in response to a request from the first device 111, assuming that the server 100 generated a document on 2014.05.12 using the fourth program, the region corresponding to 2014.05.12 of the calendar 11320 An indicator 11340 indicating 'first device' may be displayed.

The device 11310 may select the indicator 11330 indicating 'first device' according to the user input received through the user input unit 16510. When the indicator 11330 indicating 'first device' is selected, the device 11310 can output the job history information 11340 of the document to the screen. For example, in response to a request from the first device 111, the server 100 may use a fourth program to create a document named 'abc.doc' having a size of 54 kilobytes (KB) Quot; abc.doc, text, fourth program, first device, 12:28:04 PM on May 12, 2014, 54 KB, Can be output. On the other hand, the device 11310 can output the job history information 11340 of the document as a separate pop-up window on the screen.

Further, in the job history information 11340 of the document, an indicator 11350 capable of outputting the document to the screen of the device 11310 may be displayed. For example, when an indicator 11350 capable of outputting a document is selected according to a user input received through the user input unit 16510, the device 11310 outputs a document in a pop-up window separate from the calendar 11320 .

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. FIG. The calendar 11420 shown in FIG. 114 has the same frame as the calendar 1920 shown in FIG. Therefore, the above-described contents with reference to FIG. 19 for the objects that can be displayed on the calendar 11420 can be similarly applied to FIG. In the calendar 11420, an indicator 11430 indicating the name of the document may be displayed. For example, in response to a request from the first device 111, assuming that the server 100 has created a document named &quot; abc.doc &quot; at 2014.05.12, An indicator 11430 indicating 'abc.doc' may be displayed in the area.

Device 11410 may select an indicator 11430 indicating 'abc.doc' according to user input received via user input 16510. When the indicator 11430 indicating 'abc.doc' is selected, the device 11410 can output the job history information 11440 of the document to the screen.

For example, in response to a request from the first device 111, the server 100 may use a fourth program to create a document named 'abc.doc' having a size of 54 kilobytes (KB) Quot; abc.doc, text, the fourth program, the first device, 12:28:04 PM on May 12, 2014, 54 KB, &quot; Can be output. On the other hand, the device 11410 can output the job history information 11440 of the document as a separate popup window on the screen.

Also, the job history information 11440 of the document may be provided with an indicator 11450 capable of outputting the document to the screen of the device 11410. [ For example, when an 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 popup window separate from the calendar 11420, 111) can output the generated document to the screen.

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

115, on a screen of the device 11510, a monthly calendar 11520 is output. The calendar 11520 shown in FIG. 115 has the same frame as the calendar 1920 shown in FIG. Therefore, the above description with reference to FIG. 19 for the objects that can be displayed on the calendar 11520 can be equally applied to FIG.

In the calendar 11520, an indicator 11530 indicating a program used for document work may be displayed. For example, in response to a request from the first device 11510, assuming that the server 100 has generated a document using the fourth program at 2014.05.12, the region corresponding to 2014.05.12 of the calendar 11520 An indicator 11530 indicating 'fourth program' may be displayed.

The device 11510 may select an indicator 11530 indicating a 'fourth program' according to the user input received via the user input unit 16510. When the indicator 11530 indicating 'fourth program' is selected, the device 11510 can output the job history information 11540 of the document to the screen. For example, in response to a request from the first device 111, the server 100 may use the fourth program to send a document named 'abc.doc' having a size of 54 kilobytes (KB) 12:28:04, the job history information 11540 includes 'abc.doc, text, fourth program, first device, 12:28:04 PM on May 12, 2014, 54 KB' Can be output. On the other hand, the device 11510 can output the job history information 11540 of the document as a separate popup window on the screen.

In addition, in the job history information 11540 of the document, an indicator 11550 capable of outputting the document to the screen of the device 11510 may be displayed. For example, if 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 may display a popup window separate from the calendar 11520, 111) can output the generated document to the screen.

116 is a diagram showing another example of the monthly calendar displayed on the screen of the device according to some embodiments.

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. Therefore, the above description with reference to FIG. 19 for the objects that can be displayed on the calendar 11620 can be similarly applied to FIG.

In the calendar 11620, an indicator 11630 indicating the name of the device may be displayed. For example, in response to a request from the first device 111, if it is assumed that the server 100 has generated a document at 2014.05.12, the 'first device' is stored in the area corresponding to 2014.05.12 of the calendar 11620 An indicator 11630 may be displayed.

The device 11610 may select an indicator 11630 indicating 'first device' according to the user input received via the user input section 16510. When the indicator 11630 indicating 'first device' is selected, the device 11610 can output the job history information 11640 of the document to the screen. For example, in response to a request from the first device 111, the server 100 may use a fourth program to create a document named 'abc.doc' having a size of 54 kilobytes (KB) Quot; abc.doc, text, the fourth program, the first device, 12:28:04 PM on May 12, 2014, 54 KB, Can be output. On the other hand, the device 11610 can output the job history information 11640 of the document as a separate popup window on the screen.

In addition, the job history information 11640 of the document may be provided with an indicator 11650 capable of outputting the document to the screen of the device 11610. [ For example, if an indicator 11650 capable of outputting a document according to a user input received via the user input unit 16510 is selected, the device 11610 may display a popup window separate from the calendar 11620, 111) can output the generated document to the screen.

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

117, on the screen of the device 11710, an annual calendar 11720 is output. As described above with reference to FIG. 22, the calendar 11720 may include an area 11721 in which months included in one year are displayed, and an indicator 11722 that allows the user to specify a desired year. In addition, the calendar 11720 may include an indicator 11723 capable of displaying a calendar of the year including the date of 'today'. In addition to the above-described indicators, the calendar 11720 may include any number of indicators that allow the user to control the display type.

Indicators 11730, 11740, and 11750 indicating the name of the document may be displayed on the calendar 11720. For example, in response to a request from the first device 111, if it is assumed that the server 100 has generated a document named 'xyz.doc' in 2014.02.12, then in the area corresponding to 2014.02 in the calendar 11720 an indicator 11730 indicating 'xyz.doc' may be displayed.

Assuming that the server 100 has generated a document named 'abcd.xls' on 2014.04.22 in response to a request from the first device 111, 'abcd.xls' is entered in the area corresponding to 2014.04 in the calendar 11720 an indicator 11740 indicating .xls' may be displayed.

Assuming that the server 100 has generated a document named 'abc.doc' in 2014.05.12 by using the fourth program in response to a request from the first device 111, An indicator 11750 indicating 'abc.doc' may be displayed in the corresponding area.

In the above description, 'xyz.doc', 'abcd.xls', and 'abc.doc' are all 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 directors 11730, 11740, and 11750 indicating the name of the document are selected, the device 11710 can output the job history information 11760 of the document to the screen.

For example, in response to a request from the first device 111, the server 100 may use a fourth program to create a document named 'abc.doc' having a size of 54 kilobytes (KB) It is assumed that it is stored at 12:28:04 PM. At this time, if the indicator 11750 indicating 'abc.doc' is selected, 'abc.doc', text, the fourth program, the first device, 12:28:28 PM on May 12, 04, 54 KB 'can be output. On the other hand, the device 11710 can output the job history information 11760 of the document as a separate popup window on the screen.

In the document operation history information 11760, an indicator 11770 capable of outputting a document to the screen of the device 11710 may be displayed. 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 popup window separate from the calendar 11720, 111) can output the generated document to the screen.

118 is a diagram showing another example of the annual calendar displayed on the screen of the device according to some embodiments.

118, on the screen of the device 11810, an annual calendar 11820 is output. In the calendar 11820, an indicator 11830 indicating a program (for example, a fourth program) used for document work is displayed.

As described above with reference to FIG. 117, when the indicator 11830 indicating the program used for document operation is selected, the device 11810 can output the job history information 11840 of the document to the screen. When an indicator 11850 capable of outputting a document is selected on the screen on which the job history information 11840 of the document is displayed, the device 11810 can output the document generated by the first device 111 to the screen .

119 is a diagram showing another example of the annual calendar displayed on the screen of the device according to some embodiments.

119, on the screen of the device 11910, an annual calendar 11920 is output. In the calendar 11920, an indicator 11930 indicating a device is displayed. As described above with reference to Fig. 117, when the indicator 11930 indicating the device is selected, the device 11910 can output the execution history information 11940 of the document to the screen. When the indicator 11950 capable of outputting a document is selected on the screen displaying the execution history information 11940 of the document, the device 11910 can output the document generated by the first device 111 to the screen .

120 is a diagram showing another example of the annual calendar displayed on the screen of the device according to some embodiments.

Referring to FIG. 120, an annual calendar 12020 is output on the screen of the device 12010. The annual calendar shown in FIG. 117 to FIG. 119 includes an area in which the months included in the year are displayed. However, in the annual calendar 12020 shown in FIG. 120, . In other words, the device 12010 can change the format of the annual calendar and output it to the screen.

In the calendar 12020, indicators 12031, 12032, and 12033 may be displayed on the date the job of the document is performed. For example, in response to a request from the first device 111, assuming that the server 100 has generated a document named 'xyz.doc' in 2014.02.12, An indicator 12031 indicating 'xyz.doc' may be displayed in the area.

Assuming that the server 100 has generated a document named 'abcd.xls' in 2014.04.22 in response to a request from the first device 111, it is assumed that the region corresponding to 2014.04.22 in the calendar 12020 an indicator 12032 indicating 'abcd.xls' may be displayed.

Further, in response to a request from the first device 111, assuming that the server 100 has generated a document named 'abc.doc' in 2014.05.12 using the fourth program, An indicator 12033 indicating 'abc.doc' may be displayed in an area corresponding to 12.

In the above description, 'xyz.doc', 'abcd.xls', and 'abc.doc' are all generated by the first device 111, but 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 can 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 in the job history information 12040. When an indicator 12050 capable of outputting a document is selected on the screen on which the job history information 12040 of the document is displayed, the device 12010 can output the document generated by the first device 111 to the screen .

FIGS. 121A to 121C illustrate a case where a server performs a document operation according to a document operation request of a first device according to some embodiments, and a server displays operation history information in a calendar of a first user Fig. 2 is a flowchart showing an example of interworking.

In FIGS. 121A to 121C, the server 100 is shown to work on a document according to a document work request of 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. There is also 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 a server connection program. The first device 111 can execute the server connection program in order for the user to request the document operation to the server 100. [ For example, the user of the first device 111 can execute a server connection program and input his / her own ID / password.

In step S12111, the first device 111 transmits information requesting the document operation 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 can execute a program used for creating a document on the server 100, and can generate a document using a program executed on the server 100. [

For example, assuming that the document generated by the server 100 is 'abc.doc' and that the program used for generating 'abc.doc' is the fourth program, the server 100 executes the fourth program , 'abc.doc' can be created, viewed or edited.

In step S12113, the server 100 transmits information on 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 can transmit information on the work screen of the document to the first device 111 every time the document is operated. In other words, the server 100 can use the program executed in the server 100 to transmit to the first device 111 information regarding the work screen of the document to be changed each time the document is operated.

In step S12114, the first device 111 outputs a job screen of the document. For example, the first device 111 can output a job screen of a document based on information on a job 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 job history information of the document. For example, the server 100 can acquire job history information of a document at the time when the 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 job history information in the storage space corresponding to the account of the user of the first device 111. [

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

At 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 the job history information to be displayed on the screen of the device as the indicator to be displayed on the calendar or the indicator displayed on the calendar is selected. The second device 112 may execute the calendar output program installed in the second device 112 and authenticate the user using the input user account and then request the server 100 to transmit information to be displayed on the calendar .

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

121A shows that the server 100 transmits information to be displayed on the calendar in step S12119 when the second device 112 requests the server 100 to transmit information to be displayed on the calendar in step S12118, It is not limited. For example, the second device 112 may transmit (e. G., Push) information to be displayed on the calendar, even if there is no transmission request of the second device 112. [

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

In S12121, the second device 112 executes the server connection program. In order for a user to request a document job from the server 100, the second device 112 may execute a server connection program. For example, the user of the second device 112 may execute a server connection program and input his / her own ID / password.

In step S12122, the second device 112 transmits information requesting the document processing to the server 100. [

In step S12123, the second device 112 receives information on the operation screen of the document from the server 100. [

In step S12124, the second device 112 outputs a job screen of the document.

In S12125, the second device 112 ends the output of the job screen.

In step S12126, the second device 112 notifies the server 100 that the output of the job 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 job history information in the storage space corresponding to the account of the user of the second device 112. [

In S12128, the server 100 links the job history information to the calendar using the time information included in the obtained job history information.

In step 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 displayed on the screen of the device, by selecting an indicator to be displayed on the calendar or an indicator to be displayed on the calendar.

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

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

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

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

122, the second device 112 requests the server 100 to perform a document operation, and the server 100 requests the document to be processed from the server 100. In step S12134, the second device 112 outputs a calendar on the screen. Will be described.

122 is a diagram for explaining an example in which a second device according to some embodiments requests a server to perform a job of a document and receives information about a job screen.

122, a calendar 12210 output on the screen of the second device 112 is shown. Here, the calendar 12210 means 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 that selects the indicator 12220 displayed on the calendar 12210 via the user input 16510. [ The second device 112 outputs job history information 12230 of the document on the screen in accordance with the received user input. At this time, on the screen displaying the job history information 12230 of the document, an indicator 12240 capable of outputting the document to the screen of the second device 112 may be displayed.

The second device 112 receives a user input for selecting the indicator 12240 via the user input 16510. [ The second device 112 requests (12250) a document job from the server 100 according to the received user input. In response to a request from the second device 112, the server 100 transmits information about the operation screen to the second device 112 (12260).

Referring again to FIG. 122, in step S12224, the second device 112 outputs a job screen of the document transmitted from the server 100. FIG.

In S12225, the second device 112 ends the output of the job screen. Hereinafter, an example in which the second device 112 ends the output of the job screen will be described with reference to FIG.

123 is a diagram for explaining an example in which a second device according to some embodiments terminates the output of a job screen.

123, the work screen received from the server 100 is output (12310) to the screen of the second device 112. [ The second device 112 receives a user input for terminating the output 12310 of the work screen via the user input unit 16510. [ For example, the user input may be an input 12320 that terminates execution of a program used for document operation.

123, the second device 112 receives a user input for selecting an indicator 12320 displayed on the screen. Then, the second device 112 terminates 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 according to some embodiments transmits job history information of a document to a server.

124, the second device 112 notifies the server 100 of the end of the output of the document, and the server 100 receives the job history information of the document from the second device 112. [

After storing the text document, the server 100 acquires job history information of the text document. For example, if the second device 112 has stored a document named 'abc.doc' with a size of 54 kilobytes using the first program at 20:20:20 PM on May 20, 2014 Assuming that the server 100 can acquire at least one of "abc.doc, text, fourth program, second device, May 20, 2014 at 08:46:11, 54 KB".

On the other hand, as described above with reference to FIG. 106, encryption can be additionally performed and stored in the job history information of a document requiring high security.

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

In step S12510, the server 100 obtains the browse time information of the document included in the obtained job history information by browsing 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, when the server 100 reads the document based on the job request from the second device 112, : 46: 11 '.

126 to 127 are diagrams showing an example of job history information of a document according to some embodiments.

126, an example of job history information 12610 of a document is shown. For example, the job history information 12610 of the document includes the name of the document 12611, the type of document, the name of the job program, the name of the user who has worked, the name of the job device, the job type, But is not limited thereto. In other words, the job history information 12610 of the document can be applied without restriction as long as the information can be generated by performing the job 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. In other words, the job history information 10810 of the document shown in FIG. 108 means the job history information generated as the device generates the document.

On the other hand, the job history information 12620 of the document shown in FIG. 126 indicates that the first device 111 generates the document and the new job history information 12620 is added as the second device views the document. 126, the first device 111 generates the abc.doc document at 2014.05.12 PM 12:28:04 and the second device 112 generates the abc.doc document at 2014.05.20 PM 08:46 : 11 shows a case where new job history information 12620 is added.

The job history information 12630 of the document shown in FIG. 126 is obtained by adding the new job history information 12630 as the Nth device 114 generates the document and the third device 113 reads the document . 126, a first user creates a kkk.ppt document on 2013.01.01 AM 2:21:04 using the N-th device 114, and the first user uses the third device 113 kkk.ppt document is added to the new job history information 12630 that was viewed at 2014.05.28 PM 08:21:11.

Referring to FIG. 127, another example of job history information 12710 of a document is shown. 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 a job device request name 12711, a document type, a job program name, a document name, a job type, a user who has worked, .

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. In other words, the job history information 10910 of the document shown in FIG. 109 means the job history information 10910 generated as the device generates the document. On the other hand, the job history information 12710 of the document shown in FIG. 127 indicates that the new job history information 12720 and 12730 have been added as a result of viewing at least one of the devices.

The job history information 12710 of the document shown in FIG. 127 indicates that the new job history information 12720 is added as the second device 112 browses the abc.doc document. Specifically, FIG. 127 shows an example of the case where the second device 112 adds new job history information 12720, which reads the abc.doc document at 2014.05.20 PM 08:46:11.

The job history information 12710 of the document shown in FIG. 127 indicates that the new job history information 12730 is added as the third device 113 browses the kkk.ppt document. Specifically, FIG. 127 shows an example of the case where the third job history information 12730, in which the third device 113 has viewed the kkk.ppt document at 2014.05.28 PM 08:21:11, is added.

128 is a flowchart showing an example in which a server according to some embodiments links work history information to a calendar of a user.

In S12810, the server 100 acquires the calendar of the created user. Here, the created user's calendar means a frame in which the job history information of the document is to be linked. For example, the server 100 may read the calendar of the user, which is matched with the user's account from the database 16430, and may receive the user's calendar from at least one of the devices 110. [ For example, a user's calendar can include a calendar displayed in days, a calendar in week, a calendar in month, or a calendar in year.

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 job 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 to browse the document, and the name of the device requesting the reading of the document as an item indicated by the indicator, and generates an indicator based on the determined item.

In S12830, the server 100 determines the job history information to be displayed on the calendar on the basis of the browsed indicator.

In S12840, the server 100 adds an indicator to the area corresponding to the date or time indicating the time when the document is viewed on the calendar, and displays the indicator.

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. In the calendar 12911, an indicator 12920 indicating the name of the document may be displayed. For example, if the server 100 generates a document named 'abc.doc' in 2014.05.12 in response to a request from the first device 111, then the calendar 12911 returns an area corresponding to 2014.05.12 An indicator 12920 indicating 'abc.doc' may be displayed.

The device 12910 may select an indicator 12920 indicating 'abc.doc' according to the user input received via the user input unit 16510. When the indicator 12920 indicating 'abc.doc' is selected, the device 12910 can output the job history information 12921 of the document to the screen. For example, in response to a request from the first device 111, the server 100 may use a fourth program to create a document named 'abc.doc' having a size of 54 kilobytes (KB) Quot; abc.doc, text, the fourth program, the first device, 12:28:04 PM on May 12, 2014, and 54 KB, respectively, on the job history information 12921. [ Can be output. On the other hand, the device 12910 can output the job history information 12921 of the document as a separate popup window on the screen.

In the job history information 12921 of the document, an indicator 12922 capable of outputting a document to the screen of the device 12910 may be displayed. For example, when an 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 popup window separate from the calendar 12911, 111) can output the generated document to the screen.

Similarly, a plurality of indicators indicating the name of the document can be displayed in one calendar 12911. [ For example, upon request of the second device 112, assuming that the server 100 has browsed a document named "abc.doc" on 2014.05.20, An indicator 12930 indicating 'abc.doc' may be displayed in the area.

The device 12910 may select an indicator 12930 indicating 'abc.doc' according to the user input received via the user input unit 16510. When the indicator 12930 indicating 'abc.doc' is selected, the device 12910 can output the job history information 12931 of the document to the screen. For example, in response to a request from the second device 112, the server 100 may use a fourth program to send a document named 'abc.doc' having a size of 54 kilobytes (KB) Quot; abc.doc, text, fourth program, second device, May 20, 2014 at 08:46:11, 54 KB, and the like, on the job history information 12931. [ Can be output. On the other hand, the device 12910 can output the job history information 12931 of the document as a separate popup window on the screen.

In the job history information 12931 of the document, an indicator 12932 capable of outputting the document to the screen of the device 12910 may be displayed. 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 popup window separate from the calendar 12911, 112 can output the document viewed on the screen.

130 is a diagram showing another example of the daily calendar displayed on the screen of the device according to some embodiments.

Referring to FIG. 130, a daily calendar 13011 is output on the screen of the device 13010. FIG. An indicator 13020 indicating the name of the device may be displayed in the calendar 13011. [ For example, if the first device 111 generates a document at 2014.05.12, an indicator 13020 indicating 'first device' may be displayed in an area corresponding to 2014.05.12 of the calendar 13011 have.

The device 13010 may select an indicator 13020 indicating 'first device' according to the user input received through the user input unit 16510. When the indicator 13020 indicating 'first device' is selected, the device 13010 can output the job history information 13021 of the document to the screen. For example, in response to a request from the first device 111, the server 100 may use a fourth program to create a document named 'abc.doc' having a size of 54 kilobytes (KB) Quot; abc.doc, text, fourth program, first device, 12:28:04 PM on May 12, 2014, 54 KB, Can be output. On the other hand, the device 13010 can output the job history information 13021 of the document as a separate popup window on the screen.

In the job history information 13021 of the document, an indicator 13022 capable of outputting the document to the screen of the device 13010 may be displayed. For example, when an 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 popup window separate from the calendar 13011, 111) can output the generated document to the screen.

Similarly, in one calendar 13011, a plurality of directives indicating the name of the device can be displayed. For example, in response to a request from the second device 112, assuming that the server 100 has read a document named "abc.doc" on 2014.05.20, An indicator 13030 indicating 'second device' may be displayed in the area.

The device 13010 may select an indicator 13030 indicating 'second device' according to the user input received through the user input unit 16510. When the indicator 13030 indicating 'second device' is selected, the device 13010 can output the job history information 13031 of the document to the screen. For example, in response to a request from the second device 112, the server 100 may use a fourth program to send a document named 'abc.doc' having a size of 54 kilobytes (KB) Quot; abc.doc, text, a fourth program, a second device, a job of 54 KB on May 20, 2014 at 08:46:11, &quot; Can be output. On the other hand, the device 13010 can output the job history information 13031 of the document as a separate popup window on the screen.

In the job history information 13031 of the document, an indicator 13032 capable of outputting the document to the screen of the device 13010 may be displayed. 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 popup window separate from the calendar 13011, 112 can output the document viewed on the screen.

Hereinafter, with reference to FIGS. 131A to 140, the server 110 generates a document according to a request of the first device 111, and the server 110 edits the document according to a request of the second device 112 An example in which the server 110 links the job history information with the user's calendar will be described.

FIGS. 131A through 131C illustrate a case where, when a server generates a document according to a request of a first device according to some embodiments and a server edits a document according to a request of a second device, As shown in Fig.

131A to 131C, 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. 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.

There is no limit to the number of devices. Assuming that the number of devices requesting a document job 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, Lt; RTI ID = 0.0 &gt; N) &lt; / RTI &gt;

S13110 to S13120 in Fig. 131A correspond to S10410 to S10420 in Fig. Therefore, even if omitted from the following description, the above description with reference to FIGS. 104 to 120 can be applied to the contents to be described later with reference to S13110 to S13120 of FIG.

In S13110, the first device 111 executes a server connection program. The first device 111 can execute the server connection program in order for the user to request the document operation to the server 100. [ For example, the user of the first device 111 can execute a server connection program and input his / her own ID / password.

In step S13111, the first device 111 transmits information requesting the document processing to the server 110. [

In step S13112, the server 110 generates a document according to the request received from the first device 111. [

In step 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 job 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 job history information of a document at the time of storing the document. For example, the server 100 may store the obtained job history information in the storage space corresponding to the account of the user of the first device 111. [

In S13117, the server 110 links the job history information to the calendar using the time information included in the acquired job history information.

At 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 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 110 .

In step S13119, the server 110 transmits information to be displayed on the calendar to the second device 112. [

In FIG. 131A, in step S13118, when the second device 112 requests the server 110 to transmit information to be displayed on the calendar, the server 110 transmits the information to be displayed on the calendar in step S13119. It is not limited. For example, the second device 112 may transmit (e. G., Push) information to be displayed on the calendar, even if there is no transmission request of the second device 112. [

At S13120, the second device 112 outputs the calendar to the screen.

In S13121, the second device 112 executes the server connection program. In order for a user to request a document job from the server 100, the second device 112 may execute a server connection program. For example, the user of the second device 112 may execute a server connection program and input his / her own ID / password.

In S13122, the second device 112 transmits information requesting the document processing to the server 110. [

In S13123, the server 110 executes the document.

In step S13124, the server 110 transmits information on the work screen of the document to the second device 112. [

In S13125, the second device 112 outputs a job screen of the document.

In step S13126, the second device 112 transmits the edit 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 edit request information of the document according to the received user input to the server 110).

In S13127, the server 110 edits the document.

In step S13128, the server 110 transmits information on the work screen of the edited document to the second device 112. [

In step S13129, the server 110 stores the edited document, and in step 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 FIG. 132 to FIG.

FIGS. 132 through 133 are diagrams for implementing examples in which the server 110 edits a document according to some embodiments.

Referring to FIGS. 132 to 133, the second device 112 receives the document operation screen 13210 and 13310 from the server 110 and displays the operation screen 13210 and 13310 on the screen. The second device 112 receives a user input for editing a document via a user input 16510. For example, the user input may be to add 13220 a new content to the document, or may be to delete 13320 some or all of the content of the document. Although not shown in the figure, the user input may be for changing some or all of the contents of the document.

132, when the second device 112 receives a user input for adding a new content to a document, the second device 112 transmits the edit request information of the document requesting the addition of new content to the server 110, And the server 110 transmits the work screen 13210 of the document to which the new content is added 13220 to the second device 112 according to the received edit request information.

Referring to FIG. 133, when the second device 112 receives a user input for deleting a part of the contents of a document, the second device 112 transmits edit request information of a document requesting deletion of some contents to the server 110 And the server 110 transmits the job screen 13310 of the document whose content is partially deleted (13320) to the second device 112 according to the received edit request information.

Referring again to FIG. 131C, in S13131, the server 110 acquires job history information of the document. For example, the server 110 may acquire job history information of a document at a point of time when the editing of the document ends (that is, when the document is stored). Hereinafter, an example in which the server 110 acquires job history information of a document will be described with reference to FIG.

134 is a diagram for explaining an example in which the server 110 according to some embodiments acquires job history information of a document.

As described above with reference to FIGS. 132 to 133, when the server 110 receives the edit request information of the document, it may add new content to the document or change or delete some or all of the contents of the document. When the server 110 adds a new content to a document, or changes or deletes some or all of the contents of the document, and then stores the document, the server 110 determines that the document has been edited.

When the document is stored after being edited, the server 110 obtains the job history information of the document. In other words, the server 110 acquires the generated information as the document is edited.

For example, after the server 110 executes the document named 'abc.doc' using the second program (?), The server 110 edits the document according to the edit request of the document received from the second device 112 And 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 kilobytes, the server 110 reads 'abc.doc', text, Program, the second device, May 14, 2014 09:11:43, 1084 KB 'as job history information.

On the other hand, as described above with reference to FIG. 106, encryption can be additionally performed and stored in the job history information of a document requiring high security.

Referring again to FIG. 131C, in step S13132, the server 110 links the job history information to the calendar using the time information included in the acquired job history information. For example, the server 110 associates the job history information acquired in S13116 with the calendar in S13117, and further adds 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 the job history information to be displayed on the screen of the device as the indicator to be displayed on the calendar or the indicator to be displayed on the calendar is selected.

In step S13134, the server 110 transmits information to be displayed on the calendar to the first device 111. [

In S13135, the first device 111 outputs a 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 step S13133, the server 110 transmits the information to be displayed on the calendar in step S13134. It is not limited. For example, the server 110 may transmit (e. G., Push) information to be displayed on the calendar to the first device 111, even if there is no transmission request of the first device 111. [

The contents to be described later with reference to S13136 to S13138 correspond to the above contents with reference to S13133 to S13135. In other words, the second device 112 requests the server 110 to transmit the information to be displayed on the calendar, receives the information to be displayed on the calendar from the server 110, and outputs the calendar to the screen. Therefore, even if the contents are omitted in the following description, the above description with reference to S13133 to S13135 can be applied to the contents described later with reference to S13136 to S13138.

At S13136, the second device 112 requests the server 110 to transmit information to be displayed on the calendar.

In step 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 above-described contents with reference to S13132 to S13138 in FIG. 131C will be described later with reference to FIG. 135 to FIG.

135 is a flowchart showing an example in which the server 110 according to some embodiments links job history information of a document to a calendar.

The flowchart shown in FIG. 135 corresponds to the detailed flowchart of S13132 in FIG. 131C.

In step S13510, the server 110 acquires the editing time information of the document included in the obtained job history information 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 obtains '2014.05.14, 09:11:43 pm' from the job history information.

Hereinafter, an example of the job history information acquired by the server 110 will be described with reference to FIGS. 136 to 137. FIG.

136 through 137 are views showing an example of job 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. In other words, the job history information 10810 of the document shown in FIG. 108 means the job history information 10810 generated as the server that received the document work request from the device generates the document. On the other hand, 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 name 13611 of the document.

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 as the server that received the document job request from the device generates the document. On the other hand, 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 a document.

Referring to FIG. 137, the server 110 may arrange the acquired job history information based on the name 13711 of the work device.

Referring again to FIG. 135, in S13520, the server 110 links the job history information to the user's calendar based on the edit time information of the document. Hereinafter, with reference to FIG. 138, an example in which the server 110 links the job history information with the user's calendar will be described.

138 is a flowchart showing an example in which the server 110 according to some embodiments links work history information to a calendar of a user.

In S13810, the server 110 acquires the calendar of the created user. Here, the created user's calendar means a calendar created by linking the job history information acquired by the server 110 to the calendar in S13117 of FIG. 131A.

In step 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 job 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 the job history information acquired in S13131 of FIG. 131C. For example, the server 110 may determine 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 an item indicated by the indicator, and generate an indicator based on the determined item have.

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 an indicator to the area corresponding to the date or time indicating the time when the document is edited in the calendar, and displays the indicator.

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 allowing the user to specify 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.

In the calendar 13911, an indicator 13920 indicating the name of the document can be displayed. For example, in response to a request from the first device 111, if the server 100 edits a document named 'abc.doc' on 2014.05.14, then in calendar 13911, An indicator 13920 indicating 'abc.doc' may be displayed in the area.

Device 13910 may select an indicator 13920 indicating 'abc.doc' according to user input received via user input section 16510. When the indicator 13920 indicating 'abc.doc' is selected, the device 13910 can output the job history information 13921 of the document to the screen. For example, upon request of the second device 112, the server 100 may use the fourth program to send a document named 'abc.doc' with a size of 1084 kilobytes (KB) Quot; abc.doc, text, fourth program, second device, May 14, 2014 at 09:11:43 pm, and 1084 KB, respectively, on the job history information 13921. [ Can be output. On the other hand, the device 13910 can output the job history information 13921 of the document as a separate popup window on the screen.

In the document job history information 13921, indicators 13922 and 13923 capable of outputting a document to the screen of the device 13910 may be displayed. The indicator 13922 may be an original document at the time of document creation or an indicator indicating a document before the current operation, and the indicator 13923 may be an indicator indicating the current editing document.

The indicator 13923 indicating the editing document can be displayed differently from the original document or the indicator 13922 indicating the document before the current operation. For example, in the case of the indicator 13923 of the editing document, a border line can be additionally displayed in the indicator 13922 indicating the original document or the document before the current operation. 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 a popup window separate from the calendar 13911, Alternatively, the document edited by the second device can be output to the screen.

Similarly, in one calendar 13911, a plurality of indicators indicating the name of the document can be displayed. For example, in response to a request from the third device 113, assuming that the server 100 edited a document named 'xyz.doc' in 2014.05.12, the calendar 13911 corresponding to 2014.05.12 An indicator 13930 indicating 'xyz.doc' may be displayed in the area.

The device 13910 may select an indicator 13930 indicating 'xyz.doc' according to the user input received via the user input 16510. When the indicator 13930 indicating 'xyz.doc' is selected, the device 13910 can output the job history information 13931 of the document to the screen. For example, in response to a request from the third device 113, the server 100 may use the fourth program to download a document named 'xyz.doc' having a size of 2387 kilobytes (KB) on May 12, 2014 Assume that it is edited at 09:14:03 AM. The job history information 13931 includes 'xyz.doc, text, fourth program, third device, May 12, 2014 at 09:14:03, 2387 KB' Can be output. On the other hand, the device 13910 can output the job history information 13931 of the document as a separate popup window on the screen.

In the job history information 13931 of the document, indicators 13932 and 13933 capable of outputting the document to the screen of the device 13910 may be displayed. The indicator 13932 may be an original document at the time of document creation or an indicator indicating a document before the current operation, and the indicator 13933 may be an indicator indicating the current editing document.

The indicator 13933 indicating the editing document can be displayed differently from the original document or the indicator 13932 indicating the document before the current operation. For example, in the case of the indicator 13933 of the editing document, a border line may be additionally displayed in the indicator 13932 indicating the original document or the document before the current operation. When the indicator 13932 or 13933 capable of outputting a document according to the user input received through the user input unit 16510 is selected, the device 13910 displays a popup window separate from the calendar 13911, The edited document can be displayed on the screen.

140 is a diagram showing another example of the daily calendar displayed on the screen of the device according to some embodiments.

Referring to FIG. 140, a daily calendar 14011 is output on the screen of the device 14010. FIG. The calendar 14011 shown in FIG. 140 has the same frame as the calendar 13911 shown in FIG. Therefore, the above description with reference to FIG. 139 for the indicators that can be displayed on the calendar 14011 can be similarly applied to FIG.

In the calendar 14011, an indicator 14020 indicating the name of the device can be displayed. For example, in response to a request from the second device 112, if the server 100 edits the document at 2014.05.14, the 'second device' is displayed in the area corresponding to the 2014.05.12 of the calendar 14011 An indicator 14020 indicating the indicator may be displayed.

The device 14010 may select an indicator 14020 indicating 'second device' according to the user input received through the user input unit 16510. When the indicator 14020 indicating 'second device' is selected, the device 14010 can output the job history information 14021 of the document to the screen. For example, upon request of the second device 112, the server 100 may use the fourth program to send a document named 'abc.doc' with a size of 1084 kilobytes (KB) Quot; abc.doc, text, fourth program, second device, May 14, 2014 at 09:11:43 PM, and 1084 KB, respectively, on the job history information 14021. [ Can be output. On the other hand, the device 14010 can output the job history information 14021 of the document as a separate pop-up window on the screen.

Furthermore, in the job history information 14021 of the document, indicators 14022 and 14023 for outputting the document to the screen of the device 14010 may be displayed. The indicator 14022 may be an original document at the time of document creation or an indicator indicating a document before the current operation, and the indicator 14023 may be an indicator indicating the current editing document.

The indicator 14023 indicating the editing document can be displayed differently from the original document or the indicator 14022 indicating the document before the current operation. For example, in the case of the indicator 14023 of the editing document, a border line may be additionally displayed in the indicator 14022 indicating the original document or the document before the current operation. When an indicator 14022 or 14023 capable of outputting a document according to a user input received through the user input unit 16510 is selected, the device 14010 displays a popup window separate from the calendar 14011, The edited document can be displayed on the screen.

Similarly, a plurality of indicators indicating the name of the device may be displayed in one calendar 14011. [ For example, in response to a request from the third device 113, if the server 100 edits a document named "xyz.doc" on 2014.05.12, An indicator 14030 indicating 'third device' may be displayed in the area.

The device 14010 may select the indicator 14030 indicating 'third device' according to the user input received through the user input unit 16510. When the indicator 14030 indicating 'third device' is selected, the device 14010 can output the job history information 14031 of the document to the screen. For example, in response to a request from the third device 113, the server 100 may use the fourth program to send a document named 'xyz.doc' having a size of 2387 kilobytes to the server 110 on May 12, 2014 09:14:03, the job history information 14031 includes 'xyz.doc, text, fourth program, third device, May 12, 2014 at 09:14:03, 2387 KB' Can be output. On the other hand, the device 14010 can output the job history information 14031 of the document as a separate pop-up window on the screen.

In the job history information 14031 of the document, indicators 14032 and 14033 capable of outputting the document to the screen of the device 14010 may be displayed. The indicator 14032 may be an original document at the time of document creation or an indicator indicating a document before the current operation, and the indicator 14033 may be an indicator indicating the current editing document.

The indicator 14033 indicating the editing document can be displayed separately from the original document or the indicator 14032 indicating the document before the current operation. For example, in the case of the indicator 14033 of the edit document, a border line may be additionally displayed in the indicator 14032 indicating the original document or the document before the current operation. When the indicator 14032 or 14033 capable of outputting a document according to the user input received through the user input unit 16510 is selected, the device 14010 displays a popup window separate from the calendar 14011, The edited document can be displayed on the screen.

Figures 141A-141D illustrate a method in which a server generates a document upon request of a first device according to some embodiments, and when the server provides a view of the document and edits the document upon request of the second device, FIG. 7 is a flowchart showing another example of linking the job history information to the calendar of FIG.

S14110 to S14134 in Figs. 141A to 141C are diagrams for explaining the process of linking the job history information to the user's calendar in the case where the server 110 provides the document browsing according to the request of the second device 112 And is the same as S12110 to S12134 in Figs. 121A to 121C. Therefore, a detailed description of S14110 to S14134 in Figs. 141A to 141C will be omitted below.

S14135 to S14152 in FIG. 141C to FIG. 141D illustrate the processes in which the server 110 associates the job history information with the user's calendar when the server 110 edits the document according to the request of the second device 112 And is the same as S13121 to S13138 in Figs. 131B to 131C. Therefore, a detailed description of S14135 to S14152 in Figs. 141C to 141D will be omitted below.

142 through 143 are views showing examples of calendars output to the screen of the device according to some embodiments.

142, an example of the calendar 14220 output on the screen of the device 14210 is shown. In FIG. 142, monthly calendar 14220 is shown as being output on the screen of device 14210 for convenience of explanation, but it is not limited thereto.

If the server 100 has performed operations on a plurality of documents on the same date, the calendar 14220 may be displayed with an indicator 14230 indicating the number of documents in which the operation has been performed. For example, assuming that the server 100 performed a total of nine documents on 2014.01.10, the calendar 14220 indicates that an operation was performed on nine documents in the area representing 2014.01.10. An indicator 14230 may be displayed.

The device 14210 may select an indicator 14230 indicating the number of documents that have been performed according to the user input received via the user input 16510. [ When the indicator 14230 indicating the number of documents on which the job has been performed is selected, the device 14210 can output a list 14240 of documents on which the job has been performed.

When one of the documents 14241 included in the list 14240 is selected after the list 14240 of the documents on which the job has been performed, the device 14210 displays the job history information 14250 of the selected document You can print on the screen. In the job history information 14250 of the document, indicators 14251 and 14252 capable of outputting a document to the screen of the device 14210 may be displayed. Here, the indicator 14251 may be an original document at the time of document creation or an indicator indicating a document before the current operation, and the indicator 14252 may be an indicator indicating the current editing document.

Referring to FIG. 143, another example of the calendar 14320 is displayed on the screen of the device 14310. The document list 14340 in the calendar 14320 shown in FIG. 143 may show a different shape from the document list 14240 in the calendar 14220 shown in FIG. For example, the document list 14340, the job 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 showing still another example of the calendar displayed on the screen of the device according to some embodiments.

144, an example of the calendar 14420 output on the screen of the device 14410 is shown. In FIG. 144, for convenience of explanation, the monthly calendar 14420 is displayed 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 in response to a request by the same device on the same date, the calendar 14420 displays an indicator 14430 indicating the number of documents on which the operation has been performed . For example, in response to a request from the first device 111, assuming that the server 100 has performed an operation on a total of three documents at 2014.01.11, An indicator 14430 indicating that the operation has been performed on three documents may be displayed.

The device 14410 may select the indicator 14430 according to the user input received via the user input 16510. [ If the indicator 14430 is selected, the device 14410 may output a list 14440 of documents on which the job has been performed.

If one of the documents 14441 included in the list 14440 is selected after the list 14440 of the documents on which the job has been performed, the device 14410 displays the job history information 14450 of the selected document You can print on the screen. In the job history information 14450 of the document, indicators 14451 and 14452 capable of outputting the document to the screen of the device 14410 may be displayed. Here, the indicator 14451 may be an original document at the time of document creation or an indicator indicating a document before the current operation, and the indicator 14452 may be an indicator indicating the current editing document.

Referring to FIG. 145, another example of the calendar 14520 is displayed on the screen of the device 14510. FIG. The document list 14540 in the calendar 14520 shown in FIG. 145 may represent a different shape from the document list 14440 in the calendar 14420 shown in FIG. For example, the document list 14540, the job history information 14550, and the indicators 14530, 14551, and 14552 that can be output to the screen of the device 14510 can be output in various shapes or colors.

FIG. 146 is a diagram for explaining an example in which a mode of a calendar according to some embodiments is switched. FIG.

Referring to Figure 146 (a), an example of the first mode calendar 14620 output on the screen of the device 14610 is shown. Here, the first mode calendar 14620 can be associated with information related to the daily life of the user. For example, the first mode calendar 14620 may be interlocked with information about the schedule or schedule of the user. Also, the first mode calendar 14620 may be associated with history information that the user has used the function of the device 14610. [ For example, the first mode calendar 14620 may include a history of a user making a call using the device 14610, a history of shooting using a camera provided in the device 14610, a memo program installed in the device 14610, A history of generating a memo using the device 14610, a history of sending or receiving a message or an e-mail using the device 14610, a history using the SNS service using the SNS program installed in the device 14610, and the like.

Referring to Figure 146 (b), an example of the second mode calendar 14630 output on the screen of the device 14610 is shown. Here, the second mode calendar 14630 can be interlocked with the job history information of the document.

The calendars 14620 and 14630 output to the device 14610 may be displayed with indicators 14640 and 14650 capable of switching modes of the calendars 14620 and 14630. [ For example, the screen of the device 14610 may be displayed with an indicator 14640 requesting to output the first mode calendar 14620 and an indicator 14650 requesting to output the second mode calendar 14630 have.

The first mode calendar 14620 output to the device 14610 may also display schedule information related to the job history information displayed on the second mode calendar 14630. [ For example, assume that a user has worked on the "2013 Performance Reporting .doc" document on December 23, 2013, and that there is a meeting date associated with the "2013 Performance Reporting .doc" document on January 3, 2014 do. At this time, an indicator informing to review '2013 annual report .doc' may be displayed in the January 2, 2014 field on the first mode calendar 14620.

Hereinafter, referring to Figs. 147 to 149, when the users of the devices 110 are different from each other and the server 100 performs the document operation based on the request of the devices 110, An example of linking the job history information to the user's calendar will be described.

147 is a view for explaining an example in which a server cooperates with job history information on a user's calendar in the case where the users of the devices according to some embodiments are different from each other and the server performs the document operation based on the request of the devices to be.

Referring to Figure 147, the system 1 includes a server 100 and devices 110. Here, each of the devices 110 means a device of another user. 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, the Nth device 114 is the device of the M user 122 Device.

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

The server 100 in Fig. 147 executes a program used for document work installed in the server 100. Fig. therefore. The first user 120 can perform the document operation by accessing the server 100 from the device even if the device is not provided with a program used for document operation. The server 100 can obtain the job history information of the document from the server 100 without receiving the job history information of the document from the devices 110 because the server 100 performs the document job.

On the other hand, the devices 110 in FIG. 101 request the server 100 to perform a document operation without performing a document operation. 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 the document. In the same manner, the second device 112 of the second user 121 to the Nth device 114 of the third user 122 requests the server 100 to work on the document.

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

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 a 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 as an indicator to be displayed on the calendar or an indicator to be displayed on the calendar is selected.

At this time, the server 100 may transmit the information 140 to be displayed on the calendar only to the device 110 that requested the transfer of the information 140 to be displayed on the calendar. For example, the first device 111 executes a program for outputting a calendar, and authenticates the server 100 to the first user (e.g., the first user 111) by authenticating that the user is the first user based on the user account entered through the user input unit 16510 120 to be displayed on the calendar of the user.

On the other hand, the server 100 may automatically transmit (e. G., Push) the information 140 to be displayed on the calendar to the first device 111, even if there is no request from the first device 111 . For example, if there is a history that the first device 111 has previously requested the transmission of the information 140 to be displayed on the calendar of the first user 120, The information 140 to be displayed on the calendar of the first user 120 can be automatically transmitted even if there is no request from the first user 120.

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

148 is a flowchart showing an example in which a server according to some embodiments links work history information to a calendar of a user.

In step S14810, the server 100 acquires job history information of a document that has been processed in the server 100 at the request of a plurality of users. In other words, the server 100 receives a document job request from devices of a plurality of users, performs a document job, and obtains job history information.

In S14820, the server 100 links the acquired job history information to at least one of the plurality of users 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, if the server 100 generates a document 'abc.doc' at 12:28:04 pm on May 12, 2014 at the request of the first device 111 of the first user 120, (100) generates an indicator to be displayed at 2014.05.12 on the calendar of the first user (120), and determines an operation history information to be output on the screen of the first device (111) . At this time, as described above with reference to FIG. 1, only a part of the job history information acquired by the server 100 in S14810 can be linked to the user's calendar.

149, when the server 100 works on a document according to a document work request of the first device 111, the server 100 determines whether the first user 120 and the second user 121 An example of linking the job history information to the calendar will be described.

149 is a flowchart illustrating an example in which a server interlocks job history information with a calendar of a first user when a server performs a document job according to a document job request of a first device according to some embodiments.

In FIG. 149, for convenience of description, the server 100 has been shown to work on a document by a document work request of 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. There is also 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 to the server 100 information requesting a document operation. For example, the user of the first device 111 executes and logs in the fourth program, so that the first device 111 can transmit information to the server 100 requesting the document operation. At this time, the user of the first device 111 may log in the fourth program using various methods including a method of inputting an ID / password.

In S14911, the server 100 operates on the document based on the information received from the first device 111. [ For example, the server 100 can execute a program used for document operation on the server 100, and can work on the document using a program executed on the server 100. [ Assuming that the document to be processed by the server 100 is 'abc.doc' and that the program used for creating, browsing or editing 'abc.doc' is the fourth program, the server 100 transmits the fourth program Run, and create, view, or edit 'abc.doc'.

In step S14912, the server 100 transmits the information about the job screen of the document to the first device 111. [ For example, the server 100 can transmit information on the work screen of the document to the first device 111 every time the document is operated, based on the information received from the first device. In other words, the server 100 can use the program executed in the server 100 to transmit to the first device 111 information regarding the work screen of the document to be changed each time the document is operated.

In S14913, the first device 111 outputs the job screen of the document. For example, the first device 111 can output a job screen of a document based on information on a job screen of the document transmitted from the server 100. [

In S14914, the server 100 acquires job history information of the document. For example, the server 100 can acquire job history information of a document at the time when the 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 job history information in the storage space corresponding to the account of the user of the first device 111. [

In S14915, the server 100 links the acquired job history information to the user's calendar using the time information included in the acquired job history information. For example, if the server 100 stores 'abc.doc' at 12:28:04 pm on May 12, 2014, 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 displayed on the screen of the device, by selecting an indicator to be displayed on the calendar or an indicator to be displayed on the calendar.

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 a calendar on the screen. For example, the first device 111 may output a calendar on which an indicator transmitted from the server 100 is displayed.

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 the job history information to be displayed on the screen of the device as the indicator to be displayed on the calendar or the 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 a calendar on the screen. For example, the first device 111 may output a calendar on which an indicator transmitted from the server 100 is displayed.

Hereinafter, with reference to FIGS. 150 to 161, when the server 100 authorizes a document based on a request of the devices 110, the server 100 transmits the job history information to the user's calendar An example is given.

150 is a diagram for explaining an example in which a server cooperates with job history information on a user's calendar when devices according to some embodiments perform co-authoring of documents.

87, the system 1 of FIG. 87 utilizes a program installed in the device 111, 112 or 114, but the system 1 of FIG. Is connected to the server 100 and uses the fourth program installed in the server 100. [ Examples of the fourth program may be cloud-based documenting programs such as MS OFFICE 365, GOOGLE DOCS, and the like.

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 the devices used by the first user 120, the second user 121, and the M-th user 122, as in the example shown in Fig. Alternatively, all the devices 110 may correspond to the devices used by any one user (e.g., the first user 120), as in the other example shown in FIG. That is, the number of users of devices using the devices 110 is not limited by any one.

The first device 111 transmits a first document creation request 15040 to the server 100 using the fourth program. Also, the second device 112 transmits a second document creation request 15040 to the server 100 using the fourth program, and the Nth device 114 uses the fourth program to transmit the creation of the Nth document (15040) to the server (100). Accordingly, the server 100 can perform generation (15010) of the first document to the Nth document.

In this manner, each of the first device 111 to the N-th device 114 performs cooperation authoring of the document by transmitting requests for generating the first document to the N-th document to the server 100 (15040) .

The server 100 combines the first document to the Nth document received from the devices 110 (15020), and generates a single document 15001 that is the result of the co-authoring (15030). Therefore, the contents of the first document, the contents of the second document, and the contents of the Nth document can all be included in the contents of the single document 15001. [

The server 100 may transmit the generation history information of the single document 15001 to each of the devices 110 participating in the co-authoring of the single document 15001 when the single document 15001 is generated. 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 a 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 as an indicator to be displayed on the calendar or an indicator to be displayed on the calendar is selected. Here, the job history information may include the generation history information of the single document 15001. [

At this time, the server 100 may transmit the information 15050 to be displayed on the calendar only to the devices 110 that request the transmission of the information 15050 to be displayed on the calendar. For example, the first device 111 executes a program for outputting calendars, authenticates the first user 120 based on the user account input through the user input unit 16510, 1 user 120 to transmit information 15050 to be displayed on the calendar.

On the other hand, the server 100 may automatically transmit (for example, push) the information 15050 to be displayed on the calendar to the first device 111, even if there is no request from the first device 111 . For example, if there is a history that the first device 111 has previously requested transmission of the information 15050 to be displayed on the calendar of the first user 120, then the server 100 may subsequently access the first device 111, The information 15050 to be displayed on the calendar of the first user 120 can be automatically transmitted even if there is no request from the first user 120. [

151 is a flowchart illustrating an example in which a server according to some embodiments links work history information to a calendar of a user.

In S15101, the server 100 generates documents such as a first document, a second document and an Nth document in response to a request from each of the plurality of devices 110, for example.

In S15102, the server 100 acquires job history information of each of the documents.

At S15103, the server 100 generates a final document based on the connection relationship of the acquired documents. Here, the final document may correspond to the single document 15001 described in FIG. The connection relationship of the documents means the order in which the seed documents to be combined into the final document are to be linked, such as the order of the table of contents, the order of the storage date and time, and the like.

In S15104, the server 100 links the received job history information to the calendar of the user using the time information included in the obtained job history information. Here, the time information means information indicating the time when the device worked on the document. For example, if the first device 111 sends a document called &quot; abc.doc &quot; The server 100 generates an indicator to be displayed on the calendar of the user of the first device 111 on the calendar of December 4, 2015, and the indicator displayed on the calendar 2014.05.12. Is selected The job history information to be output to the screen of the first device 111 can be determined.

Hereinafter, referring to FIGS. 152A to 152C, when the first device 111 and the second device 112 perform a co-authoring of a document, the server 100 may associate the job history information with the user's calendar An example is given.

FIGS. 152A to 152C are flowcharts illustrating an example in which a server cooperates with a user's calendar with job history information when a first device and a second device according to some embodiments perform co-authoring of a document.

152A to 152C show only the first device 111 and the second device 112 for convenience of explanation, there is no limitation on the number of devices. Assuming 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, Lt; / RTI &gt;

In S15200, the first device 111 executes a server connection program. In order for the user to request the server 100 to generate the first document, the first device 111 may execute the server connection program. Here, the server connection program may correspond to the fourth program. For example, the user of the first device 111 can execute a server connection program and input his / her own 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 the server connection program. Here, the server connection program may correspond to the fourth program. For example, the user of the second device 112 may execute a server connection program and input his / her own ID / password.

In S15202, the first device 111 transmits a request for generation of the first document to the server 100. [

In S15203, the server 100 generates a first document.

At S15204, the server 100 stores the first document.

In S15205, the server 100 transmits information on the first document to the first device 111. [

In S15206, the first device 111 outputs the first document to the screen.

In S15207, the server 100 generates job history information of the first document. For example, the job history information may include at least one of a title of a document on which an operation is performed, a type of the document, a time at which the document operation was performed, a device name for performing the document operation, a user of the device, It can include the type of work. For example, the server 100 may store the acquired job history information in the storage space corresponding to the account of the user of the first device 111 and the storage space corresponding to the account of the user of the second device 112 .

In step S15208, the server 100 links the job history information to the user's calendar 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 execute the calendar output program installed in the first device 111, and may request the server 100 to transmit information to be displayed on the calendar after performing authentication of the user .

At 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 execute a calendar output program installed in the first device 112, and may request the server 100 to transmit information to be displayed on the calendar after performing authentication of the user .

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

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

In S15213, the first device 111 outputs a calendar on the screen.

In S15214, the second device 112 outputs a calendar on the screen.

In S15215, the second device 112 transmits a request for generation of the second document to the server 100. [

In S15216, the server 100 generates a second document.

In S15217, the server 100 transmits information on 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 to 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 the storage space corresponding to the account of the user of the first device 111 and the storage space corresponding to the account of the user of the second device 112 .

In S15221, the server 100 determines the connection relationship between the first document and the second document. Here, the connection relationship between the first document and the second document means a sequence in which the first document and the second document are connected to combine to form a final document, and the connection between the table of contents of the first document and the table of contents of the second document, The storage date and time of the first document, and the post-storage date and time of the second document.

In S15222, the server 100 combines the first document and the second document according to the determined connection relationship to generate a final document.

In S15223, the server 100 stores the final document.

In step S15224, the server 100 links the job history information to the user's calendar 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 execute the calendar output program installed in the first device 111, and may request the server 100 to transmit information to be displayed on the calendar after performing authentication of the user .

At 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 execute a calendar output program installed in the second device 112, and may request the server 100 to transmit information to be displayed on the calendar after performing authentication of the user .

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

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

In Fig. 152C, when the first device 111 and the second device 112 respectively request the server 100 to transmit information to be displayed on the calendar in S15225 and S15226, the server 100 in the server 1000 in the steps S15227 and S15228 The information to be displayed is transmitted to each of the first device 111 and the second device 112, but 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, push).

In S15229, the first device 111 outputs a calendar on the screen.

At S15230, the second device 112 outputs the calendar to 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 &quot; https://samsung-office.com &quot;.

The user can create texts using the fourth program 15301 executed in the first device 111. [ For example, the first device 111 transmits to the server 100 a request to generate some contents of the patent specification having the name of the invention of "METHOD FOR CONTROLLING APPLICATION" created by the user through the fourth program 15301 . When the creation of the patent specification is completed, the first device 111 can store the first document having the 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 &quot; draft specification 1.doc &quot; is, for example, &quot; 2014. May 14, AM 09:11:43 &quot;.

On the other hand, to describe the second device 112, the second device 112 executes the fourth program 15302 by accessing the web page &quot; https://samsung-office.com &quot;.

The user can create texts using the fourth program 15302 in the second device 112. [ For example, the second device 112 may transmit to the server 100 a request to generate claims of the patent specification written by the user via the fourth program 15302. [ When the creation of the claims of the patent specification is completed, the second device 112 can store the second document having the web address of &quot; https://samsung-office.com/draft specification 2.doc &quot; in the server 100 have. Here, the storage date and time of the second document of &quot; draft specification 2.doc &quot; is, for example, &quot; 2014. May 20, PM 08:46:11 &quot;.

154 is a diagram for explaining an example of job history information of documents and documents generated in the server according to some embodiments.

The server 100 stores the first document 15401 &quot; draft specification 1.doc &quot; together with the meta information of the first document 15401 &quot; draft specification 1.doc &quot;, and the second document 15401 15402) &quot; draft specification 2.doc &quot; together with the meta information of the second document 15402 &quot; draft specification 2.doc &quot;.

The meta information corresponds to job history information, and may include job date and time information, a device name, a document creator, and a table of contents information of a document.

On the other hand, the first document 15401 "draft specification 1.doc" and the second document 15402 "draft specification 2.doc" are generated for the co-authoring of the first device 111 and the second device 112 Documents.

FIG. 155 is a view for explaining an example of a process of combining documents by co-authoring devices according to some embodiments.

The first device 111, the second device 112 and the N device 114 transmit to the server 100 a request to generate a document for collaborative authoring using the fourth program. Specifically, the first device 111 stores the storage date &quot; 2014. 0514, AM 09:11:43 &quot; The second device 112 may transmit the creation request of the document 15501 related to the contents of the sales history &quot; 2014. 05.12, PM 12:28:04 &quot; , The N-th device 114 may transmit a request for generation of the document 15502 relating to the content of the sales history &quot; 201.4. 05 &lt; / RTI &gt; 28, PM 08:21:11 &quot; A request to generate a document (15503) regarding the content of &quot; sales history of 05. 28 &quot;

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, it is assumed that the connection relationship is based on the storage date and time of the documents 15501, 15502, and 15503.

The document 15501 is the first to be compared with the other documents 15502 and 15503, the stored date &quot; 2014. 05. 14, AM 09:11:43 &quot;, and thus has the first priority. The document 15502 includes a storage date &quot; 2014. 05. 12, PM 12:28:04 &quot;, and thus has a second priority. Finally, the document 15503 has a save date &quot; 2014. 05. 28, PM 08:21:11 &quot;, and therefore has the n-th priority. Accordingly, the server 100 can determine that the connection relationship 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 co-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 relationships determined for the documents 15501, 15502, and 15503. That is, the server 100 transmits the documents 15501, 15502, and 15503 in the order of the document having the first priority 15501, the document having the second priority 15502, and the document having the nth priority 15503, The final document 15510 can be generated.

Eventually, the server 100, by co-authoring, 02. 14 Sales Breakdown>, <2014. Revenue Breakdown of 05. 12> and <2014. 05 &gt; 28 > in the order of the contents of the last document (15510).

156 is a diagram for explaining another example of a process of combining documents by co-authoring devices according to some embodiments.

The first device 111, the second device 112 and the N device 114 transmit to the server 100 a request to generate a document for collaborative authoring using the fourth program. In FIG. 156, the case where the first device 111, the second device 112, and the N-th device 114 jointly author a document of the patent specification will be described as an example. Generally, the order of the contents is defined in the patent specification. For example, the order of a large table of contents in the patent specification is known to be "BACKGROUND", "SUMMARY", ..., "DETAILED DESCRIPTION", ..., "WHAT IS CLAIMED IS:" .

The first device 111 may send a request to the server 100 to generate a document 15601 "draft patent specification 1.doc" relating to the contents of the "BACKGROUND" and "SUMMARY" of the patent specification, 112 may send a request to the server 100 to generate a document 15602 "draft patent specification 2.doc" relating to the contents of the "DETAILED DESCRIPTION" in the patent specification, and the N-th device 114 may transmit a " Quot; draft patent specification 3.doc &quot; relating to the content of &quot; WHAT IS CLAIMED IS: &quot;

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 is described as being based on the table of contents included in the documents 15601, 15602, and 15603.

The document 15601 has the first priority because it contains the contents of the most advanced table of contents "BACKGROUND" and "SUMMARY" in comparison with the other documents 15602 and 15603. The document 15602 has the second priority because it contains the contents of the next order of contents &quot; DETAILED DESCRIPTION &quot;. Finally, the document 15603 has the nth priority since it contains the contents of the next order of contents &quot; WHAT IS CLAIMED IS: &quot;. Accordingly, the server 100 can determine that the connection relationship of the documents 15601, 15602, and 15603 is in the order of the document 15601, the document 15602, and the document 15603. [

The server 100 creates a final document 15610 as a result of the co-authoring of the first device 111, the second device 112 and the N-th device 114. Specifically, the server 100 can 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 transmits the documents 15601, 15602, and 15603 in the order of the document with the first priority 15601, the document with the second priority 15602, and the document having the nth priority 15603, The final document 15610 can be generated.

In the end, the server 100 creates a patent specification in which contents of "BACKGROUND", "SUMMARY", ..., "DETAILED DESCRIPTION", ..., "WHAT IS CLAIMED IS: Lt; RTI ID = 0.0 &gt; 15610 &lt; / RTI &gt;

FIGS. 157A to 157C are flowcharts illustrating an example in which, when a first device and a second device according to some embodiments perform a co-authoring of a document, the server cooperates with the user's calendar with the job history information.

In FIGS. 157A to 157C, only two of the first device 111 and the second device 112 are shown for convenience of explanation, but there is no limitation on the number of devices. Assuming 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, Lt; / RTI &gt;

In S15700, the first device 111 executes a server connection program. In order for the user to request the server 100 to generate the first document, the first device 111 may execute the server connection program. Here, the server connection program may correspond to the fourth program. For example, the user of the first device 111 can execute a server connection program and input his / her own 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 last document to be generated by the server 100 in S15720 is described, or a document in which only some pages among the entire pages of the final document are described.

As an example, assuming that the final document is a document composed of the contents of the 'meeting purpose', the 'preparation of the meeting', and the 'contents of the meeting discussion' and contents of the respective contents, May be the described 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 one or two pages of the final document are described.

In S15703, the server 100 stores the first document.

In S15704, the server 100 transmits information on 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 at least one of a title of a document on which an operation is performed, a type of the document, a time at which the document operation was performed, a device name for performing the document operation, a user of the device, It can include the type of work. For example, the server 100 may store the obtained job history information in the storage space corresponding to the account of the user of the first device 111. [

In S15707, the server 100 links the job history information to the user's calendar 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 execute the calendar output program installed in the first device 111, and may request the server 100 to transmit information to be displayed on the calendar after performing authentication of 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 execute a calendar output program installed in the first device 112, and may request the server 100 to transmit information to be displayed on the calendar after performing authentication of the user .

In S15710, the server 100 transmits the 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 the server connection program. Here, the server connection program may correspond to the fourth program. For example, the user of the second device 112 may execute a server connection program and input his / her own ID / password.

At S15713, the second device 112 transmits a job request for the second document to the server 100. [

Here, the job of the second document may include the creation of the second document, the editing of the second document, or the viewing of the second document.

At S15714, the server 100 works on the second document based on the first document. Here, the second document means a document in which the content of the table of contents included in the final document to be generated by the server 100 in S15720 is described, or a document in which only some of the entire pages of the final document are described.

As an example, assuming that the final document is a document composed of the contents of the 'purpose of meeting', 'preparation of meeting', and 'content of meeting discussion' and content of each table of contents, Quot; contents can be generated.

As another example, assuming that the final document is a document composed of 1 to 10 pages, the server 100 may generate a document describing contents of 3 to 5 pages of the final document.

In addition, the server 100 may edit the first document generated in S15702. For example, in S15702, assuming that the server 100 has created a document in which contents of one or two pages are written, the server 100 may modify, add or delete contents of one or two pages in S15714.

In S15715, the server 100 stores the second document.

At 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 at least one of a title of a document on which an operation is performed, a type of the document, a time at which the document operation was performed, a device name for performing the document operation, a user of the device, It can include the type of work. For example, the server 100 may store the obtained job history information in the storage space corresponding to the account of the user of the second device 112. [

In S15718, the server 100 outputs the second document to the screen.

In S15719, the server 100 determines the connection relationship between the first document and the second document. Here, the connection relationship between the first document and the second document means a sequence in which the first document and the second document are connected to combine to form a final document, and the connection between the table of contents of the first document and the table of contents of the second document, The storage date and time of the first document, and the post-storage date and time of the second document.

In S15720, the server 100 combines the first document and the second document according to the determined connection relationship to generate a final document.

In S15721, the server 100 stores the final document.

In step S15722, the server 100 links the job history information to the user's calendar 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 execute the calendar output program installed in the first device 111, and may request the server 100 to transmit information to be displayed on the calendar after performing authentication of 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 execute a calendar output program installed in the second device 112, and may request the server 100 to transmit information to be displayed on the calendar after performing authentication of 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 the first device 111 and the second device 112 respectively request the server 100 to transmit information to be displayed on the calendar in S15723 and S15724, the server 100 in the steps S15725 and S15726 transmits the information to the calendar The information to be displayed is transmitted to each of the first device 111 and the second device 112, but 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, push).

In S15727, the first device 111 outputs a calendar on the screen.

In S15728, the second device 112 outputs the calendar to the screen.

FIG. 158 is a view for explaining another example of a process of combining documents by co-authoring 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 co-authoring to the server 100 using the fourth program. In FIG. 158, the case where the first device 111, the second device 112, and the N-th device 114 jointly author the minutes is described as an example. In FIG. 158, it is assumed that the order of the table of minutes is specified in the order of <purpose of meeting>, <preparations for meeting> 15802 and <contents of discussion 15803>. Further, 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 the manager of the company, and the first device 111 is a device used by a company employee.

The president can transmit a request to the server 100 to generate a document 15801 in which the table of contents of the minutes is listed using the second device 112 owned by the president in order to hold a meeting for a meeting purpose for a specific subject.

Information regarding the document 15801 stored in the server 100 can be transferred to the Nth device 114 owned by the manager and the first device 111 owned by the employee as described above with reference to Figures 157A through 157C have.

If the purpose of the meeting is determined by the president, the contents of the other items of the minutes (15802) and 15803 (15803) may be prepared by the president's subordinates.

When the information about the document 15801 is transmitted to the N-th device 114 owned by the general manager through the server 100, the manager uses the N-th device 114 to perform the &quot; Preparation for Meeting &quot; 15802 And may transmit the creation request of the document 15804 to the server 100. [ Further, when the information about the document 15801 is transmitted to the first device 111 owned by the employee via the server 100, the employee uses the first device 111 to display the contents of the discussion 15803 To the server 100, a request to create a document 15805 related to the document.

The server 100 determines the connection relationship of the documents 15801, 15804, and 15805. In FIG. 158, the connection relationship is described as being based on the table of contents included in the documents 15801, 15804, and 15805.

The document 15801 has the first priority because it contains the content of the <meeting purpose> which is the most advanced table in comparison with the other documents 15804 and 15805. The document 15804 has the second priority because it contains the content of the <preparation of meeting> 15802, which is the table of contents of the next step. Finally, the document 15805 has the nth priority because it contains the content of the <meeting content> 15803 which is the table of contents of the next order. Accordingly, the server 100 can determine that the connection 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 the final document 15810 as a result of the co-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 connection relationship determined for the documents 15801, 15804, and 15805. That is, the server 100 transmits the documents 15801, 15804, and 15805 in order of the document with the first priority 15801, the document with the second priority 15804, and the document having the nth priority 15805, The final document 15810 can be generated.

Eventually, the server 100 creates a final document 15810 of the minutes in which the contents of the <purpose of meeting>, <preparation of meeting> 15802 and <contents of discussion 15803> Lt; / RTI &gt;

On the other hand, the server 100 may determine that the connection relationship of the documents 15801, 15804, and 15805 is based on the rank of the creator who created the documents 15801, 15804, and 15805.

Specifically, the document 15801 has a first priority because it is created by the president who has the highest rank compared to the other documents 15804 and 15805. The document 15804 has a second priority because it was created by the general manager who is in the next order of rank. Finally, the document 15805 has an nth priority since it was created by an employee in the next order of rank. Accordingly, the server 100 can determine that the connection 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 transmits the documents 15801, 15804, and 15805 in order of the document with the first priority 15801, the document with the second priority 15804, and the document having the nth priority 15805 ), The final document 15810 can be generated.

Figure 159 is a diagram for explaining an example of generating a final document by co-authoring of a first device, a second device, and an Nth device according to some embodiments.

In order to perform the co-authoring, the first device 111 transmits a request for generation of the first document 15901 "draft 1.doc" to the server 100, and the second device 112 transmits the second document 15902 ) Draft 2.doc to the server 100 and the N-th device 114 transmits a request for generating the Nth document 15903 "draft N.doc" to the server 100.

The server 100 determines the connection relationship of 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 to be combined to the final document 15910, Has already been described in the above examples.

The server 100 combines the first document 15901 to the Nth document 15903 according to the determined connection relationship to generate the final document 15910 and stores the generated final document 15910. [

160 is a diagram illustrating an example of displaying the history of documents generated by a co-author in a monthly calendar displayed on a screen of a device according to some embodiments.

Referring to FIG. 160, a monthly calendar 16020 is displayed on the screen of the device 16010. The calendar 16020 may be displayed with a &quot; DELTA &quot; shaped indicator 16030 indicating a co-authoring document. Indicator (16030) "△" The number inside the shape may indicate how many documents were combined by co-authoring. For example, the indicator 16030 displayed on calendar 16020 at 2014.05.04. May indicate that the three documents were combined by co-authoring.

The device 9710 may select the "Δ" shaped indicator 16030 according to the user input received via the user input 16510. When the indicator 16030 is selected, the device 16010 can output the job history information 16040 of the co-authoring document to the screen.

The job history information 16040 of the co-authoring document includes information on the file name &quot; workshop.doc &quot; of the co-authoring document, documents "workshop_1.doc", "workshop_2.doc" .doc &quot; The job history information 16040 of the co-authoring document also includes information on the creation date and time of each of the documents "workshop_1.doc", "workshop_2.doc", and "workshop_3.doc" . For example, the job history information 16040 of the co-authoring document indicates that the creation date and time of &quot; workshop_2.doc &quot; 12. 26, AM 11:40:39 &quot;, and the device that created &quot; workshop_2.doc &quot; may include the information that the first device 111 is.

Device 16010 may select item 16050 of &quot; workshop_2.doc &quot;, which is part of the collaborative authoring document, according to the user input received via user input 16510. [ When the item 16050 is selected, the device 16010 can output the job history information 16060 of the document &quot; workshop_2.doc &quot; corresponding to the item 16050 to the screen.

On the other hand, the operation history information about the co-authoring document can be displayed for other directors 16070 as described above.

161 is a diagram showing another example of displaying the history of documents generated by the co-author in the monthly calendar displayed on the screen of the device according to some embodiments.

Referring to FIG. 161, a monthly calendar 16120 is output on the screen of the device 16110. FIG.

The device 16110 may select the indicator 1630 of the &quot; DELTA &quot; shape displayed on 2014.01.06. According to the user input received via the user input section 16510. [ When the indicator 16130 is selected, the device 16110 displays the indicator 16140 on the date of 2014.01.01. And the indicator 16150 on the date of 2014.01.28.

When the indicator 16130 is selected, the indicator 16140 and indicator 16150 displayed together with the indicator 16130 are those marked to identify documents co-authored with the document specified in the indicator 16130. That is, the document specified in the indicator 16130 displayed on 2014.01.06., Together with the document specified in the indicator 16140 indicated in 2014.01.01. And the indicator 16150 indicated in 2014.01.28. It is a used document.

On the other hand, when the indicator 16130 is selected, the device 16110 can output the job history information 16160 of the co-authoring document to the screen.

The job history information 16160 of the co-authoring document includes information about the file name &quot; party.doc &quot; of the co-authoring document and the documents &quot; party_1.doc &quot;, &quot; party_2.doc & .doc &quot; The job history information 16160 of the co-authoring document also includes information on the date and time of generation of each of the documents "party_1.doc", "party_2.doc", and "party_3.doc" . For example, the job history information 16160 of the co-authored document indicates that the generation date and time of "party_2.doc" is "2014.01.06. PM 08:14:56" and the device that generated "party_2.doc" And a third device 113, for example.

Device 16110 may select item 16170 of &quot; party_2.doc &quot;, which is part of the collaborative authoring document, in accordance with the user input received via user input 16510. [ When the item 16170 is selected, the device 16110 can output the job history information 16180 of the document &quot; party_2.doc &quot; corresponding to the item 16170 to the screen.

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 of the devices 110 An example in which the device performing the function of the server 100 interlocks the job history information with the user's calendar will be described.

FIG. 162 is a flowchart illustrating an operation of a server that performs a function of a server when at least one of a plurality of devices according to some embodiments corresponds to a server, Is a diagram for explaining an example of linking job history information to a calendar of a user.

162, the system 1 includes a first device 111 and a second device 112 to an N-th device 114. Here, the first device 111 means a device that performs the function of the server 100 in Fig.

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

The first device 111 links the generated job history information to the user's calendar. Then, the first device 111 transmits information to be displayed on the calendar to at least one of the second device 112 to the N-th device 114. Here, the information to be displayed on the calendar means information to be displayed on the output calendar when a 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 as an indicator to be displayed on the calendar or an indicator to be displayed on the calendar is selected.

At this time, the first device 111 can transmit information to be displayed on the calendar only to the device requesting transmission of the information to be displayed on the calendar from the second device 112 to the N-th device 114. For example, the second device 112 executes a program for outputting a calendar and authenticates the first device 111 to the user's calendar by authenticating that the user is a user based on the user account entered through the user input unit 16510 And may request transmission of information to be displayed.

On the other hand, the first device 111 may automatically transmit (e. G., Push) information to be displayed on the calendar to the second device 112, even if there is no request from the second device 112. [

Hereinafter, with reference to FIG. 163, an example in which the first device 111 interlocks the operation history information with the user's calendar in the case where the second device 112 and the third device 113 perform the document operation do.

163 is a flowchart showing an example in which the first device associates the job history information with the user's calendar when the second device and the third device 113 according to some embodiments perform document work.

In FIG. 163, for convenience of description, the first device 100 operates the document according to the document work request of the second device 112, but the present invention is not limited thereto. In other words, there is no limit to the number of devices requesting document work. There is also no limit to the number of devices that request the first device 111 to transmit information to be displayed on the calendar.

In step S16310, the second device 112 transmits information requesting the document operation to the first device 111. [ For example, the user of the second device 112 executes and executes the fourth program, so that the second device 112 can transmit information requesting the document operation to the first device 111. [ At this time, a method of logging in the first device 111 by the user of the second device 112 may include various methods including a method of inputting an ID / password.

In step S16311, the first device 111 operates on the document based on the information received from the second device 112. [ For example, the first device 111 may execute a program used for document operation in the first device 111, and may use a program executed in the first device 111 to work on the document. Assuming that the document to be processed by the first device 111 is 'abc.doc' and that the program used for creating, browsing or editing 'abc.doc' is a fourth program, the first device 111 You can run the fourth program and create, view or edit 'abc.doc'.

In step S16312, the first device 111 transmits information about the job screen of the document to the second device 112. [ For example, each time the first device 111 works on a document based on information received from the second device, it may transmit information about the working screen of the document to the second device 112. [ In other words, the first device 111 can use the program executed in the first device 111 to transmit to the second device 112 information about the job screen of the document to be changed each time the document is operated .

In step S16313, the second device 112 outputs the job screen of the document. For example, the second device 112 can output a work screen of a document based on information about a work screen of the document transmitted from the first device 111. [

In step S16314, the first device 111 acquires job history information of the document. For example, the first device 111 can acquire job history information of a document at the time of ending execution of a program used for document work or storing a document. 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 obtained job history information in a storage space corresponding to the account of the user of the second device 112. [

In step S16315, the first device 111 links the acquired operation history information to the user's calendar using the time information included in the acquired operation history information. For example, if 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 2014.05.12 on the calendar You can generate an indicator to be

In step 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 the job history information to be displayed on the screen of the device by selecting an indicator to be displayed on the calendar or an indicator to be displayed on the calendar.

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

At S16318, the second device 112 outputs the calendar to the screen. For example, the second device 111 can output a calendar on which the indicator transmitted from the first device 111 is displayed.

In step S16319, the third device 113 requests the first device 111 to transfer information to be displayed on the calendar. For example, the third device 113 may request the first device 111 to transmit the job history information to be displayed on the screen of the device as the indicator to be displayed on the calendar or the indicator to be displayed on the calendar is selected.

In step 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 can output a calendar on which the indicator transmitted from the first device 111 is displayed.

Meanwhile, the above-described method can be implemented in a general-purpose digital computer that can be created as a program that can be executed by a computer and operates the program using a computer-readable recording medium. In addition, the structure of the data used in the above-described method can be recorded on a computer-readable recording medium through various means. The computer-readable recording medium includes a storage medium such as a magnetic storage medium (e.g., ROM, RAM, USB, floppy disk, hard disk, etc.), optical reading medium (e.g. CD ROM, 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.

164, the server 16400 may include a communication unit 16410, a control unit 16420, and a database 16430.

The communication unit 16410 transmits and receives the data necessary for linking the job history information of the document to the user's calendar with the devices 110. [ For example, the communication unit 16410 can transmit and receive the job history information of the document, the information to be displayed on the calendar, or the document with the devices 110, but is not limited thereto.

The database 16430 stores information necessary for linking the work history of the document to the calendar of the user. For example, the database 16430 may store, but is not limited to, job history information of documents, documents, account information of users, calendars of users, and information to be displayed in calendars.

The control unit 16420 controls the entire operation of the server 16400. [ The control unit 16420 controls the communication unit 2400 and the database 16430 to allow the server 16400 to link the work history of the document to the user's calendar.

Specifically, the control unit 16420 links the job history information of the document to the calendar of the user. For example, the control unit 16420 can control the communication unit 16410 to allow the communication unit 16410 to receive the job history information of the document from at least one of the devices 110. [ In addition, the control unit 16420 can link the received job history information to the calendar of the user using the time information included in the job history information of the document. Here, the time information means information indicating the time when the device worked on the document.

For example, control 16420 may obtain the user's calendar from at least one of database 16430 or devices 1104. In addition, the control unit 16420 can generate an indicator to be displayed on the calendar based on any one of the name of the document included in the job history information of the document, the program used for creating the document, and the name of the device. In addition, the control unit 16420 can determine the job history information to be displayed on the calendar based on the generated indicator. In addition, the control unit 16420 may display an indicator in an area corresponding to a date or time indicating a time point at which a document is generated in the calendar.

For example, the control unit 16420 controls the communication unit 16410 so that the communication unit 16410 receives from the devices 110 the job history information of each of the documents and documents generated in each of the devices 110 . In addition, the control unit 16420 can generate the final document based on the connection relationship of the received documents. In addition, the control unit 16420 can link the received job history information to the calendar of the user using the time information included in the received job history information.

For example, the control unit 16420 may work on a document at the request of at least one of the devices 110. [ In addition, the control unit 16420 can acquire job history information of the document as the document is operated. In addition, the control unit 16420 can link the acquired job history information to the calendar of the user using the time information included in the acquired job history information.

165 to 166 are block diagrams of a device according to some embodiments.

165 to 166 may correspond to any one of the devices 110 described above with reference to FIGS.

165, a device 16500 according to some embodiments may include a user input portion 16510, an output portion 16520, a control portion 16530, and a communication portion 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, or the first device 16500 may be implemented by fewer components than the components shown in FIG.

166, the first device 16500 according to some embodiments includes a sensing unit 16550 in addition to a user input unit 16510, an output unit 16520, a control unit 16530, and a communication unit 16540. [ ), An A / V input section 16560, and a memory 16570.

The user input unit 16510 means means for the user to input data for controlling the device 16500. [ For example, the user input unit 16510 may include a key pad, a dome switch, a touch pad (contact type capacitance type, pressure type resistive type, infrared ray detection type, surface ultrasonic wave conduction type, A tension measuring method, a piezo effect method, etc.), a jog wheel, a jog switch, and the like, but is not limited thereto.

The user input portion 16510 may receive a user input for selecting an indicator displayed on the calendar. The user input unit 16510 may also receive user input for performing document operations. Here, the operation of the document may mean generation of the document, reading of the document, or editing of the document.

The output section 16520 may output an audio signal or a video signal or a vibration signal and the output section 16520 may include a display section 16521, an acoustic output section 16522, and a vibration motor 16523 have.

The display section 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 a virtual image, and a user interface for purchasing an item of a virtual image.

Meanwhile, when the display portion 16521 and the touch pad have a layer structure and are configured as a touch screen, the display portion 16521 can be used as an input device in addition to the output device. The display portion 16521 may be a liquid crystal display, a thin film transistor-liquid crystal display, an organic light-emitting diode, a flexible display, a three-dimensional display A 3D display, and an electrophoretic display. And the device 16500 may include two or more display portions 16521 depending on the implementation of the device 16500. [ At this time, the two or more display portions 16521 may be arranged to face each other using a hinge.

The sound output section 16522 outputs audio data received from the communication section 16540 or stored in the memory 16580. Further, the sound output section 16522 outputs an acoustic signal related to the functions (e.g., call signal reception sound, message reception sound, alarm sound) performed by the device 16500. [ The sound output unit 16522 may include a speaker, a buzzer, and the like.

The vibration motor 16523 can output a vibration signal. For example, the vibration motor 16523 may output a vibration signal corresponding to an output of audio data or video data (e.g., call signal reception tone, message reception tone, etc.). In addition, the vibration motor 1230 may output a vibration signal when a touch is input to the touch screen.

The control unit 16530 typically controls the overall operation of the device 16500. For example, the control unit 16500 includes a user input unit 16510, an output unit 16520, a sensing unit 16550, a communication unit 16540, an A / V input unit 16560 ) Can be generally controlled.

Specifically, the control unit 16530 performs document processing according to the received user input. Then, the control unit 16530 generates the job history information of the document by performing the document job.

The sensing unit 16550 may sense the state of the device 16500 or the state around the device 16500 and may transmit the sensed information to the control unit 16530. [

The sensing unit 16550 includes a magnetic sensor 16551, an acceleration sensor 16552, an on / humidity sensor 16553, an infrared sensor 16554, a gyroscope sensor 16555, (GPS) 16556, an air pressure sensor 16557, a proximity sensor 16558, and an RGB sensor (illuminance sensor) 16559. However, the present invention is not limited thereto. The function of each sensor can be intuitively deduced from the name by those skilled in the art, so a detailed description will be omitted.

The communication unit 16540 may include one or more components that allow communication between the device 16500 and another device or 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 reception unit 16543.

The short-range wireless communication unit 16541 includes a Bluetooth communication unit, a Bluetooth low energy (BLE) communication unit, a near field communication unit, a WLAN communication unit, a Zigbee communication unit, IrDA, an infrared data association) communication unit, a WFD (Wi-Fi Direct) communication unit, an UWB (ultra wideband) communication unit, an Ant + communication unit, and the like.

The mobile communication unit 16542 transmits and receives a radio signal to 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 depending on a voice call signal, a video call signal, or a text / multimedia message transmission / reception.

The broadcast receiving unit 16543 receives broadcast signals and / or broadcast-related information from outside through a broadcast channel. The broadcast channel may include a satellite channel and a terrestrial channel. The device 16500 may not include the broadcast receiver 16543 according to an implementation.

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 can obtain an image frame such as a still image or a moving image through the image sensor in a video communication mode or a photographing mode. The image captured through the image sensor can be processed through the control unit 16530 or a separate image processing unit (not shown).

The image frame processed by the camera 16561 can be stored in the memory 16580 or can be transmitted to the outside via the communication unit 16540. [ The camera 16561 may be equipped with two or more cameras according to the configuration of the terminal.

The microphone 16562 receives an external acoustic signal and processes it as electrical voice data. For example, the microphone 16562 may receive acoustic signals from an external device or speaker. The microphone 16562 may use various noise reduction algorithms to remove noise generated in receiving an external sound signal.

The memory 16580 may store a program for processing and controlling the control unit 16530 and may store data input to or output from the device 16500. [

The memory 16580 may be a flash memory type, a hard disk type, a multimedia card micro type, a card type memory (e.g., SD or XD memory), a 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) , An optical disc, and the like.

Programs stored in the memory 16580 can be classified into a plurality of modules according to their functions, for example, a UI module 16581, a touch screen module 16582, a notification module 16583, .

The UI module 16581 can provide a specialized UI, a GUI, and the like that are interlocked with the device 16500 for each application. The touch screen module 16582 can detect a touch gesture on the user's touch screen and can transmit information on the touch gesture to the control unit 16530. [ The touch screen module 16582 according to some embodiments may recognize and analyze the touch code. The touch screen module 16582 may be configured as separate hardware including a controller.

Various sensors may be provided in or near the touch screen to sense the touch or near touch of the touch screen. An example of a sensor for sensing the touch of the touch screen is a tactile sensor. A tactile sensor is a sensor that detects the contact of a specific object with a degree or more that a person feels. The tactile sensor can detect various information such as the roughness of the contact surface, the rigidity of the contact object, and the temperature of the contact point.

In addition, a proximity sensor is an example of a sensor for sensing the touch of the touch screen.

The proximity sensor refers to a sensor that detects the presence or absence of an object approaching a predetermined detection surface or a nearby object without mechanical contact using the force of an electromagnetic field or infrared rays. Examples of proximity sensors 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 proximity sensor, a magnetic proximity sensor, and an infrared proximity sensor. The user's touch gestures can include tap, touch & hold, double tap, drag, panning, flick, drag and drop, swipe, and the like.

The notification module 16583 may generate a signal for notifying the occurrence of an event of the device 16500. [ Examples of events generated by 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 portion 16521 or may output a notification signal in the form of an audio signal through the sound output portion 16522, It is possible to output a notification signal in the form of a vibration signal.

It will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the invention as defined by the appended claims. Therefore, the disclosed methods should be considered from an illustrative point of view, not from a restrictive point of view. The scope of the present invention is defined by the appended claims rather than by the foregoing description, and all differences within the scope of equivalents thereof 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 a document job,
A communication unit for receiving job history information of a document operated by at least one first device of the user from the at least one first device; And
And a controller for reflecting the received job history information to a calendar capable of displaying schedule information using the time information included in the received job history information,
Wherein the communication unit provides the second device with a calendar reflecting the operation history information. The method according to claim 1,
Wherein an object representing the job history information corresponding to the date is displayed on a date field in the calendar. 3. The method of claim 2,
And a document corresponding to the selected object is executed on the second device as an object in the calendar is selected. The method of claim 3,
Wherein a document corresponding to the selected object is provided from the first device to the second device. The method of claim 3,
And a document corresponding to the selected object is provided from the server to the second device. The method according to claim 1,
And a database for storing the received job history information and the operated document,
And the communication unit receives the processed document from the first device. The method according to claim 1,
Wherein an identification value of a user who has worked on the document on the date is displayed on a date field in the calendar. The method according to claim 1,
Wherein the identification value of the first device is displayed on the date field on the calendar. The method according to claim 1,
Wherein the job history information includes at least one of a time at which the document job was performed, a name of the document to be worked on, a type of the document to be worked on, a type of the document job, an identification value of the user, And a name of a program used in the server. 10. The method of claim 9,
Wherein the type of document operation includes creating the document, viewing the document, and editing the document. A method for managing history information about a document job,
Receiving from the at least one first device operational history information of a document operated by a user's at least one first device;
Reflecting the received job history information on a calendar capable of displaying schedule information using time information included in the received job history information; And
And providing the second device with a calendar reflecting the operation history information. 12. The method of claim 11,
Wherein an object representing the job history information corresponding to the date is displayed on a date field in the calendar. 13. The method of claim 12,
Wherein a document corresponding to the selected object is executed in the second device as an object in the calendar is selected. 14. The method of claim 13,
Wherein a document corresponding to the selected object is provided from the first device to the second device. 14. The method of claim 13,
And a document corresponding to the selected object is provided from the server to the second device. 12. The method of claim 11,
And storing the received job history information and the processed document,
Wherein the receiving step receives the working document from the first device. 12. The method of claim 11,
Wherein an identification value of a user who has worked on the document on the date is displayed on a date field in the calendar. 12. The method of claim 11,
Wherein the identification value of the first device is displayed on the date field on the calendar. 12. The method of claim 11,
Wherein the job history information includes at least one of a time at which the document job was performed, a name of the document to be worked on, a type of the document to be worked on, a type of the document job, an identification value of the user, Lt; RTI ID = 0.0 &gt; a &lt; / RTI &gt; A computer-readable recording medium storing a program for causing a computer to execute the method of any one of claims 11 to 19. A server for managing history information on a document job,
A communication unit for receiving a job request of a document from at least one first device of the user; And
A job history information generating unit for generating a job history information for the document in accordance with the received job request, generating job history information of the operated document, displaying the generated job history in a calendar capable of displaying schedule information using the time information included in the job history information, And a control unit that reflects the information,
Wherein the communication unit provides the calendar with the job history information reflected to the second device. A server for managing history information on a document job,
A communication unit for receiving job history information of documents operated by first devices of each of a plurality of users from the first devices; And
And a controller for reflecting the received job history information to a calendar capable of displaying schedule information using the time information included in the received job history information,
Wherein the communication unit provides the second device with a calendar reflecting the operation history information.

Images