Atomic items
Section 20 objects, attributes or methods at this source reference.
SMETS requirement clause
4.6.5.17 — Security Log
5 technical records havebeen identified at this reference: 5 Section 20 items and 0 explicit clause references. The links below describe documented interfaces and observable effects; they do not assert compliance with the source requirement.
GSMESRV touchpoint
Documented touchpoints
Typed relationships supported by source mapping rows.
Linked SRVs
Unique retained services reached through exact control rows.
Linked alerts
Explicit requirement-to-alert references.
SMETS4.6.5.17 · item SecurityLog(notCHF).method: readLog
SecurityLog(notCHF) - readLog
The response contains all the log entries between fromDateTime and toDateTime inclusive
- Object
SecurityLog(notCHF)- Attribute / method
method: readLog- Interface disposition
- E
- Category
- Method
- Section 20 meaning
- The response contains all the log entries between fromDateTime and toDateTime inclusive
Documented touchpoints
- ReadsCS10b
0x00A1GSMESRV 6.13
SMETS4.6.5.17 · item SecurityLog(notCHF).logEntries[1..100].logEntry.logCode
SecurityLog(notCHF) - logEntries logEntry logCode
The Alert / Log Code corresponding to this event (as defined in GBCS)
- Object
SecurityLog(notCHF)- Attribute / method
logEntries[1..100].logEntry.logCode- Interface disposition
- E
- Category
- Operational data
- Section 20 meaning
- The Alert / Log Code corresponding to this event (as defined in GBCS)
Documented touchpoints
- ReadsCS10b
0x00A1GSMESRV 6.13
SMETS4.6.5.17 · item SecurityLog(notCHF).logEntries[1..100].logEntry.timestamp
SecurityLog(notCHF) - logEntries logEntry timestamp
The UTC date- time stamp of this entry
- Object
SecurityLog(notCHF)- Attribute / method
logEntries[1..100].logEntry.timestamp- Interface disposition
- E
- Category
- Operational data
- Section 20 meaning
- The UTC date- time stamp of this entry
Documented touchpoints
- ReadsCS10b
0x00A1GSMESRV 6.13
SMETS4.6.5.17 · item SecurityLog(notCHF).methodInput: fromDateTime
SecurityLog(notCHF) - fromDateTime
If the Start of Time as per GBCS section 9.1.6, response contains all entries from the oldest in the log to 'toDateTime'. If not the Start of Time, response contains all entries between fromDateTime and toDateTime inclusive
- Object
SecurityLog(notCHF)- Attribute / method
methodInput: fromDateTime- Interface disposition
- E
- Category
- Method Input
- Section 20 meaning
- If the Start of Time as per GBCS section 9.1.6, response contains all entries from the oldest in the log to 'toDateTime'. If not the Start of Time, response contains all entries between fromDateTime and toDateTime inclusive
Documented touchpoints
- ReadsCS10b
0x00A1GSMESRV 6.13
SMETS4.6.5.17 · item SecurityLog(notCHF).methodInput: toDateTime
SecurityLog(notCHF) - toDateTime
Except for GSME, if the End of Time as per GBCS section 9.1.6, the response contains all entries from 'fromDateTime' in the log to the newest. If not the End of Time, the response contains all entries between fromDateTime and toDateTime inclusive. For GSME, the response contains entries between fromDateTime and toDateTime, including those matching the fromDateTime but excluding those matching toDateTime. Note that this means GSME log entries with an 'invalid time' cannot be retrieved.
- Object
SecurityLog(notCHF)- Attribute / method
methodInput: toDateTime- Interface disposition
- E
- Category
- Method Input
- Section 20 meaning
- Except for GSME, if the End of Time as per GBCS section 9.1.6, the response contains all entries from 'fromDateTime' in the log to the newest. If not the End of Time, the response contains all entries between fromDateTime and toDateTime inclusive. For GSME, the response contains entries between fromDateTime and toDateTime, including those matching the fromDateTime but excluding those matching toDateTime. Note that this means GSME log entries with an 'invalid time' cannot be retrieved.
Documented touchpoints
- ReadsCS10b
0x00A1GSMESRV 6.13
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.