UK Smart MeteringKnowledge ProjectStructured SRV and specimen referenceBrowse SRVs

Service Reference Variant

4.4.3 · Retrieve Billing Calendar Triggered Billing Data Log

Service details

Identifiers, rules, and applicability

Service reference
4.4
Service Reference Variant
4.4.3
DUIS section
3.8.24
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
Yes
Protection against replay
No
On demand
Yes
Future dated
DSP
DSP scheduled
No
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.

ECS20c2 attributes0x0030ESME
SpecificationItemReferenceDescription
SMETSBilling Data Log5.7.5.10A log capable of storing the following UTC date and time stamped entries:
SMETSBilling Data Log5.13.2.3Billing Data Log(5.7.5.10) in Part A shall not apply to ESME.
GCS15c2 attributes0x0076GPFGSME
SpecificationItemReferenceDescription
CHTSReceipt of Information by the GPF via the HAN Interface4.5.2A GPF shall be capable, immediately upon establishment of a Communications Link with GSME of receiving GSME Configuration Data, GSME Operational Data and (with the exception of the GSME Cumulative and Historical Value Store and the GSME Profile Data Log) receiving updates of any changes in that data.
SMETSBilling Data Log4.6.5.3A log capable of storing the following UTC date and time stamped entries:

Specific Errors

Response codes and descriptions

No specific validation is defined for this SRV.

GBCS Use Case

Use cases, device coverage, and applicability

Use Case / Message Code
ECS20c0x0030
DUIS Applicability
v3.0 – v5.3
GBCS Applicability
v1.0 – v4.3
GBCS Criticality
Non-Critical
Sensitive Response
Yes
Future Dated
DSP
GBTWhat is GBT?
ResponseESMENot always GBT
SMETS1 Applicable
Yes
Eligible Roles
EISESME
Use Case / Message Code
GCS15c0x0076
DUIS Applicability
v3.0 – v5.3
GBCS Applicability
v1.0 – v4.3
GBCS Criticality
Non-Critical
Sensitive Response
Yes
Future Dated
DSP
GBTWhat is GBT?
ResponseGSMENot always GBT
ResponseGPFNot always GBT
SMETS1 Applicable
Yes
Eligible Roles
GISGSMEGPF

DUIS Service Definition

Data items and DCC processing

Request data items

Table 133: RetrieveBillingCalendarTriggeredBillingDataLog (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 requiredsr: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. Old Responsible Supplier) with respect to the BusinessTargetID specified within the Service Request.sr:Certificate (xs:base64Binary)Responsible Supplier: N/A Old Responsible Supplier: Yes Mandatory for User Roles IS/GS that do not have their credentials on the Device when sending the Service Request e.g. Old SuppliersNoneN/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
7Service Request can’t be Sequenced for Gas, because the DCC can’t read the encrypted status returned by the DeviceService Reference Variant4.4.3DS.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 →