> For the complete documentation index, see [llms.txt](https://docs.oktopus.app.br/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.oktopus.app.br/usp-tr-369/mtps.md). # MTPs The MTP, or Message Transfer Protocol, is a protocol that operates one layer below the User Services Platform (USP). Its main function is to transport messages between USP Endpoints. The MTP essentially encapsulates the datagrams that make up the USP messages, along with essential information such as the USP version and the IDs of the source and destination Endpoints. In addition, it may contain metadata to ensure integrity, security, and the delivery of fragmented messages. ## Multiple MTPs and Configuration Both Agents and Controllers can support multiple MTPs. When an Agent operates with multiple MTPs, it can be configured to connect to a specific Controller through more than one protocol. When an Agent sends a notification, it may use a specific MTP, try to send through all MTPs simultaneously, or send sequentially through each MTP. ### Supported Protocols The USP specification defines different bindings, which allow specific protocols such as **CoAP** (deprecated), **WebSockets**, **STOMP**, **MQTT**, and **UDS** to carry USP records in their payloads. ### Security :closed\_lock\_with\_key: For USP implementations in environments **where messages are transported over the internet, the use of secure transport is mandatory**. MTPs that operate over TCP must implement at least the TLS 1.2 protocol. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.oktopus.app.br/usp-tr-369/mtps.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.