ALu Seminar RX ACCH

B11 MR1 Ed1.x / Ed2.
x Seminar of GSM Network Engineering
Repeated ACCH
Jorge S. Silva, Philip Fawzy, Robin Brassac March, 2010
Agenda 1. Feature Overview Introduction Repeated DL FACCH Repeated UL SACCH Expected Gains and Limitations 2. Activation Strategy Pre-requisites Parameter settings 3. Feature Assessment Theoretical gains Impact of other features on performance
New Counter and Indicators
Monitoring method FOA tests results 4. Conclusion
2 | Repeated ACCH
All Rights Reserved Alcatel-Lucent 2009
1
3 | Repeated ACCH
Feature Overview
1.1
4 | Repeated ACCH
Feature Overview Introduction
Feature Overview Introduction Feature objectives Close performance gap between AMR speech codecs and signaling channels
When AMR speech codecs were introduced, the same ACCH (Associated Control Channels) as those used for legacy codecs were re-used:
SACCH (Slow Associated Control Channel), which is used for non-urgent procedures (mainly for the transmission of the radio measurement data needed for handover decisions, power control, TA calculation), FACCH (Fast Associated Control Channel), which is involved in delay sensitive mechanisms such as handover.
Therefore, in poor radio conditions, the more protected AMR speech codecs have now better performance than the associated control channels and the end-user who would have hang-up with legacy codec does not do so anymore. Consequently, upon AMR activation in B9, we generally see CDR increase with following causes:
Radio link failure HO failure (timer expiry)
Enable operators to realize the full capacity gains that the lower modes of the AMR can provide.
5 | Repeated ACCH All Rights Reserved Alcatel-Lucent 2009
Feature Overview Introduction Feature description Repeated ACCH consists of two features:
Repeated Downlink FACCH (RDFACCH) Repeated SACCH (RSACCH)
Required by several operators:

SFR, T-Mobile, Orange.
6 | Repeated ACCH
Feature Overview Introduction Feature description Standardized in 3GPP Release 6:

MS capability indicated by the Repeated ACCH flag in classmark 3 message (1 bit field):
0 The mobile station does not support Repeated SACCH 1 The mobile station supports Repeated SACCH and Repeated Downlink FACCH
Support mandatory for Release 6 MS,

Some pre-release 6 MS may have the Repeated ACCH flag at 1, in this case they shall support completely the feature (RDFACCH and RSACCH).
Activated on a per-call basis.
7 | Repeated ACCH
1.2
8 | Repeated ACCH
Feature Overview Repeated DL FACCH
Feature Overview Repeated DL FACCH RDFACCH operation principles 3GPP standard The feature was designed to be compatible with legacy MS for LAPDm command frames. Criteria to activate RDFACCH is implementation dependent. The operations of RDFACCH are transparent to upper layers. Involved protocol stacks (in blue):
BTS LAPDm Physical Layer
Physical connection 3GPP TS 44.006
MS LAPDm Physical Layer
9 | Repeated ACCH
Feature Overview Repeated DL FACCH RDFACCH operation principles 3GPP standard BTS side (LAPDm entity) When RDFACCH is active, each LAPDm frame is repeated twice by BTS entity. The duplicated LAPDm frame is inserted in a FACCH frame that starts ~40ms after the FACCH frame conveying the original one.
In case of TCH/FR a speech frame is inserted
The transmission of the copy has higher priority than any new signaling message. I.e. if a new LAPDm message is generated between the emission of a previous LAPDm frame and its copy, its emission is delayed.
10 | Repeated ACCH
Feature Overview Repeated DL FACCH RDFACCH operation principles 3GPP standard Delay between original FACCH and its repetition TCH/FR case:
Original FACCH frame and copy spaced by 8 or 9 (in case they are separated by an idle frame or a SACCH period) TDMA frames.
1 radio TCH
Odd Even
~40 ms
Half FACCH burst of the first transmission Half FACCH burst of the repetition 1 radio TS Half TCH/FR burst Top: first half (before the training sequence), Half idle or SACCH burst Bottom: second half (after the training Odd Even sequence).
~40 ms
Half FACCH burst of the first transmission Half FACCH burst of the repetition Half FACCH burst of another signalling message Half FACCH burst of the repetition of another signalling message Half TCH/FR burst
11 | Repeated ACCH
Feature Overview Repeated DL FACCH RDFACCH operation principles 3GPP standard Delay between original FACCH and its repetition TCH/HR case:
Original FACCH frame and copy spaced by 8 or 9 (in case they are separated by a SACCH period) TDMA frames.
Odd Even
~40 ms
Half FACCH burst of the first transmission Half FACCH burst of the repetition Half TCH/HR burst
12 | Repeated ACCH
Feature Overview Repeated DL FACCH RDFACCH operation principles 3GPP standard MS side (Physical layer) The MS shall, when receiving a downlink FACCH block, always attempt to decode it without combining with any previously received FACCH block. If it is successfully decoded and an identical FACCH block was previously received, the MS shall not send the LAPDm frame of the current FACCH block to the LAPDm entity. If it is successfully decoded and there was no such previously received identical FACCH block, the LAPDm frame of the current FACCH block is sent to the LAPDm entity. If it is unsuccessfully decoded and the previous FACCH block received was unsuccessfully decoded, a new decoding using the information from both these FACCH blocks shall be performed. If this decoding is successful the LAPDm frame produced by the new decoding is sent to the LAPDm entity.
Feature Overview Repeated DL FACCH MS BTS Msg A Msg A Msg B Msg B

OK OK OK
Assumption: RDFACCH dynamically activated
Physical
decoding
LAPDm
Msg C Msg C
NOK NOK OK
Msg D Msg D
Soft combining
NOK OK
14 | Repeated ACCH
Feature Overview Repeated DL FACCH MS BTS Msg E Msg E

NOK
Physical
decoding
LAPDm
Msg F Msg F
NOK NOK NOK
Soft combining
15 | Repeated ACCH
Feature Overview Repeated DL FACCH RDFACCH operation principles ALU implementation Only AMR calls are concerned with the feature Criteria to dynamically activate RDFACCH:
RDFACCH allowed for this call AND AMR DL codec requested is configured threshold
Simple, Fast, autonomously managed by BTS RDFACCH application dependent upon Codec Mode Adaptation behavior
Every 480 ms, the BTS checks the last Codec Mode Request (CMR) used and decides whether RDFACCH shall be activate or not. NB: Codec Mode Request (CMR) is sent every 2 speech frames (i.e. every 40 ms) in UL by MS to TC. It is the input to the Codec Mode Adaptation in DL indeed, it specifies the codec recommended in DL, based on standardized C/I computations.
When RDFACCH is dynamically activated, T200 timers (T200_TF and T200_TH) in the BTS are increased by 40 ms.
16 | Repeated ACCH
Feature Overview Repeated DL FACCH RDFACCH dynamic activation in ALU implementation

Example with AMR-FR, 4-codec subset (AMR_FR_SUBSET) and Codec mode 2 REP_DL_FACCH_THRES_AMR_FR < Codec mode 3
AMR C/I RDFACCH active RDFACCH inactive
ST HY _ R _F R_3 R AM _TH + R _3 _F R R TH AM
Codec Mode 4
Better intrinsic voice quality
Codec Mode 3
_ FR _ R AM
Codec Mode 3
T YS H _ FR _2 _ R R AM _TH + R _2 _F R R T TH AM YS R_ H F R_ R_ _F R AM 1 AM R_ H + Codec T 1 R_ R_ F Mode 1+ H R_ _T M R A F RDFACCH R_ M A
Codec Mode 2 + RDFACCH
More robust
17 | Repeated ACCH
1.3
18 | Repeated ACCH
Feature Overview Repeated SACCH
Feature Overview Repeated SACCH RSACCH operation principles 3GPP standard Applies only to SAPI 0 frames
SAPI 3 frames are already acknowledged (SACCH frames with SAPI 3 frames are used to carry SMS while in dedicated mode).
Both DL and UL signaling links can be strengthened using repetition mechanism

SACCH Repetition Order (SRO) field defined in L1 header of DL SACCH frames SACCH Repetition Request (SRR) field defined in L1 header of UL SACCH frames SRO and SRR are a 1 bit field coded as follow:
0: Repeated SACCH not required 1: Repeated SACCH required
19 | Repeated ACCH
Feature Overview Repeated DL SACCH 3GPP Standard Repeated DL SACCH operation principles 3GPP standard MS side The MS shall first attempt to decode any DL SACCH block received without combining with previously received SACCH. If it is correctly decoded, the MS shall set the SRR to Not required in the next UL SACCH block (which is not a repetition). If it is incorrectly decoded, then:
The MS shall set the SRR to Required in the next UL SACCH block (which is not a repetition). It shall try decoding using soft combining with the previously received DL SACCH block.
20 | Repeated ACCH
Feature Overview Repeated DL SACCH 3GPP Standard Repeated DL SACCH operation principles 3GPP standard BSS side The BSS may, based on the value of the last correctly received SRR from the MS, and based on implementation-dependent criteria, repeat SACCH block at the next SACCH period. If a SAPI 3 frame was also scheduled to be sent at this next SACCH period, the BSS may delay the sending of the SAPI 3 frame by one SACCH period in order to make room for the repetition.
21 | Repeated ACCH
Feature Overview Repeated UL SACCH 3GPP Standard Repeated UL SACCH operation principles 3GPP standard BSS side The BSS shall first attempt to decode any UL SACCH block received without combining with previously received SACCH block.
If decoding fails, it may try decoding using soft combining with previous SACCH block received.
The BSS may set the value of the SRO in any DL SACCH block based on implementation-dependent criteria. MS side If in the last DL SACCH block, SRO was set to Required, the MS must repeat this block in the next SACCH period.
22 | Repeated ACCH
Feature Overview Repeated DL SACCH ALU Implementation RSACCH operation principles ALU implementation RDSACCH and RUSACCH are activated independently during a call. RDSACCH dynamic activation: Disabled at call start Activated when
RSACCH allowed for this call AND BS Radio Link Counter (RLC) configured threshold RadioLink_Rep_DL_SACCH OR at least Rep_DL_SACCH_Thres SACCH frames with SRR = 1 were received in the sliding window Rep_DL_SACCH_WS
While the feature is activated, all DL SACCH frames with SAPI = 0 are repeated once, independently of DL SACCHs being well decode or not at MS
Feature Overview Repeated DL SACCH ALU Implementation RSACCH operation principles ALU implementation RDSACCH dynamic activation: Deactivated when
BS Radio link Counter configured threshold (RadioLink_Rep_DL_SACCH) ] And less than Rep_DL_SACCH_Thres SACCH frames with SRR = 1 were received in the sliding window Rep_DL_SACCH_WS
24 | Repeated ACCH
Feature Overview Repeated UL SACCH ALU Implementation RSACCH operation principles ALU implementation RUSACCH dynamic activation (1/2): Disabled at call start Activated when:
At least Rep_UL_SACCH_Thres incorrect SACCH frames before combining, were received in the sliding window Rep_UL_SACCH_WS
While the feature is activated at BTS side and SRO field in DL SACCH is equal to one and well decoded at the MS, MS repeats previous UL SACCH frame with SAPI = 0, independently of previous UL SACCHs being well decoded or not at BTS. BTS must set SRO to one in each DL SACCH as long as feature is activated, so that MS is ordered to repeat UL SACCH frames once. However if SRO was not well decoded, the MS action will be mobile supplier dependent as this is not standardized.
Feature Overview Repeated UL SACCH ALU Implementation RSACCH operation principles ALU implementation RUSACCH dynamic activation (2/2): Deactivated when
Less than Rep_UL_SACCH_Thres incorrect SACCH frames before combining, were received in the sliding window Rep_UL_SACCH_WS
26 | Repeated ACCH
Feature Overview Repeated SACCH Illustrations RSACCH operation principles illustrations Next slides show several graphical examples of RSACCH activation
1. Degradation in DL and RDSACCH dynamic activation based on SRR 2. Degradation in UL and RUSACCH dynamic activation based on bad frames indications (BFI) and SRO
Assumptions
All SACCH frames are with SAPI = 0 Rep_DL_SACCH_WS = 10, Rep_DL_SACCH_Thres = 3 Rep_UL_SACCH_WS = 10, Rep_UL_SACCH_Thres = 3
27 | Repeated ACCH
Assumption: Result after soft Result of first decodingBTS = 10 Rep_DL_SACCH_WS combining, if applicable attempt BS side = 10 Rep_UL_SACCH_WS Call start Rep_DL_SACCH_Thres = 3 Rep_UL_SACCH_Thres =3 SRR count BFI count #1, SRO = 0 As UL Frame 0/1 N/A 0/1 OK was not #2, SRO = 0 decoded, soft 0/2 N/A 0/2 OK combining is Frame not #3, SRO = 0 tried decoded! SRR 0/3 NOK 1/3 NOK value of last #4, SRO = 0 correct frame is taken 0/4 N/A 1/4 OK #5, SRO = 0 Incremented 1/5 N/A 1/5 OK because SRR = 1 #6, SRO = 0 Incremented because SRR = 1 RDSACCH dynamically activated 2/6 2/7 3/8 4/9 5/10
28 | Repeated ACCH
Count of SRR = 1 in last Count of bad frames in last Feature Overview Rep_DL_SACCH_WS frames Rep_UL_SACCH_WS frames Repeated DL SACCH Illustrations Assumption:
According to spec, MS shall try soft combining Result of first decoding with previous Frame if MS attempt side current FrameMS is not decoded #1, SRR = 0 OK #2, SRR = 0 NOK #3, SRR = 1 OK #4, SRR = 0 Because last DL NOK #5, SRR = 1 SACCH frame not decoded NOK #6, SRR = 1 OK Possibility to #7, SRR = 0 have good NOK decoding due to #8, SRR repetition of = 1 message and NOK soft combining #9, SRR = 1 NOK #10, SRR = 1 OK NOK NOK NOK
N/A N/A N/A N/A N/A
1/6 1/7 1/8 1/9 1/10
OK OK OK OK OK
#7, SRO = 0 #8, SRO = 0 #8 repeated, SRO = 0 #9, SRO = 0
NOK NOK OK
Feature Overview Repeated UL SACCH Illustrations BTS

SRR count As UL Frame 0/1 was not decoded, soft 0/2 Frame not combining is decoded, SRR tried value of last 0/3 correct frame is taken 0/4 RUSACCH dynamically 0/5 activated Possibility to have good decoding due to repetition of message and soft combining 0/6 0/7 0/8 0/9 1/10
29 | Repeated ACCH
MS
#1, SRR = 0 OK #2, SRR = 0 NOK #3, SRR = 1 NOK
BFI count N/A N/A NOK N/A NOK NOK NOK OK NOK OK 0/1 0/2 1/3 1/4 2/5 3/6 4/7 5/8 6/9 7/10 OK OK NOK
#1, SRO = 0 #2, SRO = 0 #3, SRO = 0
OK #4, SRO = 0 SRO = 1, #4, SRR = 0 requesting the Because last DL OK OK UL frames #5, SRO = 0 SRRwas =0 SACCH#5, frame repetition not decoded NOK OK #6, SRO = 0 #6, SRR = 0 OK #7, SRO = 1 SRR = 1 because #7, SRR = 0 UL SACCH OK NOK frame is #8, SRO = 1 #7 repeated, SRR = 0 repeated NOK NOK #9, SRO = 1 #8, SRR = 1 NOK NOK #10, SRO = 1 OK #8 repeated, SRR = 1 OK NOK
NOK
1.4
30 | Repeated ACCH
Feature Overview Limitations
Feature Overview Limitations Theoretical limitations of the feature No Repeated UL FACCH has been defined.
Consequently, during multi-block HOs, the response from the MS to the BTS cannot be repeated and therefore, for these HOs the signaling link (in UL) has the same performances than legacy FACCH.
The feature is fully available (RDFACCH + RSACCH) on Release 6 MS only.

But RDFACCH can also be enabled for command frames for all MS.
31 | Repeated ACCH
Feature Overview Multi-Block Handovers Limitation Multi-block Handovers Length of LAPDm messages is fixed:
23 bytes for FACCH, with 20 bytes of payload 21 bytes for SACCH, with 18 bytes of payload
Some messages can exceed this limit in some cases. This is typically the case of intercell HO commands from TCH with legacy codec to AMR TCH. UL ACK is needed for the first block
32 | Repeated ACCH
2
33 | Repeated ACCH
Activation Strategy
2.1
34 | Repeated ACCH
Activation Strategy Pre-requisites
Activation Strategy
Pre-requisites AMR is activated in multi codec configuration using subset codecs containing codecs more robust than signaling codecs. Significant AMR calls penetration, which can be checked by the indicator; RTCH_assign_AMR_penetration_rate. Significant penetration of Repeated ACCH capable MS Checked through the new indicator; RxACCH_MS_Penetration_Rate. AMR Codec Subset and Codec Adaption thresholds should be optimized for area of feature activation Checked through the RMS report ; ALC_MONO_RMS_AMR Repeated ACCH feature is not supported by BSC G2.
35 | Repeated ACCH
2.2
36 | Repeated ACCH
Activation Strategy Parameter Settings
Activation Strategy
Parameter settings New parameters
Parameter Name
EN_REP_DL_FACCH
Definition Enables repeated downlink FACCH for AMR calls Legacy support for repeated downlink FACCH for AMR calls Remarks:
Instance Cell
Range/ Default value {0, 1, 2}1/0
Recommended Value 2
REP_DL_FACCH_LEGACY_SUPPORT
1. This parameter is relevant only if repeated downlink FACCH is enabled (EN_REP_DL_FACCH parameter) 2. This parameter concerns only the LAPDm command frames. Repeated DL FACCH activation threshold for AMR FR. Dynamic activation is done as long as codec mode request CMR threshold.
Cell
{0, 1}2/0
REP_DL_FACCH_THRES_AMR_FR
Cell
{0,1,...,8}3/ 3 3
1 0: 2 0:
disabled; 1: enabled for LAPDm command frames; 2: enabled for LAPDm command frames and also for response frames
repeated DL FACCH enabled only for AMR MS with repeated ACCH Capability bit = 1; 1: repeated DL FACCH enabled for all AMR MS 0: off; 1: 4,75 kbs; 2: 5,15 kbs ; 3: 5,90 kbs; 4: 6,70 kbs; 5: 7,40 kbs; 6: 7,95 kbs; 7: 10,2 kbs; 8: 12,2 kbs
Activation Strategy
Parameter Name Definition Repeated DL FACCH activation threshold for AMR HR. Dynamic activation is done as long as codec mode request CMR threshold. Repeated DL FACCH activation threshold for AMR WB. Dynamic activation is done as long as codec mode request CMR threshold. Instan Range/ Default ce value Cell {0,1,...,5}1/3 Recommended value 3
REP_DL_FACCH_THRES_AMR_HR
REP_DL_FACCH_THRES_AMR_WB
Cell
{0, 1, 2}2/1
NA
EN_REP_SACCH
RADIOLINK_REP_DL_SACCH
Enables repeated SACCH for SAPI 0 frames in case of AMR calls (for mobile station having indicated the support of Cell the feature). Repeated DL SACCH activation threshold for UL RLT (Radio Link Timer) counter. Dynamic activation is Cell triggered in the BTS when the UL RLT counter is inferior or equal to that threshold.
{0,1}/0
10 {0,...,127}/10 For RLT of 24
1 0: 2 0:
off; 1: 4,75 kbs; 2: 5,15 kbs ; 3: 5,90 kbs; 4: 6,70 kbs; 5: 7,40 kbs off; 1: 6,60 kbs; 2: 8,85 kbs ; 3: 12,65 kbs
38 | Repeated ACCH
Activation Strategy
Parameter Name Definition Lower uplink quality threshold for power control for AMR calls with activated Repeated DL FACCH and Repeated SACCH. Instance Range/ Default value Recommended values Equal to L_RXQUAL_UL_P or slightly higher Equal to L_RXQUAL_UL_P or slightly higher
L_RXQUAL_UL_P_AMR_RXACCH1
Cell
{0,...,7}/3
L_RXQUAL_DL_P_AMR_RXACCH1
Lower downlink quality threshold for power control for AMR calls with activated Repeated DL FACCH Cell and Repeated SACCH.
{0,...,7}/3
If the customer has customized parameter L_RXQUAL_xL_P (where x is U or D) in
the previous release, then the new parameter L_RXQUAL_xL_P_AMR_RXACCH must be updated in the CDE table with THAT customized value. To take benefit from the feature repeated ACCH, Alcatel-Lucent recommends: L_RXQUAL_UL_P_AMR_RXACCH L_RXQUAL_UL_P AND L_RXQUAL_DL_P_AMR_RXACCH L_RXQUAL_DL_P.
Activation Strategy
Parameter settings Modified parameters
Parameter Name Definition changes Instance Range/ Recommended Default value value
Counter threshold to detect a radio link failure on the uplink path for calls using an RADIOLINK_TIMEOUT_BS_AMR AMR codec and for which Repeated SACCH Cell and/or Repeated DL FACCH are not activated. RADIOLINK_TIMEOUT_BS1 Updated the definition: this timer can also be used for AMR calls (NB or WB) for which Cell Repeated SACCH and Repeated DL FACCH are activated Initial value of MS counter for radio link supervision, when an AMR codec is used and for which call Repeated SACCH and/or Cell Repeated DL FACCH are not activated. Updated the definition: this timer can also be used for AMR calls (NB or WB) for which Cell Repeated SACCH and Repeated DL FACCH are activated
{1,...,255}/18 32
{1,...,255}/18 NA
RADIOLINK_TIMEOUT_AMR1 RADIOLINK_TIMEOUT1 (BSC) This also applies to RADIOLINK_TIMEOUT1 (MFS)
{4,...,64}/16
32
{4,...,64}/16
NA
1 HMI
name for RADIOLINK_TIMEOUT_BS is RADIOLINK_FAILURE_THRES
HMI name for RADIOLINK_TIMEOUT_BS_AMR is RADIOLINK_FAILURE_THRES_AMR Coding rule for RADIOLINK_TIMEOUT and RADIOLINK_TIMEOUT_AMR is as follows: step size = 4 Samfr, coded from 0 to 15 (0 == 4 Samfr, 1 == 8 Samfr ... 15 == 64 Samfr)
3
41 | Repeated ACCH
Feature Assessment
3.1
42 | Repeated ACCH
Feature Assessment
Impact of other features on performance
Feature Assessment Impact of other features on performance RSACCH and RadioLink Supervision RadioLink supervision When a SACCH block is received a first decoding is performed without combining
1) If it is correct 2) If it fails block RLC is incremented by 2
new decoding performed using soft combining with previous SACCH
a) if it is correct RLC is incremented by 2 b) if it fails RLC is decremented by 1
43 | Repeated ACCH
Feature Overview Repeated SACCH & Radio Link Supervision RSACCH and RadioLink Supervision Interaction with RadioLink Timeout For an AMR call, when both RDFACCH and RSACCH are activated the legacy RadioLink Timeout is used i.e. the following parameters:
RADIOLINK_TIMEOUT RADIOLINK_TIMEOUT_BS
Differentiated RadioLink Timeout for AMR (RADIOLINK_TIMEOUT_AMR and RADIOLINK_TIMEOUT_BS_AMR) will be used in the following conditions:
AMR calls placed by MS not supporting Repeated ACCH AMR calls placed by any MS if at least one of the two features is not allowed (RDFACCH or RSACCH).
R6 R6 MS MS will will be be using using RxACCH RxACCH for for AMR AMR calls calls Pre-Rel6 Pre-Rel6 MS MS will will be be using using DRLT DRLT for for AMR AMR calls calls Activating Activating both both features features will will improve improve the the performance performance of of all all AMR AMR calls calls
3.2
45 | Repeated ACCH
Feature Assessment New Counter and Indicators
Feature Assessment Telecom Counters New Counters

Counter refname MC990 LongName Definition Measured object Domain TRX Type
NB_MS_REPEATED_ACCH_Capa Number of calls for which the mobile stations ble supporting the repeated ACCH capability NB_Calls_RFACCH_Activated
Quality of 110 service Quality of 110 service Quality of 110 service
MC991
Number of calls for which repeated DL FACCH is TRX activated by the BSC Number of calls for which repeated SACCH (DL or UL) is activated by the BSC TRX
MC992
NB_Calls_RSACCH_Activated
MC993
Number of AMR TCH (NB or WB AMR) for which Repeated SACCH is not activated, dropped in NB_AMR_TCH_DROP_RLF_TRX TCH established phase due to radio link failure TRX (radio link timeout or Lapdm timer expiry), per TRX. Number of AMR TCH (NB or WB AMR) for which Repeated SACCH is activated, dropped in TCH NB_AMR_TCH_DROP_RLF_TRX_ established phase due to radio link failure TRX RSACCH (radio link timeout or Lapdm timer expiry), per TRX. This counter takes into account TCH in traffic.
Quality of 110 service
MC994
46 | Repeated ACCH
Feature Assessment Telecom Counters New Counters

Counter refname Definition Number of TCH using AMR codecs (NB or WB) but with Repeated FACCH not activated, NB_AMR_TCH_DROP_OUT_HO_ dropped during the execution of any TCH TRX TRX outgoing handover, per TRX. This counter takes into account handovers from TCH in traffic. Number of TCH using AMR codecs (NB or WB) and with Repeated FACCH activated, dropped NB_AMR_TCH_DROP_OUT_HO_ during the execution of any TCH outgoing TRX TRX_RFACCH handover, per TRX. This counter takes into account handovers from TCH in traffic or in signaling mode. LongName Measured object Domain Type
MC995
MC996
47 | Repeated ACCH
Feature Assessment Telecom Counters New Counters (type 10 & 15)

Counter refname Definition Domain Type Indicates the number of SAPI 0 frames that were not repeated. (SDCCH NB_FRAMES_NOT_REPEATED This counter corresponds to the CNT_I_TX field QoS 101 observations) of the 48.058 PHYSICAL CONTEXT CONFIRM message. Indicates the number of SAPI 0 frames that were repeated at least once. (SDCCH NB_FRAMES_REPEATED This counter corresponds to the CNT_I_RETX QoS 101 observations) field of the 48.058 PHYSICAL CONTEXT CONFIRM message. Indicates the number of SAPI 0 frames that were not repeated. (TCH NB_FRAMES_NOT_REPEATED This counter corresponds to the CNT_I_TX field QoS 151 observations) of the 48.058 PHYSICAL CONTEXT CONFIRM message. Indicates the number of SAPI 0 frames that were repeated at least once. (TCH This counter corresponds to the CNT_I_RETX observations) field of the 48.058 PHYSICAL CONTEXT CONFIRM message. LongName Measured object
S09
S16
T08
T15
NB_FRAMES_REPEATED
QoS
151
1Type
10 is SDCCH observation; type 15 is TCH observation

48 | Repeated ACCH
Feature Assessment Telecom Counters

Number of calls for which the mobile stations supporting the repeated ACCH capability Number of calls for which repeated DL FACCH is allowed by the BSC Number of calls for which repeated SACCH (DL or UL) is allowed by the BSC
TC
MSC
MC990 & MC991 & MC992 CHANNEL ACTIVATION or MODE MODIFY messages BTS MS Cell Abis
AterMUX-CS
BSC CONNECTION FAILURE MC995 & MC996 INDICATION or ERROR INDICATION messages MC993 & MC994
Number of AMR TCH (NB or WB AMR) for which Repeated SACCH is activated, dropped in TCH established phase due to radio link failure (radio link timeout or Lapdm timer expiry), per TRX. This counter takes into account TCH in traffic.
Number of TCH using AMR codecs (NB or WB) and with Repeated FACCH activated, dropped during the execution of any TCH outgoing handover, per TRX. This counter takes into account handovers from TCH in traffic or in signaling mode.
Number of AMR TCH (NB or WB AMR) for which Repeated SACCH is not activated, dropped in TCH established phase due to radio link failure (radio link timeout or Lapdm timer expiry), per TRX.
Number of TCH using AMR codecs (NB or WB) but with Repeated FACCH not activated, dropped during the execution of any TCH outgoing handover, per TRX. This counter takes into account handovers from TCH in traffic.
49 | Repeated ACCH
Feature Assessment Telecom Indicators Specific new basic indicators

NPO indicator refname Formula NPO B11 Description Counts the number of calls of mobile stations supporting the repeated ACCH capability. It takes into account both Normal assignment MC990 and incoming HO and DR. Counts the number of calls for which repeated DL FACCH is activated by the BSC. In this context activation means that repetition is allowed by the BSC yet for frames to be repeated it is only dependent on BTS. It takes into account both Normal assignment and MC991 incoming HO and DR. Counts the number of calls for which repeated SACCH (DL or UL) is activated by the BSC. In this context activation means that repetition is allowed by the BSC yet for frames to be repeated it is only dependent on BTS. It takes into account both Normal assignment and MC992 incoming HO and DR.
LongName NPO
GSDRACN
MS_REPEATED_ACCH_Capable
GSDRFACN
Call_RFACCH_BSC Activated
GSDRSACN
Call_RSACCH_BSC_Activated
50 | Repeated ACCH

NPO indicator refname Formula NPO B11 Description Counts the number of AMR TCH (NB or WB AMR) for which Repeated SACCH is not activated by the BSC, dropped in TCH established phase due to radio link failure (radio link timeout or Lapdm timer expiry), AMR_TCH_DROP_No_RSACCH_Activated MC993 per TRX. Counts the number of AMR TCH (NB or WB AMR) for which Repeated SACCH is activated by the BSC, dropped in TCH established phase due to radio link failure (radio link timeout or Lapdm timer expiry), per TRX. This counter AMR_TCH_DROP_RSACCH_Activated MC994 takes into account TCH in traffic. Counts the number of TCH using AMR codecs (NB or WB) but with Repeated FACCH not activated, dropped during the execution of any TCH outgoing handover, per TRX. This AMR_TCH_DROP_OUT_HO_No_RFACCH counter takes into account handovers from _Activated MC995 TCH in traffic. LongName NPO
GTCNRSACN
GTCRSACN
GTCNRFACN
51 | Repeated ACCH

NPO indicator refname Formula NPO B11 Description Counts the number of TCH using AMR codecs (NB or WB) and with Repeated FACCH activated, dropped during the execution of any TCH outgoing handover, per TRX. This AMR_TCH_DROP_OUT_HO_RFACCH_Act counter takes into account handovers from ivated MC996 TCH in traffic or in signaling mode. LongName NPO
GTCRFACN
52 | Repeated ACCH
Feature Assessment Telecom Indicators Specific new computed indicators

NPO indicator refname LongName NPO Description Represents the ratio of AMR calls with R6 Mobile stations, that are capable and allowed by the BSC of supporting both RSACCH and RDFACCH with respect to the whole population RxACCH_R6_MS_capable_Calls_Rati of considered calls that are at least capable o MC992 / MC991 and allowed by the BSC to support RDFACCH Formula NPO B11
GSDRACR6MSCO
Represents the ratio of AMR calls with Pre-R6 Mobile stations, that are capable and allowed by the BSC of supporting RDFACCH with respect to the whole population of considered calls RDFACCH_Active_PreR6_MS_capabl (MC991-MC992) that are at least capable and allowed by the GSDRFAPR6MSCO e_Calls_Ratio / MC991 BSC to support RDFACCH MC990 /(MC703 Penetration rate for the mobile stations, + MC15a + already in call state, supporting the repeated GSDRACCPR RxACCH_MS_Penetration_Rate MC15b) ACCH capability Penetration rate for the mobile stations, MC991/ RDFACCH_BSC_Activated_MS_Penet (MC703+MC15a+ already in call state, with RDFACCH BSC activated GSDRFACPR ration_Rate MC15b) MC992/ Penetration rate for the mobile stations, RSACCH_BSC_Activated_MS_Penetra (MC703+MC15a+ already in call state, with RSACCH BSC GSDRSACPR tion_Rate MC15b) activated.
53 | Repeated ACCH

NPO indicator refname Formula NPO B11
LongName NPO
Description
(MC995) / ( MC621 Ratio of AMR with RDFACCH not allowed HO AMR_NoRDFACCH_Call_drop_HO_ratio GSDNRFACCDHO + MC995 + MC996) drops compared to total HO drops (MC996) / ( MC621 Ratio of AMR with RDFACCH allowed HO + MC995 + MC996) drops compared to total HO drops MC736 / (MC736 + Ratio of Non AMR radio drops compared to MC993 + MC994) total radio drops MC621 / (MC621 + Ratio of Non AMR HO drops compared to MC995 + MC996) total HO drops (MC994) / (MC736 Ratio of AMR with RSACCH allowed calls + MC993 + MC994) radio drops compared to total radio drops
GSDRFACCDHO AMR_RDFACCH_Call_drop_HO_ratio
GQSNACDRO
NonAMR_Call_drop_radio_ratio
GQSNACDHO
NonAMR_Call_drop_HO_ratio
GSDRSACCDRO AMR_RSACCH_Call_drop_radio_ratio
(MC993) / (MC736 Ratio of AMR without RSACCH allowed calls GSDNRSACCDRO AMR_NoRSACCH_Call_drop_radio_ratio + MC993 + MC994) radio drops compared to total radio drops
54 | Repeated ACCH

NPO indicator refname Formula NPO B11
LongName NPO
GQSANARFR
AMR_NA_Call_radio_fail_rate
(MC993+MC994) / (MC704a + MC704b + MC931
GQSANAHOFR
AMR_NA_Call_HO_fail_rate
(MC995+MC996) / (MC704a + MC704b + MC931)
GQSNANARFR
NonAMR_NA_Call_radio_fail_rate
MC736 / (MC702a + MC702b + MC702c)
GQSNANAHOFR NonAMR_NA_Call_HO_fail_rate
MC621 / (MC702a + MC702b + MC702c)
Description Rate of AMR calls failed due to Radio with respect to AMR Normal assignment requests (including requests that might fail during the period of TCH assignment to TCH phase). Rate of AMR calls failed due to HO with respect to AMR Normal assignment requests (including requests that might fail during the period of TCH assignment to TCH phase). Rate of non AMR calls failed due to Radio with respect to non AMR Normal assignment requests (including requests that might fail during the period of TCH assignment to TCH phase). Rate of non AMR calls failed due to HO with respect to non AMR Normal assignment requests (including requests that might fail during the period of TCH assignment to TCH phase).
55 | Repeated ACCH

NPO indicator refname LongName NPO Formula NPO B11 Description Rate of AMR with RDFACCH allowed calls failed due to HO with respect to BSC activated RDFACCH AMR Normal assignment, incoming HO and DR requests (including requests that might fail during the period of TCH assignment to TCH phase). Rate of AMR with RSACCH allowed calls failed due to Radio with respect to allowed RSACCH AMR Normal assignment, incoming HO and DR requests (including requests that might fail during the period of TCH assignment to TCH phase).
GSDRACCAFDR AMR_RDFACCH_Call_HO_fail_rate
MC996 / MC991
GSDRACCASDR AMR_RSACCH_Call_radio_fail_rate
MC994 / MC992
56 | Repeated ACCH
Feature Assessment Telecom Indicators Specific computed indicators modified

NPO indicator refname GTMMSAMR
LongName NPO
Modification The formula only takes into account SV3. Its update to
RTCH_assign_AMR_penetration_rate considered also SV5.
(mc701d+mc932) / mc140a
Old counters MC736 or MC621 were modified due to introduction of new drop counters, MC993, MC994, MC995 and MC996. This caused formula modifications on several old indicators like Call_drop_rate or RTCH_drop_HO_rate. For details on extension of indicators affected see slides of PM counters
57 | Repeated ACCH
Feature Assessment Telecom Indicators
Report dedicated to the feature Repeated ACCH.

NPO report name Views in the report
Alc_ACCH_MS Alc_ACCH_allowed Alc_AMR_and_SACCH
Description of the views

Mobiles with RACCH capable and penetration rate. Calls with RFACCH or RSACCH allowed. AMR HO drop with and without FACCH. AMR radio drop with and without SACCH. Split of call drop radio for AMR and NonAMR calls Split of call drop HO for AMR and NonAMR calls
Alc_Mono_Repeated_ACCH
Alc_AMR_and_FACCH Alc_drop_radio_AMR_and_NonAMR Alc_drop_HO_AMR_and_NonAMR
Please refer to feature test plan for other NPO reports that can be interesting to monitor the feature behavior
58 | Repeated ACCH
3.3
59 | Repeated ACCH
Feature Assessment Monitoring Method
Feature Assessment Monitoring Method Planning Overview

Test Category Statistical Test Type Non Regression Optimization Unitary SACCH FACCH Trial Period Two Weeks Four Weeks Five Days Five Days
One RNE resource is required for generic Statistical and Unitary Tests
60 | Repeated ACCH
Feature Assessment Monitoring Method If AMR is not activated or in mono codec configuration, AMR must be adjusted to multi codec configuration as per the following TMO AMR parameters adjustment example:
Parameter Name
AMR_FR_THR3 AMR_HR_THR1 AMR_HR_THR2 AMR_HR_THR3 AMR_FR_SUBSET AMR_START_MODE_FR
Initial setting
16 10 16 22 {12.2 Kbps} 1
Date of modification
W945.1 W945.1 W945.1 W945.1 W945.1 W945.1
Value after modification

22 20 26 26 {12.2 Kbps, 10.2 Kbps, 7.4 Kbps, 4.75 Kbps} 0
AMR subset is changed to multi codec configuration to reproduce AMR signaling imbalance impact due to difference of the redundancy level AMR codec adaption thresholds are coming from best practice experience The pilot area is to be frozen during the tests. No network extension to be done neither any logical parameter change different than those requested by the tests
Statistical Tests
62 | Repeated ACCH
Feature Assessment Non Regression Tests
Test Description
The following QoS KPIs will be monitored for the pilot area during reference and activation period:
Call Drop: Call_drop_rate, Call_drop_radio_rate, Call_drop_HO_rate and AMR/Non AMR call failure rates Call Setup: Call_setup_success_rate Traffic: RTCH_full_duration_avg, RTCH_GSM_Erlang_total and RTCH_DCS_Erlang_total HO: Success rate, Reversion Old Channel Rate, Rate of HO failure, Rate of HO failure due to Radio and Handover Efficiency RMS: Noisy calls causes split and call quality statistics
63 | Repeated ACCH
Feature Assessment Optimization Tests
Test Description (1/5)

Pilot area is divided into three cell zones as follows:
Cell zone A is preferably with bad HO KPIs Call drops due to HO and HO success rates Cell Zone B is preferably with bad CDR KPIs Call drops due to Radio Cell Zone C is preferably with non optimal radio conditions at cell boarders Coverage gaps in RMS reports
TMO Essen Pilot Example
For more information about the cell zone division criterion please click here

Change the parameters REP_DL_FACCH_THRES_AMR_YY1, RADIOLINK_REP_DL_SACCH, and L_RXQUAL_XX_P_AMR_RXACCH 2 per each cell zone as per following planning
1Where
YY is FR or HR and XX is UL or DL
2Only
applicable if we can change the parameters L_RXQUAL_XL_P due to recommended rules: L_RXQUAL_UL_P_AMR_RXACCH > U_RXQUAL_UL_P (mandatory rule) L_RXQUAL_UL_P_AMR_RXACCH >= L_RXQUAL_UL_P (recommended rule) L_RXQUAL_xL_P > U_RXQUAL_xL_P (mandatory rule)
65 | Repeated ACCH

Configuration REP_DL_FACCH_THRE S_AMR_YY Cell Zone A 3 5 All Pilot 7 All BSC 3 Reference RACCH Default RACCH Tuning1 RACCH Tuning2 RACCH Final *
RADIOLINK_REP_DL_S Feature is deactivated, AMR is in multi-codec configuration ACCH Cell Zone B L_RXQUAL_XX_P_AMR _RXACCH Cell Zone C
10 5 All Pilot 3 1.1 All Pilot 4 18
10 All BSC 1.9 or 3.4 ** All BSC
* More information about choosing optimized parameter setting available in optimization test section ** If L_RXQUAL_XX_P=2.9 If L_RXQUAL_XX_P=1.1 L_RXQUAL_XX_P_AMR_RXACCH = 3.4 L_RXQUAL_XX_P_AMR_RXACCH = 1.9
66 | Repeated ACCH

On the 5th week, after deducing the optimized range for each parameter, use the optimized range of all parameters on the whole pilot area to monitor the effects of FACCH, SACCH and PC parameters changes combined. Pilot Area will be divided into two cell zones on week 49: Cell Zone D: using optimized RxACCH parameters with legacy radio link counter Cell Zone E: using optimized RxACCH parameters with AMR differentiated radio link counter
Cell Zone RADIOLINK_TIMEOUT_BS_A RADIOLINK_TIMEOUT_AMR Parameter MR Cell Zone D 24 24
TMO Essen Pilot Example
Cell Zone E
32
32
67 | Repeated ACCH

After each stage, the following indicators are observed to deduce optimized parameters values: Call Drop: [Call_drop_rate, Call_drop_radio_rate, and Call_drop_HO_rate] and AMR/Non AMR call failure rates Call Setup: Call_setup_success_rate Traffic: RTCH_full_duration_avg, RTCH_GSM_Erlang_total and RTCH_DCS_Erlang_total HO: Success rate, Reversion Old Channel Rate, Rate of HO failure, Rate of HO failure due to Radio, Handover Efficiency, AMR_TCH_OUT_HO_No_RFACCH_Activated and AMR_TCH_OUT_HO_RFACCH_Activated RMS: Noisy calls causes split and call quality statistics
The penetration of RxACCH capable Mobiles is correlated also with the observed improvements
Unitary Tests
69 | Repeated ACCH
Feature Assessment SACCH Unitary Tests
Test Description
Lock the MS on the frequency of the cell under test Drive test to record voice quality, RxQual and RxLev at cell border locked each time on codec AMR-FR, AMR-HR and WB-AMR if available Perform this test using Release 6 Mobile Station and repeat it to legacy Mobile station Compare the results before and after feature activation
Drive test route Cell coverage with RxACCH Cell coverage without RxACCH
BTS
A: Start measurement (all cases)
C: Radio link failure with RxACCH
B: Radio link failure without RxACCH

Feature Assessment FACCH Unitary Tests
Test Description
Drive test to record voice quality, RxQual, RxLev and HO procedure while crossing the boarders of the two cells under tests locked each time on codec AMR-FR, AMR-HR and WB-AMR if available to perform at least 15 HOs Perform this test before feature activation with optimized AMR RLT thresholds and then after RxACCH activation Perform this test using Release 6 Mobile Station and repeat it with legacy Mobile Station Compare the results before and after feature activation for both releases
Drive test route Cell coverage with RxACCH Cell coverage without RxACCH
71 | Repeated ACCH
3.4
72 | Repeated ACCH
Feature Assessment FOA Test Results
Statistical Tests Results
73 | Repeated ACCH
Statistical Test Results RxACCH Capable MS Penetration

Penetration Weekly
100.00% 80.00% 60.00% % 40.00% 20.00% 0.00% Mono Codec RxACCH_MS_Penetration_Rate RDFACCH_BSC_Activated_MS_Penetration_ Rate RSACCH_BSC_Activated_MS_Penetration_R ate 0.00% 0.00% 0.00% Multi Codec 9.98% 0.00% 0.00% RACCH Default 10.36% 85.71% 10.36% Time RACCH Tuning1 10.93% 85.98% 10.83%
B11 Indicators Only
RACCH Tuning2 10.97% 10.97% 10.97%
RACCH Final 10.38% 10.38% 10.38%
As the RxACCH capable MS penetration is around 10%, it is not expected to see a noticeable improvement as not all those 10% might be in bad radio conditions during calls
RDFACCH activation penetration rate dropped from ~85% to ~ 10% starting from the second tuning phase due to disabling the feature for legacy MS due to observing unexpected behavior with the feature
74 | Repeated ACCH
Statistical Test Results Radio Measurement Statistics

AMR FR DL Codec Distribution
100% 90% 80% 70% 60% 50% 40% 1.35% 1.30% 1.25%
Mono Codec 0.12% 0.29% 0.00% 99.54% 1.33% Multi Codec 1.12% 2.11% 1.71% 94.88% 1.46% RACCH Def ault 1.10% 1.21% 1.75% 95.94% 1.46% RACCH Tuning1 1.04% 1.14% 1.66% 96.15% 1.52% RACCH Tuning2 1.11% 1.22% 1.76% 95.91% 1.47% RACCH Final 1.06% 1.16% 1.65% 96.13% 1.44%
1.55% 1.50% 1.45% 1.40%
AMR 12.2 kbps Codec is dominating codec, more robust codec are not often used
30% 20% 10% 0%

DL 4.75 FR Frame Distribution DL 7.4 FR Frame Distribution DL 10.2 FR Frame Distribution
1.20%
Feature impact is expected to be minimal as calls are in good radio conditions and using AMR 12.2 kbps most of the time
DL 12.2 FR Frame Distribution RMS_Call_noisy_DL_rate
AMR FR UL Codec Distribution

120.00% 100.00% 80.00% 60.00% 40.00% 20.00% 00.00%
UL 4.75 FR Frame Distribution UL 7.4 FR Frame Distribution UL 10.2 FR Frame Distribution UL 12.2 FR Frame Distribution RMS_Call_noisy_UL_rate Mono Codec 0.00% 0.00% 0.00% 100.00% 2.46% Multi Codec 0.52% 1.39% 1.69% 96.39% 3.17% RACCH Def ault 0.49% 1.07% 1.53% 96.90% 3.17% RACCH Tuning1 0.49% 1.03% 1.47% 97.01% 3.27% RACCH Tuning2 0.50% 1.08% 1.61% 96.81% 3.38% RACCH Final 0.50% 1.08% 1.56% 96.86% 3.34%
4.00% 3.50% 3.00% 2.50% 2.00% 1.50% 1.00% 0.50% 0.00%
75 | Repeated ACCH
Statistical Test Results Non Regression Test

Non Regression Statistics
2.00% 1.50% % 1.00% 0.50% 0.00%
HO_Inc_BSC_fail_rate HO_Inc_BSC_unsuccess_rate HO_Out_BSC_drop_rate HO_Out_BSC_prep_fail_rate HO_Out_BSC_ROC_rate Call_drop_rate Call_drop_radio_rate
Mono Codec 1.31% 1.55% 0.13% 0.28% 1.18% 0.84% 0.65%
Multi Codec 1.30% 1.54% 0.13% 0.26% 1.17% 0.89% 0.69%
RACCH Default 1.22% 1.46% 0.11% 0.28% 1.10% 0.86% 0.69%
Observation Week
Up on activating AMR Multi-Codec, no impact was observed on HO and call drop KPIs Very slight fluctuations, with a small MS penetration supporting feature, which is using 12.2 Codec most of the time (good radio conditions) Feature brought No Regression on the Pilot
76 | Repeated ACCH
Optimization Test Results Cell Zone A Optimization of REP_DL_FACCH_THRES_AMR_XR

HO Call Drops
0.45% 0.40%
REP_DL_FACCH_THRES_AMR_FR=
B11 Indicators Only %
AMR HO Failure with RDFACCH support as well generic HO failures did not enhance significantly while moving the parameter from 3 to 5 or 7
0.35% 0.30% 0.25% 0.20% 0.15% 0.10% 0.05% 0.00% NonAMR_NA_Call_HO_f ail_rate AMR_NA_Call_HO_f ail_rate AMR_RDFACCH_Call_HO_f ail_rate Mono Codec 0 0 0 Multi Codec 0.34% 0.38% 0.00% RACCH Def ault 0.26% 0.22% 0.08% Obse rvation Wee k RACCH Tuning1 0.23% 0.22% 0.08% RACCH Tuning2 0.27% 0.26% 0.08%
Increasing the probability at which the RDFACCH is activated (using 5 or 7) didnt show significant impact.
HO Statistics
2.00% 1.80% 1.60% 1.40% 1.20% % 1.00% 0.80% 0.60% 0.40% 0.20% 0.00% HO_Inc_BSC_f ail_rate HO_Inc_BSC_unsuccess_rate HO_Out_BSC_drop_rate HO_Out_BSC_prep_f ail_rate HO_Out_BSC_ROC_rate Mono Codec 1.55% 1.67% 0.17% 0.16% 1.38% Multi Codec 1.60% 1.76% 0.18% 0.16% 1.40% RACCH Def ault 1.39% 1.54% 0.15% 0.16% 1.26% Tim e RA CCH Tuning1 1.40% 1.55% 0.14% 0.15% 1.24% RACCH Tuning2 1.55% 1.69% 0.18% 0.16% 1.39%
77 | Repeated ACCH
Optimization Test Results Cell Zone A Optimization of REP_DL_FACCH_THRES_AMR_XR Legacy Support

Disabled
Radio Call Drop Rates
3.00% 2.50% 2.00% % 1.50% 1.00% 0.50%
B11 Indicators Only
0.00% Call_drop_rate NonAMR_NA_Call_radio_fail_rate AMR_NA_Call_radio_fail_rate AMR_RSACCH_Call_radio_fail_rate
Mono Codec 0.90% 0.00% 0.00% 0
Multi Codec 0.92% 2.01% 0.60% 0.00%
RACCH Def ault 0.91% 2.27% 0.51% 0.17% Observation Week
RACCH Tuning1 1.29% 2.18% 1.04% 0.14%
RACCH Tuning2 1.02% 2.77% 0.52% 0.15%
Transmission It is recommended problemsto existence use the during REP_DL_FACCH_THRES_AMR_FR= tuning phase increased call drop 3 (or rates the second robust codec equivalent value in the AMR subset) as a good compromise for activating DL FACCH Observation of the feature indicators showed that some MSs legacy as current assumption- might not be Moreover well impacted as per during the current enabling assumptions DL FACCH REP_DL_FACCH_LEGACY_SUPPORT all the time. In graph, it can be seen must that call be disabled drop is less to avoid impacted during second tuning phase legacy due MSs to misbehavior legacy support with deactivation RDFACCH
78 | Repeated ACCH
Optimization Test Results Cell Zone B Optimization of RADIOLINK_REP_DL_SACCH

3.00% 2.50% 2.00% % 1.50% 1.00%
10
18
B11 Indicators Only
0.50% 0.00% NonAMR_NA_Call_radio_fail_rate AMR_NA_Call_radio_fail_rate AMR_RSACCH_Call_radio_fail_rate Call_drop_rate Mono Codec 0.00% 0.00% 0 0.86% Multi Codec 2.47% 0.81% 0.00% 0.95% RACCH Default 2.23% 0.62% 0.18% 0.94% Observation Week RACCH Tuning1 2.15% 0.69% 0.21% 1.08% RACCH Tuning2 2.48% 0.66% 0.22% 1.03%
It is recommended to use the values 10 for a good compromise for activating RSACCH and It is clear that increasing RADIOLINK_REP_DL_SACCH improves the Radio CDR, however the gain unnecessary measurement reports repetition and delay from increasing the parameter to 18 cannot be quantified or compared to RxACCH default activation period due the transmission problem and sites value failure during tuning phases For RLT ofto 24, the RADIOLINK_REP_DL_SACCH can be fine tuned up to 15 to adapt to the network and customer requirements. Above than 15 if RLT value is higher than 24 It is seen that the value 5 tuning 1 degrades AMR radio drops when compared to the value 18 tuning
79 | Repeated ACCH
Optimization Test Results Cell Zone C Optimization of L_RXQUAL_XX_P_AMR_RXACCH

HO Call Drops
L_RXQUAL_XX_P_AMR_RXACCH= 0.25%
0.20% 0.15% % 0.10% 0.05% 0.00%
1.1
Changing the L_RXQUAL_XX_P_AMR _RXACCH from 3 to 1.1 kept the same HO drops, Yet this is not totally true as upon using 1.1 transmission failures occurred.
%
Mono Codec 0 0 0
Multi Codec 0.18% 0.14% 0.00%
RACCH Default 0.23% 0.12% 0.05% Observation Week
RACCH Tuning1 0.16% 0.10% 0.04%
RACCH Tuning2 0.18% 0.16% 0.03%
NonAMR_NA_Call_HO_fail_rate AMR_NA_Call_HO_fail_rate AMR_RDFACCH_Call_HO_fail_rate
HO Statistics
L_RXQUAL_XX_P_AMR_RXACCH=
12.00% 10.00% 8.00% 6.00% 4.00% 2.00% 0.00% HO_Inc_BSC_fail_rate HO_Inc_BSC_unsuccess_rate HO_Out_BSC_drop_rate HO_Out_BSC_prep_fail_rate HO_Out_BSC_ROC_rate Mono Codec 0.92% 1.29% 0.11% 0.35% 0.82% Multi Codec 0.84% 0.99% 0.09% 0.21% 0.75%
1.1
RACCH Default 0.77% 0.99% 0.07% 0.24% 0.70% Observation Week
RACCH Tuning1 0.59% 11.20% 0.07% 9.14% 0.58%
RACCH Tuning2 0.87% 1.18% 0.11% 0.28% 0.77%
80 | Repeated ACCH
Optimization Test Results Cell Zone C Optimization of L_RXQUAL_XX_P_AMR_RXACCH

2.00% 1.50% 1.00% 0.50% %
L_RXQUAL_XX_P_AMR_RXACCH=
1.1
B11 Indicators Only
0.00% NonAMR_NA_Call_radio_fail_rate AMR_NA_Call_radio_fail_rate AMR_RSACCH_Call_radio_fail_rate Call_drop_rate
Mono Codec 0.00% 0.00% 0 0.68%
Multi Codec 1.75% 0.51% 0.00% 0.66%
RACCH Default 1.41% 0.34% 0.11% 0.56% Observation Week
RACCH Tuning1 1.07% 0.36% 0.11% 0.52%
RACCH Tuning2 1.20% 0.44% 0.17% 0.64%
According to trial the appropriate RxACCH PC parameter to be used is the same as legacy PC parameter. During changes L_RXQUAL_XX_P_AMR_RXACCH from 3 to 1.1 is observed enhances of the radio Apparently theresof some margin to increasing RxACCH PC parameter more than legacy parameter without drops, but no improves on the radio drops for AMR with RSACCH support observe impact. During changes of L_RXQUAL_XX_P_AMR_RXACCH from 3 to 4 degrades is observed that radio drops Combining ALU recommendation L_RXQUAL_xL_P_AMR_RXACCH >=L_RXQUAL_xL_P and TMO slightly increase, specifically thefollowing radio drops for AMR with RSACCH support recommendation, we will use the rules: The impact of PC parameters tuning cannot be uncorrelated with the transmission problem occurred at If L_RXQUAL_XX_P=2.9 L_RXQUAL_XX_P_AMR_RXACCH = 3.4 the same time If L_RXQUAL_XX_P=1.1 L_RXQUAL_XX_P_AMR_RXACCH = 1.9
81 | Repeated ACCH
Optimization Test Results Final optimized values Radio Call Drop Rates
Cell Zone D
2.50% 2.00%
RxACCH + LRLT --> Radio Call Drop Rates
B11 Indicators Only
AMR multi codec introduction brought no impact on LRLT+RxACCH cell zone. However for DRLT+RxACCH slight CDR degradation is noticed For LRLT cell zone a slight CDR gain is seen (enhancement of 6.5% with respect to multi codec reference) For DLRLT cell zone CDR came to initial mono codec value, recovering the slight degradation upon using multi codecs (CDR enhancement of 10.3% with respect to multi codec reference)
1.50% % 1.00% 0.50% 0.00% NonAMR_NA_Call_radio_fail_rate AMR_NA_Call_radio_fail_rate AMR_RSACCH_Call_radio_fail_rate Call_drop_rate
Mono Codec 0.00% 0.00% 0 0.92%
Multi Codec 1.99% 0.62% 0.00% 0.91%
RACCH Default 2.14% 0.49% 0.16% 0.87%
RACCH Final 1.78% 0.51% 0.20% 0.85%
Observation Week
Cell Zone E
2.50% 2.00% 1.50% % 1.00% 0.50% 0.00% NonAMR_NA_Call_radio_fail_rate AMR_NA_Call_radio_fail_rate AMR_RSACCH_Call_radio_fail_rate Call_drop_rate
DRLT + RxACCH --> Radio Call Drop Rates
B11 Indicators Only
Mono Codec 0.00% 0.00% 0 0.78%
Multi Codec 2.32% 0.72% 0.00% 0.87%
RACCH Default 2.11% 0.55% 0.16% 0.86%
RACCH Final 1.68% 0.48% 0.19% 0.78%
Observation Week
82 | Repeated ACCH
Optimization Test Results Final optimized values HO Call Drop Rates

Cell Zone D
0.40% 0.35% 0.30% 0.25% % 0.20% 0.15% 0.10%
B11 Indicators Only
LRLT+RxACCH --> HO Call Drop Rates
Is observed a slight improvement for the AMR HO fail rates with feature introduction on both areas RxACCH capable MS HO drops are stable RDFACCH capable MS HO drops slightly enhanced from 0.06% to 0.05% for LRLT cell zone and from 0.08% to 0.05% for DRLT
0.05% 0.00% NonAMR_NA_Call_HO_fail_rate AMR_NA_Call_HO_fail_rate AMR_RDFACCH_Call_HO_fail_rate Mono Codec 0 0 0 Multi Codec 0.34% 0.34% 0.00% Observation Week RACCH Default 0.27% 0.21% 0.08% RACCH Final 0.28% 0.23% 0.05%
Cell Zone E
0.30% 0.25% 0.20% % 0.15% 0.10% 0.05% 0.00% NonAMR_NA_Call_HO_fail_rate AMR_NA_Call_HO_fail_rate AMR_RDFACCH_Call_HO_fail_rate
DRLT+RxACCH --> HO Call Drop Rates
Mono Codec 0 0 0
Multi Codec 0.19% 0.26% 0.00%
RACCH Default 0.23% 0.16% 0.06%
RACCH Final 0.24% 0.20% 0.05%
Observation Week
83 | Repeated ACCH
Unitary Tests Results
84 | Repeated ACCH
INTRODUCTION
RSACCH Voice Quality Measurements
Objective: Investigate whats the Voice Quality on the edge of a cell border and if differences are observed when Repeated SACCH is activated. Investigate if RSACCH feature can extend the cells edge. Tests were performed in BSC Essen_1H MS-Fix calls configuration was used during all the trial Measurements has consisted on several passages of the same path, starting the call locked in a cell from a point under good radio conditions up to the edge of the cell where the call drops 2 different cells were tested in two different RLT tuned areas
Legacy RLT zone Cell Oberhausen-18_3a (CI 30268, BCCH 23) Differentiated RLT zone Cell Essen-Centrum-9_3 (CI 32571, BCCH 98)
VQ indicator (MOS) was assessed using an ALU internal tool, denominated Opera Radio traces (Nemo Outdoor) were done in parallel
85 | Repeated ACCH
MEASUREMENT CONFIGURATION
VQ and Unitary RSACCH Measurements Equipment:
MS<->Fix calls configuration
N85 (MS#1) and N95 (MS#2 Not for VQ propose, just for radio traces )
Opera client (SW version 2.4.2) and Opera Server Laptop with Nemo Outdoor and GPS
PLMN: TMO, BSC Essen_1H Type of tests:

Mobility test on 2 different cells, in different RLT configurations
Legacy RLT conf (RLT AMR = legacy RLT = 24) Differentiated RLT conf (RLT AMR = 32)
Each path is repeated 4 times
Sample
Speech sample has a duration of 6.7s with gap of 2.6s between samples Speech sample is in English language containing male and female voices
86 | Repeated ACCH
Test_SAMPLE.wav
MEASUREMENT CONFIGURATION
VQ and Unitary RSACCH Measurements Mobile Equipment configuration 1 MS (Nokia N85 MS#1) connected to Opera Client 1 MS (Nokia N95 MS#2) just for air traces 1 Opera Client equipment 1 Opera Server equipment 1 Nemo PC with GPS
Opera Server Opera Client BS BSC MSC TC
USB cable (AT commands, traces) GPS Audio cable Fix line MS#1 Nemo PC MS#2
87 | Repeated ACCH
GEOGRAPHICAL TESTS LOCALIZATION

VQ and Unitary RSACCH Measurements Cell Oberhausen-18_3a (CI 30268, BCCH 23) Legacy RLT area
The path shown in the picture was performed 4 times, for RSACCH feature enabled, disabled, UL and DL Total of 16 passages
Path Path representation representation for for the the cell cell measured measured in in Legacy Legacy RLT RLT area area Path Path distance distance 2.4km 2.4km
88 | Repeated ACCH
GEOGRAPHICAL TESTS LOCALIZATION

VQ and Unitary RSACCH Measurements Cell Essen-Centrum-9_3 (CI 32571, BCCH 98) Differentiated RLT area
The path shown in the picture was performed 4 times, for RSACCH feature enabled, disabled, UL and DL - Total of 16 passages
Path Path representation representation for for the the cell cell measured measured in in Differentiated Differentiated RLT RLT area area Path Path distance distance 1.3km 1.3km
89 | Repeated ACCH
RESULTS INTRODUCTION Voice Quality Measurements Results - VQ and Unitary
RSACCH Measurements
It was realized a set of tests in 2 different cells In each cell was done measurements in DL and UL, also with feature RSACCH enabled and disabled 2 different cells were tested in two different RLT tuned areas
Legacy RLT zone Cell Oberhausen-18_3a (CI 30268, BCCH 23) Differentiated RLT zone Cell Essen-Centrum-9_3 (CI 32571, BCCH 98)
For each combination, feature enabled/disabled, RLT legacy/differentiated and UL/DL it was repeated 4 passages The methodology consists in lock the mobile into the desired cell under good radio conditions and then moves into the edge of the cell until the call drops The objective is to observe if feature RSACCH can extended the radius of a cell maintaining acceptable Voice Quality During trial the tests for RFACCH were skipped, because it wasnt possible to find a good spot (HO fail or call drop) to test this feature in practical time Here is shown time Evolution Graphs (RxLev, RxQual and MOS) in mobility
90 | Repeated ACCH
-1 1 2 3 4 5 6 7
-2 7
-2 0 1 2 3 4 5 6
-1
Consistent results for the 4 passages:
MOS decrease with DL RxQual decrease in the edge of the tested cell
TIME EVOLUTION GRAPHS Voice Quality Measurements Results VQ and Unitary
91 | Repeated ACCH
Time Evolution Graph - VQ1, DL RSACCH OFF, Legacy RLT
0 -80 -60 -40 -20 -120 0 -100
10 :1 2: 31 .3 10 84 :1 2: 40 . 71 10 0 :1 2: 50 .0 10 32 :1 2: 59 .3 10 56 :1 3: 08 . 6 10 80 :1 3: 18 .0 10 04 :1 3: 27 .3 10 28 :1 3: 36 . 6 10 52 :1 3: 45 .9 10 72 :1 3: 55 .3 10 00 :1 4: 04 .6 10 20 :1 4: 13 .9 10 46 :1 4: 23 . 2 10 70 :1 4: 32 .5 10 94 :1 4: 41 .9 10 12 :1 4: 51 .2 10 32 :1 5: 00 .5 10 62 :1 5: 19 .1 04
9: 47 :5 8. 93 9: 48 2 :0 8. 25 9: 48 6 :1 7. 57 9: 48 8 :2 6. 90 9: 48 4 :3 6. 22 9: 48 4 :4 5. 55 9: 48 0 :5 4. 87 9: 49 4 :0 4. 19 9: 49 8 :1 3. 52 9: 49 0 :2 2. 81 9: 49 0 :3 2. 9: 16 49 8 :4 1. 49 9: 49 2 :5 0. 81 9: 50 6 :0 0. 13 9: 50 8 :0 9. 46 9: 50 4 :1 8. 78 9: 50 8 :2 8. 11 9: 50 0 :3 7. 43 9: 50 0 :4 6. 76 9: 50 0 :5 5. 98 9: 51 2 :0 5. 40 9: 51 4 :1 4. 72 6
-80
-60
-40
-20
-120 MOS RxQ avg RxLev avg

10 :2
0 1 2 3 4 5
-100
MOS RxQ avg RxLev avg
10 :2 7: 08 .7 20 46 68 92 16 :2 :2 10 10 10 10 10 10 10 10 10 10 10 :2 :2 :2 :2 :2 :2 :2 :2 :2 :2 :2 7: 55 10 8: 04 8: 13 8: 23 8: 32 8: 41 8: 51 9: 00 9: 09 9: 19 9: 28 9: 37 9: 47 .3 .6 .9 .3 .6 .9 .2 .6 .9 .2 .5 .8 .2 40 62 88 12 34 58 82 06 26 52 74 98 16 .0 .3 .6 .0 7: 18 7: 27 7: 36 7: 46 :2 :2 :2 :2 96 10 10 10 10 10
RSACCH Disabled (DL, Legacy RLT) VQ samples are recorded in Opera Client

6: 59 .3
-80 -60 -40 -20 -120 -100 MOS RxQ avg RxLev avg
10 :0 0: 30 .2 10 06 :0 0: 39 . 5 10 30 :0 0: 48 .8 10 52 :0 0: 58 .1 10 78 :0 1: 07 .5 10 00 :0 1: 16 .8 10 24 :0 1: 26 . 1 10 44 :0 1: 35 .4 10 70 :0 1: 44 . 79 10 2 :0 1: 54 .1 10 12 :0 2: 03 .4 10 42 :0 2: 12 . 7 10 66 :0 2: 22 .0 10 90 :0 2: 31 .4 10 12 :0 2: 40 . 7 10 38 :0 2: 50 .0 10 48 :0 2: 59 .3 10 78 :0 3: 08 .7 02
RSACCH Measurements
-80
-60
-40
-20
-120
-100
21 :4 8
0 1 2 3 4 5 6 7
0 1 2 3 4 5 6 7
21 :1
-2
-1
Similar results through this data when the feature is enabled
92 | Repeated ACCH
21
:5 2 :4 .05 9: 8 21 01. 3 :4 9: 82 21 10. 7 :4 9: 02 21 20. 0 :4 9: 30 21 29. 3 :4 9: 52 21 38. 6 :4 9: 78 21 47. 10 :4 9: 0 21 57. 3 :5 0: 24 21 06. 6 :5 0: 48 21 15. 9 :5 0: 72 21 25. 2 :5 0: 96 21 34. 61 :5 0: 8 21 43. 9 :5 0: 42 21 53. 2 :5 1: 66 21 02. 5 :5 1: 90 21 11. 9 :5 1: 14 21 21. 2 :5 1: 38 21 30. 5 :5 1: 60 21 39. 8 :5 1: 84 21 49. 20 :5 1: 6 21 58. 5 :5 2: 20 21 07. 8 :5 2: 24 21 17. 1 :5 2: 78 26 .3 42
8: 26 21 .6 :1 42 8: 35 21 .9 66 :1 8: 45 21 .2 :1 90 8: 54 21 .6 14 :1 9: 03 21 .9 :1 34 9: 13 21 .2 :1 60 9: 22 21 .5 :1 84 9: 31 21 .9 06 :1 9: 41 21 .2 :1 32 9: 50 21 .5 56 :1 9: 59 21 .8 :2 78 0: 09 21 .2 00 :2 0: 18 21 .5 :2 24 0: 27 21 .8 50 :2 0: 37 21 .1 :2 72 0: 46 21 .4 90 :2 0: 55 21 .8 :2 20 1: 05 21 .1 44 :2 1: 14 21 .4 :2 66 1: 23 21 .7 92 :2 1: 33 21 .1 :2 10 1: 42 .4 36
Time Evolution Graph - VQ3, DL RSACCH ON, Legacy RLT

0
-80
-60
-40
-20
-80
-60
-40
-20

22
-2 0 1 2 -1 3 4 5 6
-100
-120
-100
21
:3 7
RSACCH Enabled (DL, Legacy RLT) VQ samples are recorded in Opera Client

:0 1 22 :48 :0 .1 8 1 22 :57 2 :0 .50 2 22 :06 6 :0 .8 2 2 22 :16 8 :0 .1 2: 54 2 22 :0 5.4 7 2 22 :34 8 :0 .80 2 22 :44 2 :0 .1 2 2 22 :53 4 :0 .4 4 3 22 :02 8 :0 .7 7 3 22 :12 2 :0 .09 3 22 :21 6 :0 .4 1 3 22 :30 8 :0 .74 3 22 :40 4 :0 .06 3 22 :49 8 :0 .3 9 3 22 :58 2 :0 .71 4 22 :08 4 :0 .03 4 22 :17 6 :0 .3 6 4 22 :26 0 :0 .6 8 4 22 :36 4 :0 .00 4 22 :45 8 :0 .3 3 4 22 :54 2 :0 .6 5 5 22 :03 6 :0 .9 8 5 22 :13 0 :0 .30 5 22 :22 4 :0 .6 2 5 22 :31 8 :0 .9 4 5 22 :41 4 :0 .2 5: 60 50 .5 62
-80 -60 -120 -100 -40 -20 MOS RxQ avg RxLev avg
21
:3 7
:1 4. 06 4 :2 3. 21 39 :3 0 7: 32 21 .7 16 :3 7: 42 21 .0 40 :3 7: 51 21 .3 62 :3 8: 00 21 .6 82 :3 8: 10 21 .0 08 :3 8: 19 21 .3 34 :3 8: 28 21 .6 56 :3 8: 37 21 .9 78 :3 8: 47 21 .3 02 :3 8: 56 21 .6 28 :3 9: 05 21 .9 50 :3 9: 15 21 .2 76 :3 9: 24 21 .6 00 :3 9: 33 21 .9 22 :3 9: 43 21 .2 46 :3 9: 52 21 .5 70 :4 0: 01 21 .8 94 :4 0: 11 21 .1 44 :4 0: 20 .5 40

0
-80
-60
-40
-20
RSACCH Measurements
-120
-100
MOS is stable during UL tests, because UL is still good while DL is already dropping the call Imbalanced cell
93 | Repeated ACCH
Time Evolution Graph - VQ3, UL RSACCH OFF, Legacy RLT
12 :0 8: 11 .4 44 12 :0 8: 20 .7 70 12 :0 8: 30 .0 94 12 :0 8: 39 .4 18 12 :0 8: 48 .7 42 12 :0 8: 58 .0 64 12 :0 9: 07 .3 86 12 :0 9: 16 .7 12 12 :0 9: 26 .0 36 12 :0 9: 35 .3 58 12 :0 9: 54 .0 0 12 6 :1 0: 03 .3 28 12 :1 0: 12 .6 54 12 :1 0: 21 .9 76 12 :1 0: 31 .3 00 12 :1 0: 49 .9 46
11 :3 4: 11 57. 5 :3 5: 90 11 06. 9 :3 5: 14 11 16. 2 :3 5: 38 11 25. 56 :3 5: 0 11 34. 8 :3 5: 84 11 44. 2 :3 5: 08 11 53. 5 :3 6: 32 11 02. 8 :3 6: 54 11 12. 1 :3 6: 78 11 21. 50 :3 6: 2 11 30. 8 :3 6: 20 11 40. 1 :3 6: 50 11 49. 4 :3 7: 74 11 17. 4 :3 7: 44 11 26. 7 :3 7: 66 11 36. 08 :3 7: 8 11 45. 4 :3 8: 14 11 04. 0 :3 8: 60 11 13. 3 :3 8: 86 11 22. 7 :3 8: 08 11 32. 0 :3 8: 32 11 41. 3 :3 8: 56 11 50. 6 :3 9: 76 00 .0 04
-80
-60
-40
-20
-80
-60
-40
-20
-100
-120
-100
MOS RxQ avg
RxLev avg
12 :1
0 1 2 3
8: 47 .3 56
12 :1 8: 56 .6 80
12 :1 9: 06 .0 04
12 :1 9: 15 .3 28
12 :1 9: 24 .6 33 12 :1 12 9: :2 12 50 9: .9 52 0: :2 12
RSACCH Disabled (UL, Legacy RLT) VQ samples are recorded in Opera Server

12 :1 74 .6 01 0: :2 12 20 .9 11 0: :2 12 44 .2 20 0: :2 12 68 .5 39 0: :2 12 92 .2 48 0: :2 40 .5 57 1: 64 .8 25 88 .8 58
-80 -60 -40 -120 -100 MOS RxQ avg RxLev avg

0
11 :5 11 5:1 :5 2.2 11 5:2 60 :5 1.5 11 5:3 84 :5 0.9 11 5:4 06 :5 0.2 11 5:4 30 :5 9.5 11 5:5 54 :5 8.8 11 6:0 76 :5 8.2 11 6:1 02 :5 7.5 11 6:2 24 :5 6.8 11 6:3 48 :5 6.1 11 6:4 72 :5 5.4 11 6:5 88 :5 4.8 11 7:0 18 :5 4.1 11 7:1 42 :5 3.4 11 7:2 66 :5 2.7 11 7:3 90 :5 2.1 11 7:4 14 :5 1.4 11 7:5 36 :5 0.7 11 8:0 60 :5 0.0 11 8:0 84 :5 9.4 11 8:1 08 :5 8.7 11 8:2 30 :5 8.0 11 8:3 54 :5 7.3 11 8:4 78 :5 6.7 11 8:5 02 :5 6.0 11 9:0 26 :5 5.3 11 9:1 50 :5 4.6 11 9:2 74 :5 3.9 11 9:3 92 :5 3.3 11 9:4 20 :5 2.6 9: 4 51 4 .9 68
-20
-80
-60
-40
-20
RSACCH Measurements
-120
-100
0
0 1 2 3 4 5 6 7
The UL tests dont bring additional information about feature behaviour because UL remains good all the time during each passage
94 | Repeated ACCH
Time Evolution Graph - VQ3, UL RSACCH ON, Legacy RLT
22 :0 9: 21 .2 92 22 :0 9: 30 .6 16 22 :0 9: 49 .2 60 22 :0 9: 58 .5 86 22 :1 0: 07 .9 10 22 :1 0: 17 .2 34 22 :1 0: 26 .5 56 22 :1 0: 35 .8 76 22 :1 0: 45 .2 04 22 :1 0: 54 .5 28 22 :1 1: 03 .8 50 22 :1 1: 22 .4 98 22 :1 1: 31 .8 22 22 :1 1: 41 .1 42 22 :1 1: 50 .4 70 22 :1 1: 59 .7 86
21 :4 7: 53 .4 21 56 :4 8: 02 .7 21 80 :4 8: 12 .1 21 04 :4 8: 21 .4 21 92 :4 8: 40 .1 21 38 :4 8: 49 .4 21 62 :4 8: 58 .7 21 84 :4 9: 08 .1 21 08 :4 9: 17 .4 21 30 :4 9: 36 .0 21 80 :4 9: 45 .4 21 02 :4 9: 54 .7 21 26 :5 0: 04 .0 21 50 :5 0: 22 .6 21 98 :5 0: 32 .0 21 18 :5 0: 41 .3 21 44 :5 0: 50 .6 66
-80
-60
-40
-20
-80
-60
-40
-20
-120
-100
-100
22 :2 0:
0 1 2 3
00 .4 54 78 04 50 76 98 .7 .1 .7 .0 .3 09 19 37 47 56
22 :2 0: 0: 0: 0: 0: 1: 22 22 22 22 22 22 22 22 22 22 :2 :2 :2 :2 :2 :2 :2 :2 :2 :2 1: 1: 1: 1: 1: 2: 2: 2: 2: 2: :2 :2 :2 :2 :2 22 22 22 22 22
RSACCH Enabled (UL, Legacy RLT) VQ samples are recorded in Opera Server

05 15 24 33 43 52 01 10 20 29 38 .7 .0 .3 .6 .0 .3 22 46 68 92 14 40 .6 .9 .3 .6 .7 64 86 10 34 94
-80 -60 -40 -120 -100 MOS RxQ avg RxLev avg

0
21 :5 8: 47 .7 78 21 :5 8: 57 .1 00 21 :5 9: 06 .4 24 21 :5 9: 15 .7 48 21 :5 9: 25 .0 72 21 :5 9: 34 .3 9 21 6 :5 9: 43 .7 18 21 :5 9: 53 .0 42 22 :0 0: 02 .3 66 22 :0 0: 11 .6 90 22 :0 0: 21 .0 12 22 :0 0: 39 .6 60 22 :0 0: 48 .9 82 22 :0 0: 58 .3 06 22 :0 1: 07 .6 28 22 :0 1: 16 .9 54
RSACCH Measurements
-20
-80
-60
-40
-20
-120
-100
RSACCH Measurements
RSACCH Disabled (DL, Differentiated RLT) VQ samples are recorded in Opera Client
Time Evolution Graph - VQ1, DL RSACCH OFF, Differentiated RLT
7
-76
-80 -81
-78 6 -80 5
6 -82 -83 -84

4
-82
-84
4 -85 -86 -87

2 -90
-86 3 -88
-88
-92
Consistent results for 3 passages among 4:

1
-89 -90
1 -94
-96 10:57:24.844
MOS decrease with DL RxQual decrease in the edge of the tested cell
10:43:50.364 10:43:59.624
7 6 5 4

10:44:18.284
-91
Time 10:57:34.168
Evolution Graph - VQ4, 10:57:52.806 DL RSACCH OFF, Differentiated RLT 10:57:43.490 10:58:02.126 10:58:11.406
-79.5
-80
-80
-82
5 -80.5
-81
-84
4 -81.5
3 -86 2
3 -82 2 -82.5
-88
1 -83
0 11:07:48.974 -1 11:07:58.296 11:08:07.608 -90
0 11:21:32.856 -1 11:21:42.184 11:21:51.502
-83.5
-84
-2
-92
-2
-84.5
95 | Repeated ACCH
RSACCH Measurements
RSACCH Enabled (DL, Differentiated RLT) VQ samples are recorded in Opera Client
Time Evolution Graph - VQ1, DL RSACCH ON, Differentiated RLT
7 0

7 -72
-74
6
6
-20
-76
5 -40 4 -60 3 -80 MOS RxQ avg RxLev avg
5 -78 4
-80
-82
-84 2 -86
Consistent results among different passages, without additional data when feature is active
1 0
7
-100
1 -88

11:35:07.112 11:35:16.436 11:35:25.758 11:35:35.072 11:35:44.354
-120
-76
0 11:51:37.834
7
11:34:48.464
11:34:57.788
11:51:47.160

11:51:56.484 11:52:05.808 11:52:15.126 11:52:24.454
-90 11:52:33.774
-83
-78
-84 6
-80 5 -82 4 -84 3 -86 MOS RxQ avg RxLev avg
-85 5 -86 4
-87
-88
-89
2 -88
2 -90
-90
1 -91
0 12:09:37.636 12:09:46.964 12:09:56.286 12:10:05.588
-92
0 12:25:13.062 12:25:22.408 12:25:31.732 12:25:41.052
-92
96 | Repeated ACCH
RSACCH Measurements
RSACCH Disabled (UL, Differentiated RLT) VQ samples are recorded in Opera Server
Time Evolution Graph - VQ1, UL RSACCH OFF, Differentiated RLT
7 0

7 1.2
-20
5 -40 4 -60 3 -80 2
Problem with data

4 3
0.8
0.6
0.4
Once again, during UL tests theres no MOS variation because UL remains good during all passages.
1 0 7 6 5
-100
-120
0.2
15 :4 9: 26 .7 38 15 :4 9: 36 .0 60 15 :4 9: 45 .3 84 15 :4 9: 54 .7 08 15 :5 0: 13 .3 54 15 :5 0: 22 .6 78 15 :5 0: 32 .0 02 15 :5 0: 41 .3 26 15 :5 0: 50 .6 50 15 :5 0: 59 .9 72 15 :5 1: 09 .2 96 15 :5 1: 18 .5 96

0
0
7 -75
-20
-80
-40 4 -60 3 -80 2

2 4
-85
-90 3 -95
-100
-100
-120
-105
16 :1 4 16 :29 :1 .37 4 6 16 :38 :1 .70 4 0 16 :48 :1 .02 4 4 16 :57 :1 .34 5 8 16 :06 :1 .67 5 2 16 :15 :1 .99 5: 4 16 25 . :1 31 5 8 16 :34 :1 .64 5 2 16 :43 :1 .96 5 6 16 :53 . 29 :1 6 0 16 :02 :1 .61 6 2 16 :11 :1 .93 6 6 16 :21 :1 .26 6 0 16 :30 :1 .58 6 4 16 :39 . :1 90 6 8 16 :58 :1 .55 7 4 16 :07 :1 .87 7 6 16 :17 :1 .20 7 2 16 :26 :1 .52 7 6 16 :35 :1 .84 7 8 16 :45 :1 .17 7 0 16 :54 :1 .49 8 6 16 :03 . :1 81 8 8 16 :13 :1 .14 8 4 16 :31 :1 .78 8: 41 8 .1 14
97 | Repeated ACCH
16 :2 3: 12 .0 16 98 :2 3: 21 . 42 16 0 :2 3: 30 .7 16 4 :2 4 3: 40 .0 16 68 :2 3: 58 .7 16 14 :2 4: 17 .3 16 62 :2 4: 26 .6 16 82 :2 4: 36 .0 16 10 :2 4: 45 .3 16 32 :2 4: 54 .6 16 56 :2 5: 03 .9 16 80 :2 5: 13 .3 16 0 4 :2 5: 22 .6 16 24 :2 5: 31 .9 16 52 :2 5: 50 .5 16 98 :2 5: 59 .9 16 22 :2 6: 18 .5 16 6 8 :2 6: 27 .8 16 84 :2 6: 46 .5 40
16
16 :1 8
0 1 2 3 4 5 6 7
0 1 2 3 4 5 6 7
16 16
Same comment as last slide.
98 | Repeated ACCH
Time Evolution Graph - VQ3, UL RSACCH ON, Differentiated RLT
:4 1 16 :56 :4 .98 2 6 16 :15 :4 .63 2 8 16 :43 . :4 60 3 8 16 :02 :4 .25 3 6 16 :20 :4 .90 3 2 16 :39 :4 .55 3 0 16 :58 :4 .19 4: 16 26 8 :4 .16 4 8 16 :54 :4 .14 5 0 16 :22 :4 .11 5 0 16 :40 :4 .75 6 6 16 :08 :4 .72 6 8 16 :27 :4 .37 6 6 16 :46 . :4 02 7 16 :04 4 :4 .67 7 0 16 :23 :4 .31 7 8 16 :41 . :4 96 8 4 16 :00 :4 .61 8: 2 2 16 8 :4 .58 8 2 16 :47 :4 .23 9 0 16 :05 :4 .87 9 16 :24 6 :4 .52 9 4 16 :52 :5 .49 0 6 16 :11 :5 .14 0 0 16 :29 :5 .79 0: 57 0 .7 60
:0 5 :1 .43 8: 14 6 :1 .75 8 8 16 :33 :1 .40 8 6 16 :42 :1 .73 8: 0 5 16 2 :1 .05 9 4 16 :01 :1 .37 9: 8 1 16 0 :1 .70 9 2 16 :20 :1 .02 9 4 16 :29 :1 .34 9 8 16 :38 :1 .67 9: 2 4 16 7 :1 .99 9 6 16 :57 :2 .31 0: 8 0 16 6 :2 .64 0 2 16 :25 :2 .29 0: 0 3 16 4 :2 .61 0 4 16 :43 :2 .93 0 6 16 :53 :2 .26 1 2 16 :11 :2 .90 1: 8 2 16 1 :2 .23 1 2 16 :30 :2 .55 1: 4 3 16 9 :2 .87 1 8 16 :49 :2 .20 1: 2 5 16 8 :2 .52 2 6 16 :07 :2 .85 2: 35 0 .8 20
0 -80 -60 -40 -20 -120 -100
-80
-60
-40
-20
-100
MOS
RxQ avg RxLev avg
17
16 :2
RSACCH Enabled (UL, Differentiated RLT) VQ samples are recorded in Opera Server

:0 2 17 :18 :0 .6 1 2 17 :27 0 :0 .93 2 17 :37 4 :0 .2 5 2 17 :46 8 :0 .58 2: 17 55 2 :0 .9 0 3 17 :05 0 :0 .21 3 17 :14 2 :0 .5 5 3 17 :23 2 :0 .8 7 3 17 :33 6 :0 .2 0 3 17 :51 0 :0 .8 4 4 17 :01 6 :0 .1 7 4 17 :19 0 :0 .8 1 4 17 :29 8 :0 .1 4 4 17 :38 0 :0 .4 6 4 17 :47 4 :0 .7 8 4 17 :57 8 :0 .1 1 5 17 :06 2 :0 .4 3 5 17 :15 6 :0 .7 5 5 17 :25 8 :0 .0 8 5 17 :43 2 :0 .7 3 5 17 :53 0 :0 .0 5 6 17 :02 2 :0 .3 7 6 17 :11 6 :0 .7 0 6 17 :21 0 :0 .0 6: 24 3 17 :0 0.3 4 6 17 :39 6 :0 .6 6: 70 48 .9 94
9: 24 .0 16 48 :2 9: 33 .3 16 7 :2 2 9: 42 .6 16 96 :2 9: 52 .0 16 20 :3 0: 01 .3 16 44 :3 0: 10 .6 16 66 :3 0: 19 .9 16 90 :3 0: 29 .3 16 12 :3 0: 38 .6 16 36 :3 0: 47 .9 16 62 :3 0: 57 .2 16 84 :3 1: 06 .6 16 08 :3 1: 15 .9 16 32 :3 1: 25 .2 16 5 :3 6 1: 34 .5 16 80 :3 1: 43 .9 16 02 :3 2: 02 .5 16 50 :3 2: 11 .8 16 72 :3 2: 21 .1 16 96 :3 2: 30 .5 20

0
-80
-60
-40
-20
RSACCH Measurements
-120
-100
-94
-92
-90
-88
-86
-84
-82
-80
-78
-76
-74

OBSERVATIONS
RSACCH Measurements
Measurements realized in UL are not useful to assess Voice Quality indicator

The reason are linked to imbalanced radio links While the DL (decoded in the MS) is already under bad conditions, the UL (decoded in BS) are still under good radio conditions Thats why MOS indicator is not affected in UL tests
The cell and path chosen for Differentiated RLT area, had a strange radio conditions, going suddenly into very bad radio conditions
This radio characteristics has harmed the evaluation over this cell, because this path becomes very short and instable
The Time Evolution Graph didn't permit to measure a difference between the cases where the feature is active and the case where it is not
VQ indicator is similar on the edge of the cell for feature enabled or disabled
99 | Repeated ACCH
MOS representation on Map Voice Quality Measurements Results VQ and Unitary

RSACCH Disabled Legacy RLT
RSACCH Measurements
MOS MOS representation representation during during path path 1 1 measured measured in in Legacy Legacy RLT RLT area, area, for for RSACCH Disabled RSACCH Disabled Path Path distance distance 2.4km 2.4km
100 | Repeated ACCH

RSACCH Measurements
101 | Repeated ACCH

RSACCH Measurements
102 | Repeated ACCH

RSACCH Measurements
103 | Repeated ACCH

RSACCH Enabled Legacy RLT
RSACCH Measurements
MOS MOS representation representation during during path path 1 1 measured measured in in Legacy Legacy RLT RLT area, area, for for RSACCH Enabled RSACCH Enabled Path Path distance distance 2.4km 2.4km
104 | Repeated ACCH

RSACCH Measurements
105 | Repeated ACCH

RSACCH Measurements
106 | Repeated ACCH

RSACCH Measurements
107 | Repeated ACCH

RSACCH Disabled Differentiated RLT
RSACCH Measurements
MOS MOS representation representation during during path path 1 1 measured measured in in Differentiated Differentiated RLT RLT area, for RSACCH area, for RSACCH Disabled Disabled Path Path distance distance 1.3km 1.3km
108 | Repeated ACCH

RSACCH Measurements
109 | Repeated ACCH

RSACCH Measurements
110 | Repeated ACCH

RSACCH Measurements
111 | Repeated ACCH

RSACCH Enabled Differentiated RLT
RSACCH Measurements
MOS MOS representation representation during during path path 1 1 measured measured in in Differentiated Differentiated RLT RLT area, for RSACCH area, for RSACCH Enabled Enabled Path Path distance distance 1.3km 1.3km
112 | Repeated ACCH

RSACCH Measurements
113 | Repeated ACCH

RSACCH Measurements
114 | Repeated ACCH

RSACCH Measurements
115 | Repeated ACCH

OBSERVATIONS
RSACCH Measurements
Accordingly to what was expected, with introduction of RSACCH, the SACCH repetition would turn the signaling more robust, making that in practice this could extend the limit of a cell.
From the trial point of view it was expected to see, when the call is locked into specific cell, that the call drops later when feature is active. The several tests do not reveal such extension for the cell limit, otherwise we would have samples decoded in far points.
116 | Repeated ACCH
CONCLUSION Voice Quality Measurements Results - VQ and Unitary
RSACCH Measurements
There was no chance during this trial to measure the RFACCH feature due to time constraints and difficulty on finding, on-site, a HO Fail or a Call drop during drive tests According to this set of tests and the cells chosen, it doesnt allow to show that the feature RSACCH extends the cells size
The reason could be linked with RSACCH not being triggered or triggered too late
Triggered by the RLT counter Apparently this trigger would be working Triggered for DL if BS receives a certain nb of SRR=1 during a sliding window. Not working with N85!
According to ALU previous tests N85 is not full compliant with RSACCH. The SRR=1 is not sent even under poor radio conditions This is being discussed with Nokia According According to to recent recent on-air on-air tests tests in in Lab, Lab, with with Nokia Nokia cooperation, cooperation, Mobile Mobile N6720 N6720 according according to to Nokia, Nokia, is is working working properly, properly, although although this this is is still still under under discussions discussions with with ALU ALU
117 | Repeated ACCH
4
118 | Repeated ACCH
Conclusion
Conclusion Non Regression Test: Feature is operational and brings no regression on the pilot area upon activating the feature with the default parameters. Slight variation are observed on pilot area as following:
Call drop rate is slightly enhanced by 3.3% Incoming HO failure rate is enhanced by 5~6% Outgoing HO drop rate enhanced by 15 %
Those Those variations variations cannot cannot be be confirmed confirmed as as gains gains as as the the tested tested network network is is using using very very slightly slightly the the most most robust robust codecs codecs
119 | Repeated ACCH
Conclusion Justifications Possible explanation for not so much observed impact Low percentage (%) of mobiles supporting Repeated SACCH feature (only 10%), and not necessarily those 10% facing radio problems Bug in Nokia mobiles with respect to Repeated SACCH, already acknowledged by Nokia (FR 3BKA45FBR286294) No major impact from AMR signaling vs. speech gap in TMO network was observed during the transition from mono codec to multi codec: 96% of codec distribution is 12.2kbps
Downlink AMR FR distribution - OZ_CELL2G: CellZone_TMO1_Essen1_H (217) - 11/05/2009 (Working Zone: WorkingZone_B11Test_extended_to_adjaBSCs) 90.% 80.% 70.% 60.% 50.% 40.% 30.% 20.% 10.% .% 4.75 5.15 5.9 6.7 7.4 7.95 10.2 12.2 FR AMR Codec (kbit/s ) % % Frames dist
120 | Repeated ACCH
Conclusion Lessons Learned Pilot area to be used should have been impacted by the AMR introduction or at least with significant radio and HO call drop rates For other trials, AMR Codec adaption thresholds should be fine tuned for the AMR subset containing robust codecs to the pilot area. Despite this trial permit access on most parameters tuning, it might be required a dedicated fine tuning on an implementation in a new network The issues found, which should be corrected soon, will contribute to enhance the feature performance: Nokia phones Misbehavior with RSACCH feature FR 3BKA45FBR286294 CDR increase with RxACCH FR 3BKA45FBR289679
Workaround applied to disable legacy MS support put KPIs back to normal values
121 | Repeated ACCH
5
122 | Repeated ACCH
Annex
Codec Redundancy Levels

Level of redundancy of EFR, AMR-FR and AMR-HR codecs: The SACCH frames have a 60% redundancy. The codecs in blue are more robust than the SACCH frames. Codec EFR (12.2 kbps) AMR-FR 12.2 kbps AMR-FR 10.2 kbps AMR-FR 7.95 kbps AMR-FR 7.40 kbps AMR-FR 6.70 kbps AMR-FR 5.90 kbps AMR-FR 5.15 kbps AMR-FR 4.75 kbps AMR-HR 7.95 kbps AMR-HR 7.40 kbps AMR-HR 6.70 kbps AMR-HR 5.90 kbps AMR-HR 5.15 kbps AMR-HR 4.75 kbps
123 | Repeated ACCH
Redundancy 46.5% 46.5% 55.3% 65.1% 67.5% 70.6% 74.1% 77.4% 79.2% 30.3% 35.1% 41.2% 48.2% 54.8% 58.3%
Cell Zone Division Criterion

Significant RxACCH capable MSs penetration > 5% Minimum 20 cells and traffic of 500 Erlangs as minimum per day in average Homogenous location of cells with no overlapping between cell zones should be considered as much as possible (trying to minimize inter-cellzone handovers). Cell zone A is preferably with bad HO KPIs, Cell Zone B is preferably with bad CDR KPIs, Cell Zone C is preferably with non optimal radio conditions at cell borders Cell Zone D and E should be impacted by AMR signaling imbalance problem equally as much as possible
124 | Repeated ACCH
Cell Zone Division Method (1/2)

The following information for all pilot cells is tabulated as following:
The pilot cells are plotted using MapInfo for CDR Radio, CDR HO, and Erlangs Following the division criterion, a compromise between Erlangs, call drops (due radio and HO) and location was followed to divide the pilot area to: Three cell zones for tuning phases Two cell zones for final optimization phase
A compromise was used as cells with bad KPIs were non-homogeneously located and pilot KPIs on average was very good
125 | Repeated ACCH
Cell Zone Division Method (2/2)

Division criteria was more biased towards Erlangs and CDR radio than CDR HO, as CDR HO was very low and CDR radio already indicated bad radio conditions for cell zone observed
Erlangs=921 Erlangs=2683 CDR Radio= 0.716% CDR HO= 0.27% CDR Radio= 0.43% CDR HO= 0.18%
Erlangs=2116 CDR Radio= 0.77% CDR HO= 0.31%
Erlangs=2035 Erlangs=2390 CDR Radio= 0.67% CDR HO= 0.25% CDR Radio= 0.75% CDR HO= 0.27%
Back
126 | Repeated ACCH
Nokia phones Misbehavior with RSACCH feature Not responding to SRO
127 | Repeated ACCH
Nokia phones Misbehavior with RSACCH feature Not setting SRR when needed
Back
128 | Repeated ACCH
www.alcatel-lucent.com
129 | Repeated ACCH

ALu Seminar RX ACCH

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

ALu Seminar RX ACCH

Uploaded by

Copyright:

Available Formats

B11 MR1 Ed1.x / Ed2.

x Seminar of GSM Network Engineering

Jorge S. Silva, Philip Fawzy, Robin Brassac March, 2010

Monitoring method FOA tests results 4. Conclusion

All Rights Reserved Alcatel-Lucent 2009

All Rights Reserved Alcatel-Lucent 2009

Feature Overview Introduction

All Rights Reserved Alcatel-Lucent 2009

Required by several operators:

All Rights Reserved Alcatel-Lucent 2009

Feature Overview Introduction Feature description Standardized in 3GPP Release 6:

Support mandatory for Release 6 MS,

Activated on a per-call basis.

All Rights Reserved Alcatel-Lucent 2009

Feature Overview Repeated DL FACCH

All Rights Reserved Alcatel-Lucent 2009

MS LAPDm Physical Layer

All Rights Reserved Alcatel-Lucent 2009

All Rights Reserved Alcatel-Lucent 2009

All Rights Reserved Alcatel-Lucent 2009

All Rights Reserved Alcatel-Lucent 2009

Feature Overview Repeated DL FACCH MS BTS Msg A Msg A Msg B Msg B

All Rights Reserved Alcatel-Lucent 2009

Feature Overview Repeated DL FACCH MS BTS Msg E Msg E

All Rights Reserved Alcatel-Lucent 2009

All Rights Reserved Alcatel-Lucent 2009

Feature Overview Repeated DL FACCH RDFACCH dynamic activation in ALU implementation

Better intrinsic voice quality

T YS H _ FR _2 _ R R AM _TH + R _2 _F R R T TH AM YS R_ H F R_ R_ _F R AM 1 AM R_ H + Codec T 1 R_ R_ F Mode 1+ H R_ _T M R A F RDFACCH R_ M A

Codec Mode 2 + RDFACCH

Codec Mode 2 + RDFACCH

Codec Mode 1 + RDFACCH

Feature Overview Repeated SACCH

All Rights Reserved Alcatel-Lucent 2009

Both DL and UL signaling links can be strengthened using repetition mechanism

All Rights Reserved Alcatel-Lucent 2009

All Rights Reserved Alcatel-Lucent 2009

All Rights Reserved Alcatel-Lucent 2009

All Rights Reserved Alcatel-Lucent 2009

All Rights Reserved Alcatel-Lucent 2009

All Rights Reserved Alcatel-Lucent 2009

All Rights Reserved Alcatel-Lucent 2009

N/A N/A N/A N/A N/A

1/6 1/7 1/8 1/9 1/10

#7, SRO = 0 #8, SRO = 0 #8 repeated, SRO = 0 #9, SRO = 0

All Rights Reserved Alcatel-Lucent 2009

Feature Overview Repeated UL SACCH Illustrations BTS

#1, SRO = 0 #2, SRO = 0 #3, SRO = 0

All Rights Reserved Alcatel-Lucent 2009

Feature Overview Limitations

All Rights Reserved Alcatel-Lucent 2009

The feature is fully available (RDFACCH + RSACCH) on Release 6 MS only.

All Rights Reserved Alcatel-Lucent 2009

All Rights Reserved Alcatel-Lucent 2009

All Rights Reserved Alcatel-Lucent 2009

Activation Strategy Pre-requisites

All Rights Reserved Alcatel-Lucent 2009

All Rights Reserved Alcatel-Lucent 2009

Activation Strategy Parameter Settings

All Rights Reserved Alcatel-Lucent 2009

Range/ Default value {0, 1, 2}1/0

10 {0,...,127}/10 For RLT of 24

If the customer has customized parameter L_RXQUAL_xL_P (where x is U or D) in