1. Using Mica Motes for Platform Management A Telecommunications Application

2. Telecommunications Overview Statistics $30 Billion per year industry $30 Billion per year industry 170 Million US cell phone users 170 Million US cell phone users Wired and wireless service/hardware providers Intel, Sun Microsystems, Motorola Intel, Sun Microsystems, Motorola Nokia, Ericsson, Nortel Nokia, Ericsson, Nortel

3. Telco Requirements Reliability and Availability Availability means little system “down time” Availability means little system “down time” Industry accepted standard of 99.999% availability Industry accepted standard of 99.999% availability 5 minutes of down time per year Reliability means high fault tolerance Reliability means high fault tolerance High processing power Ability to handle high network traffic Ability to handle high network traffic i.e. no dropped phone calls

4. System Form Factors Intel® NetStructure™ MPCHC0001 14U Shelf 14U Shelf Intel® NetStructure™ MPCBL0001 High-Performance Single Board Computer High-Performance Single Board Computer Intel® NetStructure™ MPCMM0001 Chassis Management Module Chassis Management Module

5. The Problem Operational Costs High operational costs are passed on to the consumer - keep prices low to be competitive High operational costs are passed on to the consumer - keep prices low to be competitive Added hardware and components are costly Want to minimize costs while maintaining functionality Want to minimize costs while maintaining functionality High processing speeds causes increased heat transfer

6. The Proposed Solution Abstract temperature sensing from a management module to a wireless sensor network If this abstraction is successful, can try other areas of abstraction If this abstraction is successful, can try other areas of abstraction A CMM is expensive, and motes are cheap A CMM is expensive, and motes are cheap Costs saved include manufacturing, and space on the system Costs saved include manufacturing, and space on the system

7. Solution (cont) Proposed functionality Sensor nodes will sense the temperatures and compare them to an established threshold Sensor nodes will sense the temperatures and compare them to an established threshold If a sensed temperature is above the threshold, it will send an alert to the base and raise the fan speed on the system If a sensed temperature is above the threshold, it will send an alert to the base and raise the fan speed on the system If a sensed temperature is below, it will send an alert and lower the fan speed If a sensed temperature is below, it will send an alert and lower the fan speed Base station will send requests to set thresholds, and query temperatures Base station will send requests to set thresholds, and query temperatures

8. Prototype Development Develop a prototype of the application with the following structure Base Station Monitored Systems Sensor Node Sensor Node

9. Prototype Development (cont) Features missing from original statement In reality two thresholds are needed In reality two thresholds are needed User commands for setting one node’s threshold, or all nodes’ thresholds User commands for setting one node’s threshold, or all nodes’ thresholds User commands to query one node’s temperature, or all nodes’ temperatures User commands to query one node’s temperature, or all nodes’ temperatures Method by which nodes will raise and lower system fan speeds Method by which nodes will raise and lower system fan speeds

10. Prototype Components A multi-threaded Java-based user program on the base station that sends queries, receives responses and alerts A NesC module for all sensor nodes that receive queries, take periodic temperatures and send commands to the systems being monitored via RPC calls An RPC server that will take incoming commands to raise and lower fan speeds

11. Prototype Components (cont) RoutingSchedulingAggregationSecurity

12. Summary of Results Wireless Sensor Networks cannot replace the CMM All network functionality already implemented in TCP/IP All network functionality already implemented in TCP/IP Hardware management is still implemented on the actual hardware Hardware management is still implemented on the actual hardware i.e. fan controls High number of components leads to high complexity High number of components leads to high complexity All components are validated Increased complexity means increase possibility of failure Can implement same functionality on CMM without concern of battery power Can implement same functionality on CMM without concern of battery power

13. Comparison of Chassis Management Methods Mica Motes components User interface User interface Protocols ProtocolsAggregationRoutingSecurityT-Mac RPC client/server RPC client/server Hardware controls Hardware controls CMM components Middleware to sit on top of HPI Hardware controls

14. Related Links www.saforum.com http://www.picmg.org/newinitiative.stm http://www.intel.com/technology/atca/prod dev.htm

15. Questions?

16. Backup Information