GBCS 16.2 / 0x8F22 / Message Patterns

Critical Duty Cycle Action Taken

WAN: YGeneric Alert Structure
Generating Device
No specific device applicability

Message Pattern

Success Examples

Alert triggeredDevice (internal)

The device detects the condition and generates GBCS event/alert code 0x8F22.

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).

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).

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