ISO 15118-9:2022 道路车辆 车辆到电网通信接口 第9部分：无线通信的物理和数据链路层一致性试验

标准编号：ISO 15118-9:2022

中文名称：道路车辆 车辆到电网通信接口 第9部分：无线通信的物理和数据链路层一致性试验

英文名称：Road vehicles — Vehicle to grid communication interface — Part 9: Physical and data link layer conformance test for wireless communication

发布日期：2022-11

标准范围

ISO 15118-9:20 22本文件以抽象测试套件（ATS）的形式规定了被测系统（SUT）的一致性测试，该被测系统实现了电动汽车或供电设备通信控制器（EVCC或SECC），支持根据ISO 15118的基于WLAN的高层通信（HLC）？8并以ISO 15118-1为背景。这些符合性测试规定了SUT的能力和行为的测试，以及根据ISO 15118中规定的符合性要求检查观察到的内容？8并根据实施者陈述SUT实现的能力。ATS内的性能测试检查SUT的可观察性能是否符合ISO 15118中定义的静态一致性要求？8.ATS的性能测试尽可能彻底地检查ISO 15118中定义的所有动态一致性要求的实施情况？8并在SUT的能力范围内（见否下面）。对应于ATS描述测试架构。本文档中的抽象测试用例利用该测试体系结构进行描述，并以描述性表格格式为ISO/OSI物理层和数据链路层（第1层和第2层）指定。就覆盖范围而言，本文件仅涵盖ISO 15118中的规范性章节和要求？8.本文件可以另外参考参考标准（例如IEEE或工业联盟标准，如WiFi联盟）要求的特定测试，只要它们与根据ISO 15118的实施的一致性相关？8.但是，如果ISO 15118的一致性测试在技术上不是必需的，则明确不打算将本一致性规范的范围扩大到此类外部标准？8.此外，本文档中指定的一致性测试不包括对实现的性能、健壮性或可靠性的评估。它们不能提供关于抽象服务原语的物理实现、系统如何实现、它如何提供任何请求的服务以及协议实现的环境的判断。此外，本文档中定义的抽象测试用例仅考虑ISO 15118定义的通信协议和系统行为？8.不考虑EVSE和EV之间的功率流。请注意，实际的限制使得不可能定义一个详尽的测试套件，经济上的考虑会进一步限制测试。因此，本文档的目的是增加不同实现能够互通的可能性。这是通过借助于协议测试套件来验证它们来实现的，从而增加每个实现符合协议规范的置信度。然而，指定的协议测试套件不能保证符合规范，因为它检测错误而不是错误的缺失。因此，仅符合测试套件不能保证互通。相反，它给人一种信心，即一个实现具有所需的能力，并且它的行为在典型的通信实例中是一致的。

ISO 15118-9:2022 This document specifies conformance tests in the form of an abstract test suite (ATS) for a system under test (SUT) implementing an electric-vehicle or supply-equipment communication controller (EVCC or SECC) with support for WLAN-based high-level communication (HLC) according to ISO 15118？8 and against the background of ISO 15118-1. These conformance tests specify the testing of capabilities and behaviours of an SUT, as well as checking what is observed against the conformance requirements specified in ISO 15118？8 and against what the implementer states the SUT implementation's capabilities are.
The capability tests within the ATS check that the observable capabilities of the SUT are in accordance with the static conformance requirements defined in ISO 15118？8. The behaviour tests of the ATS examine an implementation as thoroughly as practical over the full range of dynamic conformance requirements defined in ISO 15118？8 and within the capabilities of the SUT (see NOTE below).
A test architecture is described in correspondence to the ATS. The abstract test cases in this document are described leveraging this test architecture and are specified in descriptive tabular format for the ISO/OSI physical and data link layers (layers 1 and 2).
In terms of coverage, this document only covers normative sections and requirements in ISO 15118？8. This document can additionally refer to specific tests for requirements on referenced standards (e.g. IEEE, or industry consortia standards, like WiFi Alliance) as long as they are relevant in terms of conformance for implementations according to ISO 15118？8. However, it is explicitly not intended to widen the scope of this conformance specification to such external standards, if it is not technically necessary for the purpose of conformance testing for ISO 15118？8. Furthermore, the conformance tests specified in this document do not include the assessment of performance nor robustness or reliability of an implementation. They cannot provide judgments on the physical realization of abstract service primitives, how a system is implemented, how it provides any requested service, nor the environment of the protocol implementation. Furthermore, the abstract test cases defined in this document only consider the communication protocol and the system's behaviour defined ISO 15118？8. The power flow between the EVSE and the EV is not considered.
NOTE Practical limitations make it impossible to define an exhaustive test suite, and economic considerations can restrict testing even further. Hence, the purpose of this document is to increase the probability that different implementations are able to interwork. This is achieved by verifying them by means of a protocol test suite, thereby increasing the confidence that each implementation conforms to the protocol specification. However, the specified protocol test suite cannot guarantee conformance to the specification since it detects errors rather than their absence. Thus, conformance to a test suite alone cannot guarantee interworking. Instead, it gives confidence that an implementation has the required capabilities and that its behaviour conforms consistently in representative instances of communication.

标准预览图