6LoWPAN: IPv6 over Low-Power Wireless PAN Adaptation Layer

What is 6LoWPAN? (In Simple Words)

6LoWPAN stands for IPv6 over Low-Power Wireless Personal Area Networks.

To understand why 6LoWPAN is needed, look at this common IoT problem:

• We want all smart sensors to connect to the Internet using IPv6 because IPv6 provides unlimited IP addresses.
• At the same time, battery-powered sensors use the low-power wireless standard IEEE 802.15.4 because it uses very little battery.

Now comes the big engineering problem:

• A standard IPv6 packet requires a minimum size of 1,280 bytes!
• But an IEEE 802.15.4 wireless frame can hold a maximum of only 127 bytes!
• To make matters worse, normal IPv6 headers (40 bytes) and UDP headers (8 bytes) take up 48 bytes by themselves. In a tiny 127-byte frame, almost no space is left for actual sensor readings!

6LoWPAN is a specialized Adaptation Layer (Layer 2.5) placed between IPv6 and the IEEE 802.15.4 radio layer to solve this size mismatch.

1. Core Functions of the 6LoWPAN Adaptation Layer

To fit large IPv6 packets into tiny 127-byte radio frames, 6LoWPAN performs three core functions:

A. Header Compression (How it Shrinks Headers):

How does 6LoWPAN compress a 48-byte header into just 2 to 4 bytes?

• Removes Predictable Data: Many fields in a local sensor network never change (for example, the IP version is always 6, and traffic priority is 0). 6LoWPAN removes these repetitive fields completely.
• Uses MAC Addresses: The sender and receiver IP addresses are automatically calculated from the hardware MAC addresses of the radios.
• By replacing repeated fields with simple 1-bit flags, the bulky 48-byte header shrinks down to only 2 to 4 bytes, leaving plenty of room for real sensor data!

B. Fragmentation and Reassembly:

If an incoming message (such as a remote software update) is larger than 127 bytes:

1. 6LoWPAN chops the big packet into smaller fragments.
2. The First Fragment (FRAG1) has a small 4-byte header specifying the total size and a packet ID tag.
3. The Remaining Fragments (FRAGN) include an offset tag to show their position in the sequence.
4. When all pieces reach the receiving node, 6LoWPAN reassembles them back into the original 1,280-byte IPv6 packet before passing it to the application!

C. Mesh Under vs. Route Over:

• Mesh Under: Routing happens at the adaptation layer (Layer 2.5) using hardware MAC addresses. To the outside Internet, the entire sensor network looks like one single local link.
• Route Over: Every sensor node acts like a mini IP router at Layer 3, using the standard RPL (Routing Protocol for Low-Power and Lossy Networks) protocol.

2. Advantages of 6LoWPAN

1. Direct Internet Connection: Sensor nodes talk genuine IPv6. A server in Delhi can directly ping an individual sensor in an Indore warehouse without needing an expensive translation gateway!
2. Open Standard: Standardized by the IETF, which means products from different manufacturers work together seamlessly.
3. Low Memory Footprint: Very lightweight software that easily runs on tiny microcontrollers with only 32 KB of code memory and 4 KB of RAM.

💡 DAVV Exam Preparation Tips

5-Mark Question: “What is 6LoWPAN? Explain the packet size mismatch problem between IPv6 and IEEE 802.15.4.”

• Full Form: IPv6 over Low-Power Wireless Personal Area Networks.
• Packet Size Mismatch: IPv6 requires packets of at least 1,280 bytes, while IEEE 802.15.4 frames are capped at only 127 bytes.
• Solution: 6LoWPAN sits as an adaptation layer (Layer 2.5) to perform Header Compression and Packet Fragmentation.

10-Mark Question: “Explain the architecture and working of the 6LoWPAN adaptation layer. Detail Header Compression, Fragmentation & Reassembly, and Mesh Routing with suitable diagrams.”

• Draw the protocol stack diagram showing 6LoWPAN between IPv6 and IEEE 802.15.4.
• Explain Header Compression: 48 bytes of IPv6+UDP headers compressed down to 2 to 4 bytes.
• Explain Fragmentation: How large packets are split using FRAG1 and FRAGN headers, then reassembled.
• Contrast Mesh-Under (Layer 2.5 MAC routing) vs. Route-Over (Layer 3 IP routing).