GBCS 16.2 / 0x8183
Device joined SMHAN
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
6 clauses · 6 linked records- SMETS 4.3Exact evidence
1 direct clause reference
- Physical requirements
GSMEEvidence: gbcs_device_alert_extract_16.2.json · 16.2 · row 96 · reference 4.3
- SMETS 4.5.2.8Exact evidence
1 direct clause reference
- Find Smart Metering Home Area Network and Re-establish Communications Links
GSMEEvidence: gbcs_device_alert_extract_16.2.json · 16.2 · row 96 · reference 4.5.2.8
- SMETS 5.4Exact evidence
1 direct clause reference
- Physical Requirements
ESMEEvidence: gbcs_device_alert_extract_16.2.json · 16.2 · row 96 · reference 5.4
- SMETS 5.6.2.6Exact evidence
1 direct clause reference
- Find Smart Metering Home Area Network and Re-establish Communications Links
ESMEEvidence: gbcs_device_alert_extract_16.2.json · 16.2 · row 96 · reference 5.6.2.6
- SMETS 5.10Exact evidence
1 direct clause reference
- Physical Requirements
ESMEEvidence: gbcs_device_alert_extract_16.2.json · 16.2 · row 96 · reference 5.10
- SMETS 5.16Exact evidence
1 direct clause reference
- Physical Requirements
ESMEEvidence: gbcs_device_alert_extract_16.2.json · 16.2 · row 96 · reference 5.16
Device Specific Details
- GSME
- Supplier
- ESME
- Supplier
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 →