Geran Ur13 Zgo-04-05-xxx Vamos Feature Guide (v4)_v1.0

ZGO-04-05-xxx VAMOS Feature Guide

ZGO-04-05-xxx VAMOS

ZGO-04-05-xxx VAMOS Version V1.00

Date

2014/03/15

Author

Li Rian

Reviewer

Gu Yuhui

Notes

New

© 2014 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

ZGO-04-05-xxx VAMOS

TABLE OF CONTENTS

2

1

Feature Attribute ............................................................................................... 5

2 2.1 2.2 2.3

Overview ............................................................................................................ 5 Feature Introduction ............................................................................................. 5 License Control .................................................................................................... 8 Correlation with Other Features ........................................................................... 9

3 3.1 3.2 3.3 3.4 3.5 3.5.1 3.5.2 3.5.3 3.5.4 3.5.5 3.5.6 3.6 3.6.1 3.6.2 3.6.3 3.6.4 3.6.5 3.6.6 3.7 3.8 3.9 3.10

Technical Description ....................................................................................... 9 MS Capability Pre-Check ..................................................................................... 9 Mute SAIC Detection ........................................................................................... 9 SAIC AFC Detection .......................................................................................... 10 Trigger VAMOS Pairing...................................................................................... 11 VAMOS Pairing Algorithm .................................................................................. 12 Requirement on Speech Version ....................................................................... 13 Requirement on User Priority ............................................................................. 14 Requirement on Receiving Power Level and Receiving Quality ......................... 14 Selection of Users with Similar Path Loss .......................................................... 15 DL Initial Power Allocation According to the SCPIR ........................................... 15 Pairing Methods ................................................................................................. 16 VAMOS De-pairing Algorithm............................................................................. 17 De-pairing Algorithm When the Power Exceeds Threshold ................................ 17 De-pairing Algorithm When the UL SCPIR Exceeds Threshold .......................... 17 De-pairing Algorithm When the DL SCPIR Exceeds Threshold .......................... 17 De-pairing Algorithm When the UL Quality Exceeds Threshold.......................... 18 De-pairing Algorithm When the DL Quality Exceeds Threshold.......................... 18 De-pairing Algorithm When the Load Decreases ............................................... 18 VAMOS Power Control ...................................................................................... 18 AFC Power Control ............................................................................................ 21 Shift SACCH ...................................................................................................... 22 DL Signaling ...................................................................................................... 22

4

Parameters....................................................................................................... 24

5 5.1 5.2

Related Counters and Alarms ........................................................................ 33 Related Counters ............................................................................................... 33 Related Alarms .................................................................................................. 36

6 6.1 6.2

Engineering Guide .......................................................................................... 36 Application Scenario .......................................................................................... 36 Feature Activation Procedure ............................................................................. 36

ZTE Confidential Proprietary

ZGO-04-05-xxx VAMOS

6.3 6.3.1 6.3.2 6.3.3 6.3.4 6.4 6.5

Feature Validation Procedure............................................................................. 38 MUTE SAIC MS Capability Detection................................................................. 38 SAIC AFC MS Capability Detection ................................................................... 39 VAMOS Pairing and De-pairing of FR ................................................................ 39 VAMOS Pairing and De-pairing of HR................................................................ 40 Feature Deactivation Procedure......................................................................... 41 Impact on the Network ....................................................................................... 41

7

Abbreviation .................................................................................................... 41

8

Reference Document....................................................................................... 42

ZTE Confidential Proprietary

3

ZGO-04-05-xxx VAMOS

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

4

ZTE Confidential Proprietary

ZGO-04-05-xxx VAMOS

1

Feature Attribute BSC version: [ZXUR 9000 GSM (V6.50.20)] BTS version: [SDR V4.11 and later version] Attribute: [Optional] Involved NEs: NE Name

Related or Not

MS/UE

√

BTS

√

BSC

√

iTC

-

MSC

-

MGW

-

SGSN

-

GGSN

-

HLR

-

Special Requirement

“√”: Involved, “-”: Not involved

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.

ZTE Confidential Proprietary

5

ZGO-04-05-xxx VAMOS

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.

6

ZTE Confidential Proprietary

ZGO-04-05-xxx VAMOS

Figure 2-2

Two Users Multiplexed

ARFCN: 160 TS: 3 TSC: 0 ARFCN: 160 TS: 3 TSC: 5

BTS

ARFCN: 160 TS: 3 TSC: 5

ARFCN: 160 TS: 3 TSC: 0

MS1 MS2 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

ZTE Confidential Proprietary

7

ZGO-04-05-xxx VAMOS

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. This feature includes the following feature:

2.2

ZGO-04-05-001

Adaptive QPSK Modulation

ZGO-04-05-002

VAMOS Power Control

ZGO-04-05-003

VAMOS Pairing and De-Pairing

ZGO-04-05-004

VAMOS Pairing Based on Signal Level and Quality

ZGO-04-05-005

VAMOS Pairing Based on Path Loss

ZGO-04-05-006

VAMOS Pairing Based on User Priority

ZGO-04-05-007

Detection of Mute-SAIC Mobile Stations

ZGO-04-05-008

Detection of SAIC Mobile Stations with AFC Problem

ZGO-04-05-009

Shift SACCH

ZGO-04-05-010

Downlink Signaling

License Control Table 2-1

License Control List

Feature ID

8

Feature Name

License

Configured

Control Item

NE

Unit

ZTE Confidential Proprietary

ZGO-04-05-xxx VAMOS

ZGO-04-05-XXX

VAMOS

VAMOS

BSC

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

ZTE Confidential Proprietary

9

ZGO-04-05-xxx VAMOS

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

BTS

MS

BSC

ClassmrakChange:DARP=0,VAMOS=0 Channel active: need detect Access TCH Send downlink interference signal in TCH Measure Report …………

………

According the mute SAIC detect threshold SAIC Result = Mute SAIC

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.

10

ZTE Confidential Proprietary

ZGO-04-05-xxx VAMOS

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

BTS

MS

BSC

ClassmrakChange:DARP=1,VAMOS=0 Channel active: need detect Access TCH Send downlink -3.5db SCPIR signal in TCH Measure Report …………

………

According the SAIC AFC detect threshold SAIC Result =SAIC AFC

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

ZTE Confidential Proprietary

11

ZGO-04-05-xxx VAMOS

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.

12

ZTE Confidential Proprietary

ZGO-04-05-xxx VAMOS

The cell load reaches the pairing threshold.

Select two online users.

Is neither of them a high-priority user?

No

是

No

Do their speech versions meet the requirements?

No No

是

Do their receiving power level and RQ meet the requirements?

No

是

Does their path loss difference meet the requirements? 是 Do their initial power allocated meet the requirements?

是 Make one user to execute handover to perform the pairing.

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.

ZTE Confidential Proprietary

13

ZGO-04-05-xxx VAMOS

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.

14

ZTE Confidential Proprietary

ZGO-04-05-xxx VAMOS

Figure 3-3

User Classification According to the Receiving Quality and Power Level

B

A

Increase Power

High Level C

D

Decrease Power

Margin

Low Level Keep Power Level HO Threshold Low Bit Erro Rate

High Bit Erro Rate Quality Handover Threshold

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

ZTE Confidential Proprietary

15

ZGO-04-05-xxx VAMOS

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:

16



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.

ZTE Confidential Proprietary

ZGO-04-05-xxx VAMOS

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.

ZTE Confidential Proprietary

17

ZGO-04-05-xxx VAMOS

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

18

ZTE Confidential Proprietary

ZGO-04-05-xxx VAMOS

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 1

ZTE Confidential Proprietary

[User 0] Increase

[User 1] Power stay

19

ZGO-04-05-xxx VAMOS

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.

20

ZTE Confidential Proprietary

ZGO-04-05-xxx VAMOS

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.

ZTE Confidential Proprietary

21

ZGO-04-05-xxx VAMOS

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 st

1 and 2

nd

sub-timeslot are the thirteenth frame and the twenty-fourth frame respectively. SACCH FS

TCH TCH TCH TCH TCH TCH TCH TCH TCH TCH TCH TCH TCH FS FS FS FS FS FS FS FS FS FS FS FS FS 12 0 1 2 3 4 5 6 7 8 9 10 11

0

1

2

3

4

5

6

7

8

9

10

11

12

13

13

TCH TCH TCH TCH TCH TCH TCH TCH TCH TCH TCH IDLE FS FS FS FS FS FS FS FS FS FS FS 14 15 16 17 18 19 20 21 22 23 24 25

14

15

16

17

18

19

20

21 22

23

24

Subchannel 0 TCH/HS

TCH/HS

TCH/HS

TCH/HS

TCH/HS

TCH/HS

0

2

4

6

8

10

0

1

2

3

4

5

6

7

8

9

10

TCH/HS SACCH HS 12 13

11

12

13

14

TCH/HS

TCH/HS

TCH/HS

TCH/HS

TCH/HS

15

17

19

21

23

15

16

17

18

19

20

21 22

TCH/HS

TCH/HS

TCH/HS

TCH/HS

TCH/HS

TCH/HS

TCH/HS

TCH/HS

TCH/HS

TCH/HS

TCH/HS

1

3

5

7

9

11

14

16

18

20

22

23

24

25

SACCH TCH/HS HS 24 25

Subchannel 1

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

22

ZTE Confidential Proprietary

25

ZGO-04-05-xxx VAMOS

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.

ZTE Confidential Proprietary

23

ZGO-04-05-xxx VAMOS

4

Parameters Table 4-1 Managed Object

Parameters List

Logic Name

Parameter Description

Cell

Value Range

Unit

Default Value

Recom mended Value

0: Not support VAMOS 1: Support intra-cell handover This parameter indicates If support

whether the cell supports

VAMOS

VAMOS. Enable the VAMOS when operator requires.

and pair 2: Support assigning None

0

0

None

0

0

None

0

0

None

1

1

pair 3: Support intra-cell handover and pair and assigning pair

Cell

This parameter indicates If support MUTE SAIC detection

whether the cell supports MUTE SAIC detection. According to

0: No

the operator’s requirement,

1: Yes

enable the feature before activating VAMOS.

Cell

If support

This parameter indicates

SAIC AFC

whether the cell supports SAIC

detection

AFC detection.

Cell

0: No 1: Yes

For users in high priority, their The priority

voice quality should be

level of

guaranteed according to the

VAMOS

operator’s requirement. There

pairing

is no need to perform pair

1..14

process.

24

ZTE Confidential Proprietary

ZGO-04-05-xxx VAMOS

Managed Object

Logic Name

Parameter Description

Value

Unit

Range

Default Value

Recom mended Value

When system enables VAMOS, only pair the users in low 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. Cell

When the cell load exceeds the threshold, the FR pairing 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 FR pairing

%

40

40

%

80

80

None

30

30

congestion happens. The lower the value, the greater the HR pairing probability. The increased VAMOS pairs bring the system interference growth.

Cell

When the cell load exceeds the threshold, the FR or HR pairing process can be initiated. The higher the value, the The load of

smaller the HR pairing

start VAMOS probability, and easier the cell 20..100 HR pairing

congestion happens. The lower the value, the greater the HR pairing probability. The increased VAMOS pairs bring the system interference growth.

Cell

For two users reuse the same The level

timeslot, certain requirements

threshold of

on the receive quality and level 0..63

Vamos paring are imposed to ensure their normal work and keep no

ZTE Confidential Proprietary

25

ZGO-04-05-xxx VAMOS

Managed Object

Logic Name

Parameter Description

Value Range

Unit

Default Value

Recom mended Value

impacts on other users. The higher the value, the requirements imposed on users’ level are higher, which makes the pairing more difficult. The higher the value, the requirements imposed on users’ level are lower, which makes the pairing easier. While the probability of pair release or call drop is higher. Cell

For two users reuse the same timeslot, certain requirements on the receive quality and level are imposed to ensure their normal work and keep no impacts on other users. The quality threshold of Vamos paring

The lower the value, the requirements imposed on users’ quality are higher, which

0..70

None

10

10

0..100

None

10

10

makes the pairing more difficult. The higher the value, the requirements imposed on users’ quality l are lower, which makes the pairing easier. While the probability of pair release or call drop is higher.

Cell

The users with close pass loss ratio enjoy better pairing effect. The lower the value, the The pass loss ratio of candidates

requirements imposed on users’ pass loss ratio are higher, which makes the pairing more difficult. The higher the value, the requirements imposed on users’ downlink receive level

26

ZTE Confidential Proprietary

ZGO-04-05-xxx VAMOS

Managed Object

Logic Name

Parameter Description

Value Range

Unit

Default Value

Recom mended Value

are lower, which makes the pairing easier. While the probability of pair release or call drop is higher due to the different radio environment. Cell

This parameter refers to the lowest level that user expects to receive. The higher the value, the requirements imposed on users’ downlink receive level The expected received level

and power are higher, which makes the pairing more difficult. 0..63

None

20

20

15..30

None

25

25

21..30

None

21

21

The lower the value, the requirements imposed on users’ downlink receive level are lower, which makes the pairing easier. While the probability of pair release or call drop is higher. Cell

The higher the value, the requirements imposed on users’ SCPIR are higher, which makes The uplink SCPIR threshold

the pairing more difficult. The lower the value, the requirements imposed on users’ SCPIR are lower, which makes the pairing easier. While the probability of pair release or call drop is higher.

Cell

The downlink The higher the value, the requirements imposed on SCPIR threshold of

users’

NON-SAIC

SCPIR are higher, which makes

ZTE Confidential Proprietary

27

ZGO-04-05-xxx VAMOS

Managed Object

Logic Name MS

Parameter Description

Value Range

Unit

Default Value

Recom mended Value

the pairing more difficult. The lower the value, the requirements imposed on users’ SCPIR are lower, which makes the pairing easier. While the probability of pair release or call drop is higher.

Cell

The higher the value, the requirements imposed on users’ The downlink SCPIR threshold of MUTE SAIC MS

SCPIR are higher, which makes the pairing more difficult. The lower the value, the requirements imposed on

11..30

None

11

11

11..30

None

11

11

15..30

None

15

15

users’ SCPIR are lower, which makes the pairing easier. While the probability of pair release or call drop is higher.

Cell

The higher the value, the requirements imposed on users’ SCPIR are higher, which makes The downlink the pairing more difficult. SCPIR

The lower the value, the

threshold of

requirements imposed on

SAIC MS

users’ SCPIR are lower, which makes the pairing easier. While the probability of pair release or call drop is higher.

Cell

28

The downlink The higher the value, the requirements imposed on SCPIR threshold of

users’

SAIC AFC

SCPIR are higher, which makes

ZTE Confidential Proprietary

ZGO-04-05-xxx VAMOS

Managed Object

Logic Name MS

Parameter Description

Value Range

Unit

Default Value

Recom mended Value

the pairing more difficult. The lower the value, the requirements imposed on users’ SCPIR are lower, which makes the pairing easier. While the probability of pair release or call drop is higher.

Cell

The higher the value, the requirements imposed on users’ SCPIR are higher, which makes The downlink the pairing more difficult. SCPIR

The lower the value, the

threshold of

requirements imposed on

11..30

None

11

11

5..30

None

5

5

None

0

0

None

2

2

VAMOS I MS users’ SCPIR are lower, which makes the pairing easier. While the probability of pair release or call drop is higher. Cell

The higher the value, the requirements imposed on users’ SCPIR are higher, which makes The downlink the pairing more difficult. SCPIR

The lower the value, the

threshold of

requirements imposed on

VAMOS II MS users’ SCPIR are lower, which makes the pairing easier. While the probability of pair release or call drop is higher. Cell

Support VAMOS II

Cell

This parameter indicates whether to support VAMOS II MS

0: No 1: Yes

P value of pair This parameter refers to the P 1..20

ZTE Confidential Proprietary

29

ZGO-04-05-xxx VAMOS

Managed Object

Logic Name process

Parameter Description

Value

Unit

Range

Default Value

Recom mended Value

value of two users who satisfy pairing conditions.

Cell

N value of

None

3

3

%

20

20

None

0

0

None

1

1

0..70

None

39

39

0..70

None

39

39

1..20

None

6

6

1..20

None

8

8

P value of

This parameter refers to the P

pair-release

value of pair-release downlink 1..20

None

6

6

downlink

quality after pairing.

pair process Cell

The load of VAMOS pair release

Cell

This parameter refers to the N value of two users who satisfy 1..20 pairing conditions. Enabling this parameter can initiate VAMOS pair release when the cell load is lower than the threshold.

Support

After VAMOS FR pairing, this

handover

parameter decides whether to

from VAMOS perform handover from VAMOS FR to VAMOS FR to VAMOS HR due to the HR Cell

Cell

1: Yes

continuous load increase.

threshold is allowed.

1: Allow

Uplink receive This parameter refers to the quality of

uplink receive quality of

pair-release

pair-release threshold after

threshold

pairing.

Downlink receive quality of pair-release threshold

Cell

0: No

Support pair The pair release by calculating 0: Not release due to whether the quality exceeds the allow quality

Cell

20..100

This parameter refers to the downlink receive quality of pair-release threshold after pairing.

P value of

This parameter refers to the P

pair-release

value of pair-release uplink

uplink quality quality after pairing. Cell

N value of

This parameter refers to the N

pair-release

value of pair-release uplink

uplink quality quality after pairing. Cell

30

ZTE Confidential Proprietary

ZGO-04-05-xxx VAMOS

Managed Object

Logic Name

Parameter Description

Value Range

Unit

Default Value

Recom mended Value

quality Cell

N value of pair-release downlink quality

This parameter refers to the N value of pair-release downlink 1..20

None

8

8

None

3

3

3..15

None

5

5

3..20

None

5

5

47..85

None

75

75

70..111

None

85

85

None

0

0

quality after pairing.

Cell

0: F+F and F+H not allowed 1: F+F

VAMOS Pair Selecting

This parameter indicates whether the cell allows FR+FR or FR+HR pairing.

allowed 2: F+H allowed 3: F+F and F+H allowed

Cell

P value of MS capability predetect

Cell

N value of MS capability predetect

Cell

P value of MS capability pre-detect

N value of MS capability pre-detect. VAMOS MS capability detection

High level threshold of MS capability detect

parameter. This parameter refers to the high threshold of MS DL receive level before detection. MS level being lowerer than the parameter satisfies the detection condition.

Cell

VAMOS MS capability detection Low level threshold of MS capability detect

parameter. This parameter refers to the low threshold of MS DL receive level before detection. MS level being higher than the parameter satisfies the detection condition.

Cell

The level

ZTE Confidential Proprietary

VAMOS MS capability detection 0: Off;

31

ZGO-04-05-xxx VAMOS

Managed Object

Logic Name

Parameter Description

power control parameter. In places with DL

Value Range

Unit

Default Value

Recom mended Value

1: On

switch of MS power control disabled, the capability

switch controls whether to

detect

perform power control on the detected MS, helping the level to reach the value between the high and low detection threshold.

Cell

The period of SAIC AFC power control

Cell

The alpha

VAMOS power control related parameters. This parameter uses the burst number of

refers to the SCPIR value that

control

SAIC AFC power control uses.

value of SAIC AFC power control TRX

2

2

1..10

None

4

4

None

1

1

None

0

0

VAMOS power control related

AFC power

The alpha

None

+SCPIR and –SCPIR.

value of SAIC parameter. This parameter

Cell

1..20

VAMOS MS capability detection parameter. This parameter

0: Not

controls whether to perform the Detect AFC detection of the MUTE

1: Detect

SAIC MS. 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

TSC and TSC2 are brought to BTS by channel activation. The TSC and TSC2 have to be different.

32

ZTE Confidential Proprietary

ZGO-04-05-xxx VAMOS

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)

C902210007

Number of attempt of pair releasing between two TCH/Fs(Times)

C902210008

Number of pair releasing success between two TCH/Fs(Times)

C902210009

Number of attempt of pair releasing between two TCH/Hs(Times)

C902210010

Number of pair releasing success between two 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)

C902210017

Number of attempt of pairing between TCH/F and TCH/H(Times)

C902210018

Number of Pairing success between TCH/F and TCH/H(Times) Number of attempt of pair releasing between TCH/F and

C902210019

TCH/H(Times)

C902210020

Number of pair releasing success between TCH/F and TCH/H(Times)

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)

ZTE Confidential Proprietary

33

ZGO-04-05-xxx VAMOS

34

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)

ZTE Confidential Proprietary

ZGO-04-05-xxx VAMOS

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)

C902210077

Number of handover attmpts from VAMOS FR to VAMOS HR(Times) Number of handover performed from VAMOS FR to VAMOS

C902210078

HR(Times)

C902210079

Number of handover success from VAMOS FR to VAMOS HR(Times)

C902210080

Number of samples with UL RQ = 0 of pairing(Num)

C902210081

Number of samples with UL RQ = 1 of pairing(Num)

C902210082

Number of samples with UL RQ = 2 of pairing(Num)

C902210083

Number of samples with UL RQ = 3 of pairing(Num)

C902210084

Number of samples with UL RQ = 4 of pairing(Num)

C902210085

Number of samples with UL RQ = 5 of pairing(Num)

C902210086

Number of samples with UL RQ = 6 of pairing(Num)

C902210087

Number of samples with UL RQ = 7 of pairing(Num)

ZTE Confidential Proprietary

35

ZGO-04-05-xxx VAMOS

5.2

C902210088

Number of samples with DL RQ = 0 of pairing(Num)

C902210089

Number of samples with DL RQ = 1 of pairing(Num)

C902210090

Number of samples with DL RQ = 2 of pairing(Num)

C902210091

Number of samples with DL RQ = 3 of pairing(Num)

C902210092

Number of samples with DL RQ = 4 of pairing(Num)

C902210093

Number of samples with DL RQ = 5 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)

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

Configuration

Management>Managed Element>GSM Logical Configuration>Cell Information Configuration>GSM Cell Configuration, and set related parameters.

36

ZTE Confidential Proprietary

ZGO-04-05-xxx VAMOS

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.

ZTE Confidential Proprietary

37

ZGO-04-05-xxx VAMOS

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

MUTE SAIC MS Capability Detection Test Item Prerequisites

Steps

MUTE SAIC MS Capability Detection 1.

The CN state is normal.

2.

The BSC state and its configuration are normal.

3.

The BTS state and its configuration are normal.

4.

The test cell service is normal.

5.

A MUTE SAIC MS and a NO SAIC MS are available.

1.

Configure the cell to support MUTE SAIC detection.

2.

Use the MUTE SAIC MS to initiate a call inside the cell and trace signaling messages. Check the VAMOS Description field in the ChannelActivation message.

3.

If the BSC receives an AbisSAICResult message, check the message and use an MS without the VAMOS capability to repeat the above steps.

38

ZTE Confidential Proprietary

ZGO-04-05-xxx VAMOS

Test Item Expected Result

MUTE SAIC MS Capability Detection 1.

In step 3, the reported MUTE SAIC capability can be viewed in the AbisSAICResult message.

2.

In step 3, the reported NO SAIC capability can be viewed in the AbisSAICResult message.

6.3.2

SAIC AFC MS Capability Detection Test Item Prerequisites

Steps

SAIC AFC MS Capability Detection 1.

The CN state is normal.

2.

The BSC state and its configuration are normal.

3.

The BTS state and its configuration are normal.

4.

The test cell service is normal.

5.

A SAIC AFC MS and a SAIC MS are available.

1.

Configure the cell to support SAIC AFC detection.

2.

Use the SAIC AFC MS to initiate a call inside the cell and trace signaling messages. Check the VAMOS Description field in the ChannelActivation message.

3.

If BSC receives an AbisSAICResult message, check the message and use a SAIC MS to repeat the above steps.

Expected Result

1.

In step 3, the reported SAIC AFC capability can be viewed in the AbisSAICResult message.

2.

In step 3, the reported SAIC capability can be viewed in the AbisSAICResult message.

6.3.3

VAMOS Pairing and De-pairing of FR Test Item Prerequisites

VAMOS Pairing and De-pairing of FR 1.

The CN state is normal.

2.

The BSC state and its configuration are normal.

3.

The BTS state and its configuration are normal.

4.

The test cell service is normal.

5.

The UE supports VAMOS pairing (for SAIC and MUTE SAIC).

Steps

1.

Configure the cell to support VAMOS.

2.

Configure the cell to support MUTE detection and AFC detection.

3.

ZTE Confidential Proprietary

Initiate FR calls in the cell and block the available

39

ZGO-04-05-xxx VAMOS

Test Item

VAMOS Pairing and De-pairing of FR channels in the cell. The current channel occupation rate exceeds the “The load of start VAMOS FR pairing” threshold. 4.

Initiate a call in the cell to trigger VAMOS pairing.

5.

Keep the paired MSs away from each other, increasing level distance until they are depaired.

Expected Result

1.

In step 4, the MS served by the cell initiates an intra-cell handover to perform pairing, taking the same FR timeslot with another MS.

2.

In step 5, the paired MSs initiate an intra-cell handover, taking different FR timeslots.

6.3.4

VAMOS Pairing and De-pairing of HR Test Item Prerequisites

VAMOS Pairing and De-pairing of HR 1.

The CN state is normal.

2.

The BSC state and its configuration are normal.

3.

The BTS state and its configuration are normal.

4.

The test cell service is normal.

5.

The UE supports VAMOS pairing (for SAIC and MUTE SAIC).

Steps

1.

Configure the cell to support VAMOS.

2.

Configure the cell to support MUTE detection and AFC detection.

3.

Initiate HR calls in the cell and block the available channels in the cell. The current channel occupation rate exceeds the “The load of start VAMOS HR pairing” threshold.

4.

Initiate a call in the cell to trigger VAMOS pairing.

5.

Keep the paired MSs away from each other, increasing level distance until they are depaired.

Expected Result

1.

In step 4, the MS served by the cell initiates an intra-cell handover to perform pairing, taking the same HR timeslot with another MS.

2.

In step 5, the paired MSs initiate an intra-cell handover, taking different HR timeslots.

40

ZTE Confidential Proprietary

ZGO-04-05-xxx VAMOS

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, If support MUTE SAIC detection to Not Support, and If support SAIC AFC detection to Not Support.

6.5

Impact on the Network 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 Abbreviation

Full Name rd

3GPP

3 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

ZTE Confidential Proprietary

41

ZGO-04-05-xxx VAMOS

8

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

Reference Document ZXUR 9000 GSM (V6.50.20) Base Station Controller Performance Counter Reference ZXUR 9000 GSM (V6.50.20) Base Station Controller Radio Parameter Reference

42

ZTE Confidential Proprietary