Document

TS014-1.0.0 End-Device Capabilities API

Issue link: https://read.uberflip.com/i/1543540

Contents of this Issue

Navigation

Page 5 of 10

LoRaWAN ® End-Device Capabilities API Specification TS014-1.0.0 ©2026 LoRa Alliance ® Page 6 of 11 The authors reserve the right to change specifications without notice. 3 Device Profiles 108 3.1 Interface 109 DPS interfaces with the Home Network Server (hNS). A given hNS MAY interface with one 110 or more DPSs. A given DPS MAY interface with one or more hNS. 111 112 The specification in OpenAPI Definition of the Device Profile Server is available at: 113 114 https://resources.lorawan.net/openapis/end-device-capabilities/v1/operations.yaml 115 116 The specification is committed to a Git repository [GIT] with commit hash 117 073dfd477809836ab76ad18d873dbadf89aade56. 118 119 This document references reusable components in separate OpenAPI Definition documents. 120 It is expected that future specifications reference (parts of) these reusable components. 121 3.2 Message Flow 122 Figure 1 shows message flow between the hNS and the DPS for retrieving the Device 123 Profile for a given end-device based on its VendorID and VendorProfileID as defined in 124 [TS018]. 125 126 127 Figure 1: Message Flow 128 Step 1: 129 130 The hNS MUST determine the URL of the Device Profile Server. See Section 3.3 for 131 mechanisms to determine this URL. The Device Profile Server URL is the base URL: paths 132 of the operations in the OpenAPI Definition are appended to form the HTTP request URL. 133 134 Step 2: 135 136

Articles in this issue

Links on this page

view archives of Document - TS014-1.0.0 End-Device Capabilities API