IoT Chapter 3 - IoT Internetworking - IEEE 802.15.4 - Part B

Main ideas / concepts conveyed

• 802.15.4 MAC layer is organized into two service groups

  • MAC management services (control/coordination tasks)
    • Beacon management
    • Handling general access frames
    • Validation/delivery of frames
    • Association / dissociation (adding/removing devices)
    • Security integration hooks (points where security mechanisms plug in)
  • MAC data services (actual message transport)
    • Message transmission service
    • Message reception service
    • MAC data services use the physical layer’s data service (MAC packets are handed down to PHY)

• Security is not “fixed” by the standard

  • 802.15.4 does not mandate a specific security algorithm/mechanism
  • Instead it provides hooks to “plug in” security
  • Reason given: security mechanisms often become insecure over time; if a specific mechanism were standardized, updates would require breaking compatibility or waiting for new standards—both undesirable. So the standard keeps insertion points and allows evolution via recommendations.

• MAC frame structure (what is actually sent)

  • The MAC data unit is the MPDU (MAC Protocol Data Unit)
  • MPDU has three parts:
    • MAC header (management info)
    • Payload (data unit)
    • Footer containing CRC (error detection)
  • MAC header components:
    • Frame Control: indicates frame type (e.g., data, acknowledgment, beacon)
    • Sequence number: increments per new message; helps detect duplicates on retransmission (1 byte, wraps eventually)
    • Address information: optional depending on frame type; can vary in size up to 20 bytes

• How MAC hands data to PHY and max payload sizes

  • MPDU is passed to PHY as the PHY payload
  • Mentioned PHY limits:
    • PHY has a 6-byte header
    • Up to 127-byte PHY payload
  • Implied MAC-to-PHY payload capacity:
    • MAC-visible maximum data after subtracting PHY footer: ~125 bytes for MPDU payload portion (with further overhead reducing usable MAC payload)

• Addressing in 802.15.4

  • Up to 20 bytes of address information are available in the MAC header.

  • Two addressing modes:

    • 16-bit addresses
      • Assigned per small network by an operator
      • Not globally unique (can be reused across different networks)
      • Pros: short
      • Cons: requires assignment/uniqueness management; changes when joining a different network
      • Can be disabled depending on hardware/driver
    • 64-bit addresses
      • Manufacturer-provided, globally unique
      • Pros: no need for network-wide assignment
      • Cons: longer (more overhead); sometimes driver may allow changing them
      • Format is aligned with IPv6-style device identifier (mentioned as “same as device part”)

  • Why 20 bytes? (explicit calculation)

    • For normal peer communication, the header may include:
      • Sender 64-bit address = 8 bytes
      • Receiver 64-bit address = 8 bytes
      • plus PAN ID (2 bytes) to identify the personal area network
        • Total per device: 8 bytes (EUI-64) + 2 bytes (PAN ID) = 10 bytes
        • Both sender + receiver: 10 + 10 = 20 bytes

• MAC operation modes (CSMA/CA-based)

  • 802.15.4 has multiple MAC “versions” / modes; conceptually:
    • Beacon-enabled: slotted CSMA/CA
      • Uses beacons and superframe structure
      • Supports clock synchronization, lower latency options, and guaranteed time slots
    • Non-beacon / unslotted: unslotted CSMA/CA
      • Simpler contention without beacon timing and slotting

• Core CSMA/CA idea (how devices avoid collisions)

  • When a device wants to transmit:
    • Wait a random backoff time
    • Perform carrier sense (CCA) to check if the channel is busy/idle
    • If busy: wait again (with backoff increasing)
    • If idle: transmit
  • Two major reasons not to “sense continuously”:
    • Acknowledgment timing conflicts (receiver may send ACK right when sender starts)
    • Multiple senders starting simultaneously (collisions)
  • Also: continuous sensing wastes energy; sleep/wakeup saves battery.

---

Methodologies / instruction-like processes (detailed bullets)

A) CSMA/CA transmission process (general idea)

• Before sending
  • Choose a random wait/backoff time
• Then
  • Perform carrier sense (CCA)
    • If channel is busy:
      • Increase backoff window and try again (repeat sensing after waiting)
    • If channel is idle:
      • Transmit
• Retransmissions
  • If acknowledgment is not received in time:
    • Treat retransmission as a new transmission attempt
    • Compete again per CSMA/CA rules
    • Limit number of retransmissions (configurable)

B) Slotted CSMA/CA (beacon-enabled networks)

• Superframe context
  • Superframe starts at each beacon from the PAN coordinator
• Transmission timing constraint
  • Transmission can occur only at the beginning of a slot
• Backoff procedure uses parameters
  • BE (backoff exponent)
    • Starts at minimum
    • After each busy CCA, BE increases by 1 (capped at max)
  • CW (contention window / retries counter)
    • Initialized to CW0
    • Decremented after each successful idle check
  • NB (number of backoff attempts / retries level)
    • Tracks how many times waiting has occurred
    • If NB exceeds max trials → transmission attempt fails
• When CCA indicates idle
  • Decrement CW
  • If CW reaches 0 → start sending
  • Otherwise:
    • Wait for next slot and repeat CCA + decrement logic
• Goal
  • Be configurable: more aggressive (smaller initial CW/BE) vs more conservative.

C) Unslotted CSMA/CA (non-beacon networks)

• Differences from slotted
  • No guaranteed slots and no requirement to wait for slot boundaries
• Procedure
  • For each attempt:
    • Pick a random backoff within an interval based on current backoff settings
    • Perform channel idle check (CCA)
      • If idle: transmit immediately
      • If busy: increase backoff interval and repeat
    • Stop after reaching a maximum number of trials; then fail or restart attempt for a new frame

D) Superframe structure (beacon-enabled mode)

• Superframe begins with a beacon sent by the PAN coordinator and ends at the next beacon.
• Beacon provides:
  • PAN ID
  • Superframe configuration (structure parameters)
  • Clock synchronization for devices
• Superframe is divided into:
  • Active period
    • Contention access period: uses slotted CSMA/CA
    • Contention-free period
      • Contains guaranteed time slots
      • Devices must reserve slots in advance from the PAN coordinator
  • Inactive period (optional)
    • Devices (including coordinator) may sleep to save energy

E) Guaranteed time slots usage (real-time behavior)

• Device requests/reserves a guaranteed time slot from the PAN coordinator
• In each superframe:
  • If it reserved slot(s):
    • Device can transmit and receive ACK within the reserved slot
    • Other devices are prevented from transmitting in that slot

F) Acknowledgment (ACK) mechanism process

• Sender may request ACK via a bit/field in the MAC header.

• If ACK requested

  • Receiver sends ACK after successful reception
  • Retransmission strategy:
    • If ACK not received within timeout: resend up to max retransmissions
    • Each resend is treated as a new contention attempt (no special priority)

• ACK restrictions stated

  • No ACK is expected for:
    • Beacons
    • ACK requests for an ACK (cannot acknowledge the acknowledgment)

G) Time-Slotted Channel Hopping (TSCH) MAC (802.15.4e / 2015 revision)

• Motivated by:
  • Dense networks
  • High reliability requirements
  • Strong timing constraints
  • Need to avoid uncertainty of “may not get the channel / collision”
• Key changes described:
  • Removes superframes
  • De-emphasizes/removes most CSMA/CA contention behavior
  • Uses a mix of:
    • TDMA (time division multiple access)
    • FDMA (frequency division multiplexing)
    • Frequency channel hopping
• Slotframe concepts:
  • Communication is organized into slot frames (time slots)
  • Each communication between specific nodes uses a predefined channel-hopping sequence
  • Dedicated cells
    • Reserved for a specific link (e.g., node A ↔ node B)
  • Shared cells
    • Multiple devices can attempt transmissions
    • Shared cells still use contention via CSMA/CA
• ACK behavior in TSCH:
  • Sender data transmission and receiver ACK occur within the same slot (if no errors)
• Schedule management:
  • PAN coordinator assigns/coordinates the hopping schedules
  • The standard does not fully specify the schedule-finding algorithm; higher layers/protocol work may define it.

---

“Why it matters / comparison” conclusions

• 802.15.4 is characterized as:
  • Low cost
  • Low energy usage (claimed at least an order of magnitude better than Wi‑Fi)
• Earlier MAC modes had issues for:
  • Timing guarantees
  • Reliability and channel access fairness (possible starvation/unpredictable access)
• 802.15.4 (2015 revisions, especially 802.15.4e) improves by offering specialized MAC modes (e.g., TSCH) for reliability and latency.
• Trade-off vs Wi‑Fi:
  • Wi‑Fi solved many fairness/reliability mechanisms, but 802.15.4 tends to “minimize complexity” for constrained devices.
• Common competitor mentioned:
  • Bluetooth Low Energy
• Marketing/naming change:
  • “personal area networking” part removed in later revision because newer PHY layers increase range.

---

Speakers / sources featured

• No identifiable named speakers are present in the subtitles.
• Primary source: IEEE 802.15.4 / 802.15.4e / IEEE 802.15.4 (2015 revision) standard concepts referenced by the instructor narrating the video.