For the complete documentation index, see llms.txt. This page is also available as Markdown.

Eseye connectivity overview

When you design and deploy your IoT devices, consider how data moves into your network. Consider your deployment options. Data movement depends on connectivity across the networks between the data source and its destination.

If you use AnyNet, connectivity can enable data flow across four network systems:

Data path from an IoT device through Eseye points of presence to a customer network
  • A — Device to ingress PoP: Data travels between the device, mobile network, and Eseye ingress Point of Presence (PoP).

  • B — Between Eseye PoPs: Data travels through Eseye's high-speed MPLS network.

  • C — Egress PoP to customer network: Data travels over the internet from the Eseye egress PoP to the customer network.

  • D — Within the customer network: Incoming data can be stored and used for business purposes.

As each customer network is different, we can only describe the first three sections of the data journey.

Last updated

Was this helpful?