# What this dispute is about TRAI proposed draft amendments covering 5G network slicing, coverage map accuracy and financial penalties for missing service-quality benchmarks. The regulator suggested limiting radio resource usage in cells where slicing is active, proposing an 80% utilisation cap so operators keep headroom for specialised slices.
# Where telcos stand Bharti Airtel and Reliance Jio told TRAI at an open house that the 80% cap is technically inappropriate. Their main points:
- 5G slicing is an architectural capability. Regulatory intervention should follow only when a customer-facing problem appears, not pre-emptively.
- Current 5G deployments often reuse the same network resources and can push effective cell capacity beyond 100% without degrading user experience. An internal utilisation metric therefore may not map to real consumer outcomes.
- Measuring capacity utilisation in sliced areas is an engineering parameter, not a direct proxy for service quality perceived by users.
- Implementing TRAI's proposals requires significant changes — IT architectures, data pipelines, geospatial platforms, customer service systems and cross-functional procedures — and telcos said the regulator's proposed effective start date is unachievable.
# Where consumer groups and public-interest voices stand Consumer Care Society and other consumer groups backed keeping the 80% utilisation benchmark. Their rationale:
- The benchmark creates regulatory pressure on operators to augment capacity where cells are chronically overloaded.
# Industry technical interest groups Forum (BIF) took a middle path. BIF said network slicing can be compatible with India's net neutrality framework if deployments are transparent and non-discriminatory. At the same time, BIF strongly opposed allowing differential connectivity tied to specific use-cases (for example paid prioritisation for gaming or live streaming), arguing that would violate net neutrality principles.
# Practical implications if TRAI keeps the 80% rule
- Operators would need continuous, cell-level measurement of resource utilisation where slicing is enabled.
- Network planning and capital allocation might shift toward more aggressive capacity upgrades where utilisation repeatedly breaches the cap.
# Practical implications if TRAI drops or relaxes the rule
- Regulators would be relying more on complaint-driven enforcement and customer-experience metrics rather than engineering headroom limits.
- Operators could continue to use internal resource sharing and dynamic reuse practices without a hard utilisation ceiling.
# What TRAI heard at the open house At the public session, telcos emphasised implementation complexity and timeline infeasibility. Consumer groups emphasised the need for enforceable limits to prevent chronic congestion. BIF and MediaNama pressed for clarity on how slicing would be implemented without breaching net neutrality.
# What to watch next Watch for TRAI's final decision on the 80% utilisation cap, any adjustments to implementation timelines, and whether the regulator adds consumer-facing outcome metrics alongside engineering thresholds.