Static private IPs
Each SIM can receive a predictable address from the client's private range.
Private device connectivity
A private M2M APN for automation and distributed sites
A separated cellular network for controllers, routers and metering devices. Traffic stays off the public internet and devices receive static private IP addresses.
Essentials
What is a private M2M APN?
An APN defines how a SIM card enters a mobile data network. In a private setup, client devices operate in a separated address space that cannot be reached directly from the internet.
IoT M2M provides static private IP addresses, controlled routing and a connection to either the monitoring platform or the client network. PLCs, HMIs and data loggers therefore need no public open ports.
No public exposure
Inbound internet traffic cannot reach the field devices directly.
One network for the fleet
Consistent addressing and access rules across all site locations.
Architecture
How do APN and MPLS connectivity work?
A device connects to the mobile network through an M2M SIM. The operator gateway routes traffic into the private APN and then over a private MPLS link to BREPO infrastructure.
Traffic can then reach the IoT M2M platform or the client network through an agreed VPN tunnel. Routing and access rules are defined for each deployment.
- A router or modem establishes a data session through an M2M SIM.
- The private APN assigns a static private IP address to the device.
- MPLS carries traffic to BREPO without entering the public internet.
- The platform or client network exposes only the approved services and devices.
Choosing the design
Private APN, VPN and public IP serve different roles
A private APN separates device routing and addressing. A VPN encrypts and authenticates a connection between agreed endpoints. A static public IP enables internet reachability, but requires additional protection and is unnecessary in a typical IoT M2M deployment.
BREPO selects the design after reviewing devices, protocols, locations and integration requirements. Operator status is listed in the UKE register under no. 13575, and LIR membership on the RIPE NCC member list.
FAQ
Frequently asked questions
Is a private APN the same as a VPN?
No. An APN separates mobile routing and addressing, while a VPN provides an encrypted tunnel between endpoints. The two mechanisms can work together.
Does a device need a public IP address?
No. With IoT M2M, a device can use a static private IP and remain off the public internet.
Can one APN support many sites?
Yes. One private network can cover a fleet of SIMs and devices in many locations, with agreed segmentation and access rules.
How is the APN connected to the client network?
Through private connectivity and an agreed VPN tunnel or another carrier design, depending on project requirements.
Contact
Let's discuss your deployment
Show us the devices, locations and access workflow. We will prepare the connectivity and monitoring design for the first site.
Ask about a demo- E-mailiotm2m@iotm2m.pl
- Phone+48 32 720 20 60
- Addressul. Ks. Fr. Górka 144
43-196 Mikołów