데이터 시트
Decode CCS Charging Protocols
The Keysight SL1487A CCS Charging Protocol Trace Viewer (CPT) enables decoding of Combined Charging System (CCS) charging protocols and supports DIN 70121, ISO 15118-2/-20 for vehicle-to-grid (V2G) communication, but also other proprietary messages defined for the hardware abstraction layer (HAL). With the CPT and Wireshark, a packet analyzing tool, you can track the communication between electric vehicles (EV) and electric vehicle supply equipment (EVSE) easily and detailed.
CPT Decoder
Decode captured communication packets defined by the corresponding charging protocol with the CPT decoder.
The CPT decoder supports the following protocols.
Protocol |
Function |
Description |
HAL |
Internal Keysight configuration messages for the CCS hardware test adapter |
• IEC 61851-1:2017 Control Pilot (CP) configuration and event messages related to PWM signal characteristics • IEC 61851-1:2017 Proximity configuration and event messages |
V2G DIN 70121:2014 |
• SDP messages • EXI-encoded SupportAppProtocol messages • EXI-encoded V2G messages |
Message structure defined by XSD schema of DIN 70121:2014 norm |
V2G ISO 15118-2:2014 |
• SDP messages • EXI-encoded SupportAppProtocol messages • EXI-encoded V2G messages |
Message structure defined by XSD schema of ISO 15118-2:2014 norm |
V2G ISO 15118-20 |
• SDP messages • EXI-encoded V2G messages |
Message structure defined by XSD schema of ISO 15118-20:2022 norm |
Wireshark Plugin Protocol
In addition, the following included Wireshark plugin protocol, Transport Layer Security (TLS) Session Master Key, ensures a decrypted TLS communication.
TLS Session Master Key protocol function
• Rivest-Shamir-Adleman (RSA): 48 bytes for the premaster secret, encoded as 96 hexadecimal characters (removed in Network Security Services (NSS) 3.34)
• CLIENT_RANDOM: 48 bytes for the master secret, encoded as 96 hexadecimal characters (for Secure Sockets Layer (SSL) 3.0, TLS 1.0, 1.1, and 1.2)
• CLIENT_EARLY_TRAFFIC_SECRET: The hex-encoded early traffic secret for the client side (for TLS 1.3)
• CLIENT_HANDSHAKE_TRAFFIC_SECRET: The hex-encoded handshake traffic secret for the client side (for TLS 1.3)
• SERVER_HANDSHAKE_TRAFFIC_SECRET: The hex-encoded handshake traffic secret for the server side (for TLS 1.3)
• CLIENT_TRAFFIC_SECRET_0: The first hex-encoded application traffic secret for the client side (for TLS 1.3)
• SERVER_TRAFFIC_SECRET_0: The first hex-encoded application traffic secret for the server side (for TLS 1.3)
TLS Session Master Key protocol description
The TLS Session Master Key protocol reads the master key used for the TLS communication so that external programs can decrypt TLS connections. Analyze these packets with encrypted V2G communication. The session master key is sent after the handshake as a UDP packet. This is based on the “NSS Key Log Format”.
무엇을 찾고 있습니까?