How should teams handle constrained devices under ETSI EN 303 645 for consumer IoT products?
Start with the ETSI definition. EN 303 645 describes a constrained device as one with physical limitations in processing, communication, storage, or user interaction because of its intended use. The standard gives power supply, battery life, processing power, physical access, limited functionality, limited memory, and limited network bandwidth as examples of limits.
That status does not remove the product from the standard. EN 303 645 says its baseline provisions apply across consumer IoT, while recognizing that applicability is device-dependent. A constrained-device decision therefore belongs in the implementation record for the specific provision, product, and feature.
- Identify the physical constraint and explain why it arises from intended use, not from an avoidable design shortcut.
- Apply each provision normally unless the provision's own condition, product functionality, or documented risk rationale supports a different answer.
- Record whether the provision is supported, not supported, or not applicable, with enough detail for an assessor, supply-chain reviewer, researcher, or retailer to understand the decision.
Defines constrained devices and explains that provision applicability depends on the device while EN 303 645 remains a consumer IoT baseline.
Explains that the supplier organization provides ICS and IXIT information and that a test laboratory uses them to derive the test plan.