GSOC2010Projects

From Nsnam
Jump to: navigation, search

Main Page - Current Development - Developer FAQ - Tools - Related Projects - Project Ideas - Summer Projects

Installation - Troubleshooting - User FAQ - HOWTOs - Samples - Models - Education - Contributed Code - Papers

Please visit GSoC 2010 Accepted Projects to learn more about ns3 projects for GSoC 2010

Ns3GSoC2010Flyer.jpg

GSoC 2010 Ideas

This webpage highlights project ideas for ns-3's Google Summer of Code 2010 effort.


About the ns-3 project

ns-3 is a discrete-event network simulator, with a particular emphasis on network research and education. Users of ns-3 can construct simulations of computer networks using models of traffic generators, protocols such as TCP/IP, and devices and channels such as WiFi, and analyze or visualize the results. Simulation plays a vital role in the research and education process, because of the ability for simulations to obtain reproducible results (particularly for wireless protocol design), scale to large networks, and study systems that have not yet been implemented. A particular emphasis in ns-3 is the high degree of realism in the models (including frameworks for real application and kernel code) and integration of the tool with virtual machine environments and testbeds; we view that researchers need to move more effortlessly between simulation, testbeds, and live experiments, and ns-3 is designed to facilitate that.

ns-3 has been in development since 2005 and has been making quarterly releases since June 2008 (our last release was ns-3.7 in January 2010). ns-3 is replacing the popular ns-2 tool which was developed in the 1997-2000 timeframe but became out of date and unmaintained. The tool is coming into wide use; our web server logged over 10,000 successful downloads of our released software in January 2010, and we have a users mailing list of about 500 members now averaging 200-300 posts per month.

Our GSOC organizational admin is Alina Quereilhac and our backup org admin is Tom Henderson.


Project Ideas

The following are project ideas which the ns-3 team has identified as important and is most interested in working on as part of the 2010 Google Summer of Code. GSoC applicants are however free to propose their own ideas. In addition, please note that these ideas are not limited to Google Summer of Code, anyone is welcome to work on them. Please email the ns-developers list if one interests you. GSoC applicants are encourage to look over this list, pick one that especially interests them, think about it, and discuss potential approaches on the ns-developers list. That will help you develop the idea and present a concrete, meaningful application.

Each project idea has been tagged with the following properties:

  • Required Experience: Languages, concepts, or packages with which applicants must be familiar.
  • Bonus Experience: Other experience or familiarity which would be greatly helpful to applicants for this project.
  • Interests: Areas of particular relevance to this project, and an indicator of where successful students might apply their experiences coming out of this project.
  • Difficulty: easy, medium or difficult
  • Recommended reading: pointers to documentation, papers, specific bugs, etc.

Note that all of the projects require some experience and comfort with C++. Project ideas for which C++ is noted as a required experience will require more and deeper familiarity with the language. A similar notion applies to computer networking, BSD sockets, etc: Familiarity is strongly preferred, but is not required except where explicitly noted due to the topic being more advanced in that regard.


Priority Project Ideas


The following are work areas the ns-3 project has identified as the highest priorities, has several mentors available, and would be especially interested in having students work on.


Model Store

Mentors: TBD

  • Model Store. The recent ns-3 developers meeting identified a high priority project need to extend the overall build and packaging system for ns-3 to support a user-contributed "model store" inspired by the iPhone App Store. Presently, ns-3 has a monolithic build system and model contributors from outside the project have the choice of trying to integrate their code into the main tree, or else maintaining it (or not) as an independent third-party archive. However, from a maintenance perspective, the project cannot accept maintenance of all contributed models in the long term, and users also do not want to download and build an ever growing code base that may contain many models of no interest to them. Yet we do not want this maintenance and build time bottleneck to stifle user contributions. What we envision is a student project to develop a system and template for future contributors that will allow third-party developers to package, distribute, and update ns-3 protocol models and manage dependencies between models and the core of ns-3.
  • App Store Technical Requirements
  • Required Experience: Python (ns-3 build system is Python-based)
  • Bonus Experience: Packaging frameworks, C++
  • Interests: Build systems, packaging
  • Difficulty: Medium to high
  • Recommended reading: ns-3's waf build system, package management tools, Firefox plugin management, Apple App Store

Routing

Mentors: Ruben Merz

  • Click Modular Router Integration. Completed by Lalith Suresh This project would port and enable ns-3 simulations to use the Click modular router, widely used in research. This has been previously done for ns-2, and accomplishing this integration for ns-3 would enable faster protocol development and utilization of many existing protocol implementations.

Network Stack

Mentors: Florian Westphal Note: We do not have a mentor identified for this project.

  • Network Simulation Cradle for IPv4. See Mathieu's ns-3-linux repository which may obsolete this project idea. Last year's ns-3 Google Summer of Code very successfully ported the Network Simulation Cradle, providing the ability to run Linux TCP code over ns-3's IPv4 stack. This project would extend that effort to completely port the Linux TCP/IPv4 stack. This wolud start by adding IPv4 support to NSC, then support for multiple interfaces, routing tables, and assigning addresses, then making those features available in ns-3.
    • Required Experience: C
    • Bonus Experience: Linux kernel, TCP/IP
    • Interests: Linux, operating systems, virtualization, software-in-the-loop
    • Difficulty: medium to high
    • Recommended reading:

Emulation and Simulation In The Loop

Mentors: Craig Dowell Note: We probably do not have a mentor for this project in 2010.

  • EMULAB Support and Integration. This project would attempt to integrate ns-3 and Emulab, a leading testbed for Internet research. Emulab experiments are described in tcl-like ns-2 scripts and are driven by ns-2 emulation. Two main goals of this effort would be: 1) Test and document how ns-3 emulation mode could be used in Emulab instead of ns-2, and compare its features and performance. 2) Investigate whether Emulab scripting could be moved to Python/ns-3 or whether ns-3 simulations need to generate Tcl for Emulab and attempt to do this integration.
    • Required Experience: C/C++
    • Bonus Experience: Emulab, ns-2, Tcl
    • Interests: Simulation, emulation, simulation-in-the-loop
    • Difficulty: medium to high
    • Recommended reading:

Peer to Peer and Content Based Routing

Mentors: Marcello Caleffi

  • Mobile P2P. ns-3 currently does not include any implementation of Mobile Peer-to-Peer (P2P) systems. This project would implement some additional networking protocols based on a cross-layer approach between routing and Distributed Hash Tables (DHTs), such as ATR and MADPastry. Both the ns-2 implementations of the cited protocols are currently available and could be used as design guides.
    • Required Experience: C/C++
    • Bonus Experience: P2P, mobile ad hoc networks (MANETs), ns-2
    • Interests: P2P, DHT, MANETs, routing.
    • Difficulty: medium
    • Recommended reading:
      • Mobile ad hoc networking: imperatives and challenges by Imrich Chlamtac, Marco Conti, Jennifer J. -N. Liu, - Ad Hoc Networks, Volume 1, Issue 1, July 2003, Pages 13-64, ISSN 1570-8705, DOI: 10.1016/S1570-8705(03)00013-1.
      • MADPastry: A DHT Substrate for Practicably Sized MANETs. by Thomas Zahn and Jochen Schiller - In Proc. of 5th Workshop on Applications and Services in Wireless Networks (ASWN2005), Paris, France, June 2005.
      • Chord: A scalable peer-to-peer lookup service for internet applications. by Stoica, I., Morris, R., Karger, D., Kaashoek, M. F., and Balakrishnan, H. 2001. - In Proceedings of the 2001 Conference on Applications, Technologies, Architectures, and Protocols For Computer Communications (San Diego, California, United States). SIGCOMM '01. ACM, New York
      • P2P over MANET: Indirect tree-based routing by Caleffi, M.; Paura, L.; - Pervasive Computing and Communications, 2009. PerCom 2009. IEEE International Conference on , vol., no., pp.1-5, 9-13 - March 2009.
      • Mobile Ad Hoc Networks: the DHT Paradigm, Ph.D. Thesis by M. Caleffi - University of Naples Federico II - December 2008.


Satellite network stack

Mentors: Tommaso Pecorella


Cognitive Radio Networks

Mentors: Marcello Caleffi

  • Cognitive Networks ns-3 currently does not include any implementation of routing protocols for cognitive networks. This project would implement some additional networking protocols for this scenario. Such protocols should be able to deliver packets across multiple channels avoiding to interfere with primary users. A cross-layer approach with the physical layer is required for spectrum sensing.
    • Required Experience: C/C++
    • Bonus Experience: mobile ad hoc networks (MANETs), ns-2
    • Interests: MANETs, routing, cognitive networks.
    • Difficulty: Medium
    • Recommended reading:
      • Mobile ad hoc networking: imperatives and challenges, Ad Hoc Networks by Imrich Chlamtac, Marco Conti, Jennifer J. -N. Liu - Volume 1, Issue 1, July 2003, Pages 13-64, ISSN 1570-8705, DOI: 10.1016/S1570-8705(03)00013-1.
      • Multihop cognitive radio networks: to route or not to route by Khalife, H.; Malouch, N.; Fdida, S. - Network, IEEE , vol.23, no.4, pp.20-25 - July-August 2009
      • Search: A routing protocol for mobile cognitive radio ad-hoc networks, Computer Communications by K.R. Chowdhury, M.D. Felice - Volume 32, Issue 18, Cognitive Radio and Dynamic Spectrum Sharing -Systems, 15 December 2009, Pages 1983-1997, ISSN 0140-3664, DOI: 10.1016/j.comcom.2009.06.011.
      • Mobile Ad Hoc Networks: the DHT Paradigm, Ph.D. Thesis by M. Caleffi - University of Naples Federico II - December 2008


MAC and PHY models for LTE

Mentors: Nicola Baldo, Marco Miozzo

  • 3GPP Long Term Evolution (LTE) Update: Basic LTE support (PHY) is Giuseppe Piro's 2010 GSOC project; please contact him for status and next steps. LTE is an upcoming wireless technology already widely endorsed among mobile operators and manufacturers. Unfortunately, ns-3 still does not feature any model for LTE. The LTE standard is very complex, so it is not reasonable to develop a NetDevice modeling all aspects of LTE within the limited time span of the GSOC. Rather, we propose students to focus on the implementation of a subset of the functionality of LTE. This can include (but is not necessary limited to) the following aspects:
    1. Frequency Division Duplex PHY layer based on OFDMA/SC-FDMA (the ns-3 spectrum framework) could be used for this purpose)
    2. Medium Access Control (scheduling, timing, HARQ)
    3. Radio Link Control (RLC) (transparent mode (TM), unacknowledged mode (UM), acknowledged mode (AM))
    • Required Experience: C++, generic understanding of PHY and MAC layers
    • Bonus Experience: OFDM/OFDMA, HARQ
    • Interests: 4G mobile communications
    • Difficulty: medium to difficult (depending on what functionality the student proposes to implement)
    • Recommended reading:

Underwater Acoustic Network

Mentors: Leonard Tracy

  • UAN framework Update: This project completed by Andrea Sacco in 2010 Extend the currently proposed UAN modules to support a wider variety of common underwater networking scenarios. The developed extensions could be a subset of: Support for modeling of AUV network nodes, accurate PHY layer modeling of new modulations (e.g. ZP-OFDM), power management layers, or routing layers (e.g. P2P).

Transport

Update: Adrian Tam's ns-3-tcp repository has made progress on the below two topics and should be considered as the new baseline for TCP work

Mentors: Josh Pelkey, Tom Henderson

  • TCP Validation. TCP is one of the most widely used and widely studied protocols in the Internet. ns-3 has two TCP implementations. Recently, RFC 5681 was published, documenting recommended TCP behavior. This project would consist of reviewing the ns-3 TCP implementations and testing them for conformance to RFC 5681 (and fixing any issues that were found to arise). One outcome of this project would be a test suite that will ensure that ns-3's TCP implementation is accurate and does not regress over time.


Mentors: Alfredo Grieco

  • TCP Congestion Avoidance. Linux TCP implements a lot of TCP congestion control variants, including variants such as Veno, Westwood, Vegas, etc. This project would attempt to provide a library of congestion avoidance types, including test suites that exercised each one.


Additional Project Ideas


The following are additional project ideas that the ns-3 team has highlighted as important projects to support, and are suggested for students to extend. Not all of them have specific mentors assigned yet but we would seek out mentors from our mentor pool if high quality applications came in on these topics (or any ns-3 topic, for that matter).


Routing

  • Generalized Router Models/Structure. Many simulators, including ns-3, do not provide high fidelity models of Internet routers. For instance, intra-device latencies and input queuing behavior are not modeled. This project would adapt recent results on empirical router testing to develop a new, more detailed Router node type for ns-3.
    • Required Experience:
    • Bonus Experience: Routing architectures, routing protocols, queueing theory, statistics
    • Interests: High fidelity simulation, queueing theory, statistics, data driven model development
    • Difficulty: medium-to-high, because there may be a dependency on Click router


MAC and PHY Models

  • CSMA/CD and Aloha
    • Description: Implement a CSMA/CD MAC protocol. Optionally, implement slotted aloha. A good reference describing the CSMA/CD and aloha protocols as well as basic theoretical results about these protocols is "Computer Networking: A Top-Down Approach.".
    • Required Experience: basic C++, know what aloha and CSMA/CD are.
    • Bonus Experience: ns-3 programming, contributions to open source projects.
    • Interests: networking, C++ programming
    • Difficulty: easy
    • Recommended reading: Computer Networking: a top down approach, chapter 5.
  • SNS for ns-3 Wifi. Staged Network Simulations (SNS) is a patch for the ns-2 wireless models which provides for function approximation and caching. That mechanism greatly speeds up the many calculations required in mobile wireless simulations. This project would incorporate those techniques into the ns-3 WiFi model.
    • Required Experience:
    • Bonus Experience: Software profiling, software tuning
    • Interests: Approximation, caching, software profiling, high performance computing, scientific computing
    • Difficulty: depends on what functionality the student proposes to implement


Applications and Systems

  • Large Scale Topology Generation and Management. ns-2 incorporates support for various topology generators, which would be useful to also support in ns-3. This project would investigate porting topology generators or mapping their output to ns-3 simulations. It would also touch on the problem of coherent IP addressing in generated topologies. In particular, recent work by the Emulab project may be useful in this regard.
    • Required Experience:
    • Bonus Experience: Graph theory, network management, Internet topology
    • Interests: Internet topology, Internet autonomous systems, graph theory
    • Difficulty: depends on what functionality the student proposes to implement