GBCS 16.2 / 0x8071 / Message Patterns
GPF Device Log Changed
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 0x8071.
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.NC) — GCS62GBCS Hex
DD00000000000081A81100000000DF09
0300000000000003E90800DB12345678
90A30890B3D51F30000002000200B274
30720203008071180F32303135303130
313030303030305A305A300D04080102
030405060708020106300D040800DB12
3456789099020105300D040800DB1234
56789097020105300D040800DB123456
789096020105300D040800DB12345678
9098020105300D040800DB1234567890
9B02010600915CDB433FE849FB459585
67
View in GBCS Parser →—
Alert received and validatedDSP (internal)
DSP authenticates the GBCSResponse against the device certificate and validates the alert content.
—
No DCC User deliveryDSP (internal)
This alert is not delivered to a DCC User. RTDS GBCS HEX is therefore sufficient for coverage; DUIS Response and MMC Parse examples are not required.