CS 158A Introduction to Computer
Project 2 –
SIMULATION and PERFORMANCE EVALUATION OF
A
IEEE 802 MEDIUM ACCESS CONTROL (MAC) PROTOCOLS
(Last Update: 3/6/2008)
1. Group
Form a group of 2-4 members and elect a coordinator.
2. Objective
Write a to simulate the behavior of
a. A LAN Medium Access Control (MAC) protocol – IEEE 802.3, 802.5, 802.11, 802.15.1, 802.16, 802.17, etc.
b. Its support of both asynchronous data traffic and synchronous, multimedia (including voice and video) traffic.
Compare their performance in terms of delay, delay jitter, and throughput under various traffic loads.
3. Project
Description
Following is a description of network parameters (a-c) and performance criteria (d-e):
a. Traffic Types - For simplicity you may consider two (or more) of the following traffic types: Synchronous class (video and voice) and asynchronous class (data files and images). At least one traffic type should be chosen from each class.
b. Arrival Process - Assume constant bit rate at 1.5 M bps for video, 64 Kbps for voice, and Poisson process for data files. Choose your arrival rate and message length properly. Message length should follow exponential distribution with a proper choice of mean value.
c. Network Description - The transmission rate (or data rate), network length, station number, propagation rate, etc., should all be taken according to the (or at least close to) standard, practical values for your chosen MAC protocol. You may use other additional values on the final report.
d. Average Delay - Measure the mean and variance of packet delay, which is measured from the time that a packet arrives the interface and ready to be transmitted until the time it has been successfully transmitted, versus the input traffic load (the arriving traffic load, in terms of bits/sec).
e. Throughput - Measure the throughput (average network traffic successfully transmitted, in terms of bits/sec), versus the input traffic load (the arriving traffic load, in terms of bits/sec).
4. References
a.
The set of handout on simulation (to be
provided).
b.
IEEE 802 standards or drafts.
c.
Textbook by Peterson and
d.
Loads of information available on the Internet!
5. Deadlines
a. Project Distribution: 3/6.
b. Group Formed: 3/11. Turn in one-page, typed report including the coordinator’s name, group members including phone number and email address of every member.
c. Proposal: 3/18. Survey the literature. Submit a typed proposal including description of 1) The choice of the simulating protocol, especially its MAC protocol, computer language, platform, etc. 2) the high-level description (pseudo code OK) of the simulation algorithm, 3) the mathematical formulae for the arrival process, input traffic load, average packet delay, delay variance, and throughput, and 4) list of references.
d. First Draft: 4/3. Be able to vary input network traffic load, and measure one performance criterion (delay or throughput), supporting one type of traffic, one network topology, one transmission rate. Submit a typed report, extended from the Proposal, with detailed description of 1) the MAC protocol, 2) the parameters chosen, 3) the simulation setting, 4) one figure (table/curve/histogram/etc.) to show the performance, 5) discussion of the simulation result, and 6) list of references.
e. Final Report and Demonstration: 4/17. Be able to measure all three performance criteria of the MAC protocol. You should vary input traffic type (asynchronous and synchronous) and input traffic load. In addition, you may vary network topology and traffic pattern, and compare the performance of different settings. Submit a final report, extended from the First Draft, including 1) detailed description of the project: the WLAN MAC protocol, parameters, input traffic type, input traffic load, etc., 2) all the different simulation settings, the associated performance measurements in terms of tables and/or figures, and a careful discussion of each of the results, 3) list of references, and 4) a hard copy of your program listing, and 5) a CD ROM containing the report, source code, binary code, and a Readme file on how to run your program. An in-class demo is required.