1. Development of PMIPv6 based 6LoWPAN Sensor Node Mobility Scheme Jin Ho Kim, Rim Haw, Choong Seon Hong Kyung Hee University, KOREA 2010.02.25 AsiaFI School

2. Sensor with MANET Sensor Node (or Network) Mobility Sensor with NEMO Sensor with PMIPv6 Sensor with Mobile IPv6 2

3. Kyung Hee University3 PMIPv6 based 6LoWPAN sensor device mobility IPv6 Network Home Agent 6LoWPAN GW 6LoWPAN GW 6LoWPAN Node (FFD) 6LoWPAN Mobile Node 6LoWPAN Node (FFD) Intra-PAN Mobility Inter-PAN Mobility Router IPv6 Network Home Agent 6LoWPAN GW AAA 6LoWPAN GW 6LoWPAN Node (FFD) 6LoWPAN Mobile Node 6LoWPAN Node (FFD) Intra-PAN Mobility Inter-PAN Mobility Router  6LoWPAN : Low Power, Low Cost WPAN  It’s so hard to load of mobility protocol  In order to support mobility of sensors in 6LoWPAN environments, 6LoWPAN Gateway is applied to Proxy Mobile IPv6 - 6LoWPAN Gateway can distinguish between Intra-PAN Mobility and Inter-PAN Mobility  PAN attachment detection mechanism for 6LoWPAN sensor devices in multi-hop communication environments

4. Kyung Hee University4 A conventional PMIPv6 Protocol  Single-hop based mobility support protocol  cannot support in Multi-hop based 6LoWPAN environments 6LoWPAN Node Movement Notification Mechanism for multi-hop  6LoWPAN Node’s PAN Attachment Detection Mechanism  Using modified Neighbor Discovery protocol  It needs to consider for Multi-hop and Mobility environment  Proposed Router Solicitation and Router Advertisement Messages  The goal is to minimize signaling of 6LoWPAN node attachment  Neighbor Discovery  RS and RA messages are exchanged by adaptation layer routing 6LoWPAN GW1 6LoWPAN GW2 6LoWPAN Node (FFD) 6LoWPAN Node (FFD) Inter-PAN Mobility 6LoWPAN Mobile Node RA RS Attachment PAN Attachment Notification Mechanism

5. Kyung Hee University5 Proposed Scheme : Movement Detection & Association (b) Active Scan (c) Measurement for RSSI of beacon (d) Associated with the new PAN Intra-PAN Mobility Inter-PAN Mobility (a) 6LoWPAN sensor node mobility scenario PAN#1 (PAN ID : 0x0020) PAN#2 (PAN ID : 0x0030) FFD11 FFD12 FFD21 FFD22 FFD12 FFD21 FFD22 FFD12 FFD21 FFD22 Inter-PAN Mobility Send beacon request message (broadcast) Receive beacon messages with PAN ID from neighbor FFDs PAN#1 PAN#2

6. Kyung Hee University6 (a) Send the unicast RS message with MN_ID option (b) Exchanging AAA Request & AAA Reply (c) Exchanging Proxy Binding Update & Proxy Binding Acknowledgement, and establishment a bi-directional tunnel (d) Receive the unicast RA message with HNP and 16-bit address options AAA Request IPv6 Network AAA Reply Bi-directional Tunnel PBU Proposed RS Proposed RA PBA Proposed Scheme : Home Registration AAA HA

7. 7 HeaderFieldData IEEE 802.15.4 MAC header Source Address6LoWPAN Node’s 64-bit MAC address Destination AddressFFD1’s 16-bit MAC address 6LoWPAN Mesh header MD (Mesh Dispatch)Original address flag=64 bits, Final address flag=16 bits, Hop Left Original Address6LoWPAN Node’s 64-bit address Final Address6LoWPAN Gateway’s 16-bit address 6LoWPAN IP (addressing) header DSP (Dispatch)Compressed IPv6 HC1 (IPv6 Header Compression) Source prefix: compressed, Source IID: non-compressed Destination prefix: compressed, Destination IID: compressed Next Header=ICMP IPv6 header Source address  6LoWPAN Node’s link-local address (64 bits), Hop Limit (8 bits) Router Solicitation RS headerRouter Solicitation header RS optionMN_ID (6LoWPAN Node’s profile: 64 bits) option Router Solicitation  6LoWPAN MN’s PAN Attachment Notification  6LoWPAN MN’s 6LoWPAN Gateway Discovery  Destination address of RS is set to the 6LoWPAN Gateway (All of 6LoWPAN Gateway’s 16-bit address is 0x0001)  Unicast  Signaling messages can be reduced in PAN area since RS message is being sent in unicast directly, not broadcast.  MN_ID (6LoWPAN MN’s profile information) option is included in RS message.  With receiving the RS message, the 6LoWPAN Gateway can get 6LoWPAN MN’s MAC address, link-local address and MN_ID. Source Addr. (64) Dest. Addr.(16) MD Original Addr.(64) Final Addr.(16) HC1IPv6 RS header RS option IEEE 802.15.4 MAC header 6LoWPAN Mesh header 6LoWPAN IP (addressing) header DSP Router Solicitation RS Proposed Scheme : RS message

8. 8 HeaderFieldData IEEE 802.15.4 MAC header Source Address6LoWPAN Gateway’s 16-bit MAC address Destination AddressFFD2’s 16-bit MAC address 6LoWPAN Mesh header MD (Mesh Dispatch)Original address flag=16 bits, Final address flag=64 bits, Hop Left Original Address6LoWPAN Gateway’s 16-bit address Final Address6LoWPAN Node’s 64-bit address 6LoWPAN IP (addressing) header DSP (Dispatch)Compressed IPv6 HC1 (IPv6 Header Compression) Source prefix: compressed, Source IID: non-compressed, Destination prefix: compressed, Destination IID: non-compressed, Next Header=ICMP IPv6 header Source address  6LoWPAN Gateway’s link-local address (64 bits), Destination address  6LoWPAN Node’s link-local address (64 bits), Hop Limit (8 bits) Router Advertisement RA headerRouter Advertisement header RA option 6LoWPAN Node’s Home Prefix option (8 bytes), 6LoWPAN Node’s 16-bit address option (2 bytes) Source Addr.(16) Dest. Addr.(16) MD Original Addr.(16) Final Addr.(64) HC1IPv6 RA header RA options IEEE 802.15.4 MAC header 6LoWPAN Mesh header 6LoWPAN IP (addressing) header DSP Router Advertisement RA Router Advertisement  6LoWPAN MN’s Home Prefix and 16-bit address options are included.  The 6LoWPAN GW assigns a 16-bit address to the 6LoWPAN MN, and it has a list of all the 6LoWPAN nodes with 16- bit addresses.  Therefore, the 6LoWPAN GW discovery does not require the 16-bit address collision avoidance mechanism.  Destination address of RA is set to the 6LoWPAN MN (6LoWPAN GW can get the 6LoWPAN MN’s address from RS message)  Unicast Proposed Scheme : RA message

9. Kyung Hee University9 What we had done ● TinyOS 2.0 based 6LoWPAN protocol stack  Neighbor discovery for 6LoWPAN  Multi-hop routing protocol for 6LoWPAN  Communication test and demo between 6LoWPAN sensor node and IPv6 main server ● A daemon for supporting 6LoWPAN node mobility based on PMIPv6  Proxy Mobile IPv6 protocol stack  6LoWPAN sensor node's PAN attachment detection mechanism  The health condition monitoring application

10. PMIPv6 based 6LoWPAN sensor node mobility Testbed 6LoWPAN sensor network Testbed Router & AAA Server LMA (Home Agent) IPv6 Network MAG1 (6LoWPAN GW1) MAG2 (6LoWPAN GW2) 6LoWPAN 1 6LoWPAN 2 Main Server 6LoWPAN Sensor Node 10 Testbed ① ② ① Pulse & Oximeter Board ② Sensor Interface (Saturation of partial pressure oxyzen :SpO2)

11. Kyung Hee University11 6LoWPAN GW’s PMIPv6 packet capture and Routing Table  Proxy Binding Update Implementation

12. 12 Base Station 3ffe:qwe:ert:fdg/64 0x0001 Sensor Node 0x0003 Sensor Node 0x0005 RREQ RREP Mobile Node 3ffe:1:3::20:ff:fe00:9/64 0x0009 IPv6 Network DATA packet Main Server 3ffe:aaaa:bbbb:cccc:dddd/64 Base Station 3ffe:qwe:ert:fdg/64 0x0001 Sensor Node 0x0012 Sensor Node 0x0014 Mobile Node 3ffe:1:3::20:ff:fe00:9/64 0x0009 Data Request delivery (Main Server -> BS -> 0x0003 -> 0x0005 -> MN) 6LoWPAN packet capture  Data Request/Data Reply between Main Server and Mobile Node Implementation

13. Experimental Results Kyung Hee University13 Handover (PAN#2  PAN#1) Handover (PAN#1  PAN#2) Handover (PAN#2  PAN#1) Handover (PAN#1  PAN#2) Sending interval is 500ms and Payload size is 10 bytes The total handover delays of the first test from the 6LoWPAN network#1 to 6LoWPAN network#2 and from the 6LoWPAN network#2 to 6LoWPAN network#1 are 1.357s and 1.208s, respectively. The total handover latency with ICMPv6 echo/reply packet using ping6 command between the 6LoWPAN sensor node and its CN Sending interval is 500ms and Payload size is 1000 bytes The total handover delays of the second test from the 6LoWPAN network#1 to 6LoWPAN network#2 and from the 6LoWPAN network#2 to 6LoWPAN network#1 are 2.874s and 2.593s, respectively.

14. ● We focused on the scheme which supports mobility for 6LoWPAN sensor nodes. ● We adopt PMIPv6 protocol to provide mobility for low power 6LoWPAN sensor nodes. ● The attachment of 6LoWPAN sensor nodes can minimize signaling costs by using RS and RA messages. ● We also implemented the development environment for our proposed interworking mechanism between 6LoWPAN and PMIPv6 to apply in the healthcare system. ● We can verify that the 6LoWPAN sensor node can maintain the connectivity even though it has the freedom of moving between PANs without mobility protocol stack. Conclusion 14

15. Thank you Q & A