CBOR Support
Sensitive data such as encryption keys, graphic data, or sensor values cannot be transferred in plain text or in JSON format by client. This information is transferred in binary data as hexencoded string as shown below:
<<<<<<<<<<<<<<< parseCborOpaque - opaque content is[383331393146344130313831383331413539413741373532304138413033313836333138333231383336313835443138334431303138354230393138324}3
The opaque hexencoded content is now parsed by LWM2M server using CBOR library and is converted into a base64 string and sent as response for Get details operation.
This is done only for specific object IDs as listed below:
| New SEW Object ID | New SEW Resource ID |
|---|---|
| 10266 | 6009, 6029 |
| 10267 | 6009, 6029 |
| 10268 | 6009, 6029 |
| 10269 | 6009, 6029 |
| 10270 | 6009, 6029 |
| 10271 | 6009, 6029 |
| 10272 | 6025 |
| 10273 | 6025 |
| 10274 | 6025 |
| 10275 | 6025 |
| 10276 | 6025 |
| 10277 | 6025 |
| 10278 | 6025 |
| 10279 | 6025 |
| 10280 | 6025 |
| 10281 | 6025 |
| 10282 | 6025 |
| 10283 | 6025 |
| 10284 | 6025 |
| 10262 | 2 |
| 10263 | 2 |