Bug #1654
closed
Added by laforge about 8 years ago.
Updated almost 8 years ago.
Description
- TBF establishment success rate (%) =
missing it's 100 % because those can not fail
- TBF completion rate (%) = 1 - (tbf.dl.aborted + tbf.ul.aborted) / (tbf.dl.alloc + tbf.ul.alloc)
- GPRS DL and UL (for GPRS)
- overall throughput (kbps) = rlc.dl_bytes + rlc.ul_bytes
- TBF attempts (number) = tbf.dl.alloc tbf.dl.alloc
- payload througput (kbps) = rlc.dl_payload_bytes + rlc.ul_payload_bytes
- radio block utilization (%) = (1 - (rlc.sent_dummy / rlc.sent)) g85
EGRPS counters moved to a seperate ticket #1766
- Related to Bug #1652: Expose statistics / KPIs programmatically added
- Status changed from New to In Progress
laforge wrote:
- GPRS DL and UL (for GPRS and EGPRS separately)
- overall throughput (kbps)
as determined on the layer boundary between MAC and PHY, i.e. all bits that are not padding bits
payload == LLC frame including LLC header, excluding RLC/MAC headers
- radio block utilization (%)
at boundary between PCU and PHY socket (or OsmoBTS socket), where ready-to-send requests are being responded.
- radio block utilization (%)
determed by rlc_sent_dummy and rlc_sent packages.
- Description updated (diff)
- Description updated (diff)
- when can a TBF alloc fail? is this even possible (for osmopcu)?
- Description updated (diff)
- % Done changed from 0 to 90
- Description updated (diff)
- Related to Bug #1766: KPIs for OsmoPCU: EGPRS added
- % Done changed from 90 to 100
- Status changed from In Progress to Resolved
- Status changed from Resolved to Closed
Also available in: Atom
PDF
