1
2
3
O NE M2M
T E C H NI C AL S P E CI FI C AT I O N
Document Number
oneM2M-TS-0019-V-0.0.1
Document Name:
Abstract Test Suite and Implementation eXtra Information for Test
Date:
2014-April-15
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 (Dot not modify)
4
5
6
7
8
9
10
11
This Specification is provided for future development work within oneM2M only. The Partners accept no
liability for any use of this Specification.
12
13
14
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.
15
16
17
© oneM2M Partners Type 1 (ARIB, ATIS, CCSA, ETSI, TIA, TSDSI, TTA, TTC)
Page 1 of 8
This is a draft oneM2M document and should not be relied upon; the final version, if any, will be made available by oneM2M Partners Type 1.
18
About oneM2M
19
20
21
22
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.
23
More information about oneM2M may be found at: http//www.oneM2M.org
24
Copyright Notification
25
© 2015, oneM2M Partners Type 1 (ARIB, ATIS, CCSA, ETSI, TIA, TSDSI, TTA, TTC).
26
All rights reserved.
27
The copyright extends to reproduction in all media.
28
29
Notice of Disclaimer & Limitation of Liability
30
31
32
33
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.
34
35
36
37
38
39
40
41
42
43
44
45
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.
46
© oneM2M Partners Type 1 (ARIB, ATIS, CCSA, ETSI, TIA, TSDSI, TTA, TTC)
Page 2 of 8
This is a draft oneM2M document and should not be relied upon; the final version, if any, will be made available by oneM2M Partners Type 1.
47
Contents
48
Contents .............................................................................................................................................................. 3
49
*1
Scope ........................................................................................................................................................ 3
50
51
52
2
References ................................................................................................................................................ 4
53
54
55
56
57
3
58
4
Conventions.............................................................................................................................................. 6
59
60
61
62
63
5
Abstract Test Method (ATM) .................................................................................................................. 6
64
6
Untestable Test Purposes ......................................................................................................................... 6
65
66
67
68
7
ATS Conventions ..................................................................................................................................... 6
69
70
Proforma copyright release text block ............................................................................................................... 7
71
Annex <y>: Bibliography ................................................................................................................................. 8
72
73
History ................................................................................................................................................................ 8
74
2.1
2.2
3.1
3.2
3.3
3.4
5.1
5.2
5.3
5.4
7.1
7.2
7.3
Normative references ......................................................................................................................................... 4
Informative references ....................................................................................................................................... 4
Definitions, symbols and abbreviations ................................................................................................... 4
Definitions ......................................................................................................................................................... 4
Symbols ............................................................................................................................................................. 5
Abbreviations ..................................................................................................................................................... 5
Acronyms ........................................................................................................................................................... 5
Abstract protocol tester ...................................................................................................................................... 6
Test Configuration ............................................................................................................................................. 6
Test architecture................................................................................................................................................. 6
Ports and ASPs (Abstract Services Primitives) .................................................................................................. 6
Testing conventions ........................................................................................................................................... 6
Naming conventions .......................................................................................................................................... 6
IXIT ................................................................................................................................................................... 6
Annexes 7
*
© oneM2M Partners Type 1 (ARIB, ATIS, CCSA, ETSI, TIA, TSDSI, TTA, TTC)
Page 3 of 8
This is a draft oneM2M document and should not be relied upon; the final version, if any, will be made available by oneM2M Partners Type 1.
1 Scope
75
76
The present document …
77
EXAMPLE:
The present document provides the necessary adaptions to the endorsed document.
78
The Scope shall not contain requirements.
79
2
80
The following text block applies.
81
82
83
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references,only the cited version applies. For non-specific references, the latest version of the
referenced document (including any amendments) applies.
84
2.1
85
86
Clause 2.1 only shall contain normative (essential) references which are cited in the document itself. These references
have to be publicly available and in English.
87
The following referenced documents are necessary for the application of the present document.
References
Normative references
88
89
90

91
EXAMPLE:
92
[1]
Use the EX style, enclose the number in square brackets and separate it from the title with a tab (you may use
sequence fields for automatically numbering references, see clause A.4: "Sequence numbering") (see
example).
ETSI TR 102 473: "<Title>".
93
2.2
94
Clause 2.2 shall only contain informative references which are cited in the document itself.
95
96
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.

97
98
99
100
101
[i.1]
Informative references
Use the EX style, add the letter "i" (for informative) before the number (which shall be in square brackets) and
separate this from the title with a tab (you may use sequence fields for automatically numbering references).
oneM2M Drafting Rules
(http://member.onem2m.org/Static_pages/Others/Rules_Pages/oneM2M-Drafting-RulesV1_0.doc)
102
3
Definitions, symbols and abbreviations
103
Delete from the above heading the word(s) which is/are not applicable.
104
3.1
Definitions
105
106
107
Clause numbering depends on applicability.

A definition shall not take the form of, or contain, a requirement.
© oneM2M Partners Type 1 (ARIB, ATIS, CCSA, ETSI, TIA, TSDSI, TTA, TTC)
Page 4 of 8
This is a draft oneM2M document and should not be relied upon; the final version, if any, will be made available by oneM2M Partners Type 1.
108
109

The form of a definition shall be such that it can replace the term in context. Additional information
shall be given only in the form of examples or notes (see below).
110

The terms and definitions shall be presented in alphabetical order.
111
For the purposes of the present document, the [following] terms and definitions [given in ... and the following] apply:
112
Definition format
113
<defined term>: <definition>
114
115
If a definition is taken from an external source, use the format below where [N] identifies the external document which
must be listed in Section 2 References.
116
<defined term>[N]: <definition>
117
example 1: text used to clarify abstract rules by applying them literally
118
NOTE:
This may contain additional information.
119
3.2
120
Clause numbering depends on applicability.
121
For the purposes of the present document, the [following] symbols [given in ... and the following] apply:
122
Symbol format
123
124
125
Symbols
<symbol>
<2nd symbol>
<3rd symbol>
<Explanation>
<2nd Explanation>
<3rd Explanation>
126
3.3
127
Abbreviations should be ordered alphabetically.
128
Clause numbering depends on applicability.
129
For the purposes of the present document, the [following] abbreviations [given in ... and the following] apply:
130
Abbreviation format
131
132
133
Abbreviations
<ABREVIATION1> <Explanation>
<ABREVIATION2> <Explanation>
<ABREVIATION3> <Explanation>
134
3.4
135
Acronyms should be ordered alphabetically.
136
Clause numbering depends on applicability.
137
For the purposes of the present document, the [following] abbreviations [given in ... and the following] apply:
138
Acronym format
139
140
141
Acronyms
<ACRONYM1> <Explanation>
<ACRONYM2> <Explanation>
<ACRONYM3> <Explanation>
142
© oneM2M Partners Type 1 (ARIB, ATIS, CCSA, ETSI, TIA, TSDSI, TTA, TTC)
Page 5 of 8
This is a draft oneM2M document and should not be relied upon; the final version, if any, will be made available by oneM2M Partners Type 1.
143
4
Conventions
144
145
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]
146
5
Abstract Test Method (ATM)
147
5.1
Abstract protocol tester
148
5.2
Test Configuration
149
5.3
Test architecture
150
5.4
Ports and ASPs (Abstract Services Primitives)
6
Untestable Test Purposes
157
7
ATS Conventions
158
7.1
Testing conventions
159
7.2
Naming conventions
160
7.3
IXIT
151
152
153
154
155
156
161
162
163
164
165
166
167
© oneM2M Partners Type 1 (ARIB, ATIS, CCSA, ETSI, TIA, TSDSI, TTA, TTC)
Page 6 of 8
This is a draft oneM2M document and should not be relied upon; the final version, if any, will be made available by oneM2M Partners Type 1.
168
169
Proforma copyright release text block
170
171
This text box shall immediately follow after the heading of an element (i.e. clause or annex) containing a proforma or
template which is intended to be copied by the user. Such an element shall always start on a new page.
172
173
174
Notwithstanding the provisions of the copyright clause related to the text of the present document, oneM2M grants that
users of the present document may freely reproduce the <proformatype> proforma in this {clause|annex} so that it can
be used for its intended purposes and may further publish the completed <proformatype>.
175
<PAGE BREAK>
176
Annexes
177
Each annex shall start on a new page (insert a page break between annexes A and B, annexes B and C, etc.).
178
Use the Heading 9 style for the title and the Normal style for the text.
179
Annex A (Normative): TTCN-3 library modules
180
<Text>
181
A.1
Electronic annex, zip file with TTCN-3 code
182
183
<PAGE BREAK>
184
Annex B (Normative): IXIT proforma
185
<Text>
186
B.1
187
<Text>
188
B.1.1
189
<Text>
190
<PAGE BREAK>
First clause of the annex
First subdivided clause of the annex (style H2)
© oneM2M Partners Type 1 (ARIB, ATIS, CCSA, ETSI, TIA, TSDSI, TTA, TTC)
Page 7 of 8
This is a draft oneM2M document and should not be relied upon; the final version, if any, will be made available by oneM2M Partners Type 1.
191
The following text is to be used when appropriate:
193
Annex <y>:
Bibliography
194
The annex entitled "Bibliography" is optional.
195
196
It shall contain a list of standards, books, articles, or other sources on a particular subject which are not mentioned in the
document itself
197
It shall not include references mentioned in the document.
198
Use the Heading 9 style for the title and B1+ or Normal for the text.
192

199
<Publication>: "<Title>".
200
OR
201
<Publication>: "<Title>".
202
<PAGE BREAK>
203
History
204
205
This clause shall be the last one in the document and list the main phases (all additional information will be removed at
the publication stage).
Publication history
V1.1.1
<dd-Mmm-yyyy> <Milestone>
206
207
208
Draft history (to be removed on publication)
V.1.1.1
<dd Mmm yyyy> <CR ID> applied – <Summary of changes>
209
210
© oneM2M Partners Type 1 (ARIB, ATIS, CCSA, ETSI, TIA, TSDSI, TTA, TTC)
Page 8 of 8
This is a draft oneM2M document and should not be relied upon; the final version, if any, will be made available by oneM2M Partners Type 1.