Internet of Things system

Abstract

This application relates to an Internet of Things (IoT) system, including: an IoT device module, a front-end routing module, and a server module. By binding the IP of the front-end router to the IoT device, and through the parsing and forwarding of the front-end router, it can be connected to different privately deployed server platforms. Compared with the prior art, there is no need to manually configure the server IP address, saving workload. Additionally, if the IoT device is updated, the front-end router can also perform protocol parsing and conversion and then forward it to the corresponding server, enabling the IoT system to support access to more different IoT devices and having wide applicability.

Description

Technical Field

[0001] This application relates to the field of Internet of Things technology, and particularly to an Internet of Things system. Background Art

[0002] Under strict restrictions on the use of Internet of Things cards, the Internet of Things cards need to be bound to an IP or use general traffic. For Internet of Things devices to connect to different servers, the Internet of Things card needs to be unbound and then bound to the IP address of the new server.

[0003] In the configuration and use of the server address of Internet of Things devices, such as the single-lamp controller of LED street lights, the private server of the single-lamp controller purchased by the user needs to be deployed to its own server. At this time, the server address of the LED street light single-lamp controller needs to be reconfigured. Currently, most of the configuration information of Internet of Things devices connecting to the server uses serial ports and WEB configuration.

[0004] Serial port configuration usually requires preparing wires such as USB to 485 / TTL, and then cooperating with serial port software or configuration tools for configuration. Moreover, the Internet of Things card needs to be bound to the configured server IP address. When using this configuration method for a large number of Internet of Things devices, the workload is large and it is easy to make mistakes during configuration.

[0005] The configuration method of the WEB page has the main advantage of being convenient to use. The configuration computer does not need to install any software, and only needs to use a browser to configure the device. This configuration method also needs to bind the new server IP to the Internet of Things card. In the configuration of a large number of devices, there are also problems of large workload and easy configuration errors. Summary of the Invention

[0006] This application provides an Internet of Things system to solve the problem in the prior art that when Internet of Things devices connect to different servers, they need to bind the corresponding server IP address, resulting in a large workload and easy errors.

[0007] In a first aspect, this application provides an Internet of Things system, which includes: an Internet of Things device module, a front-end routing module, and a server module.

[0008] The Internet of Things device module includes at least one Internet of Things device;

[0009] The front-end routing module includes a front-end router and a front-end routing management platform. The server IP address of the Internet of Things device is configured through the front-end routing management platform, and different Internet of Things devices correspond to different server IP addresses;

[0010] The server module includes an upstream server and a device server;

[0011] Among them, the IP address of the pre-routing is bound to the IoT device, and the IoT device is connected to the corresponding server through the pre-routing. The server of the IoT device is deployed on its own device server, and the upstream server is a cloud server.

[0012] Further, the pre-routing management platform has a page configuration function, and the IP address and port information of the upstream server are added through the page of the pre-routing management platform.

[0013] Further, the IoT system further includes a configuration database, which stores the UID of the IoT device, the IP address and port information of the upstream server, and the UID of the IoT device and the protocol conversion script in an associated manner in the configuration database.

[0014] Further, the login information of the IoT device is sent to the pre-routing, and the pre-routing matches the corresponding server for the IoT device according to the query result of the configuration database, where the login information includes the IoT device UID.

[0015] Further, the login information of the IoT device is sent to the pre-routing, and the pre-routing matches the corresponding server for the IoT device according to the query result of the configuration database, including:

[0016] If the pre-routing queries the corresponding upstream server information in the configuration database according to the IoT device UID in the login information, then parse the data format of the login information;

[0017] Judge whether communication protocol conversion is required according to the data format parsing result;

[0018] If not, connect the IoT device to the upstream server, and the upstream server then connects the IoT device to the corresponding device server.

[0019] Further, after judging whether communication protocol conversion is required according to the data format parsing result, it further includes:

[0020] If required, match the corresponding protocol conversion script in the configuration database according to the IoT device UID;

[0021] Connect the IoT device to the upstream server based on the protocol conversion script, and the upstream server then connects the IoT device to the corresponding device server.

[0022] Further, judging whether communication protocol conversion is required according to the data format parsing result includes:

[0023] Judge whether the current Internet of Things device is a newly added device to the system according to the data format parsing result;

[0024] If it is a newly added device, communication protocol conversion is required;

[0025] If it is not a newly added device, communication protocol conversion is not required.

[0026] Furthermore, the judging whether the current Internet of Things device is a newly added device to the system according to the data format parsing result includes:

[0027] Judge whether it is a preset data format according to the data format parsing result;

[0028] If so, it is determined that the current Internet of Things device is not a newly added device to the system;

[0029] If not, it is determined that the current Internet of Things device is a newly added device to the system.

[0030] Furthermore, in the Internet of Things system, if the login information of the logged-in Internet of Things device is different from the historical login information recorded in the system, then the Internet of Things device is a newly added device to the system.

[0031] Furthermore, the login information of the Internet of Things device is sent to the front-end router, and the front-end router matches a corresponding server for the Internet of Things device according to the query result of the configuration database, and further includes:

[0032] If the front-end router does not query the associated information in the configuration database according to the UID of the Internet of Things device in the login information, then connect the Internet of Things device to the default server.

[0033] The above technical solutions provided by the embodiments of the present application have the following advantages compared with the prior art: When the Internet of Things device connects to different server platforms, it does not need to bind the corresponding server IP address. It only needs to bind the IP of the front-end router to the Internet of Things device, and then connect to different private deployment server platforms through the front-end router. The Internet of Things system provided by the embodiments of the present application includes: an Internet of Things device module, a front-end router module, and a server module. Specifically, the Internet of Things device module includes at least one Internet of Things device, the front-end router module includes a front-end router and a front-end router management platform, and the server IP address of the Internet of Things device is configured through the front-end router management platform. Different Internet of Things devices correspond to different server IP addresses. The server module includes an upstream server and a device server. Among them, the Internet of Things device binds the IP address of the front-end router, and the Internet of Things device is connected to the corresponding server through the front-end router. The server of the Internet of Things device is deployed on its own device server, and the upstream server is a cloud server. It can be understood that the front-end router is equivalent to a transfer liaison station. The Internet of Things device discovers the actual server through the front-end router for parsing and forwarding, so that when a large number of Internet of Things devices are connected to the Internet of Things system, a large number of manual configurations of server IP addresses are not required, saving workload. In addition, if the Internet of Things device is updated, the front-end router performs protocol parsing and conversion, and then forwards it to the corresponding server, so that the Internet of Things system of the present application is applicable to more different Internet of Things devices. BRIEF DESCRIPTION OF THE DRAWINGS

[0034] The accompanying drawings herein are incorporated into the specification and form a part of the specification, showing embodiments consistent with the present invention and, together with the specification, are used to explain the principles of the present invention.

[0035] In order to more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the following will briefly introduce the drawings required for use in the description of the embodiments or the prior art. Obviously, for those of ordinary skill in the art, without creative efforts, other drawings can also be obtained based on these drawings.

[0036] One or more embodiments are illustrated by way of example in the accompanying drawings, and these exemplary illustrations do not limit the embodiments. Elements with the same reference numerals in the drawings are represented as similar elements, unless otherwise stated, and the drawings in the drawings do not constitute a proportional limitation.

[0037] Figure 1 It is a schematic diagram of module interaction of an Internet of Things system provided by an embodiment of the present application;

[0038] Figure 2 It is a schematic diagram of system flow provided by an embodiment of the present application. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0039] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the following will clearly and completely describe the technical solutions in the embodiments of this application with reference to the accompanying drawings in the embodiments of this application. Obviously, the described embodiments are part of the embodiments of this application, rather than all of them. All other embodiments obtained by those of ordinary skill in the art based on the embodiments in this application without creative efforts belong to the scope of protection of this application.

[0040] The following disclosure provides many different embodiments or examples for implementing different structures of the present invention. To simplify the disclosure of the present invention, components and settings of specific examples are described below. Of course, they are only examples and are not intended to limit the present invention. In addition, the present invention may repeat reference numerals and / or letters in different examples. This repetition is for the purpose of simplification and clarity, and does not itself indicate the relationship between the various embodiments and / or settings discussed.

[0041] Figure 1 A schematic diagram of module interaction of an Internet of Things system provided for an embodiment of this application. The system includes: an Internet of Things device module, a front-end routing module, and a server module. Specifically, the Internet of Things device module includes at least one Internet of Things device. The front-end routing module includes a front-end router and a front-end routing management platform. The server IP address of the Internet of Things device is configured through the front-end routing management platform. Different Internet of Things devices correspond to different server IP addresses. The server module includes an upstream server and a device server. Among them, the Internet of Things device binds the IP address of the front-end router, and connects the Internet of Things device to the corresponding server through the front-end router. The server of the Internet of Things device is deployed on its own device server, and the upstream server is a cloud server.

[0042] In one embodiment, the front-end routing management platform has a page configuration function. The IP address and port information of the upstream server can be configured through the page of the front-end routing management platform. Further, the Internet of Things system also includes a configuration database, which associates and stores the UID of the Internet of Things device, the IP address, and port information of the upstream server in the configuration database. In addition, the UID of the Internet of Things device and the protocol conversion script are also associated and stored in the configuration database. It should be noted that the protocol conversion script is a preset script for converting the data format in the network transmission process of the Internet of Things system.

[0043] In the embodiments of the present application, when the Internet of Things device in the Internet of Things system connects to the corresponding server, since the Internet of Things device is bound to the IP address of the front-end router, the Internet of Things device first connects to the front-end router. After the Internet of Things device successfully connects to the front-end router, the information of this Internet of Things device can be viewed on the page of the front-end router management platform. Then, the information of the upstream server is configured according to the UID used when the Internet of Things device connects, and after the configuration is completed on the page, the configuration information is associated and stored in the configuration database.

[0044] After that, the front-end router performs traffic forwarding, that is, the front-end router forwards the traffic of the Internet of Things device to the corresponding device server, so that a communication connection is established between the Internet of Things device and the device server. After the communication connection is successfully established, the Internet of Things device can be controlled and its status can be viewed on the server platform of the Internet of Things device. It should be noted that the front-end router uses IPTABLES and the rule table for data forwarding. In the present application, the upstream server is equivalent to a cloud server. Before adopting the Internet of Things system of the embodiments of the present application, the Internet of Things devices in the Internet of Things system default to connect to the server platform deployed on the cloud server. However, in actual scenarios, considering data security and privacy, the Internet of Things devices need to connect to a privately deployed server. The privately deployed server refers to the server deployed on the device server of the Internet of Things device. Therefore, in the present application, the Internet of Things device is bound to the IP of the front-end router, and then connects to different privately deployed server platforms through the front-end router. The front-end router is equivalent to a transit liaison station, and the Internet of Things device discovers the actual server through the front-end router, that is, the server platform deployed on the device server corresponding to this Internet of Things device.

[0045] In one embodiment, when the Internet of Things device logs in to the Internet of Things system, the login information of the Internet of Things device is sent to the front-end router, and the front-end router matches the corresponding server for the Internet of Things device according to the query result of the configuration database. Among them, the login information includes the UID of the Internet of Things device. The system process is shown in Figure 2 , including the following situations:

[0046] The first situation is that the front-end router queries the corresponding upstream server information in the configuration database according to the UID of the Internet of Things device in the login information. At this time, the front-end router parses the data format of the login information, and judges whether communication protocol conversion is required according to the parsing result of the data format. If communication protocol conversion is not required, the Internet of Things device is connected to the upstream server, and the upstream server then connects the Internet of Things device to the corresponding device server; if communication protocol conversion is required, the corresponding protocol conversion script is matched in the configuration database according to the UID of the Internet of Things device, and the Internet of Things device is connected to the upstream server based on the protocol conversion script, and the upstream server then connects the Internet of Things device to the corresponding device server.

[0047] It should be noted that the login information in the embodiments of the present application may include multiple field information related to the Internet of Things device, such as the UID of the Internet of Things device, device type, device model, software version information, hardware version information, etc. Since the constituent fields of the login information are different, the corresponding encapsulated data formats are different, and thus the communication protocols used in network transmission are different. In this way, different login information requires different communication protocols, that is, the network protocols for parsing and forwarding the login information are different. In the present application, different protocol conversion scripts are preset to perform data format conversion on the login information with different data formats, so that different login information can be recognized and forwarded. The present application defines Internet of Things devices with different login information as newly added devices to the system, and it can be known whether a certain logged-in Internet of Things device is a newly added device to the system by comparing and querying with the historical login information of the Internet of Things system.

[0048] Furthermore, in one embodiment, if the data format parsing result of the login information is the preset data format, it is determined that the current Internet of Things device is not a newly added device to the system; otherwise, it is a newly added device to the system. It can be understood that if the login information of the current Internet of Things device is stored in the Internet of Things system, then the front-end router has parsed and forwarded this login information, so there is a corresponding data format record in the system record, which is the preset data format defined in the present application. In this way, the current Internet of Things device is not a newly added device to the system. On the contrary, if the login information of the current Internet of Things device is not in the Internet of Things system, then the front-end router has not parsed and forwarded this login information, so there is no corresponding data format record in the system record. In this way, the current Internet of Things device is a newly added device to the system.

[0049] For newly added devices to the system, communication protocol conversion is required, that is, the corresponding protocol conversion script is queried and matched through the UID of the Internet of Things device, and the login information of the newly added device to the system is parsed and converted to meet the communication protocol requirements of the device side and the server side. It should be noted that in the present application, when the upstream server remains unchanged, if the login information is updated, correspondingly, the communication interaction protocol between the device side and the server side is updated. At this time, the front-end router is used to parse the new protocol and forward it to the upstream server. Parsing the new protocol involves protocol conversion, and the protocol conversion script is used. For non-newly added devices to the system, there is no need to match the protocol conversion script because the front-end router in the Internet of Things system can directly parse the login information.

[0050] The second case is that the pre - routing fails to query the associated information in the configuration database based on the UID of the Internet of Things device in the login information. That is, the Internet of Things device does not have its own private deployment server, and no information related to the Internet of Things device is configured and saved on the pre - routing management platform. At this time, the Internet of Things device is connected to the default server, which is preferably a cloud server, that is, the server platform deployed on the cloud server. In this way, the Internet of Things device has a fallback server platform to connect to in the Internet of Things system.

[0051] In the Internet of Things system involved in the embodiments of the present application, the Internet of Things device is bound to the IP of the pre - routing, and then can be connected to different private deployment server platforms through the parsing and forwarding of the pre - routing. Compared with the prior art, there is no need to manually configure the server IP address, saving workload. Further, if the Internet of Things device is updated, the pre - routing can also perform protocol parsing and conversion, and then forward it to the corresponding server, enabling the Internet of Things system to support access to more different Internet of Things devices, with wide applicability.

[0052] Through the description of the above embodiments, those skilled in the art can clearly understand that each embodiment can be implemented by means of software plus a general - purpose hardware platform, and of course, it can also be implemented by hardware. Based on this understanding, the essence of the above - mentioned technical solution, or the part that contributes to the related technology, can be embodied in the form of a software product. This computer software product can be stored in a computer - readable storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., including several instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute the methods described in each embodiment or some parts of the embodiments.

[0053] It should be understood that the terms used in this document are only for the purpose of describing specific example embodiments and are not intended to be limiting. Unless the context clearly indicates otherwise, the singular forms "a", "an", and "the" as used in this document may also include the plural forms. The terms "include", "comprise", "contain", and "have" are inclusive and thus specify the presence of the stated features, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, steps, operations, elements, components, and / or combinations thereof. The method steps, processes, and operations described in this document are not to be construed as necessarily requiring them to be executed in the specific order described or illustrated, unless the execution order is clearly indicated. It should also be understood that additional or alternative steps can be used.

[0054] The above are only specific embodiments of the present invention, enabling those skilled in the art to understand or implement the present invention. Various modifications to these embodiments will be obvious to those skilled in the art, and the general principles defined herein can be implemented in other embodiments without departing from the spirit or scope of the present invention. Therefore, the present invention will not be limited to these embodiments shown herein, but rather to the broadest scope consistent with the principles and novel features claimed herein.

Claims

1. An Internet of Things system, characterized in that, The Internet of Things system includes: an Internet of Things device module, a front-end routing module, and a server module. The Internet of Things device module includes at least one Internet of Things device. The front-end routing module includes a front-end router and a front-end routing management platform. The server IP address of the Internet of Things device is configured through the front-end routing management platform, and different Internet of Things devices correspond to different server IP addresses. The server module includes an upstream server and a device server. Among them, the Internet of Things device binds to the IP address of the front-end router, and the Internet of Things device is connected to the corresponding server through the front-end router. The server of the Internet of Things device is deployed on its own device server, and the upstream server is a cloud server. The Internet of Things device is connected to a privately deployed server, and the privately deployed server is the server deployed on the device server of the Internet of Things device. The front-end routing management platform has a page configuration function, and the IP address and port information of the upstream server are added through the page of the front-end routing management platform. The Internet of Things system further includes a configuration database, which associates and stores the UID of the Internet of Things device with the IP address and port information of the upstream server, and associates and stores the UID of the Internet of Things device with the protocol conversion script in the configuration database. The login information of the Internet of Things device is sent to the front-end router, and the front-end router matches the corresponding server for the Internet of Things device according to the query result of the configuration database, including: If the front-end router queries the corresponding upstream server information in the configuration database according to the UID of the Internet of Things device in the login information, then parse the data format of the login information. Judge whether communication protocol conversion is required according to the data format parsing result. If not, connect the Internet of Things device to the upstream server, and the upstream server then connects the Internet of Things device to the corresponding device server. If the login information is updated, the communication interaction protocol between the Internet of Things device and the device server is updated to a new protocol. The front-end router uses the protocol conversion script to parse the new protocol and forward it to the upstream server. If the front-end router does not query the associated information in the configuration database according to the UID of the Internet of Things device in the login information, then connect the Internet of Things device to the default server.

2. The system according to claim 1, characterized in that, After judging whether communication protocol conversion is required according to the data format parsing result, it further includes: If required, match the corresponding protocol conversion script in the configuration database according to the UID of the Internet of Things device. Based on the protocol conversion script, connect the Internet of Things device to the upstream server, and the upstream server then connects the Internet of Things device to the corresponding device server.

3. The system according to claim 1, wherein Judging whether communication protocol conversion is required according to the data format parsing result includes: Judge whether the current Internet of Things device is a newly added device to the system according to the data format parsing result. If it is a newly added device, communication protocol conversion is required. If it is not a newly added device, communication protocol conversion is not required.

4. The system according to claim 3, wherein Determining whether the current Internet of Things device is a newly added device to the system according to the data format parsing result includes: Determining whether it is a preset data format according to the data format parsing result; If so, determining that the current Internet of Things device is not a newly added device to the system; If not, determining that the current Internet of Things device is a newly added device to the system.

5. The system according to claim 3 or 4, characterized in that, In the Internet of Things system, if the login information of the logged-in Internet of Things device is different from the historical login information recorded in the system, then the Internet of Things device is a newly added device to the system.

Images