Atomic items
Section 20 objects, attributes or methods at this source reference.
SMETS requirement clause
4.5.3.3 — Add Credit
3 technical records havebeen identified at this reference: 2 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 onlyLocal HAN pathSRV 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.5.3.3 · item PrepaymentCredit.methodInput: creditToken
PrepaymentCredit - creditToken
The 20 digit UTRN as a 20 octet long octet string in visible string format
- Object
PrepaymentCredit- Attribute / method
methodInput: creditToken- Interface disposition
- E
- Category
- Method Input
- Section 20 meaning
- The 20 digit UTRN as a 20 octet long octet string in visible string format
Documented touchpoints
- UpdatesCS01b
0x0097GSMESRV 2.2
SMETS4.5.3.3 · item PrepaymentCredit.methodInput: creditToken
PrepaymentCredit - creditToken
Input parameter to addCreditMethod
- Object
PrepaymentCredit- Attribute / method
methodInput: creditToken- Interface disposition
- E
- Category
- Method Input
- Section 20 meaning
- Input parameter to addCreditMethod
Documented touchpoints
- Local HANPCS01
0x009BGSME
SMETS4.5.3.3 · item clause.4.5.3.3
Add Credit
This source clause is explicitly referenced by the GBCS device alert table.
- Category
- Alert reference
Documented touchpoints
- Alert touchpointGSME0x8F64UTRN not for this Device
- Alert touchpointGSME0x8F32Supply Armed
- Alert touchpointGSME0x8F47Credit would cause Meter Balance to exceed Maximum Meter Balance Threshold
- Alert touchpointGSME0x8F5BUTRN exceeds Maximum Credit Threshold
- Alert touchpointGSME0x8F51Duplicate UTRN entered
- Alert touchpointGSME0x810ECredit Added Locally
- Alert touchpointGSME0x8F63UTRN not Authentic
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.