【学习路线】
Part 0 – 快速了解 2.0.1 新特性
Part 1 – 架构 / 拓扑 / 设备模型（宏观）
Part 4 – JSON over WebSockets（实现基础）
Part 5/6 – 认证与测试（明确标准）
Part 2/3 – 消息手册（附录、规范） / Schemas（按需查阅使用）
【第一部分笔记】
1、基础信息
OCPP（开放充电点协议）是一个充电桩与充电管理系统（CSMS）通信事实标准，免费无授权壁垒。
传输2.0.1仅支持OCPP-J（Json+WebSocket），不再支持SOAP。适配充电桩受限硬件。
2、核心术语
CSMS：充电桩管理系统，负责设备管理、用户授权
EVSE：电动汽车供电设备，充电桩独立供电单元
CSO：充电桩运营商
EMS：能源管理系统，本地负荷与能源调度
3、16大功能模块
-
Security 安全
- OCPP 1.6：仅有简单密码认证
- 2.0.1：全新升级，3 级安全配置、证书管理、安全日志、安全事件
-
Provisioning 配置
- OCPP 1.6：只有简单启动、重置、基础配置
- 2.0.1：全新增强，资产上报、变量读写、设备监控、换 CSMS
-
Authorization 授权
- OCPP 1.6：主要支持 RFID 刷卡
- 2.0.1：大幅扩展，新增 PIN、银行卡、即插即充、启动按钮等
-
Local Authorization List 本地授权列表
- OCPP 1.6：已有本地白名单、离线授权
- 2.0.1：继承功能，小幅优化，逻辑基本不变
-
Transactions 交易
- OCPP 1.6：Start/StopTransaction 多消息分开
- 2.0.1：完全重构，统一用 TransactionEvent
-
Remote Control 远程控制
- OCPP 1.6：已有远程启动、远程停止、解锁枪
- 2.0.1：继承功能，小幅优化，新增 ISO15118 远程停止
-
Availability 可用性
- OCPP 1.6：已有状态上报、心跳、设置可用 / 不可用
- 2.0.1：继承功能，小幅优化，逻辑保持一致
-
Reservation 预约
- OCPP 1.6：已有充电桩预约、取消预约
- 2.0.1：继承功能，无重大变动
-
Tariff and Cost 费率
- OCPP 1.6：没有费率显示功能
- 2.0.1：全新功能
-
Metering 计量
- OCPP 1.6：已有定时上报电压 / 电流 / 电量
- 2.0.1：继承功能，结构优化，整合进 TransactionEvent
-
Smart Charging 智能充电
- OCPP 1.6：已有基础充电配置、负荷管理
- 2.0.1：大幅升级，支持 EMS、本地控制器、ISO15118
-
Firmware Management 固件管理
- OCPP 1.6：已有固件升级
- 2.0.1：继承功能，安全升级，支持安全验签升级
-
Certificate Management 证书管理
- OCPP 1.6：没有证书管理
- 2.0.1：全新功能
-
Diagnostics 诊断
- OCPP 1.6：只有简单日志上传
- 2.0.1：全新增强，监控、告警、变量上报
-
Display Message 屏显消息
- OCPP 1.6：没有远程屏显消息
- 2.0.1：全新功能
-
Data Transfer 数据透传
- OCPP 1.6：已有自定义扩展透传
- 2.0.1：继承功能，完全不变
4、基础实现必备消息
- 启动：BootNotification
- 配置：SetVariables / GetVariables
- 重置：Reset
- 授权：Authorize
- 交易 / 计量：TransactionEvent
- 状态：ChangeAvailability / StatusNotification
- 事件：NotifyEvent
- 透传：DataTransfer（至少支持拒绝）
5、授权方式补充说明
| 授权方式 | 通俗叫法 | 怎么用 | 特点 |
|---|---|---|---|
| RFID | 刷卡充电 | 刷充电卡 / 钥匙扣 | 传统、稳定、离线可用 |
| PIN 码 | 密码充电 | 充电桩输 4-6 位数字 | 不用卡，好记 |
| ISO 15118 EIM | 外部认证 | 车机认证 / APP 间接授权 | 车网互动标准 |
| Plug & Charge | 即插即充 | 插枪自动充 | 最方便、安全等级高 |
| 银行卡 / 支付终端 | 刷卡支付充 | 充电桩刷银行卡 | 直接支付 + 授权 |
| Local Id | 本地账号 | 运营商本地账号 | 离线也能用 |
| Contract Certificate | 证书认证 | 车辆数字证书 | 高安全、官方合规 |
| 启动按钮 | 一键启动 | 按桩上按钮开始 | 简单、公共桩常用 |
下面是用ai翻译的Part0，参考协议的连接路径替换成了可见的中文版本路径
第一部分：介绍/总览
原文翻译
OCPP 2.0.1 Part 0 – Introduction
Edition 4, 2025-12-03
第 1 页 (Page 1)
原文：
0CPP 2.0.1 Part 0 - Introduction Edition 4, 2025-12-03
译文：
OCPP 2.0.1 第 0 部分 - 引言 第 4 版，2025 年 12 月 3 日
第 2 页 (Page 2)
原文：
Introduction. 3
1.1. OCPP version 2.0.1. 3
1.2. Terms and abbreviations. 3
1.3. References. 4New functionalities in OCPP 2.0.1 5
2.1. Device Management. 5
2.2. Improvements for better handling of large amounts of transactions. 5
2.3. Improvements regarding cyber security. 5
2.4. Extended Smart Charging. 5
2.5. Support for ISO 15118. 6
2.6. Improvements for customer experience. 6
2.7. Transport Protocols: OCPP-J Improvements. 6
2.8. Minor changes/extensions. 7OCPP 2.0.1 Documentation Structure. 8
3.1. Overview of Specification Parts. 8
3.2. Functional Blocks. 9
3.3. All Functional Blocks and use cases. 10Basic implementation of OCPP 2.0.1. 13
译文：
引言 ................................ 3
1.1. OCPP 2.0.1 版本 ................. 3
1.2. 术语与缩写 ...................... 3
1.3. 参考文献 ........................ 4OCPP 2.0.1 中的新功能 .............. 5
2.1. 设备管理 ........................ 5
2.2. 针对大量交易处理的改进 ........... 5
2.3. 网络安全方面的改进 ............... 5
2.4. 扩展的智能充电 ................... 5
2.5. 对 ISO 15118 的支持 .............. 6
2.6. 客户体验的改进 ................... 6
2.7. 传输协议：OCPP-J 的改进 .......... 6
2.8. 小的变更/扩展 .................... 7OCPP 2.0.1 文档结构 ................ 8
3.1. 规范各部分概述 ................... 8
3.2. 功能块 .......................... 9
3.3. 所有功能块与用例 ................ 10OCPP 2.0.1 的基本实现 .............. 13
第 3 页 (Page 3)
原文：
2025-12-03
Disclaimer
Copyright © 2010 - 2025 Open Charge Alliance. All rights reserved.
This document is made available under the *Creative Commons Attribution-NoDerivatives 4.0 International Public License* (https://creativecommons.org/licenses/by-nd/4.0/legalcode).
译文：
2025-12-03
免责声明
版权所有 © 2010 - 2025 开放充电联盟。保留所有权利。
本文档根据《知识共享署名-禁止演绎 4.0 国际公共许可协议》提供 (https://creativecommons.org/licenses/by-nd/4.0/legalcode)。
第 4 页 (Page 4)
原文：
2025-11 have been merged into this version of the specification.
Version Date Description 2.0.1 Edition 4 2025-12-03 OCPP 2.0.1 Edition 4. All errata from OCPP 2.0.1 Part 0 until and including Errata 2025-11 have been merged into this version of the specification. 2.0.1 Edition 3 2024-05-06 OCPP 2.0.1 Edition 3. All errata from OCPP 2.0.1 Part 0 until and including Errata 2024-04 have been merged into this version of the specification. 2.0.1 2020-03-31 Final version of OCPP 2.0.1 2.0 2018-04-11 OCPP 2.0 April 2018
First release of this Introduction document
译文：
2025-11 的内容已合并到本版规范中。
版本 日期 描述 2.0.1 第 4 版 2025-12-03 OCPP 2.0.1 第 4 版。自 OCPP 2.0.1 第 0 部分起至并包括 2025-11 版勘误表的所有勘误，均已合并到本版规范中。 2.0.1 第 3 版 2024-05-06 OCPP 2.0.1 第 3 版。自 OCPP 2.0.1 第 0 部分起至并包括 2024-04 版勘误表的所有勘误，均已合并到本版规范中。 2.0.1 2020-03-31 OCPP 2.0.1 最终版本 2.0 2018-04-11 OCPP 2.0 2018 年 4 月版
本引言文档的首次发布
第 5 页 (Page 5)
原文：
Chapter 1. Introduction
Electric Vehicles (EVs) are becoming the new standard for mobility all over the world. This development is only possible with a good coverage of Charging Stations. To advance the roll out of charging infrastructure, open communication standards play a key role: to enable switching from charging network without necessarily replacing all the Charging Stations, to encourage innovation and cost effectiveness and to allow many and diverse players participate in this new industry.
Additionally, the EV charging infrastructure is part of the Smart Grid, a larger and still evolving ecosystem of actors, devices and protocols. In this Smart Grid ecosystem, open communication standards are key enablers for bidirectional power flows, real time information exchange, demand control and eMobility services.
The Open Charge Point Protocol (OCPP) is the industry-supported de facto standard for communication between a Charging Station and a Charging Station Management System (CSMS) and is designed to accommodate any type of charging technique. OCPP is an open standard with no cost or licensing barriers for adoption.
1.1. OCPP version 2.0.1
This specification defines version 2.0.1 of OCPP.
After the release of OCPP 2.0, some issues were found in OCPP 2.0. Some of these issues could not be fixed issuing errata to the specification text only, as has been done with OCPP 1.6, but required changes to the protocol's machine-readable schema definition files that cannot be backward compatible.
To prevent confusion in the market and possible interoperability issues in the field, OCA has decided to name this version: 2.0.1. OCPP 2.0.1 contains fixes for all the known issues, to date, not only the fixes to the messages.
This version replaces OCPP 2.0. OCA advises implementers of OCPP to no longer implement OCPP 2.0 and only use version 2.0.1 going forward.
Any mentions of "OCPP 2.0" refers to revision 2.0.1 unless specifically stated otherwise.
译文：
第 1 章 引言
电动汽车 (EV) 正成为全球出行的新标准。这一发展只有通过良好的充电桩覆盖才能实现。为了推进充电基础设施的部署，开放通信标准发挥着关键作用：它使得运营商可以在不必更换所有充电桩的情况下切换充电网络，促进创新和成本效益，并允许各种不同的参与者进入这个新兴行业。
此外，电动汽车充电基础设施是智能电网的一部分，而智能电网是一个更大、仍在不断演进的由参与者、设备和协议组成的生态系统。在这个智能电网生态系统中，开放通信标准是实现双向电力流动（可实现车辆向电网反向送电）、实时信息交换、需求控制和电动出行服务的关键推动因素。
开放充电点协议 (OCPP) 是业界支持的、用于充电桩与充电桩管理系统 (CSMS) 之间通信的事实标准，并且被设计为能够适应任何类型的充电技术。OCPP 是一个开放标准，采用它无需任何成本或许可障碍。
1.1. OCPP 2.0.1 版本
本规范定义了 OCPP 的 2.0.1 版本。
在 OCPP 2.0 发布之后，发现了一些问题。其中一些问题无法像 OCPP 1.6 那样仅通过对规范文本发布勘误表来修复，而是需要对协议的机器可读模式定义文件进行更改，且这些更改不能向后兼容。
为了避免市场上的混淆以及现场可能出现的互操作性问题，OCA 决定将该版本命名为 2.0.1。OCPP 2.0.1 包含了迄今为止所有已知问题的修复，而不仅仅是对消息的修复。
本版本取代了 OCPP 2.0。OCA 建议 OCPP 的实现者不要再实现 OCPP 2.0，而应在未来只使用 2.0.1 版本。
除非特别说明，任何对 "OCPP 2.0" 的提及均指修订版 2.0.1。
原文：
1.2. Terms and abbreviations
This section contains the terminology and abbreviations that are used throughout this document.
1.2.1. Terms
Term Meaning Charging Station The Charging Station is the physical system where an EV can be charged. A Charging Station has one or more EVSEs. Charging Station Management System (CSMS) Charging Station Management System: manages Charging Stations and has the information for authorizing Users for using its Charging Stations. Electric Vehicle Supply Equipment (EVSE) EVSE is considered as an independently operated and managed part of the Charging Station that can deliver energy to one EV at a time. Energy Management System (EMS) In this document this is defined as a device that manages the local loads (consumption and production) based on local and/or contractual constraints and/or contractual incentives. It has additional inputs, such as sensors and controls from e.g. PV, battery storage. 1.2.2. Abbreviations
Term Meaning CSO Charging Station Operator CSMS Charging Station Management System EMS Energy Management System EV Electric Vehicle EVSE Electric Vehicle Supply Equipment RFID Radio-Frequency Identification
译文：
1.2. 术语与缩写
本节包含本文档中使用的术语和缩写。
1.2.1. 术语
术语 含义 充电桩 (Charging Station) 可以为电动汽车充电的物理系统。一个充电桩有一个或多个 EVSE。 充电桩管理系统 (CSMS) 负责对各类充电桩进行集中管理，并具备用户充电权限授权相关信息管理功能。 电动汽车供电设备 (EVSE) 被视为充电桩中独立运行和管理的一部分，一次只能为一辆电动汽车提供电能。 能源管理系统 (EMS) 一套管控本地负荷（用电消耗与能源产出）的设备系统，根据现场实际用电条件、用电合同限制以及电价激励政策规则进行负荷管理； 同时可以接入光伏、储能电池等设备的传感器信号和控制信号作为外部输入。
1.2.2. 缩写
术语 含义 CSO 充电桩运营商 CSMS 充电桩管理系统 EMS 能源管理系统 EV 电动汽车 EVSE 电动汽车供电设备 RFID 射频识别
第 6 页 (Page 6)
原文：
1.3. References
Table 1. References
Reference Description [IEC61851-1] IEC 61851-1 2017: EV conductive charging system - Part 1: General requirements. https://webstore.iec.ch/publication/33644 [IEC62559-2:2015] Definition of the templates for use cases, actor list and requirements list. https://webstore.iec.ch/publication/22349 [ISO15118-1] ISO 15118-1 specifies terms and definitions, general requirements and use cases as the basis for the other parts of ISO 15118. It provides a general overview and a common understanding of aspects influencing the charge process, payment and load leveling. https://webstore.iec.ch/publication/9272 [OCPP1.5] http://www.openchargealliance.org/downloads/ [OCPP1.6] http://www.openchargealliance.org/downloads/
译文：
1.3. 参考文献
表 1. 参考文献
参考文献 描述 [IEC61851-1] IEC 61851-1 2017: 电动汽车传导充电系统 - 第 1 部分：通用要求。（地址贴实际可看的了哦，官方地址英文的还收费）IEC 61851-1 2017 高清中文版 - 道客巴巴 [IEC62559-2:2015] 用例模板、参与者列表和需求列表的定义。GB_T 39260.2-2020 用例方法 第2部分：用例模板、参与方清单和需求清单的定义 - 道客巴巴 [ISO15118-1] ISO 15118-1 规定了术语和定义、通用要求以及作为 ISO 15118 其他部分基础的用例。它提供了对影响充电过程、支付和负荷调节等方面的总体概述和共同理解。（这份可能是机翻的术语那边有些看着有点怪）
[OCPP1.5] OCPP 1.5 规范下载链接 [OCPP1.6] OCPP 1.6 规范下载链接
第 7 页 (Page 7)
原文：
2. New functionalities in OCPP 2.0.1
2.1. Device Management
Device Management (also known as Device Model) is a long awaited feature especially welcomed by CSOs who manage a network of (complex) charging stations (from different vendors).
It provides the following functionality:
Inventory reporting
Improved error and state reporting
Improved configuration
Customizable Monitoring
This all should help CSOs to reduce the costs of operating a Charging Station network.
Charging Station Manufacturers are free to decide themselves how much details about a Charging Station they want to publish via Device Management: for example, they can decide what can be monitored, and what not.
译文：
2. OCPP 2.0.1 中的新功能
2.1. 设备管理
设备管理（也称为设备模型）是一个期待已久的功能，尤其受到管理（来自不同供应商的复杂）充电桩网络的 CSO 的欢迎。
它提供了以下功能：
资产清单报告
改进的错误和状态报告
改进的配置
可定制的监控
所有这些都应有助于 CSO 降低运营充电桩网络的成本。
充电桩制造商可以自行决定希望通过设备管理发布多少关于充电桩的细节：例如，他们可以决定什么可以被监控，什么不可以。
原文：
2.2. Improvements for better handling of large amounts of transactions
2.2.1. One message for all transaction related functionalities
With the growing of the EV charging market, the number of Charging Stations and transactions that the CSMS needs to manage also grows. The structure and method for reporting transaction is unified in OCPP 2.0. In OCPP 1.x, the reporting of transaction data is split over the messages StartTransaction, StopTransaction, MeterValue and StatusNotification. With the market progressing towards more enhanced scheduling, a need is born for more sophisticated handling of transaction data. All the StartTransaction, StopTransaction, and transaction related MeterValue and StatusNotification messages are replaced by 'TransactionEvent'. The StatusNotification message still exists, but only for non-transaction related status notifications about connector availability.
2.2.2. Data reduction
With the introduction of JSON over Websockets in OCPP 1.6 [OCPP1.6] a great reduction of mobile data cost can be achieved. With OCPP 2.0, support for WebSocket Compression is introduced, which reduces the amount of data even more.
译文：
2.2. 针对大量交易处理的改进
2.2.1. 一个消息涵盖所有交易相关功能
随着电动汽车充电市场的增长，CSMS 需要管理的充电桩和交易数量也在增长。交易报告的结构和方法在 OCPP 2.0 中得到了统一。在 OCPP 1.x 中，交易数据的报告被分散在 StartTransaction、StopTransaction、MeterValue 和 StatusNotification 消息中。随着市场向更强化调度方向发展，出现了对更复杂交易数据处理的需求。所有 StartTransaction、StopTransaction 以及与交易相关的 MeterValue 和 StatusNotification 消息都被 'TransactionEvent' 所取代。StatusNotification 消息仍然存在，但仅用于与交易无关的连接器可用性状态通知。
2.2.2. 数据缩减
随着 OCPP 1.6 中引入基于 WebSocket 的 JSON，移动数据成本得以大幅降低。在 OCPP 2.0 中，引入了对 WebSocket 压缩的支持，进一步减少了数据量。
原文：
2.3. Improvements regarding cyber security
The following improvements have been added to harden OCPP against cyber attacks:
Security profiles (3 levels) for Charging Station and/or CSMS authentication and Communication Security
Key management for Client-Side certificates
Secure firmware updates
Security event log
译文：
2.3. 网络安全方面的改进
增加了以下改进以增强 OCPP 抵御网络攻击的能力：
用于充电桩和/或 CSMS 认证及通信安全的安全配置文件（3 个级别）
客户端证书的密钥管理
安全的固件更新
安全事件日志
原文：
2.4. Extended Smart Charging
In OCPP 2.0.1 Smart Charging functionality has been extended (compared to OCPP 1.6 [OCPP1.6]) to support:
Direct Smart Charging inputs from an Energy Management System (EMS) to a Charging Station
Improved Smart Charging with a local controller
Support for integrated smart charging of the CSMS, Charging Station and EV (ISO15118-1).
译文：
2.4. 扩展的智能充电
在 OCPP 2.0.1 中，智能充电功能得到了扩展（与 OCPP 1.6 相比），以支持：
从能源管理系统 (EMS) 到充电桩的直接智能充电输入
通过本地控制器改进的智能充电
支持 CSMS、充电桩和电动汽车 (ISO 15118-1) 的集成智能充电。
第 8 页 (Page 8)
原文：
2.5. Support for ISO 15118
The ISO 15118 standard [ISO15118-1] is a newer protocol for EVSE to EV communication, compared to IEC 61851 [IEC61851-1]. ISO 15118 allows a lot of new features and more secure communication between EVSE and EV. OCPP 2.0.1 supports the ISO 15118 standard, the newly added features are:
Plug & Charge
Smart Charging including input from the EV
译文：
2.5. 对 ISO 15118 的支持
与 IEC 61851 相比，ISO 15118 标准是一种较新的 EVSE 与 EV 通信协议。ISO 15118 提供了许多新功能和更安全的 EVSE 与 EV 之间的通信。OCPP 2.0.1 支持 ISO 15118 标准，新增的功能包括：
即插即充 (Plug & Charge)
包含来自 EV 输入的智能充电
原文：
2.6. Improvements for customer experience
2.6.1. More authorization options
OCPP 1.x was designed (mainly) for Charging Stations that authorize an EV driver via an RFID card/token. If other authorization systems or a mix of systems are used, the CSMS needs to know what system is used for which authorization. OCPP 2.0.1 has been extended to support things like: 15118 Plug & Charge [ISO15118-1], Payment Terminals, local mechanical key, Smart-phones, etc.
2.6.2. Display Messages
This provides Charging Station Operators with the possibility to configure - from the CSMS - a message on a Charging Station to be displayed to EV drivers. Messages can be transaction related or global.
2.6.3. EV Driver preferred languages
To be able to show messages to an EV driver in a language the driver understands best, OCPP 2.0.1 provides the possibility to send the language preference of a driver to a Charging Station.
2.6.4. Tariff and Costs
OCPP 2.0.1 allows Charging Stations to show the applicable tariff/price before an EV driver starts charging, to show the running total cost during a charging transaction and/or to show the final total cost after the transaction is finished.
译文：
2.6. 客户体验的改进
2.6.1. 更多的授权选项
OCPP 1.x 主要为通过 RFID 卡/令牌授权 EV 驾驶员的充电桩而设计。如果使用其他授权系统或混合使用多种系统，CSMS 需要知道哪个系统用于哪项授权。OCPP 2.0.1 已扩展以支持：15118 即插即充、支付终端、本地机械钥匙、智能手机等。
2.6.2. 显示消息
这为充电桩运营商提供了从 CSMS 配置充电桩上向 EV 驾驶员显示消息的能力。消息可以是与交易相关的，也可以是全局性的。
2.6.3. EV 驾驶员首选语言
为了能够以驾驶员最理解的语言向其显示消息，OCPP 2.0.1 提供了将驾驶员的语言偏好发送到充电桩的功能。
2.6.4. 资费与费用
OCPP 2.0.1 允许充电桩在 EV 驾驶员开始充电前显示适用的资费/价格，在充电交易期间显示累计费用，和/或在交易结束后显示最终总费用。
原文：
2.7. Transport Protocols: OCPP-J Improvements
2.7.1. Simple Message routing
A description has been added how to create a simple solution for OCPP message routing in, for example, a Local Controller. This is defined in Part 4, Section 6: OCPP Routing.
2.7.2. No SOAP Support
OCPP 2.0.1 no longer supports SOAP as a transport protocol. This decision was taken by the OCA members, who believe that the protocol does no longer lend itself for constrained computing resources that many Charging Stations operate under. The verbosity of the protocol could lead to slower performance and requires a higher bandwidth, which, in many cases, leads to higher cellular costs. SOAP is also difficult to support when communication is via local site networking.
译文：
2.7. 传输协议：OCPP-J 的改进
2.7.1. 简单的消息路由
已添加了关于如何在例如本地控制器中为 OCPP 消息路由创建简单解决方案的描述。这在第 4 部分第 6 节 "OCPP 路由" 中定义。
2.7.2. 不再支持 SOAP
OCPP 2.0.1 不再支持 SOAP 作为传输协议。这一决定由 OCA 成员做出，他们认为该协议已不再适用于许多充电桩运行时所处的受限计算资源环境。该协议的冗长性可能导致较慢的性能，并需要更高的带宽，这在许多情况下会导致更高的蜂窝网络成本。当通过本地站点网络进行通信时，SOAP 也难以支持。
第 9 页 (Page 9)
原文：
2.8. Minor changes/extensions
2.8.1. Renamed messages
In the OCPP 1.x series, the names of all messages were kept unchanged for backward compatibility, even though some message names were found to be confusing or misleading in practice. In OCPP 2.0.1 message names have been changed, where appropriate, to improve clarity and understanding.
Example: RemoteStartTransaction.req: a lot of implementers thought it meant the Charging Station should start the transaction, but in fact it is a request to try to start a transaction. However, for example, if no cable is plugged in, no transaction can be started. Since the message was always intended to be a request, it has been changed to a more logical name: RequestStartTransactionRequest.
译文：
2.8. 小的变更/扩展
2.8.1. 消息重命名
在 OCPP 1.x 系列中，为了向后兼容，所有消息的名称都保持不变，尽管实际上发现某些消息名称令人困惑或产生误导。在 OCPP 2.0.1 中，消息名称在适当的地方进行了更改，以提高清晰度和理解性。
示例：RemoteStartTransaction.req：许多实现者认为它意味着充电桩应该开始交易，但实际上它是一个请求，尝试开始一个交易。然而，例如，如果没有插入电缆，则无法开始交易。由于该消息始终旨在作为一个请求，因此已更改为更符合逻辑的名称：RequestStartTransactionRequest。
原文：
2.8.2. TransactionId Identification & Message Sequencing
In OCPP 2.0, transaction identifiers are generated by the Charging Station, to facilitate offline charging sessions, in contrast to OCPP 1.x, where transaction identifiers were generated at the CSMS and sent to the Charging Station. In addition, all messages relating to a transaction are assigned incremental sequence numbering, to facilitate transaction data completeness checking at the CSMS.
2.8.3. Extended enumerations
Many enumerations have been extended to support more use cases, provide more options etc.
2.8.4. Offline Transaction Event Indication
Charging Stations can optionally indicate in transaction messages that a transaction event occurred while the Charging Station was Offline. This can assist a CSMS with the processing of transactions.
2.8.5. Personal message
Message that can be shown to the EV Driver and can be used for tariff information, user greetings and for indicating why a driver is not authorized to charge. When a driver uses an authorization method (RFID for example) and the CSMS does not authorize the driver to start charging, this field can thus contain additional reasons to provide the driver with a meaningful explanation why (s)he is not allowed to charge.
译文：
2.8.2. 交易标识符与消息序列号
在 OCPP 2.0 中，交易标识符由充电桩生成，以支持离线充电会话，这与 OCPP 1.x 不同——在 1.x 中交易标识符由 CSMS 生成并发送给充电桩。此外，与交易相关的所有消息都被分配了递增的序列号，以便于 CSMS 检查交易数据的完整性。
2.8.3. 扩展的枚举
许多枚举已被扩展以支持更多用例、提供更多选项等。
2.8.4. 离线交易事件指示
充电桩可以选择性地在交易消息中指示某个交易事件是发生在充电桩离线期间。这可以帮助 CSMS 处理交易。
2.8.5. 个人消息
可以显示给 EV 驾驶员的消息，可用于资费信息、用户问候以及指示驾驶员未被授权充电的原因。当驾驶员使用某种授权方式（例如 RFID）而 CSMS 未授权其开始充电时，该字段可以包含附加原因，向驾驶员提供有意义的解释，说明为什么他/她不被允许充电。
第 10 页 (Page 10)
原文：
3. OCPP 2.0.1 Documentation Structure
3.1. Overview of Specification Parts
The overall structure of the standard has been improved, making the new specification easier to read, implement and test.
For readability and implementation purposes, OCPP 2.0.1 is divided in seven parts.
Table 2. Parts
Part Title Part 0 Introduction (this document) Part 1 Architecture & Topology Part 2 Specification:
Use Cases and Requirements, Messages, Data Types and Referenced Components and Variables
Appendices:
Security Events, Standardized Units of Measure, Components and VariablesPart 3 Schemas Part 4 Implementation Guide JSON Part 5 Certification Profiles Part 6 Test Cases
译文：
3. OCPP 2.0.1 文档结构
3.1. 规范各部分概述
标准的整体结构得到了改进，使新规范更易于阅读、实现和测试。
为了便于阅读和实现，OCPP 2.0.1 被分为七个部分。
表 2. 各部分
部分 标题 第 0 部分 引言（本文档） 第 1 部分 架构与拓扑 第 2 部分 规范：
用例与需求、消息、数据类型以及引用的组件和变量
附录：
安全事件、标准化计量单位、组件和变量第 3 部分 模式定义 (Schemas) 第 4 部分 JSON 实现指南 第 5 部分 认证配置文件 第 6 部分 测试用例
原文：
In contrast to OCPP 1.6 [OCPP1.6], the OCPP 2.0.1 specification is written in a different structure, based on [IEC62559-2:2015]: "Use case methodology - Part 2: Definition of the template for use cases, actor list and requirements list".
Part 2, the specification, is divided into 'Functional Blocks'. These Functional Blocks contain use cases and requirements. Messages, Data Types and Referenced Components and Variables are described at the end of the document. The Appendices can be found in the separate document: Part 2 - Appendices.
译文：
与 OCPP 1.6 相比，OCPP 2.0.1 规范的编写采用了不同的结构，基于 [IEC62559-2:2015]《用例方法论 - 第 2 部分：用例、参与者列表和需求列表的模板定义》。
第 2 部分（规范）被划分为多个 "功能块"。这些功能块包含用例和需求。消息、数据类型以及引用的组件和变量在文档末尾描述。附录可以在单独的文档《第 2 部分 - 附录》中找到。
第 11 页 (Page 11)
原文：
3.2. Functional Blocks
OCPP 2.0.1 consists of the following Functional Blocks.
Table 3. Functional Blocks
Clause Functional Block Title Description A Security This Functional Block describes a security specification for the OCPP protocol. B Provisioning This Functional Block describes all the functionalities that help a CSO provision their Charging Stations, allowing them to be registered and accepted on their network and retrieving basic configuration information from these Charging Stations. C Authorization This Functional Block describes all the authorization related functionality: AuthorizeRequest message handling/behavior and Authorization Cache functionality. D Local Authorization List Management This Functional Block describes functionality for managing the Local Authorization List. E Transactions This Functional Block describes the basic OCPP Transaction related functionality for transactions that are started/stopped on the Charging Station. F Remote Control This Functional Block describes three types of use cases for remote control management from the CSMS: Remote Transaction Control, Unlocking a Connector and Remote Trigger. G Availability This functional Block describes the functionality of sending status notification messages. H Reservation This Functional Block describes the reservation functionality of a Charging Station. I Tariff and Cost This Functional Block provides tariff and cost information to an EV Driver, when a Charging Station is capable of showing this on a display. Before a driver starts charging tariff information needs to be given, detailed prices for all the components that make up the tariff plan applicable to this driver at this Charging Station. During charging the EV Driver needs to be shown the running total cost, updated at a regular, fitting interval. When the EV Driver stops charging the total cost of this transaction needs to be shown. J Metering This Functional Block describes the functionality for sending meter values, on a periodic sampling and/or clock-aligned timing basis. K Smart Charging This Functional Block describes all the functionality that enables the CSO (or indirectly a third party) to influence the charging current/power of a charging session, or set limits to the amount of power/current a Charging Station can offer to an EV. L Firmware Management This Functional Block describes the functionality that enables a CSO to update the firmware of a Charging Station. M Certificate Management This Functional Block provides the installation and update of certificates. N Diagnostics This Functional Block describes the functionality that enables a CSO to request and track the upload of a diagnostics file from a Charging Station, and to manage the monitoring of Charging Station data. O Display Message With the DisplayMessage feature OCPP enables a CSO to display a message on a Charging Station, that is not part of the firmware of the Charging Station. The CSO gets control over these messages: the CSO can set, retrieve (get), replace and clear messages. P Data Transfer This Functional Block describes the functionality that enables a party to add custom commands to OCPP, enabling custom extension to OCPP.
译文：
3.2. 功能块
OCPP 2.0.1 由以下功能块组成。
表 3. 功能块
条款 功能块名称 描述 A 安全 本功能块描述了 OCPP 协议的安全规范。 B 配置 本功能块描述了帮助 CSO 配置其充电桩的所有功能，使其能够在其网络上注册、被接受，并从这些充电桩获取基本配置信息。 C 授权 本功能块描述了所有与授权相关的功能：AuthorizeRequest 消息处理/行为以及授权缓存功能。 D 本地授权列表管理 本功能块描述了管理本地授权列表的功能。 E 交易 本功能块描述了与在充电桩上启动/停止的交易相关的基本 OCPP 交易功能。 F 远程控制 本功能块描述了来自 CSMS 的远程控制管理的三种用例：远程交易控制、解锁连接器和远程触发。 G 可用性 本功能块描述了发送状态通知消息的功能。 H 预约 本功能块描述了充电桩的预约功能。 I 资费与费用 本功能块在充电桩能够在显示屏上显示信息时，向 EV 驾驶员提供资费和费用信息。在驾驶员开始充电前需要给出资费信息，包括构成适用于该驾驶员在此充电桩的资费计划的所有组件的详细价格。在充电期间，需要向 EV 驾驶员显示累计费用，并以适当的规律间隔更新。当 EV 驾驶员停止充电时，需要显示本次交易的总费用。 J 计量 本功能块描述了基于周期性采样和/或时钟对齐定时发送电表读数的功能。 K 智能充电 本功能块描述了使 CSO（或间接地第三方）能够影响充电会话的充电电流/功率，或设置充电桩可向 EV 提供的功率/电流限制的所有功能。 L 固件管理 本功能块描述了使 CSO 能够更新充电桩固件的功能。 M 证书管理 本功能块提供了证书的安装和更新。 N 诊断 本功能块描述了使 CSO 能够请求和跟踪从充电桩上传诊断文件，以及管理充电桩数据监控的功能。 O 显示消息 通过 DisplayMessage 功能，OCPP 使 CSO 能够在充电桩上显示不属于充电桩固件的消息。CSO 获得对这些消息的控制权：CSO 可以设置、获取、替换和清除消息。 P 数据传输 本功能块描述了使一方能够向 OCPP 添加自定义命令的功能，从而实现对 OCPP 的自定义扩展。
第 12 页 (Page 12)
原文：
3.3. All Functional Blocks and use cases
The following table shows the full list of use cases supported by OCPP 2.0.1 and which use cases were already supported by OCPP 1.6 [OCPP1.6].
Clause Functional Block UC ID Use case name OCPP 1.6 New in OCPP 2.0.1 A Security A01 Update Charging Station Password for HTTP Basic Authentication ● A Security A02 Update Charging Station Certificate by request of CSMS ● A Security A03 Update Charging Station Certificate initiated by the Charging Station ● A Security A04 Security Event Notification ● B Provisioning B01 Cold Boot Charging Station ✓ B Provisioning B02 Cold Boot Charging Station - Pending ✓ B Provisioning B03 Cold Boot Charging Station - Rejected ✓ B Provisioning B04 Offline Behavior Idle Charging Station ✓ B Provisioning B05 Set Variables ✓ B Provisioning B06 Get Variables ✓ B Provisioning B07 Get Base Report ● B Provisioning B08 Get Custom Report ● B Provisioning B09 Setting a new NetworkConnectionProfile ● B Provisioning B10 Migrate to new CSMS ● B Provisioning B11 Reset - Without Ongoing Transaction ✓ B Provisioning B12 Reset - With Ongoing Transaction ✓ C Authorization C01 EV Driver Authorization using RFID ✓ C Authorization C02 Authorization using a start button ✓ C Authorization C03 Authorization using credit/debit card ● C Authorization C04 Authorization using PIN-code ✓ C Authorization C05 Authorization for CSMS initiated transactions ✓ C Authorization C06 Authorization using local id type ● C Authorization C07 Authorization using Contract Certificates ● C Authorization C08 Authorization at EVSE using ISO 15118 External Identification Means (EIM) ● C Authorization C09 Authorization by GroupId ● C Authorization C10 Store Authorization Data in the Authorization Cache ✓ C Authorization C11 Clear Authorization Data in Authorization Cache ✓ C Authorization C12 Start Transaction - Cached Id ✓ C Authorization C13 Offline Authorization through Local Authorization List ✓ C Authorization C14 Online Authorization through Local Authorization List ✓ C Authorization C15 Offline Authorization of unknown Id ● C Authorization C16 Stop Transaction with a Master Pass ● D LocalAuthorizationList D01 Send Local Authorization List ✓ D LocalAuthorizationList D02 Get Local List Version ✓ E Transactions E01 Start Transaction Options ✓ E Transactions E02 Start Transaction - Cable Plugin First ✓ E Transactions E03 Start Transaction - IdToken First ✓ E Transactions E04 Transaction started while Charging Station is offline ✓
译文：
3.3. 所有功能块与用例
下表显示了 OCPP 2.0.1 支持的完整用例列表，以及 OCPP 1.6 已经支持了哪些用例。
条款 功能块 UC ID 用例名称 OCPP 1.6 OCPP 2.0.1 新增 A 安全 A01 更新充电桩的 HTTP 基本认证密码 ● A 安全 A02 应 CSMS 请求更新充电桩证书 ● A 安全 A03 由充电桩主动发起的证书更新 ● A 安全 A04 安全事件通知 ● B 配置 B01 冷启动充电桩 ✓ B 配置 B02 冷启动充电桩 - 挂起 ✓ B 配置 B03 冷启动充电桩 - 被拒绝 ✓ B 配置 B04 空闲充电桩的离线行为 ✓ B 配置 B05 设置变量 ✓ B 配置 B06 获取变量 ✓ B 配置 B07 获取基础报告 ● B 配置 B08 获取自定义报告 ● B 配置 B09 设置新的网络连接配置文件 ● B 配置 B10 迁移到新的 CSMS ● B 配置 B11 重置 - 无进行中的交易 ✓ B 配置 B12 重置 - 有进行中的交易 ✓ C 授权 C01 使用 RFID 的 EV 驾驶员授权 ✓ C 授权 C02 使用启动按钮授权 ✓ C 授权 C03 使用信用卡/借记卡授权 ● C 授权 C04 使用 PIN 码授权 ✓ C 授权 C05 CSMS 发起交易的授权 ✓ C 授权 C06 使用本地 ID 类型授权 ● C 授权 C07 使用合同证书授权 ● C 授权 C08 在 EVSE 上使用 ISO 15118 外部识别方式 (EIM) 授权 ● C 授权 C09 按组 ID 授权 ● C 授权 C10 在授权缓存中存储授权数据 ✓ C 授权 C11 清除授权缓存中的授权数据 ✓ C 授权 C12 启动交易 - 使用缓存的 ID ✓ C 授权 C13 通过本地授权列表进行离线授权 ✓ C 授权 C14 通过本地授权列表进行在线授权 ✓ C 授权 C15 未知 ID 的离线授权 ● C 授权 C16 使用主控密码停止交易 ● D 本地授权列表 D01 发送本地授权列表 ✓ D 本地授权列表 D02 获取本地列表版本 ✓ E 交易 E01 启动交易选项 ✓ E 交易 E02 启动交易 - 先插枪 ✓ E 交易 E03 启动交易 - 先出示 ID ✓ E 交易 E04 充电桩离线时启动的交易 ✓
第 13 页 (Page 13)
原文：
Clause Functional Block UC ID Use case name OCPP 1.6 New in OCPP 2.0.1 E Transactions E05 Start Transaction - Id not Accepted ✓ E Transactions E06 Stop Transaction Options ✓ E Transactions E07 Transaction locally stopped by IdToken ✓ E Transactions E08 Transaction stopped while Charging Station is offline ✓ E Transactions E09 When cable disconnected on EV-side: Stop Transaction ✓ E Transactions E10 When cable disconnected on EV-side: Suspend Transaction ✓ E Transactions E11 Connection Loss During Transaction ✓ E Transactions E12 Inform CSMS of an Offline Occurred Transaction ● E Transactions E13 Transaction related message not accepted by CSMS ● E Transactions E14 Check transaction status ● E Transactions E15 End of charging process ● F RemoteControl F01 Remote Start Transaction - Cable Plugin First ✓ F RemoteControl F02 Remote Start Transaction - Remote Start First ✓ F RemoteControl F03 Remote Stop Transaction ✓ F RemoteControl F04 Remote Stop ISO 15118 charging from CSMS ● F RemoteControl F05 Remotely Unlock Connector ✓ F RemoteControl F06 Trigger Message ✓ G Availability G01 Status Notification ✓ G Availability G02 Heartbeat ✓ G Availability G03 Change Availability EVSE ✓ G Availability G04 Change Availability Charging Station ✓ G Availability G05 Lock Failure ✓ H Reservation H01 Reservation ✓ H Reservation H02 Cancel Reservation ✓ H Reservation H03 Use a reserved EVSE ✓ H Reservation H04 Reservation Ended, not used ✓ I Tariff and Costs I01 Show EV Driver-specific tariff information ● I Tariff and Costs I02 Show EV Driver running total cost during charging ● I Tariff and Costs I03 Show EV Driver final total cost after charging ● I Tariff and Costs I04 Show fallback tariff information ● I Tariff and Costs I05 Show fallback total cost message ● I Tariff and Costs I06 Update Tariff Information During Transaction ● J Metering J01 Sending Meter Values not related to a transaction ✓ J Metering J02 Sending transaction related Meter Values ✓ J Metering J03 Charging Loop with metering information exchange ● K SmartCharging K01 SetChargingProfile ✓ K SmartCharging K02 Central Smart Charging ✓ K SmartCharging K03 Local Smart Charging ✓ K SmartCharging K04 Internal Load Balancing ✓ K SmartCharging K05 Remote Start Transaction with Charging Profile ✓ K SmartCharging K06 Offline Behavior Smart Charging During Transaction ● K SmartCharging K07 Offline Behavior Smart Charging at Start of Transaction ● K SmartCharging K08 Get Composite Schedule ●
译文：
条款 功能块 UC ID 用例名称 OCPP 1.6 OCPP 2.0.1 新增 E 交易 E05 启动交易 - ID 未被接受 ✓ E 交易 E06 停止交易选项 ✓ E 交易 E07 由 IdToken 在本地停止交易 ✓ E 交易 E08 充电桩离线时停止的交易 ✓ E 交易 E09 当 EV 侧断开电缆时：停止交易 ✓ E 交易 E10 当 EV 侧断开电缆时：暂停交易 ✓ E 交易 E11 交易期间连接丢失 ✓ E 交易 E12 告知 CSMS 离线期间发生的交易 ● E 交易 E13 与交易相关的消息未被 CSMS 接受 ● E 交易 E14 检查交易状态 ● E 交易 E15 充电过程结束 ● F 远程控制 F01 远程启动交易 - 先插枪 ✓ F 远程控制 F02 远程启动交易 - 先远程启动 ✓ F 远程控制 F03 远程停止交易 ✓ F 远程控制 F04 从 CSMS 远程停止 ISO 15118 充电 ● F 远程控制 F05 远程解锁连接器 ✓ F 远程控制 F06 触发消息 ✓ G 可用性 G01 状态通知 ✓ G 可用性 G02 心跳 ✓ G 可用性 G03 更改 EVSE 可用性 ✓ G 可用性 G04 更改充电桩可用性 ✓ G 可用性 G05 锁故障 ✓ H 预约 H01 预约 ✓ H 预约 H02 取消预约 ✓ H 预约 H03 使用已预约的 EVSE ✓ H 预约 H04 预约结束，未被使用 ✓ I 资费与费用 I01 显示 EV 驾驶员特定的资费信息 ● I 资费与费用 I02 充电期间显示 EV 驾驶员的累计费用 ● I 资费与费用 I03 充电后显示 EV 驾驶员的最终总费用 ● I 资费与费用 I04 显示备用资费信息 ● I 资费与费用 I05 显示备用总费用消息 ● I 资费与费用 I06 交易期间更新资费信息 ● J 计量 J01 发送与交易无关的电表读数 ✓ J 计量 J02 发送与交易相关的电表读数 ✓ J 计量 J03 带计量信息交换的充电循环 ● K 智能充电 K01 设置充电配置文件 ✓ K 智能充电 K02 中央智能充电 ✓ K 智能充电 K03 本地智能充电 ✓ K 智能充电 K04 内部负载均衡 ✓ K 智能充电 K05 带充电配置文件的远程启动交易 ✓ K 智能充电 K06 交易期间的离线智能充电行为 ● K 智能充电 K07 交易开始时的离线智能充电行为 ● K 智能充电 K08 获取复合调度表 ●
第 14 页 (Page 14)
原文：
Clause Functional Block UC ID Use case name OCPP 1.6 New in OCPP 2.0.1 K SmartCharging K09 Get Charging Profiles ● K SmartCharging K10 Clear Charging Profile ● K SmartCharging K11 Set / Update External Charging Limit With Ongoing Transaction ● K SmartCharging K12 Set / Update External Charging Limit Without Ongoing Transaction ● K SmartCharging K13 Reset / release external charging limit ● K SmartCharging K14 External Charging Limit with Local Controller ● K SmartCharging K15 Charging with load leveling based on High Level Communication ● K SmartCharging K16 Optimized charging with scheduling to the CSMS ● K SmartCharging K17 Renegotiating a Charging Schedule ● L Firmware Management L01 Secure Firmware Update ● L Firmware Management L02 Non-Secure Firmware Update ✓ L Firmware Management L03 Publish Firmware file on Local Controller ● L Firmware Management L04 Unpublish Firmware file on Local Controller ● M Certificate Management M01 Certificate Installation EV ● M Certificate Management M02 Certificate Update EV ● M Certificate Management M03 Retrieve list of available certificates from a Charging Station ● M Certificate Management M04 Delete a specific certificate from a Charging Station ● M Certificate Management M05 Install CA certificate in a Charging Station ● M Certificate Management M06 Get Charging Station Certificate status ● N Diagnostics N01 Retrieve Log Information ✓ N Diagnostics N02 Get Monitoring report ● N Diagnostics N03 Set Monitoring Base ● N Diagnostics N04 Set Variable Monitoring ● N Diagnostics N05 Set Monitoring Level ● N Diagnostics N06 Clear / Remove Monitoring ● N Diagnostics N07 Alert Event ● N Diagnostics N08 Periodic Event ● N Diagnostics N09 Get Customer Information ● N Diagnostics N10 Clear Customer Information ● O Display Message O01 Set DisplayMessage ● O Display Message O02 Set DisplayMessage for Transaction ● O Display Message O03 Get All DisplayMessages ● O Display Message O04 Get Specific DisplayMessages ● O Display Message O05 Clear a DisplayMessage ● O Display Message O06 Replace DisplayMessage ● P DataTransfer P01 Data Transfer to the Charging Station ✓ P DataTransfer P02 Data Transfer to the CSMS ✓
OCPP is used in many different regions and for many different charging solutions. Not all functionalities offered by OCPP will be applicable to all implementations. Implementers can decide what specific functionalities apply to their charging solution. For interoperability purposes, the Open Charge Alliance introduces Certification Profiles in Part 5 of the specification.
译文：
条款 功能块 UC ID 用例名称 OCPP 1.6 OCPP 2.0.1 新增 K 智能充电 K09 获取充电配置文件 ● K 智能充电 K10 清除充电配置文件 ● K 智能充电 K11 在有进行中交易时设置/更新外部充电限制 ● K 智能充电 K12 在无进行中交易时设置/更新外部充电限制 ● K 智能充电 K13 重置/释放外部充电限制 ● K 智能充电 K14 带本地控制器的外部充电限制 ● K 智能充电 K15 基于高层通信的负荷调节充电 ● K 智能充电 K16 通过向 CSMS 调度实现优化充电 ● K 智能充电 K17 重新协商充电调度表 ● L 固件管理 L01 安全固件更新 ● L 固件管理 L02 非安全固件更新 ✓ L 固件管理 L03 在本地控制器上发布固件文件 ● L 固件管理 L04 在本地控制器上取消发布固件文件 ● M 证书管理 M01 EV 证书安装 ● M 证书管理 M02 EV 证书更新 ● M 证书管理 M03 从充电桩检索可用证书列表 ● M 证书管理 M04 从充电桩删除特定证书 ● M 证书管理 M05 在充电桩中安装 CA 证书 ● M 证书管理 M06 获取充电桩证书状态 ● N 诊断 N01 检索日志信息 ✓ N 诊断 N02 获取监控报告 ● N 诊断 N03 设置监控基准 ● N 诊断 N04 设置变量监控 ● N 诊断 N05 设置监控级别 ● N 诊断 N06 清除/移除监控 ● N 诊断 N07 告警事件 ● N 诊断 N08 周期性事件 ● N 诊断 N09 获取客户信息 ● N 诊断 N10 清除客户信息 ● O 显示消息 O01 设置显示消息 ● O 显示消息 O02 为交易设置显示消息 ● O 显示消息 O03 获取所有显示消息 ● O 显示消息 O04 获取特定显示消息 ● O 显示消息 O05 清除显示消息 ● O 显示消息 O06 替换显示消息 ● P 数据传输 P01 向充电桩传输数据 ✓ P 数据传输 P02 向 CSMS 传输数据 ✓
OCPP 被用于许多不同的地区和许多不同的充电解决方案。并非 OCPP 提供的所有功能都适用于所有实现。实现者可以决定哪些特定功能适用于他们的充电解决方案。出于互操作性的目的，开放充电联盟在规范的第 5 部分引入了认证配置文件。
第 15 页 (Page 15)
原文：
4. Basic implementation of OCPP 2.0.1
This section is informative.
The OCPP protocol describes a large number of use cases and messages, which are not all needed to implement a basic Charging Station or CSMS. The table below lists messages that are typically implemented to deliver basic functionality for an OCPP managed Charging Station. The purpose of this list is to guide developers that are new to OCPP.
Please note: this table does not define what needs to be done to become OCPP 2.0.1 "certified". The functionality that is to be implemented to become OCPP 2.0.1 certified is described in Part 5 of the specification, "Certification Profiles".
Table 4. OCPP 2.0.1 Basic Implementation
Functionality Use cases Messages Booting a Charging Station B01-B04 BootNotification Configuring a Charging Station B05-B07 SetVariables, GetVariables and GetReportBase (respond correctly to requests with reportBase = ConfigurationInventory, FullInventory and SummaryInventory). Resetting a Charging Station B11-B12 Reset Authorization options One of C01, C02 and C04 Authorize Transaction mechanism E01 (one of S1-S6), E02-E03, E05, E06 (one of S1-S6), E07-E08, One of E09-E10, E11-E13 TransactionEvent Availability G01, G03-G04 Only ChangeAvailability and StatusNotification. Monitoring Events G05, N07 A basic implementation of the NotifyEvent message to be used to report operational state changes and problem/error conditions of the Charging Station, e.g. for Lock Failure. Also used for reporting built-in monitoring events. Sending transaction related Meter values J02 TransactionEvent DataTransfer P01-P02 Any OCPP implementations should at least be able to reject any request for DataTransfer if no (special) functionality is implemented. NOTE: Please also refer to the section on Minimum Device Model in part 1.
译文：
4. OCPP 2.0.1 的基本实现
本章节为参考性信息。
OCPP 协议描述了大量的用例和消息，但实现一个基本的充电桩或 CSMS 并不需要全部。下表列出了通常为实现一个受 OCPP 管理的充电桩的基本功能而需要实现的消息。此列表的目的是指导刚接触 OCPP 的开发者。
请注意：此表格并未定义成为 OCPP 2.0.1 "认证" 需要做什么。要成为 OCPP 2.0.1 认证所需实现的功能在规范的第 5 部分 "认证配置文件" 中描述。
表 4. OCPP 2.0.1 基本实现
功能 用例 消息 启动充电桩 B01-B04 BootNotification 配置充电桩 B05-B07 SetVariables, GetVariables 以及 GetReportBase（对带有 reportBase = ConfigurationInventory、FullInventory 和 SummaryInventory 的请求作出正确响应） 重置充电桩 B11-B12 Reset 授权选项 C01、C02 和 C04 中的一种 Authorize 交易机制 E01（S1-S6 之一）、E02-E03、E05、E06（S1-S6 之一）、E07-E08、E09-E10 之一、E11-E13 TransactionEvent 可用性 G01, G03-G04 仅 ChangeAvailability 和 StatusNotification 监控事件 G05, N07 NotifyEvent 消息的基本实现，用于报告充电桩的运行状态变化和问题/错误情况，例如锁故障。也用于报告内置监控事件。 发送与交易相关的电表读数 J02 TransactionEvent 数据传输 P01-P02 任何 OCPP 实现至少应该能够在没有实现（特定）功能的情况下拒绝任何 DataTransfer 请求。 注：另请参阅第 1 部分中关于最小设备模型的部分
扫一扫
5741
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
