Keeping EV Chargers Online
💡 M2M SIM Card And Charger Connectivity: Key Highlights
- A 60 kW DC charger at 10% utilisation grosses roughly ₹2,600–₹3,500 a day. Two days offline plus one site visit costs more than three years of the connectivity that would have prevented it.
- OCPP 1.6J authorises and meters offline, but the central system owns the transaction ID — so an offline session carries a temporary ID and must be replayed in order. OCPP 2.0.1 moves ID generation to the charging station and stamps every
TransactionEventwith a sequence number and anofflineflag. AllowOfflineTxForUnknownIdis the setting that quietly gives energy away — one unbilled 30 kWh session at ₹20/kWh is ₹600 delivered and uninvoiceable.- Budget about 100 MB per charger per month. Telemetry runs 15–25 MB at 60-second metering; a single 5–20 MB firmware image is the spike that breaks a 50 MB plan.
- In India an M2M SIM card is issued in bulk to the organisation, not to a person, under DoT’s 2018 restrictive-features instruction — and TRAI’s March 2024 recommendation would give an imported charger’s foreign eSIM profile six months before it must carry an Indian operator’s profile.
India had 29,151 public EV charging stations installed as of December 2025 — 8,805 fast, 20,346 slow — per figures the Ministry of Heavy Industries tabled in the Lok Sabha. Nobody publishes how many a backend can reach right now, and for a charge point operator that is the number that decides revenue: a charger the platform cannot see cannot authorise a driver, push a session into billing, or be reset without a van. The cheapest item in the cabinet — an M2M SIM card — decides whether the other ₹8–15 lakh of hardware earns anything.
This is for CPO operations and engineering leads — whoever gets the “charger showing offline” ticket at 9 p.m. — and for fuel retailers and enterprise site hosts whose forecourt or campus internet the chargers are quietly borrowing. The CPO owns the uptime obligation but not the pipe; the host owns the pipe and no reason to care when it changes.
We have covered the layers above this one — EV charger remote monitoring, multi-vendor charger estates and telling drivers about downtime. This post is the layer underneath all three: the physical and contractual link between a charger and its backend, and what happens in the seconds, hours and invoices after it drops.
What An Offline EV Charger Actually Costs
Start with the arithmetic. It is the only thing that justifies spending money on a link nobody sees.
The energy you never sell
A 60 kW DC charger at 10% utilisation delivers about 144 kWh a day (60 kW × 24 h × 0.10). At an Indian public DC tariff of ₹18–₹24 per kWh, that is ₹2,600–₹3,500 of gross revenue a day from one bay. Two days offline before anyone notices — ordinary when the first alarm is a driver complaint — is ₹5,000–₹7,000 gone, against a connectivity line of about ₹100 a month.
The sessions you cannot invoice
Offline does not always mean idle. A charger configured to keep serving while disconnected meters locally and queues the result, but nothing reaches billing until it reconnects — and if that queue is lost to a power cycle, a full buffer or a crash mid-outage, the energy is gone. One 30 kWh session at ₹20 per kWh is ₹600 delivered and uninvoiceable.
The truck roll
An offline charger cannot take a remote reset, which is exactly what clears most soft faults. A site visit 60 km out is a technician’s half day plus travel — ₹1,500–₹3,000 in India — for a power cycle that costs nothing when the link is up.
The driver who does not come back
The last cost never appears in a P&L. When Rempel and colleagues physically tested all 655 open public CCS fast-charging ports across nine San Francisco Bay Area counties, only 73.3% were functional — network failures sitting alongside payment failures, blank screens and failed charge initiation. A driver who arrives at a dead charger does not file a ticket; they delete the site from their route, and the utilisation assumption under your business case degrades one driver at a time.
What OCPP Does When The Link Drops — 1.6J vs 2.0.1
OCPP softens each of those costs, and the settings that do it are operator choices, not vendor defaults. In OCPP 1.6J, five configuration keys govern offline authorisation: LocalAuthListEnabled with SendLocalList pushes accepted identifiers to the charge point; AuthorizationCacheEnabled lets it remember tokens already authorised online; LocalAuthorizeOffline starts transactions for locally known identifiers while disconnected; LocalPreAuthorize does the same while online, to cut the wait; and AllowOfflineTxForUnknownId accepts a token it has never seen. Identifiers on the local list with a status other than Accepted, and expired ones, must still be refused — offline is not an amnesty.
AllowOfflineTxForUnknownId maximises availability, and is simultaneously a decision to hand free energy to anyone holding any RFID card. On a paid public network, leave it off and maintain a real local authorisation list. On a captive fleet or employee depot, where every card in circulation is already yours, switching it on is usually right.
While disconnected, a 1.6J charge point must queue its transaction messages — StartTransaction, StopTransaction, MeterValues — and replay them in order on reconnect, with TransactionMessageAttempts and TransactionMessageRetryInterval governing retries. The awkward part: in 1.6 the central system generates the transaction ID, so an offline session carries a temporary one until its queued StartTransaction is acknowledged. That is why replay order matters, and why the Open Charge Alliance’s own errata sheet had to clarify the surrounding behaviour.
OCPP 2.0.1 removes the problem rather than papering over it. StartTransaction, StopTransaction and the transaction-related MeterValues and StatusNotification messages are replaced by a single TransactionEvent message; generating the transaction ID moves to the charging station; every event carries a sequence number so the CSMS can reconstruct order and detect gaps; and the chronological-order requirement is lifted. In operator terms, a 2.0.1 estate can lose its link mid-session and still hand the backend a complete, auditable transaction; a 1.6J estate manages that only if its queue survives intact. Worth knowing before a hardware order is signed — and why OCPP-compliant charging software has to speak both dialects.
M2M SIM Card, Broadband Or Wi-Fi: The Options Compared
Five realistic ways exist to get a charger onto the internet. The figures below are Indian budgeting bands for 2026, not quotes.
| Option | Indicative cost / charger / month | Where it fails | Use it when |
|---|---|---|---|
| Multi-operator (roaming) M2M SIM card | ₹150–₹400 | Still one antenna and one modem; a coverage hole hurts every operator equally | Revenue-critical public sites, highway corridors, anywhere a single network is patchy |
| Single-network M2M SIM | ₹50–₹150 | One operator’s outage, tower maintenance or congestion is your outage | Dense urban sites with a verified strong signal and low revenue per bay |
| Host’s wired broadband | ₹0 marginal (host pays) | Router swaps, ISP changes and firewall rules you are never told about | Campuses and malls where the link can be written into the site agreement |
| Host Wi-Fi | ₹0 marginal | Captive portals, password rotations, VLAN changes, guest-network timeouts | Almost never for revenue-earning bays; acceptable for home or small workplace units |
| Wired Ethernet from a site gateway | ₹8,000–₹25,000 router capex + one shared SIM plan + ₹1,500–₹4,000 cabling per bay | The gateway becomes a single point of failure for the whole site | Hubs of 4+ chargers, depots, and any site already being trenched |
Then size the data. A 300-second heartbeat is 288 round trips a day at well under a kilobyte — 3–4 MB a month. MeterValues every 60 seconds across five hours of charging adds ~300 messages a day at 1–2 KB, or 13–18 MB. With status notifications, authorisations and a TLS handshake per reconnect, a busy charger sits at 15–25 MB a month; 15-second metering quadruples it; one firmware campaign pulls a 5–20 MB image down the same link. Budget 100 MB per charger per month.
India: M2M SIM Card Rules, KYC And Who Holds The Connection
Machine connections in India sit under a separate regime from consumer SIMs. Under DoT’s instructions of 16 May 2018, connections used solely for M2M are issued in the name of the entity providing the M2M service under the bulk-connection procedure, with restrictive features compared to ordinary SIMs; India also allocates a dedicated 13-digit M2M numbering series. For a CPO: the connection belongs to the company, not a site engineer’s personal account, and cannot be swapped for a retail SIM bought at a kiosk during a rushed commissioning.
Above that sits DoT’s Guidelines for Registration of M2M Service Providers (M2MSP), dated 8 February 2022 and administered through the Saral Sanchar portal. They cover entities providing M2M services over telecom resources obtained from licensed operators, and on a plain reading reach captive deployments too — take a view with counsel. The mirror-image question is who holds the connection when the host provides it: the CPO carries an uptime obligation on a link it has no right to, and when a tenancy ends or an IT team re-segments the network the estate goes dark with no notice. Write the link into the site agreement with a named contact and a change-notification clause, or fit your own M2M SIM card.
The third item matters most when importing hardware. TRAI’s recommendations on the Usage of Embedded SIM for M2M Communications (21 March 2024) propose that every profile on an M2M eSIM in an imported device on international roaming in India be converted to an Indian operator’s profile within six months of roaming activation, or on change of ownership, whichever is earlier — tightening the three-year window TRAI recommended in 2017. These are recommendations to DoT rather than an operative rule, so confirm the enforceable position before relying on it. The planning assumption is not in doubt: a charger arriving with a foreign eSIM profile already active is not a connectivity strategy.
Designing A Site That Stays Online
Survey the signal before commissioning, not after
The commonest design failure is checking coverage on a phone in the forecourt, then bolting the modem into a steel enclosure at ankle height behind a locked door. Measure at the real antenna position, in the real cabinet, door shut. RSRP better than −100 dBm with SINR above 5 dB is comfortable; −110 dBm or worse means budgeting an external antenna or a wired path now, not a return visit later.
Two paths where the revenue is
Redundancy should follow revenue. On a highway hub earning ₹10,000–₹20,000 a day, a second independent path — dual-SIM across two operators, or cellular backed by host broadband — pays for itself in one avoided outage. On a workplace AC bay doing four sessions a week, it does not. A multi-operator M2M SIM card is the middle option.
Alert on flapping, not only on dead
A link that drops forty times a day and recovers in thirty seconds reports 99%+ connected minutes on a monthly uptime summary while wrecking session reliability, because each drop lands somewhere in an authorisation or a meter stream. Alert on reconnections per hour, not only on “offline for more than X minutes”, and pair it with a modem watchdog inhibited while a transaction is running. Remote charging management software should set those thresholds per site, not apply one rule to a basement and a highway plaza alike.
Stage firmware over the link you actually have
A half-downloaded image on a flapping link is how a connectivity problem becomes a bricked charger. Roll out 5% canary, then 25%, then the rest, and hold back any charger whose link is already marginal.
The link is also your attack surface
Every choice above is also a security decision. Keep charger traffic outbound-only over TLS, put chargers on their own VLAN or a private APN rather than the host’s flat corporate network, and verify certificates at both ends — the full treatment is in IEC 62443 for EV charging. None of this is exotic: a signal survey, a sensible SIM contract, a few OCPP keys chosen deliberately, and alerts that match how links really fail — all visible in a charging management system like YoCharge.
Frequently Asked Questions
Connectivity, M2M SIM cards and offline behaviour — the questions operators ask most.
Sources: Open Charge Alliance — What is new in OCPP 2.0.1 | TRAI — Recommendations on Usage of Embedded SIM for M2M Communications (21.03.2024) | DoT — Registration Process of M2M Service Providers (M2MSP) | PIB / Ministry of Heavy Industries — Electric Vehicle Charging Stations, Lok Sabha reply | Rempel et al. — Reliability of Open Public Electric Vehicle Direct Current Fast Chargers
Know Which Chargers Are Reachable — Before A Driver Tells You
Connection health per charger, reconnect counts that expose a flapping link, queued-session recovery and staged firmware rollouts across mixed OCPP 1.6J and 2.0.1 hardware. YoCharge gives CPOs and fuel retailers that view across the whole network.
Talk to Sales