alu seminar rx acch

7/22/2019 ALu seminar RX ACCH

1/129

B11 MR1 Ed1.x / Ed2.xSeminar of GSM Network EngineeringRepeated ACCH

Jorge S. Silva, Philip Fawzy, Robin Brassac

March, 2010


2/129

2 | Repeated ACCH All Rights Reserved Alcatel-Lucent 2009

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


3/129


1 Feature Overview


4/129


1.1 Feature OverviewIntroduction


5/129


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 ControlChannels) as those used for legacy codecs were re-used:

SACCH (Slow Associated Control Channel), which is used for non-urgentprocedures (mainly for the transmission of the radio measurement dataneeded 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.


6/129


Feature description

Repeated ACCH consists of two features:

Repeated Downlink FACCH (RDFACCH)

Repeated SACCH (RSACCH)

Required by several operators:

SFR, T-Mobile, Orange.

Feature Overview

Introduction


7/129


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 DownlinkFACCH

Support mandatory for Release 6 MS,

Some pre-release 6 MS may have the Repeated ACCHflag at 1, in thiscase they shall support completely the feature (RDFACCH and RSACCH).

Activated on a per-call basis.

Feature Overview

Introduction


8/129


1.2 Feature OverviewRepeated DL FACCH


9/129


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):

3GPP TS 44.006LAPDm LAPDm

Physical Layer Physical Layer

Physical connection

BTS MS


10/129



BTS side (LAPDm entity)

When RDFACCH is active, each LAPDm frame is repeated twice by BTSentity.

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.

Feature Overview

Repeated DL FACCH


11/129



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.OddEven

~40 ms

Half FACCH burst of the first transmission

Half FACCH burst of the repetition

Half TCH/FR burst

Half idle or SACCH burst

OddEven

~40 ms



Half TCH/FR burst

Half FACCH burst of another signalling message

Half FACCH burst of the repetition of another signalling message

1 radio TS

Top: first half (before the training sequence),

Bottom: second half (after the training

sequence).

1 radio

TCH

Feature Overview

Repeated DL FACCH


12/129



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.

OddEven

~40 ms



Half TCH/HR burst

Feature Overview

Repeated DL FACCH


13/129



MS side (Physical layer)

The MS shall, when receiving a downlink FACCH block, always attempt todecode 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


14/129


BTSPhysical LAPDm

OK

OK

Msg A

Msg A

OK

Msg B

Msg B

NOK

NOK

Msg C

Msg C

OK

NOK

OK

Msg D

Msg D

decoding

MS

Soft combining

Assumption: RDFACCHdynamically activated

Feature Overview

Repeated DL FACCH


15/129


BTSPhysical LAPDm

NOK

Msg E

Msg E

NOK

NOK

Msg F

Msg F

NOK

decoding

MS

Soft combining

Feature Overview

Repeated DL FACCH


16/129


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.

Feature Overview

Repeated DL FACCH


17/129


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

Codec

Mode 2 +

RDFACCH

CodecMode 3

Codec

Mode 4

Codec

Mode 3

Codec

Mode 2 +RDFACCH

CodecMode 1 +

RDFACCH

Codec

Mode 1 +

RDFACCH

AMR_FR

_THR

_3+AMR

_FR_

HYST

AMR_FR_TH

R_3

AMR_FR

_THR_

2+AMR_

FR_HYST

AMR_F

R_TH

R_2

AMR

_FR_TH

R_1+

AMR

_FR_HY

ST

AMR_FR

_THR

_1

RDFACCH active

RDFACCH inactive

AMR C/I

More robust

Better intrinsicvoice quality

Feature Overview

Repeated DL FACCH


18/129


1.3 Feature OverviewRepeated SACCH


19/129


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


20/129


Repeated DL SACCH operation principles 3GPP standard

MS side

The MS shall first attempt to decode any DL SACCH block received withoutcombining 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.

Feature Overview

Repeated DL SACCH 3GPP Standard


21/129


Repeated DL SACCH operation principles 3GPP standard

BSS side

The BSS may, based on the value of the last correctly received SRR fromthe 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 inorder to make room for the repetition.

Feature Overview

Repeated DL SACCH 3GPP Standard


22/129


Repeated UL SACCH operation principles 3GPP standard

BSS side

The BSS shall first attempt to decode any UL SACCH block received withoutcombining 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 onimplementation-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.

Feature Overview

Repeated UL SACCH 3GPP Standard


23/129


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


24/129



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

Feature Overview

Repeated DL SACCH ALU Implementation


25/129



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 andwell 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 isordered 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


26/129



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

Feature Overview

Repeated UL SACCH ALU Implementation


27/129


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

Feature Overview

Repeated SACCH Illustrations


28/129


Feature Overview

Repeated DL SACCH Illustrations

SRR count BFI count

NOK

#2, SRR = 0#2, SRO = 0

#1, SRR = 0#1, SRO = 0

#3, SRR = 1#3, SRO = 0

#4, SRR = 0#4, SRO = 0

#5, SRR = 1#5, SRO = 0

#6, SRR = 1#6, SRO = 0

#7, SRO = 0 #7, SRR = 0

#8, SRR = 1#8, SRO = 0

Call startBTS MS

#8 repeated, SRO = 0 #9, SRR = 1

#9, SRO = 0 #10, SRR = 1

OKOK0/1 0/1N/A

OK0/2 NOK0/2N/A

NOK0/3 OK1/3

Frame notdecoded! SRRvalue of last

correct frame istaken OK0/4 NOK1/4N/A

OK1/5 NOK1/5N/A

OK2/6 OK1/6N/A

OK2/7 1/7 NOKN/A

OK3/8 NOK1/8

RDSACCH

dynamicallyactivated N/A

OK4/9 1/9 NOKN/A

OK5/10 1/10 OKN/A

Result of first decodingattempt BS side Result of first decodingattempt MS side

Because last DLSACCH frame

not decoded

Count of SRR = 1 in lastRep_DL_SACCH_WS frames

Assumption:

Rep_DL_SACCH_WS = 10

Rep_DL_SACCH_Thres = 3

Count of bad frames in lastRep_UL_SACCH_WS frames

Assumption:

Rep_UL_SACCH_WS = 10Rep_UL_SACCH_Thres = 3

As UL Framewas not

decoded, soft

combining istried

Incrementedbecause SRR = 1

Incrementedbecause SRR = 1

NOK

According to spec, MSshall try soft combining

with previous Frame ifcurrent Frame is not

decoded

NOK

NOK

NOK

NOK

OK

Possibility tohave good

decoding due to

repetition ofmessage andsoft combining

Result after softcombining, if applicable


29/129


Feature Overview

Repeated UL SACCH Illustrations

NOK

#2, SRR = 0#2, SRO = 0

#1, SRR = 0#1, SRO = 0

#3, SRR = 1#3, SRO = 0

#4, SRR = 0#4, SRO = 0

#5, SRR = 0#5, SRO = 0

#6, SRR = 0#6, SRO = 0

#7, SRO = 1 #7, SRR = 0

#7 repeated, SRR = 0#8, SRO = 1

BTS MS

#9, SRO = 1 #8, SRR = 1

#10, SRO = 1 #8 repeated, SRR = 1

OKOK0/1 0/1N/A

OK0/2 NOK0/2N/A

NOK0/3 OK1/3

Frame notdecoded, SRRvalue of last

correct frame istaken

OK0/4 OK1/4N/A

NOK0/5 OK2/5

NOK0/6 OK3/6NOK

NOK0/7 4/7 OKNOK

NOK0/8 NOK5/8

RUSACCHdynamicallyactivated

OK

NOK0/9 6/9 OKNOK

NOK1/10 7/10 OKOK

SRR = 1 becauseUL SACCHframe is

repeated

Because last DLSACCH frame was

not decodedNOK

SRR count BFI count

As UL Framewas not

decoded, soft

combining istried

SRO = 1,requesting the

UL framesrepetition

NOK

NOK


decoding due to



decoding due to



30/129


1.4 Feature OverviewLimitations


31/129


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.


32/129


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


33/129


2 Activation Strategy


34/129


2.1 Activation StrategyPre-requisites

A i i S


35/129


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.


36/129


2.2 Activation StrategyParameter Settings

Activation Strategy


37/129


{0,1,...,8}3/

3

{0, 1}2/0

{0, 1, 2}1/0

Range/

Default

value

3

0

2

Recommended

ValueParameter Name Definition Instance

EN_REP_DL_FACCHEnables repeated downlink FACCH for

AMR callsCell

REP_DL_FACCH_LEGACY_SUPPORT

Legacy support for repeated downlinkFACCH for AMR calls

Remarks:

1. This parameter is relevant only ifrepeated downlink FACCH is enabled

(EN_REP_DL_FACCH parameter)

2. This parameter concerns only theLAPDm command frames.

Cell

REP_DL_FACCH_THRES_AMR_FR

Repeated DL FACCH activationthreshold for AMR FR. Dynamicactivation is done as long as codec

mode request CMR threshold.

Cell

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 allAMR 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

Activation Strategy

Parameter settings

Activation Strategy


38/129


{0,...,127}/10

{0,1}/0

{0, 1, 2}2/1

{0,1,...,5}1/3

Range/ Default

valueParameter Name Definition

Instan

ce

Recommended

value

REP_DL_FACCH_THRES_AMR_HR

Repeated DL FACCH activationthreshold for AMR HR. Dynamic

activation is done as long as codecmode request CMR threshold.

Cell 3

REP_DL_FACCH_THRES_AMR_WB

Repeated DL FACCH activationthreshold for AMR WB. Dynamicactivation is done as long as codecmode request CMR threshold.

Cell NA

EN_REP_SACCH

Enables repeated SACCH for SAPI 0frames in case of AMR calls (for mobilestation having indicated the support ofthe feature).

Cell 1

RADIOLINK_REP_DL_SACCH

Repeated DL SACCH activationthreshold for UL RLT (Radio LinkTimer) counter. Dynamic activation istriggered in the BTS when the UL RLTcounter is inferior or equal to thatthreshold.

Cell10

For RLT of 24

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

Activation Strategy

Parameter settings

Activation Strategy


39/129


1 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.

Parameter Name Definition InstanceRange/

Default value

Recommended

values

L_RXQUAL_UL_P_AMR_RXACCH1

Lower uplink quality threshold for

power control for AMR calls withactivated Repeated DL FACCH andRepeated SACCH.

Cell {0,...,7}/3

Equal to

L_RXQUAL_UL_P

or slightly higher

L_RXQUAL_DL_P_AMR_RXACCH1

Lower downlink quality thresholdfor power control for AMR callswith activated Repeated DL FACCHand Repeated SACCH.

Cell {0,...,7}/3

Equal to

L_RXQUAL_UL_P

or slightly higher

New parameters

Activation Strategy

Parameter settings

Activation Strategy


40/129


Modified parameters

Parameter Name Definition changes InstanceRange/

Default value

Recommended

value

RADIOLINK_TIMEOUT_BS_AMR

Counter threshold to detect a radio link

failure on the uplink path for calls using anAMR codec and for which Repeated SACCHand/or Repeated DL FACCH are notactivated.

Cell {1,...,255}/18 32

RADIOLINK_TIMEOUT_BS1

Updated the definition: this timer can alsobe used for AMR calls (NB or WB) for whichRepeated SACCH and Repeated DL FACCHare activated

Cell {1,...,255}/18 NA

RADIOLINK_TIMEOUT_AMR1Initial value of MS counter for radio linksupervision, when an AMR codec is usedand for which call Repeated SACCH and/orRepeated DL FACCH are not activated.

Cell {4,...,64}/16 32

RADIOLINK_TIMEOUT1 (BSC)This also applies toRADIOLINK_TIMEOUT1 (MFS)

Updated the definition: this timer can alsobe used for AMR calls (NB or WB) for whichRepeated SACCH and Repeated DL FACCHare activated

Cell {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)

Activation Strategy

Parameter settings


41/129


3 Feature Assessment


42/129


3.1 Feature AssessmentImpact of other features on performance

Feature Assessment


43/129


RSACCH and RadioLink Supervision

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

Feature Assessment

Impact of other features on performance

Feature Overview


44/129


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 andRADIOLINK_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).

Repeated SACCH & Radio Link Supervision

R6 MS will be using RxACCH for AMR calls

Pre-Rel6 MS will be using DRLT for AMR calls

Activating both features will improve the performance of all AMR calls

R6 MS will be using RxACCH for AMR calls

Pre-Rel6 MS will be using DRLT for AMR calls

Activating both features will improve the performance of all AMR calls


45/129


3.2 Feature AssessmentNew Counter and Indicators

Feature Assessment


46/129


New Counters

Telecom Counters

Counterrefname LongName Definition

Measuredobject Domain Type

MC990 NB_MS_REPEATED_ACCH_Capable Number of calls for which the mobile stationssupporting the repeated ACCH capability TRX Quality ofservice 110

MC991 NB_Calls_RFACCH_ActivatedNumber of calls for which repeated DL FACCH is

activated by the BSCTRX

Quality of

service110

MC992 NB_Calls_RSACCH_ActivatedNumber of calls for which repeated SACCH (DL

or UL) is activated by the BSC

TRXQuality of

service

110

MC993 NB_AMR_TCH_DROP_RLF_TRX

Number of AMR TCH (NB or WB AMR) for which

Repeated SACCH is not activated, dropped inTCH established phase due to radio link failure

(radio link timeout or Lapdm timer expiry), per

TRX.

TRXQuality of

service

110

MC994NB_AMR_TCH_DROP_RLF_TRX_

RSACCH

Number of AMR TCH (NB or WB AMR) for whichRepeated 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.

TRX

Quality of

service110

Feature Assessment


47/129


New Counters



MC995NB_AMR_TCH_DROP_OUT_HO_

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.

TRXQuality of

service110

MC996NB_AMR_TCH_DROP_OUT_HO_

TRX_RFACCH

Number of TCH using AMR codecs (NB or WB)

and with Repeated FACCH activated, droppedduring the execution of any TCH outgoing

handover, per TRX. This counter takes intoaccount handovers from TCH in traffic or in

signaling mode.

TRXQuality of

service110

Telecom Counters

Feature Assessment


48/129


New Counters (type 10 & 15)



S09 NB_FRAMES_NOT_REPEATED

Indicates the number of SAPI 0 frames that were

not repeated.This counter corresponds to the CNT_I_TX field

of the 48.058 PHYSICAL CONTEXT CONFIRM

message.

(SDCCH

observations)QoS 101

S16 NB_FRAMES_REPEATED


repeated at least once.This counter corresponds to the CNT_I_RETX

field of the 48.058 PHYSICAL CONTEXT CONFIRMmessage.

(SDCCH


T08 NB_FRAMES_NOT_REPEATED


not repeated.

This counter corresponds to the CNT_I_TX fieldof the 48.058 PHYSICAL CONTEXT CONFIRM

message.

(TCH


T15 NB_FRAMES_REPEATED

Indicates the number of SAPI 0 frames that wererepeated at least once.

This counter corresponds to the CNT_I_RETX

field of the 48.058 PHYSICAL CONTEXT CONFIRM

message.

(TCH


1Type 10 is SDCCH observation; type 15 is TCH observation

Telecom Counters

Feature Assessment


49/129


BTS

Cell

MS

TC MSC

Abis

AterMUX-CS

A

BSC

CHANNEL

ACTIVATION or MODE

MODIFY messages

CONNECTION FAILURE

INDICATION

or

ERROR INDICATION messages

MC990 & MC991 & MC992

MC993 & MC994

Number of calls for whichthe mobile stationssupporting the repeatedACCH capability

Number of calls for whichrepeated DL FACCH isallowed by the BSC

Number of calls for whichrepeated SACCH (DL or UL) isallowed by the BSC

Number of AMR TCH (NB or

WB AMR) for whichRepeated SACCH is not

activated, dropped in TCHestablished phase due to

radio link failure (radio linktimeout or Lapdm timer

expiry), per TRX.

Number of AMR TCH (NB or WBAMR) for which Repeated SACCH is

activated, dropped in TCHestablished phase due to radio

link failure (radio link timeout orLapdm timer expiry), per TRX.This counter takes into account

TCH in traffic.

Number of TCH using AMR codecs (NB or WB) but withRepeated FACCH not activated, dropped during theexecution of any TCH outgoing handover, per TRX.

This counter takes into account handovers from TCHin traffic.

MC995 & MC996

Number of TCH using AMR codecs (NBor WB) and with Repeated FACCH

activated, dropped during theexecution of any TCH outgoinghandover, per TRX. This counter

takes into account handovers fromTCH in traffic or in signaling mode.

Telecom Counters

Feature Assessment


50/129


Specific new basic indicators

Telecom Indicators

NPOindicatorrefname LongName NPO

FormulaNPO B11 Description

GSDRACN MS_REPEATED_ACCH_Capable MC990

Counts the number of calls of mobile stations

supporting the repeated ACCH capability. Ittakes into account both Normal assignment

and incoming HO and DR.

GSDRFACN Call_RFACCH_BSC Activated MC991

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 takesinto account both Normal assignment and

incoming HO and DR.

GSDRSACN Call_RSACCH_BSC_Activated MC992

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 takesinto account both Normal assignment and

incoming HO and DR.

Feature Assessment


51/129



Counts the number of AMR TCH (NB or WB

AMR) for which Repeated SACCH is activated

by the BSC, dropped in TCH established phasedue to radio link failure (radio link timeout or

Lapdm timer expiry), per TRX. This counter

takes into account TCH in traffic.MC994AMR_TCH_DROP_RSACCH_ActivatedGTCRSACN

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. Thiscounter takes into account handovers from

TCH in traffic.MC995

AMR_TCH_DROP_OUT_HO_No_RFACCH

_ActivatedGTCNRFACN



GTCNRSACN AMR_TCH_DROP_No_RSACCH_Activated MC993

Counts the number of AMR TCH (NB or WB

AMR) for which Repeated SACCH is notactivated by the BSC, dropped in TCH

established phase due to radio link failure

(radio link timeout or Lapdm timer expiry),

per TRX.

Telecom Indicators

Feature Assessment

T l I di


52/129



Counts the number of TCH using AMR codecs

(NB or WB) and with Repeated FACCHactivated, 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.MC996

AMR_TCH_DROP_OUT_HO_RFACCH_Act

ivatedGTCRFACN



Telecom Indicators

Feature Assessment

T l I di t


53/129


Penetration rate for the mobile stations,already in call state, with RDFACCH BSC

activated

MC991/(MC703+MC15a+

MC15b)

RDFACCH_BSC_Activated_MS_Penet

ration_RateGSDRFACPR

Penetration rate for the mobile stations,

already in call state, with RSACCH BSC

activated.

MC992/

(MC703+MC15a+

MC15b)

RSACCH_BSC_Activated_MS_Penetra

tion_RateGSDRSACPR

Represents the ratio of AMR calls with R6

Mobile stations, that are capable and allowedby the BSC of supporting both RSACCH and

RDFACCH with respect to the whole population

of considered calls that are at least capable

and allowed by the BSC to support RDFACCHMC992 / MC991

RxACCH_R6_MS_capable_Calls_Rati

oGSDRACR6MSCO

Represents the ratio of AMR calls with Pre-R6

Mobile stations, that are capable and allowed

by the BSC of supporting RDFACCH with respectto the whole population of considered calls

that are at least capable and allowed by the

BSC to support RDFACCH

(MC991-MC992)

/ MC991

RDFACCH_Active_PreR6_MS_capabl

e_Calls_RatioGSDRFAPR6MSCO



GSDRACCPR RxACCH_MS_Penetration_Rate

MC990 /(MC703

+ MC15a +

MC15b)

Penetration rate for the mobile stations,

already in call state, supporting the repeated

ACCH capability

Specific new computed indicators

Telecom Indicators

Feature Assessment

T l I di t


54/129


Ratio of AMR with RDFACCH not allowed HOdrops compared to total HO drops

(MC995) / ( MC621+ MC995 + MC996)AMR_NoRDFACCH_Call_drop_HO_ratioGSDNRFACCDHO

Ratio of AMR with RDFACCH allowed HO

drops compared to total HO drops

(MC996) / ( MC621

+ MC995 + MC996)AMR_RDFACCH_Call_drop_HO_ratioGSDRFACCDHO

Ratio of Non AMR radio drops compared to

total radio drops

MC736 / (MC736 +

MC993 + MC994)NonAMR_Call_drop_radio_ratioGQSNACDRO

Ratio of Non AMR HO drops compared to

total HO drops

MC621 / (MC621 +

MC995 + MC996)NonAMR_Call_drop_HO_ratioGQSNACDHO

Ratio of AMR without RSACCH allowed callsradio drops compared to total radio drops

(MC993) / (MC736+ MC993 + MC994)AMR_NoRSACCH_Call_drop_radio_ratioGSDNRSACCDRO

Ratio of AMR with RSACCH allowed calls

radio drops compared to total radio drops

(MC994) / (MC736

+ MC993 + MC994)AMR_RSACCH_Call_drop_radio_ratioGSDRSACCDRO




Telecom Indicators

Feature Assessment

Telecom Indicators


55/129


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 TCHassignment to TCH phase).

MC736 / (MC702a +MC702b + MC702c)NonAMR_NA_Call_radio_fail_rateGQSNANARFR

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 assignmentto TCH phase).

(MC995+MC996) /

(MC704a + MC704b +MC931)AMR_NA_Call_HO_fail_rateGQSANAHOFR

Rate of non AMR calls failed due to HOwith respect to non AMR Normal

assignment requests (including requests

that might fail during the period of TCH

assignment to TCH phase).

MC621 / (MC702a +

MC702b + MC702c)NonAMR_NA_Call_HO_fail_rateGQSNANAHOFR

Rate of AMR calls failed due to Radio

with respect to AMR Normal assignmentrequests (including requests that might

fail during the period of TCH assignment

to TCH phase).

(MC993+MC994) /

(MC704a + MC704b +

MC931AMR_NA_Call_radio_fail_rateGQSANARFR




Telecom Indicators

Feature Assessment

Telecom Indicators


56/129


Rate of AMR with RDFACCH allowed calls

failed due to HO with respect to BSCactivated RDFACCH AMR Normal

assignment, incoming HO and DR requests

(including requests that might fail duringthe period of TCH assignment to TCH

phase).MC996 / MC991AMR_RDFACCH_Call_HO_fail_rateGSDRACCAFDR

Rate of AMR with RSACCH allowed calls

failed due to Radio with respect to allowedRSACCH AMR Normal assignment, incoming

HO and DR requests (including requests that

might fail during the period of TCH

assignment to TCH phase).MC994 / MC992AMR_RSACCH_Call_radio_fail_rateGSDRACCASDR




Telecom Indicators

Feature Assessment

Telecom Indicators


57/129


The formula only takes into account SV3. Its update to

considered also SV5. (mc701d+mc932) / mc140aRTCH_assign_AMR_penetration_rateGTMMSAMR

NPOindicatorrefname LongName NPO Modification

Specific computed indicators modified

Old counters MC736 or MC621 were modified dueto introduction of new drop counters, MC993,

MC994, MC995 and MC996.

This caused formula modifications on several old

indicators like Call_drop_rate orRTCH_drop_HO_rate. For details on extension of

indicators affected see slides of PM counters

Telecom Indicators

Feature Assessment

Telecom Indicators


58/129


Report dedicated to the feature Repeated ACCH.

Please refer to feature test plan for other NPO reports that can be interesting to

monitor the feature behavior

Split of call drop HO for AMR and NonAMR callsAlc_drop_HO_AMR_and_NonAMR

Split of call drop radio for AMR and NonAMR

callsAlc_drop_radio_AMR_and_NonAMR

AMR HO drop with and without FACCH.Alc_AMR_and_SACCH

Calls with RFACCH or RSACCH allowed.Alc_ACCH_allowed

AMR radio drop with and without SACCH.Alc_AMR_and_FACCH

NPO report name Views in the report Description of the views

Alc_Mono_Repeated_ACCH

Alc_ACCH_MS Mobiles with RACCH capable and penetrationrate.

Telecom Indicators


59/129


3.3 Feature AssessmentMonitoring Method

Feature Assessment

Monitoring Method


60/129


Planning Overview

Test Category Test Type Trial Period

Statistical Non Regression Two Weeks

Optimization Four Weeks

Unitary SACCH Five Days

FACCH Five Days

One RNE resource is required for generic Statistical and Unitary Tests

Monitoring Method

Feature Assessment

Monitoring Method


61/129


g

0W945.11AMR_START_MODE_FR

{12.2 Kbps, 10.2 Kbps,

7.4 Kbps, 4.75 Kbps}W945.1{12.2 Kbps}AMR_FR_SUBSET

26W945.122AMR_HR_THR3



22W945.116AMR_FR_THR3

Value aftermodification

Date ofmodification

InitialsettingParameter Name

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 anylogical parameter change different than those requested by the tests

If AMR is not activated or in mono codec configuration, AMR must be adjustedto multi codec configuration as per the following TMO AMR parameters

adjustment example:


62/129


Statistical Tests

Feature Assessment

Non Regression Tests


63/129


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

Feature Assessment

Optimization Tests


64/129


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

For more information about the cell zone division criterion please click here

TMO Essen Pilot Example

Feature Assessment

Optimization Tests


65/129



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)

Feature Assessment

Optimization Tests


66/129



3

All BSC75

3

All Pilot

Feature is deactivated, AMR is in

multi-codec configuration

REP_DL_FACCH_THRE

S_AMR_YY

Cell Zone A

10

All BSC

185

10

All Pilot

RADIOLINK_REP_DL_S

ACCH

Cell Zone B

1.9 or 3.4 **

All BSC

41.1

3

All Pilot

L_RXQUAL_XX_P_AMR

_RXACCH

Cell Zone C

Configuration RACCH Final *RACCH Tuning2RACCH Tuning1RACCH DefaultReference

* More information about choosing optimized parameter setting available in optimization test section

** If L_RXQUAL_XX_P=2.9 L_RXQUAL_XX_P_AMR_RXACCH = 3.4

If L_RXQUAL_XX_P=1.1 L_RXQUAL_XX_P_AMR_RXACCH = 1.9

Feature Assessment

Optimization Tests


67/129



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 linkcounter

3232Cell Zone E

2424Cell Zone D

RADIOLINK_TIMEOUT_AMRRADIOLINK_TIMEOUT_BS_A

MRCell Zone

Parameter

TMO EssenPilot

Example

Feature Assessment

Optimization Tests


68/129



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 theobserved improvements


69/129


Unitary Tests

Feature Assessment

SACCH Unitary Tests


70/129


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

B: Radio link failurewithout RxACCH

C: Radio link failure with

RxACCH

A: Start measurement(all cases)

Drive test routeCell coveragewith RxACCH

Cell coverage

without RxACCH

BTS

Feature Assessment

FACCH Unitary Tests


71/129


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 coveragewith RxACCH

Cell coverage

without RxACCH


72/129


3.4 Feature AssessmentFOA Test Results


73/129


Statistical Tests Results

Statistical Test Results

RxACCH Capable MS Penetration

B11 Indicators Only


74/129


As the RxACCH capable MS penetration is around 10%, it is not expected to see anoticeable 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 tuningphase due to disabling the feature for legacy MS due to observing unexpected behavior with thefeature

Penetration Weekly

0.00%

20.00%

40.00%

60.00%

80.00%

100.00%

Time

%

RxACCH_MS_Penetration_Rate 0.00% 9.98% 10.36% 10.93% 10.97% 10.38%

RDFACCH_BSC_Activated_MS_Penetration_

Rate

0.00% 0.00% 85.71% 85.98% 10.97% 10.38%

RSACCH_BSC_Activated_MS_Penetration_R

ate

0.00% 0.00% 10.36% 10.83% 10.97% 10.38%

Mono Codec Multi Codec RACCH Default RACCH

Tuning1

RACCH

Tuning2 RACCH Final


Radio Measurement Statistics


75/129


AMR FR DL Codec Distribution

0%

10%

20%

30%

40%

50%

60%

70%

80%

90%

100%

1.20%

1.25%

1.30%

1.35%

1.40%

1.45%

1.50%

1.55%

DL 4.75 FR Frame Distribution 0.12% 1.12% 1.10% 1.04% 1.11% 1.06%




RMS_Call_noisy_DL_rate 1.33% 1.46% 1.46% 1.52% 1.47% 1.44%

Mono Codec Multi Codec RACCH Default RACCH Tuning1 RACCH Tuning2 RACCH Final

AMR FR UL Codec Distribution

00.00%

20.00%

40.00%

60.00%

80.00%

100.00%

120.00%

0.00%

0.50%

1.00%1.50%

2.00%

2.50%

3.00%

3.50%

4.00%

UL 4.75 FR Frame Distribution 0.00% 0.52% 0.49% 0.49% 0.50% 0.50%




RMS_Call_noisy_UL_rate 2.46% 3.17% 3.17% 3.27% 3.38% 3.34%

Mono Codec Mu lt i Codec RACCH Default RACCH Tuning1 RACCH Tuning2 RACCH Final

AMR 12.2 kbps Codec isdominating codec, morerobust codec are not oftenused

Feature impact isexpected to be minimal

as calls are in good radioconditions and using AMR12.2 kbps most of thetime


Non Regression Test


76/129


Non Regression Statistics

0.00%

0.50%

1.00%

1.50%

2.00%

Observation Week

%

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%

Mono Codec Multi Codec RACCH Default

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 ofthe time (good radio conditions)

Feature brought No Regression on the Pilot

Optimization Test Results

Cell Zone A Optimization of REP_DL_FACCH_THRES_AMR_XR


77/129


HO Statistics

0.00%

0.20%

0.40%

0.60%

0.80%

1.00%

1.20%

1.40%

1.60%

1.80%

2.00%

Time

HO_Inc_BSC_fail_rate 1.55% 1.60% 1.39% 1.40% 1.55%

HO_Inc_BSC_unsuccess_rate 1.67% 1.76% 1.54% 1.55% 1.69%

HO_Out_BSC_drop_rate 0.17% 0.18% 0.15% 0.14% 0.18%

HO_Out_BSC_prep_fail_rate 0.16% 0.16% 0.16% 0.15% 0.16%

HO_Out_BSC_ROC_rate 1.38% 1.40% 1.26% 1.24% 1.39%

Mono Codec Multi Codec RACCH Default RACCH Tuning1 RACCH Tuning2

HO Call Drops

0.00%

0.05%

0.10%

0.15%

0.20%

0.25%

0.30%

0.35%

0.40%

0.45%

Observation Week

NonAMR_NA_Call_HO_fail_rate 0 0.34% 0.26% 0.23% 0.27%

AMR_NA_Call_HO_fail_rate 0 0.38% 0.22% 0.22% 0.26%

AMR_RDFACCH_Call_HO_fail_rate 0 0.00% 0.08% 0.08% 0.08%


AMR HO Failurewith RDFACCHsupport as wellgeneric HO failures

did not enhancesignificantly whilemoving theparameter from 3to 5 or 7

Increasing theprobability atwhich theRDFACCH isactivated (using 5or 7) didnt showsignificantimpact.

B11

Indicators

Only

REP_DL_FACCH_THRES_AMR_FR= 3 5 7



Cell Zone A Optimization of REP_DL_FACCH_THRES_AMR_XR

Legacy SupportDisabled


78/129


Transmission problems existence during tuning phase increased call drop rates

Observation of the feature indicators showed that some MSs legacy as current assumption- might not bewell impacted during enabling DL FACCH all the time. In graph, it can be seen that call drop is lessimpacted during second tuning phase due to legacy support deactivation

It is recommended to use the REP_DL_FACCH_THRES_AMR_FR= 3 (or the second robust codecequivalent value in the AMR subset) as a good compromise for activating DL FACCH

Moreover as per the current assumptions REP_DL_FACCH_LEGACY_SUPPORT must be disabled to avoidlegacy MSs misbehavior with RDFACCH

Radio Call Drop Rates

0.00%

0.50%

1.00%

1.50%

2.00%

2.50%

3.00%

Observation Week

%

Call_drop_rate 0.90% 0.92% 0.91% 1.29% 1.02%

NonAMR_NA_Call_radio_fail_rate 0.00% 2.01% 2.27% 2.18% 2.77%

AMR_NA_Call_radio_fail_rate 0.00% 0.60% 0.51% 1.04% 0.52%

AMR_RSACCH_Call_radio_fail_rate 0 0.00% 0.17% 0.14% 0.15%



B11

Indica

torsOnly


Cell Zone B Optimization of RADIOLINK_REP_DL_SACCH



79/129


It is clear that increasing RADIOLINK_REP_DL_SACCH improves the Radio CDR, however the gain

from increasing the parameter to 18 cannot be quantified or compared to RxACCH default activationperiod due to the transmission problem and sites failure during tuning phases

It is seen that the value 5 tuning 1 degrades AMR radio drops when compared to the value 18tuning


0.00%

0.50%

1.00%

1.50%

2.00%

2.50%

3.00%

Observation Week

%




Call_drop_rate 0.86% 0.95% 0.94% 1.08% 1.03%



B11

Ind

icatorsOnly

It is recommended to use the values 10 for a good compromise for activating RSACCH and

unnecessary measurement reports repetition and delayFor RLT of 24, the RADIOLINK_REP_DL_SACCH value 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


Cell Zone C Optimization of L_RXQUAL_XX_P_AMR_RXACCH

HO Call Drops


80/129


0.00%

0.05%

0.10%

0.15%

0.20%

0.25%

Observation Week

%

NonAMR_NA_Call_HO_fail_rate 0 0.18% 0.23% 0.16% 0.18%

AMR_NA_Call_HO_fail_rate 0 0.14% 0.12% 0.10% 0.16%

AMR_RDFACCH_Call_HO_fail_rate 0 0.00% 0.05% 0.04% 0.03%

Mono Codec Multi Codec RACCH Default RACCH Tuning1 RACCH Tuning2Changing the

L_RXQUAL_XX_P_AMR_RXACCH from 3 to 1.1kept the same HOdrops, Yet this is not

totally true as uponusing 1.1 transmissionfailures occurred.

HO Statistics

0.00%

2.00%

4.00%

6.00%

8.00%

10.00%

12.00%

Observation Week

%

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%

Mono Codec Mult i Codec RACCH Default RACCH Tuning1 RACCH Tuning2

L_RXQUAL_XX_P_AMR_RXACCH= 3 1.1 4



Cell Zone C Optimization of L_RXQUAL_XX_P_AMR_RXACCH


81/129


During changes ofL_RXQUAL_XX_P_AMR_RXACCH from 3 to 1.1 is observed enhances of the radiodrops, but no improves on the radio drops for AMR with RSACCH support

During changes ofL_RXQUAL_XX_P_AMR_RXACCH from 3 to 4 degrades is observed that radio dropsslightly increase, specifically the radio drops for AMR with RSACCH support

The impact of PC parameters tuning cannot be uncorrelated with the transmission problem occurred atthe same time


0.00%

0.50%

1.00%

1.50%

2.00%

Observation Week

%




Call_drop_rate 0.68% 0.66% 0.56% 0.52% 0.64%



B11

IndicatorsOnly

According to trial the appropriate RxACCH PC parameter to be used is the same as legacy PC parameter.Apparently theres some margin to increasing RxACCH PC parameter more than legacy parameter without

observe impact.

Combining ALU recommendation L_RXQUAL_xL_P_AMR_RXACCH >=L_RXQUAL_xL_P and TMOrecommendation, we will use the following rules:



Optimization Test Results Final optimized values


RxACCH + LRLT --> Radio Call Drop RatesCell Zone D


82/129


AMR multi codec introductionbrought no impact onLRLT+RxACCH cell zone.

However for DRLT+RxACCH slightCDR degradation is noticed

For LRLT cell zone a slight CDRgain is seen (enhancement of6.5% with respect to multi codecreference)

For DLRLT cell zone CDR came toinitial mono codec value,recovering the slight degradationupon using multi codecs (CDRenhancement of 10.3% withrespect to multi codecreference)

0.00%

0.50%

1.00%

1.50%

2.00%

2.50%

Observation Week

%

NonAMR_NA_Call_radio_fail_rate 0.00% 1.99% 2.14% 1.78%

AMR_NA_Call_rad io_fail_rate 0.00% 0.62% 0.49% 0.51%

AMR_RSACCH_Call_ radio_fai l_rate 0 0.00% 0.16% 0.20%

Call_drop_rate 0.92% 0.91% 0.87% 0.85%

Mono Codec Multi Codec RACCH Default RACCH Final

DRLT + RxACCH --> Radio Call Drop Rates

0.00%

0.50%

1.00%

1.50%

2.00%

2.50%

Observation Week

%

NonAMR_NA_Call_radio_fail_rate 0.00% 2.32% 2.11% 1.68%

AMR_NA_Call_radio_fail_ rate 0.00% 0.72% 0.55% 0.48%

AMR_RSACCH_Call_radio_fail_rate 0 0.00% 0.16% 0.19%

Call_drop_rate 0.78% 0.87% 0.86% 0.78%


B11

IndicatorsO

nly

B11

Indicators

Only

Cell Zone E

Optimization Test Results Final optimized values

HO Call Drop Rates

LRLT+RxACCH --> HO Call Drop Rates

B11 Indicators Only

Cell Zone D


83/129


Is observed a slight improvementfor the AMR HO fail rates withfeature introduction on bothareas

RxACCH capable MS HO drops arestable

RDFACCH capable MS HO dropsslightly enhanced from 0.06% to0.05% for LRLT cell zone andfrom 0.08% to 0.05% for DRLT

0.00%

0.05%

0.10%

0.15%

0.20%

0.25%

0.30%

0.35%

0.40%

Observation Week

%

NonAMR_NA_Call_HO_fail_rate 0 0.34% 0.27% 0.28%

AMR_NA_Call_HO_fail_rate 0 0.34% 0.21% 0.23%

AMR_RDFACCH_Cal l_HO_fail_ rate 0 0.00% 0.08% 0.05%


DRLT+RxACCH --> HO Call Drop Rates

0.00%

0.05%

0.10%

0.15%

0.20%

0.25%

0.30%

Observation Wee k

%

NonAMR_NA_Call_HO_fail_rate 0 0.19% 0.23% 0.24%

AMR_NA_Cal l_H O_fail_rate 0 0.26% 0.16% 0.20%

AMR_RDFACCH_ Cal l_HO_ fail_rate 0 0.00% 0.06% 0.05%


Cell Zone E


84/129


Unitary Tests Results

INTRODUCTION

RSACCH Voice Quality Measurements


85/129


Objective: Investigate whats the Voice Quality on the edge of a cell borderand 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

MEASUREMENT CONFIGURATION

VQ and Unitary RSACCH Measurements


86/129


Equipment:

MSFix 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

MEASUREMENT CONFIGURATION


M bil E i fi i


87/129


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

USB cable (AT commands, traces)

Audio cable

Nemo PC

MS#1

MS#2

BSC

MSC TC

Opera ClientBS

GPS

Opera Server

Fix line

GEOGRAPHICAL TESTS LOCALIZATION


C ll Ob h 18 3 (CI 30268 BCCH 23) L RLT


88/129


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 representationfor the cell

measured in LegacyRLT area Path

distance 2.4km

Path representationfor the cell

measured in LegacyRLT area Path

distance 2.4km

GEOGRAPHICAL TESTS LOCALIZATION


C ll E C t 9 3 (CI 32571 BCCH 98) Diff ti t d RLT


89/129


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 representationfor the cellmeasured in

Differentiated RLTarea Path distance

1.3km

Path representationfor the cellmeasured in

Differentiated RLTarea Path distance

1.3km

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


90/129


It was realized a set of tests in 2 different cells In each cell was donemeasurements 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 goodradio 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

TIME EVOLUTION GRAPHS

Voice Quality Measurements Results VQ and Unitary RSACCH Measurements

RSACCH Disabled (DL Legacy RLT) VQ samples are recorded in Opera Client


91/129


RSACCH Disabled (DL, Legacy RLT) VQ samples are recorded in Opera Client

Time Evolution Graph - VQ1, DL RSACCH OFF, Legacy RLT

-2

-1

0

1

2

3

4

5

6

7

9:47

:58.93

2

9:48

:08.25

6

9:48

:17.57

8

9:48

:26.90

4

9:48

:36.22

4

9:48

:45.55

0

9:48

:54.87

4

9:49

:04.198

9:49

:13.52

0

9:49

:22.81

0

9:49

:32.

168

9:49

:41.492

9:49

:50.81

6

9:50

:00.

138

9:50

:09.

464

9:50

:18.78

8

9:50

:28.

110

9:50

:37.

430

9:50

:46.76

0

9:50

:55.98

2

9:51

:05.

404

9:51

:14.72

6

-120

-100

-80

-60

-40

-20

0

MOS

RxQ avg

RxLev avg


0

1

2

3

4

5

6

7

10:00:30.2

06

10:00:39.5

30

10:00:

48.852

10:00:58.1

78

10:01:07.5

00

10:01:16.8

24

10:01:26.1

44

10:01:35.4

70

10:01:44.7

92

10:01:54.1

12

10:02:03.4

42

10:02:

12.766

10:02:22.0

90

10:02:31.4

12

10:02:

40.738

10:02:50.0

48

10:02:59.3

78

10:03:08.7

02

-120

-100

-80

-60

-40

-20

0

MOS

RxQ avg

RxLev avg


-2

-1

0

1

2

3

4

5

6

7

10:12:31

.384

10:12:

40.710

10:12:50

.032

10:12:59

.356

10:13:08

.680

10:13:

18.004

10:13:27

.328

10:13:36

.652

10:13:

45.972

10:13:55

.300

10:14:04

.620

10:14:13

.946

10:14:23

.270

10:14:32

.594

10:14:41

.912

10:14:51

.232

10:15:00

.562

10:15:

19.104

-120

-100

-80

-60

-40

-20

0

MOS

RxQ avgRxLev avg


0

1

2

3

4

5

6

7

10:26:59

.396

10:27:08

.720

10:27:

18.046

10:27:27

.368

10:27:36

.692

10:27:

46.016

10:27:55

.340

10:28:04

.662

10:28:

13.988

10:28:23

.312

10:28:32

.634

10:28:

41.958

10:28:51

.282

10:29:00

.606

10:29:09

.926

10:29:

19.252

10:29:28

.574

10:29:37

.898

10:29:

47.216

-120

-100

-80

-60

-40

-20

0

MOS

RxQ avg

RxLev avg

Consistent results for the 4passages:

MOS decrease with DLRxQual decrease in the edgeof the tested cell



RSACCH Enabled (DL Legacy RLT) VQ samples are recorded in Opera Client


92/129


RSACCH Enabled (DL, Legacy RLT) VQ samples are recorded in Opera Client

Time Evolution Graph - VQ1, DL RSACCH ON, Legacy RLT

0

1

2

3

4

5

6

7

21:18:2

6.64

2

21:18:3

5.96

6

21:18:4

5.29

0

21:18:5

4.61

4

21:19:0

3.93

4

21:19:1

3.26

0

21:19:2

2.58

4

21:19:3

1.90

6

21:19:4

1.23

2

21:19:5

0.55

6

21:19:5

9.87

8

21:20:0

9.20

0

21:20:1

8.52

4

21:20:2

7.85

0

21:20:3

7.172

21:20:4

6.490

21:20:5

5.82

0

21:21:0

5.14

4

21:21:1

4.466

21:21:2

3.79

2

21:21:3

3.110

21:21:4

2.436

-120

-100

-80

-60

-40

-20

0

MOS

RxQ avg

RxLev avg


0

1

2

3

4

5

6

7

21:37:

14.064

21:37:

23.390

21:37:

32.716

21:37:

42.040

21:37:

51.362

21:38:

00.682

21:38:

10.008

21:38:

19.334

21:38:

28.656

21:38:

37.978

21:38:

47.302

21:38:

56.628

21:39:

05.950

21:39:

15.276

21:39:

24.600

21:39:

33.922

21:39:

43.246

21:39:

52.570

21:40:

01.894

21:40:

11.144

21:40:

20.540

-120

-100

-80

-60

-40

-20

0

MOS

RxQ avg

RxLev avg


-2

-1

0

1

2

3

4

5

6

7

21:48:52

.058

21:49:01

.382

21:49:

10.702

21:49:20

.030

21:49:29

.352

21:49:38

.678

21:49:

47.100

21:49:57

.324

21:50:06

.648

21:50:

15.972

21:50:25

.296

21:50:34

.618

21:50:

43.942

21:50:53

.266

21:51:02

.590

21:51:11

.914

21:51:21

.238

21:51:30

.560

21:51:39

.884

21:51:49

.206

21:51:58

.520

21:52:07

.824

21:52:

17.178

21:52:26

.342

-120

-100

-80

-60

-40

-20

0

MOS

RxQ avg

RxLev avg


-2

-1

0

1

2

3

4

5

6

7

22:01:48

.182

22:01:57

.506

22:02:06

.828

22:02:

16.154

22:02:25

.478

22:02:34

.802

22:02:

44.124

22:02:53

.448

22:03:02

.772

22:03:

12.096

22:03:21

.418

22:03:30

.744

22:03:

40.068

22:03:

49.392

22:03:58

.714

22:04:08

.036

22:04:17

.360

22:04:26

.684

22:04:36

.008

22:04:45

.332

22:04:54

.656

22:05:03

.980

22:05:

13.304

22:05:22

.628

22:05:31

.944

22:05:

41.260

22:05:50

.562

-120

-100

-80

-60

-40

-20

0

MOS

RxQ avg

RxLev avg

Similar results through thisdata when the feature isenabled



RSACCH Disabled (UL Legacy RLT) VQ samples are recorded in Opera


93/129


RSACCH Disabled (UL, Legacy RLT) VQ samples are recorded in Opera

Server Time Evolution Graph - VQ1, UL RSACCH OFF, Legacy RLT

0

1

2

3

4

5

6

7

11:34:57

.590

11:35:06

.914

11:35:

16.238

11:35:25

.560

11:35:34

.884

11:35:

44.208

11:35:53

.532

11:36:02

.854

11:36:

12.178

11:36:21

.502

11:36:30

.820

11:36:

40.150

11:36:

49.474

11:37:

17.444

11:37:26

.766

11:37:36

.088

11:37:

45.414

11:38:04

.060

11:38:

13.386

11:38:22

.708

11:38:32

.032

11:38:

41.356

11:38:50

.676

11:39:00

.004

-120

-100

-80

-60

-40

-20

0

MOSRxQ avg

RxLev avg

Time Evolution Graph - VQ2, UL RSACCH OFF, Legacy RLT

0

1

2

3

4

5

6

7

11:55:

12.260

11:55:21

.584

11:55:30

.906

11:55:

40.230

11:55:

49.554

11:55:58

.876

11:56:08

.202

11:56:

17.524

11:56:26

.848

11:56:36

.172

11:56:

45.488

11:56:54

.818

11:57:04

.142

11:57:

13.466

11:57:22

.790

11:57:32

.114

11:57:

41.436

11:57:50

.760

11:58:00

.084

11:58:09

.408

11:58:

18.730

11:58:28

.054

11:58:37

.378

11:58:

46.702

11:58:56

.026

11:59:05

.350

11:59:

14.674

11:59:23

.992

11:59:33

.320

11:59:

42.644

11:59:51

.968

-120

-100

-80

-60

-40

-20

0

MOSRxQ avg

RxLev avg


0

1

2

3

4

5

6

7

12:08:

11.444

12:08:20

.770

12:08:30

.094

12:08:39

.418

12:08:

48.742

12:08:58

.064

12:09:07

.386

12:09:

16.712

12:09:26

.036

12:09:35

.358

12:09:54

.006

12:10:03

.328

12:10:

12.654

12:10:21

.976

12:10:31

.300

12:10:

49.946

-120

-100

-80

-60

-40

-20

0

MOS

RxQ avg

RxLev avg


0

1

2

3

4

5

6

7

12:18:

47.356

12:18:56

.680

12:19:06

.004

12:19:

15.328

12:19:24

.650

12:19:33

.974

12:19:52

.620

12:20:01

.944

12:20:

11.268

12:20:20

.592

12:20:39

.240

12:20:

48.564

12:20:57

.888

12:21:25

.858

-120

-100

-80

-60

-40

-20

0

MOS

RxQ avg

RxLev avg

MOS is stable during UL tests,because UL is still good whileDL is already dropping thecall Imbalanced cell



RSACCH Enabled (UL Legacy RLT) VQ samples are recorded in Opera


94/129


RSACCH Enabled (UL, Legacy RLT) VQ samples are recorded in Opera

Server Time Evolution Graph - VQ1, UL RSACCH ON, Legacy RLT

0

1

2

3

4

5

6

7

21:47:53

.456

21:48:02

.780

21:48:

12.104

21:48:21

.492

21:48:

40.138

21:48:

49.462

21:48:58

.784

21:49:08

.108

21:49:

17.430

21:49:36

.080

21:49:

45.402

21:49:54

.726

21:50:04

.050

21:50:22

.698

21:50:32

.018

21:50:

41.344

21:50:50

.666

-120

-100

-80

-60

-40

-20

0

MOSRxQ avg

RxLev avg

Time Evolution Graph - VQ2, UL RSACCH ON, Legacy RLT

0

1

2

3

4

5

6

7

21:58:

47.778

21:58:57

.100

21:59:06

.424

21:59:

15.748

21:59:25

.072

21:59:34

.396

21:59:

43.718

21:59:53

.042

22:00:02

.366

22:00:

11.690

22:00:21

.012

22:00:39

.660

22:00:

48.982

22:00:58

.306

22:01:07

.628

22:01:16

.954

-120

-100

-80

-60

-40

-20

0

MOS

RxQ avg

RxLev avg


0

1

2

3

4

5

6

7

22:09:21

.292

22:09:30

.616

22:09:

49.260

22:09:58

.586

22:10:07

.910

22:10:

17.234

22:10:26

.556

22:10:35

.876

22:10:

45.204

22:10:54

.528

22:11:03

.850

22:11:22

.498

22:11:31

.822

22:11:41

.142

22:11:50

.470

22:11:59

.786

-120

-100

-80

-60

-40

-20

0

MOS

RxQ avg

RxLev avg


0

1

2

3

4

5

6

7

22:20:00

.454

22:20:09

.778

22:20:

19.104

22:20:37

.750

22:20:

47.076

22:20:56

.398

22:21:05

.722

22:21:15

.046

22:21:24

.368

22:21:33

.692

22:21:43

.014

22:21:52

.340

22:22:01

.664

22:22:

10.986

22:22:20

.310

22:22:29

.634

22:22:38

.794

-120

-100

-80

-60

-40

-20

0

MOS

RxQ avg

RxLev avg

The UL tests dont bringadditional information about

feature behaviour becauseUL remains good all the timeduring each passage



RSACCH Disabled (DL, Differentiated RLT) VQ samples are recorded in Opera


95/129


RSACCH Disabled (DL, Differentiated RLT) VQ samples are recorded in OperaClient

Time Evolution Graph - VQ1, DL RSACCH OFF, Differentiated RLT

0

1

2

3

4

5

6

7

10:43:50.364 10:43:59.624 10:44:18.284

-91

-90

-89

-88

-87

-86

-85

-84

-83

-82

-81

-80

MOS

RxQ avg

RxLev avg

Time Evolution Graph - VQ2, D L RSACCH OFF, Differentiated RLT

0

1

2

3

4

5

6

7

1 0: 57 :2 4. 84 4 1 0: 57 :3 4. 16 8 1 0: 57 :4 3. 49 0 1 0: 57 :5 2. 80 6 1 0: 58 :0 2. 12 6 1 0: 58 :1 1. 40 6

-96

-94

-92

-90

-88

-86

-84

-82

-80

-78

-76

MOS

RxQ avg

RxLev avg

Time Evolution Graph - VQ3, DL RSACCH OFF, Differentiated RLT

-2

-1

0

1

2

3

4

5

alu seminar rx acch

Documents