Skip to content
Documentation Menu

TC_019_CS — Retrieve configuration

TC_019_CS — Retrieve configuration

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

Identification

FieldValue
Test case nameRetrieve configuration
Test case IdTC_019_CS
System under testCharge Point

Description

The Central System is able to retrieve all available or specific configuration keys.

Purpose

To check whether the Charge Point has all required keys configured.

Prerequisite(s)

  • N/a

Before (Preparations)

Configuration State(s):

  • AuthorizationKey is <Configured AuthorizationKey> (If implemented)

Memory State(s):

  • N/a

Reusable State(s):

  • N/a

Scenario Detail(s)

Charge Point (SUT)Central System (Tool)
4. The Charge Point responds with a GetConfiguration.conf.3. The Central Systems sends a GetConfiguration.req message to the Charge Point.
6. The Charge Point responds with a GetConfiguration.conf.5. The Central Systems sends a GetConfiguration.req message to the Charge Point.
8. The Charge Point responds with a GetConfiguration.conf.7. The Central Systems sends a GetConfiguration.req message to the Charge Point.
Test case nameRetrieve configuration
Tool validation(s)* Step 2:; (Message: GetConfiguration.conf) unknownKey list is <Empty> configurationKey.key should be SupportedFeatureProfiles configurationKey.value should contain <A comma- separated list in which 'Core' is required and optionally contains one or more of the other profiles; FirmwareManagement, LocalAuthListManagement, ResAervation, SmartCharging, RemoteTrigger.>; * Step 4:; (Message: GetConfiguration.conf); - Contains at least all required keys from the supported profiles from step 2.; - Check if accessibility contains the correct value. Core: RConfiguration Key / accessibility AuthorizeRemoteTxRequests / R OR RW ClockAlignedDataInterval / RW ConnectionTimeOut / RW ConnectorPhaseRotation / RW GetConfigurationMaxKeys / R HeartbeatInterval / RW LocalAuthorizeOffline / RW LocalPreAuthorize / RW MeterValuesAlignedData / RW MeterValuesSampledData / RW MeterValueSampleInterval / RW NumberOfConnectors / R ResetRetries / RW StopTransactionOnInvalidId / RW StopTxnAlignedData / RW StopTxnSampledData / RW SupportedFeatureProfiles / R TransactionMessageAttempts / RW TransactionMessageRetryInterval / RW UnlockConnectorOnEVSideDisconnect / R OR RW If AuthorizationKey is present, the value must either be omitted, empty or contain a value that does NOT equal the <configured AuthorizationKey> value in either its plain text or hex representation. Local Auth List Management: LocalAuthListEnabled / RW LocalAuthListMaxLength / R SendLocalListMaxLength / R Smart Charging Profile: ChargeProfileMaxStackLevel / R ChargingScheduleAllowedChargingRateUnit / R ChargingScheduleMaxPeriods / R MaxChargingProfilesInstalled / R Reservation: None Remote Trigger: None; * Step 8:
(Message: GetConfiguration.conf) unknownKey list is <Empty> configurationKey list contains all the keys requested in step 7.

Tool validation(s)

Charge Point side:

  • N/a

Central System side:

  • N/a

Expected result(s) / behaviour

Charge Point side:

All required keys are configured.

Central System side:

The Central System is able to retrieve the values of all requested configuration keys.