Edge Node Management

IEF can connect to a large number of edge nodes, automatically generate configuration information about edge nodes, and efficiently and conveniently manage edge nodes where Edge Agent is installed. In this way, all edge nodes can be managed, monitored, and maintained in the cloud.

Figure 1 Edge node management

Edge Device Management

Devices can be connected to IEF through edge nodes by using the MQTT, Modbus, or OPC UA protocol. After devices are connected to IEF, you can manage them on IEF in a unified manner.

Figure 2 Edge device management

Edge Application Management

IEF allows containerized applications and functions to be deployed on edge nodes, and manages these containerized applications and functions.

• Containerized applications

  IEF allows edge applications to be deployed on edge nodes as containers. Specially, edge applications are packed into container images and pushed to Software Repository for Container (SWR) of HUAWEI CLOUD. Then, edge applications are deployed on edge nodes by using the edge application template created on IEF. In addition, IEF supports version upgrade, configuration change, uninstallation, monitoring, and log collection for applications.

  The container ecosystem is prosperous, which can help your containerized applications seamlessly switch to other runtime environments and enhance their portability. In addition, containers can isolate resources better and support CPU/GPU scheduling.

• Functions

  IEF allows functions in HUAWEI CLOUD FunctionGraph to be deployed on edge nodes. Then, IEF can control the start and stop of the functions.

  Functions provide more lightweight architecture and faster deployment than containers. You are advised to use functions in the following scenarios:

  • Edge node resources are limited.
  • The service logic of edge applications is event-driven. In this way, functions can quickly respond to service requirements through the event-based triggering mechanism.

Message Route Management

IEF provides the message routing function. Based on configured routes, IEF forwards edge messages to the corresponding service endpoint (sender or recipient). In this way, messages can be forwarded based on specified paths, enhancing flexibility in data routing control and improving data security.

Currently, the following message forwarding paths are supported:

• SystemREST -> ServiceBus: The REST gateway interface is called to obtain file services on edge nodes. The collaboration with the edge file service in the edge market is required.
• SystemREST -> SystemEventBus: The REST gateway interface is called to send messages to SystemEventBus (MQTT Broker) on edge nodes.
• SystemEventBus -> DIS/API Gateway: SystemEventBus forwards the edge device data bound to edge nodes to the Data Ingestion Service (DIS) or a specified API Gateway address. The collaboration with the edge device connection application in the edge market is required. Alternatively, SystemEventBus directly forwards the edge device data to DIS or a specified API Gateway address through SystemEventBus on edge nodes.
• SystsEdgedb -> Systsdb: SystsEdgedb calls the REST interface of CloudTable at the edge to upload the time series data of edge nodes to CloudTable. The collaboration with the CloudTable application in the edge marketplace is required.

Figure 4 Message forwarding paths