Definition
EV Charging Station (EV Charger / EV Charging Station) is specialized equipment that provides electric power to electric vehicles, including two types: AC slow charging and DC fast charging. The EV charging station communicates with the vehicle BMS via the CAN bus to complete the charging handshake and power negotiation, connects to the charging platform via 4G/5G IoT SIM cards, and realizes remote monitoring, billing, fault reporting, and firmware upgrades. It is a core component of charging stations.
EV charging stations must comply with national standards GB/T, European standard IEC 61851, and American standard SAE J1772, support the OCPP protocol and interface with charging operation platforms, and, for cross-border deployment, must support local certification and one card multi-country connectivity.
Technical Features and Architecture
The EV charging station technical architecture includes: Power Module — AC/DC conversion, power ratings (7kW/60kW/120kW/350kW, etc.); Control Unit — main MCU, CAN communication with vehicle BMS, safety inspections (insulation, leakage); Communication Module — built-in IoT SIM cards, communication with the platform via MQTT/OCPP, reporting device status and charging data collection; Human-Machine Interaction — display screen, scan/ swipe payment, QR code. DC fast EV charging stations also require liquid-cooled cables, multi-gun coordination, etc.
In the charging management system, EV charging stations, as edge devices, transmit data such as charging sessions, electricity consumption, and faults back to the Device Management Platform , supporting operational and maintenance decisions.
Application in IoT and cross-border scenarios
The applications of EV charging stations in IoT and cross-border scenarios include: Urban Charging Network — large-scale deployment in public charging stations, residential communities, shopping malls, and other scenarios; Cross-border Charging — European, Southeast Asian, and other cross-border self-driving and logistics EV charging abroad, where EV charging stations require local certification and stable network connectivity; Dedicated Scenarios — dedicated charging stations for buses, logistics, taxis, etc. SimtoLink provides IoT connectivity for EV charging stations across 200+ countries, supporting data pool sharing and multi-country single-card use, ensuring stable operation of cross-border EV charging stations.
The vehicle handshake and the platform session are two conversations
An EV charging station is the device installed on site that exchanges charging permission and energy directly with the vehicle. Its conversation with the vehicle uses control pilot, or the matching vehicle-side communication, to confirm that the connector is inserted, what current is allowed, and whether power may be applied. Its conversation with the platform uses cellular or the site network, to collect authorization, report the session, and receive start and stop. Both conversations have to succeed for one complete charge. If only the vehicle handshake finishes, the vehicle can charge and the platform has no order. If only the platform session finishes, the order exists and there is no current at the connector. The vehicle-side messages of an AC charger and a DC charger differ. A joint-test record from one kind of charger cannot be applied to the other. In a cross-border deployment, the plug, the voltage, and the interface approved locally must match the destination, and the protocol version must match the version agreed with the platform.
Conditions of use run from installation through offline operation. Protective earth, cable capacity, and the connector rating follow the circuit on site, not the maximum printed on the nameplate. The platform address, the charge-point identity, and the meter clock have to be written at commissioning. When the network drops, whether the charger may continue on a locally cached authorization must be decided in advance, and the energy from that stretch must be catchable after recovery. The sample time of metering has to be comparable with the start and end of the platform session. Firmware and tariff delivery should avoid a vehicle session that is in progress. The network the IoT SIM is on must be able to reach the platform address. A test that passes in the warehouse on a domestic access point does not mean the roaming egress in the destination country can resolve that address. Local protections, such as the connector lock, insulation detection, and door-open detection, take priority over any remote start command.
Getting online in the warehouse is treated as proof the connector works
A likely mistake is to verify only that the module can open a web page, and not the vehicle handshake or registration with the platform. After the device goes abroad the platform address is unreachable, or the plug standard is wrong. Charging is impossible on site, and the remote view still shows the SIM online. Another mistake is an AC charger and a DC charger using the same start message, so one side ignores the vehicle's permission signal. Another is a meter clock a few minutes off the platform. The energy of a short session is counted into the next order, or dropped. After a SIM change, if the charge-point identity is not kept, the platform treats this as a new charger, and every locally cached authorization from before is void.
When the offline policy is not written down, the charger may keep delivering power with no authorization, or refuse to deliver power when authorization exists. Neither has anything to do with the SIM still being online. Split an investigation into three parts: whether the vehicle allowed it, whether the charger reported the session to the platform, and whether the platform returned an authorization. Do not reduce a failure in any one part to a signal-bar count. When an order has to stay uninterrupted, see next whether the backup link can catch up the unfinished session after the primary path drops. Whether that catch-up was confirmed is whether the ACK returned by the platform matches that session number.
Vehicle permission, platform authorization, and contactor state should be lined up in the local log under one session number. If the three timestamps differ by too much, stop delivering power rather than keep waiting for the network. The platform address for the destination should be written per site in the shipment configuration. Do not depend on automatic discovery at first power-up. Discovery often points at the test entry of the warehouse country. The deviation allowed between metering and the session start and end has to be set in advance. Beyond that deviation, mark the record for checking and do not settle it automatically. A cached offline authorization needs a count and an expiry. After it expires, power must not continue even if the network has not returned.