Introduction continued

Transcription

1 Acknowledgments Design and Evaluation of Power Management Support for s Jakob Klamra and Martin Olsson Department of Communication Systems Lund Institute of Technology Lund, SWEDEN Thanks to: Dr. Christensen, USF Dr. Nyberg, LTH Dr. Labrador and Dr. Rundus, USF Bruce Nordman, LBNL Chamara Gunaratne, USF 1 Masters Defense June 7, 2005 (Tampa, Florida) 2 Topics Introduction Analysis Design Implementation Validation Energy Savings Estimate Introduction Problem: increased energy use by IT equipment More devices in US households IT equipment use 280 kwh/year per US household Adds up to $ 2240 million Problem: IT equipment always on, even when idle Required by some protocols Universal Plug and Play (UPnP) has this problem Our work solves the problem for UPnP Investigate the use of a power management proxy Conclusions and Future Work 3 4 1

2 Introduction continued UPnP is for automatic device configuration Network analogy of Microsoft plug-and-play Control points and services Discovery, eventing and control Introduction continued SSDP message exchange Discovery SSDP:discover Answered by Standardized by UPnP Forum More than 700 vendors, Microsoft, Intel, Nokia UPnP uses Simple Discovery Protocol SSDP is the key issue Control Point SSDP:discover SSDP:discover SSDP:discover 5 6 Introduction continued SSDP message exchange (continued) Notification Sent out periodically Introduction continued UPnP foundation, the stack SSDP use UDP UPnP Vendor Specific UPnP Forum Specific Architecture Eventing and control use TCP Our work is done here Control Point HTTP-MU SSDP UDP HTTP-U SSDP HTTP GENA TCP SOAP GENA 7 8 IP 2

3 Analysis Requirements for power management solutions: R1 Enable UPnP devices to enter power sleep R2 - Not interfere with existing UPnP functionality Analysis continued New Low power proxy Acts (answers and speaks) for sleeping devices Wakes up sleeping devices when they are needed R3 - Be robust R4 - Work for wired and wireless R5 - Handle many devices R6 - Be possible for us to implement Control Point 4. powered up 1. in power sleep 2. Request for service 3. Wake up SLEEP 9 10 Analysis continued Possible solutions to UPnP power management Three categories: Centralized proxy, no change to devices Invisible proxy Centralized proxy, minor change to devices Cooperating proxy No proxy, major change to devices ing NICs Design Selection of the solutions All requirements must be fulfilled Desirable properties As much power sleep as possible As little configuration as possible As little changes to UPnP protocol as possible Our design decision Invisible proxy Cooperating proxy

4 Design continued Design of invisible proxy 1. Timeout start proxy 6. Forward TCP SYN 2.SSDP:discover ST = Printer 4.TCP SYN 3. (Spoofed) ST=Printer 5.Wake On Lan ACK 7.TCP SYN SLEEP Control point Design continued Invisible proxy FSM LISTENING P1 P12 Timeout PROXY DEVICE P2 P23 SSDP:discover P32b S in proxy cache Discovery answer P24 TCP from CP WAIT FOR ALIVE P5 P45 S in proxy cache WOL to S P51a from S P55 Timeout Forward packet from CP CHECK PROXY CACHE DISCOVERY P3 CHECK PROXY CACHE TCP P CP = Control point, S =, WOL = Wake On Lan 15 Design continued Design of cooperating proxy 3.SSDP:discover ST = Printer 4. (Spoofed) ST=Printer 5.TCP SYN 1.GENA Powermgmt = SLEEP 2. 6.Wake On Lan 7.GENA Powermgmt = POWER 8.Forward TCP SYN SLEEP Control point 9.TCP SYN ACK 16 Design continued Cooperating proxy FSM LISTENING P1 P12 GENA, Power mgmt=sleep P51a GENA, Power mgmt=power Forward packet from CP PROXY DEVICE P2 P51a GENA Power mgmt=power, Forward packet from CP P23 SSDP:discover CHECK PROXY CACHE DISCOVERY P3 P32a S in proxy cache Discovery answer CHECK PROXY CACHE TCP P4 P24 TCP from CP FORWARD PACKET P5 CP = Control point, S =, WOL = Wake On Lan P45 S in proxy cache WOL to S 4

5 Implementation Development Tools Programming environment Dev-C++ Packet handling routines NETWIB libraries Packet capture and decoding Ethereal UPnP device toolkit Intel software for UPnP technologies Implementation continued Data structure for proxies Device Cache All devices on the network Cache All devices proxy is answering for Implementation continued Implementation continued Name Description Implementation of invisible proxy Main thread ip eth IP address Ethernet address Discover devices and build cache Start threads Notification 19 service server location last_activity All services of the device Server name Location Time for last activity from the device 20 Main loop Sniff packets Process packets Send answer and update caches cache update Check devices in Device Cache Update Cache Check Cache If needed send 5

6 Implementation continued Validation Implementation of cooperating proxy Main Thread Discover power management services and build cache Start threads Main loop Sniff packets Process packets Cache update Check Device cache Notification Check cache Read event socket Read and parse incoming events Update cache Validation design and implementation must meet requirements Known shortcomings TCP forwarding not implemented Cannot detect crashed devices Test cases 7 tests for each solution 3 tests not executed because lack of equipment 21 Answer and update caches Update Device cache Send 22 Validation continued Energy saving estimation Validation of invisible proxy 1 test passed 3 partially failed No unexpected behavior Estimates made for US residential IT equipment Estimates made for: Stock, power consumption, usage patterns Validation of cooperating proxy 2 tests passed 2 partially failed No unexpected behavior Calculations made for: Total energy and economic savings in 2008 Estimates from work by Energy Analysis Program at Lawrence Berkley National Laboratory Bruce Nordman

7 Energy saving estimation continued Background, stocks Energy saving estimation continued Results Device Devices 2001 Devices 2008 Network Connected devices 2008 Savings in GWh/year Savings in million dollars per year Notebooks Low estimation Desktops % Inkjets High estimation Laser printers % (all figures are in million) (8 cents/kwh) Conclusions and future work Conclusions and future work continued Conclusions Power management in UPnP achieved Proved by implementation and validation $71 - $285 million saved in American households using UPnP by 2008 Shortcomings of the design Long response time TCP connection between service and control point not established 27 Contributions First to design and implement power management proxy for UPnP Energy savings estimate motivates our work Member and contributors to UPnP Forum UPnP power management problem solved 28 can crash Lost information about sleeping devices not discoverable Need to support several medium UPnP is media independent 7

8 Conclusion and future work continued Future work UPnP power management standard Smart NIC NIC with proxy capability Distributed solution Extended proxy functionality Automatic configuration of power management Routing of services References In order of importance: [20] M. Jeronimo and J. Weast, UPnP Design by Example, Volume 1, April 2003 [26] B. Nordman and A. Meier, Energy Consumption of Home Information Technology, July 2004 [2] Y. Y. Goland, T. Cai, P. Leach and Y. Gu, Simple Discovery Protocol/1.0 Operating without an Arbiter, draft-cai-ssdp-v1-03.txt, IETF draft, October 1999 [5] UPnP Forum, May 2005 [27] K. Christensen, B. Nordman and A. George, The Next Frontier for Communications Networks: Power Management, Computer Communications, Volume 27, Number 18, pages , December 2004 [3] D. Box, G. Kakivaya, A. Layman, S. Thatte and D. Winer, SOAP: Simple Object Access Protocol, draft-box-http-soap-01.txt, IETF draft, November 1999 [4] J. Cohen, S. Aggarwal and Y. Y. Goland, General Event Notification Architecture Base: Client to Arbiter, draft-cohen-gena-p-base-01.txt, IETF draft, September Jakob Klamra Thank you Martin Olsson Project homepage: