What changes in OCPI 2.2.1
Modules in OCPI 2.2.1
Sessions
CDRs
Locations
Tariffs
Tokens
Commands
Credentials
Versions
Hub Client Info
Charging Profiles
Payments · extension
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.
Start by identifying the platform sending a message and the platform receiving it. The same company can play more than one role.
Which platforms use OCPI?
- Charging Point Operator (CPO)
- Operates a network of Charge Points.
- e-Mobility Service Provider (eMSP)
- Gives EV drivers access to charging services.
Source
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
OCPI supports roaming between participating CPO and eMSP networks. A provider's card or app works where those networks support it.