GBCS 16.2 / 0x8F3D
Trusted Source Authentication Failure
Cross-specification evidence
Technical requirement relationships
The source clauses below explicitly relate this alert to equipment behaviour. Confidence and evidence labels show how each relationship was established.
Alert touchpoint
5 clauses · 5 linked records- SMETS 4.4.2Exact evidence
1 direct clause reference
- Communications
GSMEEvidence: gbcs_device_alert_extract_16.2.json · 16.2 · row 53 · reference 4.4.2
- CHTS 4.4.2.1Exact evidence
1 direct clause reference
- Communications Links with the CHF
Evidence: gbcs_device_alert_extract_16.2.json · 16.2 · row 53 · reference 4.4.2.1
- CHTS 4.4.2.2Exact evidence
1 direct clause reference
- Communications Links with the GPF
Evidence: gbcs_device_alert_extract_16.2.json · 16.2 · row 53 · reference 4.4.2.2
- SMETS 5.5.2Exact evidence
1 direct clause reference
- Communications
ESMEEvidence: gbcs_device_alert_extract_16.2.json · 16.2 · row 53 · reference 5.5.2
- SMETS 9.4.2Exact evidence
1 direct clause reference
- Communications
SAPCEvidence: gbcs_device_alert_extract_16.2.json · 16.2 · row 53 · reference 9.4.2
Device Specific Details
- GSME
- Supplier
- ESME
- Supplier
- CHF
- WAN Provider
- GPF
- Supplier
- HCALCS
- Supplier
- PPMID
- Access Control Broker
Message Patterns and Examples
View the step-by-step alert delivery pattern — from device event through WAN transmission to Known Remote Party notification — with available XML examples.
View Message Patterns →