7.1 Introduction
7.1.1 TP definition conventions
The TP definition is constructed according to Test Suite Structure & Test Purposes(TSS&TP) in Testing Framework(TS-0015 [3]).
7.1.2 TP Identifier naming conventions
The identifier of the TP is constructed according to table 7.1.2-1.
Table 7.1.2-1: TP naming convention for oneM2M
|
Name |
Option |
Interpretation |
|---|---|---|
|
TP/<root>/<ent>/<gr>[/<sgr>][/<opr>]/<nnn>_<pmu> |
||
|
<root> = root |
oneM2M |
oneM2M |
|
<ent> = entity |
AE |
Application Entity |
|
CSE |
Common Services Entity |
|
|
<gr> = group |
GEN |
Common Service Function |
|
REG |
||
|
DMR |
||
|
SUB |
||
|
GMG |
||
|
DIS |
||
|
LOC |
||
|
DMG |
||
|
CMDH |
||
|
SEC |
||
|
ANNC |
||
|
FLXC |
||
|
DAU |
||
|
SEM |
||
|
ISP |
||
|
<sgr> = sub-group |
ACP |
AccessControlPolicy |
|
<opr> = operation |
CRE |
Create |
|
UPD |
Update |
|
|
RET |
Retrieve |
|
|
DEL |
Delete |
|
|
NTF |
Notify |
|
|
<nnn> = sequential number |
001 to 999 |
023 |
|
<pmu> = permutation part |
May be number, short name of attribute or resource type depending on the permutated part in the TP. If there are more than one permutated variables, they should be separated by slash '/'. |
Enumerated type attribute and its value is represented as <VARIABLE_1>/<VALUE>, e.g. TP/oneM2M/CSE/DMR/RET/020_RCN/0 |
7.1.3 Rules for the behaviour description
The description of the TP is built according to TS-0015 [3] Testing Framework.
In addition, the following rules apply:
Primitive parameters shall use their Parameter name as indicated in TS-0004 [2] table 8.2.2-1
Resource attributes shall use their Attribute name as indicated in TS-0004 [2] tables 8.2.3 followed by "attribute".
When_Content_ request parameter contains a resource representation, such representation shall contain all mandatory attributes and could contain some optional attributes. Only those attributes and/or child resources required by the test purpose will be explicitly indicated.
When_Content_ response parameter contains a resource representation, such representation shall contain attributes and/or child resources according to the Result Content parameter of the corresponding request. Only those attributes and/or child resources required by the test purpose will be explicitly indicated.
7.1.4 ICS reference
|
Item |
Name of field |
Reference |
Status |
Support |
|---|---|---|---|---|
|
1 |
ASN (Application Service Node) |
5.1.2 |
o.1 |
|
|
2 |
ADN (Application Dedicated Node) |
5.1.2 |
o.1 |
|
|
3 |
IN (Infrastructure Node) |
5.1.2 |
o.1 |
|
|
4 |
MN (Middle Node) |
5.1.2 |
o.1 |
|
|
o.1: Exactly one item shall be supported |
||||
Table 7.1.4-2: Functional entity type
|
Prerequisite: A.1 |
||||
|---|---|---|---|---|
|
Item |
Name of field |
Reference |
Status |
Support |
|
1 |
AE |
5.1.1 |
c.1 |
|
|
2 |
CSE |
5.1.1 |
c.2 |
|
|
c.1: If A.1-1 or A.1-2 then m else o |
||||