Validate without a PnC vehicle
BARK reproduces the vehicle role to check contract certificate requests, TLS/PnC authentication, and charging authorization conditions in the lab.
PKI BACKEND · PNC SERVER
Backend architecture
for issuing and validating
PnC certificates
Even before a real PnC vehicle or external certificate infrastructure is available, ELIOLABS can validate the Plug and Charge flow end to end with its own PKI Backend.
BARK reproduces the vehicle role, while TROY SECC, the HAROK charger app, ARCANIA CSMS, and the PKI Backend connect certificate issuance, authentication, charging authorization, and transaction evidence in one validation loop.
Standard APIPublic interface prepared for standard-aligned integration
pnc-webAPI, Workbench, request validation and response routing
pnc-caPKI Core for issuing, revocation state and chain validation
EXIISO 15118 response generation path
EvidenceARCANIA, BARK and THOR validation outputs
Why a dedicated PKI Backend?
It keeps product development and CSMS integration moving even when a PnC-capable vehicle or external certificate infrastructure is not yet ready.
Standard-facing boundary
The public integration surface is organized around /v1 style APIs so CSMS and device-side tools can work from the same interface.
Separated certificate management
Certificate issuance and validation are handled by a separated PKI Core layer, keeping the operational UI and trust boundary distinct.
Device-to-server evidence
TROY, HAROK, ARCANIA, BARK and THOR outputs are connected into reports that show authentication flow and transaction records.
Validation flow without a PnC vehicle
BARK takes the vehicle role, and pnc-server provides the certificate layer that links to charging authorization and transaction evidence.
BARK EV Role
Reproduces vehicle-side authentication requests and charging session conditions without a real PnC vehicle.
TROY / HAROK
Connects SECC communication and charger app control into actual charger behavior.
pnc-web Routing
Handles standard-facing APIs, Workbench UI, external response format, and request validation.
pnc-ca Core
Processes contract certificate issuance, chain validation, revocation state, and certificate hierarchy management.
ARCANIA Evidence
Connects authentication result to charging authorization, transaction event, and validation report.
How it connects inside the system
BARK, TROY, HAROK, ARCANIA, and the PKI Backend operate as one Plug and Charge validation loop.
Creates an ISO 15118 session as the vehicle-side test device and provides screen/report evidence.
Handles PLC, SLAC, SDP, and V2G sessions from the charger-side communication layer.
Links charger state control and OCPP-side operating conditions through the app flow.
Manages Authorize, Transaction, MeterValue, SimCert, and report flows.
Provides certificate issuance, validation, and test-set management for the PnC trust layer.
Plug and Charge validation connected through the backend
pnc-server, ARCANIA CSMS, and BARK/THOR evidence make the standard implementation visible as a product-level validation loop.