Service Reference Variant

11.3 · Activate Firmware

Service details

Identifiers, rules, and applicability

Service reference
11.3
Service Reference Variant
11.3
DUIS section
3.8.125
Command variants
4, 5, 6, 7
DUIS possible responses
AcknowledgementResponse to Transform Request - PreCommand FormatService Response from Device - GBCSPayloadFutureDatedDeviceAlertMessageResponse to a Command for Local Delivery Request - LocalCommand FormatCountersigned SMETS1 Response
Critical
Yes
Sensitive response
No
Protection against replay
No
On demand
Yes
Future dated
Device
DSP scheduled
No
DCC only
No
SMETS1 applicability
Yes
SAPC requirement
Mandatory
DUIS applicability
3.0, 3.1, 4.0, 5.0, 5.1, 5.2, 5.3

Cross-specification evidence

SMETS/CHTS to GBCS Mapping

This section shows the SMETS and CHTS attributes that can be read or written by the identified GBCS Use Case. Command requirements are shown separately from the mapped attributes.

CS061 command0 attributes0x0012ESME

Command mapped to CS06

No mapped data attributes.

Specific Errors

Response codes and descriptions

No specific validation is defined for this SRV.

GBCS Use Case

Use cases, device coverage, and applicability

Use Case / Message Code
CS060x0012
DUIS Applicability
v3.0 – v5.3v5.0 – v5.3
GBCS Applicability
v1.0 – v4.3v4.1 – v4.3
GBCS Criticality
Critical
Sensitive Response
No
Future Dated
Device
GBT
No
SMETS1 Applicable
NoYes
Eligible Roles
EISESMEHCALCS
GISGSME
SMETS1 note

HCALCS is not a valid SMETS1 Device Type

DUIS Service Definition

Data items and DCC processing

Request data items

Table 257: ActivateFirmware (sr:ActivateFirmware) data items
Data ItemDescription / Allowable valuesTypeMandatoryDefaultUnits
ExecutionDateTimeA User shall only add this Data Item to the Service Request where they require the Service Request to be executed at a future date and time. The date and time at which the firmware will be activated • Date-time in the future that is either <= current date + 30 days or the date = ‘3000-12-31T00:00:00Z’xs:dateTimeNoNoneN.A
FirmwareHashHash calculated over the Manufacturer Image part of the FirmwareImage as defined by GBCS. The Firmware Hash as held in the CPL and presented in the format XX..XX (64 characters) where each X is one of the characters 0 to 9 or A to F. This data item must align with the value on the CPL (excluding the colon separator between octet values). Note that a hexBinary value of length 32 is defined as 32 octets; an octet is represented as 2 characters.Restriction of xs:hexBinary (minLength = 32, maxLength = 32)YesNoneN/A

Additional System Processing - DUIS

The DCC Systems shall monitor all Responses received to this Service Request.

Where the DCC identifies any Response where the current Firmware Version returned by the Device matches an entry on the CPL for that Device Model and that Firmware Version is different to the value currently held in the Smart Metering Inventory for that Device, an update to the Smart Metering Inventory shall be made by the DCC.

The DCC Systems shall update the DeviceFirmwareVersion data item within the Smart Metering Inventory to record the new DeviceFirmwareVersion value for the specified Device ID received in the Response. Where the DeviceFirmwareVersion for the specified Device is now the current valid version, and the Device Status was ‘Suspended’ and the Firmware Version returned by the Device matches an entry on the CPL for that Device Model with a status of “Current” the DCC Systems shall update the Device Status to the status it held immediately prior to its suspension and DCC Alert N29 will be sent to the Responsible Supplier and to the Electricity Distributor or Gas Transporter.

If the Firmware Version returned by the Device matches an entry on the CPL for that Device Model with a status of ‘Removed’, the SMI Firmware Version will be updated, and the Device Status will be set to ‘Suspended’. In this case DCC Alert N50 will be sent to the Responsible Supplier. In addition, DCC Alert N28 will be sent to the Responsible Supplier and to the Electricity Distributor or Gas Transporter to notify the suspension of the Device. All DSP Future Dated and Scheduled Service Requests shall be deleted for the ‘Suspended’ Device(s) and DCC Alert N40 and N41 will be sent to the Users responsible for those Service Requests.

If the Firmware Version returned by the Device is invalid (doesn’t match an entry on the CPL for that Device Model) and that Firmware Version is different to the value currently held in the Smart Metering Inventory for that Device, DCC Alert N51 will be sent to the Responsible Supplier and the Smart Metering Inventory Firmware Version will be updated with the Firmware Version returned by the Device. As there is no entry on the CPL, the Device Status of the Device will be set to ‘Suspended’ and an additional DCC Alert N28 will be sent to the Responsible Supplier and to the Electricity Distributor or Gas Transporter. All DSP Future Dated and Scheduled Service Requests shall be deleted for the ‘Suspended’ Device and DCC Alerts N40 and N41 will be sent to the Users responsible for those Service Requests.

DUGIDS service matrix

DUGIDS DS.0226 Table 36 footnote extract

FootnoteExtractColumnCell ValueSource
8Yes for SMETS1 DevicesProtection Against ReplayYesDS.0226 Table 36 Service Request Matrix

Message Patterns & Examples

Pattern explorer

Open Message Patterns →

SMETS1 Supporting Requirements

Device-model variations and equivalent steps

Review the Section 18 requirements and their applicability across the documented manufacturer, Device Type, model, and firmware profiles.

Open S1SR Requirements →