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

[中文适用范围]： 本文件以抽象测试套件 (ATS) 的形式规定了被测系统 (SUT) 的一致性测试，该系统实现电动汽车或供电设备通信控制器（EVCC 或 SECC），支持基于 WLAN 的高级通信(HLC) 根据 ISO 15118-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.