GBFD-115830

VAMOS Feature
Test & Quality Assurance Test
Exit Report (TER)
Version: 0.2

Date: 09/04/2018

Author: Firoz Alam

Project Reference: [31791]

Document Change History:

Version CR Number Change Date Changed By Change Summary
v0.1 N/A 09/04/2018 Firoz Alam Initial Draft

Table 1 Document Change History

EE Internal Document1 Page 1 of 22

 Executive Summary
Test & Quality Assurance Test
GREEN
RAG on Completion:

Overall Summary:

VAMOS testing performed in line with most expectations. From 55 total test cases, 51 passed, 2 where de-
scoped, 2 passed with comments due to reduce in the MOS levels in two scenarios
1. MOS score dropped from 3.7 (AMR-HR with VAMOS not enabled) to 3.4 (with VAMOS enabled).
The drop in the levels were observed in those scenarios where two VAMOS calls are orthogonal
and are occupying the same half rate timeslot.
2. Also, the MOS level dropped from 3.4 to 2.8 when four VAMOS calls occupies all the four TS of a
TCHH in a TRX.

Concessions:

Since no VAMOS I or VAMOS II UEs were available, testing was done with SAIC capable UEs. Most of the
testing done against SAIC UE is valid for VAMOS as well.

Impact to Service Quality:

MOS level observed via POLSKA on Xcal shows a drop from 3.7 in AMR-HR to 3.4 in case of two VAMOS
calls on same channel and from 3.4 to 2.8 when 4 calls are on same channel.

Impact to Service Operations:

None

Test & Quality Assurance Recommendation:

It is recommended that the feature progresses to limited field trial, and observe Link Quality and Voice
Quality KPIs.
Since VAMOS capable UE can offer better performance than simple SAIC UE, it is also recommended that
VAMOS I and VAMOS II enabled UEs to be tested when available to test if the same performance
degradation is observed with them as well.

Distribution and sign-off

The RACI methodology has been used to identify the following as document receivers, according to
need:
 R = responsible for document content
 A = accountable for document content
 C = consulted on the document content
 I = kept informed on the document content

Sign-off
Name Title Department RACI Required Y/N
(insert approval)
Sebastian Pineda Test & Integration Test & Quality R

EE Internal Document1 Page 2 of 22

 Sign-off
Name Title Department RACI Required Y/N
(insert approval)
Manager Assurance
Firoz Alam
Test & Quality
& Integration Engineer R
Assurance
Imran Jan
Konstantina
Senior Designer Access Design A
Ntanaka
Peter Lamacraft 2G Design Authority Access Design A
Technology Delivery
Alison Lambert Project Manager I
– Networks
Technology Delivery
Phil Hackett Senior Manager I
– Networks
RAN Operations
Rob Garner RAN Programmes I
Manager
Senior Support
Pauline Pike Access Design I
Engineer
Mark Newton Principal Designer Access Design
Andy Cliff Senior Designer Access Design I
Table 2 Distribution

EE Internal Document1 Page 3 of 22

 Table of contents
Executive Summary ...................................................................................................................2
Table of contents..............................................................................................................................4
Table of figures.................................................................................................................................5
1. INTRODUCTION ................................................................................................................6
1.1 PURPOSE ..........................................................................................................................6
1.2 REFERENCES .....................................................................................................................6
2. PROJECT OVERVIEW .........................................................................................................7
2.1 IN SCOPE ...........................................................................................................................7
2.2 OUT OF SCOPE ..................................................................................................................8
2.3 SYSTEMS UNDER TEST .....................................................................................................8
2.4 TEST ENVIRONMENT ........................................................................................................9
2.4.1 TEST EQUIPMENT .............................................................................................................9
2.4.2 TEST PROCEDURE .............................................................................................................9
2.5 TEST RESULT ................................................................... Error! Bookmark not defined.
2.6 TEST TEAM ......................................................................................................................13
2.7 RISKS AND ISSUES ..........................................................................................................13
2.8 TEST PLAN VARIANCES ..................................................................................................13
3. DETAILED TEST RESULTS ...............................................................................................14
3.1 TEST CASE SUMMARY ....................................................................................................14
3.2 TEST CASE RESULTS .......................................................................................................16
3.3 TEST CASES WITH CONCESSIONS OR NOT PASSED ......................................................16
3.4 REQUIREMENTS COVERAGE ..........................................................................................16
4. DEFECTS..........................................................................................................................18
5. LESSONS LEARNT AND RECOMMENDATIONS ..............................................................19
5.1 LESSONS LEARNT ...........................................................................................................19
5.2 RECOMMENDATIONS .....................................................................................................19
6. ADDITIONAL CONTEXT SPECIFIC INFORMATION ..........................................................20
7. TEMPLATE INFORMATION ..............................................................................................21
8. APPENDIX A – GLOSSARY...............................................................................................22

EE Internal Document1 Page 4 of 22

 Table of figures

Figure 1: VAMOS HR- 2 calls on same channel ............................................................................. 7

Figure 2: VAMOS HR- 4 calls on same channel ............................................................................. 7
Figure 3: MOS Score for AMR HR (Without VAMOS ) ................................................................... 9
Figure 4: MOS score for AMR-HR (two calls on same channel of TRX-0).................................... 10
Figure 5: MOS score for AMR-HR (four calls on same channel of TRX-0) ................................... 11

EE Internal Document1 Page 5 of 22

 1. INTRODUCTION
1.1 PURPOSE
The purpose of this document is to report on the findings and results ,in relation to the validation of
GBFD-115832 VAMOS Call Drop Solution Feature.
The VAMOS function allows one TCH to carry two calls. The VAMOS feature multiplexes two calls onto
one TCHH and four calls onto one TCHH in VAMOS HR, increasing the network capacity compared with
when common TCHHs are used. This feature therefore helps expand capacity and alleviate network
congestion.
All testing documented in this report was performed in Eagles Wood test facility.

1.2 REFERENCES
# Document Title Link or Location Version Date
Test Strategy Test Strategy 1.0 16-Oct-2017
Environment
Gemini Hardware and Backhaul Details 4.9 08/02/2018
Delivery Plan
Technical
Architecture GBSS19.1 Feature Description 1.0 03/01/2018
Document
Low Level
LLD 2G 0 19/01/2018
Design
Parameter
Parameters 2G and 4G 1.0 19/12/2017
Alignment
Table 3 References

EE Internal Document1 Page 6 of 22

 2. PROJECT OVERVIEW

Voice services over adaptive multi-user channels on one slot (VAMOS) was introduced in GSM/EDGE
radio access network (GERAN) evolution and developed based on Multi-User Reusing One Slot
(MUROS) technology. VAMOS expands GERAN network capacity without adding transceivers (TRXs)
or frequencies.
VAMOS is a technique used on Global System for Mobile Communications (GSM) networks to increase
voice capacity. It multiplexes two voice calls onto one voice channel, especially one half-rate traffic
channel (TCHH). As shown in Figure 1, a high-order modulation scheme similar to quaternary phase
shift keying (QPSK) works with orthogonal training sequence codes (TSCs) to multiplex the calls in the
downlink, and Gaussian minimum shift-frequency keying (GMSK) is used to modulate signals in the
uplink. The two sub channels use orthogonal TSCs to occupy the same voice channel. Huawei's VAMOS
multiplexes two voice calls onto the same TCHH to double network capacity.

Figure 1: VAMOS HR- 2 calls on same channel

VAMOS HR multiplexes four voice calls on same TCHH , resulting degradation in MOS levels but
increasing the network capacity.

Figure 2: VAMOS HR- 4 calls on same channel

2.1 IN SCOPE
 Feature Activation/Deactivation
 Effect of changes in Parameter threshold values on the feature
 BTS 3900L on IP
 CS Calls
 CS Mobility
 CS Data

EE Internal Document1 Page 7 of 22

  Validation of Counters
 Voice Quality
 SAIC Capable Handset (Nokia C5)
 VAMOS I and II capable handset
 Validation of Alarms
 RF and BB Hopping CS VAMOS Calls
 Handover from 3G to 2G ( only VAMOS Cell)
 SRVCC 4G to 2G ( only VAMOS Cell)

2.2 OUT OF SCOPE

The following items have been defined as out of scope of testing:
 BTS 3900 on TDM abis (Flex Abis feature required)
 BTS 3900L on MLPPP
 No testing with high load scenarios
 BTS Hardware combinations
 Device testing
 Validation against NSN 3G on OUK Core
 Non-Edge Capable Device
 BTS 3900E
 GBFD-115831 Mute SAIC MS Identification feature
 PS Data
 Non-Hopping
 FR VAMOS
 SOAK Testing
 Load Thres. in Overlaid Subcell


2.3 SYSTEMS UNDER TEST

Test Items (Artefacts)
ID Name Version Type Comments
1 Huawei BSC6900 V900R019ENGC1 BSC Software
0SPC520
2 Huawei BTS3900A or BTS3900L or V100R012C10SP3 BTS Software
DBS3900 10
Table 4. Software regression versions

EE Internal Document1 Page 8 of 22

 2.4 TEST ENVIRONMENT

2.4.1 TEST EQUIPMENT

 5 x Samsung S5 (SAIC) and 2 x Nokia 6230( non-SAIC) UEs were used to generate
traffic.
 The RF tools used were NEMO Outdoor Version 8.01 and Xcal-M O3.5.0.14

2.4.2 TEST PROCEDURE

 The Feature was activated using the below MML command
SET GCELLVAMOS: IDTYPE=BYID, CELLID=0, VamosSwitch=VHR;
 Parameter thresholds were changed to observed effects on calls.
 Counters were observed to check that they were working as expected.
 NEMO was used to measure AMR Link Quality.
 XCAL was used to measure the POLSKA MOS levels for voice quality.

2.5 TEST RESULTS

XCAL results show that MOS levels for pure AMR-HR and non-orthogonal Vamos calls are 3.8 while for
orthogonal it is 3.4.
When a Vamos Call occupies its own HR TS of the TCHH the quality is fine i.e 3.4 , which can be seen
from below X-cal Screenshots.

Figure 3: MOS Score for AMR HR (Without VAMOS enabled )

EE Internal Document1 Page 9 of 22

 When two Vamos calls are orthogonal and share the same TS, the quality degrades to 3.4 (average)

Figure 4: MOS score for AMR-HR (two calls on same TCHH)

EE Internal Document1 Page 10 of 22

 However when four Vamos calls are orthogonal and share the same TS, the quality degrades to 2.8
(average).

Figure 5: MOS score for AMR-HR (four calls on same channel of TRX-0)

EE Internal Document1 Page 11 of 22

 In the attached logs, the TS assignment is random for calls. About half of the calls are orthogonal.
The link quality observed on NEMO outdoor also shows degradation on Vamos. The first figure below is
a normal AMR-HR call, while the second show the addition of an orthogonal Vamos call.

EE Internal Document1 Page 12 of 22

 2.6 PAIRING OF SAIC AND NON-SAIC UES
A SAIC UE and non-SAIC UE can be paired by configuring the parameter VamosNoneSaic.
The observations from testing this parameter are :
1. A non-SAIC MS can be assigned a channel if both HR TS are being used by SAIC MSs

2. A SAIC MS cannot be assigned a channel if both HR TS are being used by non-SAIC MSs

3. A non-SAIC MS causes high interference when paired with SAIC MS

2.7 TEST TEAM

Role Name Contact Details Responsibility

Test & Integration Sebastian.PinedaCarrillo Planning, execution and

Sebastian Pineda
Manager @ee.co.uk reporting on the testing

Test & Integration

Firoz Alam Firoz.Alam@ee.co.uk Test execution
Engineer

Test & Integration

Imran Jan Imran.Jan@ee.co.uk Test execution
Engineer

Environment
Arun Gopinathan Arun.Gopinathan@ee.co.uk Test environment
Manager

Programme Test Review & approval of

Martin Gilkes Martin.Gilkes@ee.co.uk
Manager testing

Portfolio Delivery Review & approval of

Alison Lambert alison.lambert@ee.co.uk
Manager testing
Table 5 Test Team

2.8 RISKS AND ISSUES

Impact
ID Risk/Issue Description Probability Mitigation
H,M,L

Table 6 Risks and Issues

2.9 TEST PLAN VARIANCES

None.

EE Internal Document1 Page 13 of 22

 3. DETAILED TEST RESULTS
3.1 TEST CASE SUMMARY

Total No
No
Test Set of Test Pass Failed NA De-scoped Blocked
Run
Cases

Basic Testing 14 14

Counters 08 07 01

CS Data Tests in
VAMOS enabled 07 07
cell

CS Mobility for
13 13
VAMOS calls

CS Tests in
VAMOS enabled 08 08
cell

Voice Quality
05 04 01
(MOS Score)

Total 55 53 02
Table 8 Test Case Results Summary

Sl Execution
Test Set Name Test case Name
No Status
1 3G AMR ISHO to AMR-HR Passed
2 SRVCC to GERAN (EE 2G) Passed
3 SRVCC to GERAN (EE 2G) Passed
4 Idle Cell Reselection Intra-PLMN Intra-BSC Inter-BTS Passed

5 Intra-PLMN Intra-BSC Inter-BTS Huawei AMR-FR to Huawei

VAMOS - based on RxLevel Passed

6 Intra-PLMN Intra-BSC Inter-BTS Huawei VAMOS to Huawei

VAMOS - based on RxLevel Passed
CS Mobility for Intra-PLMN Inter-BSC Inter-BTS Huawei AMR-HR to
7
VAMOS calls Huawei VAMOS - based on RxLevel Passed

8 Intra-PLMN Intra-BSC Inter-BTS Huawei VAMOS to

Huawei VAMOS - based on RxLevel Passed

9 Intra-PLMN Intra-BSC Inter-BTS Huawei VAMOS to Huawei

EFR - based on RxLevel Passed
10 Huawei VAMOS Call Handover to AMR Cell Passed
11 AMR Call Handover to Huawei VAMOs Cell Passed

12 Remote Web-LMT Forced Handover MML Command - SET

FHO ( for VAMOS call) Passed

EE Internal Document1 Page 14 of 22

 13 Huawei Cell congested. Directed Retry Handover to second
Huawei Cell. (VAMOS cell) Passed

14 Activate the feature with Recommended parameters

settings Passed
15 Change parameter value of VamosMultLoadThd Passed
16 Change parameter value of VamosIntraHoSwitch Passed
17 Verify parameter value of VamosLoadReuseLoadThd Passed
18 Change parameter value of VamosQualReuseSwitch Passed

19
Verify parameter value of VamosQualReuseUpLinkQualThd Passed

20 Verify parameter value of

VamosQualReuseDownLinkQualThd Passed
Basic Testing
21 VAMOS TSC Automatic Mapping set ON FH Mode Passed

22
VAMOS TSC Automatic Mapping set ON Non-FH Mode Passed
23 Verify parameter value of Primary TSC in VAMOS Passed
24 Verify parameter value of Secondary TSC in VAMOS Passed
25 VAMOS TSC Automatic Mapping set OFF FH Mode Passed

26
VAMOS TSC Automatic Mapping set OFF Non-FH Mode Passed

27 Make simultaneous Vamos call on corresponding channels

of different TRXs in the same cell Passed
28 Power on UE in Huawei coverage area Passed
29 Huawei Cell Reselection onto second Huawei Cell Passed
30 VAMOS 7.4 Kbps BTS 3900L IP Abis Passed
31 999 Call on Huawei Cell. VAMOS Passed
32 CS Tests in VAMOS 112 Call on Huawei Cell. VAMOS Passed
33 enabled cell Establish AMR-HR Call. Check AMR link adaptation. Passed

34
Originating & Terminating SMS on SDCCH 160 characters. Passed

35 Originating & Terminating SMS on SDCCH morethan160

ALL characters. Passed
36 Autobaud Passed
37 300 bps (V.21) Passed
38 2400 bps (V.22bis) Passed
CS Data Tests in
39 4800 bps (V.32) Passed
VAMOS enabled cell
40 9600 bps (V.32) Passed
41 9600 bps (V.110 or X.31 flag stuffing) Passed
42 1200 bps (V.22) Passed
43 AMR-HR 7.40kbps call. Speech MOS check. Passed

44 AMR-HR 7.40kbps call. Speech MOS check. Without

VAMOS enabled De-scoped
Voice Quality (MOS
45 Score) AMR-HR 7.40kbps call. Speech MOS check. With Vamos
enabled Passed

46 Two AMR-HR 7.4kbps calls. Speech MOS check. With Passed with
Vamos enabled comments

EE Internal Document1 Page 15 of 22

 47 Four AMR-HR 7.4kbps calls. Speech MOS check. With Passed with
Vamos enabled comments
48 K3014 Traffic Volume on TCH Passed
49 K3034 TCHH Traffic Volume Passed
50 R3501 Mean Number of VAMOS Busy HR Channels Passed

51 De-scoped
R3550N2 Average Number of VAMOS Busy FR Channels
Counters
52
ZTR304 Call Drop Rate on TCH per cell(including Handover) Passed
53 RH303A Success Rate of Radio Handover Passed
54 TCH congestion rate Passed
55 AA3250 Average Call Access Duration Passed

3.2 TEST CASE RESULTS

Vamos_Test_Exit.xls
m

Detailed test results can be found in HP ALM - https://almee12.saas.hp.com/qcbin/start_a.jsp

SRAN EE_Technology / EE_Technology
Projects -> 31791 –SRAN12.1 -> VAMOS

3.3 TEST CASES WITH CONCESSIONS OR NOT PASSED

HP ALM
Defect
Test Area Description Status Comments
ID/Issue
Number

AMR-HR
Voice 7.40kbps call.
Quality Speech MOS De- Its same test case as AMR-HR 7.40kbps call.
N/A
(MOS check. Without scoped Speech MOS check and so its De-scoped.
Score) VAMOS
enabled
R3550N2
Average
De- This counter works for FR .As testing is carried
Counters Number of scoped
N/A
out on HR, so its not applicable.
VAMOS Busy
FR Channels

3.4 REQUIREMENTS COVERAGE

The feature enhancement test has covered the following:
- Basic testing
- Counters

EE Internal Document1 Page 16 of 22

 - CS in VAMOS enabled calls
- CA Data in VAMOS enabled calls
- CS Mobility in VAMOS enabled calls.
- Voice Quality.

EE Internal Document1 Page 17 of 22

 4. DEFECTS
No defects were raised during this test campaign.

EE Internal Document1 Page 18 of 22

 5. LESSONS LEARNT AND RECOMMENDATIONS
5.1 LESSONS LEARNT
 Parameter alignment needs to be on a regular basis to keep the environment in line with
the live network
 Test environment stability has a major impact in terms of throughput and transport
related features and tests

5.2 RECOMMENDATIONS
 The test team recommends that the feature be sent to limited field trial, and
observe Link Quality and Voice Quality KPIs.
 It is also recommended that VAMOS I and VAMOS II enabled UEs to be tested
when available to test if the same performance degradation is observed with
them as well.

EE Internal Document1 Page 19 of 22

 6. ADDITIONAL CONTEXT SPECIFIC INFORMATION
NA

EE Internal Document1 Page 20 of 22

 7. TEMPLATE INFORMATION
This document was produced using the following Test & Quality Assurance template.

Template: Test & Quality Assurance Test Exit Report Template

Template Version v1.2

Template Owner: Lisa Lessels

Published Date: 31/03/2017

Test & Quality Assurance Test Exit Report Template Change History:

Version Change Date Changed By Change Summary

v0.1 15/04/15 Chris Child Draft template for review
v1.0 23/05/16 Chris Child Updated following review
Security Classification changed to
V1.1 17/10/16 Chris Child
EE Internal & Template Information section added.
V1.2 24/3/17 Chris Child Updates to reflect change of team name
Table 15 Template Change History

EE Internal Document1 Page 21 of 22

 8. APPENDIX A – GLOSSARY

Term/Acronym Definition
BRS Business Requirements Specification
EE Everything Everywhere
E2E End to End
EDP Environment Delivery Plan
TIM Test & Integration Manager
I&V Integration & Validation
KPI Key Performance Indicator
NP&SI Network Products and Service Integration
PO Purchase Order
SUT System under Test
TF Test Facility
T&I Test and Integration
SVHO Smooth Voice Handover
QC Quality Centre
HO Handover
MOS Mean Opinion Score
PESQ Perceptual Evaluation of Speech Quality
TBF Temporary Block Flow
PDCH Packet Data Channel
TCH Traffic channel
TS Time slot
CH Channel
VAMOS Voice services over Adaptive Multi- user channels on One Slot
FR Full Rate channel
HR Half rate channel

EE Internal Document1 Page 22 of 22