meta data for this page
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
homeautomation2018:group3:start [2018/05/17 18:19] anpham [Documentation] |
homeautomation2018:group3:start [2018/05/21 14:11] (current) anpham [Documentation] |
||
|---|---|---|---|
| Line 2: | Line 2: | ||
| ====== Group 3: Pied Piper ====== | ====== Group 3: Pied Piper ====== | ||
| ^ Name ^ Student ID ^ | ^ Name ^ Student ID ^ | ||
| - | | Amir RAHAFROUZ | 0000 | | + | | Amir RAHAFROUZ | 0528941| |
| - | | An PHAM | 0000 | | + | | An PHAM | 0528938 |
| - | | Meruyert NURGAZY | 0000 | | + | | Meruyert NURGAZY | 0528899 |
| - | | Sunnat | + | | Sunnatillo |
| \\ | \\ | ||
| ====== Problem Description ====== | ====== Problem Description ====== | ||
| Line 246: | Line 246: | ||
| </ | </ | ||
| - | ====== Protocol for Home Automation ====== | + | ====== |
| + | {{ : | ||
| + | ===== Intro ===== | ||
| + | Nowadays, there are different high data rate protocols and technologies available, but none of these meet requirements of home sensors and control devices. These high data rate technologies provide wide bandwidth and low latency, but energy consumption is high. Zigbee technology is low cost, low power and it is an excellent communication candidate which makes communication best suited | ||
| + | ===== What is Zigbee technology? ===== | ||
| + | Zigbee is the product of Zigbee Alliance and it is specifically built for control and sensor networks on IEEE 802.15.4 standard. The communication standard defines physical and MAC (Media Access Control) layers to handle many devices. The Zigbee WPAN works at 868 MHz, 902-928MHz, and 2.4 GHz frequencies. | ||
| + | ==== Interference Problem between ZigBee and WiFi ==== | ||
| + | There are different wireless technologies that share the same 2.4 GHz frequency band. Such technologies usually operate in proximity and have to co-exist with each other. For example, WiFi uses the same frequency band that is used by ZigBee, however, WiFi uses higher power levels compared with ZigBee. When the ZigBee and WiFi use the channel at the same time, an interference problem appears which causes loss of the data packets being transmitted. This will result in retransmission in both WiFi and ZigBee until a successful transmission is achieved. This, in turn, causes delay and mitigation in the delivery ratio for both technologies. Moreover, ZigBee would wait longer to get free medium for transmission, | ||
| + | |||
| + | Interference Problem between ZigBee and WiFi (PDF Download Available). Available from: https:// | ||
| + | |||
| + | ==== Zigbee Features ==== | ||
| + | Zigbee is low-cost and low-powered mesh network widely deployed for controlling and monitoring applications where it covers 10-100 meters within the range. This communication system is less expensive and simpler than the other proprietary short-range wireless sensor networks as Bluetooth and Wi-Fi. | ||
| + | Zigbee supports different network configurations for the master to master or master to slave communications. And also, it can be operated in different modes, as a result, the battery power is conserved. Zigbee networks are extendable with the use of routers and allow many nodes to interconnect with each other for building a wider area network. Most important features are: | ||
| + | * Support for multiple network topologies such as point-to-point, | ||
| + | * Low duty cycle – provides long battery life | ||
| + | * Low latency | ||
| + | * Direct Sequence Spread Spectrum (DSSS) | ||
| + | * Up to 65,000 nodes per network | ||
| + | * 128-bit AES encryption for secure data connections | ||
| + | * Collision avoidance, retries, and acknowledgments | ||
| + | |||
| + | {{ : | ||
| + | |||
| + | ==== Zigbee Architecture ==== | ||
| + | {{: | ||
| + | Zigbee system structure consists of three different types of devices such as **Zigbee coordinator**, | ||
| + | routers act as intermediary devices that permit data to pass to and go through them to other devices. End devices have limited functionality to communicate with the parent nodes such that the battery power is saved as shown in the figure. The number of routers, coordinators and end devices depends on the type of networks such as star, tree and mesh networks. | ||
| + | Zigbee protocol architecture consists of a stack of various layers where IEEE 802.15.4 is defined by physical and MAC layers while this protocol is completed by accumulating Zigbee’s own network and application layers. | ||
| + | ==== Zigbee Protocol ==== | ||
| + | Zigbee protocol architecture consists of a stack of various layers where IEEE 802.15.4 is defined by physical and MAC layers while this protocol is completed by accumulating Zigbee’s own network and application layers. | ||
| + | === Zigbee Protocol Architecture === | ||
| + | == Physical Layer == | ||
| + | This layer does modulation and demodulation operations upon transmitting and receiving signals respectively. This layer’s frequency, data rate and the number of channels are given below. | ||
| + | == MAC Layer == | ||
| + | This layer is responsible for reliable transmission of data by accessing different networks with the carrier sense multiple access collision avoidances (CSMA). This also transmits the beacon frames for synchronizing communication. | ||
| + | Network Layer: This layer takes care of all network related operations such as network setup, end device connection, and disconnection to network, routing, device configurations, | ||
| + | == Application Support Sub-layer == | ||
| + | This layer enables the services necessary for Zigbee device object and application objects to interface with the network layers for data managing services. This layer is responsible for matching two devices according to their services and needs. | ||
| + | == Application Framework == | ||
| + | It provides two types of data services as a key-value pair and generic message services. A generic message is a developer-defined structure, whereas the key-value pair is used for getting attributes within the application objects. ZDO provides an interface between application objects and APS layer in Zigbee devices. It is responsible for detecting, initiating and binding other devices to the network. | ||
| + | |||
| + | === Zigbee Packet === | ||
| + | Zigbee networks can be configured in many different ways. Let’s consider the simple case of a single full-function device controlling multiple reduced-function devices in a time-slotted manner using beacon frames. Figure 6.17 shows the case where the Zigbee network divides time into recurring superframes, | ||
| + | {{ : | ||
| + | |||
| + | ==== Zigbee Operation Modes ==== | ||
| + | Zigbee two-way data is transferred in two modes: Non-beacon mode and Beacon mode. In a beacon mode, the coordinators and routers continuously monitor the active state of incoming data hence more power is consumed. In this mode, the routers and coordinators do not sleep because at any time any node can wake up and communicate. However, it requires more power supply and its overall power consumption is low because most of the devices are in an inactive state for over long periods in the network. | ||
| + | {{ : | ||
| + | In a beacon mode, when there is no data communication from end devices, then the routers and coordinators enter into the sleep state. Periodically this coordinator wakes up and transmits the beacons to the routers in the network. These beacon networks are work for time slots which means, they operate when the communication needed results in lower duty cycles and longer battery usage. These beacon and non-beacon modes of Zigbee can manage periodic (sensors data), intermittent (Light switches) and repetitive data types. | ||
| + | |||
| + | ==== Zigbee Topologies ==== | ||
| + | Zigbee supports several network topologies; however, the most commonly used configurations are the star, mesh and cluster tree topologies. Any topology consists of one or more coordinator. In a star topology, the network consists of one coordinator which is responsible for initiating and managing the devices over the network. All other devices are called end devices that directly communicate with the coordinator. This is used in industries where all the endpoint devices are needed to communicate with the central controller, and this topology is simple and easy to deploy. | ||
| + | In mesh and tree topologies, the Zigbee network is extended with several routers where the coordinator is responsible for staring them. These structures allow any device to communicate with any other adjacent node for providing redundancy to the data. If any node fails, the information is routed automatically to other devices by these topologies. As the redundancy is the main factor in industries, hence mesh topology is mostly used. In a cluster-tree network, each cluster consists of a coordinator with leaf nodes, and these coordinators are connected to parent coordinator which initiates the entire network. | ||
| + | {{ : | ||
| + | ==== Zigbee Use-cases ==== | ||
| + | === Industrial Automation === | ||
| + | In manufacturing and production industries, a communication link continually monitors various parameters and critical equipment. Hence Zigbee considerably reduces this communication cost as well as optimizes the control process for greater reliability. | ||
| + | === Home Automation === | ||
| + | Zigbee is perfectly suited for controlling home appliances remotely as a lighting system control, appliance control, heating and cooling system control, safety equipment operations and control, surveillance, | ||
| + | Smart Metering: Zigbee remote operations in smart metering include energy consumption response, pricing support, security overpower theft, etc. | ||
| + | ===Smart Grid Monitoring === | ||
| + | Zigbee operations in this smart grid involve remote temperature monitoring, fault locating, reactive power management, and so on. | ||
| + | This is all about a brief description of Zigbee technology’s architecture, | ||
| + | |||
| - | Discuss one protocol here | ||
| ====== Poster ====== | ====== Poster ====== | ||
| + | {{ : | ||
| + | |||
| + | ====== Documentation ====== | ||
| + | 1. Report: {{ : | ||
| + | |||
| + | 2. FHEM config file: {{ : | ||
| - | ====== Presentation ====== | + | 3. [[https:// |
| - | [[https:// | + | 4. {{ : |
| ====== References ====== | ====== References ====== | ||
| Line 268: | Line 338: | ||
| - https:// | - https:// | ||
| - https:// | - https:// | ||
| + | - Kurose, James F., and Keith W. Ross. " | ||