Repeated ACCH: B11 MR1 Ed1.x / Ed2.x Seminar of GSM Network Engineering
Repeated ACCH: B11 MR1 Ed1.x / Ed2.x Seminar of GSM Network Engineering
x
Seminar of GSM Network Engineering
Repeated ACCH
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
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.
Feature description
Repeated ACCH consists of two features:
Repeated Downlink FACCH (RDFACCH)
Repeated SACCH (RSACCH)
Required by several operators:
SFR, T-Mobile, Orange.
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.
BTS MS
3GPP TS 44.006
LAPDm LAPDm
1 radio TS
Ha lf FACCH burst of the repetition
Ha lf TCH/ FR burst
• Top: first half (before the training sequence),
Ha lf idle or SACCH burst
~40 ms
Ha lf TCH/ FR burst
O dd
Even
~40 ms
Ha lf TCH/ HR burst
Msg C
NOK
Msg C
NOK
OK
Msg F
NOK
Msg F
NOK
NOK
Soft combining
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.
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.
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.
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
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.
RDSACCH
2/7 N/A 1/7 OK decoding due to NOK
#8, SRO = 0 #8, SRR
repetition of = 1 NOK
dynamically
activated 3/8 N/A 1/8 OK message and NOK
#8 repeated, SRO = 0 soft combining
#9, SRR = 1 OK
4/9 N/A 1/9 OK NOK
#9, SRO = 0 #10, SRR = 1
5/10 N/A 1/10 OK OK
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
AMR Codec Subset and Codec Adaption thresholds should be optimized for area of
feature activation “Checked through the RMS report ; ALC_MONO_RMS_AMR”
New parameters
Range/
Recommended
Parameter Name Definition Instance Default
Value
value
Enables repeated downlink FACCH for
EN_REP_DL_FACCH Cell {0, 1, 2}1/0 2
AMR calls
1
0: disabled; 1: enabled for LAPDm command frames; 2: enabled for LAPDm command frames and also for response frames
2
0: repeated DL FACCH enabled only for AMR MS with repeated ACCH Capability bit = 1; 1: repeated DL FACCH enabled for
all AMR MS
3
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
New parameters
Instan Range/ Default Recommended
Parameter Name Definition
ce value value
Repeated DL FACCH activation
threshold for AMR HR. Dynamic
REP_DL_FACCH_THRES_AMR_HR activation is done as long as codec Cell {0,1,...,5}1/3 3
mode request CMR threshold.
Repeated DL FACCH activation
threshold for AMR WB. Dynamic
REP_DL_FACCH_THRES_AMR_WB activation is done as long as codec Cell {0, 1, 2}2/1 NA
mode request CMR threshold.
Enables repeated SACCH for SAPI 0
frames in case of AMR calls (for mobile
EN_REP_SACCH station having indicated the support of Cell {0,1}/0 1
the feature).
Repeated DL SACCH activation
threshold for UL RLT (Radio Link
Timer) counter. Dynamic activation is 10
RADIOLINK_REP_DL_SACCH triggered in the BTS when the UL RLT Cell {0,...,127}/10
counter is inferior or equal to that “For RLT of 24”
threshold.
1
0: off; 1: 4,75 kbs; 2: 5,15 kbs ; 3: 5,90 kbs; 4: 6,70 kbs; 5: 7,40 kbs
2
0: off; 1: 6,60 kbs; 2: 8,85 kbs ; 3: 12,65 kbs
New parameters
Range/ Recommended
Parameter Name Definition Instance
Default value values
Lower uplink quality threshold for Equal to
power control for AMR calls with
L_RXQUAL_UL_P_AMR_RXACCH1 activated Repeated DL FACCH and Cell {0,...,7}/3 L_RXQUAL_UL_P
Repeated SACCH. or slightly higher
Modified parameters
Range/ Recommended
Parameter Name Definition changes Instance
Default value value
Counter threshold to detect a radio link
failure on the uplink path for calls using an
AMR codec and for which Repeated SACCH Cell {1,...,255}/1
RADIOLINK_TIMEOUT_BS_AMR 32
and/or Repeated DL FACCH are not 8
activated.
Updated the definition: this timer can also
be used for AMR calls (NB or WB) for which {1,...,255}/1
RADIOLINK_TIMEOUT_BS1 Repeated SACCH and Repeated DL FACCH Cell 8
NA
are activated
Initial value of MS counter for radio link
supervision, when an AMR codec is used
RADIOLINK_TIMEOUT_AMR1 and for which call Repeated SACCH and/or Cell {4,...,64}/16 32
Repeated DL FACCH are not activated.
Updated the definition: this timer can also
RADIOLINK_TIMEOUT1 (BSC)
This also applies to be used for AMR calls (NB or WB) for which
Repeated SACCH and Repeated DL FACCH Cell {4,...,64}/16 NA
RADIOLINK_TIMEOUT1 (MFS) are activated
1
HMI name for RADIOLINK_TIMEOUT_BS is RADIOLINK_FAILURE_THRES
RadioLink supervision
When a SACCH block is received a first decoding is performed without
combining
1) If it is correct RLC is incremented by 2
2) If it fails new decoding performed using soft combining with previous SACCH
block
– a) if it is correct RLC is incremented by 2
– b) if it fails RLC is decremented by 1
New Counters
Counter Measured
refname LongName Definition object Domain Type
NB_MS_REPEATED_ACCH_Capa Number of calls for which the mobile stations Quality of
MC990 TRX 110
ble supporting the repeated ACCH capability service
New Counters
Counter Measured
refname LongName Definition object Domain Type
Number of TCH using AMR codecs (NB or WB)
but with Repeated FACCH not activated,
NB_AMR_TCH_DROP_OUT_HO_ Quality of
MC995 dropped during the execution of any TCH TRX 110
TRX service
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 Quality of
MC996 TRX 110
TRX_RFACCH handover, per TRX. This counter takes into service
account handovers from TCH in traffic or in
signaling mode.
Counter Measured
refname LongName Definition objectDomain Type
Indicates the number of SAPI 0 frames that were
not repeated.
(SDCCH
S09 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
S16 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
T08 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
T15 NB_FRAMES_REPEATED This counter corresponds to the CNT_I_RETX QoS 151
observations)
field of the 48.058 PHYSICAL CONTEXT CONFIRM
message.
1
Type 10 is SDCCH observation; type 15 is TCH observation
TC MSC
A
Please refer to feature test plan for other NPO reports that can be interesting to
monitor the feature behavior
Planning Overview
One RNE resource is required for generic Statistical and Unitary Tests
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
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
HO: Success rate, Reversion Old Channel Rate, Rate of HO failure, Rate of HO failure due to Radio and
Handover Efficiency
Where YY is FR or HR and XX is UL or DL
1
2
Only applicable if we can change the parameters L_RXQUAL_XL_P due to recommended rules:
REP_DL_FACCH_THRE
S_AMR_YY 3 3
5 7
“Cell Zone A” All Pilot All BSC
L_RXQUAL_XX_P_AMR
3 1.9 or 3.4 **
_RXACCH 1.1 4
All Pilot All BSC
“Cell Zone C”
* More information about choosing optimized parameter setting available in optimization test section
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
TMO Essen
Cell Zone RADIOLINK_TIMEOUT_BS_A
RADIOLINK_TIMEOUT_AMR Pilot
Parameter MR Example
Cell Zone D 24 24
Cell Zone E 32 32
Call Drop: [Call_drop_rate, Call_drop_radio_rate, and Call_drop_HO_rate] and AMR/Non AMR call failure rates
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
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
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
100.00%
80.00%
60.00%
%
40.00%
20.00%
0.00%
RACCH RACCH
Mono Codec Multi Codec RACCH Default RACCH Final
Tuning1 Tuning2
RxACCH_MS_Penetration_Rate 0.00% 9.98% 10.36% 10.93% 10.97% 10.38%
RDFACCH_BSC_Activated_MS_Penetration_ 0.00% 0.00% 85.71% 85.98% 10.97% 10.38%
Rate
RSACCH_BSC_Activated_MS_Penetration_R 0.00% 0.00% 10.36% 10.83% 10.97% 10.38%
ate
Time
100% 1.55%
90%
1.50%
80%
70% 1.45%
60%
1.40%
50%
1.35%
40%
robust codec are not often 0% Mono Codec Multi Codec RACCH Def ault RACCH Tuning1 RACCH Tuning2 RACCH Final
1.20%
expected to be minimal
as calls are in good radio AMR FR UL Codec Distribution
1.50%
1.00%
%
0.50%
0.00%
Mono Codec Multi Codec RACCH Default
HO_Inc_BSC_fail_rate 1.31% 1.30% 1.22%
HO_Inc_BSC_unsuccess_rate 1.55% 1.54% 1.46%
HO_Out_BSC_drop_rate 0.13% 0.13% 0.11%
HO_Out_BSC_prep_fail_rate 0.28% 0.26% 0.28%
HO_Out_BSC_ROC_rate 1.18% 1.17% 1.10%
Call_drop_rate 0.84% 0.89% 0.86%
Call_drop_radio_rate 0.65% 0.69% 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
0.45%
REP_DL_FACCH_THRES_AMR_FR= 3 5 7
0.40%
with RDFACCH
0.30%
0.25%
support as well
0.00%
moving the Mono Codec
0
Multi Codec
0.34%
RACCH Default
0.26%
RACCH Tuning1
0.23%
RACCH Tuning2
0.27%
parameter from 3
NonAMR_NA_Call_HO_f ail_rate
AMR_NA_Call_HO_f ail_rate 0 0.38% 0.22% 0.22% 0.26%
RDFACCH is 1.60%
1.40%
impact.
0.20%
0.00%
Mono Codec Multi Codec RACCH Def ault RACCH Tuning1 RACCH Tuning2
2.50%
2.00%
1.50%
%
1.00%
0.50%
0.00%
B11 Indicators Only
Mono Codec Multi Codec RACCH Default RACCH Tuning1 RACCH Tuning2
Transmission
It is recommended
problemstoexistence
use the during
REP_DL_FACCH_THRES_AMR_FR=
tuning phase increased call drop
3 (orrates
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 supportwith
deactivation
RDFACCH
3.00%
REP_DL_FACCH_THRES_AMR_FR= 10 5 18
2.50%
2.00%
1.50%
%
1.00%
0.50%
B11 Indicators Only
0.00%
Mono Codec Multi Codec RACCH Default RACCH Tuning1 RACCH Tuning2
NonAMR_NA_Call_radio_fail_rate 0.00% 2.47% 2.23% 2.15% 2.48%
AMR_NA_Call_radio_fail_rate 0.00% 0.81% 0.62% 0.69% 0.66%
AMR_RSACCH_Call_radio_fail_rate 0 0.00% 0.18% 0.21% 0.22%
Call_drop_rate 0.86% 0.95% 0.94% 1.08% 1.03%
Observation Week
• It isItclear
is recommended to use the values 10 for a good compromise for activating RSACCH and
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
For RLT due
of to the
24, transmission
the problem and sites value
RADIOLINK_REP_DL_SACCH failurecan
during tuning
be fine phases
tuned up to 15 to adapt to the
• It is seennetwork and customer requirements. Above than 15 if RLT value is higher than 24
that the value 5 “tuning 1” degrades AMR radio drops when compared to the value 18
“tuning
L_RXQUAL_XX_P_AMR_RXACCH=
0.25%
3 1.1 4
0.20%
0.15%
%
0.10%
0.05%
0.00%
Mono Codec Multi Codec RACCH Default RACCH Tuning1 RACCH Tuning2
Changing the NonAMR_NA_Call_HO_fail_rate 0 0.18% 0.23% 0.16% 0.18%
L_RXQUAL_XX_P_AMR AMR_NA_Call_HO_fail_rate 0 0.14% 0.12% 0.10% 0.16%
8.00%
6.00%
%
4.00%
2.00%
0.00%
Mono Codec Multi Codec RACCH Default RACCH Tuning1 RACCH Tuning2
HO_Inc_BSC_fail_rate 0.92% 0.84% 0.77% 0.59% 0.87%
HO_Inc_BSC_unsuccess_rate 1.29% 0.99% 0.99% 11.20% 1.18%
HO_Out_BSC_drop_rate 0.11% 0.09% 0.07% 0.07% 0.11%
HO_Out_BSC_prep_fail_rate 0.35% 0.21% 0.24% 9.14% 0.28%
HO_Out_BSC_ROC_rate 0.82% 0.75% 0.70% 0.58% 0.77%
Observation Week
2.00%
L_RXQUAL_XX_P_AMR_RXACCH= 3 1.1 4
1.50%
1.00%
%
0.50%
B11 Indicators Only
0.00%
Mono Codec Multi Codec RACCH Default RACCH Tuning1 RACCH Tuning2
NonAMR_NA_Call_radio_fail_rate 0.00% 1.75% 1.41% 1.07% 1.20%
AMR_NA_Call_radio_fail_rate 0.00% 0.51% 0.34% 0.36% 0.44%
AMR_RSACCH_Call_radio_fail_rate 0 0.00% 0.11% 0.11% 0.17%
Call_drop_rate 0.68% 0.66% 0.56% 0.52% 0.64%
Observation Week
According to trial the appropriate RxACCH PC parameter to be used is the same as legacy PC parameter.
During changes
Apparently there’sofsome
L_RXQUAL_XX_P_AMR_RXACCH from
margin to increasing RxACCH PC 3 to 1.1 ismore
parameter observed enhances
than legacy of the radio
parameter without
drops, but no
observe impact. improves on the radio drops for AMR with RSACCH support
During changes
Combining of L_RXQUAL_XX_P_AMR_RXACCH
ALU recommendation from 3 to 4 degrades
“L_RXQUAL_xL_P_AMR_RXACCH is observed thatand
>=L_RXQUAL_xL_P” radio
TMOdrops
slightly increase,we
recommendation, specifically thefollowing
will use the radio drops for AMR with RSACCH support
rules:
The impact of PC parameters
If L_RXQUAL_XX_P=2.9 tuning cannot be uncorrelated
L_RXQUAL_XX_P_AMR_RXACCH = with
3.4 the transmission problem occurred at
the same time
If L_RXQUAL_XX_P=1.1 L_RXQUAL_XX_P_AMR_RXACCH = 1.9
81 | Repeated ACCH All Rights Reserved © Alcatel-Lucent 2009
Optimization Test Results “Final optimized values”
Radio Call Drop Rates
Cell Zone D RxACCH + LRLT --> Radio Call Drop Rates
2.50%
2.00%
%
brought no impact on 1.00%
For LRLT cell zone a slight CDR AMR_NA_Call_radio_fail_rate 0.00% 0.62% 0.49% 0.51%
reference)
Cell Zone E DRLT + RxACCH --> Radio Call Drop Rates
For DLRLT cell zone CDR came to
initial mono codec value, 2.50%
reference) 0.50%
0.00%
Mono Codec Multi Codec RACCH Default RACCH Final
0.40%
0.35%
0.30%
0.25%
0.20%
%
0.15%
0.10%
areas AMR_NA_Call_HO_fail_rate
AMR_RDFACCH_Call_HO_fail_rate
0
0
0.34%
0.00%
0.21%
0.08%
0.23%
0.05%
Observation Week
RxACCH capable MS HO drops are
stable Cell Zone E
DRLT+RxACCH --> HO Call Drop Rates
0.30%
RDFACCH capable MS HO drops
slightly enhanced from 0.06% to 0.25%
0.10%
0.05%
0.00%
Mono Codec Multi Codec RACCH Default RACCH Final
NonAMR_NA_Call_HO_fail_rate 0 0.19% 0.23% 0.24%
AMR_NA_Call_HO_fail_rate 0 0.26% 0.16% 0.20%
AMR_RDFACCH_Call_HO_fail_rate 0 0.00% 0.06% 0.05%
Observation Week
Objective: Investigate what’s 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
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
Test_SAMPLE.wav
Nemo PC
Path representation
for the cell
measured in Legacy
RLT area – Path
distance 2.4km
Path representation
for the cell
measured in
Differentiated RLT
area – Path distance
1.3km
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 wasn’t 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
-2
-1
0
1
2
3
4
5
6
7
-2
-1
0
1
2
3
4
5
6
7
31 8.
.3 9:
4
93
10 8 4 2
: 12
8:
08
: 40 9: .2
.7 48 56
10
0 1 :1
:
passages:
12 7.
:5 9: 57
0. 48 8
10 03 :2
:12 2 9:
6.
90
:5 48 4
9. :3
10 35 6.
:1 6 9: 22
4
91 | Repeated ACCH
48
3: :4
08 5.
10 .6 9: 55
:1
80 48 0
3: :5
4.
51 9: 76
.2 50 0
10 32 :5
:1 5.
5: 51 4
19 :1
.1 4.
72
04
6
0
0
-80
-60
-40
-20
-80
-60
-40
-20
-120
-100
-120
-100
MOS
MOS
RxQ avg
RxQ avg
RxLev avg
RxLev avg
10
10 :0
:26 0 :3
0
1
2
3
4
5
6
7
:5
0
1
2
3
4
5
6
7
0.
9. 10 20
10
:2
39
6 :0 6
7: 0:3
08 9.
10 .7 10 53
:2 20 :0 0
7: 0:
18 48
10 .0 10 .8
:2 46 52
:0
7: 0:
27 58
10 .3 .1
:2 68 10 78
7: :0
36 1:
07
.9 1:
10 88 44
:2 .7
8: 10 92
23 :0
10 .3 1:
:2 12 54
8: 10 .1
32 12
.6 :0
10 3 2:
:2 4 03
8: 10 . 4
41 42
10 .9 :0
58 2:
:2 12
8:
51 10 .7
66
10 .2 :0
:2 82 2:
9: 22
00 10 .0
.6 90
10 0 :0
:2 6 2:
31
9:
09 10 . 4
.9 12
10 26 :0
:2 2:
9: 40
19
10 .7
10 .2 38
:2 52 :0
9: 2:
50
28
.5 10 . 04
10
:2 74 :0 8
Time Evolution Graph - VQ4, DL RSACCH OFF, Legacy RLT
Time Evolution Graph - VQ2, DL RSACCH OFF, Legacy RLT
9: 2:
37 59
10 .8 10 .3
98 78
:2 :0
9: 3:
47 08
.2 .7
16 02
0
0
-80
-60
-40
-20
-80
-60
-40
-20
-120
-100
-120
-100
RSACCH Measurements
RSACCH Disabled (DL, Legacy RLT) – VQ samples are recorded in Opera Client
MOS
MOS
RxQ avg
RxQ avg
RxLev avg
RxLev avg
21 21
:4
8: :18
:2
-2
-1
0
1
2
3
4
5
6
7
0
1
2
3
4
5
6
7
21 52. 6.
:4 0 21 64
9: 58 :1 2
8:
21 01. 35
:4 3 21 .9
:1
enabled
9: 82 66
21 10. 8:
:4 7 21
45
.2
9: 02 :1 90
21 20. 8:
:4 0 21
54
9: 30 .6
:1 14
21 29. 9:
:4 3 03
9: 52 21 .9
21 38. :1 34
:4 6 9:
92 | Repeated ACCH
13
9: 78 21 .2
21 47. :1 60
:4 1 9:
22
9: 00 21 .5
21 57.
3 :1 84
:5 9:
0: 24 31
21 06. 21 .9
:5 6 :1 06
0: 48 9:
41
21 15. 21 .2
:5 9 :1 32
0: 72 9:
50
21 25. 21 .5
:5 2 :1 56
0: 96 9:
21 34. 59
6 21 .8
:5 :2 78
0: 18 0:
21 07. 21 .7
:5 8 :2 92
2: 24 1:
33
21 17. 21 .1
:5 1 :2 10
2: 78 1:
26 42
.3 .4
42 36
0
0
-80
-60
-40
-20
-80
-60
-40
-20
-120
-100
-120
-100
MOS
MOS
RxQ avg
RxQ avg
RxLev avg
RxLev avg
22 21
:0 :
1 37
:1
0
1
2
3
4
5
6
7
22 :48
-2
-1
0
1
2
3
4
5
6
7
:0 .18 21 4.
1 06
:3 4
22 :57 2 7:
:0 .50 23
2 21 .3
22 :06 6 :3 90
:0 .82 7:
2 32
22 :16 8 21 .7
:0 .15 :3 16
2 7:
42
22 :25 4 21 .0
:0 .47 :3 40
2: 7:
22 34 8 51
:0 .80
2 21 .3
22 :44 2 :3 62
8:
:0 .12 00
2 21 .6
22 :53 4 :3 82
:0 .44 8:
3
22 :58 2 8:
:0 .71 56
4 21 .6
22 :08 4 :3 28
:0 .03 9:
4 05
22 :17 6 21 .9
:0 .3 6 :3 50
4 9:
15
22 :26 0 21 .2
:0 .68
4 :3 76
9:
22 :36 4 24
:0 .00 21 .6
4 :3 00
22 :45 8 9:
:0 .3 33
4 3 21 .9
22 :54 2 :3 22
:0 .65 9:
5: 43
22 03 6 21 .2
:0 .98 :3 46
5 9:
52
22 :13 0
:0 .30 21 .5
5 :4
0:
70
22 :22 4 01
:0 .6 21 .8
Time Evolution Graph - VQ2, DL RSACCH ON, Legacy RLT
5: 28
22 31 :4 94
:0 .94 0:
5 21
11
.1
22 :41 4 :4 44
:0 .26 0:
5: 20
50 0 .5
.5 40
62
0
0
-80
-60
-40
-20
-80
-60
-40
-20
-120
-100
-120
-100
MOS
MOS
RSACCH Measurements
RxQ avg
RxQ avg
RSACCH Enabled (DL, Legacy RLT) – VQ samples are recorded in Opera Client
RxLev avg
RxLev avg
12 11
:0
8: : 34
0
1
2
3
4
5
6
7
1 :5
0
1
2
3
4
5
6
7
1. 11 7.
12
44
4 : 35 590
:0 :
8: 11 06.
2 0. :3 9
77 5: 14
12 0 11 16.
: 08 :3 2
:3 5: 38
0 .0 11 25.
12 94 :3 5
: 5: 60
08 11 34.
:3
9 :3 8
.4 5 : 84
93 | Repeated ACCH
12 18 11 44.
Server
: 08 :3 2
:4 5: 08
8 .7 11 53.
4 :3 5
12 2 6: 32
:0
8 :5
11 02.
8
8. :3
06 6: 54
12 4 11 12.
1
: 09 :3
:0 6: 78
7 .3 11 21.
5
1 .3
11 41.
3
0 :3
12 0 8: 56
: 10 11 50.
:4 :3 6
9 .9 9: 76
46 00
.0
04
0
0
-80
-60
-40
-20
-80
-60
-40
-20
-120
-100
-120
-100
MOS
MOS
RxQ avg
RxQ avg
RxLev avg
RxLev avg
12 11
:1 :5
0
1
2
3
4
5
6
7
8: 11 5:1
4
0
1
2
3
4
5
6
7
7. :5 2.2
35 11 5:2 60
12 6 :5 1.5
: 18 11 5:3 84
:5 :5 0.9
6 .6 11 5:4 06
8 0 :5 0.2
12 11 5:4 30
:1 :5 9.5
9:
0 6. 11 5:5 54
00 :5 8.8
12 4 11 6:0 76
:1 :5 8.2
9 :1 11 6:1 02
5. :5 7.5
32
12 8 11 6:2 24
: :5 6.8
19 11 6:3 48
:2
4 .6
:5 6.1
5 11 6:4 72
12 :5 0.7
:2
0: 11 8:0 60
1 1. :5 0.0
26 11 8:0 84
12 8 :5 9.4
:2 11 8:1 08
0:
2 0.
:5 8.7
59 11 8:2 30
12 2 :5 8.0
: 20
11 8:3 54
:5 7.3
:3
9 .2
11 8:4 78
4 0
:5 6.7
12 11 8:5 02
:2 :5 6.0
0:
4 8.
11 9:0 26
56 :5 5.3
12 4 11 9:1 50
:2 :5 4.6
0: 11 9:2 74
5
Time Evolution Graph - VQ2, UL RSACCH OFF, Legacy RLT
:5 3.9
Time Evolution Graph - VQ4, UL RSACCH OFF, Legacy RLT
7.
88 11 9:3 92
12 8 :5 3.3
: 21 11 9:4 20
:2 :5 2.6
5 .8 9: 4
51 4
5 8 .9
68
0
0
-80
-60
-40
-20
-80
-60
-40
-20
-120
-100
-120
-100
RSACCH Disabled (UL, Legacy RLT) – VQ samples are recorded in Opera
MOS
MOS
RxQ avg
RxQ avg
RxLev avg
RxLev avg
RSACCH Measurements
22
:0 21
9:
0
1
2
3
4
5
6
7
21 :4
.2 7
0
1
2
3
4
5
6
7
92 :5
22 3.
:0 21 45
9: :4 6
30
.6 8 :0
22 16 2.
78
:0 21 0
9: :48
49 :1
.2 2.
22 60 10
:0 21 4
9: :4
58 8:
.5 21
94 | Repeated ACCH
22 86 .4
21 92
Server
:1 :4
0: 8:
07 40
.9 .1
22 10 21 38
:1 :4
0: 8:
17 49
.2 .4
22 34 21 62
:4
:5
50 0:
.4 41
22 70 .3
21 44
:1 :5
1: 0:
59 50
.7 .6
86 66
0
0
-80
-60
-40
-20
-80
-60
-40
-20
-120
-100
-120
-100
MOS
MOS
RxQ avg
RxQ avg
RxLev avg
RxLev avg
22 21
:2 : 58
0:
0
1
2
3
4
5
6
7
0
1
2
3
4
5
6
7
00 :4
.4 7 .7
22 5 4 21 78
:2 :5
0: 8
0 9. :5
22 77 7 .1
: 8 21 00
20
:1 :5
9 9 :0
.1 6
22 0 4 .4
:20 21 24
:3 : 59
7. :1
22 75 5
:2 0 .7
0: 21 48
47 : 59
.0 :2
22 76 5.
:2 07
0: 21 2
56 : 59
.3
.6 22 66
22 92 : 00
:2 :1
1:
43 1 .6
.0 22 90
22 14 :0
:2 0 :2
1: 1
52 .0
.3 22 12
22 40 :0
:2 0
2: :3
01 9 .6
.6 22 60
22 64
:2 : 00
2: :4
10
.9 8 .9
22 86 22 82
:2
2: : 00
20 :5
.3 8 .3
22 10 22 06
:2 :
Time Evolution Graph - VQ4, UL RSACCH ON, Legacy RLT
2: 01
Time Evolution Graph - VQ2, UL RSACCH ON, Legacy RLT
29 :0
.6 7.
22 34 62
:2 22 8
2: : 01
38 :1
.7 6
94 .9
54
0
RSACCH Enabled (UL, Legacy RLT) – VQ samples are recorded in Opera
0
-80
-60
-40
-20
-120
-100
-80
-60
-40
-20
-120
-100
MOS
MOS
RxQ avg
RxLev avg
RxQ avg
RxLev avg
RSACCH Measurements
TIME EVOLUTION GRAPHS
Voice Quality Measurements Results – VQ and Unitary RSACCH Measurements
7 -76
7 -80
-78
-81
6
6
-82 -80
5 -82
5 -83
-84 -84
4
4 MOS
-85 MOS -86 RxQ avg
RxQ avg RxLev avg
-86 RxLev avg 3
3 -88
-87
-90
2
2 -88
passages among 4:
1
-90
-94
0 -96
0 Time Evolution Graph - VQ3, DL RSACCH OFF, Differentiated RLT -91 Time Evolution Graph - VQ4, 10:57:52.806
DL RSACCH OFF,10:58:02.126
Differentiated RLT
• MOS decrease with DL
10:57:24.844 10:57:34.168 10:57:43.490 10:58:11.406
10:43:50.364 10:43:59.624 10:44:18.284
-82
-80.5
5 5
-81
4 -84 4
-81.5
3 3
MOS MOS
-86 RxQ avg -82 RxQ avg
RxLev avg RxLev avg
2 2
-82.5
1 -88 1
-83
0 0
-83.5
11:07:48.974 11:07:58.296 11:08:07.608 11:21:32.856 11:21:42.184 11:21:51.502
-90
-1 -1 -84
-2 -92 -2 -84.5
7 0 7 -72
-74
6 6
-20
-76
5 5
-40 -78
4 4
-80
MOS MOS
-60 RxQ avg RxQ avg
RxLev avg -82 RxLev avg
3 3
-80 -84
2 2
is active
7
11:34:48.464 11:34:57.788 11:35:07.112 11:35:16.436 11:35:25.758 11:35:35.072 11:35:44.354
-76
7
11:51:37.834 11:51:47.160 11:51:56.484 11:52:05.808 11:52:15.126 11:52:24.454 11:52:33.774
-83
-78 -84
6
6
-80 -85
5
5
-86
-82
4
MOS 4
-87
MOS
-84 RxQ avg
RxQ avg
RxLev avg
3 -88 RxLev avg
3
-86
-89
2
-88 2
-90
1
-90 1
-91
0 -92
0 -92
12:09:37.636 12:09:46.964 12:09:56.286 12:10:05.588
12:25:13.062 12:25:22.408 12:25:31.732 12:25:41.052
7 0 7 1.2
6 6
-20 1
5
-40 5
4
MOS
4
Problem with data 0.8
-80 3
2
0.4
2
6
8
6
6
67
32
29
3
.0
.7
.3
.7
.3
.6
.9
.5
2.
1.
9.
32
6
8
:2
:4
:5
:1
:2
:4
:5
:5
:0
:1
9:
0:
49
49
49
50
50
50
50
50
51
51
:5
:
:
:
15
15
15
15
15
15
15
15
15
15
15
15
7 0
7 -75
6 6
-20 -80
5 5
-40 -85
4 4
MOS MOS
-60 RxQ avg -90 RxQ avg
RxLev avg RxLev avg
3 3
-80 -95
2 2
-100 -100
1 1
0 -120 0 -105
8
04
24
98
22
84
4
68
40
0
41 8
14
6
98
6
65
5
:1 .70
:1 .31
55
:1 .87
52
:1 .78
:1 .37
:1 .02
:1 .34
:1 .67
:1 .99
64
:1 .96
:1 .29
:1 .61
:1 .93
:1 .26
:1 .58
:1 .90
:1 .20
:1 .84
:1 .17
:1 .49
:1 .81
14
.0
.4
.7
.0
.7
.3
.6
.0
.3
.3
.6
.9
.5
.9
.5
.8
.5
.1
3.
4.
.
.
12
13
22
31
50
59
18
27
8
46
16 :38
16 :06
16 :15
16 :25
16 :53
16 :58
16 :07
16 :26
16 :54
16 :03
16 :31
16 :29
16 :48
16 :57
16 :34
16 :43
16 :02
16 :11
16 :21
16 :30
16 :39
16 :17
16 :35
16 :45
16 :13
:2
:3
:4
:1
:2
:3
:4
:0
:5
:5
3:
5:
5:
5:
5:
5:
6:
6:
6:
8:
23
23
23
24
24
24
24
25
23
24
5
8
14
:2
:2
:2
:2
:2
:2
:2
:2
:2
:1
:1
:1
:1
:
:
16
16
16
16
16
16
16
16
16
16
16
16
16
16
16
16
16
16
16
16
0
1
2
3
4
5
6
7
16 :05
0
1
2
3
4
5
6
7
:4 .98
2 6 :1 .43
8
16 :15 6
:4 .63 16 :14.
2 :1 75
16 :43 8 8 8
:4 .60 16 :33
3 8 :1 .40
16 :02 8:
4 6
:4 .2 5
3
16 2
6 :1 .73
16 :20 8 0
:4 .90
3 2
16 :52
:1 .05
16 :39 4
98 | Repeated ACCH
9:
:4 .5 5 0 1
3 0 16
16 :58 :1 .37
:4 .19 9 8
4 8 16 :10.
16 :26 :1 7
9: 02
:4 .1 6
4 2 0
8 16
16 :54 :1 .02
:4 .14 9 4
5 0 16 :29
16 :22 :1 .34
: 4 . 11
5
9:
3 8
0 16 8
16 :40 :1 .67
:4 .75
6 9 2
6 16 :47
16 :08
. :1 .99
Opera Server
:4 72 6
6 8
9:
5
16 :27 16 7
:2 .31
:4 .37
6 6 0 8
16 :46 16 :06
:4 .02 :2 .64
7 0:
2 2
16 :04 4
.
16 5
:4 67 :2 .29
7
:5 49 9
0 6
16
:2 .20
16 :11
:5 .1 4 1 2
0 0 16 :58.
5
:5 .79 2: 26
0: 16 07
57 0 :2 .85
.7 2:
60 35 0
.8
20
0
0
-80
-60
-40
-20
-120
-100
-80
-60
-40
-20
-120
-100
MOS
MOS
RxQ avg
RxLev avg
RxQ avg
RxLev avg
17
: 02 16
17 :18 :
0
1
2
3
4
5
6
7
29
:0 .6 :2
1
0
1
2
3
4
5
6
7
2 4.
17 :27 0 16 04
:0 .9 :29 8
2: 34 :3
17 37 3.
:0 .2 16 37
2 5 :2 2
17 :46 8 9:
: 0 . 58 42
2 16 .6
17 : 55 2 :2 96
:0 .9 9:
3 0 52
17 :05 0 16 .0
:0 .2 :3 20
3 1 0:
17 :14 2 01
:0 .5 16 .3
3 5 :3 44
17 :23 2 0:
17 :38 0 16 .9
:0 .4 :3 62
4 6 0:
17 :47 4 57
:0 .7 .2
4 8 16 84
17 :57 8 :3
:0 .1 1:
5 1 06
.6
17 : 06 2 16
:3 08
:0 .43
5 1:
15
17 :15 6 16 .9
:0 .7
5 5 :3 32
17 :25 8 1:
:0 .0 25
5 8 16 .2
56
17 : 43 2 :3
:0 .7 1:
5 3 34
17 :53 0 16 .5
:0 .0 :3 80
6 5 1:
17 :02 2 43
:0 .37 16 .9
6 :3 02
17 :11 6 2:
:0 .7 02
6 0 16 .5
17 :21 0 :3 50
:0 .0 2:
6 2 11
17 : 30 4 16 .8
: 0 . 34 :3 72
Time Evolution Graph - VQ4, UL RSACCH ON, Differentiated RLT
6:
3 6 2:
Time Evolution Graph - VQ2, UL RSACCH ON, Differentiated RLT
17 21
:0 9.6 16 .1
6: 70 :3 96
48 2:
.9 30
94 .5
RSACCH Enabled (UL, Differentiated RLT) – VQ samples are recorded in
20
0
-80
-60
-40
-20
-120
-100
-94
-92
-90
-88
-86
-84
-82
-80
-78
-76
-74
RSACCH Measurements
MOS
MOS
RxQ avg
RxQ avg
RxLev avg
RxLev avg
TIME EVOLUTION GRAPHS
Voice Quality Measurements Results – VQ and Unitary RSACCH Measurements
OBSERVATIONS
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 – That’s 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
RSACCH Disabled
Legacy RLT
RSACCH Disabled
Legacy RLT
RSACCH Disabled
Legacy RLT
RSACCH Disabled
Legacy RLT
RSACCH Enabled
Legacy RLT
RSACCH Enabled
Legacy RLT
RSACCH Enabled
Legacy RLT
RSACCH Enabled
Legacy RLT
RSACCH Disabled
Differentiated RLT
RSACCH Disabled
Differentiated RLT
RSACCH Disabled
Differentiated RLT
RSACCH Disabled
Differentiated RLT
RSACCH Enabled
Differentiated RLT
RSACCH Enabled
Differentiated RLT
RSACCH Enabled
Differentiated RLT
RSACCH Enabled
Differentiated RLT
OBSERVATIONS
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.
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 doesn’t 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 to recent on-air tests in Lab, with Nokia cooperation, Mobile N6720 according to
Nokia, is working properly, although this is still under discussions with ALU
Those variations cannot be confirmed as gains as the tested network is using very
slightly the most robust codecs
90.%
80.%
70.%
60.%
50.% % Frames dist
%
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 )
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
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
Erlangs=2116
CDR Radio= 0.77%
CDR HO= 0.31%
Erlangs=2035
Erlangs=2390
CDR Radio= 0.75%
CDR Radio= 0.67%
CDR HO= 0.27%
CDR HO= 0.25%
Back
126 | Repeated ACCH All Rights Reserved © Alcatel-Lucent 2009
Nokia phones Misbehavior with RSACCH feature
Not responding to SRO
Back
128 | Repeated ACCH All Rights Reserved © Alcatel-Lucent 2009
www.alcatel-lucent.com