Professional Documents
Culture Documents
2020-11-10 HUAWEI Confidential Page1, Total11
2020-11-10 HUAWEI Confidential Page1, Total11
2020-11-10 HUAWEI Confidential Page1, Total11
The CSR and ASR for these 3 kinds of call are as below:
1.1. Formula:
CSR=Call Completion Times/Call attempts*100%
ASR=Answer Times/Call attempts*100%
1.1.1. Call completion times
Description
This measurement entity counts the number of put-through calls originated by local 2G
subscribers. A call is considered to be put through if the callee is alerted.
Application Scenario
Create a measurement task with this measurement entity to learn the number of put-through
calls originated by local 2G subscribers.
Unit
None
Measurement Point
The local MSC sends an Alerting message to the originating MS. For details, see Figure 1.
If the call is an inter-MSC call, the local MSC sends an Alerting message to the originating MS
only when it receives an ACM message from the terminating MS. If the call is an intra-MSC
call, the local MSC sends an Alerting message to the originating MS only when it receives an
Alerting message from the terminating MS.
This measurement entity counts the number of call attempts made by local 2G subscribers.
By analyzing the measurement result, you can learn the statistics about the following types of
MOC attempts in the local MSC area.
Application Scenario
During network migration and upgrade, create a measurement task with this measurement
entity to learn the number of call attempts made by local 2G subscribers.
Unit
None
Measurement Point
In the normal service procedure, the local MSC receives a CM SERVICE REQUEST
message from the originating BSC.
In the CM-incurred call re-establishment or MPTY service procedure, the local MSC
receives a DTAP CM SERVICE REQUEST message from the originating BSC.
This measurement entity counts the number of answered calls originated by local 2G
subscribers.
Application Scenario
Create a measurement task with this measurement entity to learn the number of answered
calls originated by local 2G subscribers.
Unit
None
Measurement Point
If the call is an inter-MSC call, the measurement starts when the local MSC sends a
CONNECT message to the originating MS after receiving the ANC/ANN or ANM message
from the VMSC. If the call is an intra-MSC call, the measurement starts when the local MSC
This measurement entity counts the number of put-through calls originated by local 3G
subscribers. A call is considered to be put through if the callee is alerted.
Application Scenario
Create a measurement task with this measurement entity to learn the number of put-through
calls originated by local 3G subscribers.
Unit
None
Measurement Point
If the call is an inter-MSC call, the measurement starts when the local MSC receives an ACM
message from the terminating MSC. If the call is an intra-MSC call, the measurement starts
when the local MSC sends an ALERTING message to the originating MS after receiving the
ALERTING message from the terminating MS. For details, see Figure 1.
This measurement entity counts the number of call attempts made by local 3G subscribers.
By analyzing the measurement result, you can learn the statistics about the following types of
MOC attempts in the local MSC area:
Application Scenario
During network migration and upgrade, create a measurement task with this measurement
entity to learn the number of call attempts made by local 3G subscribers.
Unit
None
Measurement Point
In the normal service procedure, the local MSC receives a CM SERVICE REQUEST
message from the originating RNC.
In the ICA service procedure, the local MSC receives an ICA message from the SCP.
Application Scenario
Create a measurement task with this measurement entity to learn the number of answered
calls originated by local 3G subscribers.
Unit
None
Measurement Point
If the call is an inter-MSC call, the measurement starts when the local MSCa receives a TUP
ANC or an ISUP ANN message from the terminating MSCb and then sends a CONNECT
message to the originating RNC. If the call is an intra-MSC call, the measurement starts when
the local MSC receives a CONNECT message from the terminating MS/UE and then sends a
CONNECT message to the originating RNC. For details of inter-MSC call,seeFigure 1.For
details of intra-MSC call, see Figure 2.
This measurement entity counts the number of put-through inter-MSC calls to the local MSC.
A call is considered to be put through if the callee is alerted.
Application Scenario
Create a measurement task with this measurement entity to learn the number of put-through
inter-MSC calls to the local MSC.
Unit
None
Measurement Point
The local MSC (MSCb) sends a TUP ACM, an ISUP ACM, an R2 LINE_STAUS_IND, a PRA
ALERTING, a BICC ACM, a SIP 180 message to MSCa. For details, see Figure 1.
This measurement entity counts the number of successful attempts to seize trunks for inter-
MSC calls to the local MSC.
Application Scenario
Unit
None
Measurement Point
The local MSC (MSCb) receives a TUP IAI, an ISUP IAM, an R2 SEIZE, a PRA SETUP, a
BICC IAM, or a SIP INVITE message from MSCa. For details, see Figure 1.
This measurement entity counts the number of answered inter-MSC calls to the local MSC.
Application Scenario
Create a measurement task with this measurement entity to learn the number of answered
inter-MSC calls to the local MSC or the frequency of local subscriber participation in
conversation.
Unit
None
Measurement Point
The local MSC(MSCb) sends a TUP ANC, an ISUP ANM, an R2 ANSWER, a PRA
CONNECT, a BICC ANM, or a SIP 200 message to the peer MSC(MSCa). For details, see
Figure 1.
Remark:
The CSR formula for other performance report are the same, such as Trunk office direction,
outgoing call and on.
CSR=completion times or alert times/attempt times or seizure times*100%