Log Status Notification

Source: OCPP 1.6 Security Whitepaper Edition 2 (2020-03-31) — Use Case N01 (Retrieve Log Information), Sections 5.13 / 5.14 (Messages)

Overview

The Charge Point uses LogStatusNotification.req to inform the Central System about the progress of a log file upload that was started by GetLog.req. The CP sends one or more notifications during the upload — typically Uploading when the transfer begins, then Uploaded on success or one of the failure values otherwise.

Every LogStatusNotification.req sent for a specific log upload SHALL contain the same requestId as the GetLog.req that started the upload.

The requestId field is mandatory unless the message was triggered by an ExtendedTriggerMessage.req AND there is no log upload ongoing — in that case the CP may send LogStatusNotification.req(status = Idle) without a requestId.

Sequence Diagram

Charge Point  ──── LogStatusNotification.req ────▶  Central System
                   (status, requestId?)
Charge Point  ◀─── LogStatusNotification.conf ────  Central System

Initiator

Charge Point → Central System

Fields

UploadLogStatusEnumType values

• BadMessage — A badly formatted packet or other protocol incompatibility was detected.
• Idle — The Charge Point is not uploading a log file. SHALL only be used when triggered by ExtendedTriggerMessage.req.
• NotSupportedOperation — The server does not support the operation.
• PermissionDenied — Insufficient permissions to perform the operation.
• Uploaded — File has been uploaded successfully.
• UploadFailure — Failed to upload the requested file.
• Uploading — File is being uploaded.

Examples

{
  "status": "Uploading",
  "requestId": 123
}

{
  "status": "Uploaded",
  "requestId": 123
}

{
  "status": "Idle"
}

{}

Schema

Source: schemas/LogStatusNotification.json, schemas/LogStatusNotificationResponse.json (OCPP 1.6 Security Whitepaper, JSON Schema draft-06)