UK Smart MeteringKnowledge ProjectStructured SRV and specimen referenceBrowse SRVs

Service Reference Variant

8.9 · Read Device Log

Service details

Identifiers, rules, and applicability

Service reference
8.9
Service Reference Variant
8.9
DUIS section
3.8.113
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.

CCS063 attributes0x010FCHF
SpecificationItemReferenceDescription
CHTSCHF Device Log4.6.2.1The Security Credentials for each of the Type 1 Devices, Type 2 Devices, GSME, ESME, SAPC and GPF with which the CHF can establish Communications Links.
CHTSCHF Communications Store4.6.3.2A store holding, for each Device in the CHF Device Log(4.6.2.1), the UTC date and time of the last Communications Link established with the CHF.
CHTSCHF Communications Store - Sub GHz Link Quality [DBCH]4.6.3.14A store holding, for each Device in the CHF Device Log(4.6.2.1), an indication of its quality of communication for Communication Links in Sub GHz Bands.
CCS072 commands2 attributes0x00FECHF

Commands mapped to CCS07

  • CHTSRead CHF Configuration Data4.5.1.5CHF
  • CHTSRead CHF Operational Data4.5.1.7CHF
SpecificationItemReferenceDescription
CHTSCHF Device Log4.6.2.1The Security Credentials for each of the Type 1 Devices, Type 2 Devices, GSME, ESME, SAPC and GPF with which the CHF can establish Communications Links.
CHTSCHF Historic Device Log4.6.3.15A circular buffer containing the Security Credentials for an aggregate of up to fifteen Type 1 Devices, Type 2 Devices, GSME, ESME and SAPC which have previously been recorded in the CHF Device Log and then most recently been removed from that log.
CS072 commands1 attribute0x0013ESME

Commands mapped to CS07

  • SMETSAdd Device Security Credentials5.6.3.4ESME
  • SMETSRemove Device Security Credentials5.6.3.19ESME
SpecificationItemReferenceDescription
SMETSDevice Log5.7.4.14The Security Credentials for each of the Type 1 Devices and Type 2 Devices with which ESME can establish Communications Links.

Specific Errors

Response codes and descriptions

Response CodeResponse Code Description
E080902
ReadSecurityDetails is specified in the Service Request but the Firmware Version recorded in the SMI for the Device is not at GBCS version 3.2 or later.
E080903
ReadSecurityDetails is specified in the Service Request but the Device Type is not a CHF.

Source: DUIS 3.8.113.3

SMETS1-specific validation

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

SMETS1 supplementary validation
E080901

Check that if the target Device is a SMETS1 Device according to the Smart Metering Inventory then the target Device’s Device Type is CHF according to the Smart Metering Inventory. For clarity, SMETS1 does not require any other Device Logs be supported.

Applies to: SMETS1 Devices only

Source: DUIS 1.4.6 Table 2

GBCS Use Case

Use cases, device coverage, and applicability

Use Case / Message Code
CCS05/CCS040x0004
DUIS Applicability
v3.0 – v5.3
GBCS Applicability
v1.0 – v1.1
GBCS Criticality
Non-Critical
Sensitive Response
No
Future Dated
DSP
GBT
No
SMETS1 Applicable
No
Eligible Roles
EISGISOUCHF
Use Case / Message Code
CCS060x010F
DUIS Applicability
v3.0 – v5.3
GBCS Applicability
v2.0 – v4.3
GBCS Criticality
Non-Critical
Sensitive Response
No
Future Dated
DSP
GBT
No
SMETS1 Applicable
Yes
Eligible Roles
EISGISOUCHF
Use Case / Message Code
CCS070x00FE
DUIS Applicability
v4.0 – v5.3
GBCS Applicability
v3.2 – v4.3
GBCS Criticality
Non-Critical
Sensitive Response
No
Future Dated
DSP
GBT
No
SMETS1 Applicable
No
Eligible Roles
EISGISOUCHF
Use Case / Message Code
CS070x0013
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
No
Eligible Roles
EISESMEHCALCSPPMID
GISGSMEGPFPPMID
OUESMEGSMEGPFHCALCSPPMID

DUIS Service Definition

Data items and DCC processing

Request data items

Table 243: ReadDeviceLog (sr:ReadDeviceLog) data items
Data ItemDescription / 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 Date-time in the future that is either <= current date + 30 days or the date = ‘3000-12-31T00:00:00Z’xs:dateTimeNoNoneUTC Date-Time
ReadSecurityDetailsThis parameter is supplied if the User wishes to receive the CHF Device Log and the CHF Historic Device Log.sr: ReadSecurityDetailsNoNoneNone

Additional System Processing - DUIS

For CHF with a Device Model recorded in the Smart Metering Inventory that pertains to GBCS version 2.0 according to the entry for that Device Model in the Central Products List, the Service Request Response will also contain details of Sub GHz signal strength, for dual band CHF using the Sub GHz frequency band interface.

If the Service Request Business Originator User Role is IS and the Target Device Type is HCALCS, even though the User is a KRP to the Device, the Command will be submitted to the Device by the DCC Access Control Broker using the URP interaction type. This is because HCALCS hold Supplier Digital Signature, but not Key Agreement Credentials.

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 →