Service Reference Variant

3.3 · Clear Event Log

Service details

Identifiers, rules, and applicability

Service reference
3.3
Service Reference Variant
3.3
DUIS section
3.8.14
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
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.

CS112 commands0 attributes0x0015GPFGSME

Commands mapped to CS11

No mapped data attributes.

ECS15a1 command1 attribute0x0024ESME

Command mapped to ECS15a

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.
ECS15c1 command0 attributes0x00C1ESME

Command mapped to ECS15c

  • SMETSClear Auxiliary Controller Event Log5.6.3.8ESME

No mapped data attributes.

Specific Errors

Response codes and descriptions

Response CodeResponse Code Description
E030301
The combination of Device Type and Event Log Type is incorrect

Source: DUIS 3.8.14.3

SMETS1-specific validation

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

SMETS1 supplementary validation
E030302

Check that if the ESMEEventLogType is ALCS then the target Device is not a SMETS1 Device according to the Smart Metering Inventory. For clarity, SMETS1 ESMEs 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
CS110x0015
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
NoYes
Eligible Roles
GISGSMEGPF
Use Case / Message Code
ECS15a0x0024
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
EISESME
Use Case / Message Code
ECS15c0x00C1
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
EISESME

DUIS Service Definition

Data items and DCC processing

Request data items

Table 124: ClearEventLog (sr:ClearEventLog) data items
Data ItemDescription / ValuesTypeMandatoryDefaultUnits
ESMEEventLogTypeIt specifies which of the two Event Logs included in an Electricity Smart Meter is to be cleared. Note that ALCS refers to the Auxiliary Controller Event Log for Devices which comply with GBCS v4.0 or later Valid set: ESME ALCSRestriction of xs:string (Enumeration)Device Type = ESME: Yes Otherwise: N/ANoneN/A

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 →