AmI Taxonomy AmI Taxonomy Network Characteristics of the - - PDF document

AmI Taxonomy

AmI Taxonomy

Network Characteristics of the technologies allowing devices to communicate an collaborate in the exchange of information. Infrastructure How the devices communicate. Wired All devices are connected trough a set of wires. Depending on the protocol, we may use 2 wires or more. Examples: KNX, bTicino MyOpen, ModBus Powerline Re-uses the power lines for data communication, by modulating signals that are superimposed to the electric AC supply. Examples: Lonworks, Echelon (e.g. the ENEL meter), X10 Wireless Uses radio frequencies to exchange data. Devices need not be connected for communicating. They may need to be connected for power supply. Examples: Z-Wave, ZigBee, Wi-Fi, Bluetooh, 433Mhz, ... Mixed

AmI Taxonomy file:///D:/Mirror/elite/Didattica/Laurea/01PRD Ambient Intelligence/sl... 1 di 9 08/05/2014 14:50

Some technologies may allow a mix of different connection methods. Mainly, wired technologies that allow for wireless extensions. Also, Wireless technologies that allow routing through a physical link. Examples: KNX. ModBus Topology The set of physical paths that are followed by communication messages. Bus One flat shared infrastructure where every node may send information to every other node directly, without intermediaries. Routed Special nodes are used to route and forward messages between different segments of the network. Example: in ZigBee and Z-Wave, powered devices may act as routers. Mesh Messages may be routed through any device, and are relayed until they reach the destination. Often, the mesh is dynamic and may be reconfigured (automatically or programmatically) according to device locations, and signal strength). Example: practically all wireless protocols Star All devices connect to one specific central node and may exchange data only with that node. Logical Hierarchy What is the flow of communications among nodes. Master-slave Only one "central" node (master) may contact all other nodes (devices, slaves). The master may be fixed, or may change over time (but only one master at a time must be active). Examples: ModBus, RFID, USB, CAN, ... Multi-master A master-slave hierarchy where more than one node may play the role of the master, simultaneously. Peer to peer All nodes in the network play the same role. Each of them may send/receive messages to any other node. Examples: IP-based networks, KNX Coordinator + nodes Mainly peer to peer network (nodes may communicate directly), where one node has a distinguished role of "coordinator" of the network (that has some unique and specific services and capabilities). The coordinator may be needed to keep the list of registered devices, or to allow devices to join the network, or to manage device configuration, etc. Examples: KNX, Z-Wave, ZigBee. Controller/Master In master-slave or coordinated networks, what is the nature of the controller or master node. Not needed Special node (boundary) One special device in the network takes the role of a controller or master. Very often, this device is also at the "boundary" with external infrastructure: it may be connected to the LAN, it may offer serial/USB

• ports. In these cases, all communications to/from the devices will always be routed by the controller, that thus acts as a gateway, too.

Examples: ModBus, MyOpen, KNX Any node Any node (e.g. through election mechanisms) may take the role of controller. Examples: SMB Addressing

AmI Taxonomy file:///D:/Mirror/elite/Didattica/Laurea/01PRD Ambient Intelligence/sl... 2 di 9 08/05/2014 14:50

The mechanism by which each device can be identified uniquely in the network, and messages may find the correct destination. Device address Each physical device has one specific address. The address may be hardware-defined (e.g. MAC addresses in WiFi or Bluetooth, or jumpers in MyOpen), or software-assigned (e.g., IP addresses in DHCP). Serial number Network address Group address In some networks, we may define addresses that reach "groups" of devices. Similar to "multicast" messages. Groups may be formed by the controller node, or may be published by the devices. Sub-function address Some devices include multiple sub-devices, that are separately addressable. Example: a bank of 8 relays (KNX "endpoints"), ModBus register ranges Discovery Capability of the network of determining which devices are currently connected, and what is the nature of those devices. Discoverable The network has a discovery capability. In some cases it needs to be activated with a special command (e.g. KNX). In other cases the list of devices is always kept updated (e.g., Z-Wave). Non discoverable No discovery available. To contact devices, you must know (beforehand) their addresses (at least). Example: MyOpen, ModBus Communication When information messages are exchanged among devices/nodes. Polling Nodes may be queried by the controller/master. Nodes will never send any communication, unless explicitly queried. To have an updated state of the network, usually a periodic "polling cycle" in needed, where each devices is queried at regular time intervals. Examples: ModBus Synchronous Devices can be instructed to send their status (or their measurements) at regular intervals (e.g. a new data sample every 200ms). In some cases, the temporal sequence of communications is predetermined (i.e., there is a global "time wheel" and each device has one specific "time slot" in which it transmits). This is usually associated with tight timing constraints. In other cases, the device decides to transmit on its own schedule, and accesses the network at that time. Examples: CAN Asynchronous (events) Devices may transmit data at any time. This is often associated with transmission of information related to specific "events": a button has been pressed, a sensor has crossed a threshold, some condition has been met, etc. Asynchronous event sending may also be combined with periodical synchronous updates (e.g., send updates every 30 minutes, but send an update immediately if the temperature has changed more than 1°C). Example: Z-Wave sensors. Data handling What is the conceptual data model uses to represent and exchange information with the device. Register-based

AmI Taxonomy file:///D:/Mirror/elite/Didattica/Laurea/01PRD Ambient Intelligence/sl... 3 di 9 08/05/2014 14:50

Devices offer a bank of registers (usually, 8-bit). Each register (or pair/quadruple) or register encodes a specific value. Values may be read-only (e.g., for sensor values), or write-only or read-write (e.g., for sending commands or configuring the device). The meaning of the registers must be known to the programmer (e.g., through the device data sheets). Example: ModBus Command-based Devices can be contacted by sending commands (usually, in an asynchronous way). Commands may have parameters. Commands may change the device status, cause some actions, or modify device configuration. Commands may also be used to query for device values. Examples: KNX, MyOpen, Z-Wave Notification-based The device will send (usually in an asynchronous way) some message (event, notification), according to its internal strategies and configuration. Examples: MyOpen, Z-Wave Transport Protocol The organization of binary messages, their format, their exchange mechanisms. At this level, we are not concerned with the meaning of messages, but just with their encoding and transmission. Open standard The format of data and messages is public, is often "blessed" by some standardization organization, and everybody is free to read, write, and develop new components using those messages. Examples: ZigBee (TCP)/IP Data transmission is based on the IP (Internet Protocol). Both bare-IP or TCP-over-IP are used. This usually requires more powerful nodes and may open the device to the "Internet of Things" Examples: surveillance infrastructures, industrial internet, internet of things, ... Proprietary standard The format of data and messages is known, and has been defined by a company (or by a closed group of companies). Developing new components using the standards may be: forbidden -or- requiring a certification -or- allowed. Usually it requires signing some agreement or joining some association. Examples: MyOpen, KNX Generally available Even if the standard is controlled by some commercial entity(ies), its specification is public. Example: MyOpen Restricted availability Accessing the technical documentation requires joining some association and/or signing some agreement. Example: KNX Ad hoc Proprietary system, usually developed by one company, that uses custom methods, protocols, and data formats. Such protocols are not published, and usually components must be developed (or adapted) by the company. Examples: too many. Application protocol The high-level format of messages (where the messages assume an application-defined meaning). An application protocol may usually be applied on-top-of different transport protocols. Open standard

AmI Taxonomy file:///D:/Mirror/elite/Didattica/Laurea/01PRD Ambient Intelligence/sl... 4 di 9 08/05/2014 14:50

The application protocol has been defined and/or approved by a recognized independent standardization authority (e.g., IEEE, IETF, ISO, W3C). Examples: ZigBee, WiFi Proprietary standard The application protocol has been defined and/or approved by a company or a group of companies. Examples: KNX, MyOpen Ad hoc The application developer chose to adopt an application protocol without resorting to standard ones. This may happen even if the transport protocol is standard. Device association The mechanism by which a new device/node may "join" the network and be recognized by other nodes. Not needed The network infrastructure does not require devices to be associated, they just need to be connected and they may start communicating. Some mechanism (or some external information) will be required to discover them. Example: IP/Ethernet, ModBus Through configuration The devices are configured in such a way that, when connected, will be able to exchange data. Example: MyOpen Explicit association There exists a specific modality in the network, usually managed by a controller, that opens the network to accepting new devices. A specific association procedure must be correctly managed, and it usually involves both the controller and the (new) device. Note: this association usually generates a "shared secret", a cryptographic information that will be used to encrypt traffic and/or to recognize the device in the future. Examples: Bluetooth pairing, Z-Wave, ZigBee Automatic association When a new device is connected to the network, it executes a association procedure, that may be completed by the network controller without user intervention. New devices may join the network at any time, provided they may connect at the physical level. Examples: DLNA, USB Configuration The mechanism for determining the operating parameters of the network (besides addressing). Not needed Network behavior is fixed. No configuration is required. Example: MyOpen Managed An external tool/application/procedure must be used to configure the network parameters. Examples: TCP/IP, KNX (Semi)Automatic The network is able to auto-adapt (within limit) and self-configure (within limits). Examples: wireless mesh networks Device Functions What is the intended purpose of the device, from the application point of view. Here we refer to the main function of the device, of course there will be network-specific functions (i.e., routing, association, ...) that will always be present.

AmI Taxonomy file:///D:/Mirror/elite/Didattica/Laurea/01PRD Ambient Intelligence/sl... 5 di 9 08/05/2014 14:50

Examples: meter, sensor, switch, ... Single-function The device may accomplish only one (main) function. Multi-function The device may implement more than one main function. Example: multi-sensors, 8-relay bank. Identification How the device describes itself to the network (visible to the other devices, the controller, and the applications). Manufacturer / Model number The device published an identification of the manufacturer, and an identification of the model produced by that manufacturer. Manufacturer IDs are released by some naming authority, while model IDs are specific to each manufactures. No explicit information about the function, some external information about the device (e.g., through datasheets) is needed. Device type The device is classified according to a network-dependent list of possible device types, defined by the standard. The device should implement and behave accordingly to its category. Extensions to this behavior are possible, but in some cases they may not be "declared" by the device itself. Example: KNX, MyOpen List of functions The device is described by listing a set of functional identifiers, each representing a subset of the device capabilities. Examples: ZigBee Clusters, Z-Wave Command Classes (ex: http://wiki.micasaverde.com/index.php/ZWave_Command_Classes) Intelligence What is the internal intelligence available to the device. Dumb The device has no possibility of being programmed. It executes its function in a rigid and pre-defined way. The only configuration is one related to network addressing. Configurable The device accepts one or more configuration parameters. Such parameters will modify its behavior, according to pre-defined schemes. Parameters may be thresholds, time outs, notification frequencies, enable/disable some advanced functions and/or some I/O channels, ... Most devices fall into this category. Programmable Devices allow some software to be written into their memory, and will execute such program. Firmware Only software produced by the device manufacturer may be downloaded on the device. Example: KNX Application software The application developer has the possibility to download some specific software. Example: programmable displays

AmI Taxonomy file:///D:/Mirror/elite/Didattica/Laurea/01PRD Ambient Intelligence/sl... 6 di 9 08/05/2014 14:50

Smart The device has a "powerful" operating system on-board, and executes a complex application, trying to fulfill its goals. May or may not be programmable/configurable. Example: the Nest thermostat Automation The mechanism by which devices may co-operate and implement automatic behaviors, without requiring external applications. Triggers The device will emit an event upon reaching some internal condition. The event might be sent in broadcast, to a group, or to a device. Another device will react to this event, and trigger some of its actions. Receiving devices may need to 'subscribe' to event streams or notifications. Example: Z-Wave, ZigBee Bindings One function/variable/sensor of one device is "bound" to one function/action/command of another device (or group). The binding mechanism guarantees that the destination device will always react to changes of the source variable, thus creating a virtual link between the two devices. Example: KNX Address matching The network addresses of the devices are assigned in such a way to create a fixed binding between devices with same (or matching) addresses. The behavior of the network is therefore dependent on the assignment of addresses. Example: MyOpen None Devices don't have autonomous automation capabilities. Everything should be managed by the controller and/or the application. Example: ModBus Configuration The mechanism for defining/loading configuration parameters into the device. In-network The network protocol itself contains commands/methods for modifying device configuration. Devices may be reconfigured at runtime, by using "normal" commands/methods. No additional or more advanced mechanism is available. Example: ModBus, Z-Wave With ad hoc tools / procedures Some external tool (software and/or cable) must be used to put the network in configuration mode and download configuration information into the devices. This may be interactive (view&modify parameters) or batch (download all configuration at once). Example: KNX

AmI Taxonomy file:///D:/Mirror/elite/Didattica/Laurea/01PRD Ambient Intelligence/sl... 7 di 9 08/05/2014 14:50

Manual (hardware) Some physical modification to the device is needed. The user should modify some micro-switch, some jumper position, some (un)connected pin, ... Example: MyOpen Power How the device gets its power supply. Powered (always-on) The device is connected to a (wired) power supply line. Mains Power is delivered through the AC mains lines. Each device is connected to the mains (usually through a transformer). Example: WiFi cameras Bus The network bus (for transferring data) also has the capability to transport power (usually DC) to all connected devices. The bus must be terminated by a suitable power supply (or more than one, if the network layout is too wide). Examples: Power-over-Ethernet, MyOpen, KNX

AmI Taxonomy file:///D:/Mirror/elite/Didattica/Laurea/01PRD Ambient Intelligence/sl... 8 di 9 08/05/2014 14:50

Battery-operated (mostly sleeping) Devices are not connected to an external power supply, and rely on a local battery (rechargeable or disposable). To enable sufficient battery duration, such devices are usually in sleep mode (only minimal functionality is available, such as sensing

• r metering), and they wake up at regular (but long) interval, and/or when they have some data to transmit or some triggering event.

Only when in the wake-up period, they may receive commands. Example: Z-Wave, ZigBee Energy harvesting The device is not connected to a power supply, and does not have any on-board battery. The device gathers the energy by harvesting it from the surrounding environment (light, movement, RF waves). Sometimes the presence of the energy source triggers device activity. In other period, the device is shut-off (not even sleeping, in most cases). Examples: RFID, EnOcean Location Where the device is physically located, and whether it may be moved during its operation. Fixed The device is in a fixed location, e.g., wired and connected to a wall fixture. It may not be moved without shutting down the network. Example: KNX, MyOpen Movable The device must be connected to operate, but may be easily disconnected, moved to a different location, and reconnected. After the move, reconfiguration is not necessary or automatic. Examples: Z-Wave smart plugs, Ethernet devices Mobile The device has no specific location, may be moved around freely. Example: mobile phone, RFID On-person The device is mobile, but is usually attached to one person. Example: smart watch. Virtualization The ability of integrating into a network one device that does not belong to the same technology Software nodes Software modules, that are running on the controller and/or the gateway and/or some "rich" network node and/or on some application sever, that "emulate" the presence and the behavior of some specific node. Foreign protocol proxy Devices that may forward (unidirectionally or bidirectionally) information to other "real" devices (or groups of devices) that speak a different protocol/technology. This technique is adopted to integrate a (small) number of "different" devices into an otherwise-uniform network. Application area Automation Lighting Metering Entertainment Automotive General purpose

AmI Taxonomy file:///D:/Mirror/elite/Didattica/Laurea/01PRD Ambient Intelligence/sl... 9 di 9 08/05/2014 14:50