IoT 5G Router: Connecting Machines, Chargers, Kiosks and Sensors

People connections and machine connections have different priorities. A person will notice slow speed and complain. A machine will quietly stop sending data, and nobody will notice until a report is missing or a customer rings. IoT routers are built around that difference. Reliability, recovery and remote visibility matter far more than headline throughput.

IoT router, M2M router, gateway: what is the difference?

The terms overlap. In practice:

• M2M router is the older term, used for cellular routers connecting machines, often over serial or Ethernet.
• IoT router is the same idea with more emphasis on cloud platforms, protocols such as MQTT, and large-scale management.
• IoT gateway usually implies the device also collects and processes data itself, for example reading Modbus devices and publishing values to a cloud platform, rather than just passing traffic.

Many modern industrial routers do all three, with the gateway functions built into the operating system.

Typical IoT applications

Is 5G needed for IoT?

For many applications, not for the data itself. A vending machine sending sales data and taking card payments needs a tiny fraction of what 4G can carry. The case for 5G in IoT rests on other things:

Device lifetime. If the device will be in service for ten years, network support over that period matters more than speed today.

Applications that grow. Signage that starts with static images moves to video. A charger that sends status messages starts receiving large firmware updates. A remote site adds a camera.

RedCap. 5G RedCap gives IoT devices a 5G option with cost and power closer to 4G. It needs standalone 5G. See our RedCap guide.

Standalone features. Power saving, network slicing and more consistent latency all arrive with SA. See 5G SA routers.

For the very smallest devices, LTE-M and NB-IoT remain the right technologies. They are designed for battery devices sending small messages and have long-term support plans on UK networks.

SIMs for IoT routers

IoT deployments usually use specialist IoT SIMs rather than standard business SIMs. Common features include:

• Multi-network access. The SIM can use more than one UK network, so each device connects to whichever is strongest at its location.
• Pooled data. Data is shared across all SIMs, so a busy device and an idle device balance out.
• Private APN. Devices connect directly to your network with private IP addresses, never touching the public internet.
• Management portal. Activate, suspend, monitor and diagnose SIMs centrally.
• eSIM or eUICC. The network profile can be changed remotely, avoiding SIM swaps if you change provider. See eSIM in 5G routers.

Gateway features worth having

Modern IoT routers often include data handling features that save adding a separate gateway:

• Modbus TCP and RTU polling, with values published to a cloud platform
• MQTT client and sometimes a local broker
• Data buffering when the connection drops, then upload when it returns
• Support for container or package installs to run custom code
• Integration with common cloud IoT platforms
• GNSS for location tracking on mobile assets

Managing thousands of devices

At IoT scale, almost everything happens remotely. You need:

Zero touch provisioning. A router arrives at site, powers up, connects to the management platform and pulls its configuration automatically. No engineer configures it by hand.

Staged firmware updates. Update a small group first, check for problems, then roll out to the rest.

Alerts and dashboards. Know when devices go offline, when signal quality drops or when data use spikes unexpectedly.

Remote access to the router. To diagnose a problem without travelling to site.

Ask how the management platform is priced, whether there are free tiers, and how easy it is to export configurations if you ever move away from it.

Power and size

IoT devices often have tight power and space budgets. A full 5G router can draw several times more power than a 4G Cat 1 device, which matters on battery or solar. Check typical and peak consumption, and whether the router supports power saving modes. Compact routers and modules are available for embedding in equipment such as chargers and kiosks.

Worked example: a network of EV chargers

EV charging is a good illustration of how IoT connectivity decisions play out. Each charger needs to talk to a back office platform, usually over OCPP, to authorise sessions, report energy use and receive tariff and firmware updates. Card payment terminals in the charger need their own secure path. The operator wants to see which chargers are offline before drivers start complaining on social media.

The data per charger is modest, so raw speed is not the issue. Reliability is. Chargers sit in car parks, retail sites and roadside locations where coverage varies and fixed lines are rarely available. A common design is a small 4G or 5G router per site, or one per charger cluster, using a multi-network IoT SIM on a private APN. The private APN keeps the chargers off the public internet and gives the back office platform a predictable address for every site. Pooled data covers the occasional large firmware download.

The router’s management platform watches signal and connection status. If a site drops, the platform alerts operations, who can see straight away whether the problem is coverage, power or the charger itself. That saves a lot of wasted engineer visits.

Why choose 5G for something that moves so little data? Mostly lifecycle. Charging hardware is expected to stay in service for many years, and operators do not want to replace thousands of routers because the networks have moved on. RedCap is increasingly attractive here as it matures.

Common IoT router failure modes

Most IoT connectivity problems fall into a small number of patterns, and good router configuration prevents most of them:

• Registered but not passing data. The router shows signal and thinks it is online, but traffic is going nowhere. A connectivity health check with automatic modem restart fixes this.
• SIM suspended. The SIM was suspended for inactivity, non-payment or a portal mistake. Monitoring that alerts on connection failure catches it quickly.
• Data runaway. A device starts sending far more than normal, often after a firmware change. Usage alerts and caps protect the bill.
• Power problems. Brownouts or unstable supplies cause reboots and corruption. A clean DC supply and a small buffer battery solve many mystery faults.
• Antenna damage. Vandalism, weather or a forklift. Signal history in the management platform shows a sudden step change that points straight at it.

Security for IoT routers

IoT devices are often deployed in public places, unattended, for years. That makes security important:

• no default passwords, ideally unique credentials per device
• no management interfaces exposed to the internet
• signed firmware and a supplier with a security update track record
• private APN or VPN rather than public IP addresses where possible
• network segmentation so a compromised device cannot reach others

Upcoming UK and EU product security rules are also raising the bar for connected devices, which is a good reason to choose manufacturers who take updates seriously.

Planning for the end of life

IoT deployments are often planned around installation and forgotten after that. It is worth deciding up front how long the devices are expected to run, how they will be updated over that time, and what happens when they are replaced. Keep an asset register with router serial numbers, SIM identifiers and installation dates. Budget for a refresh cycle. And when devices are retired, remove their SIMs from billing, revoke their VPN credentials or certificates, and wipe their configurations, so a router pulled from a skip does not still have keys to your network.

Choosing an IoT 5G router

1. Work out real data needs per device, now and in five years.
2. Decide between full 5G, RedCap and 4G based on data, power and lifetime.
3. Choose the SIM strategy: single network, multi-network, private APN, eSIM.
4. Confirm interfaces: Ethernet, serial, I/O, Wi-Fi, GNSS.
5. Check management platform features and pricing at your scale.
6. Pilot in real locations before ordering in volume.

For help choosing hardware and SIMs for an IoT rollout, email sales@5grouter.co.uk.