> For the complete documentation index, see [llms.txt](https://docs.eseye.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eseye.com/anynet-sim/connectivity/section-a-connecting-over-the-mobile-network/section-b-connecting-over-eseyes-mpls-network.md).

# Section B – Connecting over Eseye's MPLS network

This section of topics unpacks the second part of the data journey between a device and the customer network.

Depending on your unique configuration, data either passes through the Eseye network or bypasses it altogether. This section describes how data passes through the Eseye MPLS network.

{% hint style="info" %}
Regardless of how data passes from a device to the customer network, Eseye provides the overall SIM management.
{% endhint %}

![](https://2995386447-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzlTL8FVu6GaQkB5i1TRY%2Fuploads%2Fjy8N7a59SytqckLcGPoW%2FConnectivity_NetworkOverviewSection2.png?alt=media)

For an overview of connectivity, see [Eseye connectivity overview](/anynet-sim/connectivity/eseye-connectivity-overview.md).

## About Multiple Protocol Label Switching (MPLS)

Multi-protocol Label Switching is a high-speed, protocol-independent networking technology that routes data traffic along preconfigured paths, to handle forwarding over private wide area networks. MPLS assigns labels to each data packet, rather than network addresses, to control the path each packet follows.

* **High speed** – data passing through an MPLS network is labelled and forwarded in packets along preconfigured pathways through the network. This has a faster handling time than other encapsulation methods, where the source and destination IP addresses are checked at every point in the data journey in order to decide where to send the data. The journey between points in the preconfigured path is called a *hop*.
* **Protocol-independent** – an MPLS network can handle data in any format, regardless of the connections used to send and receive it.
* **Preconfigured paths** – Eseye has set up the MPLS network between Eseye PoPs, which exist worldwide.

  For more information, see [About Eseye PoPs](/anynet-sim/connectivity/about-eseye-pops.md).

  Any data processed by the Eseye MPLS network ingresses at a preconfigured PoP. For operator locations, see [Mobile Network Operators by PoP](/anynet-sim/connectivity/mobile-network-operators-by-pop.md). The data then either egresses at the same PoP or travels in hops to another PoP before egressing to its destination.

  We can prioritise data in times of high traffic to ensure optimum connectivity for your devices.

  For information about egress data processing, see [Section C – Connecting over the internet](/anynet-sim/connectivity/section-a-connecting-over-the-mobile-network/section-c-connecting-over-the-internet.md).
* **Security** – Eseye encrypts all data that passes through the MPLS network. For more information, see [AnyNet security options](/anynet-sim/connectivity/security.md).

Eseye's MPLS network uses AWS cloud-based services for operation. It uses a combination of SDWAN and fiber optic technology for providing connectivity. The network is established as a mesh network to optimise availability.


---

# 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.eseye.com/anynet-sim/connectivity/section-a-connecting-over-the-mobile-network/section-b-connecting-over-eseyes-mpls-network.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.