4G eNodeB Validation

Procedure

Cod:
Prot:

Pag.:1/7
Rev:

Index

1
2
3

Document Objective........................................................................................................................ 3
Thresholds ........................................................................................................................................... 3
Latency test......................................................................................................................................... 5
3.1 Goal ................................................................................................................................................... 5
3.2 Outputs............................................................................................................................................ 5
4 DL/UL Throughput test .................................................................................................................. 5
4.1 Goal ................................................................................................................................................... 5
4.2 Outputs............................................................................................................................................ 5
5 CSFB Call (MOC/MTC) ..................................................................................................................... 5
5.1 Goal ................................................................................................................................................... 5
5.2 Outputs............................................................................................................................................ 5
6 VoLTE Call (MOC/MTC)................................................................................................................... 6
6.1 Goal ................................................................................................................................................... 6
6.2 Outputs............................................................................................................................................ 6
7 Emergency Call.................................................................................................................................. 6
7.1 Goal ................................................................................................................................................... 6
7.2 Outputs............................................................................................................................................ 6
8 SMS ......................................................................................................................................................... 6
8.1 Goal ................................................................................................................................................... 6
8.2 Outputs............................................................................................................................................ 6
9 Swapped feeders ............................................................................................................................... 7
9.1 Goal ................................................................................................................................................... 7
9.2 Outputs............................................................................................................................................ 7
10 Alarm clearance................................................................................................................................. 7
10.1 Goal .............................................................................................................................................. 7
10.2 Outputs ....................................................................................................................................... 7

Cod:
Prot:

Pag.:2/7
Rev:

1 Document Objective
This document describes the Vodafone validation procedure for the LTE eNodeB acceptance.
The procedure consists of a set of tests to be done live in the network, in a static position
under optimal radio condition, just after the eNodeB integration. In order to evaluate whether
the eNodeB performs as expected, the outputs of each test need to be compared with predefined thresholds. The following aspects are considered in the acceptance phase:

CSFB (both MO and MT calls)

VoLTE (both MO and MT calls)
Emergency calls
E2E Latency
DL/UL Throughput
SMS transmission and reception
Swapped feeders
Alarm verification and clearance on both 4G and legacy sistems
Antenna system validation

2 Thresholds
For each test, two different thresholds have been defined:
A.

B.

ON/OFF Threshold: this threshold should indicate whether the eNodeB should be kept
switched on or not. It represents a very basic threshold that ensures that the 4G eNodeB
performs at least as good as an average 3G NodeB and therefore can be opened to
commercial traffic
Acceptance Threshold: this threshold represents the green light for considering the
eNodeB as fully accepted

After the completion of the procedure, three situations may occur:

1.
2.

3.

eNodeB < Threshold A: in this case the eNodeB shall be locked (i.e. not opened to
commercial traffic) and an immediate troubleshooting session shall start
eNodeB > Threshold A and < Threshold B: in this case the eNodeB shall be switched on (i.e.
declared as in service and opened to commercial traffic) and a troubleshooting session
shall be organized for the day after in order to fix the problems and let the eNodeB
overcoming Threshold B
eNodeB > Threshold B: in this case the eNodeB shall be switched on (i.e. declared as in
service and opened to commercial traffic) and considered ready for next steps of conditional
acceptance/acceptance verifications (defined in separate documents)

Information Originators are responsible for classifying ('valuing') their information and for ensuring appropriate security measures are applied
and maintained. Currently there are four levels of classification in use at Vodacom, C1, C2, C3 and C4. Information considered to be sensitive is
classified as C2, C3 and C4. C1 refers to Vodacom information that is already in the public domain. You must understand how to recognise and
protect sensitive information.

Page 3 of 7

Bandwidth
dependancy

Threshold A
- ON/OFF-

Threshold B
- Acceptance -

5 MHz

>5 Mbps

>17 Mbps

10 MHz

>10 Mbps

>35 Mbps

15 MHz

>15 Mbps

>50 Mbps

20 MHz
(or 10 + 10 MHz)

>20 Mbps

>70 Mbps

10 + 15 MHz

>25 Mbps

>85 Mbps

10 + 20 MHz
15 + 15 MHz

>30 Mbps

>105 Mbps

15 + 20 MHz

>35 Mbps

>120 Mbps

20 + 20 MHz

>40 Mbps

> 140 Mbps

5 MHz

>2 Mbps

>5 Mbps

10 MHz

>2 Mbps

>10 Mbps

15 MHz

>3 Mbps

>15 Mbps

>4 Mbps

>20 Mbps

>5 Mbps

>25 Mbps

>6 Mbps

>30 Mbps

>7 Mbps

>35 Mbps

>8 Mbps

>40 Mbps

<50 ms

<50 ms

CSFB Call (MOC/MTC)

OK

<11s (call setup time)

VoLTE Call (MOC/MTC)

OK

<5s (call setup time)

Emergency call

OK

OK

SMS (send/receive)

OK

OK

Alarm clearance on 4G

OK

OK

Alarm clearance on 2G/3G

OK

OK

Swapped feeders

OK

OK

Test

DL throughput

UL throughput

20 MHz
(or 10 + 10 MHz)
10 + 15 MHz
10 + 20 MHz
15 + 15 MHz
15 + 20 MHz
20 + 20 MHz

Latency

Antenna system validation

According to specific Vodafone Guidelines

Table 1: Acceptance Thresholds

Information Originators are responsible for classifying ('valuing') their information and for ensuring appropriate security measures are applied
and maintained. Currently there are four levels of classification in use at Vodafone, C1, C2, C3 and C4. Information considered to be sensitive is
classified as C2, C3 and C4. C1 refers to Vodafone information that is already in the public domain. You must understand how to recognise and
protect sensitive information.

Page 4 of 7

3 Latency test
3.1 Goal
This test aims at measuring the E2E latency between the user and the Internet. The test shall
be performed three times per each sector and the best values shall be considered.

3.2 Outputs
For each cell, report the best results out of the three latency tests.

4 DL/UL Throughput test

4.1 Goal
The goal of this test is to measure DL and UL performances. The test shall be performed
three times per each sector and the best values shall be considered. The test for each cell
must be performed in a location where the measured SINR is higher than 25 dB.

4.2 Outputs
For each cell, report the best results out of the three DL/UL throughput tests.

5 CSFB Call (MOC/MTC)

5.1 Goal
The goal of this test is to verify CSFB functionality and call setup times. The test shall
consider both MTC and MOC per each sector.

5.2 Outputs
For each cell and call type (MOC or MTC), call setup times must be reported.

Information Originators are responsible for classifying ('valuing') their information and for ensuring appropriate security measures are applied
and maintained. Currently there are four levels of classification in use at Vodafone, C1, C2, C3 and C4. Information considered to be sensitive is
classified as C2, C3 and C4. C1 refers to Vodafone information that is already in the public domain. You must understand how to recognise and
protect sensitive information.

Page 5 of 7

6 VoLTE Call (MOC/MTC)

6.1 Goal
The goal of this test is to verify VoLTE functionality and call setup times. The test shall
consider both MTC and MOC per each sector.

6.2 Outputs
For each cell and call type (MOC or MTC), call setup times must be reported.

7 Emergency Call
7.1 Goal
The goal of this test is to verify CSFB functionality for Emergency call and the correctness of
the call routing. The test shall be performed once per eNodeB and for all the Emergency
numbers defined in the specific country (e.g. 112, 113, 115 and 118 in Italy). During each call
it is mandatory to wait for the answer and ask whether the call has been received from the
right location. E.g.: if I call the 113 from Milan, I need to be sure that the call has been
received by the police headquarter in Milan.

7.2 Outputs
OK/NOK Flag shall be reported for each eNodeB and emergency number.

8 SMS
8.1 Goal
The goal of this test is to verify SMS functionality over 4G. The test shall consider both SMS
transmission and reception and shall be performed once per cell of the eNodeB.

8.2 Outputs
OK/NOK Flag shall be reported for each cell and test type (SMS sent or received).

Information Originators are responsible for classifying ('valuing') their information and for ensuring appropriate security measures are applied
and maintained. Currently there are four levels of classification in use at Vodafone, C1, C2, C3 and C4. Information considered to be sensitive is
classified as C2, C3 and C4. C1 refers to Vodafone information that is already in the public domain. You must understand how to recognise and
protect sensitive information.

Page 6 of 7

9 Swapped feeders
9.1 Goal
The goal of this test is to verify the correcteness of the feeders installation. In order to verify
this aspect, the coherence between HW/SW configuration and radiated PCI/Cell ID shall be
verified (in front of each cell) and reported.

9.2 Outputs
OK/NOK Flag shall be reported for each cell.

10 Alarm clearance
10.1 Goal
The goal of this verification is to avoid active alarms on both legacy and 4G systems after the
integration of the eNodeB.

10.2 Outputs
OK/NOK Flag shall be reported for each eNodeB

Information Originators are responsible for classifying ('valuing') their information and for ensuring appropriate security measures are applied
and maintained. Currently there are four levels of classification in use at Vodafone, C1, C2, C3 and C4. Information considered to be sensitive is
classified as C2, C3 and C4. C1 refers to Vodafone information that is already in the public domain. You must understand how to recognise and
protect sensitive information.

Page 7 of 7