DCC User Gateway Interface. Design Specification. Annex - Service Request Definitions 16 DCC Alerts

Transcription

1 DCC User Gateway Interface Design Specification Annex - Service Request Definitions 16 DCC Alerts Author: DCC Version: v0.8 Draft Date: 12 th September 2014 Page 1 of 30

2 Contents 16 DCC Alerts Service Request Responses DCC Alert Message Response... 3 Page 2 of 30

3 16 DCC Alerts DCC Alerts are unsolicited messages generated by the DCC Service Data Systems and sent to the DCC Service Users. The recipient is defined within the DCC Alert. See Main Document of this documentation set section 13 for the list of possible DCC Alerts and their triggers Service Request Service Requests are not applicable to DCC Alerts, since they are unsolicited messages Responses The Service Response message type for DCC Alerts is specific to them. The AsynchronousServiceResponse XML element of the XSD (see XML Schema document 3 of this documentation set) defines the structure of the Asynchronous Service Response. For DCC Alerts, the ResponseCode will depend on the DCC Alert type. See section and Main Document of this documentation set section 12.3 for the full list of generic error / response codes DCC Alert Message Response Format This is the only response type applicable to DCC Alerts. See Main Document of this documentation set section Depending on the data included in the DCC Alert, the DCC Alert responses have been divided into 5 67 types: 1. Power Status ChangeOutage Event 2. Device Status Change Event 3. DSP Schedule Removal 4. Command Failure 5. Firmware Distribution Failure 6. Update HAN Device Log Result 5.7. Change Of Supplier The following sections describe the format and specific data items of the DCC Alerts and each of their types. DCC Alerts are defined in the XSD DCCAlertMessage DCCAlert XML element. Page 3 of 30

4 Page 4 of 30

5 Formatted: Font: Italic, Font color: Blue Figure 1 DCC Alert Response Structure Specific Data Items Data Item Description / Valid Set Type Mandatory for Alert Default Units Formatted Table Sensitivity Codes 1 PowerStatusChangeEventPow eroutageevent DeviceStatusChangeEvent DSPScheduleRemoval The trigger event indicates that a device power has failed or been restored The trigger event indicates that a device has been withdrawn from Inventory or its status has changed The trigger event indicates that a DSP Schedule is to be deleted sr:powerstatuschangeeventpo weroutageevent (see PowerOutageEvent Data Items DefinitionPowerStatusChangeEv ent Data Items DefinitionPowerStatusChangeEv ent Data Items Definition) sr:devicestatuschangeevent (see DeviceStatusChangeEvent Data Items DefinitionDeviceStatusChangeE vent Data Items DefinitionDeviceStatusChangeE vent Data Items DefinitionDeviceStatusChangeE vent Data Items Definition) sr:dspscheduleremoval (see DSPScheduleRemoval Data Items DefinitionDSPScheduleRemoval Data Items DefinitionDSPScheduleRemoval Data Items DefinitionDSPScheduleRemoval Data Items Definition) AD1 and AD2 N1, N2, N8, N9 and N16 N4, N5, N6 and N17 None N/A Non- Formatted: Table Text - Centre, Space After: 0 pt Field Code Changed Formatted: None N/A Non- Field Code Changed Formatted: Table bullet 2, Space After: 0 pt Field Code Changed None N/A Formatted: Non- Field Code Changed Page 5 of 30

6 Data Item Description / Valid Set Type Mandatory for Alert Default Units Formatted Table Sensitivity Codes 1 CommandFailure FirmwareDistributionFailure UpdateHANDeviceLogResult ChangeOfSupplier The trigger event indicates that a Command has failed The trigger event indicates that a Firmware Distribution Command to the CSP has failed, at least for some of the Devices The trigger event indicates if a Command to Update a Communications Hub Whitelist Update (add or remove a Device) has succeeded or failed The trigger event indicates if an Update Security Credentials (CoS) has succeeded or has failed the CoS Party Access Control sr:commandfailure (see CommandFailure Data Items DefinitionCommandFailure Data Items DefinitionCommandFailure Data Items Definition CommandFailure Data Items Definition)) sr:firmwaredistributionfailure (see FirmwareDistributionFailure Data Items DefinitionFirmwareDistributionFa ilure Data Items DefinitionFirmwareDistributionFa ilure Data Items DefinitionFirmwareDistributionFa ilure Data Items Definition) sr: UpdateHANDeviceLogResult (see UpdateHANDeviceLogResult Data Items Definition) sr:changeofsupplier (see ChangeOfSupplier Data Items Definition) N3, N7, N10, N11, N12, N13, N14 and, N15 N18 and, N19, N20, N21, N22 and N23 N24, N25 N26, N27 Table 1 DCC Alert Service Response Data Items None N/A Non- Formatted: Indent: Left: 0 cm None N/A Non- Field Code Changed None N/A Non- None N/A Non- Formatted: Formatted: 1 N/A for all other DCC Alert Codes PowerStatusChangeEventPowerOutageEvent PowerOutageEvent Format PowerStatusChangeEvent Format Formatted: Normal DCC Alerts Power Status Change Event is defined in the XSD PowerStatusChangeEvent PowerOutageEvent XML element. Page 6 of 30

7 Formatted: Indent: Left: 1.5 cm Figure 222 DCC Alert Response PowerStatusChangeEvent PowerOutageEvent Structure PowerStatusChangeEvent Data Items Definition PowerOutage The trigger event indicates that a device power has failed sr:powerstatuschange (see PowerStatusChange Data Items DefinitionPowerStatusC hange Data Items Definition) AD1: Yes AD2: N/A None N/A Non- Field Code Changed PowerRestore The trigger event indicates that a device power has been restored sr:powerrestore (see PowerRestore Data Items DefinitionPowerRestore Data Items Definition) AD1: N/A AD2: Yes None N/A Non- Table 2 DCC Alert Asynchronous Service Response - PowerStatusChangeEvent Data Items Field Code Changed PowerRestore Data Items Definition Page 7 of 30

8 PowerStatusChange PowerOutageDuration The trigger event indicates that a device power has failed or been restored The trigger event indicates the duration of the last power outage on the device (from the time of the actual outage to the restore). This value is provided by the CSP sr:powerstatuschange (see PowerStatusChange Data Items DefinitionPowerStatusC hange Data Items Definition) xs:positiveinteger Yes None Seconds Non- Table 3 DCC Alert Asynchronous Service Response - PowerRestore Data Items Field Code Changed PowerOutageEvent Data Items DefinitionPowerStatusChange Data Items Definition CommsHubDeviceID StartDateTime MPxN The Device ID of the Communications Hub that reported the Power Outage or Restore The timestamp when the Power Outage / Restore started. This value is provided by the CSP DCC Alerts sent to User Roles: EIS and ENO. The primary import MPAN of the Electricity Smart Meter associated with the Communications Hub Function. sr:eui (see Annex section 17see Main Document of this documentation set section 9.2) xs:timedatetime sr:importmpxn (Restriction of xs:string (min length = 1, max length = 1313)) Formatted: Indent: Left: 0 cm Formatted: List Paragraph GIS and GNO. The MPRN of the Gas Smart Meter associated with the Communications Hub Function.The primary MPAN for the Electricity Smart Meter, or MPRN for the Gas Smart Meter associated with the Communications Hub. For dual fuel sites supplied by a single energy supplier, the MPAN shall returned. Formatted: List Paragraph, Don't add space between paragraphs of the same style, Bulleted + Level: 1 + Aligned at: 0 cm + Indent at: 0.63 cm, Font color: Auto Formatted: List Paragraph Table 224 DCC Alert Asynchronous Service Response - PowerStatusChange PowerOutageEvent Data Items DeviceStatusChangeEvent DeviceStatusChangeEvent Format Page 8 of 30

9 DCC Alerts Device Status Change Event is defined in the XSD DeviceStatusChangeEvent XML element. Formatted: Font: (Default) Times New Roman, 0 pt, Font color: Black, Character scale: 0%, Border: : (No border), Pattern: Clear (Black) Figure 3 DCC Alert Response DeviceStatusChangeEvent Structure Page 9 of 30

10 Figure 4 DCC Alert Response DeviceStatusChangeEvent DeviceCommissioning MeterCommissioning Structure Page 10 of 30

11 Figure 5 DCC Alert Response DeviceStatusChangeEvent DeviceDecommissioningOrWithdrawal MeterDecommissioningOrWithdrawal Structure Formatted: Normal Figure 6 DCC Alert Response DeviceStatusChangeEvent DeviceRemovedFromInventory Structure Formatted: Normal Figure 7 DCC Alert Response DeviceStatusChangeEvent CHFDecommissioning Structure Formatted: Normal DeviceStatusChangeEvent Data Items Definition DeviceID The Device ID which status is changing sr:eui (see Main Document of this documentation set Asnnex section 9.217) DeviceStatusChange The type of Device Status Change sr:devicestatuschange Page 11 of 30

12 Table 335 DCC Alert Asynchronous Service Response - DeviceStatusChangeEvent Data Items DeviceStatusChange Data Items Definition Data Item Description / Valid Set Type Mandatory 1 Default Units Sensitivity DeviceCommissioningM etercommissioning DeviceDecommissionin gorwithdrawalmeterde commissioningorwithdr awal DeviceRemovedFromIn ventory CHFDecommissioning Device Meter Commissioning details Device Decommissioning / Withdrawal details Device in a status of pending for > 12 months has been removed from Inventory Communications Hub Function Decommissioning detailsed sr:meterstatuschangemeter MPxNsCommissioning (see MeterCommissioning Data Items DefinitionMeterMPxNs Data Items DefinitionMeterStausChange Data Items Definition) sr:devicedecommissioning OrWithdrawalMeterDecomm issioningorwithdrawal (see MeterDecommissioningOrWi thdrawal Data Items DefinitionMeterDecommissio ningorwithdrawal Data Items DefinitionMeterDecommissio ningorwithdrawal Data Items DefinitionDeviceDecommissi oningorwithdrawal Data Items Definition) sr:deviceremovedfrominve ntory (empty included in the XML to describe DCC Alert Type)N/A sr:chfdecommissioning (empty included in the XML to describe DCC Alert Type)??? NoN16: Yes Otherwise: N/A N1, N2: Yes Otherwise: N/ANo N8: Yes Otherwise: N/ANo N9: Yes Otherwise: N/ANo None N/A Non- None N/A Non- N/A N/A Non- N/ A Formatted: Superscript None N/A Non- Table 446 DCC Alert Asynchronous Service Response - DeviceStatusChange Data Items 1 The DCC Alert will include either DeviceCommissioning or DeviceDecommissioningOrWithdrawanonly one of the Data Items in the choice MeterCommissioning Data Items Definition Field Code Changed Field Code Changed Field Code Changed Formatted: Formatted: Formatted: Highlight MeterMPxNs MPxNs associated to the Meter sr:metermpxns (see MeterMPxNs Data Items Definition) Page 12 of 30

13 ESMEVariant Electricity Smart Metering Equipment Variant. Valid set: A. Single Element B. Twin Element C. Polyphase AD. Single Element with ALCS BD. Twin Element with ALCS CD. Polyphase with ALCS ADE. Single Element with ALCS and Boost Function BDE. Twin Element with ALCS and Boost Function CDE. Polyphase with ALCS and Boost Function sr:esmevariant Restriction of xs:string (Enumeration) DeviceType = ESME: Yes Otherwise: Table 5 DCC Alert Service Response - MeterCommissioning Data Items N/A None N/A Non- Formatted: Left Formatted: List Paragraph, Space After: 3 pt, Bulleted + Level: 1 + Aligned at: 0 cm + Indent at: 0.63 cm Formatted: Caption MeterStausChange MeterMPxNs Data Items Definition ImportMPxN The reference number identifying an Import electricity or a gas metering point sr:importmpxn (Restriction of xs:string (min length = 1, max length = 1313)) SecondaryImportMPAN The reference number identifying a Twin Element Import electricity secondary metering point sr:mpan (Restriction of xs:string (min length = 1, max length = 13)) Twin Element Electricity Smart Meter: YesNo ElseOtherwise: N/A None N/A Non- ExportMPAN The reference number identifying an Export electricity metering point sr:mpan (Restriction of xs:string (min length = 1, max length = 13)) Export Electricity Smart Meter: YesNo ElseOtherwise: Table 667 DCC Alert Asynchronous Service Response - MeterStatusChange MeterMPxNs Data Items N/A None N/A Non- Formatted: Highlight DeviceDecommissioningOrWithdrawal MeterDecommissioningOrWithdrawal Data Items Definition Page 13 of 30

14 MeterDecommissionOr Withdrawal MPxNs associated to the Meter sr:meterstatuschangemeter MPxNs (see MeterMPxNs Data Items DefinitionMeterMPxNs Data Items DefinitionMeterMPxNs Data Items DefinitionMeterStausChange Data Items Definition) Field Code Changed AssociatedType1Device Type 1 devices Associated to the Device being Decommissioned / Withdrawn sr:associatedtype1device (see AssociatedType1Device Data Items DefinitionAssociatedType1D evice Data Items DefinitionAssociatedType1D evice Data Items DefinitionAssociatedType1D evice Data Items Definition) Table 778 DCC Alert Asynchronous Service Response - DeviceDecommissioningOrWithdrawal Data Items No 1 None N/A Non- Field Code Changed 1 All associated type Type 1 devices are to be included AssociatedType1Device Data Items Definition DeviceID Device ID of the Type 1 associated devicedevice sr:eui (see Annex section 17see Main Document of this documentation set section 9.2) DeviceType Device Type of the Type 1 associated device Valid set: ElectricitySmartMet er GasSmartMeter GasProxy CommunicationsHu bfunction HCALCS PPMID sr:devicetype (Restriction of xs:string (Enumeration)) Table 889 DCC Alert Asynchronous Service Response AssociatedType1Device Data Items DSPScheduleRemoval DSPScheduleRemoval Format DCC Alerts DSP Schedule Removal is defined in the XSD DSPScheduleRemoval XML element. There is one DSPScheduleRemoval DCC Alert for each DSP Schedule being removed. Page 14 of 30

15 Figure 886 DCC Alert Response DSPScheduleRemoval Structure DSPScheduleRemoval Data Items Definition DSPScheduleID ID of the DSP Schedule being removed xs:positiveinteger DeviceID The Device ID for which the DSP Schedule is being removed sr:eui (see Annex section 17see Main Document of this documentation set section 9.2) Table 9910 DCC Alert Asynchronous Service Response DSPScheduleRemoval Data Items CommandFailure CommandFailure Format DCC Alerts CommandFailure is defined in the XSD CommandFailure XML element. Figure 997 DCC Alert Response CommandFailure Structure CommandFailure Data Items Definition Page 15 of 30

16 CommandRequestID Request ID of the Command that failed sr:requestidtype (see Annex section17see Main Document of this documentation set section 9.2) DSPScheduleID For DSP Scheduled Commands, ID of the DSP Schedule associated to the Command xs:positiveinteger No 1 None N/A Non- DeviceID The Device ID for which the Command failed sr:eui (see Annex section 17see Main Document of this documentation set section 9.2) Table DCC Alert Asynchronous Service Response CommandFailure Data Items 1 Only applicable to DSP Scheduled Commands FirmwareDistributionFailure Format FirmwareDistributionFailure Format DCC Alerts FirmwareDistributionFailure is defined in the XSD FirmwareDistributionFailure XML element. Page 16 of 30

17 Figure DCC Alert Response FirmwareDistributionFailure Structure Formatted: Normal FirmwareDistributionFailure Data Items Definition UpdateFirmwareReques tid Request ID of the Update Firmware Service Request associated to the Command that failed sr:requestidtype (see Annex section17see Main Document of this documentation set section 9.2) CommsHubAndMeterID s Comma separated list of Comms Hub Function ID concatenated to ; and to Comms Hub and Meter Device ID pairs (each with the sr:eui format defined in Annex section 17) that: Tthe CSP wasn t able to identify - N19 Were included in the Command that failed CSP validation N18, N20, N21 Were included in the Command that failed delivery to the CSP N22 Were included in the Command for which no Validation Response was received from the CSP N23 sr:deviceidlist (Restriction of xs:string (min length = 23 pattern = ([A-Fa-f0-9]{2}-[A- Fa-f0-9]{2}-[A-Fa-f0-9]{2}-[A- Fa-f0-9]{2}-[A-Fa-f0-9]{2}-[A- Fa-f0-9]{2}-[A-Fa-f0-9]{2}-[A- Fa-f0-9]{2},)*([A-Fa-f0-9]{2}- [A-Fa-f0-9]{2}-[A-Fa-f0-9]{2}- [A-Fa-f0-9]{2}-[A-Fa-f0-9]{2}- [A-Fa-f0-9]{2}-[A-Fa-f0-9]{2}- [A-Fa-f0-9]{2}) ))sr:commshubandm eteridsrestriction of xs:string (pattern = (([A-Faf0-9]{2}-[A-Fa-f0-9]{2}-[A-Faf0-9]{2}-[A-Fa-f0-9]{2}-[A-Faf0-9]{2}-[A-Fa-f0-9]{2}-[A-Faf0-9]{2}-[A-Fa-f0-9]{2};)([A- Fa-f0-9]{2}-[A-Fa-f0-9]{2}-[A- Fa-f0-9]{2}-[A-Fa-f0-9]{2}-[A- Fa-f0-9]{2}-[A-Fa-f0-9]{2}-[A- Fa-f0-9]{2}-[A-Fa-f0-9]{2}),)*(([A-Fa-f0-9]{2}-[A- Fa-f0-9]{2}-[A-Fa-f0-9]{2}-[A- Fa-f0-9]{2}-[A-Fa-f0-9]{2}-[A- Fa-f0-9]{2}-[A-Fa-f0-9]{2}-[A- Fa-f0-9]{2};)([A-Fa-f0-9]{2}- [A-Fa-f0-9]{2}-[A-Fa-f0-9]{2}- [A-Fa-f0-9]{2}-[A-Fa-f0-9]{2}- [A-Fa-f0-9]{2}-[A-Fa-f0-9]{2}- [A-Fa-f0-9]{2})) ) DCC Alert N18: N/A DCC Alert N19: Yes 1 Table DCC Alert Asynchronous Service Response FirmwareDistributionFailure Data Items None N/A Non- Formatted: Bulleted + Level: 1 + Aligned at: 0 cm + Indent at: 0.63 cm Formatted: Font color: Text 1 Formatted: Font: (Default) Arial, 8 pt Formatted: Font color: Text 1 Formatted: Font color: Text 1, Not Highlight Formatted: Not Highlight 1 Minimum of 1 and maximum of 50,000 pairsdevice IDs UpdateHANDeviceLogResult UpdateHANDeviceLogResult Format DCC Alerts UpdateHANDeviceLogResult is defined in the XSD UpdateHANDeviceLogResult XML element. Page 17 of 30

18 Formatted: Font: (Default) Times New Roman, 0 pt, Font color: Black, Character scale: 0%, Border: : (No border), Pattern: Clear (Black) Formatted: Font: (Default) Times New Roman, 0 pt, Font color: Black, Character scale: 0%, Border: : (No border), Pattern: Clear (Black) Figure 11 DCC Alert Response UpdateHANDeviceLogResult Structure Formatted: Normal Page 18 of 30

19 UpdateHANDeviceLogResult Data Items Definition Formatted: Left, Indent: Left: 0 cm, Space Before: 0 pt, After: 0 pt UpdateHANServiceReq uestid Request ID of the Update HAN Device Log Service Request. The DCC Alert Code indicates success (N24) or failure (N25) sr:requestidtype (see Main Document of this documentation set section 9.2Annex section17) Table 12 DCC Alert Asynchronous Service Response UpdateHANDeviceLogResult Data Items ChangeOfSupplier ChangeOfSupplier Format DCC Alerts ChangeOSupplier are defined in the XSD ChangeOfSupplier XML element. Formatted: Caption Figure 12 DCC Alert Response ChangeOfSupplier Structure ChangeOfSupplier Data Items Definition ChangeOfSupplierServi cerequestid Sent to the Update Security Credentials (CoS) sender. Request ID of the Update Security Credentails (CoS) Service Request. The DCC Alert Code (N26) indicates that the request has failed CoS Party Access Control or, for Future Dated Requests, DSP Access Control at the point the Request is to be sent to the CoS Party sr:requestidtype (see Annex section17) N26: Yes Otherwise: N/A None N/A Non- Page 19 of 30

20 DeviceChangeOfSuppli er Sent to the Old registered Import Supplier for the Device, together with DCC Alert Code N27 to inform them of the Change of Supplier sr:devicechangeofsupplier (see section ChangeOfSupplier Data Items Definition) N27: Yes Otherwise: N/A Table 13 DCC Alert Service Response ChangeOfSupplier Data Items None N/A Non- Field Code Changed DeviceChangeOfSupplier Data Items Definition DeviceID DeviceType MPxNs The Device ID which has changed Supplier Device Type that has changed Supplier Valid set: ESME GSME GPF HCALCS MPxN(s) associated to the Device, i.e. MPAN(s) for ESME and HCALCS MPRN for GSME or GPF sr:eui (see Annex section 17) sr:devicetype (Restriction of xs:string (Enumeration)) sr:metermpxns (see MeterMPxNs Data Items Definition) Table 14 DCC Alert Service Response DeviceChangeOfSupplier Data Items FirmwareDistributionFailure CommsHubAndMeterIDs Data Items Definition Formatted: List Paragraph, Space No None N/A After: 3 pt, Bulleted + Level: 1 + Non- Aligned at: 0 cm + Indent at: 0.63 cm, Font color: Black Formatted: Bulleted + Level: 1 + Aligned at: 0 cm + Indent at: 0.63 cm Formatted: Caption CommsHubDeviceID MeterDeviceID The Comms Hub Device ID for which the Command failed The Meter Device ID for which the Command failed sr:eui (see Main Document of this documentation set section 9.2) sr:eui (see Main Document of this documentation set section 9.2) Table 13 DCC Alert Asynchronous Service Response FirmwareDistributionFailure - CommsHubAndMeterIDs Data Items Relationship between DCC Alert Codes and Response Codes DCC Alert Code Response Codes AD1 AD2 N1 N2 N3 Page 20 of 30

21 DCC Alert Code Response Codes N4 N5 N6 N7 N8 N9 N10 N11 N12 N13 N14 N15 N16 N17 N18 N19 N20 N21 N22 N23 N24 N25 N26 E1, E3, E4, E5, E100, E1007 E30 E31 E20 E21 E43, E46, E47 E44 E1, E3, E4, E5, E100, E1007 Formatted: Font color: Text 1 Formatted: Font color: Text 1 Formatted: Font color: Text 1 Formatted: Font color: Text 1 Formatted: Font color: Text 1 Formatted: Font color: Text 1 Formatted: Font color: Text 1 N27 Table Relationship between DCC Alert Codes and Response Codes Formatted: Font color: Text DCC Alert Samples Power Outage A sample DCC Alert is given in Annex Introduction Appendix 4. The specific information for this DCC Alert is as follows: A sample Power Outage DCC Alert Asynchronous Service Response message document is as follows: Page 21 of 30

22 <?xml version="1.0" encoding="utf-8"?> <AsynchronousServiceResponse xmlns:ds=" xmlns=" xmlns:xsi=" <ResponseID>11-DB : :1000</ResponseID> <BusinessOriginatorID>11-DB </BusinessOriginatorID> <BusinessTargetID> </BusinessTargetID> <OriginatorCounter>1000</OriginatorCounter> <ResponseCode></ResponseCode> <ResponseDateTime> T07:10:12.0</ResponseDateTime> <DCCAlertMessage> <DCCAlertCode>AD1</DCCAlertCode> <DCCAlert> <PowerStatusChangeEventPowerOutageEvent> <PowerOutage> <CommsHubDeviceID>88-00-AA-BB-CC-DD-EE-FF</CommsHubDeviceID> <StartDateTime> T07:05: </StartDateTime> <MPxN>S </MPxN> </PowerOutage> </PowerStatusChangeEventPowerOutageEvent> </DCCAlert> </DCCAlertMessage> <ds:signature> <ds:signedinfo> <ds:canonicalizationmethod Algorithm=" </ds:canonicalizationmethod> <ds:signaturemethod Algorithm=" </ds:signaturemethod> <ds:reference> <ds:digestmethod Algorithm=" </ds:digestmethod> <ds:digestvalue>zgvmyxvsda==</ds:digestvalue> </ds:reference> </ds:signedinfo> <ds:signaturevalue>zgvmyxvsda==</ds:signaturevalue> </ds:signature> </AsynchronousServiceResponse> Formatted Table Figure Sample Power Outage DCC Alert Response Format Power Restore A sample Power Restore DCC Alert Response message document is as follows: Page 22 of 30

23 <?xml version="1.0" encoding="utf-8"?> <AsynchronousServiceResponse xmlns:ds=" xmlns=" xmlns:xsi=" <ResponseID>11-DB : :1000</ResponseID> <BusinessOriginatorID>11-DB </BusinessOriginatorID> <BusinessTargetID> </BusinessTargetID> <OriginatorCounter>1000</OriginatorCounter> <ResponseCode></ResponseCode> <ResponseDateTime> T07:10:12.0</ResponseDateTime> <DCCAlertMessage> <DCCAlertCode>AD2</DCCAlertCode> <DCCAlert> <PowerStatusChangeEvent> <PowerRestore> <PowerStatusChange> <CommsHubDeviceID>88-00-AA-BB-CC-DD-EE-FF</CommsHubDeviceID> <StartTime>07:05:53.000</StartTime> <MPxN>S </MPxN> </PowerStatusChange> <PowerOutageDuration>50</PowerOutageDuration> </PowerRestore> </PowerStatusChangeEvent> </DCCAlert> </DCCAlertMessage> <ds:signature> <ds:signedinfo> <ds:canonicalizationmethod Algorithm=" </ds:canonicalizationmethod> <ds:signaturemethod Algorithm=" </ds:signaturemethod> <ds:reference> <ds:digestmethod Algorithm=" </ds:digestmethod> <ds:digestvalue>zgvmyxvsda==</ds:digestvalue> </ds:reference> </ds:signedinfo> <ds:signaturevalue>zgvmyxvsda==</ds:signaturevalue> </ds:signature> </AsynchronousServiceResponse> Formatted Table Figure Sample Power Restore DCC Alert Response Format Meter Commissioning A sample DCC Alert is given in Annex Introduction Appendix 4. The specific information for this DCC Alert is as followsa sample Meter Commissioning DCC Alert Response message document is as follows: Page 23 of 30

24 <?xml version="1.0" encoding="utf-8"?> <AsynchronousServiceResponse xmlns:ds=" xmlns=" xmlns:xsi=" <ResponseID>11-DB : :1000</ResponseID> <BusinessOriginatorID>11-DB </BusinessOriginatorID> <BusinessTargetID> </BusinessTargetID> <OriginatorCounter>1000</OriginatorCounter> <ResponseCode></ResponseCode> <ResponseDateTime> T07:10:12.0</ResponseDateTime> <DCCAlertMessage> <DCCAlertCode>N16</DCCAlertCode> <DCCAlert> <DeviceStatusChangeEvent> <DeviceID>99-00-AA-BB-CC-DD-EE-FF</DeviceID> <DeviceStatusChange> <MeterCommissioning> <MeterMPxNs> <ImportMPxN>S </ImportMPxN> </MeterMPxNs> <ESMEVariant>A</ESMEVariant> </MeterCommissioning> </DeviceStatusChange> </DeviceStatusChangeEvent> </DCCAlert> </DCCAlertMessage> <ds:signature> <ds:signedinfo> <ds:canonicalizationmethod Algorithm=" </ds:canonicalizationmethod> <ds:signaturemethod Algorithm=" </ds:signaturemethod> <ds:reference> <ds:digestmethod Algorithm=" </ds:digestmethod> <ds:digestvalue>zgvmyxvsda==</ds:digestvalue> </ds:reference> </ds:signedinfo> <ds:signaturevalue>zgvmyxvsda==</ds:signaturevalue> </ds:signature> </AsynchronousServiceResponse> Figure 14 Sample Meter Commissioning DCC Alert Response Format Meter Decommissioning Or Withdrawal A sample DCC Alert is given in Annex Introduction Appendix 4. The specific information for this DCC Alert is as follows:a sample Meter Decommissioning Or Withdrawal DCC Alert Response message document is as follows: Formatted Table Page 24 of 30

25 <?xml version="1.0" encoding="utf-8"?> <AsynchronousServiceResponse xmlns:ds=" xmlns=" xmlns:xsi=" <ResponseID>11-DB : :1000</ResponseID> <BusinessOriginatorID>11-DB </BusinessOriginatorID> <BusinessTargetID> </BusinessTargetID> <OriginatorCounter>1000</OriginatorCounter> <ResponseCode></ResponseCode> <ResponseDateTime> T07:10:12.0</ResponseDateTime> <DCCAlertMessage> <DCCAlertCode>N1</DCCAlertCode> <DCCAlert> <DeviceStatusChangeEvent> <DeviceID>99-00-AA-BB-CC-DD-EE-FF</DeviceID> <DeviceStatusChange> <MeterDecommissioningOrWithdrawal> <MeterDecommissionOrWithdrawal> <ImportMPxN>S </ImportMPxN> </MeterDecommissionOrWithdrawal> </MeterDecommissioningOrWithdrawal> </DeviceStatusChange> </DeviceStatusChangeEvent> </DCCAlert> </DCCAlertMessage> <ds:signature> <ds:signedinfo> <ds:canonicalizationmethod Algorithm=" </ds:canonicalizationmethod> <ds:signaturemethod Algorithm=" </ds:signaturemethod> <ds:reference> <ds:digestmethod Algorithm=" </ds:digestmethod> <ds:digestvalue>zgvmyxvsda==</ds:digestvalue> </ds:reference> </ds:signedinfo> <ds:signaturevalue>zgvmyxvsda==</ds:signaturevalue> </ds:signature> </AsynchronousServiceResponse> Figure 15 Sample Meter Decommissioning Or Withdrawal DCC Alert Response Format Device Removed From Inventory A sample DCC Alert is given in Annex Introduction Appendix 4. The specific information for this DCC Alert is as followsa sample Device Removed From Inventory DCC Alert Response message document is as follows: Formatted Table Formatted... Formatted... Formatted... Page 25 of 30 Formatted...

26 <?xml version="1.0" encoding="utf-8"?> <AsynchronousServiceResponse xmlns:ds=" xmlns=" xmlns:xsi=" <ResponseID>11-DB : :1000</ResponseID> <BusinessOriginatorID>11-DB </BusinessOriginatorID> <BusinessTargetID> </BusinessTargetID> <OriginatorCounter>1000</OriginatorCounter> <ResponseCode></ResponseCode> <ResponseDateTime> T07:10:12.0</ResponseDateTime> <DCCAlertMessage> <DCCAlertCode>N8</DCCAlertCode> <DCCAlert> <DeviceStatusChangeEvent> <DeviceID>99-00-AA-BB-CC-DD-EE-FF</DeviceID> <DeviceStatusChange> <DeviceRemovedFromInventory/> </DeviceStatusChange> </DeviceStatusChangeEvent> </DCCAlert> </DCCAlertMessage> <ds:signature> <ds:signedinfo> <ds:canonicalizationmethod Algorithm=" </ds:canonicalizationmethod> <ds:signaturemethod Algorithm=" </ds:signaturemethod> <ds:reference> <ds:digestmethod Algorithm=" </ds:digestmethod> <ds:digestvalue>zgvmyxvsda==</ds:digestvalue> </ds:reference> </ds:signedinfo> <ds:signaturevalue>zgvmyxvsda==</ds:signaturevalue> </ds:signature> </AsynchronousServiceResponse> Formatted Table Figure 16 Sample Device Removed From Inventory DCC Alert Response Format CHF Decommissioning A sample DCC Alert is given in Annex Introduction Appendix 4. The specific information for this DCC Alert is as followsa sample CHF Decommissioning DCC Alert Response message document is as follows: Page 26 of 30

27 <?xml version="1.0" encoding="utf-8"?> <AsynchronousServiceResponse xmlns:ds=" xmlns=" xmlns:xsi=" <ResponseID>11-DB : :1000</ResponseID> <BusinessOriginatorID>11-DB </BusinessOriginatorID> <BusinessTargetID> </BusinessTargetID> <OriginatorCounter>1000</OriginatorCounter> <ResponseCode></ResponseCode> <ResponseDateTime> T07:10:12.0</ResponseDateTime> <DCCAlertMessage> <DCCAlertCode>N9</DCCAlertCode> <DCCAlert> <DeviceStatusChangeEvent> <DeviceID>99-00-AA-BB-CC-DD-EE-FF</DeviceID> <DeviceStatusChange> <CHFDecommissioning/> </DeviceStatusChange> </DeviceStatusChangeEvent> </DCCAlert> </DCCAlertMessage> <ds:signature> <ds:signedinfo> <ds:canonicalizationmethod Algorithm=" </ds:canonicalizationmethod> <ds:signaturemethod Algorithm=" </ds:signaturemethod> <ds:reference> <ds:digestmethod Algorithm=" </ds:digestmethod> <ds:digestvalue>zgvmyxvsda==</ds:digestvalue> </ds:reference> </ds:signedinfo> <ds:signaturevalue>zgvmyxvsda==</ds:signaturevalue> </ds:signature> </AsynchronousServiceResponse> Formatted Table Figure 17 Sample CHF Decomissioning DCC Alert Response Format DSP Schedule Removal A sample DCC Alert is given in Annex Introduction Appendix 4. The specific information for this DCC Alert is as followsa sample DSP Schedule Removal DCC Alert Response message document is as follows: <?xml version="1.0" encoding="utf-8"?> <AsynchronousServiceResponse xmlns:ds=" xmlns=" xmlns:xsi=" <ResponseID>11-DB : :1000</ResponseID> <BusinessOriginatorID>11-DB </BusinessOriginatorID> <BusinessTargetID> </BusinessTargetID> <OriginatorCounter>1000</OriginatorCounter> <ResponseCode></ResponseCode> <ResponseDateTime> T07:10:12.0</ResponseDateTime> <DCCAlertMessage> <DCCAlertCode>N4</DCCAlertCode> <DCCAlert> <DSPScheduleRemoval> <DeviceID>99-00-AA-BB-CC-DD-EE-FF</DeviceID> <DSPScheduleID>500</DSPScheduleID> </DSPScheduleRemoval> </DCCAlert> </DCCAlertMessage> <ds:signature> <ds:signedinfo> <ds:canonicalizationmethod Algorithm=" </ds:canonicalizationmethod> <ds:signaturemethod Algorithm=" </ds:signaturemethod> <ds:reference> <ds:digestmethod Algorithm=" </ds:digestmethod> <ds:digestvalue>zgvmyxvsda==</ds:digestvalue> </ds:reference> </ds:signedinfo> <ds:signaturevalue>zgvmyxvsda==</ds:signaturevalue> </ds:signature> </AsynchronousServiceResponse> Formatted Table Page 27 of 30

28 Figure 18 Sample DSP Schedule Removal DCC Alert Response Format Command Failure A sample DCC Alert is given in Annex Introduction Appendix 4. The specific information for this DCC Alert is as followsa sample Command Failure DCC Alert Response message document is as follows: <?xml version="1.0" encoding="utf-8"?> <AsynchronousServiceResponse xmlns:ds=" xmlns=" xmlns:xsi=" <ResponseID>11-DB : :1000</ResponseID> <BusinessOriginatorID>11-DB </BusinessOriginatorID> <BusinessTargetID> </BusinessTargetID> <OriginatorCounter>1000</OriginatorCounter> <ResponseCode></ResponseCode> <ResponseDateTime> T07:10:12.0</ResponseDateTime> <DCCAlertMessage> <DCCAlertCode>N3</DCCAlertCode> <DCCAlert> <CommandFailure> <CommandRequestID> :99-00-AA-BB-CC-DD-EE-FF:50</CommandRequestID> <DeviceID>99-00-AA-BB-CC-DD-EE-FF</DeviceID> </CommandFailure> </DCCAlert> </DCCAlertMessage> <ds:signature> <ds:signedinfo> <ds:canonicalizationmethod Algorithm=" </ds:canonicalizationmethod> <ds:signaturemethod Algorithm=" </ds:signaturemethod> <ds:reference> <ds:digestmethod Algorithm=" </ds:digestmethod> <ds:digestvalue>zgvmyxvsda==</ds:digestvalue> </ds:reference> </ds:signedinfo> <ds:signaturevalue>zgvmyxvsda==</ds:signaturevalue> </ds:signature> </AsynchronousServiceResponse> Formatted Table, Not Bold, Font color: Auto Formatted: Figure 19 Sample Command Failure DCC Alert Response Format Firmware Distribution Failure A sample DCC Alert is given in Annex Introduction Appendix 4. The specific information for this DCC Alert is as followsa sample Firmware Distribution Failure DCC Alert Response message document is as follows: Page 28 of 30

29 <?xml version="1.0" encoding="utf-8"?> Formatted Table <AsynchronousServiceResponse xmlns:ds=" xmlns=" xmlns:xsi=" <ResponseID>11-DB : :1000</ResponseID> <BusinessOriginatorID>11-DB </BusinessOriginatorID> <BusinessTargetID> </BusinessTargetID> <OriginatorCounter>1000</OriginatorCounter> <ResponseCode></ResponseCode> <ResponseDateTime> T07:10:12.0</ResponseDateTime> <DCCAlertMessage> <DCCAlertCode>N18</DCCAlertCode> <DCCAlert> <FirmwareDistributionFailure> <UpdateFirmwareRequestID> :11-DB :100</UpdateFirmwareRequestID> <CommsHubAndMeterIDs>1F-2D-3E-4A-5B-6C-76-87; E-4A-5B-6C-76-87,2F-3D-4E-5A-6B-7C-76-87;, E-4A-5B-6C-76-87</CommsHubAndMeterIDs> </FirmwareDistributionFailure> </DCCAlert> </DCCAlertMessage> <ds:signature> <ds:signedinfo> <ds:canonicalizationmethod Algorithm=" </ds:canonicalizationmethod> <ds:signaturemethod Algorithm=" </ds:signaturemethod> <ds:reference> <ds:digestmethod Algorithm=" </ds:digestmethod> <ds:digestvalue>zgvmyxvsda==</ds:digestvalue> </ds:reference> </ds:signedinfo> <ds:signaturevalue>zgvmyxvsda==</ds:signaturevalue> </ds:signature> </AsynchronousServiceResponse> Figure 20 Sample Firmware Distribution Failure DCC Alert Response Format Update HAN Device Log Result A sample DCC Alert is given in Annex Introduction Appendix 4. The specific information for this DCC Alert is as followsa sample Update HAN Device Log Result DCC Alert Response message document is as follows: <?xml version="1.0" encoding="utf-8"?> <AsynchronousServiceResponse xmlns:ds=" xmlns=" xmlns:xsi=" <ResponseID>11-DB : :1000</ResponseID> <BusinessOriginatorID>11-DB </BusinessOriginatorID> <BusinessTargetID> </BusinessTargetID> <OriginatorCounter>1000</OriginatorCounter> <ResponseCode></ResponseCode> <ResponseDateTime> T09:12:25.0</ResponseDateTime> <DCCAlertMessage> <DCCAlertCode>N24</DCCAlertCode> <DCCAlert> <UpdateHANDeviceLogResult> <UpdateHANDeviceLogServiceRequestID> :11-DB :100</UpdateHANDeviceLogServiceRequestID> </UpdateHANDeviceLogResult> </DCCAlert> </DCCAlertMessage> <ds:signature> <ds:signedinfo> <ds:canonicalizationmethod Algorithm=" </ds:canonicalizationmethod> <ds:signaturemethod Algorithm=" </ds:signaturemethod> <ds:reference> <ds:digestmethod Algorithm=" </ds:digestmethod> <ds:digestvalue>zgvmyxvsda==</ds:digestvalue> </ds:reference> </ds:signedinfo> <ds:signaturevalue>zgvmyxvsda==</ds:signaturevalue> </ds:signature> </AsynchronousServiceResponse> Figure 21 Sample Update HAN Device Log Result DCC Alert Response Format Page 29 of 30 Formatted Table Formatted: Caption

30 Change Of Supplier Result A sample DCC Alert is given in Annex Introduction Appendix 4. The specific information for this DCC Alert is as follows: <DCCAlertMessage> <DCCAlertCode>N27</DCCAlertCode> <DCCAlert> <ChangeOfSupplier> <DeviceChangeOfSupplier> <DeviceID> </DeviceID> <DeviceType>ESME</DeviceType> <MPxNs> <ImportMPxN> </ImportMPxN> </MPxNs> </DeviceChangeOfSupplier> </ChangeOfSupplier> </DCCAlert> </DCCAlertMessage> Figure 22 Sample Change Of Supplier DCC Alert Response Format Formatted Table Formatted: Caption Page 30 of 30