RNP_ProcDesc_ed03.pdf

1/2

Site LUDWIGSBURG

MOBILE NETWORK DIVISION

Professional Customer Services

Originator(s) Matthias Hahn, Gunter

Schubert, Franz-Josef Klein, Jens Eichelbaum

Radio Network Planning Process for GSM/UMTS

Domain : RADIO NETWORK PLANNING Division : Quality & Organization Rubric : PROCESS DESCRIPTION Type : PRODUCT DESCRIPTION Distribution Codes Internal : IDDL External : EDDL

PREDISTRIBUTION (for document reading cycle):

Name Dept. Name Dept. Name Dept. K. Heinlein PCS M. Hahn PCS K. Daniel ND F.-J. Klein PCS F. Ehret OFS H. Ramzi ND X. Jiao PCS H.-J. Majcher PCS E. Detollenaere CSPL E. Salomon PCS P. Schneider ACS/O C. Blachier PCS F. Jarreau PCS ABSTRACT

This document describes the Radio Network Planning Process for GSM and UMTS networks. The process is subdivided into smaller entities. For each entity the responsible department, the output and the interfaces are given.

KEYWORDS

RNP, Process Description, GSM, UMTS

Approvals (get approvals from document manager)

Name

App.

Appraisal Authority: C. Brechtmann, PCS

M. Hahn, PCS K. Heinlein, PCS

Name

App.

ED 03 RELEASED CONFIDENTIAL

RCD RNP_ProcDesc_ed03.doc 2002-04-12 3DF 00902 3000 DEZZA Y

3DF 00902 3000 DEZZA Y 2/2 RNP_ProcDesc_ed03.doc RCD

CONFIDENTIAL RELEASED 03 ED

REVIEW

HISTORY

Edition Date Reason of Change ED 01 97/05/22 Creation ED 02 01/01/08 Total revision, including UMTS ED 03 Draft 1 01/03/30 Including latest information in chapter

3.3 Step 2: ED 03 Draft 2 02/02/19 Updating the process with latest information from the

field.

Short description of significant changes to previous edition: Including UMTS RNE process Process description subdivided in more detail Responsibilities added INTERNAL REFERENCED DOCUMENTS Not applicable FOR INTERNAL USE ONLY

Not applicable IDDL - ALCATEL-INTERNAL DOCUMENT DISTRIBUTION LIST (Announcement of document availability by e-mail) Originator, Predistribution and Stuttgart Vlizy

Name Dept. Name Dept. Name Dept. Documentation Management Systems : DIAMS, CMCS EDDL - ALCATEL-EXTERNAL DOCUMENT DISTRIBUTION LIST (electronic attachment to e-mail or paper copy) Stuttgart Vlizy

Name Dept. Name Dept. Name Dept.

END OF DOCUMENT

3DF 00902 3000 DEZZA 3/38 RNP_ProcDesc_ed03.doc RCD

RELEASED 03 ED

PRODUCT DESCRIPTION

TABLE OF CONTENTS

REFERENCED DOCUMENTS ..................................................................................... 5 PREFACE ................................................................................................................. 5 SCOPE..................................................................................................................... 5 1 Overview & Flowchart of the RNP process .......................................................... 6 1.1 Differences between GSM and UMTS network planning processes...................................6 1.2 Anticipation Program differences to the normal RNP process.....................................6 1.3 Overall RNP Process .....................................................................................................7 1.4 Detailed RNP Process Flowchart - Description.................................................................8 2 Detailed RNP Process Flow Chart ........................................................................ 9 3 Detailed description of the different steps of the RNP process ......................... 16 3.1 Step 0: Evaluating Customer Requirements ..................................................................16 3.2 Step 1: Preliminary Network Design.............................................................................16 3.3 Step 2: Project Setup & Management...........................................................................17 3.4 Step 3: Initial Radio Design .........................................................................................18 3.5 Step 4: Planning of Fixed Part of Mobile Network .........................................................19 3.6 Step 5: Delivery of Site Candidates ..............................................................................19 3.7 Step 6: Find Alternative Site.........................................................................................19 3.8 Step 7: Check SAR......................................................................................................20 3.9 Step 8: Correct SAR ....................................................................................................20 3.10 Step 9: Site Acceptance (IEA) .....................................................................................20 3.11 Step 10: Site Ranking (CER).......................................................................................21 3.12 Step11: Start Site Contract Negotiation......................................................................21 3.13 Step 12: Technical Site Survey ...................................................................................21 3.14 Step 13: Creation of Site Layout Plan.........................................................................22 3.15 Step 14: Sign Lease Contract ....................................................................................22 3.16 Step 15: Request for Building Permit ..........................................................................23 3.17 Step 16: Detailed Site Layout Plan .............................................................................23 3.18 Step 17: Civil Works and Site Preparation ..................................................................23 3.19 Step 18: Basic Parameter Definition...........................................................................23 3.20 Step 19: Installation..................................................................................................24 3.21 Step 20: TOC Parameter Definition ...........................................................................24 3.22 Step 21: Commissioning and Integration ...................................................................25 3.23 Step 22: Call Test .....................................................................................................25

03 02/02/19 Update C. Brechtmann M. Hahn, PCS

02 01/01/08 Update (New Ref. Number) C. Brechtmann, PCS M. Hahn, PCS

01 97/05/22 Creation R. Klahm, COR R. Collmann, COR

ED DATE CHANGE NOTE APPRAISAL AUTHORITY ORIGINATOR

Radio Network Planning Process for GSM/UMTS


RELEASED 03 ED

3.24 Step 23: TOC Activation ...........................................................................................26 3.25 Step 24: Site Verification / Drivetest ...........................................................................27 3.26 Step 25: Stability Test................................................................................................27 3.27 Step 26: Hardware / Software Problem Detection.......................................................27 3.28 Step 27: Basic Network Optimization.........................................................................28 3.29 Step 28: Preparing Network Acceptance ....................................................................28 3.30 Step 29: Network Acceptance Test .............................................................................28 3.31 Step 30: Further Optimization ...................................................................................29 4 RNE Project Scheduling ..................................................................................... 30 5 RNP Process Related AIO Service Modules........................................................ 34 APPENDIX A ......................................................................................................... 36 LIST OF ABBREVIATIONS ...................................................................................... 37


RELEASED 03 ED

REFERENCED DOCUMENTS

[1] Forms and templates for anticipation programs / projects 3DF 00902 UA30 PTZZA

[2] GSM/UMTS Preliminary Network Design Questionnaire (Available within/from Mobile Network Design department)

[3] All-In-One Services Roadmap Phase 6 (aiodpP6d.xls) aww.rcd.alcatel.com ->AIO -> Support Center

[4] All-In-On Technical Feature Descriptions Phase 6.1 aww.rcd.alcatel.com ->AIO -> Support Center

[5] Business Management Process; 8BL 10200 0001 UZZZA

[6] Modules of Service Activities, 8AK 07021 0016 ASZZA

PREFACE

This document describes the different steps and responsibilities of Radio Network Planning for GSM and UMTS networks.

SCOPE

Each main step of the RNP process is described in this document. As no RNE project is like the other one due to different pre-conditions, this process description is giving the main steps of the RNP process with its contents and responsibilities, but does not explain each procedure. This is subject to the respective engineering guidelines for GSM and UMTS.


RELEASED 03 ED

1 OVERVIEW & FLOWCHART OF THE RNP PROCESS

In this chapter the differences between GSM and UMTS projects and the aim of an anticipation program are given. Furthermore it will be explained, how the process flowchart in chapter 2 has to be read.

The forms used during the RNP process are given in the process flowchart of chapter 2, can be found in [1]. Furthermore a list of the used forms is given in the ANNEX.

1.1 Differences between GSM and UMTS network planning processes

It is not described in this document how to find suitable site areas, and what parameters are influencing this. This document focuses on the process, e.g. who is responsible for finding suitable site areas, what is the output and who has to use this information for doing the next step. The method of finding suitable site areas is of course different for GSM and UMTS networks, but this does not influence the content of this document.

Assuming a greenfield design (no existing network), both system technologies follow mainly the same planning process. The only difference between them is the contents of the step CAE parameter planning, as the systems will have different parameters.

The more usual case is to reuse the existing infrastructure from 2G networks to deploy 3G networks more cost effective and faster. Thus for the UMTS planning process, the part definition of search areas will only be true for UMTS sites where no existing GSM site is available in the area of interest. Through the reuse of existing sites the acquisition process will be different. The acquisition team has to negotiate with the site owner about adding additional equipment.

Conclusion:

The RNP process itself does not differ between UMTS and GSM networks, just the internal planning methods can differ.

1.2 Anticipation Program differences to the normal RNP process

To convince a possible customer to choose Alcatel as supplier, one strategy is to perform an anticipation program. The anticipation program is more or less identical with the first part of the complete RNP process. As it is not sure to get the contract after doing the anticipation, the process is stopped after the step Site Ranking or Request for Building Permit. The main goal is to show the customer the experience of Alcatel in planning radio networks and to reserve suitable sites for the customer.

Anticipation programs follow in general steps number 0 to 10 or15 in the RNP process flowchart (see 2 - Detailed RNP Process Flow Chart). The final step of the anticipation program depends on the customer requirements, budget and time schedule.

If there is no pre-deployment included in the anticipation program, the intention is to stop the RNP process for all sites at this stage until the contract with the operator is signed. In case of pre-deployment, pre-booking is done.


RELEASED 03 ED

1.3 Overall RNP Process

To provide an overview on the overall RNP process, this section shows and describes the main processes and important project milestones.

NetworkDesignPhase

Design Bill of Quantity (BSS) Coverage prediction

Site SearchRadio Network Planning

Implementation

Basic OptimizationBTS Re-location

Overall networkoptimization

QoS enhancement

MS: Initial Radio Design Complete and Approved

MS: PAT passed

First BTSclusters on air

Network commercial operation

MS: FAT passed

Optional Post-Turnkey optimization phaseExtensions

MS: Site Integrated

NetworkDesignPhase

Design Bill of Quantity (BSS) Coverage prediction

Site SearchRadio Network Planning

Implementation

Basic OptimizationBTS Re-location

Overall networkoptimization

QoS enhancement

MS: Initial Radio Design Complete and Approved

MS: PAT passed

First BTSclusters on air

Network commercial operation

MS: FAT passed

Optional Post-Turnkey optimization phaseExtensions

MS: Site Integrated

Figure 1: Overall RNP Process

Network design phase

This phase includes all tasks related to the initial radio network planning. The customer will normally approve the initial design, before the site acquisition for all sites can be started. Accepting the initial radio design leads to the milestone Initial Radio Design Complete and Approved.

Radio network planning, implementation and optimization phases

This phase is the most time consuming one from RNE point of view. This part is described in detail within the chapter 3. As soon as the first cluster of BTSs is on air, the optimization phase can start for this area. As soon as the implementation of the planned equipment is finished, Preliminary Acceptance Tests (PAT) can be done on a cell or cluster basis. Even if the QoS guaranteed in the contract (to be validated by the Final Acceptance Test FAT) is not achieved, the network can go into commercial operation to provide revenues as fast as possible. The commercial operation is normally started after the milestone PAT passed is achieved.

End of turnkey project and optional additional tasks

After passing the PAT, clusters are further optimized (if necessary) to be able to pass the Final Acceptance Test (FAT). If the FAT is passed by reaching the requested QoS values (Key Performance Indicators KPI) in predefined acceptance areas stated in the contract, the milestone FAT passed is achieved. This is the end of the turnkey project if no other commitments are given in the contract. Optionally Alcatel can perform further optimization and QoS improvements.


RELEASED 03 ED

1.4 Detailed RNP Process Flowchart - Description

The RNP process is subdivided into different steps shown in Figure 2. Each step contains information about

Responsible department/team

Name of the process step

Reference number

Rough contents

Output

Output format for delivering the required input to the next RNP process step

Where to find this information in the flow chart is shown by the following demo step on page 8.

The process flow chart itself is given in the next chapter 2 Detailed RNP Process Flow Chart.

Within the flowchart, documents for information exchange are given, e.g. SAM (Search Area Map). These documents are summarized in [1].

RNE Dummy Step

This step is for explaining the contents of theflowchart steps.

1

O Dummy_output I Dummy_interface

Responsibledepartment / team

Name of the stepStep reference

number

Step contents

Interface formatto next stepOutput of the step

2

0

Input to this step iscoming from step #0

Output of this step isused by step #2

Figure 2: Example step for explanation of step description


RELEASED 03 ED

2 DETAILED RNP PROCESS FLOW CHART

RNE Initial Radio Design 3

RNP tool calibration Area surveys Definition of search areas (SAM) Selection of number of sectos/TRX per site together with

PM and customer Get real design acceptance from customer based on

coverage prediction and predefined design level thresholds

O Revised BoQ, Search Area Map

I BoQ, SAMs, RNP tool files

SAL/ND/RNE Customer Requirements (RfQ) 0

Coverage Requirements QoS Requirements Traffic Assumptions

O Filled Questionnaire I Document with Cust-omer Requirements

ND/RNE Preliminary Network Design 1

Geo Data Procurement if required Coverage Plots Definition of standard equipment configurations Definition of roll out phases Network architecture design Creation of Bill of Quantity (BoQ)

O Dimensioned Network I BoQ, Report, RNP tool files

PM/RNE/ND/TEN/SEN/SAQ Project Setup & Management

2

Geo Data Procurement if required Setting up the global rules of the project define and agree on reporting scheme to be used Each department to prepare its part of the project Definition of required manpower and budget Selection of Project Database More details can be found in the text afterwards

O Project Plan, defined process/milestones

I CustomizedRNE-Guideline

5 4

Start of anticipation program


RELEASED 03 ED

No

No

TMP/RNE Planning Fixed Part of Mobile Network 4

Definition of BSC/RNC sites (size/location) Selection of transmission technology Planning of network topology Planning of all links between Node B/BTS BSC/RNC and

MSC BSC Dimensioning

O Network Architecture/Topology

I TBD

Important Note: Module 4 is a long lasting process, which is triggered first time for the Initial Radio Design. Its output is determined interactive with the outputs of the RNE modules down to module 8.

9, 12

3

SAQ Delivery of Site Candidates 5

Search ca. 3 possible site candidates Select only sites were contract is not impossible For each candidate fill Site Acquisition Report SAR

O List with site candidates I SAR

RNE Check SAR 7

Check if the SARs content is sufficient to qualify the candidate

O Accepted / Rejected SAR I SAR, Project Database

RNE Find Alternative Site 6

Whenever a planned site is not possible (whatever the reason is) alternatives have to be found

O Proposal of site alternatives I SAM

SAQ Correct SAR 8

Correct SAR content

O Site candidate I SAR, Project Database

Site found?

Yes

SAR accepted?

Yes

9

9


RELEASED 03 ED

Site approved and contract negotiation positiv.

RNE/TMP Site Acceptance (IEA) 9

If necessary perform site survey (SAQ is responsible for organisation)

O Accepted/Rejected site candidates

I RIEA, TIEA

SAQ/RNE/ TMP/SEN

Site Ranking (CER) 10

d Based on RNE given priorities Influenced by TMP, SEN

O List with ranked sites I CER, Project Database

Site accepted? No

Yes

7

5

SAQ Start Site Contract Negotiation 11

Take site with highest ranking on list Organize date for final site survey

O Date for TSS, ongoing contract negotiations

I Invitation, Project Database

SAQ/RNE/TMP/SEN Technical Site Survey 12

Define antenna directions / mast positions / BTS location & type / power supply / transmission RNE/TEN check EMS compatibility with other installed

devices Final Line Of Site (LOS) confirmation

O Site layout definition I TSSR, RFEA, TFEA

No

Yes

13

4

Earliest stop foranticipation programs

Alternative Site available? No

Yes

5


RELEASED 03 ED

17 18

SEN Creation of Site Layout Plan 13

Create Site Layout Play To be signed by RNE / TEN

O Site Layout Plan I Site Drawings

SAQ Sign Lease Contract 14

Owner signs site contract

O Lease Contract I Lease Contract, PDB

SAQ Request for Building Permit 15

The site layout plan is used to get the building permits from the relevant authorities EMC situation on site must fulfill local rules for getting

the building permit

O Building Permit I Building Permit

SEN Detailed Site Layout Plan 16

Creation of site delivery list Revise bill of quantity (BoQ) Material and Equipment Purchase Order Order of Power Connection and LL (if necessary)

O Site Delivery List I Delivery List

Site drawings accepted? No

Yes

12

Latest stop foranticipation programs

Contract signed? No

Yes

11

Both processes canrun in parallel.

Alternative Site available? No

Yes

5


RELEASED 03 ED

SEN Civil Works and Site Preparation 17

Installation of masts, building towers, etc. Power supply

O Prepared site I

OFS/RNE Basic Parameter Definition 18

General CAE / BSS parameters Testparameter Templates

O CAE Software I PRC File Template

RNE TOC Parameter Definition 20

Frequency Neighborhood list Transmit power Generating of PRC files with A955 PRC GeneratorO PRC Files, TOC activation

form I A955 PRC Generator,

PDB

OFS Commissioning and Integration 21

Set testparameters Test links Site must have connection to OMC-R

O Commissioning and Integration Report

I Commissioning and Integration Report

OFS Installation 19

Installation of antennas, BTS, feeders, rectifiers Transmission equipment

O Completely installed site I Punch List

16

OFS Call Test 22

Call setup and release BCCH, antenna system check If feeder cross connection detected then direct

corrective action Intra site handover

O Commissioning and Integration Report

I TBD

23


RELEASED 03 ED

RNE TOC Activation 23

Upload PRC files into OMC-R Unlock site

O Partly launched network I TOC Activation Form

OFS Stability Test 25

24h on air test

O TBD I TBD

RNE Site Verification / Drivetest 24

Check frequencies / neighbors / scrambling codes Check coverage (cell coverage footpring) Check quality and handover

O Drive Test Report I TBD

OFS/RNE HW / SW Problem Detection 26

Lock site Error detection Problem solving Eventually adjusting antenna tilt, orientation

O Request for fault elimination

I Change Request Form

RNE Basic Network Optimization 27

Networkwide air interface drive tests and KPI measurements Optimization of the network If required add new sitesO Optimized site and cluster

(area) I Drivetest Report,

KPI Report

Predicted coverage area fulfilled and site working properly? No

Yes

22 20

RNE Preparing Network Acceptance 28

Calculate results according to acceptance requirements in contract (KPI monitoring)

O Calculation results I Measurement Report

Acceptance requirements fulfilled?

No

Yes

29

If new sites have to be added it might be necessary to go back to step 4 again.

If new sites have to beadded it might be

necessary to go back tostep 4 again.


RELEASED 03 ED

Important Remark: The steps related to the Turn On Cycle (TOC) depend on the used system technology. The given process description only shows the GSM process and might be adapted for UMTS in the future. These steps are:

18 Basic Parameter Definition 20 TOC Parameter Definition 23 TOC Activation

28

RNE Further Optimization 30

Optimization of network when it is already in commercial operation As the network is in commercial operation the significant

traffic allows to use OMC based statistics by using A956 RNO and A985 NPA End depends on contract and mutual agreement

between Alcatel and customerO Improvement of KPI I Predefined regular

reports from A956

RNE Network Acceptance Test 29

Presentation of KPI to the customer Customer accepts network by comparing requirements

and calculated network results

O Radio Network Test Acceptance Report

I Acceptance Report, PDB


RELEASED 03 ED

3 DETAILED DESCRIPTION OF THE DIFFERENT STEPS OF THE RNP PROCESS

This chapter gives a detailed description for each step defined in the previous section.

3.1 Step 0: Evaluating Customer Requirements

Content: Before the network can be dimensioned or planned, the requirements given by the customer have to be known or, in case e.g. of anticipation programs, to be assumed. Based on these requirements, the dimensioning of the network (preliminary network design) is possible.

Important requirements are e.g.: Traffic assumptions, coverage areas, service classes, QoS values to be achieved, etc. This information is usually part of the RfQ from the customer.

Responsible: Sales Department / UMTS pre-sales department

Output: Filled questionnaire, giving the required details for dimensioning/planning a mobile communication network

Interface: Filled GSM/UMTS Preliminary Network Design Questionnaire [2] Anwers to the RfQ

3.2 Step 1: Preliminary Network Design

Content: In case of a RfQ or a dedicated anticipation program, ND uses the filled questionnaire. In case of a generic anticipation program ND is using default or estimated values.

Using the questionnaire or estimated values, a first rough network design is made using link budget calculations. According to the link budgets, the cells are more or less equally distributed over the area to be covered. Coverage is proofed by using the Alcatel RNP tool (Back-Office RNP). As a planning tool is used, digital databases have to be procured.

Another part of the dimensioning step is the dimensioning of the BSCs/RNCs, MSCs, required transmission equipment and backbone (network architecture and Preliminary Transmission Design).

The results from the dimensioning parts are used to calculate the bill of quantity, giving the amount of equipment needed for installing the network. As the output of this process is directly linked to the price of the Alcatel offer, the calculation is usually optimistic in order to reduce its overall cost and make it more attractive (money oriented approach). This step also includes a Geo-Marketing analysis and Telecom Landscape study (field constraints like interconnection, existing backbone, cost of Leased lines,) anything that can influence the architecture.

In addition, the standard configurations of the BTSs/Node Bs are defined, to minimize the number of configurations to be handled within the project.

As the number of subscribers within a network is growing, the network has to grow also. Thus, different roll-out phases are defined. Each roll out phase is characterized by the areas to be covered, the number of sites to be installed and of course the date, when the roll out takes place.

Responsible: Network Design department (ND); support by RNE

Output: Dimensioned Network inclusive Bill of Quantity


RELEASED 03 ED

Interface: Preliminary Network Design report, RNP files and Bill of Quantity (BoQ)

3.3 Step 2: Project Setup & Management

Content: The project setup and management phase includes all tasks to be performed before the on site part of the RNP process takes place. This ramp up phase includes:

ALL:

Define targets & dimension teams

Define Budget

Define reporting channels

Define necessary equipment and tools

Organize training for staff on used tools/equipment

Select Project Database (normally combination of MatrixX and PMS 2000)

PM:

Budget approval and follow up

Provide office environment

RNE:

Perform RNE project setup and management

Define network identifier coding (site, NE, Link, LAC, CI) together with other departments

Estimation of the required human resource in the different teams

Select consultants for RNE

Select external teams, e.g. for acquisition, measurement campaigns,

Make external planners familiar with Alcatel BSS and planning strategy

Purchase digital databases if not yet done by ND (step 1)

SAQ:

Collect information about local law, e.g. EMC rules, civil work limitations

Find hereafter some rules of thumb for calculating the required RNE human resources:

Duration of ramp up phase after signature of contracts: 2 months During that time the already available Radio Network Planning engineers can perform area surveys in the area they are responsible for and start preparing Initial Radio Design.

Output of Radio Network Planning after this phase: 5 sites per month per planner This output is an effective number which already includes waiting periods (e.g for site canditates provided by acquisition). Please keep in mind that for each real site the planner has to consider as an average 3 site alternatives including site surveys.


RELEASED 03 ED

Note: For swap-out projects, where only a few sites have to be found (most of the existing sites will be reused), the ramp-up phase takes 1 month and 12 sites per planner and month can be expected.

Additionally to the number of RNEs calculated with the rules given before, the final RNE headcount has to take teamleaders, RNE managers and some exports for tool support, drivetests, etc. into account. Find an example for RNE team organization in Figure 3.

TeamleaderCentral Services

RNE TeamleaderRegion 1


RNE TeamleaderRegion n..

Project DB / A955 Support

Planer 1Planer 2

Planer xDrivetestBasic Opt.

..

Planer 1Planer 2

Planer yDrivetestBasic Opt.

..

Planer 1Planer 2

Planer zDrivetestBasic Opt.

..

Architecture Network Performance Acceptance Tests Student Assistant

CAE ParameterProject Follow UpInitial NetworkDesign

..

RNEManager

TeamleaderCentral Services



RNE TeamleaderRegion n..

Project DB / A955 Support

Planer 1Planer 2


..

Planer 1Planer 2


..

Planer 1Planer 2


..

Planer 1Planer 2


..

Planer 1Planer 2


..

Planer 1Planer 2


..

Architecture Network Performance Acceptance Tests Student Assistant



..

RNEManager

Figure 3: Proposal for RNE team setup

This phase must not be underestimated when setting up the project plan.

Responsible: PM, ND, RNE, TMP, SEN, SAQ

Output: Project plan, means the goals to be achieved during the project are allocated on a time scale -> milestones are defined.

Interface: Project plan, customized RNE Guideline and Project Database setup

3.4 Step 3: Initial Radio Design

Content: The initial radio design done by the RNE team, is based on first area surveys. A search area is characterized by its center location and its radius. The search area for the sites is defined according to the given traffic and propagation conditions. According to maps or area surveys the search areas are defined only in areas, where possible site locations (buildings, masts) can be found. The Search Area Map (SAM) includes these search areas. The design achieved by the initial radio planning would be ready for implementation if for all search radii a suitable site can be acquired, and of course the transmission connection (Abis, A) is possible.


RELEASED 03 ED

In large projects, were many RNE are involved in the Initial Radio Design phase, it is important to arrange meetings between the different RNEs where the proposed designs can be reviewed.

Every radio network planning task after the initial radio design will trigger a permanent re-design process (adaption) of the Initial Radio Design.

Responsible: RNE

Output: Revised BoQ, Search Area Map

Interface: BoQ, Search Area Map, RNP tool files (A955 files), Project Database

3.5 Step 4: Planning of Fixed Part of Mobile Network

Content: The TMP team works closely together with the RNE team. His job is to find suitable locations for BSC sites and define the architecture of the network. On the one hand, it would be advantageous to know all BTS locations in beforehand for finding suitable BSC sites. On the other hand it is not always possible to establish the transmission in this case (especially with microwave links). So the locations of BTS and BSC must be - up to a certain extend planned interactive. This can be seen e.g. at step 12, the technical site survey. Here RNE, TMP and others are doing the survey together for approving an acceptable site for all parties.

This process description does only cover the Radio Network Planning part of a project. Transmission Planning is another large part. This step replaces all necessary steps necessary for complete transmission planning.

Responsible: TMP/RNE

Output: Network Architecture, network transmission plan, network routing plan

Interface: Project Database, Transmission Planning tool files

3.6 Step 5: Delivery of Site Candidates

Content: The site acquisition (SAQ) team receives from the RNE team SAMs including - among other things - the search area location coordinates and radius. The SAQ team selects approximately 3 possible site candidates per given search area. These candidates must fulfill the requirements and there must be a possibility to get a contract with the site owner. The SARs are handed over to RNE. HO is monitored by Project Database.

Responsible: SAQ (Acquisition team)

Output: For each SAM three site candidates described in the SAR

Interface: SAR (Site acquisition report)

3.7 Step 6: Find Alternative Site


RELEASED 03 ED

Content: During the planning process of a mobile network, there are lots of possibilities that a suitable candidate is not available within the search area. In this case alternative sites or search areas will have to be defined. This step is will be jointly accomplished by RNE and SAQ.

As often RNE has to look for alternative sites (re-design the network), as more the final network will be different from the initial radio design.

Responsible: RNE

Output: Proposal of site alternatives

Interface: SAM

3.8 Step 7: Check SAR

Content: The RNE receives from SAQ the three SARs/SAMs and checks, if the SAR is complete. SARs containing the obligatory site information are accepted by the RNE. A SAR is incomplete, if it is impossible to qualify a site candidate for acceptance due to missing information. SARs with missing information are rejected and sent back to SAQ (step 8). The monitoring of this procedure is done in the PDB.

In general the SAR check and the site ranking should not last longer then five days, to avoid the owner to change his mind meanwhile.

Responsible: RNE

Output: Accepted / Rejected SAR

Interface: SAR, Project Database

3.9 Step 8: Correct SAR

Content: SAQ receives all rejected SARs from RNE. These SARs will be corrected, missing information added and sent back to RNE. The monitoring is of this procedure is done in the PDB.

Responsible: RNE

Output: Corrected SARs

Interface: SAR, Project Database

3.10 Step 9: Site Acceptance (IEA)

Content: If the RNE is satisfied with the coverage conditions given by the site candidate and the TMP can ensure the possibility to connect the site with the network, both will accept this site. An acceptance is indicated in the corresponded Initial Engineering Approvals (RIEA, TIEA) and in the PDB.

If the RNE or TMP needs a site survey to finalize his decision on acceptance, this survey has to be organized by SAQ. Especially for critical sites (coverage area difficult to predict) it is possible that


RELEASED 03 ED

wave propagation measurements have to be done for coverage verification before a decision on acceptance can be made.

Site candidates not accepted by the RNE, TMP; SEN or SAQ for different reasons can be monitored in the PDB.

Responsible: RNE, TMP

Output: Accepted / Rejected sites

Interface: RIEA, TIEA, PDB

3.11 Step 10: Site Ranking (CER)

Content: In the CER (Candidate Evaluation Report) all accepted sites for one search radius are sorted by their radio conditions and their possibility to be finally built or not. The result is written in the candidate evaluation report.

Responsible: SAQ, RNE, TMP, SEN

Output: List with ranked sites

Interface: CER (Candidate Evaluation Report), PDB (Project Database)

3.12 Step11: Start Site Contract Negotiation

Content: The target is to get the site with highest priority from the site ranking list under lease contract. Under contract means, that the owner allows the operator/Alcatel to put its equipment at the owners premises. For this reason SAQ organizes a date for a technical site survey with all relevant persons to define the equipment configuration and the installation of the site. This is generally a precondition to convince the owner for final lease contract negotiations.

Sometimes SEN has the responsibility to care for the date of the final site survey.

Responsible: SAQ

Output: Date for final site survey

Interface: Invitation, PDB (Project Database)

3.13 Step 12: Technical Site Survey

Content: During this survey the involved people visit the site and agree on an equipment installation solution satisfying the needs of RNE, TMP, SEN and the owner.

During the survey the following is defined and written in the Technical Site Survey Report (TSSR):


RELEASED 03 ED

Antenna type, position, bearing and tilt

Mast/pole or wall mounting position of antennas taking also EMC rules into account

BTS/Node B location

Power and feeder cable mount

Transmission equipment installation

Line of Site (LOS) confirmation

It can be possible that obviously the site is not acceptable or the owner disagrees with all suggested solutions. In such a case the site will be rejected and SAQ has to organize a new date with the next site from the ranking list.

Responsible: SAQ, RNE, TMP, SEN

Output: Site layout, final equipment definition

Interface: TSSR (Technical Site Survey Report), RFEA, TFEA

3.14 Step 13: Creation of Site Layout Plan

Content: Taking the TSSR and its sketches the SEN has to prepare the site layout plan according to the agreements during the final site survey. RNE and TMP have to accept (sign) this first site layout plan before the owner has to give his final OK (signature).

If one signature is missing, the plan has to be corrected until the plan gets all signatures. Additionally SAQ can organize a further site survey if it is convenient.

Responsible: SEN

Output: Site layout plan

Interface: Site layout plan

3.15 Step 14: Sign Lease Contract

Content: The owner signs the lease contract. The site layout plan, a major part of the site contract is because it includes everything that will be built on the owners premises.

If the contract differs significantly from a standard contract the customer has to approve it before the owner finally signs it.

The owner normally gets a rent from the day the site is under construction. This eliminates the risk of having a site contract without getting a building permit.

A signed contract will be monitored in the PDB. A copy of the lease contract is part of the site documentation.

Responsible: SAQ

Output: Lease Contract

Interface: Lease Contract, PDB


RELEASED 03 ED

3.16 Step 15: Request for Building Permit

Content: Using the site layout plan, SAQ has to contact the local authorities for getting the site building permit. In some countries the corresponding authority checks EMC before the permission is applied. It depends on the country what are the exact rules to get the building permit.

If the permission is rejected, either the layout plan has to be modified (back to step 12 Final site survey) or a complete new site has to be found (step 11 Start Site Contract Negotiation).

After getting the building permit the site reaches the milestone Site Ready to Build.

Responsible: SAQ

Output: Site building permit

Interface: Building Permit

3.17 Step 16: Detailed Site Layout Plan

Content: The SEN creates a detailed site layout and construction plan after getting the building permit for the site. This is called the executive project. This plan describes the installation in detail.

Based on it, the site related delivery list to purchase the required material and equipment will be created. The project wide BoQ will be updated.

Responsible: SEN

Output: Site delivery list, revised bill of quantity (BoQ)

Interface: Delivery List

3.18 Step 17: Civil Works and Site Preparation

Content: In this step SEN performs all necessary civil works to prepare the site for installation of antennas and equipment. This includes building masts, towers, feeder mount, power supply, etc.

After this step the equipment should be delivered and the site reaches the milestone Equipment Delivery.

Responsible: SEN

Output: Prepared Site

Interface: TBD

3.19 Step 18: Basic Parameter Definition

Content: This step is not yet defined for UMTS, so it is only valid for GSM networks.


RELEASED 03 ED

OFS generates the basic software based on templates defined by RNE. These are temporary CAE test parameters that are used for later commissioning and installation and the following call test. Following parameters have to be defined:

CI/LAC/BSIC

Test frequencies / intra site neighborhood relations

Test transmit power

Cell type (macro, micro, umbrella, )

Abis/A settings

Responsible: OFS, RNE

Output: CAE Software

Interface: PRC File Template

3.20 Step 19: Installation

Content: After equipment delivery OFS installs the BTS, antennas, feeders and rectifiers as well as the required transmission equipment. After this step the equipment hardware on the site is completely installed and all installation faults are eliminated.

Responsible: OFS

Output: Completely installed site, punch list

Interface: punch list

3.21 Step 20: TOC Parameter Definition

Content: A TOC is a Turn on Cycle. The network is launched step by step (TOC by TOC) because it is not possible to wait with the opening of the network until the last BTS is integrated. A single TOC cycle is typically two or three weeks long. It should not be mismatched with the different rollout phases of a network where each phase has duration of months or even years.

The RNE has to decide which sites go on air during the next TOC and should therefore be considered for this parameter definition. The definition of the candidates is necessary because it is only possible to calculate the frequency plan if all involved sites are known.

Parallel to the whole equipment installation and commissioning the RNE team can define the TOC software. This step is not yet defined for UMTS, so it is only valid for GSM networks.

First the CAE parameters are defined. They will be used for this site on the next TOC activation. These parameters can change from TOC to TOC, because all sites in an area are activated step by step, so that frequencies for instance can change very often.

The CAE data are calculated by the central A955 RNP tool. For which sites the CAE data have to be planned is given by the PDB. In MatrixX all relevant mile stones (site statuses) can be


RELEASED 03 ED

monitored. The CAE parameters are created in A955, from where the OMC readable PRC files are generated.

Following parameters have to be defined.

GSM:

CI/LAC/BSIC (refer to basic CAE software)

Frequencies / neighborhood relationships

Transmit power

TRX enabled/disabled

UMTS:

Frequency band to be used

Codes to be assigned

Neighbors

Active set members for soft HO

All these data are processed by the A955 PRC generator, which produces corresponding PRC files that are used for further activation of the site.

Responsible: RNE

Output: PRC file, TOC activation form

Interface: A955 PRC generator, PDB

3.22 Step 21: Commissioning and Integration

Content: The equipment of the site has already been installed. The transmission equipment and the BTS are operational and tested. If no failure will be detected, the BTS will be connected to the BSC and test CAE software will be loaded. The BTS is now connected to the OMC-R and future changes in the parameters can be done remotely from the OMC-R.

The status of the site after this step is described in the Commissioning and Integration Report.

Responsible: OFS

Output: Commissioning and Integration Report (without Call Test)

Interface: Commissioning and Integration Report

3.23 Step 22: Call Test

Content: In this step OFS tests a call setup and a call release as well as the intra site handovers. Furthermore the allocation of the BCCH to the correct sector of the BTS is approved. This is done


RELEASED 03 ED

to detect a possible cross connection of feeders. If feeder cross connection or hardware / software failure are detected, corrective action will be directively done on site.

If these tests are successful the site will be locked. That means the site is in hot standby, so that the OMC-R can easily set new CAE parameters and can activate (unlock) this site during a TOC.

The result of the call test is written in the Commissioning and Integration Report.

The site reaches the milestone Site Integrated after this step.

Responsible: OFS

Output: Commissioning and Integration Report

Interface: call

3.24 Step 23: TOC Activation

Content: This step is not yet defined for UMTS, so it is only valid for GSM networks.

The candidate sites for this TOC activation have already been defined during the step TOC Parameter Definition. Due to installation and commissioning problems it can be possible that a site is not ready for activation. In such a case a small update of the TOC PRC files has to be performed (update of neighborhood list, frequency plan, etc.).

Then the PRC files being generated in step TOC Parameter Definition are downloaded into the OMC-R at night. The OMC-R itself distributes the particular PRC files to the dedicated base stations. This is done by a so-called Massive Logical Update (MLU). That means, the complete set of old parameters is swapped with the new ones at once. If there are any parameters not yet defined when activating the cell, default values are used. Finally the sites will be unlocked.

Attention: If the site is on air, commercial mobiles are able to make phone calls on this site. There are two possibilities to overcome this problem:

1. Switch the site off again after implementing the software/parameters ->no possibility to do quick site checks.

2. Keep the site on air and accept the immediate commercial use (quick RNE site check necessary)

Which of the two solutions shall be used has to be defined during this step.

There are other possibilities to overcome this problem (special SIMs, barring, access channel 15) but they are not really suitable for usage during network roll out. More problems are generated, than avoided.

This step also starts the network monitoring for later optimization.

Responsible: RNE

Output: Partly launched network

Interface: TOC Activation Form


RELEASED 03 ED

3.25 Step 24: Site Verification / Drivetest

Content: After the BTS is on air, RNE has to perform a coverage and performance drivetest around the site. The purpose of this drivetest is to compare the real coverage footprint of the cells with the predicted coverage area in A955 tool. If RNE detects coverage holes or areas of high interference, they will have to adjust the antenna tilt and orientation. Furthermore RNE verifies the assigned frequencies/codes and other CAE parameters like BSIC, LAC, handover relationship, etc.

It is highly recommended to perform such a drivetest because todays networks should fulfill such high acceptance requirements. It seems nearly impossible to reach the acceptance criteria without basic site and area optimization. They also limit the probability to have unforeseen network behavior afterwards.

Responsible: RNE

Output: Drive Test Report

Interface: TBD

3.26 Step 25: Stability Test

Content: To approve the correct operation of the full equipment installed on a site, a monitoring period of 24 hours on the OMC is sampled and added as a report to the acceptance document. These reports are created automatically.

Responsible: OFS

Output: TBD

Interface: TBD

3.27 Step 26: Hardware / Software Problem Detection

Content: Due to drive tests or equipment monitoring (OMC; Metrica; A956) problems like equipment faults, SW faults, faulty parameters or faulty antenna installation can be detected. If the problem is classified as serious, the BTS will be locked again until the fault is cleared.

Faulty parameters are corrected by OMC or in the next TOC. Wrong coverage footprints of the site will trigger antenna re-alignments. Faulty equipment will trigger replacement by OFS.

Responsible: RNE, OFS

Output: Request for antenna re-alignment, equipment replacement, parameter change

Interface: Change Request Form


RELEASED 03 ED

3.28 Step 27: Basic Network Optimization

Content: It is highly recommended to perform network wide drive tests (air interface measurements) before doing the commercial opening of the network. These drive tests are used for basic optimization (no traffic yet -> not all parameters can be optimized) of the network. Furthermore, post-processing routines of KPI for the network acceptance can use these results from the air interface measurements.

At this phase of the process all optimization tasks are still site related. Following tasks can be performed: alignment of antenna system, parameter optimization, adding new sites in case of too large coverage holes.

If the network is already in commercial service and only a few sites are going on air with a TOC, the basic optimization will be included in the site verification procedure.

Responsible: RNE

Output: Optimized site and cluster (area)

Interface: Drive test report, KPI Report

3.29 Step 28: Preparing Network Acceptance

Content: The customer has to accept the network or parts of it before the official launch. The acceptance requirements were written in the contract. A partly launch of the network is possible if the majority of the cells are in service.

Digital drive measurements are performed and post processed. A measurement report presenting the KPI values for acceptance is prepared and the results are compared with the values given in the contract.

If the acceptance requirements cannot be reached the network has to be optimized again until the requirements are fulfilled.

Responsible: RNE

Output: Calculation Results

Interface: Measurement Report

3.30 Step 29: Network Acceptance Test

The customer can accept the whole network or only parts of it step by step. The customer compares the real measured coverage and QoS values with the acceptance targets in the contract. This step can include possible penalty negotiations.

After this step the network is ready for commercial launch.

Responsible: RNE

Output: Radio Network Test Acceptance Report

Interface: Acceptance Report, PDB


RELEASED 03 ED

3.31 Step 30: Further Optimization

After successful network acceptance the network goes into commercial operation.

Passing the acceptance test does not mean, that the network already performs a state of the art level. Network optimization is rather a never-ending task in commercial networks.

Usually Alcatel is involved in first post-commercial opening optimization activities. These activities end according to contract or mutual agreements between Alcatel and the customer.

As the network is in commercial operation the significant traffic allows to use OMC based statistics by using A956 RNO and A985 NPA.

Responsible: RNE

Output: Improvement of KPI

Interface: Predefined regular reports from A956


RELEASED 03 ED

4 RNE PROJECT SCHEDULING

Like in every project where several dependent tasks have to be performed, the tasks have to be scheduled and controlled. The Business Management Process [5] gives among other things three main documents to be created before starting of the project:

Program/Project Management Plan (PMP)

Work Breakdown Structure (WBS)

Master Plan Schedule (MBS)

In the Program/Project Management Plan PMP, the overall schedule of the project is given. Scope and objectives of the work of each partner is defined and the roles and responsibilities within the project organization are defined. The RNE related parts of this PMP are included in Step 2 of the RNP process, the Ramp Up Phase.

The Work Breakdown Structure WBS is a breakdown of the total work to be done during the project into small packages. These packages include:

Required Inputs

Deliverables to be produced

Workload

Required resources

External dependencies

Required methodologies

Process to be applied

Completion/measurement criteria

Knowing the completion criteria of each package, the overall process can be monitored by just checking if the completion of the packages is done in time or not. Creating statistics on fulfilling packages in time or not, can be done e.g. by using a site related project follow up tool. Alcatels Project Follow Up tool for RNE tasks is the so-called MatrixX tool, which is developed and maintained by the PCS department. Together with the PMS2000 tool of Alcatel NSD, it will be normally used as Project Database (PDB) for all turn key project related tasks.

The Master Plan Schedule MPS is giving the time frame for each package defined in the WBS.

The intention of this document is not to repeat the Business Management Process given in [5], it shall give a guideline how to plan and control the RNP process. Therefore the overall schedule of the RNE project and an exemplary Site Status Schedule of the planning process of a exemplary site is given hereafter (See Figure 4 and Figure 5). It is important to note, that the definition of such overall and site schedule has to be done at the beginning of the project.

For the following example (Figure 4) of an overall RNE schedule, five different specified site statuses have been assumed. The example network shall have at the end 60 sites on air.


RELEASED 03 ED

Overall Site Status

0

10

20

30

40

50

60

70

Time t

Num

ber o

f Site

s

MS0100 0 20 32 45 55 60 60MS0300 0 10 22 34 45 56 60MS0800 0 0 6 18 37 53 60MS1400 0 0 0 12 30 48 60MS1600 0 0 0 0 20 40 55

t_0 t_1 t_2 t_3 t_4 t_5 t_6

Figure 4: Example for overall RNPproject follow up

Figure 4 shows the overall schedule of the RNP process, which must be reviewed during execution of the project. Comparing this schedule regular with the actual status of the sites gives a clear overview if the project is delayed or in time. S1 to S5 are the site statuses, which have to be reached at a given time (project start t0 up to t6).

To be able to create this overall schedule, the time to bring an average site from one site status into the next one has to be known. This average site schedule has to be defined at the beginning of the project. Figure 5 shows an example for scheduling the site statuses on an average site, assuming five defined site statuses.

It is not possible to define a default average site schedule as it is strongly related to the local conditions like customer requirements, local administration performance, availability of possible site candidates, existing infrastructure etc.


RELEASED 03 ED

MS0100

t0 t1 t2 t3 t4 t5 time t

Site Status

MS0300

MS0800

MS1400

MS1600

MS0100

t0 t1 t2 t3 t4 t5 time t

Site Status

MS0300

MS0800

MS1400

MS1600

Figure 5: Example of site status scheduling

The previous examples assume a number of five different site statuses. This is just for explaining the principle of scheduling without overloading the figures.

Within the project many site statuses are defined, reflecting the structure of the local teams. As it is not possible to define all site statuses in this generic document, hereafter the most important site statuses are given. They correlate of course with the RNP process flow chart. For easy follow up of the site development, each statuses gets a unique number, which can be used for status reporting. Sub statuses can easily use the numbers between the basic site statuses.

Table 1: Basic site status

Mile Stone Mile Stone Name Relation to RNE process flow chart

MS0100 Search Area Map Issued 3 - Initial Radio Design

MS0200 Site Option Approved 9 - Site Acceptance

MS0300 TSS Complete 12 Final Site Survey

MS0400 Site Rental Approved 13 - Creation of Site Layout Plan

MS0500 Network Link Planned 4 - Planning of Fixed Part of Mobile Network

MS0600 Lease Contract Signed 14 - Sign Lease Contract

MS0700 Build Permit Application Submitted

15 - Request for Building Permit

MS0800 Site Ready to Build 15 - Request for Building Permit

MS0900 Construction Started on Site 17 - Civil Works and Site Preparation

MS0950 Civil Works Completed 17 - Civil Works and Site Preparation

MS1000 Radio and Transmission Equipment Delivered to Site

17 - Civil Works and Site Preparation


RELEASED 03 ED

Mile Stone Mile Stone Name Relation to RNE process flow chart

MS1100 Radio Installation and Commissioning Complete

19 Installation 20 - Commissioning and Integration

MS1200 Transmission Installation and Commissioning Complete

19 Installation 20 - Commissioning and Integration

MS1300 Site Inspection Completed, Ready for Integration

20 - Commissioning and Integration

MS1400 Site Integrated 20 - Commissioning and Integration

MS1500 Site Acceptance Tests Complete

29 - Network Acceptance Test

MS1600 Preliminary Acceptance Test Complete


MS1700 Site Passing Commercial Traffic


MS1800 Fnal Acceptance Test Complete


MS9100 Site Rejected


RELEASED 03 ED

5 RNP PROCESS RELATED AIO SERVICE MODULES

A mobile radio network turnkey project consists of a huge number of single tasks. In this process description only the ones related to radio network planning are considered.

The Alcatel AIO service portfolio provides packages of different tasks (AIO modules) to simplify the offer process. To assist the offer department in selecting the proper AIO modules when preparing an offer for a turnkey project, in the following a mapping between the previous shown RNE tasks and the RNE AIO modules is given.

For information also tasks under responsibility of other teams than RNE are given and a mapping to AIO modules is done (only informative, no guarantee for correctness).

Latest information on AIO services can be found in [3] and [4].

The following table gives an overview, which RNP process step belongs to which AIO module. Those steps not handled by RNE are given in gray font.

Important Note: The given AIO modules are valid modules in the AIO Service Portfolio Release 7.1.

RNP Process step Part of RNE Related AIO Module

Nb. Name Responsible Name 0 Evaluating Customer

Requirements SAL/ND/RNE Preliminary Network Design plus

(module under responsibility of ND) 1 Preliminary Network

Design ND/RNE

Preliminary Network Design plus (module under responsibility of ND) RNP Tool Calibration premier

2 Project Setup & Management

PM/RNE/ND/TMP/SEN/ SAQ

RNE Project Management #1 Cell Planning plus

3 Initial Radio Design RNE RNE Project Management #1 Initial Radio Design plus (If applicable: Indoor Radio Design plus) RNP Tool Calibration premier (if not yet done)

4 Planning of fixed part of mobile network

TMP/RNE Preliminary Network Design plus Architect & Dimension premier

5 Delivery of site candidates SAQ External Acquisition Module 6 Find alternative site RNE Cell Planning plus 7 Check SAR RNE Cell Planning plus 8 Correct SAR RNE Cell Planning plus 9 Site Acceptance RNE/TMP Cell Planning plus 10 Site Ranking SAQ/SEN/

RNE/TMP Cell Planning plus External Acquisition Module

11 Start Site Contract Negotiation

SAQ External Acquisition Module

12 Final Site Survey SAQ/RNE/ TMP/SEN

RNE Part included in Cell Planning plus Survey premier

13 Creation of Site Layout Plan

SEN Prepare premier

14 Sign Site Contract SAQ External Acquisition Module 15 Request for Building

Permit SAQ External Acquisition Module


RELEASED 03 ED

RNP Process step Part of RNE Related AIO Module Nb. Name Responsible Name 16 Detailed Site Layout Plan SEN Prepare premier

Engineering premier #1 17 Civil Works and Site

Preparation SEN Install premier

18 Basic Software Production OFS/RNE Cell Planning plus Engineering premier #2

19 Installation OFS Install premier Cable premier

20 TOC Software Production RNE Frequency Planning plus 21 Commissioning and

Integration OFS Engineering premier #2

Activate premier 22 Call Test OFS Activate premier 23 TOC activation OFS Activate premier 24 Site Verification / Drivetest RNE Cell Planning plus

Air Measurement premier 25 Stability Test OFS Activate premier 26 HW/SW Problem

Detection OFS/RNE Cell Planning plus

Activate premier 27 Network Optimization RNE Air Measurement premier

Radio Tuning plus 28 Preparing Network

Acceptance RNE Air Measurement premier

Radio Tuning plus 29 Network Acceptance Test RNE -

30 Further Optimization RNE Network Parameter Tuning plus Radio Tuning plus Air Measurement premier End-User Quality Analyze premier

Out of the above mapping, the required AIO service modules performed by RNE during a turnkey project can be extracted:

Preliminary Network Design plus (if not done by ND before)

Architect & Dimension premier

RNE Project Management #1

Initial Radio Design plus

Cell Planning plus

Frequency Planning plus

Indoor Radio Design plus (optional, but usually not)

RNP Tool Calibration premier

Air Measurement premier

Network Parameter Tuning plus

Radio Tuning plus

End-User Quality Analyze premier


RELEASED 03 ED

APPENDIX A

Find below a table giving the form templates used during RNE projects and anticipation programs. It is distinguished between forms used in projects with site related project follow up tool

Table 2: Form templates to be used in RNE projects

Template Filename W Example coding scheme for sites Bts_code.doc SAM (Search Area Map) Defines the search area, optional candidates may be included

SAM.xls

SAR document SAR.xls SAR example SAR KW Greifenstein.xls SAR checklist SARcheck.xls Radio Initial Engineering Approval RIEA.xls X Radio Final Engineering Approval RFEA.xls X Transmission Initial Engineering Approval TIEA.xls X Transmission Final Engineering Approval TFEA.xls X Candidate Evaluation Report CER.doc Line of sight LOS.doc Technical Site Survey Report TSSR.doc TOC Activation Form TOC.doc X Standard Drivetest Report SDTR.doc KPI report KPIR.xls Site Status Report SSR_date.xls X

Note: Column W indicates the templates to be automatically created out of the project database.


RELEASED 03 ED

LIST OF ABBREVIATIONS

AIO All-In-One BoQ Bill of Quantity BCCH Broadcast Control Channel BSIC Base Station Identification Code BTS Base Transceiver Station CAE Customer Application Engineering CER Candidate Evaluation Report CI Cell Identifier EMC Electro Magnetic Compatibility FAT Final Acceptance Test FEA Final Engineering Approval GSM Global System for Mobile Communication HO Hand Over IEA Initial Engineering Approval KPI Key Performance Indicator LAC Location Area Code LL Leased Line LOS Line of Sight MLU Massive Logical Update MND Mobile Networks Division MPS Master Plan Schedule MS Mile Stone, Mobile Station (context dependent) MSC Mobile Switching Center ND Network Design NE Network Element Node B UMTS Base Station OFS Operations Field Service OMC-R Operation and Maintenance Center (for Radio) PAT Preliminary Acceptance Test PCS Professional Customer Services PDB Project Database PM Project Management PMP Program/Project Management Plan, Point to Multipoint PMS Project Management System PRC Provisioning Radio Configuration QoS Quality of Service RF Radio Frequency RFEA Radio Final Engineering Approval RIEA Radio Initial Engineering Approval RNC Radio Network Controller RNE Radio Network Engineering RNO Radio Network Optimization RNP Radio Network Planning RNS Radio Network Subsystem (equal to BSS in GSM) SAL Sales Department SAM Search Area Map SAR Site acquisition report


RELEASED 03 ED

SAQ Site Acquisition SEN Site Engineer TBD To be defined TFEA Transmission Final Engineering Approval TIEA Transmission Initial Engineering Approval TMP Transmission Planning TOC Turn on Cycle TSS Technical Site Survey TSSR Technical Site Survey Report UMTS Universal Mobile Telecommunication System WBS Work Breakdown Structure

END OF DOCUMENT

RNP_ProcDesc_ed03.pdf

Documents

Transcript of RNP_ProcDesc_ed03.pdf