3.2 Required Agent InformationĪ Controller that has a relationship with an Agent needs to know the Agent’s Endpoint Identifier, connectivity information for the Agent’s MTP(s), and credentials.Ĭontrollers acquires this information upon initial connection by an Agent, though a LAN based Controller may acquire an Agent’s MTP information through mDNS Discovery. Other trust models are also possible, where an Agent without a current Controller association will trust the first discovered Controller, or where the Agent has a UI that allows a User to indicate whether a discovered Controller is authorized to configure that Agent. The Agent can be pre-configured with trusted root certificates or trusted certificates to allow authentication of Controllers. R-DIS.0 - An Agent that supports USP configuration of Controllers MUST implement the Object as defined in the Device:2 Data Model. Configured through a separate bootstrap mechanism such as a user interface or other management interface.Configured by an already-known-and-trusted Controller.This may be a URL with all of these components, a FQDN that resolves to provide all of these components via DNS-SD records, or mDNS discovery in the LAN.Įxample mechanisms for configuration include but are not limited to: 3.1 Controller InformationĪn Agent that has a USP relationship with a Controller needs to know that Controller’s Endpoint Identifier, credentials, and authorized Role.Īn Agent that has a USP relationship with a Controller needs to obtain information that allows it to determine at least one MTP, IP address, port, and resource path (if required by the MTP) of the Controller. Appendix V: IoT Data Model Theory of Operationĭiscovery is the process by which USP Endpoints learn the USP properties and MTP connection details of another Endpoint, either for sending USP Messages in the context of an existing relationship (where the Controller’s USP Endpoint Identifier, credentials, and authorized Role are all known to the Agent) or for the establishment of a new relationship.Īdvertisement is the process by which USP Endpoints make their presence known (or USP Endpoint presence is made known) to other USP Endpoints.IV.4 Message Transfer Protocol (MTP) Proxy.II.1 Getting the firmware image onto the device.
Appendix II: Firmware Management of Devices with USP Agents.A.6 Using Alternative Names in the Report.A.5 Using Wildcards to Reference Object Instances in the Report.8.8 Analysis of Controller Certificates.7.6 Notifications and Subscription Mechanism.7.5 Reading an Agent’s State and Capabilities.7.4 Creating, Updating, and Deleting Objects.6.3 Validating the Integrity of the USP Record.6.2 Exchange of USP Records without an E2E Session Context.6.1 Exchange of USP Records within an E2E Session Context.5.1 Parameter and Argument Value Encoding.3.7 Using the SendOnBoardRequest() operation and OnBoardRequest notification.3.3 Use of DHCP for Acquiring Controller Information.| Appendix V: IoT Data Model Theory of Operation
| Appendix II: Firmware Management of Devices with USP Agents
DESKOVERY 3.2 PDF
Specification HTML PDF Data Models Test Plan Resources FAQ
0 kommentar(er)
