Service Reference Variant

11.1 · Update Firmware

Service details

Identifiers, rules, and applicability

Service reference
11.1
Service Reference Variant
11.1
DUIS section
3.8.123
Command variants
8
DUIS possible responses
AcknowledgementResponse to a Non-Device Service Request
Critical
No
Sensitive response
No
Protection against replay
No
On demand
No
Future dated
No
DSP scheduled
No
DCC only
Yes
SMETS1 applicability
Yes
SAPC requirement
Not stated
DUIS applicability
3.0, 3.1, 4.0, 5.0, 5.1, 5.2, 5.3

Specific Errors

Response codes and descriptions

Response CodeResponse Code Description
E110101
The Firmware Version is not approved. The Firmware version ID does not align with an entry on the Central Products List.
W110101
The Update Firmware Warning contains between one and five lists of Device IDs for which the validation failed for each DeviceID: InvalidDeviceIDList . The DeviceID does not exist or the User is not the Meter or HCALCS Import Supplier NotCommissionedDeviceIDList. The Meter status is not ‘Commissioned’ or ‘Suspended’ or the Device is not a Meter or a HCALCS NotApplicableFirmwareDeviceIDList. The Firmware Version is not applicable to the Device OtherRequestsInProgressList. The Device already has another Firmware update request in progress.InvalidGBCSVersionList. The CHF associated with the HCALCS Device has a GBCS Version prior to v4.1,or the HCALCS Device currently has a GBCS Version that is prior to v4.1.
E110102
The firmware is not marked as active in the Central Products List and Smart Metering Inventory.
E110103
The DCC Systems calculated Hash value over the Manufacturer Image part of the FirmwareImage provided by the User within the Service Request differs from that held in the CPL for the specified FirmwareVersion.
E110105
The firmware image is not constructed as per the GBCS definition, i.e. the FirmwareImage does not contain both an OTA Header and a Firmware Image concatenated together , or where the Target Device is a SMETS2+ Device, the Length of the base64 encoded version of the GBCS defined Firmware “OTA Upgrade Image” exceeds 1024000.

Source: DUIS 3.8.123.3

SMETS1-specific validation

Additional SMETS1 conditions are shown separately from the SRV-specific DUIS table.

SMETS1 supplementary validation
W110101

Invalid conditions listed in this Update Firmware warning may relate to a SMETS1 CHF, a SMETS1 PPMID or a Smart Meter. An additional condition for listing a SMETS1 CHF or a SMETS1 PPMID in the InvalidDeviceIDList is where the DCC User submitting the Update Firmware Service Request is not the Responsible Supplier for the SMETS1 ESME which is connected to the same home area network as the SMETS1 CHF / PPMIDThe Response Code description within the InvalidDeviceIDList shall not contain the OtherRequestsInProgressList Update Firmware Warning as this is not applicable for SMETS1 Devices.

Applies to: Amended condition for SMETS1 Devices

Source: DUIS 1.4.6 Table 2

GBCS Use Case

Use cases, device coverage, and applicability

Instruction
UpdateFirmware
DUIS Applicability
v3.0 – v5.3
GBCS Applicability
DCC Only
GBCS Criticality
N/A
Sensitive Response
No
Future Dated
No
GBT
No
SMETS1 Applicable
Yes
Eligible Roles
EISGISDSP

DUIS Service Definition

Data items and DCC processing

Request data items

Table 254: UpdateFirmware (sr:UpdateFirmware) data items
Data ItemDescription / Allowable valuesTypeMandatoryDefaultUnits
FirmwareImageThe Firmware Image corresponding to the Firmware Version This is a base64 encoded version of the GBCS defined Firmware “OTA Upgrade Image”. The Firmware Image is the full OTA Upgrade Image as defined in GBCS. Note that this includes not only the Manufacturer Image but also additional signature and OTA Header information. Please see GBCS for details of how to construct the OTA Upgrade ImageRestriction of xs:base64Binary (max Length = 10240000)YesNoneN/A
FirmwareVersionAn identifier representing a firmware image that has been approved for release by the User concerned. The Firmware version as held in the CPL and presented in the format XXXXXXXX where each X is one of the characters 0 to 9 or A to F. This value must align with the firmware version value listed on the Central Products List (excluding the colon separator between octet values) and the Firmware Hash held on the CPL must match the Manufacturer Image Hash pursuant to clause 6.1(i) of the Service Request Processing Document. For avoidance of doubt, there is no direct comparison made between this FirmwareVersion value to the File Version value contained in the OTA Header (as defined by GBCS).sr:FirmwareVersion (Restriction of xs:string (minLength=1, maxLength = 8))YesNoneN/A
DeviceIDListComma separated list of Device IDs. Containing a minimum of 1 and a maximum of 50000 Device IDs, each as defined by sr:EUIRestriction of xs:string (minLength = 23 maxLength = 1199999 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})”)Yes Minimum 1 and Maximum 50,000 Device IDsNoneN/A

Response data items

Table 255: DSPUpdateFirmwareWarning (sr:DSPUpdateFirmwareWarning) data items
Data ItemDescription / Allowable valuesTypeMandatoryDefaultUnits
InvalidDeviceIDListComma separated list of Device IDs for which the User ID is not the Import Supplier or the DeviceIds don’t exist. Containing a minimum of one Device ID, each as defined by sr:EUIsr:DeviceIDList (Restriction of xs:string (minLength = 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})”))No The Response will contain at least one of the 5 Lists and it could contain all of themNoneN/A
NotCommissionedDeviceID ListComma separated list of Device IDs which aren’t in a status of ‘Commissioned’ or ‘Suspended’ or the Device is not a Meter or a HCALCS. Containing a minimum of one Device ID, each as defined by sr:EUIsr:DeviceIDList (Restriction of xs:string (minLength = 23 pattern = as for InvalidDeviceIDList above))No The Response will contain at least one of the 5 Lists and it could contain all of themNoneN/A
NotApplicableFirmware DeviceIDListComma separated list of Device IDs for which the Firmware is not applicable. Containing a minimum of one Device ID, each as defined by sr:EUIsr:DeviceIDList (Restriction of xs:string (minLength = 23 pattern = as for InvalidDeviceIDList above))No The Response will contain at least one of the 5 Lists and it could contain all of themNoneN/A
OtherRequestsInProgress ListComma separated list of Device IDs for which another Firmware Update request is in progress. Containing a minimum of one Device ID, each as defined by sr:EUIsr:DeviceIDList (Restriction of xs:string (minLength = 23 pattern = as for InvalidDeviceIDList above))No The Response will contain at least one of the 5 Lists and it could contain all of themNoneN/A
InvalidGBCSVersionListComma separated list of Device IDs for which either; the HCALCS DeviceID for which the GBCS Version of the associated CHF is prior to v4.1 HCALCS Device IDs for which the current GBCS Version is prior to v4.1sr:DeviceIDList (Restriction of xs:string (minLength = 23 pattern = as for InvalidDeviceIDList above))No The Response will contain at least one of the 5 Lists and it could contain all of themNoneN/A

Additional System Processing - DUIS

The DCC Systems shall calculate a Hash over the Manufacturer Image part of the FirmwareImage provided by the User within the Service Request and ensure that the Hash calculated matches that held in the CPL for the specified FirmwareVersion. Where the DCC identifies any mismatch in Hash values, a Response Code of E110103 shall be returned to the User.

DUGIDS service matrix

DUGIDS DS.0226 Table 36 footnote extract

FootnoteExtractColumnCell ValueSource
2See section 2.3.10 for details on Firmware Distribution Mode of OperationDCC OnlyYesDS.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 →