6LoWPAN Stacks: A Survey

Chen, Yibo; Hou, K.M.; Zhou, Haiying; Shi, Hongling; Xing, Liudong; Diao, Xunxing; Ding, Hao; Li, Jian-Jin; Vaulx, Christophe de

doi:10.1109/wicom.2011.6040344

Cited by 31 publications

(13 citation statements)

References 1 publication

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Thus, they do not meet the requirements from Section 2. Various other stacks, as presented by several surveys, can be roughly be put in three groups (i) discontinued, (ii) proprietary and closed-source, or (iii) open-source and freely available [21,24,26]. In the following we will focus on the third group (the analyzed requirements disqualifies the others).…”

Section: Related Work: Existing Network Stacksmentioning

confidence: 99%

Old Wine in New Skins?

Petersen

Lenders

Wählisch

et al. 2015

Proceedings of the 2015 Workshop on IoT Challenges in Mobile and Industrial Systems

View full text Add to dashboard Cite

In this paper, we argue that existing concepts for the design and implementation of network stacks for constrained devices do not comply with the requirements of current and upcoming Internet of Things (IoT) use cases. The IoT requires not only a lightweight but also a modular network stack, based on standards. We discuss functional and non-functional requirements for the software architecture of the network stack on constrained IoT devices. Then, revisiting concepts from the early Internet as well as current implementations, we propose a future-proof alternative to existing IoT network stack architectures, and provide an initial evaluation of this proposal based on its implementation running on top of state-of-the-art IoT operating system and hardware.

show abstract

Section: Related Work: Existing Network Stacksmentioning

confidence: 99%

Old Wine in New Skins?

Petersen

Lenders

Wählisch

et al. 2015

Proceedings of the 2015 Workshop on IoT Challenges in Mobile and Industrial Systems

View full text Add to dashboard Cite

show abstract

“…As previously commented, this CoAP implementation was developed on top of an unsupported and limited 6LoWPAN implementation named 6lowpancli [37]. In particular, as pointed out in [18,19], 6lowpancli provides only basic functionalities of 6LoWPAN. 6Lowpancli doesn't support any type of neighbor discovery mechanism, it is completely static and requires manual configuration.…”

Section: Related Workmentioning

confidence: 99%

“…6Lowpancli doesn't support any type of neighbor discovery mechanism, it is completely static and requires manual configuration. As reported in [18,19] the support for mesh network is not provided and when a packet with different destination address is received, it is just dropped. The results of a performance evaluation done in [18] show that 6lowpancli does not perform well in terms of energy consumption and latency.…”

Section: Related Workmentioning

confidence: 99%

“…Furthermore, being an adaptation of an external library its code does not result optimized for TinyOS. The implementation presented in [17] has been developed on top of a 6LoWPAN implementation that is no longer supported, and is affected by various limitations [18,19]. Therefore, the existing CoAP implementations for TinyOS would not allow either the functionalities or the performance offered by this protocol to be fully realized.…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

TinyCoAP: A Novel Constrained Application Protocol (CoAP) Implementation for Embedding RESTful Web Services in Wireless Sensor Networks Based on TinyOS

Ludovici

Moreno

Calveras

2013

JSAN

View full text Add to dashboard Cite

Abstract:In this paper we present the design and implementation of the Constrained Application Protocol (CoAP) for TinyOS, which we refer to as TinyCoAP. CoAP seeks to apply the same application transfer paradigm and basic features of HTTP to constrained networks, while maintaining a simple design and low overhead. The design constraints of Wireless Sensor Networks (WSNs) require special attention in the design process of the CoAP implementation. We argue that better performance and minimal resource consumption can be achieved developing a native library for the operating system embedded in the network. TinyOS already includes in its distribution an implementation of CoAP called CoapBlip. However, this is based on a library not originally designed to meet the requirements of TinyOS. We demonstrate the effectiveness of our approach by a comprehensive performance evaluation. In particular, we test and evaluate TinyCoAP and CoapBlip in a real scenario, as well as solutions based on HTTP. The evaluation is performed in terms of latency, memory occupation, and energy consumption. Furthermore, we evaluate the reliability of each solution by measuring the goodput obtained in a channel affected by Rayleigh fading. We also include a study on the effects that high workloads have on a server.

show abstract

“…As node density in sensor networks increases and these networks required connection with other networks via internet, then Internet Engineering Task Force (IETF) [2] defines IPv6 over LoWPAN as techniques to implement the TCP/IP protocol in WSNs [3]. 6LoWPAN provides a WSN node with IP communication capabilities by putting an adaptation layer above the IEEE 802.15.4 link layer for the packet fragmentation and reassembly purpose [4][5][6]. IP routing protocols are used to maintain routing tables on IP routers which indicates on which next-hop forwarding decision should be made for the destination of an IP packet.…”

Section: Introductionmentioning

confidence: 99%

Routing in IPv6 over Low-Power Wireless Personal Area Networks (6LoWPAN): A Survey

Kumar

Tiwari

2012

Journal of Computer Networks and Communications

View full text Add to dashboard Cite

6LoWPANs (IPv6-based Low-Power Personal Area Networks) are formulated by devices that are compatible with the IEEE 802.15.4 standard. To moderate the effects of network mobility, the Internet Protocol (IP) does not calculate routes; it is left to a routing protocol, which maintains routing tables in the routers. 6LowPAN uses an adaptation layer between the network (IPv6) and data link layer (IEEE802.15.4 MAC) to fragment and reassemble IPv6 packets. The routing in 6LoWPAN is primarily divided on the basis of routing decision taken on adaptation or network layer. The objective of this paper is to present a state-of-the-art survey of existing routing protocols: LOAD, M-LOAD, DYMO-Low, Hi-Low, Extended Hi-Low, and S-AODV. These routing protocols have compared on the basis of different metric like energy consumption, memory uses, mobility, scalability, routing delay, an RERR message, a Hello message, and local repair. We have also presented the taxonomy of routing requirement; parameter for evaluating routing algorithm, and it was found that the routing protocol has its own advantages depending upon the application where it is used.

show abstract

6LoWPAN Stacks: A Survey

Cited by 31 publications

References 1 publication

Old Wine in New Skins?

Old Wine in New Skins?

TinyCoAP: A Novel Constrained Application Protocol (CoAP) Implementation for Embedding RESTful Web Services in Wireless Sensor Networks Based on TinyOS

Routing in IPv6 over Low-Power Wireless Personal Area Networks (6LoWPAN): A Survey

Contact Info

Product

Resources

About