Cloud-side collaborative intelligent building control system, method and equipment
By deploying virtual controllers on the cloud and adopting a cloud-side collaboration smart building control system, the complexity and difficulty of existing systems under the demand for high-complexity control is solved, and comprehensive monitoring and management of device life cycle data is achieved.
Patent Information
- Application Number
- CN202411776410.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-12-05
- Publication Date
- 2025-03-18
- Estimated Expiration
- Not applicable · inactive patent
AI Technical Summary
When facing high-complexity control needs, the existing smart building control system is complex and difficult to implement, and it is impossible to fully monitor data changes in the entire life cycle of the equipment to be managed.
The intelligent building control system with cloud edge collaboration is adopted. Through the three-layer structure of the equipment layer, data aggregation layer and the cloud, a virtual controller is deployed to control it in the cloud, simplifying the system structure, and the data is collected and reported to the cloud for management through the data aggregation layer.
The system structure is simplified, the difficulty of controller computing power expansion and logic update is reduced, and the comprehensive monitoring of data changes in the entire life cycle of the device operation is realized, which improves the system's management efficiency and data monitoring capabilities.
Smart Images

Figure CN119652940A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the field of smart building technology, and in particular to a cloud-edge collaborative smart building control system, method and device. Background Art
[0002] At present, building control is constantly moving towards digital operation. By combining digital technology to intelligently control and manage various equipment in the building, the level of intelligent building management can be improved, thereby further improving building safety and the operating efficiency of building equipment, and achieving energy conservation and environmental protection.
[0003] In practice, it is found that the application scale of smart building control is constantly expanding, such as from controlling a single building to controlling the buildings of the entire park. In this large-scale smart building control scenario, the types and number of devices to be managed increase dramatically, so the overall smart building control complexity is very high. In this regard, the existing smart building control system often has some areas to be improved in terms of performance when facing high-complexity control requirements.
[0004] For example, existing smart building control systems usually include: equipment and accessories layer, field control layer, system integration layer, and cloud. Based on the overall architecture of this smart building control system, if the types and quantities of managed devices that need to be connected are large, it is necessary to adjust the hardware access of the managed devices, and the field controllers of the field control layer need to be expanded. At the same time, it is necessary to write corresponding field control logic for specific field controllers and devices to be managed. The overall hardware architecture is relatively complex, and the coding of software control logic is difficult. In addition, the software coding of the field controller during subsequent updates and upgrades is also relatively complex. In addition, the system integration layer only collects the results of data processing by the field controller, and cannot grasp the data changes during the entire life cycle of the managed device.
[0005] In summary, in building control scenarios with a large number of devices to be managed and multiple protocols, the existing smart building control systems have technical problems such as high system complexity, difficulty in implementation, and inability to grasp the data changes of the managed devices throughout their entire life cycle. Summary of the invention
[0006] In view of this, the purpose of the present invention is to provide a cloud-edge collaborative smart building control system, method and equipment to solve the problems in the prior art of high system complexity, great implementation difficulty, and inability to grasp data changes in the entire life cycle of the managed equipment.
[0007] According to a first aspect of an embodiment of the present invention, a cloud-edge collaborative smart building control system is provided, comprising: a device layer, a data aggregation layer, and a cloud; wherein the cloud comprises a data base, a business middle platform, and an application layer; wherein the data base comprises a virtual controller;
[0008] The data aggregation layer is used to aggregate the device data of the device layer and report the device data to the data base, so that the virtual controller in the data base can perform control operations on the corresponding devices in the device layer based on the device data; wherein the control operation includes at least one of the following: data storage operation, data monitoring operation, and control instruction generation operation;
[0009] The application layer is used to receive control instructions and send the control instructions to the business middle station;
[0010] The business middle station is used to send the control instruction to the virtual controller;
[0011] The virtual controller is used to receive the control instruction and control the corresponding device in the device layer according to the control instruction.
[0012] According to a second aspect of an embodiment of the present invention, a cloud-edge collaborative smart building control method is provided, which is applied to a virtual controller in a cloud-edge collaborative smart building control system as described in the first aspect of the embodiment of the present invention, including:
[0013] Acquire device data of a building device to be controlled, and perform a control operation on the building device to be controlled based on the device data; wherein the control operation includes at least one of the following: a data storage operation, a data monitoring operation, and a control instruction generation operation; and
[0014] Receive control instructions sent by the user through the human-computer interaction interface, and control the building device to be controlled according to the control instructions.
[0015] According to a third aspect of an embodiment of the present invention, an electronic device is provided for providing cloud computing services for the cloud-edge collaborative smart building control system described in the first aspect of an embodiment of the present invention.
[0016] The technical solution provided by the embodiments of the present invention may have the following beneficial effects:
[0017] Through the three-layer structure of device layer, data aggregation layer and cloud, a virtual controller is deployed in advance on the cloud. The virtual controller directly controls the devices in the device layer, and the control operations performed by the local controller in the original architecture are virtualized and deployed, which can simplify the overall system structure. In addition, when expanding the computing power and updating the logic of the controller, the virtualized controller can be updated and controlled directly on the cloud, which is less difficult to implement than the combination of hardware deployment and software logic update. In addition, this solution aggregates and transparently transmits data to the cloud for management through the data aggregation layer, and all control data during the control process of the virtual controller will also be stored in the cloud, so that all data changes during the entire life cycle of the equipment can be monitored in the cloud, achieving more comprehensive data monitoring.
[0018] It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the invention. BRIEF DESCRIPTION OF THE DRAWINGS
[0019] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the invention and, together with the description, serve to explain the principles of the invention.
[0020] Figure 1 is a schematic architecture diagram of a smart building control system according to an exemplary embodiment;
[0021] Figure 2 is a schematic block diagram of a logic of an identification device of a virtual controller according to an exemplary embodiment;
[0022] Figure 3 It is a flow chart of a cloud-edge collaborative smart building control method according to an exemplary embodiment;
[0023] Figure 4 The diagram is a schematic diagram showing an internal control circuit of an electronic device according to an exemplary embodiment. DETAILED DESCRIPTION
[0024] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present invention. Instead, they are merely examples of devices and methods consistent with some aspects of the present invention as detailed in the appended claims.
[0025] Figure 1 is a schematic architecture diagram of a smart building control system according to an exemplary embodiment. Figure 1As shown, it includes: a device layer, a data aggregation layer, and a cloud layer; wherein the cloud layer includes a data base, a business middle platform, and an application layer; wherein the data base includes a virtual controller;
[0026] The data aggregation layer is used to aggregate the device data of the device layer and report the device data to the data base, so that the virtual controller in the data base can perform control operations on the corresponding devices in the device layer based on the device data; wherein the control operation includes at least one of the following: data storage operation, data monitoring operation, and control instruction generation operation;
[0027] The application layer is used to receive control instructions and send the control instructions to the business middle station;
[0028] The business middle station is used to send the control instruction to the virtual controller;
[0029] The virtual controller is used to receive the control instruction and control the corresponding device in the device layer according to the control instruction.
[0030] The smart building control system of this solution is a three-layer system framework built on the data base, which mainly includes: device layer, data aggregation layer, and cloud. Based on the digital base technology, it realizes the unified analysis of data between devices with different protocols and provides an operating environment for virtual controllers.
[0031] Among them, the equipment layer includes all the electromechanical equipment on site, including various subsystems, such as cold and heat source control systems, terminal air-conditioning control systems, water supply and drainage control systems, lighting control systems, power distribution control systems, etc. The cold and heat source control system may include water pumps, cooling towers, cold / heat units and other equipment; the terminal air-conditioning control system may include VAV-BOX (terminal device of variable air volume air-conditioning system), various wind cabinets, fans and ducts and other equipment; the water supply and drainage control system may include water supply / drainage pumps, liquid switches and other equipment; the lighting control system may include various types of electric lights, sensors and other equipment; the power distribution control system may include transformers, generators and other equipment.
[0032] Furthermore, the data convergence layer in this solution may include a data gateway or local controller connected to each electromechanical device in the device layer. The data gateway is mainly used for the docking and conversion of protocol data, and the local controller and the virtual controller run the same operating system core. A logic can be executed in both the local controller and the virtual controller. The virtual controller is an application that can run on a PC or server and has the same functions as the physical controller. It usually runs inside a container deployed on a computer or server, communicates with electromechanical devices through Ethernet, and realizes the functions of device monitoring and logic control.
[0033] In addition, when collecting data in the cloud, a third-party service layer can also be introduced. The third-party service layer includes third-party software, third-party hardware, third-party cloud, etc. The specific communication protocol used by the third-party service layer can be but is not limited to the HTTP protocol.
[0034] Furthermore, the cloud in this solution mainly includes the digital base, the business middle platform, and the application layer. Among them, the digital base can uniformly process the device access protocol, provide the operating environment of the virtual controller, and build the message bus of the overall internal Can4Net protocol; the business middle platform can use the message bus provided by the digital base as the data source to build a platform for distributed deployment of microservices for different business needs; the application layer can obtain the service interface data provided by the business middle platform microservices, provide customers with a visual display platform, and can also connect to the logic programming software to perform remote programming, program upgrades and other services on the virtual controller and local controller.
[0035] This application proposes a smart building control system, which can deploy a virtual controller in the cloud in advance through a three-layer structure of device layer, data aggregation layer and cloud, directly control the devices in the device layer through the virtual controller, and virtualize the control operations performed by the local controller in the original architecture, which can simplify the overall system structure. In addition, when expanding the computing power of the controller and updating the logic, the virtualized controller can be updated and controlled directly in the cloud, which is less difficult to implement than the combination of hardware deployment and software logic update. In addition, this solution aggregates and transparently transmits data to the cloud for management through the data aggregation layer, and all control data in the control process of the virtual controller will also be stored in the cloud, so that all data changes in the entire life cycle of the equipment can be monitored in the cloud, realizing more comprehensive data monitoring.
[0036] As an optional implementation, the data convergence layer is specifically used to report the device data to the virtual controller in the data base through the Can4Net protocol, wherein the device data includes device feature information, device attribute information and device attribute values.
[0037] Among them, the Can4Net protocol is a communication protocol that contains device categories and attributes, allowing the protocol parser to automatically identify devices. It has high versatility when transmitting device data and can be used as both a southbound device data access protocol and a northbound business service docking protocol. The data bus based on the Can4Net protocol can bring together southbound electromechanical equipment, local controllers and virtual controllers, and business service data, realizing cross-system electromechanical equipment collaborative operation and logical cloud-edge collaborative functions.
[0038] In this embodiment, the Can4Net protocol defines the content and format of data transmission. According to such format requirements, relevant content will be defined for each device, including device feature information, device attribute information and device attribute value. Among them, the device feature information may include but is not limited to the unique identifier of the protocol component, the device type, the device manufacturer, etc., the device attribute information may include but is not limited to the switch control point, frequency control point, etc. of the device, and the device attribute value may correspond to the actual value of the relevant attribute of the device.
[0039] For example, for water pump equipment, the corresponding water pump Can4Net protocol components are as follows:
[0040] {
[0041] "Device Characteristics": {
[0042] “Brand”:”XX Company”,
[0043] "Power":"XXX",
[0044] "Production date":""
[0045] },
[0046] "Device Properties": [
[0047] {
[0048] "name": "switch",
[0049] "value":1,
[0050] "type":0,
[0051] "instance":1
[0052] },
[0053] {
[0054] "name": "frequency",
[0055] "value":50,
[0056] "type":1,
[0057] "instance":2
[0058] } ]
[0060] }
[0061] As an optional implementation, the virtual controller is specifically used to determine the device type based on the device feature information; and determine the device control parameters based on the device type, the device attribute information and the device attribute value; and perform control operations on the corresponding device in the device layer based on the device control parameters; wherein one virtual controller corresponds to one device in the device layer.
[0062] In this embodiment, the Can4Net protocol stipulates that when a signal for obtaining device data is received on a device compatible with the protocol component, the data of the three parts will be reported according to the definition of the protocol component, and the reported data will be sent to the Can4Net message scheduling pipeline. In addition, the protocol components of all devices are also integrated in the virtual controller. When the corresponding Can4Net data report is received, the corresponding device type can be distinguished according to the unique identifier of the protocol component, and then the relevant control points and data points of the device can be identified according to the attribute value of the corresponding device type, and finally the automatic identification of the device is realized without human intervention. Among them, the protocol component is generated by registration. By uploading the device protocol of the device itself on the Can4Net protocol generation website, the automatically generated Can4Net protocol component is obtained. When submitting the device protocol of the device itself, the website will automatically generate a unique identifier to identify the Can4Net protocol generated this time.
[0063] As an optional implementation, the device layer includes a first device type that supports the Can4Net protocol and a second device type that does not support the Can4Net protocol; and the data convergence layer includes at least a data gateway;
[0064] The device layer is used for transmitting the device data to the message scheduling pipeline directly through the Can4Net protocol for the first device of the first device type, so as to report the device data to the virtual controller through the message scheduling pipeline;
[0065] The device layer is also used to perform protocol conversion on the second device of the second device type through the data gateway, and then transmit the device data to the message scheduling pipeline, so as to report the device data to the virtual controller through the message scheduling pipeline.
[0066] Among them, electromechanical equipment is classified into two types, one is the first device type that is already compatible with the Can4Net protocol, and the other is the second device type that needs to be converted to the Can4Net protocol through a data gateway. Among them, some air-conditioning models are already compatible with the Can4Net protocol and belong to the first device type. Equipment accessed through Modbus and Bacnet protocols need to be converted to the Can4Net protocol through a data gateway and belong to the second device type. Specifically, the equipment layer will involve a variety of subsystem electromechanical equipment (such as HVAC, fire protection, lighting and other electromechanical equipment). Different subsystem electromechanical equipment will use different communication protocols for data transmission. Modbus, BacNet and other protocols are commonly used in engineering. When such electromechanical equipment needs to be connected, they can be connected through a data gateway. The data gateway can convert such protocols into Can4Net protocols and transmit them to the cloud.
[0067] Please also read Figure 2 , Figure 2 is a schematic block diagram of a recognition device logic of a virtual controller according to an exemplary embodiment. Figure 2 As shown, it includes cooling towers, water pumps, centrifuges, street lights, alarms and other equipment. The cooling tower belongs to the first equipment type, and the water pumps, centrifuges, street lights, alarms and other equipment belong to the second equipment type. When the data is interacted between the device layer and the cloud virtual controller, for the cooling tower of the first equipment type, the device data can be directly transmitted to the message scheduling pipeline through the Can4Net protocol, and then transmitted to the virtual controller. For the second equipment type of water pumps, centrifuges, street lights, alarms and other equipment, it is necessary to first perform protocol conversion through the data gateway, and then convert the protocol into the device data of the Can4Net protocol to the message scheduling pipeline, and then transmit it to the virtual controller.
[0068] Furthermore, for devices of the second device type, they need to be assigned to different data access processes according to the type of access protocol. Taking the HTTP protocol as an example, the data will first be connected according to the HTTP protocol, and then the data will be pushed to the data gateway. The data gateway has the ability to parse the protocol points. The format of the transmitted data may be a non-standard protocol format. At this time, the protocol point parsing can be performed through a custom script, and the data of the private data structure of different protocols is converted into the Can4Net protocol through the protocol format, and the data is sent to the message scheduling bus. For different types of protocols, it is necessary to pre-adapt and modify the receiving end encoding method of the parsing script, and then implement the format conversion of the Can4Net protocol through a custom script.
[0069] Specifically, the virtual controller container can manage the life cycle of each virtual controller based on the digital base and Docker container technology. The number of virtual controllers is usually multiple, and it can manage the real electromechanical devices that need to be bound to each virtual controller access port, as well as the communication port configuration of each virtual controller. First, the virtual controller container first establishes a virtual controller so that the virtual controller runs the same control logic as the local controller. In actual building control scenarios, there are often many terminal device controls involved. If only local controllers are used to control terminal devices, a large number of local controllers are required, and the maintenance of each local controller logic and the upgrade of hardware programs need to be maintained at the engineering site. Virtual controllers can be established and run on cloud services through container virtualization. Compared with local controllers, the cost of expanding the hardware performance of cloud servers is lower. Moreover, all virtual controllers run on the cloud, and can be directly connected to the cloud remotely to upgrade the logic and virtual hardware programs, reducing the operation and maintenance costs. After the new virtual controller is created, the logic can be issued through the logic programming software of the application layer, and then the electromechanical devices that need to be controlled in the logic are configured, and the abstract devices in the logic are bound to the real electromechanical devices in the data management. Then, the communication port of the virtual controller is specified, and the entire virtual controller can work like a local controller. The message dispatch bus receives changes in the parameter values of electromechanical equipment, and can also pass control instructions to the electromechanical equipment for operation control through the bus. In addition, the virtual controller can also send temporary variables in the entire logical operation process to the message dispatch bus through the container memory mapping mechanism, realizing data monitoring of the entire life cycle of electromechanical equipment operation. Specifically, the virtual controller will create a map in memory for all configuration points (including temporary variables) during operation. Each variable will be assigned an address as the key and a value as the value. This map will monitor all value changes, and when changes occur, the current key and value will be pushed to the message dispatch bus. Among them, the mapping relationship between the virtual controller and the real electromechanical equipment is a one-to-one mapping, and the equipment points in the virtual controller are mapped one-to-one to the actual equipment.
[0070] When programming the logic of the virtual controller, an abstract device is used, such as an abstract water pump. The abstract device can include two values: switch and frequency, which are represented as AV.1 and AV2 respectively. The water pump of the real device will have two point values. If it is Can4Net, it will be transmitted directly. If not, it can also be converted to Can4Net through the data gateway and then transmitted. Since the protocol contains the points of the real device, the control logic code can be written to bind AV.1 to the points of the real device. The specific control logic code is as follows:
[0071] {
[0072] "name":"switch",
[0073] "value":1,
[0074] "type":0,
[0075] "instance":1
[0076] }
[0077] Alternatively, you can write control logic code to bind AV.2 to the points of the real device. The specific control logic code is as follows:
[0078] {
[0079] "name":"frequency",
[0080] "value":50,
[0081] "type":1,
[0082] "instance":2
[0083] }
[0084] As an optional implementation, the business middle platform includes at least one of the following business service modules: an APP business service module, a visualization business service module and a programming software business service module; wherein the APP business service module includes at least one of the following sub-modules: an equipment monitoring service sub-module, a fault management service sub-module, and a program upgrade service sub-module; wherein the visualization business service module includes at least one of the following sub-modules: the equipment monitoring service sub-module, the fault management service sub-module, and an equipment transportation service sub-module; wherein the programming software business service module includes at least one of the following sub-modules: a control logic upload service sub-module and a control logic download service sub-module; and the application layer includes at least one of the following human-computer interaction modules: an APP interaction module, a PC interaction module, and a controller programming interaction module.
[0085] In this embodiment, the application layer provides user-oriented interactive functions. Users can control the system through the mobile phone APP, or operate the device through the PC visual interface. Users can also directly connect to the virtual controller and the local controller connected to the device through the controller programming software to achieve remote logic update.
[0086] Among them, the business middle platform can deploy different business services through microservices. For example, if the mobile APP needs to monitor the device, the business middle platform can deploy the mobile APP background microservices to provide support for equipment monitoring business services. Data can be obtained through the message scheduling bus, and the data can be processed according to the background microservice business needs and then provided to the mobile APP to realize the entire equipment monitoring process.
[0087] As an optional implementation, the business middle station further includes a first storage module, wherein the first storage module is used to store business data and / or file data;
[0088] The data base also includes a second storage module, wherein the second storage module is used to store real-time data and historical data, and the second storage module supports access to a third-party system to transmit data, and the third-party system supports transmitting data to the cloud message scheduling pipeline.
[0089] In this embodiment, business-related data will be generated during the operation of the business middle platform, and the business middle platform provides data storage services, which can store business data generated during business execution in the first storage module, and can also store file data transmitted in the business process. Mapping different data types to different storage databases can effectively improve data reading performance.
[0090] Furthermore, after receiving the corresponding data, the message dispatching bus will forward it to the corresponding data processing module in the data base. For example, the changes in the attribute values during the operation of the electromechanical equipment will be transferred to the data storage module (second storage module) through the bus for storage, and the intermediate value variables generated by the logic during the operation of the virtual controller will also be transferred to the data storage through the bus for storage. For example, in an efficient computer room, when coordinating and controlling multiple units for polling operation, the unit with the shortest operating time will be selected to start first. However, the operating time parameter is not recorded by the unit itself, but requires the controller to count the operating time of each unit. This statistical value (unit operating time) is the intermediate value variable, which can be passed to the data storage module for storage.
[0091] Among them, when the second storage module performs data storage, two data storage methods are generated, real-time data storage method and historical data storage method. Each value will store its most recent change value each time as real-time data storage. Each time real-time data is stored, the original data will be transferred to historical data storage, which can improve the efficiency of data storage and reading.
[0092] Furthermore, in addition to passing data to the data storage, the message scheduling pipeline will also pass it to the data opening module. Among them, the data opening module can open all the data received by the data base during data management according to the specified protocol category for the third-party platform to connect to the system to obtain data. Among them, the open data can be real-time data or historical data. Each time the data content needs to be read, it will be obtained from the data storage module through the message scheduling pipeline.
[0093] As an optional implementation, the data convergence layer further includes a local controller, and the local controller is used to control devices of the local control category in the device layer.
[0094] In this embodiment, if the terminal device at the equipment layer needs to perform local self-contained logic control in addition to basic data communication, a local controller can be used for connection. The local controller can establish a connection with the built-in data gateway in the cloud, convert the communication protocol of the electromechanical equipment into the Can4Net protocol, and the local controller can also run its own logic control. For example, the control inside the high-efficiency computer room is a self-contained local control, which needs to control the unit, water pump, and butterfly valve to achieve the optimal control of the system energy efficiency. At this time, the local controller can access the unit, water pump, butterfly valve and other equipment for local control, and can also transmit the equipment data of these devices to the cloud.
[0095] Optionally, during the process of device layer access to the cloud, if the data gateway does not support conversion of the protocol of the electromechanical device to be accessed to the Can4Net protocol, it can be directly connected to the cloud through, but not limited to, the HTTP protocol.
[0096] Optionally, in addition to accessing various electromechanical devices at the device layer, the cloud can also access other data sources such as third-party software, third-party hardware, and third-party cloud to obtain data. The data aggregation layer collects and processes data from different data sources in a unified manner.
[0097] Among them, the local controller is mainly used to control the operating status of the device at the device end. Its characteristics are that the operating logic is relatively simple and solidified, and no dynamic optimization is required. However, it cannot run large model data optimization processing, mainly because the computing power is insufficient. The local controller has the advantages of fast control and timely response, but it is difficult to expand the computing power. In this regard, this solution deploys local controllers for devices of the local control category, and no longer deploys local controllers for devices that do not require local integrated control, but adopts the control method of virtual controllers.
[0098] Among them, the virtual controller is installed on the server side for operation, and its computing power depends entirely on the overall performance of the server, and the cost of expanding the performance of the server is much lower than the cost of expanding the local computing power of the same. And with the popularization of 5G networks, the data transmission delay of virtual controllers is getting shorter and shorter, which makes the advantages of virtual controllers gradually manifested. Relying on the high computing power of the server, large models can be run in the virtual controller, and the optimized control parameters can be sent to the message scheduling bus online in the data structure of Can4Net. The message scheduling bus then forwards the data to the corresponding local controller or directly to the terminal device to achieve dynamic tuning.
[0099] In this regard, this solution integrates local controllers and virtual controllers to jointly deploy the system architecture. If the data is sent to the local controller, the local controller receives the configuration data and records it. It can also combine its own control logic to implement local control logic tuning, while also leveraging its own control low latency advantage to optimize the device. If the data is sent to the virtual controller, it relies on the high computing power of the server to perform data calculations in the virtual controller, and together they achieve cloud-edge collaboration.
[0100] As an optional implementation, the application layer, the business middle platform, and the data base can be connected to a data security module for security control.
[0101] Preferably, in order to ensure data security in the cloud, this solution provides a data security module, including but not limited to SSL data encryption, access control, SMS authentication, audit logs, security log alarms and other services.
[0102] Based on the same inventive concept, Figure 3 The invention is a flow chart of a cloud-edge collaborative smart building control method, which is applied to the virtual controller in the cloud-edge collaborative smart building control system mentioned above, such as Figure 3 As shown, including:
[0103] S31, acquiring device data of a building device to be controlled, and performing a control operation on the building device to be controlled based on the device data; wherein the control operation includes at least one of the following: a data storage operation, a data monitoring operation, and a control instruction generation operation; and
[0104] S32, receiving a control instruction sent by a user through a human-computer interaction interface, and controlling the building device to be controlled according to the control instruction.
[0105] The present invention provides a cloud-edge collaborative smart building control method, which is applied to the virtual controller in the above-mentioned cloud-edge collaborative smart building control system. Through the three-layer structure of the device layer, the data aggregation layer and the cloud, the virtual controller is deployed in advance on the cloud. The virtual controller directly controls the devices in the device layer, and the control operations performed by the local controller in the original architecture are virtualized and deployed, which can simplify the overall system structure. In addition, when expanding the computing power and updating the logic of the controller, the virtualized controller can be updated and controlled directly on the cloud, which is less difficult to implement than the method of combining hardware deployment with software logic updates. In addition, this solution aggregates and transparently transmits data to the cloud for management through the data aggregation layer, and all control data in the process of executing the control by the virtual controller will also be stored in the cloud, so that all data changes in the entire life cycle of the equipment can be monitored in the cloud, realizing more comprehensive data monitoring.
[0106] Based on the same inventive concept, Figure 4 is a schematic diagram of an internal control circuit of an electronic device according to an exemplary embodiment. Figure 4 As shown, the electronic device comprises:
[0107] At least one processor 401, a communication interface 402; and
[0108] A memory 403 communicatively connected to the at least one processor 401;
[0109] Among them, the processor 401, the communication interface 402 and the memory 403 communicate with each other through the communication bus 404; the memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can provide cloud computing services for the above-mentioned cloud-edge collaborative smart building control system.
[0110] According to an exemplary embodiment, a non-transitory computer-readable storage medium storing computer instructions is shown, wherein the computer instructions are used to enable a computer to provide cloud computing services for the above-mentioned cloud-edge collaborative smart building control system.
[0111] The computer-readable storage medium disclosed in this embodiment includes, but is not limited to: electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices or components, or any combination of the above. More specific examples (non-exhaustive list) of computer-readable storage media include: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present invention, a computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, device or device.
[0112] It can be understood that the same or similar parts of the above embodiments can be referenced to each other, and the contents not described in detail in some embodiments can refer to the same or similar contents in other embodiments.
[0113] It should be noted that, in the description of the present invention, the terms "first", "second", etc. are only used for descriptive purposes and cannot be understood as indicating or implying relative importance. In addition, in the description of the present invention, unless otherwise specified, the meaning of "plurality" refers to at least two.
[0114] Any process or method description in a flowchart or otherwise described herein may be understood to represent a module, segment or portion of code that includes one or more executable instructions for implementing the steps of a specific logical function or process, and the scope of the preferred embodiments of the present invention includes alternative implementations in which functions may not be performed in the order shown or discussed, including performing functions in a substantially simultaneous manner or in the reverse order depending on the functions involved, which should be understood by those skilled in the art to which the embodiments of the present invention belong.
[0115] It should be understood that the various parts of the present invention can be implemented by hardware, software, firmware or a combination thereof. In the above-mentioned embodiments, a plurality of steps or methods can be implemented by software or firmware stored in a memory and executed by a suitable instruction execution system. For example, if implemented by hardware, as in another embodiment, it can be implemented by any one of the following technologies known in the art or their combination: a discrete logic circuit having a logic gate circuit for implementing a logic function for a data signal, a dedicated integrated circuit having a suitable combination of logic gate circuits, a programmable gate array (PGA), a field programmable gate array (FPGA), etc.
[0116] A person skilled in the art may understand that all or part of the steps in the method for implementing the above-mentioned embodiment may be completed by instructing related hardware through a program, and the program may be stored in a computer-readable storage medium, which, when executed, includes one or a combination of the steps of the method embodiment.
[0117] In addition, each functional unit in each embodiment of the present invention may be integrated into a processing module, or each unit may exist physically separately, or two or more units may be integrated into one module. The above-mentioned integrated module may be implemented in the form of hardware or in the form of a software functional module. If the integrated module is implemented in the form of a software functional module and sold or used as an independent product, it may also be stored in a computer-readable storage medium.
[0118] The storage medium mentioned above can be a read-only memory, a magnetic disk or an optical disk, etc.
[0119] In the description of this specification, the description with reference to the terms "one embodiment", "some embodiments", "examples", "specific examples", or "some examples" means that the specific features, structures, materials or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the present invention. In this specification, the schematic representation of the above terms does not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described may be combined in any one or more embodiments or examples in a suitable manner.
[0120] Although the embodiments of the present invention have been shown and described above, it is to be understood that the above embodiments are exemplary and are not to be construed as limitations of the present invention. A person skilled in the art may change, modify, replace and vary the above embodiments within the scope of the present invention.
Claims
1. A cloud-edge collaborative smart building control system, characterized in that: include: Device layer, data aggregation layer, and cloud; wherein the cloud includes a data base, a business middle platform, and an application layer; wherein the data base includes a virtual controller; The data aggregation layer is used to aggregate the device data of the device layer and report the device data to the data base, so that the virtual controller in the data base can perform control operations on the corresponding devices in the device layer based on the device data; wherein the control operation includes at least one of the following: data storage operation, data monitoring operation, and control instruction generation operation; The application layer is used to receive control instructions and send the control instructions to the business middle station; The business middle station is used to send the control instruction to the virtual controller; The virtual controller is used to receive the control instruction and control the corresponding device in the device layer according to the control instruction.
2. The system according to claim 1, characterized in that The data convergence layer is specifically used to report the device data to the virtual controller in the data base through the Can4Net protocol, wherein the device data includes device feature information, device attribute information and device attribute values.
3. The system according to claim 2, characterized in that The virtual controller is specifically used to determine the device type according to the device feature information; and determine the device control parameters according to the device type, the device attribute information and the device attribute value; and perform control operations on the corresponding devices in the device layer based on the device control parameters; wherein one virtual controller corresponds to one device in the device layer.
4. The system according to claim 2, characterized in that The device layer includes a first device type that supports the Can4Net protocol and a second device type that does not support the Can4Net protocol; and the data convergence layer includes at least a data gateway; The device layer is used for transmitting the device data to the message scheduling pipeline directly through the Can4Net protocol for the first device of the first device type, so as to report the device data to the virtual controller through the message scheduling pipeline; The device layer is also used to perform protocol conversion on the second device of the second device type through the data gateway, and then transmit the device data to the message scheduling pipeline, so as to report the device data to the virtual controller through the message scheduling pipeline.
5. The system according to claim 1, characterized in that The business middle platform includes at least one of the following business service modules: an APP business service module, a visualization business service module and a programming software business service module; wherein the APP business service module includes at least one of the following sub-modules: an equipment monitoring service sub-module, a fault management service sub-module, and a program upgrade service sub-module; wherein the visualization business service module includes at least one of the following sub-modules: the equipment monitoring service sub-module, the fault management service sub-module, and the equipment transportation service sub-module; wherein the programming software business service module includes at least one of the following sub-modules: a control logic upload service sub-module and a control logic download service sub-module; and the application layer includes at least one of the following human-computer interaction modules: an APP interaction module, a PC interaction module, and a controller programming interaction module.
6. The system according to claim 1, characterized in that The business middle station also includes a first storage module, wherein the first storage module is used to store business data and / or file data; The data base also includes a second storage module, wherein the second storage module is used to store real-time data and historical data, and the second storage module supports access to a third-party system to transmit data, and the third-party system supports transmitting data to the cloud message scheduling pipeline.
7. The system according to claim 1, characterized in that The data convergence layer also includes a local controller, and the local controller is used to control devices of the local control category in the device layer.
8. The system according to claim 1, characterized in that The application layer, the business middle platform, and the data base can be connected to the data security module for security control.
9. A cloud-edge collaborative smart building control method, characterized in that: A virtual controller used in a cloud-edge collaborative smart building control system as described in any one of claims 1 to 8, comprising: Acquire device data of a building device to be controlled, and perform a control operation on the building device to be controlled based on the device data; wherein the control operation includes at least one of the following: a data storage operation, a data monitoring operation, and a control instruction generation operation; and Receive control instructions sent by the user through the human-computer interaction interface, and control the building device to be controlled according to the control instructions.
10. An electronic device, characterized in that: Used to provide cloud computing services for the cloud-edge collaborative smart building control system described in any one of claims 1-8.
Citation Information
Patent Citations
General internet platform for real-time monitoring of digital products in small and medium-sized manufacturing industry
CN115102827A
Management method and system for intelligent building networking equipment
CN115834634A
Management control system and method for digital building
CN116366701A
Building control system and method, electronic equipment and storage medium
CN117348455A
Building management system with control logic distributed between a virtual controller and a smart edge controller
US20210382449A1
Cited By
Virtualization control system
CN119916669A