diff --git a/public/v0.0.2/5.1/index.html b/public/v0.0.2/5.1/index.html
index 1175ac506911a1f7ca8f90fd40d3d9b47116294e..66ff123cf50ca64dd2c2cec3a5e915f7a5e6ccb3 100644
--- a/public/v0.0.2/5.1/index.html
+++ b/public/v0.0.2/5.1/index.html
@@ -1258,12 +1258,17 @@
<li>3GPP Connection Efficiency Features</li>
</ul>
<p>oneM2M is most beneficially able to support an efficient communication in the area of the IoT Device Application, while other areas, like required support of "3GPP Connection Efficiency Features" can be considered out of scope of oneM2M, and hence out of scope of this WI.
-With regards to "IoT Device Application Requirements", GSMA TS.34 <a href="#_ref_1">[1]</a> differentiates further between:
-1. Monolithic IoT Device Application Requirements: Those requirements are applicable for devices without an embedded Service layer and hence are out of scope oneM2M anyway.</p>
+With regards to "IoT Device Application Requirements", GSMA TS.34 <a href="#_ref_1">[1]</a> differentiates further between:</p>
<ol>
-<li>Tiered IoT Device Applications Requirements: Those requirements are applicable for applications providing the required functionality according to GSMA TS.34 <a href="#_ref_1">[1]</a> , cooperatively together with the embedded Service layer.
-. </li>
-<li>IoT Embedded Service Layer Requirements: Those requirements are applicable for the embedded Service layer, providing the required functionality according to GSMA TS.34 [i.1]</li>
+<li>
+<p>Monolithic IoT Device Application Requirements: Those requirements are applicable for devices without an embedded Service layer and hence are out of scope oneM2M anyway.</p>
+</li>
+<li>
+<p>Tiered IoT Device Applications Requirements: Those requirements are applicable for applications providing the required functionality according to GSMA TS.34 <a href="#_ref_1">[1]</a> , cooperatively together with the embedded Service layer.</p>
+</li>
+<li>
+<p>IoT Embedded Service Layer Requirements: Those requirements are applicable for the embedded Service layer, providing the required functionality according to GSMA TS.34 [i.1]</p>
+</li>
</ol>
<p>While the main focus of this work is primarily on 2) and 3) further requirements in GSMA TS.34 <a href="#_ref_1">[1]</a> have been screened, analysed and used to inspire functionality to be taken for oneM2M to ensure an efficient IoT communication.</p>
<p>The considered Requirements out of GSMA TS.34 <a href="#_ref_1">[1]</a> in the context of oneM2M are listed in the subsequent sections, with the respective numbering schema kept as used in TS.34 <a href="#_ref_1">[1]</a> , for your reference.</p>
diff --git a/public/v0.0.2/5.2/index.html b/public/v0.0.2/5.2/index.html
index a15a408cfb724c1824f5856dca721b05805e5106..fec08cd0295476be01ade8019f8251068f4a31f3 100644
--- a/public/v0.0.2/5.2/index.html
+++ b/public/v0.0.2/5.2/index.html
@@ -1245,13 +1245,38 @@
<h1>5.2 IoT Device Requirements</h1>
-<p>**Table 5.2-1: GSMA defined requirements from GSMA TS 34 <a href="#_ref_1">[1]</a> **
-| Requirement ID | Description from GSMA TS 34 <a href="#_ref_1">[1]</a> | Reference clause |
-| ------ | ------ | ------ |
-|TS.34_3.0_REQ_001|The IoT Device SHOULD conform to all IoT Device Application requirements defined in TS.34, section 4.| 5.4 |
-|TS.34_3.0_REQ_002|The IoT Device SHALL conform to all Communication Module requirements defined in TS.34, section 5.| Not within the scope of oneM2M|
-|TS.34_3.0_REQ_003|The IoT Device SHOULD conform to GSMA TS.24 "Operator Minimum Acceptance Values for Device Antenna Performance" [x].|Not within the scope of oneM2M |
-|TS.34_3.0_REQ_004|When required by the Mobile Network Operator, the IoT Device SHALL be certified by the GCF and/or the PTCRB.|Recommended by oneM2M. Conformance test cases are defined in TS-0018 [i.4]. Profiles are defined in TS-0025 [i.5]|</p>
+<p><strong>Table 5.2-1: GSMA defined requirements from GSMA TS 34 <a href="#_ref_1">[1]</a></strong></p>
+<table>
+<thead>
+<tr>
+<th>Requirement ID</th>
+<th>Description from GSMA TS 34 <a href="#_ref_1">[1]</a></th>
+<th>Reference clause</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td>TS.34_3.0_REQ_001</td>
+<td>The IoT Device SHOULD conform to all IoT Device Application requirements defined in TS.34, section 4.</td>
+<td>5.4</td>
+</tr>
+<tr>
+<td>TS.34_3.0_REQ_002</td>
+<td>The IoT Device SHALL conform to all Communication Module requirements defined in TS.34, section 5.</td>
+<td>Not within the scope of oneM2M</td>
+</tr>
+<tr>
+<td>TS.34_3.0_REQ_003</td>
+<td>The IoT Device SHOULD conform to GSMA TS.24 "Operator Minimum Acceptance Values for Device Antenna Performance" [x].</td>
+<td>Not within the scope of oneM2M</td>
+</tr>
+<tr>
+<td>TS.34_3.0_REQ_004</td>
+<td>When required by the Mobile Network Operator, the IoT Device SHALL be certified by the GCF and/or the PTCRB.</td>
+<td>Recommended by oneM2M. Conformance test cases are defined in TS-0018 [i.4]. Profiles are defined in TS-0025 [i.5]</td>
+</tr>
+</tbody>
+</table>
diff --git a/public/v0.0.2/5.4/index.html b/public/v0.0.2/5.4/index.html
index 583cc4d9fc051c6eb974e8f478b8c9fd52c5e390..203742dd85a0048ac1609df5a9912e33db8bbb22 100644
--- a/public/v0.0.2/5.4/index.html
+++ b/public/v0.0.2/5.4/index.html
@@ -1246,13 +1246,38 @@
<h1>5.4 Tiered IoT Device Application Requirements</h1>
<p>In the GSMA evolved architecture the Tiered IoT Device Application performs the business logic of the IoT solution. The GSMA requirements for such an application are captured in table 5.4-1.</p>
-<p><strong>Table 5.4 1: Tiered IoT Device Requirements</strong>
-| Requirement ID | Description from GSMA TS 34 <a href="#_ref_1">[1]</a> | Reference clause |
-| ------ | ------ | ------ |
-|TS.34_4.1_REQ_001|If data speed and latency is critical to the IoT Service the IoT Device Application should be able to retrieve mobile network speed and connection quality information from the IoT Embedded Service Layer in order to request the appropriate quality of content from the IoT Service Platform.|See clause 6.1 |
-|TS.34_4.1_REQ_002|The IoT Device Application should always be prepared to handle situations when communication requests fail, when such failure is reported by the IoT Embedded Service Layer.|See clause 6.2 |
-|TS.34_4.1_REQ_003|Each time there is a need to send data over the mobile network the IoT Device Application should classify the priority of each communication. For example, the IoT Device Application should distinguish between data that requires instantaneous transmission and delay tolerant data that could be aggregated and/or sent during non-peak hours. Such information about the priority of the communication should be communicated to the IoT Embedded Service Layer.|<mark>See below [UPDATE THIS]</mark>|
-|TS.34_4.1_REQ_004|When an IoT Device Application does not need to perform regular data transmissions and it can tolerate some latency for its IoT Service, it should communicate this information to the IoT Embedded Service Layer so that it can use this information in its interactions with the network.|<mark>See below [UPDATE THIS]</mark>|</p>
+<p><strong>Table 5.4 1: Tiered IoT Device Requirements</strong></p>
+<table>
+<thead>
+<tr>
+<th>Requirement ID</th>
+<th>Description from GSMA TS 34 <a href="#_ref_1">[1]</a></th>
+<th>Reference clause</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+<td>TS.34_4.1_REQ_001</td>
+<td>If data speed and latency is critical to the IoT Service the IoT Device Application should be able to retrieve mobile network speed and connection quality information from the IoT Embedded Service Layer in order to request the appropriate quality of content from the IoT Service Platform.</td>
+<td>See clause 6.1</td>
+</tr>
+<tr>
+<td>TS.34_4.1_REQ_002</td>
+<td>The IoT Device Application should always be prepared to handle situations when communication requests fail, when such failure is reported by the IoT Embedded Service Layer.</td>
+<td>See clause 6.2</td>
+</tr>
+<tr>
+<td>TS.34_4.1_REQ_003</td>
+<td>Each time there is a need to send data over the mobile network the IoT Device Application should classify the priority of each communication. For example, the IoT Device Application should distinguish between data that requires instantaneous transmission and delay tolerant data that could be aggregated and/or sent during non-peak hours. Such information about the priority of the communication should be communicated to the IoT Embedded Service Layer.</td>
+<td><mark>See below [UPDATE THIS]</mark></td>
+</tr>
+<tr>
+<td>TS.34_4.1_REQ_004</td>
+<td>When an IoT Device Application does not need to perform regular data transmissions and it can tolerate some latency for its IoT Service, it should communicate this information to the IoT Embedded Service Layer so that it can use this information in its interactions with the network.</td>
+<td><mark>See below [UPDATE THIS]</mark></td>
+</tr>
+</tbody>
+</table>
diff --git a/public/v0.0.2/download/TR-0063-oneM2M-Effective_IoT_Communication_to_Protect_3GPP_Networks_v0.0.2.docx b/public/v0.0.2/download/TR-0063-oneM2M-Effective_IoT_Communication_to_Protect_3GPP_Networks_v0.0.2.docx
index 3d72843cb4e9b76a9f2f3c3e5d374596b21958a9..d7ff8422944af0f4adfd3e10308c4d3625b4d21d 100644
Binary files a/public/v0.0.2/download/TR-0063-oneM2M-Effective_IoT_Communication_to_Protect_3GPP_Networks_v0.0.2.docx and b/public/v0.0.2/download/TR-0063-oneM2M-Effective_IoT_Communication_to_Protect_3GPP_Networks_v0.0.2.docx differ
diff --git a/public/v0.0.2/download/TR-0063-oneM2M-Effective_IoT_Communication_to_Protect_3GPP_Networks_v0.0.2.epub b/public/v0.0.2/download/TR-0063-oneM2M-Effective_IoT_Communication_to_Protect_3GPP_Networks_v0.0.2.epub
index fa792855cf9fdcc4bc39845942df1c9b5f73fa5d..4a8cc0ee1c092aeff848d41502419e9012d58440 100644
Binary files a/public/v0.0.2/download/TR-0063-oneM2M-Effective_IoT_Communication_to_Protect_3GPP_Networks_v0.0.2.epub and b/public/v0.0.2/download/TR-0063-oneM2M-Effective_IoT_Communication_to_Protect_3GPP_Networks_v0.0.2.epub differ
diff --git a/public/v0.0.2/download/TR-0063-oneM2M-Effective_IoT_Communication_to_Protect_3GPP_Networks_v0.0.2.pdf b/public/v0.0.2/download/TR-0063-oneM2M-Effective_IoT_Communication_to_Protect_3GPP_Networks_v0.0.2.pdf
index 1aeed27406eb009b060668ce5599b9112237d23c..8fa3afb5e50b3e8e9c28f6970d56cbcb9f188226 100644
Binary files a/public/v0.0.2/download/TR-0063-oneM2M-Effective_IoT_Communication_to_Protect_3GPP_Networks_v0.0.2.pdf and b/public/v0.0.2/download/TR-0063-oneM2M-Effective_IoT_Communication_to_Protect_3GPP_Networks_v0.0.2.pdf differ
diff --git a/public/v0.0.2/feed_json_created.json b/public/v0.0.2/feed_json_created.json
index 8195c72640ec56ec817b86051a22837a31efb9b1..2807385e81610a97585c4ef32a42e2313026c660 100644
--- a/public/v0.0.2/feed_json_created.json
+++ b/public/v0.0.2/feed_json_created.json
@@ -1 +1 @@
-{"version": "https://jsonfeed.org/version/1", "title": "oneM2M Specifications", "home_page_url": "https://specifications.onem2m.org/ts-0019/v0.0.2/", "feed_url": "https://specifications.onem2m.org/ts-0019/v0.0.2/feed_json_created.json", "description": "oneM2M Specifications navigator", "icon": null, "authors": [], "language": "en", "items": [{"id": "https://specifications.onem2m.org/ts-0019/v0.0.2/download/", "url": "https://specifications.onem2m.org/ts-0019/v0.0.2/download/", "title": "Download", "content_html": "<p>Download baseline for TR-0063 version v0.0.2:</p>\n<p><a href=\"TR-0063-oneM2M-Effective_IoT_Communication_to_Protect_3GPP_Networks_v0.0.2.docx\"><img alt=\"Word\" src=\"images/Word.png\"></a>[![...</p>", "image": null, "date_published": "2024-04-25T11:25:32.015435+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v0.0.2/y/", "url": "https://specifications.onem2m.org/ts-0019/v0.0.2/y/", "title": "Annex <y>:Bibliography", "content_html": "<p><mark>The annex entitled \"Bibliography\" is optional.</mark></p>\n<p><mark>It shall contain a list of standards, books, articles, or other sources on a particular su...</p>", "image": null, "date_published": "2024-04-25T11:25:31.998193+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v0.0.2/m01K3C/", "url": "https://specifications.onem2m.org/ts-0019/v0.0.2/m01K3C/", "title": "Annexes", "content_html": "<p><mark>Each annex shall start on a new page (insert a page break between annexes A and B, annexes B and C, etc.).<mark></p>", "image": null, "date_published": "2024-04-25T11:25:31.982173+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v0.0.2/K763Qg/", "url": "https://specifications.onem2m.org/ts-0019/v0.0.2/K763Qg/", "title": " First clause of the annex", "content_html": "<p><Text></p>\n<h3>B.1.1 First subdivided clause of the annex</h3>\n<p><Text></p>\n<p><mark><PAGE BREAK></mark></p>", "image": null, "date_published": "2024-04-25T11:25:31.963870+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v0.0.2/B/", "url": "https://specifications.onem2m.org/ts-0019/v0.0.2/B/", "title": "Introduction", "content_html": "<p><Text></p>", "image": null, "date_published": "2024-04-25T11:25:31.943451+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v0.0.2/A/", "url": "https://specifications.onem2m.org/ts-0019/v0.0.2/A/", "title": "Annex <A>:Title of annex", "content_html": "<p><Text></p>\n<p><mark><PAGE BREAK></mark></p>", "image": null, "date_published": "2024-04-25T11:25:31.926786+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v0.0.2/9/", "url": "https://specifications.onem2m.org/ts-0019/v0.0.2/9/", "title": "9", "content_html": "", "image": null, "date_published": "2024-04-25T11:25:31.911377+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v0.0.2/9.1/", "url": "https://specifications.onem2m.org/ts-0019/v0.0.2/9.1/", "title": "9.1\tIntroduction", "content_html": "<p>Editor\u2019s Note: This clause describes the coverage of GSMA TS.34 requirements. Identifies possible feedback to GSMA for further work on this topic.</p>", "image": null, "date_published": "2024-04-25T11:25:31.896193+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v0.0.2/8/", "url": "https://specifications.onem2m.org/ts-0019/v0.0.2/8/", "title": "8", "content_html": "", "image": null, "date_published": "2024-04-25T11:25:31.880289+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v0.0.2/8.2/", "url": "https://specifications.onem2m.org/ts-0019/v0.0.2/8.2/", "title": "8.2\t Enhancement 1 Description", "content_html": "<p>Editor\u2019s Note: This clause describes a specific change</p>", "image": null, "date_published": "2024-04-25T11:25:31.864134+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v0.0.2/8.1/", "url": "https://specifications.onem2m.org/ts-0019/v0.0.2/8.1/", "title": "8.1 Introduction", "content_html": "<p>Editor\u2019s Note: This clause proposes enhancements to existing specifications if any that are identified in Clause 6</p>", "image": null, "date_published": "2024-04-25T11:25:31.846667+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v0.0.2/7/", "url": "https://specifications.onem2m.org/ts-0019/v0.0.2/7/", "title": "7", "content_html": "", "image": null, "date_published": "2024-04-25T11:25:31.830452+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v0.0.2/7.2/", "url": "https://specifications.onem2m.org/ts-0019/v0.0.2/7.2/", "title": "7.2 Scenario 1", "content_html": "", "image": null, "date_published": "2024-04-25T11:25:31.815806+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v0.0.2/7.1/", "url": "https://specifications.onem2m.org/ts-0019/v0.0.2/7.1/", "title": "7.1 Introduction", "content_html": "<p>Editor\u2019s Note: This clause proposes examples that are used to describe solutions in clause 6</p>", "image": null, "date_published": "2024-04-25T11:25:31.799893+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v0.0.2/6/", "url": "https://specifications.onem2m.org/ts-0019/v0.0.2/6/", "title": "6", "content_html": "", "image": null, "date_published": "2024-04-25T11:25:31.783013+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v0.0.2/6.1/", "url": "https://specifications.onem2m.org/ts-0019/v0.0.2/6.1/", "title": "6.1 Use Case / Solution 1", "content_html": "<p>Editor\u2019s Note: To define call flows that implement the requirements described in clause 5.</p>", "image": null, "date_published": "2024-04-25T11:25:31.768364+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v0.0.2/5/", "url": "https://specifications.onem2m.org/ts-0019/v0.0.2/5/", "title": "Introduction", "content_html": "<p><Text></p>", "image": null, "date_published": "2024-04-25T11:25:31.753278+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v0.0.2/5.4/", "url": "https://specifications.onem2m.org/ts-0019/v0.0.2/5.4/", "title": "5.4 Tiered IoT Device Application Requirements", "content_html": "<p>In the GSMA evolved architecture the Tiered IoT Device Application performs the business logic of the IoT solution. The GSMA requirements for such an applica...</p>", "image": null, "date_published": "2024-04-25T11:25:31.736333+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v0.0.2/5.3/", "url": "https://specifications.onem2m.org/ts-0019/v0.0.2/5.3/", "title": "5.3 IOT Device Application Requirements", "content_html": "<p>This clause is derived from GSMA TS.34 <a href=\"#_ref_1\">[1]</a> , clause 4. Two architectures are described in GSMA TS.34 <a href=\"#_ref_1\">[1]</a> , where ...</p>", "image": null, "date_published": "2024-04-25T11:25:31.716793+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v0.0.2/5.2/", "url": "https://specifications.onem2m.org/ts-0019/v0.0.2/5.2/", "title": "5.2 IoT Device Requirements", "content_html": "<p>**Table 5.2-1: GSMA defined requirements from GSMA TS 34 <a href=\"#_ref_1\">[1]</a> **\n| Requirement ID | Description from GSMA TS 34 <a href=\"#_ref_1\">[1]</a...</p>", "image": null, "date_published": "2024-04-25T11:25:31.699981+00:00", "authors": [], "tags": null}]}
\ No newline at end of file
+{"version": "https://jsonfeed.org/version/1", "title": "oneM2M Specifications", "home_page_url": "https://specifications.onem2m.org/ts-0019/v0.0.2/", "feed_url": "https://specifications.onem2m.org/ts-0019/v0.0.2/feed_json_created.json", "description": "oneM2M Specifications navigator", "icon": null, "authors": [], "language": "en", "items": [{"id": "https://specifications.onem2m.org/ts-0019/v0.0.2/download/", "url": "https://specifications.onem2m.org/ts-0019/v0.0.2/download/", "title": "Download", "content_html": "<p>Download baseline for TR-0063 version v0.0.2:</p>\n<p><a href=\"TR-0063-oneM2M-Effective_IoT_Communication_to_Protect_3GPP_Networks_v0.0.2.docx\"><img alt=\"Word\" src=\"images/Word.png\"></a>[![...</p>", "image": null, "date_published": "2024-04-25T11:52:11.225910+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v0.0.2/y/", "url": "https://specifications.onem2m.org/ts-0019/v0.0.2/y/", "title": "Annex <y>:Bibliography", "content_html": "<p><mark>The annex entitled \"Bibliography\" is optional.</mark></p>\n<p><mark>It shall contain a list of standards, books, articles, or other sources on a particular su...</p>", "image": null, "date_published": "2024-04-25T11:52:11.209474+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v0.0.2/m01K3C/", "url": "https://specifications.onem2m.org/ts-0019/v0.0.2/m01K3C/", "title": "Annexes", "content_html": "<p><mark>Each annex shall start on a new page (insert a page break between annexes A and B, annexes B and C, etc.).<mark></p>", "image": null, "date_published": "2024-04-25T11:52:11.193597+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v0.0.2/K763Qg/", "url": "https://specifications.onem2m.org/ts-0019/v0.0.2/K763Qg/", "title": " First clause of the annex", "content_html": "<p><Text></p>\n<h3>B.1.1 First subdivided clause of the annex</h3>\n<p><Text></p>\n<p><mark><PAGE BREAK></mark></p>", "image": null, "date_published": "2024-04-25T11:52:11.178376+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v0.0.2/B/", "url": "https://specifications.onem2m.org/ts-0019/v0.0.2/B/", "title": "Introduction", "content_html": "<p><Text></p>", "image": null, "date_published": "2024-04-25T11:52:11.155068+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v0.0.2/A/", "url": "https://specifications.onem2m.org/ts-0019/v0.0.2/A/", "title": "Annex <A>:Title of annex", "content_html": "<p><Text></p>\n<p><mark><PAGE BREAK></mark></p>", "image": null, "date_published": "2024-04-25T11:52:11.123564+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v0.0.2/9/", "url": "https://specifications.onem2m.org/ts-0019/v0.0.2/9/", "title": "9", "content_html": "", "image": null, "date_published": "2024-04-25T11:52:11.107720+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v0.0.2/9.1/", "url": "https://specifications.onem2m.org/ts-0019/v0.0.2/9.1/", "title": "9.1\tIntroduction", "content_html": "<p>Editor\u2019s Note: This clause describes the coverage of GSMA TS.34 requirements. Identifies possible feedback to GSMA for further work on this topic.</p>", "image": null, "date_published": "2024-04-25T11:52:11.092266+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v0.0.2/8/", "url": "https://specifications.onem2m.org/ts-0019/v0.0.2/8/", "title": "8", "content_html": "", "image": null, "date_published": "2024-04-25T11:52:11.078046+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v0.0.2/8.2/", "url": "https://specifications.onem2m.org/ts-0019/v0.0.2/8.2/", "title": "8.2\t Enhancement 1 Description", "content_html": "<p>Editor\u2019s Note: This clause describes a specific change</p>", "image": null, "date_published": "2024-04-25T11:52:11.063857+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v0.0.2/8.1/", "url": "https://specifications.onem2m.org/ts-0019/v0.0.2/8.1/", "title": "8.1 Introduction", "content_html": "<p>Editor\u2019s Note: This clause proposes enhancements to existing specifications if any that are identified in Clause 6</p>", "image": null, "date_published": "2024-04-25T11:52:11.048938+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v0.0.2/7/", "url": "https://specifications.onem2m.org/ts-0019/v0.0.2/7/", "title": "7", "content_html": "", "image": null, "date_published": "2024-04-25T11:52:11.032826+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v0.0.2/7.2/", "url": "https://specifications.onem2m.org/ts-0019/v0.0.2/7.2/", "title": "7.2 Scenario 1", "content_html": "", "image": null, "date_published": "2024-04-25T11:52:11.017750+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v0.0.2/7.1/", "url": "https://specifications.onem2m.org/ts-0019/v0.0.2/7.1/", "title": "7.1 Introduction", "content_html": "<p>Editor\u2019s Note: This clause proposes examples that are used to describe solutions in clause 6</p>", "image": null, "date_published": "2024-04-25T11:52:11.003193+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v0.0.2/6/", "url": "https://specifications.onem2m.org/ts-0019/v0.0.2/6/", "title": "6", "content_html": "", "image": null, "date_published": "2024-04-25T11:52:10.988944+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v0.0.2/6.1/", "url": "https://specifications.onem2m.org/ts-0019/v0.0.2/6.1/", "title": "6.1 Use Case / Solution 1", "content_html": "<p>Editor\u2019s Note: To define call flows that implement the requirements described in clause 5.</p>", "image": null, "date_published": "2024-04-25T11:52:10.974619+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v0.0.2/5/", "url": "https://specifications.onem2m.org/ts-0019/v0.0.2/5/", "title": "Introduction", "content_html": "<p><Text></p>", "image": null, "date_published": "2024-04-25T11:52:10.958572+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v0.0.2/5.4/", "url": "https://specifications.onem2m.org/ts-0019/v0.0.2/5.4/", "title": "5.4 Tiered IoT Device Application Requirements", "content_html": "<p>In the GSMA evolved architecture the Tiered IoT Device Application performs the business logic of the IoT solution. The GSMA requirements for such an applica...</p>", "image": null, "date_published": "2024-04-25T11:52:10.941411+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v0.0.2/5.3/", "url": "https://specifications.onem2m.org/ts-0019/v0.0.2/5.3/", "title": "5.3 IOT Device Application Requirements", "content_html": "<p>This clause is derived from GSMA TS.34 <a href=\"#_ref_1\">[1]</a> , clause 4. Two architectures are described in GSMA TS.34 <a href=\"#_ref_1\">[1]</a> , where ...</p>", "image": null, "date_published": "2024-04-25T11:52:10.913259+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v0.0.2/5.2/", "url": "https://specifications.onem2m.org/ts-0019/v0.0.2/5.2/", "title": "5.2 IoT Device Requirements", "content_html": "<p><strong>Table 5.2-1: GSMA defined requirements from GSMA TS 34 <a href=\"#_ref_1\">[1]</a></strong></p>\n<p>| Requirement ID | Description from GSMA TS 34 <a href=\"#_ref_1\">[1]</a...</p>", "image": null, "date_published": "2024-04-25T11:52:10.880263+00:00", "authors": [], "tags": null}]}
\ No newline at end of file
diff --git a/public/v0.0.2/feed_json_updated.json b/public/v0.0.2/feed_json_updated.json
index cf0fc28cdbb92a63cdabe50a903132618bb09ec2..141deefbc6d0c7fb9992cce5a09bbeeff994e35f 100644
--- a/public/v0.0.2/feed_json_updated.json
+++ b/public/v0.0.2/feed_json_updated.json
@@ -1 +1 @@
-{"version": "https://jsonfeed.org/version/1", "title": "oneM2M Specifications", "home_page_url": "https://specifications.onem2m.org/ts-0019/v0.0.2/", "feed_url": "https://specifications.onem2m.org/ts-0019/v0.0.2/feed_json_updated.json", "description": "oneM2M Specifications navigator", "icon": null, "authors": [], "language": "en", "items": [{"id": "https://specifications.onem2m.org/ts-0019/v0.0.2/download/", "url": "https://specifications.onem2m.org/ts-0019/v0.0.2/download/", "title": "Download", "content_html": "<p>Download baseline for TR-0063 version v0.0.2:</p>\n<p><a href=\"TR-0063-oneM2M-Effective_IoT_Communication_to_Protect_3GPP_Networks_v0.0.2.docx\"><img alt=\"Word\" src=\"images/Word.png\"></a>[![...</p>", "image": null, "date_modified": "2024-04-25T11:25:32.015449+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v0.0.2/y/", "url": "https://specifications.onem2m.org/ts-0019/v0.0.2/y/", "title": "Annex <y>:Bibliography", "content_html": "<p><mark>The annex entitled \"Bibliography\" is optional.</mark></p>\n<p><mark>It shall contain a list of standards, books, articles, or other sources on a particular su...</p>", "image": null, "date_modified": "2024-04-25T11:25:31.998206+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v0.0.2/m01K3C/", "url": "https://specifications.onem2m.org/ts-0019/v0.0.2/m01K3C/", "title": "Annexes", "content_html": "<p><mark>Each annex shall start on a new page (insert a page break between annexes A and B, annexes B and C, etc.).<mark></p>", "image": null, "date_modified": "2024-04-25T11:25:31.982186+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v0.0.2/K763Qg/", "url": "https://specifications.onem2m.org/ts-0019/v0.0.2/K763Qg/", "title": " First clause of the annex", "content_html": "<p><Text></p>\n<h3>B.1.1 First subdivided clause of the annex</h3>\n<p><Text></p>\n<p><mark><PAGE BREAK></mark></p>", "image": null, "date_modified": "2024-04-25T11:25:31.963885+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v0.0.2/B/", "url": "https://specifications.onem2m.org/ts-0019/v0.0.2/B/", "title": "Introduction", "content_html": "<p><Text></p>", "image": null, "date_modified": "2024-04-25T11:25:31.943464+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v0.0.2/A/", "url": "https://specifications.onem2m.org/ts-0019/v0.0.2/A/", "title": "Annex <A>:Title of annex", "content_html": "<p><Text></p>\n<p><mark><PAGE BREAK></mark></p>", "image": null, "date_modified": "2024-04-25T11:25:31.926804+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v0.0.2/9/", "url": "https://specifications.onem2m.org/ts-0019/v0.0.2/9/", "title": "9", "content_html": "", "image": null, "date_modified": "2024-04-25T11:25:31.911390+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v0.0.2/9.1/", "url": "https://specifications.onem2m.org/ts-0019/v0.0.2/9.1/", "title": "9.1\tIntroduction", "content_html": "<p>Editor\u2019s Note: This clause describes the coverage of GSMA TS.34 requirements. Identifies possible feedback to GSMA for further work on this topic.</p>", "image": null, "date_modified": "2024-04-25T11:25:31.896207+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v0.0.2/8/", "url": "https://specifications.onem2m.org/ts-0019/v0.0.2/8/", "title": "8", "content_html": "", "image": null, "date_modified": "2024-04-25T11:25:31.880304+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v0.0.2/8.2/", "url": "https://specifications.onem2m.org/ts-0019/v0.0.2/8.2/", "title": "8.2\t Enhancement 1 Description", "content_html": "<p>Editor\u2019s Note: This clause describes a specific change</p>", "image": null, "date_modified": "2024-04-25T11:25:31.864148+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v0.0.2/8.1/", "url": "https://specifications.onem2m.org/ts-0019/v0.0.2/8.1/", "title": "8.1 Introduction", "content_html": "<p>Editor\u2019s Note: This clause proposes enhancements to existing specifications if any that are identified in Clause 6</p>", "image": null, "date_modified": "2024-04-25T11:25:31.846681+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v0.0.2/7/", "url": "https://specifications.onem2m.org/ts-0019/v0.0.2/7/", "title": "7", "content_html": "", "image": null, "date_modified": "2024-04-25T11:25:31.830466+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v0.0.2/7.2/", "url": "https://specifications.onem2m.org/ts-0019/v0.0.2/7.2/", "title": "7.2 Scenario 1", "content_html": "", "image": null, "date_modified": "2024-04-25T11:25:31.815820+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v0.0.2/7.1/", "url": "https://specifications.onem2m.org/ts-0019/v0.0.2/7.1/", "title": "7.1 Introduction", "content_html": "<p>Editor\u2019s Note: This clause proposes examples that are used to describe solutions in clause 6</p>", "image": null, "date_modified": "2024-04-25T11:25:31.799907+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v0.0.2/6/", "url": "https://specifications.onem2m.org/ts-0019/v0.0.2/6/", "title": "6", "content_html": "", "image": null, "date_modified": "2024-04-25T11:25:31.783028+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v0.0.2/6.1/", "url": "https://specifications.onem2m.org/ts-0019/v0.0.2/6.1/", "title": "6.1 Use Case / Solution 1", "content_html": "<p>Editor\u2019s Note: To define call flows that implement the requirements described in clause 5.</p>", "image": null, "date_modified": "2024-04-25T11:25:31.768377+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v0.0.2/5/", "url": "https://specifications.onem2m.org/ts-0019/v0.0.2/5/", "title": "Introduction", "content_html": "<p><Text></p>", "image": null, "date_modified": "2024-04-25T11:25:31.753292+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v0.0.2/5.4/", "url": "https://specifications.onem2m.org/ts-0019/v0.0.2/5.4/", "title": "5.4 Tiered IoT Device Application Requirements", "content_html": "<p>In the GSMA evolved architecture the Tiered IoT Device Application performs the business logic of the IoT solution. The GSMA requirements for such an applica...</p>", "image": null, "date_modified": "2024-04-25T11:25:31.736347+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v0.0.2/5.3/", "url": "https://specifications.onem2m.org/ts-0019/v0.0.2/5.3/", "title": "5.3 IOT Device Application Requirements", "content_html": "<p>This clause is derived from GSMA TS.34 <a href=\"#_ref_1\">[1]</a> , clause 4. Two architectures are described in GSMA TS.34 <a href=\"#_ref_1\">[1]</a> , where ...</p>", "image": null, "date_modified": "2024-04-25T11:25:31.716810+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v0.0.2/5.2/", "url": "https://specifications.onem2m.org/ts-0019/v0.0.2/5.2/", "title": "5.2 IoT Device Requirements", "content_html": "<p>**Table 5.2-1: GSMA defined requirements from GSMA TS 34 <a href=\"#_ref_1\">[1]</a> **\n| Requirement ID | Description from GSMA TS 34 <a href=\"#_ref_1\">[1]</a...</p>", "image": null, "date_modified": "2024-04-25T11:25:31.699995+00:00", "authors": [], "tags": null}]}
\ No newline at end of file
+{"version": "https://jsonfeed.org/version/1", "title": "oneM2M Specifications", "home_page_url": "https://specifications.onem2m.org/ts-0019/v0.0.2/", "feed_url": "https://specifications.onem2m.org/ts-0019/v0.0.2/feed_json_updated.json", "description": "oneM2M Specifications navigator", "icon": null, "authors": [], "language": "en", "items": [{"id": "https://specifications.onem2m.org/ts-0019/v0.0.2/download/", "url": "https://specifications.onem2m.org/ts-0019/v0.0.2/download/", "title": "Download", "content_html": "<p>Download baseline for TR-0063 version v0.0.2:</p>\n<p><a href=\"TR-0063-oneM2M-Effective_IoT_Communication_to_Protect_3GPP_Networks_v0.0.2.docx\"><img alt=\"Word\" src=\"images/Word.png\"></a>[![...</p>", "image": null, "date_modified": "2024-04-25T11:52:11.225922+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v0.0.2/y/", "url": "https://specifications.onem2m.org/ts-0019/v0.0.2/y/", "title": "Annex <y>:Bibliography", "content_html": "<p><mark>The annex entitled \"Bibliography\" is optional.</mark></p>\n<p><mark>It shall contain a list of standards, books, articles, or other sources on a particular su...</p>", "image": null, "date_modified": "2024-04-25T11:52:11.209486+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v0.0.2/m01K3C/", "url": "https://specifications.onem2m.org/ts-0019/v0.0.2/m01K3C/", "title": "Annexes", "content_html": "<p><mark>Each annex shall start on a new page (insert a page break between annexes A and B, annexes B and C, etc.).<mark></p>", "image": null, "date_modified": "2024-04-25T11:52:11.193608+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v0.0.2/K763Qg/", "url": "https://specifications.onem2m.org/ts-0019/v0.0.2/K763Qg/", "title": " First clause of the annex", "content_html": "<p><Text></p>\n<h3>B.1.1 First subdivided clause of the annex</h3>\n<p><Text></p>\n<p><mark><PAGE BREAK></mark></p>", "image": null, "date_modified": "2024-04-25T11:52:11.178387+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v0.0.2/B/", "url": "https://specifications.onem2m.org/ts-0019/v0.0.2/B/", "title": "Introduction", "content_html": "<p><Text></p>", "image": null, "date_modified": "2024-04-25T11:52:11.155094+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v0.0.2/A/", "url": "https://specifications.onem2m.org/ts-0019/v0.0.2/A/", "title": "Annex <A>:Title of annex", "content_html": "<p><Text></p>\n<p><mark><PAGE BREAK></mark></p>", "image": null, "date_modified": "2024-04-25T11:52:11.123576+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v0.0.2/9/", "url": "https://specifications.onem2m.org/ts-0019/v0.0.2/9/", "title": "9", "content_html": "", "image": null, "date_modified": "2024-04-25T11:52:11.107733+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v0.0.2/9.1/", "url": "https://specifications.onem2m.org/ts-0019/v0.0.2/9.1/", "title": "9.1\tIntroduction", "content_html": "<p>Editor\u2019s Note: This clause describes the coverage of GSMA TS.34 requirements. Identifies possible feedback to GSMA for further work on this topic.</p>", "image": null, "date_modified": "2024-04-25T11:52:11.092281+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v0.0.2/8/", "url": "https://specifications.onem2m.org/ts-0019/v0.0.2/8/", "title": "8", "content_html": "", "image": null, "date_modified": "2024-04-25T11:52:11.078059+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v0.0.2/8.2/", "url": "https://specifications.onem2m.org/ts-0019/v0.0.2/8.2/", "title": "8.2\t Enhancement 1 Description", "content_html": "<p>Editor\u2019s Note: This clause describes a specific change</p>", "image": null, "date_modified": "2024-04-25T11:52:11.063869+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v0.0.2/8.1/", "url": "https://specifications.onem2m.org/ts-0019/v0.0.2/8.1/", "title": "8.1 Introduction", "content_html": "<p>Editor\u2019s Note: This clause proposes enhancements to existing specifications if any that are identified in Clause 6</p>", "image": null, "date_modified": "2024-04-25T11:52:11.048950+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v0.0.2/7/", "url": "https://specifications.onem2m.org/ts-0019/v0.0.2/7/", "title": "7", "content_html": "", "image": null, "date_modified": "2024-04-25T11:52:11.032840+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v0.0.2/7.2/", "url": "https://specifications.onem2m.org/ts-0019/v0.0.2/7.2/", "title": "7.2 Scenario 1", "content_html": "", "image": null, "date_modified": "2024-04-25T11:52:11.017764+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v0.0.2/7.1/", "url": "https://specifications.onem2m.org/ts-0019/v0.0.2/7.1/", "title": "7.1 Introduction", "content_html": "<p>Editor\u2019s Note: This clause proposes examples that are used to describe solutions in clause 6</p>", "image": null, "date_modified": "2024-04-25T11:52:11.003206+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v0.0.2/6/", "url": "https://specifications.onem2m.org/ts-0019/v0.0.2/6/", "title": "6", "content_html": "", "image": null, "date_modified": "2024-04-25T11:52:10.988962+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v0.0.2/6.1/", "url": "https://specifications.onem2m.org/ts-0019/v0.0.2/6.1/", "title": "6.1 Use Case / Solution 1", "content_html": "<p>Editor\u2019s Note: To define call flows that implement the requirements described in clause 5.</p>", "image": null, "date_modified": "2024-04-25T11:52:10.974636+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v0.0.2/5/", "url": "https://specifications.onem2m.org/ts-0019/v0.0.2/5/", "title": "Introduction", "content_html": "<p><Text></p>", "image": null, "date_modified": "2024-04-25T11:52:10.958588+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v0.0.2/5.4/", "url": "https://specifications.onem2m.org/ts-0019/v0.0.2/5.4/", "title": "5.4 Tiered IoT Device Application Requirements", "content_html": "<p>In the GSMA evolved architecture the Tiered IoT Device Application performs the business logic of the IoT solution. The GSMA requirements for such an applica...</p>", "image": null, "date_modified": "2024-04-25T11:52:10.941430+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v0.0.2/5.3/", "url": "https://specifications.onem2m.org/ts-0019/v0.0.2/5.3/", "title": "5.3 IOT Device Application Requirements", "content_html": "<p>This clause is derived from GSMA TS.34 <a href=\"#_ref_1\">[1]</a> , clause 4. Two architectures are described in GSMA TS.34 <a href=\"#_ref_1\">[1]</a> , where ...</p>", "image": null, "date_modified": "2024-04-25T11:52:10.913303+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v0.0.2/5.2/", "url": "https://specifications.onem2m.org/ts-0019/v0.0.2/5.2/", "title": "5.2 IoT Device Requirements", "content_html": "<p><strong>Table 5.2-1: GSMA defined requirements from GSMA TS 34 <a href=\"#_ref_1\">[1]</a></strong></p>\n<p>| Requirement ID | Description from GSMA TS 34 <a href=\"#_ref_1\">[1]</a...</p>", "image": null, "date_modified": "2024-04-25T11:52:10.880276+00:00", "authors": [], "tags": null}]}
\ No newline at end of file
diff --git a/public/v0.0.2/feed_rss_created.xml b/public/v0.0.2/feed_rss_created.xml
index fdbc05c8be8d39e8b4dd428f457f4b32ff1b8187..d03975a00148e7dcf71f89db7a807bdb41fc4ad4 100644
--- a/public/v0.0.2/feed_rss_created.xml
+++ b/public/v0.0.2/feed_rss_created.xml
@@ -1 +1 @@
-<?xml version="1.0" encoding="UTF-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/"> <channel><title>oneM2M Specifications</title><description>oneM2M Specifications navigator</description><link>https://specifications.onem2m.org/ts-0019/v0.0.2/</link><atom:link href="https://specifications.onem2m.org/ts-0019/v0.0.2/feed_rss_created.xml" rel="self" type="application/rss+xml" /><language>en</language> <pubDate>Thu, 25 Apr 2024 11:25:31 -0000</pubDate> <lastBuildDate>Thu, 25 Apr 2024 11:25:31 -0000</lastBuildDate> <ttl>1440</ttl> <generator>MkDocs RSS plugin - v1.12.1</generator> <item> <title>Download</title> <description><p>Download baseline for TR-0063 version v0.0.2:</p><p><a href="TR-0063-oneM2M-Effective_IoT_Communication_to_Protect_3GPP_Networks_v0.0.2.docx"><img alt="Word" src="images/Word.png"></a>[![...</p></description><link>https://specifications.onem2m.org/ts-0019/v0.0.2/download/</link> <pubDate>Thu, 25 Apr 2024 11:25:32 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v0.0.2/feed_rss_created.xml">oneM2M Specifications</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v0.0.2/download/</guid> </item> <item> <title>Annex &lt;y>:Bibliography</title> <description><p><mark>The annex entitled "Bibliography" is optional.</mark></p><p><mark>It shall contain a list of standards, books, articles, or other sources on a particular su...</p></description><link>https://specifications.onem2m.org/ts-0019/v0.0.2/y/</link> <pubDate>Thu, 25 Apr 2024 11:25:31 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v0.0.2/feed_rss_created.xml">oneM2M Specifications</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v0.0.2/y/</guid> </item> <item> <title>Annexes</title> <description><p><mark>Each annex shall start on a new page (insert a page break between annexes A and B, annexes B and C, etc.).<mark></p></description><link>https://specifications.onem2m.org/ts-0019/v0.0.2/m01K3C/</link> <pubDate>Thu, 25 Apr 2024 11:25:31 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v0.0.2/feed_rss_created.xml">oneM2M Specifications</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v0.0.2/m01K3C/</guid> </item> <item> <title> First clause of the annex</title> <description><p>&lt;Text&gt;</p><h3>B.1.1 First subdivided clause of the annex</h3><p>&lt;Text&gt;</p><p><mark>&lt;PAGE BREAK&gt;</mark></p></description><link>https://specifications.onem2m.org/ts-0019/v0.0.2/K763Qg/</link> <pubDate>Thu, 25 Apr 2024 11:25:31 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v0.0.2/feed_rss_created.xml">oneM2M Specifications</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v0.0.2/K763Qg/</guid> </item> <item> <title>Introduction</title> <description><p>&lt;Text&gt;</p></description><link>https://specifications.onem2m.org/ts-0019/v0.0.2/B/</link> <pubDate>Thu, 25 Apr 2024 11:25:31 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v0.0.2/feed_rss_created.xml">oneM2M Specifications</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v0.0.2/B/</guid> </item> <item> <title>Annex &lt;A>:Title of annex</title> <description><p>&lt;Text&gt;</p><p><mark>&lt;PAGE BREAK&gt;</mark></p></description><link>https://specifications.onem2m.org/ts-0019/v0.0.2/A/</link> <pubDate>Thu, 25 Apr 2024 11:25:31 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v0.0.2/feed_rss_created.xml">oneM2M Specifications</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v0.0.2/A/</guid> </item> <item> <title>9</title> <description></description><link>https://specifications.onem2m.org/ts-0019/v0.0.2/9/</link> <pubDate>Thu, 25 Apr 2024 11:25:31 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v0.0.2/feed_rss_created.xml">oneM2M Specifications</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v0.0.2/9/</guid> </item> <item> <title>9.1 Introduction</title> <description><p>Editor’s Note: This clause describes the coverage of GSMA TS.34 requirements. Identifies possible feedback to GSMA for further work on this topic.</p></description><link>https://specifications.onem2m.org/ts-0019/v0.0.2/9.1/</link> <pubDate>Thu, 25 Apr 2024 11:25:31 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v0.0.2/feed_rss_created.xml">oneM2M Specifications</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v0.0.2/9.1/</guid> </item> <item> <title>8</title> <description></description><link>https://specifications.onem2m.org/ts-0019/v0.0.2/8/</link> <pubDate>Thu, 25 Apr 2024 11:25:31 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v0.0.2/feed_rss_created.xml">oneM2M Specifications</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v0.0.2/8/</guid> </item> <item> <title>8.2 Enhancement 1 Description</title> <description><p>Editor’s Note: This clause describes a specific change</p></description><link>https://specifications.onem2m.org/ts-0019/v0.0.2/8.2/</link> <pubDate>Thu, 25 Apr 2024 11:25:31 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v0.0.2/feed_rss_created.xml">oneM2M Specifications</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v0.0.2/8.2/</guid> </item> <item> <title>8.1 Introduction</title> <description><p>Editor’s Note: This clause proposes enhancements to existing specifications if any that are identified in Clause 6</p></description><link>https://specifications.onem2m.org/ts-0019/v0.0.2/8.1/</link> <pubDate>Thu, 25 Apr 2024 11:25:31 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v0.0.2/feed_rss_created.xml">oneM2M Specifications</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v0.0.2/8.1/</guid> </item> <item> <title>7</title> <description></description><link>https://specifications.onem2m.org/ts-0019/v0.0.2/7/</link> <pubDate>Thu, 25 Apr 2024 11:25:31 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v0.0.2/feed_rss_created.xml">oneM2M Specifications</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v0.0.2/7/</guid> </item> <item> <title>7.2 Scenario 1</title> <description></description><link>https://specifications.onem2m.org/ts-0019/v0.0.2/7.2/</link> <pubDate>Thu, 25 Apr 2024 11:25:31 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v0.0.2/feed_rss_created.xml">oneM2M Specifications</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v0.0.2/7.2/</guid> </item> <item> <title>7.1 Introduction</title> <description><p>Editor’s Note: This clause proposes examples that are used to describe solutions in clause 6</p></description><link>https://specifications.onem2m.org/ts-0019/v0.0.2/7.1/</link> <pubDate>Thu, 25 Apr 2024 11:25:31 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v0.0.2/feed_rss_created.xml">oneM2M Specifications</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v0.0.2/7.1/</guid> </item> <item> <title>6</title> <description></description><link>https://specifications.onem2m.org/ts-0019/v0.0.2/6/</link> <pubDate>Thu, 25 Apr 2024 11:25:31 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v0.0.2/feed_rss_created.xml">oneM2M Specifications</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v0.0.2/6/</guid> </item> <item> <title>6.1 Use Case / Solution 1</title> <description><p>Editor’s Note: To define call flows that implement the requirements described in clause 5.</p></description><link>https://specifications.onem2m.org/ts-0019/v0.0.2/6.1/</link> <pubDate>Thu, 25 Apr 2024 11:25:31 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v0.0.2/feed_rss_created.xml">oneM2M Specifications</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v0.0.2/6.1/</guid> </item> <item> <title>Introduction</title> <description><p>&lt;Text&gt;</p></description><link>https://specifications.onem2m.org/ts-0019/v0.0.2/5/</link> <pubDate>Thu, 25 Apr 2024 11:25:31 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v0.0.2/feed_rss_created.xml">oneM2M Specifications</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v0.0.2/5/</guid> </item> <item> <title>5.4 Tiered IoT Device Application Requirements</title> <description><p>In the GSMA evolved architecture the Tiered IoT Device Application performs the business logic of the IoT solution. The GSMA requirements for such an applica...</p></description><link>https://specifications.onem2m.org/ts-0019/v0.0.2/5.4/</link> <pubDate>Thu, 25 Apr 2024 11:25:31 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v0.0.2/feed_rss_created.xml">oneM2M Specifications</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v0.0.2/5.4/</guid> </item> <item> <title>5.3 IOT Device Application Requirements</title> <description><p>This clause is derived from GSMA TS.34 <a href="#_ref_1">[1]</a> , clause 4. Two architectures are described in GSMA TS.34 <a href="#_ref_1">[1]</a> , where ...</p></description><link>https://specifications.onem2m.org/ts-0019/v0.0.2/5.3/</link> <pubDate>Thu, 25 Apr 2024 11:25:31 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v0.0.2/feed_rss_created.xml">oneM2M Specifications</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v0.0.2/5.3/</guid> </item> <item> <title>5.2 IoT Device Requirements</title> <description><p>**Table 5.2-1: GSMA defined requirements from GSMA TS 34 <a href="#_ref_1">[1]</a> **| Requirement ID | Description from GSMA TS 34 <a href="#_ref_1">[1]&lt;/a...</p></description><link>https://specifications.onem2m.org/ts-0019/v0.0.2/5.2/</link> <pubDate>Thu, 25 Apr 2024 11:25:31 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v0.0.2/feed_rss_created.xml">oneM2M Specifications</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v0.0.2/5.2/</guid> </item> </channel></rss>
\ No newline at end of file
+<?xml version="1.0" encoding="UTF-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/"> <channel><title>oneM2M Specifications</title><description>oneM2M Specifications navigator</description><link>https://specifications.onem2m.org/ts-0019/v0.0.2/</link><atom:link href="https://specifications.onem2m.org/ts-0019/v0.0.2/feed_rss_created.xml" rel="self" type="application/rss+xml" /><language>en</language> <pubDate>Thu, 25 Apr 2024 11:52:10 -0000</pubDate> <lastBuildDate>Thu, 25 Apr 2024 11:52:10 -0000</lastBuildDate> <ttl>1440</ttl> <generator>MkDocs RSS plugin - v1.12.1</generator> <item> <title>Download</title> <description><p>Download baseline for TR-0063 version v0.0.2:</p><p><a href="TR-0063-oneM2M-Effective_IoT_Communication_to_Protect_3GPP_Networks_v0.0.2.docx"><img alt="Word" src="images/Word.png"></a>[![...</p></description><link>https://specifications.onem2m.org/ts-0019/v0.0.2/download/</link> <pubDate>Thu, 25 Apr 2024 11:52:11 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v0.0.2/feed_rss_created.xml">oneM2M Specifications</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v0.0.2/download/</guid> </item> <item> <title>Annex &lt;y>:Bibliography</title> <description><p><mark>The annex entitled "Bibliography" is optional.</mark></p><p><mark>It shall contain a list of standards, books, articles, or other sources on a particular su...</p></description><link>https://specifications.onem2m.org/ts-0019/v0.0.2/y/</link> <pubDate>Thu, 25 Apr 2024 11:52:11 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v0.0.2/feed_rss_created.xml">oneM2M Specifications</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v0.0.2/y/</guid> </item> <item> <title>Annexes</title> <description><p><mark>Each annex shall start on a new page (insert a page break between annexes A and B, annexes B and C, etc.).<mark></p></description><link>https://specifications.onem2m.org/ts-0019/v0.0.2/m01K3C/</link> <pubDate>Thu, 25 Apr 2024 11:52:11 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v0.0.2/feed_rss_created.xml">oneM2M Specifications</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v0.0.2/m01K3C/</guid> </item> <item> <title> First clause of the annex</title> <description><p>&lt;Text&gt;</p><h3>B.1.1 First subdivided clause of the annex</h3><p>&lt;Text&gt;</p><p><mark>&lt;PAGE BREAK&gt;</mark></p></description><link>https://specifications.onem2m.org/ts-0019/v0.0.2/K763Qg/</link> <pubDate>Thu, 25 Apr 2024 11:52:11 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v0.0.2/feed_rss_created.xml">oneM2M Specifications</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v0.0.2/K763Qg/</guid> </item> <item> <title>Introduction</title> <description><p>&lt;Text&gt;</p></description><link>https://specifications.onem2m.org/ts-0019/v0.0.2/B/</link> <pubDate>Thu, 25 Apr 2024 11:52:11 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v0.0.2/feed_rss_created.xml">oneM2M Specifications</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v0.0.2/B/</guid> </item> <item> <title>Annex &lt;A>:Title of annex</title> <description><p>&lt;Text&gt;</p><p><mark>&lt;PAGE BREAK&gt;</mark></p></description><link>https://specifications.onem2m.org/ts-0019/v0.0.2/A/</link> <pubDate>Thu, 25 Apr 2024 11:52:11 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v0.0.2/feed_rss_created.xml">oneM2M Specifications</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v0.0.2/A/</guid> </item> <item> <title>9</title> <description></description><link>https://specifications.onem2m.org/ts-0019/v0.0.2/9/</link> <pubDate>Thu, 25 Apr 2024 11:52:11 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v0.0.2/feed_rss_created.xml">oneM2M Specifications</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v0.0.2/9/</guid> </item> <item> <title>9.1 Introduction</title> <description><p>Editor’s Note: This clause describes the coverage of GSMA TS.34 requirements. Identifies possible feedback to GSMA for further work on this topic.</p></description><link>https://specifications.onem2m.org/ts-0019/v0.0.2/9.1/</link> <pubDate>Thu, 25 Apr 2024 11:52:11 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v0.0.2/feed_rss_created.xml">oneM2M Specifications</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v0.0.2/9.1/</guid> </item> <item> <title>8</title> <description></description><link>https://specifications.onem2m.org/ts-0019/v0.0.2/8/</link> <pubDate>Thu, 25 Apr 2024 11:52:11 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v0.0.2/feed_rss_created.xml">oneM2M Specifications</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v0.0.2/8/</guid> </item> <item> <title>8.2 Enhancement 1 Description</title> <description><p>Editor’s Note: This clause describes a specific change</p></description><link>https://specifications.onem2m.org/ts-0019/v0.0.2/8.2/</link> <pubDate>Thu, 25 Apr 2024 11:52:11 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v0.0.2/feed_rss_created.xml">oneM2M Specifications</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v0.0.2/8.2/</guid> </item> <item> <title>8.1 Introduction</title> <description><p>Editor’s Note: This clause proposes enhancements to existing specifications if any that are identified in Clause 6</p></description><link>https://specifications.onem2m.org/ts-0019/v0.0.2/8.1/</link> <pubDate>Thu, 25 Apr 2024 11:52:11 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v0.0.2/feed_rss_created.xml">oneM2M Specifications</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v0.0.2/8.1/</guid> </item> <item> <title>7</title> <description></description><link>https://specifications.onem2m.org/ts-0019/v0.0.2/7/</link> <pubDate>Thu, 25 Apr 2024 11:52:11 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v0.0.2/feed_rss_created.xml">oneM2M Specifications</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v0.0.2/7/</guid> </item> <item> <title>7.2 Scenario 1</title> <description></description><link>https://specifications.onem2m.org/ts-0019/v0.0.2/7.2/</link> <pubDate>Thu, 25 Apr 2024 11:52:11 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v0.0.2/feed_rss_created.xml">oneM2M Specifications</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v0.0.2/7.2/</guid> </item> <item> <title>7.1 Introduction</title> <description><p>Editor’s Note: This clause proposes examples that are used to describe solutions in clause 6</p></description><link>https://specifications.onem2m.org/ts-0019/v0.0.2/7.1/</link> <pubDate>Thu, 25 Apr 2024 11:52:11 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v0.0.2/feed_rss_created.xml">oneM2M Specifications</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v0.0.2/7.1/</guid> </item> <item> <title>6</title> <description></description><link>https://specifications.onem2m.org/ts-0019/v0.0.2/6/</link> <pubDate>Thu, 25 Apr 2024 11:52:10 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v0.0.2/feed_rss_created.xml">oneM2M Specifications</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v0.0.2/6/</guid> </item> <item> <title>6.1 Use Case / Solution 1</title> <description><p>Editor’s Note: To define call flows that implement the requirements described in clause 5.</p></description><link>https://specifications.onem2m.org/ts-0019/v0.0.2/6.1/</link> <pubDate>Thu, 25 Apr 2024 11:52:10 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v0.0.2/feed_rss_created.xml">oneM2M Specifications</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v0.0.2/6.1/</guid> </item> <item> <title>Introduction</title> <description><p>&lt;Text&gt;</p></description><link>https://specifications.onem2m.org/ts-0019/v0.0.2/5/</link> <pubDate>Thu, 25 Apr 2024 11:52:10 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v0.0.2/feed_rss_created.xml">oneM2M Specifications</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v0.0.2/5/</guid> </item> <item> <title>5.4 Tiered IoT Device Application Requirements</title> <description><p>In the GSMA evolved architecture the Tiered IoT Device Application performs the business logic of the IoT solution. The GSMA requirements for such an applica...</p></description><link>https://specifications.onem2m.org/ts-0019/v0.0.2/5.4/</link> <pubDate>Thu, 25 Apr 2024 11:52:10 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v0.0.2/feed_rss_created.xml">oneM2M Specifications</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v0.0.2/5.4/</guid> </item> <item> <title>5.3 IOT Device Application Requirements</title> <description><p>This clause is derived from GSMA TS.34 <a href="#_ref_1">[1]</a> , clause 4. Two architectures are described in GSMA TS.34 <a href="#_ref_1">[1]</a> , where ...</p></description><link>https://specifications.onem2m.org/ts-0019/v0.0.2/5.3/</link> <pubDate>Thu, 25 Apr 2024 11:52:10 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v0.0.2/feed_rss_created.xml">oneM2M Specifications</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v0.0.2/5.3/</guid> </item> <item> <title>5.2 IoT Device Requirements</title> <description><p><strong>Table 5.2-1: GSMA defined requirements from GSMA TS 34 <a href="#_ref_1">[1]</a></strong></p><p>| Requirement ID | Description from GSMA TS 34 <a href="#_ref_1">[1]&lt;/a...</p></description><link>https://specifications.onem2m.org/ts-0019/v0.0.2/5.2/</link> <pubDate>Thu, 25 Apr 2024 11:52:10 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v0.0.2/feed_rss_created.xml">oneM2M Specifications</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v0.0.2/5.2/</guid> </item> </channel></rss>
\ No newline at end of file
diff --git a/public/v0.0.2/feed_rss_updated.xml b/public/v0.0.2/feed_rss_updated.xml
index 6ab08806f9268eea2d92de58d741a3cfaead3883..e562ac66eb701f423b7e790b272b38b73d70ba69 100644
--- a/public/v0.0.2/feed_rss_updated.xml
+++ b/public/v0.0.2/feed_rss_updated.xml
@@ -1 +1 @@
-<?xml version="1.0" encoding="UTF-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/"> <channel><title>oneM2M Specifications</title><description>oneM2M Specifications navigator</description><link>https://specifications.onem2m.org/ts-0019/v0.0.2/</link><atom:link href="https://specifications.onem2m.org/ts-0019/v0.0.2/feed_rss_updated.xml" rel="self" type="application/rss+xml" /><language>en</language> <pubDate>Thu, 25 Apr 2024 11:25:31 -0000</pubDate> <lastBuildDate>Thu, 25 Apr 2024 11:25:31 -0000</lastBuildDate> <ttl>1440</ttl> <generator>MkDocs RSS plugin - v1.12.1</generator> <item> <title>Download</title> <description><p>Download baseline for TR-0063 version v0.0.2:</p><p><a href="TR-0063-oneM2M-Effective_IoT_Communication_to_Protect_3GPP_Networks_v0.0.2.docx"><img alt="Word" src="images/Word.png"></a>[![...</p></description><link>https://specifications.onem2m.org/ts-0019/v0.0.2/download/</link> <pubDate>Thu, 25 Apr 2024 11:25:32 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v0.0.2/feed_rss_updated.xml">oneM2M Specifications</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v0.0.2/download/</guid> </item> <item> <title>Annex &lt;y>:Bibliography</title> <description><p><mark>The annex entitled "Bibliography" is optional.</mark></p><p><mark>It shall contain a list of standards, books, articles, or other sources on a particular su...</p></description><link>https://specifications.onem2m.org/ts-0019/v0.0.2/y/</link> <pubDate>Thu, 25 Apr 2024 11:25:31 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v0.0.2/feed_rss_updated.xml">oneM2M Specifications</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v0.0.2/y/</guid> </item> <item> <title>Annexes</title> <description><p><mark>Each annex shall start on a new page (insert a page break between annexes A and B, annexes B and C, etc.).<mark></p></description><link>https://specifications.onem2m.org/ts-0019/v0.0.2/m01K3C/</link> <pubDate>Thu, 25 Apr 2024 11:25:31 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v0.0.2/feed_rss_updated.xml">oneM2M Specifications</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v0.0.2/m01K3C/</guid> </item> <item> <title> First clause of the annex</title> <description><p>&lt;Text&gt;</p><h3>B.1.1 First subdivided clause of the annex</h3><p>&lt;Text&gt;</p><p><mark>&lt;PAGE BREAK&gt;</mark></p></description><link>https://specifications.onem2m.org/ts-0019/v0.0.2/K763Qg/</link> <pubDate>Thu, 25 Apr 2024 11:25:31 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v0.0.2/feed_rss_updated.xml">oneM2M Specifications</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v0.0.2/K763Qg/</guid> </item> <item> <title>Introduction</title> <description><p>&lt;Text&gt;</p></description><link>https://specifications.onem2m.org/ts-0019/v0.0.2/B/</link> <pubDate>Thu, 25 Apr 2024 11:25:31 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v0.0.2/feed_rss_updated.xml">oneM2M Specifications</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v0.0.2/B/</guid> </item> <item> <title>Annex &lt;A>:Title of annex</title> <description><p>&lt;Text&gt;</p><p><mark>&lt;PAGE BREAK&gt;</mark></p></description><link>https://specifications.onem2m.org/ts-0019/v0.0.2/A/</link> <pubDate>Thu, 25 Apr 2024 11:25:31 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v0.0.2/feed_rss_updated.xml">oneM2M Specifications</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v0.0.2/A/</guid> </item> <item> <title>9</title> <description></description><link>https://specifications.onem2m.org/ts-0019/v0.0.2/9/</link> <pubDate>Thu, 25 Apr 2024 11:25:31 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v0.0.2/feed_rss_updated.xml">oneM2M Specifications</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v0.0.2/9/</guid> </item> <item> <title>9.1 Introduction</title> <description><p>Editor’s Note: This clause describes the coverage of GSMA TS.34 requirements. Identifies possible feedback to GSMA for further work on this topic.</p></description><link>https://specifications.onem2m.org/ts-0019/v0.0.2/9.1/</link> <pubDate>Thu, 25 Apr 2024 11:25:31 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v0.0.2/feed_rss_updated.xml">oneM2M Specifications</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v0.0.2/9.1/</guid> </item> <item> <title>8</title> <description></description><link>https://specifications.onem2m.org/ts-0019/v0.0.2/8/</link> <pubDate>Thu, 25 Apr 2024 11:25:31 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v0.0.2/feed_rss_updated.xml">oneM2M Specifications</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v0.0.2/8/</guid> </item> <item> <title>8.2 Enhancement 1 Description</title> <description><p>Editor’s Note: This clause describes a specific change</p></description><link>https://specifications.onem2m.org/ts-0019/v0.0.2/8.2/</link> <pubDate>Thu, 25 Apr 2024 11:25:31 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v0.0.2/feed_rss_updated.xml">oneM2M Specifications</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v0.0.2/8.2/</guid> </item> <item> <title>8.1 Introduction</title> <description><p>Editor’s Note: This clause proposes enhancements to existing specifications if any that are identified in Clause 6</p></description><link>https://specifications.onem2m.org/ts-0019/v0.0.2/8.1/</link> <pubDate>Thu, 25 Apr 2024 11:25:31 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v0.0.2/feed_rss_updated.xml">oneM2M Specifications</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v0.0.2/8.1/</guid> </item> <item> <title>7</title> <description></description><link>https://specifications.onem2m.org/ts-0019/v0.0.2/7/</link> <pubDate>Thu, 25 Apr 2024 11:25:31 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v0.0.2/feed_rss_updated.xml">oneM2M Specifications</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v0.0.2/7/</guid> </item> <item> <title>7.2 Scenario 1</title> <description></description><link>https://specifications.onem2m.org/ts-0019/v0.0.2/7.2/</link> <pubDate>Thu, 25 Apr 2024 11:25:31 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v0.0.2/feed_rss_updated.xml">oneM2M Specifications</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v0.0.2/7.2/</guid> </item> <item> <title>7.1 Introduction</title> <description><p>Editor’s Note: This clause proposes examples that are used to describe solutions in clause 6</p></description><link>https://specifications.onem2m.org/ts-0019/v0.0.2/7.1/</link> <pubDate>Thu, 25 Apr 2024 11:25:31 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v0.0.2/feed_rss_updated.xml">oneM2M Specifications</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v0.0.2/7.1/</guid> </item> <item> <title>6</title> <description></description><link>https://specifications.onem2m.org/ts-0019/v0.0.2/6/</link> <pubDate>Thu, 25 Apr 2024 11:25:31 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v0.0.2/feed_rss_updated.xml">oneM2M Specifications</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v0.0.2/6/</guid> </item> <item> <title>6.1 Use Case / Solution 1</title> <description><p>Editor’s Note: To define call flows that implement the requirements described in clause 5.</p></description><link>https://specifications.onem2m.org/ts-0019/v0.0.2/6.1/</link> <pubDate>Thu, 25 Apr 2024 11:25:31 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v0.0.2/feed_rss_updated.xml">oneM2M Specifications</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v0.0.2/6.1/</guid> </item> <item> <title>Introduction</title> <description><p>&lt;Text&gt;</p></description><link>https://specifications.onem2m.org/ts-0019/v0.0.2/5/</link> <pubDate>Thu, 25 Apr 2024 11:25:31 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v0.0.2/feed_rss_updated.xml">oneM2M Specifications</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v0.0.2/5/</guid> </item> <item> <title>5.4 Tiered IoT Device Application Requirements</title> <description><p>In the GSMA evolved architecture the Tiered IoT Device Application performs the business logic of the IoT solution. The GSMA requirements for such an applica...</p></description><link>https://specifications.onem2m.org/ts-0019/v0.0.2/5.4/</link> <pubDate>Thu, 25 Apr 2024 11:25:31 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v0.0.2/feed_rss_updated.xml">oneM2M Specifications</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v0.0.2/5.4/</guid> </item> <item> <title>5.3 IOT Device Application Requirements</title> <description><p>This clause is derived from GSMA TS.34 <a href="#_ref_1">[1]</a> , clause 4. Two architectures are described in GSMA TS.34 <a href="#_ref_1">[1]</a> , where ...</p></description><link>https://specifications.onem2m.org/ts-0019/v0.0.2/5.3/</link> <pubDate>Thu, 25 Apr 2024 11:25:31 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v0.0.2/feed_rss_updated.xml">oneM2M Specifications</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v0.0.2/5.3/</guid> </item> <item> <title>5.2 IoT Device Requirements</title> <description><p>**Table 5.2-1: GSMA defined requirements from GSMA TS 34 <a href="#_ref_1">[1]</a> **| Requirement ID | Description from GSMA TS 34 <a href="#_ref_1">[1]&lt;/a...</p></description><link>https://specifications.onem2m.org/ts-0019/v0.0.2/5.2/</link> <pubDate>Thu, 25 Apr 2024 11:25:31 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v0.0.2/feed_rss_updated.xml">oneM2M Specifications</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v0.0.2/5.2/</guid> </item> </channel></rss>
\ No newline at end of file
+<?xml version="1.0" encoding="UTF-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/"> <channel><title>oneM2M Specifications</title><description>oneM2M Specifications navigator</description><link>https://specifications.onem2m.org/ts-0019/v0.0.2/</link><atom:link href="https://specifications.onem2m.org/ts-0019/v0.0.2/feed_rss_updated.xml" rel="self" type="application/rss+xml" /><language>en</language> <pubDate>Thu, 25 Apr 2024 11:52:10 -0000</pubDate> <lastBuildDate>Thu, 25 Apr 2024 11:52:10 -0000</lastBuildDate> <ttl>1440</ttl> <generator>MkDocs RSS plugin - v1.12.1</generator> <item> <title>Download</title> <description><p>Download baseline for TR-0063 version v0.0.2:</p><p><a href="TR-0063-oneM2M-Effective_IoT_Communication_to_Protect_3GPP_Networks_v0.0.2.docx"><img alt="Word" src="images/Word.png"></a>[![...</p></description><link>https://specifications.onem2m.org/ts-0019/v0.0.2/download/</link> <pubDate>Thu, 25 Apr 2024 11:52:11 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v0.0.2/feed_rss_updated.xml">oneM2M Specifications</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v0.0.2/download/</guid> </item> <item> <title>Annex &lt;y>:Bibliography</title> <description><p><mark>The annex entitled "Bibliography" is optional.</mark></p><p><mark>It shall contain a list of standards, books, articles, or other sources on a particular su...</p></description><link>https://specifications.onem2m.org/ts-0019/v0.0.2/y/</link> <pubDate>Thu, 25 Apr 2024 11:52:11 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v0.0.2/feed_rss_updated.xml">oneM2M Specifications</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v0.0.2/y/</guid> </item> <item> <title>Annexes</title> <description><p><mark>Each annex shall start on a new page (insert a page break between annexes A and B, annexes B and C, etc.).<mark></p></description><link>https://specifications.onem2m.org/ts-0019/v0.0.2/m01K3C/</link> <pubDate>Thu, 25 Apr 2024 11:52:11 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v0.0.2/feed_rss_updated.xml">oneM2M Specifications</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v0.0.2/m01K3C/</guid> </item> <item> <title> First clause of the annex</title> <description><p>&lt;Text&gt;</p><h3>B.1.1 First subdivided clause of the annex</h3><p>&lt;Text&gt;</p><p><mark>&lt;PAGE BREAK&gt;</mark></p></description><link>https://specifications.onem2m.org/ts-0019/v0.0.2/K763Qg/</link> <pubDate>Thu, 25 Apr 2024 11:52:11 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v0.0.2/feed_rss_updated.xml">oneM2M Specifications</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v0.0.2/K763Qg/</guid> </item> <item> <title>Introduction</title> <description><p>&lt;Text&gt;</p></description><link>https://specifications.onem2m.org/ts-0019/v0.0.2/B/</link> <pubDate>Thu, 25 Apr 2024 11:52:11 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v0.0.2/feed_rss_updated.xml">oneM2M Specifications</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v0.0.2/B/</guid> </item> <item> <title>Annex &lt;A>:Title of annex</title> <description><p>&lt;Text&gt;</p><p><mark>&lt;PAGE BREAK&gt;</mark></p></description><link>https://specifications.onem2m.org/ts-0019/v0.0.2/A/</link> <pubDate>Thu, 25 Apr 2024 11:52:11 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v0.0.2/feed_rss_updated.xml">oneM2M Specifications</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v0.0.2/A/</guid> </item> <item> <title>9</title> <description></description><link>https://specifications.onem2m.org/ts-0019/v0.0.2/9/</link> <pubDate>Thu, 25 Apr 2024 11:52:11 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v0.0.2/feed_rss_updated.xml">oneM2M Specifications</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v0.0.2/9/</guid> </item> <item> <title>9.1 Introduction</title> <description><p>Editor’s Note: This clause describes the coverage of GSMA TS.34 requirements. Identifies possible feedback to GSMA for further work on this topic.</p></description><link>https://specifications.onem2m.org/ts-0019/v0.0.2/9.1/</link> <pubDate>Thu, 25 Apr 2024 11:52:11 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v0.0.2/feed_rss_updated.xml">oneM2M Specifications</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v0.0.2/9.1/</guid> </item> <item> <title>8</title> <description></description><link>https://specifications.onem2m.org/ts-0019/v0.0.2/8/</link> <pubDate>Thu, 25 Apr 2024 11:52:11 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v0.0.2/feed_rss_updated.xml">oneM2M Specifications</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v0.0.2/8/</guid> </item> <item> <title>8.2 Enhancement 1 Description</title> <description><p>Editor’s Note: This clause describes a specific change</p></description><link>https://specifications.onem2m.org/ts-0019/v0.0.2/8.2/</link> <pubDate>Thu, 25 Apr 2024 11:52:11 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v0.0.2/feed_rss_updated.xml">oneM2M Specifications</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v0.0.2/8.2/</guid> </item> <item> <title>8.1 Introduction</title> <description><p>Editor’s Note: This clause proposes enhancements to existing specifications if any that are identified in Clause 6</p></description><link>https://specifications.onem2m.org/ts-0019/v0.0.2/8.1/</link> <pubDate>Thu, 25 Apr 2024 11:52:11 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v0.0.2/feed_rss_updated.xml">oneM2M Specifications</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v0.0.2/8.1/</guid> </item> <item> <title>7</title> <description></description><link>https://specifications.onem2m.org/ts-0019/v0.0.2/7/</link> <pubDate>Thu, 25 Apr 2024 11:52:11 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v0.0.2/feed_rss_updated.xml">oneM2M Specifications</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v0.0.2/7/</guid> </item> <item> <title>7.2 Scenario 1</title> <description></description><link>https://specifications.onem2m.org/ts-0019/v0.0.2/7.2/</link> <pubDate>Thu, 25 Apr 2024 11:52:11 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v0.0.2/feed_rss_updated.xml">oneM2M Specifications</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v0.0.2/7.2/</guid> </item> <item> <title>7.1 Introduction</title> <description><p>Editor’s Note: This clause proposes examples that are used to describe solutions in clause 6</p></description><link>https://specifications.onem2m.org/ts-0019/v0.0.2/7.1/</link> <pubDate>Thu, 25 Apr 2024 11:52:11 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v0.0.2/feed_rss_updated.xml">oneM2M Specifications</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v0.0.2/7.1/</guid> </item> <item> <title>6</title> <description></description><link>https://specifications.onem2m.org/ts-0019/v0.0.2/6/</link> <pubDate>Thu, 25 Apr 2024 11:52:10 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v0.0.2/feed_rss_updated.xml">oneM2M Specifications</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v0.0.2/6/</guid> </item> <item> <title>6.1 Use Case / Solution 1</title> <description><p>Editor’s Note: To define call flows that implement the requirements described in clause 5.</p></description><link>https://specifications.onem2m.org/ts-0019/v0.0.2/6.1/</link> <pubDate>Thu, 25 Apr 2024 11:52:10 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v0.0.2/feed_rss_updated.xml">oneM2M Specifications</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v0.0.2/6.1/</guid> </item> <item> <title>Introduction</title> <description><p>&lt;Text&gt;</p></description><link>https://specifications.onem2m.org/ts-0019/v0.0.2/5/</link> <pubDate>Thu, 25 Apr 2024 11:52:10 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v0.0.2/feed_rss_updated.xml">oneM2M Specifications</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v0.0.2/5/</guid> </item> <item> <title>5.4 Tiered IoT Device Application Requirements</title> <description><p>In the GSMA evolved architecture the Tiered IoT Device Application performs the business logic of the IoT solution. The GSMA requirements for such an applica...</p></description><link>https://specifications.onem2m.org/ts-0019/v0.0.2/5.4/</link> <pubDate>Thu, 25 Apr 2024 11:52:10 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v0.0.2/feed_rss_updated.xml">oneM2M Specifications</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v0.0.2/5.4/</guid> </item> <item> <title>5.3 IOT Device Application Requirements</title> <description><p>This clause is derived from GSMA TS.34 <a href="#_ref_1">[1]</a> , clause 4. Two architectures are described in GSMA TS.34 <a href="#_ref_1">[1]</a> , where ...</p></description><link>https://specifications.onem2m.org/ts-0019/v0.0.2/5.3/</link> <pubDate>Thu, 25 Apr 2024 11:52:10 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v0.0.2/feed_rss_updated.xml">oneM2M Specifications</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v0.0.2/5.3/</guid> </item> <item> <title>5.2 IoT Device Requirements</title> <description><p><strong>Table 5.2-1: GSMA defined requirements from GSMA TS 34 <a href="#_ref_1">[1]</a></strong></p><p>| Requirement ID | Description from GSMA TS 34 <a href="#_ref_1">[1]&lt;/a...</p></description><link>https://specifications.onem2m.org/ts-0019/v0.0.2/5.2/</link> <pubDate>Thu, 25 Apr 2024 11:52:10 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v0.0.2/feed_rss_updated.xml">oneM2M Specifications</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v0.0.2/5.2/</guid> </item> </channel></rss>
\ No newline at end of file
diff --git a/public/v0.0.2/search/search_index.json b/public/v0.0.2/search/search_index.json
index e7de89b2b70f92d6f290cf24a915458fcd418ed9..aa3d9f28e257e39207a5872d115fab4e38cb3817 100644
--- a/public/v0.0.2/search/search_index.json
+++ b/public/v0.0.2/search/search_index.json
@@ -1 +1 @@
-{"config":{"lang":["en"],"separator":"[\\s\\-]+","pipeline":["stopWordFilter"]},"docs":[{"location":"","title":"Home","text":"oneM2MTechnical Report oneM2MTechnical Report Document Number TR-0063-V-0.0.2 Document Name: Effective IoT Communication to Protect 3GPP Networks Date: <2024-04-24> Abstract: < An abstract of the document and information that may be used in subsequent electronic searches> Template Version: January 2020 (do not modify) <p>The present document is provided for future development work within oneM2M only. The Partners accept no liability for any use of this report.</p> <p>The present document has not been subject to any approval process by the oneM2M Partners Type 1. Published oneM2M specifications and reports for implementation should be obtained via the oneM2M Partners' Publications Offices.</p> <p>About oneM2M </p> <p>The purpose and goal of oneM2M is to develop technical specifications which address the need for a common M2M Service Layer that can be readily embedded within various hardware and software, and relied upon to connect the myriad of devices in the field with M2M application servers worldwide. </p> <p>More information about oneM2M may be found at: http//www.oneM2M.org</p> <p>Copyright Notification</p> <p>(c) 2020, oneM2M Partners Type 1 (ARIB, ATIS, CCSA, ETSI, TIA, TSDSI, TTA, TTC).</p> <p>All rights reserved.</p> <p>The copyright and the foregoing restriction extend to reproduction in all media.</p> <p>Notice of Disclaimer & Limitation of Liability </p> <p>The information provided in this document is directed solely to professionals who have the appropriate degree of experience to understand and interpret its contents in accordance with generally accepted engineering or other professional standards and applicable regulations. No recommendation as to products or vendors is made or should be implied. </p> <p>NO REPRESENTATION OR WARRANTY IS MADE THAT THE INFORMATION IS TECHNICALLY ACCURATE OR SUFFICIENT OR CONFORMS TO ANY STATUTE, GOVERNMENTAL RULE OR REGULATION, AND FURTHER, NO REPRESENTATION OR WARRANTY IS MADE OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR AGAINST INFRINGEMENT OF INTELLECTUAL PROPERTY RIGHTS. NO oneM2M PARTNER TYPE 1 SHALL BE LIABLE, BEYOND THE AMOUNT OF ANY SUM RECEIVED IN PAYMENT BY THAT PARTNER FOR THIS DOCUMENT, WITH RESPECT TO ANY CLAIM, AND IN NO EVENT SHALL oneM2M BE LIABLE FOR LOST PROFITS OR OTHER INCIDENTAL OR CONSEQUENTIAL DAMAGES. oneM2M EXPRESSLY ADVISES ANY AND ALL USE OF OR RELIANCE UPON THIS INFORMATION PROVIDED IN THIS DOCUMENT IS AT THE RISK OF THE USER.</p>"},{"location":"0/","title":"0","text":"oneM2MTechnical Report oneM2MTechnical Report Document Number TR-0063-V-0.0.2 Document Name: Effective IoT Communication to Protect 3GPP Networks Date: <2024-04-24> Abstract: < An abstract of the document and information that may be used in subsequent electronic searches> Template Version: January 2020 (do not modify) <p>The present document is provided for future development work within oneM2M only. The Partners accept no liability for any use of this report.</p> <p>The present document has not been subject to any approval process by the oneM2M Partners Type 1. Published oneM2M specifications and reports for implementation should be obtained via the oneM2M Partners' Publications Offices.</p> <p>About oneM2M </p> <p>The purpose and goal of oneM2M is to develop technical specifications which address the need for a common M2M Service Layer that can be readily embedded within various hardware and software, and relied upon to connect the myriad of devices in the field with M2M application servers worldwide. </p> <p>More information about oneM2M may be found at: http//www.oneM2M.org</p> <p>Copyright Notification</p> <p>(c) 2020, oneM2M Partners Type 1 (ARIB, ATIS, CCSA, ETSI, TIA, TSDSI, TTA, TTC).</p> <p>All rights reserved.</p> <p>The copyright and the foregoing restriction extend to reproduction in all media.</p> <p>Notice of Disclaimer & Limitation of Liability </p> <p>The information provided in this document is directed solely to professionals who have the appropriate degree of experience to understand and interpret its contents in accordance with generally accepted engineering or other professional standards and applicable regulations. No recommendation as to products or vendors is made or should be implied. </p> <p>NO REPRESENTATION OR WARRANTY IS MADE THAT THE INFORMATION IS TECHNICALLY ACCURATE OR SUFFICIENT OR CONFORMS TO ANY STATUTE, GOVERNMENTAL RULE OR REGULATION, AND FURTHER, NO REPRESENTATION OR WARRANTY IS MADE OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR AGAINST INFRINGEMENT OF INTELLECTUAL PROPERTY RIGHTS. NO oneM2M PARTNER TYPE 1 SHALL BE LIABLE, BEYOND THE AMOUNT OF ANY SUM RECEIVED IN PAYMENT BY THAT PARTNER FOR THIS DOCUMENT, WITH RESPECT TO ANY CLAIM, AND IN NO EVENT SHALL oneM2M BE LIABLE FOR LOST PROFITS OR OTHER INCIDENTAL OR CONSEQUENTIAL DAMAGES. oneM2M EXPRESSLY ADVISES ANY AND ALL USE OF OR RELIANCE UPON THIS INFORMATION PROVIDED IN THIS DOCUMENT IS AT THE RISK OF THE USER.</p>"},{"location":"1/","title":"1 Scope","text":"<p>Mass deployment of IoT devices, is causing an increased risk of signalling floods e.g. by concurrently transmitting IoT devices and hence causing a risk for the stability- and the efficient use of their mobile networks. One of the reasons is that IoT customers or integrators, often do not considering the specifics of mobile networks in their IoT device application design, subsequently causing inefficient communication or even loss of reachability. Operators are increasingly reporting problems from their live networks, like masses of concurrently resetting and reattaching devices within a small geographical region. Such events may cause their networks to collapse. GSMA has already flagged such events and has started to address the subject of badly behaving IoT devices / Applications. To avoid such scenarios upfront, GSMA released TS.34, \"IoT Device Connection Efficiency Guideline\" [1] . GSMA TS. 34 [1] gives guidance, which IoT device applications need to consider, to safely- and efficiently cooperate with cellular networks. However, the drawback of guidelines is the fact that the target audience: a.) needs to be aware of the existence of such guidelines and b.) needs to read, understand and follow such guidelines. This work aims to check and enhance oneM2M as an Embedded Service Layer in a way that the requirements formulated in GSMA TS.34 [1] are taken into account and Applications developed not considering requirements in GSMA TS.34 [1] , do not create adverse effects in the network, because the oneM2M as Embedded Service Layer is shielding the network from badly behaving applications. GSMA TS. 34 [1] is already referring towards an evolution of an IoT Service Architecture, where the IoT Device Applications are becoming disaggregated from an Embedded Service Layer. Such an Embedded Service Layer is providing several generic IoT functionalities (e.g. device management, security, location, application framework\u2026). The common service layer specified by oneM2M complies to this IoT Service Architecture.</p> <p></p> <p>Figure 1-1: Generalised \u201cLayered\u201d IoT Service Architecture, as depicted GSMA TS 34 Figure 3</p> <p>Applications being deployed on top of a common service layer are less critical to the network, because the common service layer takes over a protection role for the network. Inefficient or even harmful activities of applications would be prevented upfront and can\u2019t hit the network. On the other hand, oneM2M provides functionality for the applications, e.g. scheduling transmissions according to the service needs. The recommended evolved architecture in GSMA TS.34 [1] (refer Figure 1X) aligns well with the oneM2M architecture shown in Fig 1-1.</p> <p></p> <p>Figure 1 2: oneM2M architecture for CIoT devices</p> <p>oneM2M with the CSE functionality in between the IoT Application and the network connectivity, is well suited to enforce the requirements being addressed in GSMA TS.34 [1] , and hence protect the network from unwanted signalling floods and enforces an efficient communication, even if the Application (AE) has been created without GSMA TS.34 [1] knowledge or compliance. This TR is analysing which functionalities recommended by GSMA TS.34 [1] being in scope of an Embedded Service Layer are already covered by oneM2M functionality (e.g. like in CDMH), and which GSMA TS.34 [1] functionality is missing from oneM2M, to identify it and enhance oneM2M accordingly to meet the GSMA TS.34 [1] recommendations.</p>"},{"location":"2.1/","title":"2.1 Normative references","text":"<p>As a Technical Report (TR) is entirely informative it shall not list normative references.</p> <p>The following referenced documents are necessary for the application of the present document.</p> <p>Not applicable.</p>"},{"location":"2.2/","title":"2.2 Informative references","text":"<p>Clause 2.2 shall only contain informative references which are cited in the document itself.</p> <p>The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area.</p> <ul> <li>[1] GSM Association Official Document TS.34 \"IoT Device Connection Efficiency Guidelines\"</li> <li>[i.2] oneM2M Drafting Rules https://member.onem2m.org/static_Pages/others/Rules_Pages/oneM2M-Drafting-Rules-V1%202%202.doc</li> <li>[i.3] oneM2M TS-0001: \"Functional Architecture\"</li> <li>[i.4] oneM2M TS-0018: \"Test Suite Structure & Test Purposes\"</li> <li>[i.5] oneM2M TS-0025: \"Definition of Product Profiles\"</li> <li>[i.6] oneM2M TS-0026: \"3GPP Interworking\"</li> </ul>"},{"location":"2/","title":"Introduction","text":"<p>The following text block applies.</p> <p>References are either specific (identified by date of publication and/or edition number or version number) or nonspecific. For specific references,only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies.</p>"},{"location":"25wIfS/","title":"Introduction","text":"<p>This text box shall immediately follow after the heading of an element (i.e. clause or annex) containing a proforma or template which is intended to be copied by the user. Such an element shall always start on a new page.</p> <p>Notwithstanding the provisions of the copyright clause related to the text of the present document, oneM2M grants that users of the present document may freely reproduce the <proformatype> proforma in this {clause|annex} so that it can be used for its intended purposes and may further publish the completed <proformatype>.</p> <p><PAGE BREAK></p>"},{"location":"3.1/","title":"3.1 Terms","text":"<p>IoT Device : The combination of both the IoT Device Application and the Communications Module.</p> <p>Well-known location: a target URI in the oneM2M CSE resource tree that is a place where you should store information that is expected to be at the same location on every oneM2M CSE. </p>"},{"location":"3.2/","title":"3.2 Symbols","text":"<p>Clause numbering depends on applicability.</p> <p>For the purposes of the present document, the [following] symbols [given in ... and the following] apply:</p> <p>Symbol format</p> <p><code>&lt;symbol> &lt;Explanation></code> <code>&lt;2nd symbol> &lt;2nd Explanation></code> <code>&lt;3rd symbol> &lt;3rd Explanation></code> </p>"},{"location":"3.3/","title":"3.3 Abbreviations","text":"<p>Abbreviations should be ordered alphabetically.</p> <p>Clause numbering depends on applicability.</p> <p>For the purposes of the present document, the [following] abbreviations [given in ... and the following] apply:</p> <p>Abbreviation format</p> <p><code>&lt;ABBREVIATION1> &lt;Explanation></code> <code>&lt;ABBREVIATION2> &lt;Explanation></code> <code>&lt;ABBREVIATION3> &lt;Explanation></code> </p>"},{"location":"3/","title":"Introduction","text":"<p>Delete from the above heading the word(s) which is/are not applicable.</p>"},{"location":"4/","title":"4 Conventions","text":"<p>The key words \"Shall\", \"Shall not\", \"May\", \"Need not\", \"Should\", \"Should not\" in this document are to be interpreted as described in the oneM2M Drafting Rules [i.2]</p>"},{"location":"5.1/","title":"5.1 Introduction","text":"<p>GSMA TS.34 [1] represents a guideline and giving requirements for whole IoT Device, as defined in Figure X to ensure an efficient connection. </p> <p></p> <p>Figure 5.1-1: Generalised IoT Device Architecture according to GSMA TS.34[1]</p> <p>Requirements with regards to an efficient communication are grouped and categorized in TS.34 [1] . E.g. requirements are formulated for the following areas:</p> <ul> <li>IoT Device Application Requirements</li> <li>Communication Module Requirements</li> <li>IoT Service Provider Requirements</li> <li>Policy-based Connection Efficiency Requirements</li> <li>Radio Policy Manager Requirements </li> <li>3GPP Connection Efficiency Features</li> </ul> <p>oneM2M is most beneficially able to support an efficient communication in the area of the IoT Device Application, while other areas, like required support of \"3GPP Connection Efficiency Features\" can be considered out of scope of oneM2M, and hence out of scope of this WI. With regards to \"IoT Device Application Requirements\", GSMA TS.34 [1] differentiates further between: 1. Monolithic IoT Device Application Requirements: Those requirements are applicable for devices without an embedded Service layer and hence are out of scope oneM2M anyway.</p> <ol> <li>Tiered IoT Device Applications Requirements: Those requirements are applicable for applications providing the required functionality according to GSMA TS.34 [1] , cooperatively together with the embedded Service layer. . </li> <li>IoT Embedded Service Layer Requirements: Those requirements are applicable for the embedded Service layer, providing the required functionality according to GSMA TS.34 [i.1]</li> </ol> <p>While the main focus of this work is primarily on 2) and 3) further requirements in GSMA TS.34 [1] have been screened, analysed and used to inspire functionality to be taken for oneM2M to ensure an efficient IoT communication.</p> <p>The considered Requirements out of GSMA TS.34 [1] in the context of oneM2M are listed in the subsequent sections, with the respective numbering schema kept as used in TS.34 [1] , for your reference.</p>"},{"location":"5.2/","title":"5.2 IoT Device Requirements","text":"<p>**Table 5.2-1: GSMA defined requirements from GSMA TS 34 [1] ** | Requirement ID | Description from GSMA TS 34 [1] | Reference clause | | ------ | ------ | ------ | |TS.34_3.0_REQ_001|The IoT Device SHOULD conform to all IoT Device Application requirements defined in TS.34, section 4.| 5.4 | |TS.34_3.0_REQ_002|The IoT Device SHALL conform to all Communication Module requirements defined in TS.34, section 5.| Not within the scope of oneM2M| |TS.34_3.0_REQ_003|The IoT Device SHOULD conform to GSMA TS.24 \"Operator Minimum Acceptance Values for Device Antenna Performance\" [x].|Not within the scope of oneM2M | |TS.34_3.0_REQ_004|When required by the Mobile Network Operator, the IoT Device SHALL be certified by the GCF and/or the PTCRB.|Recommended by oneM2M. Conformance test cases are defined in TS-0018 [i.4]. Profiles are defined in TS-0025 [i.5]|</p>"},{"location":"5.3/","title":"5.3 IOT Device Application Requirements","text":"<p>This clause is derived from GSMA TS.34 [1] , clause 4. Two architectures are described in GSMA TS.34 [1] , where the IoT Device application can be a monolithic application that meets all the requirements in clause 4.0 or an evolved architecture that separates the device application requirements into clause 4.1 and the IoT embedded service layer requirements into clause 4.2. This technical report addresses the evolved architecture. The remainder of this section is organized by the components shown in figure 5.3-1. </p> <p></p> <p>Figure 5.3-1: Requirements for CIoT solutions</p>"},{"location":"5.4/","title":"5.4 Tiered IoT Device Application Requirements","text":"<p>In the GSMA evolved architecture the Tiered IoT Device Application performs the business logic of the IoT solution. The GSMA requirements for such an application are captured in table 5.4-1.</p> <p>Table 5.4 1: Tiered IoT Device Requirements | Requirement ID | Description from GSMA TS 34 [1] | Reference clause | | ------ | ------ | ------ | |TS.34_4.1_REQ_001|If data speed and latency is critical to the IoT Service the IoT Device Application should be able to retrieve mobile network speed and connection quality information from the IoT Embedded Service Layer in order to request the appropriate quality of content from the IoT Service Platform.|See clause 6.1 | |TS.34_4.1_REQ_002|The IoT Device Application should always be prepared to handle situations when communication requests fail, when such failure is reported by the IoT Embedded Service Layer.|See clause 6.2 | |TS.34_4.1_REQ_003|Each time there is a need to send data over the mobile network the IoT Device Application should classify the priority of each communication. For example, the IoT Device Application should distinguish between data that requires instantaneous transmission and delay tolerant data that could be aggregated and/or sent during non-peak hours. Such information about the priority of the communication should be communicated to the IoT Embedded Service Layer.|See below [UPDATE THIS]| |TS.34_4.1_REQ_004|When an IoT Device Application does not need to perform regular data transmissions and it can tolerate some latency for its IoT Service, it should communicate this information to the IoT Embedded Service Layer so that it can use this information in its interactions with the network.|See below [UPDATE THIS]|</p>"},{"location":"5/","title":"Introduction","text":"<p><Text></p>"},{"location":"6.1/","title":"6.1 Use Case / Solution 1","text":"<p>Editor\u2019s Note: To define call flows that implement the requirements described in clause 5.</p>"},{"location":"7.1/","title":"7.1 Introduction","text":"<p>Editor\u2019s Note: This clause proposes examples that are used to describe solutions in clause 6</p>"},{"location":"8.1/","title":"8.1 Introduction","text":"<p>Editor\u2019s Note: This clause proposes enhancements to existing specifications if any that are identified in Clause 6</p>"},{"location":"8.2/","title":"8.2\t Enhancement 1 Description","text":"<p>Editor\u2019s Note: This clause describes a specific change</p>"},{"location":"9.1/","title":"9.1\tIntroduction","text":"<p>Editor\u2019s Note: This clause describes the coverage of GSMA TS.34 requirements. Identifies possible feedback to GSMA for further work on this topic.</p>"},{"location":"A/","title":"Annex <A>:Title of annex","text":"<p><Text></p> <p><PAGE BREAK></p>"},{"location":"B/","title":"Introduction","text":"<p><Text></p>"},{"location":"K763Qg/","title":"First clause of the annex","text":"<p><Text></p>"},{"location":"K763Qg/#b11-first-subdivided-clause-of-the-annex","title":"B.1.1 First subdivided clause of the annex","text":"<p><Text></p> <p><PAGE BREAK></p>"},{"location":"m01K3C/","title":"Annexes","text":"<p>Each annex shall start on a new page (insert a page break between annexes A and B, annexes B and C, etc.)."},{"location":"y/","title":"Annex <y>:Bibliography","text":"<p>The annex entitled \"Bibliography\" is optional.</p> <p>It shall contain a list of standards, books, articles, or other sources on a particular subject which are not mentioned in the document itself.</p> <p>It shall not include references mentioned in the document.</p> <ul> <li><Publication>: \"<Title>\".</li> </ul> <p>OR</p> <p><Publication>: \"<Title>\".</p> <p><PAGE BREAK></p>"},{"location":"download/","title":"Download","text":"<p>Download baseline for TR-0063 version v0.0.2:</p> <p></p>"}]}
\ No newline at end of file
+{"config":{"lang":["en"],"separator":"[\\s\\-]+","pipeline":["stopWordFilter"]},"docs":[{"location":"","title":"Home","text":"oneM2MTechnical Report oneM2MTechnical Report Document Number TR-0063-V-0.0.2 Document Name: Effective IoT Communication to Protect 3GPP Networks Date: <2024-04-24> Abstract: < An abstract of the document and information that may be used in subsequent electronic searches> Template Version: January 2020 (do not modify) <p>The present document is provided for future development work within oneM2M only. The Partners accept no liability for any use of this report.</p> <p>The present document has not been subject to any approval process by the oneM2M Partners Type 1. Published oneM2M specifications and reports for implementation should be obtained via the oneM2M Partners' Publications Offices.</p> <p>About oneM2M </p> <p>The purpose and goal of oneM2M is to develop technical specifications which address the need for a common M2M Service Layer that can be readily embedded within various hardware and software, and relied upon to connect the myriad of devices in the field with M2M application servers worldwide. </p> <p>More information about oneM2M may be found at: http//www.oneM2M.org</p> <p>Copyright Notification</p> <p>(c) 2020, oneM2M Partners Type 1 (ARIB, ATIS, CCSA, ETSI, TIA, TSDSI, TTA, TTC).</p> <p>All rights reserved.</p> <p>The copyright and the foregoing restriction extend to reproduction in all media.</p> <p>Notice of Disclaimer & Limitation of Liability </p> <p>The information provided in this document is directed solely to professionals who have the appropriate degree of experience to understand and interpret its contents in accordance with generally accepted engineering or other professional standards and applicable regulations. No recommendation as to products or vendors is made or should be implied. </p> <p>NO REPRESENTATION OR WARRANTY IS MADE THAT THE INFORMATION IS TECHNICALLY ACCURATE OR SUFFICIENT OR CONFORMS TO ANY STATUTE, GOVERNMENTAL RULE OR REGULATION, AND FURTHER, NO REPRESENTATION OR WARRANTY IS MADE OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR AGAINST INFRINGEMENT OF INTELLECTUAL PROPERTY RIGHTS. NO oneM2M PARTNER TYPE 1 SHALL BE LIABLE, BEYOND THE AMOUNT OF ANY SUM RECEIVED IN PAYMENT BY THAT PARTNER FOR THIS DOCUMENT, WITH RESPECT TO ANY CLAIM, AND IN NO EVENT SHALL oneM2M BE LIABLE FOR LOST PROFITS OR OTHER INCIDENTAL OR CONSEQUENTIAL DAMAGES. oneM2M EXPRESSLY ADVISES ANY AND ALL USE OF OR RELIANCE UPON THIS INFORMATION PROVIDED IN THIS DOCUMENT IS AT THE RISK OF THE USER.</p>"},{"location":"0/","title":"0","text":"oneM2MTechnical Report oneM2MTechnical Report Document Number TR-0063-V-0.0.2 Document Name: Effective IoT Communication to Protect 3GPP Networks Date: <2024-04-24> Abstract: < An abstract of the document and information that may be used in subsequent electronic searches> Template Version: January 2020 (do not modify) <p>The present document is provided for future development work within oneM2M only. The Partners accept no liability for any use of this report.</p> <p>The present document has not been subject to any approval process by the oneM2M Partners Type 1. Published oneM2M specifications and reports for implementation should be obtained via the oneM2M Partners' Publications Offices.</p> <p>About oneM2M </p> <p>The purpose and goal of oneM2M is to develop technical specifications which address the need for a common M2M Service Layer that can be readily embedded within various hardware and software, and relied upon to connect the myriad of devices in the field with M2M application servers worldwide. </p> <p>More information about oneM2M may be found at: http//www.oneM2M.org</p> <p>Copyright Notification</p> <p>(c) 2020, oneM2M Partners Type 1 (ARIB, ATIS, CCSA, ETSI, TIA, TSDSI, TTA, TTC).</p> <p>All rights reserved.</p> <p>The copyright and the foregoing restriction extend to reproduction in all media.</p> <p>Notice of Disclaimer & Limitation of Liability </p> <p>The information provided in this document is directed solely to professionals who have the appropriate degree of experience to understand and interpret its contents in accordance with generally accepted engineering or other professional standards and applicable regulations. No recommendation as to products or vendors is made or should be implied. </p> <p>NO REPRESENTATION OR WARRANTY IS MADE THAT THE INFORMATION IS TECHNICALLY ACCURATE OR SUFFICIENT OR CONFORMS TO ANY STATUTE, GOVERNMENTAL RULE OR REGULATION, AND FURTHER, NO REPRESENTATION OR WARRANTY IS MADE OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR AGAINST INFRINGEMENT OF INTELLECTUAL PROPERTY RIGHTS. NO oneM2M PARTNER TYPE 1 SHALL BE LIABLE, BEYOND THE AMOUNT OF ANY SUM RECEIVED IN PAYMENT BY THAT PARTNER FOR THIS DOCUMENT, WITH RESPECT TO ANY CLAIM, AND IN NO EVENT SHALL oneM2M BE LIABLE FOR LOST PROFITS OR OTHER INCIDENTAL OR CONSEQUENTIAL DAMAGES. oneM2M EXPRESSLY ADVISES ANY AND ALL USE OF OR RELIANCE UPON THIS INFORMATION PROVIDED IN THIS DOCUMENT IS AT THE RISK OF THE USER.</p>"},{"location":"1/","title":"1 Scope","text":"<p>Mass deployment of IoT devices, is causing an increased risk of signalling floods e.g. by concurrently transmitting IoT devices and hence causing a risk for the stability- and the efficient use of their mobile networks. One of the reasons is that IoT customers or integrators, often do not considering the specifics of mobile networks in their IoT device application design, subsequently causing inefficient communication or even loss of reachability. Operators are increasingly reporting problems from their live networks, like masses of concurrently resetting and reattaching devices within a small geographical region. Such events may cause their networks to collapse. GSMA has already flagged such events and has started to address the subject of badly behaving IoT devices / Applications. To avoid such scenarios upfront, GSMA released TS.34, \"IoT Device Connection Efficiency Guideline\" [1] . GSMA TS. 34 [1] gives guidance, which IoT device applications need to consider, to safely- and efficiently cooperate with cellular networks. However, the drawback of guidelines is the fact that the target audience: a.) needs to be aware of the existence of such guidelines and b.) needs to read, understand and follow such guidelines. This work aims to check and enhance oneM2M as an Embedded Service Layer in a way that the requirements formulated in GSMA TS.34 [1] are taken into account and Applications developed not considering requirements in GSMA TS.34 [1] , do not create adverse effects in the network, because the oneM2M as Embedded Service Layer is shielding the network from badly behaving applications. GSMA TS. 34 [1] is already referring towards an evolution of an IoT Service Architecture, where the IoT Device Applications are becoming disaggregated from an Embedded Service Layer. Such an Embedded Service Layer is providing several generic IoT functionalities (e.g. device management, security, location, application framework\u2026). The common service layer specified by oneM2M complies to this IoT Service Architecture.</p> <p></p> <p>Figure 1-1: Generalised \u201cLayered\u201d IoT Service Architecture, as depicted GSMA TS 34 Figure 3</p> <p>Applications being deployed on top of a common service layer are less critical to the network, because the common service layer takes over a protection role for the network. Inefficient or even harmful activities of applications would be prevented upfront and can\u2019t hit the network. On the other hand, oneM2M provides functionality for the applications, e.g. scheduling transmissions according to the service needs. The recommended evolved architecture in GSMA TS.34 [1] (refer Figure 1X) aligns well with the oneM2M architecture shown in Fig 1-1.</p> <p></p> <p>Figure 1 2: oneM2M architecture for CIoT devices</p> <p>oneM2M with the CSE functionality in between the IoT Application and the network connectivity, is well suited to enforce the requirements being addressed in GSMA TS.34 [1] , and hence protect the network from unwanted signalling floods and enforces an efficient communication, even if the Application (AE) has been created without GSMA TS.34 [1] knowledge or compliance. This TR is analysing which functionalities recommended by GSMA TS.34 [1] being in scope of an Embedded Service Layer are already covered by oneM2M functionality (e.g. like in CDMH), and which GSMA TS.34 [1] functionality is missing from oneM2M, to identify it and enhance oneM2M accordingly to meet the GSMA TS.34 [1] recommendations.</p>"},{"location":"2.1/","title":"2.1 Normative references","text":"<p>As a Technical Report (TR) is entirely informative it shall not list normative references.</p> <p>The following referenced documents are necessary for the application of the present document.</p> <p>Not applicable.</p>"},{"location":"2.2/","title":"2.2 Informative references","text":"<p>Clause 2.2 shall only contain informative references which are cited in the document itself.</p> <p>The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area.</p> <ul> <li>[1] GSM Association Official Document TS.34 \"IoT Device Connection Efficiency Guidelines\"</li> <li>[i.2] oneM2M Drafting Rules https://member.onem2m.org/static_Pages/others/Rules_Pages/oneM2M-Drafting-Rules-V1%202%202.doc</li> <li>[i.3] oneM2M TS-0001: \"Functional Architecture\"</li> <li>[i.4] oneM2M TS-0018: \"Test Suite Structure & Test Purposes\"</li> <li>[i.5] oneM2M TS-0025: \"Definition of Product Profiles\"</li> <li>[i.6] oneM2M TS-0026: \"3GPP Interworking\"</li> </ul>"},{"location":"2/","title":"Introduction","text":"<p>The following text block applies.</p> <p>References are either specific (identified by date of publication and/or edition number or version number) or nonspecific. For specific references,only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies.</p>"},{"location":"25wIfS/","title":"Introduction","text":"<p>This text box shall immediately follow after the heading of an element (i.e. clause or annex) containing a proforma or template which is intended to be copied by the user. Such an element shall always start on a new page.</p> <p>Notwithstanding the provisions of the copyright clause related to the text of the present document, oneM2M grants that users of the present document may freely reproduce the <proformatype> proforma in this {clause|annex} so that it can be used for its intended purposes and may further publish the completed <proformatype>.</p> <p><PAGE BREAK></p>"},{"location":"3.1/","title":"3.1 Terms","text":"<p>IoT Device : The combination of both the IoT Device Application and the Communications Module.</p> <p>Well-known location: a target URI in the oneM2M CSE resource tree that is a place where you should store information that is expected to be at the same location on every oneM2M CSE. </p>"},{"location":"3.2/","title":"3.2 Symbols","text":"<p>Clause numbering depends on applicability.</p> <p>For the purposes of the present document, the [following] symbols [given in ... and the following] apply:</p> <p>Symbol format</p> <p><code>&lt;symbol> &lt;Explanation></code> <code>&lt;2nd symbol> &lt;2nd Explanation></code> <code>&lt;3rd symbol> &lt;3rd Explanation></code> </p>"},{"location":"3.3/","title":"3.3 Abbreviations","text":"<p>Abbreviations should be ordered alphabetically.</p> <p>Clause numbering depends on applicability.</p> <p>For the purposes of the present document, the [following] abbreviations [given in ... and the following] apply:</p> <p>Abbreviation format</p> <p><code>&lt;ABBREVIATION1> &lt;Explanation></code> <code>&lt;ABBREVIATION2> &lt;Explanation></code> <code>&lt;ABBREVIATION3> &lt;Explanation></code> </p>"},{"location":"3/","title":"Introduction","text":"<p>Delete from the above heading the word(s) which is/are not applicable.</p>"},{"location":"4/","title":"4 Conventions","text":"<p>The key words \"Shall\", \"Shall not\", \"May\", \"Need not\", \"Should\", \"Should not\" in this document are to be interpreted as described in the oneM2M Drafting Rules [i.2]</p>"},{"location":"5.1/","title":"5.1 Introduction","text":"<p>GSMA TS.34 [1] represents a guideline and giving requirements for whole IoT Device, as defined in Figure X to ensure an efficient connection. </p> <p></p> <p>Figure 5.1-1: Generalised IoT Device Architecture according to GSMA TS.34[1]</p> <p>Requirements with regards to an efficient communication are grouped and categorized in TS.34 [1] . E.g. requirements are formulated for the following areas:</p> <ul> <li>IoT Device Application Requirements</li> <li>Communication Module Requirements</li> <li>IoT Service Provider Requirements</li> <li>Policy-based Connection Efficiency Requirements</li> <li>Radio Policy Manager Requirements </li> <li>3GPP Connection Efficiency Features</li> </ul> <p>oneM2M is most beneficially able to support an efficient communication in the area of the IoT Device Application, while other areas, like required support of \"3GPP Connection Efficiency Features\" can be considered out of scope of oneM2M, and hence out of scope of this WI. With regards to \"IoT Device Application Requirements\", GSMA TS.34 [1] differentiates further between:</p> <ol> <li> <p>Monolithic IoT Device Application Requirements: Those requirements are applicable for devices without an embedded Service layer and hence are out of scope oneM2M anyway.</p> </li> <li> <p>Tiered IoT Device Applications Requirements: Those requirements are applicable for applications providing the required functionality according to GSMA TS.34 [1] , cooperatively together with the embedded Service layer.</p> </li> <li> <p>IoT Embedded Service Layer Requirements: Those requirements are applicable for the embedded Service layer, providing the required functionality according to GSMA TS.34 [i.1]</p> </li> </ol> <p>While the main focus of this work is primarily on 2) and 3) further requirements in GSMA TS.34 [1] have been screened, analysed and used to inspire functionality to be taken for oneM2M to ensure an efficient IoT communication.</p> <p>The considered Requirements out of GSMA TS.34 [1] in the context of oneM2M are listed in the subsequent sections, with the respective numbering schema kept as used in TS.34 [1] , for your reference.</p>"},{"location":"5.2/","title":"5.2 IoT Device Requirements","text":"<p>Table 5.2-1: GSMA defined requirements from GSMA TS 34 [1]</p> Requirement ID Description from GSMA TS 34 [1] Reference clause TS.34_3.0_REQ_001 The IoT Device SHOULD conform to all IoT Device Application requirements defined in TS.34, section 4. 5.4 TS.34_3.0_REQ_002 The IoT Device SHALL conform to all Communication Module requirements defined in TS.34, section 5. Not within the scope of oneM2M TS.34_3.0_REQ_003 The IoT Device SHOULD conform to GSMA TS.24 \"Operator Minimum Acceptance Values for Device Antenna Performance\" [x]. Not within the scope of oneM2M TS.34_3.0_REQ_004 When required by the Mobile Network Operator, the IoT Device SHALL be certified by the GCF and/or the PTCRB. Recommended by oneM2M. Conformance test cases are defined in TS-0018 [i.4]. Profiles are defined in TS-0025 [i.5]"},{"location":"5.3/","title":"5.3 IOT Device Application Requirements","text":"<p>This clause is derived from GSMA TS.34 [1] , clause 4. Two architectures are described in GSMA TS.34 [1] , where the IoT Device application can be a monolithic application that meets all the requirements in clause 4.0 or an evolved architecture that separates the device application requirements into clause 4.1 and the IoT embedded service layer requirements into clause 4.2. This technical report addresses the evolved architecture. The remainder of this section is organized by the components shown in figure 5.3-1. </p> <p></p> <p>Figure 5.3-1: Requirements for CIoT solutions</p>"},{"location":"5.4/","title":"5.4 Tiered IoT Device Application Requirements","text":"<p>In the GSMA evolved architecture the Tiered IoT Device Application performs the business logic of the IoT solution. The GSMA requirements for such an application are captured in table 5.4-1.</p> <p>Table 5.4 1: Tiered IoT Device Requirements</p> Requirement ID Description from GSMA TS 34 [1] Reference clause TS.34_4.1_REQ_001 If data speed and latency is critical to the IoT Service the IoT Device Application should be able to retrieve mobile network speed and connection quality information from the IoT Embedded Service Layer in order to request the appropriate quality of content from the IoT Service Platform. See clause 6.1 TS.34_4.1_REQ_002 The IoT Device Application should always be prepared to handle situations when communication requests fail, when such failure is reported by the IoT Embedded Service Layer. See clause 6.2 TS.34_4.1_REQ_003 Each time there is a need to send data over the mobile network the IoT Device Application should classify the priority of each communication. For example, the IoT Device Application should distinguish between data that requires instantaneous transmission and delay tolerant data that could be aggregated and/or sent during non-peak hours. Such information about the priority of the communication should be communicated to the IoT Embedded Service Layer. See below [UPDATE THIS] TS.34_4.1_REQ_004 When an IoT Device Application does not need to perform regular data transmissions and it can tolerate some latency for its IoT Service, it should communicate this information to the IoT Embedded Service Layer so that it can use this information in its interactions with the network. See below [UPDATE THIS]"},{"location":"5/","title":"Introduction","text":"<p><Text></p>"},{"location":"6.1/","title":"6.1 Use Case / Solution 1","text":"<p>Editor\u2019s Note: To define call flows that implement the requirements described in clause 5.</p>"},{"location":"7.1/","title":"7.1 Introduction","text":"<p>Editor\u2019s Note: This clause proposes examples that are used to describe solutions in clause 6</p>"},{"location":"8.1/","title":"8.1 Introduction","text":"<p>Editor\u2019s Note: This clause proposes enhancements to existing specifications if any that are identified in Clause 6</p>"},{"location":"8.2/","title":"8.2\t Enhancement 1 Description","text":"<p>Editor\u2019s Note: This clause describes a specific change</p>"},{"location":"9.1/","title":"9.1\tIntroduction","text":"<p>Editor\u2019s Note: This clause describes the coverage of GSMA TS.34 requirements. Identifies possible feedback to GSMA for further work on this topic.</p>"},{"location":"A/","title":"Annex <A>:Title of annex","text":"<p><Text></p> <p><PAGE BREAK></p>"},{"location":"B/","title":"Introduction","text":"<p><Text></p>"},{"location":"K763Qg/","title":"First clause of the annex","text":"<p><Text></p>"},{"location":"K763Qg/#b11-first-subdivided-clause-of-the-annex","title":"B.1.1 First subdivided clause of the annex","text":"<p><Text></p> <p><PAGE BREAK></p>"},{"location":"m01K3C/","title":"Annexes","text":"<p>Each annex shall start on a new page (insert a page break between annexes A and B, annexes B and C, etc.)."},{"location":"y/","title":"Annex <y>:Bibliography","text":"<p>The annex entitled \"Bibliography\" is optional.</p> <p>It shall contain a list of standards, books, articles, or other sources on a particular subject which are not mentioned in the document itself.</p> <p>It shall not include references mentioned in the document.</p> <ul> <li><Publication>: \"<Title>\".</li> </ul> <p>OR</p> <p><Publication>: \"<Title>\".</p> <p><PAGE BREAK></p>"},{"location":"download/","title":"Download","text":"<p>Download baseline for TR-0063 version v0.0.2:</p> <p></p>"}]}
\ No newline at end of file