Documentation

Mistake on this page? Email us

Edge Core

Edge Core hosts Device Management Client, which provides the connectivity to Device Management.

  • Edge Core has its own Objects, Object Instances, and Resources.
  • Device Management Client has a firmware update feature, which updates the Edge firmware.

Edge Core stores all mediated Resource values currently in string format. To see how Device Management Client handles the values internally, read the Device Management Resource handling documentation.

When Edge Core receives a value from the protocol translator, it expects binary data in the request. It then converts the binary data to string format for Device Management Client.

When Edge Core receives a value from Device Management, it expects data in string format. It then converts the value, if necessary, to the corresponding binary representation for the targeted Resource and its data type. Edge Core writes the integer and float values to the protocol translator as 64-bit values. It uses the widest format because the original precision is lost in the conversion to string.

Data type Protocol translator and management Edge Core Device Management Client Device Management
String String String String String
Integer Integer Integer String String
Float Float Float String String
Boolean Boolean Boolean String String
Opaque Opaque Opaque Opaque Opaque
Time Time Time String String
Objlnk Objlnk Objlnk Objlnk Objlnk

For string, opaque, and objlnk, the bytes are passed through the layers.

The values must follow the LwM2M specification of the data types. See Appendix C for the table.

See the Protocol translator API documentation for more information on handling Resource values in implementation. You can also refer to the protocol translator example implementation pt-example in the Device Managment Edge example repository.

See the Local management API documentation for more information on handling Resource values in implementation. You can also refer to the management application example implementation simple-js-examples/simple-mgmt-example.js in the Device Managment Edge example repository.

Limitations

Edge Core does not have a separate lifetime for the mediated endpoints. They inherit the lifetime of the Edge device. When the mediated devices are disconnected, the protocol translator issues a deregistration to Edge Core.

The only hook point to set the existing Edge Core-specific Resources is reset factory settings. For more information about this, see the Edge API documentation.

See the release notes for other known issues.

Edge service API

Edge offers a REST API to check the Device Management connection status, the internal status, and the version information of the device. For documentation, see Edge Core Rest API.