JP2005143057A - Address table management method, and terminal - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide an address table management method whereby a particular network manages an address table wherein network addresses of terminals are unified without the need for utilizing the communication protocol unique to a Vender and to provide the terminals. <P>SOLUTION: The address table management method for managing the address table including IP addresses of the terminals belonging to a multicast group includes: a step A of the terminal 10a informing the terminal 10b about the IP address of the terminal 10a and the network address of a network to which the terminal 10a belongs; a step B of the terminal 10b setting the IP address of the terminal 10b on the basis of the network address and the IP address of the terminal 10a notified by the terminal 10a; a step C of the terminal 10b informing the terminal 10a about the IP address of the terminal 10b set in the step B; and a step D of the terminal 10a updating the address table on the basis of the IP address of the terminal 10b notified by the terminal 10b. <P>COPYRIGHT: (C)2005,JPO&NCIPI

Description

  The present invention relates to an address table management method for managing an address table including IP addresses of terminals connected to a network, and a terminal.

  An identifier called URI (Uniform Resource Identifier) [IETF RFC2396 “Uniform Resource Identifiers”] is known as an identifier for uniquely specifying a user or a terminal device. The URI is a logical identifier and is used for identifying a transmission source and a transmission destination when performing communication. Also, since the URI is an identifier in the application layer, when the URI is used for communication, it is necessary to perform mapping between the URI and the IP address.

  Note that the most used URI is a URL (Uniform Resource Locator) used when a Resource is uniquely specified in a Web Browser or the like.

  As described above, when a URL is used for communication, it is necessary to map (name resolution) the URL and the IP address. As this mapping technique, a technique called DNS (Domain Name System) [IETF RFC1035 “Domain names-implementation and specification”] is known. In DNS, name resolution on the Internet is performed by a server (name server) that stores data necessary for name resolution.

  Another name resolution method that is effective in a network that is relatively smaller than the entire Internet is also known. For example, in Windows, which is a Microsoft OS, communication is possible by mapping host names and IP addresses using a method unique to Vender. At this time, as the communication protocol itself, a protocol uniquely defined by Vender (eg, Microsoft NetBIOS) is used. Also, a method is known in which a combination of a host name and an IP address is stored in advance in each terminal, like a hosts file in UNIX.

On the other hand, in the AdHoc network, each other knows the other party's IP address in advance, and communication is performed based on the IP address. Further, depending on the application and the OS, the host name and the IP address are mapped by a method unique to Vender, and communication is performed using the host name.
JP-A-11-55350

  However, since the communication protocol unique to Vender is different from the communication protocol in the public network, there is a problem that it is necessary to implement software that operates the communication protocol unique to Vender.

  Accordingly, the present invention has been made to solve the above-described problem, and the network address of each terminal is unified in a specific network (for example, AdHoc network) without using a communication protocol unique to Vender. It is an object of the present invention to provide an address table management method and a terminal capable of managing an address table.

  According to a first aspect of the present invention, there is provided an address table management method for managing an address table including IP addresses of terminals belonging to a multicast group, wherein the parent terminal determines an IP address of the parent terminal and a network address of a network to which the parent terminal belongs. Set in Step A and Step B in which the child terminal notifies the child terminal, and the child terminal sets the IP address of the child terminal based on the IP address and network address of the parent terminal notified by the parent terminal. And a step C in which the child terminal notifies the parent terminal of the IP address of the child terminal, and a step D in which the parent terminal updates the address table based on the IP address of the child terminal notified by the child terminal. And

  The second feature of the present invention is that the first terminal managing the address table including the IP addresses of the terminals belonging to the multicast group includes the IP address of the first terminal and the network address of the network to which the first terminal belongs. The second terminal IP address set in the second terminal is based on the notification unit that notifies the second terminal of the second terminal, and the IP address and network address of the first terminal notified by the notification unit. And an update unit that updates the address table based on the IP address of the second terminal when notified by the second terminal.

  According to this feature, the first terminal (parent terminal) is set in the second terminal (child terminal) based on the IP address of the first terminal and the network address of the network to which the first terminal belongs By updating the address table based on the IP address of the second terminal, the first terminal can use the network of each terminal in a specific network (for example, AdHoc network) without using a Vender-specific protocol. An address table with a unified address can be managed.

  In the second feature of the present invention, the notifying unit notifies the second terminal that the IP address is duplicated when the IP address of the second terminal is duplicated with an IP address included in the address table. It is preferable.

  In the second feature of the present invention, the notifying unit notifies the second terminal of an IP address not included in the address table when the IP address of the second terminal overlaps with an IP address included in the address table. It is preferable to do.

  In the second feature of the present invention, it is preferable that the notification unit notifies the second terminal of the address table when the IP address of the second terminal overlaps with an IP address included in the address table.

  In the second aspect of the present invention, it is preferable that the notification unit notifies the address table to the multicast group when the IP addresses included in the address table do not overlap.

  In the second feature of the present invention, it is preferable that the updating unit deletes the IP address included in the address table when a predetermined time has elapsed.

  In the second feature of the present invention, it is preferable that the updating unit manages the IP address of the second terminal included in the address table in association with the user identifier of the second terminal.

  In the second feature of the present invention, the updating unit preferably manages the IP address of the second terminal included in the address table and the terminal identifier of the second terminal in association with each other.

  The third feature of the present invention is that the second terminal uses the IP address of the first terminal based on the IP address of the first terminal notified by the first terminal and the network address of the network to which the first terminal belongs. The gist of the invention is that it includes an IP address setting unit for setting an address and a notification unit for notifying the first terminal of the IP address of the terminal set by the IP address setting unit.

  According to such a feature, the second terminal sets the IP address of its own terminal based on the IP address of the first terminal and the network address of the network to which the first terminal belongs, whereby the second terminal Can set an IP address consistent with the network address of the first terminal as the IP address of the own terminal.

  A fourth feature of the present invention is that a second terminal requests a terminal belonging to a multicast group for an IP address of the first terminal and a network address of a network to which the first terminal belongs, and a multicast group An IP address setting unit for setting the IP address of the own terminal based on the IP address and network address of the first terminal notified by the terminal belonging to the terminal, and the IP address of the own terminal set by the IP address setting unit The gist is to include a notification unit that notifies the first terminal.

  According to such a feature, the second terminal requests the IP address of the first terminal and the network address of the network to which the first terminal belongs, whereby a specific network formed by the first terminal (for example, , AdHoc network). Further, the second terminal can set an IP address matched with the network address of the first terminal as the IP address of the own terminal.

  In the third feature or the fourth feature of the present invention, the IP address setting unit may reset the IP address of the own terminal when the first terminal requests to change the IP address of the own terminal. preferable.

  In the third feature or the fourth feature of the present invention, when the IP address setting unit is notified of the IP address generated by the first terminal by the first terminal, the IP address setting unit transmits the notified IP address to the own terminal. It is preferable to set it as the IP address.

  In the third feature or the fourth feature of the present invention, the IP address setting unit is included in the notified address table when the address table managed by the first terminal is notified by the first terminal. It is preferable to set an unassigned IP address as the IP address of the own terminal.

  In the third feature or the fourth feature of the present invention, the notifying unit transmits the user identifier of the second terminal to the first terminal together with the IP address of the own terminal set by the IP address setting unit. preferable.

  In the third feature or the fourth feature of the present invention, the notification unit transmits the terminal identifier of the second terminal to the first terminal together with the IP address of the own terminal set by the IP address setting unit. preferable.

  According to the present invention, an address table management method for managing an address table in which network addresses of terminals are unified in a specific network (for example, AdHoc network) without using a communication protocol unique to Vender, and a terminal Can be provided.

(Configuration of terminal according to one embodiment of the present invention)
Hereinafter, the configuration of a terminal according to an embodiment of the present invention and a network to which the terminal is connected will be described with reference to FIGS. FIG. 1 is an overall configuration diagram of a network to which terminals according to the present embodiment are connected.

  As shown in FIG. 1, the terminals 10a to 10d according to the present embodiment form a specific network (hereinafter referred to as AdHoc network). Further, the terminals 10a to 10d are assumed to form an AdHoc mode communication network in a physical layer (Layer 1) and a MAC sub-layer (Layer 2) by a wireless network (for example, a wireless LAN compliant with IEEE 802.11). Further, it is assumed that the terminals 10a to 10d belong to a predetermined multicast group.

  In the present embodiment, the terminal 10a constitutes a parent terminal (or first terminal) that manages an address table including IP addresses of terminals participating in the AdHoc network. In addition, the terminals 10b to 10d are slave terminals (or second terminals) that set their own IP addresses based on the IP address of the terminal 10a notified by the terminal 10a and the network address of the network to which the terminal 10a belongs. Terminal).

  Since the terminals 10b to 10d have the same configuration, the terminal 10b will be described as an example of a child terminal (or a second terminal).

  As shown in FIG. 2A, the terminal 10a includes a transmission / reception unit 11a, a control unit 12a, an IP address generation unit 13a, and a storage unit 14a.

  The transmission / reception unit 11a transmits / receives each information to / from the terminal 10b. For example, the transmission / reception unit 11a includes an IP address (192.168.0.11), a user identifier (hereinafter, URI (alice@company.co.jp)), a terminal identifier (hereinafter, MAC address), and a subnet mask of the terminal 10a. (255.255.255.0), a name resolution information request including the AdHoc network name and the effective duration of the AdHoc network is transmitted to the multicast group. That is, the transmission / reception unit 11a transmits the IP address (192.168.0.11) of the terminal 10a and the subnet mask (255.255.255.0) to the multicast group, whereby the IP address ( 192.168.0.11) and the network address (192.168.0.0) of the network to which the terminal 10a belongs are notified to the terminal 10b.

  Further, as a response to the name resolution information request, the transmission / reception unit 11a receives a name resolution information response including the IP address, URI, and MAC address of the terminal 10b from the terminal 10b.

  The control unit 12a manages a name resolution table (address table) (see FIG. 3) including IP addresses of terminals participating in the AdHoc network. For example, when receiving a name resolution information response from the terminal 10b, the control unit 12a updates the name resolution table based on the IP address, URI, and MAC address included in the name resolution information response. That is, when the control unit 12a receives the IP address of the terminal 10b set in the terminal 10b based on the IP address of the terminal 10a and the network address of the network to which the terminal 10a belongs, the control unit 12a is based on the IP address of the terminal 10b. Update the name resolution table (address table).

  Further, the control unit 12a checks whether or not the IP address included in the name resolution table and the IP address of the terminal 10b are duplicated. If the IP address is duplicated, the IP address is duplicated. The transmission / reception unit 11a is controlled so as to transmit information (hereinafter, IP address change request) indicating that it is present to the terminal 10b.

  Further, when the effective duration of the AdHoc network associated with the IP address included in the name resolution table is exhausted, the control unit 12a deletes information associated with the IP address. The control unit 12a may be configured to extend the effective duration according to a predetermined condition when the effective duration of the AdHoc network is exhausted.

  The IP address generation unit 13a generates an IP address not included in the name resolution table (an IP address that does not overlap with the IP address of another terminal) as the IP address (candidate) of the terminal 10b. For example, when transmitting an IP address change request to the terminal 10b, the IP address generation unit 13a generates the IP address (candidate) of the terminal 10b included in the IP address change request.

  The storage unit 14a stores a name resolution table (address table) including IP addresses of terminals participating in the AdHoc network. Specifically, this will be described with reference to FIG.

  As shown in the figure, the storage unit 14a includes the URIs of the terminals participating in the AdHoc network (for example, IP address, MAC address, and Status (whether the terminal is a parent terminal or not, the terminal participates in the AdHoc network). In addition to the above-mentioned information, the name resolution table is associated with the AdHoc network name, the AdHoc network effective duration, and the like. ing.

  As illustrated in FIG. 2B, the terminal 10b includes a transmission / reception unit 11b, a control unit 12b, an IP address setting unit 13b, and a storage unit 14b.

  The transmission / reception unit 11b transmits / receives each information to / from the terminal 10a. For example, the transmission / reception unit 11b receives the above-described name resolution information request or IP address change request from the terminal 10a, and transmits the above-described name resolution information response to the terminal 10a.

  That is, the transmission / reception unit 11b sets the terminal 10b set based on the IP address (192.168.0.11) and the subnet mask (255.255.255.0) of the terminal 10a (parent terminal or first terminal). Is sent to the terminal 10a.

  Whether or not to set the IP address generated by the terminal 10a as the IP address of the terminal 10b when the control unit 12b receives information including the IP address generated by the terminal 10a (for example, an IP address change request) Determine whether.

  The IP address setting unit 13b sets the IP address of the terminal 10b based on information received from the terminal 10a.

  For example, when the IP address setting unit 13b receives a name resolution information request from the terminal 10a, the IP address (192.168.0.11) and subnet mask (255.255) of the terminal 10a included in the name resolution information request. 255.0), the IP address of the terminal 10b is set. The IP address setting unit 13b receives the network address (192.168.0.0), the broadcast address (192.168.0.255), and the IP address (192.168.0.11) of the terminal 10a as the terminal. Assume that the IP address of 10b is not set.

  That is, the IP address setting unit 13b is based on the IP address (192.168.0.11) of the terminal 10a notified by the terminal 10a and the network address (192.168.0.0) of the network to which the terminal 10a belongs. To set the IP address of the terminal itself.

  The storage unit 14b stores a name resolution table that is received from the terminal 10a and does not include a duplicate IP address.

(Operation of terminal according to one embodiment of the present invention)
The operation of the terminal in the network according to the embodiment of the present invention will be described below with reference to FIGS. 4 and 5 are flowcharts showing name resolution table sharing processing (formation) in the present embodiment.

  As shown in the figure, in Step 11, the terminal 10a resolves the name including the terminal 10a IP address, terminal identifier (hereinafter, URI and MAC address), subnet mask, AdHoc network name, and AdHoc network effective duration. Send an information request to the multicast group. The terminal 10a may transmit the name resolution information request to the multicast group a plurality of times.

  In step 12, the terminal 10b checks whether there is one name resolution information request transmitted to the multicast group. The terminal 10b proceeds to the process of step 14 when there is one name resolution information request, and proceeds to the process of step 13 when there is not one name resolution information request.

  In step 13, the terminal 10b recognizes the name resolution information request with the earliest transmission time as valid. Further, the terminal 10b may be configured to recognize a name resolution information request or the like with the smallest contained MAC as valid.

  In step 14, the terminal 10b recognizes the terminal (terminal 10a) that has transmitted a valid name resolution information request as the parent terminal (or first terminal).

  In step 15, the terminal 10b sets the IP address of its own terminal based on the name resolution information request received from the terminal 10a.

  Specifically, the terminal 10b specifies a network address based on the IP address and subnet mask of the terminal 10a included in the name resolution information request, and randomly selects and selects the IP address according to the specified network address. The set IP address is set as the IP address of the own terminal. The terminal 10b does not set the network address, the broadcast address, and the IP address of the terminal 10a as the IP address of the terminal 10b.

  In step 16, the terminal 10b transmits a name resolution information response including the set IP address, URI, MAC address, name of the AdHoc network, and effective duration of the AdHoc network to the terminal 10a by unicast.

  In step 17, the terminal 10a associates and stores each information included in the name resolution information response received from the terminal 10b. That is, the terminal 10a updates the name resolution table (address table) including the IP addresses of the terminals participating in the AdHoc network. Since the terminal 10a does not know the number of terminals participating in the AdHoc network, the terminal 10a is configured to wait for a reply of a name resolution information response for a certain period of time.

  In step 18, after waiting for a predetermined time, the terminal 10a checks whether or not the IP address included in the name resolution table and the IP address of the terminal 10b overlap. Further, the terminal 10a proceeds to the process of step 19 when the IP address is duplicated, and proceeds to the process of step 23 when the IP address is not duplicated.

  In step 19, the terminal 10a transmits an IP address change request including an IP address not included in the name resolution table (an IP address not overlapping with the IP address of another terminal) to the terminal 10b by unicast. The IP address change request may include a name resolution table.

  In step 20, the terminal 10b determines whether or not to set the IP address included in the IP address change request received from the terminal 10a as the IP address of its own terminal. Further, when the terminal 10b sets the IP address included in the IP address change request as the IP address of the own terminal, the terminal 10b moves to the process of step 22 and changes the IP address included in the IP address change request to the own terminal. If the IP address is not set, the process proceeds to step 21.

  In step 21, the terminal 10b resets its own IP address based on the IP address and subnet mask of the terminal 10a included in the name resolution information request received from the terminal 10a.

  In step 22, the terminal 10b transmits the IP address change response including the IP address included in the IP address change request or the IP address reset in step 21 to the terminal 10a by unicast.

  In step 23, the terminal 10a transmits to the multicast group a name resolution table in which the included IP addresses are not duplicated.

  In step 24, the terminal 10b transmits a name resolution table reception confirmation indicating that the name resolution table transmitted to the multicast group has been received to the terminal 10a by unicast.

  In step 25, the terminal 10a compares the number of terminals included in the name resolution table with the number of received name resolution table reception confirmations. If the two match, the terminal 10a ends the name resolution table sharing process. If the two do not match, the terminal 10a proceeds to the process of step 26.

  In step 26, the terminal 10a retransmits the name resolution table by unicast to a terminal that has not received the name resolution table reception confirmation.

  Hereinafter, a process when a terminal joins an already formed AdHoc network from the middle will be described. 6 and 7 are flowcharts showing the name resolution table sharing process (participation in the middle). In the following description, it is assumed that the terminal 10d is a terminal participating from the middle.

  As shown in the figure, in step 31, the terminal 10d transmits a parent terminal search request for confirming the parent terminal to the multicast group.

  In step 32, the terminal 10a sends a name resolution information request including the IP address of the terminal 10a, the URI, the MAC address, the AdHoc network name, the AdHoc network valid duration, and an IP address not overlapping with other terminals to the multicast group. Send to. Note that terminals other than the terminal 10d ignore the name resolution information request.

  In step 33, the terminal 10d determines whether or not to set the IP address included in the name resolution information request (or IP address change request) received from the terminal 10a as the IP address of its own terminal. If the terminal 10d sets the IP address included in the name resolution information request (or IP address change request) as the IP address of its own terminal, the terminal 10d moves to the process of step 35 (or changes the IP address). If the IP address included in the request is not set as the IP address of the own terminal, the process proceeds to step 34.

  In step 34, the terminal 10d sets the IP address of its own terminal based on the IP address and subnet mask of the terminal 10a included in the name resolution information request received from the terminal 10a.

  In step 35, the terminal 10d includes the IP address included in the name resolution information request or the IP address set in step 34, the URI of the terminal 10d, the MAC address, the AdHoc network name, and the AdHoc network valid duration. A name resolution information response is transmitted to the terminal 10a by unicast.

  In step 36, the terminal 10a associates and stores each information included in the name resolution information response received from the terminal 10d. That is, the terminal 10a updates the name resolution table (address table) including the IP addresses of the terminals participating in the AdHoc network.

  In step 37, the terminal 10a checks whether or not the IP address included in the name resolution table overlaps with the IP address of the terminal 10d. If the IP address is duplicated, the terminal 10a proceeds to the process of step 38, and if the IP address is not duplicated, the terminal 10a proceeds to the process of step 39.

  In step 38, the terminal 10a transmits an IP address change request including an IP address not included in the name resolution table (an IP address not overlapping with other terminals) to the terminal 10d by unicast. The IP address change request may include a name resolution table.

  In step 39, the terminal 10a transmits to the multicast group a name resolution table in which the IP addresses of the included terminals are not duplicated.

  In step 40, the terminal 10d transmits a name resolution table reception confirmation indicating that the name resolution table transmitted to the multicast group has been received, to the terminal 10a by unicast.

  In step 41, the terminal 10a compares the number of terminals included in the name resolution table with the number of received name resolution table reception confirmations. If the two match, the terminal 10a ends the name resolution table sharing process. If the two do not match, the terminal 10a proceeds to the process of step 42.

  In step 42, the terminal 10a retransmits the name resolution table by unicast to a terminal that has not received the name resolution table reception confirmation.

  Hereinafter, processing when a terminal participating in the AdHoc network leaves midway will be described with reference to the drawings. In the following description, it is assumed that the terminal that leaves midway is the terminal 10d. FIG. 8 is a flowchart showing name resolution table sharing processing (withdrawal on the way) in the present embodiment.

  As shown in the figure, in step 51, the terminal 10d transmits an exit request indicating exit from the AdHoc network to the terminal 10a by unicast. Note that the terminal 10d may transmit an exit request to the multicast group. At this time, each terminal that has received the exit request may be configured to update the name resolution table.

  In step 52, the terminal 10a updates the name resolution table based on the exit request received from the terminal 10d. At this time, considering the possibility that the terminal 10d will rejoin, the terminal 10a changes the status of the terminal 10d from “Active” to “Halt” without deleting the information related to the terminal 10d. Note that if the terminal 10d does not rejoin even after a certain period of time has elapsed, the terminal 10a deletes the information related to the terminal 10d from the name resolution table.

  In step 53, the terminal 10a transmits the updated name resolution table to the multicast group.

  In step 54, each terminal receiving the name resolution table transmits a name resolution table reception confirmation indicating that the name resolution table transmitted to the multicast group has been received to the terminal 10a by unicast.

  In step 55, the terminal 10a compares the number of terminals included in the name resolution table with the number of received name resolution table reception confirmations. If the two match, the terminal 10a ends the name resolution table sharing process (withdrawal on the way), and if the two do not match, the terminal 10a proceeds to the process of step 56.

  In step 56, the terminal 10a retransmits the name resolution table by unicast to the terminal that has not received the name resolution table reception confirmation.

  Hereinafter, processing when a terminal that leaves the AdHoc network rejoins the AdHoc network will be described with reference to the drawings. In the following description, it is assumed that the rejoining terminal is the terminal 10d. FIG. 9 and FIG. 10 are flowcharts showing the name resolution table sharing process (re-participation) in this actual form.

  As shown in the figure, in step 61, the terminal 10d transmits a rejoin request indicating rejoin to the AdHoc network to the terminal 10a by unicast. When the terminal 10d leaves the AdHoc network, the terminal 10a stores the URI, IP address, MAC address, and the like of the terminal 10a without deleting them.

  In step 62, the terminal 10a sends a request for name resolution information including the IP address, URI, MAC address, AdHoc network name, AdHoc network valid duration, and IP address not overlapping with other terminals to the terminal 10d. Send by unicast.

  In step 63, the terminal 10d determines whether or not to set the IP address included in the name resolution information request (or IP address change request) received from the terminal 10a as the IP address of its own terminal. Further, when the terminal 10d sets the IP address included in the name resolution information request (or IP address change request) as the IP address of the terminal itself, the terminal 10d proceeds to the process of step 65, and the name resolution information request (or If the IP address included in the (IP address change request) is not set as the IP address of the own terminal, the process proceeds to step 64.

  In step 64, the terminal 10d sets the IP address of its own terminal based on the IP address and subnet mask of the terminal 10a included in the name resolution information request received from the terminal 10a.

  In step 65, the terminal 10d includes the IP address included in the name resolution information request or the IP address set in step 64, the URI of the terminal 10d, the MAC address, the AdHoc network name, and the AdHoc network valid duration. A name resolution information response is transmitted to the terminal 10a by unicast.

  In step 66, the terminal 10a associates and stores each information included in the name resolution information response received from the terminal 10d. That is, the terminal 10a updates the name resolution table (address table) including the IP addresses of the terminals participating in the AdHoc network.

  In step 67, the terminal 10a checks whether or not the IP address included in the name resolution table overlaps with the IP address of the terminal 10d. If the IP address is duplicated, the terminal 10a proceeds to step 68. If the IP address is not duplicated, the terminal 10a proceeds to step 69.

  In step 68, the terminal 10a transmits an IP address change request including an IP address not overlapping with other terminals to the terminal 10d by unicast. The IP address change request may include a name resolution table.

  In step 69, the terminal 10a transmits to the multicast group a name resolution table in which the IP addresses of the included terminals are not duplicated.

  In step 70, the terminal 10d transmits a name resolution table reception confirmation indicating that the name resolution table transmitted to the multicast group has been received to the terminal 10a by unicast.

  In step 71, the terminal 10a compares the number of terminals included in the name resolution table with the number of received name resolution table reception confirmations. If the two match, the terminal 10a ends the name resolution table sharing process. If the two do not match, the terminal 10a proceeds to the process of step 72.

  In step 72, the terminal 10a retransmits the name resolution table by unicast to a terminal that has not received the name resolution table reception confirmation.

  In this embodiment, only one AdHoc network is formed. However, a plurality of AdHoc networks are formed in the same LAN segment (in the case of a wired network) or the same wireless channel (in the case of a wireless network). May be.

  At this time, it is assumed that the parent terminal in each AdHoc network manages a name resolution table unified with different network addresses. Further, it is assumed that terminals belonging to a plurality of AdHoc networks can set different IP addresses for each AdHoc network.

(Operation and effect of terminal according to one embodiment of the present invention)
According to the terminal according to the present embodiment, the terminal 10a (parent terminal) transmits the IP address and subnet mask of the terminal 10a to the multicast group, so that the network of the network to which the terminal 10a belongs and the IP address of the terminal 10a belongs to. The terminal 10b (child terminal) notifies the terminal 10b (child terminal), and the terminal 10b sets the IP address of the terminal 10b based on the notified IP address and network address of the terminal 10a. An IP address that matches the network address of the terminal can be set as the IP address of the own terminal.

  Also, the terminal 10b notifies the terminal 10a of the IP address of the terminal 10a set based on the IP address and the network address of the terminal 10a, and the name resolution table (based on the IP address of the terminal 10b to which the terminal 10a is notified ( By updating the address table, the terminal 10a can manage the name resolution table in which the network address is unified with the network address of the terminal 10a.

  Furthermore, the terminal 10a transmits the name resolution table managed by the terminal 10a to the multicast group, so that each terminal participating in the AdHoc network has a name resolution table in which the network address is unified with the network address of the terminal 10a. Can be shared.

  Further, the terminal 10a checks whether the IP address of each terminal included in the name resolution table is duplicated, and if the IP address of each terminal is duplicated, the duplicate IP address is set. By transmitting the IP address change request to the terminal, the terminal 10a can manage the name resolution table so that the IP address of each terminal included in the name resolution table does not overlap.

1 is an overall configuration diagram of a network to which a terminal according to the present embodiment is connected. It is a block diagram which shows the structure of the terminal 10a (parent terminal) and the terminal 10b (child terminal) which concern on this embodiment. It is a figure which shows an example of the name resolution table managed by the terminal 10a (parent terminal) which concerns on this embodiment. It is a flowchart which shows the name resolution table sharing process (formation) which concerns on this embodiment (the 1). It is a flowchart which shows the name resolution table sharing process (formation) which concerns on this embodiment (the 2). It is a flowchart which shows the name resolution table sharing process (participation in the middle) which concerns on this embodiment (the 1). It is a flowchart which shows the name solution table sharing process (participation in the middle) which concerns on this embodiment (the 2). It is a flowchart which shows the name resolution table sharing process (midway leaving) which concerns on this embodiment. It is a flowchart which shows the name resolution table sharing process (repartition) which concerns on this embodiment (the 1). It is a flowchart which shows the name resolution table sharing process (repartition) which concerns on this embodiment (the 2).

Explanation of symbols

  10a to 10d ... terminal, 11a and 11b ... transmission / reception unit, 12a and 12b ... control unit, 13a ... IP address generation unit, 13b ... IP address setting unit, 14a and 14b ... Storage

Claims (16)

An address table management method for managing an address table including IP addresses of terminals belonging to a multicast group,
A process in which the parent terminal notifies the child terminal of the IP address of the parent terminal and the network address of the network to which the parent terminal belongs;
A step B in which the child terminal sets the IP address of the child terminal based on the IP address of the parent terminal notified by the parent terminal and the network address;
A step C in which the child terminal notifies the parent terminal of the IP address of the child terminal set in the step B;
An address table management method comprising: a step D in which the parent terminal updates the address table based on an IP address of the child terminal notified by the child terminal. A first terminal that manages an address table including IP addresses of terminals belonging to a multicast group,
A notification unit that notifies the second terminal of the IP address of the first terminal and the network address of the network to which the first terminal belongs;
Based on the IP address of the first terminal and the network address notified by the notification unit, the IP address of the second terminal set in the second terminal is notified by the second terminal. And an update unit that updates the address table based on the IP address of the second terminal.   The notifying unit notifies the second terminal that the IP address is duplicated when the IP address of the second terminal is duplicated with an IP address included in the address table. The first terminal according to claim 2.   The notifying unit notifies the second terminal of an IP address not included in the address table when an IP address of the second terminal overlaps with an IP address included in the address table. The first terminal according to claim 2 or 3.   The said notification part notifies the said address table to the said 2nd terminal, when the IP address of the said 2nd terminal overlaps with the IP address contained in the said address table. Item 5. The first terminal according to Item 4.   The first notification according to any one of claims 2 to 5, wherein the notification unit notifies the address table to the multicast group when the IP addresses included in the address table do not overlap. Terminal.   The first terminal according to claim 2, wherein the update unit deletes an IP address included in the address table when a predetermined time elapses.   The update unit according to any one of claims 2 to 7, wherein the updating unit manages the IP address of the second terminal included in the address table and the user identifier of the second terminal in association with each other. 1 terminal.   9. The update unit according to claim 2, wherein the updating unit manages the IP address of the second terminal included in the address table and the terminal identifier of the second terminal in association with each other. 1 terminal. An IP address setting unit configured to set the IP address of the own terminal based on the IP address of the first terminal notified by the first terminal and the network address of the network to which the first terminal belongs;
A second terminal comprising: a notifying unit for notifying the first terminal of the IP address of the terminal set by the IP address setting unit. A request unit that requests a terminal belonging to the multicast group for the IP address of the first terminal and the network address of the network to which the first terminal belongs;
An IP address setting unit for setting an IP address of the own terminal based on the IP address of the first terminal and the network address notified by the terminals belonging to the multicast group;
A second terminal comprising: a notifying unit for notifying the first terminal of the IP address of the terminal set by the IP address setting unit.   The IP address setting unit resets the IP address of the own terminal when the change of the IP address of the own terminal is requested from the first terminal. Second terminal.   The IP address setting unit sets the notified IP address as the IP address of the own terminal when the IP address generated by the first terminal is notified by the first terminal. The 2nd terminal of Claim 10 thru | or 12.   When the address table managed by the first terminal is notified by the first terminal, the IP address setting unit assigns an IP address not included in the notified address table to the IP address of the own terminal. 14. The second terminal according to claim 10, wherein the second terminal is set as an address.   The said notification part transmits the user identifier of a said 2nd terminal to a said 1st terminal with the IP address of the own terminal set by the said IP address setting part, The said terminal is characterized by the above-mentioned. The 2nd terminal as described in. The said notification part transmits the terminal identifier of a said 2nd terminal to a said 1st terminal with the IP address of the self-terminal set by the said IP address setting part, The Claim 15 thru | or 15 characterized by the above-mentioned. The 2nd terminal as described in.

Images