Issue link: https://read.uberflip.com/i/1545681
LoRaWAN ® Device Identification QR Codes for Automated Onboarding Specification TS018- 1.0.0 ©2026 LoRa Alliance ® Page 7 of 17 The authors reserve the right to change specifications without notice. 4 Onboarding Tag Content 151 4.1 Character Set 152 153 The characters used in the QR code SHALL use the Augmented Backus-Naur Form (ABNF) 154 [RFC5234], as follows: 155 156 QRALPHANUM = DIGIT / UPPERALPHA / "$" / "%" / "*" / "+" / "-" / "." / "/" 157 ; ":" excluded, except when used as separator 158 UPPERALPHA = %x41-5A ; "A" to "Z" 159 DIGIT = %x30-39 ; "0" to "9" 160 4.2 Tag Information 161 162 Data is organized similarly to URN. A specific sequence of values and optional values SHALL 163 be delimited by a colon character ":". 164 165 Note: This document has been written to enable the option to adopt this 166 identifier within a standard URN as managed by IETF in the future. 167 Specifically, this document would allow the identifier as described to be 168 prefaced by "URN:DEV:LW:" if and when IANA allocates this URN to 169 the LoRa Alliance. 170 171 172 The preface of the identifier SHALL consist of "LW:". 173 174 The identifier SHALL be, at the minimum, composed of the following mandatory values, and 175 always in this order: SchemaID, JoinEUI, DevEUI, ProfileID. 176 177 The mandatory values MAY be followed by one or more optional extensions. The optional 178 extensions are CheckSum, OwnerToken, SerNum, DevProfileServer, and Proprietary 179 extension and are pre-fixed by a key: 180 181 Parameters Key Description CheckSum C QR Checksum OwnerToken O Owner Token SerNum S Device Serial Number DevProfileServer D Device Profile Server (hostname and port number) Proprietary P Proprietary Extension Table 1: Extension Keys 182 Any other Key not defined in this specification is RFU (Reserved for Future Use) and SHALL 183 NOT be used. 184 185 If a QR reader encounters an unrecognized Key value (e.g., because the QR code is 186 generated by using a later version of this specification that defined a new Key value), it SHALL 187 skip the unrecognized extension and still process the recognized ones. 188 189 The maximum size of the full tag information SHALL be 128 characters. 190