Table 12-7: CryptoProcessJoinAccept Response
Byte
Data from Host
Data to Host
•
DecKeyID and VerKeyID are defined in
DecKeyID specifies the key used for decryption of the message.
VerKeyID specifies the key used for the MIC verification.
•
Depending on the LoRaWanVer, the expected Header size N is 1 byte (v1.0) or 12 bytes (v1.1).
LoRaWanVer=0: LoRaWAN verison 1.0
LoRaWanVer=1: LoRaWAN verison 1.1
...
•
Header1, ... ,HeaderN: Header
•
Data1, ... ,DataN: Data. Data size M is either 16 Bytes or 32 Bytes. Data must include the encrypted MIC.
•
CEStatus is defined in section
12.3.5 CryptoComputeAesCmac
The command CryptoComputeAesCmac( ) will compute the AES CMAC of the provided data using the specified Key and
return the MIC.
Table 12-8: CryptoComputeAesCmac Command
Byte
Data from Host
Data to Host
Table 12-9: CryptoComputeAesCmac Response
Byte
0
Data from Host
0x00
Data to Host
Stat1
•
KeyID: specified Key ID, as defined in
•
Data1, Data2, ... , DataN: Provided data, considered as Byte buffers.
•
CEStatus: defined in section
•
MIC: Message Integrity Check (first 4 bytes of the CMAC).
LR1110
User Manual
Rev.1.0
UM.LR1110.W.APP
March 2020
0
1
0x00
0x00
Stat1
CEStatus
Table 12-1: Cryptographic Keys Usage and
CEStatus on page
107.
0
1
KeyID
0x05
0x05
(7:0)
IrqStatus
Stat1
Stat2
(31:24)
1
0x00
CEStatus
Table 12-1: Cryptographic Keys Usage and
CEStatus on page
107.
www.semtech.com
2
0x00
Data1
2
3
4
Data1
Data2
IrqStatus
IrqStatus
(23:16)
(15:8)
2
3
0x00
0x00
MIC1
MIC2
...
...
...
DataM
Derivation:
5
...
Data3
...
IrqStatus
...
(7:0)
4
0x00
MIC3
Derivation. Goes from 0 to 27.
M+3
0x00
N+3
DataN
0x00
5
0x00
MIC4
109 of 130
Semtech