ELEC6255 IoT Networks
Coursework 2024/25
Assignment Set: Wednesday 09th October 2024, during lecture
Assignment Type: Individual coursework
Submission Deadline(s): Fri 13th December 2024, by 4pm (written report)
Feedback: We aim to return your mark and written feedback by Friday 17th January 2025, though will try to get this to you before the examination.
Mark Contribution: This assignment is worth 40% of your mark for ELEC6255
Required Effort: You should expect to spend up to 60 hours on this coursework
Examiners: Professor Geoff Merrett and Dr Alex Weddell
Learning Outcomes
Having successfully completed this coursework, you will be able to:
• demonstrate understanding of the principles of layered networking models, architectures and protocols which enable IoT networking
• use simulation to test and evaluate networking algorithms, protocols and architectures
• find, read and evaluate technical literature, and interpret standardisation documents
• communicate your technical work
Task Summary
A billionaire property owner has contacted you to provide an IoT smart lighting system for one of their mansions. They want you to investigate and provide some assurances about the reliability, latency, and additional energy consumption of such a system. Your task, in this coursework, is to use OMNeT++ to simulate, evaluate and analyse the performance of such a smart lighting network, based loosely around the ‘Hue’ smart lighting system.
This coursework is solely assessed through your individual report, which must be submitted along with your source code. The report must document your investigation into this system, using network simulation as a tool. This is not a ‘lab’ exercise: we are not posing an exhaustive list of specific questions that we want you to answer, we want you to perform your own research and investigation of a system within the scope of the coursework brief, and this is reflected in the marking scheme.
Full Task Description
Part 1: Model your Network
Your first task is to create an OMNeT++ network using the IEEE 802.15.4 PHY and DLL layers,and the AODV NET layer.
You can find the floor plan for the property that you are to model in Appendix 1 (listed by name), at the end of this document. You do NOT need to model this building perfectly, and can estimate the sizes and locations of rooms from the floor plan. You should arrange the following nodes throughout the property: 1 ‘hub’, 25 ‘smart light’, and 10 ‘light switch’ nodes. You can place them where you like, ensuring that you spread them out all around the property.
Each light switch controls all of the smart lights that are located in the same room as it. All packets sent from light switches get transmitted to the hub (possibly being routed via other light switches and/or smart lights). The hub uses a lookup table to identify the addresses of the smart lights that are located in the same room as the light switch, and then transmits packets to each of them (possibly being routed via other light switches and/or smart lights).
Your simulation should approximately (but realistically) represent the system that you are modelling. You should make appropriate and justifiable modelling decisions, including:
• Consider your choice of parameters in the physical layer (e.g. radio transmit power, sensitivity, data rates, frequency, bandwidth, etc). You could assume that the nodes will be based around the NXP JN516X radio module/system-on-chip. Consider your choice of an appropriate indoor wireless channel model, to model path loss and noise. Your chosen radio transmit power, channel model, hub location etc MUST ensure that multi-hop packet routing is required; it should not be possible for all nodes to be able to communicate directly (in asingle-hop) with the hub. You may want to put your hub at one side of the network (not the centre) to help with this. Make sure you set sensible dimensions for your simulated floorplan, and locate devices inappropriate locations.
• Consider how to model packet generation, and model/approximate the flow of data through the various types of node in the network. You can model light switch presses however you wish, in order to explore system operation. For example, do you think it is realistic that every light switch might be pressed once per second? Are they all pressed at the sametime?
• Consider how to model the energy properties (e.g. the capacity of the energy stores, their initial values, and the radio power consumption in various receive/transmit/idle states) of the different devices. The light switches are battery powered, while the hub and smart lights are powered from mains. Your nodes should NOT harvest energy (i.e. you should not model any energy generation).
• Consider how long your simulations should run for. You should simulate the network for a period of time sufficient to explore expected/typical behaviour. How many simulation runs do you need in order to be able to draw general conclusions?
You are strongly encouraged to look at what you are required to write about in Section 1 of your individual report, to ensure that you are making the necessary decisions and appropriately recording your justification for them.
Part 2: Check your Model and Simulation Setup
To check that you have made appropriate modelling decisions, and setup the simulation correctly, you should first check that the network performs as you would expect it to. Use OMNeT++ to simulate a small subset of the network (1 hub, 2 switches, 4 lights). All devices should be located sufficiently close to each other that they can communicate directly (i.e. multi-hop routing is not needed for this Part). Obtain simulation results for:
- Reliability: what proportion of the packets that are sent reach their destination? Based on your chosen floorplan dimensions and radio transmit power, is the resulting transmission range appropriate for your simulation?
- Latency: how long does it take for a packet to be received at its destination?
- Energy Consumption: How much power do the various nodes consume?
We encourage you to look at the what you need to write for Section 2 of your report. Consider whether or not you have enough results, or if you need to conduct more simulations.
Part 3. Analyse the Network Performance
Add all of the nodes back into the network (1 hub, 32 lights, 8 switches), located inappropriate places on your simulated floorplan. Your task is to analyse the performance of the full system you have modelled, in particular investigating the customer’s concerns,i.e. reliability, latency and energy consumption. This document does not provide a prescriptive or exhaustive set of questions for you to answer. However, you may wish to consider:
• Reliability: How often might a switch be pressed, but the light not respond? Is this acceptable? If anode fails, does the rest of the network recover and operate correctly?
• Latency: How long does it take for a light to turn on after pressing a switch? Is this an acceptable delay? What is the delay caused by; how might you improve it?
• Energy Consumption: How much energy do the nodes consume? How large would a switch’s battery need to be to last a year; is this realistic? Consider the energy consumption of switches and lights, but ignore the energy consumption of the hub.
Interpret your results; if the reliability/latency/power differs at different nodes in the network, what are the causes of this? How can you evidence this? Explore the routing table formed by the network. What does it look like, and does it change during simulation? Do the results depend on the type of node, or its distance/number of hops from the hub? Consider the different results you could obtain/plot to explore behaviour – for example, for energy consumption you could obtain data for Remaining Energy vs Time, or you could obtain results for the Remaining Energy at the end of the simulation. What is most appropriate?
Think about suitable statistical methods to use to analyse and evaluate your results. It is unlikely that the average (mean) alone will ‘tell the whole story’ , and you may wish to consider additional appropriate metrics (e.g. range, variance, standard deviation, interquartile range). Note that analysis is more than just presenting data/results and describing them. You should discuss why the behaviour is seen, and what is happening to cause this. You may need to do some reading of the technical literature and/or further experiments to answer this.
Deliverables and Marking Scheme
There is a single deliverable, marked out of 40, contributing 40% of the credit for this module.
Individual Report [total of 40 marks]
(due by 4pm on Friday 13th December 2024, online hand-in)
You should produce a written report documenting your investigation. The report must be single-spaced, single-column, use 12pt Times New Roman, and contain the following sections:
Section 1: Network Model [maximum of 1000 words]
You should include a screenshot showing the network topology, i.e. where various device types (light switches, smart lights and the hub) were spatially located. State and justify the physical dimensions of your floorplan (as defined in your .ned file).
You should then state and justify all of the modelling decisions (i.e. the models and parameters that you chose) that you made in Part A of the coursework. Justify how all of these were appropriate for the scenario that you are modelling. You should refer to the contents of your simulation’s .ini file (which you will include in Appendix 1), referring to individual lines (or ranges of lines) of this by line number. As a minimum, you should ensure that you state and justify all of the following:
• Radio and wireless channel
o Radio transmit power, sensitivity, data rate, frequency, bandwidth
o Channel background noise, path loss model, and associated parameters
• Power/energy
o Initial and nominal capacities of energy storage devices
o Power consumption models and parameters in various states
• Packet flows
o How did you configure the devices to model packet flows through the network?
o Packet generation start times, send intervals, packet lengths etc
• Simulation setup
o Simulation time/duration
o Number of simulation runs
Where appropriate, you should substantiate your modelling decisions using references to standards, datasheets, and the technical literature.
Section 2: Model Validation [maximum of 1000 words]
Present and explain how your results from Part 2 show that that packets are being appropriately sent, received and propagated through the small network at desired times, that energy is decreasing during the simulation, etc. For all of your results, you should consider ‘Is this what I expect?’ and ‘Why is this the case?’. For example:
• If only 50% of sent packets are received, why are some of them getting lost? If 100% of sent packets are received, what’s ensuring that none of them get lost? Do you have results that evidence that this is indeed what is causing this behaviour? Is this supported by the technical literature?
• If some nodes deplete their energy store more/faster than others, why is this? What influenceshow much energy they consume? Do you have results that show that this is indeed what is causing this behaviour? Is this supported by the technical literature?
Section 3: Network Analysis [maximum of 1000 words]
Present the results you obtained from simulating your full network in Part 3, and discuss the conclusions that you draw from them. Are your conclusions from Section 2 the same, or does the network behave differently at scale? Explore why the network performs as it does. Support your analysis and conclusions using the technical literature, where appropriate.
For both Section 2 and Section 3, do not underestimate the importance of results – this is where you explore various aspects of your simulation (e.g. energy, latency, lost/received packets). Make sure that you evidence your conclusions (i.e. use figures to show data/graphs/networks etc) with results, and that you explain them in detail (i.e. don’t leave the reader(s) to draw their own conclusions from your results). Label all axes on graphs, and state units where appropriate. We encourage you to replot data obtained from your simulations (e.g. in Excel), rather than just pasting OMNeT++ screenshots in your report (as these can be difficult to read and omit important information) .