> 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/sccp-architecture.md).

# SCCP Architecture

The SCCP software supports these functions:

* [Connectionless Service](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/protocols/connectionless-service/README.md)
* [Management](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/protocols/management/README.md)
* [Routing](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/protocols/sccp-routing/README.md)
* [Traffic Limitation and Congestion Control](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/protocols/traffic-limitation-and-congestion-control/README.md) (ITU-96)
* [Interworking](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/protocols/interworking/README.md)

SCCP provides the functions and procedures to transfer data across an [SS7](https://telcobridges.com/media-gateways/solutions/signaling/migrating-ss7-sigtran/) network. SCCP is a service provider to [TCAP](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/protocols/tcap/README.md) and a service user of [MTP Level 3](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/protocols/mtp3/README.md) (as shown in the figure immediately below).

![SCCP architecture](https://docs.telcobridges.com/w/images/1/14/SCCP_architecture.JPG)

A SCCP layer has a Network section which represents a network identifier for a specific protocol variant. For a Network you must define:

* [LSAP(s)](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/signalling/lsap/README.md)
* Routes (for a specific or range of [destination point codes (DPC)](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/signalling/dpc/README.md))
* Userpart

SCCP LSAP must be associated with one MTP3 Userpart via a 1-to-1 association. A SCCP Route indicates a DPC that is accessible from this SCCP configuration node and their [SSN](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/parameters/sub-system-number/README.md).

SCCP Userpart can be used in conjunction with an above local TCAP layer and can be used as a standalone and communicates with remote TCAP layer (host application). See the connection mode table in the SCCP Userpart Configuration section.

A SCCP layer has a Userpart section which represents a sub-system number.

### References

* [Connectionless Service](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/protocols/connectionless-service/README.md)
* [Management](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/protocols/management/README.md)
* [Addressing](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/protocols/sccp-addressing/README.md)
* [Global Title Translation Association](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/protocols/global-title-translation-association/README.md)
* [Routing](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/protocols/sccp-routing/README.md)
* [Traffic Limitation and Congestion Control](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/protocols/traffic-limitation-and-congestion-control/README.md)
* [Interworking](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/protocols/interworking/README.md)
* [Messages](https://github.com/telcobridges-main/tmedia-wiki/tree/main/reference/protocols/sccp-messages/README.md)


---

# 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/sccp-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.