Geran Ur14 Zgo-04-05-Xxx Vamos Feature Guide (v4)

ZGO-04-05-xxx VAMOS
Feature Guide
GERAN UR14
ZGO-04-05-xxx VAMOS Feature Guide

Version Date Author Reviewer Notes
V1.0 2015/07/23 First Release
© 2018 ZTE Corporation. All rights reserved.

ZTE CONFIDENTIAL: This document contains proprietary information of ZTE and is not to be disclosed or used
without the prior written permission of ZTE.
Due to update and improvement of ZTE products and technologies, information in this document is subjected to
change without notice.
ZTE Confidential & Proprietary 1

TABLE OF CONTENTS
1 Feature Attribute............................................................................................................. 5
2 Overview............................................................................................................................5
2.1 Feature Introduction.......................................................................................................... 5
2.2 License Control.................................................................................................................. 8
2.3 Correlation with Other Features...................................................................................... 8
3 Technical Description.................................................................................................... 9
3.1 MS Capability Pre-Check................................................................................................. 9
3.2 Mute SAIC Detection.........................................................................................................9
3.3 SAIC AFC Detection....................................................................................................... 10
3.4 Trigger VAMOS Pairing.................................................................................................. 11
3.5 VAMOS Pairing Algorithm..............................................................................................12
3.5.1 Requirement on Speech Version.................................................................................. 13
3.5.2 Requirement on User Priority........................................................................................ 14
3.5.3 Requirement on Receiving Power Level and Receiving Quality..............................14
3.5.4 Selection of Users with Similar Path Loss................................................................... 15
3.5.5 DL Initial Power Allocation According to the SCPIR.................................................. 15
3.5.6 Pairing Methods............................................................................................................... 16
3.6 VAMOS De-pairing Algorithm........................................................................................17
3.6.1 De-pairing Algorithm When the Power Exceeds Threshold..................................... 17
3.6.2 De-pairing Algorithm When the UL SCPIR Exceeds Threshold.............................. 17
3.6.3 De-pairing Algorithm When the DL SCPIR Exceeds Threshold.............................. 17
3.6.4 De-pairing Algorithm When the UL Quality Exceeds Threshold.............................. 18
3.6.5 De-pairing Algorithm When the DL Quality Exceeds Threshold.............................. 18
3.6.6 De-pairing Algorithm When the Load Decreases....................................................... 18
3.7 VAMOS Power Control................................................................................................... 18
3.8 AFC Power Control......................................................................................................... 21
3.9 Shift SACCH.....................................................................................................................22
3.10 DL Signaling..................................................................................................................... 22
4 Parameters..................................................................................................................... 24
5 Related Counters and Alarms................................................................................... 32

5.1 Related Counters.............................................................................................................32
5.2 Related Alarms.................................................................................................................36
6 Engineering Guide........................................................................................................36
6.1 Application Scenario....................................................................................................... 36
6.2 Feature Activation Procedure........................................................................................ 36
2 ZTE Confidential & Proprietary

6.3 Feature Validation Procedure........................................................................................38

6.3.1 MUTE SAIC MS Capability Detection...........................................错误！未定义书签。
6.3.2 SAIC AFC MS Capability Detection.............................................. 错误！未定义书签。
6.3.3 VAMOS Pairing and De-pairing of FR.......................................... 错误！未定义书签。
6.3.4 VAMOS Pairing and De-pairing of HR......................................... 错误！未定义书签。
6.4 Feature Deactivation Procedure................................................................................... 39
6.5 Network Impact................................................................................................................ 39
7 Abbreviation...................................................................................................................40
8 Reference Document................................................................................................... 40

FIGURES
Figure 2- 1 Channel Frame Structure in VAMOS Mode............................................................... 6

Figure 2- 2 Two Users Multiplexed...................................................................................................7
Figure 3- 1 Flow Chart of Mute SAIC Detection...........................................................................10
Figure 3- 2 Flow Chart of SAIC AFC Detection............................................................................11
Figure 3- 3 User Classification According to the Receiving Quality and Power Level...........15
Figure 6- 1 Configuration Interface................................................................................................ 37
Figure 6- 2 Configuring TSC2......................................................................................................... 38
TABLES
Table 2- 1 License Control List......................................................................................................... 8

Table 4- 1 Parameters List.............................................................................................................. 24
Table 5- 1 Counter List.....................................................................................................................32

1 Feature Attribute
BSC/RNC Version: [ZXUR 9000 GSM(V6.50.30)]
BTS/Node B Version: [SDR V4.11 and later version]
Attribute: [Optional]
Related Network Element:
NE Name Related or Not Special Requirements
MS/UE √
BTS/Node B √
BSC/RNC √
iTC -
MSC -
MGW -
SGSN -
GGSN -
HLR -
“√”: Related, “-”: Irrelative
2 Overview
2.1 Feature Introduction
Voice services over Adaptive Multi-user Channels on One Slot (VAMOS) refers to that an
ARFCN multiplexes several voice service users in one timeslot, enhancing the network
capacity.
Because one timeslot is able to bear one common FR voice service or two common HR
services, the following channel combinations might exist in VAMOS mode:
2 FR users multiplex one timeslot.
1 FR user + 2 HR users multiplex one timeslot.
3 HR users multiplex one timeslot.

4 HR users multiplex one timeslot.
The following figure shows the frame structure of channel combination.
Figure 2- 1 Channel Frame Structure in VAMOS Mode
When two users share one timeslot, ARFCN and TDMA frame numbers make up one
VAMOS pair where each channel is a VAMOS sub-channel. In a VAMOS pair, the only
difference between two users is their different training sequence.
The following figure shows how two users are multiplexed. Each user takes one VAMOS
sub-channel, which is differentiated by the training sequence.

Figure 2- 2 Two Users Multiplexed
For the traditional CS voice service, one user takes one timeslot. Both uplink and
downlink adopt the GMSK (Gaussian Minimum Shift-frequency Keying) modulation
scheme. For VAMOS mode, there are two users in one timeslot. The BTS sends an
a-QPSK (Adaptive Quadrature Phase Shift Keying) signal, and then the mobile station
eliminates other signals as interference through the training sequence and interference
cancellation to demodulate its own signals. For the uplink, the multiplexed two MSs still
use the GMSK modulation to send signals in the timeslot, and the BTS uses the
enhanced demodulation algorithm to demodulate the signals and differentiate the users
by training sequence.
The VAMOS technology enables two users to use the same channel simultaneously.
When two users are using resources of the same channel, they can make calls normally
and in the meantime their mutual interference is tolerable. This is the principle of
selecting paired users. At least one member of a VAMOS pair must have the
anti-interference capability. Whether an MS supports VAMOS is reported by the MS itself,
which is carried in Classmark3. The BSC gets such information, which carries two fields,
VAMOS capability and DARP capability, from the signaling.
There are two VAMOS levels, VAMOS I and VAMOS II. Meanwhile, there are three
DARP levels, DARP 0, DARP 1 and DARP 2. The VAMOS I, VAMOS II and DARP 2
MSs can directly execute VAMOS pairing. The handset which is incapable of VAMOS but

capable of DARP 1 is the so called SAIC handset. Many SAIC handsets do not report
that they support SAIC (DARP=1) and are thus called Mute SAIC Handsets. It is
necessary for these mute SAIC handsets to execute MUTE SAIC detection. Though
some MSs such as the Nokia handsets report they support SAIC (DARP=1), they do not
actually support VAMOS due to the AFC algorithm. AFC detection (we call these
handsets the SAIC AFC handsets) is essential to check whether they support VAMOS
pairing.
2.2 License Control
Table 2- 1 License Control List
License Configured Sales

Feature ID Feature Name
Control Item NE Unit
ZGO-04-05-XXX VAMOS VAMOS BSC TRX
2.3 Correlation with Other Features
1. Required Features
None
2. Mutually Exclusive Features
ZGO-04-01-001 Extended Cell Coverage
3. Affected Features
ZGO-03-02-005 Dynamic Half Rate Allocation

3 Technical Description
3.1 MS Capability Pre-Check
Before detecting the MS, first pre-check whether it is eligible for the detection. Check
whether the receiving quality and power level meet the threshold configured on the
OMCR. If the power level is not within the detection scope configured on the OMCR,
adjust it through power control. Whether to perform power control separately is
configurable. If the power level after the adjustment still fails to meet the threshold for
pre-check, the MS capability detection will not be performed during this call.
3.2 Mute SAIC Detection
Suppose the system supports MUTE SAIC detection. When a newly admitted speech
user reports his/her MS as a traditional one (DARP=0, VAMOS=0) and no record of the
MS capability is found on the BSC, it is necessary to inform the BTS to check the SAIC
capability of the MS.
Upon receiving the message that carries MUTE SAIC performance test indication, the
BTS begins to detect SAIC performance and sends detection signals to the MS
periodically. It adds some DL interference when the DL RQ runs good, and determines
whether the MS supports SAIC through the RQ value the MS reports.
When the detection finishes, the BTS sends a message to inform the BSC of the MS
SAIC capability. The BSC records the MS capability for the reference of VAMOS pairing.
Whether to enable this feature depends on the cell-level switch “If support MUTE SAIC
detection”. Figure 3-1 shows the flow chart.

Figure 3- 1 Flow Chart of Mute SAIC Detection
3.3 SAIC AFC Detection
Suppose the system supports SAIC AFC detection. When a newly admitted speech user
reports his/her MS capability as DARP=1 and no record of the MS capability is found on
the BSC, it is necessary to inform the BTS to check the SAIC AFC capability of the MS.
Upon receiving the message that carries SAIC AFC detection indication, the BTS begins
to detect SAIC AFC performance and sends α-QPSK signals to the MS periodically.
Some interference is added during the detection. The RQ and frequency deviation
should be considered.
When the detection finishes, the BTS sends a message to inform the BSC of the MS
SAIC capability. The BSC records the MS capability for the reference of VAMOS pairing.
Whether to enable this feature depends on the cell-level switch “If support SAIC AFC
detection”. Figure 3-2 shows the flow chart.

Figure 3- 2 Flow Chart of SAIC AFC Detection
3.4 Trigger VAMOS Pairing
Whether to enable VAMOS depends on the cell-level switch “If support VAMOS”.
VAMOS not only brings the mutual interference among users, it also affects other users
in the system. If the network has sufficient channel resources, VAMOS pairing is not
considered in order to achieve better communication performance. VAMOS pairing can
be used only when the channel resource load reaches two thresholds.
The two load thresholds are “The load of start VAMOS FR pairing” and “The load of start
VAMOS HR pairing”.
When the channel load of a certain cell exceeds “The load of start VAMOS FR pairing”,
two FR users in the cell can be selected for pairing. If no FR user fits, the pairing fails. As
the channel load exceeds “The load of start VAMOS HR pairing”, both the FR users and
HR users can be selected for pairing.
There are many countermeasures to handle the increasing load. According to their
respective gain, the values of the thresholds should follow the following principle:

dynamic HR conversion load threshold < FR to HR handover threshold (a single user is

first considered, and then a VAMOS user) < the load for starting VAMOS pairing.
3.5 VAMOS Pairing Algorithm
Before VAMOS pairing, it is necessary to detect the MS capability and save the result in
the database. If no MS capability record is found in the database, the MS cannot be
paired. It is recommended to enable MUTE SAIC detection and SAIC AFC detection
before enabling VAMOS.
After VAMOS is enabled and the conditions to trigger VAMOS pairing are met, the
VAMOS pairing algorithm flow starts. Users are selected for pairing according to the user
priority, speech version, wireless quality and path loss. Neither the users with high
priority nor the users with poor wireless quality or serious path loss are selected as the
candidates for VAMOS pairing.
The BTS power is a fixed value. After the candidates are selected, it is necessary to
check whether the power of the two candidates to be paired meet the BTS power
requirements and the SCPIR restriction.

Then, the two users start the pairing flow. The following six sections describe the details
on the pairing algorithm.
3.5.1 Requirement on Speech Version
Pairing of the following speech versions is supported: FR, EFR, AMR FR, AMR HR and
FR_AMR_WB.

3.5.2 Requirement on User Priority
Pairing means that two users share resources of the same channel. In this case, the
mutual interference is inevitable and there needs to be requirements on the priority of
users to be paired. High-priority users are not paired to ensure their voice quality. Only
some low-priority users are paired.
3.5.3 Requirement on Receiving Power Level and Receiving Quality
To ensure that the two users who multiplex the same timeslot can be served properly and
do not affect other users after being paired, requirements on the receiving quality and
power level of the paired users must be specified.
According to the simulation result, two MSs paired in similar wireless conditions shows
the best VAMOS performance. A pair of MSs in greatly different wireless conditions is
very likely to be depaired finally.
Pairing two users with the similar receiving quality and power level will lead to a better
result. Figure 3-3 shows VAMOS user classification by nine-rectangle-grid.
As shown in Figure 3-3, the horizontal axis indicates the receiving quality of the MS (bit
error rate) while the vertical axis represents the receiving power level of the MS.

Figure 3- 3 User Classification According to the Receiving Quality and Power Level
The users in A, B, C and D are regarded to have higher wireless quality, which enables
them to be candidates for VAMOS pairing.
3.5.4 Selection of Users with Similar Path Loss
After some candidates for pre-pairing are selected after their receiving quality and power
level are evaluated, the BSC will calculate their path loss. Users with similar path loss will
be considered for pairing. The UL and DL path losses of a user are almost the same, so
calculating the path loss of one direction is enough.
If the path loss of two users is similar and their path loss difference is less than the path
loss ratio threshold, they are regarded to meet the path loss requirements for pairing.
3.5.5 DL Initial Power Allocation According to the SCPIR
Besides selecting the users with similar path loss, initial power calculation is important.
The initial power must satisfy the preset target power level. The real pairing will not start
until the two calculations are completed. The following describes the calculations.
Since the max DL transmitting power of the BTS is fixed, when two users are multiplexed
over one channel, the total power of the two users must not exceed the max DL power.
According to the path loss decision, we assume that their path losses are similar. For the

power allocation, only the MS receiving performance is considered. A large proportion of

power is allocated to the weak-capability user and a small proportion to the
strong-capability user. To avoid great power difference between the two users, Sub
Channel Power Imbalance Ratio (SCPIR) is used. As long as the initial power of each
user satisfies its DL SCPIR threshold, the users are regarded to be eligible for pairing.
In addition, the preset target power level must be satisfied. In other words, it is the
minimum DL power level expected after the pairing. Pairing will not be considered as
successful unless the DL power level is higher than this threshold. The two users’ DL
transmitting power must be greater than their respective path loss + target power level.
3.5.6 Pairing Methods
The system supports two ways of pairing.
When assigning a TCH to a user, make the user a candidate. Select another user for
pairing within the cell. The two users must satisfy the conditions for triggering VAMOS
pairing. For details on how to select a user, refer to the VAMOS pairing algorithm above.
When the database is applying for channels, execute the VAMOS pairing algorithm in the
cell to select two suitable users who have already occupied the TCH to start the pairing
process. The two users must satisfy the conditions for triggering VAMOS pairing and
support pairing through intra-cell handover.
Pairing methods can be controlled by a switch. The switch values are as follows:
 0: VAMOS is not supported;
 1: Pairing through intra-cell handover is supported;
 2: Pairing through assignment is supported;
 3: Both pairing through intra-cell handover and through assignment is supported.

3.6 VAMOS De-pairing Algorithm
For VAMOS users, the communication quality might degrade after pairing due to the
mobility of the MS and the interference among users or from the environment. In this
case, de-multiplexing and handover should be performed according to users’ actual
conditions to ensure the VAMOS users’ normal communication.
When the network determines that pairing is no longer suitable for the two users
according to any algorithm, the two users have to be de-paired. The intra-cell handover
can be initiated for one user. The following sections describe the major De-pairing
algorithms.
3.6.1 De-pairing Algorithm When the Power Exceeds Threshold
The BTS performs power control over two users after the VAMOS pairing. But the total
DL power of the two users must not exceed the maximum DL power. So if the total DL
power exceeds the maximum DL power, the two users are allocated with the calculated
power. If the total DL power exceeds the threshold for P times after N times of power
control, the power is considered to have exceeded the threshold.
3.6.2 De-pairing Algorithm When the UL SCPIR Exceeds Threshold
This kind of algorithm is similar to that described in section 3.6.1. Determine whether the
UL SCPIR exceeds the threshold during power control. If the UL SCPIR exceeds the
threshold for P times after N times of power control, the UL SCPIR is considered to have
exceeded the threshold.
3.6.3 De-pairing Algorithm When the DL SCPIR Exceeds Threshold
The process is similar to that described in section 3.6.2. The only difference is to
calculate and decide the DL SCPIR. If the DL SCPIR exceeds the threshold for P times
after N times of power control, the DL SCPIR is considered to have exceeded the
threshold.

3.6.4 De-pairing Algorithm When the UL Quality Exceeds Threshold
When the UL quality of the paired users gets worse and reaches the threshold of
de-pairing, the de-pairing process will start. If the P out of N UL quality exceeds the
threshold, the UL quality is considered to have exceeded the threshold, which triggers
de-pairing.
3.6.5 De-pairing Algorithm When the DL Quality Exceeds Threshold
When the DL quality of the paired users gets worse and reaches the threshold of
De-pairing, the De-pairing process will start. If the P out of N DL quality exceeds the
threshold, the DL quality is considered to have exceeded the threshold, which triggers
De-pairing.
3.6.6 De-pairing Algorithm When the Load Decreases
When the cell load decreases and reaches the threshold of De-pairing, the paired users
will be de-paired to enhance network performance.
3.7 VAMOS Power Control
The VAMOS power control switch operates in the same way as the common power
control switch. When the switch is set to off, the UL and DL power keeps the power of
pairing. When the switch is set to on, the two paired users should perform the common
power control as well as the VAMOS power control. The details are described as follows.
After the VAMOS pairing, the two MSs which are in the same channel cause serious
mutual interference. The interference rejection capability of different MSs differs, and
different algorithms lead to different interference rejection capabilities. The power
difference between two users is called SCPIR, which reflects the power difference one
MS can bear. For example, if the SCPIR of an SAIC MS is -4, it indicates that this MS can
operate at the power of at most 4dB lower than the other MS. To guarantee the normal
communication of the two users, SCPIR should be considered besides the common
power control. In addition, since the two users share the DL power, the total power is

limited by the maximum power, which should also be considered in VAMOS power
control.
When a timeslot is multiplexed, the UL and DL power of the two users have to be
adjusted by power control, ensuring better quality. VAMOS pairing users use AQPSK
modulation in the DL. Two users take I and Q respectively. Different Alpha values make
the two users’ power different, namely, the SCPIR is different. Then the DL power control
is achieved by adjusting the Alpha value.
The principle of VAMOS power control is as follows: The system obtains the expected
value after the power control decision, and then decides whether it satisfies the VAMOS
power control requirement. For DL VAMOS power control, if the expected value after
power control separately satisfies the condition that SCPIR does not exceed the
threshold (SCPIR thresholds of various MSs are preset on the OMCR) or the sum of two
users’ power does not exceed the total DL power (decided by P/N principle, P and N can
be set on OMCR), the expected power value is used to transmit signals. If any one of the
two above mentioned parameters exceeds the threshold, VAMOS DL power control
should be performed. The SCPIR and the sum of power are guaranteed not to exceed
the threshold. The system then uses the adjusted power level to transmit signals. For UL
VAMOS power control, if the expected value after two users’ power control separately
satisfies the condition that SCPIR does not exceed the threshold, then the expected UL
value is sent to the MS. If not, UL VAMOS power control is adjusted. In this case, only
SCPIR is guaranteed not to exceed the threshold.
Since the max DL transmit power of BTS is fixed, when two users are multiplexed over
one channel, the total power of the two users cannot exceed the max DL power. The
BSC estimates the initial power according to the path loss + target power level of the two
paired users. After estimating the initial power, the system pairs two users who satisfy
the requirement.
VAMOS paired users might be in three power adjustment states after their power is
determined separately: Power stay, Decrease, and Increase. For VAMOS paired users,
there are nine types of power adjustment methods (PowerControlState[User 0][User 1]).
For details, refer to the following table.
PowerControlState [User 0] [User 1]
1 Increase Power stay

PowerControlState [User 0] [User 1]
2 Increase Increase
3 Power stay Increase
4 Decrease Increase
5 Decrease Power stay
6 Decrease Decrease
7 Power stay Decrease
8 Increase Decrease
9 Power stay Power stay
Because the DL power of VAMOS users is restricted by the total power and SCPIR,
besides the 9th adjustment method, the other eight might appear in the following three
states:
 The SCPIR exceeds the threshold. The SCPIR counts.
 The total power exceeds the threshold. The total power counts.
 The SCPIR and total power exceed the threshold. The SCPIR counts with a higher
priority.
The above table shows that two types of adjustment cause the max total power to
exceed the threshold.
 If two users are in Increase state in DL, check whether the total power exceeds the
threshold. If yes, adjust the power level and make it count.
How to adjust: Adjust the weak user. Increase the power level of the weak user, and
check whether the strong user meets the requirement of VAMOS power control after
power adjustment. The requirement is that SCPIR and the total power exceed the
thresholds. If the requirement is satisfied, the system then starts searching for the
proper power level for VAMOS power control. If no proper power level is found, the
current level is adopted.
 If one user is in Increase state and the other in Decrease, check whether the total
power exceeds the threshold. If yes, adjust the power level and make it count.

How to adjust: Decrease the power level of the user in Decrease state, and check
whether the power level satisfies the requirement of VAMOS power control. If not,
calculate the available power level according to the max total power and SCPIR
thresholds.
During VAMOS power control, if the SCPIR or total power exceeds the threshold, the
number of times is counted. The sliding window N/P decision mechanism determines
whether the number is greater than the threshold preset on the OMCR. Then it decides
whether to continue the VAMOS pairing. If the number of times exceeds the threshold,
the BSC is requested to depair the VAMOS pair.
Under the condition that users are multiplexed in the same timeslot, the UL power control
process is the same as that of DL. First, perform the power decision synchronization.
VAMOS paired users also have nine types of adjustment methods (PowerControlState).
The UL VAMOS power adjustment will not be made unless the SCPIR exceeds the
threshold (the UL SCPIR threshold is set on the OMCR). The number of times is counted.
After being decided by the sliding window decision mechanism, the BSC is requested to
depair the VAMOS pair.
3.8 AFC Power Control
When one of the paired MSs is an AFC MS, AFC power control is implemented. Whether
to enable the AFC power control can be configured on the OMCR.
The SCPIR threshold of the AFC MS differs from that of the SAIC MS. Sometimes the
RQ is bad and call dropping occurs though the AFC MS is paired under a high SCPIR. If
one of the paired MSs is an AFC MS, AFC power control improves this situation.
AFC power control depends on the periodic SCPIR change of the paired users. The
change period and SCPIR value can be set on the OMCR. The other paired user with an
SAIC MS is driven to change. Each of the paired users performs their own power control.
Their power control merely helps to adjust the total power.

3.9 Shift SACCH
This feature shifts the SACCHs of the two VAMOS sub-channels. The SACCH of one
sub-channel is always multiplexed with the TCH of the other sub-channel. When the
other user starts DTX, the SACCH performance is improved.
The mutual interference is serious when the two paired users map SACCH in an identical
way. During a call, the mute period takes a big proportion. Shifted SACCH effectively
improves the performance gain of the SACCH. When the SACCH of one user meets the
mute period, the SACCH is hardly affected.
When a VAMOS II MS uses the TSC of TSC set 2, its SACCH is mapped by Shifted
SACCH. The position of the shifted SACCH frame among the 26 frames is as follows:
For TCH/F, the shifted SACCH frame is the thirteenth frame (even-numbered timeslot) or
the twenty-fourth frame (odd-numbered timeslot). For TCH/H, the shifted SACCHs of the
1st and 2nd sub-timeslot are the thirteenth frame and the twenty-fourth frame respectively.
3.10 DL Signaling
When a VAMOS II MS operates in VAMOS paired mode, receivers with a strong

interference rejection capability such as JD and SIC are usually used to guarantee the
performance. For single user mode, the performance of a JD or SIC receiver is not as

good as that of an SAIC one. Therefore, when a VAMOS II MS is in single user mode, an
SAIC receiver is recommended to ensure the performance.
When the VAMOS II MS operates in another mode, the system informs the MS of its
current state through DL signaling. The MS then selects a JD/SIC receiver or an SAIC
receiver.
When a VAMOS II MS is in VAMOS paired mode and single user mode, an SAIC
receiver is recommended to ensure the performance. The system informs the MS of its
current state through DL signaling. The MS then selects a JD/SIC receiver or an SAIC
receiver.
When the channel state changes, the MS will be informed of the change through the
channel mode modify message, which is marked by the field “channel mode”.
The “channel mode” is encoded as follows.

4 Parameters
Table 4- 1 Parameters List
Recom
Managed Value Default
Logic Name Parameter Description Unit mended
Object Range Value
Value
VAMOS 0: Not
Configuratio support
n VAMOS
1: Support
VAMOS pair
by handover
This parameter indicates
2: Support
If support whether the cell supports
VAMOS pair None 0 0
VAMOS VAMOS. Enable the VAMOS
by
when operator requires.
assignment
3: Support
VAMOS pair
by handover
and
assignment
VAMOS This parameter indicates

Configuratio whether the cell supports MUTE
If support 0: Not
n SAIC detection. According to
MUTE SAIC Support None 0 0
the operator’s requirement,
detection 1: Support
enable the feature before
activating VAMOS.
VAMOS If support This parameter indicates 0: Not

Configuratio SAIC AFC whether the cell supports SAIC Support None 0 0
n detection AFC detection. 1: Support
VAMOS For users in high priority, their

Configuratio voice quality should be
n The priority guaranteed according to the
level of operator’s requirement. There
1..14 None 1 1
VAMOS is no need to perform pair
pairing process.
When system enables VAMOS,
only pair the users in low

Recom
Object Range Value
Value
priority.
If operator has no special
requirements, all users are
allowed to be paired. If operator
has some requirements, adjust
the priority of users to be
paired.
VAMOS When the cell load exceeds the

Configuratio threshold, the FR pairing
n process can be initiated.
The higher the value, the
The load of smaller the FR pairing
start VAMOS probability, and easier the cell 20..100 % 40 40
FR pairing congestion happens.
The lower the value, the greater
the HR pairing probability. The
increased VAMOS pairs bring
the system interference growth.
VAMOS When the cell load exceeds the

Configuratio threshold, the FR or HR pairing
n process can be initiated.
The load of smaller the HR pairing
start VAMOS probability, and easier the cell 20..100 % 80 80
HR pairing congestion happens.
The lower the value, the greater
the HR pairing probability. The
increased VAMOS pairs bring
the system interference growth.
VAMOS For two users reuse the same

Configuratio timeslot, certain requirements
n The level on the receive quality and level
threshold of are imposed to ensure their 0..63 None 30 30
Vamos paring normal work and keep no
impacts on other users.

Recom
Object Range Value
Value
requirements imposed on
users’ level are higher, which
makes the pairing more difficult.
The lower the value, the
users’ level are lower, which
makes the pairing easier. While
the probability of pair release or
call drop is higher.
VAMOS For two users reuse the same

Configuratio timeslot, certain requirements
n on the receive quality and level
are imposed to ensure their
normal work and keep no
impacts on other users.
The quality
threshold of 0..70 None 10 10
users’ quality are higher, which
Vamos paring
users’ quality are lower, which
VAMOS The users with close pass loss

Configuratio ratio enjoy better pairing effect.
n The lower the value, the
users’ pass loss ratio are
The pass loss
higher, which makes the pairing
ratio of 0..100 None 10 10
more difficult.
candidates
users’ downlink receive level
are lower, which makes the
pairing easier. While the

Recom
Object Range Value
Value
probability of pair release or call
drop is higher due to the
different radio environment.
VAMOS This parameter refers to the

Configuratio lowest level that user expects to
n receive.
and power are higher, which
The expected
makes the pairing more difficult. 0..63 None 20 20
received level
are lower, which makes the
pairing easier. While the
probability of pair release or call
drop is higher.
VAMOS The higher the value, the

Configuratio requirements imposed on
n users’ SCPIR are higher, which
The uplink
SCPIR 15..30 None 25 25
threshold
users’ SCPIR are lower, which

n The downlink users’ SCPIR are higher, which
SCPIR makes the pairing more difficult.
threshold of The lower the value, the 21..30 None 21 21
NON-SAIC requirements imposed on
MS users’ SCPIR are lower, which

Recom
Object Range Value
Value

The downlink
SCPIR
MUTE SAIC
MS

The downlink makes the pairing more difficult.
SCPIR The lower the value, the
11..30 None 11 11
threshold of requirements imposed on
SAIC MS users’ SCPIR are lower, which

The downlink
SCPIR
SAIC AFC
MS

The downlink
SCPIR
n users’ SCPIR are higher, which 11..30 None 11 11
threshold of
VAMOS I MS

Recom
Object Range Value
Value

The downlink makes the pairing more difficult.
SCPIR The lower the value, the
5..30 None 5 5
threshold of requirements imposed on
VAMOS II MS users’ SCPIR are lower, which
VAMOS This parameter indicates

Support 0: No
Configuratio whether to support VAMOS II None 0 0
VAMOS II 1: Yes
n MS
VAMOS This parameter refers to the P

P value of pair
Configuratio value of two users who satisfy 1..20 None 2 2
process
n pairing conditions.
VAMOS This parameter refers to the N

N value of
Configuratio value of two users who satisfy 1..20 None 3 3
pair process
n pairing conditions.
VAMOS Enabling this parameter can

The load of
Configuratio initiate VAMOS pair release
VAMOS pair 20..100 % 20 20
n when the cell load is lower than
release
the threshold.
VAMOS Support After VAMOS FR pairing, this

Configuratio handover parameter decides whether to
0: No
n from VAMOS perform handover from VAMOS None 0 0
1: Yes
FR to VAMOS FR to VAMOS HR due to the
HR continuous load increase.
VAMOS Support pair The pair release by calculating

0: No
Configuratio release due to whether the quality exceeds the None 1 1
1: Yes
n quality threshold is allowed.

Recom
Object Range Value
Value
VAMOS Uplink receive This parameter refers to the

Configuratio quality of uplink receive quality of
0..70 None 39 39
n pair-release pair-release threshold after
threshold pairing.
VAMOS Downlink
This parameter refers to the
Configuratio receive
downlink receive quality of
n quality of 0..70 None 39 39
pair-release threshold after
pair-release
pairing.
threshold
VAMOS P value of This parameter refers to the P

Configuratio pair-release value of pair-release uplink 1..20 None 6 6
n uplink quality quality after pairing.
VAMOS N value of This parameter refers to the N

Configuratio pair-release value of pair-release uplink 1..20 None 8 8
n uplink quality quality after pairing.
VAMOS P value of
This parameter refers to the P
Configuratio pair-release
value of pair-release downlink 1..20 None 6 6
n downlink
quality after pairing.
quality
VAMOS N value of
This parameter refers to the N
Configuratio pair-release
value of pair-release downlink 1..20 None 8 8
n downlink
quality after pairing.
quality
VAMOS 0: Not
Configuratio Support F+F
n or F+H
This parameter indicates 1: Support

VAMOS Pair
whether the cell allows FR+FR F+F None 3 3
Selecting
or FR+HR pairing. 2: Support
F+H
3: Support
F+F and F+H
VAMOS P value of MS
P value of MS capability
Configuratio capability 3..15 None 5 5
pre-detect
n predetect

Recom
Object Range Value
Value
VAMOS N value of MS
N value of MS capability
Configuratio capability 3..20 None 5 5
pre-detect.
n predetect
VAMOS VAMOS MS capability detection

Configuratio parameter. This parameter
High level
n refers to the high threshold of
threshold of
MS DL receive level before 47..85 None 75 75
MS capability
detection. MS level being
detect
lowerer than the parameter
satisfies the detection condition.

Configuratio parameter. This parameter
Low level
n refers to the low threshold of
threshold of
MS DL receive level before 70..111 None 85 85
MS capability
detection. MS level being higher
detect
than the parameter satisfies the
detection condition.

Configuratio parameter. In places with DL
n The level power control disabled, the
power control switch controls whether to
0: No
switch of MS perform power control on the None 0 0
1: Yes
capability detected MS, helping the level
detect to reach the value between the
high and low detection
threshold.
VAMOS 0: Not use

Configuratio SAIC AFC This parameter controls AFC power
n power control whether to perform the SAIC control None 0 0
switch AFC power control 1: Use AFC
power control
VAMOS VAMOS power control related

The period of
Configuratio parameters. This parameter
SAIC AFC 1..20 None 2 2
n uses the burst number of
power control
+SCPIR and –SCPIR.
VAMOS The alpha VAMOS power control related 1..10 None 4 4

Recom
Object Range Value
Value
Configuratio value of SAIC parameter. This parameter
n AFC power refers to the SCPIR value that
control SAIC AFC power control uses.

Configuratio AFC detect parameter. This parameter 0: Not
n switch of controls whether to perform the Detect None 1 1
MUTE SAIC AFC detection of the MUTE 1: Detect
SAIC MS.
TRX This parameter is applied for

two non-VAMOS MSs pairing.
One VAMOS sub-user uses
TSC, another uses TSC2. For
TSC2 MUTE or AFC detection, the 0..7 None 0 0
TSC and TSC2 are brought to
BTS by channel activation. The
TSC and TSC2 have to be
different.
5 Related Counters and Alarms
5.1 Related Counters
Table 5- 1 Counter List
Counter ID Name
C902210001 Number of MUTE SAIC detection(Times)

C902210002 Number of SAIC AFC detection(Times)
C902210003 Number of attempt of pairing between two TCH/Fs(Times)
C902210004 Number of Pairing success between two TCH/Fs(Times)
C902210005 Number of attempt of pairing between two TCH/Hs(Times)
C902210006 Number of Pairing success between two TCH/Hs(Times)

Number of attempt of pair releasing between two

C902210007 TCH/Fs(Times)
Number of pair releasing success between two
C902210008 TCH/Fs(Times)
Number of attempt of pair releasing between two
C902210009 TCH/Hs(Times)
Number of pair releasing success between two
C902210010 TCH/Hs(Times)
C902210011 Number of pair release due to power(Times)
C902210012 Number of pair release due to uplink SCPIR(Times)
C902210013 Number of pair release due to downlink SCPIR(Times)
C902210014 Number of connect failure due to no DSP resource(Times)
C902210015 Number of drop call during pairing(TCH/F)(Times)
C902210016 Number of drop call during pairing(TCH/H)(Times)
Number of attempt of pairing between TCH/F and
C902210017 TCH/H(Times)
Number of Pairing success between TCH/F and
Number of attempt of pair releasing between TCH/F and
Number of pair releasing success between TCH/F and
C902210021 Number of pair attempt time of NON- SAIC MS(Times)
C902210022 Number of Pairing success of NON-SAIC MS(Times)
C902210023 Number of pair attempt time of Mute SAIC MS(Times)
C902210024 Number of Pairing success of Mute SAIC MS(Times)
C902210025 Number of pair attempt time of SAIC AFC MS(Times)
C902210026 Number of Pairing success of SAIC AFC MS(Times)
C902210027 Number of pair attempt time of SAIC MS(Times)
C902210028 Number of Pairing success of SAIC MS(Times)
C902210029 Number of pair attempt time of VAMOS I MS(Times)
C902210030 Number of Pairing success of VAMOS I MS(Times)
C902210031 Number of pair attempt time of VAMOS II MS(Times)
C902210032 Number of Pairing success of VAMOS II MS(Times)

C902210033 Number of drop call during pairing(NON-SAIC) (Times)

C902210034 Number of drop call during pairing(Mute SAIC) (Times)
C902210035 Number of drop call during pairing(SAIC AFC) (Times)
C902210036 Number of drop call during pairing(SAIC) (Times)
C902210037 Number of drop call during pairing(VAMOS I) (Times)
C902210038 Number of drop call during pairing(VAMOS II) (Times)
C902210039 Number of handover attempt during pairing(Times)
C902210040 Number of handover perform during pairing(Times)
C902210041 Number of handover success during pairing(Times)
C902210042 TCH/F busy time during pairing(Second)
C902210043 TCH/H busy time during pairing(Second)
C902210044 NON-SAIC ms busy time during pairing(Second)
C902210045 MUTE SAIC ms busy time during pairing(Second)
C902210046 SAIC AFC ms busy time during pairing(Second)
C902210047 SAIC ms busy time during pairing(Second)
C902210048 VAMOS I ms busy time during pairing(Second)
C902210049 VAMOS II ms busy time during pairing(Second)
C902210050 NON-SAIC ms busy time(Second)
C902210051 MUTE SAIC ms busy time(Second)
C902210052 SAIC AFC ms busy time(Second)
C902210053 SAIC ms busy time(Second)
C902210054 VAMOS I ms busy time(Second)
C902210055 VAMOS II ms busy time(Second)
C902210056 NON VAMOS ms busy time(Second)
C902210057 Number of pair release due to uplink quality(Times)
C902210058 Number of pair release due to downlink quality(Times)
C902210059 Number of pair release attempts due to load(Times)
C902210060 Number of pair release due to load(Times)
C902210061 Number of pair release success due to load(Times)
C902210062 Number of NON SAIC MS(Num)
C902210063 Number of MUTE SAIC MS(Num)
C902210064 Number of SAIC AFC MS(Num)

C902210065 Number of SAIC MS(Num)

C902210066 Number of NON VAMOS MS(Num)
C902210067 Number of pair attempts of assign(Times)
C902210068 Number of pair success of assign(Times)
C902210069 Number of pair attempts of handover(Times)
C902210070 Number of pair success of handover(Times)
C902210071 Number of pair release attempts of assign(Times)
C902210072 Number of pair release success of assign(Times)
C902210073 Number of pair release attempts of handover(Times)
C902210074 Number of pair release success of handover(Times)
C902210075 Number of drop call during assign pairing(Times)
C902210076 Number of drop call during handover pairing(Times)
Number of handover attmpts from VAMOS FR to VAMOS
C902210077 HR(Times)
Number of handover performed from VAMOS FR to VAMOS
Number of handover success from VAMOS FR to VAMOS
C902210080 Number of samples with UL RQ = 0 of pairing(Num)
C902210088 Number of samples with DL RQ = 0 of pairing(Num)
C902210094 Number of samples with DL RQ =6 of pairing(Num)

C902210095 Number of samples with DL RQ =7 of pairing(Num)
5.2 Related Alarms
This feature has no related alarm.
6 Engineering Guide
6.1 Application Scenario
This feature is applicable to the area with heavy traffic. Check network KPIs before using
the feature. This feature is considered for the heavily congested cell. In addition, the
feature has a requirement on the MS capability. The network is required to have enough
VAMOS pairing capable MSs to achieve the expected expansion effect. The number of
capable MSs can be obtained after enabling SAIC AFC and MUTE SAIC detection.
This feature is not applicable to the high rail scenario.
6.2 Feature Activation Procedure
In the Configuration Management window, select GSM Logical Feature

Configuration>Cell Feature Configuration>VAMOS Configuration and select a cell
from the cell list in the right pane. On the VAMOS Configuration tab, set If support
VAMOS to Support VAMOS and set If support MUTE SAIC detection and If support
SAIC AFC detection. See the following figure.
It is recommended to set If support MUTE SAIC detection and If support SAIC AFC
detection to Support first, and check the UE capability in the cell to be commissioned. If
there are enough SAIC capable MSs, set If support VAMOS to Support VAMOS. The
load related parameters can be adjusted according to the actual needs. The default
values are recommended for the other parameters.

Figure 6- 1 Configuration Interface
Select GSM Logical Feature Configuration>Cell Feature Configuration and

double-click TRX Configuration to configure two different training sequences.
The TSC2 has to be configured for TRX when comissioning VAMOS. The value
combinations of (0, 2); (1, 7); (3, 4); and (5, 6) are recommended for TSC and TSC2.

Figure 6- 2 Configuring TSC2
6.3 Feature Validation Procedure
6.3.1 VAMOS Pairing and De-Pairing

Test Item VAMOS Pairing and De-Pairing
1. The default cell configuration and parameters was done in BSC;
Precondition 2. SAIC (Including mute SAIC, DARP I and DARP II) or VAMOS (Including
VAMOS I and VAMOS II) capability handsets are ready.
1. Enable cell support VAMOS
2. Enable cell support MUTE SAIC detection
3. Enable cell support SAIC AFC detection
4. Disable the dynamic half rate function
5. Configure cell support Intra-cell handover
6. Set the load of start VAMOS FR paring (FRPairLoadThr) as 20%
Test Steps 7. Set the level threshold of VAMOS paring (LevThrOfPair) as 20
8. Set the quality threshold of VAMOS paring (QualThrOfPair) as 50
9. Use signaling trace tools to trace A and Abis signaling
10. Reserve three timeslots unblocked and block other timeslots of the test
cell in dynamic management page.
11. MS1 and MS2 make two calls on the same TRX in the test cell near the
antenna,

12. MS3 makes the third call in the test cell to make the traffic load of the cell
exceed the FRPairLoadThr.
13. Check the signaling trace and the channel occupation state in dynamic
management
1. In step 11, MS1 and MS2 should use full rate. The two calls can be
established successfully.
2. In step 12, MS1 and MS2 can be multiplexed on one timeslot successfully
Anticipative
by intra-cell handover. MS1 and MS2 should use full rate after
Result
multiplexing.
3. In step 13 has VAMOS pair can be observed in TS management of
dynamic management
6.4 Feature Deactivation Procedure
In the Configuration Management window, select GSM Logical Feature

Configuration>Cell Feature Configuration and double-click VAMOS Configuration.
Select the cell from the cell list in the right pane. On the VAMOS Configuration tab, set
If support VAMOS to Not Support. Set If support MUTE SAIC detection to Not
Support, and If support SAIC AFC detection to Not Support.
6.5 Network Impact

This feature improves the whole network’s capacity.
Meanwhile, VAMOS has the following impacts on KPIs:
1. Pairing and De-pairing are implemented through intra-cell handover. Therefore, this
feature increases the number of intra-cell handover times.
2. Pairing reduces the cell load to a certain degree, so the congestion rate drops and
the appointment success rate improves.
3. The mutual interference between MSs increases during pairing, which may degrade
the RQ and increase the call drop rate.

7 Abbreviation
Abbreviations Full Characteristics
3GPP 3rd Generation Partnership Project
VAMOS Voice services over Adaptive Multi-user Channels on One Slot
DARP Downlink Advanced Receiver Performance
GMSK Gaussian Minimum Shift-frequency Keying
QPSK Quaternary Phase Shift Keying
SAIC Single Antenna Interference Cancellation
SCPIR SubChannel Power Imbalance Ratio
AFC Automatic Frequency Control
BSC Base Station Controller
BTS Base Transceiver Station
FR Full Rate
GERAN GSM/EDGE Radio Access Network
GSM Global System for Mobile Communication
HR Half Rate
MS Mobile Station
SDCCH Stand alone dedicated Control Channel
OMC Operation and Maintenance Center
TCH Traffic Channel
TDMA Time Division Multiple Access
RQ Receive quality
TSC Train Sequence Code
AFRCN Absolute Radio Frequency Channel Number
TS Time Slot
8 Reference Document
ZXUR 9000 GSM (V6.50.30) Base Station Controller Performance Counter Reference
ZXUR 9000 GSM (V6.50.30) Base Station Controller Radio Parameter Reference

Geran Ur14 Zgo-04-05-Xxx Vamos Feature Guide (v4)

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Geran Ur14 Zgo-04-05-Xxx Vamos Feature Guide (v4)

Încărcat de

Drepturi de autor:

Formate disponibile

ZGO-04-05-xxx VAMOS

ZGO-04-05-xxx VAMOS Feature Guide

V1.0 2015/07/23 First Release

© 2018 ZTE Corporation. All rights reserved.

ZTE Confidential & Proprietary 1

5 Related Counters and Alarms................................................................................... 32

2 ZTE Confidential & Proprietary

6.3 Feature Validation Procedure........................................................................................38

ZTE Confidential & Proprietary 3

Figure 2- 1 Channel Frame Structure in VAMOS Mode............................................................... 6

Table 2- 1 License Control List......................................................................................................... 8

4 ZTE Confidential & Proprietary

2.1 Feature Introduction

2 FR users multiplex one timeslot.

1 FR user + 2 HR users multiplex one timeslot.

3 HR users multiplex one timeslot.

ZTE Confidential & Proprietary 5

4 HR users multiplex one timeslot.

The following figure shows the frame structure of channel combination.

Figure 2- 1 Channel Frame Structure in VAMOS Mode

6 ZTE Confidential & Proprietary

Figure 2- 2 Two Users Multiplexed

ZTE Confidential & Proprietary 7

2.2 License Control

Table 2- 1 License Control List

License Configured Sales

ZGO-04-05-XXX VAMOS VAMOS BSC TRX

2.3 Correlation with Other Features

2. Mutually Exclusive Features

ZGO-04-01-001 Extended Cell Coverage

ZGO-03-02-005 Dynamic Half Rate Allocation

8 ZTE Confidential & Proprietary

3.1 MS Capability Pre-Check

3.2 Mute SAIC Detection

ZTE Confidential & Proprietary 9

Figure 3- 1 Flow Chart of Mute SAIC Detection

3.3 SAIC AFC Detection

10 ZTE Confidential & Proprietary

Figure 3- 2 Flow Chart of SAIC AFC Detection

3.4 Trigger VAMOS Pairing

ZTE Confidential & Proprietary 11

dynamic HR conversion load threshold < FR to HR handover threshold (a single user is

3.5 VAMOS Pairing Algorithm

12 ZTE Confidential & Proprietary

3.5.1 Requirement on Speech Version

ZTE Confidential & Proprietary 13

3.5.2 Requirement on User Priority

3.5.3 Requirement on Receiving Power Level and Receiving Quality

14 ZTE Confidential & Proprietary

3.5.4 Selection of Users with Similar Path Loss

3.5.5 DL Initial Power Allocation According to the SCPIR

ZTE Confidential & Proprietary 15

power allocation, only the MS receiving performance is considered. A large proportion of

3.5.6 Pairing Methods

The system supports two ways of pairing.

 0: VAMOS is not supported;

 1: Pairing through intra-cell handover is supported;

 2: Pairing through assignment is supported;

 3: Both pairing through intra-cell handover and through assignment is supported.

16 ZTE Confidential & Proprietary

3.6 VAMOS De-pairing Algorithm

3.6.1 De-pairing Algorithm When the Power Exceeds Threshold

3.6.2 De-pairing Algorithm When the UL SCPIR Exceeds Threshold