TWI875017B - Internet of things system - Google Patents

Abstract

An Internet of Things (IoT) system includes a plurality of terminal devices, a cloud device and a human machine interface (HMI) device. The cloud device is communicatively connected to the terminal devices. The human machine interface (HMI) device is communicatively connected to the terminal devices via a plurality of first communication channels, and communicatively connected to the cloud device via a first dedicated communication channel. The HMI device determines a subscription sequence according to priority information of a plurality of control commands, and schedules and dynamically subscribes to the first communication channels according to the subscription sequence. The HMI device respectively determines whether the terminal devices are adjacent to the HMI device, and transmits switch transmission mode request messages corresponding to the terminal devices adjacent to the HMI device to the cloud device via the first dedicated communication channel.

Description

Internet of Things System

The present invention relates to a communication architecture, and more particularly to an Internet of Things system.

The architecture of a traditional IoT system can be built based on the Message Queuing Telemetry Transport (MQTT) communication protocol. The terminal devices of a traditional IoT system establish a connection with a cloud server through a channel with a Universally Unique Identifier (UUID). In this regard, the terminal devices transmit and receive data through this channel, and the human-machine interface device also controls the terminal devices through this channel. However, when the number of terminal devices increases and exceeds the limit on the number of subscribed channels, the traditional IoT system will have the problem of being unable to simultaneously and efficiently manage or control a large number of terminal devices, and may even cause the computing load of the human-machine interface device to exceed the burden, causing security concerns on the user side. Therefore, how to efficiently manage or control a large number of terminal devices with a limited number of subscription channels is one of the important research directions in the field of Internet of Things.

The IoT system of the present invention includes multiple terminal devices, cloud devices and human-machine interface devices. The cloud device is connected to the terminal device in a communication manner. The human-machine interface device is connected to the cloud device in a communication manner via multiple first communication channels, and is suitable for determining the subscription order according to the priority information of multiple control commands. The human-machine interface device schedules and dynamically subscribes to the first communication channel according to the subscription order, so as to transmit the control command to the cloud device through different first communication channels according to the subscription order, so that the cloud device transmits the control command to the corresponding terminal device.

The IoT system of the present invention includes multiple terminal devices, cloud devices and human-machine interface devices. The cloud device is connected to the terminal device in a communication manner. The human-machine interface (HMI) device is connected to the terminal device in a communication manner via multiple first communication channels, and is connected to the cloud device in a communication manner via a first dedicated communication channel. The HMI device determines the subscription order based on the priority information of multiple control commands, and schedules and dynamically subscribes to the first communication channel based on the subscription order. The HMI device determines whether the terminal device is adjacent to the HMI device, and transmits a switching transmission mode request message corresponding to the terminal device adjacent to the HMI device to the cloud device via the first dedicated communication channel.

Based on the above, the IoT system of the present invention efficiently schedules and dynamically subscribes to multiple first communication channels to transmit multiple control commands to the cloud device by determining the priority order of the control commands. The cloud device transmits the control commands to multiple corresponding terminal devices. Therefore, the IoT system of the present invention effectively controls a large number of terminal devices. In addition, the HMI device of the IoT system of the present invention can be switched to a regional transmission mode to manage and control the terminal devices adjacent to the HMI device with lower latency and low power consumption.

In order to provide a further understanding of the above features and advantages of the present invention, embodiments will be described in detail below with reference to the accompanying drawings.

In order to make the content of the present invention more clearly understood, the following embodiments are specifically cited as examples that the present disclosure can be implemented. In addition, wherever possible, the elements/components/steps with the same reference numerals in the drawings and embodiments represent the same or similar components.

FIG. 1 is a schematic diagram of an Internet of Things system of an embodiment of the present invention. Referring to FIG. 1 , the Internet of Things (IoT) system 100 includes a human-machine interface device 110, a cloud device 120, and a plurality of terminal devices 130_1 to 130_N, where N is a positive integer. In this embodiment, the cloud device 120 can be communicatively connected to the plurality of terminal devices 130_1 to 130_N. The human-machine interface device (HMI) 110 can establish a plurality of first communication channels to communicate with the cloud device 120. The cloud device 120 can establish a plurality of second communication channels to communicate with the plurality of terminal devices 130_1 to 130_N. The number of first communication channels is limited, and the number of second communication channels can be greater than or equal to the number of first communication channels. It is worth noting that the number of terminal devices 130_1~130_N is greater than the number of multiple first communication channels. The human-machine interface device 110 can also establish a first dedicated communication channel to communicate with the cloud device 120, and the cloud device 120 can establish one or more second dedicated communication channels to communicate with multiple terminal devices 130_1~130_N.

In addition, in one embodiment, the IoT system 100 may be applied to a home energy management system (HEMS) and manage multiple terminal devices 130_1~130_N, wherein the multiple terminal devices 130_1~130_N may include, for example, solar devices, home appliances, and related mains devices corresponding to one or more users' homes, and other IoT devices. However, the application of the IoT system 100 of this embodiment is not limited to the home energy management system.

In this embodiment, the human-machine interface device 110 may be a display device that can provide user monitoring and control functions, and can install corresponding applications (apps) or can execute corresponding web programs, such as smart phones, tablet computers, and laptops, but the present invention is not limited thereto. In this embodiment, the human-machine interface device 110 can determine a subscription order according to the priority information of the multiple control commands, and can schedule and dynamically subscribe to multiple first communication channels according to the subscription order, so as to transmit multiple control commands to the cloud device 120 through different first communication channels according to the subscription order, so that the cloud device 120 can transmit the multiple control commands to multiple corresponding terminal devices 130_1~130_N through different second communication channels. In addition, the terminal devices 130_1~130_N can respectively return multiple corresponding IoT messages to the cloud device 120 through different second communication channels, so that the cloud device 120 can transmit multiple corresponding IoT messages to the human-machine interface device 110. In this way, the human-machine interface device 110 can effectively control and monitor the terminal devices 130_1 to 130_N. In addition, the multiple IoT messages of this embodiment can include, for example, at least one of device status information, sensing data, and reply commands.

FIG. 2 is a schematic diagram of an Internet of Things system of another embodiment of the present invention. Referring to FIG. 2 , the Internet of Things system 200 includes a human-machine interface device 210, a cloud device 220, and a terminal device 230. This embodiment is illustrated by taking a terminal device 230 as an example, and each of the terminal devices 130_1 to 130_N of FIG. 1 is respectively implemented as the terminal device 230 of FIG. 2 . In this embodiment, the human-machine interface device 210 may include a transmission module 211, a channel management module 212, a data management module 213, and an application function module 214. In this embodiment, the cloud device 220 may include a transmission module 221, a terminal device management module 222, a storage module 223, and a human-machine interface device management module 224. The terminal device 230 may include a transmission module 231 and an application function module 232. In this embodiment, the human-machine interface device 210, the cloud device 220 and the terminal device 230 may include processors and memories corresponding to their respective device specifications, and their respective memories may be used to store the above-mentioned multiple modules for their respective processors to access and execute their related functions. In this regard, the above-mentioned modules may be implemented in the form of software or firmware with hardware circuits, and their respective processors may execute corresponding algorithms to implement their related functions.

In this embodiment, the transmission modules 211, 221, and 231 can be implemented based on the Message Queuing Telemetry Transport (MQTT) communication protocol, and can include a wired or wireless transmission interface to implement communication connection and message transmission and reception between the human-machine interface device 210, the cloud device 220, and the terminal device 230. The transmission module 211 of the human-machine interface device 210 can be communicatively connected to the transmission module 221 of the cloud device 220, and can transmit and receive messages based on the Message Queuing Telemetry Transport communication protocol. The transmission module 221 of the cloud device 220 can be communicatively connected to the transmission module 231 of the terminal device 230, and can transmit and receive messages based on the message queue telemetry transmission protocol.

In this embodiment, the channel management module 212 of the human-machine interface device 210 can schedule and allocate subscriptions to multiple first communication channels corresponding to different terminal devices in a limited number of channels to transmit different control commands. In this embodiment, the data management module 213 of the human-machine interface device 210 can also use a first dedicated communication channel to receive the aggregated information of multiple terminal devices transmitted by the cloud device 220, and can send a delegated control command. In this embodiment, the cloud device 220 can aggregate multiple IoT messages of at least a portion of the multiple terminal devices to generate an aggregated message. In this embodiment, the application function module 214 of the human-machine interface device 210 can display a user interface with an operation screen and related functions on the display screen of the human-machine interface device 210 , so that the user can control and monitor multiple terminal devices through the human-machine interface device 210 .

In this embodiment, the terminal device management module 222 of the cloud device 220 can classify the control commands provided by the human-machine interface device 210 and the multiple IoT messages returned by the multiple terminal devices 230, and can also explore the first exclusive communication channel between the human-machine interface device 210 and the second exclusive communication channel between the multiple terminal devices, and can perform message push operations. In this embodiment, the storage module 223 of the cloud device 220 can, for example, use a binary tree data structure technology to store multiple connection messages and multiple IoT messages of multiple terminal devices, and can also temporarily store the control commands provided by the human-machine interface device 210. In this embodiment, the human-machine interface device management module 224 of the cloud device 220 can manage the connection status of multiple terminal devices and the schedule of related message push.

In this embodiment, the application function module 232 of the terminal device 230 can realize a specific application function (such as a sensing function of a certain sensor), and can generate an IoT message corresponding to the specific application function, and send it to the cloud device 220 via the corresponding second communication channel or the corresponding second dedicated communication channel. The application function module 232 of the terminal device 230 can also receive the corresponding control command and the delegated control command from the cloud device 220 via the corresponding second communication channel or the corresponding second dedicated communication channel to perform the corresponding operation according to the control command or the delegated control command. In addition, the implementation of each of the aforementioned modules will be described in detail by the exemplary embodiments of the operation schematic diagrams of Figures 3 to 8 below.

FIG3 is an operation diagram of a management terminal device of an embodiment of the present invention. The Internet of Things system 300 includes a human-machine interface device 310, a cloud device 320, and a terminal device 330. In this embodiment, the channel management module 312 of the human-machine interface device 310 may include a channel scheduling unit 312_1 and a channel allocation unit 312_2. The channel scheduling unit 312_1 may calculate a subscription order based on priority information of a plurality of control commands. The channel allocation unit 312_2 may allocate a plurality of first communication channels according to the subscription order for transmitting a plurality of control commands to be subscribed in sequence. In this embodiment, the data management module 313 of the human-machine interface device 310 may include a message application unit 313_1 and a control delegation unit 313_2. The message application unit 313_1 can receive the aggregated message sent by the cloud device 320 via the first dedicated communication channel, and can classify the aggregated message. The cloud device 320 can aggregate multiple IoT messages of at least a part of multiple terminal devices 330 to generate the aggregated message. In this embodiment, when all the first communication channels are occupied, the data management module 313 can transfer at least one control command with a higher priority to the control delegation unit 313_2 to transmit the corresponding delegated control command to the cloud device 320 via the first dedicated communication channel. In this embodiment, the application function module 314 of the human-machine interface device 310 can generate control commands and receive classified aggregated information provided by the message application unit 313_1.

In this embodiment, the terminal device management module 322 of the cloud device 320 may include a message classification unit 322_1, a message monitoring unit 322_2, and a device control unit 322_3. The message classification unit 322_1 may classify and store multiple device connection information and multiple IoT messages received by the transmission module 321 into the device data unit 323_1 and the device connection unit 323_2 of the storage module 323. The message monitoring unit 322_2 may monitor the device data unit 323_1 to determine whether at least one of the multiple terminal devices has not returned the IoT message. The device control unit 322_3 may explore multiple terminal devices to establish a connection with at least one corresponding terminal device.

In this embodiment, the storage module 323 of the cloud device 320 may include a device data unit 323_1, a device connection unit 323_2, and a message buffer unit 323_3. The device data unit 323_1 may store control instructions and IoT messages respectively from the human-machine interface device 310 and the plurality of terminal devices 330. The device connection unit 323_2 may store a plurality of device connection information respectively corresponding to the human-machine interface device 310 and the plurality of terminal devices 330. The message buffer unit 323_3 may store a plurality of control commands to be sent to the plurality of terminal devices.

In this embodiment, the human-machine interface device management module 324 of the cloud device 320 may include a scheduling unit 324_1 and a message aggregation unit 324_2. The scheduling unit 324_1 may monitor the device connection information of the human-machine interface device 310 stored in the device connection unit 323_2 to generate a message push schedule. The message aggregation unit 324_2 may aggregate at least one IoT message of at least one terminal device 330 stored in the device data unit 323_1 to generate an aggregated message.

In this embodiment, the functions and implementation methods of the relevant modules and units executed by the human-machine interface device 310, the cloud device 320 and the terminal device 330 of the Internet of Things system 300 can also refer to the description of the embodiments of Figures 1 and 2 above, so they are not elaborated here.

In this embodiment, the human-machine interface device 310, the cloud device 320 and the terminal device 330 of the IoT system 300 can be operated as follows in steps S301-S312 to realize the function of managing the terminal device 330. It is worth noting that this embodiment is explained by taking a terminal device 330 as an example, and can be analogized to the implementation method of communication connection to multiple terminal devices. In step S301, the application function module 332 of the terminal device 330 can output the corresponding IoT message to the transmission module 331, for example, according to the sensing result of the sensor or the operating state of the terminal device 330. In step S302, the transmission module 331 can transmit the IoT message to the transmission module 321 of the cloud device 320. In step S303, the transmission module 321 may provide the IoT message to the message classification unit 322_1.

In step S304, the message classification unit 322_1 can classify the IoT message according to the state or data format, and store it in the device data unit 323_1 and the device connection unit 323_2 of the storage module 323. In step S305, the scheduling unit 324_1 can determine the connection state between the terminal device 330 and the human-machine interface device 310 through the device connection unit 323_2. In step S306, the scheduling unit 324_1 can control the message aggregation unit 324_2 according to the preset message push time schedule. In step S307, the message aggregation unit 324_2 may read the aforementioned IoT message and other IoT messages corresponding to other terminal devices from the device data unit 323_1, and aggregate the messages to generate an aggregated message.

In step S308, the message aggregation unit 324_2 may provide the aggregated message to the device control unit 322_3. In step S309, the device control unit 322_3 may provide the aggregated message to the transmission module 321 according to the message push schedule, and subscribe to the first dedicated communication channel for message transmission. In step S310, the transmission module 321 may transmit the aggregated message to the transmission module 311 of the human-machine interface device 310 via the first dedicated communication channel. In step S311, the transmission module 311 may transmit the aggregated message to the message application unit 313_1. In step S312 , the message application unit 313_1 may classify the aggregated message and transmit it to the application function module 314 , so that the user can realize the monitoring and management functions of the terminal device 330 by operating the application function module 314 of the human-machine interface device 310 .

In other words, when the cloud device 320 is connected to multiple terminal devices, the cloud device 320 can collect multiple IoT messages of multiple terminal devices 330 through the above steps S301 to S304. And, after the message aggregation, the human-machine interface device 310 only needs to subscribe to a first dedicated channel between the human-machine interface device 310 and the cloud device 320 to obtain a large number of IoT messages of a large number of terminal devices at the same time. Therefore, the IoT system 300 of this embodiment can realize the function of monitoring or managing a large number of terminal devices at the same time.

FIG4 is a schematic diagram of the operation of monitoring IoT messages in an embodiment of the present invention. Referring to FIG4, the functions and related technical features of the relevant modules and units executed by the cloud device 420 and the terminal device 430 of the IoT system 400 of this embodiment can refer to the description of the embodiments of FIG1 to FIG3 above, so no further details are given here. In this embodiment, the cloud device 420 and the terminal device 430 of the IoT system 400 can execute the following steps S401~S408 to realize the function of monitoring IoT messages. In step S401, the message monitoring unit 422_2 will continuously check the data of the device data unit 423_1 and the device connection unit 423_2 in the storage module 423. When the message monitoring unit 422_2 determines that the terminal device 430 does not return the IoT message, in step S402, the message monitoring unit 422_2 operates the device control unit 422_3.

In step S403, the message monitoring unit 422_2 may send a status report command to the transmission module 421 through the device control unit 422_3. In step S404, the transmission module 421 may transmit a status report command to the transmission module 431 of the terminal device 430 via the second dedicated communication channel between the terminal device 430. In step S405, the application function module 432 of the terminal device 430 may receive the status report command provided by the transmission module 431 and return the corresponding IoT message to the transmission module 431. In step S406, the terminal device 430 may return the IoT message to the transmission module 421 of the cloud device 420 according to the status report command and through the transmission module 431. In step S407, the message classification unit 422_1 can classify the IoT message according to the status or data format. In step S408, the message classification unit 422_1 can store the classified IoT message in the device data unit 423_1 of the storage module 423. Therefore, the IoT system 400 of this embodiment can ensure that the device data unit 423_1 in the storage module 423 of the cloud device 420 can stably update the latest status of each of the multiple terminal devices to effectively avoid data loss caused by, for example, unstable connection status.

FIG5 is a schematic diagram of the operation of the Internet of Things system of an embodiment of the present invention in the general mode. Referring to FIG5, the functions and related technical features of the relevant modules and units executed by the human-machine interface device 510, the cloud device 520 and the terminal device 530 of the Internet of Things system 500 of this embodiment can refer to the description of the embodiments of FIG1 to FIG4 above, so no further details are given here. In this embodiment, the human-machine interface device 510, the cloud device 520 and the terminal device 530 of the Internet of Things system 500 can execute the following steps S501~S510 to realize the function of the general mode of controlling the terminal device 530. In step S501, the user can transmit the control command to the channel scheduling unit 512_1 of the channel management module 512 by operating the application function module 514 of the human-machine interface device 510. In this embodiment, the channel scheduling unit 512_1 may include a command queue. The channel scheduling unit 512_1 may sort the control commands into the command queue according to the subscription order. In this regard, the channel scheduling unit 512_1 may calculate the priority order and update the command queue according to the level and priority of the control command. The channel allocation unit 512_2 will subscribe to the idle first communication channel in sequence according to the order of the control commands in the command queue, and dynamically release the first communication channel that has completed the transmission of the control command for subscription to the control command of the next order. In step S503, the channel allocation unit 512_2 transmits the control command to the transmission module 511, so that the transmission module 511 can transmit the control command to the transmission module 521 of the cloud device 520 via the subscribed first communication channel in step S504. In step S505, the transmission module 521 of the cloud device 520 can transmit the control command to the transmission module 531 of the terminal device 530 via the corresponding second communication channel. It is worth noting that the channel allocation unit 512_2 can calculate and set the dynamic release time of the subscribed first communication channel and the corresponding second communication channel to improve the channel throughput.

In step S506, the application function module 532 of the terminal device 530 may receive the control command provided by the transmission module 531, and return the corresponding IoT message to the transmission module 531. In step S507, the terminal device 530 may return the IoT message to the transmission module 521 of the cloud device 520 through the transmission module 531. In step S508, the transmission module 521 may transmit the IoT message to the transmission module 511 of the human-machine interface device 510 via the subscribed first communication channel. In step S509, the transmission module 511 may transmit the IoT message to the message application unit 513_1. In step S510, the message application unit 513_1 can classify the IoT message and transmit it to the application function module 514, so that the user can obtain the IoT message returned by the terminal device 530 by operating the application function module 514 of the human-machine interface device 510. Therefore, the IoT system 500 of this embodiment can be operated in a general mode to efficiently control the terminal device 530 and realize the function of operating a large number of terminal devices at the same time.

In this embodiment, the channel allocation unit 512_2 can sequentially subscribe to the idle first communication channel and the corresponding second communication channel according to the command queue, and dynamically release the first communication channel and the corresponding second communication channel that have completed the transmission of the control command, so as to be subscribed for the transmission of the next sequence of control commands. In other words, when the cloud device 520 is communicatively connected to multiple terminal devices, the user can control these terminal devices through the human-machine interface device 510, and is not limited by the number of channels to achieve efficient terminal device control functions. The Internet of Things system 500 of this embodiment can effectively ensure that the human-machine interface device 510 can perform efficient channel scheduling and allocation through the channel management module 512 under the condition of a limited number of first communication channels.

FIG6 is a schematic diagram of the operation of the Internet of Things system of an embodiment of the present invention executing the timeout mode. Referring to FIG6, the functions and related technical features of the relevant modules and units executed by the human-machine interface device 610, the cloud device 620 and the terminal device 630 of the Internet of Things system 600 of this embodiment can refer to the description of the embodiments of FIG1 to FIG3 above, so no further details are given here. In this embodiment, the human-machine interface device 610, the cloud device 620 and the terminal device 630 of the Internet of Things system 600 can execute the following steps S601~S621 to realize the function of controlling the timeout mode of the terminal device 630. In step S601, the user can transmit the control command to the channel scheduling unit 612_1 of the channel management module 612 by operating the application function module 614 of the human-machine interface device 610. In this embodiment, the channel scheduling unit 612_1 may include a command queue. The channel scheduling unit 612_1 may sort the control commands into the command queue according to the subscription order. In this regard, the channel scheduling unit 612_1 may calculate the priority order and update the command queue according to the information such as the level and priority of the control command. The channel allocation unit 612_2 will dynamically subscribe to one of the first communication channels with a limited number (and the corresponding second communication channel) according to the order of the control commands in the command queue, and subscribe to one of the first communication channels corresponding to the terminal device 630. In step S603, the channel allocation unit 612_2 transmits the control command to the transmission module 611, so that the transmission module 611 can transmit the control command to the transmission module 621 of the cloud device 620 via the subscribed first communication channel in step S604. In step S605, the message classification unit 622_1 of the terminal device management module 622 can receive the control command provided by the transmission module 621. In step S606, the message classification unit 622_1 can classify the control command according to the state or data format, and store it in the message temporary storage unit 623_3 of the storage module 623. In step S607, the message monitoring unit 622_2 can monitor whether the control command temporarily stored in the message temporary storage unit 623_3 has been sent to the terminal device 630. In step S608, when the message monitoring unit 622_2 determines that the control command has timed out and has not been sent to the corresponding terminal device 630, the message monitoring unit 622_2 can notify the device control unit 622_3. In step S609, the device control unit 622_3 can confirm the connection status of the terminal device 630 through the device connection unit 623_2. In step S610, when the connection status of the terminal device 630 is normal, the message monitoring unit 622_2 can resend the control command through the second dedicated communication channel between the corresponding terminal device through the device control unit 622_3. In this regard, the device control unit 622_3 can generate a delegated control command based on the aforementioned unsent control command and transmit the delegated control command to the transmission module 621.

In step S611, the transmission module 621 of the cloud device 620 may transmit the delegated control command to the transmission module 631 of the terminal device 630 via the corresponding second dedicated communication channel. In step S612, the application function module 632 of the terminal device 630 may receive the delegated control command provided by the transmission module 631, and return the corresponding IoT message to the transmission module 631. In step S613, the terminal device 630 may return the IoT message to the transmission module 621 of the cloud device 620 via the transmission module 631. In step S614, the message classification unit 622_1 may receive the IoT message provided by the transmission module 621. In step S615, the message classification unit 622_1 can classify the IoT message according to the state or data format, and store it in the message temporary storage unit 623_3 of the storage module 623. In step S616, the message monitoring unit 622_2 can determine that the delegated control has been completed according to the IoT message temporarily stored in the message temporary storage unit 623_3. In step S617, the device control unit 622_3 can confirm the connection status of the human-machine interface device 610 through the device connection unit 623_2. In step S618, the device control unit 622_3 can transmit the IoT message to the transmission module 621.

In step S619, the transmission module 621 may transmit the IoT message to the transmission module 611 of the human-machine interface device 610 via the subscribed first dedicated communication channel. In step S620, the transmission module 631 may transmit the IoT message to the message application unit 613_1. In step S621, the message application unit 613_1 may classify the IoT message and transmit it to the application function module 614, so that the user can obtain the IoT message returned by the terminal device 630 by operating the application function module 614 of the human-machine interface device 610. Therefore, the IoT system 600 of this embodiment may operate in a timeout mode to delegate control functions to the terminal device 630. The IoT system 600 of this embodiment can effectively ensure that the control process between the human-machine interface device 610 and the terminal device 630 will not cause control failure or data loss due to abnormal connection and other situations.

FIG7 is an operation diagram of an IoT system of an embodiment of the present invention executing a delegation mode. Referring to FIG7, the functions and related technical features of the relevant modules and units executed by the human-machine interface device 710, the cloud device 720, and the terminal device 730 of the IoT system 700 of the present embodiment can refer to the description of the embodiments of FIG1 to FIG3 above, so no further details are given here. In the present embodiment, the human-machine interface device 710, the cloud device 720, and the terminal device 730 of the IoT system 700 can execute the following steps S701~S721 to realize the function of the delegation mode of controlling the terminal device 730. In step S701, the user can transmit the control command to the channel scheduling unit 712_1 of the channel management module 712 by operating the application function module 714 of the human-machine interface device 710. In this embodiment, when the channel scheduling unit 712_1 detects that the command queue is congested and there is a control command with a higher level (or higher priority), the channel scheduling unit 712_1 can transmit the control command with the higher level to the control delegation unit 713_2 of the data management module 713 to generate a corresponding delegated control command. In step S703, the control delegation unit 713_2 transmits the delegated control command to the transmission module 711. In step S704, the transmission module 711 may transmit the delegated control command to the transmission module 721 of the cloud device 720 via the first dedicated communication channel. In other words, when all the first communication channels are occupied, the channel scheduling unit 712_1 of this embodiment may transfer at least one control command (or emergency control command) with a higher priority to the control delegation unit 713_2 to transmit the corresponding delegated control command to the cloud device 720 via the first dedicated communication channel.

In step S705, the message classification unit 722_1 of the terminal device management module 722 may receive the delegated control command provided by the transmission module 721. In step S706, the message classification unit 722_1 may classify the delegated control command according to the state or data format and store it in the message temporary storage unit 723_3 of the storage module 723. In step S707, the message monitoring unit 722_2 may monitor whether the delegated control command temporarily stored in the message temporary storage unit 723_3 has been sent to the terminal device 730. In step S708, the message monitoring unit 722_2 may notify the device control unit 722_3. In step S709, the device control unit 722_3 can confirm the connection status of the terminal device 730 through the device connection unit 723_2. In step S710, when the connection status of the terminal device 730 is normal, the device control unit 722_3 can send the delegated control command to the terminal device 730 via the second dedicated communication channel between the terminal device 730 and the terminal device 730.

In step S711, the transmission module 721 of the cloud device 720 may transmit the delegated control command to the transmission module 731 of the terminal device 730 via the corresponding second dedicated communication channel. In step S712, the application function module 732 of the terminal device 730 may receive the delegated control command provided by the transmission module 731, and return the corresponding IoT message to the transmission module 731. In step S713, the terminal device 730 may return the IoT message to the transmission module 721 of the cloud device 720 via the transmission module 731. In step S714, the message classification unit 722_1 may receive the IoT message provided by the transmission module 721. In step S715, the message classification unit 722_1 can classify the IoT message according to the state or data format, and store it in the message temporary storage unit 723_3 of the storage module 723. In step S716, the message monitoring unit 722_2 can determine that the delegated control has been completed according to the IoT message temporarily stored in the message temporary storage unit 723_3. In step S717, the device control unit 722_3 can confirm the connection status of the human-machine interface device 710 through the device connection unit 723_2. In step S718, the device control unit 722_3 can transmit the IoT message to the transmission module 721.

In step S719, the transmission module 721 may transmit the IoT message to the transmission module 711 of the human-machine interface device 710 via the first dedicated communication channel. In step S720, the transmission module 731 may transmit the IoT message to the message application unit 713_1. In step S721, the message application unit 713_1 may classify the IoT message and transmit it to the application function module 714, so that the user can obtain the IoT message returned by the terminal device 730 by operating the application function module 714 of the human-machine interface device 710. Therefore, the IoT system 700 of this embodiment can be operated in a delegation mode to delegate control functions to the terminal device 730, and can effectively avoid the situation where the emergency control command is delayed in being sent to the corresponding terminal device due to congestion in the first communication channel.

FIG8 is a schematic diagram of an electronic device of an embodiment of the present invention. Referring to FIG1, each of the cloud device 120 and the terminal devices 130_1 to 130_N in FIG1 can be implemented in the same manner as the electronic device 800. In an embodiment of the present invention, the electronic device 800 includes a transmission module 801, an IoT device management module 802, a storage module 803, an HMI device management module 804, and an application function module 805. The IoT device management module 802 includes a message classification unit 802_1, a message monitoring unit 802_2, and a device control unit 802_3. The storage module 803 includes a device data unit 803_1, a device connection unit 803_2, and a message buffer unit 803_3. The HMI device management module 804 includes a scheduling unit 804_1 and a message organization unit 804_2. The electronic device 800 can communicate with the HMI device via the transmission module 801.

In an embodiment of the present invention, the electronic device 800 may include a processor and a memory, and the memory may store relevant programs and software, so that the processor may execute the relevant programs and software to implement the above units and modules in the electronic device 800. In an embodiment of the present invention, the processor may be a central processing unit (CPU), a microcontroller unit (MCU) or other processing circuits, and the memory may be a non-temporary computer-readable recording medium, such as a read-only memory (ROM), an erasable programmable read-only memory (EPROM), an electrically-erasable programmable read-only memory (EEPROM) or a non-volatile memory (NVM).

In an embodiment of the present invention, the transmission module 801 can transmit and receive messages based on a wired/wireless communication protocol, and the transmission module 801 can include a device scan function. The transmission module 801 can include at least one of a fifth-generation mobile network (5G) module, a Bluetooth module, a wireless fidelity (WiFi) module, a Zigbee module, a Matter module, and a Message Queuing Telemetry Transmission (MQTT) module. In an embodiment of the present invention, the message classification unit 802_1 can be used to classify the messages received from the transmission module 801 into categories such as connection status, device data and control commands, and store these messages in the storage module 803, and can directly respond to the commands through the device control unit 802_3 according to the dedicated communication channel mode and whether an immediate response is required. The message monitoring unit 802_2 can monitor whether the command stored in the message buffer unit 803_3 has been completed, whether the device data unit 803_1 has timed out, and whether the control assignment of the HMI device has been received, and needs to obtain control rights to trigger the device control unit 802_3 to perform control on behalf of the message monitoring unit 802_2. In the device management mode and the general communication channel mode, the message monitoring unit 802_2 can also monitor whether the HMI device does not connect to access the device data after the timeout period. If a timeout occurs, the message monitoring unit 802_2 can restore the connection with the original management device via the dedicated communication channel and send a request to switch the transmission mode to the original mode and cancel the hosting. In an embodiment of the present invention, the device control unit 802_3 can explore the exclusive channel of the IoT device (terminal device/HMI) and perform a message push operation.

In an embodiment of the present invention, the device data unit 803_1 can store terminal/HMI device environment information, such as sensor data, user permission, etc. In an embodiment of the present invention, the device connection unit 803_2 can store terminal/HMI device connection information, including, for example, device transmission mode (BitTorrent (BT), WiFi, Matter, etc.), communication channel, additional information (Internet Protocol (IP), device name, etc.), and fields such as device hosting or HMI hosting. In an embodiment of the present invention, the message buffer unit 803_3 can temporarily store control commands of the HMI device.

In an embodiment of the present invention, the scheduling unit 804_1 can monitor the connection status of the HMI device in the device connection unit 803_2 in the storage module 803, and can guide the push time control of the collected information. In an embodiment of the present invention, the message organization unit 804_2 can collect and convert the information in the device data unit 803_1, and can identify whether the terminal device and the HMI device are located in the same communication area. If the terminal device and the HMI device are located in the same communication area, the message organization unit 804_2 can collect multiple information detected by the HMI that multiple terminal devices exist in the adjacent area or the same area, and transmit the result to the device control unit 802_3 in the IoT device management module 802. In the embodiment of the present invention, the application function module 805 can provide application functions of the electronic device 800, and can further include functions such as timing report.

In addition, the relevant technical features of the electronic device 800 in this embodiment can be further referred to the description of the embodiments in FIG. 1 to FIG. 7 , and thus will not be elaborated here.

FIG9 is a flow chart of a message classification method of an embodiment of the present invention. Referring to FIG8 and FIG9 , the message classification unit 802_1 may perform the following steps S910 to S960. In step S910, the message classification unit 802_1 may receive a message from the transmission module 801, and the message may include a control command. In step S920, the message classification unit 802_1 may classify the message and determine whether the message indicates the use of a general communication channel or a dedicated communication channel. If the message classification unit 802_1 determines that the message indicates the use of a general communication channel, then in step S930, the message classification unit 802_1 may transmit the message to the device control unit 802_3 and transmit the corresponding command via the general communication channel. If the message classification unit 802_1 determines that the message indicates the use of a dedicated communication channel, then in step S940, the message classification unit 802_1 can determine whether the command has an immediate response requirement. If the command has an immediate response requirement, then in step S950, the message classification unit 802_1 can transmit the message to the device control unit 802_3 and transmit the corresponding command via the dedicated communication channel. If the command does not have an immediate response requirement, then in step S960, the message classification unit 802_1 can store the message in the storage module 803, and the HMI device management module 804 transmits the corresponding command via the dedicated communication channel.

FIG. 10 is a flow chart of a message monitoring method of an embodiment of the present invention. Referring to FIG. 8 and FIG. 10 , the message monitoring unit 802_2 may perform the following steps S1010 to S1040. In step S1010, the message monitoring unit 802_2 may monitor the HMI device by monitoring the message. In step S1020, the message monitoring unit 802_2 may determine the channel mode operated between the electronic device 800 and the HMI device. If the electronic device 800 communicates with the HMI device via a dedicated communication channel, then in step S1030, the message monitoring unit 802_2 may monitor whether the IoT message has timed out. If the electronic device 800 communicates with the HMI device via the universal communication channel, then in step S1040, the message monitoring unit 802_2 can monitor whether the HMI device has timed out and whether it has not been connected for access.

FIG. 11 is a schematic diagram of a human-machine interface device of an embodiment of the present invention. Referring to FIG. 1 , the HMI device 110 in FIG. 1 can be implemented in the same manner as the HMI device 1110. In the embodiment of the present invention, the HMI device 1110 includes a transmission module 1111, a channel management module 1112, a data management module 1113, and an application function module 1114. The channel management module 1112 includes a channel allocation unit 1112_1, a device connection unit 1112_2, a channel scheduling unit 1112_3, and a scheduling unit 1112_4. The data management module 1113 includes a message application unit 1113_1 and a control request unit 1113_2.

In an embodiment of the present invention, the HMI device 1110 may include a processor and a memory, and the memory may store relevant programs and software, so that the processor may execute the relevant programs and software to implement the above units and modules in the HMI device 1110. In an embodiment of the present invention, the processor may be a central processing unit (CPU), a microcontroller unit (MCU) or other processing circuits, and the memory may be a non-transitory computer-readable recording medium, such as a read-only memory (ROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM) or a non-volatile memory (NVM).

In an embodiment of the present invention, the transmission module 1111 can establish multiple first communication channels and first dedicated communication channels between the HMI device 1110 and the above electronic device 800 (i.e., terminal device or cloud device). The transmission module 1111 can transmit and receive messages based on wired/wireless communication protocols, and the transmission module 1111 can include a device scanning function.

In an embodiment of the present invention, the channel management module 1112 can schedule and allocate dedicated communication channels for terminal devices to subscribe in a limited number of channels used for control command transmission. In an embodiment of the present invention, the channel allocation unit 1112_1 can dynamically and sequentially subscribe to the occupied communication channels according to the queue priority calculated by the channel scheduling unit 1112_3, and design a dynamic release time to speed up the efficiency of communication channel allocation. When the channel allocation unit 1112_1 determines that the communication channel has not responded or delayed response, the message monitoring unit of the IOT device management module in the cloud device is responsible, and the channel allocation unit 1112_1 can allocate (shared) communication channels, dedicated communication channels and transmission modes, and can use the header of the message to explain the transmission mode and communication channel mode of the message. In an embodiment of the present invention, the device connection unit 1112_2 can store the near-end connection information of the device, wherein the near-end connection information at least includes the device unique code, the managed sub-device, the communication channel information, the transmission mode information, and the previous control time information. The near-end connection information is used to distinguish the transmission mode and communication channel of the HMI device, for example, connecting to the cloud device to transmit the commands to the terminal device, or connecting to the terminal device to transmit the commands to the sub-terminal device.

In an embodiment of the present invention, the channel scheduling unit 1112_3 can calculate the priority of the command queue based on information such as the rank and weight of the control command, and has a mechanism to select a higher-rank command in the command queue when all channels are busy, and deliver the control command to the cloud device for control via the control request unit 1113_2 in the data management module 1113. In an embodiment of the present invention, the scheduling unit 1112_4 can periodically determine the terminal device that supports the transmission mode switching by reading the device connection unit 1112_2, and generate a low-priority detection command to the command queue in the channel scheduling unit 1112_3. In addition, the scheduling unit 1112_4 can also periodically read the managed terminal device by reading the device connection unit 1112_2 that is in the general communication channel mode and has reached the time to be controlled and managed, and can generate a medium priority message to obtain a control command and transmit the control command to the command queue in the channel scheduling unit 1112_3.

In an embodiment of the present invention, the message application unit 1113_1 can receive the collected terminal device messages (collected information), classify the messages according to the actual application, and transmit the messages to the application function module. If the message application unit 1113_1 identifies that the message is a change in the transmission mode or communication channel mode, the message is assigned to the device connection unit 1112_2 and marked. If the message application unit 1113_1 identifies that the message is a managed device message, the message application unit 1113_1 will transmit the message to the original management device (e.g., cloud device) via the first dedicated communication channel. In an embodiment of the present invention, the control request unit 1113_2 can push the control command to the IOT device management module in the cloud device via the dedicated communication channel of the HMI device, so that the message monitoring unit of the cloud device can issue the control command instead of the HMI after detection. In an embodiment of the present invention, the application function module 1114 can have an operation screen or function that can actually interact with the user, and can include a function that can be set to connect the device via a dedicated communication channel mode.

In addition, the relevant technical features of the HMI device 1110 in this embodiment can be further referred to the description of the embodiments in Figures 1 to 7, so they will not be repeated here.

FIG. 12 is a flow chart of a channel allocation method according to an embodiment of the present invention. Referring to FIG. 11 and FIG. 12, the message classification unit 802_1 may perform the following steps S1210 to S1250. In step S1210, the channel allocation unit 1112_1 may identify the channel mode according to the header of the message. In step S1220, the channel allocation unit 1112_1 may determine whether the terminal device is connected. If the channel allocation unit 1112_1 is not connected to the terminal device, then in step S1230, the channel allocation unit 1112_1 may allocate a dedicated communication channel. If the channel allocation unit 1112_1 is connected to the terminal device, then in step S1240, the channel allocation unit 1112_1 can further determine whether the terminal device has a sub-terminal device. If the terminal device has a sub-terminal device, then in step S1230, the channel allocation unit 1112_1 can allocate a dedicated communication channel. If the terminal device does not have a sub-terminal device, then in step S1250, the channel allocation unit 1112_1 can allocate a general communication channel.

It should be noted that the IoT system of each of the following embodiments can not only be implemented as the IoT system of the above embodiments of Figures 1 to 7, but can also further implement the functions of the following embodiments of Figures 13 to 17, thereby switching the HMI device to manage and control the terminal devices adjacent to the HMI device without going through the cloud device.

FIG13 is a schematic diagram of an HMI device that actively switches the transmission mode according to an embodiment of the present invention. Referring to FIG13 , the IoT system 1300 includes an HMI device 1310, a cloud device 1320, and a terminal device 1330. The HMI device 1310 includes a transmission module 1311, a channel management module 1312, a data management module 1313, and an application function module 1314. The channel management module 1312 includes a channel allocation unit 1312_1, a device connection unit 1312_2, a channel scheduling unit 1312_3, and a scheduling unit 1312_4. The data management module 1313 includes a message application unit 1313_1 and a control request unit 1313_2.

The cloud device 1320 includes a transmission module 1321, an IoT device management module 1322, a storage module 1323, an HMI device management module 1324, and an application function module 1325. The IoT device management module 1322 includes a message classification unit 1322_1, a message monitoring unit 1322_2, and a device control unit 1322_3. The storage module 1323 includes a device data unit 1323_1, a device connection unit 1323_2, and a message buffer unit 1323_3. The HMI device management module 1324 includes a scheduling unit 1324_1 and a message organization unit 1324_2. The cloud device 1320 can communicate with the transmission module 1311 of the HMI device 1310 via the transmission module 1321 .

The terminal device 1330 includes a transmission module 1331, an IoT device management module 1332, a storage module 1333, an HMI device management module 1334, and an application function module 1335. The IoT device management module 1332 includes a message classification unit 1332_1, a message monitoring unit 1332_2, and a device control unit 1332_3. The storage module 1333 includes a device data unit 1333_1, a device connection unit 1333_2, and a message buffer unit 1333_3. The HMI device management module 1334 includes a scheduling unit 1334_1 and a message organization unit 1334_2. The terminal device 1330 can communicate with the transmission module 1311 of the HMI device 1310 via the transmission module 1331 .

In an embodiment of the present invention, the IoT system 1300 may perform the following steps S1301 to S1333 to implement active switching of the transmission mode through the HMI device 1310. In step S1301, the scheduling unit 1312_4 may determine the terminal device 1330 that supports the transmission mode switching by reading the device connection unit 1312_2, and generate a low priority detection command to the command queue in the channel scheduling unit 1312_3. The channel scheduling unit 1312_3 includes a command queue. In step S1302, the channel scheduling unit 1312_3 may calculate the subscription order according to the priority information of the control command. In step S1303, the channel allocation unit 1312_1 may allocate the first communication channel according to the subscription order for the control commands to be transmitted to be subscribed in sequence. In step S1304, the transmission module 1311 may determine whether the terminal device 1330 is adjacent to the HMI device 1310. In an embodiment of the present invention, the terminal device 1330 determined to be adjacent to the HMI device 1310 is located in the same communication area as the HMI device 1310, or the distance between the HMI device 1310 and the terminal device 1330 determined to be adjacent to the HMI device 1310 is less than a predetermined distance.

In step S1305, the transmission module 1311 may transmit the transmission mode switching request message corresponding to the terminal device 1330 adjacent to the HMI device 1310 to the cloud device 1320 via the first dedicated communication channel. In step S1306, the transmission module 1321 may transmit the transmission mode switching request message to the message classification unit 1322_1. In step S1307, the message classification unit 1322_1 may classify the transmission mode switching request message and store the transmission mode switching request message in the device data unit 1323_1 and the device connection unit 1323_2 of the storage module 1323. In step S1308, the scheduling unit 1324_1 can determine the connection status between the terminal device 1330 and the HMI device 1310 via the device connection unit 1323_2. In step S1309, the scheduling unit 1324_1 can control the message organization unit 1324_2 according to the preset message push time schedule. The scheduling unit 1324_1 can monitor the device connection information of the HMI device 1310 stored in the device connection unit 1323_2 to generate a message push schedule. In step S1310, the message organization unit 1324_2 may read the IoT message and other IoT messages corresponding to other terminal devices from the device data unit 1323_1, and perform message organization to generate an organized message.

The message organizing unit 1324_2 can organize the IoT messages of the terminal device 1330 stored in the device data unit 1323_1 to generate an organized message. In step S1311, the message organizing unit 1324_2 can provide the organized message to the device control unit 1322_3. In step S1312, the device control unit 1322_3 can receive the organized message provided by the message organizing unit 1324_2, and transmit the organized message to the transmission module 1321 according to the message push schedule, and subscribe to the first dedicated communication channel for message transmission. In step S1313, the transmission module 1321 may transmit the organized message to the transmission module 1311 of the HMI device 1310 via the first dedicated communication channel. In step S1314, the transmission module 1311 may transmit the organized message to the message application unit 1313_1. The message application unit 1313_1 may classify the organized message and transmit the organized message to the application function module 1314, so that the user can achieve the function of monitoring and managing the terminal device 1330 by operating the application function module 1314 of the HMI device 1310. In step S1315, the message application unit 1313_1 may switch the original management device permission of the classification tag to the device connection unit 1312_2.

In step S1316, the scheduling unit 1312_4 can further determine the terminal device 1330 that supports the transmission mode switching by reading the device connection unit 1312_2, and further generate a high priority detection command to the command queue in the channel scheduling unit 1312_3. In step S1317, the channel scheduling unit 1312_3 can calculate the subscription order according to the priority information of the control command. In step S1318, the channel allocation unit 1312_1 can allocate the first communication channel according to the subscription order for the control command to be transmitted to be subscribed in sequence. In step S1319, the transmission module 1311 may again determine whether the terminal device 1330 is adjacent to the HMI device 1310, and transmit a transmission mode switching request message to the transmission module 1331 of the terminal device 1330 adjacent to the HMI device 1310 via the first communication channel.

In step S1320, the transmission module 1331 may transmit the switching transmission mode request message to the message classification unit 1332_1. The message classification unit 1332_1 may receive the switching transmission mode request message and determine that it must immediately respond to the switching transmission mode request message. In step S1321, the message classification unit 1332_1 may store the switching transmission mode request message in the device connection unit 1333_2 and further determine whether the terminal device has a sub-terminal device. In the embodiment of the present invention, when the terminal device 1330 has a sub-terminal device, the message classification unit 1332_1 replies to the HMI device 1310 to execute the dedicated communication channel mode and enable the HMI device management module 1334. In step S1322, when the terminal device 1330 does not have a sub-terminal device, the message classification unit 1332_1 disables the HMI device management module 1334, replies to the HMI device 1310 that the request to switch the transmission mode has been completed from the first (general) communication channel via the device control unit 1332_3, and interrupts the second dedicated communication channel between the cloud device 1320 and the terminal device 1330.

In step S1323, the device control unit 1332_3 may reply the proximal connection information to the HMI device via the transmission module 1331. In step S1324, the HMI device 1310 may notify the cloud device 1320 and the message application unit 1313_1 that the management switch has been completed via the transmission module 1311. In an embodiment of the present invention, the proximal connection information may include a device unique code, a managed sub-terminal device, communication channel information, transmission mode information, and previous control time information.

In step S1325, the message application unit 1313_1 may update the information recorded in the device connection unit 1312_2 that the management switching has been completed. In step S1326, the transmission module 1321 may transmit the proximal connection information to the message classification unit 1322_1. In step S1327, the message classification unit 1322_1 may classify the proximal connection information and store the proximal connection information in the device data unit 1323_1 and the device connection unit 1323_2 of the storage module 1323.

In addition, if the HMI device 1310 is currently using the dedicated communication channel mode during the scheduling unit detection, then in step S1328, the scheduling unit 1312_4 can determine the transmission mode of the HMI device 1310 by reading the device connection unit 1312_2, and generate a dedicated communication channel establishment command with the highest priority to the command queue in the channel scheduling unit 1312_3. In step S1329, the channel allocation unit 1312_1 can allocate the first dedicated communication channel for transmitting the dedicated communication channel establishment command. In step S1330, the channel allocation unit 1312_1 can transmit the dedicated communication channel establishment command to the transmission module 1311. In step S1331, the transmission module 1311 may transmit the dedicated communication channel establishment command to the transmission module 1331. In step S1332, the transmission module 1331 may transmit the dedicated communication channel establishment command to the message classification unit 1332_1. In step S1333, the message classification unit 1332_1 may mark completion in the device connection unit 1333_2, and the device connection unit 1333_2 may establish the dedicated communication channel.

Therefore, the HMI device 1310 of the present embodiment can switch to the local transmission mode to use lower latency and lower power consumption to manage and control the terminal device 1330. In addition, after releasing the second dedicated communication channel, the terminal device 1330 can effectively reduce its power consumption.

FIG14 is a schematic diagram of the operation of the universal communication channel mode of an embodiment of the present invention. Referring to FIG14 , the IoT system 1400 includes an HMI device 1410, a cloud device 1420, and a terminal device 1430. The HMI device 1410 includes a transmission module 1411, a channel management module 1412, a data management module 1413, and an application function module 1414. The channel management module 1412 includes a channel allocation unit 1412_1, a device connection unit 1412_2, a channel scheduling unit 1412_3, and a scheduling unit 1412_4. The data management module 1413 includes a message application unit 1413_1 and a control request unit 1413_2.

The cloud device 1420 includes a transmission module 1421, an IoT device management module 1422, a storage module 1423, an HMI device management module 1424, and an application function module 1425. The IoT device management module 1422 includes a message classification unit 1422_1, a message monitoring unit 1422_2, and a device control unit 1422_3. The storage module 1423 includes a device data unit 1423_1, a device connection unit 1423_2, and a message buffer unit 1423_3. The HMI device management module 1424 includes a scheduling unit 1424_1 and a message organization unit 1424_2. The cloud device 1420 can communicate with the transmission module 1411 of the HMI device 1410 via the transmission module 1421 .

The terminal device 1430 includes a transmission module 1431, an IoT device management module 1432, a storage module 1433, an HMI device management module 1434, and an application function module 1435. The IoT device management module 1432 includes a message classification unit 1432_1, a message monitoring unit 1432_2, and a device control unit 1432_3. The storage module 1433 includes a device data unit 1433_1, a device connection unit 1433_2, and a message buffer unit 1433_3. The HMI device management module 1434 includes a scheduling unit 1434_1 and a message organization unit 1434_2. The terminal device 1430 can communicate with the transmission module 1411 of the HMI device 1410 via the transmission module 1431 .

In an embodiment of the present invention, the IoT system 1400 may execute the following steps S1401 to S1415 to execute the general communication channel mode. In step S1401, the scheduling unit 1412_4 of the channel management module 1412 in the HMI device 1410 may periodically read the information recorded in the device connection unit 1412_2 of the managed terminal device in the general communication channel mode and reaching the time to be controlled and managed, and the scheduling unit 1412_4 may generate a message acquisition command with a medium priority and transmit the message acquisition command to the command queue in the channel scheduling unit 1412_3. In step S1402, the channel scheduling unit 1412_3 may calculate the subscription order according to the priority information of the message acquisition command. In step S1403, the channel allocation unit 1412_1 may allocate the first communication channel according to the subscription order for the message acquisition command to be transmitted to be subscribed in sequence. In step S1404, the transmission module 1411 may transmit the message acquisition command to the transmission module 1431. In step S1405, the transmission module 1431 may transmit the message acquisition command to the message classification unit 1432_1. In step S1406, the message classification unit 1432_1 may cooperate with the device connection unit 1433_2 to identify the message acquisition command as a general communication channel request. In step S1407, the message classification unit 1432_1 may transmit the message acquisition command to the device control unit 1432_3. The device control unit 1432_3 may obtain a reply message from the device data unit 1433_1 or the application function module 1435. In step S1408, the device control unit 1432_3 may transmit the reply message to the transmission module 1431. In step S1409, the transmission module 1431 may transmit the reply message to the transmission module 1411 via the first communication channel.

In step S1410, the transmission module 1411 transmits the reply message to the message application unit 1413_1. In step S1411, the message application unit 1413_1 can identify that the message currently in the first communication channel mode needs to update the latest control time point in the device connection unit 1412_2. In step S1412, the message application unit 1413_1 can distinguish whether there is an original management device (i.e., cloud device 1420). If there is an original management device (i.e., cloud device 1420), the message application unit 1413_1 can copy the reply message to the original management device (i.e., cloud device 1420) via the first dedicated communication channel. In step S1413, the transmission module 1411 may transmit the reply message to the transmission module 1421 via the first dedicated communication channel. In step S1414, the transmission module 1421 may transmit the reply message to the message classification unit 1422_1. In step S1415, the message classification unit 1422_1 may classify the reply message and store the reply message in the device data unit 1423_1 and the device connection unit 1423_2 of the storage module 1423.

Therefore, using a limited number of universal communication channels, the HMI device 1410 of this embodiment can be effectively scheduled and allocated via the channel management module 1412, so that the control of the terminal device 1430 will not be limited by the number of channels.

FIG15 is a schematic diagram of the operation of the dedicated communication channel mode of an embodiment of the present invention. Referring to FIG15 , the IoT system 1500 includes an HMI device 1510, a cloud device 1520, and a terminal device 1530. The HMI device 1510 includes a transmission module 1511, a channel management module 1512, a data management module 1513, and an application function module 1514. The channel management module 1512 includes a channel allocation unit 1512_1, a device connection unit 1512_2, a channel scheduling unit 1512_3, and a scheduling unit 1512_4. The data management module 1513 includes a message application unit 1513_1 and a control request unit 1513_2.

The cloud device 1520 includes a transmission module 1521, an IoT device management module 1522, a storage module 1523, an HMI device management module 1524, and an application function module 1525. The IoT device management module 1522 includes a message classification unit 1522_1, a message monitoring unit 1522_2, and a device control unit 1522_3. The storage module 1523 includes a device data unit 1523_1, a device connection unit 1523_2, and a message buffer unit 1523_3. The HMI device management module 1524 includes a scheduling unit 1524_1 and a message organization unit 1524_2. The cloud device 1520 can communicate with the transmission module 1511 of the HMI device 1510 via the transmission module 1521 .

The terminal device 1530 includes a transmission module 1531, an IoT device management module 1532, a storage module 1533, an HMI device management module 1534, and an application function module 1535. The IoT device management module 1532 includes a message classification unit 1532_1, a message monitoring unit 1532_2, and a device control unit 1532_3. The storage module 1533 includes a device data unit 1533_1, a device connection unit 1533_2, and a message buffer unit 1533_3. The HMI device management module 1534 includes a scheduling unit 1534_1 and a message organization unit 1534_2. The terminal device 1530 can communicate with the transmission module 1511 of the HMI device 1510 via the transmission module 1531 .

In an embodiment of the present invention, the IoT system 1500 may execute the following steps S1501 to S1524 to execute the dedicated communication channel mode. In step S1501, the scheduling unit 1534_1 may control the message organization unit 1534_2 according to the preset message push time schedule. In step S1502, the scheduling unit 1534_1 may determine the connection status between the terminal device 1530 and the HMI device 1510 via the device connection unit 1533_2. In step S1503, the message organization unit 1534_2 can read the above IoT message and other IoT messages corresponding to other terminal devices from the device data unit 1533_1 and/or the application function module 1535, and perform message organization to generate an organized message. In step S1504, the message organization unit 1534_2 can provide the organized message to the device control unit 1532_3. In step S1505, the device control unit 1532_3 can provide the organized message to the transmission module 1531 according to the message push schedule, and subscribe to the first dedicated communication channel for message transmission. In step S1506, the transmission module 1531 may transmit the organized message to the transmission module 1511 of the HMI device 1510 via the first dedicated communication channel. In step S1507, the transmission module 1511 may transmit the organized message to the message application unit 1513_1. In step S1508, the message application unit 1513_1 may classify the organized message and transmit the organized message to the application function module 1514, so that the user can achieve the function of monitoring and managing the terminal device 1530 by operating the application function module 1514 of the HMI device 1510.

In step S1509, the message application unit 1513_1 can distinguish whether the original management device (i.e., the cloud device 1520) exists. If the original management device (i.e., the cloud device 1520) exists, the message application unit 1513_1 can copy the organized message to the original management device (i.e., the cloud device 1520) via the first dedicated communication channel. In step S1510, the message application unit 1513_1 can transmit the organized message to the transmission module 1511. In step S1511, the transmission module 1511 can transmit the reply message to the transmission module 1511 via the first dedicated communication channel. In step S1512, the transmission module 1521 may transmit the organized message to the message classification unit 1522_1. In step S1513, the message classification unit 1522_1 may classify the organized message and store the organized message in the device data unit 1523_1 and the device connection unit 1523_2 of the storage module 1523.

In an embodiment of the present invention, the application function module 1635 may have the function of enabling and disabling the first dedicated communication channel mode. In step S1514, the application function module 1514 may read the relevant required information from the device connection unit 1512_2, including the unique code of the device, sub-device custody, communication channel and transmission mode, etc. In step S1515, the application function module 1514 may transmit the enable command or disable command of the dedicated communication channel mode with the highest priority to the command queue of the channel scheduling unit 1512_3.

In step S1516, the channel scheduling unit 1512_3 may subscribe (or release) the first dedicated communication channel. In step S1517, the channel allocation unit 1512_1 may allocate the first communication channel according to the subscription order for the enable command or disable command of the dedicated communication channel mode to be transmitted in sequence. In step S1518, the transmission module 1511 may transmit the enable command or disable command of the dedicated communication channel mode to the transmission module 1531. In the embodiment of the present invention, the first dedicated communication channel will not be released dynamically, which can reduce data transmission delay.

In step S1519, the transmission module 1531 may transmit the enable command or disable command of the dedicated communication channel mode to the message classification unit 1532_1. In step S1520, the message classification unit 1532_1 may transmit the enable command or disable command of the dedicated communication channel mode to the device control unit 1532_3. In step S1521, the device control unit 1532_3 may directly transmit the reply message to the transmission module 1531. In step S1522, the transmission module 1531 may transmit the reply message to the transmission module 1521 via the first dedicated communication channel.

In step S1523, the transmission module 1521 transmits the reply message to the message classification unit 1522_1. In step S1524, the message classification unit 1522_1 may mark the successful switching to the first dedicated communication channel mode. Therefore, the HMI device 1510 can control and manage complex devices with the lowest latency, and is suitable for scenarios that require real-time high priority or control of sub-devices via the cloud device 1520 or the terminal device 1530.

FIG16 is a schematic diagram of the operation of the cloud device notification switching transmission mode of an embodiment of the present invention. Referring to FIG16 , the IoT system 1600 includes an HMI device 1610, a cloud device 1620, and a terminal device 1630. The HMI device 1610 includes a transmission module 1611, a channel management module 1612, a data management module 1613, and an application function module 1614. The channel management module 1612 includes a channel allocation unit 1612_1, a device connection unit 1612_2, a channel scheduling unit 1612_3, and a scheduling unit 1612_4. The data management module 1613 includes a message application unit 1613_1 and a control request unit 1613_2.

The cloud device 1620 includes a transmission module 1621, an IoT device management module 1622, a storage module 1623, an HMI device management module 1624, and an application function module 1625. The IoT device management module 1622 includes a message classification unit 1622_1, a message monitoring unit 1622_2, and a device control unit 1622_3. The storage module 1623 includes a device data unit 1623_1, a device connection unit 1623_2, and a message buffer unit 1623_3. The HMI device management module 1624 includes a scheduling unit 1624_1 and a message organization unit 1624_2. The cloud device 1620 can communicate with the transmission module 1611 of the HMI device 1610 via the transmission module 1621 .

The terminal device 1630 includes a transmission module 1631, an IoT device management module 1632, a storage module 1633, an HMI device management module 1634, and an application function module 1635. The IoT device management module 1632 includes a message classification unit 1632_1, a message monitoring unit 1632_2, and a device control unit 1632_3. The storage module 1633 includes a device data unit 1633_1, a device connection unit 1633_2, and a message buffer unit 1633_3. The HMI device management module 1634 includes a scheduling unit 1634_1 and a message organization unit 1634_2. The terminal device 1630 can communicate with the transmission module 1611 of the HMI device 1610 via the transmission module 1631 .

In an embodiment of the present invention, the IoT system 1600 may execute the above steps S1301 to S1333 of the embodiment of FIG. 13 to implement the active switching of the transmission mode by the HMI device 1610, and the IoT system 1600 may continue to execute the following steps S1601 to S1612 to further perform the operation of notifying the cloud device to switch the transmission mode. In step S1601, the device connection unit 1633_2 and the application function module 1635 may transmit a message of uploading information to the transmission module 1631, and the information may include a control command provided by the application function module 1635 and a connection message provided by the device connection unit 1633_2. The message of the upload information may include information of the transmission mode (e.g., Bluetooth, WiFi, and Matter), additional information (ip, device name), and other relevant information that can be used as a regional identifier. In step S1602, the transmission module 1631 may transmit the message of the upload information to the transmission module 1621. In step S1603, the transmission module 1621 may transmit the message of the upload information to the message classification unit 1622_1. In step S1604, the message classification unit 1622_1 may classify the message of the upload information and store the message of the upload information in the device data unit 1623_1 and the device connection unit 1623_2 of the storage module 1623.

In step S1605, the scheduling unit 1624_1 can determine the connection status between the terminal device 1630 and the HMI device 1610 via the device connection unit 1623_2. In step S1606, the scheduling unit 1324_1 can control the message organization unit 1624_2 according to the preset message push time schedule. The scheduling unit 1624_1 can monitor the device connection information of the HMI device 1610 stored in the device connection unit 1623_2 to generate a message push schedule. In step S1607, the message organization unit 1624_2 can read the above IoT message and other IoT messages corresponding to other terminal devices from the device data unit 1623_1, and perform message organization to generate an organized message. In addition, the message organization unit 1624_2 can further identify whether the terminal device 1630 and the HMI device 1610 are located in the same communication area. The message organization unit 1624_2 can detect whether the terminal device 1630 exists in an area adjacent to or in the same area as the HMI device 1610. If the terminal device 1630 exists in an area adjacent to or in the same area as the HMI device 1610, the message organizing unit 1624_2 will collect multiple information detected by the HMI device 1610 that multiple terminal devices exist in the adjacent area or the same area, and organize the multiple information into organized messages. In step S1608, the message organizing unit 1624_2 can provide the organized message to the device control unit 1622_3. In step S1609, the device control unit 1622_3 may receive the organized message provided by the message organization unit 1624_2, and transmit the organized message to the transmission module 1621 according to the message push schedule, and subscribe to the first dedicated communication channel for message transmission. In step S1610, the transmission module 1621 may transmit the organized message to the transmission module 1611 of the HMI device 1610 via the first dedicated communication channel. In step S1611, the transmission module 1611 may transmit the organized message to the message application unit 1613_1. The message application unit 1613_1 may classify the organized message and transmit the organized message to the application function module 1614, so that the user can achieve the function of monitoring and managing the terminal device 1330 by operating the application function module 1314 of the HMI device 1310. In step S1612, the message application unit 1613_1 may switch the original management device permission of the classification tag to the device connection unit 1612_2. And then, the IoT system 1600 may execute the above steps S1301 to S1333 of the embodiment of FIG. 13 again.

Therefore, the HMI device 1610 of the present embodiment can switch to the local transmission mode to use lower latency and lower power consumption to manage and control the terminal device 1630. In addition, after releasing the second dedicated communication channel, the terminal device 1630 can effectively reduce its power consumption.

FIG17 is a schematic diagram of the operation of the terminal device notification switching transmission mode of an embodiment of the present invention. Referring to FIG17, the IoT system 1700 includes an HMI device 1710, a cloud device 1720, and a terminal device 1730. The HMI device 1710 includes a transmission module 1711, a channel management module 1712, a data management module 1713, and an application function module 1714. The channel management module 1712 includes a channel allocation unit 1712_1, a device connection unit 1712_2, a channel scheduling unit 1712_3, and a scheduling unit 1712_4. The data management module 1713 includes a message application unit 1713_1 and a control request unit 1713_2.

The cloud device 1720 includes a transmission module 1721, an IoT device management module 1722, a storage module 1723, an HMI device management module 1724, and an application function module 1725. The IoT device management module 1722 includes a message classification unit 1722_1, a message monitoring unit 1722_2, and a device control unit 1722_3. The storage module 1723 includes a device data unit 1723_1, a device connection unit 1723_2, and a message buffer unit 1723_3. The HMI device management module 1724 includes a scheduling unit 1724_1 and a message organization unit 1724_2. The cloud device 1720 can communicate with the transmission module 1711 of the HMI device 1710 via the transmission module 1721 .

The terminal device 1730 includes a transmission module 1731, an IoT device management module 1732, a storage module 1733, an HMI device management module 1734, and an application function module 1735. The IoT device management module 1732 includes a message classification unit 1732_1, a message monitoring unit 1732_2, and a device control unit 1732_3. The storage module 1733 includes a device data unit 1733_1, a device connection unit 1733_2, and a message buffer unit 1733_3. The HMI device management module 1734 includes a scheduling unit 1734_1 and a message organization unit 1734_2. The terminal device 1730 can communicate with the transmission module 1711 of the HMI device 1710 via the transmission module 1731 .

In an embodiment of the present invention, the IoT system 1700 may execute the following steps S1701 to S1714 to further perform the operation of the terminal device notifying the switching of the transmission mode. In step S1701, when the terminal device 1730 is in the managed mode (i.e., the terminal device 1730 is managed by the HMI device 1710) and the transmission mode is the general communication channel mode, the message monitoring unit 1732_2 may monitor whether the HMI device 1710 does not connect to access the device data within the timeout period. If the HMI device 1710 does not connect to access the device data within the timeout period, then in step S1702, the message monitoring unit 1732_2 may request the device control unit 1732_3 to transmit a switching transmission mode request message to switch the transmission mode to the original mode and cancel the hosting. In step S1703, the device control unit 1732_3 transmits the switching transmission mode request message to the transmission module 1731. In step S1704, the transmission module 1731 transmits the switching transmission mode request message to the transmission module 1721. In step S1705, the transmission module 1721 transmits the switching transmission mode request message to the message classification unit 1722_1.

In step S1706, the message classification unit 1722_1 may classify the transmission mode switching request message and store the transmission mode switching request message in the device data unit 1723_1 and the device connection unit 1723_2 of the storage module 1723. In step S1707, the scheduling unit 1724_1 may determine the connection status between the terminal device 1730 and the HMI device 1710 through the device connection unit 1723_2. In step S1708, the scheduling unit 1724_1 may control the message organization unit 1724_2 according to the preset message push time schedule. The scheduling unit 1724_1 can monitor the device connection information of the HMI device 1710 stored in the device connection unit 1723_2 to generate a message push schedule. In step S1709, the message organization unit 1324_2 can read the above IoT message and other IoT messages corresponding to other terminal devices from the device data unit 1723_1, and perform message organization to generate an organized message.

The message organizing unit 1724_2 can organize the IoT messages of the terminal device 1730 stored in the device data unit 1723_1 to generate an organized message. In step S1710, the message organizing unit 1724_2 can provide the organized message to the device control unit 1722_3. In step S1711, the device control unit 1722_3 can receive the organized message provided by the message organizing unit 1724_2, and transmit the organized message to the transmission module 1721 according to the message push schedule, and subscribe to the first dedicated communication channel for message transmission. In step S1712, the transmission module 1721 may transmit the organized message to the transmission module 1711 of the HMI device 1710 via the first dedicated communication channel. In step S1713, the transmission module 1711 may transmit the organized message to the message application unit 1713_1. The message application unit 1713_1 may classify the organized message and transmit the organized message to the application function module 1714, so that the user can achieve the function of monitoring and managing the terminal device 1730 by operating the application function module 1714 of the HMI device 1710. In step S1714, the message application unit 1713_1 may switch the original management device permission of the classification tag to the device connection unit 1712_2 to set the HMI device 1710 to cancel the hosting. Therefore, the terminal device 1730 may enable the HMI device 1710 to resume the management of the terminal device 1730 via the cloud device 1720 via the second dedicated communication channel between the terminal device 1730 and the cloud device 1720.

In summary, the IoT system of the present invention can effectively control and monitor a large number of terminal devices under the scenario of a limited number of communication channels. The IoT system of the present invention can efficiently schedule and dynamically subscribe to the first communication channel to transmit the control command to the cloud device according to the priority order of the control command, and can dynamically release the first communication channel that completes the command transmission for the next control command. In addition, the IoT system of the present invention can also transmit the control command and emergency control command that have been timed out and not yet transmitted in the form of the request control instruction to be transmitted through a dedicated communication channel to effectively avoid control failure, data loss or control delay. In addition, the HMI device of the IoT system can switch to the local transmission mode to use lower latency and low power consumption to manage and control the terminal devices adjacent to the HMI device, rather than controlling the terminal devices through the cloud device. In addition, after releasing the second dedicated communication channel, the terminal device can also effectively reduce its power consumption.

Although the present invention has been disclosed as above by the embodiments, they are not intended to limit the present invention. Any person with ordinary knowledge in the relevant technical field can make some changes and modifications without departing from the spirit and scope of the present invention. Therefore, the protection scope of the present invention shall be defined by the scope of the attached patent application.

100, 200, 300, 400, 500, 600, 700, 1300, 1400, 1500, 1600, 1700: Internet of Things (IoT) systems 110, 210, 310, 510, 610, 710, 1110, 1310, 1410, 1510, 1610, 1710: Human Machine Interface (HMI) equipment 120, 220, 320, 420, 520, 620, 720, 1320, 1420, 1520, 1620, 1720: Cloud equipment 130_1, 130_2~130_N, 230, 330, 430, 530, 630, 730, 1330, 1430, 1530, 1630, 1730: terminal equipment 211, 221, 231, 311, 321, 331, 421, 431, 511, 521, 531, 611, 631, 711, 731, 801, 1111, 1311, 1321, 1331, 1411, 1421, 1431, 1511, 1521, 1531, 1611, 1621, 1631, 1711, 1721, 1731: transmission module 212, 312, 512, 612, 712, 1112, 1312, 1412, 1512, 1612, 1712: Channel management module 213, 313, 713, 1113, 1313, 1413, 1513, 1613, 1713: Data management module 214, 232, 314, 332, 432, 514, 532, 614, 632, 714, 732, 805, 1114, 1314, 1325, 1335, 1414, 1425, 1435, 1514, 1525, 1535, 1614, 1625, 1635, 1714, 1725, 1735: Application function module 222, 322, 622, 722: Terminal equipment management module 223, 323, 423, 623, 723, 803, 1323, 1333, 1423, 1433, 1523, 1533, 1623, 1633, 1723, 1733: Storage module 224, 324, 804, 1324, 1334, 1424, 1434, 1524, 1534, 1624, 1634, 1724, 1734: Human-machine interface (HMI) equipment management module 312_1, 512_1, 612_1, 712_1, 1112_3, 1312_3, 1412_3, 1512_3, 1612_3, 1712_3: Channel scheduling unit 312_2, 512_2, 612_2, 1112_1, 1312_1, 1412_1, 1512_1, 1612_1, 1712_1: Channel allocation unit 313_1, 513_1, 613_1, 713_1, 1113_1, 1313_1, 1413_1, 1513_1, 1613_1, 1713_1: Message application unit 313_2, 713_2, 1113_2, 1313_2, 1413_2, 1513_2, 1613_2, 1713_2: control request unit 322_1, 422_1, 622_1, 722_1, 802_1, 1322_1, 1332_1, 1422_1, 1432_1, 1522_1, 1532_1, 1622_1, 1632_1, 1722_1, 1732_1: message classification unit 322_2, 422_2, 622_2, 722_2, 802_2, 1322_2, 1332_2, 1422_2, 1432_2, 1522_2, 1532_2, 1622_2, 1632_2, 1722_2, 1732_2: message monitoring unit 322_3, 422_3, 622_3, 722_3, 802_3, 1322_3, 1332_3, 1422_3, 1432_3, 1522_3, 1532_3, 1622_3, 1632_3, 1722_3, 1732_3: equipment control unit 323_1, 423_1, 803_1, 1323_1, 1333_1, 1423_1, 1433_1, 1523_1, 1533_1, 1623_1, 1633_1, 1723_1, 1733_1: Equipment data unit 323_2, 423_2, 623_2, 723_2, 803_2, 1112_2, 1312_2, 1323_2, 1333_2, 1412_2, 1423_2, 1433_2, 1512_2, 1523_2, 1533_2, 1612_2, 1623_2, 1633_2, 1712_2, 1723_2, 1733_2: Equipment connection unit 323_3, 623_3, 723_3, 803_3, 1323_3, 1333_3, 1423_3, 1433_3, 1523_3, 1533_3, 1623_3, 1633_3, 1723_3, 1733_3: message register unit 324_1, 804_1, 1112_4, 1312_4, 1324_1, 1334_1, 1412_4, 1424_1, 1434_1, 1512_4, 1524_1, 1534_1, 1612_4, 1624_1, 1634_1, 1712_4, 1724_1, 1734_1: scheduling unit 324_2, 804_2, 1324_2, 1334_2, 1424_2, 1434_2, 1524_2, 1534_2, 1624_2, 1634_2, 1724_2, 1734_2: message organization unit 621, 721: transmission module 800: electronic equipment 802, 1322, 1332, 1422, 1432, 1522, 1532, 1622, 1632, 1722, 1732: IoT device management module S301~S312, S401~S408, S501~S510, S601~S621, S701~S721, S910~S960, S1010~S1040, S1210~S1250, S1301~S1333, S1401~S1415, S1501~S1524, S1601~S1612, S1701~S1714: Steps

FIG. 1 is a schematic diagram of an Internet of Things system of an embodiment of the present invention. FIG. 2 is a schematic diagram of an Internet of Things system of another embodiment of the present invention. FIG. 3 is an operation schematic diagram of a management terminal device of an embodiment of the present invention. FIG. 4 is an operation schematic diagram of monitoring Internet of Things messages of an embodiment of the present invention. FIG. 5 is an operation schematic diagram of an Internet of Things system of an embodiment of the present invention executing a general mode. FIG. 6 is an operation schematic diagram of an Internet of Things system of an embodiment of the present invention executing a timeout mode. FIG. 7 is an operation schematic diagram of an Internet of Things system of an embodiment of the present invention executing a delegation mode. FIG. 8 is a schematic diagram of an electronic device of an embodiment of the present invention. FIG. 9 is a flow chart of a message classification method of an embodiment of the present invention. FIG. 10 is a flow chart of a message monitoring method of an embodiment of the present invention. FIG. 11 is a schematic diagram of a human-machine interface device of an embodiment of the present invention. FIG. 12 is a flow chart of a channel allocation method of an embodiment of the present invention. FIG. 13 is a schematic diagram of an HMI device that actively switches the transmission mode of an embodiment of the present invention. FIG. 14 is a schematic diagram of the operation of a general communication channel mode of an embodiment of the present invention. FIG. 15 is a schematic diagram of the operation of a dedicated communication channel mode of an embodiment of the present invention. FIG. 16 is a schematic diagram of the operation of a cloud device notification switching transmission mode of an embodiment of the present invention. FIG. 17 is a schematic diagram of the operation of a terminal device notification switching transmission mode of an embodiment of the present invention.

800: Electronic equipment

801: Transmission module

802: IoT device management module

802_1: Message classification unit

802_2: Message monitoring unit

802_3: Equipment control unit

803: Storage module

803_1: Equipment data unit

803_2: Equipment connection unit

803_3: Message register unit

804: Human-machine interface (HMI) equipment management module

804_1: Scheduling unit

804_2: Message organization unit

805: Application function module

Claims (19)

An Internet of Things (IoT) system includes: a plurality of terminal devices, wherein each of the plurality of terminal devices includes at least a first device connection unit and a first message classification unit, wherein the first message classification unit stores a transmission mode switching request message in the first device connection unit, and further determines whether the plurality of terminal devices have a sub-terminal device; a cloud device, connected to the plurality of terminal devices in a communication manner, wherein the cloud device includes at least a device data unit, a second device connection unit and a second message classification unit, wherein the second message classification unit stores the transmission mode switching request message in the device data unit and the second device connection unit. and a human-machine interface (HMI) device, which is communicatively connected to the plurality of terminal devices via a plurality of first communication channels, and is communicatively connected to the cloud device via a first dedicated communication channel, wherein the human-machine interface device determines a subscription order according to priority information of a plurality of control commands, and schedules and dynamically subscribes to the first communication channel according to the subscription order, wherein the human-machine interface device determines whether the plurality of terminal devices are adjacent to the human-machine interface device, and transmits the switching transmission mode request message corresponding to the terminal device adjacent to the human-machine interface device to the cloud device via the first dedicated communication channel. The Internet of Things system as described in claim 1, wherein the terminal device that is determined to be adjacent to the human-machine interface device is located in the same communication area as the human-machine interface device. The IoT system as described in claim 1, wherein the human-machine interface device comprises: a channel management module, including: a device connection unit; a channel scheduling unit, including a command queue; and a first scheduling unit, for periodically determining the plurality of terminal devices supporting transmission mode switching by reading the device connection unit, and generating a low priority detection command to the command queue in the channel scheduling unit. The IoT system as described in claim 3, wherein the channel management module further comprises: a channel allocation unit, wherein the channel scheduling unit is used to calculate the subscription order according to the priority information of the control command, and the channel allocation unit is used to allocate the first communication channel according to the subscription order for the control command to be transmitted to be subscribed in sequence. The IoT system as described in claim 4, wherein the human-machine interface device further comprises: a transmission module for respectively determining whether the plurality of terminal devices are adjacent to the human-machine interface device, wherein the first scheduling unit further generates a high priority detection command to the command queue in the channel scheduling unit, so that the transmission module respectively determines again whether the terminal device is adjacent to the human-machine interface device, and transmits the switching transmission mode request message to the terminal device adjacent to the human-machine interface device via the first communication channel. The IoT system as described in claim 5, wherein each of the plurality of terminal devices further comprises: a first human-machine interface device management module; and a first IoT device management module, comprising: the first message classification unit, for receiving the transmission mode switching request message, and determining that the transmission mode switching request message must be responded to immediately. The IoT system as described in claim 6, wherein the first IoT device management module further includes a first device control unit, wherein when the plurality of terminal devices have the sub-terminal device, the first message classification unit responds to the human-machine interface device to execute a dedicated communication channel mode and enables the first human-machine interface device management module, wherein when the plurality of terminal devices do not have the sub-terminal device, the first message classification unit disables the first human-machine interface device management module, responds to the human-machine interface device from the first communication channel via the first device control unit that the request to switch the transmission mode has been completed, and interrupts a second dedicated communication channel between the cloud device and the terminal device. The IoT system as described in claim 7, wherein the first device control unit responds to the human-machine interface device with a proximal connection message, and the human-machine interface device notifies the cloud device management switch that has been completed. The IoT system as described in claim 8, wherein the proximal connection information includes a device unique code, a managed sub-terminal device, a communication channel information, a transmission mode information, and a time information of a previous control. The IoT system as described in claim 1, wherein the cloud device further includes: a second human-machine interface device management module, including: a second scheduling unit for monitoring the device connection information of the human-machine interface device stored in the second device connection unit to generate a message push schedule. The IoT system as described in claim 10, wherein the second human-machine interface device management module further includes: a message organization unit for organizing an IoT message stored in the second device data unit of the terminal device to generate an organized message. The IoT system as described in claim 11, wherein the second human-machine interface management module further comprises: a second device control unit for receiving the organized message provided by the message organization unit, and transmitting the organized message to the human-machine interface device via the first dedicated communication channel according to the message push schedule. The IoT system as described in claim 1, wherein the human-machine interface device comprises: a channel management module, comprising: a device connection unit; a channel scheduling unit, comprising a command queue; and a first scheduling unit, for reading information recorded in the device connection unit of a managed terminal device in a general communication channel mode and reaching the time when it should be controlled and managed, and generating a message acquisition command with a medium priority and transmitting the message acquisition command to the command queue in the channel scheduling unit. The IoT system as claimed in claim 1, wherein the human-machine interface device comprises: a channel management module, comprising: a channel scheduling unit, comprising a command queue; and an application function module, for transmitting an enable command or a disable command of a dedicated communication channel mode with a highest priority to the command queue of the channel scheduling unit, so that the channel scheduling unit subscribes to or releases the first dedicated communication channel connected to the plurality of terminal devices in a communication manner. The Internet of Things system as described in claim 1, wherein the cloud device includes: a second human-machine interface device management module, including: a message organization unit, used to determine whether the multiple terminal devices are adjacent to the human-machine interface device, wherein when the message organization unit determines that the multiple terminal devices are in an area adjacent to the human-machine interface device or in the same area as the human-machine interface device, the message organization unit is used to collect multiple information detected by the human-machine interface device that multiple terminal devices are in the adjacent area or the same area, and organize the multiple information into organized messages. The IoT system as claimed in claim 1, wherein at least one of the plurality of terminal devices comprises: an IoT device management module, comprising: a message monitoring unit, when at least one of the plurality of terminal devices is managed by the human-machine interface device and the transmission mode is a universal communication channel mode, the message monitoring unit is used to monitor whether the human-machine interface device has not been connected within a timeout period to access a device data. The Internet of Things system as described in claim 16, wherein when the message monitoring unit determines that the human-machine interface device has not been connected to access the device data within the timeout period, the at least one of the multiple terminal devices enables the human-machine interface device to resume management of the at least one of the multiple terminal devices via the cloud device via a second dedicated communication channel between the at least one of the multiple terminal devices and the cloud device. An Internet of Things system as described in claim 1, wherein the terminal device adjacent to the human-machine interface device is switched to be managed by the human-machine interface device instead of the cloud device. An Internet of Things system as described in claim 1, wherein the number of the plurality of terminal devices is greater than the number of the plurality of first communication channels.

Images