FSAN

Introduction

Setting the working directory of MATLAB to this directory and typing startup <ENTER>  will automatically set up the search paths for MATLAB properly and make it possible to run any of the SDSL simulation examples.

To have a look on the source code of the program files, please click on the file's name in the corresponding pragraph title.

ExSDSLmargin:

This example routine computes the resulting noise margin at LT and NT side of SDSL transmissions for a given topology and traffic scenario.

In the 'Parameter Setup Section' following the file header a the following parameters must be set to define the needed input parameters for the simulation run:

• Modification of ex struct (ex.tfplist, ex.lclist, ex.clist) according to the used scenario.
• Noise model to be applied (ex.param.NoiseModel), predefined or ‘Calculate’.
• Definition of modems to be evaluated in the experiment (ex.param.modemlist)
• gui.ttlist to set up a list of scenarios regarding traffic and topology.
• scenario to select a specific scenario from the list.
• Switch variables plotit and plot_detail to define the format of graphical output

Execution steps:

1. Adding linecodes and tfps for each service contained in the scenario to ex.lclist and ex.tfplist  (transmit PSD of SDSL service depends on bitrate) by calling ETSI_SDSL_traffic2lctf.
2. Evaluation of  the experiment by calling evalExperiment.
3. Evaluation of resulting margin by calling calcXDSLresult.
4. Numerical results (margin of the considered services) are shown in the Command Window
5. Optional showing details of experiment (switch plotit in ‘Set up Parameter section’) graphically 

ExSDSLmaxrate:

Computes the maximum possible bitrate for a specific SDSL modem in a given traffic/topology  scenario.

In the 'Parameter Setup Section' following the file header a the following parameters must be set to define the needed input parameters for the simulation run:

• Modification of ex struct (ex.tfplist, ex.lclist, ex.clist) according to the used scenario.
• Noise model to be applied (ex.param.NoiseModel), predefined or ‘Calculate’.
• Definition of modems to be evaluated in the experiment (ex.param.modemlist). The name of the considered modem must not contain the ‘bitrate-indication-section’ at the end of the name (for structure of names of SDSL services, see also description of UserLoopsSDSL)
• gui.ttlist to set up a list of scenarios regarding traffic and topology.
• scenario to select a specific scenario from the list.
• target_margin defines target margin (including implementation loss) to be met for calculation of maximum bitrate.
• bitrate_range defines the range and the stepwidth of bitrates used  for the iteration process.

Execution steps:

1. Show traffic and topology graph of considered scenario
2. Iteratively searching for the bitrate which meets the defined target margin, using ETSI_SDSL_traffic2lctf,evalExperiment, and calcXDSLresult.
3. Numerical results (margin of the considered services) are shown in the Command Window

ExSDSLreach:

Computes the maximum possible looplength for a  SDSL service on a cable section (only one cable type between CO and a single NT point).

In the 'Parameter Setup Section' following the file header a the following parameters must be set to define the needed input parameters for the simulation run:

• Modification of ex struct (ex.tfplist, ex.lclist, ex.clist) according to the used scenario.
• Noise model to be applied (ex.param.NoiseModel), predefined or ‘Calculate’.
• Definition of modems to be evaluated in the experiment in ex.param.modemlist (for structure of names of SDSL services, see also description of UserLoopsSDSL).
• gui.ttlist to set up a list of scenarios regarding traffic and topology.
• scenario to select a specific scenario from the list.
• target_margin defines target margin (including implementation loss) to be met for calculation of maximum possible looplength.
• start_len defines the start value for the length-iteration process.

Execution steps:

1. Adding linecodes and tfps for each service contained in the scenario to ex.lclist and ex.tfplist  (transmit PSD of  SDSL service depends on bitrate) by calling ETSI_SDSL_traffic2lctf.
2. Iteratively searching for the looplength which meets the defined target margin, using evalExperiment, and calcXDSLresult.
3. Show the result numerically in the Command Window and graphically in the topology graph

ExSDSLtestloop:

Computes the resulting margin of a SDSL transmission on an ETSI testloop.

In the 'Parameter Setup Section' following the file header a the following parameters must be set to define the needed input parameters for the simulation run:

• Modification of ex struct (ex.tfplist, ex.lclist, ex.clist) according to the used scenario.
• Noise model to be applied (ex.param.NoiseModel), predefined or ‘Calculate’.
• Definition of modems to be evaluated in the experiment in ex.param.modemlist.
• gui.ttlist to set up the list of ETSI Testloops.
• scenario to select a specific testloop from the list.
• testlooplen length of selected testloop in meters.
• Switch variables plotit and plot_detail to define the format of graphical output.

Execution steps:

1. Adding linecodes and tfps for each service contained in the scenario to ex.lclist and ex.tfplist  (transmit PSD of  SDSL service depends on bitrate) by calling ETSI_SDSL_traffic2lctf.
2. Evaluation of  the experiment by calling evalExperiment.
3. Evaluation of resulting margin by calling calcXDSLresult.
4. Numerical Results (margin of the considered services) are shown in the Command Window.
5. Optional graphically showing details of experiment (switch plotit in ‘Set up Parameter section’)

SDSLIL(loopno,frequ,len):

Computes the insertion loss of  ETSI SDSL testloop loopno of given length len  at a defined frequency frequ. Uses function getIL  from the main simulator files for calculation of loop attenuation.  

UserloopsSDSL:

This is an example-file for definitions of traffic and topology scenarios for SDSL simulations. In principal the same format for traffic and topology definition as defined in the main simulator description holds also for SDSL simulations. The only exception is the naming of the SDSL services in the traffic struct (the naming of services others than SDSL are not affected).

• for scenarios analysed with ExSDSLmargin: SDSL service names must contain full information on PSD used (symmetric or asymmetric) and bitrate as shown exemplarily in the following :

‘SDSL-sym-512’ (e.g. for symmetric SDSL at 512 kBps)
‘SDSL-asym-2048’ (e.g. for asymmetric SDSL at 2048 kBps)
‘SDSL-sym-2304’ (e.g. for asymmetric SDSL at 2304 kBps)

• for scenarios analysed with ExSDSLmaxrate: SDSL service names must contain full information on PSD used (symmetric or asymmetric) and must not indicate a bitrate as shown exemplarily in the following :

‘SDSL-sym’ (e.g. for analysing symmetric SDSL)
‘SDSL-asym’ (e.g. for analysing asymmetric SDSL)

• for scenarios analysed with ExSDSLreach: same as mentioned for ExSDSLmargin, if a looplength is given in the topology struct it will be ignored.