Adapter device, file exchange system, file exchange method, and program

Abstract

To provide an adapter device, a file exchange system, a file exchange method, and a program, capable of suitably coping with update of a file exchange device.SOLUTION: A file exchange system comprises an adapter device 14 comprising: a communication unit 64 for performing communication with a file exchange device 16 on the basis of a predetermined communication protocol; a transmission processing unit 68 that, when a transmission object file to be an object of transmission is written in a shared directory 98, transmits a transmission file corresponding to the transmission object file in a transmission folder 100 to the file exchange device via the communication unit; and a reception processing unit 70 that, when receiving a reception file from the file exchange device via the communication unit, writes a received file corresponding to the reception file into the shared directory.SELECTED DRAWING: Figure 1

Description

Technical Field

[0001] The present invention relates to an adapter device, a file exchange system, a file exchange method, and a program.

Background Art

[0002] Patent Document 1 discloses a file exchange system capable of exchanging data files via a data server connected to a network.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] However, the file exchange device constituting the file exchange system may be updated. When the file exchange device is updated, each of a plurality of devices that communicate with the file exchange device is also updated. Updating each of the plurality of devices requires a huge cost. In addition, there is also a risk of security defects or the like occurring during the update of each device.

[0005] An object of the present invention is to solve the above-described problems.

Means for Solving the Problems

[0006] An adapter device according to one aspect of the present invention includes a communication unit that communicates with a file exchange device based on a predetermined communication protocol, and when a transmission target file to be transmitted is written in a shared directory, a transmission processing unit that transmits a transmission file corresponding to the transmission target file to the file exchange device via the communication unit, and a reception processing unit that writes a received file corresponding to the received file in the shared directory when receiving a received file from the file exchange device via the communication unit.

[0007] A file exchange system according to another aspect of the present invention is a file exchange system that performs file transmission and reception between one user and another user using a file exchange device, and includes a device operated by the one user and an adapter device including a communication unit that communicates with the file exchange device based on a predetermined communication protocol. The device includes a writing unit that writes a transmission target file, which is a file to be transmitted, in a shared directory, and the adapter device includes a transmission processing unit that transmits a transmission file corresponding to the transmission target file to the file exchange device via the communication unit when the transmission target file is written in the shared directory.

[0008] A file exchange method according to still another aspect of the present invention includes a step of checking whether a transmission target file to be transmitted is written in a shared directory, and a step of transmitting a transmission file corresponding to the transmission target file to a file exchange device via a communication unit based on a predetermined communication protocol when the transmission target file is written in the shared directory.

[0009] A program according to still another aspect of the present invention causes a computer to execute steps of: checking whether a transmission target file to be transmitted is written in a shared directory; and when the transmission target file is written in the shared directory, transmitting a transmission file corresponding to the transmission target file to a file exchange device via a communication unit based on a predetermined communication protocol.

Advantages of the Invention

[0010] According to the present invention, it is possible to provide an adapter device, a file exchange system, a file exchange method, and a program that can favorably cope with the update of a file exchange device.

Brief Description of the Drawings

[0011]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Embodiments for Carrying Out the Invention

[0012] [One Embodiment] An adapter device, a file exchange system, a file exchange method, and a program according to one embodiment will be described with reference to FIGS. 1 to 8. FIG. 1 is a block diagram showing a file exchange system according to this embodiment.

[0013] The file exchange system 10 according to this embodiment performs file transmission and reception between one user and another user using the file exchange device 16.

[0014] The file exchange system 10 may be composed of a device 12, an adapter device 14, a file exchange device 16, and a device 18.

[0015] The device 12 is provided, for example, in a certain office of a certain company. The user of the device 12 is, for example, an employee who works at the office where the device 12 is provided.

[0016] The device 18 is provided, for example, at a business partner of the company where the device 12 is provided. The user of the device 18 is, for example, an employee who works at the business partner.

[0017] File exchange using the file exchange device 16 can be performed between the user who operates the device 12 and the user who operates the device 18.

[0018] The device 12 may be provided in the first office among a plurality of offices belonging to a certain company, and the device 18 may be provided in the second office among such a plurality of offices.

[0019] The device 12 may be located in the first country, and the device 18 may be located in a second country different from the first country.

[0020] The device 12 may be provided with an arithmetic unit 22, a storage unit 24, an operation unit 26, and a display unit 28. Note that the device 12 may also be provided with components other than these components, but the description thereof is omitted here. For example, at least a part of the device 12 may be constituted by a server or the like provided outside the business office where the device 12 is installed.

[0021] The arithmetic unit 22 may be constituted by, for example, a processor such as a CPU (Central Processing Unit) or a GPU (Graphics Processing Unit), that is, a processing circuitry.

[0022] The arithmetic unit 22 may be provided with a control unit 30, a CDX format file generation unit 32, a writing unit 34, a reading unit 36, a transmission ACK confirmation unit 38, a reception ACK generation unit 40, and a display control unit 42. The control unit 30, the CDX format file generation unit 32, the writing unit 34, the reading unit 36, the transmission ACK confirmation unit 38, the reception ACK generation unit 40, and the display control unit 42 may be realized by a program stored in the storage unit 24 being executed by the arithmetic unit 22. Note that the arithmetic unit 22 may also be provided with components other than these components, but the description thereof is omitted here.

[0023] Note that at least a part of the control unit 30, the CDX format file generation unit 32, the writing unit 34, the reading unit 36, the transmission ACK confirmation unit 38, the reception ACK generation unit 40, and the display control unit 42 may be realized by an integrated circuit such as an ASIC (Application Specific Integrated Circuit) or an FPGA (Field-Programmable Gate Array). Further, at least a part of the control unit 30, the CDX format file generation unit 32, the writing unit 34, the reading unit 36, the transmission ACK confirmation unit 38, the reception ACK generation unit 40, and the display control unit 42 may be constituted by an electronic circuit including discrete devices.

[0024] The storage unit 24 may include a volatile memory (not shown) and a non-volatile memory (not shown). Examples of the volatile memory may include a RAM (Random Access Memory) or the like. The volatile memory is used as the working memory of the processor and temporarily stores data and the like necessary for processing or calculation. Examples of the non-volatile memory may include a ROM (Read Only Memory), a flash memory, or the like. The non-volatile memory is used as a storage memory and stores programs, tables, maps, and the like. At least a part of the storage unit 24 may be provided in the above-described processor, integrated circuit, or the like. Further, the storage unit 24 may be further provided with an HDD (Hard Disk Drive), an SSD (Solid State Drive), or the like. Various applications (application programs) may be installed in the storage unit 24. For example, a CAD (Computer-Aided Design) application or the like may be installed in the storage unit 24. Further, the storage unit 24 may be provided with a destination database 44, that is, a destination DB. The storage unit 24 may be further provided with a transmission / reception history storage unit 45. The destination database 44 stores information indicating the destination (transmission destination) of the file. The transmission / reception history storage unit 45 stores a transmission / reception history, which is a history of file transmission and reception. The transmission / reception history includes a transmission / reception management number sequentially assigned to the file transmission and reception and information indicating the status of the transmission and reception. In order to enable tracking when a confidentiality leak occurs, the transmission / reception history is retained in the transmission / reception history storage unit 45 even after the file transmission and reception is completed.

[0025] The operation unit 26 can be used when the user performs an operation input on the device 12. Examples of the operation unit 26 may include, but are not limited to, a keyboard, a mouse, and the like. The display unit 28 is provided with a display element (not shown). As the display element, for example, a liquid crystal display element, an organic electroluminescence display element, or the like may be used. The operation unit 26 and the display unit 28 may be configured by a touch panel (not shown) provided with such a display element.

[0026] The device 18 may be provided with an arithmetic unit 46, a storage unit 48, an operation unit 50, a display unit 52, and a communication unit 54. Note that the device 18 may be provided with components other than these components, but the description thereof is omitted here.

[0027] The arithmetic unit 46 may be constituted by a processor such as a CPU or a GPU, that is, a processing circuit. The arithmetic unit 46 may be provided with a control unit 56 and a display control unit 58. The control unit 56 and the display control unit 58 may be realized by a program stored in the storage unit 48 being executed by the arithmetic unit 46. Note that the arithmetic unit 46 may be provided with components other than these components, but the description thereof is omitted here. The control unit 56 controls the entire device 18. The display control unit 58 may control the screen display of the display unit 52. Note that at least a part of the control unit 56 and the display control unit 58 may be realized by an integrated circuit such as an ASIC or an FPGA. Also, at least a part of the control unit 56 and the display control unit 58 may be constituted by an electronic circuit including discrete devices.

[0028] The storage unit 48 may include a volatile memory (not shown) and a non-volatile memory (not shown). Further, the storage unit 48 may be further provided with an HDD, an SSD, or the like.

[0029] The operation unit 50 may be used when a user performs an operation input on the device 18. Examples of the operation unit 50 include, but are not limited to, a keyboard, a mouse, and the like. The display unit 52 is provided with a display element (not shown).

[0030] The communication unit 54 is provided with, for example, a communication module (not shown). The communication unit 54 can transmit and receive data to and from the communication unit 96 described later via a network 20 such as the Internet.

[0031] The adapter device 14 may be provided with an arithmetic unit 60, a storage unit 62, and a communication unit 64. Note that the adapter device 14 may be provided with components other than these components, but the description thereof is omitted here.

[0032] The arithmetic unit 60 can be constituted by, for example, a processor such as a CPU or a GPU, that is, a processing circuit.

[0033] The storage unit 62 can include a volatile memory (not shown) and a non-volatile memory (not shown). Further, the storage unit 62 can be further provided with an HDD, an SSD, etc. The storage unit 62 can be provided with a destination database 61 and a transmission / reception history storage unit 63. Information indicating the destination of a file is stored in the destination database 61. The transmission / reception history is stored in the transmission / reception history storage unit 63. The transmission / reception history includes a transmission / reception management number sequentially assigned to the transmission / reception of a file and the status of the transmission / reception. The transmission / reception history is retained in the transmission / reception history storage unit 63 even after the transmission / reception of a file is completed in order to enable tracking in the event of a confidentiality leak.

[0034] The communication unit 64 is provided with, for example, a communication module (not shown). The communication unit 64 can transmit and receive data to and from the communication unit 96 via a network (not shown) or the like.

[0035] The arithmetic unit 60 can be provided with a control unit 66, a transmission processing unit 68, and a reception processing unit 70. The control unit 66, the transmission processing unit 68, and the reception processing unit 70 can be realized by the arithmetic unit 60 executing a program stored in the storage unit 62. Note that the arithmetic unit 60 can also be provided with components other than these components, but the description thereof is omitted here. Note that at least a part of the control unit 66, the transmission processing unit 68, and the reception processing unit 70 may be realized by an integrated circuit such as an ASIC or an FPGA. Further, at least a part of the control unit 66, the transmission processing unit 68, and the reception processing unit 70 may be constituted by an electronic circuit including discrete devices.

[0036] The transmission processing unit 68 may include a CDX format file acquisition unit 72, a comment file analysis unit 74, a file transmission unit 76, a transmission status acquisition unit 78, and a transmission ACK generation unit 80. The CDX format file acquisition unit 72, the comment file analysis unit 74, the file transmission unit 76, the transmission status acquisition unit 78, and the transmission ACK generation unit 80 may be realized by a program stored in the storage unit 62 being executed by the arithmetic unit 60.

[0037] The reception processing unit 70 may include a new arrival information acquisition unit 82, a file reception unit 84, a CDX format conversion unit 86, a reception ACK confirmation unit 88, and a reception status update unit 90. The new arrival information acquisition unit 82, the file reception unit 84, the CDX format conversion unit 86, the reception ACK confirmation unit 88, and the reception status update unit 90 may be realized by a program stored in the storage unit 62 being executed by the arithmetic unit 60.

[0038] The file exchange device 16 may include an arithmetic unit 92, a storage unit 94, and a communication unit 96. Note that the file exchange device 16 may also include components other than these components, but the description thereof is omitted here.

[0039] The arithmetic unit 92 may be constituted by a processor such as a CPU or a GPU, that is, a processing circuit. The arithmetic unit 92 may include a control unit 97. The control unit 97 controls the entire file exchange device 16. Note that at least a part of the control unit 97 may be realized by an integrated circuit such as an ASIC or an FPGA. Also, at least a part of the control unit 97 may be constituted by an electronic circuit including discrete devices.

[0040] The storage unit 94 may include a volatile memory (not shown) and a non-volatile memory (not shown). Further, the storage unit 94 may be further provided with an HDD, an SSD, etc. The storage unit 94 may be provided with a destination database 93 and a transmission / reception history storage unit 95. Information indicating the destination of a file is stored in the destination database 93. The transmission / reception history storage unit 95 stores the transmission / reception history. The transmission / reception history includes a transmission / reception management number sequentially assigned to the transmission / reception of a file and the status of the transmission / reception. In order to enable tracking in the event of a confidentiality leak, the transmission / reception history is retained in the transmission / reception history storage unit 95 even after the transmission / reception of a file is completed.

[0041] The communication unit 96 is provided with, for example, a communication module (not shown). The communication unit 96 can transmit and receive data to and from the communication unit 54 via a network 20 such as the Internet. Further, the communication unit 96 can transmit and receive data to and from the communication unit 64 via a network (not shown).

[0042] The shared directory 98 can be set, for example, in a storage unit (storage) (not shown) provided in an NFS (Network File System) server (not shown). The storage area corresponding to the shared directory 98 is mounted on the local storage constituted by the storage unit 24 by NFS. Further, the storage area corresponding to the shared directory 98 is mounted on the local storage constituted by the storage unit 62 by NFS. The device 12 and the adapter device 14 can each access the shared directory 98.

[0043] The shared directory 98 may be provided with a transmission folder 100, a transmission ACK folder 102, a reception folder 104, and a reception ACK folder 106.

[0044] As described above, the device 12 may be provided with a control unit 30. The control unit 30 is in charge of overall control of the device 12.

[0045] As described above, the device 12 may be provided with a CDX format file generation unit 32. The CDX format file generation unit 32 generates a transmission target file 108 which is a file to be transmitted. FIG. 2A is a diagram conceptually showing an example of the transmission target file. In FIG. 2A, a state where the transmission target file 108 is written in the transmission folder 100 is conceptually shown. As shown in FIG. 2A, the transmission target file 108 includes a transmission comment file 110, a transmission target data file 112, and a transmission token file 114. The transmission target data file 112 contains transmission target data which is data to be transmitted. The transmission target data may include, for example, but is not limited to, CAD data generated by CAD. The transmission comment file 110 contains comments (comment information) regarding the transmission target data. The transmission comment file 110 may include destination information indicating the destination of the transmission target file 108. Also, the transmission comment file 110 may include transmission source information indicating the transmission source of the transmission target file 108. The transmission token file 114 contains authentication information. The transmission token file 114 serves to indicate that both the writing of the transmission comment file 110 to the transmission folder 100 and the writing of the transmission target data file 112 to the transmission folder 100 have been completed. Therefore, after the writing of the transmission comment file 110 to the transmission folder 100 and the writing of the transmission target data file 112 to the transmission folder 100 are completed, the writing of the transmission token file 114 to the transmission folder 100 is performed.

[0046] At the beginning of the file name of the transmission comment file 110, as will be described later, a type code "C" is attached. At the beginning of the file name of the transmission target data file 112, as will be described later, a type code "D" is described. At the beginning of the file name of the transmission token file 114, as will be described later, a type code "X" is described. For this reason, a file having such a configuration may be referred to as a CDX format file. These files 110, 112, 114 constituting the CDX format transmission target file 108 are associated with each other.

[0047] FIG. 3A is a diagram showing an example of a file name. The file name of the transmission comment file 110, the file name of the data file 112 to be transmitted, and the file name of the transmission token file 114 are shown in FIG. 3A.

[0048] As shown in FIG. 3A, the file name may be composed of a type code, a destination code, date and time information, a management number, and free information. The type code is information indicating the type of the file. The type code is described at the beginning of the file name. The type code of the transmission comment file 110 is "C". The type code of the data file 112 to be transmitted is "D". The type code of the transmission token file 114 is "X".

[0049] The destination code is information indicating the destination (transmission destination) of the file. Note that the destination code corresponding to each destination is stored in the destination database 44.

[0050] The date and time information is information indicating the date and time (year, month, day, hour, minute, second) when the data file 112 to be transmitted was generated.

[0051] The destination code and date and time information in the transmission comment file 110 corresponding to the data file 112 to be transmitted are the same as the destination code and date and time information in the data file 112 to be transmitted. Also, the destination code and date and time information in the transmission token file 114 corresponding to the data file 112 to be transmitted are the same as the destination code and date and time information in the data file 112 to be transmitted. These three files 110, 112, and 114 are associated with each other because the information included in the file names matches each other.

[0052] As described above, the device 12 may be provided with a writing unit 34. The writing unit 34 writes the transmission target file 108 generated by the CDX format file generation unit 32 into the transmission folder 100. That is, the writing unit 34 writes the transmission target file 108 in the CDX format into the transmission folder 100.

[0053] As described above, the device 12 may be provided with a reading unit 36. The reading unit 36 checks whether the transmission ACK token file 113 has been written into the transmission ACK folder 102. FIG. 2B is a diagram conceptually showing an example of the transmission ACK file and the transmission ACK token file. In FIG. 2B, a state where the transmission ACK file 115 and the transmission ACK token file 113 are written in the transmission ACK folder 102 is conceptually shown. The transmission ACK file 115 and the transmission ACK token file 113 are written into the transmission ACK folder 102 by the adapter device 14 as will be described later. The transmission ACK token file 113 serves to indicate that the writing of the transmission ACK file 115 into the transmission ACK folder 102 has been completed. For this reason, after the writing of the transmission ACK file 115 into the transmission ACK folder 102 is completed, the transmission ACK token file 113 is written into the transmission ACK folder 102. When the transmission ACK token file 113 is written in the transmission ACK folder 102, the reading unit 36 reads the transmission ACK file 115 written in the transmission ACK folder 102. The transmission ACK file 115 includes a status code indicating the status of file transmission. The reading unit 36 repeats the reading process from the transmission ACK folder 102 until a transmission ACK file 115 including a status code indicating that the file transmission has been completed or a transmission ACK file 115 indicating a status code indicating that an error has occurred in the file transmission is obtained.

[0054] FIG. 3B is a diagram showing an example of file names. The file name of the transmission ACK file 115 and the file name of the transmission ACK token file 113 are shown in FIG. 3B.

[0055] As shown in FIG. 3B, the file name may be composed of a type code, a destination code, date and time information, a management number, and free information. The type code of the transmission ACK file 115 is "A". The type code of the transmission ACK token file 113 is "X". The destination code and date and time information in the files 110, 112, and 114 that make up the transmission target file 108 are the same as the destination code and date and time information in the transmission ACK file 115 generated when the transmission of the transmission file 1081 (see FIG. 6A) corresponding to the transmission target file 108 is completed. Also, the destination code and date and time information in the transmission ACK token file 113 corresponding to the transmission ACK file 115 are the same as the destination code and date and time information in the transmission ACK file 115. The transmission ACK file 115 and the transmission ACK token file 113 are associated with each other because these information included in the file names match each other.

[0056] As described above, the device 12 may be provided with a transmission ACK confirmation unit 38. The transmission ACK confirmation unit 38 confirms the transmission ACK file 115 read by the reading unit 36 from the transmission ACK folder 102. When the destination code and date and time information in the transmission ACK file 115 match the destination code and date and time information in the files 110, 112, and 114 that make up the transmission target file 108, and a status code indicating that the transmission of the file is completed is included in the transmission ACK file 115, the transmission ACK confirmation unit 38 performs the following processing. That is, in such a case, the transmission ACK confirmation unit 38 determines that the transmission of the transmission file 1081 corresponding to the transmission target file 108 is completed.

[0057] The reading unit 36 can read the received file 116, which will be described later and is written in the reception folder 104. Note that the received file 116 is written in the reception folder 104 by the adapter device 14 as will be described later. FIG. 4A is a diagram conceptually showing an example of the received file. In FIG. 4A, a state where the received file 116 is written in the reception folder 104 is conceptually shown. As shown in FIG. 4A, the received file 116 includes a received comment file 118, a received data file 120, and a received token file 122. The received data file 120 contains received data that has been received. The received comment file 118 contains comments regarding the received data. The received comment file 118 may include destination information indicating the destination of the received file 116. Also, the received comment file 118 may include source information indicating the source of the received file 116. The received token file 122 contains authentication information.

[0058] At the beginning of the file name of the received comment file 118, a type code "C" is attached as will be described later. At the beginning of the file name of the received data file 120, a type code "D" is described as will be described later. At the beginning of the file name of the received token file 122, a type code "X" is described as will be described later. As described above, a file in such a format can be referred to as a CDX format file. These files 118, 120, 122 that constitute the received file 116 in CDX format are associated with each other.

[0059] FIG. 5A is a diagram showing an example of the file name. The file name of the received comment file 118, the file name of the received data file 120, and the file name of the received token file 122 are shown in FIG. 5A.

[0060] As shown in FIG. 5A, the file name may be composed of a type code, a destination code, date and time information, a management number, and free information. The type code of the received comment file 118 is "C". The type code of the received data file 120 is "D". The type code of the received token file 122 is "X". The destination code and the date and time information in the received comment file 118 corresponding to the received data file 120 are the same as those in the received data file 120. Also, the destination code and the date and time information in the received token file 122 corresponding to the received data file 120 are the same as those in the received data file 120. These three files 118, 120, and 122 are associated with each other because the information included in the file names is the same as each other.

[0061] As described above, the device 12 may be provided with a received ACK generation unit 40. The received ACK generation unit 40 generates a received ACK file 124 corresponding to the received file 116 read by the reading unit 36 from the received folder 104. FIG. 4B is a diagram conceptually showing an example of the received ACK file and the received ACK token file. In FIG. 4B, a state in which the received ACK file 124 and the received ACK token file 123 are written in the received ACK folder 106 is conceptually shown. The received ACK file 124 includes a status code indicating the status of file reception. For example, the received ACK file 124 includes a status code indicating that the reception of the received file 116 has been completed. More specifically, the received ACK file 124 includes a status code indicating that the received file 116 has been acquired by the device 12. The received ACK generation unit 40 includes the destination code and date / time information in the received ACK file 124 that match the destination code and date / time information included in the files 118, 120, and 122 constituting the received file 116. The received ACK generation unit 40 further generates a received ACK token file 123. The received ACK token file 123 serves to indicate that the writing of the received ACK file 124 to the received ACK folder 106 has been completed. Therefore, after the received ACK file 124 is written in the received ACK folder 106, the received ACK token file 123 is written in the received ACK folder 106.

[0062] FIG. 5B is a diagram showing an example of file names. The file name of the received ACK file 124 and the file name of the received ACK token file 123 are shown in FIG. 5B.

[0063] As shown in FIG. 5B, the file name can be composed of a type code, a destination code, date and time information, a management number, and free information. The type code of the received ACK file 124 is "A". The type code of the received ACK token file 123 is "X". The destination code and date and time information in the files 118, 120, and 122 that make up the received file 116 are identical to the destination code and date and time information in the received ACK file 124 generated when the reception of the received file 116 is completed. Also, the destination code and date and time information in the received ACK token file 123 corresponding to the received ACK file 124 are identical to the destination code and date and time information in the received ACK file 124. The received ACK file 124 and the received ACK token file 123 are associated with each other by virtue of these pieces of information included in the file name being identical to each other.

[0064] The writing unit 34 can write the received ACK file 124 generated by the received ACK generation unit 40 into the received ACK folder 106. Also, the writing unit 34 can write the received ACK token file 123 generated by the received ACK generation unit 40 into the received ACK folder 106. After writing the received ACK file 124 into the received ACK folder 106, the writing unit 34 writes the received ACK token file 123 into the received ACK folder 106.

[0065] As described above, the device 12 may be provided with a display control unit 42. The display control unit 42 can control the screen display of the display unit 28. The display control unit 42 can display on the display unit 28 a transmission screen for transmitting data to be transmitted. The data to be transmitted can be selected on the transmission screen. Also, an operation for transmitting the selected data can be performed on the transmission screen. The display control unit 42 can display on the display unit 28 information indicating that the transmission of the transmission target file 108 has been completed. Also, the display control unit 42 can display on the display unit 28 information indicating that the reception of the received file 116 has been completed.

[0066] As described above, the adapter device 14 may be provided with a control unit 66. The control unit 66 controls the entire adapter device 14.

[0067] As described above, the adapter device 14 may be provided with a CDX format file acquisition unit 72. The CDX format file acquisition unit 72 checks at a predetermined time interval whether the transmission target file 108 is written in the transmission folder 100. This time interval is, for example, one minute. Specifically, the CDX format file acquisition unit 72 checks whether the transmission token file 114 is written in the transmission folder 100. When the transmission token file 114 is written in the transmission folder 100, the CDX format file acquisition unit 72 makes the following determination. That is, in such a case, the CDX format file acquisition unit 72 determines that the transmission comment file 110 and the transmission target data file 112 corresponding to the transmission token file 114 are written in the transmission folder 100. After that, the CDX format file acquisition unit 72 reads out the transmission comment file 110 and the transmission target data file 112 associated with the transmission token file 114 from the transmission folder 100 together with the transmission token file 114.

[0068] As described above, the adapter device 14 may be provided with a comment file analysis unit 74. The comment file analysis unit 74 generates a transmission meta file 126 and a transmission config file 130 based on comment information and the like included in the transmission comment file 110. FIG. 6A is a diagram conceptually showing a transmission file. As shown in FIG. 6A, the transmission file 1081 may be composed of a transmission meta file 126, transmission data 128, and a transmission config file 130. The transmission meta file 126 may include transmission command parameters. The transmission meta file 126 may include destination information indicating the destination of the transmission file 1081. The transmission meta file 126 may include transmission source information indicating the transmission source of the transmission file 1081. The transmission data 128 may be composed of data included in the transmission target data file 112.

[0069] As described above, the adapter device 14 may be provided with a file transmission unit 76. The file transmission unit 76 transmits the transmission data 128 based on the transmission command parameters included in the transmission meta file 126 and the information included in the transmission configuration file 130. The file transmission unit 76 transmits the transmission data 128 to the file exchange device 16 via the communication unit 64. The communication unit 64 communicates with the communication unit 96 provided in the file exchange device 16. The communication between the communication unit 64 and the communication unit 96 is performed based on a predetermined communication protocol.

[0070] As described above, the adapter device 14 may be provided with a transmission status acquisition unit 78. The transmission status acquisition unit 78 can acquire the transmission status information supplied from the file exchange device 16 via the communication unit 64.

[0071] As described above, the adapter device 14 may be provided with a transmission ACK generation unit 80. The transmission ACK generation unit 80 can determine the transmission status regarding the transmission file 1081 based on the transmission status information acquired by the transmission status acquisition unit 78. The transmission ACK generation unit 80 can determine whether or not the transmission of the transmission file 1081 to the destination has been completed based on the transmission status information. When it is determined that the transmission of the transmission file 1081 to the destination has been completed, the transmission ACK generation unit 80 generates a transmission ACK file 115. The transmission ACK generation unit 80 writes the transmission ACK file 115 generated by the transmission ACK generation unit 80 into the transmission ACK folder 102. After writing the transmission ACK file 115 into the transmission ACK folder 102, the transmission ACK generation unit 80 writes a transmission ACK token file 113 into the transmission ACK folder 102.

[0072] The transmission processing unit 68 is composed of a CDX format file acquisition unit 72, a comment file analysis unit 74, a file transmission unit 76, a transmission status acquisition unit 78, and a transmission ACK generation unit 80. When the transmission target file 108 is written in the shared directory 98, the transmission processing unit 68 can transmit a transmission file 1081 corresponding to the transmission target file 108 to the file exchange device 16 via the communication unit 64.

[0073] As described above, the adapter device 14 may be provided with a new arrival information acquisition unit 82. The new arrival information acquisition unit 82 can acquire new arrival information supplied from the file exchange device 16 via the communication unit 64. The new arrival information is information indicating that the file exchange device 16 has newly received a received file 1161 destined for the device 12.

[0074] As described above, the adapter device 14 may be provided with a file reception unit 84. The file reception unit 84 can determine, based on the new arrival information acquired by the new arrival information acquisition unit 82, that the file exchange device 16 has newly received a received file 1161 destined for the device 12. When the file reception unit 84 determines that the file exchange device 16 has newly received a received file 1161 destined for the device 12, the file reception unit 84 performs the following processing. That is, in such a case, the file reception unit 84 receives the received file 1161 from the file exchange device 16 via the communication unit 64. FIG. 6B is a diagram conceptually showing a received file. As shown in FIG. 6B, the received file 1161 may be composed of a received metadata file 132, received data 134, and a received config file 136. The received metadata file 132 may contain received command parameters. Further, the received metadata file 132 may contain destination information indicating the destination of the received data 134. Further, the received metadata file 132 may contain source information indicating the source of the received data 134.

[0075] As described above, the adapter device 14 may be provided with a CDX format conversion unit 86. The CDX format conversion unit 86 generates a received file 116 in the CDX format based on the received file 1161. The CDX format conversion unit 86 writes the generated received file 116 into the reception folder 104.

[0076] As described above, the adapter device 14 may be provided with a reception ACK confirmation unit 88. The reception ACK confirmation unit 88 checks whether a reception ACK token file 123 is written in the reception ACK folder 106. When the reception ACK token file 123 is written in the reception ACK folder 106, the reception ACK confirmation unit 88 reads out a reception ACK file 124 written in the reception ACK folder 106. The reception ACK file 124 includes a status code indicating the reception status of the file. When the destination code and the date / time information in the reception ACK file 124 match the destination code and the date / time information in the files 118, 120, and 122 constituting the received file 116, and the reception ACK file 124 includes a status code indicating that the reception of the file is completed, the reception ACK confirmation unit 88 performs the following processing. That is, in such a case, the reception ACK confirmation unit 88 determines that the reception of the received file 116 corresponding to the received file 1161 is completed.

[0077] As described above, the adapter device 14 may be provided with a reception status update unit 90. When the reception of the received file 116 corresponding to the received file 1161 is completed, the reception status update unit 90 transmits reception status information indicating that the reception of the received file 116 is completed to the file exchange device 16 via the communication unit 64. In other words, the reception status update unit 90 transmits reception status information indicating that the reception of the received file 1161 is completed to the file exchange device 16 via the communication unit 64.

[0078] The receiving processing unit 70 is composed of a new information acquisition unit 82, a file receiving unit 84, a CDX format conversion unit 86, a received ACK confirmation unit 88, and a received status update unit 90. When the receiving processing unit 70 receives the received file 1161 from the file exchange device 16 via the communication unit 64, it can write the received file 116 corresponding to the received file 1161 into the shared directory 98.

[0079] Next, the operation of the file exchange system according to this embodiment will be described. FIG. 7 is a flowchart showing an example of the operation of the file exchange system according to this embodiment. An example of the case of transmitting a file is shown in FIG. 7.

[0080] First, in step S1, the data to be transmitted is selected by the user. The selection of the data to be transmitted can be performed on the transmission screen displayed on the display unit 28 provided in the device 12. After that, the process proceeds to step S2.

[0081] In step S2, the CDX format file generation unit 32 provided in the device 12 generates the transmission target file 108. As described above with reference to FIG. 2A, the transmission target file 108 includes a transmission comment file 110, a transmission target data file 112, and a transmission token file 114. After that, the process proceeds to step S3.

[0082] In step S3, the writing unit 34 provided in the device 12 writes the transmission target file 108 into the transmission folder 100. That is, the writing unit 34 writes the CDX format transmission target file 108 into the transmission folder 100. After that, the process proceeds to step S4.

[0083] In step S4, the CDX format file acquisition unit 72 provided in the adapter device 14 checks whether the transmission target file 108 has been written into the transmission folder 100. If the transmission target file 108 is written in the transmission folder 100, the process proceeds to step S5.

[0084] In step S5, the CDX format file acquisition unit 72 reads the transmission target file 108 from the transmission folder 100. After that, the process proceeds to step S6.

[0085] In step S6, the comment file analysis unit 74 provided in the adapter device 14 generates a transmission metadata file 126 and a transmission configuration file 130 based on the comment information and the like included in the transmission comment file 110. After that, the process proceeds to step S7.

[0086] In step S7, the file transmission unit 76 provided in the adapter device 14 transmits the transmission file 1081 based on the transmission command parameters included in the transmission metadata file 126 and the information included in the transmission configuration file 130. The file transmission unit 76 transmits the transmission file 1081 to the file exchange device 16 via the communication unit 64 based on a predetermined communication protocol. The destination of the transmission data 128 is, for example, the device 18. The control unit 97 provided in the file exchange device 16 transfers the transmission file 1081 supplied from the adapter device 14 to the device 18 via the communication unit 96 and the network 20. Note that the transmission file 1081 supplied from the adapter device 14 may be temporarily stored in the storage unit 94 provided in the file exchange device 16. In this way, the transmission file 1081 is transmitted to the device 18 which is the destination of the transmission file 1081. When the transmission of the transmission file 1081 is completed, the process proceeds to step S8.

[0087] In step S8, the control unit 97 supplies transmission status information indicating that the transmission of the transmission file 1081 to the device 18 has been completed to the adapter device 14 via the communication unit 96. After that, the process proceeds to step S9.

[0088] In step S9, the transmission status acquisition unit 78 provided in the adapter device 14 acquires the transmission status information indicating that the transmission of the transmission file 1081 to the device 18 has been completed. After that, the process proceeds to step S10.

[0089] In step S10, the transmission ACK generation unit 80 provided in the adapter device 14 generates a transmission ACK file 115. The transmission ACK generation unit 80 further generates a transmission ACK token file 113. The transmission ACK generation unit 80 writes the generated transmission ACK file 115 into the transmission ACK folder 102. After writing the transmission ACK file 115 into the transmission ACK folder 102, the transmission ACK generation unit 80 writes the transmission ACK token file 113 into the transmission ACK folder 102. Thereafter, the process proceeds to step S11.

[0090] In step S11, the reading unit 36 provided in the device 12 checks whether the transmission ACK token file 113 is written in the transmission ACK folder 102. If the transmission ACK token file 113 is written in the transmission ACK folder 102, the reading unit 36 reads the transmission ACK file 115 written in the transmission ACK folder 102. Thereafter, the process proceeds to step S12.

[0091] In step S12, the transmission ACK confirmation unit 38 provided in the device 12 checks the transmission ACK file 115 read by the reading unit 36. If the destination code and date / time information in the transmission ACK file 115 match the destination code and date / time information in the files 110, 112, and 114 that make up the transmission target file 108, and the status code indicating that the transmission of the file is completed is included in the transmission ACK file 115, the transmission ACK confirmation unit 38 performs the following processing. That is, in such a case, the transmission ACK confirmation unit 38 determines that the transmission of the transmission file 1081 corresponding to the transmission target file 108 is completed.

[0092] In this way, the file is transmitted.

[0093] FIG. 8 is a flowchart showing an example of the operation of the file exchange system according to the present embodiment. An example of the case of receiving a file is shown in FIG. 8.

[0094] In step S21, the new arrival information acquisition unit 82 provided in the adapter device 14 checks whether the new arrival information has been supplied from the file exchange device 16. The new arrival information is information indicating that the file exchange device 16 has newly received the received file 1161 addressed to the device 12. If the new arrival information has not been supplied from the file exchange device 16 (NO in step S21), step S21 is repeated. If the new arrival information has been supplied from the file exchange device 16 (YES in step S21), the process proceeds to step S22.

[0095] In step S22, the file reception unit 84 provided in the adapter device 14 receives the received file 1161 from the file exchange device 16. After that, the process proceeds to step S23.

[0096] In step S23, the CDX format conversion unit 86 provided in the adapter device 14 generates the received file 116 in CDX format based on the received file 1161. After that, the process proceeds to step S24.

[0097] In step S24, the CDX format conversion unit 86 provided in the adapter device 14 writes the generated received file 116 into the reception folder 104. After that, the process proceeds to step S25.

[0098] In step S25, the reading unit 36 provided in the device 12 reads the received file 116 from within the reception folder 104. After that, the process proceeds to step S26.

[0099] In step S26, the reception ACK generation unit 40 provided in the device 12 generates a reception ACK file 124 corresponding to the received file 116. The reception ACK generation unit 40 further generates a reception ACK token file 123. After that, the process proceeds to step S27.

[0100] In step S27, the writing unit 34 provided in the device 12 writes the received ACK file 124 into the received ACK folder 106. After that, the writing unit 34 further writes the received ACK token file 123 into the received ACK folder 106. Then, the process proceeds to step S28.

[0101] In step S28, the received ACK confirmation unit 88 provided in the adapter device 14 checks whether the received ACK token file 123 is written in the received ACK folder 106. If the received ACK token file 123 is written in the received ACK folder 106, the received ACK confirmation unit 88 reads out the received ACK file 124 written in the received ACK folder 106. Then, the process proceeds to step S29.

[0102] In step S29, the received status update unit 90 transmits received status information indicating that the received file 116 corresponding to the received file 1161 has been received by the device 12 to the file exchange device 16. In other words, the received status update unit 90 transmits received status information indicating that the reception of the received file 1161 has been completed to the file exchange device 16.

[0103] In this way, the file is received.

[0104] As described above, according to the present embodiment, file transfer between the device 12 and the adapter device 14 is performed in the shared directory 98. Communication is not performed between the device 12 and the file exchange device 16, and communication is performed between the communication unit 64 provided in the adapter device 14 and the file exchange device 16. When the file exchange device 16 is updated, the communication unit 64 provided in the adapter device 14 is updated, and it is not necessary to update the device 12. That is, according to the present embodiment, it is possible to cope with the update of the file exchange device 16 without updating the device 12. The adapter device 14 is provided for each of the plurality of devices 12. When the file exchange device 16 is updated, the adapter devices 14 provided for each of the plurality of devices 12 can be updated collectively. According to the present embodiment, since it is not necessary to update each of the plurality of devices 12 individually when the file exchange device 16 is updated, it can contribute to a reduction in the update cost. Thus, according to the present embodiment, it is possible to favorably cope with the update of the file exchange device 16.

[0105] Note that the present invention is not limited to the above-described embodiment, and various configurations can be adopted without departing from the gist of the present invention.

[0106] The invention that can be grasped from the above embodiment will be described below.

[0107] The adapter device (14) includes a communication unit (64) that communicates with a file exchange device (16) based on a predetermined communication protocol, and when a transmission target file (108) to be transmitted is written in a shared directory (98), a transmission processing unit (68) that transmits a transmission file (1081) corresponding to the transmission target file to the file exchange device via the communication unit, and a reception processing unit (70) that, when receiving a received file (1161) from the file exchange device via the communication unit, writes a received file (116) corresponding to the received file into the shared directory. According to such a configuration, between the device and the adapter device, the transfer of files is performed in the shared directory. Communication is not performed between the device and the file exchange device, and communication is performed between the communication unit provided in the adapter device and the file exchange device. When the file exchange device is updated, the communication unit provided in the adapter device is updated, and it is not necessary to update the device. That is, according to such a configuration, it is possible to cope with the update of the file exchange device without updating the device. The adapter device is provided for each of a plurality of devices. When the file exchange device is updated, the adapter devices provided for each of the plurality of devices can be updated collectively. According to such a configuration, when the file exchange device is updated, it is not necessary to update each of the plurality of devices individually, so it can contribute to reducing the update cost. According to such a configuration, it is possible to favorably cope with the update of the file exchange device.

[0108] The transmission target file may be written in a transmission folder (100) provided in the shared directory.

[0109] The received file may be written in a reception folder (104) provided in the shared directory.

[0110] The transmission target file may include destination information indicating the destination of the transmission file.

[0111] The received file may include source information indicating the source of the received file.

[0112] The file to be transmitted may include a transmission target data file (112) including transmission target data which is data to be transmitted, a transmission comment file (110) associated with the transmission target data file and including a comment regarding the transmission target data, and a transmission token file (114) associated with the transmission target data file and including a token.

[0113] The received file may include a received data file (120) including received data which is received data, a reception comment file (118) associated with the received data file and including a comment regarding the received data, and a reception token file (122) associated with the received data file and including a token.

[0114] A file exchange system (10) is a file exchange system that performs file transmission and reception between one user and another user using a file exchange device, and includes a device (12) operated by the one user, and an adapter device including a communication unit that communicates with the file exchange device based on a predetermined communication protocol. The device includes a writing unit (34) that writes a file to be transmitted, which is a transmission target file, to a shared directory. The adapter device includes a transmission processing unit that transmits a transmission file corresponding to the transmission target file to the file exchange device via the communication unit when the transmission target file is written to the shared directory.

[0115] The adapter device may further include a reception processing unit that writes a received file corresponding to the received file to the shared directory when receiving the received file from the file exchange device via the communication unit. The device may further include a reading unit (36) that reads the received file written to the shared directory.

[0116] The file exchange method includes a step (S4) of checking whether a transmission target file to be transmitted is written in a shared directory, and a step (S7) of, when the transmission target file is written in the shared directory, transmitting a transmission file corresponding to the transmission target file to a file exchange device via a communication unit based on a predetermined communication protocol.

[0117] The method may further include a step (S22) of receiving a received file from the file exchange device via the communication unit based on the communication protocol, and a step (S24) of, when the received file is received from the file exchange device via the communication unit, writing a received file corresponding to the received file in the shared directory.

[0118] The program causes a computer to execute a step of checking whether a transmission target file to be transmitted is written in a shared directory, and a step of, when the transmission target file is written in the shared directory, transmitting a transmission file corresponding to the transmission target file to a file exchange device via a communication unit based on a predetermined communication protocol.

[0119] The program may further cause the computer to execute a step of receiving a received file from the file exchange device via the communication unit based on the communication protocol, and a step of, when the received file is received from the file exchange device via the communication unit, writing a received file corresponding to the received file in the shared directory.

Description of Reference Numerals

[0120] 10: File exchange system 12, 18: Devices 14: Adapter device 16: File exchange device 20: Network 22, 46, 60, 92: Arithmetic units 24, 48, 62, 94: Storage units 26, 50: Operation units 28, 52: Display unit 30, 56, 66, 97: Control unit 32: CDX format file generation unit 34: Writing unit 36: Reading unit 38: Transmission ACK confirmation unit 40: Reception ACK generation unit 42, 58: Display control unit 44, 61, 93: Destination database 45, 63, 95: Transmission / reception history storage unit 54: Communication unit 64, 96: Communication unit 68: Transmission processing unit 70: Reception processing unit 72: CDX format file acquisition unit 74: Comment file analysis unit 76: File transmission unit 78: Transmission status acquisition unit 80: Transmission ACK generation unit 82: New arrival information acquisition unit 84: File reception unit 86: CDX format conversion unit 88: Reception ACK confirmation unit 90: Reception status update unit 98: Shared directory 100: Transmission folder 102: Transmission ACK folder 104: Reception folder 106: Reception ACK folder 108: Files to be transmitted 110: Transmission comment file 112: Data files to be transmitted 113: Transmission ACK token file 114: Transmission token file 115: Transmission ACK file 116: Received files 118: Reception comment file 120: Received data files 122: Reception token file 123: Reception ACK token file 124: Reception ACK file 126: Transmission metadata file 128: Transmission data 130: Transmission configuration file 132: Reception metadata file 134: Reception data 136: Reception configuration file 1081: Transmission files 1161: Reception files

Claims

1. A first device operated by one user, a second device operated by another user, a file exchange device used for sending and receiving files between the first device and the second device, and an adapter device including a communication unit that communicates with the file exchange device based on a predetermined communication protocol. In the adapter device in the file exchange system, when a transmission target file to be transmitted is written in a shared directory that can be accessed from the first device operated by the one user but cannot be accessed from the second device operated by the other user, a transmission processing unit that transmits a transmission file corresponding to the transmission target file to the file exchange device via the communication unit; a reception processing unit that, when receiving a received file from the file exchange device via the communication unit, writes a received file corresponding to the received file in the shared directory; characterized by comprising; the file exchange device cannot access the shared directory; file transmission and reception between the file exchange device and the first device are performed via the shared directory and the adapter device; the transmission target file written in the shared directory includes destination information indicating the destination of the transmission file; when the transmission file is transmitted to the second device, the destination information indicating the second device, which is the destination of the transmission file, is included in the transmission target file written in the shared directory, and the destination information is extracted from the transmission target file by the adapter device for use in determining the second device. An adapter device.

2. The adapter device according to claim 1, wherein the transmission target file is written in a transmission folder provided in the shared directory. An adapter device.

3. The adapter device according to claim 1 or 2, wherein the received file is written in a reception folder provided in the shared directory. An adapter device.

4. The adapter device according to any one of claims 1 to 3, wherein the received file includes source information indicating the source of the received file. An adapter device.

5. The adapter device according to any one of claims 1 to 4, wherein The transmission target file includes a transmission target data file containing transmission target data which is data to be transmitted, a transmission comment file associated with the transmission target data file and containing comments regarding the transmission target data, and a transmission token file associated with the transmission target data file and containing tokens, and is an adapter device.

6. In the adapter device according to any one of Claims 1 to 5, The received file includes a received data file containing received data which is received data, a received comment file associated with the received data file and containing comments regarding the received data, and a received token file associated with the received data file and containing tokens, and is an adapter device.

7. A file exchange system including a first device operated by one user, a second device operated by another user, a file exchange device used for file transmission and reception between the first device and the second device, and an adapter device including a communication unit that communicates with the file exchange device based on a predetermined communication protocol, The first device includes a writing unit that writes a transmission target file, which is a file to be transmitted, to a shared directory that can be accessed from the first device operated by the one user and cannot be accessed from the second device operated by the other user, The adapter device includes a transmission processing unit that transmits a transmission file corresponding to the transmission target file to the file exchange device via the communication unit when the transmission target file is written to the shared directory, The file exchange device cannot access the shared directory, File transmission and reception between the file exchange device and the first device is performed via the shared directory and the adapter device, The transmission target file written in the shared directory includes destination information indicating the destination of the transmission file. When the transmission file is transmitted to the second device, destination information indicating the second device which is the destination of the transmission file is included in the transmission target file written in the shared directory, and the destination information is extracted from the transmission target file by the adapter device for use in determining the second device. A file exchange system.

8. In the file exchange system according to claim 7, when the adapter device receives a received file from the file exchange device via the communication unit, the adapter device further includes a reception processing unit that writes a received file corresponding to the received file in the shared directory. The first device further includes a reading unit that reads the received file written in the shared directory. A file exchange system.

9. A file exchange method in a file exchange system including a first device operated by one user, a second device operated by another user, a file exchange device used for file transmission and reception between the first device and the second device, and an adapter device including a communication unit that communicates with the file exchange device based on a predetermined communication protocol, a step of checking whether a transmission target file to be transmitted is written in a shared directory that can be accessed from the first device operated by the one user and cannot be accessed from the second device operated by the other user; when the transmission target file is written in the shared directory, a step of transmitting a transmission file corresponding to the transmission target file to the file exchange device via the communication unit based on a predetermined communication protocol; having, the file exchange device cannot access the shared directory, file transmission and reception between the file exchange device and the first device are performed via the shared directory and the adapter device, the transmission target file written in the shared directory includes destination information indicating the destination of the transmission file. When the transmission file is transmitted to the second device, destination information indicating the second device, which is the destination of the transmission file, is included in the transmission target file written in the shared directory, and the destination information is extracted from the transmission target file by the adapter device for use in determining the second device. A file exchange method.

10. In the file exchange method according to claim 9, receiving a received file from the file exchange device via the communication unit based on the communication protocol; when the received file is received from the file exchange device via the communication unit, writing a received file corresponding to the received file into the shared directory; A file exchange method further comprising:

11. A first device operated by one user, a second device operated by another user, a file exchange device used for file transmission and reception between the first device and the second device, and a communication unit for communicating with the file exchange device based on a predetermined communication protocol An adapter device, a computer provided in a file exchange system including: confirming whether a transmission target file to be transmitted has been written in a shared directory that can be accessed from the first device operated by the one user and cannot be accessed from the second device operated by the other user; when the transmission target file is written in the shared directory, transmitting a transmission file corresponding to the transmission target file to the file exchange device via the communication unit based on a predetermined communication protocol; A program for causing the computer to execute: the file exchange device cannot access the shared directory; file transmission and reception between the file exchange device and the first device are performed via the shared directory and the adapter device; the transmission target file written in the shared directory includes destination information indicating the destination of the transmission file When the transmission file is transmitted to the second device, destination information indicating the second device, which is the destination of the transmission file, is included in the transmission target file written in the shared directory, and the destination information is extracted from the transmission target file by the adapter device for use in determining the second device. A program.

12. In the program according to claim 11, Receiving a received file from the file exchange device via the communication unit based on the communication protocol; When the received file is received from the file exchange device via the communication unit, writing a received file corresponding to the received file into the shared directory; A program for further causing the computer to execute.

Images