1 / 30

INtegration and Demonstration of Energy Efficient Dwelling NETwork (IndeedNET)

INtegration and Demonstration of Energy Efficient Dwelling NETwork (IndeedNET). Prof. Shaun H Yang FInstMC, SMIEEE, CEng. Email: s.h.yang@lboro.ac.uk Telephone:01509-635670. Outline. IndeedNET Overview Consortium Project web site System architecture Work plan Questions.

efuru
Download Presentation

INtegration and Demonstration of Energy Efficient Dwelling NETwork (IndeedNET)

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. INtegration and Demonstration of Energy Efficient Dwelling NETwork (IndeedNET) Prof. Shaun H Yang FInstMC, SMIEEE, CEng Email: s.h.yang@lboro.ac.uk Telephone:01509-635670

  2. Outline • IndeedNET Overview • Consortium • Project web site • System architecture • Work plan • Questions

  3. IndeedNET Overview • This project aims to develop a wireless sensor/actuator information infrastructure within and beyond the home to enable residents both locally and remotely to intelligently and easily monitor and control the energy use within their homes. • The projects aims to produce an affordable system focused on energy conservation within the home.

  4. Features of IndeedNET • Wireless sensor/actuator Home Network • Energy saving focused • Operated locally and remotely • Easy-to-install • Low cost • Distinguish from next wave technology, EHS, and X10

  5. Consortium

  6. Role of Advantica • Project management • Providing the test house for system implementation and demonstration for a period of time • One engineer to support a research assistant (Loughborough University employed) to implement and demonstrate the system.

  7. Role of Sure Technology • Assist in two-way wireless communication technology development. • Assist in hardware design, including radiator valves, window opening devices, wireless light and remote control device

  8. Role of EMHA • Assist in end-user requirement analysis • Assist in dissemination and demonstration

  9. Role of Loughborough University • Technical development of IndeedNET system • Document preparation

  10. IndeedNET website An official project website domain name has been registered. http://www.indeedNET.org

  11. Private part • All the minutes of meeting, technical reports will be uploaded in the private part. • Advantica (Username: Password: ) • Loughborough (Username: Password: ) • Sure (Username: Password: ) • EMHA (Username: Password: )

  12. System Conceptual Architecture

  13. Requirements The indeedNET project consists of four identifiable entities

  14. System Core Entity ? • The System Core entity is located within the home environment and performs activities such as user authentication, message distribution and forms the core of the system. • The system core entity may be formed of more than one device. • Master Device Node (MDN), Web Server Device Node (WSDN), Wireless Access Point and ADSL modem.

  15. Device(s) Entity ? • The Device(s) are the products that will run on the system including products designed to save domestic energy. • Device Node (DN)

  16. Local User(s) Entity ? • Local User(s)” are the people who will access the system using the system remote control, form a given area around the system core. • Local Remote Controller Node (LRCN)

  17. Remote User(s) Entity ? • The Remote User(s) are the people and devices that will connect to the system over the internet. These users could be from outside of the home using a mobile phone or inside the home using a desktop computer. • Remote Controller Node (RCN).

  18. Master Device Node • The master device node also known as the control node is at the heart of the system. The MDN is responsible for device registration and deregistration, implementation of security procedures and the routing of all communications to end devices. • The MDN consists of five crucial hardware components: • Microprocessor • Wireless two way communications module (Jennic ZigBee IEEE802.15.4 ) • AES encryption module • Spread spectrum module • Battery Backup

  19. Device Node • The device nodes are the end devices that will connect to the LR-WPAN, they will consist of the following crucial hardware elements. • The DN consists of four crucial hardware components: • Microprocessor • Two way wireless communication module (Jennic ZigBee IEEE802.15.4 ) • AES encryption module (Optional Dependent on specific end device) • Battery Power/Mains Power or combination of the two using the battery as a backup during power failure.

  20. Device Node • The DN offer similar services to the MDN however there are two unique policies which are detailed below. • Alert Policy: The alert policy will send alert messages to the MDN from the DN one at a time in the order that they occurred. The DN will not use a sorting algorithm to send each alert in the order of priority as it would be faster to send them as soon as it gets them as the event of multiple alerts at any one moment is unlikely. • Device Configuration Policy: The DN will change its configuration based on commands from the MDN. The DN will send an update request to the MDN if one of its settings is manually changed to update the devices table in the system database. If the device is changed manually and remotely at the same time the manual setting will be used and the remote user sent an error message.

  21. Local Remote Controller Node • The LRCN will provide local users within a certain range of their MDN to access and control their system. We will use an existing hardware controller running our software for this part of the system. The controller will have to be modified so that its uses ZigBee to access the system. • The crucial hardware parts of the controller are as follows • Hardware controller

  22. Remote Controller Node • The remote controller will not be provided by the indeedNET project, the system will be designed to be operated by any hardware device such as a pda, phone, web TV that supports an html compatible web browser and the minimum requirements outlined by the final system specification. • The RCN will be any device the user may choose to access the home system from a location outside of the house. • The RCN will access the system over the internet through a web browser. • The RCN will have to support the level of security required by the system.

  23. Web Server Device Node • The WSDN is an optional plug-in device that users who wish to access their system over the internet through a web page will be able to purchase and in a plug and play manor connect to their LR-WPAN. The WSDN will consist of the following crucial hardware components. • Microprocessor • Web Server Module (Built in security or use AES Module) • Two way communication module • The services that the WSDN will provide are similar to those offered by the other devices however include the following unique policy. • Wireless Protocol Policy: The WSDN will need to be able to connect to the MDN and the access point. The MDN will use ZigBee IEEE 802.15.4 to communicate the access point will use WIFI 802.11 to communicate this will require the WSDN to be able to switch its communications protocol.

  24. Wireless Access Point The wireless access point will not be designed by the indeedNET project. We will use a commercially available Wireless Access point. This is inline with one of our primary objectives of keeping the cost down. Those people who already have a wireless access point through which they connect to the internet will be able to use their existing hardware and those who do not wish to access the system over the internet will simply not need to buy this device. The wireless access point will have to provide the connection from the WSDN to the ADSL modem and thus the internet. The wireless access point must route all the network traffic from the internet to the WSDN. The wireless access point may be integrated into the ADSL modem this is the prevalent situation in the industry amongst the existing hardware. The wireless access point will have to support the security needs of the system.

  25. ADSL Modem As stated above this may be integrated with the Wireless Access point, as before this technology will not be developed by indeedNET instead we will use existing ADSL modems. This means the households that have existing broadband connections will not have the additional cost of this hardware. The ADSL modem will the portal to the internet, it will allow remote users to access the LR-WPAN. The Proposed system will require an internet connection. The Internet connection will have to have sufficient bandwidth to meet the systems requirements.

  26. System Technical Architecture A detailed view of the proposed system architecture that satisfies the specification is shown below.

  27. Work packages and Milestones • WP1: System simulation (six months) • WP2: System components implementation (six months) • WP3: System integration and testing (six months) • WP4: Demonstration and exploitation (24 months) • WP5: Project management (24 months) • M1: completion of IndeedNET simulation (Month 6) • M2: Completion of IndeedNET components design (Month 12) • M3: Completion of integrated IndeedNET (Month 18) • M4: Completion of testing and demonstration (Month 24)

  28. Work Plan

  29. Any Questions ?

  30. Demonstration of the Smart Home Environment Monitoring

More Related