You are on page 1of 193

VAMOS

Feature introduction Strategy & Monitoring


VAMOS Program Core Team
MGR / TIPS / NEA
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT CONFIDENTIAL SOLELY FOR AUTHORIZED PERSONS HAVING A NEED TO KNOW PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

PUBLICATION INFORMATION
Author
Ramez SOSS
Updates: Mrio BERNARDES / Alexandru PETRAN / Ruben CORREIA / Nenad MOMIR

Reference documentation
VAMOS SFD 3BK 10204 0678 DTZZA
System Level Simulations MEMO 211157 (R&D/SYT/211157_v1)
3GPP TS 45.914 - Circuit switched voice capacity evolution for GERAN (Rel-9)

Publication history
July 2011 - Document creation
March 2012 Document update (Ed1 Rel.)

COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.


ALCATEL-LUCENT CONFIDENTIAL SOLELY FOR AUTHORIZED PERSONS HAVING A NEED TO KNOW PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

CONTENTS
1 | FEATURE DESCRIPTION
2 | FEATURE ACTIVATION STRATEGY
3 | TEST STRATEGY
4 | PERFORMANCE EVALUATION
5 | RESTRICTIONS / OTHER ISSUES
6 | CONCLUSION
7 | APPENDIX A: VAMOS SUITABILITY EVALUATION
8 | APPENDIX B: VAMOS SIMULATION RESULTS
9 | APPENDIX C: VAMOS DEPENDENCIES - BSSoIP
3
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

CONTENTS
1 | FEATURE DESCRIPTION
2 | FEATURE ACTIVATION STRATEGY
3 | TEST STRATEGY
4 | PERFORMANCE EVALUATION
5 | RESTRICTIONS / OTHER ISSUES
6 | CONCLUSION
7 | APPENDIX A: VAMOS SUITABILITY EVALUATION
8 | APPENDIX B: VAMOS SIMULATION RESULTS
9 | APPENDIX C: VAMOS DEPENDENCIES - BSSoIP
4
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

1 | VAMOS TECHNICAL DESCRIPTION


1.1 | INTRODUCTION

5
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

VAMOS TECHNICAL DESCRIPTION


WHAT IS VAMOS?
VAMOS (Voice services over Adaptive Multi-user channels on One Slot)
is a 3GPP Rel-9 feature
MUROS (Multi-User Reusing-One-Slot) is the corresponding 3GPP study item described
by Technical Report 3GPP 45.914

VAMOS allows multiplexing of two users simultaneously on the same


radio resource in the CS mode both in DL & UL, using the same timeslot
number, physical sub-channel, ARFCN and TDMA frame number
Accordingly, VAMOS allows assignment on a single GSM CS radio timeslot of:
Two users in Full Rate (instead of one),
Or four users in Half Rate (instead of two),
Or three users in Half Rate (instead of two)

Benefits for the operator: Decrease Total Cost of Ownership (TCO)


Increased hardware efficiency (more users per TRX)
Increased spectral efficiency (then network capacity) in certain scenarios
6
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

VAMOS TECHNICAL DESCRIPTION


VAMOS BENEFITS
As voice service price gets cheaper, most operators face the challenge to
obtain efficient utilization of hardware and spectrum resources:
VAMOS allows significant capacity gains: Multiplexing two users on the same
carrier/timeslot will also allow reducing the number of TRXs
Target average capacity gain around x1.5
Capacity gains are more important using VAMOS-HR channels, whereas VAMOS-FR
(especially with AMR-WB) might be interesting for operators seeking high voice quality

HOWEVER, capacity increase due to VAMOS is performed to the detriment


of the call quality performance
In VAMOS mode, each user generates strong additional co-channel interference to the
paired user, thus increasing the overall interference level in the network
In case a network is quality-limited, there is no room for VAMOS gain

VAMOS allows to convert a quality margin to additional capacity


Good C/I conditions: Up to 100% gains
Poor C/I conditions: No gain
7
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

VAMOS TECHNICAL DESCRIPTION


VAMOS INTRODUCTION SCENARIOS

CS capacity increase in existing network with medium or good quality:

Instead of new TRX + reworked frequency planning

Or PS capacity increase, as an induced effect of voice efficiency

Ex: for Operators w/o 3G/LTE

Less TRX to deploy in new networks (hardware saving)

CS capacity recovery in case of GSM re-farming, 2 possible scenarios:

Both GSM spectrum reduction + GSM h/w capacity reduction


=> VAMOS allows recovering part of the lost capacity provided
that there is some quality margin after refarming

GSM HW capacity reduction only => VAMOS allows recovering


lost capacity
VAMOS shall not be interesting where the operator reduces its GSM
spectrum with the same GSM HW capacity since the quality margin
after refarming will be low (due to the tighter frequency planning)

Hot spots, occasional events

GSM TRX 1 TRX 3

MHz

UMTS

GSM TRX 1 TRX 2 + VAMOS

MHz
8

COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.


ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

VAMOS TECHNICAL DESCRIPTION


RADIO TRANSMISSION IN VAMOS MODE
With VAMOS, two users are multiplexed on a given timeslot:
In Downlink
The BTS transmits simultaneously to 2 MSs on the same timeslot and frequency
Using two different Training Sequences (TSC)
With adaptive-QPSK modulation
One adaptive-QPSK symbol is a pair of bits,
where each bit belongs to a different sub-channel

BTS

ARFCN : 160
TS: 3
TSC : 0

Allows to double the throughput compared


to legacy GMSK
Variant of QPSK allowing for independent
power control for the two users

ARFCN : 160
TS : 3
TSC : 0

ARFCN: 160
TS: 3
TSC: 5

ARFCN : 160
TS: 3
TSC : 5

MS1
MS2

In Uplink
2 MSs transmit simultaneously on the same timeslot and frequency, using GMSK and
different TSC
The BTS uses the different TSC to separate the signals from the two MSs
9
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

VAMOS TECHNICAL DESCRIPTION


VAMOS PAIRING TDMA MULTIFRAME
26-Multiframe for a FR channel: 26 bursts in 120 ms

T T T T T T T T T T T T A T T T T T T T T T T T T i
T = TCH

A = SACCH

i = idle frame

Non-VAMOS

26-Multiframe for two HR channels: 13 bursts for each user in 120 ms

T t T t T t T t T t T t A T t T t T t T t T t T t a
T = TCH user 1

t = TCH user 2

A = SACCH user 1

a = SACCH user 2

26-Multiframe for two VAMOS FR subchannels

T T T T T T T T T T T T A T T T T T T T T T T T T i
T T T T T T T T T T T T A T T T T T T T T T T T T i
T = TCH user #2
A = SACCH user #1
T = TCH user #1
26-Multiframe for four VAMOS HR subchannels

A = SACCH user #2
VAMOS

T t T t T t T t T t T t A T t T t T t T t T t T t a
T t T t T t T t T t T t A T t T t T t T t T t T t a
T = TCH user #1

T = TCH user #2

A = SACCH user #1

A = SACCH user #2

t = TCH user #3
a = SACCH user #3
10

COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.


ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

t = TCH user #4
a = SACCH user #4

VAMOS TECHNICAL DESCRIPTION


TRAINING SEQUENCE CODES
Training sequence: a fixed bit sequence (26 bits) known by the receiver for
synchronization and channel estimation purposes
A TSC is assigned to a MS during channel allocation and transmitted in each UL/DL burst

With VAMOS, 2 different TSCs must be assigned to the paired VAMOS subchannels:
On the UL, the BTS uses the different TSCs to separate the received signals
On the DL, the MS uses its own TSC knowledge (and, in some cases, also the knowledge of the TSC
associated to the paired user) to detect the desired signal

A new set of TSCs (TSC Set 2 including 8 TSC) - with improved cross correlation
properties compared to the legacy TSC set 1 - has been proposed for VAMOS
11
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

VAMOS TECHNICAL DESCRIPTION


VAMOS IMPACT ON MOBILE TERMINALS
Due to the high co-channel interference created by the paired user, VAMOS needs
powerful interference cancellation techniques and requires advanced receivers
able to operate at SIR close to 0dB with acceptable performance
This is the case of SAIC (DARP Phase 1) receivers as well as new VAMOS-aware
receivers that will be specifically designed for VAMOS
Two levels of VAMOS-aware MSs are introduced in Rel-9, supporting TSC set 2:
VAMOS Level 1: SAIC MSs that in addition understand and can use the new training
sequences
VAMOS Level 2: Advanced VAMOS-specific algorithms for interference cancellation
instead of SAIC

Nevertheless, legacy non-SAIC terminals could also support VAMOS operations but
only if coupled to VAMOS-aware terminals with advanced receiver architectures
specifically designed for VAMOS (VAMOS L2)
12
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

VAMOS TECHNICAL DESCRIPTION


VAMOS CONCEPTS - AQPSK MODULATION

A new modulation technique used only in Downlink transmission in VAMOS mode

AQPSK modulation shall only be used when 2-bits symbols (one bit for each
paired VAMOS user) must be transmitted during a burst
When DL DTX is enabled, during a speech pause of one of the paired users, legacy GMSK
must be used for the other user if he is in a speech period
The radio transmission will be cut when both users have entered a speech pause and they
have no SID frames to transmit

The AQPSK symbol rate is equal to GMSK symbol rate (around 270,833 ksymb/s)

The power ratio between Q & I channels is defined as the


SubChannel Power Imbalance Ratio (SCPIR):

SCPIR = 20 x log10 (tan()) dB

is dynamically chosen by the BSS - according to the radio


conditions & the MS capabilities - such that |SCPIR| 10 dB

A constant AQPSK backoff value is applied by the BTS


(estimated at = 45). A 3 dB backoff is expected, to avoid
any distortion to the transmitted signal in AQPSK modulation

13
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

VAMOS TECHNICAL DESCRIPTION


VAMOS CONCEPTS SCPIR
(1/3)
Why power balancing is needed between the 2 VAMOS subchannels?
i.

Due to different terminal capabilities: Both terminals of a VAMOS


pair do not necessarily have the same reception capabilities =>
the signal for the MS with the lower capabilities can be favored

ii.

Since the 2 paired users do not necessarily experience the same


path loss and/or radio conditions, power balancing is needed to
allow independent power control on both sub-channels

SCPIR is the ratio between the DL power transmitted by the BTS for the
subchannel#1 and the DL power transmitted by the BTS for the subchannel#2:
SCPIR [dB] = BS_TXPWR_1 BS_TXPWR_2, both in dBm
BTS power for subchannel #2

BTS power for subchannel #1

AQPSK power: BS_TXPWR [dBm] = 10 log(BS_TXPWR_1 [mW] + BS_TXPWR_2 [mW])


There is physically ONE transmitted power: the symbol power (AQPSK power)

Too high SCPIR => sub-channel#2 signal could be severely disturbed


Too low SCPIR => sub-channel#1 signal could be severely disturbed
SCPIR should be kept within a range defined by SCPIRlow & SCPIRhigh,
function of MS capabilities
14
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

VAMOS TECHNICAL DESCRIPTION


VAMOS CONCEPTS SCPIR
(2/3)
SCPIRlow of a VAMOS pair is the minimum SCPIR value allowing correct
signal decoding for the MS allocated to subchannel#1 of that pair (independently
of the MS capabilities of the MS allocated into subchannel#2)

SCPIRhigh of a VAMOS pair is the maximum SCPIR value allowing correct


signal decoding for the MS allocated to subchannel#2 of that pair (independently
of the MS capabilities of the MS allocated into subchannel#1)

A negative SCPIRlow value means that the MS is capable of correctly decoding its
VAMOS signal even when the paired sub-channel is transmitted with a higher power

If MS_1 is on VAMOS subchannel#1 and MS_2 is on VAMOS subchannel#2, then


SCPIRlow & SCPIRhigh for any VAMOS couple (MS_1, MS_2) are computed as follows:
SCPIRlow(MS_1, MS_2) = SCPIRlow(MS_1, x),
SCPIRhigh(MS_1, MS_2) = - SCPIRlow(MS_2, x)

Condition for MS_1 & MS_2 pairing:


SCPIRlow(MS_1, MS_2) SCPIRhigh(MS_1, MS_2)
=> SCPIRlow(MS_1, x) + SCPIRlow(MS_2, x) 0
15
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

VAMOS TECHNICAL DESCRIPTION


VAMOS CONCEPTS SCPIR
(3/3)

Recommended SCPIRlow value @ VAMOS allocation per MS type:

MS capability of the MS on subchannel#1

SCPIRlow (MS_1, x)

legacy non-SAIC

+8

legacy SAIC

-2

VAMOS-1

-4

VAMOS-2

-10

These values are configurable


at OMC-R level through the
parameters:
SCPIR_LOW_MS_ALLOC_xxx

For correct decoding of both DL signals:


SCPIRlow (MS_1, MS_2) < SCPIR (MS_1, MS_2) < SCPIRhigh (MS_1, MS_2)

Ex: From a given BS_TXPWR_2 value of a VAMOS pair, assuming SCPIRlow < 0 ,
BS_TXPWR_1 shall be in the range [BS_TXPWR_2+SCPIRlow, BS_TXPWR_2+SCPIRhigh]

The BTS cannot compute UL SCPIR because the UL signal level measured at the
antenna connector is the sum of the UL signals of both VAMOS subchannels
16
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

VAMOS TECHNICAL DESCRIPTION


VAMOS PAIRING COMBINATIONS
The operator can configure the allowed MS pairings via a set of 8
parameters:
EN_PAIRING_xxx_yyy: to activate/deactivate MS pairings depending
on the MS capabilities xxx and yyy
Mandatory rules exist between the EN_PAIRING_xxx_yyy flag and the related
SCPIR_LOW_MS_ALLOC_xxx and SCPIR_LOW_MS_ALLOC_yyy parameters
Recommended pairing combinations:
SubCh#2

legacy non-SAIC

legacy SAIC

VAMOS-1

VAMOS-2

legacy non-SAIC

No

No

No

Yes

legacy SAIC

No

Yes

Yes

Yes

VAMOS-1

No

No

Yes

Yes

VAMOS-2

No

No

Yes

Yes

SubCh#1

Note: Non-SAIC MSs can never be paired to Non-SAIC or SAIC MSs


17
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

VAMOS TECHNICAL DESCRIPTION


HOW THE BSS DERIVES THE MS CAPABILITY
The BSS derives the MS capabilities from the VAMOS Level and the Downlink
Advanced Receiver Performance (DARP) fields of MS CLASSMARK 3:
VAMOS Level = 01: the MS capability shall be set to VAMOS-1 MS
VAMOS Level = 10 or 11: the MS capability shall be set to VAMOS-2 MS
VAMOS Level = 00 and DARP = 01, 10 or 11: the MS capability set to legacy SAIC
VAMOS Level = 00 and DARP = 00 then: the MS capability shall be set to "to be
tested" (see section 1.6) if the EN_TEST_FOR_NON_SAIC parameter = 1, otherwise the
MS capability is set to legacy non-SAIC
VAMOS Level
DARP

00

00

Depending on
EN_TEST_FOR_NON_SAIC

01

01
10

VAMOS-1
SAIC

11
18
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

10

11

VAMOS-2

VAMOS TECHNICAL DESCRIPTION


TSC ALLOCATION RULES
3GPP rule: the TSCs for the 2 VAMOS subchannels are selected either from
different TSC Sets or both from TSC Set 1 in case of SAIC-SAIC pairs, but cannot
be both from TSC Set 2
If at least one MS of a VAMOS pair is VAMOS capable, then the BSS shall assign:
A training sequence chosen from TSC Set 1 for VAMOS subchannel#1 in the VAMOS pair
And the training sequence with the same training sequence code and selected from TSC
Set 2 for the VAMOS subchannel#2 in the VAMOS pair

Supported TSC pairs used for traffic channels in VAMOS mode:


VAMOS subchannel#1

VAMOS subchannel#2

Usage

TSC_1 (Set 1)

TSC_1 (Set 2)

(legacy, VAMOS) or (VAMOS, VAMOS) pairs

TSC_1 (Set 1)

TSC_2 (Set 1)

Only (legacy SAIC, legacy SAIC) pairs

TSC_2 (Set 1)

TSC_2 (Set 2)

(legacy, VAMOS) or (VAMOS, VAMOS) pairs

For common control channels, BCCH and packet channels TSC is the same as B11 (TSC
parameter).
No notifications from BSC to MFS will be needed when VAMOS is enabled/disabled in the cell.

In cells where VAMOS is not enabled, the TSC parameter shall be used as in B11
TSC_1 & TSC_2 are defined according to the telecom parameter TSC_1_2
19
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

VAMOS TECHNICAL DESCRIPTION


SIGNALING CHANNELS IN VAMOS MODE
According to 3GPP simulation results, the SACCH performance of a VAMOS user
may not meet the requirements in some scenarios:
As the SACCH frames of both users are transmitted simultaneously, SACCH decoding might
be impacted by the increased interference

SACCH performance can be improved using:


The repeated SACCH technique (standardized since Rel-6, available since B11) or
The shifted SACCH mapping (introduced in Rel-9)
The objective is to enhance SACCH performance both in UL & DL by rearranging the TDMA frame
mapping of 2nd VAMOS subchannel so that the allocation of the SACCH frames does not collide with
the SACCH frames of 1st VAMOS subchannel where the legacy TDMA frame mapping is applied
Consequently, SACCH performance is enhanced taking profit of the GMSK transmission during speech
pauses of the paired user entering DTX or even during AQPSK modulation by applying power
increase to favor the SACCH frame over the paired TCH frame
3GPP rule: Shifted SACCH shall always/only be used with a VAMOS Level 2 MS using a
TSC from the Set 2 even if it is allocated in Non-VAMOS mode
Example: TDMA multiframe
organization with 2 FR users:

9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25

u1 T T T T T T T T T T T T S T T T T T T T T T T T T I
u2 T T T T T T T T T T T T T S T T T T T T T T T T T I
20

COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.


ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

VAMOS TECHNICAL DESCRIPTION


VAMOS IN ALU

VAMOS is supported in IP mode only


Following 3GPP rules, VAMOS pairing is forbidden in an inter-cell HO
Supported VAMOS configurations: VAMOS-FR, VAMOS-HR and Semi-VAMOS HR

VAMOS FR/HR configurations are not supported in B12 (high complexity of radio
allocation and power control algorithms)

ALU strongly recommends AMR activation in VAMOS mode, to enhance voice


quality and increase signal immunity to interference
21
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

VAMOS TECHNICAL DESCRIPTION


VAMOS IN ALU - WHY IP TRANSPORT?

VAMOS allows to carry up to 4 calls per radio timeslot

In TDM, existing mapping between one radio timeslot and one Abis nibble does
not work any more: 16 kbits/s are not enough

Possible solutions:
a. Using two 16 kbits/s nibbles, i.e. doubling the Abis bandwidth requirements for voice,
whereas only a part of the traffic will be using VAMOS
=> Waste of resources!
b. Using pools of 16 kbits/s resources and 32 kbits/s resources could be used
=> Complex feature implementation and subsequent resource dimensioning!
c. A single large Abis pipe is the optimal solution: This pipe is provided by native
IP transport in the BSS

Can be used either with IPoEthernet or IPoverE1 (see Appendix C)

Efficient voice multiplexing allows to compensate IP overheads

22
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

1 | VAMOS TECHNICAL DESCRIPTION


1.2 | VAMOS SUITABILITY EVALUATION

23
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

VAMOS SUITABILITY EVALUATION


CONTEXT
Purpose: Assess the possibility of VAMOS introduction depending on
network conditions:

VAMOS is beneficial in good quality networks, as it converts the quality margin


into additional capacity

Networks that are capacity-limited before VAMOS introduction are likely to be


quality-limited after VAMOS; therefore, there is no room for VAMOS in a network
already suffering from high interference (i.e. quality-limited)

The methodology described in the next slides aims at evaluating to which


extent is a network favourable for VAMOS introduction

2 case studies are presented: (details in Appendix A)


Case Study 1: Vodafone Qatar => Very favourable case with very good network quality
Case Study 2: CMCC - Shanghai area => Medium network quality, less favourable for
VAMOS
24
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

VAMOS SUITABILITY EVALUATION


HOW TO ESTIMATE NETWORK QUALITY (1/2)
1. Through C/I measurements (e.g. drive tests):

Average C/I < 12 dB

=> VAMOS benefits: LOW

12 < Average C/I < 18 dB

=> VAMOS benefits: MEDIUM

Average C/I > 18 dB

=> VAMOS benefits: HIGH

2. Through analysis of available frequency spectrum & reuse size:

Average Reuse Cluster Size (ARCS)

For example, assuming dedicated BCCH band:


BCCH ARCS = number of BCCH frequencies
TCH ARCS = number of TCH frequencies / average number of TCH TRXs per cell
25
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

VAMOS SUITABILITY EVALUATION


HOW TO ESTIMATE NETWORK QUALITY (2/2)
Average Reuse Cluster Size (ARCS) criteria:
Low quality

Medium quality

ARCS

Aggressive FP

Typical FP

Conservative FP

BCCH

12

18

20

TCH non-Hopping

10

12

12

TCH Hopping

12

12

High quality

For Synthesized Frequency Hopping (SFH), RF load is used to estimate


the FP quality:

RFload = # Hopping TRX per cell/ # Hopping frequencies per cell

In case of 1x1 fractional reuse, RFload should be strictly less than 10%

In case of 1x3 fractional reuse, RFload should be strictly less than 30%
26
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

VAMOS SUITABILITY EVALUATION


OTHER CRITERIA

Assess network interference level from Performance


Measurement (PM) counters
DL Quality HO rate: [MC672] / CHO_All
UL Quality HO rate: [MC670] / CHO_All
However, the % of Quality HO depends on the settings of corresponding parameters
triggering emergency HO

Penetration of recent mobiles

As VAMOS requires advanced receivers able to work at low SIR ranges, a reasonable
penetration of Single Antenna Interference Cancellation mobiles (SAIC) is mandatory to
ensure significant VAMOS gain

In B11, there is no way to count SAIC mobiles penetration; but at least the penetration of
Rel-4 mobiles can be estimated from PM counters as [P450e] / [P450d]

A low penetration of Rel-4 mobiles indicates low penetration of SAIC mobiles. However,
Rel-04 mobiles are not necessarily SAIC-capable
27
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

VAMOS SUITABILITY EVALUATION


OTHER FEATURES LINKED TO VAMOS

IP transmission: VAMOS is only supported in IP mode


whether using IPoEth or IPoE1

H/W: VAMOS is supported on Twin & MC-TRX/RRH; it also requires


Mx-BSC

At VAMOS introduction, the following features are strongly


recommended:

AMR: To improve voice quality in VAMOS mode and increase signal robustness against
interference, AMR is strongly recommended

HR: It doesnt make sense to look for capacity increase by VAMOS introduction if HR is not
already exploited in the network

DTX & Power Control: Power Control and Discontinuous Transmission are key features
to minimize interference in VAMOS mode

28
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

1 | VAMOS TECHNICAL DESCRIPTION


1.3 | RADIO ALLOCATION STRATEGY

29
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

VAMOS RADIO ALLOCATION STRATEGY


MAIN APPROACH
The user pairing strategy is a trade-off between the following objectives:
Maximize the capacity gain,
Minimize the un-pairing probability,
Minimize the co-channel interference for the paired users
while keeping acceptable call quality performance

The radio allocation strategy determines the most appropriate users to pair
together and on which VAMOS capable-timeslot, taking into account:
The cell load: VAMOS pairing can be only triggered beyond a given traffic load in the cell;
no need to pair users when the load is low
Radio conditions: To reduce unpairing probability, pairing should be avoided if a user
already experiences bad radio conditions
The MS capabilities
The allowed pairing combinations in the cell

The VAMOS user pairing process is integrated into the radio TCH allocation
function
30
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

VAMOS RADIO ALLOCATION STRATEGY


DEFINITION: SOURCE MS vs. TARGET MS
Source MS is a MS whose presence can potentially trigger the VAMOS user
pairing process in that cell; when it is:
Either candidate for intra-cell HO (current channel can be non-VAMOS or VAMOS TCH)
Or in the call establishment phase in the cell (with the exception of a MS to be allocated on
a TCH in the inner zone of a concentric cell)

MS cannot be directly allocated to a VAMOS subchannel neither after an inter-cell


handover nor after a directed retry => ALU rule inspired by 3GPP specifications
Target MS is a MS which can be potentially paired with a Source MS, when it is:
Allocated to a non-VAMOS TCH on a VAMOS-capable TRX,
In dedicated mode, not allocated in DTM and N_DELAYED_HO_CAUSE30 is not running
Fulfilling radio conditions criteria (detailed in next slides)

A Target MS which is selected to be paired with a given Source MS is not handedover; but its current non-VAMOS TCH channel simply becomes a VAMOS TCH,
sharing the same physical resource with the Source MS
31
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

VAMOS RADIO ALLOCATION STRATEGY


VAMOS PAIRING SCENARIOS
VAMOS pairing can be reached in the following scenarios:
During intra-cell VAMOS pairing HO (cause 35), if EN_VAMOS_PAIRING_CA =TRUE
At call establishment of the source MS, if EN_VAMOS_NASS = TRUE

VAMOS pairing is forbidden in the following scenarios:


During an inter-cell HO or Directed Retry
If the mobile is already engaged in Dual Transfer Mode (DTM)
At call establishment if the TCH request is queued

If EN_VAMOS_NON_AMR=FALSE, VAMOS pairing is allowed only for AMR calls


In case of concentric cell:
VAMOS allocation in the inner zone is only allowed on intra-cell HO, when both mobiles
candidate for pairing are located in the same zone.
A direct allocation in VAMOS mode in the inner zone is not possible on call establishment,
as signal strength values of the Source MS (assigned an SDCCH on the outer zone) &
Target MS (already in the inner zone) are not comparable
32
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

VAMOS RADIO ALLOCATION STRATEGY


VAMOS PAIRING SCENARIOS : EXAMPLE
Animated slide:

VAMOS pairing during


call establishment

Play in Slide Show mode

(EN_VAMOS_NASS = True)

During inter-cell Handover


VAMOS pairing HO
(cause 35)

Target
MS
F1, TS 3,

At call establishment:
SDCCH sub-channel
Not queued
No Directed retry

CLICK TO PLAY

Source MS

Source MS
MS2

MS2

F1, TS 3,
TCH
VAMOS-FR
TCH-FR

Cell A

Inter-cell HO: MS2 cannot be source MS

No VAMOS allocation
33
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

Cell B

VAMOS RADIO ALLOCATION STRATEGY


CELL LOAD CRITERIA
(1/2)
As in B11, the choice whether a FR or HR channel shall be assigned is based on
the load evaluation (among other criteria)
In addition to LOAD_SV1 & LOAD_SV3 levels used for non-VAMOS allocations,
new load levels have been defined in B12 for VAMOS allocation:
LOAD_VAMOS_FR: if the cell load increases up to this level, a VAMOS FR subchannel can
be allocated to the Source MS (if supported by MS/cell & suitable Target MS can be found)
LOAD_VAMOS_HR: if the cell load still increases up to that level, a VAMOS HR
subchannel can be allocated to the Source MS (if supported by MS/cell and if a suitable
Target MS can be found)
The following mandatory rules should be respected:
LOAD_SV3 LOAD_VAMOS_HR: Given the co-channel interference generated by the paired user,
it doesnt make sense to allow VAMOS-HR allocation before permitting non-VAMOS HR in the cell
LOAD_VAMOS_FR LOAD_VAMOS_HR: Gradual load increase triggers VAMOS-FR allocations
before VAMOS-HR allocations (or at least both allocations at the same time)

To allow a hysteresis zone between VAMOS & non-VAMOS allocations, 4 parameters are
defined in B12: THR_FR_LOAD_L_VAMOS_FR, THR_FR_LOAD_U_VAMOS_FR,
THR_FR_LOAD_L_VAMOS_HR and THR_FR_LOAD_U_VAMOS_HR
34
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

VAMOS RADIO ALLOCATION STRATEGY


CELL LOAD CRITERIA
(2/2)
The Cell Load Evaluation is computed as in B11:
Cell load AV_LOAD() computed from
Load samples = NB_BUSY_TS / NB_TS * 100
Non sliding window (LOAD_EV_PERIOD) averaging process
Example:

AV_LOAD
100%

VAMOS-FR & VAMOS-HR allocations


THR_FR_LOAD_U_VAMOS_HR

THR_FR_LOAD_U_VAMOS_FR
THR_FR_LOAD_L_VAMOS_HR

VAMOS-FR allocations
Non-VAMOS HR allocations
Non-VAMOS
allocations
VAMOS-FR allocations
Non-VAMOS HR allocations

THR_FR_LOAD_L_VAMOS_FR

Non-VAMOS allocations
Time
35
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

VAMOS RADIO ALLOCATION STRATEGY


CELL LOAD CRITERIA CASE 1
LOAD_VAMOS_FR < LOAD_SV3 & LOAD_VAMOS_HR > LOAD_SV1
Cell load
Non-VAMOS FR
LOAD_VAMOS_HR
Non-VAMOS HR
SV3
Non-VAMOS HR
(SV1 and SV3)

LOAD_SV1

LOAD_SV3

VAMOS FR

VAMOS HR

LOAD_VAMOS_FR

Pros:

Non-Vamos
allocation

Vamos
allocation

Could be beneficial if VAMOS-FR can provide better voice quality than non-VAMOS HR
Allows early VAMOS-FR allocation, therefore providing high capacity gains
Cons:
Non-VAMOS HR has higher output power than VAMOS-FR due to AQPSK back-off,
accordingly, this scenario will probably cause performance degradation compared to case 3
36
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

VAMOS RADIO ALLOCATION STRATEGY


CELL LOAD CRITERIA CASE 2
LOAD_SV3 < LOAD_VAMOS_FR < LOAD_SV1 & LOAD_VAMOS_HR > LOAD_SV1
Cell load
Non-VAMOS FR
LOAD_VAMOS_HR
Non-VAMOS HR
SV3
Non-VAMOS HR
(SV1 and SV3)

LOAD_SV1
LOAD_VAMOS_FR
LOAD_SV3

VAMOS FR

VAMOS HR

Non-Vamos
allocation

Vamos
allocation

Pros:
Compared to case 1, more calls can benefit from high DL transmit power
Cons:
Still sub-optimal coverage vs. capacity comprise due to early VAMOS-FR allocations with
respect to non-AMR HR
37
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

VAMOS RADIO ALLOCATION STRATEGY


CELL LOAD CRITERIA CASE 3
LOAD_SV1 < LOAD_VAMOS_FR < LOAD_VAMOS_HR
Cell load
Non-VAMOS FR
LOAD_VAMOS_HR
Non-VAMOS HR
SV3

LOAD_VAMOS_FR

Non-VAMOS HR
(SV1 and SV3)

LOAD_SV1

LOAD_SV3

VAMOS FR

VAMOS HR

Pros:

Non-Vamos
allocation

Vamos
allocation

Best choice to limit AQPS back-off impact: HR allocations have higher precedence than
VAMOS allocations
Cons:
Late VAMOS allocation compared to cases 1 & 2, but this could be compensated by HO
Cause 35 (VAMOS_PAIRING_HO)
38
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

VAMOS RADIO ALLOCATION STRATEGY


CELL LOAD CRITERIA CASE 4
LOAD_VAMOS_FR < LOAD_SV3 & LOAD_SV3 < LOAD_VAMOS_HR < LOAD_SV1
Cell load
Non-VAMOS FR
Non-VAMOS HR
SV3
LOAD_SV1
Non-VAMOS HR
(SV1 and SV3)

LOAD_VAMOS_HR

LOAD_SV3

VAMOS FR

VAMOS HR

LOAD_VAMOS_FR

Pros:

Non-Vamos
allocation

Vamos
allocation

High capacity gains: VAMOS is allowed very early in the cell


Cons:
Early VAMOS allocation increase the impact of AQPS back-off on overall cell coverage
Bad speech performance if VAMOS-FR cannot provide better VQ than non-VAMOS HR
Sub-optimal capacity usage caused by non-AMR mobiles mostly allocated 1 FR timeslot
39
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

VAMOS RADIO ALLOCATION STRATEGY


CELL LOAD CRITERIA CASE 5
LOAD_SV3 < LOAD_VAMOS_FR < LOAD_VAMOS_HR < LOAD_SV1
Cell load
Non-VAMOS FR
Non-VAMOS HR
SV3

LOAD_SV1

Non-VAMOS HR
(SV1 and SV3)

LOAD_VAMOS_HR
LOAD_VAMOS_FR
LOAD_SV3

VAMOS FR

VAMOS HR

Pros:

Non-Vamos
allocation

Vamos
allocation

Trade-off between coverage and capacity


Cons:
Sub-optimal capacity usage caused by non-AMR mobiles mostly allocated 1 FR timeslot

40
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

VAMOS RADIO ALLOCATION STRATEGY


RADIO CONDITIONS CRITERIA
(1/4)
The aim of checking radio conditions criteria is to:
1. Ensure minimum acceptable radio conditions for both users candidate for VAMOS pairing
2. Ensure appropriate radio conditions between both users (i.e. pathloss difference between
both users should be within a certain range defined by SCPIRlow & SCPIRhigh values)

The VAMOS user pairing algorithm relies on the AV_RXQUAL_DL_VAMOS_PAIRING


and AV_RXLEV_DL_VAMOS_PAIRING averages computed by the BSC using the DL
measurements provided by the Source and Target MSs

Note: UL measurements are not used to reduce the processing effort of the pairing algorithm and
because the DL is considered the limiting link for VAMOS

NORM_RXLEV_DL values are used to compute the AV_RXLEV_DL_VAMOS_PAIRING


averaged values using the A_LEV_VAMOS_PAIRING averaging window

RXQUAL_DL values are used to compute the AV_RXQUAL_DL_VAMOS_PAIRING averaged


values using the A_QUAL_VAMOS_PAIRING averaging window

41
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

VAMOS RADIO ALLOCATION STRATEGY


RADIO CONDITIONS CRITERIA
(2/4)

AV_RXLEV_DL_VAMOS_PAIRING is computed based on Normalized RxLev:


NORM_RXLEV_DL is the normalized RXLEV_DL value with respect to the BTS
transmitted power, computed as:
NORM_RXLEV_DL = RXLEV_DL + BS_TXPWR
BS_TXPWR: Attenuation with respect to the maximum BTS transmitted power

This normalization allows a fair comparison between RxLev values of different users
regardless their different power transmission levels (due to power control etc)

When a Source MS is in the call establishment phase, the averaging is based on the
NORM_RXLEV_DL measurements on DL SDCCH & SACCH bursts

If Source & Target MS are already allocated to a TCH in the cell, the averaging is
based on NORM_RXLEV_DL & RXQUAL_DL measurements on DL TCH/FACCH &
SACCH bursts

42
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

VAMOS RADIO ALLOCATION STRATEGY


RADIO CONDITIONS CRITERIA
(3/4)
1. Ensure minimum acceptable radio conditions for both users
candidate for VAMOS pairing:
To allow VAMOS pairing of a Source MS with a Target MS, the following
conditions must be fulfilled:

AV_RXQUAL_DL_VAMOS_PAIRING < RXQUAL_DL_MAX_VAMOS_PAIRING


=> Applicable to Target MS

Note: The RXQUAL criterion is not valid for Source MS because there is a strong possibility that the
frequency used for such RXQUAL measurements will change after VAMOS pairing, therefore this
information is not relevant for the pairing algorithm

AV_RXLEV_DL_VAMOS_PAIRING > RXLEV_DL_MIN_VAMOS_PAIRING


=> Applicable to both the Source MS & Target MS

43
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

VAMOS RADIO ALLOCATION STRATEGY


RADIO CONDITIONS CRITERIA
(4/4)
2. Ensure appropriate radio conditions between both users
(i.e. path loss difference between both users should be within
a certain range defined by SCPIRlow & SCPIRhigh values)
To VAMOS-pair 2 MSs (with MS1 in VAMOS subchannel#1 & MS2 in subchannel#2), their
AV_RXLEV_DL_VAMOS_PAIRING values should fulfill the following condition:

SCPIRlow(MS1, MS2) - DELTA_SCPIR_VAMOS_PAIRING


AV_RXLEV_DL_VAMOS_PAIRING(MS2) AV_RXLEV_DL_VAMOS_PAIRING(MS1)
SCPIRhigh(MS1, MS2) + DELTA_SCPIR_VAMOS_PAIRING
SCPIRlow (MS1, MS2) = SCPIR_LOW_MS_ALLOC_xxx
(xxx is MS capability of MS1)
SCPIRhigh (MS1, MS2) = - SCPIR_LOW_MS_ALLOC_yyy (yyy is MS capability of MS2)

DELTA_SCPIR_VAMOS_PAIRING is introduced to add flexibility to the pairing


algorithm:

If it is set to a positive value, then it will be allowed to VAMOS-pair two MSs having a difference
between the DL RXLEV values (in dBm) higher than SCPIRhigh or lower than SCPIRlow, i.e. the two
MSs may be in non-optimal radio conditions to be VAMOS-paired together

If it is set to a negative value, then the two MSs shall only be in optimal radio conditions to be
paired
44
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

VAMOS RADIO ALLOCATION STRATEGY


MS CAPABILITIES CRITERIA
Priorities are set for the different pairing combinations
The target is to exploit the best capacity gains from VAMOS pairing:
It is preferable to pair a VAMOS-L2 MS with a legacy non-SAIC MS than with a VAMOS-L1
MS, because a legacy non-SAIC MS can only be paired with a VAMOS- L2 MS (i.e. no
VAMOS pairing of legacy non-SAIC MS if VAMOS-L2 MS isnt available)
As very few VAMOS MSs will be available on the field at early VAMOS introduction, their
pairing with a legacy MS shall have a higher priority than pairing with another VAMOS one
Default priorities are presented below (1: highest priority, 6 = least priority)
Such priority rules are configurable by the operator through the parameters
PAIRING_PRIORITIES_NON_SAIC , PAIRING_PRIORITIES_SAIC ,
PAIRING_PRIORITIES_VAMOS1 and PAIRING_PRIORITIES_VAMOS2
Non-SAIC

SAIC

VAMOS-1
(TSC Set1)

VAMOS-1
(TSC Set2)

VAMOS-2
(TSC Set1)

VAMOS-2
(TSC Set2)

PAIRING_PRIORITIES_NON_SAIC

PAIRING_PRIORITIES_SAIC

PAIRING_PRIORITIES_VAMOS_1

PAIRING_PRIORITIES_VAMOS_2

45
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

VAMOS RADIO ALLOCATION STRATEGY


TARGET_MS LIST
This list is created in all VAMOS-supporting cells (where VAMOS is enabled)
Contains all the active MSs of the cell fulfilling ALL the following conditions:
MS is allocated into a non-VAMOS channel for a speech call on a VAMOS-capable TRX
MS type is allowed to be paired, based on the flags EN_PAIRING_xxx_yyy
The last AV_RXQUAL_DL_VAMOS_PAIRING < RXQUAL_DL_MAX_VAMOS_PAIRING
The last AV_RXLEV_DL_VAMOS_PAIRING > RXLEV_DL_MIN_VAMOS_PAIRING
The allocated TCH is not in DTM mode or it is in dedicated mode and the
N_DELAYED_HO_CAUSE30 is not running
The used codec is AMR or EN_VAMOS_NON_AMR is TRUE
When any of the above conditions is not fulfilled, the MS is removed from the
Target_MS list (e.g. call release, radio conditions criteria not satisfied)

The MSs contained in this list are candidate Target MS for VAMOS pairing, and
also Source MS in case of VAMOS pairing HO (cause 35)
46
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

VAMOS RADIO ALLOCATION STRATEGY


VAMOS PAIRING PROCESS DESCRIPTION (1/2)
When is VAMOS user pairing algorithm triggered?
When all the following conditions are fulfilled:
VAMOS is enabled in the cell
There are idle VAMOS subchannels in a VAMOS-capable TRX
The cell load criteria for VAMOS allocation is satisfied
There is a Source MS fulfilling the rules described in slide 32, either at call establishment
phase or subject to intra-cell HO cause 35
The last AV_RXLEV_DL_VAMOS_PAIRING of the Source MS > RXLEV_DL_MIN_VAMOS_PAIRING
EN_VAMOS_NON_AMR parameter is set to enabled or the Source MS will use an AMR codec
A source MS at call establishment phase is candidate for VAMOS allocation only if
EN_VAMOS_NASS = TRUE and RTCH request is not put in queue

Once the user pairing algorithm is triggered, it starts looking for a suitable
Target_MS => steps described in the next slide
47
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

VAMOS RADIO ALLOCATION STRATEGY


VAMOS PAIRING PROCESS DESCRIPTION (2/2)

48
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

VAMOS RADIO ALLOCATION STRATEGY


INITIAL SCPIR COMPUTATION
(1/2)
SCPIR is set according to the MS capabilities and radio conditions
For a (legacy SAIC, legacy SAIC) pair, when the parameter
EN_SAIC_SCPIR_MODIF is set to False, then DL SCPIR shall remain at 0 dB
Given that MS1 is allocated on VAMOS sub-channel1 & MS2 on sub-channel2
Case 1: DELTA_SCPIR_VAMOS_PAIRING > 0 => Initial DL SCPIR (MS1, MS2) is
computed as follows:
Initial SCPIR
SCPIRhigh
L1 = last AV_RXLEV_DL_VAMOS_PAIRING value
of the user to be allocated in subchannel#1
L2 = last AV_RXLEV_DL_VAMOS_PAIRING value
of the user to be allocated in the subchannel#2

SCPIRlow + (SCPIRhigh-SCPIRlow)/2

DELTA = DELTA_SCPIR_VAMOS_PAIRING

SCPIRlow
L2 L1
SCPIRlow DELTA

SCPIRlow

SCPIRlow + (SCPIRhigh SCPIRlow)/2

SCPIRhigh

49
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

SCPIRhigh + DELTA

VAMOS RADIO ALLOCATION STRATEGY


INITIAL SCPIR COMPUTATION
(2/2)
Case 2: DELTA_SCPIR_VAMOS_PAIRING 0 => Initial DL SCPIR (MS1, MS2) is
equal to L2-L1

L1 = last AV_RXLEV_DL_VAMOS_PAIRING value of


the user to be allocated in subchannel#1

Initial SCPIR

L2 = last AV_RXLEV_DL_VAMOS_PAIRING value of


the user to be allocated in the subchannel#2
SCPIRhigh + DELTA

DELTA = DELTA_SCPIR_VAMOS_PAIRING
SCPIRlow + (SCPIRhighSCPIRlow)/2

SCPIRlow - DELTA

L2 L1
SCPIRlow

SCPIRlow DELTA

SCPIRlow +
(SCPIRhigh SCPIRlow)/2

50
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

SCPIRhigh +
DELTA

SCPIRhigh

VAMOS RADIO ALLOCATION STRATEGY


INITIAL POWER COMPUTATION OF SOURCE MS
VAMOS pairing @ intra-cell handover: The MS power of the handed-over MS
(the Source MS) shall be kept equal to the last used value
VAMOS pairing @ call establishment: The BSS uses the difference between
the AV_RXLEV_DL_VAMOS_PAIRING averaged measurements, used to compute
the initial DL SCPIR, to compute the initial MS power of the Source MS:
Initial MS_power of Source MS = Roundup ( MS_power [Target MS] +
(AV_RXLEV_DL_VAMOS_PAIRING [Target MS]
AV_RXLEV_DL_VAMOS_PAIRING [Source MS]) )

Target MS keeps its power equal to the last used value when it is VAMOS-paired,
it can be changed later-on based on UL power control mechanisms

51
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

1 | VAMOS TECHNICAL DESCRIPTION


1.4 | NEW HO CAUSES IN VAMOS

52
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

NEW HO CAUSES IN VAMOS


VAMOS UNPAIRING HO (CAUSE 34)
Occurs due to too bad radio quality for a VAMOS subchannel, leading to intra-cell
handover of one of the paired users from a VAMOS channel to another channel
(either VAMOS or non-VAMOS) when EN_VAMOS_UNPAIRING_CA = TRUE
The codec type (FR, HR) remains the same after unpairing
Condition: For one user of the VAMOS pair,
AV_RXQUAL_DL_VAMOS_UNPAIRING > RXQUAL_DL_MIN_VAMOS_UNPAIRING, or
AV_RXLEV_DL_VAMOS_UNPAIRING < RXLEV_DL_MAX_VAMOS_UNPAIRING
New window sizes: A_LEV_VAMOS_UNPAIRING & A_QUAL_VAMOS_UNPAIRING

Result: Only one user of the VAMOS pair is handed-over: the one reporting better quality
and/or higher signal level measurements (to avoid call drop/HO failure of the user suffering
from bad radio conditions)
Benefits on the remaining user: higher transmit power in GSMK and no more co-channel
interference from the paired user
If both paired MSs fulfill the unpairing conditions, with similar RxQual/RxLev average
measurements, the user on sub-channel 2 is handed-over to another channel
When the MS is unpaired and allocated on a non-VAMOS channel, then the timer
MIN_TIME_BTW_VAMOS_PAIRING is launched to define the frequency by which HOP
shall try a VAMOS pairing algorithm on that MS
53
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

NEW HO CAUSES IN VAMOS


VAMOS PAIRING HO (CAUSE 35)
Occurs in case of high signal level and high load for VAMOS pairing, leading to
intra-cell handover of one user from a non-VAMOS channel to a VAMOS channel
The codec type (FR or HR) remains the same after pairing
Concerns the MSs allocated to a non-VAMOS channel, when all the below
conditions are fulfilled:
EN_VAMOS_PAIRING_CA = TRUE
AV_RXLEV_DL_VAMOS_PAIRING > RXLEV_DL_MIN_VAMOS_PAIRING
Cell load conditions for VAMOS allocation are fulfilled
The timer MIN_TIME_BTW_VAMOS_PAIRING has expired for that MS
Averaging window sizes: A_LEV_VAMOS_PAIRING & A_QUAL_VAMOS_PAIRING

If that Source_MS cannot be allocated on a VAMOS subchannel because no


suitable Target MS can be found, this MS keeps its current non-VAMOS channel
and the timer MIN_TIME_BTW_VAMOS_PAIRING is launched for this MS (to avoid
triggering this HO cause immediately for that MS)
54
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

NEW HO CAUSES IN VAMOS


OTHER HO CAUSES
All the B11 HO causes will apply also to VAMOS-paired MSs
Only Fast Traffic HO (cause 28) is impacted by VAMOS:
A resource allocated in VAMOS mode is not candidate for Fast Traffic HO to another cell,
because a queued request cannot be allocated in VAMOS mode
A MS included in the Target MSs list is not candidate for Fast Traffic HO

It is not planned to define a specific intra-cell HO just to change the TSC of an


existing user
HO cause priorities:
A VAMOS unpairing handover cause 34 has a higher priority than the HR-to-FR channel
adaptation cause 26 and emergency intra-cell interference HOs (cause 15 & 16)
A VAMOS pairing handover cause 35 has a lower priority than the FR-to-HR channel
adaptation cause 27 (to allow a FR call to be allocated in a non-VAMOS HR channel if such
channel is available) and PBGT HO cause 12
Emergency HO causes 27 have higher priority than VAMOS intra-cell HO cause 34, but
the trigger condition of cause 34 might be usually reached before causes 4 & 5 (due to
shorter averaging window size and lower threshold values for cause 34)
55
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

NEW HO CAUSES IN VAMOS


INTERACTION BETWEEN DIFFERENT HO CAUSES
Example: A FR call started in non-VAMOS mode, assuming a user in mobility on
a highway between 2 sites with the below Avg_RxLev/Traffic_load relationship
AV_DLRxLev
-45 dBm

Call started: Non-VAMOS channel


(Load condition not fulfilled)

Intra-cell HO cause 35
Possible VAMOS pairing
HO 35 in the new cell

RXLEV_DL_MIN_VAMOS_PAIRING

RXLEV_DL_MAX_VAMOS_UNPAIRING
L_RXLEV_DL_H

VAMOS unpairing HO cause 34


(bad signal strength)
Inter-cell HO cause 5

-110 dBm

AV_LOAD
THR_FR_LOAD_U_VAMOS_FR

Note: Different averaging window size for VAMOS pairing, unpairing and emergency HO
56
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

1 | VAMOS TECHNICAL DESCRIPTION


1.5 | POWER CONTROL STRATEGY

57
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

VAMOS POWER CONTROL STRATEGY


POWER CONTROL APPROACH
Power Control handles the adaptive control of RF transmit power of the MS & BTS
Goals:
Minimize the co-channel interference
Reduce the DC power consumption of the BTS and MS

VAMOS power control is based on RxQual & RxLev averaged measurements


Initial SCPIR having been optimally chosen during VAMOS pairing phase (based on MS
capabilities of paired users), SCPIR is then changed reactively based on RxQual values:
In case of RXQUAL degradation experienced by a VAMOS user, the VAMOS DL Power
Control process will react increasing its power level with respect to the power level of the
paired VAMOS user by modifying the SCPIR to favor the degraded user
The operator can choose different SCPIR constraints SCPIR_LOW_MS_PC_xxx for
VAMOS Power Control algorithm than the SCPIR constraints of the VAMOS Radio Allocation
procedure SCPIR_LOW_MS_ALLOC_xxx
e.g. very strict SCPIR constraints for the radio allocation procedure to minimize unpairing
possibilities - and smoother constraints for the power control algorithm with reactive SCPIR
update based on RxQual
58
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

VAMOS POWER CONTROL STRATEGY


RECALL OF NON-VAMOS POWER CONTROL
Power decrease happens when:
Too good quality & fair signal level: Average Quality < U_RXQUAL_xL_P AND
Average Rxlev >= L_RXLEV_xL_P + POW_RED_STEP_SIZE or,
Too good level & fair quality: Average Rxlev > U_RXLEV_xL_P AND
U_RXQUAL_xL_P Average Quality < L_RXQUAL_xL_P + OFFSET_HOPPING_PC
RXQUAL
0

Power increase happens when:


Average Quality > L_RXQUAL_xL_P +
OFFSET_HOPPING_PC (*)
Or

1
U_RXQUAL_UL_P
2

Power increase
PC-3

3
4
L_RXQUAL_UL_P

No
PC
r
e
q
u
i
r
e
d

Power decrease
PC-2

Power decrease
PC-4

Average Quality <= L_RXQUAL_xL_P +


OFFSET_HOPPING_PC (*) AND
Average Rxlev < L_RXLEV_xL_P

Power increase
PC-1

6
7

10
20
40
0
30
50
L_RXLEV_UL_P
U_RXLEV_UL_P
L_RXLEV_UL_P + POW_RED_STEP_SIZE

(*) only in hopping channels


59

COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.


ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

60

RXLEV

VAMOS POWER CONTROL STRATEGY


VAMOS DL POWER CONTROL
3 zones are identified depending on the averaged RXQUAL and RXLEV values:
0

Zone A: bad quality


or/and low level
Zone B: good quality
and good level
Zone C: good quality
and too high level

Bi

L_RXQUAL_DL_P_VAMOS

i = 1 or 2 (VAMOS
subchannel number)

Ai

7
RXQUAL_i

Ci

RXLEV_i
L_RXLEV_DL_P_VAMOS

U_RXLEV_DL_P_VAMOS

In VAMOS mode, L_RXLEV_DL_P_VAMOS, U_RXLEV_DL_P_VAMOS and


L_RXQUAL_DL_P_VAMOS replace L_RXLEV_DL_P, U_RXLEV_DL_P and
L_RXQUAL_DL_P respectively
For simplicity, the parameter U_RXQUAL_DL_P is not supported by the VAMOS DL PC
process (i.e. no differentiation between PC-2 & PC-4 zones of previous slide)
New averaging window size parameters are defined for VAMOS: A_LEV_PC_VAMOS &
A_QUAL_PC_VAMOS to allow more reactivity to radio condition variations than B11 PC
60
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

VAMOS POWER CONTROL STRATEGY


VAMOS DL POWER CONTROL - RULES

The BTS cannot transmit with a power higher than powermax_AQPSK

AQPSK power increase is performed when at least one user is in the zone A (but only if
the constraint on the maximum transmitted power allows it)

AQPSK power decrease is performed when at least one user is in the zone C (but only
if the other user is not in the zone A)

Power increase/decrease is applied to both users of the VAMOS pair, since there is only
1 physical AQPSK power

No VAMOS Power Control when both users are in the zone B

SCPIR modification

SCPIR modification without AQPSK power modification stands for a modification of the
power ratio between the users while keeping a constant AQPSK power level

SCPIR modification is always performed when the 2 users are in different zones
(except when the new SCPIR value would be out of the allowed range) to favor a user in
the zone A and/or to penalize a user in the zone C. The SCPIR modification can be
performed on top of the AQPSK power increase /decrease when one user is in the zone A
or C

For a (legacy SAIC, legacy SAIC) pair, when EN_SAIC_SCPIR_MODIF = False, then
the DL SCPIR value is fixed to 0dB and only the AQPSK power can be modified
61
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

VAMOS POWER CONTROL STRATEGY


VAMOS DL POWER CONTROL COMMANDS (1/2)
1. PC_COMMAND (BS, INC, BS_P_INC, < powermax):
Increase BS_TXPWR_1 and BS_TXPWR_2 by min (BS_P_INC, MAX_POW_INC_VAMOS,
powermax - BS_TXPWR), where BS_P_INC = max (BS_P_INC_1, BS_P_INC_2)
BS_P_INC_i is evaluated using the same approach as in non-VAMOS case:
If (AV_RXLEV_DL_PC_VAMOS_i < L_RXLEV_DL_P_VAMOS) (Signal strength problem)
If (AV_RXQUAL_DL_PC_VAMOS_i L_RXQUAL_DL_P(_AMR_RxACCH)_VAMOS +
OFFSET_RXQUAL_FH) (good quality)
then BS_P_INC_i = roundup [POW_INC_FACTOR_VAMOS x
(TARGET_RXLEV_DL - AV_RXLEV_DL_PC_VAMOS_i)]
Else BS_P_INC_i = roundup [MAX (POW_INC_FACTOR_VAMOS x
(TARGET_RXLEV_DL - AV_RXLEV_DL_PC_VAMOS_i), POW_INC_STEP_SIZE_VAMOS)]
Else (Quality problem)
BS_P_INC_i = POW_INC_STEP_SIZE_VAMOS
TARGET_RXLEV_DL = (U_RXLEV_DL_P_VAMOS + L_RXLEV_DL_P_VAMOS)/2
62
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

VAMOS POWER CONTROL STRATEGY


VAMOS DL POWER CONTROL COMMANDS (2/2)
2. PC_COMMAND (BS, RED, BS_P_RED, > powermin):
Decrease BS_TXPWR_1 and BS_TXPWR_2 by min (BS_P_RED, MAX_POW_RED_VAMOS,
BS_TXPWR powermin) where BS_P_RED = min (BS_P_RED_1, BS_P_RED_2)
BS_P_RED_i is evaluated using the same approach as in non-VAMOS case:
If (AV_RXLEV_DL_PC_VAMOS_i > U_RXLEV_DL_P_VAMOS)
Then BS_P_RED_i = rounddown [MAX (POW_RED_FACTOR_VAMOS x
(AV_RXLEV_DL_PC_VAMOS_i - TARGET_RXLEV_DL), POW_RED_STEP_SIZE_VAMOS)]
Else BS_P_RED_i = POW_RED_STEP_SIZE_VAMOS

3. PC_COMMAND (SCPIR, INC, SCPIR_MODIF_STEP_SIZE, <= SCPIRhigh_PC):


SCPIRnew = MIN (SCPIRold + SCPIR_MODIF_STEP_SIZE, SCPIRhigh_PC) keeping same BS_TXPWR
SCPIRhigh_PC is equal to SCPIR_LOW_MS_PC_xxx where xxx is the MS capability of MS2

4. PC_COMMAND (SCPIR, RED, SCPIR_MODIF_STEP_SIZE, >= SCPIRlow_PC):


SCPIRnew = MAX (SCPIRold SCPIR_MODIF_STEP_SIZE, SCPIRlow_PC) keeping same BS_TXPWR
63
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

VAMOS POWER CONTROL STRATEGY


VAMOS DL POWER CONTROL CAUSES (1/3)
1. Too bad quality or/and too low level for both users (PC-A1A2):
Both user powers shall be increased without modifying the SCPIR
=> PC_COMMAND (BS, INC, BS_P_INC, < powermax_AQPSK)
2. Too bad quality or/and too low level for user1 & good quality/level for user2
(PC-A1B2):
Both user powers are increased and then the SCPIR is increased to favor user 1
=> PC_COMMAND (BS, INC, BS_P_INC, <powermax_AQPSK)
and PC_COMMAND (SCPIR, INC, SCPIR_MODIF_STEP_SIZE, <= SCPIRhigh_PC)
3. Too bad quality or/and too low level for user1 & too high level for user2
(PC-A1C2):
Both user powers are increased and then the SCPIR is increased to favor user 1
=> PC_COMMAND (BS, INC, BS_P_INC, <powermax_AQPSK)
and PC_COMMAND (SCPIR, INC, SCPIR_MODIF_STEP_SIZE, <=SCPIRhigh_PC)
64
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

VAMOS POWER CONTROL STRATEGY


VAMOS DL POWER CONTROL CAUSES (2/3)
4. Good quality and level for user1 & too bad quality or/and too low level for user2
(PC-B1A2):
Both user powers are increased and then the SCPIR is increased to favor user 2
=> PC_COMMAND (BS, INC, BS_P_INC, <powermax_AQPSK)
and PC_COMMAND (SCPIR, RED, SCPIR_MODIF_STEP_SIZE, >= SCPIRlow_PC)
5. Good quality and level for both users (PC-B1B2):
No power control is applied
6. Good quality/level for user1 & too high level for user2 (PC-B1C2):
Both user powers are decreased and then the SCPIR is increased to favor user 1
=> PC_COMMAND (BS, RED, BS_P_RED, > BS_TXPWR_MIN)
and PC_COMMAND (SCPIR, INC, SCPIR_MODIF_STEP_SIZE, <= SCPIRhigh_PC)

65
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

VAMOS POWER CONTROL STRATEGY


VAMOS DL POWER CONTROL CAUSES (3/3)
7. Too high level for user1 & too bad quality or/and too low level for user2
(PC-C1A2):
Both user powers are increased and then the SCPIR is reduced to favor user 2
=> PC_COMMAND (BS, INC, BS_P_INC, <powermax_AQPSK)
and PC_COMMAND (SCPIR, RED, SCPIR_MODIF_STEP_SIZE, >= SCPIRlow_PC)
8. Too high level for user1 & good quality/level for user2 (PC-C1B2):
Both user powers are decreased and then the SCPIR is reduced to favor user 2
=> PC_COMMAND (BS, RED, BS_P_RED, > BS_TXPWR_MIN)
and PC_COMMAND (SCPIR, RED, SCPIR_MODIF_STEP_SIZE, >= SCPIRlow_PC)
9. Too high level for both users (PC-C1C2):
Both user powers shall be decreased
=> PC_COMMAND (BS, RED, BS_P_RED, > BS_TXPWR_MIN)
66
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

VAMOS POWER CONTROL STRATEGY


VAMOS DL POWER CONTROL GENERAL HINTS
At VAMOS pairing/unpairing, the BSC stops the BS PC algorithms for the paired MS
during a period defined by T_INHIBIT_VAMOS_PC, this timer guarantees that:
The BSC has enough time to receive the DL measurement results from both paired MSs
following VAMOS pairing
The BSC has enough time to receive the first DL measurement results in non-VAMOS mode
performed by the remaining MS, following VAMOS unpairing

When DL DTX is enabled, during a speech pause of one of the paired users,
legacy GMSK is used for the other user if it is in a speech period; while AQPSK
must be used when SID frames are transmitted
Those GMSK bursts are transmitted with the power level computed by the BSC as if they
were AQPSK bursts

When a SACCH/FACCH frame for one user in a VAMOS pair is multiplexed with a
TCH frame for the paired user (e.g. shifted SACCH technique is used, valid for
VAMOS-L2 using TSC set2), the BTS modifies the SCPIR to favor the user
transmitting the FACCH/SACCH frame. This SCPIR modification shall be equal to
the SCPIR_MODIF_VAMOS_CCCH parameter value
67
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

VAMOS POWER CONTROL STRATEGY


VAMOS UL POWER CONTROL (1/2)
Goal: Reach an ideal UL signal level detected in the BTS, allowing correct signal decoding
Measured UL RXLEV in VAMOS mode: is the total received signal (subchannel#1 +

subchannel#2) measured at the antenna connector => The 2 UL RXLEV values will be equal,
the BTS cant measure a different UL RXLEV value for each of the 2 VAMOS subchannels.
The MS Power Control commands in VAMOS mode are based on the UL RXQUAL
measurements for each of the 2 GMSK signals and on the total received signal

Approach: In order to avoid an increase of UL interference in the network, UL PC process


tries to have the same level for the 2 UL VAMOS signals, even if the BTS cannot measure it.
Then, to react to bad RxQual of one of the 2 MSs, increasing the MS power should be
controlled in order to keep the difference between the 2 UL VAMOS signals within a specific
range (otherwise, decoding of one of these signals will become impossible). Thus, if the
maximum allowed MS power difference is reached with still bad UL_RXQUAL of one user, the
BSS shall stop increasing the MS power and trigger a handover.

How: For simplicity, it is assumed that DL path loss is similar to UL path loss (i.e., the
requested difference between MS1 & MS2 UL transmitted powers should be similar to
DELTA_DLRXLEV):
DELTA_DLRXLEV = [AV_RXLEV_DL_PC_VAMOS_2 AV_RXLEV_DL_PC_VAMOS_1]
68
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

VAMOS POWER CONTROL STRATEGY


VAMOS UL POWER CONTROL (2/2)
How (cont.):
Whenever MS Power Control algorithm implies a modification of MS_TXPWR_1 and/or
MS_TXPWR_2, the BSC applies the below rule:
MS_TXPWR_1 - MS_TXPWR_2 should be in the range:
[DELTA_DLRXLEV - UL_VAMOS_PC_CORRECTION_FACTOR, DELTA_DLRXLEV +
UL_VAMOS_PC_CORRECTION_FACTOR]
DELTA_DLRXLEV = AV_RXLEV_DL_PC_VAMOS_2 AV_RXLEV_DL_PC_VAMOS_1
UL_VAMOS_PC_CORRECTION_FACTOR is a correction factor to introduce some flexibility,

taking into account the fact that this rule is based on a simplification and that the BTS
has better decoding capabilities than a MS. Its value is a tradeoff between interference
and unpairing probability: A low value reduces the allowed range in MS power difference
but increases unpairing probability

Similar to the BS PC process, the T_INHIBIT_VAMOS_PC timer is used to stop the MS Power
Control process during a VAMOS pairing and a VAMOS unpairing
2 new parameters are used by UL PC process in VAMOS mode: L_RXLEV_UL_P_VAMOS &
U_RXLEV_UL_P_VAMOS. Their default value are 3dB higher than the default values of
L_RXLEV_UL_P & U_RXLEV_UL_P respectively (since the measured UL signal is the sum of
both subchannels)
69
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

1 | VAMOS TECHNICAL DESCRIPTION


1.6 | SAIC MS ISSUES IN VAMOS MODE

70
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

SAIC MS ISSUES IN VAMOS MODE


NOTIFICATION ISSUE
(1/2)
SAIC capability is release independent, indicated by MS CLASSMARK3
Information Element (IE)
Problem description: Some mobile dont report their real voice SAIC capability
As SAIC performance requirements are more complex for data services than voice services,
many SAIC mobiles are designed to cope with SAIC voice requirements but not for data
Consequence: Such MSs dont declare themselves as SAIC-capable in Classmark3 IE
=> Wrong information acquired by the BSS about the SAIC capabilities for voice services
=> These MSs are managed as non-SAIC MSs!
=> Thus, they cant be paired to SAIC or VAMOS-1 MSs but only to VAMOS-2 MSs (i.e. less
chances to be paired, restricted SCPIR range and increased interference probability)

This notification issue is present in most Nokia SAIC handsets as well as SAIC
mobiles based on Qualcomm chipsets
ALU workaround: Test those non-SAIC MSs already having a call established in nonVAMOS mode (and present in Target MSs list) by sending AQPSK bursts - during four 26frame multiframes (4x120ms) - superposed to the information intended to the MS
71
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

SAIC MS ISSUES IN VAMOS MODE


NOTIFICATION ISSUE
(2/2)
ALU workaround (cont.):
Accordingly, an MS cannot be directly allocated a VAMOS channel at TCH establishment
even if load condition is fulfilled, but it can be inserted into Target MSs list and marked as
To be tested

MS

BSC

BTS

Normal GMSK bursts


Cell load >= LOAD_VAMOS_FR
threshold
Normal burst

Dummy burst

1 message for
each To be
tested mobile

Test MS

AQPSK bursts (1 SACCH mf)

Check RxQual_DL in the 4


consecutive reporting periods:
- Any RxQual >= 6?
=> Non SAIC MS

Meas. report
Meas. report
Meas. report
Meas. report

- Otherwise, SAIC MS

[Back]
72
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

SAIC MS ISSUES IN VAMOS MODE


PERFORMANCE ISSUE
Some SAIC mobiles (Nokia, Qualcomm-based, some blackberries) suffer
from bad performance in VAMOS mode:
Call drop after several minutes
Such mobiles require SCPIR > 0, otherwise, RxQual will degrade gradually until
call drop
SAIC-VAMOS1
pair, SCPIR = 0

According to Nokia, SCPIR = 0 + DL DTX activation can minimize the issue in


parallel with more reactive Power Control settings
A solution based on a black-list of "substandard SAIC MSs" is under evaluation
73
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

SAIC MS ISSUES IN VAMOS MODE


PERFORMANCE ISSUE
ALU recommendation:
DL DTX activation is mandatory
SCPIR_LOW_MS_ALLOC_SAIC default value = -2 => allows fast recovery of RxQual
degradation in case of bugged SAIC mobile
SCPIR_LOW_MS_PC_SAIC default value = -4 => to exploit the full SCPIR range of nonbugged SAIC mobiles, BUT it still could be risky for bugged mobiles (to be confirmed by
ALU tests)

74
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

CONTENTS
1 | FEATURE DESCRIPTION
2 | FEATURE ACTIVATION STRATEGY
3 | TEST STRATEGY
4 | PERFORMANCE EVALUATION
5 | RESTRICTIONS / OTHER ISSUES
6 | CONCLUSION
7 | APPENDIX A: VAMOS SUITABILITY EVALUATION
8 | APPENDIX B: VAMOS SIMULATION RESULTS
9 | APPENDIX C: VAMOS DEPENDENCIES - BSSoIP
75
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

2 | FEATURE ACTIVATION STRATEGY


2.1 | VAMOS ACTIVATION

76
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

FEATURE ACTIVATION STRATEGY


VAMOS Activation

This feature is activated at cell level

The feature can be activated through the EN_VAMOS telecom parameter

EN_VAMOS= 0 or 1 / 0 (disabled)

VAMOS can be allowed at the following mobile stations levels through a set of 8
telecom parameters:
1. For the Legacy non-SAIC VAMOS Level 1 pairs: EN_PAIRING_NON_SAIC_VAMOS1
2. For the Legacy non-SAIC VAMOS Level 2 pairs: EN_PAIRING_NON_SAIC_VAMOS2
3. For the Legacy SAIC Legacy SAIC pairs: EN_PAIRING_SAIC_SAIC
4. For the Legacy SAIC VAMOS Level 1 pairs: EN_PAIRING_SAIC_VAMOS1
5. For the Legacy SAIC VAMOS Level 2 pairs: EN_PAIRING_SAIC_VAMOS2
6. For the VAMOS Level 1 VAMOS Level 1 pairs: EN_PAIRING_VAMOS1_VAMOS1
7. For the VAMOS Level 1 VAMOS Level 2 pairs: EN_PAIRING_VAMOS1_VAMOS2
8. For the VAMOS Level 2 VAMOS Level 2 pairs: EN_PAIRING_VAMOS2_VAMOS2
77
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

FEATURE ACTIVATION STRATEGY


VAMOS Activation
Feature optionality
The VAMOS feature is optional for the network.
Sold by counting the number of TRX

Feature availability
This feature is available starting with B12.1 release

Feature recommendations:
In B12 ALU BSS VAMOS will be allowed in IP transport only (IPoEth or IPoE1)
The following features should be enable (but not mandatory) in order to enhance VAMOS
operation:
DTX
Repeated SACCH/FACCH
AMR
DL Power Control
78
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

2 | FEATURE ACTIVATION STRATEGY


2.2 | HW SUPPORT

79
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

FEATURE ACTIVATION STRATEGY


HW Support
The following is required by product management for hardware
support:
BTS: A9100 (EVOLIUM standard) and SUMA and SUMX
SUMP, A9110-E (M5M), A9110 (M4M) dont support VAMOS operation

TRE: G5 TRE (TWIN) and G6 TRE(MC-TRE and MC-RRH)


G3(GPRS only) & G4(GPRS & EDGE) TRX dont support VAMOS operation

BSC generation: Evolution BSC (Mx) with TPV1/TPV3


G2 BSC doesnt support VAMOS operation

TC: TRAU G2.5 (with MT120) or (with MT120-WB)


TRAU G2(MT120/DT16) doesnt support VAMOS operation

O&M: OMC-R and NPO


POLO and OEF dont support VAMOS operation

MFS: not impacted


80
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

FEATURE ACTIVATION STRATEGY


HW Support
MC_Module compatibility:
The number of TRX supporting VAMOS on a MC-Module is limited due to
processing issues, DSP capacity in the BTS.
This limitation is managed in a static way. BTS gives to the BSC the VAMOS
capability for every TRX. This information is an input for TRX/RSL mapping and
resource allocation.

Cell Topology compatibility:


VAMOS is supported on all cell topologies

81
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

2 | FEATURE ACTIVATION STRATEGY


2.3 | NEW VAMOS PARAMETERS

82
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

FEATURE ACTIVATION STRATEGY


NEW VAMOS TELECOM PARAMETERS (1/12)
Parameter
Name

Definition

SubSystem

Insta
nce

Category/
OMC-R
access

Type

Range/
Default
value

BSC

Cell

Site (CAE)/
Changeable

Flag

0 or 1 / 0
(disabled)

EN_VAMOS

Enables / disables VAMOS in the cell

EN_PAIRING_
NON_SAIC_VA
MOS1

When VAMOS is activated, enables or disables


pairing between Non-SAIC and VAMOS1 MSs

BSC

Cell

Site (CAE)/
Changeable

Flag

0 or 1 / 0
(disabled)

EN_PAIRING_
NON_SAIC_VA
MOS2

When VAMOS is activated, enables or disables


pairing between Non-SAIC and VAMOS2 MSs

BSC

Cell

Site (CAE)/
Changeable

Flag

0 or 1 / 1
(enabled)

EN_PAIRING_
SAIC_SAIC

When VAMOS is activated, enables/ disables


pairing between SAIC MSs

BSC

Cell

Site (CAE)/
Changeable

Flag

0 or 1 / 1
(enabled)

EN_PAIRING_
SAIC_VAMOS1

When VAMOS is activated, enables or disables


pairing between SAIC and VAMOS1 MSs

BSC

Cell

Site (CAE)/
Changeable

Flag

0 or 1 / 1
(enabled)

EN_PAIRING_
SAIC_VAMOS2

When VAMOS is activated, enables or disables


pairing between SAIC and VAMOS2 MSs

BSC

Cell

Site (CAE)/
Changeable

Flag

0 or 1 / 1
(enabled)

EN_PAIRING_
VAMOS1_VAM
OS1

When VAMOS is activated, enables or disables


pairing between VAMOS1 MSs

BSC

Cell

Site (CAE)/
Changeable

Flag

0 or 1 / 1
(enabled)

83
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

FEATURE ACTIVATION STRATEGY


NEW VAMOS TELECOM PARAMETERS (2/12)
Parameter
Name

SubInsta
Syste
nce
m

Definition

Category/
OMC-R
access

Type

Range/ Default
value

EN_PAIRING
_VAMOS1_V
AMOS2

When VAMOS is activated, enables or disables


pairing between VAMOS1 and VAMOS2 MS

BSC

Cell

Site (CAE)/
Changeable

Flag

0 or 1 /
1 (enabled)

EN_PAIRING
_VAMOS2_V
AMOS2

When VAMOS is activated, enables or disables


pairing between VAMOS2 MSs

BSC

Cell

Site (CAE)/
Changeable

Flag

0 or 1 /
1 (enabled)

EN_VAMOS_
NASS

When VAMOS is activated, enables or disables


pairing on Normal Assignment

BSC

Cell

Site (CAE)/
Changeable

Flag

0 or 1 /
1 (enabled)

EN_VAMOS_
NON_AMR

When VAMOS is activated, enables or disables


pairing of calls using non-AMR codecs

BSC

Cell

Site (CAE)/
Changeable

Flag

0 or 1 /
1 (enabled)

EN_SAIC_SC
PIR_MODIF

When VAMOS is activated and the pairing


between SAIC MSs is enabled, enables/disables
SCPIR values different from 0 dB

BSC

Cell

Site (CAE)/
Changeable

Flag

0 or 1 /
0 (disabled)

Enu
mer
ated

0: (0, 5)
1: (1, 7)
2: (2, 6)
3: (3, 4)
4: (4, 2)
5: (5, 1)
6: (6, 3)
7: (7, 0)
8 to 15: reserved

TSC_1_2

When VAMOS is activated, this parameter


represents the two Training Sequence Codes
(TSC_1, TSC_2) that can be used for any
circuit channel established in VAMOS mode;
TSC_1 is always used when a circuit channel is
established in Non-VAMOS mode

BSC

Cell

Site (CAE)/
Changeable

84
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

FEATURE ACTIVATION STRATEGY


NEW VAMOS TELECOM PARAMETERS (3/12)
Definition

SubSyste
m

Insta
nce

Category/
OMC-R
access

Type

Range/
Default
value

THR_FR_LOAD
_L_VAMOS_FR

Lower load threshold to accept VAMOS allocation


in FR

BSC

Cell

Site (CAE)/
Changeable

Thresho
ld

0 to 100
/ 100(%)

THR_FR_LOAD
_U_VAMOS_FR

Higher load threshold for VAMOS allocation in FR

BSC

Cell

Site (CAE)/
Changeable

Thresho
ld

0 to 100
/ 100(%)

THR_FR_LOAD
_L_VAMOS_HR

Lower load threshold to accept VAMOS allocation


in HR

BSC

Cell

Site (CAE)/
Changeable

Thresho
ld

0 to 100
/ 100(%)

THR_FR_LOAD
_U_VAMOS_HR

Higher load threshold for VAMOS allocation in HR

BSC

Cell

Site (CAE)/
Changeable

Thresho
ld

0 to 100
/ 100(%)

Parameter
Name

SCPIR_LOW_M
S_ALLOC_NON
_SAIC

Minimum value of SCPIR allowing a correct


decoding of the signal for a Legacy non-SAIC
capable MS, allocated to VAMOS sub-channel #1.
It is used by the resource allocation algorithm

BSC

Cell

Site (CAE)/
Changeable

Number

-10 to 10
/ 8 (dB)

SCPIR_LOW_M
S_ALLOC_SAIC

Minimum value of SCPIR allowing a correct


decoding of the signal for a Legacy SAIC capable
MS, allocated to the VAMOS sub-channel #1. It is
used by the resource allocation algorithm

BSC

Cell

Site (CAE)/
Changeable

Number

-10 to 10
/ -2 (dB)

SCPIR_LOW_M
S_ALLOC_VAM
OS1

Minimum value of SCPIR allowing a correct


decoding of the signal for a VAMOS-1 capable
MS, allocated to the VAMOS sub-channel #1. It is
used by the resource allocation algorithm

BSC

Cell

Site (CAE)/
Changeable

Number

-10 to 10
/ -4 (dB)

85
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

FEATURE ACTIVATION STRATEGY


NEW VAMOS TELECOM PARAMETERS (4/12)
Definition

SubSyste
m

Insta
nce

Category/
OMC-R
access

Type

Range/
Default
value

SCPIR_LOW_M
S_ALLOC_VAM
OS2

Minimum value of SCPIR allowing a correct


decoding of the signal for a VAMOS-2 capable
MS, allocated to the VAMOS sub-channel #1. It is
used by the resource allocation algorithm

BSC

Cell

Site (CAE)/
Changeable

Number

-10 to 10
/
-10(dB)

SCPIR_LOW_M
S_PC_NON_SAI
C

Minimum value of SCPIR allowing a correct


decoding of the signal for a Legacy non-SAIC
capable MS, allocated to the VAMOS sub-channel
#1. It is used by the power control algorithm

Cell

Site (CAE)/
Changeable

Number

-10 to 10
/
8 (dB)

SCPIR_LOW_M
S_PC_SAIC

Minimum value of SCPIR allowing a correct


decoding of the signal for a Legacy SAIC capable
MS, allocated to the VAMOS sub-channel #1. It is
used by the power control algorithm

BSC

Cell

Site (CAE)/
Changeable

Number

-10 to 10
/
-4 (dB)

SCPIR_LOW_M
S_PC_VAMOS1

Minimum value of SCPIR allowing a correct


decoding of the signal for a VAMOS-1 capable
MS, allocated to the VAMOS sub-channel #1. It is
used by the power control algorithm

BSC

Cell

Site (CAE)/
Changeable

Number

-10 to 10
/
-4 (dB)

SCPIR_LOW_M
S_PC_VAMOS2

Minimum value of SCPIR allowing a correct


decoding of the signal for a VAMOS-2 capable
MS, allocated to the VAMOS sub-channel #1. It is
used by the power control algorithm

BSC

Cell

Site (CAE)/
Changeable

Number

-10 to 10
/
-10(dB)

Parameter
Name

BSC

86
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

FEATURE ACTIVATION STRATEGY


NEW VAMOS TELECOM PARAMETERS (5/12)
Definition

SubSystem

Inst
ance

Category/
OMC-R
access

Type

Range/
Default
value

L_RXLEV_DL_P
_VAMOS

Lower DL level threshold for VAMOS BS


power control

BSC

Cell

Site
(CAE)/
Changeable

Threshold

-110 to 47
-85(dBm)

U_RXLEV_DL_P
_VAMOS

Upper DL level threshold for VAMOS BS


power control

Cell

Site
(CAE)/
Changeable

Threshold

-110 to 47
-75(dBm)

L_RXLEV_UL_P
_VAMOS

Lower uplink level threshold for VAMOS MS


power control

BSC

Cell

Site
(CAE)/
Changeable

Threshold

-110 to 47 / -87
(dBm)

U_RXLEV_UL_P
_VAMOS

Upper uplink level threshold for VAMOS MS


power control

BSC

Cell

Site
(CAE)/
Changeable

Threshold

-110 to 47 / -72
(dBm)

L_RXQUAL_DL
_P_VAMOS

Lower downlink quality threshold for


VAMOS power control (all VAMOS calls
except AMR-NB / AMR-WB ones where
repeated DL FACCH / SACCH are activated)

BSC

Cell

Site
(CAE)/
Changeable

Threshold

0 to 7 / 3

L_RXQUAL_DL
_P_AMR_RXAC
CH_VAMOS

Lower downlink quality threshold for


VAMOS power control for VAMOS calls with
AMR-NB / AMR-WB ones where repeated
DL FACCH / SACCH are activated)

BSC

Cell

Site
(CAE)/
Changeable

Threshold

0 to 7 / 3

Parameter
Name

BSC

87
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

FEATURE ACTIVATION STRATEGY


NEW VAMOS TELECOM PARAMETERS (6/12)
Parameter
Name

Definition

SubSystem

Inst
ance

Category/
OMC-R
access

Type

Range/
Default
value

MAX_POW_INC
_VAMOS

Maximum Power increase of a VAMOS subchannel in one power command

BSC

Cell

Site
(CAE)/
Changeable

Number

2 to 16 /
8 (dB)

MAX_POW_RE
D_VAMOS

Maximum Power decrease of a VAMOS


sub-channel in one power command

BSC

Cell

Site
(CAE)/
Changeable

Number

2 to 16 /
8 (dB)

POW_INC_FAC
TOR_VAMOS

VAMOS weighting factor for power increase

BSC

Cell

Site
(CAE)/
Changeable

Number

0 to 1 /
0.8

POW_INC_STE
P_SIZE_VAMO
S

Power increase step size of a VAMOS subchannel in case of power command


triggered on quality criterion

BSC

Cell

Site
(CAE)/
Changeable

Number

2 to 14 /
6 (dB)

POW_RED_FAC
TOR_VAMOS

VAMOS weighting
decrease

BSC

Cell

Site
(CAE)/
Changeable

Number

0 to 1 /
0.5

POW_RED_STE
P_SIZE_VAMO
S

Power reduction step size of a VAMOS subchannel in case of power command


triggered on quality criterion

BSC

Cell

Site
(CAE)/
Changeable

Number

2 to 4 /
2 (dB)

SCPIR_MODIF_
STEP_SIZE

SCPIR step size for increase or reduction

BSC

Cell

Site
(CAE)/
Changeable

Flag

0 to 20 /
2 (dB)

A_LEV_PC_VA
MOS

Window size for level average for VAMOS


PC

BSC

Cell

Site
(CAE)/
Changeable

Number

1 to 31 /
4

factor

for

power

88
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

FEATURE ACTIVATION STRATEGY


NEW VAMOS TELECOM PARAMETERS (7/12)
Parameter
Name

Definition

SubSystem

Inst
ance

Category/
OMC-R
access

Type

Range/
Default
value

W_LEV_PC_VA
MOS

Weight applicable to level samples for


VAMOS power control when no DTX is
applied

BSC

Cell

Site
(CAE)/
Changeable

Number

1 to 3 / 1

A_QUAL_PC_V
AMOS

Window size for quality average for VAMOS


PC

BSC

Cell

Site
(CAE)/
Changeable

Number

1 to 31 /
4

W_QUAL_PC_V
AMOS

Weight applicable to quality samples for


VAMOS power control when no DTX is
applied

BSC

Cell

Site
(CAE)/
Changeable

Number

1 to 3 / 1

A_LEV_
VAMOS_PAIRI
NG

Window size for level average for VAMOS


pairing

BSC

Cell

Site
(CAE)/
Changeable

Number

1 to 31 /
5

A_LEV_
VAMOS_UNPAI
RING

Window size for level average for VAMOS


unpairing

BSC

Cell

Site
(CAE)/
Changeable

Number

1 to 31 /
3

A_QUAL_
VAMOS_PAIRI
NG

Window size for quality average for VAMOS


pairing

BSC

Cell

Site
(CAE)/
Changeable

Number

1 to 31 /
5

A_QUAL_
VAMOS_UNPAI
RING

Window size for quality average for VAMOS


unpairing

BSC

Cell

Site
(CAE)/
Changeable

Number

1 to 31 /
3

89
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

FEATURE ACTIVATION STRATEGY


NEW VAMOS TELECOM PARAMETERS (8/12)
Inst
ance

Category/
OMC-R
access

BSC

Maximum averaged quality value allowing


VAMOS pairing

DELTA_SCPIR_
VAMOS_PAIRI
NG

Maximum deviation on the difference


between averaged level values of two MSs
allowing them to be VAMOS-paired on the
same TCH

RXLEV_DL_MA
X_VAMOS_UNP
AIRING

Maximum averaged level value allowing


VAMOS unpairing

RXQUAL_DL_M
IN_VAMOS_UN
PAIRING

Minimum averaged quality value allowing


VAMOS unpairing

MIN_TIME_BT
W_VAMOS_PAI
RING

Minimum time to wait for a CS call before a


new pairing attempt after a failed pairing
attempt or after an unpairing

Parameter
Name

Definition

RXLEV_DL_MI
N_VAMOS_PAI
RING

Minimum averaged level value allowing


VAMOS pairing

RXQUAL_DL_M
AX_VAMOS_PA
IRING

Type

Range/
Default
value

Cell

Site
(CAE)/
Changeable

Threshold

-110 to 17 /
75 (dBm)

BSC

Cell

Site
(CAE)/
Changeable

Threshold

0 to 7 / 1

BSC

Cell

Site
(CAE)/
Changeable

Number

-10 to 10
/ 0 (dB)

BSC

Cell

Site
(CAE)/
Changeable

Threshold

-110 to 47 / 90 (dBm)

BSC

Cell

Site
(CAE)/
Changeable

Threshold

0 to 7 / 4

BSC

Cell

Site
(CAE)/
Changeable

Timer

1 to 10 /
1
(second)

SubSystem

90
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

FEATURE ACTIVATION STRATEGY


NEW VAMOS TELECOM PARAMETERS (9/12)
Definition

SubSystem

Inst
ance

Category/
OMC-R
access

Type

Range/
Default
value

W_LEV_
VAMOS_PAIRI
NG

Weight applicable to level samples for


VAMOS pairing when DTX is disabled or
when DTX is enabled and no silence period
is present in the multiframe

BSC

Cell

Site
(CAE)/
Changeable

Number

1 to 3 / 1

W_QUAL_
VAMOS_PAIRI
NG

Weight applicable to quality samples for


VAMOS pairing when DTX is disabled or
when DTX is enabled and no silence period
is present

BSC

Cell

Site
(CAE)/
Changeable

Number

1 to 3 / 1

W_LEV_
VAMOS_UNPAI
RING

Weight applicable to level samples for


VAMOS unpairing when DTX is disabled or
when DTX is enabled and no silence period
is present

BSC

Cell

Site
(CAE)/
Changeable

Number

1 to 3 / 1

W_QUAL_
VAMOS_UNPAI
RING

Weight applicable to quality samples for


unpairing when DTX is disabled or when
DTX is enabled and no silence period is
present

BSC

Cell

Site
(CAE)/
Changeable

Number

1 to 3 / 1

SCPIR_MODIF_
VAMOS_CCCH

Power increase for FACCH and SACCH


frames

BSC

Cell

Site
(CAE)/
Changeable

Flag

0 to 4 / 0
[dB]

EN_TEST_FOR
_NON_SAIC

When VAMOS is activated, enable/disable


the transmission of AQPSK test bursts for
non-SAIC MSs

Cell

Site
(CAE)/
Changeable

Flag

0 or 1 / 0
(disabled
)

Parameter
Name

BSC

91
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

FEATURE ACTIVATION STRATEGY


NEW VAMOS TELECOM PARAMETERS (10/12)
Category/
OMC-R
access

Type

Range/
Default
value

Cell

Site (CAE)/
Changeable

Flag

0 or 1 / 1
(enabled)

BSC

Cell

Site (CAE)/
Changeable

Flag

0 or 1 / 1
(enabled)

BSC

Cell

Site (CAE)/
Changeable

Number

0 to 10 /
6 [dB]

Cell

Site (CAE)/
Changeable

Threshold

-10 to +10 /
8, 10,10
[dB]

BSC

Cell

Site (CAE)/
Changeable

Threshold

-10 to +10 /
8, 10,10
[dB]

BSC

Cell

Site (CAE)/
Changeable

Threshold

-10 to +10 /
-2, 0, 2
[dB]

Parameter
Name

SubInsta
System nce

Definition

EN_VAMOS_PA
IRING_CA

When VAMOS is activated, enable/disable


intracell HO for VAMOS pairing (cause 35)

BSC

EN_VAMOS_UN
PAIRING_CA

When VAMOS is activated, enable/disable


intracell HO for VAMOS unpairing (cause
34)

UL_VAMOS_PC
_CORRECTION
_FACTOR

Correction factor used to determine the


transmitted powers of the paired MSs from
the last computed DL RxLev value

SCPIR_NON_S
AIC_VAMOS1_
THR_1,...THR_
2,...THR_3

Limits of the band N for distribution of


SCPIR counters for (non-SAIC, VAMOS-1)
pairs

SCPIR_NON_S
AIC_VAMOS2_
THR_1,...THR_
2,...THR_3

Limits of the band N for distribution of


SCPIR counters for (non-SAIC, VAMOS-2)
pairs

SCPIR_SAIC_V
AMOS1_THR_1
...THR_2,...TH
R_3

Limits of the band N for distribution of


SCPIR counters for (SAIC, VAMOS-1) pairs

BSC

92
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

FEATURE ACTIVATION STRATEGY


NEW VAMOS TELECOM PARAMETERS (11/12)
Type

Range/
Default
value

Cell

Site (CAE)/
Changeable

Threshold

-10 to +10 /
-2, 2, 6
[dB]

BSC

Cell

Site (CAE)/
Changeable

Threshold

-10 to +10 /
-2, 0, 2 [dB]

Limits of the band N for distribution of


SCPIR counters for (VAMOS-1, VAMOS2) pairs

BSC

Cell

Site (CAE)/
Changeable

Threshold

-10 to +10 /
-2, 2, 6 [dB]

SCPIR_VAMOS2_V
AMOS1_THR_1,
...THR_2, ...THR_3

Limits of the band N for distribution of


SCPIR counters for (VAMOS-2, VAMOS1) pairs

BSC

Cell

Site (CAE)/
Changeable

Threshold

-10 to +10 /
-6, -2, 2
[dB]

SCPIR_VAMOS2_V
AMOS2_THR_1,
...THR_2, ...THR_3

Limits of the band N for distribution of


SCPIR counters for (VAMOS-2, VAMOS2) pairs

BSC

Cell

Site (CAE)/
Changeable

Threshold

-10 to +10 /
-4, 0, 4
[dB]

SCPIR_SAIC_SAIC
_THR1, THR_2,
THR_3

Limits of the band N for distribution of


SCPIR counters for (SAIC, SAIC) pairs

BSC

Cell

Site (CAE)/
Changeable

Threshold

-10 to +10 /
-2, 0, 2
[dB]

SubInsta
System nce

Parameter Name

Definition

SCPIR_SAIC_VAM
OS2_THR_1,...THR
_2,...THR_3

Limits of the band N for distribution of


SCPIR counters for (SAIC, VAMOS-2)
pairs

BSC

SCPIR_VAMOS1_V
AMOS1_THR_1,
...THR_2, ...THR_3

Limits of the band N for distribution of


SCPIR counters for (VAMOS-1, VAMOS1) pairs

SCPIR_VAMOS1_V
AMOS2_THR_1,
...THR_2, ...THR_3

Category/
OMC-R
access

93
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

FEATURE ACTIVATION STRATEGY


NEW VAMOS TELECOM PARAMETERS (12/12)
SubSystem

Instance

Category/
OMC-R access

Type

Range/
Default
value

List of
numbers

0x000000 to
0x666666 /
0x666261

Parameter Name

Definition

PAIRING_PRIORIT
IES_NON_SAIC

When VAMOS is activated,


configure the VAMOS pairing
priorities for a NON SAIC MS

BSC

BSC

Network(CDE)
+ none(DLS)

PAIRING_PRIORIT
IES_SAIC

When VAMOS is activated,


configure the VAMOS pairing
priorities for a SAIC MS

BSC

BSC

Network(CDE)
+ none(DLS)

List of
numbers

0x000000 to
0x666666 /
0x626163

PAIRING_PRIORIT
IES_VAMOS1

When VAMOS is activated,


configure the VAMOS pairing
priorities for a VAMOS1 MS

BSC

BSC

Network(CDE)
+ none(DLS)

List of
numbers

0x000000 to
0x666666 /
0x612345

PAIRING_PRIORIT
IES_VAMOS2

When VAMOS is activated,


configure the VAMOS pairing
priorities for a VAMOS2 MS

BSC

BSC

Network(CDE)
+ none(DLS)

List of
numbers

0x000000 to
0x666666 /
0x123456

Note: The selection of the allowed/forbidden VAMOS pairs is only done using the parameters
EN_PAIRING_xxx_yyy
94
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

2 | FEATURE ACTIVATION STRATEGY


2.4 | CHANGED VAMOS PARAMETERS

95
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

FEATURE ACTIVATION STRATEGY


CHANGED VAMOS TELECOM PARAMETERS (1/12)
Parameter
Name

Insta Category/
nce
OMC-R access

Type

Range/
Default
value

Definition

SubSystem

Window size for level averages for power


control. For uplink, it is applicable to both
VAMOS and non-VAMOS mode; for downlink,
to non-VAMOS mode only.

BSC

cell

Site
(CAE)/
Changeable

Numb
er

1 to 31/ 4

Window size for quality averages for power


control. For uplink, it is applicable to both
VAMOS and non-VAMOS mode; for downlink,
to non-VAMOS mode only.

BSC

cell

Site
(CAE)/
Changeable

Numb
er

1 to 31/ 4

BS_P_CON_AC
K

Supervision of the BS Power Control


procedure (used also by the VAMOS DL
power control).

BSC

cell

Site
(CAE)/
Changeable

Timer

0 to 31/ 3

BS_P_CON_IN
T

Minimum delay between two consecutive BS


power commands (used also by the VAMOS
DL power control).

BSC

cell

Site
(CAE)/
Changeable

Timer

0 to 31/ 1

ECSC

Indicates to the MS whether or not early


sending of CLASSMARK CHANGE is allowed.

BSC

BSS

System (CST)/
None (DLS)

Flag

A_LEV_PC

A_QUAL_PC

96
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

1 to 1 / 1

Before (0 to 1)

FEATURE ACTIVATION STRATEGY


CHANGED VAMOS TELECOM PARAMETERS (2/12)
Parameter
Name

SubSystem

Definition

Insta Category/
nce
OMC-R access

Type

Range/
Default
value

THR_FR_LOAD
_L_SV1

Lower load threshold for allocation policy


with HR or AMR-NB HR codec type in a dual
rate cell.
Mandatory Rule updated

BSC

cell

Site
(CAE)/
Changeable

Thres
hold

0 to 100 /
100

THR_FR_LOAD
_L_SV3

Lower load threshold for allocation policy


with AMR-NB HR codec type and for AMR-NB
channel adaptation handover (Cause 26 and
Cause 27) in a dual rate cell.
Mandatory Rule updated

BSC

cell

Site
(CAE)/
Changeable

Thres
hold

0 to 100 /
100

THR_FR_LOAD
_U_SV1

Higher load threshold for allocation policy


with HR or AMR-NB HR codec type in a dual
rate cell.
Mandatory Rule updated

BSC

cell

Site
(CAE)/
Changeable

Thres
hold

0 to 100 /
100

THR_FR_LOAD
_U_SV3

Higher load threshold for allocation policy


with AMR-NB HR codec type and for AMR-NB
channel adaptation handover (Cause 26 and
Cause 27) in a dual rate cell.
Mandatory Rule updated

BSC

cell

Site
(CAE)/
Changeable

Thres
hold

0 to 100 /
100

97
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

FEATURE ACTIVATION STRATEGY


CHANGED VAMOS TELECOM PARAMETERS (3/12)
Parameter
Name
TSC

W_LEV_HO

W_LEV_MCHO

W_LEV_PC

SubSystem

Definition

Insta Category/
nce
OMC-R access

Type

Range/
Default
value

Training Sequence Code for:


- any packet channel (when EN_VAMOS
enabled or not in the cell), and
- any circuit channel (when EN_VAMOS
disabled in the cell)
- except for common control channels
(BCCH, CCCH and CBCH).

BSC

cell

Site
(CAE)/
Changeable

Numb
er

0 to 7/ 0

Weight applicable to level samples for


handover either when DTX is disabled, or
when DTX is enabled and no silence period is
present in the multiframe.

BSC

cell

Site
(CAE)/
Changeable

Numb
er

1 to 3/ 1

Weight applicable to level samples for


microcell handover either when DTX is
disabled, or when DTX is enabled and no
silence period is present in the multiframe.

BSC

cell

Site
(CAE)/
Changeable

Numb
er

1 to 3/ 1

Weight applicable to level samples for power


control either when DTX is disabled, or when
DTX is enabled and no silence period is
present in the multiframe. For uplink, it is
applicable to both VAMOS and non-VAMOS
mode; for downlink, to non-VAMOS mode
only.

BSC

cell

Site
(CAE)/
Changeable

Numb
er

1 to 3/ 1

98
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

FEATURE ACTIVATION STRATEGY


CHANGED VAMOS TELECOM PARAMETERS (4/12)
Parameter
Name
W_PBGT_HO

W_QUAL_HO

W_QUAL_PC

Insta Category/
nce
OMC-R access

Type

Range/
Default
value

Definition

SubSystem

Weight applicable to level samples for power


budget either when DTX is disabled, or when
DTX is enabled and no silence period is
present in the multiframe.

BSC

cell

Site
(CAE)/
Changeable

Numb
er

1 to 3/ 1

Weight applicable to quality samples for


handover either when DTX is disabled, or
when DTX is enabled and no silence period is
present in the multiframe.

BSC

cell

Site
(CAE)/
Changeable

Numb
er

1 to 3/ 1

Weight applicable to quality samples for


power control either when DTX is disabled,
or when DTX is enabled and no silence
period is present in the multiframe. For
uplink, it is applicable to both VAMOS and
non-VAMOS mode; for downlink, to nonVAMOS mode only.

BSC

cell

Site
(CAE)/
Changeable

Numb
er

1 to 3/ 1

99
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

CONTENTS
1 | FEATURE DESCRIPTION
2 | FEATURE ACTIVATION STRATEGY
3 | TEST STRATEGY
4 | PERFORMANCE EVALUATION
5 | RESTRICTIONS / OTHER ISSUES
6 | CONCLUSION
7 | APPENDIX A: VAMOS SUITABILITY EVALUATION
8 | APPENDIX B: VAMOS SIMULATION RESULTS
9 | APPENDIX C: VAMOS DEPENDENCIES - BSSoIP
100
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

Optional slide:
to be included in
case of having
sub-headings

3 | TEST STRATEGY (ONLY FOR 2G)


3.1 | SUBHEADINGS 18pt

101
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

TEST STRATEGY (only for 2G)


OVERVIEW & REQUIREMENTS

(1/2)

Which benefits are expected from this feature and which outcomes can be
measured?
Performances
QoS
Stability
Resource usage (dimensioning)

Which are the possible degradations caused by this feature (side effect)?

102
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

TEST STRATEGY (only for 2G)


DETAILED PLANNING

(2/2)

Give highlights from the test plan & how the feature will be validated:
type of tests: unitary, drive tests, statistical tests, ...
type of analysis: QoS, dimensioning, performance, stability, voice quality,
objective of each test type (what is it used to check?)
required tools (internal and external)
required means (car, driver, subcontractors, ...)
estimated duration of the tests (post-processing included)

103
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

VAMOS TEST STRATEGY


OVERVIEW
Two categories of tests are planned:
1. Statistical tests:
VAMOS benefits assessment: Activate VAMOS on a pilot area (at least 1 BSC) to
show VAMOS capacity gains:

If the pilot area is initially congested, VAMOS activation should help reducing cell congestion
Otherwise, VAMOS gain can be exploited by locking some TREs prior to feature activation,
demonstrating VAMOS capability to recover part of the lost h/w capacity
Capacity gain assessment through monitoring of traffic & congestion specific
indicators (detailed in next slides)

VAMOS performance optimization: Making VAMOS more efficient through fine


tuning of some key parameters, aiming to optimize VAMOS algorithms
Assessment through careful follow-up of main CS KPIs as well as VAMOS-specific
indicators

Global stability assessment + dimensioning assessment

2. Unitary tests:

Drive tests to assess end-user perspective of VAMOS impact on DL transmission (backoff impact), RxLev/RxQual distribution in VAMOS mode, voice quality, HO
104
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

VAMOS TEST STRATEGY


PREREQUISITES
o At least 1 Mx-BSC for the pilot area, running with IP transport (IPoEth or IP/E1)
o Twin/MC-TRX, TRAU G2.5
o AMR, DL power control, DL DTX and Repeated SACCH/FACCH are recommended
o TSC code planning should be reviewed for efficient SAIC/SAIC pairing
o SAIC MS penetration should be sufficiently fair in allow statistically reliable
assessment (at least 40%)
o Abis IP dimensioning should secure enough bandwidth for VAMOS introduction
(e.g. assuming 30% VAMOS allocation @ busy hour, IP bandwidth requirements
would increase by a factor of 1.3 when VAMOS is activated)
o Pilot area selection:

High traffic load => to show VAMOS benefits to increase capacity

Very good C/I distribution & relaxed frequency reuse (cf section 1.2) to allow SAIC pairing

o Tools:

NPO with NUART facility (for QoS & stability follow-up)


Drive test toolchain with voice quality measurements (e.g. Qvoice)
105
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

VAMOS TEST STRATEGY


STATISTICAL TESTS: DETAILED PLANNING

VAMOS optimization

106
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

VAMOS TEST STRATEGY


STATISTICAL TESTS MAIN KPIs
o Circuit-switching KPIs are the main ones impacted by the feature and should
be monitored VAMOS has no direct impact on PS performance
However, for non-regression purposes and considering that the increase on CS
capacity will free resources for PS and consequently increase of data performance, PS
KPI can also be followed

o Main KPIs include the following categories:

Call Establishment phase: RTCH assignment failure, RTCH congestion, CSSR

Call Drop Rate, HO success rate, HO split, RTCH Erlang

VAMOS-specific counters/indicators should be closely monitored (see section 3)

RMS indicators provide relevant insight on radio conditions: Average DL RxLev,


RxQuality, UL Frame Erasure Rate, % noisy calls

107
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

VAMOS TEST STRATEGY


STABILITY & DIMENSIONING ASSESSMENT
o Stability assessment:

Target: Assess the impact of VAMOS activation on system stability e.g. any negative
impact on TRX or BSC availability? Specific alarms raised due to VAMOS operation?

Expected outcome: No regression in system stability/resource availability following


VAMOS activation

Means to follow: NPO-NUART

Reference period: 1 week prior to VAMOS activation

Observation period: 1-2 weeks after VAMOS activation

o Dimensioning assessment:

Target: Assess the increase in Abis traffic load due to VAMOS, and anticipate the need
for additional Abis bandwidth in case the initial dimensioning is not satisfactory

Expected outcome: % increase in Abis traffic after VAMOS activation

Means to follow: PM counters introduced to AMT tool

108
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

VAMOS TEST STRATEGY


UNITARY TESTS
1. Stationary tests - Voice quality assessment in good and medium radio conditions:
o Reference test 1: non VAMOS AMR-FR
o Reference test 2: non VAMOS AMR-HR
o Pairing test 1: VAMOS AMR-FR (SAIC/SAIC pair or SAIC/VAMOS1 pair)
o Pairing test 2: VAMOS AMR-HR (SAIC/SAIC pair or SAIC/VAMOS1 pair)
Expected outcome:
Comparison of average MOS, RxLev, RxQual values with and without VAMOS pairing
Comparison of VQ scores offered by VAMOS-FR versus non-VAMOS HR

2. Semi-Mobility tests - Voice quality assessment with 1 MS in static mode (good


radio condition while the other mobile moves around in the cell)
o Target: Assess the dynamic behaviour of VAMOS algorithms depending on radio
conditions variation, PC response, VQ at different locations, unpairing due to radio
conditions degradation of the moving user (e.g. moving towards cell edge), HO
o In case needed, a reference test (having VAMOS deactivated) can be also executed to
benchmark VAMOS versus non VAMOS in mobility conditions
109
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

VAMOS TEST STRATEGY


PLANNING SUMMARY
Test Category

Test Type
Non Regression

Statistical

Optimization
Stability/

Unitary

Trial Period

Needed resources

1 wk reference
+ 2 weeks observation 1 RNE for QoS follow-up
+ 1 TIS expert for
analysis/troubleshooting
4 Weeks
1 wk reference

Dimensioning

+ 1-2 weeks
observation

Drive tests

Five Days

110
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

1 TIS dimensioning
expert
1 Drive test engineer

CONTENTS
1 | FEATURE DESCRIPTION
2 | FEATURE ACTIVATION STRATEGY
3 | TEST STRATEGY
4 | PERFORMANCE EVALUATION
5 | RESTRICTIONS / OTHER ISSUES
6 | CONCLUSION
7 | APPENDIX A: VAMOS SUITABILITY EVALUATION
8 | APPENDIX B: VAMOS SIMULATION RESULTS
9 | APPENDIX C: VAMOS DEPENDENCIES - BSSoIP
111
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

4 | PERFORMANCE EVALUATION
4.1 | NEW VAMOS COUNTERS

112
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

PERFORMANCE EVALUATION
NEW VAMOS COUNTERS (1/12)
Counter
number

Mnemonic

Definition / Trigger(s)

Measure
d object

MC1401a

NB_TCH_REQ_NON_SAIC

Number of request coming from legacy non-SAIC capable MS

Cell

MC1401b

NB_TCH_REQ_SAIC

Number of request coming from legacy SAIC capable MS

Cell

MC1401c

NB_TCH_REQ_VAMOS1

Number of request coming from VAMOS-1 MS

Cell

MC1401d

NB_TCH_REQ_VAMOS2

Number of request coming from VAMOS-2 MS

Cell

MC1402a

NB_TCH_PAIR_ATPT
_NON_SAIC

Number of request coming from legacy non-SAIC capable MS for


which pairing attempt is triggered

Cell

MC1402b

NB_TCH_PAIR_ATPT_SAIC

Number of request coming from legacy SAIC capable MS for


which pairing attempt is triggered

Cell

MC1402c

NB_TCH_PAIR_ATPT_VAMOS1

Number of request coming from VAMOS-1 MS for which pairing


attempt is triggered

Cell

MC1402d

NB_TCH_PAIR_ATPT_VAMOS2

Number of request coming from VAMOS-2 MS for which pairing


attempt is triggered

Cell

MC1403a

NB_TCH_PAIR_SUCC
_NON_SAIC

Number of request coming from legacy non-SAIC capable MS that


are established successfully in VAMOS mode (after pairing)

Cell

MC1403b

NB_TCH_PAIR_SUCC_SAIC

Number of request coming from legacy SAIC capable MS that are


established successfully in VAMOS mode (after pairing)

Cell

MC1403c

NB_TCH_PAIR_SUCC_VAMOS1

Number of request coming from VAMOS-1 MS that are


established successfully in VAMOS mode (after pairing)

Cell

MC1403d

NB_TCH_PAIR_SUCC_VAMOS2

Number of request coming from VAMOS-2 MS that are


established successfully in VAMOS mode (after pairing)

Cell

113
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

PERFORMANCE EVALUATION
NEW VAMOS COUNTERS (2/12)
Counter
number

Mnemonic

Definition / Trigger(s)

Measured
object

MC1404a

NB_TCH_PAIR_HO_ATPT_NON_SAIC

Number of intra-cell HO request coming from legacy


non-SAIC capable MS for which pairing attempt is
triggered

Cell

MC1404b

NB_TCH_PAIR_HO_ATPT__SAIC

Number of intra-cell HO request coming from legacy


SAIC capable MS for which pairing attempt is triggered

Cell

MC1404c

NB_TCH_PAIR_HO_ATPT__VAMOS1

Number of intra-cell HO request coming from VAMOS-1


MS for which pairing attempt is triggered

Cell

MC1404d

NB_TCH_PAIR_HO_ATPT_VAMOS2

Number of intra-cell HO request coming from VAMOS-2


MS for which pairing attempt is triggered

Cell

MC1405a

NB_TCH_PAIR_HO_SUCC_NON_SAIC

Number of intra-cell HO request coming from legacy


non-SAIC capable MS that are established in VAMOS
mode (after pairing)

Cell

MC1405b

NB_TCH_PAIR_HO_SUCC_SAIC

Number of intra-cell HO request coming from legacy


SAIC capable MS that are established in VAMOS mode
(after pairing)

Cell

MC1405c

NB_TCH_PAIR_HO_SUCC_VAMOS1

Number of intra-cell HO request coming from VAMOS-1


MS that are established in VAMOS mode (after pairing)

Cell

MC1405d

NB_TCH_PAIR_HO_SUCC_VAMOS2

Number of intra-cell HO request coming from VAMOS-2


MS that are established in VAMOS mode (after pairing)

Cell

114
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

PERFORMANCE EVALUATION
NEW VAMOS COUNTERS (3/12)
Counter
number

Mnemonic

Definition / Trigger(s)

Measured
object

MC1406a

NB_TCH_EST_PAIR_DROP_
NON_SAIC

Number of call drop (TCH in traffic VAMOS mode) for a legacy nonSAIC capable MS

Cell

MC1406b

NB_TCH_EST_PAIR_DROP_
SAIC

Number of call drop (TCH in traffic VAMOS mode) for a legacy SAIC
capable MS

Cell

MC1406c

NB_TCH_EST_PAIR_DROP_
VAMOS1

Number of call drop (TCH in traffic VAMOS mode) for a VAMOS-1


MS

Cell

MC1406d

NB_TCH_EST_PAIR_DROP_
VAMOS2

Number of call drop (TCH in traffic VAMOS mode) for a VAMOS-2


capable MS

Cell

MC1407a

NB_TCH_EST_UNPAIR_DRO
P_NON_SAIC

Number of call drop (TCH in traffic non-VAMOS mode) for a legacy


non-SAIC capable MS

Cell

MC1407b

NB_TCH_EST_UNPAIR_DRO
P_SAIC

Number of call drop (TCH in traffic non-VAMOS mode) for a legacy


SAIC capable MS

Cell

MC1407c

NB_TCH_EST_UNPAIR_DRO
P_VAMOS1

Number of call drop (TCH in traffic non-VAMOS mode) for a VAMOS1 MS

Cell

MC1407d

NB_TCH_EST_UNPAIR_DRO
P_VAMOS2

Number of call drop (TCH in traffic non-VAMOS mode) for a VAMOS2 capable MS

Cell

MC1408a

NB_PAIR_PER_MS_NON_SAI Number of pairing (due to any reason) per CS call for a legacy nonC
SAIC capable MS

Cell

MC1408b

NB_PAIR_PER_MS_SAIC

Number of pairing (due to any reason) per call for legacy SAIC MS

Cell

MC1408c

NB_PAIR_PER_MS_VAMOS1

Number of pairing (due to any reason) per call for a VAMOS1 MS

Cell

MC1408d

NB_PAIR_PER_MS_VAMOS2

Number of pairing (due to any reason) per call for a VAMOS2 MS

Cell

115
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

PERFORMANCE EVALUATION
NEW VAMOS COUNTERS (4/12)
Counter
number

Mnemonic

Definition / Trigger(s)

Measured
object

MC1409a

NB_UNPAIR_PER_MS_NON_SAIC

Number of unpairing (due to any reason) per CS call for a


legacy non-SAIC capable MS

Cell

MC1409b

NB_UNPAIR_PER_MS_SAIC

Number of unpairing (due to any reason) per CS call for a


legacy SAIC capable MS

Cell

MC1409c

NB_UNPAIR_PER_MS_VAMOS1

Number of unpairing (due to any reason) per CS call for a


VAMOS-1 MS

Cell

MC1409d

NB_UNPAIR_PER_MS_VAMOS2

Number of unpairing (due to any reason) per CS call for a


VAMOS-2 capable MS

Cell

MC1410a

NB_ONE_CALL_PER_RADIO_TS_N
ON_VAMOS

Number of speech CS calls which are alone on a radio time


slot

Cell

MC1410b

NB_TWO_CALL_PER_RADIO_TS_
NON_VAMOS

Number of speech CS non-VAMOS calls which share a radio


time slot with another call

Cell

MC1410c

NB_TWO_CALL_PER_RADIO_TS_
VAMOS

Number of speech CS VAMOS calls which share a radio time


slot with another call

Cell

MC1410d

NB_THREE_CALL_PER_RADIO_TS
_VAMOS

Number of speech CS VAMOS calls which share a radio time


slot with two other calls

Cell

MC1410e

NB_FOUR_CALL_PER_RADIO_TS_
VAMOS

Number of speech CS VAMOS calls which share a radio time


slot with three other calls

Cell

116
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

PERFORMANCE EVALUATION
NEW VAMOS COUNTERS (5/12)
Counter
number

Mnemonic

Definition / Trigger(s)

Measured
object

MC1411a

DISTRIB_1_SCPIR_NON_SAIC_VAMOS1

Distribution 1 value of SCPIR for a legacy non-SAIC /


VAMOS1 pair

Cell

MC1411b

DISTRIB_2_SCPIR_NON_SAIC_VAMOS1

Distribution 2 value of SCPIR for a legacy non-SAIC /


VAMOS1 pair

Cell

MC1411c

DISTRIB_3_SCPIR_NON_SAIC_VAMOS1

Distribution 3 value of SCPIR for a legacy non-SAIC /


VAMOS1 pair

Cell

MC1411d

DISTRIB_4_SCPIR_NON_SAIC_VAMOS1

Distribution 4 value of SCPIR for a legacy non-SAIC /


VAMOS1 pair

Cell

MC1412a/
b/c/d

DISTRIB_x_SCPIR_NON_SAIC_VAMOS2

Distribution x value of SCPIR for a legacy non-SAIC /


VAMOS2 pair

Cell

MC1413a/
b/c/d

DISTRIB_x_SCPIR_SAIC_VAMOS1

Distribution x value of SCPIR for a legacy SAIC /


VAMOS1 pair

Cell

MC1414a/
b/c/d

DISTRIB_x_SCPIR_SAIC_VAMOS2

Distribution x value of SCPIR for a legacy SAIC /


VAMOS2 pair

Cell

MC1415a/
b/c/d

DISTRIB_x_SCPIR_VAMOS1_VAMOS1

Distribution x value of SCPIR for a VAMOS1/VAMOS1


pair

Cell

MC1416a/
b/c/d

DISTRIB_x_SCPIR_ VAMOS1_VAMOS2

Distribution x value of SCPIR for a VAMOS1 / VAMOS2


pair

Cell

117
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

PERFORMANCE EVALUATION
NEW VAMOS COUNTERS (6/12)
Counter
number

Mnemonic

Definition / Trigger(s)

Measured
object

MC1417a
/b/c/d

DISTRIB_x_SCPIR_ VAMOS2_VAMOS1

Distribution x value of SCPIR for a VAMOS2/VAMOS1 pair

Cell

MC1418a
/b/c/d

DISTRIB_x_SCPIR_VAMOS2_VAMOS2

Distribution x value of SCPIR for a VAMOS2/VAMOS2 pair

Cell

MC1419a
/b/c/d

DISTRIB_x_SCPIR_SAIC_SAIC

Distribution x value of SCPIR for a legacy SAIC / legacy


SAIC pair

Cell

MC1420a

NB_TCH_HO_ATPT_35_pairing_NON_
SAIC

Number of handover attempts with the cause 35 (pairing)


for a legacy non-SAIC capable MS

Cell

MC1420b

NB_TCH_HO_ATPT_35_pairing_SAIC

Number of handover attempts with the cause 35 (pairing)


for a legacy SAIC capable MS

Cell

MC1420c

NB_TCH_HO_ATPT_35_pairing_VAMO
S1

Number of handover attempts with the cause 35 (pairing)


for a legacy VAMOS1 capable MS

Cell

MC1420d

NB_TCH_HO_ATPT_35_pairing_VAMO
S2

Number of handover attempts with the cause 35 (pairing)


for a legacy VAMOS2 capable MS

Cell

MC1421a

NB_TCH_HO_ATPT_34_unpairing_NO
N_SAIC

Number of handover attempts with the cause 34


(unpairing) for a legacy non-SAIC capable MS

Cell

MC1421b

NB_TCH_HO_ATPT_34_unpairing_SAI
C

Number of handover attempts with the cause 34


(unpairing) for a legacy SAIC capable MS

Cell

MC1421c

NB_TCH_HO_ATPT_34_unpairing_VA
MOS1

Number of handover attempts with the cause 34


(unpairing) for a legacy VAMOS1 capable MS

Cell

MC1421d

NB_TCH_HO_ATPT_34_unpairing_VA
MOS2

Number of handover attempts with the cause 34


(unpairing) for a legacy VAMOS2 capable MS

Cell

118
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

PERFORMANCE EVALUATION
NEW VAMOS COUNTERS (7/12)
Counter
number

Mnemonic

Definition / Trigger(s)

Measured
object

MC1422a

AV_RXQUAL_DL_VAMOS_NON_SAIC

Average downlink quality measured by non-SAIC MS in


VAMOS mode (paired)

Cell

MC1422b

AV_RXQUAL_DL_VAMOS_SAIC

Average downlink quality measured by SAIC MS in


VAMOS mode (paired)

Cell

MC1422c

AV_RXQUAL_DL_VAMOS_VAMOS1

Average downlink quality measured by VAMOS1 MS in


VAMOS mode (paired)

Cell

MC1422d

AV_RXQUAL_DL_VAMOS_VAMOS2

Average downlink quality measured by VAMOS2 MS in


VAMOS mode (paired)

Cell

MC1423a

AV_RXQUAL_UL_VAMOS_NON_SAIC

Average uplink quality measured by BTS for non-SAIC


MS in VAMOS mode (paired)

Cell

MC1423b

AV_RXQUAL_UL_VAMOS_SAIC

Average uplink quality measured by BTS for SAIC MS


in VAMOS mode (paired)

Cell

MC1423c

AV_RXQUAL_UL_VAMOS_VAMOS1

Average uplink quality measured by BTS for VAMOS1


MS in VAMOS mode (paired)

Cell

MC1423d

AV_RXQUAL_UL_VAMOS_VAMOS2

Average uplink quality measured by BTS for VAMOS2


MS in VAMOS mode (paired)

Cell

119
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

PERFORMANCE EVALUATION
NEW VAMOS COUNTERS (8/12)

Counter
number

Mnemonic

MC1425a/b
/C/d

DISTRIB_x_SCPIR_NON_SAIC_NON_S
AIC

MC1426a/b
/C/d
MC1427

DISTRIB_x_SCPIR_NON_SAIC_SAIC
NB_MS_NON_SAIC_VAMOS_CAPABLE

Definition / Trigger(s)

Measured
object

Distribution x value of SCPIR for a non SAIC / non


SAIC pair

Cell

Distribution x value of SCPIR for a non SAIC MS / SAIC


MS pair or SAIC MS / non SAIC MS pair

Cell

Number of non-SAIC MS which are tested as VAMOS


capable

120
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

Cell

PERFORMANCE EVALUATION
NEW VAMOS COUNTERS (9/12)
Counter
number

Mnemonic

Change

Measure
d object

(M)C250

AV_NB_AVAIL_TCH

Updated to work with VAMOS or non-VAMOS mode

Cell

(M)C28a

AV_NB_BUSY_CS_TS

A radio timeslot in VAMOS usage is said busy when at least one


of the VAMOS sub channels is busy.

Cell

(M)C29a

NB_MAX_SIMUL_BUSY_CS_TS

A radio timeslot in VAMOS usage is said busy when at least one


of the VAMOS sub channels is busy.

Cell

(M)C320
a/b/c/d/e

AV_NB_IDLE_TCH_INTERF_BA
ND1to5

When VAMOS is enabled, the BTS sends idle measurements only


when the physical resource is unused

Cell

(M)C34

TIME_ALL_AVAIL_TRX_TS_BUS
Y

Updated to work with VAMOS or non-VAMOS mode

Cell

C370a

NB_TCH_FR_ALLOC

In VAMOS mode, the counter is incremented for each FR TCH


VAMOS subchannel of the timeslot.

TRX_TS

C370b

NB_TCH_HR_ALLOC

In VAMOS mode, the counter is incremented for each HR TCH


VAMOS subchannel of the timeslot.

TRX_TS

TIME_FR_TCH_BUSY

In VAMOS mode, The counter cumulates, over the Accumulation


Period all unit times during which a VAMOS TCH FR channel of
the timeslot is busy. Both VAMOS TCH FR of the timeslot are
counted independently.

TRX_TS

TIME_HR_TCH_BUSY

In VAMOS mode, The counter cumulates, over the Accumulation


Period all unit times during which a VAMOS TCH HR channel of
the timeslot is busy. Both VAMOS TCH HR of the timeslot are
counted independently.

TRX_TS

C380a

C380b

121
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

PERFORMANCE EVALUATION
NEW VAMOS COUNTERS (10/12)
Counter
number

Mnemonic

Change

Measure
d object

TIME_FR_TCH_BUSY_BY_MULT
IBAND_MS

In VAMOS mode, the counter cumulates, over the Accumulation


Period all unit times during which a VAMOS TCH FR channel of
the timeslot is busy. Both VAMOS TCH FR of the timeslot are
counted independently.

TRX_TS

C381b

TIME_HR_TCH_BUSY_BY_MUL
TIBAND_MS

In VAMOS mode, the counter cumulates, over the Accumulation


Period all unit times during which a VAMOS TCH HR channel of
the timeslot is busy. Both VAMOS TCH HR of the timeslot are
counted independently.

TRX_TS

C442

NB_TIMES_TRAF_DETECTED_H
IGH

A radio timeslot in TCH VAMOS usage is said not free when at


least one of the VAMOS subchannels is busy.

Cell

C443

NB_TIMES_TRAF_DETECTED_L
OW

A radio timeslot in TCH VAMOS usage is said not free when at


least one of the VAMOS subchannels is busy.

Cell

(M)C460
a

NB_TCH_EMERGENCY_HO_PRE
SERVATION

Not incremented in VAMOS mode

Cell

NEW_CHANNEL_ID

Sub-Channel field gives the subchannel number in case of HR


TCH and also the TSC which allows to differentiate physically two
VAMOS subchannels

NEW_RTCH_TYPE

Updated to work with VAMOS or non-VAMOS mode

C381a

HO43/HO
06
HO43a/H
O06a

122
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

PERFORMANCE EVALUATION
NEW VAMOS COUNTERS (11/12)
Counter
number

Mnemonic

Change

Measure
d object

HO64/HO
5

OLD_CHANNEL_ID

Sub-Channel field gives the subchannel number in case of HR


TCH and also the TSC which allows to differentiate physically two
VAMOS subchannels

HO64a/H
O5a

OLD_RTCH_TYPE

Updated to work with VAMOS or non-VAMOS mode

MC1212/
3/4/5

TIME_PWR_RED_GMSK_1to4

AQPSK bursts transmitting a signaling frame for at least one of


the two VAMOS sub-channels (either in the whole burst or in a
half burst) are not concerned

TRX

MC1221

TIME_GMSK_BURST_TRANSMI
SSION

AQPSK bursts transmitting a signaling frame for at least one of


the two VAMOS sub-channels (either in the whole burst or in a
half burst) are not concerned

TRX

TIME_TRX_GSM_FR_BUSY

In VAMOS mode, the counter cumulates, over the Accumulation


Period all unit times during which a VAMOS TCH FR channel of
the timeslot in the GSM frequency band is busy. Both VAMOS
TCH FR of the timeslot are counted independently.

TRX

TIME_TRX_GSM_HR_BUSY

In VAMOS mode, The counter cumulates, over the Accumulation


Period all unit times during which a VAMOS TCH HR channel of
the timeslot in the GSM frequency band is busy. All VAMOS TCH
HR of the timeslot are counted independently.

TRX

MC380c

MC380d

123
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

PERFORMANCE EVALUATION
NEW VAMOS COUNTERS (12/12)
Counter
number

Change

Measure
d object

TIME_TRX_DCS_FR_BUSY

In VAMOS mode, the counter cumulates, over the Accumulation


Period all unit times during which a VAMOS TCH FR channel of
the timeslot in the DCS/PCS frequency band is busy. Both VAMOS
TCH FR of the timeslot are counted independently.

TRX

MC380f

TIME_TRX_DCS_HR_BUSY

In VAMOS mode, The counter cumulates, over the Accumulation


Period all unit times during which a VAMOS TCH HR channel of
the timeslot in the DCS/PCS frequency band is busy. All VAMOS
TCH HR of the timeslot are counted independently.

TRX

MC801a

AV_NB_BUSY_DYN_TCH

Updated to work with VAMOS or non-VAMOS mode

Cell

MC801b

MAX_NB_BUSY_DYN_TCH

Updated to work with VAMOS or non-VAMOS mode

Cell

R01/T01

CHANNEL_ID (TCH)

Sub-Channel field gives the subchannel number in case of HR


TCH (HR/FR type is given in R01a counter) and also the TSC
(training sequence code) which allows to differentiate physically
two VAMOS subchannels

R01a/T0
1a

RTCH_TYPE

Updated to work with VAMOS or non-VAMOS mode

MC380e

Mnemonic

124
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

4 | PERFORMANCE EVALUATION
4.2 | NEW VAMOS INDICATORS

125
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

PERFORMANCE EVALUATION
NEW VAMOS INDICATORS (1/24)
NPO indicator
ref name

NPO Long Name

NPO Formula

GHCSTVAPNSN

CHO_Vamos_Pairing_Non_
MC1420a
Saic

GHCSTVAPSN

CHO_Vamos_Pairing_Saic

MC1420b

GHCSTVAPV1N

CHO_Vamos_Pairing_Vam
os_1

MC1420c

GHCSTVAPV2N

CHO_Vamos_Pairing_Vam
os_2

MC1420d

Description
Number of handover attempts, with the cause
35 (VAMOS pairing channel adaptation: Good
radio quality, high signal level and high load
leading to handover of one user on a VAMOS
channel) related to non-SAIC capable MS.
Number of handover attempts, with the cause
35 (VAMOS pairing channel adaptation: Good
radio quality, high signal level and high load
leading to handover of one user on a VAMOS
channel) related to SAIC capable MS.
Number of handover attempts, with the cause
35 (VAMOS pairing channel adaptation: Good
radio quality, high signal level and high load
leading to handover of one user on a VAMOS
channel) related to VAMOS1 capable MS.
Number of handover attempts, with the cause
35 (VAMOS pairing channel adaptation: Good
radio quality, high signal level and high load
leading to handover of one user on a VAMOS
channel) related to VAMOS2 capable MS.

126
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

PERFORMANCE EVALUATION
NEW VAMOS INDICATORS (2/24)
NPO indicator
ref name

NPO Long Name

NPO Formula

GHCSTVAUPNSN

CHO_Vamos_Unpairing_No
MC1421a
n_Saic

GHCSTVAUPSN

CHO_Vamos_Unpairing_Sa
MC1421b
ic

GHCSTVAUPV1N

CHO_Vamos_Unpairing_Va
MC1421c
mos_1

GHCSTVAUPV2N

CHO_Vamos_Unpairing_Va
MC1421d
mos_2

Description
Number of handover attempts, with the cause
34 (VAMOS unpairing channel adaptation: Too
bad radio quality for a VAMOS subchannel
leading to handover of one or both paired user)
related to non-SAIC capable MS.
Number of handover attempts, with the cause
34 (VAMOS unpairing channel adaptation: Too
bad radio quality for a VAMOS subchannel
leading to handover of one or both paired user)
related to SAIC capable MS.
Number of handover attempts, with the cause
34 (VAMOS unpairing channel adaptation: Too
bad radio quality for a VAMOS subchannel
leading to handover of one or both paired user)
related to VAMOS1 capable MS.
Number of handover attempts, with the cause
34 (VAMOS unpairing channel adaptation: Too
bad radio quality for a VAMOS subchannel
leading to handover of one or both paired user)
related to VAMOS2 capable MS.

127
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

PERFORMANCE EVALUATION
NEW VAMOS INDICATORS (3/24)
NPO indicator
ref name

NPO Long Name

NPO Formula

GQSCDNVNSN

Call_Drop_VAMOS_non_SA
MC1406a
IC

GQSCDNVSN

Call_Drop_VAMOS_SAIC

MC1406b

GQSCDNVV1N

Call_Drop_VAMOS_Vamos
_1

MC1406c

GQSCDNVV2N

Call_Drop_VAMOS_Vamos
_2

MC1406d

Description
Number of 48.008 CLEAR REQUEST sent to the
MSC for speech CS calls in TCH established
phase (traffic) in VAMOS mode related to nonSAIC capable MS.
Handover failures are not taken into account.
Number of 48.008 CLEAR REQUEST sent to the
MSC for speech CS calls in TCH established
phase (traffic) in VAMOS mode related to SAIC
capable MS.
Handover failures are not taken into account.
Number of 48.008 CLEAR REQUEST sent to the
MSC for speech calls in TCH established phase
(traffic) in VAMOS mode related to VAMOS-1
capable MS.
Handover failures are not taken into account
Number of 48.008 CLEAR REQUEST sent to the
MSC for speech CS calls in TCH established
phase (traffic) in VAMOS mode related to
VAMOS-2 capable MS.
Handover failures are not taken into account

128
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

PERFORMANCE EVALUATION
NEW VAMOS INDICATORS (4/24)
NPO indicator
ref name

NPO Long Name

NPO Formula

GQSCDVNSN

Call_Drop_non_VAMOS_no
MC1407a
n_SAIC

GQSCDVSN

Call_Drop_non_VAMOS_SA
MC1407b
IC

GQSCDVV1N

Call_Drop_non_VAMOS_Va
MC1407c
mos_1

GQSCDVV2N

Call_Drop_non_VAMOS_Va
MC1407d
mos_2

Description
Number of 48.008 CLEAR REQUEST sent to the
MSC for speech CS calls in TCH established
phase (traffic) in non VAMOS mode related to
non-SAIC capable MS.
Handover failures are not taken into account
Number of 48.008 CLEAR REQUEST sent to the
MSC for speech CS calls in TCH established
phase (traffic) in non VAMOS mode related to
SAIC capable MS.
Handover failures are not taken into account
Number of 48.008 CLEAR REQUEST sent to the
MSC for speech CS calls in TCH established
phase (traffic) in non VAMOS mode related to
VAMOS-1 capable MS.
Handover failures are not taken into account
Number of 48.008 CLEAR REQUEST sent to the
MSC for speech CS calls in TCH established
phase (traffic) in non VAMOS mode related to
VAMOS-2 capable MS.
Handover failures are not taken into account

129
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

PERFORMANCE EVALUATION
NEW VAMOS INDICATORS (5/24)
NPO indicator
ref name

NPO Long Name

NPO
Formula

Description
Indicates the average receive downlink quality (0..7)
of the serving cell measured by non-SAIC MSs in
VAMOS mode (paired).

GQSCQQLDVANSN

Rx_Quality_DL_Vamos_No
n_Saic_Avg

GQSCQQLDVASN

Rx_Quality_DL_Vamos_Sai
MC1422b
c_Avg

GQSCQQLDVAV1N

Rx_Quality_DL_Vamos_Va
mos_1_Avg

MC1422c

GQSCQQLDVAV2N

Rx_Quality_DL_Vamos_Va
mos_2_Avg

MC1422d

GQSCQQLUVANSN

Rx_Quality_UL_Vamos_No
n_Saic_Avg

MC1423a

GQSCQQLUVASN

Rx_Quality_UL_Vamos_Sai
c_Avg

MC1423b

Indicates the average receive uplink quality (0..7) of


the serving cell measured by the BTS related to SAIC
MSs in VAMOS mode (paired).

GQSCQQLUVAV1N

Rx_Quality_UL_Vamos_Va
mos_1_Avg

MC1423c

Indicates the average receive uplink quality (0..7) of


the serving cell measured by the BTS related to
VAMOS-1 MSs in VAMOS mode (paired).

GQSCQQLUVAV2N

Rx_Quality_UL_Vamos_Va
mos_2_Avg

MC1423d

Indicates the average receive uplink quality (0..7) of


the serving cell measured by the BTS related to
VAMOS-2 MSs in VAMOS mode (paired).

MC1422a

Indicates the average receive downlink quality (0..7)


of the serving cell measured by SAIC MSs in VAMOS
mode (paired).
Indicates the average receive downlink quality (0..7)
of the serving cell measured by VAMOS-1 MSs in
VAMOS mode (paired).
Indicates the average receive downlink quality (0..7)
of the serving cell measured by VAMOS-2 MSs in
VAMOS mode (paired).
Indicates the average receive uplink quality (0..7) of
the serving cell measured by the BTS related to nonSAIC MSs in VAMOS mode (paired).

130
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

PERFORMANCE EVALUATION
NEW VAMOS INDICATORS (6/24)
NPO indicator
ref name

GTCDT1NSVA1N

GTCDT1NSVA2N
GTCDT1SSN
GTCDT1SVA1N
GTCDT1SVA2N
GTCDT1VA1VA1N
GTCDT1VA1VA2N
GTCDT1VA2VA1N
GTCDT1VA2VA2N
GTCDT1NSNSN
GTCDT1NSSN

NPO Long Name

NPO
Formula

SCPIR_Distribution_First_Inter
MC1411a
val_Non_SAIC_Vamos_1

SCPIR_Distribution_First_Inter
val_Non_SAIC_Vamos_2
SCPIR_Distribution_First_Inter
val_Saic_Saic
SCPIR_Distribution_First_Inter
val_SAIC_Vamos_1
SCPIR_Distribution_First_Inter
val_SAIC_Vamos_2
SCPIR_Distribution_First_Inter
val_Vamos_1_Vamos_1
SCPIR_Distribution_First_Inter
val_Vamos_1_Vamos_2
SCPIR_Distribution_First_Inter
val_Vamos_2_Vamos_1
SCPIR_Distribution_First_Inter
val_Vamos_2_Vamos_2
SCPIR_Distribution_First_Inter
val_Non_SAIC_Non_SAIC
SCPIR_Distribution_First_Inter
val_Non_SAIC_SAIC

Description
First interval of distribution of SCPIR for a non-SAIC MS/
VAMOS1 MS pair. Accumulates the distribution of calls for
a non-SAIC MS/VAMOS1 MS pair whose SCPIR lies during
a measurement reporting period within the first SCPIR
range defined by the values strictly below the threshold
SCPIR_NON_SAIC_VAMOS1_THR_1.

MC1412a

Similar to previous but for non-SAIC MS/VAMOS2 MS pair

MC1419a

Similar to previous but for SAIC MS/SAIC MS pair

MC1413a

Similar to previous but for SAIC MS/VAMOS1 MS pair

MC1414a

Similar to previous but for SAIC MS/VAMOS2 MS pair

MC1415a

Similar to previous but for VAMOS1 MS/VAMOS1 MS pair

MC1416a

Similar to previous but for VAMOS1 MS/VAMOS2 MS pair

MC1417a

Similar to previous but for VAMOS2 MS/VAMOS1 MS pair

MC1418a

Similar to previous but for VAMOS2 MS/VAMOS2 MS pair

MC1425a

Similar to previous but for Non-SAIC MS/Non-SAIC MS pair

MC1426a

Similar to previous but for Non-SAIC MS/SAIC MS pair

131
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

PERFORMANCE EVALUATION
NEW VAMOS INDICATORS (7/24)
NPO indicator
ref name
GTCDT2NSVA1N

GTCDT2NSVA2N
GTCDT2SSN
GTCDT2SVA1N
GTCDT2SVA2N
GTCDT2VA1VA1N
GTCDT2VA1VA2N
GTCDT2VA2VA1N
GTCDT2VA2VA2N
GTCDT2NSNSN
GTCDT2NSSN

NPO Long Name

SCPIR_Distribution_Second_Int
erval_Non_SAIC_Vamos_1

SCPIR_Distribution_Second_Int
erval_Non_SAIC_Vamos_2
SCPIR_Distribution_Second_Int
erval_Saic_Saic
SCPIR_Distribution_Second_Int
erval_SAIC_Vamos_1
SCPIR_Distribution_Second_Int
erval_SAIC_Vamos_2
SCPIR_Distribution_Second_Int
erval_Vamos_1_Vamos_1
SCPIR_Distribution_Second_Int
erval_Vamos_1_Vamos_2
SCPIR_Distribution_Second_Int
erval_Vamos_2_Vamos_1
SCPIR_Distribution_Second_Int
erval_Vamos_2_Vamos_2
SCPIR_Distribution_Second_Int
erval_Non_SAIC_Non_SAIC
SCPIR_Distribution_Second_Int
erval_Non_SAIC_SAIC

NPO
Formula
MC1411b

Description
Second interval of distribution of SCPIR for a non-SAIC MS /
VAMOS1 MS pair. Accumulates the distribution of calls for a
non-SAIC MS / VAMOS1 MS pair whose SCPIR lies during a
measurement reporting period within the second SCPIR range
defined by the values between the thresholds [SCPIR_NON_
SAIC_VAMOS1_THR_1,SCPIR_NON_SAIC_VAMOS1_THR_2 [.

MC1412b Similar to previous but for non-SAIC MS/VAMOS2 MS pair


MC1419b Similar to previous but for SAIC MS/SAIC MS pair
MC1413b Similar to previous but for SAIC MS/VAMOS1 MS pair
MC1414b Similar to previous but for SAIC MS/VAMOS2 MS pair
MC1415b Similar to previous but for VAMOS1 MS/VAMOS1 MS pair
MC1416b Similar to previous but for VAMOS1 MS/VAMOS2 MS pair
MC1417b Similar to previous but for VAMOS2 MS/VAMOS1 MS pair
MC1418b Similar to previous but for VAMOS2 MS/VAMOS2 MS pair
MC1425b

Similar to previous but for Non-SAIC MS/Non-SAIC MS


pair

MC1426b Similar to previous but for Non-SAIC MS/SAIC MS pair


132

COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.


ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

PERFORMANCE EVALUATION
NEW VAMOS INDICATORS (8/24)
NPO indicator
ref name
GTCDT3NSVA1N

GTCDT3NSVA2N
GTCDT3SSN
GTCDT3SVA1N
GTCDT3SVA2N
GTCDT3VA1VA1N
GTCDT3VA1VA2N
GTCDT3VA2VA1N
GTCDT3VA2VA2N
GTCDT3NSNSN
GTCDT3NSSN

NPO Long Name

NPO
Formula

SCPIR_Distribution_Third_Inter
MC1411c
val_Non_SAIC_Vamos_1

SCPIR_Distribution_Third_Inter
val_Non_SAIC_Vamos_2
SCPIR_Distribution_Third_Inter
val_Saic_Saic
SCPIR_Distribution_Third_Inter
val_SAIC_Vamos_1
SCPIR_Distribution_Third_Inter
val_SAIC_Vamos_2
SCPIR_Distribution_Third_Inter
val_Vamos_1_Vamos_1
SCPIR_Distribution_Third_Inter
val_Vamos_1_Vamos_2
SCPIR_Distribution_Third_Inter
val_Vamos_2_Vamos_1
SCPIR_Distribution_Third_Inter
val_Vamos_2_Vamos_2
SCPIR_Distribution_Third_Inter
val_Non_SAIC_Non_SAIC
SCPIR_Distribution_Third_Inter
val_Non_SAIC_SAIC

Description
Third interval of distribution of SCPIR for a non-SAIC MS /
VAMOS1 MS pair. Accumulates the distribution of calls for a
non-SAIC MS / VAMOS1 MS pair whose SCPIR lies during a
measurement reporting period within the third SCPIR range
defined by the values between the thresholds [SCPIR_NON_
SAIC_VAMOS1_THR_2,SCPIR_NON_SAIC_VAMOS1_THR_3 [.

MC1412c

Similar to previous but for non-SAIC MS/VAMOS2 MS pair

MC1419c

Similar to previous but for SAIC MS/SAIC MS pair

MC1413c

Similar to previous but for SAIC MS/VAMOS1 MS pair

MC1414c

Similar to previous but for SAIC MS/VAMOS2 MS pair

MC1415c

Similar to previous but for VAMOS1 MS/VAMOS1 MS pair

MC1416c

Similar to previous but for VAMOS1 MS/VAMOS2 MS pair

MC1417c

Similar to previous but for VAMOS2 MS/VAMOS1 MS pair

MC1418c

Similar to previous but for VAMOS2 MS/VAMOS2 MS pair

MC1425c

Similar to previous but for Non-SAIC MS/Non-SAIC MS


pair

MC1426c

Similar to previous but for Non-SAIC MS/SAIC MS pair

133
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

PERFORMANCE EVALUATION
NEW VAMOS INDICATORS (9/24)
NPO indicator
ref name

GTCDT4NSVA1N

GTCDT4NSVA2N
GTCDT4SSN
GTCDT4SVA1N
GTCDT4SVA1VA1N
GTCDT4SVA1VA2N
GTCDT4SVA2N
GTCDT4SVA2VA1N
GTCDT4SVA2VA2N
GTCDT4NSNSN
GTCDT4NSSN

NPO Long Name

SCPIR_Distribution_Fourth_Inte
rval_Non_SAIC_Vamos_1

SCPIR_Distribution_Fourth_Inte
rval_Non_SAIC_Vamos_2
SCPIR_Distribution_Fourth_Inte
rval_Saic_Saic
SCPIR_Distribution_Fourth_Inte
rval_SAIC_Vamos_1
SCPIR_Distribution_Fourth_Inte
rval_Vamos_1_Vamos_1
SCPIR_Distribution_Fourth_Inte
rval_Vamos_1_Vamos_2
SCPIR_Distribution_Fourth_Inte
rval_SAIC_Vamos_2
SCPIR_Distribution_Fourth_Inte
rval_Vamos_2_Vamos_1
SCPIR_Distribution_Fourth_Inte
rval_Vamos_2_Vamos_2
SCPIR_Distribution_Fourth_Inte
rval_Non_SAIC_Non_SAIC
SCPIR_Distribution_Fourth_Inte
rval_Non_SAIC_SAIC

NPO
Formula

Description

Fourth interval of distribution of SCPIR for a non-SAIC MS


/ VAMOS1 MS pair. Accumulates the distribution of calls
for a non-SAIC MS / VAMOS1 MS pair whose SCPIR lies
MC1411d
during a measurement reporting period within the fourth
SCPIR range defined by the values strictly above the
threshold [SCPIR_NON_SAIC_VAMOS1_THR_3.
MC1412d Similar to previous but for non-SAIC MS/VAMOS2 MS pair
MC1419d Similar to previous but for SAIC MS/SAIC MS pair
MC1413d Similar to previous but for SAIC MS/VAMOS1 MS pair
MC1415d Similar to previous but for SAIC MS/VAMOS2 MS pair
MC1416d Similar to previous but for VAMOS1 MS/VAMOS1 MS pair
MC1414d Similar to previous but for VAMOS1 MS/VAMOS2 MS pair
MC1417d Similar to previous but for VAMOS2 MS/VAMOS1 MS pair
MC1418d Similar to previous but for VAMOS2 MS/VAMOS2 MS pair
MC1425d

Similar to previous but for Non-SAIC MS/Non-SAIC MS


pair

MC1426d Similar to previous but for Non-SAIC MS/SAIC MS pair


134

COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.


ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

PERFORMANCE EVALUATION
NEW VAMOS INDICATORS (10/24)
NPO indicator
ref name

NPO Long Name

NPO Formula

GTCHOINNSPAN

RTCH_HO_non_SAIC_Intra
MC1404a
_Pairing_Attempt

GTCHOINNSSUN

RTCH_HO_non_SAIC_Intra
MC1405a
_success

GTCHOINSPAN

RTCH_HO_SAIC_Intra_Pair
MC1404b
ing_Attempt

GTCHOINSSUN

RTCH_HO_SAIC_Intra_suc
MC1405b
cess

GTCHOINV1PAN

RTCH_HO_VAMOS_1_Intra
MC1404c
_Pairing_Attempt

GTCHOINV1SUN

RTCH_HO_VAMOS_1_Intra
MC1405c
_success

GTCHOINV2PAN

RTCH_HO_VAMOS_2_Intra
MC1404d
_Pairing_Attempt

GTCHOINV2SUN

RTCH_HO_VAMOS_2_Intra
MC1405d
_success

Description
Number of intra-cell TCH (in HR or FR usage)
handover with VAMOS pairing attempt related to
non-SAIC capable MS
Number of intra-cell TCH (HR or FR) handover
successes related to non-SAIC capable MS that are
established in Vamos mode (after pairing).
Number of intra-cell TCH (in HR or FR usage)
handover with VAMOS pairing attempt related to
SAIC capable MS.
Number of intra-cell TCH (HR or FR) handover
successes related to SAIC capable MS that are
established in Vamos mode (after pairing).
Number of intra-cell TCH (in HR or FR usage)
handover with VAMOS pairing attempt related to
VAMOS-1 capable MS.
Number of intra-cell TCH (in HR or FR usage)
handover successes related to legacy VAMOS-1
capable MS that are established in Vamos mode
(after pairing).
Number of intra-cell TCH (in HR or FR usage)
handover with VAMOS pairing attempt related to
VAMOS-2 capable MS.
Number of intra-cell TCH (in HR or FR usage)
handover successes related to legacy VAMOS-2
capable MS that are established in Vamos mode
(after pairing).

135
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

PERFORMANCE EVALUATION
NEW VAMOS INDICATORS (11/24)
NPO indicator
ref name

NPO Long Name

NPO
Formula

GTCNAANSN

RTCH_assign_non_SAIC_allocated

MC1403a

GTCNAASN

RTCH_assign_SAIC_allocated

MC1403b

GTCNAAV1N

RTCH_assign_VAMOS_1_allocated

MC1403c

GTCNAAV2N

RTCH_assign_VAMOS_2_allocated

MC1403d

GTCNARQNSN

RTCH_assign_non_SAIC_request

MC1401a

GTCNARQSN

RTCH_assign_SAIC_request

MC1401b

GTCNARQV1N

RTCH_assign_VAMOS_1_request

MC1401c

GTCNARQV2N

RTCH_assign_VAMOS_2_request

MC1401d

Description
Number of TCH normal assignment from non-SAIC
capable mobiles whose channel is allocated in the
BSC in VAMOS mode after pairing.
Number of TCH normal assignment from SAIC
capable mobiles whose channel is allocated in the
BSC in VAMOS mode after pairing.
Number of TCH normal assignment from VAMOS-1
capable mobiles whose channel is allocated in the
BSC in VAMOS mode after pairing.
Number of TCH normal assignment from VAMOS-2
capable mobiles whose channel is allocated in the
BSC in VAMOS mode after pairing.
Number of TCH normal assignments requests from
non-SAIC capable mobiles related to speech CS call.
Number of TCH normal assignments requests from SAIC
capable mobiles related to speech CS call.

Number of TCH normal assignments requests from


VAMOS-1 capable mobiles related to speech CS call.
Number of TCH normal assignments requests from
VAMOS-2 capable mobiles related to speech CS call.

136
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

PERFORMANCE EVALUATION
NEW VAMOS INDICATORS (12/24)
NPO indicator
ref name

NPO Long Name

NPO Formula

GTCNANSPTN

RTCH_assign_non_SAIC_P
airing_Attempted_Triggere MC1402a
d

GTCNASPTN

RTCH_assign_SAIC_Pairing
MC1402b
_Attempted_Triggered

GTCNAV1PTN
GTCNAV2PTN

RTCH_assign_VAMOS_1_P
airing_Attempted_Triggere MC1402c
d
RTCH_assign_VAMOS_2_P
airing_Attempted_Triggere MC1402d
d

Description
Number of TCH normal assignment from nonSAIC capable mobiles for which pairing attempt
is triggered.
Number of TCH normal assignment from SAIC
capable mobiles for which pairing attempt is
triggered.
Number of TCH normal assignment from
VAMOS-1 capable mobiles for which pairing
attempt is triggered
Number of TCH normal assignment from
VAMOS-2 capable mobiles for which pairing
attempt is triggered.

137
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

PERFORMANCE EVALUATION
NEW VAMOS INDICATORS (13/24)
NPO indicator
ref name

NPO Long Name

NPO Formula

GTCVA1CNVN

CS_Calls_One_per_Time_S
MC1410a
lot_non_Vamos

GTCVA2CNVN

CS_Calls_Two_per_Time_S
MC1410b
lot_non_Vamos

GTCVA2CVN

CS_Calls_Two_per_Time_S
MC1410c
lot_Vamos

GTCVA3CVN

CS_Calls_Three_per_Time
_Slot_Vamos

MC1410d

GTCV4CVN

CS_Calls_Four_per_Time_
Slot_Vamos

MC1410e

Description
Number of speech CS calls which are alone on a
radio time slot (one call per radio time slot). It
matches a FR TCH or one HR TCH allocated in
non-VAMOS mode on a radio time slot.
Number of speech CS calls which share a radio
time slot with another call (two calls per radio
time slot) in case of two HR TCH allocated in
non-VAMOS mode.
Number of speech CS calls which share a radio
time slot with another call (two calls per radio
time slot) in case of two FR TCH allocated in
VAMOS mode or two HR TCH in VAMOS mode.
Number of speech CS calls which share a radio
time slot with two other calls (three calls per
radio time slot). It matches the case of two HR
TCH in VAMOS mode and one HR TCH in nonVAMOS mode on a radio time slot.
Number of speech CS calls which share a radio
time slot with three other calls during the
accumulation period (four calls per radio time
slot). It matches the case of four HR TCH in
VAMOS mode on a radio time slot.

138
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

PERFORMANCE EVALUATION
NEW VAMOS INDICATORS (14/24)
NPO indicator
ref name

NPO Long Name

NPO Formula

GTCVAPNSN

VAMOS_pairings_per_call_
non_SAIC

MC1408a

GTCVAPSN

VAMOS_pairings_per_call_
SAIC

MC1408b

GTCVAPV1N

VAMOS_pairings_per_call_
Vamos_1

MC1408c

GTCVAPV2N

VAMOS_pairings_per_call_
Vamos_2

MC1408d

Description
Number of VAMOS pairing (due to any reason)
per CS call for a non-SAIC capable MS.
A CS call can be paired due to its own TCH
assignment (at establishment or at handover) or
because another call is paired with it on a radio
time slot.
Number of VAMOS pairing (due to any reason)
per CS call for a SAIC capable MS.
A CS call can be paired due to its own TCH
assignment (at establishment or at handover) or
because another call is paired with it on a radio
time slot.
"Number of VAMOS pairing (due to any reason)
per CS call for a VAMOS-1 capable MS.
A CS call can be paired due to its own TCH
assignment (at establishment or at handover) or
because another call is paired with it on a radio
time slot.
Number of VAMOS pairing (due to any reason)
per CS call for a VAMOS-2 capable MS.
A CS call can be paired due to its own TCH
assignment (at establishment or at handover) or
because another call is paired with it on a radio
time slot.

139
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

PERFORMANCE EVALUATION
NEW VAMOS INDICATORS (15/24)
NPO indicator
ref name

NPO Long Name

NPO Formula

GTCVAUPNSN

VAMOS_unpairings_per_call_
MC1409a
non_SAIC

GTCVAUPSN

VAMOS_unpairings_per_call_
MC1409b
SAIC

GTCVAUPV1N

VAMOS_unpairings_per_call_
MC1409c
Vamos_1

GTCVAUPV2N

VAMOS_unpairings_per_call_
MC1409d
Vamos_2

GTRNSVN

NON_SAIC_VAMOS_CAPABL
E_MS_NB

MC1427

Description
Number of unpairing (due to any reason e.g.
release of paired call) per CS call for a non-SAIC
capable MS.
Release of the call is not considered as
unpairing.
Number of unpairing (due to any reason e.g.
release of paired call) per CS call for a SAIC
capable MS.
Release of the call is not considered as
unpairing.
Number of unpairing (due to any reason e.g.
release of paired call) per CS call for a VAMOS-1
capable MS.
Release of the call is not considered as
unpairing.
Number of unpairing (due to any reason e.g.
release of paired call) per CS call for a VAMOS-2
capable MS.
Release of the call is not considered as
unpairing.
Number of non-SAIC MS which are tested as
VAMOS capable (undeclared SAIC capability for
voice services).

140
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

PERFORMANCE EVALUATION
NEW VAMOS INDICATORS (16/24)
NPO indicator
ref name
GHCSTVAPTN

GHCSTVAPNSR

GHCSTVAPSR

GHCSTVAPV1R

GHCSTVAPV2R

NPO Long Name

NPO Formula

Description

CHO_Vamos_Pairing_Non_Saic
Total number of handover attempts,
CHO_VAMOS_PARING_TOTA +CHO_Vamos_Pairing_Saic+C
with the cause 35 (VAMOS pairing
L
HO_Vamos_Pairing_Vamos_1+
channel adaptation)
CHO_Vamos_Pairing_Vamos_2
Rate of handover attempts, with the
cause 35 (VAMOS pairing channel
CHO_Vamos_Pairing_Non_S CHO_Vamos_Pairing_Non_Saic
adaptation) related to non-SAIC
aic_Rate
/CHO_VAMOS_PARING_TOTAL
capable MS.

CHO_Vamos_Pairing_Saic
_Rate

Rate of handover attempts, with the


cause 35 (VAMOS pairing channel
CHO_Vamos_Pairing_Saic
adaptation) related to SAIC capable
/CHO_VAMOS_PARING_TOTAL
MS.

Rate of handover attempts, with the


cause 35 (VAMOS pairing channel
CHO_Vamos_Pairing_Vamos CHO_Vamos_Pairing_Vamos_1
adaptation) related to VAMOS1
_1_Rate
/CHO_VAMOS_PARING_TOTAL
capable MS.
Rate of handover attempts, with the
cause 35 (VAMOS pairing channel
CHO_Vamos_Pairing_Vamos CHO_Vamos_Pairing_Vamos_2
adaptation) related to VAMOS2
_2_Rate
/CHO_VAMOS_PARING_TOTAL
capable MS.

141
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

PERFORMANCE EVALUATION
NEW VAMOS INDICATORS (17/24)
NPO indicator
ref name
GHCSTVAUPTN

GHCSTVAUPNSR

GHCSTVAUPSR

GHCSTVAUPV1R

GHCSTVAUPV2R

NPO Long Name

NPO Formula

Description

CHO_Vamos_Unpairing_Non_S
aic+CHO_Vamos_Unpairing_S Total number of handover attempts,
CHO_VAMOS_UNPARING_T
aic+CHO_Vamos_Unpairing_V with the cause 34 (VAMOS unpairing
OTAL
amos_1+CHO_Vamos_Unpairi channel adaptation)
ng_Vamos_2
Rate of handover attempts, with the
CHO_Vamos_Unpairing_Non_S cause 34 (VAMOS unpairing channel
CHO_Vamos_UnPairing_Non
aic/CHO_VAMOS_UNPARING_ adaptation) related to non-SAIC
_Saic_Rate
TOTAL
capable MS.
Rate of handover attempts, with the
CHO_Vamos_Unpairing_Saic/C cause 34 (VAMOS unpairing channel
CHO_Vamos_UnPairing_Saic
HO_VAMOS_UNPARING_TOTA adaptation) related to SAIC capable
_Rate
L
MS.
Rate of handover attempts, with the
CHO_Vamos_Unpairing_Vamos cause 34 (VAMOS unpairing channel
CHO_Vamos_UnPairing_Vam
_1/CHO_VAMOS_UNPARING_T adaptation) related to VAMOS1
os_1_Rate
OTAL
capable MS.
Rate of handover attempts, with the
CHO_Vamos_Unpairing_Vamos cause 34 (VAMOS unpairing channel
CHO_Vamos_UnPairing_Vam
_2/CHO_VAMOS_UNPARING_T adaptation) related to VAMOS2
os_2_Rate
OTAL
capable MS.

142
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

PERFORMANCE EVALUATION
NEW VAMOS INDICATORS (18/24)
NPO indicator
ref name

GQSCDVTN

GQSCDVNSR

GQSCDVSR

GQSCDVV1R

GQSCDVV2R

NPO Long Name

NPO Formula

Description

Total number of 48.008 CLEAR REQUEST


Call_Drop_VAMOS_non_SAIC+ sent to the MSC for speech CS calls in TCH
Call_Drop_VAMOS_SAIC+
established phase (traffic) in VAMOS
Call_Drop_VAMOS_Total
Call_Drop_VAMOS_Vamos_1+ mode.
Call_Drop_VAMOS_Vamos_2
Handover failures are not taken into
account.
Rate of 48.008 CLEAR REQUEST sent to
Call_Drop_VAMOS_non_S Call_Drop_VAMOS_non_SAIC/ the MSC for speech CS calls in TCH
AIC_Rate
Call_Drop_VAMOS_Total
established phase (traffic) in VAMOS mode
related to non-SAIC capable MS.
Rate of 48.008 CLEAR REQUEST sent to
Call_Drop_VAMOS_SAIC_ Call_Drop_VAMOS_SAIC/
the MSC for speech CS calls in TCH
Rate
Call_Drop_VAMOS_Total
established phase (traffic) in VAMOS mode
related to SAIC capable MS.
Rate of 48.008 CLEAR REQUEST sent to
Call_Drop_VAMOS_Vamos Call_Drop_VAMOS_Vamos_1/ the MSC for speech CS calls in TCH
_1_Rate
Call_Drop_VAMOS_Total
established phase (traffic) in VAMOS mode
related to VAMOS1 capable MS.
Rate of 48.008 CLEAR REQUEST sent to
Call_Drop_VAMOS_Vamos Call_Drop_VAMOS_Vamos_2/ the MSC for speech CS calls in TCH
_2_Rate
Call_Drop_VAMOS_Total
established phase (traffic) in VAMOS mode
related to VAMOS2 capable MS.

143
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

PERFORMANCE EVALUATION
NEW VAMOS INDICATORS (19/24)
NPO indicator
ref name

NPO Long Name

GQSCDNVTN

Call_Drop_non_VAMOS
_Total

GQSCDNVNSR

Call_Drop_non_VAMOS
_non_SAIC_Rate

GQSCDNVSR

Call_Drop_non_VAMOS
_SAIC_Rate

GQSCDNVV1R

Call_Drop_non_VAMOS
_Vamos_1_Rate

GQSCDNVV2R

Call_Drop_non_VAMOS
_Vamos_2_rate

NPO Formula

Description

Total number of 48.008 CLEAR REQUEST


Call_Drop_non_VAMOS_non_SAIC sent to the MSC for speech CS calls in
+Call_Drop_non_VAMOS_SAIC+C TCH established phase (traffic) in nonall_Drop_non_VAMOS_Vamos_1+ VAMOS mode.
Call_Drop_non_VAMOS_Vamos_2 Handover failures are not taken into
account.
Rate of 48.008 CLEAR REQUEST sent to
Call_Drop_non_VAMOS_non_SAIC the MSC for speech CS calls in TCH
/Call_Drop_non_VAMOS_Total
established phase (traffic) in non-VAMOS
mode related to non-SAIC capable MS.
Rate of 48.008 CLEAR REQUEST sent to
Call_Drop_non_VAMOS_SAIC/Call the MSC for speech CS calls in TCH
_Drop_non_VAMOS_Total
established phase (traffic) in non-VAMOS
mode related to SAIC capable MS.
Rate of 48.008 CLEAR REQUEST sent to
Call_Drop_non_VAMOS_VAMOS_1 the MSC for speech CS calls in TCH
/Call_Drop_non_VAMOS_Total
established phase (traffic) in non-VAMOS
mode related to VAMOS1 capable MS.
Rate of 48.008 CLEAR REQUEST sent to
Call_Drop_non_VAMOS_VAMOS_2 the MSC for speech CS calls in TCH
/Call_Drop_non_VAMOS_Total
established phase (traffic) in non-VAMOS
mode related to VAMOS2 capable MS.

144
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

PERFORMANCE EVALUATION
NEW VAMOS INDICATORS (20/24)
NPO indicator NPO Long
ref name
Name

GTCDT1APN

GTCDT2APN

NPO Formula

Description

SCPIR_Distribution_First_Interval_Non_SAIC_Vamo
s_1+SCPIR_Distribution_First_Interval_Non_SAIC_ First Interval of distribution of
Vamos_2+SCPIR_Distribution_First_Interval_Saic_S SCPIR for all pairs. Accumulates
SCPIR_Distrib aic+SCPIR_Distribution_First_Interval_SAIC_Vamos the distribution of calls whose
ution_First_In _1+SCPIR_Distribution_First_Interval_SAIC_Vamos SCPIR lies during a measurement
terval_All_Pai _2+SCPIR_Distribution_First_Interval_Vamos_1_Va reporting period within the first
rs
mos_1+SCPIR_Distribution_First_Interval_Vamos_ SCPIR range defined by the values
1_Vamos_2+SCPIR_Distribution_First_Interval_Va strictly below the threshold
mos_2_Vamos_1+SCPIR_Distribution_First_Interva SCPIR_NON_SAIC_VAMOS1_THR_
l_Vamos_2_Vamos_2
1.
Second Interval of distribution of
SCPIR for all pairs. Accumulates
SCPIR_Distribution_Second_Interval_Non_SAIC_Va the distribution of calls whose
mos_1+SCPIR_Distribution_Second_Interval_Non_ SCPIR lies during a measurement
SCPIR_Distrib SAIC_Vamos_2+SCPIR_Distribution_Second_Interv reporting period within the second
ution_Second al_Saic_Saic+SCPIR_Distribution_Second_Interval_ SCPIR range defined by the values
_Interval_All_ SAIC_Vamos_1+SCPIR_Distribution_Second_Interv between the thresholds
Pairs
al_SAIC_Vamos_2+SCPIR_Distribution_Second_Int [SCPIR_NON_SAIC_VAMOS1_THR
erval_Vamos_1_Vamos_1+SCPIR_Distribution_Sec _1,
ond_Interval_Vamos_1_Vamos_2+SCPIR_Distributi SCPIR_NON_SAIC_VAMOS1_THR_
on_Second_Interval_Vamos_2_Vamos_1+SCPIR_Di 2 [.
stribution_Second_Interval_Vamos_2_Vamos_2

145
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

PERFORMANCE EVALUATION
NEW VAMOS INDICATORS (21/24)
NPO indicator NPO Long
ref name
Name

GTCDT3APN

GTCDT4APN

GTCDTAIN

NPO Formula

Description

Third Interval of distribution of


SCPIR_Distribution_Third_Interval_Non_SAIC_Vam SCPIR for all pairs. Accumulates
os_1+SCPIR_Distribution_Third_Interval_Non_SAI the distribution of calls whose
C_Vamos_2+SCPIR_Distribution_Third_Interval_S SCPIR lies during a measurement
SCPIR_Distrib
aic_Saic+SCPIR_Distribution_Third_Interval_SAIC_ reporting period within the third
ution_Third_I
Vamos_1+SCPIR_Distribution_Third_Interval_SAIC SCPIR range defined by the values
nterval_All_Pa
_Vamos_2+SCPIR_Distribution_Third_Interval_Va between the thresholds
irs
mos_1_Vamos_1+SCPIR_Distribution_Third_Interv [SCPIR_NON_SAIC_VAMOS1_THR_
al_Vamos_1_Vamos_2+SCPIR_Distribution_Third_ 2
Interval_Vamos_2_Vamos_1+SCPIR_Distribution_ ,SCPIR_NON_SAIC_VAMOS1_THR_
Third_Interval_Vamos_2_Vamos_2
3[.
SCPIR_Distribution_Fourth_Interval_Non_SAIC_Va
mos_1+SCPIR_Distribution_Fourth_Interval_Non_ Fourth Interval of distribution of
SAIC_Vamos_2+SCPIR_Distribution_Fourth_Interv SCPIR for all pairs. Accumulates
SCPIR_Distrib al_Saic_Saic+SCPIR_Distribution_Fourth_Interval_ the distribution of calls whose
ution_Fourth_ SAIC_Vamos_1+SCPIR_Distribution_Fourth_Interv SCPIR lies during a measurement
Interval_All_P al_SAIC_Vamos_2+SCPIR_Distribution_Fourth_Int reporting period within the fourth
airs
erval_Vamos_1_Vamos_1+SCPIR_Distribution_Fou SCPIR range defined by the values
rth_Interval_Vamos_1_Vamos_2+SCPIR_Distributi strictly above the threshold
on_Fourth_Interval_Vamos_2_Vamos_1+SCPIR_Di [SCPIR_NON_SAIC_VAMOS1_THR_
stribution_Fourth_Interval_Vamos_2_Vamos_2
3.
SCPIR_Distribution_First_Interval_All_Pairs+SCPIR
SCPIR_Distrib
_Distribution_Second_Interval_All_Pairs+SCPIR_Di
ution_All_Inte
stribution_Third_Interval_All_Pairs+SCPIR_Distribu Incremented when a SCPIR in any
rval
tion_Fourth_Interval_All_Pairs
range 4 is applied to a channel
146
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

PERFORMANCE EVALUATION
NEW VAMOS INDICATORS (22/24)
NPO indicator
ref name
GTCDT1APR
GTCDT2APR
GTCDT3APR
GTCDT4APR

GTCHOINPAN

GTCHOINSUN

NPO Long Name

NPO Formula

Description

SCPIR_Distribution_First_Inter
SCPIR_Distribution_First_Int
Rate of SCPIR in range 1 applied to a
val_All_Pairs/SCPIR_Distributio
erval_All_Pairs_Rate
channel
n_All_Interval
SCPIR_Distribution_Second_In
SCPIR_Distribution_Second_
Rate of SCPIR in range 2 applied to a
terval_All_Pairs/SCPIR_Distrib
Interval_All_Pairs_Rate
channel
ution_All_Interval
SCPIR_Distribution_Third_Inte
SCPIR_Distribution_Third_In
Rate of SCPIR in range 3 applied to a
rval_All_Pairs/SCPIR_Distributi
terval_All_Pairs_Rate
channel
on_All_Interval
SCPIR_Distribution_Fourth_Int
Rate of SCPIR in range 4 applied to a
SCPIR_Distribution_Fourth_I
erval_All_Pairs/SCPIR_Distribu
nterval_All_Pairs_Rate
channel
tion_All_Interval
RTCH_HO_non_SAIC_Intra_Pa
iring_Attempt+RTCH_HO_SAI
Number of intra-cell TCH (in HR or
RTCH_HO_VAMOS_Intra_Pai C_Intra_Pairing_Attempt+RTC
FR usage) handover pairing attempt
ring_Attempt
H_HO_VAMOS_1_Intra_Pairing
to VAMOS mode
_Attempt+RTCH_HO_VAMOS_
2_Intra_Pairing_Attempt
RTCH_HO_non_SAIC_Intra_su
ccess+RTCH_HO_SAIC_Intra_
RTCH_HO_VAMOS_Intra_Pai
Number of intra-cell TCH (HR or FR)
success+RTCH_HO_VAMOS_1
ring_Success
handover successes to VAMOS mode
_Intra_success+RTCH_HO_VA
MOS_2_Intra_success

147
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

PERFORMANCE EVALUATION
NEW VAMOS INDICATORS (23/24)
NPO indicator
ref name
GTCHOINFAN

GTCHOINSUR
GTCHOINFAR

GTCNARQTN

GTCNAPTTN

GTCNAATN

NPO Long Name

NPO Formula

Description

RTCH_HO_VAMOS_Intra_Pairing_Atte
Number of intra-cell TCH (HR
RTCH_HO_VAMOS_Intra_Pa mptor FR) handover fail to VAMOS
iring_Fail
RTCH_HO_VAMOS_Intra_Pairing_Succe
mode
ss
RTCH_HO_VAMOS_Intra_Pairing_Succe Rate of intra-cell TCH (HR or
RTCH_HO_VAMOS_Intra_Pa
ss/RTCH_HO_VAMOS_Intra_Pairing_Att FR) handover successes to
iring_Success_Rate
empt
VAMOS mode
RTCH_HO_VAMOS_Intra_Pairing_Fail/R Rate of intra-cell TCH (HR or
RTCH_HO_VAMOS_Intra_Pa
TCH_HO_VAMOS_Intra_Pairing_Attemp FR) handover fail to VAMOS
iring_Fail_Rate
t
mode
Number of TCH normal
RTCH_assign_non_SAIC_request+RTC
asssignment request, from MS
RTCH_assign_request_VAM H_assign_SAIC_request+RTCH_assign
capable of VAMOS, in VAMOS
OS_capable_MS
_VAMOS_1_request+RTCH_assign_VA
cell (The request might be for
MOS_2_request
Pairing in VAMOS or not)
RTCH_assign_non_SAIC_Pairing_Attem
pted_Triggered+RTCH_assign_SAIC_P Number of TCH normal
assignment from mobile for
RTCH_assign_Pairing_Attem airing_Attempted_Triggered
pted_Triggered_VAMOS
+RTCH_assign_VAMOS_1_Pairing_Atte which pairing attempt is
mpted_Triggered+RTCH_assign_VAMO triggered
S_2_Pairing_Attempted_Triggered
RTCH_assign_non_SAIC_allocated+RT Number of TCH normal
assignment from mobile whose
RTCH_assign_allocated_suc CH_assign_SAIC_allocated
cess_VAMOS
+RTCH_assign_VAMOS_1_allocated+R channel is allocated (after
TCH_assign_VAMOS_2_allocated
pairing)
148
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

PERFORMANCE EVALUATION
NEW VAMOS INDICATORS (24/24)
NPO indicator
ref name
GTCNAPTUNN
GTCNAPTSUR
GTCNAPTUNSR
GTCNAPTVR

GTCVAPTN

GTCVAUPTN

NPO Long Name

NPO Formula

Description

RTCH_assign_Pairing_Attempted_
RTCH_assign_allocated_u
Number of not successful TCH
Triggered_VAMOSnsuccess_VAMOS
normal asssignment allocation
RTCH_assign_allocated_VAMOS
RTCH_assign_allocated_success_V Rate of successful TCH normal
RTCH_assign_VAMOS_Su
AMOS\RTCH_assign_Pairing_Atte asssignment from mobile whose
ccessful_Pairing_Rate
mpted_Triggered_VAMOS
channel is allocated (after pairing)
RTCH_assign_allocated_unsuccess Rate of unsuccessful TCH normal
RTCH_assign_VAMOS_Un
_VAMOS\RTCH_assign_Pairing_Att asssignment from mobile whose
Successful_Pairing_Rate
empted_Triggered_VAMOS
channel is allocated (after pairing)
RTCH_assign_attempt_VA RTCH_assign_Pairing_Attempted_
Rate of TCH normal assignment that
MOS_MS_VAMOS_mode_ Triggered_VAMOS/RTCH_assign_r
will attempt VAMOS mode
Rate
equest_VAMOS_capable_MS
Number of VAMOS pairing (due to
VAMOS_pairings_per_call_non_SAI any reason) per CS call for VAMOS
C+VAMOS_pairings_per_call_SAIC capable MS.A CS call can be paired
VAMOS_pairings_per_call +VAMOS_pairings_per_call_Vamos due to its own TCH assignment (at
_1+VAMOS_pairings_per_call_Va establishment or at handover) or
mos_2
because another call is paired with it
on a radio time slot.
VAMOS_unpairings_per_call_non_ Number of unpairing (due to any
SAIC+VAMOS_unpairings_per_call reason e.g. release of paired call)
VAMOS_unpairings_per_c
_SAIC+VAMOS_unpairings_per_ca per CS call for VAMOS capable MS.
all
ll_Vamos_1+VAMOS_unpairings_p Release of the call is not considered
er_call_Vamos_2
as unpairing.
149
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

4 | PERFORMANCE EVALUATION
4.3 | MODIFIED VAMOS INDICATORS

150
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

PERFORMANCE EVALUATION
CHANGED VAMOS INDICATORS (1/3)
NPO indicator
ref name

NPO Long Name

NPO Formula

GTCRRIF1N

RTCH_idle_interference_band1

MC320a

GTCRRIF2N

RTCH_idle_interference_band2

MC320b

GTCRRIF3N

RTCH_idle_interference_band3

MC320c

GTCRRIF4N

RTCH_idle_interference_band4

MC320d

GTCRRIF5N

RTCH_idle_interference_band5

MC320e

Description
Average number of radio timeslots with free
resources (timeslot in TCH usage and dynamic
SDCCH/8 allocated as TCH) belonging to the
interference band 1. This number is updated
upon the receipt of 48.058 RF RESOURCE
INDICATION. In this message, one interference
level is reported for every time slot with an idle
channel or an idle subchannel.
Average number of radio timeslots with free
resources (timeslot in TCH usage and free
dynamic SDCCH/8 allocated as TCH) belonging
to the interference band 2.
Average number of radio timeslots with free
resources (timeslot in TCH usage and free
dynamic SDCCH/8 allocated as TCH) belonging
to the interference band 3.
Average number of radio timeslots with free
resources (timeslot in TCH usage and free
dynamic SDCCH/8 allocated as TCH) belonging
to the interference band 4.
Average number of radio timeslots with free
resources (timeslot in TCH usage and free
dynamic SDCCH/8 allocated as TCH) belonging
to the interference band 5.

151
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

PERFORMANCE EVALUATION
CHANGED VAMOS INDICATORS (2/3)
NPO indicator
ref name

NPO Long Name

NPO Formula

GTCTRCAMN

RTCH_allocated_peak_avg

MC29a

GTCTRCAMN_MA

RTCH_allocated_peak

MC29a

GTCTRCAMN_X

RTCH_allocated_peak

MC29a

GTCTRFDT

RTCH_DCS_full_occy_total

MC380e

GTCTRFGT

RTCH_GSM_full_occy_total MC380c

GTCTRHDT

RTCH_DCS_half_occy_tota
MC380f
l

GTCTRHGT

RTCH_GSM_half_occy_tota
MC380d
l

Description
Maximum number of simultaneously busy TCH
radio timeslots (in HR or FR usage) and
simultaneously busy dynamic SDCCH/8 radio
timeslots allocated as TCH.
Maximum number of simultaneously busy TCH
radio timeslots (in HR or FR usage) and
simultaneously busy dynamic SDCCH/8 radio
timeslots allocated as TCH.
Maximum number of simultaneously busy TCH
radio timeslots (in HR or FR usage) and
simultaneously busy dynamic SDCCH/8 radio
timeslots allocated as TCH.
Total time occupancy of Full Rate (classical FR,
EFR and AMR FR) RTCH channels in the
DCS/PCS frequency band.
Total time occupancy of Full Rate (classical FR,
EFR, AMR FR and AMR WB) RTCH channels in
the GSM frequency band.
Total time occupancy of Half Rate (classical HR
and AMR HR) RTCH channels in the DCS/PCS
frequency band.
Total time occupancy of Half Rate (classical HR
and AMR HR) RTCH channels in the GSM
frequency band.

152
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

PERFORMANCE EVALUATION
CHANGED VAMOS INDICATORS (3/3)
NPO indicator
ref name

NPO Long Name

NPO
Formula

GTCOCTSA

RTCH_busy_TS_avg

GTCCGT

RTCH_time_system_conge
MC34
stion

GTCAVSAN

RTCH_static_available_nb_
MC250
avg

GTCAVSAN_AW
GTCAVSAN_BH
GTCAVSAN_MA
GTCAVSAN_MW
GDYAHCATAN

RTCH_static_available_nb_
avg_WH
RTCH_static_available_nb_
avg_BH
RTCH_static_available_nb_
avg_max
RTCH_static_available_nb_
avg_max_WH
RTCH_dynamic_allocated_
nb_avg

MC28a

MC250
MC250
MC250
MC250
MC801a

Description
Average number of busy TCH radio timeslot (in FR or
HR usage, in traffic or in signaling mode) and busy
dynamic SDCCH/8 radio timeslot allocated as TCH.
Cumulated time (in seconds) during which there is no
free radio timeslot to serve an incoming FR TCH
request.
Average number of available static radio timeslots for
traffic usage (i.e TCH (HR or FR usage in VAMOS
mode or not) or PDCH) at any hour.
-The timeslot is available if it is not "blocked" or "out
of service".
Average number of available static radio timeslots for
traffic usage at any hour.
Average number of available static radio timeslots for
traffic usage at any hour.
Average number of available static radio timeslots for
traffic usage at any hour.
Average number of available static radio timeslots for
traffic usage at any hour.
Average number of busy dynamic SDCCH/8 timeslots
allocated as TCH (in FR or HR usage in VAMOS mode
and non-VAMOS mode) at any hour.

153
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

4 | PERFORMANCE EVALUATION
4.4 | NPO VAMOS REPORTS

154
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

PERFORMANCE EVALUATION
NPO NEW VAMOS REPORTS
(1/1)

NPO report name

Alc_Mono_Vamos

Views in the report

Description of the views

Call_Drop_VAMOS

Call Drop in VAMOS mode

Call_Drop_VAMOS_Impact

Call Drop in VAMOS mode and non-VAMOS

Call_Drop_non_VAMOS

Call Drop in non-VAMOS mode

SCPIR_Distribution

SCPIR Distribution Rate per intervals

CHO_VAMOS_Paring

Vamos Pairing

CHO_VAMOS_UnParing

Vamos UnParing

RTCH_HO

Vamos Handover

RTCH_Assign

RTCH Assignment Attempts/Success

155
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

CONTENTS
1 | FEATURE DESCRIPTION
2 | FEATURE ACTIVATION STRATEGY
3 | TEST STRATEGY
4 | PERFORMANCE EVALUATION
5 | RESTRICTIONS / OTHER ISSUES
6 | CONCLUSION
7 | APPENDIX A: VAMOS SUITABILITY EVALUATION
8 | APPENDIX B: VAMOS SIMULATION RESULTS
9 | APPENDIX C: VAMOS DEPENDENCIES - BSSoIP
156
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

Restrictions / Other Issues


N/A

157
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

CONTENTS
1 | FEATURE DESCRIPTION
2 | FEATURE ACTIVATION STRATEGY
3 | TEST STRATEGY
4 | PERFORMANCE EVALUATION
5 | RESTRICTIONS / OTHER ISSUES
6 | CONCLUSION
7 | APPENDIX A: VAMOS SUITABILITY EVALUATION
8 | APPENDIX B: VAMOS SIMULATION RESULTS
9 | APPENDIX C: VAMOS DEPENDENCIES - BSSoIP
158
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

Conclusion

Supported by its own simulation results, Alcatel-Lucent believes that VAMOS


can bring to mobile operators important network capacity gains in
many scenarios (New deployment, swap, capacity extension, frequency
refarming), the only main condition being that the network has enough quality
margin before VAMOS feature activation.

Contrary to the BSS (New modulation, Radio resource allocation, Power control,
), VAMOS has low impact on terminals, which is a good news for its
ecosystem given the relevance of mobile penetration for such kind of features.

As a matter of fact:

Legacy SAIC mobiles can be used in VAMOS operation, in order to reach significant
VAMOS gains even when VAMOS mobile penetration is still low.

Efforts requested to mobile station suppliers to obtain VAMOS Level 1 mobiles from
Legacy SAIC ones is quite limited: only the new training sequences have to be
implemented. First VAMOS level 1 mobiles should be available first half of 2012.
Prototypes already exist, which have been already used by Alcatel-Lucent for test
purposes.

Due to more powerful interference rejection algorithms, VAMOS level 2 mobiles will
require more processing, but it seems reasonable to expect the first ones during the
second half of 2012.

Therefore, Alcatel-Lucent will provide VAMOS feature within its B12


BSS Release: it will be supported by legacy and new equipments.
159
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

CONTENTS
1 | FEATURE DESCRIPTION
2 | FEATURE ACTIVATION STRATEGY
3 | TEST STRATEGY
4 | PERFORMANCE EVALUATION
5 | RESTRICTIONS / OTHER ISSUES
6 | CONCLUSION
7 | APPENDIX A: VAMOS SUITABILITY EVALUATION
8 | APPENDIX B: VAMOS SIMULATION RESULTS
9 | APPENDIX C: VAMOS DEPENDENCIES - BSSoIP
160
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

VAMOS SUITABILITY EVALUATION


CASE STUDY 1 - NETWORK QUALITY

GSM & EGSM frequency band:

DCS frequency band:

8 frequencies in GSM (Bandwidth = 1.8 MHz) + 25 frequencies EGSM (BW = 5 MHz)


Mixed band: BCCH frequency reuse = TCH frequency reuse = 16.5
Average number of TRX: 2
Tight frequency band, higher interference than DCS band

76 frequencies, including 1 guard frequency between BCCH & TCH (BW = 15.2 MHz)
Dedicated band: 38 BCCH channels (BCCH frequency reuse = 38) and 37 TCH
channels (TCH frequency reuse = 22.29)
Average number of TRX for outdoor cells: 2.8
Average number of TRX for indoor cells: 2.15
Very relaxed frequency band => No interference issue on DCS band

C/I values on the whole network show low interference level:


From drive test: average C/I for GSM band: 17.56, for DCS band: 26.3

Bad quality emergency HO = 6% of overall HO causes


161
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

VAMOS SUITABILITY EVALUATION


CASE STUDY 1 OTHER CRITERIA

General network settings

HR penetration: HR is activated on 80% of the cells, 60-65% of the calls are HR


Power control and DTX (Discontinuous Transmission):

DL Power Control is activated on 93.5% of the cells, DL DTX activated on all cells
UL DTX used only for FR, not activated for HR

Frequency Hopping mode: Baseband Hopping is the most used hopping mode,
activated on 83.4% of the cells; other cells are No Hopping

H/W: All Twin TRA, Mx-BSC

VAMOS can provide important capacity gains in the DCS 1800 band (converting
the big quality margin into capacity margin). For GSM 900, VAMOS gain could be
reduced due to the tighter frequency spectrum

This network has a high penetration of new MSs:

Almost 89% of the MSs are Release 4 onwards (supporting GERAN FEATURE PACKAGE
1) ; around 38% are DTM capable (DTM is a feature supported by advanced MSs)
Good probability to have SAIC capable MSs in the network
162
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

VAMOS SUITABILITY EVALUATION


CASE STUDY 2 - NETWORK QUALITY

ARCS per frequency band (4 OMCs) => good frequency reuse size in PGSM
& DCS cells

From drive tests, C/I in GSM band = 17.61, 18.33 in DCS band

% DL quality HO = 18% (relatively high)

Overall: Medium network quality, some room available for VAMOS


163
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

VAMOS SUITABILITY EVALUATION


CASE STUDY 2 OTHER CRITERIA

General settings:

RH/NH frequency hopping mode used, but works as BBH (except that BCCH TRX
is not hopping) => MAL length = number of hopping TRX

HR is activated on only 20% of the cells

AMR is not activated

DL Power Control is activated on 93% of the cells, UL PC on 96% of the cells

DTX (UL & DL) is activated only for FR codecs

Average penetration of Rel-4 mobiles is around 52%


This indicates a significant population of legacy non-SAIC mobiles, thus reducing
VAMOS gains

Conclusion: There is indeed some room for VAMOS introduction, thanks to


the quality margin (depicted by good ARCS and C/I values). However, VAMOS
introduction doesnt make sense in the short term:
[BACK]
Capacity can be increased by massive HR activation
Today, the relatively low penetration of advanced mobiles reduces VAMOS gains
164
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

CONTENTS
1 | FEATURE DESCRIPTION
2 | FEATURE ACTIVATION STRATEGY
3 | TEST STRATEGY
4 | PERFORMANCE EVALUATION
5 | RESTRICTIONS / OTHER ISSUES
6 | CONCLUSION
7 | APPENDIX A: VAMOS SUITABILITY EVALUATION
8 | APPENDIX B: VAMOS SIMULATION RESULTS
9 | APPENDIX C: VAMOS DEPENDENCIES - BSSoIP
165
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

VAMOS SIMULATION RESULTS


DIFFERENT STUDIES

VAMOS Feature Simulation Using L2S Simulator


Simulations performed at system level to estimate
maximum capacity, pairing/un-pairing algorithms and
computing user satisfaction rate.

Impacts of VAMOS Parameters on Performance


Impact of the different configurations on the reachable
capacity with VAMOS and on the performance (Power
Control, Pairing / un-pairing, etc.).
Deduce from the simulations the best set of default
values for the VAMOS configuration.
166
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

VAMOS L2S SIMULATION


Summary of performed simulations
2 kinds of scenarios:
Classical (w/o re-farming)
Re-farming

For each scenario, 2 cases:


Pairing of VAMOS 1 mobiles
Pairing of SAIC mobiles

For each case


FR mobiles
HR mobiles

167
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

VAMOS L2S SIMULATION


Principles and assumptions
Principles

Simulations at system (Network) level


Only DL is simulated since DL is expected to be the limiting link for VAMOS
Idea is not to simulate the dynamic behaviour with high and low load periods, but to estimate
maximum capacity
The network is progressively loaded and remains loaded up to the end of the simulation
Allocation in VAMOS is possible when 50% of load is reached in the cell

The simulator computes RX_LEV, RX_QUAL and FER considering co-channel and adjacent
interferences and using Link-to-System mapping tables.
This feeds the power control pairing/un-pairing algorithms and allows computing user satisfaction rate

Simulated time: around 3 hours

Main assumptions and parameters


The network has 225 identical cells - Mean call duration of 90s with a minimum of 5s
The path loss model is the one defined in TR 30.03U for vehicular test environment
Attenuation of 3dB for AQPSK maximum power compared to GMSK
Either FR or HR per simulation: No FR/HR adaptation - No AMR codec adaptation
Inter-cell HOs are only based on MS location in the network (and not based on radio quality)
DTX is not implemented (Foreseen in a next step)
168
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

VAMOS L2S SIMULATION


Scenario 1: Classical case, w/o re-farming (1)
Method (Similar to 3GPP MUROS studies)
Run a simulation with VAMOS disabled. CS load is computed to reach 2% of blocking rate.
If at the end of the simulation, the unsatisfied rate is strictly lower than 5%, run a simulation
with VAMOS enabled and with above CS load.
If at the end of the simulation, the unsatisfied rate is:
Greater than 5%: there is no VAMOS gain for this network.
Else, re-run simulations with increasing CS loads to reach either 2% of blocking rate or 5% of
unsatisfied rate to compute capacity gains
Blocking rate

User satisfaction rate based


on Call FER:
< 2% for at least 95% users in
case of FR channel type,
< 3% for at least 95% users in
case of HR channel type.

Maximum load (i.e.


capacity)

VAMOS disabled
2%

Gain

VAMOS enabled
0%
0%

5%
: Increasing load

169
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

User un-satisfaction
rate

VAMOS L2S SIMULATION


Scenario 1: Classical case, w/o re-farming (2)
Example of simulation run: network similar to Vodafone Qatar

Network definition

170
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

VAMOS L2S SIMULATION


Scenario 1: Classical case, w/o re-farming (3)
Case 1: Only VAMOS 1 capable MS, SCPIR range [-4,+4], FR case
Unsatisfied User versus Blocking Rate
3.0%

2.5%

2.0%
Blocking Rate [%]

3080 Erlang

GAIN

1800 Erlang

Traffic Load Increase

1.5%

Non-Vamos
Vamos

2910 Erlang

1.0%

0.5%

0.0%
0.0%

1840 Erlang

0.5%

1.0%

1.5%

2.0%

2.5%

3.0%

3.5%

4.0%

Unsatisfied User Rate [%]

Capacity gain: 72 %
171
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

4.5%

5.0%

VAMOS L2S SIMULATION


Scenario 1: Classical case, w/o re-farming (4)
Case 1: Only VAMOS 1 capable MS, SCPIR range [-4,+4] , HR case
Unsatisfied User versus Blocking Rate
3.0%

2.5%
6760 Erlang
GAIN

Blocking Rate [%]

2.0%

4000 Erlang

Non-Vamos

1.5%

Vamos

1.0%

5730 Erlang

0.5%

Traffic Load Increase

4100 Erlang
0.0%
0.0%

0.5%

1.0%

1.5%

2.0%

2.5%

3.0%

3.5%

Unsatisfied User Rate [%]

Capacity gain: 69 %
172
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

4.0%

4.5%

5.0%

VAMOS L2S SIMULATION


Scenario 1: Classical case, w/o re-farming (5)
Case 2: Only SAIC capable MS, SCPIR=0
Degradation of 2dB due to pairing with legacy TSC, FR case
Unsatisfied User versus Blocking Rate
3.0%

2.5%
2410 Erlang

GAIN
Blocking Rate [%]

2.0%
1800 Erlang
1.5%

Non-Vamos

2190 Erlang

Vamos
Traffic Load Increase

1.0%

1830 Erlang

0.5%

0.0%
0.0%

0.5%

1.0%

1.5%

2.0%

2.5%

3.0%

3.5%

4.0%

Unsatisfied User Rate [%]

Capacity gain: 35 %
173
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

4.5%

5.0%

VAMOS L2S SIMULATION


Scenario 1: Classical case, w/o re-farming (6)
Case 2: Only SAIC capable MS, SCPIR=0
Degradation of 2dB due to pairing with legacy TSC, HR case
Unsatisfied User versus Blocking Rate
3.0%

2.5%
5600 Erlang
Blocking Rate [%]

2.0%

1.5%

4000 Erlang

GAIN

Non-Vamos
Vamos

4890 Erlang

Traffic Load Increase

1.0%

4100 Erlang

0.5%

0.0%
0.0%

0.5%

1.0%

1.5%

2.0%

2.5%

3.0%

3.5%

4.0%

Unsatisfied User Rate [%]

Capacity gain: 40 %
174
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

4.5%

5.0%

VAMOS L2S SIMULATION


Scenario 1: Classical case, w/o re-farming
Sum up
Gain [%]

Erl / TRX

EFL [%]

ENT

ENT_PERC [%]

3.98

3.45%

1.1

56.8%

VAMOS enabled
Case 1: VAMOS1 VAMOS1

71.8%

6.84

5.92%

1.9

96.8%

VAMOS enabled
Case 2: SAIC - SAIC

34.8%

5.36

4.64%

1.5

76.2%

Gain [%]

Erl / TRX

EFL [%]

ENT

ENT_PERC [%]

8.89

8.29%

1.4

67.7%

VAMOS enabled
Case 1: VAMOS1 VAMOS1

68.8%

15.01

13.99%

2.3

113.8%

VAMOS enabled
Case 2: SAIC - SAIC

40.1%

12.46

11.62%

1.9

94.6%

VAMOS disabled

FR

VAMOS disabled

HR

Effective Frequency Load (EFL):


EFL =

Capacity
100%
N _ Freq av(NFR _ TS _ per _ TRX )

Equivalent Number of TRX (ENT):


ENT =

N _ TS[Capacity ]
av(N TS _ per _ TRX )

Capacity
N_Freq
av(NFR_TS_per_TRX)
N_TS[Capacity]

- N_TRX

:
:
:
:

Capacity in Erlang as determined by simulation,


Total number of frequencies,
Average number of available FR timeslot per TRX.
Number of TS obtained using the Erlang B at 2%
blocking rate for the supported traffic as determined by
simulation.
: Number of TRX

ENT_PERC = ENT / N_TRX


175
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

VAMOS L2S SIMULATION


Scenario 2: Re-farming (1)
Method
Run a simulation before re-farming with VAMOS disabled. The input CS load is
computed to reach 2% of blocking rate
Run a simulation after re-farming with VAMOS disabled
Run a simulation after re-farming and with VAMOS enabled and an input load
computed to
reach the 2% of blocking rate as if VAMOS was not enabled
But as VAMOS is enabled, the blocking rate will be much lower than 2%.
Then run a simulation with increased input load to reach 2% blocking rate

176
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

VAMOS L2S SIMULATION


Scenario 2: Re-farming (2)
Example of simulation run

Network definition (FR)

177
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

VAMOS L2S SIMULATION


Scenario 2: Re-farming (3)
Example of simulation run

Network definition (HR)

178
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

VAMOS L2S SIMULATION


Scenario 2: Re-farming (4)
Case 1: Only VAMOS 1 capable MS, SCPIR range [-4,+4] , FR case
Unsatisfied User versus Blocking Rate
3.0%

2.5%

2670 Erlang

Blocking Rate [%]

2.0%

1.5%

3240 Erlang

1790 Erlang

(before refarming)

(after refarming)

2550 Erlang
Non-Vamos
Vamos
Traffic Load Increase

1.0%

0.5%

0.0%
0.0%

1830 Erlang

0.5%

1.0%

1.5%

2.0%

2.5%

3.0%

3.5%

4.0%

4.5%

5.0%

Unsatisfied User Rate [%]

Recovered capacity: 82%


Capacity gain after re-farming: 49 %

(comparison w/ and w/o VAMOS)


179

COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.


ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

5.5%

VAMOS L2S SIMULATION


Scenario 2: Re-farming (5)
Case 1: Only VAMOS 1 capable MS, SCPIR range [-4,+4] , HR case
Unsatisfied User versus Blocking Rate
3.0%

2.5%

6820 Erlang

Blocking Rate [%]

2.0%

4000 Erlang
1.5%

Non-Vamos

(after refarming)
6740 Erlang

Vamos

6100 Erlang

(before refarming)
Traffic Load Increase

1.0%

0.5%
4100 Erlang
0.0%
0.0%

1.0%

2.0%

3.0%

4.0%

5.0%

Unsatisfied User Rate [%]

Recovered capacity: 101%


Capacity gain after re-farming: 70 %

(comparison w/ and w/o VAMOS)


180

COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.


ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

VAMOS L2S SIMULATION


Scenario 2: Re-farming (6)
Case 2: Only SAIC capable MS, SCPIR=0
Degradation of 2dB due pairing with legacy TSC, FR case
Unsatisfied User versus Blocking Rate
3.0%

2.5%
2120 Erlang

Blocking Rate [%]

2.0%
3240 Erlang
1.5%

(before refarming)

1790 Erlang

Non-Vamos

(after refarming)

Vamos

Traffic Load Increase


1830 Erlang

1.0%

0.5%

0.0%
0.0%

1.0%

2.0%

3.0%

4.0%

5.0%

Unsatisfied User Rate [%]

Recovered capacity: 65%


Capacity gain after re-farming: 18%

(comparison w/ and w/o VAMOS)


181

COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.


ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

VAMOS L2S SIMULATION


Scenario 2: Re-farming (7)
Case 2: Only SAIC capable MS, SCPIR=0
Degradation of 2dB due pairing with legacy TSC, HR case
Unsatisfied User versus Blocking Rate
3.0%

2.5%

5420 Erlang

Blocking Rate [%]

2.0%
4000 Erlang

4890 Erlang

(after refarming)

1.5%

Vamos

6740 Erlang
(before refarming)

Traffic Load Increase

1.0%

4100 Erlang

0.5%

0.0%
0.0%

1.0%

Non-Vamos

2.0%

3.0%

4.0%

5.0%

Unsatisfied User Rate [%]

Recovered capacity: 80%


Capacity gain after re-farming: 35%

(comparison w/ and w/o VAMOS)


182

COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.


ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

VAMOS L2S SIMULATION


Scenario 2: Re-farming
Sum up
FR

HR

Gain [%]

Erl / TRX

EFL [%]

ENT

ENT_PERC [%]

VAMOS disabled (3 TRX)

4.80

4.56%

1.9

64.8%

VAMOS disabled (2 TRX)

3.96

5.66%

1.1

56.5%

VAMOS enabled (2 TRX)


Case 1: VAMOS1 VAMOS1

-17.4% / 49.9%

5.94

8.48%

1.7

84.3%

VAMOS enabled (2 TRX)


Case 2: SAIC - SAIC

-34.5% / 18.9%

4.71

6.73%

1.3

67.0%

Gain [%]

Erl / TRX

EFL [%]

ENT

ENT_PERC [%]

VAMOS disabled (3 TRX)

9.97

10.44%

2.2

73.7%

VAMOS disabled (2 TRX)

8.86

10.90%

1.3

67.4%

1.3% / 71.1%

15.16

18.65%

2.3

114.9%

-19.4% / 36.1%

12.05

14.83%

1.8

91.5%

VAMOS enabled (2 TRX)


Case 1: VAMOS1 VAMOS1
VAMOS enabled (2 TRX)
Case 2: SAIC - SAIC

Effective Frequency Load (EFL):


EFL =

Capacity
100%
N _ Freq av(NFR _ TS _ per _ TRX )

Equivalent Number of TRX (ENT):


ENT =

N _ TS[Capacity ]
av(N TS _ per _ TRX )

ENT_PERC = ENT / N_TRX

Capacity
N_Freq
av(NFR_TS_per_TRX)
N_TS[Capacity]

- N_TRX

:
:
:
:

Capacity in Erlang as determined by simulation,


Total number of frequencies,
Average number of available FR timeslot per TRX.
Number of TS obtained using the Erlang B at 2%
blocking rate for the supported traffic as determined by
simulation.
: Number of TRX

183
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

VAMOS L2S SIMULATION


Conclusion and next steps
Those simulation results show important VAMOS capacity gains when
radio conditions are good
Between 49 % and 72 % (with all MSs being VAMOS Level 1 MSs)

Those simulation show also significant SAIC pairing capacity gains


Between 18 % and 40% (with all MSs being Legacy SAIC MSs)

Main next steps


Mixing Legacy MSs, Legacy SAIC MSs and VAMOS-1 MSs
DTX, which should show even higher gains

184
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

VAMOS CONFIGURATION
IMPACT OF PARAMETERS

Impacts of VAMOS Parameters on Performance


Impacts of VAMOS
rameters on perform

185
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

CONTENTS
1 | FEATURE DESCRIPTION
2 | FEATURE ACTIVATION STRATEGY
3 | TEST STRATEGY
4 | PERFORMANCE EVALUATION
5 | RESTRICTIONS / OTHER ISSUES
6 | CONCLUSION
7 | APPENDIX A: VAMOS SUITABILITY EVALUATION
8 | APPENDIX B: VAMOS SIMULATION RESULTS
9 | APPENDIX C: VAMOS DEPENDENCIES - BSSoIP
186
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

VAMOS DEPENDENCIES: BSS OVER IP


IP OVER ETHERNET
Full IP over Ethernet
BTS

IP entry point
in Backhaul Network

DSL (copper)

Eth

PDH/SDH

TC

Ethernet Microwave

Eth

DSLAM
BTS

(Circuit)

BTS

IP Backbone
(Packet)

Eth
BTS

GPON
(PtMultiP fibre)

BTS

SDH
(PtP fibre)

(Sig)

BTS

BSC

Benefits:

SGSN
MFS

9 Simplified network architecture and network operations


9 Unified RAN aggregation and Core Ethernet backhaul network
9 Backhaul costs savings in access and aggregation networks
187
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

VAMOS DEPENDENCIES: BSS OVER IP


IP OVER ETHERNET
Support of mixed mode

TDM BTS
IP BSS / IPoE1 BTS
IP BSS / IPoEth BTS

Eth
BTS

Ethernet
access network

IP Backbone

Eth
TC

Eth
PDH/SDH

E1
BTS

BSC E1

PDH/SDH

E1

MFS

BTS
188
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

VAMOS DEPENDENCIES: BSS OVER IP


IP OVER ETHERNET PREREQUISITES
Native IP transmission for Abis & Ater interfaces over Ethernet
H/W prerequisites:
BTS: Evolium with SUMx boards
TRE generations: G3 onwards
Controllers: Mx-BSC & Mx-MFS
Transcoder: TC G2.5 with TC-STM1 IP boards

S/W prerequisites: B12.1.1


BTS synchronization options:
NTP synchro, with very accurate OCXO in the BTS
GPS synchro

IP backbone SLA (Service Level Agreement) metrics should be checked to


confirm that jitter and delay requirements specified by ITU-T are fulfilled (e.g.
acceptable jitter is about 10% of the total delay)
189
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

VAMOS DEPENDENCIES: BSS OVER IP


IP OVER ETHERNET FOA TEST STRATEGY
Lab phase:
At least 2 BTSs required (1 in TDM and 1 in IP) to test mixed mode and Abis BTS group configuration
Objective: Verification of B12.1.1 non regression and functional validation of IPoEth feature (telecom +
O&M tests)

Pilot phase:
Start with a few BTSs (2-3 BTS) in IP, then progressively move other BTSs to IP to ensure enough
statistical results
Planned tests:

Unitary test in static and mobility conditions,

Voice quality assessment,

Statistical tests

Objective:

Check that the feature does not cause any regressions on QoS, Data Performances, network stability

Verify the feature benefit on:

Dimensioning: resource usage, possibility to compress the CS bandwidth


PS Performance: latency reduction

FOA estimated duration: 4 months


190
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION

VAMOS DEPENDENCIES: BSS OVER IP


IP OVER E1
Abis transmission in IP mode over the existing E1 links, Ater remains on IPoEth
H/W prerequisites:
Controllers: Mx-BSC with new TPGSM V3 (with TPIP) & Mx-MFS
Transcoder: TC-STM1 IP boards

BTS synchronization options:


In mixed mode: Synchronization is similar to B11MR1, BSC synchronization taken from
TDM Ater-mux E1 links
In Full-IP mode: 2 possibilities:
PRC (primary reference clock) from IP/MPLS backhaul, with Synchronous Ethernet used in BH
BTS using NTP and Abis links are in free mode (from internal Mx-BSC clock)

Topologies impact (currently no impact for VFQ):


BTS ring topology is not supported
Star with fractional E1 (based on TDM cross-connect) is not possible in IP transport
mode (only one IPoE1 is supported on E1 link)

BACK
191
COPYRIGHT 2011 ALCATEL-LUCENT. ALL RIGHTS RESERVED.
ALCATEL-LUCENT INTERNAL PROPRIETARY USE PURSUANT TO COMPANY INSTRUCTION