OCPP Conf

Configuration key Required Optional

AllowOfflineTxForUnknownId x
AuthorizationCacheEnabled x
AuthorizeRemoteTxRequests x
BlinkRepeat x
ClockAlignedDataInterval x
ConnectionTimeOut x
GetConfigurationMaxKeys x
HeartbeatInterval x
LightIntensity x
LocalAuthorizeOffline x
LocalPreAuthorize x
MaxEnergyOnInvalidId x
MeterValuesAlignedData x
MeterValuesAlignedDataMaxLength x
MeterValuesSampledData x
MeterValuesSampledDataMaxLength x
MeterValueSampleInterval x
MinimumStatusDuration x
NumberOfConnectors x
ResetRetries x
ConnectorPhaseRotation x
ConnectorPhaseRotationMaxLength x
StopTransactionOnEVSideDisconnect x
StopTransactionOnInvalidId x
StopTxnAlignedData x
StopTxnAlignedDataMaxLength x
StopTxnSampledData x
StopTxnSampledDataMaxLength x
SupportedFeatureProfiles x
SupportedFeatureProfilesMaxLength x
TransactionMessageAttempts x
TransactionMessageRetryInterval x
UnlockConnectorOnEVSideDisconnect x
WebSocketPingInterval x
LocalAuthListEnabled x
LocalAuthListMaxLength x
SendLocalListMaxLength x
ReserveConnectorZeroSupported x
ChargeProfileMaxStackLevel x
ChargingScheduleAllowedChargingRateUnit x
ChargingScheduleMaxPeriods x
ConnectorSwitch3to1PhaseSupported x
MaxChargingProfilesInstalled x
Additional Requirements for Configuration keys fro
chargerID x

Endpoint x

APN x
IMSI x

ICCID x

DefaultID x

Freemode x

ConnectorPhaseRotation x

StopTxnAlignedData x

StopTxnSampledData x

StopTxnSampledDataMaxLength x
StopTransactionOnEVSideDiscon- nect x

UnlockConnectorOnEVSideDis- connect x
 OCPP Configuration Keys
Supported By Default value
Supplier
(Yes/No)
l Requirements for Configuration keys from Blusmart
Keys
Comments by supplier, OCPP 1.6 standard reference
if key is named by something else but have the Full DOCUMENT location
same function http://www.openchargealliance.org/download
please write that name s/

9.1.1
9.1.2
9.1.3
9.1.4
9.1.5
9.1.6
9.1.7
9.1.8
9.1.9
9.1.10
9.1.11
9.1.12
9.1.13
9.1.14
9.1.15
9.1.16
9.1.17
9.1.18
9.1.19
9.1.20
9.1.21
9.1.22
9.1.23
9.1.24
9.1.25
9.1.26
9.1.27
9.1.28
9.1.29
9.1.30
9.1.31
9.1.32
9.1.33
9.1.34
9.2.1
9.2.2
9.2.3
9.3.1
9.4.1
9.4.2
9.4.3
9.4.4
9.4.5
Comments from the Purchaser

The Charger shall support updating the

chargerID using change configuration operation
The charger shall support updating of End point
using change configuration operation
Charger shall support customized APN
Charger shall have a configuration key that will
return the IMSI number of the SIM card installed
in the charger
Charger shall have a configuration key that will
return the ICCID number of the SIM card
installed in the charger

The default idtag should be an additional

configuration key supported by the Charger to
set the idtag that shall be sent in
starttransaction when freemode is on. This key
shall have Read-Write access
When set to true, the charger shall support Free
mode of charging by allowing CP to start a new
transaction as soon as car is connected.

For individual connector phase rotation infor-

mation, the Central System may query the Con-
nectorPhaseRotation configuration key on the
Charging Point via GetConfigura- tion. The
Charge Point shall report the phase rotation in
re- spect to the grid connection.

Clock-aligned periodic measurand(s) to be

included in the TransactionData element of
Stop- Transaction.req Meter- Values.req PDU for
every ClockAlignedDataInterval of the charging
session

Sampled measurands to be included in the

Trans- ac- tionData element of
StopTransaction.req PDU, every Meter-
ValueSampleInterval seconds from the start of
the charging session
Maximum number of items in a
StopTxnSampledData Con- figuration Key.
When set to true, the Charge Point shall
administratively stop the transaction when the
cable is unplugged from the EV.
NOTE: this parameter is not being used,
Transaction will al- ways stop on EV disconnect
or even before.

When set to true, the Charge Point shall unlock

the cable on Charge Point side when the cable is
unplugged at the EV.

NOTE: not applicable for ABB TerraAC chargers,

not imple- mented
 Operation Initiated by Supported By Supplier
Authorize CP Yes
BootNotification CP Yes
Data Transfer CP
Diagnostics Status Notification CP Yes
Firmware Status Notification CP Yes
Heartbeat CP Yes

MeterValues CP Yes

Start Transaction CP Yes

StatusNotification CP Yes

Stop Transaction CP Yes

Cancel Reservation CS
Change Availability CS

Change Configuration CS Yes

Clear Cache CS Yes

Clear Charging Profile CS Yes
Data Transfer CS
Get Composite Schedule CS Yes

Get Configuration CS Yes

Get Diagnostics CS Yes

Get Local List Version CS Yes

Remote Start Transaction CS Yes
Remote Stop Transaction CS Yes
Reserve Now CS Yes

Reset (Soft and Hard) CS Yes

Send Local List CS Yes

Set Charging Profile CS Yes

Trigger Message CS Yes
Unlock Connector CS Yes

Update Firmware CS Yes

Open mode/Free Charging CS Yes

Core CS Yes

Firmware CS Yes
Management CS Yes

Local Auth List Management CS Yes

Reservation CS Yes
Smart Charging CS Yes
Remote Trigger CS Yes
Dynamic Load Sharing CS Yes
Vehicle ID (VIN) Number CS Yes
 OCPP Operations
OCPP 1.6 Full Document Location
OCPP 1.6 Standard Reference
OCPP 1.6 Standard Reference
OCPP 1.6 Standard Reference
OCPP 1.6 Standard Reference
OCPP 1.6 Standard Reference
OCPP 1.6 Standard Reference
OCPP 1.6 Standard Reference
OCPP 1.6 Standard Reference

OCPP 1.6 Standard Reference

OCPP 1.6 Standard Reference

OCPP 1.6 Standard Reference
OCPP 1.6 Standard Reference

OCPP 1.6 Standard Reference

OCPP 1.6 Standard Reference

OCPP 1.6 Standard Reference
OCPP 1.6 Standard Reference
OCPP 1.6 Standard Reference
OCPP 1.6 Standard Reference

OCPP 1.6 Standard Reference

OCPP 1.6 Standard Reference
OCPP 1.6 Standard Reference
OCPP 1.6 Standard Reference
OCPP 1.6 Standard Reference
OCPP 1.6 Standard Reference

OCPP 1.6 Standard Reference

OCPP 1.6 Standard Reference
OCPP 1.6 Standard Reference
OCPP 1.6 Standard Reference

OCPP 1.6 Standard Reference

OCPP 1.6 Standard Reference

OCPP 1.6 Standard Reference

OCPP 1.6 Standard Reference
OCPP 1.6 Standard Reference

OCPP 1.6 Standard Reference

OCPP 1.6 Standard Reference

OCPP 1.6 Standard Reference
OCPP 1.6 Standard Reference
OCPP 1.6 Standard Reference
OCPP 1.6 Standard Reference
 OCPP Operations
Requirements from Blusmart
4.1 Authorize request shall support all idtag byte lengths (it shall handle 4, 7, 3, 5, and other byte lengths)
4.2 Bootnotification shall include firmwareVersion, ChargePointModel, ICCID, IMSI, ChargePointVendor, ChargePointSerialNumber
4.3
4.4
4.5
4.6
4.7 MeterValueSampleInterval shall be editable. Charger shall support turning off and turning on of MeterValues. The MeterValues sh
contain voltage, current, SoC, Power, Temperature
4.8
4.9 If the power goes off and the modem is on backup battery, the charger shall send unavailable status, with info "No Power availabl
When the power comes back, the charger shall send available status with info "Power Available." Other faults from the charger like MC
trip, Over current, under voltage, over voltage, high temperature, Earth fault at input and output, Emergency shut-down, Emergency
stop, Over temperature, etc. shall be sent to the CS as status notification with appropriate error code and info. Refer OCPP 1.6 protoco
section 7.6 ChargePointErrorCode for reference
4.10 The stoptransaction request shall contain the "reason" why the transaction was stopped.
5.1
5.2
5.3 Change Configuration key shall only update the keys with Read Write access from CS. Charger shall send accepted on keys that ar
changed to correct values. Charger shall send rejected on keys that are changed to faulty values. Charger shall send reboot required o
settings that require a reboot in order to apply the changes made
5.4 Clear Cache shall clear the Authorization Cache. Not the Local Authorization List
5.5
5.6
5.7
An empty GetConfiguration.req shall give all Configuration keys for the charger (See sheet OCPP Configuration keys list expected from
the charger)
5.9 The file uploaded shall include enough information for the Charger operator to do full diagnosis of the charger's fault without hav
to manually go to the charger
5.1
5.11 Remote Start Transaction shall support all idtag byte lengths (it shall handle 4, 7, 3, 5, and other byte lengths)
5.12
5.13
5.14 The charger shall support Soft reset and Hard reset. The charger should handle Soft reset and Hard reset differently according to
section 5.14 in OCPP standard document
5.15 SetCharging Profile shall support all idtag bytes lengths (it shall handle 4, 7, 3, 5, and other byte lengths). The Charger shall be ab
to store 10,000,000 RFID tags. The List shall remain after reboot
5.16 TxDefaultProfile shall remain after reboot
5.17
5.18
5.19 Update firmware shall update the FW through a single file uploaded to the charger from the CS. No manual intervention is allow
All settings of the charger shall remain the same before and after the FW update also it should comply OTA updatation
The Charger shall support Open mode/Free charging mode of charging by allowing CP to start a new transaction as soon as the car is
connected to it. All the starttransactions to CS should contain idTag as the default idtag. The default idtag should be an additional
configuration key supported by the Charger and shall have Read-Write access (See sheet OCPP Configuration Keys)
Basic Charge Point functionality comparable with OCPP without support for firmware updates, local authorization list management an
reservations.
Support for firmware update management and diag- nostic log file download.

Features to manage the local authorization list in Charge Points.

Support for reservation of a Charge Point

Support for basic Smart Charging
Support for remote triggering of Charge Point initi-ated messages
Support Auto Dynamic Load balancing Through both Charging Guns
Support VIN Detection Number before Pre Authorisation stage
Vendor Comments
 Vendor
Message Comments
Supported (Y/N)
Core profile

Authorize Y

BootNotification Y
ChangeAvailability Y
ChangeConfiguration Y

ClearCache Y

DataTransfer Y

GetConfiguration Y

POWER LOSS Y
HeartBeat Y

MeterValues Y

RemoteStartTransaction Y
RemoteStopTransaction Y

Reset Y

StartTransaction Y
StatusNotification Y
StopTransaction Y

UnlockConnector Y

Firmware Management profile

GetDiagnostics Y

DiagnosticsStatusNotification Y

FirmwareStatusNotification Y
FirmwareStatusNotification Y

UpdateFirmware Y
Local Auth List Management
GetLocalListVersion Y

SendLocalList Y

Reservation
CancelReservation N
ReserveNow N
Smart charging
ClearChargingProfile Y
GetCompositeSchedule Y

SetChargingProfile Y

Remote Trigger

TriggerMessage Y

Improved Security

SecurityEventNotification Y

GetLog Y

LogStatusNotification Y

Dynamic Load sharing

Dynamic Switching Y
 Requirement Comment

Core profile
Example when two different online cards: card #1 swiped and starts, card #2 swipes, card #2 is checked by
back-end card, if ac- cepted charging stops. If rejected charging continues

The cache is empty, while the charger re-ceived the command, it will response accept but do nothing. While
the charger connects to customer’s own back end, customer could use this mes- sage for log transfer.

Through UPS , Power Loss detection per phase is required

Trigger Capabilities from Client side if Loss of Heartbeat

· Energy.Active .Import.Register ·
· Current.Import
· Voltage
· Power.Active.Import
· Current.Offered
· Vehicle Demand Voltage & Current
· AC Grid Voltage

Chargers support hard reset and soft reset.Hard reset fully reboot charger. The resets gracefully stop
charging session if one is in pro- gress before resetting.
Soft reset gracefully stops charging session if one is in progress before resetting. Then the charger
gracefully disconnects from the server. After disconnection, the charger will reboot it- self.

Message is supported only to socket variants, upon receiving this message, socket variantscharger will
release the E-lock of socket. If send the message to cable variants, the charger will response with
NotSupported.
Firmware Management profile
Supports 7-day logs with 300 lines/less than 25kb per day.
Charger uploads the files by HTTP/HTTPS based on the server connection.
Support status: Uploading, Uploaded, Upload- Failed, Idle.
Charger will response the status:
· Downloading
· Installed
 · DownloadFailed
· InstallationFailed
OTA
Local Auth List Management

Each list is limited to 8 ID tag, each ID tag with max 20 characters; The charger has a total limit of 16 ID
tags.
Reservation
Planned in roadmap.
Planned in roadmap.
Smart charging

ChargeProfileMaxStackLevel = 16 for display models.

ChargeProfileMaxStackLevel = 3 for non-display models.
Remote Trigger
Chargers supports below MessageTrigger:
· BootNotification
· DiagnosticsStatusNotification
· FirmwareStatusNotification
· Heartbeat
· MeterValues
· StatusNotification
Improved Security
Chargers supports below SecurityEventNotification:
· FirmwareUpdated
· SettingSystemTime
· StartupOfTheDevice
· ResetOrReboot
· MemoryExhaustion
· SecurityLogWasCleared
· InvalidFirmwareSignature
· AttemptedReplayAttacks
Chargers only supports request SecurityLog, Diagnos-ticsLog to be supported

Charger will response the status:

· Uploading
· Uploaded
· UploadFailure
Dynamic Load sharing
Charger will support Dynamic load sharing and publish message on each active switching by GUN transfer
or Load Balancing Stage