Remote Start Transaction

Source: OCPP 1.6 Specification — Section 5.11 (Operation), Sections 6.33 / 6.34 (Messages)

Overview

Central System can request a Charge Point to start a transaction by sending a RemoteStartTransaction.req. Upon receipt, the Charge Point SHALL reply with RemoteStartTransaction.conf and a status indicating whether it is able to start a transaction or not.

The effect of the RemoteStartTransaction.req message depends on the value of the AuthorizeRemoteTxRequests configuration key in the Charge Point.

• If the value of AuthorizeRemoteTxRequests is true, the Charge Point SHALL behave as if in response to a local action at the Charge Point to start a transaction with the idTag given in the RemoteStartTransaction.req message. This means that the Charge Point will first try to authorize the idTag, using the Local Authorization List, Authorization Cache and/or an Authorize.req request. A transaction will only be started after authorization was obtained.
• If the value of AuthorizeRemoteTxRequests is false, the Charge Point SHALL immediately try to start a transaction for the idTag given in the RemoteStartTransaction.req message. Note that after the transaction has been started, the Charge Point will send a StartTransaction request to the Central System, and the Central System will check the authorization status of the idTag when processing this StartTransaction request.

The following typical use cases are the reason for Remote Start Transaction:

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

The RemoteStartTransaction.req SHALL contain an identifier (idTag), which Charge Point SHALL use, if it is able to start a transaction, to send a StartTransaction.req to Central System. The transaction is started in the same way as described in Start Transaction. The RemoteStartTransaction.req MAY contain a connectorId if the transaction is to be started on a specific connector. When no connector id is provided, the Charge Point is in control of the connector selection. A Charge Point MAY reject a RemoteStartTransaction.req without a connector id.

The Central System MAY include a ChargingProfile in the RemoteStartTransaction request. The purpose of this ChargingProfile SHALL be set to TxProfile. If accepted, the Charge Point SHALL use this ChargingProfile for the transaction.

NOTE: If a Charge Point without support for Smart Charging receives a RemoteStartTransaction.req with a Charging Profile, this parameter SHOULD be ignored.

Sequence Diagram

Figure 32. Sequence Diagram: Remote Start Transaction

Central System  ──── RemoteStartTransaction.req ────▶  Charge Point
                     (connectorId?, idTag, chargingProfile?)
Central System  ◀─── RemoteStartTransaction.conf ────  Charge Point
                     (status)

Initiator

Central System → Charge Point

Fields

RemoteStartStopStatus values

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

Examples

{
  "connectorId": 1,
  "idTag": "044943121F1A80"
}

{
  "status": "Accepted"
}

Related Configuration Keys

• AuthorizeRemoteTxRequests — Whether the Charge Point first sends Authorize.req for remote-initiated transactions.

Schema

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