IoT reference architectures and standards: an ISO/IEC 30141 overview

What a reference architecture is

A reference architecture (RA) is a generic blueprint. It does not tell you which products to buy; it gives standard names for the parts of a system, their responsibilities and the relationships between them. Teams use RAs to check designs for gaps, compare vendors on equal terms and communicate across disciplines. Think of it as a more formal, more complete version of the layered models taught in introductory courses.

ISO/IEC 30141

ISO/IEC 30141, "Internet of Things (IoT) - Reference architecture", is the international standard RA for IoT, developed by the joint ISO and IEC committee on IoT. It was first published in 2018 and has since been revised. It describes IoT through a conceptual model, a set of characteristics that IoT systems should have (such as trustworthiness, interoperability and scalability), and several viewpoints.

The domain model groups entities by function:

• Physical entity domain: the real-world things being sensed or controlled.
• Sensing and controlling domain: sensors, actuators and gateways that interact with them.
• Resource access and interchange domain: interfaces that expose data and functions to other parties.
• Application and service domain: the services and analytics built on the data.
• Operations and management domain: provisioning, monitoring, policy and device management.
• User domain: the people and systems who use the IoT services.

Viewpoints then look at the same system from different angles, such as functional, system, communications, information and usage, so that each stakeholder sees the concerns that matter to them. Domain names have been refined between editions, so always check the edition you are citing.

Other frameworks you will meet

RAs describe structure; baselines describe minimum security. Use both: the RA to make sure nothing is missing, the baseline to check each part is protected. For industrial systems, IEC 62443 adds zones, conduits and security levels.

Using an RA in practice

1. Map your design onto the RA's domains, listing every component.
2. Look for empty domains: no operations and management domain usually means no plan for updates or monitoring.
3. For each interface between domains, note the protocol, authentication and data classification.
4. Check each component against a security baseline such as EN 303 645.
5. Record the result in your design document so reviewers can follow it.

Tip: standards are copyrighted and revised over time. In academic work, cite the exact edition you used and describe it in your own words rather than copying clauses.