GBCS 16.2 / 0x8F66 / Message Patterns
Future – date HAN Interface Command Successfully Actioned
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 0x8F66.
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).
—
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 based on the alert code and triggering device type. The DUIS Response (sr:Response) wraps the raw GBCS payload in sr:GBCSPayload (base64).
GSME: Transitional Change of Supplier, Supplier
ESME: Transitional Change of Supplier, Supplier, Load Controller
CHF: WAN Provider
GPF: Transitional Change of Supplier, Supplier
HCALCS: Transitional Change of Supplier, Supplier
Select a device type above to see the applicable role.
—
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
Body path: ra:GBCSResponse/ra:Body/ra:DeviceAlertMessage/ra:DeviceAlertContent
Header fields
| Field | Type | Mandatory | Description |
|---|---|---|---|
BusinessOriginatorID | ra:EUI / identifier | Yes | Entity identifier of the message originator. |
BusinessTargetID | ra:EUI / identifier | Yes | Entity identifier of the message target. |
OriginatorCounter | xs:nonNegativeInteger | Yes | Originator counter in the response/alert header. |
SupplementaryRemotePartyID | identifier | Conditional | Supplementary party identifier; only present for alert families whose header table permits it. |
SupplementaryRemotePartyCounter | xs:nonNegativeInteger | Conditional | Supplementary party counter; only present for alert families whose header table permits it. |
SupplementaryOriginatorCounter | xs:nonNegativeInteger | Conditional | Only present where the specific header table permits it. |
Timestamp | xs:dateTime | Conditional | Only present where the specific header table permits it. |
GBCSHexadecimalMessageCode | xs:hexBinary | Yes | GBCS/MMC message code used to identify the alert use case. |
ra:DeviceAlertContent fields
| Field | Type | Mandatory | Description |
|---|---|---|---|
GBCSHexAlertCode | xs:hexBinary | Yes | Device Alert code as parsed from the GBCS payload. |
AlertDescription | xs:string (maxLength = 250) | Yes | Human-readable alert description. |
Timestamp | xs:dateTime | Yes | Device Alert timestamp as sent by the Device, in UTC time. |
Payload | choice | Conditional | Optional payload element present for the alert families in section 15.4. |
Figure 17 Device Alert 0x8F66 Future-Dated Command Successful DLMS/COSEM Instruction Parse Response SampleFutureDatedCommandOutcomeDeviceAlert
<?xml version="1.0" encoding="UTF-8"?>
<ra:GBCSResponse xmlns:ds="http://www.w3.org/2000/09/xmldsig#"
xmlns:sr="http://www.dccinterface.co.uk/ServiceUserGateway"
xmlns:ra="http://www.dccinterface.co.uk/ResponseAndAlert"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.dccinterface.co.uk/ResponseAndAlert" schemaVersion="1.0">
<ra:Header>
<ra:BusinessOriginatorID>10-20-30-40-50-60-70-80</ra:BusinessOriginatorID>
<ra:BusinessTargetID>10-00-20-00-30-00-40-00</ra:BusinessTargetID>
<ra:OriginatorCounter>150</ra:OriginatorCounter>
<ra:GBCSHexadecimalMessageCode>00CC</ra:GBCSHexadecimalMessageCode>
</ra:Header>
<ra:Body>
<ra:DeviceAlertMessage>
<ra:DeviceAlertContent>
<ra:GBCSHexAlertCode>8F66</ra:GBCSHexAlertCode>
<ra:AlertDescription> Future Dated Command Successful Device Alert</ra:AlertDescription>
<ra:Timestamp>2014-05-04T18:13:51.00</ra:Timestamp>
<ra:Payload>
<ra:FutureDatedCommandOutcomeDeviceAlert>
<ra:COSEMFutureDatedAlert>
<ra:FutureDatedCommandMessageCode>00B7</ra:FutureDatedCommandMessageCode>
<ra:FutureDatedCommandOriginatorCounter>130</ra:FutureDatedCommandOriginatorCounter>
<ra:DLMSCOSEMFDInstructionIdentification>
<ra:ClassId>0014</ra:ClassId>
<ra:InstanceId>00000D0001FF</ra:InstanceId>
<ra:AttributeId>09</ra:AttributeId>
</ra:DLMSCOSEMFDInstructionIdentification>
</ra:COSEMFutureDatedAlert>
</ra:FutureDatedCommandOutcomeDeviceAlert>
</ra:Payload>
</ra:DeviceAlertContent>
</ra:DeviceAlertMessage>
</ra:Body>
</ra:GBCSResponse>
Figure 18 Device Alert 0x8F66 Future-Dated Command Successful GBZ Instruction Parse Response SampleFutureDatedCommandOutcomeDeviceAlert
<?xml version="1.0" encoding="UTF-8"?>
<ra:GBCSResponse xmlns:ds="http://www.w3.org/2000/09/xmldsig#"
xmlns:sr="http://www.dccinterface.co.uk/ServiceUserGateway"
xmlns:ra="http://www.dccinterface.co.uk/ResponseAndAlert"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.dccinterface.co.uk/ResponseAndAlert" schemaVersion="1.0">
<ra:Header>
<ra:BusinessOriginatorID>10-20-30-40-50-60-70-80</ra:BusinessOriginatorID>
<ra:BusinessTargetID>10-00-20-00-30-00-40-00</ra:BusinessTargetID>
<ra:OriginatorCounter>150</ra:OriginatorCounter>
<ra:GBCSHexadecimalMessageCode>00CD</ra:GBCSHexadecimalMessageCode>
</ra:Header>
<ra:Body>
<ra:DeviceAlertMessage>
<ra:DeviceAlertContent>
<ra:GBCSHexAlertCode>8F66</ra:GBCSHexAlertCode>
<ra:AlertDescription> Future Dated Command Successful Device Alert</ra:AlertDescription>
<ra:Timestamp>2014-05-04T18:13:51.00</ra:Timestamp>
<ra:Payload>
<ra:FutureDatedCommandOutcomeDeviceAlert>
<ra:GBZFutureDatedAlert>
<ra:FutureDatedCommandMessageCode>006B</ra:FutureDatedCommandMessageCode>
<ra:FutureDatedCommandOriginatorCounter>130</ra:FutureDatedCommandOriginatorCounter>
<ra:GBZFDInstructionIdentification>
<ra:ExtendedHeaderClusterID>0707</ra:ExtendedHeaderClusterID>
<ra:FrameControl>01</ra:FrameControl>
<ra:CommandIdentifier>02</ra:CommandIdentifier>
</ra:GBZFDInstructionIdentification>
</ra:GBZFutureDatedAlert>
</ra:FutureDatedCommandOutcomeDeviceAlert>
</ra:Payload>
</ra:DeviceAlertContent>
</ra:DeviceAlertMessage>
</ra:Body>
</ra:GBCSResponse>
Figure 19 Device Alert 0x8F66 Future-Dated Firmware Activation Parse Response SampleFutureDatedCommandOutcomeDeviceAlert
<?xml version="1.0" encoding="UTF-8"?>
<ra:GBCSResponse xmlns:ds="http://www.w3.org/2000/09/xmldsig#"
xmlns:sr="http://www.dccinterface.co.uk/ServiceUserGateway"
xmlns:ra="http://www.dccinterface.co.uk/ResponseAndAlert"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.dccinterface.co.uk/ResponseAndAlert" schemaVersion="1.0">
<ra:Header>
<ra:BusinessOriginatorID>10-20-30-40-50-60-70-80</ra:BusinessOriginatorID>
<ra:BusinessTargetID>10-00-20-00-30-00-40-00</ra:BusinessTargetID>
<ra:OriginatorCounter>50</ra:OriginatorCounter>
<ra:GBCSHexadecimalMessageCode>00CA </ra:GBCSHexadecimalMessageCode>
</ra:Header>
<ra:Body>
<ra:DeviceAlertMessage>
<ra:DeviceAlertContent>
<ra:GBCSHexAlertCode>8F66</ra:GBCSHexAlertCode>
<ra:AlertDescription>Update Security Credentials Device Alert</ra:AlertDescription>
<ra:Timestamp>2014-05-04T18:13:51.00</ra:Timestamp>
<ra:Payload>
<ra:FutureDatedCommandOutcomeDeviceAlert >
<ra:FirmwareActivationDeviceAlert>
<ra:ExecutionDateTime>2014-05-04T18:13:41.00</ra:ExecutionDateTime>
<ra:OriginatorCounterFromCommand>12345</ra:OriginatorCounterFromCommand>
<ra:ActivateImageResponseCode ResponseCode="0">
<ra:ASN1Status>success</ra:ASN1Status>
</ra:ActivateImageResponseCode>
<ra:FirmwareVersion>1100EEFF</ra:FirmwareVersion>
</ra:FirmwareActivationDeviceAlert>
</ra:FutureDatedCommandOutcomeDeviceAlert >
</ra:Payload>
</ra:DeviceAlertContent>
</ra:DeviceAlertMessage>
</ra:Body>
</ra:GBCSResponse>