RF Process

Work Package 1 - RF Engineering Process Description
RF Engineering Package for Bids, Proposals and Projects
Lucent Technologies
Bell Labs Innovations
Top level RF Engineering Process Description
December 1999 GSM RF Engineering AP and EMEA RF Engineering Groups
GPM.RFE.WP1.1V2.0
RF Engineering Platform Group Lucent Technologies Proprietary
Lucent Technologies
1. Introduction ______________________________________________________4
1.1 1.2 1.3 Purpose ___________________________________________________________ 4 Scope _____________________________________________________________ 4 References _________________________________________________________ 4
2. Work Packages____________________________________________________5
2.1 Work Package 1 - Comparative Analysis _______________________________ 5
Comparative Analysis ___________________________________________________5 Present Comparative Analysis to customer ___________________________________5 Discuss parameters and assumptions with customer ____________________________7 Discuss the RF Design Objectives and Assumptions with Customer ________________7 Database investigation ___________________________________________________8 RF Design Objectives____________________________________________________9 Coverage Area Visits / Analysis___________________________________________10 Link budget __________________________________________________________11 Estimation of the Cell Ranges ____________________________________________12 Traffic Study _________________________________________________________12 Estimation of the Number of Sites and Radios________________________________13 Install ASSET ________________________________________________________14 Primary CW Drive Tests ________________________________________________14 First ASSET Tune _____________________________________________________15 Build-up the Antenna Pattern Library ______________________________________15 Coverage area visits ____________________________________________________16 Proposal RF Design ____________________________________________________16 Proposal Frequency Plan ________________________________________________17 Proposal RF Report ____________________________________________________17 RF Engineering review of Proposal RF Design _______________________________18 RF Design Presentation _________________________________________________18 Evaluate RFQ/RFT_____________________________________________________19 Respond to RFQ/RFT __________________________________________________19 Respond to response clarifications _________________________________________20 Discuss the RF Network Performance Objectives with Customer _________________20 Discuss RF Optimisation Services with Customer _____________________________20 Revised Estimation of the Number of Sites and Radios _________________________20 Review pre-sales activities _______________________________________________20 Visit site locations _____________________________________________________22 Define search rings_____________________________________________________22 Assess candidate site ___________________________________________________23 RF Engineering Platform Group Lucent Technologies Proprietary 2 2.1.1 2.1.2
2.2
Work Package 2 ROM Site and Radio Estimate ________________________ 7
2.2.1 2.2.2 2.2.3 1.1.4 1.1.5 1.1.6 1.1.7 1.1.8 1.1.9
1.3
Work Package 3 - Initial ASSET Preparation __________________________ 14
1.3.1 1.3.2 1.1.3 1.1.4
1.4
Work Package 4 - RF Design Proposal ________________________________ 16
1.4.1 1.4.2 1.4.3 1.4.4 1.4.5 1.4.6
1.5
Work Package 5 - RFT/RFQ Response ________________________________ 19
1.5.1 1.5.2 1.5.3 1.5.4 1.5.5 1.5.6 1.5.7
1.6
Work Package 6 - RF Site Realisation _________________________________ 22
1.6.1 1.6.2 1.1.3
GPM.RFE.WP1.1V2.0
Lucent Technologies
1.1.4 Design Review Report __________________________________________________23 1.1.5 Internal Design Review _________________________________________________24 1.1.6 Survey sites (RF part)___________________________________________________24 1.1.7 Generate Site Survey Report _____________________________________________25 1.1.8 Repeat from Assess candidate site (Section 2.6.3) to Generate Site Survey Report (Section 2.6.7) for sites that either cannot be acquired or are unsuitable____________________25 1.1.9 Report and review progress ______________________________________________25
1.7
Work Package 7 - Final ASSET Preparation ___________________________ 26

Upgrade ASSET system_________________________________________________26 Secondary CW Drive Tests ______________________________________________26 Second ASSET Tune ___________________________________________________27 Neighbour lists ________________________________________________________28 Frequency plan ________________________________________________________28 Staged rollout _________________________________________________________28 RF Network Design internal review________________________________________29 RF Network Design customer review_______________________________________30 Preparation of RF OMC Defaults__________________________________________31 RF OMC Data Release__________________________________________________31 Task inputs ___________________________________________________________32 Task Description ______________________________________________________32 Deliverables __________________________________________________________32 Task inputs ___________________________________________________________33 Task Description ______________________________________________________33 Deliverables __________________________________________________________33 Task inputs ___________________________________________________________33 Task Description ______________________________________________________33 Deliverables __________________________________________________________34 Task inputs ___________________________________________________________34 Task Description ______________________________________________________34 Deliverables __________________________________________________________35
1.7.1 1.7.2 1.7.3
1.8
Work Package 8 RF Network Design Delivery ________________________ 28
1.8.1 1.8.2 1.8.3 1.8.4 1.8.5
1.9
Work Package 9 RF OMC Data Release ______________________________ 31
1.9.1 1.9.2 1.10.1 1.10.2 1.10.3 1.11.1 1.11.2 1.11.3 1.12.1 1.12.2 1.12.3 1.13.1 1.13.2 1.13.3
1.10 Work Package 10 Site Verification __________________________________ 32
1.11 Work Package 11 Initial Optimisation _______________________________ 33
1.12 Work Package 12 Primary Optimisation _____________________________ 33
1.13 Work Package 13 Network Verification ______________________________ 34
1.14 Ongoing Network Operation and Maintenance _________________________ 35
3. Document Control ________________________________________________36

3.1 3.2 3.3 Ownership and control information___________________________________ 36 Amendment History________________________________________________ 36 Document feedback form ___________________________________________ 38
GPM.RFE.WP1.1V2.0
Lucent Technologies
1. INTRODUCTION
1.1 PURPOSE
This document is a Process Description of RF Engineering services offered for all GSM projects. The complete RF Engineering process has been divided into 16 work packages. These can be grouped and packaged into separate RF Engineering Service Products. This document is a top level Process Description. The tasks of each work package form the subjects of lower level documents which provide more detailed Process Descriptions. This documents structure is used to derive the RF Engineering cost model structure.
1.2 SCOPE
This document will be used either for all new bids and proposals that require a quotation for RF Engineering services or projects where RF Engineering services will be delivered. RF Engineering is divided into RF Design and RF Optimisation. Generally, all activities carried out to support site construction are RF Design activities. Those carried out after site construction to support network operation and performance are RF Optimisation activities.
1.3 REFERENCES
Undefined DEM DTM GIS database RF Dimensioner tool RF Optimistation Process Description Digital Elevation Model. An electronic database of the elevation (terrain plus land use) of the earth surface Digital Terrain Model. An electronic database of the ground height of the earth surface. An electronic database comprised of a DTM/DEM, vector database and morphology database An Excel spreadsheet used to calculate the number of sites required to achieve a given service level in a defined coverage area to a defined coverage probability. Wireless Design Center Lucents Project Management Database
WDC CellTracker
GPM.RFE.WP1.1V2.0
Lucent Technologies
2. WORK PACKAGES
2.1 WORK PACKAGE 1 - COMPARATIVE ANALYSIS
2.1.1 COMPARATIVE ANALYSIS
2.1.1.1 Task Description
Comparative Analysis will either help an existing operator in building out their network or identify to a new operator where their network should be built. If appropriate the customer should be involved in all activities. Identify all networks that are competitors to the customer. In the case of GSM competitors obtain their SIMs; in the case of other technologies obtain service for the test equipment to be used. Design drive routes that take in the high density traffic areas of interest. Include any areas where the customer has no or poor service and the competitors have service. Perform the drive tests and analyse their results. Write a report on the results and have it reviewed by the Bid and Proposal team for inclusion in: the Comparative Analysis Presentation (section 2.1.2) Discuss parameters and assumptions with customer (section 2.2.1) Work Package 5 - RFT/RFQ Response (Section 2.5) the RF Design Presentation of Work Package 4 - RF Design Proposal (in section 2.4.6) and for passing to the customer as a stand-alone document. The report will confirm in format and content to the Optimisation Document Standard.
2.1.1.2 Deliverables
1. 2. 3. The report detailing the Comparative Test and its findings. A complete presentation in the form of view charts and presentation notes that can be given to the customer. Both report and presentation to include: All problems encountered in the customer network All areas where the customer has no service and a competitor does Recommendations for solving any coverage and quality problems
2.1.2 PRESENT COMPARATIVE ANALYSIS TO CUSTOMER

Present the results of the Comparative Analysis to the customer so that they understand the knowledge that Lucent has obtained and the strength of Lucents position in offering them RF Engineering services. This should be in the form of a presentation and a distributed report. Seek feedback from the customer about: the suitability of the design approach used so far and the assumptions used; the likelihood of being awarded parts or the whole of RF Engineering services in any contract; the level of RF Engineering knowledge and resources possessed by them. GPM.RFE.WP1.1V2.0 RF Engineering Platform Group Lucent Technologies Proprietary 5
Lucent Technologies
1. 2. 3. 4. Presentation and report on the results of the Comparative Analysis. Customer feedback on the analysis that can be used to align better the remainder of the RF Design with the Customers expectations and requirements. An indication of the likelihood of being asked for RF Engineering services in any contact. An assessment from the people attending the presentation of the level of RF Engineering knowledge and amount of RF resources possessed by the customer.
GPM.RFE.WP1.1V2.0
Lucent Technologies
2.2 WORK PACKAGE 2 ROM SITE AND RADIO ESTIMATE

2.2.1 DISCUSS PARAMETERS AND ASSUMPTIONS WITH CUSTOMER
Discuss the parameters that are used to obtain the site and radio estimate in section 2.2.9. Obtain agreement on their values.
2.2.2 DISCUSS THE RF DESIGN OBJECTIVES AND ASSUMPTIONS WITH CUSTOMER

2.2.2.1 Task inputs
Lucent-recommended values and the arguments used for adopting the values for all the issues shown below.

The following technical items will be addressed during the period of technical discussions: 1. Target coverage areas 2. Service types for the target coverage areas. These should be marked geographically in hardcopy maps and MapInfo electronic street maps. 3. Erlangs per subscriber in the busy hour 4. Quality of Services in terms of blocking rate in the air interface 5. Network Capacity and the growth plan 6. Available frequency resources and any frequency usage restrictions in particular areas. 7. Quality of Network (C/I values) and related network features (FH, DTX, DPC ) 8. Any limitations of the quantity of sites and radios. 9. Means and standard deviations of the penetration loss of buildings and cars, used in the link budget calculations described in the Link budget (Section 2.2.6) 10. Coverage probabilities in terms of percentage in the cell area, used for the link budget calculation in section Link budget (Section 2.2.6) 11. Antenna diversity gain, the achievable antenna diversity gain for different diversity schemes and propagation environments. 12. Lucents BTS hardware specification, the BTS sensitivity under different propagation profiles and hardware configurations. 13. Antennas to be used in the Design as described in the Build-up the Antenna Pattern Library section (2.3.4). 14. Limitations of the RF prediction tools 15. RF Site realisation process as described in Work Package 6 - RF Site Realisation (Section 2.6). 16. Site candidates assessment as described in Assess candidate site (Section 2.6.3). 17. Number or percentage of site candidates that will be assessed by using CW drive test as described in the Task Description of Assess candidate site (Section 2.6.3). 18. RF network design review process as described in the RF Network Design customer review (Section 2.8.5). 19. Site naming convention. 20. Agreements on using any sites that have already been acquired or are available by the customer. In case the customer has no RF staff with whom to discuss these technical items, a well documented RF design document with all the related RF design objectives, assumptions, definitions should be prepared, approved by the Lucent Technical Director and then proposed to the customer. GPM.RFE.WP1.1V2.0 RF Engineering Platform Group Lucent Technologies Proprietary 7
Lucent Technologies
The whole RF network will be realised by using these customer-approved technical objectives and assumptions. Any change in these items in the implementation stage will have serious impacts on the implementation schedule and additional project costs may occur.
A document that is signed by both parties to indicate agreement on the items listed above.
2.2.3 DATABASE INVESTIGATION

2.2.3.1 Task inputs
1. 2. A list of the coverage area elements identifying cities, towns, villages and roads for which cellular coverage is required. For each coverage area element a description of its size, either as an outline drawn on a map or area in km2.

Search the WDC web site at http://wdc-lib.wh.lucent.com/ for a suitable GIS database. Survey the resolution, format, availability and accuracy of the following products: 1. Demography (Population statistics, income and road traffic statistics) 2. Paper maps. Use two scales: 1:500,000 or better for the whole service area; and 1:25,000 or better with enough details for the population centres. 3. Topographic databases (containing morphology, terrain height and vector data) in MapInfo and ASSET format. 4. Electronic street maps in MapInfo format. These should show enough detail to enable a reader to identify roads, towns, prominent buildings, railway stations and other important features. Obtain quotations and delivery times for products 1-4 for the cities, towns, villages and roads for which cellular coverage is required.
Availability of the following database products: 1. Demography 2. Paper maps 3. GIS databases in MapInfo and ASSET format 4. Electronic street maps in MapInfo format. If these products are available from the WDC web site then the files could be located on a server in a remote country office. If that is the case then the deliverable is to ensure that the files do exist and to obtain a delivery period for them. If the files do not exist within Lucent then the deliverable is to get quotations and delivery times for them from the WDC web site by making a New Data Request.
GPM.RFE.WP1.1V2.0
Lucent Technologies
Wherever possible obtain samples of the database products and assess their cost and validate their format and content.
2.2.4 RF DESIGN OBJECTIVES

2.2.4.1 Task inputs
1. 2. List of coverage area elements from the Database investigation (Section 2.2.3) Cellular service types (as defined in the RF Engineering Glossary of Terms ) to be provided in each coverage area element 3. Blocking rate at the air interface 4. Expected busy hour load in Erlangs per subscriber 5. Expected number of cellular subscribers 6. Available GSM spectrum and a list of any other services sharing any part of the whole GSM spectrum (such as ETACS, microwave transmission links or paging) 7. Expected quality of network (C/I values) 8. Related network features (FH, DTX, DPC ) 9. Any limitations on the number of sites and radios 10. Customers site naming convention 11. Cost constraints

The RF Design objectives define the customers inputs for the duration of the RF Design process. They will be fully defined and documented to ensure clarity and consistency in the RF Design. These objectives may came from one of the following sources or processes: 1. The customer (most preferable) 2. The Comparative Analysis report produced in section 2.1. 3. Conversion from the customers more-general requirements 4. Preparation by Lucents own RF Engineering team and approval by the technical director of Lucent if there is no defined customer. These design objectives may be different for various land usage types. If possible, discuss with the customer and record the definitions and validation methods of these objectives. Propose and record electronically the geographical areas where the objectives will apply. The agreed-upon site naming convention should make it easy to identify candidate sites and design sites. It will either be identical to the convention used by CellTracker or not, in which case it will be related to the Site Database convention via a look-up table.
1. An RF Design Objectives document that: clearly identifies all the items listed in the Task inputs and their values contains maps that show the geographically extent of the coverage area and each service type A Site Naming Convention document describing the agreed-upon site naming convention. The validation methods for each service area element that will be used to ensure that the RF Design objectives have been met.
2. 3.
GPM.RFE.WP1.1V2.0
Lucent Technologies
All maps will be generated, stored and displayed in MapInfo format and use a scanned street directory of the coverage area as an underlay to aid in visualisation.
2.2.5 COVERAGE AREA VISITS / ANALYSIS

2.2.5.1 Task inputs
1. 2. 3. 4. Morphology part of the topographic databases from Database investigation (output of section 2.2.3). List of Coverage area elements from Database investigation (input to section 2.2.3). RF Design Objectives document from RF Design Objectives (output of section 2.2.4) Electronic street maps from Database investigation (output of section 2.2.3)

This task will involve either actual visits to the coverage area or a paper analysis of the coverage area. The decision which to carry out falls on the RF Engineering Manager. However, if this WP is being performed in isolation as part of a ROM exercise, then typically only a paper analysis will be carried out. If this WP is part of a larger program of work, that includes latter WPs such as Work Package 4 RF Design Proposal, then typically actual coverage visits will be carried out. If only a paper analysis is carried out here, and Work Package 4 - RF Design Proposal is carried out later, then an actual site visit will need to be carried out in task 1 (Coverage area visits) of Work Package 4 - RF Design Proposal.
COVERAGE AREA VISITS

Visit the areas proposed in the RF Design Objectives document to gain familiarity with them. Review, and revise if required, the coverage areas proposed in the RF Design Objectives document. All revisions should be stored electronically in the document. If the morphology database is already available and up-to-date, validate the accuracy of the morphology classes in the database with those visited. If the morphology database is not up-to-date check the boundaries of cities and any newly developed areas (such as new housing areas on the edges of towns, industrial areas that have been built on rural land etc). If any differences exist, get the database updated. If the morphology database is not available at this stage, as most likely will be the case, carry out subjective categorisation of land usage types. Mark the boundaries of each land use type on the electronic street maps. For compatibility with the RF Dimensioning tool use the following land use type definitions: 1. 2. 3. 4. 5. 6. dense urban urban suburban quasi open open highway
Estimate the antenna heights, within each land use area or morphology class, that in the opinion of the RF Engineer are achievable. Base this on the heights of existing masts, existing cellular antennas and buildings. Provide the information for each land use type or morphology class in MapInfo format. GPM.RFE.WP1.1V2.0 RF Engineering Platform Group Lucent Technologies Proprietary 10
Lucent Technologies
Estimate the Correction Factors (CFs) for each land use type or morphology class for the COST231/Okumura-Hata propagation model. See RF Dimensioner for the recommended values.
COVERAGE AREA ANALYSIS

From topographic maps and other information about the coverage area, estimate the geographical extent of the morphology classifications listed above. Examine the intersection of the coverage area with the morphology class areas and calculate the area of coverage for each morphology class area in km2.
A detailed report showing: 1. A Revised RF Design Objectives document containing any revisions to coverage areas. 2. Either: the validated or updated morphology database (if the database is available in this stage); or subjective categorisation of the coverage area into the morphology classes listed above (if the database is not available) 3. The estimated CF for each of these morphology classes or land use types defined in item 2 above. 4. A list of antenna heights for each morphology class or land use type. 5. A list of the population centres and roads with their coverage areas subdivided into the different morphology classes. The area of each subdivision in km2. This will be used to populate the Site worksheet of the RF Dimensioner tool. In order to maintain consistency, all morphology class or land use areas must be defined by short descriptions. Example photographs will also be provided if an actual coverage area visit has been undertaken.
2.2.6 LINK BUDGET

2.2.6.1 Task inputs
1. 2. 3. 4. 5. 6. 7. 8. RF Dimensioner tool Related network features (input to section 2.2.4) In-car penetration loss and probability In-building penetration loss(es) and probabilities BS equipment parameters (RX sensitivity, TX maximum transmit power etc) Antenna types (Beamwidth, gain, polarisation etc) Diversity schemes (horizontal space, cross-polar etc) Coverage probabilities for each type of coverage and service type defined in the RF Design Objectives document (output of section 2.2.4) 9. CFs for each morphology class (output of section 2.2.5) 10. GSM specification 05.05

Ensure that the probabilities of the penetration losses in task inputs 3 and 4 correspond to the probabilities of task input 1. Using the RF Dimensioner Tool, calculate balanced link budgets for the up-link and down-link paths for each 1. Morphology area
GPM.RFE.WP1.1V2.0
11
Lucent Technologies
2. 3.
Service type GSM channel model (see annex C.3 of GSM specification 05.05)
Calculate the powers (in dBm) required at the input to the antenna to achieve the signal levels shown in each link budget.
1. 2. 3. Comprehensive link budgets Transmit powers An RF Dimensioner tool with link budget information completed.
2.2.7 ESTIMATION OF THE CELL RANGES

2.2.7.1 Task inputs
1. 2. Maximum path losses from each Link budget (Deliverable 3 of section 2.2.6) Revised RF Design Objectives document (output of section 2.2.4)

Define one cell type for each Link budget. Use the Link Budgets and CFs to calculate the cell range for each cell type. The cell ranges will be used to estimate the number of cells required in section 2.2.7 (Estimation of the Cell Ranges). Estimate the variances in each cell range caused by errors in subjective classification or morphology classification in task input 3.
1. An RF Dimensioner tool showing all cell ranges for all morphology types specified in section 2.2.5.2.
2.2.8 TRAFFIC STUDY

2.2.8.1 Task inputs
1. 2. 3. 4. 5. 6. Any traffic data from Work Package 1 - Comparative Analysis (Section 2.1) The expected growth of the subscriber base Measured traffic statistics if available The Blocking rate at the air interface, expected busy hour load in Erlangs per subscriber and expected number of cellular subscribers Population statistics (one part of the demography output of section 2.2.3) Either morphology classes or subjective land use types from section 2.2.5 (Coverage Area Visits)

Use the task inputs to create a model of the traffic in the network. Estimate the traffic in Erlangs/km2 for each morphology class or land use type. This information will be used by ASSET in planning radio GPM.RFE.WP1.1V2.0 RF Engineering Platform Group Lucent Technologies Proprietary 12
Lucent Technologies
resources. Include any traffic information obtained from Work Package 1 - Comparative Analysis (Section 2.1). Use the model to estimate the network load in E/km2 for each morphology class or land use type at network turn-on and at defined points in its growth. This information will be provided in a table and, if possible, in a MapInfo map.
1. An estimate of the network load at turn-on and at defined points in its growth.
2.2.9 ESTIMATION OF THE NUMBER OF SITES AND RADIOS

2.2.9.1 Task inputs
1. 2. 3. 4. Link budgets (output of section 2.2.6) Cell ranges (output of section 2.2.7) Traffic Load Study (output of section 2.2.8) RF Dimensioner tool (Deliverable of section 2.2.7.3)

Enter the information from the Traffic Study (section 2.2.8) into the RF Dimensioner tool from the Link budget (section 2.2.6) Estimate the total number of sites and radios required to provide the appropriate level of service to the coverage areas. Calculate the variance in the site and radio numbers caused by the variances in the cell ranges. Review these estimates by the RF Manager and the RF Team and then deliver them to the marketing and sales team for project pricing and Network Dimensioning team for transmission & BSC/MSC dimensioning. These results may be adjusted when the Proposal RF Design is made in Work Package 4 - RF Design Proposal in section 2.4.
A document set containing: 1. Tabular lists of the number of sites in each morphology area or land use type and the number of radios for each cell, at all subscriber growth points in the network 2. The variances in site and radio count and caused by cell range variances. 3. All the assumptions used in the estimates, such as traffic data and link budgets.
GPM.RFE.WP1.1V2.0
13
Lucent Technologies
2.3 WORK PACKAGE 3 - INITIAL ASSET PREPARATION

2.3.1 INSTALL ASSET
2.3.1.1 Task inputs
1. 2. 3. 4. 5. 6. Site and radio estimate document from Estimation of the Number of Sites and Radios (output of section 2.2.9) Topographic database availability from Database investigation (output of section 2.2.3) A Windows NT server computer if a client-server architecture is required LAN facilities Peripherals (A4, A3 and A0 plotters. A4 printers) Windows NT laptops and PCs as required.
All computers will comply with the minimum specifications as defined on the RF Engineering web site at: http://rfwww.de.lucent.com/

Install ASSET on the server that is correctly dimensioned to the expected network size and areas as defined in Task inputs 1 and 2 above. Acquire and install the topographic database on the machine(s). Connect the machine to a LAN so that graphics and text can be printed on networked plotters and printers and remote maintenance can be carried out from the Lucent office in Nuernberg, Germany.
1. 2. A fully operational and networked server with ASSET, topographic and vector databases installed so that graphical and textual information can be plotted and remote maintenance can be carried out. A network of laptops and PCs that can use ASSET as remote clients of the server.
2.3.2 PRIMARY CW DRIVE TESTS

2.3.2.1 Task inputs
1. 2. Morphology database from Database investigation (output of section 2.2.3) or the subjective land use classifications if the morphology database is not available. CW measurement test equipment.

The purpose of this task is to collect sufficient measurement points to tune ASSET. Based on the morphology database choose 3 to 5 test locations for each morphology class. The test locations should not be blocked in any direction, otherwise a rental crane should be used to raise the test transmitter and antenna to the expected antenna height.
GPM.RFE.WP1.1V2.0
14
Lucent Technologies
The test locations should located within the morphology class under test and the drive routes should be all within the morphology class. The collected data should be displayed and screened in MapInfo to ensure the data is collected within the morphology class under test. The screened and processed data will be converted into the ASSET format then imported and processed in the measurement function part of ASSET.
The RF Engineering Report for CW Drive Test will be prepared, it includes the following items: 1. MapInfo plots with morphology class boundaries, test locations, drive routes and the measured signal strengths. 2. Test configuration tables for details of the instrumentation used in these tests. 3. All drive tests represented in electronic format suitable for importing into ASSET.
2.3.3 FIRST ASSET TUNE

2.3.3.1 Task inputs
1. 2. 3. The RF Engineering Report for CW Drive Test report from Primary CW Drive Tests (Section 2.3.2). Electronic drive test results Morphology database from Database investigation (output of section 2.2.3).

Tune the propagation parameters of the morphology classes used in ASSET according to the ASSET user manual on http://rfwww.de.lucent.com/
1. A version of ASSET that has been tuned against all measurement data collected to date and is the best-tuned model available.
2.3.4 BUILD-UP THE ANTENNA PATTERN LIBRARY

2.3.4.1 Task inputs
1. 2. Antenna libraries used in previous projects. New antennas expected to be used in this project

The accuracy of the radio network design tools depends heavily on the tuning of the propagation model and the correctness of the antenna patterns. The preferred antenna vendors and suitable antenna types from each vendor should be listed and the following information should be acquired from the antenna vendor: 1. 2. Both the technical and mechanical specification. The simulated or measured radiation pattern data in numerical table lists format. RF Engineering Platform Group Lucent Technologies Proprietary 15
GPM.RFE.WP1.1V2.0
Lucent Technologies
3.
The vendor should also provide the simulated or measured impact of the radiation pattern caused by the mounting structures if available.
Based on the information listed above, antenna pattern data should be prepared in ASSET.
1. 2. A ASSET version with the radiation pattern data for the antennas. An Antenna Usage Guideline document with lists of the antenna types, mechanical specifications, technical specifications, radiation patterns and cautions to RF engineers. The document will be both in electrical and hardcopy formats. One copy of the document in item 2 to each RF Engineer working on the project.
3.
2.4 WORK PACKAGE 4 - RF DESIGN PROPOSAL

2.4.1 COVERAGE AREA VISITS
2.4.1.1 Task inputs
The same inputs as in the Coverage Area Visits / Analysis task of Work Package 2 ROM Site and Radio Estimate (Section 2.2.5)

If no coverage area visits were performed in Work Package 2 ROM Site and Radio Estimate, then carry them out here.
The same deliverables as in the Coverage Area Visits / Analysis task of Work Package 2 ROM Site and Radio Estimate (Section 2.2.5)
2.4.2 PROPOSAL RF DESIGN

2.4.2.1 Task inputs
1. All design information collected to date.

The proposal RF design is high-level design documentation set that is aimed to propose a RF network design to the customer that meets the RF objectives, capacity requirements and the cost constrains as described in the RF Design Objectives (section 2.2.4) and Coverage Area Visits (section 2.2.5). Enter all sites into ASSET and calculate all coverage plots for each site and city. Collect the assumptions and parameters used in the design to date.
The following information: 1. RF network architecture
GPM.RFE.WP1.1V2.0
16
Lucent Technologies
2. 3. 4. 5. 6. 7. 8. 9. 10. 11.
RF network design objectives and propagation environments as described in Database investigation (section 2.2.3.1). Link budget calculations as described in the Link budget section (2.2.6). Estimation of cell ranges in each layer, land usage type and service types as described in the Estimation of the Cell Ranges (Section 2.2.7). RF network capacity and growth plan as described in the Traffic Study (Section 2.2.8). The estimated number of sites, radio and uncertainties as described in the Estimation of the Number of Sites and Radios (Section 2.2.9) Network features (FH, DTX and DPC ) Coverage plots prepared by ASSET Site distribution plots overlaid with scanned street maps prepared by using MapInfo Estimated RF engineering working hours An installation of ASSET in which the proposed network has been entered and all coverage generated.
2.4.3 PROPOSAL FREQUENCY PLAN

2.4.3.1 Task inputs
1. 2. All design information collected to date. Deliverable 11 of previous task Proposal RF Design

Use the ILSA planning tool within ASSET to generate a proposal frequency plan based on the proposal design. Save and print the output in a format that is suitable for inclusion in the proposal document. No manual frequency planning is required at this stage as the design is a proposal only and will change when realistic sites locations are found. However, the plan will be checked for errors and omissions.
1. 2. A proposal frequency plan that has been optimised by ASSET ILSA and has been sanity-checked by RF Engineering. A file and printout showing the channel allocations.
2.4.4 PROPOSAL RF REPORT

2.4.4.1 Task inputs
1. 2. 3. All design information collected to date. The RF Cost model tool The frequency plan from deliverable 1 in the Proposal Frequency Plan task

The proposal RF design is high-level design documentation set that is aimed to propose a RF network design to the customer that meets the RF objectives, capacity requirements and the cost constrains as described in the RF Design Objectives (section 2.2.4) and Coverage Area Visits (section 2.2.5 or 2.4.1). All design data collected to date will be collected and re-organised into the proposal RF design documentation set.
GPM.RFE.WP1.1V2.0
17
Lucent Technologies
The RF network design proposal with items listed bellow in both report and presentation formats will be prepared. The RF design proposal document will include but not limited to the following information: 12. 13. 14. 15. 16. 17. 18. 19. 20. 21. 22. 23. 24. RF network architecture RF network design objectives and propagation environments as described in Database investigation (section 2.2.3.1). Link budget calculations as described in the Link budget section (2.2.6). Estimation of cell ranges in each layer, land usage type and service types as described in the Estimation of the Cell Ranges (Section 2.2.7). RF network capacity and growth plan as described in the Traffic Study (Section 2.2.8). The estimated number of sites, radio and uncertainties as described in the Estimation of the Number of Sites and Radios (Section 2.2.9) Frequency plan strategy Network features (FH, DTX and DPC ) Coverage plots prepared by ASSET Site distribution plots overlaid with scanned street maps prepared by using MapInfo The expected RF network performance objectives (call success rate, drop call rate, handover success rate etc.) Competitive Analysis if it has been carried out Estimated RF engineering working hours
2.4.5 RF ENGINEERING REVIEW OF PROPOSAL RF DESIGN

2.4.5.1 Task inputs
The Proposal Document from Proposal RF Report (section 2.4.4).

The proposal document will be internally reviewed by the RF team and approved by the Lucent technical director. It will also be reviewed separately and discussed jointly by the Marking teams, Project Management teams other technical teams before it is presented to the customer.
A Proposal RF Design documentation set that has been explained to the Sales and Marketing teams and Technical Management and meets with their approval.
2.4.6 RF DESIGN PRESENTATION

2.4.6.1 Task inputs
The Proposal RF Design.
GPM.RFE.WP1.1V2.0
18
Lucent Technologies

Give a presentation to the customer using the RF design proposal documentation set prepared in the Proposal RF Report (Section 2.4.4) and approved in the RF Engineering review of Proposal RF Design section (2.4.5). The available RF services include the optimisation services should also be presented.
A complete presentation after which the customer will understand the 1. RF Engineering Capabilities on offer, including RF Optimisation Services; 2. Designed RF network architecture; 3. Differences in performance between the Customer network and that of their competitors if that has been carried out; 4. Design parameters and assumptions made in the proposal RF Design; 5. Planned services types and coverage areas; 6. Available network features and related performance improvement; 7. Capacity growth plan; 8. Estimated number of sites and radios; 9. Expected project costs and duration
2.5 WORK PACKAGE 5 - RFT/RFQ RESPONSE

2.5.1 EVALUATE RFQ/RFT
2.5.1.1 Task inputs
1. 2. 3. Electronic copy of the RFQ/RFT document. Deadlines for response Names of Business Development, Project Management and Sales staff responsible for the customer and project

Examine the RFQ/RFT issued by the customer, identify all points and issues requiring an RF Engineering input and assign resources required to answer them.
A list of the issues and points requiring RF Engineering input and a list of the resources required to address them and their deadlines.
2.5.2 RESPOND TO RFQ/RFT

2.5.2.1 Prepare RFQ/RFT response
Use the resources assigned in the Evaluate RFQ/RFT section (2.5.1) to prepare the RFQ/RFT response.
2.5.2.2 Review RFQ/RFT response

Review the contents with the Sales and Business Development teams.
GPM.RFE.WP1.1V2.0
19
Lucent Technologies
2.5.2.3 Submit RFT/RFQ response

A point by point response to the RFQ/RFT together with a proposal RF Design to the standard delivered in the Proposal RF Report (Section 2.4.4).
2.5.3 RESPOND TO RESPONSE CLARIFICATIONS

Receive Customer questions and provide clarifications.
2.5.4 DISCUSS THE RF NETWORK PERFORMANCE OBJECTIVES WITH CUSTOMER

2.5.4.1 Task inputs
Default network performance objectives. (To be developed by RF Optimisation)

Discuss the methods to be used to measure and demonstrate acceptable network performance once the network has been built and optimised. (To be further developed by RF Optimisation)
Agreed-upon network performance objectives and techniques for measuring them.
2.5.5 DISCUSS RF OPTIMISATION SERVICES WITH CUSTOMER

(To be developed by RF Optimisation)
2.5.6 REVISED ESTIMATION OF THE NUMBER OF SITES AND RADIOS

Rework the RF Design to the level of detail described in the Proposal RF Design (Section 2.4) accounting for any affecting changes to the agreed-upon parameters and assumptions in Discuss parameters and assumptions with customer (section 2.2.1).
A reworked RF Design based on parameters and assumptions proposed by the RF Design team in Work Package 4 - RF Design Proposal (Section 2.4) and negotiated and agreed with the customer in the RF Design Presentation (section 2.4.6) and any other technical discussions.
2.5.7 REVIEW PRE-SALES ACTIVITIES

2.5.7.1 Task inputs
1. 2. Confirmation of an LOI. RF Engineering portion of RFQ response.

When an LOI has been issued, review the work that has been carried out. Perform a red line review of the RF proposal. This is a technical critical review carried out by the GSM team in Swindon whose members have not been involved in the proposal design. GPM.RFE.WP1.1V2.0 RF Engineering Platform Group Lucent Technologies Proprietary 20
Lucent Technologies
1. 2. A list of items where improvements can be made in future RFQ responses. An RF Proposal that has been successfully reviewed by the red line review team.
GPM.RFE.WP1.1V2.0
21
Lucent Technologies
2.6 WORK PACKAGE 6 - RF SITE REALISATION

Based on the results carried out in Work Package 4 - RF Design Proposal (Section 2.4), the RF site realisation will proceed. In this WP, RF Engineering services will work with inter-disciplinary teams to build and integrate new sites.
2.6.1 VISIT SITE LOCATIONS

2.6.1.1 Task inputs
1. 2. 3. RF Design proposal from Work Package 4 - RF Design Proposal (section 2.4) with any amendments after Revised Estimation of the Number of Sites and Radios (section 2.5.6). Electronic street maps from Work Package 3 - Initial ASSET Preparation (section 2.3) Site survey kits.

Visit the site locations defined in Work Package 4 - RF Design Proposal (Section 2.4), and identify potential candidates. Take photographs of the candidates from street level. Move site locations away from hard-to-acquire areas if required.
A completed Site Location Visit Report (SLVR) containing: 1. Photographs showing potential sites at street level. 2. Map showing locations of potential candidates. 3. Revised locations of sites as placed in the Proposal RF Design (section 2.4.2).
2.6.2 DEFINE SEARCH RINGS

2.6.2.1 Task inputs
1. 2. RF Design proposal from Work Package 4 - RF Design Proposal (section 2.4) with any amendments after Revised Estimation of the Number of Sites and Radios (section 2.5.6). Electronic street maps from Work Package 3 - Initial ASSET Preparation (section 2.3)

Using site locations from the Visit site locations task (section 2.6.1) plot search rings to identify the area within which a search will be carried out for candidates. The search rings will be generated and stored electronically in MapInfo as vectors on a street directory underlay. There will be one search ring per site and it will include the structure height required. If the RF Engineer has identified sites that would make suitable candidates they will list the proposed candidate sites.
For each site one Search Ring Report (SRR) that includes: 1. A map of the area to be searched indicating the boundary within which the search is to be restricted; 2. An indication of the antenna height required; 3. Any photographs of the site area taken during the Visit site locations (2.6.1) and Coverage Area Visits (2.2.5) sections.
GPM.RFE.WP1.1V2.0
22
Lucent Technologies
4.
A list of proposed candidate sites if available.
2.6.3 ASSESS CANDIDATE SITE

2.6.3.1 Task inputs
1. 2. Candidate reports from Site Acquisition ASSET installation from Work Package 3 - Initial ASSET Preparation (section 2.3)

Take the candidate sites identified in the Visit site locations section (2.6.1) and assess their suitability in satisfying the coverage requirements of the site. Reject any that are unsuitable. Visit the location of each design site, access each candidate site and assess its suitability in satisfying the coverage objective. If the candidate site is an existing structure then climb it to the proposed antenna height. If the candidate site is a new structure then use other means to assess it, such as previous photographs or a crane elevated to the proposed antenna height. Perform CW drive tests to evaluate the suitability of candidates for the conditions listed bellow: 1. The antennas will be blocked in a particular orientation caused by the surrounding buildings. 2. The antenna mounting locations are non-optimum. Building structure limitations, rental issues or isolation concerns for co-located sites may cause this. 3. The candidate sites are located within areas with severe terrain variations and the available resolution of the terrain database is not enough to depict the RF signal strength accurately. Please note that the total number of CW tests will not exceed the numbers agreed with the customer in the Discuss the RF Network Performance Objectives with Customer section (2.5.4)
A Candidate Assessment Report (CAR) containing a list of all candidate sites in order of suitability. Include the mounting structure height required to satisfy the RF objective of the site.
2.6.4 DESIGN REVIEW REPORT

2.6.4.1 Task inputs
1. 2. 3. 4. The CAR for the site. Electronic street maps from Work Package 3 - Initial ASSET Preparation (section 2.3) Coverage plots for the preferred candidate site Local traffic information.

In order to review the RF Design of each site a Site Design Review Report (SDRR) will be prepared and completed once the RF Engineer has assessed all candidate sites and identified one that will satisfy the coverage objective. This report should address all aspects of the RF Design and give reasons for the sites existence including: 1. Predicted data available; 2. Traffic distribution calculations;
GPM.RFE.WP1.1V2.0
23
Lucent Technologies
3.
Analysis of all candidates for the search ring with regard to all RF Design issues, acquisition difficulty, ability to build, site maintainability and transmission;
One SDRR for each site designed. The report will be suitable for justifying that site at an internal review by peers and superiors and using as a technical source for the Site Design Package (SDP).
2.6.5 INTERNAL DESIGN REVIEW

2.6.5.1 Inputs
The SDRR for each site.

Conduct a design review of each site based on the contents of the SDRR. This review will be carried out by the following staff: 1. Site RF Engineer, 2. RF Design Manager or their appointee, 3. Customer RF Engineer(s) (only if the customer is being provided with training), 4. Junior RF Engineer (only required for internal training purposes), 5. Peer-level RF Design Engineers (at least one required per review)
The Internal Design Review will provide the following: 1. Training for Junior RF Engineers and customer RF Engineers if required; 2. A site design that has undergone critical review by peers and superiors; 3. Either an acceptance or a rejection of the site under review. In the case of rejection then the staff attending the review will include their reasons and suggested remedial action in the appropriate section of the SDRR.
2.6.6 SURVEY SITES (RF PART)

2.6.6.1 Task inputs
The SDRR for each site.

Attend the site and survey its location for antenna locations and orientations and other RF Design issues that will be required to complete the RF Design of the site. Other staff will attend the survey from the customer, site owner and Lucent. This is probably the last time that RF Engineering will attend the site before its civil and structural design therefore it is important that all information affecting the location and effectiveness of RF Engineering components is noted for latter definition.
All information to generate the documentation in the Generate Site Survey Report section (2.6.7).
GPM.RFE.WP1.1V2.0
24
Lucent Technologies
2.6.7 GENERATE SITE SURVEY REPORT

2.6.7.1 Task inputs
1. 2. All sketches and information gathered at the site survey activity in section 2.6.6. Coverage plots for the preferred candidate.

Using the information gathered during the Survey sites (RF part) task in section 2.6.6, complete the Site Survey Report (SSR) and ensure that all factors that affect the RF Engineering performance of the site have been specified and defined. Although the site survey is carried out by a number of different cellular disciplines the activity is owned by RF Engineering. It is their responsibility to ensure that all information has been collected and that the report is correct in all aspects.
A Site Survey Report showing: 1. Photographs of the views from the site in the directions of the eight points of the compass. 2. The height of the mounting structure above ground level in metres 3. Proposed locations and orientations of cellular antennas 4. Proposed type of cellular antennas 5. All civil works drawings to the standard required by the local construction and implementation organisation for construction to proceed.
2.6.8 REPEAT FROM ASSESS CANDIDATE SITE (SECTION 2.6.3) TO GENERATE SITE SURVEY REPORT (SECTION 2.6.7) FOR SITES THAT EITHER CANNOT BE ACQUIRED OR
ARE UNSUITABLE
2.6.8.1 Task inputs

No specific inputs required.

While carrying out the tasks between sections Assess candidate site (2.6.3) and Generate Site Survey Report (2.6.7) some sites will be rejected for any one of a number of RF, civil, equipment or acquisition reasons. At those sites it will be necessary to repeat these tasks. This will be accounted for by assuming a proportion of the sites estimated in the Bid and Proposal phase will be rejected.
All documentation and deliverables as described in sections Assess candidate site (2.6.3) to Generate Site Survey Report (2.6.7) for sites that have been rejected after the activities of task Assess candidate site (Section 2.6.3) and subsequent tasks have been started.
2.6.9 REPORT AND REVIEW PROGRESS

2.6.9.1 Task inputs
No specific inputs required. GPM.RFE.WP1.1V2.0 RF Engineering Platform Group Lucent Technologies Proprietary 25
Lucent Technologies

At the rates agreed upon in Discuss the RF Network Performance Objectives with Customer (section 2.5.4) carry out meetings and generate reports for the duration of the project.
At all meetings minutes will be taken and distributed by administrative staff. Two working days will be given for the customer to approve the minutes after which time approval will be assumed unless the customer indicates otherwise. Approved minutes will be used as working instructions for the RF Engineering part of the project.
2.7 WORK PACKAGE 7 - FINAL ASSET PREPARATION

2.7.1 UPGRADE ASSET SYSTEM
2.7.1.1 Task Inputs
1. 2. 3. 4. Indication of the location(s) and city(-ies) in which the RF Design will be carried out. Site and radio count from the Revised Estimation of the Number of Sites and Radios (Section 2.5.6) Signed document from section 2.2.2 (Discuss the RF Design Objectives and Assumptions with Customer) Estimate of the project duration

Upgrade the ASSET computer, topographic databases and software installed in Work Package 3 Initial ASSET Preparation (Section 2.3) to enable full post-contract RF Design to be carried out. This will involve performing the following tasks: Upgrading topographic databases; Upgrading any laptop computers used so far to more powerful server or workstation machines; Upgrading operating system and planning tool licenses to cater for the expected number of users; Acquiring sufficient laptop computers for all expected RF Engineers to operate the planning tool software; Upgrading graphics packages and database licenses.
A fully functioning planning tool and graphics software system, with regard to hardware capacity, software versions and operating system capacity, that is capable of performing RF Design to the completion of the project and is correctly dimensioned to complete the project on time.
2.7.2 SECONDARY CW DRIVE TESTS

2.7.2.1 Task inputs
1. 2. 3. Updated or existing morphology database from Upgrade ASSET system (section 2.7.1) CW measurement test equipment. A list of the sites that were tested in the Primary CW Drive Tests (section 2.3.2)
GPM.RFE.WP1.1V2.0
26
Lucent Technologies

In the ASSET system upgrade process described in Upgrade ASSET system (section 2.7.1), if the morphology data has been changed or upgraded, the suitability of the propagation parameters used in ASSET must be carefully investigated. The previous collected data in the Primary CW Drive Tests (Section 2.3.2) should be reviewed again. If the collected data is still useful, re-screen them based on the updated morphology database and determine the required propagation parameters for each morphology types. The results should be carefully analysed and compared with the results in the Primary CW Drive Tests. If the comparison shows any difference, a second ASSET tune described in the Second ASSET Tune (Section 2.7.3) should be conducted. If the previous collected data is not suitable for tuning the updated morphology database, additional drive tests should be conducted.
1. 2. A revised version of the RF Engineering Report for CW Drive Test prepared in the Primary CW Drive Tests (Section 2.3.2). New drive test data files.
2.7.3 SECOND ASSET TUNE

2.7.3.1 Task inputs
1. 2. 3. 4. Revised version of the RF Engineering Report for CW Drive Test from Secondary CW Drive Tests (Section 2.7.2) Updated morphology database from Upgrade ASSET system (output of section 2.7.1). All deliverables of Primary CW Drive Tests (Section 2.3.2) New drive test data files from Secondary CW Drive Tests.

Tune the propagation parameters of the morphology classes used in ASSET according to the ASSET user manual on http://rfwww.de.lucent.com/ Compare data collected and analysis results in the Primary CW Drive Tests (Section 2.3.2) and Secondary CW Drive Tests (Section 2.7.2). If the comparison shows any difference, the planning tool should be re-tuned according to the standard Process defined in the RF Engineering Standard Process for Propagation Model Tuning.
1. 2. A version of ASSET that has been tuned against all measurement data collected to date and is the best-tuned model available. The revised version of the RF Engineering Report for Propagation Model Tuning prepared in First ASSET Tune will be issued.
GPM.RFE.WP1.1V2.0
27
Lucent Technologies
2.8 WORK PACKAGE 8 RF NETWORK DESIGN DELIVERY

2.8.1 NEIGHBOUR LISTS
2.8.1.1 Task inputs
1. 2. 3. Design review reports for each site in the vicinity of the site whose neighbour lists are to be generated (from the Design Review Report task in section 2.6.4) ASSET site and network coverage and interference plots. The network implementation in ASSET

Use ASSET to generate neighbour lists for each cell in the network. Using network knowledge, such as the expected size of the neighbour list for the given site density, review and alter the lists.
Reviewed neighbour lists for all cells in the network.
2.8.2 FREQUENCY PLAN

2.8.2.1 Task inputs
1. 2. 3. The network neighbour lists generated above. The network implementation in ASSET The spectrum available

Use the ILSA or ComOpt modules in ASSET to generate a frequency plan for each region or city in the network. Ensure each plan is reviewed and inappropriate allocations corrected. The frequency plan will assume the following: 1. All sites will be integrated in one pass 2. There will be no re-tuning required (ie there are no existing sites) 3. No auditing is required (ie the ASSET database is correct and there are no existing sites)
An Excel sheet that shows the frequency plan for each region and city in the network design, which assumes all sites are integrated.
2.8.3 STAGED ROLLOUT

2.8.3.1 Task inputs
1. 2. 3. 4. The agreed-upon number of sites in each rollout phase. ASSET site and network coverage and interference plots. Design review reports for each site in the vicinity of the sites which are to be integrated into the network (from the Design Review Report task in section 2.6.4) The latest site integration schedule. RF Engineering Platform Group Lucent Technologies Proprietary 28
GPM.RFE.WP1.1V2.0
Lucent Technologies

The Proposal RF Design described above is the final view of the RF network. It assumes one OMC data release will be generated and that it will either be downloaded in parts during the network implementation or in whole when all sites have been integrated. In practise, during the implementation phase, sites will be leased and integrated in an almost random manner. It is very likely that the sites in some areas will not all be ready at the same time. However, the customer will require service as soon as possible. In order to provide the best service with the limited number of sites available, a staged rollout will be required. As new sites are integrated they will be held in a staging bin. When the number of sites in this bin reaches the agreed-upon staging bin size then a phased rollout will be performed for all sites in the staging bin and those sites removed from the staging bin. At each stage of this rollout the following will be produced for the sites already integrated and for those that will be integrated: 1. Interim frequency plan, neighbour lists and other RF OMC data set to avoid call drops caused by missing neighbours. Details for the RF OMC data release will be discussed in Work Package 9 RF OMC Data Release (section 2.9). 2. Support for the RF Optimisation team to reach the optimum interim performance as described and quantified in Work Package 11 in section 2.11. Note that staged rollout includes no hardware changes or rigging work; all interim settings will be software-related OMC changes.
For each stage the following will be provided: 1. Interim neighbour lists and frequency plan 2. Interim Best server plots 3. Interim RF OMC data release
2.8.4 RF NETWORK DESIGN INTERNAL REVIEW

2.8.4.1 Task inputs
1. 2. 3. 4. 5. The implementation schedule The Proposal RF Report (section 2.4.4) after the RF Engineering review of Proposal RF Design (Section 2.4.5) Site Survey reports for each sits Neighbour lists and frequency plans Coverage and interference plots for the complete network.

Review the final RF Design by the Technical and the Sales and Marketing teams separately to: 1. assess the conformity of the design against the design parameters discussed and agreed Discuss the RF Design Objectives and Assumptions with Customer (Section 2.2.2); 2. estimate the extent of any up-scope; 3. discuss any last-minute changes to the design.
GPM.RFE.WP1.1V2.0
29
Lucent Technologies
The review teams will include: 1. All RF Engineering team members responsible for the design; 2. The RF Engineering Manager; 3. The technical director responsible for the market within which the customer falls; 4. Sales and Marketing team members.
An RF Design that satisfies Engineering, Technical Management, Sales and Marketing requirements.
2.8.5 RF NETWORK DESIGN CUSTOMER REVIEW

2.8.5.1 Task inputs
1. 2. 3. 4. 5. The implementation schedule The Proposal RF Report (section 2.4.4) after the RF Engineering review of Proposal RF Design (Section 2.4.5) Site Survey reports for each sits Neighbour lists and frequency plans Coverage and interference plots for the complete network.

Upon completion of the RF Network Design internal review (Section 2.8.4) issue a complete report to the customer. This will be the same in content as the reports in the Proposal RF Report (section 2.4.4) and RF Design Presentation (Section 2.4.6) and will be given as a presentation and a written report. The customer will be able to review the RF Design, become familiar with it ask questions about it. The review team will include: 1. All RF Engineering team members responsible for the design; 2. The RF Engineering Manager; 3. The Technical director responsible for the market within which the customer falls; 4. Sales and Marketing team members; 5. Customer staff, preferably including RF Engineering staff. Allow the customer to review and comment on the report. At this stage the design is very mature and the customer has had frequent visibility and input to it. So any changes proposed by the customer should be very carefully assessed. Changes at this stage will very likely result in costly and timeconsuming workarounds. Owing to the large review team required it may be necessary to divide parts of the review into regions and have the staff responsible for designing the sites in that region attend that part of the review.
1. 2. 3. A report and presentation that summarises the completed RF Design to the same level of detail as in the Proposal RF Report (section 2.4.4) and RF Design Presentation (Section 2.4.6). An RF Design that has been reviewed by the customer and is acceptable to them. An acceptance form that has been signed by all the parties attending the review.
GPM.RFE.WP1.1V2.0
30
Lucent Technologies
2.9 WORK PACKAGE 9 RF OMC DATA RELEASE

2.9.1 PREPARATION OF RF OMC DEFAULTS
2.9.1.1 Task inputs
1. 2. The Lucent Technologies PARCAT database. ASSET RF-Design parameters

The RF OMC data is composed of two parts: the BSS system default settings; and the site-dependent data. These data will be loaded into the OMC database and then the BTS integration and commission works can proceed. Default settings of the RF OMC data will be prepared and released in both hard-copy and electronic format using the PARCAT system. Both BSS and RF engineers will carefully review these defaults and the approval of the Lucent technical director is required for release or any revision.
A document will be issued with appropriate approvals. This document will contain the all the defaults values and explanations of the OMC objects.
2.9.2 RF OMC DATA RELEASE

2.9.2.1 Task inputs
Interim parameter lists from Neighbour lists, Frequency plan and Staged rollout tasks in this WP.

In order to accommodate the optional staged implementation schedule and the resulted staged RF network design as described in the Staged rollout task (section 2.8.3), the RF OMC data set will be released for every new phase 5 to 10 days before the integration date. Operations and Maintenance staff will carry out this activity, with input from the RF Engineering team.
The OMC data will incorporate the in Neighbour lists, Frequency plan and the other RF parameters. The data release will include the system default settings and following site-dependent parameters: 1. Frequency plan 2. Neighbour lists 3. Cell re-selection lists 4. CellID 5. BSIC 6. LAC
GPM.RFE.WP1.1V2.0
31
Lucent Technologies
2.10 WORK PACKAGE 10 SITE VERIFICATION

2.10.1 TASK INPUTS
1. OMC dump of the following objects: BSC BTS ADJCELL ADJRES POWER HOCTRL RT FH CHN RF Design database
2.
2.10.2 TASK DESCRIPTION

Site Verification is carried out on a new site in order to ensure that the site is functioning to an acceptable degree. The minimum verification required to release the site to the customer is as follows: 1. Verify RF OMC data is input correctly at the OMC. 2. Verify the site dependent parameters as stated in the RF OMC data using test equipment from field measurements. 3. Verify the output power within the main lobe near to the site is at an acceptable level, with line of site to the antennas if possible. Ensure the correct BCCH frequency is serving in the direction the sites sector is pointing plus the TCH for sites with more than 1RT, as per the Proposal RF Design as described in the RF Design Presentation in section 2.4.6. 4. Verify the output power between transceivers on the same cell is similar. A discrepancy of more than 6dB are unacceptable. A stationary external antenna with unity gain should be used to receive field measurements for a comparison to be made between transceivers. BTS power control and DTX should be disabled for this test. 5. Verify that call set-up and call termination can take place on each cell. Ensure a call can be made on every timeslot on each cell successfully and verify audio quality in both directions. 6. Drive test the areas as highlighted in the Discuss the RF Design Objectives and Assumptions with Customer task (in section 2.2.2) to ensure the design objectives are met. 7. Ensure inter-cell handovers and intra-cell handovers (between channels or timeslots) can take place. If applicable, test at least 1 of the inter-BSC and inter-MSC handovers to ensure they can take place.
2.10.3 DELIVERABLES
The Site Verification report will incorporate: Site ID Configuration Neighbor relations A parameter list for each cell A checklist of the Site Verification tasks items 3 to 7.
GPM.RFE.WP1.1V2.0
32
Lucent Technologies
Plots of the following Best Server Receive Level Receive Quality MS Transmit Power
2.11 WORK PACKAGE 11 INITIAL OPTIMISATION

2.11.1 TASK INPUTS
SiteVerification Reports from Work Package 10 Site Verification for all sites that have been verified and will be optimised in this task.

Initial optimisation consists of auditing and preparing sites for Work Package 12 Primary Optimisation in section 2.12. These tasks include: Reviewing site/customer design objectives (if available) Determining drive test routes (customer input & sign off) Determining default parameter settings Identifying neighbours through RF prediction tools Reviewing of frequency plan Identifying missing neighbours through analysis of drive test data Auditing all parameters within the OMC database for proper values. This includes ensuring that: - defaults are set. - adjacent cells information is validated with BTS information. - adjacent reselection lists match adjacent cells list. - neighbour lists are audited to ensure they are mutually defined. Completing site audits. This includes: - verification of site operation, i.e. there is no equipment/hardware problems identified. - verification of antenna configurations, sector identification, correct connection and direction - completion of call tests to verify the BCCH & TCH(s) frequency, BSIC, transmitted power and power reduction of the mobile.
2.11.3 DELIVERABLES
Sites that have been audited.
2.12 WORK PACKAGE 12 PRIMARY OPTIMISATION

2.12.1 TASK INPUTS
Sites that have undergone initial optimisation.

The primary optimisation phase is the most detailed and time consuming optimisation phase. To be done efficiently and effectively, management attention to this phase is crucial. This includes the prioritisation of workload & problems, co-ordination with internal & external customers/departments,
GPM.RFE.WP1.1V2.0
33
Lucent Technologies
assignment of tasks and documentation. A significant part of this optimisation phase is the fine-tuning of site configurations and the finalising of frequency plans. If either of these two steps is not performed properly, parameter adjustments will have a minimal effect on resolving a problem area. The steps of the primary optimisation phase include: baseline drive tests analysis and identification of problem areas from drive test data prioritisation of problem areas investigation & analysis of each problem area, this includes verification of sites original coverage objectives. investigation of each problem area, including interference/coverage analysis. identification of solutions and implement resolutions retest of problem area, to ensure that the problem has been resolved and verify that the solution did not cause additional problems to other areas of the network document changes (to provide a history of all changes and understanding of current settings) move to next problem It is important to note that each change is implemented and tested individually to ensure that there is no degradation to the surrounding network and to identify the impact of each change. These steps are repeated until all of the identified problem areas have been investigated, analysed and resolved.
2.12.3 DELIVERABLES
A cluster of sites that are operating and able to carry network traffic.
2.13 WORK PACKAGE 13 NETWORK VERIFICATION

2.13.1 TASK INPUTS
1. OMC dump of the following objects: BTS ADJCELL ADJRES POWER HOCTRL RT BSS RF Design database
2.

This Work Package verifies that the entire network has met the RF network design objectives agreed upon with the customer during the Discuss the RF Design Objectives and Assumptions with Customer task (in section 2.2.2). Network Verification is completed following Work Package 12 Primary Optimisation, once the network is stable after build activities. Any sites/areas that are not to be considered at the time of the Network Verification should be clearly identified and signed-off approval received from the customer. Such areas may exist due to current build activities or site changes that are being made outside the scope of Lucent obligations.
GPM.RFE.WP1.1V2.0
34
Lucent Technologies
This WP involves Performing a final consistency check on all RF related objects. Any discrepancies should be corrected or identified as to their reason. Performing a final drive test on the entire network. Drive test routes should be based on the major roads and highways without respect to cluster boundaries. Analyse the collected drive test data to pinpoint any areas that do not meet the required design objectives. Any such areas should be further optimised until corrected or documented as to their reason. .
2.13.3 DELIVERABLES
A report consisting of: 1. A listing of all the sites or clusters considered as delivered at the time of the testing. 2. A summary of the consistency check results. 3. A softcopy of an OMC dump of the RF related objects. 4. A softcopy of the RF Change database. 5. Network-wide plots of: RxLevel RxQuality Best Server
2.14 ONGOING NETWORK OPERATION AND MAINTENANCE

Although RF Engineering may provide resources to carry out this task, it is not owned and managed by RF Engineering and so it is outside the scope of this document.
GPM.RFE.WP1.1V2.0
35
Lucent Technologies
3. DOCUMENT CONTROL
3.1 OWNERSHIP AND CONTROL INFORMATION
Author: Location: Created: Last updated: Owning organisation: Chris Sroka D:\Chris Sroka\GSM Platform Group\Wp01 - RF Process\RF Eng process description v2.0.doc 10 March 1998 14 December 1999 GSM Customer Support & Services (CSS) - Network Quality Engineering GSM/UMTS RF Engineering Group
3.2 AMENDMENT HISTORY

Version Draft 1.0 Draft 1.1 1.0 1.1 1.2 1.3 Date Feb 98 11 Mar 98 11 Mar 98 13 Mar 98 17 Mar 98 25 Mar 98 2.8.3 2.8.4 2.12.2 2.9.4 Section (wrt previous doc) All 2.8.1 Nature of Amendment Document creation Inclusion of section. First release after review Inclusion of RAM Distinguished between site and candidate site Altered section title to better reflect purpose Corrected reference to cw drive tests Added references to expense and COGS risks Added section Added project costs and durations Incorporated GPM numbering scheme Included references to Site Location Visit Report Search Ring Report Candidate Site Identification Report Candidate Assessment Report Site Design Review Report Included references to Site Design Review Report Site Survey Report Documentation flow chart and references to it. RF Engineering Platform Group Lucent Technologies Proprietary Amendment Author Chris Sroka Chris Sroka Chris Sroka Reiner Beck Chris Sroka Chris Sroka Chris Sroka
1.4 1.5
31 Mar 98 7 Apr 98
2.4.2 2.4.3.2 Footers
Chris Sroka Chris Sroka
2.8.1.2 2.8.2.2 2.8.3.2 2.8.4.2 1.6 23 April 98 2.8.5.2 2.8.7.2
Chris Sroka
GPM.RFE.WP1.1V2.0
36
Lucent Technologies
1.7
12 May 98
All
All All All
V1.7 d13
Nov 99
2.2.4
V1.7 d14
Dec 99
WP2.1, 3, 6 WP3.1, 3 WP4.1, 2 WP5 moved to WPs 2 & 6 WP7.1, 3, 4 WPs 8, 9, 10
V2.0
Dec 99
WPs 10-13
Documentation fields and relationships After meetings with Chris Sroka, Reiner Beck, Adrian Flewitt, Luc Ngo and Zia Khan: Moved all references on documentation to document GPM.RFE.WP1.4 Moved RAM references to GPM.RFE.WP1.5 Restructured tasks into Work Packages. Rearranged and added sections according to Taiwan RF Design experience (from T C Tsao) Moved RFT/RFQ response to immediately after RF Design Proposal Added review and Clarifications to RFT/RFQ response In order to align with cost model: Removed section 2.2.4 Preliminary propagation environment investigation, 2.2.6 RF Design Objectives Review and 2.3.4 Build up the Antenna Pattern Library Updated changes after 1Dec99 phone conference attended by following RF reps: Chris Wateness (KSA) Mathias Guetermann (EMEA) Ian Webber (GSM support) Mark Brady (Australia) Philip Bell (Taiwan) Meng Li (China) Lee Kong Wah (Asia Pacific) Adrian Flewitt (GSM support) Chris Sroka (GSM support) Complete for RF Design activities (WPs 1-9) Complete for Optimisation WPs (10-13) Awaiting confirmation
Chris Sroka
Chris Sroka
CS
CS, Mike Boyd
GPM.RFE.WP1.1V2.0
37
Lucent Technologies
3.3 DOCUMENT FEEDBACK FORM

Document Title Document number Top level RF Engineering Process Description PM.RFE.WP1.1 Version 2.0 Date 14 Dec 1999
We welcome your feedback on this document. Your comments can be of great value in helping us improve our documentation. Please rate the effectiveness of this document in the following areas. Excellent Ease of use Clarity Completeness Accuracy Organisation Appearance Examples Illustrations Overall Satisfaction Please check the ways you feel we could improve this document. Improve the overview/introduction Make it more concise/brief Improve the table of contents Add more step-by-step procedures/tutorials Improve the organisation Add more troubleshooting information Include more figures Make it less technical Add more examples Add more/better quick reference aids Add more detail Please provide details for the suggested improvement Good Fair Poor
What did you like most about this document?
Feel free to write any comments below or on an attached sheet
If we may contact you concerning your comments please complete the following Name Phone number Department Date Address Email When you have completed this form please either email or fax it to: Chris Sroka RF Engineering Consultant GSM RF Engineering csroka@lucent.com Fax +44 (0)1793 886235
GPM.RFE.WP1.1V2.0
38

RF Process

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

RF Process

Hochgeladen von

Copyright:

Verfügbare Formate

Work Package 1 - RF Engineering Process Description

RF Engineering Package for Bids, Proposals and Projects

Top level RF Engineering Process Description

December 1999 GSM RF Engineering AP and EMEA RF Engineering Groups

RF Engineering Platform Group Lucent Technologies Proprietary

Work Package 1 - RF Engineering Process Description

RF Engineering Package for Bids, Proposals and Projects

Work Package 2 ROM Site and Radio Estimate ________________________ 7

2.2.1 2.2.2 2.2.3 1.1.4 1.1.5 1.1.6 1.1.7 1.1.8 1.1.9

Work Package 3 - Initial ASSET Preparation __________________________ 14

1.3.1 1.3.2 1.1.3 1.1.4

Work Package 4 - RF Design Proposal ________________________________ 16

1.4.1 1.4.2 1.4.3 1.4.4 1.4.5 1.4.6

Work Package 5 - RFT/RFQ Response ________________________________ 19

1.5.1 1.5.2 1.5.3 1.5.4 1.5.5 1.5.6 1.5.7

Work Package 6 - RF Site Realisation _________________________________ 22

1.6.1 1.6.2 1.1.3

Work Package 1 - RF Engineering Process Description

RF Engineering Package for Bids, Proposals and Projects

Work Package 7 - Final ASSET Preparation ___________________________ 26

1.7.1 1.7.2 1.7.3

Work Package 8 RF Network Design Delivery ________________________ 28

1.8.1 1.8.2 1.8.3 1.8.4 1.8.5

Work Package 9 RF OMC Data Release ______________________________ 31

1.10 Work Package 10 Site Verification __________________________________ 32

1.11 Work Package 11 Initial Optimisation _______________________________ 33

1.12 Work Package 12 Primary Optimisation _____________________________ 33

1.13 Work Package 13 Network Verification ______________________________ 34

1.14 Ongoing Network Operation and Maintenance _________________________ 35

3. Document Control ________________________________________________36

RF Engineering Platform Group Lucent Technologies Proprietary

Work Package 1 - RF Engineering Process Description

RF Engineering Package for Bids, Proposals and Projects

RF Engineering Platform Group Lucent Technologies Proprietary

Work Package 1 - RF Engineering Process Description

RF Engineering Package for Bids, Proposals and Projects

2.1.2 PRESENT COMPARATIVE ANALYSIS TO CUSTOMER

Work Package 1 - RF Engineering Process Description

RF Engineering Package for Bids, Proposals and Projects

RF Engineering Platform Group Lucent Technologies Proprietary

Work Package 1 - RF Engineering Process Description

RF Engineering Package for Bids, Proposals and Projects

2.2 WORK PACKAGE 2 ROM SITE AND RADIO ESTIMATE

2.2.2 DISCUSS THE RF DESIGN OBJECTIVES AND ASSUMPTIONS WITH CUSTOMER

2.2.2.2 Task Description

Work Package 1 - RF Engineering Process Description

RF Engineering Package for Bids, Proposals and Projects

2.2.3 DATABASE INVESTIGATION

2.2.3.2 Task Description

RF Engineering Platform Group Lucent Technologies Proprietary

Work Package 1 - RF Engineering Process Description

RF Engineering Package for Bids, Proposals and Projects

2.2.4 RF DESIGN OBJECTIVES

2.2.4.2 Task Description

RF Engineering Platform Group Lucent Technologies Proprietary

Work Package 1 - RF Engineering Process Description

RF Engineering Package for Bids, Proposals and Projects

2.2.5 COVERAGE AREA VISITS / ANALYSIS

2.2.5.2 Task Description

COVERAGE AREA VISITS

Work Package 1 - RF Engineering Process Description

RF Engineering Package for Bids, Proposals and Projects

COVERAGE AREA ANALYSIS

2.2.6 LINK BUDGET