DAISY2GSWAP StepByStep

DAISY for 2G SWAP
Step-by-Step User Guide
Leandro Palagiano, Venanzio Traversa, Ernesto Esposito

07/07/2010
For internal use

1 © 2008 Nokia Siemens Networks. All rights reserved.
DAISY 2G Swap: Assumptions
DAISY supports the daily swap activities for a “parcel” scenario, where sites are swapped
in “clusters”. At every “cluster swap”, DAISY calculates parameters using internal mapping
rules, fixes all the incoming/out coming neighbors, and generates the proper data for the
NetAct.
The tool is able to manage a general M:N BSC swap scenario, and It can be used for
GEMINI (providing input as “.asc” ex-Siemens DB in ACL format) or in Multivendor
projects (using a general purpose Excel template).
DAISY works together with Plan Editor to generate data for the NetAct. After the initial
configuration of Plan Editor there is no need to access it again, since DAISY is able to
directly interwork with the tool to upload the generated cluster plan and to export it toward
NetAct.
DAISY 2G Swap Assumptions

- BSC must be already integrated to the Core Network;
- BSC must be already integrated to NetAct, so that plan provisioning is possible;
- BSC, as a logical object, must be already created in RNW DB;
- DAISY doesn’t provide all parameters needed to build up the objects, but only the
relevant ones: the “default” parameter values for each objects have to be already defined
in Plan Editor’s templates. The PE templates will be referred by DAISY, when importing
data into PE.
For internal use
MUSA-DAISY Startup: Startup of MUSA
DAISY is a module of MUSA tool. To access DAISY it is needed to run MUSA and to select a
MUSA Project.
Note: The features described in this slide-set are related to the version 4.9.1.1 of DAISY.
For internal use

MUSA-DAISY Startup: Project creation
A Project can represent a BSC to be swapped, a group of them, a Town, an
area, etc.
At each DAISY project corresponds a folder in the MUSA\Projects directory,
where the tool will search for input (by default) and will store all its output
data.
The first time you run the tool two choices

are available:
- use the Demo Project already present
- create a new empty project, to store your
input and output files generated by DAISY.
To create an empty project, when the

“Select Project” dialog appears, press the
“New Project” button…
…and type your project name
For internal use

MUSA-DAISY Startup: Project selection
To select an already created or a

new Project, select the Project
Name in the left panel, [Empty…]
in the right panel, and press the
“Empty” button.
Then press “Finish” in the next

dialog window (you can ignore all
controls since they are valid only
for other MUSA modules).
After the project selection, the

MUSA environment is accessible
and it will be possible to open the
DAISY module.
For internal use

MUSA-DAISY Startup: DAISY Module
In the following the view of the main MUSA toolbar is reported.

To activate the DAISY Module please click on the highlighted button (or select Tools
menu DAISY)
If the button is disabled please check the licence availability by pressing the
highlighted button shown below
For internal use

DAISY Modules: Main window
DAISY module is composed by three parts or sub-modules
DAISY for 3G Auto-Swap

(RAS06, RU10, Common
Iub scenario)
DAISY for LACE (3G

data build creation for
roll-out)
DAISY for 2G Swaps
For internal use

DAISY 2G Swap: Phases
Initial Configuration: Plan Definition: the Cluster Swap: sites are swapped in
discussion with the customer, TRS start of the BSC swap. clusters, day by day. The cluster can be
planning considerations, Plan Editor Definition of the scenario. easily defined graphically using the GUI.
setting. DAISY is used to create Ex-Siemens DB is Planner must fill few data inputs.
TRS configurations. provided in ACL format.
time
DAISY “ideal” time-process:

complexity mostly placed in
the two initial phases, which
should be executed only
once, defining and mapping
all configurations.
Of course users can use the
tool in a more “iterative”
way, pairing configurations
step by step, after each
cluster swap.
For internal use

DAISY 2G Swap: Configurations Phase
Unfortunately TRS data objects can not be
generated directly and automatically from
the ex-Siemens counterpart, as mostly
happen for objects of the radio part.
The Configurations button gives access to the NSN Configurations page. Here the user can
see all available configurations, used to generate the TRS part for the swapping sites. The user
can import a set of already prepared configurations or creates them starting from scratch.
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.
Using this button it is possible

to close the page and return to
the standard “network” view of
DAISY.
For internal use

DAISY 2G Swap: Configuration Editor (1/3)
The Configuration Editor is divided in several
frames, which must be used to create/select items.
A timeslots representation of the selected PCM is
given using colors for each kind of TRS object.
PCM frame: to TRX frame: to add

add up to 4 PCM TRXs needed by the
objects. selected site.
LAPD/MUX frame: it
Sites frame, to add can be used to
all sites that belong specify MUX for the
to the configuration.
selected site.
Cells frame, to
specify the number
of sectors for the
selected site (in the
frame above)
The grid gives a

“timeslot picture” for
Parameters frame,
the selected PCM. to see all available
On the grid it is properties of the
possible to place selected item.
and see TRS
objects.
To close the Editor.
For internal use

DAISY 2G Swap: Configurations Editor (2/3)
The Configuration control at the

top of the window can be use to
select an already created NSN
TRS configuration, for review or
changes. At the beginning, the
Editor is always set in read-only
mode.
Immediately on the right, a group of buttons permits to create new configurations
and to change the editor from read-only to modify mode. The save button stores
changes and return to the read-only mode. Finally the delete button can be used
to erase unwanted configurations.
Summary of the steps needed to create a new configuration

1. Press the “+” button and select “+ Empty”
2. Add as many PCMs as your configuration needs (PCM frame)
3. Add all your sites (Sites frame)
4. Selecting one site at time, create all the required sectors (Cells frame)
5. Add TRXs for the selected site, using for example the layout button present in
the TRX frame: typing 222 for example means: “add 2 TRXs on the first sector, 2
more TRXs on the second one, and further 2 TRXs on the third and last one”.
6. Add all the MUX objects required by the selected site (LAPD/MUX frame)
7. Select a PCM and right-click on the grid to place any TRS objects using
the context menu tree.
For internal use
DAISY 2G Swap: Configurations Editor (3/3)
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.
Examples of TRX-Sig placement in an

empty sub-timeslot or in a MUX. A TRX-Sig
can be added on a PCM only after the
corresponding TRX has been placed.
An example of O&M placement in an empty sub-timeslot. The “width” of

the object must be selected: 16 kbps (1 STL), 32 kbps (2 STL),
64 kbps (1 TS = 4STL). The O&M LAPD can be also inserted in an
already existent MUX.
An example of EDAP placement:

selecting “Add…” the tool will
asks for the number of TS (rows)
which will be allocated for that
object.
For internal use

DAISY 2G Swap: Plan Definition Phase
The Plan Definition phase must be executed
only once (or few times) at the beginning of
the Swap of one or more BSC.
During this phase the user defines the swap type,
the scenario, provides the source ex-Siemens
DBs (in ACL format), and optionally an “.mdb”
file from Plan Editor.
DAISY analyzes input files to identify all the TRS
configurations in terms of PCMB, BTSM, TRX,
LPDLM, etc. All the collected information are also
saved in some output reports for user reference.
At the end of the process, each ex-Siemens
schemas can be mapped to the NSN one,
defined with the previous Configuration button.
The first step after the pressing of the Plan Definition button is the selection of the Swap Type:
Siemens BR 9.0 NSN RG 10
Siemens BR 10.0 NSN RG 10
Multivendor NSN RG 10
The last option permits to replace the ex-Siemens DB in ACL format with a generic Excel file
containing all relevant objects and parameters. It can be useful in swap scenario from other
vendors. The Excel template required in this case can be found in the Musa\Help folder.
For internal use
The second step of the Plan Definition
consists of the choice of the Swap
Scenario in terms of number of ex-S
BSCs to be swapped into the NSN ones
(N:M scenario).
The tool asks for an Excel file containing
the so called Swap Plan:
In the example above, we define 3 ex-S BSCs

(1, 5, 30) belonging to the Milan Radio
Commander which must be swapped into 2
new NSN BSCs (33357 and 33366). The “*”
notation means “all CGI”. So we define a 3:2
scenario where all sites will be moved with the
same CGI. The user can also specify a
different map between source and target CGI
(e.g. to change the LAC) row by row.
For internal use
As a third step the user can specify User
Defined parameters, creating one or more
User Sets, which can be assigned later to
group of cells.
DAISY assumes that most parameters are
already defined in PE templates: it doesn’t
handle all parameters but only the relevant
subset.
Basically there are 4 different operations

performed on parameters by DAISY:
Translation from ex-Siemens DB by means of a
mapping rule.
Calculated parameters: for some reason the value
cannot be translated from the ex-Siemens side, but
is calculated autonomously according to a rule.
User Defined (considered here): the user has to
define those parameters which either do not exist in
ex-Siemens network, or have different meaning,
and DAISY can not calculate it.
Synchronized: parameters having an
interdependency between different object in RNW
DB, and requiring a consistency check (e.g. in the
target object of the ADCE/ADJW)
For internal use

DAISY 2G SWAP: Parameters Mapping (1/2)
In the first stage the Parameter Mapping has been done at Object Level:
For internal use

DAISY 2G SWAP: Parameters Mapping (2/2)
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
For internal use

Now it is time to specify the ex-Siemens
BSC databases.
The user must provide at least each
ex-Siemens BSC written in the Cluster
Plan: BSC 1, 5, 30 in the example
below.
DAISY can read BSC databases in ACL

format (.asc/.acl). Since the identification
of the BSC using the internal MELId can
be ambiguous, all the requested files must All .asc/.acl files must
be stored in folder on Radio Commander be stored in a folder
(RC) basis. In our example all three files structure divided by
are located in a folder representing the Radio Commander.
Milan RC.
DAISY will ask the user to specify Note: Ex-Siemens BSC DBs available in “dba”
sequentially those folders. format must be converted into “asc” format
before using them in DAISY.
For internal use
After the import of all ex-Siemens BSCs the tool shows a log
window reporting a summary of all sites, cells, TRXs, and
neighbors read from them.
During the import phase, DAISY will also analyze some key
parameters in order to identify all the used TRS configurations.
For each .asc/.acl files, an Excel report file on BTSM, PCMB
and TRX basis is created. In addition a “configurations.xls”
file with a graphical representation of the TRS schema is
provided. All those files are stored in a new folder with the
following name convention: <date>-<time>-<BSC filename>
located in you Project folder.
Sites.xls
PCMBs.xls
Configurations.xls
TRXs.xls
For internal use

The “configurations.xls” report can be very useful to understand how the transmission part is
organized in the considered BSC for all the contained sites. It shows a diagram of all “chains”
(PCMs shared by several sites) including the number of sectors, TRXs, EDGE capabilities,
LAPD for TRX Signaling and O&M. The elements in the pictures are the most important ones for
the matching with the NSN TRS configurations defined with the “Configurations” button. In
particular please pay attention to the LAPD timeslots.
This report can be also used to define clusters: in the example below it makes sense to swap all
together BTSM 0, BTSM 1, BTSM 2 sharing PCM 0 and 18.
3 sites (BTSM 0, 1, 2) in a “drop”

configuration of 2 PCM (id=0 and 18).
BTSM 0 has 1 sector, 2 TRX (GE = the first
GSM/GPRS, the second EDGE). There are
one LAPD on the first timeslot of the PCM 0
(P0:T1) and another LAPD on first timeslot
of the PCM 18 (P18:T1).
BTSM 1: 1 sector, 3 TRX (GEG), LAPD on
second timeslot of PCM 0 and PCM 18
BTSM 2: 1 sector, 2 TRX (GE), LAPD on
timeslot 3 of both PCMs.
1 site (BTSM 3) in a “star” configuration on

PCM with id 1. The site has 3 sector with 2
TRX each (222). The EDGE is present on
the second TRX of each sector (GE GE GE).
LAPD is located on timeslot 1.
For internal use

In case the NSN BSC is not empty,
optionally the user can provide a Plan
Editor “.mdb” file containing already
integrated sites. In this way DAISY can
calculate correctly neighbors considering
the presence of those initial sites.
In case the user selects this option, the

successive “Synchronization” steps will
be performed to make some consistency
checks between ex-Siemens and NSN
DBs. Otherwise the user can skip them
pressing the corresponding buttons.
For internal use

The last step of the Plan
Definition is the Configuration
Pairing: here the user creates a
link between ex-Siemens TRS
schemas and NSN configurations
already prepared with the
“Configurations” button.
During the swap, TRS objects
(PCM, DAP, LAPD, partly TRX
objects) will be generated
according the selected NSN TRS
configuration.
It is possible to skip the selection
for some schemas: for all sites
that belong to an unmatched
schema only the radio part will
be generated by DAISY. It is
also possible to skip the selection
at all, pressing the “Skip” button
on the bottom of the window.
Finally, the “View NSN Conf.”
button can be used to open the
Configuration Editor, to review
possible matching
For internal use candidates.
After the Plan Definition wizard
ends, the main window will show
two panels containing all imported
objects from ex-Siemens (on the
left) and NSN (if provided, on the Source NW (ex-S) Target NW (NSN)
right).
The tree structure can be

expanded to analyze in details
imported sites, cells, TRXs,
neighbors, etc.
Also parameters, features, and
TRS information (relevant for the
swap mapping rules) can be
shown expanding the “Params”
nodes for the desired object.
For internal use

DAISY 2G Swap: Cluster Definition Phase
After the Plan Definition, usually performed
only once at the beginning, the user can swap
sites in clusters on daily basis.
To start the swap procedure, the first operation is the definition of the cluster by means of the
“Cluster Def.” button: DAISY will show a dialog window and the user can simply drag and drop
sites from the left side to the right one (or use “>” and “<“ controls).
Drag and
Drop of
sites to
define the
Cluster
For internal use

DAISY 2G Swap: Cluster Definition Phase
After the cluster building, it is possible to press the “OK”
button to generate the corresponding Cluster File in Excel
format (the tool will ask for the target location and the
filename).
Then MS Excel is started to open this file, to let the user to
fill the part not already prepared automatically by DAISY.
The Cluster File will represent the

input for the next Cluster Swap
phase: with it the user can provide
further user defined parameters
(on site or cell basis) and see
enabled ex-S features. The Cluster
File gives also the flexibility to
change feature implementation of
the swapping sites (orange
columns) and to “override”
Here it is possible to view a parameter values calculated using
commented template of the the “hard-coded” mapping rules
Microsoft Excel
Cluster File. Worksheet (blue columns).
For internal use
DAISY 2G Swap: Cluster File Example (1/5)
In the next slides an example of Cluster File filling will be shown in details.
Consider to swap the chain of PCM 0/18, shared
by the three sites BTSM 0, 1, and 2, (found in the
report file “Configurations.xls”). Assume that
this schema was already matched in the Plan
Definition phase with a “compatible” NSN
configuration made of 2 PCMs and 3 sites,
created in the Configurations phase.
In the Cluster Definition phase such cluster will

be built moving on the right BTSM 0, 1 and 2 with
the drag & drop.
The Cluster file below will be saved and directly

opened in Excel. At least the highlighted region
must be checked/filled by the user.
For internal use

About the radio part, the Cluster File can be filled simply
giving BTS Name, BTS nwName, and BTS maioOffset
(mandatory if SFH is enabled).
The BCF Name is calculated automatically by DAISY with an
increment of 3 or 6 (depending on the number of sectors)
checking for collisions. In our case DAISY generates the
following name correspondence:
BTSM 0 BCF 1
BTSM 1 BCF 4
BTSM 2 BCF 7
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
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
For internal use

To complete the Cluster File filling with the TRS part (in
red), we have to consider how the assigned NSN
configuration (on the left) is internally made.
The NSN configuration has 2 PCM and three sites, named
Site#1, Site#2, and Site#3, with one sector each, as can be
seen from with Configuration Editor (on the right).
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
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
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.
For internal use

The second step will involve User
Defined parameters, which are grouped
in User Sets.
The window is exactly the same already
presented in the Plan Definition phase,
and here it is shown again to let the user
the possibility to create or change
parameters contained in the User Sets,
specified in the Cluster File.
For internal use

The third “Swap” step
applies the internal
mapping rules and
calculates objects and
neighbors for sites of the
considered cluster.
Finally the fourth (and
last) “Export” step will
create RAML 2.0 xml files
for Plan Editor.
A global file containing all
objects to be created
(RAML_Delta_All.xml in
the shown example) and
single files per each
object type are generated.
In addition, after the first
cluster swap, DAISY can
also generate some
“delete” files, that must
be processed before the
standard “delta” files.
For internal use

All resulting files will be stored in a newly
created folder (located in the project folder)
named using current date, time and cluster
filename.
For internal use

In addition to the RAML 2.0 files for Plan
Editor, DAISY generates also some “.csv” files.
Fixed-OTHER-ADJ.csv This file contains

the neighbor relations that should be fixed in
the other-vendor databases.
Fixed-3G-ADJC.csv This file contains the

neighbor relations that should be fixed in the
3G network. The source cells are indicated
using MCC-MNC-RNDID-CELLID.
Fixed-ExS-ADJC.csv This file contains the

neighbor relations that should be fixed in the
ex-Siemens DB. A future version of the tool
should replace this csv file with CLI scripts, as
already done in DAISY for 3G Auto-swap.
For internal use

After the Cluster Swap, DAISY will show immediately the updated network state, both in the
left and right panels: red items represent deleted objects, green items are the created ones,
while yellow items are the objects changed by DAISY for some reason (e.g. to fix neighbors
that address newly swapped sites). Of course the user can also see any calculated values
expanding “Params” nodes in the right panel.
For internal use

DAISY 2G Swap: Plan Editor Data Upload
In order to upload generated RAML
2.0 files for the swapped cluster,
there is no need for the user to
manually run Plan Editor.
In fact DAISY has a dedicated window
to perform that task. The user can
select the “Data Upload” button and
gives few inputs, like Plan Editor file
path, the folder containing the DAISY
xml files just generated in the
previous Cluster Swap, the “plan” to
be created in Plan Editor.
Then pressing “Execute”, DAISY will
run Plan Editor in background, driving
the upload of all selected files.
At the end the user could check the
result of the operation using the log
panel at the bottom.
For internal use

DAISY 2G Swap: Plan Editor Data Export
At the same manner, in order to
export data from Plan Editor towards
NetAct, DAISY offers a dedicated
window.
The user can select the “Data
Export” button and gives all the
requested inputs: Plan Editor
installation path, Plan Editor plan
used in the previous “Data Upload”
procedure, the Export profile, and
the filename to be created.
Then pressing “Execute”, DAISY will
run Plan Editor in background to get
the desired export file.
For internal use

DAISY 2G Swap: Auxiliary Functions
Other auxiliary buttons on the

main toolbar allow to recall the
User Parameters manager, or
to re-open the Configuration
Pairing window (in order to
change or map new TRS
schemas).
In addition with the History
button the user can manually
create restore points before any
critical operation, and easily revert
the internal status of the tool to any previously saved
one. The tool is also able to create automatically restore
points (before any cluster swap) if the Auto Backup function is enabled.
For internal use
DAISY 2G Swap: Multi-Vendor Swap
During the Plan Definition phase, the user
can specify the Multi-Vendor swap type.
Selecting this option, DAISY will try to load
all the source BSC parameters
from a general Excel template
that replaces the ex-Siemens Microsoft Excel
Worksheet
ACL file.
Since DAISY can determine the swap
scenario and other information directly from
such template, the Plan Definition phase
will be simplified, requiring only the source
template and the optional Plan Editor DB,
with the consequent synchronization task.
For internal use

DAISY 2G Swap: Multi-Vendor Swap
After the end of the Multi-Vendor Plan Definition

phase, the main toolbar is slightly different: the “Cluster
Def.” button is no more present.
To perform the sites swap is sufficient only to press the
Cluster Swap button.
Also the Cluster file is no more

used, since all information to process
the cluster were read at the Plan
Definition time.
After the pressing of the Cluster
Swap button, DAISY will show the
Cluster Definition window and
immediately after the sites selection,
it will generate the Plan Editor data,
updating also its internal status.
For internal use

DAISY 2G Swap: Release Note
Supported features of the current version
- Direct import of ex-Siemens BSC in ACL format (.asc files), with identification of all TRS
configurations. Possibility to replace it with a general Excel template.
- BCF, BCF_TRE, BTS, TRX, ADCE, ADJW, POC, HOC, MAL, PCM, LAPD, DAP data
generation.
- AMR, Half Rate, AMR Half Rate, and Synthesized Frequency Hopping (w/o Dynamic MAIO
allocation) features mapping.
- Editor for the planning of the dynamic and compressed Abis configurations, with the possibility
to place up to four PCMs, allocation of sub-timeslots for MUX, EDAP, LAPD, and TRX objects.
Both “Star” and “Drop” configuration are supported.
Features available in the next versions
- Layering, Segments, GPRS/EDGE, BaseBand Hopping, DTX, Extended Cells, Dual Band, and
Concentric Cell features mapping.
- Enhancement of the GEMINI TRS part: automatic creation of NSN schemas in the Editor during
the initial “Configurations” phase by means of ACL “sample” files; usage of “larger” NSN
configuration to reduce the number of needed TRS configuration.
Limitations
- Synthesized Hopping with layering.
For internal use

DAISY License
Tool availability and licensing
DAISY is a dedicated module of MUSA tool. It can

be used in all WSE and Global projects.
To run the tool users need hardware dongles with

an expiration date. Licenses must be requested to
seppo.ripatti@nsn.com.
SW downloads, installation procedures, roadmap, MUSA

and other documentation, can be found on IMS at: HW Key
(2G Swap) https://sharenet-

ims.inside.nokiasiemensnetworks.com/Open/
409504014
(Other functionalities) https://sharenet-
ims.inside.nokiasiemensnetworks.com/Open/
395892487
For more information and support please contact:
leandro.palagiano@nsn.com
venanzio.traversa@nsn.com
For internal use


DAISY2GSWAP StepByStep

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

DAISY2GSWAP StepByStep

Uploaded by

Copyright:

Available Formats

DAISY for 2G SWAP

Step-by-Step User Guide

Leandro Palagiano, Venanzio Traversa, Ernesto Esposito

For internal use

DAISY 2G Swap Assumptions

For internal use

The first time you run the tool two choices

To create an empty project, when the

…and type your project name

For internal use

To select an already created or a

Then press “Finish” in the next

After the project selection, the

For internal use

In the following the view of the main MUSA toolbar is reported.

For internal use

DAISY for 3G Auto-Swap

DAISY for LACE (3G

DAISY for 2G Swaps

For internal use

DAISY “ideal” time-process:

For internal use

Using this button it is possible

For internal use

PCM frame: to TRX frame: to add

The grid gives a

For internal use

The Configuration control at the

Summary of the steps needed to create a new configuration

Examples of TRX-Sig placement in an

An example of O&M placement in an empty sub-timeslot. The “width” of

An example of EDAP placement:

For internal use

In the example above, we define 3 ex-S BSCs

Basically there are 4 different operations

For internal use

For internal use

For internal use

DAISY can read BSC databases in ACL

For internal use

3 sites (BTSM 0, 1, 2) in a “drop”

1 site (BTSM 3) in a “star” configuration on

For internal use

In case the user selects this option, the

For internal use

The tree structure can be

For internal use

For internal use

The Cluster File will represent the

In the Cluster Definition phase such cluster will

The Cluster file below will be saved and directly

For internal use

For internal use

For internal use

For internal use

For internal use

For internal use

Fixed-OTHER-ADJ.csv This file contains

Fixed-3G-ADJC.csv This file contains the

Fixed-ExS-ADJC.csv This file contains the

For internal use

For internal use