Service Reference Variant

6.11 · Synchronise Clock

Service details

Identifiers, rules, and applicability

Service reference
6.11
Service Reference Variant
6.11
DUIS section
3.8.61
Command variants
4, 5, 6, 7
DUIS possible responses
AcknowledgementResponse to Transform Request - PreCommand FormatService Response from Device - GBCSPayloadResponse to a Command for Local Delivery Request - LocalCommand FormatCountersigned SMETS1 Response
Critical
Yes
Sensitive response
No
Protection against replay
Yes
On demand
Yes
Future dated
No
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.

ECS701 command1 attribute0x0062ESME

Command mapped to ECS70

SpecificationItemReferenceDescription
SMETSClock5.5.1The Clock forming part of ESME shall be capable of operating so as to be accurate to within 10 seconds of the UTC date and time under normal operating conditions.

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
ECS700x0062
DUIS Applicability
v3.0 – v5.3
GBCS Applicability
v1.0 – v4.3
GBCS Criticality
Critical
Sensitive Response
No
Future Dated
No
GBT
No
SMETS1 Applicable
Yes
Eligible Roles
EISESME
Use Case / Message Code
GCS280x007F
DUIS Applicability
v3.0 – v5.3
GBCS Applicability
v1.0 – v4.3
GBCS Criticality
Critical
Sensitive Response
No
Future Dated
No
GBT
No
SMETS1 Applicable
Yes
Eligible Roles
GISGSME

DUIS Service Definition

Data items and DCC processing

Request data items

Table 175: SynchroniseClock (sr:SynchroniseClock) data items
Data ItemDescription / Valid SetTypeMandatoryDefaultUnits
CurrentDateTimeThe Supplier’s current date-time, that define the “validity interval start” Valid set: Valid date-timexs:dateTimeYesNoneUTC Date-Time
TolerancePeriodThe maximum number of seconds that, added to the CurrentDateTime, define the “validity interval end” Valid set: >= 0 and <= 86400 (Note that for the GSME this may need to be at least 1800)sr:tolerancePeriod (Restriction of xs:int minInclusive = 0, maxInclusive = 86400)YesNoneSeconds

Additional System Processing - DUIS

For Gas a Command response indicates successful execution of the Command.

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 →