8 IPv6 and Sensor Networks

8/8/2019 8 IPv6 and Sensor Networks

1/50


2/50


3/50

IPv6 Deployment and Support

Introduction

Standards and Technologies

onc us on

6DEPLOY IPv6 Training,Athens, 22/06/2010 3


4/50

Back roundIPv6 Deployment and Support

Different from most modules in this seriesNeed first to define Wireless SensorNetworks and show why they are different

Then show where IPv6 technology kicks inConsider some applications



5/50

What is a sensor?IPv6 Deployment and Support

You feel COLD.Instruments are more precise. They give

, , .

Thermometer

You feel your heartum ing !You feel WET .

Humidit Meter

Heart Monitor

Rain Gauge



6/50

Sensor Network TechnoloIPv6 Deployment and Support

Sensor nets often wireless towards sensorsMay use Wifi 802.11Often use Zi Bee 802.15.4 low- owerOther technology under development and use

Is good standard for heterogeneity

towards Internet

Often wired with normal technolo iesOften wireless e.g. cellular or Wifi



7/50




8/50

IPv6 Deployment and Support Network of small-footprint computers p m se or ong- e on ow power Equipped to sense physical data

Networked using low-power radio

PhyNetServer

Function:Sense any measurable physical parameter

Light, motion, chemicals, proximity, biometrics

Internet or Enterprise

wired or wireless u links =Area Network and communicate

Automatic meshing and routing over radioApply user-defined business logic Ph Net Routers

Sampling, summarizing, reporting events

Form:

Node (Processor, Radio, Storage) + SensorsEmbedded OS, Networking, ApplicationsServers and Routers interfacing with Enterprise ITsystems

Wireless Sensor Nodes



9/50

IPv6 Deployment and Support The term Sensor Web is used by the Open Geospatial

Consortium (OGC) and has the following characteristics:,devices that report data through the Web.entire networks can be seen as single interconnected nodes that

communicate via the Internet and can be controlled andaccessed through a web interface.,

interpretation and their cooperation as a whole, in order to sense

and respond to changes of their environment and extract.



10/50




11/50


12/50

Advanta esIPv6 Deployment and Support

Implementing IP requires tackling the general case, not

just a specific operational slice Potential to name and route to any IP-enabled device within securitydomain

o ust operat on esp te externa actorsCoexistence, interference, errant devices, ...

While meetin the critical embedded wireless requirements

High reliability and adaptabilityLong lifetime on limited energyManageability of many devicesWithin hi hl constrained resources



13/50

Sensor Network ConstraintsIPv6 Deployment and Support

Sensors are often small devices, in large numbers, that

need to be addressed ,they are not wired

Sensor networks are often wireless with insufficient

power to reach all nodesThey need wireless ad-hoc networks

Interoperability among different sensor networks and

seamless integration with existing IP networks is difficultSo far many are not even IP-enabled, but are changingSeveral recent protocols and systems have been

eve ope or t em6DEPLOY IPv6 Training,

Athens, 22/06/2010 13


14/50

Sensor Network ConstraintsIPv6 Deployment and Support

ontrary, t e nternet rotoco as een es gne or networ swithout these constraints in mind and, hence, traditionally other layer3 mechanisms have been developed and adapted to wirelesssensor networks

Big packet size power consumption

More Sensor Implementations are based on 802.15.4

n -ena e sensor networ requ resthe implementation of an IP stack in the sensor nodes and

a ro riate interworkin between IP la er and link la er.



15/50

Movin to IPv6IPv6 Deployment and Support

The ado tion of IP as the La er-3 rotocol toconnect wireless sensors has been slow down by

the common belief that IP is too large to fit on amemory constrained device.

There have been recent attempts to integrate Internet services

IEEE 802.15.4 protocol and the Internet protocol (IP).Yet, a real Internet of Things requires the large address space of

v .This extended address space together with its auto-configurationca abilities makes IPv6 a suitable rotocol for lar e scale sensornetwork deployments.



16/50

Movin to IPv6IPv6 Deployment and Support

IP-based protocols such as TCP/IP usually require

heavy resources to be allocated to a sensor node.ere ave een s u es con uc e o reso ve eproblems that occur when operating IP-based stacks in

,6LoWPAN working group (WG) has worked on IPv6 overIEEE 802.15.4.

It has reduced the header overhead of IPv6, thereby reducing itspower consumption.

network layers to handle interoperation between these layers andto reduce resources.



17/50

IPv6 over IEEE 802.15.4IPv6 Deployment and Support

Each sensor

uses IPv6 over IEEE 802.15.4, ,a far remote network.



18/50




19/50


20/50




21/50

IEEE 802.15.4IPv6 Deployment and Support

IEEE 802.15.4-2006 is a standard which specifies the

physical layer and media access control for low-rate- .maintained by the IEEE 802.15 working group.

, ,specification, each of which further attempts to offer acomplete networking solution by developing the upperlayers which are not covered by the standard.

Alternatively, it can be used with 6LoWPAN andstandard Internet protocols to build a WirelessEmbedded Internet.



22/50


23/50

A Low-Power Standard LinkIPv6 Deployment and Support

802.15.1 802.16. . (Bluetooth) (WiMax) . .

Class WPAN WPAN Metro Area WLAN LANLifetime(days) 100-1000+ 1-7 Powered 0.1-5 Powered

-,

BW 20-250 Kb/s 720 Kb/s 75Mb/s 11(b)-108(n)Mb/s10Mb/s-10Gb/s

Range (m) 1-100+ 1-10+ 50K 1-100+ 185 (wired)

GoalsLow Power,Lar e Scale Cable Cable Throu h ut Throu h ut

Low Cost ep acemen ep acemen

Low Transmit power, Low SNR, modest BW, Little Frames



24/50

IPv6 Deployment and Support. .

868MHz / 915MHzChannel 0 Channels 1-10 2 MHz

868.3 MHz 928 MHz902 MHz

Channels 11-26 5 MHz.

PHY

2.4 GHz 2.4835 GHz

16 channels in the 2.4GHz ISM band 10 channels in the 915MHz ISM band 1 channel in the European 868MHz band

Capable of at least 1 mWReceiver Sensitivity (Packet Error Rate


25/50

IPv6 Deployment and Support. .

PreambleStart ofPacket

Delimiter

PHYHeader

PHY ServiceData Unit (PSDU)

6 Octets 0-127 Octets

PHY Packet Fields Preamble (32 bits) synchronization

Frequency Bands 2.4 GHz PHY

PHY Header (8 bits)

Frame Length (7 bits)

, . 868MHz/915MHz PHY

868 MHz Band: 20 Kb/s (1 bit/symbol, 20

PSDU (0 to 1016 bits) Data field 915 MHz Band: 40 Kb/s (1 bit/symbol, 40Kbaud)



26/50

IPv6 Deployment and Support. .Network Topologies

Star, Peer-to-Peer, meshed

Full function device (FFD)Any topologyNetwork coordinator capableTalks to any other deviceArchRock nodes are FFD

e uce unc on ev ceLimited to star topologyCannot become a network coordinatorTalks only to a network coordinator

Each independent PAN selects a

unique identifierAddressing modes:

Network + device identifier (star)Source/destination identifier (peer-peer)

Full function device



27/50

IPv6 Deployment and Support ore v6 spec cat ons are sta e an we teste ra t

Standards

IPv6 Addressing Architecture, ICMPv6, Neighbor Discovery, Stateless- Routing Protocols, Tunneling, MIBs, Header Compression, MLD, etc.

2007: IPv6 WG now closed replaced by 6MAN (Maintenance) WGhttp://www.ietf.org/html.charters/ipv6-charter.html

IPv6 Transition, then now Operations focused Working GroupsNGTrans WG (closed), v6ops (active)

Working Groups focusing on Wireless Sensor Networks6LoWPAN - IPv6 over Low power Wireless Personal Area Networks

-. . . .RoLL - Routing Over Low power and Lossy networkshttp://www.ietf.org/html.charters/roll-charter.html



28/50


6lowpan is an acronym of IPv6 over Low power Wireless Personal AreaNetworks. 6lowpan is the name of the working group in the internet areaof IETF.

that allow IPv6 packets to be sent to and received from over IEEE802.15-based networks.

v4 an v6 are t e wor orses or ata e very or oca -areanetworks, metropolitan area networks, and wide-area networks such asthe Internet.Likewise, IEEE 802.15.4 devices provide sensing communication-abilityin the wireless domain. The inherent natures of the two networks

, .



29/50


Adapting the packet sizes of the two networks

IPv6 requires the maximum transmission unit (MTU) to be at least 1280 Bytes. Incontrast, IEEE802.15.4's standard packet size is 127 octets.

An adaptation mechanism to allow interoperability between IPv6 domain and the IEEE802.15.4 can best be viewed as a layer problem. Identifying the functionality of thislayer and defining newer packet formats, if needed, is an enticing research area.RFC 4944 proposes an adaptation layer to allow the transmission of IPv6 datagrams

. . .

IPv6 nodes are assigned 128 bit IP addresses in a hierarchical manner,through an arbitrary length network prefix.IEEE 802.15.4 devices may use either of IEEE 64 bit extendedaddresses or (after an association event), or 16 bit addresses that are

uni ue within a PAN. Small Packets to keep packet error rate low and permit media sharing



30/50

IPv6 Deployment and Support 64-bit Suffix or

64-bit Prefix Interface Identifier

2001 0DB8 Interface ID

Global, ULA, Link Local

802.15.4AddressPAN* 00FF FE00 short

-64

PAN* - complement the Universal/Local" (U/L) bit,

Allow IP routing over a mesh of 802.15.4 nodes- -



31/50

IPv6 Deployment and Support Coexistence with other network protocols over same linkHeader dispatch (dsp) - understand whats coming

x00Not a LoWPAN frame

10LoWPAN IPv6 addressing header HeaderDispatch

11

LoWPAN fragmentation header

Src EUI-64Dst EUI-64Dst

PAN IDSrc

PAN ID

Preamble SPD PHYHeader

Network Hdr + Data FCSFrameControl

S.N. Addressing dsp


c e s - c e s


32/50

IPv6 Deployment and Support RFC 4944 Almost no overhead for the ability to interoperate and scaleMesh + Fragmentation Frag. HC1HC1

dspMesh Addr.

tan ar v ea er ytes vs nt re . . ytes

Frame Fragmentation Frag. HC1HC1dsp

HC1

IP Upper layersHC1dsp

IPv6 6LoWPAN (RFC 4944)

. dsp


PAN IDSrc

PAN ID

Preamble SPD PHYHeader

Network Hdr + Data FCSFrameControl

S.N. Addressing


6 Octets 0-127 Octets


33/50

IPv6 Deployment and Support Allow link-layer mesh routing under IP topology. .

Similar to LAN switching within IP routing domain in Ethernet Originating node and Final node specified by either short or EUI-64 address

In addition to IP source and destination V = Very First, F = Final 0= EUI-64, 1= short

Hops Left (4 bits) up to 14 hops, then add byte (indicated by 0xF) if more hops Mesh protocol determines node at each mesh hop

Mesh Header V F01 Hops Left OriginatorAddress FinalAddress


PAN IDSrc

PAN ID

Preamble SPD PHYHeaderNetwork Hdr + Data FCSFrameControl S.N. Addressing


6 ctets 0-127 ctets


34/50

6LoWPAN vs Zi beeIPv6 Deployment and Support

g eecommunication between 15.4 nodes (layer 2 in IP terms), not the rest of the

network (other links, other nodes).Defines new upper layers, all the way to the application, similar to IRDA, USB,and Bluetooth, rather utilizing existing standards.Specification in progress (Zigbee 2006 incompatible with Zigbee 1.0, Zigbee Pro

Code size for full featured stack is 90KB vs. 30KB for 6LoWPAN6LoWPAN

defines how established IP networking layers utilize the 15.4 link.It enables 15.4 to15.4 and 15.4 to non-15.4 communication

It enables the use of a broad body of existing standards as well as higher levelprotocols, software, and tools.It is a focused extension to the suite of IP technologies that enables the use of anew class of devices in a familiar manner.



35/50

RoLL - Routin Over Low owerIPv6 Deployment and Supportand Lossy networks

Low power and Lossy networks (LLNs) are made up ofmany embedded devices with limited power, memory,

.They are interconnected by a variety of links, such as

. . , , ,

other low power PLC (Powerline Communication) links.LLNs are transitionin to an end-to-end IP-basedsolution to avoid the problem of non-interoperable

networks interconnected by protocol translationgateways and proxies.



36/50


Distinguishing characteristics:LLNs operate with a hard, very small bound on state.

, .Typical traffic patterns are not simply unicast flows (e.g. in somecases most if not all traffic can be point to multipoint).

In most cases, LLNs will be employed over link layers withrestricted frame-sizes, thus a routing protocol for LLNs should be.

LLN routing protocols have to be very careful when trading offefficiency for generality; many LLN nodes do not have resourceso was e.

These specific properties cause LLNs to have specific.



37/50


Existing routing protocols such as OSPF, IS-IS,

AODV, and OLSR have been found to notsatisfy all of these specific routing requirements.The Working Group focuses only on IPv6 routing

Various aspects are taken into considerationin l in :

high reliability in the presence of time

connectivity while permitting low-power operation



38/50

IPv6 Deployment and Supporte - on gur ngThroughput

Latency



39/50

IPv6 Deployment and Supportca ng eMax

Throughput

Latency



40/50

IPv6 Deployment and Supportca ng eMax

Throughput

Latency



41/50

IPv6 Deployment and Supportes ency o eThroughput

Latency



42/50

IPv6 Deployment and Supportes ency o eMax

Throughput

Latency



43/50

IPv6 Deployment and Supporto y n,

mobility of nodes within the WSN

Emer in mobilit atterns see RUNES/U-2010 PANs for emergency responders (firemen with uniform-attached sensors, etc.

Dynamically deployed nodesNetwork Mobilit NEMO scenarios a lMobile Ad-hoc Network Mobility (MANEMO) often more

suitableAvoid nested tunneling



44/50

IPv6 Deployment and Supporto e pera ng ys emsVarious compact operating systems developed forsensor nodes

ma memory s zePower saving facilities

e uce v tacExamples:

ont , ttp://www.s cs.se/contTinyOS, http://www.tinyos.net

Common smart sensor node is MOTES



45/50


ny s an open-source operat ng system es gne orwireless embedded sensor networks.

It features a com onent-based architecture which enables ra idinnovation and implementation while minimizing code size.TinyOS's component library includes network protocols,

, , .

TinyOS's event-driven execution modelenables fine- rained ower mana ementallows the scheduling flexibility made necessary by theunpredictable nature of wireless communication and physical

.TinyOS has been ported to over a dozen platforms andnumerous sensor boards



46/50


47/50


Contiki o en source hi hl ortable multi-taskin OS for networkedmemory-constrained networked embedded systems.A typical Contiki configuration is 2 KB of RAM and 40 KB of ROM.

ont cons sts o an event- r ven erne on top o w c app cat onprograms are dynamically loaded and unloaded at runtime.Contiki contains two communication stacks: uIP and Rime.

uIP - a small RFC-compliant TCP/IP stack that makes it possible forContiki to communicate over the Internet.me - a g we g commun ca on s ac a me a ow-power ra os.

Contiki runs on a variety of platform ranging from embedded

microcontrollers to old home com uters. Code foot rint is on the order ofkilobytes and memory usage can be configured to be as low as tens ofbytes.


.


48/50

IPv6 Deployment and Supportgen aIntroductionThe Generic ComponentsStandards and TechnologiesConclusion



49/50

IPv6 Deployment and Supportonc us on

Wireless Sensor Networks will be everywhere

Internet of things

requiredO en standardInteroperable with existing IP infrastructureInteroperability with existing non-IP WSNs



50/50

Date post:	10-Apr-2018
Category:	Documents
Upload:	rahil16
View:	217 times
Download:	0 times

8 IPv6 and Sensor Networks

Documents