New measurement - 128 - ETP Ethernet BSC Counter name Description RECEIVED_ETH_ Number of received Ethernet frames contain errorred and non-errorred frames. FRAMES_ETP_B Unit: 1000 frames SC (128000) Updated: When an Ethernet frame is received. Use case: UL_ FRAME_ERROR_RATE = ERRORED_ETH_FRAMES_ETP_BSC * 100 / RECEIVED_ETH_FRAMES_ETP_BSC It is aggregated over ETPE (Exchange Terminal for Packet Transport over Ethernet) and indicates quality of IP cloud. If high it means that IP cloud could be congested or link is down or equipment failure (e.g. switch is down). ERRORED_ETH_ Number of received error Ethernet frames. FRAMES_ETP_B Unit: 1000 frames SC (128001) Updated: when error Ethernet frame is received. FCS errors, undersized frames, oversized frames, header error and other Ethernet framing errors (errors preventing from being deliverable to a higher-layer protocol) are included Use case: UL_ FRAME_ERROR_RATE Performance Measurements for Packet Abis New measurement - 128 - ETP Ethernet BSC Counter name Description TRANSM_ETH_F Number of transmitted Ethernet frames. Unit: 1000 frames RAMES_ETP_BS Updated: When an Ethernet frame is sent C (128002) Use case: AVG_DL_FRAME_SIZE= TRANSM_ETH_OCTETS_ETP_BSC /(TRANSM_ETH_FRAMES_ETP_BSC * 1000) Unit: Bytes This KPI can be used to optimize setting of multiplexing parameters (e.g. if frame size is well below settings of Ethernet MTU size in case of Packet Abis over Ethernet then more aggressive multiplexing can be applied) AVG_DL_GROSS_BIT_RATE = TRANSM_ETH_OCTETS_ETP_BSC * 8 / granularity_period (sec) Unit: Mbps E.g. if granularity is of 1 hour: AVG_DL_GROSS_BIT_RATE= TRANSM_ETH_OCTETS_ETP_BSC*8 / 3600 This KPI can be used to estimate needed bandwidth RECEIVED_ETH_ Number of octets in valid frames received on the interface. OCTETS_ETP_B Unit: 1000000 octets (i.e. MByte) SC (128003) Updated: when an Ethernet frame is received. TRANSM_ETH_O Number of octets in valid frames sent. CTETS_ETP_BS Unit: 1000000 octets (i.e. MByte) C (128004) Updated: when an Ethernet frame is sent. Use case: AVG_DL_FRAME_SIZE Performance Measurements for Packet Abis New counters in 72 – Packet Control Unit measurement Counter name Description UL_MCS_REDUC Number of times when uplink MCS has been limited due to PCU resources in case of TION_PCU_RES Packet Abis. OURCE (072265) Updated: When uplink MCS has been limited due to PCU resources. Counter is updated in case of Packet Abis only. Use case: UL_MCS_LIMITED_BY_PA = UL_MCS_REDUCTION_PCU_RESOURCE/ 60*((UL GPRS payload_Gbyte) + (UL EGPRS payload_Gbyte)) = b.UL_MCS_REDUCTION_PCU_RESOURCE/60 * ( b.rlc_data_blocks_ul_cs1 *20 + b.rlc_data_blocks_ul_cs2 *30 + sum over MCS-1 (xx)* 22 + sum over MCS-2 (xx)* 28 + sum over MCS-3 (xx)* 37 + sum over MCS-4 (xx)* 44 + sum over MCS-5 (xx)* 56 + sum over MCS-6 (xx)* 74 + sum over MCS-7 (xx/2)*112 + sum over MCS-8 (xx/2)*136 + sum over MCS-9 (xx/2)*148 + sum over MCS-11(xx)*36 ;CS3 + sum over MCS-12(xx)*50 ;CS4 ) / (1024*1024*1024) where xx = (a.ul_rlc_blocks_in_ack_mode + a.ul_rlc_blocks_in_unack_mode) Counters from table(s): a = p_nbsc_coding_scheme b = p_nbsc_packet_control_unit Unit: limitation per Gbyte Note: This KPI shows how many times MCS was limited due to lack of PCU resources while transmitting 1 Gbyte payload. Performance Measurements for Packet Abis New counters in 72 – Packet Control Unit measurement Counter name Description DL_MCS_REDUC Number of times when downlink MCS has been reduced due to PCU resources in case of TION_PCU_RES Packet Abis. OURCE (072266) Updated: When downlink MCS has been reduced due to PCU resources. Counter is updated in case of Packet Abis only. Use case: DL_MCS_LIMITED_BY_PA = DL_MCS_REDUCTION_PCU_RESOURCE/ 60*((DL GPRS payload_Gbyte) + (DL EGPRS payload_Gbyte)) = b.DL_MCS_REDUCTION_PCU_RESOURCE/60 * (b.rlc_data_blocks_dl_cs1 *20 + b.rlc_data_blocks_dl_cs2 *30 + sum over MCS-1 (xx)* 22 + sum over MCS-2 (xx)* 28 + sum over MCS-3 (xx)* 37 + sum over MCS-4 (xx)* 44 + sum over MCS-5 (xx)* 56 + sum over MCS-6 (xx)* 74 + sum over MCS-7 (xx/2)*112 + sum over MCS-8 (xx/2)*136 + sum over MCS-9 (xx/2)*148 + sum over MCS-11(xx)*36 ;CS3 + sum over MCS-12(xx)*50 ;CS4 ) / (1024*1024*1024) where xx = (a.dl_rlc_blocks_in_ack_mode + a.dl_rlc_blocks_in_unack_mode) Counters from table(s): a = p_nbsc_coding_scheme b = p_nbsc_packet_control_unit Unit: limitation per Gbyte Note: This KPI shows how many times MCS was limited due to lack of PCU resources while transmitting 1 Gbyte payload. Performance Measurements Modified counter for Packet Abis in 110 – PCU utilization Counter name Description PEAK_RESERVE Peak number of reserved PCUPCM (16 kbit/s) channels. All reserved channels within a D_PCUPCM_CH measurement period are taken into account: GPRS channels, EGPRS master and slave (110000) channels. Modification in Packet Abis environment: With Packet Abis the peak number of maximum possible PCU resource allocation units (16 kbit/s channel equivalents) according to the maximum MCS for the territory, e.g. 1 RTSL with MCS3 + 1 RTSL with MCS6 + 1 RTSL with MCS9 gives in total 400 octets allocated in PCU (cf. Slide51) Updated: When the sampled value exceeds the current peak value. Use case: Peak PCU utilization PCU2D_UTIL = PEAK_RESERVED_PCUPCM_CH / (40 x 8 x 32) = PEAK_RESERVED_PCUPCM_CH / 10240 PCU2E_UTIL = PEAK_RESERVED_PCUPCM_CH / (40 x 6 x 172) = PEAK_RESERVED_PCUPCM_CH / 41280 Peak PCU utilization represents the ratio between peak reservation of PCU resources and all available resources for given PCU HW variant (expressed in number of octets that can be allocated during single scheduling cycle e.g. for PCU2D we can allocate up to 32 equivalents of 16 kbit/s channels per each DSP and we have 8 DSPs per logical PCU) High (greater than 80%) Peak PCU utilization indicates the need for additional PCU (and re-allocation of cells among existing PCUs): especially when it comes together with frequent reductions of MCS (cf. counters 072265 and 072266)