DCC Alert

`N62` — Comms Hub Alert

SMETS applicability: SMETS2 or later

Trigger & context

When and why this alert fires

Event: A Comms Hub generates a Device Alert as defined by GBCS
Trigger: An Alert from a Comms Hub is received by the DSP Access Control Broker.
Recipient(s): Responsible EIS Responsible GIS (For firmware delivery status the Alerts will be delivered to the sender of the Request)
SMETS applicability: SMETS2 or later
Introduced in DUIS: 5.0
Payload DUIS applicability: >= 5.0

DUIS delivery

Wrapper and field names

Wrapper element: DCCAlertMessage
Alert code field: DCCAlertCode
Payload field: DCCAlert
Throttling supported: Yes

Payload structure (16.2.1)

`CommsHubAlert` — sr:CommsHubAlert

Device Alert generated by the Comms Hub.

Field	Type	Mandatory	Description	Sensitivity
`CommsHubDeviceID`	`sr:EUI`	Yes	Device ID of the Comms Hub that generated the Device Alert.	Non-Sensitive
`AlertCode`	`xs:hexBinary`	Yes	Device Alert Code generated by the Comms Hub.	Non-Sensitive
`TimeStamp`	`xs:dateTime`	No	Timestamp at which the event responsible for this Device Alert occurred.	Non-Sensitive
`FirmwareTransferAlert`	`sr:FirmwareTransferAlert`	No	Comms Hub alert reporting transfer status of a firmware image to the target Device.	Non-Sensitive

Response codes (16.2.1.3)

DUIS response codes applicable to this alert

I0

DUIS XSD version: >= 5.0

XML examples

Sample DUIS delivery messages

Figure 57Figure 57.5 Sample CommsHubAlert DCC Alert Response Format Page 72 of 76

                <DCCAlertMessage>
<DCCAlertCode>N62</DCCAlertCode>
<DCCAlert>
<CommsHubAlert>
<CommsHubDeviceID>13-00-AA-BB-CC-DD-EE-FF</CommsHubDeviceID>
<AlertCode>8F89</AlertCode>
<TimeStamp>2020-09-10T07:05:03.00</TimeStamp>
<FirmwareTransferAlert>
<OtherDeviceID>11-00-AA-BB-CC-DD-EE-FF</OtherDeviceID>
<FirmwareVersion>11A0EEFF</FirmwareVersion>
<TransferResponseCode>FileTransferFailed</TransferResponseCode>
</FirmwareTransferAlert>
</CommsHubAlert>
</DCCAlert>
</DCCAlertMessage>

N62 — Comms Hub Alert