WO2012063324A1

WO2012063324A1 - Communication network system, terminal, and constituting method

Info

Publication number: WO2012063324A1
Application number: PCT/JP2010/069949
Authority: WO
Inventors: 原田　諭; 和也門田; 悠一五十嵐; 芳樹松浦; 義則望月; 小泉　稔
Original assignee: 株式会社日立製作所
Priority date: 2010-11-09
Filing date: 2010-11-09
Publication date: 2012-05-18
Also published as: JP5576497B2; JPWO2012063324A1

Abstract

A communication network system comprises: a first network having a first relay device; a second network having a second relay device; a first terminal which transmits a connection request to the first network; and a second terminal which is connected to the first network and can be connected to the second network. The communication network system further comprises a third terminal which is connected to the first network; in response to the reception of a connection request from the first terminal, when the remaining number of first connectable terminals to the first network is 0, inquires whether or not the second terminal can change its connection destination to the second network; and if the second terminal can change its connection destination to the second network, connects the first terminal to the first network.

Description

Communication network system, terminal, and configuration method

The present invention relates to a communication network system, terminals constituting the communication network system, and a communication network configuration method.

Regarding the construction of a communication network system, Patent Document 1 describes that “each communication terminal means can be reliably and efficiently connected to a repeater having a substantially even load balance”. Further, Patent Document 2 describes that “even if there are many wireless communication devices in the vicinity, it is possible to suppress generation of useless communication protocols between wireless communication devices”.

JP 2001-256157 A JP 2009-218811 A

In an automatic meter reading system in a smart grid (next-generation power network), it is necessary to construct a highly reliable network to collect data used for billing. In particular, when collecting data, it is required to reliably collect the amount of data determined for each terminal. This limits the number of terminals that can be connected to the network according to the communication speed. The construction of a network that considers restrictions is an issue. Further, since periodic data collection is required, there is a problem that a network must be quickly rebuilt when a change occurs in the network topology.

In Patent Document 1, when a repeater breaks down, it is possible to quickly rebuild a network. However, when a terminal or a repeater is newly installed, connection information to the repeaters of all terminals needs to be collected again and reconstructed. There is a problem that the network cannot be rebuilt.

In Patent Document 2, when a newly installed terminal can detect a plurality of networks as connection destinations, a network can be constructed so as to further improve the communication speed of the entire network. However, when a plurality of networks cannot be detected, such as when a new terminal is installed near a repeater, the communication band will be shared among all the terminals under the network, so a network construction that takes into account the restriction on the number of connected terminals There is a problem that is difficult.

A disclosed communication network system includes a first network including a first repeater, a second network including a second repeater, and a first terminal that transmits a connection request to the first network. There is a second terminal that connects to the first network and can also connect to the second network. Further, when the first terminal remaining in the first network is 0 in response to the connection request from the first terminal connected to the first network, the second terminal Inquiry about whether or not the connection destination to the second network can be changed, and a third terminal for connecting the first terminal is provided according to whether or not the second terminal can be changed to the second network.

In another preferred aspect of the communication network system, the first network has a first repeater as a root node, and the third terminal is connected to the first repeater closer to the first repeater than the second terminal. Configure the topology.

In a communication network system according to still another desirable aspect, the third terminal is connected to the first repeater closer to the first repeater than the third terminal in response to the second terminal's connection destination change refusal to the second network. If there is no such other terminal, the connection request from the first terminal is transmitted to the first repeater.

In a communication network system according to still another desirable aspect, in response to a connection destination change refusal to the first network from the first repeater receiving the connection request from the first terminal, the third terminal Wait for the first terminal to connect to the first network.

In a communication network system according to still another desirable aspect, the third terminal connects to the second network via the second terminal in response to the first repeater leaving the first network.

The communication network system according to still another preferred aspect responds to reception of a connection destination repeater change request including the third number of remaining accommodated terminals of the third network from the third repeater configuring the third network. Then, the third terminal is connected to one of the first network and the third network corresponding to the larger one of the first number of remaining accommodated terminals and the third number of remaining accommodated terminals.

When there is a change in the network topology, it is possible to construct a network within the limit on the number of terminals that can be connected to the network.

It is a figure which illustrates the topology in case a terminal connects with the some network which can be selected. It is a hardware block diagram of a terminal. It is a hardware block diagram of a repeater. It is a hardware block diagram of a data collection server. It is a hardware block diagram of a management server. It is a functional block diagram of a terminal. It is a functional block diagram of a repeater. It is a functional block diagram of a data collection server. It is a functional block diagram of a management server. It is a block diagram of an adjacent terminal management table. It is a block diagram of a topology management table. It is a block diagram of an emergency topology management table. It is a block diagram of a network management table. It is a block diagram of a standby terminal management table. It is a connection sequence diagram to the network of the terminal. It is a flowchart of a channel scan process. It is a figure which illustrates the topology in case a terminal cannot connect to the selected network but connects to another network. It is a figure which illustrates the connection sequence in case a terminal cannot connect to the selected network but connects to another network. It is a figure which illustrates the connection sequence in case a terminal cannot connect to the selected network but connects to another network. It is a figure which illustrates topology when a terminal cannot connect to a selected network, and cannot connect to other networks. It is a figure which illustrates the sequence which tries a connection when a terminal cannot connect to the selected network and cannot connect to another network. It is a figure which illustrates topology when a terminal leaves | separates from a network. It is a figure which illustrates the sequence which a terminal leaves | separates from a network. It is a flowchart of a connection request reception process. It is a flowchart of the connection request reception process in a repeater. It is a flowchart of a connection destination change examination process. It is a figure which illustrates the topology when a repeater leaves | separates. It is a figure which illustrates a network reconstruction sequence when a repeater leaves | separates. It is a figure which illustrates a network reconstruction sequence when a repeater leaves | separates. It is a figure which illustrates a network reconstruction sequence when a repeater leaves | separates. It is a figure which illustrates the sequence which the disconnected repeater reconnects. It is a figure which illustrates the topology in case a repeater is newly installed. It is a figure which illustrates the network reconstruction sequence at the time of repeater installation. It is a figure which illustrates the network reconstruction sequence at the time of repeater installation.

The communication network system of the present embodiment includes a first network including a first repeater and a second network including a second repeater, and transmits a connection request to the first network. There is a terminal, a second terminal that connects to the first network and is also connectable to the second network. Further, when the first terminal remaining in the first network is 0 in response to the connection request from the first terminal connected to the first network, the second terminal Inquiry about whether or not the connection destination to the second network can be changed, and a third terminal for connecting the first terminal is provided according to whether or not the second terminal can be changed to the second network.

In the communication network system, the first network has a tree-like topology in which the first repeater is used as a root node, and the third terminal is connected to the first repeater closer to the first repeater than the second terminal. Yes.

In the communication network system, in response to refusal to change the connection destination of the second terminal to the second network, the third terminal is connected to the other terminal connected closer to the first repeater than the third terminal. If there is no such other terminal, a connection request from the first terminal is transmitted to the first repeater.

The communication network system receives the connection request from the first terminal, and in response to the change of the connection destination to the first network from the first repeater, the third terminal Wait for connection to the first network.

In the communication network system, the third terminal connects to the second network via the second terminal in response to the disconnection of the first repeater from the first network.

The communication network system responds to the reception of a connection destination repeater change request including the remaining number of third accommodated terminals of the third network from the third repeater constituting the third network, Is connected to one of the first network and the third network corresponding to the larger one of the remaining number of first accommodated terminals and the remaining number of accommodated terminals.

A communication network system, a terminal constituting the communication network, and a method for configuring the communication network are disclosed as examples. First, items common to the embodiments will be described.

FIG. 1 is a diagram illustrating a topology in a case where the terminal 130 is connected to a plurality of selectable networks according to the first embodiment described later. Specifically, in the situation where the terminal 130 is connected to the network, the connection destination network can be selected from the network under the relay 110 and the network under the relay 120. Each network is specified by each repeater connected to the data collection server 102. The terminals under the repeater constitute a tree-like network having the repeater as a root node. Another terminal connected to the repeater side when viewed from a certain terminal is called an upper terminal, and another terminal connected to the opposite side of the repeater is called a lower terminal. The data collection server 102 is connected to the management server 100 as shown.

FIG. 2A shows a hardware configuration diagram of the terminal, and FIG. 3A shows a functional configuration diagram of the terminal. As shown in FIG. 2A, the terminal is a terminal equipped with a CPU (Central Processing Unit) 200, a volatile memory 202, a storage device 204, and a communication interface 206, and corresponds to a smart meter, a sensor, or the like. The storage device 204 is a storage medium such as a hard disk or a nonvolatile memory, and includes an adjacent terminal management table 300, a topology management table 302, and an emergency topology management table 304 as shown in FIG. 3A. The configurations of the adjacent terminal management table 300, the topology management table 302, and the emergency topology management table 304 are shown in FIGS. 4A to 4C. Note that the terminal is shown in FIG. 3A so as to have the emergency topology management table 304, and FIG. 4C is also described, but this is not used in this embodiment, but is used in embodiment 2 described later.

The adjacent terminal management table 300 shown in FIG. 4A is a table that records information about terminals (neighboring terminals: upper terminal and lower terminal) that exist in the vicinity and can be directly communicated, and includes a channel number 400, a terminal ID 402, a repeater It consists of an ID 404, a data collection server ID 406, and an accommodation remaining number 408. The channel number 400 is set with an ID (Identification) that is defined corresponding to the network specified by the repeater and uniquely identifies a communication channel used by a terminal connected to the network. In the terminal ID 402, an ID that uniquely identifies an adjacent terminal such as an IP (Internet Protocol) address is set. In the repeater ID 404, an ID such as an IP address that uniquely identifies the repeater of the network to which the adjacent terminal belongs is set. The data collection server ID 406 is set with an ID such as an IP address that uniquely identifies the data collection server to which the network repeater to which the adjacent terminal belongs is connected. In the remaining accommodation number 408, the remaining number of terminals that can be connected to the network under the relay is set.

The topology management table 302 shown in FIG. 4B includes the relay ID 410 that identifies the network to which the terminal belongs, the ID 412 of the upper terminal connected to the own terminal, the ID 414 of the lower terminal connected to the own terminal, and the own terminal. It consists of the number of connected terminals 416 connected to the network. The repeater ID 410 is the same as the repeater ID 404 of the adjacent terminal management table 300 for each terminal.

The configuration of the emergency topology management table 304 shown in FIG. 4C is the same as that of the topology management table 302, and includes a repeater ID 420, an upper terminal ID 422, a lower terminal ID 424, and the number of connected terminals 426.

3A, the terminal includes a communication unit 306, a channel scan unit 308, a transmission packet generation unit 310, a reception packet analysis unit 312, a packet relay unit 314, and a table update unit 316. The communication unit 306 communicates directly or indirectly with each terminal, repeater, and data collection server through the communication interface 206. The terminal ID 402, the repeater ID 404, the data collection server ID 406, and the remaining number 408 are transmitted and received by direct communication with the adjacent terminal. The channel scanning unit 308 detects a channel used for communication in the vicinity through the communication interface 206, and detects an adjacent terminal that can communicate with the channel. The transmission packet generation unit 310 generates a control packet such as a connection request through the communication interface 206 when the terminal connects to the network or leaves the network in addition to the generation and transmission of a normal data packet. Send. The received packet analysis unit 312 analyzes the type of packet received through the communication interface 206 and extracts data and control data included in the packet. When the data packet received through the communication interface 206 is not a packet addressed to the own terminal, the packet relay unit 314 relays the packet to the next adjacent terminal so as to approach the regular destination. The table updating unit 316 updates the values of various tables based on the data extracted by the received packet analysis unit 312. In this embodiment, a table such as the adjacent terminal management table 300 is updated based on the control data.

FIG. 2B shows a hardware configuration diagram of the repeater, and FIG. 3B shows a functional configuration diagram of the repeater. As shown in FIG. 2B, the repeater is a terminal equipped with a CPU 210, a volatile memory 212, a storage device 214, and a communication interface 216, and corresponds to a gateway or the like. The storage device 214 is a storage medium such as a hard disk or a nonvolatile memory, and includes a topology management table 302 and a network management table 320 similar to those of the terminal, as shown in FIG. 3B. The configuration of the network management table 320 is shown in FIG. 4D.

The network management table 320 shown in FIG. 4D is a table for managing the number of terminals accommodated in the network under the relay, and includes the maximum accommodated terminal number 430, the accommodated terminal number 432, and the accommodated remaining number 434. In the maximum accommodated terminal number 430, the maximum value of the number of terminals connectable to the network under the repeater calculated from the performance of the CPU mounted on the repeater, the communication medium, and the like is set. In the number of accommodated terminals 432, the number of terminals connected to the network under the relay is set. A value obtained by subtracting the number of accommodated terminals 432 from the maximum accommodated terminal number 430 is set in the accommodated remaining number 434.

As shown in FIG. 3B, the repeater includes a communication unit 322, a channel scan unit 324, a transmission packet generation unit 326, a received packet analysis unit 328, a packet relay unit 330, and a table update unit 332. The communication unit 322 transmits / receives the terminal ID 402, the relay ID 404, the data collection server ID 406, and the accommodation remaining number 408 by communicating with each terminal and other relays through the communication interface 216. The channel scanning unit 308 detects a channel used for communication in the vicinity through the communication interface 216. The transmission packet generator 326 transmits a connection request or the like through the communication interface 216 when the repeater connects to the network or leaves the network. The received packet analysis unit 328 analyzes the type of packet received through the communication interface 216 and extracts data included in the packet. When the packet received through the communication interface 216 is not a packet addressed to the own relay device, the packet relay unit 330 relays the packet to the next relay device or terminal so as to approach the regular destination. The network management table update unit 332 updates the value of the network management table 320 based on the data extracted from the received packet by the received packet analysis unit 328.

FIG. 2C shows a hardware configuration diagram of the data collection server, and FIG. 3C shows a functional configuration diagram of the data collection server. As shown in FIG. 2C, the data collection server is an information processing apparatus including a CPU 220, a volatile memory 222, a storage device 224, and a communication interface 226, and corresponds to a database server that manages data uploaded from a terminal. . The storage device 224 is a storage medium such as a hard disk or a nonvolatile memory.

As illustrated in FIG. 3C, the data collection server includes a communication unit 340, a transmission packet generation unit 342, a reception packet analysis unit 344, and a packet relay unit 346. The communication unit 340 transmits and receives the ID of the data collection server and the ID of the standby terminal by communicating with each repeater and the management server through the communication interface 226. The transmission packet generation unit 342 transmits the ID of the data collection server through the communication interface 226. The received packet analysis unit 344 analyzes the type of packet received through the communication interface 226 and extracts data included in the packet. When the packet received through the communication interface 226 is not a packet addressed to the own terminal, the packet relay unit 346 relays the packet to the management server or the relay device so as to approach the regular destination.

FIG. 2D shows a hardware configuration diagram of the management server, and FIG. 3D shows a functional configuration diagram of the management server. As shown in FIG. 2D, the management server is an information processing apparatus including a CPU 230, a volatile memory 232, a storage device 234, a communication interface 236, and a screen display unit 238, and corresponds to an application server or the like. The storage device 234 is a storage medium such as a hard disk or a nonvolatile memory, and includes a standby terminal management table 360 as shown in FIG. 3D. The configuration of standby terminal management table 360 is shown in FIG. 4E.

The standby terminal management table 360 shown in FIG. 4E is a table for managing information related to terminals that could not be connected to the network, and includes a standby terminal ID 440, a repeater ID 442, and a data collection server ID 444. The standby terminal ID 440 is set with the ID of a terminal that could not be connected to the network. In the repeater ID 442, the ID of the repeater to which the terminal that cannot be connected to the network belongs is set. The data collection server ID 444 is set with the ID of the data collection server to which the terminal that cannot be connected to the network belongs.

3D, the management server includes a communication unit 362, a transmission packet generation unit 364, a reception packet analysis unit 366, a packet relay unit 368, and a standby terminal management table update unit 370. The communication unit 362 communicates with the data collection server through the communication interface 236, thereby transmitting and receiving the management server ID, the data collection server ID, and the like. The transmission packet generation unit 364 transmits the management server ID and the like through the communication interface 236. The received packet analyzer 366 analyzes the type of packet received through the communication interface 236 and extracts data contained in the packet. The terminal status display unit 368 displays information on the standby terminal through the screen display unit 238 by a method provided by the management server. Standby terminal management table update unit 370 updates the value of standby terminal management table 360 based on the data extracted by received packet analysis unit 366.

The operation in the above configuration will be described with reference to the following examples.

In the present embodiment, an example of a sequence when a newly installed terminal connects to the network and a sequence when the terminal leaves the network will be described.

FIG. 1 is a diagram illustrating a topology in the case where the terminal 130 is connected to a plurality of selectable networks as described above. Specifically, in the situation where the terminal 130 is connected to the network, the connection destination network can be selected from the network under the relay 110 and the network under the relay 120.

FIG. 5 is a diagram showing a sequence when the terminal 130 shown in FIG. 1 connects to the network under the relay 110. The same applies to a sequence diagram to be described later, but the side-by-side steps by a plurality of terminals or the like are for convenience of illustration and do not indicate that they are synchronized in time.

When the terminal 130 is connected to the network, it executes a channel scan process (step 500). A flowchart of the channel scan process is shown in FIG. The terminal 130 sets “1” in the variable i and scans for the presence of a peripheral terminal that performs communication using the first channel (steps 600 to 604). When the terminal 112 that communicates using the first channel is detected as a peripheral terminal, the terminal 130 receives from the terminal 112 the ID of the terminal 112, the ID of the repeater 110 of the network to which the terminal 112 is connected, and data collection. The server 102 receives the ID of the server 102 and the remaining capacity of the repeater 110 (steps 606 and 608). In response to the scan from the terminal 130, the terminal 112 transmits the ID of the repeater 110 registered in its own adjacent terminal management table 300 together with its own ID (the ID of the terminal 112). The terminal 130 that has received the ID of the data collection server 102 determines whether the data collection server 102 is a data collection server that can be selected as a connection destination, and the channel number 400 of the adjacent terminal management table 300 is “1”. Register the ID of the terminal 112 in the ID 402, the ID of the relay 110 in the relay ID 404, the ID of the data collection server 102 in the data collection server ID 406, and the remaining number received from the terminal 112 in the remaining number 408 (step 610, step 612). If no other terminal using the first channel is detected, “1” is added to the variable i (step 614). When the peripheral terminal 124 that uses the second channel is detected, the adjacent terminal management table 300 and the variable i are updated in the same procedure as when the peripheral terminal 112 is detected (steps 602 to 614). In all the channels used in the system, after confirming whether there is a peripheral terminal using the channel, the channel scanning process is terminated (step 602).

The terminal 130 that has finished the channel scanning process refers to the adjacent terminal management table 300, and the number of terminals connected to the terminal 112, which is a peripheral terminal belonging to the network having the largest value of the remaining capacity 408, is “1”. And a connection request packet including the terminal 130 ID as the terminal ID (hereinafter referred to as simply transmitting a connection request for transmission to a control packet such as a connection request. (Including the ID of the terminal of the transmission source of the control packet) (step 502).

The terminal 112 that has received the connection request executes a connection request reception process and transmits a connection permission to the terminal 130 (steps 504 to 508). Details of the connection request reception process will be described later. The terminal 112 that transmitted the connection permission registers the ID of the terminal 130 that is the transmission source of the connection request in the lower terminal ID 414 of its own topology management table 302 (step 510).

The terminal 130 that has received the connection permission registers the terminal 112 that is the transmission source of the connection permission in the upper terminal ID 422 of its own topology management table 302, and includes a connection that includes information that the number of terminals to be connected is “1”. A notification is transmitted to the terminal 112 (steps 512 to 516).

The terminal 130 that has received the connection notification adds “1” to the number of connected terminals 416 in the topology management table 302 and relays the connection notification to the repeater 110 (steps 518 to 522).

The repeater 110 that has received the connection notification adds “1” to the number of accommodated terminals 432 in the network management table 320 and subtracts “1” from the accommodated remaining number 434 (steps 524 and 526). The value of the remaining capacity 434 after the update is distributed to all terminals connected to the network under the relay 110 (step 528).

The terminal 112 that has received the remaining number of accommodations updates the remaining number of accommodations 408 in the adjacent terminal management table 300 and transmits the remaining number of accommodations to the terminal 130 that is a lower terminal (steps 530 to 534).

The terminal 130 updates (sets) the received accommodation remaining number in the accommodation remaining number 408 of the adjacent terminal management table 300 (steps 536 and 538).

FIG. 7 is a diagram illustrating a topology when a terminal cannot connect to a selected network but connects to another network. Specifically, in the situation where terminal 730 is connected to the network, it is a diagram illustrating a topology in the case where the remaining number of accommodation of relay 700 is “0”. FIGS. 8 and 9 are diagrams illustrating a sequence when the terminal 730 cannot connect to the network under the relay 700 in the situation of FIG. 7 and connects to the network under the relay 710.

After executing the channel scan process, the terminal 700 transmits a connection request to the terminal 706 (Step 800, Step 802).

The terminal 706 that has received the connection request executes a connection request reception process, and transmits a connection destination change request to the terminal 708, which is a lower terminal, because the remaining number of accommodation is “0” (steps 804 to 808). . Details of the connection request reception process will be described later.

The terminal 708 that has received the connection destination change request executes a connection destination change examination process and sends a connection destination change rejection (here, it is assumed that the connection destination cannot be changed) to the transmission source of the connection destination change request. Is transmitted to the terminal 706 (steps 810 to 814). Details of the connection destination change examination process will be described later.

The terminal 706 that has received the connection destination change refusal executes the connection request accepting process, and the connection destination change approval has not been obtained from the lower terminal registered in the topology management table 302. A connection destination change request is transmitted (steps 816 to 820). Details of the connection request reception process will be described later.

The terminal 702 that has received the connection destination change request executes the connection destination change examination process, and transmits the connection destination change request to the terminal 704, which is a lower terminal (steps 822 to 826). Details of the connection request reception process will be described later.

The terminal 704 that has received the connection destination change request executes the connection destination change examination process and can communicate with the terminal 712 belonging to the network under the relay 710 (assuming that the terminal 708 cannot change the connection destination, the terminal 704 Will be described on the assumption that the connection can be changed to the terminal 712 belonging to the network under the relay 710.), and the connection destination change approval including the information regarding the terminal 712 registered in the adjacent terminal management table 300 is transmitted to the terminal 702. (Steps 828 to 832). Details of the connection destination change examination process will be described later. If the terminal 704 cannot change the connection, the terminal 704 follows a sequence for transmitting a connection destination change rejection, which will be described later with reference to FIG.

The terminal 702 that has received the connection destination change approval transmits the connection destination change approval to the terminal 706 that is the transmission source of the connection destination change request (steps 834 and 836). The terminal 702 deletes the terminal 712 from the lower terminal ID 414 of the topology management table 302 and subtracts “1” from the number of connected terminals 416 (step 838). The example of FIG. 4B shows the case where there is one lower terminal, but when there are a plurality of lower terminals, the lower terminal ID 414 column is set to a plurality of lower terminals. The terminal 702 has information related to the terminal 712 received from the terminal 704 (the terminal 704 has information related to the terminal 712 connected to the network under the relay 710 in its adjacent terminal management table 300). Based on this, the channel number 400, the relay ID 404, the data collection server ID 406, and the remaining capacity 408 relating to the terminal 704 in the adjacent terminal management table 300 are updated (step 840). The accommodated remaining number 408 corresponds to the channel number 400 related to the terminal 704 and is a value obtained by subtracting “1” from the accommodated remaining number of the network under the repeater 710 included in the information related to the terminal 712, and the channel number related to the terminal 706 Corresponding to 400, “0” is updated to “1”.

The terminal 706 that has received the connection destination change approval transmits a connection permission to the terminal 730, and registers the terminal 730 that is the transmission source of the connection request in the lower terminal ID 414 of the topology management table 302 (steps 842 to 846).

The terminal 730 that has received the connection permission registers the terminal 706 that is the connection permission transmission source in the upper terminal ID 422 of the topology management table 302, and sends a connection notification including information that the number of connected terminals is “1”. The data is transmitted to the terminal 706 (steps 848 to 900).

Thereafter, similarly to the sequence shown in FIG. 5, the connection notification is relayed to the repeater 700, and the topology management table 302 of each terminal is updated, and the accommodation remaining number is distributed from the repeater 700 to the entire network. (Steps 902 to 942).

FIG. 10 is a diagram illustrating a topology when the terminal cannot connect to the selected network and cannot connect to other networks. Specifically, in a situation where the terminal 730 is connected to the network, the remaining number of the repeaters 700 is “0”, the terminal 708 refuses to change the connection destination, and the terminal 704 cannot communicate with the terminal 712. It is a figure which illustrates the topology in the case of (rejecting a connection destination change). FIG. 11 is a diagram showing a sequence when the terminal 730 tries to connect to the network under the relay 700 in the situation of FIG. Since the process until the terminal 704 receives the connection destination change request is the same as the sequence in FIG. 8, the subsequent sequence will be described below.

The terminal 704 that has received the connection destination change request executes a connection destination change examination process, and transmits a connection destination change rejection to the terminal 702 that is the transmission source of the connection destination change request (steps 1100 to 1104). Details of the connection destination change examination process will be described later.

The terminal 702 that has received the connection destination change refusal executes the connection request acceptance process, and the connection destination change approval has not been obtained from the lower terminal registered in the topology management table 302. The connection destination change request is transmitted to (step 1106 to step 1110). Details of the connection request reception process will be described later.

The repeater 700 that has received the connection destination change request executes connection request reception processing, and transmission of the connection destination change request has not been obtained from the lower terminal registered in the topology management table 302. A connection rejection is transmitted to the original terminal 702 (step 1112 to step 1116). Details of the connection request reception process in the repeater will be described later.

The terminal 702 that has received the connection refusal transmits a connection refusal to the terminal 706 that is the transmission source of the connection destination change request (steps 1118 and 1120).

The terminal 706 that has received the connection refusal transmits a connection refusal to the terminal 730 that is the source of the connection request (steps 1122 and 1124).

The terminal 730 that has received the connection refusal transmits a standby notification to the terminal 706 and waits (steps 1126 to 1130).

The terminal 706 that has received the standby notification transmits a standby notification to the terminal 702 that is a higher-level terminal (steps 1132 and 1134).

The terminal 702 that has received the standby notification transmits a standby notification to the repeater 700 (steps 1136 and 1138).

The repeater 700 that has received the standby notification transmits a standby notification to the data collection server 102 (steps 1140 and 1142).

The data collection server 102 that has received the standby notification transmits a standby notification to the management server 100 (steps 1144 and 1146).

The management server 100 that has received the standby notification includes the ID of the terminal 730 that issued the standby notification, the ID of the repeater 700 of the network to which the terminal 730 belongs, and the management server 100 included in the control packet indicating the received standby notification. The ID of the data collection server 102 that transmitted the standby notification to the standby terminal management table 360 is registered in the standby terminal ID 440, the repeater ID 442, and the data collection server ID 444, respectively. The management server 100 further displays the ID of the terminal 730 that is the transmission source of the standby notification on the screen display unit 238 (steps 1148 and 1150).

Note that the waiting terminal 730 transmits a connection request to the terminal 706 at a predetermined cycle (corresponding to step 502 in FIG. 5). If the connection is established, the repeater 700 notifies the management server 100 via the data collection server 102 that the terminal 706 has been connected to the network (at the timing of step 524 to step 528 in FIG. 5). The server 100 clears the standby terminal management table 360, and the standby state of the terminal 730 is canceled.

FIG. 12 is a diagram illustrating a topology when the terminal 1204 leaves the network under the repeater 1200. FIG. 13 is a diagram showing a sequence when the terminal 1204 leaves the network under the relay 1200 in the situation of FIG.

The terminal 1204 leaving the network transmits a network disconnection notification to the terminal 1206 and the terminal 1202 (step 1300).

The terminal 1206 that has received the network disconnection notification deletes information related to the terminal 1204 from the topology management table 302 and the adjacent terminal management table 300, and executes the initial connection sequence shown in FIG. 5 (steps 1302 to 1306). ).

The terminal 1202 that has received the network disconnection notification deletes information related to the terminal 1204 from the topology management table 302 and the adjacent terminal management table 300, and transmits a network disconnection notification to the repeater 1200 (steps 1308 to 1314).

The repeater 1200 that has received the network disconnection notification subtracts “2” from the number of accommodated terminals 432 in the network management table 320 and adds “2” to the remaining accommodated number 434 (steps 1316 and 1318). The updated remaining capacity 434 is transmitted to all terminals under the repeater 1200 (step 1320).

The terminal 1202 and the terminal 1208 that have received the remaining number of accommodations update the remaining number of accommodations 408 in the adjacent terminal management table 300 (steps 1322 to 1328).

FIG. 14 shows a flowchart of the connection request reception process. When a connection request is received, it is determined by referring to the adjacent terminal management table 300 whether the number of remaining networks in the network to which the terminal is connected is greater than “0” (steps 1400 and 1402). If the remaining capacity is greater than “0”, a connection permission is transmitted to the terminal that has transmitted the connection request (step 1404). Further, when the remaining number of accommodation is “0”, or when a connection destination change request and a connection destination change refusal are received, the lower terminal ID 414 of the topology management table 302 is referred to and registered there. A connection destination change request is transmitted to the terminal (steps 1406 to 1410). If connection destination change approval is not obtained even if the connection destination change request is transmitted to all terminals registered in the lower terminal ID 414, the connection destination is changed to the terminal registered in the upper terminal 412 of the topology management table 302. A request is transmitted (step 1412).

FIG. 15 shows a flowchart of connection request reception processing in the repeater. Steps 1400 to 1410 of the terminal connection destination request reception process shown in FIG. 14 are the same, and therefore, step 1512 different from the terminal connection destination request reception process will be described here. If the repeater transmits a connection destination change request to all the lower-level terminals and the connection destination change approval is not obtained, a connection rejection is transmitted to the terminal that has transmitted the connection request (step 1512).

FIG. 16 shows a flowchart of the connection destination change examination process. First, the terminal that has received the connection destination change request refers to the adjacent terminal management table 300, and there is a terminal that is connected to a network under another relay different from the network under the currently connected relay. (Step 1600, step 1602). If there is a terminal connected to the network under another relay, send a connection destination change approval to the terminal that sent the connection destination change request to the terminal connected to the network under the other relay. The connection request is transmitted (steps 1604 and 1606). If no terminal connected to another repeater is registered in the adjacent terminal management table, a connection refusal is transmitted to the terminal that has transmitted the connection destination change request (step 1608).

In the present embodiment, an example of a network construction method when a repeater is temporarily disconnected due to a failure or the like, and a network construction method when the repeater returns from a failure and reconnects will be described.

FIG. 17 is a diagram illustrating a topology when the repeater 700 is temporarily disconnected due to a failure or the like. 18, 19, and 20 are diagrams showing a sequence when the network is reconstructed when the repeater 700 is disconnected due to a failure or the like in the situation of FIG.

The terminal 702 that has detected the failure of the repeater 700 for a certain period (for example, 30 seconds) due to the reason that communication cannot be performed refers to the topology management table 302 and requests the other repeater connection status report to the terminal 704 that is a lower order terminal. Is transmitted (step 1800, step 1802).

The terminal 704 that has received the request for reporting other relay connection status refers to the adjacent terminal management table 300 and confirms whether a terminal connected to a relay different from the failed relay 700 is registered. The repeater connection status is transmitted to notify that there is no terminal connected to the repeater (steps 1804 to 1808).

The terminal 702 that has received the other relay connection status transmits the other relay connection status report request to the terminal 706, which is a lower level terminal, in the same manner as in Step 1802 (Step 1810, Step 1812). The terminal 702 may execute Step 1812 in parallel with Step 1802.

The terminal 706 that has received the other relay connection status report request refers to the adjacent terminal management table 300 and confirms whether a terminal connected to a relay different from the failed relay 700 is registered (step 1814). Step 1816). The terminal 706 transmits an accommodation remaining number report request to the terminal 712 connected to the other repeater 710 (step 1818).

The terminal 712 that has received the remaining capacity report request transmits a remaining capacity report to the terminal 706 with reference to the adjacent terminal management table 300 (steps 1820 and 1822).

The terminal 706 that has received the accommodation remaining number report transmits the other relay connection status including the content of the accommodation remaining number report to the terminal 702 (steps 1824 and 1826).

The terminal 702 that has received the connection status of the other repeater compares the accommodated remaining number included in the other repeater connection status received from the lower-level terminal, and connects to the terminal that can be connected to the repeater having the largest accommodated remaining value. The destination repeater change is transmitted (steps 1828 to 1902). The change of the connection destination repeater to be transmitted includes contents for changing the connection destinations of the three terminals of the terminal 702, the terminal 704, and the terminal 706. Here, since the other relay connection status including the content of the remaining capacity report is only from the terminal 706 that is the lower terminal, the terminal 706 is selected as a terminal that can be connected to the relay with the largest remaining capacity value. However, if other repeater connection status including the content of the remaining capacity report is received from a plurality of lower terminals, it is connected to the terminal that can be connected to the repeater with the largest remaining capacity value. Submit changes.

The terminal 706 that has received the connection destination repeater change transmits a connection request to the terminal 712 (steps 1904 and 1906).

The terminal 712 that has received the connection request transmits a connection permission to the terminal 706 after executing the connection request receiving process (steps 1908 to 1912). The terminal 712 registers the terminal 706 that is the source of the connection request in the lower terminal ID 414 of the topology management table 302 (step 1914).

The terminal 706 that has received the connection permission transmits a connection notification including the content that the terminal 702, the terminal 704, and the terminal 706 are newly connected to the terminal 712, and the three terminals are newly connected. The connection destination repeater change completion including the channel number of the network under the repeater 710 and the remaining number (the value obtained by subtracting 3 from the remaining number 408 of the channel whose repeater ID 404 of the adjacent terminal management table 300 is the repeater 710). Is transmitted to the terminal 702 (steps 1916 to 1920). In order to manage that the topology change in this sequence is temporary, the terminal 706 registers the terminal 712 in the upper terminal ID 422 of the emergency topology management table 304 and registers the terminal 702 in the lower terminal ID 424. (Step 1922). In addition, the terminal 706 updates (−3) the remaining number of accommodated channels 408 in which the relay ID 404 of the adjacent terminal management table 300 is the relay 710 (step 1924).

The terminal 702 that has received the connection destination repeater change completion transmits a channel change notification including the content of the connection destination repeater change completion to the terminal 704 that is a lower order terminal (steps 1926 and 1928). After changing the channel to be used, the terminal 702 registers the ID of the terminal 706 in the upper terminal ID 422 of the emergency topology management table 304 and updates the number of connected terminals 426 (steps 1930 and 1932). Further, the terminal 702 updates the channel number 400, the repeater ID 404, and the remaining capacity 408 in the adjacent terminal management table 300 based on the received content of the connection destination repeater change completion (step 1934).

The terminal 704 that has received the channel change notification changes the channel to be used, and updates the channel number 400, the repeater ID 404, and the remaining capacity 408 in the adjacent terminal management table 300 based on the content of the channel change notification ( Step 1936 to Step 1940).

The terminal 712 that has received the connection notification updates the lower terminal ID 414 and the number of connected terminals 416 in the topology management table 302 from 0 to 3, and transmits the connection notification to the repeater 710 (steps 1942 to 1946).

The repeater 710 that has received the connection notification distributes the remaining number of accommodations from the repeater 710 to the entire network in the same manner as step 524 and subsequent steps in the sequence shown in FIG. 2022,).

FIG. 21 is a diagram showing a sequence when the repeater 700 disconnected due to a failure or the like is restored and reconnected in the situation of FIG.

The terminal 702 that has detected the recovery of the repeater 700 by receiving a beacon transmitted from the repeater 700 transmits a reconnection request to the repeater 700 (steps 2100 and 2102).

The repeater 700 that has received the reconnection request recognizes that the terminal 702 has been previously connected to the repeater 700 by referring to the network management table 320 stored in the nonvolatile storage device 214. The reconnection approval is transmitted to the terminal 702 (steps 2104 to 2108).

The terminal 702 that has received the reconnection approval request transmits a network disconnection request to the terminal 706 (step 2110 and step 2112).

The terminal 706 that has received the network disconnection request leaves the network of the repeater 710 and transmits a network disconnection completion to the terminal 702 in the same procedure as the sequence shown in FIG. 13 (steps 2114 to 2118).

Thereafter, similarly to the sequence shown in FIG. 13, the topology management table 302 of the terminal 712 and the adjacent terminal management table 300 are updated, and the accommodation remaining number is distributed from the repeater 710 that has received the network disconnection notification ( Step 2120 to Step 2136).

The terminal 702 that has received the completion of network disconnection transmits a channel change notification to the terminal 704 and the terminal 706, and transmits reconnection completion to the repeater 700 (steps 2138 to 2142).

The terminal 704 and the terminal 706 that have received the channel change notification update the channel number 400 and the repeater ID 404 in the adjacency management table 300 after changing the channel to be used (steps 2144 to 2154).

The repeater 700 that has received the connection completion distributes the remaining number of accommodation to the entire network (steps 2156 to 2174), as in step 524 and subsequent steps of the sequence shown in FIG.

In this embodiment, an example of a network construction method when a repeater is newly installed will be described. FIG. 22 is a diagram illustrating a topology when a repeater 710 is newly installed. FIG. 23 and FIG. 24 are diagrams showing a sequence when the network is reconstructed when the repeater 710 is newly installed in the situation of FIG.

The newly installed repeater 710 detects a terminal that performs communication in the vicinity by executing a channel scan process, and transmits a connection destination repeater change request including information on the remaining number of accommodation (step 2300, Step 2302).

The terminal 704 that has received the connection-destination repeater change request refers to the adjacent terminal management table 300 to determine the remaining number 408 of the network under the currently connected repeater 700 and the remaining number received from the repeater 710. In comparison, if the value of the remaining capacity received from the repeater 710 is large, a connection destination repeater change approval is transmitted to the repeater 710 (steps 2304 to 2308).

The repeater 710 having received the connection destination repeater change approval transmits the channel number used in the newly constructed network to the terminal 704 (steps 2310 and 2312).

The terminal 704 that has received the channel number transmits a network disconnection notification to the terminal 702 (steps 2314 and 2316). Also, the terminal 704 transmits the channel number to the terminal 706, changes the channel to be used, updates the channel number in the adjacent management terminal table 300, and transmits the connection destination repeater change completion to the repeater 710. (Steps 2318 to 2324).

Thereafter, similarly to the sequence shown in FIG. 13, a network disconnection notification is transmitted from the terminal 702 to the repeater 700, and the topology management table 302, the adjacent terminal management table 300 of the terminal 702, and the network management table of the repeater 700 are transmitted. Is updated, the remaining capacity is distributed to the entire network under the repeater 700 (steps 2326 to 2342).

The terminal 706 that has received the channel change notification changes the channel to be used, and then updates the channel number 400 and the relay ID 404 in the adjacent terminal management table 300 (steps 2344 to 2348).

The repeater 710 that has received the change of connection destination repeater updates the network management table 320 and transmits the remaining number of accommodations to the terminal 704 (steps 2350 to 2354).

Thereafter, similarly to step 524 and subsequent steps in the sequence shown in FIG. 5, the remaining number is distributed to the entire network under the repeater 710 (steps 2356 to 2364).

The repeater 710 that has finished distributing the remaining number of accommodations transmits a connection destination repeater change request to the terminal 704 (step 2400).

The terminal 704 that has received the connection destination repeater change request refers to the adjacent terminal management table 300 and transmits the connection destination repeater change request to the terminal 702 that is connected to another repeater (steps 2402 to 2406). .

The terminal 702 that has received the connection destination repeater change request compares the accommodation remaining number of the currently connected repeater 700 with the accommodation remaining number of the repeater 710 by referring to the adjacent terminal management table 300, and repeaters When the value of the remaining capacity of 700 is large, a connection destination repeater change refusal is transmitted to the terminal 704 (steps 2408 to 2412).

The terminal 704 that has received the connection destination repeater change refusal transmits the connection destination repeater change refusal to the repeater 710 (steps 2414 and 2416).

The repeater 710 that has received the connection destination repeater change rejection refers to the network management table 320 and ends the processing if there is no terminal that has not transmitted the connection destination repeater change request (steps 2418 and 2420). .

As mentioned above, although concretely demonstrated based on embodiment, it cannot be overemphasized that this invention is not limited to it and can be variously changed in the range which does not deviate from the summary.

For example, the criterion for selecting a network to connect to may be the electric field strength between terminals that can improve the communication speed, not the remaining number of accommodations that makes the load on the repeater as uniform as possible.

According to the described embodiment, when there is a change in the topology of the network, it is possible to construct a network within the limitation of the number of terminals that can be connected to the network.

100: management server, 102: data collection server, 110: relay, 112: terminal, 120: relay, 122: terminal, 124: terminal, 130: terminal, 200: CPU, 202: volatile memory, 204: storage Device 206: communication interface 210: CPU 212: volatile memory 214: storage device 216: communication interface 220: CPU 222: volatile memory 224: storage device 226: communication interface 230: CPU 232: Volatile memory, 234: Storage device, 236: Communication interface, 238: Screen display unit, 300: Adjacent terminal management table, 302: Topology management table, 304: Emergency topology management table, 306: Communication unit, 308 : Channel scanning unit, 310: transmission packet generation unit, 3 2: received packet analysis unit, 314: packet relay unit, 316: table update unit, 320: network management table, 322: communication unit, 324: channel scan unit, 326: transmission packet generation unit, 328: received packet analysis unit, 330: packet relay unit, 332: network management table update unit, 340: communication unit, 342: transmission packet generation unit, 344: received packet analysis unit, 346: packet relay unit, 360: standby terminal management table, 362: communication unit 364: transmission packet generation unit, 366: reception packet analysis unit, 368: terminal status display unit, 370: standby terminal management table update unit, 400: channel number, 402: terminal ID, 404: repeater ID, 406: data Collection server ID, 408: remaining capacity, 410: repeater ID, 412: Rank terminal ID, 414: lower terminal ID, 416: number of connected terminals, 420: repeater ID, 422: upper terminal ID, 424: lower terminal ID, 426: number of connected terminals, 430: maximum number of accommodated terminals, 432: accommodated Number of terminals, 434: remaining capacity, 436: lower terminal ID, 440: standby terminal ID, 442: repeater ID, 444: data collection server ID, 700: repeater, 702: terminal, 704: terminal, 706: terminal 708: terminal, 710: relay, 712: terminal, 730: terminal, 1200: relay, 1202: terminal, 1204: terminal, 1206: terminal, 1208: terminal.

Claims

A first network including a first repeater, a second network including a second repeater, a first terminal that transmits a connection request to the first network, a connection to the first network, A second terminal that is also connectable to the second network, and connects to the first network, and responds to reception of the connection request from the first terminal, to the first network. When the first remaining number of accommodated terminals is 0, the second terminal has a third terminal that connects the first terminal according to whether the connection destination of the second terminal to the second network can be changed. Communication network system.
The first network has a tree topology in which the first repeater is a root node, and the third terminal is connected to the first repeater closer to the first repeater than the second terminal. The communication network system according to claim 1, wherein:
In response to refusal to change the connection destination of the second terminal to the second network, the third terminal transfers to another terminal connected to the first repeater closer to the first relay than the third terminal. 3. The communication network system according to claim 2, wherein when there is no other terminal, the connection request from the first terminal is transmitted to the first repeater.
In response to refusal to change the connection destination to the first network from the first repeater that has received the connection request from the first terminal, the third terminal is connected to the first terminal. 4. The communication network system according to claim 3, wherein the communication network system waits for connection to the first network.
The third terminal connects to the second network via the second terminal in response to the first repeater leaving the first network. 2. The communication network system according to 2.
In response to receiving a connection destination repeater change request including the remaining number of third accommodated terminals of the third network from the third repeater constituting the third network, the third terminal The connection to one of the first network and the third network corresponding to a larger one of the first remaining number of accommodated terminals and the third remaining number of accommodated terminals. Communication network system.
In response to receiving a connection request from the first terminal to the first network, the first accommodating terminal remaining in the first network is connected to the first network including the first repeater. When the number is 0, the first terminal is connected to the first network according to whether the second terminal that can be connected to the first network can be connected to the second network. A communication network terminal characterized by connecting.
The first network comprises a tree-like topology with the first repeater as a root node, and is connected closer to the first repeater than the second terminal. Item 12. A communication network terminal according to Item 1.
In response to refusal to change the connection destination of the second terminal to the second network, if there is no other terminal connected to the other terminal closer to the first repeater, the first terminal 9. The communication network terminal according to claim 8, wherein the connection request from the first terminal is transmitted to a repeater.
In response to the connection destination change refusal to the first network from the first repeater that has received the connection request from the first terminal, the first terminal to the first network The communication network terminal according to claim 9, wherein the communication network terminal is made to wait for connection.
9. The communication network terminal according to claim 8, wherein the communication terminal is connected to the second network through the second terminal in response to the first repeater leaving the first network.
In response to receiving a connection destination repeater change request including the third accommodated terminal remaining number of the third network from the third repeater constituting the third network, the first accommodated terminal remaining number 9. The communication network terminal according to claim 8, wherein the communication network terminal is connected to one of the first network and the third network corresponding to a larger one of the remaining number of remaining terminals and the third accommodation terminal.
A first network including a first repeater, a second network including a second repeater, a first terminal that transmits a connection request to the first network, a connection to the first network, In a communication network system having a second terminal connectable to the second network and a third terminal connected to the first network, the third terminal is:
In response to receiving the connection request from the first terminal, when the first number of remaining accommodated terminals in the first network is 0, the connection of the second terminal to the second network Inquire about whether to change the destination,
A communication network configuration method, wherein the first terminal is connected in accordance with whether the connection destination of the second terminal to the second network can be changed.
The first network constitutes a tree topology with the first repeater as a root node, and the third terminal is connected to the first repeater closer to the first repeater than the second terminal. 14. The communication network configuration method according to claim 13, characterized in that:
In response to refusal to change the connection destination of the second terminal to the second network, the third terminal transfers to another terminal connected to the first repeater closer to the first relay than the third terminal. 15. The communication network configuration method according to claim 14, wherein when there is no other terminal, the connection request from the first terminal is transmitted to the first repeater.
In response to refusal to change the connection destination to the first network from the first repeater that has received the connection request from the first terminal, the third terminal is connected to the first terminal. The communication network configuration method according to claim 15, further comprising waiting for connection to the first network.
The third terminal connects to the second network via the second terminal in response to the first repeater leaving the first network. 14. A communication network configuration method according to 14.
In response to receiving a connection destination repeater change request including the remaining number of third accommodated terminals of the third network from the third repeater constituting the third network, the third terminal 15. The method according to claim 14, wherein a connection is made to one of the first network and the third network corresponding to a larger one of the first accommodation terminal remaining number and the third accommodation terminal remaining number. Communication network configuration method.