CMPE 257 Reading List

Project Guidelines

These guidelines will be strictly enforced. Please make sure that you read the guidelines and follow them. Everyone should have accounts on sanskriti. Those who do not have accounts or have trouble logging in mail me asap since all demos will be conducted on sanskriti (even windows users). After you have finished your implementation you will have to transfer all your files to your respective accounts and check to see that your code compiles and executes on the class server. if you have problems compiling your code on the server, mail me and i'll try to fix it. 10% of your project grade will be assigned to correct compilation and execution of your code on the server.

General guidelines: Students will need to include trace comments in their implementation code which has to be written to a file called trace.out. This is the only way for us to figure out that your implemention is working without looking through the code. The more verbose the comments the better. You could also assign various debugging levels from the command line. eg. "glomosim -l1 config.in" or "glomosim -l2 config.in" with more information being printed at the higher levels. (However, debugging levels is not a requirement)

The trace comments should have the following format. (Packet type will of course vary depending on the implementation)

# Timestamp Node Id Packet Type Action (Tx/Rx) Destination Node
1.23123 Node (1) Beacon Tx --> Node (5)

1.24567 Node (5) Beacon Rx <-- Node (1)

2.34356 Node (21) RFN Tx --> Node (11)

Project Report: The project report will be formatted similar to most conference style papers. The report will typically be 5-8 pages (11pt font size) including an Abstract, Introduction, Methodology (details about your implementaion/modifications), Simulation setup, Results and finally Analysis/Conclusions. Accepted formats are pdf, ps and doc files. if you are using doc files do not embed excel charts in the document. Convert the charts to bmp or jpeg and paste them into the word document.

In terms of the demo you can design your experiments however you want. However, we will change some parameters in the config file to test (not stress) your implementation.

Below are some comments specific to the projects.

1. MAC

For this project, students will implement 802.11's PCF (Point Coordination Function).

Your experiment setup will typically consist of 20 nodes and one access point that functions as the PC. Ensure that you do not hard code any node as the PC. It should be set from the config file. eg "Node[1] Acess-Point Yes". Ensure that nodes are setup in the topology such that every node is one hop away from the Access Point (AP) (even when the nodes move). The AP can be assumed to be fixed. You can use static routing and specify the routes in routes.in. For the experiments, you can setup 5-10 ftp sessions between different nodes and generate statistics on the throughput and delay per session and compare these values with DCF for the same node setup and parameters and verify the fairness of the two schemes.

2. Mobility Model

For this project, students will have to look up different mobility models such as group mobility model, pursue model, etc. The project consists of implementing a new mobility model not included in GloMoSim's default distribution. GloMosim currently has two mobility models: Random Waypoint and Pathloss Matrix.

Your experiment setup will typically consist of 50-75 nodes in a 1500x1500 m2 field. You can use any unicast routing protocol (dsr/aodv) and setup cbr/ftp traffic between 10 nodes in the network. You will use the implemented mobility model and vary mobility from (0 -15 m/s) in steps of 3 and compare the PDR/throughput/delay with glomosims random waypoint model (same speeds).
In your report you will have to justify (qualitatively) scenarios where the implemented mobility models will be most suited.

3. TCP-F for Wireless Networks

For this project, students will compare the performance of TCP-F (feedback) with regular TCP over wireless links.

Your experiment setup will typically consist of 50 nodes in a 1500x1500 m2 field. You can use any unicast routing protocol (dsr/aodv) and setup cbr/ftp traffic between 10 different nodes in the network. Node mobility will vary from 0 -15 m/s in steps of 3. For the same setup, you will compare the PDR/throughput/delay of the different sessions using TCP-F, regular TCP and UDP as the transport protocol.

4. Multipath Routing

This project will involve extending either DSR or AODV to do multipath routing. DSR and AODV are on-demand protocols in which routes are established by a Route-Discovery phase. The Route Discovery process involves flooding Route-Requests and receiving Route-Replies. In the normal version only the best route is chosen from the different Route-Replies received, based on the shortest route or the route with the latest sequence number.

In the extended version, students will have to modify the routing protocol to maintain the two best routes to destinations instead of one. Both routes will have to be used for subsequent data transmissions. To decide which route to use for transmitting data, you can use a simple probabilistic method or plain round-robin.

Your experiment setup will typically consist of 50-75 nodes in a 1500x1500 m2 field. You can use any unicast routing protocol (dsr/aodv) and setup cbr/ftp traffic between 10 different nodes in the network. Node mobility will vary from 0 -15 m/s in steps of 3. For the same setup, you will compare the PDR/throughput/delay of the different sessions for multipath routing and unipath routing.

Project Guidelines
	These guidelines will be strictly enforced. Please make sure that you read the guidelines and follow them. Everyone should have accounts on sanskriti. Those who do not have accounts or have trouble logging in mail me asap since all demos will be conducted on sanskriti (even windows users). After you have finished your implementation you will have to transfer all your files to your respective accounts and check to see that your code compiles and executes on the class server. if you have problems compiling your code on the server, mail me and i'll try to fix it. 10% of your project grade will be assigned to correct compilation and execution of your code on the server. General guidelines: Students will need to include trace comments in their implementation code which has to be written to a file called trace.out. This is the only way for us to figure out that your implemention is working without looking through the code. The more verbose the comments the better. You could also assign various debugging levels from the command line. eg. "glomosim -l1 config.in" or "glomosim -l2 config.in" with more information being printed at the higher levels. (However, debugging levels is not a requirement) The trace comments should have the following format. (Packet type will of course vary depending on the implementation) # Timestamp Node Id Packet Type Action (Tx/Rx) Destination Node 1.23123 Node (1) Beacon Tx --> Node (5) 1.24567 Node (5) Beacon Rx <-- Node (1) 2.34356 Node (21) RFN Tx --> Node (11) Project Report: The project report will be formatted similar to most conference style papers. The report will typically be 5-8 pages (11pt font size) including an Abstract, Introduction, Methodology (details about your implementaion/modifications), Simulation setup, Results and finally Analysis/Conclusions. Accepted formats are pdf, ps and doc files. if you are using doc files do not embed excel charts in the document. Convert the charts to bmp or jpeg and paste them into the word document. In terms of the demo you can design your experiments however you want. However, we will change some parameters in the config file to test (not stress) your implementation. Below are some comments specific to the projects.
	1. MAC For this project, students will implement 802.11's PCF (Point Coordination Function). Your experiment setup will typically consist of 20 nodes and one access point that functions as the PC. Ensure that you do not hard code any node as the PC. It should be set from the config file. eg "Node[1] Acess-Point Yes". Ensure that nodes are setup in the topology such that every node is one hop away from the Access Point (AP) (even when the nodes move). The AP can be assumed to be fixed. You can use static routing and specify the routes in routes.in. For the experiments, you can setup 5-10 ftp sessions between different nodes and generate statistics on the throughput and delay per session and compare these values with DCF for the same node setup and parameters and verify the fairness of the two schemes.
	2. Mobility Model For this project, students will have to look up different mobility models such as group mobility model, pursue model, etc. The project consists of implementing a new mobility model not included in GloMoSim's default distribution. GloMosim currently has two mobility models: Random Waypoint and Pathloss Matrix. Your experiment setup will typically consist of 50-75 nodes in a 1500x1500 m2 field. You can use any unicast routing protocol (dsr/aodv) and setup cbr/ftp traffic between 10 nodes in the network. You will use the implemented mobility model and vary mobility from (0 -15 m/s) in steps of 3 and compare the PDR/throughput/delay with glomosims random waypoint model (same speeds). In your report you will have to justify (qualitatively) scenarios where the implemented mobility models will be most suited.
	3. TCP-F for Wireless Networks For this project, students will compare the performance of TCP-F (feedback) with regular TCP over wireless links. Your experiment setup will typically consist of 50 nodes in a 1500x1500 m2 field. You can use any unicast routing protocol (dsr/aodv) and setup cbr/ftp traffic between 10 different nodes in the network. Node mobility will vary from 0 -15 m/s in steps of 3. For the same setup, you will compare the PDR/throughput/delay of the different sessions using TCP-F, regular TCP and UDP as the transport protocol.
	4. Multipath Routing This project will involve extending either DSR or AODV to do multipath routing. DSR and AODV are on-demand protocols in which routes are established by a Route-Discovery phase. The Route Discovery process involves flooding Route-Requests and receiving Route-Replies. In the normal version only the best route is chosen from the different Route-Replies received, based on the shortest route or the route with the latest sequence number. In the extended version, students will have to modify the routing protocol to maintain the two best routes to destinations instead of one. Both routes will have to be used for subsequent data transmissions. To decide which route to use for transmitting data, you can use a simple probabilistic method or plain round-robin. Your experiment setup will typically consist of 50-75 nodes in a 1500x1500 m2 field. You can use any unicast routing protocol (dsr/aodv) and setup cbr/ftp traffic between 10 different nodes in the network. Node mobility will vary from 0 -15 m/s in steps of 3. For the same setup, you will compare the PDR/throughput/delay of the different sessions for multipath routing and unipath routing.

CMPE 257 : Wireless & Mobile Networking
Spring 2003