Analytics & ML · Study deck

Edge Acquisition: Control Paths and Bandwidth

A cloud command travels to a remote service, while an edge alarm is checked near the device.

Data Dora is your guide for this deck.

edge
Data Dora, the module guide, in a scene from this chapter.
iotclass.org

After studying this chapter

Learning objectives

You will be able to:

  • Explain: The widening orders-of-magnitude gap means one forwarding policy cannot fit every source: sparse events may travel intact, periodic measurements may be batched, and continuous media often needs local selection or inference.
  • Explain: This connects the example to the running volume argument: edge windows should retain the features required by the decision while replacing a continuous six-axis stream with an auditable summary.
  • Explain: Edge takeaway: High-frequency six-axis data is useful locally, but the transmission layer should send aggregated summaries instead of every raw sample.
  • Trace cloud and edge control paths with failure states.
Edge-centric cold-store path with a local gateway and actuator loop plus a separate evidence record sent to cloud analytics.
Edge-centric cold-store path with a local gateway and actuator loop plus a separate evidence record sent to cloud analytics.
iotclass.org

Major section

Cloud and Edge Control Paths

The: DESIGN INFERENCE explains that central history is simple, but a WAN failure interrupts the decision unless a safe fallback exists.

  • That split improves continuity but makes gateway update and replay ownership explicit.
  • The latency chips and continuity ledger show why urgency, sensitivity, and replay needs—not data volume alone—set placement.
  • That platform supplies shared context and rules, but it does not erase local ownership of buffering and replay.

Why it matters

As the number of zones grows, those two records prevent a delayed irrigation instruction from being mistaken for a current one and show whether approved control actually reached the field.

Cloud-centric cold-store path from a temperature sensor through an IP gateway and cloud rule to an actuator, with WAN continuity called out as the trade-off.
Cloud-centric cold-store path from a temperature sensor through an IP gateway and cloud rule to an actuator, with WAN continuity called out as the trade-off.
iotclass.org

Major section

Data Generation Patterns

Understanding data generation patterns is essential for designing efficient edge acquisition systems.

  • Different device types produce vastly different data volumes and require different handling strategies.
  • This carries the category model into the running acquisition narrative by turning device capability into a bandwidth, storage, and processing obligation.
Data generation statistics for IoT devices
Data generation statistics for IoT devices
iotclass.org

Major section

Mobile figure summary

Big Things: Servers and PLCs have full IP connectivity, so they can upload structured data directly to the cloud.

  • Small IP Things: Smart cameras and other embedded devices connect over Wi-Fi or cellular and can pre-filter data before upload.
  • Non-IP Things: Simple sensors use Zigbee, BLE, Modbus, or similar buses and rely on a nearby gateway for translation and aggregation.
  • Connectivity path: Non-IP sensor -> gateway -> cloud, while Big Things and Small IP Things can usually reach the cloud without protocol translation.
Data generation rates and volumes comparison table
Data generation rates and volumes comparison table
iotclass.org

Major section

Data Volume by Device Type

This view shows how data generation rates vary dramatically by device type, driving different edge processing strategies.

  • The widening orders-of-magnitude gap means one forwarding policy cannot fit every source: sparse events may travel intact, periodic measurements may be batched, and continuous media often needs local selection or inference.
  • The comparison connects the chapter's device categories to its running budget argument: preserve raw evidence only where the downstream decision needs it, and measure the bandwidth, storage, energy, and privacy cost of that choice.
iotclass.org

Major section

Inertial Measurement Example

High-frequency sensors like accelerometers and gyroscopes demonstrate why edge aggregation is critical.

  • Accelerometer changes combine motion and gravity; gyroscope changes record rotation.
  • A motion event can therefore span several axes and both sensor types, which is why a single average may erase useful structure.
  • This connects the example to the running volume argument: edge windows should retain the features required by the decision while replacing a continuous six-axis stream with an auditable summary.
Accelerometer and gyroscope example sensor data
Accelerometer and gyroscope example sensor data
iotclass.org

Major section

Mobile figure summary

Edge aggregation reduces this to statistical summaries at 1 Hz.

  • Accelerometer axes: X, Y, and Z linear acceleration are tracked together to capture movement and gravity.
  • Edge takeaway: High-frequency six-axis data is useful locally, but the transmission layer should send aggregated summaries instead of every raw sample.
  • Transmitting raw data as 16-bit integers would require ~1.2 KB/s -- unsustainable for battery-powered devices on LPWAN networks.
Data generation rates and volumes comparison table
Data generation rates and volumes comparison table
iotclass.org

Deck summary

Key takeaways

The: DESIGN INFERENCE explains that central history is simple, but a WAN failure interrupts the decision unless a safe fallback exists.

  • Understanding data generation patterns is essential for designing efficient edge acquisition systems.
  • Big Things: Servers and PLCs have full IP connectivity, so they can upload structured data directly to the cloud.
  • This view shows how data generation rates vary dramatically by device type, driving different edge processing strategies.
  • High-frequency sensors like accelerometers and gyroscopes demonstrate why edge aggregation is critical.
iotclass.org

Retrieval practice

Recall check 1 of 2

Data Dora says: answer from memory, then check your reasoning.

Q1A cold-store WAN link fails while the compressor still needs control decisions. Which design preserves the local decision path?

ASend the sensor directly to cloud history
BEvaluate the rule at the edge gateway
CWait for the remote event replay
DEvaluate the rule in cloud analytics
Show answer

Answer: B The edge path connects gateway decisions to a local actuator while cloud analytics receive evidence separately.

iotclass.org

Retrieval practice

Recall check 2 of 2

Data Dora says: answer from memory, then check your reasoning.

Q2A gateway serves continuous high-volume sources and sparse event-driven sensors. What should guide its bandwidth plan?

APlan storage from the number of categories
BGroup sources by their direct IP capability
CCompare volume, transmission rhythm, and connectivity
DAssign equal upload capacity to each device
Show answer

Answer: C The device-class comparison connects these properties to bandwidth, storage, and processing needs.

Q3A raw IMU stream uses 1200 B/s. Its local summary uses 18 B/s. How many bytes per second does the uplink save?

A1218 B/s
B67 B/s
C1182 B/s
D18 B/s
Show answer

Answer: C Subtract the summary rate from the raw rate.

iotclass.org

Print reference

Answers

Answer key.

  1. B · The edge path connects gateway decisions to a local actuator while cloud analytics receive evidence separately.
  2. C · The device-class comparison connects these properties to bandwidth, storage, and processing needs.
  3. C · Subtract the summary rate from the raw rate.
iotclass.org