Service Reference Variant

4.10 · Read Network Data

Service details

Identifiers, rules, and applicability

Service reference
4.10
Service Reference Variant
4.10
DUIS section
3.8.32
Command variants
1, 2, 3
DUIS possible responses
AcknowledgementService Response from Device - GBCSPayloadService Response from Device - DSPScheduledMessage FormatResponse to a Command for Local Delivery Request - LocalCommand FormatCountersigned SMETS1 Response
Critical
No
Sensitive response
Elec No, Gas Yes
Protection against replay
No
On demand
Yes
Future dated
DSP
DSP scheduled
Yes
DCC only
No
SMETS1 applicability
Yes
SAPC requirement
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.

ECS238 attributes0x0039ESME
SpecificationItemReferenceDescription
SMETSAverage RMS Voltage Measurement Period5.7.4.6The length of time in seconds over which the RMS voltage is averaged.
SMETSAverage RMS Over Voltage Counter5.7.5.7The number of times the average RMS voltage, as calculated in Section 5.5.12.1, has been above the Average RMS Over Voltage Threshold(5.7.4.4) since last reset.
SMETSAverage RMS Under Voltage Counter5.7.5.8The number of times the average RMS voltage, as calculated in Section 5.5.12.1, has been below the Average RMS Under Voltage Threshold(5.7.4.5) since last reset.
SMETSAverage RMS Voltage Profile Data Log5.7.5.9A log capable of storing 4320 entries (including the UTC date and time at the end of the period to which the value relates) comprising the averaged RMS voltage for each Average RMS Voltage Measurement Period(5.7.4.6) arranged as a circular buffer such that when full, further writes shall cause the oldest entry to be overwritten.
SMETSPhase [n] Average RMS Voltage Measurement Period5.19.1.3The length of time in seconds over which the RMS voltage is averaged for phase [n].
SMETSPhase [n] Average RMS Over Voltage Counter5.19.2.1The number of times the average RMS voltage for phase [n], as calculated in Section 5.17.2.1, has been above the Phase [n] Average RMS Over Voltage Threshold(5.19.1.1) since this counter was last reset.
SMETSPhase [n] Average RMS Under Voltage Counter5.19.2.2The number of times the average RMS voltage for phase [n], as calculated in accordance with Section 5.17.2.1, has been below the Phase [n] Average RMS Under Voltage Threshold(5.19.1.2) since this counter was last reset.
SMETSPhase [n] Average RMS Voltage Profile Data Log5.19.2.3A log capable of storing 4320 entries (including the UTC date and time at the end of the period to which the values relate) comprising the averaged RMS voltage for phase [n] for each Phase [n] Average RMS Voltage Measurement Period(5.19.1.3) arranged as a circular buffer such that when full, further writes shall cause the oldest entry to be overwritten.
ECS23b8 attributes0x00BCESME
SpecificationItemReferenceDescription
SMETSAverage RMS Voltage Measurement Period5.7.4.6The length of time in seconds over which the RMS voltage is averaged.
SMETSAverage RMS Over Voltage Counter5.7.5.7The number of times the average RMS voltage, as calculated in Section 5.5.12.1, has been above the Average RMS Over Voltage Threshold(5.7.4.4) since last reset.
SMETSAverage RMS Under Voltage Counter5.7.5.8The number of times the average RMS voltage, as calculated in Section 5.5.12.1, has been below the Average RMS Under Voltage Threshold(5.7.4.5) since last reset.
SMETSAverage RMS Voltage Profile Data Log5.7.5.9A log capable of storing 4320 entries (including the UTC date and time at the end of the period to which the value relates) comprising the averaged RMS voltage for each Average RMS Voltage Measurement Period(5.7.4.6) arranged as a circular buffer such that when full, further writes shall cause the oldest entry to be overwritten.
SMETSPhase [n] Average RMS Voltage Measurement Period5.19.1.3The length of time in seconds over which the RMS voltage is averaged for phase [n].
SMETSPhase [n] Average RMS Over Voltage Counter5.19.2.1The number of times the average RMS voltage for phase [n], as calculated in Section 5.17.2.1, has been above the Phase [n] Average RMS Over Voltage Threshold(5.19.1.1) since this counter was last reset.
SMETSPhase [n] Average RMS Under Voltage Counter5.19.2.2The number of times the average RMS voltage for phase [n], as calculated in accordance with Section 5.17.2.1, has been below the Phase [n] Average RMS Under Voltage Threshold(5.19.1.2) since this counter was last reset.
SMETSPhase [n] Average RMS Voltage Profile Data Log5.19.2.3A log capable of storing 4320 entries (including the UTC date and time at the end of the period to which the values relate) comprising the averaged RMS voltage for phase [n] for each Phase [n] Average RMS Voltage Measurement Period(5.19.1.3) arranged as a circular buffer such that when full, further writes shall cause the oldest entry to be overwritten.
GCS181 attribute0x0079GSME
SpecificationItemReferenceDescription
SMETSNetwork Data Log4.6.5.12A log capable of storing four hours of UTC date and time stamped six minute Consumption data 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

No specific error data is available for this SRV.

GBCS Use Case

Use cases, device coverage, and applicability

Use Case / Message Code
ECS230x0039
DUIS Applicability
v3.0 – v5.3
GBCS Applicability
v1.0 – v4.3
GBCS Criticality
Non-Critical
Sensitive Response
No
Future Dated
DSP
ResponseESMENot always GBT
SMETS1 Applicable
Yes
Eligible Roles
EISENOESME
Use Case / Message Code
ECS23b0x00BC
DUIS Applicability
v3.0 – v5.3
GBCS Applicability
v1.0 – v4.3
GBCS Criticality
Non-Critical
Sensitive Response
No
Future Dated
DSP
ResponseESMENot always GBT
SMETS1 Applicable
No
Eligible Roles
EISENOESME
Use Case / Message Code
GCS180x0079
DUIS Applicability
v3.0 – v5.3
GBCS Applicability
v1.0 – v4.3
GBCS Criticality
Non-Critical
Sensitive Response
Yes
Future Dated
DSP
GBT
No
SMETS1 Applicable
Yes
Eligible Roles
GISGNOGSME

DUIS Service Definition

Data items and DCC processing

Request data items

Table 146: ReadNetworkData (sr:ReadLogFutureDatableAndURPCredentials) 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 Date-time in the future that is either <= current date + 30 days or the date = ‘3000-12-31T00:00:00Z’xs:dateTimeNoNoneUTC Date-Time
ReadLogPeriodThe Start and End Date-Times for which the data is required Note that for Service Requests targeted at Gas Smart Meters, this date range must surround the 4 hour period.sr:ReadLogPeriod (see clause 3.10.1.14)YesNoneN/A
KAPublicSecurityCredentialsThe Key Agreement Public Security Credentials (of the requesting party) to be used where the request is from an Unknown Remote Party (i.e. Gas Transporter) with respect to the BusinessTargetID specified within the Service Request.xs:base64BinaryUser Role IS, GS, ED: N/A User Role GT: YesNoneN/A
Table 147: DSPReadNetworkData (sr:ReadLogPeriodOffset) data items
Data ItemDescription / Allowable valuesTypeMandatoryDefaultUnits
DSPReadNetworkDataThe Start and End Date Offsets from the current date and the Start and End Times which together define the date-time period for which the data is requiredsr:ReadLogPeriodOffset (See clause 3.10.1.15)YesNoneN/A

DUGIDS service matrix

DUGIDS DS.0226 Table 36 footnote extract

FootnoteExtractColumnCell ValueSource
UnnumberedElec No, Gas YesSensitive ResponseElec No, Gas YesDS.0226 Table 36 Service Request Matrix
7Service Request can’t be Sequenced for Gas, because the DCC can’t read the encrypted status returned by the DeviceService Reference Variant4.10DS.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 →