KR20230114082A - IoT ENGINE ALGORITHM AND SOFTWARE FOR SMART GATEWAY INTERWORKING WITH LOCAL SERVER - Google Patents

Abstract

The present invention relates to an IoT engine algorithm and software that interworks with a local server of a smart gateway, comprising: a smart gateway that connects and interfaces wired and wirelessly with IoT devices such as sensors and actuators; an authentication server (Auth server) that receives and stores the address and identification information of the smart gateway's public IP from the smart gateway to the Internet; and a user application device that primarily connects, in order to find and connect to the public IP address of the smart gateway including the local server, to a predetermined authentication server, acquires the public IP of the smart gateway, secondly connects to the local server of the smart gate using the acquired public IP address to receive the hybrid app program, and receives related information from the IoT device and displays the same on a screen. In particular, the user notification service effectively enables interactive communication by featuring the push method of web socket and MQTT in the IoT engine.

Description

IoT engine algorithm and software for smart gateway with local server interworking method {IoT ENGINE ALGORITHM AND SOFTWARE FOR SMART GATEWAY INTERWORKING WITH LOCAL SERVER}

The present invention relates to the field of Internet of Things (IoT). More specifically, the present invention relates to an IoT engine algorithm and software including a communication method for an interface of an IoT device, a user application device, and a smart gateway.

IoT (Internet of Things) is one of the core technologies of the 4th Industrial Revolution, a new computing paradigm that is expected to improve the quality of our lives based on intelligent smart devices.

IoT technology can be applied to numerous industrial fields, including smart homes, smart farms, smart cities, smart factories, smart plugs, smart power, and smart displays.

In order to build an IoT system, a gateway must exist to connect external user application devices and internal IoT devices over the Internet. There were downsides in terms of time and cost.

Recently, 32-bit high-end, low-cost embedded platforms such as Raspberry Pi and Orange Pi have been released as one of the IoT platforms, and IoT engine algorithms and software have been developed for such embedded IoT platforms so that various IoT systems can be implemented faster, easier, and cheaper. is expected to be

The IoT engine algorithm and software for a local server-linked smart gateway according to an embodiment of the present invention operate a general gateway that connects user applications and IoT devices, eliminating costly external servers. Instead of using it, the technical task is to process data in a distributed manner by directly mounting a local server on the gateway used by each user.

In addition, the IoT engine algorithm and software for the smart gateway of the local server interlocking method according to an embodiment of the present invention operates a local server inside the smart gateway and uses existing data to find the public IP of the local server. It is a technical task to solve the inconvenience of the DDNS (Dynamic DNS) method.

In addition, the IoT engine algorithm and software for the smart gateway of the local server interworking method according to an embodiment of the present invention avoids the TCP Socket method, which is an existing unstable network communication technology, and implements a new communication method as a technical task. do.

In addition, the IoT engine algorithm and software for the smart gateway of the local server interlocking method according to an embodiment of the present invention takes a long time to develop and provides a more efficient IoT engine out of the existing firmware method having technical limitations. make it a technical challenge.

In addition, the IoT engine algorithm and software for the smart gateway of the local server interlocking method according to an embodiment of the present invention monitors the normal operating state of the smart gateway that connects and manages the information of the IoT device to the user application device when a failure occurs. It is a technical challenge to inform in real time.

In addition, an IoT engine algorithm and software for a smart gateway of a local server interworking method according to an embodiment of the present invention makes it a technical task to mediate information of an IoT device with a user application device in a wired/wireless communication method.

An IoT system according to an embodiment of the present invention includes a smart gateway connecting a user application and IoT devices; And an authentication server that stores and provides public IP address information to find the public IP of the local server operated inside the smart gateway. And when the IoT program starts, it first connects to the authentication server and executes the login program, and when the user's authentication status is confirmed in the login step, address information such as the public IP of the smart gateway is transmitted from the authentication server and secondarily It can include user application devices that connect to the local server of the smart gateway.

When the smart gateway is operated, the IoT engine identifies information such as the public IP, local IP, and Mac address of the smart gateway, and transmits the user ID and the identified information to the authentication server, and the authentication server stores the transmitted data in the database. can be saved

In order to monitor the normal operating state of the smart gateway in the user application device, the IoT engine of the smart gateway periodically transmits keep alive information to the authentication server at regular intervals. It is determined that it has been detected, and an abnormal state may be displayed on the screen in the user application device such as the corresponding smartphone.

When an event occurs in the IoT device, the hybrid app program of the user application device transmits the event to the user application device in a push method through the web socket processing software of the IoT engine of the smart gateway, and the event is displayed on the screen of the user application device. displayed as a pop-up alarm,

In the native app program, when data is transmitted in a push method from the IoT engine of the smart gateway to the user application device through the MQTT Publisher, the user application device displays event information as a pop-up notification on the screen and generates a notification sound as needed. can

The IoT device is wired and wirelessly connected to the smart gateway to exchange IoT information. A fire alarm sensor, door open/close sensor, temperature/humidity sensor, etc. transmits data to the smart gateway through ZigBee, Bluetooth, Wi-Fi, and wireless communication in the 400 MHz band. and is connected to a smart box including an IoT sensor and an actuator via a wired USB method to transmit or control IoT data.

In addition, the smart gateway interfaces with a RESTful API method, so it can be easily linked with other systems.

The IoT system according to an embodiment of the present invention,

A smart gateway connected to IoT devices to obtain IoT device-related data; an authentication server receiving identification information and an IP address of the smart gateway from the smart gateway; And a user application that first accesses the authentication server to receive the IP address of the smart gateway, and secondarily accesses the smart gateway according to the received IP address to receive the IoT device-related data and display it on the screen. device may be included.

The authentication server may receive identification information of the user application device from the user application device, and transmit an IP address of a smart gateway having identification information mapped to the identification information of the user application device to the user application device.

The authentication server stores an identification information list of pre-registered smart gateways, compares the identification information list with identification information received from at least one smart gateway, and has an abnormality in the state of a smart gateway not transmitting identification information. can be judged to have occurred.

The IP address of the smart gateway includes a dynamic IP address, and the smart gateway may periodically transmit the identification information and the IP address to the authentication server.

The user application device may primarily access the authentication server according to the pre-stored IP address of the authentication server.

The data related to the IoT device may include at least one of CCTV image data, fire alarm data, door opening/closing notification data, call reception notification data, and trespass notification data.

A smart gateway according to another embodiment of the present invention,

A first web server connected to the upper terminal through the HTTP protocol; a web socket for driving an interface bidirectionally connecting the upper terminal and the first web server; an MQTT module connected to the upper terminal through an MQTT protocol; and a central control module transmitting a push message to the upper terminal through the web socket and the MQTT module, respectively, based on event data received from the lower terminal.

A push message transmitted to the upper terminal through the web socket is received through a web application of the upper terminal and displayed on the screen, and a push message transmitted to the upper terminal through the MQTT module is a native of the upper terminal. It can be received through the application and displayed on the screen.

The web server may receive control request data for the lower terminal from the upper terminal, and the central control module may transmit control command data to the lower terminal through the MQTT module.

The central control module may generate control command data based on event data received from a lower terminal and transmit the generated control command data to another lower terminal through the MQTT module.

The upper terminal is plural, and the first web server receives event data for another upper terminal from one upper terminal, and the central control module controls the event data received from the upper terminal based on the event data received from the upper terminal. , A push message may be transmitted to the other upper terminal through the web socket and the MQTT module, respectively.

The smart gateway may further include a second web server connected to the lower terminal through an HTTP protocol, and the second web server may receive the event data from the lower terminal.

The smart gateway may further include a short-range communication module for short-range communication with the lower-level device, and the short-range communication module may receive the event data from the lower-level device through a short-range communication method.

IoT engine algorithm and software for smart gateway of local server interworking method according to an embodiment of the present invention proposes IoT engine algorithm and software including communication method for interface of IoT device, user application device and smart gateway, It can be applied as a base technology to numerous IoT industrial fields such as farms, smart cities, smart factories, smart plugs, smart power and smart displays to effectively provide IoT products and services required by the market.

In addition, the IoT engine algorithm and software for the smart gateway of the local server interworking method according to an embodiment of the present invention improves the existing DDNS method and uses the authentication server method to find the public IP address of the new smart gateway. By developing, it is possible to build an effective IoT platform because it is easier to connect to a local server than before.

In addition, the IoT engine algorithm and software for the local server-linked smart gateway according to an embodiment of the present invention periodically transmits Keep Alive information to the authentication server from the smart gateway to enable monitoring by the user application device, thereby providing high reliability. IoT system can be provided.

In addition, the IoT engine algorithm and software for the smart gateway of the local server interlocking method according to an embodiment of the present invention deviate from the existing TCP Socket method of self-communication method and transmit the push event of the web socket and MQTT method to provide an effective notification service. is possible

However, the effects that can be achieved by the IoT engine algorithm and software for the smart gateway of the local server interworking method according to an embodiment of the present invention are not limited to those mentioned above, and other effects not mentioned are as follows From the description, it will be clear to those skilled in the art to which the present invention belongs.

In order to more fully understand the drawings cited herein, a brief description of each drawing is provided.
1 is a diagram for explaining an IoT system according to an embodiment of the present invention.
2 is a diagram for explaining the operation of a smart gateway, an authentication server, and a user application device.
3 is an exemplary diagram illustrating data stored in an authentication server.
4 is an exemplary diagram illustrating a smart gateway, an upper terminal, and a lower terminal according to an embodiment of the present invention.
5 is a diagram for explaining the configuration of a smart gateway according to an embodiment of the present invention.
6 is a diagram for explaining a process of transmitting a push message to an upper terminal according to event data of a lower terminal.
7 is a diagram for explaining a process of transmitting a push message to another upper terminal according to event data of one upper terminal.
8 is a diagram for explaining a process of transmitting control command data to a lower terminal according to control request data from an upper terminal.
9 is a diagram for explaining a process of transmitting control command data to another lower level terminal according to event data of one lower level terminal.
10 to 12 are exemplary diagrams illustrating software blocks of a smart gateway according to an embodiment of the present invention.

Since the present invention can make various changes and have various embodiments, specific embodiments are illustrated in the drawings and will be described in detail through detailed description. However, this is not intended to limit the present invention to specific embodiments, and it should be understood that the present invention includes all modifications, equivalents, and substitutes included in the spirit and scope of the present invention.

In describing the present invention, if it is determined that a detailed description of related known technologies may unnecessarily obscure the subject matter of the present invention, the detailed description will be omitted. In addition, numbers (eg, 1st, 2nd, etc.) used in the description process of this specification are only identifiers for distinguishing one component from another component.

In addition, in this specification, when one component is referred to as “connected” or “connected” to another component, the one component may be directly connected or directly connected to the other component, but in particular Unless otherwise described, it should be understood that they may be connected or connected via another component in the middle.

In addition, in the present specification, components expressed as '~ unit (unit)', 'module', etc. are two or more components combined into one component, or one component is divided into two or more components for each more subdivided function. may be differentiated into In addition, each of the components to be described below may additionally perform some or all of the functions of other components in addition to its own main function, and some of the main functions of each component may be different from other components. Of course, it may be performed exclusively by a component.

Hereinafter, embodiments according to the technical idea of the present invention will be described in detail in turn.

1 is a diagram for explaining an IoT system according to an embodiment of the present invention.

Referring to FIG. 1 , a smart gateway 100 is connected to several IoT devices 10 through an internal network. The smart gateway 100 may operate as a local server in a smart home. The smart gateway 100 may control the operation of IoT devices 10, for example, actuators.

The internal network is a LAN (local area network), and the smart gateway 100 and several IoT devices 10 are Zigbee communication, Bluetooth communication, RF443MHz communication, RF447MHz communication, Wifi communication, RFID (radio frequency identification) communication. , Ethernet communication, USB communication, serial communication, etc. can be used to communicate with each other. The communication method between the smart gateway 100 and the IoT devices 10 is not limited to the above-exemplified method, and various communication methods may be used within a range obvious to those skilled in the art.

The IoT devices 10 may include, for example, sensors and actuators, and the IoT devices 10 may be connected to the smart gateway 100 through wired or wireless communication.

The IoT devices 10 may include, for example, a CCTV 10a, a smoke detection sensor 10b, a motion detection sensor 10c, a door opening/closing detection sensor 10d, and an Internet phone 10e, but are limited thereto. It is not. Each of the IoT devices 10 transmits data related to itself, for example, state data, sensing data, etc., to the smart gateway 100, and the corresponding data is transmitted to the user application device 300 through the smart gateway 100. can be made

The smart gateway 100, the authentication server 200, and the user application device 300 may be connected to each other through an external network, and the external network may include the Internet as a wide area network (WAN). .

The user application device 300 accesses the smart gateway 100 to receive IoT device-related data and display it on the screen. 1 shows a smartphone as the user application device 300, but this is only one example, and the user application device 300 can connect to the smart gateway 100 and receive data as well as the smartphone. It may include various devices, for example, a desktop PC, a tablet PC, a wearable device, a laptop computer, and the like. Also, although FIG. 1 shows only one user application device 300, the number of user application devices 300 may be plural.

An application capable of receiving related data by accessing the smart gateway 100 may be installed in the user application device 300 . The user application device 300 may connect to the authentication server 200 to download and install an application.

The IoT devices 10 operate as lower-order devices for the user application device 300, and the user application device 300 operates as a higher-order device for the IoT devices 10, and communication between them is shown in FIG. It will be described later with reference to the following.

The authentication server 200 mediates the access of the user application device 300 to the smart gateway 100 . Since the user application device 300 does not know the publicIP address for accessing the smart gateway 100 operating as a local server, it can obtain the publicIP address of the smart gateway 100 through the authentication server 200. The user application device 300 may access the smart gateway 100 according to the publicIP address of the smart gateway 100 obtained from the authentication server 200 to receive IoT device-related data and display the data on the screen.

Hereinafter, with reference to FIG. 2 , operations of the smart gateway 100 , the authentication server 200 and the user application device 300 will be described in detail.

2 is a diagram for explaining the operation of the smart gateway 100, the authentication server 200, and the user application device 300.

In step S210, the smart gateway 100 obtains IoT device-related data. Each of the IoT devices 10 may transmit data related to the IoT device, such as its state data and sensing data, to the smart gateway 100 through an internal network.

In one embodiment of the present invention, the IoT device-related data includes state data of the IoT device 10 (eg, battery state information, failure information, etc.), CCTV image data, fire notification data, door opening and closing notification It may include at least one of data, call reception notification data, and trespass notification data.

In addition, in step S210, the smart gateway 100 can check its own user ID, public IP, local IP, and Mac address as a step of identifying local server information.

In step S220, the smart gateway 100 transmits its own identification information and IP address to the authentication server 200 through an external network. Identification information of the smart gateway 100 may include, for example, a MAC address, and an IP address may include a public IP address.

In one embodiment, the smart gateway 100 may further transmit identification information of a terminal accessible to it (eg, the user application device 300) to the authentication server 200.

Depending on the embodiment, in the step S220, the smart gateway 100 periodically provides its user ID, public IP, local IP, and Mac address to the authentication server 200 via the Internet. It can be transmitted, and the authentication server 200 can store the received information in a DB (DataBase). As described later, the purpose of the smart gateway 100 periodically transmitting information is to enable the user application device 300 to find the IP of the local server, and transmits keep alive information at regular time intervals to the smart gateway. This is to enable the user application device 300 to check the normal operating state of (100).

In step S230, the user application device 300 that wants to access the smart gateway 100 first connects to the authentication server 200 and transmits its own identification information to the authentication server 200. The user may access the authentication server 200 through an application installed on the user application device 300 and input ID, which is his or her identification information.

The user application device 300 may store the IP address of the authentication server 200 in advance. For example, an application installed in the user application device 300 may access the initial authentication server 200 according to the IP address of the previously stored authentication server 200 . The identification information of the user application device 300 may include, for example, an ID of a user who has joined as a member or a MAC address of the user application device 300, but is not limited thereto.

In step S240, the authentication server 200 compares the identification information of the smart gateway 100 and the identification information of the user application device 300. The authentication server 200 may map identification information of several smart gateways 100 and identification information of several user application devices 300 and store them in a table. When identification information is received from one user application device 300, The smart gateway 100 mapped to the identification information of the user application device 300 may be specified.

In one embodiment, when identification information of a terminal capable of accessing the smart gateway 100 is transmitted from the smart gateway 100 to the authentication server 200, the authentication server 200 transmits the terminal information received from the smart gateway 100. The smart gateway 100 may be specified by comparing the identification information with the identification information of the user application device 300 .

In step S250, the authentication server 200 transmits the IP address of the smart gateway 100 having identification information mapped to the identification information of the user application device 300 to the user application device 300.

The IP address transmitted from the authentication server 200 to the user application device 300 is an IP address received by the authentication server 200 from the smart gateway 100 .

In step S260, the user application device 300 secondarily accesses the smart gateway 100 according to the IP address received from the authentication server 200.

In step S270, the smart gateway 100 transmits IoT device-related data to the user application device 300, and in step S280, the user application device 300 displays the received IoT device-related data on the screen. In the embodiment, the user application device 300 executes a hybrid app program, which is an IoT program provided by the local server of the smart gateway 100, and receives status information of various IoT devices 10 connected to the smart gateway 100. Alternatively, it is possible to control the operation of the IoT device 10.

Depending on implementation, the IP address of the smart gateway 100 may be a dynamic IP address. In this case, the smart gateway 100 may periodically transmit its IP address to the authentication server 200.

For example, in step S220, the smart gateway 100 may transmit its identification information and IP address to the authentication server 200 every 10 minutes.

After the authentication server 200 transmits the IP address of the smart gateway 100 to the user application device 300 for the first time in step S250, the smart gateway 100 according to the IP address periodically received from the smart gateway 100. If the IP address of ) is changed, the changed IP address can be transmitted to the user application device 300 so that the user application device 300 can smoothly access the smart gateway 100.

3 is an exemplary diagram illustrating a table 350 stored in the authentication server 200.

As described above, the authentication server 200 may map and store identification information of various smart gateways 100 and identification information of the user application device 300 . As shown in FIG. 3, the smart gateway 100 having identification information of 00:90:C0:06:96:31 is mapped to the user application device B, and 01:35:30:AC:DA:32 The smart gateway 100 having identification information of may be mapped to the user application device C. In addition, depending on the implementation, the smart gateway 100 having identification information of 11:22:33:44:55:AB and the smart gateway 100 having identification information of A7:B2:32:21:98:C0 may be mapped to user application device A, which is a case where user A is using two smart gateways 100.

The authentication server 200 updates the table 350 according to the IP address received from each smart gateway 100, and then maps it to the identification information of the user application device 300 according to the connection of the user application device 300. The IP address of the smart gateway 100 to be transmitted to the user application device 300.

3, when the user application device B accesses the authentication server 200, the authentication server 200 has a smart gateway with identification information of 00:90:C0:06:96:31 mapped to the user application device B ( 100) IP address, that is, 255.147.69.1, can be transmitted to the user application device B.

When the user application device A accesses the authentication server 200, the authentication server 200 sends the smart gateway 100 having identification information of 11:22:33:44:55:AB mapped to the user application device A. The IP address of 112.222.101.193 and the IP address of the smart gateway 100 having identification information of A7:B2:32:21:98:C0, ie 255.255.21.101, can be transmitted to the user application device A. The user of the user application device A may access one of the two smart gateways 100 by selecting one of the two IP addresses.

Depending on the implementation, the authentication server 200 may determine that an abnormality has occurred in the smart gateway 100 that has not transmitted identification information and an IP address. For example, it was scheduled to receive identification information and an IP address from each smart gateway 100 at 10:00, but the smart gateway did not transmit the identification information and IP address at 10:00 or within a predetermined time interval from 10:00 ( 100) is present, it can be determined that an abnormality has occurred in the corresponding smart gateway 100. In FIG. 3, when the identification information and the IP address are not received from the smart gateway 100 having identification information C1:34:12:95:BA:00, it is determined that an error has occurred in the corresponding smart gateway 100 and the manager Related information may be transmitted to the terminal.

As described above, when the identification information and the IP address are periodically transmitted from each smart gateway 100 to the authentication server 200, the authentication server 200 periodically determines whether the identification information and the IP address are received or not. It is possible to determine whether the smart gateway 100 is abnormal.

Hereinafter, a communication method between the smart gateway 100, the IoT device 10, and the user application device 300 will be described in detail with reference to FIGS. 4 to 9.

4 is an exemplary diagram illustrating a smart gateway 100, an upper terminal 400, and a lower terminal 500 according to an embodiment of the present invention.

Referring to FIG. 4 , the smart gateway 100 is connected to at least one lower terminal 500 and at least one upper terminal 400 to control communication between them. Here, the upper terminal 400 may include the user application device 300 described with reference to FIG. 1 , and the lower terminal 500 may include the IoT device 10 described with reference to FIG. 1 .

1 shows five lower terminals 500 and three upper terminals 400, but this is only an example, and each of the lower terminals 500 and the upper terminals 400 may be at least one or a plurality. there is.

The smart gateway 100 according to an embodiment of the present invention informs the upper terminal 400 of an event generated in the lower terminal 500 or transmits data to the lower terminal 500 according to the request of the upper terminal 400. can transmit In addition, the smart gateway 100 according to an embodiment of the present invention may determine by itself which terminal to transmit related data to based on data transmitted from the upper terminal 400 or the lower terminal 500.

In one embodiment of the present invention, the upper terminal 400 means a terminal used by a user such as a desktop PC, a smart phone, a tablet PC, a smart watch, and the lower terminal 500 is, for example, various factories Devices, various sensors, various measuring devices, and the like may be included.

5 is a diagram for explaining the functional configuration of the smart gateway 100 according to an embodiment of the present invention.

Referring to FIG. 5 , the smart gateway 100 according to an embodiment of the present invention includes a first web server 110, a web socket 120, a Message Queue Telemetry Transport (MQTT) module 130, and a second web server. 140, a short-distance communication module 150 and a central control module 160 may be included.

The first web server 110 is connected to the upper terminal 400 through HTTP protocol. For example, the upper terminal 400 may transmit data to the first web server 110 through the HTTP protocol while connected to the first web server 110 through the Internet. The IP address of the smart gateway 100 previously described with reference to FIG. 2 may include the IP address of the first web server 110 .

Each of the first higher level terminal 400a and the second higher level terminal 400b shown in FIG. 5 may mean any one of at least one upper level terminal 400 shown in FIG. 4 . Although two upper terminals 400a and 400b are shown in FIG. 5, this is only an example, and one upper terminal 400 or more upper terminals 400 are connected to the first web server 110. may be connected.

The web socket 120 drives an interface that connects the upper terminal 400 and the first web server 110 in both directions. Through the web socket 120, the first web server 110 and the upper terminal 400 can perform bi-directional communication.

The MQTT module 130 is connected to the upper terminal 400 and the lower terminal 500 through the MQTT protocol. The MQTT module 130 uses an open standard messaging protocol, that is, the MQTT protocol, for exchanging messages in a publish/subscribe method through a broker instead of a request/response method of HTTP. Like HTTP, the MQTT protocol operates on top of the TCP/IP protocol, but prevents reliability and speed degradation of existing protocols, as well as battery and performance degradation due to polling.

The second web server 140 is connected to the first lower terminal 500a through the HTTP protocol. For example, the first lower terminal 500a may transmit data to the second web server 140 through the HTTP protocol while connected to the second web server 140 through the Internet. The first lower terminal 500a may correspond to any one of at least one lower terminal 500 shown in FIG. 4 .

The short-distance communication module 150 is connected to the second lower terminal 500b in a short-range communication method. Here, the short-distance communication method may include, for example, Wifi communication, Zigbee communication, Bluetooth communication, USB communication, or RF communication, but is not limited thereto. The second lower terminal 500b may transmit data to the short-range communication module 150 through short-range communication. The second lower terminal 500b may correspond to any one of at least one lower terminal 500 shown in FIG. 4 .

5 shows that the first lower terminal 500a communicates with the second web server 140 and the second lower terminal 500b communicates with the short-range communication module 150, but this is only an example. , all lower terminals 500 may communicate with the second web server 140, all lower terminals 500 may communicate with the short-range communication module 150, or some lower terminals 500 may communicate with the second web server 140. It communicates with the server 140 and the remaining sub-terminals 500 may communicate with the short-range communication module 150 .

The central control module 160 mediates data between the upper terminal 400 and the lower terminal 500 or transmits related data to another terminal according to the state of either terminal.

Although not shown, the smart gateway 100 may further include a database, and the database may store data transmitted from at least one of the upper terminal 400 and the lower terminal 500 .

6 is a diagram for explaining a process of transmitting a push message to an upper terminal 400 according to event data of a lower terminal 500 .

In step S610, the first lower terminal 500a transmits event data to the second web server 140. The event data may include at least one of state data, sensing data, and request data of the first lower terminal 500a.

As described above, the first lower terminal 500a may transmit event data to the second web server 140 according to the HTTP protocol. Depending on implementation, when the first sub-terminal 500a communicates with the short-range communication module 150, the first sub-terminal 500a transmits event data to the short-range communication module 150 according to the short-range communication method. can

In step S620, the second web server 140 (or short-distance communication module 150) transfers the event data to the central control module 160.

In step S630, the central control module 160 generates a first push message corresponding thereto according to the event data and transmits it to the first upper terminal 400a through the web socket 120, and in step S640, the second push message is generated. A message is generated and transmitted to the first upper terminal 400a through the MQTT module 130. That is, the central control module 160 generates two push messages and transmits them to the first upper terminal 400a.

In step S650, the first higher terminal 400a displays at least one of the first push message and the second push message on the screen. Specifically, since the first push message is transmitted through the web, the first higher terminal 400a may receive the first push message through a web application and display the message on the screen. In addition, since the second push message is transmitted according to the MQTT protocol, the first upper terminal 400a may receive the second push message through a native application and display it on the screen.

The first upper terminal 400a (specifically, a web browser) accesses the first web server 110 through the Internet, executes a web application, receives a first push message provided through socket communication, and displays it on the screen. However, when the web application is not executed, the first push message cannot be received. Therefore, in one embodiment of the present invention, the second push message for the MQTT protocol is also transmitted to the first upper terminal 400a, so that when the web application is not running in the first upper terminal 400a, the second push message is transmitted through the native application. This is to allow push messages to be received.

Conversely, when the native application is not running, the first upper terminal 400a may receive the first push message through the web application and display it on the screen.

That is, according to an embodiment of the present invention, regardless of which application is running in the upper terminal 400, the smart gateway 100 transmits two push messages to the upper terminal 400 to transmit the It is to allow administrators to clearly check push messages. In addition, since the upper terminal 400 does not poll event data from the first web server 110, there is an advantage in that the load of the first web server 110 can be reduced.

In step S660, the central control module 160 generates a first push message corresponding thereto according to the event data and transmits it to the second upper terminal 400b through the web socket 120, and in step S670, the second push message is generated. A message is generated and transmitted to the second upper terminal 400b through the MQTT module 130. In step S680, the second higher terminal 400b displays at least one of the first push message and the second push message on the screen.

In steps S660 to S680, the second higher level terminal 400b is connected to the smart gateway 100, and the second higher level terminal 400b connects to the smart gateway 100 together with the first higher level terminal 400a. It may be performed when the user has authority, and steps S660 to S680 may not be performed if the second upper terminal 400b is not connected to the smart gateway 100.

Push messages may also be transmitted to other upper terminals 400 if other upper terminals 400 other than the first upper terminal 400a and the second upper terminal 400b are further connected to the smart gateway 100.

That is, push messages can be transmitted to all upper terminals 400 connected to the smart gateway 100, specifically, to all upper terminals 400 managed by the same user.

Depending on implementation, the first push message and the second push message may be delivered only to the preset upper terminal 400 among several upper terminals 400 according to the event data of the lower terminal 500 .

The central control module 160 may transmit the first push message and the second push message in a unicast manner as in steps S630, S640, S660, and S670, but depending on implementation, the first push message and the second push message may be transmitted. 2 The push message may be transmitted in a multicast method or a broadcast method.

7 is a diagram for explaining a process of transmitting a push message to another upper terminal 400 according to event data of one upper terminal 400 .

In step S710, the first upper terminal 400a transmits event data to the first web server 110. As described above, the first upper terminal 400a may transmit event data to the first web server 110 according to the HTTP protocol. The event data may include at least one of state data, sensing data, and request data of the first upper terminal 400a.

In step S720, the first web server 110 transfers the event data to the central control module 160.

In step S730, the central control module 160 transmits the first push message to the second upper terminal 400b through the web socket 120, and in step S740, the second push message through the MQTT module 130. It is transmitted to the second upper terminal (400b).

In step S750, the second higher terminal 400b displays at least one of the first push message and the second push message on the screen. The second upper terminal 400b may receive the first push message through the web application and display it on the screen, or receive the second push message through the native application and display it on the screen.

According to the embodiment shown in FIG. 7 , the smart gateway 100 may control communication between upper terminals 400 . For example, a first user of the first upper terminal 400a having authority to access the smart gateway 100 communicates with a second user of the second higher terminal 400b having authority to access the smart gateway 100 as well. Event data may be transmitted to the first web server 110 for message transmission and reception, and accordingly, the second user of the second upper terminal 400b may request or report content requested by the first user of the first upper terminal 400a. can confirm.

8 is a diagram for explaining a process of transmitting control command data to the lower terminal 500 according to the control request data of the upper terminal 400 .

In step S810, the upper terminal 400 transmits control request data to the first web server 110 according to the HTTP protocol. The control request data is data transmitted to control the operation of at least one lower terminal 500 .

As an example, when any one lower terminal 500 is a door opening and closing device, the control request data may be request data to open the door. As another example, any one lower terminal 500 In the case of an air conditioner, the control request data may be request data to lower the room temperature.

In step S820, the first web server 110 transmits control request data to the central control module 160, and in step S830, the central control module 160 generates control command data. The control command data may be data conforming to the MQTT protocol.

In step S840, the central control module 160 transmits the control command data to the first lower terminal 500a through the MQTT module 130, and in step S850, the first lower terminal 500a according to the control command data It performs a corresponding function (eg, a function of opening a door, a function of lowering the indoor temperature, etc.).

In step S860, the central control module 160 transmits the control command data to the second lower terminal 500b through the MQTT module 130, and in step S870, the second lower terminal 500b according to the control command data perform the corresponding function.

Steps S860 and S870 are performed when the control request data of the upper terminal 400 is transmitted to the second lower terminal 500b, and the control request data of the upper terminal 400 is transmitted to the first lower terminal ( In the case of transmission only for function control of 500a), steps S860 and S870 may not be performed.

The central control module 160 may transmit the control command data in a unicast manner as in steps S840 and S860, but may also transmit the control command data in a multicast manner or a broadcast manner, depending on implementation. In this case, the first lower terminal 500a and the second lower terminal 500b receive the control command data transmitted in the multicast method or the broadcast method, and respond to it only when the control command data is targeting them. It may also perform the function of

Meanwhile, depending on the embodiment, in the step S830, the central control module 160 analyzes the control request data of the upper terminal 400, generates a plurality of control command data accordingly, and each of the plurality of control command data may be transmitted to different lower terminals 500. In other words, when the control request data is received, the central control module 160 interprets it to generate a control command data, b control command data, and c control command data, and the a control command data is transmitted to the lower terminal 500. , b control command data can be transmitted to the b sub-terminal 500 and c control command data to the c sub-terminal 500.

As an example, when the control request data of the upper terminal 400 is a request to lower the indoor temperature, the central control module 160 generates control command data to lower the set temperature of the air conditioner, transmits the control command data to the air conditioner, and It is possible to generate control command data to close the door and transmit it to the door opener.

That is, according to an embodiment of the present invention, the smart gateway 100 interprets the control request data of the upper terminal 400 and controls the lower terminals 500 to meet the intention, so that the upper terminal 400 is used. User convenience can be increased.

Meanwhile, depending on implementation, control request data targeting the same lower terminal 500 may be transferred from the first upper terminal 400a and the second upper terminal 400b to the central control module 160. In this case, the central control module 160 generates control command data based on only one of the control request data of the first higher level terminal 400a and the control request data of the second higher level terminal 400b to generate the corresponding lower level terminal 500. can be forwarded to Since the two upper terminals 400 can transmit contradictory control request data to the central control module 160, the central control module 160 gives a control command based on only one of the two contradictory control request data. is to generate data.

For example, the control request data of the first higher level terminal 400a is control request data for causing the air conditioner to lower the room temperature, and the control request data of the second higher level terminal 400b is control requesting the air conditioner to raise the room temperature. In the case of requested data, the central control module 160 selects a higher-order terminal 400 having a higher priority among the first higher-order terminal 400a and the second higher-order terminal 400b, for example, the first higher-order terminal 400a. According to the control request data of the control command data to lower the room temperature to the air conditioner may be transmitted.

9 is a diagram for explaining a process of transmitting control command data to another lower terminal 500 according to event data of one lower terminal 500 .

In step S910, the first lower terminal 500a transmits event data to the second web server 140 according to the HTTP protocol.

In step S920, the second web server 140 transfers the event data to the central control module 160.

In step S930, the central control module 160 analyzes the event data to generate control command data, and in step S940, the control command data is transmitted to the second lower terminal 500b through the MQTT module 130.

In step S950, the second lower terminal 500b performs a function corresponding to the control command data.

The embodiment shown in FIG. 9 is a process in which the smart gateway 100 controls communication between lower terminals 500, and the communication of other lower terminals 500 according to an event occurred in one lower terminal 500. to control the function.

For example, if the event data transmitted from the first lower terminal 500a is fire notification data, the central control module 160 may transmit control command data to eject water to the sprinkler device based on this. .

Hereinafter, the configuration of the smart gateway 100 according to an embodiment of the present invention will be described in terms of software and hardware.

10 to 12 are exemplary diagrams showing software blocks of the smart gateway 100 according to an embodiment of the present invention.

10 to 12 show an authentication server 200, a user application device 300, and several IoT devices (Internet phone, fire detection sensor, IoT box, etc.) 10 together with the smart gateway 100. there is.

The smart gateway 100 according to an embodiment of the present invention is a software module, and may include an IoT engine 1010 and a local server 1030. In addition, the smart gateway 100 may include a hardware module for connection with the IoT engine 1010 and input/output of network, ZigBee, and RF.

The IoT engine 1010 is software for implementing the Internet of Things (IoT) in the smart gateway 100, and various frameworks required to run the IoT engine 1010 on OS such as Windows 10 IoT and Linux are installed. and developed in programming languages such as Python, C++, and Node.Js.

Specifically, the IoT engine 1010 may be composed of the following software or algorithm modules.

1) IoT H/W Input/Output Interface: Sensors directly connected to the system H/W in the smart gateway 100 and communication modules such as various H/W, that is, NFC modules, display modules such as LED and LCD, WCDMA modules, LTE modules, etc. interface program to control

2) IoT Device Interface: I/O processing software with IoT Device (10), such as a sensor connected through a Zigbee module in the smart gateway (100), and I/O processing with IoT Device (10) connected through wireless communication such as RF433MHz and RF447MHz modules Software, input/output processing algorithm and software with IoT Device (10) connected by wireless communication such as Bluetooth and Wi-Fi.

3) Smart IoT Box interface: As an input/output processing algorithm and software with a smart box connected by USB communication from the smart gateway 100, the smart box is basically a microcom platform such as Arduino H/W Consists of Sensor and Actuator H/W, and can be connected up to 20 with Smart Gateway (100) by USB method. Characteristically, the connection protocol between the smart gateway 100 and the smart box interfaces data in a format such as JSON or XML as a RESTful API.

4) VoIP system CTI interface: CTI events of VoIP system, such as internet phone, are interfaced with RESTful API, and when the network device transmits the signal of VoIP system, such as internet phone, to the smart gateway 100 through Ethernet via port mirroring, Internet phone During inbound, a CTI event push is generated through the SIP Protocol Interpreter, and 　 is displayed as a pop-up on the user application device 300. Also, for phone recording, G.711 PCM signals are modulated and demodulated to generate audio files such as Wave files. Algorithms and software stored in the smart gateway (100).

5) Smart Gateway IP Search: Software that broadcasts through UDP communication so that the user application device 300 connected to the same network can find the public IP and local IP of the smart gateway 100.

6) Sound Play QueueInterface: In order to effectively process the sound signal in the smart gateway 100, the stored sound file is played when an IoT event occurs, and at this time, the data is queued in the sound buffer for real-time processing Algorithms and software that store the sound processing, skip it as needed if the sound processing is delayed, and execute the final sound.

7) Local Server Database Interface: IoT-related information is stored in a database such as MySQL installed on the local server 1030 in the smart gateway 100, and Create, Insert, and Update of this database Software that handles (Modify), Delete (Delete).

8) MQTT Event interface: In order to provide the user application device 300 with a PUSH notification service for the event of the IoT device 10, an MQTT Server is installed in the smart gateway 100, and MQTT Broker, Publisher, Subscriber, etc. Software that generates and handles PUSH events corresponding to IoT events.

9) Web Socket Event Interface: In order to provide a PUSH notification service for the event of the IoT Device (10) to the user application device (300) running the hybrid App, a web socket program is developed and embedded in the smart gateway (100) and IoT Software that displays and processes a PUSH Event in a web socket method on the user application device 300 when an event occurs.

10) Authentication server (Auth Server) 200 interface: Periodically transmits data to the authentication server 200 to check the information and operation status of the smart gateway 100, and the user application device 300 uses the smart gateway ( Algorithm and software that connects to a local server through address information such as Public IP and Local IP of 100) and enables monitoring whether the smart gateway 100 operates normally.

11) Local server interface: Software that directly interfaces and stores IoT information in the database of the local server in the smart gateway 100.

12) RESTFul API Interface: Algorithms and software that process the RESTFul API method corresponding to the IoT protocol and interface the necessary information by interpreting the requested information from the user application device (300).

Next, the local server 1030 installs a web server such as Apache and a server interpreter program such as PHP, JSP, and ASP in the smart gateway 100, which is the same system as the IoT engine, and installs HTML, It is a structure operated by uploading a Hybrid App program developed in PHP, JavaScript, etc., and is a platform that provides services by being connected to the Public IP or Domain of the smart gateway 100.

Specifically, the local server 1030 may be configured with the following software or algorithm modules.

1) HTTP Server: Linux Apache Server or Window IIS Server

2) Web Server

- PHP Server, JSP Server, ASP Server

- Server-side scripting languages: PHP, JSP, ASP

- Client Language: Java Script

3) DataBase Server: Stores IoT-related information in databases such as MySql and MsSQL.

4) FTP Server: Web programs can be uploaded from the developer system through the FTP server.

5) Hybrid App Program: As a Hybrid App program developed with HTML5, CSS3, PHP, JavaScript, Jquery Mobile, AJAX, etc., it is uploaded to the program storage space.

6) Local Storage: Installed in the data file space of the smart gateway 100 and configured by uploading Application Program Source, Audio Record File, Document File, etc. through FTP Server.

Meanwhile, the above-described embodiments of the present invention can be written as a program that can be executed on a computer, and the written program can be stored in a medium.

The medium may continuously store programs executable by a computer or temporarily store them for execution or download. In addition, the medium may be various recording means or storage means in the form of a single or combined hardware, but is not limited to a medium directly connected to a certain computer system, and may be distributed on a network. Examples of the medium include magnetic media such as hard disks, floppy disks and magnetic tapes, optical recording media such as CD-ROM and DVD, magneto-optical media such as floptical disks, and ROM, RAM, flash memory, etc. configured to store program instructions. In addition, examples of other media include recording media or storage media managed by an app store that distributes applications, a site that supplies or distributes various other software, and a server.

In the above, the technical spirit of the present invention has been described in detail with preferred embodiments, but the technical spirit of the present invention is not limited to the above embodiments, and those skilled in the art within the scope of the technical spirit of the present invention Various modifications and changes are possible by the person.

10: IoT devices
100: smart gateway
110: first web server
120: web socket
130: MQTT module
140: second web server
150: short-range communication module
160: central control module
200: authentication server
300: user application device
400: upper terminal
500: lower terminal
1010: IoT engine
1030: local server

Claims (11)

A smart gateway connected to IoT devices including sensors and actuators to interface IoT-related data;
an authentication server receiving identification information and an IP address of the smart gateway from the smart gateway; and
Including a user application device connected to the smart gateway and the Internet to display and control IoT services,
The user application device firstly accesses the authentication server to obtain the public IP address of the smart gateway, and secondarily accesses the smart gateway according to the obtained public IP address to receive the IoT device-related data, An IoT system characterized in that it can be displayed on the screen or control the IoT device from the user application device.
According to claim 1,
The IoT system, characterized in that the local server is executed by itself in the smart gateway to provide IoT services in a distributed manner.
According to claim 1,
The authentication server,
When the smart gateway operates, at least one information of Public IP, Local IP, and Mac Address of the smart gateway identified by the IoT engine of the smart gateway is received, and the user ID is received from the user application device and stored in the database. IoT system characterized in that.
According to claim 1,
The authentication server,
When the smart gateway is operated, the IoT engine of the smart gateway receives keep alive information including the user ID periodically at regular time intervals and stores it in a database to monitor whether the smart gateway operates normally, and to monitor whether the smart gateway operates normally. When transmission is interrupted, it is determined that an abnormality has occurred in the smart gateway, and a screen indicating an abnormal state is displayed on the user application device.
According to claim 1,
When the IoT program starts in the user application device, it first connects to the authentication server and executes the login program. When user authentication is confirmed in the login step, public IP address information of the smart gateway is received from the authentication server. IoT system characterized in that it connects to the local server of the smart gateway secondarily.
According to claim 1,
The smart gateway includes an IoT engine and a local server, and the IoT engine is connected to a plurality of IoT devices and contains algorithms and programs for controlling the plurality of IoT devices. An IoT system characterized in that it provides an IoT program as an application device.
The method of claim 1, wherein the IoT device,
IoT information is exchanged with the smart gateway through wired or wireless communication, and CCTV image data, fire notification sensor data, door opening and closing sensor data, and temperature and humidity sensor data are transmitted through ZigBee, Bluetooth, Wi-Fi, and 400Mhz wireless communication. and transmitted to the smart gateway.
The smart box including the IoT sensor and actuator is connected to the smart gateway by USB method and exchanges information through a RESTful API protocol. IoT management system, characterized in that it comprises at least one of the notification data.
A web server installed to provide web programs to user application devices;
An IoT engine including a web socket server algorithm and software to transmit a web socket push event to the user application device, and an MQTT Broker, Publisher, and Subscriber algorithm and software to transmit a push event to the user application device; and
Based on the event data received from the IoT device, an algorithm and control software for transmitting a push message to the user application device through the IoT engine of the smart gateway in the web socket method and the MQTT method Smart characterized in that it comprises gateway.
According to claim 8,
When an event occurs in the IoT device, the smart gateway transmits the event to the user application device in a push method through the web socket processing software of the IoT engine, and the hybrid app program of the user application device displays a pop-up alarm on the screen. and
When an event occurs in the IoT device, the smart gateway transmits data in a push method to the user application device through the MQTT Publisher in the IoT engine, and the native app program of the user application device displays a pop-up notification on the screen, A smart gateway characterized by generating a notification sound.
According to claim 9,
The hybrid app program may make a web socket control request to the smart gateway to control the IoT device, and the smart gateway may control the IoT device according to a control command,
The native app program may request control through an MQTT Publisher to the smart gateway to control the IoT device, and the smart gateway controls the IoT device according to a control command Smart gateway.
According to claim 8,
The smart gateway, characterized in that for receiving the event data through a Zigbee (Zigbee), Bluetooth, short-range communication method of 400MHz band with the IoT device.