> For the complete documentation index, see [llms.txt](https://prosbcdocs.telcobridges.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://prosbcdocs.telcobridges.com/telecom-references/protocols/tcap-architecture.md).

# TCAP Architecture

[TCAP](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/protocols/tcap/README.md) software supports only a connectionless network service. No functionality is needed from the ISP (Intermediate Service Part); only the connectionless functionality of [SCCP](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/protocols/sccp/README.md) is required. Therefore, the transaction sublayer always interfaces with SCCP through the connectionless primitives.

TCAP is intended to be used by real-time, sensitive applications (with small amounts of transferred data). The data transfer rate capability is limited by [MTP2](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/protocols/mtp2/README.md) links bandwidth. Refer to the MTP2 configuration section to learn how to configure MTP2 links to increase MTP2 links bandwidth by using multiple timeslots by link or High Speed Link ([HSL](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/protocols/hsl/README.md)) links. Each [timeslot](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/transmission/timeslot/README.md) could transfer a maximum of 64KBPS. In multiple timeslots mode, it is possible to transfer a maximum of 256KBPS by MTP2 link. When using HSL, it is possible to transfer a maximum of 1984KBPS by MTP2 link. Thus the data transfer rate capability depends on the available MTP2 links and its configuration. The application real-time requirement and available MTP2 links bandwidth will mainly determine the maximum TCAP message size that could be used.

Each TCAP instance can handle a maximum of 8 userparts, 80,000 dialogs and 80,000 components. Each TCAP userpart can handle a maximum of 10,000 dialogs and 10,000 components. These limits could be modified if required by TelcoBridges upon request.

TCAP provides the functions and procedures to create dialogues between applications and invoke application operations across an [SS7](https://telcobridges.com/media-gateways/solutions/signaling/migrating-ss7-sigtran/) network. TCAP is a service provider to MAP (Mobile Application Part) and INAP (Intelligent Network Application Protocol) and a service user of SCCP (as shown in the figure immediately below.

![filename](https://docs.telcobridges.com/w/images/1/13/Filename)

![filename](https://docs.telcobridges.com/w/images/1/13/Filename)


---

# 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://prosbcdocs.telcobridges.com/telecom-references/protocols/tcap-architecture.md?ask=<question>&goal=<endgoal>
```

`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.