GPEH
For Ericsson, we use GPEH files (General Perforamance Event Handling). Below we describe how each event is detected.
| Name | How to detect? |
| DNS_RSCP_AVG DNS_RSCP_MAX DNS_ECNO_AVG DNS_ECNO_MAX |
extracted from RRC message “rrcMeasurementReport” (UL DCCH) |
| DNS_VOICE_CALL_START EVT_VOICE_CALL_START |
detected from GPEH event “RRC_DOWNLINK_DIRECT_TRANSFER”
where NAS protocol = 3 (“Call Control”) and NAS service type = 1 (“mobile terminated call”) and NAS message type is or 5 CC_SETUP or 15 – “CC_CONNECT_ACKNOWLEDGE”. OR where NAS protocol = 3 (“Call Control”) and NAS service type = 0 (“mobile originated call”) and NAS message type is 2 – “CC_CALL_PROCEEDING” or 3 -“CC_PROGRESS” detected from GPEH event “RRC_UPLINK_DIRECT_TRANSFER” where NAS protocol = 3 (“Call Control”) and NAS service type = 1 (“mobile terminated call”) and NAS message type is 1 -CC_ALERTING or 7 – “CC_CONNECT” or 8 – CC_CALL_CONFIRMED. OR where NAS protocol = 3 (“Call Control”) and NAS service type = 0 (“mobile originated call”) and NAS message type is 5 CC_SETUP |
| DNS_PACKET_CALL_START EVT_PACKET_CALL_START | detected from GPEH event “RRC_INITIAL_DIRECT_TRANSFER”
where NAS protocol = 8 (“GPRS mobility management”) and NAS message type = 12 (“service request”) and NAS service type = 8 (“data”) |
| DNS_SPEECH_DROP_CALL EVT_SPEECH_DROP_CALL | detected from GPEH “RANAP event”
where ranapCause is RANAP_IU_RELEASE_COMMAND and its value is not 11,16,31,40,41 or 46 and call is PS |
| DNS_PS_DROP_CALL EVT_PS_DROP_CALL |
detected from GPEH “RANAP event”
where ranapCause is RANAP_IU_RELEASE_COMMAND and its value is not 11,16,31,40 or 41 and call is mobile originated or terminated and call is not PS |
| DNS_LOCATION_AREA_UPDATE EVT_LOCATION_AREA_UPDATE | detected from GPEH event “RRC_INITIAL_DIRECT_TRANSFER”
where NAS protocol = 5 (“mobility management”) and NAS message type = 8 (“location updating request”) |
| DNS_ROUTING_AREA_UPDATE EVT_ROUTING_AREA_UPDATE | detected from GPEH event “RRC_INITIAL_DIRECT_TRANSFER”
where NAS protocol = 8 (“GPRS mobility management”) and NAS message type = 8 (“routing area update request”) |
| DNS_RRC_CONNECTION_REQUEST EVT_RRC_CONNECTION_REQUEST | detected from RRC message “rrcConnectionRequest” (UL CCCH) additional information: “establishmentCause” |
| DNS_RRC_CONNECTION_RELEASE EVT_RRC_CONNECTION_RELEASE | detected from RRC message “rrcConnectionRelease” (DL CCCH) additional information: “releaseCause” |
| DNS_RRC_CONNECTION_REJECT EVT_RRC_CONNECTION_REJECT | detected from RRC message “rrcConnectionReject” (DL CCCH) additional information: “RejectionCause” |
| DNS_SOFT_HO_EXECUTION EVT_SOFT_HO_EXECUTION | detected from GPEH message “INTERNAL_SOFT_HANDOVER_EXECUTION” |
| DNS_IRAT_HO_CC_EXECUTION EVT_IRAT_HO_CC_EXECUTION |
detected from GPEH message “INTERNAL_IRAT_HO_CC_EXECUTION” |
| DNS_PS_DATA_VOLUME | detected from GPEH message “INTERNAL_PACKET_DEDICATED_THROUGHPUT”
The event periodically (every two seconds) reports the UL/DL data rate. The used counters are EVENT_PARAM_UL_USER_THROUGHPUT and EVENT_PARAM_DL_USER_THROUGHPUT. Throughput is in Kbits/s. |
| DNS _THROUGHPUT_DL DNS _THROUGHPUT_UL |
detected from GPEH message “INTERNAL_PACKET_DEDICATED_THROUGHPUT”
The event periodically (every two seconds) reports the UL/DL data rate. The used counters are EVENT_PARAM_UL_USER_THROUGHPUT and EVENT_PARAM_DL_USER_THROUGHPUT. |