JP2010045526A - Method of updating program of wireless ad-hoc network terminal, and wireless ad-hoc network terminal - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a method of efficiently updating a program of each terminal constituting a wireless ad-hoc network without requiring connection to a server for program management or a base station. <P>SOLUTION: This method is used for updating a program in a wireless ad-hoc network comprising a network management terminal CD, a relay function holding terminal RD, and a plurality of end terminals ED, and having a parent-child relationship among the terminals. First an update-dedicated terminal EDU is connected to the network; network information is acquired from the network management terminal CD; a update program distribution list including a distribution order and a distribution route is created based on the network information; and an update program is distributed in accordance with the update program distribution list. For the distribution route, a plurality of block management nodes are set on the network, and the update program is distributed by using the block management nodes as base points. <P>COPYRIGHT: (C)2010,JPO&INPIT

Description

  The present invention relates to a program updating method for a wireless ad hoc network terminal and a wireless ad hoc network terminal capable of efficiently updating a program stored in each terminal constituting the wireless ad hoc network.

  When upgrading a program version or the like in a network to which a large number of terminals are connected, it is necessary to update the program stored in each terminal. For this purpose, conventionally, a method has been used in which a program management device for managing the entire network is installed and each terminal acquires a program from the program management device by wireless communication or the like.

  For example, Patent Document 1 discloses a method of checking the version of a program stored in a mobile terminal by communication between the program management apparatus and the mobile terminal, and downloading an update program if necessary. Patent Document 2 discloses a method of updating PHS radio base station software within a short time using a private branch exchange. Also in this case, an update program is transmitted from the management radio base station for program management to the private branch exchange, and the private branch exchange updates the software of each radio base station.

However, each of these conventional technologies connects each terminal to a program management server or base station via a line to update the program, and it is complicated work such as grasping the position of the existing parent terminal and cable connection. Was necessary. In addition, any of these conventional techniques is a program update method in a network in which connected terminals are registered in advance, and cannot be applied to a wireless ad hoc network configured by unspecified terminals.
JP 2000-188769 A JP 2002-232466 A

  Therefore, the object of the present invention is to solve the above-mentioned conventional problems, and in a wireless ad hoc network composed of unspecified terminals, it is not necessary to connect to a program management server or a base station. It is an object of the present invention to provide a program update method for a wireless ad hoc network terminal that can be updated efficiently.

  In order to solve the above problems, the invention of claim 1 is directed to a network management terminal for managing the entire network and one or more relays having a relay function for relaying data to other terminals connected to the network management terminal. In a wireless ad hoc network composed of a plurality of terminals including a function holding terminal and having a parent-child relationship between the terminals, a terminal holding an update program is connected to the wireless ad hoc network, and network information is acquired from the network management terminal Then, an update program distribution list including a distribution order and a distribution route is created based on the network information, and the update program is distributed to at least one of the plurality of terminals according to the update program distribution list. The terminal that has received the program updates the program using the distributed update program. It is characterized in.

  In addition, as in claim 2, the distribution route is a set of a plurality of block management nodes in the network, and the terminal holding the update program distributes the update program and the update program distribution list to the block management node, The distributed block management node transfers the distributed update program to other block management nodes and terminals belonging to its own block, and further updates the distribution distribution list received by the other block management node. It is preferable to transfer.

  In the second aspect of the present invention, as described in the third aspect, the block management node further includes a parent terminal of the terminal holding the update program, a parent terminal of the block management node, and a child terminal of the block management node. It is preferable to have a terminal.

  According to a fourth aspect of the present invention, the distribution order is preferably to distribute the update program and the update program distribution list in the order of the smallest number of hops when viewed from the terminal holding the update program among the plurality of block management nodes. . In the invention of claim 4, when the number of hops is the same as described in claim 5, the update program and update program distribution are given priority to the block management node over other terminals belonging to its own block. It is preferable to distribute the list, and when the number of hops is the same as in claim 6, the update program and the update program distribution list are distributed in preference to the block management node having a large number of nodes to be managed. You can also Furthermore, as described in claim 7, when the number of hops is the same, an update program and an update program distribution list are given priority to a block management node having a large number of transfers excluding an overlap portion based on the block management node. Can also be distributed.

  As in claim 8, it is preferable that the terminal holding the update program creates an update program distribution list based on the network information and update conditions acquired from the network management terminal.

  According to a ninth aspect of the present invention, it is preferable that the update program and the update program distribution list are distributed with priority given to the block management nodes having a large number of nodes that meet the update conditions.

  Further, as in claim 10, the program update of the wireless ad hoc network terminal by the distributed update program is preferably performed with the node on the end side preceding, and the network management terminal or the update program as in claim 11. After it is confirmed that all terminals belonging to the network have been updated, it is preferable to discard the update program distribution list stored in each terminal.

  A wireless ad hoc network terminal according to a twelfth aspect of the present invention includes a network management terminal that manages the entire network, and one or more relay function holding terminals that have a relay function that relays data to other terminals connected to the network. In a wireless ad hoc network composed of a plurality of terminals and having a parent-child relationship between the terminals, a terminal holding an update program is connected to the wireless ad hoc network, network information is acquired from the network management terminal, and the network information An update program distribution list including a distribution order and a distribution route based on the update program distribution list is created, and the update program is distributed to at least one of the plurality of terminals according to the update program distribution list. Update the program with the distributed update program The program is updated by the program update method characterized by the above.

  According to the first aspect of the present invention, when the terminal holding the update program is connected to the wireless ad hoc network, the terminal holding the update program acquires network information from the network management terminal of the wireless ad hoc network, and sets the distribution order and distribution route. An update program distribution list is created, and the update program is distributed to one or more of a plurality of terminals constituting the wireless ad hoc network according to the update program distribution list. The program is updated by the program. For this reason, it is not necessary to connect with a server for managing programs and a base station as in the prior art, and it is possible to efficiently update the program of each terminal constituting the wireless ad hoc network.

  According to the invention of claim 2, a plurality of block management nodes are set in the network, and update programs and update program distribution lists are distributed through these block management nodes. As a result, distribution of the update program in the wireless ad hoc network can be performed systematically and efficiently.

  According to the invention of claim 3, it is possible to appropriately select the block management node and distribute the update program systematically and efficiently.

  According to the invention of claim 4, the update program and the update program distribution list are distributed more quickly by distributing the update program and the update program distribution list in ascending order of the number of hops when viewed from the terminal holding the update program among the plurality of block management nodes. Distribution is possible. When the number of hops is the same, the distribution is performed by distributing the update program and the update program distribution list to the block management node in preference to other terminals belonging to the block, as in the invention of claim 5. The received block management node can start distributing the next update program and the update program distribution list, so that the time required to complete the distribution of the update program to all terminals can be shortened. When the number of hops is the same, the time required for completing the distribution of the update program to all terminals can be shortened in the inventions of claims 6 and 7 as well.

  As in the invention of claim 8, if the terminal holding the update program creates the update program distribution list based on the network information and update conditions acquired from the network management terminal, the terminal that does not need to be updated can be used. There is no waste of distributing update programs, and rational distribution of update programs becomes possible.

  As in the ninth aspect of the invention, if the update program and the update program distribution list are distributed with priority given to the block management node having a large number of nodes that meet the update condition, the update program is distributed to the terminals that need to be updated. Can be shortened.

  As in the invention of claim 10, if the update of the wireless ad hoc network terminal by the distributed update program is performed in advance by the node on the end side, the restart of the terminal necessary for installing the update program is performed. Will no longer affect other terminals.

  Further, as in claim 11, after the network management terminal or the terminal holding the update program confirms that all the terminals belonging to the network have been updated, the update program distribution list stored in each terminal is discarded. As a result, it is possible to prevent useless data from remaining in the storage device.

  According to the wireless ad hoc network terminal of claim 12, a wireless ad hoc network can be configured by simply connecting a terminal holding an update program to the wireless ad hoc network without requiring connection to a program management server or a base station. The program of each terminal to be updated can be efficiently updated.

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

(Basic Configuration) FIG. 1 is a system configuration diagram of the present invention. In addition to a large number of end terminals (end devices) ED, a network management terminal (coordinator device) CD for managing the entire network and other terminals to be connected 2 shows a state in which a relay function holding terminal (full function device) RD having a relay function for relaying data is connected to the wireless ad hoc network 10. In the present invention, the relay function holding terminal RD is arranged below the higher-level network management terminal CD, and a number of end terminals ED are arranged below the higher-level network management terminal CD, and the wireless ad hoc network 10 having a parent-child relationship between the terminals is provided. Assume that it is configured.

  Each of these network management terminal CD, relay function holding terminal RD, and end terminal ED includes a CPU 1, a ROM 2, a RAM 3, and a data input / output unit 4 for wireless communication, which are connected by a bus 5. The network information of the wireless ad hoc network 10 is stored in the ROM 2 or RAM 3 of the network management terminal CD. In the present embodiment, the update dedicated terminal EDU holding the update program is connected to the wireless ad hoc network 10 only when the program is updated. The update dedicated terminal EDU includes an input device 6 and an output device 7 in addition to the CPU 1, ROM 2, RAM 3, and data input / output unit 4, and distributes an update program according to the procedure described below.

In addition to the update dedicated terminal EDU, the terminal that holds the update program may be a network management terminal CD and a relay function holding terminal RD with an update program holding / distribution function added. In this case, the system configuration of the terminal is the same as that of the update dedicated terminal EDU.
In addition, the update operation of the program by the update method of the present invention is performed when the network terminal CD to which the update program holding / distributing function is added and the relay function holding terminal RD obtain the update program other than when the update dedicated terminal is connected to the network. It is good also as starting from the time.

  FIG. 2 is a node configuration diagram during normal operation of the wireless ad hoc network, and shows one network management terminal CD, five relay function holding terminals RD, and nine end terminals ED. When updating the program of this wireless ad hoc network, as shown in FIG. 3, the update dedicated terminal EDU is allowed to participate in the network. In the embodiment of FIG. 3, the update dedicated terminal EDU is connected to RD3, which is one of the relay function holding terminals RD. However, in the present invention, any terminal (network management terminal CD) that holds the update dedicated terminal EDU. The relay function holding terminal RD) may be connected, and for example, it may be connected to a terminal having the best wireless communication state or a short-distance terminal. It is assumed that the update dedicated terminal EDU is disconnected from the network after the distribution of the update program is completed.

  As described in claim 1, basic steps in the present invention are connection of the update dedicated terminal EDU, network information acquisition from the network management terminal, creation of an update program distribution list, and distribution of the update program. FIG. 4 shows a flow of main processing of the update dedicated terminal EDU for executing these steps, and FIG. 5 shows a subroutine for creating an update program distribution list.

(Operation of Update Dedicated Terminal EDU) Initialization (S101) is performed when the update dedicated terminal EDU is first joined to the wireless ad hoc network. This includes initialization of a participation node management list, which will be described later, and initialization of an update program distribution list. When the update process is started (S102), a new participation node management list is acquired (S103). The contents of the participating node management list are as shown in FIG. 6. The node ID of each terminal constituting the wireless ad hoc network, the node ID of the parent terminal viewed from each terminal, the device type of each terminal, and each terminal The stored program version is listed. In addition, FFFF in FIG. 6 is synonymous with “none”. This participating node management list is stored in the network management terminal CD, and is acquired by the update dedicated terminal EDU.

  When the participation node management list is acquired (S103), the update dedicated terminal EDU next sets distribution conditions (S104) as shown in FIG. 4, and creates an update program distribution list (S105). Thereafter, the update dedicated terminal EDU transmits the update program distribution list (S106) and the update program (S107), and ends when the transmission completion is confirmed (S108). However, when a different program is updated, the update program is updated. The distribution list transmission (S106) and the update program transmission (S107) are repeated. The subroutine for creating an update program distribution list (S105) is as shown in FIG. 5. First, a node with matching update conditions is searched (S201), an update priority is determined (S202), and an update program distribution list is created. Is created (S203).

(Setting of Block Management Node) In the present invention, in order to efficiently update the program, a plurality of block management nodes are set in the wireless ad hoc network, and the update dedicated terminal EDU has an update program for the block management node. An update program distribution list is distributed, and the block management node receiving the distribution transfers the received update program to another block management node and a terminal belonging to its own block, and further to the other block management node Take the procedure of transferring the update distribution list that received the distribution.

  Next, setting criteria for the block management node will be described. FIG. 8 is an explanatory diagram thereof. First, RD3 which is a parent terminal when viewed from the update dedicated terminal EDU, that is, a terminal to which the update dedicated terminal EDU is connected becomes a block management node. Further, RD2, which is the parent terminal of the block management node RD3, and further, the CD which is the parent terminal, become block management nodes. Further, there are RD1, RD4, and ED3 as child terminals of the block management node CD. Among them, those having child terminals are RD1 and RD4, and these are also set as block management nodes. The child terminals of RD4 include RD5, ED5, and ED6. Of these, RD5 having a child terminal is set as a block management node. As a result, in this embodiment, RD3, RD2, CD, RD1, RD4, and RD5 are set as block management nodes. FIG. 8 illustrates management blocks managed by each block management node.

  Therefore, the content of the update program distribution list created by the update dedicated terminal EDU is as shown in FIG. 7, for example. FIG. 7 includes a block management node ID, a block management node ID of the transfer destination from the block management node (transfer node ID), and a node ID (distribution / update node ID) of the distribution / update destination of the update program. The update program is transferred in order. The update program distribution list of FIG. 7 means the following contents.

RD3, RD2, CD, RD4, RD5, and RD1 were set as 1 block management nodes.
2. The update dedicated terminal EDU first distributes the update program distribution list and the update program to the RD 3.
3 RD3 transfers the update program distribution list and the update program to RD2 whose transfer node ID is 0200. The RD 3 updates the program of its own terminal (node ID: 0300).
4 RD2 transfers the update program distribution list and the update program to the CD whose transfer node ID is 0000. Further, the update program is transferred to ED4 whose node ID is 5004, which is a child terminal of RD2, and after updating the program, the program of the own terminal (node ID: 0200) is updated.
5 CD transfers the update program distribution list and the update program to RD4 whose forwarding node ID is 0400 and RD1 whose forwarding node ID is 0100. In addition, the update program is transferred to the ED3 whose node ID is 5003 which is a child terminal of the CD, the program is updated, and then the program of the own terminal (node ID: 0000) is updated.
6 Similarly, RD4, RD1, and RD5 sequentially transfer the update program distribution list and the update program and update the program.

  As described above, the “update program distribution list” and the “update program” are sequentially distributed to each node in the order of the update program distribution list. The order is the order of forwarding node ID → distribution / update node ID. The reason why the forwarding node ID is preceded is that further program distribution is performed after that. Also, an update program distribution list is created so that the program update of the terminal of the block management node will be the last. The reason for this is to prevent the effect of the restart of the terminal performed with the program update from affecting other terminals (child terminals).

(Distribution Order) Next, the distribution order of the update program and the update program distribution list will be described. In the update program distribution list of FIG. 7 described above, the order is RD3, RD2, CD, RD4, RD1, and RD5. As shown in FIG. 9, this is the order in which the number of hops is small (close to EDU) when viewed from the update dedicated terminal EDU. However, when the number of hops is the same, there are several options regarding the order in which the update program and the update program distribution list are distributed.

  First, FIG. 10 is a diagram showing an example in which an update program (and an update program distribution list) is distributed to the block management node in preference to other terminals belonging to its own block. In this figure, the number of hops from RD2 to ED4 and the number of hops from RD2 to CD are both 1 and the same. In this case, it is preferable to distribute the update program (and the update program distribution list) with priority given to the CD that is the block management node over the ED4. The CD that is the block management node further distributes the update program (and the update program distribution list) ahead of it, whereas the ED 4 does not need to be distributed beyond that, so by making such a selection, all terminals It is possible to shorten the time until the program update is completed.

  FIG. 11 is a diagram showing an example in which an update program and an update program distribution list are distributed with priority given to a block management node having a large number of nodes to be managed when the number of hops is the same. In this figure, the number of hops to ED3, RD4, and RD1 is the same as seen from the CD. However, since priority is given to the block management node, RD4 and RD1 are given priority first. Further, when the number of nodes to be managed for RD4 and RD1 is counted, RD4 is 6, whereas RD1 is 2. Therefore, RD4, which is a block management node with a large number of nodes, has the highest priority. It is preferable that the order is RD1 and ED3.

  FIG. 12 is a diagram showing an example in which an update program and an update program distribution list are distributed preferentially to a block management node having a large number of transfers excluding overlaps based on the block management node when the number of hops is the same. It is. Note that the number of times that a certain block management node distributes (transfers) the update program (and the update program distribution list) to one child terminal with one hop is defined as the number of transfers. In the case of FIG. 12, the number of nodes to be managed is 6 for RD4 and 5 for RD1. However, in RD4, the update program reaches all the terminals to be managed with a transfer count of four times, whereas in RD1, the number of transfers until the update program reaches all the terminals to be managed is five. For this reason, priority is given to RD1 with a small number of nodes but a large number of transfers, so that the time required to complete the program update of all terminals can be shortened.

  In this way, the distribution order can be determined in the present invention. In the case where selection is not possible in light of these criteria (in the case of the same conditions), any may be prioritized.

(Conditions for creating an update program distribution list) Next, a description will be given of a case where conditions are specified for creating an update program distribution list. FIG. 13 shows an example in which a condition that only a terminal having an older program version is updated is designated. As shown in FIG. 13, it is assumed that the program version of each terminal is registered in the participating node management list, and only the node with version 1.00 is updated here. Since only CD, ED1, RD4, RD5, ED5, ED7, and ED8 meet this condition, the update program distribution list is distributed / updated only to these nodes as shown in FIG. It has become. However, since the distribution route is the same as in FIG. 7, the block management node ID and the forwarding node ID are the same as those in FIG.

  In addition, the distribution order can be changed depending on the update distribution list creation conditions. 15 to 17 show examples in which update programs are distributed in descending order of the number of nodes to be upgraded. In this example, the update dedicated terminal EDU is connected to the CD, and the program versions of all end terminals ED are updated to 1.01. In this case, when viewed from the CD, there are RD1 and RD2 which are block management nodes, but four end terminals ED1 to ED4 are connected to RD1, and three of ED6, ED7 and ED8 are connected to RD2. End terminal ED is connected. Therefore, the CD first transfers the update program to RD1, and then transfers it to RD2. The participating node management list in this case is as shown in FIG. 16, and the update program distribution list is as shown in FIG.

(Distribution is completed) After the network management terminal or the update dedicated terminal confirms that all the terminals belonging to the network have been updated in this way, it is preferable to discard the update program distribution list stored in each terminal. . This is because the update program distribution list is unnecessary data once distribution is completed, and is deleted to prevent useless data from remaining in the storage device. As described above, the update dedicated terminal EDU is also disconnected from the network. When the terminal that holds the update program is the network management terminal CD or the relay function holding terminal RD, it is not necessary to disconnect from the network.

(Operations of other terminals) The main processing flow of the update dedicated terminal EDU has been described above. Finally, the network management terminal (coordinator device) CD, the relay function holding terminal (full function device) RD, and the end terminal (end device) ) The main processing flow of ED is shown.

  FIG. 18 is a diagram showing a main processing flow of the network management terminal CD. At the start, the buffer memory and the like are first initialized (S301), and it is determined whether or not there is a request for a participating node management list from the update dedicated terminal EDU (S302). If there is a request, the participating node management list is transmitted to the update dedicated terminal EDU (S303), and if the power is not turned off, the process returns. If there is no request for the participating node management list (if it has been requested), it is determined whether or not an update program distribution list has been received (S304), and if received, the update program distribution list is included in the list. Transfer to the designated terminal (S305). Further, it is determined whether or not an update program has been received (S306), and if received, the program is transferred / updated (S307). If none of the above conditions is met, other processing (for example, sensor data collection processing performed in the wireless ad hoc network or discard of the update program distribution list) (S308) is performed, and the power is turned off (S309). Repeat this loop until

  FIG. 19 is a diagram showing a main processing flow of the relay function holding terminal RD. At the start, the buffer memory and the like are first initialized (S401), and it is determined whether or not an update program distribution list has been received (S402). If received, the update program distribution list is designated in the list. Transfer to the terminal (S403). Also, it is determined whether or not an update program has been received (S404). If received, the program is transferred / updated (S405). If none of the above conditions is met, other processing (for example, sensor data collection processing performed in the wireless ad hoc network or discard of the update program distribution list) (S406) is performed, and the power is turned off (S407). Repeat this loop until

  FIG. 20 is a diagram showing a main processing flow of the end terminal ED. At the start, the buffer memory and the like are first initialized (S501), and it is determined whether an update program has been received (S502). If received, the program is transferred / updated (S503). If an update program has not been received, other processing (eg, sensor data collection processing performed in a wireless ad hoc network) (S504) is performed (S504), and this loop is repeated until the power is turned off (S505).

  As described above, according to the present invention, by connecting the update dedicated terminal to the wireless ad hoc network at the time of program update, it is not necessary to connect to a program management server or base station as in the past, There is an advantage that the program of each terminal constituting the wireless ad hoc network can be updated efficiently.

It is a system configuration diagram of the present invention. It is a node block diagram at the time of normal operation of a wireless ad hoc network. It is a node block diagram at the time of program update. It is a flowchart of the main process of the update exclusive terminal EDU. It is a flowchart which shows the subroutine of update program distribution list creation. It is a figure which shows the content of the participating node management list. It is a figure which shows the content of the update program distribution list. It is explanatory drawing of the setting reference | standard of a block management node. It is explanatory drawing in the case of distributing in order with few hops. FIG. 10 is an explanatory diagram in a case where an update program is distributed with priority given to a block management node over a terminal belonging to its own block when the number of hops is the same. FIG. 10 is an explanatory diagram when distributing an update program with priority given to a block management node having a large number of nodes when the number of hops is the same; FIG. 10 is an explanatory diagram in a case where an update program is distributed with priority given to a block management node having a large number of transfers when the number of hops is the same. FIG. 10 is an explanatory diagram when a condition is specified for creating an update program distribution list. It is a figure which shows the content of the update program distribution list. It is a node block diagram which shows the example which distributes an update program in order with many nodes which should be upgraded. It is a figure which shows the content of the participating node management list. It is a figure which shows the content of the update program distribution list. It is a figure which shows the main processing flow of network management terminal CD. It is a figure which shows the main process flow of the relay function holding terminal RD. It is a figure which shows the main process flow of the end terminal ED.

Explanation of symbols

1 CPU
2 ROM
3 RAM
4 Data input / output section 5 Bus 6 Input device 7 Output device

Claims (12)

A network management terminal that manages the entire network,
It is composed of a plurality of terminals including one or more relay function holding terminals equipped with a relay function for relaying data to other terminals of the connection destination,
In a wireless ad hoc network with a parent-child relationship between terminals,
Connecting a terminal holding an update program to the wireless ad hoc network, obtaining network information from the network management terminal, and creating an update program distribution list including a distribution order and a distribution route based on the network information;
Distributing an update program to at least one of the plurality of terminals according to the update program distribution list;
A program update method for a wireless ad hoc network terminal, wherein a terminal that has received a distribution of an update program updates the program using the distributed update program. The distribution route is a set of multiple block management nodes in the network.
The terminal holding the update program distributes the update program and the update program distribution list to the block management node,
The distributed block management node transfers the distributed update program to other block management nodes and terminals belonging to its own block, and further updates the distribution distribution list received by the other block management node. The program update method for a wireless ad hoc network terminal according to claim 1, wherein the program is transferred.   3. The radio according to claim 2, wherein the block management node is a parent terminal of a terminal holding the update program, a parent terminal of the block management node, and a child terminal of the block management node, further having a child terminal. Program update method for ad hoc network terminals.   3. The wireless ad hoc network according to claim 2, wherein the distribution order is to distribute the update program and the update program distribution list in the order of decreasing number of hops as viewed from the terminal holding the update program among the plurality of block management nodes. How to update terminal program.   5. The wireless ad hoc according to claim 4, wherein when the number of hops is the same, the update program and the update program distribution list are distributed to the block management node in preference to other terminals belonging to the block. Network terminal program update method.   5. The wireless ad hoc network terminal program according to claim 4, wherein when the number of hops is the same, the update program and the update program distribution list are distributed in preference to a block management node having a large number of nodes to be managed. Update method.   The update program and the update program distribution list are distributed in preference to a block management node having a large number of transfers excluding an overlap portion based on the block management node when the number of hops is the same. 5. The program update method for a wireless ad hoc network terminal according to 4.   2. The program update method for a wireless ad hoc network terminal according to claim 1, wherein the terminal holding the update program creates an update program distribution list based on network information and update conditions acquired from the network management terminal.   9. The program update method for a wireless ad hoc network terminal according to claim 8, wherein the distribution order is to distribute the update program and the update program distribution list in preference to a block management node having a large number of nodes that meet the update condition.   2. The program update method for a wireless ad hoc network terminal according to claim 1, wherein the program update of the wireless ad hoc network terminal by the distributed update program is performed in advance of a terminal node.   2. The update program distribution list stored in each terminal is discarded after the network management terminal or the terminal holding the update program confirms that all the terminals belonging to the network have been updated. The program update method of the radio | wireless ad hoc network terminal of description. A network management terminal that manages the entire network,
It is composed of a plurality of terminals including one or more relay function holding terminals equipped with a relay function for relaying data to other terminals of the connection destination,
In a wireless ad hoc network with a parent-child relationship between terminals,
Connecting a terminal holding an update program to the wireless ad hoc network, obtaining network information from the network management terminal, and creating an update program distribution list including a distribution order and a distribution route based on the network information;
Distributing an update program to at least one of the plurality of terminals according to the update program distribution list,
A wireless ad hoc network terminal that updates a program by a program update method, wherein a terminal that has received the distribution of the update program updates the program using the distributed update program.

Images