Processing device, program, and processing method

Abstract

To provide a processing device, a program, and a processing method in which a time required for data synchronization can be restrained.SOLUTION: A client terminal 20 serving as a processing device includes a first processing unit that defines a mode related to file synchronization between the processing device and a first device, and a second processing unit that, if the mode defined for file synchronization is a first mode, executes an uploading process of a file updated by the processing device, among files downloaded from the first device, to the first device.SELECTED DRAWING: Figure 7

Description

[Technical field]

[0001] The present invention relates to a processing device, a program, and a processing method. [Background technology]

[0002] It is common practice to display drawing data managed by a host computer (or server, etc.) on an information terminal (or tablet terminal, etc.). In this regard, for example, there is a technology described in Patent Document 1. Patent Document 1 describes the transfer of data from a host computer (or server, etc.) to an information terminal (or tablet terminal, etc.), data search and viewing on the information terminal, on-site data collection and storage on the information terminal, and synchronization of data between the host computer and the information terminal. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2013-190969 A Summary of the Invention [Problem to be solved by the invention]

[0004] However, in the data synchronization described in Patent Document 1, all data (files) stored in the storage means of the host computer are the targets of data synchronization, and all data (files) stored in the storage means of the information terminal (or tablet terminal, etc.) are the targets of data synchronization, so when there is a lot of data (files), the synchronization process takes a long time. Therefore, for example, a person working on site wants to limit the drawing data (files) to be synchronized to only the drawing data (files) that he or she is responsible for, in order to shorten the time required for data synchronization.

[0005] The present invention has been made in consideration of the above-mentioned problems, and provides a processing device, a program, and a processing method that can reduce the time required for synchronizing data (files). [Means for solving the problem]

[0006] In order to solve the above problem, the processing device of the present invention is characterized in that it comprises a first processing unit that sets a mode related to file synchronization between the processing device and a first device, and a second processing unit that, if the mode set in file synchronization is a first mode, executes an upload process to the first device for files downloaded from the first device that have been updated by the processing device.

[0007] In addition, the program of the present invention is characterized in that it causes a computer of a processing device to function as a first processing unit that sets a mode related to file synchronization between the processing device and a first device, and a second processing unit that, in file synchronization, if the set mode is a first mode, executes an upload process to the first device for files downloaded from the first device that have been updated on the processing device.

[0008] Furthermore, a method according to the present invention is a processing method of a processing device, characterized in that the processing device has a first processing step of setting a mode related to file synchronization between the processing device and a first device, and a second processing step of, if the mode set in the file synchronization is a first mode, performing an upload process to the first device for files downloaded from the first device that have been updated by the processing device. Effect of the Invention

[0009] According to the present invention, the time required for synchronizing data (files) can be reduced. [Brief description of the drawings]

[0010] [Figure 1] 1 is an overall configuration diagram of a system according to an embodiment of the present invention. [Diagram 2] FIG. 2 is a functional configuration diagram of a cloud server according to an embodiment of the present invention. [Diagram 3] This is an image of the correspondence between drawings and sheets on a cloud server. [Figure 4] 13 is a diagram illustrating an example of the configuration of a file ID table included in a cloud server. [Diagram 5] 13 is a diagram showing an example of a memo (addition) table stored in a cloud server. [Figure 6] 13 is a diagram illustrating an example of the configuration of a file update table included in a cloud server. [Figure 7] FIG. 2 is a functional configuration diagram of a client terminal according to the embodiment of the present invention. [Figure 8] This is an image of the corresponding relationship between drawings and sheets on a client terminal. [Figure 9] 13 is a diagram showing an example of a configuration of a file ID table held by a client terminal. [Figure 10] 13 is a diagram showing an example of a memo (addition) table included in a client terminal. [Figure 11] 13 is a configuration example of a file synchronization management table included in a client terminal. [Figure 12] FIG. 2 is a diagram showing an operation flow of the system according to the embodiment of the present invention. [Figure 13] FIG. 2 is a sequence diagram relating to the operation of the system according to the embodiment of the present invention. [Figure 14] 1 is an example of a flowchart illustrating a process relating to synchronization. [Figure 15] 13 is an example of a flowchart illustrating a process for selecting a mode of synchronization. [Figure 16] 13 is an example of a flowchart illustrating a process for creating a list of files to be synchronized. [Figure 17] 13 is an example of a flowchart illustrating a process of performing bidirectional synchronization between a client terminal and a cloud server. [Figure 18] 11A and 11B are diagrams for explaining changes in a file update table and a file synchronization management table due to processing relating to synchronization; [Figure 19] 11A and 11B are diagrams for explaining changes in a file update table and a file synchronization management table due to processing relating to synchronization; [Figure 20] 11A and 11B are diagrams for explaining changes in a file update table and a file synchronization management table due to processing relating to synchronization; [Figure 21] 11A and 11B are diagrams for explaining changes in a file update table and a file synchronization management table due to processing relating to synchronization. [Figure 22] 11A and 11B are diagrams for explaining changes in a file update table and a file synchronization management table due to processing relating to synchronization; [Diagram 23] 11A and 11B are diagrams for explaining changes in a file update table and a file synchronization management table due to processing relating to synchronization. [Figure 24] 11A and 11B are diagrams for explaining changes in a file update table and a file synchronization management table due to processing relating to synchronization; [Diagram 25] 11A and 11B are diagrams for explaining changes in a file update table and a file synchronization management table due to processing relating to synchronization. [Figure 26] 11A and 11B are diagrams for explaining changes in a file update table and a file synchronization management table due to processing relating to synchronization. [Figure 27] 11A and 11B are diagrams for explaining changes in a file update table and a file synchronization management table due to processing relating to synchronization. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0011] Hereinafter, the embodiments for carrying out the present invention will be described in detail with reference to the drawings as appropriate. Each figure is merely a schematic illustration to the extent that the present invention can be fully understood. Therefore, the present invention is not limited to only the illustrated examples. In addition, in each embodiment, the explanation of the configuration that is not directly related to the present invention or the well-known configuration may be omitted. In addition, in each figure, the same reference numerals are given to the common components or similar components, and the duplicate explanations thereof will be omitted.

[0012] Configuration of the system according to the embodiment The configuration of system 1 according to the embodiment will be described with reference to Fig. 1. System 1 has a function of managing at least one of drawings (drawings) required for carrying out construction work on a building, documents explaining the contents and procedures required for carrying out construction work on a building, such as specifications (including specifications with drawings), and photographs related to construction work, and displays the drawings, documents, and photographs upon request of the parties involved in the construction work. In the embodiments, the case where drawings are managed and displayed will be mainly described as an example, and the management and display of documents and photographs will be omitted. The management and display of documents and photographs is similar to the management and display of drawings, and can be described by replacing "drawings" in each embodiment with "documents" or "photographs". Here, the drawings, documents, and photographs described above are one piece of information that constitutes the information of design documents.

[0013] FIG. 1 shows a system configuration of a system 1 according to an embodiment. The system 1 includes a cloud server 10 and a plurality of client terminals 20. The cloud server 10 and the plurality of client terminals 20 are connected to each other so as to be able to communicate data with each other via a communication network NW such as the Internet. The system 1 manages construction drawings in the construction industry on the cloud server 10, and enables each client terminal 20 to make notes (additions) to the construction drawings and check the construction drawings including the notes (additions) at the construction site, office, contractor, client's home, etc. The system 1 is mainly used by construction companies, architectural companies, etc. that plan and carry out construction work. The system 1 has a function of synchronizing the drawings managed by the cloud server 10 with the drawings memorized (added) by the client terminal 20. In other words, the system 1 plays a role as a synchronization system. Note that the configuration of the system 1 shown in FIG. 1 is merely an example.

[0014] The cloud server 10 is an example of a “first device”, and an example of the “first device” is not limited to the cloud server 10. Moreover, the client terminal 20 is an example of a “processing device”, and an example of a “processing device” is not limited to the client terminal 20.

[0015] 2 is a block diagram showing the functional configuration of the cloud server 10. The cloud server 10 includes a CPU (Central Processing Unit) 11, a RAM (Random Access Memory) 12, an input unit 13, a display unit 14, a communication unit 15, a storage unit 16, and a drawing storage device 17, and each unit is connected via a bus 18.

[0016] The CPU 11 comprehensively controls the processing operations of each unit of the cloud server 10. The CPU 11 reads out various programs stored in the storage unit 16, loads them into the RAM 12, and performs various processes in cooperation with the programs.

[0017] The RAM 12 is a volatile memory that temporarily stores various programs to be executed and data related to these programs.

[0018] The input unit 13 includes a keyboard having character input keys, numeric input keys, various function keys, etc., and a pointing device such as a mouse. The input unit 13 outputs to the CPU 11 operation signals input by the user operating the keyboard or the mouse.

[0019] The display unit 14 is configured with an LCD (Liquid Crystal Display) etc. The display unit 14 performs screen display in accordance with a display control signal from the CPU 11.

[0020] The communication unit 15 is configured by a network interface, etc. The communication unit 15 transmits and receives data to and from a connected external device via the communication network NW.

[0021] The storage unit 16 is configured with a HDD (Hard Disk Drive), a non-volatile memory, etc. The storage unit 16 stores information in a readable and writable manner. The storage unit 16 stores a drawing processing program P1.

[0022] The drawing storage device 17 shown in FIG. 2 is a storage device that stores information in a readable and writable manner. The drawing storage device 17 stores electronic data (drawing files) of multiple drawings at a construction site. In addition, the drawing storage device 17 stores multiple sheets including notes (retouching) written on the drawing for each of the multiple drawings in association with the drawing. The sheets are virtual transparent sheets on which notes (retouching) on ​​the drawing are recorded, and are overlaid on the drawing. For example, in the drawing storage device 17, a drawing file including information on the drawing of the construction work and a memo (retouching) file including information on the sheet to be memoed (retouched) are stored in association with each other in a predetermined folder. The sheets of the memo (retouching) file are managed as layers (first layer, second layer, third layer, ...).

[0023] An image of the correspondence between drawings and sheets is shown in Fig. 3. In Fig. 3, sheets "a", "b", and "c" are associated with drawing A. Note "A" has been added as a memo to sheet "a", note "B" has been added as a memo to sheet "b", and notes "C" and "D" have been added as memos to sheet "c". For example, sheet "a" is the main sheet (original sheet), and viewing and updating permissions are given to a wide range of related parties (viewing and updating permissions are set broadly), while sheets "b" and "c" are given to related parties with special roles (viewing and updating permissions are set narrowly).

[0024] As shown in Fig. 3, the data format of the electronic data of the drawings (drawing files) is, for example, "PDF (Portable Document Format)". The data format of the electronic data of the notes (additions) (note (addition) files) is, for example, "XML (Extensible Markup Language)", and sheets are distinguished by XML attribute information. In this way, in the cloud server 10, the electronic data of the drawings (drawing files) and the electronic data of the notes (additions) (note (addition) files) are stored as separate files in different data formats.

[0025] As shown in Fig. 2, the drawing file and the memo (addition) file are linked (associated) with each other. With reference to Fig. 4, an example of a method for linking (associating) the drawing file and the memo (addition) file will be described.

[0026] The file ID table T1 shown in Fig. 4 stores information for linking (tying) drawing files and memo (edited) files. As shown in Fig. 4, in this embodiment, the file ID table T1 is composed of a file ID column T1a, a drawing file name column T1b, and a memo (edited) file name column T1c.

[0027] The file ID stored in the field T1a is information for identifying a group of linked drawing files and memo (addition) files, and in FIG. 4, "ID1" is shown as an example. The drawing file name stored in the field T1b is the name of the drawing file, and in FIG. 4, "AAAA.pdf" is shown as an example. The memo (addition) file name stored in the field T1c is the name of the memo (addition) file, and in FIG. 4, "AAAA.xml" is shown as an example.

[0028] As shown in Figure 4, it is also possible to link (link) drawing files and memo (addition) files without using file IDs by making the base name in the drawing file name the same as the base name in the memo (addition) file name. Here, the base name is the portion of the file name (drawing file name, memo (addition) file name) other than the extension (the portion to the left of the period).

[0029] With reference to Fig. 5, the information of the sheets in the memo (edit) file will be described. The memo (edit) table T2 shown in Fig. 5 is generated for each drawing, and stores information of the sheet on which the memo (edit) is added to each drawing. As shown in Fig. 5, in this embodiment, the memo (edit) table T2 is composed of a memo ID column T2a, a sheet name column T2b, a memo type column T2c, a memo display position coordinate column T2d, a memo content column T2e, and a creation / update date column T2f.

[0030] The memo ID stored in the field T2a is information for identifying a memo added to a drawing, and in FIG. 5, "AAAA1", "AAAA2", "AAAA3", and "AAAA4" are exemplified. The sheet name stored in the field T2b is the name of the sheet associated with the drawing, and in FIG. 5, sheet "a", sheet "b", and sheet "c" are exemplified. The type of note stored in the field T2c is information for classifying the note to be added, and "comment" is exemplified in Fig. 5. The type of note may be, for example, "image" or "icon" in addition to "comment".

[0031] The coordinates of the display position of the note stored in column T2d are the coordinates (position information) of the display position of the note in the drawing. In FIG. 5, the coordinates of the display position of the note are composed of the x coordinate in the x-axis direction (an example is "XXX1") and the y coordinate in the y-axis direction (an example is "YYY1"). The contents of the memo stored in the field T2e are information related to the contents of the added memo, and in FIG. 5, note "A", note "B", note "C", and note "D" are shown as examples. The creation / update date and time stored in the field T2f is information about the creation date and time or the update date and time when the memo was added, and in FIG. 5, the creation / update date and time are composed of "year / month / date" and "hour / minute".

[0032] As shown in Fig. 2, a file update table T3 is stored in the drawing storage device 17. Fig. 6 shows an example of the configuration of the file update table T3. The file update table T3 shown in Fig. 6 stores information regarding the creation / update of files on the cloud server 10 side. As shown in Fig. 6, in this embodiment, the file update table T3 is made up of a target file ID column T3a, a file name column T3b, and a creation date / time / update date / time column T3c by the cloud server.

[0033] The target file ID stored in field T3a is information that identifies a group of linked drawing files and memo (addition) files, and in FIG. 6, "ID1", "ID2", "ID3", and "ID4" are shown as examples. The file names stored in the field T3b are the names of drawing files and memo (addition) files. In FIG. 6, for example, "AAAA.pdf" and "AAAA.xml" are shown as file names corresponding to the target file ID "ID1".

[0034] The creation date / time / update date / time by the cloud server stored in the field T3c is the date / time (one example is the year / month / date and hour / minute) when the file was created or updated by the cloud server 10. The creation or update of the file by the cloud server 10 includes uploading of the file created / updated by the client terminal 20, in which case the date / time when the created / updated file was uploaded from the client terminal 20 to the cloud server 10 is stored in the field T3c. In FIG. 6, the latest upload date / time of the drawing file name "AAAA.pdf" of the target file ID "ID1" is "2023 / 05 / 19 09:00", and the latest upload date / time of the memo (addition) file name "AAAA.xml" is "2023 / 05 / 19 09:00".

[0035] The CPU 11 shown in FIG. 2 is configured to execute the following processes based on the configuration of the cloud server 10 described above. Based on an instruction (download) from the client terminal 20, the CPU 11 outputs the instructed "drawing file" and "memo (addition) file linked to the drawing file" which are stored in the drawing memory device 17 to the client terminal 20 via the communication unit 15.

[0036] In addition, based on an instruction (synchronization (upload)) from the client terminal 20, the CPU 11 inputs either one or both of the instructed "drawing file" and "note (addition) file linked to the drawing file" from the client terminal 20 via the communication unit 15. Furthermore, the CPU 11 synchronizes (updates) the file stored in the drawing storage device 17 based on either or both of the input "drawing file" and "memo (addition) file linked to the drawing file."

[0037] In addition, based on an instruction (synchronization (download)) from the client terminal 20, the CPU 11 outputs to the client terminal 20 via the communication unit 15 either or both of the instructed "drawing file" and "note (addition) file linked to the drawing file", which are synchronized (updated) files stored in the drawing memory device 17.

[0038] 7 is a block diagram showing the functional configuration of the client terminal 20. The client terminal 20 includes a CPU 21, a RAM 22, an input unit 23, a display unit 24, a communication unit 25, a storage unit 26, and a drawing storage device 27, and each unit is connected via a bus 28. The client terminal 20 is a device having a display function, and is configured by a general tablet-type information terminal (tablet terminal) or a PC (Personal Computer). Here, when the client terminal 20 is configured by a PC, examples of the PC include a notebook PC equipped with a display device, and a desktop PC connected to a display device.

[0039] The CPU 21 comprehensively controls the processing operations of each unit of the client terminal 20. The CPU 21 reads out various programs stored in the storage unit 26, loads them into the RAM 22, and performs various processes in cooperation with the programs.

[0040] The RAM 22 is a volatile memory that temporarily stores various programs to be executed and data related to these programs.

[0041] The input unit 23 includes a touch panel provided on the display screen of the display unit 24. The input unit 23 detects the position of a touch operation by a user's finger or a dedicated pen, and outputs an operation signal according to the position to the CPU 21. The input unit 23 includes a keyboard having character input keys, number input keys, various function keys, and the like, and a pointing device such as a mouse. The input unit 23 may output to the CPU 21 an operation signal input by the user's key operation on the keyboard or mouse operation.

[0042] The display unit 24 is configured with an LCD etc. The display unit 24 performs screen display in accordance with a display control signal from the CPU 21.

[0043] The communication unit 25 is configured by a network interface, etc. The communication unit 25 transmits and receives data to and from a connected external device via the communication network NW.

[0044] The storage unit 26 is configured with a HDD, a non-volatile memory, etc. The storage unit 26 stores information in a readable and writable manner. The storage unit 26 stores a drawing processing program P2.

[0045] The drawing storage device 27 shown in FIG. 7 is a storage device that stores information in a readable and writable manner. The drawing storage device 27 stores electronic data (drawing files) of multiple drawings at a construction site. In addition, the drawing storage device 27 stores multiple sheets including notes (retouching) written on the drawing for each of the multiple drawings in association with the drawing. The sheets are virtual transparent sheets on which notes (retouching) on ​​the drawing are recorded, and are overlaid on the drawing. For example, in the drawing storage device 27, a drawing file including information on the drawing of the construction work and a memo (retouching) file including information on the sheet to be memoed (retouched) are stored in association with each other in a predetermined folder. The sheets of the memo (retouching) file are managed as layers (first layer, second layer, third layer, ...).

[0046] An image of the correspondence between drawings and sheets is shown in Fig. 8. In Fig. 8, sheets "a", "b", and "c" are associated with drawing A. Note "A" has been added as a memo to sheet "a", note "B" has been added as a memo to sheet "b", and notes "C" and "D" have been added as memos to sheet "c". For example, sheet "a" is the main sheet (original sheet), and viewing and updating permissions are given to a wide range of related parties (viewing and updating permissions are set broadly), while sheets "b" and "c" are given to related parties with special roles (viewing and updating permissions are set narrowly).

[0047] Here, when the "drawings and sheets (see Figure 3)" stored in the cloud server 10 and the "drawings and sheets (see Figure 8)" stored in the client terminal 20 are synchronized, the "drawings and sheets" shown in Figure 3 will have the same content (same configuration) as the "drawings and sheets" shown in Figure 8.

[0048] Fig. 8 has the same content (same configuration) as Fig. 3, for example, and as shown in Fig. 8, the data format of the electronic data of the drawing (drawing file) is, for example, "PDF (Portable Document Format)". Also, the data format of the electronic data of the memo (additions) (memo (additions) file) is, for example, "XML (Extensible Markup Language)", and sheets are distinguished by XML attribute information. In this way, in the client terminal 20, the electronic data of the drawing (drawing file) and the electronic data of the memo (additions) (memo (additions) file) are stored as separate files in different data formats.

[0049] The drawing storage device 27 also stores a file ID table T4, a memo (addition) table T5, and a file synchronization management table T6. Fig. 9 is a configuration example of a file ID table T4, Fig. 10 is a configuration example of a memo (addition) table T5, and Fig. 11 is a configuration example of a file synchronization management table T6. The file ID table T4 and the memo (addition) table T5 may have the same contents as the file ID table T1 and the memo (addition) table T2 held by the cloud server 10. The file ID tables T1, T4 and the memo (addition) tables T2, T5 are shared by the cloud server 10 and the client terminal 20 by some method.

[0050] The file ID table T4 shown in Fig. 9 stores information for linking (tying) drawing files and memo (edited) files. The file ID table T4 shown in Fig. 9 has the same configuration as the file ID table T1 shown in Fig. 4. As shown in Fig. 9, in this embodiment, the file ID table T4 is made up of a file ID column T4a, a drawing file name column T4b, and a memo (edited) file name column T4c. A description of the information stored in each column of the file ID table T4 will be omitted.

[0051] The memo (editing) table T5 shown in Fig. 10 is generated for each drawing, and stores information on the sheet on which the memo (editing) is added to each drawing. The memo (editing) table T5 shown in Fig. 10 has the same configuration as the memo (editing) table T5 shown in Fig. 5. As shown in Fig. 10, in this embodiment, the memo (editing) table T5 is configured with a memo ID column T5a, a sheet name column T5b, a memo type column T5c, a memo display position coordinate column T5d, a memo content column T5e, and a creation / update date column T5f. A description of the information stored in each column of the memo (editing) table T5 will be omitted.

[0052] 11 is used for file synchronization management, and stores information related to the synchronization management of files managed by the cloud server 10. As shown in Fig. 11, in this embodiment, the file synchronization management table T6 is made up of a target file ID column T6a, a file name column T6b, a synchronization mode column T6c, a selected file column T6d, a client terminal download date and time column T6e, a client terminal creation date and time / update date and time column T6f, and a file list column T6g to be synchronized.

[0053] The target file ID stored in field T6a is information that identifies a group of linked drawing files and memo (addition) files, and in FIG. 11, "ID1", "ID2", "ID3", and "ID4" are shown as examples. The file names stored in the field T6b are the names of drawing files and memo (addition) files. In FIG. 11, for example, "AAAA.pdf" and "AAAA.xml" are shown as file names corresponding to the target file ID "ID1".

[0054] The synchronization mode stored in field T6c is information related to the synchronization processing method, and "self" is shown as an example in FIG. 11. When the synchronization mode is "self", it is possible to select the data (files) to be synchronized. In addition to "self", other synchronization modes include "all". When the synchronization mode is "all", all data (files) are subject to synchronization. The selected file stored in column T6d is information that identifies the data (files) to be synchronized when the synchronization mode is "self", and FIG. 11 shows "selected" and "-" as examples. A file with "selected" registered is data (files) to be synchronized, and a file with "-" registered is data (files) that is not to be synchronized. Note that when the synchronization mode is "all", "selected" may be registered in column T6d for all files. The synchronization mode "self" is an example of a "first mode," and the synchronization mode "all" is an example of a "second mode."

[0055] The download date and time by the client terminal stored in the field T6e is the date and time (one example is the year, month, date, and hour and minute) when the file was downloaded by the client terminal 20. In FIG. 11, for example, a file with the drawing file name "AAAA.pdf" was downloaded on "2023 / 05 / 19 10:01", and a file with the memo (addition) file name "AAAA.xml" was downloaded on "2023 / 05 / 19 10:02". Here, the field T6e in which the download date and time by the client terminal is stored also stores the date and time based on the update of the file downloaded from the cloud server 10. The creation date / time / update date / time by the client terminal stored in the field T6f is the date and time (one example is the year, month, date, and hour and minute) when the file was created or updated by the client terminal 20. In Fig. 11, the field T6f is blank, which indicates that no file has been created or updated by the client terminal 20.

[0056] The file list to be synchronized stored in field T6g is information that identifies the data (files) that will actually undergo synchronization processing. In FIG. 11, field T6g is blank, and no files that will actually undergo synchronization processing are registered. For example, when the synchronization mode is "self", "selection" is registered in field T6d, and files with date and time registered in field T6f are registered as files to be actually synchronized. When the synchronization mode is "all", all files are registered as files to be actually synchronized.

[0057] The CPU 21 shown in FIG. 7 is configured to execute the following processes based on the configuration of the client terminal 20 described above. Based on a user instruction (download) on the client terminal 20, the CPU 21 inputs the specified “drawing file” and “memo (addition) file linked to the drawing file”, which are to be stored in the drawing memory device 17, from the cloud server 10 via the communication unit 25.

[0058] In addition, based on a user instruction (synchronization (upload)) on the client terminal 20, the CPU 21 outputs either one or both of the specified “drawing file” and “note (addition) file linked to the drawing file” to the cloud server 10 via the communication unit 25. Furthermore, based on a user instruction (synchronization (download)) on the client terminal 20, the CPU 21 inputs from the cloud server 10 via the communication unit 25 either one or both of the specified "drawing file" and "note (addition) file linked to the drawing file," which have been synchronized (updated) on the cloud server 10.

[0059] It should be noted that the CPU 21 of the client terminal 20 is an example of a “computer”, and the example of a “computer” is not limited to the CPU 21 of the client terminal 20. Furthermore, the functions realized by CPU21 are examples of the "first processing unit," "second processing unit," "third processing unit," and "fourth processing unit," and examples of the "first processing unit," "second processing unit," "third processing unit," and "fourth processing unit" are not limited to the functions realized by CPU21.

[0060] <<Operation of the System According to the Embodiment>> An operation flow of the system 1 according to the embodiment will be described below with reference to Fig. 12 (and Figs. 1 to 11 as appropriate). Fig. 12 is a diagram showing an operation flow of the system 1 according to the embodiment.

[0061] First, the client terminal 20 downloads in advance a drawing file from the cloud server 10 (process (a)). In process (a), a memo (retouching) file linked to the drawing file is also downloaded. Here, it is assumed that the “drawing file” and the “memo (addition) file linked to the drawing file” are stored in advance in the drawing storage device 17 of the cloud server 10.

[0062] Next, the client terminal 20 adds a memo to the "sheet" included in the memo (addition) file (process (b)). Note that the client terminal 20 may update the drawing file. Then, the client terminal 20 and the cloud server 10 synchronize with each other regarding either or both of the "drawing file" and the "memo (edited) file linked to the drawing file" (process (c)).

[0063] Next, the operation of each of the client terminal 20 and the cloud server 10 will be described with reference to Fig. 13 (and Figs. 1 to 12 as appropriate). Fig. 13 is a sequence diagram relating to the operation of the system 1 according to the embodiment. Here, it is assumed that the client terminal 20 is operated by an operator (user) who is capable of updating "sheet a" but is only capable of viewing (but not updating) "sheet b" and "sheet c."

[0064] <Processing (a)> [Processing on cloud server 10 side] Based on an instruction (download) from the client terminal 20, the cloud server 10 outputs the specified "drawing file" and "memo (addition) file linked to the drawing file" which are stored in the drawing memory device 17 to the client terminal 20 via the communication unit 15.

[0065] [Processing on the client terminal 20 side] Based on a user instruction (download) on the client terminal 20, the client terminal 20 inputs the specified “drawing file” and “note (addition) file linked to the drawing file”, which are to be stored in the drawing storage device 17, from the cloud server 10 via the communication unit 25. Here, if the "drawing file" and the "note (addition) file linked to the drawing file" are not pre-stored in the drawing storage device 27, the "drawing file" and the "note (addition) file linked to the drawing file" input from the cloud server 10 are stored in the drawing storage device 27 by a process of storing new files. In addition, if the "drawing file" and the "memo (addition) file linked to the drawing file" are pre-stored in the drawing storage device 27, the "drawing file" and the "memo (addition) file linked to the drawing file" input from the cloud server 10 are stored in the drawing storage device 27 by an overwrite process.

[0066] <Processing (b)> [Processing on the client terminal 20 side] The client terminal 20 adds a memo to the sheet of the operated "memo (edit) file" based on the operation (memo (edit)) of the user on the client terminal 20. The sheet with the memo (edit) is stored in the drawing storage device 27. For example, the user adds a memo to the "a sheet" of the memo (addition) file name "AAAA.xml" and also adds a memo to the "a sheet" of the memo (addition) file name "DDDD.xml".

[0067] [Processing on cloud server 10 side] In the cloud server 10, there is no processing related to the process (b).

[0068] <Processing (c)> [Processing on the client terminal 20 side] Based on a user instruction (synchronization (upload)) on the client terminal 20, the client terminal 20 outputs either one or both of the specified “drawing file” and “note (addition) file linked to the drawing file” to the cloud server 10 via the communication unit 25. For example, a memo (edited) file with the memo (edited) file name “AAAA.xml” and a memo (edited) file with the memo (edited) file name “DDDD.xml” are output (uploaded) to the cloud server 10.

[0069] In addition, based on a user instruction (synchronization (download)) on the client terminal 20, the client terminal 20 inputs from the cloud server 10 via the communication unit 25 either one or both of the specified "drawing file" and "note (addition) file linked to the drawing file," which have been synchronized (updated) on the cloud server 10. For example, memo (edited) files with the memo (edited) file name "AAAA.xml", the memo (edited) file name "BBBB.xml", and the memo (edited) file name "DDDD.xml" are input (downloaded) from the cloud server 10. Note that the memo (edited) file with the memo (edited) file name "BBBB.xml" is a synchronized (updated) file that has been synchronized (updated) by the operation of another user.

[0070] [Processing on cloud server 10 side] Based on an instruction (synchronization (upload)) from the client terminal 20, the cloud server 10 inputs either one or both of the instructed "drawing file" and "note (addition) file linked to the drawing file" from the client terminal 20 via the communication unit 15. Furthermore, the cloud server 10 synchronizes (updates) the files stored in the drawing storage device 17 based on either or both of the input "drawing file" and "memo (addition) file linked to the drawing file."

[0071] For example, a memo (edited) file with a memo (edited) file name "AAAA.xml" and a memo (edited) file with a memo (edited) file name "DDDD.xml" are input (uploaded) from the client terminal 20 by a user operation, and the files stored in the drawing storage device 17 are synchronized (updated). Also, although not shown in the figure, a memo (edited) file with a memo (edited) file name "BBBB.xml" is input (uploaded) from another client terminal 20 by a different user operation, and the files stored in the drawing storage device 17 are synchronized (updated).

[0072] In addition, based on an instruction (synchronization (download)) from the client terminal 20, the cloud server 10 outputs to the client terminal 20 via the communication unit 15 either or both of the instructed "drawing file" and "note (addition) file linked to the drawing file," which are synchronized (updated) files stored in the drawing memory device 17. For example, the memo (edited) files with the memo (edited) file name “AAAA.xml”, the memo (edited) file name “BBBB.xml”, and the memo (edited) file name “DDDD.xml” are output (downloaded) to the client terminal 20.

[0073] <<About synchronization processes>> The process relating to synchronization will now be described in more detail with reference to Fig. 14, which is a flowchart showing an example of the process relating to synchronization. As shown in FIG. 14, the processes related to synchronization are broadly divided into a process of selecting a synchronization mode on the client terminal (step S10), a process of creating a list of files to be synchronized (step S20), and a process of performing two-way synchronization between the client terminal and the cloud server (step S30).

[0074] Among the processes related to synchronization in Fig. 14, the processes of steps S10 and S20 can be executed in parallel with the processes (a) and (b) shown in Fig. 12 and Fig. 13. Also, among the processes related to synchronization in Fig. 14, the process of step S30 corresponds to the process (c) shown in Fig. 12 and Fig. 13. In the following description, the process of step S30 in Fig. 14 will be described with a focus on the process for the memo (revised) file including the memo (revised) sheet. Note that the process for the drawing file in the process of step S30 in Fig. 14 is similar to the process for the memo (revised) file including the memo (revised) sheet in the process of step S30 in Fig. 14.

[0075] <Processing of step S10 related to synchronization> Fig. 15 is a flowchart showing an example of a process (step S10) for selecting a synchronization mode. The process in Fig. 15 is executed by the client terminal 20 (one example is a tablet terminal). Before executing the synchronization process (step S30), the user specifies whether to synchronize only the files specified by the user (for example, files updated by the user) or to synchronize all files. For example, two options, "synchronize only files updated by the user" and "synchronize all files," are displayed on the screen of the client terminal 20, and the user can select one.

[0076] Then, when synchronization of only the files that the client terminal 20 has updated is selected ("Yes" in step S11), the CPU 21 of the client terminal 20 stores "self" in the synchronization mode column T6c of the file synchronization management table T6 (step S12, see the area surrounded by a bold frame in FIG. 18). It also stores "selected" in the selected file column T6d of the files to be synchronized, and stores "-" in the selected file column T6d of the files not to be synchronized (see the area surrounded by a bold frame in FIG. 18). In FIG. 18, the files "ID1", "ID2", and "ID4" are to be synchronized, and the file "ID3" is not to be synchronized.

[0077] On the other hand, if synchronization of only the files that the client terminal 20 has updated is not selected (step S11: No), the CPU 21 of the client terminal 20 stores "all" in the synchronization mode field T6c of the file synchronization management table T6 (step S13, see the area surrounded by a thick frame in FIG. 19). Also, it stores "selected" in the selected file field T6d of all files (see the area surrounded by a thick frame in FIG. 19).

[0078] <Processing of step S20 related to synchronization> Fig. 16 is an example of a flowchart showing the process (step S20) of creating a list of files to be synchronized. The process in Fig. 16 is executed by the client terminal 20 (one example is a tablet terminal).

[0079] When the synchronization mode is set to synchronize only files updated by the client terminal 20 (synchronization mode is "self") ("Yes" in step S21), the CPU 21 of the client terminal 20 searches for files updated by the client terminal 20 and creates a file list to be synchronized (step S22). For example, the download date and time of each file stored in the column T6e of the file synchronization management table T6 is compared with the update date and time stored in the column T6f, and if the update date and time is newer than the download date and time, the file is added to the file list to be synchronized in the column T6g as a file updated by the client terminal 20 (see the area surrounded by a thick frame in FIG. 20). By performing this process for all files in the terminal, the file list to be synchronized is completed. In FIG. 20, the file with the file name "AAAA.xml" of the memo (addition) of "ID1" and the file with the file name "DDDD.xml" of the memo (addition) of "ID4" are added to the file list to be synchronized.

[0080] On the other hand, if the synchronization mode is not to synchronize only files updated by the terminal itself (synchronization mode is "all") ("No" in step S21), a file list for synchronizing all files is created (step S23). In Fig. 21, the list is completed by adding all files in the terminal to the file list for synchronization in field T6g.

[0081] <Processing of step S30 related to synchronization> FIG. 17 is an example of a flowchart showing a process (step S30) of performing bidirectional synchronization between the client terminal 20 and the cloud server 10. As shown in FIG. 17, a created list of files to be synchronized is read (step S31), and the files listed in this list are bidirectionally synchronized (uploaded and downloaded) between the cloud server 10 and the client terminal 20 (step S32).

[0082] An example of processing when the synchronization mode is "self" in which only files updated by the device itself are synchronized will be described with reference to Figs. 22 to 24. In Figure 22, a file with the note (addition) file name "AAAA.xml" for "ID1" and a file with the note (addition) file name "DDDD.xml" for "ID4" have been added to the list of files to be synchronized, so these files are uploaded from the client terminal 20 to the cloud server 10.

[0083] The CPU 11 of the cloud server 10 stores the upload date and time in the client terminal creation date and time / update date and time column T3c of the file update table T3 for the file with the memo (addition) file name "AAAA.xml" of "ID1" and the file with the memo (addition) file name "DDDD.xml" uploaded from the client terminal 20 (see FIG. 23). In FIG. 23, the file with the memo (addition) file name "AAAA.xml" of "ID1" was uploaded on "2023 / 05 / 19 13:01", and the file with the memo (addition) file name "DDDD.xml" of "ID4" was uploaded on "2023 / 05 / 19 13:02". The file with the memo (addition) file name "BBBB.xml" of "ID2" was uploaded by another user on "2023 / 05 / 19 11:14".

[0084] Next, the CPU 21 of the client terminal 20 downloads a file that is a file with the selected file column T6d set to "selected" and has a newer date and time in the client terminal creation date and time / update date and time column T3c than the client terminal download date and time column T6e. In FIG. 23, the file with the memo (edited) file name "AAAA.xml" of "ID1" has a date and time in column T6e of "2023 / 05 / 19 10:02" while the date and time in column T3c is "2023 / 5 / 19 13:01", so the file is downloaded (see FIG. 24). Similarly, the file with the memo (edited) file name "BBBB.xml" of "ID2" and the file with the memo (edited) file name "DDDD.xml" of "ID4" are downloaded. Then, as shown in FIG. 24, the CPU 21 of the client terminal 20 updates the date and time in column T6e of the downloaded file. Also, the information stored in columns T6f and T6g is deleted.

[0085] An example of processing when all files are synchronized (synchronization mode is "all") will be described with reference to Figs. 25 to 27. As shown in FIG. 25, all files have been added to the file list to be synchronized, so these files are all uploaded from the client terminal 20 to the cloud server 10.

[0086] The CPU 11 of the cloud server 10 updates the files updated on the client terminal 20 side among the files uploaded from the client terminal 20 (for example, a file whose date and time in the column T6f of the creation date and time / update date and time by the client terminal is newer than the date and time in the column T3c of the creation date and time / update date and time by the client terminal of the file update table T3), and updates the date and time in the column T3c of the creation date and time / update date and time by the client terminal of the file (see FIG. 26). In FIG. 26, a file with the memo (addition) file name "AAAA.xml" of "ID1" was uploaded on "2023 / 05 / 19 13:02", and a file with the memo (addition) file name "DDDD.xml" of "ID4" was uploaded on "2023 / 05 / 19 13:08". Note that a file with the memo (addition) file name "BBBB.xml" of "ID2" was uploaded by another user on "2023 / 05 / 19 11:14".

[0087] Next, the CPU 21 of the client terminal 20 downloads all files from the cloud server 10 to the client terminal 20 (see FIG. 27). Then, as shown in FIG. 27, the CPU 21 of the client terminal 20 updates the date and time in the column T6e of the downloaded file. Also, the CPU 21 of the client terminal 20 deletes the information stored in the columns T6f and T6g.

[0088] [Variations] Modifications to the embodiment of the present invention are shown below. The modified example is a modified example in the processing of step S30 related to synchronization, in which the synchronization mode is "self", and a file uploaded by another user on "2023 / 05 / 19 11:14" (the note (addition) file name of "ID2" is "BBBB.xml") is not subject to download (not subject to synchronization), as shown below.

[0089] <<Modification of the Processing in Step S30 Regarding Synchronization>> FIG. 17 is an example of a flowchart showing a process (step S30) of performing bidirectional synchronization between the client terminal 20 and the cloud server 10. As shown in FIG. 17, a created list of files to be synchronized is read (step S31), and the files listed in this list are bidirectionally synchronized (uploaded and downloaded) between the cloud server 10 and the client terminal 20 (step S32).

[0090] An example of processing when the synchronization mode is "self" in which only files updated by the device itself are synchronized will be described with reference to Figs. 22 to 24. In Figure 22, a file with the note (addition) file name "AAAA.xml" for "ID1" and a file with the note (addition) file name "DDDD.xml" for "ID4" have been added to the list of files to be synchronized, so these files are uploaded from the client terminal 20 to the cloud server 10.

[0091] The CPU 11 of the cloud server 10 stores the upload date and time in the client terminal creation date and time / update date and time column T3c of the file update table T3 for the file with the memo (addition) file name "AAAA.xml" of "ID1" and the file with the memo (addition) file name "DDDD.xml" uploaded from the client terminal 20 (see FIG. 23). In FIG. 23, the file with the memo (addition) file name "AAAA.xml" of "ID1" was uploaded on "2023 / 05 / 19 13:01", and the file with the memo (addition) file name "DDDD.xml" of "ID4" was uploaded on "2023 / 05 / 19 13:02". The file with the memo (addition) file name "BBBB.xml" of "ID2" was uploaded by another user on "2023 / 05 / 19 11:14".

[0092] Next, the CPU 21 of the client terminal 20 downloads a file that has "selected" in the selected file column T6d and has a newer date and time in the client terminal creation date and time / update date and time column T3c than the client terminal download date and time column T6e. In Fig. 23, the file with the memo (addition) file name "AAAA.xml" of "ID1" has a date and time in column T6e of "2023 / 05 / 19 10:02" but a date and time in column T3c of "2023 / 5 / 19 13:01", so the file is downloaded (see Fig. 24). Similarly, download the "ID4" memo (addition) file named "DDDD.xml". In the above embodiment, as shown in FIG. 24, a file with the note (addition) file name "BBBB.xml" for "ID2" was downloaded, but in the modified example, as shown in FIG. 24, a file with the note (addition) file name "BBBB.xml" for "ID2" is not downloaded. In other words, in the modified example, a file uploaded by another user on "2023 / 05 / 19 11:14" (the note (addition) file name of "ID2" is "BBBB.xml") can be excluded from downloading (excluding from synchronization). 24, the CPU 21 of the client terminal 20 updates the date and time in the field T6e of the downloaded file, and deletes the information stored in the fields T6f and T6g.

[0093] As described above, in the system 1 according to the embodiment, the user of the client terminal 20 can select whether to synchronize all files or only files specified by the user (one example is a file that the user has updated). By synchronizing only files specified by the user (one example is a file that the user has updated), the files that the user has updated, i.e., the files that the user is responsible for, can be made up to date in a short time. This reduces the time required for data synchronization.

[0094] Although the embodiment of the present invention has been described above, the present invention is not limited to this, and can be practiced within the scope of the claims. [Explanation of symbols]

[0095] 1 System 10. Cloud Server 11 CPU 12 RAM 13 Input section 14 Display section 15 Communications Department 16 Memory section 17 Drawing storage device P1 Drawing processing program T1 File ID Table T2 Memo (addition) table T3 File Update Table 20 Client Terminals 21 CPU 22 RAM 23 Input section 24 Display 25 Communications Department 26 Memory section 27 Drawing storage device P2 Drawing processing program T4 File ID Table T5 Memo (addition) table T6 File Synchronization Management Table

Claims

1. A processing device comprising: a first processing unit that sets a mode related to file synchronization between the processing device and a first device; and a second processing unit that, when the set mode is a first mode in file synchronization, executes an upload process to the first device for a file that has been updated in the processing device among the files downloaded from the first device. A processing device comprising:

2. a third processing unit that, when the set mode is a second mode in file synchronization, executes an upload process to the first device for all files downloaded from the first device; 2. The processing device according to claim 1 .

3. The files involved in the synchronization include a drawing file and a memo file linked to the drawing file, and updates to the files are determined for each of the drawing file and the memo file; the second processing unit executes an upload process for uploading the updated drawing file and / or the updated memo file to the first device; 2. The processing device according to claim 1 .

4. the first processing unit sets the mode for the group of the drawing file and the memo file; 4. The processing device according to claim 3.

5. a fourth processing unit that, when the set mode is a first mode in file synchronization, executes a process of downloading a file that has been updated in a second device and uploaded from the second device to the first device; 2. The processing device according to claim 1 .

6. The computer of the processing device, a first processing unit that sets a mode related to file synchronization between the processing device and a first device; and functioning as a second processing unit that, when the set mode is a first mode in file synchronization, executes a process of uploading to the first device, among the files downloaded from the first device, files that have been updated in the processing device. A program characterized by:

7. A processing method for a processing device, comprising the steps of: The processing device includes: a first processing step of setting a mode relating to file synchronization between the processing device and a first device; and a second processing step of, if the set mode is a first mode in the file synchronization, executing an upload process to the first device for files that have been updated in the processing device among the files downloaded from the first device. A processing method comprising:

Images