doc.: IEEE /0260r1 Submission March 2007 Emily Qi (Intel Corp) et alSlide 1 Wake-on WLAN Notice: This document has been prepared to assist IEEE It is offered as a basis for discussion and is not binding on the contributing individual(s) or organization(s). The material in this document is subject to change in form and content after further study. The contributor(s) reserve(s) the right to add, amend or withdraw material contained herein. Release: The contributor grants a free, irrevocable license to the IEEE to incorporate material contained in this contribution, and any modifications thereof, in the creation of an IEEE Standards publication; to copyright in the IEEE’s name any IEEE Standards publication even though it may include portions of this contribution; and at the IEEE’s sole discretion to permit others to reproduce in whole or in part the resulting IEEE Standards publication. The contributor also acknowledges and accepts that this contribution may be made public by IEEE Patent Policy and Procedures: The contributor is familiar with the IEEE 802 Patent Policy and Procedures, including the statement "IEEE standards may include the known use of patent(s), including patent applications, provided the IEEE receives assurance from the patent holder or applicant with respect to patents essential for compliance with both mandatory and optional portions of the standard." Early disclosure to the Working Group of patent information that might be relevant to the standard is essential to reduce the possibility for delays in the development process and increase the likelihood that the draft publication will be approved for publication. Please notify the Chair as early as possible, in written or electronic form, if patented technology (or technology under patent application) might be incorporated into a draft standard being developed within the IEEE Working Group. If you have questions, contact the IEEE Patent Committee Administrator at. ieee802.org/guides/bylaws/sb-bylaws.pdf Date: Authors:

doc.: IEEE /0260r1 Submission March 2007 Emily Qi (Intel Corp) et alSlide 2 Abstract This presentation describes use cases and requirements for Wake-on WLAN.

doc.: IEEE /0260r1 Submission March 2007 Emily Qi (Intel Corp) et alSlide 3 Objectives Enable an IEEE standards-based Wake-on WLAN Solution to provide power savings for WLAN devices, in the following use cases: –IT night-time updates –Remote Access to corporate computers while working from home, or remote access to home computer from work without having computer on all time –Initiate video streaming to idle multimedia server (home networking) –Deliver SIP calls and instant messages to roaming devices

doc.: IEEE /0260r1 Submission March 2007 Emily Qi (Intel Corp) et alSlide 4 Motivation: An Example Today’s PC Device Power States –Awake State Host system is fully powered up and in operation mode WNIC is powered on –Sleep States All power to the CPU in the host system is shut off, and suspended to disk/RAM WNIC is powered off Goal: Provide ability for the network to reach the client while saving power Awake State Power is 7, 25, or 55 times the Sleep State Power. Issues: –Devices are either in sleep state without network connectivity, or –In awake states all the time, ready to receive packets from the network

doc.: IEEE /0260r1 Submission March 2007 Emily Qi (Intel Corp) et alSlide 5 Wake-on-LAN Mechanism Wake-on-LAN enables host system in Sleep States and switches to Awake State only when receiving the desired packet patterns A “Proprietary” Wake-on-LAN mechanism: –The OS or application sets wake patterns or a magic packet in a NIC through standard MSFT OIDs. –Then while the system is in sleep state (S3 system, D3 NIC), –The NIC receives packets, attempts to match the pattern stored in the NIC to sequential bytes. –The NIC wakes the system, if a pattern match is found. –What are the Wake-on WLAN requirements?

doc.: IEEE /0260r1 Submission March 2007 Emily Qi (Intel Corp) et alSlide 6 Wake-on WLAN Requirements Network must be aware that a client is in reduced- power consumption state – idle or standby The network must be able to reach the client while the client is in the reduced-power consumption state The network must be able to wake up the client The client must be able to wake up The client must be able to retrieve pending frames, if any

doc.: IEEE /0260r1 Submission March 2007 Emily Qi (Intel Corp) et alSlide 7 IEEE status Current standard is inadequate –No support for arbitrarily long sleep periods –An unassociated STA cannot be reached by the network –Association may be lost while system is sleeping Straw Poll: Should TGV solve this problem? Yes No Abstain