https://github.com/openchargingcloud/wwcp_ocpi

Communication between the World Wide Charging Protocol (WWCP) and the Open Charge Point Interface (OCPI v2.1.1 & v2.2.1).
https://github.com/openchargingcloud/wwcp_ocpi

e-mobility ev-roaming ocpi

Last synced: 2 days ago
JSON representation

Communication between the World Wide Charging Protocol (WWCP) and the Open Charge Point Interface (OCPI v2.1.1 & v2.2.1).

• Host: GitHub
• URL: https://github.com/openchargingcloud/wwcp_ocpi
• Owner: OpenChargingCloud
• License: apache-2.0
• Created: 2015-09-01T15:37:45.000Z (over 9 years ago)
• Default Branch: master
• Last Pushed: 2024-12-27T09:10:33.000Z (9 days ago)
• Last Synced: 2024-12-27T10:20:00.573Z (9 days ago)
• Topics: e-mobility, ev-roaming, ocpi
• Language: C#
• Homepage:
• Size: 10.8 MB
• Stars: 27
• Watchers: 5
• Forks: 7
• Open Issues: 1
• Metadata Files:
  • Readme: README.md
  • Funding: .github/FUNDING.yml
  • License: LICENSE

Awesome Lists containing this project

README

        
WWCP OCPI

=========

This software will allow the communication between World Wide Charging Protocol (WWCP) entities and entities implementing the [Open Charge Point Interface (OCPI)](https://github.com/ocpi/ocpi) which is defined and used by the [EVRoaming Foundation](https://evroaming.org). The focus of this protocol is a scalable, automated EV roaming setup between Charge Point Operators (EVSE Operators) and e-Mobility Service Providers. The focus of this protocol is communication within a **peer-to-peer** topology of CPOs, EMPs and other actors, but since v2.2 also roaming hubs are defined.

## Implementation Details and Differences

The following desribes differences of this implementation to the official protocol specification.

Most changes are intended to simplify the daily operations business or to support additional concepts/methods like the *European General Data Protection Regulation (GDPR)*, the *German Calibration Law (Eichrecht)*, the *Alternative Fuels Infrastructure Regulation (AFIR)* or the *Public Charge Point Regulations 2023* within the United Kingdom.

- The [OCPI v2.1.x ](WWCP_OCPIv2.1.1/README.md) focuses on simple *"one peer connected to one other peer"*-topologies, but besides its simplicity the specification has unfortunatelly some design flaws. This implementation provides extentions and work-arounds for most of these issues to simplify the daily operations business, high availability or to support additional concepts/methods like *European General Data Protection Regulation (GDPR)* and the *German Calibration Law (Eichrecht)*.

- The [OCPI v2.2.x ](WWCP_OCPIv2.2.1/README.md) extends its focus on many *"CPOs/EMPs on one peer"*-topologies and introduces a *"hub*"-concept like OICP. This specification is unfortunatelly more a hack, has many design flaws and security issues. This implementation provides extentions and work-arounds for most of these issues to simplify the daily operations business, high availability or to support additional concepts/methods like *European General Data Protection Regulation (GDPR)* and the *German Calibration Law (Eichrecht)*.

- The [OCPI v2.3](WWCP_OCPIv2.3/README.md) is a simple data structures extension to v2.2.1. So the same problems exist and are still unsolved. This implementation provides extentions and work-arounds for most of these issues to simplify the daily operations business, high availability or to support additional concepts/methods like *European General Data Protection Regulation (GDPR)*, the *German Calibration Law (Eichrecht)*, *EU Alternative Fuels Infrastructure Regulation (AFIR)* and the *UK's Public Charge Point Regulations 2023*.

- The [OCPI v3.0](WWCP_OCPIv2.0/README.md) is very different to the v2.x versions of the protocol specification, closer to WWCP, but still has many (new) design flaws and security issues. This implementation provides extentions and work-arounds for most of these issues to simplify the daily operations business, high availability or to support additional concepts/methods like *European General Data Protection Regulation (GDPR)*, the *German Calibration Law (Eichrecht)*, *EU Alternative Fuels Infrastructure Regulation (AFIR)* and the *UK's Public Charge Point Regulations 2023*.    

**Note:** OCPI v3.0 has not been officially released yet. The latest draft, *"OCPI v3.0-2 review2, 2024-02-22"*, still contains numerous issues. As a result, this implementation should be considered a technology preview rather than a production-ready solution.

## Open Data by Default

This OCPI implementation includes an optional feature to enable anonymous, unauthenticated access to the VERSIONS, LOCATIONS, and TARIFFS endpoints via a simple WebAPI. By activating this feature, you can ensure compliance with regulatory requirements such as the *EU Alternative Fuels Infrastructure Regulation (AFIR)* and the *UK's Public Charge Point Regulations 2023*.

This capability facilitates the provision of open and transparent access to essential data about charging station availability, locations, and pricing, aligning with the mandates for publicly accessible information to promote interoperability and user convenience. Additionally, this feature simplifies integration with third-party platforms and services that rely on open access to charging infrastructure data, supporting a seamless user experience while adhering to legal standards.

### Your participation

This software is free and Open Source under [**Apache 2.0 license**](LICENSE).

We appreciate your participation in this ongoing project, and your help to

improve it and the e-mobility ICT in general. If you find bugs, want to request

a feature or send us a pull request, feel free to use the normal GitHub

features to do so. For this please read the Contributor License Agreement

carefully and send us a signed copy or use a similar free and open license.