GBCS 16.2 / 0x8F2C / Message Patterns
Message Discarded Due to Duty Cycle Management
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 0x8F2C.
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) — DBCH10GBCS Hex
DD000000000000681100000000DF0903
0000000000000FA00800DB1234567890
A20890B3D51F3000000200020114340F
20000FA0000203128F2C090C07DF0101
FF000000008000FF091990B3D51F3001
000000DB1234567890A0010000000000
0003E8005B4E3544FC88DEE2539D7EEA
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.