Integration & Gateways · Study deck
Edge and Fog Gateways
A wildfire sensor can trigger a local alarm in seconds even when the mountain backhaul is down.
Gateway Gus is your guide for this deck.
After studying this chapter
Learning objectives
You will be able to:
- place each processing task at the layer where its supporting evidence can survive
- design a data-reduction pipeline that keeps reduced records traceable to their source
- treat "at the edge" as a claim that needs evidence, not a location label
- define the cloud handoff as a contract, not just a network hop
Major section
Place Each Task Where the Evidence Survives
It may need to warn the driver now, join records at the depot, and send a smaller history to a central service.
- Those jobs do not all belong in the same place.
- A gateway is a bridge that moves or changes data between systems.
- Central work keeps long history and supports work across many sites.
Major section
Place the Fire Decision Where It Can Finish
The placed gateway placement can read those devices, reject impossible values, and sound the local siren.
- A placed fog node at the ranger office can compare several ridges and suppress one isolated false alarm.
- The cloud placement can retain images, train models, and show long-term patterns.
- Reduction must stay traceable.
Major section
Place the Fire Decision Where It Can Finish (continued)
Yet the placed fog node can also fail.
- The sensor-to-edge path takes 120 ms, local processing takes 80 ms, and siren activation takes 150 ms.
- The local total is (120+80+150=350\ \mathrm{ms}), leaving 1,650 ms of margin.
- Privacy can force a placement boundary too.
Major section
Place the Fire Decision Where It Can Finish (continued)
A cloud placement round trip that varies from 900 ms to 4 s cannot be the required alarm path.
- It may confirm or enrich the event later, but the edge must own the immediate safety action.
- The feature record should name the source camera, window times, model version, selected frames, and reason for selection so the fog result can be audited.
- Fog placement helps when several placed edge sites share a regional fact.
Major section
Place the Fire Decision Where It Can Finish (continued)
The ranger office can compare wind direction and alarms from three ridges without sending every frame to a distant cloud placement.
- Placed edge sites need an offline mode, retained identifiers, and a rule for reconciling events when the regional link returns.
- Disconnect the placed fog node and expect each ridge to keep its local rule but lose cross-site confirmation.
- The placed fog service may receive location and confidence but no continuous video.
Major section
Place the Fire Decision Where It Can Finish (continued)
The exact latency and capacity depend on the deployed hardware, radio, model, and workload.
- Re-run the placement measurements on the target devices; the worked values explain the decision method, not a universal performance promise.
- The edge may turn a camera frame into a smoke score and retain only the two evidence images named by policy.
- A fog model expecting a new feature cannot silently treat old edge records as current.
Major section
Summary
A mobile gateway can act as an edge node, a fog node, or a cloud handoff point, and a real release often uses several of these layers at once.
- Placement is a per-task decision that must be reviewable; "local is always faster" and "the cloud is always easier" are both wrong as universal rules.
Deck summary
Key takeaways
It may need to warn the driver now, join records at the depot, and send a smaller history to a central service.
- The placed gateway placement can read those devices, reject impossible values, and sound the local siren.
- Yet the placed fog node can also fail.
- A cloud placement round trip that varies from 900 ms to 4 s cannot be the required alarm path.
- The ranger office can compare wind direction and alarms from three ridges without sending every frame to a distant cloud placement.
Retrieval practice
Recall check 1 of 3
Gateway Gus says: answer from memory, then check your reasoning.
Q1Which task best fits the 'nearby fog' layer rather than the sensor edge or the cloud?
Show answer
Answer: B Fog is a shared local coordination layer: it aggregates and reconciles across several sources near the deployment, which neither a single sensor nor the distant cloud is positioned to do.
Retrieval practice
Recall check 2 of 3
Gateway Gus says: answer from memory, then check your reasoning.
Q2A mobile gateway must classify short vibration bursts while the upload path is often unavailable. Raw vibration windows are large and only exceptions need cloud review. Where should the first classification run?
Show answer
Answer: C The mobile gateway is close enough to classify during outages and to cut upload volume, while still preserving exception raw windows and audit evidence for the cloud review.
Retrieval practice
Recall check 3 of 3
Gateway Gus says: answer from memory, then check your reasoning.
Q3The cloud receives only an hourly summary from a phone gateway. What additional information best makes that summary reviewable?
Show answer
Answer: C A summary is auditable only when the cloud can trace who produced it, from what inputs, with which rule or model version, and under what quality state, with raw evidence available on request.
Print reference
Answers 1 of 2
Answer key.
- B · Fog is a shared local coordination layer: it aggregates and reconciles across several sources near the deployment, which neither a single sensor nor the distant cloud is positioned to do.
- C · The mobile gateway is close enough to classify during outages and to cut upload volume, while still preserving exception raw windows and audit evidence for the cloud review.
Print reference
Answers 2 of 2
Answer key.
- C · A summary is auditable only when the cloud can trace who produced it, from what inputs, with which rule or model version, and under what quality state, with raw evidence available on request.