Difference between revisions of "Software Defined Networking for tactical communications"
Geir.Bakken (Talk | contribs) |
Geir.Bakken (Talk | contribs) |
||
Line 6: | Line 6: | ||
|ThesisStatus=Planned | |ThesisStatus=Planned | ||
|Objective=The Norwegian Defence Communication Infrastructure (NDCI) is a term that describes the communication part in the Norwegian Defence information infrastructure. It is systems of tactical and strategic networks, transmission as well as how these systems are linked together to produce the communications services. | |Objective=The Norwegian Defence Communication Infrastructure (NDCI) is a term that describes the communication part in the Norwegian Defence information infrastructure. It is systems of tactical and strategic networks, transmission as well as how these systems are linked together to produce the communications services. | ||
− | A tactical communication node is tactical communication solutions for both portable and mobile nodes that are connected to the infrastructure | + | A tactical communication node is tactical communication solutions for both portable and mobile nodes that are connected to the infrastructure through defined termination points and uses different kinds of transmission bearers, for example radio, Satcom or Internet through 3G. These solutions make the services of the strategic part of the infrastructure available in the tactical domain. The nodes are also capable to operate autonomously and be independent. The objective of this thesis is to look into software defined networking (SDN) and how its control plane layer can be established into the infrastructure. And further, how tactical communication nodes with relevant real-time data can have available resources and military priority in the network when they need it according to predefined policies. A tactical node that can get the necessary priorities for its real-time data and sufficient capacity to transmit data will as a result give the decisions makers in the Norwegian Defence better situation awareness. Disclosure of relevant and real-time-updated data streams into command and control systems will provide increased operational effect. This document presents an implementation of the OpenFlow controller into a simulated network environment, and how traffic engineering and military priority can be established. |
− | The objective of this thesis is to look into software defined networking (SDN) and how its control plane layer can be established into the infrastructure. And further, how tactical communication nodes with relevant real-time data can have available resources and military priority in the network when they need it according to predefined | + | |
− | This document presents an implementation of the OpenFlow controller into a simulated network environment, and how traffic engineering and military priority can be established | + | |
|Methods=The tools and methods in this thesis are based on | |Methods=The tools and methods in this thesis are based on | ||
* A set of scenario, describing the challenges | * A set of scenario, describing the challenges |
Revision as of 10:28, 9 April 2014
Wiki for ITS | ||||||
---|---|---|---|---|---|---|
|
![]() |
Using Software Defined Network in the Norwegian Communication Infrastructure for tactical communication nodes.
by | Geir.Bakken |
---|---|
Supervisor(s) | Knut Øvsthus, Josef Noll |
Due date | 1.11.2014 |
Status | Planned |
Problem description: | The Norwegian Defence Communication Infrastructure (NDCI) is a term that describes the communication part in the Norwegian Defence information infrastructure. It is systems of tactical and strategic networks, transmission as well as how these systems are linked together to produce the communications services.
A tactical communication node is tactical communication solutions for both portable and mobile nodes that are connected to the infrastructure through defined termination points and uses different kinds of transmission bearers, for example radio, Satcom or Internet through 3G. These solutions make the services of the strategic part of the infrastructure available in the tactical domain. The nodes are also capable to operate autonomously and be independent. The objective of this thesis is to look into software defined networking (SDN) and how its control plane layer can be established into the infrastructure. And further, how tactical communication nodes with relevant real-time data can have available resources and military priority in the network when they need it according to predefined policies. A tactical node that can get the necessary priorities for its real-time data and sufficient capacity to transmit data will as a result give the decisions makers in the Norwegian Defence better situation awareness. Disclosure of relevant and real-time-updated data streams into command and control systems will provide increased operational effect. This document presents an implementation of the OpenFlow controller into a simulated network environment, and how traffic engineering and military priority can be established. |
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 | |
Depiction |
this page was created by Special:FormEdit/Thesis, and can be edited by Special:FormEdit/Thesis/Software Defined Networking for tactical communications
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).