Remote Stop Transaction

Source: OCPP 1.6 Specification — Section 5.12 (Operation), Sections 6.35 / 6.36 (Messages)

Overview

Central System can request a Charge Point to stop a transaction by sending a RemoteStopTransaction.req to the Charge Point with the identifier of the transaction. Charge Point SHALL reply with RemoteStopTransaction.conf to indicate whether it is indeed able to stop the transaction.

This remote request to stop a transaction is equal to a local action to stop a transaction. Therefore, the transaction SHALL be stopped, the Charge Point SHALL send a StopTransaction.req and, if applicable, unlock the connector.

The following two main use cases are the reason for Remote Stop Transaction:

• Enable a CPO operator to help an EV driver that has problems stopping a transaction.
• Enable mobile apps to control charging transactions via the Central System.

Sequence Diagram

Figure 33. Sequence Diagram: Remote Stop Transaction

Central System  ──── RemoteStopTransaction.req ────▶  Charge Point
                     (transactionId)
Central System  ◀─── RemoteStopTransaction.conf ────  Charge Point
                     (status)

Initiator

Central System → Charge Point

Fields

RemoteStartStopStatus values

• Accepted — Command will be executed.
• Rejected — Command will not be executed.

Examples

{
  "transactionId": 1234
}

{
  "status": "Accepted"
}

Schema

Source: schemas/RemoteStopTransaction.json, schemas/RemoteStopTransactionResponse.json (OCPP 1.6, JSON Schema draft-04)