Design of RESTful APIs for M2M services

Abstract

The upcoming communication aim will not focus on connecting humans by different kinds of multimedia services, but also connecting machines of different aspects, providing a global smart world. The telecommunication industry is currently moving towards service-oriented infrastructures based on Internet Protocol (IP), Service Oriented Architectures (SOA), and Service Delivery Platforms (SDP). In this paper we introduce the Machine-to-Machine (M2M) trend of communications, which evoked more interest recently, and describe a set of proposed Application Programming Interfaces (APIs) to interact with our new OpenMTC framework at FOKUS

A Framework for the Secure Storage of Data Generated in the IoT

“…More recently, in [9], another RESTful-based middleware framework was also proposed, differing by its use of the MQTT protocol [15]. Another RESTful middleware was also presented in [10], this one focusing more on the interaction with devices by means of the OpenMTC framework. The second approach focuses on data acquisition, integration and storage in a way that still enables access control and the management of security and privacy.…”

Design aspects for a reference M2M communication platform for Smart Cities

“…The OpenMTC SDK consist of a set of high-level abstraction Application Programming Interfaces (APIs) which hide internal system complexity, and allow the developer to focus on the implementation of the application logic. In [17] we present and describe our work in designing a set of APIs for the OpenMTC platform. Adopting the RESTful style facilitates the development of M2M applications, due to its simplicity in comparison with most SOA technologies.…”

Application-derived communication protocol selection in M2M platforms for smart cities

“…These functionalities are inline with the oneM2M common service functions listed in Table 3.3. REST is based on the concept of resources addressed by a URI, thus it provides to M2M devices a place to store their states and data, which is always on and connectable [31]. The main idea is to let transactions occur in a subscription/notication manner.…”

“…OpenMTC supports both of MIa interface specied by ETSI as well as Mca interface specied by oneM2M. In order to support the development of M2M applications and make the core assets and service capabilities available to 3rd party developers, the OpenMTC application enablement layer denes a set of high-level abstraction APIs, which are categorized under three groups: Device, Data and Network API [31], as shown in …”

“…In the course of the research for this dissertation, several related publications have been disseminated that present the work within the topic of interest: eight conference papers reecting the main contributions ( [42,43,5,32,45,46,40,39]), one book chapter ( [190]) and six conference papers about related elds of application in the context of Smart City services ( [24,31,35,29,38,176]), and seven joint papers with other research projects members ( [191,136,36,37,43,44,192] open research issues to be addressed for the realization of this device-tier interaction [194]. However, it shall bring signicant improvements in developing emergency applications and vehicle-to-vehicle (V2V) communication.…”