OCPI 2.2.1
Compare this step across versionsThe parties in an OCPI exchange: the Charge Point Operator, the eMobility Service Provider and the roaming hub between them.
0 / 6 completed
Each OCPI message has a sender and a receiver. These are the parties you will meet in them:
Charge Point Operator (CPO)
Operates a network of Charge Points.
eMobility Service Provider (eMSP)
Gives EV drivers access to charging services.
Roaming hub
Connects CPOs and eMSPs through a roaming platform.
Charge Point Operators operate charging networkseMSPs give drivers access to charging servicesA roaming hub connects participating platforms
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.