Ericsson 3G pmCounters

c
 "

  


  
  
"

pmNoOfDiscardedMsg Monitors the number of messages that are discarded due to congestion control on the control plane over Iub owing to UNI SAAL or SCTP Congestion Control. Counter type: Peg Counter is reset after measurement interval: Yes Condition: Stepped every time a message is discarded. Undefined value: -1

"

  


  
  
"

pmTotalTimeIubLinkCongestedUl The time that the Iub link is congested for the NBAP Common part of the control plane in the uplink direction. Counter type: Peg Counter is reset after measurement interval: Yes Condition: The actual measurement is started when the MO NbapCommon is created. The counter is stepped once per second from when a congestion is detected until the congestion is ceased or NBAP Common communication is lost. Unit: 1 s Undefined value: -1

  c
 "

  


  
  
"

pmNoOfDiscardedMsg Monitors the number of messages that are discarded due to congestion control on the control plane over Iub owing to UNI SAAL or SCTP Congestion Control. Counter type: Peg Counter is reset after measurement interval: Yes Condition: Stepped every time a message is discarded. Undefined value: -1

"

  


  
  
"

pmTotalTimeIubLinkCongestedUl The time that the Iub link is congested for the NBAP Common part of the control plane in the uplink direction. Counter type: Peg Counter is reset after measurement interval: Yes Condition: The actual measurement is started when the MO NbapCommon is created. The counter is stepped once per second from when a congestion is detected until the congestion is ceased or NBAP Common communication is lost. Unit: 1 s Undefined value: -1

  "

  


  
  
"

"

  


  
  
"

pmDchFramesReceived The number of received DCH Iub frames in kframes (1000 frames). Counter type: Peg Counter is reset after measurement interval: Yes Condition: Measurement can be started on at least one DBCH device set. That is, state is operational and the device board has correct capability. Undefined value: -1 pmDchFramesTooLate The number of DCH Iub FP frames discarded owing to too late arrival, that is, after LTOA. Counter type: Peg Counter is reset after measurement interval: Yes Condition: Measurement can be started on at least one DBCH device set. That is, state is operational and the device board has correct capability. Undefined value: -1

"

  


  
  
"

pmEdchIubLimitingRatio Indicates in what degree the EUL traffic in uplink is limited by the Iub/Iur interfaces, between RBS and SRNC. When a high value is indicated, it should be considered to extend Iub/Iur with higher EUL bandwidth. Indicates the percentage of 100 ms periods with scheduled EUL traffic where Iub has been the only limiting factor during at least one TTI. The result is a percentage figure between 0.0 and 100.0%. Counter type: Gauge Counter is reset after measurement interval: Yes Condition: Measurement can be started on at least one device set (EScDeviceSet). That is, state is operational and the corresponding device board has correct capability. The E-DCH scheduler is limited by: 1) RBS HW, 2) Iub bandwidth, and 3) Uu interface resources. These resource limitations are for this measurement measured every 100 ms period. Each 100 ms period that the UE required EUL bit rate (edchGrantRate)

during any of the 2 and/or 10 ms TTIs during the 100 ms period that has been higher than the available resources and that the only limiting resource during at least one of these TTIs has been the E-DCH Iub Scheduler Limit Rate (edchIubSchLimitRate), Then that 100 ms period is marked as an Iub Limiting period. Unit: 0.1% Undefined value: -1 "




  


  
  
"

pmHsDataFrameDelayIubSpi00 The PM counter presents a histogram over the dynamic delay experienced between SRNC and RBS by the flow controlled HSDPA flows, that is, the buffer build-up delay distribution for HS traffic. Counter type: PDF Counter is reset after measurement interval: Yes Condition: Measurement can be started on at least one DBCC device set. That is, state is operational and the device board has correct capability. The delay is between SRNC and RBS, that is, both Iub and Iur are included in the delay measurement. Sampled every 100 ms period. The samples are taken from all the HS-DSCH channels scheduled on priority class 00. PDF range: [0]: Number of samples in range [0..10[ [1]: Number of samples in range [10..20[ [2]: Number of samples in range [20..30[ ... [14]: Number of samples in range [140..150[ [15]: Number of samples >= 150 ms Unit: 1 ms Undefined value: -1

"




  


  
  
"

pmHsDataFrameDelayIubSpi01 The PM counter presents a histogram over the dynamic delay experienced between SRNC and RBS by the flow controlled HSDPA flows, that is, the buffer build-up delay distribution for HS traffic. Counter type: PDF Counter is reset after measurement interval: Yes Condition: Measurement can be started on at least one DBCC device set. That is, state is operational and the device board has correct capability. The delay is between SRNC and RBS, that is, both Iub and Iur are included in the delay measurement. Sampled every 100 ms period. The samples are taken from all the HS-DSCH channels scheduled on priority class 01.

PDF range: [0]: Number of samples in range [0..10[ [1]: Number of samples in range [10..20[ [2]: Number of samples in range [20..30[ ... [14]: Number of samples in range [140..150[ [15]: Number of samples >= 150 ms Unit: 1 ms Undefined value: -1 "




  


  
  
"

pmHsDataFrameDelayIubSpi02 The PM counter presents a histogram over the dynamic delay experienced between SRNC and RBS by the flow controlled HSDPA flows, that is, the buffer build-up delay distribution for HS traffic. Counter type: PDF Counter is reset after measurement interval: Yes Condition: Measurement can be started on at least one DBCC device set. That is, state is operational and the device board has correct capability. The delay is between SRNC and RBS, that is, both Iub and Iur are included in the delay measurement. Sampled every 100 ms period. The samples are taken from all the HS-DSCH channels scheduled on priority class 02. PDF range: [0]: Number of samples in range [0..10[ [1]: Number of samples in range [10..20[ [2]: Number of samples in range [20..30[ ... [14]: Number of samples in range [140..150[ [15]: Number of samples >= 150 ms Unit: 1 ms Undefined value: -1

       

"

  


  
  
"

"

  


  
  
"

pmDchFramesTooLate The number of DCH Iub FP frames discarded owing to too late arrival, that is, after LTOA. Counter type: Peg Counter is reset after measurement interval: Yes Condition: Measurement can be started on at least one DBCH device set. That is, state is operational and the device board has correct capability. Undefined value: -1 pmEdchIubLimitingRatio Indicates in what degree the EUL traffic in uplink is limited by the Iub/Iur interfaces, between RBS and SRNC. When a high value is indicated, it should be considered to extend Iub/Iur with higher EUL bandwidth. Indicates the percentage of 100 ms periods with scheduled EUL traffic where Iub has been the only limiting factor during at least one TTI. The result is a percentage figure between 0.0 and 100.0%. Counter type: Gauge Counter is reset after measurement interval: Yes Condition: Measurement can be started on at least one device set (EScDeviceSet). That is, state is operational and the corresponding device board has correct capability. The E-DCH scheduler is limited by: 1) RBS HW, 2) Iub bandwidth, and 3) Uu interface resources. These resource limitations are for this measurement measured every 100 ms period. Each 100 ms period that the UE required EUL bit rate (edchGrantRate) during any of the 2 and/or 10 ms TTIs during the 100 ms period that has been higher than the available resources and that the only limiting resource during at least one of these TTIs has been the E-DCH Iub Scheduler Limit Rate (edchIubSchLimitRate), Then that 100 ms period is marked as an Iub Limiting period. Unit: 0.1% Undefined value: -1

"




  


  
  
"

pmHsDataFrameDelayIubSpi00 The PM counter presents a histogram over the dynamic delay experienced between SRNC and RBS by the flow controlled HSDPA flows, that is, the buffer build-up delay distribution for HS traffic. Counter type: PDF

Counter is reset after measurement interval: Yes Condition: Measurement can be started on at least one DBCC device set. That is, state is operational and the device board has correct capability. The delay is between SRNC and RBS, that is, both Iub and Iur are included in the delay measurement. Sampled every 100 ms period. The samples are taken from all the HS-DSCH channels scheduled on priority class 00. PDF range: [0]: Number of samples in range [0..10[ [1]: Number of samples in range [10..20[ [2]: Number of samples in range [20..30[ ... [14]: Number of samples in range [140..150[ [15]: Number of samples >= 150 ms Unit: 1 ms Undefined value: -1 "




  


  
  
"

pmHsDataFrameDelayIubSpi01 The PM counter presents a histogram over the dynamic delay experienced between SRNC and RBS by the flow controlled HSDPA flows, that is, the buffer build-up delay distribution for HS traffic. Counter type: PDF Counter is reset after measurement interval: Yes Condition: Measurement can be started on at least one DBCC device set. That is, state is operational and the device board has correct capability. The delay is between SRNC and RBS, that is, both Iub and Iur are included in the delay measurement. Sampled every 100 ms period. The samples are taken from all the HS-DSCH channels scheduled on priority class 01. PDF range: [0]: Number of samples in range [0..10[ [1]: Number of samples in range [10..20[ [2]: Number of samples in range [20..30[ ... [14]: Number of samples in range [140..150[ [15]: Number of samples >= 150 ms Unit: 1 ms Undefined value: -1

"




  


  
  
"

pmHsDataFrameDelayIubSpi02 The PM counter presents a histogram over the dynamic delay experienced between SRNC and RBS by the flow controlled HSDPA flows, that is, the buffer build-up delay distribution for HS traffic. Counter type: PDF Counter is reset after measurement interval: Yes Condition: Measurement can be started on at least one

DBCC device set. That is, state is operational and the device board has correct capability. The delay is between SRNC and RBS, that is, both Iub and Iur are included in the delay measurement. Sampled every 100 ms period. The samples are taken from all the HS-DSCH channels scheduled on priority class 02. PDF range: [0]: Number of samples in range [0..10[ [1]: Number of samples in range [10..20[ [2]: Number of samples in range [20..30[ ... [14]: Number of samples in range [140..150[ [15]: Number of samples >= 150 ms Unit: 1 ms Undefined value: -1

  "

  


  
  
"

pmEdchIubLimitingRatio Indicates in what degree the EUL traffic in uplink is limited by the Iub/Iur interfaces, between RBS and SRNC. When a high value is indicated, it should be considered to extend Iub/Iur with higher EUL bandwidth. Indicates the percentage of 100 ms periods with scheduled EUL traffic where Iub has been the only limiting factor during at least one TTI. The result is a percentage figure between 0.0 and 100.0%. Counter type: Gauge Counter is reset after measurement interval: Yes Condition: Measurement can be started on at least one device set (EScDeviceSet). That is, state is operational and the corresponding device board has correct capability. The E-DCH scheduler is limited by: 1) RBS HW, 2) Iub bandwidth, and 3) Uu interface resources. These resource limitations are for this measurement measured every 100 ms period. Each 100 ms period that the UE required EUL bit rate (edchGrantRate) during any of the 2 and/or 10 ms TTIs during the 100 ms period that has been higher than the available resources and that the only limiting resource during at least one of these TTIs has been the E-DCH Iub Scheduler Limit Rate (edchIubSchLimitRate), Then that 100 ms period is marked as an Iub Limiting period.

Unit: 0.1% Undefined value: -1 "




  


  
  
"

pmHsDataFrameDelayIubSpi00 The PM counter presents a histogram over the dynamic delay experienced between SRNC and RBS by the flow controlled HSDPA flows, that is, the buffer build-up delay distribution for HS traffic. Counter type: PDF Counter is reset after measurement interval: Yes Condition: Measurement can be started on at least one DBCC device set. That is, state is operational and the device board has correct capability. The delay is between SRNC and RBS, that is, both Iub and Iur are included in the delay measurement. Sampled every 100 ms period. The samples are taken from all the HSDSCH channels scheduled on priority class 00. PDF range: [0]: Number of samples in range [0..10[ [1]: Number of samples in range [10..20[ [2]: Number of samples in range [20..30[ ... [14]: Number of samples in range [140..150[ [15]: Number of samples >= 150 ms Unit: 1 ms Undefined value: -1

"




  


  
  
"

pmHsDataFrameDelayIubSpi01 The PM counter presents a histogram over the dynamic delay experienced between SRNC and RBS by the flow controlled HSDPA flows, that is, the buffer build-up delay distribution for HS traffic. Counter type: PDF Counter is reset after measurement interval: Yes Condition: Measurement can be started on at least one DBCC device set. That is, state is operational and the device board has correct capability. The delay is between SRNC and RBS, that is, both Iub and Iur are included in the delay measurement. Sampled every 100 ms period. The samples are taken from all the HSDSCH channels scheduled on priority class 01. PDF range: [0]: Number of samples in range [0..10[ [1]: Number of samples in range [10..20[ [2]: Number of samples in range [20..30[ ... [14]: Number of samples in range [140..150[ [15]: Number of samples >= 150 ms Unit: 1 ms Undefined value: -1

"




  


  
  
"

pmHsDataFrameDelayIubSpi02 The PM counter presents a histogram over the dynamic delay experienced between SRNC and RBS by the flow controlled HSDPA flows, that is, the buffer build-up delay distribution for HS traffic. Counter type: PDF Counter is reset after measurement interval: Yes Condition: Measurement can be started on at least one DBCC device set. That is, state is operational and the device board has correct capability. The delay is between SRNC and RBS, that is, both Iub and Iur are included in the delay measurement. Sampled every 100 ms period. The samples are taken from all the HSDSCH channels scheduled on priority class 02. PDF range: [0]: Number of samples in range [0..10[ [1]: Number of samples in range [10..20[ [2]: Number of samples in range [20..30[ ... [14]: Number of samples in range [140..150[ [15]: Number of samples >= 150 ms Unit: 1 ms Undefined value: -1

  "

  


  
  
"

pmIfInOctetsHi The number of octets received by a port, including framing characters and bad packets, but excluding preamble sequences. The high capacity counter for received octets on an interface is split into two parts. This counter represents the higher part of the 62 least significant bits of the high capacity counter for received octets. The two most significant bits of this 64 bit counter are discarded. This 64-bit counter is presented as 2*31 bits: pmIfInOctetsHi (bit 61-31) and pmIfInOctetsLo (bit 30-0) in the MOM. Condition: An octet is received. Counter is reset after measurement period: Yes Counter type: PEG Unit: Number of octets Specification: RFC 2863

"


pmIfInOctetsLo


  


  
  
"

The number of octets received by a port, including framing characters and bad packets, but excluding preamble sequences. The high capacity counter for received octets on an interface is split into two parts. This counter represents the lower part of the 62 least significant bits of the high capacity counter for octets transmitted out on the interface. The two most significant bit of this 64 bits counter are discarded. This 64-bit counter is presented as 2*31 bits: pmIfInOctetsHi (bit 61-31) and pmIfInOctetsLo (bit 30-0) in the MOM. Condition: An octet is received. Counter is reset after measurement period: Yes Counter type: PEG Unit: Number of octets Specification: RFC 2863

 pmIfInOctetsLo "
 The number of octets received by a port, including framing
  
 characters and bad packets, but excluding preamble sequences.

  
  
" The high capacity counter for received octets on an interface is split into two parts. This counter represents the lower part of the 62 least significant bits of the high capacity counter for octets transmitted out on the interface. The two most significant bit of this 64 bits counter are discarded. This 64-bit counter is presented as 2*31 bits: pmIfInOctetsHi (bit 61-31) and pmIfInOctetsLo (bit 30-0) in the MOM. Condition: An octet is received. Counter is reset after measurement period: Yes Counter type: PEG Unit: Number of octets Specification: RFC 2863

  

pmIfOutOctetsHi "
 The number of octets transmitted by a port, including framing
  
 characters and bad packets, but excluding preamble sequences.

  
  
" The high capacity counter for octets transmitted out on an interface is split into two parts. This counter represents the higher part of the 62 least significant bits of the high capacity counter for octets transmitted out on the interface. The two most significant bits of this 64 bits counter are discarded. This 64-bit counter is presented as 2*31 bits: pmIfOutOctetsHi (bit 61-31) and pmIfOutOctetsLo (bit 30-0) in the MOM. Condition: An octet is transmitted. Counter is reset after measurement period: Yes Counter type: PEG Unit: Number of octets Specification: RFC 2863

   pmIfOutOctetsLo "
 The number of octets transmitted by a port, including framing
  
 characters and bad packets, but excluding preamble sequences.

  
  
" The high capacity counter for octets transmitted out on an interface is split into two parts. This counter represents the lower part of the 62 least significant bits of the high capacity counter for octets transmitted out on the interface. The two most significant bits of this 64 bit counter are discarded. This 64-bit counter is presented as 2*31 bits: pmIfOutOctetsHi (bit 61-31) and pmIfOutOctetsLo (bit 30-0) in the MOM. Condition: An octet is transmitted. Counter is reset after measurement period: Yes Counter type: PEG Unit: Number of octets Specification: RFC 2863



"

  


  
  
"

pmNoActive10msFramesEul Sum of used 10 ms frames (TTI) that receive E-DCH data in a cell during an ROP for all E-DCH users, excluding frames that are not decoded due to lack of hardware. Counter type: Peg Counter is reset after measurement interval: Yes Condition: Every 10 ms TTI that receives E-DCH data that is active, excluding frames that are not decoded due to lack of hardware. The actual measurement is started when the EUL resources are setup. Undefined value: -1

"

  


  
  
"

pmNoActive10msIntervalsEulTti10 Counter for the total amount of 10 ms intervals in a cell in which the transmission of one or more E-DCH frames has been detected, exluding frames that are not decoded due to lack of hardware to decode the frame. Counter type: Peg Counter is reset after measurement interval: Yes Condition: Stepped every 10 ms for 10 ms TTI users on the reception of any MAC-e PDU in the last 10 ms. Frames that are not decoded due to lack of hardware to decode the frame are excluded from contributing to the count. The actual measurement is started when the EUL resources are setup. Undefined value: -1

"

  


  
  
"

pmNoActive2msFramesEul Sum of used 2 ms frames (TTI) that receive E-DCH data in a cell during an ROP for all E-DCH users, excluding frames that are not decoded due to lack of hardware. Counter type: Peg Counter is reset after measurement interval: Yes Condition: Every 2 ms TTI that receives E-DCH data that is active. Note that if e.g. 3 users transmit during a specific 2 ms period, the counter will be incremented by 3. Undefined value: -1

"

  


  
  
"

pmNoActive2msIntervalsEul Counter for the total amount of 2 ms intervals in a cell in which the transmission of one or more E-DCH frames has been detected, excluding frames that are not decoded due to lack of hardware to decode the frame. Counter type: Peg Counter is reset after measurement interval: Yes Condition: Stepped after a successful decoding of a MAC-

e frame. Counted for both 10 ms TTI and 2 ms TTI users. Frames that are not decoded due to lack of hardware to decode the frame are excluded from contributing to the count. A 10 ms frame is counted as 5 intervals and a 2 ms frame is counted as 1 interval. Note that no interval may be counted more than once. The actual measurement is started when the EUL resources are setup. Undefined value: -1 "

  


  
  
"

pmNoActive2msIntervalsEulTti2 Counter for the total amount of 2 ms intervals in a cell in which the transmission of one or more E-DCH frames has been detected, excluding frames that are not decoded due to lack of hardware to decode the frame. Counter type: Peg Counter is reset after measurement interval: Yes Condition: Stepped every 2 ms for 2 ms TTI users on the reception of any MAC-e PDU in the last 2 ms. Frames that are not decoded due to lack of hardware to decode the frame are excluded from contributing to the count. The actual measurement is started when the EUL resources are setup. Undefined value: -1

 pmNoActive2msFramesEul "
 Sum of used 2 ms frames (TTI) that receive E-DCH data in a cell
  
 during an ROP for all E-DCH users, excluding frames that are not

  
 decoded due to lack of hardware.  
" Counter type: Peg Counter is reset after measurement interval: Yes Condition: Every 2 ms TTI that receives E-DCH data that is active. Note that if e.g. 3 users transmit during a specific 2 ms period, the counter will be incremented by 3. Undefined value: -1

 pmSumAckedBitsCellEulTti10 "
 Counter for the total amount of acked data received in kbits after
  
 HARQ process on MAC-e level for all 10 ms TTI users in a cell. Note

  
 that k = 1000.  
" Counter type: Peg Counter is reset after measurement interval: Yes Condition: Stepped every 10 ms for 10 ms TTI users when received data are acknowledged after HARQ process. The actual measurement is started when the EUL resources are setup.

Unit: kbits Undefined value: -1

 pmSumAckedBitsCellEulTti2 "
 Counter for the total amount of acked data received in kbits after
  
 HARQ process on MAC-e level for all 2 ms TTI users in a cell. Note

  
 that k = 1000.  
" Counter type: Peg Counter is reset after measurement interval: Yes Condition: Stepped every 2 ms for 2 ms TTI users when received data are acknowledged after HARQ process. The actual measurement is started when the EUL resources are setup. Unit: kbits Undefined value: -1