TC_B_08_CS — Get Variables - limit to maximum number of values

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

Identification

Field	Value
Test case name	Get Variables - limit to maximum number of values
Test case Id	TC_B_08_CS
Use case Id(s)	B06
Requirement(s)	B06.FR.05
System under test	Charging Station
Functional block	B. Provisioning

Do not return more variables than supported by MaxItemsPerMessageGetVariables.

To test that Charging Station does not return more variables than it reports to support in the variable MaxItemsPerMessageGetVariables.

CS needs to have more configured variables than MaxItemsPerMessageGetVariables.

Configuration State:

Memory State:

Reusable State(s):

Charging Station	CSMS
2. Charging Station responds with GetBaseReportResponse	1. OCTT sends GetBaseReportRequest for type FullInventory
3. Charging Station sends NotifyReportRequest; Note(s):; - This step may be executed multiple times, until all components/variables are reported.	4. OCTT responds with NotifyReportResponse
6. Charging Station responds with GetVariablesResponse; Note(s):; - It is up to Charging Station to decide whether it wants to return return every variable as Rejected or return ItemsPerMessageGetVariables values; with attributeStatus = Accepted and the rest as Rejected.	5. OCTT sends GetVariablesRequest for x amount of variables:; Note(s):; - x equals ItemsPerMessageGetVariables + 1

Step 6:

Message: GetVariablesResponse has a list of GetVariableResultType values (in arbitrary order) of which either:

all have attributeStatus = Rejected
or the last has attributeStatus = Rejected and the rest have attributeStatus = Accepted. and if attributeStatusInfo is provided:
the accepted items have attributeStatusInfo.reasonCode = "NoError"
the rejected items have attributeStatusInfo.reasonCode = "TooManyElements"