A method for easily expanding integrated drive under internet of things

Abstract

The application discloses a method for easily expanding integrated driving under the Internet of Things, and the method comprises the following steps: constructing a driving management framework in an Internet of Things platform, developing a new self-defined protocol matched with the type of field equipment according to a self-defined protocol package module, packing the new self-defined protocol into a jar package, uploading the jar package to the driving management framework to register the self-defined protocol, and supporting the new self-defined protocol and the equipment supporting the new self-defined protocol after the registration is successful. The application has the characteristics of effectively improving the expansibility.

Description

TECHNICAL FIELD

[0001] The application relates to an Internet of Things program driving method, in particular to an easy-to-expand integrated driving method under the Internet of Things. BACKGROUND

[0002] The driving part in the Internet of Things lacks unified standards, and different protocols need to be developed for connecting different types of devices. At present, many self-defined protocols are put into a protocol package for calling by the Internet of Things program or directly written into the Internet of Things program. Both of the two methods lack a certain expansibility, and are a relatively good solution for driving management under the premise that the connected devices are stable and unchanged. However, in most cases, when many Internet of Things projects are deployed to the field for implementation, new device types are encountered, and the existing Internet of Things program of the company does not support the driving. In this case, the company has to choose to customize development or cut off the access of the device. If the company chooses to customize development, it is difficult to guarantee that the program can be directly put into use after development, which may be another risk that causes the business of the company to be delayed. If the company chooses to cut off the access of the device, the development of the company will be hindered, the income will be reduced, and it is also difficult to guarantee that the next customer will not have new devices. Obviously, both of the two methods are not perfect for the development of the company or the development of the Internet of Things industry. Therefore, the existing technology has the problem of poor expansibility. SUMMARY

[0003] The application aims to provide an easy-to-expand integrated driving method under the Internet of Things. The application has the characteristics of effectively improving the expansibility.

[0004] The technical scheme of the application is an easy-to-expand integrated driving method under the Internet of Things. A driving management framework is constructed in the Internet of Things platform, a new self-defined protocol is developed according to the type of the field device by a self-defined protocol package module, and the new self-defined protocol is packed into a jar package and uploaded to the driving management framework for registration of the self-defined protocol. After successful registration, the Internet of Things platform supports the new self-defined protocol and can also access the devices supported by the new self-defined protocol.

[0005] In the foregoing easy-to-expand integrated driving method under the Internet of Things, the driving management framework comprises a protocol registration module, a protocol management module, a message distribution module, a network component module, a device binding module and a data underlay module.

[0006] In the foregoing easy-to-expand integrated driving method under the Internet of Things, the driving management framework is further provided with a device authentication interface, a message encoding and decoding interface, a message sending interceptor interface, a configuration metadata interface, a network component interface and a device binding interface.

[0007] The method for easy expansion and integrated driving under the Internet of Things further includes a self-defined protocol package module.

[0008] The method for easy expansion and integrated driving under the Internet of Things further includes a self-defined protocol package module.

[0009] The method for easy expansion and integrated driving under the Internet of Things further includes a specific operation process of the driving management framework.

[0010] 1) Registration of a new self-defined protocol: After receiving the jar package, the driving management framework determines whether the jar package is a new protocol package. If the jar package is a new protocol package, the driving management framework adds and publishes the new protocol package. Otherwise, the driving management framework updates an existing protocol package and republishes the updated protocol package. The registration of the jar package in the driving management framework is completed, and the driving management framework manages the jar package.

[0011] 2) Creation of product information in the driving management framework: According to the information of the jar package, a driving used by the product is selected, and a thing model of the product is configured and published, so that the creation of the product information is completed.

[0012] 3) Addition of a new device: The product information is used to add the new device, and a bit number attribute of the device depends on the thing model in the product information. After the new device is added, the device reports an online event on the Internet of Things platform. The driving management framework calls a corresponding device protocol to authenticate the device, decodes a message, and reports data to the Internet of Things platform through a network component module. Thus, the device is authenticated on the Internet of Things platform and changes to an online state.

[0013] After the device is online, the device reports a bit number attribute value at irregular time intervals. The driving management framework calls a corresponding device protocol to decode a message and reports data to the Internet of Things platform through a network component module. The device is bound, and attribute information of a thing model of a product corresponding to the device is bound to the bit number attribute value reported by the device. After the binding is successful, the attribute value of the device is stored in a time series database.

[0014] For a device supporting data underwriting, the Internet of Things program writes a to-be-modified bit number into a modification value through a unified message format of a platform, and sends the modification value to a corresponding self-defined protocol module through a network component module. After the self-defined protocol module decodes the message, the self-defined protocol module underwrites data to the corresponding device through a communication protocol between the self-defined protocol module and the device.

[0015] Compared with the prior art, the application builds a drive management framework in the Internet of Things platform, and develops a new custom protocol matched with the type of field equipment through a custom protocol package module, and packs it into a jar package, uploads it to the drive management framework for registration of the custom protocol; after successful registration, the Internet of Things platform supports the new custom protocol, and can also access the equipment supported by the new custom protocol, achieves unified management of the drive protocol, and does not need to change the Internet of Things program when developing a new protocol, greatly improves the expansibility of the protocol. After using the method for easily expanding integrated drive of the application, the company only needs to embed the necessary and known drive protocol of the company, without deliberately expanding the range of the supported protocol, avoids the phenomenon of high or low, can greatly reduce the enterprise investment cost, and shortens the business expansion period. Meanwhile, the application also achieves registration and uninstallation of the drive protocol at any time, temporary storage of data when the equipment is offline, continues to use after the equipment is online, and can directly add online in the production environment without pre-development of the drive protocol. The method has low invasion to the original program architecture, does not affect the original process, can develop different equipment protocols according to the actual situation, can uninstall the registered protocol according to the situation, has high expansibility. In summary, the application has the characteristics of effectively improving the expansibility. BRIEF DESCRIPTION OF DRAWINGS

[0016] Figure 1 is a flowchart of introducing a custom protocol package into the Internet of Things platform by the application;

[0017] Figure 2 is a block diagram of the drive management framework. DETAILED DESCRIPTION

[0018] The application will be further described below in combination with the drawings and examples, but is not used as the basis for limiting the application.

[0019] Example. A method for easily expanding integrated drive under the Internet of Things, constitutes as shown in Figure 1 and 2 , a drive management framework is built in the Internet of Things platform, a custom protocol package module develops a new custom protocol matched with the type of field equipment, and packs it into a jar package, uploads it to the drive management framework for registration of the custom protocol; after successful registration, the Internet of Things platform supports the new custom protocol, and can also access the equipment supported by the new custom protocol.

[0020] The drive management framework includes a protocol registration module, a protocol management module, a message distribution module, a network component module, a device binding module and a data underlay module.

[0021] The drive management framework is further provided with a device authentication interface, a message encoding and decoding interface, a message sending interceptor interface, a configuration metadata interface, a network component interface and a device binding interface.

[0022] The custom protocol package module comprises a device authentication unit, a message decoding unit, a message sending interceptor unit and a configuration metadata unit.

[0023] Custom process of the custom protocol package module: when a new device protocol needs to be connected, the interface implementation of the device authentication, message encoding and decoding and message interceptor conforming to the specification is added in the custom protocol package module, packed into a jar package and uploaded to the drive management framework for registration.

[0024] The specific operation process of the drive management framework is as follows:

[0025] 1) Registration of a new custom protocol: after receiving the jar package, the drive management framework judges whether the jar package is a new protocol package, if yes, a new protocol package is added and published on the drive management framework, otherwise, the existing protocol package is updated and republished, the registration of the jar package in the drive management framework is completed, and the drive management framework will manage the jar package;

[0026] 2) Creation of product information in the drive management framework: according to the information of the jar package, the drive to be used by the product is selected, then the physical model of the product is configured and published, and the creation of the product information is completed;

[0027] 3) Addition of a new device: the created product information is used to complete the addition of a new device, the bit number attribute of the device depends on the physical model in the product information; after the addition and creation of the new device, the device reports an online event on the Internet of Things platform, the drive management framework calls the corresponding device protocol to authenticate the device, decodes the message after the authentication is successful, and reports the data to the Internet of Things platform through the network component module, thus, the device completes the authentication in the Internet of Things platform and the state is changed to online.

[0028] After the device is online, the bit number attribute value of the device is reported at irregular time intervals, the message is decoded through the drive management framework calling the corresponding device protocol, and the data is reported to the Internet of Things platform through the network component module, the device binding is performed, the attribute information of the physical model of the corresponding product of the device is bound with the bit number attribute value reported by the device one by one, after the successful binding, the device attribute value is stored in a time series database.

[0029] For the device supporting data underlay, the Internet of Things program can write the to-be-modified bit number into the modification value through the unified message format of the platform, send the modification value to the corresponding custom protocol module through the network component module, decode the message after the custom protocol module, and underlay the data to the corresponding device through the communication protocol between the custom protocol module and the device.

[0030] IoT Platform: An integrated platform encompassing device management, secure data communication, and message subscription capabilities. It supports connecting massive numbers of devices and uploading device data to the cloud; it provides cloud APIs, allowing servers to send commands to devices for remote control.

[0031] Product: A collection of devices, typically referring to a group of devices with the same function. The IoT platform issues a globally unique ProductKey to each product.

[0032] Device: A specific device belonging to a particular product. The IoT platform issues a unique certificate, DeviceName, to each device within the product.

[0033] Item model: This is a functional description of a device in the cloud, including its attributes, services, and events. IoT platforms describe item models using a defined language called TSL (Thing Specification Language), which is in JSON format. Data from the reported devices can be assembled based on the TSL.

[0034] Attributes: One of the functional models of a device, generally used to describe the device's operational state, such as the current ambient temperature read by an environmental monitoring device. Attributes support GET and SET request methods. Application systems can initiate requests to read and set attributes.

[0035] JAR file: A file packaged from a Java Web project that can be called by other programs or run independently.

[0036] The process of customizing a new custom protocol:

[0037] When a protocol other than the program's default protocol is required and the device protocol is already determined and cannot be modified, a custom protocol needs to be developed for access. As the company's technology accumulates and develops, the number of custom protocols will increase. The traditional method of deploying each protocol as a program becomes increasingly cumbersome and error-prone, lacking unified management. However, after using this method, all custom protocols can be managed in the management page of the driver management framework. Compared with the past, all supported protocols can be viewed more clearly and are easier to manage, while still retaining the protocol's ability to interface with devices.

[0038] After developing the driver framework, when authenticating a specified device, the new custom protocol belongs to different network types. The request type can be converted to the corresponding type according to the actual situation. A device operation interface is provided, through which the device configuration and device configuration information can be obtained.

[0039] After the device authentication is successful, if the device message is sent to the Internet of Things platform, the message needs to be sent to the custom protocol package module first. The program in the custom protocol package module will convert the message into a unified message format of the platform by calling the corresponding message encoder and decoder, and send it to the platform through the network component. If the platform needs to send a message to a specified device, it sends the message to the program in the custom protocol package module through the network component. The custom protocol package module calls the corresponding message encoder and decoder to process the message, and sends it to the device after processing;

[0040] Using the message sending interceptor can intercept the message sending and returning actions, and realize custom logic by modifying parameters and other operations, such as: when the device is offline, cache the message in the device configuration, and resend when the device is online;

[0041] The configuration metadata is used to tell the Internet of Things platform that some custom configurations need to be added to the device configuration when using this protocol, and can be obtained through the corresponding method in other places;

[0042] After the above steps are completed, the new custom protocol is packaged into a jar package, uploaded and registered in the management page of the driver management framework, and after verification, the platform supports the protocol, and the device supported by the custom protocol can also be accessed.

[0043] The management process of the driver management framework is as shown in Figure 1

[0044] The driver management framework provides device authentication, message encoding and decoding, message interceptor, and configuration metadata interfaces for custom protocol implementation, and provides implementation specifications;

[0045] In the case of stable operation of the Internet of Things program, if the developer needs to connect a new device protocol, the device authentication, message encoding and decoding, and message interceptor interface implementation conforming to the specification need to be added in the custom protocol package. After being packaged into a jar package, the protocol package is uploaded to the driver management page of the Internet of Things. At this time, it needs to be judged whether the protocol package is a new package. If it is a new package, it is added and published in the driver management. Otherwise, update the existing protocol and republish. At this time, the protocol package has been registered to the driver management framework and managed by the driver management framework;

[0046] When creating a product, select the driver that needs to be used by this product, and then configure the thing model of this product and publish it. At this time, the product has met the use standard of the Internet of Things, and a new device is created using this product. The bit number attribute of the device depends on the thing model of the product and cannot be expanded alone. It can only be expanded by re-publishing after editing the thing model on the product side;

[0047] ​After the new device is created, the device reports its online event on the platform, the drive management framework calls the corresponding device protocol to authenticate it, decodes the message after successful authentication, and reports the data to the platform through the basic network component. At this point, the device completes the authentication in the Internet of Things program and the status changes to online.

[0048] After the device is online, it will report its bit number attribute value at irregular intervals. At this time, the drive management framework also needs to call the corresponding device protocol to decode the message and report the data to the platform through the basic network component. However, since the bit number attribute value of the device is still in a scattered state, the device time sequence value cannot be stored at this time. Therefore, the drive management framework provides a bit number attribute page for device binding. The attribute information of the product model corresponding to the device is bound one by one with the bit number attribute value reported by the device. After successful binding, the device attribute value is stored using a time sequence database.

[0049] For devices that support data underlay, the Internet of Things program can write the to-be-modified bit number into the modification value through the platform unified message format, send it to the corresponding custom protocol through the basic network component, decode the message, and use the device's own communication protocol to underlay the data to the corresponding device.

[0050] The composition of the drive management framework is shown in Figure 2 For custom protocols that meet the specifications, the drive management framework provides six major functions: protocol registration, protocol management, message distribution, network components, device binding, and data underlay. Protocol registration ensures that the protocols registered with the drive management framework meet the implementation specifications. Protocol management controls the release and deletion of protocols, allowing protocols to be used as plug-ins. Message distribution selects the corresponding protocol for interaction during device and Internet of Things program interaction by creating a protocol when the product is preset. Network components provide the ability for custom protocols to communicate with the drive management framework. Device binding makes data upload and underlay more secure and reliable. The value of the unbound bit number attribute will be discarded. Data underlay enables the Internet of Things program to control the device, allowing the program to be more useful in real life.

[0051] The drive management framework based on this method has low invasiveness to the original program architecture and does not affect the original process. Different device protocols can be developed according to actual conditions, and registered protocols can be unloaded according to conditions, with high expandability.

Claims

1. A method for easily expandable and integrated driving in the Internet of Things, characterized in that: By constructing a drive management framework in the Internet of Things platform, a new custom protocol is developed according to the type of the field device, and is packed into a jar package and uploaded to the drive management framework for registration of the custom protocol; after successful registration, the Internet of Things platform supports the new custom protocol and can access the device supported by the new custom protocol; The specific operation process of the drive management framework is as follows: 1) Registration of the new custom protocol: after receiving the jar package, the drive management framework judges whether the jar package is a new protocol package, if it is a new protocol package, a new one is added and published on the drive management framework, otherwise, the existing protocol package is updated and republished, the registration of the jar package in the drive management framework is completed, and the drive management framework will manage the jar package; 2) Create product information in the drive management framework: according to the information of the jar package, first select the drive to be used by the product, then configure the thing model of the product and publish it, and complete the creation of the product information; 3) Add new device: use the created product information to complete the addition of the new device, the bit number attribute of the device depends on the thing model in the product information; after the new device is added and created, it reports its online event on the Internet of Things platform, the drive management framework calls the corresponding device protocol to authenticate it, decodes the message after successful authentication, and then reports the data to the Internet of Things platform through the network component module, thus the device completes the authentication in the Internet of Things platform and the state changes to online. 2.The method of claim 1, wherein: The drive management framework includes a protocol registration module, a protocol management module, a message distribution module, a network component module, a device binding module and a data downlink module.

3. The method of claim 1, wherein: The drive management framework also has a device authentication interface, a message encoding and decoding interface, a message sending interceptor interface, a configuration metadata interface, a network component interface and a device binding interface.

4. The method of claim 1, wherein: The custom protocol package module includes a device authentication unit, a message decoding unit, a message sending interceptor unit and a configuration metadata unit.

5. The method of claim 4, wherein: Custom process of the custom protocol package module: when a new device protocol needs to be connected, add the interface implementation of the device authentication, message encoding and decoding, and message interceptor in the custom protocol package module according to the specification, pack it into a jar package, and upload it to the drive management framework for registration.

6. The method of claim 1, wherein: After the device is online, it will report its bit number attribute value at irregular intervals, which is decoded by the drive management framework calling the corresponding device protocol and reported to the Internet of Things platform through the network component module for device binding. The attribute information of the thing model of the corresponding product of the device is bound one by one with the bit number attribute value reported by the device, and after successful binding, the device attribute value is stored in a time series database.

7. The method of claim 1, wherein: For devices supporting data downlink, the Internet of Things program can write the to-be-modified bit number into the modification value through the platform's unified message format, send it to the corresponding custom protocol module through the network component module, and after decoding the message, downlink the data to the corresponding device through the communication protocol between the custom protocol module and the device.

Images