Not clear how to access TS-0022 resources as an unregistered M2M node
TS-0022 defines resources that can be used to configure nodes in Field Domian. However, it is not clear how exactly those resources are provisioned to the M2M nodes that have not established M2M Service Layer operation yet, meaning they are not registered with the Registrar CSE.
These three configuration methods of M2M nodes in Field Domain are possible:
- Device Management technologies using the mc reference point
- oneM2M Mcc and Mca reference point when M2M Service Layer operation has been established
- oneM2M IPE technology
The method 1 (mc reference point) relies on technology specific protocols (e.g. BBF). The mc interface in general is out of scope of oneM2M.
The method 2 (oneM2M Mcc and Mca reference point) can not be used for the unregistered nodes as it requires prior establishment of M2M Service Layer operation.
The method 3 (oneM2M IPE technology) requires a Configuration IPE. The interface between Configuration IPE and the Field Domain M2M node is not specified.
In summary, only methods 1 and 3 can be used when M2M Service Layer operation is not established yet and in both the interface towards the M2M node is not specified in oneM2M. This may not be a big issue when all entities are implemented by the same provider, however if a M2M node and the rest of the system (e.g. IN-CSE, Configuration IPE) are implemented by different parties, it is practically impossible to establish the communication according to the mc reference point or the unspecified reference point (towards Configuration IPE).
One of the solutions would be to pre-provision registration data to the unregistered the M2M node. This data can be [registration], [authenticationProfile] resources or other TS-0022 resources or only partial information from those resources. With such pre-provisioned data, the M2M node does not have to use mc reference point of Configuration IPE and would only use Mca/Mcc reference point.