Lab validation
BARK can reproduce contract certificate requests, TLS/PnC authentication and charging authorization conditions before a real PnC vehicle is available.
PNC · CONTRACT · TRANSACTION
PnC authentication connected to charging authorization, transaction and meter data
Plug and Charge does not end at vehicle certificate validation. The contract certificate result must connect to charging authorization, transaction creation and meter values before it becomes a real service.
Contract CertPnC credential
TLS/PKITrust validation
AuthorizeCharging permission
TransactionCSMS state
ReportEvidence output
Certificate management
pnc-server provides certificate issuance, chain validation and test-set management.
TROY communication
The charger-side modem handles ISO 15118 session behavior.
ARCANIA
Authorization and transaction results are visible in the server flow.
PnC authentication and PKI Backend architecture
The execution structure connects BARK contract-authentication results to TROY SECC, HAROK charger app, ARCANIA CSMS and the PKI Backend.
BARK EV role
Vehicle-side request is reproduced.
TROY SECC
V2G and secure session flow.
HAROK App
Charging permission and local control.
PKI Backend
Contract certificate and trust chain.
ARCANIA CSMS
Authorization, transaction and report.