Analysis and Standards for the Information-Internet

From its-wiki.no

Jump to: navigation, search

Creating Analysis and Standards for the Information-Internet

by Vlorjan Badallaj
Supervisor(s) Josef.Noll, Iñaki Garitano
Due date 2018/11/05
Status Planned
Problem description: The need for basic information delivery over capacity-limited networks requires new standards for an Information-Internet (InfoInternet), delivering compressed text and picturesto everyone. The goal of this Master Thesis is to establish and elaborate the standards for the InfoInternet.

The Internet links several billion devices worldwide together, and consists of a multitude of networks with local or global scope, private or public connected to a broad array of networking technologies. Today, around 46% of the world’s households have access to Internet through either fixed or mobile subscriptions. However, the gap between developed and developing countries is still wide. According to ITU [2], by the end of 2015, 34% of households in developing countries had Internet access, compared with more than 80% in developed countries. In the least developed countries, only 7% of households have Internet access. In this same set of countries, 12 of 100 inhabitants have active mobile broadband subscriptions, whereas less than 1 of 100 inhabitants have fixed broadband subscriptions.

Thus, a large number of inhabitants don't have access to information, not even basic information. The expected outcome of this Master Thesis is a set of elements being the basis for the InfoInternet, and a simulation on how the choice of parameters will influence the size of information being sent to the users' devices. As an example, the size of pictures is a measure of information, but also a criteria for the InfoInternet. One might either restrict to size (e.g. 200 kB), to pixel resolution (e.g. 640 x 480) or to compression modes. Other elements include dynamic styling information.

Methods and Tools: The tools and methods in this thesis are based on
  • A set of scenario, describing the challenges
  • A list of requirements being extracted from the scenarios
  • A description and evaluation of technologies and tools being candidates for solutions
  • A functional architecture/description of the envisaged system
  • An implementation of the core concepts
  • A demonstration of the solution
  • An evaluation of the solution, including a critical review of the descisions taken earlier
  • Conclusions
  • References
Time schedule The envisaged time schedule (for a long thesis/60 ECTS) is:
T0 0 starting month, T0+m denotes the month where the contribution to a certain chapter shalle be finalized
T0+2 months: create an initial page describing the scenario
T0+3: Provide a list of technologies which you think are necessary for the thesis
T0+4: Establish the table of content (TOC) of the envisaged thesis. Each section shall contain 3-10 keywords describing the content of that section
T0+7: Provide a draft of section 2 (scenario) and 3 (technologies)
T0+10: Establish a draft on what to implement/architecture
T0+11: Set-up an implementation, testing and evaluation plan
T0+15: Evaluate your solution based on a set of parameters, keep in mind there is no such thing as a free lunch
T0+17: Deliver the thesis
Pre-Knowledge This thesis includes a reasonable amount of programming. The envisaged thesis is based on radio communications, thus expects the user to have followed at least two radio-related courses
Approved Pending by
Keywords Basic Internet, Basic Education
Depiction

this page was created by Special:FormEdit/Thesis, and can be edited by Special:FormEdit/Thesis/Analysis and Standards for the Information-Internet

This page provides hints on what to include in your master thesis.

TOC

Title page, abstract, ...

1. Introduction, containing: short intro into the area, what is happening
1.1 Motivation, containing: what triggered me to write about what I'm writing about
1.2 Methods, containing: which methods are you using, how do you apply them
2. Scenario, optional chapter for explaining some use cases
2.1 user scenario, (bad name, needs something bedre)
2.2 Requirements/Technological challenges
3. State-of-the art/Analysis of technology, structure your content after hardware/SW (or other domains). Describe which technologies might be used to answer the challenges, and how they can answer the challenges
3.1 technology A
3.2 technology B
4. Implementation
4.1 Architecture, functionality
4.2
5. Evaluation
6. Conclusions
References

Comments

Red line

Your thesis should have a "red line", which is visible throughout the whole thesis. This means you should mention in the beginning of each chapter how the chapter contributes to the "goals of the thesis".

Use of scientific methods

A thesis follows a standard method:

  • describe the problem (problemstilling)
  • extract the challenges. These challenges should be measurable, e.g. method is too slow to be useful to voice handover.
  • Analyse technology with respect to challenges. Don't write & repeat "everything" from a certain technology, concentrate on those parts (e.g. protocols) which are of importance for your problem

References

  • Wikipedia is good to use to get an overview on what is happening. But there is not scientific verification of Wikipedia, thus you should use wikipedia only in the introduction of a chapter (if you use text from wikipedia). Use scientific literature for your thesis.
  • Scientific library is "at your hand", you can get there directly from UiO: [[How to get access to IEEE, Springer and other scientific literature -> Unik/UiOLibrary]]
  • I suggest that references to web pages, e.g. OASIS, W3C standards, are given in a footnote. Only if you find white papers or other .pdf documents on a web page then you refer to them in the reference section.

Evaluation of own work

Perform an evaluation of your own work. Revisit the challenges and discuss in how you fulfilled them. Provide alternative solution and discuss what should be done (or what could have been done).