Course Project


The objective of this course project is allow students to have an in-depth understanding and more visible experience (via either simulations or hands-on experiments) with one of the topics covered in this class. There are five suggested projects and you can choose any one of them in the capacity of equipment. All these projects require a fair amount of work (read "lots of work").

How to start?

  1. Read the section of suggested projects and this is the individual project.Everyone is expected to domenstrate his/her own independing thinking and solving problems' capability.
  2. Send your project topic to the TA by April 2th.
  3. Submit a two-page progress report from each one to the Dr. Wang every Monday. In this report, list and explain what you have done in the past week, are the risks/threats to the project (i.e. what might go wrong), and what you are going to do in the next week. The team leader does not need to be the one to write the progress report (he/she might assign it to a team member), but the team leader is the one to take the blame (and a one point penalty) if it is not submitted on time.

Deliverables and grading

At the end of the project it is expected that the students will make a practical demonstration and oral presentation, will turn in their properly commented code, and a written report both soft copy and hard copy. All the reports, demos, score sheets must be turned in no later than 5:00pm, June 19, 2016.

Project report: Each team is expected up up to 20-page, that includes the description of project, objectives, practical problems and solutions, software and hardware, results, explanations, conclusions, and references. The commented source code, specifications of software and hardware, and references are excluded in the report, but they are submitted as appendix.

Presentation and peer review: For demos and presentation, everyone is encouraged to participate, discuss, and score a peer review report. The participation and your comments count 5%. All arrangement will be posted on the Announcement page. Presentations will be scheduled on the due day of the project for peer review. Each group will have a 15-minute slot for presenting your project features and strength. 3 minutes will be remained for Q&A.

Grading: The projects from each person will be graded.

Check equipment out

Except for simulation-based projects, hardware are needed for hands-on projects. We have a common list of resources that we can use for this lab. Each student will be able to check in and out different resources (e.g. iPAQ, notebook, GPS receivers, trucks, wireless cards, etc.) from the TA. If one resource is in short supply, the resource will have to be time-shared (e.g. returned after one week).

Anything you break you have to replace. For example a screen replacement for the iPAQs is around 2000RMB.

Anytime you check something out (from the TA.) you'll have to do the following two things:

Suggested Projects

  1. Acemap: topic analysis
  2. Resource Allocation for Selfish Network for Non-cooperatavie Networks
  3. Bluetooth for Ad-Hoc Networking
  4. App development of Wearable Computing
  5. Bluetooth Cochlear
  6. crowdsourcing incentive design in fingerprints based localization
  7. Indoor LocalizationNetwork functions virtualization (NFV)
  8. Admission Control in Cooporative Systems:Cellular + WiFi + WiMax :
  9. Recommendation in Scholarly Big Data
  10. Intelligent Handoff in Mobile IP Networks
  11. Geocasting Protocol for Mobile Adhoc Networks
  12. Comparison of Routing Protocols for Mobile Adhoc Networks
  13. Energy issues in wireless networking
  14. Voice over Adhoc Networks
  15. QoS in Wireless LANs,e.g. VoIP
  16. New MAC for Sensor Networks
  17. Transport Layer Protocol for Sensor Networks:
  18. Routing in Sensor Networks:
  19. Distributed Resource Allocation for Hybrid Networks