TC_N_26_CS — Retrieve Log Information - Diagnostics Log - Upload failed
TC_N_26_CS — Retrieve Log Information - Diagnostics Log - Upload failed
Source: OCPP 2.0.1 Part 6 — Test Cases (Core & Advanced Security, FINAL, 2023-06-30) — Functional block N. Diagnostics, page 286.
Identification
| Field | Value |
|---|---|
| Test case name | Retrieve Log Information - Diagnostics Log - Upload failed |
| Test case Id | TC_N_26_CS |
| Use case Id(s) | N01 |
| Requirement(s) | N01.FR.01, N01.FR.02, N01.FR.04, N01.FR.07, N01.FR.08, N01.FR.10, N01.FR.13 |
| System under test | Charging Station |
| Functional block | N. Diagnostics |
Description
This test case covers the functionality of getting log information from a Charging Station. The CSMS can request a Charging Station to upload a file with log information to a given location (URL). The format of this log file is not prescribed. The Charging Station unsuccessfully uploads a log file and gives information about the status of the upload by sending status notifications to the CSMS.
Purpose
To verify if the Charging Station is able to correctly communicate with the CSMS after failing to upload a log as described at the OCPP specification.
Prerequisite(s)
- Charging Station has log information available.
Before (Preparations)
Configuration State:
- N/a
Memory State:
- Charging Station has log information available.
Reusable State(s):
- N/a
Main (Test scenario)
| Charging Station | CSMS |
|---|---|
| 2. The Charging Station responds with a GetLogResponse | 1. The OCTT sends a GetLogRequest with; - logType DiagnosticsLog; - retries 3; - retryInterval <Configured retryInterval> |
| 3. The Charging Station sends a LogStatusNotificationRequest | 4. The OCTT responds with a LogStatusNotificationResponse |
| 5. The Charging Station sends a LogStatusNotificationRequest | 6. The OCTT responds with a LogStatusNotificationResponse |
| Note(s):; - Steps 3 & 4 are optional after the first attempt.; - The Charging Station will perform step (3,) 5, three times with <Configured retryInterval> seconds in between. |
Tool validations
Step 1:
Message GetLogResponse
- status Accepted
Step 3:
Message LogStatusNotificationRequest
- status Uploading
- requestId Same Id as the GetLogRequest
Step 5:
Message LogStatusNotificationRequest
- status UploadFailure
- requestId Same Id as the GetLogRequest OR Message LogStatusNotificationRequest
- status BadMessage
- requestId Same Id as the GetLogRequest OR Message LogStatusNotificationRequest
- status PermissionDenied
- requestId Same Id as the GetLogRequest OR Message LogStatusNotificationRequest
- status NotSupportedOperation
- requestId Same Id as the GetLogRequest
- The time between the first LogStatusNotificationRequest Uploading and the last LogStatusNotificationRequest UploadFailure/BadMessage/PermissionDenied/NotSupportedOperation equals (3 * <Configured retryInterval>)
Post scenario validations
- N/a