Section A – Connecting over the mobile network

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

For an overview on Connectivity, see Eseye connectivity overview.

About the AnyNet solution

The AnyNet solution provides access to mobile networks across the world. Devices connect on whichever mobile network provides the best connectivity for their location and requirements. The AnyNet Connectivity Management Platform (CMP) can use steering of roaming and IMSI switching to connect to different mobile networks in order to maintain optimum connectivity between a device and the customer network.

The AnyNet solution provides cellular connectivity in the following countries:

Americas Europe Africa Asia Middle East Oceania
Anguilla Panama Austria Latvia Burundi Azerbaijan Israel Australia
Antigua and Barbuda Peru Belgium Liechtenstein Democratic Republic of Congo China Kuwait New Zealand
Barbados Puerto Rico Bulgaria Lithuania Ghana Hong Kong Qatar  
Brazil St Kitts And Nevis Croatia Luxembourg Kenya Japan Saudi Arabia  
Canada St Lucia Cyprus Malta Lesotho Malaysia    
Cayman Islands St Vincent And The Grenadines Czech Republic Monaco Malawi Taiwan    
Chile Turks and Caicos Islands Denmark Netherlands Mozambique Thailand    
Colombia United States Estonia Norway Namibia      
Dominica Virgin Islands (U.S.) Finland Poland Rwanda      
El Salvador   France Portugal South Africa      
French Guiana   Germany Romania Kingdom of Eswatini (Swaziland)      
Grenada   Gibraltar Slovakia Tanzania      
Guadeloupe   Greece Slovenia Uganda      
Jamaica   Hungary Spain Zambia      
Martinique   Iceland Sweden Zimbabwe      
Mexico   Ireland Switzerland        
Montserrat   Italy United Kingdom        

Understanding data movement

Data needs a direction of flow, and as such it needs to know where it has come from (the source) and where it is going to (the destination). Direction of flow is determined on a device level (for example, the device needs to know which mobile network it can connect to) and network level (for example, the mobile network needs to know which TCP/IP network to connect with).

Configuring a device for the mobile network

Configuring a device to access the correct network

Before an IoT device can send data, it must first get permission to use a mobile network.

All SIMs contain unique numbers that the network uses to identify the SIM, the subscriber, and the home network. The modem also contains a unique identifier.

Every customer device must also contain the Eseye network Access Point Name (APN) details. The APN that the customer must use is detailed in the customer contract. For more information, see Current AnyNet APN list.

When the device requests to connect to a mobile network, the network operator uses the SIM and device unique identifiers, as well as the APN details, to authenticate the device via a Packet Gateway (PGW).

For the sake of simplicity, the image below depicts the Packet Gateway (PGW) between the Eseye and MNO networks. However, the PGW will actually exist within either network, depending on the agreed configuration between Eseye and the MNO.

The current IMSI determines which mobile network the device uses. This means that data sent from a device may ingress the Eseye network at different PoPs, depending on the current IMSI (and therefore the MNO). For more information, see About Eseye PoPs.

If the device is roaming, the data will ingress the Eseye network using the home mobile network. For more information, see Understanding roaming.