MIOTY Alliance Launches Software LPWAN at Embedded World, Adds Fifth Protocol to IoT Stack
MIOTY Alliance positioned ETSI-compliant protocol for massive IoT at Embedded World, creating another LPWAN choice alongside LoRaWAN, NB-IoT, and LTE-M without published deployment data or pricing.
MIOTY enters LPWAN market with software-based protocol
The MIOTY Alliance launched a software-based LPWAN protocol at Embedded World this week, positioning it as an alternative for massive IoT deployments. The ETSI-compliant protocol joins LoRaWAN, NB-IoT, LTE-M, and Sigfox in a fragmented low-power wide-area network market, but the alliance published no pricing, device-count targets, battery-life measurements, or customer deployment figures.
The software-based approach differentiates MIOTY from cellular LPWAN standards while competing directly with LoRaWAN's mature ecosystem. LoRaWAN claims over 200 million connected devices and broad sensor manufacturer support. NB-IoT and LTE-M benefit from existing cellular operator infrastructure and spectrum allocations. MIOTY's value proposition centers on ETSI compliance and software implementation rather than new radio technology, but without quantitative comparisons, buyers cannot assess trade-offs in coverage, battery life, or gateway density.
Enterprises evaluating MIOTY should treat this as a vendor-watch signal rather than a procurement trigger. The absence of gateway availability data, certified device volume, spectrum licensing detail, and interoperability test results makes apples-to-apples comparison impossible. Buyers considering pilot deployments must require proof of regional spectrum support, published battery-life benchmarks under realistic workloads, module pricing with volume tiers, and migration cost estimates from existing LoRaWAN or cellular LPWAN estates.
Microsoft consolidates MQTT and industrial protocols in Azure IoT Operations
Microsoft documented support for MQTT 3.1.1 and MQTT 5 in Azure IoT Operations, adding connectors for OPC UA, ONVIF, REST, SQL, and media-streaming protocols. The platform can handle tens of thousands of MQTT clients per broker, positioning Azure against AWS IoT Core, HiveMQ, EMQX, and Siemens Industrial Edge.
The move reduces protocol gateway requirements for enterprises managing mixed industrial estates. A manufacturer running OPC UA on production lines, ONVIF on security cameras, and MQTT on environmental sensors can consolidate edge data flows without custom integration code. Microsoft's differentiator is the combination of MQTT brokering with industrial and video protocol support rather than reliance on a single device standard.
However, Microsoft has not published Azure IoT Operations pricing, broker throughput benchmarks, maximum supported device counts under specified workloads, or connector general-availability dates. Buyers cannot model total cost of ownership or performance against HiveMQ Enterprise or EMQX Enterprise without those figures. Existing Azure customers should request pricing for their anticipated device count and message volume before committing to architecture changes.
GSMA eSIM standards create five-year multi-standard migration burden
GSMA's three eSIM specifications — SGP.02 for machine-to-machine, SGP.22 for consumer devices, and SGP.32 for IoT — will coexist for at least five years, according to connectivity management platform provider Eseye. SGP.32 uses an IoT Profile Assistant and remote eSIM IoT Manager but is not yet widely deployed, leaving global fleet operators managing three incompatible standards simultaneously.
SGP.02 remains entrenched in existing M2M deployments. SGP.22 dominates consumer smartphone implementations. SGP.32 offers operator-independent profile management but lacks broad device support and operator coverage data. The result is a migration timeline measured in years rather than quarters, with enterprises bearing the cost of dual- or triple-standard device management.
Buyers deploying global connected-device fleets should specify support for all three standards in procurement requirements. Include remote profile switching, device-side IoT Profile Assistant support, eSIM-manager interoperability testing, and migration tooling in RFPs. The lack of published implementation costs and per-operator coverage maps means the financial case must be modeled per fleet size and geography rather than assumed from vendor claims.
What to watch
The pattern this week is protocol fragmentation rather than consolidation. MIOTY adds a fifth LPWAN option without displacing incumbents. Microsoft adds MQTT and industrial protocol support without sunsetting existing connectivity paths. GSMA's eSIM standards multiply rather than simplify fleet management requirements.
Buyers should prioritize interoperability proof over vendor ecosystem claims, published benchmarks over marketing performance assertions, and migration cost models over greenfield deployment promises. Protocol choice matters less than the ability to change protocols without replacing hardware — a capability few vendors document and fewer still deliver.
Technology decisions, clearly explained.
Weekly analysis of the tools, platforms, and strategies that matter to B2B technology buyers. No fluff, no vendor spin.
