Introduction and Call for Interest in Standardizing Wake On Wireless

Download Report

Transcript Introduction and Call for Interest in Standardizing Wake On Wireless

March 2004
doc.: IEEE 802.11-04/388r0
Introduction and Call for Interest
in Standardizing Wake On
Wireless LAN
Michael Paljug
Conexant
Submission
Slide 1
Michael Paljug, Conexant
March 2004
doc.: IEEE 802.11-04/388r0
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
Submission
Slide 2
Michael Paljug, Conexant
March 2004
doc.: IEEE 802.11-04/388r0
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
Submission
Slide 3
Michael Paljug, Conexant
March 2004
doc.: IEEE 802.11-04/388r0
Why Standardize WOWL?
•
•
•
•
Common customer requirement
Ambiguous specifications
Differences in implementations
Security
Submission
Slide 4
Michael Paljug, Conexant
March 2004
doc.: IEEE 802.11-04/388r0
WOWL Interfaces
• Different Interfaces have unique
characteristics pertaining to power,
signaling, device states, etc.
–
–
–
–
Submission
Cardbus
USB
PCI/Mini-PCI/PCI Express
Etc.
Slide 5
Michael Paljug, Conexant
March 2004
doc.: IEEE 802.11-04/388r0
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
Submission
Slide 6
Michael Paljug, Conexant
March 2004
doc.: IEEE 802.11-04/388r0
WOL (Wired) – Wake Events
•
Any one of these events will wake the
system:
–
Detection of a change in the network link
state
•
–
–
Submission
i.e. Ethernet cable insertion
Receipt of a network wake-up frame
Receipt of a Magic™ packet
Slide 7
Michael Paljug, Conexant
March 2004
doc.: IEEE 802.11-04/388r0
(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
Submission
Slide 8
Michael Paljug, Conexant
March 2004
doc.: IEEE 802.11-04/388r0
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
Submission
Slide 9
Michael Paljug, Conexant
March 2004
doc.: IEEE 802.11-04/388r0
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
Submission
Slide 10
Michael Paljug, Conexant
March 2004
doc.: IEEE 802.11-04/388r0
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
Submission
Slide 11
Michael Paljug, Conexant
March 2004
doc.: IEEE 802.11-04/388r0
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?
Submission
Slide 12
Michael Paljug, Conexant