diff --git a/public/latest b/public/latest
index 15a2b33b2448206077ddef5352a1d835f9677cb0..4b23c7e2c994ab29c78106e59da4b0b878c4619b 120000
--- a/public/latest
+++ b/public/latest
@@ -1 +1 @@
-v4.2.0
\ No newline at end of file
+v4.1.1
\ No newline at end of file
diff --git a/public/latestR4 b/public/latestR4
index 15a2b33b2448206077ddef5352a1d835f9677cb0..4b23c7e2c994ab29c78106e59da4b0b878c4619b 120000
--- a/public/latestR4
+++ b/public/latestR4
@@ -1 +1 @@
-v4.2.0
\ No newline at end of file
+v4.1.1
\ No newline at end of file
diff --git a/public/v4.1.1/0/index.html b/public/v4.1.1/0/index.html
index 580f862eefa5e3d38ea2aff1d4dfd7d820b8f228..86aa797171c3628e6290b11a520f04876d069ad9 100644
--- a/public/v4.1.1/0/index.html
+++ b/public/v4.1.1/0/index.html
@@ -10,7 +10,7 @@
- <link rel="canonical" href="https://specifications.onem2m.org/ts-0019/v4.1.1/0/">
+ <link rel="canonical" href="https://specifications.onem2m.org/v4.1.1/0/">
@@ -90,7 +90,7 @@
<header class="md-header md-header--shadow" data-md-component="header">
<nav class="md-header__inner md-grid" aria-label="Header">
- <a href=".." title="oneM2M TS-0019" class="md-header__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
+ <a href="https://specifications.onem2m.org" title="oneM2M TS-0019" class="md-header__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
<img src="../images/onem2m.png" alt="logo">
@@ -203,7 +203,7 @@
<nav class="md-nav md-nav--primary" aria-label="Navigation" data-md-level="0">
<label class="md-nav__title" for="__drawer">
- <a href=".." title="oneM2M TS-0019" class="md-nav__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
+ <a href="https://specifications.onem2m.org" title="oneM2M TS-0019" class="md-nav__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
<img src="../images/onem2m.png" alt="logo">
@@ -236,7 +236,7 @@
<span class="md-ellipsis">
-
+ Home
</span>
diff --git a/public/v4.1.1/1/index.html b/public/v4.1.1/1/index.html
index cea3136f9547c3667940a6bff645b88d3287bbe6..e72f02d44512e41232da1513ae32f544a8f07aa5 100644
--- a/public/v4.1.1/1/index.html
+++ b/public/v4.1.1/1/index.html
@@ -10,7 +10,7 @@
- <link rel="canonical" href="https://specifications.onem2m.org/ts-0019/v4.1.1/1/">
+ <link rel="canonical" href="https://specifications.onem2m.org/v4.1.1/1/">
<link rel="prev" href="..">
@@ -94,7 +94,7 @@
<header class="md-header md-header--shadow" data-md-component="header">
<nav class="md-header__inner md-grid" aria-label="Header">
- <a href=".." title="oneM2M TS-0019" class="md-header__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
+ <a href="https://specifications.onem2m.org" title="oneM2M TS-0019" class="md-header__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
<img src="../images/onem2m.png" alt="logo">
@@ -207,7 +207,7 @@
<nav class="md-nav md-nav--primary" aria-label="Navigation" data-md-level="0">
<label class="md-nav__title" for="__drawer">
- <a href=".." title="oneM2M TS-0019" class="md-nav__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
+ <a href="https://specifications.onem2m.org" title="oneM2M TS-0019" class="md-nav__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
<img src="../images/onem2m.png" alt="logo">
@@ -240,7 +240,7 @@
<span class="md-ellipsis">
-
+ Home
</span>
diff --git a/public/v4.1.1/2.1/index.html b/public/v4.1.1/2.1/index.html
index c5cb171ebd85d99f9d99aa95dc21c7856c129246..c6a1fd36a5f0cf478824b7d6a9a8019772a784ae 100644
--- a/public/v4.1.1/2.1/index.html
+++ b/public/v4.1.1/2.1/index.html
@@ -10,7 +10,7 @@
- <link rel="canonical" href="https://specifications.onem2m.org/ts-0019/v4.1.1/2.1/">
+ <link rel="canonical" href="https://specifications.onem2m.org/v4.1.1/2.1/">
<link rel="prev" href="../1/">
@@ -94,7 +94,7 @@
<header class="md-header md-header--shadow" data-md-component="header">
<nav class="md-header__inner md-grid" aria-label="Header">
- <a href=".." title="oneM2M TS-0019" class="md-header__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
+ <a href="https://specifications.onem2m.org" title="oneM2M TS-0019" class="md-header__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
<img src="../images/onem2m.png" alt="logo">
@@ -207,7 +207,7 @@
<nav class="md-nav md-nav--primary" aria-label="Navigation" data-md-level="0">
<label class="md-nav__title" for="__drawer">
- <a href=".." title="oneM2M TS-0019" class="md-nav__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
+ <a href="https://specifications.onem2m.org" title="oneM2M TS-0019" class="md-nav__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
<img src="../images/onem2m.png" alt="logo">
@@ -240,7 +240,7 @@
<span class="md-ellipsis">
-
+ Home
</span>
diff --git a/public/v4.1.1/2.2/index.html b/public/v4.1.1/2.2/index.html
index 942fbc7a8bf931b6dacb282d648c7ad9af12d3b8..56d5b8ba53df53aee3b8d4aee9cbd24f2e67a1d5 100644
--- a/public/v4.1.1/2.2/index.html
+++ b/public/v4.1.1/2.2/index.html
@@ -10,7 +10,7 @@
- <link rel="canonical" href="https://specifications.onem2m.org/ts-0019/v4.1.1/2.2/">
+ <link rel="canonical" href="https://specifications.onem2m.org/v4.1.1/2.2/">
<link rel="prev" href="../2.1/">
@@ -94,7 +94,7 @@
<header class="md-header md-header--shadow" data-md-component="header">
<nav class="md-header__inner md-grid" aria-label="Header">
- <a href=".." title="oneM2M TS-0019" class="md-header__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
+ <a href="https://specifications.onem2m.org" title="oneM2M TS-0019" class="md-header__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
<img src="../images/onem2m.png" alt="logo">
@@ -207,7 +207,7 @@
<nav class="md-nav md-nav--primary" aria-label="Navigation" data-md-level="0">
<label class="md-nav__title" for="__drawer">
- <a href=".." title="oneM2M TS-0019" class="md-nav__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
+ <a href="https://specifications.onem2m.org" title="oneM2M TS-0019" class="md-nav__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
<img src="../images/onem2m.png" alt="logo">
@@ -240,7 +240,7 @@
<span class="md-ellipsis">
-
+ Home
</span>
diff --git a/public/v4.1.1/2/index.html b/public/v4.1.1/2/index.html
index 77102fa89f51f0e17ea1164da20e835797d0b0e7..6cb98f877c4fb5ebabfabe475d7091ec23c1254b 100644
--- a/public/v4.1.1/2/index.html
+++ b/public/v4.1.1/2/index.html
@@ -10,7 +10,7 @@
- <link rel="canonical" href="https://specifications.onem2m.org/ts-0019/v4.1.1/2/">
+ <link rel="canonical" href="https://specifications.onem2m.org/v4.1.1/2/">
@@ -90,7 +90,7 @@
<header class="md-header md-header--shadow" data-md-component="header">
<nav class="md-header__inner md-grid" aria-label="Header">
- <a href=".." title="oneM2M TS-0019" class="md-header__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
+ <a href="https://specifications.onem2m.org" title="oneM2M TS-0019" class="md-header__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
<img src="../images/onem2m.png" alt="logo">
@@ -203,7 +203,7 @@
<nav class="md-nav md-nav--primary" aria-label="Navigation" data-md-level="0">
<label class="md-nav__title" for="__drawer">
- <a href=".." title="oneM2M TS-0019" class="md-nav__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
+ <a href="https://specifications.onem2m.org" title="oneM2M TS-0019" class="md-nav__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
<img src="../images/onem2m.png" alt="logo">
@@ -236,7 +236,7 @@
<span class="md-ellipsis">
-
+ Home
</span>
diff --git a/public/v4.1.1/3.1/index.html b/public/v4.1.1/3.1/index.html
index e7e6392478f0fcb05d8376c61207d7409148e037..6d7f5aae5e143234e5e080e4e59229aa31d9509e 100644
--- a/public/v4.1.1/3.1/index.html
+++ b/public/v4.1.1/3.1/index.html
@@ -10,7 +10,7 @@
- <link rel="canonical" href="https://specifications.onem2m.org/ts-0019/v4.1.1/3.1/">
+ <link rel="canonical" href="https://specifications.onem2m.org/v4.1.1/3.1/">
<link rel="prev" href="../2.2/">
@@ -94,7 +94,7 @@
<header class="md-header md-header--shadow" data-md-component="header">
<nav class="md-header__inner md-grid" aria-label="Header">
- <a href=".." title="oneM2M TS-0019" class="md-header__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
+ <a href="https://specifications.onem2m.org" title="oneM2M TS-0019" class="md-header__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
<img src="../images/onem2m.png" alt="logo">
@@ -207,7 +207,7 @@
<nav class="md-nav md-nav--primary" aria-label="Navigation" data-md-level="0">
<label class="md-nav__title" for="__drawer">
- <a href=".." title="oneM2M TS-0019" class="md-nav__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
+ <a href="https://specifications.onem2m.org" title="oneM2M TS-0019" class="md-nav__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
<img src="../images/onem2m.png" alt="logo">
@@ -240,7 +240,7 @@
<span class="md-ellipsis">
-
+ Home
</span>
diff --git a/public/v4.1.1/3.2/index.html b/public/v4.1.1/3.2/index.html
index 1da88a72947e84cc58a9ef9ab11b13e0d39b529c..5fb4d74f8a235a93caa37864e5425fbe33c59f9a 100644
--- a/public/v4.1.1/3.2/index.html
+++ b/public/v4.1.1/3.2/index.html
@@ -10,7 +10,7 @@
- <link rel="canonical" href="https://specifications.onem2m.org/ts-0019/v4.1.1/3.2/">
+ <link rel="canonical" href="https://specifications.onem2m.org/v4.1.1/3.2/">
<link rel="prev" href="./">
@@ -94,7 +94,7 @@
<header class="md-header md-header--shadow" data-md-component="header">
<nav class="md-header__inner md-grid" aria-label="Header">
- <a href=".." title="oneM2M TS-0019" class="md-header__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
+ <a href="https://specifications.onem2m.org" title="oneM2M TS-0019" class="md-header__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
<img src="../images/onem2m.png" alt="logo">
@@ -207,7 +207,7 @@
<nav class="md-nav md-nav--primary" aria-label="Navigation" data-md-level="0">
<label class="md-nav__title" for="__drawer">
- <a href=".." title="oneM2M TS-0019" class="md-nav__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
+ <a href="https://specifications.onem2m.org" title="oneM2M TS-0019" class="md-nav__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
<img src="../images/onem2m.png" alt="logo">
@@ -240,7 +240,7 @@
<span class="md-ellipsis">
-
+ Home
</span>
diff --git a/public/v4.1.1/3/index.html b/public/v4.1.1/3/index.html
index 790b56576c21113744180d112092c1db44371eff..667030bcc4f4e0f8a4c04afc72745870459235d6 100644
--- a/public/v4.1.1/3/index.html
+++ b/public/v4.1.1/3/index.html
@@ -10,7 +10,7 @@
- <link rel="canonical" href="https://specifications.onem2m.org/ts-0019/v4.1.1/3/">
+ <link rel="canonical" href="https://specifications.onem2m.org/v4.1.1/3/">
@@ -90,7 +90,7 @@
<header class="md-header md-header--shadow" data-md-component="header">
<nav class="md-header__inner md-grid" aria-label="Header">
- <a href=".." title="oneM2M TS-0019" class="md-header__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
+ <a href="https://specifications.onem2m.org" title="oneM2M TS-0019" class="md-header__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
<img src="../images/onem2m.png" alt="logo">
@@ -203,7 +203,7 @@
<nav class="md-nav md-nav--primary" aria-label="Navigation" data-md-level="0">
<label class="md-nav__title" for="__drawer">
- <a href=".." title="oneM2M TS-0019" class="md-nav__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
+ <a href="https://specifications.onem2m.org" title="oneM2M TS-0019" class="md-nav__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
<img src="../images/onem2m.png" alt="logo">
@@ -236,7 +236,7 @@
<span class="md-ellipsis">
-
+ Home
</span>
diff --git a/public/v4.1.1/4/index.html b/public/v4.1.1/4/index.html
index 324625feea7c27cfeb7b1ff3bacd9882d8ad2559..15f0f1f1668fd59f7f48470cde361e15b69538e6 100644
--- a/public/v4.1.1/4/index.html
+++ b/public/v4.1.1/4/index.html
@@ -10,7 +10,7 @@
- <link rel="canonical" href="https://specifications.onem2m.org/ts-0019/v4.1.1/4/">
+ <link rel="canonical" href="https://specifications.onem2m.org/v4.1.1/4/">
<link rel="prev" href="../3.2/">
@@ -94,7 +94,7 @@
<header class="md-header md-header--shadow" data-md-component="header">
<nav class="md-header__inner md-grid" aria-label="Header">
- <a href=".." title="oneM2M TS-0019" class="md-header__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
+ <a href="https://specifications.onem2m.org" title="oneM2M TS-0019" class="md-header__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
<img src="../images/onem2m.png" alt="logo">
@@ -207,7 +207,7 @@
<nav class="md-nav md-nav--primary" aria-label="Navigation" data-md-level="0">
<label class="md-nav__title" for="__drawer">
- <a href=".." title="oneM2M TS-0019" class="md-nav__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
+ <a href="https://specifications.onem2m.org" title="oneM2M TS-0019" class="md-nav__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
<img src="../images/onem2m.png" alt="logo">
@@ -240,7 +240,7 @@
<span class="md-ellipsis">
-
+ Home
</span>
diff --git a/public/v4.1.1/404.html b/public/v4.1.1/404.html
index 91796586527cea2c5b9c53b248f074f82743dbab..e6c06a0188cb39824bc35f29fa30cf206f60f78b 100644
--- a/public/v4.1.1/404.html
+++ b/public/v4.1.1/404.html
@@ -13,10 +13,10 @@
- <link rel="alternate" type="application/rss+xml" title="RSS feed" href="/ts-0019/v4.1.1/feed_rss_created.xml">
- <link rel="alternate" type="application/rss+xml" title="RSS feed of updated content" href="/ts-0019/v4.1.1/feed_rss_updated.xml">
+ <link rel="alternate" type="application/rss+xml" title="RSS feed" href="/v4.1.1/feed_rss_created.xml">
+ <link rel="alternate" type="application/rss+xml" title="RSS feed of updated content" href="/v4.1.1/feed_rss_updated.xml">
- <link rel="icon" href="/ts-0019/v4.1.1/images/favicon.ico">
+ <link rel="icon" href="/v4.1.1/images/favicon.ico">
<meta name="generator" content="mkdocs-1.6.1, mkdocs-material-9.5.44">
@@ -25,10 +25,10 @@
- <link rel="stylesheet" href="/ts-0019/v4.1.1/assets/stylesheets/main.0253249f.min.css">
+ <link rel="stylesheet" href="/v4.1.1/assets/stylesheets/main.0253249f.min.css">
- <link rel="stylesheet" href="/ts-0019/v4.1.1/assets/stylesheets/palette.06af60db.min.css">
+ <link rel="stylesheet" href="/v4.1.1/assets/stylesheets/palette.06af60db.min.css">
@@ -47,9 +47,9 @@
- <link rel="stylesheet" href="/ts-0019/v4.1.1/stylesheets/extra.css">
+ <link rel="stylesheet" href="/v4.1.1/stylesheets/extra.css">
- <script>__md_scope=new URL("/ts-0019/v4.1.1",location),__md_hash=e=>[...e].reduce(((e,_)=>(e<<5)-e+_.charCodeAt(0)),0),__md_get=(e,_=localStorage,t=__md_scope)=>JSON.parse(_.getItem(t.pathname+"."+e)),__md_set=(e,_,t=localStorage,a=__md_scope)=>{try{t.setItem(a.pathname+"."+e,JSON.stringify(_))}catch(e){}}</script>
+ <script>__md_scope=new URL("/v4.1.1",location),__md_hash=e=>[...e].reduce(((e,_)=>(e<<5)-e+_.charCodeAt(0)),0),__md_get=(e,_=localStorage,t=__md_scope)=>JSON.parse(_.getItem(t.pathname+"."+e)),__md_set=(e,_,t=localStorage,a=__md_scope)=>{try{t.setItem(a.pathname+"."+e,JSON.stringify(_))}catch(e){}}</script>
@@ -88,9 +88,9 @@
<header class="md-header md-header--shadow" data-md-component="header">
<nav class="md-header__inner md-grid" aria-label="Header">
- <a href="/ts-0019/v4.1.1/." title="oneM2M TS-0019" class="md-header__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
+ <a href="https://specifications.onem2m.org" title="oneM2M TS-0019" class="md-header__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
- <img src="/ts-0019/v4.1.1/images/onem2m.png" alt="logo">
+ <img src="/v4.1.1/images/onem2m.png" alt="logo">
</a>
<label class="md-header__button md-icon" for="__drawer">
@@ -201,9 +201,9 @@
<nav class="md-nav md-nav--primary" aria-label="Navigation" data-md-level="0">
<label class="md-nav__title" for="__drawer">
- <a href="/ts-0019/v4.1.1/." title="oneM2M TS-0019" class="md-nav__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
+ <a href="https://specifications.onem2m.org" title="oneM2M TS-0019" class="md-nav__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
- <img src="/ts-0019/v4.1.1/images/onem2m.png" alt="logo">
+ <img src="/v4.1.1/images/onem2m.png" alt="logo">
</a>
oneM2M TS-0019
@@ -230,11 +230,11 @@
<li class="md-nav__item">
- <a href="/ts-0019/v4.1.1/." class="md-nav__link">
+ <a href="/v4.1.1/." class="md-nav__link">
<span class="md-ellipsis">
-
+ Home
</span>
@@ -250,7 +250,7 @@
<li class="md-nav__item">
- <a href="/ts-0019/v4.1.1/1/" class="md-nav__link">
+ <a href="/v4.1.1/1/" class="md-nav__link">
<span class="md-ellipsis">
@@ -305,7 +305,7 @@
<li class="md-nav__item">
- <a href="/ts-0019/v4.1.1/2.1/" class="md-nav__link">
+ <a href="/v4.1.1/2.1/" class="md-nav__link">
<span class="md-ellipsis">
@@ -326,7 +326,7 @@
<li class="md-nav__item">
- <a href="/ts-0019/v4.1.1/2.2/" class="md-nav__link">
+ <a href="/v4.1.1/2.2/" class="md-nav__link">
<span class="md-ellipsis">
@@ -389,7 +389,7 @@
<li class="md-nav__item">
- <a href="/ts-0019/v4.1.1/3.1/" class="md-nav__link">
+ <a href="/v4.1.1/3.1/" class="md-nav__link">
<span class="md-ellipsis">
@@ -410,7 +410,7 @@
<li class="md-nav__item">
- <a href="/ts-0019/v4.1.1/3.2/" class="md-nav__link">
+ <a href="/v4.1.1/3.2/" class="md-nav__link">
<span class="md-ellipsis">
@@ -431,7 +431,7 @@
<li class="md-nav__item">
- <a href="/ts-0019/v4.1.1/3.2/" class="md-nav__link">
+ <a href="/v4.1.1/3.2/" class="md-nav__link">
<span class="md-ellipsis">
@@ -459,7 +459,7 @@
<li class="md-nav__item">
- <a href="/ts-0019/v4.1.1/4/" class="md-nav__link">
+ <a href="/v4.1.1/4/" class="md-nav__link">
<span class="md-ellipsis">
@@ -514,7 +514,7 @@
<li class="md-nav__item">
- <a href="/ts-0019/v4.1.1/5.1/" class="md-nav__link">
+ <a href="/v4.1.1/5.1/" class="md-nav__link">
<span class="md-ellipsis">
@@ -535,7 +535,7 @@
<li class="md-nav__item">
- <a href="/ts-0019/v4.1.1/5.2/" class="md-nav__link">
+ <a href="/v4.1.1/5.2/" class="md-nav__link">
<span class="md-ellipsis">
@@ -556,7 +556,7 @@
<li class="md-nav__item">
- <a href="/ts-0019/v4.1.1/5.3/" class="md-nav__link">
+ <a href="/v4.1.1/5.3/" class="md-nav__link">
<span class="md-ellipsis">
@@ -577,7 +577,7 @@
<li class="md-nav__item">
- <a href="/ts-0019/v4.1.1/5.4/" class="md-nav__link">
+ <a href="/v4.1.1/5.4/" class="md-nav__link">
<span class="md-ellipsis">
@@ -598,7 +598,7 @@
<li class="md-nav__item">
- <a href="/ts-0019/v4.1.1/5.5/" class="md-nav__link">
+ <a href="/v4.1.1/5.5/" class="md-nav__link">
<span class="md-ellipsis">
@@ -619,7 +619,7 @@
<li class="md-nav__item">
- <a href="/ts-0019/v4.1.1/5.6/" class="md-nav__link">
+ <a href="/v4.1.1/5.6/" class="md-nav__link">
<span class="md-ellipsis">
@@ -647,7 +647,7 @@
<li class="md-nav__item">
- <a href="/ts-0019/v4.1.1/6/" class="md-nav__link">
+ <a href="/v4.1.1/6/" class="md-nav__link">
<span class="md-ellipsis">
@@ -702,7 +702,7 @@
<li class="md-nav__item">
- <a href="/ts-0019/v4.1.1/7.0/" class="md-nav__link">
+ <a href="/v4.1.1/7.0/" class="md-nav__link">
<span class="md-ellipsis">
@@ -723,7 +723,7 @@
<li class="md-nav__item">
- <a href="/ts-0019/v4.1.1/7.1/" class="md-nav__link">
+ <a href="/v4.1.1/7.1/" class="md-nav__link">
<span class="md-ellipsis">
@@ -744,7 +744,7 @@
<li class="md-nav__item">
- <a href="/ts-0019/v4.1.1/7.2/" class="md-nav__link">
+ <a href="/v4.1.1/7.2/" class="md-nav__link">
<span class="md-ellipsis">
@@ -765,7 +765,7 @@
<li class="md-nav__item">
- <a href="/ts-0019/v4.1.1/7.3/" class="md-nav__link">
+ <a href="/v4.1.1/7.3/" class="md-nav__link">
<span class="md-ellipsis">
@@ -793,7 +793,7 @@
<li class="md-nav__item">
- <a href="/ts-0019/v4.1.1/8/" class="md-nav__link">
+ <a href="/v4.1.1/8/" class="md-nav__link">
<span class="md-ellipsis">
@@ -848,7 +848,7 @@
<li class="md-nav__item">
- <a href="/ts-0019/v4.1.1/A.1/" class="md-nav__link">
+ <a href="/v4.1.1/A.1/" class="md-nav__link">
<span class="md-ellipsis">
@@ -876,7 +876,7 @@
<li class="md-nav__item">
- <a href="/ts-0019/v4.1.1/B/" class="md-nav__link">
+ <a href="/v4.1.1/B/" class="md-nav__link">
<span class="md-ellipsis">
@@ -896,7 +896,7 @@
<li class="md-nav__item">
- <a href="/ts-0019/v4.1.1/download/" class="md-nav__link">
+ <a href="/v4.1.1/download/" class="md-nav__link">
<span class="md-ellipsis">
@@ -1022,10 +1022,10 @@
</div>
- <script id="__config" type="application/json">{"base": "/ts-0019/v4.1.1", "features": ["content.code.annotate", "content.code.copy", "content.footnote.tooltips", "search.suggest", "search.highlight", "search.share"], "search": "/ts-0019/v4.1.1/assets/javascripts/workers/search.6ce7567c.min.js", "translations": {"clipboard.copied": "Copied to clipboard", "clipboard.copy": "Copy to clipboard", "search.result.more.one": "1 more on this page", "search.result.more.other": "# more on this page", "search.result.none": "No matching documents", "search.result.one": "1 matching document", "search.result.other": "# matching documents", "search.result.placeholder": "Type to start searching", "search.result.term.missing": "Missing", "select.version": "Select version"}, "version": {"provider": "mike"}}</script>
+ <script id="__config" type="application/json">{"base": "/v4.1.1", "features": ["content.code.annotate", "content.code.copy", "content.footnote.tooltips", "search.suggest", "search.highlight", "search.share"], "search": "/v4.1.1/assets/javascripts/workers/search.6ce7567c.min.js", "translations": {"clipboard.copied": "Copied to clipboard", "clipboard.copy": "Copy to clipboard", "search.result.more.one": "1 more on this page", "search.result.more.other": "# more on this page", "search.result.none": "No matching documents", "search.result.one": "1 matching document", "search.result.other": "# matching documents", "search.result.placeholder": "Type to start searching", "search.result.term.missing": "Missing", "select.version": "Select version"}, "version": {"provider": "mike"}}</script>
- <script src="/ts-0019/v4.1.1/assets/javascripts/bundle.83f73b43.min.js"></script>
+ <script src="/v4.1.1/assets/javascripts/bundle.83f73b43.min.js"></script>
</body>
diff --git a/public/v4.1.1/5.1/index.html b/public/v4.1.1/5.1/index.html
index 5c487236071ba7df3b900a3caf7ca5fd02eda4db..5a679b3863b763eec97e33c57d43eb6ed8d6213f 100644
--- a/public/v4.1.1/5.1/index.html
+++ b/public/v4.1.1/5.1/index.html
@@ -10,7 +10,7 @@
- <link rel="canonical" href="https://specifications.onem2m.org/ts-0019/v4.1.1/5.1/">
+ <link rel="canonical" href="https://specifications.onem2m.org/v4.1.1/5.1/">
<link rel="prev" href="../4/">
@@ -94,7 +94,7 @@
<header class="md-header md-header--shadow" data-md-component="header">
<nav class="md-header__inner md-grid" aria-label="Header">
- <a href=".." title="oneM2M TS-0019" class="md-header__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
+ <a href="https://specifications.onem2m.org" title="oneM2M TS-0019" class="md-header__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
<img src="../images/onem2m.png" alt="logo">
@@ -207,7 +207,7 @@
<nav class="md-nav md-nav--primary" aria-label="Navigation" data-md-level="0">
<label class="md-nav__title" for="__drawer">
- <a href=".." title="oneM2M TS-0019" class="md-nav__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
+ <a href="https://specifications.onem2m.org" title="oneM2M TS-0019" class="md-nav__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
<img src="../images/onem2m.png" alt="logo">
@@ -240,7 +240,7 @@
<span class="md-ellipsis">
-
+ Home
</span>
diff --git a/public/v4.1.1/5.2/index.html b/public/v4.1.1/5.2/index.html
index 07378304aa3b8e2f00c238ea3c47277089718e08..2f2600cf50f2f09be5b4864b2b77ff23c6ccedfe 100644
--- a/public/v4.1.1/5.2/index.html
+++ b/public/v4.1.1/5.2/index.html
@@ -10,7 +10,7 @@
- <link rel="canonical" href="https://specifications.onem2m.org/ts-0019/v4.1.1/5.2/">
+ <link rel="canonical" href="https://specifications.onem2m.org/v4.1.1/5.2/">
<link rel="prev" href="../5.1/">
@@ -99,7 +99,7 @@
<header class="md-header md-header--shadow" data-md-component="header">
<nav class="md-header__inner md-grid" aria-label="Header">
- <a href=".." title="oneM2M TS-0019" class="md-header__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
+ <a href="https://specifications.onem2m.org" title="oneM2M TS-0019" class="md-header__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
<img src="../images/onem2m.png" alt="logo">
@@ -212,7 +212,7 @@
<nav class="md-nav md-nav--primary" aria-label="Navigation" data-md-level="0">
<label class="md-nav__title" for="__drawer">
- <a href=".." title="oneM2M TS-0019" class="md-nav__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
+ <a href="https://specifications.onem2m.org" title="oneM2M TS-0019" class="md-nav__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
<img src="../images/onem2m.png" alt="logo">
@@ -245,7 +245,7 @@
<span class="md-ellipsis">
-
+ Home
</span>
diff --git a/public/v4.1.1/5.3/index.html b/public/v4.1.1/5.3/index.html
index b6e0401a50e59b36e9a3aefdeec217818ac67cb2..3cc7e9b3162ac2c72f0460c01f7ce7f9f266b853 100644
--- a/public/v4.1.1/5.3/index.html
+++ b/public/v4.1.1/5.3/index.html
@@ -10,7 +10,7 @@
- <link rel="canonical" href="https://specifications.onem2m.org/ts-0019/v4.1.1/5.3/">
+ <link rel="canonical" href="https://specifications.onem2m.org/v4.1.1/5.3/">
<link rel="prev" href="../5.2/">
@@ -94,7 +94,7 @@
<header class="md-header md-header--shadow" data-md-component="header">
<nav class="md-header__inner md-grid" aria-label="Header">
- <a href=".." title="oneM2M TS-0019" class="md-header__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
+ <a href="https://specifications.onem2m.org" title="oneM2M TS-0019" class="md-header__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
<img src="../images/onem2m.png" alt="logo">
@@ -207,7 +207,7 @@
<nav class="md-nav md-nav--primary" aria-label="Navigation" data-md-level="0">
<label class="md-nav__title" for="__drawer">
- <a href=".." title="oneM2M TS-0019" class="md-nav__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
+ <a href="https://specifications.onem2m.org" title="oneM2M TS-0019" class="md-nav__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
<img src="../images/onem2m.png" alt="logo">
@@ -240,7 +240,7 @@
<span class="md-ellipsis">
-
+ Home
</span>
diff --git a/public/v4.1.1/5.4/index.html b/public/v4.1.1/5.4/index.html
index 070ed6b5dc6a753da65b1a46af6f461993570122..3e1f24effbe95429a1431ccb9126fabc3d46d167 100644
--- a/public/v4.1.1/5.4/index.html
+++ b/public/v4.1.1/5.4/index.html
@@ -10,7 +10,7 @@
- <link rel="canonical" href="https://specifications.onem2m.org/ts-0019/v4.1.1/5.4/">
+ <link rel="canonical" href="https://specifications.onem2m.org/v4.1.1/5.4/">
<link rel="prev" href="../5.3/">
@@ -99,7 +99,7 @@
<header class="md-header md-header--shadow" data-md-component="header">
<nav class="md-header__inner md-grid" aria-label="Header">
- <a href=".." title="oneM2M TS-0019" class="md-header__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
+ <a href="https://specifications.onem2m.org" title="oneM2M TS-0019" class="md-header__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
<img src="../images/onem2m.png" alt="logo">
@@ -212,7 +212,7 @@
<nav class="md-nav md-nav--primary" aria-label="Navigation" data-md-level="0">
<label class="md-nav__title" for="__drawer">
- <a href=".." title="oneM2M TS-0019" class="md-nav__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
+ <a href="https://specifications.onem2m.org" title="oneM2M TS-0019" class="md-nav__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
<img src="../images/onem2m.png" alt="logo">
@@ -245,7 +245,7 @@
<span class="md-ellipsis">
-
+ Home
</span>
diff --git a/public/v4.1.1/5.5/index.html b/public/v4.1.1/5.5/index.html
index c07205f614416eb1eded465cdc0daa9af7fc60fe..ab2a5ce10612cb9d1f2388649bb6ae5e614aab22 100644
--- a/public/v4.1.1/5.5/index.html
+++ b/public/v4.1.1/5.5/index.html
@@ -10,7 +10,7 @@
- <link rel="canonical" href="https://specifications.onem2m.org/ts-0019/v4.1.1/5.5/">
+ <link rel="canonical" href="https://specifications.onem2m.org/v4.1.1/5.5/">
<link rel="prev" href="../5.4/">
@@ -99,7 +99,7 @@
<header class="md-header md-header--shadow" data-md-component="header">
<nav class="md-header__inner md-grid" aria-label="Header">
- <a href=".." title="oneM2M TS-0019" class="md-header__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
+ <a href="https://specifications.onem2m.org" title="oneM2M TS-0019" class="md-header__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
<img src="../images/onem2m.png" alt="logo">
@@ -212,7 +212,7 @@
<nav class="md-nav md-nav--primary" aria-label="Navigation" data-md-level="0">
<label class="md-nav__title" for="__drawer">
- <a href=".." title="oneM2M TS-0019" class="md-nav__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
+ <a href="https://specifications.onem2m.org" title="oneM2M TS-0019" class="md-nav__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
<img src="../images/onem2m.png" alt="logo">
@@ -245,7 +245,7 @@
<span class="md-ellipsis">
-
+ Home
</span>
diff --git a/public/v4.1.1/5.6/index.html b/public/v4.1.1/5.6/index.html
index fd05d18ee745282b53a21df1e27c29c83e79c0fd..c38564e523260e2e13adcec914920ddaca84e9cb 100644
--- a/public/v4.1.1/5.6/index.html
+++ b/public/v4.1.1/5.6/index.html
@@ -10,7 +10,7 @@
- <link rel="canonical" href="https://specifications.onem2m.org/ts-0019/v4.1.1/5.6/">
+ <link rel="canonical" href="https://specifications.onem2m.org/v4.1.1/5.6/">
<link rel="prev" href="../5.5/">
@@ -94,7 +94,7 @@
<header class="md-header md-header--shadow" data-md-component="header">
<nav class="md-header__inner md-grid" aria-label="Header">
- <a href=".." title="oneM2M TS-0019" class="md-header__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
+ <a href="https://specifications.onem2m.org" title="oneM2M TS-0019" class="md-header__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
<img src="../images/onem2m.png" alt="logo">
@@ -207,7 +207,7 @@
<nav class="md-nav md-nav--primary" aria-label="Navigation" data-md-level="0">
<label class="md-nav__title" for="__drawer">
- <a href=".." title="oneM2M TS-0019" class="md-nav__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
+ <a href="https://specifications.onem2m.org" title="oneM2M TS-0019" class="md-nav__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
<img src="../images/onem2m.png" alt="logo">
@@ -240,7 +240,7 @@
<span class="md-ellipsis">
-
+ Home
</span>
diff --git a/public/v4.1.1/5/index.html b/public/v4.1.1/5/index.html
index 7616c6bc2f5bcd5410e49596576f81edaa916294..7a0378c53fea91cc945b77d4f20ddda4787fb217 100644
--- a/public/v4.1.1/5/index.html
+++ b/public/v4.1.1/5/index.html
@@ -10,7 +10,7 @@
- <link rel="canonical" href="https://specifications.onem2m.org/ts-0019/v4.1.1/5/">
+ <link rel="canonical" href="https://specifications.onem2m.org/v4.1.1/5/">
@@ -90,7 +90,7 @@
<header class="md-header md-header--shadow" data-md-component="header">
<nav class="md-header__inner md-grid" aria-label="Header">
- <a href=".." title="oneM2M TS-0019" class="md-header__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
+ <a href="https://specifications.onem2m.org" title="oneM2M TS-0019" class="md-header__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
<img src="../images/onem2m.png" alt="logo">
@@ -203,7 +203,7 @@
<nav class="md-nav md-nav--primary" aria-label="Navigation" data-md-level="0">
<label class="md-nav__title" for="__drawer">
- <a href=".." title="oneM2M TS-0019" class="md-nav__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
+ <a href="https://specifications.onem2m.org" title="oneM2M TS-0019" class="md-nav__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
<img src="../images/onem2m.png" alt="logo">
@@ -236,7 +236,7 @@
<span class="md-ellipsis">
-
+ Home
</span>
diff --git a/public/v4.1.1/6/index.html b/public/v4.1.1/6/index.html
index 5b63f472a2e9cd557d2172e361af839723e21b03..270f697c25b9a1a31c52cff3f63a398e475a9c22 100644
--- a/public/v4.1.1/6/index.html
+++ b/public/v4.1.1/6/index.html
@@ -10,7 +10,7 @@
- <link rel="canonical" href="https://specifications.onem2m.org/ts-0019/v4.1.1/6/">
+ <link rel="canonical" href="https://specifications.onem2m.org/v4.1.1/6/">
<link rel="prev" href="../5.6/">
@@ -94,7 +94,7 @@
<header class="md-header md-header--shadow" data-md-component="header">
<nav class="md-header__inner md-grid" aria-label="Header">
- <a href=".." title="oneM2M TS-0019" class="md-header__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
+ <a href="https://specifications.onem2m.org" title="oneM2M TS-0019" class="md-header__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
<img src="../images/onem2m.png" alt="logo">
@@ -207,7 +207,7 @@
<nav class="md-nav md-nav--primary" aria-label="Navigation" data-md-level="0">
<label class="md-nav__title" for="__drawer">
- <a href=".." title="oneM2M TS-0019" class="md-nav__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
+ <a href="https://specifications.onem2m.org" title="oneM2M TS-0019" class="md-nav__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
<img src="../images/onem2m.png" alt="logo">
@@ -240,7 +240,7 @@
<span class="md-ellipsis">
-
+ Home
</span>
diff --git a/public/v4.1.1/7.0/index.html b/public/v4.1.1/7.0/index.html
index 421167e2349bfc63f49da271c3fb244f914da0c2..f99db43bdac67d10134a194447af7e05f9eba3bc 100644
--- a/public/v4.1.1/7.0/index.html
+++ b/public/v4.1.1/7.0/index.html
@@ -10,7 +10,7 @@
- <link rel="canonical" href="https://specifications.onem2m.org/ts-0019/v4.1.1/7.0/">
+ <link rel="canonical" href="https://specifications.onem2m.org/v4.1.1/7.0/">
<link rel="prev" href="../6/">
@@ -94,7 +94,7 @@
<header class="md-header md-header--shadow" data-md-component="header">
<nav class="md-header__inner md-grid" aria-label="Header">
- <a href=".." title="oneM2M TS-0019" class="md-header__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
+ <a href="https://specifications.onem2m.org" title="oneM2M TS-0019" class="md-header__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
<img src="../images/onem2m.png" alt="logo">
@@ -207,7 +207,7 @@
<nav class="md-nav md-nav--primary" aria-label="Navigation" data-md-level="0">
<label class="md-nav__title" for="__drawer">
- <a href=".." title="oneM2M TS-0019" class="md-nav__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
+ <a href="https://specifications.onem2m.org" title="oneM2M TS-0019" class="md-nav__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
<img src="../images/onem2m.png" alt="logo">
@@ -240,7 +240,7 @@
<span class="md-ellipsis">
-
+ Home
</span>
diff --git a/public/v4.1.1/7.1/index.html b/public/v4.1.1/7.1/index.html
index 7c4746d82bf48405584dec403e315a4c0ba7de95..6706367df32a6fae1ee96d30b1b37bf706942bb4 100644
--- a/public/v4.1.1/7.1/index.html
+++ b/public/v4.1.1/7.1/index.html
@@ -10,7 +10,7 @@
- <link rel="canonical" href="https://specifications.onem2m.org/ts-0019/v4.1.1/7.1/">
+ <link rel="canonical" href="https://specifications.onem2m.org/v4.1.1/7.1/">
<link rel="prev" href="../7.0/">
@@ -99,7 +99,7 @@
<header class="md-header md-header--shadow" data-md-component="header">
<nav class="md-header__inner md-grid" aria-label="Header">
- <a href=".." title="oneM2M TS-0019" class="md-header__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
+ <a href="https://specifications.onem2m.org" title="oneM2M TS-0019" class="md-header__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
<img src="../images/onem2m.png" alt="logo">
@@ -212,7 +212,7 @@
<nav class="md-nav md-nav--primary" aria-label="Navigation" data-md-level="0">
<label class="md-nav__title" for="__drawer">
- <a href=".." title="oneM2M TS-0019" class="md-nav__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
+ <a href="https://specifications.onem2m.org" title="oneM2M TS-0019" class="md-nav__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
<img src="../images/onem2m.png" alt="logo">
@@ -245,7 +245,7 @@
<span class="md-ellipsis">
-
+ Home
</span>
diff --git a/public/v4.1.1/7.2/index.html b/public/v4.1.1/7.2/index.html
index 83d52f6849577adbde604bfd9db9c741b54695c4..854a435095b0b0f4c511d802f55a34fabe29b2b0 100644
--- a/public/v4.1.1/7.2/index.html
+++ b/public/v4.1.1/7.2/index.html
@@ -10,7 +10,7 @@
- <link rel="canonical" href="https://specifications.onem2m.org/ts-0019/v4.1.1/7.2/">
+ <link rel="canonical" href="https://specifications.onem2m.org/v4.1.1/7.2/">
<link rel="prev" href="../7.1/">
@@ -99,7 +99,7 @@
<header class="md-header md-header--shadow" data-md-component="header">
<nav class="md-header__inner md-grid" aria-label="Header">
- <a href=".." title="oneM2M TS-0019" class="md-header__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
+ <a href="https://specifications.onem2m.org" title="oneM2M TS-0019" class="md-header__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
<img src="../images/onem2m.png" alt="logo">
@@ -212,7 +212,7 @@
<nav class="md-nav md-nav--primary" aria-label="Navigation" data-md-level="0">
<label class="md-nav__title" for="__drawer">
- <a href=".." title="oneM2M TS-0019" class="md-nav__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
+ <a href="https://specifications.onem2m.org" title="oneM2M TS-0019" class="md-nav__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
<img src="../images/onem2m.png" alt="logo">
@@ -245,7 +245,7 @@
<span class="md-ellipsis">
-
+ Home
</span>
diff --git a/public/v4.1.1/7.3/index.html b/public/v4.1.1/7.3/index.html
index c856ac0b2d582df5a384eb26a6765674215427fe..2832c14b26b4aaeada5fd47ac851ac9ef0aec777 100644
--- a/public/v4.1.1/7.3/index.html
+++ b/public/v4.1.1/7.3/index.html
@@ -10,7 +10,7 @@
- <link rel="canonical" href="https://specifications.onem2m.org/ts-0019/v4.1.1/7.3/">
+ <link rel="canonical" href="https://specifications.onem2m.org/v4.1.1/7.3/">
<link rel="prev" href="../7.2/">
@@ -94,7 +94,7 @@
<header class="md-header md-header--shadow" data-md-component="header">
<nav class="md-header__inner md-grid" aria-label="Header">
- <a href=".." title="oneM2M TS-0019" class="md-header__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
+ <a href="https://specifications.onem2m.org" title="oneM2M TS-0019" class="md-header__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
<img src="../images/onem2m.png" alt="logo">
@@ -207,7 +207,7 @@
<nav class="md-nav md-nav--primary" aria-label="Navigation" data-md-level="0">
<label class="md-nav__title" for="__drawer">
- <a href=".." title="oneM2M TS-0019" class="md-nav__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
+ <a href="https://specifications.onem2m.org" title="oneM2M TS-0019" class="md-nav__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
<img src="../images/onem2m.png" alt="logo">
@@ -240,7 +240,7 @@
<span class="md-ellipsis">
-
+ Home
</span>
diff --git a/public/v4.1.1/7/index.html b/public/v4.1.1/7/index.html
index b018e57c48957bb59ad1a08e1c7810c1ea49bfa5..e71e5e6bb4bda6aab1a5eba3f78040a4177cfa27 100644
--- a/public/v4.1.1/7/index.html
+++ b/public/v4.1.1/7/index.html
@@ -10,7 +10,7 @@
- <link rel="canonical" href="https://specifications.onem2m.org/ts-0019/v4.1.1/7/">
+ <link rel="canonical" href="https://specifications.onem2m.org/v4.1.1/7/">
@@ -90,7 +90,7 @@
<header class="md-header md-header--shadow" data-md-component="header">
<nav class="md-header__inner md-grid" aria-label="Header">
- <a href=".." title="oneM2M TS-0019" class="md-header__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
+ <a href="https://specifications.onem2m.org" title="oneM2M TS-0019" class="md-header__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
<img src="../images/onem2m.png" alt="logo">
@@ -203,7 +203,7 @@
<nav class="md-nav md-nav--primary" aria-label="Navigation" data-md-level="0">
<label class="md-nav__title" for="__drawer">
- <a href=".." title="oneM2M TS-0019" class="md-nav__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
+ <a href="https://specifications.onem2m.org" title="oneM2M TS-0019" class="md-nav__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
<img src="../images/onem2m.png" alt="logo">
@@ -236,7 +236,7 @@
<span class="md-ellipsis">
-
+ Home
</span>
diff --git a/public/v4.1.1/8/index.html b/public/v4.1.1/8/index.html
index 7baf4c4fb37b43016958326a888e01cc9cd675c8..8550ae45fa68ab5187abd4bcbdf2381cd3050ef4 100644
--- a/public/v4.1.1/8/index.html
+++ b/public/v4.1.1/8/index.html
@@ -10,7 +10,7 @@
- <link rel="canonical" href="https://specifications.onem2m.org/ts-0019/v4.1.1/8/">
+ <link rel="canonical" href="https://specifications.onem2m.org/v4.1.1/8/">
<link rel="prev" href="../7.3/">
@@ -94,7 +94,7 @@
<header class="md-header md-header--shadow" data-md-component="header">
<nav class="md-header__inner md-grid" aria-label="Header">
- <a href=".." title="oneM2M TS-0019" class="md-header__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
+ <a href="https://specifications.onem2m.org" title="oneM2M TS-0019" class="md-header__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
<img src="../images/onem2m.png" alt="logo">
@@ -207,7 +207,7 @@
<nav class="md-nav md-nav--primary" aria-label="Navigation" data-md-level="0">
<label class="md-nav__title" for="__drawer">
- <a href=".." title="oneM2M TS-0019" class="md-nav__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
+ <a href="https://specifications.onem2m.org" title="oneM2M TS-0019" class="md-nav__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
<img src="../images/onem2m.png" alt="logo">
@@ -240,7 +240,7 @@
<span class="md-ellipsis">
-
+ Home
</span>
diff --git a/public/v4.1.1/A.1/index.html b/public/v4.1.1/A.1/index.html
index 8f95e8506a6e8ee4cb6eb18ea2330cca6ece1625..06126266e3165037f9b998fd5ba5f738969d8d95 100644
--- a/public/v4.1.1/A.1/index.html
+++ b/public/v4.1.1/A.1/index.html
@@ -10,7 +10,7 @@
- <link rel="canonical" href="https://specifications.onem2m.org/ts-0019/v4.1.1/A.1/">
+ <link rel="canonical" href="https://specifications.onem2m.org/v4.1.1/A.1/">
<link rel="prev" href="../8/">
@@ -94,7 +94,7 @@
<header class="md-header md-header--shadow" data-md-component="header">
<nav class="md-header__inner md-grid" aria-label="Header">
- <a href=".." title="oneM2M TS-0019" class="md-header__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
+ <a href="https://specifications.onem2m.org" title="oneM2M TS-0019" class="md-header__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
<img src="../images/onem2m.png" alt="logo">
@@ -207,7 +207,7 @@
<nav class="md-nav md-nav--primary" aria-label="Navigation" data-md-level="0">
<label class="md-nav__title" for="__drawer">
- <a href=".." title="oneM2M TS-0019" class="md-nav__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
+ <a href="https://specifications.onem2m.org" title="oneM2M TS-0019" class="md-nav__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
<img src="../images/onem2m.png" alt="logo">
@@ -240,7 +240,7 @@
<span class="md-ellipsis">
-
+ Home
</span>
diff --git a/public/v4.1.1/A/index.html b/public/v4.1.1/A/index.html
index 52595731d9509f343908c853c1c79386f198f8a4..dba7c7bed1b692a02c03f72d75fc782a160f4858 100644
--- a/public/v4.1.1/A/index.html
+++ b/public/v4.1.1/A/index.html
@@ -10,7 +10,7 @@
- <link rel="canonical" href="https://specifications.onem2m.org/ts-0019/v4.1.1/A/">
+ <link rel="canonical" href="https://specifications.onem2m.org/v4.1.1/A/">
@@ -90,7 +90,7 @@
<header class="md-header md-header--shadow" data-md-component="header">
<nav class="md-header__inner md-grid" aria-label="Header">
- <a href=".." title="oneM2M TS-0019" class="md-header__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
+ <a href="https://specifications.onem2m.org" title="oneM2M TS-0019" class="md-header__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
<img src="../images/onem2m.png" alt="logo">
@@ -203,7 +203,7 @@
<nav class="md-nav md-nav--primary" aria-label="Navigation" data-md-level="0">
<label class="md-nav__title" for="__drawer">
- <a href=".." title="oneM2M TS-0019" class="md-nav__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
+ <a href="https://specifications.onem2m.org" title="oneM2M TS-0019" class="md-nav__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
<img src="../images/onem2m.png" alt="logo">
@@ -236,7 +236,7 @@
<span class="md-ellipsis">
-
+ Home
</span>
diff --git a/public/v4.1.1/B/index.html b/public/v4.1.1/B/index.html
index de2a04a1b4f3f9a1577c4626e8b0f574f5c2eb91..9aab9862c6590415e32e8ee6b0e84de7e083bd99 100644
--- a/public/v4.1.1/B/index.html
+++ b/public/v4.1.1/B/index.html
@@ -10,7 +10,7 @@
- <link rel="canonical" href="https://specifications.onem2m.org/ts-0019/v4.1.1/B/">
+ <link rel="canonical" href="https://specifications.onem2m.org/v4.1.1/B/">
<link rel="prev" href="../A.1/">
@@ -94,7 +94,7 @@
<header class="md-header md-header--shadow" data-md-component="header">
<nav class="md-header__inner md-grid" aria-label="Header">
- <a href=".." title="oneM2M TS-0019" class="md-header__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
+ <a href="https://specifications.onem2m.org" title="oneM2M TS-0019" class="md-header__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
<img src="../images/onem2m.png" alt="logo">
@@ -207,7 +207,7 @@
<nav class="md-nav md-nav--primary" aria-label="Navigation" data-md-level="0">
<label class="md-nav__title" for="__drawer">
- <a href=".." title="oneM2M TS-0019" class="md-nav__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
+ <a href="https://specifications.onem2m.org" title="oneM2M TS-0019" class="md-nav__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
<img src="../images/onem2m.png" alt="logo">
@@ -240,7 +240,7 @@
<span class="md-ellipsis">
-
+ Home
</span>
diff --git a/public/v4.1.1/download/TS-0019-Abstract_Test_Suite_and_implementation_eXtra_Information_for_Test_v4.1.1.docx b/public/v4.1.1/download/TS-0019-Abstract_Test_Suite_and_implementation_eXtra_Information_for_Test_v4.1.1.docx
index 532fd704dab63ef397decaecd436ce322aeaa6bf..3605a236f8d434b271ea1b2fee4fe391f69c2013 100644
Binary files a/public/v4.1.1/download/TS-0019-Abstract_Test_Suite_and_implementation_eXtra_Information_for_Test_v4.1.1.docx and b/public/v4.1.1/download/TS-0019-Abstract_Test_Suite_and_implementation_eXtra_Information_for_Test_v4.1.1.docx differ
diff --git a/public/v4.1.1/download/TS-0019-Abstract_Test_Suite_and_implementation_eXtra_Information_for_Test_v4.1.1.epub b/public/v4.1.1/download/TS-0019-Abstract_Test_Suite_and_implementation_eXtra_Information_for_Test_v4.1.1.epub
index 733b5c0b64a5396422a3a0ac920270f1c4f2679a..505c2f064ac4b67394df78b707396f5ca29e0617 100644
Binary files a/public/v4.1.1/download/TS-0019-Abstract_Test_Suite_and_implementation_eXtra_Information_for_Test_v4.1.1.epub and b/public/v4.1.1/download/TS-0019-Abstract_Test_Suite_and_implementation_eXtra_Information_for_Test_v4.1.1.epub differ
diff --git a/public/v4.1.1/download/TS-0019-Abstract_Test_Suite_and_implementation_eXtra_Information_for_Test_v4.1.1.pdf b/public/v4.1.1/download/TS-0019-Abstract_Test_Suite_and_implementation_eXtra_Information_for_Test_v4.1.1.pdf
index 7bc9a8e722d3a21250bd7ead4aaa3fe77908206b..8888a322d2accbb653ab73f290879aeb958c33e4 100644
Binary files a/public/v4.1.1/download/TS-0019-Abstract_Test_Suite_and_implementation_eXtra_Information_for_Test_v4.1.1.pdf and b/public/v4.1.1/download/TS-0019-Abstract_Test_Suite_and_implementation_eXtra_Information_for_Test_v4.1.1.pdf differ
diff --git a/public/v4.1.1/download/index.html b/public/v4.1.1/download/index.html
index 7366490144ff1ba0e89a02b947535a6848d19b51..951224ac564804fbe698181b43250f3a09265581 100644
--- a/public/v4.1.1/download/index.html
+++ b/public/v4.1.1/download/index.html
@@ -10,7 +10,7 @@
- <link rel="canonical" href="https://specifications.onem2m.org/ts-0019/v4.1.1/download/">
+ <link rel="canonical" href="https://specifications.onem2m.org/v4.1.1/download/">
<link rel="prev" href="../B/">
@@ -92,7 +92,7 @@
<header class="md-header md-header--shadow" data-md-component="header">
<nav class="md-header__inner md-grid" aria-label="Header">
- <a href=".." title="oneM2M TS-0019" class="md-header__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
+ <a href="https://specifications.onem2m.org" title="oneM2M TS-0019" class="md-header__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
<img src="../images/onem2m.png" alt="logo">
@@ -205,7 +205,7 @@
<nav class="md-nav md-nav--primary" aria-label="Navigation" data-md-level="0">
<label class="md-nav__title" for="__drawer">
- <a href=".." title="oneM2M TS-0019" class="md-nav__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
+ <a href="https://specifications.onem2m.org" title="oneM2M TS-0019" class="md-nav__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
<img src="../images/onem2m.png" alt="logo">
@@ -238,7 +238,7 @@
<span class="md-ellipsis">
-
+ Home
</span>
diff --git a/public/v4.1.1/feed_json_created.json b/public/v4.1.1/feed_json_created.json
index 11d70666b6f1d72a53c830225fc3c5d70445d1b2..b0ac324990244915662b871e6122bef13a8ca050 100644
--- a/public/v4.1.1/feed_json_created.json
+++ b/public/v4.1.1/feed_json_created.json
@@ -1 +1 @@
-{"version": "https://jsonfeed.org/version/1", "title": "oneM2M TS-0019", "home_page_url": "https://specifications.onem2m.org/ts-0019/v4.1.1/", "feed_url": "https://specifications.onem2m.org/ts-0019/v4.1.1/feed_json_created.json", "description": "oneM2M Specifications navigator", "icon": null, "authors": [], "language": "en", "items": [{"id": "https://specifications.onem2m.org/ts-0019/v4.1.1/download/", "url": "https://specifications.onem2m.org/ts-0019/v4.1.1/download/", "title": "Download", "content_html": "<p>Download baseline for TS-0019 version v4.1.1:</p>\n<p>[<img alt=\"Word\" src=\"images/Word.png\">](TS-0019-Abstract_Test_Suite_and_implementation_eXtra_Information_for_Test_v4.1.1.do...</p>", "image": null, "date_published": "2024-11-14T14:10:06.643512+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v4.1.1/B/", "url": "https://specifications.onem2m.org/ts-0019/v4.1.1/B/", "title": "Annex B (informative): Bibliography", "content_html": "<p>ISO/IEC 9646-6 (1994): \"Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 6: Protocol profile test...</p>", "image": null, "date_published": "2024-11-14T14:10:06.625264+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v4.1.1/A/", "url": "https://specifications.onem2m.org/ts-0019/v4.1.1/A/", "title": "A", "content_html": "", "image": null, "date_published": "2024-11-14T14:10:06.604352+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v4.1.1/A.1/", "url": "https://specifications.onem2m.org/ts-0019/v4.1.1/A.1/", "title": "A.1 Electronic annex, zip file with TTCN-3 code", "content_html": "<p>This ATS has been produced using the Testing and Test Control Notation (TTCN) according to ETSI ES 201 873-1 <a href=\"../2.1/#_ref_6\">[6]</a>.</p>\n<p>This test sui...</p>", "image": null, "date_published": "2024-11-14T14:10:06.582599+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v4.1.1/8/", "url": "https://specifications.onem2m.org/ts-0019/v4.1.1/8/", "title": "8 TTCN-3 Verifications", "content_html": "<p>The principles for Verifying the TTCN-3 test code are given in oneM2M TS-0015 <a href=\"../2.2/#_ref_i.2\">[i.2]</a>.</p>\n<p>All test cases provided with the present...</p>", "image": null, "date_published": "2024-11-14T14:10:06.565645+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v4.1.1/7/", "url": "https://specifications.onem2m.org/ts-0019/v4.1.1/7/", "title": "7", "content_html": "", "image": null, "date_published": "2024-11-14T14:10:06.548582+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v4.1.1/7.3/", "url": "https://specifications.onem2m.org/ts-0019/v4.1.1/7.3/", "title": "7.3 IXIT", "content_html": "<p>The following parameters are used by the oneM2M ATS for the correct execution of the test cases.</p>\n<p><strong>Table 7.3-1: oneM2M ATS IXITs</strong><a name=\"table_7.3-1\"></a...</p>", "image": null, "date_published": "2024-11-14T14:10:06.534479+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v4.1.1/7.2/", "url": "https://specifications.onem2m.org/ts-0019/v4.1.1/7.2/", "title": "7.2 Naming conventions", "content_html": "<h3>7.2.1 General guidelines</h3>\n<p>This test suite follows the naming convention guidelines provided in oneM2M TS-0015 <a href=\"../2.2/#_ref_i.2\">[i.2]</a>.</p>\n<p>The n...</p>", "image": null, "date_published": "2024-11-14T14:10:06.503875+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v4.1.1/7.1/", "url": "https://specifications.onem2m.org/ts-0019/v4.1.1/7.1/", "title": "7.1 Testing conventions", "content_html": "<h3>7.1.1 Testing states</h3>\n<h4>7.1.1.1 Initial state</h4>\n<p>All test cases start with the function f_preamble_XYZ. This function brings the IUT in an \"initialized...</p>", "image": null, "date_published": "2024-11-14T14:10:06.470172+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v4.1.1/7.0/", "url": "https://specifications.onem2m.org/ts-0019/v4.1.1/7.0/", "title": "7.0 Introduction", "content_html": "<p>The ATS conventions are intended to give a better understanding of the ATS but they also describe the conventions made for the development of the ATS. These ...</p>", "image": null, "date_published": "2024-11-14T14:10:06.453644+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v4.1.1/6/", "url": "https://specifications.onem2m.org/ts-0019/v4.1.1/6/", "title": "6 Untestable Test Purposes", "content_html": "<p>Void.</p>", "image": null, "date_published": "2024-11-14T14:10:06.431362+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v4.1.1/5/", "url": "https://specifications.onem2m.org/ts-0019/v4.1.1/5/", "title": "5", "content_html": "", "image": null, "date_published": "2024-11-14T14:10:06.416860+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v4.1.1/5.6/", "url": "https://specifications.onem2m.org/ts-0019/v4.1.1/5.6/", "title": "5.6 Test strategy", "content_html": "<p>This clause introduces the test strategy being used for the TTCN-3 test cases. The chosen strategy permits to have a clear structure of the code that facilit...</p>", "image": null, "date_published": "2024-11-14T14:10:06.402562+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v4.1.1/5.5/", "url": "https://specifications.onem2m.org/ts-0019/v4.1.1/5.5/", "title": "5.5 Test components", "content_html": "<h3>5.5.1 Tester</h3>\n<p>The Tester test component includes a set of ports, timers and variables that are common to the other defined components which are described ...</p>", "image": null, "date_published": "2024-11-14T14:10:06.384327+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v4.1.1/5.4/", "url": "https://specifications.onem2m.org/ts-0019/v4.1.1/5.4/", "title": "5.4 Ports and ASPs (Abstract Services Primitives)", "content_html": "<h3>5.4.0 Introduction</h3>\n<p>The oneM2M ATS implements the following ports:</p>\n<ul>\n<li>The mcaPort and mcaPortIn</li>\n<li>The mccPort and mccPortIn</li>\n<li>The acPort</li>\n<li>The utPort</li>\n<li>...</li>\n</ul>", "image": null, "date_published": "2024-11-14T14:10:06.349746+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v4.1.1/5.3/", "url": "https://specifications.onem2m.org/ts-0019/v4.1.1/5.3/", "title": "5.3 Test architecture", "content_html": "<p>The approach for the implementation of an Abstract Protocol Tester selected in oneM2M follows the recommendation of the oneM2M Testing Framework oneM2M TS-00...</p>", "image": null, "date_published": "2024-11-14T14:10:06.293634+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v4.1.1/5.2/", "url": "https://specifications.onem2m.org/ts-0019/v4.1.1/5.2/", "title": "5.2 Test Configuration", "content_html": "<h3>5.2.1 AE Test Configuration</h3>\n<p>Test configurations are defined to test different entities such as CSE and AE, etc.</p>\n<p>Figure 5.2.1-1 shows a AE test configura...</p>", "image": null, "date_published": "2024-11-14T14:10:06.265100+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v4.1.1/5.1/", "url": "https://specifications.onem2m.org/ts-0019/v4.1.1/5.1/", "title": "5.1 Abstract protocol tester", "content_html": "<p>An abstract protocol tester (APT) is a process that provides behaviours for testing an IUT by emulating a peer IUT at the same layer, and enabling to address...</p>", "image": null, "date_published": "2024-11-14T14:10:06.247759+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v4.1.1/4/", "url": "https://specifications.onem2m.org/ts-0019/v4.1.1/4/", "title": "4 Conventions", "content_html": "<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 Rule...</p>", "image": null, "date_published": "2024-11-14T14:10:06.232108+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v4.1.1/3/", "url": "https://specifications.onem2m.org/ts-0019/v4.1.1/3/", "title": "3", "content_html": "", "image": null, "date_published": "2024-11-14T14:10:06.217917+00:00", "authors": [], "tags": null}]}
\ No newline at end of file
+{"version": "https://jsonfeed.org/version/1", "title": "oneM2M TS-0019", "home_page_url": "https://specifications.onem2m.org/v4.1.1/", "feed_url": "https://specifications.onem2m.org/v4.1.1/feed_json_created.json", "description": "oneM2M Specifications navigator", "icon": null, "authors": [], "language": "en", "items": [{"id": "https://specifications.onem2m.org/v4.1.1/download/", "url": "https://specifications.onem2m.org/v4.1.1/download/", "title": "Download", "content_html": "<p>Download baseline for TS-0019 version v4.1.1:</p>\n<p>[<img alt=\"Word\" src=\"images/Word.png\">](TS-0019-Abstract_Test_Suite_and_implementation_eXtra_Information_for_Test_v4.1.1.do...</p>", "image": null, "date_published": "2024-11-15T16:22:58.316250+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/v4.1.1/B/", "url": "https://specifications.onem2m.org/v4.1.1/B/", "title": "Annex B (informative): Bibliography", "content_html": "<p>ISO/IEC 9646-6 (1994): \"Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 6: Protocol profile test...</p>", "image": null, "date_published": "2024-11-15T16:22:58.298658+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/v4.1.1/A/", "url": "https://specifications.onem2m.org/v4.1.1/A/", "title": "A", "content_html": "", "image": null, "date_published": "2024-11-15T16:22:58.284579+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/v4.1.1/A.1/", "url": "https://specifications.onem2m.org/v4.1.1/A.1/", "title": "A.1 Electronic annex, zip file with TTCN-3 code", "content_html": "<p>This ATS has been produced using the Testing and Test Control Notation (TTCN) according to ETSI ES 201 873-1 <a href=\"../2.1/#_ref_6\">[6]</a>.</p>\n<p>This test sui...</p>", "image": null, "date_published": "2024-11-15T16:22:58.269644+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/v4.1.1/8/", "url": "https://specifications.onem2m.org/v4.1.1/8/", "title": "8 TTCN-3 Verifications", "content_html": "<p>The principles for Verifying the TTCN-3 test code are given in oneM2M TS-0015 <a href=\"../2.2/#_ref_i.2\">[i.2]</a>.</p>\n<p>All test cases provided with the present...</p>", "image": null, "date_published": "2024-11-15T16:22:58.249596+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/v4.1.1/7/", "url": "https://specifications.onem2m.org/v4.1.1/7/", "title": "7", "content_html": "", "image": null, "date_published": "2024-11-15T16:22:58.226431+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/v4.1.1/7.3/", "url": "https://specifications.onem2m.org/v4.1.1/7.3/", "title": "7.3 IXIT", "content_html": "<p>The following parameters are used by the oneM2M ATS for the correct execution of the test cases.</p>\n<p><strong>Table 7.3-1: oneM2M ATS IXITs</strong><a name=\"table_7.3-1\"></a...</p>", "image": null, "date_published": "2024-11-15T16:22:58.211223+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/v4.1.1/7.2/", "url": "https://specifications.onem2m.org/v4.1.1/7.2/", "title": "7.2 Naming conventions", "content_html": "<h3>7.2.1 General guidelines</h3>\n<p>This test suite follows the naming convention guidelines provided in oneM2M TS-0015 <a href=\"../2.2/#_ref_i.2\">[i.2]</a>.</p>\n<p>The n...</p>", "image": null, "date_published": "2024-11-15T16:22:58.178784+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/v4.1.1/7.1/", "url": "https://specifications.onem2m.org/v4.1.1/7.1/", "title": "7.1 Testing conventions", "content_html": "<h3>7.1.1 Testing states</h3>\n<h4>7.1.1.1 Initial state</h4>\n<p>All test cases start with the function f_preamble_XYZ. This function brings the IUT in an \"initialized...</p>", "image": null, "date_published": "2024-11-15T16:22:58.144587+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/v4.1.1/7.0/", "url": "https://specifications.onem2m.org/v4.1.1/7.0/", "title": "7.0 Introduction", "content_html": "<p>The ATS conventions are intended to give a better understanding of the ATS but they also describe the conventions made for the development of the ATS. These ...</p>", "image": null, "date_published": "2024-11-15T16:22:58.128515+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/v4.1.1/6/", "url": "https://specifications.onem2m.org/v4.1.1/6/", "title": "6 Untestable Test Purposes", "content_html": "<p>Void.</p>", "image": null, "date_published": "2024-11-15T16:22:58.112538+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/v4.1.1/5/", "url": "https://specifications.onem2m.org/v4.1.1/5/", "title": "5", "content_html": "", "image": null, "date_published": "2024-11-15T16:22:58.095827+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/v4.1.1/5.6/", "url": "https://specifications.onem2m.org/v4.1.1/5.6/", "title": "5.6 Test strategy", "content_html": "<p>This clause introduces the test strategy being used for the TTCN-3 test cases. The chosen strategy permits to have a clear structure of the code that facilit...</p>", "image": null, "date_published": "2024-11-15T16:22:58.078101+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/v4.1.1/5.5/", "url": "https://specifications.onem2m.org/v4.1.1/5.5/", "title": "5.5 Test components", "content_html": "<h3>5.5.1 Tester</h3>\n<p>The Tester test component includes a set of ports, timers and variables that are common to the other defined components which are described ...</p>", "image": null, "date_published": "2024-11-15T16:22:58.057033+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/v4.1.1/5.4/", "url": "https://specifications.onem2m.org/v4.1.1/5.4/", "title": "5.4 Ports and ASPs (Abstract Services Primitives)", "content_html": "<h3>5.4.0 Introduction</h3>\n<p>The oneM2M ATS implements the following ports:</p>\n<ul>\n<li>The mcaPort and mcaPortIn</li>\n<li>The mccPort and mccPortIn</li>\n<li>The acPort</li>\n<li>The utPort</li>\n<li>...</li>\n</ul>", "image": null, "date_published": "2024-11-15T16:22:58.020038+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/v4.1.1/5.3/", "url": "https://specifications.onem2m.org/v4.1.1/5.3/", "title": "5.3 Test architecture", "content_html": "<p>The approach for the implementation of an Abstract Protocol Tester selected in oneM2M follows the recommendation of the oneM2M Testing Framework oneM2M TS-00...</p>", "image": null, "date_published": "2024-11-15T16:22:57.928152+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/v4.1.1/5.2/", "url": "https://specifications.onem2m.org/v4.1.1/5.2/", "title": "5.2 Test Configuration", "content_html": "<h3>5.2.1 AE Test Configuration</h3>\n<p>Test configurations are defined to test different entities such as CSE and AE, etc.</p>\n<p>Figure 5.2.1-1 shows a AE test configura...</p>", "image": null, "date_published": "2024-11-15T16:22:57.904947+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/v4.1.1/5.1/", "url": "https://specifications.onem2m.org/v4.1.1/5.1/", "title": "5.1 Abstract protocol tester", "content_html": "<p>An abstract protocol tester (APT) is a process that provides behaviours for testing an IUT by emulating a peer IUT at the same layer, and enabling to address...</p>", "image": null, "date_published": "2024-11-15T16:22:57.882284+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/v4.1.1/4/", "url": "https://specifications.onem2m.org/v4.1.1/4/", "title": "4 Conventions", "content_html": "<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 Rule...</p>", "image": null, "date_published": "2024-11-15T16:22:57.865105+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/v4.1.1/3/", "url": "https://specifications.onem2m.org/v4.1.1/3/", "title": "3", "content_html": "", "image": null, "date_published": "2024-11-15T16:22:57.848219+00:00", "authors": [], "tags": null}]}
\ No newline at end of file
diff --git a/public/v4.1.1/feed_json_updated.json b/public/v4.1.1/feed_json_updated.json
index dd8bc6a1d68b37dae93e3e57ed00f05b8b2eeff3..ee5691288458e32e05b6268c25663eb66110846c 100644
--- a/public/v4.1.1/feed_json_updated.json
+++ b/public/v4.1.1/feed_json_updated.json
@@ -1 +1 @@
-{"version": "https://jsonfeed.org/version/1", "title": "oneM2M TS-0019", "home_page_url": "https://specifications.onem2m.org/ts-0019/v4.1.1/", "feed_url": "https://specifications.onem2m.org/ts-0019/v4.1.1/feed_json_updated.json", "description": "oneM2M Specifications navigator", "icon": null, "authors": [], "language": "en", "items": [{"id": "https://specifications.onem2m.org/ts-0019/v4.1.1/download/", "url": "https://specifications.onem2m.org/ts-0019/v4.1.1/download/", "title": "Download", "content_html": "<p>Download baseline for TS-0019 version v4.1.1:</p>\n<p>[<img alt=\"Word\" src=\"images/Word.png\">](TS-0019-Abstract_Test_Suite_and_implementation_eXtra_Information_for_Test_v4.1.1.do...</p>", "image": null, "date_modified": "2024-11-14T14:10:06.643528+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v4.1.1/B/", "url": "https://specifications.onem2m.org/ts-0019/v4.1.1/B/", "title": "Annex B (informative): Bibliography", "content_html": "<p>ISO/IEC 9646-6 (1994): \"Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 6: Protocol profile test...</p>", "image": null, "date_modified": "2024-11-14T14:10:06.625279+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v4.1.1/A/", "url": "https://specifications.onem2m.org/ts-0019/v4.1.1/A/", "title": "A", "content_html": "", "image": null, "date_modified": "2024-11-14T14:10:06.604367+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v4.1.1/A.1/", "url": "https://specifications.onem2m.org/ts-0019/v4.1.1/A.1/", "title": "A.1 Electronic annex, zip file with TTCN-3 code", "content_html": "<p>This ATS has been produced using the Testing and Test Control Notation (TTCN) according to ETSI ES 201 873-1 <a href=\"../2.1/#_ref_6\">[6]</a>.</p>\n<p>This test sui...</p>", "image": null, "date_modified": "2024-11-14T14:10:06.582614+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v4.1.1/8/", "url": "https://specifications.onem2m.org/ts-0019/v4.1.1/8/", "title": "8 TTCN-3 Verifications", "content_html": "<p>The principles for Verifying the TTCN-3 test code are given in oneM2M TS-0015 <a href=\"../2.2/#_ref_i.2\">[i.2]</a>.</p>\n<p>All test cases provided with the present...</p>", "image": null, "date_modified": "2024-11-14T14:10:06.565661+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v4.1.1/7/", "url": "https://specifications.onem2m.org/ts-0019/v4.1.1/7/", "title": "7", "content_html": "", "image": null, "date_modified": "2024-11-14T14:10:06.548597+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v4.1.1/7.3/", "url": "https://specifications.onem2m.org/ts-0019/v4.1.1/7.3/", "title": "7.3 IXIT", "content_html": "<p>The following parameters are used by the oneM2M ATS for the correct execution of the test cases.</p>\n<p><strong>Table 7.3-1: oneM2M ATS IXITs</strong><a name=\"table_7.3-1\"></a...</p>", "image": null, "date_modified": "2024-11-14T14:10:06.534495+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v4.1.1/7.2/", "url": "https://specifications.onem2m.org/ts-0019/v4.1.1/7.2/", "title": "7.2 Naming conventions", "content_html": "<h3>7.2.1 General guidelines</h3>\n<p>This test suite follows the naming convention guidelines provided in oneM2M TS-0015 <a href=\"../2.2/#_ref_i.2\">[i.2]</a>.</p>\n<p>The n...</p>", "image": null, "date_modified": "2024-11-14T14:10:06.503891+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v4.1.1/7.1/", "url": "https://specifications.onem2m.org/ts-0019/v4.1.1/7.1/", "title": "7.1 Testing conventions", "content_html": "<h3>7.1.1 Testing states</h3>\n<h4>7.1.1.1 Initial state</h4>\n<p>All test cases start with the function f_preamble_XYZ. This function brings the IUT in an \"initialized...</p>", "image": null, "date_modified": "2024-11-14T14:10:06.470188+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v4.1.1/7.0/", "url": "https://specifications.onem2m.org/ts-0019/v4.1.1/7.0/", "title": "7.0 Introduction", "content_html": "<p>The ATS conventions are intended to give a better understanding of the ATS but they also describe the conventions made for the development of the ATS. These ...</p>", "image": null, "date_modified": "2024-11-14T14:10:06.453660+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v4.1.1/6/", "url": "https://specifications.onem2m.org/ts-0019/v4.1.1/6/", "title": "6 Untestable Test Purposes", "content_html": "<p>Void.</p>", "image": null, "date_modified": "2024-11-14T14:10:06.431376+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v4.1.1/5/", "url": "https://specifications.onem2m.org/ts-0019/v4.1.1/5/", "title": "5", "content_html": "", "image": null, "date_modified": "2024-11-14T14:10:06.416875+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v4.1.1/5.6/", "url": "https://specifications.onem2m.org/ts-0019/v4.1.1/5.6/", "title": "5.6 Test strategy", "content_html": "<p>This clause introduces the test strategy being used for the TTCN-3 test cases. The chosen strategy permits to have a clear structure of the code that facilit...</p>", "image": null, "date_modified": "2024-11-14T14:10:06.402577+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v4.1.1/5.5/", "url": "https://specifications.onem2m.org/ts-0019/v4.1.1/5.5/", "title": "5.5 Test components", "content_html": "<h3>5.5.1 Tester</h3>\n<p>The Tester test component includes a set of ports, timers and variables that are common to the other defined components which are described ...</p>", "image": null, "date_modified": "2024-11-14T14:10:06.384342+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v4.1.1/5.4/", "url": "https://specifications.onem2m.org/ts-0019/v4.1.1/5.4/", "title": "5.4 Ports and ASPs (Abstract Services Primitives)", "content_html": "<h3>5.4.0 Introduction</h3>\n<p>The oneM2M ATS implements the following ports:</p>\n<ul>\n<li>The mcaPort and mcaPortIn</li>\n<li>The mccPort and mccPortIn</li>\n<li>The acPort</li>\n<li>The utPort</li>\n<li>...</li>\n</ul>", "image": null, "date_modified": "2024-11-14T14:10:06.349761+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v4.1.1/5.3/", "url": "https://specifications.onem2m.org/ts-0019/v4.1.1/5.3/", "title": "5.3 Test architecture", "content_html": "<p>The approach for the implementation of an Abstract Protocol Tester selected in oneM2M follows the recommendation of the oneM2M Testing Framework oneM2M TS-00...</p>", "image": null, "date_modified": "2024-11-14T14:10:06.293650+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v4.1.1/5.2/", "url": "https://specifications.onem2m.org/ts-0019/v4.1.1/5.2/", "title": "5.2 Test Configuration", "content_html": "<h3>5.2.1 AE Test Configuration</h3>\n<p>Test configurations are defined to test different entities such as CSE and AE, etc.</p>\n<p>Figure 5.2.1-1 shows a AE test configura...</p>", "image": null, "date_modified": "2024-11-14T14:10:06.265115+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v4.1.1/5.1/", "url": "https://specifications.onem2m.org/ts-0019/v4.1.1/5.1/", "title": "5.1 Abstract protocol tester", "content_html": "<p>An abstract protocol tester (APT) is a process that provides behaviours for testing an IUT by emulating a peer IUT at the same layer, and enabling to address...</p>", "image": null, "date_modified": "2024-11-14T14:10:06.247774+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v4.1.1/4/", "url": "https://specifications.onem2m.org/ts-0019/v4.1.1/4/", "title": "4 Conventions", "content_html": "<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 Rule...</p>", "image": null, "date_modified": "2024-11-14T14:10:06.232123+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/ts-0019/v4.1.1/3/", "url": "https://specifications.onem2m.org/ts-0019/v4.1.1/3/", "title": "3", "content_html": "", "image": null, "date_modified": "2024-11-14T14:10:06.217932+00:00", "authors": [], "tags": null}]}
\ No newline at end of file
+{"version": "https://jsonfeed.org/version/1", "title": "oneM2M TS-0019", "home_page_url": "https://specifications.onem2m.org/v4.1.1/", "feed_url": "https://specifications.onem2m.org/v4.1.1/feed_json_updated.json", "description": "oneM2M Specifications navigator", "icon": null, "authors": [], "language": "en", "items": [{"id": "https://specifications.onem2m.org/v4.1.1/download/", "url": "https://specifications.onem2m.org/v4.1.1/download/", "title": "Download", "content_html": "<p>Download baseline for TS-0019 version v4.1.1:</p>\n<p>[<img alt=\"Word\" src=\"images/Word.png\">](TS-0019-Abstract_Test_Suite_and_implementation_eXtra_Information_for_Test_v4.1.1.do...</p>", "image": null, "date_modified": "2024-11-15T16:22:58.316265+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/v4.1.1/B/", "url": "https://specifications.onem2m.org/v4.1.1/B/", "title": "Annex B (informative): Bibliography", "content_html": "<p>ISO/IEC 9646-6 (1994): \"Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 6: Protocol profile test...</p>", "image": null, "date_modified": "2024-11-15T16:22:58.298672+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/v4.1.1/A/", "url": "https://specifications.onem2m.org/v4.1.1/A/", "title": "A", "content_html": "", "image": null, "date_modified": "2024-11-15T16:22:58.284595+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/v4.1.1/A.1/", "url": "https://specifications.onem2m.org/v4.1.1/A.1/", "title": "A.1 Electronic annex, zip file with TTCN-3 code", "content_html": "<p>This ATS has been produced using the Testing and Test Control Notation (TTCN) according to ETSI ES 201 873-1 <a href=\"../2.1/#_ref_6\">[6]</a>.</p>\n<p>This test sui...</p>", "image": null, "date_modified": "2024-11-15T16:22:58.269659+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/v4.1.1/8/", "url": "https://specifications.onem2m.org/v4.1.1/8/", "title": "8 TTCN-3 Verifications", "content_html": "<p>The principles for Verifying the TTCN-3 test code are given in oneM2M TS-0015 <a href=\"../2.2/#_ref_i.2\">[i.2]</a>.</p>\n<p>All test cases provided with the present...</p>", "image": null, "date_modified": "2024-11-15T16:22:58.249611+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/v4.1.1/7/", "url": "https://specifications.onem2m.org/v4.1.1/7/", "title": "7", "content_html": "", "image": null, "date_modified": "2024-11-15T16:22:58.226447+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/v4.1.1/7.3/", "url": "https://specifications.onem2m.org/v4.1.1/7.3/", "title": "7.3 IXIT", "content_html": "<p>The following parameters are used by the oneM2M ATS for the correct execution of the test cases.</p>\n<p><strong>Table 7.3-1: oneM2M ATS IXITs</strong><a name=\"table_7.3-1\"></a...</p>", "image": null, "date_modified": "2024-11-15T16:22:58.211238+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/v4.1.1/7.2/", "url": "https://specifications.onem2m.org/v4.1.1/7.2/", "title": "7.2 Naming conventions", "content_html": "<h3>7.2.1 General guidelines</h3>\n<p>This test suite follows the naming convention guidelines provided in oneM2M TS-0015 <a href=\"../2.2/#_ref_i.2\">[i.2]</a>.</p>\n<p>The n...</p>", "image": null, "date_modified": "2024-11-15T16:22:58.178800+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/v4.1.1/7.1/", "url": "https://specifications.onem2m.org/v4.1.1/7.1/", "title": "7.1 Testing conventions", "content_html": "<h3>7.1.1 Testing states</h3>\n<h4>7.1.1.1 Initial state</h4>\n<p>All test cases start with the function f_preamble_XYZ. This function brings the IUT in an \"initialized...</p>", "image": null, "date_modified": "2024-11-15T16:22:58.144602+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/v4.1.1/7.0/", "url": "https://specifications.onem2m.org/v4.1.1/7.0/", "title": "7.0 Introduction", "content_html": "<p>The ATS conventions are intended to give a better understanding of the ATS but they also describe the conventions made for the development of the ATS. These ...</p>", "image": null, "date_modified": "2024-11-15T16:22:58.128530+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/v4.1.1/6/", "url": "https://specifications.onem2m.org/v4.1.1/6/", "title": "6 Untestable Test Purposes", "content_html": "<p>Void.</p>", "image": null, "date_modified": "2024-11-15T16:22:58.112554+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/v4.1.1/5/", "url": "https://specifications.onem2m.org/v4.1.1/5/", "title": "5", "content_html": "", "image": null, "date_modified": "2024-11-15T16:22:58.095845+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/v4.1.1/5.6/", "url": "https://specifications.onem2m.org/v4.1.1/5.6/", "title": "5.6 Test strategy", "content_html": "<p>This clause introduces the test strategy being used for the TTCN-3 test cases. The chosen strategy permits to have a clear structure of the code that facilit...</p>", "image": null, "date_modified": "2024-11-15T16:22:58.078117+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/v4.1.1/5.5/", "url": "https://specifications.onem2m.org/v4.1.1/5.5/", "title": "5.5 Test components", "content_html": "<h3>5.5.1 Tester</h3>\n<p>The Tester test component includes a set of ports, timers and variables that are common to the other defined components which are described ...</p>", "image": null, "date_modified": "2024-11-15T16:22:58.057049+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/v4.1.1/5.4/", "url": "https://specifications.onem2m.org/v4.1.1/5.4/", "title": "5.4 Ports and ASPs (Abstract Services Primitives)", "content_html": "<h3>5.4.0 Introduction</h3>\n<p>The oneM2M ATS implements the following ports:</p>\n<ul>\n<li>The mcaPort and mcaPortIn</li>\n<li>The mccPort and mccPortIn</li>\n<li>The acPort</li>\n<li>The utPort</li>\n<li>...</li>\n</ul>", "image": null, "date_modified": "2024-11-15T16:22:58.020054+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/v4.1.1/5.3/", "url": "https://specifications.onem2m.org/v4.1.1/5.3/", "title": "5.3 Test architecture", "content_html": "<p>The approach for the implementation of an Abstract Protocol Tester selected in oneM2M follows the recommendation of the oneM2M Testing Framework oneM2M TS-00...</p>", "image": null, "date_modified": "2024-11-15T16:22:57.928168+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/v4.1.1/5.2/", "url": "https://specifications.onem2m.org/v4.1.1/5.2/", "title": "5.2 Test Configuration", "content_html": "<h3>5.2.1 AE Test Configuration</h3>\n<p>Test configurations are defined to test different entities such as CSE and AE, etc.</p>\n<p>Figure 5.2.1-1 shows a AE test configura...</p>", "image": null, "date_modified": "2024-11-15T16:22:57.904964+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/v4.1.1/5.1/", "url": "https://specifications.onem2m.org/v4.1.1/5.1/", "title": "5.1 Abstract protocol tester", "content_html": "<p>An abstract protocol tester (APT) is a process that provides behaviours for testing an IUT by emulating a peer IUT at the same layer, and enabling to address...</p>", "image": null, "date_modified": "2024-11-15T16:22:57.882300+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/v4.1.1/4/", "url": "https://specifications.onem2m.org/v4.1.1/4/", "title": "4 Conventions", "content_html": "<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 Rule...</p>", "image": null, "date_modified": "2024-11-15T16:22:57.865121+00:00", "authors": [], "tags": null}, {"id": "https://specifications.onem2m.org/v4.1.1/3/", "url": "https://specifications.onem2m.org/v4.1.1/3/", "title": "3", "content_html": "", "image": null, "date_modified": "2024-11-15T16:22:57.848234+00:00", "authors": [], "tags": null}]}
\ No newline at end of file
diff --git a/public/v4.1.1/feed_rss_created.xml b/public/v4.1.1/feed_rss_created.xml
index c82813e399fe8e9ec90cb80b16e0ee72f3671169..a0b16fae1e4888f02a7e97681d206fd871096d1d 100644
--- a/public/v4.1.1/feed_rss_created.xml
+++ b/public/v4.1.1/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 TS-0019</title><description>oneM2M Specifications navigator</description><link>https://specifications.onem2m.org/ts-0019/v4.1.1/</link><atom:link href="https://specifications.onem2m.org/ts-0019/v4.1.1/feed_rss_created.xml" rel="self" type="application/rss+xml" /><docs>https://git.onem2m.org/specifications/ts/ts-0019.git</docs><language>en</language> <pubDate>Thu, 14 Nov 2024 14:10:05 -0000</pubDate> <lastBuildDate>Thu, 14 Nov 2024 14:10:05 -0000</lastBuildDate> <ttl>1440</ttl> <generator>MkDocs RSS plugin - v1.16.0</generator> <item> <title>Download</title> <description><p>Download baseline for TS-0019 version v4.1.1:</p><p>[<img alt="Word" src="images/Word.png">](TS-0019-Abstract_Test_Suite_and_implementation_eXtra_Information_for_Test_v4.1.1.do...</p></description><link>https://specifications.onem2m.org/ts-0019/v4.1.1/download/</link> <pubDate>Thu, 14 Nov 2024 14:10:06 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v4.1.1/feed_rss_created.xml">oneM2M TS-0019</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v4.1.1/download/</guid> </item> <item> <title>Annex B (informative): Bibliography</title> <description><p>ISO/IEC 9646-6 (1994): "Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 6: Protocol profile test...</p></description><link>https://specifications.onem2m.org/ts-0019/v4.1.1/B/</link> <pubDate>Thu, 14 Nov 2024 14:10:06 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v4.1.1/feed_rss_created.xml">oneM2M TS-0019</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v4.1.1/B/</guid> </item> <item> <title>A</title> <description></description><link>https://specifications.onem2m.org/ts-0019/v4.1.1/A/</link> <pubDate>Thu, 14 Nov 2024 14:10:06 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v4.1.1/feed_rss_created.xml">oneM2M TS-0019</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v4.1.1/A/</guid> </item> <item> <title>A.1 Electronic annex, zip file with TTCN-3 code</title> <description><p>This ATS has been produced using the Testing and Test Control Notation (TTCN) according to ETSI ES 201 873-1 <a href="../2.1/#_ref_6">[6]</a>.</p><p>This test sui...</p></description><link>https://specifications.onem2m.org/ts-0019/v4.1.1/A.1/</link> <pubDate>Thu, 14 Nov 2024 14:10:06 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v4.1.1/feed_rss_created.xml">oneM2M TS-0019</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v4.1.1/A.1/</guid> </item> <item> <title>8 TTCN-3 Verifications</title> <description><p>The principles for Verifying the TTCN-3 test code are given in oneM2M TS-0015 <a href="../2.2/#_ref_i.2">[i.2]</a>.</p><p>All test cases provided with the present...</p></description><link>https://specifications.onem2m.org/ts-0019/v4.1.1/8/</link> <pubDate>Thu, 14 Nov 2024 14:10:06 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v4.1.1/feed_rss_created.xml">oneM2M TS-0019</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v4.1.1/8/</guid> </item> <item> <title>7</title> <description></description><link>https://specifications.onem2m.org/ts-0019/v4.1.1/7/</link> <pubDate>Thu, 14 Nov 2024 14:10:06 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v4.1.1/feed_rss_created.xml">oneM2M TS-0019</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v4.1.1/7/</guid> </item> <item> <title>7.3 IXIT</title> <description><p>The following parameters are used by the oneM2M ATS for the correct execution of the test cases.</p><p><strong>Table 7.3-1: oneM2M ATS IXITs</strong><a name="table_7.3-1">&lt;/a...</p></description><link>https://specifications.onem2m.org/ts-0019/v4.1.1/7.3/</link> <pubDate>Thu, 14 Nov 2024 14:10:06 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v4.1.1/feed_rss_created.xml">oneM2M TS-0019</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v4.1.1/7.3/</guid> </item> <item> <title>7.2 Naming conventions</title> <description><h3>7.2.1 General guidelines</h3><p>This test suite follows the naming convention guidelines provided in oneM2M TS-0015 <a href="../2.2/#_ref_i.2">[i.2]</a>.</p><p>The n...</p></description><link>https://specifications.onem2m.org/ts-0019/v4.1.1/7.2/</link> <pubDate>Thu, 14 Nov 2024 14:10:06 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v4.1.1/feed_rss_created.xml">oneM2M TS-0019</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v4.1.1/7.2/</guid> </item> <item> <title>7.1 Testing conventions</title> <description><h3>7.1.1 Testing states</h3><h4>7.1.1.1 Initial state</h4><p>All test cases start with the function f_preamble_XYZ. This function brings the IUT in an "initialized...</p></description><link>https://specifications.onem2m.org/ts-0019/v4.1.1/7.1/</link> <pubDate>Thu, 14 Nov 2024 14:10:06 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v4.1.1/feed_rss_created.xml">oneM2M TS-0019</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v4.1.1/7.1/</guid> </item> <item> <title>7.0 Introduction</title> <description><p>The ATS conventions are intended to give a better understanding of the ATS but they also describe the conventions made for the development of the ATS. These ...</p></description><link>https://specifications.onem2m.org/ts-0019/v4.1.1/7.0/</link> <pubDate>Thu, 14 Nov 2024 14:10:06 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v4.1.1/feed_rss_created.xml">oneM2M TS-0019</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v4.1.1/7.0/</guid> </item> <item> <title>6 Untestable Test Purposes</title> <description><p>Void.</p></description><link>https://specifications.onem2m.org/ts-0019/v4.1.1/6/</link> <pubDate>Thu, 14 Nov 2024 14:10:06 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v4.1.1/feed_rss_created.xml">oneM2M TS-0019</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v4.1.1/6/</guid> </item> <item> <title>5</title> <description></description><link>https://specifications.onem2m.org/ts-0019/v4.1.1/5/</link> <pubDate>Thu, 14 Nov 2024 14:10:06 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v4.1.1/feed_rss_created.xml">oneM2M TS-0019</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v4.1.1/5/</guid> </item> <item> <title>5.6 Test strategy</title> <description><p>This clause introduces the test strategy being used for the TTCN-3 test cases. The chosen strategy permits to have a clear structure of the code that facilit...</p></description><link>https://specifications.onem2m.org/ts-0019/v4.1.1/5.6/</link> <pubDate>Thu, 14 Nov 2024 14:10:06 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v4.1.1/feed_rss_created.xml">oneM2M TS-0019</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v4.1.1/5.6/</guid> </item> <item> <title>5.5 Test components</title> <description><h3>5.5.1 Tester</h3><p>The Tester test component includes a set of ports, timers and variables that are common to the other defined components which are described ...</p></description><link>https://specifications.onem2m.org/ts-0019/v4.1.1/5.5/</link> <pubDate>Thu, 14 Nov 2024 14:10:06 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v4.1.1/feed_rss_created.xml">oneM2M TS-0019</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v4.1.1/5.5/</guid> </item> <item> <title>5.4 Ports and ASPs (Abstract Services Primitives)</title> <description><h3>5.4.0 Introduction</h3><p>The oneM2M ATS implements the following ports:</p><ul><li>The mcaPort and mcaPortIn</li><li>The mccPort and mccPortIn</li><li>The acPort</li><li>The utPort</li><li>...</li></ul></description><link>https://specifications.onem2m.org/ts-0019/v4.1.1/5.4/</link> <pubDate>Thu, 14 Nov 2024 14:10:06 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v4.1.1/feed_rss_created.xml">oneM2M TS-0019</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v4.1.1/5.4/</guid> </item> <item> <title>5.3 Test architecture</title> <description><p>The approach for the implementation of an Abstract Protocol Tester selected in oneM2M follows the recommendation of the oneM2M Testing Framework oneM2M TS-00...</p></description><link>https://specifications.onem2m.org/ts-0019/v4.1.1/5.3/</link> <pubDate>Thu, 14 Nov 2024 14:10:06 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v4.1.1/feed_rss_created.xml">oneM2M TS-0019</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v4.1.1/5.3/</guid> </item> <item> <title>5.2 Test Configuration</title> <description><h3>5.2.1 AE Test Configuration</h3><p>Test configurations are defined to test different entities such as CSE and AE, etc.</p><p>Figure 5.2.1-1 shows a AE test configura...</p></description><link>https://specifications.onem2m.org/ts-0019/v4.1.1/5.2/</link> <pubDate>Thu, 14 Nov 2024 14:10:06 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v4.1.1/feed_rss_created.xml">oneM2M TS-0019</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v4.1.1/5.2/</guid> </item> <item> <title>5.1 Abstract protocol tester</title> <description><p>An abstract protocol tester (APT) is a process that provides behaviours for testing an IUT by emulating a peer IUT at the same layer, and enabling to address...</p></description><link>https://specifications.onem2m.org/ts-0019/v4.1.1/5.1/</link> <pubDate>Thu, 14 Nov 2024 14:10:06 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v4.1.1/feed_rss_created.xml">oneM2M TS-0019</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v4.1.1/5.1/</guid> </item> <item> <title>4 Conventions</title> <description><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 Rule...</p></description><link>https://specifications.onem2m.org/ts-0019/v4.1.1/4/</link> <pubDate>Thu, 14 Nov 2024 14:10:06 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v4.1.1/feed_rss_created.xml">oneM2M TS-0019</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v4.1.1/4/</guid> </item> <item> <title>3</title> <description></description><link>https://specifications.onem2m.org/ts-0019/v4.1.1/3/</link> <pubDate>Thu, 14 Nov 2024 14:10:06 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v4.1.1/feed_rss_created.xml">oneM2M TS-0019</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v4.1.1/3/</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 TS-0019</title><description>oneM2M Specifications navigator</description><link>https://specifications.onem2m.org/v4.1.1/</link><atom:link href="https://specifications.onem2m.org/v4.1.1/feed_rss_created.xml" rel="self" type="application/rss+xml" /><docs>https://git.onem2m.org/specifications/ts/ts-0019.git</docs><language>en</language> <pubDate>Fri, 15 Nov 2024 16:22:57 -0000</pubDate> <lastBuildDate>Fri, 15 Nov 2024 16:22:57 -0000</lastBuildDate> <ttl>1440</ttl> <generator>MkDocs RSS plugin - v1.16.0</generator> <item> <title>Download</title> <description><p>Download baseline for TS-0019 version v4.1.1:</p><p>[<img alt="Word" src="images/Word.png">](TS-0019-Abstract_Test_Suite_and_implementation_eXtra_Information_for_Test_v4.1.1.do...</p></description><link>https://specifications.onem2m.org/v4.1.1/download/</link> <pubDate>Fri, 15 Nov 2024 16:22:58 +0000</pubDate><source url="https://specifications.onem2m.org/v4.1.1/feed_rss_created.xml">oneM2M TS-0019</source><guid isPermaLink="true">https://specifications.onem2m.org/v4.1.1/download/</guid> </item> <item> <title>Annex B (informative): Bibliography</title> <description><p>ISO/IEC 9646-6 (1994): "Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 6: Protocol profile test...</p></description><link>https://specifications.onem2m.org/v4.1.1/B/</link> <pubDate>Fri, 15 Nov 2024 16:22:58 +0000</pubDate><source url="https://specifications.onem2m.org/v4.1.1/feed_rss_created.xml">oneM2M TS-0019</source><guid isPermaLink="true">https://specifications.onem2m.org/v4.1.1/B/</guid> </item> <item> <title>A</title> <description></description><link>https://specifications.onem2m.org/v4.1.1/A/</link> <pubDate>Fri, 15 Nov 2024 16:22:58 +0000</pubDate><source url="https://specifications.onem2m.org/v4.1.1/feed_rss_created.xml">oneM2M TS-0019</source><guid isPermaLink="true">https://specifications.onem2m.org/v4.1.1/A/</guid> </item> <item> <title>A.1 Electronic annex, zip file with TTCN-3 code</title> <description><p>This ATS has been produced using the Testing and Test Control Notation (TTCN) according to ETSI ES 201 873-1 <a href="../2.1/#_ref_6">[6]</a>.</p><p>This test sui...</p></description><link>https://specifications.onem2m.org/v4.1.1/A.1/</link> <pubDate>Fri, 15 Nov 2024 16:22:58 +0000</pubDate><source url="https://specifications.onem2m.org/v4.1.1/feed_rss_created.xml">oneM2M TS-0019</source><guid isPermaLink="true">https://specifications.onem2m.org/v4.1.1/A.1/</guid> </item> <item> <title>8 TTCN-3 Verifications</title> <description><p>The principles for Verifying the TTCN-3 test code are given in oneM2M TS-0015 <a href="../2.2/#_ref_i.2">[i.2]</a>.</p><p>All test cases provided with the present...</p></description><link>https://specifications.onem2m.org/v4.1.1/8/</link> <pubDate>Fri, 15 Nov 2024 16:22:58 +0000</pubDate><source url="https://specifications.onem2m.org/v4.1.1/feed_rss_created.xml">oneM2M TS-0019</source><guid isPermaLink="true">https://specifications.onem2m.org/v4.1.1/8/</guid> </item> <item> <title>7</title> <description></description><link>https://specifications.onem2m.org/v4.1.1/7/</link> <pubDate>Fri, 15 Nov 2024 16:22:58 +0000</pubDate><source url="https://specifications.onem2m.org/v4.1.1/feed_rss_created.xml">oneM2M TS-0019</source><guid isPermaLink="true">https://specifications.onem2m.org/v4.1.1/7/</guid> </item> <item> <title>7.3 IXIT</title> <description><p>The following parameters are used by the oneM2M ATS for the correct execution of the test cases.</p><p><strong>Table 7.3-1: oneM2M ATS IXITs</strong><a name="table_7.3-1">&lt;/a...</p></description><link>https://specifications.onem2m.org/v4.1.1/7.3/</link> <pubDate>Fri, 15 Nov 2024 16:22:58 +0000</pubDate><source url="https://specifications.onem2m.org/v4.1.1/feed_rss_created.xml">oneM2M TS-0019</source><guid isPermaLink="true">https://specifications.onem2m.org/v4.1.1/7.3/</guid> </item> <item> <title>7.2 Naming conventions</title> <description><h3>7.2.1 General guidelines</h3><p>This test suite follows the naming convention guidelines provided in oneM2M TS-0015 <a href="../2.2/#_ref_i.2">[i.2]</a>.</p><p>The n...</p></description><link>https://specifications.onem2m.org/v4.1.1/7.2/</link> <pubDate>Fri, 15 Nov 2024 16:22:58 +0000</pubDate><source url="https://specifications.onem2m.org/v4.1.1/feed_rss_created.xml">oneM2M TS-0019</source><guid isPermaLink="true">https://specifications.onem2m.org/v4.1.1/7.2/</guid> </item> <item> <title>7.1 Testing conventions</title> <description><h3>7.1.1 Testing states</h3><h4>7.1.1.1 Initial state</h4><p>All test cases start with the function f_preamble_XYZ. This function brings the IUT in an "initialized...</p></description><link>https://specifications.onem2m.org/v4.1.1/7.1/</link> <pubDate>Fri, 15 Nov 2024 16:22:58 +0000</pubDate><source url="https://specifications.onem2m.org/v4.1.1/feed_rss_created.xml">oneM2M TS-0019</source><guid isPermaLink="true">https://specifications.onem2m.org/v4.1.1/7.1/</guid> </item> <item> <title>7.0 Introduction</title> <description><p>The ATS conventions are intended to give a better understanding of the ATS but they also describe the conventions made for the development of the ATS. These ...</p></description><link>https://specifications.onem2m.org/v4.1.1/7.0/</link> <pubDate>Fri, 15 Nov 2024 16:22:58 +0000</pubDate><source url="https://specifications.onem2m.org/v4.1.1/feed_rss_created.xml">oneM2M TS-0019</source><guid isPermaLink="true">https://specifications.onem2m.org/v4.1.1/7.0/</guid> </item> <item> <title>6 Untestable Test Purposes</title> <description><p>Void.</p></description><link>https://specifications.onem2m.org/v4.1.1/6/</link> <pubDate>Fri, 15 Nov 2024 16:22:58 +0000</pubDate><source url="https://specifications.onem2m.org/v4.1.1/feed_rss_created.xml">oneM2M TS-0019</source><guid isPermaLink="true">https://specifications.onem2m.org/v4.1.1/6/</guid> </item> <item> <title>5</title> <description></description><link>https://specifications.onem2m.org/v4.1.1/5/</link> <pubDate>Fri, 15 Nov 2024 16:22:58 +0000</pubDate><source url="https://specifications.onem2m.org/v4.1.1/feed_rss_created.xml">oneM2M TS-0019</source><guid isPermaLink="true">https://specifications.onem2m.org/v4.1.1/5/</guid> </item> <item> <title>5.6 Test strategy</title> <description><p>This clause introduces the test strategy being used for the TTCN-3 test cases. The chosen strategy permits to have a clear structure of the code that facilit...</p></description><link>https://specifications.onem2m.org/v4.1.1/5.6/</link> <pubDate>Fri, 15 Nov 2024 16:22:58 +0000</pubDate><source url="https://specifications.onem2m.org/v4.1.1/feed_rss_created.xml">oneM2M TS-0019</source><guid isPermaLink="true">https://specifications.onem2m.org/v4.1.1/5.6/</guid> </item> <item> <title>5.5 Test components</title> <description><h3>5.5.1 Tester</h3><p>The Tester test component includes a set of ports, timers and variables that are common to the other defined components which are described ...</p></description><link>https://specifications.onem2m.org/v4.1.1/5.5/</link> <pubDate>Fri, 15 Nov 2024 16:22:58 +0000</pubDate><source url="https://specifications.onem2m.org/v4.1.1/feed_rss_created.xml">oneM2M TS-0019</source><guid isPermaLink="true">https://specifications.onem2m.org/v4.1.1/5.5/</guid> </item> <item> <title>5.4 Ports and ASPs (Abstract Services Primitives)</title> <description><h3>5.4.0 Introduction</h3><p>The oneM2M ATS implements the following ports:</p><ul><li>The mcaPort and mcaPortIn</li><li>The mccPort and mccPortIn</li><li>The acPort</li><li>The utPort</li><li>...</li></ul></description><link>https://specifications.onem2m.org/v4.1.1/5.4/</link> <pubDate>Fri, 15 Nov 2024 16:22:58 +0000</pubDate><source url="https://specifications.onem2m.org/v4.1.1/feed_rss_created.xml">oneM2M TS-0019</source><guid isPermaLink="true">https://specifications.onem2m.org/v4.1.1/5.4/</guid> </item> <item> <title>5.3 Test architecture</title> <description><p>The approach for the implementation of an Abstract Protocol Tester selected in oneM2M follows the recommendation of the oneM2M Testing Framework oneM2M TS-00...</p></description><link>https://specifications.onem2m.org/v4.1.1/5.3/</link> <pubDate>Fri, 15 Nov 2024 16:22:57 +0000</pubDate><source url="https://specifications.onem2m.org/v4.1.1/feed_rss_created.xml">oneM2M TS-0019</source><guid isPermaLink="true">https://specifications.onem2m.org/v4.1.1/5.3/</guid> </item> <item> <title>5.2 Test Configuration</title> <description><h3>5.2.1 AE Test Configuration</h3><p>Test configurations are defined to test different entities such as CSE and AE, etc.</p><p>Figure 5.2.1-1 shows a AE test configura...</p></description><link>https://specifications.onem2m.org/v4.1.1/5.2/</link> <pubDate>Fri, 15 Nov 2024 16:22:57 +0000</pubDate><source url="https://specifications.onem2m.org/v4.1.1/feed_rss_created.xml">oneM2M TS-0019</source><guid isPermaLink="true">https://specifications.onem2m.org/v4.1.1/5.2/</guid> </item> <item> <title>5.1 Abstract protocol tester</title> <description><p>An abstract protocol tester (APT) is a process that provides behaviours for testing an IUT by emulating a peer IUT at the same layer, and enabling to address...</p></description><link>https://specifications.onem2m.org/v4.1.1/5.1/</link> <pubDate>Fri, 15 Nov 2024 16:22:57 +0000</pubDate><source url="https://specifications.onem2m.org/v4.1.1/feed_rss_created.xml">oneM2M TS-0019</source><guid isPermaLink="true">https://specifications.onem2m.org/v4.1.1/5.1/</guid> </item> <item> <title>4 Conventions</title> <description><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 Rule...</p></description><link>https://specifications.onem2m.org/v4.1.1/4/</link> <pubDate>Fri, 15 Nov 2024 16:22:57 +0000</pubDate><source url="https://specifications.onem2m.org/v4.1.1/feed_rss_created.xml">oneM2M TS-0019</source><guid isPermaLink="true">https://specifications.onem2m.org/v4.1.1/4/</guid> </item> <item> <title>3</title> <description></description><link>https://specifications.onem2m.org/v4.1.1/3/</link> <pubDate>Fri, 15 Nov 2024 16:22:57 +0000</pubDate><source url="https://specifications.onem2m.org/v4.1.1/feed_rss_created.xml">oneM2M TS-0019</source><guid isPermaLink="true">https://specifications.onem2m.org/v4.1.1/3/</guid> </item> </channel></rss>
\ No newline at end of file
diff --git a/public/v4.1.1/feed_rss_updated.xml b/public/v4.1.1/feed_rss_updated.xml
index b77c39d167fb6ccc999cb541e43fc0c1cfe9ed54..225df076e9d54d6ebdee5d6bc9f8dfa0a7e15155 100644
--- a/public/v4.1.1/feed_rss_updated.xml
+++ b/public/v4.1.1/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 TS-0019</title><description>oneM2M Specifications navigator</description><link>https://specifications.onem2m.org/ts-0019/v4.1.1/</link><atom:link href="https://specifications.onem2m.org/ts-0019/v4.1.1/feed_rss_updated.xml" rel="self" type="application/rss+xml" /><docs>https://git.onem2m.org/specifications/ts/ts-0019.git</docs><language>en</language> <pubDate>Thu, 14 Nov 2024 14:10:05 -0000</pubDate> <lastBuildDate>Thu, 14 Nov 2024 14:10:05 -0000</lastBuildDate> <ttl>1440</ttl> <generator>MkDocs RSS plugin - v1.16.0</generator> <item> <title>Download</title> <description><p>Download baseline for TS-0019 version v4.1.1:</p><p>[<img alt="Word" src="images/Word.png">](TS-0019-Abstract_Test_Suite_and_implementation_eXtra_Information_for_Test_v4.1.1.do...</p></description><link>https://specifications.onem2m.org/ts-0019/v4.1.1/download/</link> <pubDate>Thu, 14 Nov 2024 14:10:06 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v4.1.1/feed_rss_updated.xml">oneM2M TS-0019</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v4.1.1/download/</guid> </item> <item> <title>Annex B (informative): Bibliography</title> <description><p>ISO/IEC 9646-6 (1994): "Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 6: Protocol profile test...</p></description><link>https://specifications.onem2m.org/ts-0019/v4.1.1/B/</link> <pubDate>Thu, 14 Nov 2024 14:10:06 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v4.1.1/feed_rss_updated.xml">oneM2M TS-0019</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v4.1.1/B/</guid> </item> <item> <title>A</title> <description></description><link>https://specifications.onem2m.org/ts-0019/v4.1.1/A/</link> <pubDate>Thu, 14 Nov 2024 14:10:06 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v4.1.1/feed_rss_updated.xml">oneM2M TS-0019</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v4.1.1/A/</guid> </item> <item> <title>A.1 Electronic annex, zip file with TTCN-3 code</title> <description><p>This ATS has been produced using the Testing and Test Control Notation (TTCN) according to ETSI ES 201 873-1 <a href="../2.1/#_ref_6">[6]</a>.</p><p>This test sui...</p></description><link>https://specifications.onem2m.org/ts-0019/v4.1.1/A.1/</link> <pubDate>Thu, 14 Nov 2024 14:10:06 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v4.1.1/feed_rss_updated.xml">oneM2M TS-0019</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v4.1.1/A.1/</guid> </item> <item> <title>8 TTCN-3 Verifications</title> <description><p>The principles for Verifying the TTCN-3 test code are given in oneM2M TS-0015 <a href="../2.2/#_ref_i.2">[i.2]</a>.</p><p>All test cases provided with the present...</p></description><link>https://specifications.onem2m.org/ts-0019/v4.1.1/8/</link> <pubDate>Thu, 14 Nov 2024 14:10:06 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v4.1.1/feed_rss_updated.xml">oneM2M TS-0019</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v4.1.1/8/</guid> </item> <item> <title>7</title> <description></description><link>https://specifications.onem2m.org/ts-0019/v4.1.1/7/</link> <pubDate>Thu, 14 Nov 2024 14:10:06 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v4.1.1/feed_rss_updated.xml">oneM2M TS-0019</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v4.1.1/7/</guid> </item> <item> <title>7.3 IXIT</title> <description><p>The following parameters are used by the oneM2M ATS for the correct execution of the test cases.</p><p><strong>Table 7.3-1: oneM2M ATS IXITs</strong><a name="table_7.3-1">&lt;/a...</p></description><link>https://specifications.onem2m.org/ts-0019/v4.1.1/7.3/</link> <pubDate>Thu, 14 Nov 2024 14:10:06 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v4.1.1/feed_rss_updated.xml">oneM2M TS-0019</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v4.1.1/7.3/</guid> </item> <item> <title>7.2 Naming conventions</title> <description><h3>7.2.1 General guidelines</h3><p>This test suite follows the naming convention guidelines provided in oneM2M TS-0015 <a href="../2.2/#_ref_i.2">[i.2]</a>.</p><p>The n...</p></description><link>https://specifications.onem2m.org/ts-0019/v4.1.1/7.2/</link> <pubDate>Thu, 14 Nov 2024 14:10:06 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v4.1.1/feed_rss_updated.xml">oneM2M TS-0019</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v4.1.1/7.2/</guid> </item> <item> <title>7.1 Testing conventions</title> <description><h3>7.1.1 Testing states</h3><h4>7.1.1.1 Initial state</h4><p>All test cases start with the function f_preamble_XYZ. This function brings the IUT in an "initialized...</p></description><link>https://specifications.onem2m.org/ts-0019/v4.1.1/7.1/</link> <pubDate>Thu, 14 Nov 2024 14:10:06 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v4.1.1/feed_rss_updated.xml">oneM2M TS-0019</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v4.1.1/7.1/</guid> </item> <item> <title>7.0 Introduction</title> <description><p>The ATS conventions are intended to give a better understanding of the ATS but they also describe the conventions made for the development of the ATS. These ...</p></description><link>https://specifications.onem2m.org/ts-0019/v4.1.1/7.0/</link> <pubDate>Thu, 14 Nov 2024 14:10:06 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v4.1.1/feed_rss_updated.xml">oneM2M TS-0019</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v4.1.1/7.0/</guid> </item> <item> <title>6 Untestable Test Purposes</title> <description><p>Void.</p></description><link>https://specifications.onem2m.org/ts-0019/v4.1.1/6/</link> <pubDate>Thu, 14 Nov 2024 14:10:06 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v4.1.1/feed_rss_updated.xml">oneM2M TS-0019</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v4.1.1/6/</guid> </item> <item> <title>5</title> <description></description><link>https://specifications.onem2m.org/ts-0019/v4.1.1/5/</link> <pubDate>Thu, 14 Nov 2024 14:10:06 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v4.1.1/feed_rss_updated.xml">oneM2M TS-0019</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v4.1.1/5/</guid> </item> <item> <title>5.6 Test strategy</title> <description><p>This clause introduces the test strategy being used for the TTCN-3 test cases. The chosen strategy permits to have a clear structure of the code that facilit...</p></description><link>https://specifications.onem2m.org/ts-0019/v4.1.1/5.6/</link> <pubDate>Thu, 14 Nov 2024 14:10:06 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v4.1.1/feed_rss_updated.xml">oneM2M TS-0019</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v4.1.1/5.6/</guid> </item> <item> <title>5.5 Test components</title> <description><h3>5.5.1 Tester</h3><p>The Tester test component includes a set of ports, timers and variables that are common to the other defined components which are described ...</p></description><link>https://specifications.onem2m.org/ts-0019/v4.1.1/5.5/</link> <pubDate>Thu, 14 Nov 2024 14:10:06 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v4.1.1/feed_rss_updated.xml">oneM2M TS-0019</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v4.1.1/5.5/</guid> </item> <item> <title>5.4 Ports and ASPs (Abstract Services Primitives)</title> <description><h3>5.4.0 Introduction</h3><p>The oneM2M ATS implements the following ports:</p><ul><li>The mcaPort and mcaPortIn</li><li>The mccPort and mccPortIn</li><li>The acPort</li><li>The utPort</li><li>...</li></ul></description><link>https://specifications.onem2m.org/ts-0019/v4.1.1/5.4/</link> <pubDate>Thu, 14 Nov 2024 14:10:06 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v4.1.1/feed_rss_updated.xml">oneM2M TS-0019</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v4.1.1/5.4/</guid> </item> <item> <title>5.3 Test architecture</title> <description><p>The approach for the implementation of an Abstract Protocol Tester selected in oneM2M follows the recommendation of the oneM2M Testing Framework oneM2M TS-00...</p></description><link>https://specifications.onem2m.org/ts-0019/v4.1.1/5.3/</link> <pubDate>Thu, 14 Nov 2024 14:10:06 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v4.1.1/feed_rss_updated.xml">oneM2M TS-0019</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v4.1.1/5.3/</guid> </item> <item> <title>5.2 Test Configuration</title> <description><h3>5.2.1 AE Test Configuration</h3><p>Test configurations are defined to test different entities such as CSE and AE, etc.</p><p>Figure 5.2.1-1 shows a AE test configura...</p></description><link>https://specifications.onem2m.org/ts-0019/v4.1.1/5.2/</link> <pubDate>Thu, 14 Nov 2024 14:10:06 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v4.1.1/feed_rss_updated.xml">oneM2M TS-0019</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v4.1.1/5.2/</guid> </item> <item> <title>5.1 Abstract protocol tester</title> <description><p>An abstract protocol tester (APT) is a process that provides behaviours for testing an IUT by emulating a peer IUT at the same layer, and enabling to address...</p></description><link>https://specifications.onem2m.org/ts-0019/v4.1.1/5.1/</link> <pubDate>Thu, 14 Nov 2024 14:10:06 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v4.1.1/feed_rss_updated.xml">oneM2M TS-0019</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v4.1.1/5.1/</guid> </item> <item> <title>4 Conventions</title> <description><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 Rule...</p></description><link>https://specifications.onem2m.org/ts-0019/v4.1.1/4/</link> <pubDate>Thu, 14 Nov 2024 14:10:06 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v4.1.1/feed_rss_updated.xml">oneM2M TS-0019</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v4.1.1/4/</guid> </item> <item> <title>3</title> <description></description><link>https://specifications.onem2m.org/ts-0019/v4.1.1/3/</link> <pubDate>Thu, 14 Nov 2024 14:10:06 +0000</pubDate><source url="https://specifications.onem2m.org/ts-0019/v4.1.1/feed_rss_updated.xml">oneM2M TS-0019</source><guid isPermaLink="true">https://specifications.onem2m.org/ts-0019/v4.1.1/3/</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 TS-0019</title><description>oneM2M Specifications navigator</description><link>https://specifications.onem2m.org/v4.1.1/</link><atom:link href="https://specifications.onem2m.org/v4.1.1/feed_rss_updated.xml" rel="self" type="application/rss+xml" /><docs>https://git.onem2m.org/specifications/ts/ts-0019.git</docs><language>en</language> <pubDate>Fri, 15 Nov 2024 16:22:57 -0000</pubDate> <lastBuildDate>Fri, 15 Nov 2024 16:22:57 -0000</lastBuildDate> <ttl>1440</ttl> <generator>MkDocs RSS plugin - v1.16.0</generator> <item> <title>Download</title> <description><p>Download baseline for TS-0019 version v4.1.1:</p><p>[<img alt="Word" src="images/Word.png">](TS-0019-Abstract_Test_Suite_and_implementation_eXtra_Information_for_Test_v4.1.1.do...</p></description><link>https://specifications.onem2m.org/v4.1.1/download/</link> <pubDate>Fri, 15 Nov 2024 16:22:58 +0000</pubDate><source url="https://specifications.onem2m.org/v4.1.1/feed_rss_updated.xml">oneM2M TS-0019</source><guid isPermaLink="true">https://specifications.onem2m.org/v4.1.1/download/</guid> </item> <item> <title>Annex B (informative): Bibliography</title> <description><p>ISO/IEC 9646-6 (1994): "Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 6: Protocol profile test...</p></description><link>https://specifications.onem2m.org/v4.1.1/B/</link> <pubDate>Fri, 15 Nov 2024 16:22:58 +0000</pubDate><source url="https://specifications.onem2m.org/v4.1.1/feed_rss_updated.xml">oneM2M TS-0019</source><guid isPermaLink="true">https://specifications.onem2m.org/v4.1.1/B/</guid> </item> <item> <title>A</title> <description></description><link>https://specifications.onem2m.org/v4.1.1/A/</link> <pubDate>Fri, 15 Nov 2024 16:22:58 +0000</pubDate><source url="https://specifications.onem2m.org/v4.1.1/feed_rss_updated.xml">oneM2M TS-0019</source><guid isPermaLink="true">https://specifications.onem2m.org/v4.1.1/A/</guid> </item> <item> <title>A.1 Electronic annex, zip file with TTCN-3 code</title> <description><p>This ATS has been produced using the Testing and Test Control Notation (TTCN) according to ETSI ES 201 873-1 <a href="../2.1/#_ref_6">[6]</a>.</p><p>This test sui...</p></description><link>https://specifications.onem2m.org/v4.1.1/A.1/</link> <pubDate>Fri, 15 Nov 2024 16:22:58 +0000</pubDate><source url="https://specifications.onem2m.org/v4.1.1/feed_rss_updated.xml">oneM2M TS-0019</source><guid isPermaLink="true">https://specifications.onem2m.org/v4.1.1/A.1/</guid> </item> <item> <title>8 TTCN-3 Verifications</title> <description><p>The principles for Verifying the TTCN-3 test code are given in oneM2M TS-0015 <a href="../2.2/#_ref_i.2">[i.2]</a>.</p><p>All test cases provided with the present...</p></description><link>https://specifications.onem2m.org/v4.1.1/8/</link> <pubDate>Fri, 15 Nov 2024 16:22:58 +0000</pubDate><source url="https://specifications.onem2m.org/v4.1.1/feed_rss_updated.xml">oneM2M TS-0019</source><guid isPermaLink="true">https://specifications.onem2m.org/v4.1.1/8/</guid> </item> <item> <title>7</title> <description></description><link>https://specifications.onem2m.org/v4.1.1/7/</link> <pubDate>Fri, 15 Nov 2024 16:22:58 +0000</pubDate><source url="https://specifications.onem2m.org/v4.1.1/feed_rss_updated.xml">oneM2M TS-0019</source><guid isPermaLink="true">https://specifications.onem2m.org/v4.1.1/7/</guid> </item> <item> <title>7.3 IXIT</title> <description><p>The following parameters are used by the oneM2M ATS for the correct execution of the test cases.</p><p><strong>Table 7.3-1: oneM2M ATS IXITs</strong><a name="table_7.3-1">&lt;/a...</p></description><link>https://specifications.onem2m.org/v4.1.1/7.3/</link> <pubDate>Fri, 15 Nov 2024 16:22:58 +0000</pubDate><source url="https://specifications.onem2m.org/v4.1.1/feed_rss_updated.xml">oneM2M TS-0019</source><guid isPermaLink="true">https://specifications.onem2m.org/v4.1.1/7.3/</guid> </item> <item> <title>7.2 Naming conventions</title> <description><h3>7.2.1 General guidelines</h3><p>This test suite follows the naming convention guidelines provided in oneM2M TS-0015 <a href="../2.2/#_ref_i.2">[i.2]</a>.</p><p>The n...</p></description><link>https://specifications.onem2m.org/v4.1.1/7.2/</link> <pubDate>Fri, 15 Nov 2024 16:22:58 +0000</pubDate><source url="https://specifications.onem2m.org/v4.1.1/feed_rss_updated.xml">oneM2M TS-0019</source><guid isPermaLink="true">https://specifications.onem2m.org/v4.1.1/7.2/</guid> </item> <item> <title>7.1 Testing conventions</title> <description><h3>7.1.1 Testing states</h3><h4>7.1.1.1 Initial state</h4><p>All test cases start with the function f_preamble_XYZ. This function brings the IUT in an "initialized...</p></description><link>https://specifications.onem2m.org/v4.1.1/7.1/</link> <pubDate>Fri, 15 Nov 2024 16:22:58 +0000</pubDate><source url="https://specifications.onem2m.org/v4.1.1/feed_rss_updated.xml">oneM2M TS-0019</source><guid isPermaLink="true">https://specifications.onem2m.org/v4.1.1/7.1/</guid> </item> <item> <title>7.0 Introduction</title> <description><p>The ATS conventions are intended to give a better understanding of the ATS but they also describe the conventions made for the development of the ATS. These ...</p></description><link>https://specifications.onem2m.org/v4.1.1/7.0/</link> <pubDate>Fri, 15 Nov 2024 16:22:58 +0000</pubDate><source url="https://specifications.onem2m.org/v4.1.1/feed_rss_updated.xml">oneM2M TS-0019</source><guid isPermaLink="true">https://specifications.onem2m.org/v4.1.1/7.0/</guid> </item> <item> <title>6 Untestable Test Purposes</title> <description><p>Void.</p></description><link>https://specifications.onem2m.org/v4.1.1/6/</link> <pubDate>Fri, 15 Nov 2024 16:22:58 +0000</pubDate><source url="https://specifications.onem2m.org/v4.1.1/feed_rss_updated.xml">oneM2M TS-0019</source><guid isPermaLink="true">https://specifications.onem2m.org/v4.1.1/6/</guid> </item> <item> <title>5</title> <description></description><link>https://specifications.onem2m.org/v4.1.1/5/</link> <pubDate>Fri, 15 Nov 2024 16:22:58 +0000</pubDate><source url="https://specifications.onem2m.org/v4.1.1/feed_rss_updated.xml">oneM2M TS-0019</source><guid isPermaLink="true">https://specifications.onem2m.org/v4.1.1/5/</guid> </item> <item> <title>5.6 Test strategy</title> <description><p>This clause introduces the test strategy being used for the TTCN-3 test cases. The chosen strategy permits to have a clear structure of the code that facilit...</p></description><link>https://specifications.onem2m.org/v4.1.1/5.6/</link> <pubDate>Fri, 15 Nov 2024 16:22:58 +0000</pubDate><source url="https://specifications.onem2m.org/v4.1.1/feed_rss_updated.xml">oneM2M TS-0019</source><guid isPermaLink="true">https://specifications.onem2m.org/v4.1.1/5.6/</guid> </item> <item> <title>5.5 Test components</title> <description><h3>5.5.1 Tester</h3><p>The Tester test component includes a set of ports, timers and variables that are common to the other defined components which are described ...</p></description><link>https://specifications.onem2m.org/v4.1.1/5.5/</link> <pubDate>Fri, 15 Nov 2024 16:22:58 +0000</pubDate><source url="https://specifications.onem2m.org/v4.1.1/feed_rss_updated.xml">oneM2M TS-0019</source><guid isPermaLink="true">https://specifications.onem2m.org/v4.1.1/5.5/</guid> </item> <item> <title>5.4 Ports and ASPs (Abstract Services Primitives)</title> <description><h3>5.4.0 Introduction</h3><p>The oneM2M ATS implements the following ports:</p><ul><li>The mcaPort and mcaPortIn</li><li>The mccPort and mccPortIn</li><li>The acPort</li><li>The utPort</li><li>...</li></ul></description><link>https://specifications.onem2m.org/v4.1.1/5.4/</link> <pubDate>Fri, 15 Nov 2024 16:22:58 +0000</pubDate><source url="https://specifications.onem2m.org/v4.1.1/feed_rss_updated.xml">oneM2M TS-0019</source><guid isPermaLink="true">https://specifications.onem2m.org/v4.1.1/5.4/</guid> </item> <item> <title>5.3 Test architecture</title> <description><p>The approach for the implementation of an Abstract Protocol Tester selected in oneM2M follows the recommendation of the oneM2M Testing Framework oneM2M TS-00...</p></description><link>https://specifications.onem2m.org/v4.1.1/5.3/</link> <pubDate>Fri, 15 Nov 2024 16:22:57 +0000</pubDate><source url="https://specifications.onem2m.org/v4.1.1/feed_rss_updated.xml">oneM2M TS-0019</source><guid isPermaLink="true">https://specifications.onem2m.org/v4.1.1/5.3/</guid> </item> <item> <title>5.2 Test Configuration</title> <description><h3>5.2.1 AE Test Configuration</h3><p>Test configurations are defined to test different entities such as CSE and AE, etc.</p><p>Figure 5.2.1-1 shows a AE test configura...</p></description><link>https://specifications.onem2m.org/v4.1.1/5.2/</link> <pubDate>Fri, 15 Nov 2024 16:22:57 +0000</pubDate><source url="https://specifications.onem2m.org/v4.1.1/feed_rss_updated.xml">oneM2M TS-0019</source><guid isPermaLink="true">https://specifications.onem2m.org/v4.1.1/5.2/</guid> </item> <item> <title>5.1 Abstract protocol tester</title> <description><p>An abstract protocol tester (APT) is a process that provides behaviours for testing an IUT by emulating a peer IUT at the same layer, and enabling to address...</p></description><link>https://specifications.onem2m.org/v4.1.1/5.1/</link> <pubDate>Fri, 15 Nov 2024 16:22:57 +0000</pubDate><source url="https://specifications.onem2m.org/v4.1.1/feed_rss_updated.xml">oneM2M TS-0019</source><guid isPermaLink="true">https://specifications.onem2m.org/v4.1.1/5.1/</guid> </item> <item> <title>4 Conventions</title> <description><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 Rule...</p></description><link>https://specifications.onem2m.org/v4.1.1/4/</link> <pubDate>Fri, 15 Nov 2024 16:22:57 +0000</pubDate><source url="https://specifications.onem2m.org/v4.1.1/feed_rss_updated.xml">oneM2M TS-0019</source><guid isPermaLink="true">https://specifications.onem2m.org/v4.1.1/4/</guid> </item> <item> <title>3</title> <description></description><link>https://specifications.onem2m.org/v4.1.1/3/</link> <pubDate>Fri, 15 Nov 2024 16:22:57 +0000</pubDate><source url="https://specifications.onem2m.org/v4.1.1/feed_rss_updated.xml">oneM2M TS-0019</source><guid isPermaLink="true">https://specifications.onem2m.org/v4.1.1/3/</guid> </item> </channel></rss>
\ No newline at end of file
diff --git a/public/v4.1.1/index.html b/public/v4.1.1/index.html
index 89bef717b4e70d7741ae8c98ebc12cd76f157b7c..070b5d7cd8f234852c1dc0641147ac60c3118f72 100644
--- a/public/v4.1.1/index.html
+++ b/public/v4.1.1/index.html
@@ -10,7 +10,7 @@
- <link rel="canonical" href="https://specifications.onem2m.org/ts-0019/v4.1.1/">
+ <link rel="canonical" href="https://specifications.onem2m.org/v4.1.1/">
@@ -92,7 +92,7 @@
<header class="md-header md-header--shadow" data-md-component="header">
<nav class="md-header__inner md-grid" aria-label="Header">
- <a href="." title="oneM2M TS-0019" class="md-header__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
+ <a href="https://specifications.onem2m.org" title="oneM2M TS-0019" class="md-header__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
<img src="images/onem2m.png" alt="logo">
@@ -111,7 +111,7 @@
<div class="md-header__topic" data-md-component="header-topic">
<span class="md-ellipsis">
-
+ Home
</span>
</div>
@@ -205,7 +205,7 @@
<nav class="md-nav md-nav--primary" aria-label="Navigation" data-md-level="0">
<label class="md-nav__title" for="__drawer">
- <a href="." title="oneM2M TS-0019" class="md-nav__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
+ <a href="https://specifications.onem2m.org" title="oneM2M TS-0019" class="md-nav__button md-logo" aria-label="oneM2M TS-0019" data-md-component="logo">
<img src="images/onem2m.png" alt="logo">
@@ -245,7 +245,7 @@
<span class="md-ellipsis">
-
+ Home
</span>
@@ -952,7 +952,7 @@
- <h1>oneM2M TS-0019</h1>
+ <h1>Home</h1>
<p><img alt="~~CAPTION~~" src="media/image1.png" /></p>
<table>
diff --git a/public/v4.1.1/search/search_index.json b/public/v4.1.1/search/search_index.json
index a3f3697de5f6f7363886cf1a097c9f7ec6a1a2d2..c0fc8b3bf1572c3a9a86a2808a028c729b523666 100644
--- a/public/v4.1.1/search/search_index.json
+++ b/public/v4.1.1/search/search_index.json
@@ -1 +1 @@
-{"config":{"lang":["en"],"separator":"[\\s\\-]+","pipeline":["stopWordFilter"]},"docs":[{"location":"","title":"","text":"oneM2MTechnical Specification oneM2MTechnical Specification Document Number oneM2M-TS-0019-V-4.1.1 Document Name: Abstract Test Suite and Implementation eXtra Information for Test Date: 2024 March 1 Abstract: Abstract Test Suite and Implementation eXtra Information for Test consists of :- Definition of the Abstract Protocol Tester (APT)- Definition of TTCN-3 test architecture- Development of TTCN-3 test suite, e.g. naming conventions, code documentation, test case structure.- IXIT proforma; Template Version:23 February 2015 (Do not modify) Template Version:23 February 2015 (Do not modify) <p>This Specification is provided for future development work within oneM2M only. The Partners accept no liability for any use of this Specification.</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) 2019, oneM2M Partners Type 1 (ARIB, ATIS, CCSA, ETSI, TIA, TSDSI, TTA, TTC).</p> <p>All rights reserved.</p> <p>The copyright extends 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 Specification oneM2MTechnical Specification Document Number oneM2M-TS-0019-V-4.1.1 Document Name: Abstract Test Suite and Implementation eXtra Information for Test Date: 2024 March 1 Abstract: Abstract Test Suite and Implementation eXtra Information for Test consists of :- Definition of the Abstract Protocol Tester (APT)- Definition of TTCN-3 test architecture- Development of TTCN-3 test suite, e.g. naming conventions, code documentation, test case structure.- IXIT proforma; Template Version:23 February 2015 (Do not modify) Template Version:23 February 2015 (Do not modify) <p>This Specification is provided for future development work within oneM2M only. The Partners accept no liability for any use of this Specification.</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) 2019, oneM2M Partners Type 1 (ARIB, ATIS, CCSA, ETSI, TIA, TSDSI, TTA, TTC).</p> <p>All rights reserved.</p> <p>The copyright extends 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>The present document contains the Abstract Test Suite (ATS) for oneM2M as defined in oneM2M TS-0001 [1] and oneM2M TS-0004 [2] in compliance with the relevant requirements and in accordance with the relevant guidance given in ISO/IEC 96467 [5].</p> <p>The objective of the present document is to provide a basis for conformance tests for oneM2M products giving a high probability of interoperability between different manufacturers' equipment.</p> <p>The ISO standard for the methodology of conformance testing (ISO/IEC 96461 [3] and ISO/IEC 96462 [4]) as well as oneM2M TS-0015 Testing Framework [i.2] are used as a basis for the test methodology.</p>"},{"location":"2.1/","title":"2.1 Normative references","text":"<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> <p>The following referenced documents are necessary for the application of the present document.</p> <ul> <li>[1] oneM2M TS-0001: \"Functional Architecture\".</li> <li>[2] oneM2M TS-0004: \"Service Layer Core Protocol\".</li> <li>[3] ISO/IEC 9646-1 (1994): \"Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 1: General concepts\".</li> <li>[4] ISO/IEC 9646-2 (1994): \"Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 2: Abstract Test Suite specification\".</li> <li>[5] ISO/IEC 9646-7 (1995): \"Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 7: Implementation Conformance Statements\".</li> <li>[6] ETSI ES 201 873-1 (V4.5.1): \"Methods for Testing and Specification (MTS); The Testing and Test Control Notation version 3; Part 1: TTCN-3 Core Language\".</li> <li> <p>[7] oneM2M TS-0018: \"Test Suite Structure and Test Purposes\".</p> </li> <li> <p>[8] 3GPP TS 29.122; T8 reference point for Northbound APIs (Release 15)</p> </li> </ul>"},{"location":"2.2/","title":"2.2 Informative references","text":"<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> <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>[i.1] oneM2M Drafting Rules.</li> </ul> <p>Note</p> <p>Available at http://www.onem2m.org/images/files/oneM2M-Drafting-Rules.pdf.</p> <ul> <li>[i.2] oneM2M TS-0015: \"Testing Framework\".</li> <li>[i.3] oneM2M TS-0025: \"Product profiles\".</li> </ul>"},{"location":"3.1/","title":"3.1 Terms","text":"<p>For the purposes of the present document, the terms given in ISO/IEC 96461 [3], ISO/IEC 96467 [5] and oneM2M TS-0015 [i.2] apply.</p>"},{"location":"3.2/","title":"3.2 Symbols","text":"<p>For the purposes of the present document, the following abbreviations apply:</p> <p><code>AE Application Entity</code> <code>APT Abstract Protocol Tester</code> <code>ATM Abstract Test Method</code> <code>ATS Abstract Test Suite</code> <code>CoAP Constrained Application Protocol</code> <code>CSE Common Service Entity</code> <code>HTTP Hypertext Transfer Protocol</code> <code>IP Internet Protocol</code> <code>IUT Implementation Under Test</code> <code>IXIT Implementation eXtra Information for Test</code> <code>JSON JavaScript Object Notation</code> <code>MQTT Message Queuing Telemetry Transport</code> <code>MTC Main Test Component</code> <code>PA Platform Adaptor</code> <code>PICS Protocol Implementation Conformance Statement</code> <code>PTC Paralell Test Component</code> <code>PX PiXit</code> <code>SA System Adaptor</code> <code>SUT System Under Test</code> <code>TC Test Case</code> <code>TCP Transmission Control Protocol</code> <code>TP Test Purposes</code> <code>TS Test System</code> <code>TSS Test Suite Structure</code> <code>TTCN Tree and Tabular Combined Notation</code> <code>UDP User Datagram Protocol</code> <code>UT Upper Tester</code> <code>XML eXtensible Markup Language</code> </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.1].</p>"},{"location":"5.1/","title":"5.1 Abstract protocol tester","text":"<p>An abstract protocol tester (APT) is a process that provides behaviours for testing an IUT by emulating a peer IUT at the same layer, and enabling to address a single test objective.</p> <p>APTs used by the oneM2M test suite are described in figure 5.1-1. The test system will simulate valid and invalid protocol behaviour, and will analyse the reaction of the IUT.</p> <p></p> <p>Figure 5.1-1: Abstract protocol testers - oneM2M</p> <p>As figure 5.1-1 illustrates, the corresponding ATS needs to use lower layers to establish a proper connection to the system under test (SUT) over a physical link (Lower layers link). Four different lower layers have been specified corresponding to the binding protocols considered in oneM2M: HTTP, CoAP, WebSocket and MQTT.</p>"},{"location":"5.2/","title":"5.2 Test Configuration","text":""},{"location":"5.2/#521-ae-test-configuration","title":"5.2.1 AE Test Configuration","text":"<p>Test configurations are defined to test different entities such as CSE and AE, etc.</p> <p>Figure 5.2.1-1 shows a AE test configuration which is mapped to CF03 in clause 6.3.3.3 in oneM2M TS0015 [i.2] and aligns with conformance test system architecture in clause 6.3.3.2 in oneM2M TS-0015 [i.2].</p> <p>The TTCN-3 Test Component in Test System sends triggering actions or behaviour to the Upper Tester Application of SUT through upper tester transport link Ut while the IUT sends/receives oneM2M service primitives through Mca to/from CSE in Test System.</p> <p></p> <p>Figure 5.2.1-1: AE test configuration</p>"},{"location":"5.3/","title":"5.3 Test architecture","text":"<p>The approach for the implementation of an Abstract Protocol Tester selected in oneM2M follows the recommendation of the oneM2M Testing Framework oneM2M TS-0015 [i.2] where the TTCN-3 language and its architecture are recommended.</p> <p>Following this recommendation the oneM2M tester architecture comprises a non-platform dependent Test Suite, and a platform dependent part.</p> <p></p> <p>Note</p> <p>However, it can be implemented in a semi-independent manner, which will minimize the dependency to those elements.</p> <p>Figure 5.3-1: High level oneM2M Test Architecture</p> <ul> <li>oneM2M TTCN -3 Abstract Test Suite: the test suite is platform independent, and it is the cornerstone of the architecture. It allows a complete decoupling between the test suite and the rest of the test system. The test suite is composed of a complete set of test cases covering oneM2M requirements specified by oneM2M TS0001 [1] and oneM2M TS-0004 [2].</li> <li>oneM2M System Adaptor : this is the platform dependent part that includes adaptors and codecs (out of the scope of the present document). This part of the architecture definition depends on the specific platform (e.g. Windows or Linux) and test tool on which the tester is going to run.</li> </ul> <p>Figure 5.3-2 shows the oneM2M TTCN-3 test architecture design used for the oneM2M ATS. The Test Suite needs to interact with the System Adaptor to implement the collection of TTCN-3 test cases that are intended to be used to test the oneM2M IUTs.</p> <p>The oneM2M TTCN-3 test cases implement the test algorithms specified in the TSS&TP document oneM2M TS0018 [7], including verdict logic that allows pass/fail diagnosis.</p> <p>The test algorithms use the interfaces defined in [1] and [2] (mca, mcc) in order to:</p> <ol> <li>control the test event to be sent towards the IUT; and</li> <li>observe the test events received from the IUT.</li> </ol> <p>In TTCN-3 these two interfaces have been implemented through a set of logical TTCN-3 ports (mcaPort and mcaPortIn for mca interface, and mccPort and mccPortIn for mcc interface) which allows oneM2M message primitives exchange with the IUT.</p> <p></p> <p>Figure 5.3-2: oneM2M Test Architecture</p> <p>The oneM2M primitive messages have been mapped into TTCN-3 structure. Through this mapping, the TTCN-3 is able to build and send these messages, as well as receive them via the ports defined above.</p> <p>Additionally, the test cases are able to control and configure the test platform through a dedicated port called acPort while port utPort enables oneM2M TTCN-3 Test Component module to trigger specific action or behaviour on IUT. TTCN3 Test Components can also exchange information through a dedicated port called infoPort.</p> <p>To build up a tester, the test platform needs to be also developed (out of scope). This test platform is composed of three adaptation layers:</p> <ul> <li>PA (Platform Adaptor) layer functionality implements the communication between the TTCN-3 modules and external elements that constitute the test tool such as timers and external functions. The External functions are a powerful resources supported by TTCN-3 language. An External function is a function declared at the TTCN-3 level but implemented at the native level.</li> <li> <p>SA (System Adaptor) layer functionality is divided into two modules:</p> <ul> <li>oneM2M lower layers stack module implements the communication with the IUT and carries out the oneM2M primitives messages sent to or received from the IUT. This module is based on TCP or UDP depending on the binding supported by the IUT. The binding is a system adaptor parameter.</li> <li>Upper Tester Transport module implements functions that enable triggering specific actions or behaviour on the IUT.</li> </ul> </li> <li> <p>CODECS layer is the part of the tester to encode and decode messages between the TTCN-3 abstract internal data representation and the format required by the related base standard which the IUT understands. Several CODECS are required in oneM2M tester to cope with the bindings considered in oneM2M (HTTP, CoAP, MQTT) and the serialization methods (xml, json).</p> </li> </ul>"},{"location":"5.4/","title":"5.4 Ports and ASPs (Abstract Services Primitives)","text":""},{"location":"5.4/#540-introduction","title":"5.4.0 Introduction","text":"<p>The oneM2M ATS implements the following ports:</p> <ul> <li>The mcaPort and mcaPortIn</li> <li>The mccPort and mccPortIn</li> <li>The acPort</li> <li>The utPort</li> <li>The InfoPort</li> </ul>"},{"location":"5.4/#541-mcaport-mcaportin-mccport-mccportin","title":"5.4.1 mcaPort, mcaPortIn, mccPort, mccPortIn","text":"<p>These ports are used to send and receive the following message sets:</p> <ul> <li>Request Primitives messages in accordance with oneM2M TS-0004 [2].</li> <li>Response Primitives messages in accordance with oneM2M TS-0004 [2].</li> </ul> <p>Two primitives are currently defined for these ports indicated as table 5.4.1-1:</p> <ol> <li>The M2MRequestPrimitive - to send or receive oneM2M messages to/from the IUT. Depending on the IUT to be tested:<ol> <li>If the IUT is an AE, these messages are either received or sent by the tester which is associated with the CSE role through the mcaPortIn or the mcaPort respectively.</li> <li>If the IUT is a CSE, these messages are either sent or received by the tester when it plays the AE role through the mcaPort or the mcaPortIn respectively, or sent or received by the tester when it plays the CSE role through the mccPort or the mccPortIn respectively.</li> </ol> </li> <li>The M2MResponsePrimitive - to send or receive oneM2M messages to/from the IUT. Depending on the IUT to be tested:<ol> <li>If the IUT is an AE, these messages are either sent or received by the tester which is associated with the CSE role through the mcaPortIn or the mcaPort respectively.</li> <li>If the IUT is a CSE, these messages are either sent or received by the tester when it plays the CSE role through the mccPortIn or the mccPort respectively, sent or received by the tester when it plays the AE role through the mcaPortIn or mcaPort respectively.</li> </ol> </li> </ol> <p>Both primitives contain another parameters that permits to dynamically configure the test adaptor for every single sending. These parameters are:</p> <ul> <li>Host: IP address of the IUT</li> <li>XML Namespace</li> <li>Protocol binding</li> <li>Serialization</li> <li>ForceFields: used to force invalid or empty values to certain attributes. This behaviour shall be implemented by the System Adaptor.</li> </ul> <p>Table 5.4.1-1: Mapping of TTCN-3 Primitives to oneM2M Service Primitives</p> TTCN-3 Primitive oneM2M Message Direction IUT M2MRequestPrimitive Request Primitive <=> AE M2MRequestPrimitive Request Primitive <=> CSE M2MResponsePrimitive Response Primitive <=> AE M2MResponsePrimitive Response Primitive <=> CSE"},{"location":"5.4/#542-mcnport-mcnportin","title":"5.4.2 mcnPort, mcnPortIn","text":"<p>These ports are used to send and receive the following message sets:</p> <ul> <li>Request Primitives messages in accordance with oneM2M TS-0004 [2].</li> <li>Response Primitives messages in accordance with oneM2M TS-0004 [2].</li> </ul> <p>Two primitives are currently defined for these ports indicated:</p> <ol> <li> <p>The T8Request - to send T8 request messages to/from the IUT according to 3GPP TS 29.122 [8]. </p> </li> <li> <p>The T8Response - to receive T8 response messages to/from the IUT according to 3GPP TS 29.122 [8].</p> </li> </ol> <p>Further primitives might be defined to support other underlying networks.</p>"},{"location":"5.4/#543-mccportinternal","title":"5.4.3 mccPortInternal","text":"<p>This port is used to send and receive the following message sets between TTCN-3 components:</p> <ul> <li>Request Primitives messages in accordance with oneM2M TS-0004 [2].</li> <li>Response Primitives messages in accordance with oneM2M TS-0004 [2].</li> </ul>"},{"location":"5.4/#544-utport","title":"5.4.4 utPort","text":""},{"location":"5.4/#5440-introduction","title":"5.4.4.0 Introduction","text":"<p>The utPort is included in the oneM2M ATS in order to be able to stimulate the IUT and receive extra information from IUT upper layers. For instance, the utPort can be applied to automate AE testing shown as clause 5.4.4.1.</p>"},{"location":"5.4/#5441-usage-for-automated-ae-testing","title":"5.4.4.1 Usage for Automated AE Testing","text":"<p>The utPort is in charge of the communication between TTCN-3 Test Component module in Test System and the Upper Tester Application in SUT.</p> <p>Functionalities that TTCN-3 Test Component module and the Upper Tester Application are required to implement are listed as follows:</p> <ul> <li>TTCN-3 Test Component is able to configure the Test System and send standardized triggering commands to the SUT (Upper Tester Application).</li> <li>Upper Tester Application can process the triggering command messages received from Test System (TTCN-3 Test Component) and stimulates IUT to act following the corresponding triggering command (i.e. sending oneM2M service primitives to Test System through Mca port).</li> </ul> <p>oneM2M service Primitive defined for utPort is listed as follows:</p> <ul> <li>The UtTrigger primitive is used to trigger upper layer events in IUT (i.e. sending oneM2M service primitives to Test System through Mca port).</li> <li>The UtTriggerAck primitive is used by IUT to send acknowledgement back to the Test System.</li> </ul> <p>The Upper Tester Application in SUT can be implemented as an embedded source code. An example for implementation of automated AE test for Registration is shown as figure 5.4.4.1-1.</p> <p></p> <p>Figure 5.4.4.1-1: Example of automated AE test using Ut interface</p>"},{"location":"5.4/#5442-upper-tester-control-primitives","title":"5.4.4.2 Upper Tester Control Primitives","text":""},{"location":"5.4/#54421-introduction","title":"5.4.4.2.1 Introduction","text":"<p>The upper tester triggering message is used to transport control commands between Test System and the Upper Tester Application. The control command will contain essential parameters that are required for certain test case.</p> <p>The upper tester triggering message type maps to particular message formats for exchanging data and those message formats are defined by TTCN-3 primitive as shown at table 5.4.4.2.1-1, U tTrigger and U tTriggerAck primitive.</p> <p>Table 5.4.4.2.1-1: Mapping of TTCN-3 Primitives to oneM2M Service Primitives</p> Upper Tester Control Message Type TTCN-3 Primitives Direction Direction Trigger UtTrigger Primitive TS UT Trigger Acknowledgement UtTriggerAck Primitive UT TS"},{"location":"5.4/#54422-uttrigger-and-uttriggerack-primitives","title":"5.4.4.2.2 UtTrigger and UtTriggerAck Primitives","text":"<p>The UtTrigger primitive is initialized by the Test System to send triggering message to the target IUT as depicted in figure 5.4.4.2.2-1. The IUT will send acknowledgement message back to the Test System using UtTriggerAck primitive if trigger message is successfully transported to the IUT. Then IUT starts interaction with Test System through oneM2M request and response primitives.</p> <p></p> <p>Figure 5.4.4.2.2-1: Trigger message flow</p> <p>Table 5.4.4.2.2-1 defines UtTrigger and UtTriggerAck primitives including oneM2M data types to which are mapped as well as examples to show how to implement UtTrigger and UtTriggerAck primitives.</p> <p>Table 5.4.4.2.2-1: UtTrigger and UtTriggerAck Primitive</p> Ut Control Primitive Mapping to oneM2M data types Description Reference Triggering Message HTTP message UtTrigger Primitive requestPrimitive ONLY essential parameters included for certain test caseSee note 1 oneM2MTS-0004 [2] EXAMPLE 1:If the test objective is to test \"Test System triggers IUT to execute a test case for creation of < AE > with labels attribute under a CSEBase resource \", then the triggering message would be serialized as following. EXAMPLE 1:If the test objective is to test \"Test System triggers IUT to execute a test case for creation of < AE > with labels attribute under a CSEBase resource \", then the triggering message would be serialized as following. UtTrigger Primitive requestPrimitive ONLY essential parameters included for certain test caseSee note 1 oneM2MTS-0004 [2] Request{\"m2m:rqp\" :{ \"op\": 1, //indicate CREATE operation \"ty\": 2, //indicate AE resource type \"to\": {TEST_SYSTEM_ADDRESS}, \"pc\": { \"m2m:ae\": { \"lbl\":\"UNINITIALIZED\" //indicate that attribute labels needs to be included }, } \"rvi\": \"2a\"}} RequestPOST /{SUT_UT_APPLICATION_URL} HTTP/1.1Host : {SUT_IP_ADDRESS:PORT}Content-Length : {PAYLOAD_LENGTH}Content-Type : application/ json{\"m2m:rqp\" :{ \"op\": 1, //indicate CREATE operation \"ty\": 2, //indicate AE resource type \"to\": {TEST_SYSTEM_ADDRESS}, \"pc\": { \"m2m:ae\": { \"lbl\":\"UNINITIALIZED\" //indicate that attribute labels needs to be included } }, \"rvi\": \"2a\"}} UtTrigger Primitive requestPrimitive ONLY essential parameters included for certain test caseSee note 1 oneM2MTS-0004 [2] EXAMPLE 2: If the test objective is to test \"Test System triggers IUT to execute a test case for delete of a < AE > resource. \", then the triggering message would be serialized as following. EXAMPLE 2: If the test objective is to test \"Test System triggers IUT to execute a test case for delete of a < AE > resource. \", then the triggering message would be serialized as following. UtTrigger Primitive requestPrimitive ONLY essential parameters included for certain test caseSee note 1 oneM2MTS-0004 [2] Request{\"m2m:rqp\" :{ \"op\": 4, //indicate DELETE operation \"to\": {TARGET_AE_RESOURCE_ADDRESS}, //indicate Target AE resource address \"rvi\": \"2a\"}} RequestPOST /{SUT_UT_APPLICATION_URL} HTTP/1.1Host : {SUT_IP_ADDRESS:PORT}Content-Length : {PAYLOAD_LENGTH}Content-Type : application/ json{\"m2m:rqp\" :{ \"op\": 4, //indicate DELETE operation \"to\": {TARGET_AE_RESOURCE_ADDRESS}, //indicate Target AE resource address \"rvi\": \"2a\"}} UtTriggerPrimitive N/A Special upper tester commands N/A \"RESET\" RequestPOST /{SUT_UT_APPLICATION_URL} HTTP/1.1Host : {SUT_IP_ADDRESS:PORT}X-M2M-UTCMD: Reset UtTrigger Ack Primitive responsePrimitive ONLY responseStatusCode attribute includedSee note 2 oneM2M TS-0004 [2] Response{ \"m2m:rsp\": { \"rsc\": 2000 }}For any triggering response, it only contains a response status code, and the response status code for the triggering operation can only be set to either 2000 (OK) or 4000 (BAD_REQUEST) according to the rules for triggering operations. ResponseHTTP/1.1 200 OKX-M2M-RSC: 2000 NOTE 1: Additional rules defined in table 5.4.4.2.2-3 are also applied.NOTE 2: Attribute response status code is defined at table 5.4.4.2.2-3. NOTE 1: Additional rules defined in table 5.4.4.2.2-3 are also applied.NOTE 2: Attribute response status code is defined at table 5.4.4.2.2-3. NOTE 1: Additional rules defined in table 5.4.4.2.2-3 are also applied.NOTE 2: Attribute response status code is defined at table 5.4.4.2.2-3. NOTE 1: Additional rules defined in table 5.4.4.2.2-3 are also applied.NOTE 2: Attribute response status code is defined at table 5.4.4.2.2-3. NOTE 1: Additional rules defined in table 5.4.4.2.2-3 are also applied.NOTE 2: Attribute response status code is defined at table 5.4.4.2.2-3. NOTE 1: Additional rules defined in table 5.4.4.2.2-3 are also applied.NOTE 2: Attribute response status code is defined at table 5.4.4.2.2-3. <p>Table 5.4.4.2.2-2: Definition of special Upper Tester commands</p> Value Interpretation Reset Inidicates that the IUT should reset <p>The rules for defining UtTrigger and UtTriggerAck primitives are:</p> <ol> <li> <p>UtTrigger primitive is represented in requestPrimitive serialized in JSON format. </p> </li> <li> <p>UtTrigger primitive shall be interpreted as follows:</p> <ul> <li>Any attribute/parameter containing a value shall be present and equal in the triggered request primitive.</li> <li>Any attribute/parameter containing \"UNINITIALIZED\" value shall be present in the triggered request primitive.</li> <li>Any other attribute/parameter shall comply with oneM2M TS-0004 [2].</li> </ul> </li> <li> <p>Parameters within UtTrigger are listed as following:</p> <ul> <li>operation: (mandatory) operation type that IUT is triggered to perform.</li> <li>resourceType: (optional) resource type of a target resource against which IUT is triggered to perform certain operation</li> <li>to: (mandatory) target resource against which IUT is triggered to perform certain operation. </li> <li>primitiveContent: (optional) represents the resource attributes that shall be included in the requestPrimitive.</li> </ul> </li> </ol> <p>Table 5.4.4.2.2-3: Definition of ResponseStatusCode for UtTriggerAck primitive</p> Response Status Code Description Response Status Code Value Interpretation OK 2000 The SUT receives successfully the triggering message from Test System BAD_REQUEST 4000 The SUT does not interpret correctly the UtTrigger primitive NOTE: Only above two response status codes are allowed to use in UtTriggerAck primitive. NOTE: Only above two response status codes are allowed to use in UtTriggerAck primitive. NOTE: Only above two response status codes are allowed to use in UtTriggerAck primitive."},{"location":"5.4/#54423-control-communication-protocol","title":"5.4.4.2.3 Control Communication Protocol","text":"<p>Protocol used for proceeding communications between Test System and Upper Tester Application is designated to the Hypertext Transfer Protocol (HTTP) protocol owning it is an application protocol that is widely supported by most all IoT devices and various intrinsic features such as persistent connection, ease of programming, flexibility, etc.</p>"},{"location":"5.4/#54424-control-message-serialization","title":"5.4.4.2.4 Control Message Serialization","text":"<p>Control commands that are wrapped within a request body of HTTP message shall be serialized into JavaScript Object Notation (JSON) because it is very lightweight and easy to parse and generate for machines.</p>"},{"location":"5.4/#545-acport","title":"5.4.5 acPort","text":"<p>The acPort is included in the oneM2M ATS in order to be able to control and configure the test adaptor for specific cases.</p>"},{"location":"5.4/#546-infoport","title":"5.4.6 infoPort","text":"<p>The infoPort is included in the oneM2M ATS in order for the TTCN-3 test components to be able to exchange information such as last response primitives or request primitives received by a component, retrieved primitive contents.</p>"},{"location":"5.5/","title":"5.5 Test components","text":""},{"location":"5.5/#551-tester","title":"5.5.1 Tester","text":"<p>The Tester test component includes a set of ports, timers and variables that are common to the other defined components which are described in table 5.5.1-1.</p> <p>Table 5.5.1-1: Tester component elements</p> Name Instance type Element type Description acPort port AdapterControlPort Port that communicates with the adapter for sending configuration parameters infoPort port InfoPort Port between test components for exchanging information utPort port UpperTesterPort Port that communicates with the UT Application for triggering actions on the IUT tc_ac timer N/A Timer for the reception of a message tc_wait timer N/A Timer for the reaction of the IUT to an upper tester primitive tc_done Timer N/A Timer for waiting completion of a component behaviour vc_config variable Configurations Configuration being used for the given test case vc_testSystemRole variable TestSystemRole Role of the test component vc_componentRegistered variable boolean Flag to indicate when a component has registered to the IUT vc_resetRequired variable Boolean Flag to indicate whether a reset of the IUT is necessary vc_resourcesList variable MyResourcesList List of all resources created by the test system on the IUT vc_resourcesIndexToBeDeleted variable IntegerList List of indexes of resources created by the test system on the IUT that need to be deleted vc_acpIndex variable integer Index of accessControlPolicy resource used by the test system by default (when required) vc_request variable MsgIn Latest request primitive received/sent vc_response variable MsgIn Latest response primitive received/sent vc_aeSimu variable default Reference to the default behaviour for an AeSimu component vc_cseSimu variable default Reference to the default behaviour for an CseSimu component vc_primitiveContentRetrievedResource variable PrimitiveContent Latest content of a RETRIEVE operation vc_myInterfaces variable Interfaces Parameters for the ports of the given component:Port (mcaPort, mcaPortIn, mccPort, mccPortIn)Host (SUT IP address :port)Protocol bindingSerialization <p>Note that vc_aeSimu and vc_cseSimu are not common to the other defined test components, but those variables are required in Tester for the correct activation/deactivation of default behaviours.</p>"},{"location":"5.5/#552-aesimu","title":"5.5.2 AeSimu","text":"<p>The AeSimu test component extends the Tester component by adding elements specific to an AE entity. Table 5.5.2-1 summarizes those elements.</p> <p>Table 5.5.2-1: AeSimu component elements</p> Name Instance type Element type Description mcaPort port OneM2MPort Port that implements the mca interface when test system is the client (sending requests) mcaPortIn port OneM2MPort Port that implements the mca interface when test system is the server (receiving requests) vc_ae2 test component AeSimu Reference to the AE2 component when required vc_cse1 test component CseSimu Reference to the CSE1 component when CF02 is used vc_ae1 test component AeSimu Reference to the AE1 component when required vc_das test component AeSimu Reference to the DAS component when required vc_aeSimuDesc variable AeSimuComponentDesc Component configuration extracted from required (AE1 or AE2) tester pixit vc_dasSimuDesc variable AeSimuComponentDesc Component configuration extracted from DAS tester pixit vc_auxiliaryAe2Up variable boolean Flag to indicate that AE2 component has been started vc_aeIndex variable integer Index of the AE resource in vc_resourcesList created by AeSimu component"},{"location":"5.5/#553-csesimu","title":"5.5.3 CseSimu","text":"<p>The CseSimu test component extends the Tester component by adding elements specific to an CSE entity. Table 5.5.3-1 summarizes those elements.</p> <p>Table 5.5.3-1: CseSimu component elements</p> Name Instance type Element type Description mcaPort port OneM2MPort Port that implements the mca interface when test system is the client (sending requests) mcaPortIn port OneM2MPort Port that implements the mca interface when test system is the server (receiving requests) mccPort port OneM2MPort Port that implements the mcc interface when test system is the client (sending requests) mccPortIn port OneM2MPort Port that implements the mcc interface when test system is the server (receiving requests) mccPortInternal port OneM2MPortInternal Port that implements the mcc and mcc' interfaces between TTCN-3 components vc_ae1 test component AeSimu Reference to the AE1 component when CF02 (CseSimu as master) is used vc_cse2 test component CseSimu Reference to the CSE1 component when required vc_cseSimuDesc variable CseSimuComponentDesc Component configuration extracted from required (CSE1 or CSE2) tester pixit vc_localResourcesList variable MyResourcesList List of all resources created by the IUT on the test system vc_localCSEBaseAnncIndex variable integer Index of the CSEBaseAnnc resource corresponding to the IUT vc_localRemoteCseIndex variable integer Index of the remoteCSE resource in vc_localResourcesList representing the IUT (CSE) vc_remoteCseIndex variable integer Index of the remoteCSE resource in vc_resourcesList representing the CseSimu component vc_cSEBaseIndex variable integer Index of the CSEBase resource in vc_localResourcesList of the CseSimu component vc_cseType variable CseTypeID CSE type of the test system (default is MN) vc_auxiliaryCse2Up variable boolean Flag to indicate that CSE2 component has been started"},{"location":"5.5/#554-scefsimu","title":"5.5.4 ScefSimu","text":"<p>The ScefSimu test component extends the Tester component by adding elements specific to an SCEF entity. Table 5.5.4-1 summarizes those elements.</p> <p>Table 5.5.4-1: ScefSimu component elements</p> Name Instance type Element type Description mcnPort port OneM2MPort Port that implements the mcn interface when test system is the client (sending requests) mcnPortIn port OneM2MPort Port that implements the mcn interface when test system is the server (receiving requests) vc_ae1 test component AeSimu Reference to the AE1 component when required vc_cse2 test component CseSimu Reference to the CSE1 component when required vc_aeSimuDesc variable AeSimuComponentDesc Component configuration extracted from required (AE1) tester pixit vc_cseSimuDesc variable CseSimuComponentDesc Component configuration extracted from required (CSE1) tester pixit vc_cseType variable CseTypeID CSE type of the test system (default is MN) vc_scefSimuDesc variable ScefSimuComponentDesc Component configuration extracted from required (SCEF) tester pixit vc_configurations variable NiddConfigurations NIDD configurations of SCEF component"},{"location":"5.6/","title":"5.6 Test strategy","text":"<p>This clause introduces the test strategy being used for the TTCN-3 test cases. The chosen strategy permits to have a clear structure of the code that facilitates an easy navigation throw the different test steps.</p> <p>The use of the TTCN-3 MTC and PTC(s) is as depicted in figure 5.6-1.</p> <p></p> <p>Figure 5.6-1: Use of TTCN-3 components</p> <p>At the start of the test case execution, the MTC is created. Then, the MTC executes the following steps:</p> <ul> <li>Step 1) initialization of the master PTC.</li> <li>Step 2) initialization of some parameters if required for the permutation test cases.</li> <li> <p>Step 3) running of the appropriate function on the master PTC. The function run on the master PTC implements a given Test Purpose. Such function follows a code structure as indicated here below:</p> <ul> <li>Local Variables, declaration of local variables.</li> <li>Test Control, checking IUT capability parameters required for the proper execution of the test.</li> <li>Test Component Configuration, that initializes the given test component and other test components acting as slave PTC(s) as required by a given configuration.</li> <li>Test adapter configuration, that configures the test adapter throw the acPort if required.</li> <li>Preamble, that implements the necessary test steps as described in the Initial conditions of a Test Purpose. It may also implement additional test steps which are required for the correct execution of the test.</li> <li>Test body, that implements the test steps as described in the Expected behaviour of a Test Purpose.</li> <li>Postamble, that implements the necessary test steps to bring the IUT back to the initial state.</li> <li>Tear down, that finalizes properly the TTCN-3 ports used by the different test components depending on the configuration.</li> </ul> </li> </ul> <p>While master PTC follows the test structure described above, slave PTC(s) run only certain procedures, usually one by one, as mandated by the master PTC.</p> <p>A procedure usually implements a oneM2M request-response exchange between a given PTC and the IUT, although it can implement any other specific action (sending or reception of a message, several request-response exchanges, etc.).</p> <ul> <li>Step 4) checking of some parameters if required for the permutation test cases.</li> </ul> <p>This test strategy may slightly vary for certain cases where specific requirements need to be fulfilled.</p>"},{"location":"6/","title":"6 Untestable Test Purposes","text":"<p>Void.</p>"},{"location":"7.0/","title":"7.0 Introduction","text":"<p>The ATS conventions are intended to give a better understanding of the ATS but they also describe the conventions made for the development of the ATS. These conventions shall be considered during any later maintenance or further development of the ATS.</p> <p>The ATS conventions contain two clauses, the naming conventions and the implementation conventions. The naming conventions describe the structure of the naming of all ATS elements. The implementation conventions describe the functional structure of the ATS.</p> <p>To define the ATS, the guidelines of oneM2M TS-0015 [i.2] were considered.</p>"},{"location":"7.1/","title":"7.1 Testing conventions","text":""},{"location":"7.1/#711-testing-states","title":"7.1.1 Testing states","text":""},{"location":"7.1/#7111-initial-state","title":"7.1.1.1 Initial state","text":"<p>All test cases start with the function f_preamble_XYZ. This function brings the IUT in an \"initialized\" state by performing some actions such as registration of AE, creation of auxiliary access control policy resource, creation of additional needed resources.</p>"},{"location":"7.1/#7112-final-state","title":"7.1.1.2 Final state","text":"<p>All test cases end with the function f_postamble_XYZ. This function brings the IUT back in an \"idle\" state which means deletion of all created resources being used by the test case so that next test case execution is not disturbed.</p> <p>As necessary, further actions may be included in the f_postamble functions.</p>"},{"location":"7.2/","title":"7.2 Naming conventions","text":""},{"location":"7.2/#721-general-guidelines","title":"7.2.1 General guidelines","text":"<p>This test suite follows the naming convention guidelines provided in oneM2M TS-0015 [i.2].</p> <p>The naming convention is based on the following underlying principles:</p> <ul> <li>in most cases, identifiers should be prefixed with a short alphabetic string (specified in table 7.2.1-1) indicating the type of TTCN3 element it represents;</li> <li>suffixes should not be used except in those specific cases identified in table 7.2.1-1;</li> <li>prefixes and suffixes should be separated from the body of the identifier with an underscore (\"_\");</li> </ul> <p><code>EXAMPLE 1: c\\_sixteen, t\\_wait.</code> </p> <ul> <li>only module names, data type names and module parameters should begin with an uppercase letter. All other names (i.e. the part of the identifier following the prefix) should begin with a lowercase letter;</li> <li>the start of second and subsequent words in an identifier should be indicated by capitalizing the first character. Underscores should not be used for this purpose.</li> </ul> <p><code>EXAMPLE 2: f\\_initialState.</code> </p> <p>Table 7.2.1-1 specifies the naming guidelines for each element of the TTCN3 language indicating the recommended prefix, suffixes (if any) and capitalization.</p> <p>Table 7.2.1-1: TTCN-3 generic naming conventions</p> Language element Naming convention Prefix Example identifier Module Use upper-case initial letter none OneM2M_Templates Group within a module Use lower-case initial letter none messageGroup Data type Use upper-case initial letter none SetupContents Message template Use lower-case initial letter m_ m_setupInit Message template with wildcard or matching expression Use lower-case initial letters mw_ mw_anyUserReply Signature template Use lower-case initial letter s_ s_callSignature Port instance Use lower-case initial letter none signallingPort Test component instance Use lower-case initial letter none userTerminal Constant Use lower-case initial letter c_ c_maxRetransmission Constant (defined within component type) Use lower-case initial letter cc_ cc_minDuration External constant Use lower-case initial letter cx_ cx_macId Function Use lower-case initial letter f_ f_authentication() External function Use lower-case initial letter fx_ fx_calculateLength() Altstep (incl. Default) Use lower-case initial letter a_ a_receiveSetup() Test case Use ETSI numbering TC_ TC_COR_0009_47_ND Variable (local) Use lower-case initial letter v_ v_macId Variable (defined within a component type) Use lower-case initial letters vc_ vc_systemName Timer (local) Use lower-case initial letter t_ t_wait Timer (defined within a component) Use lower-case initial letters tc_ tc_authMin Module parameters for PICS Use all upper case letters PICS_ PICS_DOOROPEN Module parameters for other parameters Use all upper case letters PX_ PX_TESTER_STATION_ID Formal Parameters Use lower-case initial letter p_ p_macId Enumerated Values Use lower-case initial letter e_ e_syncOk"},{"location":"7.2/#722-onem2m-specific-ttcn-3-naming-conventions","title":"7.2.2 oneM2M specific TTCN-3 naming conventions","text":"<p>Next to such general naming conventions, table 7.2.2-1 shows specific naming conventions that apply to the oneM2M TTCN-3 ATS.</p> <p>Table 7.2.2-1: oneM2M specific TTCN-3 naming conventions</p> Language element Naming convention Prefix Example identifier oneM2M Module Use upper-case initial letter OneM2M_ OneM2M_Testcases_ Module containing oneM2M types Use upper-case initial letter OneM2M_Types OneM2M_Types Module containing types and values Use upper-case initial letter OneM2M_TypesAndValues OneM2M_TypesAndValues Module containing Templates Use upper-case initial letter OneM2M_Templates OneM2M_Templates Module containing test cases Use upper-case initial letter OneM2M_Testcases OneM2M_Testcases Module containing functions Use upper-case initial letter OneM2M_Functions OneM2M_Functions Module containing external functions Use upper-case initial letter OneM2M_ExternalFunctions OneM2M_ExternalFunctions Module containing components, ports and message definitions Use upper-case initial letter OneM2M_TestSystem OneM2M_TestSystem Module containing module parameters Use upper-case initial letter OneM2M_Pixits OneM2M_Pixits"},{"location":"7.2/#723-usage-of-log-statements","title":"7.2.3 Usage of Log statements","text":"<p>All TTCN-3 log statements use the following format using the same order:</p> <ul> <li>The TTCN-3 test case or function identifier in which the log statement is defined.</li> <li>One of the categories of log: INFO, WARNING, ERROR, TIMEOUT, NONE.</li> <li>Free text.</li> </ul> <p><code>EXAMPLE 1: **log** (\"f\\_utInitializeIut: INFO: IUT initialized\");</code> </p> <p>Furthermore, the following rules are applied too:</p> <ul> <li>All TTCN-3 setverdict statements are combined (as defined in TTCN-3 - ETSI ES 201 873-1 [6]) with a log statement following the same above rules (see example 2).</li> </ul> <p><code>EXAMPLE 2: **setverdict** (**pass** , \"TC\\_ONEM2M\\_CSE\\_DMR\\_CRE\\_001: Received correct message\");</code> </p>"},{"location":"7.2/#724-test-case-tc-identifier","title":"7.2.4 Test Case (TC) identifier","text":"<p>Table 7.2.4-1: TC naming convention</p> Identifier: TC_<root>_<gr>_<sgr>_<nn>_<per> <root> = root ONEM2M oneM2M <gr> = group CSE CSE testing AE AE testing <sgr> = subgroup REG Registration DMR Data Management and Repository SUB Subscription and Notification GMG Group Management DIS Discovery LOC Location DMG Device Management CMDH Communication Management and Delivery Handling SEC Security <nn> = sequential number 001 to 999 <per> = permutation P1_P2_..PN Permutation parameters <p><code>EXAMPLE: TP identifier: TP/oneM2M/CSE/DMR/CRE/001</code> <code>TC identifier: TC\\_ONEM2M\\_CSE\\_DMR\\_CRE\\_001.</code> </p>"},{"location":"7.3/","title":"7.3 IXIT","text":"<p>The following parameters are used by the oneM2M ATS for the correct execution of the test cases.</p> <p>Table 7.3-1: oneM2M ATS IXITs</p> GROUP IXIT NAME DESCRIPTION DEFAULT VALUE IutParameters PX_IN_CSE MN-CSE True IutParameters PX_MN_CSE IN-CSE False IutParameters PX_ASN_CSE ASN-CSE False IutParameters PX_SUT_ADDRESS SUT address \"127.0.0.1:8080\" IutParameters PX_UT_IMPLEMENTED Upper Tester implemented False IutParameters PX_CSE_NAME IUT CSE Name \"cseName\" IutParameters PX_CSE_ID IUT CSE-ID with SP-relative-CSE-ID format (relative) according to oneM2M TS-0001 [1], table 7.2-1 \"/cseId\" IutParameters PX_CSE_RESOURCE_ID IUT CSE resource ID with Unstructured-CSE-relative-Resource-ID (relative) format according to oneM2MTS-0001 [1], table 7.2-1 \"cseResourceId\" IutParameters PX_SP_ID IUT M2M-SP-ID with M2M-SP-ID format (absolute) according to oneM2M TS-0001 [1], table 7.2-1 Unstructured-CSE-relative -Resource-ID \"//om2m.org\" IutParameters PX_SUPER_AE_ID AE-ID with privileges to CREATE at the IUT CSEBase with AE-ID-Stem format (relative) according to oneM2M TS-0001 [1], table 7.2-1 \"admin:admin\" IutParameters PX_SUPER_CSE_ID CSE-ID with privileges to CREATE at the IUT CSEBase with SPrelative-CSE-ID format (relative) according to oneM2M TS-0001 [1], table 7.2-1 \"/admin:admin\" IutParameters PX_ALLOWED_C_AE_IDS {\"C-AllowedAeId\"} IutParameters PX_NOT_ALLOWED_C_AE_IDS {\"C-NotAllowedAeId\"} IutParameters PX_ALLOWED_S_AE_IDS {\"S-AllowedAeId\"} IutParameters PX_NOT_ALLOWED_S_AE_IDS {\"S-NotAllowedAeId\"} IutParameters PX_NOT_ALLOWED_APP_ID \"NotAllowedAppId\" IutParameters PX_ADDRESSING_METHOD Addressing method e_hierarchical IutParameters PX_PRIMITIVE_SCOPE Primitive scope e_cseRelative IutParameters PX_WS_PROTOCOL WebSocket protocol \"oneM2M.R2.0.xml\" IutParameters PX_REQUEST_URI WebSocket context \"/\" IutParameters PX_HOSTING_CSE_ID Hosting CSE-ID for MQTT \"CSE-ID\" IutParameters PX_CREDENTIAL_ID Credential-ID for MQTT \"admin:admin\" IutParameters PX_XML_NAMESPACE XML Namespace \"m2m=\"\"http://www.onem2m.org/xml/protocols\"\"\" IutParameters PX_ACOR AccessControlOriginators {\"all\"} IutParameters PX_TCONFIG_IUT Time to configure IUT after a requested action 10.0 TesterParameters PX_TS_AE1 AE1 component settings aeIdStem = \"\"appId = \"NMyApp1Id\"mcaPort and mcaPortIn settings which include per port the following info:Binding: - bindingProtocol - bindingDesc: - tsAddress - localPort - sutAddress - remotePortSerialization TesterParameters PX_TS_AE2 AE2 component settings aeIdStem = \"\"appId = \"NMyApp2Id\"mcaPort and mcaPortIn settings which include per port the following info:Binding: - bindingProtocol - bindingDesc: - tsAddress - localPort - sutAddress - remotePortSerialization TesterParameters PX_TS_CSE1 CSE1 component settings cseName = \"CSE1_NAME\"cseId = \"/CSE1_ID\"cseResourceId = \"CSE1_RESOURCE_ID\"spId = \"//onem2m.org\"supportedResourceType = {int1, int2, int3, int16}mcaPort, mcaPortIn, mccPort and mccPortIn settings which include per port the following info:Binding: - bindingProtocol - bindingDesc: - tsAddress - localPort - sutAddress - remotePortSerialization TesterParameters PX_TS_CSE2 CSE2 component settings cseName = \"CSE2_NAME\"cseId = \"/CSE2_ID\"cseResourceId = \"CSE2_RESOURCE_ID\"spId = \"//onem2m.org\"supportedResourceType = {int1, int2, int3, int16}mcaPort, mcaPortIn, mccPort and mccPortIn settings which include per port the following info:Binding: - bindingProtocol - bindingDesc: - tsAddress - localPort - sutAddress - remotePortSerialization PX_TS_DAS DAS1 component settings aeIdStem = \"\"appId = \"\"mcaPort and mcaPortIn settings which include per port the following info:Binding: - bindingProtocol - bindingDesc: - tsAddress - localPort - sutAddress - remotePortSerialization PX_TS_UT UpperTester settings url = \"http://127.0.0.1:43000/\" ExecutionParameters PX_RESOURCES_TO_BE_DELETED (For debugging purposes) {\"MyAe\", \"MyAccessControlPolicyResource\", \"SubscriptionVerificationAcp\", \"MyAcp\", \"MyRemoteCSEResource\"} ExecutionParameters PX_RUN_POSTAMBLE (For debugging purposes) true ExecutionParameters PX_CERTIFICATE_PATH charstring \"\" ExecutionParameters PX_CERTIFICATE_NAME charstring \"\" ExecutionParameters PX_PAIRWISEKEY_METHOD PairwiseKeyMethod e_establish ExecutionParameters PX_KEY_PROVISION Provisioned e_preProvisioning"},{"location":"8/","title":"8 TTCN-3 Verifications","text":"<p>The principles for Verifying the TTCN-3 test code are given in oneM2M TS-0015 [i.2].</p> <p>All test cases provided with the present document in annex A which correspond to at least one of the product profiles defined in oneM2M TS-0025 [i.3] have been verified at the time of publication of the present document which corresponds with the TTCN-3 code gitlab tag provided in annex A.</p>"},{"location":"A.1/","title":"A.1 Electronic annex, zip file with TTCN-3 code","text":"<p>This ATS has been produced using the Testing and Test Control Notation (TTCN) according to ETSI ES 201 873-1 [6].</p> <p>This test suite has been compiled error-free using two different commercial TTCN-3 compilers.</p> <p>The TTCN-3 library modules, which form parts of the present document, are contained in the following gitLab tag:</p> <p>https://git.onem2m.org/TST/ATS/-/tags/TS-0019-baseline-v4_1_1 </p> <p></p>"},{"location":"B/","title":"Annex B (informative): Bibliography","text":"<p>ISO/IEC 9646-6 (1994): \"Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 6: Protocol profile test specification\".</p> <p>oneM2M TS-0017: \"Implementation Conformance Statement\".</p> <p>oneM2M TS-0031: \"Feature catalogue\".</p>"},{"location":"download/","title":"Download","text":"<p>Download baseline for TS-0019 version v4.1.1:</p> <p></p>"}]}
\ No newline at end of file
+{"config":{"lang":["en"],"separator":"[\\s\\-]+","pipeline":["stopWordFilter"]},"docs":[{"location":"","title":"Home","text":"oneM2MTechnical Specification oneM2MTechnical Specification Document Number oneM2M-TS-0019-V-4.1.1 Document Name: Abstract Test Suite and Implementation eXtra Information for Test Date: 2024 March 1 Abstract: Abstract Test Suite and Implementation eXtra Information for Test consists of :- Definition of the Abstract Protocol Tester (APT)- Definition of TTCN-3 test architecture- Development of TTCN-3 test suite, e.g. naming conventions, code documentation, test case structure.- IXIT proforma; Template Version:23 February 2015 (Do not modify) Template Version:23 February 2015 (Do not modify) <p>This Specification is provided for future development work within oneM2M only. The Partners accept no liability for any use of this Specification.</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) 2019, oneM2M Partners Type 1 (ARIB, ATIS, CCSA, ETSI, TIA, TSDSI, TTA, TTC).</p> <p>All rights reserved.</p> <p>The copyright extends 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 Specification oneM2MTechnical Specification Document Number oneM2M-TS-0019-V-4.1.1 Document Name: Abstract Test Suite and Implementation eXtra Information for Test Date: 2024 March 1 Abstract: Abstract Test Suite and Implementation eXtra Information for Test consists of :- Definition of the Abstract Protocol Tester (APT)- Definition of TTCN-3 test architecture- Development of TTCN-3 test suite, e.g. naming conventions, code documentation, test case structure.- IXIT proforma; Template Version:23 February 2015 (Do not modify) Template Version:23 February 2015 (Do not modify) <p>This Specification is provided for future development work within oneM2M only. The Partners accept no liability for any use of this Specification.</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) 2019, oneM2M Partners Type 1 (ARIB, ATIS, CCSA, ETSI, TIA, TSDSI, TTA, TTC).</p> <p>All rights reserved.</p> <p>The copyright extends 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>The present document contains the Abstract Test Suite (ATS) for oneM2M as defined in oneM2M TS-0001 [1] and oneM2M TS-0004 [2] in compliance with the relevant requirements and in accordance with the relevant guidance given in ISO/IEC 96467 [5].</p> <p>The objective of the present document is to provide a basis for conformance tests for oneM2M products giving a high probability of interoperability between different manufacturers' equipment.</p> <p>The ISO standard for the methodology of conformance testing (ISO/IEC 96461 [3] and ISO/IEC 96462 [4]) as well as oneM2M TS-0015 Testing Framework [i.2] are used as a basis for the test methodology.</p>"},{"location":"2.1/","title":"2.1 Normative references","text":"<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> <p>The following referenced documents are necessary for the application of the present document.</p> <ul> <li>[1] oneM2M TS-0001: \"Functional Architecture\".</li> <li>[2] oneM2M TS-0004: \"Service Layer Core Protocol\".</li> <li>[3] ISO/IEC 9646-1 (1994): \"Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 1: General concepts\".</li> <li>[4] ISO/IEC 9646-2 (1994): \"Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 2: Abstract Test Suite specification\".</li> <li>[5] ISO/IEC 9646-7 (1995): \"Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 7: Implementation Conformance Statements\".</li> <li>[6] ETSI ES 201 873-1 (V4.5.1): \"Methods for Testing and Specification (MTS); The Testing and Test Control Notation version 3; Part 1: TTCN-3 Core Language\".</li> <li> <p>[7] oneM2M TS-0018: \"Test Suite Structure and Test Purposes\".</p> </li> <li> <p>[8] 3GPP TS 29.122; T8 reference point for Northbound APIs (Release 15)</p> </li> </ul>"},{"location":"2.2/","title":"2.2 Informative references","text":"<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> <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>[i.1] oneM2M Drafting Rules.</li> </ul> <p>Note</p> <p>Available at http://www.onem2m.org/images/files/oneM2M-Drafting-Rules.pdf.</p> <ul> <li>[i.2] oneM2M TS-0015: \"Testing Framework\".</li> <li>[i.3] oneM2M TS-0025: \"Product profiles\".</li> </ul>"},{"location":"3.1/","title":"3.1 Terms","text":"<p>For the purposes of the present document, the terms given in ISO/IEC 96461 [3], ISO/IEC 96467 [5] and oneM2M TS-0015 [i.2] apply.</p>"},{"location":"3.2/","title":"3.2 Symbols","text":"<p>For the purposes of the present document, the following abbreviations apply:</p> <p><code>AE Application Entity</code> <code>APT Abstract Protocol Tester</code> <code>ATM Abstract Test Method</code> <code>ATS Abstract Test Suite</code> <code>CoAP Constrained Application Protocol</code> <code>CSE Common Service Entity</code> <code>HTTP Hypertext Transfer Protocol</code> <code>IP Internet Protocol</code> <code>IUT Implementation Under Test</code> <code>IXIT Implementation eXtra Information for Test</code> <code>JSON JavaScript Object Notation</code> <code>MQTT Message Queuing Telemetry Transport</code> <code>MTC Main Test Component</code> <code>PA Platform Adaptor</code> <code>PICS Protocol Implementation Conformance Statement</code> <code>PTC Paralell Test Component</code> <code>PX PiXit</code> <code>SA System Adaptor</code> <code>SUT System Under Test</code> <code>TC Test Case</code> <code>TCP Transmission Control Protocol</code> <code>TP Test Purposes</code> <code>TS Test System</code> <code>TSS Test Suite Structure</code> <code>TTCN Tree and Tabular Combined Notation</code> <code>UDP User Datagram Protocol</code> <code>UT Upper Tester</code> <code>XML eXtensible Markup Language</code> </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.1].</p>"},{"location":"5.1/","title":"5.1 Abstract protocol tester","text":"<p>An abstract protocol tester (APT) is a process that provides behaviours for testing an IUT by emulating a peer IUT at the same layer, and enabling to address a single test objective.</p> <p>APTs used by the oneM2M test suite are described in figure 5.1-1. The test system will simulate valid and invalid protocol behaviour, and will analyse the reaction of the IUT.</p> <p></p> <p>Figure 5.1-1: Abstract protocol testers - oneM2M</p> <p>As figure 5.1-1 illustrates, the corresponding ATS needs to use lower layers to establish a proper connection to the system under test (SUT) over a physical link (Lower layers link). Four different lower layers have been specified corresponding to the binding protocols considered in oneM2M: HTTP, CoAP, WebSocket and MQTT.</p>"},{"location":"5.2/","title":"5.2 Test Configuration","text":""},{"location":"5.2/#521-ae-test-configuration","title":"5.2.1 AE Test Configuration","text":"<p>Test configurations are defined to test different entities such as CSE and AE, etc.</p> <p>Figure 5.2.1-1 shows a AE test configuration which is mapped to CF03 in clause 6.3.3.3 in oneM2M TS0015 [i.2] and aligns with conformance test system architecture in clause 6.3.3.2 in oneM2M TS-0015 [i.2].</p> <p>The TTCN-3 Test Component in Test System sends triggering actions or behaviour to the Upper Tester Application of SUT through upper tester transport link Ut while the IUT sends/receives oneM2M service primitives through Mca to/from CSE in Test System.</p> <p></p> <p>Figure 5.2.1-1: AE test configuration</p>"},{"location":"5.3/","title":"5.3 Test architecture","text":"<p>The approach for the implementation of an Abstract Protocol Tester selected in oneM2M follows the recommendation of the oneM2M Testing Framework oneM2M TS-0015 [i.2] where the TTCN-3 language and its architecture are recommended.</p> <p>Following this recommendation the oneM2M tester architecture comprises a non-platform dependent Test Suite, and a platform dependent part.</p> <p></p> <p>Note</p> <p>However, it can be implemented in a semi-independent manner, which will minimize the dependency to those elements.</p> <p>Figure 5.3-1: High level oneM2M Test Architecture</p> <ul> <li>oneM2M TTCN -3 Abstract Test Suite: the test suite is platform independent, and it is the cornerstone of the architecture. It allows a complete decoupling between the test suite and the rest of the test system. The test suite is composed of a complete set of test cases covering oneM2M requirements specified by oneM2M TS0001 [1] and oneM2M TS-0004 [2].</li> <li>oneM2M System Adaptor : this is the platform dependent part that includes adaptors and codecs (out of the scope of the present document). This part of the architecture definition depends on the specific platform (e.g. Windows or Linux) and test tool on which the tester is going to run.</li> </ul> <p>Figure 5.3-2 shows the oneM2M TTCN-3 test architecture design used for the oneM2M ATS. The Test Suite needs to interact with the System Adaptor to implement the collection of TTCN-3 test cases that are intended to be used to test the oneM2M IUTs.</p> <p>The oneM2M TTCN-3 test cases implement the test algorithms specified in the TSS&TP document oneM2M TS0018 [7], including verdict logic that allows pass/fail diagnosis.</p> <p>The test algorithms use the interfaces defined in [1] and [2] (mca, mcc) in order to:</p> <ol> <li>control the test event to be sent towards the IUT; and</li> <li>observe the test events received from the IUT.</li> </ol> <p>In TTCN-3 these two interfaces have been implemented through a set of logical TTCN-3 ports (mcaPort and mcaPortIn for mca interface, and mccPort and mccPortIn for mcc interface) which allows oneM2M message primitives exchange with the IUT.</p> <p></p> <p>Figure 5.3-2: oneM2M Test Architecture</p> <p>The oneM2M primitive messages have been mapped into TTCN-3 structure. Through this mapping, the TTCN-3 is able to build and send these messages, as well as receive them via the ports defined above.</p> <p>Additionally, the test cases are able to control and configure the test platform through a dedicated port called acPort while port utPort enables oneM2M TTCN-3 Test Component module to trigger specific action or behaviour on IUT. TTCN3 Test Components can also exchange information through a dedicated port called infoPort.</p> <p>To build up a tester, the test platform needs to be also developed (out of scope). This test platform is composed of three adaptation layers:</p> <ul> <li>PA (Platform Adaptor) layer functionality implements the communication between the TTCN-3 modules and external elements that constitute the test tool such as timers and external functions. The External functions are a powerful resources supported by TTCN-3 language. An External function is a function declared at the TTCN-3 level but implemented at the native level.</li> <li> <p>SA (System Adaptor) layer functionality is divided into two modules:</p> <ul> <li>oneM2M lower layers stack module implements the communication with the IUT and carries out the oneM2M primitives messages sent to or received from the IUT. This module is based on TCP or UDP depending on the binding supported by the IUT. The binding is a system adaptor parameter.</li> <li>Upper Tester Transport module implements functions that enable triggering specific actions or behaviour on the IUT.</li> </ul> </li> <li> <p>CODECS layer is the part of the tester to encode and decode messages between the TTCN-3 abstract internal data representation and the format required by the related base standard which the IUT understands. Several CODECS are required in oneM2M tester to cope with the bindings considered in oneM2M (HTTP, CoAP, MQTT) and the serialization methods (xml, json).</p> </li> </ul>"},{"location":"5.4/","title":"5.4 Ports and ASPs (Abstract Services Primitives)","text":""},{"location":"5.4/#540-introduction","title":"5.4.0 Introduction","text":"<p>The oneM2M ATS implements the following ports:</p> <ul> <li>The mcaPort and mcaPortIn</li> <li>The mccPort and mccPortIn</li> <li>The acPort</li> <li>The utPort</li> <li>The InfoPort</li> </ul>"},{"location":"5.4/#541-mcaport-mcaportin-mccport-mccportin","title":"5.4.1 mcaPort, mcaPortIn, mccPort, mccPortIn","text":"<p>These ports are used to send and receive the following message sets:</p> <ul> <li>Request Primitives messages in accordance with oneM2M TS-0004 [2].</li> <li>Response Primitives messages in accordance with oneM2M TS-0004 [2].</li> </ul> <p>Two primitives are currently defined for these ports indicated as table 5.4.1-1:</p> <ol> <li>The M2MRequestPrimitive - to send or receive oneM2M messages to/from the IUT. Depending on the IUT to be tested:<ol> <li>If the IUT is an AE, these messages are either received or sent by the tester which is associated with the CSE role through the mcaPortIn or the mcaPort respectively.</li> <li>If the IUT is a CSE, these messages are either sent or received by the tester when it plays the AE role through the mcaPort or the mcaPortIn respectively, or sent or received by the tester when it plays the CSE role through the mccPort or the mccPortIn respectively.</li> </ol> </li> <li>The M2MResponsePrimitive - to send or receive oneM2M messages to/from the IUT. Depending on the IUT to be tested:<ol> <li>If the IUT is an AE, these messages are either sent or received by the tester which is associated with the CSE role through the mcaPortIn or the mcaPort respectively.</li> <li>If the IUT is a CSE, these messages are either sent or received by the tester when it plays the CSE role through the mccPortIn or the mccPort respectively, sent or received by the tester when it plays the AE role through the mcaPortIn or mcaPort respectively.</li> </ol> </li> </ol> <p>Both primitives contain another parameters that permits to dynamically configure the test adaptor for every single sending. These parameters are:</p> <ul> <li>Host: IP address of the IUT</li> <li>XML Namespace</li> <li>Protocol binding</li> <li>Serialization</li> <li>ForceFields: used to force invalid or empty values to certain attributes. This behaviour shall be implemented by the System Adaptor.</li> </ul> <p>Table 5.4.1-1: Mapping of TTCN-3 Primitives to oneM2M Service Primitives</p> TTCN-3 Primitive oneM2M Message Direction IUT M2MRequestPrimitive Request Primitive <=> AE M2MRequestPrimitive Request Primitive <=> CSE M2MResponsePrimitive Response Primitive <=> AE M2MResponsePrimitive Response Primitive <=> CSE"},{"location":"5.4/#542-mcnport-mcnportin","title":"5.4.2 mcnPort, mcnPortIn","text":"<p>These ports are used to send and receive the following message sets:</p> <ul> <li>Request Primitives messages in accordance with oneM2M TS-0004 [2].</li> <li>Response Primitives messages in accordance with oneM2M TS-0004 [2].</li> </ul> <p>Two primitives are currently defined for these ports indicated:</p> <ol> <li> <p>The T8Request - to send T8 request messages to/from the IUT according to 3GPP TS 29.122 [8]. </p> </li> <li> <p>The T8Response - to receive T8 response messages to/from the IUT according to 3GPP TS 29.122 [8].</p> </li> </ol> <p>Further primitives might be defined to support other underlying networks.</p>"},{"location":"5.4/#543-mccportinternal","title":"5.4.3 mccPortInternal","text":"<p>This port is used to send and receive the following message sets between TTCN-3 components:</p> <ul> <li>Request Primitives messages in accordance with oneM2M TS-0004 [2].</li> <li>Response Primitives messages in accordance with oneM2M TS-0004 [2].</li> </ul>"},{"location":"5.4/#544-utport","title":"5.4.4 utPort","text":""},{"location":"5.4/#5440-introduction","title":"5.4.4.0 Introduction","text":"<p>The utPort is included in the oneM2M ATS in order to be able to stimulate the IUT and receive extra information from IUT upper layers. For instance, the utPort can be applied to automate AE testing shown as clause 5.4.4.1.</p>"},{"location":"5.4/#5441-usage-for-automated-ae-testing","title":"5.4.4.1 Usage for Automated AE Testing","text":"<p>The utPort is in charge of the communication between TTCN-3 Test Component module in Test System and the Upper Tester Application in SUT.</p> <p>Functionalities that TTCN-3 Test Component module and the Upper Tester Application are required to implement are listed as follows:</p> <ul> <li>TTCN-3 Test Component is able to configure the Test System and send standardized triggering commands to the SUT (Upper Tester Application).</li> <li>Upper Tester Application can process the triggering command messages received from Test System (TTCN-3 Test Component) and stimulates IUT to act following the corresponding triggering command (i.e. sending oneM2M service primitives to Test System through Mca port).</li> </ul> <p>oneM2M service Primitive defined for utPort is listed as follows:</p> <ul> <li>The UtTrigger primitive is used to trigger upper layer events in IUT (i.e. sending oneM2M service primitives to Test System through Mca port).</li> <li>The UtTriggerAck primitive is used by IUT to send acknowledgement back to the Test System.</li> </ul> <p>The Upper Tester Application in SUT can be implemented as an embedded source code. An example for implementation of automated AE test for Registration is shown as figure 5.4.4.1-1.</p> <p></p> <p>Figure 5.4.4.1-1: Example of automated AE test using Ut interface</p>"},{"location":"5.4/#5442-upper-tester-control-primitives","title":"5.4.4.2 Upper Tester Control Primitives","text":""},{"location":"5.4/#54421-introduction","title":"5.4.4.2.1 Introduction","text":"<p>The upper tester triggering message is used to transport control commands between Test System and the Upper Tester Application. The control command will contain essential parameters that are required for certain test case.</p> <p>The upper tester triggering message type maps to particular message formats for exchanging data and those message formats are defined by TTCN-3 primitive as shown at table 5.4.4.2.1-1, U tTrigger and U tTriggerAck primitive.</p> <p>Table 5.4.4.2.1-1: Mapping of TTCN-3 Primitives to oneM2M Service Primitives</p> Upper Tester Control Message Type TTCN-3 Primitives Direction Direction Trigger UtTrigger Primitive TS UT Trigger Acknowledgement UtTriggerAck Primitive UT TS"},{"location":"5.4/#54422-uttrigger-and-uttriggerack-primitives","title":"5.4.4.2.2 UtTrigger and UtTriggerAck Primitives","text":"<p>The UtTrigger primitive is initialized by the Test System to send triggering message to the target IUT as depicted in figure 5.4.4.2.2-1. The IUT will send acknowledgement message back to the Test System using UtTriggerAck primitive if trigger message is successfully transported to the IUT. Then IUT starts interaction with Test System through oneM2M request and response primitives.</p> <p></p> <p>Figure 5.4.4.2.2-1: Trigger message flow</p> <p>Table 5.4.4.2.2-1 defines UtTrigger and UtTriggerAck primitives including oneM2M data types to which are mapped as well as examples to show how to implement UtTrigger and UtTriggerAck primitives.</p> <p>Table 5.4.4.2.2-1: UtTrigger and UtTriggerAck Primitive</p> Ut Control Primitive Mapping to oneM2M data types Description Reference Triggering Message HTTP message UtTrigger Primitive requestPrimitive ONLY essential parameters included for certain test caseSee note 1 oneM2MTS-0004 [2] EXAMPLE 1:If the test objective is to test \"Test System triggers IUT to execute a test case for creation of < AE > with labels attribute under a CSEBase resource \", then the triggering message would be serialized as following. EXAMPLE 1:If the test objective is to test \"Test System triggers IUT to execute a test case for creation of < AE > with labels attribute under a CSEBase resource \", then the triggering message would be serialized as following. UtTrigger Primitive requestPrimitive ONLY essential parameters included for certain test caseSee note 1 oneM2MTS-0004 [2] Request{\"m2m:rqp\" :{ \"op\": 1, //indicate CREATE operation \"ty\": 2, //indicate AE resource type \"to\": {TEST_SYSTEM_ADDRESS}, \"pc\": { \"m2m:ae\": { \"lbl\":\"UNINITIALIZED\" //indicate that attribute labels needs to be included }, } \"rvi\": \"2a\"}} RequestPOST /{SUT_UT_APPLICATION_URL} HTTP/1.1Host : {SUT_IP_ADDRESS:PORT}Content-Length : {PAYLOAD_LENGTH}Content-Type : application/ json{\"m2m:rqp\" :{ \"op\": 1, //indicate CREATE operation \"ty\": 2, //indicate AE resource type \"to\": {TEST_SYSTEM_ADDRESS}, \"pc\": { \"m2m:ae\": { \"lbl\":\"UNINITIALIZED\" //indicate that attribute labels needs to be included } }, \"rvi\": \"2a\"}} UtTrigger Primitive requestPrimitive ONLY essential parameters included for certain test caseSee note 1 oneM2MTS-0004 [2] EXAMPLE 2: If the test objective is to test \"Test System triggers IUT to execute a test case for delete of a < AE > resource. \", then the triggering message would be serialized as following. EXAMPLE 2: If the test objective is to test \"Test System triggers IUT to execute a test case for delete of a < AE > resource. \", then the triggering message would be serialized as following. UtTrigger Primitive requestPrimitive ONLY essential parameters included for certain test caseSee note 1 oneM2MTS-0004 [2] Request{\"m2m:rqp\" :{ \"op\": 4, //indicate DELETE operation \"to\": {TARGET_AE_RESOURCE_ADDRESS}, //indicate Target AE resource address \"rvi\": \"2a\"}} RequestPOST /{SUT_UT_APPLICATION_URL} HTTP/1.1Host : {SUT_IP_ADDRESS:PORT}Content-Length : {PAYLOAD_LENGTH}Content-Type : application/ json{\"m2m:rqp\" :{ \"op\": 4, //indicate DELETE operation \"to\": {TARGET_AE_RESOURCE_ADDRESS}, //indicate Target AE resource address \"rvi\": \"2a\"}} UtTriggerPrimitive N/A Special upper tester commands N/A \"RESET\" RequestPOST /{SUT_UT_APPLICATION_URL} HTTP/1.1Host : {SUT_IP_ADDRESS:PORT}X-M2M-UTCMD: Reset UtTrigger Ack Primitive responsePrimitive ONLY responseStatusCode attribute includedSee note 2 oneM2M TS-0004 [2] Response{ \"m2m:rsp\": { \"rsc\": 2000 }}For any triggering response, it only contains a response status code, and the response status code for the triggering operation can only be set to either 2000 (OK) or 4000 (BAD_REQUEST) according to the rules for triggering operations. ResponseHTTP/1.1 200 OKX-M2M-RSC: 2000 NOTE 1: Additional rules defined in table 5.4.4.2.2-3 are also applied.NOTE 2: Attribute response status code is defined at table 5.4.4.2.2-3. NOTE 1: Additional rules defined in table 5.4.4.2.2-3 are also applied.NOTE 2: Attribute response status code is defined at table 5.4.4.2.2-3. NOTE 1: Additional rules defined in table 5.4.4.2.2-3 are also applied.NOTE 2: Attribute response status code is defined at table 5.4.4.2.2-3. NOTE 1: Additional rules defined in table 5.4.4.2.2-3 are also applied.NOTE 2: Attribute response status code is defined at table 5.4.4.2.2-3. NOTE 1: Additional rules defined in table 5.4.4.2.2-3 are also applied.NOTE 2: Attribute response status code is defined at table 5.4.4.2.2-3. NOTE 1: Additional rules defined in table 5.4.4.2.2-3 are also applied.NOTE 2: Attribute response status code is defined at table 5.4.4.2.2-3. <p>Table 5.4.4.2.2-2: Definition of special Upper Tester commands</p> Value Interpretation Reset Inidicates that the IUT should reset <p>The rules for defining UtTrigger and UtTriggerAck primitives are:</p> <ol> <li> <p>UtTrigger primitive is represented in requestPrimitive serialized in JSON format. </p> </li> <li> <p>UtTrigger primitive shall be interpreted as follows:</p> <ul> <li>Any attribute/parameter containing a value shall be present and equal in the triggered request primitive.</li> <li>Any attribute/parameter containing \"UNINITIALIZED\" value shall be present in the triggered request primitive.</li> <li>Any other attribute/parameter shall comply with oneM2M TS-0004 [2].</li> </ul> </li> <li> <p>Parameters within UtTrigger are listed as following:</p> <ul> <li>operation: (mandatory) operation type that IUT is triggered to perform.</li> <li>resourceType: (optional) resource type of a target resource against which IUT is triggered to perform certain operation</li> <li>to: (mandatory) target resource against which IUT is triggered to perform certain operation. </li> <li>primitiveContent: (optional) represents the resource attributes that shall be included in the requestPrimitive.</li> </ul> </li> </ol> <p>Table 5.4.4.2.2-3: Definition of ResponseStatusCode for UtTriggerAck primitive</p> Response Status Code Description Response Status Code Value Interpretation OK 2000 The SUT receives successfully the triggering message from Test System BAD_REQUEST 4000 The SUT does not interpret correctly the UtTrigger primitive NOTE: Only above two response status codes are allowed to use in UtTriggerAck primitive. NOTE: Only above two response status codes are allowed to use in UtTriggerAck primitive. NOTE: Only above two response status codes are allowed to use in UtTriggerAck primitive."},{"location":"5.4/#54423-control-communication-protocol","title":"5.4.4.2.3 Control Communication Protocol","text":"<p>Protocol used for proceeding communications between Test System and Upper Tester Application is designated to the Hypertext Transfer Protocol (HTTP) protocol owning it is an application protocol that is widely supported by most all IoT devices and various intrinsic features such as persistent connection, ease of programming, flexibility, etc.</p>"},{"location":"5.4/#54424-control-message-serialization","title":"5.4.4.2.4 Control Message Serialization","text":"<p>Control commands that are wrapped within a request body of HTTP message shall be serialized into JavaScript Object Notation (JSON) because it is very lightweight and easy to parse and generate for machines.</p>"},{"location":"5.4/#545-acport","title":"5.4.5 acPort","text":"<p>The acPort is included in the oneM2M ATS in order to be able to control and configure the test adaptor for specific cases.</p>"},{"location":"5.4/#546-infoport","title":"5.4.6 infoPort","text":"<p>The infoPort is included in the oneM2M ATS in order for the TTCN-3 test components to be able to exchange information such as last response primitives or request primitives received by a component, retrieved primitive contents.</p>"},{"location":"5.5/","title":"5.5 Test components","text":""},{"location":"5.5/#551-tester","title":"5.5.1 Tester","text":"<p>The Tester test component includes a set of ports, timers and variables that are common to the other defined components which are described in table 5.5.1-1.</p> <p>Table 5.5.1-1: Tester component elements</p> Name Instance type Element type Description acPort port AdapterControlPort Port that communicates with the adapter for sending configuration parameters infoPort port InfoPort Port between test components for exchanging information utPort port UpperTesterPort Port that communicates with the UT Application for triggering actions on the IUT tc_ac timer N/A Timer for the reception of a message tc_wait timer N/A Timer for the reaction of the IUT to an upper tester primitive tc_done Timer N/A Timer for waiting completion of a component behaviour vc_config variable Configurations Configuration being used for the given test case vc_testSystemRole variable TestSystemRole Role of the test component vc_componentRegistered variable boolean Flag to indicate when a component has registered to the IUT vc_resetRequired variable Boolean Flag to indicate whether a reset of the IUT is necessary vc_resourcesList variable MyResourcesList List of all resources created by the test system on the IUT vc_resourcesIndexToBeDeleted variable IntegerList List of indexes of resources created by the test system on the IUT that need to be deleted vc_acpIndex variable integer Index of accessControlPolicy resource used by the test system by default (when required) vc_request variable MsgIn Latest request primitive received/sent vc_response variable MsgIn Latest response primitive received/sent vc_aeSimu variable default Reference to the default behaviour for an AeSimu component vc_cseSimu variable default Reference to the default behaviour for an CseSimu component vc_primitiveContentRetrievedResource variable PrimitiveContent Latest content of a RETRIEVE operation vc_myInterfaces variable Interfaces Parameters for the ports of the given component:Port (mcaPort, mcaPortIn, mccPort, mccPortIn)Host (SUT IP address :port)Protocol bindingSerialization <p>Note that vc_aeSimu and vc_cseSimu are not common to the other defined test components, but those variables are required in Tester for the correct activation/deactivation of default behaviours.</p>"},{"location":"5.5/#552-aesimu","title":"5.5.2 AeSimu","text":"<p>The AeSimu test component extends the Tester component by adding elements specific to an AE entity. Table 5.5.2-1 summarizes those elements.</p> <p>Table 5.5.2-1: AeSimu component elements</p> Name Instance type Element type Description mcaPort port OneM2MPort Port that implements the mca interface when test system is the client (sending requests) mcaPortIn port OneM2MPort Port that implements the mca interface when test system is the server (receiving requests) vc_ae2 test component AeSimu Reference to the AE2 component when required vc_cse1 test component CseSimu Reference to the CSE1 component when CF02 is used vc_ae1 test component AeSimu Reference to the AE1 component when required vc_das test component AeSimu Reference to the DAS component when required vc_aeSimuDesc variable AeSimuComponentDesc Component configuration extracted from required (AE1 or AE2) tester pixit vc_dasSimuDesc variable AeSimuComponentDesc Component configuration extracted from DAS tester pixit vc_auxiliaryAe2Up variable boolean Flag to indicate that AE2 component has been started vc_aeIndex variable integer Index of the AE resource in vc_resourcesList created by AeSimu component"},{"location":"5.5/#553-csesimu","title":"5.5.3 CseSimu","text":"<p>The CseSimu test component extends the Tester component by adding elements specific to an CSE entity. Table 5.5.3-1 summarizes those elements.</p> <p>Table 5.5.3-1: CseSimu component elements</p> Name Instance type Element type Description mcaPort port OneM2MPort Port that implements the mca interface when test system is the client (sending requests) mcaPortIn port OneM2MPort Port that implements the mca interface when test system is the server (receiving requests) mccPort port OneM2MPort Port that implements the mcc interface when test system is the client (sending requests) mccPortIn port OneM2MPort Port that implements the mcc interface when test system is the server (receiving requests) mccPortInternal port OneM2MPortInternal Port that implements the mcc and mcc' interfaces between TTCN-3 components vc_ae1 test component AeSimu Reference to the AE1 component when CF02 (CseSimu as master) is used vc_cse2 test component CseSimu Reference to the CSE1 component when required vc_cseSimuDesc variable CseSimuComponentDesc Component configuration extracted from required (CSE1 or CSE2) tester pixit vc_localResourcesList variable MyResourcesList List of all resources created by the IUT on the test system vc_localCSEBaseAnncIndex variable integer Index of the CSEBaseAnnc resource corresponding to the IUT vc_localRemoteCseIndex variable integer Index of the remoteCSE resource in vc_localResourcesList representing the IUT (CSE) vc_remoteCseIndex variable integer Index of the remoteCSE resource in vc_resourcesList representing the CseSimu component vc_cSEBaseIndex variable integer Index of the CSEBase resource in vc_localResourcesList of the CseSimu component vc_cseType variable CseTypeID CSE type of the test system (default is MN) vc_auxiliaryCse2Up variable boolean Flag to indicate that CSE2 component has been started"},{"location":"5.5/#554-scefsimu","title":"5.5.4 ScefSimu","text":"<p>The ScefSimu test component extends the Tester component by adding elements specific to an SCEF entity. Table 5.5.4-1 summarizes those elements.</p> <p>Table 5.5.4-1: ScefSimu component elements</p> Name Instance type Element type Description mcnPort port OneM2MPort Port that implements the mcn interface when test system is the client (sending requests) mcnPortIn port OneM2MPort Port that implements the mcn interface when test system is the server (receiving requests) vc_ae1 test component AeSimu Reference to the AE1 component when required vc_cse2 test component CseSimu Reference to the CSE1 component when required vc_aeSimuDesc variable AeSimuComponentDesc Component configuration extracted from required (AE1) tester pixit vc_cseSimuDesc variable CseSimuComponentDesc Component configuration extracted from required (CSE1) tester pixit vc_cseType variable CseTypeID CSE type of the test system (default is MN) vc_scefSimuDesc variable ScefSimuComponentDesc Component configuration extracted from required (SCEF) tester pixit vc_configurations variable NiddConfigurations NIDD configurations of SCEF component"},{"location":"5.6/","title":"5.6 Test strategy","text":"<p>This clause introduces the test strategy being used for the TTCN-3 test cases. The chosen strategy permits to have a clear structure of the code that facilitates an easy navigation throw the different test steps.</p> <p>The use of the TTCN-3 MTC and PTC(s) is as depicted in figure 5.6-1.</p> <p></p> <p>Figure 5.6-1: Use of TTCN-3 components</p> <p>At the start of the test case execution, the MTC is created. Then, the MTC executes the following steps:</p> <ul> <li>Step 1) initialization of the master PTC.</li> <li>Step 2) initialization of some parameters if required for the permutation test cases.</li> <li> <p>Step 3) running of the appropriate function on the master PTC. The function run on the master PTC implements a given Test Purpose. Such function follows a code structure as indicated here below:</p> <ul> <li>Local Variables, declaration of local variables.</li> <li>Test Control, checking IUT capability parameters required for the proper execution of the test.</li> <li>Test Component Configuration, that initializes the given test component and other test components acting as slave PTC(s) as required by a given configuration.</li> <li>Test adapter configuration, that configures the test adapter throw the acPort if required.</li> <li>Preamble, that implements the necessary test steps as described in the Initial conditions of a Test Purpose. It may also implement additional test steps which are required for the correct execution of the test.</li> <li>Test body, that implements the test steps as described in the Expected behaviour of a Test Purpose.</li> <li>Postamble, that implements the necessary test steps to bring the IUT back to the initial state.</li> <li>Tear down, that finalizes properly the TTCN-3 ports used by the different test components depending on the configuration.</li> </ul> </li> </ul> <p>While master PTC follows the test structure described above, slave PTC(s) run only certain procedures, usually one by one, as mandated by the master PTC.</p> <p>A procedure usually implements a oneM2M request-response exchange between a given PTC and the IUT, although it can implement any other specific action (sending or reception of a message, several request-response exchanges, etc.).</p> <ul> <li>Step 4) checking of some parameters if required for the permutation test cases.</li> </ul> <p>This test strategy may slightly vary for certain cases where specific requirements need to be fulfilled.</p>"},{"location":"6/","title":"6 Untestable Test Purposes","text":"<p>Void.</p>"},{"location":"7.0/","title":"7.0 Introduction","text":"<p>The ATS conventions are intended to give a better understanding of the ATS but they also describe the conventions made for the development of the ATS. These conventions shall be considered during any later maintenance or further development of the ATS.</p> <p>The ATS conventions contain two clauses, the naming conventions and the implementation conventions. The naming conventions describe the structure of the naming of all ATS elements. The implementation conventions describe the functional structure of the ATS.</p> <p>To define the ATS, the guidelines of oneM2M TS-0015 [i.2] were considered.</p>"},{"location":"7.1/","title":"7.1 Testing conventions","text":""},{"location":"7.1/#711-testing-states","title":"7.1.1 Testing states","text":""},{"location":"7.1/#7111-initial-state","title":"7.1.1.1 Initial state","text":"<p>All test cases start with the function f_preamble_XYZ. This function brings the IUT in an \"initialized\" state by performing some actions such as registration of AE, creation of auxiliary access control policy resource, creation of additional needed resources.</p>"},{"location":"7.1/#7112-final-state","title":"7.1.1.2 Final state","text":"<p>All test cases end with the function f_postamble_XYZ. This function brings the IUT back in an \"idle\" state which means deletion of all created resources being used by the test case so that next test case execution is not disturbed.</p> <p>As necessary, further actions may be included in the f_postamble functions.</p>"},{"location":"7.2/","title":"7.2 Naming conventions","text":""},{"location":"7.2/#721-general-guidelines","title":"7.2.1 General guidelines","text":"<p>This test suite follows the naming convention guidelines provided in oneM2M TS-0015 [i.2].</p> <p>The naming convention is based on the following underlying principles:</p> <ul> <li>in most cases, identifiers should be prefixed with a short alphabetic string (specified in table 7.2.1-1) indicating the type of TTCN3 element it represents;</li> <li>suffixes should not be used except in those specific cases identified in table 7.2.1-1;</li> <li>prefixes and suffixes should be separated from the body of the identifier with an underscore (\"_\");</li> </ul> <p><code>EXAMPLE 1: c\\_sixteen, t\\_wait.</code> </p> <ul> <li>only module names, data type names and module parameters should begin with an uppercase letter. All other names (i.e. the part of the identifier following the prefix) should begin with a lowercase letter;</li> <li>the start of second and subsequent words in an identifier should be indicated by capitalizing the first character. Underscores should not be used for this purpose.</li> </ul> <p><code>EXAMPLE 2: f\\_initialState.</code> </p> <p>Table 7.2.1-1 specifies the naming guidelines for each element of the TTCN3 language indicating the recommended prefix, suffixes (if any) and capitalization.</p> <p>Table 7.2.1-1: TTCN-3 generic naming conventions</p> Language element Naming convention Prefix Example identifier Module Use upper-case initial letter none OneM2M_Templates Group within a module Use lower-case initial letter none messageGroup Data type Use upper-case initial letter none SetupContents Message template Use lower-case initial letter m_ m_setupInit Message template with wildcard or matching expression Use lower-case initial letters mw_ mw_anyUserReply Signature template Use lower-case initial letter s_ s_callSignature Port instance Use lower-case initial letter none signallingPort Test component instance Use lower-case initial letter none userTerminal Constant Use lower-case initial letter c_ c_maxRetransmission Constant (defined within component type) Use lower-case initial letter cc_ cc_minDuration External constant Use lower-case initial letter cx_ cx_macId Function Use lower-case initial letter f_ f_authentication() External function Use lower-case initial letter fx_ fx_calculateLength() Altstep (incl. Default) Use lower-case initial letter a_ a_receiveSetup() Test case Use ETSI numbering TC_ TC_COR_0009_47_ND Variable (local) Use lower-case initial letter v_ v_macId Variable (defined within a component type) Use lower-case initial letters vc_ vc_systemName Timer (local) Use lower-case initial letter t_ t_wait Timer (defined within a component) Use lower-case initial letters tc_ tc_authMin Module parameters for PICS Use all upper case letters PICS_ PICS_DOOROPEN Module parameters for other parameters Use all upper case letters PX_ PX_TESTER_STATION_ID Formal Parameters Use lower-case initial letter p_ p_macId Enumerated Values Use lower-case initial letter e_ e_syncOk"},{"location":"7.2/#722-onem2m-specific-ttcn-3-naming-conventions","title":"7.2.2 oneM2M specific TTCN-3 naming conventions","text":"<p>Next to such general naming conventions, table 7.2.2-1 shows specific naming conventions that apply to the oneM2M TTCN-3 ATS.</p> <p>Table 7.2.2-1: oneM2M specific TTCN-3 naming conventions</p> Language element Naming convention Prefix Example identifier oneM2M Module Use upper-case initial letter OneM2M_ OneM2M_Testcases_ Module containing oneM2M types Use upper-case initial letter OneM2M_Types OneM2M_Types Module containing types and values Use upper-case initial letter OneM2M_TypesAndValues OneM2M_TypesAndValues Module containing Templates Use upper-case initial letter OneM2M_Templates OneM2M_Templates Module containing test cases Use upper-case initial letter OneM2M_Testcases OneM2M_Testcases Module containing functions Use upper-case initial letter OneM2M_Functions OneM2M_Functions Module containing external functions Use upper-case initial letter OneM2M_ExternalFunctions OneM2M_ExternalFunctions Module containing components, ports and message definitions Use upper-case initial letter OneM2M_TestSystem OneM2M_TestSystem Module containing module parameters Use upper-case initial letter OneM2M_Pixits OneM2M_Pixits"},{"location":"7.2/#723-usage-of-log-statements","title":"7.2.3 Usage of Log statements","text":"<p>All TTCN-3 log statements use the following format using the same order:</p> <ul> <li>The TTCN-3 test case or function identifier in which the log statement is defined.</li> <li>One of the categories of log: INFO, WARNING, ERROR, TIMEOUT, NONE.</li> <li>Free text.</li> </ul> <p><code>EXAMPLE 1: **log** (\"f\\_utInitializeIut: INFO: IUT initialized\");</code> </p> <p>Furthermore, the following rules are applied too:</p> <ul> <li>All TTCN-3 setverdict statements are combined (as defined in TTCN-3 - ETSI ES 201 873-1 [6]) with a log statement following the same above rules (see example 2).</li> </ul> <p><code>EXAMPLE 2: **setverdict** (**pass** , \"TC\\_ONEM2M\\_CSE\\_DMR\\_CRE\\_001: Received correct message\");</code> </p>"},{"location":"7.2/#724-test-case-tc-identifier","title":"7.2.4 Test Case (TC) identifier","text":"<p>Table 7.2.4-1: TC naming convention</p> Identifier: TC_<root>_<gr>_<sgr>_<nn>_<per> <root> = root ONEM2M oneM2M <gr> = group CSE CSE testing AE AE testing <sgr> = subgroup REG Registration DMR Data Management and Repository SUB Subscription and Notification GMG Group Management DIS Discovery LOC Location DMG Device Management CMDH Communication Management and Delivery Handling SEC Security <nn> = sequential number 001 to 999 <per> = permutation P1_P2_..PN Permutation parameters <p><code>EXAMPLE: TP identifier: TP/oneM2M/CSE/DMR/CRE/001</code> <code>TC identifier: TC\\_ONEM2M\\_CSE\\_DMR\\_CRE\\_001.</code> </p>"},{"location":"7.3/","title":"7.3 IXIT","text":"<p>The following parameters are used by the oneM2M ATS for the correct execution of the test cases.</p> <p>Table 7.3-1: oneM2M ATS IXITs</p> GROUP IXIT NAME DESCRIPTION DEFAULT VALUE IutParameters PX_IN_CSE MN-CSE True IutParameters PX_MN_CSE IN-CSE False IutParameters PX_ASN_CSE ASN-CSE False IutParameters PX_SUT_ADDRESS SUT address \"127.0.0.1:8080\" IutParameters PX_UT_IMPLEMENTED Upper Tester implemented False IutParameters PX_CSE_NAME IUT CSE Name \"cseName\" IutParameters PX_CSE_ID IUT CSE-ID with SP-relative-CSE-ID format (relative) according to oneM2M TS-0001 [1], table 7.2-1 \"/cseId\" IutParameters PX_CSE_RESOURCE_ID IUT CSE resource ID with Unstructured-CSE-relative-Resource-ID (relative) format according to oneM2MTS-0001 [1], table 7.2-1 \"cseResourceId\" IutParameters PX_SP_ID IUT M2M-SP-ID with M2M-SP-ID format (absolute) according to oneM2M TS-0001 [1], table 7.2-1 Unstructured-CSE-relative -Resource-ID \"//om2m.org\" IutParameters PX_SUPER_AE_ID AE-ID with privileges to CREATE at the IUT CSEBase with AE-ID-Stem format (relative) according to oneM2M TS-0001 [1], table 7.2-1 \"admin:admin\" IutParameters PX_SUPER_CSE_ID CSE-ID with privileges to CREATE at the IUT CSEBase with SPrelative-CSE-ID format (relative) according to oneM2M TS-0001 [1], table 7.2-1 \"/admin:admin\" IutParameters PX_ALLOWED_C_AE_IDS {\"C-AllowedAeId\"} IutParameters PX_NOT_ALLOWED_C_AE_IDS {\"C-NotAllowedAeId\"} IutParameters PX_ALLOWED_S_AE_IDS {\"S-AllowedAeId\"} IutParameters PX_NOT_ALLOWED_S_AE_IDS {\"S-NotAllowedAeId\"} IutParameters PX_NOT_ALLOWED_APP_ID \"NotAllowedAppId\" IutParameters PX_ADDRESSING_METHOD Addressing method e_hierarchical IutParameters PX_PRIMITIVE_SCOPE Primitive scope e_cseRelative IutParameters PX_WS_PROTOCOL WebSocket protocol \"oneM2M.R2.0.xml\" IutParameters PX_REQUEST_URI WebSocket context \"/\" IutParameters PX_HOSTING_CSE_ID Hosting CSE-ID for MQTT \"CSE-ID\" IutParameters PX_CREDENTIAL_ID Credential-ID for MQTT \"admin:admin\" IutParameters PX_XML_NAMESPACE XML Namespace \"m2m=\"\"http://www.onem2m.org/xml/protocols\"\"\" IutParameters PX_ACOR AccessControlOriginators {\"all\"} IutParameters PX_TCONFIG_IUT Time to configure IUT after a requested action 10.0 TesterParameters PX_TS_AE1 AE1 component settings aeIdStem = \"\"appId = \"NMyApp1Id\"mcaPort and mcaPortIn settings which include per port the following info:Binding: - bindingProtocol - bindingDesc: - tsAddress - localPort - sutAddress - remotePortSerialization TesterParameters PX_TS_AE2 AE2 component settings aeIdStem = \"\"appId = \"NMyApp2Id\"mcaPort and mcaPortIn settings which include per port the following info:Binding: - bindingProtocol - bindingDesc: - tsAddress - localPort - sutAddress - remotePortSerialization TesterParameters PX_TS_CSE1 CSE1 component settings cseName = \"CSE1_NAME\"cseId = \"/CSE1_ID\"cseResourceId = \"CSE1_RESOURCE_ID\"spId = \"//onem2m.org\"supportedResourceType = {int1, int2, int3, int16}mcaPort, mcaPortIn, mccPort and mccPortIn settings which include per port the following info:Binding: - bindingProtocol - bindingDesc: - tsAddress - localPort - sutAddress - remotePortSerialization TesterParameters PX_TS_CSE2 CSE2 component settings cseName = \"CSE2_NAME\"cseId = \"/CSE2_ID\"cseResourceId = \"CSE2_RESOURCE_ID\"spId = \"//onem2m.org\"supportedResourceType = {int1, int2, int3, int16}mcaPort, mcaPortIn, mccPort and mccPortIn settings which include per port the following info:Binding: - bindingProtocol - bindingDesc: - tsAddress - localPort - sutAddress - remotePortSerialization PX_TS_DAS DAS1 component settings aeIdStem = \"\"appId = \"\"mcaPort and mcaPortIn settings which include per port the following info:Binding: - bindingProtocol - bindingDesc: - tsAddress - localPort - sutAddress - remotePortSerialization PX_TS_UT UpperTester settings url = \"http://127.0.0.1:43000/\" ExecutionParameters PX_RESOURCES_TO_BE_DELETED (For debugging purposes) {\"MyAe\", \"MyAccessControlPolicyResource\", \"SubscriptionVerificationAcp\", \"MyAcp\", \"MyRemoteCSEResource\"} ExecutionParameters PX_RUN_POSTAMBLE (For debugging purposes) true ExecutionParameters PX_CERTIFICATE_PATH charstring \"\" ExecutionParameters PX_CERTIFICATE_NAME charstring \"\" ExecutionParameters PX_PAIRWISEKEY_METHOD PairwiseKeyMethod e_establish ExecutionParameters PX_KEY_PROVISION Provisioned e_preProvisioning"},{"location":"8/","title":"8 TTCN-3 Verifications","text":"<p>The principles for Verifying the TTCN-3 test code are given in oneM2M TS-0015 [i.2].</p> <p>All test cases provided with the present document in annex A which correspond to at least one of the product profiles defined in oneM2M TS-0025 [i.3] have been verified at the time of publication of the present document which corresponds with the TTCN-3 code gitlab tag provided in annex A.</p>"},{"location":"A.1/","title":"A.1 Electronic annex, zip file with TTCN-3 code","text":"<p>This ATS has been produced using the Testing and Test Control Notation (TTCN) according to ETSI ES 201 873-1 [6].</p> <p>This test suite has been compiled error-free using two different commercial TTCN-3 compilers.</p> <p>The TTCN-3 library modules, which form parts of the present document, are contained in the following gitLab tag:</p> <p>https://git.onem2m.org/TST/ATS/-/tags/TS-0019-baseline-v4_1_1 </p> <p></p>"},{"location":"B/","title":"Annex B (informative): Bibliography","text":"<p>ISO/IEC 9646-6 (1994): \"Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 6: Protocol profile test specification\".</p> <p>oneM2M TS-0017: \"Implementation Conformance Statement\".</p> <p>oneM2M TS-0031: \"Feature catalogue\".</p>"},{"location":"download/","title":"Download","text":"<p>Download baseline for TS-0019 version v4.1.1:</p> <p></p>"}]}
\ No newline at end of file
diff --git a/public/v4.1.1/sitemap.xml b/public/v4.1.1/sitemap.xml
index 9755964bb4d35f870e3d6fa4ae34797eb4e593cc..2247036d169414af9a31f2506bf1a9f2ce610533 100644
--- a/public/v4.1.1/sitemap.xml
+++ b/public/v4.1.1/sitemap.xml
@@ -1,115 +1,115 @@
<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
<url>
- <loc>https://specifications.onem2m.org/ts-0019/v4.1.1/</loc>
- <lastmod>2024-11-14</lastmod>
+ <loc>https://specifications.onem2m.org/v4.1.1/</loc>
+ <lastmod>2024-11-15</lastmod>
</url>
<url>
- <loc>https://specifications.onem2m.org/ts-0019/v4.1.1/0/</loc>
- <lastmod>2024-11-14</lastmod>
+ <loc>https://specifications.onem2m.org/v4.1.1/0/</loc>
+ <lastmod>2024-11-15</lastmod>
</url>
<url>
- <loc>https://specifications.onem2m.org/ts-0019/v4.1.1/1/</loc>
- <lastmod>2024-11-14</lastmod>
+ <loc>https://specifications.onem2m.org/v4.1.1/1/</loc>
+ <lastmod>2024-11-15</lastmod>
</url>
<url>
- <loc>https://specifications.onem2m.org/ts-0019/v4.1.1/2.1/</loc>
- <lastmod>2024-11-14</lastmod>
+ <loc>https://specifications.onem2m.org/v4.1.1/2.1/</loc>
+ <lastmod>2024-11-15</lastmod>
</url>
<url>
- <loc>https://specifications.onem2m.org/ts-0019/v4.1.1/2.2/</loc>
- <lastmod>2024-11-14</lastmod>
+ <loc>https://specifications.onem2m.org/v4.1.1/2.2/</loc>
+ <lastmod>2024-11-15</lastmod>
</url>
<url>
- <loc>https://specifications.onem2m.org/ts-0019/v4.1.1/2/</loc>
- <lastmod>2024-11-14</lastmod>
+ <loc>https://specifications.onem2m.org/v4.1.1/2/</loc>
+ <lastmod>2024-11-15</lastmod>
</url>
<url>
- <loc>https://specifications.onem2m.org/ts-0019/v4.1.1/3.1/</loc>
- <lastmod>2024-11-14</lastmod>
+ <loc>https://specifications.onem2m.org/v4.1.1/3.1/</loc>
+ <lastmod>2024-11-15</lastmod>
</url>
<url>
- <loc>https://specifications.onem2m.org/ts-0019/v4.1.1/3.2/</loc>
- <lastmod>2024-11-14</lastmod>
+ <loc>https://specifications.onem2m.org/v4.1.1/3.2/</loc>
+ <lastmod>2024-11-15</lastmod>
</url>
<url>
- <loc>https://specifications.onem2m.org/ts-0019/v4.1.1/3/</loc>
- <lastmod>2024-11-14</lastmod>
+ <loc>https://specifications.onem2m.org/v4.1.1/3/</loc>
+ <lastmod>2024-11-15</lastmod>
</url>
<url>
- <loc>https://specifications.onem2m.org/ts-0019/v4.1.1/4/</loc>
- <lastmod>2024-11-14</lastmod>
+ <loc>https://specifications.onem2m.org/v4.1.1/4/</loc>
+ <lastmod>2024-11-15</lastmod>
</url>
<url>
- <loc>https://specifications.onem2m.org/ts-0019/v4.1.1/5.1/</loc>
- <lastmod>2024-11-14</lastmod>
+ <loc>https://specifications.onem2m.org/v4.1.1/5.1/</loc>
+ <lastmod>2024-11-15</lastmod>
</url>
<url>
- <loc>https://specifications.onem2m.org/ts-0019/v4.1.1/5.2/</loc>
- <lastmod>2024-11-14</lastmod>
+ <loc>https://specifications.onem2m.org/v4.1.1/5.2/</loc>
+ <lastmod>2024-11-15</lastmod>
</url>
<url>
- <loc>https://specifications.onem2m.org/ts-0019/v4.1.1/5.3/</loc>
- <lastmod>2024-11-14</lastmod>
+ <loc>https://specifications.onem2m.org/v4.1.1/5.3/</loc>
+ <lastmod>2024-11-15</lastmod>
</url>
<url>
- <loc>https://specifications.onem2m.org/ts-0019/v4.1.1/5.4/</loc>
- <lastmod>2024-11-14</lastmod>
+ <loc>https://specifications.onem2m.org/v4.1.1/5.4/</loc>
+ <lastmod>2024-11-15</lastmod>
</url>
<url>
- <loc>https://specifications.onem2m.org/ts-0019/v4.1.1/5.5/</loc>
- <lastmod>2024-11-14</lastmod>
+ <loc>https://specifications.onem2m.org/v4.1.1/5.5/</loc>
+ <lastmod>2024-11-15</lastmod>
</url>
<url>
- <loc>https://specifications.onem2m.org/ts-0019/v4.1.1/5.6/</loc>
- <lastmod>2024-11-14</lastmod>
+ <loc>https://specifications.onem2m.org/v4.1.1/5.6/</loc>
+ <lastmod>2024-11-15</lastmod>
</url>
<url>
- <loc>https://specifications.onem2m.org/ts-0019/v4.1.1/5/</loc>
- <lastmod>2024-11-14</lastmod>
+ <loc>https://specifications.onem2m.org/v4.1.1/5/</loc>
+ <lastmod>2024-11-15</lastmod>
</url>
<url>
- <loc>https://specifications.onem2m.org/ts-0019/v4.1.1/6/</loc>
- <lastmod>2024-11-14</lastmod>
+ <loc>https://specifications.onem2m.org/v4.1.1/6/</loc>
+ <lastmod>2024-11-15</lastmod>
</url>
<url>
- <loc>https://specifications.onem2m.org/ts-0019/v4.1.1/7.0/</loc>
- <lastmod>2024-11-14</lastmod>
+ <loc>https://specifications.onem2m.org/v4.1.1/7.0/</loc>
+ <lastmod>2024-11-15</lastmod>
</url>
<url>
- <loc>https://specifications.onem2m.org/ts-0019/v4.1.1/7.1/</loc>
- <lastmod>2024-11-14</lastmod>
+ <loc>https://specifications.onem2m.org/v4.1.1/7.1/</loc>
+ <lastmod>2024-11-15</lastmod>
</url>
<url>
- <loc>https://specifications.onem2m.org/ts-0019/v4.1.1/7.2/</loc>
- <lastmod>2024-11-14</lastmod>
+ <loc>https://specifications.onem2m.org/v4.1.1/7.2/</loc>
+ <lastmod>2024-11-15</lastmod>
</url>
<url>
- <loc>https://specifications.onem2m.org/ts-0019/v4.1.1/7.3/</loc>
- <lastmod>2024-11-14</lastmod>
+ <loc>https://specifications.onem2m.org/v4.1.1/7.3/</loc>
+ <lastmod>2024-11-15</lastmod>
</url>
<url>
- <loc>https://specifications.onem2m.org/ts-0019/v4.1.1/7/</loc>
- <lastmod>2024-11-14</lastmod>
+ <loc>https://specifications.onem2m.org/v4.1.1/7/</loc>
+ <lastmod>2024-11-15</lastmod>
</url>
<url>
- <loc>https://specifications.onem2m.org/ts-0019/v4.1.1/8/</loc>
- <lastmod>2024-11-14</lastmod>
+ <loc>https://specifications.onem2m.org/v4.1.1/8/</loc>
+ <lastmod>2024-11-15</lastmod>
</url>
<url>
- <loc>https://specifications.onem2m.org/ts-0019/v4.1.1/A.1/</loc>
- <lastmod>2024-11-14</lastmod>
+ <loc>https://specifications.onem2m.org/v4.1.1/A.1/</loc>
+ <lastmod>2024-11-15</lastmod>
</url>
<url>
- <loc>https://specifications.onem2m.org/ts-0019/v4.1.1/A/</loc>
- <lastmod>2024-11-14</lastmod>
+ <loc>https://specifications.onem2m.org/v4.1.1/A/</loc>
+ <lastmod>2024-11-15</lastmod>
</url>
<url>
- <loc>https://specifications.onem2m.org/ts-0019/v4.1.1/B/</loc>
- <lastmod>2024-11-14</lastmod>
+ <loc>https://specifications.onem2m.org/v4.1.1/B/</loc>
+ <lastmod>2024-11-15</lastmod>
</url>
<url>
- <loc>https://specifications.onem2m.org/ts-0019/v4.1.1/download/</loc>
- <lastmod>2024-11-14</lastmod>
+ <loc>https://specifications.onem2m.org/v4.1.1/download/</loc>
+ <lastmod>2024-11-15</lastmod>
</url>
</urlset>
\ No newline at end of file
diff --git a/public/v4.1.1/sitemap.xml.gz b/public/v4.1.1/sitemap.xml.gz
index 05c7954fc1eb65c13ad2c883019e8864d5a71de6..a864394ba9bef4ccf742e8413176756826bcd127 100644
Binary files a/public/v4.1.1/sitemap.xml.gz and b/public/v4.1.1/sitemap.xml.gz differ
diff --git a/public/versions.json b/public/versions.json
index a1cc85fcbb877348eec17d2dab66158e10ba6af8..804b8456e102e084158e8d0afb6440be53edf0c8 100644
--- a/public/versions.json
+++ b/public/versions.json
@@ -7,10 +7,7 @@
{
"version": "v4.2.0",
"title": "v4.2.0",
- "aliases": [
- "latest",
- "latestR4"
- ],
+ "aliases": [],
"properties": {
"hidden": false
}
@@ -18,7 +15,10 @@
{
"version": "v4.1.1",
"title": "v4.1.1",
- "aliases": [],
+ "aliases": [
+ "latestR4",
+ "latest"
+ ],
"properties": {
"hidden": false
}