Allocate a 5G small-cell application's round-trip latency target across radio access, transport and core, application processing, and jitter margin. The calculator totals the planned components, identifies the largest contributor, and shows whether the target still has room. It supports early edge-placement and transport decisions, while real percentile latency still needs measurement under representative load and radio conditions.
A positive main result is unallocated round-trip margin. Zero means every millisecond is assigned, while a negative result shows how far the component plan exceeds the target.
Use the same measurement direction for every input. This calculator expects round-trip milliseconds and does not include unspecified client or server work.
A 30 ms target with 6 ms access, 7 ms transport, 8 ms processing, and 4 ms jitter allowance allocates 25 ms. The remaining budget is 5 ms.
It is the target round-trip latency minus the entered radio, transport, processing, and jitter allowances. A negative value means the component plan exceeds the target.
Use round-trip values throughout this calculator. Mixing one-way and round-trip measurements makes the result invalid.
Variation can force buffering or create deadline misses. Reserving a jitter allowance keeps the design from consuming the entire target with average delay.
Not directly, but congestion and serialization can add delay when demand approaches capacity. Test the latency budget under realistic load.
It estimates a network budget from entered components. Client work, server execution, retries, and application logic may add delay outside this model.
| Variable | Meaning | Unit |
|---|---|---|
| Target | Maximum desired round-trip delay | ms |
| Access | Radio or local access path | ms RTT |
| Transport/core | Backhaul, core, and routed transport | ms RTT |
| Processing | Edge or application execution allowance | ms |
| Jitter allowance | Reserved variation margin | ms |