BS ISO IEC 29341-30-1-2015 pdf free download – Information technology — UPnP Device Architecture Part 30-1: Sensor management device control protocol — Sensor management architecture.
4.1 The SensorManagement device provides the following services:
• Sensor Description
• Sensor Data Transport
• Device Protection (opt)
• Vendor defined services (opt)
The following figure shows component services contained in the UPnP SensorManagement device:
4.1.1Sensor Data Model
The UPnPSensorManagement device includesan instance of the UPnPConfigurationManagement service [16]. The UPnP SensorManagement Sensor DataModelservice specification [14] defines the SensorManagement Sensor DataModel service and aprofile for hosting the “ConfigurationManagement service within the SensorManagementdevice.The SensorManagement Sensor DataModel service provides the primary method forUPnP home-network clients to identify sensors and ‘actuators supported by theSensorManagement device.
4.1.2Sensor Collections
UPnP SensorManagement groups Sensors within SensorCollections(s) which provide bothphysical and logical context for otherwise unrelated sensors. A simple example would be arefrigerator. This device would likely support a number of different types of sensors whichperform various functions such as compartment temperature control and monitoring,powerusage and door status.However, given the myriad of real-world uses of sensors, UPnP doesnot typically attempt to define a standard sensor model for refrigerators. Instead，UPnPSensorManagement advertises the type of the collection, allowing UPnP control points whichrecognize the advertised collection type to provide user-interface and control services.
4.1.3Sensor Control
Sensors managed by UPnP SensorManagement are generally expected to operate withoutdirect supervision by UPnP home-network clients.However，the SensorManagement devicedoes provide basic facilities to enable automatic polling of sensors which require it. Thesefacilities are controlled by parameter nodes in the UPnP SensorManagement SensorDataModel service [14]. In addition, sensor types which require more detailed controls maydefine additional control parameters under the CollectionSpecific and SensorSpecific nodes ofthe UPnP SensorManagement Sensor DataModel service.
4.1.4Sensors Dataltem(s)
UPnP treats Sensor(s) as sources of data.UPnP defines the term Dataltem as a data source(or sink) with a “name”, an associated “type” and “encoding”.The data type associated with a Sensor Dataltem may range from simple scalar quantities to an XML document depending onsensor’s parent ecosystem.Each Sensor may define multiple Dataltem(s) which are groupedunder a SensorURN node.
4.1.5Sensor Dataltem Description Document
Many sensors generate simple data and in these instances a text-based description of thesensor accompanied by information on the method of sampling, (average, instantaneous) andthe units of the measurement are sufficient to interpret the information provided by a Dataltem.To facilitate the description of Dataltem(s)，UPnP SensorManagement defines DataltemDescriptive XML schema [25]. This XML document is provided by the Sensor’sDataltem’s Description parameter node (see subclause 4.4，”Dataltem Description XMLDocument”).
4.1.6Sensors DataRecord(s)
A UPnP SensorManagement device can advertise sensors which may generate one or moreDataltem(s). A UPnP client can then inspect the Dataltem(s) advertised for the target Sensorand can request generation of DataRecord(s) consisting of a requested subset of Dataltem(s)provided by the Sensor.
4.1.7Sensors Data Transport
A UPnP SensorManagement devices supports two methods for obtaining sensor data:. HTTP/HTTPS based transport connections
. SOAP based transport
When using HTTP transport connections，a SensorManagement control point provides atransport URL that can accept DataRecord(s) produced by the SensorManagement device.The control point then issues SOAP actions to the SensorManagement device providing thetransport URL and the Dataltem(s) to be included in the DataRecord(s) provided.Onceestablished, the SensorManagement device will connect directly to the HTTP server identifiedby the transport URL and will deliver DataRecord directly’without further control pointinteraction.This method is suited to cases where a sensor may either generate large amountsof data as well as sensors which generate infrequent data requests. in addition, this methodallows the SensorManagement device to support multiple independent transport connectionsallowing sensor data to be replicated to multiple UPnP clients.
When using SOAP based transport，the SensorManagement device generates an eventindicating one or more Sensor(s) has data available to be read.A UPnP SensorManagementcontrol point can then issue a SOAP action to request DataRecord(s) from the SensorSensorManagement device SensorGenericTransport service.BS ISO IEC 29341-30-1 pdf download.