summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMichal Hanus <mikehanus@protonmail.com>2024-03-31 21:24:01 +0200
committerMichal Hanus <mikehanus@protonmail.com>2024-03-31 21:24:01 +0200
commitdcae801533e050242d69c78ecc6b59a492a7024f (patch)
treee97ebfe95ef75bf103bb602f2db729497b55b999
parent9f280c29bb372407bb2ee06dc054271375216804 (diff)
Smysl osnovy snad splnen
-rw-r--r--.gitignore1
-rw-r--r--bakalarka.pdfbin4895283 -> 4913243 bytes
-rw-r--r--bakalarka.tex6
-rw-r--r--nastaveni.tex2
-rw-r--r--pdf/student-desky.pdfbin468516 -> 468517 bytes
-rw-r--r--pdf/student-titulka.pdfbin39804 -> 39820 bytes
-rw-r--r--pdf/student-zadani-cs.pdf (renamed from pdf/student-zadani-en.pdf)bin1369815 -> 1369578 bytes
-rw-r--r--pdf/student-zadani.pdfbin1369618 -> 1370475 bytes
-rw-r--r--text/protokolyLPWAN.tex95
-rw-r--r--text/uvod.tex28
-rw-r--r--text/zaver.tex23
11 files changed, 65 insertions, 90 deletions
diff --git a/.gitignore b/.gitignore
index e964244..ae200d1 100644
--- a/.gitignore
+++ b/.gitignore
@@ -299,3 +299,4 @@ TSWLatexianTemp*
# option is specified. Footnotes are the stored in a file with suffix Notes.bib.
# Uncomment the next line to have this generated file ignored.
#*Notes.bib
+zdroje
diff --git a/bakalarka.pdf b/bakalarka.pdf
index 1fc5d33..2b2705b 100644
--- a/bakalarka.pdf
+++ b/bakalarka.pdf
Binary files differ
diff --git a/bakalarka.tex b/bakalarka.tex
index 29b47be..73768eb 100644
--- a/bakalarka.tex
+++ b/bakalarka.tex
@@ -179,7 +179,7 @@
\includepdf[pages=1]% buďto generovaného informačním systémem
{pdf/student-titulka}% název souboru nesmí obsahovat mezery!
%% NEBO vytvoření titulní stránky z balíčku
-%\maketitle
+% \maketitle
%%
\oddpage % při dvojstranném tisku se přidá prázdná stránka
@@ -237,7 +237,7 @@
%%% Vložení souboru 'text/reseni' s popisem řešení práce
% (rozdělte na více souborů či kapitol, pokud je vhodné)
-\include{text/protokolyLPWA}
+\include{text/protokolyLPWAN}
\include{text/chipy}
@@ -249,7 +249,7 @@
\include{text/zhodnoceni}
-include{text/zaver}
+\include{text/zaver}
%%% Vložení souboru 'text/literatura' se seznamem zdrojů
\include{text/literatura}
diff --git a/nastaveni.tex b/nastaveni.tex
index 3a29ccf..6096597 100644
--- a/nastaveni.tex
+++ b/nastaveni.tex
@@ -62,7 +62,7 @@
%%% Označení oboru studia
% Parametr ve složených závorkách {} je název oboru v originálním jazyce,
% parametr v hranatých závorkách [] je překlad
-\specialization[Teleinformatics]{Teleinformatika}
+% \specialization[Teleinformatics]{Teleinformatika}
%%% Označení ústavu
% Parametr ve složených závorkách {} je název ústavu v originálním jazyce,
diff --git a/pdf/student-desky.pdf b/pdf/student-desky.pdf
index 2e3c370..15695c8 100644
--- a/pdf/student-desky.pdf
+++ b/pdf/student-desky.pdf
Binary files differ
diff --git a/pdf/student-titulka.pdf b/pdf/student-titulka.pdf
index a06b0e3..6122a92 100644
--- a/pdf/student-titulka.pdf
+++ b/pdf/student-titulka.pdf
Binary files differ
diff --git a/pdf/student-zadani-en.pdf b/pdf/student-zadani-cs.pdf
index 7ce2bb4..ffa7c02 100644
--- a/pdf/student-zadani-en.pdf
+++ b/pdf/student-zadani-cs.pdf
Binary files differ
diff --git a/pdf/student-zadani.pdf b/pdf/student-zadani.pdf
index 6c5529a..65954fd 100644
--- a/pdf/student-zadani.pdf
+++ b/pdf/student-zadani.pdf
Binary files differ
diff --git a/text/protokolyLPWAN.tex b/text/protokolyLPWAN.tex
index 6387a49..69870c4 100644
--- a/text/protokolyLPWAN.tex
+++ b/text/protokolyLPWAN.tex
@@ -35,68 +35,22 @@
%\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}
+\section{Established communication standards for IoT devices}
-\begin{itemize}
- \item doplnit GSM, LoRa, Zigbee, Sigfox, Wifi, ESP32, 433 MHz
-\end{itemize}
+\colorbox{orange}{doplnit GSM, LoRa, Zigbee, Sigfox, Wifi, ESP32, 433 MHz} \\
-\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}
+\section{4G IoT networks (LPWAN)}
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.
+%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 supposed 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}.
+\colorbox{orange}{Kajsik zrcadlova $\lambda$ krivka} \\
+
\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}.
@@ -123,7 +77,6 @@ Single NB-IoT communication channel corresponds to a single 180 kHz LTE frequenc
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.
%
@@ -150,7 +103,12 @@ As of writing this thesis (December 2023) LTE-M is covered in Czechia by O2 in 9
%
%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}
+\subsection{Comparison of 4G LPWAN with established technologies}
+
+\section{Cellular 5G IoT networks}
+
+\colorbox{orange}{Kajsik 5G trojuhelnik}
+
5G implementation into the mobile networks can be achieved via two methods \cite{5gnruk}:
\begin{itemize}
@@ -173,6 +131,8 @@ As of December 2023, 5G IoT networks are not yet commercially available in Czech
%%%%%%
\subsection{URLLC requirements}
+\colorbox{orange}{Zestrucnit} \\
+
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}:
@@ -202,10 +162,10 @@ There are several possible approaches that can lead to reduced communication tim
\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).
+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 scheduling timing mainly in Time Division Duplex (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.
+This aspect is supported in 5G using larger subcarrier spacing. This shortens slot duration and gives bigger opportunity 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.
@@ -214,8 +174,25 @@ In cases with very low latency demand, grant-free uplink transition, specific pe
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}.
+Another method of lowering transport network latency is to avoid transport network completely. This is experimented in vehicle-to-vehicle (V2V) protocols and in non-IP based communication \cite{5gamericav2v}.
+
+\subsection{Cellular 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 exceeding 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}.
+
+\subsection{Shortcomings of cellular URLLC and time horizon}
-\subsection{URLLC reliability optimization}
+\section{DECT NR+ standard for 5G IoT networks}
-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}.
+\subsection{Plain DECT}
+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\#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
diff --git a/text/uvod.tex b/text/uvod.tex
index 285254e..da70113 100644
--- a/text/uvod.tex
+++ b/text/uvod.tex
@@ -1,19 +1,15 @@
\chapter*{Introduction}
-%\phantomsection
-%\addcontentsline{toc}{chapter}{Introduction}
-%
-%AI, ale fakticky ok:
-%
-%The main objective of this thesis is to provide a comprehensive overview of the 4G and 5G cellular networks and their applications for the internet-of-things (IoT) domain. The first part of the thesis focuses on the theoretical aspects of the IoT protocols that are specifically designed to meet the requirements and challenges of the IoT scenarios, such as low power consumption, high reliability, and scalability. It also compares and contrasts the different protocols and evaluates their performance and suitability in the existing 4G and 5G networks.
-%
-%The second part of the thesis presents a detailed analysis of the various hardware components that are available for building IoT devices, such as chips, modules, and development kits. It also discusses the advantages and disadvantages of each component and provides some recommendations for choosing the best option for a given project.
-%
-%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.
-%
+\phantomsection
+\addcontentsline{toc}{chapter}{Introduction}
-Tu uvod.
+%\section{Current situation}
-% 27 Popis 4G/5g
-% 28 Nordic a Quactel
-% 29 nRF s MQTT
-% 30 teplota a hodit tam kód
+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}.
+
+\colorbox{orange}{Graf IoT zarizeni here} \\
diff --git a/text/zaver.tex b/text/zaver.tex
index 2fc9d02..5316a0e 100644
--- a/text/zaver.tex
+++ b/text/zaver.tex
@@ -1,15 +1,16 @@
-\chapter{Conclusions for the follow-up bachelor thesis}
+\chapter*{Conclusion}
This semestral thesis provided a brief introduction to 4G/5G mobile networks for the Internet of Things (IoT) applications in the embedded electronic systems. Related communication protocols for 4G IoT networks (LPWAN NB-IoT and LTE-M) and 5G IoT networks (5G NR - URLLC) were described and a survey of two selected chipsets for 4G networks (Nordic Semiconductor nRF9160) and 5G networks (Quectel RM520N) and their development modules and kits was made.
-One of the development kits (nRF9160 DK) was then used for practical demonstration of an IoT device with LPWAN connectivity on an example of a combined burglary and fire alarm system with 4 sensors, transferring data to a remote cloud server via MQTT protocol. This demo allowed to establish a firmware development base for 4G IoT devices based on nRF9160 System-in-Package and get familiarized with the software development kit by Nordic Semiconductor with Zephyr RTOS support.
-Since there seem to be issues with a delivery of the appropriate 5G development kit by Quectel, being ordered for several months already, it would be advisable to focus the follow-up bachelor thesis only to 4G communication kits with nRF9160 System-in-Package and to further explore extensive firmware possibilities of this system for reliable and secure industrial IoT communication, specifically:
-
-\begin{itemize}
- \item Firmware upgrades via FOTA (firmware over the air)
- \item Implementation of ARM TrustZone technology for firmware protection against unauthorized changes
- \item ARM CryptoCell solution for high-performance cryptography
-\end{itemize}
-
-Experimental parameters of IoT communication (power consumption, lattency, reliability, effective range in complicated urban environment) shall also be verified, comparatively for NB-IoT and LTE-M protocols.
+%One of the development kits (nRF9160 DK) was then used for practical demonstration of an IoT device with LPWAN connectivity on an example of a combined burglary and fire alarm system with 4 sensors, transferring data to a remote cloud server via MQTT protocol. This demo allowed to establish a firmware development base for 4G IoT devices based on nRF9160 System-in-Package and get familiarized with the software development kit by Nordic Semiconductor with Zephyr RTOS support.
+%
+%Since there seem to be issues with a delivery of the appropriate 5G development kit by Quectel, being ordered for several months already, it would be advisable to focus the follow-up bachelor thesis only to 4G communication kits with nRF9160 System-in-Package and to further explore extensive firmware possibilities of this system for reliable and secure industrial IoT communication, specifically:
+%
+%\begin{itemize}
+% \item Firmware upgrades via FOTA (firmware over the air)
+% \item Implementation of ARM TrustZone technology for firmware protection against unauthorized changes
+% \item ARM CryptoCell solution for high-performance cryptography
+%\end{itemize}
+%
+%Experimental parameters of IoT communication (power consumption, lattency, reliability, effective range in complicated urban environment) shall also be verified, comparatively for NB-IoT and LTE-M protocols.