WO2017217476A1 - Terminal for remote monitoring system, program for remote monitoring, and remote monitoring system - Google Patents

Abstract

[Problem] To provide a remote monitoring system that allows a user terminal device to access, at a desired timing, a plurality of terminals connected to the Internet through an Internet Server Provider. [Solution] A remote monitoring system 1 is equipped with: a plurality of terminals 4 connected to the Internet 5 via an Internet Server Provider 6 having a global IP address, each being assigned a private IP address; a cloud server 2 connected to the Internet 5; and user terminal devices (3a, 3b) connected to the cloud server 2. The cloud server 2 assigns a first connection port to one terminal from among the plurality of terminals 4 and assigns a second connection port to the user terminal devices (3a, 3b). The one terminal and the user terminal devices (3a, 3b) communicate via the first connection port, the second connection port, and the cloud server 2.

Description

Remote monitoring system terminal, remote monitoring program, and remote monitoring system

The present invention relates to a remote monitoring system that monitors various terminals connected via the Internet or the like, and more particularly to a remote monitoring system that enables connection with various terminals to be monitored at an arbitrary timing.

In recent years, technology called IoT (Internet of Things: hereinafter referred to as IoT) and the Internet of Things has attracted attention, including fields such as monitoring. IoT is a mechanism in which a uniquely identifiable computer or device is connected to the Internet, and devices mutually control each other by exchanging information. Here, the device includes all things such as measuring devices such as various sensors, surveillance cameras, and devices for daily life such as air conditioners and cooking devices.

In IoT, for example, in an information processing system called Industrial Internet, devices and people can be connected, data can be acquired in real time, and actions based on this can be performed to improve device operation efficiency. The effect of reducing human waiting time is expected.

As a technique related to IoT, for example, techniques described in Patent Document 1 and Patent Document 2 have been proposed.

In Patent Document 1, a workflow management device holds a transition condition from each stage to the next stage and stage information indicating the current stage of the workflow for a workflow that controls the operation of an IoT device over a plurality of stages. There is a partial order relationship between the stages, the first stage and the second stage cannot be compared, and the third stage can be executed next to the first stage, but the third stage cannot be compared with the second stage. If possible, the workflow management device determines that the workflow is the third stage after the first stage when the transition condition of the first stage is satisfied but the transition condition of the second stage is not satisfied. And the technique of updating stage information to show that it is also a 2nd stage is disclosed. Here, the stage is a temperature collection stage, an average temperature calculation stage, an energy accounting calculation stage, or the like.

Patent Document 2 also deploys a device configuration when a complete solution template is selected upon selection of a solution template for a specific automatic interaction device configuration between two or more IoT devices. To do. Otherwise, receive IoT device selection, access device functions in the IoT database of the selected IoT device, set up a network connection between the selected IoT devices, and simulate the device configuration in the IoT database Determine whether the device configuration is available. Techniques are disclosed for reconfiguring a device configuration to include an alternative IoT device if it is not available and deploying the device configuration if it is available. Here, the device configuration is to establish a communication connection between two or more IoT devices via a network.

Japanese Patent Laying-Open No. 2015-204033 Japanese Unexamined Patent Publication No. 2016-45964

However, Patent Document 1 only discloses a workflow management apparatus that controls the operation of an IoT device over a plurality of stages. In other words, the IoT device transmits the status of the device to be monitored via the Internet service provider (ISP) to the cloud server via the Internet, and the cloud server holds the device to be monitored. From the viewpoint of application to a remote monitoring system that periodically (predetermined) transmission to a user terminal device of an operator or a business operator who undertakes maintenance of equipment to be monitored.

Generally, in such a remote monitoring system, a plurality of terminals (IoT devices) connected to an Internet service provider (ISP) having one global IP address have different private IP addresses, respectively. The number of events assigned by is increasing significantly. Therefore, if access to a plurality of terminals (IoT devices) is required from the user terminal device, the user terminal device can access the Internet service provider (ISP) via the Internet, but the Internet service provider ( The private IP addresses assigned to a plurality of terminals (IoT devices) connected to the ISP) are not acquired, and it is difficult to access the plurality of terminals (IoT devices) at a desired timing. In Patent Document 1, no consideration is given to dealing with such a situation.

Further, in Patent Document 2, although communication connection between two or more IoT devices can be established with each other, as described above, in the remote monitoring system, the user terminal device is temporarily connected to a plurality of terminals (IoT devices). When access is required, the user terminal device is accessible to the Internet service provider (ISP) via the Internet, but is assigned to a plurality of terminals (IoT devices) connected to the Internet service provider (ISP). It is difficult to access a plurality of terminals (IoT devices) at a desired timing without acquiring a private IP address. In Patent Document 2, no consideration is given to dealing with such a situation.

SUMMARY OF THE INVENTION An object of the present invention is to provide a remote monitoring system terminal, a remote monitoring program, and remote monitoring that can be accessed from a user terminal device at a desired timing to a plurality of terminals connected to the Internet via an Internet service provider. To provide a system.

In order to solve the above problems, a remote monitoring system of the present invention is connected to the Internet via a plurality of terminals assigned with private IP addresses and connected to the Internet via an Internet service provider having a global IP address. A cloud server and a user terminal device connected to the cloud server, wherein the cloud server assigns a first connection port to one terminal of the plurality of terminals, and the user terminal device includes a second connection port. The one terminal and the user terminal device communicate with each other via the first connection port, the second connection port, and the cloud server.

In another aspect of the remote monitoring system of the present invention, the cloud server randomly assigns the first connection port and the second connection port to the one terminal and the user terminal device, respectively. And

Still further, another aspect of the remote monitoring system of the present invention is characterized in that the user terminal device transmits a connection request to one terminal of the plurality of terminals to the cloud server.

In the remote monitoring system of the present invention, the cloud server assigns a different first connection port to the plurality of terminals for each connection request to one terminal among the plurality of terminals transmitted from the user terminal device. And a connection port assigning unit for assigning a different second connection port to the user terminal device.

According to another aspect of the remote monitoring system of the present invention, the cloud server includes: the one terminal to which the first connection port is assigned; and the user terminal device to which the second connection port is assigned. It has a connection time management part which makes it possible to continue communication for a predetermined time.

In addition, according to another aspect of the remote monitoring system of the present invention, the user terminal device has at least one IP address, one of the plurality of terminals to be connected, and a connection time to the cloud server. It is characterized by transmitting.

According to another aspect of the remote monitoring system of the present invention, the connection time management unit is configured to pass the first connection port and the second connection port when the connection time transmitted from the user terminal device has elapsed. The communication between one terminal and the user terminal device is cut off.

According to another aspect of the remote monitoring system of the present invention, the plurality of terminals are connected to a measuring device and / or an imaging device by wire or wireless, respectively, and the target terminal or target device measured by the measuring device. The measurement value and / or image data of the target terminal or target device imaged by the imaging device is transmitted to the cloud server via the Internet service provider and the Internet at a predetermined cycle.

According to another aspect of the remote monitoring system of the present invention, the user terminal device transmits a connection request to a lower device connected to one terminal of the plurality of terminals to the cloud server, When the terminal receives the connection request from the cloud server, the terminal connects communication with the user terminal device to the lower-level device.

According to another aspect of the remote monitoring system of the present invention, the user terminal device is a terminal selection screen for selecting one terminal of the plurality of terminals, and one terminal selected on the terminal selection screen. When a lower-level device connected to the one terminal is selected as a connection destination on the connection-destination selection screen, the cloud server is connected to the lower-level device. The connection request is transmitted.

The remote monitoring system terminal of the present invention is connected to the Internet via an Internet service provider having a global IP address, and is a plurality of terminals assigned with private IP addresses. The terminal is connected via a cloud server and the Internet. A first connection port different from a second connection port assigned to the user terminal device by the cloud server and assigned to the user terminal device via the cloud server, It is possible to communicate with the user terminal device via the first connection port and the second connection port.

In another aspect of the remote monitoring system terminal of the present invention, a first connection port different from a second connection port assigned to the user terminal device by the cloud server is randomly assigned. .

Still further, another aspect of the remote monitoring system terminal of the present invention is to continuously communicate with the user terminal device to which the second connection port has been assigned for a predetermined time via the first connection port. It is characterized by.

According to another aspect of the remote monitoring system terminal of the present invention, a tunneling connection that communicates with the user terminal device to which the second connection port is assigned via the first connection port has elapsed for a predetermined time. It is characterized by having a tunneling connection disconnection execution unit that sometimes disconnects.

Further, according to another aspect of the remote monitoring system terminal of the present invention, when the terminal is connected to a lower level device and receives a connection request from the cloud server to the lower level device, the user terminal device and the terminal It is possible to communicate with a lower device.

The remote monitoring program of the present invention assigns a first connection port to one terminal among a plurality of terminals assigned a private IP address, which is connected to the Internet via an Internet service provider having a global IP address, Allocating a second connection port to a user terminal device connected to the cloud server connected to the Internet, and causing a processor to execute a function of randomly assigning the first connection port and the second connection port. Features.

According to another aspect of the program for remote monitoring of the present invention, communication between one terminal assigned with the first connection port and a user terminal device assigned with the second connection port is continued for a predetermined time. A function to be executed by a processor.

According to the present invention, there are provided a remote monitoring system terminal, a remote monitoring program, and a remote monitoring system, which are accessible from a user terminal device to a plurality of terminals connected to the Internet via an Internet service provider at a desired timing. It becomes possible to provide.

Issues, configurations, and effects other than those described above will be clarified by the following description of the embodiments.

1 is an overall schematic configuration diagram of a remote monitoring system according to an embodiment of the present invention. It is a functional block diagram of the cloud server shown in FIG. It is a functional block diagram of the terminal shown in FIG. It is a functional block diagram of the user terminal device shown in FIG. It is a schematic sequence diagram of the remote monitoring system shown in FIG. It is a schematic sequence diagram of the remote monitoring system shown in FIG. It is a schematic sequence diagram of the remote monitoring system shown in FIG. It is a schematic sequence diagram of a remote monitoring system when a user (user) directs disconnection. It is a schematic sequence diagram of the remote monitoring system at the time of the cutting | disconnection by a timer function. It is a flowchart which shows the processing flow of the cloud server shown in FIG. It is a flowchart which shows the processing flow of the terminal shown in FIG. It is a flowchart which shows the processing flow of the user terminal device shown in FIG. It is a figure which shows an example of the screen in the modification of the remote monitoring system shown in FIG.

In this specification, a “remote monitoring system” is a system that monitors the state of a target terminal or target device and / or provides maintenance for the target terminal or target device or information related to maintenance. Remote maintenance system (remote maintenance system) "and" remote monitoring system ".

Embodiments of the present invention will be described below with reference to the drawings.
FIG. 1 is an overall schematic configuration diagram of a remote monitoring system according to an embodiment of the present invention. As shown in FIG. 1, the remote monitoring system 1 includes a user terminal device 3a that is a personal computer owned by a user (user) 3, a user terminal device 3b such as a smartphone (mobile phone) or a tablet, and a router 3c. , A cloud server 2, a remote monitoring system terminal 4 including a plurality of terminals 4 a to 4 c, the Internet 5, and an Internet service provider (ISP) 6.

The cloud server 2 is a server that is virtually constructed by connecting a plurality of servers, and FIG. 1 shows an example in which the cloud server 2 is constructed by connecting three servers. The cloud server 2 only needs to be constructed by a plurality of servers, and is not limited to the three servers shown in FIG. 1, and the number of the servers is set as appropriate.

The user terminal device 3a and the user terminal device 3b are connected to the cloud server 2 via a router 3c or a general public line. The user terminal device 3a, the user terminal device 3b, and the router 3c are connected to each other by, for example, Wi-Fi (registered trademark of Softbank BB Corp.) or a wired LAN (Local Area Network).

A terminal 4 including a plurality of terminals 4a to 4c, which will be described in detail later, is connected to a camera or a measuring device (not shown) which is a lower device, respectively, by wire or wirelessly, and image data or measuring device imaged by the camera Various measured values (hereinafter, unless otherwise specified, image data or various measured values are simply referred to as “various measured values”), for example, an Internet service provider (ISP) 6 by wireless communication such as a 3G line. At a predetermined cycle.

The Internet service provider (ISP) 6 transmits various measurement values received from the terminal 4 including the plurality of terminals 4 a to 4 c to the cloud server 2 via the Internet 5. That is, in the remote monitoring system 1 shown in FIG. 1, various measured values are transmitted from the terminal 4 to the cloud server 2 via the Internet service provider (ISP) 6 and the Internet 5 in a predetermined cycle by IoT on the uplink. The system configuration to be performed is shown as an example.

Further, the desired terminal 4 is sent from the user terminal device 3a or the user terminal device 3b to the cloud server 2 at a timing at which various measured values are transmitted from the terminal 4 at a predetermined cycle on the uplink or at a different timing. An access request for access to (that is, a connection request to one of a plurality of terminals) is transmitted.

In response to the access request, the cloud server 2 randomly assigns connection ports to the user terminal device 3a or the user terminal device 3b and one of the terminals 4a to 4c constituting the terminal 4. The tunneling 7 enables communication between the user terminal device 3a or the user terminal device 3b and one of the terminals 4a to 4c constituting the terminal 4 via the Internet 5 and the Internet service provider (ISP) 6. To do.

When the tunneling 7 connects the user terminal device 3a or the user terminal device 3b and one of the terminals 4a to 4c constituting the terminal 4 via the cloud server 2 so that they can communicate with each other, for example, Since SSH (Secure Shell) connection is established, communication on all networks including an authentication part such as a password is encrypted, and it becomes possible to communicate safely.

In addition, a global IP address (Global Internet Protocol Address) is uniquely assigned to the Internet service provider (ISP) 6. A plurality of terminals 4a, 4b, and 4c constituting the terminal 4 connected to the Internet service provider (ISP) 6 by wireless communication such as a 3G line are respectively connected to the private IP by the Internet service provider (ISP) 6. An address (Private Internet Protocol Address) is assigned.

These IP addresses include, for example, IPv4 which is a 32-bit numerical value or IPv6 which is a 128-bit numerical value. Also, as private IP addresses assigned to the plurality of terminals 4a, 4b, and 4c constituting the terminal 4, for example, “10.0.0.0” to “10.255.255.255” ( Class A), “172.16.0.0” to “172.23.255.255” (class B), or “192.168.0.0” to “192.168.255.255” ( Any of class C) is used.

The Internet service provider (ISP) 6 includes a broadband router (not shown), and transmits various measured values from the plurality of terminals 4a, 4b, and 4c constituting the terminal 4 on the above-described uplink in a predetermined cycle on the Internet. 5, a network address translation (NAT) function that translates private IP addresses assigned to the terminals 4 a, 4 b, and 4 c into global IP addresses when transmitting to the cloud server 2 via the network server 5 is provided. Alternatively, a broadband router (not shown) further has a network address port translation (NAPT) function for converting to a different port number for each private IP address.

(Cloud server)
FIG. 2 is a functional block diagram of the cloud server shown in FIG. 2, the cloud server 2 includes an input unit 201, a display unit 202, an input I / F 203, an output I / F 204, an identification information management unit 205, a relay unit 206, an access request reception unit 207, and a communication I / F 208. A terminal identification information storage unit 209, a user terminal device storage unit 210, an authentication unit 211, a connection port allocation unit 212, a connection time management unit 213, and an internal bus 214 that interconnects them. Here, the identification information management unit 205, the relay unit 206, the access request reception unit 207, the authentication unit 211, the connection port assignment unit 212, and the connection time management unit 213 include, for example, a ROM for storing various programs (not shown) and a calculation process This is realized by a memory such as a RAM that temporarily stores the data and a processor such as a CPU that reads and executes a program stored in the ROM.

The terminal identification information storage unit 209 stores a unique identifier made up of alphanumeric characters assigned to the plurality of terminals 4a, 4b, and 4c constituting the terminal 4, respectively.

In addition, the user terminal device storage unit 210 stores at least user information, connection authority, identification information, and the like of the user terminal device 3a and the user terminal device 3b that can be connected to the cloud server 2.

The identification information management unit 205 reads the identification information allocated to each of the terminals 4a to 4c with reference to the terminal identification information storage unit 209 and / or the user terminal device storage unit 210 as necessary via the internal bus 214. Moreover, the identification information of the user terminal device 3a and the user terminal device 3b is read. When the number of user terminal devices connectable to the cloud server 2 is increased, user information such as user terminal device identification information and a user name input via the input unit 201 and the input I / F 203 is displayed as an identification information management unit. 205 is updated and registered in the user terminal device storage unit 210 via the internal bus 214. Similarly, when a new terminal 4 is added, identification information of the terminal 4 input via the input unit 201 and the input I / F 203 is input to the identification information management unit 205 via the internal bus 214. Update registration is performed in the information storage unit 209.

The access request accepting unit 207 receives the information of the terminal 4 desired to be accessed, the desired connection time, and the IP address of the user terminal device 3a or the user terminal device 3b from the user terminal device 3a or the user terminal device 3b. Accepted via F208 and the internal bus 214. Further, the access request receiving unit 207 receives a tunneling connection release request from the user terminal device 3 a or the user terminal device 3 b via the communication I / F 208 and the internal bus 214.

The authentication unit 211 encrypts authentication information for enabling the terminal 4 to connect to the cloud server 2 (for example, SSH), and transmits it to the corresponding terminal 4 via the internal bus 214 and the communication I / F 208. Based on the authentication information from the terminal 4, whether tunneling is possible is determined.

For each access request, the connection port assignment unit 212 sets one of the two connection ports indicated by two numbers randomly selected from 10000 to 65535 as the first connection port and the other as the second connection port. Connection port. Then, the connection port assignment unit 212 assigns the first connection port to one of the terminals 4a to 4c constituting the terminal 4, and assigns the second connection port to the user terminal device 3a or the user terminal device 3b.

The relay unit 206 relays the maintenance / status grasping work request transmitted from the user terminal device 3a or the user terminal device 3b to the second connection port from the second connection port to the first connection port during tunneling. Then, the data is transmitted to one of the terminals 4a to 4c constituting the terminal 4. In addition, as a result of the maintenance / status grasping work request, various measured values transmitted from one of the terminals 4a to 4c constituting the terminal 4 to the first connection port are transmitted from the first connection port to the first connection port. 2 to the connection port, and various measurement values are transmitted to the user terminal device 3a or the user terminal device 3b. When the tunneling connection is established, the relay unit 206 changes the status of the tunneling connection from not connected to being connected.

The connection time management unit 213 has a tunneling connection time monitoring function. Specifically, the connection time management unit 213 starts a timer (not shown) at the start of tunneling, and forcibly terminates the tunneling connection when a predetermined time (for example, several minutes to several tens of minutes) has elapsed. Change the connection status from connected to not connected.

Note that the cloud server 2 may further include a storage unit (not shown), and may be configured to store history information indicating which terminal 4 is accessed (tunnel connection) from which user terminal device. In addition, the cloud server 2 periodically performs PING and TCP port monitoring with respect to the terminal 4, that is, transmits a PING packet to the terminal 4 or makes a TCP connection, and if the terminal 4 does not return a PING packet or the TCP connection is established. When it is not possible, it is good also as a structure provided with the function to notify to a user terminal device by mail etc. that the said terminal 4 is in an abnormal state.

(Terminal)
FIG. 3 is a functional block diagram of the terminal 4 shown in FIG. In FIG. 3, the functional block diagram of the terminal 4a is shown as an example, but the same applies to the other terminals 4b and 4c. As illustrated in FIG. 3, the terminal 4 a includes an access request monitoring unit 301, a tunneling request generation unit 302, an authentication information decryption unit 303, a measurement value acquisition unit 304, a communication I / F 305, a storage unit 306, and a tunneling connection disconnection request monitor. A unit 307, a tunneling connection disconnection execution unit 308, a login authentication unit 309, and an internal bus 310 that interconnects them. Here, the access request monitoring unit 301, the tunneling request generation unit 302, the authentication information decoding unit 303, the measurement value acquisition unit 304, the tunneling connection disconnection request monitoring unit 307, the tunneling connection disconnection execution unit 308, and the login authentication unit 309 are: For example, a ROM for storing various programs (not shown), a memory such as a RAM for temporarily storing operation process data, etc., and a processor such as a CPU for reading and executing a program stored in the ROM (that is, a remote monitoring program) It is realized by.

The access request monitoring unit 301 inquires of the cloud server 2 via the communication I / F 305 and the Internet service provider (ISP) 6 whether or not there is an access request from the user terminal device 3a or the user terminal device 3b at a predetermined cycle. A reply from the server 2 is received and the access request is monitored.

When the tunneling is necessary as a result of monitoring by the access request monitoring unit 301, the authentication information decrypting unit 303 receives and receives encrypted authentication information received from the cloud server 2 via the communication I / F 305. Decrypt the encrypted authentication information. The authentication information decryption unit 303 transmits the decrypted authentication information to the cloud server 2 via the communication I / F 305 and the Internet service provider (ISP) 6 by, for example, SSH.

The tunneling request generation unit 302 generates a tunneling request when tunneling is necessary as a result of monitoring by the access request monitoring unit 301. The tunneling request generation unit 302 transmits the generated tunneling request to the cloud server 2 via the communication I / F 305 and the Internet service provider (ISP) 6 by, for example, SSH.

The login authentication unit 309 transmits a request for the ID and password of the user terminal device that is tunnel-connected to the cloud server 2, and executes login authentication of the corresponding user terminal device based on the ID and password received from the cloud server 2. .

The measurement value acquisition unit 304 acquires various measurement values of the target terminal or target device measured by the measurement device 8 via the communication I / F 305 and stores them in a predetermined storage area of the storage unit 306 via the internal bus 310. Write. The measurement value acquisition unit 304 transmits the above various measurement values on the uplink to the cloud server 2 via the communication I / F 305, the Internet service provider (ISP) 6, and the Internet 5 at a predetermined cycle by IoT. . Further, the measurement value acquisition unit 304 receives a maintenance / status grasping work request from a user terminal device, which will be described in detail later, via the communication I / F 305 and stores the request in the storage unit 306 corresponding to the work request. The various measurement values are read out and transmitted to the cloud server 2. The measurement value acquisition unit 304 may read the various measurement values at a different timing and transmit them to the cloud server 2. Note that the measurement value acquisition unit 304 may perform a process such as noise removal on the acquired various measurement values.

The storage unit 306 stores various measurement values of the target terminal or target device measured by the measurement device 8 in association with the date and time.

The tunneling connection disconnection request monitoring unit 307 inquires the cloud server 2 about the presence of a tunneling connection disconnection request via the communication I / F 305, the Internet service provider (ISP) 6 and the Internet 5 at a predetermined cycle, and makes a tunneling connection. If there is a disconnection request, the fact is transferred to the tunneling connection disconnection execution unit 308 via the internal bus 310.

When the tunneling connection disconnection execution unit 308 receives information indicating that a tunneling connection disconnection request has been received from the tunneling connection disconnection request monitoring unit 307 via the internal bus 310, the tunneling connection disconnection information is immediately disconnected and information indicating that the tunneling connection disconnection execution unit 308 has been disconnected. Alternatively, the signal is transmitted to the cloud server 2 via the communication I / F 305, the Internet service provider (ISP) 6, and the Internet 5. The tunneling connection disconnection execution unit 308 includes a timer (not shown), starts the timer to disconnect the tunneling connection when the connection time acquired from the cloud server 2 via the communication I / F 305 elapses, and activates the timer (connection time When the time elapses, the tunneling connection is disconnected, and information or a signal indicating the disconnection is transmitted to the cloud server 2 via the communication I / F 305, the Internet service provider (ISP) 6, and the Internet 5.

(User terminal device)
FIG. 4 is a functional block diagram of the user terminal device shown in FIG. In FIG. 4, the functional block diagram of the user terminal device 3a is shown as an example, but the same applies to the other user terminal devices 3b. As shown in FIG. 4, the user terminal device 3a includes an input unit 401, a display unit 402, an input I / F 403, an output I / F 404, a calculation unit 405, a communication I / F 406, a storage unit 407, and these components connected to each other. An internal bus 409 is provided. The user terminal device 3a includes a battery unit 408 that includes a power source and a battery. Here, the calculation unit 405 includes, for example, a ROM for storing various programs (not shown), a memory such as a RAM for temporarily storing calculation process data, and a CPU for reading and executing the programs stored in the ROM. Realized by a processor.

The input unit 401 includes, for example, a keyboard and a mouse. The input unit 401 includes an access request to a desired terminal 4, an ID and a password that are input at the time of login for tunneling connection, and a request for maintenance / status grasping described later. Are input to the input I / F 403.

The input I / F 403 transmits input information such as the access request, ID and password, and maintenance / status grasping work request to the cloud server 2 via the internal bus 409, the communication I / F 406, and the router 3c. . The output I / F 404 receives various measured values from one of the terminals 4a to 4c constituting the terminal 4 connected by tunneling in response to the maintenance / status grasping request, and the communication I / F 406. And the measurement values are output to the display unit 402 and displayed on the display screen.

The storage unit 407 includes at least its own IP address, parameters used for various calculations by the calculation unit 405, and a target terminal or target terminal of a target device that is acquired in response to the maintenance / status grasping work request. Stores various measurement values of the target device. The calculation unit 405 has a function of reading a desired application program from a ROM (not shown) and executing it, and outputting the calculation result to the display unit 402 via the internal bus 409 and the output I / F 404.

Next, the overall operation of the remote monitoring system 1 will be described. In the following description, it is assumed that the user terminal device 3a and the terminal 4b are connected by tunneling as an example. 6 to 7 are schematic sequence diagrams of the remote monitoring system, FIG. 8 is a schematic sequence diagram of the remote monitoring system when a user (user) instructs disconnection, and FIG. 9 is a disconnection by the timer function. It is a schematic sequence diagram of the remote monitoring system.

First, as shown in FIG. 5, the access request monitoring unit 301 (FIG. 3) constituting the terminal 4b informs the cloud server 2 whether or not there is an access request to the desired terminal 4 at a predetermined cycle (whether tunneling is necessary). Inquiries are made via the communication I / F 305, the Internet service provider (ISP) 6, and the Internet 5 (S101). When the access request reception unit 207 constituting the cloud server 2 does not receive an access request from the user terminal device 3a, the access request reception unit 207 notifies the terminal 4b via the Internet 5 and the Internet service provider (ISP) 6 that there is no need for tunneling. Transmit (S102). As shown in FIG. 5, these processes are executed at a predetermined cycle, as also shown in S103 and S104.

The user terminal device 3a sends an access request to the terminal 4b to the cloud server 2 via the communication I / F 406 and the router 3c, including, for example, a predetermined connection time and the IP address of the user terminal device 3a itself that is the connection source. (S105).

When the access request accepting unit 207 constituting the cloud server 2 accepts an access request to the terminal 4b from the user terminal device 3a, the identification information management unit 205 accesses the user terminal device storage unit 210 and makes an access request. The connection source is specified as the user terminal device 3a by the included IP address. Also, the identification information management unit 205 accesses the terminal identification information storage unit 209 and acquires the identification information of the terminal 4b that is the connection destination. Subsequently, the connection port assignment unit 212 acquires two connection ports at random. If the acquired two connection ports (No. X, No. Y) are not in use, the connection port assignment unit 212 reserves the first connection port (No. X) of the cloud server 2 to be assigned to the terminal 4b, and the user The second connection port (No. Y) of the cloud server 2 assigned to the terminal device 3a is reserved. In addition to this, the connection port allocation unit 212 arbitrarily selects one server (server address “Z”) from a plurality of servers constituting the cloud server 2 to which the user terminal device 3a is connected (S106).

Next, the access request reception unit 207 configuring the cloud server 2 receives presence / absence of access request (whether tunneling is necessary) from the access request monitoring unit 301 configuring the terminal 4b (S107), and configures the cloud server 2 The connection port allocating unit 212 indicates that tunneling is necessary, the server address “Z” to be connected (hereinafter referred to as server Z), the first connection port (No. X), the predetermined connection time, and the encrypted Along with the authentication information, it is transmitted to the terminal 4b via the Internet 5 and the Internet service provider (ISP) 6 (S108).

The authentication information decryption unit 303 constituting the terminal 4b decrypts the encrypted authentication information received from the cloud server 2. Further, the tunneling request generation unit 302 that configures the terminal 4b generates a tunneling request, and sends the generated tunneling request to the cloud server 2 via the communication I / F 305 and the Internet service provider (ISP) 6, for example, by SSH. The information is transmitted to the server Z to be configured (S109).

Next, as shown in FIG. 6, the server Z transmits an authentication information transmission request to the terminal 4b via the Internet 5 and the Internet service provider (ISP) 6 (S110). The authentication information decryption unit 303 constituting the terminal 4b transmits the decrypted authentication information to the server Z via the communication I / F 305 and the Internet service provider (ISP) 6, for example, by SSH (S111).

The authentication unit 211 constituting the server Z determines whether tunneling is possible based on the received authentication information, and transmits a connection permission notification to the terminal 4b via the Internet 5 and the Internet service provider (ISP) 6 (S112). When receiving the connection permission notification from the server Z via the communication I / F 305 and the internal bus 310, the tunneling request generation unit 302 constituting the terminal 4b communicates with the server Z to the first connection port (No. X). Transmits a request to transmit to itself via the Internet service provider (ISP) 6 and the Internet 5 (S113).

Next, the access request receiving unit 207 constituting the server Z transmits a signal (Ack) indicating that the server Z has been acknowledged to the terminal 4b via the Internet 5 and the Internet service provider (ISP) 6 (S114). The tunneling connection disconnection execution unit 308 constituting the terminal 4b starts a timer (not shown) to disconnect after a predetermined connection time received by the connection port assignment unit 212 previously constituting the server Z (S115). Further, the relay unit 206 constituting the server Z activates a service that relays access to the second connection port (No. Y) from the user terminal device 3a to the first connection port (No. X). Further, the connection time management unit 213 constituting the server Z starts a timer (not shown) so as to be disconnected after a predetermined connection time (S116). The relay unit 206 changes the status of the tunneling connection from not connected to being connected.

The connection port assignment unit 212 constituting the server Z transmits to the user terminal device 3a that the server to be connected is the server Z and the connection port is the second connection port (Y number) (S117). The user terminal device 3a transmits a connection request to the second connection port (No. Y) to the server Z (S118). The relay unit 206 constituting the server Z relays from the second connection port (No. Y) to the first connection port (No. X), and flows access to the first connection port (No. X) to the terminal 4b. (S119). The relay unit 206 constituting the server Z transmits a connection request to the terminal 4b via the communication I / F 208, the Internet 5, and the Internet service provider (ISP) 6 (S200).

The login authentication unit 309 constituting the terminal 4b transmits a request for the ID and password of the user terminal device 3a to the server Z via the communication I / F 305, the Internet service provider (ISP) 6, and the Internet 5 (S201). .

Next, as shown in FIG. 7, the relay unit 206 constituting the server Z relays from the first connection port (No. X) to the second connection port (Y No.) (S202). Then, the relay unit 206 transmits an ID / password transmission request to the user terminal device 3a (S203). When the communication I / F 406 constituting the user terminal device 3a receives the ID / password transmission request, the input unit 401 constituting the user terminal device 3a inputs the ID and password necessary for login during tunneling connection. The data is transmitted to the server Z via the input I / F 403, the internal bus 409, and the communication I / F 406 (S204).

The relay unit 206 constituting the server Z relays from the second connection port (No. Y) to the first connection port (No. X), and flows access to the first connection port (No. X) to the terminal 4b. (S205). The relay unit 206 constituting the server Z transmits the ID and password of the user terminal device 3a to the terminal 4b via the communication I / F 208, the Internet 5 and the Internet service provider (ISP) 6 (S206). The login authentication unit 309 constituting the terminal 4b executes login authentication based on the ID and password of the user terminal device 3a transmitted from the server Z, and indicates that it is OK (permission notification) to the Internet service provider (ISP) 6 And it transmits to the server Z via the Internet 5 (S207).

The relay unit 206 constituting the server Z relays from the first connection port (No. X) to the second connection port (No. Y) (S208). And the relay part 206 transmits that the result of login authentication is OK (permission notification) to the user terminal device 3a (S209).

When the communication I / F 406 configuring the user terminal device 3a receives that the login authentication result is OK (permission notification), the input unit 401 configuring the user terminal device 3a requests a maintenance / status grasping operation request. Is transmitted to the server Z via the input I / F 403, the internal bus 409, and the communication I / F 406 (S210).

The relay unit 206 constituting the server Z relays from the second connection port (No. Y) to the first connection port (No. X), and flows access to the first connection port (No. X) to the terminal 4b. (S211). The relay unit 206 constituting the server Z transmits a request for maintenance / status grasping work to the terminal 4b via the communication I / F 208, the Internet 5, and the Internet service provider (ISP) 6 (S212).

When the measurement value acquisition unit 304 constituting the terminal 4 b receives a maintenance / status grasping operation request via the communication I / F 305, the measurement value acquisition unit 304 accesses the storage unit 306 via the internal bus 310 and stores the request in the storage unit 306. The process execution results corresponding to the above various measurement values and work requests are read out and transmitted to the server Z via the Internet service provider (ISP) 6 and the Internet 5 as the maintenance / status grasping work request results (S213).

The relay unit 206 constituting the server Z relays from the first connection port (No. X) to the second connection port (No. Y) (S214). And the relay part 206 transmits the process execution result according to the various measurement values and work request of an object terminal or an object apparatus to the user terminal device 3a as a request result of the maintenance / status grasping work (S215).

Next, an outline sequence of the remote monitoring system 1 when the user (user) instructs to disconnect will be described. As shown in FIG. 8, the tunneling connection disconnection request monitoring unit 307 constituting the terminal 4 b transmits to the server Z via the communication I / F 305, the Internet service provider (ISP) 6, and the Internet 5 at a predetermined cycle. An inquiry is made as to whether there is a tunneling connection disconnection request (S301). The access request receiving unit 207 constituting the server Z indicates that there is no need for disconnection when the tunneling connection disconnection request is not received from the user terminal device 3a, and that the terminal 4b is connected via the Internet 5 and the Internet service provider (ISP) 6. (S302).

When the operation is completed, the user terminal device 3a inputs a tunneling connection release request (tunneling connection disconnection request) through the input unit 401 and transmits it to the server Z via the input I / F 403, the internal bus 409, and the communication I / F 406. (S303). When receiving the tunneling connection release request (tunneling connection disconnection request), the access request receiving unit 207 configuring the server Z transmits an acknowledgment (Ack) to the user terminal device 3a (S304). Then, the access request reception unit 207 changes the status of the tunneling connection from being connected to a disconnection request (S305).

The tunneling connection disconnection request monitoring unit 307 configuring the terminal 4b inquires of the server Z about the presence of a tunneling connection disconnection request via the communication I / F 305, the Internet service provider (ISP) 6, and the Internet 5 (S306). At this time, since the status of the tunneling connection is changed from being connected to a disconnection request, the access request accepting unit 207 constituting the server Z sends the request to the terminal 4b via the Internet 5 and the Internet service provider (ISP) 6. A tunneling connection disconnection request is transmitted (S307).

Upon receiving the tunneling connection disconnection request from the tunneling connection disconnection request monitoring unit 307 via the internal bus 310, the tunneling connection disconnection execution unit 308 constituting the terminal 4b immediately disconnects the tunneling connection (ends connection) and is not illustrated. The timer is stopped (S308). Then, the tunneling connection disconnection execution unit 308 transmits information indicating that the timer has been stopped to the server Z via the Internet service provider (ISP) 6 and the Internet 5 (S309).

The relay unit 206 constituting the server Z terminates the relay service, the connection time management unit 213 stops the timer, and changes the status of the tunneling connection from the disconnection request to the unconnected (S310). Then, the connection time management unit 213 transmits an acknowledgment (Ack) to the terminal 4b via the Internet 5 and the Internet service provider (ISP) 6 (S311). Thereafter, the connection port allocation unit 212 constituting the server Z cancels the reserved first connection port (No. X) and second connection port (No. Y) (S312).

Next, an outline sequence of the remote monitoring system 1 at the time of disconnection by the timer function will be described. As shown in FIG. 9, the tunneling connection disconnection execution unit 308 constituting the terminal 4b activates a timer when a predetermined time, which is a connection time of the tunneling connection, has elapsed, and ends the tunneling connection (S401). . Similarly, the connection time management unit 213 configuring the server Z activates a timer when a predetermined time, which is a connection time for tunneling connection, has elapsed, and the relay unit 206 ends the relay service (S402). As a result, the user terminal device 3a is forced to terminate the tunneling connection and cannot access the server Z (S403).

The tunneling connection disconnection execution unit 308 constituting the terminal 4b transmits a notification that the timer has been stopped to the server Z via the Internet service provider (ISP) 6 and the Internet 5 (S404). The connection time management unit 213 configuring the server Z changes the status of the tunneling connection from being connected to not being connected (S405). Then, the connection time management unit 213 transmits an acknowledgment (Ack) to the terminal 4b via the Internet 5 and the Internet service provider (ISP) 6 (S406). After that, the connection port allocation unit 212 constituting the server Z cancels the reserved first connection port (No. X) and second connection port (No. Y) (S407). As described above, when the set time (predetermined connection time) elapses, the tunneling connection is automatically disconnected by the trigger of the timer, so even if the forgetting to transmit the tunneling connection disconnection request occurs after the work is completed. It becomes possible to prevent forgetting to close the connection port.

(Processing flow of cloud server)
FIG. 10 is a flowchart showing a processing flow of the cloud server 2 shown in FIG. As shown in FIG. 10, in step S2001, the access request receiving unit 207 determines whether there is an inquiry from the terminal 4b. That is, it is determined whether or not there is an inquiry about whether or not there is an access request (whether tunneling is necessary) from the terminal 4b. If there is no inquiry, step S2001 is repeated to enter a standby state. On the other hand, if there is an inquiry about whether there is an access request from the terminal 4b (whether tunneling is necessary), the process proceeds to step S2002.

In step S2002, the access request receiving unit 207 determines whether or not there is an access request from the user terminal device 3a. As a result of the determination, if there is no access request from the user terminal device 3a, the process proceeds to step S2003 to indicate that there is no need for tunneling (tunneling not required), and to the terminal 4b via the Internet 5 and the Internet service provider (ISP) 6. Then, the process returns to step S2002. On the other hand, if there is an access request from the user terminal device 3a, the process proceeds to step S2004.

In step S2004, the identification information management unit 205 specifies the terminal 4b with reference to the terminal identification information storage unit 209 and specifies the user terminal device 3a with reference to the user terminal device storage unit 210. That is, the identification information management unit 205 accesses the user terminal device storage unit 210, and specifies that the connection source is the user terminal device 3a based on the identification information included in the access request. Also, the identification information management unit 205 accesses the terminal identification information storage unit 209 and acquires the identification information of the terminal 4b that is the connection destination.

In step S2005, a first connection port to be assigned to the terminal 4b and a second connection port to be assigned to the user terminal device 3a are randomly obtained, and a server to be reserved and connected is selected. Specifically, the connection port assignment unit 212 acquires two connection ports at random. If the acquired two connection ports (No. X, No. Y) are not in use, the connection port assignment unit 212 reserves the first connection port (No. X) of the cloud server 2 to be assigned to the terminal 4b, and the user The second connection port (No. Y) of the cloud server 2 assigned to the terminal device 3a is reserved. In addition to this, the connection port assignment unit 212 arbitrarily selects one server (server address “Z”) from a plurality of servers constituting the cloud server 2 to which the user terminal device 3a is connected. Then, the connection port assignment unit 212 indicates that the tunneling is necessary, the server address “Z” (hereinafter referred to as server Z) to be connected, the first connection port (No. X), the predetermined connection time, the encryption The authentication information is transmitted to the terminal 4b via the Internet 5 and Internet service provider (ISP) 6.

In step S2006, an authentication process for the terminal 4b is executed. Specifically, the authentication unit 211 performs authentication processing by determining whether or not tunneling is possible based on authentication information received from the terminal 4b. In step S2007, relay service activation & timer activation from the second connection port to the first connection port is executed. Specifically, the relay unit 206 activates a service that relays access to the second connection port (No. Y) from the user terminal device 3a to the first connection port (No. X). In addition, the connection time management unit 213 starts a timer to disconnect after a predetermined connection time. In addition, the relay unit 206 changes the status of the tunneling connection from not connected to being connected.

In step S2008, relay is performed from the first connection port to the second connection port. Specifically, the relay unit 206 relays from the first connection port (No. X) to the second connection port (No. Y).

In step S2009, the presence / absence of a maintenance / situation grasping work request is determined from the user terminal device 3a. If there is no maintenance / situation grasping work request, a standby state is entered in step S2009. On the other hand, if there is a maintenance / status grasping work request, the process proceeds to step S2010. Specifically, the access request reception unit 207 determines whether or not there is a maintenance / status grasping work request from the user terminal device 3a. Become. On the other hand, when the access request receiving unit 207 receives a maintenance / status grasping work request from the user terminal device 3a via the communication I / F 208, the process proceeds to step S2010.

In step S2010, a maintenance / status grasping work request is transmitted to the terminal 4b. Specifically, the relay unit 206 relays from the second connection port (No. Y) to the first connection port (No. X), and flows access to the first connection port (No. X) to the terminal 4b. . Then, the relay unit 206 transmits a request for maintenance / status grasping work to the terminal 4b via the communication I / F 208, the Internet 5, and the Internet service provider (ISP) 6.

In step S2011, the result of the work request from the terminal 4b is relayed to the user terminal device 3a. Specifically, the relay unit 206 relays from the first connection port (No. X) to the second connection port (No. Y). Then, the relay unit 206 transmits, to the user terminal device 3a, processing results corresponding to various measurement values and work requests of the target terminal or target device as the maintenance / status grasping work request results received from the terminal 4b.

In step S2012, it is determined whether or not there is a tunneling connection release request from the user terminal device 3a. If there is a tunneling connection release request, the process proceeds to step S2014, and if there is no tunneling connection release request, the process proceeds to step S2013. Specifically, the access request receiving unit 207 determines whether there is a tunneling connection release request (tunneling connection disconnection request) from the user terminal device 3a, and there is a tunneling connection release request (tunneling connection disconnection request) from the user terminal device 3a. If YES in step S2014, the process advances to step S2014. If there is no tunneling connection release request (tunneling connection disconnection request) from the user terminal device 3a, the process advances to step S2013.

In step S2013, it is determined whether or not the timer activation / tunneling connection is completed. If the timer is not activated and the tunneling connection is not completed, the process returns to step S2012. On the other hand, when the timer is activated and the tunneling connection is terminated, the process proceeds to step S2015. Specifically, the connection time management unit 213 starts the timer, and the relay unit 206 continues the relay service without activating the timer before a predetermined time, which is the connection time of the tunneling connection, elapses. Return to S2012. On the other hand, the connection time management unit 213 activates the timer when a predetermined time, which is the connection time of the tunneling connection, has elapsed since the start of the timer, the relay unit 206 ends the relay service, and the process proceeds to step S2015.

In step S2014, the status of the tunneling connection is changed from being connected to a disconnection request. Specifically, the access request reception unit 207 changes the status of the tunneling connection from being connected to a disconnection request. Then, in response to an inquiry as to whether there is a tunneling connection disconnection request from the terminal 4b, a tunneling connection disconnection request is transmitted to the terminal 4b.

In step S2015, it waits for the timer transmitted from the terminal 4b to be stopped.

In step S2016, the status of the tunneling connection is changed from being connected or disconnected to not being connected. Specifically, the relay unit 206 ends the relay service, and the connection time management unit 213 stops the timer, and changes the status of the tunneling connection from being connected or disconnecting to being unconnected.

In step S2017, the first connection port and the second connection port being reserved are released, and the process ends. Specifically, the connection port allocation unit 212 releases the reserved first connection port (X number) and second connection port (Y number), and ends the process.

(Terminal processing flow)
FIG. 11 is a flowchart showing the processing flow of the terminal 4 shown in FIG. Hereinafter, the terminal 4b will be described as an example. As shown in FIG. 11, in step S4001, the access request monitoring unit 301 determines whether tunneling is necessary. That is, the access request monitoring unit 301 inquires of the cloud server 2 through the communication I / F 305, the Internet service provider (ISP) 6, and the Internet 5 about the presence / absence of an access request (whether tunneling is necessary) at a predetermined cycle. If there is no access request as a result of the inquiry, step S4001 is repeated to enter a standby state. On the other hand, if there is a tunneling request, the process proceeds to step S4002.

In step S4002, a server address to be connected, a first connection port number, a connection time, and encrypted authentication information are acquired. Specifically, a server address “Z” (hereinafter referred to as a server Z) to be connected received from the cloud server 2 via the Internet 5, Internet service provider (ISP) 6, and communication I / F 305, Of the first connection port (X number), the predetermined connection time, and the encrypted authentication information, the server address “Z” (hereinafter referred to as server Z) to be connected and the first connection port (X number) Is acquired by the tunneling request generation unit 302 via the internal bus 310. Further, the predetermined connection time is acquired by the tunneling connection disconnection execution unit 308 via the internal bus 310. The encrypted authentication information is acquired by the authentication information decryption unit 303 via the internal bus 310.

In step S4003, the acquired authentication information is decrypted. Specifically, the authentication information decryption unit 303 decrypts the encrypted authentication information received from the cloud server 2.

In step S4004, a tunneling request is transmitted to the server Z to be connected. Specifically, the tunneling request generation unit 302 generates a tunneling request and configures the cloud server 2 with the generated tunneling request via the communication I / F 305 and the Internet service provider (ISP) 6 using, for example, SSH. Send to server Z.

In step S4005, authentication information is transmitted to the server Z to be connected. Specifically, the authentication information decryption unit 303 transmits the decrypted authentication information to the server Z via the communication I / F 305 and the Internet service provider (ISP) 6 by, for example, SSH.

In step S4006, the server Z to be connected is requested to transmit the communication to the first connection port to itself. Specifically, the tunneling request generation unit 302 sends a request to the server Z to send communication to the first connection port (No. X) to itself via the Internet service provider (ISP) 6 and the Internet 5. Send.

In step S4007, a timer is started to disconnect the tunneling connection when the acquired connection time has elapsed. Specifically, the tunneling connection disconnection execution unit 308 starts a timer (not shown) so as to disconnect after a predetermined connection time previously received from the server Z.

In step S4008, the server Z is requested for the ID and password of the user terminal device 3a. Specifically, the login authentication unit 309 transmits a request for the ID and password of the user terminal device 3 a to the server Z via the communication I / F 305, the Internet service provider (ISP) 6, and the Internet 5.

In step S4009, login authentication processing is executed. Specifically, the login authentication unit 309 executes login authentication based on the ID and password of the user terminal device 3a transmitted from the server Z, and notifies the Internet service provider (ISP) 6 that it is OK (permission notification). And to the server Z via the Internet 5.

In step S4010, a maintenance / status grasping work request is received. Specifically, the measured value acquisition unit 304 receives a maintenance / status grasping request from the user terminal device 3a via the communication I / F 305.

In step S4011, the measurement value and maintenance information by the measurement device are read from the storage unit, and the result is transmitted to the server Z. Specifically, the measurement value acquisition unit 304 accesses the storage unit 306 via the internal bus 310, and displays processing results corresponding to various measurement values and work requests of the target terminal or target device stored in the storage unit 306. As a request result of the work of reading and maintenance / status grasping, it is transmitted to the server Z via the Internet service provider (ISP) 6 and the Internet 5.

In step S4012, it is determined whether or not there is a tunneling connection release request from the user terminal device 3a. If there is a tunneling connection release request, the process proceeds to step S4014. If there is no tunneling connection release request, the process proceeds to step S4013. Specifically, the tunneling connection disconnection request monitoring unit 307 inquires of the server Z about the presence or absence of the tunneling connection disconnection request via the communication I / F 305, the Internet service provider (ISP) 6, and the Internet 5. As a result of the inquiry, if there is a tunneling connection disconnection request (tunneling connection release request), the process proceeds to step S4014. If there is no tunneling connection disconnection request (tunneling connection release request), the process proceeds to step S4013.

In step S4013, it is determined whether or not the timer activation / tunneling connection is completed. If the timer is not activated and the tunneling connection is not completed, the process returns to step S4012. The terminal 4b continuously communicates with the user terminal device 3a to which the second connection port is assigned via the first connection port for a predetermined time. On the other hand, if the timer is activated and the tunneling connection is terminated, the process proceeds to step S4014. Specifically, the tunneling connection disconnection execution unit 308 continues the tunneling connection without activating the timer before elapse of a predetermined time, which is the connection time of the tunneling connection, after starting the timer, and returns to step S4012. On the other hand, the tunneling connection disconnection execution unit 308 activates the timer when a predetermined time, which is the connection time of the tunneling connection, has elapsed since the start of the timer, and proceeds to step S4014.

In step S4014, the tunneling connection disconnection execution unit 308 executes the tunneling connection disconnection and ends the process.

(Processing flow of user terminal device)
FIG. 12 is a flowchart showing a processing flow of the user terminal device shown in FIG. Hereinafter, the user terminal device 3a will be described as an example. As shown in FIG. 12, in step S3001, an access request to the terminal 4b is transmitted to the cloud server 2 (connection time and connection source information transmission). Specifically, the user terminal device 3a sends an access request to the terminal 4b to the communication I / F 406 and the router 3c including, for example, a predetermined connection time and the IP address of the user terminal device 3a that is the connection source. To the cloud server 2.

In step S3002, a server address to be connected and a second connection port number are acquired. Specifically, the cloud server 2 acquires that the server to be connected is the server Z and the connection port is the second connection port (Y number).

In step S3003, a connection request is transmitted to the server Z to be connected through the second connection port. Specifically, the user terminal device 3a transmits a connection request to the second connection port (No. Y) to the server Z.

In step S3004, an ID and password transmission request is received from the server to be connected. Specifically, the communication I / F 406 receives an ID and password transmission request from the server Z.

In step S3005, the ID and password are transmitted to the server Z to be connected. Specifically, the input unit 401 inputs an ID and a password that are required at the time of login at the time of tunneling connection, and transmits them to the server Z via the input I / F 403, the internal bus 409, and the communication I / F 406.

In step S3006, a login authentication result is received. Specifically, the communication I / F 406 receives from the server Z that the login authentication result is OK (permission notification).

In step S3007, a maintenance / status grasping work request is transmitted. Specifically, the input unit 401 inputs a request for maintenance / status grasping work, and transmits the request to the server Z via the input I / F 403, the internal bus 409, and the communication I / F 406.

In step S3008, the measurement value and maintenance information by the measuring device are received as a request result via the second connection port. Specifically, the communication I / F 406 receives processing results corresponding to various measurement values and work requests of the target terminal or target device from the server Z as a result of the maintenance / status grasping work request, and ends the process. To do.

In FIG. 12, although not shown, various measurement values of the target terminal or target device and the processing results corresponding to the work request are displayed via the output I / F 404 as a request result of the received maintenance / status grasping work request. Displayed on the display screen of the unit 402. As a result, the user (user) 3 who is the owner of the user terminal device 3a can easily examine the necessity of maintenance and the contents of the maintenance for the target terminal or the target device.

In this embodiment, various measurement values of the target terminal or target device by IoT are transmitted from the terminal 4 to the cloud server 2 via the Internet service provider (ISP) 6 and the Internet 5 at a predetermined cycle. Although described as an example, it is not limited to this. For example, instead of the terminal 4 constituted by the terminals 4a to 4c described above, a personal computer, a smartphone (mobile phone), a tablet or the like may be used.

According to the present embodiment, it is possible to provide a remote monitoring system in which a plurality of terminals connected to the Internet via an Internet service provider can be accessed from a user terminal device at a desired timing.

Further, according to the present embodiment, it is possible to grasp the necessity of maintenance for the target terminal or target device in a timely manner by tunneling connection between the user terminal device and one of the plurality of terminals. At the same time, it becomes possible to easily examine the contents of maintenance.

Also, at the time of tunneling connection, forgetting to close the first and second connection ports randomly assigned to one terminal and user terminal device can be prevented, and security can be improved.

In the above-described embodiment, the configuration in which the user terminal device 3 and the terminal 4 can communicate with each other via the cloud server 2 has been described. In this configuration, the user terminal device 3 and the lower connection port of the terminal 4 are connected. In order to enable communication with lower-level devices such as measurement devices and cameras, the following processing is required. In order to distinguish from the connection port of the cloud server 2, the connection port of the terminal 4 is expressed as “lower connection port”.

That is, after the processing of S101 to S208 in FIGS. 5 to 7 is executed among the user terminal device 3, the cloud server 2, and the terminal 4 to connect the user terminal device 3 and the terminal 4 so that they can communicate, the user terminal device 3. When a predetermined request is input from 3 to the terminal 4, the terminal 4 receiving the request connects (relays) the lower-level device connected to the lower-level connection port and the user terminal device 3 so that they can communicate with each other. . However, since such a request from the user terminal device is normally performed by command line input, it is a complicated operation for those who are not familiar with the operation.

Therefore, the following configuration may be adopted. On the display unit 402 of the user terminal device 3, for example, as shown in FIG. 13A, a terminal selection screen G1 including a button for selecting a terminal 4 (4a to 4c) to be connected and a terminal to be connected is displayed. indicate. Then, when a terminal to be connected is selected by a button operation on the terminal selection screen G1, as shown in FIG. 13B, a connection destination (terminal 4 itself or its lower connection port) that becomes a connection candidate in the selected terminal 4 And a connection destination selection screen G2 including a button for selecting a connection destination. And it connects automatically to the connection destination selected by button operation in the connection destination selection screen G2. When the terminal itself is selected on the connection destination selection screen G2, the same operation as that described in the above-described embodiment is performed. As an example, the display of the terminal selection screen G1 and the connection destination selection screen G2 on the display unit 402 of the user terminal device 3 is performed by accessing the cloud server 2 as a Web server by the browser software of the user terminal device 3. Is called.

Here, an example in which a measurement device connected to the lower connection port (No. A) of the terminal 4 is automatically connected as a connection destination will be described. The operation of automatically connecting is common to the processes of S101 to S208 shown in FIGS. 5 to 7 in many parts, and the difference from these processes will be mainly described.

First, it is assumed that the terminal 4b is selected on the terminal selection screen G1, and the measuring device is selected on the connection destination selection screen G2. Then, in S105 of FIG. 5, an access request to the terminal 4b is added to a predetermined connection time and the IP address of the user terminal device 3a itself, and information indicating the measurement device as a connection destination (for example, a lower connection port (number A) ) And a unique identification number assigned to the measuring device) and the like are transmitted to the cloud server 2.

Then, in S106, the cloud server 2 reserves the first connection port (No. X) and the second connection port (No. Y) and selects the server Z to be connected. After that, when the cloud server 2 accepts the presence / absence of a tunneling request from the terminal 4b in S107, the server Z to be connected, the first connection port (No. X), a predetermined number in S108 indicate that tunneling is necessary. The connection time, encrypted authentication information, and information indicating the measurement device are transmitted to the terminal 4b. The information transmitted to the terminal 4b and the access request correspond to a connection request to the measuring device connected to the terminal 4b.

Thereafter, the process proceeds from S109 to S206, and the terminal 4b executes login authentication based on the ID and password of the user terminal device 3a transmitted from the server Z. If the authentication is OK, the terminal 4b transfers the information from the server Z to the lower connection port (No. A) to which the measuring device is connected, and transmits the information from the lower connection port (No. A) to the server Z. After setting to forward to the first connection port (No. X), in S207, the fact that the authentication is OK (permission notice) is transmitted to the server Z.

As a result, the user terminal device 3a and the measuring device connected to the lower connection port (No. A) of the terminal 4b are communicably tunneled and the request of the user terminal device 3a is directly input to the measuring device.

That is, when the terminal 4b receives a connection request from the cloud server 2 to the measuring device connected to the terminal 4b, the terminal 4b uses the first connection port (No. X), the second connection port (No. Y), and the cloud server 2. Since the communication with the user terminal device 3a is connected (relayed) with the measurement device, the user terminal device 3a and the measurement device can directly communicate with each other.

In this way, when it is desired to directly communicate between the user terminal device 3a and the measurement device connected to the lower connection port of the terminal 4b, information indicating the lower device of the connection destination is included in the access request from the user terminal device 3a. In addition, by making a connection request to the lower-level device, it is possible to automatically connect the user terminal device 3a and the lower-level device without performing a complicated request input operation.

Note that the timing at which communication is transferred between the server Z and the lower connection port in the terminal 4b is not limited to immediately before S207, but may be, for example, the timing before or after S109. Unless determined, it may be determined appropriately according to the configuration. Further, in the above description, the connection destination is selected by operating the connection button displayed on the display unit 402. In addition to this, for example, a command character string including the selected connection destination is input. It is good also as a structure.

In addition, this invention is not limited to the above-mentioned Example, Various modifications are included. For example, the above-described embodiments have been described in detail for easy understanding of the present invention, and are not necessarily limited to those having all the configurations described.

1 ... Remote monitoring system 2 ... Cloud server 3 ... User (user)
3a ... User terminal device a
3b User terminal device b
3c ... Router 4 ... Terminal 4a ... Terminal a
4b ... Terminal b
4c ... terminal c
5 ... Internet 6 ... Internet Service Provider (ISP)
7 ... Tunneling 8 ... Measuring device 201 ... Input unit 202 ... Display unit 203 ... Input I / F
204 ... Output I / F
205 ... Identification information management unit 206 ... Relay unit 207 ... Access request reception unit 208 ... Communication I / F
209 ... Terminal identification information storage unit 210 ... User terminal device storage unit 211 ... Authentication unit 212 ... Connection port allocation unit 213 ... Connection time management unit 214 ... Internal bus 301 ... Access request monitoring unit 302 ... Tunneling request generation unit 303 ... Authentication information Decoding unit 304 ... Measurement value acquisition unit 305 ... Communication I / F
306 ... Storage unit 307 ... Tunneling connection disconnection request monitoring unit 308 ... Tunneling connection disconnection execution unit 309 ... Login authentication unit 310 ... Internal bus 401 ... Input unit 402 ... Display unit 403 ... Input I / F
404 ... Output I / F
405 ... Calculation unit 406 ... Communication I / F
407: Storage unit 408 ... Battery unit 409 ... Internal bus G1 ... Terminal selection screen G2 ... Connection destination selection screen

Claims (17)

1. A plurality of terminals assigned private IP addresses, connected to the Internet via an Internet service provider having a global IP address;
   A cloud server connected to the Internet;
   A user terminal device connected to the cloud server,
   The cloud server assigns a first connection port to one terminal of the plurality of terminals, and assigns a second connection port to the user terminal device,
   The remote monitoring system, wherein the one terminal communicates with the user terminal device via the first connection port, the second connection port, and the cloud server.
2. The remote monitoring system according to claim 1,
   The cloud server randomly assigns the first connection port and the second connection port to the one terminal and the user terminal device, respectively.
3. The remote monitoring system according to claim 1 or 2,
   The remote monitoring system, wherein the user terminal device transmits a connection request to one of the plurality of terminals to the cloud server.
4. The remote monitoring system according to claim 3, wherein
   The cloud server assigns a different first connection port to one terminal among the plurality of terminals and is different for each connection request to one terminal among the plurality of terminals transmitted from the user terminal device. A remote monitoring system comprising: a connection port assignment unit for assigning a second connection port to the user terminal device.
5. The remote monitoring system according to claim 4, wherein
   The cloud server is a connection that allows communication between the one terminal to which the first connection port is assigned and a user terminal device to which the second connection port is assigned to continue for a predetermined time. A remote monitoring system comprising a time management unit.
6. The remote monitoring system according to claim 5, wherein
   The remote monitoring system, wherein the user terminal device transmits at least its own IP address, any one of the plurality of terminals to be connected, and a connection time to the cloud server.
7. The remote monitoring system according to claim 6, wherein
   The connection time management unit disconnects communication between the one terminal and the user terminal device via the first connection port and the second connection port when a connection time transmitted from the user terminal device has elapsed. A remote monitoring system characterized by that.
8. The remote monitoring system according to claim 7,
   The plurality of terminals are connected to a measurement device and / or an imaging device respectively by wire or wirelessly, and the measurement value of the target terminal or target device measured by the measurement device and / or the target terminal imaged by the imaging device Alternatively, the remote monitoring system is characterized in that image data of a target device is transmitted to the cloud server via the Internet service provider and the Internet at a predetermined cycle.
9. The remote monitoring system according to claim 1 or 2,
   The user terminal device transmits a connection request to a lower device connected to one terminal among the plurality of terminals to the cloud server,
   When the one terminal receives the connection request from the cloud server, the one terminal connects communication with the user terminal device to the lower-level device.
10. The user terminal device displays a terminal selection screen for selecting one terminal among the plurality of terminals and a connection destination selection screen for selecting a connection destination in one terminal selected on the terminal selection screen. 10. When a lower-level device connected to the one terminal is selected as a connection destination on the connection destination selection screen, a connection request to the lower-level device is transmitted to the cloud server. The remote monitoring system described in 1.
11. In a plurality of terminals assigned with private IP addresses connected to the Internet via an Internet service provider having a global IP address,
    The terminal can be connected to a cloud server via the Internet, can communicate with a user terminal device via the cloud server,
    A first connection port different from a second connection port assigned to the user terminal device by the cloud server is assigned, and communication with the user terminal device is possible via the first connection port and the second connection port. A terminal for a remote monitoring system characterized by this.
12. The remote monitoring system terminal according to claim 11,
    A remote connection terminal for a remote monitoring system, wherein a first connection port different from a second connection port assigned to the user terminal device by the cloud server is randomly assigned.
13. The terminal for a remote monitoring system according to claim 12,
    A terminal for a remote monitoring system, which communicates continuously with the user terminal device to which the second connection port is assigned for a predetermined time via the first connection port.
14. The terminal for a remote monitoring system according to claim 13,
    A remote control system comprising: a tunneling connection disconnection execution unit that disconnects a tunneling connection that communicates with the user terminal device to which the second connection port is assigned via the first connection port when a predetermined time elapses. Terminal for monitoring system.
15. The remote monitoring system terminal according to claim 11 or 12,
    The terminal is connected to a lower level device, and when receiving a connection request from the cloud server to the lower level device, the user terminal device and the lower level device can communicate with each other. Terminal.
16. Assigning a first connection port to one of a plurality of terminals assigned with a private IP address connected to the Internet via an Internet service provider having a global IP address;
    Assigning a second connection port to a user terminal connected to the cloud server connected to the Internet;
    A remote monitoring program causing a processor to execute a function of randomly assigning the first connection port and the second connection port.
17. The remote monitoring program according to claim 16, wherein
    Remote monitoring characterized by causing a processor to execute a function of continuing communication between the one terminal to which the first connection port is assigned and the user terminal device to which the second connection port is assigned for a predetermined time. Program.

Images