Professional Documents
Culture Documents
DAISY2GSWAP StepByStep
DAISY2GSWAP StepByStep
DAISY2GSWAP StepByStep
Note: The features described in this slide-set are related to the version 4.9.1.1 of DAISY.
If the button is disabled please check the licence availability by pressing the
highlighted button shown below
time
DB Import/DB Export
functions, useful in case of
TRS configurations distribution
among local offices/projects.
This button opens the
Listed here are all NSN TRS Configuration Editor, to
Configurations available for the create, modify, or delete items.
site swap.
Cells frame, to
specify the number
of sectors for the
selected site (in the
frame above)
To place a TRX on the PCM grid, right-click on the first sub-timeslot and
from the context menu select the site and Traffic Channel type. A group
of 8 sub-timeslots will be created. After the creation, the user can still
change the channel type for each sub-timeslot.
Note: [COPY] means to map the channel type from the ex-Siemens one.
Then also a Parameter Mapping based on Feature has been done like for the following
features:
• AMR (AMR_HOC, AMR_POC, AMR_HR);
• Hopping (SFH, Dynamic SFH, BBH);
• Half Rate
Sites.xls
PCMBs.xls
Configurations.xls
TRXs.xls
Drag and
Drop of
sites to
define the
Cluster
However, the user can freely overwrite and change the BCF
Name, in case the project requires a different rule.
Finally, the User Set parameter can be modified in order to Syntax for “parameter
assign to each site the desired User Defined parameters override”:
(basically Plan Editor templates for each objects). (OBJ) <param.name>
In addition, to show a possible mapping rule override, the (<optional index for
sub-cell obj>)
LAC will be changed (usually LAC is copied from ex-
Siemens DB). To force that parameter, a new column is
added in the blue area using the correct NSN parameter
name (as it is indicated in the Plan Editor dictionary). Since
the LAC is a parameter on BTS basis, values must be
written in the “white” rows (cell type rows) and not in the
“green” ones (site type rows). The LAC will be changed as
follow: 30104 10104.
For internal use
27 © 2010 Nokia Siemens Networks. All rights reserved.
DAISY 2G Swap: Cluster File Example (3/5)
To complete the radio part, now the yellow and orange area of the Cluster File will be
described.
In the yellow part, DAISY indicates the features activated for each site in the ex-Siemens DB.
This part is read-only, and is reported for user reference. The “*” character means that the
corresponding feature was found “active” for the BTSM or for the BTS objects.
The orange part gives a mapping with the features available in the NSN side and supported by
DAISY. The user can change the implemented NSN feature deleting or adding the “*”
character. The activation of an NSN feature will change the internal mapping rules for the
involved parameters.
Features mapping
between ex-Siemens
and NSN sides
First PCM Second PCM Site#1 has 2 TRXs. The first TRX
(Site#1 – TRX#1) is located on
the first PCM, the second TRX
with EDGE capabilities is located
on the second PCM. For that
reason EDAP for Site#1 is
located on the second PCM too.
Signaling is present on the first
timeslot of each PCM.
Site#2 and Site#3 have the
EDGE TRXs (TRX#2) on the first
PCM, where is located also the
Site#2 – EDAP and Site#3 EDAP.
For each site there are two MUX
objects with O&M and TRX-SIG.
The position of the LAPD are the
same indicated in the ex-Siemens
schema.
For internal use
29 © 2010 Nokia Siemens Networks. All rights reserved.
DAISY 2G Swap: Cluster File Example (5/5)
To summarize, the elements needed to correctly fill the Cluster File are:
(A) BCF / Site# assignment: DAISY need to know which site will be considered the Site#1 of the
configuration, the Site#2, etc. The “Config Site No.” column is used to create this link.
(B) Since our NSN configuration has two PCMs, we need the PCM ID for the first PCM and
PCM ID for the second one. Columns “PCM ID 1” and “PCM ID 2” can be used to provide the
information.
(C) BCF 1 (= Site#1 of the NSN configuration) has its TRX#2 with EDGE on the second PCM,
where is also located its EDAP (Site#1 – EDAP). For that reason the DAP ID must be filled using
“DAP ID (PCM 2)” column. BCF 4 (=Site#2) and BCF 7 (=Site#3) have TRX#2 with EDGE and
EDAP on the first PCM. Their DAP ID must be indicated in the “DAP ID (PCM 1)” column.
(D) BCSU-PCUs follow the same rule applied at point (C).
A B C D
For internal use
30 © 2010 Nokia Siemens Networks. All rights reserved.
DAISY 2G Swap: Cluster Swap Phase
After the filling of the Cluster File generated
in the previous Cluster Definition phase, it
will be finally possible to generate Plan Editor
data in RAML 2.0 file format.
By pressing the Cluster Swap button the swap wizard will be shown to guide the user in all
required steps. Firstly, the tool will asks for the Cluster File. A log window will give a feedback on
any errors found.