KR102006219B1 - SYSTEM AND METHOD FOR AUTO CONFIGURATION OF IoT NODES - Google Patents

Abstract

The present invention relates to an IoT node automatic configuration system and method for facilitating a process of acquiring data and managing nodes such as sensors and drivers in an IoT environment.
The IoT node automatic configuration system according to the present invention includes a memory for storing an application requesting / responding to the value of an IoT node and a controller for executing the application, wherein the controller obtains the equipment profile of the IoT node to determine the manufacturer-specific identifier and address. When the mapping table is constructed and the identifier-based data request received from the user terminal is received through the application, the identifier-based data request is automatically converted into a register address-based data request for each IoT node.

Description

SYSTEM AND METHOD FOR AUTO CONFIGURATION OF IoT NODES}

The present invention relates to an IoT node automatic configuration system and method for facilitating a process of acquiring data and managing nodes such as sensors and drivers in an IoT environment.

According to the prior art, a control application (SW) is designed and used based on address (address) information of a memory in which data is stored for each product such as a sensor and a driver.

In the case of using such a control application, a request / response for acquiring data of each node is made based on a predefined manufacturer-specific register address. There is a problem that the adaptability to the changed environment is inferior since it is available only after newly coding.

The present invention has been proposed to solve the above-mentioned problem, and automatically configures a mapping table of manufacturer-specific identifiers and registers for installed IoT nodes, automatically converts an identifier-based request into an address-based request, and responds to the request. By receiving, the object of the present invention is to provide an IoT node auto-configuration system and method that can secure universality even when a change such as addition of an IoT node occurs, without requiring modification of the application itself.

The IoT node automatic configuration system according to the present invention includes a memory for storing an application requesting / responding to the value of an IoT node and a controller for executing the application, wherein the controller obtains the equipment profile of the IoT node to determine the manufacturer-specific identifier and address. When the mapping table is constructed and the identifier-based data request received from the user terminal is received through the application, the identifier-based data request is automatically converted into a register address-based data request for each IoT node.

The method for automatically configuring an IoT node according to the present invention includes recognizing a connection of an IoT node, obtaining identification information of the recognized IoT node, and using the identification information of the IoT node, for a memory address where data of the IoT node is stored. The method includes acquiring an equipment profile and receiving an identifier-based data request, and automatically converting the equipment profile into a register address-based data request for each IoT node.

According to the IoT node automatic configuration system and method according to an embodiment of the present invention, the application (control application SW) is composed of a common SW for transmitting (relaying) an identifier-based request, the automatic configuration module is based on the identifier received from the user It automatically converts the request into a register-based request to perform the request / response on the value of the IoT node. Even if an event such as adding or replacing an IoT node occurs, code modification of the application (control application SW) is unnecessary. However, there is an effect that is adaptive and universally applicable.

The effects of the present invention are not limited to those mentioned above, and other effects that are not mentioned will be clearly understood by those skilled in the art from the following description.

1 is a diagram illustrating a system to which an integrated node controller according to the prior art is applied.
2 is a view showing the configuration of an integrated node controller according to the prior art.
3 is a sequence diagram showing a data acquisition process according to the prior art.
4 is a diagram illustrating an IoT node automatic configuration system according to the present invention.
5 is a sequence diagram showing a method for automatically configuring an IoT node according to the present invention.

BRIEF DESCRIPTION OF THE DRAWINGS The above and other objects, advantages and features of the present invention, and methods of achieving them will be apparent with reference to the embodiments described below in detail with the accompanying drawings.

However, the present invention is not limited to the embodiments disclosed below, but may be implemented in various forms, and only the following embodiments are provided to those skilled in the art to which the present invention pertains. It is merely provided to easily inform the configuration and effects, the scope of the present invention is defined by the description of the claims.

It is to be understood that the terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. In the present specification, the singular form includes plural forms unless otherwise specified in the specification. As used herein, “comprises” and / or “comprising” refers to the presence of one or more other components, steps, operations and / or devices in which the mentioned components, steps, operations and / or devices are described. Or does not exclude addition.

Hereinafter, in order to help those skilled in the art to understand the present invention will be described first with respect to the background, the embodiment of the present invention will be described.

1 is a diagram illustrating a system to which an integrated node controller 10 according to the related art is applied.

As the node 20, sensor #a, sensor #b, sensor #c and driver #d are installed (connected), and the analog values obtained from the sensor and the driver are connected to the input / output units IO and 11 and the ADC 12. Is passed to the processor 14.

Instructions issued from the processor 14 are transmitted to the outside through the communication module 15.

For example, the value of each node 20 is information about temperature, humidity, roughness, soil moisture, and the like, for example, and these are stored in memory addresses defined by the manufacturer of the product.

As shown in FIG. 1, the application 13 of the controller 10 builds a mapping table for what data is stored for each address.

The application 13 according to the prior art could only code at which address the node's value is stored (i.e., an address map).

For example, if the temperature value obtained by the sensor #a of the node 20 is stored at address # 100, the application 13 includes the item in the mapping table, and when a request from the user to know the temperature value comes, The processor 14 issues a command to retrieve the data stored in # 100.

Referring to FIG. 2 illustrating a configuration of an integrated node controller according to the prior art, as described above, the application 13 and the processor 14 of the controller 10 perform a request and response for a register map for each manufacturer and model. do.

The integrated node controller 10 according to the prior art is implemented by including hardware and an application (control application). As a remote type of implementation, it is also possible to connect a control application and a processor by networking using a communication module.

Hereinafter, a register address based request / response according to the prior art will be described with reference to FIG. 3.

Referring to FIG. 3, the integrated node 20A manufactured by Company A may have a sensor #a value at address # 1, a sensor #b value at address # 2, a sensor #c value at address # 3, and a driver. It is assumed that the #d value is designed to be stored at address # 4.

In addition, assuming that the integration node 20B manufactured by Company B is designed to store the driver #e value at address # 1, the sensor #f value at address # 2, and the sensor #g value at address # 3. Explain.

According to the prior art, the application 13 could only be coded by knowing at which address the address of each value is stored, i.e., knowing the address map.

Referring to FIG. 3, the user terminal 30 requests to know the sensor #a value, #b value, #c value, and driver #d value (GET_VAL {sensor #a, sensor #b, sensor #c, driver # d}).

In order to obtain each request value, the application 13 requests a value based on a register address requesting a value by referring to an address number where each request value is stored (GET_VAL {Addr # 1, Addr # 2, Addr # 3, Addr # 4). }) Is configured and delivered to the processor 14, which transmits it to the integration node 20A.

The processor 14 receives the response (PUT_VAL {Addr # 1, Addr # 2, Addr # 3, Addr # 4}) from the integrated node 20A and forwards it to the application 13, and the application 13 ) Displays the register address based response (PUT_VAL {Addr # 1, Addr # 2, Addr # 3, Addr # 4}) before the user request value is displayed through the UI. , Sensor # b, sensor # c, driver # d}) and transmits the same to the user terminal 300.

When the user terminal 300 sends a request (GET_VAL {sensor #g, sensor #f, driver #e}) to know the sensor #g value, the #f value, and the driver #e value, the application 13 may be instrumented. By using the address map, it configures a register address-based request (GET_VAL {Addr # 3, Addr # 2, Addr # 1) that refers to an address number and requests a value, and delivers the same to the processor 14, and the processor 14 Sends it to the integration node 20B.

The processor 14 receives the response (PUT_VAL {Addr # 3, Addr # 2, Addr # 1}) from the integration node 20B and forwards it to the application 13, and the application 13 receives a user request value. The register address-based response (PUT_VAL {Addr # 3, Addr # 2, Addr # 1}) is sent to the identifier-based response (PUT_VAL {sensor # g, sensor # f, driver #e}) ) Is converted to the user terminal 30 and transmitted.

That is, according to the prior art, the request / response between the application 13-the processor 14 and the processor 14-the integration node 20A, 20B is a request address / response based on the register address, each application 13 Only those who are familiar with the manufacturer's address map can design it.

In the situation of FIG. 3, it is assumed that only an integrated node 20A of a manufacturer A is connected to a specific greenhouse, and an integrated node 20B of a B manufacturer is newly added.

According to the prior art, since the application 13 has only the address map information of the integrated node 20A of the A manufacturer, the sensor #g, the sensor # of the integrated node 20B of the B manufacturer using the corresponding application 13 is used. f, it is not possible to retrieve the driver #e value.

That is, as the connection node 20B of the manufacturer B is connected, the acquired value may not be immediately identified, and the service provider may determine address map information of the integration node 20B of the manufacturer B, that is, what value is stored at which address. Next, the application 13 should be modified to enable configuration related to the B manufacturer.

In other words, according to the related art, when the sensor / driver is changed, such as adding a sensor, the inconvenience of changing the instrumented application itself is required. There is a problem that it can be used only by changing the configuration and changing the configuration logic itself.

The present invention has been proposed to solve the above-described problem, and on the premise of a common application that does not perform configuration, an automatic configuration module included in a processor automatically configures a mapping table for identifier-registers for each manufacturer, and from a user terminal. By automatically converting the received identifier-based request into an address-based request, we propose a new integrated controller that can be adaptively applied without changing the application in a changed situation such as adding an IoT node.

According to the present invention, 1) a request / response for a model-specific register map is performed between a controller and an equipment profile server, 2) an identifier-based request / response is performed between an application and a processor, and 3) a request between processor-integrated nodes. Proposes an IoT node automatic configuration system in which a manufacturer-specific request converted by each integration node is performed and the response is performed by a manufacturer-specific response based on a register address.

The equipment described in the embodiment of the present invention is a concept including an IoT node which is a device including sensing and communication functions, and an IoT node which is a device including driving and communication functions.

4 is a diagram illustrating an IoT node automatic configuration system according to the present invention.

The IoT node automatic configuration system according to an embodiment of the present invention is a controller including a memory (not shown) storing an application 130 requesting / responding to a value of an IoT node and a processor 140 for executing the application 130. It consists of 100.

Unlike the prior art described above, the application 130 is a common SW that receives an identifier-based request (eg, get temperature) and delivers it to the processor 140 (relay).

As shown in FIG. 4, the application 130 and the processor 140 according to an embodiment of the present invention perform an identifier-based request / response regardless of a manufacturer, unlike the prior art.

The IoT node 200 collectively refers to a sensor / driver and is a concept that also includes referring to each individual sensing stage / each individual driving stage.

As described above, the equipment is a concept including an IoT node including sensing and communication functions, and an IoT node including driving and communication functions.

The controller 100 according to an embodiment of the present invention includes an internal communication module 150, and the internal communication module 150 communicates with the communication module 210 of the IoT node 200.

The internal communication module 150 and the communication module 210 of the IoT node 200 may convert the request / response of the identification information (model identifier, number, text, barcode, image, etc.) of the IoT node 200 and each IoT node. Send and receive data requests and register address-based responses.

The external communication module 160 of the controller 100 according to an embodiment of the present invention requests a register map for each model of the IoT node 200 to the equipment profile server 400, and receives the response (material profile) to automatically receive the response. Transfer to configuration module 141.

Equipment profile server 400 may exist in a variety of aspects, such as cloud, personal, etc. In the following will be described by exemplifying its name as "material profile server" to help those skilled in the art to understand.

The equipment profile server may be an integrated server that stores / manages profiles of IoT nodes of all manufacturers, or may be individual servers that store / manage profiles of IoT nodes for each manufacturer.

Processor 140 according to an embodiment of the present invention includes an automatic configuration module 141, the automatic configuration module 141 obtains the equipment profile of the IoT node 200 to map the mapping table of the manufacturer-specific identifiers and addresses, namely Build a manufacturer-specific mapping table 141-2.

The equipment profile obtained by the automatic configuration module 141 is obtained from the equipment profile server 400 as described above, or directly from the IoT node 200.

For example, if the IoT node 200 transmits a model identifier (in which case, the transmission of the model identifier may occur as the controller interface is newly activated, so that the controller recognizes the connection of the new IoT node and returns the model identifier to the new IoT node). Transmitted as a response in response to the request), the controller 100 obtains the equipment profile of the corresponding IoT node from the equipment profile server 400 using the model identifier.

At this time, the controller 100 first checks whether or not the register map information for the received model identifier is stored in the manufacturer-specific mapping table 141-2, and if it is not stored, to the equipment profile server 400. Request the equipment profile of the IoT node.

As another example, when the IoT node 200 transmits a model identifier and its equipment profile, the controller 100 receives it.

As another example, when the IoT node 200 transmits a model identifier, the controller 100 checks whether register map information is previously stored in the manufacturer-specific mapping table 141-2 for the corresponding model identifier. If it is not stored, it requests the equipment profile transmission to the IoT node 200, and directly receives the equipment profile from the IoT node 200.

When the automatic configuration module 141 according to an embodiment of the present invention receives an identifier-based data request of the user terminal through the application 130, the IoT-based module requests the identifier-based data request through the identifier-register converter 141-1. It automatically converts the register address-based data request for each node and transmits it to the IoT node 200 through the internal communication module 150.

For example, if Company A stores the sensed temperature value at address # 100, and Company B stores the sensed temperature value at address # 1000, the automatic configuration module 141 "differs in temperature value". Automatically converts the request to get the value stored at address # 100 and the request to get the value stored at address # 1000.

At this time, the automatic configuration module 141 automatically converts an identifier-based data request into a register address-based data request for each IoT node, but if it is configurable into a single message, generates a request message based on a single equipment register address. If not composed of messages, it generates a request message based on multiple equipment register addresses.

The application 130 according to the embodiment of the present invention transfers the identifier-based request to the processor 140 as it is, and the configuration process is not performed in the application 130.

That is, as mentioned above, the application 130 is a common SW that transmits an identifier-based request. Even when the IoT node 200 is newly added, the application 130 may have a mapping to the application 130 in order to obtain the data. No coding modifications are necessary.

The internal communication module 150 of the controller 100 according to an embodiment of the present invention receives a response to a register address based data request from the communication module 210 of the IoT node 200, and sends it to the automatic configuration module 141. To pass.

The automatic configuration module 141 automatically converts the register address based data response into the identifier based data response using the identifier-register converter 141-1 and the manufacturer-specific mapping table 141-2. Pass (display) to the user via.

Hereinafter, a method of automatically configuring an IoT node according to an embodiment of the present invention will be described with reference to FIG. 5.

The controller 100 according to the embodiment of the present invention includes the processor 140, the internal communication module 150, and the external communication module 160 as described above. The processor 140 includes an autoconfiguration module 141, and the autoconfiguration module 141 includes an identifier-register converter 141-1 and a manufacturer-specific mapping table 141-2.

FIG. 5 shows a sequence diagram, illustrated by the controller 100, rather than each detailed component, to aid those skilled in the art.

The controller 100 detects an event in which the IoT node 200 is newly installed (S100).

At this time, when the controller interface is newly activated, the processor 140 recognizes that the new IoT node 200 is connected, and identifies information (model identifier) of the IoT node 200 through the internal communication module 150. Transmits a message requesting (S150).

The model identifier is transmitted as at least one of a number, text, barcode, and image, and is information for identifying a model of the IoT node.

From the communication module 210 of the IoT node 200, the internal communication module 150 of the controller 100 returns a model identifier of the IoT node 200 (S150).

The controller 100 checks the model identifier of the received IoT node 200, checks whether the model is already included in the manufacturer-specific mapping table 141-2, and writes to the manufacturer-specific mapping table 141-2. If the new model does not exist, the model identifier of the IoT node 200 is transmitted to the equipment profile server 400 through the external communication module 160 of the controller 100, and the equipment profile is requested (S250). .

Although FIG. 5 illustrates obtaining the equipment profile of the IoT node 200 from the equipment profile server 400, as described above, the equipment profile may be directly obtained from the IoT node 200. N

The equipment profile server 400 may be implemented in various aspects such as cloud and personal, and transmits the corresponding descriptor profile by referring to the model identifier of the IoT node 200 (S300), which is an external communication module 160. Is sent to the automatic configuration module (141).

The automatic configuration module 141 included in the processor 140 of the controller 100 stores the equipment profile and builds a mapping table for each manufacturer (S350).

In this process, the IoT node 200 is designed to store the sensor #a value, the sensor #b value, the sensor #c value, and the sensor #d value at address # 1, address # 2, address # 3, and address # 4, respectively. Assume that

The user terminal 300 transmits the identifier-based data request through the application (S400).

The application 130 bypasses the received identifier-based data request, GET_VAL {sensor # a, sensor # b, sensor # c, and sensor # d} to the processor 140 of the controller 100. (S450).

The auto configuration module 141 of the controller 100 performs auto configuration for the identifier-based data request, so that the register address-based data request GET_VAL {Addr # 1, Addr # 2, Addr # 3, Addr # 4} is automatically converted (S500).

Upon receiving the register address based data request (S550), the IoT node 200 transmits the register address based data response PUT_VAL {Addr # 1, Addr # 2, Addr # 3, Addr # 4} to the automatic configuration module of the controller 100 ( 141) (S600).

The autoconfiguration module 141 automatically converts the register address based data response into an identifier based data response, that is, PUT_VAL {sensor # a, sensor # b, sensor # c, sensor # d} (S650), thereby converting the application 130. Through the transmission to the user terminal 300 (S700, S750).

According to an embodiment of the present invention, the application 130 is configured to bypass the identifier-based data request and the identifier-based data response to the controller 100 and the user terminal 300, respectively, and does not perform any configuration role.

Therefore, even when a new IoT node is connected, no modification to the application itself is required, and according to the present invention, auto-configuration is performed by the autoconfiguration module 140 of the controller 100. In this situation, the IoT node can be managed and used adaptively and universally.

So far I looked at the center of the embodiments of the present invention. It will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the invention as defined by the appended claims. Therefore, the disclosed embodiments should be considered in an illustrative rather than a restrictive sense. The scope of the present invention is defined by the appended claims rather than by the foregoing description, and all differences within the scope of equivalents thereof should be construed as being included in the present invention.

10: controller 11: input / output unit
12: ADC 13: Application
14: processor 15: communication module
20: node 30: user terminal
100: controller 130: application
140: Processor 141: Autoconfiguration Module
141-1: Identifier-register converter 141-2: Manufacturer-specific mapping table
150: internal communication module 160: external communication module
200: IoT node 210: communication module
300: user terminal 400: equipment profile server

Claims (11)

A memory storing an application requesting / responding to a value of an IoT node; And
A controller for executing the application,
The controller acquires the equipment profile of the IoT node, constructs a mapping table of identifiers and addresses for each manufacturer, and receives the identifier-based data request received from the user terminal through the application. When the IoT node automatically converts to a register address based data request and receives a register address based data response from the IoT node, the register address based data response is automatically converted into an identifier based data response to the user through the application. Conveying
IoT node autoconfiguration system.
The method of claim 1,
The controller recognizes that a new IoT node is connected as the controller interface is newly activated, and requests the new IoT node to return a model identifier.
IoT node autoconfiguration system.
3. The method of claim 2,
The controller requests the register map of the connected IoT node to the equipment profile server, and stores the obtained equipment profile of the IoT node.
IoT node autoconfiguration system.
3. The method of claim 2,
The controller receiving the equipment profile from the IoT node
IoT node autoconfiguration system.
The method of claim 1,
The controller automatically converts the identifier-based data request into a register address-based data request for each IoT node, and generates and transmits a request message based on a single equipment register address if composed of one message, and not composed of one message. Otherwise, generate and send a request message based on multiple equipment register addresses.
IoT node autoconfiguration system.
delete (a) recognizing a connection of an IoT node and obtaining identification information of the recognized IoT node;
(b) obtaining a material profile for a memory address where data of the IoT node is stored using the identification information of the IoT node;
(c) receiving an identifier-based data request and automatically converting it into a register address-based data request for each IoT node; And
(d) receiving a response to the register address-based data request from the IoT node, and automatically converting it to an identifier-based data response and delivering it to a user through an application.
IoT node automatic configuration method comprising a.
The method of claim 7, wherein
In step (b), the identification information of the IoT node is transmitted to an equipment profile server to receive the equipment profile, and a mapping table for identifiers and registers for each manufacturer is generated.
How to automatically configure IoT nodes.
The method of claim 7, wherein
Step (b) is to directly receive the equipment profile from the IoT node
How to automatically configure IoT nodes.
The method of claim 7, wherein
In step (c), the identifier-based data request transmitted from the user terminal receives the identifier-based data request as it is, and the identifier-based data request is referred to the register address with reference to the equipment profile. Automatic conversion to data-based requests
How to automatically configure IoT nodes.
delete

Images