Definition
Charging operation platform(Charging Operation Platform) is the core software system used by EV charging station operators to manage Charging Station, EV Charging Station Assets, handle user charging orders, billing and settlement, operation and maintenance scheduling, and interoperability. Compared with general Charging Platform, a charging operation platform focuses more on operator-side business operations, including device access,Charging Management, revenue analysis, and interfacing with protocols such as OCPI .
The Charging Operation Platform supports operators in deploying charging networks locally or across regions, provides services for B2C users, B2B corporate clients, and Roaming interconnection with other operators, making it key infrastructure for cross-border charging network implementation.
Technical Features and Architecture
Typical architecture of a charging operation platform includes:Device access layer—— Connects to charging stations via protocols like OCPP and MQTT, with charging stations equipped with built-in IoT SIM cards for remote communication;Business Core Layer—— Order management, billing engine, user accounts, coupons, and marketing;Interconnection Layer—— Data exchange with CPOs (Charge Point Operators) and eMSPs (Electric Mobility Service Providers) implemented via OCPI/OCPP;Data Analysis Layer—— Operational reports, device utilization, and fault statistics. The platform must support high concurrency, multi-tenancy, and multi-region deployment.
In cross-border scenarios, the charging operation platform must support multi-currency settlement, multilingual interfaces, local payment methods, and One SIM for Multiple Countries IoT connectivity ensures stable network connection and data transmission for overseas charging stations.
Application in IoT and cross-border scenarios
The application of the charging operation platform in IoT and cross-border scenarios includes: Domestic large-scale operation — Operators manage thousands of charging stations, achieving centralized monitoring, remote fault handling, and user services through the platform; Cross-border Roaming — Users charge in Country B using accounts from the operator in Country A, achieving cross-platform authentication and settlement through OCPI; Enterprise fleet management — Providing dedicated charging and billing solutions for logistics, taxi, and other enterprises. SimtoLink provides IoT connectivity to charging stations covering over 200 countries, supporting the reliable operation of charging platforms in cross-border scenarios.
The operator side uses charge-point identity as the key
A charging operation platform is the system a charge-point operator uses to register assets, accept sessions, issue settlement records, and connect to outside e-mobility service providers. Its key should be the stable identity of the charge point and the connector, not the charger's current network address. After the SIM attaches again, the address changes. The identity should not. Every session on the platform must be traceable to which connector, which authorization identifier, which period, and how much energy. When location, tariff, and settlement records are exchanged with an outside service provider, the party identifiers and object identifiers the two sides agreed are what get used. An internal database auto-increment must not be handed out as the external identity. In cross-border operation, one platform can manage sites in several countries, but currency, tax handling, language, and the settlement party have to be configured separately for the country where the site sits.
Conditions of use include master data before business. A charge point is registered and brought online for the first time before its location is published. A tariff takes effect before a session. An authorization identifier must be recognized by the visited site, whether it comes from a user of this platform or from a roaming partner. The clock must be reliable, or the other party will not accept the start and end times on a settlement record. The IoT connection is responsible only for delivering the charger's messages to the platform. The platform is responsible for whether those messages make a valid session. After a SIM or a communications module is replaced, keep the charge-point identity and update only the communications parameters. When several tenants share a platform, one operator's tariffs and users must not be readable by another operator's site. A test of the external roaming interface must use the party identifier of the target country. Do not declare cross-border use ready from a domestic sandbox identity alone.
After a SIM swap, the charger is registered again as a new unit
A likely mistake is to create a new charge point automatically whenever the communications address changes. The old point becomes permanently offline. The new point has no tariff and no roaming publication. The connector on site is still charging, and the platform has two incomplete assets. Another mistake is to treat the operation platform as the back office of the driver application, and to register chargers in the driver account system, so a session belongs to the wrong party. Another is to settle from an estimated energy at the start of the session and refuse metering corrections after the end. Roaming reconciliation is then permanently short. If tax handling for the country of the site was never configured, the other party rejects the settlement record, and the platform still shows the session as successful.
A first commissioning done only in the warehouse, with the wrong access-point name after the unit goes abroad, means the charger has never registered with that platform, while the point on the map is already published. Look up the most recent commissioning by charge-point identity first, then see whether the address change is from the same communications-module replacement. The session record, the settlement record, and the published location must agree. Whether the link reached the platform is checked with data backhaul. Whether the service should stay on the original charger when the address changes is checked against the switch record of the backup link. Do not write a switch as a new asset coming online.
Before a location is published externally, check the connector count, the socket standard, and the tariff currency. If any of the three disagrees with the site, do not publish yet. When a roaming partner rejects a settlement record, keep the missing field they pointed out. Common ones are the session reference, the currency, or the end time, rather than only a line that says the exchange failed. A work order that replaces a communications module must fill in the original charge-point identity. If the identity is empty, creating a new point is not allowed. Reports for sites in different countries handle tax by the country of the site. Do not add different currencies together and call the sum one revenue figure.