Академический Документы
Профессиональный Документы
Культура Документы
IP Iu-PS throughput - ingress IP Iur throughput - ingress IP Iub throughput - ingress Average Reserved IP bit rate
IP Route Egress Reservation Rate Max reserved IP based route bandwidth utilization Average UDP connections of the IP based route Maximum UDP connections of the IP based route Successful IP transport resource reservations in the RNC for Iub IP transport resource reservation failures due to external CAC for Iub IP transport resource reservation failures due to internal CAC for Iub
IP transport resource reservation failures due to other CAC reasons for Iub
IP Route Accessibility for outgoing traffic in Iub Successful IP transport resource reservations in the BTS for Iub IP transport resource reservations failures in the BTS due to external CAC for Iub IP transport resource reservations failures in the BTS due to other transport related failure than congestion for Iub IP Route Accessibility for incoming traffic in Iub Successful IP transport resource reservations in the RNC for Iu-PS IP transport resource reservation failures due to external CAC for Iu-PS IP transport resource reservation failures due to internal CAC for Iu-PS
IP transport resource reservation failures due to other CAC reasons for Iu-PS
IP Route Accessibility for outgoing traffic in Iu-PS Successful IP transport resource reservations in the RNC for Iu-CS IP transport resource reservation failures due to external CAC for Iu-CS IP transport resource reservation failures due to internal CAC for Iu-CS
IP transport resource reservation failures due to other CAC reasons for Iu-CS
IP Route Accessibility for outgoing traffic in Iu-CS Successful IP transport resource reservations in the RNC for Iur IP transport resource reservation failures due to external CAC for Iur IP transport resource reservation failures due to internal CAC for Iur
IP transport resource reservation failures due to other CAC reasons for Iur
Outgoing IPv4 traffic volume Outgoing IPv6 traffic volume Outgoing IPv4 throughput Outgoing IPv6 throughput
Ingress EF throughput
Ingress BE throughput
Ingress EF throughput
Egress BE throughput
Description
Total outgoing data volume for IP based Traffic in Controlling RNC for the reporting period for a selected logical interface. The outgoing Traffic includes all user plane and control plane traffic between RNC and BTS/neighbour RNC/CN (depends on what is the receiving NE). Includes both the payload and IP datagram header bytes. Total incoming data volume for IP based Traffic in Controlling RNC for the reporting period for a selected logical interface. The incoming Traffic includes all user plane and control plane traffic between RNC and BTS/neighbour RNC/CN (depends on what is the receiving NE). Includes both the payload and IP datagram header bytes. Iu-CS IP layer uplink throughput in RNC.
Iu-PS IP layer uplink throughput in RNC. SRNC Iur IP layer downlink throughput in RNC RNC Iub IP layer downlink throughput in RNC.
IP Iub traffic load in DL direction. It compares the DL traffic throughput against the available bandwith.
Iu-PS IP layer downlink throughput in RNC. SRNC Iur IP layer uplink throughput in RNC RNC Iub IP layer uplink throughput in RNC. Average reserved IP bit rate for a specific IP route
The minimum value of reserved IP layer bit rate during the measurement interval
The maximum value of reserved IP layer bit rate during the measurement interval
This KPI represents the reservation rate of guaranteed IP transport resources. Average reserved IP based route bandwidth utilization related to the committed bit rate defined for that IP route. Maximum reserved IP based route bandwidth utilization related to the committed bit rate defined for that IP route. Average number of UDP connections of the IP based route Maximum number of UDP connections of the IP based route The number of successful IP transport reservations in the RNC for Iub. The number of failed IP transport resource reservations in the RNC for Iub due to external connection admission control. The number of failed IP transport resource reservations in the RNC for Iub due to internal connection admission control.
The number of failed IP transport resource reservations in the RNC for Iub due to other reasons than connection admission control reasons.
The transport resource request success ratio [%]. This KPI describes the average success rate of the transport resource reservation attempts for IP Route based connections corresponding to Iub for the downlink traffic. The number of successful IP transport resource reservations in the BTS. The number of failed IP transport resource reservations in the BTS due to external connection admission control. The number of failed IP transport resource reservations in the BTS due to some other transport related failure than congestion. Also RNC internal failures after BTS successful response are included in this counter. The transport resource request success ratio [%]. This KPI describes the average success rate of the transport resource reservation attempts for IP Route based connections corresponding to Iub for the uplink traffic. The number of successful IP transport reservations in the RNC for Iu-PS. The number of failed IP transport resource reservations in the RNC for Iu-PS due to external connection admission control. The number of failed IP transport resource reservations in the RNC for Iu-PS due to internal connection admission control.
The number of failed IP transport resource reservations in the RNC for Iu-PS due to other reasons than connection admission control reasons.
The transport resource request success ratio [%]. This KPI describes the average success rate of the transport resource reservation attempts for IP Route based connections corresponding to Iu-PS. The number of successful IP transport reservations in the RNC for Iu-CS. The number of failed IP transport resource reservations in the RNC for Iu-CS due to external connection admission control. The number of failed IP transport resource reservations in the RNC for Iu-CS due to internal connection admission control.
The number of failed IP transport resource reservations in the RNC for Iu-CS due to other reasons than connection admission control reasons.
The transport resource request success ratio [%]. This KPI describes the average success rate of the transport resource reservation attempts for IP Route based connections corresponding to Iu-CS. The number of successful IP transport reservations in the RNC for Iur. The number of failed IP transport resource reservations in the RNC for Iur due to external connection admission control. The number of failed IP transport resource reservations in the RNC for Iur due to internal connection admission control.
The number of failed IP transport resource reservations in the RNC for Iur due to other reasons than connection admission control reasons.
The transport resource request success ratio [%]. This KPI describes the average success rate of the transport resource reservation attempts for IP Route based connections corresponding to Iur. The amount of data sent in IPv4 datagrams. The counter includes user plane traffic, datagrams targeted to NPGE host processor are not included. The amount of data sent in IPv6 datagrams. Average IPv4 throughput over a measurement period per IP interface Average IPv6 throughput over a measurement period per IP interface
Formula
sum (OUT_DATA_IP_ROUTE) / 1000
8* sum (OUT_DATA_IP_ROUTE) / sum (60 * PERIOD_DURATION)*1000 8* sum (OUT_DATA_IP_ROUTE) / sum (60 * PERIOD_DURATION)*1000 8* sum (OUT_DATA_IP_ROUTE) / sum (60 * PERIOD_DURATION)*1000
8* sum (IN_DATA_IP_ROUTE) / sum (60 * PERIOD_DURATION)*1000 8* sum (IN_DATA_IP_ROUTE) / sum (60 * PERIOD_DURATION)*1000 8* sum (IN_DATA_IP_ROUTE) / sum (60 * PERIOD_DURATION)*1000 sum (SUM_RESERVED_RATE_IP_ROUTE) / sum (NBR_SAMPLES_IP_ROUTE)
min (MIN_RESERVED_RATE_IP_ROUTE)
max (MAX_RESERVED_RATE_IP_ROUTE)
100 *(sum (SUM_RESERVED_RATE_IP_ROUTE / NBR_SAMPLES_IP_ROUTE) / (sum COMMITTED_BIT_RATE_IP_ROUTE)) 100 * sum (MAX_RESERVED_RATE_IP_ROUTE) / sum (COMMITTED_BIT_RATE_IP_ROUTE) sum (SUM_IP_UDP_CONN_IP_ROUTE) / sum (NBR_SAMPLES_IP_ROUTE) max (MAX_UDP_CONN_IP_ROUTE) sum (SUCC_RNC_IP_RES)
sum (FAIL_RNC_IP_RES_EXT)
sum (FAIL_RNC_IP_RES_INT)
sum (FAIL_RNC_IP_RES_OTHER)
100* sum(SUCC_RNC_IP_RES) / sum(SUCC_RNC_IP_RES + FAIL_RNC_IP_RES_EXT + FAIL_RNC_IP_RES_INT + FAIL_RNC_IP_RES_OTHER) sum (SUCC_BTS_IP_RES) sum (FAIL_BTS_IP_RES_EXT_TRANS) sum (FAIL_BTS_IP_RES_OTHER_TRANS) 100* sum(SUCC_BTS_IP_RES) / sum (SUCC_BTS_IP_RES + FAIL_BTS_IP_RES_EXT_TRANS + FAIL_BTS_IP_RES_OTHER_TRANS) sum (SUCC_RNC_IP_RES)
sum (FAIL_RNC_IP_RES_EXT)
sum (FAIL_RNC_IP_RES_INT)
sum (FAIL_RNC_IP_RES_OTHER)
sum (FAIL_RNC_IP_RES_EXT)
sum (FAIL_RNC_IP_RES_INT)
sum (FAIL_RNC_IP_RES_OTHER)
sum (FAIL_RNC_IP_RES_EXT)
sum (FAIL_RNC_IP_RES_INT)
sum (FAIL_RNC_IP_RES_OTHER)
100* sum(SUCC_RNC_IP_RES) / sum(SUCC_RNC_IP_RES + FAIL_RNC_IP_RES_EXT + FAIL_RNC_IP_RES_INT + FAIL_RNC_IP_RES_OTHER) sum (0.1 * IP4_OUT_BYTES) sum (0.1 * IP6_OUT_BYTES) sum (8 * 100 * IP4_OUT_BYTES) / (1000000 * sum (60 * PERIOD_DURATION)) sum (8 * 100 * IP6_OUT_BYTES) / (1000000 * sum (60 * PERIOD_DURATION))
Comment
OUT_DATA_IP_ROUTE en KB
Formula_id/counter_id
RNC_5022a
RNC_5029a
Iu-CS interface identification should be done by showing RNC_1629a info about the relation between RNC and MSC/VLR. Iu-PS interface identification should be done by showing RNC_1631a info about the relation between RNC and SGSN. Iur interface identification should be done by showing RNC_1633a info about the relation between SRNC and DRNC. Iub interface identification should be done by showing RNC_1635a info about the relation between RNC and NodeB. This KPI can potentailly provide results higher than 100 %. Explanation: M568C2 COMMITTED_BIT_RATE_IP_ROUTE - This counter is calculated using the following formulae: "IP based route CAC bandwidth" - "signalling bandwidth" - "DCN bandwidth" RNC_1794a Since the total egress traffic of the IP based route presented by M568C0 OUT_DATA_IP_ROUTE can be higher than the configured IP Based Route Committed Bit Rate of the IP based route presented by M568C2 COMMITTED_BIT_RATE_IP_ROUTE, this can lead to KPI values higher than 100%. Iu-CS interface identification should be done by showing RNC_1630a info about the relation between RNC and MSC/VLR. Iu-PS interface identification should be done by showing RNC_1632a info about the relation between RNC and SGSN. Iur interface identification should be done by showing info about the relation between SRNC and DRNC. Iub interface identification should be done by showing info about the relation between RNC and NodeB. RNC_1634a RNC_1636a RNC_1865a The bit rate is sampled with 5 second interval. If calculated for the same IP route over several measurement periods, min (MIN_RSERVED_RATE_IP_ROUTE) or sum (MIN_RESERVED_RATE_IP_ROUTE) can be used. If calculated over several IP route for the same measurement period, sum (MIN_RESERVED_RATE_IP_ROUTE) has to be used
M568C4
The bit rate is sampled with 5 second interval. If calculated for the same IP route over several measurement periods, max (MAX_RSERVED_RATE_IP_ROUTE) or sum M568C5 (MAX_RESERVED_RATE_IP_ROUTE) can be used. If calculated over several IP route for the same measurement period, sum (MAX_RESERVED_RATE_IP_ROUTE) has to be used RNC_5052a
Updated when the IP resources are successfully reserved on the RNC side. The sum has to be done over the IP routes corresponding to the Iub. Updated when the RNC external IP CAC rejects the resource request. The sum has to be done over the IP routes corresponding to the Iub. Updated when the RNC internal IP CAC rejects the resource request. The sum has to be done over the IP routes corresponding to the Iub. Updated when the IP resource reservation fails due to any reason other than connection admission control failure. Such a reason could be for example route analysis failure caused by a configuration error. The sum has to be done over the IP routes corresponding to the Iub. The sums have to be done over the IP routes corresponding to the Iub.
M804C0
M804C1
M804C2
M804C3
The sums have to be done over the IP routes corresponding to the Iub. Updated when the IP resources are successfully reserved on the RNC side. The sum has to be done over the IP routes corresponding to the Iu-PS. Updated when the RNC external IP CAC rejects the resource request. The sum has to be done over the IP routes corresponding to the Iu-PS. Updated when the RNC internal IP CAC rejects the resource request. The sum has to be done over the IP routes corresponding to the Iu-PS.
RNC_5031a or RNC_1783a
M804C0
M804C1
M804C2
Updated when the IP resource reservation fails due to any reason other than connection admission control failure. Such a reason could be for example route analysis failure caused by a configuration error. The sum has to be done over the IP routes corresponding to the Iu-PS. The sums have to be done over the IP routes corresponding to the Iu-PS. Updated when the IP resources are successfully reserved on the RNC side. The sum has to be done over the IP routes corresponding to the Iu-CS. Updated when the RNC external IP CAC rejects the resource request. The sum has to be done over the IP routes corresponding to the Iu-CS. Updated when the RNC internal IP CAC rejects the resource request. The sum has to be done over the IP routes corresponding to the Iu-CS. Updated when the IP resource reservation fails due to any reason other than connection admission control failure. Such a reason could be for example route analysis failure caused by a configuration error. The sum has to be done over the IP routes corresponding to the Iu-CS. The sums have to be done over the IP routes corresponding to the Iu-CS. Updated when the IP resources are successfully reserved on the RNC side. The sum has to be done over the IP routes corresponding to the Iur. Updated when the RNC external IP CAC rejects the resource request. The sum has to be done over the IP routes corresponding to the Iur. Updated when the RNC internal IP CAC rejects the resource request. The sum has to be done over the IP routes corresponding to the Iur. Updated when the IP resource reservation fails due to any reason other than connection admission control failure. Such a reason could be for example route analysis failure caused by a configuration error. The sum has to be done over the IP routes corresponding to the Iur. The sums have to be done over the IP routes corresponding to the Iur. This counter is reported per IP interface and not per VLAN in case some are defined This counter is reported per IP interface and not per VLAN in case some are defined This counter is reported per IP interface and not per VLAN in case some are defined This counter is reported per IP interface and not per VLAN in case some are defined
M804C3
RNC_5005a
M804C0
M804C1
M804C2
M804C3
RNC_5005a
M804C0
M804C1
M804C2
M804C3
RNC_5005a
This counter is reported per IP interface and not per VLAN in case some are defined. The filter has to be done with the PHB = EF. This counter is reported per IP interface and not per VLAN in case some are defined. The filter has to be done with the PHB = AF1. This counter is reported per IP interface and not per VLAN in case some are defined. The filter has to be done with the PHB = AF2. This counter is reported per IP interface and not per VLAN in case some are defined. The filter has to be done with the PHB = AF3. This counter is reported per IP interface and not per VLAN in case some are defined. The filter has to be done with the PHB = AF4. This counter is reported per IP interface and not per VLAN in case some are defined. The filter has to be done with the PHB = BE. This counter is reported per IP interface and not per VLAN in case some are defined. The filter has to be done with the PHB = EF. This counter is reported per IP interface and not per VLAN in case some are defined. The filter has to be done with the PHB = AF1. This counter is reported per IP interface and not per VLAN in case some are defined. The filter has to be done with the PHB = AF2. This counter is reported per IP interface and not per VLAN in case some are defined. The filter has to be done with the PHB = AF3. This counter is reported per IP interface and not per VLAN in case some are defined. The filter has to be done with the PHB = AF4. This counter is reported per IP interface and not per VLAN in case some are defined. The filter has to be done with the PHB = BE. This counter is reported per IP interface and not per VLAN in case some are defined. The filter has to be done with the PHB = EF. These counters are reported per IP interface and not per VLAN in case some are defined. The filter has to be done with the PHB = AF1. These counters are reported per IP interface and not per VLAN in case some are defined. The filter has to be done with the PHB = AF2. These counters are reported per IP interface and not per VLAN in case some are defined. The filter has to be done with the PHB = AF3. These counters are reported per IP interface and not per VLAN in case some are defined. The filter has to be done with the PHB = AF4. These counters are reported per IP interface and not per VLAN in case some are defined. The filter has to be done with the PHB = BE.
Object
Network, RNC, IP Route
Unit
Mbytes
Measurement
M568_IP_based_route
Mbytes
M568_IP_based_route
Mbps
M568_IP_based_route
Network, RAN, RNC, IP Route Network, RAN, RNC, IP Route Network, RAN, RNC, IP Route, WBTS
M568_IP_based_route
Mbps
M568_IP_based_route
Network, RAN, RNC, IP Route Network, RAN, RNC, IP Route Network, RAN, RNC, IP Route, WBTS Network, Area, RAN, RNC, IP Route, WBTS
kbps
M568_IP_based_route
kbps
M568_IP_based_route
Network, Area, RAN, RNC, IP Route Network, Area, RAN, RNC, IP Route IP Route IP Route Network, Area, RAN, RNC, IP Route Network, Area, RAN, RNC, IP Route Network, Area, RAN, RNC, IP Route
% % # # #
M804_RNC_IP_CAC
M804_RNC_IP_CAC
M804_RNC_IP_CAC
% Network, Area, RAN, RNC, IP Route Network, Area, RAN, RNC, IP Route Network, Area, RAN, RNC, IP Route Network, Area, RAN, RNC, IP Route Network, Area, RAN, RNC, IP Route Network, Area, RAN, RNC, IP Route Network, Area, RAN, RNC, IP Route # # #
M804_RNC_IP_CAC
M804_RNC_IP_CAC
M804_RNC_IP_CAC
M804_RNC_IP_CAC
M804_RNC_IP_CAC
Network, Area, RAN, RNC, IP Route Network, Area, RAN, RNC, IP Route Network, Area, RAN, RNC, IP Route Network, Area, RAN, RNC, IP Route
M804_RNC_IP_CAC
M804_RNC_IP_CAC
M804_RNC_IP_CAC
M804_RNC_IP_CAC
M804_RNC_IP_CAC
Network, Area, RAN, RNC, IP Route Network, Area, RAN, RNC, IP Route Network, Area, RAN, RNC, IP Route Network, Area, RAN, RNC, IP Route
M804_RNC_IP_CAC
M804_RNC_IP_CAC
M804_RNC_IP_CAC
M804_RNC_IP_CAC
M804_RNC_IP_CAC
M804_RNC_IP_CAC
IP Interface
Mbps
M567_IP_QoS
IP Interface
Mbps
M567_IP_QoS
IP Interface
Mbps
M567_IP_QoS
IP Interface
Mbps
M567_IP_QoS
IP Interface
Mbps
M567_IP_QoS
IP Interface
Mbps
M567_IP_QoS
IP Interface
Mbps
M567_IP_QoS
IP Interface
Mbps
M567_IP_QoS
IP Interface
Mbps
M567_IP_QoS
IP Interface
Mbps
M567_IP_QoS
IP Interface
Mbps
M567_IP_QoS
IP Interface
Mbps
M567_IP_QoS
IP Interface
M567_IP_QoS
IP Interface
M567_IP_QoS
IP Interface
M567_IP_QoS
IP Interface
M567_IP_QoS
IP Interface
M567_IP_QoS
IP Interface
M567_IP_QoS
Metric Name
Average ingress Ethernet Traffic Average egress Ethernet Traffic
Egress packet drop ratio Ethernet interface unavailable Ethernet interface errors
Description
Average ingress Ethernet Traffic Average egress Ethernet Traffic
This KPI is reporting the average ingress (Iub downlink) packet drop ratio of the Ethernet interface in FTM
This KPI is reporting the average egress (Iub link) packet drop ratio of the Ethernet interface in FTM. This KPI is reporting the seconds Ethernet interface has been unavailable during the measurement period This KPI is reporting the seconds Ethernet interface has been severely affected
Formula
sum ( EthIfInOcts_15 * 8) / 1000 * sum (60 * PERIOD_DURATION) sum ( EthIfOutOcts_15 * 8) / 1000 * sum (60 * PERIOD_DURATION)
100 * sum (EthIfOutDiscShaping_15) / sum (EthIfOutDiscShaping_15 + EthIfOutPkt_15) 100 * sum (EthIfUas_15) / sum (60 * PERIOD_DURATION) 100 * sum (EthIfSec_15 / sum (60 * PERIOD_DURATION)
Comment
Formula_id/counter_id
M5110C0 M5110C1
Following errors are counted: number of received Ethernet packets with Frame check sequence errors, number od received Ethernet packets with unknown VLAN-ID, number of received Ethernet frames whose PSN headers is not configured or has a reserved value (contains an invalid Pseudo wire tunnel header i.e. IP address)
Following error is currently counted: number of Ethernet M5110C6 / (M5110C6 + Tx packets that are discarded due to rate shaping. M5110C3) M5110C9 M5110C10
Object
WBTS WBTS
Unit
kbps kbps
Measurement
FTM_ethernet_link FTM_ethernet_link
WBTS
FTM_ethernet_link
% % %