GBCS 16.2 / 0x8F72 / Message Patterns
Firmware Verification Successful
WAN: YUse Case Specific Alert Structure
Generating Device
Select a generating device type above to see the alert delivery pattern.
Message Pattern
Success Examples
—
Alert triggeredDevice (internal)
The device detects the condition and generates GBCS event/alert code 0x8F72.
2
DeviceAlertMessageDevice → DSP (WAN)
The device transmits a GBCSResponse/DeviceAlertMessage to the DSP via the WAN. Payload contains alert code, timestamp, and use-case specific data (Use Case Specific Alert Structure).
GBCS Device Alert — RTDS example (SME.A.C) — FDRA-DLMS-ESMEGBCS Hex
DF090300000000000007D00800DB1234
567890A00890B3D51F30010000000200
CE3B0F200007D0000203128F72090C07
DF0101FF000000008000FF0920010101
01010101010101010101010101010101
01010101010101010101010101405910
A033CDCE3B205216A9C11DEED1D03874
7BC39B67E0EEBC146AF087F03D9B89FC
181F6EA989E7834B1C21262183F5854F
F97BA48DF7F7CB95285C5D8C9B3F
View in GBCS Parser →GBCS Device Alert — RTDS example (SME.A.C) — FDRA-DLMS-HCALCSGBCS Hex
DF090300000000000017700800DB1234
567890A50890B3D51F30010000000201
2C3B0F20001770000203128F72090C07
DF0101FF000000008000FF0920010101
01010101010101010101010101010101
01010101010101010101010101407425
5B459E3703B4A27C78C9CC3B7C838D99
132607CF9307934124C6C08DAC2D4327
86C7830ADE4C20A932009524F27D973D
A8E11E9E8CBD47B17AE6C70A028F
View in GBCS Parser →GBCS Device Alert — RTDS example (SME.A.C) — FDRA-ZigBeeGBCS Hex
DF09030000000000000BB80800DB1234
567890A10890B3D51F30010000000200
CF2B0109018F721C374A800920A1A1A1
A1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A1
A1A1A1A1A1A1A1A1A1A1A1A1A140F346
C4C92CC5B540138D66E0E03ECE63F31B
0C7DB7AB796D5BBFFE12E8138D7879E6
558805F9DAF8FA83F03AC39BC7BBD65A
DD2872BFAD59C591C433E66C252C
View in GBCS Parser →—
Alert received and validatedDSP (internal)
DSP authenticates the GBCSResponse against the device certificate and validates the alert content.
4
Alert delivered to Known Remote PartyDSP → Known Remote Party
DSP delivers the alert to the relevant Known Remote Party based on the alert code and triggering device type. The DUIS Response (sr:Response) wraps the raw GBCS payload in sr:GBCSPayload (base64).
GSME: Supplier
ESME: Supplier
HCALCS: Supplier
Select a device type above to see the applicable role.
DUIS Response (sr:Response) — to Supplier — FDRA-DLMS-ESMEDUIS Response
<?xml version="1.0" encoding="UTF-8"?>
<sr:Response schemaVersion="5.4" xmlns:ns5="http://www.dccinterface.co.uk/sm" xmlns:ns4="http://www.dccinterface.co.uk/S1SP" xmlns:sr="http://www.dccinterface.co.uk/ServiceUserGateway" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:ns3="http://www.dccinterface.co.uk/ResponseAndAlert">
<sr:Header>
<sr:ResponseID>00-DB-12-34-56-78-90-01:90-B3-D5-1F-30-01-00-00:1</sr:ResponseID>
<sr:ResponseCode>I0</sr:ResponseCode>
<sr:ResponseDateTime>2026-05-01T12:00:00.00Z</sr:ResponseDateTime>
</sr:Header>
<sr:Body>
<sr:DeviceAlertMessage>
<sr:AlertCode>8F72</sr:AlertCode>
<sr:GBCSPayload>3wkDAAAAAAAAB9AIANsSNFZ4kKAIkLPVHzABAAAAAgDOOw8gAAfQAAIDEo9yCQwH3wEB/wAAAACAAP8JIAEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBQFkQoDPNzjsgUhapwR3u0dA4dHvDm2fg7rwUavCH8D2bifwYH26pieeDSxwhJiGD9YVP+Xukjff3y5UoXF2Mmz8=</sr:GBCSPayload>
</sr:DeviceAlertMessage>
</sr:Body>
</sr:Response>
DUIS Response (sr:Response) — to Supplier — FDRA-DLMS-HCALCSDUIS Response
<?xml version="1.0" encoding="UTF-8"?>
<sr:Response schemaVersion="5.4" xmlns:ns5="http://www.dccinterface.co.uk/sm" xmlns:ns4="http://www.dccinterface.co.uk/S1SP" xmlns:sr="http://www.dccinterface.co.uk/ServiceUserGateway" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:ns3="http://www.dccinterface.co.uk/ResponseAndAlert">
<sr:Header>
<sr:ResponseID>00-DB-12-34-56-78-90-01:90-B3-D5-1F-30-01-00-00:1</sr:ResponseID>
<sr:ResponseCode>I0</sr:ResponseCode>
<sr:ResponseDateTime>2026-05-01T12:00:00.00Z</sr:ResponseDateTime>
</sr:Header>
<sr:Body>
<sr:DeviceAlertMessage>
<sr:AlertCode>8F72</sr:AlertCode>
<sr:GBCSPayload>3wkDAAAAAAAAF3AIANsSNFZ4kKUIkLPVHzABAAAAAgEsOw8gABdwAAIDEo9yCQwH3wEB/wAAAACAAP8JIAEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBAQEBQHQlW0WeNwO0onx4ycw7fIONmRMmB8+TB5NBJMbAjawtQyeGx4MK3kwgqTIAlSTyfZc9qOEenoy9R7F65scKAo8=</sr:GBCSPayload>
</sr:DeviceAlertMessage>
</sr:Body>
</sr:Response>
DUIS Response (sr:Response) — to Supplier — FDRA-ZigBeeDUIS Response
<?xml version="1.0" encoding="UTF-8"?>
<sr:Response schemaVersion="5.4" xmlns:ns5="http://www.dccinterface.co.uk/sm" xmlns:ns4="http://www.dccinterface.co.uk/S1SP" xmlns:sr="http://www.dccinterface.co.uk/ServiceUserGateway" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:ns3="http://www.dccinterface.co.uk/ResponseAndAlert">
<sr:Header>
<sr:ResponseID>00-DB-12-34-56-78-90-01:90-B3-D5-1F-30-01-00-00:1</sr:ResponseID>
<sr:ResponseCode>I0</sr:ResponseCode>
<sr:ResponseDateTime>2026-05-01T12:00:00.00Z</sr:ResponseDateTime>
</sr:Header>
<sr:Body>
<sr:DeviceAlertMessage>
<sr:AlertCode>8F72</sr:AlertCode>
<sr:GBCSPayload>3wkDAAAAAAAAC7gIANsSNFZ4kKEIkLPVHzABAAAAAgDPKwEJAY9yHDdKgAkgoaGhoaGhoaGhoaGhoaGhoaGhoaGhoaGhoaGhoaGhoaFA80bEySzFtUATjWbg4D7OY/MbDH23q3ltW7/+EugTjXh55lWIBfna+PqD8DrDm8e71lrdKHK/rVnFkcQz5mwlLA==</sr:GBCSPayload>
</sr:DeviceAlertMessage>
</sr:Body>
</sr:Response>
—
Alert converted to MMC via ParseKnown Remote Party (internal)
The DCC User runs the received DUIS Response through the Parse tool, which decodes the GBCS payload and produces an ra:GBCSResponse (MMC) document containing the structured alert data.
MMC parse output structure (DUIS Annex 18 section 18.4.3)ra:GBCSResponse
Body path: ra:GBCSResponse/ra:Body/ra:DeviceAlertMessage/ra:DeviceAlertContent
Header fields
| Field | Type | Mandatory | Description |
|---|---|---|---|
BusinessOriginatorID | ra:EUI / identifier | Yes | Entity identifier of the message originator. |
BusinessTargetID | ra:EUI / identifier | Yes | Entity identifier of the message target. |
OriginatorCounter | xs:nonNegativeInteger | Yes | Originator counter in the response/alert header. |
SupplementaryRemotePartyID | identifier | Conditional | Supplementary party identifier; only present for alert families whose header table permits it. |
SupplementaryRemotePartyCounter | xs:nonNegativeInteger | Conditional | Supplementary party counter; only present for alert families whose header table permits it. |
SupplementaryOriginatorCounter | xs:nonNegativeInteger | Conditional | Only present where the specific header table permits it. |
Timestamp | xs:dateTime | Conditional | Only present where the specific header table permits it. |
GBCSHexadecimalMessageCode | xs:hexBinary | Yes | GBCS/MMC message code used to identify the alert use case. |
ra:DeviceAlertContent fields
| Field | Type | Mandatory | Description |
|---|---|---|---|
GBCSHexAlertCode | xs:hexBinary | Yes | Device Alert code as parsed from the GBCS payload. |
AlertDescription | xs:string (maxLength = 250) | Yes | Human-readable alert description. |
Timestamp | xs:dateTime | Yes | Device Alert timestamp as sent by the Device, in UTC time. |
Payload | choice | Conditional | Optional payload element present for the alert families in section 15.4. |
MMC Output (ra:GBCSResponse) — Supplier — FDRA-DLMS-ESMEMMC
<?xml version="1.0"?>
<ra:GBCSResponse xmlns:ra="http://www.dccinterface.co.uk/ResponseAndAlert" xmlns:sr="http://www.dccinterface.co.uk/ServiceUserGateway" schemaVersion="5.4">
<ra:Header>
<ra:BusinessOriginatorID>00-DB-12-34-56-78-90-A0</ra:BusinessOriginatorID>
<ra:BusinessTargetID>90-B3-D5-1F-30-01-00-00</ra:BusinessTargetID>
<ra:OriginatorCounter>2000</ra:OriginatorCounter>
<ra:GBCSHexadecimalMessageCode>00CE</ra:GBCSHexadecimalMessageCode>
</ra:Header>
<ra:Body>
<ra:DeviceAlertMessage>
<ra:DeviceAlertContent>
<ra:GBCSHexAlertCode>8F72</ra:GBCSHexAlertCode>
<ra:AlertDescription>Firmware verification succeeded</ra:AlertDescription>
<ra:Timestamp>2015-01-01T00:00:00.00Z</ra:Timestamp>
<ra:Payload>
<ra:FirmwareVerificationDeviceAlert>
<ra:ManufacturerImageHash>0101010101010101010101010101010101010101010101010101010101010101</ra:ManufacturerImageHash>
</ra:FirmwareVerificationDeviceAlert>
</ra:Payload>
</ra:DeviceAlertContent>
</ra:DeviceAlertMessage>
</ra:Body>
</ra:GBCSResponse>
MMC Output (ra:GBCSResponse) — Supplier — FDRA-DLMS-HCALCSMMC
<?xml version="1.0"?>
<ra:GBCSResponse xmlns:ra="http://www.dccinterface.co.uk/ResponseAndAlert" xmlns:sr="http://www.dccinterface.co.uk/ServiceUserGateway" schemaVersion="5.4">
<ra:Header>
<ra:BusinessOriginatorID>00-DB-12-34-56-78-90-A5</ra:BusinessOriginatorID>
<ra:BusinessTargetID>90-B3-D5-1F-30-01-00-00</ra:BusinessTargetID>
<ra:OriginatorCounter>6000</ra:OriginatorCounter>
<ra:GBCSHexadecimalMessageCode>012C</ra:GBCSHexadecimalMessageCode>
</ra:Header>
<ra:Body>
<ra:DeviceAlertMessage>
<ra:DeviceAlertContent>
<ra:GBCSHexAlertCode>8F72</ra:GBCSHexAlertCode>
<ra:AlertDescription>Firmware verification succeeded</ra:AlertDescription>
<ra:Timestamp>2015-01-01T00:00:00.00Z</ra:Timestamp>
<ra:Payload>
<ra:FirmwareVerificationDeviceAlert>
<ra:ManufacturerImageHash>0101010101010101010101010101010101010101010101010101010101010101</ra:ManufacturerImageHash>
</ra:FirmwareVerificationDeviceAlert>
</ra:Payload>
</ra:DeviceAlertContent>
</ra:DeviceAlertMessage>
</ra:Body>
</ra:GBCSResponse>
MMC Output (ra:GBCSResponse) — Supplier — FDRA-ZigBeeMMC
<?xml version="1.0"?>
<ra:GBCSResponse xmlns:ra="http://www.dccinterface.co.uk/ResponseAndAlert" xmlns:sr="http://www.dccinterface.co.uk/ServiceUserGateway" schemaVersion="5.4">
<ra:Header>
<ra:BusinessOriginatorID>00-DB-12-34-56-78-90-A1</ra:BusinessOriginatorID>
<ra:BusinessTargetID>90-B3-D5-1F-30-01-00-00</ra:BusinessTargetID>
<ra:OriginatorCounter>3000</ra:OriginatorCounter>
<ra:GBCSHexadecimalMessageCode>00CF</ra:GBCSHexadecimalMessageCode>
</ra:Header>
<ra:Body>
<ra:DeviceAlertMessage>
<ra:DeviceAlertContent>
<ra:GBCSHexAlertCode>8F72</ra:GBCSHexAlertCode>
<ra:AlertDescription>Firmware verification succeeded</ra:AlertDescription>
<ra:Timestamp>2015-01-01T00:00:00.00Z</ra:Timestamp>
<ra:Payload>
<ra:FirmwareVerificationDeviceAlert>
<ra:ManufacturerImageHash>A1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A1A1</ra:ManufacturerImageHash>
</ra:FirmwareVerificationDeviceAlert>
</ra:Payload>
</ra:DeviceAlertContent>
</ra:DeviceAlertMessage>
</ra:Body>
</ra:GBCSResponse>