Definition
In the "Remote Telemetry of Refrigerated Containers (Logistics Box Perspective)" scenario, sensors and business terminals often access the platform through cellular IoT; factors such as coverage quality, latency, security, and the full lifecycle of the SIM card need to be considered.
Technical Features
It is recommended to differentiate telemetry, alarms, configuration, and OTA traffic; configure caching and retransmission in weak network environments; include TLS, certificates, and keys in the change and rollback strategy.
Use Cases
Applicable to distributed sites and remote operations. SimtoLink can provide combined capabilities like connection management, data pool, and directed/private networks, supporting large-scale replication.
Key points for cooperation with IoT SIM cards
- Ledger: ICCID / IMEI bound to device number, installation location, and person in charge.
- Network: APN, whitelist, SIM-device binding, and regional/roaming policies.
- Operations & Maintenance: online rate, abnormal traffic, silent SIMs, and alert closure in ITSM.
- Compliance: log desensitization, retention period, and cross-border/subcontracting agreements.
How reefer condition and the container number stay bound
From the container side, reefer telemetry puts setpoint, return air, supply air, alarm codes, and fuel or shore-power state into one traceable record with that box’s number. The IoT SIM sits on the reefer controller or an external logger. The box moves among yard, road, rail, and port, and the network switches repeatedly. Position may be interrupted. The temperature curve should not break without a reason. A reefer alarm has to say which compressor or which power state, not only “communications restored.” The container number, the reefer serial number, and the SIM identity are three different identifiers. A reefer change or a SIM change must be handed over, or the cargo owner sees another box’s temperature.
The box has to keep unsent data in a metal yard and at the edge of a ship’s hold, then catch up on the original timestamp after it lands or leaves a tunnel. A setpoint change, a door opening, and a switch from the diesel generator to terminal power should each be an event. They should not appear only as a jump in the temperature number. Roaming and the access point must cover the networks the voyage or the road actually crosses, and the segments that are expected to have no coverage should be known in advance, so a lack of signal at sea is not treated as a device fault. The cellular module may restart when power switches. Write the last operating state locally before that restart. If several boxes are aggregated through a vehicle gateway, each record still carries the container number, not only the vehicle plate. The shipping line, the fleet, and the cargo owner may all receive alarms, with different field rights. Do not send every controller parameter to everyone by default.
A common error is to let the first temperature packet after the yard stand for the whole voyage. An excursion in the middle was discarded and the platform still shows normal throughout. Another is a wrong container number: the curve is perfect and attached to an empty, while the loaded box has no data. Treating the reefer’s communications heartbeat as proof that refrigeration is running is a third. The controller is online and the compressor has stopped for lack of oil or a wrong power mode. Crane and slot shadowing in a yard causes periodic offline. If the rule is “offline means cargo damage,” the result is a mass of false alarms. If there is no alarm at all, a real reefer stop is explained away as shadowing. Acceptance should follow one box across at least two networks and check that a setpoint change, a power switch, and the catch-up timestamp still point at that container number. The temperature criterion is described under temperature deviation. How in-transit information is seen upstream and downstream is described under supply chain visibility.
When the reefer, the logger, or the SIM changes, write the container number, the setpoint, and the last successful operating state at the handover moment. The new device continues from that record. It does not bring in the old box’s history, and it does not start blank while claiming the voyage is continuous. Expected lack of coverage at sea or in a tunnel belongs in the route note. No message in that interval is a planned gap. Only an unplanned gap alarms. A switch from diesel to terminal power has to be visible on its own, because many temperature swings come from the switch and not from the cargo. Keep the controller’s alarm code in its original form. Do not translate it only to “abnormal,” or the shore side cannot tell oil, a sensor, and an open door apart. When several cargo owners share a platform, authorize by container number. A SIM that belongs to the fleet must not display parameters of the other boxes on the same vehicle. Long shadowing in a yard may allow delayed catch-up, but after catch-up finishes the excursion has to be recalculated. Do not drop it because the box was “offline too long to calculate.”
Use the time the box enters and leaves the yard to cut that segment of the curve. Do not join the tail of the previous voyage to the head of this one. If the controller address changes and the container number does not, treat it as a controller replacement and break the old and new curves at that point. If fuel level or shore-power state stays unchanged for a long time while temperature leaves the setpoint, suspect a stalled operating message before suspecting the cargo. A brief offline is allowed when the SIM changes operator in port. If the offline exceeds the plan, alarm. Set the plan from the port, not from road experience. The cargo owner may see fewer fields than the shipping line, but the container number, the setpoint, and the excursion interval cannot be missing, or there is no shared object to coordinate on. After catch-up, still notify the excursion. Do not treat it as already told because the box was offline at the time. The notice should at least include the carrier responsible then.