GBCS 16.2 / 0x8F85 / Message Patterns
ECS100 Command not supported by Device
WAN: YUse Case Specific Alert Structure
Generating Device
No specific device applicability
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 0x8F85.
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) — ECS100GBCS Hex
DF090300000000000007D00800DB1234
567890A60890B3D51F30010000000201
20250F200007D0000203128F85090C07
DF0101FF000000008000FF090A001200
000000000186A0409B1DD5D050E70B78
706BE78341E8413436F122FEB1AACACD
DBE10F61D4254CF6022E7B726AB172A6
4B9727BF70C19FD76E5208418D5FF91C
7D8C8F866BC5F1F2
View in GBCS Parser →GBCS Device Alert — RTDS example (SME.A.C) — ECS100 SUPPLEMENTARY REMOTE PARTYGBCS Hex
DF090300000000000007D10800DB1234
567890A60890B3D51F30000002001201
2090B3D51F300100000000000000030D
40250F200007D1000203128F85090C07
DF0101FF000000008000FF090A001200
000000000186A04058C9F05D9044CB21
CF6140CEF1A9467E52D3C30490A31E9E
64781A1A91ED401D2B6E09978D39F0EE
AEE5C4F89CA390FEF51FD62E7AAE753C
07A600E5E4A35804
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. The DUIS Response (sr:Response) wraps the raw GBCS payload in sr:GBCSPayload (base64).
DUIS Response (sr:Response) — to Supplier — ECS100DUIS 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>8F85</sr:AlertCode>
<sr:GBCSPayload>3wkDAAAAAAAAB9AIANsSNFZ4kKYIkLPVHzABAAAAAgEgJQ8gAAfQAAIDEo+FCQwH3wEB/wAAAACAAP8JCgASAAAAAAABhqBAmx3V0FDnC3hwa+eDQehBNDbxIv6xqsrN2+EPYdQlTPYCLntyarFypkuXJ79wwZ/XblIIQY1f+Rx9jI+Ga8Xx8g==</sr:GBCSPayload>
</sr:DeviceAlertMessage>
</sr:Body>
</sr:Response>
DUIS Response (sr:Response) — to Supplier — ECS100 SUPPLEMENTARY REMOTE PARTYDUIS 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>8F85</sr:AlertCode>
<sr:GBCSPayload>3wkDAAAAAAAAB9EIANsSNFZ4kKYIkLPVHzAAAAIAEgEgkLPVHzABAAAAAAAAAAMNQCUPIAAH0QACAxKPhQkMB98BAf8AAAAAgAD/CQoAEgAAAAAAAYagQFjJ8F2QRMshz2FAzvGpRn5S08MEkKMenmR4GhqR7UAdK24Jl4058O6u5cT4nKOQ/vUf1i56rnU8B6YA5eSjWAQ=</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. |
Figure 22.3 - Device Alert 0x8F85 Command not supported by Device Parse Response SampleCommandNotSupportedbyDevice
<?xml version="1.0" encoding="UTF-8"?>
<ra:GBCSResponse xmlns:ds="http://www.w3.org/2000/09/xmldsig#"
xmlns:sr="http://www.dccinterface.co.uk/ServiceUserGateway"
xmlns:ra="http://www.dccinterface.co.uk/ResponseAndAlert"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.dccinterface.co.uk/ResponseAndAlert" schemaVersion="4.0">
<ra:Header>
<ra:BusinessOriginatorID>10-20-30-40-50-60-70-80</ra:BusinessOriginatorID>
<ra:BusinessTargetID>10-00-20-00-30-00-40-00</ra:BusinessTargetID>
<ra:OriginatorCounter>50</ra:OriginatorCounter>
<ra:SupplementaryRemotePartyID>10-00-20-00-30-00-70-00</ra:SupplementaryRemotePartyID>
<ra:GBCSHexadecimalMessageCode>0120</ra:GBCSHexadecimalMessageCode>
</ra:Header>
<ra:Body>
<ra:DeviceAlertMessage>
<ra:DeviceAlertContent>
<ra:GBCSHexAlertCode>8F85</ra:GBCSHexAlertCode>
<ra:AlertDescription>Command not supported by Device</ra:AlertDescription>
<ra:Timestamp>2021-05-04T18:13:51.00</ra:Timestamp>
<ra:Payload>
<ra:CommandNotSupportedbyDevice>
<ra:MessageCodeofCommandReceived>001B</ra:MessageCodeofCommandReceived>
<ra:OriginatorCounterfromCommandReceived>1501</ra:OriginatorCounterfromCommandReceived>
</ra:CommandNotSupportedbyDevice>
</ra:Payload>
</ra:DeviceAlertContent>
</ra:DeviceAlertMessage>
</ra:Body>
</ra:GBCSResponse>
MMC Output (ra:GBCSResponse) — Supplier — ECS100MMC
<?xml version="1.0" encoding="UTF-8"?>
<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-A6</ra:BusinessOriginatorID>
<ra:BusinessTargetID>90-B3-D5-1F-30-01-00-00</ra:BusinessTargetID>
<ra:OriginatorCounter>2000</ra:OriginatorCounter>
<ra:GBCSHexadecimalMessageCode>0120</ra:GBCSHexadecimalMessageCode>
</ra:Header>
<ra:Body>
<ra:DeviceAlertMessage>
<ra:DeviceAlertContent>
<ra:GBCSHexAlertCode>8F85</ra:GBCSHexAlertCode>
<ra:AlertDescription>Command not supported by Device</ra:AlertDescription>
<ra:Timestamp>2015-01-01T00:00:00.00Z</ra:Timestamp>
<ra:Payload>
<ra:CommandNotSupportedbyDevice>
<ra:MessageCodeofCommandReceived>0012</ra:MessageCodeofCommandReceived>
<ra:OriginatorCounterfromCommandReceived>100000</ra:OriginatorCounterfromCommandReceived>
</ra:CommandNotSupportedbyDevice>
</ra:Payload>
</ra:DeviceAlertContent>
</ra:DeviceAlertMessage>
</ra:Body>
</ra:GBCSResponse>
MMC Output (ra:GBCSResponse) — Supplier — ECS100 SUPPLEMENTARY REMOTE PARTYMMC
<?xml version="1.0" encoding="UTF-8"?>
<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-A6</ra:BusinessOriginatorID>
<ra:BusinessTargetID>90-B3-D5-1F-30-00-00-02</ra:BusinessTargetID>
<ra:OriginatorCounter>2001</ra:OriginatorCounter>
<ra:SupplementaryRemotePartyID>90-B3-D5-1F-30-01-00-00</ra:SupplementaryRemotePartyID>
<ra:SupplementaryRemotePartyCounter>200000</ra:SupplementaryRemotePartyCounter>
<ra:GBCSHexadecimalMessageCode>0120</ra:GBCSHexadecimalMessageCode>
</ra:Header>
<ra:Body>
<ra:DeviceAlertMessage>
<ra:DeviceAlertContent>
<ra:GBCSHexAlertCode>8F85</ra:GBCSHexAlertCode>
<ra:AlertDescription>Command not supported by Device</ra:AlertDescription>
<ra:Timestamp>2015-01-01T00:00:00.00Z</ra:Timestamp>
<ra:Payload>
<ra:CommandNotSupportedbyDevice>
<ra:MessageCodeofCommandReceived>0012</ra:MessageCodeofCommandReceived>
<ra:OriginatorCounterfromCommandReceived>100000</ra:OriginatorCounterfromCommandReceived>
</ra:CommandNotSupportedbyDevice>
</ra:Payload>
</ra:DeviceAlertContent>
</ra:DeviceAlertMessage>
</ra:Body>
</ra:GBCSResponse>