Issue link: https://read.uberflip.com/i/1428395
LoRaWAN ® L2 1.0.4 Specification © 2020 LoRa Alliance ® Page 48 of 90 The authors reserve the right to change specifications without notice. receives the first downlink from the Network (while respecting duty cycles, if applicable, and 1548 retransmission timers). 1549 The Network Server SHALL NOT transmit a downlink before it has received a first uplink 1550 frame. 1551 6.3 Activation by Personalization 1552 Activation by personalization ties an end-device directly to a specific network, thus bypassing 1553 the Join-Request – Join-Accept procedure. 1554 Activating an end-device by personalization means that the DevAddr and the two session 1555 keys NwkSKey and AppSKey are stored directly in the end-device instead of being derived 1556 from DevEUI, JoinEUI and the AppKey. The end-device is equipped with the required 1557 information for participating in a specific LoRaWAN network as soon as it is started. 1558 Each end-device SHALL have a unique set of NwkSKey and AppSKey values. 1559 Compromising the keys of one end-device SHALL NOT compromise the security of the 1560 communications of other end-devices. The process to build those keys SHALL be such that 1561 the keys cannot be derived in any way from publicly available information such as the end- 1562 device address or DevEUI. 1563 Upon first boot and following a reset, personalized end-devices SHALL have all available 1564 channels for that region enabled and SHOULD use all required data rates for that region. 1565 Configurations of the end-device by the Network that controls downlink connectivity (controlled 1566 by RXParamsSetupReq, DlChannelReq, RXTimingSetupReq, and TXParamSetupReq) 1567 SHALL be persisted by the end-device, even after a reset. 1568 Frame counter values SHALL be used only once in all invocations of a same key with the 1569 CCM* (Counter with CBC Message Authentication Code) mode of operation [IEEE802154]. 1570 Therefore, re-initialization of an ABP end-device frame counters is forbidden. ABP end- 1571 devices SHALL store the frame counters persistently (e.g., in non-volatile memory). 1572 1573 Note: ABP end-devices use the same session keys throughout their 1574 lifetime (i.e., no rekeying is possible). Therefore, it is recommended that 1575 OTAA end-devices be used for higher security applications. 1576