GBCS 16.2 / 0x8F3E

Unauthorised Communication Access attempted

Alert Details

WAN: YGeneric Alert StructureMandatedCriticalPre-config: No

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

7 clauses · 7 linked records
  • CHTS 4.4.6.6Exact evidence

    1 direct clause reference

    • CHF Secure Communications

    Evidence: gbcs_device_alert_extract_16.2.json · 16.2 · row 54 · reference 4.4.6.6

  • CHTS 4.4.6.7Exact evidence

    1 direct clause reference

    • GPF Secure Communications

    Evidence: gbcs_device_alert_extract_16.2.json · 16.2 · row 54 · reference 4.4.6.7

  • SMETS 4.4.10.5Exact evidence

    1 direct clause reference

    • Communications
    GSME

    Evidence: gbcs_device_alert_extract_16.2.json · 16.2 · row 54 · reference 4.4.10.5

  • SMETS 5.5.10.5Exact evidence

    1 direct clause reference

    • Communications
    ESME

    Evidence: gbcs_device_alert_extract_16.2.json · 16.2 · row 54 · reference 5.5.10.5

  • SMETS 7.4.1Exact evidence

    1 direct clause reference

    • Communications
    PPMID

    Evidence: gbcs_device_alert_extract_16.2.json · 16.2 · row 54 · reference 7.4.1

  • SMETS 8.4.2Exact evidence

    1 direct clause reference

    • Communications
    HCALCS

    Evidence: gbcs_device_alert_extract_16.2.json · 16.2 · row 54 · reference 8.4.2

  • SMETS 9.4.4.5Exact evidence

    1 direct clause reference

    • Communications
    SAPC

    Evidence: gbcs_device_alert_extract_16.2.json · 16.2 · row 54 · reference 9.4.4.5

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 →