# |
Criterion |
Discussion |
1 |
Meets system requirements |
How well does the proposed MAC protocol meet the requirements described in the current version of the 802.16 System Requirements ( Document IEEE 802.16s0-99/n)? |
2 |
MAC Delays |
Is it possible to bound the delay of the proposed MAC protocol? |
3 |
Payload and bandwidth efficiency |
How well does the overhead due to the proposed MAC PDU headers allow for efficient user data transfer over the 802.16 air interface? Is the proposed MAC protocol designed such that the MAC signaling is efficient in terms of not requiring excessive overhead? How well does the proposed MAC protocol provide the mechanisms for fair allocation and sharing of the bandwidth among users? |
4 |
Simplicity of implementation/cost |
How well does the proposed MAC protocol allow for an implementation that is simple and generic enough that it is likely to be accepted by industry? |
5 |
Scalability |
Does the MAC protocol support a broad range of operational bandwidths and number of connections? |
6 |
Service Support Flexibility |
Does the MAC protocol support the services mentioned in the 802.16 System Requirements (Document IEEE 802.16s0-99/n) and is it open to the possible support of other services? |
7 |
Robustness |
Can the MAC protocol continue normal operation when presented with various unexpected events, e.g., corrupted MAC header, undefined MAC message (other protocol)? Is the MAC protocol able to recover from events such unexpected shut down or loss of link? |
8 |
Security |
How well does the MAC protocol provide security mechanisms to meet the System Requirements? |
9 |
Physical Channel Configurability |
Does the MAC protocol provide mechanisms to control the PHY parameters? |
10 |
Maturity |
Does the proposed MAC protocol have data to demonstrate its ability to operate in an actual system that is representative of the BWA networks target for 802.16? |
11 |
Convergence with existing technologies |
How simple is it to adapt the proposed MAC protocol to existing technologies? |
12 |
Ability to work with physical layer variations, e.g., duplexing, constellation |
How independent is the proposed MAC protocol of the PHY protocol? |
13 |
Mean access delay and variance |
No submission required for Session #4; will address later |
14 |
Sign-on process |
No submission required for Session #4; will address later |
15 |
Verifiability |
No submission required for Session #4; will address later |
16 |
Adequacy of management functions |
No submission required for Session #4; may address later |
Download the PDF version of this Call for Contributions