1 / 5

Mesh Routing Optimization for 6LoWPAN

IETF 6LoWPAN WG 65th, Dallas, Tx. Mesh Routing Optimization for 6LoWPAN. Ki-Hyung Kim (Ajou University) and S. Daniel Park (SAMSUNG Electronics). Mesh Routing underneath to IPv6 Layer. Application. Application. Application. Transport. Transport. Transport. IPv6. IPv6. IPv6.

glora
Download Presentation

Mesh Routing Optimization for 6LoWPAN

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. IETF 6LoWPAN WG 65th, Dallas, Tx Mesh Routing Optimization for 6LoWPAN Ki-Hyung Kim (Ajou University) and S. Daniel Park (SAMSUNG Electronics)

  2. Mesh Routing underneath to IPv6 Layer Application Application Application Transport Transport Transport IPv6 IPv6 IPv6 Adaptation Adaptation Adaptation 802.15.4 MAC 802.15.4 MAC 802.15.4 MAC PHY PHY PHY

  3. LoWPAN Optimizations • Sub-IP Routing • Allows efficient header compression, smaller route tables • Use EUI-64 or 16 bit addresses • Use prot_type field to indicate AODV control messages instead of UDP ports • Utilization of 6lowpan characteristics • Use the route cost by utilizing the LQI of the 6LoWPAN PHY • Allow multiple schemes such as hop counts, aggregated LQI values, and minimum LQI value along a route • Hello messages are not used, instead use 802.15.4 link layer mechanisms such as ACKs, beacon responses, overhearing packets, etc • Use broadcast in the route discovery

  4. LoWPAN Optimizations II • Minimize power consumption and complexity • Do not use the destination sequence number • Only destination Replies to RREQ by RREP • Do not use the local repair • Report back to the originator by RERR upon a link break • Do not maintain the precursorlist • Send RERR only to the originator of the data which caused the link break • Utilize Efficient RERR reporting • Reuse existing specs, such as AODV and DYMO, as much as possible

  5. Summary • Feedback is welcome.

More Related