Search NASA⌕ Search

SEARCH · Search NASA

Results for “OCPP”

Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 19 records
All sourcesNASA NTRSDOE OSTI
DOE OSTI2023

Disrupting EV Charging Sessions and Gaining Remote Code Execution with DoS, MITM, and Code Injection Exploits using OCPP 1.6

Open Charge Point Protocol (OCPP) 1.6 is widely used in the electric vehicle (EV) charging industry to communicate between Charging System Management Services (CSMSs) and Electric Vehicle Supply Equipment (EVSE). Unlike OCPP 2.0.1, OCPP 1.6 uses unencrypted websocket communications to exchange information between EVSE devices and an onpremise or cloud-based CSMS. In this work, we demonstrate two machine-in-the-middle (MITM) attacks on OCPP sessions to terminate charging sessions and gain root access to the EVSE equipment via remote code execution (RCE). Second, we demonstrate a malicious firmware update with a code injection payload to compromise an EVSE. Lastly, we demonstrate two methods to prevent availability of the EVSE or CSMS. One of these, originally reported by SaiFlow, prevents traffic to legitimate EVSE equipment using a DoS-like attack on CSMSs by repeatedly connecting and authenticating several CPs with the same identities as the legitimate CP. These vulnerabilities were demonstrated with proof-of-concept exploits in a virtualized Cyber Range at Wright State University and/or with a 350 kW Direct Current Fast Charger (DCFC) at Idaho National Laboratory. The team found that OCPP 1.6 could be protected from these attacks by adding secure shell (SSH) tunnels to the protocol, if upgrading to OCPP 2.0.1 was not an option. Index Terms—Electric vehicle charging, cybersecurity, OCPP, cyberattack, cyber-resilience. INSPEC Accession Number: 23981565

99 GENERAL AND MISCELLANEOUS↗
DOE OSTI2025

Ocpp 2.0.1. Interim Kpi Calculator

The project is split into four pieces. The first is a raw OCPP log parser. The second is a file splitter. The third is a message parser. The final piece is the Interim KPI calculator. The OCPP log parser was created from two different formats of raw OCPP 2.0.1 data. Its intended purpose is to extract device IDs and OCPP event messages from nontabular text logs. The parser looks for specific substrings in the logs to identify which of the two "standards" it should select from. The KPI generator does not perform any of its calculations in parallel. Instead, we opt for a naive batching approach. The splitter takes the file generated from the parser and creates many smaller files for each of the device IDs in the dataset. This allows the pandas queries in the log formatter to be iterate over a significantly smaller slice of data, increasing performance significantly. The message parser step takes messages from each of the files (containing distinct device IDs) and breaks the message out into pieces. The final result is a file with different columns specifying different attributes of the JSON message. The file is an aggregation of all different devices. This is the most complex portion of the code. The KPI calculator takes the parsed messages, as a single file, and calculates the KPI from that data. An excel file is produced with four sheets. These contain the metrics for Session Success, Charge Start Success, Charge End Success, and Charge Start Time. It includes the metrics for the different equations in the Interim KPI Implementation Guide as well as a weighted sum of the different equations for each KPI (excluding Charge End Success and Charge Start Time).

Quinn, Casey↗
DOE OSTI2026

Unsupervised Detection of SOC Spoofing in OCPP 2.0.1 EV Charging Communication Protocol Using One-Class SVM

The electric vehicles (EVs) market keeps growing globally; thus, it is critical to secure the EV charging communication protocols in order to guarantee reliable and fair charging operations among the customers. The Open Charge Point Protocol (OCPP) 2.0.1 supports the communication between the Electric Vehicle Supply Equipment (EVSE) and Charging Station Management Systems (CSMSs); therefore, it becomes vulnerable to several types of attacks, which aim to jeopardize smart charging, billing, and energy management. Specifically, OCPP 2.0.1 allows the self-reporting of the State of Charge (SOC) values, which makes it vulnerable to spoofing-based cyberattacks, which target manipulating the scheduling priorities, distorting the load forecasts, and extending the charging sessions in an unfair manner. In this paper, we try to address this type of attack by providing a comprehensive analysis of the SOC spoofing attacks and introducing a novel unsupervised detection framework based on the One-Class Support Vector Machine (OCSVM) algorithm. Specifically, two types of attack scenarios are analyzed (i.e., priority manipulation and session extension) by deriving engineered features that capture the nonlinear relationships under normal charging behavior. Detailed simulation-based results are derived by utilizing the DESL-EPFL Level 3 EV charging dataset. Our results demonstrate high F1-score and recall in identifying spoofed SOC values and that the proposed OCSVM model demonstrates superior performance compared to alternative clustering and deep-learning based detectors.

EV charging↗
DOE OSTI2024

Motivation and Design of the OCPP Security Service

Pacific Northwest National Laboratory is conducting in-depth research aimed at exploring how zero trust security principles can be effectively applied to electric vehicle charging infrastructure. This investigation seeks to enhance the resilience and reliability of these systems against cyber threats, ensuring secure and uninterrupted access to charging services for electric vehicle users and electric supply. Zero trust is a security concept centered on the belief that system operators should not automatically trust users or systems based on their location, whether inside or outside the organization, but instead must verify everything trying to connect to their systems before granting access. A key aspect of the project is to demonstrate and validate zero trust approaches targeted to electric vehicle (EV) charging infrastructure. It has been observed that both open-source and commercial solutions often overlook the specific protocols employed in managing EV charging stations and proceeded with a general, protocol-agnostic approach. While these strategies effectively block non-authorized routes to the charging infrastructure, they do not tackle the situations where attackers may exploit legitimate access channels, such as the inattentive operator model posited by the Idaho National Laboratory. To address this gap, this paper proposes and discusses a new security service targeted to the Open Charge Point Protocol (OCPP), which is the de facto protocol for the management of charging stations and serves a critical role in the broader adoption of electric vehicles. The design and architecture of the proposed OCPP security service are discussed in detail, outlining how it aims to safeguard charging station management system (CSMS) functions. The service is particularly important in scenarios where the charging station operator (CSO), responsible for the maintenance and operation of charging stations, and the charging network provider (CNP), which manages the charging network's accessibility and billing, are separate entities. This distinction is crucial because CSOs and CNPs often have different priorities, objectives, and operational responsibilities, which may not always align perfectly. For instance, a CSO might prioritize uptime and customer satisfaction, while a CNP might focus on maximizing revenue and network utilization. Such misalignment can create security vulnerabilities, as each entity might implement different policies and standards, potentially leaving gaps in the overall security posture.

33 ADVANCED PROPULSION SYSTEMS↗
DOE OSTI2025

ChargeX Consortium Presentation at OCPP Plugfest

This is a presentation that outlines the past successes of the INL led Charging Experience Consortium and lists current projects related to vehicle-grid integration. The primary purpose of this presentation is to engage with industry experts and practitioners about the use of the protocol OCPP to enable key improvements to the charging experience for both drivers and the grid.

42 ENGINEERING↗
DOE OSTI2024

Electric Vehicle Standards – Grid Service Capabilities: Evaluation of IEEE 2030.13, SAE J3072, ISO 15118-2, ISO 15118-20, OCPP, IEC 61850-7-420, IEEE 2030.5, and OpenADR

This report examines a selection of standards associated with vehicle-grid-integration. The standards will be evaluated on their support for electric vehicles to provide/participate in component distributed energy resource grid services. Challenges associated with the deployments of the standards will also be discussed.

24 POWER TRANSMISSION AND DISTRIBUTION↗
DOE OSTI2023

Recommendations for Minimum Required Error Codes for Electric Vehicle Charging Infrastructure

OCPP protocol manages the interaction between the EVSE and its respective back-end communication network. It plays a pivotal role in both error reporting and troubleshooting, carried out primarily through the CSMS. OCPP defines both standard error codes and a flexible framework for creating and communicating custom error codes. The OCPI protocol orchestrates the communication between different backhaul communication networks, incorporating the exchange of error codes. These error codes are instrumental in pinpointing and rectifying issues that can surface prior to, during, or after charging operations, fortifying the reliability and resilience of the EV charging infrastructure. The flexibility offered by the OCPP and OCPI frameworks through the introduction of custom error codes also creates its own set of challenges. While the integration of custom error codes allows for enhanced granularity, it also introduces inconsistencies and fragmentation within the overarching diagnostic reporting system. To address the challenges with custom error codes this report proposes a set of Minimum Required Error Codes (MRECs) for streamlined error reporting, interpretability, and diagnostics. Recommendations in this report are based on independent analysis of custom error codes from multiple stakeholders within the EV charging ecosystem. For better error resolution, this report also assigns one or more entities responsible for the resolution of every mentioned error code. Finally, a functional classification for each mentioned error code is also identified to describe the nature of the error. In summary, the purpose of this document is to simplify the troubleshooting process and increase charging reliability for all EV users. This report serves as a recommendation for industry stakeholders, encouraging a unified methodology to define, transmit, and interpret common error codes.

29 ENERGY PLANNING, POLICY, AND ECONOMY↗
DOE OSTI2023

Controller Hardware-in-the-Loop Modeling and Operation of a High-Power DC Charging Hub

High-power charging (HPC) concept will be a critical enabler for the wide-scale adoption and integration of electric vehicles (EVs). HPC hubs will have a significant impact on achieving this goal, particularly when considering the charging requirements of next-generation medium and heavy-duty vehicles (MD/HD) used in various vocational scenarios. This emphasizes the significance of evaluating and confirming the technical planning and multi-level operation of HPC hubs through modeling, protocol implementation, and simulation before hardware demonstration. The focus of this study is to develop the architecture, modeling, communication, and real-time controller hardware-in-the-loop (C-HIL) simulation of HPC hubs using the DC distribution system approach. Specifically, this work demonstrates the practical implementation of a custom Smart Energy Management System (SEMS) for a real-time C-HIL HPC hub simulation using the Open Charge Point Protocol (OCPP) for communication. OCPP is implemented on the Node-Red framework and the custom controller is executed in Python. We developed a rule-based controller to demonstrate the proposed approach.

ADVANCED PROPULSION SYSTEMS↗
DOE OSTI2024

node-red-contrib-ocpp2

Open source Node-Red "nodes" to support the Open Charge Point Protocol (OCPP) 2.0.1 protocol.

Nystrom, Bryan↗
DOE OSTI2025

EVSE DERMS Controls [SWR-26-010]

An MQTT (Message Queuing Telemetry Transport) and OCPP (Open Charge Point Protocol) based remote smart charging controller framework for AC Electric Vehicle Supply Equipments (EVSEs). The code in this repo allows for the National Laboratory of the Rockies (NLR) controls to interface with the real Distributed Energy Resource Management System (DERMS) and EVSEs in NLR's ESIF Optimization and Control Laboratory (OCL). Different charge management algorithms can be tested to determine which power allocation method is most effective with the overall goal of demonstrating clear and well documented test results as well as providing functional control algorithms which could be utilized to provide effective smart charge management (SCM) at EV charging stations. Different power allocation methods are programmed in lab_demo_controller.py and include allocation based on first come first served, equal sharing, state of charge (SOC), priority factors, and behind the meter control methods.

Panossian, Nadia [National Laboratory of the Rocki↗
DOE OSTI2023

Implementation Guide for Minimum Required Error Codes in Electric Vehicle Charging Infrastructure

With the growing adoption of Electric Vehicles (EVs), there is an increasing need for a reliable EV charging infrastructure. To help meet this need, the report “Recommendations for Minimum Required Error Codes for Electric Vehicle Charging Infrastructure,” recommends a set of minimum required error codes (MRECs) and their functional and responsibility classification. Charger manufacturers, charging station operators, EV manufacturers, and other stakeholders in the North American market are encouraged to uniformly adopt the MRECs to enhance EV charging error reporting, interpretation, and diagnostics. This document serves as a guide to enable uniform implementation of the MRECs using the Open Charge Point Protocol (OCPP).

29 ENERGY PLANNING, POLICY, AND ECONOMY↗
DOE OSTI2025

Implementation Guide of Customer-Focused Key Performance Indicators for Electric Vehicle Charging

This report describes how individual and unique messages that are sent over in OCPP sessions and/or transactions are used to calculate the interim set of key performance indicators (KPI) established by ChargeX Consortium’s Working Group 1: Defining the Charging Experience in the report entitles “Customer-Focused Key Performance Indicators for Electric Vehicle Charging.

33 ADVANCED PROPULSION SYSTEMS↗
DOE OSTI2025

Recommendations for Minimum Required Diagnostics Information

The rapid growth of electrified transportation, including light- and medium-duty electric vehicles (EVs) as a mobility solution requires a reliable EV-charging infrastructure. To advance charging reliability, the ChargeX Consortium reports “Recommendations for Minimum Required Error Codes for Electric Vehicle Charging Infrastructure” and “Implementation Guide for Minimum Required Error Codes in Electric Vehicle Charging Infrastructure” provided recommendations for a set of minimum required error codes (MRECs), their functional and responsibility classifications, and a guide for their implementation, using Open Charge Point Protocol (OCPP) versions 1.6J4 and 2.0.1.5 These reports outline a recommended practice for consistent error reporting and interpretation, which is essential for communicating issues uniformly across the complex and diverse EV-charging ecosystem. However, MRECs are just one part of diagnosing issues; another critical part is obtaining enough information about the current state and performance of the various charging components to identify root causes for each of the error codes. This additional diagnostics data can be used by technicians or automated systems to understand the context around an issue, allowing for timely resolution, decreased maintenance costs, and increased charging reliability. During everyday operations, data are regularly collected and analyzed across the ecosystem. Although sharing of all that available data would be great for diagnostics, concerns on data ownership, privacy, and original equipment manufacturer (OEM) intellectual property pose a challenge. To overcome this obstacle, this report proposes a set of minimum required diagnostic information (MRDI) and recommends that the industry implement these uniformly across the North American EV charging ecosystem. MRDI provides a means to exchange only data deemed necessary for root cause determination.

33 ADVANCED PROPULSION SYSTEMS↗
DOE OSTI2024

Implementation Guide of Customer-Focused Key Performance Indicators for Electric Vehicle Charging

This report describes how individual and unique messages that are sent over in OCPP sessions and/or transactions are used to calculate the interim set of key performance indicators (KPI) established by ChargeX Consortium’s Working Group 1: Defining the Charging Experience in the report entitles “Customer-Focused Key Performance Indicators for Electric Vehicle Charging.

33 - ADVANCED PROPULSION SYSTEMS↗
DOE OSTI2025

Recommendations for Minimum Required Diagnostics Information for Electric Vehicle Charging Infrastructure

The rapid growth of electrified transportation, including light- and medium-duty electric vehicles (EVs) as a mobility solution requires a reliable EV charging infrastructure. To advance charging reliability, the ChargeX Consortium reports “Recommendations for Minimum Required Error Codes for Electric Vehicle Charging Infrastructure” and “Implementation Guide for Minimum Required Error Codes in Electric Vehicle Charging Infrastructure” have provided recommendations for a set of minimum required error codes (MRECs), their functional and responsibility classifications, and a guide for their implementation using OCPP versions 1.6J and 2.0.1. These reports outline a recommended practice for consistent error reporting and interpretation, which is essential for communicating issues uniformly across the complex and diverse EV charging ecosystem. However, MRECs are just one part of diagnosing issues, another critical part is obtaining enough information about the current state and performance of the various charging components to identify root causes for each of the error codes. This additional diagnostics data can be used by technicians or automated systems to understand the context around an issue, allowing for timely resolution, decreased maintenance costs, and increased charging reliability. During everyday operations, data is regularly collected and analyzed across the ecosystem. Although sharing of all that available data would be great for diagnostics, concerns on data ownership, privacy, and OEM intellectual property pose a challenge. To overcome this obstacle, this report proposes a set of Minimum Required Diagnostic Information (MRDI) and recommends that the industry implement these uniformly across the North American EV charging ecosystem. MRDI provides a means to exchange only data deemed necessary for root cause determination.

32 - ENERGY CONSERVATION, CONSUMPTION, AND UTILIZA↗