CHTS requirement clause

4.6.1.3 — Model Type

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.

CHFGPFSRV 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.1.3 · item ModelType(CommsHub).value

ModelType(CommsHub) - value

SRV touchpoint

The value shall be fixed at manufacture to be the 8 octet concatenation (value of Image Type) || (value of OTA Hardware Version), and so shall be fixed to the corresponding DUIS Read Inventory DeviceModel data item value for this Device. The (value of Image Type) shall be a 4 octet utf-8 encoded, hexadecimal representation of the 16 bit unsigned integer equating to the Image Type parameter in the OTA cluster. The (value of OTA Hardware Version) shall be a 4 octet utf-8 encoded, hexadecimal representation of the 16 bit unsigned integer equating to the value of the Hardware Version parameter in the OTA cluster.

Object
ModelType(CommsHub)
Attribute / method
value
Interface disposition
E
Category
Constant data
Section 20 meaning
The value shall be fixed at manufacture to be the 8 octet concatenation (value of Image Type) || (value of OTA Hardware Version), and so shall be fixed to the corresponding DUIS Read Inventory DeviceModel data item value for this Device. The (value of Image Type) shall be a 4 octet utf-8 encoded, hexadecimal representation of the 16 bit unsigned integer equating to the Image Type parameter in the OTA cluster. The (value of OTA Hardware Version) shall be a 4 octet utf-8 encoded, hexadecimal representation of the 16 bit unsigned integer equating to the value of the Hardware Version parameter in the OTA cluster.

Documented touchpoints

Evidence:source paragraph 464, 465Section 20 row 1962

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.