Iot sdk thesis

2.6.2
 
Interfaces 
As seen in Figure 2.6.1.1, “Interfaces” exist between the client and server, as logical 
points of contact to exchange information relevant to that interface. As seen, there are four 
interfaces defined between LWM2M server and LWM2M client. Interfaces and typical message 
exchange through them have been shown in Figure 2.6.2.2 
 
Figure 2.6.2.2 LWM2M Interfaces and Information Exchange [26]
Bootstrap 
Bootstrap interface is meant to operate between a LWM2M client and a LWM2M 
bootstrap server. It is different from regular LWM2M server. Bootstrap server manages the 

---

33 
keying, access control of the client device. Also, it is used to enrol the client to a LWM2M 
server.
Device Discovery and Registration 
Through this interface, LWM2M client can let the server know of its existence. After 
discovery, the client can register itself with the discovered server through this interface. 
Device Management and Service Enablement 
Allows LWM2M server to perform device management tasks and M2M service 
enablement on the client. It also is used for client to send the appropriate responses to the server 
to let its status known. 
Information Reporting 
This interface is used by clients to report the resource values to the server as per the 
application. The reporting can either be periodic or event triggered. 
2.6.3
 
LWM2M: Role in Thesis 
As has been described before, the aim of the thesis is to completely port Eclipse 
Wakaama LWM2M integration in C for Arduino-like boards such as Arduino Mega or SODAQ 
SARA. Wakaama has been designed to work on UNIX/POSIX compliant systems. The 
complete Wakaama LWM2M stack has been composed of different libraries. The library 
mapping has been shown in Figure 2.6.3.1