There are two kinds of endpoints in USP: Agents, and Controllers. A USP Agent is an Endpoint that exposes functions represented by a set of service elements. It is mostly designed to receive and respond to messages from a USP Controller, or send Notifications about activity that the Controller has subscribed to. A USP Controller allows users and applications to manipulate the functions exposed by an Agent.
USP Agent and Controller Architecture (from TR-369).
In a USP system, endpoints identify themselves using an Endpoint ID. This is a value that can be either globally or locally unique, and is generated using a special scheme defined in TR-369. This ID is composed of three parts:
authority-scheme ":" [authority-id] ":" instance-id
The Endpoint ID is used in the to_id and from_id fields of a USP record. Endpoints must ignore messages that do not contain their own Endpoint Identifier in the to_id. While it is possible for a given Controller and Agent to have the same ID, these types of endpoints would never communicate with each other.
When used in the to_id or from_id, the Endpoint ID is used literally. However, the Endpoint ID can also be used in an endpoint’s certificate when providing authentication. In this case, the Endpoint ID is expressed as a Uniform Resource Name unique to the Broadband Forum, as follows:
"urn:bbf:usp:id:" authority-scheme ":" [authority-id] ":" instance-idv
Get your USP Agent certified now with the official Broadband Forum test platform.