Diameter Bandwidth vs DRA Dimensioning
One tool forecasts interface traffic; the other turns that traffic into DRA node counts.
Start with Diameter Bandwidth (and S6a/Gy models) to estimate peak TPS and Mbps. Feed those peaks into DRA Dimensioning with vendor per-node ratings and N+1/geo redundancy. Skipping the traffic step produces arbitrary node counts.
Diameter Bandwidth
Estimates peak Diameter TPS and approximate bandwidth from subscriber events and interface mix.
Best for
- ▸S6a/Gx/Gy interface forecasts
- ▸Firewall and link capacity
- ▸Inputs to DRA and OCS planning
DRA Dimensioning
Converts peak TPS into Diameter Routing Agent instance counts with redundancy and binding headroom.
Best for
- ▸DRA BOM and license counts
- ▸N+1 / geo-redundant layouts
- ▸VoLTE binding-aware peaks
How to choose
Never dimension DRA from subscriber count alone. Derive TPS first (bandwidth/S6a/quota tools), then apply DRA ratings. If charging grant policy changes, re-run bandwidth before touching DRA count.
FAQ
Is DRA the same as HSS capacity?
No. DRA routes; HSS/OCS/PCRF terminate applications. Size each tier separately.
Where does S6a modeling fit?
S6a Traffic Modeler feeds Diameter Bandwidth for MME–HSS load, then DRA.
What about HTTP SBI in 5GC?
Analogous service mesh sizing replaces classic DRA for many SA interfaces—use 5GC dimensioning for NF scale.