A Security Generic Service Interface of Internet of Things (IoT) Platforms

Mi Kim, Nam Lee, Jin Park
2017 Symmetry  
Internet of Things (IoT) platforms are the key for the development of scalable IoT applications and services that connect real and virtual worlds between objects, systems, and people. However, as the IoT platform market represents a truly new market segment that was almost non-existent a few years ago, the platforms are complex and changing quickly. These IoT platforms perform simple functions such as providing useful information, and others can provide services through collaborations with IoT
more » ... borations with IoT devices. This situation needs a generic service interface, and results in a range of IoT architectures through not only the configuration setting of IoT devices and resources but also the varied environments of collaboration of each device. Due to these heterogeneities, it is quite challenging to develop applications working with diverse IoT services, and it is even more difficult to maintain such applications. Therefore, this paper presents a security generic service interface with the effective common characteristics of an IoT platform by defining a set of generic interfaces and adopting well-known design patterns. The generic interface solves the heterogeneity-driven problems and makes it possible to effectively adopt a platform-independent Generic Interface that could be operated in diverse IoT platforms. The security generic service interface is proposed in order to build an IoT-based configurable resource-time and battery-consumption service platform for design. A number of things connecting it led to the proposal of a common service to create flexibility in the common characteristics where heterogeneous environments control the flow of data. The rest of this paper is organized as follows: Section 2 discusses the related work, Section 3 presents a Security Generic Service Interface, Section 4 presents a case study and evaluation, and Section 5 gives a conclusion. Related Work Most IoT management platforms, such as Philips Hue [1] and Internet of Things Environment for Service Creation and Testing (IoT.est) [2], focus on home automations or sensor networks. By the end of 2011, more than 4.5 billion USD were spent thanks to the introduction of application programming interfaces (APIs) [3] over IPv6 over Low power Wireless Personal Area Networks (6LoWPAN). This solution was seen as highly flexible and powerful. Moreover, a reduced version of representational state transfer (RESTFul) for constrained devices was proposed as a constrained application protocol (COAP). The solutions for IoT implementation focus on uniform naming [4] and addressing, while common protocols for ubiquitous smart objects center on exposing virtual representations of physical objects to develop a common communication platform. In this way, the SENSEI project [5] introduces the concept of resource, which corresponds to a physical entity in the real world and modern power of the management of IoT [6] [7] [8] . Furthermore, the resource is related to a software process (called Resource EndPoint), which represents the physical resource in the resource layer and implements a set of resource access interfaces. A dynamic architecture for services orchestration and self-adaptation has been proposed in the IoT.est [9] . To overcome technology and sector boundaries, dynamically design and integrate new types of services, and generate the new business opportunities mentioned, a dynamic service creates an environment that gathers and exploits data and information from sensors and actuators that use different communication technology formats. The service creation environment will enable the acquisition of sensors, objects, and actuators. Networked Smart Objects (NOSs) collect data transmitted by different kinds of sources (i.e., nodes). The system has been designed to support both registered sources and anonymous ones, each characterized by different communication technologies and providing diverse quality levels for their computational data. They connect between the interface IoT device, a centralized platform [10]. Message Queue Telemetry Transport (MQTT) is a machine-to-machine (M2M)/IoT connectivity protocol. It was designed as an extremely lightweight publish/subscribe messaging transport [11] . It is useful for connections with remote locations where a small code footprint is required and/or network bandwidth is at a premium. NOS and MQTT retrieve them, through Hypertext Transfer Protocol (HTTP), to requests messages. The security generic interface comparison with MQTT and NOSs are through a broker message, not only available for the heterogeneous device described but also proposed. The generic interface is defined as a driver interface and service interface without broker messages. Also, the proposed generic interface uses a common defined external agent to communicate with the heterogeneous device, among each device a connection through a common connecting message is made. MQTT has been used in sensors communicating to a broker, via mobile link, over an occasional dial-up connection with healthcare providers as well as in a range of home automation and small device scenarios. Therefore, it is only ideal for mobile applications, however the proposed generic interface is adapted to all networks. It also has an effectively low power usage, minimized data packets, and efficient distribution of information to one. In summary, while there are several papers available, describing exactly what a heterogeneous environment should offer from a special structure for platform, hardly any domain is available on the common capabilities of existing IoT services. However, relevant research builds upon relevant IoT
doi:10.3390/sym9090171 fatcat:2fblki446zhyxhm3csnay4l4ai