TC_069_CS — Stop transaction - ParentIdTag in StopTransaction matches ParentIdTag in StartTransaction

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

Identification

Field	Value
Test case name	Stop transaction - ParentIdTag in StopTransaction matches ParentIdTag in StartTransaction
Test case Id	TC_069_CS
System under test	Charge Point

The Charge Point stops a transaction when a card is swiped with the same ParentIdTag as used to start the transaction.

Check whether the Charge Point is able to handle a stop transaction with same ParentIdTag.

If the Charge Point has multiple connectors attached to one RFID reader, then the connector which is NOT under test should be occupied.

Configuration State(s):

Memory State(s):

Reusable State(s):

Charge Point (SUT)	Central System (Tool)
[EV driver authorizes / swipes card with a different IdTag and the same ParentIdTag than the one used to start the transaction]; 1. The Charge Point sends an Authorize.req	2. The Central System responds with an Authorize.conf
[Step 3 and step 5 may be reversed.]; 3. The Charge Point sends a StopTransaction.req	4. The Central System responds with a StopTransaction.conf
[Step 3 and step 5 may be reversed.]; 5. The Charge Point sends a StatusNotification.req	6. The Central System responds with a StatusNotification.conf

Charge Point side:

Step 1:

(Message: Authorize.req) The idTag is different from the one used to start the transaction.

Step 3:

(Message: StopTransaction.req) The idTag matches the idTag from step 1.

Step 5:

(Message: StatusNotification.req) The status is Finishing

Central System side:

Step 2:

(Message: Authorize.conf) The idTagInfo.status is Accepted The idTagInfo.parentIdTag matches the parentIdTag that was used to start the transaction.

Charge Point side:

The Charge Point stops the transaction when receiving a (different) idTag with the same parentIdTag, as the one used to start the transaction.

Central System side: