Skip to content
Documentation Menu

TC_B_13_CS — Get Base Report - FullInventory

TC_B_13_CS — Get Base Report - FullInventory

Source: OCPP 2.0.1 Part 6 — Test Cases (Core & Advanced Security, FINAL, 2023-06-30) — Functional block B. Provisioning, page 49.

Identification

FieldValue
Test case nameGet Base Report - FullInventory
Test case IdTC_B_13_CS
Use case Id(s)B07
Requirement(s)B07.FR.01, B07.FR.03, B07.FR.04, B07.FR.08, B07.FR.10, B07.FR.12
System under testCharging Station
Functional blockB. Provisioning

Description

CSMS requests a FullInventory base report.

Purpose

To test that Charging Station supports the FullInventory base report.

Prerequisite(s)

N/A

Before (Preparations)

Configuration State:

  • N/a

Memory State:

  • N/a

Reusable State(s):

  • N/a

Main (Test scenario)

Charging StationCSMS
2. Charging Station responds with: GetBaseReportResponse1. OCTT sends GetBaseReportRequest with:; - requestId = <Generated requestId>; - reportBase = FullInventory
3. Charging Station responds with: NotifyReportRequest4. OCTT sends NotifyReportResponse
Step 3 and 4 are repeated as often as needed to report all configuration variables.

Tool validations

Step 2:

Message: GetBaseReportResponse

  • status = Accepted
  • statusInfo is absent or statusInfo.reasonCode = "NoError"

Step 3:

Message: NotifyReportRequest

  • requestId = <Generated requestId>
  • generatedAt = <timestamp at charging station>
  • seqNo = 0 - if variableCharacteristics.dataType = OptionList, SequenceList or MemberList then valuesList must be provided. while tbc = true

Post scenario validations

Check for all received variables:

  • variableCharacteristics are present Validate that as a minimum the required variables mentioned in section "Charging Infrastructure Related" are reported as well as the required variables in section "Referenced Components and Variables", that are relevant to each functional block that has been implemented.