> 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/ss7-and-signalling/ss7/hsl.md).

# HSL

High Speed Link (HSL) refers to a single MTP2 link that uses the entire bandwidth of a trunk to transport MTP2 data.

The difference between a HSL MTP2 link and a Nx64/56kbps MTP2 link is that the Nx64/56kbps link uses many (N) independent [timeslots](/telecom-references/transmission-and-lines/timeslot.md), instead of all the [timeslots](/telecom-references/transmission-and-lines/timeslot.md). The HSL link and Nx64/56kbps link use a single [HDLC](/telecom-references/transmission-and-lines/hdlc.md) receiver/transmitter that is not bound by a timeslot's normal 7/8 bit boundary like it is for a low speed link (LSL). The HSL can use the complete bandwidth of a channelized trunk to transmit data. All MTP2 links on channelized T1/E1 trunks can be switched via digital cross-connect equipment that can handle the timeslot level.

### References

* [Wikipedia article](http://en.wikipedia.org/wiki/Signaling_System_7)


---

# 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://prosbcdocs.telcobridges.com/telecom-references/ss7-and-signalling/ss7/hsl.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.