Issue link: https://read.uberflip.com/i/1543540
LoRaWAN ® End-Device Capabilities API Specification TS014-1.0.0 ©2026 LoRa Alliance ® Page 8 of 11 The authors reserve the right to change specifications without notice. 3.3 Device Profile Server Discovery 139 The hNS is expected to identify and locate the DPS for a given end-device. There are 140 various ways for a hNS to do so. The hNS MAY use one or more of these methods to 141 determine the URL of the DPS. 142 3.3.1 DNS Lookup 143 The hNS can use DNS to lookup the Device Profile Server IP address or hostname using a 144 given VendorID [TS018]. 145 146 The hNS SHALL form the URL of the DPS by prepending "https://" to the IP address or 147 hostname. 148 3.3.2 Static Host 149 When relying on static hostnames, the hNS is configured to use a given DPS for all end- 150 devices, for end-devices of subset of vendors as identified by their VendorID [TS018], or for 151 a subset of end-devices according to other criteria. 152 153 If the static hostname does not include a scheme, the hNS SHALL form the URL of the DPS 154 by prepending "https://" to the hostname. 155 3.3.3 URL Extracted from QR Code 156 The hNS can extract the DPS URL value from the QR code of the end-device [TS018], if 157 available. 158 159 The hNS SHALL form the URL of the DPS by prepending "https://" to the DevProfileServer 160 hostname described in the QR code. 161 162 If a port number is encoded in the QR code along with the server name (e.g., server name 163 "example.com" and port 444 encoded as "example.com%3A444"), then the hNS SHALL use 164 that port instead of the default HTTPS port (443) to form the DPS URL. 165