1 / 26

Wireless Networking & Mobile Computing CS 752/852 - Spring 2012

Wireless Networking & Mobile Computing CS 752/852 - Spring 2012. Suggested Ideas for Class Project. Tamer Nadeem Dept. of Computer Science. Year 2011Projects. Proj. #1: Evaluation of charging battery electrical vehicles at traffic lights.

nam
Download Presentation

Wireless Networking & Mobile Computing CS 752/852 - Spring 2012

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Wireless Networking & Mobile ComputingCS 752/852 - Spring 2012 Suggested Ideas for Class Project Tamer Nadeem Dept. of Computer Science

  2. Year 2011Projects

  3. Proj. #1: Evaluation of charging battery electrical vehicles at traffic lights • Charging of Vehicle in the intersection through controlling traffic light

  4. Project summary • Investigating • the specifications of battery and charging, discharging models • Charging devices specifications: mats, Plugless power, Online Electric Vehicle, … • intersection delays • Simulation in SUMO + traci • Modules: electrical vehicles and electrical lane • Network of intersection and vehicle movement • control interface in traci for three strategy • No charging, no strategy for charging and charging strategy

  5. Sample Simulation Result Performance of Different Charging Schemes (Veh=120 , I = 4kWh, Crate=15kW)

  6. Possible Extension • More realistic battery model. • Enhanced charging strategies • Develop an analytical model for optimum charging strategy

  7. Proj. #2: Physical Testing of Moral Algorithm Retry Limits • Data rate anomaly in multi-rate environments • MORAL: Adjusting retry-rates to achieve better fairness • Algorithm only tested by simulation • Testing theoretical basis of retry limit modification, not full algorithm

  8. Project summary • Equipment used • Knoppix • Linux distribution with many network tools built in • Iperf • Open-source traffic generation and analysis tool • Iwconfig • Linux wireless network configuration tool

  9. Proj. #3: Evaluation of TCP performance over MORAL rate adaptation scheme using NS3 • Optimize the maximum retransmissions parameter in mac layer. • TCP fairness is evaluated • Implemented simple MORAL in NS3 • Evaluate MORAL for different TCP scenarios

  10. Projects Ideas

  11. Idea #1:Understanding Power consumption of Smartphone modules • Tool: • Monsoon Power Monitor tool • Objective: • Classify power consumption for different components if smartphone: • Incoming/outgoing Call • Incoming/outgoing SMS • Speaker/Microphone Usage • Data upload/download using WiFi/Cellular • Related work: • PowerTutor: http://ziyang.eecs.umich.edu/projects/powertutor/

  12. Idea #2: Detecting Driver/Passenger Phones • Objective: • Driver & passenger uses different doors to enter. • Idea: Correlate accelerometer/gyro/compass sensor readings with the door open/close timing • Goal: Identify the door a phone has entered from. • Related work: • MobiCom 2011 paper: “Detecting Driver Phone Use Leveraging Car Speakers”, http://www.sigmobile.org/mobicom/2011/slides/215-detecting-slides.ppt • MobiSys 2011 poster: “You Driving? Talk to you later”, http://synrg.ee.duke.edu/papers/driver-detect-poster.pdf • Duke Univ. 2011 Technical Report: “In-Vehicle Driver Detection Using Mobile Phone Sensors”, http://www.ee.duke.edu/files/ece/GWDD2011_Chu.pdf

  13. Idea #3: Video Perception on Smartphone over Different Mobility Modes • Objective: • Video streaming have different resolutions and frame rates. Each configuration will have different power consumption. • Idea: Under different mobility patterns (e.g., walking, running, riding on car, .etc.), user will have different perception. For example, with high vibration, user do not need high frame rate. • Goal: Through user studies, find the correlation between the video configuration and mobility pattern. • Similarly, could replace mobility with background ambient light (e.g., darkroom, sunny day, etc.) • Related work: • MobiSys 2011 paper: “Chameleon: a color-adaptive web browser for mobile OLED displays”, http://www.ruf.rice.edu/~mobile/publications/dong11mobisys_chameleon.pdf

  14. Idea #4: Crowd Source to Detect Timing Information of Traffic Light • Objective: • Many of the Traffic Lights uses a static pre-timing phases. • Idea: A vehicle passing and stopping at specific traffic, could collect information on when it stopped (red phase) and moved (green phase). Collecting this information from different vehicles at same traffic light could give us a detail on the traffic phase information. • Goal: Utilize accelerometer/gyro/compass sensors in smartphones to collect stopping/moving times. Emulate traffic light at parking lot and run experiments to collect info from different phones. Fuse this information to get idea on the traffic light. • Related work: • MobiSys 2011 paper: “SignalGuru: Leveraging Mobile Phones for Collaborative Traffic Signal Schedule Advisory”, http://www.sigmobile.org/mobisys/2011/slides/signalguru.pdf

  15. Idea #5: Vehicle’s Lane Identification • Objective: • Different lanes on the road on different times have unique driving characteristics in addition to physical characteristics. • Idea: Profile one of these characteristics (e.g., average speed, # of stops, etc.) over different lanes for different lane segments. • Goal: Utilize accelerometer/gyro/compass/GPS sensors in smartphones to collect physical and driving characteristics of lane segments. Build a classifier based on the data collected. Build an app that measure driving characteristics and detect the best matching lane giving the GPS and current time.

  16. Idea #6: Vehicle’s Switching Lane Detection • Objective: • Switching lane require a swift action in most cases. This action has a temporal impact on the smartphone mobility sensors (i.e., accelerometer/gyro/compass). • Idea: Utilize accelerometer/gyro/compass sensors in smartphones to detect switching lane actions. • Goal: Develop an application that collect accelerometer/gyro/compass data. Run several experiments on lane switching to collect data. Detect the correlation between lane switch and sensor data. Develop a scheme to detect lane switch from sensor data. Evaluate your scheme.

  17. Idea #7: Cloud Computing - Windows Azure  • Windows Azure is a foundation for running applications and storing data in the cloud • Customers use it to run applications and store data on Internet-accessible machines owned by Microsoft. • Related Work: • Introducing Windows Azure (http://download.microsoft.com/download/0/A/9/0A9F8C97-8F40-4D63-9AE7-3B2F20B57F93/Introducing%20Windows%20Azure,%20Final%20PDC10.pdf) • Azure: http://www.microsoft.com/windowsazure/learn/get-started/ • Hawaii: http://research.microsoft.com/en-us/um/redmond/projects/hawaii/students • Students Projects: http://research.microsoft.com/en-us/um/redmond/projects/hawaii/applications/

  18. Idea #8: Sectorized Antennas • Objective: • Evaluate S-MAC using NS2/3 simulator under different configuration parameters: • Mobility • Infrastructure/Ad hoc • Dynamic Carrier Sense Threshold for S-MAC

  19. Idea #9: Inter-vehicular Communications • Objective: • In this project you will investigate the mobility patterns of cabs in a typical urban city and design a protocol that is specifically designed to facilitate multi-hop communication and routing via cabs.   • In the first part you will use the extensive data‐sets that capture the movement of cabs in San Francisco city. These data‐sets are available at the CRAWDAD site (www.crawdad.org) (http://www.crawdad.org/meta.php?name=epfl/mobility) and provide the gps coordinates of about 500 cabs for a 30 day period. Using these data‐sets you are expected to provide important insights regarding cab movements. For example: typical speed of the vehicles, how often couple of same cabs come in vicinity of each other (rendezvous points as traffic lights), the duration of rendezvous, popular spots, congested spots and durations, etc. • In the second part you are expected to design a scheme that exploits one or more of the insights from part 1 to improve routing in vehicular networks. For example, you can think of a geographic scheme that utilize hotspots You are expected to do an evaluation of the scheme using an appropriate simulation.

  20. Idea #10: Software‐defined Radios • Software‐defined radios implement most of the radio functionality in software, so they offer a lot of flexibility.   • Objective: • Understand and get familiar with USRP hardware we have in lab. • With the resources on net, use USRP boards to construct MIMO testbed • Experiment and test with the constructed board.

  21. Idea #11: Cell Breathing • Cell Breathing is an admission control scheme that is utilized in cellular networks. It is adapted in WLAN. It is based on adjusting transmission power of access points for load balance. Major idea is by reducing AP coverage range for beacons, nodes at the edges will move to another AP in region. • However, nodes at edges suffer always from low RSSI from any neighbor AP. • Objective: • Evaluate the Cell Breathing scheme using simulation to understand the limitation and cons introduces by this scheme. Then, propose an enhancement to Cell Breathing scheme. Evaluate your modified scheme compared to Cell Breathing scheme.

  22. Other ideas • Reliable Broadcast/Multicast scheme for infrastructure mode • Power control / Mobility control for ad hoc networks • Location service for mobile device

  23. Deadlines • Feb 29th: Team information and 1-2 pages draft on project’s idea, motive, objectives, and tasks. • March 19th: Project updates (Each group present their project progress and timeline). Deliverable: 1 page + presentation • March 30th: Survey paper due date. Deliverable: 10 pages report • April 2nd: Project updates. Deliverable: 1 page + presentation • April 4th: Mid-Term Exam • April 11th: Survey paper presentations. Deliverable: presentation • April 23rd: Project due date and presentations. Deliverable: project report + presentation

  24. Survey Paper • Tips: • You should not blindly accept all statements you read. • Being biased • Ignore relevant related work • Overstate the results that are presented • Assess the accuracy of the results • Uses inaccurate simulators • Ignores certain sources of overhead • Presents graphs in misleading ways • Very limited in scope (e.g. collects results on one testbed that may not be typical) • You cannot copy text from other papers or the web • Still, you can quote short excerpts or figures from other material (must reference it) • Deliverable: • 15-20 min presentation • 10 pages paper

  25. More on Survey Paper • Paper Structure: • A descriptive title (“Survey of …”) and your name and student number on a separate title page, • An abstract (written last) which briefly describes the entire paper, • An introduction (written second last) that summarizes what the paper presents without expecting the reader to have already read the paper – this can be tricky, • A problem description which explains the problem and motivates interest in it, • The actual survey with critical analysis of each paper presented and the liberal use of figures to aid in the exposition, • A conclusion which summarizes the paper (now assuming the reader has read it) and which describes possible directions for future research, and • A detailed bibliography presented in an easy to read and consistent format

  26. Course Project • Goal: obtain hands-on experience • Initial proposal 1-page due before Spring break+ 1- page progress report every 2 weeks (due Friday night) + final report + presentation • Projects consist of 3 parts: • Problem identification • Solution design • Performance evaluation • Deliverable: • 15-20 min presentation • Project report

More Related