Simulating Time Slotted Channel Hopping in Wireless Sensor Networks

From its-wiki.no

Jump to: navigation, search

Simulating Time Slotted Channel Hopping in Wireless Sensor Networks

by Mathias Utgård
Supervisor(s) Knut Øvsthus, Josef Noll
Due date 2018/11/01
Status Ongoing
Problem description: The growing trend of utilizing solutions featuring Wireless Sensor Networks (WSN) for various applications in industrial, medical and commercial domains introduces a set of challenges for the underlying protocols used to enable these networks. Sensor nodes in a WSN have a limited amount of energy available and are often deployed in unpredictable environments which makes energy efficiency and effective sharing of the wireless medium a very important concern. The IEEE 802.15.4e amendment to the IEEE 802.15.4 Standard for Low-Rate Wireless Networks aims to address the issues related to WSN for devices running the 802.15.4 stack, by introducing several general enhancements at the MAC layer and a new set of MAC “behavior modes”. These are different access schemes for the MAC layer that enable support for various applications with stringent requirements in terms of latency, reliability and timeliness (such as process automation and control, smart utility, and infrastructure monitoring networks). Time Slotted Channel Hopping (TSCH) is among the new MAC modes introduced in the 4e amendment. It is considered one of the more interesting additions of the amendment and is meant to satiate the requirements of various WSN applications such as those found in healthcare and industry, as well as in commercial domains. TSCH combines time slotted access with multi-channel and channel hopping capabilities, which allows for networks with higher throughput, deterministic latency and low energy usage, as well as increased network capacity with reduced impact of interference and multipath fading [2]. According to [3], TSCH is currently considered the de-facto technology for highly reliable, low-power wireless sensor networking technology, and is also found in commercial solutions like WirelessHART and ISA100.11a.
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 IoTSec
Depiction

this page was created by Special:FormEdit/Thesis, and can be edited by Special:FormEdit/Thesis/Simulating Time Slotted Channel Hopping in Wireless Sensor Networks

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).