Frequently Asked Questions
What counts as a ‘device’ in this category, beyond smartphones?
It spans smartphones, tablets, wearables like smartwatches and fitness trackers, mobile hotspots, IoT sensors deployed across industries from agriculture to manufacturing, connected vehicles, fixed wireless access routers used for home and business broadband, and increasingly, AI-capable hardware designed to run machine learning models directly on the device. Each device category has different priorities: a smartphone needs to balance performance, battery life, and broad consumer features, while an industrial IoT sensor might prioritize extremely low power consumption and a multi-year battery life over raw performance, and an enterprise device built for a private 5G network might prioritize certified protocol compatibility and ruggedized durability over consumer-friendly design.
Why does device support matter for new network technologies like 5G Standalone or network slicing?
Even if a network supports a capability, like dynamic network slicing or a specific 5G Standalone feature, customers can’t actually use it unless their device’s chipset, modem, and software also support that capability, which often lags meaningfully behind network rollout. Chipset manufacturers need time to design, test, and certify support for new network features, and device manufacturers then need to integrate those chipsets into actual products and release them to market, a process that can take a year or more after a network feature first becomes available. Device readiness is frequently the real bottleneck determining how quickly new network capabilities translate into a noticeably different experience for everyday users.
What’s driving demand for ruggedized or purpose-built enterprise devices?
Standard consumer smartphones are generally designed for everyday consumer environments and aren’t built to handle the physical conditions, security requirements, or specific network protocols many enterprise and industrial deployments require. Manufacturing floors, mining operations, ports, and outdoor industrial sites often expose devices to dust, moisture, extreme temperatures, and physical impact that consumer-grade hardware isn’t rated to withstand reliably over time. Beyond physical ruggedness, enterprises increasingly need devices specifically certified to work with private 5G network protocols, dedicated security requirements, or specialized application software, creating a distinct market for ruggedized, enterprise-focused devices from manufacturers who specialize in industrial and field-service hardware.
How is AI changing what we expect from connected devices?
Devices are increasingly expected to run AI processing locally, known as on-device inference, rather than sending every request to a cloud server for processing. This reduces latency, since results don’t need to travel to a distant data center and back, and it can improve privacy, since sensitive data doesn’t necessarily need to leave the device at all. However, on-device AI requires meaningfully more capable chipsets than older devices needed, since running AI models locally demands processing power and memory simpler, lower-cost devices may not have. This is driving tighter coordination between chipset makers, device manufacturers, and network operators.
Why do some phones get 5G features faster than others, even on the same network?
Even on the same underlying network, different phones can support meaningfully different real-world 5G performance because of differences in their specific modem chipsets, the particular frequency bands those chipsets support, and how well each device’s software has been optimized to take advantage of available network features. A phone with a more advanced or recently released modem might support carrier aggregation across more frequency bands simultaneously, or be certified for 5G Standalone features that an older or lower-cost device’s modem simply can’t process, even if both phones are technically labeled as 5G phones. Marketing labels alone don’t guarantee equivalent performance.
What’s the difference between a consumer device and an IoT device in terms of design priorities?
Consumer device design generally prioritizes a balance of performance, battery life, screen quality, and broad appeal, with relatively frequent product refresh cycles to stay competitive in a crowded market. IoT device design tends to prioritize very different things: extremely low power consumption to support battery life measured in years, low manufacturing cost to make large-scale deployment of thousands or millions of units economically viable, and a narrow, specific function rather than broad general-purpose capability. An IoT sensor monitoring soil moisture in agriculture doesn’t need a high-resolution display; it needs to reliably transmit a small amount of data for years on a single battery charge.
How long does it typically take for a new network capability to reach mainstream devices?
The timeline varies considerably, but it’s common for a meaningful gap, often a year or more, to exist between when a network feature first becomes technically available and when it reaches a meaningful share of mainstream devices in active use. Flagship devices released around the same time as a new network capability typically support it fastest, since manufacturers often coordinate development timelines with major network milestones. Mid-range and budget devices generally lag further behind, both because manufacturers prioritize newer chipsets in premium products first, and because many consumers keep mid-range and budget devices for longer before upgrading.
What role do device makers play in network standards development?
Device makers, particularly major chipset manufacturers like Qualcomm and MediaTek, participate directly in standards bodies such as 3GPP, contributing technical expertise and influencing which features make it into a given network generation’s specifications. This involvement matters because standards need to reflect what’s actually feasible to build into real hardware within a reasonable cost and power budget, not just an idealized technical capability no chipset could practically support. Device makers also often run early interoperability testing with network equipment vendors before a standard is finalized, helping ensure compatible devices can realistically follow soon after a standard is specified.
