In Building System Acceptance GuidelinesCoverage Acceptance (Part 1)

Document InformationVersion: 1.0Document Owner: Vodafone & Optus SingtelAuthor(s):Release Date:Maturity:Status:Approved by:Reviewed by:

Distribution List:

Storage:Restriction: Restricted to Distribution listType of document: Acceptance GuidelinesDocument No:

Table of Contents

1. OVERVIEW.........................................................................................................................3

2. SCOPE................................................................................................................................4

3. PROCESS...........................................................................................................................5

4. PRE-REQUISITES..............................................................................................................6

5. 3G DATA COLLECTION WITH WCDMA SCANNER.........................................................7

5.1. WCDMA scanner....................................................................................................7

5.2. Walk test.................................................................................................................7

6. EC AND EC/IO REQUIREMENT.........................................................................................8

6.1. Ec requirement........................................................................................................8

6.2. Ec/Io requirement....................................................................................................8

The In building system should fulfil all the following requirement:.......................................8

7. COVERAGE ACCEPTANCE REPORT..............................................................................9

8. NEIGHBOUR LIST OPTIMISATION.................................................................................10

9. 2G DATA COLLECTION...................................................................................................11

9.1. 2G data collection equipment...............................................................................11

9.2. Walk test...............................................................................................................11

9.3. RxLev Requirement..............................................................................................11

All the following requirement must be met:.......................................................................11

IBC

1. Overview

The purpose of this document is to provide a technical 3G In-building coverage acceptance

guideline for the RF design vendors involved in the Project Spinoza Joint Venture (JV).

This will ensure the In Building System (IBS) meets the requirements of the JV specified in the

In Building System Design Guidelines.

There will be 2 parts of acceptance process:

i) The coverage acceptance process

a. The process ensures the RF signal strength (Ec, Ec/Io) meets design

requirement stated in the Design Guidelines as well as design reports.

b. The process also ensures that the neighbourlist required in the In-building cells

are optimised.

c. The JV will be viewed as a single entity in this process.

ii) The KPI acceptance process

a. The process ensures KPI requirements are met. The KPI include Drop call

rate, Call setup success rate, Packet call throughput etc.

b. The process will be performed separately by Vodafone and Optus Singtel

separate by the designers of the In-building system.

c. The JV will not be viewed as single entity in this process.

IBC

2. Scope

This document is intended to provide sufficient information for the RF design vendor to perform coverage acceptance process only. KPI acceptance process will be specified the the In building System KPI acceptance guidelines document.

Test and tools required will be mentioned in the document along with the process flow.

Acceptance for service KPI’s and capacity will be performed individually for Optus SingTel and Vodafone.

IBC

3. Process

IBC

2GUpgraded site?

2G data collection

3G data collection with WCDMA Scanner

Ec, Ec/Io meet requirement?

Investigate design, Make changes to design if required

Generate Acceptance Report

No

No

Pass Ec, Ec/Io log files to KPI acceptance process for

neighbourlist optimisation

4. Pre-requisites

Before starting the coverage acceptance process, the following are several perquisites which has to be fulfilled:

4.1. If the 3G In building system is upgraded from the existing 2G In building system, optimisation engineer is required to perform 2G data collection before the system is upgraded. These data will be used for comparison with 2G data which will be collector after the In building system is upgraded to 3G compliance system. The same equipment must be used for the walk test before and after the In building system is upgraded. Please refer to section 9 for details of 2G data collection process and requirement.

4.2. Statistically (busy hour and daily) and drop call rate, call setup success rate, traffic erlang of the 2G In building cell must be recorded for 1 week before the 2G In building cell is being upgraded.

4.3. Walk test route will be proposed to, and agreed by, the JV by the optimisation engineers before the start of the walk test. The walk test route should be presented with a floor plan underneath in a picture file.

IBC

5. 3G data collection with WCDMA scanner

5.1. WCDMA scanner

Unless otherwise suggested by optimisation engineers, either DTI or Anritsu scanner can be used in this process

The scanner must work in conjunction with software which will produce a ‘snail trail’ of the walk test overlaid on top of the floor plan. Some example this software would be Nemo, TEMs 6.0, Wireless Valley etc. The ‘snail trial’ to be demonstrated MUST follow the agreed walk test route specified.

Minimum information required in WCDMA scanner log files are Ec and Ec/Io of all available Scrambling code for both Vodafone and Optus frequency.

Vodafone frequency is 2162.4MHz.

Optus frequency is xxxxxMHz.

5.2. Walk test

Optimisation engineer must invite a representative from the JV along with the walk test. The JV representative would choose to be part of the walk test process at random. The walk test must be conducted in a constant speed. The scanner must be held in between 1.5-1.8m above the floor, e.g. chest level.

IBC

6. Ec and Ec/Io requirement

6.1. Ec requirement

The In building system should fulfil all the following requirement:

6.1.1. 100% of walk test route must be Ec>-90dB.

6.1.2. 100% of walk test route must be Ec> design shown in design report.

6.1.3. 98% Ec must be 5dB above macro cells’ Ec without changing any macro cell antenna or parameter configuration.

6.1.4. The in building cell should not be an active server at 20m radius away from the outside wall of the building.

6.2. Ec/Io requirement

The In building system should fulfil all the following requirement:

6.2.1. 100% of walk test route must be Ec>-10dBm.

IBC

7. Coverage Acceptance Report

The coverage acceptance report must keep the look and feel of the IBC Design Report.

The following must consist of the following items:

1. Agreed walk test route overlaid on top of floor plan.

2. Walk test route ‘snail trial’ of Ec overlaid on top of floor plan.

3. Walk test route ‘snail trial’ of Ec/Io overlaid on top of floor plan.

4. Percentage of walk test route meeting requirement shown in section 6.1.1, 6.1.2, 6.1.3 and 6.2.1.

5. Elaborate problems discovered during walk test and steps taken to overcome the problem. Eg. Found loose feeder connection and wrong feeder input into coupler etc.

6. If design is changed to meet Ec, Ec/Io requirements, an updated design report must be attached to the report. The updated design report must be of the same format as the original report highlighting changes made to the original design. This report shall be of the same title of the original design report labelled as Version 2.

7. DAS acceptance report to be attached. Minimum items in DAS acceptance report should include the following:

a. VSWR sweep test results.

b. Minimum coupling loss.

c. Distance to fault.

d. 0dBm signal insertion result for each antenna port.

e. Combiner isolation test.

IBC

8. Neighbour list optimisation

Neighbour list optimisation is not included in this process. However, the log files must be passed to the In building system designer of respective operator ie. Vodafone (AAPCS), Optus (Nokia), for neighbour list optimisation.

IBC

9. 2G data collection

This section specifies the process and requirement of 2G data collection.

The optimisation engineer will be provided with 2G sim card of both Optus and Vodafone.

9.1. 2G data collection equipment

The optimisation engineer can propose equipment to be used for data collection. The equipment must work in conjunction with software which will produce a ‘snail trail’ of the walk test overlaid on top of the floor plan. Example this equipment would be TEMS light. The ‘snail trial’ to be demonstrated MUST follow the agreed walk test route specified. This walk test route does not have to be the same walk test route as the 3G walk test route.

Minimum information required from the 2G data collection are:

9.1.1. RxLev of server all and neighbours measure of both Vodafone and Optus frequency.

9.1.2. Daily and busy hour statistically drop call rate for 1week.

9.1.3. Daily and busy hour statistically call setup success rate for 1week.

9.1.4. Daily and busy hour statistically traffic Erlang for 1week.

9.2. Walk test

Optimisation engineers will be provided with both Vodafone and Optus 2G sim card. This sim will be used for the walk test. The optimisation engineer can choose either perform the walk test of both operator concurrently or one after another as long as the walk test route is consistence.

Optimisation engineer must invite a representative from the JV along with the walk test. The JV representative would choose to be part of the walk test process at random. The walk test must be conducted in a constant speed. The equipment must be held in between 1.5-1.8m above the floor, e.g. chest level.

9.3. RxLev Requirement

All the following requirement must be met:

9.3.1. The 100% of RxLev of server, unless otherwise stated in the design report, should be at least equal to the RxLev data collected before the In building system is upgraded.

9.3.2. The daily and busy hour statistical drop call rate must be at most of 1% deviation before the system is upgraded.

9.3.3. The daily and busy hour statistical call setup succes rate must be at most of 1% deviation before the system is upgraded.

IBC

IBC