TW202344023A - Extended terminal device, aggregation device, communication system, communication method, and communication program - Google Patents

Abstract

An extended terminal device (4) according to the present disclosure comprises: a first communication unit (41) that uses a first communication method to communicate with at least a portion of a plurality of terminal devices; a second communication unit (42) that performs communication by using a second communication method different from the first communication method; a multi-hop communication control unit (44) that performs control of multi-hop communication in a multi-hop network where an aggregation device serves as a master station; and a protocol conversion processing unit (43) that performs protocol conversion of uplink data from the first communication method to the second communication method when the first communication unit (41) receives the uplink data, which is data to be sent to the aggregation device and is for managing the terminal device, from the terminal device. The second communication unit (42) transmits, to a counterpart device that is a next node on an uplink path to an aggregation device in a multi-hop network, the uplink data that has undergone the protocol conversion. The counterpart device performs protocol conversion of the uplink data from the second communication method to the first communication method.

Description

Extended terminal devices, hub devices, communication systems, communication methods and storage media

This disclosure relates to extended terminal devices, hub devices, communication systems, communication methods and storage media in wireless multi-pop networks.

In a wireless multi-hop network, terminal devices constituting the wireless multi-hop network relay data to construct a communication path from the terminal device at the source to the terminal device at the destination. In a wireless multi-hop network, each terminal device can relay data, so the data can be transmitted to a wider range than the reach range of the radio waves sent by the terminal device. Therefore, in recent years, systems that collect data from a wide range of terminal devices, such as automatic meter reading, such as the detection of electricity or natural gas, and the collection of various measurement data, have been introduced into wireless multi-hop networks. road. For example, Patent Document 1 discloses a data collection system that uses a wireless multi-hop network to collect power meter reading data. [Advanced technical documents] [Patent Document]

Patent Document 1: Japanese Patent No. 6498375

[Problem to be solved by the invention]

Wireless transmission distance is generally affected by the transmission rate. When the transmission rate becomes higher, the wireless transmission distance becomes shorter. Therefore, if there is no other terminal device around the terminal device within the wireless transmission distance corresponding to the required transmission capacity, the terminal device cannot communicate. When a wireless multi-hop network is used for automatic meter reading, collection of measurement data, etc., the terminal device will be installed in a location suitable for obtaining data. Therefore, there may be no other terminal device within the communication range and communication may not be possible. status. For example, if the terminal device is a communication device used in a smart meter that automatically reads meters, the smart meter will be installed in a place where users are required to measure power. When the distance between the users is too far, there may be an inability to participate. Smart meter for wireless multi-hop network. Therefore, it is desired to have a technology that can construct a multi-hop network including terminal devices where communication between terminal devices is difficult.

In view of the above-mentioned problems, the purpose of this disclosure is to obtain an extended terminal device that can construct a multi-hop network including terminal devices where communication between terminal devices is difficult. [Means used to solve problems]

In order to solve the above problems and achieve the purpose, the extended terminal device of the present disclosure includes: a first communication unit that communicates with at least some terminal devices among the plurality of terminal devices that can perform wireless communication using the first communication method. ; The second communication unit performs communication using a second communication method that is different from the first communication method; the multi-hop communication control unit performs control of multi-hop communication in a multi-hop network with the hub device as the main station. The extended terminal device further includes a protocol conversion processing unit. When the first communication unit receives data from the terminal device that is destined for the hub device, that is, uplink data, it processes the uplink data from the first communication method to the first communication mode. 2. Protocol conversion of communication methods. The second communication unit sends the protocol-converted uplink data to the next node on the uplink path toward the hub device in the multi-hop network, that is, the opposite end device. The opposite end device performs the uplink data from the second communication method. Protocol conversion to the first communication method. [Invention effect]

The extended terminal device disclosed in the present disclosure can achieve the effect of constructing a multi-hop network including terminal devices where communication between terminal devices is difficult.

Hereinafter, the expansion terminal device, line hub device, communication system, communication method and storage medium of the embodiment will be described in detail based on the drawings.

[Implementation type 1] FIG. 1 is a schematic diagram showing an example of the architecture of the communication system according to Embodiment 1. The communication system 7 of Embodiment 1 is, for example, a system that collects measurement data for automatically reading electricity and natural gas meters. However, it may also be a sensor network system that collects measurement data. The use of the communication system 7 is not limited to this.

As shown in FIG. 1 , the communication system 7 includes a central device 1, a line concentrator 2, terminal devices 3-1 to 3-7, and expansion terminal devices 4-1 and 4-2. The central device 1 controls the communication system 7 and receives data from the terminal devices 3-1~3-7 in the communication system 7 through the line hub device 2. In the following, when the terminal devices 3-1 to 3-7 are not displayed separately, they will be described as the terminal device 3. The extension terminal device 4-2 is an example of the first device of this embodiment, and the extension terminal device 4-1 is an example of the second device of this embodiment.

The hub device 2 and the terminal devices 3-1 to 3-7 can each perform, for example, specific low-power wireless communication in the 920 MHz band (hereinafter, simply referred to as 920 MHz band ultra-small wireless communication), and can perform communications for constructing a multi-hop network. control. The multi-hop network may be a wireless multi-hop network in which all nodes communicate wirelessly, or a multi-hop network including a wired section (as a channel section to be described later). Furthermore, as will be described later, the expansion terminal devices 4-1 and 4-2 can also perform specific low-power wireless communication in the 920 MHz band, and can also perform communication control for constructing a wireless multi-hop network. Furthermore, as will be described later, there may be cases where the connection between the extension terminal device 4-1 and the extension terminal device 4-2 is not actually a wireless line, but the extension includes the interval between the extension terminal device 4-1 and the extension terminal device 4-2. Multi-hop networks are also called wireless multi-hop networks. In addition, in FIG. 1 , seven terminal devices 3 are shown, but the number of terminal devices 3 is not limited to this. The number of line concentrating devices 2 is not limited to the example shown in FIG. 1 . Generally, a plurality of line concentrating devices 2 are used.

The hub device 2 is a device that becomes the root (master station) of the wireless multi-hop network and sends data received from the underlying terminal device 3 and the expansion terminal devices 4-1 and 4-2 to the central device 1; The central device 1 receives the control data of the underlying terminal device 3 and the extended terminal devices 4-1 and 4-2, etc., and sends it to the destination device through the wireless multi-hop network. Hereinafter, the hub device 2, the terminal device 3, and the extension terminal devices 4-1 and 4-2 constituting the wireless multi-hop network are respectively referred to as nodes.

In the wireless multi-hop network of this embodiment, path control is performed according to a predetermined path control protocol. As the path control protocol, RPL (IPv6 Routing Protocol for Low-Power and Lossy Networks) can be used. The path control protocol is not limited to this. In the following embodiment, an example of using RPL as the path protocol will be described. In RPL, regarding the communication path (upstream path) from each terminal device 3 and the extension terminal devices 4-1 and 4-2 to the hub device 2, each terminal device 3 and the extension terminal devices 4-1 and 4-2 maintain the communication path to the hub device 2. The next node (next node) on the path of the line concentrator 2 serves as the upstream path. The terminal device 3 and the extension terminal devices 4-1 and 4-2 control the upstream path in accordance with the path control protocol, and the data destined for the hub device 2 is transmitted to the next node, whereby the terminal device 3 and the extension terminal device 4-1 , The data sent by 4-2 arrives at the hub device 2. The downstream path is determined by the line concentrator 2 based on the upstream path, for example, but is not limited to this.

In addition, here, an example is explained in which the communication between the hub device 2 and the terminal devices 3-1 to 3-7 when constructing a wireless multi-hop network is 920 MHz band ultra-small wireless communication. However, the communication method when constructing a wireless multi-hop network is (First communication method) is not limited to this. In addition, the following describes an example in which the communication system 7 is used for automatic meter reading of electricity. That is, the terminal device 3 and the extended terminal devices 4-1 and 4-2 are examples of communication devices in smart meters. However, as mentioned above, The use of the communication system 7 is not limited to this.

The central device 1 and the hub device 2 are connected via an IP (Internet Protocol) network, for example. As a line of IP network. Various lines can be used, such as optical fiber, wired lines other than optical fiber, mobile phone networks, other wireless lines, etc., or a combination of two or more of them can be used.

In FIG. 1 , the first line 5 , which is a communication line between devices with ultra-small wireless communication at 920 MHz, is represented by a solid line. The same solid line without the symbol 5 is also the first line 5. In the example shown in FIG. 1 , the line concentrator 2 and the terminal devices 3 - 1 to 3 - 5 are surrounded by other terminal devices 3 capable of communicating with 920 MHz band ultra-small wireless communication. Therefore, the line concentrator 2 and the terminal devices 3 -1~3-5 can construct a wireless multi-hop network with the hub device 2 as the main station.

On the other hand, no terminal device 3 is installed between the terminal devices 3-6 and 3-7, the line concentrator 2, and the terminal devices 3-1 to 3-5, for example because there is no need for a user due to the presence of a mountain or the like. Therefore, none of the terminal devices 3-6, 3-7, and the terminal devices 3-1 to 3-5 can communicate using the 920 MHz band ultra-small wireless communication. Therefore, the terminal devices 3-6 and 3-7 cannot directly participate in the wireless multi-hop network with the hub device 2 as the master station. Hereinafter, the section between the terminal devices 3-6 and 3-7 and the terminal devices 3-1 to 3-5 will be called a divided section. From the side of the line concentrator 2, the terminal devices 3-6 and 3-7 are the terminal devices 3 located outside the divided section. Hereinafter, the terminal devices 3-6 and 3-7 are referred to as terminal devices located outside the divided section. 3 or a terminal device 3 existing outside the divided interval.

In addition, FIG. 1 schematically shows an example in which there is a mountain between the terminal devices 3-6 and 3-7, the line hub device 2, and the terminal devices 3-1 to 3-5. However, there may be divisions even if there is no mountain. interval situation. If the distance between the terminal devices 3-6 and 3-7, the line hub device 2, and the terminal devices 3-1 to 3-5 is more than the wireless transmission distance of 920 MHz ultra-small wireless communication, even if there is no mountain, the same , the terminal devices 3-6 and 3-7 cannot directly communicate with the line hub device 2 and the terminal devices 3-1~3-5 in the 920MHz band extra-small wireless communication. In this embodiment, by using the extension terminal devices 4-1 and 4-2, the cost can be suppressed more than when the line concentrator 2 is installed outside the divided area, so that the terminal device 3 outside the divided area can Communicates with hub device 2. Thereby, a wireless multi-hop network including the terminal devices 3 with which communication between the terminal devices 3 is difficult can be constructed. That is, the wireless multi-hop network with the hub device 2 as the main station can be extended to the terminal device 3 outside the divided section.

The extension terminal devices 4-1 and 4-2 are capable of performing 920 MHz ultra-small wireless communication (an example of the first communication method), and are also capable of performing other communication methods (second communication method) other than 920 MHz ultra-small wireless communication. Communication. Communication using other communication methods includes communication using a mobile phone network, communication using an optical communication line, and communication using a wired line other than an optical communication line, but is not limited thereto. In addition, other communication methods are, for example, communication methods based on IP, but are not limited thereto. For example, communication methods based on MAC (Media Access Control) layer connections or communication methods based on other communication protocols may also be used. In FIG. 1 , the communication line of another communication method is represented by a dotted line as the second line 6 . Hereinafter, as an example, the communication using another communication method is the communication according to the LTE (Long Term Evolution) standard, which is one of the communication using the mobile phone network. Therefore, communication between the extension terminal device 4-1 and the extension terminal device 4-2 is performed through an LTE base station that is not actually shown in FIG. 1 .

The expansion terminal devices 4-1 and 4-2 of this embodiment perform protocol conversion between the first communication method and another communication method (second communication method). Thereby, the terminal devices 3-6 and 3-7, the line hub device 2 and the terminal devices 3-1 to 3-5 can be connected through the expansion terminal devices 4-1 and 4-2. Hereinafter, when the extension terminal devices 4-1 and 4-2 are displayed without distinction, they will be described as the extension terminal device 4.

As shown in Figure 1, in a place where there are divided sections between the wireless multi-hop networks constructed by the hub device 2, when a smart meter for reading power is installed, communication that can communicate via a mobile phone network is sometimes used. device as the communication device in the smart meter. For example, when there are a small number of users in the mountains, communication devices that can communicate through the mobile phone network are used. However, when the number of communication devices that communicate through the mobile phone network increases, the cost of using the mobile phone network will increase. Furthermore, if the number of required users existing outside the divided section exceeds a certain level, it may be considered to install another line concentrating device 2 on the right side of FIG. 1 , for example. However, installing the line concentrator 2 requires considerable cost. Therefore, when the number of terminal devices 3 outside the divided section is small compared to the maximum number of terminal devices 3 that the line concentrator 2 can accommodate, outside the divided section It is not appropriate to install the line concentrator 2. In addition, the line concentrating device 2 is often installed on a utility pole together with the transformer, so maintenance costs are also required. In this embodiment, the wireless multi-hop network sandwiched between the divided sections can be constructed using the extension terminal devices 4-1 and 4-2. Therefore, there is no need to install the line concentrator 2 outside the divided sections, and the cost can be suppressed. , and enables communication between the terminal device 3 and the line concentrator 2 existing outside the divided section.

Next, an example of the architecture of each device in this embodiment will be described. FIG. 2 is a schematic diagram showing an architectural example of the terminal device 3 of this embodiment. The terminal device 3 includes a first communication unit 31 , a multi-hop communication control unit 32 , and an application processing unit 33 . The terminal device 3 is connected to an electric meter (not shown), and obtains the measurement result of the electric quantity measured by the electric meter as the meter reading data. In addition, the electric meter connected to the terminal device 3 may also be a gas meter that measures natural gas usage as described above. In addition, due to the different purposes of the communication system 7 , it may not be an electric meter, but a sensor that obtains measurement data may be connected to the terminal device 3 . In addition, the terminal device 3 may transmit and receive data in order to control the user's power generation equipment, power storage equipment, load equipment, etc., for control of a virtual power plant (VPP) or energy management.

The first communication unit 31 performs physical layer and MAC layer processing under 920 MHz ultra-small wireless communication. For example, when the first communication unit 31 receives data transmitted as radio waves using 920 MHz band ultra-small wireless communication from other devices such as the hub device 2, other terminal devices 3, and extension terminal devices 4, it will process the received data. The data is processed at the physical layer and MAC layer, and then the processed data is output to the multi-hop communication control unit 32 . Furthermore, the first communication unit 31 performs physical layer and MAC layer processing on the transmission data received from the multi-hop communication control unit 32, and sends the processed transmission data as radio waves.

The multi-hop communication control unit 32 performs communication control under the wireless multi-hop network in accordance with the path control protocol, thereby grasping the next node on the path of the hub device 2, and retains information indicating the next node as the upstream path. For example, the multi-hop communication control unit 32 generates various messages as transmission data in accordance with the path control protocol, and outputs the generated transmission data to the first communication unit 31 . Furthermore, when the data received from the first communication unit 31 is a path control message and a response is necessary, the multi-hop communication control unit 32 generates a response message as transmission data and outputs it to the first communication unit 31 . Furthermore, when the data received from the first communication unit 31 is a message destined for another terminal device 3, the multi-hop communication control unit 32 determines the message to be transmitted based on the information indicating the downlink path stored in the data. The terminal device 3 (or the hub device 2) instructs the first communication unit to send the data to the terminal device 3 determined to be transmitted. When transmission data is received from the application processing unit 33, the multi-hop communication control unit 32 adds a destination to the data and determines the terminal device 3 (or hub device 2) to be transmitted corresponding to the destination. The first communication unit is instructed to transmit the data to the terminal device 3 determined to be transmitted. Furthermore, when the data received from the first communication unit 31 is control data destined for the own terminal device, the multi-hop communication control unit 32 outputs the control data to the application processing unit 33 .

The application processing unit 33 executes application processing. For example, when the application process is to collect measurement data of electric power, the application processing unit 33 generates transmission data including measurement data obtained from an electric meter (not shown) as an application telegram, and outputs the generated application telegram to Multi-hop communication control unit 32. In addition, when the application processing unit 33 receives data from the multi-hop communication control unit 32, it will perform processing according to the data. In addition, the terminal device 3 is a general terminal device constituting a wireless multi-hop network, and therefore detailed description is omitted.

FIG. 3 is a schematic diagram showing an architectural example of the extension terminal device 4 in this embodiment. The extension terminal device 4 includes a first communication unit 41 , a second communication unit 42 , a protocol conversion processing unit 43 , a multi-hop communication control unit 44 and an application processing unit 45 . The extension terminal device 4 is also connected to the electric meter like the terminal device 3 . As mentioned above, depending on the purpose of the communication system 7, it may not be connected to the electric meter but may be connected to the sensor. In addition, although the example in which the extension terminal device 4 is connected to an electric meter or a sensor is described here, the extension terminal device 4 may not be connected to the electric meter and may be provided as a device specifically used for protocol conversion. In this case, the extension terminal device 4 does not need to include the application processing unit 45 .

The application processing unit 45 executes application processing. The operation of the application processing unit 45 is the same as that of the application processing unit 33 in the terminal device 3 . The multi-hop communication control unit 44 controls multi-hop communication in the multi-hop network with the hub device 2 as the master station. That is, the multi-hop communication control unit 44 will perform communication control under the multi-hop network in accordance with the path control protocol. The operation of the multi-hop communication control unit 44 is the same as that of the multi-hop communication control unit 32 in the terminal device 3 except that the transmitted data is sent to the first communication unit 41 through the protocol conversion processing unit 43 .

The first communication unit 41 performs processing of the physical layer and MAC layer of the first communication method (920 MHz ultra-small wireless communication). The first communication unit 41 can communicate with at least some of the terminal devices 3 among the plurality of terminal devices 3 capable of performing 920 MHz band ultra-small wireless communication using the first communication method. The operation of the first communication unit 41 is the same as that of the first communication unit 31 in the terminal device 3 except that it receives transmission data from the multi-hop communication control unit 44 through the protocol conversion processing unit 43 .

The second communication unit 42 can communicate using a second communication method that is different from the first communication method. For example, the second communication unit 42 performs processing of the physical layer and the MAC layer IP layer (network layer) in communication using communication methods other than 920 MHz ultra-small wireless communication. Here, as mentioned above, although the example in which the other communication method is based on LTE has been described, the other communication method is not limited to this.

When the first communication unit 41 receives data (uplink data) destined for the management terminal device 3 to the hub device 2 from the terminal device 3, the protocol conversion processing unit 43 changes the uplink data from the first communication method to the second communication method. Protocol conversion of communication methods. The protocol conversion processing unit 43 includes a transmission/reception control unit 431, a header generation and connection unit 432, a header division and analysis unit 433, a network control unit (hereinafter referred to as the NW control unit) 434, an information storage unit 435, and a distribution unit 436 .

The transmission/reception control unit 431 controls transmission/reception of the second communication unit 42 . The header generation and connection unit 432 generates a header for communication between the extension terminal devices 4 when sending a message to the extension terminal device 4 of the communication partner, and connects the generated header with the message. The header division and analysis unit 433 separates headers for communication between the extension terminal devices 4 from the data received from the extension terminal device 4 of the communication partner, and analyzes the separated headers. The NW control unit 434 controls communication with the extension terminal device 4 of the communication partner, and generates messages for communication between the extension terminal devices 4 . The information storage unit 435 stores information used in the allocation unit 436 to determine allocation (allocation information). The distribution unit 436 determines the distribution destination (output destination) of the message or notification generated by the protocol conversion processing unit 43 and the message or notification input to the protocol conversion processing unit 43 based on the distribution information, and distributes the message or notification according to the judgment result. Output to distribution destination. The details of the processing in the protocol conversion processing unit 43 will be described later.

FIG. 4 is a schematic diagram showing an architectural example of the line concentrating device 2 in this embodiment. The hub device 2 includes a first communication unit 21 , a third communication unit 22 , a multi-hop communication control unit 23 and an application processing unit 24 .

The application processing unit 24 executes application processing as the hub device 2 . For example, when the application process is to collect measurement data of electric power, the application processing unit 24 will aggregate the measurement data received from the underlying terminal device 3 and the extended terminal device 4 and output the aggregated data to the third communication unit 22 .

The third communication unit 22 communicates with the central device 1 . For example, the third communication unit 22 sends the data received from the application processing unit 24 to the central device 1, and when the data received from the central device 1 is data related to the control of the wireless multi-hop network, it communicates to the multi-hop. The control unit 23 outputs data related to application processing to the application processing unit 24 .

Like the first communication unit 31 of the terminal device 3 , the first communication unit 21 performs physical layer and MAC layer processing in 920 MHz ultra-small wireless communication. The multi-hop communication control unit 23 performs communication control as the master station in the wireless multi-hop network in accordance with the path control protocol.

FIG. 5 is a schematic diagram showing an architectural example of the central device 1 in this embodiment. The central device 1 includes a third communication unit 11 and an application processing unit 12 . The third communication unit 11 communicates with the line concentrating device 2 . The application processing unit 12 executes application processing as the central device 1 . For example, when the application processing is the collection of power measurement data, the application processing unit 12 has the third communication unit 11 send the data received from the hub device 2 to a device (not shown) that manages meter reading data. In addition, the application processing unit 12 generates control data for controlling the hub device 2, the terminal device 3 and the extended terminal device 4, and outputs the generated data to the third communication unit 211, thereby allowing the third communication unit 11 to transmit the control data. Sent to hub device 2.

Next, the operation of the communication system 7 of this embodiment will be described. FIG. 6 , FIG. 7 , and FIG. 8 are sequence diagrams showing an example of connection processing between the extension terminal devices 4 in this embodiment. As shown in FIG. 6 , the extension terminal devices 4-1 and 4-2 each perform connection processing (base station connection processing) with an LTE base station (step S1). In addition, when the other communication method is a communication method other than LTE, the extension terminal devices 4-1 and 4-2 will perform connection processing corresponding to the communication method.

The NW control unit 434 of the protocol conversion processing unit 43 of the extension terminal device 4-1 starts (activates) the transmission random timer (step S2). The transmission random timer is a timer with an expiration time randomly set in order to disperse the transmissions of the extension terminal devices 4, and is built-in in the NW control unit 434, for example. In this example, an example will be described in which the transmission random timer of the extension terminal device 4-1 expires sooner among the extension terminal devices 4-1 and 4-2, and the processing is performed first. Although illustration is omitted, the extension terminal device 4-2 also starts the transmission random timer in the same manner.

When the transmission random timer expires (step S3), the NW control unit 434 of the extended terminal device 4-1 generates transmission information and a network confirmation message (hereinafter referred to as the NW confirmation message), and outputs the generated transmission information and NW confirmation message. to the header generation linking unit 432 (step S4). The NW confirmation message is a message used to confirm that communication between the extension terminal devices 4 can be performed normally. The transmission message is information used for generation of the conversion header described later and for communication control in LTE. The sending information includes, for example, sending source terminal identification information, sending destination IP (IP address), sending destination port (Port), and sending protocol. In addition, it is assumed that each extension terminal device 4 holds its own IP address and the IP address of the extension terminal device 4 to be a communication partner in advance. These IP addresses are, for example, logged in beforehand. The IP address may be fixed, and each extension terminal device 4 may retain the MAC address of the extension terminal device 4 that becomes the communication partner, and use the MAC address to query the IP address. Each extension terminal device 4 will generate an NW confirmation message and send it when the random transmission timer expires or when the NW confirmation message is received before the random transmission timer expires.

Alternatively, either one of the extension terminal device 4-1 and the extension terminal device 4-2 may maintain its own IP address and the extension terminal device 4 that becomes the communication partner (for the extension terminal device 4-1, it is the extension terminal device 4-1). The terminal device 4-2, for the extended terminal device 4-2, is the IP address of the extended terminal device 4-1). These IP addresses are, for example, pre-registered. Alternatively, the central device 1 may notify the extension terminal device 4-1 of the IP address of the extension terminal device 4-1 and the IP address of the extension terminal device 4-2. When either the extension terminal device 4-1 or the extension terminal device 4-2 holds an IP address, the extension terminal device 4 holding the IP address sends an NW confirmation message when the transmission random timer expires. . When the extension terminal device 4 that does not hold an IP address receives the NW confirmation message from the communication partner, it will generate the NW confirmation message and send the generated NW confirmation message to the extension terminal device 4 from which the received NW confirmation message was sent. .

The transmission source terminal identification information is, for example, the MAC address of the transmission source extension terminal device 4, but is not limited thereto, as long as it is identification information unique to the hardware of the extension terminal device 4. The NW confirmation message includes information indicating that it is an NW confirmation message, serial number, and connection availability information. In addition, the NW confirmation message may also include information indicating that it is an NW control message, and one or more of the serial number and connection availability information may not be included in the NW confirmation message. The connection availability information is information showing whether the extension terminal device 4 of the sending source can communicate with other extension terminal devices 4 through other communication methods (LTE). For example, the connection availability information will become a value indicating that the connection is possible after the connection process is performed with the base station. The connection is possible during the period when communication with the base station is possible. For example, when there is a communication failure with LTE, or an instruction to stop LTE communication is received from the central device 1, the hub device 2, etc., the connection availability information becomes a value indicating that the connection is not possible.

When receiving the transmission information and the NW confirmation information, the header generation connection unit 432 of the extension terminal device 4-1 generates a conversion header using the transmission information (step S5), and generates transmission parameters using the transmission information (step S6). The conversion header is a header used to convert the communication protocol in the wireless multi-hop network into the communication protocol between the extended terminal devices 4 . The conversion header includes, for example, sending source identification information. The transmission parameters are, for example, parameters used in transmission control of LTE. The sending parameters include the sending destination IP, the sending destination port and the sending protocol.

Here, the conversion header is explained. In the wireless multi-hop network formed by the hub device 2 and the terminal device 3, a header for path control (multi-hop network header) in accordance with the path control protocol is added to the transmitted data. Data transmitted and received in the wireless multi-hop network formed by the hub device 2 and the terminal device 3 will also have headers such as layer 2 (L2) added in addition to the multi-hop network header. For example, when the first communication unit 41 of the extension terminal device 4-1 attaches a communication path header and sends the data including all of these headers as a payload, the first communication unit 41 of the extension terminal device 4-2 By deleting the communication path header, a wireless multi-hop network including the communication path between the extension terminal device 4-1 and the extension terminal device 4-2 can be constructed. That is, the extension terminal device 4-1 can perform protocol conversion by encapsulation, and the extension terminal device 4-2 can perform protocol conversion by deleting the header attached due to encapsulation. In this way, protocol conversion can be performed by encapsulation, but here, regarding headers other than the multi-hop network header, it will be explained that not all headers are left, but only necessary information is extracted, and the extracted information is used as conversion Example of headers and appending for protocol conversion. In this way, the communication volume can be reduced more than in the case of encapsulation.

As mentioned above, the conversion header is, for example, the sending source identification information, such as the MAC address of the sending source device. Here, the conversion header is explained as an example of transmission source identification information, but the conversion header is not limited to this. Information extracted from headers other than multi-hop network headers may be included, and plural information may be included. When the extension terminal device 4-1 transmits the NW confirmation message, since the transmission source device is the extension terminal device 4-1, the transmission source identification information is the identification information of the extension terminal device 4-1. That is, the transmission source identification information is, for example, the identification information in L2 of the extension terminal device 4 of the transmission source among the adjacent extension terminal devices 4 . In this way, by including the identification information in the L2 of the extension terminal device 4 of the transmission source in the conversion header, the multi-hop communication control unit 44 of the extension terminal device 4 can use this information, and perform the multi-hop communication control unit 44. L2 processing. Therefore, the extension terminal device 44 that sends the data can appear to be located next to the extension terminal device 4 that receives the data in the multi-hop communication control. That is, the extension terminal device 4 that has received data from another extension terminal device 4 uses the first communication unit 41 to perform the same processing as when it receives data from another extension terminal device 4, whereby the extension terminal device 4 can be Acts as an adjacent node in a wireless multi-hop network.

Next, the header generation and connection unit 432 of the extension terminal device 4-1 performs connection of the messages (step S7). Specifically, the header generation and linking unit 432 adds a conversion header to the NW confirmation information, thereby linking the conversion header to the NW confirmation message. The addition of the conversion header is an example of protocol conversion from the first communication method to the second communication method. Next, the header generation connection unit 432 of the extension terminal device 4-1 outputs the NW confirmation message with the converted header added to the transmission/reception control unit 431, and notifies the transmission/reception control unit 431 of the transmission parameters (step S8).

The transmission/reception control unit 431 of the extension terminal device 4-1 outputs the NW confirmation message with the conversion header added to the first communication unit 41, and requests the second communication unit 42 to send the NW confirmation message using the transmission parameters (step S9 ). The second communication unit 42 of the extension terminal device 4-1 adds a communication path header in LTE to the NW confirmation message with the conversion header received from the transmission/reception control unit 431, and converts the communication path header and conversion The NW confirmation message of the header is sent with the extension terminal device 4-2 as the destination (step S10). The communication path header is generated using send parameters. However, the communication path header includes the sending source IP (IP address) and the sending source port (Port). In addition, although illustration is omitted, this NW confirmation message reaches the extension terminal device 4-2 via the base station. This example is an example, but it is not limited to this. If the other communication method is other than LTE, the header corresponding to the communication method will be attached as the communication path header, and the parameters corresponding to the communication method will also be used for the transmission parameters.

As shown in FIG. 7 , when the second communication unit 42 of the extension terminal device 4-2 receives the NW confirmation message to which the communication path header and the conversion header are attached from the extension terminal device 4-1, it receives the communication path header from the communication path header. The LTE communication information is extracted, and the LTE communication information and the NW confirmation information with the conversion header added are output to the transmission/reception control unit 431 (step S11).

The transmission/reception control unit 431 of the extension terminal device 4-2 outputs the LTE communication information and the NW confirmation information to which the conversion header is added to the header division and analysis unit 433 (step S12). The header division analysis unit 433 of the extension terminal device 4-2 performs header division (step S13). Specifically, the header division and analysis unit 433 separates the conversion header and the NW confirmation message. Next, the header division and analysis unit 433 of the extension terminal device 4-2 creates reception information (step S14). Specifically, the header segmentation and analysis unit 433 uses the conversion header and the LTE communication information to create reception information. The sending source terminal identification information is included in the conversion header, and the sending source IP, sending source port, and receiving protocol are included in the communication path header.

Next, the header division and analysis unit 433 of the extension terminal device 4-2 outputs the reception information and the NW confirmation message to the NW controller 434 (step S15). The NW control unit 434 of the extension terminal device 4-2 retains the information (step S16). That is, the NW control unit 434 retains the information included in the reception information and the NW confirmation message.

Next, the NW control unit 434 of the extension terminal device 4-2 generates an NW confirmation message as a reply to the received NW confirmation message, and outputs the generated transmission information and the NW confirmation message to the header generation connection unit 432 (step S17). The transmission information is the same as the information generated by the extension terminal device 4-1 in step S4, but in step S4 the transmission source identification information is the identification information of the extension terminal device 4-1, and in step S17 the transmission source identification information is the extension terminal device 4 -2 identification information. The NW confirmation information is also the same as the information generated by the extension terminal device 4-1 in step S4, but the sequence number can be the same as the sequence number included in the NW confirmation message received from the extension terminal device 4-1, but it is not limited thereto. Here it is. When the serial number check described below is not performed, the serial number may be determined by any method. Furthermore, as mentioned above, the NW confirmation message only needs to contain information indicating that this is an NW confirmation message, and the serial number does not need to be included in the NW confirmation message. Here, the sequence number is the same as the sequence number included in the NW confirmation message received from the extension terminal device 4-1.

Thereafter, in the same manner as steps S5 to S10 in the extension terminal device 4-1, steps S18 to S23 shown in FIGS. 7 and 8 are executed in the extension terminal device 4-2. Thereby, the NW confirmation message with the communication path header and the conversion header appended is sent from the extension terminal device 4-2 to the extension terminal device 4-1.

As shown in FIG. 8 , after step S23, in the extension terminal device 4-1, steps S24 to S28 are executed in the same manner as steps S11 to S15. After step S28, the NW control unit 434 of the extension terminal device 4-1 checks the serial number (step S29). Here, since the extension terminal device 4-2 includes the same sequence number as the NW confirmation message sent by the extension terminal device 4-1 in the NW confirmation message, the NW control unit 434 of the extension terminal device 4-1 determines from Whether the sequence number included in the NW confirmation message received by the extension terminal device 4-2 is consistent with the sequence number of the NW confirmation message generated in step S4. Thereby, the extension terminal device 4-1 can confirm that the NW confirmation message received from the extension terminal device 4-2 is a reply to the NW confirmation message sent by itself.

Next, the NW control unit 434 of the extension terminal device 4-1 checks the connection availability information (step S30). Specifically, the NW control unit 434 confirms whether the connection availability information indicates that the connection is possible. If the connection availability information indicates that the connection is possible, then the NW control unit 434 performs processing using communication between the extended terminal devices 4 . When the connection availability information displays unconnectable information, the process may be repeated from step S2 after a certain period of time, or the central device 1 or the concentrating device 2 may be notified that communication with the extension terminal device 4-2 is impossible.

In addition, as mentioned above, the NW confirmation message does not need to include the sequence number. When the NW confirmation message does not include the sequence number, the NW control unit 434 of the extension terminal device 4-1 does not perform step S29, but confirms whether the received message is It is a NW confirmation message. As mentioned above, the NW confirmation message includes information indicating that this is the NW confirmation message. The NW control unit 434 can refer to this information and confirm that the received information is the NW confirmation information. When the received message is an NW confirmation message and the transmission source identification information stored in the conversion header is the identification information of the extension terminal device 4-2 determined as the communication partner of the extension terminal device 4-1, the NW control unit 434 will determine that the received message is the answer to the NW confirmation message sent by itself.

Furthermore, as mentioned above, the NW confirmation message does not need to include the connection availability information. When the NW confirmation message does not include the connection availability information, the NW control unit 434 of the extension terminal device 4-1 does not execute step S30. When step S30 is not performed but step S29 is performed, when the serial number is confirmed to be correct during the serial number check in step S29, the NW control unit 434 of the extension terminal device 4-1 determines that communication with the extension terminal device 4-2 is possible. . When step S30 is not executed and a judgment is made using information showing that this is the NW confirmation message instead of step S29, similarly, when it is judged that the received message is a reply to the NW confirmation message sent by itself, It is determined that communication with the extension terminal device 4-2 is possible.

In the example shown in FIG. 1 , two extension terminal devices 4 corresponding to one line concentrator device 2 are shown. However, three or more extension terminal devices 4 corresponding to one line concentrator device 2 may be installed. In this case, the extension terminal device 4 similarly sends the NW confirmation message to the other extension terminal devices 4 of the communication partners to confirm the connection. When the connection is confirmed, similarly, the extension terminal device 4 is configured to include the extension terminal device. 4 wireless multi-hop networks.

Next, the connection processing to the wireless multi-hop network in the extension terminal device 4 will be described. 9 to 12 are sequence diagrams illustrating an example of connection processing to a wireless multi-hop network in the extension terminal device 4 of this embodiment.

In addition, here, it is assumed that the extension terminal device 4-1 implements a wireless multi-hop network including the hub device 2 in accordance with the path control protocol through the multi-hop communication control unit 44 and the first communication unit 41 like the terminal device 3. The construction of paths in the road. For example, the path is constructed using the DIO (DODAG (Destination Oriented Directed Acyclic Graph) Information Object) message sent from the hub device 2 of the master station. In addition, the DIO message is a message used for path construction. The master station broadcasts the DIO message to each node. Each node updates the level contained in the DIO message to the value after adding its own level and transmits it, thereby constructing an uplink communication path. . The level is determined based on the number of hops, communication quality, etc., for example. The multi-hop communication control unit 44 of the extension terminal device 4-1 grasps the level of the master station (hub device 2) corresponding to the extension terminal device 4-1.

As shown in FIG. 9 , after confirming the connection with the extension terminal device 4-2 using the above-mentioned NW confirmation message, the NW control unit 434 of the extension terminal device 4-1 starts the wireless multi-hop connection (including the extension terminal device). The start of the connection process of the wireless multi-hop network including communication between 4) is notified to the distribution unit 436 (step S31). In step S31, the NW control unit 434 also notifies the distribution unit 436 of the transmission information regarding the direct transmission to the extension terminal device 4-2 of the transmission destination in the communication between the extension terminal devices 4.

When receiving the notification of the start of the wireless multi-hop connection, the allocation unit 436 will perform allocation judgment based on the transmission information and determine the allocation destination of the notification (step S32). For example, the information storage unit 435 stores information indicating that the notification of the start of the wireless multi-hop connection is allocated to the multi-hop communication control unit 44. As the allocation information, the allocation unit 436 determines the allocation of the notification of the start of the wireless multi-hop connection based on the allocation information. The destination is the multi-hop communication control unit 44. Furthermore, the extension terminal device 4-2 is the destination of communication using the extension terminal device 4. Therefore, the information storage unit 435 stores a header generation link indicating that the distribution destination of the message sent to the extension terminal device 4-2 is The information of part 432 is used as allocation information. Based on the transmission information, the distribution unit 436 grasps that the transmission destination of the message generated by the multi-hop communication control unit 44 is the extension terminal device 4-2 through the notification of the start of the wireless multi-hop connection, and assigns the distribution destination of the message based on the distribution information. It is determined that the header generation link unit 432 is used.

The allocation unit 436 outputs a notification of the start of the wireless multi-hop connection to the multi-hop communication control unit 44 of the allocation destination (step S33). When receiving the notification of the start of the wireless multi-hop connection, the multi-hop communication control unit 44 generates a DIO message (abbreviated as DIO in the figure) (step S34), and outputs the generated DIO message to the distribution unit 436 (step S35). This DIO message contains the level corresponding to hub device 2.

The distribution unit 436 determines that the distribution destination of the DIO message is the header generation connection unit 432 through the judgment in step S32, and therefore outputs the DIO message received from the multi-hop communication control unit 44 together with the transmission message received in step S31. The header generation connection unit 432 is generated (step S36). Thereafter, steps S5 to S10 are performed similarly to the example shown in FIG. 6 . However, part of the NW confirmation message becomes the DIO message.

As shown in FIG. 10 , when the extension terminal device 4 - 2 receives the DIO message to which the communication path header and the conversion header are attached, steps S11 to S15 are performed in the same manner as in the example shown in FIG. 7 . However, part of the NW confirmation message becomes the DIO message. In addition, in FIG. 7 , the illustration of the distribution unit 436 is omitted. However, even in the example shown in FIG. 7 , in step S15 , the header division analysis unit 433 notifies the distribution unit 436 of the reception information and the NW confirmation message. However, the NW confirmation message is specified not to be output in the distribution information, and the distribution unit 436 does not output the reception information and the NW confirmation message even if it receives the notification.

The allocation unit 436 of the extension terminal device 4-2 performs allocation judgment after receiving the reception information and the DIO message (step S37). When a message in the wireless multi-hop network including a DIO message is received, the distribution to the multi-hop communication control unit 44 is specified by the distribution information, and the distribution unit 436 determines the distribution destination of the DIO message to be multi-hop. Communication control unit 44.

The distribution unit 436 of the extension terminal device 4-2 outputs the DIO message to the multi-hop communication control unit 44 based on the distribution determination (step S38). The multi-hop communication control unit 44 of the extension terminal device 4-2 selects the hub device 2 using the quality information (determination of the hub device 2) (step S39). The determination method of the hub device 2 in the multi-hop communication control unit 44 is the same as the determination method of a general master station using DIO messages, so the detailed description is omitted. In the example shown in Figure 1, the information about the hub device 2 shown in Figure 1 can be obtained through the DIO message through the extension terminal device 4-1. Since there is no other hub device 2, the multi-hop communication control unit 44 determines the master station as the line concentrator 2 shown in FIG. 1 . The multi-hop communication control unit 44 holds the identification information of the extension terminal device 4-1 from which the DIO message is sent as the path information as the upstream path corresponding to the determined hub device 2, that is, as the next node. In addition, when there are a plurality of concentrator devices 2, the concentrator device 2 is determined based on quality information and the like. Although illustration is omitted, the multi-hop communication control unit 44 of the extension terminal device 4-2 causes the first communication unit 41 to transmit the DIO message through broadcasting.

On the other hand, when receiving the reception information and the DIO message, the NW control unit 434 of the extension terminal device 4-2 notifies the distribution unit 436 of the start of the wireless multi-hop connection in the same manner as step S31 in the extension terminal device 4-1 ( Step S40). Thereafter, steps S41 to S45 are performed in the same manner as steps S32 to S36 in the extension terminal device 4-1. Thereafter, steps S18 to S23 are performed similarly to the examples shown in FIGS. 7 and 8 . However, part of the NW confirmation message becomes the DIO message.

As shown in FIG. 12 , when the extension terminal device 4 - 1 receives the DIO message to which the communication path header and the conversion header are attached, steps S24 to S28 are performed similarly to the example shown in FIG. 8 . Thereafter, in the extension terminal device 4-1, steps S47 to S49 are executed in the same manner as steps S37 to S39 in the extension terminal device 4-2 shown in FIG. 10 .

Next, the notification process from the extension terminal device 4-2 to the uplink path will be described. By receiving the above-mentioned DIO message, the extension terminal device 4-2 retains the upstream path to the hub device 2 as path information. The extension terminal device 4-2 notifies the hub device 2 of this upstream path. The message notifying the uplink path is the same as the message notifying the uplink path from the terminal device 3, and is a message destined for the hub device 2.

13 and 14 are sequence diagrams showing an example of the steps of the notification process from the extension terminal device 4-2 to the uplink path in this embodiment. As shown in FIG. 13 , the multi-hop communication control unit 44 of the extension terminal device 4-2 generates a message notifying an uplink path (uplink path notification message, simply referred to as an uplink path notification in the figure), and outputs the generated uplink path notification message to Protocol conversion processing unit 43 (step S51). The protocol conversion processing unit 43 of the extension terminal device 4-2 performs protocol conversion processing (protocol conversion processing during transmission) (step S52), and outputs the processed message to the second communication unit 42 (step S53). 42 sends the processed message to the extension terminal device 4-1 (step S54). Although the contents of the messages are different, step S52 is the same as steps S18 to S21 shown in FIG. 11 , step S53 is the same as step S22 shown in FIG. 11 , and step S54 is the same as step S23 shown in FIG. 11 .

In the extension terminal device 4-1, when the second communication unit 42 receives the message sent in step S54 (the message to which the communication path header and the conversion header are added), it outputs the received message to the protocol conversion processing unit 43 (step S54). S55). The protocol conversion processing unit 43 of the extension terminal device 4-1 performs protocol conversion processing (protocol conversion processing at the time of reception) (step S56), and outputs the processed message to the multi-hop communication control unit 44 (step S57). The content of the message is different, but step S56 is the same as steps S24 to S28 and S47 shown in FIG. 12 , and step S57 is the same as step S48 shown in FIG. 12 .

The multi-hop communication control unit 44 of the extension terminal device 4-1 updates the multi-hop network header in the message received from the protocol conversion processing unit 43 (step S58), and outputs the message with the updated multi-hop network header to the protocol conversion unit. Processing unit 43 (step S59). The multi-hop network header is a header used for communication in a wireless multi-hop network, such as a header in RPL, but is not limited thereto. The multi-hop communication control unit 44 will update the multi-hop network header according to the path control protocol. For example, the multi-hop communication control unit 44 adds the identification information of its own node to update the multi-hop network header and determine the forwarding destination of the message. Specifically, the multi-hop communication control unit 44 adds information indicating the next node of the forwarding destination to the message based on the maintained uplink path. In the examples shown in FIGS. 13 and 14 , the expansion terminal device 4-1 retains information indicating that the next uplink node is the terminal device 3-2 as path information.

The allocation unit 436 in the protocol conversion processing unit 43 of the extension terminal device 4-1 performs allocation determination using the destination and allocation information of the message received from the multi-hop communication control unit 44 (step S60). That is, the distribution unit 436 uses the destination of the message received from the multi-hop communication control unit 44 and the distribution information to determine the distribution destination of the message received from the multi-hop communication control unit 44 . As mentioned above, the information storage unit 435 stores allocation information. The allocation information includes information indicating whether the destination of each sent message is to be sent through the first communication unit 41 or the second communication unit 42 . For example, the distribution unit 436 displays a message indicating that the node is the source node (terminal device 3, extension terminal device 4, hub device 2) of the message received from the first communication unit 41. Information such as destination information is stored in the information storage unit 435 as distribution information. In addition, the distribution unit 436 displays information indicating that the second communication unit 42 is used to transmit a message destined for the node of the message received from the second communication unit 42, and stores it as distribution information in the information. Storage section 435. In the example shown in FIG. 13 , the destination of the message is the hub device 2 , so the distribution unit 436 determines that the first communication unit 41 is used to send the message.

The protocol conversion processing unit 43 of the expansion terminal device 4-1 outputs the message received from the multi-hop communication control unit 44 to the first communication unit 41 based on the result of the allocation judgment (step S61). The first communication unit 41 sends the message to the terminal device 3-2 of the transfer destination (step S62).

In the terminal device 3-2, when the first communication unit 31 receives the message from the extended terminal device 4-1, it outputs the message to the multi-hop communication control unit 32 (step S63). The multi-hop communication control unit 32 of the terminal device 3-2 updates the multi-hop network header of the received message in the same manner as step S58 (step S64). The multi-hop communication control unit 32 of the terminal device 3-2 outputs the message in which the multi-hop network header has been updated to the first communication unit 31 (step S65).

As shown in FIG. 14 , the first communication unit 31 of the terminal device 3-2 sends the message to the line hub device 2 (step S66). The first communication unit 21 of the line hub device 2 outputs the received message to the multi-hop communication control unit 23 (step S67). The multi-hop communication control unit 23 obtains the path from the multi-hop network header of the received message and stores it (step S68). More specifically, in the example shown in FIG. 14 , the hub device 2 extracts the node on the upstream path of the extension terminal device 4-2 of the transmission source from the multi-hop network header, thereby assigning the node corresponding to the extension terminal device 4-2 The nodes on the uplink path are stored as path information. Afterwards, when the hub device 2 uses this path information to send data destined for the extended terminal device 4-2, it will add the node included in the corresponding path information as the downlink path to the multi-hop network header. Thereby, the data sent from the line hub device 2 and destined for the extension terminal device 4-2 will be forwarded by each node on the downlink path and reach the extension terminal device 4-2. At this time, the extension terminal device 4-1 will perform protocol conversion as described above, and send downlink data to the extension terminal device 4-2.

Next, the application message transmission process from the extension terminal device 4-2 will be described. FIGS. 15 and 16 are sequence diagrams showing an example of the processing procedure for transmitting an application message from the extension terminal device 4-2 in this embodiment.

As shown in FIG. 15 , when the application processing unit 45 of the expansion terminal device 4-2 generates an application telegram, it notifies the multi-hop communication control unit 44 of the application telegram (step S71). The multi-hop communication control unit 44 adds a multi-hop network header to the application telegram (step S72), and outputs the application telegram to which the multi-hop network header is added to the protocol conversion processing unit 43 (step S73). Thereafter, in the example shown in FIG. 13 , steps S52 to S54 are implemented.

As shown in FIGS. 15 and 16 , the extension terminal device 4-1, the terminal device 3-2 and the line concentrator 2 perform the processing of steps S55 to S68 in the same manner as in the example shown in FIGS. 13 and 14. The line concentrator device After step S68, the multi-hop communication control unit 23 of 2 will delete the multi-hop network header from the data (step S80) because the received data is an application telegram, and will delete the multi-hop network header data (that is, Application telegram) is output to the third communication unit 22 (step S81).

The third communication unit 22 sends the application telegram to the central device 1 (step S82). The third communication unit 11 of the central device 1 sends the received application telegram to the application processing unit 12 (step S83). The application processing unit 12 performs processing corresponding to the application telegram (step S84).

In addition, in the examples shown in FIGS. 15 and 16 , when the hub device 2 receives the application telegram, it directly forwards it to the central device 1 . However, the application processing unit 24 in the hub device 2 may also process the application telegram, and then The processed application telegram is sent to the central device 1 . For example, when the application telegram includes meter reading data on electric power, the application processing unit 24 aggregates the meter reading data received from a plurality of nodes and sends the aggregated data to the central device 1 .

Next, the notification process from the terminal device 3-6 to the uplink path will be described. When the terminal device 3-6 receives the above-mentioned DIO message, it holds the upstream path to the hub device 2 as path information. The terminal device 3-6 notifies the hub device 2 of this upstream path.

17 and 18 are sequence diagrams showing an example of the notification processing procedure from the terminal device 3-6 to the uplink path in this embodiment. As shown in FIG. 17 , the multi-hop communication control unit 32 of the terminal device 3-6 generates a message notifying the uplink path (uplink path notification message, simply referred to as the uplink path notification in the figure), and appends to the generated uplink path notification message a message indicating the uplink path. The information of the next node on the path is then output to the first communication unit 31 (step S91). The uplink path notification message is an example of uplink data destined for the hub device 2 . The first communication unit 31 sends the uplink path notification message to the extension terminal device 4-2 of the next node (step S92).

The first communication unit 41 of the extension terminal device 4-2 outputs the received uplink path notification message to the multi-hop communication control unit 44 (step S93). The multi-hop communication control unit 44 updates the multi-hop network header of the received uplink path notification message (step S94), and outputs the upstream path notification message with the updated multi-hop network header to the protocol conversion processing unit 43 (step S95). Thereafter, steps S52 to S68 are implemented by the extension terminal device 4-2, the extension terminal device 4-1, the terminal device 3-2, and the line concentrator 2, similarly to the examples shown in FIGS. 13 and 14 .

In this manner, the second communication unit 42 of the extension terminal device 4-2 transmits the protocol-converted uplink data to the next node on the uplink path toward the hub device 2 in the multi-hop network. In the examples shown in FIGS. 17 and 18 , the counterpart device is the extension terminal device 4-1. The extension terminal device 4-1 as the peer device performs protocol conversion on the uplink data from the second communication method to the first communication method, and then sends the protocol-converted uplink data to the hub device 2 in the first communication method.

Next, the application message transmission process from the terminal device 3-6 will be described. FIG. 19 is a sequence diagram showing an example of the procedure for sending an application message from the terminal device 3-6 in this embodiment.

As shown in FIG. 19 , when an application telegram is generated, the application processing unit 33 of the terminal device 3 - 6 notifies the multi-hop communication control unit 32 of the application telegram (step S101 ). The application telegram is an example of upstream data destined for the hub device 2 . The multi-hop communication control unit 32 adds a multi-hop network header to the application telegram (step S102), and outputs the application telegram to which the multi-hop network header is added to the first communication unit 31 (step S103). The first communication unit 31 sends the application telegram to which the multi-hop network header is added to the extension terminal device 4-2 (step S104). Thereafter, similarly to the examples shown in FIGS. 17 and 18 , steps S93 to S95 and S52 to S62 are implemented by the extension terminal device 4-2 and the extension terminal device 4-1. Thereafter, although illustration is omitted, steps S63 to S68 and S80 to S84 are executed in the terminal device 3-2, the line concentrator 2 and the central device 1 in the same manner as in the examples shown in FIGS. 15 and 16 .

Next, the hardware structure of the expansion terminal device 4 of this embodiment will be described. The extension terminal device 4 of this embodiment implements the protocol conversion processing unit 43, the multi-hop communication control unit 44 and The function of the application processing unit 45 is applied. FIG. 20 is a schematic diagram showing an example of the architecture of a computer system that implements the expansion terminal device 4 of this embodiment. As shown in Figure 20, this computer system includes a control unit 101 and a storage unit 102 that constitute a processing circuit, a first communication device 103, and a second communication device 104, which are connected through a system bus. The first communication device 103 is, for example, a receiver and a transmitter composed of an antenna and a communication circuit. The second communication device 104 is, for example, a receiver and a transmitter composed of an antenna and a communication circuit. However, when wired communication is performed, the antenna does not need to be provided.

In FIG. 20 , the control unit 101 is, for example, a processor such as a CPU (Central Processing Unit), and executes a program describing the processing in the extension terminal device 4 of this embodiment. In addition, a part of the control unit 101 may be implemented by dedicated hardware such as an FPGA (Field-Programmable Gate Array). The storage unit 102 includes various storage devices such as RAM (Random Access Memory) and ROM (Read Only Memory) and hard disks, and stores the programs to be executed by the control unit 101, necessary data obtained during processing, etc. . In addition, the storage unit 102 may be used as a temporary storage area for programs. In addition, FIG. 20 is an example, and the architecture of the computer system is not limited to the example of FIG. 20 .

Here, an example of the operation of the computer system until the program of this embodiment can be executed is explained. In a computer system with the above-mentioned architecture, a computer program is installed into the storage unit from a CD-ROM or DVD-ROM placed in a CD (Compact Disc)-ROM drive or a DVD (Digital Versatile Disc)-ROM drive (not shown). 102. Then, when the program is executed, the program read from the storage unit 102 is stored in the main storage area of the storage unit 102 . In this state, the control unit 101 executes the processing of the extension terminal device 4 of this embodiment in accordance with the program stored in the storage unit 102 .

In addition, in the above description, CD-ROM or DVD-ROM is used as the storage medium to provide a program describing the processing in the extended terminal device 4, but it is not limited to this, and it can also be provided according to the architecture of the computer system and the program to be provided. capacity, etc., for example, using a program provided by the transmission medium through the first communication device 103 or the second communication device 104 .

The communication program of this embodiment, for example, causes the extension terminal device 4 to execute steps of controlling multi-hop communication in a multi-hop network with the hub device 2 as the master station; Steps for managing data (upstream data) of the terminal device 3 destined for the hub device 2 and performing protocol conversion on the upstream data from a first communication method to a second communication method different from the first communication method; using the second communication method The protocol-converted uplink data is sent to the next node (peer device) on the uplink path toward the hub device 2 in the multi-hop network.

The protocol conversion processing unit 43, the multi-hop communication control unit 44 and the application processing unit 45 shown in Fig. 3 are realized by the control unit 101 shown in Fig. 20 executing the computer program stored in the storage unit 102 shown in Fig. 20 . To implement the protocol conversion processing unit 43, the multi-hop communication control unit 44 and the application processing unit 45 shown in Fig. 3, the storage unit 102 shown in Fig. 20 is also used. The first communication unit 41 shown in FIG. 3 is realized by the first communication device 103 shown in FIG. 20 , and the second communication unit 42 shown in FIG. 3 is realized by the second communication device 104 shown in FIG. 20 .

The terminal device 3 is realized by, for example, the control unit 101 and the storage unit 102 that constitute a processing circuit, and the first communication device 103 among the components shown in FIG. 20 . The hub device 2 is realized by, for example, the control unit 101 and the storage unit 102 constituting the processing circuit, the first communication device 103, and a third communication device not shown among the components shown in FIG. 20 . The central device 1 is realized by a control unit 101 and a storage unit 102 constituting a processing circuit among the components shown in FIG. 20 , and a third communication device (not shown). In addition, the central device 1 may be a server, etc., may also be implemented by a plurality of computer systems, or may be implemented by a cloud computing system.

As described above, in this embodiment, the extension terminal devices 4-1 and 4-2 perform protocol conversion, thereby enabling communication lines of other communication methods to be used within a part of the wireless multi-hop network. Terminal devices 3 in which communication between terminal devices 3 is difficult can participate in a wireless multi-hop network. Furthermore, when there are a certain number of terminal devices 3 that can communicate with each other on a wireless multi-hop network outside the area where communication between terminal devices 3 is difficult, all of these terminal devices 3 can be replaced with those that can communicate with each other. Terminal devices connected to LTE lines and the like can suppress costs more than when the central device 1 and the like collect data individually. In addition, since the number of terminal devices 3 is less than the maximum accommodated number of line concentrators 2, there is no need to install line concentrators 2, and the cost can be reduced compared to the case of adding additional line concentrators 2.

[Implementation type 2] FIG. 21 is a schematic diagram showing an example of the architecture of the communication system according to Embodiment 2. The communication system 7a of the embodiment 2 includes a central device 1a instead of the hub device 2 and the central device 1, and terminal devices 3-8 to 3-17 instead of the terminal devices 3-1 to 3-7. In addition, the communication system 7a is the same as the embodiment 2. The communication system 7 of state 1 is the same. The central device 1a includes an expansion hub device 2a. The terminal devices 3-8 to 3-17 are each the same as the terminal devices 3-1 to 3-7 in Embodiment 1. If the terminal devices 3-8 to 3-17 are displayed without distinguishing each other, they will be described as the terminal device 3. Components having the same functions as those in Embodiment Type 1 will be assigned the same symbols as those in Embodiment Type 1, and repeated descriptions will be omitted. Hereinafter, the differences from the first embodiment will be mainly explained. The extension terminal devices 4-1 and 4-2 are examples of the first device of this embodiment, and the extension hub device 2a is an example of the second device of this embodiment.

Assume that the terminal devices 3-8 to 3-12 are regarded as one group and the terminal devices 3-13 to 3-17 are regarded as another group. In the example shown in FIG. 21, each terminal device 3 can be in the group. It can communicate with other terminal devices 3 in the surrounding area, but cannot communicate between terminal devices 3 in different groups. Therefore, if this is maintained, it will be difficult to place the terminal devices 3-8 to 3-17 under one hub device. In this implementation mode, the expansion terminal device 4 is installed in each group, and the expansion terminal device 4 and the expansion hub device 2a will use other communication methods that are different from the wireless communication method used between the terminal devices 3 to communicate. By performing protocol conversion, the terminal devices 3-8 to 3-17 can be arranged under one expansion hub device 2a. For example, when there are multiple places where a certain number of terminal devices 3 are gathered, and a line concentrator is installed in all of these places, and the number of terminal devices 3 is much less than the maximum number that the line concentrator can accommodate, Inefficient in terms of cost. In this embodiment, the expansion line concentrator 2a can accommodate the terminal devices 3 in a plurality of locations, so the cost can be suppressed. In addition, in FIG. 21 , two groups are shown, but there may be three or more groups. In this case, the extension terminal device 4 is installed in each group.

In this embodiment, although illustration is omitted in FIG. 21 , the central device 1 a is equipped with the third communication unit 11 and the application processing unit 12 like the central unit 1 of the first embodiment. In this embodiment, the central device 1a further includes a hub device (extension hub device 2a) for extending the terminal device 4. The expansion hub device 2a is a master station (hub device) that constructs a multi-hop network together with a plurality of terminal devices 3 capable of wireless communication using the first communication method. The expansion hub device 2a is connected to the expansion terminal devices 4-1 and 4-2 respectively through the second line 6a using a communication method other than 920Mhz ultra-small wireless communication. The second line 6a may be a mobile phone network such as LTE, a combination of a mobile phone network and a wired line such as an optical line, or a wired line. Although illustration is omitted, the central device 1a may communicate with a hub device other than the expansion hub device 2a, such as the hub device 2 described in Embodiment 1, to collect meter reading data.

FIG. 22 is a schematic diagram showing an architectural example of the expansion hub device 2a in this embodiment. As shown in FIG. 22 , the expansion hub device 2 a includes the same third communication unit 22 , multi-hop communication control unit 23 and application processing unit 24 as the hub device 2 of Embodiment 1, and further includes a protocol conversion processing unit 25 . The third communication unit 22 of this embodiment is an example of a second communication unit that communicates using a second communication method that is different from the first communication method. The protocol conversion processing unit 25 includes a transmission/reception control unit 251, a header generation and connection unit 252, a header division and analysis unit 253, a NW control unit 254, an information storage unit 255, and a distribution unit 256. The functions of the transmission/reception control unit 251, the header generation and connection unit 252, the header division and analysis unit 253, the NW control unit 254, the information storage unit 255 and the distribution unit 256 are respectively the same as those of the transmission/reception control unit 431 and the header generation and connection unit. 432, the header segmentation analysis unit 433, the NW control unit 434, the information storage unit 435 and the distribution unit 436 have the same functions.

Assuming that the second line 6a to which the extension hub device 2a is connected is the same IP network as the communication line through which the central device 1a communicates using the third communication unit 11, there is no need to introduce a new communication line for the extension hub device 2a. to the central device 1a. The following describes an example in which the extension terminal devices 4-1 and 4-2 are connected to the IP network through communication using LTE, and the extension hub device 2a is connected to the IP network. However, the example of the communication line is not limited to this.

In this embodiment, protocol conversion is performed between the extension terminal device 4-1 and the extension terminal device 4-2 and the extension hub device 2a in the same manner as the communication between the extension terminal device 4 in the first embodiment. communication method.

FIG. 23 is a sequence diagram showing an example of the connection process between the extension terminal device 4-2 and the extension hub device 2a in this embodiment. As shown in FIG. 23 , the extension terminal device 4-2 performs steps S1 to S9 in the same manner as the extension terminal device 4-1 of the first embodiment shown in FIG. 6 . However, the destination IP address in the sent information is the address of the extension hub device 2a. After step S9, the second communication unit 42 of the extension terminal device 4-2 sends the NE confirmation message to which the communication path header and the conversion header are added to the extension hub device 2a (step S10a).

After receiving the NW confirmation message with the communication path header and the conversion header added from the extension terminal device 4-2, the third communication unit 22 of the extension hub device 2a proceeds with the steps shown in FIG. 7 of the embodiment 1. In the same manner as S11, the LTE communication information is extracted from the communication path header, and the LTE communication information and the NW confirmation message with the conversion header added are output to the transmission/reception control unit 251 (step S11a). Next, the transmission/reception control unit 251, the header generation and connection unit 252, the header division and analysis unit 253, the NW control unit 254 and the third communication unit 22 of the extension hub device 2a respectively perform operations with the extension terminal device 4 shown in Fig. 7 -2's transmission/reception control unit 431, header generation and connection unit 432, header division and analysis unit 433, NW control unit 434 and second communication unit 42 operate in the same manner. That is, the same processing as steps S12 to S30 shown in FIGS. 7 and 8 will be implemented by the extension hub device 2a and the extension terminal device 4-2. The connection processing is performed similarly between the extension terminal device 4-2 and the extension hub device 2a.

When the connection process between the extension terminal device 4-2 and the extension hub device 2a is completed and the extension terminal device 4-2 determines that it can be connected to the extension hub device 2a, the extension terminal device 4-2 performs the same process as in the first embodiment. Connection processing for wireless multi-hop networks. The connection processing to the wireless multi-hop network in the extension terminal device 4-2 of this embodiment is the same as that in FIGS. 9 to 12 of the first embodiment except that the extension terminal device 4-1 is changed to the extension terminal device 4- 2, and except that the extension terminal device 4-2 is changed to the extension hub device 2a, the rest is the same as the processing shown in FIGS. 9 to 12 of the first embodiment.

FIG. 24 is a sequence diagram showing an example of the notification processing procedure from the extension terminal device 4-2 to the upstream path in this embodiment. Steps S51 to S53 are the same as the processing in FIG. 13 of Embodiment 1. In step S54a, the extension terminal device 4-2 sends the uplink path notification message to the extension hub device 2a. The extension hub device 2a executes steps S111 to S113 in the same manner as steps S55 to S57 executed by the extension terminal device 4-1 in FIG. 13 of Embodiment 1. Thereafter, the expansion line concentrator 2a performs step S114 in the same manner as step S68 in the line concentrator 2 of FIG. 14 .

FIG. 25 is a sequence diagram showing an example of the procedure for sending an application message from the extension terminal device 4-2 in this embodiment. Steps S71 to S73, S52, and S53 are the same as the processing in FIG. 15 of Embodiment 1. In step S54a, the extension terminal device 4-2 transmits the application telegram to which the header is attached to the extension hub device 2a. The extension hub device 2a performs steps S111 to S114 in the same manner as in FIG. 24 . Thereafter, the multi-hop communication control unit 23 of the extension hub device 2a deletes the multi-hop network header (step S115), and outputs the application message with the multi-hop network header deleted to the protocol conversion processing unit 25 (step S116). The protocol conversion processing unit 25 performs allocation judgment (step S117), and outputs the application telegram in which the multi-hop network header is deleted to the third communication unit 22 (step S118).

Thereafter, similarly to the line concentrating device 2 and the central device 1 in FIG. 16 of Embodiment 1, the expansion concentrating device 2a and the central device 1a execute steps S82 to S84. In addition, here, the central device 1a and the extension hub device 2a will use the third communication unit 11 and the third communication unit 22 to communicate. However, since the extension hub device 2a is provided in the central device 1a, steps S82 and S83 may also be replaced. , the protocol conversion processing unit 25 outputs the application telegram after deleting the multi-hop network header to the application processing unit 12 .

FIG. 26 is a sequence diagram showing an example of the notification processing procedure from the terminal device 3-14 to the uplink path in this embodiment. Steps S91 to S95, S52, and S53 are the same as the processes of the terminal device 3-6 and the extended terminal device 4-2 in FIG. 17 of the first embodiment. In step S54a, the extension terminal device 4-2 sends the uplink path notification message to the extension hub device 2a. The extension hub device 2a performs steps S111 to S114 in the same manner as in FIG. 24 . In this way, the extension terminal device 4-2 receives the uplink data sent by the terminal device 3 in the first communication method, performs protocol conversion on the uplink data from the first communication method to the second communication method, and converts the protocol-converted uplink data sent to the expansion hub device 2a. The third communication unit 22 of the extension hub device 2a receives data from the next node (extension terminal device 4-2) on the downstream path in the multi-hop network using a second communication method different from the first communication method, with the terminal device 3 as the transmission source. And the uplink data is destined to the expansion hub device 2a. Then, when the third communication unit 22 receives the uplink data, the protocol conversion processing unit 25 performs protocol conversion on the uplink data from the second communication method to the first communication method.

FIG. 27 is a sequence diagram showing an example of the notification processing procedure from the terminal device 3-14 to the uplink path in this embodiment. Steps S101 to S104, S93 to S95, S52, and S53 are the same as the processing in FIG. 19 of the first embodiment except that the processing of the terminal device 3-6 is changed to the processing of the terminal device 3-14. In step S54a, the extension terminal device 4-2 sends the application telegram to which the header is attached to the extension hub device 2a. The extension concentrator device 2a executes steps S111 to S118 and S82 in the same manner as in FIG. 25 . Since the subsequent processing of the central device 1a is the same as the processing of the central device 1 in FIG. 16 of Embodiment 1, description thereof will be omitted.

In FIG. 23 and FIG. 27 , the processing of the extension terminal device 4-2 is exemplified and explained. However, the extension terminal device 4-1 also performs the same processing as the extension terminal device 4-2. Take this. The expansion hub device 2a can construct a wireless multi-hop network including the expansion terminal devices 4-1 and 4-2, and can communicate with the terminal devices 3-8~3-17.

In addition, in the example shown in FIG. 21 , the extension hub device 2 a is installed in the central device 1 a. However, the present invention is not limited to this, and the extension hub device 2 a and the central device 1 described in Embodiment 1 may be installed separately. Furthermore, the extension concentrator device 2a may have the function of the concentrator device 2 of the first embodiment for communicating with the terminal device 3. In this case, the extension hub device 2a is equipped with the first communication unit 21 like the hub device 2 of the first embodiment, and the allocation unit 256 of the protocol conversion processing unit 25 determines to use the first communication unit 21 according to the transmission destination. To send data, or to use the third communication unit 22 to send data.

The functions of the protocol conversion processing unit 25, the multi-hop communication control unit 23 and the application processing unit 24 of the extension hub device 2a are the same as those of the extension terminal device 4 of the first embodiment. They are described by executing on the processing circuit of the computer system. The processing in the expansion hub device 2a is implemented by a computer program.

In this embodiment, the expansion hub device 2a and the expansion terminal devices 4-1 and 4-2 perform protocol conversion, thereby enabling communication lines using other communication methods to be used in a portion of the wireless multi-hop line, and the terminal devices 3 The terminal device 3 that has difficulty in communication between the two terminals can participate in the wireless multi-hop network. Compared with the case where all terminal devices 3, which are difficult to communicate with each other, are replaced with terminal devices capable of connecting to LTE lines and the like, and a central device, etc. collects data individually, costs can be suppressed. Furthermore, when a certain number of terminal devices 3 are gathered at a plurality of locations and are dispersed, costs can be reduced more than installing line concentrators at all of these locations.

The architecture shown in the above embodiments is only an example, and may be combined with other disclosed technologies or may be a combination between embodiments. The architecture may be omitted or changed without departing from the gist of the invention. a part of.

1,1a: Central unit 2: Line collection device 2a: Expansion hub device 3,3-1,3-2,3-3,3-4,3-5,3-6,3-7,3-8,3-9,3-10,3-11,3-12, 3-13,3-14,3-15,3-16,3-17: terminal device 4,4-1,4-2:Extended terminal device 5: Line 1 6,6a: Line 2 7,7a: Communication system 11,22:3rd Communications Department 12,24,33,45:Application Processing Department 21,31,41: 1st Communications Department 23,32,44:Multi-hop communication control department 25,43: Protocol conversion processing department 42: 2nd Communications Department 101:Control Department 102:Storage Department 103: 1st communication device 104: Second communication device 251,431: Transmission/reception control department 252,432: Header generation connection part 253,433:Header segmentation and analysis department 254,434:NW Control Department (Network Control Department) 255,435:Information Storage Department 256,436:Distribution Department

FIG. 1 is a schematic diagram showing an example of the architecture of the communication system according to Embodiment 1. FIG. 2 is a schematic diagram showing an architectural example of a terminal device according to Embodiment 1. FIG. FIG. 3 is a schematic diagram showing an architectural example of an extension terminal device according to Embodiment 1. FIG. 4 is a schematic diagram showing an architectural example of the line concentrator device according to Embodiment 1. FIG. 5 is a schematic diagram showing an architectural example of the central device according to the first embodiment. FIG. 6 is a sequence diagram showing an example of connection processing between extension terminal devices according to the first embodiment. FIG. 7 is a sequence diagram showing an example of connection processing between extension terminal devices according to the first embodiment. FIG. 8 is a sequence diagram showing an example of connection processing between extension terminal devices according to the first embodiment. FIG. 9 is a sequence diagram showing an example of connection processing to a wireless multi-hop network in the extension terminal device according to Embodiment 1. FIG. 10 is a sequence diagram showing an example of connection processing to a wireless multi-hop network in the extension terminal device according to Embodiment 1. FIG. 11 is a sequence diagram showing an example of connection processing to a wireless multi-hop network in the extension terminal device according to Embodiment 1. FIG. 12 is a sequence diagram showing an example of connection processing to a wireless multi-hop network in the extension terminal device according to Embodiment 1. FIG. 13 is a sequence diagram showing an example of the notification processing procedure from the extension terminal device to the uplink path according to the first embodiment. FIG. 14 is a sequence diagram showing an example of the notification processing procedure from the extension terminal device to the uplink path according to the first embodiment. FIG. 15 is a sequence diagram showing an example of a processing procedure for transmitting an application message from an extension terminal device according to Embodiment 1. FIG. 16 is a sequence diagram showing an example of a processing procedure for transmitting an application message from an extension terminal device according to Embodiment 1. FIG. 17 is a sequence diagram showing an example of the notification processing procedure from the terminal device to the uplink path according to the first embodiment. FIG. 18 is a sequence diagram showing an example of the notification processing procedure from the terminal device to the uplink path according to the first embodiment. FIG. 19 is a sequence diagram showing an example of a processing procedure for transmitting an application message from a terminal device according to Embodiment 1. FIG. 20 is a schematic diagram showing an architectural example of a computer system that implements the extended terminal device according to Embodiment 1. FIG. 21 is a schematic diagram showing an example of the architecture of the communication system according to Embodiment 2. FIG. 22 is a schematic diagram showing an architectural example of an expansion hub device according to Embodiment 2. FIG. 23 is a sequence diagram showing an example of connection processing between the extension terminal device and the extension hub device according to the second embodiment. FIG. 24 is a sequence diagram showing an example of the notification processing procedure from the extension terminal device to the uplink path according to the second embodiment. FIG. 25 is a sequence diagram showing an example of a processing procedure for transmitting an application message from an extension terminal device according to Embodiment 2. FIG. 26 is a sequence diagram showing an example of the notification processing procedure from the terminal device to the uplink path according to the second embodiment. FIG. 27 is a sequence diagram showing an example of a processing procedure for transmitting an application message from a terminal device according to Embodiment 2.

4:Extended terminal device

41: 1st Communications Department

42: 2nd Communications Department

43: Agreement conversion processing department

44:Multi-hop communication control department

45:Application Processing Department

431:Sending/receiving control department

432: Header generation connection part

433:Header segmentation analysis department

434:NW Control Department

435:Information Storage Department

436:Distribution Department

Claims (11)

An extended terminal device, including: The first communication unit is capable of communicating by the first communication method with at least some of the terminal devices among the plurality of terminal devices that can perform wireless communication with the first communication method; The second communication unit is capable of communicating by a second communication method that is different from the first communication method; The multi-hop communication control unit controls multi-hop communication in a multi-hop network with the hub device as the main station; and The protocol conversion processing unit, when the first communication unit receives data destined for the hub device that manages the terminal device, that is, uplink data, converts the uplink data from the first communication method to the Protocol conversion of the second communication method, The second communication part sends the uplink data converted by the protocol to the next node on the uplink path toward the hub device in the multi-hop network, that is, the peer device. The peer device The uplink data performs protocol conversion from the second communication method to the first communication method. For example, the extended terminal device of claim 1, wherein the peer device sends the uplink data converted by the protocol to the hub device through the first communication method. The extended terminal device of claim 1, wherein the peer device is the hub device. For example, the extended terminal device according to any one of claims 1 to 3, wherein the protocol conversion processing unit appends a conversion header including the identification information of the extended terminal device to the upstream data as a link from the first communication method to The protocol conversion process of the second communication method. A line concentrating device that constructs a multi-hop network with a plurality of terminal devices capable of wireless communication using the first communication method and becomes the master station of the multi-hop network. The line concentrating device includes: The second communication unit is capable of receiving, using a second communication method different from the first communication method, from the next node of the downlink path in the multi-hop network, that is, the extended terminal device, with the terminal device as the transmission source and Uplink data destined for this hub device; The multi-hop communication control unit controls multi-hop communication in the multi-hop network; and The protocol conversion processing unit, when the second communication unit receives the uplink data, performs protocol conversion on the uplink data from the second communication method to the first communication method, The extended terminal device receives the uplink data using the first communication method, performs protocol conversion on the uplink data from the first communication method to the second communication method, and sends the protocol-converted uplink data to the hub device. Send. A communication system including: a first device and a second device, The first device includes: The first communication unit is capable of communicating by the first communication method with at least some of the terminal devices among the plurality of terminal devices that can perform wireless communication with the first communication method; The second communication unit is capable of communicating by a second communication method that is different from the first communication method; The multi-hop communication control unit controls multi-hop communication in a multi-hop network with the hub device as the main station; and The protocol conversion processing unit, when the first communication unit receives data destined for the hub device that manages the terminal device, that is, uplink data, converts the uplink data from the first communication method to the terminal device. Protocol conversion of the second communication method, The second communication part sends the uplink data converted by the protocol to the next node on the uplink path toward the hub device in the multi-hop network, that is, the second device, and the second device The uplink data performs protocol conversion from the second communication method to the first communication method. For example, the communication system of claim 6, wherein the second device sends the uplink data converted by the protocol to the hub device through the first communication method. The communication system of claim 6, wherein the second device is the hub device. If the communication system of any one of items 6 to 8 is requested, the first device appends a conversion header including the identification information of the first device to the upstream data as a link from the first communication method to the first device. 2. The protocol conversion processing of communication methods, The first device removes the conversion header as the protocol conversion process from the second communication method to the first communication method. A communication method for communicating with at least part of a plurality of terminal devices capable of wireless communication using the first communication method using the first communication method, the communication method comprising: Control multi-hop communications in a multi-hop network with the hub device as the main station; When data destined for the hub device that manages the terminal device is received from the terminal device using the first communication method, that is, uplink data, the uplink data is transferred from the first communication method to the first communication method. Protocol conversion of different second communication methods; and Use the second communication method to send the uplink data converted by the protocol to the next node on the uplink path toward the hub device in the multi-hop network, that is, the peer device, The peer device performs protocol conversion on the uplink data from the second communication method to the first communication method. A storage medium that stores a program that performs the following steps: For an expansion terminal device that communicates with at least a part of a plurality of terminal devices capable of wireless communication using the first communication method by the first communication method, the multi-hop network with the hub device as the main station is performed. Control of multi-hop communications; When data destined for the hub device that manages the terminal device is received from the terminal device in the first communication method, that is, uplink data, the uplink data is transferred from the first communication method to the first communication method. Protocol conversion of the second communication method in a different manner; and Use the second communication method to send the uplink data converted by the protocol to the next node on the uplink path of the hub device in the multi-hop network, that is, the peer device, The peer device performs protocol conversion on the uplink data from the second communication method to the first communication method.

Images