KR20180094584A - Fusion type internet of things middleware system - Google Patents

Abstract

The present invention provides an integrated internet-of-things (IoT) middleware system which integrates functions of multiple types of middleware to unify the functions and play an excellent role in efficiency, cost reduction, and optimization. The integrated IoT middleware system comprises: an edge middleware unit to perform connection to an IoT device and an RFID device, and transmit information recognized by the IoT device and the RFID device to an integrated middleware unit; a mobile middleware unit to perform connection to a client, perform a database job based on a command for the corresponding database job from the client, and transmit a result value to the client; and the integrated middleware unit to manage the edge middleware unit and an IoT device and an RFID device connected to the edge middleware unit, and generate a report based on values from the IoT device and the RFID device received via the edge middleware unit to output the report.

Description

Fusion type internet of things middleware system

BACKGROUND OF THE INVENTION 1. Field of the Invention [0002] The present invention relates to a converged-type Internet middleware system, and more particularly, to a converged-type Internet middleware system using an access network technology for industrial IoT multi-device connection required for introduction of SMART Factory.

Conceptual extension of RFID / USN standard technology and objects with sensors, drivers and contextual cues provide connectivity between people, objects, objects and objects through various network technologies, Service.

Object Internet services that can support and seamlessly integrate the global concept of Internet of Things (IoT) have not yet appeared. In addition to the technical problems, various countries, industries, society, personal interests, policies, and security issues are inherent in the Internet.

In addition, it is necessary to spread intelligent sensor services that anyone can use, install, access, develop, and utilize sensors without conscious of the vast USN technology / infrastructure that has been built so far.

In the current convergence type IoT middleware, an operating program is separately installed for each hardware device and a separate customization is required. In other words, current IoT software (SW) can be used for RFID, NFC, barcode, BLE, beacon, GPS, temperature sensor, humidity sensor, motion sensor, weight sensor, LPR, LED, wearable equipment, and smart device operating program should be separately installed and customized.

The SI main system, which is the existing IoT SW, has increased maintenance and management costs due to the operation of each program. In other words, the separation of IoT SW (individual program) has increased management object and management cost. Also, since it is individually developed software, installation and management costs are high. It is also vulnerable to flexible interworking with smart devices.

On the other hand, when three or more IoT sensing devices (barcode, Bluetooth, GPS, temperature / humidity / motion / weight sensor, car number and camera recognition, . In other words, expensive software must be developed to utilize each IoT sensing device. And, due to the use of high performance server system, hardware performance is limited due to middleware and related applications.

In other words, there are various sensing devices (barcode, RFID, NFC, BLE, beacon, GPS, temperature sensor, humidity sensor, motion sensor, weight sensor, LPR, ) LEDs, wearable devices, smart devices, etc.) are connected to the operating platform through middleware according to each device. At this time, the role of middleware due to the diversification and massification of equipment is becoming more important.

1 is a diagram illustrating an example of a conventional Internet Internet (IoT) infrastructure construction.

The IoT sensing device 1 and the RFID device 2 communicate with each other through communication with corresponding middleware servers 3, 4, 5 and 6 in the conventional Internet Internet (IoT) infrastructure shown in FIG. And receives the control from the middleware server or exchanges information with the corresponding middleware server.

1, the IoT sensing device 1 may be, for example, a barcode, a Bluetooth, a GPS, a temperature / humidity / motion / weight sensor, a car number and a camera recognition, a wearable device, and a smart device.

The RFID device 2 transmits and receives information in an electronic tag attached to an object using radio waves and provides related services, and there can be various kinds of RFID devices.

Each middleware server 3, 4, 5, 6 is connected to the IoT main system 7.

Each of the middleware servers 3, 4, 5 and 6 receives information from the corresponding IoT sensing device 1 or the RFID device 2 and transfers the information to the IoT main system 7.

On the other hand, an IoT sensing monitoring system 8 is connected to the IoT main system 7.

The IoT main system 7 sends the received information to the IoT sensing monitoring system 8.

Here, the middleware server may be an IoT middleware server (IoT sensing device server) 3, a mobile IoT middleware server 4, an RFID middleware server 5, and an RFID mobile middleware server 6.

As described above, in the conventional Internet Internet Protocol (IoT) infrastructure, the software developed for each middleware is used, which requires a large installation and management cost.

Prior Art 1: Korean Patent Laid-Open No. 10-2010-0073889 (Integrated Middleware Device of Wireless Identification System and Sensor Network) Prior Art 2: Korean Patent No. 10-1672868 (System and Method for Software Provisioning of Internet Devices) Prior Art 3: Korean Patent No. 10-1689593 (IoT based data collection system and data collection method using it) Prior Art 4: Korean Patent No. 10-0991714 (Sensor node management system and method in RFID / USN infrastructure and gateway system used therein) Prior art 5: Korean Patent Laid-Open No. 10-2016-0148911 (information integration system based on process data analysis and verification technology and HW-SW fusion framework by industry type)

SUMMARY OF THE INVENTION The present invention has been proposed in order to solve the problems of the related art, and it is an object of the present invention to provide a converged object Internet middleware system which unifies functions of various kinds of middleware and plays an excellent role in efficiency, cost reduction and optimization. have.

According to another aspect of the present invention, there is provided a converged-object Internet middleware system for managing connection between an IoT device and an RFID device, the information being recognized by the IoT device and the RFID device, An edge middleware section for transmitting the data to the terminal; A mobile middleware part for performing connection to the client, performing a corresponding DB operation based on an instruction for DB operation from the client, and transmitting the result to the client; And an integrated middleware unit for managing the IoT device and the RFID device connected to the edge middleware unit and the edge middleware unit and generating and outputting a report based on the values from the IoT device and the RFID device received through the edge middleware unit, .

The edge middleware unit and the integrated middleware unit can perform encryption and decryption in mutual data transmission and reception.

The mobile middleware unit and the client can perform encryption and decryption in mutual data transmission and reception.

The encryption and decryption can be performed by the AES algorithm.

The edge middleware portion may be configured as one or more than one.

Wherein the edge middleware unit comprises: an edge monitoring and managing unit for monitoring and managing the edge middleware unit itself; A device monitoring and management unit for performing status monitoring and management for the IoT device and the RFID device; An RFID device proxy unit for generating commands for controlling the RFID device and controlling the RFID device according to the generated command; An IoT device proxy unit for generating instructions for controlling the IoT device and controlling the IoT device according to the generated instruction; And an information security unit for applying encryption / decryption to the sensing value of the IoT device, the IoT device, and the control information of the RFID device.

Wherein the edge middleware unit comprises: a daemon unit waiting for connection with the integrated middleware unit; A basic filter unit for removing redundant data from data from the IoT device and the RFID device; And a log management unit for storing information from the IoT device and the RFID device as logs; And < / RTI >

Wherein the mobile middleware unit comprises: a communication security adapter unit for performing connection authentication for the client and for decrypting a report from the integrated middleware unit; A connection manager for performing connection management of the client; A DB management unit for performing a DB operation corresponding to the request of the client; And a customizing unit for identifying and customizing an abnormality in the report from the integrated middleware unit.

The communication security adapter unit may allow and deny access through the MAC address or the IP address of the client to be connected.

Wherein the mobile middleware comprises: a log management unit for storing the contents of the execution of the connection from the client to the end of the connection as a log file; And a control method and control method for the beacon are defined in an environment setting file and the beacon is controlled with the defined contents; And < / RTI >

The customized result of the customizing unit may be stored in the log management unit and used as data for controlling the beacon.

The integrated middleware unit may include an information security unit for encrypting / decrypting transmission / reception information for the IoT device and the RFID device; A system monitoring unit monitoring the state of the edge middleware, the IoT device connected to the edge middleware unit, the RFID device, and a client connected to the mobile middleware unit; An edge managing unit for managing the edge middleware unit, the IoT device and the RFID device, and an instruction for the IoT device and the RFID device; A filtering and reporting unit that performs filtering of the tag value of the RFID device, creates a report according to the result, and transmits the report to a notification URL (Notification URL) or the mobile middleware unit; And an IoT reporting unit for creating a report of the value recognized and transmitted by the IoT device and transmitting it to a notification URL (Notification URL) or the mobile middleware unit.

Wherein the integrated middleware unit comprises: a management channel for transmitting control commands for the IOT device and the RFID device to the edge middleware; And a notification channel for receiving data from the edge middleware unit.

The control command word may be encrypted and transmitted by the information security unit.

The data from the edge middleware unit is encrypted and can be decrypted by the information security unit.

The system monitoring unit may represent an abnormality of the IoT device and the RFID device in an alarm form.

The integrated middleware unit may further include a log management unit for processing a log of information transmitted and received by the integrated middleware unit.

According to the present invention having such a configuration, the configuration of a system that is connected to an operating system by applying a separate middleware to each existing device is unified by middleware for multiple devices based on RFID / USN standard technology, Real-time data processing for a device to be connected and application service linkage. And it can play an excellent role in efficiency, cost reduction, and optimization.

In other words, a plurality of tasks can be unified in each IoT sensing device SW and RFID middleware.

Conventional IoT sensing device SW and integrated RFID middleware are composed of JAVA and always operated as a dual system, but according to the present invention, they can be operated as a unified system by JAVA.

In addition, the initial construction cost of the IoT management system through the convergence type IoT middleware can be reduced.

When using various sensing devices used on the Internet, IoT SW can optimize the Internet service of objects and create a SMART Factory configuration environment.

1 is a diagram illustrating an example of a conventional Internet Internet (IoT) infrastructure construction.
FIG. 2 is a diagram schematically illustrating an example of the construction of a converged object Internet middleware system according to an embodiment of the present invention.
3 is a block diagram schematically illustrating a converged object Internet middleware system according to an embodiment of the present invention.
4 is a block diagram illustrating an internal configuration of a converged object Internet middleware system according to an embodiment of the present invention.
FIG. 5 is a flowchart illustrating a process for generating an IoT report in a converged-type Internet middleware system according to an embodiment of the present invention.
FIG. 6 is a flowchart illustrating a process for controlling an IoT device by mutual interaction between an edge middleware unit and an integrated middleware unit in a converged-type Internet middleware system according to an embodiment of the present invention.
FIG. 7 is a flowchart illustrating a process of generating an ALE report by mutual exchange between an edge middleware unit and an integrated middleware unit in a converged-type Internet middleware system according to an embodiment of the present invention.
FIG. 8 is a flowchart illustrating a data transmission process in a mobile middleware unit in a converged-type Internet middleware system according to an embodiment of the present invention.

While the invention is susceptible to various modifications and alternative forms, specific embodiments thereof are shown by way of example in the drawings and will herein be described in detail.

It should be understood, however, that the invention is not intended to be limited to the particular embodiments, but includes all modifications, equivalents, and alternatives falling within the spirit and scope of the invention.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. The singular expressions include plural expressions unless the context clearly dictates otherwise. In the present application, the terms "comprises" or "having" and the like are used to specify that there is a feature, a number, a step, an operation, an element, a component or a combination thereof described in the specification, But do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, or combinations thereof.

Unless defined otherwise, all terms used herein, including technical or scientific terms, have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs. Terms such as those defined in commonly used dictionaries should be interpreted as having a meaning consistent with the meaning in the context of the relevant art and are to be interpreted in an ideal or overly formal sense unless explicitly defined in the present application Do not.

Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the accompanying drawings. In order to facilitate the understanding of the present invention, the same reference numerals are used for the same constituent elements in the drawings and redundant explanations for the same constituent elements are omitted.

FIG. 2 is a diagram schematically illustrating an example of the construction of a converged object Internet middleware system according to an embodiment of the present invention.

2, a conventional IoT middleware server (IoT sensing device server) 3, a mobile IoT middleware server 4, an RFID middleware server 5, and an RFID mobile middleware server 6 are integrated into a single integrated Internet middleware system (100). ≪ / RTI >

2, the FOUNDATION Internet middleware system 100 of FIG. 2 can use an RFID, a barcode, and an IoT. And it can be used universally for smart factories and smart logistics. In addition, it can be applied as a management system by linking RFID and IoT SW to U-City business field.

In the conventional integrated RFID middleware, a separate program (I / O control program, IoT middleware) that can control the I / O (in / out) port was needed. In contrast, the converged Internet middleware system 100 of the present invention can be regarded as a fused IoT SW in which the function of the RFID middleware and the I / O port control (IoT sensing device SW) are integrated to solve this problem.

FIG. 3 is a block diagram schematically illustrating a converged object Internet middleware system according to an embodiment of the present invention, and FIG. 4 is a block diagram illustrating an internal configuration of a converged object Internet middleware system according to an embodiment of the present invention.

The integrated object Internet middleware system 100 includes an edge middleware unit 10, a mobile middleware unit 30, and an integrated middleware unit 50.

The edge middleware 10 is responsible for connection to the IoT device (sensor) and the RFID device (reader). The reader 19 shown in FIG. 4 is a representative of an RFID device (equipment) and can be regarded as various types of RFID readers. The sensor 20 shown in FIG. 4 is referred to as an IoT device, and may be considered to include various kinds of IoT sensors.

The edge middleware unit 10 transmits information recognized by the IoT device (sensor) and / or the RFID device (reader) to the integrated middleware unit 50.

In other words, the edge middleware unit 10 is connected to the reader 19, and recognizes an electronic tag (for example, an RFID tag), performs basic filtering, and then extracts the RFID tag value. The edge middleware unit 10 can transmit the extracted RFID tag value to the integrated middleware unit 50. [

Also, the edge middleware unit 10 is connected to the sensor 20, and can receive a value by requesting the sensor 20 at a defined time. The edge middleware unit 10 can transmit the received sensing value to the integrated middleware unit 50. [

Although only one edge middleware section 10 is shown in FIGS. 3 and 4, multiple edge middleware sections can be operated as needed.

The mobile middleware 30 is responsible for connection to the client 70 such as a PDA, a smart phone, a computer (PC), a notebook computer, and the like.

The mobile middleware unit 30 can perform a DB operation related to inventory management and material management of an operator using the client 70 and deliver the result to the client 70. [

The integration middleware 50 provides an administrator's home page and is connected to one or more edge middleware units 10 to collect information from the edge middleware unit 10 and outputs the information to a legacy system Lt; / RTI >

In other words, the integrated middleware unit 50 can manage one or more edge middleware units 10. The integrated middleware unit 50 can monitor and manage both the reader 19 and the sensor 20 connected to each edge middleware unit 10. [ The integrated middleware unit 50 configures an administrator screen so that the administrator can easily manage the web screen through the client 80. [ The integrated middleware unit 50 configures the tag value received through the edge middleware unit 10 as an ALE report and configures the sensing value received through the edge middleware unit 10 as an IoT report and transmits the tag value to the legacy system Lt; / RTI > Here, the client 80 may be, for example, a PDA, a smart phone, a computer (PC), a notebook computer, or the like.

The integrated middleware unit 50 can control the user connected to the mobile middleware unit 30. [

4, the edge middleware unit 10 includes an edge monitoring and management unit 11, a device monitoring and management unit 12, a daemon unit 13, a basic filter unit 14, a log management unit 15 ), An RFID device proxy unit 16, an IoT device proxy unit 17, and an information security unit 18.

The edge monitoring and management unit 11 monitors and manages the edge middleware unit 10 itself. At this time, the edge monitoring and management unit 11 can send a predetermined command to the integrated middleware unit 50 through the management channel 51 of the integrated middleware unit 50. The edge monitoring and management unit 11 may send predetermined data to the integrated middleware unit 50 through the notification channel 52 of the integrated middleware unit 50. [

The device monitoring and management unit 12 performs status monitoring and management for the devices managed by the edge middleware unit 10 (i.e., the reader 19 and the sensor 20). At this time, the device monitoring and management unit 12 can send a predetermined command to the integrated middleware unit 50 through the management channel 51 of the integrated middleware unit 50. Meanwhile, the device monitoring and management unit 12 can send predetermined data to the integrated middleware unit 50 through the notification channel 52 of the integrated middleware unit 50.

The daemon unit 13 performs an operation of the edge middleware unit 10 and waits for a connection with the integrated middleware unit 50. [ In the case of the daemon unit 13, an administrator page is not provided.

The basic filter unit 14 can remove redundant data from the data from the reader 19 and / or the sensor 20. [

The basic filter unit 14 may be composed of, for example, a smoothing filter, and may be set differently depending on the characteristics of the device (the reader 19 and the sensor 20).

The log management unit 15 can store all the information from the devices (i.e., the reader 19 and the sensor 20) connected to the edge middleware unit 10 as a log (which may be referred to as a log file). The log at this time contains the connection status of the corresponding device, the recognized information, and the transmission information to the integrated middleware unit 50.

Here, the daemon unit 13, the basic filter unit 14, and the log management unit 15 may be integrated into one module.

The RFID device proxy unit 16 generates basic commands for controlling the RFID device (i.e., the reader 19) and controls the reader 19 by the generated command. Here, the control may be a connection with the reader 19, an operation interruption of the reader 19, an operation start of the reader 19, and the like.

The IoT device proxy unit 17 generates basic instructions for controlling the IoT device (i.e., the sensor 20), and controls the sensor 20 by the generated instructions. Here, the control may be a connection with the sensor 20, a reading of a value recorded in an object to be sensed, and the like.

The information security unit 18 applies encryption / decryption to data requiring security such as the sensing value of the sensor 20, the reader 19, and the sensor 20. For example, the information security unit 18 may encrypt the sensing value of the sensor 20 to be transmitted to the integrated middleware unit 50 through the AES algorithm. The information security unit 18 can decrypt the control information (encrypted) of the reader 19 and the sensor 20 received from the integrated middleware unit 50 through the AES algorithm.

Here, the RFID device proxy unit 16, the IoT device proxy unit 17, and the information security unit 18 may be integrated into one module. One module at this time may be referred to as a device proxy.

4, the mobile middleware unit 30 includes a communication security adapter unit 31, a connection management unit 32, a DB management unit 33, a log management unit 34, a customizing unit 35, A warning light management unit 36, and an RMS linkage management unit 37. [

The communication security adapter unit 31 performs connection authentication for the client 70. [ That is, since the client 70 connects to the mobile middleware 30 and performs work on the DB, the communication security adapter unit 31 performs connection authentication for the client 70 through a predetermined connection procedure . At this time, the communication security adapter unit 31 can allow and deny access through the MAC address or IP address of the client 70 to be connected. When the integrated middleware unit 50 transmits the ALE report (for example, the encrypted XML data) to the mobile middleware unit 30 via TCP / IP or function call, the communication security adapter unit 31 transmits the corresponding data , Encrypted XML data).

The connection management unit 32 performs connection management of the client 70, which is a mobile equipment. In addition, the connection management unit 32 can terminate the connection if there is no work for a certain period of time after connection.

Here, the communication security adapter unit 31 and the connection management unit 32 may be integrated into one module. One module at this time can be referred to as a connection part.

The DB management unit 33 accesses the DBMS (Oracle, MS-SQL, MySQL, Tibero) according to the setting contents of the environment setting file for driving the mobile middleware unit 30 for each user's request and performs the request. The DB management unit 33 terminates the DBMS connection when the user's request is completed.

The log management unit 34 stores the contents of all the operations performed from the connection of the client 70 to the end of the connection in a log file.

The log management unit 34 may set the number of log files and store the log files by rotation.

The customizing unit 35 can confirm the abnormality of the ALE report from the integration middleware unit 50 and customize (modify) the ALE report.

The result customized by the customizing unit 35 is not only stored in the log managing unit 34 but also can be used as data for controlling the beacon light 90. [

The warning light management unit 36 defines a control method and a control method for the warning light 90 in an environment setting file and controls the warning light 90 with the defined contents.

The beacon management unit 36 can be connected to the beacon 90 with TCP / IP.

Here, the DB management unit 33, the log management unit 34, the customizing unit 35, and the warning light management unit 36 may be integrated into one module. One module at this time may be referred to as a processing unit.

The RMS association manager 37 accesses the RMS (Record Management System) 92 to perform data transmission and reception. The RMS 92 refers to a system in which a national registrar is defined as a standard.

The RMS association manager 37 may be connected to the RMS 92 via TCP / IP.

4, the integrated middleware unit 50 includes a management channel 51, a notification channel 52, an information security unit 53, a web browser 54, a log management unit 55, A monitoring unit 56, an apparatus and edge management unit 57, an ALE interface unit 58, a filtering and reporting unit 59, and an IoT reporting unit 60.

The management channel 51 is a channel for transmitting management commands to the devices (the reader 19, the sensor 20) of the edge middleware unit 10. [

The notification channel 52 is a channel for receiving data such as device identification information in the edge middleware unit 10. [

The information security section 53 encrypts / decrypts the transmission / reception information for the devices (the reader 19, the sensor 20) via the management channel 51 and the notification channel 52.

The management channel 51, the notification channel 52 and the information security unit 53 are internal protocols for data transmission and reception between the edge middleware unit 10 and the integrated middleware unit 50.

The web browser 54 provides an integrated management page that allows an administrator to manage the middleware units 10, 30, and 50.

For example, the web browser 54 may add / delete / modify the edge middleware unit 10 and add / delete / modify the devices (reader 19, sensor 20) It is possible to provide an integrated management function for the middleware units 10, 30, and 50 such as user disconnection and restart.

The log management unit 55 processes a log (referred to as a log file) of information transmitted and received by the integration middleware unit 50.

The system monitoring unit 56 includes all the edge middleware units 10 that can be managed by the integration middleware unit 50, the devices (the reader 19 and the sensor 20) connected to the edge middleware unit 10, And monitors the status of the client 70 and the like connected to the middleware unit 30. [

Then, the system monitoring unit 56 can express the abnormality of the device (reader 19, sensor 20) in the form of an alarm.

The device and edge management unit 57 manages (adds / modifies / deletes) the registered edge middleware unit 10 and the devices (the reader 19 and the sensor 20) )).

Here, the log management unit 55, the system monitoring unit 56, the device and the edge management unit 57 may be integrated into one module. One module at this time may be referred to as a system monitoring and management section.

The ALE interface unit 58 can transmit the message exchange via SOAP and the ECReport via the Notification URL. At this time, the ALE interface unit 58 can define the definition of the message exchange, the contents of the report, and the transmission period.

The filtering and reporting unit 59 performs filtering of the RFID tag values according to the set values defined through the ALE interface unit 58, creates an ALE report according to the result, and transmits the ALE report to the notification URL (Notification URL) .

On the other hand, when the ALE report is transmitted to the mobile middleware unit 30 instead of the Notification URL, the filtering and reporting unit 59 may transmit the ALE report using an internal function, not a URL, in order to reduce the communication load.

The IoT reporting unit 60 can generate the IoT report by recognizing the transferred value from the IoT device (i.e., the sensor 20), and transmit the created value to the Notification URL.

On the other hand, when the IoT report is transmitted to the mobile middleware unit 30 instead of the Notification URL, the IoT reporting unit 60 can transmit using an internal function, not a URL, in order to reduce the communication load.

Here, the ALE interface unit 58, the filtering and reporting unit 59, and the IoT reporting unit 60 may be integrated into one module. One module at this time may be referred to as a report service section.

As described above, the converged object Internet middleware system 100 can perform encryption on the value of the sensor 20 and the control information of the IoT device (i.e., the sensor 20). Also, in the converged object Internet middleware system 100, the edge middleware unit 10 and the integrated middleware unit 50 can perform encryption / decryption in mutual data transmission. Also, in the converged object Internet middleware system 100, the mobile middleware unit 30 and the client 70 can perform encryption / decryption in mutual data transmission / reception.

Since the converged object Internet middleware system 100 is operated as a unified system by using JAVA, in order to make it easy to use in Java, the encryption uses the AES algorithm (for example, AES128, AES256) .

FIG. 5 is a flowchart illustrating a process for generating an IoT report in a converged-type Internet middleware system according to an embodiment of the present invention.

First, the administrator accesses the web browser 54 of the integrated middleware unit 50 through the client 80 and registers the IoT edge in the web browser 54 (S10). Here, registering the IoT edge means registering a new edge middleware unit 10. When the new edge middleware unit 10 is registered, the ID, IP, monitoring monitoring period, and device status monitoring period of the corresponding edge middleware unit can be registered as registration values. The edge middleware unit 10 to be registered may be one or more.

Then, the manager registers the registered IoT device (i.e., sensor 20; IoT sensor) of the registered edge middleware 10 in the web browser 54 (S12). Here, when registering the IoT device, the ID of the edge middleware unit to which the IoT device is connected, the ID and name of the IoT device, the proxy, the IP, the port, and the recognition period can be registered as registration values. And, the registered IoT device (i.e., the sensor 20) may be one or more.

Thereafter, when the recognition period of the sensor 20 arrives, the edge middleware unit 10 sends a command requesting the sensing value to the sensor 20 (S14). At this time, the command requiring the sensing value is preferably encrypted by the AES algorithm for security.

The edge middleware unit 10 receives the data including the sensing value from the sensor 20 that received the command requesting the sensing value (S16). The data at this time is preferably encrypted by the AES algorithm for security.

The edge middleware unit 10 stores the received data as a log (also referred to as a log file) (S18). At this time, the edge middleware unit 10 decodes the received data and stores it as a log. For example, the ID of the edge middleware unit to which the sensor 20 is connected, the ID, IP, time and sensing value of the sensor 20, and the like can be stored as a log.

The edge middleware unit 10 encrypts the decrypted data and transmits the decrypted data to the integrated middleware unit 50 through the notification channel 52 of the integrated middleware unit 50 at step S20. Here, it is necessary for security to encrypt the decrypted data.

Accordingly, the integration middleware unit 50 receives the encrypted data through the notification channel 52 (S22).

Then, the integrated middleware unit 50 decrypts the received encrypted data and stores the decrypted data as a log (S24). For example, the ID of the edge middleware unit to which the sensor 20 is connected, the ID, IP, time and sensing value of the sensor 20, and the like can be stored as a log.

Then, the IoT reporting unit 60 of the integrated middleware unit 50 generates an IoT report, for example, an IoT report in the form of an XML document (S26). Here, the generated IoT report includes the ID of the edge middleware unit to which the sensor 20 is connected, the ID, IP, time and sensing value of the sensor 20, and the like.

Then, the IoT reporting unit 60 of the integrated middleware unit 50 transfers the generated IoT report (e.g., XML document type) to the Notification URL (S28). Here, it is preferable that the IoT report is transmitted after being encrypted by the AES algorithm for security.

Then, the IoT report in the integration middleware unit 50 will be transmitted to the mobile middleware unit 30 by the internal function call.

The mobile middleware unit 30 receives and customizes the IoT report (S30). That is, the mobile middleware unit 30 confirms whether there is an abnormality after XML decoding the received IoT report.

Then, when confirmation is completed, the mobile middleware unit 30 stores and manages the corresponding data (e.g., abnormality check, time, contents of the check result, etc.) as a log (S32).

Further, the mobile middleware section 30 manages (controls) the beacon light 90 based on the customized result (S34). At this time, the mobile middleware unit 30 is controllable by sending a beacon control command to the beacon light 90. [

FIG. 6 is a flowchart illustrating a process of controlling an IoT device by mutual exchange between an edge middleware unit and an integrated middleware unit in a converged-object Internet middleware system according to an embodiment of the present invention.

First, a user (which may be an administrator) accesses the web browser 54 of the integrated middleware unit 50 through a client 80 such as a smart phone (S50). The user inputs user information (e.g., ID, password, and telephone number of the corresponding user), and the integrated middleware unit 50 performs user authentication based on the received user information.

If the user is an authenticated user, the web browser 54 of the integration middleware unit 50 receives the IoT device control request (including the control type) from the user (S52).

Accordingly, the integrated middleware unit 50 stores the data corresponding to the received IoT device control request as a log (S54). At this time, the stored data may be the ID of the edge middleware unit to which the corresponding IoT device (i.e., the sensor 20) is connected, the user information, the ID, IP, time and control type of the IoT device.

The integrated middleware unit 50 transmits the control command to the edge middleware unit 10 connected to the corresponding IoT device (i.e., the sensor 20) through the management channel 51 (S56). Here, the control command contains contents corresponding to the control command for the IoT device (i.e., the sensor 20) requested by the authenticated user. The integrated middleware unit 50 transmits the control command to the edge middleware unit 10 through the management channel 51. For security, the integrated middleware unit 50 encrypts and transmits the control command word through the AES algorithm.

Thereafter, the edge middleware 10 decodes the received control command (encrypted) and controls the IoT device (i.e., the sensor 20) according to the decoded result (S58).

The edge middleware unit 10 stores the control result of the corresponding IoT device (i.e., the sensor 20) as a log and sends the control result to the web via the notification channel 52 of the integrated middleware unit 50. [ To the client 80 via the browser 54 (S60). Here, the control result will be encrypted through the AES algorithm for security and transferred to the integrated middleware unit 50, and the integrated middleware unit 50 will decrypt the encrypted control result and transmit the decrypted control result to the client 80.

FIG. 7 is a flowchart illustrating a process of generating an ALE report by mutual exchange between an edge middleware unit and an integrated middleware unit in a converged-type Internet middleware system according to an embodiment of the present invention.

First, the manager accesses the web browser 54 of the integrated middleware unit 50 through the client 80 and registers the new edge middleware unit 10 in the web browser 54 (S70). When the new edge middleware unit 10 is registered, the ID, IP, monitoring monitoring period, and device status monitoring period of the corresponding edge middleware unit can be registered as registration values. The edge middleware unit 10 to be registered may be one or more.

Then, the manager registers the reader 19 (i.e., the RFID reader) of the registered edge middleware unit 10 in the web browser 54 (S72). Here, when registering the reader 19, the ID of the edge middleware unit to which the reader is connected, the ID and name of the reader, the proxy, the IP, the port, and the recognition period can be registered as registration values. The registered reader 19 may be one or more.

Then, when the recognition period of the reader 19 arrives, the edge middleware unit 10 requests recognition data from the reader 19 (S74). At this time, the request of the recognition data is in the form of a command, and the command requesting the recognition data is preferably encrypted by the AES algorithm for security. If necessary, encryption may be omitted.

The edge middleware unit 10 receives data including the tag value (i.e., the RFID tag value) from the reader 19 (S76). The data at this time is preferably encrypted by the AES algorithm for security.

The edge middleware unit 10 stores the received data as a log (S78). At this time, the edge middleware unit 10 decodes the received data and stores it as a log. For example, the ID of the edge middleware unit to which the reader 19 is connected, the ID and IP of the reader 19, the time and the tag value, and the like can be stored as a log.

The edge middleware unit 10 encrypts the decrypted data and transmits the decrypted data to the integrated middleware unit 50 through the notification channel 52 of the integrated middleware unit 50 at step S80. Here, it is necessary for security to encrypt the decrypted data.

Accordingly, the integrated middleware unit 50 receives the encrypted data through the notification channel 52 (S82).

Then, the integrated middleware unit 50 decrypts the received encrypted data and stores the decrypted data as a log (S84). For example, the ID of the edge middleware unit to which the reader 19 is connected, the ID and IP of the reader 19, the time and the tag value, and the like can be stored as a log.

Then, the ALE reporting unit 58 of the integrated middleware unit 50 generates an ALE report, for example, an ALE report in the form of an XML document (S86). Here, the generated ALE report includes the ID of the edge middleware unit to which the reader 19 is connected, the ID and IP of the reader 19, and the time and tag value.

Then, the ALE reporting unit 58 of the integrated middleware unit 50 transfers the generated ALE report (for example, XML document type) to the Notification URL (S88). Here, it is preferable that the ALE report is transmitted after being encrypted by the AES algorithm for security.

Thereafter, the ALE report in the integration middleware unit 50 will be transmitted to the mobile middleware unit 30 by the internal function call.

The mobile middleware unit 30 receives and customizes the ALE report (S90). That is, the mobile middleware unit 30 confirms whether there is an abnormality after XML decoding the received ALE report.

Then, when the confirmation is completed, the mobile middleware unit 30 stores and manages the corresponding data (e.g., abnormality confirmation, time, contents of the confirmation result, etc.) as a log (S92).

Further, the mobile middleware section 30 manages (controls) the beacon 90 based on the customized result (S94). At this time, the mobile middleware unit 30 is controllable by sending a beacon control command to the beacon light 90. [

FIG. 8 is a flowchart illustrating a data transmission process in a mobile middleware unit in a converged-type Internet middleware system according to an embodiment of the present invention.

First, a user who wishes to perform a DB operation accesses a mobile middleware unit 30 through a client 70 such as a PDA, a smart phone, or a notebook computer (S100). At this time, the mobile middleware unit 30 can grasp the IP address, the MAC address, and the time of the connected client 70.

Accordingly, the mobile middleware unit 30 performs authentication for the connected user (i.e., user) (S110). For example, since the client 70 and the mobile middleware unit 30 use a private communication protocol, the mobile middleware unit 30 can confirm whether the client 70 and the mobile middleware unit 30 are authorized devices by using the IP address or the MAC address of the corresponding client 70.

When the connection is authenticated ("Yes" in S110), the mobile middleware unit 30 performs the DB operation in the client 70. [ That is, when the connection is authenticated, the client 70 will input a command for the desired DB operation.

Accordingly, the mobile middleware unit 30 performs a DB operation according to a command for the received DB operation, converts the result into a data, and transmits the data to the client 70 (S120). At this time, the result of DB operation will be encrypted and transmitted through AES algorithm for security.

Thereafter, the client 70 decodes the received data by using the AES algorithm and displays it, so that the user can check the result of the DB operation.

As described above, an optimal embodiment has been disclosed in the drawings and specification. While specific terms have been employed herein, they are used for the purpose of describing the invention only and are not used to limit the scope of the invention as defined in the claims or the claims. Therefore, those skilled in the art will appreciate that various modifications and equivalent embodiments are possible without departing from the scope of the present invention. Accordingly, the true scope of the present invention should be determined by the technical idea of the appended claims.

10: Edge middleware department
30: Mobile middleware department
50: Integrated middleware department
70, 80: Client
100: Fusion type Internet middleware system

Claims (18)

An edge middleware unit which is connected to the IoT device and the RFID device and transmits the information recognized by the IoT device and the RFID device to the integrated middleware;
A mobile middleware part for performing connection to the client, performing a corresponding DB operation based on an instruction for DB operation from the client, and transmitting the result to the client; And
An integrated middleware unit for managing the IoT device and the RFID device connected to the edge middleware unit and the edge middleware unit and generating and outputting a report based on the values from the IoT device and the RFID device received through the edge middleware unit; And the Internet middleware system. The method according to claim 1,
Wherein the edge middleware unit and the integrated middleware unit perform encryption and decryption in mutual data transmission and reception. The method of claim 2,
Wherein the encryption and decryption are performed using an AES algorithm. The method according to claim 1,
Wherein the mobile middleware unit and the client perform encryption and decryption in mutual data transmission and reception. The method of claim 4,
Wherein the encryption and decryption are performed using an AES algorithm. The method according to claim 1,
Wherein the edge middleware unit comprises at least one edge middleware unit. The method according to claim 1,
The edge middleware unit,
An edge monitoring and managing unit for monitoring and managing the edge middleware itself;
A device monitoring and management unit for performing status monitoring and management for the IoT device and the RFID device;
An RFID device proxy unit for generating commands for controlling the RFID device and controlling the RFID device according to the generated command;
An IoT device proxy unit for generating instructions for controlling the IoT device and controlling the IoT device according to the generated instruction; And
And an information security unit for applying encryption / decryption to the IoT device's sensing value, the IoT device, and the control information of the RFID device. The method of claim 7,
The edge middleware unit,
A daemon unit waiting for connection with the integrated middleware unit;
A basic filter unit for removing redundant data from data from the IoT device and the RFID device; And
A log management unit for storing information from the IoT device and the RFID device in a log; Wherein the Internet middleware system further includes at least one of the Internet middleware system and the Internet middleware system. The method according to claim 1,
The mobile middleware unit,
A communication security adapter unit for performing connection authentication for the client and for decrypting a report from the integrated middleware unit;
A connection manager for performing connection management of the client;
A DB management unit for performing a DB operation corresponding to the request of the client; And
And a customizing unit for checking whether the report is abnormal from the integrated middleware unit and customizing the report. The method of claim 9,
The communication security adapter unit,
And permits or denies the connection through the MAC address or IP address of the client to be connected. The method of claim 9,
The mobile middleware unit,
A log management unit for storing the content of the execution of the connection from the client to the end of the connection as a log file; And
A beacon management unit for defining a control method and a control method for the beacon in an environment setting file and controlling the beacon with the defined content; Wherein the Internet middleware system further includes at least one of the Internet middleware system and the Internet middleware system. The method of claim 11,
Wherein the customized result of the customizing unit is stored in the log management unit and used as data for controlling the beacon light. The method according to claim 1,
The integrated middleware unit,
An information security unit for encrypting / decrypting transmission / reception information for the IoT device and the RFID device;
A system monitoring unit monitoring the state of the edge middleware, the IoT device connected to the edge middleware unit, the RFID device, and a client connected to the mobile middleware unit;
An edge managing unit for managing the edge middleware unit, the IoT device and the RFID device, and an instruction for the IoT device and the RFID device;
A filtering and reporting unit that performs filtering of the tag value of the RFID device, creates a report according to the result, and transmits the report to a notification URL (Notification URL) or the mobile middleware unit; And
And an IoT reporting unit configured to generate a report of the value recognized and transmitted by the IoT device and transmit the report to a notification URL or the mobile middleware unit. 14. The method of claim 13,
The integrated middleware unit,
A management channel for transmitting control commands for the IOT device and the RFID device to the edge middleware; And
And a notification channel for receiving data from the edge middleware unit. 15. The method of claim 14,
Wherein the control command is encrypted and transmitted by the information security unit. 15. The method of claim 14,
Wherein the data from the edge middleware unit is encrypted and decrypted by the information security unit. 14. The method of claim 13,
The system monitoring unit,
Wherein the abnormality of the IoT device and the RFID device is expressed in an alarm form. 14. The method of claim 13,
The integrated middleware unit,
And a log management unit for processing a log of information transmitted and received by the integrated middleware unit.

Images