CN112929855B - Internet of things equipment binding method and system - Google Patents

Abstract

The present invention provides an Internet of Things device binding method and system. The method includes: receiving device information of the Internet of Things device; obtaining the user's setting information for the Internet of Things device; reacting to determining that the device information and setting information are in compliance with specifications, encoding them as device primary key codes; reacting to the The Internet-connected device is bound to the component, and corresponding attribute fields are generated for setting; in response to determining that the setting of the attribute fields has been completed, a specific description file associated with the IoT device is generated based on the device primary key code and attribute fields.

Description

Internet of Things device binding method and system

Technical field

The present invention relates to an Internet of Things device management mechanism, and in particular to an Internet of Things device binding method and system.

Background technique

With the development of science and technology and the evolution of the times, systems with services related to Internet of Things (IoT) devices, such as smart cities, smart buildings, and smart campuses, have become more and more popular.

However, since most systems involving IoT services need to centrally manage a large number of IoT devices, how to design a more efficient management mechanism is an important issue for those skilled in the art.

Contents of the invention

In view of this, the present invention provides an Internet of Things device binding method and system, which can be used to solve the above technical problems.

The invention provides an Internet of Things device binding method, which includes: receiving device values, signal types, device serial numbers and value times associated with the Internet of Things device from a device monitoring unit, where the Internet of Things device is connected to the device monitoring unit; obtaining the user The device project code, area information and device function type set for the Internet of Things device; in response to determining that the signal type, device serial number, device project code, area information and device function type are all in compliance with the specifications, the signal type, device serial number, device project The code, area information and device function type are encoded as the device primary key code associated with the IoT device; in response to the IoT device being bound to the new component located on the online dashboard, the corresponding device function type is generated based on the IoT device. Attribute fields are available for setting; in response to determining that the setting of the attribute fields of the new component has been completed, a specific description file associated with the IoT device is generated based on the device primary key code and attribute fields to complete the creation of new components and things. Binding operation of networked devices.

The invention provides an Internet of Things device binding system, which includes a device management module, a device binding module and a dashboard component management module. The device management module is configured to: receive the device value, signal type, device serial number and value time associated with the Internet of Things device from the device monitoring unit, where the Internet of Things device is connected to the device monitoring unit; obtain the user's settings for the Internet of Things device Equipment project code, area information and equipment function type; in response to determining that the signal type, equipment serial number, equipment project code, area information and equipment function type all comply with the specifications, the signal type, equipment serial number, equipment project code, area information and equipment function The type code is the device primary key code associated with the IoT device. The device binding module is configured to: respond to the IoT device being bound to the new component located on the online dashboard, and generate corresponding attribute fields for setting according to the device function type of the IoT device. The dashboard component management module is configured to: respond to the determination that the setting of the attribute fields of the new component has been completed, and generate a specific description file associated with the IoT device based on the device primary key code and attribute fields to complete the new component and Binding operation of IoT devices.

In order to make the above-mentioned features and advantages of the present invention more obvious and understandable, embodiments are specifically enumerated below and described in detail with reference to the attached drawings.

Description of the drawings

The accompanying drawings are included to provide a further understanding of the invention, and are incorporated in and constitute a part of this specification. The drawings illustrate embodiments of the invention and, together with the description, serve to explain the principles of the invention.

FIG. 1 is a schematic diagram of an Internet of Things system according to an embodiment of the present invention.

FIG. 2 is a flow chart illustrating an Internet of Things device binding method according to an embodiment of the present invention.

Figure 3 is a schematic diagram of a JSON description file and its bound dashboard components according to an embodiment of the present invention.

Detailed ways

In summary, the IoT device binding method and system of the present invention can bind the IoT device's monitoring point of the physical device to the screen element of the online dashboard through the unique project device primary key, thereby establishing a virtual virtualization of the physical IoT device. Doppelgänger. After adding components to the online dashboard, the user can then edit the location (drag), set the data format, set the alarm image switching, etc., and after the editing is completed, the virtual clone of the IoT device can be presented in the designated Online Dashboard Location. Therefore, users can learn relevant information about IoT devices from the online dashboard, allowing users to instantly check device usage, control device status, and obtain device alarm status. Details are as follows.

Please refer to FIG. 1 , which is a schematic diagram of an Internet of Things system according to an embodiment of the present invention. In this embodiment, the Internet of Things system 100 of the present invention includes an Internet of Things device binding system 10, the Internet 40, a device monitoring unit 50 and an Internet of Things device 60.

As shown in Figure 1, the IoT device binding system 10 may include a device status module 11, a device control module 12, a device alarm module 13, a dashboard screen module 14, a device data storage module 21, a device binding module 22, and device management. Module 31 and dashboard element management module 32, and their individual functions will be described in detail later.

In an embodiment of the present invention, the IoT device binding system 10 can be connected to the device monitoring unit 50 through the Internet 40 to receive information related to the IoT device 60 from the device monitoring unit 50, thereby implementing the method proposed by the present invention. IoT device binding method.

Please refer to FIG. 2 , which is a flow chart of an IoT device binding method according to an embodiment of the present invention. The method of this embodiment can be executed by the IoT device binding system 10 in Figure 1. The details of each step in Figure 2 will be described below with the components shown in Figure 1.

First, in step S210, the device management module 31 may receive the device value, signal type, device serial number and value time associated with the Internet of Things device 60 from the device monitoring unit 50. In different embodiments, the Internet of Things device 60 can be various sensors (such as temperature sensors, gas sensors, etc.), and its related device values can be sensed values, such as temperature, Gas concentration, etc., but may not be limited to this. In other embodiments, the Internet of Things device 60 may also be a controller or alarm with specific functions, but is not limited thereto. In addition, the signal types of the IoT device 60 may include analog in (AI), analog out (AO), digital in (DI), digital out (DO), etc. The device serial number may be the serial number of the Internet of Things device 60 , and the value acquisition time may be the time when the Internet of Things device 60 obtains the device value, but is not limited to this.

In an embodiment of the present invention, the Internet of Things device 60 can provide the above information to the device monitoring unit 50 regularly or irregularly after being connected to the corresponding device monitoring unit 50, and the device monitoring unit 50 can correspondingly provide the above information to the device monitoring unit 50 through the Internet. 40. Send the above information to the Internet of Things device binding system 10, but it may not be limited to this.

In one embodiment, the device value, signal type, device serial number and value time associated with the Internet of Things device 60 may be stored in the device data storage module 21 .

Afterwards, in step S220, the device management module 31 may obtain the device project code, area information and device function type set by the user for the Internet of Things device 60. In one embodiment, the IoT device binding system 10 can present an online dashboard through a user interface. In embodiments of the present invention, the online dashboard may include, for example, a map corresponding to a certain IoT service, and elements of various bound IoT devices belonging to the IoT service may be distributed on it. Moreover, this online dashboard can be used to allow users to add other IoT devices they want to bind.

Roughly speaking, assuming that the Internet of Things device 60 has not been bound and the user wants to perform a binding operation on it, the user can add a new component on the online dashboard. In one embodiment, the device management module 31 can organize the IoT devices that have not yet been bound into a form, so that when the user adds a component, the user can select the IoT device to be bound to the new component. In this case, the user can select the IoT device 60 from the above form and enter the information related to the IoT device 60 (such as the above-mentioned device project code, area information and device function type) to create the new component and the IoT device. The details of the correlation of the networked device 60 are as follows.

In the embodiment of the present invention, the device project code is, for example, the code of the project to which the Internet of Things device 60 belongs. The area information is, for example, information about the area where the Internet of Things device 60 is located. In one embodiment, the regional information may include larger-scale location information and finer spatial information. For example, if the above-mentioned IoT service corresponds to the campus, and the IoT device 60 is installed in a certain room of a certain building, the user can set the location information of the IoT device 60 to correspond to the above-mentioned building, and set The spatial information is set to correspond to the above-mentioned room, but the present invention is not limited thereto.

Additionally, different IoT devices can have different device functionality types. In the embodiment of the present invention, the device function type is, for example, one of a status type, a control type, and an alarm type, and can be set by the user according to the function type of the Internet of Things device 60 , but it is not limited thereto. For example, if the IoT device 60 is a sensor for detecting a certain environmental state (such as a temperature sensor), it can be set to belong to the state type. If the IoT device 60 is a controller used to control a certain object (for example, a window opening/closing controller), it can be set to belong to the control type. In addition, if the Internet of Things device 60 provides alarm sensing in response to a certain situation (such as a fire alarm), it can be set to belong to the alarm type, but the present invention is not limited thereto.

In one embodiment, after obtaining the signal type, device serial number, device project code, area information, and device function type input by the user, the device management module 31 can determine whether these information all comply with the specifications. . In one embodiment, the device management module 31 can determine whether any of the above information is null. If so, it can determine that the above information does not meet the specifications, and send a corresponding notification to remind the user to fill in the required information. On the other hand, if none of the above information is null, the device management module 31 determines that all the above information meets the specifications, and continues to execute step S230.

In step S230, in response to determining that the signal type, equipment serial number, equipment project code, area information and equipment function type all comply with the specifications, the equipment management module 31 can combine the signal type, equipment serial number, equipment project code, area information and equipment function type. The code is a device primary key code associated with the Internet of Things device 60 . In one embodiment, the device primary key code of the Internet of Things device 60 can be characterized as:

{ProjectID},{LocationID},{RoomID},{DeviceType},{MonitorType},{SerialNum}, where ProjectID is the device project code, LocationID is the location code, RoomID is the space code, DeviceType is the device function type, and MonitorType is the number Type, SerialNum is the device serial number. In short, the device management module 31 can convert the signal type, device serial number, device project code, area information and device function type into the device master key code in the above format, but the invention is not limited thereto.

In one embodiment, the device management module 31 can integrate device primary key codes that have not been bound to any IoT device into a primary key form. Then, when the user adds a new component to the online dashboard, the device management module 31 can provide the above-mentioned primary key form to the user for the user to select the device primary key code to be bound to the new component, but it is not limited to this.

Afterwards, in step S240, in response to the IoT device 60 being bound to the new element on the online dashboard, the device binding module 22 can generate corresponding attribute fields according to the device function type of the IoT device 60. set up.

In one embodiment, after the IoT device 60 (the device primary key code) is bound to a new component, the device binding module 22 can generate the corresponding attribute field according to the device function type of the IoT device 60 for setting. Specifically, as described in the previous embodiment, the device function type of the Internet of Things device 60 may be one of a status type, a control type, and an alarm type. In one embodiment, if the device function type of the Internet of Things device 60 belongs to the status type, the device binding module 22 can provide the status value display format, number of decimal points, value unit, and value name as corresponding attribute fields for setting. . For example, if the Internet of Things device 60 is a thermometer, the device binding module 22 can, after confirming that it belongs to the status type, allow the user to set the display format of the temperature value, the number of decimal points (such as one decimal place), and the value unit accordingly. (such as Celsius), numerical name (such as "temperature value"), but it is not limited to this.

In another embodiment, if the device function type of the Internet of Things device 60 belongs to the control type, the device binding module 22 can provide the control action name represented by the specified value as the corresponding attribute field for setting. For example, if the Internet of Things device 60 is a controller of a window switch, the device binding module 22 can, after confirming that it belongs to the control type, allow the user to set a control action corresponding to a specified value, for example, 1 means opening the window. , 0 means closing the window, etc., but it is not limited to this.

In another embodiment, if the device function type of the Internet of Things device 60 belongs to the alarm type, the device binding module 22 can provide daily pictures, alarm pictures, alarm sounds, and alarm notification forms as corresponding attribute fields for setting. For example, if the Internet of Things device 60 is a fire alarm, the device binding module 22 can, after confirming that it belongs to the alarm type, correspondingly allow the user to select a normal picture representing no fire detected or an alarm picture representing a detected fire. , the alarm sound of a detected fire, and the form of alarm notification of a detected fire (such as sending an email to one or more designated mailboxes and/or sending a mobile phone message to one or more designated numbers, etc.), but it is not limited to this.

Next, in step S250, in response to determining that the setting of the attribute fields of the newly added component has been completed, the dashboard component management module 32 can generate a specific description file associated with the Internet of Things device 60 based on the device primary key code and the attribute fields. To complete the binding operation of the new component and the Internet of Things device 60. In one embodiment, the specific description file associated with the Internet of Things device 60 may be a JSON description file including signal type, device serial number, device project code, area information, device function type and attribute fields, but the invention is not limited thereto. . In other embodiments, the designer can select the required description file format according to the needs, and is not limited to JSON files.

In one embodiment, after the user adds an element to the online dashboard, the element can be dragged on the map to a location corresponding to the IoT device to display the location of the IoT device in the actual environment.

In addition, in embodiments of the present invention, users can bind multiple IoT devices to multiple elements of the online dashboard according to the above teachings at one time. Moreover, after the user confirms that the required binding operation has been completed, the dashboard component management module 32 can generate a JSON description file accordingly, including a description of the location of each component newly added to the dashboard on the online dashboard, and its binding. A certain device, the format of its display value, the action name represented by each value, the normal picture it displays, the alarm picture, the text it displays, the picture it displays when it alarms, the details of its alarm notification, etc.

In order to make the above concepts easier to understand, Figure 3 is supplemented below for further explanation. Please refer to FIG. 3 , which is a schematic diagram of a JSON description file and its bound dashboard components according to an embodiment of the present invention. In this embodiment, it is assumed that the JSON description file 700 includes three description file components 701, 702, and 703, which correspond to three different IoT devices, and the dashboard components 801, 802, and 803 are user-specific components corresponding to these IoT devices. Devices and new components on the online dashboard. In Figure 3, each description file component 701-703 has similar fields, so only the meaning of each field in the description file component 701 will be explained below. Those skilled in the art should be able to understand the description file components 702 and 703 accordingly. The meaning of each field. Specifically, as can be seen from Figure 3, the description file component 701 includes a device primary key encoding field (ie, "PK"), which includes ProjectID (for example, "A1", which may represent the corresponding project name), LocationID (for example, "A1", which may represent the corresponding project name), LocationID (for example, "PK"), "TC", which can represent the location), RoomID (such as "1", which can represent the space), DeviceType (such as "status", which can indicate that the IoT device belongs to the status type), MonitorType (such as "AI", It can represent the signal type as analog input) or SerialNum (such as "8988.1163.1955.8237"). In addition, the description file component 701 also includes value (for example, "30", which is the corresponding device value) and time (for example, "2019-08-01T13:13:11.123Z", which is the value time), but is not limited to this.

In one embodiment, the dashboard screen module 14 can read the JSON description file 700 in the future, and then restore the online dashboard according to the location and bound device described in the content. In this case, when the user uses the online dashboard, the dashboard screen module 14 can obtain the latest device status for the user to query through the device status module 11 according to the type of components in the screen, obtain the device value through the device control module 12 and Control the device and/or obtain the latest alarm information through the device alarm module 13 and present it on the dashboard.

In summary, the present invention allows users to create the required online dashboard screen by themselves, and can add, modify, and delete Internet of Things devices on the online dashboard through the device primary key binding mechanism, allowing users to focus on The devices you care about reduce the complexity of the user interface and improve the ease of use of the system. In addition, the present invention allows users to check the status of equipment on a self-created online dashboard, making it more convenient and faster to know the real-time status of equipment at a specific location and improving management efficiency. Moreover, the present invention allows users to control the status of equipment at a specific location on a self-created online dashboard, making it more intuitive and convenient to change the status of equipment, reduce the risk of controlling incorrect equipment, and improve operation and management efficiency.

The invention allows users to obtain the equipment alarm status of a specific location on a self-created online dashboard, and can more quickly find equipment that issues abnormal alarms and perform maintenance operations immediately.

Finally, it should be noted that the above embodiments are only used to illustrate the technical solution of the present invention, but not to limit it. Although the present invention has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that: The technical solutions described in the foregoing embodiments can still be modified, or some or all of the technical features can be equivalently replaced; and these modifications or substitutions do not deviate from the essence of the corresponding technical solutions from the technical solutions of the embodiments of the present invention. scope.

Claims (9)

1. An Internet of Things device binding method, characterized by including: Receive the device value, signal type, device serial number and value time associated with the Internet of Things device from the device monitoring unit, where the Internet of Things device is connected to the device monitoring unit; Obtain the device project code, regional information and device function type set by the user for the Internet of Things device; In response to determining that the signal type, the equipment serial number, the equipment project code, the area information and the equipment function type all comply with the specifications, the signal type, the equipment serial number, the equipment project code, The area information and the device function type code are device primary key codes associated with the Internet of Things device; In response to the IoT device being bound to the new component located on the online dashboard, corresponding attribute fields are generated for setting according to the device function type of the IoT device; In response to determining that the setting of the attribute field of the new component has been completed, a specific description file associated with the Internet of Things device is generated based on the device primary key code and the attribute field to complete the new Add the binding operation between the component and the IoT device. 2. The method according to claim 1, characterized in that the device value, the signal type, the device serial number and the value time of the Internet of Things device are obtained from the device monitoring unit. The Internet of Things device. 3. The method according to claim 1, characterized in that, in response to determining that the signal type, the equipment serial number, the equipment project code, the area information and the equipment function type are all non-null values , it is determined that the signal type, the equipment serial number, the equipment project code, the area information and the equipment function type all comply with the specification. 4. The method according to claim 1, characterized in that the area information includes a location code and a space code corresponding to the Internet of Things device, and the device primary key encoding is represented by: {ProjectID},{LocationID},{RoomID},{DeviceType},{MonitorType},{SerialNum} Wherein ProjectID is the device project code, LocationID is the location code, RoomID is the space code, DeviceType is the device function type, MonitorType is the number type, and SerialNum is the device serial number. 5. The method of claim 1, wherein the step of generating corresponding attribute fields for setting according to the device function type of the Internet of Things device includes: If the device function type of the Internet of Things device belongs to the status type, the status value display format, number of decimal points, value unit, and value name are provided as corresponding attribute fields for setting. 6. The method of claim 1, wherein the step of generating corresponding attribute fields for setting according to the device function type of the Internet of Things device includes: If the device function type of the Internet of Things device belongs to the control type, the control action name represented by the specified value is provided as the corresponding attribute field for setting. 7. The method according to claim 1, wherein the step of generating corresponding attribute fields for setting according to the device function type of the Internet of Things device includes: If the device function type of the Internet of Things device belongs to an alarm type, daily pictures, alarm pictures, alarm sounds, and alarm notification forms are provided as corresponding attribute fields for setting. 8. The method of claim 1, wherein the specific description file associated with the Internet of Things device includes the signal type, the device serial number, the device project code, and the area information. , the JSON description file of the device function type and the attribute field. 9. An Internet of Things device binding system, characterized by including: A device management module configured to: Receive the device value, signal type, device serial number and value time associated with the Internet of Things device from the device monitoring unit, where the Internet of Things device is connected to the device monitoring unit; Obtain the device project code, regional information and device function type set by the user for the Internet of Things device; In response to determining that the signal type, the equipment serial number, the equipment project code, the area information and the equipment function type all comply with the specifications, the signal type, the equipment serial number, the equipment project code, The area information and the device function type code are device primary key codes associated with the Internet of Things device; A device binding module configured to: In response to the IoT device being bound to the new component located on the online dashboard, corresponding attribute fields are generated for setting according to the device function type of the IoT device; A dashboard element management module configured to: In response to determining that the setting of the attribute field of the new component has been completed, a specific description file associated with the Internet of Things device is generated based on the device primary key code and the attribute field to complete the new Add the binding operation between the component and the IoT device.