doc.: IEEE /388r0 Submission March 2004 Michael Paljug, ConexantSlide 1 Introduction and Call for Interest in Standardizing Wake On Wireless LAN Michael Paljug Conexant

doc.: IEEE /388r0 Submission March 2004 Michael Paljug, ConexantSlide 2 Why Wake On LAN? Allows an authorized agent to transition a Host machine (or group of Host machines) from a low power state to a fully operational state

doc.: IEEE /388r0 Submission March 2004 Michael Paljug, ConexantSlide 3 Why Do We Need Wake On Wireless LAN (WOWL)? Wake On LAN already widely deployed and commonly available Offers these features: –Remote administration –Scheduled IT maintenance –Remote troubleshooting

doc.: IEEE /388r0 Submission March 2004 Michael Paljug, ConexantSlide 4 Why Standardize WOWL? Common customer requirement Ambiguous specifications Differences in implementations Security

doc.: IEEE /388r0 Submission March 2004 Michael Paljug, ConexantSlide 5 WOWL Interfaces Different Interfaces have unique characteristics pertaining to power, signaling, device states, etc. –Cardbus –USB –PCI/Mini-PCI/PCI Express –Etc.

doc.: IEEE /388r0 Submission March 2004 Michael Paljug, ConexantSlide 6 Example: MiniPCI 3VAUX – Alternate source of power –Only available source of power in device state D3cold –Standby power is limited (200 mA); radio must maintain operational state PME# - Signal for waking Host system

doc.: IEEE /388r0 Submission March 2004 Michael Paljug, ConexantSlide 7 WOL (Wired) – Wake Events Any one of these events will wake the system: –Detection of a change in the network link state i.e. Ethernet cable insertion –Receipt of a network wake-up frame –Receipt of a Magic™ packet

doc.: IEEE /388r0 Submission March 2004 Michael Paljug, ConexantSlide 8 (Wired) Network Wake-Up Frames NetBIOS broadcast queries –NetBIOS over TCP/IP broadcast for station's assigned computername (frames with DIX header) Hardware address resolution –address resolution protocol (ARP) broadcast for station IP address (frames with DIX header) Unicast –Directed Layer Two packet

doc.: IEEE /388r0 Submission March 2004 Michael Paljug, ConexantSlide 9 Processing Network Wake-Up Frames 1.Host determines NIC capabilities through query at system initialization 2.Host downloads pattern(s) to match –Pattern(s) matching is limited to first 128 bytes of frame 3.Host system transitions adapter to low power state

doc.: IEEE /388r0 Submission March 2004 Michael Paljug, ConexantSlide 10 Magic™ Packet Packet that contains 16 contiguous copies of the receiving NIC's Ethernet address May be B-Cast, M-Cast or unicast Multiple NICs may be addressed in single packet, so a particular NIC’s pattern may appear anywhere within the Magic Packet™ –Magic™ Packet may be as large as maximum packet size for given network medium

doc.: IEEE /388r0 Submission March 2004 Michael Paljug, ConexantSlide 11 Conclusions Provides an important method for remote administration Specifications are ambiguous for Wireless LAN devices Standardization needed for interoperability and to enable network administration for wireless NICs at the same level as wired NICs

doc.: IEEE /388r0 Submission March 2004 Michael Paljug, ConexantSlide 12 Next Steps Is there any interest in standardizing WOWL? Is a study group warranted? –Is this covered by the scope of an existing Task or Study Group?