Rectifiers, batteries, gensets, cooling and door controllers at thousands of cell sites and edge locations report through a patchwork of vendor EMS tools and SNMP pollers. Publish them to one MQTT broker for your NOC — and give enterprise customers their own private broker for the IoT services you sell.
No card required
Rectifiers, battery strings, gensets, cooling and access control report to different EMS tools, often via SNMP polling. The NOC sees radio alarms in the OSS, but not why a site is running on battery.
Most sites have no staff and share backhaul with traffic. Truck rolls are expensive, so field ops needs fuel level, battery runtime and door events before anyone is dispatched.
Customers buying IoT connectivity increasingly expect a platform too. Building and operating a broker for every customer project ties up engineers who should be working on the network.
ConnectMQ runs private, isolated MQTT broker instances: your network team gets one place for site telemetry, and your enterprise business can offer brokers to customers without operating them.
Each broker is a private instance — one for your site estate, and separate ones per customer project if you need them. No clustering, scaling or patching for your team.
Every site controller or gateway authenticates with its own username and password over TLS, and per-topic ACLs keep regions, tower tenants and contractors to their own topics.
Site gateways publish when a value changes over one outbound connection. Retained state gives the NOC every site’s current status as a dashboard opens; persistent sessions ride out backhaul drops.
Threshold rules on battery voltage, fuel level or shelter temperature, and Last Will for gateways that go silent, trigger alerts and notifications — your OSS and ticketing take it from there.
Operators usually start with site power and environment monitoring, then reuse the same broker pattern for edge data centers, energy reporting and the IoT platforms they offer to enterprise customers.
Base station sites, rectifiers and batteries, shelter HVAC and CPE/edge devices reporting live over MQTT
Explore the use caseManaged MQTT brokers that telcos, MVNOs and integrators offer alongside IoT SIMs
Explore the use casePDU, UPS, cooling and rack sensor data for your DCIM and NOC
Explore the use caseSub-metered energy per site, line and asset, with peak-demand alerts in real time
Explore the use casetelco/north/site-2241/power/battery
telco/north/site-2241/genset/fuel
telco/north/site-2241/alarms
telco/north/site-2241/status (retained)Put a small gateway or site controller at each site that reads the rectifier, battery and genset controllers (often over Modbus or SNMP locally) and publishes to topics such as telco/{region}/{site}/power/battery. Your NOC dashboard subscribes per region, and ConnectMQ rules raise alerts when battery voltage or fuel level crosses a threshold.
SNMP is still how many network elements are managed, and it works well locally. For site infrastructure across thousands of locations, MQTT adds publish-on-change, one outbound TLS connection per site instead of central polling, retained last state and any number of subscribers. Many operators keep SNMP at the site and bridge to MQTT in the gateway.
Yes — it is a common way to add a platform to IoT connectivity. With ConnectMQ you can run a separate private broker instance per customer or project, each with its own credentials, ACLs and dashboard, on the Basic or Scale plan to match. Your customer portal and billing stay in your BSS.
MQTT was designed for constrained, unreliable links. Keep-alives detect dead connections, persistent sessions and QoS 1 deliver queued messages after a reconnect, and Last Will tells subscribers when a site gateway has gone silent. Payloads are small, so site telemetry adds little load to the backhaul.
Start on the Free plan — no card required. Connect a cluster of sites to your NOC, then move to Basic or Scale when you go live. No overage charges, cancel anytime.
