From 2a9a6483aeb8ae571bf2b2da6268a1f88676ab1e Mon Sep 17 00:00:00 2001 From: Bob Flynn <bob.flynn@exactagss.com> Date: Wed, 24 Apr 2024 12:05:22 +0000 Subject: [PATCH] Added captions --- ...2M-Effective_IoT_Communication_to_Protect_3GPP_Networks.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/TR-0063-oneM2M-Effective_IoT_Communication_to_Protect_3GPP_Networks.md b/TR-0063-oneM2M-Effective_IoT_Communication_to_Protect_3GPP_Networks.md index c7de1f5..23619df 100644 --- a/TR-0063-oneM2M-Effective_IoT_Communication_to_Protect_3GPP_Networks.md +++ b/TR-0063-oneM2M-Effective_IoT_Communication_to_Protect_3GPP_Networks.md @@ -149,7 +149,7 @@ GSMA TS.34 [i.1] represents a guideline and giving requirements for whole IoT De ![Figure 5.1-1: Generalised IoT Device Architecture according to GSMA TS.34 [i.1]](media/Fig3.png) -Figure 5.1-1: Generalised IoT Device Architecture according to GSMA TS.34 [i.1] +**Figure 5.1-1: Generalised IoT Device Architecture according to GSMA TS.34 [i.1]** Requirements with regards to an efficient communication are grouped and categorized in TS.34 [i.1]. E.g. requirements are formulated for the following areas: @@ -190,7 +190,7 @@ The remainder of this section is organized by the components shown in figure 5.3  -Figure 5.3-1: Requirements for CIoT solutions +**Figure 5.3-1: Requirements for CIoT solutions** ## 5.4 Tiered IoT Device Application Requirements -- GitLab