Sei sulla pagina 1di 23

Sunrise Communications AG

Network Radio Access


Hagenholzstrasse 20/22
CH-8050 Zurich

Email
Internet
Phone
Fax

nicolas.paul@sunrise.net
www.sunrise.ch
+41 (0) 76 777 34 67

Engineering Central
(NERAENCE)
ATOLL
USER GUIDELINE
Version
Author
Date

V1.3
Nicolas Paul
March 10, 2008

The material contained within this documentation is legal property of Sunrise Communications AG and may
not be copied, reproduced or published by any methods without prior written permission of Sunrise
Communications AG.

Title
Version
Page

ATOLL / USER GUIDELINE


V1.3 / January 23, 2008
2/23

1 Introduction............................................................................................3
1.1 Report Revision History.....................................................................................3
2 Naming Convention.................................................................................4
2.1 Introduction....................................................................................................... 4
2.2 Special Cases.................................................................................................... 4
2.3 Common Convention......................................................................................... 4
2.3.1 Site Table................................................................................................4
2.3.2 Transmitters Table..................................................................................5
2.4 RND Site............................................................................................................ 6
2.4.1 Naming.................................................................................................... 6
2.4.2 Flagging..................................................................................................6
2.5 Approved Rollout...............................................................................................7
2.5.1 Naming.................................................................................................... 7
2.5.2 Flagging..................................................................................................7
2.6 Trial Site............................................................................................................ 8
2.6.1 Naming.................................................................................................... 8
2.6.2 Flagging..................................................................................................8
3 Costumized Fields....................................................................................9
3.1 Site Table (automatic update from Netsite)......................................................9
3.2 Transmitter table............................................................................................... 9
3.2.1 SR_COVERAGE.........................................................................................9
3.2.2 SR_PROJECT_TYPE...................................................................................9
3.2.3 SR_JOBSTATUS........................................................................................9
3.2.4 Transmitter information (automatic updated from Netsite)...................10
3.2.5 Used for RF data definition (part of the Re-import)...............................11
3.3 Base Station Equipment..................................................................................12
3.4 Radio Repeaters equipment............................................................................12
4 Transmitter........................................................................................... 13
4.1 Transmitter Numbers......................................................................................13
4.2 POWER Setting................................................................................................ 13
4.2.1 For GSM Project.....................................................................................13
4.2.2 For UMTS Project...................................................................................14
4.3 Antenna Height............................................................................................... 15
4.4 Antenna Type.................................................................................................. 15
4.5 Mechanical Tilt................................................................................................ 16
4.6 Propagation Model........................................................................................... 17
5 Microcells / Macrocells Layer..................................................................18
6 Sector SPLIT..........................................................................................19
7 Repeater............................................................................................... 20
7.1 Off air repeaters.............................................................................................. 20
7.2 Optical repeaters............................................................................................. 20
8 Projects................................................................................................. 21

Title
Version
Page

ATOLL / USER GUIDELINE


V1.3 / January 23, 2008
3/23

1 Introduction
This document describes basic parts of the working processes
concerning radio planning.
Main theme is the naming convention of network elements and the
usage of the customized fields in the Atoll site database.

1.1 Report Revision History


Version

Date

Author

Comments

Draft 0.1

2006-1220

Paul N.

New RF Tool / Atoll

Version
1.0

2007.01.1
1

Paul N.

Reviewed by the
regions

Version
1.2

2007-0125

Paul N.

Atoll Version 2.6.2

Version
1.3

2008-0303

Paul N.

Update for
Repeater

Title
Version
Page

ATOLL / USER GUIDELINE


V1.3 / January 23, 2008
4/23

2 Naming Convention
2.1 Introduction
The unique naming allocation of network elements in the
Radio Planning tool ATOLL, for example a base station or a
radio repeater, is a basic and indispensable element of the
whole planning process.
Ignoring the naming convention may cause important
problems.
Besides we have to keep in mind that all data concerning the
radio configuration of a site have to be defined into ATOLL.
For further descriptions about Atoll, please refer to the
following documents:
Implementation Concept
Macros specifications
Interfaces specifications
Atoll custom fields
2.2 Special Cases
If no suitable candidate for a given Site (for example TI555)
can be acquired and the Site is built co-located to an existing
Transmission Repeater, BSC or whatever other existing
Network Element (for example TI777), then the original Site
TI555 is deactivated in NETsite The already existing Site Code
TI777 is taken for this site. The base station TI777-GSM-1 is
just co-located to TI777-REP-1.
2.3 Common Convention
The following fields in the Atoll Database have to be filled out
corresponding to the rules as follows:
2.3.1Site Table
NAME:
This is the Primary Key to the Atoll Site Table, therefore
it has to be unique. The naming convention.
(SITE_NAME) in Atoll has to match with the site
name in NETsite. The site naming is one of the key
between Atoll and Netsite DB. For example this matching
is needed for preparing integration data.

Title
Version
Page

ATOLL / USER GUIDELINE


V1.3 / January 23, 2008
5/23

If the site is not yet defined in Netsite, the design


naming has to be used (Chapter 2.4)
COMMENT_:
Enter comments here if needed
SR_SITE_OBJECTIVE: Enter the site Objective here if needed
2.3.2Transmitters Table
Transmitter Name (TX_ID):
This is the Primary Key to the Atoll Transmitters Table,
therefore it has to be unique like naming convention.
The Transmitter name (TX_ID) in Atoll has to
match with the site, Network element and sectors
name in NETsite. The transmitter naming is the key for
the NE and sector information between Atoll and Netsite
DB. For example this matching is needed for preparing
integration data.
The Transmitter Name corresponds more or less to the to BTS
name in the network. (cp. Network BTS naming + the
candidate information)
- Characters 1 to 7 :
Correspond to the site Name
(ZH001-3)
- Character 8 : Corresponds to the Transmitter sector letter
(i.e. A, B, C or D.)
- Character 9 : Corresponds to the Transmitter frequency
band,
G
GSM 900 BASESTATION
D
GSM 1800
BASESTATION
U
UMTS Node B
- Character 10:
i.e. [1,9].

Corresponds to the sunrise BCF number,

Example: ZH001-3AG1
For further description please refer to the following
documents NE Naming Convention.

Title
Version
Page

ATOLL / USER GUIDELINE


V1.3 / January 23, 2008
6/23

2.4 RND Site


A RND (RadioNetworkDesign) Site is created if an official RND
order exists. A RND sites never exists in NetSite.
During the Design phase all new site have to respect the
following rule
2.4.1Naming
The following Naming convention applies:
C YY QQ NPA ZZ T
C
Cluster Code (1=Lausanne, 2=Bern,
3=Nordostschweiz , 4=Sdostschweiz , 5=Zentralschweiz)
YY

RND Year

QQ

RND Quarter (Q1, Q2, Q3, Q4 according to season)

NPA NPA Code (3 digits)


ZZ

Incremental Number (starting at 01)

Type of planned site (G=GSM, D=DCS, U=UMTS)

Examples:
107Q3LAU01G
Cluster Lausanne for RND07Q3: 1.Site in Lausanne
City: Type GSM
207Q1BEC02D
Cluster Bern for RND07Q3: 2.Site in Bern: Type DCS
2.4.2Flagging
The Field SR_JOBSTATUS must be set to RND

Title
Version
Page

ATOLL / USER GUIDELINE


V1.3 / January 23, 2008
7/23

2.5 Approved Rollout


2.5.1Naming
You get the Site_ID from netsites definition; the naming in
atoll has to be the same as the one in Netsite.
For the Site ID naming convention in Atoll follow the rule
describe in chap 2.3 commun convention .

looks as follows:
- Characters 1 to 5: correspond to the site_id_body (ex
ZH001). Where site_id_body consists of:
2 alphabetic characters, i.e. [A,Z] (ex ZH).
3 numeric characters, i.e. [0,9] (ex 001).
- Characters 6: is -.
- Characters 7: being a numeric/alphabetic character, i.e.
[0,9] or [A,Z], corresponds to the site_candidate_number
(ex 1). (the candidate number as in NetSITE)
Atoll: ZH001-1 (cp. Netsite site name)
Examples:
BA101-3 is the third candidate of a Site in Basel with the
ongoing number 101
GE002-5 is the fifth candidate of a Site in Geneva with the
ongoing number 002
ZH250-4 is the fourth candidate of a UMTS Site in Zrich with
the
ongoing number 250
2.5.2Flagging

Title
Version
Page

ATOLL / USER GUIDELINE


V1.3 / January 23, 2008
8/23

2.6 Trial Site


A Trial Site can be created anytime by the Radio-Planner for
trial purpose. But that is recommended to do those trials on a
local Project.
2.6.1Naming
The following Naming convention applies:
TYYMMDDXXZZ
YYMMDD
XX

Creation date (Format Year, Month, Day)


Initials of RadioPlanner

ZZ
Incremental Number
Examples:
T011213JQ01
Joakim Quensel created this 1. Trialsite on 13.12.2001
T011213JQ02
Joakim Quensel created this 2. Trialsite on 13.12.2001
T011214JQ01
Joakim Quensel created this 1. Trialsite on 14.12.2001
2.6.2Flagging
If you want to save the Trial site in a shared DB you have to
set the SR_JOB_Status field to RND. Otherwise do this Trial
on a local project.

Title
Version
Page

ATOLL / USER GUIDELINE


V1.3 / January 23, 2008
9/23

3 Costumized Fields
3.1 Site Table (automatic update from Netsite).
The following Fields are automatically updated from Netsite if
the SR_JOBSTATUS is set to As Planned or As Built.
Therefore the definition is the same than the one in Netsite.
It is not mandatory to update these fields during the design
phase.
SR_SITE_NAME: From the netsite site name
SR_PREFERED_SITE: from the netsite definition
SR_ADDRESS: from the netsite Address (ZIP + City,
Address)
SR_NPA_CODE: from the netsite definition
SR_NPA_NAME: from the netsite definition
SR_CLUSTER: from the netsite definition
3.2 Transmitter table
3.2.1SR_COVERAGE
With the help of the Coverage Field it can be distinguished
between different coverage types like indoor, outdoor and
tunnel coverage
3.2.2SR_PROJECT_TYPE
This Field enables selection of sites by Project Type. This Field
should be set from the regional planner corresponding to the
Project Type the site is linked to.
Ex:
Target non target for GSM,
PS128 PS384
for UMTS
3.2.3SR_JOBSTATUS
The Atoll concept is based on 4 site statuses called
SR_JOBSTATUS

Title
Version
Page

ATOLL / USER GUIDELINE


V1.3 / January 23, 2008
10/23

SR_JOBSTATU
S
RND
As Planned
RF Data
As Built
The RND, As Planned, RF Data are used for the planning
phase. The site name and the transmitter name have to be
unique within these 3 job statuses (i.e.: for a defined
transmitter, a Planned configuration has an unique
SR_JOBSTATUS).
The As Built status corresponds to the live network, therefore
the naming has to correspond to the site name in Netsite and
the transmitter name in the network.
To know more about atoll concept please refer to the
Implementation Concept document
Each Jobstatus has its own interface definition (see Interfaces
specification document).
3.2.4Transmitter information (automatic updated from
Netsite).
The following Fields are automatically updated from Netsite if
the SR_JOBSTATUS is set to As Planned or As Built.
Therefore the definition is the same than the one in Netsite.
It is not mandatory to update these fields during the design
phase (if the SR_JOBSTATUS = RND).
3.2.4.1

Netsite Information Fields

SR_SITE_UNDER_6W: from the netsite definition.


SR_NETWORK_ELEMENT_STATUS: from the netsite
definition.
3.2.4.2 Transmitter configuration.
Those fields are automatically updated thanks to Netsite
As planned information if the transmitter
SR_JOBSTATUS is set to As Planned
As Built information if the transmitter SR_JOBSTATUS
is set to As Built.
ANTENNA_NAME from the netsite definition

Title
Version
Page

ATOLL / USER GUIDELINE


V1.3 / January 23, 2008
11/23

HEIGHT from the netsite definition


AZIMUT from the netsite definition
TILT from the netsite definition
SR_TILT_EL: from the netsite definition (used for UMTS RF
data definition)
FEEDERLENGTH_DL: From Netsite total feeder attenuation
3.2.4.3 Used for WINES restrictions
Those fields are automatically updated thanks to Netsite with
As submitted information if the transmitter
SR_JOBSTATUS is set to As Planned
As Permitted information if the transmitter
SR_JOBSTATUS is set to As Built.
SR_MECHANICAL_DOWNTILT_RANGE_MIN
SR_MECHANICAL_DOWNTILT_RANGE_MAX
SR_ELECTRICAL_DOWNTILT_RANGE_MIN
SR_ELECTRICAL_DOWNTILT_RANGE_MAX
SR_AZIMUTH_RANGE_MIN
SR_AZIMUTH_RANGE_MAX
SR_POWER_RANGE_MAX
3.2.5Used for RF data definition (part of the Re-import).
SR_LAC: set by the RF planner
SR_RAC: set by the RF planner
SR_RZ: set by the RF planner
SR_CELLID: A Macro does the allocation
MISCDLL: For GSM Project only, it corresponds to the
BsTxPwMax (GSM attenuation)

Title
Version
Page

ATOLL / USER GUIDELINE


V1.3 / January 23, 2008
12/23

POWER: For GSM Project only, Set by the RF Planner (Chapter


4.3.1)
POWER_MAX: For UMTS Project only, Set by the RF Planner
(Chapter 4.3.2)
PILOT_POWER: For UMTS Project only, Set by the RF Planner
(Chapter 4.3.2)
The SR_BSC, SR_ MSC for GSM and SR_RNC, SR_MSC for UMTS
fields are useless for the RF data task, it is just in Atoll for
your information (part of the Re-import).
SR_MAL_DISPLAY
All those fields are part of the re-import if the Transmitter
SR_JOBSTATUS is set to As Built.
3.3 Base Station Equipment.
The entry in the Base Station Equipment field is important to
distinguish between GSM, DCS and Dualband sites. It gives
also an indication for the power setting.
GSM: Talkfamily GSM
DCS: Talkfamily DCS
DUA: Ultrasite or metro site (Dualband site GSM or DCS)
NOB: RBS UMTS

3.4 Radio Repeaters equipment


It is defined in the Transmitter equipment table.
To be defined with Forsk.

Title
Version
Page

ATOLL / USER GUIDELINE


V1.3 / January 23, 2008
13/23

4 Transmitter
4.1 Transmitter Numbers
A standard site in sunrise network has 1 to 3 sectors. Only in
special cases like indoor solutions or tunnel sites.
Atoll transmitter numbers starting from A to C, missing
numbers are possible. The definition is the same that the one
in the NMS.
Sectors have to be entered clockwise sorted by azimuth,
starting with 0 degree. Therefore an azimuth of 360 degree is
forbidden.
4.2 POWER Setting
4.2.1For GSM Project

DCS
1800

UltraSite with
TSxB

UltraSite with
TSxA

MetroSite 10W

42.
3
39.
3
36.3
41.
8
37.
8

MetroSite 5W

FlexiTalk

42.
3
39.
3
36.3
41.
8
37.
8

MetroSite 1W

3 to 4 TRX
5 to 6 TRX

42.
3
39.
3
36.3
41.
8
37.
8

IntraTalk

GSM 900 1 to 2 TRX

CityTalk

Number of TRX

GSM BTS Type

4.2.1.1 POWER:
Correspond to the BTS output power
The correct use of the POWER field in the Transmitter Table is
very important for a correct frequency planning.

30 37 41 45.4 45.7

27 34 38 42.1
24 31 35 38.8
45.2
1 to 2 TRX
30 37 41
5
41.9
3 to 4 TRX
27 34 38
5
38.6
5 to 6 TRX 34.8 34.8 34.8 24 31 35
5

42.4
39.1
45.7
5
42.4
5
39.15

Title
Version
Page

ATOLL / USER GUIDELINE


V1.3 / January 23, 2008
14/23

This information is part of the re-import from the Live


Network (As Built)
4.2.1.2 MISCDLL:
Correspond to the BsTxPwMax (GSM attenuation with 2 dB
steps).
This information is part of the re-import for the Live
Network (As Built).
This field is part of the RF data definition.(RF Data)
4.2.1.3 FEEDERLENGTH_DL:
Correspond to the total feeder attenuation
This field is automatically updated thanks to Netsite with
As planned information if the transmitter SR_JOBSTATUS
is set to As Planned
As Built information if the transmitter SR_JOBSTATUS is
set to As Built.
This field can be exported to Netsite As planned if the
SR_JOBSTATUS is set to RND.
4.2.2For UMTS Project
4.2.2.1 POWER_MAX and PILOT_POWER
That information is part of the re-import for the Live Network
(As Built).
This field is part of the RF data definition. .(From the GL
CDR_values_RBS.pdf)
4.2.2.2 JUMPER ATT and JUMPER DELAY
Those fields are part of the RF data definition.(From the GL
CDR_values_RBS.pdf)
SR_ UL_JUMPER_DELAY_BRANCH_A
SR_ UL_JUMPER_DELAY_BRANCH_B

Title
Version
Page

ATOLL / USER GUIDELINE


V1.3 / January 23, 2008
15/23

SR_ DL_JUMPER_DELAY_BRANCH_A
SR_ DL_JUMPER_DELAY_BRANCH_B
SR_ UL_JUMPER_ATT_BRANCH_A
SR_ UL_JUMPER_ATT_BRANCH_B
SR_ DL_JUMPER_ATT_BRANCH_A
SR_ DL_JUMPER_ATT_BRANCH_B
4.2.2.3 FEEDER ATT and FEEDER DELAY
Those fields are part of the RF data definition.(Info from the
commissioning summary)
SR_ UL_FEEDER_DELAY_BRANCH_A
SR_ UL_FEEDER_DELAY_BRANCH_B
SR_ DL_FEEDER_DELAY_BRANCH_A
SR_ DL_FEEDER_DELAY_BRANCH_B
SR_ UL_FEEDER_ATT_BRANCH_A
SR_ UL_FEEDER_ATT_BRANCH_B
SR_ DL_FEEDER_ATT_BRANCH_A
SR_ DL_FEEDER_ATT_BRANCH_B
4.3 Antenna Height
Antenna height is entered as center height of the antenna.
That is the distance between the centerline of the antenna
and the ground level in meters.
4.4 Antenna Type
The antenna types in Planet can be grouped by any fields
defined on the Antenna table.
NAME
GAIN
CONSTRUCTOR

Title
Version
Page

ATOLL / USER GUIDELINE


V1.3 / January 23, 2008
16/23

COMMENT_
DIAGRAM

OLE Object

ELECTRICAL_TILT
Beamwidth
FMin
FMax
SR_FRONT_TO_BACK
SR_BEAMWIDTH_V
SR_ANTENNA_NAME
SR_BAND
SR_POLARIZATION
SR_ANTENNA_LENGHT
SR_MULTIBAND
SR_ELECTRICAL_RANGE
SR_STATUS
SR_ANTENNA_TYPE
SR_FREQUENCY
The antenna name is composed out of the type no.,
polarization, beam width horizontal, integer gain and tilt.
In case of dual/triple band antennas a D, G or U is attached to
the type no. to distinguish the correct pattern. It is therefore
important for dual/triple band sites to use the correct antenna
type. Use
D 1800 band,
G 900 band U UMTS band

4.5 Mechanical Tilt


In the Atoll User Reference Guideline the definition of
mechanical tilt is:
Down Tilt: The antenna mechanical down tilt in degrees. (A
positive number for down

Title
Version
Page

ATOLL / USER GUIDELINE


V1.3 / January 23, 2008
17/23

tilt and a negative number for up tilt.)


Example:
For six degrees mechanical down tilt enter 6.
For two degrees mechanical up tilt enter 2.
In the same way tilts are entered in NetSite:
For NIS calculations, see the BUWAL Calculation Guideline.pdf

4.6 Propagation Model


The following models are available:
URBAN 900
SUBURBAN_RURAL_900
URBAN 1800
SUBURBAN_RURAL_1800
URBAN UMTS
SUBURBAN_RURAL_UMST
Wavecall Model (can be used where 3D data are available).
The frequency has to match the corresponding band and pixel
size has to match the mapping settings to be able to perform
a successful prediction. For best results, Urban models should
be used in areas where are mainly low_density_urban or
high_density_urban clutter.

Title
Version
Page

ATOLL / USER GUIDELINE


V1.3 / January 23, 2008
18/23

5 Microcells / Macrocells Layer


A microcell will get different parameter than Macro cells. This
entry is set on the Layer field (in the transmitter table).
This information is part of the re-import from the Live
Network (SR_JOBSTATUS 0 As Built)
This field is part of the RF data definition.( SR_JOBSTATUS
= RF Data)
For microcells 1km prediction size is recommended
For macrocells 20km prediction size is recommended

Title
Version
Page

ATOLL / USER GUIDELINE


V1.3 / January 23, 2008
19/23

6 Sector SPLIT
To be defined with Forsk.

Title
Version
Page

ATOLL / USER GUIDELINE


V1.3 / January 23, 2008
20/23

7 Repeater
7.1 Off air repeaters
To be defined with Forsk.

7.2 Optical repeaters


To be defined with Forsk.

Title
Version
Page

ATOLL / USER GUIDELINE


V1.3 / January 23, 2008
21/23

8 Projects
The data status will be assigned on Transmitters level and will
apply to child objects as well. The workspace concept will be
implemented using Atoll projects. The number of projects is
defined as following:
Master Project. This project will store live data only (As
Built status).
RF DATA Project. This project stores RF DATA and As
Build data without planned modifications.
Planning Project. This project stores planning, RF DATA
data, and As Built data without planned modifications.
Design Project. This project stores design, planned, RF
DATA and As Built data without planned modifications.
The work teams will get their set of data based on selection of
objects from the database using status criteria.
The Design team works on the Design project which
shows all statuses.
The RF planning team works on the Planning project
(showing the As Planned, RF Data, and As Built
statuses).
The RF planning team (AFP) works on the RF DATA
project (showing the RF Data and As Built statuses).
The RF DATA team works on the RF DATA project
(showing the RF Data and As Built statuses).
The Reporting team works in read-only mode on the
Planning, RF DATA, and Master projects.
The Optimization team works in read-only mode on the
Planning and Master projects.
Changing the status is allowed according to defined.
The Design team can change the status from As Built
and RDN to As Planned.

Title
Version
Page

ATOLL / USER GUIDELINE


V1.3 / January 23, 2008
22/23

The RF planning team can change the status from As


Planned and As Built to RF Data.
The RF planning team (AFP) can change the status As
Built to RF Data.
RF DATA users can change the status from RF Data to
As Built.
These sets of rules will be implemented using Oracle triggers
and user rights per tables.
The data with the As Built status in Design, Planning and RF
DATA projects will be updated on a regular basis from the
Master project using a synchronization tool.
The work cycle will be as follows:
1. The Design project gets updated with As Planned, RF
Data, and As Built data from their source projects.
2. The Design group creates the list of transmitters with
the status As Planned based on RND and As Built
data.
3. The Planning project gets updated with transmitters with
the status As Planned, RF Data, and As Built from
the Design, Master and RF DATA projects.
4. Transmitters with the status As Planned are
synchronized with Netsite.
5. The RF planning group creates the list of transmitters
with the status RF Data based on As Planned and
As Built data in the Planning project.
6. The RF Data data are sent to PMD.
7. RF DATA users change the status of transmitters from
RF Data to As Built.
8. As Built data are updated in the Master database from
the RF DATA project.
9. The Master project gets updated from PMD (Re-import)
and Netsite.

Title
Version
Page

ATOLL / USER GUIDELINE


V1.3 / January 23, 2008
23/23

Functional Implementation diagram

Netsite
Write

PMD

DPI map
Read

Read

Read

Design Project
Planning Project

As Planned

As Planned

Official New Transmitters

Official New Transmitters

Job in TOC

Job in TOC

On going modification

On going modification

New Transmitters

New Transmitters

Live Network

Live Network

Without planned

Without planned

modification

modification

Reimport

Read

Write

Atoll
Database
environment

RND
Future Transmitters

DIP

TOC project
Job in TOC
On going modification
New Transmitters

Master Project

Live Network
without planned
modifications

Live Network
All On air
Transmitters

Merger
Synchronizes Atoll
Projects

AddIns
Atoll Sessions
Wavesight
WiNeS

Potrebbero piacerti anche