Salam,

Below 4 topic related to formula that should be discussed.

 GSM Call queuing

 LTE Drop with Huawei MME.
 GSM Drop formula
 3G CSSR when URA activated

1. GSM Call queuing

The legacy GSM congestion formulas don’t includes released SDCCH connection from the queue when MS Call
Queuing is activated, this release is perceived by the customer.
There is another way to calculate congestion, which is Hard Congestion that count only released SDCCH due to radio
resource congestion.
Ericsson recommendation for this formula when queuing is activated is to make the sum of CNRLCONG & RQT11CNT

Feature was activated in one node from Mobilis network in 2013, Below impact. It is clear that we do not consider
the RQT11CNT, feature activation shows good improvement.

In Huawei, below timer expiry counters when GSM Call queuing is activated should be considered if the feature is
active.

Counter ID : 1278478423
In an assignment procedure or incoming-BSC handover procedure, the MSC requests a TCH, but the BSC finds no
TCH available for assignment. If both the BSC and the call support preemption, the BSC performs the preemption
procedure. If the preemption is successful and the system supports queuing, the queuing procedure is performed.
Meanwhile, the related timer is triggered to wait for an idle TCH. When the timer expires, the measurement of the
counter R3136:CELL.QUEUE.FAIL.TIMES.PREEMPTION is triggered.

Counter ID : 1278478424
In the assignment procedure or incoming-BSC handover procedure, the MSC requests a TCH, but the BSC finds no
TCH available for assignment. If the BSC does not perform the preemption procedure or dynamic adjustment
procedure and if the BSC supports queuing, the call queuing procedure is performed. Meanwhile, the related timer is
triggered to wait for an idle TCH. When the timer expires, the measurement of the counter
R3137:CELL.QUEUE.FAIL.TIMES.TIMEOUT is triggered.

Counter ID : 1278478425
In the assignment procedure or incoming-BSC handover procedure, the MSC requests a TCHF or a TCHH, but the BSC
finds no TCHF or TCHH available for assignment. If the BSC supports dynamic adjustment procedure and if the
conditions for dynamic adjustment are met, the BSC performs the dynamic adjustment procedure. If the BSC also
supports queuing, the call queuing procedure is performed. Meanwhile, the related timer is triggered to wait for an
idle TCHF or TCHH. When the timer expires, the measurement of the counter
R3138:CELL.QUEUE.FAIL.TIMES.DYNADJ.TIMEOUT is triggered.

2. LTE Drop with Huawei MME.

Observation shows that in Erbs under Huawei MME there is negligible drops compared to the ones connected to
Ericsson MME.
Investigation done to catch problematic scenario which Huawei MME considering it as “NORMAL RELEASE”

1 - UE is connected to S-eNB and has active UE_context

2 - Due to problem in radio, UE will initiate RRC-Connection-reestablishmentrequest with T-eNB
3 - If T-eNB would reject the RRC-Connection-reestablishment-request, the UE will initiate new radio connection with
T-eNB
4 - UE sends Initial_UE_message to the MME through T-eNB
5 - Huawei MME would find this UE already has active UE-Context, so will send UE_context_release_command with
“normal release’ to S-eNB. The same scenario under Ericsson MME is considered as drop as Ericsson MME is sending
release command to S-eNB with cause: release-due-to eutran-generated-reason and considered as drop call/session
in S-eNB.

Region Earb Drop % pmErabRelAbnormalEnbAct pmErabRelAbnormalMmeAct

Ain Defla 0.46 4399 7691
Algiers 1.07 347493 564299
BBA 0.31 31751 0
Bejaia 0.25 16710 0
Blida 0.63 38579 73123
Bouira 0.31 4259 0
Boumerdes 1.07 70939 63758
Chlef 0.41 6046 9731
Constantine 0.23 34677 0
Jijel 0.17 7261 0
Setif 0.18 15538 0
Tipaza 0.55 30299 46552
Tizi 0.60 26798 46785

The cause code sent by Ericsson MME is more suitable and matching the radio link failure scenario observed in the
network, where the one used by Huawei MME gives false interpretation that everything is fine in network while
actually it is NOT.
For fair KPIs benchmark, it is highly recommended to have an unified formula that gives same measure of drop
between Erbs of Ericsson in different region, and between different regions vendors.
Counter pmErabRelAbnormalMmeAct should be removed from Earb Drop %
 3. GSM Drop formula:

Ericsson Speech Drop Counter TxNDROP

The counters are incremented when a connection is dropped after one of the messages 44.018 ASSIGNMENT
COMPLETE or 44.018 HANDOVER COMPLETE is received by the BSC, or the message 08.06 SCCP CONNECTION
CONFIRMED is received by the BSC during Immediate Assignment on TCH
This counter also counts the dropped call EVEN if the B – party has already released the call – as the network has
“dropped” the connection I.E when “CLEAR COMMAND” is received from MSC to BSC

TxNCEDROP (User perceived dropped call counters)

The counters are incremented when a connection is dropped after any of the three messages 44.018 ASSIGNMENT
COMPLETE, 44.018 HANDOVER COMPLETE, 44.018 CHANNEL MODE MODIFY ACKNOWLEDGE and before one of the
DTAP messages 24.008 RELEASE or 24.008 DISCONNECT is received by the BSC.

Huawei Speech Drop Counter CELL_TRAF_CH_CALL_DROPS (CM33)

This counter provides the number of call drops due to various reasons after the MS seizes a traffic channel. The MS
seizures a traffic channel in any of the following conditions:
1) The MS sends an ASS CMP message to the BSC
2) The MS sends an HO CMP message to the BSC and seizes a traffic channel and and before the BSC receives the
CLEAR CMD message from the MSC
This is on the clear request from the BSC to the core network
CM33:Call Drops on Traffic Channel =
CM330:Call Drops on Radio Interface in Stable State (Traffic Channel)+
CM331:Call Drops on Radio Interface in Handover State (Traffic Channel)
Huawei also has another dropped call counter CM3303A – this is the closest to TxNCEDROP for Ericsson
In order to have comparable drop call rate calculations between the two radio vendor, the following Dropped Call
Rate definition should be used for Ericsson to compare to Huawei CM3303A:

(TFNCEDROP+TFNCEDROPSUB+THCENDROP+THNCEDROPSUB)/(TFNCEDROP+TFNCEDROPSUB+THNCEDROP+THNCE
DROPSUB + DISNORM)

Huawei counters pegging:

Below comparison between the legacy formula and the proposed one to map Huawei pegging
 4. 3G CSSR when URA activated.

Ericsson recommends to replace accessibility indicators with the following two given, due to approximative 70%
decrease in RRC establishment from idle replaced by up-switch from URA.

PS RRC : =100*((<ReqPsSucc>+<pmChSwitchSuccUraFach>)/(<ReqPs>+<pmChSwitchAttemptUraFach>-
<pmNoLoadSharingRrcConnPs>))
PS RAB :
=100*((<pmNoRabEstSuccessPsIntNonHs>+<pmNoRabEstablishSuccess.PacketInteractiveHs>+<pmChSwitchSuccUra
Fach>)/
(<pmNoRabEstAttemptPsIntNonHs>+<pmNoRabEstablishAttempt.PacketInteractiveHs>+<pmChSwitchAttemptUraFa
ch>))

Below impact of Activation in one Node from Mobilis.

Regards,
El Habri BENZEGUIR
Radio Optimization Engineer
00 231 661 91 0682
Ext: 2250