TinyOS Motes on the Internet: IPv6 over 802.15.4 (6lowpan)

Harvan, Matúš; Schönwälder, Jürgen

doi:10.1515/piko.2008.0042

Cited by 9 publications

(4 citation statements)

References 1 publication

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Due to our efficient implementation of CoAP, the success probability only slightly depends on the number of servers running on the nodes. As expected, a very high (i.e., higher than 60 requests/second) request rate severely impacts the access performance but this is due to the inherent limitations of the currently used 6LoWPAN library [24]. Given that, we can conclude that our CoAP implementation scales well with the number of server instances without causing a major and noticeable decrease in the access performance.…”

Section: A Coapsupporting

confidence: 60%

“…Also, CoAP features a transaction layer between the application protocol and UDP to provide basic reliability and session matching support 1 . We designed and developed a TinyOS CoAP implementation using the 6LoWPAN header-compression (HC) library from Harvan and Schoenwaelder (6lowpan [24]) which implements the first version of the HC (RFC 4944) [25]. CoAPP is a monolithic component providing client and server functionalities; it handles session data regardless of its type (either client or server), thus optimizing its memory usage.…”

Section: Constrained Application Protocolmentioning

confidence: 99%

See 1 more Smart Citation

Web Services for the Internet of Things through CoAP and EXI

Castellani

Gheda

Bui

et al. 2011

2011 IEEE International Conference on Communications Workshops (ICC)

125

View full text Add to dashboard Cite

Abstract-According to the Internet of Things (IoT) vision, everyday objects such as domestic appliances, actuators and embedded systems of any kind in the near future will be connected with each other and with the Internet. These will form a distributed network with sensing capabilities that will allow unprecedented market opportunities, spurring new services, including energy monitoring and control of homes, buildings, industrial processes and so forth.In this paper, we concentrate on the actual implementation of the communication technology, adopting the Representational State Transfer (REST) approach. REST only relies on the HTTP methods such as GET and POST. Embedded communication devices are addressed using Universal Resource Indicators (URI) and data is exchanged through standard XML.We present our TinyOS design and implementation of two components that will play a fundamental role in the communication stack of REST-based devices. First, we focus on the Constrained Application Protocol (CoAP), which allows RESTbased communications among applications residing in distributed and networked embedded systems. Second, we present our lightweight implementation of a EXI library: an efficient binary compressor for XML data files. Experimental results are provided in terms of compression, decoding (EXI) and access time (CoAP) performance.

show abstract

Section: A Coapsupporting

confidence: 60%

Section: Constrained Application Protocolmentioning

confidence: 99%

Web Services for the Internet of Things through CoAP and EXI

Castellani

Gheda

Bui

et al. 2011

2011 IEEE International Conference on Communications Workshops (ICC)

125

View full text Add to dashboard Cite

show abstract

“…Furthermore, TCP or SCTP are currently not supported on some platforms, like on TinyOS [Harvan08]. Hence, UDP may be the only option.…”

Section: Transport Protocol Constraintsmentioning

confidence: 99%

TinyIPFIX for Smart Meters in Constrained Networks

Schmitt¹,

Stiller²,

Trammell³

2017

View full text Add to dashboard Cite

This document specifies the TinyIPFIX protocol that is used for transmitting smart-metering data in constrained networks such as IPv6 over Low-Power Wireless Personal Area Networks (6LoWPAN, RFC 4944). TinyIPFIX is derived from IP Flow Information Export (RFC 7011) and adopted to the needs of constrained networks. This document specifies how the TinyIPFIX Data and Template Records are transmitted in constrained networks such as 6LoWPAN and how TinyIPFIX data can be converted into data that is not TinyIPFIX in a proxy device.

show abstract

“…As home networks are usually based on the IP protocol, sensor nodes should support IP, too [7]. This can be performed by using 6LoWPAN [8], [9], [10], an IPv6 standard for IEEE 802.15.4 networks. As IPFIX was designed to run on top of IP, it is not necessary to adapt IPFIX to work with other network layer protocols.…”

Section: A Application Scenariomentioning

confidence: 99%

IPFIX for wireless sensors in home networks

Schmitt

Braun

Carle

2009

2009 2nd IFIP Wireless Days (WD)

View full text Add to dashboard Cite

The developments in the military, health and home area call for new approaches for data acquisition in real-time. Such application areas frequently include challenging requirements for collection, processing and analysis of environmental data. Wireless Sensor Networks can collect the needed environmental data efficiently. Collected sensor node data needs to be transmitted in an efficient way due to limitations of sensor node resources in battery power and available bandwidth. In this paper, we present a method for efficient transmission of sensor measurement data using the IETF standard IPFIX. We show that its template based design is suitable for efficient transmission of senor data with low bandwidth consumption. Additionally, aggregation can be performed on top of IPFIX, which further reduces the amount of data. By using a standardized protocol like IPFIX, interoperability between devices from different vendors can be ensured.

show abstract

TinyOS Motes on the Internet: IPv6 over 802.15.4 (6lowpan)

Cited by 9 publications

References 1 publication

Web Services for the Internet of Things through CoAP and EXI

Web Services for the Internet of Things through CoAP and EXI

TinyIPFIX for Smart Meters in Constrained Networks

IPFIX for wireless sensors in home networks

Contact Info

Product

Resources

About