OCPI 2.2.1
Compare this step across versionsOCPI connects charging platforms. Start here to see which platforms use it and how it supports EV roaming between their networks.
Sources for OCPI roaming
"The Open Charge Point Interface (OCPI) enables a scalable, automated EV roaming setup between Charge Point Operators and e-Mobility Service Providers."OCPI 2.1.1 specification · #introduction-and-background"The Open Charge Point Interface (OCPI) enables a scalable, automated EV roaming setup between Charge Point Operators and e-Mobility Service Providers."OCPI 2.2.1 and 2.3.0 specification · #introduction_introduction_and_background
0 / 6 completed
OCPI, the Open Charge Point Interface, connects charging platforms. Start by identifying the party sending a message and the party receiving it.
Two roles do most of the talking:
- Charge Point Operator (CPO)
- Operates a network of Charge Points.
- eMobility Service Provider (eMSP)
- Gives EV drivers access to charging services.
Sources for CPO and eMSP roles
"|CPO |Charging Point Operator. Operates a network of Charge Points. |eMSP |e-Mobility Service Provider. Gives EV drivers access to charging services. |Hub |Can connect one or more CPOs to one or more eMSPs. |NAP |National Access Point. Provides a national database with all (public) charging locations. Information can be sent and retrieved from the NAP. This makes it different from a typical NSP. |NSP |Navigation Service Provider. Provides EV drivers with location information of Charge Points. Usually only interested in Location information. |Roaming Hub |See: Hub. |SCSP |Smart Charging Service Provider. Provides Smart Charging service to other parties. Might use a lot of different inputs to calculate Smart Charging Profiles."OCPI 2.2.1 specification · #terminology_roles"|CPO |Charging Point Operator. Operates a network of Charge Points. |eMSP |e-Mobility Service Provider. Gives EV drivers access to charging services. |NAP |National Access Point. Provides a national database with all (public) charging locations. Information can be sent and retrieved from the NAP. This makes it different from a typical NSP. |NSP |Navigation Service Provider. Provides EV drivers with location information of Charge Points. Usually only interested in Location information. |Roaming Hub |A business that facilitates roaming by offering integration with multiple roaming partners through one technical connection. |SCSP |Smart Charging Service Provider. Provides Smart Charging service to other parties. Might use a lot of different inputs to calculate Smart Charging Profiles. |PTP |Payment Terminal Provider. Refers to the party operating the payment terminal management system. This can be the terminal vendor (re/seller) and manufacturer |PSP |Payment Service Provider. Refers to the party providing acquiring services, which is typically a bank or institution that accepts and processes electronic payments. Merchant can enter into a direct contract with an acquirer or use the services of an intermediary (a payment service provider)"OCPI 2.3.0 specification · #terminology_roles
OCPI supports roaming between participating CPO and eMSP networks. A provider's card or app works where those networks support it.
Every message has a sender and a receiverA CPO operates charge pointsAn eMSP gives drivers access to charging
What OCPI 2.2.1 defines for this lesson
Modules in this version
Locations
Sessions
CDRs
Tariffs
Tokens
Commands
Credentials
Hub Client Info
Charging Profiles
Payments
Bookings
Advertised sender and receiver interfaces
An endpoint declares how another platform can pull or push data. Credentials uses the same interface for both roles.
The header token is encoded
The request header carries an encoded token; the Credentials body still carries the raw token.
Billing records name the Token owner
A charge record names the country and company that own the driver's Token.