- ESA Summer of Code in Space 2017 (SOCIS)
- SOCIS Frequently Asked Questions
- ESA-SOCIS google mailing list
- Get in contact with the ns-3 team: ns-developers mailing list | IRC #ns-3 on freenode.net
SOCIS 2017 Ideas
This webpage highlights project ideas for ns-3's ESA Summer of Code in Space 2017 effort.
SOCIS 2017 Timeline is:
- Until 31 may 2017: Students application
- June-August 2017: 3-months coding period
Full timeline is here:http://sophia.estec.esa.int/socis/?q=timeline
While discussions about ideas can be done earlier, please note that ns-3 will not receive an answer to its SOCIS application before May.
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.10 in January 2011). 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 almost 51,000 successful downloads of our released software between January 2011 and January 2012, and we have a users mailing list of about 2392 members now averaging 574 posts per month. The code base has a total of 113 authors and 25 maintainers.
Our SOCIS organizational admin is Tommaso Pecorella.
Mentors will be paired with students based on the projects that are selected. Mentors from companies are welcome, if the employer will permit the mentor sufficient time to perform the mentoring. Prospective mentors should notify Tommaso Pecorella of interest. Mentors familiar with ns-3 development practices will be preferred, to improve the chances of student code merge.
For students interested in applying to ns-3 for SOCIS, keep in mind that the application period will be in May, if ns-3 is accepted to participate again. However, student applications will be better positioned if the student starts early to work with mentors to develop ideas. Please go through the following list to get started:
- Read the official SOCIS Student Participant Agreement.
- Read SOCIS FAQ. In particular:
- Double check if you can participate: Eligibility.
- Look through our ideas list below to see if you find a project that interests you. Check back in the future as ideas may be added.
- Review the ns-3 tutorial thoroughly, if you have not already done so.
- Look through the GSoC2015 Student application template to start preparing your proposal.
- Next, proceed to get in touch with the developers on the mailing list and refine your proposal. It is possible (i.e., almost sure) that a proof of your ns-3 knowledge is asked.
The following are a list of project proposals from the ns-3 team for ESA Summer of Code in Space 2016. Applicants are however free to propose their own ideas. In addition, please note that these ideas are not limited to SOCIS, anyone is welcome to work on them. Please email the ns-developers list if you have an idea that you'd like to work on. Applicants are encouraged to look over this list, pick one that especially interests them, think about it, and discuss potential approaches on the ns-developers list. Previous experience with the Google Summer of Code programmes suggest that the more you discuss and refine your proposal on the mailing list beforehand, the more stronger a proposal it will develop into, and the higher your chances of being accepted into the programme.
Due to the SOCIS focus, only space-related ideas can be considered.
Each project idea within a particular priority 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.
Guidelines for project ideas
For mentors who're adding project ideas to the list below, please ensure that:
- The projects are sized such that there can be a code merge by the end of the coding period. The scope of the project should be such that it is very difficult to not have a code merge by the end of the summer.
- The proposed projects are not too open-ended. That is, if the deliverables or a clear path to the same are not well understood, it is better kept outside GSOC.
- There should be a clear merge path to one of the main project code repositories (ns-3-dev, ns-3-dce, bake) by the end of the summer, either because the patches directly apply or they directly apply to an ns-3 module that is in the process of merging with ns-3-dev.
- The projects are related to Space applications and technologies.
Delay-Tolerant Networking integration
Delay-Tolerant Networking (DTN) is the protocol architecture for deep-space communications. Previous editions of SOCIS and GSoC for ns-3 resulted in the development of two protocols in the ns-3 stack, the Bundle Protocol and the Licklider Transmission Protocol:
However, these protocols were never integrated following the conclusion of the summer projects, and furthermore, there aren't any DTN applications or DTN routing protocols to use with ns-3. This project is therefore focused on providing a complete DTN stack by integrating the code from the past two projects referenced above, plus developing a simple DTN routing protocol and simple DTN application that can sit on top of the bundle protocol. The overall project goal is to demonstrate a multihop, multipath DTN network in ns-3 over simple link models (e.g. point-to-point like links with a static delay that is very large, measured in seconds or tens of seconds) and to test and document how conforming the implementation is to the standard.
In your application, tell us how you plan to test the implementation. For example, NASA has built a virtual machine equipped with a network emulator for testing of DTN protocol implementations. The CORE emulator was also used to test the ns-3 DTN code in 2014. This type of testing would be useful for this suggested project (running ns-3 in emulation mode in one of the containers, and making it interoperate with a ION stack provided by NASA). Please consider this or let us know about your other testing ideas.
In your application, tell us about the current status of the existing ns-3 implementations and sketch out what you think needs to be done, along with a rough schedule, to complete this project.
- Required Experience: C++
- Bonus Experience: any previous DTN experience
- Interests: Network protocols, software integration and testing
- Difficulty: medium
- Recommended reading:
Satellite Mobility Model
ns-3-SatMobility Satellite communications are affected by satellite and user's mobility. In order to simulate a channel, it is of paramount importance to know the satellite(s) mobility (orbits) and user's mobility (mostly statistical properties to simulate the sky's portions seen by the user). The goal of the idea is to provide a framework to easily define a single satellite or a constellation movement pattern and the user's properties according to a predefined scenario (e.g., urban, hills, mountain, etc.). The framework should come with pre-defined well-known satellite constellations, e.g., GALILEO, GPS, Inmarsat, etc.). The model should also provide an easy way to define the satellite footprints (Satellite-fixed and Earth-fixed footprints is a plus). The model should extend the ns-3 mobility model, and should also be able to provide triggers to enable/disable satellite links (e.g., Inter-satellite links).
- Required Experience: C++
- Bonus Experience: Satellite constellations
- Interests: Satellite visibility, satellite networking
- Difficulty: easy / medium
- Recommended reading:
Real device Emulation improvements
Mentors: Tommaso Pecorella
One of the most important features for a network simulator is its ability to work in `emulation' mode, i.e., to receive and send real data through real network interfaces. Although ns-3 can do that, the emulation performances are severely hindered by how the network interfaces are handled. As a consequence, even with high-performance CPUs and high-performance network adapters, the bandwidth is severely limited.
Next-generation satellite systems (even CubeSats) are expected to have multiple, high-performance links, e.g., space-hearth, inter-satellite, etc. Moreover, the research field is also interested in extra-terrestrial networks, like extra-planetary sensor networks, etc. In order to effectively simulate real hardware, including satellites, extra-terrestrial vehicles, etc., it is important to be able to overcome the actual network interface performance limitations.