Modul 6 von 11 · 📖 5 min Lesezeit · ⏱ 30 min gesamt

FI-DV 06 Edge Computing und Gateways (EN)

Inhaltsverzeichnis (6 Abschnitte)
  1. Concepts and Background
  2. Architecture Diagram
  3. Practical Steps
  4. Common Pitfalls
  5. Further Resources
  6. Knowledge Check

FI-DV 06 Edge Computing and Gateways

Edge Computing enables local processing of data directly at the source, rather than sending it to central cloud systems. In this module, you will learn how Edge Gateways serve as an interface between physical devices and cloud services to reduce latency and save bandwidth. You will gain insights into architectures that combine local data processing with cloud services, and practical applications using frameworks such as EdgeX Foundry and Azure IoT Edge.

Concepts and Background

Edge Computing
Decentralized data processing that occurs close to data sources to minimize latency and reduce network load.
Edge Gateway
A physical or virtual device that acts as an intermediary between local devices (sensors, actuators) and cloud services, performs protocol translations, and enables local processing.
EdgeX Foundry
An open-source framework for Edge-IoT that provides a standardized architecture for Edge devices and ensures interoperability between different manufacturers.
Azure IoT Edge
Microsoft's platform for Edge Computing that enables cloud functionality to be provided directly on local devices and allows IoT solutions to be extended modularly.
Latency
The delay between requesting an action and the start of the response, which is significantly reduced in Edge Computing through local processing.

Architecture Diagram

flowchart LR
  A[IoT Devices] --> B[Edge Gateway]
  B --> C[Local Data Processing]
  B --> D[EdgeX Foundry]
  D --> E[Registration & Discovery]
  D --> F[Data Aggregation]
  D --> G[Local Storage]
  B --> H[Azure IoT Edge Hub]
  H --> I[Cloud Services]
  H --> J[Azure IoT Hub]
  H --> K[Azure Stream Analytics]

Practical Steps

  1. Install Docker on your Edge Gateway, as both EdgeX and Azure IoT Edge run as containers. This ensures a consistent environment.
  2. Configure the network interfaces of the gateway to ensure that IoT devices and the cloud can communicate through separate interfaces.
  3. Deploy EdgeX Foundry with the command 
    docker-compose -f edgex-compose.yml up -d
    to start the core services.
  4. Install Azure IoT Edge Runtime with 
    curl -L https://aka.ms/iotedged-linux-x64-latest -o iotedged-linux-x64-latest.deb && sudo dpkg -i iotedged-linux-x64-latest.deb
    .
  5. Configure the EdgeX Device Services for your specific IoT devices by adjusting the configuration files in the /etc/edgex/devices directory.
  6. Create an Azure IoT Edge Module in the Azure Portal that contains your local logic and upload it as a Docker image.
  7. Deploy the module to your Edge Gateway via the Azure IoT Edge settings by specifying the module ID and the desired target device ID.
  8. Implement local data filtering to send only relevant data to the cloud and save bandwidth.
  9. Test the failover functionality by interrupting the connection to the cloud and ensuring that data is stored locally.
  10. Implement a security policy that enforces access to the Edge Gateway via SSH certificates instead of passwords.

Common Pitfalls

Further Resources

Knowledge Check

Four questions for self-assessment. Click on each question to see the correct answer and explanation.

What is the main advantage of Edge Computing compared to pure cloud processing?
  • A) Higher security through centralized data management
  • B) Reduced latency through local data processing
  • C) Lower costs through less hardware usage
  • D) Easier implementation without specialized knowledge

Correct Answer: B. Edge Computing reduces latency by processing data directly at the source, rather than having to be sent to remote cloud systems. Option A is incorrect because Edge Computing is decentralized and requires different security considerations. Option C is incorrect because Edge Computing requires additional hardware. Option D is false because Edge Computing requires specific expertise.

What function does an Edge Gateway fulfill in an IoT architecture?
  • A) It serves exclusively as a pure data relay point
  • B) It translates protocols and performs local processing
  • C) It completely replaces cloud services
  • D) It stores all data permanently locally

Correct Answer: B. An Edge Gateway acts as an intermediary between local devices and cloud services, performs protocol translations, and enables local data processing. Option A is incomplete because Gateways do more than just forward. Option C is incorrect because Gateways complement, not replace, cloud services. Option D is incorrect because Gateways typically only store data temporarily.

What is a key difference between EdgeX Foundry and Azure IoT Edge?
  • A) EdgeX Foundry is a commercial p