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 2 © 2010 Nokia Siemens Networks. All rights reserved.

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 3 © 2010 Nokia Siemens Networks. All rights reserved.

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 4 © 2010 Nokia Siemens Networks. All rights reserved.

. All rights reserved.MUSA-DAISY Startup: Project selection To select an already created or a new Project. Then press “Finish” in the next dialog window (you can ignore all controls since they are valid only for other MUSA modules). select the Project Name in the left panel. the MUSA environment is accessible and it will be possible to open the DAISY module. After the project selection. [Empty…] in the right panel. and press the “Empty” button. For internal use 5 © 2010 Nokia Siemens Networks.

MUSA-DAISY Startup: DAISY Module In the following the view of the main MUSA toolbar is reported. . All rights reserved. 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 6 © 2010 Nokia Siemens Networks.

. RU10.DAISY Modules: Main window DAISY module is composed by three parts or sub-modules DAISY for 3G Auto-Swap (RAS06. All rights reserved. Common Iub scenario) DAISY for LACE (3G data build creation for roll-out) DAISY for 2G Swaps For internal use 7 © 2010 Nokia Siemens Networks.

Ex-Siemens DB is provided in ACL format. which should be executed only once. Of course users can use the tool in a more “iterative” way. Planner must fill few data inputs. day by day. Plan Editor setting.DAISY 2G Swap: Phases Initial Configuration: discussion with the customer. time DAISY “ideal” time-process: complexity mostly placed in the two initial phases. All rights reserved. defining and mapping all configurations. The cluster can be easily defined graphically using the GUI. pairing configurations step by step. Plan Definition: the start of the BSC swap. DAISY is used to create TRS configurations. after each cluster swap. TRS planning considerations. For internal use 8 © 2010 Nokia Siemens Networks. Definition of the scenario. Cluster Swap: sites are swapped in clusters. .

DB Import/DB Export functions. to create. Listed here are all NSN TRS Configurations available for the site swap. All rights reserved. Using this button it is possible to close the page and return to the standard “network” view of DAISY. or delete items. Here the user can see all available configurations. modify. The Configurations button gives access to the NSN Configurations page. For internal use 9 © 2010 Nokia Siemens Networks. The user can import a set of already prepared configurations or creates them starting from scratch. This button opens the Configuration Editor. .DAISY 2G Swap: Configurations Phase Unfortunately TRS data objects can not be generated directly and automatically from the ex-Siemens counterpart. used to generate the TRS part for the swapping sites. useful in case of TRS configurations distribution among local offices/projects. as mostly happen for objects of the radio part.

to add all sites that belong to the configuration. which must be used to create/select items. All rights reserved. On the grid it is possible to place and see TRS objects. PCM frame: to add up to 4 PCM objects. . to specify the number of sectors for the selected site (in the frame above) The grid gives a “timeslot picture” for the selected PCM. TRX frame: to add TRXs needed by the selected site. For internal use 10 © 2010 Nokia Siemens Networks. Parameters frame. A timeslots representation of the selected PCM is given using colors for each kind of TRS object.DAISY 2G Swap: Configuration Editor (1/3) The Configuration Editor is divided in several frames. to see all available properties of the selected item. Cells frame. To close the Editor. LAPD/MUX frame: it can be used to specify MUX for the selected site. Sites frame.

. 3.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. 2 more TRXs on the second one. The save button stores changes and return to the read-only mode. 4. 6. a group of buttons permits to create new configurations and to change the editor from read-only to modify mode. and further 2 TRXs on the third and last one”. For internal use 11 © 2010 Nokia Siemens Networks. All rights reserved. Press the “+” button and select “+ Empty” Add as many PCMs as your configuration needs (PCM frame) Add all your sites (Sites frame) Selecting one site at time. Immediately on the right. 5. Finally the delete button can be used to erase unwanted configurations. create all the required sectors (Cells frame) Add TRXs for the selected site. the Editor is always set in read-only mode. for review or changes. At the beginning. 7. Summary of the steps needed to create a new configuration 1. Add all the MUX objects required by the selected site (LAPD/MUX frame) Select a PCM and right-click on the grid to place any TRS objects using the context menu tree. using for example the layout button present in the TRX frame: typing 222 for example means: “add 2 TRXs on the first sector. 2.

All rights reserved. right-click on the first sub-timeslot and from the context menu select the site and Traffic Channel type. Note: [COPY] means to map the channel type from the ex-Siemens one. An example of EDAP placement: selecting “Add…” the tool will asks for the number of TS (rows) which will be allocated for that object. The “width” of the object must be selected: 16 kbps (1 STL). .DAISY 2G Swap: Configurations Editor (3/3) To place a TRX on the PCM grid. 64 kbps (1 TS = 4STL). The O&M LAPD can be also inserted in an already existent MUX. A group of 8 sub-timeslots will be created. An example of O&M placement in an empty sub-timeslot. 32 kbps (2 STL). For internal use 12 © 2010 Nokia Siemens Networks. Examples of TRX-Sig placement in an empty sub-timeslot or in a MUX. the user can still change the channel type for each sub-timeslot. After the creation. A TRX-Sig can be added on a PCM only after the corresponding TRX has been placed.

and optionally an “. At the end of the process.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. The first step after the pressing of the Plan Definition button is the selection of the Swap Type: Siemens BR 9.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. TRX. LPDLM. . defined with the previous Configuration button. 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. All rights reserved. During this phase the user defines the swap type.0 NSN RG 10 Siemens BR 10. provides the source ex-Siemens DBs (in ACL format). BTSM. each ex-Siemens schemas can be mapped to the NSN one. For internal use 13 © 2010 Nokia Siemens Networks. All the collected information are also saved in some output reports for user reference. the scenario.mdb” file from Plan Editor. etc. DAISY analyzes input files to identify all the TRS configurations in terms of PCMB.

The “*” notation means “all CGI”. .g. The user can also specify a different map between source and target CGI (e.DAISY 2G Swap: Plan Definition Phase 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). we define 3 ex-S BSCs (1. 5. All rights reserved. The tool asks for an Excel file containing the so called Swap Plan: In the example above. 30) belonging to the Milan Radio Commander which must be swapped into 2 new NSN BSCs (33357 and 33366). to change the LAC) row by row. So we define a 3:2 scenario where all sites will be moved with the same CGI. For internal use 14 © 2010 Nokia Siemens Networks.

which can be assigned later to group of cells.DAISY 2G Swap: Plan Definition Phase As a third step the user can specify User Defined parameters. Basically there are 4 different operations performed on parameters by DAISY: Translation from ex-Siemens DB by means of a mapping rule. in the target object of the ADCE/ADJW) For internal use 15 © 2010 Nokia Siemens Networks.g. but is calculated autonomously according to a rule. and requiring a consistency check (e. User Defined (considered here): the user has to define those parameters which either do not exist in ex-Siemens network. DAISY assumes that most parameters are already defined in PE templates: it doesn’t handle all parameters but only the relevant subset. Calculated parameters: for some reason the value cannot be translated from the ex-Siemens side. or have different meaning. creating one or more User Sets. Synchronized: parameters having an interdependency between different object in RNW DB. and DAISY can not calculate it. . All rights reserved.

All rights reserved. .DAISY 2G SWAP: Parameters Mapping (1/2) In the first stage the Parameter Mapping has been done at Object Level: For internal use 16 © 2010 Nokia Siemens Networks.

All rights reserved. AMR_HR). AMR_POC. Dynamic SFH.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. • Half Rate For internal use 17 © 2010 Nokia Siemens Networks. BBH). . • Hopping (SFH.

asc/.acl files must be stored in a folder structure divided by Radio Commander. . 5. All rights reserved. For internal use 18 © 2010 Nokia Siemens Networks. Since the identification of the BSC using the internal MELId can be ambiguous. All . all the requested files must be stored in folder on Radio Commander (RC) basis. The user must provide at least each ex-Siemens BSC written in the Cluster Plan: BSC 1.DAISY 2G Swap: Plan Definition Phase Now it is time to specify the ex-Siemens BSC databases. In our example all three files are located in a folder representing the Milan RC. DAISY will ask the user to specify sequentially those folders. DAISY can read BSC databases in ACL format (.asc/.acl). Note: Ex-Siemens BSC DBs available in “dba” format must be converted into “asc” format before using them in DAISY. 30 in the example below.

In addition a “configurations.acl files.xls TRXs.asc/. During the import phase. . Sites. cells.xls” file with a graphical representation of the TRS schema is provided. PCMB and TRX basis is created.xls For internal use 19 © 2010 Nokia Siemens Networks.xls Configurations.DAISY 2G Swap: Plan Definition Phase After the import of all ex-Siemens BSCs the tool shows a log window reporting a summary of all sites. All rights reserved. TRXs. and neighbors read from them. For each . an Excel report file on BTSM. DAISY will also analyze some key parameters in order to identify all the used TRS configurations. All those files are stored in a new folder with the following name convention: <date>-<time>-<BSC filename> located in you Project folder.xls PCMBs.

2 TRX (GE). The EDGE is present on the second TRX of each sector (GE GE GE). The site has 3 sector with 2 TRX each (222). BTSM 1: 1 sector. BTSM 1. LAPD is located on timeslot 1. 2 TRX (GE = the first GSM/GPRS. LAPD on second timeslot of PCM 0 and PCM 18 BTSM 2: 1 sector. BTSM 2 sharing PCM 0 and 18.DAISY 2G Swap: Plan Definition Phase The “configurations. This report can be also used to define clusters: in the example below it makes sense to swap all together BTSM 0. 2) in a “drop” configuration of 2 PCM (id=0 and 18). EDGE capabilities. 1. For internal use 20 © 2010 Nokia Siemens Networks. 3 sites (BTSM 0. TRXs. 3 TRX (GEG). BTSM 0 has 1 sector. 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. 1 site (BTSM 3) in a “star” configuration on PCM with id 1. All rights reserved. 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). LAPD on timeslot 3 of both PCMs. .xls” report can be very useful to understand how the transmission part is organized in the considered BSC for all the contained sites. the second EDGE). LAPD for TRX Signaling and O&M. It shows a diagram of all “chains” (PCMs shared by several sites) including the number of sectors.

Otherwise the user can skip them pressing the corresponding buttons. the successive “Synchronization” steps will be performed to make some consistency checks between ex-Siemens and NSN DBs. For internal use 21 © 2010 Nokia Siemens Networks.mdb” file containing already integrated sites. optionally the user can provide a Plan Editor “. In case the user selects this option. .DAISY 2G Swap: Plan Definition Phase In case the NSN BSC is not empty. In this way DAISY can calculate correctly neighbors considering the presence of those initial sites. All rights reserved.

TRS objects (PCM. All rights reserved. During the swap. to review possible matching candidates. Finally.” button can be used to open the Configuration Editor. It is also possible to skip the selection at all. partly TRX objects) will be generated according the selected NSN TRS configuration. pressing the “Skip” button on the bottom of the window. .DAISY 2G Swap: Plan Definition Phase 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. DAP. the “View NSN Conf. For internal use 22 © 2010 Nokia Siemens Networks. 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. LAPD.

DAISY 2G Swap: Plan Definition Phase After the Plan Definition wizard ends. cells. All rights reserved. Also parameters. neighbors. For internal use 23 © 2010 Nokia Siemens Networks. . features. TRXs. and TRS information (relevant for the swap mapping rules) can be shown expanding the “Params” nodes for the desired object. the main window will show two panels containing all imported objects from ex-Siemens (on the left) and NSN (if provided. etc. on the right). Source NW (ex-S) Target NW (NSN) The tree structure can be expanded to analyze in details imported sites.

All rights reserved.” 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). usually performed only once at the beginning.DAISY 2G Swap: Cluster Definition Phase After the Plan Definition. . Drag and Drop of sites to define the Cluster For internal use 24 © 2010 Nokia Siemens Networks. the first operation is the definition of the cluster by means of the “Cluster Def. the user can swap sites in clusters on daily basis. To start the swap procedure.

to let the user to fill the part not already prepared automatically by DAISY.DAISY 2G Swap: Cluster Definition Phase After the cluster building. Then MS Excel is started to open this file. For internal use 25 © 2010 Nokia Siemens Networks. . All rights reserved. Here it is possible to view a commented template of the Cluster File. The Cluster File gives also the flexibility to change feature implementation of the swapping sites (orange columns) and to “override” parameter values calculated using the “hard-coded” mapping rules (blue columns). 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). Microsoft Excel Worksheet 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.

and 2. (found in the report file “Configurations. All rights reserved. In the Cluster Definition phase such cluster will be built moving on the right BTSM 0.xls”). 1. . For internal use 26 © 2010 Nokia Siemens Networks. shared by the three sites BTSM 0. 1 and 2 with the drag & drop. Assume that this schema was already matched in the Plan Definition phase with a “compatible” NSN configuration made of 2 PCMs and 3 sites.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. created in the Configurations phase. At least the highlighted region must be checked/filled by the user. The Cluster file below will be saved and directly opened in Excel.

Since the LAC is a parameter on BTS basis. To force that parameter. the LAC will be changed (usually LAC is copied from exSiemens DB). In our case DAISY generates the following name correspondence: BTSM 0 BTSM 1 BTSM 2 BCF 1 BCF 4 BCF 7 However. BTS nwName. the Cluster File can be filled simply giving BTS Name. Finally. Syntax for “parameter override”: (OBJ) <param. in case the project requires a different rule. a new column is added in the blue area using the correct NSN parameter name (as it is indicated in the Plan Editor dictionary). The LAC will be changed as follow: 30104 10104. the User Set parameter can be modified in order to assign to each site the desired User Defined parameters (basically Plan Editor templates for each objects). and BTS maioOffset (mandatory if SFH is enabled). values must be written in the “white” rows (cell type rows) and not in the “green” ones (site type rows). The BCF Name is calculated automatically by DAISY with an increment of 3 or 6 (depending on the number of sectors) checking for collisions.DAISY 2G Swap: Cluster File Example (2/5) About the radio part. to show a possible mapping rule override. In addition.name> (<optional index for sub-cell obj>) . All rights reserved. For internal use 27 © 2010 Nokia Siemens Networks. the user can freely overwrite and change the BCF Name.

The user can change the implemented NSN feature deleting or adding the “*” character. . All rights reserved. DAISY indicates the features activated for each site in the ex-Siemens DB. This part is read-only. Features mapping between ex-Siemens and NSN sides For internal use 28 © 2010 Nokia Siemens Networks. The orange part gives a mapping with the features available in the NSN side and supported by DAISY. and is reported for user reference. now the yellow and orange area of the Cluster File will be described. The “*” character means that the corresponding feature was found “active” for the BTSM or for the BTS objects. In the yellow part. The activation of an NSN feature will change the internal mapping rules for the involved parameters.DAISY 2G Swap: Cluster File Example (3/5) To complete the radio part.

For internal use 29 © 2010 Nokia Siemens Networks. the second TRX with EDGE capabilities is located on the second PCM. with one sector each. we have to consider how the assigned NSN configuration (on the left) is internally made. Signaling is present on the first timeslot of each PCM. Site#2. as can be seen from with Configuration Editor (on the right). First PCM Second PCM Site#1 has 2 TRXs. For that reason EDAP for Site#1 is located on the second PCM too. Site#2 and Site#3 have the EDGE TRXs (TRX#2) on the first PCM. All rights reserved. named Site#1. The NSN configuration has 2 PCM and three sites. and Site#3. For each site there are two MUX objects with O&M and TRX-SIG. The first TRX (Site#1 – TRX#1) is located on the first PCM. where is located also the Site#2 – EDAP and Site#3 EDAP.DAISY 2G Swap: Cluster File Example (4/5) To complete the Cluster File filling with the TRS part (in red). . The position of the LAPD are the same indicated in the ex-Siemens schema.

A For internal use 30 © 2010 Nokia Siemens Networks.” column is used to create this link.DAISY 2G Swap: Cluster File Example (5/5) To summarize. Columns “PCM ID 1” and “PCM ID 2” can be used to provide the information. The “Config Site No. Their DAP ID must be indicated in the “DAP ID (PCM 1)” column. For that reason the DAP ID must be filled using “DAP ID (PCM 2)” column. etc. (C) BCF 1 (= Site#1 of the NSN configuration) has its TRX#2 with EDGE on the second PCM. we need the PCM ID for the first PCM and PCM ID for the second one. (D) BCSU-PCUs follow the same rule applied at point (C). All rights reserved. where is also located its EDAP (Site#1 – EDAP). 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. B C D . (B) Since our NSN configuration has two PCMs. the Site#2. BCF 4 (=Site#2) and BCF 7 (=Site#3) have TRX#2 with EDGE and EDAP on the first PCM.

. Firstly.0 file format. A log window will give a feedback on any errors found.DAISY 2G Swap: Cluster Swap Phase After the filling of the Cluster File generated in the previous Cluster Definition phase. For internal use 31 © 2010 Nokia Siemens Networks. the tool will asks for the Cluster File. it will be finally possible to generate Plan Editor data in RAML 2. By pressing the Cluster Swap button the swap wizard will be shown to guide the user in all required steps. All rights reserved.

The window is exactly the same already presented in the Plan Definition phase. For internal use 32 © 2010 Nokia Siemens Networks.DAISY 2G Swap: Cluster Swap Phase The second step will involve User Defined parameters. All rights reserved. which are grouped in User Sets. specified in the Cluster File. and here it is shown again to let the user the possibility to create or change parameters contained in the User Sets. .

A global file containing all objects to be created (RAML_Delta_All. For internal use 33 © 2010 Nokia Siemens Networks. that must be processed before the standard “delta” files. DAISY can also generate some “delete” files. after the first cluster swap.xml in the shown example) and single files per each object type are generated. In addition.DAISY 2G Swap: Cluster Swap Phase 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. . All rights reserved.0 xml files for Plan Editor.

time and cluster filename. For internal use 34 © 2010 Nokia Siemens Networks. .DAISY 2G Swap: Cluster Swap Phase All resulting files will be stored in a newly created folder (located in the project folder) named using current date. All rights reserved.

For internal use 35 © 2010 Nokia Siemens Networks. The source cells are indicated using MCC-MNC-RNDID-CELLID. DAISY generates also some “.csv This file contains the neighbor relations that should be fixed in the other-vendor databases. A future version of the tool should replace this csv file with CLI scripts. Fixed-3G-ADJC.csv” files. . All rights reserved. Fixed-ExS-ADJC.0 files for Plan Editor.csv This file contains the neighbor relations that should be fixed in the 3G network. Fixed-OTHER-ADJ.csv This file contains the neighbor relations that should be fixed in the ex-Siemens DB.DAISY 2G Swap: Cluster Swap Phase In addition to the RAML 2. as already done in DAISY for 3G Auto-swap.

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

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

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

or to re-open the Configuration Pairing window (in order to change or map new TRS schemas).DAISY 2G Swap: Auxiliary Functions Other auxiliary buttons on the main toolbar allow to recall the User Parameters manager. and easily revert the internal status of the tool to any previously saved one. All rights reserved. . For internal use 39 © 2010 Nokia Siemens Networks. The tool is also able to create automatically restore points (before any cluster swap) if the Auto Backup function is enabled. In addition with the History button the user can manually create restore points before any critical operation.

requiring only the source template and the optional Plan Editor DB. All rights reserved.DAISY 2G Swap: Multi-Vendor Swap During the Plan Definition phase. For internal use 40 © 2010 Nokia Siemens Networks. with the consequent synchronization task. . Selecting this option. the user can specify the Multi-Vendor swap type. DAISY will try to load all the source BSC parameters from a general Excel template Microsoft Excel that replaces the ex-Siemens Worksheet ACL file. the Plan Definition phase will be simplified. Since DAISY can determine the swap scenario and other information directly from such template.

For internal use 41 © 2010 Nokia Siemens Networks. Also the Cluster file is no more used. DAISY will show the Cluster Definition window and immediately after the sites selection. To perform the sites swap is sufficient only to press the Cluster Swap button. it will generate the Plan Editor data. since all information to process the cluster were read at the Plan Definition time.” button is no more present. All rights reserved. . updating also its internal status.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. After the pressing of the Cluster Swap button.

BaseBand Hopping. Extended Cells. MAL. with the possibility to place up to four PCMs.Synthesized Hopping with layering. ADCE. POC. usage of “larger” NSN configuration to reduce the number of needed TRS configuration. Possibility to replace it with a general Excel template. BCF_TRE.Layering. .BCF. DAP data generation.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. Features available in the next versions .DAISY 2G Swap: Release Note Supported features of the current version . LAPD.asc files). and Concentric Cell features mapping. .Direct import of ex-Siemens BSC in ACL format (. ADJW. LAPD. For internal use 42 © 2010 Nokia Siemens Networks. . EDAP. . GPRS/EDGE. Segments. with identification of all TRS configurations. AMR Half Rate. and Synthesized Frequency Hopping (w/o Dynamic MAIO allocation) features mapping. Both “Star” and “Drop” configuration are supported. HOC. BTS. TRX. . Half Rate. allocation of sub-timeslots for MUX. PCM.AMR. DTX. Dual Band. and TRX objects. Limitations . All rights reserved.Editor for the planning of the dynamic and compressed Abis configurations.

.com/Open/ 395892487 For more information and support please contact: leandro. It can be used in all WSE and Global projects.com venanzio.com/Open/ 409504014 (Other functionalities) https://sharenetims.com. SW downloads.com MUSA HW Key For internal use 43 © 2010 Nokia Siemens Networks. installation procedures.palagiano@nsn.traversa@nsn. roadmap. All rights reserved.nokiasiemensnetworks.nokiasiemensnetworks. Licenses must be requested to seppo.DAISY License Tool availability and licensing DAISY is a dedicated module of MUSA tool. can be found on IMS at: (2G Swap) https://sharenetims. and other documentation. To run the tool users need hardware dongles with an expiration date.ripatti@nsn.inside.inside.

Sign up to vote on this title
UsefulNot useful