SMETS requirement clause

4.5.3.4 — Add Device Security Credentials

9 technical records havebeen identified at this reference: 8 Section 20 items and 1 explicit clause reference. The links below describe documented interfaces and observable effects; they do not assert compliance with the source requirement.

GSMEAlert touchpoint onlyNo Section 20 bridge

8

Atomic items

Section 20 objects, attributes or methods at this source reference.

2

Documented touchpoints

Typed relationships supported by source mapping rows.

0

Linked SRVs

Unique retained services reached through exact control rows.

2

Linked alerts

Explicit requirement-to-alert references.

Entity Identifier of another Device that this Device is authorised to send message to / from

Object: DeviceLog(notCHF)
Attribute / method: logEntry[1..15].deviceIdentifier
Interface disposition: E
Category: Configuration data
Section 20 meaning: Entity Identifier of another Device that this Device is authorised to send message to / from

No GBCS or SRV bridge is recorded for this item in the current Section 20 mapping. This is an evidence status, not a statement of non-compliance.

Add an entry to the Device Log as per section 13.

Object: DeviceLog(notCHF)
Attribute / method: method: addEntry
Interface disposition: E
Category: Method
Section 20 meaning: Add an entry to the Device Log as per section 13.

No GBCS or SRV bridge is recorded for this item in the current Section 20 mapping. This is an evidence status, not a statement of non-compliance.

The type of the join and role of the receiving device if relevant.

Object: DeviceLog(notCHF)
Attribute / method: methodInput: joinTypeandRole
Interface disposition: E
Category: Method
Section 20 meaning: The type of the join and role of the receiving device if relevant.

No GBCS or SRV bridge is recorded for this item in the current Section 20 mapping. This is an evidence status, not a statement of non-compliance.

The Entity Identifier of the Device to be removed

Object: DeviceLog(notCHF)
Attribute / method: methodInput: deviceIDToBeRemoved
Interface disposition: E
Category: Method Input
Section 20 meaning: The Entity Identifier of the Device to be removed

No GBCS or SRV bridge is recorded for this item in the current Section 20 mapping. This is an evidence status, not a statement of non-compliance.

The Entity Identifier of the Device to be added

Object: DeviceLog(notCHF)
Attribute / method: methodInput: deviceIDToBeAdded
Interface disposition: E
Category: Method Input
Section 20 meaning: The Entity Identifier of the Device to be added

No GBCS or SRV bridge is recorded for this item in the current Section 20 mapping. This is an evidence status, not a statement of non-compliance.

The type of the Device to be added

Object: DeviceLog(notCHF)
Attribute / method: methodInput: deviceType
Interface disposition: E
Category: Method Input
Section 20 meaning: The type of the Device to be added

No GBCS or SRV bridge is recorded for this item in the current Section 20 mapping. This is an evidence status, not a statement of non-compliance.

Required only for the Join between the PPMID and GSME

Object: DeviceLog(notCHF)
Attribute / method: methodInput: keyAgreementCertificate
Interface disposition: E
Category: Method Input
Section 20 meaning: Required only for the Join between the PPMID and GSME

No GBCS or SRV bridge is recorded for this item in the current Section 20 mapping. This is an evidence status, not a statement of non-compliance.

Device Type for the corresponding Device Identifier

Object: DeviceLog(notCHF)
Attribute / method: logEntry[1..15].deviceType
Interface disposition: E
Category: Configuration data
Section 20 meaning: Device Type for the corresponding Device Identifier

No GBCS or SRV bridge is recorded for this item in the current Section 20 mapping. This is an evidence status, not a statement of non-compliance.

This source clause is explicitly referenced by the GBCS device alert table.

Category: Alert reference

Documented touchpoints

Alert touchpointGSME0x8F48Device joining failed
Alert touchpointGSME0x8F49Device joining succeeded

How to read this page

Evidence is kept at record level

A source clause can contain several separately mapped Section 20 items and an explicit alert reference. One item may be read by an SRV, another updated by a different service, and another have only an Alert or local-HAN path. Accordingly, the clause summary does not collapse those distinctions into a single covered or uncovered result.