|author||Tony Walsworth <firstname.lastname@example.org>||Wed Aug 31 14:59:24 2016 +1200|
|committer||GitHub <email@example.com>||Wed Aug 31 14:59:24 2016 +1200|
Merge pull request #6 from rolandbewick/dev Updated examples and fixed issue with example parsing in documentation generator.
The device server is a LWM2M management server designed to be implemented alongside third party cloud services to integrate M2M capability into an IoT application. The device server exposes two secure interfaces; REST API/HTTPs and LWM2M/CoAP, and implements DTLS.
The device server interfaces securely with LWM2M device networks via the Constrained Application Protocol (CoAP) and aids device and application interoperability by supporting both IPSO registered smart object definitions and custom object definitions.
Device management is enabled through the implementation of the Open Mobile Alliance LWM2M standard. The CoAP interface and all LWM2M functionality is abstracted by the device server libraries, so intimate knowledge of LWM2M and CoAP is not required.
Web and mobile applications interface with the device server via an authenticated REST API with a single entry point URL.
Since LWM2M relies on CoAP for communications, the device server acts as a bridge between the CoAP and HTTP protocols, allowing devices and applications which are outside the LWM2M device network to query resource and connectivity data using HTTP via the device server's REST API. No resource states are cached by the server, so all resource queries are propagated via CoAP directly to the targeted device/s. The device server does cache client connectivity status however, so this data is returned directly.
The CoAP Observe verb is supported by registering (subscribing to) an observation with the device server which will POST a notification to a specified web hook when the value or state of the observed resource meets the desired criteria.
For an introduction to the device server, installation details, use of the REST API, client/device authentication and examples of common operations, see our user guide.
We welcome all contributions to this project and we give credit where it's due. Anything from enhancing functionality to improving documentation and bug reporting - it's all good.
Find out more in the contributor guide.
We would like to thank all of our current contributors.
Special thanks to the DTLS.Net team.
A list of ongoing development tasks can be seen here.