Protocol Bridge Boundary Experiments
Protocol Bridge Boundary Experiments
Compare Four Protocol translation Paths
Apply the sequence to a factory tank. A Modbus register contains 725 with scale 0.1 kPa, so the protocol bridge derives . It publishes the tank identity, 72.5 kPa, source observation time, quality, and mapping version. If the cloud schema expects pascals, the next explicit conversion is . Keeping both rules makes the result re-derivable.
Now compare a LoRaWAN soil probe. Its frame counter helps detect a replay, while the tank’s polled Modbus source needs a separate sample identifier. Compare a building thermostat whose protocol provides a quality flag with an analogue probe that does not. The normalized records may share a protocol target shape, but their evidence cannot claim identical source certainty.
Predict one result for each diagram. Trace a known tank value through every pipeline boundary. Force a source timeout and locate its failure branch. Submit an invalid protocol target bridging record and confirm that it is rejected visibly. Send an unauthorized command and verify that it never reaches the field device. The four results show whether the examples preserve meaning in both telemetry and control directions.
Retain the four bridging examples together. Their common protocol target fields show where normalization helps, while their source samples show why one decoder cannot stand in for another. That comparison is the evidence for a reusable protocol bridge pattern.
Summary: Carry One Reading Across a Translation Boundary
Picture a factory meter that exposes a numbered register while a cloud service expects a named temperature event. A bridge can move the bytes, yet still attach the wrong unit, time, identity, or meaning. The system owner must prove that the target record means what the source measured.
Choose one real reading and draw both sides. Record source address, field meaning, unit, source time, quality, poll rule, translated name, target route, delivery state, and owner. Keep a versioned point map that explains every change. Mark which side controls commands and which side only reports.
Test a source timeout, a repeated value, a changed map, a wrong unit, a full buffer, a target outage, a restart, and replay after recovery. Check that stale data is marked, bad quality survives, duplicates are safe, and delayed records keep their event time. Trace one command back with the same care.
Keep urgent safe control on the local side when a distant target can be late. Translation does not create trust, and a successful connection does not prove meaning. Recheck identity and rights at the boundary, especially for writes.