A computer-implemented method and platform for planning and operating building devices

Automatically compute and deploy connection groups through machine-readable providers and consumer models, solving the problem of function and equipment matching in building installation planning and engineering design, achieving efficient automatic matching and interoperability, reducing workload and independent communication, independent of communication technology.

CN119065760APending Publication Date: 2024-12-03SIEMENS SCHWEIZ AG
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202410697716.5
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2023-05-31
Filing Date
2024-05-31
Publication Date
2024-12-03

AI Technical Summary

Technical Problem

During the planning and engineering stages of building installations, the lack of models of automatic matching functions and equipment leads to a large amount of workload and traditional platforms cannot provide a common model description of functions and equipment interoperability.

Method used

Through machine-readable provider and consumer models, describe the provision and consumption of data by functions, automatically calculate the linking group, and deploy on the controller of the building device, independent of the underlying communication technology stack, to implement functions and equipment Automatic matching and interoperability.

Benefits of technology

It significantly reduces the planning and engineering workload of building installations, improves the automatic matching and interoperability efficiency of functions and equipment, and simplifies the connection and verification of functions and equipment instances independently of communication technology.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119065760A_ABST
    Figure CN119065760A_ABST
Patent Text Reader

Abstract

A computer-implemented method and platform for planning and operating building devices by processing machine-readable provider and consumer models that describe data points that model the provision or consumption of functional data, and exchange of data over a connection with other data points that model the provision or consumption of data for the equipment of the building device.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to a computer-implemented method and platform for planning and operating building equipment of a building using thing-based interworking based on affected contexts and connection groups. The method can be particularly applied during the planning and / or commissioning phase of HVAC equipment in a building. Background Art

[0002] In the past, during the planning of building installations, manual mapping and binding of the provided data points for each instance has been performed in most cases. Furthermore, in conventional platform mappings, addresses have to be edited manually.

[0003] In conventional systems, the interlinking of identifiers or unique names between consumers and producers is performed to some extent by using discovery and instance id mapping.During building installation planning, further preconfigured typed applications with placeholders can be replaced by using automatic substitution.

[0004] The traditional KNX application and group architecture allows to bind functions to devices by mapping group addresses. However, the provided binding only covers execution and instance level and is not communication technology independent.

[0005] Runtime models, such as the OPC UA Platform, cover some aspects of an interoperable platform that supports multiple communication paradigms and technology stacks, but do not provide a common model that describes how functions and devices interoperate with each other and can be used on a template basis.

[0006] Generally speaking, the goal of traditional building equipment models is operation and monitoring, rather than engineering design interoperability. The planning and engineering design of buildings is very labor-intensive because there is still a lack of models that can be used to automatically match the functions and equipment of building equipment. Summary of the invention

[0007] It is therefore an object of the present invention to provide a method and a platform which significantly reduces the planning and engineering effort for planning and engineering building installations of a building.

[0008] This object is achieved by a computer-implemented method comprising the features of claim 1 .

[0009] According to a first aspect, the present invention provides a computer-implemented method for planning and operating a building installation by processing machine-readable provider and consumer models, which describe data points modeling the provision or consumption of data by functions and the exchange of data through connections with other data points modeling the provision or consumption of data by equipment of the building installation.

[0010] In a possible embodiment of the computer-implemented method, the functions and devices of the machine-readable provider and consumer models are deployed as instances to the controllers of the building installations during commissioning.

[0011] In a possible embodiment of the computer-implemented method, the associated connection groups are linked to functions of the machine-readable provider and consumer models.

[0012] In a possible embodiment of the computer-implemented method, during planning of a building installation, the groups of connections linked to the functions are automatically calculated from the bounded contexts affected by the respective functions.

[0013] In a possible computer-implemented embodiment, the affected context of the functionality comprises an area, a sub-area or a room of a building or an installation type or a single device of a building installation.

[0014] In a possible embodiment of the computer-implemented method, the connection set linked to the function comprises a list of instance identifiers of device instances connected to the respective function.

[0015] In a possible embodiment of the computer-implemented method, the connection groups linked to the functions are deployed together with their associated functions to the controller of the building installation during commissioning.

[0016] In a possible embodiment of the computer-implemented method, each data point of the machine-readable provider and consumer models comprises a semantic name, a type and a protocol binding portion.

[0017] In a possible embodiment of a computer-implemented method, the functions are deployed as instances on edge controllers, each edge controller comprising a runtime engine having an interaction layer for reading and writing data points of machine-readable provider and consumer models.

[0018] In a possible embodiment of the computer-implemented method, the deployed function instance runs as a program function on a runtime engine of the edge controller.

[0019] In a possible embodiment of the computer implemented method, the connection groups linked to the functions are evaluated during runtime when an IO router call is made to filter devices of the corresponding connection group.

[0020] In a possible embodiment of a computer-implemented method, machine-readable provider and consumer models are read from a data storage device or database.

[0021] In a possible embodiment of the computer-implemented method, the devices of the building installation include peripheral devices, in particular HVAC devices, which include sensor devices providing data and actuator devices consuming data.

[0022] In a possible embodiment of the computer-implemented method, a common semantic naming model is used to address functions, function instances, function instance data points and to address devices, device instances and device instance data points.

[0023] The present invention also provides a computer-implemented platform for planning and operating building installations of a building, the computer-implemented platform comprising a processor adapted to process stored machine-readable provider and consumer models describing data points modeling the provision or consumption of data by functions, and data exchange through connections with other data points modeling the provision or consumption of data by devices of the building installation. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] In the following, possible embodiments of different aspects of the invention are described in more detail with reference to the accompanying drawings.

[0025] Figure 1 A building site is schematically shown for illustrating the operation of the computer-implemented method according to the present invention; Figure 2 shows connections between function instances and device instances employed by an embodiment of a computer-implemented method according to the present invention; Figure 3 shows the deployment of devices, functions and connection groups on an edge controller of an automation system employed according to an embodiment of the computer-implemented method of the present invention; Figure 4 The intercommunication between devices, functions and connection groups employed by an embodiment of the computer-implemented method according to the present invention is shown; Figure 5 , which includes Figure 5A and Figure 5B , showing the connection of data points between the functions employed by an embodiment of the computer-implemented method according to the present invention and the interfaces of the device instance; Figure 6 The intercommunication between edge devices and peripheral devices through an IO router employed by an embodiment of a computer-implemented method according to the present invention is shown. DETAILED DESCRIPTION

[0026] like Figure 1As shown, heating, ventilation and air conditioning (HVAC) equipment is installed at a building site (HVAC). Different technologies can be used to control the temperature, humidity and purity of the air in enclosed spaces such as buildings. The installed HVAC equipment can be planned to provide thermal comfort and acceptable indoor air quality to the people in the corresponding building. HVAC system design is a branch of mechanical engineering design, which is based on the principles of thermodynamics, fluid mechanics and heat transfer. The components of the HVAC equipment can be optimally matched during planning and commissioning, so that the operator of the building or facility not only benefits from minimized installation and operating costs, but also from a high level of safety against failures.

[0027] like Figure 1 The HVAC devices schematically shown installed in building locations can form part of residential structures that use fresh air from the outdoors (such as single-family homes, apartment buildings, hotels, and senior living facilities); medium to large industrial and office buildings, such as skyscrapers and hospitals; vehicles such as automobiles, trains, airplanes, ships, and submarines; and parts of marine environments where safe and healthy building conditions are regulated in terms of temperature and humidity.

[0028] The three main tasks performed by HVAC devices, namely heating, ventilation and air conditioning, are interrelated, especially the need to provide thermal comfort and acceptable indoor air quality within reasonable installation, operation and maintenance costs. HVAC systems can be used in both domestic and commercial environments. HVAC systems can provide ventilation and maintain pressure relationships between spaces. The means of air delivery and air removal from a space is called indoor air distribution. In modern buildings, the design, installation and control of peripheral equipment that performs these tasks are integrated into one or more HVAC systems. Although HVAC is performed in a single building or other enclosed space, in some cases, the devices involved can form an extension of a larger district heating (DH) or district cooling (DC) network or a combined DHC network.

[0029] To apply an energy efficiency monitoring and optimization system to a heating, ventilation, and air conditioning (HVAC) system, metadata for system components and equipment can be included that can be automatically extracted and stored in a machine-readable manner. Integrating computers and microprocessors into HVAC devices allows facility managers of building facilities to access an almost unlimited stream of data. Facility managers can access system and device data such as supply and return temperatures, occupancy scheduling, and in some cases metered energy usage. Analyzing the available data can enable facility managers to better understand the operation of their HVAC devices, particularly how the different hardware and software components of the HVAC devices interact with each other, and how different factors can affect the performance and efficiency of the HVAC devices. Sensors and metering devices connected to the system, along with installed software, can provide facility managers with a wealth of information.

[0030] The present invention provides a computer-implemented method for planning and operating building equipment, particularly HVAC equipment, such as Figure 1 The method does process machine-readable provider and consumer models read from a storage device or database. The machine-readable provider and consumer models describe data points that model the provision or consumption of data by functions, and data exchanges through connections with other data points that model the provision or consumption of data by devices of building installations. Figure 3 As shown, the functions and devices of the machine-readable provider and consumer models can be deployed as instances to the controllers of the building installations during commissioning.

[0031] In building automation, building equipment can be controlled and automated through flexible application functions running on programmable controllers that interact with sensors, actuators, and other building equipment devices. Building equipment can include HVAC equipment.

[0032] By providing and processing machine-readable provider and consumer models, the function can interact with peripherals and other functions in a way that the planning and engineering effort is minimized. In addition, the machine-readable provider and consumer models are independent of the underlying communication technology stack (e.g., IO, fieldbus, http, CoAP, etc.).

[0033] By processing machine-readable provider and consumer models, devices (primarily exposing data points) and functions (exposing and consuming data points) can be configured and interconnected in various combinations and bounded contexts.

[0034] Furthermore, by processing machine-readable provider and consumer models, devices and functions can be verified at different levels, such as for catalog libraries (type-based), site-specific project planning (instance-based), and at runtime in programmable controllers (execution-based). Figure 1 The functions shown can interact with peripheral devices through various communication media. Typically, they are interconnected via different communication media (e.g., fieldbus). The functions can consume data received from devices such as sensor devices or instrumentation devices. The functions can also send data to devices such as actuators. Functions have affected contexts. For example, Figure 1 As shown, the room coordination function uses the rooms within the building as the context boundaries of the function.

[0035] In a possible embodiment of the computer-implemented method of the present invention, the associated connection groups are automatically linked to the functionality of the machine-readable provider and consumer models, also as Figure 2 The connections linked to a function are calculated during the planning of the building installation from the bounded contexts affected by the respective function. The affected contexts of a function include, for example, areas, subareas or rooms of a building or types of installation or individual devices of a building installation, as also shown in FIG. Figure 1 As shown. In a preferred embodiment, the connection group linked to the function includes a list of instance identifiers of device instances connected to the corresponding functions. The connection group linked to the function can be deployed to the controller of the building device together with its associated function during commissioning. Each data point of the machine-readable provider and consumer model can include a semantic name, type and protocol binding part.

[0036] Functions can be deployed as instances on edge controllers, each of which includes a runtime engine with an interaction layer for reading and writing data points of machine-readable provider and consumer models, such as Figure 6 The deployed function instance runs as a program function on the runtime engine of the edge controller. The connection group linked to the function is evaluated during runtime when an IO router call is made to filter the devices of the corresponding connection group. The devices of the building installation include Figure 6 The peripheral devices shown, particularly HVAC devices, include sensor devices that provide data and actuator devices that consume data.

[0037] In a preferred embodiment, a common semantic naming model is used to address functions, function instances, function instance data points and to address devices, device instances, and device instance data points.

[0038] A computer-implemented platform can be used for planning and operating building installations of a building, comprising a processor adapted to process stored machine-readable provider and consumer models describing data points modeling the provision or consumption of data by functions and data exchanges through connections with other data points modeling the provision or consumption of data by devices of the building installation. The platform may include a provider model enriched with W3C thing descriptions and thing model semantics. A module classification between devices (e.g., data providers) and functions (e.g., data consumers) may be provided. A type / instance model may be implemented for directory / project / controller runtimes. In addition, a runtime engine with a communication technology independent interaction layer may be employed to read and write arbitrary data points. In a preferred embodiment, a common semantic naming model is used at all levels from types to instances and runtime engine interfaces to address devices or functions. The platform may include a consumer model to generally describe which data points of a function (as a client) actually consume data from devices, other functions, or event abstract interfaces. Connection groups may be used for group calculations (during planning) and group name resolution (at controller runtime).

[0039] The provider and consumer model of functions and devices and their interactions can be loaded from a storage device or database. For this model, the W3C Thing Description can be used as a basis.

[0040] In the following, an example of functionality with a provider model enriched with functional classification semantics and also a consumer model is given:

[0041] A module classification between devices (usually data providers) and functions (usually data consumers) can be performed. Devices usually represent externally attached devices or controllers. Thing descriptions may describe how to contact and talk to them. Functions are entities that do something with it (hence functions). Functions usually interact or exchange data with devices (read / write or generally interact) by reading / writing data points. Therefore, devices provide data points (exposed as W3C things with properties). Functions mainly consume data received at data points (consumer points), however functions can also be data providers.

[0042] Figure 2 An example of using a Thing instance during project planning is shown. The bounded context is a location / region 1..n. As a result of the matching algorithm, a connection group that groups the Thing IDs that match the consumer provider connections is linked to the function.

[0043] This allows you to implement a type / instance model for directories / projects / controllers at runtime.

[0044] At the catalog level (type mode), in a possible embodiment, devices and functions can be provided as specific types and saved as library elements in the catalog. Here the thing model can be used.

[0045] For example, a heating application may use a scheduler and a series of valves that implement the data points required by the scheduler interface, such as the set point for temperature heating (SpTRH).

[0046] In a possible embodiment, the provider and consumer models are used to perform validity checks on whether functions within the same application can interact with the associated device.

[0047] At the project level: (instance level during planning) of the HVAC project, the HVAC entities (i.e. the devices, equipment and functions that interact with it) are placed in the customer project as digital twins to represent the real-world item (e.g. scheduler 1 affects valves 1..20 in heating zone 1).

[0048] The Provider and Consumer models can be used to do validity checks to determine if all provider instances match the consumer. The Provider and Consumer models can be further processed to find the correct peer and compute the connection group based on its bounded context.

[0049] At the controller runtime level: (instance level during commissioning), devices and functions (as thing instances) and connectivity groups are deployed to edge controllers for automated interaction with actual hardware, e.g. Figure 3 shown.

[0050] The provider and consumer models can be processed to find the connection group associated with the usage name with the function and filter the connected peers according to the list of things allowed in the connection group.

[0051] The runtime engine can include a communication technology independent interaction layer to read and write arbitrary data points. The edge controller has a runtime that uses the protocol bindings in the thing description to support interoperability with things on a generic level of functionality or specific devices. In this way, the functionality is decoupled from the communication technology of the real device.

[0052] For example, Figure 4 As shown, device A is connected via Modbus protocol binding, while device B is connected via CoAP protocol binding. The function(s) with which devices A, B interact are unaware of the different technologies. A bridge with a common interface is provided by the runtime IO router interface.

[0053] A common semantic naming model can be applied at all levels, from types to instances and runtime engine interfaces, to address a device or function. Semantic names are used to categorize the meaning of a device or function and all data points and give them stable names. Naming is used in matching algorithms to find peers for consumed data points. This is achieved by using stable and unique names that conform to the semantic model.

[0054] Things or instances of equipment or functions can use a description at the thing level (calcElMtrTrf) as well as a description for each data point (ProgState). This can be done using lcas:datatype or @type.

[0055] Also like Figure 5 As shown, the provider and consumer models are used to generally describe which data point functions (as clients) actually consume data from the device.

[0056] The provider model contains a generic description of the data points implemented in a description representing a peripheral device and / or functionality. The W3C Thing Model can be used for this. Each data point is given a stable semantic name and data mode (type of data point, read-only, write-only, etc.) and a protocol binding section which describes the settings (containing the URL and other bus-related parameters) for how to interact with that data point in the device. The provider model for a specific device can be implemented in association with an interface contract using the same description mechanism to enforce a generic representation.

[0057] In a preferred embodiment, the consumer model contains a general description of how a data point in a thing or instance is used in the functionality programmed against it. The consumer model also conforms to the interface and version implemented by the data point. The model can also work without an interface by referencing the device data point directly. This provides some tighter coupling but reduces the burden of maintaining an interface for each use case (such as configuration or calibration functionality).

[0058] The advantage achieved thereby is that it allows the intercommunication with the functional device instance to be inspected and calculated independently of the implementation of the functional device instance, and allows for abstraction and separation of concerns and management.

[0059] The computation of connection groups is performed during planning of a building installation and group name resolution is done during the controller runtime. During planning, connection groups are computed in a bounded context. Connection groups are linked to functions. Connection groups are then deployed and updated along with functions during commissioning. During runtime, connection groups are evaluated when an IO router interface call is made to filter devices for that connection group, also as Figure 6The interface and functionality of the IO Router, how it is programmed, and how calls to its connection groups are resolved at runtime, can also be found in Figure 6 Seen in.

[0060] The computer-implemented method according to the present invention does deal with a machine-readable model of consumer and provider interactions that describes types, instances and runtime environments. The method focuses on data point exchange, as this is the main building block in the building application domain. In W3C Transaction Descriptions, data points can be modeled using attributes (simple read / write) or actions (RPC style).

[0061] Functions can remain generic (based on types) and require no modifications in source code or ID replacement. Connections between functions and device instances can be simplified without adding them separately during planning / debugging. Name-to-Id resolution can be done for each bounded context at both planning and runtime levels.

[0062] The approach leverages provider and consumer models for types and instances. The provider model specifies what things / instances and data points are exposed (W3C Thing Descriptions) and how to reach them (protocol bindings). Additionally, the provider model can use abstract interface definitions to enforce specific contracts when (multiple) data points need to be implemented in different device or function types.

[0063] The consumer model specifies a common model for the client side, i.e. what data points are actually consumed in the function, without exposing its real implementation. Functions can be implemented in different programming languages ​​and paradigms. (block programming, line programming, configuration behavior, etc.).

[0064] Consumes.usageName specifies the instance name used within the function. If more than one is used, multiple connection groups are required.

[0065] Consumes.contextHint gives the planning application a hint on how to scope the bounded context.

[0066] Consumes.min / maxCardinality indicates how many peers are expected in the capability for this particular consumption name. Defaults to unlimited. 0..n.

[0067] The list Consumes.consumedPoints contains the name of the (thing) / data point really used within the feature and directions on how to use it.

[0068] Consumes.consumedInterface references the interface and specific version from which the client consumed the data point.

[0069] Data point / interface matching is performed within the bounded context and connection group filtering is done during runtime.

[0070] At the catalog level, interoperability in the catalog of functions and devices can be checked. The bounded context includes the application type that aggregates the interoperability of functions and devices. boundedContext:application-type_aggregate for each function func with a "consumes" part in boundedContext. For each "consume" element in func["consumes"], check if all consume.consumedPoints exist in all things.providedPoints found in boundedContext and check if the consume.consumedInterface version matches the interface implemented in the things found in bounded_context.

[0071] A peer signature check may be performed, including type and direction (consumer input / output matches provider read / write only). If all checks succeed, the function will successfully reference other devices / functions in the same application-type_aggregate.

[0072] At the plan level, check the plan for interoperability with the instance. This can be selected by the user, and / or can be automatically selected by the discipline filter boundedContext:heating zones1..n. For each function within the bounded context and for each function func in the bounded context that has a "consumers" part, add an empty connection group for each consumer with usageName as the key of the function. For each "consume" element in func["consumes"], check if all consume.consumedPoints are present in all thing.providedPoints found in the bounded context, and check if the consume.consumedInterface version matches the interface implemented in the thing found in the bounded context. This includes a direction check that consumer input / output matches provider read / write). A point signature check can be performed, including type and direction (consumer input / output matches provider readonly read / write), and a list of all things matching the check is generated. This list is updated in the associated connection group.

[0073] For connection group filtering during runtime for each usageName of a feature, the corresponding connection group and filter results are found in writeType or readType calls for all elements.

[0074] In a possible embodiment, the machine-readable provider and consumer models can be edited by an engineer through a graphical user interface GUI. The machine-readable provider and consumer models can be customized for a specific building and stored in a database of the platform. The machine-readable provider and consumer models can provide simulation results during the planning of building installations. The functions and devices of the optimized machine-readable provider and consumer models can be deployed as instances on controllers of building installations, particularly edge controllers, during commissioning.

Claims

1. A computer-implemented method for planning and operating a building installation by processing machine-readable provider and consumer models that describe data points modeling the provision or consumption of data by functions, and the exchange of data through connections with other data points modeling the provision or consumption of data by devices of the building installation.

2. The computer-implemented method of claim 1 , wherein: The functions and devices of the machine-readable provider and consumer models are deployed as instances to the controllers of the building installations during commissioning.

3. A computer-implemented method according to claim 1 or 2, wherein the associated connection groups are linked to functions of the machine-readable provider and consumer models.

4. The computer-implemented method of claim 3, wherein: During the planning of a building installation, the groups of connections linked to functions are calculated according to the bounded contexts affected by the corresponding functions.

5. The computer-implemented method of claim 4, wherein the affected context of the function comprises an area, a sub-area or a room of a building or an equipment type or a single device of a building equipment. 6 . The computer-implemented method of claim 4 , wherein the set of connections linked to a function comprises a list of instance identifiers of device instances connected to the corresponding function.

7. The computer-implemented method of claim 5, wherein the connection groups linked to functions are deployed to the controller of the building device along with their associated functions during commissioning.

8. A computer-implemented method according to any one of the preceding claims 1 to 7, wherein each data point of the machine-readable provider and consumer models comprises a semantic name, type and protocol binding parts.

9. A computer-implemented method according to any one of the preceding claims 2 to 8, wherein the functionality is deployed as instances on edge controllers, each edge controller comprising a runtime engine having an interaction layer for reading and writing data points of machine-readable provider and consumer models.

10. The computer-implemented method of claim 9, wherein the deployed function instance runs as a program function on a runtime engine of the edge controller.

11. The computer-implemented method of claim 10, wherein: The connection groups linked to the functions are evaluated during runtime when an IO router call is made to filter the devices of the corresponding connection group.

12. A computer-implemented method according to any one of the preceding claims 1 to 11, wherein: The machine-readable provider and consumer models are read from a data store or database.

13. A computer-implemented method according to any one of the preceding claims 1 to 12, wherein: The equipment of the building installation includes peripheral equipment, in particular HVAC equipment, which includes sensor equipment that provides data and actuator equipment that consumes data.

14. A computer-implemented method according to any one of the preceding claims 1 to 13, wherein: A common semantic naming model is used to address functions, function instances, function instance data points, and to address devices, device instances, and device instance data points.

15. A computer-implemented platform for planning and operating building installations of a building, comprising a processor adapted to process stored machine-readable provider and consumer models describing data points modeling the provision or consumption of data by functions and the exchange of data through connections with other data points modeling the provision or consumption of data by equipment of the building installation.