You are on page 1of 4

Abstract Vic s dng web services cho mng cm bin gi m v tr quan trng trong s bng

n ca Machine to Machine (M2M) communications. The Constrained Application Protocol


(CoAP) c Internet Engineering Task Force (IETF) ngh ti u ha t RESful web service
architecture nhm p ng cc rng buc ca mng khng dy, in hnh l mng cm bin ko
dy (WSN).

Trong bi bo ny, chng ta trnh by s pht trin ca CoAP protocol s dng trn h thng
nhng TinyOS. CoapBlip gm 20 Telos motes to thnh mt mng multi-hop s dng Routing
Protocol cho Low-power v Lossy Networks (RPL) gm 2 chc nng MRHOF vs OF0. CoAP s
dng c hai function trn cng vi Low Power Listening.

Introduction:
Trong mng cm bin ko dy, nh l 6LoWPANs phi chu cc rng bun nht nh: nng lng,
bng thng, b nh, v tiu chun IEEE 802.15.4 vi maximum packet size ch c 127 byte, cc
IP (internet protocol) hin ti ko p ng c cc yu cu trn, nn c s xut hin ca CoAp (
thc hin bi IETF Constrained RESful Invironments CorE) c b dng di tn CoapBlip
trn TinyOS p ng c nhng rng buc trn.

The IETF Routing Over Low power and Lossy networks (RoLL) pht trin ra mt Routing
protocol tn Routing Protocol for Low-power and Lossy Networks (RPL) s dng to nn cc
multi-hop cho WSN.

CoAP, 6LoWPAN, RPL and IP l nhng giao thc c bn nht cho mt h thng WSN.

Cng vi s pht trin ca cc ng dng ca WSN ( v d Intelligent Container tm cc container


b mt tng qu trnh vn chuyn c trn bin) , cc nh nghin cu k vng rng vic ng dng
cho h thng M2M l kh thi.

Cc nh nghin cu ko ngng pht trin CoAP, RPL, LPL protocols s dng 20 TelosB. Tuy
nhin s pht trin cng nh i n vic s dng nng lng, delay v LPL.

II. EVALUATED PROTOCOLS AND RELATED WORK

A. Constrained Application Protocol (CoAP)

CoAP l dng web protocol ch p ng cc yu cu ca mng ko dy. ng dng cho


M2M application, ta cn low message overhead, n gin, hn ch s dng fragmentation,
d liu ng tin cy v c ng b ha.

CoAP da trn m hnh client/ server ca HTTP ch l c phn nh hn. Resource c yu


cu v xc nhn bi URIs (Uniform Resource Identifiers ) s dng phng php
Representational State Transfer (REST). Khc vi HTTP, CoAP ng b tin nhn qua UDP-
User Datagram Protocol.

The total size of the CoAP server and client implementationon a sensor node is about 45430
bytes.

B. RPL

RPL c thit k cho low-power and lossy Ipv6 networks da trn source routing ( distance
vector rounting protocol ). RPL dng to mng multi-hop trong WSN. Trong TinyOS,
objective functions OF0 vs MRHOF c dng tm parent node v tnh ton hng.

C. LPL

Tnh ton nng lng tiu th v tit kim nng lng.

D. Related Work

RPL ch s dng OF0 cho cc t th nghim trn TinyOS v ContikiOS.

Mt vi v d khc ch CoAP: CoAP for ContikiOS, CoAPy, jCoAP. CoAp c pht trin
da trn nhng yu cu v low-power v multi-hop network. Trong s pht trin , ch c 4
hop network c s dng vs static routes (nh tuyn phng). Ngc li, nu ch s dng 20
nodes network, ta c th ty chnh routes thay v statically route c t trc.

im ni bt ca CoAP resources (ko bit dch sao) trong bi bo ny l s trong nhng ng


dng logic. Chng ta pht trin CoAP da trn s kt hp CoAP vs RPL trong multi-hop vi
2 object functions trn ( OF0 vs MRHOF ) trong iu kin c LPL hoc khng tm ra nng
lng tiu th cng nhng thng s ph hp nht.
III. TESTBED SETUP

For the experiments presented in this paper, a set of 20 TelosB nodes, operating at the 2.4
GHz ISM band with IEEE 802.15.4 based radio chips, are used. All sensor nodes are
configured to run on the TinyOS operating system includingthe Berkeley Low-power IP
stack (Blip 2.0) stack with Ipv and 6LoWPAN, RPL and CoapBlip. The global address of
each node is preconfigured.

We evaluate the performance of our CoAP implementation in terms of Round-Trip Time


(RTT) (tng thi gian bao gm gi v nhn ack), and number of bytes transmitted by using
two testbed setups.

We evaluate the performance of our CoAP implementation in terms of Round-Trip Time


(RTT) and number of bytes transmitted by using two testbed setups. The single-hop consists
of two nodes, where one runs as a CoapBlip server and one as a PppRouter. The multi-hop
testbed is setup with 20 TelosB sensor nodes, spread over 3 office rooms of the University (
hnh trn ). It consists of 19 CoapBlip server nodes and one PppRouter node. In both
scenarios, the PppRouter is used to connect the local computer to the WSN.

V d ny cng tng t ng dng Intelligent container trong thc t: mi thng container c


20 pallets ( cng thit b ), ta gn 4 sensor vo 4 cng kim sut trng thi container.
Trong Testbed setup ny, nng lng tiu th c a v gi t thp nht (-25dBm test
b lin kt). cng vi l so snh performance ca RPL ( OF0 v MRHOF) v nh
hng ca LPL ln appication layer. Node root (PppRouter) kch hot RPL sau khi khi
ng. Sau khi routes hnh thnh, cc CoAP client nhn thng tin t cc node mi 5 pht. Mi
test ko di 12h v thu c tng cng 2508 yu cu t CoAP client.

In the multi-hop setup, the following parameters are used for the evaluation:

RTT: ( mi senser node hot ng nh CoAP sever, Application layer thu nhn thi gian
thc hin qu trnh: thu cc gi ACK cha cc thng tin t sensor ( nhit , m,.. ) sau
yu cu ca cc nodes. Bao gm thi gian truyn li ). The ACK message carries the temperature,
voltage and humidity values piggy-backed in a Time-Length-Value (TLV) structure. The RTT includes the time
taken for any retransmissions (triggered by the CoAP layer) in case of lost packets.

Retransmissions: Cho bit tng s ln truyn li ti CoAP layer ( timeout sau 6s v ti a 5


ln ).

Packets lost: Cho bit s gi truyn ko thnh cng ( ko nhn ACK ).

Packet Delivery Ratio: T s gia s gi truyn thnh cng (nhn c ACK) v tng s
yu cu ca application layer.

IV. ANALYSIS OF RESULTS

This section details the evaluation of CoAP and RPL that are proposed to use in the
Intelligent Container project.

A. Single-Hop Evaluation

Trong phn ny, Route-Trip Time v tng s bytes c truyn trong m phng single-hop
s dng CoAP implementaion c m t nh trn.