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