View
128
Download
6
Category
Tags:
Preview:
Citation preview
EVDO Rev A KPI
ZTE University
Content
Call Processing KPI
RAN Performance KPI
Call Processing KPI
1x EVDO Session Setup Time
AT Initiated Connection Setup Time
AN Initiated Connection Setup Time PPP Session Setup
Time
PPP Setup Failure Rate
1x EVDO Session Setup Time(1)
Definition
The interval of AT sending UATIRequest to receiving
ConfigurationComplete
Actual Test Results:
Qualcomm’s recommended value: 90% test results are less
than or equal to 3000ms
Actual test: 2200~2700ms (on average)
1x EVDO Session Setup Time(2)
Flow chart
AT Initiated Connection Setup Time(1)
Definition
The interval from AT sending ConnectionRequest to
receiving TrafficChannelComplete
Actual test results:
Qualcomm’s recommended value: 90% test results are less
than or equal to 1000ms
Actual test: 300~400ms (on average)
AT Initiated Connection Setup Time(2)
Flow chart
AN Initiated Connection Setup Time
Definition
The interval from AN sending Page to receiving
TrafficChannelComplete
Actual Test Results:
Qualcomm’s recommended value: 90% test results are less
than or equal to 5000ms
Actual test: 1780ms (on average)
AN Initiated Connection Setup Time
PPP Session Setup Time(1)
Definition
The interval from AN sending the first LCP Config Req to
receiving the last IPCP Config Ack
Actual Test Results:
Qualcomm’s recommended value: 90% test results are less
than or equal to 1500ms
Actual test: 600~900ms (on average)
PPP Session Setup Time(2)
PPP Setup Failure Rate
Definition
Num of failed PPP setups / num of total PPP setup
attempts
Actual Test Results:
ZTE’s recommended value: <3%
Actual test: 0%
Content
Call Processing KPI
RAN Performance KPI
RAN Performance KPI
Call KPI
Call Drop KPI
Reverse Handoff KPI
Virtual handoff KPI
Release KPI
Session KPI
Call KPI (1)
AT Originated Connection Flow:
Call KPI (2)
AN Originated Connection Flow:
Call KPI (3)
AT Originated Fast Connection Flow:
Call KPI (4)
Fast connection refers to the following:
Only AN originates fast connection.
Fast connection does not need signaling of the
Page/ConnectionRequest message.
AN may select whether to support fast connection, while AT
must support it.
AN originates fast connection only when AN can measure
the current position of AT.
Call KPI (5)
Call KPI needs to collect the following variables.
CMO_CallTotalNum: Total number of AT call
CMO_CallSNum: Success number of AT originating call
CMO_ExtInterruptNum: External interruption number of AT originating call
CMO_BlockFNum: Failure number of AT originating call blocked
CMO_OtherFNum: Other failure number of AT originating call
CMT_CallTotalNum: Total number of AN originating call
CMT_CallSNum: Success number of AN originating call
CMT_ExtInterruptNum: External interruption number of AN originating call
CMT_BlockFNum: Failure number of AN originating call blocked
CMT_OtherFNum: Other failure number of AN originating call
FMT_CallTotalNum: Total number of fast originating call
FMT_CallSNum: Success number of fast originating call
FMT_ExtInterruptNum: External interruption number of fast originating call
FMT_BlockFNum: Failure number of fast originating call blocked
FMT_OtherFNum: Other failure number of fast originating call
Call KPI (6)
Statistical method:
CMO_CallTotalNum: At Counter 1, when AN receives
ConnectionRequest and successfully sends AcAck,
CMO_CallTotalNum is reported.
CMO_CallSNum: At Counter 2, when AN receives
TrafficChannelComplete, CMO_CallSNum is reported.
CMO_ExtInterruptNum: When AN receives ReleaseRequest from
AT or PDSN, CMO_ExtInterruptNum is reported.
CMO_BlockFNum: When resource shortage (including CE,
MacIndex and power) results in connection failure,
CMO_BlockFNum is reported.
CMO_OtherFNum: When some unknown causes result in
connection failure, CMO_OtherFNum is reported.
Call KPI (7)
Statistical method:
CMT_CallTotalNum: At Counter 3, when AN sends Paging and receives
ConnectionRequest from AT, CMT_CallTotalNum is reported.
CMT_CallSNum: At Counter 4, the method is same as AT’s related index.
CMT_ExtInterruptNum: The method is same as AT’s related index.
CMT_BlockFNum: The method is same as AT’s related index.
CMT_OtherFNum: The method is same as AT’s related index.
FMT_CallTotalNum: At Counter 5, when AN directly establishes
connection and assigns resource to AT without sending Page,
FMT_CallTotalNum is reported.
FMT_CallSNum: At Counter 6, the method is same as AT’s related index
FMT_ExtInterruptNum:The method is same as AT’s related index
FMT_BlockFNum: The method is same as AT’s related index
FMT_OtherFNum: The method is same as AT’s related index
Call KPI (8)
KPI Calculation Formula
Call Success Rate = (CMO_CallSNum +CMT_CallSNum +
FMT_CallSNum) / (CMT_CallTotalNum+ CMT_CallTotalNum
+FMT_CallTotalNum)
External Interruption Rate = (CMO_ExtInterruptNum +
CMT_ExtInterruptNum + FMT_ExtInterruptNum)
/( CMT_CallTotalNum+ CMT_CallTotalNum +FMT_CallTotalNum)
Call Failure Rate = (CMO_BlockFNum + CMO_OtherFNum +
CMT_BlockFNum + CMT_OtherFNum + FMT_BlockFNum +
FMT_OtherFNum) /( CMT_CallTotalNum+ CMT_CallTotalNum
+FMT_CallTotalNum)
Call KPI (9)
Qualcomm’s recommended value:
Call Success Rate > 95%
OMC’s statistical index:
Service Object Call Success Rate External Interruption Call Failure Rate
Czechic 98.834 0.002 0.644
Morocco 97.976 0.021 1.850
Esthonia 99.101 0.000 0.856
G-Mobile 96.570 0.004 3.154
SKYTEL 97.940 0.121 1.364
Reverse Handoff KPI (1)
Reverse handoff flow:
Reverse Handoff KPI (2)
Reverse handoff KPI needs to collect the following
variables.
SFT_HoRNum: Soft handoff request number
SFT_HoSNum: Soft handoff success number
SFR_HoRNum: Softer handoff request number
SFR_HoSNum:Softer handoff success number
IFR_HoRNum: Frequency-change handoff request number
IFR_HoSNum:Frequency-change handoff success number
Reverse Handoff KPI (3)
Statistical method:
SFT_HoRNum : At Counter 1, under the connection status, when AN receives
RouteUpdate and handoff requests between BTSs, SFT_HoRNum is reported.
SFT_HoSNum : At Counter 2, under the connection status, when AN perform
software handoff and receives TrafficChannelComplete, SFT_HoSNum is reported.
SFR_HoRNum : At Counter 1, under the connection status, when AN receives
RouteUpdate and handoff requests of different sectors in one BTS, SFR_HoRNum is
reported.
SFR_HoSNum : At Counter 2, under the connection status, when AN performs
softer handoff and receives TrafficChannelComplete, SFR_HoSNum is reported.
IFR_HoRNum : At Counter 1, under the connection staus, when AN receives
RouteUpdate and handoff requests of different frequency points in BTSs,
IFR_HoRNum is reported.
IFR_HoSNum : At Counter 2, under the connection status, when AN performs
frequency-change handoff and receives TrafficChannelComplete, IFR_HoSNum is
reported.
Reverse Handoff KPI (4)
KPI Calculation Formula
Reverse Handoff Success Rate = (SFT_HoSNum+ SFR_HoSNum+
IFR_HoSNum)/ (SFT_HoRNum+ SFR_HoRNum+ IFR_HoRNum)
Qualcomm’s recommended value:
Reverse Handoff Success Rate > 95%
OMC’s statistical index:
Service Object Reverse Handoff Success Rate
Czechic 97.829
Morocco 95.596
Esthonia 97.394
G-Mobile 99.031
SKYTEL 96.094
Virtual Handoff KPI (1)
Virtual handoff KPI needs to collect the following
variables.
SFT_HoSNum: Virual soft handoff success number
SFT_HoFNum: Virtual soft handoff failure number
SFR_HoSNum: Virtual softer handoff success number
SFR_HoFNum: Virtual softer handoff failure number
IFR_HoSNum: Virtual frequency-change handoff success
number
IFR_HoFNum: Virtual frequency-change handoff failure
number
Virtual Handoff KPI (2)
Statistical method:
SFT_HoSNum: When AN requests handoff from the source sector to the
target sector after capturing DRC from AT, and successfully acquires
service from the target sector, SFT_HoSNum is reported.
SFT_HoFNum: When AN requests handoff from the source sector to the
target sector after capturing DRC from AT, and fails to acquires service
from the target sector, SFT_HoFNum is reported.
SFR_HoSNum: It is similar to virtual soft handoff, but handoff occurs under
different sectors of the same BTS.
SFR_HoFNum: It is similar to virtual soft handoff, but handoff occurs under
different sectors of the same BTS.
IFR_HoSNum: It is similar to virtual soft handoff, but the frequency point is
different.
IFR_HoFNum: It is similar to virtual soft handoff, but the frequency point is
different.
Virtual Handoff KPI (3)
KPI Calculation Formula
Virtual Handoff Success Rate = (SFT_HoSNum+ SFR_HoSNum+
IFR_HoSNum)/ (SFT_HoSNum+ SFR_HoSNum+ IFR_HoSNum+
SFT_HoFNum+ SFR_HoFNum+ IFR_HoSNum)
OMC’s statistical index:
Service Object Virtual Handoff Success Rate
Czechic 99.981
Morocco 100.000
Esthonia 99.999
G-Mobile 100.000
SKYTEL 100.000
Release VPI (1)
AT Originated Release Flow
Release VPI (2)
AN Originated Release Flow
Release VPI (3)
Release KPI needs to collect the following variables.
CMO_RlsSNum: Normal release number of AT originating call
CMO_SystemFNum: System call drop number of AT originating
call
CMO_RadioFNum: Radio call drop number of AT originating call
CMT_RlsSNum: Normal release number of AN originating call
CMT_SystemFNum: System call drop number of AN originating
call
CMT_RadioFNum: Radio call drop number of AN originating call
FMT_RlsSNum: Normal release number of fast call
FMT_SystemFNum: System call drop number of fast call
FMT_RadioFNum: Radio call drop number of fast call
Release VPI (4)
Statistical method:
RlsSNum: Normal release causes include the following,
such as AT sending ConnectionClose, time out of dormant
timer, negotiation success but authentication failure,
resource shortage at PDSN. AN will report RlsSNum when
these kinds of release flows are completed.
SystemFNum: When abnormal connection interruption is
caused by the system fault, such as overload,
SystemFNum is reported.
RadioFNum: When abnormal connection interruption is
caused by the radio link fault, RadioFNum is reported.
Release VPI (5)
KPI Calculation Formula
System Call Drop Rate = SystemFNum/(RlsSNum+
SystemFNum+ RadioFNum)
Radio Call Drop Rate = RadioFNum /(RlsSNum+
SystemFNum+ RadioFNum)
Session KPI (1)
Session Establishment Flow
Session KPI (2)
Statistical method:
SessionSetupAttempNum: At Counter 1, when AN receives
UATIRequest from AT, SessionSetupAttempNum is
reported.
SessionSetupSNum: At Counter 2, when AN receives
UATIComplete, SessionSetupSNum is reported.
SessionNegoSNum: At Counter 3, when negotiation is
completed and AN successfully sends
ConfigurationComplete, SessionNegoSNum is reported.
Session KPI (2)
KPI Calculation Formula
Session Setup Success Rate = SessionSetupSNum/
SessionSetupAttempNum
Session Negotiation Success Rate = SessionNegoSNum
/SessionSetupSNum
OMC’s statistical index:
Service Object Session Setup Success Rate Session Negotiation Success Rate
Czechic 97.761 97.720
Morocco 92.717 98.897
Esthonia 88.880 97.880
G-Mobile 99.909 99.901
SKYTEL 98.267 66.695
Recommended