JP3913750B2 - Data transmission / reception system - Google Patents

Description

  The present invention relates to a data transmission / reception system, and more particularly to a data transmission / reception system capable of performing data transmission / reception control by a simple and high-speed method.

In a conventional data transmission / reception system, data transmission or reception is controlled with reference to the contents of a file in which information related to data transmission / reception is stored when data is transmitted / received (see, for example, Patent Document 1).
Japanese Patent Laid-Open No. 7-146851

  However, the file reference method differs depending on the file type, OS (Operating System) type, and the like. For this reason, in the method of performing transmission / reception control while referring to the contents of the file, it is necessary to construct a system depending on the model, and in an environment where different models are mixed, it takes time to construct a data transmission / reception system. There is a problem that it takes.

  Therefore, the present invention has been made to solve the above-described problems, and an object of the present invention is to provide a data transmission / reception system that can be easily constructed even in an environment in which different models are mixed.

  It is another object of the present invention to provide a data transmission / reception system capable of performing data transmission / reception control at high speed.

  A data transmission / reception system according to an aspect of the present invention is a data transmission / reception system that transmits / receives data, and includes a data transmission device that transmits the data, and a data reception device that receives the data. The data receiving apparatus controls transmission or reception of the data depending on the presence / absence of a predetermined control file.

  According to this configuration, since the OS file system can be used, the functions provided in the OS such as a UNIX (registered trademark) shell script are used without using a special computer language. Thus, it is possible to construct a data transmission / reception system. Therefore, it is easy to construct a data transmission / reception system even in an environment where different models are mixed.

  Data transmission / reception is controlled only by the presence / absence of a control file. Therefore, it is not necessary to open a control file every time data is transmitted / received, and data transmission / reception control can be performed at high speed. Further, it is possible to grasp an operation state in data transmission / reception based on the presence / absence of a control file.

  Preferably, the data transmission device transmits the data as a data file, and the data reception device changes a file name of the data file received from the data transmission device.

  According to this configuration, the data file transmitted from the data transmission device is stored with a different name in the data reception device. For this reason, the data transmission processing by the data transmission device and the data reception processing by the data reception device do not interfere with each other. This configuration is realized by the first embodiment.

  More preferably, the data reception device performs reception control of the data file based on the presence of the control file and the storage unit that stores the control file and the data file received from the data transmission device. A data reception management unit, and the control file includes a transmission permission / inhibition file indicating whether or not the data file can be transmitted from the data transmission device to the data reception device, and the data transmission device When the transmission availability file exists, the transmission availability file is deleted, and then the data file is transmitted to the data reception device. The data reception management unit receives the data file from the data transmission device. After the file name is changed, the transmission permission / inhibition file is generated.

  According to this configuration, only the data transmission device that has deleted the transmission permission / inhibition file can transmit the data file to the data reception device. For this reason, a plurality of data transmission devices do not simultaneously transmit data files to the data reception device. In the first embodiment, the storage unit corresponds to a working area, and the data reception management unit corresponds to a management module.

  The data transmission device includes a storage unit that stores the control file and a data file that stores the data, and a data transmission management unit that performs transmission control of the data file based on whether or not the control file exists. The control file includes a reception availability file indicating whether or not the data reception device can receive the data file depending on whether or not the data file can be received, and the data transmission management unit stores the data file to be transmitted. The reception availability file is created at the time of generation, and when the reception availability file exists, the data reception device receives the data file from the data transmission device after deleting the reception availability file. It may be a feature.

  According to this configuration, only the data reception device from which the reception availability file has been deleted can receive the data file from the data transmission device. For this reason, a plurality of data receiving apparatuses do not receive data files from the data transmitting apparatus at the same time. This configuration is realized by the second embodiment. The storage unit corresponds to a working area, and the data transmission management unit corresponds to a management module.

  The data transmission / reception system according to the present invention enables high-speed data transmission / reception control. In particular, the practical value of the data transmission / reception system for transmitting / receiving large amounts of data is extremely high.

Hereinafter, a data transmission / reception system according to an embodiment of the present invention will be described with reference to the drawings.
[Embodiment 1]
FIG. 1 is a diagram showing a configuration of a data transmission / reception system according to Embodiment 1 of the present invention. The data transmission / reception system 20 is a system for transmitting data from one device to the other device, and is a data transmission device 22 and a data reception device 24 interconnected with the data transmission device 22 via a computer network 26. Including. The computer network 26 is connected to a number of other data transmission devices that transmit data to the data reception device 24.

  In the present embodiment, a method will be described in which the data transmission device 22 sequentially transmits data used in the data reception device 24 to the data reception device 24.

  FIG. 2 is an external view of the data transmission device 22. The data transmission device 22 is a device for transmitting data to the data reception device 24, and presents information such as a computer 34, a keyboard 36 and a mouse 38 for giving instructions to the computer 34, and calculation results of the computer 34. A display 32, a CD-ROM (Compact Disc-Read Only Memory) device 40 for reading a program executed by the computer 34, and a communication modem (not shown).

  A program for transmitting data is stored in a CD-ROM 42 which is a computer-readable medium and is read by the CD-ROM device 40. Alternatively, it is read by a communication modem through the computer network 26.

  FIG. 3 is a block diagram illustrating a hardware configuration of the data transmission device 22. The computer 34 includes a CPU (Central Processing Unit) 44, a ROM (Read Only Memory) 46, a RAM (Random Access Memory) 48, a hard disk 50, a communication modem 52, and a bus 54.

  The CPU 44 executes a program read via the CD-ROM device 40 or the communication modem 52. The ROM 46 stores programs and data necessary for the operation of the computer 34. The RAM 48 stores data such as parameters at the time of program execution. The hard disk 50 stores programs and data. The communication modem 52 communicates with other computers via the computer network 26. The bus 54 connects the CPU 44, the ROM 46, the RAM 48, the hard disk 50, the communication modem 52, the display 32, the keyboard 36, the mouse 38, and the CD-ROM device 40 to each other.

  The data receiving device 24 shown in FIG. 1 is a device for receiving data transmitted from the data transmitting device 22, and has the hardware configuration shown in FIGS. Have. Therefore, detailed description thereof will not be repeated here.

  FIG. 4A is a functional block diagram showing the configuration of the data transmission / reception system 20.

  The CPU 44 of the data transmission device 22 executes a data transmission module 62 that is a program for performing control related to data transmission. The CPU 44 of the data receiving device 24 includes a management module 64 that is a program for performing control related to data reception, and a plurality of application modules 66a and 66b that are programs for executing predetermined processing using the data. An application module group 66 including 66c and the like is executed. Hereinafter, the application module 66a in the application module group 66 will be described as a representative example. Other application modules perform the same operation.

  The hard disk 50 of the data receiving device 24 is provided with a working area 68 for storing a file including data transmitted / received between the data transmitting device 22 and the data receiving device 24 and a file indicating a transmission / reception state. In addition, the hard disk 50 is provided with a definition file 70 in which a name part of a file name of a file transmitted / received between the data transmitting device 22 and the data receiving device 24 is defined. Here, when the file name is “xxx.yyy”, the part “xxx” in the first half of the period is called “name part” and the part “yyy” in the latter half is called “extension”.

  The management module 64 and the application module 66 a can know what the name portions of various files stored in the working area 68 are by referring to the definition file 70 stored in the hard disk 50.

  FIG. 4B is a functional block diagram showing a detailed configuration of the data transmission module 62.

  More specifically, the data transmission module 62 includes a data transmission availability determination unit 62a, a control file management unit 62b, and a data transmission unit 62c. The data transmission availability determination unit 62a is a processing unit that determines whether data transmission is possible based on the presence / absence of various files stored in the working area 68.

  The control file management unit 62b is a processing unit that generates and deletes various files in the working area 68 based on the data transmission state, and includes an access exclusion unit 63a and a write end declaration unit 63b. The access exclusion unit 63a eliminates an access to the working area 68 by a data transmission module of another data transmission device by deleting an OK file described later. The writing end declaration unit 63b declares that writing of data (an FTP file described later) by the data transmission module 62 is completed by creating an END file described later in the working area 68.

  The data transmission unit 62c is a processing unit that transmits data according to the determination result of the data transmission availability determination unit 62a.

  FIG. 4C is a functional block diagram showing a detailed configuration of the management module 64.

  The management module 64 includes a data writability determination unit 64a, a control file management unit 64b, and a data writing unit 64c. The data writability determination unit 64 a is a processing unit that determines whether data can be written between files stored in the working area 68 based on the presence or absence of various files stored in the working area 68.

  The control file management unit 64b is a processing unit that generates and disappears various files in the working area 68 based on the data writing state. The control file management unit 64b includes a write declaration unit 65a, a data transmission module exclusive control release unit 65b, An application module exclusive control release unit 65c. The write declaration unit 65a creates a wlock file, which will be described later, thereby declaring that the data writing unit 64c writes data to the working area 68 and excludes the application module 66a from reading data from the working area 68. The data transmission module exclusive control release unit 65b is a processing unit that releases exclusive control for the data transmission module 62 by creating an OK file to be described later. In addition, the data transmission module exclusive control release unit 65b notifies the application module 66a that there is a usable data file (a dat file described later) by creating an event file described later. The application module exclusive control release unit 65c releases exclusive control of the application module 66a by deleting a wlock file described later.

  The data writing unit 64c is a processing unit that writes data between files stored in the working area 68 according to the determination result of the data writing permission / inhibition determining unit 64a, and includes an application module usage data creating unit 65d, a backup file And a creation unit 65e. The application module usage data creation unit 65d creates the data used by the application module by adding the contents of the FTP file described later to the end of the dat file described later. The backup file creation unit 65e creates a backup file (bakup file to be described later) of the FTP file.

  FIG. 4D is a functional block diagram illustrating a detailed configuration of the application module 66a as a representative example.

  The application module 66a includes a data read availability determination unit 67a, a control file management unit 67b, a data read unit 67c, and an application unit 67d. The data reading availability determination unit 67a is a processing unit that determines whether data stored in the working area 68 can be read based on the presence / absence of various files stored in the working area 68.

  The control file management unit 67b is a processing unit for generating and erasing various files in the working area 68 based on the data read state. The data file exclusion unit 69a, the data write permission unit 69b, And a backup file 0 clear unit 69c. The data write exclusion unit 69 a excludes the management module 64 from writing data to the working area 68 by creating an rlock file to be described later in the working area 68. The data write permission unit 69b permits the management module 64 to write data by deleting the rlock file. The backup file 0 clear unit 69c sets the file size of the backup file (bakup file) of the FTP file to 0 bytes.

  The data reading unit 67c is a processing unit that reads the data stored in the working area 68 in accordance with the determination result of the data reading possibility determination unit 67a. The application unit 67d is a processing unit that executes a predetermined process using the data read by the data reading unit 67c.

  FIG. 5 is a table in which the meanings of various files stored in the working area 68 are organized by extension.

  A file whose extension is “OK” (hereinafter referred to as “OK file”) is a file that exists when data can be transmitted from the data transmission device 22 to the data reception device 24. The file size of the OK file is 0 bytes.

  A file whose extension is “FTP” (hereinafter referred to as “FTP file”) is a file including the substance of data transmitted from the data transmission device 22 to the data reception device 24.

  A file with an extension “END” (hereinafter referred to as “END file”) is a file that is generated when transmission of the FTP file from the data transmission device 22 to the data reception device 24 is completed. The file size of the END file is 0 bytes.

  A file having an extension “rlock” (hereinafter referred to as “rlock file”) is a file created when the application module 66 a reads data from the working area 68. While the rlock file exists, the management module 64 cannot write data to the working area 68. The file size of the rlock file is 0 bytes.

  A file having an extension “wlock” (hereinafter referred to as “wlock file”) is a file created when the management module 64 writes data in the working area 68. While the wlock file exists, the application module 66a cannot read data from the working area 68.

  A file having an extension “dat” (hereinafter referred to as “dat file”) is a file created by the management module 64 sequentially storing FTP files received from the data transmission device 22, and is an application module 66a. Is a file used by

  A file having an extension “bakup” (hereinafter referred to as “bakup file”) is a backup file of an FTP file created by the management module 64.

  A file whose extension is “event” (hereinafter referred to as “event file”) is a file for informing the application module 66a that a dat file has been newly generated by the management module 64. The file size of the event file is 0 bytes.

  Next, operations performed by the data transmission module 62, the management module 64, and the application module 66a will be described with reference to flowcharts. Here, it is assumed that the file name names of the files generated and deleted by the three modules are the same.

  FIG. 6 is a flowchart of processing executed by the data transmission module 62. FIG. 7 is a diagram showing an example of a file stored in the working area 68 when the data transmission module 62 is executed. Hereinafter, processing executed by the data transmission module 62 will be described with reference to FIGS. 6 and 7 as appropriate.

  The data transmission module 62 checks whether or not an OK file exists in the working area 68 (S2), and if the OK file does not exist (NO in S2), the process ends. If the OK file exists (YES in S2), the data transmission module 62 deletes the OK file (S4). The presence of the OK file indicates that the data transmission module is in a state where it can transmit the FTP file. Further, by deleting the OK file, the data transmission module of another data transmission apparatus is prevented from accessing the working area 68. The application module 66a is also excluded from accessing the working area 68.

  Next, the data transmission module 62 writes the FTP file in the working area 68 (S6). When writing of the FTP file is completed, the data transmission module 62 creates an END file in the working area 68 (S8), and declares that writing of the FTP file by the data transmission module 62 is completed.

  Since the data transmission module 62 cannot directly refer to the working area 68, the above processing is performed via the management module 64 of the data receiving device 24.

  FIG. 8 is a flowchart of processing executed by the management module 64. FIG. 9 is a diagram showing an example of a file stored in the working area 68 when the management module 64 is executed. Hereinafter, processing executed by the management module 64 will be described with reference to FIGS. 8 and 9 as appropriate.

  The management module 64 checks whether an FTP file and an END file exist in the working area 68 and no rlock file exists (S12). The existence of the FTP file and the END file indicates that the FTP file has been written in the working area 68 by the data transmission module 62. The absence of the rlock file indicates that the working area 68 is not accessed by the application module 66a.

  If even one of the above three conditions is not satisfied (NO in S12), the process is terminated. If all three conditions are satisfied (YES in S12), the management module 64 creates a wlock file (S14). By creating a wlock file, the data writing unit 64 c declares that data is written to the working area 68, and the application module 66 a is excluded from reading data from the working area 68.

  After creating the wlock file, the management module 64 adds the contents of the FTP file to the end of the dat file (S16). If the dat file has already been used by the application module 66a, the dat file is deleted. In this case, the FTP file is copied to the dat file. However, when the dat file is not used by the application module 66a, the file size of the dat file increases by the file size of the FTP file.

  The management module 64 copies the FTP file to the bakuup file and creates a backup (S18).

  After the FTP file copy process (S16 and S18) is completed, the management module 64 deletes the FTP file and the END file (S20). Also, the wlock file is deleted (S22). Thereby, the exclusive control of the application module 66a is released.

  Finally, the management module 64 creates an OK file and an event file (S24). By creating the OK file, the exclusive control for the data transmission module 62 is released. Also, by creating an event file, the application module 66a is notified that there is a usable dat file.

  FIG. 10 is a flowchart of processing executed by the application module 66a. FIG. 11 is a diagram showing an example of a file stored in the working area 68 when the application module 66a is executed. Hereinafter, processing executed by the application module 66a will be described with reference to FIGS. 10 and 11 as appropriate.

  The application module 66a checks whether an event file exists in the working area 68, a wlock file does not exist, and an OK file exists (S32). The presence of the event file means that a dat file that can be used by the application module 66a has already been generated. The absence of the wlock file means that the management module 64 has not written data in the working area 68. The presence of the OK file indicates that the FTP module addition processing to the dat file by the management module 64 has been completed.

  If even one of the above three conditions is not satisfied (NO in S32), the process is terminated. If all three conditions are satisfied (YES in S32), the application module 66a creates an rlock file in the working area 68 (S34). By creating the rlock file, the management module 64 is excluded from writing data in the working area 68 and is now declared to use the dat file.

  The application module 66a reads and uses the dat file at the time of execution (S36). After using the dat file, the application module 66a deletes the dat file (S38). Further, the rlock file and the event file are deleted (S40). By deleting the rlock file, the management module 64 can write data.

  Finally, the contents of the bakuup file are deleted, and the file size of the bakuup file is set to 0 bytes (S42).

  Note that the management module 64 outputs a log file (not shown) indicating the state of operation as needed when a file stored in the working area 68 is changed.

  FIG. 12 is a diagram illustrating an operation subject, an operation state, and existence of various files in the file transmission / reception process.

  As shown in FIG. 12, in a typical file transmission / reception process, the data transmission module 62 transmits an FTP file, the management module stores it in a dat file, and finally the application module 66a uses the dat file. However, since the data transmission module 62, the management module 64, and the application module 66a operate as independent processes, the processing is not necessarily performed in this order.

  As shown in FIG. 12, for example, when the file transmission process by the data transmission module 62 is completed (S8), the FTP file and the END file exist, but the OK file, the rlock file, and the wlock file do not exist. Show.

  FIG. 13 is a diagram showing an example of a list of files stored in the working area 68 in each operation state. The list shown in FIG. 13 is generated by executing the “ls command” in UNIX (registered trademark). FIGS. 13A to 13F sequentially show transitions of files created in accordance with the above-described typical file transmission / reception process and stored in the working area 68. FIG.

  As shown in FIG. 13A, immediately after the FTP file writing process (S6) by the data transmission module 62 shown in FIG. 6 is completed, the OK file is deleted and the FTP file is generated. .

  As shown in FIG. 13B, an END file is newly generated immediately after the END file creation process (S8) is completed.

  As shown in FIG. 13C, immediately after the dat file creation process (S16) by the management module 64 shown in FIG. 8 is completed, the wlock file is created and the FTP file is added to the dat file. Has been. Note that the name part of the file name of the dat file is obtained by changing the upper case of the name part of the file name of the FTP file to lower case.

  As shown in FIG. 13D, immediately after the OK file and event file creation process (S24) is finished, the FTP file, the END file, and the wlock file are deleted, and the OK file and the event file are deleted. Has been created.

  As shown in FIG. 13E, an rlock file is created immediately after the dat file use process (S36) by the application module 66a shown in FIG.

  As shown in FIG. 13 (f), immediately after the bakup file zero clear process (S42) is completed, the dat file, rlock file, and event file are deleted, and the file size of the bakuup file is reduced to 0 byte. It has become.

  Next, focusing on each of the representative OK file, wlock file, and rlock file among the files used for exclusive control of each module, the process from the generation to the disappearance will be described.

  FIG. 14 is a diagram illustrating a transition from the generation to the disappearance of an OK file. The OK file is created after the management module 64 updates the dat file (S16) and creates a bakeup file (S18) as shown in FIGS. 8 and 9 (S24). Further, as shown in FIGS. 6 and 7, the OK file is deleted when the OK file exists in the working area 68 (YES in S2) (S4). The FTP file can be transmitted by the data transmission module 62 during the period when the OK file exists, and the FTP file cannot be transmitted by the data transmission module 62 during the period when the OK file does not exist. As described above, the exclusive control of the access to the working area 68 by the data transmission module 62 is performed according to the presence or absence of the OK file.

  FIG. 15 is a diagram illustrating a transition from the generation to the disappearance of a wlock file. 8 and 9, the wlock file is created by the management module 64 when the FTP file and the END file exist in the working area 68 and the rlock file does not exist (YES in S12). (S14). 8 and 9, the wlock file is deleted by the management module 64 (S22) after the dat file is updated (S16) and the bakeup file is generated (S18). Data cannot be read by the application module 66a during a period when the wlock file exists, and data can be read by the application module 66a during a period when the wlock file does not exist. In this way, exclusive control of access to the working area 68 by the application module 66a is performed depending on the presence or absence of the wlock file.

  FIG. 16 is a diagram illustrating a transition from the generation to the disappearance of the rlock file. As shown in FIG. 10 and FIG. 11, the rlock file is created by the application module 66a when there is an event file in the working area 68, no wlock file and OK file (YES in S32) ( S34). The rlock file is deleted by the application module 66a (S40) after the dat file is used by the application module 66a (S36). Data cannot be written by the management module 64 during the period when the rlock file exists, and data can be written by the management module 64 during a period when the rlock file does not exist. As described above, exclusive control of access to the working area 68 is performed by the management module 64 depending on whether or not the rlock file exists.

  As described above, according to the present embodiment, various states are indicated by whether or not an OK file, an END file, an rlock file, a wlock file, and an event file exist, and accordingly, the data transmission module 62 and the management module 64 are displayed. The operation of the application module 66a is controlled.

  As described above, various modules are controlled only by the existence of the file. Therefore, it is not necessary to open a file every time data is transmitted / received, and data transmission / reception control can be performed at high speed.

  The FTP file written in the working area 68 by the data transmission module 62 is added to the dat file by the management module 64, and is deleted after the addition. For this reason, the data transmission module 62 can sequentially write the FTP file into the working area 68 when it becomes writable. In addition, the extension of the file to which the data transmission module 62 writes data is different from the extension of the file to which the management module 64 writes data. For this reason, the data writing process by the data transmission module 62 and the data writing process by the management module 64 do not interfere with each other.

  Further, the management module 64 outputs log files as needed. Therefore, the system administrator can manage whether or not the data transmission / reception processing is correctly performed.

  Furthermore, the management module 64 creates a bakuup file that is a copy of the FTP file. For this reason, even if the system does not operate properly halfway, important data is not lost.

[Embodiment 2]
FIG. 17 is a diagram showing a configuration of a data transmission / reception system according to Embodiment 2 of the present invention. The data transmission / reception system 80 is a system for transmitting data from one device to the other device, and is a data transmission device 82 and a data reception device 84 interconnected with the data transmission device 82 via the computer network 26. Including. The computer network 26 is also connected with many other data receiving devices that receive data transmitted from the data transmitting device 82.

  In the present embodiment, unlike the first embodiment, a method in which the data reception device 84 sequentially receives data created in the data transmission device 82 will be described.

  The hardware configuration of each of the data transmission device 82 and the data reception device 84 is the same as the hardware configuration of the data transmission device 22 (data reception device 24) shown in FIGS. Therefore, detailed description thereof will not be repeated here.

  FIG. 18A is a functional block diagram showing the configuration of the data transmission / reception system 80.

  The CPU 44 of the data transmission device 82 includes a management module 88 that is a program for performing control related to data transmission and an application module group 86 that includes a plurality of application modules 86a, 86b, and 86c, each of which is a program for creating transmission data. Execute. Hereinafter, the application module 86a in the application module group 86 will be described as a representative example. Other application modules perform the same operation. The CPU 44 of the data receiving device 84 executes a data receiving module 90 that is a program for performing control related to data reception.

  The hard disk 50 of the data transmission device 82 is provided with a working area 68 for storing a file including data transmitted and received between the data transmission device 82 and the data reception device 84 and a file indicating a transmission / reception state. In addition, the hard disk 50 is provided with a definition file 70 in which a name portion is defined among file names of files transmitted and received between the data transmission device 82 and the data reception device 84.

  FIG. 18B is a functional block diagram showing a detailed configuration of the data receiving module 90.

  More specifically, the data reception module 90 includes a data reception availability determination unit 90a, a control file management unit 90b, and a data reception unit 90c. The data reception availability determination unit 90 a is a processing unit that determines whether data reception is possible based on the presence or absence of various files stored in the working area 68.

  The control file management unit 90b is a processing unit that generates and disappears various files in the working area 68 based on the data reception state. The other data reception module exclusion unit 91a, the data write exclusion unit 91b, A reception end declaration unit 91c. The other data receiving module exclusion unit 91a eliminates an access to the working area 68 by a data receiving module of another data receiving apparatus by deleting an OK file described later. The data write exclusion unit 91b eliminates the management module 88 from writing data into the working area 68 by creating a START file to be described later. The data reception end declaration unit 91c declares that reception of data (an FTP file described later) by the data receiving unit 90c is completed by creating an END file described later.

  The data reception unit 90c is a processing unit that receives data according to the determination result of the data reception availability determination unit 90a.

FIG. 18C is a functional block diagram showing a detailed configuration of the management module 88.
The management module 88 includes a data writability determination unit 88a, a control file management unit 88b, and a data writing unit 88c. The data writability determination unit 88 a is a processing unit that determines whether data can be written between files stored in the working area 68 based on the presence or absence of various files stored in the working area 68.

  The control file management unit 88b is a processing unit for generating and erasing various files in the working area 68 based on the data write state. The data file declaration unit 89a, the data write permission unit 89b, and the transmission data And an existence declaration unit 89c. The data write declaration unit 89a creates a wlock file, which will be described later, thereby declaring that the data write unit 88c writes data to the working area 68 and excludes the application module 86a from writing data to the working area 68. The data write permission unit 89b allows the application module 86a to write the dat file in the working area 68 by deleting the wlock file and a dat file (data entity) described later. The transmission data existence declaration unit 89c declares that there is data to be transmitted to the data reception module 90 (an FTP file described later) by creating an OK file described later.

  The data writing unit 88c is a processing unit that writes data between files stored in the working area 68 in accordance with the determination result of the data writing permission / inhibition determining unit 88a, and includes a transmission data generation unit 89d, a backup file generation unit 89e. The transmission data creation unit 89d creates data to be transmitted by adding a dat file (described later) to an FTP file (described later). The backup file creation unit 89e creates a backup file (a BAK file described later) of the dat file.

  FIG. 18D is a functional block diagram illustrating a detailed configuration of the application module 86a as a representative example.

  The application module 86a includes a data write availability determination unit 87a, a data write unit 87c, and an application unit 87d. The data writability determination unit 87 a is a processing unit that determines whether data can be written to the working area 68 based on the presence / absence of various files stored in the working area 68. The data writing unit 87c is a processing unit that writes data to the working area 68 in accordance with the determination result of the data writing possibility determination unit 87a. The application unit 87d is a processing unit that generates data to be written by the data writing unit 87c by executing predetermined processing.

  FIG. 19 is a table in which the meanings of various files stored in the working area 68 are organized by extension.

  A file whose extension is “OK” (hereinafter referred to as “OK file”) is a file that exists when the data receiving device 84 can receive a file from the data transmitting device 82. The file size of the OK file is 0 bytes.

  A file whose extension is “START” (hereinafter referred to as “START file”) indicates that the data receiving device 84 has started receiving data from the data transmitting device 82. The file size of the START file is 0 bytes.

  A file having an extension of “FTP” (hereinafter referred to as “FTP file”) is a file including the substance of data transmitted from the data transmission device 82 to the data reception device 84.

  A file having an extension “END” (hereinafter referred to as “END file”) is a file that is generated when the data receiving device 84 completes reception of data from the data transmitting device 82. The file size of the END file is 0 bytes.

  A file having an extension “BAK” (hereinafter referred to as “BAK file”) is a backup file of a dat file, which will be described later, created by the application module 86a.

  A file having an extension “wlock” (hereinafter referred to as “wlock file”) is a file generated when the management module 88 writes data in the working area 68. While the wlock file exists, the application module 86a cannot write data to the working area 68.

  A file having an extension “dat” (hereinafter referred to as “dat file”) is a file created by the application module 86a, and stores data transmitted from the data transmission device 82 to the data reception device 84. Is a file.

  Next, operations performed by the data reception module 90, the management module 88, and the application module 86a will be described with reference to flowcharts. Here, the files generated and deleted by the three modules have the same name part.

  FIG. 20 is a flowchart of processing executed by the data receiving module 90. FIG. 21 is a diagram showing an example of a file stored in the working area 68 when the data receiving module 90 is executed. Hereinafter, processing executed by the data receiving module 90 will be described with reference to FIGS. 20 and 21 as appropriate.

  The data receiving module 90 checks whether or not an OK file exists in the working area 68 (S52). The state where the OK file exists indicates that there is a file that the data transmitting apparatus 82 should receive from the data receiving apparatus 84.

  If the OK file does not exist (NO in S52), the data receiving module 90 ends the process. If the OK file exists (YES in S52), the data reception module 90 deletes the OK file (S54). By deleting the OK file, the data receiving module of another data receiving apparatus is prevented from accessing the working area 68.

  The data receiving module 90 creates a START file (S56). By creating the START file, the management module 88 is prevented from writing data to the working area 68.

  The data receiving module 90 receives the FTP file stored in the working area 68 (S58). When the reception is completed, the data reception module 90 creates an END file in the working area 68 (S60), and declares that reception of the FTP file from the working area 68 is completed.

  Since the data reception module 90 cannot directly refer to the working area 68, the above-described processing is performed via the management module 88 of the data transmission device 82.

  FIG. 22 is a flowchart of processing executed by the management module 88. FIG. 23 is a diagram showing an example of a file stored in the working area 68 when the management module 88 is executed. Hereinafter, processing executed by the management module 88 will be described with reference to FIGS. 22 and 23 as appropriate.

  The management module 88 checks whether a START file exists in the working area 68 (S62). If the START file exists, there is a possibility that the data receiving module 90 is receiving the FTP file. For this reason, if the START file exists (NO in S62), the management module 88 ends the process. If the START file does not exist (YES in S62), the management module 88 creates a wlock file in the working area 68 (S64). By creating a wlock file, it is declared that data is to be written to the working area 68, and the application module 86a is excluded from writing data to the working area 68.

  After creating the wlock file, the management module 88 adds the dat file to the FTP file (S66), and copies the dat file to the BAK file (S68).

  Thereafter, the management module 88 deletes the START file and the END file (S70), and deletes the wlock file and the dat file (S72). By deleting the wlock file and the dat file, the application module 86 a is allowed to write the dat file in the working area 68.

  Finally, the management module 88 creates an OK file (S74). By creating the OK file, it is declared that there is an FTP file to be transmitted to the data receiving module 90, and the data receiving module 90 can receive the FTP file from the working area 68.

  FIG. 24 is a flowchart of processing executed by the application module 86a. FIG. 25 is a diagram showing an example of a file stored in the working area 68 when the application module 86a is executed. Hereinafter, processing executed by the application module 66a will be described with reference to FIGS. 24 and 25 as appropriate.

  The application module 86a refers to the working area 68 and checks whether both the wlock file and the dat file exist (S82). When the wlock file exists, the application module 86a cannot write data because the management module 88 has written data. If the application module 86a further creates a dat file when a dat file already exists, the dat file originally stored in the working area 68 is overwritten.

  Therefore, when either the wlock file or the dat file exists in the working area 68 (NO in S82), the application module 86a ends the process.

  If neither the wlock file nor the dat file exists (YES in S82), the application module 86a uses the data created as a result of the execution of the application module 86a in the working area 68 as a dat file. (S84).

  As in the first embodiment, the management module 88 outputs a log file (not shown) indicating the operation status as needed when a file stored in the working area 68 is changed.

  FIG. 26 is a diagram illustrating the operation subject, the operation state, and the presence / absence of various files in the file transmission / reception apparatus.

  As shown in FIG. 26, in a typical file transmission / reception process, the application module 86a transmits a dat file, the management module 88 accumulates it in the FTP file, and the data reception module 90 receives the FTP file. However, since the application module 86a, the management module 88, and the data receiving module 90 operate as independent processes, the processes are not necessarily performed in this order.

  As shown in FIG. 26, for example, when the transmission file creation process (S84) by the application module 86a is completed, the dat file exists, but no other files exist.

  FIG. 27 is a diagram showing an example of a list of files stored in the working area 68 in each operation state. The list shown in FIG. 27 is generated by executing the “ls command” in UNIX (registered trademark). FIG. 27A to FIG. 27E sequentially show transitions of files created in accordance with the above-described typical file transmission / reception process and stored in the working area 68. FIG.

  As shown in FIG. 27A, a dat file is generated immediately after the dat file creation process (S84) by the application module 86a shown in FIG.

  As shown in FIG. 27B, a wlock file and an FTP file are newly generated immediately after the FTP file creation process (S66) by the management module 88 shown in FIG. The name part of the file name of the FTP file is obtained by changing the lower case of the name part of the file name of the dat file to upper case.

  As shown in FIG. 27C, immediately after the OK file creation process (S74) is completed, the wlock file and the dat file are deleted, and the OK file is created.

  As shown in FIG. 27 (d), immediately after the START file creation process (S56) by the data reception module 90 shown in FIG. 20 is completed, the OK file is deleted, and the START file is created. .

  As shown in FIG. 27E, an END file is created immediately after the END file creation process (S60) is completed.

  Next, focusing on each of the representative OK file, wlock file, and START file among the files used for exclusive control of each module, the process from the generation to the disappearance will be described.

  FIG. 28 is a diagram illustrating a transition from the generation to the disappearance of an OK file. As shown in FIGS. 22 and 23, the OK file is created after the management module 88 updates the FTP file (S66) (S74). Further, as shown in FIGS. 20 and 21, the OK file is deleted by the data receiving module 90 when the OK file exists in the working area 68 (YES in S52) (S54). During the period in which the OK file exists, the data receiving module 90 can receive the FTP file, and during the period in which the OK file does not exist, the data receiving module 90 cannot receive data. In this way, exclusive control of access to the working area 68 by the data receiving module 90 is performed depending on whether or not the OK file exists.

  FIG. 29 is a diagram illustrating a transition from the generation to the disappearance of a wlock file. As shown in FIGS. 22 and 23, the wlock file is created by the management module 88 when there is no START file in the working area 68 (YES in S62) (S64). The wlock file is deleted by the management module 88 (S72) after the FTP file is updated by the management module 88 (S66). Data cannot be written by the application module 86a during the period when the wlock file exists, and data can be written by the application module 86a during a period when the wlock file does not exist. In this way, exclusive control of access to the working area 68 by the application module 86a is performed based on the presence or absence of the wlock file.

  FIG. 30 is a diagram showing a transition from the generation to the disappearance of the START file. As shown in FIG. 20 and FIG. 21, the START file is created by the data receiving module 90 when an OK file exists in the working area (YES in S52) (S56). The START file is deleted by the management module 88 (S70) after the FTP file is updated by the management module 88 (S66). Data cannot be written by the management module 88 during the period in which the START file exists, and data can be written by the management module 88 during the period in which the START file exists. In this way, exclusive control of access to the working area 68 by the management module 88 is performed depending on the presence or absence of the START file.

  As described above, according to the present embodiment, various states are indicated by whether or not an OK file, a START file, an END file, a wlock file, and a dat file exist, and accordingly, the data receiving module 90 and the management module 88 are displayed. The operation of the application module 86a is controlled.

  As described above, various modules are controlled only by the existence of the file. For this reason, a data transmission / reception system can be easily constructed even in an environment in which different models are mixed.

  Further, it is not necessary to open a file every time data is transmitted / received, and data transmission / reception control can be performed at high speed.

  Further, the dat file written in the working area 68 by the application module 86a is added to the FTP file by the management module 88, and is deleted after the addition. For this reason, the application module 86a can sequentially write the dat file to the working area 68 when it becomes writable. Also, the extension of the file to which the application module 86a writes data differs from the extension of the file to which the management module 88 writes data. For this reason, the data writing process by the application module 86a and the data writing process by the management module 88 do not interfere with each other.

  Furthermore, the management module 88 outputs log files as needed. Therefore, the system administrator can manage whether or not data transmission / reception is performed correctly.

  Furthermore, the management module 88 creates a BAK file that is a copy of the dat file. For this reason, even if the system does not operate properly halfway, important data is not lost.

  According to the present invention, it is possible to easily construct a data transmission / reception system even in an environment where different models are mixed.

In addition, data transmission / reception control can be performed at high speed.
Further, it is possible to grasp the operation state in data transmission / reception.

Furthermore, the data transmission process and the data reception process do not interfere.
Furthermore, a plurality of data transmission devices do not simultaneously transmit data files to the data reception device.

In addition, a plurality of data receiving devices do not receive data files from the data transmitting device at the same time.
Further, the system administrator can manage whether or not the data transmission / reception processing is correctly performed.

  Furthermore, even when the system does not operate normally during the process, important data is not lost.

  In the above-described embodiment, the data receiving module 90 cannot directly access the working area 68. However, the data receiving module 90 may be directly accessible.

  Further, the configuration of the data transmission / reception apparatus is not limited to the above-described embodiment. That is, as in the data transmission / reception system 100 illustrated in FIG. 31, a plurality of data transmission apparatuses 102 may be provided, or a plurality of data reception apparatuses 104 may be provided. A data management device 106 may be provided. The data management device 106 includes a management module 64 and a hard disk 50 included in the data reception device 24. Alternatively, the data management device 106 includes a management module 88 and the hard disk 50 included in the data transmission device 82. The data transmitting apparatus 102 has the same configuration as that of the data transmitting apparatus 22 or includes an application module group 86. Further, the data receiving device 104 is configured by the application module group 66 or has the same configuration as the data receiving device 84.

  The present invention can be applied to a data transmission / reception system, and in particular, can be applied to a data transmission / reception apparatus in an environment where data transmission apparatuses and data reception apparatuses of various OSs coexist.

It is a figure which shows the structure of the data transmission / reception system which concerns on Embodiment 1 of this invention. It is an external view of a data transmitter and a data receiver. It is a block diagram which shows the hardware constitutions of a data transmitter and a data receiver. It is a functional block diagram which shows the structure of the data transmission / reception system which concerns on Embodiment 1 of this invention. It is a functional block diagram which shows the detailed structure of a data transmission module. It is a functional block diagram which shows the detailed structure of a management module. It is a functional block diagram which shows the detailed structure of the application module as a representative example. It is the table | surface which arranged the meaning of the various files memorize | stored in a working area according to the extension. It is a flowchart of the process which a data transmission module performs. It is a figure which shows an example of the file stored in the working area at the time of data transmission module execution. It is a flowchart of the process which a management module performs. It is a figure which shows an example of the file stored in the working area at the time of management module execution. It is a flowchart of the process which an application module performs. It is a figure which shows an example of the file stored in the working area at the time of application module execution. It is a figure which shows the operation main body in a file transmission / reception process, an operation state, and the presence or absence of various files. It is a figure which shows an example of the list | wrist of the file stored in the working area. It is a figure which shows the transition from generation | occurrence | production to disappearance of an OK file. It is a figure which shows the transition from generation | occurrence | production to disappearance of a wlock file. It is a figure which shows the transition from generation | occurrence | production to disappearance of an rlock file. It is a figure which shows the structure of the data transmission / reception system which concerns on Embodiment 2 of this invention. It is a functional block diagram which shows the structure of the data transmission / reception system which concerns on Embodiment 2 of this invention. It is a functional block diagram which shows the detailed structure of a data reception module. It is a functional block diagram which shows the detailed structure of a management module. It is a functional block diagram which shows the detailed structure of the application module as a representative example. It is the table | surface which arranged the meaning of the various files memorize | stored in a working area according to the extension. It is a flowchart of the process which a data reception module performs. It is a figure which shows an example of the file stored in the working area at the time of data reception module execution. It is a flowchart of the process which a management module performs. It is a figure which shows an example of the file stored in the working area at the time of management module execution. It is a flowchart of the process which an application module performs. It is a figure which shows an example of the file stored in the working area at the time of application module execution. It is a figure in a file transmission / reception apparatus which shows an operation main body, an operation state, and the presence or absence of various files. It is a figure which shows an example of the list | wrist of the file stored in the working area. It is a figure which shows the transition from generation | occurrence | production to disappearance of an OK file. It is a figure which shows the transition from generation | occurrence | production to disappearance of a wlock file. It is a figure which shows the transition from generation | occurrence | production of a START file to extinction. It is a figure which shows the other structure of a data transmission / reception system.

Explanation of symbols

20, 80 Data transmission / reception system 22, 82 Data transmission device 24, 84 Data reception device 26 Computer network 32 Display 34 Computer 36 Keyboard 38 Mouse 40 CD-ROM device 42 CD-ROM
44 CPU
46 ROM
48 RAM
50 hard disk 52 communication modem 54 bus 62 data transmission module 64, 88 management module 66, 86 application module group 66a, 66b, 66c, 86a, 86b, 86c application module 68 working area 70 definition file 90 data reception module

Claims (4)

A data transmission / reception system for transmitting / receiving data,
A data transmission device for transmitting data via a network;
A data receiving device for receiving data transmitted from the data transmitting device via the network;
The data receiving device is:
A hard disk for storing received data and a plurality of control files;
A management module that controls transmission or reception of data based on the presence or absence of the plurality of control files, and stores data received from the data transmission device in the hard disk;
An application module that executes predetermined processing using received data stored in the hard disk;
The data transmission device includes:
(I) An inquiry is made to the management module via the network as to whether an OK file, which is a control file that exists when data can be transmitted from the data transmission device to the data reception device, is stored in the hard disk, (Ii) When receiving information about the existence of the OK file from the management module, and (iii) receiving information that the OK file exists, data can be transmitted from the data transmission device to the data reception device. (Iv) a data transmission availability determination unit that determines that data cannot be transmitted from the data transmission device to the data reception device when information indicating that the OK file does not exist is received;
By transmitting a request to delete the OK file to the management module via the network when it is determined by the data transmission permission determination unit that data can be transmitted from the data transmission device to the data reception device. An access excluding unit that causes the management module to delete the OK file and excludes another data transmitting apparatus from transmitting data to the data receiving apparatus via the network;
After the OK file deletion request is transmitted by the access exclusion unit, the FTP file, which is a file including the substance of data, is transmitted to the management module via the network, so that the FTP file is stored in the hard disk in the management module. A data transmission module
After the transmission of the FTP file by the data transmission module, a request for creating an END file, which is a control file indicating that the transmission of the FTP file from the data transmission device to the data reception device is completed, is sent to the management module via the network. A write end declaration unit for declaring that data writing by the data transmission module is completed.
The management module is
The FTP file is stored in the hard disk, the END file is stored in the hard disk, and the application module is a file in which data included in the FTP file stored in the hard disk is added. Data writability to determine that data included in the FTP file can be added to the dat file by determining that the rlock file that is a control file indicating that the file is used is not stored A determination unit;
A wlock file that is a control file indicating that the management module is writing data to the hard disk when the data writability determination unit determines that the data included in the FTP file can be added to the dat file A write declaration unit that declares that the management module writes data to the hard disk, and excludes the application module from reading data from the hard disk;
A data writing unit for adding data included in the FTP file stored in the hard disk to the dat file after the write declaration unit creates the wlock file;
An application module exclusive control release unit that releases exclusive control of the application module by deleting the wlock file after the data writing unit finishes adding to the dat file;
After the exclusive control is released by the application module exclusive control release unit, a control file indicating that the dat file has been newly created by releasing the exclusive control for the other data transmission device by creating the OK file. A data transmission module exclusive control release unit that notifies the application module that the dat file can be used by creating an event file;
The management module deletes the FTP file and the END file after completion of appending to the dat file by the data writing unit,
The application module is
The application module can be used by determining that the event file is stored on the hard disk, the wlock file is not stored on the hard disk, and the OK file is stored on the hard disk. A data reading availability determination unit that determines that the latest dat file is stored in the hard disk;
When the data read availability determination unit determines that the latest dat file usable by the application module is stored in the hard disk, the management module creates the rlock file on the hard disk. A data write exclusion unit that eliminates writing data to the hard disk;
An application unit that executes a predetermined process using the dat file after the creation of the rlock file on the hard disk by the data write exclusion unit is completed;
A data write permission unit that allows the management module to write data by deleting the rlock file and the event file from the hard disk after the predetermined processing is executed by the application unit;
A data transmission / reception system characterized by the above. A data transmission / reception system for transmitting / receiving data,
A data transmission device for transmitting data via a network;
A data receiving device for receiving data transmitted from the data transmitting device via the network;
The data transmission device includes:
An application module that creates the data to send,
A hard disk for storing data to be transmitted and at least one control file indicating the state of the data;
A management module that controls transmission or reception of data based on the presence or absence of the at least one control file;
The application module is
When there is no wlock file that is a control file indicating that the management module is writing data to the hard disk, and there is no dat file that is a file containing data created by the application module. A first data writability determination unit that determines that the dat file can be written to the hard disk;
An application unit that generates a dat file by performing a predetermined process when it is determined by the first data writability determination unit that the dat file can be written;
A first data writing unit that writes the dat file to the hard disk after the dat file is generated by the application unit;
The management module is
The dat file can be added to the FTP file when a START file, which is a control file indicating that the data receiving apparatus has started receiving an FTP file containing data from the data transmitting apparatus, is not stored in the hard disk. A second data writability determination unit that determines that
Creates a wlock file that is a control file indicating that the management module is writing data to the hard disk when the second data writability determination unit determines that appending to the FTP file is possible A data write declaration unit that declares that the management module writes data to the hard disk, and excludes the application module from writing data to the hard disk;
A second data writing unit that appends the dat file to the FTP file after the wlock file is created by the writing declaration unit;
A data write permission unit that permits the application module to write the dat file to the hard disk by deleting the wlock file and the dat file after the additional writing by the second data writing unit;
After the data writing permission unit permits writing, the data receiving device creates an OK file that is a control file indicating that the FTP file can be received from the data transmitting device. A transmission data existence declaration part that declares that there is an FTP file to be transmitted to the receiving device;
The management module is an END that is a control file that is generated when the START file and the data receiving device complete reception of the FTP file from the data transmitting device after the additional writing by the second data writing unit Delete files and
The data receiving device is:
(I) Inquires of the management module via the network whether or not the OK file is stored in the hard disk, (ii) receives information about the existence of the OK file from the management module, and (iii) When the information that the OK file exists is received, it is determined that the FTP file transmitted from the data transmission apparatus can be received. (Iv) When the information that the OK file does not exist is received A data reception availability determination unit that determines that reception of the FTP file transmitted from the data transmission device is impossible;
When the data reception availability determination unit determines that the FTP file transmitted from the data transmission device can be received, the OK file deletion request is transmitted to the management module via the network. The other data receiving module excluding unit that causes the management module to delete the OK file and excludes other data receiving devices from accessing the hard disk via the management module;
After exclusion by the other data module exclusion unit, the management module creates the START file by sending a request to create the START file to the management module via the network, and the management module creates the data on the hard disk. A data write exclusion unit that eliminates writing; and
A data receiving unit that receives an FTP file from the data transmission device via the network after being excluded by the data writing exclusion unit;
After receiving the FTP file by the data receiving unit, the management module sends the END file creation request to the management module via the network, and causes the management module to create the END file. It has a data reception end declaration part that declares that reception has ended
A data transmission / reception system characterized by the above. A data transmission / reception method by a data transmission / reception system for transmitting / receiving data,
The data transmission / reception system includes:
A data transmission device for transmitting data via a network;
A data receiving device for receiving data transmitted from the data transmitting device via the network;
The data receiving device is:
A hard disk for storing received data and a plurality of control files;
A management module that controls transmission or reception of data based on the presence or absence of the plurality of control files, and stores data received from the data transmission device in the hard disk;
An application module that executes predetermined processing using received data stored in the hard disk;
Via the network, the data transmission device determines whether (i) an OK file, which is a control file existing when data can be transmitted from the data transmission device to the data reception device, is stored in the hard disk. Inquiries to the management module, (ii) receives information about the existence of the OK file from the management module, and (iii) receives information that the OK file exists from the data transmission device to the data reception device. Determine whether data can be transmitted, and (iv) determine whether data cannot be transmitted from the data transmitting apparatus to the data receiving apparatus when receiving information that the OK file does not exist A decision step;
When it is determined in the data transmission availability determination step that data can be transmitted from the data transmission device to the data reception device, the data management device requests the management module to delete the OK file via the network. An access exclusion step of causing the management module to delete the OK file by transmitting and eliminating other data transmission devices from transmitting data to the data reception device via the network;
After the OK file deletion request is transmitted in the access exclusion step, the data receiving device transmits an FTP file, which is a file containing the substance of data, to the management module via the network, thereby transmitting the FTP file to the management module. Transmitting data to the hard disk, and
After completion of transmission of the FTP file in the data transmission step, the data reception device sends a request to create an END file, which is a control file indicating that transmission of the FTP file from the data transmission device to the data reception device is completed. A write end declaration step for declaring that writing of data by the data transmission module is completed, by causing the management module to create the END file by transmitting to the management module via
After the data write end declaration is made in the write end declaration step, the management module stores the FTP file in the hard disk, the END file in the hard disk, and the application By determining that the rlock file, which is a control file indicating that the module uses the dat file, which is a file in which data included in the FTP file stored in the hard disk is added, is not stored, A data writability determination step for determining that data included in the FTP file can be additionally written to the dat file;
Control indicating that the management module is writing data to the hard disk when it is determined in the data writability determination step that data included in the FTP file can be added to the dat file A write declaration step that declares that the management module writes data to the hard disk by creating a wlock file that is a file, and excludes the application module from reading data from the hard disk;
A data writing step in which, after creating the wlock file in the writing declaration step, the management module appends data included in the FTP file stored in the hard disk to the dat file;
After the addition to the dat file in the data writing step, the management module deletes the FTP file and the END file;
An application module exclusive control release step of releasing exclusive control of the application module by deleting the wlock file after the FTP file and the END file are deleted;
After the exclusive control is released in the application module exclusive control release step, the management module releases the exclusive control for the other data transmission device by creating the OK file, and the dat file is newly created. A data transmission module exclusive control release step for notifying the application module that there is the usable dat file by creating an event file, which is a control file shown in FIG.
After informing the application module that there is the usable dat file in the data transmission module exclusive control release step, the application module stores the event file on the hard disk, and the wlock file The latest dat file that can be used by the application module is stored in the hard disk by determining that the OK file is not stored in the hard disk and the OK file is stored in the hard disk. A determination step of determining whether or not data can be read;
When it is determined that the latest dat file that can be used by the application module is stored in the hard disk in the data readability determination step, the application module creates the rlock file on the hard disk. A data write exclusion step for eliminating the management module from writing data to the hard disk;
An application step in which the application module executes a predetermined process using the dat file after the creation of the rlock file in the hard disk in the data write exclusion step is completed;
A data write permission step for allowing the management module to write data by deleting the rlock file and the event file from the hard disk after execution of the predetermined processing in the application step.
A data transmission / reception method. A data transmission / reception method by a data transmission / reception system for transmitting / receiving data,
The data transmission / reception system includes:
A data transmission device for transmitting data via a network;
A data receiving device for receiving data transmitted from the data transmitting device via the network;
The data transmission device includes:
An application module that creates the data to send,
A hard disk for storing data to be transmitted and at least one control file indicating the state of the data;
A management module that controls transmission or reception of data based on the presence or absence of the at least one control file;
When there is no wlock file that is a control file indicating that the management module is writing data to the hard disk, and there is no dat file that is a file containing data created by the application module. A first data writability determination step in which the application module determines that the dat file can be written to the hard disk;
An application step of generating a dat file by performing predetermined processing by the application module when it is determined in the first data writability determination step that the dat file can be written;
A first data writing step in which the application module writes the dat file to the hard disk after the dat file is generated in the application step;
After the writing of the dat file in the first data writing step, the management module is a control file indicating that the data receiving device has started receiving an FTP file containing data from the data transmitting device. A second data writability determination step for determining that the dat file can be added to the FTP file when a certain START file is not stored in the hard disk;
When it is determined in the second data writability determination step that appending to the FTP file is possible, the management module is a control file indicating that the management module is writing data to the hard disk A data write declaration step that declares that the management module writes data to the hard disk by creating a wlock file and excludes the application module from writing data to the hard disk;
A second data writing step in which the management module appends the dat file to the FTP file after creating the wlock file in the writing declaration step;
After the appending in the second data writing step, the management module is an END that is a control file generated when the START file and the data receiving device have completed receiving the FTP file from the data transmitting device. Deleting files and
A data write permission step for allowing the application module to write the dat file to the hard disk by deleting the wlock file and the dat file after the END file is deleted;
After the write permission is performed in the data write permission step, the management module creates an OK file that is a control file indicating that the data receiving device can receive the FTP file from the data transmitting device. A transmission data existence declaration step for declaring that there is an FTP file to be transmitted to the data receiving device;
After the declaration in the transmission data existence declaration step, the data receiving device (i) inquires of the management module via the network whether or not the OK file is stored in the hard disk, and (ii) the management Receiving information about the existence of the OK file from the module, and (iii) determining that the FTP file transmitted from the data transmission device can be received when information indicating that the OK file exists is received; (Iv) a data reception availability determination step of determining that reception of the FTP file transmitted from the data transmission device is impossible when information indicating that the OK file does not exist is received;
When it is determined in the data reception availability determination step that the FTP file transmitted from the data transmission device can be received, the data reception device sends the OK file to the management module via the network. Another data receiving module exclusion step for causing the management module to delete the OK file by transmitting a deletion request, and excluding other data receiving devices from accessing the hard disk via the management module;
After the exclusion in the other data module exclusion step, the data reception device causes the management module to create the START file by transmitting a request to create the START file to the management module via the network, and the management module A data write exclusion step that eliminates writing data to the hard disk;
A data receiving step in which the data receiving device receives an FTP file from the data transmitting device via the network after being excluded in the data writing exclusion step;
After receiving the FTP file in the data receiving step, the data receiving apparatus causes the management module to create the END file by sending a request to create the END file to the management module via the network, and A data reception end declaration step for declaring that reception of data by the data receiving device has ended.
A data transmission / reception method.

Images