5 Mapping of basic data types
TR-106 [5] specifies the object structure supported by TR-069 enabled devices and specifies the structural requirements for the data hierarchy. This clause includes the mapping attribute data types to TR-181 [6] parameters which follows the conventions of section 3 of TR-106 [5] and data types described in Table 4 of TR-106 [5].
| oneM2M Data Types | Mapping to data types in TR-106 | Conversion Notes |
|---|---|---|
| xs:boolean | boolean | |
| xs:string | string | Mapping is constrained to the size of the string |
| xs:unsignedInt | unsignedInt | |
| xs:unsignedLong | unsignedLong | |
| xs:integer | long | Mapping is constrained to the size of the long data type. |
| Xs:positiveInteger | unsignedLong | Mapping is constrained to a lower limit of 1 and the size of the unsignedLong data type. |
| Xs:nonNegativeInteger | unsignedLong | Mapping is constrained the size of the unsignedLong data type. |
| Comma separated Lists | Comma separated Lists | Data structure is represented by comma separated list as described in section 3.2.3 of TR-106 [5]. |
In some instances the conversion of the contents between data types will cause an error to occur (e.g. xs:integer to long). When an error occurs in the conversion of a data type, the 4000 (BAD_REQUEST) response status code shall be given.