Issue link: https://read.uberflip.com/i/1428377
LoRaWAN Specification ©2015 LoRa™ Alliance Page 67 of 82 The authors reserve the right to change specifications without notice. 15.3.1 Gateway GPS coordinate:InfoDesc = 0, 1 or 2 1 For InfoDesc = 0 ,1 or 2, the content of the Info field encodes the GPS coordinates of the 2 antenna broadcasting the beacon 3 Size (bytes) 3 3 Info Lat Lng The latitude and longitude fields (Lat and Lng, respectively) encode the geographical 4 location of the gateway as follows: 5 The north-south latitude is encoded using a signed 24 bit word where -2 23 6 corresponds to 90° south (the South Pole) and 2 23 corresponds to 90° north (the 7 North Pole). The equator corresponds to 0. 8 The east-west longitude is encoded using a signed 24 bit word where - 9 2 23 corresponds to 180° west and 2 23 corresponds to 180° east. The Greenwich 10 meridian corresponds to 0. 11 15.4 Beaconing precise timing 12 The beacon is sent every 128 seconds starting at 00:00:00 Coordinated Universal Time 13 (UTC), 1 January 1970 plus NwkID plus TBeaconDelay. Therefore the beacon is sent at 14 B T = k * 128 + NwkID + TBeaconDelay 15 seconds after 00:00:00 Coordinated Universal Time (UTC), 1 January 1970 16 wherebyk is the smallest integer for which 17 k * 128 + NwkID>T 18 whereby 19 T = seconds since 00:00:00 Coordinated Universal Time (UTC), 1 January 1970. 20 Note: T is not (!) Unix time. Similar to GPS time and unlike Unix time, 21 T is strictly monotonically increasing and is not influenced by leap 22 seconds. 23 Whereby TBeaconDelay is a network specific delay in the [0:50] ms range. 24 TBeaconDelay may vary from one network to another and is meant to allow a slight 25 transmission delay of the gateways. TBeaconDelay must be the same for all gateways of a 26 given network. TBeaconDelay must be smaller than 50 ms. All end-devices ping slots use 27 the beacon transmission time as a timing reference, therefore the network server as to take 28 TBeaconDelay into account when scheduling the class B downlinks. 29 30 15.5 Network downlink route update requirements 31 When the network attempts to communicate with an end-device using a Class B downlink 32 slot, it transmits the downlink from the gateway which was closest to the end-device when 33 the last uplink was received. Therefore the network server needs to keep track of the rough 34 position of every Class B device. 35 Whenever a Class B device moves and changes cell, it needs to communicate with the 36 network server in order to update its downlink route. This update can be performed simply 37 by sending a ―confirmed‖ or ―unconfirmed‖ uplink, possibly without applicative payload. 38 The end-device has the choice between 2 basic strategies: 39
