6LoWPAN Protocol

Definition and Background

6LoWPAN (IPv6 over Low-Power Wireless Personal Area Networks) is an adaptation layer protocol defined by IETF that enables IPv6 to run over low-power wireless links such as IEEE 802.15.4 (e.g., Zigbee, Thread) . The MTU of 802.15.4 is only 127 bytes, while the IPv6 packet header is at least 40 bytes; with additional overhead from UDP/TCP, it cannot be directly transmitted. 6LoWPAN addresses the adaptation issue between IPv6 and low-power wireless networks through header compression, fragmentation and reassembly, and address simplification.

Core Mechanism

Complementary to Cellular IoT

6LoWPAN is aimed at non-cellular, low-power, short-range, or medium-range local area network scenarios; NB-IoT , LoRa and others are aimed at wide-area, carrier networks. In smart homes, buildings, and other scenarios, 6LoWPAN + Zigbee/Thread can form a local area network, which is then aggregated to a cellular network or cloud platform through a gateway, achieving 'end-edge-cloud' collaboration.

Typical Applications

Trade-off between context identifiers and short-address compression

6LoWPAN does not rewrite IPv6. It inserts an adaptation layer between the 802.15.4 frame and IPv6. A physical-layer frame is only 127 bytes. After frame control, addresses, and the link-layer security header, the space left for the network layer is often only a few dozen bytes. Compression first asks whether the source and destination can be replaced by a link-local prefix or a context identifier. The border router distributes contexts, and a short identifier stands for a shared prefix. If a node compresses with an expired identifier, the peer reconstructs an address on the wrong subnet. Neighbors can still talk to each other, and traffic stops having a route as soon as it crosses the gateway.

Short-address compression is valid only inside the personal-area network. When a packet leaves the local mesh, the border router must restore the full IPv6 address before forwarding. If the application has already put in a long text payload, header compression cannot save the frame. The packet should be fragmented, or the payload should be rewritten in a tighter binary form. Turning on link-layer encryption adds an auxiliary security header. The packed length must be recalculated on the encrypted frame, not copied from the cleartext rule of thumb.

How fragment-reassembly timeouts drain low-power nodes

A datagram that exceeds one frame is cut into pieces, each carrying a fragment header. The receiver reassembles them by datagram tag and offset. A low-power node has a very small reassembly buffer. If a tag collides with a neighbor, a later fragment pushes out a half-built datagram. If the sender spaces fragments too far apart, the receiver does not get the last piece before the timeout, drops the whole datagram, and the application sees only an occasional timeout. Most of the packet has already crossed the air. While troubleshooting, check that sequence numbers are contiguous and that the reassembly timer is shorter than the period of route jitter.

On a multi-hop path every hop may retransmit fragments, and the pieces of one datagram arrive more out of order as the hop count grows. The reassembly end can tolerate disorder, but it cannot buffer without limit. If a battery node is assigned as a relay, a fragment storm wakes it out of sleep again and again. Leaves should send only readings that fit in a single frame. Large payloads should be aggregated on the border-router side and then sent uplink.

Field signs that the border router has lost sync

The border router distributes contexts, proxies neighbor discovery, and forwards datagrams after reassembly. When it falls out of sync, three signs usually stack up. Nodes can reach each other by short address, but there is no next hop past the gateway. The cloud sees the gateway online, yet the sensor addresses do not match. After encryption is enabled, only some nodes can join. Check whether the context version is the same, whether the leaf next hop is still in the network, and whether the gateway uplink is merely “link up” while the adaptation layer has not synchronized. When backhaul is cellular, the IoT SIM card is only the wide-area exit. It does not replace compression and fragmentation in the adaptation layer.

In this hybrid architecture SimtoLink provides cellular backhaul and module access on the gateway side, not a 6LoWPAN stack for every sensor. Size the local frame length, encryption overhead, and gateway report period separately. Do not copy a sensor sleep setting onto a communication module. To compare which wide-area air interface the gateway should use after aggregation, Wi-Fi IoT in the same knowledge base is a different kind of local exit. Do not fold it into the 6LoWPAN adaptation parameters.

A leaf should finish reassembly before it goes back to sleep

The adaptation-layer reassembly buffer and node sleep have to sit on the same timeline. If a leaf turns the radio off before the last fragment arrives, the datagram tag may already have been taken by a neighbor when it wakes, the half-built packet is overwritten, and the application simply sends the whole datagram again. If the gateway aggregation period is shorter than the slowest sensor wake period, the cloud sees a run of empty windows and records “still asleep” as “already off the network.” Leaves should send only readings that fit in one frame, and the gateway should pack many nodes into one uplink on its own schedule. That keeps both the battery and the sequence numbers intact.

Each node needs its own sequence number and sample time in the packed payload, so the aggregated message can show which node did not refresh. If the sequence number stops while the gateway stays online, the fault is in the local mesh. If the sequence number keeps moving and the cellular uplink stops, the fault is at the gateway exit. Online time of a SimtoLink module should be read against the gateway aggregation period. Do not require the module to stay awake for the sensor sleep interval. If the two clocks differ by one reporting round, offline alarms show up in pairs on the platform. Align the clocks before judging the link.

---

Related Links

Return to the communications knowledge base