UK Smart MeteringKnowledge ProjectStructured SRV and specimen referenceBrowse SRVs

Service Reference Variant

6.13 · Read Event Or Security Log

Service details

Identifiers, rules, and applicability

Service reference
6.13
Service Reference Variant
6.13
DUIS section
3.8.63
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
No
DSP scheduled
No
DCC only
No
SMETS1 applicability
Yes
SAPC requirement
Mandatory, Optional
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.

CS10a2 attributes0x0014GPFGSME
SpecificationItemReferenceDescription
CHTSGPF Event Log4.6.3.8A log capable of storing one hundred UTC date and time stamped entries of non-security related information for diagnosis and auditing, arranged as a circular Buffer such that when full, further writes shall cause the oldest entry to be overwritten.
SMETSEvent Log4.6.5.9A log capable of storing one hundred UTC date and time stamped entries of non-security related information for diagnosis and auditing, arranged as a circular buffer such that when full, further writes shall cause the oldest entry to be overwritten.
CS10b2 attributes0x00A1GPFGSME
SpecificationItemReferenceDescription
CHTSGPF Security Log4.6.3.11A log capable of storing one hundred UTC date and time stamped entries of security related information for diagnosis and auditing, arranged as a circular Buffer such that when full, further writes shall cause the oldest entry to be overwritten.
SMETSSecurity Log4.6.5.17A log capable of storing one hundred UTC date and time stamped entries of security related information for diagnosis and auditing arranged as a circular buffer such that when full, further writes shall cause the oldest entry to be overwritten.
ECS35a1 attribute0x0048ESME
SpecificationItemReferenceDescription
SMETSEvent Log5.7.5.16A log capable of storing one hundred UTC date and time stamped entries of non-security related information for diagnosis and auditing arranged as a circular buffer such that when full, further writes shall cause the oldest entry to be overwritten.
ECS35b1 attribute0x0049ESME
SpecificationItemReferenceDescription
SMETSSecurity Log5.7.5.31A log capable of storing one hundred UTC date and time stamped entries of security related information for diagnosis and auditing arranged as a circular buffer such that when full, further writes shall cause the oldest entry to be overwritten.
ECS35c1 attribute0x0093CHF
SpecificationItemReferenceDescription
CHTSCHF Event Log4.6.3.3A log capable of storing one hundred UTC date and time stamped entries of non-security related information for diagnosis and auditing, arranged as a circular Buffer such that when full, further writes shall cause the oldest entry to be overwritten.
ECS35d1 attribute0x0094CHF
SpecificationItemReferenceDescription
CHTSCHF Security Log4.6.3.5A log capable of storing one hundred UTC date and time stamped entries of security related information for diagnosis and auditing, arranged as a circular Buffer such that when full, further writes shall cause the oldest entry to be overwritten.
ECS35e1 attribute0x00B9ESME
SpecificationItemReferenceDescription
SMETSPower Event Log5.7.5.25A log capable of storing one hundred UTC date and time stamped entries of non-security related information for diagnosis and auditing arranged as a circular buffer such that when full, further writes shall cause the oldest entry to be overwritten.
ECS35g1 attribute0x00FDESME
SpecificationItemReferenceDescription
SMETSAuxiliary Controller Event Log5.7.5.6A log capable of storing one hundred UTC date and time stamped entries of events, and associated information, related to Auxiliary Controllers arranged as a circular buffer such that when full, further writes shall cause the oldest entry to be overwritten.

Specific Errors

Response codes and descriptions

Response CodeResponse Code Description
E061301
Log To Read / Device Type mismatch. The Log to Read is not applicable to the Device Type
E061304
Invalid User Role. The ALCS Event Log is not available to the requesting User Role. The IS User Role is eligible to read this log regardless of the GBCS version that pertains to the Device Model recorded in the SMI for this Device. The ED User Role is eligible to read this log only where the GBCS version that pertains to the Device Model recorded in the SMI for this Device is GBCS v3.2 or later. All other User Roles are not eligible to read this log.

Source: DUIS 3.8.63.3

SMETS1-specific validation

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

SMETS1 supplementary validation
E061305

Check that if the LogToRead is ALCSEvent or PowerEvent then the target Device is not a SMETS1 Device according to the Smart Metering Inventory. For clarity, SMETS1 ESME are not required to support such logs.

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
CS10a0x0014
DUIS Applicability
v3.0 – v5.3
GBCS Applicability
v1.0 – v4.3
GBCS Criticality
Non-Critical
Sensitive Response
No
Future Dated
No
GBTWhat is GBT?
ResponseGSMENot always GBT
ResponseGPFNot always GBT
SMETS1 Applicable
Yes
Eligible Roles
GISGNOSNAGSMEGPF
Use Case / Message Code
CS10b0x00A1
DUIS Applicability
v3.0 – v5.3
GBCS Applicability
v1.0 – v4.3
GBCS Criticality
Non-Critical
Sensitive Response
No
Future Dated
No
GBTWhat is GBT?
ResponseGSMENot always GBT
ResponseGPFNot always GBT
SMETS1 Applicable
Yes
Eligible Roles
GISGNOSNAGSMEGPF
Use Case / Message Code
ECS35a0x0048
DUIS Applicability
v3.0 – v5.3
GBCS Applicability
v1.0 – v4.3
GBCS Criticality
Non-Critical
Sensitive Response
No
Future Dated
No
GBTWhat is GBT?
ResponseESMENot always GBT
SMETS1 Applicable
Yes
Eligible Roles
EISENOSNAESME
Use Case / Message Code
ECS35b0x0049
DUIS Applicability
v3.0 – v5.3
GBCS Applicability
v1.0 – v4.3
GBCS Criticality
Non-Critical
Sensitive Response
No
Future Dated
No
GBT
No
SMETS1 Applicable
Yes
Eligible Roles
EISENOSNAESME
Use Case / Message Code
ECS35c0x0093
DUIS Applicability
v3.0 – v5.3
GBCS Applicability
v1.0 – v4.3
GBCS Criticality
Non-Critical
Sensitive Response
No
Future Dated
No
GBTWhat is GBT?
ResponseCHFNot always GBT
SMETS1 Applicable
Yes
Eligible Roles
EISGISENOGNOSNACHF
Use Case / Message Code
ECS35d0x0094
DUIS Applicability
v3.0 – v5.3
GBCS Applicability
v1.0 – v4.3
GBCS Criticality
Non-Critical
Sensitive Response
No
Future Dated
No
GBT
No
SMETS1 Applicable
Yes
Eligible Roles
EISGISENOGNOSNACHF
Use Case / Message Code
ECS35e0x00B9
DUIS Applicability
v3.0 – v5.3
GBCS Applicability
v1.0 – v4.3
GBCS Criticality
Non-Critical
Sensitive Response
No
Future Dated
No
GBT
No
SMETS1 Applicable
No
Eligible Roles
EISENOSNAESME
Use Case / Message Code
ECS35f0x00BA
DUIS Applicability
v3.0 – v5.3
GBCS Applicability
v2.0 – v3.1
GBCS Criticality
Non-Critical
Sensitive Response
No
Future Dated
No
GBTWhat is GBT?
ResponseESMENot always GBT
SMETS1 Applicable
No
Eligible Roles
EISESME
Use Case / Message Code
ECS35g0x00FD
DUIS Applicability
v3.1 – v5.3
GBCS Applicability
v3.2 – v4.3
GBCS Criticality
Non-Critical
Sensitive Response
No
Future Dated
No
GBT
No
SMETS1 Applicable
No
Eligible Roles
EISENOESME

DUIS Service Definition

Data items and DCC processing

Request data items

Table 177: ReadEventOrSecurityLog (sr:ReadEventOrSecurityLog) data items
Data ItemDescription / Valid SetTypeMandatoryDefaultUnits
ReadLogPeriodThe Start and / or End Date-Times for which the data is requiredsr:ReadLogPeriod (see clause 3.10.1.14)YesNoneN/A
LogToReadAn enumerated value indicating the Log to be read. Valid values: Event To read a Device’s Event Log ALCSEvent Only applicable to ESME Note that ALCSEvent refers to the Auxiliary Controller Event Log for Devices which comply with GBCS v4.0 or later PowerEvent Only applicable to ESME Security To read a Device’s Security Log GSMEEvent Only applicable to GSME Event Log read on the GPF GSMESecurity. Only applicable to GSME Security Log read on the GPFRestriction of xs:string (Enumeration)YesNoneN/A

DUGIDS service matrix

DUGIDS DS.0226 Table 36 footnote extract

FootnoteExtractColumnCell ValueSource
5Service Request also available to the ‘Old’ Registered Supplier (EIS)Eligible User RoleEISDS.0226 Table 36 Service Request Matrix
5Service Request also available to the ‘Old’ Registered Supplier (EIS)Eligible User RoleGISDS.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 →