Tokenised 6G Site — ARPU Calculator (India)

Companion to Tokenisation of Future 6G Assets as a Strategy to Improve ARPU for Operators. Every assumption is an input — all on a per-hour, typical urban site basis. Your subscriber base and your own network use stay fixed — enter your own figures once, then play with the token assumptions and watch the revenue change. Demand splits across eMBB, URLLC, mIoT slices (mix from the RANSlice twin). All figures in ₹.

Your network — fixed (your figures, held constant)

Subscribers on site Current ARPU (₹/month, TRAI ~191) Data per sub (GB/month, TRAI 25.5) Annualised site cost (₹ lakh/yr)

Token assumptions — play with these

Site type (sets coverage, price & spectrum)

Stream 1 — Shared radio & spectrum

Buyer bandwidth (MHz) Coverage (km²)

Hours per day Days per year Base price (₹/MHz·hr·km²) Seller cost (₹/hr)

eMBB % mult

URLLC % mult

mIoT % mult

Stream 2 — Edge compute (GPU-hours)

Sellable GPU-hours / day Days per year Wholesale share (GPU-hrs/day) Wholesale price (₹/GPU-hr) VMs per GPU-hour VM utilisation % VM price (₹/VM-hr) Power+mgmt (₹/GPU-hr)

Revenue table (per month)

New revenue stream (outside ARPU)

Reading the model

Slice shares re-weight the Stream-1 price (URLLC premium for latency, mIoT discount for bulk). Stream 2 is the thinner-evidence stream: GPU utilisation and VM pricing are reasonable assumptions, not measured data. Personal VMs complement handset AI (needed anyway for latency/privacy/offline) and are billed separately. All prices are assumed until a registry publishes cleared prices — the claim is the margin of clearance.