JP6397711B2 - Extension method of remote unit in remote management system - Google Patents

Description

  The present invention relates to a remote management system including a parent device, a child device, and a center device, and more particularly to a child device addition method in a remote management system that can increase the maximum number of connection stages without affecting existing child devices.

Conventionally, for example, as a remote management system for metering the usage amount of gas, water, etc., a slave unit equipped with a meter meter, a master unit wirelessly connected to the slave unit, and a master unit with, for example, a telephone line A remote management system comprising a center device connected via a public line is known (Patent Document 1).
In a conventional remote management system, a slave unit is connected to a master unit using a specific low-power radio, and the master unit is connected to a center device using, for example, a mobile phone line. The master unit has a structure in which a plurality of slave units are connected in multiple layers in a hierarchical manner.

  Each slave unit is arranged so as to constitute one layer for each distance unit of, for example, about 100M from the master unit. The number of slave units is limited to a fixed number of steps (for example, three) at the system design stage of the remote management system, and the center device includes communication route information composed of the master unit and the slave unit, the number of stages of the slave unit, Each slave unit stores communication partner information (slave unit ID) and the number of stages for each route of the terminal itself.

  In such a remote management system in which the number of stages is limited in advance, the simplest method for adding a slave unit is to add a master unit and connect the slave unit to the master unit. However, since the base unit uses a commercial line (such as a mobile phone line), the unit price (cost per unit) is high. Therefore, this method is difficult to employ when cost is important.

  As another method, it can be considered that the number of connection stages can be newly increased by removing the stage number limitation in the remote management system. However, in order to change the maximum limit number of steps of the existing remote management system, it is necessary to change the settings of the entire system, that is, to upgrade the version of each terminal (parent device, child device). In this case, the version of the master unit can be upgraded by remote operation from the center side, but the version of the slave unit cannot be upgraded by remote control because of the specific low power radio. Therefore, it is necessary for the worker to go to the actual installation location of the slave unit and upgrade the slave unit software one by one. Therefore, this method is difficult to employ due to the problem of complicated work and high cost.

Japanese Patent Publication No. 2006-245666

  The present invention has been made in view of the above-described conventional problem in the case of adding a slave unit in an existing remote management system with a limited number of stages, and its purpose is to affect the existing system such as version upgrade. It is to reduce the number of slave units as much as possible, and at a lower cost compared to the case of adding a master unit, and to easily increase the number of slave units.

The present invention relates to a remote management system comprising a center device, a parent device connected to the center device via a public line, and a plurality of slave devices wirelessly connected to the parent device in a multi-tier hierarchy limited in number of steps. A method of adding a slave unit in the method, the step of connecting a relay terminal at the 0th level in the hierarchy to the master unit, and the step of connecting the second and subsequent slave units in an existing remote management system to the relay terminal And changing the number of stages of the slave unit connected to the relay terminal to the first stage to relax the stage number limitation in the communication route passing through the slave unit by at least one stage, and the master unit and the plurality of stages Storing the communication route between the slave units connected in the hierarchy in the storage unit in the storage unit of the center device and connecting the second and subsequent slave units in the existing remote management system to the relay terminal In the apparatus, the slave unit Stages wherein determining a communication route through the relay terminal includes a step of registering by changing the number of stages of the slave unit in the communication route to the first stage, and in the communication route, which corresponds to the number of stages that the relaxed This is a method of adding a slave unit in a remote management system that can add molecular units.

  According to the present invention, in an existing remote management system with a limited number of stages, the influence on the existing system is reduced as much as possible, and the number of slave units can be easily increased at a lower cost than in the case of adding a master unit. Can be stepped.

FIG. 1A is a diagram for explaining the outline of an existing remote management system, and FIG. 1B is a diagram for explaining the outline of a remote management system showing a state in which slave units are added based on the slave unit extension method according to the present embodiment. FIG. 2A to 2E are diagrams for explaining the outline of the connection method of the slave units in the remote management system. FIG. 3A is a flowchart showing a processing procedure for connecting a relay terminal (child 0) to an existing remote management system and reducing the number of stages in the new communication route of the slave unit (child 2) connected thereto by one stage. FIG. FIG. 3B is a diagram illustrating a state in which a relay terminal is installed. FIG. 3C is a diagram illustrating an updated communication route in which the relay terminal (child 0) is installed. It is a figure which shows the communication route of the existing system. It is a figure which shows the content of the route information table about the communication route of FIG. It is a figure which shows the communication route of the state which joined the relay terminal (child 0) to the communication route shown in FIG. It is a figure which shows the content of the route information table about the communication route of FIG. It is a figure which shows the route information table after an update.

Next, a remote management system according to an embodiment of the present invention will be described with reference to the drawings.
Prior to detailed description of the connection method of the slave unit in this remote management system, an outline thereof will be described first.

  FIG. 1A is a diagram illustrating an outline of an existing remote management system. This remote management system includes a parent device 10 and a child device 20 (child device (child 1) to child device (child 3) connected here in three stages; however, the numerical values of child 1 and child 2 will be described later. The number of stages registered in the storage unit of the center device and the storage unit of the child device itself), the center 30 (center device 32), and a commercial communication network 40 such as a telephone line connecting the parent device 10 and the center 30; It is made up of. FIG. 1B is a diagram of a remote management system showing a state in which slave units are added within a limit on the number of slave units in an existing remote management system based on a slave unit extension method in the remote management system according to the present embodiment described below. It is a figure explaining an outline.

As is clear when FIG. 1A and FIG. 1B are compared, in FIG. 1B, the slave unit has a configuration in which one stage is added compared to FIG. 1A. However, in this embodiment, a slave unit (also referred to as a relay terminal) (slave 0) connected between the slave unit (slave 1) and the master unit 10 is a system in this remote management system (hereinafter simply referred to as a system). This is not included in the number of stages, but is handled as 0 stages for convenience, so that the problem of restriction of the number of slave units in the remote management system is solved.
That is, a relay terminal (child 0) is connected to the parent device 10 in the existing communication route, and the second child device (child 2) on the existing communication route is connected to the relay terminal (child 0). When a communication route is newly established by connecting, the number of stages on the system of the connected slave unit (slave 2) counts up from the master unit 10 to the first level. Similarly, since the third-stage child device is moved up to the second stage, a new child device can be connected to the lower rank as the third stage of the connection route.

2A to 2E are diagrams for explaining the outline of the connection method of the slave units in the remote management system described above.
That is, FIG. 2A is a diagram illustrating a connection relationship between the parent device 10 and the child device 20 in the existing remote management system. The child machine (child 1) shows the first stage, and the child machines (child 2-1 and 2-2) show the second stage.
In this remote management system, it is assumed that a radio wave unstable state has occurred between the slave unit (slave 1) and the slave unit (slave 2-2). In this embodiment, as shown in FIG. 2B, a relay terminal (child 0) is arranged, route search is performed, and a new connection route for the child machine (child 2-2) is formed.
That is, this relay terminal (child 0) is connected between the parent device 10 and the child device (child 2-2) as shown in FIG. 2C. However, this relay terminal is registered as a 0-stage relay terminal (child 0) without adding to the number of stages in the system.

  When the relay terminal (child 0) is connected between the parent device 10 and the child device (child 2-2), the child device (child 3) connected to the lower level of the child device (child 2-2) remains as a child. Connected to the machine (child 2-2). As already described, the relay terminal (child 0) is not registered as the first stage in the existing system, is registered as out of the number of stages, that is, as zero stage, and is not included in the number of stages in the existing remote management system. Therefore, as shown in FIG. 2D, after the slave unit (child 2-2) is connected to the relay terminal (slave 0), the number of stages is rewritten in the communication route, and the slave unit (slave 3) is also the same. The number of steps is rewritten as the slave unit (slave 2).

  FIG. 2E shows a state in which a child device (child 3) is newly connected to a lower level of the child device (child 2). That is, when the child device (child 3), which is the uppermost third level (hierarchy) in the existing hierarchy, is connected to the communication route passing through the relay terminal (child 0), the second level in the communication route is obtained. It is shown that a child device (child 3) can be newly added as a third layer below it because it has been changed to the eyes (number of steps rewritten). In this case, the hierarchical structure of other slave units is not changed at all.

Next, in order to add the new slave unit described above, the relay terminal (child 0) is connected to the existing remote management system, and the existing slave unit is connected to the connected relay terminal (child 0). A specific procedure for connecting and changing the communication route will be described.
FIG. 3A is a flowchart showing a processing procedure for connecting a relay terminal (child 0) to an existing remote management system and reducing the number of stages in the new communication route of the slave unit (child 2) connected thereto by one stage. FIG.

  First, as shown in FIG. 3B, a relay terminal (child 0) is newly installed in the existing system (S101). Next, a matching process (operation for storing and registering terminal identification information such as the wireless device ID of each other in the memory of the own terminal) is performed between the parent device 10 and the relay terminal (child 0) (S102). After the match is completed, the relay terminal (child 0) transmits the match information to the center device 32 via the parent device 10 (S103). When the center device 32 receives the relationship information between the terminal (child 0) and the parent device 10 from the relay terminal (child 0), the center device 32 determines and stores the communication route based on the information (S104). Next, the slave unit (slave 2) for connecting to the new communication route is selected, and the matching process is performed between the relay terminal (slave 0) and the slave unit (slave 2) (S105).

The child device (child 2) transmits the edge information of the edge established with the relay terminal (child 0) to the center device 32 via the relay terminal (child 0) and the parent device 10 (S106). When the center device 32 receives the association information between the child device (child 2) and the relay terminal (child 0) transmitted from the child device (child 2), the center device 32 determines and stores a communication route based on the information (S107). .
The center device 32 transmits route information in order from each upstream terminal (master unit, relay terminal (child (0)), slave unit (child (2), child (3)) on the determined communication route, The transmission destination is changed and the number of stages is rewritten (S108).

The parent device 10, the relay terminal (child 0), the child device (child 2), and the child device (child 3) that have received the communication route information each store communication route information related to the own terminal in the storage unit of the own terminal. At the same time, the child device (child 2) and the child device (child 3) rewrite the number of stages stored (saved) in their own terminals from 2 to 1, and 3 to 2, respectively, and the process ends.
FIG. 3C shows an updated communication route in which the relay terminal (child 0) is installed in this way.
In the above processing procedure, the center device 32 determines the route and stores the route. However, the parent device may determine the route and hold the route.

Next, a route information table of terminals in the storage unit of the center 30 will be described.
4 shows the communication route of the existing system, and FIG. 5 shows the contents of the route information table for the communication route of FIG.
As shown in FIG. 5, the child device (child 1) is connected to the parent device 10 in the first stage in the communication route 1 (hereinafter referred to as route 1). The slave unit 2 a is connected to the slave unit 1 as the second stage in the route 1 and connected to the slave unit Q as the third stage in the route 2. In the route 1, the child device 2 b is the child device 1 as the second step in the route 1, the child device P as the second step in the route 2, the child device X as the second step in the route 3, and the child device as the third step in the route 4. Y is connected to the slave unit Z as the third stage in the route 5. The handset 3 is connected to the handset 2b as the third stage in the route 1. Similarly, for each slave unit, the number of steps is registered together with the routes 1 to 5 together with the routes.

In the above description, each slave unit is assumed to hold its own terminal connection destination (communication partner) information (connection destination ID) and stage number information in the storage unit of its own terminal. The terminal may be held by the terminal device, or may be temporarily held by the terminal according to an instruction from the center device 32.
For example, the child device “child device 2b” holds “child device 1 (child 1)” as a connection destination (route) of the main (main route 1), but is connected to “child device 1 (child 1)”. For cases where this is not possible, four other connection destinations are held.

6 shows a communication route in a state where a relay terminal (child 0) has joined the communication route shown in FIG. 4, and FIG. 7 shows the contents of the route information table for the communication route of FIG.
As shown in the figure, the relay terminal (child 0) is connected directly above the upper child machine 2b. In this state, as shown in FIG. 7, the handset 2 b is connected to the relay terminal (child 0) as the first stage in the route 1. Further, the relay terminal (child 0) is registered in the route information table as being connected to the base unit 10 as the 0th stage in the route 1.

That is, in route 1 of handset 2b, the relay terminal (child 0) has become a higher order terminal, so the number of stages of the own terminal is changed from 2 to 1. As a result, the route of parent 10 → relay terminal (child 0) → child machine (child 2) → child machine (child 3) has the number of stages (parent → 0 → 1 → 3). The number of stages registered in the route information table in route 1 connected to the child device 2b of (child 3) remains 3 because it has not yet been updated.
However, since the number of stages of the child device 3 remains three as it is, the child device cannot be connected to the subordinate of its own terminal. Therefore, in order to connect the slave unit under the slave unit 3, it is necessary to update the number of stages of the slave unit 3 to 2 or less.

Since the center device 32 holds information of parent → slave device 0 → slave device 2b → slave device 3 as a route information table, it can be seen that the exact number of stages is parent → 0 → 1 → 2. Based on this information, the route information table is updated.
FIG. 8 shows the route information table after the update.
Here, the route 1 of the child device (child 3) is changed to be connected to the child device 2b as the second stage.
After updating the route information table in this way, the center device 32 instructs each related slave unit to update the stage number information stored in the storage unit based on the update information. Here, the slave unit (child 3) is instructed to update the stage number information to 2.
As a result, since the slave unit (slave 3) can recognize that its own terminal is not in the third stage, the slave unit (slave 3) can be connected to the subordinates, and a practically four-stage configuration is possible as a system.

As described above, according to the present embodiment, when the relay terminal is arranged directly below the master unit without changing the number of stages of the entire remote management system, and the existing slave unit is connected to the relay terminal, New slave units can be added simply by updating the number of existing slave units on the route passing through the relay terminal.
Further, in the above description, a case has been described in which a new slave unit is connected directly below a slave unit that is the third stage in the existing route. However, the present invention is not limited to this, and for example, two stages in the existing route. A new slave unit can be connected between the eyes and the third stage.
That is, in this case, the second-stage slave unit (child 2) is connected to the relay terminal, the number of stages in the communication route is changed to one, the new terminal is connected as the second stage in the route, and the third-stage child is connected. The machine can be connected as it is under the new second-stage child machine.

As described above, the embodiment of the connection method of the slave unit in the remote management system of the present invention has been described. However, according to the present embodiment, the relay terminal is arranged directly below the master unit, and the existing slave unit is connected thereto. Thus, the number of slave units on the communication route passing through the relay terminal can be reduced. In this case, the number of slave units on the communication route that does not pass through the relay terminal remains unchanged, and is not affected at all by the installation of the relay terminal.
Therefore, by adopting the connection method of the slave unit in this embodiment, it is possible to freely add a slave unit in the existing remote management system without requiring a low-cost and complicated work.

  DESCRIPTION OF SYMBOLS 10 ... Master machine, 20 ... Slave machine, 30 ... Center, 32 ... Center apparatus, 40 ... Commercial communication network.

Claims (3)

A slave device in a remote management system comprising a center device, a master device connected to the center device via a public line, and a plurality of slave devices wirelessly connected to the master device in a multi-tier hierarchy limited in number of stages Expansion method,
Connecting a relay terminal that is 0 level above the hierarchy to the base unit;
Connecting the second and subsequent slave units in the existing remote management system to the relay terminal;
Changing the number of stages of the slave unit connected to the relay terminal to the first stage, and relaxing the stage number limit in the communication route passing through the slave unit by at least one stage ;
Storing a communication route between the parent device and the child devices connected at the plurality of levels in a storage unit of a center device;
When connecting the second and subsequent slave units in the existing remote management system to the relay terminal,
In the center device, determining a communication route through the relay terminal of the slave unit, changing the number of stages of the slave unit in the communication route to the first stage, and registering ,
A method of adding slave units in a remote management system in which the number of molecular machines corresponding to the relaxed number of stages can be added in the communication route. In the extension method of the subunit | mobile_unit in the remote management system described in Claim 1,
When the center device changes and registers the number of stages in the communication route passing through the relay terminal of the slave unit to the first stage, route information is transmitted to the slave unit connected to the communication route passing through the slave unit. Sending, and
In the slave unit that has received the route information, the step of changing the number of stages stored in the storage unit of the slave unit based on the route information ;
Method of adding a slave unit in a remote management system having a personal computer. In the extension method of the subunit | mobile_unit in the remote management system described in Claim 1 or 2,
The storage unit of the center device stores, for each slave unit, the route and number of stages to which the slave unit belongs,
The storage unit of the slave unit is a method of adding a slave unit in a remote management system that stores communication partner information of the slave unit and the number of stages of the slave unit.

Images