User Services Platform (USP) TR-369a2 - Issue 1 - Amendment 2

Sep 8, 2026

Upload by Rizky

User Services Platform (USP) TR-369a2 defines an architecture and protocol suite for secure end-to-end message exchange between a USP Agent and a Controller. It specifies endpoints, service elements, data model path grammar, discovery and advertisement methods, and supported message transfer protocols including WebSocket, STOMP, and MQTT. The document covers message encoding, session-context exchange rules, integrity validation, authentication and authorization with RBAC and certificates, and defined operations with error handling. It also includes annexes and appendices for bulk data collection, software module and firmware management, device proxying, and IoT data model theory of operation.

LanguageEnglish

CategoryTechnology

FormatPDF

Pages213

Reading Time8 h 57 min

AccessFree to download

Introduction

Executive Summary

Purpose and Scope

References and Terminology

Definitions

Abbreviations

Specification Impact

Architecture

Endpoints

Endpoint Identifier

Service Elements

Data Models

Path Names

Other Path Decorators

Data Model Path Grammar

Discovery and Advertisement

Controller Information

Required Agent Information

Use of DHCP for Acquiring Controller Information

Using mDNS

Using DNS

DNS-SD Records

Using the SendOnBoardRequest() operation and OnBoardRequest notification

Message Transfer Protocols

Generic Requirements

CoAP Binding (DEPRECATED)

WebSocket Binding

STOMP Binding

MQTT Binding

Message Encoding

Parameter and Argument Value Encoding

End to End Message Exchange

Exchange of USP Records within an E2E Session Context

Exchange of USP Records without an E2E Session Context

Validating the Integrity of the USP Record

Secure Message Exchange

Messages

Encapsulation in a USP Record

Requests, Responses and Errors

Message Structure

Creating, Updating, and Deleting Objects

Reading an Agent’s State and Capabilities

Notifications and Subscription Mechanism

Defined Operations Mechanism

Error Codes

Authentication and Authorization

Authentication

Role Based Access Control (RBAC)

Trusted Certificate Authorities

Trusted Brokers

Self-Signed Certificates

Agent Authentication

Challenge Strings and Images

Analysis of Controller Certificates

Theory of Operations

Annex A: Bulk Data Collection

Introduction

HTTP Bulk Data Collection

MQTT Bulk Data Collection

USPEventNotif Bulk Data Collection

Using Wildcards to Reference Object Instances in the Report

Using Alternative Names in the Report

Encoding of Bulk Data

Appendix I: Software Module Management

Lifecycle Management

Software Modules

Execution Environment Concepts

Fault Model

Appendix II: Firmware Management of Devices with USP Agents

Getting the firmware image onto the device

Using multiple firmware images

Appendix III: Device Proxy

Appendix IV: Proxying

Proxying Building Block Functions

Discovery Proxy

Connectivity Proxy

Message Transfer Protocol (MTP) Proxy

USP to Non-USP Proxy

Appendix V: IoT Data Model Theory of Operation

Introduction

IoT data model overview

Architecture mappings

IoT data model Object details

Examples

User Services Platform (USP) TR-369a2 Issue 1 Amendment 2 TR-369a2 – User Services Platform (USP) Issue: 1 Amendment 2 (release-1 .2-4) Issue Date: January 2022 1 Introduction 1.1 Executive Summary 1.2 Purpose and Scope 1.3 References and Terminology 1.4 Definitions 1.5 Abbreviations 1.6 Specification Impact 2 Architecture 2.1 Endpoints 2.2 Endpoint Identifier 2.3 Service Elements 2.4 Data Models 2.5 Path Names 2.6 Other Path Decorators 2.7 Data Model Path Grammar 3 Discovery and Advertisement 3.1 Controller Information 3.2 Required Agent Information 3.3 Use of DHCP for Acquiring Controller Information 3.4 Using mDNS 3.5 Using DNS 3.6 DNS-SD Records 3.7 Using the SendOnBoardRequest() operation and OnBoardRequest notification 4 Message Transfer Protocols 4.1 Generic Requirements 4.2 CoAP Binding (DEPRECATED) 4.3 WebSocket Binding 4.4 STOMP Binding 4.5 MQTT Binding 5 Message Encoding 5.1 Parameter and Argument Value Encoding 6 End to End Message Exchange 6.1 Exchange of USP Records within an E2E Session Context 6.2 Exchange of USP Records without an E2E Session Context 6.3 Validating the Integrity of the USP Record 6.4 Secure Message Exchange 7 Messages 7.1 Encapsulation in a USP Record January 2022 © The Broadband Forum. All rights reserved. 1 of 213 User Services Platform (USP) TR-369a2 Issue 1 Amendment 2 7.2 Requests , Responses and Errors 7.3 Message Structure 7.4 Creating , Updating , and Deleting Objects 7.5 Reading an Agent’s State and Capabilities 7.6 Notifications and Subscription Mechanism 7.7 Defined Operations Mechanism 7.8 Error Codes 8 Authentication and Authorization 8.1 Authentication 8.2 Role Based Access Control (RBAC) 8.3 Trusted Certificate Authorities 8.4 Trusted Brokers 8.5 Self-Signed Certificates 8.6 Agent Authentication 8.7 Challenge Strings and Images 8.8 Analysis of Controller Certificates 8.9 Theory of Operations Annex A: Bulk Data Collection A.1 Introduction A.2 [HTTP Bulk Data Collection](HTTP Bulk Data Collection) A.3 MQTT Bulk Data Collection A.4 USPEventNotif Bulk Data Collection A.5 Using Wildcards to Reference Object Instances in the Report A.6 Using Alternative Names in the Report A.7 Encoding of Bulk Data Appendix I: Software Module Management I.1 Lifecycle Management I.2 Software Modules I.3 Execution Environment Concepts I.4 Fault Model Appendix II: Firmware Management of Devices with USP Agents II.1 Getting the firmware image onto the device II.2 Using multiple firmware images Appendix III: Device Proxy Appendix IV: Proxying IV.1 Proxying Building Block Functions IV.2 Discovery Proxy IV.3 Connectivity Proxy IV.4 Message Transfer Protocol (MTP) Proxy IV.5 USP to Non-USP Proxy Appendix V: IoT Data Model Theory of Operation V.1 Introduction V.2 IoT data model overview V.3 Architecture mappings V.4 IoT data model Object details V.5 Examples January 2022 © The Broadband Forum. All rights reserved. 2 of 213 User Services Platform (USP) TR-369a2 Issue 1 Amendment 2 List of Figures 1. USP Agent and Controller Architecture 2. Receiving a X.509 Certificate 3. Example: USP Request/Response over the CoAP MTP 4. WebSocket Session Handshake 5. USP Request using a WebSocket Session 6. USP over STOMP Architecture 7. USP over MQTT Architecture 8. MQTT Packets 9. Processing of Received USP Records 10. E2E Segmentation and Reassembly 11. TLS Session Handshake 12. A successful request/response sequence 13. A failed request/response sequence 14. Operate Message Flow for Synchronous Operations 15. Operate Message Flow for Asynchronous Operations 16. Receiving a USP Record 17. USP Record without USP Layer Secure Message Exchange 18. Sending a USP Record 19. Checking a Certificate 20. Determin

FAQs

What core components does USP TR-369a2 specify for the agent-controller interaction?

It specifies USP endpoints, endpoint identifiers, service elements, and data models, along with path naming and path grammar used for data model references. The document also defines discovery and advertisement mechanisms to establish the controller/agent relationship.

Which message transfer protocols are supported and how are messages transported?

The specification defines a set of message transfer protocols including WebSocket binding, STOMP binding, and MQTT binding, while also listing CoAP binding as deprecated. It provides rules for generic requirements and protocol-specific transport of USP messages.

How does TR-369a2 handle security, authentication, and authorization?

It covers end-to-end secure message exchange, integrity validation of USP records, and authentication and authorization mechanisms. The document includes RBAC, trusted certificate authorities and brokers, self-signed certificates, and agent authentication topics, along with controller certificate analysis.

Sep 8, 2026

Upload by Rizky