Issue link: https://read.uberflip.com/i/1428395
LoRaWAN ® L2 1.0.4 Specification © 2020 LoRa Alliance ® Page 64 of 90 The authors reserve the right to change specifications without notice. Upon receiving this command, the end-device SHALL answer with a BeaconFreqAns frame. 1955 The MAC payload of this frame contains the following information: 1956 1957 Size (octets) 1 BeaconFreqAns payload Status Table 65: BeaconFreqAns payload format 1958 1959 The bits of the Status octet have the following meaning: 1960 1961 Bits 7:1 0 Status RFU Beacon frequency ok Table 66: Status field format 1962 1963 1964 1965 Bit=0 Bit=1 Beacon frequency ok The end-device cannot use this frequency, the previous beacon frequency is kept The beacon frequency has been changed Table 67: Meaning of beacon frequency bits 1966 1967 1968 1969 1970 12.3 PingSlotChannelReq 1971 The server MAY send this command to the end-device to modify the frequency and/or the data 1972 rate at which the end-device expects the downlink pings. 1973 Once the Network Server has sent the PingSlotChannelReq command, it SHALL NOT 1974 attempt to use a Class B ping slot until it receives the PingSlotChannelAns. 1975 1976 Note: In order to take advantage of the network-initiated downlink 1977 capabilities provided by Class B, the network needs relatively recent 1978 information of how to best contact the end-device. This information is 1979 provided to the network through any and all uplinks received from the 1980 end-device. For this reason it is important for Class B enabled end- 1981 devices to send regular uplinks which implicitly inform the network of the 1982 best way to contact it as well as providing the network a chance to send 1983 new MAC commands which may be required for proper end-device 1984 operation. 1985 1986 1987 Octets 3 1 PingSlotChannelReq payload Frequency DR Table 68: PingSlotChannelReq payload format 1988