1. Submission Title: IEEE802.15.3: Management Slots in the 802.15.3 MAC.
<October 2001>
doc.: IEEE <01/472>
<October 2001>
Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs)
Submission Title: IEEE : Management Slots in the MAC.
Date Submitted: 19 September, 2001
Source: Dr. William Shvodian Company: XtremeSpectrum
Address: 8133 Leesburg Pike, Suite 700, Vienna, Virginia 22182
Voice: , FAX: ,
Re: []
Abstract: This proposal describes the use of Management Slots for the MAC.
Purpose: To provide an improvement to the current version of the MAC
Notice: This document has been prepared to assist the IEEE P 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 acknowledges and accepts that this contribution becomes the property of IEEE and may be made publicly available by P
<William Shvodian>, <XtremeSpectrum>
William Shvodian, XtremeSpectrum

2. <October 2001>
Overview
currently has no restrictions on traffic in the CAP: Data, Commands, EPS
The impact the amount of traffic in the CAP has not been assessed in terms of the size of the CAP, the overhead it will cause and the probability of collision.
Association is the only type of frame that absolutely needs to be in the CAP.
<William Shvodian>, <XtremeSpectrum>

3. <October 2001>
Overview
Getting Management traffic out of the CAP can reduce the size of the CAP
This proposal shows a straightforward way to reduce the amount of traffic in the CAP by putting management/command frames into Management GTS slots
<William Shvodian>, <XtremeSpectrum>

4. New Information Element in the Beacon
<October 2001>
New Information Element in the Beacon
CAP Control Mode Information Element
Data in the CAP (allowed/not allowed)
EPS in CAP (allowed/not allowed)
Commands in the CAP (allowed/not allowed) Note: Association is ALWAYS allowed in the CAP
<William Shvodian>, <XtremeSpectrum>

5. CAP Control Mode Information Element
<October 2001>
CAP Control Mode Information Element
1 octet
1 octet
1 bit
1 bit
1 bit
13 bits
Element ID
Length
Data
in CAP
Commands
In CAP
EPS
In CAP
Reserved
CAP Control Mode Information Element sent in Beacon if Data, Commands or EPS frames are not allowed in the CAP.
Default is that Data, Commands and EPS are allowed in CAP
PNC can minimize the needed CAP size by disallowing Data and Commands in the CAP
Also, Disallowing Data and commands in the CAP allows stations to not listen to the CAP
<William Shvodian>, <XtremeSpectrum>

6. Commands in Management Slots
<October 2001>
Commands in Management Slots
If Commands are not allowed in CAP, they are sent in Management Slots
The PNC allocates one or more GTS slots as Management Slots. Management slots are simply GTS slots, where the PNC address (zero) is either the SA or the DA.
The PNC can change the assigned station for management slots in any beacon.
<William Shvodian>, <XtremeSpectrum>

7. Management Slot Options
<October 2001>
Management Slot Options
Contention
Access
Period
Contention Free Period
Beacon 1 2 3 4 5
A single management slot can be used where the SA can be assigned to different DEVs, including PNC, each superframe. The DA will be the PNC DA except when PNC address is the SA
Contention
Access
Period
Contention Free Period
Beacon 1 2 3 4 5 6
Slot 1 can be assigned to DEV SAs with PNC DA for DEV to PNC commands, with Slot 2 assigned to PNC SA with DEV DAs for PNC to DEV commands
Contention
Access
Period
Contention Free Period
Beacon 1 2 3 4 5 6 7 8 9
PNC may allocate multiple management GTS slots for commands
<William Shvodian>, <XtremeSpectrum>

8. <October 2001>
Summary
New CAP Control Mode Information Element in the Beacon to control the type of frames allowed in the CAP.
If the PNC disallows command frames in the CAP, management GTS slots are used to transmit command frames
<William Shvodian>, <XtremeSpectrum>