JP2005316690A - P2p file transfer method, system, user terminal, relay terminal and program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To perform direct file transfer without making a user aware of network environment even under environment wherein both terminals performing file transmission/reception can perform only one-way communication. <P>SOLUTION: A file acquisition part 112 of a user terminal 1B transmits file arrangement requirement to a relay terminal 2 by use of a P2P communication part 114. A P2P communication part 214 of the relay terminal 2 transfers the file arrangement requirement to a user terminal 1A. A P2P communication part 114 of the user terminal 1A receives the file arrangement requirement, and delivers it to the file acquisition part 112. The file acquisition part 112 acquires a designated file 11111 from a file DB 1111 inside a file management part 111, and transfers it to the relay terminal 2 from a file transfer part 115. A file transfer part 215 of the relay terminal 2 receives the file 11111, and registers it into a file DB 2111 inside a file management part 211. <P>COPYRIGHT: (C)2006,JPO&NCIPI

Description

  The present invention relates to a P2P file transfer method for directly transferring files between user terminals.

  The firewall support method in Gnutella (www.gnutella.com/), which is a typical P2P file sharing, is a method of pushing (transmitting) from the file holding side, and only supports one firewall (non-patent) Reference 1). The side to which the file is pushed (obtained) needs to change to a network environment that allows communication from the outside to the inside of the network, which is a problem in terms of security. Further, it is a function unique to Gnutella and is not a function that can be used universally by other P2P application developers / users.

Sending and receiving files between terminals located in different firewall environments is realized by an application using the current client / server model (Cybozu: http://cybozu.co.jp/). When access is permitted from the beginning, the original file is regularly stored in the server that is the file management apparatus, and security management must be strictly performed.
http: // www. atmarkit. co. jp / fwin2k / experiments / gnutella_for_admin / gnutella_for_admin_5. html "Broker Model and SIONet" published by Telecommunications Association JXTA (http://www.jxta.org/)

  In SIONet (Non-patent Document 2) which is a P2P platform, a connection method in different firewall environments has been proposed, but only a connection establishment for transmitting and receiving messages on a P2P network is performed, and a file transfer function is provided. Absent. In Non-Patent Document 3, files can be transferred between different firewalls by using a pipe. However, when transferring a large file, the file is divided and assembled in a host application because it is divided and transferred. Need to be implemented. In addition, it is necessary for the host application side to deal with the case where the loss of the divided message occurs, and it is difficult to complete the transfer of the file itself guaranteed only by JXTA.

  The object of the present invention is to make the user aware of the network environment such as whether or not bi-directional communication is possible even in an environment where both terminals performing file transmission / reception can only perform one-way communication such as a firewall and NAT (Network Address Translator). The object is to provide a P2P file transfer method, system, user terminal, relay terminal, and program that enable direct file transfer.

The P2P file transfer method of the present invention
DMZ as a means of communication in situations where two or more user terminals connected on a P2P network share files and transmit and receive arbitrary information and tasks by autonomous distributed cooperation, and bidirectional communication is impossible due to network environment restrictions A P2P file transfer method for performing communication using an RP (Random Buopia) located in (DeMilliliterized Area),
A stage in which the user terminal sends and receives predetermined file or folder information;
A stage in which the user terminal sends a predetermined file to the RP;
In the RP, ensuring the uniqueness of the file or folder information received from the terminal (that the file name or folder name can be communicated without being modified) and receiving between the corresponding user terminals;
Have

The P2P file transfer system of the present invention
A file management means for managing the file, including a file DB for managing the file;
File acquisition means for accessing the file management means and acquiring files;
A folder acquisition means for accessing a file management means and acquiring an arbitrary folder;
P2P communication means having a function of transferring by Hop-by-Hop between user terminals;
A user terminal having a P2P file transfer device including a file transfer means for transferring a file;
A file management means installed in an area accessible from other hosts outside the firewall, including a file DB for managing files, and managing the files;
P2P communication means having a function of transferring by Hop-by-Hop between user terminals;
A relay terminal having a P2P file transfer apparatus including a file transfer means for transferring a file.

  In the present invention, as shown in FIG. 16, when there is no communication with another segment via FW / NAT or the like, communication between user terminals is performed directly without passing through the RP, and the base is established via FW / NAT or the like. If there is communication between the two, communication via RP is performed.

  Since a relay device (RP) is installed in the DMZ and can be disclosed to the outside, a person at another base can place a file on the RP or obtain a file. Therefore, the RP is located outside the user terminal.

  The P2P file transfer apparatus has the software structure shown in FIG. 17 and provides a file transfer API for each file and folder without making the upper application aware of the environment such as FW / NAT.

  The present invention realizes transmission / reception of files between terminals located in different firewalls and NAT environments without impairing the introduction / operation cost of the centralized management apparatus, which is the advantage of P2P, and the reduction of the line bandwidth.

  The security problem in Gnutella is that only RP (Rendezvous Peer) that can be accessed from a file sending / receiving terminal allows access from inside to outside (Web reference etc.) that is permitted in a general Internet environment. There are no new security considerations to enable file transfer. It also supports two firewall environments.

  A file to be transferred is only temporarily stored in the RP, and a network configuration that does not require strict security management like a server is possible.

  In the present invention, even in an environment where both terminals performing file transmission / reception can only perform one-way communication such as a firewall and NAT, a network environment such as whether or not two-way communication is possible can be provided to the user by using the RP arranged in the DMZ. There is an effect that direct file transfer can be performed without being conscious.

  Next, embodiments of the present invention will be described with reference to the drawings.

  FIG. 1 is a system configuration diagram of an embodiment of the present invention.

  This system includes user terminals 1A and 1B and a relay terminal 2. The user terminal 1A includes a P2P file transfer device 11 and an application 12. The P2P file transfer apparatus 11 includes a file DB 1111 that manages files, accesses the file management unit 111 that manages files, the file management unit 111, and accesses the file acquisition unit 112 that acquires files and the file management unit 111. A folder acquisition unit 113 that acquires an arbitrary folder, a P2P communication unit 114 that transfers Hop-by-Hop to another terminal, and a file transfer unit 115 that transfers a file to the other terminal. . The user terminal 1B has the same configuration as the user terminal 1A. The relay terminal 2 is a rendezvous peer (RP) including a P2P file transfer device 21. The P2P file transfer device 21 transfers a file to and from the file management unit 211 including the file DB 2111 for managing the file, and the P2P communication unit 214 for transferring by Hop-by-Hop between the user terminals 1A and 1B. A file transfer unit 215 is included.

  Next, the file transfer operation of pull type and push type file units and folder units (all files under a folder) in this embodiment will be described.

1) Pull-type file transfer operation (FIGS. 2 to 6)
When the user terminal 1B acquires a file in the user terminal 1A, the file in the user terminal 1A is designated from the application 12 of the user terminal 1B to the file acquisition unit 112, and a Deliver Pull File (file is delivered by delivery). Request). Upon receiving the request, the file acquisition unit 112 stores information acquired by any method (a method of receiving a fixed method, adopting appropriate communication by changing communication environment step by step, It is determined whether the relay terminal 2 is used or not used in the subsequent communication or the like. That is, the user terminal 1A does not know whether the user terminal 1B is in the same network or a network that spans bases. Therefore, the user terminal 1A performs optimal processing for communicating with the user terminal 1B by performing processing (processing for confirming communication) to determine whether the user terminal 1A is in the same network or across networks. The appropriate method will be selected and appropriate communication will be performed.

  A case where file transfer is performed without going through the relay terminal 2 (FIG. 2) will be described. The file acquisition unit 112 of the user terminal 1B transmits a file acquisition request to the file transfer unit 115 of the user terminal 1A. The file transfer unit 115 accesses the file management unit 111, acquires the specified file 11111 from the file DB 1111, and transfers the file 11111 together with the file acquisition response from the file transfer unit 115 to the user terminal 1B. The file acquisition unit 112 of the user terminal 1B acquires the file 11111 and stores it in the file DB 1111.

  The case where file transfer is performed via the relay terminal 2 (FIGS. 3 to 5) will be described. The file acquisition unit 112 of the user terminal 1B transmits a file arrangement request to the relay terminal 2 using the P2P communication unit 114. The P2P communication unit 214 of the relay terminal 2 transfers the file arrangement request to the user terminal 1A. The P2P communication unit 114 of the user terminal 1A receives the file placement request and passes it to the file transfer unit 115. The file transfer unit 115 acquires the designated file 11111 from the file DB 1111 in the file management unit 111 and transfers the file 11111 from the file transfer unit 115 to the relay terminal 2. The file transfer unit 215 of the relay terminal 2 receives the file 11111 and registers it in the file DB 2111 in the file management unit 211.

  The user terminal 1 </ b> A that has transferred the file to the relay terminal 2 then transmits a file placement completion notification to the relay terminal 2. The P2P communication unit 214 of the relay terminal 2 receives this notification and notifies the user terminal 1B that the upload of the designated file has been completed. The P2P communication unit 114 of the user terminal 1B sends this notification to the file acquisition unit 112. The file acquisition unit 112 transmits a file acquisition request to the relay terminal 2. Upon receiving this request, the file transfer unit 215 of the relay terminal 2 acquires the file 11111 from the file DB 2111 in the file management unit 211, and transmits it to the user terminal 1B together with a file acquisition response. The file acquisition unit 112 of the user terminal 1B acquires the file 11111 and stores it in the file DB 1111 in the file management unit 111.

  Next, the file acquisition unit 112 of the user terminal 1 </ b> B transmits a file deletion request to the relay terminal 2. The P2P communication unit 214 of the relay terminal 2 transfers the file deletion request to the user terminal 1A. When the P2P communication unit 114 of the user terminal 1A receives the file deletion request, the file transfer unit 115 requests the relay terminal 2 to delete the file. In response to this request, the file transfer unit 215 of the relay terminal 2 deletes the file 11111 in the file DB 2111 of the file management unit 211.

  FIG. 6 shows a state in which pull-type file transfer is completed.

2) Push-type file transfer operation (FIGS. 7 to 9)
Similar to the pull-type file acquisition operation, the file in the file DB 1111 in the user terminal 1A is copied to the user terminal 1B, and this is performed by the operation on the user terminal 1A side.

  A case where file transfer is performed without going through the relay terminal 2 (FIG. 7) will be described. The application 12 of the user terminal 1A requests a Deliver Push File (sends the file by delivery) to the file acquisition unit 112, and the file acquisition unit 112 transmits the Delivery Pull File to the user terminal 1B using the P2P communication unit 114. To do. The P2P communication unit 114 of the user terminal 1B receives this, and the file acquisition unit 112 performs a Deliver Pull File of the specified file.

  Next, a case where file transfer is performed via the relay terminal 2 (FIG. 8) will be described. The application 12 of the user terminal 1 </ b> A requests a driver push file from the file acquisition unit 112. The file acquisition unit 112 uses the P2P communication unit 114 to request the relay pull file from the relay terminal 2. The P2P communication unit 214 of the relay terminal 2 transfers this request to the user terminal 1B. The P2P communication unit 114 of the user terminal 1B receives this request, and the file acquisition unit 112 performs a Deliver Pull File for the specified file.

  When not passing through the relay terminal 2, the P2P communication unit 114 performs direct communication. When passing through the relay terminal 2, the communication is performed via the P2P communication unit 214 in the relay terminal 2 as shown in FIG. However, since this difference is absorbed in the P2P communication unit 114, there is no need to be particularly conscious in the upper application.

  FIG. 9 shows a push-type file transfer result.

3) Pull-type folder unit file transfer (FIGS. 10 to 12)
Similarly to 1), the file in the file DB 1111 in the user terminal 1A is copied to the user terminal 1B. At this time, a folder is designated, and all files in the folder are copied.

  In the case of pull-type folder-based file transfer, it is necessary to acquire the file image in the folder. At this time, the P2P transfer unit 114 is used to make the inquiry.

  First, a case where pull-type folder unit file transfer is performed without using the relay terminal 2 (FIG. 10) will be described. The application 12 of the user terminal 1B requests the folder acquisition unit 113 to acquire a file for each folder, and the folder acquisition unit 113 transmits a folder information request from the P2P communication unit 114 to the user terminal 1A. The P2P communication unit 114 of the user terminal 1A receives the folder information request, creates a file list from the information in the file DB 1111 in the file management unit 111, and transmits the folder information to the user terminal 1B. The P2P communication unit 114 of the user terminal 1B receives this, and the file acquisition unit 112 performs a Deliver Pull File for each file based on the folder information.

  Next, a case where pull-type folder unit file transfer is performed via the relay terminal 2 (FIG. 11) will be described. The application 12 of the user terminal 1B requests the folder acquisition unit 113 to acquire a file for each folder. The P2P communication unit 114 transmits a folder information acquisition request to the relay terminal 2. The P2P communication unit 214 of the relay terminal 2 transfers this to the user terminal 1A. The P2P transmission unit 114 of the user terminal 1A creates a file list from the information in the file DB 1111 in the file management unit 111, and transmits folder information to the relay terminal 2. The P2P communication unit 214 of the relay terminal 2 transfers the received folder information to the user terminal 1B. The P2P communication unit 114 of the user terminal 1B receives this, and the file acquisition unit 112 performs a Deliver Pull File for each file based on the folder information.

  The user terminal 1B received via the P2P transfer unit 114 performs file transfer repeatedly based on the file information in the received folder using the pull-type file transfer procedure described in 1).

  FIG. 12 shows a pull type folder unit file transfer result.

  When the communication is performed without going through the relay terminal 2, direct communication is performed as shown in FIG. 10. When the communication is made through the relay terminal 2, as shown in FIG. Although transfer is performed using the file transfer unit 215, this difference is absorbed in the P2P communication unit 114 as in the case of 2).

4) Push-type folder-based file transfer (FIGS. 13 to 15)
Similarly to 1), the file in the file DB 1111 in the user terminal 1A is copied to the user terminal 1B. At this time, a folder is designated, and all files in the folder are copied. This operation is performed from the user terminal 1A that holds the file.

  In the case of push-type file transfer in folder units, a file image in the folder is required. Therefore, when a file acquisition request is made to the receiving side (user terminal 1B), the file management unit 111 is inquired, file information in the folder is acquired, and the request is made using the P2P transfer unit 114.

  First, a case where push type folder unit file transfer is performed without using the relay terminal 2 (FIG. 13) will be described. The application 12 of the user terminal 1A requests a driver push folder (sends a folder by delivery) to the file acquisition unit 112. The file acquisition unit 112 acquires file information in the folder from the file DB 1111 of the file management unit 111. The P2P communication unit 114 requests the user terminal 1B for a driver pull folder (acquires a folder by delivery). The P2P communication unit 114 of the user terminal 1B receives this request, and the file acquisition unit 112 performs a Deliver Pull File for the specified file.

  Next, a case where push-type folder unit file transfer is performed via the relay terminal 2 (FIG. 14) will be described. The application 12 of the user terminal 1 </ b> A requests a driver push folder from the file acquisition unit 112. The file acquisition unit 112 acquires file information in the folder from the file DB 1111 in the file management unit 111. The P2P communication unit 114 requests the relay terminal 2 for a driver pull folder. The P2P communication unit 214 of the relay terminal 2 transfers this request to the user terminal 1B. The P2P communication unit 114 of the user terminal 1B receives this request, and the file acquisition unit 112 performs a Deliver Pull File for the specified file.

  When the communication is performed without going through the relay terminal 2, direct communication is performed as shown in FIG. 13. When the communication is made through the relay terminal 2, as shown in FIG. The file is transferred using the file transfer unit 215. As in the case of 3), since this difference is absorbed in the P2P communication unit 114, there is no need to be particularly conscious in the upper application.

  The user terminal 1B received via the P2P transfer unit 114 performs file transfer repeatedly based on the file information in the received folder using the pull-type file transfer procedure described in 1).

  Through the procedure described above, the push-type folder unit file transfer is completed as shown in FIG.

  In addition to the user terminal and the relay terminal realized by dedicated hardware, a program for realizing the function is recorded on a computer-readable recording medium, and the program recorded on the recording medium is recorded. May be read by a computer system and executed. The computer-readable recording medium refers to a recording medium such as a floppy disk, a magneto-optical disk, a CD-ROM, or a storage device such as a hard disk device built in the computer system. Furthermore, a computer-readable recording medium is a server that dynamically holds a program (transmission medium or transmission wave) for a short period of time, as in the case of transmitting a program via the Internet, and a server in that case. Some of them hold programs for a certain period of time, such as volatile memory inside computer systems.

It is a block diagram of the P2P file transfer system of one Embodiment of this invention. It is a figure which shows a series of processing of pull type file transfer (RP non-passing). It is a figure which shows a series of processes of pull type file transfer (via RP). It is a figure which shows a series of processes of pull type file transfer (via RP). It is a figure which shows a series of processes of pull type file transfer (via RP). It is a figure which shows the result of a pull type file transfer. It is a figure which shows a series of processes of push type file transfer (A file is acquired by delivery without RP). It is a figure which shows a series of processes of push type file transfer (A file is acquired by delivery without RP). It is a figure which shows the result of a push type file transfer. It is a figure which shows a series of processes of pull type folder unit file transfer (folder information collection without RP). It is a figure which shows a series of processes of pull type folder unit file transfer (folder information collection without RP). It is a figure which shows the result of a pull type folder unit file transfer. It is a figure which shows a series of processes of push type folder unit file transfer (collecting a folder by delivery without RP). It is a figure which shows a series of processes of push type folder unit file transfer (collecting a folder by delivery without RP). It is a figure which shows a push type folder unit file transfer result. It is a figure which shows the environment which this invention presupposes. It is a figure which shows a software architecture.

Explanation of symbols

1A, 1B User terminal 2 Relay terminal 11 P2P file transfer device 12 Application 21 P2P file transfer device 111 File management unit 112 File acquisition unit 113 Folder acquisition unit 114 P2P communication unit 115 File transfer unit 211 File management unit 214 P2P communication unit 215 File transfer unit 1111 File DB
2111 File DB

Claims (9)

DMZ as a means of communication in situations where arbitrary information and tasks are transmitted and received by autonomous distributed cooperation, files are shared among a plurality of user terminals connected on a P2P network, and bidirectional communication is not possible due to network environment restrictions A P2P file transfer method for performing communication using an RP located in
The user terminal transmitting and receiving predetermined file or folder information; and
The user terminal transmitting a predetermined file to the RP;
In the RP, ensuring the uniqueness of the file or folder information received from the user terminal and receiving it between the corresponding terminals;
A P2P file transfer method.   The P2P file transfer method according to claim 1, wherein pull-type file transfer for acquiring information between the user terminals or push-type file transfer for providing information is performed.   The P2P file transfer method according to claim 1 or 2, wherein when information is transmitted / received between the user terminals, file transfer is performed by specifying a file unit or a folder unit.   The user terminal automatically selects direct file transfer when direct communication is possible, and file transfer using the RP when the RP needs to be used. The P2P file transfer method described. A file management means for managing the file, including a file DB for managing the file;
File acquisition means for accessing the file management means and acquiring files;
A folder acquisition unit that accesses the file management unit and acquires an arbitrary folder;
P2P communication means having a function of transferring between terminals by Hop-by-Hop;
A user terminal having a P2P file transfer device including a file transfer means for transferring a file;
A file management means installed in an area accessible from other hosts outside the firewall, including a file DB for managing files, and managing the files;
P2P communication means having a function of transferring by Hop-by-Hop between user terminals;
A P2P file transfer system having a relay terminal having a P2P file transfer device including file transfer means for transferring a file.   6. The P2P file transfer system according to claim 5, wherein both the P2P file transfer apparatuses are located between a host application and an OS. In the user terminal connected on the P2P network,
A file management means for managing the file, including a file DB for managing the file;
File acquisition means for accessing the file management means and acquiring files;
A folder acquisition unit that accesses the file management unit and acquires an arbitrary folder;
P2P communication means having a function of transferring between terminals by Hop-by-Hop;
A user terminal comprising: a P2P file transfer device including a file transfer means for transferring a file. In the relay terminal connected on the P2P network system,
A file management means installed in an area accessible from other hosts outside the firewall, including a file DB for managing files, and managing the files;
P2P communication means having a function of transferring between terminals by Hop-by-Hop;
A relay terminal comprising: a P2P file transfer device including a file transfer means for transferring a file.   The computer program for performing the function of the terminal of Claim 7 or Claim 8 with a computer.

Images