LoRaWAN OTAA joining narrated tour
LoRaWAN OTAA joining narrated tour
LoRaWAN OTAA joining narrated tour
Play silently with captions on provisional storyboard timing; narration audio is pending. Production pacing is not protocol time. Choose Reduced motion for a complete still at each beat.
Play the tour to open the workbench. Pause, replay a beat, or read the full transcript below. Some situations cannot be shown by this teaching model; those beats keep the existing frame and provide captions only.
Full transcript — LoRaWAN OTAA joining (8 beats)
B1 — Meter needs a session
You are the technician bringing a farm meter back after a power failure. Suppose the restart has lost its valid session state. The meter needs to send readings again, but normal traffic must wait for a new join request and an acceptance. What makes that join succeed?
Model caption: After a restart that loses valid session state, normal traffic waits for a new join.
B2 — Root and session keys
The method is called over the air activation. It creates session keys during joining: keys for normal traffic, with different roles for network validation and application encryption. A root key is the secret stored beforehand on the device and trusted server side. It supplies the starting material for joining.
Model caption: A provisioned root secret supplies joining; session keys serve normal network and application traffic.
B3 — Join request
The meter sends a join request containing identifiers, a device nonce, and a message integrity check. A device nonce is a value that must be fresh for that device. The integrity check lets the server check possession of the root key without sending the secret itself over the air.
Model caption: The request carries identifiers, a fresh device nonce, and an integrity check; the root secret is not sent.
B4 — Forward and validate
The gateway forwards the request. The server checks the device registry, the integrity check, and nonce freshness. For an accepted request, the network prepares an encrypted join acceptance carrying a device address and settings. Your meter then listens during receive windows, timed from the end of its transmission.
Model caption: Gateway forwarding precedes server validation; acceptance returns an address and settings in a receive window.
B5 — Second receive window
Take the teaching model's missed first window example. The first join receive window is five seconds after the request finishes transmitting. The second follows one second later. Start with five seconds, add one second, and the second window is at six seconds. The acceptance arrives in that second window.
Model caption: From transmission end: first window at five seconds; add one second; second window at six seconds receives the acceptance.
B6 — Session established
The join succeeds through the second receive window. The device and server derive matching session keys locally from root material and join nonces. The root secret stays out of the radio exchange. With the session established, the meter can send normal traffic using its assigned device address.
Model caption: The second window delivered the reply; matching session keys and the assigned address support normal traffic.
B7 — Reused nonce rejected
The misconception is that a gateway hearing the request means the meter has joined. Forwarding only gets the request to validation. In the reused nonce example, the server has already seen the device nonce. Even with a valid integrity check, freshness fails. The server rejects the join before session keys are derived, so hearing the request was insufficient.
Model caption: Heard and forwarded does not mean joined: a reused device nonce fails freshness even when the integrity check is valid.
B8 — Join takeaway
Joining turns a checked request and a timely reply into fresh session keys for normal traffic.
Model caption: Joining turns a checked request and a timely reply into fresh session keys for normal traffic.