JPS58161032A - File transfer protocol system - Google Patents

Abstract

PURPOSE:To transfer files having various organizations between computers constituting a network, by transferring detailed characteristic information of a transmission file and required information concerning a receiving file from the transmission side before file transfer. CONSTITUTION:When a file transfer controlling mechanism 3 of a computer 1 is requested to transfer a file 5 to a file 6 in a computer 2, a transmission management table 10 including characteristic information concerning the transmission file and the receiving file is transmitted to a reception side 8 by a transmission preparation processing 9 of a transmission side 7 before actual transmission and reception processings of data. The table 10 includes a file name, a file organizing method, a space quantity, a block size, a record format, etc. as transmission characteristic information and includes a file name, a file organizing method, etc. as reception file information. When receiving the table 10, the reception side 8 performs a reception preparation processing 11 and responds to the transmission side if tranfer is possible. Then, a file transmission processing 12 is performed in the transmission side 7, and the reception side 8 receives the file and performs a file reception processing 13.

Description

DETAILED DESCRIPTION OF THE INVENTION The present invention relates to a file transfer protocol (file transfer procedure) for transferring files between computers connected to Net21M.

Connecting geographically separated computers via a network and promoting mutually effective use of the computers is becoming increasingly important and continues to develop as society becomes increasingly computerized. In this type of system, computing institutions can not only send and receive small amounts of data such as messages, but also freely transfer large amounts of data such as jobs and files. It has become a necessary condition.

There are various ways to organize files handled by computers, such as sequential files, partitioned files, and direct files, depending on the purpose of use. There are a wide variety of format programs and other arbitrary data.

In file transfer processing by a computing engine that targets files with such characteristics, a problem arises as to how files with various organizations and contents can be transferred.

The general method of conventional file transfer is to individually allocate the sending file on the sending side and the receiving file on the receiving side, and then synchronize and transfer the data. Met. This method had the following problems.

(1) Things that the receiving side needs to know in advance about the received file.

(2) Transfer files are limited to specific types such as sequential files. Also, it is difficult to transfer files with different organization.

The purpose of the present invention is to provide a computing engine that configures a network warehouse,
The object of the present invention is to provide a procedure that enables the transfer of files of various types such as sequential files, partitioned files, and direct files.

Another object of the invention is to provide a procedure that allows transfer between files of potentially heterogeneous organization in any possible combination.

Another object of the present invention is that the receiving side does not need to know in advance about the received file, and therefore the sending side can transfer files to any file (either an existing file or a new file) on the receiving side. The purpose is to provide steps that can be taken.

Another object of the present invention is to provide a procedure that allows a computer to receive a file residing on another computer upon request.

The feature of the present invention is that, prior to the actual file transfer, the sending side transfers detailed characteristic information of the sending file and necessary information regarding the receiving file, so that both the sending and receiving sides can receive the same information. (9) Appropriate file transmission/reception processing can be performed according to the information on the receiving side, and it is possible to perform file transfer of various types of organization, transfer between files of different organization, transfer to any file on the receiving side, etc., as listed for the purpose of the present invention. be.

The present invention will be comprehensively explained below.

FIG. 1 shows an example of the configuration of a network consisting of a plurality of computers, using two computers as representatives. File transfer is performed between the file transfer control mechanism 3 of the computer 1 and the file transfer control mechanism 4 of the computer 2. Now, with computer 1 on the file sending side and computer 2 on the file receiving side, a request is made to the file transfer control mechanism 2 of computer 1 to transfer file 5 in computer 1 to file 6 in computer 2. There was 5
Consider the case. FIG. 4 shows the basic method of a high-order file transfer protocol in such a case. In the high-order file transfer protocol, before actual data transmission/reception processing, first, in transmission preparation processing 9 on the sending side 7, a transmission management table 10 containing detailed characteristic information regarding the sending file and the receiving file is sent to the receiving side 8. do. The transmission management table 10 contains, as characteristic information of the transmitted file, file name, file organization method, amount of space,
It includes block size (size of file input/output unit), record format, etc. Information regarding the received file includes information such as file name, file organization method, etc. In reception [8, the transmission side 7 sends a transmission management table 10 containing characteristic information of the transmitted file and the received file.
When the received file is an existing (7) 7 file, the process first performs reception preparation processing 111. If the received file is an existing (7) 7 file, obtains the characteristic information of the existing file and compares it with the characteristic information of the transmitted file in the transmission management table. to test the validity.

If the characteristic information matches, transfer is possible; if they do not match, transfer is impossible. On the other hand, if the received file is a new file, the new file can be allocated according to information such as the space amount and block size of the transmitted file in the transmission management table, and the organization method of the received file. In this way, by transferring the characteristic information of the transmitted/received file prior to the actual transmission/reception of data, transmission to any file, regardless of whether it is an existing file or a new file, becomes possible. After the file transmission/reception preparation process described above is completed, actual data transmission/reception is performed. In the file transmission process 12 of the transmitting side 7, a data transfer format is selected and determined based on the combination of transferred and received files, while the receiving side 8 The file reception processing 13 can perform reception processing and data storage processing corresponding to the characteristics of the transmitted/received file.

The basic method of such a high-order file transmission/reception protocol enables file transfer between various combinations of sending files and receiving files as shown below.

(1) Transfer from IIM-configured file to sequential-organized file.

(2) Transfer from a member of a partitioned file to a partitioned file.

(3) Transfer from an entire partitioned file to an entire partitioned file.

(4) Transfer from a sequential file to a member of a partitioned file.

(5) Transfer from a member of a partitioned file to a sequential file.

(6) Transfer from direct organization file to direct organization file.

The case where a file is transmitted from computer 1 to computer 2 has been described above. Next, a case will be described in which computer 1 requests to receive a file existing in computer 2. In this case, computer 1 first sends a transmission management table containing only the file name to be received and the file name of the recipient to computer 2, and from then on, computer 1 and computer 2 play the roles of the sender and receiver. By reversing the above, the method described above can be applied as is, and it becomes possible to receive a file existing on another computer in response to a request from one computer, which is the last objective of the present invention.

Hereinafter, the present invention will be explained in detail with reference to Examples.

FIG. 3 shows only the processing portion related to the high-order file transfer protocol when mutual file transfer is performed between the computing institutions that constitute the network. Each mechanism displayed in this figure is a functionally displayed control program for executing the present invention, and these mechanisms exist in each computer that constitutes the network.

When a file transmission request is received, the file transmission preparation controller 14 performs the necessary preparations to access the seven transmission aisles, and also creates a transmission management table containing detailed characteristic information regarding the transmission file and the reception file. It is transmitted to the file reception preparation controller vlIl 5 on the receiving side. On the other hand, the file reception preparation control mechanism 15 performs the ninth preparation process for receiving a file. Upon receiving the transmission management table, if the received file is an existing file, it checks the consistency of the characteristics of the transmitted file. do. If the received 7 file is a new file, a file is created based on the characteristics of the transmitted file.

When preparations for file transmission on the sending side and preparations for receiving files on the receiving side are completed, the mourning file transmission control mechanism and file reception control mechanism perform actual data transmission and reception, depending on the combination of the sending and receiving file organization methods. Controls processing. The sequential organization-sequential file transmission control mechanism 16 controls file transmission processing when transferring a sequential file to a sequential file, and the segmented member sequential file transmission control mechanism 17 controls the individual member order of the segmented file. Controls file transmission processing when transferring to an organization file. In both of these two cases, transmission is to a sequential file, and the data transfer format is -fi, so on the receiving side, the file reception ylylI# mechanism 21 for sequential files commonly handles reception processing.

Segmented organization member Segmented import member/Segmented organization - Segmented organization file transmission control mechanism 18 transfers individual members of a partitioned organization file to individual members/(K) of a partitioned organization file, and transfers the entire partitioned organization file to a partitioned organization file. The sequential/segmented member file transmission control mechanism 19 controls the file transmission process when transferring a sequential file to an individual member of a segmented file. Since both are transmissions to a segmented organization file and the data transfer formats match, on the receiving side, the reception control mechanism 22 for segmented organization files commonly controls the receiving unit ffl.

When transferring a direct organization file to a direct organization file, the direct organization-direct organization file transmission control mechanism 20 controls the transmission process, and the direct organization file reception controller 1p1
23 manages reception processing.

The operation of file transmission/reception preparation control performed between the file transmission preparation control mechanism 14 and the file reception preparation controller IP 115 will be explained (FIG. 4). On the sending side, first, in step 24, the process of allocating the sending file (preparation for accessing the file) is performed, and then in step 25, detailed characteristic information regarding the sending file is acquired and stored in the transmission management table. Furthermore, in step 26, the file name and file organization method type regarding the received file are stored in the transmission management table. As shown in FIG. 9, the transmission management table includes, as characteristic information of the transmitted file, file name, member name (only when transmitting individual members of a partitioned file), and file type.

File organization method type, amount of space, block length.

Includes record format, record length, etc. After all information is stored in the transmission management table, in step 27 the transmission file is opened to prepare for access to the transmission file, and in step 28 the transmission management table is sent to the receiving side and waits for notification of preparation completion from the receiving side. . On the other hand, when the receiving side receives the transmission management table in step 32, it first checks in step 33 whether the received file is an existing file or a new file to be created. If the received file is an existing file, the received file is allocated in steps 34 and 35, and at the same time, file characteristic information is acquired, and the block length and record format regarding the transmitted file in the transmission management table are acquired.

Check whether it matches characteristic information such as record length. If they match, the file can be received. On the other hand, if the received file is a new file, the file name, file organization method type, and space amount for the transmitted file of the received file in the transmission management table are entered in step 36.

A new file is created based on characteristic information such as record format and record length.Next, in step 37, the receiving file t is opened and preparations for access are made, and then in step 38, a response is sent to the sending side indicating that reception preparation is complete. . Send m for more than
The sending side completes the preparation process for sending and receiving files, and the sending side calls the file sending control mechanism t corresponding to the combination of the sending file and receiving file organization method in step 30, while the receiving side Then, in step 39, a file reception controller wt-call is made that corresponds to the organization method of the received file.

a sequential-sequential file transmission control mechanism 16 that controls transmission when transferring a sequential file to a sequential-form file;
and individual members of the partitioned file) between the two transmission control mechanisms of the partitioned member sequential file transmission controller W417 that controls transmission when transferring to the @organized file, and the file reception control mechanism 21 for sequential organization. The operation of sending and receiving files will be explained (@Figure 5). On the sending side,
When transmitting a member of a segmented file, first, in step 40, the first position in the segmented file where the member to be transmitted is stored is found, but the subsequent processing is when transmitting a sequential file. It is common to That is, in step 41, the next block 1km from the file
If the end of the file has not been reached as determined in step 42q), the block is stored in the transfer buffer in step 43, and the processing from step 41 is repeated until the transfer buffer is full. When the transfer buffer is full as determined in step 44, the transfer buffer is transmitted to the receiving side in step 45. When it is detected in step 42 that the end of the file (or the end of the member in the case of sending a member of a partitioned file -) is detected, step 46 displays the fact that it is the final data in the transfer buffer and sends it. After sending the final transfer buffer and waiting for a response from the receiving side to complete the receiving process, step 47
Performs file transmission termination processing such as closing the transmission file and deallocating it.

On the other hand, on the receiving side, when the transfer buffer is received in step 48, in step 49 individual blocks are cut out from the transfer buffer (deblocking), and in step 50, the blocks are written to the reception file, and at the end of the transfer buffer. Repeat until reached. When it is determined in step 51 that fIA output has been completed for all blocks in the transfer buffer, it is further determined in step 52 that all received data has been completed, and if it has not been completed, the next transfer buffer is received and the same process is repeated. When the writing of the block in the transfer buffer is completed, file reception end processing such as closing processing and deallocation of the received file is performed in step 54, and then, in step 35, the sending side is notified of the completion of the receiving processing.

Next, before explaining the operation of file transmission/reception control related to partitioned files, the structure of partitioned files will be explained using FIG. 6. The partitioned file is composed of two parts: a directory part 56 and a member part 57. Part 17 contains member management information 581 regarding each member stored in the file, while part 178 contains the substance of each member.

The member management information 58 includes the member name 59 and a relative block address TTR 161 (relative block address from the beginning of the file) indicating the beginning position where the actual member is stored. In this case, the member entity is divided into loading units into the main storage device as shown in (1), (2), and (3) in Figure 6, and the member entity is divided into loading units into the main storage device. The note list 62 at the end of is the relative block address TTR363,'1' pointing to the position of the division point.
The position t-m of the t-strike, such as TR, 64, is stored. When member X65 of a partitioned file with such a structure is transferred to a partitioned file in which member A66 already exists, the original TTRI in the transmitted file generally changes because the relative position from the beginning of the file changes.
~TTR, etc. will all need to be changed.

During this time, when transferring the entire one partitioned file or its individual members for mt-solving, a data transfer method as shown in FIG. 7 is used. It has already been explained that the transmission management table 67 containing characteristic information of the transmitted file and the received file is transferred prior to transmitting and receiving files. In the case of a partitioned file, a method is used in which transfer of one member is repeated for the required number of members, and when each member is transferred, the sending side sends relative block address information prior to the actual data transfer. Data 68 summarizing the member management information and note list information is transmitted, and the receiving side stores this in data 69.

Sending! In @, when the actual data block 70 is transmitted thereafter, the data block is added to the relative block address TTR 71 representing the friend position where the data block exists and is transmitted.

When the receiving side receives this, it compares the added TTR with the TTR group in the member management information and note list data 69 that has already been received and saved.
If there is a match, the received data block is replaced in the received file with TTR+' 72 at the beginning of writing. In this way, when all data has been received and stored in the received file, a note list of revision records is written out and member management information is registered in the new position information.

The structure of a partitioned file and its data transfer method have been explained above.Next, we will explain transfer from partitioned file to partitioned file1, transfer from member of partitioned file to member of partitioned file, and the order The operation of transferring from an organized file to a member of a partitioned file is explained in the 8th section.
This will be explained using figures. File transmission processing in the former two cases is controlled by the segmented organization-partitioned organization/partitioned organization member segmented organization member file transmission control mechanism 1B, and file transmission processing in the latter case is sequential organization-partitioned organization. On the other hand, on the receiving side, the file reception control mechanism 22 for partitioned organization Menno (/partitioned organization) also controls reception processing in the case of i deviation.

First, we will explain the processing on the sending side when transferring from a partitioned file to a partitioned file and from a partitioned file to a member of a partitioned file.First, the partitioned file sent in step 73 will be explained. After reading the directory part of the file, the members to be transferred are determined in step 74. When transferring the class M gold body, &C is to transfer 1111K of member names included in the directory part, but in the partitioned file. When transferring a member, only that member is to be transferred.When the member to be transferred is determined, the member management information of the member is obtained from the already read directory section in step 75, and further, in step 76, the member management information of the member is transferred. If there is a note list, it is loaded, and in step 77, the member management information and note list are stored together in the transfer buffer and sent to the receiving side.Then, in step 78, the member is positioned at the beginning of the line t. After the transfer, the actual data transmission begins.That is, the next block is read from the file in step 79, and if it is not the end of the member data as checked in step 80, then the next block is read from the file.
In step 81, the relative block address TTRt representing the position where the block existed is appended to the front of the block data just read and stored (plotted) in the transfer buffer, and when the transfer buffer is full, Receive the transfer buffer in steps 8 and 3 111
Send to. Repeat the above data transmission process,
When the end of the data of the member is reached, in step 84, the transfer buffer is displayed to indicate that it is the last data of the member, and the transfer buffer is sent to the receiving side. When the transfer of one member is completed in this way, if there are any more members to be sent in the case where the entire partitioned file is to be sent, the sending process is repeated for the next member. When the transmission for all members is completed, in step 86, file transmission termination processing such as closing the transmission file and canceling the allocation is performed.

Next, convert the sequential file to the partitioned file member /(K
When transferring, create dummy (virtual) member management information in step 87 and send it to the receiving side, and then in step 79
By merging with , the process is forced to be handled in the same way as the process for transferring members of a partitioned file as described above. However, when the block data is stored in the transfer buffer in step 81, it is also stored with a dummy relative block address (TTR) attached to the front.

Above we have explained the processing on the sending side when transferring from a partitioned file to a partitioned file, from a member of a partitioned file to a member of a partitioned file, and from a sequential file to a member of a partitioned file. Processing on the receiving side will be explained using the same Figure 8.

First, in step 88, data including member management information and note list information is received and stored in the main storage device as shown at 69 in FIG.

Next, when the transfer buffer is received in step 89, in step 90, each block is cut out from the transfer buffer (DEPTH 4KING), and in step 91, the block is written to the received file, and a relative value representing the writing position of the block is written. Get the block address (TTR). In step 92, a T is added to the beginning of the nine blocks currently cut out, indicating the original location of the block.
Check whether the same value as TR is included in the TTR group in the member management information and note list information after saving it in the main memory, and if it is included, save that TTR to the received file. Replace with the TTR at the time of writing. The above process is repeated until the transfer buffer reaches its end, and further the process starting from receiving the transfer buffer in step 89 is repeated until the member's received data ends. When the end of the member's received data is reached, it is checked in step 96 whether the member includes a note list, and if so, the note list containing the already replaced TTR information is output to the received file; In step 97, the member is registered in the directory based on the member management information including the replaced TTR information. Step 98
Check to see if reception has finished for all members, and if it has not finished yet, perform reception processing for the next member. When all the files have been received, in step 99 file reception termination processing such as closing processing and deallocation of the received files is performed, and the sending side is notified of the completion of the reception processing.

According to the present invention, in a computing institution that has a network of 1klll, (1) files can be transferred in various types of files such as sequential files, partitioned files, and direct files, and can be transferred in different types of files in any possible combination; (3) In addition, the receiving side does not need to know about the received file in advance; therefore, the sending side can transfer arbitrary files regardless of whether the received file is an existing file or a 'IIr standard file. (4) Further, upon request from one computer, files existing on another computer can be received.

From the above, it is possible to freely transfer files between the computing institutions forming the network tm, and there is an effect that mutually effective utilization of the computing institutions can be achieved.

[Brief explanation of drawings]

51g1 is a diagram showing an example of the configuration of a computer network, FIG. 2 is a diagram showing the basic system of the present invention, FIG. 3 is a diagram showing an embodiment of the present invention, N4 is a flowchart of file transmission/reception preparation control processing, Figure 5 is a flowchart of the transfer process to a sequential file, Figure 6 is a diagram showing the structure of a partitioned file, Figure 7 is a diagram showing the transfer method of a partitioned file, and Figure 8 is a diagram showing the partitioned file transfer method. 9 is a flowchart of the transfer process to the member, and FIG. 9 is a diagram showing the details of the transmission management table. Prevention) I21 Y 3 Figure 4 Mouth ￥; 5 Figure 8 Row 1571

Claims (1)

[Claims] In a computer network system in which multiple computers are connected to each other through communication lines or direct channel connections, when files are transferred between these computing institutions, the details of the sent and received files must be sent and received before the actual data transmission/reception. exchange characteristic information,
A file transfer protocol method characterized in that both the sending and receiving sides perform transmission and reception processing according to their characteristic information.