Technologies de l’information — Architecture de dispositif UPnP — Partie 30-1: Protocole de contrôle de dispositif de gestion et de contrôle de l’Internet des objets — Aperçu général de l’architecture de gestion et de contrôle de l’Internet des objets

1.1 Introduction

This document describes the overall UPnP IoTManagementAndControl Architecture, which forms the foundation for the UPnP IoTManagementAndControl device [11] and UPnP DataStore service [13] specifications. The IoTManagementAndControl device hosts services to bridge sensor devices connected to both UPnP networks as well as non-UPnP based networks. The DataStore service provides persistent retention and distribution of both sensor data as well as data from mobile devices which may leave the UPnP network at any time. This service can be hosted within the UPnP IoTManagementAndControl device as well as within other UPnP compliant devices.

1.2 Goals

The UPnP IoTManagementAndControl Architecture was explicitly defined to meet the following goals:

• Describe sensors and actuators residing on both UPnP and non-UPnP networks.
• Provide data transport services for sensors and actuators to UPnP network clients.
• Define a service to describe, retain and distribute data received from sensors as well as  other non-persistent data sources.
• Define an allowed device protection model for both the sensor and data retention components. 

1.3 Non-Goals

The following are not initial goals of the IoTManagementAndControl architecture:

• Low-level control of bridged networks

The initial version of UPnP IoTManagementAndControl treats Sensors and Actuators as abstract data sources and sinks and does not expose details or provide direct access to bridging network protocols. Low-level control of selected bridged network protocols will be considered in subsequent versions of the architecture.

• Low-latency control of sensors and actuators

The initial version of UPnP IoTManagementAndControl treats sensors and actuators as autonomous objects requiring relatively infrequent supervision from home-network clients. Closed loop control of sensor and actuator pairs is better accomplished directly within the internal vendor-device sensor/actuator architecture with UPnP home-network clients providing overall supervision. However, UPnP IoTManagementAndControl does support sensors which have substantial throughput requirements using transport connections. 

1.4 IoTManagementAndControl and DataStore Specification Map

IoTManagementAndControl Architecture Overview [10]

• Sensor Discovery and Description

– IoTManagementAndControl Detail Overview
– Sensor Protection Model
– DataStore Detail Overview
– DataStore Protection Model
– DataItem Description and Semantics
– Sample Implementation Theory of Operation

IoTManagementAndControl Device

IoTManagementAndControl Device Specification [11]
• Sensor Components High-Level Overview
• IoTManagementAndControl Required/Allowed Services

IoTManagementAndControl Sensor DataModel Service Specification [14]

–  Sensor Discovery and Description
– Sensor URN Description
– Sensor Event Model Description
– ConfigurationManagement service action(s)
– Mandatory DataItem(s)
– Common Sensor Collection types
– Sensor Data Model
– IEEE-11073 Medical Device Data Model

SensorTransportGeneric Service Specification [12]

• Sensor Transport (SOAP/HTTP)
– Sensor Transport action(s)
– Sensor Data Record(s)

DataStore Service Specification [13]            
• Persistent Data Retention
– DataStore URN Description
– DataStore (LastChange) Event Model
– DataStore action(s)
– DataTable schema(s)

Device Protection Service Specification [15]
• Device Protection
– Device Protection action(s)