GBCS 16.2 / 0x81BD / Message Patterns
Supply Connect Failure (Valve or Load Switch)
WAN: YGeneric 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 0x81BD.
2
DeviceAlertMessageDevice → DSP (WAN)
The device transmits a GBCSResponse/DeviceAlertMessage to the DSP via the WAN. Payload contains alert code and timestamp only (Generic Alert Structure).
GBCS Device Alert — pre-signed example (SME.A.NC, DLMS payload)GBCS Hex
DD0000000000004D1100000000DF0903
00000000000000010800DB1234567890
010890B3D51F3001000000021001190F
200000010002021281BD090C07EA0501
FF0C00000080000000278E601C9386DF
10C3CFEF6D
View in GBCS Parser →GBCS Device Alert — pre-signed example (SME.A.NC, ZigBee/GBZ payload)GBCS Hex
DD0000000000003D1100000000DF0903
00000000000000010800DB1234567890
010890B3D51F30010000000210010901
090081BD318752400048702CF7F9B525
B2464DD7B2
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
Select a device type above to see the applicable role.
DUIS Response (sr:Response) — to Supplier (DLMS payload)DUIS 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>81BD</sr:AlertCode>
<sr:GBCSPayload>3QAAAAAAAE0RAAAAAN8JAwAAAAAAAAABCADbEjRWeJABCJCz1R8wAQAAAAIQARkPIAAAAQACAhKBvQkMB+oFAf8MAAAAgAAAACeOYByTht8Qw8/vbQ==</sr:GBCSPayload>
</sr:DeviceAlertMessage>
</sr:Body>
</sr:Response>
DUIS Response (sr:Response) — to Supplier (ZigBee/GBZ payload)DUIS 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>81BD</sr:AlertCode>
<sr:GBCSPayload>3QAAAAAAAD0RAAAAAN8JAwAAAAAAAAABCADbEjRWeJABCJCz1R8wAQAAAAIQAQkBCQCBvTGHUkAASHAs9/m1JbJGTdey</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) — SupplierMMC
<?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-01-00-00</ra:BusinessTargetID>
<ra:OriginatorCounter>1</ra:OriginatorCounter>
<ra:GBCSHexadecimalMessageCode>1001</ra:GBCSHexadecimalMessageCode>
</ra:Header>
<ra:Body>
<ra:DeviceAlertMessage>
<ra:DeviceAlertContent>
<ra:GBCSHexAlertCode>81BD</ra:GBCSHexAlertCode>
<ra:AlertDescription>Supply Connect Failure (Valve or Load Switch)</ra:AlertDescription>
<ra:Timestamp>2026-05-01T12:00:00.00Z</ra:Timestamp>
</ra:DeviceAlertContent>
</ra:DeviceAlertMessage>
</ra:Body>
</ra:GBCSResponse>