[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"doc-detail-216847-en":3,"doc-seo-216847-105":30,"detail-sidebar-cat-0-en-105":92},{"code":4,"msg":5,"data":6},0,"success",{"doc_id":7,"user_id":8,"nickname":9,"user_avatar":10,"doc_module":4,"category_id":11,"category_name":12,"doc_title":13,"doc_description":14,"doc_content":15,"file_id":16,"file_url":17,"file_type":18,"file_size":19,"view_count":20,"is_deleted":4,"is_public":20,"is_downloadable":20,"audit_status":20,"page_count":21,"language":22,"language_code":23,"site_id":24,"html_lang":23,"table_of_contents":25,"faqs":26,"seo_title":27,"seo_description":14,"update_tm":28,"read_time":29},216847,962085564807,"Rizky","https://ap-avatar.wpscdn.com/davatar_6f874abed73319feea01a86fa6f0fab8",6,"Technology","User Services Platform (USP) TR-369a2 - Issue 1 - Amendment 2","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.","User Services Platform (USP) TR-369a2 Issue 1 Amendment 2  \nTR-369a2 – User Services Platform (USP)  \nIssue: 1 Amendment 2 (release-1 .2-4)  \nIssue Date: January 2022  \n  1 Introduction  \n  1.1 Executive Summary  \n  1.2 Purpose and Scope  \n  1.3 References and Terminology  \n  1.4 Definitions  \n  1.5 Abbreviations  \n  1.6 Specification Impact  \n 2 Architecture  \n 2.1 Endpoints  \n 2.2 Endpoint Identifier  \n 2.3 Service Elements  \n 2.4 Data Models  \n 2.5 Path Names  \n 2.6 Other Path Decorators  \n 2.7 Data Model Path Grammar  \n 3 Discovery and Advertisement  \n 3.1 Controller Information  \n 3.2 Required Agent Information  \n 3.3 Use of DHCP for Acquiring Controller Information  \n 3.4 Using mDNS  \n 3.5 Using DNS  \n 3.6 DNS-SD Records  \n 3.7 Using the SendOnBoardRequest() operation and OnBoardRequest notification  \n 4 Message Transfer Protocols  \n 4.1 Generic Requirements  \n 4.2 CoAP Binding (DEPRECATED)  \n 4.3 WebSocket Binding  \n 4.4 STOMP Binding  \n 4.5 MQTT Binding  \n 5 Message Encoding  \n 5.1 Parameter and Argument Value Encoding  \n 6 End to End Message Exchange  \n 6.1 Exchange of USP Records within an E2E Session Context  \n 6.2 Exchange of USP Records without an E2E Session Context  \n 6.3 Validating the Integrity of the USP Record  \n 6.4 Secure Message Exchange  \n 7 Messages  \n 7.1 Encapsulation in a USP Record  \nJanuary 2022 © The Broadband Forum. All rights reserved. 1 of 213  \nUser Services Platform (USP) TR-369a2 Issue 1 Amendment 2  \n 7.2 Requests , Responses and Errors  \n 7.3 Message Structure  \n 7.4 Creating , Updating , and Deleting Objects  \n 7.5 Reading an Agent’s State and Capabilities  \n 7.6 Notifications and Subscription Mechanism  \n 7.7 Defined Operations Mechanism  \n 7.8 Error Codes  \n 8 Authentication and Authorization  \n 8.1 Authentication  \n 8.2 Role Based Access Control (RBAC)  \n 8.3 Trusted Certificate Authorities  \n 8.4 Trusted Brokers  \n 8.5 Self-Signed Certificates  \n 8.6 Agent Authentication  \n 8.7 Challenge Strings and Images  \n 8.8 Analysis of Controller Certificates  \n 8.9 Theory of Operations  \n Annex A: Bulk Data Collection  \n A.1 Introduction  \n A.2 [HTTP Bulk Data Collection](HTTP Bulk Data Collection)  \n A.3 MQTT Bulk Data Collection  \n A.4 USPEventNotif Bulk Data Collection  \n A.5 Using Wildcards to Reference Object Instances in the Report  \n A.6 Using Alternative Names in the Report  \n A.7 Encoding of Bulk Data  \n Appendix I: Software Module Management  \n  I.1 Lifecycle Management  \n  I.2 Software Modules  \n  I.3 Execution Environment Concepts  \n  I.4 Fault Model  \n Appendix II: Firmware Management of Devices with USP Agents  \n II.1 Getting the firmware image onto the device  \n  II.2 Using multiple firmware images  \n Appendix III: Device Proxy  \n Appendix IV: Proxying  \n  IV.1 Proxying Building Block Functions  \n  IV.2 Discovery Proxy  \n  IV.3 Connectivity Proxy  \n  IV.4 Message Transfer Protocol (MTP) Proxy  \n  IV.5 USP to Non-USP Proxy  \n Appendix V: IoT Data Model Theory of Operation  \n V.1 Introduction  \n V.2 IoT data model overview  \n V.3 Architecture mappings  \n V.4 IoT data model Object details  \n V.5 Examples  \nJanuary 2022 © The Broadband Forum. All rights reserved. 2 of 213  \nUser Services Platform (USP) TR-369a2 Issue 1 Amendment 2  \nList of Figures  \n1. USP Agent and Controller Architecture  \n2. Receiving a X.509 Certificate  \n3. Example: USP Request/Response over the CoAP MTP  \n4. WebSocket Session Handshake  \n5. USP Request using a WebSocket Session  \n6. USP over STOMP Architecture  \n7. USP over MQTT Architecture  \n8. MQTT Packets  \n9. Processing of Received USP Records  \n10. E2E Segmentation and Reassembly  \n11. TLS Session Handshake  \n12. A successful request/response sequence  \n13. A failed request/response sequence  \n14. Operate Message Flow for Synchronous Operations  \n15. Operate Message Flow for Asynchronous Operations  \n16. Receiving a USP Record  \n17. USP Record without USP Layer Secure Message Exchange  \n18. Sending a USP Record  \n19. Checking a Certificate  \n20. Determin","cbCaid7qWRP7Pqo5","https://ap.wps.com/l/cbCaid7qWRP7Pqo5","pdf",3268979,1,213,"English","en",105,"# Introduction\n## Executive Summary\n## Purpose and Scope\n## References and Terminology\n## Definitions\n## Abbreviations\n## Specification Impact\n# Architecture\n## Endpoints\n## Endpoint Identifier\n## Service Elements\n## Data Models\n## Path Names\n## Other Path Decorators\n## Data Model Path Grammar\n# Discovery and Advertisement\n## Controller Information\n## Required Agent Information\n## Use of DHCP for Acquiring Controller Information\n## Using mDNS\n## Using DNS\n## DNS-SD Records\n## Using the SendOnBoardRequest() operation and OnBoardRequest notification\n# Message Transfer Protocols\n## Generic Requirements\n## CoAP Binding (DEPRECATED)\n## WebSocket Binding\n## STOMP Binding\n## MQTT Binding\n# Message Encoding\n## Parameter and Argument Value Encoding\n# End to End Message Exchange\n## Exchange of USP Records within an E2E Session Context\n## Exchange of USP Records without an E2E Session Context\n## Validating the Integrity of the USP Record\n## Secure Message Exchange\n# Messages\n## Encapsulation in a USP Record\n## Requests, Responses and Errors\n## Message Structure\n## Creating, Updating, and Deleting Objects\n## Reading an Agent’s State and Capabilities\n## Notifications and Subscription Mechanism\n## Defined Operations Mechanism\n## Error Codes\n# Authentication and Authorization\n## Authentication\n## Role Based Access Control (RBAC)\n## Trusted Certificate Authorities\n## Trusted Brokers\n## Self-Signed Certificates\n## Agent Authentication\n## Challenge Strings and Images\n## Analysis of Controller Certificates\n## Theory of Operations\n# Annex A: Bulk Data Collection\n## Introduction\n## HTTP Bulk Data Collection\n## MQTT Bulk Data Collection\n## USPEventNotif Bulk Data Collection\n## Using Wildcards to Reference Object Instances in the Report\n## Using Alternative Names in the Report\n## Encoding of Bulk Data\n# Appendix I: Software Module Management\n## Lifecycle Management\n## Software Modules\n## Execution Environment Concepts\n## Fault Model\n# Appendix II: Firmware Management of Devices with USP Agents\n## Getting the firmware image onto the device\n## Using multiple firmware images\n# Appendix III: Device Proxy\n# Appendix IV: Proxying\n## Proxying Building Block Functions\n## Discovery Proxy\n## Connectivity Proxy\n## Message Transfer Protocol (MTP) Proxy\n## USP to Non-USP Proxy\n# Appendix V: IoT Data Model Theory of Operation\n## Introduction\n## IoT data model overview\n## Architecture mappings\n## IoT data model Object details\n## Examples","[{\"question\":\"What core components does USP TR-369a2 specify for the agent-controller interaction?\",\"answer\":\"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.\"},{\"question\":\"Which message transfer protocols are supported and how are messages transported?\",\"answer\":\"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.\"},{\"question\":\"How does TR-369a2 handle security, authentication, and authorization?\",\"answer\":\"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.\"}]","User Services Platform (USP) TR-369a2 - Issue 1 - Amendment 2 | PDF",1788827968,537,{"code":4,"msg":31,"data":32},"ok",{"site_id":24,"language":23,"slug":33,"title":13,"keywords":34,"description":14,"schema_data":35,"social_meta":87,"head_meta":89,"extra_data":91,"updated_unix":28},"user-services-platform-usp-tr-369a2-issue-1-amendment-2","",{"@graph":36,"@context":86},[37,54,69],{"@type":38,"itemListElement":39},"BreadcrumbList",[40,44,48,51],{"item":41,"name":42,"@type":43,"position":20},"https://docshare.wps.com","Home","ListItem",{"item":45,"name":46,"@type":43,"position":47},"https://docshare.wps.com/document/","Document",2,{"item":49,"name":12,"@type":43,"position":50},"https://docshare.wps.com/document/technology/",3,{"item":52,"name":13,"@type":43,"position":53},"https://docshare.wps.com/document/user-services-platform-usp-tr-369a2-issue-1-amendment-2/216847/",4,{"url":52,"name":13,"@type":55,"author":56,"headline":13,"publisher":58,"fileFormat":61,"inLanguage":23,"description":14,"dateModified":62,"datePublished":63,"encodingFormat":61,"isAccessibleForFree":64,"interactionStatistic":65},"DigitalDocument",{"name":9,"@type":57},"Person",{"url":41,"name":59,"@type":60},"DocShare","Organization","application/pdf","2026-09-11","2026-09-08",true,{"@type":66,"interactionType":67,"userInteractionCount":20},"InteractionCounter",{"@type":68},"ViewAction",{"@type":70,"mainEntity":71},"FAQPage",[72,78,82],{"name":73,"@type":74,"acceptedAnswer":75},"What core components does USP TR-369a2 specify for the agent-controller interaction?","Question",{"text":76,"@type":77},"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.","Answer",{"name":79,"@type":74,"acceptedAnswer":80},"Which message transfer protocols are supported and how are messages transported?",{"text":81,"@type":77},"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.",{"name":83,"@type":74,"acceptedAnswer":84},"How does TR-369a2 handle security, authentication, and authorization?",{"text":85,"@type":77},"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.","https://schema.org",{"og:url":52,"og:type":88,"og:title":13,"og:site_name":59,"og:description":14},"article",{"robots":90,"canonical":52},"index,follow",{"doc_id":7,"site_id":24},{"code":4,"msg":5,"data":93},[94,98,102,106,111,114,119,124,129,132,136],{"id":20,"doc_module":4,"doc_module_name":46,"category_name":95,"show_sort_weight":96,"slug":97},"Story & Novel",90,"story-novel",{"id":47,"doc_module":4,"doc_module_name":46,"category_name":99,"show_sort_weight":100,"slug":101},"Literature",80,"literature",{"id":53,"doc_module":4,"doc_module_name":46,"category_name":103,"show_sort_weight":104,"slug":105},"Exam",70,"exam",{"id":107,"doc_module":4,"doc_module_name":46,"category_name":108,"show_sort_weight":109,"slug":110},5,"Comic",60,"comic",{"id":11,"doc_module":4,"doc_module_name":46,"category_name":12,"show_sort_weight":112,"slug":113},50,"technology",{"id":115,"doc_module":4,"doc_module_name":46,"category_name":116,"show_sort_weight":117,"slug":118},7,"Healthcare",40,"healthcare",{"id":120,"doc_module":4,"doc_module_name":46,"category_name":121,"show_sort_weight":122,"slug":123},8,"Research & Report",30,"research-report",{"id":125,"doc_module":4,"doc_module_name":46,"category_name":126,"show_sort_weight":127,"slug":128},9,"Religion & Spirituality",20,"religion-spirituality",{"id":127,"doc_module":4,"doc_module_name":46,"category_name":130,"show_sort_weight":127,"slug":131},"World Cup","world-cup",{"id":133,"doc_module":4,"doc_module_name":46,"category_name":134,"show_sort_weight":133,"slug":135},10,"Lifestyle","lifestyle",{"id":137,"doc_module":4,"doc_module_name":46,"category_name":138,"show_sort_weight":107,"slug":139},19,"General","general"]