Overview
ISO/IEC 29341-30-11:2017 is part of the UPnP Device Architecture suite and specifies Sensor Data Models for UPnP-based IoT management. Published as “IoT management and control device control protocol - IoT management and control data model service,” this document defines how sensor metadata, data records, eventing and control interfaces are modeled so that sensors and managers can interoperate across UPnP-enabled IoT ecosystems. It is intended as an adjunct to the IoT Management and Control Device and the DataStore Service specifications.
Key topics and technical requirements
The standard provides normative rules and data structures that support consistent sensor behavior and integration:
- Data model scope: Defines sensor descriptions, sensor data interfaces and sensor data records to standardize representation of measured and derived values.
- Notations and data types: Specifies notation conventions, EBNF usage and a set of data types to ensure unambiguous model interpretation.
- Vendor extensions: Guidance for vendor-defined extensions while preserving core interoperability.
- Sensor URNs and identifiers: Lists canonical SensorURNs, identifier types and identifier-dependent values for device discovery and mapping.
- Required DataItems and normative type identifiers: Enumerates mandatory DataItems and type identifiers to support consistent implementations.
- Event model and state variables: Defines eventing attributes, event enablement, and state variables used for subscription/notification mechanisms.
- Service actions: Standard action set to query and manipulate models and instances, including:
- GetSupportedDataModels()
- GetSelectedValues()
- SetValues()
- CreateInstance()
- DeleteInstance()
- SetAttributes()
- Security & permissions: Tables and defaults for permission settings and script-level access control (see annex tables on permissions).
- Annexes: Normative General Data Model, Required DataItems, Common Device Identifiers, and IEEE-11073 Personal Health Devices mapping for medical-device interoperability.
Practical applications and target users
ISO/IEC 29341-30-11:2017 is useful for organizations that need interoperable sensor data and control in UPnP/IoT deployments:
- Device manufacturers: implement consistent sensor metadata, URNs, and eventing to ensure compatibility with UPnP controllers.
- Firmware and middleware developers: map sensor outputs to the required DataItems and implement the specified actions and state variables.
- IoT platform and gateway vendors: integrate DataStore and IoT Management services to aggregate, store, and control sensor data.
- Healthcare device integrators: use the IEEE-11073 mappings in Annex D to align personal health device data with UPnP IoT models.
- System integrators and testing labs: validate compliance, interoperability and eventing behavior across multi-vendor environments.
Related standards and references
- ISO/IEC 29341 series (UPnP Device Architecture) - foundational UPnP Device and Service specifications
- IoT Management and Control Device (Part 30-xx) and DataStore Service (referenced as DataStore Service [13])
- IEEE-11073 (referenced for medical-device mappings in Annex D)
Keywords: ISO/IEC 29341-30-11:2017, UPnP Device Architecture, Sensor Data Models, IoT management and control, DataStore Service, Sensor URN, IEEE-11073, IoT interoperability.
Open preview (PDF)Information technology — UPnP Device Architecture — Part 30-11: IoT management and control device control protocol — IoT management and control data model service
