Atomic items
Section 20 objects, attributes or methods at this source reference.
SMETS requirement clause
3 technical records havebeen identified at this reference: 3 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.
Section 20 objects, attributes or methods at this source reference.
Typed relationships supported by source mapping rows.
Unique retained services reached through exact control rows.
Explicit requirement-to-alert references.
SMETS5.7.4.18 · item DeviceSecurityCredentials.methodInput: keyUsage
The key usage of the certificate requested
DeviceSecurityCredentialsmethodInput: keyUsageDocumented touchpoints
0x000CESMESRV 6.24.2SMETS5.7.4.18 · item DeviceSecurityCredentials.methodOutput: certificate
The certificate returned
DeviceSecurityCredentialsmethodOutput: certificateDocumented touchpoints
0x000CESMESRV 6.24.2SMETS5.7.4.18 · item DeviceSecurityCredentials.method: provideSecurityCredentials
Processing is as required in the GBCS in section 13 which will result in the device storing the data in DeviceSecurityCredentials(DigitalSigning).value, if all checks are passed
DeviceSecurityCredentialsmethod: provideSecurityCredentialsDocumented touchpoints
0x000CESMESRV 6.24.2How to read this page
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.