Document

LoRaWAN® Specification v1.0.1

Issue link: https://read.uberflip.com/i/1428386

Contents of this Issue

Navigation

Page 15 of 90

LoRaWAN Specification ©2016 LoRa™ Alliance Page 16 of 91 The authors reserve the right to change specifications without notice. The MAC header specifies the message type (MType) and according to which major version 1 (Major) of the frame format of the LoRaWAN layer specification the frame has been 2 encoded. 3 4.2.1 Message type (MType bit field) 4 The LoRaWAN distinguishes between six different MAC message types: join request, join 5 accept, unconfirmed data up/down, and confirmed data up/down. 6 MType Description 000 Join Request 001 Join Accept 010 Unconfirmed Data Up 011 Unconfirmed Data Down 100 Confirmed Data Up 101 Confirmed Data Down 110 RFU 111 Proprietary Table 1: MAC message types 7 4.2.1.1 Join-request and join-accept messages 8 The join-request and join-accept messages are used by the over-the-air activation procedure 9 described in Chapter 6.2. 10 4.2.1.2 Data messages 11 Data messages are used to transfer both MAC commands and application data, which can 12 be combined together in a single message. A confirmed-data message has to be 13 acknowledged by the receiver, whereas an unconfirmed-data message does not require 14 an acknowledgment. 1 Proprietary messages can be used to implement non-standard 15 message formats that are not interoperable with standard messages but must only be used 16 among devices that have a common understanding of the proprietary extensions. 17 Message integrity is ensured in different ways for different message types and is described 18 per message type below. 19 4.2.2 Major version of data message (Major bit field) 20 21 Major bits Description 00 LoRaWAN R1 01..11 RFU Table 2: Major list 22 Note: The Major version specifies the format of the messages 23 exchanged in the join procedure (see Chapter 6.2) and the first four 24 bytes of the MAC Payload as described in Chapter 4. For each major 25 version, end-devices may implement different minor versions of the 26 frame format. The minor version used by an end-device must be made 27 known to the network server beforehand using out of band messages 28 (e.g., as part of the device personalization information). 29 1 A detailed timing diagram of the acknowledge mechanism is given in Section 19.

Articles in this issue

view archives of Document - LoRaWAN® Specification v1.0.1