27 research outputs found

    IETF standardization in the field of the Internet of Things (IoT): a survey

    Get PDF
    Smart embedded objects will become an important part of what is called the Internet of Things. However, the integration of embedded devices into the Internet introduces several challenges, since many of the existing Internet technologies and protocols were not designed for this class of devices. In the past few years, there have been many efforts to enable the extension of Internet technologies to constrained devices. Initially, this resulted in proprietary protocols and architectures. Later, the integration of constrained devices into the Internet was embraced by IETF, moving towards standardized IP-based protocols. In this paper, we will briefly review the history of integrating constrained devices into the Internet, followed by an extensive overview of IETF standardization work in the 6LoWPAN, ROLL and CoRE working groups. This is complemented with a broad overview of related research results that illustrate how this work can be extended or used to tackle other problems and with a discussion on open issues and challenges. As such the aim of this paper is twofold: apart from giving readers solid insights in IETF standardization work on the Internet of Things, it also aims to encourage readers to further explore the world of Internet-connected objects, pointing to future research opportunities

    IETF standardization in the field of the internet of things (IoT): a survey

    Get PDF
    Smart embedded objects will become an important part of what is called the Internet of Things. However, the integration of embedded devices into the Internet introduces several challenges, since many of the existing Internet technologies and protocols were not designed for this class of devices. In the past few years, there have been many efforts to enable the extension of Internet technologies to constrained devices. Initially, this resulted in proprietary protocols and architectures. Later, the integration of constrained devices into the Internet was embraced by IETF, moving towards standardized IP-based protocols. In this paper, we will briefly review the history of integrating constrained devices into the Internet, followed by an extensive overview of IETF standardization work in the 6LoWPAN, ROLL and CoRE working groups. This is complemented with a broad overview of related research results that illustrate how this work can be extended or used to tackle other problems and with a discussion on open issues and challenges. As such the aim of this paper is twofold: apart from giving readers solid insights in IETF standardization work on the Internet of Things, it also aims to encourage readers to further explore the world of Internet-connected objects, pointing to future research opportunities.The research leading to these results has received funding from the European Union’s Seventh Framework Programme (FP7/2007-2013) under grant agreement no 258885 (SPITFIRE project), from the iMinds ICON projects GreenWeCan and O’CareCloudS, a FWO postdoc grant for Eli De Poorter and a VLIR PhD scholarship to Isam Ishaq

    Using SCHC for an optimized protocol stack in multimodal LPWAN solutions

    Get PDF
    Low Power Wide Area Networks (LPWANs) are formed out of cheap, small, interconnected devices which operate in the sub-GHz domain. The last couple of years, many communication technologies arose in this domain, each with its own characteristics. In order to satisfy more diverse requirements, devices are now equipped with multiple LPWAN radio technologies, which requires the use of a unified protocol stack independent of the underlying LPWAN technology. With its 2128 addresses available and its ability to operate over different link layer technologies, the IPv6 protocol stack would be the ideal candidate. However, many LPWAN configurations do not allow standardized IP/UDP communication, sometimes acquiring more header overhead than there is room for the actual payload. Recently, a new initiative to directly connect constrained devices over IP was initiated by the LPWAN working group of the Internet Engineering Task Force (IETF). This work resulted in the Static Context Header Compression or SCHC mechanism. This header compression mechanism is able to compress the overhead of these internet protocols up to 95%. In order to comply with the IPv6 Maximum Transfer Unit (MTU) of 1280 bytes, a fragmentation mechanism is also included. In this work, we validate the benefits of using SCHC for multimodal LPWAN solutions and show its implementation feasibility on such constrained devices

    Securing IoT-based collaborative applications using a new compressed and distributed MIKEY mode

    Get PDF
    International audienceMultimedia internet keying protocol (MIKEY) aims at establishing secure credentials between two communicating entities. However, existing MIKEY modes fail to meet the requirements of low-power and low-processing devices. To address this issue, we combine two previously proposed approaches to introduce a new compressed and distributed MIKEY mode applied to a collaborative internet of things context. A set of third parties is used to discharge the constrained nodes from heavy computational operations. Doing so, the MIKEY pre-shared mode is used in the constrained part of network, while the public key mode is used in the unconstrained part of the network. Furthermore, to mitigate the communication cost we introduce a new header compression scheme that reduces the size of MIKEY's header from 12 bytes to 3 bytes in the best compression case. To assess our approach, we performed a detailed security analysis using a formal validation tool (i.e., Avispa). In addition, we performed an energy evaluation of both communicational and computational costs. The obtained results show that our proposed mode is energy preserving whereas its security properties are preserved untouched

    Implementation and Evaluation of the Enhanced Header Compression (IPHC) according to 6LoWPAN Network

    Get PDF
    6LoWPAN defines how to carry Ipv6 packet over IEEE 802.15.4 low power wireless or sensor networks. Limited bandwidth, memory and energy resources require a careful application of Ipv6 in a LoWPAN network. The aim is to develop personal networks, mainly sensor based, that can be integrated to the existing wellknow network infrastructure by reusing mature and wideused technologies. IPv6 has been chosen as network protocol because its characteristics fit to the problematic that characterize LoWPAN environment such as the large number of nodes to address and stateless address autoconfiguration. However, an IPv6 header compression algorithm is necessary in order to reduce the overhead and save space in data payload. In fact, the IEEE 802.15.4 standard defines an MTU of 128 bytes that decrease to 102 bytes considering the frame overhead, a further reduction is due to the network and transport protocols frame overhead that, in case of Ipv6 and UDP, allow to carry only 33 bytes for application data. The aim of this work is to describe and compares the proposed Ipv6 header compression mechanisms for 6LoWPAN environments

    6LoWPAN Stack Model Configuration for IoT Streaming Data Transmission over CoAP

    Get PDF
    Abstract: Different protocols have been developed for the Internet of things (IoT), such as the constrained application protocol (CoAP) for the application layer of the IPv6 over low-power wireless personal area networks (6LoWPAN) stack model. Data transmitted over 6LoWPAN are limited by the throughput and the frame size defined by IEEE 805.14.5 standards. Choosing the best configuration for data transmission involves a trade off between the application requirements, the constrained network configuration, the constrained device specifications and IoT application protocols. This paper provides an analysis of message size and structure recommendations for the 6LoWPAN stack model for different network topologies using CoAP. CoAP is a promising application protocol for the 6LoWPAN stack model because it can effectively manage the transmission required functionality in small header UDP packets compared to TCP packets. However, a data model is also required to realize an effective IoT model. While fragmentation and reassembly are supported by CoAP, they should be avoided for this type of model. As for any conceptual model, a high configuration between layers is mandatory. Additionally, the proposed message format is useful for semantic web of things application development and for WSN design and management

    Securing IoT-based collaborative applications using a new compressed and distributed MIKEY mode

    Get PDF
    International audienceMultimedia internet keying protocol (MIKEY) aims at establishing secure credentials between two communicating entities. However, existing MIKEY modes fail to meet the requirements of low-power and low-processing devices. To address this issue, we combine two previously proposed approaches to introduce a new compressed and distributed MIKEY mode applied to a collaborative internet of things context. A set of third parties is used to discharge the constrained nodes from heavy computational operations. Doing so, the MIKEY pre-shared mode is used in the constrained part of network, while the public key mode is used in the unconstrained part of the network. Furthermore, to mitigate the communication cost we introduce a new header compression scheme that reduces the size of MIKEY's header from 12 bytes to 3 bytes in the best compression case. To assess our approach, we performed a detailed security analysis using a formal validation tool (i.e., Avispa). In addition, we performed an energy evaluation of both communicational and computational costs. The obtained results show that our proposed mode is energy preserving whereas its security properties are preserved untouched

    Discovery and Group Communication for Constrained Internet of Things Devices using the Constrained Application Protocol

    Get PDF
    The ubiquitous Internet is rapidly spreading to new domains. This expansion of the Internet is comparable in scale to the spread of the Internet in the ’90s. The resulting Internet is now commonly referred to as the Internet of Things (IoT) and is expected to connect about 50 billion devices by the year 2020. This means that in just five years from the time of writing this PhD the number of interconnected devices will exceed the number of humans by sevenfold. It is further expected that the majority of these IoT devices will be resource constrained embedded devices such as sensors and actuators. Sensors collect information about the physical world and inject this information into the virtual world. Next processing and reasoning can occur and decisions can be taken to enact upon the physical world by injecting feedback to actuators. The integration of embedded devices into the Internet introduces new challenges, since many of the existing Internet technologies and protocols were not designed for this class of constrained devices. These devices are typically optimized for low cost and power consumption and thus have very limited power, memory, and processing resources and have long sleep periods. The networks formed by these embedded devices are also constrained and have different characteristics than those typical in todays Internet. These constrained networks have high packet loss, low throughput, frequent topology changes and small useful payload sizes. They are referred to as LLN. Therefore, it is in most cases unfeasible to run standard Internet protocols on this class of constrained devices and/or LLNs. New or adapted protocols that take into consideration the capabilities of the constrained devices and the characteristics of LLNs, are required. In the past few years, there were many efforts to enable the extension of the Internet technologies to constrained devices. Initially, most of these efforts were focusing on the networking layer. However, the expansion of the Internet in the 90s was not due to introducing new or better networking protocols. It was a result of introducing the World Wide Web (WWW), which made it easy to integrate services and applications. One of the essential technologies underpinning the WWW was the Hypertext Transfer Protocol (HTTP). Today, HTTP has become a key protocol in the realization of scalable web services building around the Representational State Transfer (REST) paradigm. The REST architectural style enables the realization of scalable and well-performing services using uniform and simple interfaces. The availability of an embedded counterpart of HTTP and the REST architecture could boost the uptake of the IoT. Therefore, more recently, work started to allow the integration of constrained devices in the Internet at the service level. The Internet Engineering Task Force (IETF) Constrained RESTful Environments (CoRE) working group has realized the REST architecture in a suitable form for the most constrained nodes and networks. To that end the Constrained Application Protocol (CoAP) was introduced, a specialized RESTful web transfer protocol for use with constrained networks and nodes. CoAP realizes a subset of the REST mechanisms offered by HTTP, but is optimized for Machine-to-Machine (M2M) applications. This PhD research builds upon CoAP to enable a better integration of constrained devices in the IoT and examines proposed CoAP solutions theoretically and experimentally proposing alternatives when appropriate. The first part of this PhD proposes a mechanism that facilitates the deployment of sensor networks and enables the discovery, end-to-end connectivity and service usage of newly deployed sensor nodes. The proposed approach makes use of CoAP and combines it with Domain Name System (DNS) in order to enable the use of userfriendly Fully Qualified Domain Names (FQDNs) for addressing sensor nodes. It includes the automatic discovery of sensors and sensor gateways and the translation of HTTP to CoAP, thus making the sensor resources globally discoverable and accessible from any Internet-connected client using either IPv6 addresses or DNS names both via HTTP or CoAP. As such, the proposed approach provides a feasible and flexible solution to achieve hierarchical self-organization with a minimum of pre-configuration. By doing so we minimize costly human interventions and eliminate the need for introducing new protocols dedicated for the discovery and organization of resources. This reduces both cost and the implementation footprint on the constrained devices. The second, larger, part of this PhD focuses on using CoAP to realize communication with groups of resources. In many IoT application domains, sensors or actuators need to be addressed as groups rather than individually, since individual resources might not be sufficient or useful. A simple example is that all lights in a room should go on or off as a result of the user toggling the light switch. As not all IoT applications may need group communication, the CoRE working group did not include it in the base CoAP specification. This way the base protocol is kept as efficient and as simple as possible so it would run on even the most constrained devices. Group communication and other features that might not be needed by all devices are standardized in a set of optional separate extensions. We first examined the proposed CoAP extension for group communication, which utilizes Internet Protocol version 6 (IPv6) multicasts. We highlight its strengths and weaknesses and propose our own complementary solution that uses unicast to realize group communication. Our solution offers capabilities beyond simple group communication. For example, we provide a validation mechanism that performs several checks on the group members, to make sure that combining them together is possible. We also allow the client to request that results of the individual members are processed before they are sent to the client. For example, the client can request to obtain only the maximum value of all individual members. Another important optional extension to CoAP allows clients to continuously observe resources by registering their interest in receiving notifications from CoAP servers once there are changes to the values of the observed resources. By using this publish/subscribe mechanism the client does not need to continuously poll the resource to find out whether it has changed its value. This typically leads to more efficient communication patterns that preserve valuable device and LLN resources. Unfortunately CoAP observe does not work together with the CoAP group communication extension, since the observe extension assumes unicast communication while the group communication extension only support multicast communication. In this PhD we propose to extend our own group communication solution to offer group observation capabilities. By combining group observation with group processing features, it becomes possible to notify the client only about certain changes to the observed group (e.g., the maximum value of all group members has changed). Acknowledging that the use of multicast as well as unicast has strengths and weaknesses we propose to extend our unicast based solution with certain multicast features. By doing so we try to combine the strengths of both approaches to obtain a better overall group communication that is flexible and that can be tailored according to the use case needs. Together, the proposed mechanisms represent a powerful and comprehensive solution to the challenging problem of group communication with constrained devices. We have evaluated the solutions proposed in this PhD extensively and in a variety of forms. Where possible, we have derived theoretical models and have conducted numerous simulations to validate them. We have also experimentally evaluated those solutions and compared them with other proposed solutions using a small demo box and later on two large scale wireless sensor testbeds and under different test conditions. The first testbed is located in a large, shielded room, which allows testing under controlled environments. The second testbed is located inside an operational office building and thus allows testing under normal operation conditions. Those tests revealed performance issues and some other problems. We have provided some solutions and suggestions for tackling those problems. Apart from the main contributions, two other relevant outcomes of this PhD are described in the appendices. In the first appendix we review the most important IETF standardization efforts related to the IoT and show that with the introduction of CoAP a complete set of standard protocols has become available to cover the complete networking stack and thus making the step from the IoT into the Web of Things (WoT). Using only standard protocols makes it possible to integrate devices from various vendors into one bigWoT accessible to humans and machines alike. In the second appendix, we provide an alternative solution for grouping constrained devices by using virtualization techniques. Our approach focuses on the objects, both resource-constrained and non-constrained, that need to cooperate by integrating them into a secured virtual network, named an Internet of Things Virtual Network or IoT-VN. Inside this IoT-VN full end-to-end communication can take place through the use of protocols that take the limitations of the most resource-constrained devices into account. We describe how this concept maps to several generic use cases and, as such, can constitute a valid alternative approach for supporting selected applications

    Implementation and Evaluation of the Enhanced Header Compression (IPHC) according to 6LoWPAN Network

    Get PDF
    6LoWPAN defines how to carry Ipv6 packet over IEEE 802.15.4 low power wireless or sensor networks. Limited bandwidth, memory and energy resources require a careful application of Ipv6 in a LoWPAN network. The aim is to develop personal networks, mainly sensor based, that can be integrated to the existing wellknow network infrastructure by reusing mature and wideused technologies. IPv6 has been chosen as network protocol because its characteristics fit to the problematic that characterize LoWPAN environment such as the large number of nodes to address and stateless address autoconfiguration. However, an IPv6 header compression algorithm is necessary in order to reduce the overhead and save space in data payload. In fact, the IEEE 802.15.4 standard defines an MTU of 128 bytes that decrease to 102 bytes considering the frame overhead, a further reduction is due to the network and transport protocols frame overhead that, in case of Ipv6 and UDP, allow to carry only 33 bytes for application data. The aim of this work is to describe and compares the proposed Ipv6 header compression mechanisms for 6LoWPAN environments

    Literature Survey on IPv6 over low power personal area networks.

    Get PDF
    As there is an increase in (IOT) Internet of Things, there is a growing implementation of Internet of things in many areas in our day-to-day life. Internet of things entails the linking of different embedded devices like appliances, weather stations and even toys to the internet using the Internet Protocol. Surveys say that the number of embedded devices that are IP-enabled will outnumber the total personal computers in the near future. 6LoWPAN is the name of a concluded working group in the Internet area of the IETF. 6LoWPAN is the technology that enable small, low powered embedded devices to access the internet. 6LoWPAN is a protocol definition that makes IPv6 packets to be carried on top of low power wireless networks, specifically IEEE 802.15.4. In this literature survey, I am going to give the details about the architecture and design of 6LoWPAN, the routing protocols used, and the security and privacy mechanisms used. There are three types of Lowpans: Ad-Hoc lowpan, Simple lowpan and extended lowpan. I am going to write about the innovative ways to implement security in 6LoWPAN. 6LoWPAN is different because of its small address size and low power features. Hence, to make 6LoWPAN secure new and unique challenges needs to be addressed. The routing protocols in 6LoWPAN are very sensitive because of the limited node’s capabilities in terms of power, transmission range and so on. Hence, it is based on layering decisions: application-based, and other parameter bases
    corecore