|_REG_ |_AE/REG/00002_ |_AE/REG/00002/00001_ |Create <AE> with mandatory attributes |
|_DMR_ |_AE/DMR/00001_ |_AE/DMR/00001/00001_ |Create <container> with no attribute set |
| |_AE/DMR/00002_ |_AE/DMR/00002/00001_ |Create <contentInstance> with mandatory attributes |
|_SUB_ |_AE/SUB/00004_ |_AE/SUB/00004/00001_ |Receiving a notification |
...
...
@@ -246,7 +246,6 @@ oneM2M provides serveral logical entity concepts called 'Node' to explain oneM2M
This ADN Profile 1 defines set of common features which could be used for small originator device types of oneM2M services.
### 5.5.2 Profile usage examples
ADN Profile 1 could be the basic profile of oneM2M devices like sensor, actuator etc. And also this profile could be used independently when developers want to implement oneM2M device with special functions.
...
...
@@ -260,129 +259,61 @@ Table 5.5.3-1: Feature set for ADN Profile 4 GEN
|_AE/GEN/00001_ |At least one |Support one of the format of resource identification |
|_AE/GEN/00002_ |_AE/GEN/00002/00001_ |Support Create request targeting one resource |
| |_AE/GEN/00002/00002_ |Support Retrieve request targeting one resource |
| |_CE/REG/00002/00002_ |AE registration/de-registration without a pre-assigned AE-ID in the registration request and where the AE-ID Stem is configured with 'C'. |
| |_CE/REG/00002/00003_ |AE registration/de-registration without a pre-assigned AE-ID in the registration request and where the AE-ID Stem is configured with 'S'. |
| |_CE/REG/00002/00004_ |AE registration/de-registration without a pre-assigned AE-ID in the registration request and where no AE-ID Stem is included. |
| |_CE/REG/_ _00_ _002_ _/_ _0000_ _7_ |Support the _applicationName_ attribute of <AE> resource |
| |_CE/REG/_ _0_ _00_ _02_ _/_ _0000_ _8_ |Support the _pointOfAccess_ attribute of <AE> resource |
| |_CE/REG/00002/0000_ _9_ |AE registration with pre-assigned AE-ID |
| |_CE/DMR/00002/00001_ |Support the _creator_ attribute of <contentInstance> resource |
| |_CE/DMR/00002/00002_ |Support the _contentInfo_ attribute of <contentInstance> resource |
| |_CE/DMR/00002/00004_ |Retrieve and Delete of latest <contentInstance> resource by <latest> virtual resource |
| |_CE/DMR/00002/00057_ |Retrieve and Delete of oldest <contentInstance> resource by <oldest> virtual resource |
|_CE/DMR/00003_ |_CE/DMR/00003/00001_ |Support CRUD of <flexcontainer> resource |
Table 5.6.3-4: Fundamental feature set for IN Profile SUB
|**Feature Set** |**Feature** |**Re****mark** |
|**Feature Set** |**Feature** |**Remark** |
|-|-|-|
|_CE/SUB/00001_ |_CE/SUB/00001/00001_ |The Support of <subscription> resource with attributes multiplicity equals 1<ahref="#_ref_1">[1]</a> |
| |_CE/SUB/00001/00001_ |Support the _creator_ attribute of <subscription> resource |
| |_CE/SUB/00001/00001_ |Support the _subscriberURI_ attribute of <subscription> resource |
|_CE/SUB/0000_ _4_ |_CE/SUB/0000_ _4_ _/00001_ |Notify the address indicated in _notificationURI_ with notification elements multiplicity equals 1<ahref="#_ref_2">[2]</a> |
| |_CE/SUB/0000_ _4_ _/00002_ |Notify with notificationEvent/representation set in the notification |
| |_CE/SUB/0000_ _4_ _/0000_ _3_ |Notify with creator set in the notification |
|_CE/SUB/00004_ |_CE/SUB/00004/00001_ |Notify the address indicated in _notificationURI_ with notification elements multiplicity equals 1<ahref="#_ref_2">[2]</a> |
| |_CE/SUB/00004/00002_ |Notify with notificationEvent/representation set in the notification |
| |_CE/SUB/00004/00003_ |Notify with creator set in the notification |
Table 5.6.3-5: Fundamental feature set for IN Profile SEC
|_CE/SEC/00002_ |_CE/SEC/00002/00001_ |Support _accessControlPolicyIDs_ attribute for <resource> that the Implementation supports. |
| |_CE_ _/_ _SEC_ _/00_ _00_ _2/_ _0000_ _2_ |Support access control decision and enforcement making on the Hosting CSE |
| |_CE/SEC/00002/00002_ |Support access control decision and enforcement making on the Hosting CSE |
Table 5.6.3-6: Fundamental feature set for IN Profile GMG
|**Feature Set** |**Feature** |**Re****mark** |
|**Feature Set** |**Feature** |**Remark** |
|-|-|-|
|_CE/GMG/00001_ |_CE/GMG/00001_ _/_ _00001_ |Support the <group> resource with attributes multiplicity equals 1<ahref="#_ref_1">[1]</a> Support <group> resource with MIXED memberType |
|_CE/GMG/0000_ _2_ |_CE_ _/_ _GMG_ _/0000_ _2/_ _0000_ _1_ |Support <group> resource with single specific resource typesSupport _consistencyStrategy_ |
|_CE/GMG/0000_ _3_ |_CE_ _/_ _GMG_ _/00003_ _/00001_ |Fan out of request to all members |
|_CE/GMG/00001_ |_CE/GMG/00001/00001_ |Support the <group> resource with attributes multiplicity equals 1<ahref="#_ref_1">[1]</a> Support <group> resource with MIXED memberType |
|_CE/GMG/00002_ |_CE/GMG/00002/00001_ |Support <group> resource with single specific resource typesSupport _consistencyStrategy_ |
|_CE/GMG/00003_ |_CE/GMG/00003/00001_ |Fan out of request to all members |
Table 5.6.3-7: Fundamental feature set for IN Profile DIS
|**Feature Set** |**Feature** |**Re****mark** |
|**Feature Set** |**Feature** |**Remark** |
|-|-|-|
|_CE/DIS/00001_ |_CE/_ _DIS_ _/00001/00001_ |Support the Discovery request with filterUsage equals to "Discovery" |
**Table 5.7.3-2: Fundamental feature sets for constrained sensor as ASN REG**<aname="table_5.7.3-2"></a>
|**Feature Set** |**Feature** |**Re****mark** |
|**Feature Set** |**Feature** |**Remark** |
|-|-|-|
|_CE/REG/0000_ _5_ |_CE/REG/0000_ _5/00001_ |The Creation with <remoteCSE> resource for CSE registration with mandatory attributes<ahref="#_ref_2">[2]</a> |
| |_CE/REG/0000_ _5_ _/0000_ _6_ |Create the <remoteCSE> with _point_ _O_ _f_ _A_ _ccess_ |
|_CE/REG/00005_ |_CE/REG/00005/00001_ |The Creation with <remoteCSE> resource for CSE registration with mandatory attributes<ahref="#_ref_2">[2]</a> |
| |_CE/REG/00005/00006_ |Create the <remoteCSE> with _pointOfAccess_ |
**Table 5.7.3-3: Fundamental feature sets for constrained sensor as ASN DMR**<aname="table_5.7.3-3"></a>
@@ -661,132 +491,107 @@ Head unit in connected vehicles:
Sensors and actuators in the car are connected with the head unit. The sensed data and control command are reported to delivered through the head unit. Applications may access the head unit and monitor the car state via the platform. Applications may also access the head unit once connected directly with the head unit via area network such as Wifi or Bluetooth.
### 5.8.3 Fundamental feature sets
**Table 5.8.3-1: Fundamental feature sets for gateway as MN GEN**<aname="table_5.8.3-1"></a>
|**Feature Set** |**Feature** |**Re****mark** |
|**Feature Set** |**Feature** |**Remark** |
|-|-|-|
|_CE/GEN/00001_ |_CE/GEN/00001_ _/00001_ |Unstructured resource id |
| |_CE/GEN/00001_ _/00002_ |Structured resource id |
| |_CE/REG/_ _00_ _001_ _/_ _0000_ _2_ |Support the _cseType_ attribute of <CSEBase> resource |
| |_CE/REG/_ _00_ _001_ _/_ _0000_ _3_ |Support the _nodeLink_ attribute of <CSEBase> resource. This is dependent on the feature set for <node> resource. |
| |_CE/REG/00002/00002_ |AE registration/de-registration without a pre-assigned AE-ID in the registration request and where the AE-ID Stem is configured with 'C'. |
| |_CE/REG/00002/00003_ |AE registration/de-registration without a pre-assigned AE-ID in the registration request and where the AE-ID Stem is configured with 'S'. |
| |_CE/REG/00002/00004_ |AE registration/de-registration without a pre-assigned AE-ID in the registration request and where no AE-ID Stem is included. |
| |_CE/REG/00002/00005_ |AE registration/de-registration without a pre-assigned AE-ID in the registration request and where the AE-ID Stem is configured with 'S' and where announcement to an IN-CSE is needed to get an AE-ID assigned |
| |_CE/DIS/_ _00_ _00_ _1/00006_ |Support the _labels_ attribute of <AE> resource |
| |_CE/REG/_ _00_ _002_ _/_ _0000_ _7_ |Support the _applicationName_ attribute of <AE> resource |
| |_CE/REG/_ _0_ _00_ _02_ _/_ _0000_ _8_ |Support the _pointOfAccess_ attribute of <AE> resource |
| |_CE/REG/00002/0000_ _9_ |AE registration with pre-assigned AE-ID |
| |_CE/DIS/_ _00_ _00_ _1/00006_ |Support the _labels_ attribute of <remoteCSE> resource |
| |_CE/REG/0000_ _4_ _/_ _0000_ _2_ |Support the _cseType_ attribute of <remoteCSE> resource |
| |_CE/REG/0000_ _4_ _/_ _0000_ _3_ |Support the _pointOfAccess_ attribute of <remoteCSE> resource |
| |_CE/REG/0000_ _4_ _/_ _0000_ _4_ |Support the _nodeLink_ attribute of <remoteCSE> resource |
|_CE/REG/0000_ _5_ |_CE/REG/0000_ _5_ _/_ _00001_ |The Creation with <remoteCSE> resource for CSE registration with mandatory attributes<ahref="#_ref_2">[2]</a> for Create and locally create <remoteCSE> that represents the Regstree CSE |
| |_CE/REG/0000_ _5_ _/_ _00001_ |Create the <remoteCSE> with _resourceName_ attribute |
| |_CE/REG/0000_ _5_ _/_ _00001_ |Create the <remoteCSE> with expirationTime attribute |
| |_CE/REG/0000_ _5_ _/0000_ _4_ |Create the <remoteCSE> with _labels_ attribute |
| |_CE/REG/0000_ _5_ _/0000_ _2_ |Create the <remoteCSE> with _cse_ _T_ _ype_ attribute |
| |_CE/REG/0000_ _5_ _/0000_ _3_ |Create the <remoteCSE> with _point_ _O_ _f_ _A_ _ccess_ attribute |
| |_CE/REG/0000_ _5_ _/0000_ _5_ |Create the <remoteCSE> with _node_ _L_ _ink_ attribute |
| |_CE/DIS/00001/00006_ |Support the _labels_ attribute of <AE> resource |
| |_CE/REG/00002/00007_ |Support the _applicationName_ attribute of <AE> resource |
| |_CE/REG/00002/00008_ |Support the _pointOfAccess_ attribute of <AE> resource |
| |_CE/REG/00002/00009_ |AE registration with pre-assigned AE-ID |
| |_CE/DIS/00001/00006_ |Support the _labels_ attribute of <remoteCSE> resource |
| |_CE/REG/00004/00002_ |Support the _cseType_ attribute of <remoteCSE> resource |
| |_CE/REG/00004/00003_ |Support the _pointOfAccess_ attribute of <remoteCSE> resource |
| |_CE/REG/00004/00004_ |Support the _nodeLink_ attribute of <remoteCSE> resource |
|_CE/REG/00005_ |_CE/REG/00005/00001_ |The Creation with <remoteCSE> resource for CSE registration with mandatory attributes<ahref="#_ref_2">[2]</a> for Create and locally create <remoteCSE> that represents the Regstree CSE |
| |_CE/REG/00005/00001_ |Create the <remoteCSE> with _resourceName_ attribute |
| |_CE/REG/00005/00001_ |Create the <remoteCSE> with expirationTime attribute |
| |_CE/REG/00005/00004_ |Create the <remoteCSE> with _labels_ attribute |
| |_CE/REG/00005/00002_ |Create the <remoteCSE> with _cseType_ attribute |
| |_CE/REG/00005/00003_ |Create the <remoteCSE> with _pointOfAccess_ attribute |
| |_CE/REG/00005/00005_ |Create the <remoteCSE> with _nodeLink_ attribute |
| |_CE/DIS/00001/00006_ |Update the <remoteCSE> with _labels_ |
| |_CE/REG/0000_ _5_ _/_ _00001_ |Update the <remoteCSE> with _expirationTime_ |
| |_CE/REG/0000_ _5_ _/000_ _06_ |Update the <remoteCSE> with _pointOfAccess_ attribute |
| |_CE/REG/0000_ _5_ _/000_ _07_ |Update the <remoteCSE> with _requestReachability_ |
| |_CE/REG/0000_ _5_ _/000_ _08_ |Update the <remoteCSE> with _nodeLink_ attribute |
| |_CE/REG/0000_ _5_ _/000_ _01_ |Delete the <remoteCSE> resource on the Registrar, also delete the <remoteCSE> resource on the Registree |
| |_CE/REG/0000_ _5_ _/000_ _09_ |Retrieve the <remoteCSE> resource |
| |_CE/REG/00005/00001_ |Update the <remoteCSE> with _expirationTime_ |
| |_CE/REG/00005/00006_ |Update the <remoteCSE> with _pointOfAccess_ attribute |
| |_CE/REG/00005/00007_ |Update the <remoteCSE> with _requestReachability_ |
| |_CE/REG/00005/00008_ |Update the <remoteCSE> with _nodeLink_ attribute |
| |_CE/REG/00005/00001_ |Delete the <remoteCSE> resource on the Registrar, also delete the <remoteCSE> resource on the Registree |
| |_CE/REG/00005/00009_ |Retrieve the <remoteCSE> resource |
**Table 5.8.3-3: Fundamental feature sets forgateway as MNDMR**
**Table 5.****8****.3-****3****: Fundamental feature sets for****gateway as M****N****DMR**
| |_CE/DIS/00001/00006_ |Support the _labels_ attribute of <contentInstance> resource |
| |_CE/DMR/00002/00001_ |Support the _creator_ attribute of <contentInstance> resource |
| |_CE/DMR/00002/00002_ |Support the _contentInfo_ attribute of <contentInstance> resource |
| |_CE/DMR/00002/00004_ |Retrieve and Delete of latest <contentInstance> resource by <latest> virtual resource |
| |_CE/DMR/00002/00057_ |Retrieve and Delete of oldest <contentInstance> resource by <oldest> virtual resource |
**Table 5.8.3-4: Fundamental feature sets forgateway as MN SUB**
|**Feature Set** |**Feature** |**Remark** |
|-|-|-|
|_CE/SUB/00001_ |_CE/SUB/00001/00001_ |The Support of <subscription> resource with attributes multiplicity equals 1<ahref="#_ref_1">[1]</a> |
| |_CE/DIS/_ _00_ _00_ _1/00006_ |Support the _labels_ attribute of <subscription> resource. |
| |_CE/DIS/00001/00006_ |Support the _labels_ attribute of <subscription> resource. |
| |_CE/SUB/00001/00001_ |Support the _creator_ attribute of <subscription> resource |
| |_CE/SUB/00001/00001_ |Support the _subscriberURI_ attribute of <subscription> resource |
|_CE/SUB/0000_ _4_ |_CE/SUB/0000_ _4_ _/00001_ |Notify the address indicated in _notificationURI_ with notification elements multiplicity equals 1<ahref="#_ref_2">[2]</a> |
| |_CE/SUB/0000_ _4_ _/00002_ |Notify with notificationEvent/representation set in the notification |
| |_CE/SUB/0000_ _4_ _/0000_ _3_ |Notify with creator set in the notification |
|_CE/SUB/00004_ |_CE/SUB/00004/00001_ |Notify the address indicated in _notificationURI_ with notification elements multiplicity equals 1<ahref="#_ref_2">[2]</a> |
| |_CE/SUB/00004/00002_ |Notify with notificationEvent/representation set in the notification |
| |_CE/SUB/00004/00003_ |Notify with creator set in the notification |
**Table 5.8.3-5: Fundamental feature sets forgateway as MNSEC**
**Table 5.****8****.3-****5****: Fundamental feature sets for****gateway as M****N****SEC**
| |_CE/DIS/00001/00006_ |Support the _labels_ attribute of <accessControlPolicy> resource |
|_CE/SEC/00002_ |_CE/SEC/00002/00001_ |Support _accessControlPolicyIDs_ attribute for <resource> that the Implementation supports. |
| |_CE_ _/_ _SEC_ _/00_ _00_ _2/_ _0000_ _2_ |Support access control decision and enforcement making on the Hosting CSE |
| |_CE/SEC/00002/00002_ |Support access control decision and enforcement making on the Hosting CSE |
## 5.9 Field configurable oneM2M Entity Hosted on a 3GPP Device
### 5.9.1 Profile description
The profile defines the features required for a oneM2M entity hosted on a 3GPP device. This profile is intended to add required features to those specified in other profiles. For example, a temperature sensor hosted on an CIoT device would required the features described in this section plus the features described for a Constrained Sensor device.
### 5.9.2 Profile usage examples
The profile applies to CIoT devices that can receive trigger messages via a 3GPP core network. The trigger messages are used provision the device with enrolment credentials, register the device to a oneM2M CSE and re-establish a connection to the Registrar CSE.
### 5.9.3 Fundamental feature sets
**Table 5.2.3-1: Fundamental feature sets for oneM2M entity hosted on a 3GPP Device**<aname="table_5.2.3-1"></a>
**Table A-2: Mapping of feature to Test Purposes for AE**<aname="table_A-2"></a>
...
...
@@ -966,72 +684,72 @@ Annex <A> (Normative): Mapping of feature to test purposes
|-|-|-|
|_AE/GEN/00001_ |Support one of the format of resource identification |TP/oneM2M/AE/GEN/CRE/001\_CSR<br/>TP/oneM2M/AE/GEN/CRE/001\_SPR<br/>TP/oneM2M/AE/GEN/CRE/001\_ABS<br/>TP/oneM2M/AE/GEN/CRE/002\_CSR<br/>TP/oneM2M/AE/GEN/CRE/002\_SPR<br/>TP/oneM2M/AE/GEN/CRE/002\_ABS<br/>TP/oneM2M/AE/GEN/UPD/001\_CSR<br/>TP/oneM2M/AE/GEN/UPD/001\_SPR<br/>TP/oneM2M/AE/GEN/UPD/001\_ABS<br/>TP/oneM2M/AE/GEN/UPD/002\_CSR<br/>TP/oneM2M/AE/GEN/UPD/002\_SPR<br/>TP/oneM2M/AE/GEN/UPD/002\_ABS<br/>TP/oneM2M/AE/GEN/RET/001\_CSR<br/>TP/oneM2M/AE/GEN/RET/001\_SPR<br/>TP/oneM2M/AE/GEN/RET/001\_ABS<br/>TP/oneM2M/AE/GEN/RET/002\_CSR<br/>TP/oneM2M/AE/GEN/RET/002\_SPR<br/>TP/oneM2M/AE/GEN/RET/002\_ABS<br/>TP/oneM2M/AE/GEN/DEL/001\_CSR<br/>TP/oneM2M/AE/GEN/DEL/001\_SPR<br/>TP/oneM2M/AE/GEN/DEL/001\_ABS<br/>TP/oneM2M/AE/GEN/DEL/002\_CSR<br/>TP/oneM2M/AE/GEN/DEL/002\_SPR<br/>TP/oneM2M/AE/GEN/DEL/002\_ABS |
