A segment per type
EV, vending, BMS and sensors get separate rules.
IoT devices
The machine, the charger and the building controller have a name on your network.
Sensors, controllers, vending machines, EV chargers, BMS and other M2M. This is the connectivity layer of a device fleet, not another portal and not the measurement-telemetry page or the meter pages.
ExampleExample: an office building with EV chargers in the garage, vending machines and a BMS. Each group has its own segment on the private APN. An illustrative scenario, not a client reference.
Several networks
Where one operator is not enough, a second SIM joins the same address plan.
Not telemetry
Industrial measurements, energy and water have their own pages.
What bounces off the edge
Small devices get a SIM “so that it works” and are left with a public address and with access to each other.
A SIM list, a private address, a segment per device type. The charger does not talk to the vending machine. Management is from headquarters, through the tunnel. On the roof or in the cabinet, a Peplink router where several SIMs and operators meet at one point.
Security
- No public IP.
- SIM binding and, where it is possible, IMEI binding.
- Segmentation and one management point at headquarters.
Scattered M2M grows the attack surface if it sits on the internet. Pulling it onto an APN shrinks that surface. It does not fulfil the statute.
Peplink · SpeedFusion · InControl 2 Starlink How it works
Request a proposal APN types and connection types +48 698 355 667