LoRaWAN 1.

1 Regional Parameters

829 2.6 AU915-928MHz ISM Band

830
831 This section defines the regional parameters for Australia and all other countries whose ISM
832 band extends from 915 to 928MHz spectrum.
833

834 2.6.1 AU915-928 Preamble Format

835 The following synchronization words SHOULD be used:
836
Modulation Sync word Preamble length
LORA 0x34 8 symbols
837 LoRaWAN does not make use of GFSK modulation in the AU915-928 ISM band.

838 2.6.2 AU915-928 Channel Frequencies

839 The AU ISM Band SHALL be divided into the following channel plans.
840  Upstream – 64 channels numbered 0 to 63 utilizing LoRa 125 kHz BW varying from
841 DR0 to DR5, using coding rate 4/5, starting at 915.2 MHz and incrementing linearly
842 by 200 kHz to 927.8 MHz
843  Upstream – 8 channels numbered 64 to 71 utilizing LoRa 500 kHz BW at DR6
844 starting at 915.9 MHz and incrementing linearly by 1.6 MHz to 927.1 MHz
845  Downstream – 8 channels numbered 0 to 7 utilizing LoRa 500 kHz BW at DR8 to
846 DR13) starting at 923.3 MHz and incrementing linearly by 600 kHz to 927.5 MHz
847

848
849 Figure 2: AU915-928 channel frequencies

850 AU ISM band end-devices may use a maximum EIRP of +30 dBm.
851 AU915-928 end-devices SHALL be capable of operating in the 915 to 928 MHz frequency
852 band and SHALL feature a channel data structure to store the parameters of 72 channels. A
853 channel data structure corresponds to a frequency and a set of data rates usable on this
854 frequency.
855 If using the over-the-air activation procedure, the end-device SHALL broadcast the JoinReq
856 message alternatively on a random 125 kHz channel amongst the 64 channels defined using
857 DR2 and a random 500 kHz channel amongst the 8 channels defined using DR6. The end-
858 device SHOULD change channel for every transmission.
859 Personalized devices SHALL have all 72 channels enabled following a reset.
860
861 The default JoinReq Data Rate is DR2 (SF10/125KHz), this setting
862 ensures that end-devices are compatible with the 400ms dwell time
863 limitation until the actual dwell time limit is notified to the end-device by
864 the network server via the MAC command TxParamSetupReq.
©2017 LoRa™ Alliance Page 37 of 72 The authors reserve the right to change
specifications without notice.
 LoRaWAN 1.1 Regional Parameters

865 AU915-928 end-devices MUST consider UplinkDwellTime = 1 during

866 boot stage until reception of the TxParamSetupReq command.
867 AU915-928 end-devices MUST always consider DownlinkDwellTime =
868 0, since downlink channels use 500KHz bandwidth without any dwell
869 time limit.
870

871 2.6.3 AU915-928 Data Rate and End-point Output Power encoding
872 The “TxParamSetupReq/Ans” MAC commands MUST be implemented by AU915-928
873 devices.
874 If the field UplinkDwellTime is set to 1 by the network server in the
875 TxParamSetupReq command, AU915-928 end-devices SHALL adjust
876 the time between two consecutive uplink transmissions to meet the local
877 regulation. Twenty seconds (20s) are recommended between 2 uplink
878 transmissions when UplinkDwellTime = 1 but this value MAY be
879 adjusted depending on local regulation.
880 There is no such constraint on time between two consecutive
881 transmissions when UplinkDwellTime = 0.
882
883 The following encoding is used for Data Rate (DR) and End-point EIRP (TXPower) in the
884 AU915-928 band:
885
DataRate Configuration Indicative
physical bit
rate [bit/sec]
0 LoRa: SF12 / 125 kHz 250
1 LoRa: SF11 / 125 kHz 440
2 LoRa: SF10 / 125 kHz 980
3 LoRa: SF9 / 125 kHz 1760
4 LoRa: SF8 / 125 kHz 3125
5 LoRa: SF7 / 125 kHz 5470
6 LoRa: SF8 / 500 kHz 12500
7 RFU
8 LoRa: SF12 / 500 kHz 980
9 LoRa: SF11 / 500 kHz 1760
10 LoRa: SF10 / 500 kHz 3900
11 LoRa: SF9 / 500 kHz 7000
12 LoRa: SF8 / 500 kHz 12500
13 LoRa: SF7 / 500 kHz 21900
14 RFU
15 Defined in LoRaWAN
886 Table 35: AU915-928 Data rate table
887
888 DR6 is identical to DR12, DR8...13 MUST be implemented in end-devices and are reserved
889 for future applications.
890
891
892
893
894
©2017 LoRa™ Alliance Page 38 of 72 The authors reserve the right to change
specifications without notice.
 LoRaWAN 1.1 Regional Parameters

TXPower Configuration (EIRP)

0 Max EIRP
1:14 Max EIRP – 2*TXPower
15 Defined in LoRaWAN
895 Table 36 : AU915-928 TX power table
896
897 EIRP refers to the Equivalent Isotropically Radiated Power, which is the radiated output
898 power referenced to an isotropic antenna radiating power equally in all directions and whose
899 gain is expressed in dBi.
900
901 By default MaxEIRP is considered to be +30dBm. The Max EIRP can be modified by the
902 network server through the TxParamSetupReq MAC command and SHOULD be used by
903 both the end-device and the network server once TxParamSetupReq is acknowledged by
904 the device via TxParamSetupAns.

905

906 2.6.4 AU915-928 JoinAccept CFList

907
908 The AU915-928 LoRaWAN supports the use of the optional CFlist appended to the
909 JoinResp message. If the CFlist is not empty then the CFListType field SHALL contain the
910 value one (0x01) to indicate the CFList contains a series of ChMask fields. The ChMask
911 fields are interpreted as being controlled by a virtual ChMaskCntl that initializes to a value of
912 zero (0) and increments for each ChMask field to a value of four(4). (The first 16 bits
913 controls the channels 1 to 16, ..)
Size [2] [2] [2] [2] [2] [2] [3] [1]
(bytes)
CFList ChMask0 ChMask1 ChMask2 ChMask3 ChMask4 RFU RFU CFListType
914

915 2.6.5 AU915-928 LinkAdrReq command

916 For the AU915-928 version the ChMaskCntl field of the LinkADRReq command has the
917 following meaning:
918
919
ChMaskCntl ChMask applies to
0 Channels 0 to 15
1 Channels 16 to 31
.. ..
4 Channels 64 to 71
5 8LSBs controls Channel Blocks 0 to 7
8MSBs are RFU
6 All 125 kHz ON
ChMask applies to channels 64 to 71
7 All 125 kHz OFF
ChMask applies to channels 64 to 71
920 Table 37: AU915-928 ChMaskCntl value table

921 If ChMaskCntl = 5 then the corresponding bits in the ChMask enable and disable a bank of 8
922 125kHz channels and the corresponding 500kHz channel defined by the following calculation:
923 [ChannelMaskBit * 8, ChannelMaskBit * 8 +7],64+ChannelMaskBit.

©2017 LoRa™ Alliance Page 39 of 72 The authors reserve the right to change
specifications without notice.
 LoRaWAN 1.1 Regional Parameters

924 If ChMaskCntl = 6 then 125 kHz channels are enabled, if ChMaskCntl = 7 then 125 kHz
925 channels are disabled. Simultaneously the channels 64 to 71 are set according to the ChMask
926 bit mask. The DataRate specified in the command need not be valid for channels specified in
927 the ChMask, as it governs the global operational state of the end-device.
928

929 2.6.6 AU915-928 Maximum payload size

930 The maximum MACPayload size length (M) is given by the following table for both uplink
931 dwell time configurations: No Limit and 400ms. It is derived from the maximum allowed
932 transmission time at the PHY layer taking into account a possible repeater encapsulation. The
933 maximum application payload length in the absence of the optional FOpt MAC control field
934 (N) is also given for information only. The value of N might be smaller if the FOpt field is not
935 empty:
936
DataRate UplinkDwellTime=0 UplinkDwellTime=1
937
M N M N
938 0 59 51 N/A N/A
939 1 59 51 N/A N/A
2 59 51 19 11
940 3 123 115 61 53
941 4 230 222 133 125
5 230 222 250 242
942 6 230 222 250 242
943 7 Not defined Not defined
8 41 33 41 33
944 9 117 109 117 109
945 10 230 222 230 222
11 230 222 230 222
946 12 230 222 230 222
13 230 222 230 222
947
14:15 Not defined Not defined
948
949 Table 38: AU915-928 maximum payload size

950 The greyed lines correspond to the data rates that may be used by an end-device behind a
951 repeater.
952 For AU915-928, DownlinkDwellTime MUST be set to 0 (no limit). The
953 400ms dwell time MAY only apply to uplink channels depending on the
954 local regulations.
955 If the end-device will never operate with a repeater then the maximum application payload
956 length in the absence of the optional FOpt control field SHOULD be:
957
DataRate UplinkDwellTime=0 UplinkDwellTime=1
M N M N
0 59 51 N/A N/A
1 59 51 N/A N/A
2 59 51 19 11
3 123 115 61 53
4 250 242 133 125
5 250 242 250 242
6 250 242 250 242

©2017 LoRa™ Alliance Page 40 of 72 The authors reserve the right to change
specifications without notice.
 LoRaWAN 1.1 Regional Parameters

958 7 Not defined Not defined

959 8 61 53 61 53
960 9 137 129 137 129
961 10 250 242 250 242
962 11 250 242 250 242
963
964 12 250 242 250 242
965 13 250 242 250 242
966 Table 39: AU915- 14:15 Not defined Not defined 928 maximum
967 payload size (not repeater
968 compatible)
969

970 2.6.7 AU915-928 Receive windows

971  The RX1 receive channel is a function of the upstream channel used to initiate the
972 data exchange. The RX1 receive channel can be determined as follows.
973 o RX1 Channel Number = Transmit Channel Number modulo 8
974  The RX1 window data rate depends on the transmit data rate (see Table 17 below).
975  The RX2 (second receive window) settings uses a fixed data rate and frequency.
976 Default parameters are 923.3Mhz / DR8
977
Upstream Downstream data rate
data rate
RX1DROff 0 1 2 3 4 5
set
DR0 DR8 DR8 DR8 DR8 DR8 DR8
DR1 DR9 DR8 DR8 DR8 DR8 DR8
DR2 DR10 DR9 DR8 DR8 DR8 DR8
DR3 DR11 DR10 DR9 DR8 DR8 DR8
DR4 DR12 DR11 DR10 DR9 DR8 DR8
DR5 DR13 DR12 DR11 DR10 DR9 DR8
DR6 DR13 DR13 DR12 DR11 DR10 DR9
978 Table 40 : AU915-928 downlink RX1 data rate mapping
979
980 The allowed values for RX1DROffset are in the [0:5] range. Values in the range [6:7] are
981 reserved for future use.
982

983 2.6.8 AU915-928 Class B beacon

984 The beacons are transmitted using the following settings:
DR 8 Corresponds to SF12 spreading factor with
500kHz bw
CR 1 Coding rate = 4/5
Signal polarity Non-inverted As opposed to normal downlink traffic which
uses inverted signal polarity
frequencies 923.3 to 927.5MHz Beaconing is performed on the same
with 600kHz steps channel that normal downstream traffic as
defined in the Class A specification
985 Table 41 : AU915-928 beacon settings

986 The downstream channel used for a given beacon is:

𝑏𝑒𝑎𝑐𝑜𝑛_𝑡𝑖𝑚𝑒
987 Channel = [𝑓𝑙𝑜𝑜𝑟 ( )] 𝑚𝑜𝑑𝑢𝑙𝑜 8
𝑏𝑒𝑎𝑐𝑜𝑛_𝑝𝑒𝑟𝑖𝑜𝑑

©2017 LoRa™ Alliance Page 41 of 72 The authors reserve the right to change
specifications without notice.
 LoRaWAN 1.1 Regional Parameters

988  whereby beacon_time is the integer value of the 4 bytes “Time” field of the beacon
989 frame
990  whereby beacon_period is the periodicity of beacons , 128 seconds
991  whereby floor(x) designates rounding to the integer immediately inferior or equal to x
992
993 Example: the first beacon will be transmitted on 923.3Mhz , the second
994 on 923.9MHz, the 9th beacon will be on 923.3Mhz again.
995
996
Beacon channel nb Frequency [MHz]
0 923.3
1 923.9
2 924.5
3 925.1
4 925.7
5 926.3
6 926.9
7 927.5
997
998
999 The beacon frame content is:
Size (bytes) 3 4 2 7 1 2
BCNPayload RFU Time CRC GwSpecific RFU CRC
1000

1001 2.6.9 AU915-928 Default Settings

1002 The following parameters are recommended values for the AU915-928 band.
1003 RECEIVE_DELAY1 1s
1004 RECEIVE_DELAY2 2 s (MUST be RECEIVE_DELAY1 + 1s)
1005 JOIN_ACCEPT_DELAY1 5s
1006 JOIN_ACCEPT_DELAY2 6s
1007 MAX_FCNT_GAP 16384
1008 ADR_ACK_LIMIT 64
1009 ADR_ACK_DELAY 32
1010 ACK_TIMEOUT 2 +/- 1 s (random delay between 1 and 3 seconds)
1011 If the actual parameter values implemented in the end-device are different from those default
1012 values (for example the end-device uses a longer RECEIVE_DELAY1 & 2 latency), those
1013 parameters MUST be communicated to the network server using an out-of-band channel
1014 during the end-device commissioning process. The network server may not accept
1015 parameters different from those default values.
1016

©2017 LoRa™ Alliance Page 42 of 72 The authors reserve the right to change
specifications without notice.