Service Reference Variant

11.2 · Read Firmware Version

Service details

Identifiers, rules, and applicability

Service reference
11.2
Service Reference Variant
11.2
DUIS section
3.8.124
Command variants
1, 2, 3
DUIS possible responses
AcknowledgementService Response from Device - GBCSPayloadResponse to a Command for Local Delivery Request - LocalCommand FormatCountersigned SMETS1 Response
Critical
No
Sensitive response
No
Protection against replay
No
On demand
Yes
Future dated
DSP
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.

ECS522 attributes0x0059CHFESME
SpecificationItemReferenceDescription
CHTSCH Firmware Version4.6.3.4The active version of Firmware of the CHF and the GPF.
SMETSFirmware Version5.7.5.17The active version of Firmware of ESME.
GCS382 attributes0x0084GPFGSME
SpecificationItemReferenceDescription
CHTSGPF GSME Proxy Log4.6.3.9A log capable of storing UTC date and time stamped entries of the GSME Configuration Data and GSME Operational Data except for the following SMETS items:
SMETSFirmware Version4.6.5.10The active version of Firmware of GSME.

Specific Errors

Response codes and descriptions

No specific error data is available for this SRV.

GBCS Use Case

Use cases, device coverage, and applicability

Use Case / Message Code
CS080x0059
DUIS Applicability
v5.0 – v5.3
GBCS Applicability
Not stated
GBCS Criticality
Non-Critical
Sensitive Response
No
Future Dated
DSP
GBT
No
SMETS1 Applicable
Yes
Eligible Roles
EISEESGISSNAENOGNOOUPPMID
Use Case / Message Code
CS080x0129
DUIS Applicability
v5.0 – v5.3
GBCS Applicability
v4.1 – v4.3
GBCS Criticality
Non-Critical
Sensitive Response
No
Future Dated
DSP
GBT
No
SMETS1 Applicable
No
Eligible Roles
EISHCALCSPPMID
EESGISSNAENOGNOOUPPMID
Use Case / Message Code
ECS520x0059
DUIS Applicability
v3.0 – v5.3
GBCS Applicability
v1.0 – v4.3
GBCS Criticality
Non-Critical
Sensitive Response
No
Future Dated
DSP
GBT
No
SMETS1 Applicable
Yes
Eligible Roles
EISEESSNAENOOUESMECHF
GISGNOCHF
Use Case / Message Code
GCS380x0084
DUIS Applicability
v3.0 – v5.3
GBCS Applicability
v1.0 – v4.3
GBCS Criticality
Non-Critical
Sensitive Response
No
Future Dated
DSP
GBT
No
SMETS1 Applicable
Yes
Eligible Roles
GISSNAGNOOUGSMEGPF

DUIS Service Definition

Data items and DCC processing

Request data items

Table 256: ReadFirmwareVersion (sr:ReadFirmwareVersion) 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 UTC date and time the User requires the command to be executed on the Device ID Date-time in the future that is either <= current date + 30 days or the date = ‘3000-12-31T00:00:00Z’xs:dateTimeNoNoneUTC Date-Time

Additional System Processing - DUIS

Upon receipt of a Response to this Service Request containing a Firmware Version value:

  • if the Target Device Type is ESME, GSME, HCALCS, PPMID or CHF and the Firmware Version returned by the Device matches an entry on the CPL for that Device Model, but is different from that stored in the SMI, the DCC Systems shall update the Firmware Version in the SMI to the value returned by the Device. Note that updating the Firmware Version may also update the Device’s GBCS Version in the SMI.
    • If the target Device is CHF, the associated GPF Firmware Version shall also be updated.
    • If the Firmware Version entry on the CPL for that Device Model has a status of “Current” and the Read Firmware Version Service Request was not submitted by the Responsible Supplier, DCC Alert N49 shall be sent to the Responsible Supplier.
    • If the Firmware Version entry on the CPL for that Device Model has a status of ‘Removed’, the SMI Firmware Version shall be updated, and the Device Status shall be set to ‘Suspended’ (where the target Device is CHF, the associated GPF Device Status shall also be set to ‘Suspended’). In this case DCC Alert N50 shall 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 Alerts N40 and N41 will be sent to the Users responsible for those Service Requests.
    • 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 Target Device Type is ESME, GSME, HCALCS, PPMID or CHF and the Firmware Version returned by the Device does not match an entry on the CPL for that Device Model, but is different from that stored in the SMI, DCC Alert N51 will be sent to the Responsible Supplier and the SMI Firmware Version will be updated with the Firmware Version returned by the Device. The Device’s GBCS Version in the SMI will not be updated since there is no CPL entry on which to base an update.
    • As there is no entry on the CPL, the Device Status of the Device shall be set to ‘Suspended’ and an additional DCC Alert N28 shall be sent to the Responsible Supplier and to the Electricity Distributor or Gas Transporter.
    • If the target Device is CHF, the associated GPF Firmware Version shall also be updated and the GPF Device Status shall also be set to ‘Suspended’.
    • All DSP Future Dated and Scheduled Service Requests shall be deleted for the ‘Suspended’ Device(s) and DCC Alerts N40 and N41 will be sent to the Users responsible for those Service Requests.
  • if the Target Device Type is GPF and the GSME Firmware Version returned by the GPF is different from that stored in the SMI, DCC Alert N52 will be sent to the Responsible Supplier as a warning and the SMI Firmware Version will not be updated.

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 →