Skip to content
Documentation Menu

TC_C_42_CS — Authorization by GroupId - Not stopped by GroupId

TC_C_42_CS — Authorization by GroupId - Not stopped by GroupId

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

Identification

FieldValue
Test case nameAuthorization by GroupId - Not stopped by GroupId
Test case IdTC_C_42_CS
Use case Id(s)C09
Requirement(s)C09_FR_11
System under testCharging Station
Functional blockC. Authorization

Description

This test case covers how a Charging Station can authorize an action for an EV Driver based on GroupId information. This could for example be used if 2 people regularly use the same EV: they can use their own IdToken (e.g. RFID card), and can deauthorize transactions that were started with the other idToken (with the same GroupId).

Purpose

To verify if the Charging Station is able to correctly handle the Authorization of idTokens with the same GroupId, while one of them is invalid, according to the mechanism as described in the OCPP specification.

Prerequisite(s)

  • N/a

Before (Preparations)

Configuration State:

  • N/a

Memory State:

  • N/a

Reusable State(s):

  • State is EVConnectedPreSession

Main (Test scenario)

Charging StationCSMS
Manual Action: Present valid idToken with <Configured GroupId>
1. The Charging Station sends an AuthorizeRequest2. The OCTT responds with an AuthorizeResponse with; - idTokenInfo.status Accepted; - idTokenInfo.groupIdToken.idToken <Configured groupIdToken>
3. The Charging Station sends a TransactionEventRequest; Note(s):; - This step needs to be executed when TxStartPoint contains Authorized OR the transaction already started. So in the case TxStartPoint contains ParkingBayOccupancy4. The OCTT responds with a TransactionEventResponse with; - idTokenInfo.status Accepted; - idTokenInfo.groupIdToken.idToken <Configured groupIdToken>
5. Execute Reusable State EnergyTransferStarted
Manual Action: Present invalid idToken with <Configured GroupId>
6. The Charging Station sends an AuthorizeRequest7. The OCTT responds with an AuthorizeResponse with; - idTokenInfo.status Invalid; - idTokenInfo.groupIdToken.idToken <Configured groupIdToken>
Note(s): OCTT will wait to see if CS indeed doesn’t send a TransactionEventRequest

Tool validations

Step 1:

Message AuthorizeRequest

  • idToken.idToken <Configured valid_idtoken_idtoken>
  • idToken.type <Configured valid_idtoken_type>

Step 3:

Message TransactionEventRequest

  • triggerReason Authorized
  • idToken.idToken <Configured valid_idtoken_idtoken>
  • idToken.type <Configured valid_idtoken_type> if transaction was already started
  • eventType Updated else
  • eventType Started

Step 6:

Message AuthorizeRequest

  • idToken.idToken <Configured valid_idtoken_idtoken>
  • idToken.type <Configured valid_idtoken_type>

Post scenario validations

  • The energy transfer is not stopped