CHTS requirement clause

4.6.3.2 — CHF Communications Store

1 technical record hasbeen identified at this reference: 1 Section 20 item and 0 explicit clause references. The links below describe documented interfaces and observable effects; they do not assert compliance with the source requirement.

CHFSRV touchpoint
1

Atomic items

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

1

Documented touchpoints

Typed relationships supported by source mapping rows.

1

Linked SRVs

Unique retained services reached through exact control rows.

0

Linked alerts

Explicit requirement-to-alert references.

CHTS4.6.3.2 · item CHFCommunicationsStore.logEntries[0..16].logentry.lastCommsTimestamp

CHFCommunicationsStore - logEntries logentry lastCommsTimestamp

SRV touchpoint

The UTC date and time at which the Communications Hub last communicated with the Device with the corresponding entry in DeviceLog(CHF).logEntries[0..16]

Object
CHFCommunicationsStore
Attribute / method
logEntries[0..16].logentry.lastCommsTimestamp
Interface disposition
E
Category
Operational data
Section 20 meaning
The UTC date and time at which the Communications Hub last communicated with the Device with the corresponding entry in DeviceLog(CHF).logEntries[0..16]

Documented touchpoints

Evidence:source paragraph 484, 485Section 20 row 990

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.