CN106534298B

CN106534298B - Data store system based on Internet of things

Info

Publication number: CN106534298B
Application number: CN201610985180.2A
Authority: CN
Inventors: 杨朴
Original assignee: Shenzhen Huayuan Yun Lian Data Technology Co Ltd
Current assignee: Shenzhen Huayuan Yun Lian Data Technology Co Ltd
Priority date: 2016-11-09
Filing date: 2016-11-09
Publication date: 2020-01-14
Anticipated expiration: 2036-11-09
Also published as: CN106534298A

Abstract

The invention relates to a data store system based on the Internet of things, which comprises: the data acquisition unit acquires data of the monitored equipment, judges whether the data changes compared with the last report or not, and sends the data to the gateway when the change amplitude of the data exceeds a preset value; the gateway sends the received data to the cloud end; and the cloud end receives the data sent by the gateway, analyzes and stores the data, provides the analyzed data for data application as a data source, and performs data processing and returns a data processing result by the data application. The data store system can automatically discover the accessed Internet of things equipment, actively acquire data and provide different data applications based on the data, so that the process of constructing the Internet of things data monitoring system by a user is very easy to change, the construction cost of the Internet of things data monitoring system is greatly reduced, and more data-based functions are provided for the Internet of things data monitoring system.

Description

Data store system based on Internet of things

Technical Field

The invention relates to the technology of the Internet of things, in particular to a data store system based on the Internet of things.

Background

With the development of the internet of things technology, more and more devices and sensors are connected to the internet, and generate massive data, which is mainly stored in the cloud.

In the existing internet of things data cloud, some preset data applications are generally provided for users to use, or data mining is performed based on the data to obtain more valuable information. However, the modules for data statistics or data mining are all preset, and have single functions, and there is no way to meet the practical requirements of users.

Disclosure of Invention

In view of the above, there is a need for a data store system based on the internet of things, which can actively discover devices, acquire data of the devices, and provide different data applications based on the data of the devices.

An internet of things based data store system comprising: cloud, gateway and data acquisition unit:

the data acquisition unit acquires data of the monitored equipment, judges whether the data changes compared with the last report, and sends the data to the gateway when the change amplitude of the data exceeds a preset value;

the gateway sends the received data to the cloud end;

and the cloud end receives the data sent by the gateway, analyzes and stores the data, provides the analyzed data for data application as a data source, and performs data processing and returns a data processing result by the data application.

In one embodiment, the data store system further comprises: the data acquisition unit is used for acquiring configuration information of a user, the acquisition unit is started and then sends the configuration information to the gateway, the gateway sends the received configuration information to the cloud, and the cloud finishes the registration of the data acquisition unit in the cloud according to the received configuration information, so that the data sent by the data acquisition unit is stored in a corresponding user data monitoring project.

In one embodiment, the configuration information includes: the method comprises the following steps of obtaining basic information of corresponding equipment, authorization information of data monitoring items, communication configuration with a gateway, data acquisition configuration with the equipment and configuration information for generating a visual interface.

In one embodiment, the data store system described above includes: and the data application installation module is used for executing a payment process when the data application selected by the user belongs to the charging application, and adding the data application selected by the user to the corresponding data monitoring item after the user finishes payment.

In one embodiment, the data store system further comprises: the cloud end displays an entrance of the data application in a visual interface of the data monitoring project, wherein the entrance is used for triggering execution of the data application; or

And the cloud runs the data application in the background to process the original data generated by the data monitoring project.

In one embodiment, the data application is a script or an executable application that conforms to a predefined programming specification and can be directly invoked and executed by the cloud, and the cloud is further configured to receive data applications uploaded by third parties.

In one embodiment, the data store system further comprises: and the data access interface is used for providing an application programming interface, the application programming interface is used for providing data in the data cloud, the data access interface also counts the times of calling the data access interface by different data applications and data flow for statistics, and generates a bill of an operator of the data application based on a statistical result.

In one embodiment, the cloud further generates a visual interface of the data acquisition unit according to configuration information in the configuration information, where the visual interface includes static content and/or dynamic content.

In one embodiment, the data store system further comprises: and the authorization management module is used for judging whether the current authorization is overdue or whether the current data exceeds the corresponding authorization range according to the authorization information, and canceling the data access authority of the user if the authorization is overdue or the data exceeds the authorization range.

In one embodiment, the authorization management module is further configured to erase the data of the user when the time for which the authorization exceeds the deadline is greater than a preset value.

According to the technical scheme, the data store system can automatically discover the accessed Internet of things equipment, actively acquire the data of the Internet of things equipment, and provide different data applications for the user to use based on the data, so that the process of constructing the Internet of things data monitoring system by the user is very easy to change, the construction cost of the Internet of things data monitoring system is greatly reduced, and more data-based functions are provided for the Internet of things data monitoring system.

In order to make the aforementioned and other objects, features and advantages of the invention comprehensible, preferred embodiments accompanied with figures are described in detail below.

Drawings

Fig. 1 is a schematic structural diagram of a data store system according to an embodiment of the present invention.

FIG. 2 is a schematic diagram of a network connection of the data store system of FIG. 1.

Fig. 3 is a hardware architecture diagram of the gateway of fig. 1.

Fig. 4 is a hardware architecture diagram of the data acquisition unit of fig. 1.

FIG. 5 is a block diagram of the data store system of FIG. 1.

FIG. 6 is a flow diagram of a user add-on device of the data store system of FIG. 1.

FIG. 7 is a flow chart of the data store system of FIG. 1 actively discovering access to a data acquisition unit.

Fig. 8 is a flowchart of the data store system of fig. 1 in which the data acquisition unit actively reports data.

Fig. 9 is a block diagram of data application in the data store system of fig. 1.

Detailed Description

To further illustrate the technical means and effects of the present invention adopted to achieve the predetermined objects, the following detailed description of the embodiments, structures, features and effects according to the present invention will be made with reference to the accompanying drawings and preferred embodiments.

Fig. 1 is a schematic diagram of a data store system according to an embodiment of the present invention. As shown in fig. 1, the data store system 100 includes: a device layer 10, a data acquisition layer 20, an aggregation layer 30, and a data cloud 40.

The device layer 10 refers to various devices/facilities capable of generating monitoring data by themselves, or sensors provided independently. Specific examples of the device layer 10 include, but are not limited to, a server, a Power Distribution Unit (PDU), a cooling device (including an air conditioner, a water cooling device, a blower, a fan, etc.), an Uninterruptible Power Supply (UPS), a door access device, a camera, various sensors (including a temperature sensor, a humidity sensor, a light sensor, a noise sensor, an infrared sensor, an electromagnetic radiation sensor, a gas sensor, a smoke sensor, a carbon monoxide sensor, a carbon dioxide sensor, a particulate matter concentration sensor (such as a PM2.5 sensor), and the like.

The Data acquisition layer 20 includes a plurality of Data acquisition units (PDU) 21, which are connected to the monitored device or the sensor, and are used for collecting monitoring Data from the monitoring device or the sensor, and further performing Protocol conversion on the acquired Data, and converting all Data into Data of a uniform format/Protocol. It will be appreciated that different devices or sensors follow different protocols and the type of monitoring data generated will be different. Therefore, the data acquisition unit 21 also needs to adopt different interfaces and communication protocols for different monitored devices or sensors. The data collection layer 20 uploads monitoring data collected from monitored devices or sensors to the aggregation layer 30. It is understood that the data acquisition layer 20 is not necessary, and when the device or the sensor of the device layer 10 directly embeds the communication protocol matched with the data cloud, the data acquisition layer 20 is embedded in the device and the sensor.

The aggregation layer 30 includes a plurality of gateways 31, each gateway 31 being connected to a plurality of data acquisition units 21, devices, or sensors within a monitored site (e.g., the same cabinet, the same room, the same site). Typically, the gateway 31 communicates with the data acquisition unit 21 or the device/sensor via a serial port (e.g., RS 485). Certainly, serial communication is not limited to be adopted between the gateway 31 and the data acquisition unit 21, and any network protocol, such as bluetooth, infrared, WIFI, Zigbee, Near Field Communication (NFC), and the like, may be used to implement data exchange between the gateway 31 and the data acquisition unit 21. The gateway 31 is connected to the data acquisition unit 21 and also to the data cloud 40 via the internet, and converts (if necessary) the data reported by the data acquisition unit 21 and the devices/sensors and reports the converted data to the data cloud 40.

Referring to fig. 2, in one embodiment, the gateway 31 is networked to the cloud server 41 in the platform layer 40 by accessing the internet through a POE (Power Over Ethernet) switch 32. The gateway 31 and the POE switch 32 may be connected by only one cable, which simultaneously transmits network signals and provides dc power to the gateway 31.

As shown in fig. 2, the gateway 31 is provided with a plurality of interfaces 310. In this embodiment, the gateway is provided with 3 sets of interfaces 310, and each set is 8, that is, the gateway 31 is provided with 24 interfaces 310 in total. It is understood that the number of interfaces 310 on the gateway 31 is not limited in any way, and can be supported in hardware or software.

Each interface 310 is connected to one data acquisition unit 21, and each data acquisition unit 21 is connected to one device or sensor 11. The interface 310 may also have POE function, that is, the gateway 31 provides the data acquisition unit 21 with dc power required for operation.

Because POE switch 32 and gateway 31 all have the ability of ethernet power supply, consequently, gateway 31 and data acquisition unit 21 all no longer need extra power access, have reduced the quantity of cable, have reduced the complexity of maintaining.

In a specific hardware implementation, the interface 310 may be a general network card interface, i.e., an RJ45 interface. The reason why the RJ45 interface is adopted is that the connection line adopted by the RJ45 interface is a network cable, which is most easily found in various environments, especially in a machine room. However, the specific hardware implementation of the interface 310 is not limited to the RJ45 interface, and any other interface, such as an RS485 interface, an RS232 interface, etc., may be used.

In addition, it is understood that although the interface 310 is an RJ45 interface, a serial communication protocol is generally used for data communication between the gateway 31 and the data acquisition unit 21, and how to implement serial communication based on an RJ45 interface will be described below in conjunction with a hardware architecture of the gateway 31.

Referring to fig. 3, a hardware architecture diagram of the gateway 31 is shown in an exemplary embodiment. Gateway 31 includes a power converter 311, computer module 312, serial converter 313, and interface 310.

The power converter 311 is used to convert the input dc power or ac power into a required dc power (e.g., 12V dc power) and provide power to the computer module 312. In addition, the power output pin of the power converter 311 is also connected to a pin of the interface 310, and is used for providing a direct current power supply to the interface 310, so that the interface 310 has POE capability.

The computer module 312 may be, for example, a single chip microcomputer or other type of small computer system, such as a raspberry-style computer. The computer module 312 may have one or more USB interfaces 315. In a specific example, as shown in fig. 3, the computer module 312 has 4 USB interfaces 315, wherein 3 USB interfaces 315 are respectively connected to a serial port converter 313. Specifically, each serial port converter 313 also includes a USB interface. The USB interface of each serial converter 313 is connected to a corresponding USB interface 315 of the computer module 312. Alternatively, the serial port converter 313 may be directly integrated on the same circuit board as the computer module 312, and at this time, the connector interface may be directly omitted, and the signal line may be directly connected to the USB bus of the serial port converter 313 and the computer module 312 in a USB manner.

The other end of each serial port converter 313 is connected to a serial port communication bus (e.g., an RS485 bus). It will be appreciated that the RS485 bus may generally only require 2 signal lines. A plurality of interfaces 310 are connected to each serial communication bus. As mentioned above, the interface 310 is an RJ45 interface, and correspondingly, the uplink interface (see the interface 220 in fig. 4) of the data acquisition unit 21 is also an RJ45 interface. In one specific example, the line order definition of the interface 310 and the interface 220 may be as follows: DC 12V +, group, A +, B-, A2+, B2-, Unity Enable (hereinafter referred to as UE) and Data Enable (hereinafter referred to as DE).

The supply lines (DC 12V + and group) support a voltage level of 12V.

A + and B-are RS485 data lines A + and B-respectively, and are connected with the RS485 bus. Where a2+ and B2-are used as return-to-serial lines, i.e. a2+ connection a +, B2-connection B-, for supporting star connections on the gateway side (actually a concatenation, just appearing to be star-connected in appearance). This connection requires that the gateway spare port also short the signal line.

As shown in FIG. 3, the computer module 312 also has an input/output (I/O) bus (not shown), to which both the UnityEnable and the Data Enable are connected. The Unity Enable and Data Enable of different Data acquisition units 21 may be connected to the same I/O port or to different I/O ports.

Unity Enable refers to the gateway 31 controlling whether the data acquisition unit 21 can respond to a request, and allowing the data acquisition unit 21 to respond only if the UE level is pulled high. In this manner, the gateway 21 can centrally control each data acquisition unit 21.

When the Data Enable indicates that the Data acquisition unit 21 has new Data to report, the level (DE) is raised, and the gateway 31 initiates a Data polling command. According to the hardware design of the Gateway 31, the DE of multiple data acquisition units 21 may be connected to the same I/O port of the Gateway (i.e. the Gateway 31 needs to poll all data acquisition units 21), and if connected to different I/O ports, the Gateway 31 only needs to send out a polling request for the data acquisition unit 21 with the level of the corresponding DE raised. After the data acquisition unit 21 returns data, the DE level is pulled down. According to the design, the gateway 31 can send out the polling request only when the data acquisition unit 21 is pulled up, so that useless polling requests can be reduced to the maximum extent, the occupation of the serial port communication bus bandwidth is reduced, and more data acquisition units 21 can be accessed simultaneously.

In a specific example, the pin definitions of the interface 310 are shown in the following table, and it is to be understood that the specific pin definitions may be varied arbitrarily and are not limited in any way.

Pin	Definition of
		1	A+
2	B-
		3	Unity Enable
4	A2+
		5	DC 12V+
6	Data Enable
		7	B2-
8	DC 12V-

Fig. 4 is a schematic diagram of a hardware architecture of the data acquisition unit 21. The data acquisition unit 21 includes: a microcontroller module 210,

interfaces

220 and 230, a flash memory 240,

serial communication modules

250a and 250b, and an ethernet module 260. The microcontroller module 210 may be, for example, a Nano processor chip or other type of integrated circuit chip, and the flash memory 240 is used for storing codes and other data for the controller module 210 to run. The interface 220 and the interface 230 are both RJ45 interfaces, pins 1 and 2 of the interface 220 are connected to a serial communication module 250a, and the serial communication module 250a is further connected to the microcontroller module 210. Pins 3, 6 of interface 230 are connected to serial communication module 250b, and serial communication module 250b is further connected to microcontroller module 210.

Pins 3, 6 of interface 220 are connected to the I/O bus of microcontroller module 210, pins 4, 7 are connected to the power input pins of microcontroller module 210 for providing power required by microcontroller module 210, and pins 5, 8 are connected to pins 4, 8 of interface 230, respectively, for enabling POE capability of interface 230.

Pins 1, 2 of interface 230 are connected to ethernet module 260, ethernet module 260 is further connected to microcontroller module 210, pins 3, 6 of interface 230 are connected to serial communication module 250b, and serial communication module 250b is further connected to microcontroller module 210.

The interface 220 is used for connecting with the interface 314 of the gateway 31, and since both interfaces are RJ45 interfaces, a universal network cable can be directly used for connection.

The above definitions of the pins of the

interfaces

220 and 230 are only examples, and those skilled in the art can arbitrarily change the pin according to actual situations, and can achieve the same functions.

The interface 230 is used for connecting with an interface (not shown) of a monitored device, and although the RJ45 interface is taken as an example for illustration, it is understood that the interface 230 is not necessarily an RJ45 interface, but is consistent with a data interface of the monitored device. Therefore, when the monitored device supports the RJ45 interface, the interface 230 uses the RJ45 interface; when the monitored device supports the USB interface, the interface 230 adopts the USB interface. Other interfaces such as Phoenix and DB9 and so on. Since not all interfaces have enough free pins to provide POE capability, POE capability may not be provided when there are insufficient pins in an interface.

In the above examples shown in fig. 2-4, the data acquisition unit 21 is disposed outside the gateway 31, and on the panel of the gateway 31 is the interface 310. However, in other embodiments, the data acquisition unit 21 may be integrated directly inside the gateway 31, and the interface 230 of the data acquisition unit 21 may be disposed on the panel of the gateway 31 and may be directly connected to the monitored device 11. When the design is adopted, the data acquisition units can be arranged inside the gateway 31, so that scattered wiring outside is reduced, and the maintenance complexity is reduced.

The above is a schematic diagram of a network and a hardware architecture according to an embodiment of the present invention. The data store system provided by the technical scheme of the invention is described in combination with the above architecture.

Referring to fig. 5, the data store system 200 includes: a user project management module 210, a device discovery module 220, a data synchronization module 230, an authorization management module 240, a data application management module 250, and a visualization module 260.

The user item management module 210 is configured to create data monitoring items for a user, where each data monitoring item may be mounted with one or more devices, sensors, or data collection units. It will be appreciated that in the initial state, the user does not own any devices, sensors or data acquisition units. Requiring the user to make the addition.

Specifically, referring to fig. 6, the process of adding a device by a user includes the following steps:

step S11, the user selects the device model and completes the payment of the related fee;

step S12, writing the configuration information corresponding to the device model into one or more data acquisition units;

the configuration information may define basic information of the device (e.g., may include name, manufacturer, model, version, creation time, description, etc.), authorization information (e.g., may include authorization name, authorization type, authorization token, authorization period, user, data monitoring item belonging thereto, communication configuration with the gateway (e.g., may include connection type, communication protocol, communication address, connection information such as port, baud rate, parity, data bit, stop bit, etc.), and collection configuration with the monitoring device (e.g., may include manufacturer, class, model, template, collection information of the device, etc.) Port, baud rate, parity information, etc.).

Further, the configuration information may further include configuration information for enabling the data cloud to perform data visualization, and the configuration information may include static content and mapping rules of dynamic content, where the static content includes: text, pictures, animations, video, audio; the mapping rule of the dynamic content defines the mapping relation from the data of the Internet of things to the interface. The configuration information can also comprise instruction configuration information which defines the response logic of the generated visual interface responding to the user operation; the cloud further generates the response logic when the visualization interface is generated, and the response logic is triggered and executed by a user and then sends corresponding instruction codes and parameters to the cloud.

The configuration information represents a mapping from the data of the device/sensor to the visual interface, and the visual interface corresponding to the device/sensor can be generated according to the mapping relationship in the cloud.

It is understood that for an interface, it generally includes static content as well as dynamic content, where static content refers to content that does not change, such as descriptive text, background pictures, icons, content-specific animations, videos, and the like; while dynamic content is opposed to static content, the content may change as the device/sensor data changes. Static content is generally stored directly in configuration information in the form of material (including text, picture, video, audio, etc.); the dynamic content needs to be stored in the configuration information in the form of mapping rules. The mapping rule needs to define a data source and a response mode of an interface when the data source changes. Specific examples of response modes herein include, but are not limited to: updating the drawn graph and curve in real time according to the real-time updated data; the properties of the interface such as color, size, parameters of animation, sound level, displayed content, etc. are changed according to the data updated in real time.

Furthermore, another mapping relationship, namely mapping of the user operation on the generated visual interface to the device/sensor control instruction, may be included in the configuration information. At this moment, when the user operates the generated visual interface, the cloud end generates corresponding response logic according to the mapping relation, the response logic is executed by the terminal displaying the visual interface, the response logic is executed and then sends corresponding instruction codes and parameters (if any) to the cloud end, and the cloud end sends the instruction codes and parameters (if any) to the data acquisition unit. The data acquisition unit executes the corresponding instruction after receiving the instruction code and the parameters (if the instruction code and the parameters exist), so that the user can directly control the remote equipment/sensor in the visual interface.

Step S13, distributing the data acquisition unit written with the configuration information and the general gateway (if necessary) to the user;

in step S14, the user connects the cable to complete the installation of the gateway and the data acquisition unit.

According to the mode, the data acquisition unit with the configuration information stored in the data acquisition unit can be provided for the user, and the user finishes installation. The installation can be easily finished without depending on professionals trained by simply connecting cables, so that the maintenance and installation cost is reduced.

In addition, it is understood that, in addition to selecting the data acquisition unit for data acquisition, it is also possible to directly select a device in which the same data communication protocol as that of the data acquisition unit is built, and thus, in the architecture shown in fig. 1, the data acquisition unit may be omitted, and the device or the sensor may be directly connected to the gateway.

Based on the data acquisition unit written with the configuration information in advance, the data store system can actively discover whether the data acquisition unit is connected to the network, referring to fig. 7, and the method includes the following steps:

step S21, the data acquisition unit (or the device which realizes the data acquisition protocol inside) sends the configuration information to the gateway after connecting with the gateway;

step S22, the gateway uploads the configuration information to a cloud server;

and step S23, the cloud server analyzes and stores the received configuration information, and registers the data acquisition unit according to the analyzed configuration information. Specifically, the device discovery module 220 is responsible for the registration operation of the data acquisition unit.

According to the method provided by the embodiment, after the data acquisition unit is connected with the gateway, the configuration information can be actively sent to the cloud, so that the cloud can actively discover that a new data acquisition unit is accessed to the network, and further synchronize the data of the data acquisition unit to the corresponding data monitoring project, and accordingly, a user can browse the data of the data acquisition unit from the data monitoring project.

Because the configuration information already comprises the analysis of the data and even the visualization protocol, after registration, the cloud end can automatically analyze the data sent by the data acquisition unit without additional adaptation process.

As mentioned above, the data acquisition unit 21 and the gateway 31 communicate with each other through the serial communication bus, and the serial communication bus generally adopts a master-slave architecture, and the communication needs to be periodically polled by the host. Therefore, when the data of the data acquisition unit 21 is excessive, the bandwidth of the serial communication bus may be insufficient, and the network delay increases. In view of this, in the embodiment of the present invention, the polling method of the existing serial communication bus may also be changed by using the redundant interface of the 8-core cable, and the new communication mode is as follows: the gateway 31 no longer actively sends a polling request to the data acquisition unit 21, and with reference to fig. 8, further includes the following steps:

step S31, the data acquisition unit acquires data and judges whether the data changes;

step S32, when the data change exceeds the preset range, the data acquisition unit pushes the data to the gateway or notifies the gateway of acquiring the data;

step S33, the gateway forwards the data to the cloud;

in step S34, the cloud updates the database. Specifically, the received data is stored in the database by the data synchronization module 230.

According to the technical scheme, although the data acquisition unit/equipment/sensor and the gateway are communicated by adopting a serial communication bus, the data acquisition unit actively pushes data to the gateway or sends a data acquisition notice to the gateway only when the data change exceeds a preset amplitude instead of a traditional polling mode. Therefore, the polling times can be obviously reduced, and the data transmission quantity between the gateway and the cloud end is reduced.

The authorization management module 240 is responsible for managing authority management of the data monitoring items, and specifically, it may count data operations of a certain data monitoring item according to flow, the number of devices, and update/acquisition frequency of data, and determine whether the data operations exceed a predetermined authority range, and when the data operations exceed the authority range, it may omit data that exceed the authority range. In addition, the authorization for the data monitoring item may also have a corresponding time limit, and when the time exceeds the time limit, the authorization management module 240 may cancel the data access right of the user for the data monitoring item. When the time exceeding the deadline is greater than a predetermined value, the authorization management module 240 may also be responsible for irreversibly erasing the data stored in the cloud by the user.

The data application management module 250 is responsible for installation, uninstallation, and execution of data applications. A data application refers to a script program or an executable application program that conforms to a predefined specification. The data application may be written and uploaded by a third party and published within the data store system 200. That is to say, the cloud receives and audits the data application uploaded by the third party, and after the audit is completed, the data application is disclosed in the data store system, and the user can select to install the data application.

Referring to fig. 9, the data application needs to implement: data access interface 51, data processing logic 52, data return interface 53, and application installation information 54.

Wherein the data access interface 51 obtains data from the data cloud 40 by calling an Application Programming Interface (API) provided by the data store system. The data range here may be data of all devices under the data monitoring item to which the user belongs. Alternatively, the data store system provides the offering data.

The data processing logic 52 is responsible for processing the data obtained by the data access interface, and its specific functions include, but are not limited to: statistics, analysis, data visualization, building three-dimensional models, making predictions based on data, speech recognition, image recognition, generating audio, generating video, sending reminders, data synchronization, data mining, and so forth.

The data return interface 53 encapsulates the data processing result of the data processing logic 52 into a format predefined by the data cloud 40, and returns the encapsulated data to the data cloud 40 for presentation to the client. The returned data may include all the data or may be an index of the data in the storage system. In short, regardless of the data format, the data cloud 40 can read the corresponding data according to the returned result. It will be appreciated that the data processing logic 52 may also not return values, but merely perform certain data processing operations.

The application installation information 54 may define the following information: the applicable devices and the runtime require a dependent data range. The applicable devices are used for enabling the data application management module 250 to determine to which devices a certain data application is applicable, and the data range that needs to be relied on during the operation can be used for the data cloud 40 to perform data access permission setting.

In a specific implementation manner, the data application may be a script application, which is interpreted and executed by the interpreter, or may be an executable application, which may be directly executed, and the running environment of the data application may be Windows, Linux, Unix, or any variant system thereof. It is to be understood that data applications of different execution environments may be actually executed by different servers, respectively. Of course, virtual machine technology may also be used to run applications of different platforms on the same physical machine.

Data applications can be divided into two types, charging applications and free applications. The free application can be freely added to a certain data monitoring project by a user, and the charged data application requires the user to complete payment of the data application first, namely, the application can be added to the certain data monitoring project after the payment process is completed at the cloud end.

When a data application is added to a certain data monitoring item, an entry of the data application is correspondingly displayed in an interface of the data monitoring item, and through the entry, a user can trigger the interface of the data application.

In the above embodiments, the data targeted by the data application is data generated for the data monitoring item of the user, however, the technical solution of the embodiment of the present invention is not limited thereto, for example, in some data applications, the data that needs to be called is not limited to a certain data monitoring item, for example, it may call all data of a certain type of device. It will be appreciated that in the default state, the user's private device generation and data is kept secret and not open, however, the data store system can copy the data generated by the user's private device as public data upon obtaining user authorization.

For example, when massive air conditioners are connected to the data cloud, a certain proportion of users can select to share the data, and thus, the data of the massive air conditioners in the data cloud is in a state that the data cloud can be used. Referring to FIG. 9, a data access interface 270 may also be included within the data store system for providing APIs for data applications to call to obtain data that various user authorized data clouds may employ. Accordingly, the data application calls such data through the data access interface to perform certain functions, such as big data analysis, data mining, and the like.

In addition, the data access interface 270 also counts the number of times that different data applications call the data access interface and the data traffic, and generates a bill of the data application operator based on the statistical result.

In this way, data applications based on data of larger dimensions can be provided, which can provide more functionality.

In addition, an embodiment of the present invention further provides a computer-readable storage medium, in which computer-executable instructions are stored, where the computer-readable storage medium is, for example, a non-volatile memory such as an optical disc, a hard disc, or a flash memory. The computer-executable instructions are used to make a computer or similar computing device perform the methods of the embodiments.

Although the present invention has been described with reference to the preferred embodiments, it should be understood that various changes, substitutions and alterations can be made herein without departing from the spirit and scope of the invention as defined by the appended claims.

Claims

1. An internet of things based data store system comprising: user project management module, high in the clouds, gateway and data acquisition unit, its characterized in that:

the user project management module creates a data monitoring project and adds equipment to the data monitoring project, wherein the step of adding equipment comprises the following steps: selecting an equipment model and completing related expense payment, writing configuration information corresponding to the equipment model into one or more data acquisition units, wherein the configuration information comprises basic information of corresponding equipment, authorization information of a data monitoring project, communication configuration with a gateway, data acquisition configuration with the equipment and configuration information for generating a visual interface, and distributing the data acquisition units and the universal gateway into which the configuration information is written to a user, and the user is connected with a cable to complete installation of the gateway and the data acquisition units;

the data acquisition unit actively sends the configuration information which is internally arranged and comprises an analysis or visualization protocol of data to the gateway after being connected with the gateway, and the data acquisition unit adopts an 8-core cable interface so that the gateway does not actively send a polling request to the data acquisition unit;

the data acquisition unit acquires data of monitored equipment, judges whether the data changes compared with the last report, and sends the data to the gateway or sends a data acquisition notice to the gateway when the change amplitude of the data exceeds a preset value;

the gateway sends the received data and the configuration information to the cloud end;

the cloud end receives the data and the configuration information sent by the gateway, analyzes and stores the data and the configuration information, provides the analyzed data for a data application as a data source, processes the data by the data application and returns a data processing result, and synchronizes the data to a corresponding data monitoring project so that a user can browse the data of the data acquisition unit from the monitoring project, and completes the registration of the data acquisition unit at the cloud end according to the received configuration information so that the data sent by the data acquisition unit is stored to the corresponding user data monitoring project, wherein the data application comprises data generated by private equipment of the user and copied under the condition of obtaining user authorization as public data.

2. The internet of things-based data store system of claim 1, wherein the cloud comprises: and the data application installation module is used for executing a payment process when the data application selected by the user belongs to the charging application, and adding the data application selected by the user to the corresponding data monitoring item after the user finishes payment.

3. The internet of things-based data store system of claim 2, further comprising: the cloud end displays an entrance of the data application in a visual interface of the data monitoring project, wherein the entrance is used for triggering execution of the data application; or

4. The internet of things-based data store system of claim 2, wherein the data application is a script or executable application that conforms to a predefined programming specification and is directly invoked for execution by the cloud, the cloud further configured to receive data applications uploaded by a third party.

5. The internet of things-based data store system of claim 1, further comprising: and the data access interface is used for providing an application programming interface, the application programming interface is used for providing data in the data cloud, the data access interface also counts the times of calling the data access interface by different data applications and data flow for statistics, and generates a bill of an operator of the data application based on a statistical result.

6. The internet of things-based data store system of claim 1, wherein the cloud further generates a visual interface for the data acquisition unit according to configuration information in the configuration information, the visual interface including static content and/or dynamic content.

7. The internet of things-based data store system of claim 1, further comprising: and the authorization management module is used for judging whether the current authorization is overdue or whether the current data exceeds the corresponding authorization range according to the authorization information, and canceling the data access authority of the user if the authorization is overdue or the data exceeds the authorization range.

8. The internet of things-based data store system of claim 7, wherein the authorization management module is further configured to erase the user's data when the time for authorization to exceed the deadline is greater than a preset value.