JP2007102619A - Peer-to-peer file exchange system and peer-to-peer file exchange server - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To restrict file exchange by a predetermined mobile node in peer-to-peer file exchange between mobile nodes of a mobile IP network. <P>SOLUTION: In the central server-type peer-to-peer file exchange system including a plurality of mobile nodes and a server for disclosing a file list of files provided by the mobile nodes, each mobile node transmits a mobile IP packet containing a unique home address of the mobile node concerned to the server. The server stores home address information for a mobile node to which providing of files is restricted, and restricts processing for file exchange between mobile nodes when a home address transmitted from each mobile node is stored as the home address of the mobile node to which providing of files is restricted. <P>COPYRIGHT: (C)2007,JPO&INPIT

Description

  The present invention relates to a peer-to-peer file exchange system and a peer-to-peer file exchange server, and more particularly to a peer-to-peer file exchange system and a peer-to-peer file exchange server that prevent illegal file exchange.

  In recent years, a peer-to-peer file exchange system that directly exchanges files between an unspecified number of individuals using the Internet has attracted attention. In such a peer-to-peer file exchange system, a large number of computers (hereinafter referred to as PCs) can be connected to each other to share files such as music over the Internet. Such a peer-to-peer file exchange system is divided into a central server type and a pure type shown below.

  The central server type is a system in which a central server and a plurality of user PCs (here, user PC1 and user PC2) exchange files in a sequence as shown in FIG. In FIG. 12, user PC1 and user PC2 are connected to the central server (S501, S503), and a list of files stored in each user PC is transmitted to the central server and released (S502, S504). . In this way, the user PC 1 and the user PC 2 share file list information between users through the central server. When a certain user PCPC1 searches the file list information for a file held by another user PC2 (S505) and requests a download to the central server (S506), the central server notifies the user PC2 of the download request (S507). .

  After this notification, the user PC1 and the user PC2 are directly connected, and the user PC1 can download the file possessed by the user PC2 (S508). As described above, in the central server type system, the central server only provides the file search database (file list information) and the user connection management, and the data itself is exchanged by the direct connection between the users. .

  On the other hand, there is no central server for managing information, and all information is distributed between a plurality of users PC1, PC2, PC3,... In a bucket-relay type, and the sequence is shown in FIG. . In FIG. 13, the user PC1 that is a client requesting a predetermined file connects to the user PC2 that has become the server (S601), and inquires about the existence of the file (S602). If the user PC 2 does not have the target file, the user PC 1 connects to the user PC 3 to be the next server (S607). If the user PC 3 does not have the target file, the user PC 3 connects to the next user PC.

  When the user PC 2 has a file (S603), and the user PC 2 that owns the file notifies the user PC 1 of the result (S604), the user PC 1 as a client directly requests a download from the user PC 2 of the server (S605). The file is directly downloaded (S606).

  In these peer-to-peer file exchange systems, various problems such as copyright protection problems and illegal data distribution have recently emerged. Therefore, it is necessary to prevent file provision by malicious users.

  In response to such a problem, for example, in a central server type system, the central server manages the user PC based on the address of the user PC. By prohibiting it, illegal acts are prevented from being repeated.

On the other hand, in a pure type system, since there is no central server, it is not possible to prevent illegal activities by a method like the central server type. Therefore, in Patent Document 1, a server for managing the access right is provided separately, and the server receives an inquiry about the access right from the user PC, and determines the access right based on information unique to the user PC such as an address. Then, by returning the determination result to the user PC, proper file exchange is performed.
JP 2003-122635 A

  However, according to the conventional peer-to-peer file exchange technology, an appropriate file exchange can be performed by the management of the user PC based on the IP address. However, in the conventional technology, the IP address to which the IP address is fixedly assigned in the first place. Since the technology is based on the network, when the IP address of the user PC changes every time the network moves like a mobile IP network, the user PC can no longer be managed based on the IP address.

  In other words, in the mobile IP, when the user PC moves to another area, the address (care-of address) of the user PC changes, so even if the user moves illegally, the file can be transmitted again, and the malicious user can There was a problem that file exchange could not be restricted.

  The present invention has been made in view of the above, and in a P2P file exchange system using mobile IP technology, a peer-to-peer file that can completely prevent a user who has performed an illegal action from transmitting a file again The object is to obtain an exchange system and a peer-to-peer file exchange server.

  In order to solve the above problems, a peer-to-peer file exchange system according to the present invention includes a plurality of mobile nodes and a server for publishing a file list of files provided by the mobile nodes, and files between mobile nodes by peer-to-peer communication. In the central server type peer-to-peer file exchange system for performing exchange, the mobile node includes address information transmission means for transmitting a mobile IP packet including a home address unique to the mobile node to the server at the time of the file exchange. The server includes a restriction information storage unit that stores information on a home address for a mobile node that restricts file provision, and a home address transmitted from the mobile node restricts file provision to the restriction information storage unit. Mo When stored as a home address Irunodo are those having a file exchange limiting means for limiting the processing on the file exchange of the mobile node, the.

  The peer-to-peer file exchange server of the present invention is a central server type peer-to-peer file that publishes a file list of files provided by a mobile node when a plurality of mobile nodes perform file exchange between the mobile nodes through peer-to-peer communication. In the exchange server, at the time of the file exchange, address information receiving means for receiving a mobile IP packet including a home address unique to the mobile node from the mobile node, and information on the home address for the mobile node that restricts file provision And when the home address transmitted from the mobile node is stored in the restriction information storage unit as the home address of the mobile node that restricts the provision of the file, the mobile node And file exchange limiting means for limiting the processing related to file exchange, those having a.

  According to the present invention, when a mobile IP packet including a home address unique to a mobile node is received during file exchange and it is determined that the home address belongs to a mobile node that restricts file provision, Since processing related to file exchange of the mobile node is restricted, file exchange by a predetermined mobile node can be restricted even when peer-to-peer file exchange is performed between mobile nodes of the mobile IP network.

  A peer-to-peer file exchange system according to a first aspect of the present invention includes a plurality of mobile nodes and a server for publishing a file list of files provided by the mobile nodes, and performs file exchange between mobile nodes by peer-to-peer communication. In the central server type peer-to-peer file exchange system, the mobile node includes address information transmission means for transmitting a mobile IP packet including a home address unique to the mobile node to the server at the time of the file exchange. Is a restriction information storage means for storing information on a home address for a mobile node that restricts the provision of files, and a mobile node that restricts the provision of files to the restriction information storage means by the home address transmitted from the mobile node. of When stored as over beam addresses are those having a file exchange limiting means for limiting the processing on the file exchange of the mobile node, the.

  With this configuration, when a mobile IP packet including a home address unique to a mobile node is received during file exchange and it is determined that the home address belongs to a mobile node that restricts file provision, the mobile node Therefore, even when a peer-to-peer file exchange is performed between mobile nodes of a mobile IP network, there is an effect that the file exchange by a predetermined mobile node is restricted.

  The peer-to-peer file exchange system according to a second aspect of the present invention is the peer-to-peer file exchange system according to the first aspect, wherein the mobile node further comprises file list transmission means for transmitting a file list of files provided by the mobile node to the server. Mobile node information storage means for storing a home address included in the mobile IP packet transmitted from the mobile node on the file providing side in association with a care-of address, and the file list received from the mobile node on the file providing side File list storage means for storing the file in association with the care-of address of the transmission source, wherein the file exchange restriction means is a file included in the file list stored in the file list storage means from the mobile node on the file request side. If you accept a request for The care-of address corresponding to the file list including the file related to the request is acquired from the file list storage means, the home address corresponding to the acquired care-of address is acquired from the mobile node information storage means, and the acquired home address is provided by the file The file is provided only to the mobile node that determines that the file can be provided by determining whether or not the file can be provided by the mobile node of the providing source based on whether or not the restriction information is stored in the restriction information storage unit. Is possible.

  With this configuration, even when a request for providing a file in a file list associated with a fluctuating address (care-of address) is received, the fluctuating address is converted into a unique address (home address) for the mobile node. Since it is determined whether or not a file can be provided, even when a peer-to-peer file exchange is performed between mobile nodes of a mobile IP network, there is an operational effect that file provision by a predetermined mobile node can be restricted.

  A peer-to-peer file exchange server according to a third aspect of the present invention is a central server type that publishes a file list of files provided by a mobile node when a plurality of mobile nodes perform file exchange between the mobile nodes through peer-to-peer communication. In the peer-to-peer file exchange server, in the file exchange, address information receiving means for receiving a mobile IP packet including a home address unique to the mobile node from the mobile node, and a home for the mobile node that restricts file provision Restriction information storage means for storing information related to the address, and when the home address transmitted from the mobile node is stored in the restriction information storage means as the home address of the mobile node for restricting file provision, And file exchange limiting means for limiting the processing related to exchange files over de, those having a.

  With this configuration, when a mobile IP packet including a home address unique to a mobile node is received during file exchange and it is determined that the home address belongs to a mobile node that restricts file provision, the mobile node Therefore, even when a peer-to-peer file exchange is performed between mobile nodes of a mobile IP network, there is an effect that the file exchange by a predetermined mobile node is restricted.

  According to a fourth aspect of the present invention, the peer-to-peer file exchange server according to the third aspect of the present invention is the file list transmission means for receiving the file list of the file provided by the mobile node from the mobile node on the file providing side, and the file providing side Mobile node information storage means for storing the home address included in the mobile IP packet transmitted from the mobile node in association with a care-of address, and the source list of the file list received from the mobile node on the file providing side. A file list storage means for storing the file list in association with an address, wherein the file exchange restriction means sends a request to provide a file included in the file list stored in the file list storage means from the mobile node on the file request side. If accepted, the request A care-of address corresponding to a file list including a file is acquired from the file list storage unit, a home address corresponding to the acquired care-of address is acquired from the mobile node information storage unit, and the acquired home address restricts file provision It is possible to provide the file only to the mobile node that has determined that the file can be provided by determining whether or not the file of the providing source mobile node can be provided depending on whether or not the restriction information storage unit stores the file. To do.

  With this configuration, even when a request for providing a file in a file list associated with a fluctuating address (care-of address) is received, the fluctuating address is converted into a unique address (home address) for the mobile node and the file is converted. Therefore, even when a peer-to-peer file exchange is performed between mobile nodes of a mobile IP network, it is possible to limit file provision by a predetermined mobile node.

  A peer-to-peer file exchange system according to a fifth aspect of the present invention is a pure type peer-to-peer file exchange system comprising a plurality of mobile nodes and performing file exchange between mobile nodes by peer-to-peer communication. The mobile node includes address information transmitting means for transmitting a mobile IP packet including a home address unique to the mobile node to the server when the file is exchanged, and the server restricts file provision Restriction information storage means for storing information on the home address for the mobile node, and the home address transmitted from the mobile node are stored in the restriction information storage means as the home address of the mobile node that restricts the provision of files. When Are those having a file exchange limiting means for limiting the processing on the file exchange of the mobile node, the.

  With this configuration, when a mobile IP packet including a home address unique to a mobile node is received during file exchange and it is determined that the home address belongs to a mobile node that restricts file provision, the mobile node Therefore, even when a peer-to-peer file exchange is performed between mobile nodes of a mobile IP network, there is an effect that the file exchange by a predetermined mobile node is restricted.

  The peer-to-peer file exchange system according to a sixth aspect of the present invention is the peer-to-peer file exchange system according to the fifth aspect, wherein the mobile node causes the mobile node on the file request side to browse the file list of the file to be provided and the file included in the file list When the request for providing the file is received, the server further includes inquiry means for sending inquiry information asking whether or not to provide the file according to the request to the server, and the file exchange limiting means includes an inquiry from the mobile node on the file providing side. When the information is received, a home address corresponding to the care-of address of the inquiry information transmission source is acquired from the mobile node information storage means, and the acquired home address is stored in the restriction information storage means as a restriction on file provision. Depending on whether or not it is provided To determine whether to provide the file of the mobile node, provided the file is one that enables the provision of a file only mobile node it is determined that variable.

  With this configuration, the mobile node having a fluctuating address (care-of address) makes an inquiry to the server as to whether or not the file can be provided. Since it is converted to (home address) and it is determined whether or not a file can be provided, even when a peer-to-peer file exchange is performed between mobile nodes of a mobile IP network, it is possible to limit file provision by a predetermined mobile node Has an effect.

Hereinafter, embodiments of the present invention will be described with reference to the drawings.
(Embodiment 1)
The peer-to-peer file exchange system of the first embodiment is a so-called central server type peer-to-peer file exchange system in which a server provides a file search database and manages connection of terminal devices.

  FIG. 1 shows an overall configuration of a peer-to-peer file exchange system according to a first embodiment. In FIG. 1, a terminal device 10, a terminal device 20, and a plurality of other terminal devices are connected to a server device 30 (central server) via a network 40. In this peer-to-peer file exchange system, a plurality of terminal devices 10, 20... Log in to the server device 30 and send their own home address information and list information of files to be released to the server device 30 through Binding Update. After that, for example, the terminal device 10 searches for a file (of the terminal device 20) from the file list published to the server device 30, and after finding the file, transmits a download request for the file to the server device 30. When the server device 30 receives the download request from the terminal device 10, the server device 30 refers to the home address list of the terminal device to be restricted, and whether the list includes the home address of the terminal device 20 on the file providing side (the restriction is included). Check if it applies. If the restriction is satisfied (included in the list), the download request from the terminal device 10 is rejected. If the restriction is not met (not included in the list), a download request from the terminal device 10 is notified to the terminal device 20 on the providing side. The terminal device 20 receives the notification from the server device 30 and proceeds to the next step so that the corresponding file can be directly downloaded from the terminal device 10.

  Next, each device constituting the peer-to-peer file exchange system of the first embodiment will be described. First, the terminal device will be described with reference to FIG. FIG. 2 shows an internal configuration of the terminal apparatus according to the first embodiment. In FIG. 2, the terminal device 10 will be described as an example, but the other terminal devices 20... Have the same internal configuration.

  In FIG. 2, the terminal device 10 includes a database (abbreviated as DB) 11, a main function unit 15, and a network communication unit 19. The DB 11 includes download information 12, public file information 13, and home address information 14. The main function unit 15 includes an OS 18, a MIP MN function unit 17, and a P2P terminal application 16.

  The MIP MN function unit 17 transmits the association information between the home address and the care-of address of the terminal device 10 to the server device 30 as the home address information 14 of the terminal device 10 as a mobile IP packet including the home address. Further, the P2P terminal application 16 publishes the list information (file list) of the public file information 13 to the server device 30 and obtains permission from the server device 30 and then from other terminal devices 20. Download the corresponding file directly.

  The OS 18 provides a basic execution environment for realizing the functions of the MIP MN function unit 17 and the P2P terminal application 16, and the network communication unit 19 communicates with other terminal devices 20,. Transmission / reception to / from the network 40 is performed for communication.

  Next, the server device will be described with reference to FIG. FIG. 3 shows an internal configuration of the server device 30 according to the first embodiment. The server device 30 includes a DB 31, a main function unit 35, and a network communication unit 39. The DB 31 includes a terminal public file list 32, a terminal home address table 33, and a restricted home address list 34.

  The main function unit 35 includes an OS 38, a MIP HA function unit 37, and a P2P server application 36. The MIP HA function unit 37 receives the association information between the home address and the care-of address of the terminal device transmitted from the terminal device, and stores it as the terminal home address table 33 in the DB 31 that is a cache (Binding Cache).

  Further, the P2P server application 36 receives a connection request from the terminal device 10, 20,..., A login request, a file list release request, a file search request from the server file list, and a download request for the file found by the search. Perform the corresponding action.

  In particular, the P2P server application 36 refers to the restricted home address list 34 in response to a file download request from the terminal device 10, 20,..., And the home address of the terminal device 20 on the file providing side is restricted. Check whether it is applicable (is included in the list). If there is no problem (if it does not fall under the restriction), the download request is notified to the terminal device on the providing side, and the direct download between the terminal devices is successful. If there is a problem (if applicable), the download request from the terminal device is rejected.

  In addition, the OS 38 provides a basic execution environment for the MIP HA function unit 37 and the P2P server application 36 to realize functions, and the network communication unit 39 performs internal and external transmission / reception.

  Here, the configuration of the terminal home address table 33, the restricted home address list 34, and the terminal public file list 32 stored in the DB 31 of the server device 30 will be described. FIG. 4 shows an example of the terminal home address table 33 stored in the DB 31 of the server device. In this terminal home address table 33, association information between the home address (Home Address) and the care-of address (Care-of Address) of the terminal device transmitted by the MIP MN function unit 17 (see FIG. 2) of the terminal device is stored. It is remembered.

  The care-of address is an IP address assigned in the network to which the terminal device is currently physically connected. The home address is always a unique address as a fixed identifier of the terminal device, and is an address assigned in the network (home network) to which the terminal device was originally connected before moving to another network. Is the address assigned to. The terminal device associates this address (home address) with the address after the movement (care-of address) even after movement by the mechanism of the mobile IP.

  FIG. 5 shows an example of the restricted home address list 34 stored in the DB of the server device. In the restricted home address list 34, for example, when the terminal device X is to be restricted, the home address (Home Address_Tx) of the terminal device X is stored by the P2P server application 36. The storage in the restricted home address list 34 may be appropriately input from the outside by the user.

  The restricted home address list 34 may also store care-of addresses and restricted information as reference information. In the example shown in FIG. 5, a care-of address and restriction information are stored as reference information. The restriction information is information for restricting in more detail such as always prohibited or temporarily prohibited.

  FIG. 6 shows an example of the terminal public file list 32 stored in the DB of the server device. In the terminal public file list 32, the list information of the public file information (file name in FIG. 6) of the terminal device transmitted by the P2P terminal application 16 (see FIG. 2) of the terminal device and the notice of the terminal device of the transmission source. The association information with the address (Care-of Address) is stored. In FIG. 6, the file name, size, and format of the public file are shown as an example of the public file list information. When the P2P server application of the server device 30 receives the list information of the public file information from the terminal device, the received file list is associated with the care-of address of the transmission source and the terminal public file list 32 as shown in FIG. Remember as.

  In the server device 30 of FIG. 3, the P2P terminal application 16 first responds to the file download request from the terminal device 10 before notifying the request to the terminal device 20 on the file providing side, first of all, the terminal public file list 32, the care-of address associated with the list information of the public file information of the requested file is obtained, and the home address corresponding to the obtained care-of address is obtained by referring to the terminal home address table 33. It is acquired and it is confirmed whether or not the home address (acquired home address) of the terminal device 20 on the file providing side is included in the restricted home address list 34. Based on the confirmation result, it is determined whether or not the peer-to-peer file exchange between the terminal devices is successful.

  Next, the operation of the central server type peer-to-peer file exchange system of the first embodiment will be described. FIG. 7 shows a sequence of the central server type peer-to-peer file exchange system according to the first embodiment. In FIG. 7, a terminal device 10 having a mobile node function (MN), a terminal device 20 having a mobile node function (MN), a server device 30 having a home agent (HA) function, a peer-to-peer server service, and a terminal restriction function ( (Central server) is communicating.

  First, the terminal device 20 logs in to the server device 30 as a peer-to-peer client, and updates information regarding the association between the home address (HoA) and the care-of address (CoA) of the terminal device 20 itself to the server device 30 by Binding Update. Transmit (S101). The update information transmitted by Binding Update is transmitted when transmitting a file list, which will be described later, separately from transmission when moving in a normal mobile network.

  Upon receiving the Binding Update update information from the terminal device 20 and performing the update, the server device 30 notifies the terminal device 20 that the update has been successful as a Binding Ack (Binding Acknowledgment) (S102).

  The terminal device 20 transmits file list information published by the terminal device 20 itself to the server device 30 (S103). On the other hand, the sequence S104 to sequence S106 are executed in the same flow between the terminal device 10 and the server device 30.

  Next, the terminal device 10 searches a file published by the terminal device 20 from the file list of the server device 30 (S107), and if found, transmits a download request for the file to the server device 30 (S108). After receiving the file download request from the terminal device 10, the server device 30 acquires the care-of address of the terminal device 20 that provides the requested file from the terminal public file list 32, and the home address corresponding to the acquired care-of address. Is obtained from the terminal home address table 33, the restricted home address list 34 is referred to, and whether the home address of the terminal device 20 having the corresponding file is included in the restricted home address list 34 (whether it falls under the restriction) is confirmed. (S109).

  If it is not in the restricted home address list 34 (not applicable), the server device 30 notifies the terminal device 20 of a download request from the terminal device 10 (S110), and then the terminal device 10 The corresponding file is downloaded directly from 20 (S111).

  On the other hand, if it is in the restricted home address list 34 (if applicable), the server device 30 does not notify the terminal device 20 of a download request from the terminal device 10 and rejects the download request from the terminal device 10. To do.

  Next, the operation of the central server type peer-to-peer file exchange system will be described in more detail with reference to FIG. 8 showing a flowchart of the operation of each apparatus on the sequence diagram of FIG.

  FIG. 8 is a flowchart showing a processing procedure between the server device 30 (central server) and the terminal devices 10 and 20 in the central server type peer-to-peer file exchange system according to the first embodiment. The server device 30 has a home agent (HA) function, a peer-to-peer server service, and a terminal restriction function. The terminal device 10 and the terminal device 20 also have a mobile node function (MN) in addition to the peer-to-peer client function. .

  First, the terminal device 20 accesses the server device 30 and logs in. Then, the association update information of the home address (HoA) and the care-of address (CoA) of the terminal device 20 itself is transmitted to the server device 30 by Binding Update (step S201). The server device 30 receives the Binding Update update information of the terminal device 20, updates the association between the home address and the care-of address of the terminal device 20 in the terminal home address table 33 by the Binding Update (step S202), and then updates Is notified to the terminal device 20 (step S203).

  Upon receiving this notification, the terminal device 20 transmits the file list information to be disclosed to the server device 30 with its care-of address as the transmission source (step S204), and the server device 30 updates the terminal public file list 32. File list information is disclosed so that it can be seen from other terminal devices. The terminal public file list 32 is updated by the P2P server application 36 in the server device 30 by associating the received file list information with the care-of address of the terminal device 20 that is the transmission source.

  The terminal device 10 performs the same operation as steps S201 and S204 of the terminal device 20 (steps S205 and S208), and one server device 30 updates the binding update of the terminal device 10 as in step S202. The information is received, and the association between the home address and the care-of address of the terminal device 10 in the terminal home address table 33 is updated by Binding Update (step S206), and the Binding Ack is transmitted to the terminal device 10 (step S207). The public file list is updated (step S208).

  Thereafter, the terminal device 10 searches for a file (published by the terminal device 20) from the terminal public file list 32 of the server device 30 (step S209), and the server device 30 finds the search result (there is a searched file). ) Is transmitted to the terminal device 10 (step S210).

  Upon receiving the search result, the terminal device 10 transmits a download request for the file found by the search to the server device 30 (step S211). In response to the download request, the server device 30 first checks whether or not the home address (HoA) of the terminal device 20 on the providing side is included in the restricted home address list 34 (step S212).

  In step S212, the restriction is confirmed by checking that in the server device 30, the P2P server application 36 first refers to the terminal public file list 32 in response to the download request, and is the terminal that provides the file that has received the download request. The care-of address (CoA) of the device 20 is identified, the terminal home address table 33 is referred to, the identified care-of address (CoA) is converted into the home address (HoA), and the restricted home address list 34 is further referred to. This is done by checking whether the home address (HoA) falls under the restriction.

  If it is in the restricted home address list 34 (if applicable), the server device 30 notifies the terminal device 10 of a message indicating that download is not possible (step S213). The terminal device 10 determines the content of notification from the server device 30 (step S216). If it is determined that the notification is impossible, the terminal device 10 enters a standby state without doing anything.

  On the other hand, if it is not in the restricted home address list 34 (if it does not correspond to the restriction), the download request of the terminal device 10 is transferred to the terminal device 20 as it is (step S214), and download permission is notified to the terminal device 10. (Step S215). If it is determined that the notification is permission in S216, the terminal device 10 directly connects to the terminal device 20 (connecting to the terminal device 20 based on the care-of address of the terminal device 20 on the file providing side included in the permission notification). The corresponding file is downloaded (step S217).

  Thus, in the central server type peer-to-peer file exchange system, when exchanging files between terminal devices (between users) using Mobile IP (mobile IP) technology, association (binding) between the care-of address and the home address is performed. Since the stored home agent is provided with restriction information using the home address of the terminal device that is the file providing side as a keyword, and the file provision of the terminal device is restricted by this information, the file providing side is moved by moving the network like mobile IP Even if the address of the terminal device changes, it is possible to prevent illegal file exchange by the terminal device.

  Further, when the terminal devices 10, 20... Log in to publish the file list, the terminal devices 10, 20... Transmit update information on the correspondence between their home address (HoA) and the care-of address (CoA). Since the terminal home address table 33 is constantly updated to the latest state, the care-of address can be surely converted to the corresponding home address to determine whether or not the file can be provided.

  In the first embodiment described above, the configuration is such that after receiving a file provision request from the terminal device 10, 20..., It is confirmed whether the home address of the terminal device on the providing side falls under the restriction. When the terminal devices 10, 20... Disclose their own home address information to the server device 30, the server device refers to the restricted home address list 34 and whether the home address of the terminal device falls under the restriction. If there is a problem, the configuration may be such that all subsequent use of the server service is prohibited.

In the first embodiment, the binding update performed when the terminal device 10 or the terminal device 20 transmits the file list information to the server device 30 (update information is transmitted regarding the association between the home address and the care-of address) Of course, only when the file list information is transmitted to the server device 30, the timing for performing the binding update may be performed only when the file list information is transmitted to the server device 30. This can be done only when the network moves, or both. This Binding Update is preferably performed when the file list information is transmitted to the server device 30 because the latest home address and care-of address can be reliably obtained. In addition, when the Binding Update is performed when moving over the network, a server functioning as a mobile IP home agent can be used as the server device 30, so that it is not necessary to provide separate servers as the server device 30 and the home agent of the present invention. Cost saving and space saving can be realized at the same time.
(Embodiment 2)
Next, a peer-to-peer file exchange system according to the second embodiment will be described. Unlike the first embodiment, the peer-to-peer file exchange system according to the first embodiment does not have a so-called central server that manages information in the file search database, and all information is distributed between users in a bucket relay manner. Type peer-to-peer file exchange system.

  The overall configuration of the pure peer-to-peer file exchange system of the second embodiment is the same as the overall configuration of the central server peer-to-peer file exchange system of the first embodiment shown in FIG. 1, and the terminal device 10 according to the second embodiment, .. Are the same as the internal configurations of the terminal devices 10, 20,...

  FIG. 9 illustrates an internal configuration of the server device 30 (management server) according to the second embodiment. The server device 30 (management server) has an HA (home agent) function of a normal mobile IP system, and includes a DB 31, a main function unit 35, and a network communication unit 39.

  The DB 31 includes a terminal file provision history 41, a terminal home address table 33, and a home address list 34 of terminals to be restricted. The main function unit 35 includes an OS 38, a MIP HA function unit 37, and a P2P server application 36.

  The MIP HA function unit 37 can receive the association information between the home address and the care-of address of the terminal device transmitted from the terminal device, and can store it as the terminal home address table 33 in the DB 31 that is a cache (Binding Cache). .

  The P2P server application 36 can receive file information to be provided, which is transmitted from the terminal device, and can record the file information in the file provision history 41 of the terminal. Further, when the P2P server application 36 receives an inquiry from the terminal device as to whether or not to provide a file to another terminal device, the terminal device on the providing side that has made the inquiry with reference to the terminal home address table 33 The home address is specified from the current address (care-of address). Further, the P2P server application 36 refers to the restricted home address list 34 and confirms whether or not the identified home address corresponds to the restriction. In this way, the P2P server application 36 can determine whether or not the terminal device can provide a file to another terminal device based on the received home address of the terminal device.

  If it is determined that the provision is possible, the P2P server application 36 transmits a message indicating that the provision is possible to the terminal device on the providing side.

  In addition, the OS 38 provides a basic execution environment for the MIP HA function unit 37 and the P2P server application 36 to realize functions, and the network communication unit 39 performs internal and external transmission / reception.

  Further, the terminal home address table 33 and the restricted home address list 34 stored in the DB 31 of the server device according to the second embodiment are the same as those in the first embodiment, so that the description thereof is omitted.

  Next, the operation of the pure peer-to-peer file exchange system according to the second embodiment will be described. FIG. 10 shows a sequence of the pure peer-to-peer file exchange system according to the second embodiment. In FIG. 10, a terminal device 10 having a mobile node function (MN), a terminal device 20 having a mobile node function (MN), and a server device (management server) 30 having a home agent (HA) function and a terminal restriction function communicate with each other. is doing.

  First, the terminal device 10 connects to the terminal device 20 (S301), and inquires about a file (S302). In response to the inquiry from the terminal device 10, the terminal device 20 confirms the existence of the file by itself (S303).

  If there is a file, the terminal device 20 transmits the association update information between its home address (HoA) and the care-of address (CoA) to the server device 30 through Binding Update (S304). When the transmission from the terminal device 20 is received and the update is performed, the server device 30 notifies the terminal device 20 that the update is successful as a Binding Ack (Binding Acknowledgment) (S305). The update information transmitted by the binding update is transmitted when inquiry information (to be described later) is transmitted, separately from the transmission when moving in a normal mobile network.

  The terminal device 20 reports the file information that it intends to provide to the server device 30 and inquires of the server device 30 whether or not it can be provided (S306). In response to a report or inquiry from the terminal device 20, the server device 30 refers to the restricted home address list 34 and confirms whether the home address (HoA) of the terminal device 20 as the file providing side falls under the restriction. (S307). The server device 30 also stores an access history from the terminal device 20 (S308).

  When the home address of the terminal device 20 does not correspond to the restriction, the server device 30 sends a permission message indicating that provision is possible to the terminal device 20 (S309). Further, the terminal device 20 sends an inquiry result such as “there is a file” to the terminal device 10 (S310).

  Upon receiving the inquiry result such as “file exists”, the terminal device 10 immediately transmits a download request for the corresponding file to the terminal device 20 (S311), and then the terminal device 10 directly downloads the file from the terminal device 20. (S312).

  On the other hand, when the home address of the terminal device 20 corresponds to the restriction, the server device 30 sends a restriction message indicating that provision is not possible to the terminal device 20. The terminal device 20 further relays a file inquiry from the terminal device 10 to another terminal device.

  Next, the operation of the pure peer-to-peer file exchange system will be described in more detail with reference to FIG. 11 showing a flowchart of the operation of each device on the sequence diagram of FIG.

  FIG. 11 is a flowchart showing a processing procedure between the server device 30 (central server) and the terminal devices 10 and 20 in the pure peer-to-peer file exchange system according to the second embodiment. The server device 30 has a home agent (HA) function and a peer-to-peer terminal restriction function, and the terminal device 10 and the terminal device 20 also have a mobile node function (MN) in addition to the peer-to-peer file exchange function.

  First, the terminal device 10 accesses the terminal device 20 that has become a peer-to-peer server as a peer-to-peer client (step S401), and inquires about a file (step S402). In response to the inquiry from the terminal device 10, the terminal device 20 confirms the existence of the file by itself (step S 403). If there is no file, the terminal device 20 relays the inquiry from the terminal device 10 to another terminal device (step S404), and then enters a standby state.

  On the other hand, if there is a file, the terminal device 20 transmits the association update information of its home address (HoA) and care-of address (CoA) to the server device 30 through Binding Update (step S405). The server device 30 receives the update information from the terminal device 20 and updates the association between the home address and the care-of address of the terminal device 20 in the terminal home address table 33 using Binding Update (step S406), and the update is successful. This is notified to the terminal device 20 as Binding Ack (Binding Acknowledgment) (step S407).

  The terminal device 20 reports the file information that it intends to provide, and sends the inquiry to the server device 30 as to whether or not to provide the information (step S408). The server device 30 refers to the restricted home address list 34 in response to a report or inquiry from the terminal device 20, and determines whether the home address (HoA) of the terminal device 20 as the file providing side falls under the restriction. Confirmation is made (step S409). In the confirmation in step S409, the server device 30 refers to the terminal home address table 33, acquires the home address corresponding to the care-of address of the terminal device 20 that is the transmission source of the inquiry information, and further, the restricted home address list Referring to 34, it is confirmed whether or not the home address falls under the restriction.

  When the home address of the terminal device 20 corresponds to the restriction, the server device 30 sends a restriction message indicating that the provision is not possible to the terminal device 20 (step S410). On the other hand, when the home address of the terminal device 20 does not correspond to the restriction, the server device 30 sends a permission message indicating that the provision is possible to the terminal device 20 (step S411).

  The terminal device 20 receives the notification message from the server device 30, and determines the content (step S412). If it is determined that provision is possible, the terminal device 20 sends an inquiry result such as “there is a file” to the terminal device 10 (step S413). Upon receiving the request, the terminal device 10 immediately sends a download request for the corresponding file to the terminal device 20 (step S414), and then directly downloads the corresponding file from the terminal device 20 (step S415).

  On the other hand, if it is determined that provision is not possible, the terminal device 20 relays the inquiry from the terminal device 10 to another terminal device (step S416), and then enters a standby state.

  Thus, in a pure peer-to-peer file exchange system, when exchanging files between terminal devices (between users) using mobile IP technology, the home agent that stores the association (binding) between the care-of address and the home address is stored in the home agent. Since it has restriction information using the home address of the terminal device on the file providing side as a keyword, and this information restricts the file provision of the terminal device, the address of the terminal device on the file providing side is moved through the network like Mobile IP Even in the case where changes occur, illegal file exchange can be prevented.

  Further, the terminal devices 10, 20,... Send the update information of the correspondence between their home address (HoA) and the care-of address (CoA) when inquiring whether the file can be provided. Since the home address table 33 is always updated to the latest state, the care-of address can be surely converted to the corresponding home address to determine whether or not the file can be provided.

  In the second embodiment, only the binding update (sending update information regarding the association between the home address and the care-of address) performed when the terminal device 20 transmits a file provision inquiry to the server device 30 will be described. However, of course, the timing for performing the Binding Update may be any time when a file provision inquiry is transmitted to the server apparatus 30. Specifically, the binding update is performed only when a file provision inquiry is transmitted to the server apparatus 30. It can be done only when the network moves, or both. This Binding Update is preferably performed when a file provision inquiry is transmitted to the server device 30 because the latest home address and care-of address can be reliably obtained. In addition, when the Binding Update is performed when moving over the network, a server functioning as a mobile IP home agent can be used as the server device 30, so that it is not necessary to provide separate servers as the server device 30 and the home agent of the present invention. Cost saving and space saving can be realized at the same time.

  As described above, the peer-to-peer file exchange server and system according to the present invention monitor, identify, and block illegal file exchange activities by users in peer-to-peer file exchange (including data exchange) using mobile IP technology, particularly mobile IPv6 technology. And is particularly suitable for monitoring, identifying and blocking a user's illegal file exchange activity in business, SOHO market or personal free peer-to-peer file exchange.

Overall configuration diagram of a peer-to-peer file exchange system according to Embodiment 1 Functional block diagram showing an internal configuration example of the terminal device according to the first embodiment Functional block diagram showing an internal configuration example of the server apparatus in the first embodiment The figure which shows the terminal home address table stored in the server apparatus in Embodiment 1. The figure which shows the restricted terminal home address list | wrist stored in the server apparatus in Embodiment 1. The figure which shows the terminal public file list stored in the server apparatus in Embodiment 1. Sequence diagram of central server type peer-to-peer file exchange system according to the first exemplary embodiment Flowchart of processing of server device and terminal device in embodiment 1 Functional block diagram showing an internal configuration example of the server device in the second embodiment Sequence diagram of pure peer-to-peer file exchange system according to second embodiment Flowchart of processing of server device and terminal device in embodiment 2 Sequence diagram of a conventional central server type peer-to-peer file exchange system Sequence diagram of a conventional pure peer-to-peer file exchange system

Explanation of symbols

10, 20 Terminal device 11, 31 DB
12 Download Information 13 Public File Information 14, 33 Terminal Home Address Information 15, 35 Main Function Unit 16 P2P Terminal Application 17 MIP MN Function Unit 18, 38 OS
19, 39 Network communication unit 30 Server device 32 Terminal public file list 33 Terminal home address table 34 Home address table of restricted terminal 36 P2P server application 37 MIP HA function unit
40 Network 41 File provision history of terminal

Claims (6)

In a central server type peer-to-peer file exchange system comprising a plurality of mobile nodes and a server for publishing a file list of files provided by the mobile node, and performing file exchange between mobile nodes by peer-to-peer communication,
The mobile node includes address information transmission means for transmitting a mobile IP packet including a home address unique to the mobile node to the server at the time of the file exchange.
The server
Restriction information storage means for storing information on the home address of the mobile node that restricts file provision;
When the home address transmitted from the mobile node is stored in the restriction information storage means as the home address of the mobile node that restricts the provision of the file, the file exchange restriction means for restricting the processing related to the file exchange of the mobile node When,
A peer-to-peer file exchange system characterized by comprising: The mobile node further comprises file list transmission means for transmitting a file list of files provided by the mobile node to the server,
The server
Mobile node information storage means for storing a home address included in the mobile IP packet transmitted from the mobile node on the file providing side in association with a care-of address;
File list storage means for storing the file list received from the mobile node on the file providing side in association with the care-of address of the transmission source;
When the file exchange restriction unit receives a request for providing a file included in the file list stored in the file list storage unit from the mobile node on the file request side, the file exchange restriction unit notices corresponding to the file list including the file related to the request. An address is acquired from the file list storage means, a home address corresponding to the acquired care-of address is acquired from the mobile node information storage means, and the acquired home address is stored in the restriction information storage means as a restriction on file provision. The file can be provided only to the mobile node that is determined to be able to provide the file by determining whether or not the file is provided by the mobile node of the providing source based on whether or not the file is provided. The described peer-to-peer file exchange system. In a central server type peer-to-peer file exchange server that publishes a file list of files provided by a mobile node when a plurality of mobile nodes perform file exchange between the mobile nodes by peer-to-peer communication.
Address information receiving means for receiving, from the mobile node, a mobile IP packet including a home address unique to the mobile node during the file exchange;
Restriction information storage means for storing information on the home address of the mobile node that restricts file provision;
When the home address transmitted from the mobile node is stored in the restriction information storage means as the home address of the mobile node that restricts the provision of the file, the file exchange restriction means for restricting the processing related to the file exchange of the mobile node When,
A peer-to-peer file exchange server comprising: File list transmission means for receiving a file list of files provided by the mobile node from the mobile node on the file providing side;
Mobile node information storage means for storing a home address included in the mobile IP packet transmitted from the mobile node on the file providing side in association with a care-of address;
File list storage means for storing the file list received from the mobile node on the file providing side in association with the care-of address of the transmission source;
When the file exchange restriction unit receives a request for providing a file included in the file list stored in the file list storage unit from the mobile node on the file request side, the file exchange restriction unit notices corresponding to the file list including the file related to the request. An address is acquired from the file list storage means, a home address corresponding to the acquired care-of address is acquired from the mobile node information storage means, and the acquired home address is stored in the restriction information storage means as a restriction on file provision. 4. A file can be provided only to a mobile node that is determined to be able to provide a file by determining whether or not the file can be provided by the mobile node of the providing source based on whether or not the file is provided. The described peer-to-peer file exchange server. In a pure type peer-to-peer file exchange system comprising a plurality of mobile nodes and performing file exchange between mobile nodes by peer-to-peer communication,
A server capable of communicating with the mobile node;
The mobile node is
An address information transmitting means for transmitting a mobile IP packet including a home address unique to the mobile node to the server during the file exchange;
The server
Restriction information storage means for storing information on the home address of the mobile node that restricts file provision;
When the home address transmitted from the mobile node is stored in the restriction information storage means as the home address of the mobile node that restricts the provision of the file, the file exchange restriction means for restricting the processing related to the file exchange of the mobile node When,
A peer-to-peer file exchange system characterized by comprising: When the mobile node browses the file list of the file to be provided to the mobile node on the file request side and receives a request for providing the file included in the file list, an inquiry for inquiring whether or not to provide the file according to the request Inquiry means for transmitting information to the server;
When the file exchange restriction unit receives the inquiry information from the mobile node on the file providing side, the file exchange restriction unit acquires a home address corresponding to the care-of address of the transmission source of the inquiry information from the mobile node information storage unit, and acquires the acquired home The mobile that determines whether or not the file can be provided by determining whether or not the file can be provided by the mobile node of the providing source depending on whether or not the address is stored in the restriction information storage means as a restriction on the provision of the file. 6. The peer-to-peer file exchange system according to claim 5, wherein only a node can provide a file.

Images