How to Choose the Right 5G IoT Module for Your Product

Selecting a 5G module for an IoT product isn’t as simple as picking the fastest modem on the spec sheet. The right choice depends on your application’s real-world data needs, the network architecture you’ll be deploying on, and a handful of hardware and certification details that are easy to overlook until they cause a redesign. This guide walks through the key questions to ask before you commit to a module.

Start With Your Actual Data Requirements, Not Peak Speed

The biggest mistake in module selection is shopping by headline throughput. A device that typically transfers 20–30 Mbps of telemetry gains nothing from a 7 Gbps modem — it just adds cost, power draw, and antenna complexity you don’t need.

Before comparing modules, work out:

• Average and peak downlink
• Average and peak uplink (often the more important number for cameras, sensors, and gateways that are constantly sending data upstream)
• Number of simultaneous data streams
• Firmware update size and frequency
• Expected bandwidth growth over the product’s lifetime

Once you know these numbers, you can sort modules into the right performance tier instead of defaulting to the most powerful option available.

5G RedCap vs. Full 5G NR

This is the first major fork in the road for most new designs.

5G RedCap (Reduced Capability, introduced in 3GPP Release 17) sits between LTE and full 5G. It trims down bandwidth, antenna count, and RF complexity compared to full NR, while still offering a meaningful step up from LTE — typically in the range of 200+ Mbps downlink with LTE fallback built in. It’s a strong fit when LTE is starting to feel limiting, but your product doesn’t genuinely need multi-gigabit speeds.

Full 5G NR makes sense when high throughput is core to what the product does — think multi-camera surveillance, edge AI gateways, industrial routers, or applications pushing large volumes of video or sensor data to the cloud in real time.

A simple gut-check: if LTE is becoming a bottleneck but full 5G would be overkill, RedCap is usually the more efficient, lower-cost path.

Match the Module to the Application

A few common categories and how they typically shake out:

• Industrial gateways sending telemetry, alarms, and diagnostics — often well served by RedCap.
• Routers and CPE — depends heavily on WAN throughput expectations and whether the product’s value proposition is “broadband-class” performance.
• Surveillance and video — look at actual encoded bitrate and uplink load. Event-triggered or moderate-resolution streams can work on RedCap; continuous multi-stream high-res video usually needs full NR.
• Edge AI / machine vision — if inference happens on-device and only results or metadata go to the cloud, RedCap can be enough. If you’re transferring raw imagery, large models, or training data, plan for full NR.

Network Architecture: SA, NSA, and LTE Fallback

Before locking in a module, confirm:

• Whether your target operators support 5G Standalone (SA), Non-Standalone (NSA), or both — NSA leans on existing LTE infrastructure, while SA runs on a native 5G core.
• Whether RedCap is commercially available on your target network. Not every operator marketing “5G” has RedCap live yet — this needs to be checked market by market, not assumed.
• What LTE fallback category the module supports, since most real-world 5G deployments still rely on LTE as a safety net for coverage gaps.

Getting this wrong after the PCB is finalized is one of the more expensive mistakes in cellular product design — validate network support early.

Don’t Treat GNSS, OS, and Interfaces as an Afterthought

A few other factors that belong in your initial selection criteria, not a later “nice to have” pass:

• GNSS — relevant for fleet, asset tracking, and any location-aware application. Worth evaluating alongside your cellular antenna plan, since both need to share PCB space and enclosure real estate.
• Onboard OS / application support — some modules support Linux-based environments (e.g. OpenWrt) capable of running application logic directly, potentially removing the need for a separate host MCU. This can meaningfully simplify your BOM if your workload fits.
• Interfaces — build an interface matrix (PCIe, USB, UART, GPIO, I2C, SPI, Ethernet, SGMII) against your actual data path before you shortlist modules, not after.
• Form factor — LGA suits compact, permanently soldered designs; M.2 suits designs that benefit from modularity or field serviceability.

RF, Antenna, and Power Planning

Antenna requirements scale with module capability — RedCap designs typically need fewer antennas than full NR, which can require more complex MIMO configurations. Map out cellular antenna count, GNSS antenna, band coverage, and required isolation before mechanical design is frozen, not after — a module can fit your enclosure physically while its RF requirements don’t.

Power and thermal budgets deserve the same early attention. A high-performance NR modem pulling peak transmit power continuously may exceed what your enclosure, battery, or power supply can comfortably support — especially relevant for battery-powered or passively cooled designs.

Certification and Global Deployment

If your product ships into multiple markets, build a simple matrix before choosing a module:

Country → Operator → LTE bands → NR bands → SA/NSA → Certification requirements

A module marketed with broad global band coverage doesn’t automatically mean it’s certified and compatible with every operator you plan to use. Regulatory approvals, carrier certification, and finished-device compliance all need to be checked for your exact module variant and deployment region — pre-certification helps, but it rarely removes every finished-product obligation.

The Bottom Line

Choosing a 5G IoT module is a systems decision, not a modem-speed comparison. Nail down your real throughput needs, decide between RedCap and full NR based on the application (not the marketing), confirm network and certification requirements for your target markets, and treat antenna, power, and interface planning as part of the selection process — not something to solve after the module is already chosen.

Getting this right early avoids the most common and costly outcome in cellular hardware design: a PCB respin because the module didn’t actually fit the product.

For a deeper technical breakdown of 5G RedCap vs. full 5G NR modules, see Cavli Wireless’s 5G IoT Module Selection Guide.

Need help specifying the right module for your project?

Get in touch for orders or any queries: sales@rfdesign.co.za / +27 21 555 8400

Courtesy of Cavli Wireless