← Back to the chapter · Previous detail
Technical detail · Why Bridge Protocols in IoT
Four families of bridge failure
Semantic loss occurs when a unit disappears, a register map is ambiguous, or a display name replaces identity. Numbers may look plausible while their interpretation remains uncertain. Keep a point map with unit, scale, enumeration, and a versioned mapping.
Timing loss occurs when gateway time replaces source time or a last-good value is reused without a stale marker. An old value can then drive a fresh-looking alarm or control decision. Keep separate source and gateway timestamps plus a freshness or quality flag.
Reliability loss occurs when acknowledgment removes work too early, overflow silently drops messages, or replay duplicates side effects. Symptoms include missing records, double-counted events, and actions fired twice. Capture acknowledgment, overflow, dead-letter, and replay behavior with samples.
Boundary loss occurs when a bridge becomes an uncontrolled command path or a target route accepts unreviewed fields. An unauthorized or unaudited write can change device state even while telemetry remains correct. Keep authorization rules by route, an audit record, and a reviewed target schema. Because commands have physical effects, this failure deserves particular attention in release review.