bez diskuze a zaveru

21 files changed, 494 insertions, 203 deletions

diff --git a/bakalarka.pdf b/bakalarka.pdf
new file mode 100644
index 0000000..c8e93c4
--- /dev/null
+++ b/bakalarka.pdf
diff --git a/bakalarka.tex b/bakalarka.tex
index e012eb7..fa111c0 100644
--- a/bakalarka.tex
+++ b/bakalarka.tex
@@ -265,8 +265,6 @@
 
 \include{text/mobil}
 
-\include{text/vesmir}
-
 \include{text/zhodnoceni}
 
 \include{text/zaver}
diff --git a/bakalarka.toa b/bakalarka.toa
index f20a1d8..32c2367 100644
--- a/bakalarka.toa
+++ b/bakalarka.toa
@@ -1,5 +1,5 @@
-\contentsline {chapter}{\numberline {A}Result measurement tables }{59}{chapter.186}%
-\contentsline {chapter}{\numberline {B}Result of measurement - charts }{66}{chapter.211}%
-\contentsline {section}{\numberline {B.1}nRF9161 }{70}{section.228}%
-\contentsline {section}{\numberline {B.2}nRF9160 }{86}{section.295}%
-\contentsline {chapter}{\numberline {C}Demonstrator electronic schemes }{103}{chapter.362}%
+\contentsline {chapter}{\numberline {A}Result measurement - tables }{67}{chapter.215}%
+\contentsline {chapter}{\numberline {B}Result of measurement - charts }{68}{chapter.216}%
+\contentsline {section}{\numberline {B.1}nRF9161 }{68}{section.217}%
+\contentsline {section}{\numberline {B.2}nRF9160 }{85}{section.284}%
+\contentsline {chapter}{\numberline {C}Demonstrator electronic schemes }{86}{chapter.285}%
diff --git a/nastaveni.tex b/nastaveni.tex
index 6613c32..d802067 100644
--- a/nastaveni.tex
+++ b/nastaveni.tex
@@ -109,12 +109,18 @@
 
 %%% Abstrakt
 \abstract[
-	%Tato semestrální práce se zabývá úvodem do problematiky elektronických zařízení s 4G/5G mobilní konektivitou pro internet věcí (IoT). Práce popisuje související komunikační protokoly LPWAN (NB-IoT, LTE-M) a URLLC, spolu s parametry dvou vybraných komunikačních čipsetů  Quectel RM520N a Nordic Semiconductor nRF9160 a dostupných vývojových modulů tyto čipsety využívajících. Jeden z těchto vývojových modulů (nRF9160 DK) byl použit k praktické ukázce IoT zařízení s LPWAN konektivitou na příkladu kombinovaného zabezpečovacího a požárního elektronického systému se 4 senzory a přenosem dat na vzdálený virtuální server pomocí MQTT protokolu. Závěrem této semestrální práce je přehled plánovaných prací v navazujícím bakalářském projektu.
-	!!!TODO!!!
+Rostoucí počet propojených zařízení internetu věcí (IoT) a jejich narůstající složitost kladou nové požadavky na dosah, spolehlivost a škálovatelnost komunikačních sítí. Mobilní sítě 4G a 5G nabízejí slibné řešení pro komunikaci s nízkou spotřebou energie na velké vzdálenosti. Tato práce se zabývá základními principy mobilních sítí 4G a 5G se zaměřením na jejich architekturu, komunikační protokoly a specifické funkce relevantní pro případy užití v IoT. Dále analyzuje protokoly nízkoenergetických širokopásmových sítí (LPWAN), konkrétně NB-IoT a LTE-M, zdůrazňuje jejich výhody, omezení a rozdíly ve srovnání s tradičními mobilními sítěmi.
+
+Práce také poskytuje přehled čipsetů Nordic Semiconductor nRF9160 a nRF9161, spolu s recenzí komerčně dostupných vývojových modulů. Na základě tohoto výzkumu je vybrán vývojový kit Connexio Pro pro jeho podporu NB-IoT/LTE-M a integrované funkce vhodné pro rychlé prototypování IoT zařízení. Pro demonstraci praktického využití je pomocí vybraného kitu vyvinuta univerzální nízkonákladová trackovací aplikace, zaměřená na simulaci reálných scénářů, jako je vzdálené monitorování, chytré zemědělství, chytrá města a sledování majetku.
+
+Byly provedeny laboratorní experimentální měření zaměřená na klíčové komunikační parametry, jako je spotřeba energie, síla signálu a propustnost dat. Shromážděná data byla analyzována a porovnána s teoretickými očekáváními, stejně jako s jinými běžně používanými komunikačními systémy, za účelem vyhodnocení vhodností pro průmyslové IoT aplikace. Na závěr byla provedena experimentální měření v terénu, aby se ověřila schopnost navržených scénářů komunikovat v mobilním prostředí.
 ]{
-This bachelor's thesis provides an introduction to 4G/5G mobile networks for the Internet of Things (IoT) applications in the embedded electronic systems. Related communication protocols LPWAN (NB-IoT, LTE-M) and DECT-NR+ are mentioned. The selected chipset Nordic Semiconductor nRF9160/nRF9161 are described, together with their available development kits.
-Scenarios for industrial usage are outlined and demonstrated with the selected development kit !!!TODO!!!. These include a universal low-cost tracker with additional potentional sensors and staionary low-power sensoric unit for remote reading, ((wireless version of experimental measuring for in-field usage)).
-In the frame of these demonstration applications relevant detailed measurements are made and elaborated in contract to theoretical assumptions and expected results.
+The growing number of interconnected Internet of Things (IoT) devices and their increasing complexity are placing new demands on range, reliability, and scalability of communication networks. 4G and 5G cellular networks offer a promising solution for wide-area low-power communication.  This thesis explores the fundamental principles of 4G and 5G mobile networks with a focus on their architecture, communication protocols, and specific features relevant to IoT use cases.  It further analyzes Low-Power Wide-Area Network (LPWAN) protocols, specifically NB- IoT and LTE-M, highlighting their advantages, limitations, and differences compared to traditional mobile networks. 
+
+The work also provides an overview of the Nordic Semiconductor nRF9160 and nRF9161 chipsets, along with a review of commercially available development modules.  Based on this research, the Connexio Pro development kit is selected for its support of NB-IoT/LTE-M and integrated features suitable for rapid prototyping of IoT devices.  To demonstrate practical usage, a universal low-cost tracking application is developed using the selected kit, aimed to simulate real-world scenarios such as remote monitoring, smart agriculture, smart cities, and asset tracking.
+
+Laboratory experimental measurements were carried out, focusing on key communication parameters such as power consumption, signal strength, and data throughput. The collected data were analyzed and compared with theoretical expectations as well as other commonly used communication systems to evaluate performance and suitability for industrial IoT applications.
+Lastly in-field experimental measurements were carried out in the field to verify ability of suggested scenarios to communicate in mobile setting.
 }
 
 %%% Klíčová slova
diff --git a/obrazky/connexiopro.jpg b/obrazky/connexiopro.jpg
new file mode 100644
index 0000000..29d4bb3
--- /dev/null
+++ b/obrazky/connexiopro.jpg
diff --git a/obrazky/demofelda.jpg b/obrazky/demofelda.jpg
new file mode 100644
index 0000000..b70fd59
--- /dev/null
+++ b/obrazky/demofelda.jpg
diff --git a/obrazky/maplteband.png b/obrazky/maplteband.png
new file mode 100644
index 0000000..5fe5ff8
--- /dev/null
+++ b/obrazky/maplteband.png
diff --git a/obrazky/mapltem.png b/obrazky/mapltem.png
new file mode 100644
index 0000000..a09de2b
--- /dev/null
+++ b/obrazky/mapltem.png
diff --git a/obrazky/mapnbiot.png b/obrazky/mapnbiot.png
new file mode 100644
index 0000000..90c45ae
--- /dev/null
+++ b/obrazky/mapnbiot.png
diff --git a/obrazky/mqttcom2.png b/obrazky/mqttcom2.png
new file mode 100644
index 0000000..c8d68b5
--- /dev/null
+++ b/obrazky/mqttcom2.png
diff --git a/text/chipy.tex b/text/chipy.tex
index 433e9b0..786bb32 100644
--- a/text/chipy.tex
+++ b/text/chipy.tex
@@ -195,10 +195,9 @@ Comparisons of the main parameters of the most common nRF9160 boards is provided
 	\label{fig:sip61front}
 \end{figure}
 
-nRF9161 is evolution of nRF9160 in same form-factor  and it enables every function of its predecessor with additional and improved capabilities such as implementation of 3GPP Release 14 LTE-M/NB-IoT LTE stack and support for alternative modem firmware for \ac{DECT NR+} stack operating on 1.9 GHz band. Switching between \ac{LTE} and \ac{DECT NR+} is done by loading given firmware to modem part of the \ac{SiC}. \cite{cite}
+nRF9161 is evolution of nRF9160 in same form-factor  and it enables every function of its predecessor with additional and improved capabilities such as implementation of 3GPP Release 14 LTE-M/NB-IoT LTE stack and support for alternative modem firmware for \ac{DECT NR+} stack operating on 1.9 GHz band. Switching between \ac{LTE} and \ac{DECT NR+} is done by loading given firmware to modem part of the \ac{SiC}. \cite{nrfdect}
 
-This means that application such LTE and \ac{DECT NR+} gateway would by using only nRF9161 need two of them (even though technologically dubious not so much from financial sense considering \texteuro 23 for single \ac{SiC}) \cite{}
-% https://cz.mouser.com/ProductDetail/Nordic-Semiconductor/NRF9161-LACA-R
+This means that application such LTE and \ac{DECT NR+} gateway would by using only nRF9161 need two of them (even though technologically dubious not so much from financial sense considering \texteuro 23 for single \ac{SiC}).
 
 Capabilities and description of DECT NR+ can be found in chapter \ref{dectdescrition}.
 
@@ -212,7 +211,8 @@ Capabilities and description of DECT NR+ can be found in chapter \ref{dectdescri
 	\label{fig:sip51front}
 \end{figure}
 
-nRF9151 is another evolution o nRF9151. Its main advantages are smaller footprint (reduction of 20 \%), additional  Power Class 5 (20 dBm) support for LTE stack and promise of eventual addition for \ac{NTN} \cite{cite}.
+nRF9151 is another evolution o nRF9151. Its main advantages are smaller footprint (reduction of 20 \%), additional  Power Class 5 (20 dBm) support for LTE stack and promise of eventual addition for \ac{NTN}
+\cite{nrf51}.
 
 
 
@@ -242,7 +242,7 @@ nRF9160 DK is an official pre-certified development kit for nRF9160 made and sup
 	\label{fig:dk61front}
 \end{figure}
 
-nRF9161 DK is nRF9160 but with nRF9161 instead of nRF9160 and USB-C. TODO: rozepsat
+nRF9161 DK is nRF9160 but with nRF9161 instead of nRF9160 and USB-C.
 
 \subsubsection{nRF9151 DK}
 
@@ -254,7 +254,7 @@ nRF9161 DK is nRF9160 but with nRF9161 instead of nRF9160 and USB-C. TODO: rozep
 	\label{fig:dk51front}
 \end{figure}
 
-nRF9161 DK is nRF9161 DK but with nRF9151 instead of nRF9161. TODO: rozepsat
+nRF9161 DK is nRF9161 DK but with nRF9151 instead of nRF9161.
 
 
 
@@ -283,9 +283,7 @@ Nordic Thingy:91, also made by Nordic Semiconductor, is a compact small-factor m
 
 %Nordic Thingy:91X, also made by Nordic Semiconductor, is a compact small-factor module used as a rapid prototyping battery-operated platform, containing LTE-M/NB-IoT/\ac{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
 
-Thingy:91X is Thingy:91 but with nRF9161 instead of nRF9160 and \ac{Wi-Fi} chip nRF7001. TODO: rozepsat
-
-\cite{thingyxdesc}.
+Thingy:91X is Thingy:91 but with nRF9161 instead of nRF9160 and Wi-Fi chip nRF7001. \cite{thingyxdesc}.
 
 % https://www.nordicsemi.com/-/media/Software-and-other-downloads/Product-Briefs/nRF9151-SiP-PB-v1.2.pdf
 
@@ -410,16 +408,14 @@ Connexio Stratus, a crowd-funded development board, has a similar design to the
 
 \begin{figure}[H]
   \begin{center}
-	  \includegraphics[width=0.4\textwidth]{obrazky/connexio.jpg}
+	  \includegraphics[width=0.8\textwidth]{obrazky/connexiopro.jpg}
   \end{center}
-	\caption[Connexio Stratus]{Connexio Stratus\cite{connexiodesc}}
+	\caption[Connexio Stratus Pro]{Connexio Stratus Pro\cite{connexiodesc}}
 	\label{}
 \end{figure}
 
-Connexio Stratus Pro, 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
-
 
-Connexio Stratus Pron is Connexio Stratus but with nRF9151 instead of nRF9160. TODO: rozepsat
+Connexio Stratus Pro is largely based on Connexio Stratus but it uses nRF9151 instead of nRF9160.
 
 \cite{connexiodesc}.
 
diff --git a/text/demohw.tex b/text/demohw.tex
index a457d03..1674037 100644
--- a/text/demohw.tex
+++ b/text/demohw.tex
@@ -1,34 +1,35 @@
 %\chapter{Demonstration tracker}
 
 \chapter{Practical demonstration - tracker with meteo sensor}
+\label{chap:demo}
 
 For practical demonstration of an IoT device with 4G/5G connectivity, a development kit Connexio Pro with nRF9161 was selected. 
 
-Practical demonstration of an IoT device with LTE-M or NB-IoT connectivity was made on an example of an GPS tracker with meteo sensor, transferring data to a remote cloud server via MQTT protocol, simulating a data transfer to a central panel.
+Practical demonstration of an IoT device with LTE-M or NB-IoT connectivity was made on an example of an GPS tracker with meteo sensor, transferring data to a remote cloud server via MQTT protocol, simulating a data transfer to a central panel. For mobile field testing the GNSS was disabled due to long time needed to get fixed location and that get connection to LTE network. Both of these action will reset the state to the other so the behavior is very similar to cold start.
 
 \section{Hardware}
 
-nRF9161 DK development kit was adapted with an add-on board made from a universal line \ac{PCB} with headers fitting to Connexio Pro headers. The add-on PCB contained connections Li-ion accumulator and meteo sensor BME680.
+Connexio Pro development kit was adapted with an add-on board made from a universal line \ac{PCB} with headers fitting to its headers. The add-on PCB contains connections for Li-ion accumulator and meteo sensor BME680.
 
-Electronic and PCB schemes with 3D render of PCB can be found in appendix \ref{chap:demoapp}.
+Electronic and PCB schemes with 3D render of PCB can be found in appendix \ref{appendix:demoapp}.
 
 \begin{figure}[!h]
   \begin{center}
 	  \includegraphics[width=0.5\textwidth]{obrazky/32_PCB3.JPG}
   \end{center}
-	\caption[Overview of security and fire alarm]{Overview of security and fire alarm board}
-	\label{fig:pcb1}
+	\caption[PCB of demonstrator tracker]{PCB of demonstrator tracker}
+	\label{fig:pcb2}
 \end{figure}
 
+
 \begin{figure}[!h]
   \begin{center}
-	  \includegraphics[width=0.5\textwidth]{obrazky/32_PCB3.JPG}
+	  \includegraphics[width=0.5\textwidth]{obrazky/33_in_case1.JPG}
   \end{center}
-	\caption[Overview of security and fire alarm]{Overview of security and fire alarm board}
-	\label{fig:pcb2}
+	\caption[Demonstrator tracker in 3D printed case]{Demonstrator tracker in 3D printed case}
+	\label{fig:pcb1}
 \end{figure}
 
-
 \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}.
@@ -37,7 +38,7 @@ It offers a single code base for all Nordic devices and software components. It
 
 \ac{MQTT} is a lightweight, publish-subscribe protocol that enables efficient and reliable communication between devices in the IoT domain. \ac{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 \ac{MQTT}\cite{nrfmqtt}.
+This firmware is based on nRF Connect SDK example named Simple \ac{MQTT}\cite{nrfmqtt} and GNSS example.
 
 \section{Firmware outline}
 
@@ -47,18 +48,6 @@ First task for the demo firmware is an establishment of a connection to LTE netw
 
 \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 corresponding 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()}.
@@ -66,8 +55,14 @@ Publishing of message is achieved by function \texttt{mqtt\_publish()} upon a di
 
 \begin{figure}[!h]
   \begin{center}
-    \includegraphics[width=0.2\textwidth]{obrazky/mqttcom.png}
+    \includegraphics[width=0.4\textwidth]{obrazky/mqttcom2.png}
   \end{center}
 	\caption[Demo MQTT communication]{Sample of resulting MQTT communication}
 	\label{fig:mqttcom}
 \end{figure}
+
+\subsection{Application loop}
+
+The program after establishing LTE connection enters main loop which main where it disables LTE, enable GNSS and waits for modem to get from GNSS fixed location. After that it disables GNSS, enables LTE, waits for LTE connection to be established.
+
+With fresh location data it loads data over I2C from BME680 meteo sensor and gets from modem values about radio connection with \ac{BTS}. All these data are than transmitted using MQTT to remote server. After this program waits for specified time and than runs the loop again.
\ No newline at end of file
diff --git a/text/labina.tex b/text/labina.tex
index 30514b2..4664183 100644
--- a/text/labina.tex
+++ b/text/labina.tex
@@ -103,6 +103,7 @@ PDP context info 1:
 
 Another two commands are \texttt{link sysmode} for switching between NB-IoT and LTE-M and \texttt{link funmode} for turning the modem to and from flight-mode for save antenna and attenuators reconfiguration.
 
+
 \section{Power consumption - ampere meter}
 
 Power consumption can be accurately measured with negligible influenced by introduction of additional measurement equipment so measurement with external meter was chosen over the modem estimates or table values. For the power consumption evaluation of \ac{IoT} devices there are two different factors to consider. First is standby or sleep power that is usually long (orders of minutes or hours) and very small (orders of miliamps) and second are short rapid transmission spikes in orders of amperes. This requires ampere meter with very high sampling speed and very high dynamic range.
@@ -117,7 +118,6 @@ For measuring of power consumption was done using Nordic \ac{PPK II}, seen in pi
 	\label{fig:ppk}
 \end{figure}
 
-
 Its key features are \cite{ppkdatasheet}:
 \begin{itemize}
     \item 200nA to 1A current measurement range with a resolution that varies between 100nA and 1mA
@@ -127,16 +127,25 @@ Its key features are \cite{ppkdatasheet}:
     \item Supported through nRF Connect for Desktop's Power Profiler app
 \end{itemize}
 
-The measurement setup of nRF9161 DK with PPK II in EMC chamber and addition attenuators can be seen in figure \ref{fig:ppkmeas}. These development kits from Nordic enable a direct connection of serial ampere meter using special pins. This is them main reason why both boards were chosen for this measurement. 
+The measurement setup of nRF9161 DK with PPK II in EMC chamber and addition attenuators can be seen in figure \ref{fig:ppkmeas}. Antennas connected to the other end of coaxial cable can be seen in figure \ref{fig:emcant}. These development kits from Nordic enable a direct connection of serial ampere meter using special pins. This is them main reason why both boards were chosen for this measurement. 
 
 \begin{figure}[H]
 	\begin{center}
-		\includegraphics[width=0.6\textwidth]{obrazky/nrfppkemc.jpg}
+		\includegraphics[width=0.8\textwidth]{obrazky/nrfppkemc.jpg}
 	\end{center}
 	\caption[Nordic PPK II measuring setup]{Nordic Power Profiler Kit II measuring setup with nRF9161 in EMC chamber\cite{ppkdatasheet}}
 	\label{fig:ppkmeas}
 \end{figure}
 
+\begin{figure}[H]
+	\begin{center}
+		\includegraphics[width=0.6\textwidth]{obrazky/31_anthenna3.JPG}
+	\end{center}
+	\caption[Custom LTE antenna for bands around 800 MHz]{Custom LTE antenna for bands around 800 MHz}
+	\label{fig:emcant}
+\end{figure}
+
+
 The output of PPK II can be seen in figure \ref{fig:ltemcurr} for LTE-M and and in figure \ref{fig:nbiotcurr}.
 
 Yellow vertical lines mark a start of ping set and red vertical it end. These boundaries were set due to noise manually.
@@ -160,15 +169,184 @@ Green horizontal line indicates average draw in idle state where the modem does
 
 Another value that is calculated from these data and cannot be depicted in the chart is the raw charge needed for transmission of one packet. This is calculated by integration of the current over time set by the boundaries. This value expressed in coulombs or more commonly in mAh.
 
-\section{Results}
+\section{Cellular Results}
+
+Data described in sections above are aggregated into data tables using Python scripts. Example of such table can be seen in table \ref{tab:ltem61_1024ex}. Complete data for both LTE modes and all payload sizes are, for their large extent, placed in Appendix \ref{appendix:ltetables}.
+
+\begin{table}[!h]
+    \begin{center}
+        \small
+\hspace*{-2cm}\begin{tabular}{rrrrrrrrrrrr}
+\hline
+KU & RSRP & SNR & RT min & RT max & RT avg & Transmit & Max I & Ready I & Standby I & Charge & DR \\
+{[dB]} & {[dBm]} & {[dB]} & {[ms]} & {[ms]} & {[ms]} & {[s]} & {[mA]} & {[mA]} & {[mA]} & {[uAh]} & {[kB/s]} \\\hline
+
+0 & -75 & 1 & 1190 & 4500 & 3146 & 3.57 & 233.39 & 30.90 & 2.38 & 37.16 & 0.30 \\
+3 & -77 & 2 & 1039 & 3731 & 1869 & 1.95 & 222.60 & 31.11 & 2.21 & 19.20 & 0.56 \\
+6 & -82 & -1 & 983 & 2201 & 1618 & 1.74 & 220.29 & 31.56 & 2.71 & 17.59 & 0.63 \\
+10 & -84 & 2 & 1089 & 3103 & 1634 & 1.79 & 217.21 & 30.82 & 2.35 & 18.38 & 0.61 \\
+16 & -89 & 2 & 994 & 2888 & 1379 & 1.53 & 217.21 & 31.03 & 2.32 & 17.08 & 0.71 \\
+20 & -94 & 1 & 1089 & 2618 & 1660 & 1.72 & 222.60 & 31.56 & 5.71 & 19.04 & 0.63 \\
+21 & -92 & 3 & 1037 & 1542 & 1254 & 1.48 & 222.60 & 30.60 & 0.60 & 16.80 & 0.74 \\
+26 & -98 & 4 & 976 & 1364 & 1162 & 1.32 & 222.60 & 30.52 & 2.36 & 15.51 & 0.82 \\
+30 & -101 & 4 & 961 & 1670 & 1244 & 1.40 & 225.68 & 31.01 & 0.82 & 16.44 & 0.78 \\
+36 & -109 & 3 & 1127 & 1562 & 1327 & 1.52 & 221.83 & 30.58 & 2.02 & 17.68 & 0.72 \\
+40 & -112 & 4 & 1315 & 2352 & 1737 & 1.94 & 224.91 & 28.93 & 2.38 & 27.68 & 0.56 \\
+46 & -119 & 3 & 1370 & 2040 & 1717 & 1.92 & 248.06 & 28.84 & 2.22 & 34.42 & 0.57 \\
+50 & -124 & 1 & 1734 & 2917 & 2228 & 2.44 & 224.91 & 31.18 & 2.22 & 55.45 & 0.45 \\
+51 & -124 & 2 & 1645 & 2501 & 2072 & 2.30 & 224.91 & 30.13 & 2.22 & 53.41 & 0.47 \\
+56 & -131 & -3 & 3393 & 5091 & 4307 & 4.54 & 226.45 & 31.08 & 2.42 & 115.42 & 0.24 \\
+60 & -133 & -5 & 11772 & 13685 & 12833 & 11.91 & 222.60 & 29.30 & 2.22 & 435.51 & 0.09 \\
+\hline
+\end{tabular}
+
+    \end{center}
+    \caption[NB-IoT nRF9161 measurements with payload size 1024 B]{NB-IoT nRF9161 measurements with payload size 1024 B}
+    \label{tab:ltem61_1024ex}
+\end{table}
+
+These final data tables are used for generating more visually understandable plots. Lets have a closer look at some of them that would evaluate the performance of nRF916x as outlined in beginning of this chapter.
+All charts can be found in appendix \ref{appendix:ltecharts}.
+
+\subsection{Validity of attenuation and sensitivity}
+
+Firstly to ensure validity of this measurement it is important to check if the addition attenuation really corresponds to attenuation of input signal. This can be seen in figure \ref{fig:rssitoatt}. The sudden jump at 20 dB is due to transition of the physical attenuator form the inside of the EMC chamber to outside to prevent RF leakage. Th same thing happened at 50 dB. Other than that the slope of the course seems linear.
+
+Another key observation is that NB-IoT has by 3 dB better sensitivity over LTE-M (-133 dBm and -130 dB respectively). This is in contrast to datasheet values of -114 dBm and -108 dBm (see chapter \ref{chap:nrfdesc}) where the difference between the modes should be 6 dB and measured sensitivity is better by 19 dB and 22 dB.
+
+Alternative value provided by modem that could be use to guess the sensitivity is its reported \ac{DL} path loss. This was 159 dB for NB-IoT and 148 for LTE-M. If the same transmit power of 23 dBm is assumed for the \ac{BTS} it would give a sensitivity of -136 dBm for NB-IoT and -125 dBm for LTE-M. This method or reported DL path loss in general are used sporadically in subsequent analysis for the author's doubts about validity and accuracy of such numbers.
+
+Seemingly big difference is \ac{RSRP} at same attenuation between both modes. This has multiple possible explanation:
+\begin{itemize}
+    \item Slightly different bands - LTE-M was measured on LTE band 8 (UL: 880 - 915 MHz DL: 925 - 960 MHz) while NB-IoT was on LTE band 20 (UL: 832 - 862 MHz DL: 791 - 821 MHz )
+    \item Different settings on actual \ac{BTS} for both modes
+    \item Higher robustness of NB-IoT
+\end{itemize}
+For this reason subsequent analysis will be done using \ac{RSRP} supplied by modem.
+
+From these possibilities the advantage of NB-IoT compared to LTE-M for detection of very weak signals is 3 dB if RSRP is to be belived, 6 db according to datasheet, 11 dB according to reported DL pash loss and 14 dB according to attenuation.
+
+\begin{figure}[H]
+    \begin{center}
+        \includegraphics[width=1\textwidth]{"mereni/komora2/both61ReferenceSignalReceivedPowertoattenuation.png"}
+    \end{center}
+    \caption[Reference Signal Received Power to attenuation]{Reference Signal Received Power to attenuation}
+    \label{fig:rssitoatt}
+\end{figure}
+
+\subsection{Power consumption analysis}
+
+The value crucial for calculation of needed battery capacity in \ac{IoT} devices is electrical charge that is consumed by the transmission, together by constant current of ready and idle states and planned lifetime of such device.
+
+In figure \ref{fig:chargenrf} can seen a comparison of LTE-M and NB-IoT in regards to this needed charge per single transmission of given payload size dependent to the signal strength reported using \ac{RSRP} from the LTE modem.
+
+From this figure can be conclude following:
+\begin{enumerate}
+    \item LTE-M uses consistently less energy for every payload size compared to NB-IoT. If the total attenuation is takes as determinative value even than NB-IoT consumes less energy then LTE-M only at the limit of LTE-M abilities. See appendix figure \ref{fig:both61Chargepermessagetoattenuation} for this chart.
+    \item Rapid increase in used energy for LTE-M happens only at signal levels close to connection loss. Gradual mild increase can be better seen in appendix table \ref{fig:ltem61ChargepermessagetoRSRP}
+    \item NB-IoT is able to transmit messages at the cost of vastly higher energy consumption in worse conditions where LTE-M is unable to operate.
+\end{enumerate}
+
+Summed up this means that usage of NB-IoT is only advisable for situations where signal conditions are so bad that the better resilience is needed.
+
+\begin{figure}[H]
+    \begin{center}
+        \includegraphics[width=1\textwidth]{"mereni/komora2/both61ChargepermessagetoRSRP.png"}
+    \end{center}
+    \caption[nRF9161 LTE-M and NB-IoT Charge per message to RSRP]{nRF9161 LTE-M and NB-IoT Charge per message to RSRP}
+    \label{fig:chargenrf}
+\end{figure}
+
+
+\subsection{Transmission speed and comparison to LoRa}
+
+Difficulty of direct comparison of LTE modes to other technologies such as LoRa are described in depth the discussion chapter \ref{chap:drysty}. But since LoRa is the main "competitor" of LTE IoT protocols it should at least be tried with data that are available.
+
+As a representative of LoRa the Semtech SX1262 chip was chosen. Primarily for similar band (around 800 MHz) and usage in similar applications\cite{loradatasheet}.
+
+Values of data rate and formula for sensitivity of SX1262 were obtained from its datasheet \cite{loradatasheet}.
+
+The formula is following:
+$$
+S = (12 - SF) * 2.5 - 137
+$$
+
+S is sensitivity in dBm, SF is LoRa speeding factor number, 2.5 is lowering of sensitivity in dB per SF and -137 is sensitivity of SX1262 for SF 12 in dBm.
+
+These data were integrated into chart with measured data for NB-IoT and LTE-M as you can see in figure \ref{complora}.
+
+\begin{figure}[H]
+    \begin{center}
+        \includegraphics[width=1\textwidth]{mereni/complora.png}
+    \end{center}
+    \caption[Comparison of sensitivity and transmit speed of LTE to LoRa]{Comparison of sensitivity and transmit speed of LTE to LoRa}
+    \label{fig:complora}
+\end{figure}
+
+Getting conclusions from comparing measured data and datasheet data without any assurance of measurement method comparability is hard but lets at least try to find some meaning in this.
+
+NB-IoT seems to be slightly faster and so better than LoRa up to SF 10 at RSRP -132 dBm where we set a limit of NB-IoT abilities. Since attributes of fair measurement compression were not met, from current data and from knowledge of their limitation there can be made a vague statement that abilities of NB-IoT and LoRa would seem comparable.
+
+LTE-M is a considerable improvement in aspect of data rate over NB-IoT. Over LoRa even though the difference seems huge, in case of real data they share on the signal strength axis only one point. From this it seems that these two are not very comparable in their target ideal use-cases.
+
+\section{DECT NR+}
+
+An additional measurement was made to test the capability of nRF9161 to transmit and receive using DECT NR+.
+
+Measurements were done similarly to these of LTE but with other nRF9161 DK in place of LTE antenna. Measurement of current wa done on the node.
+
+The fixed slot timing property of DECT NR+ means that device can transmit only in fixed time window. This gets rid of need for integration and power consumption can be established from maximal current and number of time slots used.
+
+The two DKs do not communicate \ac{P2P} strictly speaking but one operates as a beacon that periodically sends information needed to establish communication with itself. The other operates as node, in 5G terminology named as \ac{PDU}. In implementations with more than 2 devices some devices can be beacon with established connection to other beacon and by this manner it is possible to create the mesh trees described in chapter \ref{dectdescrition}.
+
+In the analysis there is used a term of \ac{FSPL} distance. This represents the attenuation as distance in completely free space that would have the same attenuation (ignoring latency increase). Here is how it was calculated. This is equation for freespace path loss:
+
+$$ K_U = \left( \frac{4 \pi d}{\lambda} \right) ^2  $$
+
+When frequency of 1.9 GHz is substituted, the equation solved for distance and signal loss expressed in decibels it forms this equation that was used in later analysis:
+
+$$ d = 10^{\frac{K_U-98}{20}} $$
 
+%In this case a attenuation is no longer arbitrary values with loose connection to real signal degradation but real 
 
+\begin{table}[!h]
+    \begin{center}
+        \small
+\begin{tabular}{rrrrrrrr}
+\hline
+& \multicolumn{2}{c}{Beacon} & \multicolumn{2}{c}{PDU} & & & \\
+$K_U$ & RSSI & PWR & RSSI & PWR & FSPL d & Max I  & Att conf \\
+{[dB]} & {[dBm]} & {[dBm]} & {[dBm]} & {[dBm]} & {[km]} &  {[mA]} & {[dB]} \\
+\hline
+106 & -105 & 4 & -91 & 23 & 2.51  & 213.28  & 60+46 \\
+103 & -103 & 4 & -88 & 23 & 1.78  & 218.63  & 60+43 \\
+93 & -93 & 4 & -78 & 23 & 0.56    & 220.93  & 60+33 \\
+83 & -83 & 4 & -68 & 23 & 0.18    & 221.69  & 40+43 \\
+73 & -72 & 4 & -60 & 16 & 0.06    & 160.71  & 40+33 \\
+63 & -62 & 4 & -59 & 7 & 0.02     & 97.30   & 40+23 \\
+53 & -52 & 4 & -60 & -4 & 0.01    & 89.05   & 40+13 \\
+43 & -41 & 4 & -58 & -12 & 0.00   & 88.30   & 40+03 \\
+\hline
+\end{tabular}
+    \end{center}
+    \caption[Result table of DECT NR+ measurements]{Result table of DECT NR+ measurements}
+    \label{tab:dect}
+\end{table}
 
-\input{mereni/ltem61_1024_table}
+Results of these measurement can be seen in table \ref{tab:dect} and visualized in figures \ref{fig:dectPowerlevelstotoattenuation} and \ref{fig:dectRSSIlevelstotoattenuation}.
+Note to the data: maybe contrary to common sense beacon TX power is output power transmitted from the beacon but its RSSI is value measured from PDU of the beacon's signal. Same thing is true for the PDU and its values.
 
-This is 
+\input{"mereni/komoradect/dectRSSIlevelstotoattenuation"}
+\input{"mereni/komoradect/dectPowerlevelstotoattenuation"}
+From these can be conclude following:
+\begin{enumerate}
+    \item Beacon did not had automatic adjunction of power but PDU did. This can be clearly seen in figure \ref{fig:dectPowerlevelstotoattenuation}. This could be due to using experimental \ac{MoSh} for DECT NR+ that supports only the physical layer of DECT NR+.
+    \item Maximal current grows in discrete jumps with PDU power level.
+    \item Maximal theoretical range for measured power of 4 dBm is 2.5 km.
+    \item If maximal power of 23 dBm on both boards is assumed, the maximal possible attenuation is 125 dB and theoretical range is 22.4 km.
+    \item Minimal signal strength was -105 dBm. According to nRF9161 documentation its sensitivity for DECT NR+ is -103 dBm. 
+\end{enumerate}
 
-Complete data are for their large extent placed in Appendix \ref{appendix:ltetables}.
 
 
 
diff --git a/text/literatura.tex b/text/literatura.tex
index 2f8676c..019c300 100644
--- a/text/literatura.tex
+++ b/text/literatura.tex
@@ -11,6 +11,48 @@
 		\emph{From GSM to LTE-advanced pro and 5G: an introduction to mobile networks and mobile broadband.}
 	Third edition. Hoboken, NJ, USA: Wiley, 2017. ISBN 978-1-119-34686-9.
 
+\bibitem{eu2Gna3G}
+    author = {Fuentelsaz, Lucio and Maícas, Juan P. and Polo, Yolanda},
+    year = {2008},
+    month = {07},
+    pages = {436-449},
+    title = {The evolution of mobile communications in Europe: The transition from the second to the third generation},
+    journal = {Telecommunications Policy},
+    doi = {10.1016/j.telpol.2008.04.008}
+    
+\bibitem{ctu2g}
+    Meravá, Tereza.  Český telekomunikační úřad.
+        \emph{Tisková ZPRÁVA: ČTÚ Obnovil O2 Příděl Spektra 2100 mhz. Zajistí Tím Provoz sítě I pro Starší Telefony},
+		2021, 2021-12-15 [cited~on~2024-12-27].
+        Avaible at:
+        {\small \url{https://ctu.gov.cz/ctu-obnovil-o2-pridel-spektra-2100-mhz-zajisti-tim-provoz-site-i-pro-starsi-telefony}}
+
+\bibitem{wifi}
+    Wi-Fi Alliance.
+        \emph{Internet of Things (IoT)}
+        2024 [cited~on~2024-12-27].
+        Avaible at:
+        {\small \url{https://www.wi-fi.org/discover-wi-fi/internet-things}}
+
+\bibitem{semtech}
+    Semtech Corporation.
+        \emph{What Is LoRa?}
+        2024 [cited~on~2024-12-27].
+        Avaible at:
+        {\small \url{ https://www.semtech.com/lora/what-is-lora } }
+
+\bibitem{zigbee}
+    Digi International Inc. 
+        \emph{What Is Zigbee?}
+        2024 [cited~on~2024-12-27].
+        Avaible at:
+        {\small \url{ https://www.digi.com/solutions/by-technology/zigbee-wireless-standard } }
+
+\bibitem{adhocwireless}
+    Ioanis, Nikolaidis. Kui, Wu.
+        \emph{Ad-hoc, mobile and wireless networks}
+    First edition, 2010. ISBN 978-3-642-14785-2
+
 \bibitem{3gppurllc}
 	3GPP.
 		\emph{Ultra Reliable and Low Latency Communications [online]}
@@ -96,12 +138,6 @@
 	Avaible at:
 	{\small \url{https://www.nordicsemi.com/-/media/Software-and-other-downloads/Product-Briefs/nRF9160-SiP-product-brief.pdf} }
 
-\bibitem{rm520ndatasheet}
-	Quectel.
-	\emph{RM520N-GL Hardware Design [pdf]}
-	2022-07-15
-	Avaible at:
-	{\small \url{https://forums.quectel.com/uploads/short-url/1zkjPRnxF5BZ2woox386baCZx4g.pdf} }
 
 \bibitem{nrf9160cert}
 	Nordic semiconductor.
@@ -131,6 +167,13 @@
 	Avaible at:
 	{ \small \url{https://www.nordicsemi.com/Products/Development-hardware/Nordic-Thingy-91} }
 
+\bibitem{thingyxdesc}.
+	Nordic Semiconductor.
+	\emph{Nordic Thingy:91 X Cellular IoT prototyping platform [online]}
+	[cited~on~2025-04-23]
+	Avaible at:
+	{ \small \url{https://www.nordicsemi.com/Products/Development-hardware/Nordic-Thingy-91-X} }
+
 \bibitem{nimbelinkdesc}.
 	Airgain.
 	\emph{NimbeLink Nano Global LTE-M [online]}
@@ -193,57 +236,56 @@
 	\emph{Conexio Stratus - A tiny, powerful, versatile cellular-IoT prototyping platform with out-of-the-box connectivity [online]}
 	2022, [cited~on~2023-12-27]
 	Avaible at:
-	{ \small \url{https://www.crowdsupply.com/conexio/stratus} }
+	{ \small \url{https://www.crowdsupply.com/conexio/stratus} and \url{https://www.crowdsupply.com/conexio/stratus-pro} }
 
-\bibitem{waveshare1}
-	Waveshare.
-	\emph{Quectel RM520N-GL IoT 5G Global Band Module, 5G Sub-6G Module, M.2 Form Factor With 3GPP 5G Release 16 Specification. [online]}
-	[cited~on~2023-12-27]
+\bibitem{nrfdect}
+	Nordic Semiconductor.
+    \emph{DECT NR+}
+    [2025-02-21]
 	Avaible at:
-	[https://www.waveshare.com/rm520n-gl.htm]
+	{ \small \url{https://docs.nordicsemi.com/bundle/ps_nrf9161/page/dect.html}}
 
-\bibitem{waveshare2}
-	Waveshare.
-	\emph{Wiki - RM520N-GL [online]}
-	[cited~on~2023-12-27]
+\bibitem{etsidect}
+    Antipolis, Sophia.
+    \emph{World’s first non-cellular 5G technology, ETSI DECT-2020, gets ITU-R approval, setting example of new era connectivity}
+    [2021-10-19]
 	Avaible at:
-	[https://www.waveshare.com/wiki/RM520N-GL]
+	{ \small \url{https://www.etsi.org/newsroom/press-releases/1988-2021-10-world-s-first-non-cellular-5g-technology-etsi-dect-2020-gets-itu-r-approval-setting-example-of-new-era-connectivity}}
 
-\bibitem{rmdongle}
-	Waveshare.
-	\emph{5G DONGLE Module, quad antennas, USB3.1 port, Aluminum Alloy Heatsink, M.2 Key B Interface, Options For 5G Module [online]}
-	[cited~on~2023-12-27]
-	Avaible at:
-	[https://www.waveshare.com/usb-to-m.2-b-key.htm]
+\bibitem{dectnrdesc}
+    Sollie, Heidi.
+    \emph{DECT NR+: A technical dive into non-cellular 5G}
+    [2023-5-25]
+	{ \small \url{https://devzone.nordicsemi.com/nordic/nordic-blog/b/blog/posts/dect-nr-a-technical-dive-into-non-cellular-5g}}
 
-\bibitem{rmpi}
-	Waveshare.
-	\emph{RM520N-GL 5G HAT for Raspberry Pi with Case, Quad Antennas LTE-A, Global Band, GNSS Positioning, Support 3GPP 16, 4G/3G [online]}
-	[cited~on~2023-12-27]
+\bibitem{nrf91datasheet}
+	Nordic Semiconductor.
+	\emph{nRF9160 Product Specification [pdf]}
+	[2021-10]
 	Avaible at:
-	[https://www.waveshare.com/rm520n-gl-5g-hat-with-case.htm]
+	{\small \url{https://cz.mouser.com/datasheet/2/297/nRF9160_PS_v2_1-3074783.pdf} }
 
-\bibitem{rmeth}
-	Waveshare.
-	\emph{5G M.2 to Gigabit Ethernet Converter, 5G M.2 to USB3.1, Aluminum Alloy Case, Wall-Mount Support, Quad Antennas, Options For 5G Module [online]}
-	[cited~on~2023-12-27]
+\bibitem{loradatasheet}
+    Semtech Corporation.
+    \emph{SX1261/2 datasheet [pdf]}
+	[2021-12]
 	Avaible at:
-	[https://www.waveshare.com/5g-m.2-to-gigabit-eth.htm]
+	{\small \url{https://semtech.my.salesforce.com/sfc/p/#E0000000JelG/a/2R000000Un7F/yT.fKdAr9ZAo3cJLc4F2cBdUsMftpT2vsOICP7NmvMo}}
 
-\bibitem{rmjet}
-	Waveshare.
-	\emph{5G/4G/3G module designed for Jetson Nano, multi mode multi band, Options for 5G Module [online]}
-	[cited~on~2023-12-27]
+\bibitem{plaindectdesc}
+    European Telecommunications Standards Institute.
+    \emph{Digital Enhanced Cordless Telecommunications (DECT)}
+	2025
+	[cited~on~2025-6-1]
 	Avaible at:
-	[https://www.waveshare.com/sim8202g-m2-5g-for-jetson-nano.htm]
+	{\small \url{https://www.etsi.org/technologies/dect} }
 
-
-\bibitem{nrf91datasheet}
+\bibitem{nrfat}
 	Nordic Semiconductor.
-	\emph{nRF9160 Product Specification [pdf]}
-	[2021-10]
-	Avaible at:
-	{\small \url{https://cz.mouser.com/datasheet/2/297/nRF9160_PS_v2_1-3074783.pdf} }
+    \emph{nRF9160 AT Commands [online]}
+    [2025-03-07]
+    { \small \url{https://docs.nordicsemi.com/bundle/ref_at_commands/page/REF/at_commands/intro_nrf9160.html}}
+ 
 
 \bibitem{nrf91dkbrief}
 	Nordic Semiconductor.
@@ -252,6 +294,13 @@
 	Avaible at:
 	{\small \url{https://www.nordicsemi.com/-/media/Software-and-other-downloads/Product-Briefs/nRF9160-DK-product-brief.pdf} }
 
+\bibitem{nrf51}
+	Nordic Semiconductor.
+	\emph{nRF9151 System-in-Package [online]}
+	[cited~on~2025-6-1]
+	Avaible at:
+	{\small \url{https://www.nordicsemi.com/Products/nRF9151/}}
+
 \bibitem{unilabnews}
 	Brno university of technology.
 	\emph{In the laboratory of 5G networks at BUT it will be possible to easily test devices for smart homes, for example [online]}
@@ -355,6 +404,12 @@
 		Avaible at:
         {\small \url{https://www.nordicsemi.com/-/media/Software-and-other-downloads/Product-Briefs/nRF9160-SiP-PB-v2.1.pdf } }
 
+\bibitem{oneoneoneone}
+    Cloudflare, Inc.
+    [cited~on~2025-5-30].
+    Avaible at:
+    {\small \url{https://1.1.1.1}}
+
 % https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/samples/cellular/modem_shell/README.html
 %\bibitem{sr72/2017}
 %	VYSOKÉ UČENÍ TECHNICKÉ V~BRNĚ.
diff --git a/text/mobil.tex b/text/mobil.tex
index e8a2588..5b4e29c 100644
--- a/text/mobil.tex
+++ b/text/mobil.tex
@@ -1 +1,66 @@
-\chapter{Field testing of mobile capabilities of nRF916X-DK}
+\chapter{Field testing of mobile capabilities of NB-IoT and LTE-M} \label{chap:mobil}
+
+Standard notion on selecting between LTE-M and NB-IoT when one has a choice is to choose LTE-M when one needs higher speed or needs for the device to be mobile while not having not so extreme requirements for continual communication or environment with extreme attenuation and to choose NB-IoT for smaller payload applications with potential of very weak signal.
+
+To test this hypothesis an experiment was created where the created demonstrator from chapter \ref{chap:demo} was placed inside a personal car as can be seen in figure \ref{fig:demofelda}. One way to test LTE-M on road from north Moravia to Brno and to test NB-IoT on return path.
+
+Because of large intervals (orders of minutes) needed for switch between GNSS and LTE connection on nRF916x, it was chosen to perform only reading from the meteo sensor, reading of connection quality report and periodical sending of these data to MQTT server. On the same server there was running Python script that saved all data in json format to the server storage.
+Location data were collected by smartphone with GNSS logging application and later these two datasets were joined by time.
+
+\begin{figure}[H]
+	\begin{center}
+		\includegraphics[width=1\textwidth]{obrazky/demofelda.jpg}
+	\end{center}
+	\caption[Demonstrator secured in car for mobile measurement]{Demonstrator secured in car for mobile measurement}
+	\label{fig:demofelda}
+\end{figure}
+
+Gathered data included from GPS tracker included latitude, longitude, accuracy of position, smartphone battery, computed elevation, number of visible satellites, and speed.
+
+Evaluation data from LTE modem were LTE band, down link path loss, LTE mode (1 is LTE-M 2 is NB-IoT), Reference Signal Received Power (RSRP), Reference Signal Received Quality (RSRQ), Signal to Noise Ratio (SNR) and TX power.
+
+Lastly to demonstrate transfer of useful data the values form sensor BME680 were also included. These were atmospheric pressure, inside car temperature, 
+car humidity, resistance of gas sensor representing amount of for example volatile organic compounds in the air.
+
+All of these data joined by Python script were than used to create interactive maps for better data visualization.
+
+An example of such map of reported signal power can be seen in figure \ref{mapaltem} for LTE-M and \ref{mapanbiot} for LTE-M.
+
+\begin{figure}[h]
+	\begin{center}
+		\includegraphics[width=1\textwidth]{obrazky/mapltem.png}
+	\end{center}
+	\caption[Map RSRP reported by demonstrator operating using LTE-M]{Map RSRP reported by demonstrator operating using LTE-M}
+	\label{fig:mapaltem}
+\end{figure}
+
+\begin{figure}[h]
+	\begin{center}
+		\includegraphics[width=1\textwidth]{obrazky/mapnbiot.png}
+	\end{center}
+	\caption[Map RSRP reported by demonstrator operating using NB-IoT]{Map RSRP reported by demonstrator operating using NB-IoT}
+	\label{fig:mapanbiot}
+\end{figure}
+
+Findings from thise sdata are:
+\begin{itemize}
+    \item LTE-M provided stable connection for transmission of packet about 0.5 kB in size every second with exception near Lipník na Bečvou where most likely due to change in network operating LTE band demonstrator lost connection for 1.5 minutes. This transition from band 8 to band 20 can be clearly seen in figure \ref{fig:mapaltemband}.
+    \item NB-IoT also provided fairly stable connection with 2 minute connection loss near Brno airport and nearly 2 minute loss between Nový Jičín and Hranice na Moravě at borderline of Olomouc and Moravian-Silesian region (whenever is this detail significant is not clear but the band change as in the LTE-M did not happened here). Last understandable signal loss was in tunnels in west Brno (different route than LTE-M due to traffic situation in Brno). 
+\end{itemize}
+
+
+\begin{figure}[h]
+	\begin{center}
+		\includegraphics[width=1\textwidth]{obrazky/maplteband.png}
+	\end{center}
+	\caption[Map of LTE band used by demonstrator when using LTE-M]{Map of LTE band used by demonstrator when using LTE-M}
+	\label{fig:mapaltemband}
+\end{figure}
+
+
+Better visualization of these data with interactive maps can be found in this GitHub page: \url{https://mikehanus.github.io/bcthesis-datavisualisation/}
+Including them in attachments were not possible due to large size of these maps but it should be possible to generate them using python scripts and data in the attachments.
+
+
+.
+
diff --git a/text/prilohy.tex b/text/prilohy.tex
index 821da7a..ea697fa 100644
--- a/text/prilohy.tex
+++ b/text/prilohy.tex
@@ -1,33 +1,33 @@
 % \chapter{Některé příkazy balíčku \texttt{thesis}}
 
 %\appendix
-\chapter{Result measurement tables}
+\chapter{Result measurement - tables}
 \label{appendix:ltetables}
 
-\input{mereni/nbiot60_0_table}
-\input{mereni/nbiot60_64_table}
-\input{mereni/nbiot60_1024_table}
-\input{mereni/ltem60_0_table}
-\input{mereni/ltem60_64_table}
-\input{mereni/ltem60_1024_table}
-\input{mereni/nbiot61_0_table}
-\input{mereni/nbiot61_64_table}
-\input{mereni/nbiot61_1024_table}
-\input{mereni/ltem61_0_table}
-\input{mereni/ltem61_64_table}
-\input{mereni/ltem61_1024_table}
+%\input{mereni/nbiot60_0_table}
+%\input{mereni/nbiot60_64_table}
+%\input{mereni/nbiot60_1024_table}
+%\input{mereni/ltem60_0_table}
+%\input{mereni/ltem60_64_table}
+%\input{mereni/ltem60_1024_table}
+%\input{mereni/nbiot61_0_table}
+%\input{mereni/nbiot61_64_table}
+%\input{mereni/nbiot61_1024_table}
+%\input{mereni/ltem61_0_table}
+%\input{mereni/ltem61_64_table}
+%\input{mereni/ltem61_1024_table}
 
 \chapter{Result of measurement - charts}
+\label{appendix:ltecharts}
 
-
-\input{"mereni/compltem_charge_per_message_to_rsrp"}
-\input{"mereni/compnbiot_charge_per_message_to_rsrp"}
-\input{"mereni/compltem_data-rate_to_rsrp"}
-\input{"mereni/compnbiot_data-rate_to_rsrp"}
-\input{"mereni/compltem_maximal_transmit_current_to_rsrp"}
-\input{"mereni/compnbiot_maximal_transmit_current_to_rsrp"}
-\input{"mereni/compltem_average_transmit_current_to_rsrp"}
-\input{"mereni/compnbiot_average_transmit_current_to_rsrp"}
+%\input{"mereni/compltem_charge_per_message_to_rsrp"}
+%\input{"mereni/compnbiot_charge_per_message_to_rsrp"}
+%\input{"mereni/compltem_data-rate_to_rsrp"}
+%\input{"mereni/compnbiot_data-rate_to_rsrp"}
+%\input{"mereni/compltem_maximal_transmit_current_to_rsrp"}
+%\input{"mereni/compnbiot_maximal_transmit_current_to_rsrp"}
+%\input{"mereni/compltem_average_transmit_current_to_rsrp"}
+%\input{"mereni/compnbiot_average_transmit_current_to_rsrp"}
 
 \section{nRF9161}
 
@@ -67,42 +67,42 @@
 
 \section{nRF9160}
 
-\input{"mereni/komora1/both60Signal-NoiseRatiotoattenuation"}
-\input{"mereni/komora1/both60ReferenceSignalReceivedPowertoattenuation"}
-\input{"mereni/komora1/both60Readycurrenttoattenuation"}
-\input{"mereni/komora1/ltem60Transmittimetoattenuation"}
-\input{"mereni/komora1/nbiot60Transmittimetoattenuation"}
-\input{"mereni/komora1/both60Transmittimetoattenuation"}
-\input{"mereni/komora1/ltem60Transmittimetoattenuation"}
-\input{"mereni/komora1/nbiot60Transmittimetoattenuation"}
-\input{"mereni/komora1/both60Transmittimetoattenuation"}
-\input{"mereni/komora1/ltem60Chargepermessagetoattenuation"}
-\input{"mereni/komora1/nbiot60Chargepermessagetoattenuation"}
-\input{"mereni/komora1/both60Chargepermessagetoattenuation"}
-\input{"mereni/komora1/ltem60Data-ratetoattenuation"}
-\input{"mereni/komora1/nbiot60Data-ratetoattenuation"}
-\input{"mereni/komora1/both60Data-ratetoattenuation"}
-\input{"mereni/komora1/ltem60Transmittimetoattenuation"}
-\input{"mereni/komora1/nbiot60Transmittimetoattenuation"}
-\input{"mereni/komora1/both60Transmittimetoattenuation"}
-\input{"mereni/komora1/ltem60Averagetrasmitcurrenttoattenuation"}
-\input{"mereni/komora1/nbiot60Averagetrasmitcurrenttoattenuation"}
-\input{"mereni/komora1/both60Averagetrasmitcurrenttoattenuation"}
-\input{"mereni/komora1/ltem60ChargepermessagetoRSRP"}
-\input{"mereni/komora1/nbiot60ChargepermessagetoRSRP"}
-\input{"mereni/komora1/both60ChargepermessagetoRSRP"}
-\input{"mereni/komora1/ltem60Data-ratetoRSRP"}
-\input{"mereni/komora1/nbiot60Data-ratetoRSRP"}
-\input{"mereni/komora1/both60Data-ratetoRSRP"}
-\input{"mereni/komora1/ltem60MaximaltransmitcurrenttoRSRP"}
-\input{"mereni/komora1/nbiot60MaximaltransmitcurrenttoRSRP"}
-\input{"mereni/komora1/both60MaximaltransmitcurrenttoRSRP"}
-\input{"mereni/komora1/ltem60AveragetransmitcurrenttoRSRP"}
-\input{"mereni/komora1/nbiot60AveragetransmitcurrenttoRSRP"}
-\input{"mereni/komora1/both60AveragetransmitcurrenttoRSRP"}
+%\input{"mereni/komora1/both60Signal-NoiseRatiotoattenuation"}
+%\input{"mereni/komora1/both60ReferenceSignalReceivedPowertoattenuation"}
+%\input{"mereni/komora1/both60Readycurrenttoattenuation"}
+%\input{"mereni/komora1/ltem60Transmittimetoattenuation"}
+%\input{"mereni/komora1/nbiot60Transmittimetoattenuation"}
+%\input{"mereni/komora1/both60Transmittimetoattenuation"}
+%\input{"mereni/komora1/ltem60Transmittimetoattenuation"}
+%\input{"mereni/komora1/nbiot60Transmittimetoattenuation"}
+%\input{"mereni/komora1/both60Transmittimetoattenuation"}
+%\input{"mereni/komora1/ltem60Chargepermessagetoattenuation"}
+%\input{"mereni/komora1/nbiot60Chargepermessagetoattenuation"}
+%\input{"mereni/komora1/both60Chargepermessagetoattenuation"}
+%\input{"mereni/komora1/ltem60Data-ratetoattenuation"}
+%\input{"mereni/komora1/nbiot60Data-ratetoattenuation"}
+%\input{"mereni/komora1/both60Data-ratetoattenuation"}
+%\input{"mereni/komora1/ltem60Transmittimetoattenuation"}
+%\input{"mereni/komora1/nbiot60Transmittimetoattenuation"}
+%\input{"mereni/komora1/both60Transmittimetoattenuation"}
+%\input{"mereni/komora1/ltem60Averagetrasmitcurrenttoattenuation"}
+%\input{"mereni/komora1/nbiot60Averagetrasmitcurrenttoattenuation"}
+%\input{"mereni/komora1/both60Averagetrasmitcurrenttoattenuation"}
+%\input{"mereni/komora1/ltem60ChargepermessagetoRSRP"}
+%\input{"mereni/komora1/nbiot60ChargepermessagetoRSRP"}
+%\input{"mereni/komora1/both60ChargepermessagetoRSRP"}
+%\input{"mereni/komora1/ltem60Data-ratetoRSRP"}
+%\input{"mereni/komora1/nbiot60Data-ratetoRSRP"}
+%\input{"mereni/komora1/both60Data-ratetoRSRP"}
+%\input{"mereni/komora1/ltem60MaximaltransmitcurrenttoRSRP"}
+%\input{"mereni/komora1/nbiot60MaximaltransmitcurrenttoRSRP"}
+%\input{"mereni/komora1/both60MaximaltransmitcurrenttoRSRP"}
+%\input{"mereni/komora1/ltem60AveragetransmitcurrenttoRSRP"}
+%\input{"mereni/komora1/nbiot60AveragetransmitcurrenttoRSRP"}
+%\input{"mereni/komora1/both60AveragetransmitcurrenttoRSRP"}
 
 \chapter{Demonstrator electronic schemes}
-\label{chap:demoapp}
+\label{appendix:demoapp}
 
 \begin{figure}[H]
     \begin{center}
diff --git a/text/protokolyLPWAN.tex b/text/protokolyLPWAN.tex
index 5cf2cea..19f1770 100644
--- a/text/protokolyLPWAN.tex
+++ b/text/protokolyLPWAN.tex
@@ -60,7 +60,6 @@ However, due to the advancement of technology, and the need for frequency space,
 
 The deployment of \ac{LoRaWAN} or LoRaWAN-like networks necessitates the implementation of dedicated gateway infrastructure, a characteristic that, conversely, affords enhanced control over network coverage compared to cellular technologies such as 4G and 5G which is dependent on mobile operators.
 
-% https://www.semtech.com/lora/what-is-lora
 
 \subsection{Wi-Fi}
 
@@ -73,32 +72,22 @@ Other key advantage of Wi-Fi is its ubiquity. This makes it valid option even in
 Although Wi-Fi technology is predominantly utilized for short-range wireless local area networks, there are notable exceptions involving long-range deployments, such as those employed by ISPs and for low-cost  \ac{P2P} remote communication. Notable extreme example of this is 279 km long unamplified Wi-Fi link in Venezuela\cite{adhocwireless}.
 
 
-% ct wifi https://www.wi-fi.org/discover-wi-fi/internet-things
 
 \subsection{Zigbee}
 
 Zigbee is a open wireless communication protocol specification, operating within the IEEE 802.15.4 standard, designed for low-bandwidth, low-power, short-range \ac{WPAN}. It is characterized by its mesh networking capabilities, which facilitate robust and scalable communication among numerous devices in close proximity. Its main application are smart home accessories and industrial sensors on sort range \cite{zigbee}.
 
 Zigbee primarily operates on 2.4 GHz band (in usual gaps between Wi-Fi channels) but can also operate on sub-GHz bands. It is similar to Z-Wave protocol.
-% ct zigbee https://www.digi.com/solutions/by-technology/zigbee-wireless-standard
-
-\subsection{Sigfox}
-
-Sigfox is a proprietary \ac{UNB} \ac{LPWAN} technology designed for low-throughput, long-range communication primarily targeting massive \ac{IoT} applications. Operating in unlicensed sub-GHz radio frequency bands, Sigfox employs an \ac{UNB} modulation scheme that enables robust communication over significant distances with extremely low power consumption. 2  This technology is particularly suited for applications involving the transmission of small, infrequent data packets, such as basic sensor readings and status updates, where extended battery life and wide coverage are paramount
-
-
 
 \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
+%https://blog.nordicsemi.com/getconnected/what-is-cellular-iot
+%https://www.nordicsemi.com/Products/Wireless/Low-power-cellular-IoT/Development-tools?lang=en\#infotabs
 
-%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.
+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 \cite{ctu2g} it is important to look on protocols that are supposed to replace them and enhance their capabilities.
 
 \ac{LPWAN} protocols are 4G LTE wireless communication technologies that enable long-range transmission among IoT devices. \ac{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}
 \ac{NB-IoT}  is a cellular \ac{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}.
 
@@ -141,7 +130,7 @@ As of writing this thesis (December 2023) NB-IoT is supported in Czechia by all
 
 \subsection{LTE-M}
 
-LTE-M or LTE-MTC (Long-Term Evolution Machine Type Communication) is a second \ac{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}.
+LTE-M or LTE-MTC (Long-Term Evolution Machine Type Communication) is a second \ac{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}.
 
@@ -155,12 +144,10 @@ As of writing this thesis (December 2023) LTE-M is covered in Czechia by O2 in 9
 
 \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}
-	\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 NSA (non-stand alone) - 5G features are achieved by adding new \ac{RAN} 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}
 
@@ -179,8 +166,6 @@ 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}:
 
@@ -191,10 +176,10 @@ dealt in separately and sometimes were in direct contradiction to each other (re
 			\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
+			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}
@@ -224,17 +209,10 @@ Air interface is only partially responsible for total end-to-end latency. Remain
 
 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}
-
 \section{DECT NR+ standard for 5G IoT networks}
 
 \subsection{Plain DECT}
 
-
 \ac{DECT} is a digital wireless technology standard primarily known for cordless telephones, though its applications have expanded to some not foreseen use-cases (professional wireless audio solutions such as walkie-talkies and wireless audio on music concerts).
 
 \ac{DECT} is an open standard that operates in a dedicated frequency range, typically 1880-1900 MHz in Europe, Asia, Australia, New Zealand, and South America, and 1920-1930 MHz in the US. This dedicated spectrum helps minimize interference from other wireless technologies like Wi-Fi and Bluetooth. 
@@ -245,6 +223,8 @@ In \ac{3GPP} Release 16, redundant transmission for high-reliability communicati
 
 \subsection{DECT NR+} \label{dectdescrition}
 
- \cite{dectnrdesc}
+\ac{DECT NR+} is an evolution of the DECT standard, developed by \ac{ETSI}. It is designed to address the requirements of \ac{IoT} in existing DECT bands. It meets the 5G requirements for \ac{mMTC} and \ac{URLLC} applications. DECT NR+ is recognized by \ac{ITU} as the world's first non-cellular 5G technology standard (however nonsensitive it may sound) \cite{etsidect}.
+
+DECT NR+ supports \ac{P2P}, star, and mesh topologies. Devices are organized into individual cluster tree topologies, called clusters. \cite{dectnrdesc} 
 
-% https://devzone.nordicsemi.com/nordic/nordic-blog/b/blog/posts/dect-nr-a-technical-dive-into-non-cellular-5g
\ No newline at end of file
+The low latency and high reliability are done by combination of factors. The main is further division of 10 ms slots to 0.5 ms sub-slots and implementation of \ac{HARQ}. The preservation of base 10 ms slots is done to ensure backward compatibility with older DECT devices \cite{dectnrdesc}.
\ No newline at end of file
diff --git a/text/rozsireny_abstrakt.tex b/text/rozsireny_abstrakt.tex
index 7702abc..bf70fb7 100644
--- a/text/rozsireny_abstrakt.tex
+++ b/text/rozsireny_abstrakt.tex
@@ -3,6 +3,16 @@
 \cleardoublepage
 \noindent
 {\large\sffamily\bfseries\MakeUppercase{Rozšířený abstrakt}}
+
+
+Tato bakalářská práce se zabývá problematikou implementace moderních mobilních komunikačních technologií do vestavných zařízení. Cílem práce je detailně prostudovat a popsat základní principy fungování sítí 4G a 5G, konkrétně NB-IoT a LTE-M se zvláštním zaměřením na jejich aplikace v kontextu Internetu věcí (IoT) a nízkoenergetických zařízení.
+
+Práce je rozdělena na teoretickou a praktickou část. V teoretické části je popsána evoluce mobilních sítí, počínaje staršími generacemi a postupně se věnuje detailům technologií 4G, zejména LTE (Long-Term Evolution) a jejím variantám optimalizovaným pro IoT, jako jsou LTE-M (LTE for Machine-Type Communication) a NB-IoT (Narrowband IoT). Dále jsou rozebrány klíčové aspekty nastupující generace 5G sítí, včetně jejich architektury, frekvenčních pásem a potenciálu pro masivní nasazení IoT zařízení. Pozornost je věnována charakteristikám důležitým pro vestavné systémy, jako jsou nízká spotřeba energie, široké pokrytí, spolehlivost přenosu dat a bezpečnost. Diskutovány jsou rovněž relevantní komunikační protokoly a služby využívané v těchto systémech.
+
+Praktická část práce se soustředí na konkrétní implementaci a experimentální ověření vlastností vybraných komunikačních modulů. Autor pro tento účel využívá moderní vývojové platformy, konkrétně moduly nRF9160 a nRF9161 od společnosti Nordic Semiconductor, které integrují mobilní konektivitu (LTE-M/NB-IoT) a často také podporu pro globální polohové systémy (GPS/GNSS). Součástí praktické části je návrh a realizace demonstračního zařízení, jehož elektronická schémata jsou uvedena v příloze. Pro vyhodnocení výkonnostních parametrů autor provedl sérii měření zaměřených na různé aspekty, jako je spotřeba energie (pravděpodobně s využitím nástroje jako Nordic Power Profiler Kit II), kvalita přijímaného signálu (RSRP, SNR), rychlost datových přenosů a případně přesnost lokalizace.
+
+Výsledky těchto měření jsou podrobně zdokumentovány v přílohách práce formou tabulek a grafů, zvlášť pro modul nRF9160 a nRF9161. V rámci diskuse autor analyzuje naměřená data, porovnává vlastnosti testovaných modulů a hodnotí jejich vhodnost pro nasazení v různých typech vestavných aplikací. Závěrem práce shrnuje dosažené poznatky, hodnotí splnění stanovených cílů a naznačuje možné směry budoucího vývoje a aplikační potenciál 4G/5G technologií v dynamicky se rozvíjející oblasti embedded systémů.
+
 %\\
 %Výtah ze směrnice rektora 72/2017:\\
 %\emph{Bakalářská a diplomová práce předložená v angličtině musí obsahovat rozšířený abstrakt v češtině
@@ -22,4 +32,3 @@
 %Třetí část práce demonstruje praktický příklad využití vývojového modulu nRF9160 DK jako komunikační základny kombinovaného elektronického zabezpečovacího a požárního systému (EZS/EPS) s LPWAN konektivitou, využívajícího 4 senzory (pohybový senzor PIR HC-SR501, senzor hořlavých plynů MQ-2, teplotní senzor LM35, magnetický senzor otevření dveří/okna DRV5033), s lokální signalizací simulovanou 4 LED na vývojovém modulu, možností uživatelské lokální (de)aktivace jednotlivých senzorů pomocí 4 tlačítek a přepínačů na vývojovém modulu a s přenosem poplachových dat pomocí MQTT protokolu na virtuální server simulující pult centrální ochrany (PCO).
 %
 %Závěrečnou částí semestrální práce je přehled náplně navazujícího bakalářského projektu, který se bude zabývat možnostmi využití 4G/5G mobilních sítí pro průmyslovou IoT komunikaci, s experimentálním měřením parametrů komunikace, jejich srovnáním s teoretickými předpoklady a jinými v současnosti používanými komunikačními systémy.
-!!! TODO !!!
diff --git a/text/uvod.tex b/text/uvod.tex
index 2cc813c..09fb3d4 100644
--- a/text/uvod.tex
+++ b/text/uvod.tex
@@ -6,12 +6,13 @@
 
 It is estimated that currently (2024/2025) 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.
+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 advancements in \ac{LPWAN} \ac{RF} technology in regards to power saving in weak signal decoding and subsequent longer range opens a door to vast filed of usage critical scenarios currently depended on more costly solutions with private networks. \texttt{Co to znamena???}
+The advancements in \ac{LPWAN} \ac{RF} technology in regards to power saving in weak signal decoding and subsequent longer range opens a door to vast filed of usage critical scenarios currently depended on more costly solutions with private networks.
 
-%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}.
+The goal of this thesis is to describe these gradually more and more adapted protocols. Than to practically demonstrate these capabilities with current communication modules. Both in laboratory setting with detailed measurement of their radio capabilities and power consumption and in real field scenarios. And finally use these finding to recommend in which scenario use what technology.
+
+%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/zhodnoceni.tex b/text/zhodnoceni.tex
index 1e7eda6..fcd96d1 100644
--- a/text/zhodnoceni.tex
+++ b/text/zhodnoceni.tex
@@ -1,4 +1,4 @@
-\chapter{Discussion}
+\chapter{Discussion and usage scenarios} \label{chap:drysty}
 
 
 \begin{itemize}
diff --git a/text/zkratky.tex b/text/zkratky.tex
index c154191..87faef1 100644
--- a/text/zkratky.tex
+++ b/text/zkratky.tex
@@ -58,7 +58,7 @@
 	\acro{RF}{Radio Frequency}
 	\acro{GSM}{Global System for Mobile communications}
 	\acro{SMS}{Short Message Service}
-	\acro{M2G}{Machine-to-Machine}
+	\acro{M2M}{Machine-to-Machine}
 	\acro{LoRa}{Long-Range}
 	\acro{LoRaWAN}{Long-Range wide area network}
 	\acro{CSS}{chirp spread spectrum}
@@ -78,11 +78,19 @@
     \acro{SNR}{Signal to Noise Ration}
     \acro{RSRP}{Reference Signal Received Power}
     \acro{PPK II}{Nordic Power Profiler Kit II}
-
-%	%%% bsymfvz
-%	\acro{symfvz}						% název
-%		[\ensuremath{f_\textind{vz}}] % symbol
-%		{vzorkovací kmitočet}					% popis
-%	%%% esymfvz
+    \acro{ICMP}{Internet Control Message Protocol}
+    \acro{2G}{2nd generation of cellular networks}
+    \acro{MAC}{Medium Access Control}
+    \acro{SC-FDMA}{Single-Carrier Frequency-Division Multiple Access}
+    \acro{FDMA}{Frequency-Division Multiple Access}
+    \acro{TDMA}{Time-Division Multiple Access}
+    \acro{DECT}{Digital Enhanced Cordless Telecommunications}
+    \acro{DECT NR+}{Digital Enhanced Cordless Telecommunications: New Radio plus}
+    \acro{HARQ}{Hybrid Automatic Repeat Request}
+    \acro{ETSI}{European Telecommunications Standards Institute}
+    \acro{ITU}{International Telecommunication Union}
+    \acro{TDD}{Time-Division Duplex}
+    \acro{PDU}{Protocol Data Unit}
+    \acro{RSSI}{Received signal strength indicator}
 
 \end{acronym}