OCPI key terminologies

By Abhishek Uniyal · Updated

This OCPI glossary explains the parties, objects and interfaces used in roaming exchanges. Read a definition and its source, then see OCPI explained and OCPI charging session lifecycle for the terms in use.

Protocol basics

  • OCPI

    Open Charge Point Interface. It connects charging platforms, so a CPO and an eMSP can exchange locations, tariffs, sessions and charge records.

    Source
    "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 specification · #introduction_introduction_and_background
    See it in the lesson
  • Module

    One part of OCPI for one kind of data, such as Locations or Sessions. Two platforms exchange which modules each implements and at which URL. OCPI 2.2 and later also advertise an interface role; a 2.1.1 Endpoint has no role field.

    Source
    "Via the version details, the parties can exchange which modules are implemented for a specific version of OCPI, which interface role is implemented, and what the endpoint URL is for this interface."OCPI 2.2.1 Version information endpoint chapter · #version_information_endpoint_version_details_endpoint
    Browse the modules

Parties and roles

A company can provide both CPO and eMSP services. Market roles and the Role values sent on the wire are separate ideas. OCPI 2.2.1 core Role values: CPO, EMSP, HUB, NAP, NSP, OTHER, SCSP.

  • CPO

    Charging Point Operator. Operates a network of Charge Points.

    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
    See it in the lesson
  • eMSP

    e-Mobility Service Provider. 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
    See it in the lesson
  • Hub

    Connects CPOs and eMSPs.

    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
    See it in the lesson
  • Party ID

    The ID of a CPO, eMSP or other party, following the ISO-15118 standard. With a country code, it names the party in URLs and objects.

    Source
    role · Role · cardinality 1: Type of role. business_details · BusinessDetails · cardinality 1: Details of this party. party_id · CiString(3) · cardinality 1: CPO, eMSP (or other role) ID of this party (following the ISO-15118 standard). country_code · CiString(2) · cardinality 1: ISO-3166 alpha-2 country code of the country this party is operating in.OCPI 2.2.1 Credentials chapter · #credentials_credentials_role_class
    See it in the Explorer

Objects

  • Session

    The object that describes one charging session. The CPO sends it to the eMSP and updates it while the charge runs.

    Source
    "The Session object describes one charging session."OCPI 2.2.1 Sessions module · #mod_sessions_sessions_module
    See it in the lesson
  • CDR

    Charge Detail Record. The description of a concluded charging session, and the only billing-relevant object.

    Source
    "A *Charge Detail Record* is the description of a concluded charging session. The CDR is the only billing-relevant object."OCPI 2.2.1 CDRs module · #mod_cdrs_cdrs_module
    See it in the lesson
  • Token

    What a driver presents to charge, such as an RFID card. The Tokens module gives the CPO the token information of an eMSP.

    Source
    "The tokens module gives CPOs knowledge of the token information of an eMSP."OCPI 2.2.1 Tokens module · #mod_tokens_tokens_module
    See it in the lesson

How data moves

  • Push

    The owner of data sends it to the other platform's Receiver interface, as a CPO sends a Session update to the eMSP. Receiver is an advertised interface role from OCPI 2.2; 2.1.1 does not advertise it.

    Source
    SENDER: Sender Interface implementation. Interface implemented by the owner of data, so the Receiver can Pull information from the data Sender/owner. RECEIVER: Receiver Interface implementation. Interface implemented by the receiver of data, so the Sender/owner can Push information to the Receiver.OCPI 2.2.1 Version information endpoint chapter · #version_information_endpoint_interface_role_enum
    See it in the lesson
  • Pull

    A platform requests data from the owner's Sender interface, as an eMSP reads a CPO's Locations with GET. Sender is an advertised interface role from OCPI 2.2; 2.1.1 does not advertise it.

    Source
    SENDER: Sender Interface implementation. Interface implemented by the owner of data, so the Receiver can Pull information from the data Sender/owner. RECEIVER: Receiver Interface implementation. Interface implemented by the receiver of data, so the Sender/owner can Push information to the Receiver.OCPI 2.2.1 Version information endpoint chapter · #version_information_endpoint_interface_role_enum
    See it in the Explorer

Interfaces

  • Sender interface

    The interface the owner of data implements, so the other platform can pull information from it. OCPI 2.2 and later advertise SENDER in Endpoint.role; 2.1.1 has no role field.

    Source
    SENDER: Sender Interface implementation. Interface implemented by the owner of data, so the Receiver can Pull information from the data Sender/owner. RECEIVER: Receiver Interface implementation. Interface implemented by the receiver of data, so the Sender/owner can Push information to the Receiver.OCPI 2.2.1 Version information endpoint chapter · #version_information_endpoint_interface_role_enum
    See it in the Explorer
  • Receiver interface

    The interface the receiver of data implements, so the owner can push information to it. OCPI 2.2 and later advertise RECEIVER in Endpoint.role; 2.1.1 has no role field.

    Source
    SENDER: Sender Interface implementation. Interface implemented by the owner of data, so the Receiver can Pull information from the data Sender/owner. RECEIVER: Receiver Interface implementation. Interface implemented by the receiver of data, so the Sender/owner can Push information to the Receiver.OCPI 2.2.1 Version information endpoint chapter · #version_information_endpoint_interface_role_enum
    See it in the Explorer

Find the term used in an exchange

Use this glossary when a role, module or object name is unfamiliar. Parties and roles keeps the market definitions together; later sections explain the labels used in the lessons and reference.

A Charging Point Operator (CPO) operates a network of Charge Points. An e-Mobility Service Provider (eMSP) gives EV drivers access to charging services. A roaming hub connects CPOs and eMSPs.

Where to go next

Common questions

Where are CPO, eMSP and hub defined?

Open Parties and roles, or follow a role anchor directly. Each definition stays beside its context and Sources links so you can distinguish the market role from a version-specific wire value.

Where can I inspect the fields behind a term?

Use the OCPI Explorer link to open the module reference, then choose the version you are implementing. Its field tables and Sources links provide the next level of detail.

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.