GBCS 16.2 / 0x8F12 / Message Patterns
CHF 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 0x8F12.
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) — CS14GBCS Hex
DD00000000000081A51100000000DF09
030000000000000FA00800DB12345678
90A20890B3D51F300000020002001871
0F20000FA0000203128F12090C07DF01
01FF000000008000FF0203090C07DF01
01FF000000008000FF09080001020304
05060701020202090800DB1234567890
A0091083FED3407A939723A5C639B269
16D5060202090800DB1234567890A109
1083FED3407A939723A5C639B26916D5
0500223A858288D69C04E3271A97
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.