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

# MTP2 Architecture

[MTP Level 2](/telecom-references/ss7-and-signalling/mtp2.md) defines the functions and procedures of the signaling system for providing reliable transfer of signaling messages over a signaling link. The MTP2 layer is a service provider to the MTP3 Link layer. The MTP2 layer is a service user of line interfaces / line services as seen in the shown in the figure below.

![MTP2 architecture](https://docs.telcobridges.com/w/images/9/99/MTP2-architecture.jpg)

MTP2 is used in conjunction with an above local MTP3 layer.

![MTP2 layer hierarchy](https://docs.telcobridges.com/w/images/3/35/MTP2-layer-hierarchy.jpg)

A MTP2 Link must be associated with one line interface/service. It’s a 1-to-1 association. MTP Level 2 defines the functions and procedures of the signaling system for providing reliable transfer of signaling messages over a signaling link.

**IMPORTANT NOTE:** It is important to ensure that the received and transmitted clocks of the line interface/service were synchronized. This can be useful for removing/limiting undesirable FIB and BSN errors. (See section “Clock Configurations” in the TB640 user’s guide.)

### Priorities

No pre-emption of data occurs in the process of being transmitted or requiring retransmission. Only a single congestion priority is supported for ANSI and ITU. For a TTC/NTT link, transmitted data buffers are prioritized based on the priority indicated by [MTP Level 3](/telecom-references/ss7-and-signalling/mtp3.md).

### Flow control

The MTP Level 2 software regulates data flow when resource utilization (such as buffer pool size or queue length) reaches specifies thresholds. For each threshold, MTP Level 2 performs one of the following actions:

* Informs the layer manager about flow control.
* Sends a link status signal unit with status "B" (busy).
* Sends a flow control indication to the upper layer.

The MTP Level 2 software prevents deadlocks and overload conditions from occurring.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://tmediadocs.telcobridges.com/telecom-references/ss7-and-signalling/mtp2/mtp2-architecture.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.