Document

LoRaWAN® Specification v1.0.1

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

Contents of this Issue

Navigation

Page 19 of 90

LoRaWAN Specification ©2016 LoRa™ Alliance Page 20 of 91 The authors reserve the right to change specifications without notice. 4.3.1.6 Frame options (FOptsLen in FCtrl, FOpts) 1 The frame-options length field (FOptsLen) in FCtrl byte denotes the actual length of the 2 frame options field (FOpts) included in the frame. 3 FOpts transport MAC commands of a maximum length of 15 octets that are piggybacked 4 onto data frames; see Chapter 5 for a list of valid MAC commands. 5 If FOptsLen is 0, the FOpts field is absent. If FOptsLen is different from 0, i.e. if MAC 6 commands are present in the FOpts field, the port 0 cannot be used (FPort must be either 7 not present or different from 0). 8 MAC commands cannot be simultaneously present in the payload field and the frame 9 options field. Should this occur, the device shall ignore the frame. 10 4.3.2 Port field (FPort) 11 If the frame payload field is not empty, the port field must be present. If present, an FPort 12 value of 0 indicates that the FRMPayload contains MAC commands only; see Chapter 4.4 13 for a list of valid MAC commands. FPort values 1..223 (0x01..0xDF) are application- 14 specific. FPort value 224 is dedicated to LoRaWAN Mac layer test protocol. 15 Note : The purpose of Fport value 224 is to provide a dedicated Fport 16 to run Mac compliance test scenarios over-the-air on final versions of 17 devices, without having to rely on specific test versions of devices for 18 practical aspects. The test is not supposed to be simultaneous with live 19 operations, but the Mac layer implementation of the device shall be 20 exactly the one used for the normal application. The test protocol is 21 normally encrypted using the AppSKey. This ensures that the network 22 cannot enable the device's test mode without involving the device's 23 owner. If the test runs on a live network connected device, the way the 24 test application on the network side learns the AppSkey is outside of 25 the scope of the LoRaWAN specification. If the test runs using OTAA 26 on a dedicated test bench (not a live network), the way the Appkey is 27 communicated to the test bench, for secured JOIN process, is also 28 outside of the scope of the specification. 29 The test protocol, running at application layer, is defined outside of the 30 LoRaWAN spec, as it is an application layer protocol. 31 32 FPort values 225..255 (0xE1..0xFF) are reserved for future standardized application 33 extensions. 34 35 Size (bytes) 7..22 0..1 0..N MACPayload FHDR FPort FRMPayload N is the number of octets of the application payload. The valid range for N is region specific 36 and is defined in Section 7 37 N should be equal or smaller than: 38 N ≤ M - 1 - (length of FHDR in octets) 39 where M is the maximum MAC payload length. 40

Articles in this issue

view archives of Document - LoRaWAN® Specification v1.0.1