Definition
CAN Gateway Cellular Uplink refers to the process in which signals on in-vehicle CAN/CAN-FD buses are converted into structured telemetry by embedded parsing modules in the vehicle gateway or T-Box and then uploaded to the cloud platform or fleet backend via cellular IoT SIM cards. Unlike real-time CAN logging used for workshop debugging, mass production connected vehicles must preserve signals valuable for safety and maintenance under limited bandwidth while suppressing traffic avalanches caused by redundant frames. Gateways typically handle DBC parsing, signal unit conversion, invalid value filtering, and rule-based aggregation (e.g., engine speed uploaded as a histogram by range rather than millisecond by millisecond).
Sampling strategy is an engineering convention about 'when to sample, how densely to sample, and how much to transmit': it can be divided into periodic sampling (e.g., reporting SOC and mileage every 30 seconds), rate-of-change triggered (e.g., reporting more frequently when coolant temperature slope exceeds threshold), event-driven (e.g., forming batch uploads from buffers before and after airbag deployment), and on-demand pull (e.g., temporary deep diagnostic tasks issued by operations). The strategy needs to be coordinated with IoT SIM cards' data plans, base station handover hysteresis, and in-vehicle storage capacity to avoid extreme cases of 'too fine a strategy—bill spikes' or 'too coarse a strategy—faults missed'.
Technical Features
On the cellular side, it is recommended to bind CAN summary traffic to a dedicated APN or QoS level, decoupling it from high-definition maps or video-heavy traffic. Gateway firmware should support OTA updates of DBC and sampling tables to adapt to year-model differences without replacing SIM cards. Data compression can use differential encoding, dictionary-based signal IDs, or binary serialization like protobuf, significantly reducing byte count at the same information density. For security, countermeasures against forged frame injection are necessary: gateways and the cloud should establish mutual authentication, and critical commands (such as remote vehicle locking) should use separate channels with high-privilege auditing.
Operations monitoring should track 'average daily CAN uplink bytes per vehicle,' 'abnormal ID storms,' and 'retransmission queue depth,' and correlate with SIM online rates to distinguish whether issues are due to network problems or vehicle-side flashing errors. SimtoLink IoT SIM cards provide per-application usage statistics interfaces, facilitating the allocation of CAN channel costs to specific vehicle models or software versions.
Use Cases
Applicable to remote health assessment of new energy battery packs, fault warning for AMT and retarders in commercial vehicles, and detection of illegal modifications in shared cars (comparing CAN with declared configuration). When implemented, it is recommended that the OEM and TSP jointly develop a signal whitelist, perform shadow mode comparisons on the actual vehicle bus load first, and then fully enable cellular backhaul. SimtoLink can work with dedicated networks and card policies to ensure the predictability of CAN data transmission and billing.
Key points for cooperation with IoT SIM cards
It is recommended to configure a small-traffic, long-connection-friendly data plan specifically for CAN summaries, and to disable unnecessary MMS and voice channels to reduce the attack surface; gateway firmware versions and card PROFILE versions should be bidirectionally associated in the asset database to facilitate vehicle issue tracing. For high-value commercial fleets, a fixed source address can be bound on the cellular side, corresponding one-to-one with the cloud platform firewall policy. Nighttime batch deep diagnostic tasks should be scheduled off-peak and avoid overlapping with base station congestion periods to prevent competition for air interface resources with the commuting peak.