Method for updating an edge device, system for executing the method, and computer-readable data storage

Abstract

The invention discloses a method for updating an edge device, wherein the edge device is connected to at least one field device of the process automation, wherein the edge device is connected to a cloud-based application, wherein the edge device comprises several individual software components, wherein the edge device is configured to load feature detectors which are configured to recognize features of the edge device, or at least to recognize which field device is connected to the edge device, wherein a feature or group of features is associated with a software component, the method comprising the steps of: sending a message from the edge device to the cloud-based application asking whether any updates are available; sending a response from the cloud-based application with a list of general firmware updates from the cloud-based application to the edge device;Request to the cloud-based application to download new feature detectors; receiving the feature detectors in response to the request; executing the feature detectors to collect the features, in particular edge device capabilities, field protocols, gateways, device types, etc.; request from the edge device to the cloud-based application to send only the software components required for the edge device's features, in particular including dependent software components; sending the requested software components from the cloud-based application to the edge device in response; and installing and executing the received software components on the edge device.

Description

[0001] The invention relates to a method for updating an edge device, a system for executing the method, and a computer-readable data storage device.

[0002] An edge device enables the connection of field devices in an industrial process automation plant to a cloud-based application. Data is transferred to the cloud via the plant's internet connection. The information required for the cloud-based application is regularly read from the field devices by the edge device and stored in the cloud-based application. The "cloud-based" application is also frequently referred to as a "cloud-hosted" application, or simply as "the cloud."

[0003] "Cloud" or "cloud computing" describes a model that provides shared computing resources as a service on demand – usually via the internet and independent of the device used – quickly and with minimal effort. These resources can take the form of servers, data storage, or applications. The offering and use of these computing resources is defined and typically occurs via an application programming interface (API), or for end users via a website or app.

[0004] Edge devices also shift computer applications, data, and services away from local plant computers. The term "edge" refers to the fact that the relevant operations on the edge device take place at the "edge" of the network, i.e., in the network periphery between the field device and the cloud-based application. These operations can include the acquisition, aggregation, processing, and analysis of data. The calculations are performed decentrally at the point where the data actually originates or is collected.

[0005] The Endress+Hauser Group, for example, sells Edge devices under the name "FieldEdge SGC500".

[0006] Although the edge device is deployed, installed, and configured once in a plant, it should be possible to add functionality throughout its entire lifespan to offer continuously expanding cloud services. When a new cloud feature with customer value is introduced, it may require additional information from the field devices.

[0007] The invention is based on the objective of keeping an Edge device easily updatable throughout its entire lifespan.

[0008] The problem is solved procedurally by the method according to claim 1. Specifically, this is achieved by a method for updating an edge device, wherein the edge device is connected to at least one field device of the process automation, wherein the edge device is connected to a cloud-based application, wherein the edge device comprises several individual software components, wherein the edge device is configured to load feature detectors which are configured to recognize features of the edge device, or at least to recognize which field device is connected to the edge device, wherein a software component is assigned to a feature or a group of features, the method comprising the steps of: sending a message from the edge device to the cloud-based application asking whether any updates are available;Sending a response from the cloud-based application to the edge device containing a list of general firmware updates; requesting the cloud-based application to download new feature detectors; receiving the feature detectors in the response; executing the feature detectors to collect features, in particular edge device capabilities, field protocols, gateways, device types, etc.; requesting the cloud-based application from the edge device to send only the software components required for the edge device's features, including dependent software components; sending the requested software components from the cloud-based application to the edge device in response; and installing and executing the received software components on the edge device.

[0009] The basic concept is therefore to use a software platform in the edge device and to optionally allow the loading, installation and execution of software components even during runtime without shutdown.

[0010] One implementation provides that updating includes: updating or upgrading software components already installed on the Edge device, installing new software components, especially those with new features, and / or deleting software components installed on the Edge device.

[0011] One design provides for the process to take place during the operating time of the Edge device.

[0012] One embodiment provides that the feature detector recognizes: networks, bus systems and / or gateways connected to the edge device; and / or the resources, capabilities, configuration and / or settings of the edge device, in particular data preprocessing, data correlation and data aggregation, field device types, and / or field device configurations, in particular (e.g., a sensor with an activated special function for which certain data can be read).

[0013] One design provides that the software components include: a configuration setup, a schedule for data acquisition from the connected field devices or idle periods, or device-specific data acquisition.

[0014] The system-side problem is solved by claim 8. Specifically, the system for carrying out the method as described above comprises an edge device; at least one field device; and a cloud-based application.

[0015] The task is further solved by a computer-readable data storage device that stores program instructions which, when executed, cause a system as described above to perform a procedure as described above.

[0016] This will be explained in more detail using the following figures. Fig. Figure 1 shows the system under consideration. Fig. Figure 2 shows the Edge device repository.

[0017] An edge device 104 is connected to one or more field devices 90. A field device 90 is, for example, a sensor for measuring a quantity in process automation technology. The field device 90 has its own specific configuration 95. The field device 90 is connected to the edge device 104 via a fieldbus, such as PROFIBUS, PROFINET, FoundationFieldbus, HART, or similar.

[0018] The edge device 104 has firmware consisting of individual software components 106. These are numbered for simplicity. Two field devices are shown. Software components 106 can be function-specific, protocol-specific, device-type-specific, or even device-specific; see also the example in Fig. 1. Which software components 106 are installed and run on the edge device 104 depends on the connected field devices 90 and their configuration 95, or on data preprocessing for a cloud-based application. The software components 106 are organized on a firmware platform 107.

[0019] The Edge device 104 is connected to a cloud-based application, hereinafter referred to as “Cloud 100” (reference 103).

[0020] In order to ensure that the software components 106 are always up to date, and that new features and possibilities provided by the cloud 100 are supported by the edge device 104, the claimed method is proposed.

[0021] The edge device 104 regularly sends a message to the cloud 100, specifically to the edge device update manager 102, to generally request all available updates (not specific to the edge device) that can be downloaded and installed (i.e., changes since the last request). A user 50 accesses the cloud 100 via a terminal or computer. The cloud 100 comprises a storage location 101 with an edge device configuration repository 121, an edge device repository 123, and an edge device register 120 containing the following data 122.

[0022] If updates are available, the edge device 104 requests updates for software components 106 for its own configuration and equipment, and executes the new component(s) on its platform 107. This occurs at runtime. These updates are sent in a packet (reference 110) as a response to the update request from the cloud 100 to the edge device 104 (reference 111).

[0023] Firmware component 106 is a feature detector, meaning it is a component that runs and examines the capabilities and settings of the edge device, connected field networks, and field gateways, and, most importantly, identifies the types of connected field devices. For example, a feature detector detects networks, bus systems, and / or gateways connected to the edge device; the resources, capabilities, configuration, and / or settings of the edge device, particularly data preprocessing, data correlation, and data aggregation; and / or field device types and configurations, such as a sensor with a special function enabled, for which specific data can be read.

[0024] Another firmware component is a configuration module. This can, for example, implement connectivity to EtherNet / IP, store the IP address of a field gateway, or activate a cloud service subscription.

[0025] Another firmware component includes a data acquisition schedule and, for example, initiates regular queries of system diagnostic data from all connected HART devices (from different manufacturers) based on protocol-defined requirements.

[0026] Another firmware component implements manufacturer- or device-type-specific data requests, such as diagnostic data or data for predictive maintenance. These can be performed regularly, on a schedule, or on demand.

[0027] The following procedure can be carried out, see Fig. 2 in combination with Fig. 1:

[0028] A new feature is being introduced in the cloud and offered as an optional subscription. This feature may require a functional edge device extension, such as new edge computing preprocessing results, new field network connectivity (e.g., support for an additional gateway or for the new Industrial Ethernet protocol), or additional data acquisition for field devices.

[0029] Then, a new FeatureID is added to the cloud-hosted edge device configuration repository 121. A feature detector software component is implemented for this new FeatureID ( Fig. 2 (right) and also a software component that runs on the Edge device 104. Both software components are added to the “Edge Firmware Repository 123”. The Edge Firmware Repository 123 includes all software components 106.

[0030] Finally, the version number of the Edge repository is incremented and released; it is then offered by the Edge device for update requests.

[0031] The Edge Device 104 detects the new information and downloads the Edge Device Configuration Repository as well as new feature detector software components.

[0032] If a new feature detector is available in the edge device, it is executed. If a feature is found to be available, the edge feature list is updated with the corresponding FeatureID according to the edge device configuration repository.

[0033] The Edge device regularly checks the now updated Edge feature list and detects a discrepancy between the installed software component versions and those included in the feature list.

[0034] The software components that can be updated are requested for download, including the list of dependent software components.

[0035] Finally, the software components are stored, installed, and launched on the Edge device in response to the download requests.

[0036] The new software components will run as defined and publish additional data for all features - including the new features of new cloud functions based on actual field data. Reference symbol list 50 users 90 field device 95 Field Device Configuration 100 Cloud 101 storage 102 Edge Device Update Manager 103 Connection 104, 100 104 Edge device 105 Edge devices firmware 106 software components 107 Edge device firmware platform 110 packets out of 106 111 Sending from 106 to 104 120 field device register 121 Edge Device Configuration Repository 122 Field device Register entry 123 Edge device repository

Claims

[1] Procedure for updating an edge device, wherein the edge device is connected to at least one field device of the process automation, wherein the edge device is connected to a cloud-based application, wherein the edge device comprises a plurality of individual software components, wherein the edge device is configured to load feature detectors configured to detect features of the edge device, at least to detect which field device is connected to the edge device, where a software component is assigned to a feature or group of features, the procedure comprises the steps: - Sending a message from the edge device to the cloud-based application asking if there are any updates in general; - Sending a response from the cloud-based application with a list of general firmware updates from the cloud-based application to the edge device; - Request to the cloud-based application to download new feature detectors; - Receiving the feature detectors in the answer to the question; - Implementation of feature detectors to collect features, in particular edge device capabilities, field protocols, gateways, device types, etc.; - Request from the edge device to the cloud-based application to send only the software components required for the features of the edge device, in particular including the dependent software components; - Sending the requested software components from the cloud-based application as a response to the edge device; and - Install and run the received software components on the edge device. [2] The method according to claim 1, wherein the updating comprises: an update or upgrade of software components already installed on the edge device, the installation of new software components, in particular with new features, and / or the deletion of software components installed on the edge device. [3] The method of claim 1 or 2, wherein the method runs during the runtime of the edge device. [4] Method according to one of the preceding claims, wherein the feature detector detects: - networks, bus systems and / or gateways connected to the edge device, and / or - the resources, capabilities, configuration and / or settings of the edge device, in particular data preprocessing, data correlation and data aggregation, and / or field device types, and / or field device configurations. [5] Method according to one of the preceding claims, wherein the software components comprise: a configuration device, a schedule for the data acquisition of the connected field devices or rest phases, or a device-specific data acquisition. [6] System for carrying out the method according to any one of the preceding claims, comprising - an edge device; - at least one field device; and - a cloud-based application. [7] A computer-readable data storage device storing program instructions which, when executed, cause a system according to the preceding claim to perform a method according to any one of the preceding claims.

Images