Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
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
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
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.
Date
Author
Comments
Draft 0.1
2006-1220
Paul N.
Version
1.0
2007.01.1
1
Paul N.
Reviewed by the
regions
Version
1.2
2007-0125
Paul N.
Version
1.3
2008-0303
Paul N.
Update for
Repeater
Title
Version
Page
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
Example: ZH001-3AG1
For further description please refer to the following
documents NE Naming Convention.
Title
Version
Page
RND Year
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
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
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
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
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
Title
Version
Page
Title
Version
Page
Title
Version
Page
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
CityTalk
Number of TRX
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
Title
Version
Page
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
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
Title
Version
Page
Title
Version
Page
Title
Version
Page
6 Sector SPLIT
To be defined with Forsk.
Title
Version
Page
7 Repeater
7.1 Off air repeaters
To be defined with Forsk.
Title
Version
Page
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
Title
Version
Page
Netsite
Write
PMD
DPI map
Read
Read
Read
Design Project
Planning Project
As Planned
As Planned
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