A data message can carry both MAC commands and application data simultaneously in separate fields. Sending MAC Commands and Application-Specific Data #Ī data message can contain any sequence of MAC commands.
The maximum length of the MAC Payload field is region and data rate-specific and can be found in the Regional Parameters chapter. The frame header (FHDR) of the MAC payload consists of the following fields. MAC payload of the data messages consists of a frame header (FHDR) followed by an optional port field (FPort) and an optional frame payload (FRMPayload). Confirmed data messages must be acknowledged by the receiver whereas unconfirmed data messages do not need to be acknowledged by the receiver.Ī data message is constructed as shown below: Data messages can be confirmed or unconfirmed. These data message types are used to transport both MAC commands and application data which can be combined together in a single message. There are 4 data message types used in both LoRaWAN 1.0.x and 1.1. For the Rejoin-request message, the network replies with a Join-accept message. These message types are used to initialize the new session context for the end device. There are three types of Rejoin-request messages: Type 0, 1, and 2. The Rejoin-request message is always initiated by an end device and sent to the Network Server.
Then the Network Server routes the Join-accept message to the correct end-device. In both cases the message passes through the Network Server. In LoRaWAN 1.1 and 1.0.4+ the Join-accept message is generated by the Join Server. In LoRaWAN versions earlier than 1.0.4 the Join-accept message is generated by the Application Server. The Join-request message is not encrypted. In LoRaWAN 1.1 and 1.0.4+, the Network Server forwards the Join-request message to the device’s Join Server. In LoRaWAN versions earlier than 1.0.4 the Join-request message is forwarded by the Network Server to the Application Server. The Join-request message is always initiated by an end device and sent to the Network Server. In LoRaWAN 1.1, three MAC message types are used by the Over-The-Air-Activation (OTAA) procedure and for roaming purposes: In LoRaWAN 1.0.x, two MAC message types are used by the Over-The-Air-Activation (OTAA) procedure: Join-request, Rejoin-request, and Join-accept messages # Used to implement non-standard message formats LoRaWAN 1.0.xĪn uplink message, used by the over-the-air activation (OTAA) procedureĪ downlink message, used by the over-the-air activation (OTAA) procedureĪn uplink data frame, confirmation is not requiredĪ downlink data frame, confirmation is not requiredĪn uplink data frame, confirmation is requestedĪ downlink data frame, confirmation is requestedġ.1 - Uplink over-the-air activation (OTAA) Rejoin-request The following table presents MAC message types that can be found in LoRaWAN 1.0.x and 1.1. LoRaWAN defines several MAC message types. This includes some messages initiated by the Application Server and the Join Server too. If the uplink message belongs to the Application Server or the Join Server, the Network server forwards it to the correct receiver.ĭownlink messages - Each downlink message is sent by the Network Server to only one end device and is relayed by a single gateway. Uplink messages - Uplink messages are sent by end devices to the Network Server relayed by one or many gateways. LoRa messages can be divided into uplink and downlink messages based on the direction they travel.