Elaborating and implementing http2 standards for server-side compression
| Wiki for ITS | ||||||
|---|---|---|---|---|---|---|
|
|
Elaborating and implementing http2 standards for server-side compression
| by | N.n. |
|---|---|
| Supervisor(s) | Josef Noll, Iñaki Garitano |
| Due date | 2018/01/05 |
| Status | Planned |
| Problem description: | The need for basic information delivery over capacity-limited networks requires new standards for a "low-capacity Internet", delivering basic information for free to everyone.
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 goal of this Master Thesis is to elaborate the use of novel web standards for server side compression. The idea is to send compressed texted and pictures to the mobile phone. Opera Mini is currently the only browser following this principle, by reducing Web pages to text and pictures, and compress the page before sending the compressed page to the mobile phone. The thesis needs to elaborate e.g. http2 for server-side compression of content or other functionalities to deliver LC-Internet. |
| Methods and Tools: | The tools and methods in this thesis are based on
|
| Time schedule | The envisaged time schedule (for a long thesis/60 ECTS) is:
|
| 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 |
| Depiction |
this page was created by Special:FormEdit/Thesis, and can be edited by Special:FormEdit/Thesis/Elaborating and implementing http2 standards for server-side compression
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).
