Skip to content
Documentation Menu

TC_079_CS — Get Security Log

TC_079_CS — Get Security Log

Source: OCPP 1.6 — Compliancy Testing Tool — Test Case Document (Trial 2025-06, Draft). System Under Test: Charge Point, page 102.

Identification

FieldValue
Test case nameGet Security Log
Test case IdTC_079_CS
System under testCharge Point

Description

The Charge Point uploads a security log to a specified location based on a request of the Central System.

Purpose

To check whether the Charge Point can upload its security log.

Prerequisite(s)

The Charge Point supports a security profile.

Before (Preparations)

Configuration State(s):

  • N/a

Memory State(s):

  • N/a

Reusable State(s):

  • N/a

Scenario Detail(s)

Charge Point (SUT)Central System (Tool)
2. The Charge Point responds with a GetLog.conf.1. The Central System sends a GetLog.req.
[The Charge Point starts uploading the security log.]; 3. The Charge Point sends a LogStatusNotification.req.4. The Central System responds with a LogStatusNotification.conf.
[The Charge Point has finished uploading the security log.]; 5. The Charge Point sends a LogStatusNotification.req.6. The Central System responds with a LogStatusNotification.conf.

Tool validation(s)

Charge Point side:

Step 2:

(Message: GetLog.conf) The status is Accepted

Step 3:

(Message: LogStatusNotification.req) The status is Uploading requestIdSame Id as the GetLog.req

Step 5:

(Message: LogStatusNotification.req) The status is Uploaded requestIdSame Id as the GetLog.req

Central System side:

Step 1:

(Message: GetLog.req) The log.remoteLocation is <Configured log location> The logType is SecurityLog

Expected result(s) / behaviour

Charge Point side:

The Charge Point has uploaded the security log to the log.remoteLocation that was sent in step 1.

Central System side:

  • N/a