Building energy management system and method

Abstract

The invention relates to a building energy management system and method. The system comprises an acquisition module and a data management center module, the data management center module comprises a protocol gateway unit and a communication unit; the acquisition module is used for performing data acquisition processing on the terminal equipment in the to-be-managed building according to the configuration file to obtain initial equipment data; the protocol gateway unit is used for performing format conversion and edge calculation on the initial equipment data to obtain target equipment data; the communication unit is used for sending the target equipment data to the control platform, responding to a control instruction determined by the control platform according to the target equipment data, and disassembling the control instruction into a target control instruction; and the protocol gateway unit is used for converting the target control instruction into a data format corresponding to the terminal equipment, and issuing the converted target control instruction to the corresponding terminal equipment. According to the invention, acquisition, protocol conversion, edge calculation, communication and control are integrated together, and the problem of data islands caused by a plurality of independent subsystems is eliminated.

Description

Technical Field

[0001] This application relates to the field of building smart energy systems technology, and in particular to a building energy management system and method. Background Technology

[0002] Building smart energy systems refer to the use of intelligent technologies to achieve refined monitoring and control of energy consumption of various terminal devices in one or more buildings, including energy monitoring, energy management, and intelligent control. This technology can effectively optimize energy utilization and achieve energy conservation and emission reduction.

[0003] In related technologies, to meet diverse management needs, multiple independent subsystems are introduced into building smart energy systems. For example, the data acquisition subsystem relies on dedicated meters and other equipment; the data communication subsystem relies on independently deployed middleware platforms and transmission networks; the data analysis and calculation subsystem relies on backend servers or cloud computing services; and the control of terminal devices is achieved by a fixed building automation subsystem. These subsystems are separated in hardware, incompatible in software and data, and have incompatible communication protocols. This results in data being processed in different systems within the building, and the integration between these subsystems is complex and costly. Consequently, the data is scattered, difficult to integrate, and ultimately, difficult to control the various terminal devices within the building in a unified manner. Summary of the Invention

[0004] Therefore, it is necessary to provide a building energy management system and method to address the aforementioned technical problems.

[0005] In a first aspect, this application provides a building energy management system, which integrates: a data acquisition module and a data management center module; wherein the data management center module includes a protocol gateway unit and a communication unit;

[0006] The acquisition module is used to collect and process data from various terminal devices in the building to be managed according to a preset configuration file, so as to obtain initial device data.

[0007] The protocol gateway unit is used to perform format conversion and edge computing processing on the initial device data to obtain target device data;

[0008] The communication unit is used to send the target device data to a preset control platform, and in response to the control command determined by the control platform based on the target device data, decompose the control command into target control commands corresponding to each terminal device;

[0009] The protocol gateway unit is further configured to convert the target control command into a data format corresponding to each terminal device, and send the converted target control command to the corresponding terminal device at a preset frequency.

[0010] In one embodiment, the system further includes a metadata management unit and a data space register unit;

[0011] The metadata management unit is used to establish metadata information corresponding to the terminal device;

[0012] The data space register unit is used to acquire target device data corresponding to the terminal device, bind and store the target device data with the corresponding timestamp information and device identification information, and associate the bound and stored data with the corresponding metadata information.

[0013] In one embodiment, the system further includes a message storage unit;

[0014] The message storage unit is used to read persistent device data within a preset time period stored in the data space register unit and store the persistent device data in a preset storage system.

[0015] In one embodiment, the system further includes a configuration unit;

[0016] The configuration unit is used to determine configuration data for each acquisition module and generate a configuration file corresponding to each acquisition module based on the configuration data.

[0017] The configuration unit is also used to distribute the configuration file to the corresponding acquisition module.

[0018] In one embodiment, the data management center module includes a device management unit:

[0019] The device management unit is used to obtain the registration request of the acquisition module to be verified, and determine the access token of the acquisition module to be verified based on the registration request.

[0020] The device management unit is also used to generate network access information for the corresponding collection module to be verified when the access token is detected to be valid, and to bind the network access information to the collection module to be verified.

[0021] In one embodiment, the protocol gateway unit is further configured to establish a communication channel between the acquisition module to be verified and the protocol gateway unit.

[0022] Secondly, this application also provides a building energy management system deployed on the edge side, including at least one data acquisition module deployed locally on the building, and a data management center module deployed locally on the building as described in any of the above.

[0023] Thirdly, this application also provides a cloud-edge collaborative building energy management system, the system including at least one data acquisition module deployed locally on the building, and a data management center module deployed in the cloud as described in any of the above.

[0024] Fourthly, this application also provides a regionally centralized building energy management system, including multiple data acquisition modules deployed in different buildings, and a centralized data management center module deployed in a preset area as described in any of the above, wherein the data management center module is communicatively connected to each of the data acquisition modules, and the preset area includes multiple buildings on which the data acquisition modules are deployed.

[0025] Fifthly, this application also provides a building energy management method, applied to a building energy management system as described in any of the above claims, the method comprising:

[0026] Data is collected and processed from various terminal devices in the building to be managed according to the preset configuration file to obtain initial device data;

[0027] The initial device data is subjected to format conversion and edge computing processing to obtain the target device data;

[0028] The target device data is sent to a preset control platform. In response to the control command determined by the control platform based on the target device data, the control command is decomposed into target control commands corresponding to each terminal device. The target control commands are converted into data formats corresponding to each terminal device, and the converted target control commands are sent to the corresponding terminal devices at a preset frequency.

[0029] The aforementioned building energy management system and method integrate a data acquisition module and a data management center module. The data management center module includes a protocol gateway unit and a communication unit. The data acquisition module is used to acquire and process data from various terminal devices in the building under management according to a preset configuration file to obtain initial device data. The protocol gateway unit is used to perform format conversion and edge computing processing on the initial device data to obtain target device data. The communication unit is used to send the target device data to a preset control platform. In response to control instructions determined by the control platform based on the target device data, the control instructions are decomposed into target control instructions corresponding to each terminal device. The protocol gateway unit is also used to convert the target control instructions into data formats corresponding to each terminal device and send the converted target control instructions to the corresponding terminal devices at a preset frequency. The building energy management system in this embodiment integrates data acquisition, protocol conversion, edge computing, communication, and control, fundamentally eliminating the data silo problem caused by multiple independent subsystems in traditional solutions. Furthermore, this application, based on the configuration file-based data collection method and the data conversion capabilities of the protocol gateway, enables the integration with different types of terminal devices without requiring equipment replacement or in-depth customized development, saving initial construction costs and reducing the technical difficulty of project implementation. Moreover, this application utilizes the protocol gateway unit for edge computing processing, enabling rapid response to anomalies and preliminary data cleaning and calculation, thus reducing subsequent computational load. Attached Figure Description

[0030] To more clearly illustrate the technical solutions in the embodiments of this application or related technologies, the drawings used in the description of the embodiments of this application or related technologies will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0031] Figure 1 This is a schematic diagram of the building energy management system in one embodiment;

[0032] Figure 2 This is a schematic diagram illustrating the interaction between the data acquisition module and the building energy management system in one embodiment.

[0033] Figure 3 This is a schematic diagram of the structure of a third-party cloud platform, a building energy management system, and terminal equipment in one embodiment;

[0034] Figure 4 This is a flowchart illustrating a building energy management method in one embodiment. Detailed Implementation

[0035] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0036] The following explains the technical background of this application.

[0037] Building smart energy systems refer to the use of intelligent technologies to achieve refined monitoring and control of energy consumption of various terminal devices in one or more buildings, including energy monitoring, energy management, and intelligent control. This technology can effectively achieve optimized energy utilization and energy conservation and emission reduction. On the one hand, it achieves optimized energy utilization and energy conservation and emission reduction through the management and control strategies of building smart energy systems; on the other hand, it participates in demand response services during peak electricity consumption periods and obtains electricity market revenue through intelligent control and flexible adjustment of energy-consuming equipment. This is of great significance to the safe and stable operation of new power systems.

[0038] In related technologies, building smart energy systems are quite complex, involving multiple parameters, time granularities, multi-subsystem protocol interfaces, and multi-platform interactions. For example, the data acquisition subsystem relies on dedicated meters and other equipment, the data communication subsystem relies on independently deployed middleware platforms and transmission networks, the data analysis and computing subsystem relies on backend servers or cloud computing services, and the control of terminal devices is achieved by a fixed building automation subsystem. These subsystems are separated in hardware, incompatible in software and data, and incompatible in communication protocols.

[0039] In summary, the above description illustrates the main problems existing in the relevant technologies: the connection between different subsystems in the building smart energy system is complex and costly, which leads to data being relatively scattered and difficult to integrate, thus making it difficult to uniformly control various terminal devices in the building.

[0040] Based on this, this application provides a building energy management system, which integrates a data acquisition module and a data management center module. The data management center module includes a protocol gateway unit and a communication unit. The data acquisition module is used to acquire and process data from various terminal devices in the building under management according to a preset configuration file to obtain initial device data. The protocol gateway unit is used to perform format conversion and edge computing processing on the initial device data to obtain target device data. The communication unit is used to send the target device data to a preset control platform, and in response to the control instructions determined by the control platform based on the target device data, decompose the control instructions into target control instructions corresponding to each terminal device. The protocol gateway unit is also used to convert the target control instructions into data formats corresponding to each terminal device and send the converted target control instructions to the corresponding terminal devices at a preset frequency. This application integrates data acquisition, communication, edge computing, and control into a unified building energy management system, avoiding the problems of data incompatibility and protocol incompatibility between different independent subsystems, and achieving efficient acquisition of multi-source data, unified device control, and efficient coordinated control. See the following embodiments for details:

[0041] The building energy management system provided in this application embodiment, such as Figure 1 As shown, the system integrates: a data acquisition module 10 and a data management center module 20; wherein the data management center module 20 includes a protocol gateway unit 21 and a communication unit 22.

[0042] The data acquisition module 10 is used to collect and process data from various terminal devices in the building to be managed according to a preset configuration file, so as to obtain initial device data.

[0043] The aforementioned building energy management system is generally deployed within at least one building (such as a large commercial complex). The acquisition module 10 refers to an acquisition device or edge control unit that directly reads raw data from physical devices (such as electricity meters) within the building; this module is typically deployed locally within the building. The aforementioned data management center module 20 is used to process, store, and convert the acquired data, and to control various terminal devices within the building. This data management center can be deployed locally within the building or in the cloud. The aforementioned configuration file corresponds to the acquisition module 10. Data is collected according to the rules specified in the configuration file. For example, the configuration file can specify the acquisition targets (such as the parameters of the electricity meters in the distribution cabinet, the charging and discharging power of energy storage devices, and the state of charge), the acquisition frequency, etc. This configuration file can be pre-generated by relevant technical personnel using configuration tools. The aforementioned terminal devices are the various devices or subsystems within the building to be managed, such as mains power, energy storage subsystems, photovoltaic subsystems, lighting subsystems, and power subsystems.

[0044] In this embodiment of the application, each acquisition module 10 performs data acquisition and processing on the corresponding terminal device according to a preset configuration file to obtain initial device data, which is raw data that has not been processed.

[0045] Protocol gateway unit 21 is used to perform format conversion and edge computing processing on the initial device data to obtain target device data.

[0046] The protocol gateway unit 21 supports data format conversion and forwarding between terminal devices with different communication protocols, custom data formats, and even completely different data structures. It can understand and convert various protocols, transforming different types of data into a preset, unified format for easier subsequent analysis and processing. Furthermore, the protocol gateway unit also supports edge computing processing of initial device data, including but not limited to data cleaning (e.g., filtering out obviously unreasonable data), data aggregation (i.e., performing basic calculations based on initial device data, such as calculating the power consumption of each terminal device, the total power consumption of the building, etc.), and limit violation detection.

[0047] In summary, the protocol gateway unit 21 converts the collected initial device data into target device data.

[0048] The communication unit 22 is used to send target device data to a preset control platform, and in response to the control command determined by the control platform based on the target device data, decompose the control command into target control commands corresponding to each terminal device.

[0049] The control platform is a pre-set third-party cloud platform.

[0050] In this embodiment, the communication unit 22 sends target device data to the control platform via a preset network protocol. Upon receiving the target device data, the control platform analyzes and makes decisions based on the overall data. When it determines that load adjustment of the building is necessary, it generates a corresponding macro-level control target (e.g., reducing the total building load by 100 kW within one hour). Based on this control target, it determines a control command, which instructs each terminal device in the managed building to meet the aforementioned control target, and then sends the control command to the communication unit 22. In summary, the communication unit 22 achieves seamless integration between different systems and multi-platform data interaction, ensuring compatibility, security, and efficient communication. It also has cloud access capabilities, playing a crucial role in bridging the gap between different systems.

[0051] The communication unit 22 breaks down the control command into specific, executable actions, such as raising the set temperature of the No. 1 air conditioning unit by 1°C, starting the energy storage system to discharge 40kW, etc., thereby obtaining the target control command corresponding to each terminal device.

[0052] The protocol gateway unit 21 is also used to convert the target control command into the data format corresponding to each terminal device, and send the converted target control command to the corresponding terminal device at a preset frequency.

[0053] In this embodiment, after disassembly, the protocol gateway unit 21 receives these target control commands, converts them into a data format of a specific protocol that the terminal devices can recognize, and sends them to the corresponding terminal devices at a preset frequency, so that each terminal device can execute the corresponding control commands. The use of a predetermined preset sending frequency is to avoid impacting the terminal devices.

[0054] The building energy management system in this embodiment integrates data acquisition, protocol conversion, edge computing, communication, and control, fundamentally eliminating the data silos caused by multiple independent subsystems in traditional solutions. Furthermore, the data acquisition method based on configuration files and the data conversion capabilities of the protocol gateway allow for seamless integration with different types of terminal devices without requiring equipment replacement or in-depth custom development, saving initial construction costs and reducing the technical difficulty of project implementation. Moreover, the edge computing processing via the protocol gateway unit 21 enables rapid response to anomalies and preliminary data cleaning and calculation, reducing subsequent computational load.

[0055] In one exemplary embodiment, the system further includes a metadata management unit and a data space register unit;

[0056] The metadata management unit is used to establish metadata information corresponding to the terminal device;

[0057] The data space register unit is used to acquire target device data corresponding to the terminal device, bind and store the target device data with the corresponding timestamp information and device identification information, and associate the bound and stored data with the corresponding metadata information.

[0058] The metadata management unit manages the metadata information corresponding to each terminal device. The device identification information mentioned above is a unique code or string that identifies a terminal device.

[0059] Based on the register size configuration, a temporary data storage space is generated during initialization, and the validity period of the data is set. The target device data collected from each terminal device is recorded one by one.

[0060] In this embodiment, metadata information corresponding to the terminal devices is first established. In one embodiment, a list of all terminal devices to be connected within the building and their data point attributes (i.e., clearly defining the business meaning of each piece of data to avoid ambiguity) can be imported in the form of a table or configuration file using a dedicated metadata configuration tool. In another embodiment, when a new terminal device connects to the system, the protocol gateway unit can proactively initiate a registration request to the metadata management unit, submitting the device's description information. For example, if the terminal device is a chilled water pump, its metadata information could include: device identifier, installation location, device model, system to which it belongs, and a standard device protocol template, etc.

[0061] After receiving target device data corresponding to the terminal device, the data space register unit generates corresponding timestamp information, which identifies the moment when the target device data is confirmed and processed by the system. The data space register identifies the corresponding terminal device from which the data originates, extracts the device identification information of that terminal device, and binds and stores the target device data, device identification information, and timestamp information, as well as associating it with metadata information. This enables the updating of temporary space data in the data space register unit based on newly acquired data; scheduled tasks parse and store data or package and store it according to a specified format; and consume produced data at a specified time.

[0062] In summary, if it is necessary to access the target device data in the future, the metadata management unit can be queried first to clarify the metadata information of the terminal device corresponding to the target device data. Then, the data space register unit can be queried for the historical data associated with the terminal device based on the metadata information and the data can be returned.

[0063] Through the embodiments of this application, the interpretability and standardization of data are achieved. Furthermore, since the metadata is stored centrally and uniformly, if the storage device information changes (such as device renaming or replacement), it only needs to be updated once in the metadata management unit. Similarly, when it is necessary to access new devices or data points, it is only necessary to register them in the metadata, and the system will have the ability to manage and use the new data, thereby enhancing the system's flexibility and scalability.

[0064] In one exemplary embodiment, the system further includes a message storage unit;

[0065] The message storage unit is used to read persistent device data within a preset time period stored in the data space register unit and store the persistent device data in a preset storage system.

[0066] The data space register unit, as defined in the above embodiments, is the core storage module used to bind and store target device data. It typically employs a high-performance time-series database to support real-time queries and recent data analysis. The persistent device data specifically refers to historical device data that has been bound and stored by the data space register unit. The preset time period can be preset by relevant technical personnel, such as being set to "the last 24 hours". The preset storage system is a pre-configured storage facility located outside the system for long-term data storage.

[0067] In this embodiment of the application, the aforementioned persistent device data includes, but is not limited to, change storage data (i.e., storage triggered when the value changes substantially) and timed storage data. The stored data includes key indicator calculation data storage, time series data calculation storage, and control command monitoring and distribution log data storage, thereby facilitating debugging and problem diagnosis.

[0068] Then, when the persistent storage task is triggered, a query request is sent to the register unit. The query request specifies the preset time period and additional device filtering conditions. Accordingly, after receiving the request, the register unit returns the data that meets the requirements to the message storage unit. The returned data maintains its complete binding structure.

[0069] The message storage unit re-formats, compresses, or packages data to achieve persistent data storage, and also has the ability to access cloud databases.

[0070] In one exemplary embodiment, the system further includes a configuration unit;

[0071] The configuration unit is used to determine the configuration data for each acquisition module and generate a configuration file corresponding to each acquisition module based on the configuration data.

[0072] The configuration unit is also used to distribute configuration files to the corresponding acquisition modules.

[0073] The configuration data determined by the configuration module includes, but is not limited to, the host computer's preset IP address and basic parameter configuration, the unit device's feature code (each device has a unique address ID), system type, the name of the unit's acquisition node, the name of the acquisition point, the device name, the acquisition point parameters (the acquisition parameters are determined according to the communication protocol and can be customized), the data reporting cycle, whether it is controllable, the unit controller's IP address, rated power, the power adjustable range (lower limit / upper limit), and the software version number.

[0074] This configuration unit can provide services via the web, offering an interactive interface for technical personnel to customize and plan the tasks of all acquisition modules, and to solidify these configuration data into executable configuration files and distribute them to the corresponding acquisition modules.

[0075] Specifically, the configuration file can be sent to the corresponding acquisition module via the system's communication unit according to a management protocol agreed upon with the target acquisition module, such as through a dedicated MQTT (Message Queuing Telemetry Transport) topic. The acquisition module then parses the message, extracts the configuration file, and loads it to make the new configuration effective.

[0076] In one embodiment, a specific process for distributing configuration files is given:

[0077] 1. After successful authentication, each data acquisition module first uploads its configuration file. Authentication is used to check whether a newly added data acquisition module is valid. The configuration file in this step contains the basic configuration information of the data acquisition module.

[0078] 2. Modify the IP of the central server to receive the data, that is, select one or more IP addresses and ports, which means that the data collection module will feed back the collected data to the preset platform / server.

[0079] 3. Generate the configuration file corresponding to the acquisition module through the configuration unit.

[0080] 4. Download the configuration file to the corresponding acquisition module.

[0081] 5. Restart the acquisition module, or it can be automatically restarted by default after the download is complete.

[0082] Furthermore, when a new terminal device is added, it is automatically updated in the configuration file of the data acquisition module, which mainly includes the serial number, name, application time, status (synchronized, not synchronized), operation, etc. of the new terminal device.

[0083] This application provides a unified configuration unit, which allows technicians to remotely configure and manage various acquisition modules, thereby improving management efficiency and reducing operation and maintenance costs.

[0084] In one exemplary embodiment, the data management center module includes a device management unit:

[0085] The device management unit is used to obtain the registration request of the acquisition module to be verified and determine the access token of the acquisition module to be verified based on the registration request.

[0086] The device management unit is also used to generate network access information for the corresponding data collection module to be verified when a valid access token is detected, and to bind the network access information to the data collection module to be verified.

[0087] In this embodiment, the function of the device management unit is defined, mainly for authorizing the acquisition module, specifically:

[0088] First, when a newly established data acquisition module to be verified is connected to the system, it actively sends a registration request to the system. After successful registration, the corresponding configuration file is set for it. Specifically, the registration process includes:

[0089] The acquisition module to be verified generates a registration request and sends it to the device management module. The device management module obtains the access token from the registration request. When the access token is verified, it performs security authorization. A common token strategy is to generate the token based on the IP address and device ID of the acquisition module to be verified.

[0090] Based on the above registration request, network access information is generated. A communication channel is established between the network access information and the data acquisition module to be verified. Through this channel, configuration information of the data acquisition module and modification and distribution of the configuration file can be obtained. Specifically, the data acquisition parameters obtained in the configuration file include fixed parameters and custom parameters. At the same time, the device management unit can subscribe to control command topics and parse and distribute them to the corresponding data acquisition module.

[0091] In one exemplary embodiment, the protocol gateway unit is further configured to establish a communication channel between the acquisition module to be verified and the protocol gateway unit.

[0092] Specifically, the aforementioned communication channel is established by the protocol gateway unit generating network access information based on the registration request, and establishing a communication channel between the acquisition module and the protocol network management unit based on the network access information.

[0093] It should be understood that although the modules in the structural diagrams of the embodiments described above are arranged sequentially, these functions are not necessarily executed in that order. Unless otherwise expressly stated herein, there is no strict order in which the functions of these modules are executed, and they may be executed in other orders.

[0094] Based on the same inventive concept, this application also provides a building energy management system for edge-side deployment of the building energy management system described above. The solution provided by this system is similar to the solution described in the above method; therefore, the specific limitations of one or more edge-side deployed building energy management system embodiments provided below can be found in the limitations of the building energy management system described above, and will not be repeated here.

[0095] In one exemplary embodiment, a building energy management system deployed at the edge is included, comprising at least one data acquisition module deployed locally on the building, and a data management center module deployed locally on the building as described above.

[0096] In this embodiment, the data management center module is deployed inside the building but remotely to the cloud; similarly, the acquisition module is also deployed locally within the building. Each acquisition module collects corresponding data according to preset configuration file requirements and sends it to the protocol gateway unit of the local server via the local area network. The protocol gateway unit performs protocol parsing, data cleaning, and edge computing (such as real-time calculation of the entire building's power) on the local server. The communication unit can then report the aggregated data to a third-party cloud platform for monitoring via a preset communication protocol. In summary, because both the acquisition module and the data management center module are deployed locally, this embodiment offers extremely fast response times, meeting real-time requirements. Furthermore, even if the external internet is interrupted, the system can still operate by directly controlling the terminal devices through the internal protocol gateway unit.

[0097] Figure 2 This is a schematic diagram illustrating the interaction between the data acquisition module and the building energy management system in one embodiment.

[0098] 1. After the data acquisition node is powered on, it sends a login request to the building energy management system to apply for system access.

[0099] 2. The protocol gateway unit receives the login request and forwards the device information of the acquisition module to the device management unit for registration. At the same time, the acquisition module subscribes to the control command topics it needs to receive from the host computer, laying the foundation for receiving control commands in the future.

[0100] 3. The device management unit verifies the token provided by the acquisition module according to the preset security policy and checks its validity. If valid, it proceeds to the next step; otherwise, it returns to step 1.

[0101] 4. After a successful connection, the protocol gateway module sends a response message to the acquisition module.

[0102] 5. The data acquisition module periodically collects relevant data from the terminal device according to its configuration file, and packages the data and sends it to the data topic specified by the host computer.

[0103] 6. The protocol gateway unit receives the topic subscription request sent by the acquisition module. After receiving the data sent by the acquisition module in step 5, it forwards the data to the data space register module for real-time caching. It may also trigger the message storage unit to write the data to the local historical database at the same time to complete persistent storage.

[0104] 7. When the host computer needs to control the terminal device, the message communication unit publishes the control command to the corresponding control topic that the acquisition module has subscribed to through the protocol gateway unit.

[0105] 8. After subscribing to the control topic, the acquisition module continuously monitors the connection with the host computer. When it detects that the host computer sends a control command as described in step 7, the acquisition module converts the command content into a specific device protocol and sends it to the connected terminal for execution.

[0106] In one exemplary embodiment, a cloud-edge collaborative building energy management system is included, comprising at least one data acquisition module deployed locally on the building, and a data management center module as described above deployed in the cloud.

[0107] In this embodiment, the data acquisition module is deployed locally on the building, while the data management center module is deployed in a virtual server or container cluster in the cloud. Furthermore, each acquisition module transmits the collected data to the communication unit of the data management center module via the internet. In the cloud, the protocol gateway unit processes the data, performs unified analysis, and distributes the generated control policies. These policies are then sent to designated acquisition modules via the communication unit and ultimately delivered to the terminal devices for execution. In summary, this embodiment enables the monitoring and control of building equipment through a unified cloud platform wherever a network exists. It also allows the use of cloud computing to run complex algorithms for in-depth mining of massive amounts of historical data, achieving comprehensive data analysis.

[0108] In one exemplary embodiment, a building energy management system with centralized regional deployment is included. The system includes multiple data acquisition modules deployed in different buildings, and a centralized data management center module as described above, deployed in a preset area. The data management center module is communicatively connected to each of the data acquisition modules. The preset area includes multiple buildings on which the data acquisition modules are deployed.

[0109] In this embodiment, the preset area is a geographically concentrated, pre-defined region comprising multiple buildings. The aforementioned centralized data management center module provides services to these buildings, with each building equipped with an independent data acquisition module. Data from each building is then transmitted to the protocol gateway unit via the acquisition module. The data center can collaboratively optimize the energy efficiency of multiple buildings within the region based on the energy efficiency of each building. Regional control strategies are generated by the data center module, distributed to the acquisition modules in each building, and ultimately executed by the terminal devices. This embodiment demonstrates that, compared to a pure cloud solution, the regional private network offers lower latency and supports regional coordinated control with certain real-time requirements. Compared to complete localization, it achieves centralized management of multiple buildings within the region, resulting in higher efficiency.

[0110] This application provides a preferred embodiment of a building energy management system.

[0111] A building energy management system includes a multi-source acquisition module, a data management center module, a spatial register module, a configuration module, and a message storage unit. The data management center module includes a protocol gateway unit, a device management unit, a metadata management unit, and a communication unit.

[0112] A data acquisition module refers to multiple data acquisition devices or edge control units managed by the building energy management system. These devices are used to send registration requests, receive network access information, and execute data acquisition when the scheduled time for a data acquisition item arrives. The current data is then acquired and sent to a third-party platform. Fixed data acquisition parameters for the module include, but are not limited to: acquisition point ID, value, quality code (status code), and timestamp. Values ​​are custom data acquisition parameters (e.g., the communication protocol parameters in the table below). The basic configuration page allows users to configure electrical parameter types (active energy, voltage, current, power, etc.) and data types, as shown in Table 1 below. The table below lists the custom data acquisition parameters for the acquisition module.

[0113] Table 1 Custom Acquisition Quantities for the Acquisition Module

[0114]

[0115] Protocol gateway unit: Used to receive registration requests and security authorizations, generate network access information based on the registration request, and establish a communication channel with the data collection nodes based on the network access information. The gateway supports data collection, conversion, and forwarding between systems with different communication protocols, custom data formats, and even completely different data structures. It also supports edge computing, filtering invalid data and processing valid data; and controlling the number and frequency of access commands in demand response scenarios.

[0116] Device Management Unit: This service plays a crucial role in managing the authentication and authorization of data providers and consumers. It ensures that only authorized users can access data and establishes trust between participants in the data exchange process.

[0117] Metadata management unit: Easily integrates data from different sources and in different formats, making it accessible to data consumers for analysis and decision-making. Provides a centralized register, with all data concentrated in one location for participants to access.

[0118] Communication Unit: Enables seamless integration and multi-platform data interaction between different systems, ensuring compatibility, security, and efficient communication. It acts as a bridge, promoting data collaboration and interoperability. It has cloud access capabilities, controls command issuance and frequency control, forwards effective data uplink to the cloud platform or other industrial software, and receives relevant commands, playing a crucial role in bridging the gap between upstream and downstream systems.

[0119] Space Register Unit: Configures and initializes temporary data storage space and sets data validity period based on register size. Records current device acquisition parameter data item by item, mainly including ID, acquisition parameter value, and timestamp, and updates temporary space data periodically; scheduled tasks parse and store data or package and store it according to a specified format, and consume the produced data at a specified time.

[0120] Message storage unit: Supports temporary data caching and persistent storage of collected data, and has the ability to access cloud databases.

[0121] Configuration Unit: Used to configure the acquisition node through the communication channel; it involves defining connection parameters, security settings and other configurations to achieve smooth data exchange.

[0122] Specifically, external third-party platforms monitor and aggregate the building's power consumption in real time, control and scheduling algorithms issue control strategy commands based on preset control power targets, edge controllers can customize subscriptions, provide remote control interfaces, and provide developers with custom message cleaning and message distribution capabilities.

[0123] Furthermore, developers can also apply flexible control algorithms to debug data interaction with third-party platforms via HTTPS / HTTP request / response methods.

[0124] 1. The message communication unit provides pre-packaged API interfaces for developer applications;

[0125] 2. Developers use these API interfaces to complete read / write operations and device management requests to third-party platforms;

[0126] 3. The edge controller / acquisition module sends the corresponding instructions to the terminal device;

[0127] 4. The protocol gateway unit receives the data and device information from the terminal device;

[0128] 5. The protocol gateway unit feeds back the execution result to the communication unit, and the message communication unit encapsulates the data into a standard HTTP response and returns it to the third-party platform.

[0129] Figure 3 This is a schematic diagram of the structure of a third-party cloud platform, a building energy management system, and terminal equipment in one embodiment.

[0130] Among them, the API interface refers to the external service window of the building energy management system, which allows third-party applications to query data or issue instructions in a standardized manner.

[0131] The registration and authorization team is responsible for verifying the device's identity and issuing access licenses.

[0132] Protocol conversion is used to unify protocols from different vendors into a single internal system language.

[0133] Message queues are used for the ordered buffering and transmission of instructions and data, ensuring the reliability of communication.

[0134] Data forwarding is used to report local data to the cloud and distribute cloud instructions to devices.

[0135] Flow control is used to protect devices from frequent command surges by smoothing and limiting the flow.

[0136] Edge computing is used for real-time data processing and rapid decision-making response.

[0137] The data space is used to provide millisecond-level up-to-date data information for the monitoring and control of equipment.

[0138] The configuration center is used for centralized configuration, policy distribution, and batch management of all data acquisition modules.

[0139] Metric monitoring is used to continuously track device status, system performance, and trigger alarms.

[0140] Scheduled tasks are used to drive the execution of periodic tasks (such as scheduled data acquisition and data archiving).

[0141] Data storage is used to persist historical data, supporting querying, analysis, and backtracking.

[0142] In summary, the building energy management system proposed in this application is an integrated solution for building energy data acquisition and edge control. It supports the construction of an interactive data acquisition platform for digital energy projects. System developers and technicians can utilize this method to develop and build data acquisition system programs, creating a lightweight, replicable, and scalable cloud-based host computer platform system.

[0143] Compared to other methods, this invention considers numerous factors in engineering applications, focusing on the flexibility of project data integration, custom protocol expansion, and high availability capabilities for multi-source and multi-device access, thus achieving integration between traditional industrial control systems and cloud services. It considers a more comprehensive and widespread range of engineering scenarios, strengthens data interconnectivity, and its built-in protocol can directly connect to platforms such as large public building energy consumption platforms and virtual power plant platforms, reducing redundant development and integration work. It also has the function of issuing equipment control commands to meet the needs of actual engineering applications. This system can be quickly and lightweightly upgraded, and can be deployed flexibly at low cost, possessing broad market prospects.

[0144] Furthermore, this application fully considers the engineering characteristics of smart building energy projects, avoiding redundant development and integration work during data connection. The program design phase takes into account the application needs of multiple engineering scenarios, satisfying the requirements for custom protocol expansion and multi-source data interconnection. This program construction method can be used to design intelligent gateways and host computer software solutions that act as bridges between different protocols. This gateway system supports power data acquisition and access as well as edge control access for flexible unit devices, and also has the function of issuing device control commands.

[0145] Furthermore, the system can be quickly and easily upgraded, and deployed flexibly at low cost. Depending on the specific engineering characteristics and energy data requirements, the deployment methods are as follows: 1) Building energy management system deployed at the edge; 2) Building energy management system deployed in a cloud-edge collaborative manner; and 3) Building energy management system deployed in a regionally centralized manner.

[0146] The modules in the aforementioned building energy management system can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in or independent of the processor in a computer device, or stored in the computer device's memory as software, so that the processor can call and execute the corresponding operations of each module.

[0147] Based on the same inventive concept, such as Figure 4 As shown, this application also provides a building energy management method, applied to a building energy management system as described in any of the above claims, the method comprising:

[0148] Step S410: Data collection and processing are performed on various terminal devices in the building to be managed according to the preset configuration file to obtain initial device data;

[0149] Step S420: Perform format conversion and edge computing processing on the initial device data to obtain the target device data;

[0150] Step S430: Send the target device data to the preset control platform. In response to the control command determined by the control platform based on the target device data, decompose the control command into target control commands corresponding to each terminal device; convert the target control commands into the data format corresponding to each terminal device; and send the converted target control commands to the corresponding terminal devices at a preset frequency.

[0151] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. Any references to memory, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM). The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this application may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, artificial intelligence (AI) processors, etc., and are not limited to these.

[0152] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this application.

[0153] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are specific and detailed, they should not be construed as limiting the scope of this patent application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this application should be determined by the appended claims.

Claims

1. A building energy management system, characterized in that, The system integrates a data acquisition module and a data management center module; the data management center module includes a protocol gateway unit and a communication unit. The acquisition module is used to collect and process data from various terminal devices in the building to be managed according to a preset configuration file, so as to obtain initial device data. The protocol gateway unit is used to perform format conversion and edge computing processing on the initial device data to obtain target device data; The communication unit is used to send the target device data to a preset control platform, and in response to the control command determined by the control platform based on the target device data, decompose the control command into target control commands corresponding to each terminal device; The protocol gateway unit is further configured to convert the target control command into a data format corresponding to each terminal device, and send the converted target control command to the corresponding terminal device at a preset frequency.

2. The system according to claim 1, characterized in that, The system also includes a metadata management unit and a data space register unit; The metadata management unit is used to establish metadata information corresponding to the terminal device; The data space register unit is used to acquire target device data corresponding to the terminal device, bind and store the target device data with the corresponding timestamp information and device identification information, and associate the bound and stored data with the corresponding metadata information.

3. The system according to claim 2, characterized in that, The system also includes a message storage unit; The message storage unit is used to read persistent device data within a preset time period stored in the data space register unit and store the persistent device data in a preset storage system.

4. The system according to any one of claims 1 to 3, characterized in that, The system also includes a configuration unit; The configuration unit is used to determine configuration data for each acquisition module and generate a configuration file corresponding to each acquisition module based on the configuration data. The configuration unit is also used to distribute the configuration file to the corresponding acquisition module.

5. The system according to any one of claims 1 to 3, characterized in that, The data management center module includes a device management unit: The device management unit is used to obtain the registration request of the acquisition module to be verified, and determine the access token of the acquisition module to be verified based on the registration request. The device management unit is also used to generate network access information for the corresponding collection module to be verified when the access token is detected to be valid, and to bind the network access information to the collection module to be verified.

6. The system according to claim 5, characterized in that, The protocol gateway unit is also used to establish a communication channel between the acquisition module to be verified and the protocol gateway unit.

7. A building energy management system deployed at the edge, characterized in that, The system includes at least one acquisition module deployed locally on the building, and a data management center module deployed locally on the building as described in any one of claims 1 to 6.

8. A building energy management system with cloud-edge collaborative deployment, characterized in that, The system includes at least one acquisition module deployed locally on the building, and a data management center module deployed in the cloud as described in any one of claims 1 to 6.

9. A building energy management system with centralized regional deployment, characterized in that, The system includes multiple acquisition modules deployed in different buildings, and a centralized data management center module as described in any one of claims 1 to 6 deployed in a preset area. The data management center module is communicatively connected to each of the acquisition modules, and the preset area includes multiple buildings on which the acquisition modules are deployed.

10. A building energy management method, applied to the building energy management system as described in any one of claims 1 to 9, characterized in that, The method includes: Data is collected and processed from various terminal devices in the building to be managed according to the preset configuration file to obtain initial device data; The initial device data is subjected to format conversion and edge computing processing to obtain the target device data; The target device data is sent to a preset control platform. In response to the control command determined by the control platform based on the target device data, the control command is decomposed into target control commands corresponding to each terminal device. The target control commands are converted into data formats corresponding to each terminal device, and the converted target control commands are sent to the corresponding terminal devices at a preset frequency.

Images