From 9f280c29bb372407bb2ee06dc054271375216804 Mon Sep 17 00:00:00 2001 From: Michal Hanus Date: Sat, 30 Mar 2024 12:26:09 +0100 Subject: Osnova kapitol predelana do souboruu --- bakalarka.pdf | Bin 1725702 -> 4895283 bytes bakalarka.tex | 21 ++- text/chipy.tex | 445 +++++++++++++++++++++++++++++++++++++++++++++ text/hovnoZSemestralky.tex | 86 +++++++++ text/labina.tex | 83 +++++++++ text/mobil.tex | 1 + text/osnova.tex | 115 +----------- text/protokolyLPWAN.tex | 221 ++++++++++++++++++++++ text/reseni.tex | 445 --------------------------------------------- text/teorie.tex | 174 ------------------ text/uvod.tex | 2 + text/venek.tex | 20 ++ text/vysledky.tex | 86 --------- text/zhodnoceni.tex | 8 + 14 files changed, 882 insertions(+), 825 deletions(-) create mode 100644 text/chipy.tex create mode 100644 text/hovnoZSemestralky.tex create mode 100644 text/labina.tex create mode 100644 text/mobil.tex create mode 100644 text/protokolyLPWAN.tex delete mode 100644 text/reseni.tex delete mode 100644 text/teorie.tex create mode 100644 text/venek.tex delete mode 100644 text/vysledky.tex create mode 100644 text/zhodnoceni.tex diff --git a/bakalarka.pdf b/bakalarka.pdf index 2ecc2d8..1fc5d33 100644 Binary files a/bakalarka.pdf and b/bakalarka.pdf differ diff --git a/bakalarka.tex b/bakalarka.tex index 38238bd..29b47be 100644 --- a/bakalarka.tex +++ b/bakalarka.tex @@ -237,16 +237,19 @@ %%% Vložení souboru 'text/reseni' s popisem řešení práce % (rozdělte na více souborů či kapitol, pokud je vhodné) -\include{text/teorie} +\include{text/protokolyLPWA} -\include{text/osnova} +\include{text/chipy} -%%% Vložení souboru 'text/vysledky' s popisem vysledků práce -% (rozdělte na více souborů či kapitol, pokud je vhodné) -%include{text/vysledky} +\include{text/labina} + +\include{text/venek} + +\include{text/mobil} + +\include{text/zhodnoceni} -%%% Vložení souboru 'text/zaver' se závěrem -%include{text/zaver} +include{text/zaver} %%% Vložení souboru 'text/literatura' se seznamem zdrojů \include{text/literatura} @@ -259,10 +262,10 @@ %%% Vysázení seznamu příloh % (vynechejte, pokud máte dvě nebo méně příloh) -%\listofappendices +\listofappendices %%% Vložení souboru 'text/prilohy' s přílohami % Obvykle je přítomen alespoň popis co najdeme na přiloženém médiu -%\include{text/prilohy} +\include{text/prilohy} \end{document} diff --git a/text/chipy.tex b/text/chipy.tex new file mode 100644 index 0000000..5778e42 --- /dev/null +++ b/text/chipy.tex @@ -0,0 +1,445 @@ +\chapter{Communication protocols for IoT devices in 4G/5G mobile networks} + +\section{Current situation} + +It is estimated that currently (2023/2024) there are two actively connected Internet-of-Things (IoT) devices per each person living on the planet Earth and the number will almost double furthermore until 2030, reaching nearly 30 billion connected IoT devices worldwide\cite{statista}. + +At the same time, complexity of the IoT devices rises every year and so is their requirements on the underlying network infrastructure and protocols, originally designed predominantly for completely different mobile applications (text messages and voice / video streaming). Need for new IoT-related protocols started to be prominent with wide-spreading and anticipated new use-cases of IoT devices, for which \ac{GSM} and original \ac{LTE} networks were not originally intended and soon found unsuitable in terms of power efficiency, connection reliability and ability to accommodate billions of small devices with tiny average data rates. + +IoT devices today are not only simple single-purpose meteo sensors, but more and more frequently this category includes very complex vehicles and machinery, such as autonomous cars with multiple \ac{RADAR}/\ac{LIDAR} sensors or cooperative industrial robots, needing to communicate with the central command \& control facility and with each other in real time and with very high reliability. On the other hand large widespread of massive quantities of very low power devices in possibly critical application can also be expected. Related requirements on communication data volumes, response latency and network reliability far exceed capacity and technical possibilities of older mobile networks. Larger bandwidths, data speeds and lower latencies brought by 4G and especially 5G mobile networks are necessary for providing the appropriate working space for these new IoT devices. + +The necessary communication protocols for 4G and 5G mobile networks are being standardized under an umbrella of \ac{3GPP} - an association of national telecommunication standardization agencies and commercial partners. \ac{3GPP} has agreed upon and released several communication protocols (so-called „releases“) for the new generations of mobile networks, unfortunately with some ambiguities in their numbering and labeling. For example, Long-term evolution (LTE) was first introduced as a 3G technology standard but it later become a 4G standard. LTE was followed by LTE-Advanced labeled as „true 4G“ or 4.5G and LTE-Advanced Pro (LTE-A Pro) that is considered 5G but sometimes it is labeled as 4.9G \cite{nokia49g}. + +\section{4G IoT networks (LPWAN)} + +%IoT has become a large part of every day life and is now crucial to many both critical and non-critical applications. With planed shutdown of 2G and 3G networks [] it is important to look on protocols that are suposed to replace them and enhance their capabilities. + +Low-power wide-area network (LPWAN) protocols are 4G LTE wireless communication technologies that enable long-range transmission among IoT devices. LPWAN protocols are designed to meet the diverse requirements of IoT applications, mainly low power consumption, wide coverage range, capacity for large number of devices, and high reliability \cite{gsmalpwan}. + +\subsection{NB-IoT} +NB-IoT (Narrowband Internet of Things) is a cellular LPWAN standard that was developed by \ac{3GPP} for IoT devices and services in 2016 under \ac{3GPP} Release 13 and updated in 2017 with \ac{3GPP} Release 14 \cite{erf}. + +NB-IoT focuses on providing extended coverage, enhanced capacity, reduced complexity, and increased battery life for IoT devices that transmit small amounts of data infrequently \cite{rohdenbiot}. + +NB-IoT operates on the licensed spectrum and uses a subset of the LTE bands with peak data rate of 26 kb/s for downlink and 16.9 - 66 kb/s for uplink using Cat NB1. Newer standard of Cat NB2 allows maximum peak rate of 127 kb/s for downlink and 159 kb/s for uplink. NB-IoT uses orthogonal frequency division multiplexing (OFDM) modulation for downlink communication and single carrier frequency division multiple access (SC-FDMA) for uplink communication. + +Single NB-IoT communication channel corresponds to a single 180 kHz LTE frequency block \cite{ltebook}. This enables the following operation modes \cite{rohdenbiot}: + +\begin{itemize} + \item In-band operation - NB-IoT operates on standard LTE frequencies among other types of LTE communication + \item Guard band operation - Communication takes place in LTE guard-band without any other LTE communication + \item Stand alone operation - A theoretically possible scenario when mass adaption of technology will occur. This mode plans to utilize frequency allocation of current GSM networks. +\end{itemize} + +\begin{figure}[!h] + \begin{center} + \includegraphics[width=0.9\textwidth]{obrazky/nbiotmodes.png} + \end{center} + \caption[NB-IoT modes]{NB-IoT modes of operation \cite{rohdenbiot}} + \label{fig:nbiotmodes} +\end{figure} + +As of writing this thesis (December 2023) NB-IoT is supported in Czechia by all three national mobile operators. Vodafone is declaring universal coverage across the whole country \cite{vodafonemap}, T-Mobile in selected larger cities and O2 only in Moravian-Silesian region \cite{narowbandcoverage}. + + + +%NB-IoT is a cellular LPWAN standard that was developed by the 3rd Generation Partnership Project (\ac{3GPP}) for IoT devices and services and published in 2016 with \ac{3GPP} Release 13[] and its updated version in 2017 with \ac{3GPP} Release 14 []. NB-IoT operates on the licensed spectrum and uses a subset of the LTE bands with peak data rate of $26 kb/s$ for downlink and $16.9 \div 66\;kb/s$ for uplink using Cat NB1. Newer standart of Cat NB2 allow maximum peak rate of $127\;kb/s$ for downlink and $159\;kb/s$ for uplink. +%NB-IoT uses orthogonal frequency division multiplexing (OFDM) modulation for downlink communication and single carrier frequency division multiple access (SC-FDMA) for uplink communication. NB-IoT focuses on providing extended coverage, enhanced capacity, reduced complexity, and increased battery life for IoT devices that transmit small amounts of data infrequently. +% +%As of writing this thesis (December 2023) NB-IoT is supported in Czechia by all tree national mobile operators. Vodafone is declaring universal coverage in whole state \cite{vodafonemap}, T-Mobile in selected larger cities and O2 only in Moravian-Silesian region \cite{narowbandcoverage}. +% +%\subsubsection{Modes of operation} +% +%Single NB-IoT comunication channel correspondes to single 180 kHz LTE frequency block \cite{ltebook}. This enables following operation modes \cite{rohdenbiot}: +%\begin{itemize} +% \item In-band operation - NB-IoT operates in standart LTE frequencies among other types of LTE comunication +% \item Guard band operation - Communication occur in LTE guard-band where no prior LTE communication takes place +% \item Stand alone operation - A theoretically possible scenaraio when mass adaption of technology will occur. This mode plans to utilizate frequency allocation of current GSM networks +%\end{itemize} + +\subsection{LTE-M} + +LTE-M or LTE-MTC (Long-Term Evolution Machine Type Communication) is a second LPWAN protocol specified in \ac{3GPP} Release 12, with improved specification in Releases 13 and 14. Unlike NB-IoT, LTE-M uses more bandwidth (1.4 - 5 MHz) and is capable of higher communication speeds (1 - 4 Mbit/s for downlink and 1 – 7 Mbit/s for uplink). Another advantage of LTE-M over NB-IoT is an ability to function with movable objects (such as cars or drones). Higher bandwidths however lead to greater circuit complexity and possible higher energy consumption related to it \cite{nordiccompare}. + +As of writing this thesis (December 2023) LTE-M is covered in Czechia by O2 in 98.5 \% \cite{o2catm} and locally by Vodafone \cite{vodafonemap}. + +%LTE-M or LTE-MTC (Long-Term Evolution Machine Type Communication) is second LPWAN protocol specified in \ac{3GPP} release 12 with improved specification in releaes 13 and 14. +% +%Unlike NB-IoT LTE-M uses more bandwidth 1.4-5 MHz and is capable of higher comunication speeds (1-4 Mbit/s for downlink and 1-7Mbit/s for uplik depending on version). Another advantage is ability to function with movable objects (eg. cars or drones). Higher bandwidth leads to grater circuit complexity and higher energy consumption related to it. +% +%As of writing this thesis (December 2023) LTE-M is coverted in 98.5 \% in Czechina by O2 \cite{o2catm} and mostly by Vodafone \cite{vodafonemap}. + +\section{5G IoT networks} +5G implementation into the mobile networks can be achieved via two methods \cite{5gnruk}: + +\begin{itemize} + \item NSA (non-stand alone) - 5G features are achieved by adding new RAN (Radio Access Network) to existing 4G LTE core. This approach implements dynamic spectrum sharing and enables rapid deployment of enhanced mobile broadband in customer market without larger changes in existing infrastructure. + \item SA (stand alone) - LTE core and RAN are completely replaced with 5G ones. RAN can however still switch back to LTE air interface to ensure backward compatibility with non-5G devices. +\end{itemize} + +In 2018, \ac{3GPP} Release number 15 laid down 5G specification named 5G NR (New Radio). Unlike LTE-A Pro that has just added more features to 4G LTE and operated in LTE standards and channels, 5G NR introduced a new physical layer in air interface \cite{5gnruk}. + +5G NR tries to solve three key aspects of wireless technology \cite{5gnruk}: + +\begin{itemize} + \item eMBB (Enhanced Mobile Broadband): Data-intensive applications needing large bandwidth for primarily traditional end-user demand, like video streaming. This should be achieved by Gigabit LTE, massive MIMO, mmWave technologies, spectrum sharing techniques and advanced channel coding. + \item mMTC (Massive Machine Type Communications): Low-power and low-cost applications with small data volumes but potentially large number of these devices in a small footprint. It is built on LTE LPWAN protocols like LTE-M and NB-IoT, making them potentially a core part of 5G. + \item URLLC (Ultra-reliable and Low-latency Communication): Mission-critical applications traditionally possible only by direct wire connection, necessary for real-time control of autonomous vehicles and industrial machinery. +\end{itemize} + +As of December 2023, 5G IoT networks are not yet commercially available in Czechia. + +%%%%%% +\subsection{URLLC requirements} + +URLLC (Ultra-Reliable and Low-Latency Communication) is a new requirement for 5G networks for providing real-time communication protocols with very low delays and very high levels of reliability. First attempts to address this were introduced in 4G LTE HRLLC (Higher-Reliability and Low-Latency Communication) in \ac{3GPP} release 15 \cite{5gamericasurllc}. Until this point, aspects of latency and reliability were +dealt in separately and sometimes were in direct contradiction to each other (reliability was achieved with repeated data redundancy, which multiplied latency). Combination of these two aspects is however essential for several critical applications with different requirements, as shown in table \ref{tab:urllc}: + +\begin{table}[!h] + \begin{center} + \small + \begin{tabular}{|l|c|c|c|} + \hline + Scenario & E2E latency [ms] & Reliability [\%] & Data rate [Mbps] \\\hline\hline + Discrete automation & 10 & 99.99 & 10 \\\hline + Process automation – remote control & 60 & 99.9999 & 100 \\\hline + Process automation ‒ monitoring & 60 & 99.9 & 1 \\\hline + Process automation ‒ monitoring & 40 & 99.9 & 10 \\\hline + Electricity distribution – high voltage & 5 & 99.9999 & 10 \\\hline + Intelligent transport systems & 30 & 99.9999 & 10 \\\hline + \hline + \end{tabular} + \end{center} + \caption[Performance requirements for URLLC]{Performance Requirements for Low-Latency and High-Reliability Scenarios \cite{5gamericasurllc}} + \label{tab:urllc} +\end{table} + + +\subsection{Latency} +With such strict latency requirements, as low as 5 ms end-to-end latency, it is necessary to minimize air interface delay (to 1 ms or less). To achieve such low latency, intensive optimization of air data delivery is necessary. + +There are several possible approaches that can lead to reduced communication time and latency \cite{5gamericasurllc}: + +\begin{itemize} + \item Frequent transmission opportunities +Downlink control channel used to carry scheduling information for data transmission is not usually monitored by end device for power saving reasons. However to reduce the waiting time for delivering the control information, the end device could do this. For device to start uplink transmission, it needs to send a scheduling request (SR) that allocates a specific transmission slot. To minimize the waiting time, the periodicity of the SR resource configuration should reflect latency requirements. This can be further emphasized by flexible schedulling timing mainly in Time Division Dulex (TDD). + + \item Flexible transmission duration +This aspect is supported in 5G using larger subcarier spacing. This shortens slot duration and gives bigger oportunity for quicker communication establishment. + + \item Grant-free (or configured grant) uplink transmission +In cases with very low latency demand, grant-free uplink transition, specific periodic uplink resource for device can be arranged. End device in this scenario does not need to wait for scheduling request and at any time it has data it can transmit in this arranged slot without a need for dynamic grant. + +\end{itemize} + +Air interface is only partially responsible for total end-to-end latency. Remaining latency is caused by core network, internet network and particular server with which the device is communicating. This is to be solved by new concept of Edge computing. Edge computing is a possibility for a mobile operator or another entity to move services from a remote server closer to the device and to execute necessary task right in 5G core network \cite{3gppurllc}. + +Another method of lowering transport network latency is to avoid transport network completly. This is experimented in vehicle-to-vehicle (V2V) protocols and in non-IP based communication \cite{5gamericav2v}. + +\subsection{URLLC reliability optimization} + +In \ac{3GPP} Release 16, redundant transmission for high-reliability communication was introduced \cite{5gamericasurllc}. With this method, user packets are duplicated and simultaneously transferred to the receiver via two disjoint user plane paths. The redundant packets are then eliminated at the receiver side. This further avoids occasional fails in one path propagation and slims probability of exceding the delay requirements. Other changes can be made in 5G core parameters settings, like QoS Monitoring, dynamic division of Packet Delay Budget and enhancements of session continuity \cite{3gppurllc}. + +\chapter{IoT communication modules for 4G/5G networks} + +\section{Nordic Semiconductor nRF9160} + +\begin{figure}[H] + \begin{center} + \includegraphics[width=0.4\textwidth]{obrazky/nrfchip.png} + \end{center} + \caption[Nordic nRF9160 SiP]{Nordic nRF9160 SiP\cite{nrf91desc}} + \label{fig:sipfront} +\end{figure} + +nRF9160, made by Nordic Semiconductor, is a System-in-Package (SiP) combining multiple integrated circuits into a single LGA package (10x16x1.04 mm in size), functioning as an entire computing system: +\begin{itemize} + \item Application Processor with Arm Cortex-M33 core at 64 MHz, 1 MB flash memory, 256 kB RAM and usual microcontroller peripherials - 4x SPI/UART/I2C, 4x PWM, PDM, I2S, 12-bit ADC @ 200 ksps, 3x timer, 2x RTC, WDT. + \item LTE modem (700 – 2000 MHz) operating in the both LPWAN modes: LTE-M (300/375 kbps DL/UL) and NB-IoT (30/60 kbps DL/UL), supporting IPv4/IPv6 internet layer with optional security using TCP/TLS in transport layer and modem firmware upgrades via FOTA (firmware over the air). + \item Radio-Frequency Front End (RFFE) + \item GNSS receiver + \item Power management integrated circuits. +\end{itemize} + +nRF9160 is certified for global operations in multiple LTE bands, as shown in the figure below. For European operations, bands B1, B3, B8, B20 and B28 are available for both NB-IoT and LTE-M modes. Hardware security is strengthened with ARM TrustZone technology protecting against uploading unofficial or malicious firmware. TrustZone also protects from firmware attacks like memory and peripheral spoofing \cite{armtrustzone}. nRF9160 furthermore employs Arm CryptoCell solution optimized for high-performance cryptography for energy-constrained devices. + +Both SIM and eSIM are supported for connection and authentication with mobile network operators \cite{nrf91desc}. nRF9160 can be powered from relatively large range of voltages - from 3.0 to 5.5 V, allowing to directly connect Li-ion or Li-Po type batteries or USB-compatible power supplies. + +nRF9160 is manufactured in 3 modifications, sharing the same 127-pin LGA package, but differing in LTE modem capabilities, as shown in table \ref{tab:nrfchips} below. + +\begin{table}[!h] + \begin{center} + \small + \begin{tabular}{|l|l|} + \hline + Name & RF features \\ \hline + \hline + nRF9160-SICA & Only LTE-M \\ \hline + nRF9160-SIBA & Only NB-IoT \\ \hline + nRF9160-SIAA & LTE-M, NB-IoT and GNSS \\ \hline + \end{tabular} + \end{center} + \caption[nRF9160 product options]{nRF9160 LGA modules options and their limitations. \cite{nrf91datasheet}} + \label{tab:nrfchips} +\end{table} + +\subsection{Modules with nRF9160} + +There are several modules and development kits available with nRF9160 chipset, originating from Nordic Semiconductor, as well as from other vendors. + +\subsubsection{nRF9160 DK} + +\begin{figure}[H] + \begin{center} + \includegraphics[width=0.9\textwidth]{obrazky/nrf9160DKfront.png} + \end{center} + \caption[Nordic nRF9160DK]{Nordic nRF9160DK front view\cite{nrf91dkdesc}} + \label{fig:dkfront} +\end{figure} + +nRF9160 DK is an official pre-certified development kit for nRF9160 made and supported by Nordic Semiconductor. It is equipped with LTE-M/NB-IoT antenna, GNSS antenna, SIM connector, eSIM card from iBasis preloaded with 10 MB data. All peripherial GPIO pins of nRF9160 are available through connectors and headers compatible with Arduino Uno Rev3 form factor, there are also 4 on-board LEDs, 2 buttons and 2 switches connected to the application processor GPIO. The board also includes nRF52840 board controller sharing the peripherials and allowing to build a Bluetooth Low Energy gateway. Powering and communication with PC are arranged via USB (virtual COM) port. Programming and debugging is enabled through the Segger J-Link OB. The nRF9160 DK is supported by a full suite of development software tools by Nordic Semiconductor, free to download and use commercially \cite{nrf91dkdesc}. + +\subsubsection{Nordic Thingy:91} + +\begin{figure}[H] + \begin{center} + \includegraphics[width=0.4\textwidth]{obrazky/Thingy91_board.png} + \end{center} + \caption[Nordic Thisgy:91]{Nordic nRF9160DK front view\cite{thingydesc}} + \label{fig:thingy} +\end{figure} + +Nordic Thingy:91, also made by Nordic Semiconductor, is a compact small-factor module used as a rapid prototyping battery-operated platform, containing LTE-M/NB-IoT/GNSS, Bluetooth LE and NFC antennas, User-programmable button and RGB LEDs, environmental sensor for temperature, humidity, air quality and air pressure, plus a color and light sensor, low-power accelerometer and high-g accelerometer, rechargeable Li-Po battery with 1350 mAh capacity +\cite{thingydesc}. + +\subsubsection{NimbeLink Nano Global} + +\begin{figure}[H] + \begin{center} + \includegraphics[width=0.6\textwidth]{obrazky/NimbeLink-Nano.png} + \end{center} + \caption[NimbeLink Nano Global LTE-M]{NimbeLink Nano Global LTE-M\cite{nimbelinkdesc}} + \label{fig:nimbe} +\end{figure} + +NimbeLink Nano Global LTE-M (Skywire Nano Development Kit, NL-SWN-LTE-NRF9160), made by Airgain, is an add-on modem with nRF9160 and two U.FL antenna connectors, attached to a base board NL-SWNDK providing SIM holder, USB powering and distributition of GPIO pins to peripherial headers. The board has been originally certified only for Verizon networks +\cite{nimbelinkdesc}. + +\subsubsection{LN60E} + +\begin{figure}[H] + \begin{center} + \includegraphics[width=0.6\textwidth]{obrazky/LN60E.png} + \end{center} + \caption[LN60E]{LN60E\cite{ln60desc}} + \label{fig:ln60} +\end{figure} + +LN60E is a simple modem provided by Fansel, having a U.FL antenna connector, SIM connector and M.2 card connector for nRF9160 peripherials +\cite{ln60desc}. + +\subsubsection{Pebble Tracker} + +\begin{figure}[H] + \begin{center} + \includegraphics[width=0.6\textwidth]{obrazky/pebble.jpg} + \end{center} + \caption[Pebble Tracker]{Pebble Tracker\cite{pebbledesc}} + \label{fig:} +\end{figure} + +Pebble Tracker, a crowdfunded module made by IoTex, is a battery operated IoT prototyping platform based on a board with nRF9160, Bosch BME680 humidity/pressure/temperature/air quality sensor, ICM-42605 3-axial gyroscope/accelerometer, AMS TSL2572 ambient light sensor, SIM slot, OLED display, in a compact plastic case +\cite{pebbledesc} + +\subsubsection{Icarus SoM} + +\begin{figure}[H] + \begin{center} + \includegraphics[width=0.6\textwidth]{obrazky/icarus-som.png} + \end{center} + \caption[Icarus SoM]{Icarus SoM\cite{icarusdesc}} + \label{fig:icarus} +\end{figure} + +Icarus SoM, made by Actinius, is a simple module with U.FL antenna connectors for GNSS and LTE, eSIM and accelerometer, with spare GPIO pins headed to PCB edge connectors +\cite{icarusdesc}. + +\subsubsection{Icarus Bee} + +\begin{figure}[H] + \begin{center} + \includegraphics[width=0.6\textwidth]{obrazky/icarus-bee.png} + \end{center} + \caption[Icarus Bee]{Icarus Bee\cite{icarusbeedesc}} + \label{fig:icarusbee} +\end{figure} + +Icarus Bee, made by Actinius, expands the above-mentioned Icarus SoM module with a board connecting it to 64 Mbit flash memory, RGB LED, button, SIM connector and GPIO to pin headers +\cite{icarusbeedesc}. + +\subsubsection{Icarus IoT Board v2} + +\begin{figure}[H] + \begin{center} + \includegraphics[width=0.6\textwidth]{obrazky/icarus-iot.png} + \end{center} + \caption[Icarus IoT]{Icarus IoT Board v2\cite{icarusiotdesc}} + \label{fig:icarusiot} +\end{figure} + +Icarus IoT Board v2, made by Actinius, contains nRF9160 chipset on a board with USB connector, U.FL antenna connectors for LTE and GNSS, LiPo charger, eSIM and nano SIM connector, accelerometer and SPI flash memory, with pin headers compatible with Adafruit Feather footprint +\cite{icarusiotdesc}. + +\subsubsection{nRF9160 Feather} + +\begin{figure}[H] + \begin{center} + \includegraphics[width=0.6\textwidth]{obrazky/nrf9160_feather.jpg} + \end{center} + \caption[nRF9160 Feather]{nRF9160 Feather\cite{featherdesc}} + \label{fig:feather} +\end{figure} + +nRF9160 Feather, made by CircuitDojo, is a design with pin headers compatible with Adafruit Feather footprint and a functionality similar to the Icarus IoT Board v2 +\cite{featherdesc}. + +\subsubsection{SparkFun Thing Plus nRF9160} + +\begin{figure}[H] + \begin{center} + \includegraphics[width=0.7\textwidth]{obrazky/sparkfun2.jpg} + \end{center} + \caption[SparkFun Thing Plus nRF9160]{SparkFun Thing Plus nRF9160\cite{sparkfundesc}} + \label{} +\end{figure} + +SparkFun Thing Plus nRF9160, made by SparkFun, is another board with Adafruit Feather footprint and similar to Icarus IoT Board v2 described above, however with USB-C connector and providing 4 MB SPI flash memory, LiPo charger, low power RTC, a button, a LED, two U.FL antennas for LTE and GNSS +\cite{sparkfundesc}. + +\subsubsection{Connexio Stratus} + +\begin{figure}[H] + \begin{center} + \includegraphics[width=0.4\textwidth]{obrazky/connexio.jpg} + \end{center} + \caption[Connexio Stratus]{Connexio Stratus\cite{connexiodesc}} + \label{} +\end{figure} + +Connexio Stratus, a crowd-funded development board, has a similar design to the SparkFun board above, adding SIM with 500 MB of mobile data, energy harvesting integrated circuit for Li-ion and NiMH battery charging, LiPo battery connection and charging, 2 push-buttons, 1 LED, SHT4x temperature and humidity sensor, LIS2DH 3-axial accelerometer +\cite{connexiodesc}. + +Comparisons of the main parameters of the most common nRF9160 boards is provided in the following table \ref{tab:nrfmodules} taken from \cite{connexiodesc}: +\begin{table}[H] + \begin{center} + \scriptsize + \begin{tabular}{|l|l|l|l|l|l|l|l|} + \hline + & Stratus & Thingy:91 & Icarus & Feather & Pebble Tracker & Thing Plus \\\hline + \hline + Manufacturer & Conexio & Nordic Semi & Actinius & CircuitDojo & IoTex & Sparkfun \\\hline + Total Pins & 33 & 8 & 28 & 28 & None & 28 \\\hline + I/O Pins & 26 & 8 & 21 & 20 & None & 20 \\\hline + Energy Harvester & Yes & No & No & No & No & No \\\hline + Accelerometer & Yes & Yes & Yes & Yes & Yes & Yes \\\hline + Environmental Sensors & Yes & Yes & No & No & Yes & No \\\hline + Onboard LEDS & 2 & 1 RGB & 1 RGB & 2 & 1 RGB & 2 \\\hline + Sensor power gating & Yes & No & No & No & No & No \\\hline + Power switch & Yes & Yes & No & No & Yes & No \\\hline + Lipo battery charger & Yes & No & Yes & Yes & No & Yes \\\hline + USB interface & Yes & Yes & Yes & Yes & Yes & Yes \\\hline + Debugging connector & Yes & Yes & No & No & Yes & No \\\hline + Prepaid Cellular data & 500 MB & 10 MB & 10 MB & 10 MB & No & 10 MB \\\hline + Cellular data validity & 10 years & N/A & N/A & N/A & N/A & N/A \\\hline + SMS Data & 250 & No & No & No & No & No \\\hline + Dedicated sensor shield & Yes & No & No & No & No & No \\\hline + VS Code dev. extension & Yes & Yes & No & No & No & No \\\hline + Breadboard compatible & Yes & No & Yes & Yes & No & Yes \\\hline + Edge Impulse ready & Yes & Yes & No & No & No & No \\\hline + Memfault ready & Yes & No & No & No & No & No \\\hline + Golioth ready & Yes & No & No & Yes & No & No \\\hline + Open-source & HW+SW & HW+SW & No & HW+SW & No & HW+SW \\\hline + Dimension [mm] & 50.8x22.8 & 58.8x58.5 & 50.8x22.8 & 50.8x22.8 & 53x35 & 58.42x22.86 \\\hline + Weight & \~5 g & 61 g & \~5 g & \~5 g & 10 g & \~5 g \\\hline + Price (USD) & \$159 & \$126.25 & \$115 & \$99 & \$215 & \$129.95 \\\hline + \end{tabular} + \end{center} + \caption[Comparation of nRF9160 modules]{Comparation of nRF9160 main modules} + \label{tab:nrfmodules} +\end{table} + +%%------------------------------------------------------------------------------------------- + +\section{Quectel RM520N} + +\begin{figure}[h!] + \begin{center} + \includegraphics[width=0.6\textwidth]{obrazky/RM520N.png} + \end{center} + \caption[Quectel RM520N]{Quectel RM520N series front view\cite{rm520ndatasheet}} + \label{} +\end{figure} + +RM520N is a 5G Sub-6GHz IoT module, made by Chinese company Quectel, optimized for IoT and eMBB applications with worldwide spectrum coverage, but capable of also 3G/4G multi-mode operation. The module is made in an M.2 form factor (30 x 52 x 2.3 mm) with 4 antenna connectors and is compatible with \ac{3GPP} Release 16 specification, supporting both 5G NSA (data rates: 3.4 Gbps DL / 550 Mbps UL) and SA modes (data rates: 2.4 Gbps DL / 900 Mbps UL). + +The RM520N is an industrial-grade module for industrial and commercial applications. It should cover nearly all the mainstream carriers worldwide and support Qualcomm® IZat location technology Gen9C Lite (GPS, GLONASS, BDS and Galileo). The integrated GNSS receiver simplifies the product design. + +It communicates using USB and PCIe drivers provided by Quectel for Windows 7 or higher, Linux, and Android. Main anticipated usage are industrial routers, home gateways, laptops / tablet PCs as well as IoT applications \cite{rm520ndatasheet}. + +The module comes in two variants: RM520N-GL with global coverage and RM520N-EU with EU frequency regulatory spectrum. + +\subsection{Modules with RM520N} + +Development support for RM520N modules is provided by a Chinese company Waveshare \cite{waveshare1}\cite{waveshare2} +making several hardware kits for rapid development and implementation with RM520N and having a distribution network across EU (e.g. \url{https://rlx.sk/sk/vyhladavanie?controller=search&s=RM520N}) + +\subsubsection{Dongle} +\begin{figure}[H] + \begin{center} + \includegraphics[width=0.6\textwidth]{obrazky/rmdongle.jpg} + \end{center} + \caption[Waveshare dongle]{Waveshare dongle\cite{rmdongle}} + \label{} +\end{figure} + +5G DONGLE module \cite{rmdongle} +providing simple expansion board with 4 SMA antenna connectors, nano SIM card holder, M2 connector for RM520N, heatsink and USB3.1 port for connecting to PC or Raspberry Pi. + +\subsubsection{Raspberry Pi HAT} + +\begin{figure}[H] + \begin{center} + \includegraphics[width=0.6\textwidth]{obrazky/rmpi.jpg} + \end{center} + \caption[Waveshare dongle]{Waveshare dongle\cite{rmpi}} + \label{} +\end{figure} + +5G HAT for Raspberry Pi \cite{rmpi} +, with a case for Raspberry Pi 3B/4B, onboard USB3.1 and USB-C ports, 2x SIM card slot, 4 antennas, 3A power supply circuit. + +\subsubsection{USB/Ethernet converter} + +\begin{figure}[H] + \begin{center} + \includegraphics[width=0.6\textwidth]{obrazky/rmeth.jpg} + \end{center} + \caption[USB/Ethernet converter]{USB3.1 / Gigabit Ethernet converter to 5G\cite{rmeth}} + \label{} +\end{figure} + +USB3.1 / Gigabit Ethernet converter to 5G \cite{rmeth} +capable to connect RM520N module to its M2 connector header and acting as a 5G communication bridge to PC, industrial control hosts, Raspberry Pi, ethernet switch or router using their USB3.1 or Ethernet connections. + +\subsubsection{Module form Jetson Nano} + +\begin{figure}[H] + \begin{center} + \includegraphics[width=0.6\textwidth]{obrazky/rmjet.jpg} + \end{center} + \caption[Module for Jetson Nano]{Comunication module for Jetson Nano\cite{rmjet}} + \label{} +\end{figure} + +Communication module for Jetson Nano \cite{rmjet} +- interface with M2 connector, USB3.1 port, audio jack and decoder, SIM card slot, 40-pin GPIO extension header for direct connection to Jetson Nano, 4 antennas. diff --git a/text/hovnoZSemestralky.tex b/text/hovnoZSemestralky.tex new file mode 100644 index 0000000..c94f8ce --- /dev/null +++ b/text/hovnoZSemestralky.tex @@ -0,0 +1,86 @@ +\chapter{Practical demonstration} + +For practical demonstration of an IoT device with 4G/5G connectivity, a 4G development kit nRF9160 DK was selected. Demonstration of 5G connectivity could not be made due to a delay with delivery of the ordered Quectel module. + +Practical demonstration of an IoT device with LTE-M connectivity was made on an example of a combined burglary and fire alarm system with 4 sensors, transferring data to a remote cloud server via MQTT protocol, simulating a data transfer to a central security panel. + +\section{Hardware} + +nRF9160 DK development kit was adapted with an add-on board made from a universal line PCB with headers compatible to Arduino Uno form-factor fitting to nRF9160 DK headers. The add-on PCB contained connections for four sensors: + +\begin{itemize} + \item Hall effect sensor Texas Instruments DRV5033 \cite{haldatasheet}, with open-drain output (for pulled-up digital input) pulled down by an external magnetic field and simulating door/window switch, connected to GPIO pin P0.19. + \item analog thermometer Texas Instruments LM35 \cite{tempdatasheet}, with an analog output linearly corresponding to 10 mV for each oC above 0 oC, connected to GPIO pin P0.17. + \item passive infrared (PIR) motion sensor Hadson Technology HC-SR501 \cite{pirdatasheet} with digital output (3,3 VDC output reduced to 3 VDC level by a voltage divider), connected to GPIO pin P0.16. + \item sensor for combustible gases Pololu MQ-2 \cite{gasdatasheet}, with an analog ouput reduced by a voltage divider to avoid exceeding 3 VDC threshold, connected to GPIO pin P0.18. +\end{itemize} + +\begin{figure}[!h] + \begin{center} + \includegraphics[width=0.5\textwidth]{obrazky/ezsschema.png} + \end{center} + \caption[Overview of security and fire alarm]{Overview of security and fire alarm board} + \label{fig:ezsschema} +\end{figure} + +\begin{figure}[!h] + \begin{center} + \includegraphics[width=0.5\textwidth]{obrazky/ezspcb.png} + \end{center} + \caption[Schematic of security and fire demo]{Schematic of security and fire alarm demo} + \label{fig:ezspcb} +\end{figure} + + +\begin{figure}[!h] + \begin{center} + \includegraphics[width=0.9\textwidth]{obrazky/pcbphoto.jpg} + \end{center} + \caption[PCB schematic of alarm demo board]{PCB schematic for alarm demo} + \label{fig:ezsreal} +\end{figure} + +\newpage + +\section{Firmware tools} + +nRF Connect SDK was used as a software platform for the demo application. nRF Connect SDK is a unified software development kit for building products based on all Nordic nRF Series wireless devices. It integrates the Zephyr RTOS and wide range of samples, application protocols, protocol stacks, libraries and hardware drivers \cite{zephyrpp}. + +It offers a single code base for all Nordic devices and software components. It simplifies porting modules, libraries and drivers from one application to another, thus reducing development time. nRF Connect SDK is publicly available under OpenSource license, offers source code management with Git and has free nRF Connect for Visual Studio Code IDE support. Zephyr RTOS furthemore provides extensive amount of libraries including standardized access to basic peripheries, IP stack and MQTT library \cite{nrfsdk}. + +MQTT is a lightweight, publish-subscribe protocol that enables efficient and reliable communication between devices in the IoT domain. MQTT is based on a broker-client architecture, where a broker is a server that receives and routes messages from multiple clients, and a client is any device that can publish or subscribe to a topic. A topic is a hierarchical identifier that defines the content and scope of a message\cite{mqtt}. + +This firmware is based on nRF Connect SDK example named Simple MQTT\cite{nrfmqtt}. + +\section{Firmware outline} + +\subsection{LTE network connection} + +First task for the demo firmware is an establishment of a connection to LTE network. This is mostly handled by function \texttt{modem\_configure()}, which turns off power saving modes for better responsivity and calls HAL function \texttt{lte\_lc\_init\_and\_connect()}. + +\texttt{lte\_lc\_init\_and\_connect()} takes all modem settings from text config files transferred to macros by Kconfig. This ilustrates a possibility of cross-platform or regionally independent application, where only the config files for given platform or region are needed to be changed. + +\subsection{ADC configuration} +When connection with LTE network is successfully established, ADC is configured. Two analog input channels are used in this demo - AIN4 on P0.17 pin connected to LM35 temperature sensor and AIN5 on P0.18 connected to MQ-2 combustible gas sensor. For both channels, \texttt{adc\_channel\_cfg} structs are initialized and channels are set to 10bit resolution, internal 0.6 V reference voltage and 1/2 divider using \texttt{adc\_channel\_cfg()}, setting channels voltage range to 1.2 V. Both channels (if they are enabled by the button configuration) are then sampled in set interval using a custom fuction \texttt{adc\_sample()} and printed to USB serial. + +\subsection{Digital inputs and outputs} +For ease of implementation, digital sensors on GPIO pins P0.16 (DRV5033) and P0.19 (PIR) were added to the device tree as additional development kit buttons. This avoided the need for their own separate initialization and reading codes. + +These digital input sensors are then processed as buttons using callback handler \texttt{button\_handler()}. This function is called with bitmasks \texttt{button\_states} and \texttt{has\_changed}, making it ease to figure state change for these two sensors. + +Two buttons and two switchers are used for optionally disabling the corresponsing sensors. This is executed in \texttt{button\_handler()}. + +Four on-board LEDs are used for local signalization of status of PIR sensor (LED1) and Hall effect sensor (LED2), as well as over-threshold values of temperature (LED3) and combustible gas (LED4) sensors. + +\subsection{MQTT} + +Communication with MQTT server is done by zephyr/net/mqtt.h library. Connection with the server is attempted after LTE and sensors setup with function \texttt{mqtt\_connect()}. +Publishing of message is achieved by function \texttt{mqtt\_publish()} upon a digital sensor is activated or analog sensor exceeds the set threshold value. Example of the MQTT communication sent to a virtual server is shown in figure \ref{fig:mqttcom}. + +\begin{figure}[!h] + \begin{center} + \includegraphics[width=0.2\textwidth]{obrazky/mqttcom.png} + \end{center} + \caption[Demo MQTT communication]{Sample of resulting MQTT communication} + \label{fig:mqttcom} +\end{figure} diff --git a/text/labina.tex b/text/labina.tex new file mode 100644 index 0000000..1e52302 --- /dev/null +++ b/text/labina.tex @@ -0,0 +1,83 @@ +\chapter{Laboratory testing} + +\textit{Každá section jak protokol, Co chci změřit, Fyzika - princip toho co měřím, čím to měřím, zapojení měřící techniky, tabulky, graf} + +\section{Comunication range} + +One of main considaritation when choosing a IoT platfrom is communication range. Main source of attenuation of radio energy caused by electric field dispersion/diffusion of electric field. This effect if best desribed by \ac{FSPL}: + +\begin{equation} + FSPL=\left( \frac{4 \pi d}{\lambda} \right) ^2 +\end{equation} + +Signal attenuation is also dependent on directivity of antennas and loss on connectors and \textbf{electrical wiring}. When antenna and transmition total \textbf{gain} is constant and can be added to equation like this: + +\begin{equation} + A = D_{ANT} \cdot A_{RX} \cdot \left( \frac{4 \pi d}{\lambda} \right) ^2 +\end{equation} + +Where $D_{ANT}$ is directivity of antenna and $A_{RX}$ is total loss from \ac{RF} connector to \ac{LTE} modem. These must be accounted to only when maasuring on directly on LTE modem. + +This can be coverted to simplify calculation to decibel form: + +\begin{equation} + A = D_{ANT}^{[dB]} + A_{RX}^{[dB]} + 10 \cdot \log_{10} \left( \frac{4 \pi d}{\lambda} \right) ^2 +\end{equation} + +From this a maximal range can be simulated using \ac{RF} attenuators in laboratory enviroment by converting + +\begin{equation} + d = A_{max} +\end{equation} + +Dosah zásvisí na vzdálenosti, v ideálních podmínkách line of sight Free-space path loss + +Popis Free-space path loss, teorie, vzorečky + +Technika - variable attenuator, + +Tabulka utlum , km ve free-space , teoreticka sila signalu , signal na vstupu podle FW , packet drop / BER + +\section{Noise immunity - reliability} + +Noise makes signal bad, reciver much sad. + +Teorie, vzorecky, Bit error rate, Added white gausian noise + +Teoreticke vypocty pro NB-IoT, LTE-M, DECT NR+ + +Technika zdroj šumu, směšovač, + +Pro jednotlivé AWGN a CNR carier noise ratio +Tabulka utlum , km ve free-space , teoreticka sila signalu , signal na vstupu podle FW , packet drop / BER , spotřeba + +\section{Power consumtion} + +Globalni oteplovani bad, small battery good + +Technika Power Profiler Kit II + +\section{Latency} + +Pro jednotlivé AWGN a CNR carier noise ratio +Tabulka utlum , km ve free-space , teoreticka sila signalu , signal na vstupu podle FW , packet drop / BER , spotřeba , latence + +Experimentální ověření NB-IoT, LTC-M, DECT NR+: +\begin{itemize} + \item dosah - popis cesty šíření ve volném prostoru, odkaz na teoretický výpočet útlumi vzdáleností ve volném prostředí ve vzduchu. Popis atenuátoru. + \item spotřeba - variabilní snižování síly signálu, popis Power Profiler Kit II + \item přenosová rychlost - primárně pro DECT, praktická superhurbá přenosová rychlost UDP Byty/(čas od konce do začátku sleep) + \item odolnost vůči šumu - VF generátor šumu, teorie +\end{itemize} + +Experimentální ověření DECT NR+ navíc: +\begin{itemize} + \item spolehlivost - + \item latence - +\end{itemize} + +Teorie mereni - Náhradní modely prostředí. Degradace signálu. + +Popis experimentální instrumentace a sestav. + +Spotřeba, packet drop, rychlost, latence závislá na útlumu (popř. intenzita bílého šumu) (vsechny protokoly) diff --git a/text/mobil.tex b/text/mobil.tex new file mode 100644 index 0000000..e8a2588 --- /dev/null +++ b/text/mobil.tex @@ -0,0 +1 @@ +\chapter{Field testing of mobile capabilities of nRF916X-DK} diff --git a/text/osnova.tex b/text/osnova.tex index a4c0c82..0c31966 100644 --- a/text/osnova.tex +++ b/text/osnova.tex @@ -5,13 +5,13 @@ \item doplnit grafy nárůstu IoT zařízení \end{itemize} -\section{Established communication standards for IoT devices} +\paragraph{Established communication standards for IoT devices} \begin{itemize} \item doplnit GSM, LoRa, Zigbee, Sigfox, Wifi, ESP32, 433 MHz \end{itemize} -\section{4G IoT network standards (LPWAN)} +\paragraph{4G IoT network standards (LPWAN)} \begin{itemize} \item převzít kapitolu 1.2. @@ -22,14 +22,14 @@ https://blog.nordicsemi.com/getconnected/what-is-cellular-iot https://www.nordicsemi.com/Products/Wireless/Low-power-cellular-IoT/Development-tools?lang=en\#infotabs -\section{5G IoT network standards} +\paragraph{5G IoT network standards} \begin{itemize} \item převzít kapitolu 1.3, doplnit 5G trojuhelník \item zestručnit kapitolu 1.3.1 URLLC, bez zbytečných detailů \end{itemize} -\section{DECT NR+ standard for 5G IoT networks} +\paragraph{DECT NR+ standard for 5G IoT networks} \begin{itemize} \item Stary DECT a IP telefony, pasmo, HW vrstva, NR a teorie prenosovych rychlosti @@ -82,113 +82,6 @@ https://blog.nordicsemi.com/getconnected/the-next-step-for-m2m-communications \end{itemize} -\chapter{Laboratory testing} - -\textit{Každá section jak protokol, Co chci změřit, Fyzika - princip toho co měřím, čím to měřím, zapojení měřící techniky, tabulky, graf} - -\section{Comunication range} - -One of main considaritation when choosing a IoT platfrom is communication range. Main source of attenuation of radio energy caused by electric field dispersion/diffusion of electric field. This effect if best desribed by \ac{FSPL}: - -\begin{equation} - FSPL=\left( \frac{4 \pi d}{\lambda} \right) ^2 -\end{equation} - -Signal attenuation is also dependent on directivity of antennas and loss on connectors and \textbf{electrical wiring}. When antenna and transmition total \textbf{gain} is constant and can be added to equation like this: - -\begin{equation} - A = D_{ANT} \cdot A_{RX} \cdot \left( \frac{4 \pi d}{\lambda} \right) ^2 -\end{equation} - -Where $D_{ANT}$ is directivity of antenna and $A_{RX}$ is total loss from \ac{RF} connector to \ac{LTE} modem. These must be accounted to only when maasuring on directly on LTE modem. - -This can be coverted to simplify calculation to decibel form: - -\begin{equation} - A = D_{ANT}^{[dB]} + A_{RX}^{[dB]} + 10 \cdot \log_{10} \left( \frac{4 \pi d}{\lambda} \right) ^2 -\end{equation} - -From this a maximal range can be simulated using \ac{RF} attenuators in laboratory enviroment by converting - -\begin{equation} - d = A_{max} -\end{equation} - -\newpage - -Dosah zásvisí na vzdálenosti, v ideálních podmínkách line of sight Free-space path loss - -Popis Free-space path loss, teorie, vzorečky - -Technika - variable attenuator, - -Tabulka utlum , km ve free-space , teoreticka sila signalu , signal na vstupu podle FW , packet drop / BER - -\section{Noise immunity - reliability} - -Noise makes signal bad, reciver much sad. - -Teorie, vzorecky, Bit error rate, Added white gausian noise - -Teoreticke vypocty pro NB-IoT, LTE-M, DECT NR+ - -Technika zdroj šumu, směšovač, - -Pro jednotlivé AWGN a CNR carier noise ratio -Tabulka utlum , km ve free-space , teoreticka sila signalu , signal na vstupu podle FW , packet drop / BER , spotřeba - -\section{Power consumtion} - -Globalni oteplovani bad, small battery good - -Technika Power Profiler Kit II - -\section{Latency} - -Pro jednotlivé AWGN a CNR carier noise ratio -Tabulka utlum , km ve free-space , teoreticka sila signalu , signal na vstupu podle FW , packet drop / BER , spotřeba , latence - -Experimentální ověření NB-IoT, LTC-M, DECT NR+: -\begin{itemize} - \item dosah - popis cesty šíření ve volném prostoru, odkaz na teoretický výpočet útlumi vzdáleností ve volném prostředí ve vzduchu. Popis atenuátoru. - \item spotřeba - variabilní snižování síly signálu, popis Power Profiler Kit II - \item přenosová rychlost - primárně pro DECT, praktická superhurbá přenosová rychlost UDP Byty/(čas od konce do začátku sleep) - \item odolnost vůči šumu - VF generátor šumu, teorie -\end{itemize} - -Experimentální ověření DECT NR+ navíc: -\begin{itemize} - \item spolehlivost - - \item latence - -\end{itemize} - -Teorie mereni - Náhradní modely prostředí. Degradace signálu. - -Popis experimentální instrumentace a sestav. - -Spotřeba, packet drop, rychlost, latence závislá na útlumu (popř. intenzita bílého šumu) (vsechny protokoly) - - -\chapter{Field application testing of nRF9161-DK} - -Externí interference: mikrovlnka… - -\begin{itemize} - \item Urban environment (industrial plant, underground spaces, bunkers) - \begin{itemize} - \item co testovat? - \item nějaká aplikační deska pro „průmysl“? - \end{itemize} - \item Rural environment (open field, forest) - - \item Herd monitoring application (Temp+RH, Accel, Light, GPS) - \begin{itemize} - \item GPS functionality - \item FOTA - \item ARM CryptoCell - \item ARM TrustZone - \end{itemize} -\end{itemize} diff --git a/text/protokolyLPWAN.tex b/text/protokolyLPWAN.tex new file mode 100644 index 0000000..6387a49 --- /dev/null +++ b/text/protokolyLPWAN.tex @@ -0,0 +1,221 @@ +% 1 +% Communication standards for IoT devices +% in 4G/5G networks +% • převzít kapitolu 1.1 +% • doplnit grafy nárůstu IoT zařízení +% 1.1 +% Established communication standards for IoT de- +% vices +% • doplnit GSM, LoRa, Zigbee, Sigfox, Wifi, ESP32, 433 MHz +% 1.2 +% 4G IoT network standards (LPWAN) +% • převzít kapitolu 1.2. +% • doplnit kapitolu 1.2.3 Comparison of 4G LPWAN with established technologies +% • zrcadlova lambda křivka +% https://blog.nordicsemi.com/getconnected/what-is-cellular-iot https://www.nordicsemi.com/P +% power-cellular-IoT/Development-tools?lang=en#infotabs +% 1.3 +% 5G IoT network standards +% • převzít kapitolu 1.3, doplnit 5G trojuhelník +% • zestručnit kapitolu 1.3.1 URLLC, bez zbytečných detailů +% 1.4 +% DECT NR+ standard for 5G IoT networks +% • Stary DECT a IP telefony, pasmo, HW vrstva, NR a teorie prenosovych +% rychlosti +% https://www.nordicsemi.com/Products/Wireless/DECT-NR?lang=en#infotabs +% https://www.nordicsemi.com/Products/Wireless/DECT-NR/Applications?lang=en#infotabs +% https://www.nordicsemi.com/Products/Wireless/DECT-NR/Related-publications?lang=en#info +% https://blog.nordicsemi.com/getconnected/could-dect-nr-democratize-massive-iot-in- +% 5g https://docs.nordicsemi.com/bundle/ps_nrf9161/page/dect.html#ariaid-title4 +% https://devzone.nordicsemi.com/nordic/nordic-blog/b/blog/posts/dect-nr-a-technical- +% dive-into-non-cellular-5g https://blog.nordicsemi.com/getconnected/the-next-step-for- +% m2m-communications + + +%\chapter{Communication protocols for IoT devices in 4G/5G mobile networks} +\chapter{Communication standards for IoT devices in 4G/5G networks} + +\begin{itemize} + \item převzít kapitolu 1.1 + \item doplnit grafy nárůstu IoT zařízení +\end{itemize} + +\paragraph{Established communication standards for IoT devices} + +\begin{itemize} + \item doplnit GSM, LoRa, Zigbee, Sigfox, Wifi, ESP32, 433 MHz +\end{itemize} + +\paragraph{4G IoT network standards (LPWAN)} + +\begin{itemize} + \item převzít kapitolu 1.2. + \item doplnit kapitolu 1.2.3 Comparison of 4G LPWAN with established technologies + \item zrcadlova lambda křivka +\end{itemize} + +https://blog.nordicsemi.com/getconnected/what-is-cellular-iot +https://www.nordicsemi.com/Products/Wireless/Low-power-cellular-IoT/Development-tools?lang=en\#infotabs + +\paragraph{5G IoT network standards} + +\begin{itemize} + \item převzít kapitolu 1.3, doplnit 5G trojuhelník + \item zestručnit kapitolu 1.3.1 URLLC, bez zbytečných detailů +\end{itemize} + +\paragraph{DECT NR+ standard for 5G IoT networks} + +\begin{itemize} + \item Stary DECT a IP telefony, pasmo, HW vrstva, NR a teorie prenosovych rychlosti +\end{itemize} + +https://www.nordicsemi.com/Products/Wireless/DECT-NR?lang=en\#infotabs +https://www.nordicsemi.com/Products/Wireless/DECT-NR/Applications?lang=en\#infotabs +https://www.nordicsemi.com/Products/Wireless/DECT-NR/Related-publications?lang=en\#infotabs +https://blog.nordicsemi.com/getconnected/could-dect-nr-democratize-massive-iot-in-5g +https://docs.nordicsemi.com/bundle/ps\_nrf9161/page/dect.html\#ariaid-title4 + +https://devzone.nordicsemi.com/nordic/nordic-blog/b/blog/posts/dect-nr-a-technical-dive-into-non-cellular-5g +https://blog.nordicsemi.com/getconnected/the-next-step-for-m2m-communications + + + +\section{Current situation} + +It is estimated that currently (2023/2024) there are two actively connected Internet-of-Things (IoT) devices per each person living on the planet Earth and the number will almost double furthermore until 2030, reaching nearly 30 billion connected IoT devices worldwide\cite{statista}. + +At the same time, complexity of the IoT devices rises every year and so is their requirements on the underlying network infrastructure and protocols, originally designed predominantly for completely different mobile applications (text messages and voice / video streaming). Need for new IoT-related protocols started to be prominent with wide-spreading and anticipated new use-cases of IoT devices, for which \ac{GSM} and original \ac{LTE} networks were not originally intended and soon found unsuitable in terms of power efficiency, connection reliability and ability to accommodate billions of small devices with tiny average data rates. + +IoT devices today are not only simple single-purpose meteo sensors, but more and more frequently this category includes very complex vehicles and machinery, such as autonomous cars with multiple RADAR/LIDAR sensors or cooperative industrial robots, needing to communicate with the central command \& control facility and with each other in real time and with very high reliability. On the other hand large widespread of massive quantities of very low power devices in possibly critical application can also be expected. Related requirements on communication data volumes, response latency and network reliability far exceed capacity and technical possibilities of older mobile networks. Larger bandwidths, data speeds and lower latencies brought by 4G and especially 5G mobile networks are necessary for providing the appropriate working space for these new IoT devices. + +The necessary communication protocols for 4G and 5G mobile networks are being standardized under an umbrella of \ac{3GPP} - an association of national telecommunication standardization agencies and commercial partners. \ac{3GPP} has agreed upon and released several communication protocols (so-called „releases“) for the new generations of mobile networks, unfortunately with some ambiguities in their numbering and labeling. For example, Long-term evolution (LTE) was first introduced as a 3G technology standard but it later become a 4G standard. LTE was followed by LTE-Advanced labeled as „true 4G“ or 4.5G and LTE-Advanced Pro (LTE-A Pro) that is considered 5G but sometimes it is labeled as 4.9G \cite{nokia49g}. + +\section{4G IoT networks (LPWAN)} + +%IoT has become a large part of every day life and is now crucial to many both critical and non-critical applications. With planed shutdown of 2G and 3G networks [] it is important to look on protocols that are suposed to replace them and enhance their capabilities. + +Low-power wide-area network (LPWAN) protocols are 4G LTE wireless communication technologies that enable long-range transmission among IoT devices. LPWAN protocols are designed to meet the diverse requirements of IoT applications, mainly low power consumption, wide coverage range, capacity for large number of devices, and high reliability \cite{gsmalpwan}. + +\subsection{NB-IoT} +NB-IoT (Narrowband Internet of Things) is a cellular LPWAN standard that was developed by \ac{3GPP} for IoT devices and services in 2016 under \ac{3GPP} Release 13 and updated in 2017 with \ac{3GPP} Release 14 \cite{erf}. + +NB-IoT focuses on providing extended coverage, enhanced capacity, reduced complexity, and increased battery life for IoT devices that transmit small amounts of data infrequently \cite{rohdenbiot}. + +NB-IoT operates on the licensed spectrum and uses a subset of the LTE bands with peak data rate of 26 kb/s for downlink and 16.9 - 66 kb/s for uplink using Cat NB1. Newer standard of Cat NB2 allows maximum peak rate of 127 kb/s for downlink and 159 kb/s for uplink. NB-IoT uses orthogonal frequency division multiplexing (OFDM) modulation for downlink communication and single carrier frequency division multiple access (SC-FDMA) for uplink communication. + +Single NB-IoT communication channel corresponds to a single 180 kHz LTE frequency block \cite{ltebook}. This enables the following operation modes \cite{rohdenbiot}: + +\begin{itemize} + \item In-band operation - NB-IoT operates on standard LTE frequencies among other types of LTE communication + \item Guard band operation - Communication takes place in LTE guard-band without any other LTE communication + \item Stand alone operation - A theoretically possible scenario when mass adaption of technology will occur. This mode plans to utilize frequency allocation of current GSM networks. +\end{itemize} + +\begin{figure}[!h] + \begin{center} + \includegraphics[width=0.9\textwidth]{obrazky/nbiotmodes.png} + \end{center} + \caption[NB-IoT modes]{NB-IoT modes of operation \cite{rohdenbiot}} + \label{fig:nbiotmodes} +\end{figure} + +As of writing this thesis (December 2023) NB-IoT is supported in Czechia by all three national mobile operators. Vodafone is declaring universal coverage across the whole country \cite{vodafonemap}, T-Mobile in selected larger cities and O2 only in Moravian-Silesian region \cite{narowbandcoverage}. + + + +%NB-IoT is a cellular LPWAN standard that was developed by the 3rd Generation Partnership Project (\ac{3GPP}) for IoT devices and services and published in 2016 with \ac{3GPP} Release 13[] and its updated version in 2017 with \ac{3GPP} Release 14 []. NB-IoT operates on the licensed spectrum and uses a subset of the LTE bands with peak data rate of $26 kb/s$ for downlink and $16.9 \div 66\;kb/s$ for uplink using Cat NB1. Newer standart of Cat NB2 allow maximum peak rate of $127\;kb/s$ for downlink and $159\;kb/s$ for uplink. +%NB-IoT uses orthogonal frequency division multiplexing (OFDM) modulation for downlink communication and single carrier frequency division multiple access (SC-FDMA) for uplink communication. NB-IoT focuses on providing extended coverage, enhanced capacity, reduced complexity, and increased battery life for IoT devices that transmit small amounts of data infrequently. +% +%As of writing this thesis (December 2023) NB-IoT is supported in Czechia by all tree national mobile operators. Vodafone is declaring universal coverage in whole state \cite{vodafonemap}, T-Mobile in selected larger cities and O2 only in Moravian-Silesian region \cite{narowbandcoverage}. +% +%\subsubsection{Modes of operation} +% +%Single NB-IoT comunication channel correspondes to single 180 kHz LTE frequency block \cite{ltebook}. This enables following operation modes \cite{rohdenbiot}: +%\begin{itemize} +% \item In-band operation - NB-IoT operates in standart LTE frequencies among other types of LTE comunication +% \item Guard band operation - Communication occur in LTE guard-band where no prior LTE communication takes place +% \item Stand alone operation - A theoretically possible scenaraio when mass adaption of technology will occur. This mode plans to utilizate frequency allocation of current GSM networks +%\end{itemize} + +\subsection{LTE-M} + +LTE-M or LTE-MTC (Long-Term Evolution Machine Type Communication) is a second LPWAN protocol specified in \ac{3GPP} Release 12, with improved specification in Releases 13 and 14. Unlike NB-IoT, LTE-M uses more bandwidth (1.4 - 5 MHz) and is capable of higher communication speeds (1 - 4 Mbit/s for downlink and 1 – 7 Mbit/s for uplink). Another advantage of LTE-M over NB-IoT is an ability to function with movable objects (such as cars or drones). Higher bandwidths however lead to greater circuit complexity and possible higher energy consumption related to it \cite{nordiccompare}. + +As of writing this thesis (December 2023) LTE-M is covered in Czechia by O2 in 98.5 \% \cite{o2catm} and locally by Vodafone \cite{vodafonemap}. + +%LTE-M or LTE-MTC (Long-Term Evolution Machine Type Communication) is second LPWAN protocol specified in \ac{3GPP} release 12 with improved specification in releaes 13 and 14. +% +%Unlike NB-IoT LTE-M uses more bandwidth 1.4-5 MHz and is capable of higher comunication speeds (1-4 Mbit/s for downlink and 1-7Mbit/s for uplik depending on version). Another advantage is ability to function with movable objects (eg. cars or drones). Higher bandwidth leads to grater circuit complexity and higher energy consumption related to it. +% +%As of writing this thesis (December 2023) LTE-M is coverted in 98.5 \% in Czechina by O2 \cite{o2catm} and mostly by Vodafone \cite{vodafonemap}. + +\section{5G IoT networks} +5G implementation into the mobile networks can be achieved via two methods \cite{5gnruk}: + +\begin{itemize} + \item NSA (non-stand alone) - 5G features are achieved by adding new RAN (Radio Access Network) to existing 4G LTE core. This approach implements dynamic spectrum sharing and enables rapid deployment of enhanced mobile broadband in customer market without larger changes in existing infrastructure. + \item SA (stand alone) - LTE core and RAN are completely replaced with 5G ones. RAN can however still switch back to LTE air interface to ensure backward compatibility with non-5G devices. +\end{itemize} + +In 2018, \ac{3GPP} Release number 15 laid down 5G specification named 5G NR (New Radio). Unlike LTE-A Pro that has just added more features to 4G LTE and operated in LTE standards and channels, 5G NR introduced a new physical layer in air interface \cite{5gnruk}. + +5G NR tries to solve three key aspects of wireless technology \cite{5gnruk}: + +\begin{itemize} + \item eMBB (Enhanced Mobile Broadband): Data-intensive applications needing large bandwidth for primarily traditional end-user demand, like video streaming. This should be achieved by Gigabit LTE, massive MIMO, mmWave technologies, spectrum sharing techniques and advanced channel coding. + \item mMTC (Massive Machine Type Communications): Low-power and low-cost applications with small data volumes but potentially large number of these devices in a small footprint. It is built on LTE LPWAN protocols like LTE-M and NB-IoT, making them potentially a core part of 5G. + \item URLLC (Ultra-reliable and Low-latency Communication): Mission-critical applications traditionally possible only by direct wire connection, necessary for real-time control of autonomous vehicles and industrial machinery. +\end{itemize} + +As of December 2023, 5G IoT networks are not yet commercially available in Czechia. + +%%%%%% +\subsection{URLLC requirements} + +URLLC (Ultra-Reliable and Low-Latency Communication) is a new requirement for 5G networks for providing real-time communication protocols with very low delays and very high levels of reliability. First attempts to address this were introduced in 4G LTE HRLLC (Higher-Reliability and Low-Latency Communication) in \ac{3GPP} release 15 \cite{5gamericasurllc}. Until this point, aspects of latency and reliability were +dealt in separately and sometimes were in direct contradiction to each other (reliability was achieved with repeated data redundancy, which multiplied latency). Combination of these two aspects is however essential for several critical applications with different requirements, as shown in table \ref{tab:urllc}: + +\begin{table}[!h] + \begin{center} + \small + \begin{tabular}{|l|c|c|c|} + \hline + Scenario & E2E latency [ms] & Reliability [\%] & Data rate [Mbps] \\\hline\hline + Discrete automation & 10 & 99.99 & 10 \\\hline + Process automation – remote control & 60 & 99.9999 & 100 \\\hline + Process automation ‒ monitoring & 60 & 99.9 & 1 \\\hline + Process automation ‒ monitoring & 40 & 99.9 & 10 \\\hline + Electricity distribution – high voltage & 5 & 99.9999 & 10 \\\hline + Intelligent transport systems & 30 & 99.9999 & 10 \\\hline + \end{tabular} + \end{center} + \caption[Performance requirements for URLLC]{Performance Requirements for Low-Latency and High-Reliability Scenarios \cite{5gamericasurllc}} + \label{tab:urllc} +\end{table} + + +\subsection{Latency} +With such strict latency requirements, as low as 5 ms end-to-end latency, it is necessary to minimize air interface delay (to 1 ms or less). To achieve such low latency, intensive optimization of air data delivery is necessary. + +There are several possible approaches that can lead to reduced communication time and latency \cite{5gamericasurllc}: + +\begin{itemize} + \item Frequent transmission opportunities +Downlink control channel used to carry scheduling information for data transmission is not usually monitored by end device for power saving reasons. However to reduce the waiting time for delivering the control information, the end device could do this. For device to start uplink transmission, it needs to send a scheduling request (SR) that allocates a specific transmission slot. To minimize the waiting time, the periodicity of the SR resource configuration should reflect latency requirements. This can be further emphasized by flexible schedulling timing mainly in Time Division Dulex (TDD). + + \item Flexible transmission duration +This aspect is supported in 5G using larger subcarier spacing. This shortens slot duration and gives bigger oportunity for quicker communication establishment. + + \item Grant-free (or configured grant) uplink transmission +In cases with very low latency demand, grant-free uplink transition, specific periodic uplink resource for device can be arranged. End device in this scenario does not need to wait for scheduling request and at any time it has data it can transmit in this arranged slot without a need for dynamic grant. + +\end{itemize} + +Air interface is only partially responsible for total end-to-end latency. Remaining latency is caused by core network, internet network and particular server with which the device is communicating. This is to be solved by new concept of Edge computing. Edge computing is a possibility for a mobile operator or another entity to move services from a remote server closer to the device and to execute necessary task right in 5G core network \cite{3gppurllc}. + +Another method of lowering transport network latency is to avoid transport network completly. This is experimented in vehicle-to-vehicle (V2V) protocols and in non-IP based communication \cite{5gamericav2v}. + +\subsection{URLLC reliability optimization} + +In \ac{3GPP} Release 16, redundant transmission for high-reliability communication was introduced \cite{5gamericasurllc}. With this method, user packets are duplicated and simultaneously transferred to the receiver via two disjoint user plane paths. The redundant packets are then eliminated at the receiver side. This further avoids occasional fails in one path propagation and slims probability of exceding the delay requirements. Other changes can be made in 5G core parameters settings, like QoS Monitoring, dynamic division of Packet Delay Budget and enhancements of session continuity \cite{3gppurllc}. diff --git a/text/reseni.tex b/text/reseni.tex deleted file mode 100644 index 5778e42..0000000 --- a/text/reseni.tex +++ /dev/null @@ -1,445 +0,0 @@ -\chapter{Communication protocols for IoT devices in 4G/5G mobile networks} - -\section{Current situation} - -It is estimated that currently (2023/2024) there are two actively connected Internet-of-Things (IoT) devices per each person living on the planet Earth and the number will almost double furthermore until 2030, reaching nearly 30 billion connected IoT devices worldwide\cite{statista}. - -At the same time, complexity of the IoT devices rises every year and so is their requirements on the underlying network infrastructure and protocols, originally designed predominantly for completely different mobile applications (text messages and voice / video streaming). Need for new IoT-related protocols started to be prominent with wide-spreading and anticipated new use-cases of IoT devices, for which \ac{GSM} and original \ac{LTE} networks were not originally intended and soon found unsuitable in terms of power efficiency, connection reliability and ability to accommodate billions of small devices with tiny average data rates. - -IoT devices today are not only simple single-purpose meteo sensors, but more and more frequently this category includes very complex vehicles and machinery, such as autonomous cars with multiple \ac{RADAR}/\ac{LIDAR} sensors or cooperative industrial robots, needing to communicate with the central command \& control facility and with each other in real time and with very high reliability. On the other hand large widespread of massive quantities of very low power devices in possibly critical application can also be expected. Related requirements on communication data volumes, response latency and network reliability far exceed capacity and technical possibilities of older mobile networks. Larger bandwidths, data speeds and lower latencies brought by 4G and especially 5G mobile networks are necessary for providing the appropriate working space for these new IoT devices. - -The necessary communication protocols for 4G and 5G mobile networks are being standardized under an umbrella of \ac{3GPP} - an association of national telecommunication standardization agencies and commercial partners. \ac{3GPP} has agreed upon and released several communication protocols (so-called „releases“) for the new generations of mobile networks, unfortunately with some ambiguities in their numbering and labeling. For example, Long-term evolution (LTE) was first introduced as a 3G technology standard but it later become a 4G standard. LTE was followed by LTE-Advanced labeled as „true 4G“ or 4.5G and LTE-Advanced Pro (LTE-A Pro) that is considered 5G but sometimes it is labeled as 4.9G \cite{nokia49g}. - -\section{4G IoT networks (LPWAN)} - -%IoT has become a large part of every day life and is now crucial to many both critical and non-critical applications. With planed shutdown of 2G and 3G networks [] it is important to look on protocols that are suposed to replace them and enhance their capabilities. - -Low-power wide-area network (LPWAN) protocols are 4G LTE wireless communication technologies that enable long-range transmission among IoT devices. LPWAN protocols are designed to meet the diverse requirements of IoT applications, mainly low power consumption, wide coverage range, capacity for large number of devices, and high reliability \cite{gsmalpwan}. - -\subsection{NB-IoT} -NB-IoT (Narrowband Internet of Things) is a cellular LPWAN standard that was developed by \ac{3GPP} for IoT devices and services in 2016 under \ac{3GPP} Release 13 and updated in 2017 with \ac{3GPP} Release 14 \cite{erf}. - -NB-IoT focuses on providing extended coverage, enhanced capacity, reduced complexity, and increased battery life for IoT devices that transmit small amounts of data infrequently \cite{rohdenbiot}. - -NB-IoT operates on the licensed spectrum and uses a subset of the LTE bands with peak data rate of 26 kb/s for downlink and 16.9 - 66 kb/s for uplink using Cat NB1. Newer standard of Cat NB2 allows maximum peak rate of 127 kb/s for downlink and 159 kb/s for uplink. NB-IoT uses orthogonal frequency division multiplexing (OFDM) modulation for downlink communication and single carrier frequency division multiple access (SC-FDMA) for uplink communication. - -Single NB-IoT communication channel corresponds to a single 180 kHz LTE frequency block \cite{ltebook}. This enables the following operation modes \cite{rohdenbiot}: - -\begin{itemize} - \item In-band operation - NB-IoT operates on standard LTE frequencies among other types of LTE communication - \item Guard band operation - Communication takes place in LTE guard-band without any other LTE communication - \item Stand alone operation - A theoretically possible scenario when mass adaption of technology will occur. This mode plans to utilize frequency allocation of current GSM networks. -\end{itemize} - -\begin{figure}[!h] - \begin{center} - \includegraphics[width=0.9\textwidth]{obrazky/nbiotmodes.png} - \end{center} - \caption[NB-IoT modes]{NB-IoT modes of operation \cite{rohdenbiot}} - \label{fig:nbiotmodes} -\end{figure} - -As of writing this thesis (December 2023) NB-IoT is supported in Czechia by all three national mobile operators. Vodafone is declaring universal coverage across the whole country \cite{vodafonemap}, T-Mobile in selected larger cities and O2 only in Moravian-Silesian region \cite{narowbandcoverage}. - - - -%NB-IoT is a cellular LPWAN standard that was developed by the 3rd Generation Partnership Project (\ac{3GPP}) for IoT devices and services and published in 2016 with \ac{3GPP} Release 13[] and its updated version in 2017 with \ac{3GPP} Release 14 []. NB-IoT operates on the licensed spectrum and uses a subset of the LTE bands with peak data rate of $26 kb/s$ for downlink and $16.9 \div 66\;kb/s$ for uplink using Cat NB1. Newer standart of Cat NB2 allow maximum peak rate of $127\;kb/s$ for downlink and $159\;kb/s$ for uplink. -%NB-IoT uses orthogonal frequency division multiplexing (OFDM) modulation for downlink communication and single carrier frequency division multiple access (SC-FDMA) for uplink communication. NB-IoT focuses on providing extended coverage, enhanced capacity, reduced complexity, and increased battery life for IoT devices that transmit small amounts of data infrequently. -% -%As of writing this thesis (December 2023) NB-IoT is supported in Czechia by all tree national mobile operators. Vodafone is declaring universal coverage in whole state \cite{vodafonemap}, T-Mobile in selected larger cities and O2 only in Moravian-Silesian region \cite{narowbandcoverage}. -% -%\subsubsection{Modes of operation} -% -%Single NB-IoT comunication channel correspondes to single 180 kHz LTE frequency block \cite{ltebook}. This enables following operation modes \cite{rohdenbiot}: -%\begin{itemize} -% \item In-band operation - NB-IoT operates in standart LTE frequencies among other types of LTE comunication -% \item Guard band operation - Communication occur in LTE guard-band where no prior LTE communication takes place -% \item Stand alone operation - A theoretically possible scenaraio when mass adaption of technology will occur. This mode plans to utilizate frequency allocation of current GSM networks -%\end{itemize} - -\subsection{LTE-M} - -LTE-M or LTE-MTC (Long-Term Evolution Machine Type Communication) is a second LPWAN protocol specified in \ac{3GPP} Release 12, with improved specification in Releases 13 and 14. Unlike NB-IoT, LTE-M uses more bandwidth (1.4 - 5 MHz) and is capable of higher communication speeds (1 - 4 Mbit/s for downlink and 1 – 7 Mbit/s for uplink). Another advantage of LTE-M over NB-IoT is an ability to function with movable objects (such as cars or drones). Higher bandwidths however lead to greater circuit complexity and possible higher energy consumption related to it \cite{nordiccompare}. - -As of writing this thesis (December 2023) LTE-M is covered in Czechia by O2 in 98.5 \% \cite{o2catm} and locally by Vodafone \cite{vodafonemap}. - -%LTE-M or LTE-MTC (Long-Term Evolution Machine Type Communication) is second LPWAN protocol specified in \ac{3GPP} release 12 with improved specification in releaes 13 and 14. -% -%Unlike NB-IoT LTE-M uses more bandwidth 1.4-5 MHz and is capable of higher comunication speeds (1-4 Mbit/s for downlink and 1-7Mbit/s for uplik depending on version). Another advantage is ability to function with movable objects (eg. cars or drones). Higher bandwidth leads to grater circuit complexity and higher energy consumption related to it. -% -%As of writing this thesis (December 2023) LTE-M is coverted in 98.5 \% in Czechina by O2 \cite{o2catm} and mostly by Vodafone \cite{vodafonemap}. - -\section{5G IoT networks} -5G implementation into the mobile networks can be achieved via two methods \cite{5gnruk}: - -\begin{itemize} - \item NSA (non-stand alone) - 5G features are achieved by adding new RAN (Radio Access Network) to existing 4G LTE core. This approach implements dynamic spectrum sharing and enables rapid deployment of enhanced mobile broadband in customer market without larger changes in existing infrastructure. - \item SA (stand alone) - LTE core and RAN are completely replaced with 5G ones. RAN can however still switch back to LTE air interface to ensure backward compatibility with non-5G devices. -\end{itemize} - -In 2018, \ac{3GPP} Release number 15 laid down 5G specification named 5G NR (New Radio). Unlike LTE-A Pro that has just added more features to 4G LTE and operated in LTE standards and channels, 5G NR introduced a new physical layer in air interface \cite{5gnruk}. - -5G NR tries to solve three key aspects of wireless technology \cite{5gnruk}: - -\begin{itemize} - \item eMBB (Enhanced Mobile Broadband): Data-intensive applications needing large bandwidth for primarily traditional end-user demand, like video streaming. This should be achieved by Gigabit LTE, massive MIMO, mmWave technologies, spectrum sharing techniques and advanced channel coding. - \item mMTC (Massive Machine Type Communications): Low-power and low-cost applications with small data volumes but potentially large number of these devices in a small footprint. It is built on LTE LPWAN protocols like LTE-M and NB-IoT, making them potentially a core part of 5G. - \item URLLC (Ultra-reliable and Low-latency Communication): Mission-critical applications traditionally possible only by direct wire connection, necessary for real-time control of autonomous vehicles and industrial machinery. -\end{itemize} - -As of December 2023, 5G IoT networks are not yet commercially available in Czechia. - -%%%%%% -\subsection{URLLC requirements} - -URLLC (Ultra-Reliable and Low-Latency Communication) is a new requirement for 5G networks for providing real-time communication protocols with very low delays and very high levels of reliability. First attempts to address this were introduced in 4G LTE HRLLC (Higher-Reliability and Low-Latency Communication) in \ac{3GPP} release 15 \cite{5gamericasurllc}. Until this point, aspects of latency and reliability were -dealt in separately and sometimes were in direct contradiction to each other (reliability was achieved with repeated data redundancy, which multiplied latency). Combination of these two aspects is however essential for several critical applications with different requirements, as shown in table \ref{tab:urllc}: - -\begin{table}[!h] - \begin{center} - \small - \begin{tabular}{|l|c|c|c|} - \hline - Scenario & E2E latency [ms] & Reliability [\%] & Data rate [Mbps] \\\hline\hline - Discrete automation & 10 & 99.99 & 10 \\\hline - Process automation – remote control & 60 & 99.9999 & 100 \\\hline - Process automation ‒ monitoring & 60 & 99.9 & 1 \\\hline - Process automation ‒ monitoring & 40 & 99.9 & 10 \\\hline - Electricity distribution – high voltage & 5 & 99.9999 & 10 \\\hline - Intelligent transport systems & 30 & 99.9999 & 10 \\\hline - \hline - \end{tabular} - \end{center} - \caption[Performance requirements for URLLC]{Performance Requirements for Low-Latency and High-Reliability Scenarios \cite{5gamericasurllc}} - \label{tab:urllc} -\end{table} - - -\subsection{Latency} -With such strict latency requirements, as low as 5 ms end-to-end latency, it is necessary to minimize air interface delay (to 1 ms or less). To achieve such low latency, intensive optimization of air data delivery is necessary. - -There are several possible approaches that can lead to reduced communication time and latency \cite{5gamericasurllc}: - -\begin{itemize} - \item Frequent transmission opportunities -Downlink control channel used to carry scheduling information for data transmission is not usually monitored by end device for power saving reasons. However to reduce the waiting time for delivering the control information, the end device could do this. For device to start uplink transmission, it needs to send a scheduling request (SR) that allocates a specific transmission slot. To minimize the waiting time, the periodicity of the SR resource configuration should reflect latency requirements. This can be further emphasized by flexible schedulling timing mainly in Time Division Dulex (TDD). - - \item Flexible transmission duration -This aspect is supported in 5G using larger subcarier spacing. This shortens slot duration and gives bigger oportunity for quicker communication establishment. - - \item Grant-free (or configured grant) uplink transmission -In cases with very low latency demand, grant-free uplink transition, specific periodic uplink resource for device can be arranged. End device in this scenario does not need to wait for scheduling request and at any time it has data it can transmit in this arranged slot without a need for dynamic grant. - -\end{itemize} - -Air interface is only partially responsible for total end-to-end latency. Remaining latency is caused by core network, internet network and particular server with which the device is communicating. This is to be solved by new concept of Edge computing. Edge computing is a possibility for a mobile operator or another entity to move services from a remote server closer to the device and to execute necessary task right in 5G core network \cite{3gppurllc}. - -Another method of lowering transport network latency is to avoid transport network completly. This is experimented in vehicle-to-vehicle (V2V) protocols and in non-IP based communication \cite{5gamericav2v}. - -\subsection{URLLC reliability optimization} - -In \ac{3GPP} Release 16, redundant transmission for high-reliability communication was introduced \cite{5gamericasurllc}. With this method, user packets are duplicated and simultaneously transferred to the receiver via two disjoint user plane paths. The redundant packets are then eliminated at the receiver side. This further avoids occasional fails in one path propagation and slims probability of exceding the delay requirements. Other changes can be made in 5G core parameters settings, like QoS Monitoring, dynamic division of Packet Delay Budget and enhancements of session continuity \cite{3gppurllc}. - -\chapter{IoT communication modules for 4G/5G networks} - -\section{Nordic Semiconductor nRF9160} - -\begin{figure}[H] - \begin{center} - \includegraphics[width=0.4\textwidth]{obrazky/nrfchip.png} - \end{center} - \caption[Nordic nRF9160 SiP]{Nordic nRF9160 SiP\cite{nrf91desc}} - \label{fig:sipfront} -\end{figure} - -nRF9160, made by Nordic Semiconductor, is a System-in-Package (SiP) combining multiple integrated circuits into a single LGA package (10x16x1.04 mm in size), functioning as an entire computing system: -\begin{itemize} - \item Application Processor with Arm Cortex-M33 core at 64 MHz, 1 MB flash memory, 256 kB RAM and usual microcontroller peripherials - 4x SPI/UART/I2C, 4x PWM, PDM, I2S, 12-bit ADC @ 200 ksps, 3x timer, 2x RTC, WDT. - \item LTE modem (700 – 2000 MHz) operating in the both LPWAN modes: LTE-M (300/375 kbps DL/UL) and NB-IoT (30/60 kbps DL/UL), supporting IPv4/IPv6 internet layer with optional security using TCP/TLS in transport layer and modem firmware upgrades via FOTA (firmware over the air). - \item Radio-Frequency Front End (RFFE) - \item GNSS receiver - \item Power management integrated circuits. -\end{itemize} - -nRF9160 is certified for global operations in multiple LTE bands, as shown in the figure below. For European operations, bands B1, B3, B8, B20 and B28 are available for both NB-IoT and LTE-M modes. Hardware security is strengthened with ARM TrustZone technology protecting against uploading unofficial or malicious firmware. TrustZone also protects from firmware attacks like memory and peripheral spoofing \cite{armtrustzone}. nRF9160 furthermore employs Arm CryptoCell solution optimized for high-performance cryptography for energy-constrained devices. - -Both SIM and eSIM are supported for connection and authentication with mobile network operators \cite{nrf91desc}. nRF9160 can be powered from relatively large range of voltages - from 3.0 to 5.5 V, allowing to directly connect Li-ion or Li-Po type batteries or USB-compatible power supplies. - -nRF9160 is manufactured in 3 modifications, sharing the same 127-pin LGA package, but differing in LTE modem capabilities, as shown in table \ref{tab:nrfchips} below. - -\begin{table}[!h] - \begin{center} - \small - \begin{tabular}{|l|l|} - \hline - Name & RF features \\ \hline - \hline - nRF9160-SICA & Only LTE-M \\ \hline - nRF9160-SIBA & Only NB-IoT \\ \hline - nRF9160-SIAA & LTE-M, NB-IoT and GNSS \\ \hline - \end{tabular} - \end{center} - \caption[nRF9160 product options]{nRF9160 LGA modules options and their limitations. \cite{nrf91datasheet}} - \label{tab:nrfchips} -\end{table} - -\subsection{Modules with nRF9160} - -There are several modules and development kits available with nRF9160 chipset, originating from Nordic Semiconductor, as well as from other vendors. - -\subsubsection{nRF9160 DK} - -\begin{figure}[H] - \begin{center} - \includegraphics[width=0.9\textwidth]{obrazky/nrf9160DKfront.png} - \end{center} - \caption[Nordic nRF9160DK]{Nordic nRF9160DK front view\cite{nrf91dkdesc}} - \label{fig:dkfront} -\end{figure} - -nRF9160 DK is an official pre-certified development kit for nRF9160 made and supported by Nordic Semiconductor. It is equipped with LTE-M/NB-IoT antenna, GNSS antenna, SIM connector, eSIM card from iBasis preloaded with 10 MB data. All peripherial GPIO pins of nRF9160 are available through connectors and headers compatible with Arduino Uno Rev3 form factor, there are also 4 on-board LEDs, 2 buttons and 2 switches connected to the application processor GPIO. The board also includes nRF52840 board controller sharing the peripherials and allowing to build a Bluetooth Low Energy gateway. Powering and communication with PC are arranged via USB (virtual COM) port. Programming and debugging is enabled through the Segger J-Link OB. The nRF9160 DK is supported by a full suite of development software tools by Nordic Semiconductor, free to download and use commercially \cite{nrf91dkdesc}. - -\subsubsection{Nordic Thingy:91} - -\begin{figure}[H] - \begin{center} - \includegraphics[width=0.4\textwidth]{obrazky/Thingy91_board.png} - \end{center} - \caption[Nordic Thisgy:91]{Nordic nRF9160DK front view\cite{thingydesc}} - \label{fig:thingy} -\end{figure} - -Nordic Thingy:91, also made by Nordic Semiconductor, is a compact small-factor module used as a rapid prototyping battery-operated platform, containing LTE-M/NB-IoT/GNSS, Bluetooth LE and NFC antennas, User-programmable button and RGB LEDs, environmental sensor for temperature, humidity, air quality and air pressure, plus a color and light sensor, low-power accelerometer and high-g accelerometer, rechargeable Li-Po battery with 1350 mAh capacity -\cite{thingydesc}. - -\subsubsection{NimbeLink Nano Global} - -\begin{figure}[H] - \begin{center} - \includegraphics[width=0.6\textwidth]{obrazky/NimbeLink-Nano.png} - \end{center} - \caption[NimbeLink Nano Global LTE-M]{NimbeLink Nano Global LTE-M\cite{nimbelinkdesc}} - \label{fig:nimbe} -\end{figure} - -NimbeLink Nano Global LTE-M (Skywire Nano Development Kit, NL-SWN-LTE-NRF9160), made by Airgain, is an add-on modem with nRF9160 and two U.FL antenna connectors, attached to a base board NL-SWNDK providing SIM holder, USB powering and distributition of GPIO pins to peripherial headers. The board has been originally certified only for Verizon networks -\cite{nimbelinkdesc}. - -\subsubsection{LN60E} - -\begin{figure}[H] - \begin{center} - \includegraphics[width=0.6\textwidth]{obrazky/LN60E.png} - \end{center} - \caption[LN60E]{LN60E\cite{ln60desc}} - \label{fig:ln60} -\end{figure} - -LN60E is a simple modem provided by Fansel, having a U.FL antenna connector, SIM connector and M.2 card connector for nRF9160 peripherials -\cite{ln60desc}. - -\subsubsection{Pebble Tracker} - -\begin{figure}[H] - \begin{center} - \includegraphics[width=0.6\textwidth]{obrazky/pebble.jpg} - \end{center} - \caption[Pebble Tracker]{Pebble Tracker\cite{pebbledesc}} - \label{fig:} -\end{figure} - -Pebble Tracker, a crowdfunded module made by IoTex, is a battery operated IoT prototyping platform based on a board with nRF9160, Bosch BME680 humidity/pressure/temperature/air quality sensor, ICM-42605 3-axial gyroscope/accelerometer, AMS TSL2572 ambient light sensor, SIM slot, OLED display, in a compact plastic case -\cite{pebbledesc} - -\subsubsection{Icarus SoM} - -\begin{figure}[H] - \begin{center} - \includegraphics[width=0.6\textwidth]{obrazky/icarus-som.png} - \end{center} - \caption[Icarus SoM]{Icarus SoM\cite{icarusdesc}} - \label{fig:icarus} -\end{figure} - -Icarus SoM, made by Actinius, is a simple module with U.FL antenna connectors for GNSS and LTE, eSIM and accelerometer, with spare GPIO pins headed to PCB edge connectors -\cite{icarusdesc}. - -\subsubsection{Icarus Bee} - -\begin{figure}[H] - \begin{center} - \includegraphics[width=0.6\textwidth]{obrazky/icarus-bee.png} - \end{center} - \caption[Icarus Bee]{Icarus Bee\cite{icarusbeedesc}} - \label{fig:icarusbee} -\end{figure} - -Icarus Bee, made by Actinius, expands the above-mentioned Icarus SoM module with a board connecting it to 64 Mbit flash memory, RGB LED, button, SIM connector and GPIO to pin headers -\cite{icarusbeedesc}. - -\subsubsection{Icarus IoT Board v2} - -\begin{figure}[H] - \begin{center} - \includegraphics[width=0.6\textwidth]{obrazky/icarus-iot.png} - \end{center} - \caption[Icarus IoT]{Icarus IoT Board v2\cite{icarusiotdesc}} - \label{fig:icarusiot} -\end{figure} - -Icarus IoT Board v2, made by Actinius, contains nRF9160 chipset on a board with USB connector, U.FL antenna connectors for LTE and GNSS, LiPo charger, eSIM and nano SIM connector, accelerometer and SPI flash memory, with pin headers compatible with Adafruit Feather footprint -\cite{icarusiotdesc}. - -\subsubsection{nRF9160 Feather} - -\begin{figure}[H] - \begin{center} - \includegraphics[width=0.6\textwidth]{obrazky/nrf9160_feather.jpg} - \end{center} - \caption[nRF9160 Feather]{nRF9160 Feather\cite{featherdesc}} - \label{fig:feather} -\end{figure} - -nRF9160 Feather, made by CircuitDojo, is a design with pin headers compatible with Adafruit Feather footprint and a functionality similar to the Icarus IoT Board v2 -\cite{featherdesc}. - -\subsubsection{SparkFun Thing Plus nRF9160} - -\begin{figure}[H] - \begin{center} - \includegraphics[width=0.7\textwidth]{obrazky/sparkfun2.jpg} - \end{center} - \caption[SparkFun Thing Plus nRF9160]{SparkFun Thing Plus nRF9160\cite{sparkfundesc}} - \label{} -\end{figure} - -SparkFun Thing Plus nRF9160, made by SparkFun, is another board with Adafruit Feather footprint and similar to Icarus IoT Board v2 described above, however with USB-C connector and providing 4 MB SPI flash memory, LiPo charger, low power RTC, a button, a LED, two U.FL antennas for LTE and GNSS -\cite{sparkfundesc}. - -\subsubsection{Connexio Stratus} - -\begin{figure}[H] - \begin{center} - \includegraphics[width=0.4\textwidth]{obrazky/connexio.jpg} - \end{center} - \caption[Connexio Stratus]{Connexio Stratus\cite{connexiodesc}} - \label{} -\end{figure} - -Connexio Stratus, a crowd-funded development board, has a similar design to the SparkFun board above, adding SIM with 500 MB of mobile data, energy harvesting integrated circuit for Li-ion and NiMH battery charging, LiPo battery connection and charging, 2 push-buttons, 1 LED, SHT4x temperature and humidity sensor, LIS2DH 3-axial accelerometer -\cite{connexiodesc}. - -Comparisons of the main parameters of the most common nRF9160 boards is provided in the following table \ref{tab:nrfmodules} taken from \cite{connexiodesc}: -\begin{table}[H] - \begin{center} - \scriptsize - \begin{tabular}{|l|l|l|l|l|l|l|l|} - \hline - & Stratus & Thingy:91 & Icarus & Feather & Pebble Tracker & Thing Plus \\\hline - \hline - Manufacturer & Conexio & Nordic Semi & Actinius & CircuitDojo & IoTex & Sparkfun \\\hline - Total Pins & 33 & 8 & 28 & 28 & None & 28 \\\hline - I/O Pins & 26 & 8 & 21 & 20 & None & 20 \\\hline - Energy Harvester & Yes & No & No & No & No & No \\\hline - Accelerometer & Yes & Yes & Yes & Yes & Yes & Yes \\\hline - Environmental Sensors & Yes & Yes & No & No & Yes & No \\\hline - Onboard LEDS & 2 & 1 RGB & 1 RGB & 2 & 1 RGB & 2 \\\hline - Sensor power gating & Yes & No & No & No & No & No \\\hline - Power switch & Yes & Yes & No & No & Yes & No \\\hline - Lipo battery charger & Yes & No & Yes & Yes & No & Yes \\\hline - USB interface & Yes & Yes & Yes & Yes & Yes & Yes \\\hline - Debugging connector & Yes & Yes & No & No & Yes & No \\\hline - Prepaid Cellular data & 500 MB & 10 MB & 10 MB & 10 MB & No & 10 MB \\\hline - Cellular data validity & 10 years & N/A & N/A & N/A & N/A & N/A \\\hline - SMS Data & 250 & No & No & No & No & No \\\hline - Dedicated sensor shield & Yes & No & No & No & No & No \\\hline - VS Code dev. extension & Yes & Yes & No & No & No & No \\\hline - Breadboard compatible & Yes & No & Yes & Yes & No & Yes \\\hline - Edge Impulse ready & Yes & Yes & No & No & No & No \\\hline - Memfault ready & Yes & No & No & No & No & No \\\hline - Golioth ready & Yes & No & No & Yes & No & No \\\hline - Open-source & HW+SW & HW+SW & No & HW+SW & No & HW+SW \\\hline - Dimension [mm] & 50.8x22.8 & 58.8x58.5 & 50.8x22.8 & 50.8x22.8 & 53x35 & 58.42x22.86 \\\hline - Weight & \~5 g & 61 g & \~5 g & \~5 g & 10 g & \~5 g \\\hline - Price (USD) & \$159 & \$126.25 & \$115 & \$99 & \$215 & \$129.95 \\\hline - \end{tabular} - \end{center} - \caption[Comparation of nRF9160 modules]{Comparation of nRF9160 main modules} - \label{tab:nrfmodules} -\end{table} - -%%------------------------------------------------------------------------------------------- - -\section{Quectel RM520N} - -\begin{figure}[h!] - \begin{center} - \includegraphics[width=0.6\textwidth]{obrazky/RM520N.png} - \end{center} - \caption[Quectel RM520N]{Quectel RM520N series front view\cite{rm520ndatasheet}} - \label{} -\end{figure} - -RM520N is a 5G Sub-6GHz IoT module, made by Chinese company Quectel, optimized for IoT and eMBB applications with worldwide spectrum coverage, but capable of also 3G/4G multi-mode operation. The module is made in an M.2 form factor (30 x 52 x 2.3 mm) with 4 antenna connectors and is compatible with \ac{3GPP} Release 16 specification, supporting both 5G NSA (data rates: 3.4 Gbps DL / 550 Mbps UL) and SA modes (data rates: 2.4 Gbps DL / 900 Mbps UL). - -The RM520N is an industrial-grade module for industrial and commercial applications. It should cover nearly all the mainstream carriers worldwide and support Qualcomm® IZat location technology Gen9C Lite (GPS, GLONASS, BDS and Galileo). The integrated GNSS receiver simplifies the product design. - -It communicates using USB and PCIe drivers provided by Quectel for Windows 7 or higher, Linux, and Android. Main anticipated usage are industrial routers, home gateways, laptops / tablet PCs as well as IoT applications \cite{rm520ndatasheet}. - -The module comes in two variants: RM520N-GL with global coverage and RM520N-EU with EU frequency regulatory spectrum. - -\subsection{Modules with RM520N} - -Development support for RM520N modules is provided by a Chinese company Waveshare \cite{waveshare1}\cite{waveshare2} -making several hardware kits for rapid development and implementation with RM520N and having a distribution network across EU (e.g. \url{https://rlx.sk/sk/vyhladavanie?controller=search&s=RM520N}) - -\subsubsection{Dongle} -\begin{figure}[H] - \begin{center} - \includegraphics[width=0.6\textwidth]{obrazky/rmdongle.jpg} - \end{center} - \caption[Waveshare dongle]{Waveshare dongle\cite{rmdongle}} - \label{} -\end{figure} - -5G DONGLE module \cite{rmdongle} -providing simple expansion board with 4 SMA antenna connectors, nano SIM card holder, M2 connector for RM520N, heatsink and USB3.1 port for connecting to PC or Raspberry Pi. - -\subsubsection{Raspberry Pi HAT} - -\begin{figure}[H] - \begin{center} - \includegraphics[width=0.6\textwidth]{obrazky/rmpi.jpg} - \end{center} - \caption[Waveshare dongle]{Waveshare dongle\cite{rmpi}} - \label{} -\end{figure} - -5G HAT for Raspberry Pi \cite{rmpi} -, with a case for Raspberry Pi 3B/4B, onboard USB3.1 and USB-C ports, 2x SIM card slot, 4 antennas, 3A power supply circuit. - -\subsubsection{USB/Ethernet converter} - -\begin{figure}[H] - \begin{center} - \includegraphics[width=0.6\textwidth]{obrazky/rmeth.jpg} - \end{center} - \caption[USB/Ethernet converter]{USB3.1 / Gigabit Ethernet converter to 5G\cite{rmeth}} - \label{} -\end{figure} - -USB3.1 / Gigabit Ethernet converter to 5G \cite{rmeth} -capable to connect RM520N module to its M2 connector header and acting as a 5G communication bridge to PC, industrial control hosts, Raspberry Pi, ethernet switch or router using their USB3.1 or Ethernet connections. - -\subsubsection{Module form Jetson Nano} - -\begin{figure}[H] - \begin{center} - \includegraphics[width=0.6\textwidth]{obrazky/rmjet.jpg} - \end{center} - \caption[Module for Jetson Nano]{Comunication module for Jetson Nano\cite{rmjet}} - \label{} -\end{figure} - -Communication module for Jetson Nano \cite{rmjet} -- interface with M2 connector, USB3.1 port, audio jack and decoder, SIM card slot, 40-pin GPIO extension header for direct connection to Jetson Nano, 4 antennas. diff --git a/text/teorie.tex b/text/teorie.tex deleted file mode 100644 index b335a22..0000000 --- a/text/teorie.tex +++ /dev/null @@ -1,174 +0,0 @@ -% 1 -% Communication standards for IoT devices -% in 4G/5G networks -% • převzít kapitolu 1.1 -% • doplnit grafy nárůstu IoT zařízení -% 1.1 -% Established communication standards for IoT de- -% vices -% • doplnit GSM, LoRa, Zigbee, Sigfox, Wifi, ESP32, 433 MHz -% 1.2 -% 4G IoT network standards (LPWAN) -% • převzít kapitolu 1.2. -% • doplnit kapitolu 1.2.3 Comparison of 4G LPWAN with established technologies -% • zrcadlova lambda křivka -% https://blog.nordicsemi.com/getconnected/what-is-cellular-iot https://www.nordicsemi.com/P -% power-cellular-IoT/Development-tools?lang=en#infotabs -% 1.3 -% 5G IoT network standards -% • převzít kapitolu 1.3, doplnit 5G trojuhelník -% • zestručnit kapitolu 1.3.1 URLLC, bez zbytečných detailů -% 1.4 -% DECT NR+ standard for 5G IoT networks -% • Stary DECT a IP telefony, pasmo, HW vrstva, NR a teorie prenosovych -% rychlosti -% https://www.nordicsemi.com/Products/Wireless/DECT-NR?lang=en#infotabs -% https://www.nordicsemi.com/Products/Wireless/DECT-NR/Applications?lang=en#infotabs -% https://www.nordicsemi.com/Products/Wireless/DECT-NR/Related-publications?lang=en#info -% https://blog.nordicsemi.com/getconnected/could-dect-nr-democratize-massive-iot-in- -% 5g https://docs.nordicsemi.com/bundle/ps_nrf9161/page/dect.html#ariaid-title4 -% https://devzone.nordicsemi.com/nordic/nordic-blog/b/blog/posts/dect-nr-a-technical- -% dive-into-non-cellular-5g https://blog.nordicsemi.com/getconnected/the-next-step-for- -% m2m-communications - - -\chapter{Communication protocols for IoT devices in 4G/5G mobile networks} - -\section{Current situation} - -It is estimated that currently (2023/2024) there are two actively connected Internet-of-Things (IoT) devices per each person living on the planet Earth and the number will almost double furthermore until 2030, reaching nearly 30 billion connected IoT devices worldwide\cite{statista}. - -At the same time, complexity of the IoT devices rises every year and so is their requirements on the underlying network infrastructure and protocols, originally designed predominantly for completely different mobile applications (text messages and voice / video streaming). Need for new IoT-related protocols started to be prominent with wide-spreading and anticipated new use-cases of IoT devices, for which \ac{GSM} and original \ac{LTE} networks were not originally intended and soon found unsuitable in terms of power efficiency, connection reliability and ability to accommodate billions of small devices with tiny average data rates. - -IoT devices today are not only simple single-purpose meteo sensors, but more and more frequently this category includes very complex vehicles and machinery, such as autonomous cars with multiple RADAR/LIDAR sensors or cooperative industrial robots, needing to communicate with the central command \& control facility and with each other in real time and with very high reliability. On the other hand large widespread of massive quantities of very low power devices in possibly critical application can also be expected. Related requirements on communication data volumes, response latency and network reliability far exceed capacity and technical possibilities of older mobile networks. Larger bandwidths, data speeds and lower latencies brought by 4G and especially 5G mobile networks are necessary for providing the appropriate working space for these new IoT devices. - -The necessary communication protocols for 4G and 5G mobile networks are being standardized under an umbrella of \ac{3GPP} - an association of national telecommunication standardization agencies and commercial partners. \ac{3GPP} has agreed upon and released several communication protocols (so-called „releases“) for the new generations of mobile networks, unfortunately with some ambiguities in their numbering and labeling. For example, Long-term evolution (LTE) was first introduced as a 3G technology standard but it later become a 4G standard. LTE was followed by LTE-Advanced labeled as „true 4G“ or 4.5G and LTE-Advanced Pro (LTE-A Pro) that is considered 5G but sometimes it is labeled as 4.9G \cite{nokia49g}. - -\section{4G IoT networks (LPWAN)} - -%IoT has become a large part of every day life and is now crucial to many both critical and non-critical applications. With planed shutdown of 2G and 3G networks [] it is important to look on protocols that are suposed to replace them and enhance their capabilities. - -Low-power wide-area network (LPWAN) protocols are 4G LTE wireless communication technologies that enable long-range transmission among IoT devices. LPWAN protocols are designed to meet the diverse requirements of IoT applications, mainly low power consumption, wide coverage range, capacity for large number of devices, and high reliability \cite{gsmalpwan}. - -\subsection{NB-IoT} -NB-IoT (Narrowband Internet of Things) is a cellular LPWAN standard that was developed by \ac{3GPP} for IoT devices and services in 2016 under \ac{3GPP} Release 13 and updated in 2017 with \ac{3GPP} Release 14 \cite{erf}. - -NB-IoT focuses on providing extended coverage, enhanced capacity, reduced complexity, and increased battery life for IoT devices that transmit small amounts of data infrequently \cite{rohdenbiot}. - -NB-IoT operates on the licensed spectrum and uses a subset of the LTE bands with peak data rate of 26 kb/s for downlink and 16.9 - 66 kb/s for uplink using Cat NB1. Newer standard of Cat NB2 allows maximum peak rate of 127 kb/s for downlink and 159 kb/s for uplink. NB-IoT uses orthogonal frequency division multiplexing (OFDM) modulation for downlink communication and single carrier frequency division multiple access (SC-FDMA) for uplink communication. - -Single NB-IoT communication channel corresponds to a single 180 kHz LTE frequency block \cite{ltebook}. This enables the following operation modes \cite{rohdenbiot}: - -\begin{itemize} - \item In-band operation - NB-IoT operates on standard LTE frequencies among other types of LTE communication - \item Guard band operation - Communication takes place in LTE guard-band without any other LTE communication - \item Stand alone operation - A theoretically possible scenario when mass adaption of technology will occur. This mode plans to utilize frequency allocation of current GSM networks. -\end{itemize} - -\begin{figure}[!h] - \begin{center} - \includegraphics[width=0.9\textwidth]{obrazky/nbiotmodes.png} - \end{center} - \caption[NB-IoT modes]{NB-IoT modes of operation \cite{rohdenbiot}} - \label{fig:nbiotmodes} -\end{figure} - -As of writing this thesis (December 2023) NB-IoT is supported in Czechia by all three national mobile operators. Vodafone is declaring universal coverage across the whole country \cite{vodafonemap}, T-Mobile in selected larger cities and O2 only in Moravian-Silesian region \cite{narowbandcoverage}. - - - -%NB-IoT is a cellular LPWAN standard that was developed by the 3rd Generation Partnership Project (\ac{3GPP}) for IoT devices and services and published in 2016 with \ac{3GPP} Release 13[] and its updated version in 2017 with \ac{3GPP} Release 14 []. NB-IoT operates on the licensed spectrum and uses a subset of the LTE bands with peak data rate of $26 kb/s$ for downlink and $16.9 \div 66\;kb/s$ for uplink using Cat NB1. Newer standart of Cat NB2 allow maximum peak rate of $127\;kb/s$ for downlink and $159\;kb/s$ for uplink. -%NB-IoT uses orthogonal frequency division multiplexing (OFDM) modulation for downlink communication and single carrier frequency division multiple access (SC-FDMA) for uplink communication. NB-IoT focuses on providing extended coverage, enhanced capacity, reduced complexity, and increased battery life for IoT devices that transmit small amounts of data infrequently. -% -%As of writing this thesis (December 2023) NB-IoT is supported in Czechia by all tree national mobile operators. Vodafone is declaring universal coverage in whole state \cite{vodafonemap}, T-Mobile in selected larger cities and O2 only in Moravian-Silesian region \cite{narowbandcoverage}. -% -%\subsubsection{Modes of operation} -% -%Single NB-IoT comunication channel correspondes to single 180 kHz LTE frequency block \cite{ltebook}. This enables following operation modes \cite{rohdenbiot}: -%\begin{itemize} -% \item In-band operation - NB-IoT operates in standart LTE frequencies among other types of LTE comunication -% \item Guard band operation - Communication occur in LTE guard-band where no prior LTE communication takes place -% \item Stand alone operation - A theoretically possible scenaraio when mass adaption of technology will occur. This mode plans to utilizate frequency allocation of current GSM networks -%\end{itemize} - -\subsection{LTE-M} - -LTE-M or LTE-MTC (Long-Term Evolution Machine Type Communication) is a second LPWAN protocol specified in \ac{3GPP} Release 12, with improved specification in Releases 13 and 14. Unlike NB-IoT, LTE-M uses more bandwidth (1.4 - 5 MHz) and is capable of higher communication speeds (1 - 4 Mbit/s for downlink and 1 – 7 Mbit/s for uplink). Another advantage of LTE-M over NB-IoT is an ability to function with movable objects (such as cars or drones). Higher bandwidths however lead to greater circuit complexity and possible higher energy consumption related to it \cite{nordiccompare}. - -As of writing this thesis (December 2023) LTE-M is covered in Czechia by O2 in 98.5 \% \cite{o2catm} and locally by Vodafone \cite{vodafonemap}. - -%LTE-M or LTE-MTC (Long-Term Evolution Machine Type Communication) is second LPWAN protocol specified in \ac{3GPP} release 12 with improved specification in releaes 13 and 14. -% -%Unlike NB-IoT LTE-M uses more bandwidth 1.4-5 MHz and is capable of higher comunication speeds (1-4 Mbit/s for downlink and 1-7Mbit/s for uplik depending on version). Another advantage is ability to function with movable objects (eg. cars or drones). Higher bandwidth leads to grater circuit complexity and higher energy consumption related to it. -% -%As of writing this thesis (December 2023) LTE-M is coverted in 98.5 \% in Czechina by O2 \cite{o2catm} and mostly by Vodafone \cite{vodafonemap}. - -\section{5G IoT networks} -5G implementation into the mobile networks can be achieved via two methods \cite{5gnruk}: - -\begin{itemize} - \item NSA (non-stand alone) - 5G features are achieved by adding new RAN (Radio Access Network) to existing 4G LTE core. This approach implements dynamic spectrum sharing and enables rapid deployment of enhanced mobile broadband in customer market without larger changes in existing infrastructure. - \item SA (stand alone) - LTE core and RAN are completely replaced with 5G ones. RAN can however still switch back to LTE air interface to ensure backward compatibility with non-5G devices. -\end{itemize} - -In 2018, \ac{3GPP} Release number 15 laid down 5G specification named 5G NR (New Radio). Unlike LTE-A Pro that has just added more features to 4G LTE and operated in LTE standards and channels, 5G NR introduced a new physical layer in air interface \cite{5gnruk}. - -5G NR tries to solve three key aspects of wireless technology \cite{5gnruk}: - -\begin{itemize} - \item eMBB (Enhanced Mobile Broadband): Data-intensive applications needing large bandwidth for primarily traditional end-user demand, like video streaming. This should be achieved by Gigabit LTE, massive MIMO, mmWave technologies, spectrum sharing techniques and advanced channel coding. - \item mMTC (Massive Machine Type Communications): Low-power and low-cost applications with small data volumes but potentially large number of these devices in a small footprint. It is built on LTE LPWAN protocols like LTE-M and NB-IoT, making them potentially a core part of 5G. - \item URLLC (Ultra-reliable and Low-latency Communication): Mission-critical applications traditionally possible only by direct wire connection, necessary for real-time control of autonomous vehicles and industrial machinery. -\end{itemize} - -As of December 2023, 5G IoT networks are not yet commercially available in Czechia. - -%%%%%% -\subsection{URLLC requirements} - -URLLC (Ultra-Reliable and Low-Latency Communication) is a new requirement for 5G networks for providing real-time communication protocols with very low delays and very high levels of reliability. First attempts to address this were introduced in 4G LTE HRLLC (Higher-Reliability and Low-Latency Communication) in \ac{3GPP} release 15 \cite{5gamericasurllc}. Until this point, aspects of latency and reliability were -dealt in separately and sometimes were in direct contradiction to each other (reliability was achieved with repeated data redundancy, which multiplied latency). Combination of these two aspects is however essential for several critical applications with different requirements, as shown in table \ref{tab:urllc}: - -\begin{table}[!h] - \begin{center} - \small - \begin{tabular}{|l|c|c|c|} - \hline - Scenario & E2E latency [ms] & Reliability [\%] & Data rate [Mbps] \\\hline\hline - Discrete automation & 10 & 99.99 & 10 \\\hline - Process automation – remote control & 60 & 99.9999 & 100 \\\hline - Process automation ‒ monitoring & 60 & 99.9 & 1 \\\hline - Process automation ‒ monitoring & 40 & 99.9 & 10 \\\hline - Electricity distribution – high voltage & 5 & 99.9999 & 10 \\\hline - Intelligent transport systems & 30 & 99.9999 & 10 \\\hline - \end{tabular} - \end{center} - \caption[Performance requirements for URLLC]{Performance Requirements for Low-Latency and High-Reliability Scenarios \cite{5gamericasurllc}} - \label{tab:urllc} -\end{table} - - -\subsection{Latency} -With such strict latency requirements, as low as 5 ms end-to-end latency, it is necessary to minimize air interface delay (to 1 ms or less). To achieve such low latency, intensive optimization of air data delivery is necessary. - -There are several possible approaches that can lead to reduced communication time and latency \cite{5gamericasurllc}: - -\begin{itemize} - \item Frequent transmission opportunities -Downlink control channel used to carry scheduling information for data transmission is not usually monitored by end device for power saving reasons. However to reduce the waiting time for delivering the control information, the end device could do this. For device to start uplink transmission, it needs to send a scheduling request (SR) that allocates a specific transmission slot. To minimize the waiting time, the periodicity of the SR resource configuration should reflect latency requirements. This can be further emphasized by flexible schedulling timing mainly in Time Division Dulex (TDD). - - \item Flexible transmission duration -This aspect is supported in 5G using larger subcarier spacing. This shortens slot duration and gives bigger oportunity for quicker communication establishment. - - \item Grant-free (or configured grant) uplink transmission -In cases with very low latency demand, grant-free uplink transition, specific periodic uplink resource for device can be arranged. End device in this scenario does not need to wait for scheduling request and at any time it has data it can transmit in this arranged slot without a need for dynamic grant. - -\end{itemize} - -Air interface is only partially responsible for total end-to-end latency. Remaining latency is caused by core network, internet network and particular server with which the device is communicating. This is to be solved by new concept of Edge computing. Edge computing is a possibility for a mobile operator or another entity to move services from a remote server closer to the device and to execute necessary task right in 5G core network \cite{3gppurllc}. - -Another method of lowering transport network latency is to avoid transport network completly. This is experimented in vehicle-to-vehicle (V2V) protocols and in non-IP based communication \cite{5gamericav2v}. - -\subsection{URLLC reliability optimization} - -In \ac{3GPP} Release 16, redundant transmission for high-reliability communication was introduced \cite{5gamericasurllc}. With this method, user packets are duplicated and simultaneously transferred to the receiver via two disjoint user plane paths. The redundant packets are then eliminated at the receiver side. This further avoids occasional fails in one path propagation and slims probability of exceding the delay requirements. Other changes can be made in 5G core parameters settings, like QoS Monitoring, dynamic division of Packet Delay Budget and enhancements of session continuity \cite{3gppurllc}. diff --git a/text/uvod.tex b/text/uvod.tex index 52924d0..285254e 100644 --- a/text/uvod.tex +++ b/text/uvod.tex @@ -11,6 +11,8 @@ %The third and final part of the thesis describes the practical implementation of an IoT device using the nRF connect ecosystem, which is a set of tools and software for developing and testing IoT applications. It also demonstrates the MQTT communication protocol between the IoT device and a virtual server, which enables the exchange of data and commands in a secure and efficient manner. % +Tu uvod. + % 27 Popis 4G/5g % 28 Nordic a Quactel % 29 nRF s MQTT diff --git a/text/venek.tex b/text/venek.tex new file mode 100644 index 0000000..ce41d75 --- /dev/null +++ b/text/venek.tex @@ -0,0 +1,20 @@ +\chapter{Field application testing of nRF9161-DK} + +Externí interference: mikrovlnka… + +\begin{itemize} + \item Urban environment (industrial plant, underground spaces, bunkers) + \begin{itemize} + \item co testovat? + \item nějaká aplikační deska pro „průmysl“? + \end{itemize} + \item Rural environment (open field, forest) + + \item Herd monitoring application (Temp+RH, Accel, Light, GPS) + \begin{itemize} + \item GPS functionality + \item FOTA + \item ARM CryptoCell + \item ARM TrustZone + \end{itemize} +\end{itemize} diff --git a/text/vysledky.tex b/text/vysledky.tex deleted file mode 100644 index c94f8ce..0000000 --- a/text/vysledky.tex +++ /dev/null @@ -1,86 +0,0 @@ -\chapter{Practical demonstration} - -For practical demonstration of an IoT device with 4G/5G connectivity, a 4G development kit nRF9160 DK was selected. Demonstration of 5G connectivity could not be made due to a delay with delivery of the ordered Quectel module. - -Practical demonstration of an IoT device with LTE-M connectivity was made on an example of a combined burglary and fire alarm system with 4 sensors, transferring data to a remote cloud server via MQTT protocol, simulating a data transfer to a central security panel. - -\section{Hardware} - -nRF9160 DK development kit was adapted with an add-on board made from a universal line PCB with headers compatible to Arduino Uno form-factor fitting to nRF9160 DK headers. The add-on PCB contained connections for four sensors: - -\begin{itemize} - \item Hall effect sensor Texas Instruments DRV5033 \cite{haldatasheet}, with open-drain output (for pulled-up digital input) pulled down by an external magnetic field and simulating door/window switch, connected to GPIO pin P0.19. - \item analog thermometer Texas Instruments LM35 \cite{tempdatasheet}, with an analog output linearly corresponding to 10 mV for each oC above 0 oC, connected to GPIO pin P0.17. - \item passive infrared (PIR) motion sensor Hadson Technology HC-SR501 \cite{pirdatasheet} with digital output (3,3 VDC output reduced to 3 VDC level by a voltage divider), connected to GPIO pin P0.16. - \item sensor for combustible gases Pololu MQ-2 \cite{gasdatasheet}, with an analog ouput reduced by a voltage divider to avoid exceeding 3 VDC threshold, connected to GPIO pin P0.18. -\end{itemize} - -\begin{figure}[!h] - \begin{center} - \includegraphics[width=0.5\textwidth]{obrazky/ezsschema.png} - \end{center} - \caption[Overview of security and fire alarm]{Overview of security and fire alarm board} - \label{fig:ezsschema} -\end{figure} - -\begin{figure}[!h] - \begin{center} - \includegraphics[width=0.5\textwidth]{obrazky/ezspcb.png} - \end{center} - \caption[Schematic of security and fire demo]{Schematic of security and fire alarm demo} - \label{fig:ezspcb} -\end{figure} - - -\begin{figure}[!h] - \begin{center} - \includegraphics[width=0.9\textwidth]{obrazky/pcbphoto.jpg} - \end{center} - \caption[PCB schematic of alarm demo board]{PCB schematic for alarm demo} - \label{fig:ezsreal} -\end{figure} - -\newpage - -\section{Firmware tools} - -nRF Connect SDK was used as a software platform for the demo application. nRF Connect SDK is a unified software development kit for building products based on all Nordic nRF Series wireless devices. It integrates the Zephyr RTOS and wide range of samples, application protocols, protocol stacks, libraries and hardware drivers \cite{zephyrpp}. - -It offers a single code base for all Nordic devices and software components. It simplifies porting modules, libraries and drivers from one application to another, thus reducing development time. nRF Connect SDK is publicly available under OpenSource license, offers source code management with Git and has free nRF Connect for Visual Studio Code IDE support. Zephyr RTOS furthemore provides extensive amount of libraries including standardized access to basic peripheries, IP stack and MQTT library \cite{nrfsdk}. - -MQTT is a lightweight, publish-subscribe protocol that enables efficient and reliable communication between devices in the IoT domain. MQTT is based on a broker-client architecture, where a broker is a server that receives and routes messages from multiple clients, and a client is any device that can publish or subscribe to a topic. A topic is a hierarchical identifier that defines the content and scope of a message\cite{mqtt}. - -This firmware is based on nRF Connect SDK example named Simple MQTT\cite{nrfmqtt}. - -\section{Firmware outline} - -\subsection{LTE network connection} - -First task for the demo firmware is an establishment of a connection to LTE network. This is mostly handled by function \texttt{modem\_configure()}, which turns off power saving modes for better responsivity and calls HAL function \texttt{lte\_lc\_init\_and\_connect()}. - -\texttt{lte\_lc\_init\_and\_connect()} takes all modem settings from text config files transferred to macros by Kconfig. This ilustrates a possibility of cross-platform or regionally independent application, where only the config files for given platform or region are needed to be changed. - -\subsection{ADC configuration} -When connection with LTE network is successfully established, ADC is configured. Two analog input channels are used in this demo - AIN4 on P0.17 pin connected to LM35 temperature sensor and AIN5 on P0.18 connected to MQ-2 combustible gas sensor. For both channels, \texttt{adc\_channel\_cfg} structs are initialized and channels are set to 10bit resolution, internal 0.6 V reference voltage and 1/2 divider using \texttt{adc\_channel\_cfg()}, setting channels voltage range to 1.2 V. Both channels (if they are enabled by the button configuration) are then sampled in set interval using a custom fuction \texttt{adc\_sample()} and printed to USB serial. - -\subsection{Digital inputs and outputs} -For ease of implementation, digital sensors on GPIO pins P0.16 (DRV5033) and P0.19 (PIR) were added to the device tree as additional development kit buttons. This avoided the need for their own separate initialization and reading codes. - -These digital input sensors are then processed as buttons using callback handler \texttt{button\_handler()}. This function is called with bitmasks \texttt{button\_states} and \texttt{has\_changed}, making it ease to figure state change for these two sensors. - -Two buttons and two switchers are used for optionally disabling the corresponsing sensors. This is executed in \texttt{button\_handler()}. - -Four on-board LEDs are used for local signalization of status of PIR sensor (LED1) and Hall effect sensor (LED2), as well as over-threshold values of temperature (LED3) and combustible gas (LED4) sensors. - -\subsection{MQTT} - -Communication with MQTT server is done by zephyr/net/mqtt.h library. Connection with the server is attempted after LTE and sensors setup with function \texttt{mqtt\_connect()}. -Publishing of message is achieved by function \texttt{mqtt\_publish()} upon a digital sensor is activated or analog sensor exceeds the set threshold value. Example of the MQTT communication sent to a virtual server is shown in figure \ref{fig:mqttcom}. - -\begin{figure}[!h] - \begin{center} - \includegraphics[width=0.2\textwidth]{obrazky/mqttcom.png} - \end{center} - \caption[Demo MQTT communication]{Sample of resulting MQTT communication} - \label{fig:mqttcom} -\end{figure} diff --git a/text/zhodnoceni.tex b/text/zhodnoceni.tex new file mode 100644 index 0000000..1e7eda6 --- /dev/null +++ b/text/zhodnoceni.tex @@ -0,0 +1,8 @@ +\chapter{Discussion} + + +\begin{itemize} + \item Scénáře použití IoT, vhodnost jednotlivých druhů komunikace pro ně Navrhněte scénáře a možnosti využití 4G/5G komunikace a využívaných standardů (URLLC, LTE-M, NB-IoT) pro průmyslovou IoT komunikaci. + + \item Srovnání experimentálnách výsledků protokolů s teoretickými předpoklady Proveďte detailní měření parametrů. Získané údaje zpracujte a srovnejte s teoretickými předpoklady a jinými v současnosti používanými komunikačními systémy. +\end{itemize} -- cgit v1.2.3