Issue link: https://read.uberflip.com/i/1428305
TR005 LoRaWAN® Device Identification QR Codes ©2020 LoRa Alliance® Page 7 of 16 The authors reserve the right to change specifications without notice. 4 Onboarding Tag Content 134 4.1 Character Set 135 136 Only the ALPHA and DIGIT characters as defined in IETF RFC 5234 [RFC5234], ".", and ":" 137 SHALL be utilized. ALPHA characters SHALL be upper case. 138 4.2 Tag Information 139 140 Data is organized similarly to URN. A specific sequence of values and optional values are 141 delimited by a ":". 142 143 Note: This document has been written to enable the option to adopt 144 this identifier within a standard URN as managed by IETF in the future. 145 Specifically, this document would allow the identifier as described to be 146 prefaced by "URN:DEV:LW:" if and when IANA allocates this URN to 147 the LoRa Alliance. 148 149 150 The preface of the identifier SHALL only consist of "LW:". 151 152 The identifier SHALL be, at the minimum, composed of the following mandatory values, and 153 always in this order: SchemaID, JoinEUI, DevEUI, ProfileID. 154 155 The mandatory values MAY be followed by one or more optional extensions. The optional 156 extensions are CheckSum, OwnerToken, SerNum, and Proprietary extension and are pre- 157 fixed by a parameter key: 158 159 Parameters Key Description CheckSum C QR Checksum OwnerToken O Owner Token SerNum S Device Serial Number Proprietary P Proprietary Extension Table 1 – LoRaWAN® parameters keys 160 The maximum size of the full tag information shall be 128 characters, 48 characters are 161 consumed by the mandatory information which leaves 80 characters for the optional 162 extensions. 163 4.2.1 SchemaID 164 165 The SchemaID is used to indicate the schema that should be applied to the remaining data 166 of the identifier. The SchemaID consists of two characters and is currently defined in the 167 following table. 168 169 170 171 172