A general technical architecture method and system based on building energy internet of things

Abstract

The application discloses a general technical architecture method and system based on building energy internet of things, which comprises the following steps: selecting an access protocol according to the type of equipment, and accessing the end side of the energy system basic operation related equipment; matching the corresponding solution according to the business function of the end side access equipment, and converting the communication protocol of the end side access equipment into an MQTT protocol; constructing an internet of things data unified gathering layer, converting the communication protocol of a third party system into the MQTT protocol, gathering the data uploaded by the end side, the side and the third party system to the internet of things data unified gathering layer based on the MQTT protocol; extracting the data gathered by the internet of things data unified gathering layer to a data transfer system for data transfer through the internal data processing side of the cloud side, and storing the obtained transfer data to a data storage layer through a business adaptation layer. The application can realize the functions of wide access, simple analysis and efficient conversion of data for building energy scenes.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of cloud edge data collaboration, and in particular to a general technical architecture method and system based on building energy internet of things. BACKGROUND

[0002] Traditional energy management methods are simple and extensive, and are run based on experience, lacking sufficient data support for operational analysis, making it difficult to achieve further automation and further energy optimization. Based on the above industry status, major companies are actively implementing the digitization and intelligent operation of building energy systems, and the first priority is to build an internet of things base platform for various forms of building energy and various internet of things devices, as well as an internet of things technology architecture for data analysis, intelligent control, and intelligent operation needs. Currently, the architecture of the internet of things platform is in full bloom, and the industry generally adopts two methods to build the internet of things technology architecture platform. The first method is a basic architecture implementation method, which uses a simple basic architecture to collect data and directly store it in the database to complete the overall function and achieve the purpose of rapid deployment. The second method is a general internet of things technology architecture method, which is designed by referring to the methods of internet giants and includes devices, products, product categories, and object models. It also implements functions such as local access, cloud gateway capabilities, scene linkage, generalized protocols, and device authentication.

[0003] Defects and deficiencies of the prior art: The above two technical solutions can solve the problem of building energy scene internet of things data access to a certain extent, but they still fail to design an internet of things platform architecture for building energy scenes. The root cause is:

[0004] 1. It is detached from the business scene: Most designs refer to general internet of things platform designs, resulting in a bloated overall architecture and high development costs, making it difficult to implement in practice.

[0005] 2. It ignores the technical specialty: Most internet of things platforms are designed by products that do not understand technology, which has significant limitations. They often fail to use the characteristics of technology for targeted design, and as business needs grow, the platform faces the dilemma of being unable to meet demand.

[0006] 3. It is designed without considering the data platform: It does not take into account the subsequent needs of building energy intelligent operation and is limited to local internet of things needs. Subsequent integration with big data platforms or data hubs will increase data governance costs.

[0007] The above reasons ultimately result in an architecture that cannot meet business needs, leading to commercial failure, increased research and development costs, and wasted research and development resources. SUMMARY

[0008] In view of the above problems, the present application provides a general technical architecture method and system based on building energy Internet of Things, which greatly reduces the development cost under the premise of meeting the demand of continuous expansion of business, and has very high expansibility, can face the business demand of most scenarios of building energy, and at the same time, the architecture considers the demand of intelligent operation, reserves data model and interface, and can easily help enterprises to realize the technical ability of digital and intelligent operation goal.

[0009] In order to achieve the above purpose, the present application provides the following technical scheme:

[0010] According to the first aspect of the present application, a general technical architecture system based on building energy Internet of Things is provided, which comprises: end side, edge side and cloud side; the cloud side comprises external data processing side and internal data processing side;

[0011] The end side is used for realizing the access to various energy system basic operation related devices of building energy scene;

[0012] The edge side converts the communication protocol of the end side access device into MQTT protocol, and is used for realizing the standardized and unified management of the end side access device before data aggregation;

[0013] The external data processing side is used for constructing an Internet of Things data unified aggregation layer before the data of the end side or the edge side is uploaded to the cloud, converting the communication protocol of a third party system into MQTT protocol in the Internet of Things data unified aggregation layer, and based on the protocol specification of MQTT protocol, the data uploaded by the end side, the edge side and the third party system is aggregated to the Internet of Things data unified aggregation layer; the external data processing side is a technical architecture for the docking of third party system-Internet of Things protocol converter-cloud end deployment;

[0014] The internal data processing side is used for data extraction, data transfer, business adaptation and data storage of the data aggregated by the Internet of Things data unified aggregation layer, and the internal data processing side is a four-level data processing link architecture composed of high-efficiency stream data processing middleware, data transfer system, business adaptation layer and data storage layer;

[0015] The technical architecture of the general technical architecture system is a three-level data system; the three-level data system comprises a first data link, a second data link and a third data link.

[0016] Further, the end side is used for realizing the access to various energy system basic operation related devices of building energy scene, comprising:

[0017] The end side determines the device type based on the device attribute of the energy system basic operation related device; the device type includes single independent networking device, lower machine device, upper machine access device, third party system device and other customized device;

[0018] According to the device type, the corresponding access protocol is selected, and the energy system basic operation related device is accessed to the end side.

[0019] Further, the edge side is used to realize the specification and unified management of the end side access device before data aggregation, and the communication protocol of the end side access device is converted into MQTT protocol, which comprises:

[0020] The edge side determines the solution based on the business function of the end side access device; the solution includes the access scheme of hard gateway, the access scheme of hardware server and the access scheme of edge computing node;

[0021] According to the analysis of the business function of the end side access device, the corresponding solution is selected, and the communication protocol of the end side access device is converted into MQTT protocol according to the corresponding solution.

[0022] Further, the high-efficiency stream data processing middleware extracts data from MQTT through MQTT-Kafka connection component, and stores the obtained data into the data transfer system.

[0023] Further, the data transfer system uses Kafka as the basic technical support middleware of the data transfer system, and stores the data in the data transfer system through Kafka-Topic storage specification to obtain the transfer data; the latest periodic data can also be extracted from the data transfer system through ETL service, and the periodic data is put into data warehouse or connected with other data forwarding sources.

[0024] Further, the business adaptation layer is built by using IOT-HUB business adapter, and the transfer data is adapted by the business adaptation layer.

[0025] Further, the data storage layer dynamically expands the business adapter based on the business adaptation of the transfer data to load the data of multiple data sources in the transfer data.

[0026] Further, the first data link is used to store real-time data, the second data link is used to store recent data, and the third data link is used to store full data.

[0027] Further, the Internet of Things data unified convergence layer is provided with a data model; the data model comprises an edge node model, an Internet of Things device model and a progressive data model; the progressive data model comprises a basic data model, a standard data model and a unified data model;

[0028] The basic data model is used for analyzing original data;

[0029] The standard data model introduces key attributes based on the basic data model and is used for data protocol optimization;

[0030] The unified data model introduces business data based on the standard data and is used for data isolation.

[0031] The second aspect of the present application provides a general technical architecture method based on building energy Internet of Things, comprising:

[0032] The device type is determined according to the device attribute of the energy system basic operation related device on the end side, the corresponding access protocol is selected, and the energy system basic operation related device is accessed to the end side;

[0033] The communication protocol of the end side access device is converted into the MQTT protocol through the side according to the business function matching corresponding solutions of the end side access device, and the data generated by the end side access device is uploaded to the external data processing side of the cloud side based on the MQTT protocol;

[0034] The Internet of Things data unified convergence layer is constructed by the external data processing side of the cloud side before the data of the end side or the side is uploaded to the cloud, the communication protocol of the third party system is converted into the MQTT protocol in the Internet of Things data unified convergence layer, and the data uploaded by the end side, the side and the third party system is converged to the Internet of Things data unified convergence layer based on the protocol specification of the MQTT protocol;

[0035] The data converged by the Internet of Things data unified convergence layer is extracted to the data transfer system for data transfer through the efficient flow data processing middleware of the internal data processing side of the cloud side, and the obtained transfer data is stored to the data storage layer through the business adaptation layer.

[0036] The application discloses a general technical architecture method and system based on building energy internet of things, and the method comprises the following steps: selecting an access protocol according to a device type, and accessing an end side of an energy system basic operation related device; matching a corresponding solution according to a business function of the end side access device, and converting a communication protocol of the end side access device into an MQTT protocol; constructing an internet of things data unified convergence layer, converting a communication protocol of a third party system into the MQTT protocol, converging data uploaded by the end side, the edge side and the third party system to the internet of things data unified convergence layer based on the MQTT protocol; extracting the data converged by the internet of things data unified convergence layer to a data transfer system for data transfer through an internal data processing side of a cloud side, and storing the obtained transfer data to a data storage layer through a business adaptation layer. BRIEF DESCRIPTION OF DRAWINGS

[0037] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the following will briefly introduce the drawings needed to be used in the embodiments or the prior art description. Obviously, the drawings in the following description are only exemplary, and for those skilled in the art, other drawings can be obtained from the provided drawings without creative labor.

[0038] The structures, proportions, sizes and the like shown in the specification are only used to cooperate with the content disclosed in the specification, to be understood and read by those skilled in the art, and do not define the limiting conditions for the implementation of the present application, so they do not have technical significance. Any modification of structure, change of proportion relationship or adjustment of size, which does not affect the effects and purposes that can be achieved by the present application, should still fall within the scope of the technical content disclosed by the present application.

[0039] Figure 1 A schematic diagram of a general technical architecture system based on building energy internet of things provided by the present application is shown;

[0040] Figure 2 A flowchart of a general technical architecture method based on building energy internet of things provided by the present application is shown;

[0041] Figure 3 A complete architecture schematic diagram of a general technical architecture system based on building energy internet of things provided by the present application is shown;

[0042] Figure 4 A three-level data link diagram of a general technical architecture based on building energy internet of things provided by the present application is shown;

[0043] Figure 5An IOT-HUB business adapter diagram of a general technical architecture based on building energy internet of things provided by the present application is shown. DETAILED DESCRIPTION

[0044] The embodiments of the present application are illustrated by the specific embodiments below, and other advantages and effects of the present application can be easily understood by those skilled in the art from the content disclosed in the specification. Obviously, the described embodiments are part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative labor fall within the scope of protection of the present application.

[0045] Figure 1 A schematic diagram of a general technical architecture system based on building energy internet of things provided by the present application is shown.

[0046] As shown in Figure 1 The present application discloses a general technical architecture system based on building energy internet of things, which comprises an end side, a side side and a cloud side; the cloud side comprises an external data processing side and an internal data processing side;

[0047] The end side is used to realize the access of various energy system basic operation related equipment of building energy scene;

[0048] The side side converts the communication protocol of the end side access equipment into MQTT protocol, and is used to realize the standardized and unified management of the end side access equipment before data aggregation;

[0049] The external data processing side is used to build an internet of things data unified aggregation layer before the data of the end side or the side side is uploaded to the cloud, and the communication protocol of a third party system is converted into MQTT protocol in the internet of things data unified aggregation layer. The data uploaded by the end side, the side side and the third party system is aggregated to the internet of things data unified aggregation layer based on the protocol specification of MQTT protocol. The external data processing side is a technical architecture for the docking of the third party system, the internet of things protocol converter and the cloud end deployment;

[0050] The internal data processing side is used to perform data extraction, data transfer, business adaptation and data storage on the data aggregated by the internet of things data unified aggregation layer. The internal data processing side is a four-level data processing link architecture composed of high-efficiency stream data processing middleware, data transfer system, business adaptation layer and data storage layer;

[0051] The technical architecture of the general technical architecture system is a three-level data system; the three-level data system comprises a first data link, a second data link and a third data link.

[0052] It should be noted that the end side sets five types of equipment for various energy system basic operation related equipment of building energy scene, when the energy system basic operation related equipment is accessed, the equipment is accessed according to the corresponding protocol according to the equipment type.

[0053] The edge side determines the corresponding three major solutions according to different business functions; the business function of the end side access equipment matches the corresponding solution, converts the communication protocol into MQTT protocol, and completes the specification unification before data aggregation.

[0054] In order to guarantee the consistency of subsequent data processing, the security of the Internet of Things platform and other requirements, before the data on the end side or the edge side is uploaded to the cloud, the external data processing side constructs an Internet of Things data unified aggregation layer for third-party systems (i.e. devices and services outside the cloud platform), which improves and unifies the communication protocols of third-party systems in this layer, and only provides a unified and unique data communication protocol, i.e. MQTT protocol. Through the innovative design of the data model, the data uploaded by the end side and the edge side and the third-party system can be aggregated according to the MQTT protocol specification, avoiding too much protocol processing in this layer, thereby generating a large amount of protocol adaptation development work, and even with the proliferation of devices, causing a large number of instability problems, and even a large amount of adaptation work after the data aggregation layer. Among them, the data of the end side and the edge side is the data generated by the end side access equipment, and the data of the third-party system is the data generated by the cloud cloud interface equipment. At the same time, this side also provides cloud cloud interface support, which is realized through the technical architecture of third-party system-Internet of Things protocol converter design (SDK2MQTT)-Internet of Things data unified aggregation, which provides an extensible access scheme for supporting more building energy data scene requirements, and better guarantees the sustainability of business support.

[0055] The internal data processing side is hidden under the external data processing side, with high reliability, high security and high performance technical requirements, and the internal processing side provides a four-level data processing link architecture to realize data processing on the data aggregated by the Internet of Things data unified aggregation layer, including data extraction, data transfer, business adaptation and data storage, which fully meets the technical standard requirements.

[0056] As Figure 3As shown, it is a complete architecture diagram of the general technical architecture system of building energy internet of things. First, the end side is bound with devices, including five categories. The data generated by the devices is received. The single independent networking device (such as an electric meter, a weather station, etc.) and the third party system device (generally accessed through an API) directly upload the generated data to the external data processing side of the cloud side through the MQTT protocol. The lower computer device (such as a DDC, a PLC, etc., generally supporting Modbus, Mbus, serial bus, etc. protocols), the upper computer access device (generally supporting OPC, BACnet, etc. protocols) and other customized devices (which are connected through customized protocols) need to convert the non-MQTT protocol of these devices into the MQTT protocol after matching the corresponding solutions on the edge side, and then upload the generated data to the external data processing side of the cloud side through the MQTT protocol. For the third party system accessed through cloud-to-cloud connection, the external data processing side improves and unifies the communication protocol of the third party system through the internet of things data unified gathering layer, and only provides a unified and unique data communication protocol, that is, the MQTT protocol. The data uploaded by the end side access device and the third party system is gathered based on the MQTT protocol. Finally, the data extracted, data transferred, business adapted and data stored by the internal data processing side through the four-level data processing link to the data gathered by the internet of things data unified gathering layer, complete the access of various energy system basic operation related devices of building energy scene, the conversion of communication protocol, and the storage of device uploaded data.

[0057] According to the embodiment of the present application, the end side is used to realize the access of various energy system basic operation related devices of building energy scene, including:

[0058] The end side determines the device type based on the device attribute of the energy system basic operation related device. The device type includes a single independent networking device, a lower computer device, an upper computer access device, a third party system device and other customized devices.

[0059] According to the analysis of the device type, the corresponding access protocol is selected to access the energy system basic operation related device to the end side.

[0060] It should be noted that the equipment related to the basic operation of various energy systems in the building energy scene is as follows: single independent networking equipment (such as electricity meters, weather stations, etc.), lower machine equipment (such as DDC, PLC, etc., generally supporting Modbus, Mbus, serial bus protocols, etc.), upper machine access equipment (generally supporting OPC, BACnet protocols, etc.), third-party system equipment (generally accessed through API), and other customized equipment (which is connected through a customized protocol), through the analysis of the equipment type, the corresponding access protocol is selected, and the equipment related to the basic operation of the energy system is accessed to the side, which can well solve the various equipment access problems faced by the building energy scene.

[0061] According to the embodiment of the application, the side is used for realizing the unified management of the end-side access equipment before data aggregation, and converting the communication protocol of the end-side access equipment into the MQTT protocol, which comprises the following steps:

[0062] The side determines a solution based on the business function of the end-side access equipment; the solution comprises a hard gateway access solution, a hardware server access solution and an edge computing node access solution.

[0063] According to the analysis of the business function of the end-side access equipment, the corresponding solution is selected to complete the unified management of the end-side access equipment before data aggregation.

[0064] It should be noted that the traditional Internet of Things platform architecture is easy to ignore the design of the side, based on the in-depth understanding of the Internet of Things platform and business analysis, the standard of the side design is innovatively put forward, that is, the solution is defined at the side, which is used for realizing wider access support, the solution comprises an access solution for a hard gateway (cloud gateway), an access solution for a hardware server (host, industrial computer) and an access solution for an edge computing node (edge controller), through the solution, wider access support and efficient connection of the equipment at the side to complete the unified management before data aggregation are realized.

[0065] The side is compatible with various devices (not only smart gateways) at the side, the core design of the side is to adopt the MQTT protocol for transmission, and in the transmission process, the data is converted into a data exchange target through a protocol analysis adapter; and for non-MQTT protocols, a soft gateway development protocol parser such as BacNET2MQTT is adopted to convert and normalize, so as to realize the unified management of the end-side access equipment before data aggregation.

[0066] According to the embodiment of the application, the efficient stream data processing middleware extracts data from MQTT through the MQTT-Kafka connection component, and stores the obtained data into the data transfer system.

[0067] It should be noted that the MQTT represents the data uploaded to the external data processing side by the end-side access device and the third-party system and converged via the Internet of Things data unified convergence layer, the efficient stream data processing middleware refers to the data extracted from the MQTT and stored in the data transfer system through the MQTT-Kafka connection component, and the problems such as data accumulation and blockage are avoided.

[0068] According to the embodiment of the application, the data transfer system adopts Kafka as the basic technical support middleware of the data transfer system, performs data transfer on the data stored in the data transfer system through Kafka-Topic storage specification, obtains transferred data, and extracts the latest periodic data from the data transfer system through the ETL service and puts the periodic data into the data warehouse or interfaces with other data forwarding sources.

[0069] It should be noted that the data transfer system refers to the basic technical support middleware of the data transfer system adopting Kafka, and the data transfer is completed through Kafka-Topic storage specification; when other systems are interrupted, the data transfer system can retain data, and when other systems are recovered, the data transfer system can extract data to realize system-level recovery; as shown in Figure 3 The data transfer system has high expansibility, and the latest periodic data can be extracted from the data transfer system into the data warehouse or interfaced with other data forwarding sources through the ETL (Extraction Transformation Loading) service.

[0070] According to the embodiment of the application, the business adaptation layer is built by using the IOT-HUB business adapter, and the transferred data is adapted by the business adaptation layer.

[0071] It should be noted that, as shown in Figure 5The diagram shows the IoT-HUB service adapter for the general technical architecture of the Building Energy Internet of Things (IoT). The IoT-HUB service adapter extracts data via Kafka consumption, performs protocol adaptation using a protocol parser and service adapter, and then uses a DB connector to manage IoT data according to rules. The service adaptation layer is built using the IoT-HUB service adapter, implementing core functions such as Kafka consumption, protocol parsing, service adaptation, and a rule engine. It efficiently extracts and assembles relay data from Kafka and loads it into a pre-defined data storage layer. For example, standalone networked devices and third-party system devices directly upload MQTT messages to the cloud via the MQTT protocol. The protocol data within the MQTT varies depending on the device type and manufacturer. When the relay data corresponding to this MQTT reaches the internal data processing side, the IoT-HUB service adapter parses the message body within the relay data corresponding to the MQTT, adapting it to various protocols based on business characteristics and protocol features. The IoT-HUB service adaptation layer adopts an adapter concept, providing greater scalability and supporting writing to multiple data sources.

[0072] According to an embodiment of the present invention, the data storage layer dynamically expands the service adapter to load data from multiple data sources in the relay data based on the service adaptation of the relay data.

[0073] It should be noted that the data storage layer is freely expandable, depending on business needs. Business adapters can be dynamically expanded to load data from more data sources, including various data storage units such as TDengine, Redis, and Kafka, achieving true on-demand storage and expansion with business needs.

[0074] According to an embodiment of the present invention, a first data link is used to store real-time data, a second data link is used to store recent data, and a third data link is used to store all data.

[0075] It should be noted that the conventional IoT technical architecture basically only includes a two-level data system: the first data link (real-time data) and the third data link (full data). The limitation of the conventional technical architecture is that it lacks the ability to cache and temporarily store recent data. When periodic data is needed, business logic needs to be redeveloped, which increases development costs significantly. At the same time, when the third-level data link fails, the data in the first link is prone to loss. Therefore, by building a second data link (recent data) between the two data links, a three-level link data architecture can be formed, which can solve the above problems very efficiently.

[0076] like Figure 4 The diagram shown is a three-level data link diagram of the general technical architecture of the building energy Internet of Things.

[0077] The first data link includes data uploaded through the end side or the edge side and data uploaded by the policy execution engine, and the external data processing side provides the Internet of Things data unified convergence layer, and the protocols uploaded by the end side, the edge side and the policy execution engine are improved and unified into the MQTT protocol;The second data link is the data of the data transfer system;The third data link data is the data of the data storage layer.

[0078] The policy execution engine is used to realize safer and more reliable control of the Internet of Things device:The conventional Internet of Things architecture focuses on collection and light control, and generally only realizes basic control, such as control instruction-MQTT protocol-device. This basic architecture can meet the basic business requirements, but it is not reliable and safe in the face of complex control, especially in the face of building energy intelligent control scenarios. By designing a policy execution engine service between the control instruction and the MQTT protocol, the business requirements can be met under the premise of reliable and safe control.

[0079] According to the embodiment of the application, the Internet of Things data unified convergence layer provides a data model;The data model includes an edge node model, an Internet of Things device model and a progressive data model;The progressive data model includes a basic data model, a standard data model and a unified data model;

[0080] The basic data model is used for analyzing raw data;

[0081] The standard data model introduces key attributes based on the basic data model, and is used for data protocol optimization;

[0082] The unified data model introduces business data based on the standard data, and is used for data isolation.

[0083] It should be noted that the data model is designed in the Internet of Things data unified convergence layer, and various protocols and data are accessed according to the data model to achieve the goal of unification. The data model includes an edge node model, an Internet of Things device model and a progressive data model;The progressive data model includes a basic data model, a standard data model and a unified data model.

[0084] The basic data model is generally limited to the default data of the device itself or third-party devices or systems, and this data model presents multiple changes. The protocol adapter needs to be able to utilize the characteristics of the protocol to realize step-by-step analysis and complete compatibility. For example, the protocol of a certain hardware gateway contains a lot of redundant ver, pKey, sn and other information, which needs to be simplified and optimized.

[0085] The standard data model is a process of standardizing the basic data model. Through deep analysis and refinement of the basic data model, the standard model layer retains strong and key attributes to ensure that the basic business requirements are met. In the standard data model, key attributes such as flag, msgId, and cid are introduced to further optimize the data protocol and retain important data for subsequent data use and database storage.

[0086] In the unified data model, business data is introduced, including project ID and data grouping ID, to perform final processing for subsequent final database storage and forwarding. With these business data, the flow target can be controlled and data physical isolation and other business requirements can be achieved.

[0087] The edge node model is constructed according to the following model specifications:

[0088] {prefix} / {scenario identifier} / {manufacturer protocol identifier} / {manufacturer protocol version code} / {project ID} / {data grouping ID} / {function identifier} / {function value}.

[0089] Model interpretation:

[0090] {prefix}: Default is Internet of Things: / iot.

[0091] {scenario identifier}:

[0092] Electric power scenario: electric,

[0093] Other scenarios: default.

[0094] {manufacturer protocol identifier}:

[0095] For example, China Electric is the default cet-mqtt, and the middle "-" represents a direct connection MQTT device,

[0096] The protocol code configured by the R&D and operation background is used as the standard.

[0097] {manufacturer protocol version code}:

[0098] For example, if China Electric's protocol uses two versions, such as v1.0 and v1.1, we define 1 and 2 respectively,

[0099] If there is no version number, the default is 1,

[0100] In order to reduce the Topic level, it has been combined into one.

[0101] {project ID}: distinguished by project.

[0102] {data grouping ID}:

[0103] Gateway data packet as the standard, recommended with 2000 signal as the benchmark, more than the group on the upload, such as group ID is 10001,

[0104] Integrated business can be grouped in subsystem.

[0105] {Load balancing identification}: when the Topic data volume overload, new projects can go through another consumer channel, the default is 100.

[0106] {Function identification}: follow-up can be based on Topic to design more function identification, this time only define service, representing services.

[0107] {Function value}: the basic type is currently data reporting, status reporting, data delivery, history reporting, etc.

[0108] Data reporting: upload,

[0109] Status reporting: status,

[0110] Data delivery: down,

[0111] History reporting: history,

[0112] Event reporting: event,

[0113] Heartbeat reporting: keepalive,

[0114] Power loss alarm: power-loss-alarm.

[0115] Gateway as follows:

[0116] Data reporting: / iot / electric / cet-mqtt-2 / 100003 / 10001 / 100 / service / u,

[0117] Status reporting: / iot / electric / cet-mqtt-2 / 100003 / 10001 / 101 / service / s,

[0118] Data delivery: / iot / electric / cet-mqtt-1 / 100003 / 10001 / 101 / service / d,

[0119] History reporting: / iot / electric / cet-mqtt-2 / 100003 / 10001 / 101 / service / h.

[0120] Take the soft gateway as an example: (take bacnet as an example)

[0121] Data reporting: / iot / default / bacnet2mqtt-1 / 100003 / 10001 / 101 / service / u,

[0122] State reporting: / iot / default / bacnet2mqtt-1 / 100003 / 10001 / 101 / service / s,

[0123] Data delivery: / iot / default / bacnet2mqtt-1 / 100003 / 10001 / 101 / service / d,

[0124] History reporting: / iot / default / bacnet2mqtt-1 / 100003 / 10001 / 101 / service / h.

[0125] About other special events:

[0126] Heartbeat reporting: / iot / cet-mqtt / {sn} / service / k,

[0127] Power failure alarm: / iot / cet-mqtt / {sn} / service / p.

[0128] The model of Internet of Things equipment is constructed according to the following model specification:

[0129] {prefix} / {manufacturer protocol identifier} / {manufacturer protocol version code} / {project ID} / {data group ID} / {data type}.

[0130] Model interpretation:

[0131] {prefix}: Default for Huode Wisdom Internet of Things: / iot.

[0132] {manufacturer protocol identifier}: Default for sdk2mqtt, for example, black ant, which is equivalent to default access data from black ant SDK and convert to MQTT.

[0133] {product type code}: According to the general object model architecture, it should be 1 object model 1 table. The original design is not linked, and we are mainly in the gateway scenario. Some linkage design will optimize the use of data. Take indoor temperature and humidity sensor product as an example: code temp_hr, which can also correspond to product class identifier or code.

[0134] {Load balancing identifier}: The default value is 100, and subsequent 101 can be extended (when the number of single Topic access devices is too large, load balancing can be achieved).

[0135] {Function identifier}: Subsequent Topic-based function identifiers can be designed, and only service is defined this time, representing service.

[0136] {Function value}: The basic types at present are data reporting, state reporting, heartbeat reporting, and data delivery.

[0137] Enter a specific table and gradually modelize:

[0138] Take indoor temperature and humidity sensor as an example:

[0139] Data reporting: / iot / sdk2mqtt / temp_hr / 100 / service / u,

[0140] State reporting: / iot / sdk2mqtt / temp_hr / 100 / service / u,

[0141] Heartbeat reporting: / iot / sdk2mqtt / temp_hr / 101 / service / u,

[0142] Data delivery: / iot / sdk2mqtt / temp_hr / 102 / service / u.

[0143] Take indoor temperature and humidity sensor as an example:

[0144] Data reporting: / iot / sdk2mqtt / temp_hr / 100 / service / u,

[0145] State reporting: / iot / sdk2mqtt / temp_hr / 100 / service / u,

[0146] Heartbeat reporting: / iot / sdk2mqtt / temp_hr / 101 / service / u,

[0147] Data delivery: / iot / sdk2mqtt / temp_hr / 102 / service / u.

[0148] The basic data model is constructed according to the following model specification:

[0149] {

[0150] "ver": "2.x",

[0151] "pKey": "",

[0152] "sn": "NT001",

[0153] "ts": 1726489531,

[0154] "devs": [

[0155] {

[0156] "dev": "11F General Lighting",

[0157] "ts": 1726489531,

[0158] "d": [

[0159] {

[0160] "m": "1713177651031001",

[0161] "ts": 1726489531,

[0162] "v": 0.6

[0163] } ]

[0165] } ]

[0167] }

[0168] The standard data model is constructed according to the following model specifications:

[0169] {

[0170] "flag": "",

[0171] "data": [

[0172] {

[0173] "cid": "N1000001",

[0174] "v": "66.6",

[0175] "s": 1594281513,

[0176] "dq": 1

[0177] },

[0178] {

[0179] "cid": "N1000002",

[0180] "v": "62.1",

[0181] "s": 1594281513,

[0182] "dq": 0

[0183] } ]

[0185] }。

[0186] The unified data model is constructed according to the following model specification:

[0187] Protocol analysis: {start bit} {device identification} {business scenario code} {project ID} {data packet ID} {load balancing flag} {business identification} {execution action}.

[0188] Protocol content:

[0189] {

[0190] "data": [

[0191] {

[0192] "cid": "G100020",

[0193] "v": "123",

[0194] "ts": 1726489531

[0195] },

[0196] {

[0197] "cid": "G100020",

[0198] "v": "123",

[0199] "ts": 1726489531

[0200] } ]

[0202] }。

[0203] Figure 2 A flow chart of a general technical architecture method based on building energy Internet of Things is shown.

[0204] As Figure 2 shown, the second aspect of the present application provides a general technical architecture method based on building energy Internet of Things, comprising:

[0205] S21, determining a device type according to a device attribute of the energy system basis operation related device on the terminal side, selecting a corresponding access protocol, and accessing the energy system basis operation related device to the terminal side;

[0206] S22, converting a communication protocol of the terminal side accessed device into an MQTT protocol according to a service function of the terminal side accessed device on the edge side, and uploading data generated by the terminal side accessed device to an external data processing side of the cloud side based on the MQTT protocol;

[0207] S23, constructing an Internet of Things data unified convergence layer before data on the terminal side or the edge side is uploaded to the cloud side by the external data processing side of the cloud side, converting a communication protocol of a third party system into an MQTT protocol in the Internet of Things data unified convergence layer, and converging data uploaded by the terminal side, the edge side and the third party system to the Internet of Things data unified convergence layer based on a protocol specification of the MQTT protocol;

[0208] S24, extracting data converged by the Internet of Things data unified convergence layer to a data relay system for data relay by a high-efficiency streaming data processing middleware of the internal data processing side of the cloud side, and storing the obtained relay data to a data storage layer by a business adaptation layer.

[0209] In several embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. The device embodiments described above are only schematic, for example, the division of units is only a logical function division, and actual implementation can have another division manner, such as: multiple units or components can be combined, or can be integrated into another system, or some features can be ignored, or not executed. In addition, the coupling or direct coupling or communication connection between the various components shown or discussed can be through some interface, indirect coupling or communication connection of the devices or units, which can be electrical, mechanical or other forms.

[0210] The units described above as separate components can or can not be physically separated, and the components shown as units can or can not be physical units; they can be located in one place, or distributed on multiple network units; some or all of the units can be selected according to actual needs to achieve the purpose of the embodiment.

[0211] In addition, each functional unit in each embodiment of the present application can be integrated into one processing unit, or each unit can be a unit alone, or two or more units can be integrated into one unit; the integrated unit can be realized in the form of hardware or in the form of hardware plus software functional unit.

[0212] Those skilled in the art can understand that all or part of the steps of the above-mentioned method embodiments can be completed by relevant hardware of program instructions, and the foregoing program can be stored in a computer readable storage medium, and the program executes the steps of the above-mentioned method embodiments when executed; and the foregoing storage medium includes: a mobile storage device, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, and various media that can store program codes.

[0213] Alternatively, the integrated unit of the present application can also be stored in a computer readable storage medium if it is realized in the form of a software function module and sold or used as an independent product. Based on such understanding, the technical solutions of the embodiments of the present application can be embodied in the form of a software product, and the computer software product is stored in a storage medium, includes several instructions to make a computer device (which can be a personal computer, a server, or a network device, etc.) execute all or part of the embodiments of the method of the present application. The foregoing storage medium includes: a mobile storage device, a ROM, a RAM, a magnetic disk or an optical disk, and various media that can store program codes.

Claims

1. A general technical architecture system based on building energy Internet of Things, characterized in that, The general technical architecture system comprises: an end side, a side side and a cloud side; the cloud side comprises an external data processing side and an internal data processing side; The end side is used for realizing access to various energy system basic operation related devices of a building energy scene; The side side is used for realizing standardized and unified management of the end side access devices before data aggregation, and converting the communication protocol of the end side access devices into an MQTT protocol; The external data processing side is used for constructing an Internet of Things data unified aggregation layer before clouding of data of the end side or the side side, converting the communication protocol of a third party system into an MQTT protocol in the Internet of Things data unified aggregation layer, and aggregating data uploaded by the end side, the side side and the third party system to the Internet of Things data unified aggregation layer based on the protocol specification of the MQTT protocol; the external data processing side is a technical architecture for third party system-Internet of Things protocol converter-cloud end deployment docking; The internal data processing side is used for data extraction, data transfer, business adaptation and data storage of data aggregated by the Internet of Things data unified aggregation layer; the internal data processing side is a four-level data processing link architecture composed of an efficient stream data processing middleware, a data transfer system, a business adaptation layer and a data storage layer; The technical architecture of the general technical architecture system is a three-level data system; the three-level data system comprises a first data link, a second data link and a third data link; The first data link is used for storing real-time data, the second data link is used for storing recent data, and the third data link is used for storing full-amount data. 2.The general technical architecture system based on building energy Internet of Things according to claim 1, wherein, The end side is used for realizing access to various energy system basic operation related devices of a building energy scene, comprising: The end side determines the device type based on the device attribute of the energy system basic operation related device; the device type comprises a single independent networking device, a lower computer device, an upper computer access device, a third party system device and other customized devices; According to the analysis of the device type, a corresponding access protocol is selected to access the energy system basic operation related device to the end side. 3.The general technical architecture system based on building energy internet of things according to claim 1, wherein, The side side is used for realizing standardized and unified management of the end side access devices before data aggregation, and converting the communication protocol of the end side access devices into an MQTT protocol, comprising: The side side determines a solution based on the business function of the end side access device; the solution comprises a hard gateway access solution, a hardware server access solution and an edge computing node access solution; According to the analysis of the business function of the end side access device, a corresponding solution is selected, and the communication protocol of the end side access device is converted into an MQTT protocol according to the corresponding solution.

4. The general technical architecture system based on building energy internet of things according to claim 1, characterized in that, The efficient stream data processing middleware extracts data from MQTT through an MQTT-Kafka connection component, and stores the obtained data into the data transfer system. 5.The general technical architecture system based on building energy internet of things according to claim 4, characterized in that, The data transfer system adopts Kafka as the basic technical support middleware of the data transfer system, and stores the data transferred into the data transfer system through Kafka-Topic storage specification to obtain the transferred data; the latest periodic data can also be extracted from the data transfer system through ETL service, and the periodic data is put into a data warehouse or connected with other data forwarding sources. 6.The general technical architecture system based on building energy internet of things according to claim 5, wherein, The service adaptation layer is built using an IOT-HUB service adapter, and the transferred data is adapted through the service adaptation layer. 7.The general technical architecture system based on building energy internet of things according to claim 6, wherein, The data storage layer dynamically expands the service adapter based on the service adaptation of the transferred data to load the data of multiple data sources in the transferred data. 8.The general technical architecture system based on building energy internet of things according to claim 1, wherein, The Internet of Things data unified convergence layer provides a data model; the data model includes an edge node model, an Internet of Things device model, and a progressive data model; the progressive data model includes a basic data model, a standard data model, and a unified data model; The basic data model is used for analyzing original data; The standard data model introduces key attributes based on the basic data model, and is used for data protocol optimization; The unified data model introduces business data based on the standard data, and is used for data isolation.

9. A general technical architecture method based on building energy internet of things, applying a general technical architecture system based on building energy internet of things according to any one of claims 1-8, characterized in that, Comprise: Determine the type of equipment by the equipment attribute of the equipment related to the basic operation of the energy system on the end side, select the corresponding access protocol, and access the equipment related to the basic operation of the energy system on the end side; According to the business function matching corresponding solutions of the equipment access device on the end side, the communication protocol of the equipment access device on the end side is converted into MQTT protocol, and the data generated by the equipment access device on the end side is uploaded to the external data processing side of the cloud side based on the MQTT protocol; The external data processing side of the cloud side constructs an Internet of Things data unified convergence layer on the data of the end side or the edge side before uploading to the cloud, converts the communication protocol of the third party system into MQTT protocol in the Internet of Things data unified convergence layer, and aggregates the data uploaded by the end side, the edge side and the third party system to the Internet of Things data unified convergence layer based on the protocol specification of MQTT protocol; The data aggregated by the Internet of Things data unified convergence layer is extracted to the data transfer system for data transfer through the efficient stream data processing middleware of the internal data processing side of the cloud side, and the transferred data is stored to the data storage layer through the service adaptation layer.

Images