TR-069 Inform data budget calculator

Estimate ACS traffic on metered LTE, satellite or slow backhaul. Compare Inform intervals and parameter reads before choosing a fleet policy.

Free, no signup. Calculations stay in your browser; no inputs are sent or saved.

Your fleet and assumptions

Whole devices; zero shows per-device estimates only.

900 seconds = 15 minutes. Periodic Inform is assumed enabled.

Assumption: 10,000 bytes, both directions, including session overhead.

Assumption: 20,000 additional bytes per request/response exchange.

Optional: 0 disables. 24 means hourly; fractions model less than daily.

Each request adds one separate Inform session in this estimate.

Assumption: 2,000 bytes for the request exchange, before the Inform session.

Use your billed decimal-GB rate; no exchange-rate conversion.

For example USD, KES, EUR or your local currency.

Estimated budget

Bytes per CPE per day
960,000
Bytes per CPE per 30-day month
28,800,000
Fleet GB per month
28.8
Monthly backhaul cost
28.8 USD
Approximate offline-detection delay
30 minutes

Delay assumes an ACS policy of two missed intervals since the last Inform. It is not a TR-069 guarantee or a measured ISPAgents alert time.

Moderate planning band: 10 to below 100 MB per CPE per month. Compare a longer Inform interval and fewer parameter reads against your support needs.

Bands are worksheet heuristics, not protocol limits. A light per-device budget can still be costly across a large fleet.

Daily bytes per CPE by source

  • Periodic Inform: 960,000
  • Parameter reads: 0
  • Connection requests + extra Informs: 0

Formula and assumptions

Daily bytes per CPE = (86,400 ÷ Inform interval in seconds × Inform session bytes) + (parameter reads per day × parameter exchange bytes) + (connection requests per day × (request overhead bytes + Inform session bytes)).

Monthly bytes per CPE = daily bytes × 30. Fleet GB per month = monthly bytes × CPE count ÷ 1,000,000,000. Monthly cost = fleet GB × your cost per GB. Approximate detection delay = 2 × Inform interval.

Defaults are assumptions, not measurements: 1,000 CPEs, a 900-second interval, 10,000 bytes per complete Inform session, 20,000 bytes per GetParameterValues exchange, and 2,000 bytes per connection-request exchange. Optional reads and connection requests default to zero; the initial rate is 1 currency unit per GB. All sizes count both directions.

Include HTTP, TLS, TCP/IP and link overhead in your measured session sizes. Parameter reads are additional exchanges within budgeted sessions. A read that opens another session needs a corresponding connection request. This model assumes each connection request succeeds and starts one extra session, without overlap with periodic Informs.

Fractional daily frequencies are long-run averages. Retries, loss, authentication challenges beyond your size estimate, reboot/value-change Informs, NAT keepalives, firmware downloads, backups, diagnostics and other RPC traffic are excluded. Slow backhaul can also suffer bursts: this monthly average does not estimate peak throughput or session concurrency. Capture representative device traffic before committing to a paid data plan.

The Broadband Forum management data model defines periodic Inform and connection-request settings. It does not prescribe these byte assumptions, planning bands or a two-interval offline policy.

Using this with ISPAgents

ISPAgents supports TR-069/CWMP Informs, parameter reads/writes and diagnostics. The platform ACS traffic advisor is planned and is not shipped. This standalone worksheet does not measure ACS traffic or change device settings.

Check TR-069 device compatibility before a model-specific rollout.