JP2000163295A - File transfer management system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To avoid a data loss, etc., caused by the overlapping of file names by plural users. SOLUTION: A server 27 temporarily storing a data file transferred between client terminals 28 has a transmission file generation processing part 31 which changes a data file sent from a connected client terminal 28 from the original file name to a physical file name being inherent in a system and stores it and generates a tag file including the original file name and the physical file name, and has a file transfer control processing part 32 which adds a tag file to the data file and transfers it to a relay server 25. It also has a file receiving control processing part 37 which fetches a data file and a tag file to self based on the tag file of a relay server tag DB 46 and a received data file transfer control processing part 38 which changes the data file from the physical file name to the original file name and transfers it to the terminal 28 of a destination.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a file transfer management system, in particular, in a file transfer between clients performed over the same network, a data loss which may occur due to a file having the same name being transferred between clients and being overwritten. The present invention relates to a file transfer management system that can be avoided.

[0002]

2. Description of the Related Art FIG. 10 is an overall configuration diagram showing an example of a client server system used for performing a certain business. In FIG. 10, a plurality of servers 2 to 5 are connected to a network 1 such as a LAN or a dedicated line, and each of the servers 2 to 5 has a plurality of servers (two in this example) corresponding to clients. (Hereinafter, “client terminals”) 6 to 13 are connected. The client terminals 6 to 13 exchange data files with other client terminals 6 to 13 at the time of executing business processing. The servers 2 to 5 receive the data files issued by the connected client terminals 6 to 13 and transfer the data files to the designated destination.

[0003] In this configuration, the operation of the conventional system will be described by taking as an example a process in which the client terminal 6 transmits a data file to the client terminal 10. Is a data file addressed to the client terminal 10, the data file is sent to the network 1 side. If the destination is the client terminal 7, the data is transferred directly to the client 7 without sending it to the network 1. Upon receiving the data file sent by the server 2, the server 4 temporarily stores the data file therein. The client terminal 10 refers to a predetermined directory of the server 4 at an appropriate timing, and if there is a data file addressed to itself, extracts the data file therefrom. Thus, data files can be exchanged between the client terminals 6 to 13.

In the above example, in order for the client terminal 10 to determine whether or not the file in the server 4 is addressed to itself, the client terminal 10 negotiates the file name between the users who exchange files or the file name of the entire system. It is common to set rules on how to attach them. In the former case,
The file sender attaches a name determined in advance to the file recipient and transmits the file. For example,
When transmitting an invoice file, it is conceivable to give the file a name determined by including the characters "invoice" or further including a date. In the latter case, a rule is set for the method of naming the file, and the file is transferred with a name according to the rule. The file with the given name and transferred as described above is temporarily stored in a directory or folder assigned to each department of the client terminals 6 to 13 used by the recipient. The recipient recognizes that the file has been sent by finding a file having a predetermined name in the directory, and takes it out from the server 2 to 5 to its own client terminal 6 to 13.

[0005]

However, in the file transfer method used in the conventional system, a file normally sent to a certain client terminal may be lost. This is because the name of the data file temporarily stored in each server and addressed to the connected client terminal accidentally matches, and the file transferred earlier is overwritten by the file of the same name transferred later. This is because there is a case that
Even in the latter case, depending on the rules, there is a possibility that data of the same content is simultaneously transmitted from a plurality of client terminals. Note that the data having the same content here means, for example, "November bill" data, and does not mean that the billed amounts are the same.
Also, according to the rule, even if the file name cannot be duplicated, there may be a user who does not follow the rule, or the file name may be duplicated due to a human error such as an input error.

In some cases, a file sender does not know a client terminal used by a user even though the user is specified as a destination. In this case, the sender may not be able to transmit the file unless the sender recognizes the system environment.

SUMMARY OF THE INVENTION The present invention has been made to solve the above problems, and an object of the present invention is to temporarily store a transferred file in a server so that a client terminal retrieves the file from the server. It is an object of the present invention to provide a file transfer management system capable of avoiding data loss or the like due to duplication of file names by a plurality of users using a server even in a simple file storage type system.

[0008]

In order to achieve the above object, a file transfer management system according to the present invention comprises: a client as a data file transmission / reception destination;
Connecting at least one of the clients and controlling transmission of a file sent from the client;
A server for controlling the reception of the file sent to the client; and a network for connecting the servers, wherein the server stores the data file sent from the connected client in the system. A unique name is assigned, and transfer information including the unique name and the name given to the data file in the client is paired with the data file to transfer and manage the data file.

[0009] Further, the server assigns a unique name in the system to the data file sent from the connected client, and generates a tag file including transfer information of the data file. File transfer control processing means for transmitting the data file and the tag file generated by the transmission file generation processing means.

Further, the transmission file generation processing means includes:
Transfer information is generated based on information relating to transfer control such as transfer timing of the input designated data file and information related to the data file, and the file transfer control processing means converts the data file and the tag file at the input designated timing. What to send.

Alternatively, the transmission file generation processing means generates a unique file name in the system based on the user information of the transmission source and the date and time information.

Alternatively, the transmission file generation processing means generates broadcast information based on the contents specified and input when transferring the data file to a plurality of destinations, and adds it to the transfer information.

Alternatively, the server has transmission file maintenance management means for performing file management such as deletion of the data file sent from the client and the tag file generated by the transmission file generation processing means.

Alternatively, the file transfer control processing means records a file transfer result in an operation log file.

[0015] The server may further comprise a file reception control processing means for receiving a data file addressed to the connected client and transfer information corresponding to the data file, and a server addressing the client in response to a request from the connected client. Receiving data file transfer control processing means for changing the name of the data file from a unique name of the system based on the transfer information to a name given to the client at the transmission source and transferring the data file.

Further, the server has received file maintenance management means for performing file management such as update and deletion of a data file received by the file reception control processing means and a tag file including transfer information.

Alternatively, the file reception control processing means records the transfer result of the data file to the client in an operation log file.

Alternatively, the reception data file transfer control processing means changes the data file addressed to the client from a name unique to the system to a name given in the client at the transmission source based on the transfer information, and displays the screen. Is transferred to the client.

Further, the server has address information storage means for associating a user with a group to which the user belongs, and the received data file transfer control processing means stores, as destination information of the data file, When the name and the group name to which the user belongs are included, information on a data file addressed to the group to which the user using the client belongs is displayed on the screen in response to a request from the connected client. .

[0020] Also, a received file management means for receiving a data file transmitted by the server and transfer information corresponding to the data file, and responding to a request from the server, corresponding to the stored data file and the data file. File transfer control processing means for transmitting the transferred transfer information, and a relay server for relaying a file transferred between the servers via the network.

Further, the file transfer control processing means includes:
The result of the file transfer to the server is recorded in an operation log file.

Alternatively, there is provided a relay server internal file maintenance / management means for performing file management such as updating and deleting data files stored in the relay server and transfer information corresponding to the data files.

Alternatively, the server holds user information for using the connected client, and the file reception control processing means extracts a file addressed to the user using the connected client from the relay server. The processing is executed.

[0024]

Preferred embodiments of the present invention will be described below with reference to the drawings.

FIG. 1 is an overall configuration diagram showing an embodiment of a file transfer management system according to the present invention. In this embodiment, a client server system used for performing a certain task is shown. ing. FIG. 2 is a functional block diagram of each component shown in FIG.

In FIG. 1, a plurality of servers 21 to 24 and a relay server 25 are connected to a network 1 such as a LAN or a dedicated line.
24 has a plurality of client terminals 6 to 13 respectively.
However, a monitoring terminal device 26 is connected to the relay server 25. Note that the same reference numerals are given to components that may be the same as those in the related art. The client terminals 6 to 13 serve as final destinations for transmitting and receiving data files, and exchange data files with other client terminals 6 to 13 when executing business processes. The servers 21 to 24 perform transmission control of the file sent from each of the connected client terminals 6 to 13, and
3 is received. The relay server 25 is connected to the servers 21 to 24 via the network 1.
Relay files transferred between them. The monitoring terminal device 26 manages files stored in the relay server 25. In this embodiment, the four servers 21 to 2
4 to the network 1 and 2
Client terminals 6 to 7, 8 to 9, 10 to 1 each
1, 12 to 13 are connected, but each number is not limited to this example.

Since each of the servers 21 to 24 and each of the client terminals 6 to 13 may have the same configuration, FIG. 2 illustrates only one server 27 and one client terminal 28. The client terminal 28 has a conventional function such as a function of transmitting a data file to be transmitted to another client terminal 28 to the connected server 27 and a function of retrieving a self-addressed data file stored in the connected server 27. Can be realized.

The server 27 is provided with a transmission file generation processing section 31, a file transfer control processing section 32, and a transfer information setting section 33 as means for controlling file transmission. The transmission file generation processing unit 31 allocates a unique name in the system to the data file sent from the client terminal 28 and generates a tag file including transfer information of the data file. At this time, the transmitted data file is stored in the transmission data file storage unit 34, and the tag file is stored in the transmission tag file database (DB) 35. The file transfer control processing unit 32 transmits the data file and the tag file generated by the transmission file generation processing unit 31. Further, the server 27 has a transmission file maintenance management unit that performs file management such as deletion of the data file and the tag file stored in the transmission data file storage unit 34 and the transmission tag file DB 35. The functions of the maintenance management unit 36 are installed in the file transfer control processing unit 32. Further, in the present embodiment, since the transfer information is set by logging in to the server 27 from the client terminal 28, the transfer information setting unit 33 that performs the processing function for this is provided by the server 27 in FIG. And the client terminal 28.

Further, the server 27 is provided with a file reception control processing section 37 and a reception data file transfer control processing section 38 as means for controlling file reception. The file reception control processing unit 37 receives a data file addressed to the connected client terminal 28 and a tag file including transfer information corresponding to the data file.
The received data file and tag file are stored in the reception data file storage unit 39 and the reception tag file database (DB) 40, respectively. Further, the server 27 has a received file maintenance management unit that performs file management such as deletion of data files and tag files stored in the received data file storage unit 39 and the tag file DB 40 for reception. The function of the maintenance management unit 41 is installed in the file reception control processing unit 37. In response to a request from the connected client terminal 28, the reception data file transfer control processing unit 38 assigns a data file addressed to the client terminal 28 to a name assigned to the client terminal 28 from the system-specific name based on the transfer information. Change to and then transfer.

On the other hand, the relay server 25 is provided with a received file management unit 42, a file transfer control processing unit 43, and a file maintenance management unit 44 in the relay server. The received file management unit 42 receives and stores the data file transmitted by the server 27 and the tag file including the transfer information corresponding to the data file. The received data file and tag file are stored in the relay server data file storage unit 45 and the relay server tag database (DB) 46, respectively. The file transfer control processing unit 43 transmits a data file and a tag file including transfer information corresponding to the data file in response to a request from the server 27. In this embodiment, the monitoring terminal device 26 logs in to the relay server 25, and the relay server data file storage 45 and the relay server tag DB.
File management such as updating and deleting of the data file and the tag file stored in 46 is performed. The file maintenance management unit 44 in the relay server provides the function.

FIG. 3 is a diagram showing an example of a data configuration of a database for storing tag files according to the present embodiment. This data configuration includes the transmission tag DB 35, the reception tag DB 40, and the relay server 2 in the servers 21 to 24.
5 is the same as the relay server tag DB 46 in FIG. Each of the tag DBs 35, 40, and 46 is composed of a tag file generated corresponding to a data file to be transferred and an operation log file.

The tag file contains transfer information, that is, information used for transfer control of the data file. The present embodiment is characterized in that a tag file is provided corresponding to a data file, and the tag file includes a physical file name and an original file name as a part of transfer information. I have. The physical file name is a name automatically and uniquely assigned to a data file in the system.
The original file name is the name of the client terminal 2
8 is a file name to be assigned to a data file inside the file 8 and a file name to be assigned to a destination user of the file or based on rules. Other information will be described later.

FIG. 4 shows a server 27 according to the present embodiment.
Address information database (DB) 4 prepared in advance
7 is a diagram illustrating an example of a data structure of FIG. In the address information DB 47, address information on a user who uses this system is registered. In this embodiment,
It includes a user master containing information on the individual user and a group master containing information on the department to which each user belongs. In the group master, a group code (department code) and a group name (department name) are registered. The user master contains the user code (user I
D), a password, a user name (name), and a group code to which the user belongs are registered.

The feature of this embodiment is that a unique file name (physical file name) is assigned to a file name to be transferred in the system, and a tag file including the physical file name and the original file name is assigned. This is to add the data file and transfer it. Accordingly, the files transferred on the network 1 all have different file names.
24, it is possible to prevent the data file previously received with the same file name from being lost by overwriting.

Next, the operation in the present embodiment will be described with reference to a flowchart showing the procedure of each processing. Here, a case where a data file is transferred from the client terminal 6 to the client terminal 10 will be described as an example.

First, from the client terminal 6 to the server 21
Fig. 5 shows the processing performed when sending a data file to
A description will be given based on the flowchart shown in FIG.

The client terminal 6 issues a connection request to the server 21 when it wants to transmit a data file, and logs in to the server 21 when it is accepted (step 1).
01, 201). Then, necessary information is registered from the transfer information setting screen in the client terminal 6 (step 102). This process is executed by a function of the transfer information setting unit 33. The information set here is shown in FIG.
(Step 103). The information to be input and designated by the user includes the name of the data file to be transferred (original file name), a file title describing its contents, the period to be stored in the server 21, comments, and schedule information. The comments include information about the data file, for example, the purpose of the data as described in the header letter sent for business purposes, the fact that data handling precautions and responses are expected, and the response deadline. Enter characters. In the schedule information, information relating to transmission timing such as when the data file is transmitted, such as date and time and day of the week, and information relating to retransmission when transmission is not possible are set. The destination of the data file is also set here, which is set with reference to the address information DB 47.

Transmission file generation processing unit 31 of server 21
Receives the set transfer information (step 20).
3) The transfer information to be registered in the tag file is completed by automatically setting other transfer information in addition to the information (step 204), and registered in the transmission tag DB 35 (step 205). The present embodiment is characterized in that a system-specific name (physical file name) is assigned to a data file created by a user as described above. In step 204, this physical file name is generated as follows. That is, a file name is generated by concatenating information of a transmission source user, for example, a user ID and date and time information, specifically, year, month, day, hour, minute, and second when transfer information is set, and a file type (eg, “DAT”) is set. Generate physical file names by concatenating them with periods. As a result, the setting process for a plurality of data files is not usually performed by one user at the same time, so that data files with different names can be reliably generated. In the same manner, the corresponding data file and file type (for example, “TA
G ″) is assigned a different physical file name.

Thereafter, the transmission file generation processing unit 31
When the data file generated by the user is transferred from the client terminal 6, it is received (step 104,
206), the physical file name registered in the tag file is assigned to the data file and registered in the transmission data file storage unit 34 (step 207). And
The server 21 disconnects the connection in response to the connection disconnection request from the client terminal 6 (steps 105 and 208).
Specifically, the client terminal 6 logs out of the server 21.

Next, processing performed when a file is transferred from the server 21 to the relay server 25 will be described with reference to the flowchart shown in FIG.

The file transfer control processor 32 of the server 21
Checks periodically for schedule data set in the tag file of the transmission tag DB 35 to check for a data file that has reached the transmission timing (step 21).
1). When the corresponding data file exists, a connection request is issued to the relay server 25 (step 212). The relay server 25 accepts a connection in response to a request from the server 21 (Step 301). When the connection is confirmed (step 211), the server 21 searches for the corresponding tag file and transmits it to the relay server 25 (steps 213 and 214).

The received file management unit 42 of the relay server 25
Registers the tag file in the relay server tag DB 36 for each destination based on the received tag file (step 3).
02-304). Subsequently, the reception file management unit 42
Upon receiving the data file sent from the server 21 (steps 215, 305), the data file is registered in the relay server data file storage unit 45 with the physical file name registered in the tag file (step 306). Then, the connection is disconnected in response to the connection disconnection request from the server 21 (steps 216 and 307).

File transfer control processor 32 of server 21
After the line is disconnected, the file transfer result is stored in the operation log file of the transmission tag DB 35 as a transmission result log (step 217). By recording the transfer result, it can be useful for maintenance such as recovery work when a failure or the like occurs.

Further, the transmission file maintenance management section 36 searches the storage period set in the tag file (step 218), and stores the tag file having exceeded the storage period and the corresponding data file in the transmission tag, respectively. DB
35 and the transmission data file storage unit 36 (step 219).

Next, processing performed when a file is transferred from the relay server 25 to the server 23 will be described with reference to the flowchart shown in FIG.

The file reception control processing section 37 of the server 23
Issues a connection request to the relay server 25 periodically at the timing of a predetermined transfer schedule in the entire system (steps 221 and 222). Relay server 2
5 connects the line in response to a request from the server 23 (step 311), and if there is a tag file addressed to the server 23, the file transmission control unit 43 reads the tag file from the relay server tag DB 46 and 23
(Step 312), and reads the corresponding data file from the relay server data file storage unit 45 and transfers it to the server 23 (step 313). In addition,
Each of the servers 21 to 24 knows which user or department uses the connected client terminals 6 to 13 by setting a flag or the like in the address information DB 47. In addition, the transfer result of each file is accumulated in the operation log file of the relay server tag DB 46 as a transmission result log (step 314). By recording the transfer result, it can be useful for maintenance such as recovery work when a failure or the like occurs.

The file reception control processing section 37 of the server 23
Registers the tag file sent from the relay server in the receiving tag DB 40 (steps 223 and 224).
At this time, information such as registration date and time and storage period in the tag file is updated. Further, the transmitted data file is registered in the received data file storage unit 39 with the physical file name registered in the tag file (step 2).
25, 226). When the line between the server 23 and the relay server 25 is disconnected by a request from the server 23 (steps 227 and 315), the received file maintenance management unit 41
Retrieves the storage period set in the tag file (step 228), and deletes the tag file that has exceeded the storage period and the corresponding data file from the reception tag DB 40 and the reception data file storage unit 39, respectively. (Step 229).

As described above, in the present embodiment,
The servers 21 to 24 independently take out the data files from the relay server 25. This is executed when the transmission source server 21 performs broadcast transmission to a plurality of client terminals 8 to 13 connected to the other servers 22 to 24 based on one data file or when retransmission is performed due to a failure. The processing load on the transmission source server can be greatly reduced, and the processing of the entire system can be simplified.

Next, from the server 23, the client terminal 1
FIG. 8 shows a process performed when a file is transferred to “0”.
A description will be given based on the flowchart shown in FIG.

The client terminal 10 issues a connection request to the server 23 at an appropriate timing, such as when it is desired to perform processing on the data file, and logs in to the server 23 when the connection request is accepted (steps 111 and 231). Then, the reception data file transfer control processing unit 38 displays a list of transfer information in the tag file addressed to the login user read from the reception tag DB 40 by the server 23 on the screen of the client terminal 10 (step 23).
2, 112). When the users are managed by groups (departments) as in the present embodiment, information on data files addressed to the department to which the login user belongs may be displayed. At this time, the stored data file is displayed with the original file name. When the user specifies the data file to be extracted by referring to the title of the data file of the transfer information displayed on the screen, the source user name, and the like, the corresponding data file is selected in response to the specified data file extraction request. It is read from the received data file storage unit 39 (steps 113, 233, 234). Then, the reception data file transfer control processing unit 38 changes the physical file name unique to the system to the name assigned by the transmission source user (original file name) based on the transfer information and then reads the read data file to the client terminal 10. Transfer (step 235). Then, the transfer result of the data file is accumulated in the operation log file of the reception tag DB 40 as a transmission result log (step 23).
6). By recording the transfer result, it can be useful for maintenance such as recovery work when a failure or the like occurs. After saving the transferred data file (steps 114 and 115), the client terminal 10 logs out of the server 23 (steps 116 and 23).
7).

As described above, the data file is transferred from the client terminal 6 to the client terminal 10.

Finally, the maintenance management of the relay server data file storage unit 45 and the relay server tag DB 46 stored in the relay server 25 will be described with reference to the flowchart shown in FIG.

When maintenance of the relay server data file storage unit 45 or the relay server tag DB 46 of the relay server 25 is to be performed, the user issues a connection request from the monitoring terminal device 26 to the relay server 25 and receives the connection request. Login to 25 (Step 40)
1,321). Relay server internal file maintenance management unit 44
Reads the transfer information registered in the relay server tag DB 46 and displays a list on the screen of the monitoring terminal device 26 (steps 322 and 402). When the user specifies the tag file or data file to be changed or deleted by referring to the contents of the transfer information displayed on the screen,
The file maintenance management unit 44 in the relay server updates each file in response to the change / deletion request for the specified file. That is, if the request is a transfer information setting change request, the corresponding transfer information registered in the relay server tag DB 46 is changed (step 324). If the request is a data file deletion request, the corresponding data file and tag file are deleted from the DBs 45 and 46 (steps 324 and 325). When the above maintenance is completed, the user logs out of the relay server 25 in accordance with the operation of the user (steps 404 and 326).

The file maintenance management unit 44 in the relay server
Thereafter, the storage period set in the tag file is further searched (step 327), and the tag file whose storage period has been exceeded and the corresponding data file are stored in the relay server data file storage unit 45 and the relay server tag DB 46, respectively. It is deleted (step 328). As described above, since the data file and the tag file stored in the relay server 25 can be directly changed or deleted, for example, an erroneous data file is transmitted to a predetermined destination. If the data file has not been transferred to the destination server, for example, if the contents of the comment are to be changed, the change can be dealt with.

As described above, according to the present embodiment, in the servers 21 to 24, the relay server 25, and the network 1 used by a plurality of users, the file exchanged between the users is system-specific. Is assigned and stored and transferred, so that it is possible to avoid data loss due to overwriting of a file with the same name. Of course, when a user handles a data file, the data file is converted to a predetermined file name between the users and then transferred, so that the user can handle the file with the conventional file name.

In the present embodiment, a tag file is added to a data file and the data file is transferred, as in the case of a parcel package and a tag. If various information such as the correspondence relationship between the physical file name and the original file name and the transfer timing and comments are set in the tag file, various information can be stored without editing the data file itself. It can be added and transferred.

In the above embodiment, the case of one-to-one file transfer has been described as an example. However, one-to-many transfer can also be supported. In other words, if you want to send one data file to a plurality of client terminals 6 to 13,
In the present embodiment, when setting the transfer information in step 102, the fact and the destination can be set, and in step 103, the broadcast information is registered in the tag file. Each server 21 in the present embodiment
24 through 24 independently take out files addressed to themselves from the relay server 25 (steps 221 to 224). If one data file is transferred to the relay server 25, a plurality of Server 21-
24 can be implemented.

Further, by using the present embodiment, even when data files having the same contents such as a questionnaire are collected at one place, the data files can be collected without being overwritten. For example, a questionnaire form (data file) for a plurality of users (servers)
If you try to conduct a questionnaire by sending the questionnaire and adding the necessary information to the questionnaire and returning it, if you have distributed one questionnaire (data file) to multiple Since the returned data file names are the same, they are sequentially overwritten with the latest data file. If the file name of the questionnaire sheet is changed for each user, such a situation does not occur, but a heavy load is imposed on the questionnaire implementer.

Therefore, according to the present embodiment, the questionnaire results may be overwritten and lost in the server where the questionnaire is collected and stored, because the server is stored with a unique physical file name in the system. Absent. As described above, the questionnaire can be easily implemented without performing a troublesome operation of changing the data file name for each destination.

[0060]

According to the present invention, on a server or the like used by a plurality of users, a system-specific name is assigned to a file to be transferred between clients, and the file is stored and transferred. Data can be prevented from being lost due to being overwritten by a file having the same name. Of course, when the destination user receives the data file, it converts the name unique to the system to the file name set on the client before giving it to the user.
The user can handle the file on the client with a name predetermined between the sender and the receiver.

A list of information on data files addressed to a user or a group to which the user belongs is displayed in a list, and a data file to be read can be specified from the list. At the time of this display, the file name is displayed not by the system but by the name given to the client at the transmission source, so that the user can easily specify the data file to be taken out.

Further, since the transfer information is added to the data file and the data file is transferred to the destination, by setting, for example, information on the presence or absence of a comment or a response regarding the data file as the transfer information, the data file can be edited and processed. Various information can be added to the data file and transferred without the need.

In particular, if the transfer timing to the destination is set as the transfer information, the data file can be transferred at an arbitrary timing.

Since the broadcast information is added to the transfer information, the data file can be transferred to a plurality of clients only by preparing one data file.

Also, since a maintenance management means for deleting files stored in the server or the relay server is provided, unnecessary files can be deleted as appropriate.

When a file is transferred, the transfer result is recorded in an operation log file.
This can be useful for maintenance such as recovery work when a failure or the like occurs. For example, if the source user of the file that could not be transferred is recorded, the source user can be easily specified.

According to the present invention, a relay server capable of temporarily storing a file transferred between servers is provided, so that the file can be transferred to a destination client at an appropriate timing. In particular, by causing the server to retrieve a file from the relay server, it is possible to reduce the processing load on the transmission source server when a failure occurs or when a file is transferred at a scheduled timing.

[Brief description of the drawings]

FIG. 1 is an overall configuration diagram showing an embodiment of a file transfer management system according to the present invention.

FIG. 2 is a functional block diagram of a file transfer management system according to the present embodiment.

FIG. 3 is a diagram illustrating an example of a data configuration of a database that stores tag files according to the present embodiment.

FIG. 4 is a diagram showing an example of a data structure of an address information database prepared in advance in a server according to the present embodiment.

FIG. 5 is a flowchart showing processing performed when a data file is transmitted from a client terminal to a server in the present embodiment.

FIG. 6 is a flowchart illustrating processing performed when a file is transferred from a server to a relay server in the present embodiment.

FIG. 7 is a flowchart showing processing performed when a file is transferred from the relay server to the server in the present embodiment.

FIG. 8 is a flowchart showing processing performed when a file is transferred from a server to a client terminal in the present embodiment.

FIG. 9 is a flowchart illustrating a process of maintaining and managing the relay server data file storage unit and the relay server tag database stored in the relay server in the present embodiment.

FIG. 10 is a diagram showing a configuration example of a client-server system for explaining conventional file transfer management.

[Explanation of symbols]

1 network, 6 to 13,28 client terminal, 21 to 24,27 server, 25 relay server, 26
Monitoring terminal device, 31 transmission file generation processing unit, 3
2 file transfer control processing unit, 33 transfer information setting unit,
34 transmission data file storage unit, 35 transmission tag file database (DB), 36 transmission file maintenance management unit, 37 file reception control processing unit, 38 reception data file transfer control processing unit, 39 reception data file storage unit, 40 reception Tag file database (D
B), 41 received file maintenance management section, 42 received file management section, 43 file transfer control processing section, 44 relay server file maintenance management section, 45 relay server data file storage section, 46 relay server tag database (DB), 47 Address information database (DB).

Claims (16)

[Claims] 1. A client that is a data file transmission / reception destination and at least one of the clients are connected, and transmission control of a file sent from the client is performed.
A server that controls reception of a file sent to the client; and a network that connects the servers, wherein the server stores a data file sent from the connected client in the system. A unique name is assigned, and transfer information including the unique name and the name given to the data file in the client is paired with the data file to transfer and manage the data file. File transfer management system. 2. A transmission file generation processing means for allocating a unique name in the system to a data file transmitted from the connected client and generating a tag file including transfer information of the data file, the server comprising: The file transfer management system according to claim 1, further comprising: file transfer control processing means for transmitting the data file and the tag file generated by the transmission file generation processing means. 3. The transmission file generation processing means generates transfer information based on information related to transfer control such as transfer timing of an input-designated data file and information related to a data file. 3. The file transfer management system according to claim 2, wherein the data file and the tag file are transmitted at a timing specified by the input. 4. The file transfer management system according to claim 2, wherein the transmission file generation processing unit generates a unique file name in the system based on the user information and the date and time information of the transmission source. 5. The transmission file generation processing means according to claim 1, wherein when transmitting the data file to a plurality of destinations, the transmission file generation processing means generates broadcast information based on the contents designated by input and adds the broadcast information to the transfer information. 2. The file transfer management system according to 2. 6. The server has a transmission file maintenance management unit that performs file management such as deletion of a data file sent from the client and a tag file generated by the transmission file generation processing unit. The file transfer management system according to claim 2. 7. The file transfer management system according to claim 2, wherein said file transfer control processing means records a file transfer result in an operation log file. 8. The server includes: a file reception control processing unit that receives a data file addressed to the connected client and transfer information corresponding to the data file; and a server that receives the data file addressed to the client in response to a request from the connected client. 2. A reception data file transfer control processing means for transferring a data file after changing a data file name from a system-specific name based on transfer information to a name given by the client at the transmission source, and transferring the data file. File transfer management system. 9. The server according to claim 1, wherein said server has a received file maintenance management unit that performs file management such as updating and deleting a data file received by said file reception control processing unit and a tag file including transfer information. Item 8. The file transfer management system according to Item 8. 10. The file transfer management system according to claim 8, wherein said file reception control processing means records a transfer result of the data file to said client in an operation log file. 11. The reception data file transfer control processing means changes a data file addressed to the client from a name unique to the system to a name given to the client at the transmission source based on the transfer information, and displays the screen.
9. The file transfer management system according to claim 8, wherein the data file specified from the screen is transferred to the client. 12. The server has address information storage means for associating a user with a group to which the user belongs, and the received data file transfer control processing means includes a user of a file recipient as destination information of a data file. In the case where the name and the group name to which the user belongs are included, information on a data file addressed to the group to which the user using the client belongs is displayed on the screen in response to a request from the connected client. The file transfer management system according to claim 11, wherein 13. A received file management means for receiving a data file transmitted by the server and transfer information corresponding to the data file, and responding to a request from the server for storing the stored data file and the data file. The file transfer according to claim 1, further comprising: a file transfer control processing unit that transmits the transferred transfer information; and a relay server that relays a file transferred between the servers via the network. Management system. 14. The file transfer management system according to claim 13, wherein said file transfer control processing means records a file transfer result to said server in an operation log file. 15. A relay server file management unit that performs file management such as updating and deleting data files stored in the relay server and transfer information corresponding to the data files. The file transfer management system described. 16. The server holds user information for using the connected client, and the file reception control processing unit extracts a file addressed to a user using the connected client from the relay server. 14. The file transfer management system according to claim 13, wherein the system executes processing.