Definition
Charging Management refers to the full lifecycle management of electric vehicle charging stations and EV charging stations, including operation, billing, scheduling, and maintenance. It covers remote monitoring of EV charging stations, fault alarms, firmware upgrades, order and billing settlement, integration with interconnection protocols such as OCPI, as well as load control and orderly charging targeting the demand side.
Charging management is the core capability of charging platforms and charging operation platforms, supporting large-scale operation by operators, cross-platform charging for users, and cross-border charging interconnectivity.
Technical Features and Architecture
Typical architecture of charging management includes: Device Layer — EV charging stations connect to the platform via 4G/5G IoT SIM cards, reporting device status and charging data; Platform Layer — Device Management Platform is responsible for device registration, remote control, data collection ; Business Layer — Orders, billing, user accounts, interoperability (OCPI/OCPP); Scheduling Layer — Connects with the power grid and scheduling platform to achieve orderly charging and demand response. Data flow includes real-time status, charging sessions, billing records, etc., and must meet security and privacy compliance.
In cross-border charging management, it is necessary to support multi-currency, multi-language, and multi-operator settlements, as well as one card for multiple countries IoT connectivity to ensure stable network connection of EV charging stations abroad.
Application in IoT and cross-border scenarios
Applications of charging management in IoT and cross-border scenarios include: Domestic charging networks — Operators manage thousands to tens of thousands of EV charging stations via the platform, achieving centralized monitoring, remote operations and maintenance, and unified billing; Cross-border charging — Cross-border self-driving and logistics EVs in Central Europe, Southeast Asia, etc., need to charge abroad, and the charging management platform needs to connect with local operators and support cross-border payments; Orderly charging and V2G — Combined with grid demand-side management to achieve peak-valley regulation and vehicle-grid interaction. SimtoLink provides IoT connectivity for EV charging stations covering over 200 countries, supporting stable operation of the charging management platform in cross-border scenarios.
The session, the tariff, and the load limit are three separate states
Charging management is the operating method that strings one charge from authorization, through start and metering, to the end and settlement, while also holding the site's electrical limit. It is not the name of a particular server. A charge that can be managed has at least three independent states: whether the connector is really charging, which tariff applies now, and how much power the site or the circuit still has left to allocate. The three states come from different places. Connector state comes from the charger's measurement. The tariff comes from the billing rule of the site in that period. The power limit comes from the distribution circuit. At an international site, the tariff also has to carry the currency and how tax is handled, and the limit has to carry the local circuit, not a default from headquarters. Looking only at an order "in progress," and not seeing these three states, is not managing the charge.
In use, before authorization, know that the connector is idle, that the tariff is already in effect, and that the power remaining is enough for this start. After a remote start is sent, wait until the charger reports that the session has begun. Do not treat a successful click on the platform as current already flowing. Metered values should carry a sample time, and the energy difference at the end must be reconcilable with the start and end of the session. A firmware upgrade, a restart, and a price change must not fall in the middle of a session that has started and not ended, or the metering curve breaks. Clocks at a cross-border site must be unified, or a night tariff takes effect on the wrong local hour. If load dispatch lowers the power of one circuit, it must act on the sessions on that circuit, not stop every connector on the site. When the IoT connection drops, the charger should be able to end or limit power by the last rule already delivered locally, and catch that session up after the connection returns.
The remote start succeeded, but there is no current
A likely mistake is to treat the start command on the platform as the session. The command reaches the gateway when the connector is not properly inserted, or the vehicle has not allowed charging. The platform still shows a session created, and billing has no energy. Another mistake is one limit shared by the whole site. A fault on one connector reduces the power available to the others to zero. Another is a tariff that switches on headquarters time. Peak and off-peak are reversed at the site abroad, and the settlement statement does not match what is posted on site. A roaming vehicle that used another billing identifier can charge, and the settlement record has no roaming mark to match, so that energy has nowhere to go in reconciliation.
An upgrade window overlapping the charging peak restarts the charger in the middle of a session. Energy is recorded only up to the restart, and after the end the platform settles at zero energy or estimates the whole stretch. Check the command, the session the charger reported, and the metering curve separately. If any one is missing, do not reconstruct the order. Local records from a connection outage must be catchable, and the catch-up format must match the live record. Measurement on the charger itself is the metering of the EV charging station. The path the catch-up takes is data backhaul. In management, one of those records cannot stand in for the other.
A price change and a limit change both have to declare the moment they take effect. A session already started keeps the tariff from when it started and the power allocated then. The new rule applies only to sessions after that. Energy that is reported late must be marked as caught up. Settlement uses the closed energy after the catch-up. Do not treat a zero curve during the outage as real consumption. When a circuit limit changes, record which sessions it acted on and how much each session was reduced, so it is possible later to explain why current on one connector fell. A rule kept locally at a cross-border site needs a version number. After the connection returns, compare versions first, then decide whether to overwrite.