Professional Documents
Culture Documents
GPRS Kpi
GPRS Kpi
GPRS METRICS
UL Drops / 10kbyte
DL Drops / 10 kbyte
UL Multislot Blocking
DL Multislot Blocking
DESCRIPTION
It shows the number of UL drops (mobiles lost) for every 10 kbytes of
data transferred.
It shows the number of DL drops (mobiles lost) for every 10 kbytes of
data transferred.
The number of rejections for UL resource versus the num,ber of
requests for the resource.
The number of rejections for DL resource versus the num,ber of
requests for the resource.
FORMULA
trf_27a
trf_28a
tbf_15
tbf_16
Payload (kbytes)
trf_47a
trf_27d
UL BLER (%)
DL BLER (%)
DL TBFs
UL TBFs
TBF Success
UL Drops / 10kbyte
DL Drops / 10 kbyte
UL Multislot Blocking
DL Multislot Blocking
DESCRIPTION
The percentage of active cells is determined via examination of the
available TCH (speech) and the available PDTCH (GPRS timeslots).
Similar concept with the call connection procedure. The most
quantitative factor is DL TBF (temporary block flow) establishments.
Many TBFs will be established to a single user while he is holding an
active session.
For the Uplink case, the UL TBFs established can also be used to
measure the number of "accesses". This factor is prone to Ghosting
and the number can be significantly higher than the DL TBFs for cells
with low traffic.
The TBF success rate is a measure of both UL and DL TBFs.
It shows the number of UL drops (mobiles lost) for every 10 kbytes of
data transferred.
It shows the number of DL drops (mobiles lost) for every 10 kbytes of
data transferred.
The number of rejections for UL resource versus the num,ber of
requests for the resource.
The number of rejections for DL resource versus the num,ber of
requests for the resource.
FORMULA
p_nbsc_packet_control_unit.nbr_of_dl_tbf
p_nbsc_packet_control_unit.nbr_of_ul_tbf
tbf_34
trf_27a
trf_28a
tbf_15
tbf_16
UL Requests
Upgrade Rejection
DL Allocation Met
Additional TSLs
Indicates the average number of additional TSLs that have been utilized
for GPRS. A high value would indicate that the dimensioning of the
ach_1
GPRS territory is not sufficient.
Payload (kbytes)
trf_47a
trf_27d
UL BLER (%)
DL BLER (%)
blk_22
trf_89
GPRS METRICS
DESCRIPTION
FORMULA
GPRS METRICS
Cell Availability
UL
DL TBFs
DL
UL TBFs
For the Uplink case, the UL TBFs established can also be used to
measure the number of "accesses". This factor is prone to Ghosting p_nbsc_packet_control_unit.nbr_
and the number can be significantly higher than the DL TBFs for
of_ul_tbf
cells with low traffic.
TBF Success
tbf_34
UL Drops / 10kbyte
trf_27a
DL Drops / 10 kbyte
trf_28a
UL Multislot Blocking
tbf_15
DL Multislot Blocking
tbf_16
UL Requests
Upgrade Rejection
DL Allocation Met
Additional TSLs
Payload (kbytes)
trf_90
DESCRIPTION
This KPI gives the total traffic through the SGSNs in the downlink as well as in the uplink direction. It
could also be taken from BSC counters, but since it is very likely that the necessary measurements are
running in all the SGSNs (and if they don't, it would be very easy to discover it), it is recommended to
base this KPI on the SGSN counters.
This KPI gives the total traffic for each defined area. It is based on BSC counters, which gives the traffic
for each cell. These figures are then mapped to the defined areas. The KPI gives the total of uplink and
downlink traffic (in Kbytes). It is on RLC level, but does not include RLC/MAC headers
GPRS Subscribers
This KPI gives the number of subscribers that have GPRS service enabled in their subscription.
Attached GPRS
Subscribers
This KPI gives the number of subscribers that are attached to the GPRS network.
This KPI gives the number of active PDP contexts in the GPRS network.
These KPIs gives the traffic (incoming and outgoing) for each APN. The counters in the NMS table
provide the average number of packets per second during the collection interval. This should then be
multiplied with the number of seconds in the collection interval (usually 15 minutes, ie 900 seconds, but
this is a setting in the GGSN). To convert from packets to bytes, it is necessary to know the packet size.
This requires logging in to the GGSNs via the Voyager tool and (for each APN) read the total number of
OUT bytes and total number of packets. From this, the packet size can be calculated. Note that the GGSN
counters seen by Voyager are initialized (wrap around) when they reach approximately 6.000.000.000.
IN
These KPIs gives number of PDP contexts that have been activated for each APN. The counters in the
NMS table provide the average number of PDP contexts which have been activated each second during
the collection interval. This should then be multiplied with the number of seconds in the collection
interval (usually 15 minutes, ie 900 seconds, but this is a setting in the GGSN).
These are the cells where no resources are available for GPRS because CSW has taken everything. If
timeslots are dedicated to GPRS, there should not be any GPRS blocking.
GPRS Upgrade
Rejection Ratio (Top-10
Cells)
These are the cells where some, but not enough, resources are allocated to GPRS. This indicator only
works in cases where CS traffic has not compressed the GPRS territory below the default settings..
trf_27d
trf_73d
rlc_61 + rlc_7a
rlc_8a + rlc_9a
UL BLER (%)
Uplink Block Error Rate. On cell level values of 100% can be met
due to MS not responding - this can occur due to ghosting.
DL BLER (%)
These are the cells where some, but not enough, resources are allocated to GPRS. This indicator is
Bad Multi-Slot Allocation mainly applicable in cases where CS traffic has compressed the GPRS territory below the default
(Top 10 cells)
settings (see also the previous sections). It calculates the ratio between requested resources and
allocation resources.
GB Interface Downlink
Congestion
GB Interface Uplink
Congestion (Top-10)
This KPI gives the congestion in the downlink direction (ie seen from the SGSNs perspective). The
counters are on PAPU level, which means that the specific Gb link that causes the congestion cannot
be identified. This KPI should be combined with the Gb load (section 5.3) to identify the most probable
link.
This KPI gives the congestion in the uplink direction (ie seen from the BSCs perspective). The
counters are on link level, which means that the specific Gb link that causes the congestion can easily
be identified. The congestion is then given as the number of bytes that has been discarded due to
congestion, ie it is not a ratio.
The 10 Gb links with highest downlink load (presumeably also those that have highest Gb congestion).