Wi-Fi & 802.11 · Study deck

802.15.4 Specifications and Roles

Picture a warehouse tag that sends one short shelf update through a busy band.

Radio Remi is your guide for this deck.

ieee-802-15-4specificationscsma-ca

Radio Remi, the module guide, in a scene from this chapter.

After studying this chapter

Learning objectives

You will be able to:

identify the 802.15.4 PHY and MAC features that affect design review
explain why nominal data rate is not the same as usable application throughput
review how frame fields and security overhead reduce payload space
distinguish non-beacon CSMA/CA from beacon-enabled scheduling and GTS

Major section

Start With the Wireless Story

A product sheet lists range, rate, and low power, but the planner still has to fit an address, security data, and the reading into one small frame.

Nearby office traffic may also delay the send.
A supported feature is not proof of a working site.
This opening does not pick a stack or promise a fixed range.

Major section

Start With the Wireless Story (continued)

A low-power link can report and coordinate, but loss and delay still need a known local response.

Under the Hood examines timing, channel access, device roles, security cost, and the exact limits behind each choice.
If any answer is no, test again.
Specification choices become deployment limits.

Major section

In 60 Seconds · Phoebe's Field Notes: Why the Same Chair Blocks 2.4 GHz But Not 915 MHz

IEEE 802.15.4 is a low-rate wireless PHY/MAC standard.

The most important review skill is knowing which feature belongs to the standard, which feature belongs to an upper-layer stack, and which deployment claim still needs measurement.

Major section

Specification Review Map · What 802.15.4 Specifies

This separates what the standard permits from what the chosen hardware and deployment prove.

A design can be wrong even when a single data-rate, frequency, or channel number is correct.

IEEE 802.15.4 feature and specification review map.

Major section

PHY Features To Review · MAC Features To Review

The common 2.4 GHz PHY uses channels 11 through 26, spaced 5 MHz apart from 2405 MHz to 2480 MHz, with a nominal 250 kbps rate.

Regional sub-GHz PHY options also exist, and their allowed channels and rates depend on region, amendment, and local regulation.
Those choices are not interchangeable: path loss, antenna size, interference, channel availability, and local duty-cycle rules all change with frequency.
Other PHY options use different modulation.

Major section

Frame Budget · Beacon Mode And GTS

The 802.15.4 frame is small enough that every field matters.

A payload estimate should count the MAC header, addressing fields, footer, security fields, and any upper-layer adaptation headers before claiming application capacity.
Beacon-enabled operation can organize time into a superframe.
The contention access period supports CSMA/CA traffic.

IEEE 802.15.4 PHY comparison, amendment lineage, and beacon-enabled versus non-beacon timing panels.

Major section

Coexistence Review · Worked Review Examples

2.4 GHz 802.15.4 networks often share space with Wi-Fi and other radios.

A good channel plan starts with observation, not a universal "always use channel X" rule.
The route keeps spectrum observations, device capabilities, and service outcomes connected.
A classroom prototype has a few sensors sending short messages every minute.

Major section

Two Device Types and One Coordinator

802.15.4 defines two device classes.

A reduced-function device (RFD) is deliberately simpler.
It talks only to an FFD, does not become a coordinator, and is normally used as a low-power leaf node whose radio can sleep for long periods.
The role choice also affects failure analysis.

Role review starts by separating the local 802.15.4 network boundary from the upper-layer gateway boundary, then assigning coordinator, forwarding, and sleepy-leaf responsibilities to devices that can support them.

Major section

Two Device Types and One Coordinator (continued)

The map therefore connects RFD and FFD capability to actual deployment duties while keeping upper-layer routing and gateway services outside the PHY/MAC claim.

That device is an FFD, starts the PAN, chooses or owns the 16-bit PAN identifier, and manages association for devices that join.
Worked topology example: A room has 30 battery door sensors and 3 powered relay nodes.
If every node were treated as an FFD with receiver-on behavior, the design would waste energy on devices that never need to coordinate traffic.
Confusing FFD/RFD with Zigbee coordinator/router/end-device names makes this easy to miss.

Major section

Two Device Types and One Coordinator (continued)

A cleaner mapping makes the door sensors RFD leaves and the powered relays FFD-capable infrastructure.

The PAN coordinator can assign short addresses and manage the network, while the upper-layer stack decides whether powered relays also route application traffic.
The specification review should write down which role is 802.15.4 and which role belongs to the upper layer.
If a door sensor is an RFD, it cannot be blamed for failing to relay a neighbour's packet; that was never its job.
A battery sensor is usually an RFD; a powered relay or PAN coordinator must use FFD capability.

Major section

Addressing, Frame Types, and the Header Budget · The Frame Control Field and Indirect Transmission

The practical review habit is to ask for a frame budget table, not a sentence.

802.15.4 nodes carry two addresses.
The 64-bit extended address is a globally unique IEEE EUI-64 associated with the radio.
Two FCF ideas reveal how sleepy RFDs are supported.

Deck summary

Key takeaways

A product sheet lists range, rate, and low power, but the planner still has to fit an address, security data, and the reading into one small frame.

A low-power link can report and coordinate, but loss and delay still need a known local response.
IEEE 802.15.4 is a low-rate wireless PHY/MAC standard.
This separates what the standard permits from what the chosen hardware and deployment prove.
The common 2.4 GHz PHY uses channels 11 through 26, spaced 5 MHz apart from 2405 MHz to 2480 MHz, with a nominal 250 kbps rate.

Retrieval practice

Recall check 1 of 5

Radio Remi says: answer from memory, then check your reasoning.

Q1A team cites the 250 kbps PHY rate to justify adding a new sensor group to a 2.4 GHz 802.15.4 network. What evidence is still needed?

AUse headline range as a frame-budget proof.

BUse 2.4 GHz support as an airtime proof.

CThe review needs frame budget, timing, retries and losses.

DOnly that the coordinator device powers on cleanly

Show answer

Answer: C A nominal PHY data rate needs frame-budget, timing, retry/loss, and coexistence evidence before a new sensor group is accepted.

Retrieval practice

Recall check 2 of 5

Radio Remi says: answer from memory, then check your reasoning.

Q2A sensor message fits the raw frame size. What else must the payload review include?

ACount payload bytes but omit MAC and security overhead.

BCheck radio channel name as a payload budget.

CCount gateways as a substitute for frame overhead.

DThe review counts MAC, addresses, security and adaptation.

Show answer

Answer: D These fields consume space before application data.

Q3A device needs a planned transmit opportunity. Which access pattern fits that need?

AA larger payload without a slot assignment

BA channel label with no coordinator plan

CBeacon schedule with guaranteed slot

DUnslotted contention with no schedule

Show answer

Answer: C A scheduled slot can bound the opportunity for that device.

Retrieval practice

Recall check 3 of 5

Radio Remi says: answer from memory, then check your reasoning.

Q4What best distinguishes a reduced-function device (RFD) from a full-function device (FFD) in 802.15.4?

ARFD is a leaf for one FFD; FFD can coordinate and use full MAC capability.

BRFD always uses more transmit power; FFD always uses less power.

CRFD uses a different 5 GHz PHY; FFD uses only 2.4 GHz channels.

DRFD must become PAN coordinator; FFD must remain a leaf node.

Show answer

Answer: A RFDs are minimal leaf nodes; FFDs carry the full MAC capability set and can act as coordinators.

Retrieval practice

Recall check 4 of 5

Radio Remi says: answer from memory, then check your reasoning.

Q5Why do 802.15.4 nodes switch from their 64-bit extended address to a 16-bit short address after joining a PAN?

AShort MAC addresses save about 6 bytes per address field.

BThe 64-bit address stops working once a node joins a PAN.

CShort addresses are globally unique, unlike the 64-bit address.

DShort addresses double data rate after PAN association.

Show answer

Answer: A Two 64-bit addresses cost 12 more header bytes than two 16-bit ones; short addressing recovers payload.

Retrieval practice

Recall check 5 of 5

Radio Remi says: answer from memory, then check your reasoning.

Q6How does a coordinator deliver data to a sleepy RFD that keeps its radio off most of the time?

AIt transmits continuously until the RFD happens to be awake.

BThe coordinator buffers data and flags it when the RFD polls.

CKeep the RFD radio on to wait for coordinator commands.

DIt broadcasts the command on every channel simultaneously.

Show answer

Answer: B The RFD sends a data-request when awake, then receives the queued frame through indirect transmission.

Print reference

Answers 1 of 2

Answer key.

C · A nominal PHY data rate needs frame-budget, timing, retry/loss, and coexistence evidence before a new sensor group is accepted.
D · These fields consume space before application data.
C · A scheduled slot can bound the opportunity for that device.
A · RFDs are minimal leaf nodes; FFDs carry the full MAC capability set and can act as coordinators.
A · Two 64-bit addresses cost 12 more header bytes than two 16-bit ones; short addressing recovers payload.

Print reference

Answers 2 of 2

Answer key.

B · The RFD sends a data-request when awake, then receives the queued frame through indirect transmission.