The Current and Projected Stats for the EV Market

The latest release of the IEA’s annual Global Electric Vehicle Outlook 2024 suggests that electric car sales continue to rise and could reach around 17 million in 2024, accounting for more than one in five cars sold worldwide. Electric cars continue to make progress towards 

becoming a mass-market product in more countries. In the first quarter of 2024, electric car sales grew by around 25% compared with the first quarter of 2023, similar to the year-on-year growth seen in the same period in 2022. In the STEPS and APS, the global 

number of public charging points is projected to exceed 15 million by 2030, a four-fold increase compared to the almost 4 million operating in 2023. By 2035, this number is expected to reach almost 25 million in the APS, a magnificent six-fold increase relative to 2023. 

 Understanding OCPP 1.6 

OCPP 1.6 is a protocol used by charging stations and the cloud they connect to. It was designed by OCA and is accepted by major EV charger development organizations. It’s widely used because it’s efficient at making sure different parts of the EV charging system can work together smoothly. 

OCPP (Open Charge Point Protocol) 1.6 is a standard protocol in the electric vehicle (EV) 

charging infrastructure, facilitating seamless communication between charging stations and central management systems. Firmware updates in OCPP 1.6 are managed through specific commands and procedures, ensuring that charging stations can receive and install new 

firmware versions seamlessly. 

How OCPP FOTA is different from normal device FOTA? 

How Does Firmware Update Work in OCPP 1.6? 

Firmware updates typically involve steps such as initiating the update from the central system, downloading the new firmware, installing it on the charging station, and verifying successful installation. 

If customers desire products with seamless software updates, they should verify whether the Charge Point supports the firmware management profile and adheres to these guidelines. 

How to Implement Firmware Update Request in CSMS?

This section covers the specifics of the firmware update procedure within the OCPP 1.6 framework in detail.

1. Establishing Communication Channels: 
   
   • Set up secure communication channels between the CSMS and charging stations using protocols like JSON over WebSocket [OCPP-J] or SOAP [OCPP-S]. 
   • Ensure authentication mechanisms are in place to validate requests and prevent unauthorized access. 

    

2. Handling Update Requests:
   
   • Implement an endpoint in the CSMS to receive firmware update requests from mobile app or web interface. 
   • Validate incoming requests, including firmware version, checksum, and charger Id to ensure integrity and authenticity. 

    

3. Processing Update Requests:
   
   • Upon receiving a valid update request, retrieve the requested firmware version from a secure repository or external source. 
   • Verify the firmware integrity using checksums or digital signatures to prevent tampering during transmission. 

    

4. Initiating Firmware Updates:
   
   • Use specific commands like Update Firmware Request from OCPP 1.6 to start updating the firmware on the desired charging station. 
   • When sending the update command, ensure inclusion of all necessary information such as the location of the new firmware, the retrieval date, and any other relevant details. 

    

5. Monitoring and Reporting:
   
   • Implement mechanisms to monitor the update progress and status as defined by OCPP standards, such as Downloaded, DownloadFailed, Downloading, Idle, InstallationFailed, Installing, Installed on the CSMS side. 
   • Keep records to track firmware update activities, including success rates, completion times, and any problems or errors encountered along the way. 

Handling Versioning and Compatibility in Firmware Updates

Versioning and compatibility are crucial aspects of managing firmware updates for charging stations. Here are the key steps: 

• Retrieve Firmware Versions:
  • The server fetches the latest firmware version from the designated firmware location. Ensure that firmware file naming aligns with version numbers.
    
    
• Compare Versions: 
  • Compare the retrieved firmware version with the current version on the charging station to check for updates.
• Determine Update Availability: 
  • If the charging station’s firmware version is older, proceed with the update process as a newer version is available.
• Update Process: 
  • Initiate the firmware update by sending the updated firmware to the charging station for installation.
• Continued Operations: 
  • If the firmware is up to date, the server can continue normal operations without initiating an update. 

By managing firmware versions effectively, charging stations benefit from bug fixes, security enhancements, and improved compatibility offered by updated firmware. 

Best Practices for Firmware Updates 

You can use the following best practices for the firmware update process in OCPP 1.6. 

• Provide guidelines and best practices for conducting firmware updates on EV 

chargers, such as scheduling updates during off-peak hours, performing backups, and following manufacturer recommendations. 

• To restrict HTTPS URL access during firmware upgrades, implement time-based 

controls or expiration mechanisms. Use token-based authentication with time-limited tokens, validate expiration timestamps, and monitor access for security. These 

strategies enhance control and security over firmware update resources. 

• Configure the FTPS server on the charger or central server side. Ensure it supports FTP over SSL/TLS for secure file transfer. Implement strong authentication mechanisms for FTPS, such as username/password or client certificates. 

• The charging point must not be accessible while the firmware is being updated. However, it is up to the manufacturer to determine at which exact point in the upgrade the status is changed to Unavailable, via the status notification request (e.g. during downloading/Installing) 

• After the successful installation of the firmware, the charger will automatically restart itself as part of the update process. 

• After rebooting post-firmware update, the charger sends a boot notification confirming successful update and indicating the new firmware version. 

Some Standards and Guidelines for EV Domain 

Some standards for OTA (Over-The-Air) updates for chargers typically revolve around several key areas to ensure safety, reliability, and interoperability within the charging infrastructure ecosystem. 

• Authorities may encourage or mandate the use of open standards like OCPP for EV charger communication and OTA updates. 

• Policies may require OCPP chargers to adhere to cybersecurity standards to protect against cyber threats during OTA updates. This could include encryption of data, secure authentication mechanisms, and vulnerability assessments. 

• Compliance with data privacy regulations like GDPR ensures that user data collected during OTA updates on OCPP chargers is securely handled and aligned with privacy standards. 

• Charger manufacturers and operators may need certifications to prove compliance with OCPP charger OTA update regulations, validating adherence to industry standards. 

• Regulatory bodies may supervise OTA update implementation in OCPP chargers, conducting audits and mandating reports on cybersecurity, data protection, and update protocols. 

Conclusion

To put it simply, implementing Firmware Over-The-Air (FOTA) updates on the server side requires careful planning and a focus on security and user satisfaction. By following best 

practices, checking compatibility, testing thoroughly, and communicating clearly, companies can deliver smooth and secure updates to connected devices. This not only improves device performance but also makes users happy and builds trust, leading to success in the world of connected devices.

Reference Link: 

https://www.iea.org/reports/global-ev-outlook-2024/trends-in-electric-cars
https://powermin.gov.in/sites/default/files/uploads/Revised_MoP_Guidelines_01_10_2019.pdf