GBCS 16.2 / 0x8F3C / Message Patterns
Supply Outage Restored on Phase 3 Restored - Outage >= 3 minutes
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 0x8F3C.
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 — generated gap-fill example (SME.A.C)GBCS Hex
DF090300000000000000010800DB1234
567890010890B3D51F30020000000200
67350F20000001000204128F3C090C07
EA0501FF0C000000800000090C07EA05
01FF0B000000800000090C07EA0501FF
0C000000800000404DEB8D7EBFD461D5
3EBD1314743BB90FD1A4BE933F05E307
0A12A193FFFFDEADDC9609BE11FD233C
09140AFE6EBDC057F9355CD84D72796C
ABC8268919E6F6D1
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).
ESME: Network Operator
Select a device type above to see the applicable role.
DUIS Response (sr:Response) — to NetworkOperatorDUIS 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-02-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>8F3C</sr:AlertCode>
<sr:GBCSPayload>3wkDAAAAAAAAAAEIANsSNFZ4kAEIkLPVHzACAAAAAgBnNQ8gAAABAAIEEo88CQwH6gUB/wwAAACAAAAJDAfqBQH/CwAAAIAAAAkMB+oFAf8MAAAAgAAAQE3rjX6/1GHVPr0TFHQ7uQ/RpL6TPwXjBwoSoZP//96t3JYJvhH9IzwJFAr+br3AV/k1XNhNcnlsq8gmiRnm9tE=</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) — NetworkOperatorMMC
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<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-01</ra:BusinessOriginatorID>
<ra:BusinessTargetID>90-B3-D5-1F-30-02-00-00</ra:BusinessTargetID>
<ra:OriginatorCounter>1</ra:OriginatorCounter>
<ra:GBCSHexadecimalMessageCode>0067</ra:GBCSHexadecimalMessageCode>
</ra:Header>
<ra:Body>
<ra:DeviceAlertMessage>
<ra:DeviceAlertContent>
<ra:GBCSHexAlertCode>8F3C</ra:GBCSHexAlertCode>
<ra:AlertDescription>Supply Outage Restored (0x8F3C)</ra:AlertDescription>
<ra:Timestamp>2026-05-01T12:00:00.00Z</ra:Timestamp>
<ra:Payload>
<ra:SupplyOutageRestoreAlert>
<ra:interruptionValue>2026-05-01T11:00:00.00Z</ra:interruptionValue>
<ra:restorationValue>2026-05-01T12:00:00.00Z</ra:restorationValue>
</ra:SupplyOutageRestoreAlert>
</ra:Payload>
</ra:DeviceAlertContent>
</ra:DeviceAlertMessage>
</ra:Body>
</ra:GBCSResponse>