1. WAVE without beacons Date: 2007-05-14 Authors: May 2007 Month Year
doc.: IEEE yy/xxxxr0
May 2007
WAVE without beacons
Date:
Authors:
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 < ieee802.org/guides/bylaws/sb-bylaws.pdf>, 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
R. Roy / SRA

2. Month Year
doc.: IEEE yy/xxxxr0
May 2007
Abstract
This presentation contains a proposal for a new approach to WAVE that does not require changing or using beacons.
R. Roy / SRA

3. Design Principles We are designing a communication system for WAVE
Month Year
doc.: IEEE yy/xxxxr0
May 2007
Design Principles
We are designing a communication system for WAVE
In WAVE environments, there is insufficient time for the standard BSS establishment process – WAVE requires an immediate communications establishment that is not supported by traditional beaconing, authentication and association mechanisms
While ITS systems based on WAVE are not expected to use traditional beacons, there is no reason to obviate the standard BSS/IBSS features as they may prove useful.
Facilities for higher layer synchronization must be included to provide maximum flexibility in PHY channelization configurations for supporting multiple regulatory domains
R. Roy / SRA

4. Basic Approach Dictated by Principles
Month Year
doc.: IEEE yy/xxxxr0
May 2007
Basic Approach Dictated by Principles
Leave current beaconing and joining mechanisms untouched - remove any and all mention of WBSSs, etc. and limit WAVE changes to requiring data communications in the absence of beaconing, authentication and association.
Add two new frames “arbitrarily” named:
WAVE data frame (Type: 11 Subtype: 0000)
WAVE management frame (Type: 11 Subtype 0001)
WAVE management frames that include a timestamp will have the same requirement on the timestamp as the standard frames that are used for synchronization.
MAC header is the same as for current management frames
Allows inclusion of standard information elements
WSI can be moved to a data frame (higher layer frame)
WSI is optional in a management frame
STAs for which dot11WAVEServicesImplemented is true will process both types of frames.
R. Roy / SRA

5. Basic Approach Dictated by Principles
Month Year
doc.: IEEE yy/xxxxr0
May 2007
Basic Approach Dictated by Principles
WAVE Management frame allows inclusion of existing information elements that support operation in multiple regulatory domains
Need to harmonize with CALM TC204
Increase the number of regulatory classes to include various possible (frequency) channelization schemes
Details to be worked out
R. Roy / SRA

6. Basic Approach Dictated by Principles
Month Year
doc.: IEEE yy/xxxxr0
May 2007
Basic Approach Dictated by Principles
Regulatory
Class
Channel
Starting
Frequency
(GHz) BW
(MHz)
Channel set
Transmit
Power limit
(mW)
Emissions
Limits set
Behavior
<ANA>
5.000 40
174 – 181 30
173 – 182 20
172 – 183 10
xxx-255
Reserved
R. Roy / SRA