INTRODUCTION TO IP-USNnetworking.khu.ac.kr/html/lecture_data/2007_fall/IP-USN_20071103.pdfLarger...
Transcript of INTRODUCTION TO IP-USNnetworking.khu.ac.kr/html/lecture_data/2007_fall/IP-USN_20071103.pdfLarger...
2
Outline
Environments to IP-USNRelated Standardization
IEEE 802.15.4ZigBee AllianceIEEE 802.15 BAN (Body Area Networks) SGIETF 6LoWPAN WG
Conclusion
2
Environments to IP-USN
4
Network Trends4
Internet Technologies were
Control NetworkControl NetworkBuildingBuilding
PlantPlantVehicleVehicleAircraftAircraft
TelemetryTelemetryetcetc
IP Tech.IP Tech.
DataData NetworkNetworkComputerComputer
Voice NetworkVoice NetworkTelephoneTelephone
5
Internet Technologies are
Control NetworkControl NetworkBuildingBuilding
PlantPlantVehicleVehicleAircraftAircraft
TelemetryTelemetryetcetc
IP TechnologiesIP Technologies
DataData NetworkNetworkComputerComputer
Voice NetworkVoice NetworkTelephoneTelephone
New type of network(e.g. Home network)
Network Trends (con’t)
6
Internet Technologies will be
IP TechnologiesIP Technologies
Control NetworkControl NetworkBuildingBuilding
PlantPlantVehicleVehicleAircraftAircraft
TelemetryTelemetryetcetc
DataData NetworkNetworkComputerComputer
Voice NetworkVoice NetworkTelephoneTelephone
New type of network(e.g. Home network)
Network Trends (con’t)
7
USN vs IP-USN
NGN
USN Gateway
MobileGateway
SinkNode
SinkNode
SinkNode
U-Sensor Network
IP or Non-IP
IP Network(NGN, Internet, WLAN, WiBro)
IP basedSearch Service(DNS, google)
IP basedApplication
Service(Web)
Convert
Separation
USN
combine
IP-USN
8
USN vs IP-USN (con’t)
Non IP-USN IP-USN
Independently Site, Service, Technology
Locally, Small Scale
ALL-IP based convergence network
Global, Mutuality
9
Currently Available USNs
Wireless Sensor NetworkZigBee Network
6LoWPAN
Control another node
1:1 Communication
GatewayZigBee
Gateway
Sink Node
Send data periodically
Query
Data
Query
Data
DB Server Host
Web Server
Get information from internet
Control another node
End-to-End connection across network
Directly control node and p2p
communication
Indirectly control node
10
Definition and Feature of IP-USN
DefinitionInternet Protocol-Ubiquitous Sensor NetworkAll-IP based USN technology provides new valuable services
By integrating USN technology with Internet Infrastructure
Supporting the mobility to Sensor Node, Gateway and Sink Node
FeaturesEffectively integrate with Infrastructure such as NGN, IPv4/IPv6, USN
Scalability
Reliability
Dynamic
Globally
Mobility
Integration
Service Discovery
11
IP-USN Requirements
IP-USN GatewayInternet Connectivity to Legacy USN
IPv6Globally Unique Identification
H/W ChipLow Cost, Low Power and Low Bandwidth
Light-weight IP, Tiny OSEmbedded Compact Stack
SecurityConfidentiality and Integrity Protection
Killer Applications u-City, u-IT, u-Health
12
Advantage of IP-USN
Advantage Detail
Connection with NGNdirectly
Available to use abundance internet application service (web browser, messenger, telnet)
Construction is simple and easyReduction of development period, required small-sized memoryBetter competitive power of cost than Existing equipment
Suitable for large scale infraIP-USN is suitable for large scale u-City and supports optional function, such as mobility
Possible convergence network management Using IP-based network management ability
Ethernet or otherMAC / PHY
Adaptation Layer
IEEE 802.15.4 MAC/PHY
Adaptation Layer
IEEE 802.15.4 MAC/PHY
Network Layer(IPv6)
Application Layer
Transport Layer(TCP/UDP)
Network Layer(IPv6)
Ethernet or otherMAC / PHY
Network Layer(IPv6)
Ethernet or otherMAC / PHY
IEEE 802.15.4 MAC/PHY
Application Layer
IEEE 802.15.4 MAC/PHY
Transport Layer(TCP/UDP)
Application Layer
Network Layer(IPv6)
Transport Layer(TCP/UDP)
Application Layer
Applicationsupport Layer
ZigbeeNetwork Layer
IP-USN(Delivery)
Zigbee(Application transformation)
IP host IP-USN Gateway Sensor node IP host Zigbee Gateway Zigbee node
Applicationsupport Layer
ZigbeeNetwork Layer
13
IP-USN Architecture
Lightweight IPv6
U-City Application Service Disaster Prevention Application Service
Lightweight Socket API
Security
IP-USN Management(SNMP)
Service Search(Simple SLP)
Lightweight TCP Lightweight UDP
Lightweight ICMPv6
Scalable Routing
MeshRouting
Commissioning Mobility
Fragment/Reassembly
IEEE 802.15.4
IP-USN Node IP-USN Router LAN, WLAN, WiBro, HSDPA Connection
HeaderCompression
Service Search(Based on DNS)
PHY/MAC Layer
Adaptation Layer
Network Layer
Transport Layer
Application Layer
Other Services
14
Why IP
Most of the IP based technologies already exist, well known and proven to be working.
The pervasive nature of IP networks allows use of existing infrastructure.
Intellectual property conditions for IP networking technology is either more favorable or at least better understood than proprietary and newer solutions.
15
Why IP (con’t)
What about ZigBeeNew MAC – CSMS/CA + GTS/BeaconingNew Network – AODV + Cluster TreeNew API – ZigBee API + ZDOsStack is too:
ComplexExpensiveNot IP compatible *GTS: Guaranteed Time Slot
*ZDO: ZigBee Device Object
16
Why IPv6
Pros:
More suitable for higher density (futuristically 2 orders of magnitude larger than traditional networks)
Statelessness mandated
No NAT necessary (address extra cost to the cost prohibitive WSN)
Possibility of adding innovative techniques such as location aware addressing
IEEE 64 bit address subsumed into IPv6 address
Cons:
Larger address width (Having efficient address compression schemes may alleviate this con)
Complying to IPv6 node requirements (IPSec is mandated)
Limited address space
Not as compressible
NAT functionality needs gateways, etc leads to more cost
Statelessness not mandated
IPv6
IPv4
17
ZigBee vs IP-USN
ZigBee IP-USN
PHY/MAC Layer IEEE 802.15.4
Standardization Group ZigBee Alliance IETF 6LoWPAN WG
State of Standardization ZigBee Specification in v.1.0 RFC, Internet Draft
Scope of Protocol Stack All Adaptation Layer
Network Address 16bits or 64bits address IPv6 address
Unique of Network Address Unique Identification within PAN Globally Unique Identification
Address Assignment ZigBee Coordinator assigns the 16bits address IPv6 address by using EUI-64
Scalability of Topology Low High
Compatibility of IPv6 Network
Low High
Routing Support Layer ZigBee Network Layer Adaptation Layer
Routing Hierarchical Routing, AODV Algorithm In Progress
Gateway Function Application Layer Level Network Layer Level
Service Binding method Support TCP/UDP
Security Support Consider
Management Difficult Easy (SNMPv3)
Application Program Few Many (ISV, Developer)
Service Discovery Local Global
Mobility Difficult Easy (mobile IPv6)
18
Design Principles of IP-USN
Power managementLow CostConnectivity of IPScalabilitySecurityAutonomousManagementHeterogeneityMobilityEasy to use
19
Challenges of IP-USN
Impact Analysis Addressing Routing SecurityNetwork
Management
Low power (1-2 years lifetime on batteries)
Storage limitations, low overhead
Periodic sleep aware routing, low overhead
Simplicity (CPU usage), low overhead
Periodic sleep aware management, low overhead
Low cost (<$10/unit)
Stateless address generation
Small or no routing tables
Ease of Use, simple bootstrapping
Space constraints
Low bandwidth (<300kbps)
Compressed addresses
Low routing overhead
Low packet overhead
Low network overhead
High density (<2-4 unit/sq ft)
Large address space – IPv6
Scalable and routable to a node
Robust Easy to use and scalable
IP network Interaction
Address routable form IP world
Seamless IP routing
Work end to end from IP network
Compatible with SNMP, etc
20
Classification of IP-USN Technology
Function DetailEncapsulation mechanism
Address assignmentHeader compression
Scalable routing
Mesh routing
Hierarchical routing
Secure routing
FloodingMulticasting
IPv6 multicast address
Ethernet bridge
WiFi bridgeIP-USN Bridge
IP-USN protocol stackSensor node platform
Platform architecture
Mobility of USN manager
Mobility Management
Multi-WPAN
Mobility of USN sensors
Route optimization
Handover optimization
Network based mobility (NEMO)
IP-USN
Routing
Route over IP or Mesh under IP
21
Classification of IP-USN Technology (con’t)
Scanning, Self commissioning
Security policies, Key exchange
Channel policies
Joining policies
Sensor discovery
Mechanism of acquiring data from sensors
Key management
Authentication Header (AH)
Securing communication
Security Management
Network Management
DNS and ENUM approach
Socket APIProgramming API
IOCTL
IP-USN Chipset Onchip IP-USN architecture
Encryption Security Payload (ESP)
Securing binidng update
MAC PIBs and PHY PIBs
RMON, Sensor MIBs
IP and Application parameters
SLPService Discovery
IP-USN
Router advertisement
Commissioning
StandardizationIEEE 802.15.4ZigBeeIEEE 802.15 BANIETF 6LoWPAN
23
IEEE 802 Wireless Space23
Data Rate (Mbps)
Ran
ge
ZigBee802.15.415.4c
802.15.3802.15.3c
WiFi802.11
10 100 1000
WPAN
WLAN
WMAN
WWAN
0.01 0.1 1
Bluetooth802.15.1
IEEE 802.22
WiMaxIEEE 802.16
IEEE 802.20
24
IEEE 802.15.4
802.15.4 is a simple packet data protocol for lightweight wireless networks
Channel Access is via Carrier Sense Multiple Access with collision avoidance and optional time slottingMessage acknowledgement and an optional beacon structureMulti-level securityWorks well for
Long battery life, selectable latency for controllers, sensors, remote monitoring and portable electronics
Configured for maximum battery life, has the potential to last as long as the shelf life of most batteries
24
25
IEEE 802.15.4 PHY Overview
PHY functionalities:Activation and deactivation of the radio transceiverEnergy detection within the current channelLink quality indication for received packetsClear channel assessment for CSMA-CAChannel frequency selectionData transmission and reception
25
26
IEEE 802.15.4 PHY Overview (con’t)26
Frequency Band Coverage Data# of
ChannelsRx
SensitivityModulation
ISM Worldwide 250kbps 16 -85dBm O-QPSK
Europe 20kbps 1 -92dBm BPSK
ISM America 40kbps 10 -92dBm BPSK
2727
PreambleStart ofPacket
Delimiter
PHY Header
PHY ServiceData Unit (PSDU)
4 Octets 0-127 Bytes
Sync Header PHY Payload
Frame Length(7 bit)
Reserve(1 bit)
1 Octets 1 Octets
IEEE 802.15.4 PHY Frame Structure
PHY packet fieldsPreamble (32 bits) – synchronization Start of packet delimiter (8 bits) – shall be formatted as “11100101”PHY header (8 bits) –PSDU lengthPSDU (0 to 127 bytes) – data field
28
Star and peer-to-peer topologiesContention Control
CSMA-CASuperframe
Associationchannel access mechanismPacket validation and message rejectionOptional guaranteed time slots
Guaranteed packet delivery
Facilitates low-power operationUsing PAN ID and 64 bits address and 16bits address
28
IEEE 802.15.4 MAC Overview
29
Payload
PH
Y L
ayer
MA
CLa
yer MAC Header
(MHR)MAC Footer
(MFR)
MAC Protocol Data Unit (MPDU)
MAC Service Data Unit(MSDU)
PHY Header(PHR)
Synch. Header(SHR)
PHY Service Data Unit (PSDU)
4 Types of MAC Frames:
• Data Frame
• Beacon Frame
• Acknowledgment Frame
• MAC Command Frame
IEEE 802.15.4 MAC Frame Structure
30
Full function device (FFD)Any topologyNetwork coordinator capableTalks to any other device
Reduced function device (RFD)Limited to star topologyCannot become a network coordinatorTalks only to a network coordinatorVery simple implementation
30
IEEE 802.15.4 Device Type
3131
Full function device Reduced function device
Star
PANCoordinator
Cluster Tree
PANCoordinator
Mesh
PANCoordinator
IEEE 802.15.4 Topology Model
32
IEEE 802.15.4 Addressing
Two or more devices with a POS communicating on the same physical channel constitute a WPAN which includes at least one FFD (PAN coordinator)
Each independent PAN will select a unique PAN identifier
All devices operating on a network shall have unique 64-bit extended address. This address can be used for direct communication in the PAN
32
33
IEEE 802.15.4 Addressing (con’t)
A member can use a 16-bit short address, which is allocated by the PAN coordinator when the device is associated.
Addressing modes:star: Network (64 bits) + device identifier (16 bits)peer-to-peer: Source/destination identifier (64 bits)cluster tree: Source/destination cluster tree + device identifier (unclear yet)
33
34
What is ZigBee
Foundation provided by IEEE 802.15.4Targeted at home, building and industrial automation and controls, consumer electronics, PC peripherals, and medical monitoringPerformance metrics are simplicity, long battery life, networking capabilities, reliability, and costZigBee Alliance provides standards definition for interoperability, certification testing, and branding
34
35
ZigBee Alliance
A rapidly growing, worldwide, non-profit industry consortium consisting of over 60
Leading semiconductor manufacturersTechnology providersOEMsEnd-users
Mission: to enable reliable, cost-effective, low-power, wirelessly networked, monitoring and control products based on an open global standard
35
3636
The ZigBee Promoters
37
ZigBee Applications37
TELECOM SERVICES
m-commerceinfo servicesobject interaction (Internet of Things)
ZigBeeWireless Control that
Simply Works
HOME CONTROL
CONSUMER ELECTRONICS
TVVCRDVD/CDremote
securityHVAClighting controlaccess controlirrigation
PC & PERIPHERALS
INDUSTRIALCONTROL
asset mgtprocess controlenvironmental
energy mgt
PERSONAL HEALTH CARE
BUILDING AUTOMATION
securityHVACAMR
lighting controlaccess control
mousekeyboardjoystick
patient monitoring
fitness monitoring
38
ZigBee Architecture38
Application Layer
Network Layer
MAC Layer
Physical Layer
ZigBee
IEEE 802.15.4
39
ZigBee Architecture (con’t)39
SecurityServiceProvider
ZDO
Managem
ent Plane
ZigBee Device Object(ZDO)Application
Object 240Application
Object 1
APS SecurityManagement
APS MessageBroker
ReflectorManagement
NWK SecurityManagement
NWK MessageBroker
RoutingManagement
NetworkManagement
2.4 GHz Radio 868/915 MHz
NLDE-SAP
MLDE-SAP
PD-SAP
MLME-SAP
PLME-SAP
NLM
E-S
AP
AP
SM
E-S
AP
Endpoint 240APSDE-SAP
Endpoint 1APSDE-SAP
ZDO
Public
Interfaces
Endpoint 0APSDE-SAP
…
Application (APL) Layer
Application Framework
Application Support Sublayer (APS)
Physical (PHY) Layer
Medium Access Control (MAC) Layer
Network (NWK) LayerIEEE 802.15.4Defined
ZigBeeTM AllianceDefined
End manufacturerdefined
Layerfunction
Layerinterface
40
ZigBee Device Model
ZigBee Coordinator (ZC)One and only one required for each ZigBee network.
ZigBee Network has unique PAN ID and channel no
Initiates network formation.
Acts as 802.15.4 PAN coordinator (FFD).
May act as router once network is formed.
ZigBee Router (ZR)Optional network component.
May associate with ZC or with previously associated ZR.
Acts as 802.15.4 coordinator (FFD).
Participates in multihop routing of messages.
ZigBee End Device (ZED)Joins ZC or ZR.
Optional network component.
Acts as 802.15.4 End device (RFD).
Optimised for very low power operation
Shall not allow association and shall not participate in routing.
40
4141
ZigBee End Device ZigBee Coordinator
ZigBee Router
Topology of ZigBee Network
42
ZigBee Address Assignment
Distributed address assignment mechanismCm, Lm, Rm should be determined first.
Cskip(d) : a gap between direct children of the node
Address
< Formula for assigning address >
1
1 ( 1), if Rm = 1( ) 1 , otherwise
1-
Lm d
Cm Lm dCskip d Cm Rm Cm Rm
Rm
− −
+ ⋅ − −⎧⎪= ⎨ + − − ⋅⎪⎩
( )
Where 1 ( - ) and represents the address of the parent.n parent
parent
A A Cskip d Rm n
n Cm Rm A
= + ⋅ +
≤ ≤
< Formula for Cskip >
- nwkMaxChildren(Cm)- nwkMaxDepth(Lm)- nwkMaxRouters(Rm)
43
ZigBee Address Assignment (con’t)
Distributed address assignment mechanism
Cskip=1Addr=28
Cskip=5Addr=22
Cskip=5Addr=43
Cskip=5Addr=64
Cskip=0Addr=66
Cskip=1Addr=65
Cskip=1Addr=2
Cskip=5Addr=1
Cskip=1Addr=23
ZigBee CoordinatorCskip=21Addr=0
Cskip=1Addr=70
Depth in the network, d
Offset value, Cskip(d)
0 21
1 5
2 1
3 0
nwkMaxChildren=4nwkMaxRouters=4nwkMaxDepth=3
44
ZigBee Security
Master keyIt is used to establish one link key(shared key) between two nodes.
Link keyIt is shared by two nodes.It is used to encrypt network key(shared key)by two nodes.
Network keyIt is shared by all nodes in a network.It is used to encrypt data to send.
44
45
ZigBee Security (con’t)
By using both master keys of each node, link key can be established.Both node 1 and node 2 have a same link key.
45
1 2
Master key #2
Master key #1
1 2
Link key Link key
4646
1 2
Link key Link key
Network key
1 2
By using link key of sender, network key can be encrypted.
The encrypted network key is sent from node 1 to node 2, and both nodes have a same network key.
By using the network key, data can be encrypted and transmitted between the nodes.
Network key Network key
ZigBee Security (con’t)
47
Sensor Network Mobility (SNEMO)
Sensor NEMO Router(SNEMO Router)
NEMO Mobile Routers
Sensor NEMO(SNEMO)Environments
Sensors in BodyArea Network (SBAN)
Sensors in PersonalArea Network (SPAN)
Sensors in VehicleArea Network (SVAN)
Sensor NEMO Node
IPv6 Infrastructure Networks
Access RouterAccess RouterAccess Router
Home Gateway
Sensors in BodyArea Home (SHAN)
NEMOHome Agent
Mobile Routers• MR connects each other by Mesh
routing• MR has two addresses
• Home Address / Mobile Network Prefix
• Global Routable Address (CoA)
Sensors• IPv6-enabled Sensors(6LoWPAN) are
installed at the NEMO Environments.
Access Routers• Access Routers are fixed at the
Internet• Access Routers provide a global
routable address to MRs and connectivity to the Internet
Reference Environments
48
Scenario for Supporting Network Mobility of ZigBee network
Mobile ZigBeeNetwork 1
HomeAgent 1(Server)
IPv6 Internet
MobileZigBee network
Gateway 1(Mobile Router)
Mobile ZigBeeNetwork 1
MobileZigBee network
Gateway 1(Mobile Router)
BU
BA
Data orCommand
Mobile ZigBeenetwork movesto another link
by mobile router
Mobile ZigBeeNetwork 2
MobileZigBee network
Gateway 2(Mobile Router)
HomeAgent 2(Server)
Data orCommand
49
Mobile Router Architecture for Supporting Network Mobility of ZigBee network
Mobile ZigBeeNetwork Gateway
(Mobile Router)
ZigBeeDevice
HomeAgent
(Server)
AddressMapping Table
ZigBee IPv6Translator
BindingUpdate List
ZigBee Network IPv6 Network
BUBinding Update with “Z” Flag
[Binding Cache]
HoA CoA
MR’s Home of Address
MR’s Care of Address
… …
PAN ID Short Addr.
64bits Addr.
ZigBeePAN ID
16bits short
address
64bits extended address
ZigBee Addr. IPv6 Addr.
ZigBee Device Address
Home Agent
(server) Address
… …
ZigBee PAN
Co-ordinaitor
option
HoA
option
HA
(IPv6
dst)
CoA
(IPv6
src)
HA
(IPv6
src)
CoA
(IPv6
dst)
HoA
option
BA
HA (IPv6 src)
CoA (IPv6 dst)
Data or Command
(payload)
IPv6 PacketMR ID(src) Device ID
(dst)
Data or Command (payload)
ZigBee frame
[Address Mapping Table]
50
IEEE 802.15 BAN (Body Area Network) Study Group
Implanted
Body-worn
Internet
Ref: IEEE 802.15-07-0564
51
Body Area Network
Broad range of possible devicesBroad range of media typesConnect everything you carryon you and with youOffer “Connected User” experienceMatches low power environmentChallenge – scalability data rate, power
52
Body Area Networks – Target PositionAverage power consumption, sustained data rate
1000 mW500 mW100 mW50 mW10 mW
1 Gbit/s
100 kbit/s
1 Mbit/s
10 Mbit/s
100 Mbit/s
1 kbit/s
10 kbit/s
Wireless USB
IEEE 802.11 a/b/g
Bluetooth
IEEE 802.15.4
200 mW20 mW
Body Area Network
5 mW2 mW
53
BAN Uses Scenario : Body Sensor Network
Medical applicationVital patient dataWireless sensorsLink with bedside monitorCount on 10 – 20 sensors
Five similar networks in rangeMinimum setup interactionPotentially wide applicationTotal traffic / patient < 10 kbps
54
BAN Uses Scenario : Fitness Monitoring
Central device is MP3 playerWireless headset includedExpand functionality
Speed, distanceHeart rate, respiration monitorTemperature sensorPacing informationLocation informationWristwatch display unitEtc.
Total system load < 500 kbpsSynchronization may go faster
55
BAN Uses Scenario : Wearable Audio
Central device is headsetStereo audio, microphoneConnected devices
Cellular phoneMP3 player, PDACD audio playerAP at homeHandsfree carRemote controlOthers
Requires priority mechanismNetwork load < 500 kbps
56
BAN Uses Scenario : Mobile Device Centric
Mobile terminal is central point
Covers broad set of dataSensors – vital, otherHeadsetPeripheral devicesHandsfree / car
Provide gateway to outsideOffload sensor data, other
Requires priority mechanism
Network load < 500 kbps
57
BAN Technical Requirements
There is no specific standard for BANsCurrent standards come close for specific use cases, not broad enoughIssues: power consumption, discovery, QoSSupport for very low power devices, sensors
Target less than 10% power consumption for communications compared to total deviceHave single standard with broad range of supported data rate - scalability
58
BAN Requirements
Distance 2 m std, 5 m specialPiconet density 2 - 4 nets / m2
Devices per network max. 100Net network throughput 100 Mbit/s max.Power consumption ~ 1mW / Mbps
(@ 1 m distance)
Startup time < 100 us, or< 10% of TX slot
Latency (end to end) 10 ms Network setup time < 1 sec
(after initial setup, per device)
59
BAN Requirements (con’t)Implementation module cost
Should be comparable to Bluetooth module
Effective sleep mode(s)Concept for effective, remote wake-upOperates in global, license-exempt bandPrivacy, securityPeer to peer communication, point to multi-pointOmni-directional antennas: small, flexibleFuture proof [for 5 years]
Upgradeable, scaleable, backwards compatibility
Support for several power management / consumption schemes [classes]Quality of service, guaranteed bandwidth
Specific definitions, depends on application
Graceful degradation of servicesDepends on application, not always desireable
Concurrent availability of asynchronous and isochronous channelsLow duty cycle and high duty cycle modesVery low duty cycle applications (sensors)
60
IETF 6LoWPAN WG (IPv6 over IEEE 802.15.4)
1st BOF @ IETF-61
1st WG @ IETF-62
2nd WG @ IETF-63
3rd WG @ IETF-64
4th WG @ IETF-65 Rechartering: IPv6 Bootstrapping / ND Optimization / Stateful Header Compression /Transport Application analysis / Mesh routing / Security analysis
draft-ietf-6lowpan-problems-00draft-ietf-6lowpan-format-00
Intel, Invensys, Sun Microsystems- Survey on IPv6 adoption over IEEE 802.15.4- Technical solution (Sub-IP concept)
Ready to the RFC
General discussion
Security considerations
Phase I
Phase II
5th WG @ IETF-66
6th WG @ IETF-67
Rechartering
TinyOS: new format
7th WG @ IETF-68
Rechartering-II
61
Overview of 6LoWPAN
No method exists to make IP run over IEEE 802.15.4 networks
Worst case .15.4 PDU 81 octets, IPv6 MTU requirements 1280 octets
Stacking IP and above layers “as is” may not fit within one 802.15.4 frame
IPv6 40 octets, TCP 20 octets, UDP 8 octets + other layers (security, routing, etc) leaving few bytes for data
Not all adhoc routing protocols may be immediately suitable for LoWPAN
DSR may not fit within a packet, AODV needs more memory, etc
Current service discovery methods “bulky” for LoWPAN
Primarily XML based that needs computing, more memory, etc
Limited configuration and management necessarySecurity for multi hop needs to be considered
62
Conclusion
IP-USNFuture Internet Infrastructure TechnologyIPv6 based Sensor Networks (IETF 6LoWPAN)It provides
Scalability, Reliability, Globally, Mobility
Related StandardizationIEEE 802.15.4ZigBee AllianceIEEE 802.15 Body Area Network Study GroupIETF 6LoWPAN WG
63
Thank you
Q & A