BS ISO IEC 29341-30-1:2015 pdf free download – Information technology – UPnP Device Architecture
3.1.1Sensor
A Sensor defines sets of named Dataltem(s) (see subclause 3.2) which can be read and/orwritten via the SensorTransportGeneric service [12]. Access to Sensor Dataltem(s) isprovided by UPnP SOAP actions or via HTTP sensor transport connections. Discovery,control and status of Sensor(s) are provided through parameter(s) defined by theSensorManagement Sensor DataModel service [14]. Depending on the type of Sensor,additional sensor control and status parameters may also be defined by additional sensorecosystem specific specifications.
3.1.2 SensorCollection
A SensorCollection contains zero or more Sensors. The Sensors enumerated within aSensorCollection typically relate to a real world device. In some instances the Sensors maybe directly related to the operation of the device such as an IEEE-11073 Medical DeviceSystem [9], while in other instances,Sensors may indirectly assist in performing monitoringand possibly control operations on the device; such as sensors within a refrigerator or homethermostat.SensorCollections may identify other UPnP Devices which can provide additionalcommand and control functionality.
3.1.3 SensorGroup
Sensors can be grouped using SensorGroup(s).An individual Sensor may participate (be amember of) zero or more SensorGroup(s).SensorGroup(s) may include Sensors from multipleSensorCollection(s). In addition to identifying related Sensors，SensorGroup(s) also can beassigned DeviceProtection permissions which can then be used as DeviceProtection Roles.
3.1.4 SensorlD
A SensorlD is an identifier which uniquely identifies a Sensor to SOAP actions implementedby the SensorTransportGeneric service [12]. SensorlD values are provided by theSensorManagement Sensor DataModel service [14] SensorlD parameter node.
3.1.5 SensorNode
A SensorNode is a set of SensorManagement Sensor DataModel [14] nodes which describe aSensor and the Dataltem(s) it supports. The required and allowed SensorNode parametersand corresponding syntax and semantics are detailed by SensorManagement SensorDataModel service specification.
4.1.1Sensor Data Model
The UPnP SensorManagement device includes aninstance ofthe 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 forUPnPhome-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.