DIRECT User Reference Guide

DIRECT User Reference Guide
Software Version 6.0 Reference Guide Edition 1
Copyright 2007 AIRCOM International All rights reserved ADVANTAGE, ASSET3G, CONNECT, DATASAFE, ENTERPRISE, NEPTUNE, HOMEZONE, OPTIMA, OSSEXPERT, TARGET and WEBWIZARD are recognised trademarks of AIRCOM International. Other product names are trademarks of their respective companies. Microsoft Excel , .NET, Microsoft Office, Outlook , Visual Basic Windows, Windows XP and Word are trademarks of the Microsoft Corporation. This documentation is protected by copyright and contains proprietary and confidential information. No part of the contents of this documentation may be disclosed, used or reproduced in any form, or by any means, without the prior written consent of AIRCOM International. Although AIRCOM International has collated this documentation to reflect the features and capabilities supported in the software products, the company makes no warranty or representation, either expressed or implied, about this documentation, its quality or fitness for particular customer purpose. Users are solely responsible for the proper use of ENTERPRISE software and the application of the results obtained. An electronic version of this document exists. This User Reference Guide finalised on 16 May 2007. Refer to the Online Help for more information. This User Reference Guide prepared by: AIRCOM International Ltd Cassini Court Randalls Research Park Randalls Way Leatherhead Surrey KT22 7TW Telephone: Support Hotline: Fax: Web: +44 (0) 1932 442000 +44 (0) 1932 442345 +44 (0) 1932 442005 www.aircominternational.com
Contents
Chapter 1 Introduction 13
Obtaining User Assistance ............................................................................... 14
Who is This User Reference Guide For? ................................................................... 15 About the ENTERPRISE User Reference Guides .................................................... 15 Can You Improve Our User Assistance? ................................................................... 16 Obtaining Support ...................................................................................................... 17 Obtaining Further Information and Services .............................................................. 18
Chapter 2 About the DIRECT User Interface
21
Opening DIRECT in the ENTERPRISE Suite ................................................... 21 About the DIRECT Global Toolbar ................................................................... 22 About the DIRECT Routing Toolbar ................................................................. 23 About the DIRECT Modules ............................................................................. 24
About the Transmission Module ................................................................................ 24 About the Traffic Module............................................................................................ 28 About the SDH Module .............................................................................................. 36 About the PDH Module .............................................................................................. 38 About the ATM Module .............................................................................................. 41 About the IP Module .................................................................................................. 43 About the Lightpath Module ....................................................................................... 45
About the DIRECT Equipment Editor ............................................................... 46 About the Views Browser ................................................................................. 47 About the Network Browser ............................................................................. 47 About the Task Pane ....................................................................................... 48
Chapter 3 Getting Started in DIRECT
51
About the Network Planning Process ............................................................... 52

About Planning Using the DIRECT Modules ............................................................. 53
Synchronising DIRECT with ASSET3G/CONNECT ......................................... 54

Performing Synchronisation in DIRECT .................................................................... 55 Configuring Synchronisation Object Options ............................................................. 58 Editing the Synchronisation Analysis Results ........................................................... 59 How Does Synchronisation Work? ............................................................................ 59
About DIRECT's Generic Functions ................................................................. 60 Setting the Plan Preferences ........................................................................... 61
Setting How Equipment is Added .............................................................................. 62 Setting How Detail Edges are Added ........................................................................ 64 Setting the Edge Type Used in Network Plans ......................................................... 65 Setting How Items are Displayed .............................................................................. 65 Setting How Network Elements Are Selected ........................................................... 65
Using the Views Browser ................................................................................. 66

Adding and Deleting Modules .................................................................................... 66 Adding and Deleting Module Views ........................................................................... 67 DIRECT User Reference Guide Version 6.0 Page 5
Viewing Module Windows .......................................................................................... 68
Adding Equipment Nodes in the Module Window............................................. 68

Viewing and Editing the General Properties of Equipment Nodes ............................ 69 Viewing the Cross Connections of Equipment Nodes ............................................... 70
Editing Equipment............................................................................................ 70
Editing Equipment Using Editing Commands ............................................................ 70 Deleting Equipment ................................................................................................... 70
Adding Connecting Edges ............................................................................... 71

Adding Edges in the Module Window Using the Module Toolbar ............................. 71 Adding Edges in the Module Window Using the Context Menu ................................ 72 Adding Edges in the Edge Group Dialog Box ........................................................... 73 Adding Edges to an Edge Group in the Network Browser ........................................ 73 Adding Edges to a Layer in the Network Browser ..................................................... 74 Deleting Edges .......................................................................................................... 76 About Compatibility Between Connections and Conduits ......................................... 76 Viewing and Editing the General Properties of an Edge Group or Edge .................. 76
Controlling the Display ..................................................................................... 77

Selecting Items in the Module Window...................................................................... 77 Locating Network Elements and Edges ..................................................................... 78 Arranging Equipment ................................................................................................. 79 Aligning Equipment .................................................................................................... 80 Arranging Edges ........................................................................................................ 81 Showing and Hiding Layers and Edge Groups ......................................................... 81 Displaying Edges and Nodes Based On Properties, Cabinets or Equipment ........... 82 Colouring Edges Based on their Attributes................................................................ 82 Assigning Network Labels in Module Windows ......................................................... 83
About Displaying Data in Module Views ........................................................... 84

Zooming In and Out on the Module View .................................................................. 84 Resizing a Network Plan............................................................................................ 85 Redrawing the Module Window ................................................................................. 86 Showing and Hiding Properties and Cabinets ........................................................... 86 Creating Module Views Based on Routes ................................................................. 87
About Using the Task Pane ............................................................................. 87

Using the Automatic Topology Generator ................................................................. 87 Exporting and Importing in DIRECT .......................................................................... 91 Using Reports in DIRECT .......................................................................................... 94 Printing Network Plans ............................................................................................ 100 Committing Network Elements in DIRECT .............................................................. 101 Committing, Restoring and Deleting Networks and Layers ..................................... 102 Creating and Using Regions .................................................................................... 103
Chapter 4 Creating and Using Equipment
105
About the DIRECT Equipment Editor ............................................................. 107 About Equipment in DIRECT ......................................................................... 108 Creating New Logical Traffic Equipment Types ............................................. 109
Creating Logical Traffic Equipment Types Based On Existing Ones ...................... 110 About the Additional Parameters Tabs for Logical Traffic Equipment ..................... 110
Creating Logical Transport Equipment Types ................................................ 111

About the Additional Parameters Tabs For Logical Transport Equipment .............. 112
Creating Physical Element Types .................................................................. 115

Setting the General Properties for Physical Element Types ................................... 116 Setting the Traffic/Transport Functionality for Physical Element Types .................. 117 Page 6 DIRECT User Reference Guide Version 6.0
Setting the Transport Interface (Edge) Compatibility for Physical Element Types.. 118 Defining Ports for Physical Element Types ............................................................. 118 Configuring Slots for Subrack Types ....................................................................... 119 Configuring Subracks for Multi-subrack Types ........................................................ 119 Configuring Passive Equipment Parameters ........................................................... 120 Creating Cabinet Templates .................................................................................... 120 Creating SubRack Templates .................................................................................. 121 Creating MultiSubRack Templates .......................................................................... 121
Making Global Changes to Equipment ........................................................... 122 Using the Equipment Browser........................................................................ 124
Viewing Equipment in the Equipment Browser ....................................................... 124 Adding Equipment to a Network Using the Equipment Browser ............................. 124
Locating Equipment ....................................................................................... 125
Chapter 5 Creating the Transmission Network 127

Overview of the Transmission Module ........................................................... 128 Using the Equipment View of the Transmission Module................................. 133
Viewing and Editing the Transmission Properties of Equipment ............................. 133 Editing Edges in the Transmission Module ............................................................. 138
Using the Property View of the Transmission Module .................................... 143

Adding Properties .................................................................................................... 144 Adding Conduit Pits ................................................................................................. 144 About Conduits ........................................................................................................ 145 Editing Properties .................................................................................................... 146 Editing Conduit Pits ................................................................................................. 148 Editing Conduits ....................................................................................................... 148
Using the Detail View of the Transmission Module ........................................ 149

Creating Detail Views Based on Properties............................................................. 149 About Equipment in the Detail View of the Transmission Module ........................... 149 Connecting Detail Equipment Nodes ....................................................................... 150 Viewing and Editing Detail Equipment Nodes ......................................................... 151
Creating the Optical Network ......................................................................... 151
Chapter 6 Creating the Traffic Network 153

Overview of the Traffic Module Cellular Layer ................................................ 154 Setting Default Parameters for Traffic ............................................................ 156
Setting Cellular Traffic Parameters .......................................................................... 157 Setting PSTN Traffic Parameters ............................................................................ 159 Setting the TETRA Traffic Parameters .................................................................... 160 Setting the Interswitch Traffic Default Parameters .................................................. 161 Setting the Signalling Traffic Parameters ................................................................ 167 Setting the Default Parameters for Traffic Interface Edges ..................................... 172
Adding Traffic Services and Types ................................................................ 172

Editing Traffic Services ............................................................................................ 173 Editing Traffic Types ................................................................................................ 176
Adding Traffic to DIRECT Equipment............................................................. 177

Adding Traffic to BSCs ............................................................................................ 177 Adding Traffic to BTSs ............................................................................................. 177 Adding Traffic to Node Bs ........................................................................................ 180
Viewing and Editing the Traffic Properties of Equipment ................................ 181

DIRECT User Reference Guide Version 6.0 Page 7
Adding Cells to Node Bs .......................................................................................... 181 Allocating Subscribers to SMSCs ............................................................................ 181 Assigning Codec Usage Percentages to Equipment............................................... 181 Assigning Served External Networks ...................................................................... 185 Creating EDAP Pools for GPRS Data ..................................................................... 185 Defining and Using Your Own Interswitch Traffic Values ........................................ 187 Defining Preferred Nodes for Interswitch and Signalling Traffic .............................. 188 Creating Supported Services ................................................................................... 190 Viewing and Editing Dispatcher Systems on a DSC ............................................... 191 Viewing and Editing ISW Node Parameters ............................................................ 192 Viewing and Editing Isw Voice Traffic Parameters .................................................. 192 Viewing and Editing Prepay Parameters ................................................................. 193 Viewing and Editing MSC Traffic Properties............................................................ 193 Viewing and Editing PSTN Traffic Properties .......................................................... 194 Viewing and Editing RNC User Plane Traffic .......................................................... 194 Viewing and Editing Signalling Node Parameters ................................................... 195 Viewing and Editing Signalling Traffic Parameters .................................................. 195 Viewing and Editing TETRA Cells and TRXs .......................................................... 195 Viewing DXT Node Information ............................................................................... 196 Viewing (E)GPRS Traffic Results ............................................................................ 196 Viewing MGW Served Connections ........................................................................ 197 Viewing SGSN-3G Served Connections ................................................................. 197 Viewing the Routing Table for Traffic ...................................................................... 197 Viewing WMSC Served Connections ...................................................................... 197
Overview of the Traffic Module Signalling Layer ............................................ 198

Creating the Signalling Traffic Network ................................................................... 198 Defining Signalling Traffic Services and Protocols .................................................. 198 Generating Signalling Traffic ................................................................................... 213
Overview of the Traffic Module Interswitch Layer ........................................... 215

Creating the Interswitch Traffic Network .................................................................. 217
Creating a 3GPP Network .............................................................................. 224

Using IWFs in 3GPP Networks ................................................................................ 224
Creating the TETRA Traffic Network .............................................................. 225

About the TETRA Network Architecture .................................................................. 225
Using Protocol Stacks .................................................................................... 226

Creating a Protocol Stack ........................................................................................ 227 Creating Header Types............................................................................................ 235 Assigning Protocol Stacks to Traffic Interfaces ....................................................... 235 Testing Protocol Stacks ........................................................................................... 236
Planning a GPRS Network Using DIRECT..................................................... 237 Planning a Prepay Network Using DIRECT ................................................... 238
Chapter 7 Routing The Network in DIRECT
241
About the DIRECT Routing Model ................................................................. 243 About Network Routing .................................................................................. 244
About Shortest Path First Routing ........................................................................... 244 About Double Path Routing ..................................................................................... 245 About Balanced Capacity Routing ........................................................................... 248 About Balanced Fill Ratio Routing ........................................................................... 249 About Nominal and Detailed Capacity Routing ....................................................... 250 About Conduit Diverse Routing ............................................................................... 251
Setting the Routing Parameters ..................................................................... 253

Page 8 DIRECT User Reference Guide Version 6.0
Setting the Routing Target Module Layers .............................................................. 253 Setting the Target Layer Routing Weights ............................................................... 254
Using Automatic Routing in DIRECT.............................................................. 255

Defining Global Routing Settings ............................................................................. 257 Editing Route Properties for Individual Edges ......................................................... 258
Using Manual Routing in DIRECT .................................................................. 259 Creating Routing Tables ................................................................................ 261
Example of Creating Routing Tables ....................................................................... 262
Defining Routes for Individual Traffic ............................................................. 263 Viewing Routes .............................................................................................. 265 Viewing the Routing Summary ....................................................................... 267 Routing Protection Loops............................................................................... 268 Removing Under-Utilised Edges Automatically .............................................. 268
Chapter 8 Creating the SDH Network
271
Overview of the SDH/SONET Module ............................................................ 272 About Planning the SDH VC-4 Network ......................................................... 274 About the SDH and SONET Multiplexing Structures ...................................... 276 About J-KLM Numbering in DIRECT .............................................................. 277 Using Protection in the SDH Module .............................................................. 277
About Path Protection .............................................................................................. 277 About MS-SPring Protection .................................................................................... 280 About SNC Protection.............................................................................................. 282 Using Protection Topologies in the SDH Module .................................................... 282 Viewing SDH Protection Loops ............................................................................... 283
Chapter 9 Creating the PDH Network
285
Overview of the PDH Module ......................................................................... 286 Managing Timeslot Allocation ........................................................................ 288 Planning the PDH Network ............................................................................ 289
Setting the PDH Default Parameters ....................................................................... 290 About PDH Protection Loops ................................................................................... 293 About Timeslot Allocation in the PDH Module ......................................................... 295 Defining Timeslot Allocation Templates .................................................................. 298 Viewing and Editing PDH Edges ............................................................................. 302
Chapter 10 Creating the ATM Network 307

About Planning The ATM Network ................................................................. 308 Displaying Paths in the ATM Module ............................................................. 308 Setting the ATM Default Parameters.............................................................. 310
About the ATM Atm Default Parameters Tab .......................................................... 311 About the ATM Capacity Calculation Parameters Tab ............................................ 311 About the ATM Signalling Parameters Tab ............................................................. 311 About the ATM Node B Defaults Parameters Tab .................................................. 312 About the ATM AAL2 Calc Options Tab .................................................................. 312 DIRECT User Reference Guide Version 6.0 Page 9
Calculating QoS and Capacity Over ATM Networks ...................................... 312

Defining the ATM CAC Parameters Used in Capacity Calculations ....................... 314 Using the Capacity Wizard to Calculate QoS and Capacity .................................... 315 Allocating ATM Multiplexer Requirements............................................................... 317 Defining QoS Queuing Schedules ........................................................................... 317 Allocating VPT Requirements .................................................................................. 320 Calculating VCC Capacities .................................................................................... 320 Calculating VPT Capacities Based on QoS Requirements ..................................... 321 Assigning QoS Queuing Scheduling Mechanisms to VPCs and VCCs .................. 322 Performing the ATM Analysis .................................................................................. 323
About ATM Service Categories ...................................................................... 324 Creating VCI Numbering Templates .............................................................. 324
Assigning VCI Numbering Templates to VPCs ....................................................... 325
Viewing and Editing VCC Group Properties ................................................... 326

Adding and Editing VCCs in a VCC Group.............................................................. 327 About the AAL/Service Category Tabs for a VCC Group ........................................ 328 About the VCIs Tab for a VCC Group ..................................................................... 329 About the Delay Parameters Tab for a VCC Group ................................................ 329
Viewing and Editing VPC Group Properties ................................................... 330

Viewing VPCs and VCCs in a VPC Group .............................................................. 330 About the VPIs Tab of the ATM VPC Group Dialog Box ......................................... 331
Viewing and Editing VPT Group Properties.................................................... 331

About the VCCs & VPCs Tab of the ATM VPT Group Dialog Box .......................... 331 Viewing and Editing VPT Properties ........................................................................ 332
Viewing and Editing AAL Group Properties .................................................... 333

Setting the AAL Layer for ATM Traffic ..................................................................... 333 Viewing and Editing AAL Edge Properties .............................................................. 334
Chapter 11 Creating the IP Network
337
Overview of the IP Module ............................................................................. 337 About Planning The IP Network ..................................................................... 339 Setting the IP Network Default Parameters .................................................... 340
About the QoS Schemes in the IP Module .............................................................. 342
Using IP Addresses in DIRECT ..................................................................... 343

About the IP Addressing Concept ........................................................................... 344 Adding IP Addresses to Equipment ......................................................................... 345 Distributing IP Addresses ........................................................................................ 346
Calculating QoS and Capacity Over IP Networks........................................... 348

Allocating QoS Requirements ................................................................................. 349 Setting the Router Capabilities for IP Traffic Edges ................................................ 349 Calculating the IP Capacities Based on QoS/CoS Requirements .......................... 350 Performing the PQNA Analysis ............................................................................... 351 Viewing the Calculated QoS on IP Traffic Edges .................................................... 352
Page 10
DIRECT User Reference Guide Version 6.0
Chapter 12 Creating the Lightpath Network
353
Overview of the Lightpath Module .................................................................. 354 About the Lightpath Edge Types .................................................................... 355 Planning the Lightpath Network ..................................................................... 355 Editing Lightpath Edge Groups ...................................................................... 356 Editing Lightpath Edges ................................................................................. 357
Appendix A Synchronisation Data
359
Synchronising 3g Service Types .................................................................... 359 Synchronising 3g Traffic Types ...................................................................... 360 Synchronising Connection Types ................................................................... 360 Synchronising Cell Layer Types..................................................................... 360 Synchronising Properties ............................................................................... 361 Synchronising Nodes ..................................................................................... 361 Synchronising GSM Cellular Links ................................................................. 361 Synchronising Links ....................................................................................... 361 Synchronising GSM Cells .............................................................................. 362 Synchronising GSM Cell Layers .................................................................... 362 Synchronising UMTS Cells ............................................................................ 362 Synchronising UMTS Traffic .......................................................................... 362
Appendix B About DIRECT Network Labels
365
Generic Module Labels .................................................................................. 366 Transmission Module Labels ......................................................................... 366 Traffic Module Labels .................................................................................... 367 SDH/SONET and PDH Module Labels .......................................................... 368 ATM Module Labels ....................................................................................... 368 IP Module Labels ........................................................................................... 369 Lightpath Module Labels ................................................................................ 369
Page 11
Appendix C About the Traffic Utilisation Calculations 371

Traffic Utilisation Calculations ........................................................................ 371 Circuit Utilisation Calculations ........................................................................ 372 Channel Utilisation Calculations..................................................................... 374
Glossary of Terms 375 Index 387
Page 12
CHAPTER 1
Introduction
DIRECT is AIRCOM International's transmission planning, designing and dimensioning tool. It enables the user to define the 2G, 2.5G, 3G, PSTN or TETRA data/voice requirements, and plan the capacity demands back through the network using the IP, ATM, SDH, PDH and Optical modules to create the core Transmission and Switching backbone. DIRECT thus provides complete end-to-end transmission planning. Using DIRECT means that the planning cycle of a transmission network is both flexible and efficient. You can enter data from a variety of sources, set up different routing criteria and then view the results of a planned network. The planning procedure can then be repeated as many times as required until your desired transmission network has been created. DIRECT is designed for telecommunication networks with different network layers; this graphical planning tool reliably supports general and strategic planning of Cellular, PSTN and data operators' networks. It combines useful design algorithms with an intuitive, easy-to-use graphical user interface that helps you visualise your planner. As a general planning tool, DIRECT is equipment vendor-independent. Using the Equipment Editor, you can create any vendor equipment deployed in the customer network. In DIRECT, you can model and then use all interface cards, functionality and features.
In This Section
Obtaining User Assistance 14
Page 13
Obtaining User Assistance

Using Online Help ENTERPRISE products come with a complete system of online Help which you can access in three ways: From the Help menu, click Help Contents. Scroll through the table of contents and choose a relevant topic to display. To search for something particular, from the Help menu, click Help Contents and using the Index tab or Find tab, type in a letter or word to start searching for relevant topics. Press F1 in a dialog box to view context-sensitive help (available for most dialog boxes). Using ENTERPRISE User Reference Guides If you prefer to read printed content, we also provide User Reference Guides. To view or print these as PDFs (Adobe Acrobat portable document format): 1 Make sure you have Adobe Acrobat Reader installed on your PC. If you do not have this, you can install it from the ENTERPRISE CD, or get it from the Adobe website. Note : Adobe and Acrobat are trademarks of Adobe Systems, Incorporated. 2 Click Start on the taskbar, point to Programs, then AIRCOM International, then ENTERPRISE, then Docs. - or Navigate to the Docs folder in the location where you installed the product. Note : If neither of these exist, please contact your administrator. 3 Double-click the PDF file that you want to view. Tip : If you have a customer web account, you can also download the latest User Reference Guides from our website. Checking Release Notes Each release of the ENTERPRISE software is accompanied by Release Notes, giving important information on system requirements, installation, known issues, upgrades and so on. These notes are included in the ENTERPRISE CD, or you can download them from our website. For any further documentation, such as application notes and extra reference information, please email the support team at the address described in Obtaining Support on page 17.
Page 14
Who is This User Reference Guide For?

The ENTERPRISE User Reference Guides are intended for different audiences, depending on the particular product. Typical prerequisites include a good understanding of the following: The appropriate telecoms technologies and the associated network planning methods (for planning software) Relational database management, and in particular Oracle database creation and administration procedures (for administrative software) The various parameters utilised for monitoring and optimising networks (for OSS software) Irrespective of the particular product, the following basic knowledge is required: Microsoft Windows concepts The functions of the Microsoft Office suite of tools, in particular Excel
About the ENTERPRISE User Reference Guides

This table describes our range of User Reference Guides:
This Guide What's New ENTERPRISE Installation and Administration Contains Information On The main difference between the latest versions of the ENTERPRISE suite. Installing and configuring ENTERPRISE, your network, and Oracle databases. Using Administrator to create users and groups, and set permissions. Also contains information on software licensing. ENTERPRISE Database Reference ENTERPRISE User Reference ENTERPRISE Technical Reference ADVANTAGE User Reference The relationships between tables in the database and the contents of each table. Functionality that is common to most of the products in the ENTERPRISE suite, including how to access, view, edit and store data. File formats, as well as antenna and diffraction calculations. Using ADVANTAGE to plan and optimise networks automatically, consider measured data in analysis/optimisation, analyse network performance, identify problematic areas/cells, and more. Using ARRAYWIZARD to automatically generate coverage predictions and best server arrays, which gives you instantaneous display of coverage and interference information for pre-selected filters when loaded into ASSET3G. Using ASSET3G, the network planning and analysis tool, to design a range of 2g and 3g networks. Includes information on hierarchical network planning, propagation modelling, service and bearer definition, coverage analysis, traffic planning, neighbour planning, frequency planning, CW data analysis, detailed reporting, analysis arrays and simulation of network performance. ASSET3G Technical Reference Array descriptions and information on some of the algorithms used in ASSET3G.
ARRAYWIZARD User Reference
ASSET3G User Reference
Page 15
This Guide CONNECT User Reference
Contains Information On Using CONNECT, the network transmission and microwave link planning software for full network physical link design and logical link design. Also contains CONNECT-specific reference information.
DATASAFE User Reference DIRECT User Reference
Using DATASAFE, our network configuration tool to implement both small and large scale changes to networks Using DIRECT to design telecommunications networks of different network layers. Explains how to plan cellular, PSTN and data networks at a both general and strategic level. Also contains DIRECT-specific reference information.
NEPTUNE User Reference
Using NEPTUNE to collect, import and analyse testmobile data and using the optional module, PROBE for additional analysis. Also contains reference information on NEPTUNE file formats.
OPTIMA User Reference OSSEXPERT User Reference RANOPT User Reference TARGET User Reference
Using OPTIMA to view performance data and statistics both with ENTERPRISE and standalone using OPTIMA Lite. Using OSSEXPERT to manage optimisation tasks in wireless networks. Using RANOPT to efficiently find faults in your network, optimise and validate its performance prior to commercial launch. Using TARGET as an administrator to design forms, Gantt charts and reports. Using TARGET to view and edit information about your network and its roll out. Also contains TARGET reference information.
WEBWIZARD User Reference
Using WEBWIZARD to display GIS and report information of network data, including creating layers, regions, nodes, layer types, administering and configuring the system and using the GIS view, explorer and report viewers.
Can You Improve Our User Assistance?

We are always trying to improve the online Help and User Reference Guides. If you cannot find the Help you were looking for, need more information, or have any suggestions for improvements, we would be grateful for your feedback. Online Questionnaire You can help us by completing our brief online questionnaire (http://tinyurl.com/y47rqn). Alternatively, you can contact us directly at docs@aircominternational.com.
Page 16
Obtaining Support
If you have a difficulty you cannot resolve yourself using the online Help or Reference Guides, or you have found a possible fault in the software, you can log a support request as described below. You may also wish to contact us if you want to: Register for a customer web account to access the Support area Obtain further documentation, such as application notes and extra reference information Logging Support Requests Online To log a support request online: 1 2 3 4 5 6 Go to the AIRCOM website, at www.aircominternational.com. Click the link to Support. Log in, using your customer web account username and password. In the Technical Support pane, click Online Helpdesk System. Click Log New. Enter the details of your request, and then click Log.
Contacting us via Telephone or Email If you wish to contact us directly, here are the contact details of our regional offices:
Location Europe Regional Office United Kingdom Contact Details Tel : +44 (0) 01932 442345 Fax :+44 (0) 01932 442005 support@aircominternational.com Sweden France Italy Germany Belgium Middle East, Africa and Central Asia United Arab Emirates support@aircominternational.se support@aircominternational.fr support@aircominternational.it support@aircominternational.de support@aircominternational.be Tel : +971 4 391 2642 Fax :+971 4 391 8660 support@aircominternational.ae South Africa Tel : +27 11 3243600 Fax : +27 11 7848027 support@aircominternational.com Americas Mexico USA support@aircominternational.com.mx Tel : +1 866 207 8083 Fax : +1 214 360 7241 support@aircominternational.us Brazil Tel : +55 12 3941-2199 Fax : +55 12 3911-3727 support@aircominternational.com.br
Page 17
Location Asia and Oceania
Regional Office Australia Singapore China Taiwan India
Contact Details support@aircominternational.com.au support@aircominternational.sg support@aircominternational.cn support@aircominternational.com.tw support@aircominternational.in
When contacting us with a support query, it would help us if you: Give us as much information as possible about the problem and the context in which it occurred State the version and build you are using Have all the details of your query to hand Are logged into the ENTERPRISE application Can send extracts of your data sets if we need them to reproduce your problem
Obtaining Further Information and Services

As well as comprehensive online Help and User Reference Guides and dedicated Product Support, AIRCOM additionally provides: Online Knowledgebase of Articles If you register for a customer web account, you can view our searchable technical database in the Product Support section of the AIRCOM website. This Knowledgebase contains articles created by our support professionals who have resolved issues for our customers, and is constantly updated, expanded, and refined to ensure that you have access to the very latest information. Online Technical Forum You can obtain useful information from our online problem-solving technical forum. The URL address is: http://www2.aircom.co.uk/techforum If you would like permission to access to this resource, please email the support team at the address described in Obtaining Support on page 17. Power Tools If you register for a customer web account, you can download from a selection of useful power tools, such as file conversion utilities. Latest Copies of the User Reference Guides If you register for a customer web account, you can download the latest User Reference Guides PDFs from our website. If you do this, please check the back of the User Reference Guides for any additions or corrections.
Page 18
Consultancy Services AIRCOM also provide full radio consultancy services in Network Audits, Business Planning Support, Licence Applications, Radio Network Planning, Telecommunications Research and System Modelling and Propagation Analysis and Modelling. Training There is a wide variety of courses run by AIRCOM. These courses range from tool training to technology training. For details, contact Competence Development Solutions (training@aircominternational.com).
Page 19
Page 20
CHAPTER 2
About the DIRECT User Interface

This section explains the DIRECT user interface, including the windows and toolbars that you can use to plan your transmission network.
In This Section
Opening DIRECT in the ENTERPRISE Suite About the DIRECT Global Toolbar About the DIRECT Routing Toolbar About the DIRECT Modules About the DIRECT Equipment Editor About the Views Browser About the Network Browser About the Task Pane 21 22 23 24 46 47 47 48
Opening DIRECT in the ENTERPRISE Suite

DIRECT is part of the ENTERPRISE suite of tools and therefore appears in the tabs on the main menu:
DIRECT tab on the main toolbar
To open DIRECT: 1 2 On the main menu, click the DIRECT tab. From the DIRECT menu, click Launch DIRECT.
Page 21
About the DIRECT Global Toolbar

The following pictures show the Global toolbar, which is common to all modules. The first part of the Global toolbar contains generic functions, which may be familiar from other programs:
Generic functions on the Global toolbar
The next three buttons are special editing functions:
Editing functions on the Global toolbar
The next three buttons enable you to add nodes, and add and edit edges:
Node and Edge functions on the Global toolbar
The next nine buttons are special viewing functions:
View functions on the Global toolbar
Page 22
The final set of functions is as follows:
Further functions on the Global toolbar
As well as the Global toolbar, DIRECT has a dedicated Routing toolbar and each module also has its own separate toolbar.
About the DIRECT Routing Toolbar

As well as the Global toolbar, DIRECT has a Routing toolbar, which is common to all modules.
Routing toolbar
Page 23
About the DIRECT Modules

Each module has its own individual module window, where all of the planning and drawing of that particular aspect of the network is done. This section gives a brief description of each module, an example window and a description of the accompanying toolbar.
About the Transmission Module

You can use the Transmission module to create and edit your physical network in three different views, the Property view, the Equipment view and the Detail view. In the Equipment view, you can: Connect equipment using different connection types Edit equipment and connection properties This picture shows an example Transmission module window, displaying the Equipment view:
Example Transmission module window (Equipment view)
Page 24
In the Property view, you can: View Property and equipment information Connect Properties using conduits This picture shows an example Transmission module window, displaying the Property view:
Example Transmission module window (Property view)
Page 25
In the Detail view, you can: View port to port connectivity Display detailed schematic diagrams of network configurations and circuit routing This picture shows an example Transmission module window, displaying the Detail view:
Example Transmission module window (Detail view)
Page 26
About the Transmission Module Toolbars

There are two separate Transmission module toolbars, one for the Equipment view and one for the Property view. The Transmission module Equipment view toolbar has buttons for adding different kinds of edges:
Transmission module (Equipment view) toolbar
These edges can be displayed or hidden using the Network Filters toolbar across the top:
Transmission module Network Filters toolbar
The Transmission module Property view toolbar has buttons for adding Properties, pits and conduits:
Transmission module (Property view) toolbar
Page 27
About the Traffic Module

In the Traffic module, you can: Generate all of the traffic for your network View the traffic requirements for each separate layer Create and edit logical connections The Traffic module is divided into separate traffic layers, each of which has its own properties and functions:
On this Traffic layer Cellular You can View and edit RF planning data imported from ASSET3G. Add cellular equipment. Set the TRX count for 2/2.5 g cells on a node. Route traffic based on TRX, Erl, Service or Subscriber numbers. Forecast TRX counts. Set 2/2.5g network parameters. Set 3g traffic service types and subscriber numbers. Set 3g network parameters per service type. Provide soft handover between Node B elements. PSTN Set the PSTN traffic parameters. Add PSTN equipment (PSTN Access and LE nodes). TETRA Set the TETRA traffic parameters. Add TETRA equipment (DSC, DXT and TBS nodes). Interswitch Set the interswitch traffic parameters. Generate interswitch parameters. Add interswitch equipment. Set subscribers based on TRX count. Set the traffic distribution ratios, on an MSC by MSC basis. Define external networks and the Point of Interconnect. Calculate the traffic between MSCs and Interactive/Voice messaging services. Calculate traffic between PSTN LEs and Interactive/Voice messaging services. Signalling Add signalling equipment. Define the signalling traffic parameters. Set each node to have STP or SSP functionality. Generate and edit routing tables for the signalling traffic. Create and edit signalling protocols. Calculate traffic between PSTN LEs and signalling services. Generic Add generic traffic for use in special network planning scenarios.
Page 28
This picture shows an example Traffic module window, displaying traffic network elements and connections.
Example Traffic module window
Overview of the Traffic Module

All traffic is generated in the Traffic module. Traffic can be created for PSTN, Interswitch, Signalling, Cellular (2g, 2.5g and 3g) and TETRA networks, with each type having its own functionality. The Traffic module provides: A control view window, enabling you to navigate easily between the network types, with the additional flexibility to filter the nodes that you want to view (for example, 2g, 3g, interswitch nodes and so on). More than one Traffic view can be open at the same time and/or can be individually set to display different sub-sets of the network. You can specify combinations of views and filters based on your own requirements.
Page 29
For example, this picture shows the top half where only the cellular filter is displayed and the bottom half where only the interswitch filter is displayed:
Page 30
Elements in the Traffic module are 'logically' connected, based on the parenting information provided (in other words, which BTS belongs to which BSC). You can interrogate these connections and see what traffic has been generated between the two network elements:
DIRECT's methodology gives you greater control on how the traffic is routed. For example, 3g traffic does not have to be routed directly onto the ATM layer, but the logically generated traffic can then be routed onto one of the lower layers independently according to your routing requirements.
Page 31
In the Traffic module, you can define traffic per node/site in terms of Trx (for 2g and 2.5g) and enables you to specify the different traffic types for uplink and downlink for UMTS:
In order to be able to define user or handover traffic in a network, you can either use pre-defined default traffic types or define your own. Each of these traffic types must be mapped to a service class, which determines how the traffic is treated by the network. The traffic types are then used to define the traffic mixes at the network nodes.
Page 32
A new plan is always started with the default traffic types, but DIRECT enables you to export, import and set the default traffic types for a plan. User-defined traffic types are also stored in the actual plan, and can be set as default as well.
End-to-end delay, cell loss rate and tail probability determine how traffic is treated through the network on an end-to-end basis. You can define these requirements, along with creating a service type. These requirements are then distributed over the network elements, and then the requirements are used along with the traffic mix defined at the nodes to calculate capacity.
Page 33
Delay budgets can be constructed for any scenario, for example Traffic to ATM to IP or Traffic to ATM to PDH to SDH. You can define the delays at the media, AAL multiplexing delay and inside the switch, queuing delay and processing delay.
Page 34
About the Traffic Module Toolbars

The first Traffic module toolbar has buttons to select which traffic layers are active:
Traffic module toolbar
The other toolbar contains buttons to add the different types of edges, depending on which traffic layers are active:
Traffic module toolbar
Page 35
About the SDH Module

The SDH module supports both SDH and SONET. The SDH module view window displays SDH nodes and VC-4 path connections. You can use the SDH module to: Route traffic onto SDH paths (VC-4, VC-4-4c, VC-3) Route the SDH paths onto the physical STM-n network Protect the SDH paths on the physical STM-n network using path protection and MS-Spring Set up and monitor the link connectivity and node interfaces Assign KLM and J values to the traffic tributaries View the mapping of virtual channels This picture shows an example SDH module window, displaying SDH network elements and connections.
Example SDH module view window
Page 36
About the SDH Module Toolbars

The first SDH module toolbar has buttons to select which SDH/SONET multiplexing level standards are active:
SDH/SONET module toolbar
The other toolbar contains buttons to add the different types of edges, based on the SDH/SONET multiplexing level standards that are active:
SDH/SONET module toolbar
Page 37
About the PDH Module

You can use the PDH module to: View cross connections at the primary rate level, all the way down to 8k level, for use in primary rate planning Create and use timeslot allocation templates to position traffic within a frame Create PDH multiplexing hierarchies Identify and define any network protection loops The PDH module supports both ETSI and ANSI standards. This picture shows an example PDH module window, displaying PDH network elements and connections.
Example PDH module window
Page 38
About the PDH Module Toolbars

The first PDH module toolbar has buttons to select which filter will be used:
PDH module toolbar
Page 39
The other toolbar contains buttons to add the different types of edges:
PDH module toolbar
The following table lists the types of edges that you can add:
Edge group Level 0 Level 1 Level 2 Level 3 Level 4 Level 5 Physical Level Edge types 64k 1.5M, 2M 6M, 8M 32M, 34M, 45M 98M, 140M, 274M 397M, 565M E0-E5, T0-T4, J3-J5, xE1, xT1, xT3
Page 40
About the ATM Module

You can use the ATM module to: Create ATM hubs and cross connection points Create VCC, VPC and VPT paths between ATM network elements Calculate bandwidth requirements for ATM paths based on the service type and subscriber requirements Route the bandwidth requirement over the SDH and PDH layers Set connections to use inverse multiplexing Calculate delay parameters for traffic across the network Export cross connect and delay report data to Excel Define service rate and service category details This picture shows an example ATM module window, displaying ATM network elements and connections.
Example ATM module window
Page 41
About the ATM Module Toolbars

The first ATM module toolbar has buttons to select which filter will be used.
ATM module toolbar
The other toolbar contains buttons for adding and enabling the display of VCCs (Virtual Circuit Connections), VPCs (Virtual Path Connection) and VPTs (Virtual Path Terminations).
ATM module toolbar
Page 42
About the IP Module

The IP module window is used to display IP nodes and connections. In the IP module, you can: Distribute traffic Allocate and distribute IPv4 and IPv6 network addresses to network elements Add overhead traffic requirements and then route the traffic to a specific network layer This picture shows an example IP module window, displaying IP network elements and connections.
Example IP module window
About the IP Module Toolbars

The IP module layer toolbar has two buttons to select which filter will be used:
IP module layer toolbar
Page 43
The IP module edge toolbar has buttons for adding different IP edges:
IP module edge toolbar
Page 44
About the Lightpath Module

The Lightpath module is used for wavelength planning of (D)WDM networks, with a main function of modelling the lightpath network topology. In the Lightpath module you can: Import and export lightpaths Add lightpath segments Edit lightpath segments This picture shows an example Lightpath module window, displaying Lightpath network elements and connections:
Example Lightpath module window
About the Lightpath Module Toolbar

The Lightpath module toolbar has buttons for adding the different lightpath edges:
Lightpath module toolbar
Page 45
About the DIRECT Equipment Editor

You can use the DIRECT Equipment Editor to add new equipment types and configure them according to the DIRECT equipment model. The equipment model enables you to define the equipment attributes, connections and any sub-equipment. You access the Equipment Editor through the Equipment Browser.
Equipment Browser
To open the Equipment Editor, click the Open Equipment Editor button.
Equipment Editor
Page 46
About the Views Browser

In the Views Browser, you can add layers to your network by adding additional modules and additional module view windows.
Example Views Browser
About the Network Browser

In the Network Browser, you can: View all the network elements in the project Commit, delete and restore multiple modules and elements Add connecting edges between equipment in a layer
Page 47
This picture shows an example Network Browser:
Example Network Browser (Region View)
The Network Browser contains two views, which are described in the following table:
This view Region View Module View Displays All of the Properties in the network, and any cabinets, shelves and equipment contained in them. All of the modules contained in the network, and their layers, edge groups and edges.
About the Task Pane

You can use the Task pane to perform a number of different tasks in DIRECT. In the Task pane, you can: Generate a network topology automatically Import and export network data Generate reports, detailing information about your network To display the Task pane: Click the Task pane button .
Page 48
This picture shows an example Task pane:
Example Task pane
Tip : This is a toggle button, so click it again when you want to remove the Task pane. You can also slide the Task pane back and forth across the screen, by hovering the cursor over the edge, and then holding down the left mouse button and shifting the cursor back and forth.
Page 49
Page 50
CHAPTER 3
Getting Started in DIRECT

Using DIRECT makes planning a transmission network both flexible and efficient. You can enter data from a variety of sources, set up different routing criteria, and then view the results of a planned network. You can repeat the planning procedure as many times as is required until your desired transmission network has been created. Before you begin to plan your first few networks, you should ensure you understand the basic concepts that DIRECT is based around.
In This Section
About the Network Planning Process Synchronising DIRECT with ASSET3G/CONNECT About DIRECT's Generic Functions Setting the Plan Preferences Using the Views Browser Adding Equipment Nodes in the Module Window Editing Equipment Adding Connecting Edges Controlling the Display About Displaying Data in Module Views About Using the Task Pane 52 54 60 61 66 68 70 71 77 84 87
Page 51
About the Network Planning Process

Obtaining an accurate network is an iterative process. This picture shows an example of a planning cycle you could follow in DIRECT.
An example network planning cycle
Note : The work order for the planning of a network is usually decided by the network planner, and each specific project may have a different start point.
Page 52
About Planning Using the DIRECT Modules

DIRECT is built around a series of modules, which are modelled on the planning cycle. This diagram shows the modules, and their inter-relationship.
DIRECT Modules
The modules can be divided into three different types, corresponding to the four network layers. The Traffic module models the traffic layer, and this table describes the different traffic layers available:
Use this traffic layer Cellular GSM/UMTS PSTN Signalling TETRA IP To plan and model GSM or UMTS cellular networks. Non- concentrated and concentrated access node traffic for switched access traffic. SS#7 signalling. Terrestrial Trunked Radio networks. Packet switched networks.
Page 53
This table describes the modules that model the service network layer:
Use this Traffic Layer ATM IP SDH To plan and model ATM layers in data and 3g cellular networks. Packet switched networks and perform basic transmission capacity dimensioning for GPRS networks. The SDH high order path network and the SDH frame structure. The frame structure model is accurate enough to calculate payload capacity and dimension SDH node sizes (for example, the VC-4 and VC-12 cross connect sizes and number of aggregate interfaces and tributaries). This module is essential for STM-16 network plans. PDH 1.5 and 2Mb frames in the network.
This table describes the different views in the Transmission module, which model the transmission and physical connectivity layers:
Use this Module View Equipment Property Detail To plan and model Equipment node to node connectivity and circuit information on each media type. Property connectivity via physical conduits. Port to port connectivity for equipment.
Synchronising DIRECT with ASSET3G/CONNECT

DIRECT synchronisation enables you to intelligently transfer data between DIRECT and the ENTERPRISE suite of tools. This gives you more control over what gets synchronised and how. For example, you may want to import only the traffic data from each Node in the ASSET3G module into the Cellular module of DIRECT in order to see how traffic growth within the network impacts on the current network design. This provides a time- and cost-effective way of populating DIRECT with the necessary data without needing to enter the data manually. You can synchronise data from and to ASSET3G/CONNECT and DIRECT that includes: Site types and Property co-ordinates (2g BTSs, BSCs and MSCs, 3g Nodes, RNCs and SGSNs) Link types - CONNECT microwave links are synchronised as DIRECT radio links Equipment information Total traffic load (Kb/s per sector) Traffic types Parenting information DIRECT also supports easy import/export procedures for getting data from XML and Excel spreadsheets.
Page 54
Performing Synchronisation in DIRECT

To perform synchronisation: 1 2 Ensure that you have opened and logged in to DIRECT. From the DIRECT toolbar, click the Synchronise DIRECT button The Synchronisation Transfer Wizard appears. .
Select the type of transfer that you want to perform, choosing from:
Item Description Move data on additions/updates/deletions from the ASSET3G/CONNECT database to the DIRECT database.
Move data on additions/updates/deletions from the DIRECT database to the ASSET3G/CONNECT database.
Move data on additions/updates/deletions between both databases.
For more information about the data synchronised between the tools, see Synchronisation Data on page 359. 4 5 If you are transferring data from ASSET3G/CONNECT, select the filter that contains this information. Choose which actions to perform. You can select to:
Page 55
6 7
Add data Update data Delete data
Click Next, and then specify which equipment types you want to use. On the next page of the wizard, in the Action column, select the appropriate option for each of the objects, choosing from:
Item Ignore Merge (use ASSET/CONNECT data on conflict) Merge (use DIRECT data on conflict) Transfer to DIRECT Transfer to ASSET/CONNECT Description Ignores the object during synchronisation. Information relating to that object is not moved. Checks for changes in the objects in both databases and then applies those changes. If there is a conflict, the ASSET/CONNECT data is used. Checks for changes in the objects in both databases and then applies those changes. If there is a conflict, the DIRECT data is used. Checks for changes in the objects in the ASSET/CONNECT database, and applies those changes to the DIRECT database. Checks for changes in the objects in the DIRECT database, and applies those changes to the ASSET/CONNECT database.
Click the Analyse button. The databases synchronise and the results are displayed:
The objects are colour-coded as follows: 9 Green objects have been newly added to DIRECT or ASSET/CONNECT, depending on the direction of synchronisation Yellow objects have been newly added to both Red objects have been deleted from both
If you are satisfied with the results, click the Synchronise button to complete the synchronisation.
Page 56
The Synchronisation Transfer Wizard will show the synchronisation results:
- or If you want to manually edit any of the details (for example, the DIRECT equipment type that will be created), double-click the appropriate column, select the required option, and then click Synchronise. Tip : For more information on the synchronisation process, see How Does Synchronisation Work? on page 59.
Page 57
Configuring Synchronisation Object Options

In DIRECT, you can have many types of equipment for each object configured in your equipment database. For example, you may have multiple equipment types for the MSC object. Therefore, when you are synchronising (in either direction), you must specify which equipment types that you want to use. To do this: 1 On the second page of the Synchronisation Transfer Wizard, for each object, select the Default Equipment Type from the list. The list displays all of the equipment types (including radio equipment) that you have created for that object:
Note : You can also select equipment units, or templates that you have created. 2 Select which link types will have a conduit automatically created for them when they are imported. The following table explains the conduit type that will be created for each link type:
For this link type Microwave Optical Fibre Coaxial Cable Satellite Twisted Pair Leased Line This conduit type will be created Radio Duct Duct Duct Duct Leased line
3 4
If you want to automatically create a PDH/SDH edge for a link when it is imported, select the checkbox. When you have set all of the options that you want, click Next, and continue through the wizard. For more information, see Synchronising DIRECT with ASSET3G/CONNECT on page 54.
Page 58
Editing the Synchronisation Analysis Results

After you have performed a synchronisation analysis, you can edit the results before you finally synchronise. The following table describes the details that you can edit:
In this column Action ASSET3G/CONNECT Equipment DIRECT Equipment Link End A and Link End B You can edit The synchronisation action that is performed Ignore, Merge or Transfer. The equipment type stored in ASSET3G/CONNECT database. The associated equipment type template stored in DIRECT. The ASSET3G/CONNECT radio nodes at each end of the link.
How Does Synchronisation Work?

This section describes what happens when DIRECT performs synchronisation. New Nodes When a new BTS or Node B is found: 1 DIRECT checks the ASSET3G/CONNECT database for the associated equipment type. 2 For a BTS, the name is stored as the BTS Equipment Type in the Site Database, on the Site Equipment subtab of the Installation tab. For a Node B, the name is stored as the Node B Type in the Site Database, on the Resource tab.
If an associated BTS or Node B equipment type is found, then the equipment name is displayed in the ASSET3G/CONNECT Equipment column. Otherwise this field is left blank. DIRECT then tries to find an equipment with matching name in the DIRECT Equipment database. If DIRECT finds a match, this is displayed in the DIRECT Equipment column. If DIRECT does not find a match, it will use the default equipment type set in the Synchronisation Transfer Wizard. If no default has been set, the column remains blank.
When a new MSC, BSC, WMSC, SGSN or RNC is found: DIRECT will create the equipment based on the default set in the Synchronisation Transfer Wizard. If no default has been set, the column remains blank. New Links When a new radio link (with associated radio equipment) is found in the ASSET3G/CONNECT database: 1 2 DIRECT checks for radio equipment with the same name (and with radio link capability) in the DIRECT equipment database. If an appropriate radio equipment type is found, then the equipment name is displayed in the DIRECT Equipment column.
Page 59
- or If no appropriate equipment type is found, then DIRECT will create the equipment based on the default set in the Synchronisation Transfer Wizard. If no default has been set, the column remains blank. When a new non-radio link (for example, optical fibre or coaxial cable) is found: 1 2 The ASSET3G/CONNECT Equipment and DIRECT Equipment columns are left blank. DIRECT checks the Properties at either end of the link for any equipment with the appropriate link type capability. If any are found, then the first one found will be displayed in the Link A and Link B columns, depending at which end of the link they are. If none are found, then the Link End columns display New. For Radio link types, DIRECT will create a new equipment based on the DIRECT equipment type specified.
About DIRECT's Generic Functions

Although DIRECT has separate modules, there are a number of functions that are generic, and are used regularly in more than one module. It is important to understand these generic functions before you begin to use the separate modules. From the main Project menu, you can: Set the plan Preferences Print plans you have created Using the Views Browser, you can: Add and delete modules Add and delete module windows View module windows Using the Network Browser, you can: View equipment and equipment details View edge group and edge group details Select a network element in the module window Centre a network element in the module window(s) Commit, delete or restore network elements Create regions and organise Properties within them In most module windows, you can: Add equipment nodes, edit their general properties and view their cross connections Add connecting edge groups, and edit their general properties
Page 60
Add edges to edge groups, and edit their general properties Control the display in the module window Display module view information Using the Task pane, you can: Generate network topologies automatically Export and/or import data to and from DIRECT Generate network reports Using the Routing menu, you can: Route network layers onto each other Using the separate element dialog boxes you can: View and edit the general properties of nodes, edges and edge groups
Setting the Plan Preferences

Before you begin to plan, you should set up your network preferences, to ensure DIRECT creates your network in the appropriate way. To open the Preferences dialog box: From the Project menu, click Preferences. The Preferences dialog box appears.
Page 61
Setting How Equipment is Added

In the DIRECT Preferences dialog box, you can set the way in which equipment is added to the network. In a network plan, equipment is associated with cabinets and Properties, and you can decide how this association is made. To do this: 1 2 In the Preferences dialog box, click the General tab. In the When Adding Equipment pane, you can choose to associate equipment with Properties and cabinets in the following ways: DIRECT will prompt you for the Property and cabinet that you want to associate the new equipment with. For more information on how to select Properties and cabinets, see Associating Equipment with Properties and Cabinets on page 63. DIRECT to create a new Property and cabinet each time you add a new equipment. By default, this is the default option when you first launch DIRECT. DIRECT to add the new equipment to a new cabinet on the nearest Property on the view. DIRECT to add the new equipment to the first cabinet on the nearest Property on the view.
Click Apply.
Page 62
Associating Equipment with Properties and Cabinets

In the DIRECT Preferences dialog box, you can choose to be prompted for the Property and cabinet that you want to associate any new equipment with. If you select this option, the Add Equipment dialog box will appear when you add a new piece of equipment to your network plan.
Add Equipment dialog box
To select the Property and cabinet with which to associate the equipment: 1 In the Choose Property pane, either: Select the Property from the list Select the Create New Property checkbox, and type the name of the new Property in the ID Name box - or -
Note : If you create a new Property, you can also choose its location and associated region.
Page 63
In the Choose Cabinet pane, either: Select the cabinet from the list Select the Create New Cabinet checkbox, and type the name of the new Cabinet in the ID Name box - or -
Click OK.
Tip : In this dialog box, you can also edit the name of the equipment in the Equipment ID Name dialog box.
Setting How Detail Edges are Added

In the DIRECT Preferences dialog box, you can set the way in which detail edges are added to the network. In a network plan, detail edges are associated with connections, and you can decide how this association is made. To do this: 1 2 In the Preferences dialog box, click the Detail Edge Creation tab. In the When Adding Detail Edges pane, you can choose to associate detail edges with connections in the following ways: DIRECT will prompt you for the connection that you want to associate the new detail edge with. DIRECT will search for a suitable connection group, and the detail edge will be added to the first free connection. If more than one suitable connection group is found, DIRECT will prompt you to select one. DIRECT will search for a suitable connection group, and a new connection will be added for the detail edge. If more than one suitable connection group is found, DIRECT will prompt you to select one.
3 4
Optionally, DIRECT can prompt you for the port that you want your detail edge to originate from. To set this option, select the Prompt user for ports checkbox. Click Apply.
Setting the Originating Port for Detail Edges

To select the originating port for a detail edge: 1 2 3 Ensure that you have set DIRECT to prompt you for ports. When you add a detail edge, in the dialog box appears, select the port that you want the edge to originate from. Click OK.
Page 64
Setting the Edge Type Used in Network Plans

In the DIRECT Preferences dialog box, you can set the type of edges that are used in your network plan. To do this: 1 2 In the Preferences dialog box, click the Edge tab. Select either unstructured edges or structured edges. This table describes the two edge types:
Item Unstructured edges Structured edges Description Appropriate for use in the nominal planning stage. Traffic can be added to unstructured edges, but frame structure cannot. Appropriate for use in the detailed planning stage. Traffic can be added to structured edges, and frame structure can be defined as well.
Click Apply.
Setting How Items are Displayed

In the DIRECT Preferences dialog box, you can set the way in which edges, routes and selected items are displayed. You can select the line colour, width and style used to display these items. To do this: 1 2 3 4 5 6 7 In the Preferences dialog box, click the Colours tab. If you want to edit the display properties of an edge, select the edge type from the edge list in the Edge style pane. To edit the line colour, select the checkbox and double-click on the colour bar to choose the colour from the palette. To edit the line width, select the checkbox and type in the required line width. To edit the line style, select the checkbox and select the required style from the list. Set the display preferences for selected items, and primary and secondary routes. Click Apply.
Setting How Network Elements Are Selected

In the Preferences dialog box, on the General tab, you can set whether or not you can select elements across a number of Module Windows simultaneously. If you select this checkbox, when you select a network element, it will be selected in all of your other Module Views. Important : For the network element to be highlighted in a Module View, the network element has to be visible in that Module View. To ensure this, it is recommended that the Module Views are displayed in a Tiled formation. To do this, from the Windows menu, select either Tile Vertically or Tile Horizontally.
Page 65
Using the Views Browser

The Views Browser provides an overview of the different modules and views that are in a network plan. In the Views Browser, you can: Add and delete modules Add and delete module windows View module windows
Adding and Deleting Modules

In the Views Browser, you can add layers to your network by adding additional modules and additional module view windows.
Example Views Browser
To add a new Transmission or Traffic module: Click with the right mouse button on the required module type, and from the menu that appears, click the new type of view that you require. To add a new module, other than Transmission or Traffic: 1 2 Click Create Planning Module. From the menu that appears, click the name of the module you want to add. A new module view window for that module opens.
To delete a module: 1 In the tree list, click with the right mouse button on the name of the module that you want to delete.
From the menu that appears, click Delete Module.
Adding and Deleting Module Views

As well as having multiple modules (layers) in your network plan, you can also have multiple views of the same module. When you open a new module, an Equipment view is opened by default, but in the Views Browser you can add more equipment views, and in the case of the Transmission module, Property views and detail views as well. To add a new module view: 1 2 In the tree list of the Views Browser, click with the right mouse button on the name of the module that you want to delete. From the menu that appears, click New Equipment View, or (in the case of the Transmission module) New Property or New Detail View as appropriate:
Page 67
In the dialog box that appears, select which regions, Properties and so on that you want to display in the new view:
Tip : To display the same regions as another module view, in the Copy Selection From View drop-down list, select the required module view. 4 1 2 Click Apply, and then click Close. In the tree list, click with the right mouse button on the name of the module view that you want to delete. From the menu that appears, click Delete View. To delete a module view:
Important : You do not have to commit module views, as this is done automatically when they are closed.
Viewing Module Windows

You can use the Views Browser to view particular module view windows. This is useful if you have a large number of module windows open simultaneously, and want to switch from one to another. To view a module window: In the tree list, double-click on the name of the module window that you want to view. The selected module window moves to the top and becomes the active window. Tip : To bring an active module window to the top left hand position, from the Windows menu, click Tile Vertically.
Adding Equipment Nodes in the Module Window

After you have defined the equipment in the Equipment Editor, you can begin to add it to your module window. To do this: 1 2 3 Ensure that the Equipment Browser is open, and you have created all of the equipment that you require. Click the equipment node type that you want to add to the network plan. While still holding down the mouse button, drag the equipment type from the Equipment Browser list to the required position.
Page 68
Release the mouse button to place the equipment node.
- or 1 2 3 4 5 Ensure the Equipment Browser is open. Click the equipment node type that you want to add to the network plan. Click the Add Node button The node is added. .
In the module window click on the desired location of the node.
You can now edit the node properties. For information on how to edit the general properties of all equipment nodes, see Viewing and Editing the General Properties of Equipment Nodes on page 69.
Viewing and Editing the General Properties of Equipment Nodes

All equipment nodes have the same general properties, displayed on the General tab. To view or edit these: 1 2 Double-click on the equipment node. On the General tab, you can view or edit the following properties:
Item ID 1st Name 2nd Name Property ID Cabinet ID Comments Change History Description The ID code for the equipment node. The name of the equipment node. An optional name for the equipment node. The name of the Property that the equipment node is attached to. The name of the cabinet containing the equipment node. Any additional planning comments. Details of when the equipment node was created and last edited.
3 4
When you are satisfied with your changes, click Apply. You can also view or edit the General properties of equipment nodes in the Network Browser.
Viewing or Editing the General Properties of Equipment Nodes Using the Network Browser
You can use the Network Browser to view or edit the General properties of equipment nodes. To do this: 1 2 3 4 In the Network Browser, select Property view. Expand the relevant Property and cabinet, and then click with the right mouse button on the Equipment node. From the menu that appears, point to Active view, then click Show Details. In the dialog box that appears, edit the properties as required and then click OK.
Page 69
Viewing the Cross Connections of Equipment Nodes

On the Cross Connections tab of the Equipment properties dialog box, you can view the cross connections for transmission equipment.
Editing Equipment
You can edit equipment in a number of different ways.
Editing Equipment Using Editing Commands

You can edit equipment you have added by using the editing commands. This enables you to: Copy a piece of equipment from the module view window to the clipboard Paste a piece of equipment from the clipboard to the module view window
Deleting Equipment
You can delete a piece of equipment from the current module view window: 1 2 Select the equipment you wish to delete by clicking on it once. From the Edit menu, click Delete. The selected equipment is removed from the module view window and the database also. Ensure the Network Browser is displaying the Property View. Expand the Properties and cabinets to navigate to the equipment that you want to delete. Click with the right mouse button on the equipment, and from the menu that appears, click Delete. In the dialog box that appears, check that all you want to delete is listed. If so, click Confirm, otherwise click Cancel and go back to step 2. The required items are deleted.
You can also delete equipment using the Network Browser: 1 2 3 4
Page 70
Adding Connecting Edges

After you have added equipment nodes to the network plan, you can connect them using edges. You can do this in a number of places: In the Module Window, using the module toolbar In the Module Window, using the context menu In the Edge Group dialog box In the Network Browser, on the edge group In the Network Browser, on a network layer
Adding Edges in the Module Window Using the Module Toolbar

In the Module Window, you can use the module toolbar to add edges to connect the equipment that you have added to your module. To do this: 1 On the module toolbar, click the required edge type. Some of these types will only be available under special conditions, see the appropriate module chapters for more information. - or On the Global toolbar, click the Add Edge button . The first edge type in the toolbar list is shown as the default, unless you have added an edge previously, in which case it will be last edge type used. Note : The edge type must be compatible with the conduits connecting the Properties containing the equipment nodes. For more information on connectionconduit compatibility, see About Compatibility Between Connections and Conduits on page 76. 2 3 Click the equipment node at which you want to start the connection. Move the cursor to the node at which you want to terminate the connection, and click this node to anchor the connection.
Important : At this stage, you have only created a connection. The edge on the module window represents an edge group, which is a(n originally empty) container for separate edges. You now need to add edges, either in the edge group dialog box, or on the ATG tab of the Task pane.
Page 71
Adding Edges in the Module Window Using the Context Menu

In the Module Window, you can use the module toolbar to add edges to connect the equipment that you have added to your module. 1 2 In the Module Window, click with the right mouse button. From the menu that appears, click Add Edge. The Add Edge dialog box appears. This picture shows an example:
In this dialog box, select the required layer and connection type from the dropdown lists. Equipment compatible with this connection type will be displayed in black. Tip : If you want to hide any incompatible equipment, ensure that the Show All Properties/Equipments checkbox is not selected.
In the From box, locate and select the required originating equipment for the connection. Tip : You can locate specific originating and terminating equipment more quickly by typing in the equipment names in the Quick Find boxes.
5 6
In the To box, locate and select the required terminating equipment for the connection. If you are adding a PDH, SDH or IP edge to the Physical Layer, you can also create a corresponding transmission edge, by selecting the Create transmission edge checkbox and selecting the required media type. Click Add.
7
Page 72
Adding Edges in the Edge Group Dialog Box

In nearly all of the edge group dialog boxes, you can add edges to the edge group. Note : The exceptions to this are the VCC and VPT edge group dialog boxes. To add an edge to one of the edge groups: 1 2 3 In the Module Window, double-click the required edge group. In the left-hand pane, click with the right mouse button on the edge group. From the menu that appears, click Add. - or On the Global toolbar, click the Add Edge button. 4 Click Apply. After you have added edges, you can edit their general properties. For information on how to do this, see Viewing and Editing the General Properties of an Edge Group or Edge on page 76.
Adding Edges to an Edge Group in the Network Browser

To add edges to an edge group in the Network Browser: 1 In the Network Browser, in the Module View, select the required edge group. Important : You cannot create edges for edge groups that have the Freeze Load option selected on the Route Properties tab.
Page 73
Click with the right mouse button, and from the menu that appears, click Add Edge.
Adding Edges to a Layer in the Network Browser

In the Module Browser, in the Module View, you can connect equipment on a particular layer. To do this: 1 2 Select the layer containing the equipment that you want to connect. Click with the right mouse button, and from the menu that appears, click Add Edge.
Page 74
The Add Edge dialog box appears. This picture shows an example:
In this dialog box, select the required connection type from the drop-down list. Equipment compatible with this connection type will be displayed in black. Tip : If you want to hide any incompatible equipment, ensure that the Show All Properties/Equipments checkbox is not selected.
In the From box, locate and select the required originating equipment for the connection. Tip : You can locate specific originating and terminating equipment more quickly by typing the equipment names in the Quick Find boxes.
5 6
In the To box, locate and select the required terminating equipment for the connection. If you are adding a PDH, SDH or IP edge to the Physical Layer, you can also create a corresponding transmission edge, by selecting the Create transmission edge checkbox and selecting the required media type. Click Add.
Page 75
Deleting Edges
To delete an edge from the Edge Group dialog box: 1 2 Select the edge that you want to delete. Click with the right mouse button, and from the menu that appears, click Delete. - or Click the Delete Edge button.
About Compatibility Between Connections and Conduits

When adding connection groups between nodes, the connection type must be compatible with the conduit type that connects the Properties. The following table summarises the compatibility rules between connections and conduits:
This Connection Type Optical Fibre, Coaxial Cable, Twisted Pair Microwave Leased Line Is Compatible with this Conduit Type Duct Microwave Leased Line
Viewing and Editing the General Properties of an Edge Group or Edge

As well as having properties specific to each separate module, edge groups and edges all have the same general properties displayed on the General tab. To view or edit these: 1 Double-click the required edge. - or In the Network Browser, select the required edge, click with the right mouse button, and from the menu that appears, click Show Details. 2 3 The edge group dialog box opens. To edit the general properties of the edge group, click the General tab. - or To edit the general properties of an edge, click the required edge in the tree, and then click the General tab. 4 On the General tab, you can edit the following properties:
Item Name (ID) Connected Nodes Comments Change History Description The name of the edge group/edge. The equipment nodes, cabinets and Properties connected by the edge group/edge. Any additional planning comments. Details of when the edge group/edge was created and last modified.
5
Page 76
Click Apply or Commit to save your changes.

You can also view or edit the general properties of edges in the Network Browser.
Viewing or Editing the General Properties of Edge Groups Using the Network Browser
You can use the Network Browser to view or edit the general properties of edge groups. To do this: 1 2 3 4 In the Network Browser, select Module view. Expand the module and layer containing the edge, and then click with the right mouse button on the Equipment node. From the menu that appears, point to Active view, then click Show details. In the dialog box that appears, edit the properties and then click OK.
Controlling the Display

This section describes the ways in which you can customise the display in the module view window. For information on the separate module view toolbars, see the separate module chapters.
Selecting Items in the Module Window

You can select items in a variety of ways. The following table summarises the options available:
To do this Select individual items in the Module Window Do this Click the Select button - or 1. 2. In the Network Browser, ensure you have the correct view open either Module View for edge groups or Property View for equipment. Navigate to the required element by expanding modules and layers (for edge groups) or Properties and cabinets (for other network elements). Select the required item, click with the right mouse button and from the menu that appears, click either Select in Active View (to select the item in the currently active module window) or Select in All Views (to select the item in all of the module windows simultaneously). , and then click the required item.
3.
Select a group of items in the Module Window
Hold down the Control key, and click on each element that you want to select. - or 1. Click and hold down the left mouse button on the map where the centre of the box will be and drag the mouse to create a box around the network elements that you want to select. 2. Release the mouse button.
Select all of the items in the Module Window Select all of the equipment nodes in the Module Window
From the Edit menu, click Select All. 1. From the Edit menu, point to Select Nodes. 2. Click All.
Page 77
To do this
Do this
Select equipment nodes based on their equipment 1. From the Edit menu, point to Select Nodes. type in the Module Window 2. Click By Equipment Type. 3. In the dialog box that appears, select the equipment types and click OK. Select all of the edges in the Module Window 1. From the Edit menu, point to Select Edges. 2. Click All. Select all of the external network edges 1. From the Edit menu, point to Select Edges. 2. Click External Segments. Select all of the internal network edges 1. From the Edit menu, point to Select Edges. 2. Click Internal Segments. Select an individual network element and view it in Set this in the network Preferences. a number of Module Windows
Locating Network Elements and Edges

In a dense and cluttered network plan, it can be difficult to find a particular network element. However, you can use the search node function or the Network Browser to find a particular network element quickly. To do this: 1 From the Edit menu, click Search. - or In the Network Browser, click the Search button. 2 3 In the dialog box that appears, in the Type box, select the type of element you want to search for. Enter the name of the element(s) as appropriate. You can search based on exact string (for example, Property_3), substring (for example, Property_) or regular expression. For information on searching by regular expression, see Examples of Using Regular Expressions in DIRECT on page 79. Tip : You can also search for exact names by selecting the Match Case checkbox. 4 A list of the items matching your search is displayed. Click with the right mouse button on the required item, and choose how you wish to locate it. This table describes the options available:
Choose this option Select in Network Browser Select in Active View Select in All Views Centre in Active View Centre in All Views To Highlight the item in the Network Browser. Select the item in the active Module Window. Select the item in all Module Windows. Select the item and place it in the centre of the active Module Window. Select the item and place it in the centre of all Module Windows.
You can locate equipment or edges in the Network Browser or Equipment Editor while you are in the module window. To do this:
Page 78
1 2
In the module window, select the required equipment or edge. Right-click, and from the menu that appears, click either Select in Browser or Select in Equipment Editor (equipment only), depending on where you want to locate the equipment. The selected equipment is located and displayed in the required location.
Examples of Using Regular Expressions in DIRECT

This table gives some examples of regular expressions that you might use in DIRECT:
Enter .* ^BSC.* ^MSC.*A$ ^RNC83(89|98)$ ^Manchester\d\d\.*A$ .*[A-F]$ To Find Everything All BSCs beginning with BSC. All MSCs beginning with 'MSC' and ending with the letter A. RNC8389 and RNC8398. All elements beginning with Manchester followed by two digits and an A. Elements with names ending in a,b,c,d,e,f or A,B,C,D,E,F unless you have selected the Match Case checkbox, in which case it only returns elements with names ending in A,B,C,D,E,F. BSC or MSC followed by an underscore, followed by exactly 4 digits, optionally followed by one letter. For example, this matches BSC_3671 and MSC_3671C, but does not match MSC_031A or BSC_0001TEST.
^(BSC|MSC)_[0-9]{4}[a-fA-F]{0,1}
Arranging Equipment
In DIRECT, you can arrange equipment nodes in a number of different ways. To arrange equipment: 1 2 In the module view window, select the equipment that you want to arrange. From the Layout menu, point to Arrange and then click one of the following options, depending on how you want to arrange the equipment:
Choose This Option Geographical. Orthogonal (Grouped By Property). Orthogonal. Circular. Import from View. In the dialog box that appears, select the module view you want to use as a basis, and click OK. Tip : To do this in the opposite direction, and use this module view as the basis for arranging equipment in other views, select Export to Views. In the dialog box that appears, select which module views you want to export this arrangement to, and click OK.
To arrange the equipment in this way Based on the co-ordinate locations of their parent Properties Orthogonally (at right-angles), grouped according to their Property Orthogonally (at right-angles) In groups of circles Based on the arrangement in another module view
Page 79
If required, you can change the co-ordinate location of a Property. This is useful to ensure that if you choose the Geographical option, the equipment moves to the correct location. To do this: 1 2 3 In the module view window, move the Property to the required location. Select the Property. From the Layout menu, point to Arrangement and click Set as Geographical Location. The Location details on the General tab for the Property are updated.
Aligning Equipment
In DIRECT, you can align equipment in a number of ways, based on how you want to arrange your module view. To align equipment using the module view window: 1 2 In the module view window, select the required equipment. From the Layout menu, point to Alignment and select the required option. This table describes the available options:
Click this Option Left Centre Vertically Right Top Centre Horizontally Bottom
To Align the Equipment In This Way With the selected equipment node furthest to the left. With the selected equipment node closest to the centre of the group, along a vertical line. With the selected equipment node furthest to the right. With the highest selected equipment node. With the selected equipment node closest to the centre of the group, along a horizontal line. With the lowest selected equipment node.
To centre an element using the Network Browser: 1 2 3 Ensure that you have selected Property view. In the list of Properties, expand the Property and cabinet containing the network element. Select the element and click with the right mouse button. From the menu that appears, point to either Centre in Active View or Centre in All Views. The required element is selected and placed in the centre of the Module Window(s).
Page 80
Arranging Edges
In DIRECT, you can arrange edges in a number of different ways. Displaying Edge Groups as Separate Lines In the module view window, multiple edge groups linking the same two nodes are not shown as separate lines by default. However, you can use the Auto Align function in order to display the edge groups as separate lines spread out evenly between the nodes. Note : You can also display separate conduit edges in this way. To do this: 1 2 Select the nodes connected by the edges. From the Layout menu, point to Edges and click Auto Align Edges. The lines for the separate edge groups are displayed individually. Arranging the Waypoints of Edge Groups Rather than displaying the waypoints of the edge groups in the default, non-standard way, you can straighten out all of the waypoints by arranging them at right angles. To do this: 1 2 Select the required edge groups. From the Layout menu, point to Edges and click Right Angle.
To delete all the waypoints of an edge group so that it displays as a single straight line between the two connected nodes: 1 2 Select the required edge group. From the Layout menu, point to Edges and click Delete Waypoints.
Showing and Hiding Layers and Edge Groups

In the Module View dialog box, you can select which layers and edge groups are displayed. To do this: 1 2 3 4 In the current module view window, click the Module View button Click the Filter Options tab. In the Edge Selection pane, click the + sign next to the layer containing the edge group that you want to display. Choose the elements that you wish to display by selecting the appropriate checkboxes: 5 If you select a layer, all of its edge groups will be displayed in the appropriate module view window If you do not select a layer, only the individual edge groups that you select will be displayed .
Click Apply, and then click Close.

Page 81
Displaying Edges and Nodes Based On Properties, Cabinets or Equipment

In DIRECT, you may want to limit the number of edges and/or nodes that are displayed, by selecting just those edges/nodes relating to a specific Property, Cabinet or Equipment. To do this: 1 2 3 4 In the required module, click the Module View button Click the Filter Options tab. Select the Property, cabinet or equipment whose edges/nodes you want to view. Right-click, and from the menu that appears, click either Selected Connected Edges or Selected Connected Nodes as appropriate. .
Note : If you select the Selected Connected Nodes option, all of the edges connected to the nodes will be displayed as well. In the module view window, only the edges/nodes for the selected Property, cabinet or equipment are displayed.
Colouring Edges Based on their Attributes

In DIRECT, you can set edges to appear in a certain colour based on particular attributes of the edge. For example, in capacity planning, it is useful to know when the average traffic utilisation of an edge reaches a particular threshold. You can therefore set the display properties for an edge to appear in a certain colour according to traffic utilisation. Alternatively, you may want edges to appear in a certain colour according to circuit utilisation, or based on the specific edge type. To do this: 1 2 In the Transmission, PDH or SDH/SONET module view window, click the Module View button . In the dialog box that appears, click the Format tab. Under the Edge Colour heading, if you want to colour the edges according to the colours set on the Colours tab of the Preference dialog box, select the Colour by Edge Type Preferences option.
Page 82
- or If you want to colour the edges according to their traffic or circuit utilisation: Select the appropriate option for either average or worst utilisation. Double-click the threshold value, and type the minimum percentage at which you want the display colour to be shown. Note : All values below the threshold are displayed in black. Double-click the colour, and in the dialog box that appears, select the required colour and click OK.
In this example, any edge that has an average traffic utilisation above 85% will be displayed in red:
Click Apply.
Note : If a single sub-edge exceeds the threshold, then the entire group edge is coloured. Also, the colour appears on the Traffic tab for the edge.
Assigning Network Labels in Module Windows

Network labels can be used to display equipment, edge, cabinet and Property information in the module windows. To assign labels: 1 2 3 In the current module window, click the Module View button In the dialog box that appears, click the Format tab. Select the required labels for each category in the Labels pane: .
Tip : You can display more than one label for an element. 4 Click Apply.
Page 83
About Displaying Data in Module Views

You can customise the display in a module view to change the way that your plan looks and what information is displayed. This can make your planning easier and more precise, as well as improving the appearance of the plan for presentation purposes.
Zooming In and Out on the Module View

There are a number of ways of zooming on the module view: Magnifying by Two Use the zoom in and zoom out buttons to magnify or shrink the current display in the module view by a factor of two. Selecting an Area to Zoom on To select an area to zoom in or out on: 1 2 3 Click the right mouse button on the module view, and click Mouse Zoom. Click and hold down the left mouse button on the map and drag the mouse to create a rectangle. Release the mouse button and the module view redraws to display only the area selected.
Zooming to a Set Factor To zoom to a set multiplication factor or percentage: Click the right mouse button in the module view, and point to Zoom Percent, the size option you want and then click the required percentage. This table describes the size options:
Item Overview Normal Detail Description Zooms out by a large percentage, so you can look at the plan as whole in overview. Zooms in by an average percentage, so the plan remains a normal size. Zooms in by a large percentage, so you can look at a small part of the plan in detail.
Zooming to the Size of the Module View or a Defined Size To zoom the plan to remain in proportion to the size of the module view: Click the right mouse button in the module view, and click Zoom to Fit. To zoom the plan to a selected area: 1 2
Page 84
Click the Select button
, and select the area that you want to zoom in on.
Click the right mouse button in the module view, and click Zoom to Selected.
Zooming Using the Network Browser To zoom to a particular edge group using the Network Browser: 1 2 3 4 Ensure that you are in Module View. Navigate to the required edge group by expanding the modules and layers. Select the edge group, and click with the right mouse button. From the menu that appears, click either Zoom in Active View (to zoom in on the currently active module view) or Zoom in All Views (to zoom in on all views simultaneously).
Resizing a Network Plan

As you create your plan, you can resize it to suit your requirements. For example, in modules where there is a large density of network elements you may want to enlarge your view to see things more clearly, whereas in modules with large spaces between network elements you could reduce the size of the plan. You can also choose to stretch your plan in a number of different ways. For example, you can do any shrinking and enlarging by stretching it to normal size. You can also stretch a network plan to fill the size of the module view, or stretch a selected portion of your plan that is particularly cluttered. Note : Resizing retains the thickness of edges and nodes. Enlarging and Shrinking To enlarge your network plan, from the View menu, point to Stretch and click Enlarge. This increases the length of the segments in your plan by one zoom size without changing the size of the nodes. To shrink your network plan, from the View menu, point to Stretch and click Shrink. This reduces the length of the segments in your plan by one zoom size without changing the size of the nodes. Note : The size of the module view does not change. Stretching In DIRECT, it is possible to stretch your plan in a number of ways. You can stretch a plan to its normal size, to undo any shrinkage or enlargement, stretch it to fit proportionally in the module view or stretch a selected area. To stretch your plan to normal size: 1 2 1 2 Ensure the current module view is selected. From the View menu, point to Stretch and click To Normal. Ensure the current module view is selected. From the View menu, point to Stretch, then point to Stretch To and then click the required percentage.
Page 85
To stretch your plan to a specific size:
Redrawing the Module Window

To redraw or refresh the information shown in the module window, for example when you have many new things to display: In the module window, from the View menu, click Refresh.
Showing and Hiding Properties and Cabinets

In the Module View dialog box, you can select: Which specific Properties and cabinets are displayed - or Which categories of Properties and cabinets are displayed To open the Module View dialog box: In the current module window, click the Module View button To select specific Properties and cabinets: 1 2 3 4 Click the Filter Options tab. In the Node Selection pane, click the + sign next to the region containing the Property/cabinet that you want to display. If required, click the + sign next to the Property containing the cabinet that you want to display. Select the elements that you wish to display by selecting the appropriate checkboxes: 5 1 2 If you select a Property, it will be shown in the Property view and all of its cabinets and equipment will be shown in the Detail view. If you do not select a Property, but select specific cabinets, just the cabinets and equipment will be shown in the Detail view. If you do not select a Property or a cabinet, only equipment that you select will be shown in the Detail view. .
Click Apply, and then click Close. Click the Format tab. In the Show Properties pane, select which Properties you want to display - all Properties containing equipment, only those containing multiple equipment or only those containing multiple cabinets. In the Show Cabinets pane, select which categories of cabinets you want to display - no cabinets, all cabinets containing equipment or only those containing multiple equipment. Click Apply.
To select categories of Properties and cabinets:
Page 86
Creating Module Views Based on Routes

In DIRECT, you can create module views based on a particular route in a specific module. For example, you may want to create a route view from an edge in the Traffic module to see where it is routed in the SDH and PDH modules. To do this: 1 2 3 In the active module view or in Module View of the Network Browser, select an edge that has been routed. Right-click and from the menu that appears, point to Create Route View and then click the module view that you want to create. In the dialog box that appears, select the route for which you want to create a module view. A new module view appears, displaying the selected edge and all related network elements which form part of the chosen route (nodes, other edges, and so on).
About Using the Task Pane

You can use the Task pane to: Automatically generate a network topology Export data and/or import data Generate reports To display this dialog box, click the Task pane button .
Tip : This is a toggle button, so click it again when you want to remove the Task pane. You can also slide the Task pane back and forth across the screen, by hovering the cursor over the edge, and then holding down the left mouse button and shifting the cursor back and forth.
Using the Automatic Topology Generator

On the ATG tab of the Task pane, you can add and edit links in a number of ways: By generating simple network topologies automatically - choose from Ring/Loop, Star/Hub, Tree, Bus or Mesh. By duplicating the topology from one layer of the network to any other network layer. By adding, removing and setting edges on an existing edge group. By planning access networks. You can automatically create BSC/RNC nodes and areas, to create more realistic models.
Page 87
This picture shows an example ATG tab:
Automatic Topology Generator tab
Page 88
Generating Network Topologies Automatically

In DIRECT, you can link up your equipment with edges in pre-defined network topologies. There are five standard models, as shown in this picture.
Standard topology diagrams (clockwise from top left) : Mesh, Star, Ring, Bus, Tree
This table describes the five topology models:

Model name Mesh topology Star topology Ring topology Bus topology Tree topology Description Each edge is connected to every other edge in the network. Each edge is connected to a central 'hub' node. Each edge is connected to two adjacent edges, forming a circle or ring. Each edge is connected to one other adjacent edge, forming a longer string of edges. Edges are connected in a minimum spanning tree.
To generate one of these topologies: 1 2 3 4 Ensure you are displaying the Task pane, and that the ATG tab is visible. In the module view window, select the nodes that you want to link. In the Task pane, click the button corresponding to the topology that you want to create. If you are creating a star topology, select the hub node, and click OK.
Page 89
Duplicating Edges Between Modules

On the ATG tab of the Task pane you can duplicate edges from one module to another, and in this way model the topology of that module. For example, you may want to create transmission segments to match the layout of your E1/STM-1 edges. To do this: 1 In the Duplicate pane, select the edges you want to duplicate - all of the edges of the module, a group of selected edges, or all of the edges between a group of selected nodes. Note : You need to select the edges yourself in the appropriate module view window. 2 In the Target Layer pane, select the Target layers which you want to have the duplicate edges in: 3 All layers Only the Target layer that has been set All other layers apart from the Target layer
In the Source Layer pane, select the Target layer(s) if required both the layer containing the edges that you want to duplicate (From Layer), and the layer in which you want the duplicated edges to appear (To Layer). Note : If you have selected edges in a particular module view window, the module will be automatically selected as the From Layer.
4 5 6
If you do not want to overwrite any edges that already exist, select the Only if edge doesnt exist checkbox. Click the Duplicate button. In the dialog box, select the edge type from the list available, and then click OK. Tip : If you want the edges to be all of the same type, select the Use edge type for all edges (if possible) checkbox before you click OK.
Adding, Removing and Setting Edges on an Existing Edge Group

On the ATG tab of the Task pane you can add, remove and set a specific number of edges on an existing edge group. To do this: 1 2 Select the edge group you want to add to, remove from or set to. In the Add/Remove pane, follow the instructions in this table depending on what you want to do:
If you want to Add edges to an existing edge group Do this 1. Select the Add option. 2. Type the number of edges you want to add. 3. Click the Add/Remove button. Remove edges from an existing edge group 1. Select the Remove option. 2. Type the number of edges you want to remove. 3. Click the Add/Remove button.
Page 90
If you want to Set the edges for an edge group to a specific number
Do this 1. Select the Set to option. 2. Type the number of edge that you want to set the edge group to. Note : This can be lower, higher, or the same value as the edge group presently contains. If you set it higher, the additional edges will be added to the edge group, while if you set it lower the additional edges will be removed from the edge group. 3. Click the Add/Remove button.
Planning Access Networks Using the ATG

On the ATG tab of the Task pane you can plan access networks - RNC, BSC or DXT. You can use internal algorithms to calculate a suitable amount of BSCs or RNCs for the selected BTSs, or a suitable amount of DXTs for the selected TBSs, based on the network capacity values. To do this: 1 2 3 Select the BTS node(s) (or TBS node(s)) for which you want to plan. In the Task pane, on the ATG tab, click the required button - RNC Area, BSC Area or DXT Area. If you are planning RNCs, in the dialog box that appears, set the maximum number of TRXs per RNC, and click OK. - or If you are planning DXTs, in the dialog box that appears, select the DXT equipment type, and click OK. Note : If you are planning BSCs, this dialog box will not appear. 4 DIRECT calculates the number of BSCs or RNCs required, add these and then connects the BTS nodes to them in appropriate groupings.
Exporting and Importing in DIRECT

In the Task pane, you can export and import data from and to DIRECT. To export data: 1 2 Click the Export tab. Select the data you want to export. You can export from a number of categories, including Connection Types, Routes and Node Data. Tip : To expand the data layer to reveal the more detailed categories, click the + sign. To select or unselect all of the details for a category, click with the right mouse button on the category name, and choose Select All or Unselect All as appropriate. See Data For Import and Export in DIRECT on page 93 for a summary of the data that you can import and export. 3 Type the filename that you want to use for the export file. - or Click the Browse button
, and locate the required file.

Page 91
4 5
Select the file type of the export (Comma separated values in a text file, an Excel spreadsheet, a Plain Text file, or an XML file). Click the Export button. DIRECT will export the data in the required format. The DIRECT message log details the success or failure of the export.
To import data: 1 2 Click the Import tab. Select the data you want to import. You can import from a number of categories, including Connection Types, Routes and Node Data. Tip : To expand the data layer to reveal the more detailed categories, click the + sign. To select or unselect all of the details for a category, click with the right mouse button on the category name, and choose Select All or Unselect All as appropriate. See Data For Import and Export in DIRECT on page 93 for a summary of the data that you can import and export. Important : If you want to import module parameters, you should only select these, as you cannot import anything else simultaneously. 3 If you want to update existing data items, select this checkbox. If you choose this option, imported data items are merged with existing data items with the same name. Important : If you are importing module parameters, you should select this option. 4 Type the filename of the import file. - or Click the Browse button 5 , and locate the required file.
Select the file type of the import (Comma separated values in a text file, an Excel spreadsheet, a Plain Text file, or an XML file). You can upgrade older XML versions if required. Important : If you are importing module parameters, you should select commaseparated values.
Click the Import button. DIRECT will import the data in the required format. The DIRECT message log details the success or failure of the report. Important : Objects which are duplicates of others already existing in the DIRECT project will not be imported.
Page 92
Data for Import and Export in DIRECT

You can import and export the following data categories and sub-categories in DIRECT:
Data category Equipment Library Data subcategory Equipment Folders, Traffic Logical Functionality, Defined Traffic Functionality, Transport Logical Functionality, Physical Element Type, Equipment Slot, Equipment Type Port, Cabinet Type, Patch Panel, Distribution Frame, Cabinet Template, Shelf Template, Equipment Template, Subrack Template, Cabinet Component Template, Port Template, XC Data Template. Traffic Service, Traffic Type, Budget, Budget Layer. Protocol Stack, Protocol Stack Layer, Service Access Point, Protocol Stack Connection, Operation Set, Operation Set Distribution, Destination, Protocol Primitive Header Type Coaxial Type, Leased Line Type, Optical Fibre Type, Radio Type, Twisted Pair Type, Satellite Type. Signalling Protocol, Signalling Service. Cac2 Parameter Map Entry ATM Module, IP Module, Lightpath Module, PDH Module, SDH/SONET Module, Traffic Module, Transmission Module, Module Parameters (ATM Default Parameters, IP Default Parameters, Cellular Parameter Data, Interswitch Parameter Data, External Network, Route Alternative, PSTN Parameter Data, Signalling Parameter Data, TETRA Parameter Data, Cell Layer Type, PDH Default Parameters). Region. Property, Pit, Cabinet, Shelf, Equipment Instance. Hyperlink, BSC Data, BTS Data, Interswitch Data, IswGeneric Data, IswTraffic Data, Isw Cs Core Data, Isw Voice Traffic Data, Node B Data, Preferred Node Data, PSTN Data, PSTN Exchange Data, RNC Data, TBS Data, Trx, External Network POI, Isw Generated Traffic, RNC Estimated Traffic, Routing Table Data, Served External Network, SHO Traffic Element, UMTS Cell, UMTS Traffic Element, Cell Layer, GSM Cell Data, Signalling Data, Routing Table, Signalling Traffic Data, Signalling SMSC Data, Location Update, Handover Data, Network Address, EDAP Pool Data, Workstation Data, Cross Connection Data, Codec Usage Data, Codec Conversion, Isw Prepay Data. AAL, AAL Group, VCC, VCC Group, VPC, VPC Group, VPT, ATM Queue, Queue Edge, VPT Group, IP Logical, IP Logical Group, Ethernet, IP Queue, Ethernet Group, Lightpath Edge, Lightpath Edge Group, PDH Edge, 2M, PDH Edge Group, SDH/SONET Edge, SDH/SONET Edge Group, Protection Loop, Loop Edge, Traffic Edge Group, Signalling Interface Edge Group, ISW Requirement Edge group, ISW Interface Edge Group, Signalling Requirement Edge Group, GSM Edge Group, GSM Traffic, GSM Traffic Group, Signalling Requirement Edge, Signalling Interface Edge, ISW Interface Edge, Bidirectional Generic Edge, Unidirectional Generic Edge, Gb Interface, UMTS Group, UMTS Control Plane, UMTS User Plane, UMTS Plane Group, Conduit Edge, Segment Group, Segment, PSTN Edge Group, PSTN Edge, TETRA Edge, TETRA Dispatch Edge, Edge Route Alternative. Traffic Edge, Template Traffic, Application Traffic Position, Traffic Container Position, Timeslot Allocation Template, Interswitch Traffic, Signalling Traffic, Interswitch Traffic Position, Erlang Traffic. Route, Route Hop.
Traffic Services and Types Protocol Stacks Header Types Connection Types Signalling Services Cac2 Parameter Map Entry Modules
Nodes Node Data
Edges
Traffic Data
Routes
Note : If you are importing transport edges (that is, any edges not created in the Traffic module) using an Excel spreadsheet, you do not need to include edge groups. When you import the edges, DIRECT automatically creates the required edge groups for them.
Page 93
Using Reports in DIRECT

You can use DIRECT to produce detailed reports showing profiles of different parts of your network. You can define your own reports, or use the ones provided by DIRECT. All reports are generated from a common tab, on which you can specify the level of detail you want to include in the reports. You can: Choose to generate reports for the entire plan or for the selected nodes or edges only Select the appropriate checkboxes to specify the information that you want to extract from DIRECT and include in the report Generate reports in Microsoft Excel or text format This picture shows an example Reports tab:
Reports tab
Page 94
Generating Reports
To generate a report: 1 In the Task pane, click the required tab: 2 Reports - if you want to generate one of the reports provided by DIRECT User Reports - if you want to generate a report that you have defined yourself
In the Select Report pane of the Reports tab or the reports pane of the User Reports tab, select the type of report that you want to display.
Tip : To expand a category to reveal the more detailed list, click the folder. 3 Select to generate this type of report for: All objects Only selected objects, in all views Only selected objects in the active view
4 5
Click Generate. Specify a filename and a location for the saved report, and then click OK. The report is generated, and displayed in either: MS Excel or Notepad, depending on what you have installed (for Reports) The format specified for that report type (for User Reports)
Page 95
This picture shows an example report in a Microsoft Excel spreadsheet.
This picture shows an example report in Microsoft Notepad.
Page 96
Organizing Reports
In DIRECT you can define your own types of reports, and group them in the most convenient way for your users. You define and group reports in the Organize Reports dialog box. This picture shows an example:
Example Organize Reports dialog box
To open the Organize Reports dialog box: 1 2 1 Click the Reports tab. Click the Organize button. In the Organize Reports dialog box: Click Add Folder. - or Right-click, and from the menu that appears, click Add Folder. A new report folder is created. 2 Select the new folder, and in the name box, type a name. Tip : It is recommended that you organize your reports in folders, which have useful, descriptive names. 3 Click Apply. For information on how to add reports to folders, see Defining Reports on page 98.
To create a folder:
Page 97
Defining Reports
In DIRECT, you can define your own reports, selecting which information they include and in what format they are displayed. To define a report: 1 2 In the Organize Reports dialog box, if required, select the folder to which you want to add the report. Click the Add Report button. - or Right-click, and from the menu that appears, click Add Folder. 3 4 5 In the Name box, type a name for the new report. In the Type box, select the general type of report you want to create. This will determine the Element Types and Fields that will be available for your report. In the Formatting File box, click the Browse button file: and locate a formatting
If you want to produce a report in other format apart from Crystal Reports, you must select an XML transformation file (*.xslt) If you want to produce a report in Crystal Reports format, you must select a Crystal Reports file (*.rpt)
Tip : You can also type the file path directly into the Formatting File box. 6 If you chose an XML transformation file: Choose the file type for the report, and the associated viewer that will be used to display the report. If the required option is not available, you can create your own file type/viewer combination. For information on how to do this, see Creating Filetype Associations on page 99. Important : The file type association that you select must be compatible with the format the XML transformation file creates. Choose which element types and fields will be displayed in the report.
Note : If you are defining a Crystal Reports-type report, you can only exclude element types and fields. 7 Click Apply.
Page 98
Creating Filetype Associations When you are defining a report, you can choose the file type you want to produce and an associated viewer with which to display the report. However, if a particular file type/viewer association is unavailable, you can create your own. To do this: 1 In the Organize Reports dialog box, from the File Type/Associated Viewer dropdown list, click [more ...]:
The Filetype Associations dialog box appears, displaying all current report file types and viewers:
To add a new association: 1 2 In the File Extension box, type the extension for the file type you want to use, for example xls. Select the associated viewer that you want to use for this file type: The Windows default. MS Excel.
Page 99
Another viewer of your choosing. Click the Browse button executable file for this viewer.
, and locate the
Click Add.
To edit an existing association, select it in the left-hand pane, change the details on the right hand side as required, and then click Apply.
Printing Network Plans

You can print the contents of a module window. To do this: 1 2 Ensure that the required module window is active by clicking in it, and the entire area that you wish to print is visible. From the Project menu, click Print Setup. Specify page orientation, size and source; change the printer, printer properties and number of copies. These settings will be retained as the default for your selected printer. Click OK. From the Project menu, click Print Title and Logo. In the dialog box that appears, you can define the logo and caption information for the printed plan. You can set the following options:
Item Text Box A Description Choose to display text in the left hand text box by selecting the checkbox. Defaults as the Title box (for the title of your network plan) but can be used for any text. Choose to display text in the centre text box by selecting the checkbox. Defaults as the Copyright box (for copyright information) but can be used for any text. Choose to display text in the right hand text box by selecting the checkbox. Defaults as the Comments box (for planning comments) but can be used for any text. Select whether or not to display a logo on the network plan. Click the Select Logo button, and from the menu that appears, either: Select a logo from the default list. - or Click Other, browse to the appropriate bitmap and click Open. Time and Date Select whether or not to display the time and date on which the network plan was printed.
3 4
Text Box B Text Box C
Logo
This picture shows an example section of a printed network plan:
5 6
Click OK. Select the area of your network that you want to print, by selecting the required network elements. If nothing is selected, then the printed network plan will show the entire network. Note : If you have Properties and cabinets displayed, these will be shown in the printed network plan even if you have not selected them.
Page 100
7 8 9
From the Project menu, click Print Preview and ensure that the network plan, logo and text are displayed correctly. When you are satisfied with the Print Preview, click the Close button, and then from the Project menu, click Print. Click OK.
Committing Network Elements in DIRECT

The procedure for committing network elements in DIRECT follows a strict order, which must be followed in order to correctly store these items in the master database. Each group of elements has a different order. Committing Nodes Node-related elements should be committed in the following order: 1 2 3 Properties. Cabinet. Equipment.
Committing Edges Edge-related elements should be committed in the following order: 1 2 3 Equipment at both ends of the edge. Edge groups. Edges.
Committing Conduits Conduit-related elements should be committed in the following order: 1 2 Properties at both ends of the conduit. Conduits.
Committed Routed Edges Routed edge-related elements should be committed in the following order: 1 2 3 4 Equipment at both ends of the edge. Edge groups. The lower level edges that the edge is routed onto. Edges.
As well as committing individual network elements, you can also commit entire networks, modules and layers.
Page 101
Committing, Restoring and Deleting Networks and Layers

As well as committing individual network elements, you can also use the Network Browser to commit the entire networks, or separate modules and layers. To commit a layer, and all of the elements contained in it: 1 2 3 1 2 3 Ensure that the Network Browser is displaying the Module View. Select the required layer, and click with the right mouse button. From the menu that appears, click Commit. Ensure that the Network Browser is displaying the Module View. Select the required module, and click with the right mouse button. From the menu that appears, click Commit. Click the Commit All button.
To commit a module, and all of the layers contained in it:
To commit all of the elements in a network:
Deleting Modules and Layers

As well as deleting single network elements, using the Network Browser you can also delete an entire module or layer from the network. To do this: 1 2 3 Ensure that the Network Browser is displaying the Module View. Select the required module or layer. Click with the right mouse button, and from the menu that appears, click Delete. The module or layer is deleted. Important : You cannot delete either the Transmission module or the Traffic module. Tip : To restore a network to its previously applied state, click the Restore All button.
Showing and Hiding Layers and Edges

In the Property view dialog box, you can select module layers and edge groups within layers to be hidden or displayed. To do this: 1 2 Click the Module View button .
In the dialog box appears, click the Filter Options tab. In the Edge Selection pane, select the required layers or edge groups that you want to display: Selecting a module will display all of the layers for that module Selecting a layer will display all of the edge groups for that layer If you do not select an entire module/layer, then you can display individual layers/edge groups
Page 102
In this example, in the first pane, all of the layers in the Traffic module will be displayed; in the second pane, all of the edge groups in the interswitch layer will be displayed; in the third pane, only interswitch requirement edge group 1 will be displayed.
Click Apply. Only the selected regions are displayed in the module window.
Creating and Using Regions

In DIRECT's Network Browser, you can create regions, and organise your Properties within regions. DIRECT supports regions based on physical area (in terms of the position of Properties rather than geographical co-ordinates). Creating regions is helpful in network planning because it enables you to divide a large network up into smaller sub-sections, and you can display and work on each region separately. To create a region: 1 2 In the Network Browser, ensure that you are in Region View. Click with the right mouse button, and from the menu that appears, click Add Region. A new region is created. 3 4 Click with the right mouse button on the required region, and from the menu that appears, click Show Details. In the dialog box that appears, you can specify the name of the region and add any additional planning comments (for example, the name of the planner(s)) responsible for this region. Click Apply, and then click Close.
Unassigned Properties and pits are displayed beneath regions:
You can assign Properties and pits to regions in two ways: Using the Network Browser Using the Transmission module Property view window
Page 103
Assigning Properties and Pits to Regions in the Network Browser

After you have created a region, in the Transmission module Property View window, you can assign Properties and pits to a region. To do this: 1 2 3 4 Select the Properties and pits that you want to assign to a region. Click with the right mouse button, and from the menu that appears, click Add to Region. In the dialog box that appears, select the required region, and then click OK. The Properties and pits are added to this region.
Assigning Properties and Pits to Regions in the Transmission Module

After you have created a region, in the Transmission module Property View window, you can assign Properties and pits to a region. To do this: 1 2 3 Select the Properties and pits that you want to assign to a region. Click with the right mouse button, and from the menu that appears, click Add to Region. In the dialog box that appears, select the required region, and then click OK. The Properties and pits are added to this region.
Showing and Hiding Regions

After you have assigned Properties and pits to regions, you can then select certain regions to be hidden or displayed. To do this: 1 2 3 Click the Module View button .
In the dialog box appears, click the Filter Options tab. In the Node Selection pane, select the required regions that you want to display:
Click Apply. Only the selected regions are displayed in the module window.
Page 104
CHAPTER 4
Creating and Using Equipment

DIRECT uses a number of equipment entities, which are explained in the following table:
Item Cabinet Rack Description The storage unit for all equipment. Cabinets contain Racks. Containers within a Cabinet. Racks can contain Equipment Types, SubRacks and/or Shelves. Racks are automatically created when you create a Cabinet. Equipment Type Equipment entities that designate the equipment functionality - possible connection types, sub-equipment and other parameters. An Equipment Type can contain one or more Subracks, which have backplane connectivity. Containers for IFCs. Its dimensions are based on the size of the Cabinet, and it is divided into fixed size Slots. Slots contain Cards. Containers within a Rack. Shelves contain Equipment Units. Shelves are automatically created when you add an Equipment Unit to a Cabinet. Equipment Unit Equipment entities that can be connected together with a bus. Unlike Equipment Types, Equipment Units can contain their own Ports, as well as SubRacks. In DIRECT, Equipment Units are automatically placed on Shelves. An example of an Equipment Unit is a Router. Also known as an Equipment Node. Card A piece of hardware that provides the physical or logical interface of the cabinet with external network elements via Ports and connecting edges. Also known as an Interface Card (or IFC). Passive Equipment Stored inside the Cabinet, and used for cross-connections. Passive Equipment is used to model Patch Panels and Distribution Frames.
SubRack Shelf
Page 105
This picture shows the DIRECT equipment structure.
DIRECT Equipment Cabinet Model
You will create different sorts of equipment entities, depending on what type of network planning you are doing. This table describes what you need to create:
For this type of planning Nominal Planning Detailed Planning You will need to create Equipment types only. All equipment entities, and any templates of equipment configuration that you require.
In This Section
About the DIRECT Equipment Editor About Equipment in DIRECT Creating New Logical Traffic Equipment Types Creating Logical Transport Equipment Types Creating Physical Element Types Making Global Changes to Equipment Using the Equipment Browser Locating Equipment 107 108 109 111 115 122 124 125
Page 106
About the DIRECT Equipment Editor

You can use the Equipment Editor to: Create your own generic vendor-independent equipment, with defined functionality. Design card, equipment, rack, multi-subrack and cabinet templates. Create your own card and equipment types (containing information about possible connections, slots and ports), including equipment that contains subequipment. This picture shows an example:
Store equipment costs, which can then be extracted in reports. Add individual serial numbers, enabling you to track equipment through the network. Store equipment in folders.
Page 107
About Equipment in DIRECT

In DIRECT, equipment is divided into two categories: Equipment with logical functionality (either traffic or transport) Physical element types You can add and edit logical functionality equipment in the existing folders, and subdivide equipment for use in either all projects, or just the currently loaded project. Within the All projects and Current project folders, you can add and edit physical element types within their own sub-folders - cards, subracks, equipment units, multisubrack equipment, passive equipment and cabinets. To open the Equipment Editor, click the Open Equipment Editor button in the Equipment Browser. Note : To close the Equipment Editor when you have finished, click the Close Equipment Editor button. You are returned to the Equipment Browser. If you are new to DIRECT, it is recommended that you follow the work order set out below when creating equipment for the first few times: 1 2 Create logical traffic and transport equipment types. Create the physical element types that your network will require: Interface cards. Equipment units. Important : These should be configured according to the manufacturer's specifications. 3 4 5 6 Subracks.
Allocate slots to the interface cards on the racks. Create passive equipment, if required. Create a cabinet. Place the subracks, passive equipment and equipment units inside the cabinet via a cabinet template.
Important : As it is listed in the GSM group, the MSC logical equipment type only supports GSM interfaces (A-ter and A). To give an MSC physical element type interswitch and signalling functionality, you must create GSW and STP logical equipment types (respectively) and ensure the functionality of these is selected on the MSC. For more information, see Setting the Traffic/Transport Functionality for Physical Element Types on page 117.
Page 108
Creating New Logical Traffic Equipment Types

To create a logical traffic equipment type, you must: 1 2 Create a logical traffic equipment group, which you can then use as a template to create a number of similar equipment types. Create a detailed logical traffic equipment type, based on a particular group. You can create a number of different equipment types for different networks - for example, for a GSM network you can create BSCs, BTSs, TRAUs and so on, while for interswitch (ISW) networks you can create EXT, IVR and VMS nodes and so on. In the Equipment Editor, select the folder matching the required equipment group, for example the GSM BSC folder available to all projects:
To create the logical traffic equipment group: 1
2 3 4
Right-click, and from the menu that appears, click Add New. On the General Tab, type the name for the new logical traffic equipment group. In the Node types pane, select the equipment types that you want to allow to connect to the new equipment group. If required, double-click in the No allowed column and set the limit on the number of the equipment type that can be connected. Important : The number of types allowed should normally be smaller than the number of edges allowed.
5 1 2
Click Apply. In the Equipment Editor, select the equipment group that you want to use as a template. Right-click, and from the menu that appears, click Add Detailed Type.
To create a detailed logical traffic equipment type:
A new equipment type based on the equipment group is created. 3 4 On the General tab, type the name for the new logical traffic equipment type. On the equipment-specific parameters tabs, enter the appropriate details for the equipment type you have created. For more information on these tabs, see About the Additional Parameters Tabs For Logical Traffic Equipment on page 110.
Creating Logical Traffic Equipment Types Based On Existing Ones

Rather than creating a completely new logical traffic equipment group or type, you may want to use an existing one as the basis for a new one. To do this: 1 2 3 4 Select the existing logical traffic equipment group or type. Right-click and from the menu that appears, click Copy. Select the folder into which you want to add the new equipment. Right-click and from the menu that appears, click Paste.
About the Additional Parameters Tabs for Logical Traffic Equipment

Some of the logical traffic equipment types will have an additional tab, which provides some extra parameters specific to that equipment type.
About the BSC Parameters Tab

In the Equipment Editor, on the BSC Parameters tab for a BSC, you can edit the following details:
Property Submultiplexing (channels per trunk) Maximum number of TRXs PCU Switching Capacity PCU TCH Capacity PCU TRX Capacity PCU Cell Capacity Description The submultiplexing capacity of the BSC node, expressed in the number of channels per trunk. The maximum number of TRXs that can be supported by the BSC. The packet switching capacity of the PCU unit, in Mbits per second. The maximum number of traffic channels that can use the same PCU. The maximum number of TRXs that can use the same PCU. The maximum number of simultaneous cells that can be attached to the same PCU.
About the BTS Parameters Tab

In the Equipment Editor, on the BTS Parameters tab for a BTS, you can edit the following details:
Property Family name BCF Signalling Rate Description The equipment family that the BTS is assigned to. The value of the signalling rate for the BTS.
About the SGSN Parameters Tab

In the Equipment Editor, on the SGSN Parameters tab for an SGSN, you can edit the following details:
Property PAPU switching capacity (Mbit/s) Description The bit-switching capacity of the selected PAPU unit, in Mbits per second.
Page 110
Property PAPU subscriber capacity (#) SMMU subscriber capacity (#)
Description Maximum number of active users attached to the selected PAPU unit. Maximum number of active users attached to the SMMU unit.
About the PSTN Parameters Tab

In the Equipment Editor, on the PSTN Parameters tab for a PSTN Access node or a PSTN Local Exchange node, you can edit the following details:
Property Maximum number of trunks Description The maximum size of a trunk group that can connect the node upwards. Note : This value depends on the capacities of the equipment used and directly affects the concentration capability of the node. If the limit is exceeded, the traffic has to be divided into multiple equipment, each piece being concentrated individually. If this happens, more capacity is required, since concentration is more efficient over a large number of users and lines.
About the DXT Parameters Tab

In the Equipment Editor, on the DXT Parameters tab for a DXT, you can edit the following details:
Property Maximum number of TRXs Maximum number of DWSs Description The maximum number of TRXs that can be attached to the same DXT. The maximum number of DWSs that can be attached to the same DXT.
About the RNC Parameters Tab

In the Equipment Editor, on the RNC Parameters tab for an RNC, you can edit the following details:
Property Maximum bit throughput Description The maximum data speed in kbit/s.
Creating Logical Transport Equipment Types

To create a logical transport equipment type: 1 2 In the Equipment Editor, select the folder matching the required equipment group, for example AALT. Right-click, and from the menu that appears, click Add New Type:
On the General Tab, type the name for the new logical transport equipment type.
Page 111
Click the Transport Interfaces tab, and in the Interfaces pane select the edge types that you want the new equipment type to support. If required, double-click in the No allowed column and set the limit on the number of edges of that type that the equipment can support. In the example below, the AALT supports any number of PDH 1.5M and 2M edges, but only up to five 4M edges.
On the equipment-specific parameters tabs, enter the appropriate details for the equipment type you have created. For more information on these tabs, see About the Additional Parameters Tabs For Logical Transport Equipment on page 112.
Click Apply.
Rather than creating a completely new logical transport equipment type, you may want to use an existing one as the basis for a new one. To do this: 1 2 3 4 Select the existing logical transport equipment type. Right-click and from the menu that appears, click Copy. Select the folder into which you want to add the new equipment. Right-click and from the menu that appears, click Paste.
About the Additional Parameters Tabs For Logical Transport Equipment

Some of the logical transport equipment types will have an additional tab, which provides some extra parameters specific to that equipment type.
About the ATM Parameters Tab for an AALT

In the Equipment Editor, on the ATM Parameters tab for an AALT or WAM, you can edit the following details:
Property Maximum AALs per VCC Processing delay (ms) Timer CU (ms) CPS Packet Description The maximum number of AALs that a VCC can contain. The total delay caused by processing. The internal VCC multiplexing delays between the AAL2 multiplexer and the AALT. If the Shaped option is selected, the packets are shaped locally at the node containing the AALT.
About the ATM Parameters Tab for an ATM AXC

In the Equipment Editor, on the ATM Parameters tab for an ATM AXC, you can edit the following details:
Property Maximum AALs per VCC Processing delay (ms) Description The maximum number of AALs that a VCC can contain. The total delay caused by processing.
Page 112
Property Timer CU (ms) Maximum number of crossconnections CPS Packet Allow AAL, VCC, VPC crossconnections
Description The internal VCC multiplexing delays between the AAL2 multiplexer and the AXC equipment. The maximum number of cross connections that the AXC can contain. If the Shaped option is selected, the packets are shaped locally at the node containing the AXC. Select the required checkboxes to enable you to create different types of crossconnections at this AXC.
About the IP Parameters Tab

In the Equipment Editor, on the IP Parameters tab for an IP Router, you can edit the following details:
Property Maximum bit throughput (Mbits/s) Description Maximum limit of the incoming and outgoing bitstream that the node can handle.
About the PDH Mux Parameters Tab

In the Equipment Editor, on the PDH Mux Parameters tab for a PDH Mux, you can set the multiplexing levels. To do this: 1 2 Click the PDH MUX Parameters tab. For each type of multiplexing level (ETSI, ANSI etc.): 3 Select the multiplexing scenarios you want to enable If you want to limit the number of times that a scenario can be used, doubleclick the Limit column and type the maximum number
Click Apply.
About the PDH XC Parameters Tab

In the Equipment Editor, on the PDH XC Parameters tab for a PDH XC, you can set the cross-connections. To do this: 1 2 3 Click the PDH XC Parameters tab. If you want the PDH cross-connections to have protection termination points, select the Can protect option. For each type of cross-connect level (ETSI, ANSI etc.): 4 Select the data rates you want to enable If you want to limit the number of cross-connects at a data rate, double-click the Limit column and type the maximum number
Click Apply.
Page 113
About the SDH/SONET ADM Levels Tab for SDH/SONET Equipment

In the Equipment Editor, on the SDH/SONET ADM Levels tab for SDH/SONET equipment, you can set the add/drop multiplexing levels. To do this: 1 2 Click the SDH/SONET ADM Levels tab. For each type of multiplexing level: Select the levels at which the equipment can add and drop If you want to limit the number of times that the equipment can add/drop multiplex at this level, double-click the Limit column and type the maximum number
In this example, any number of SDH add/drop multiplexes are allowed at the VC12 level, and additionally 4 at VC-3 level:
Click Apply.
About the SDH/SONET XC Levels Tab for SDH/SONET Equipment

In the Equipment Editor, on the SDH/SONET XC Levels tab for SDH/SONET equipment, you can set the cross-connecting levels. To do this: 1 2 Click the SDH/SONET XC Levels tab. If you want the SDH cross-connections to have protection termination points and/or MS Spring protection, select the Path Protection and/or Supports MS Spring option(s). For each type of cross-connect level: Select the data rates you want to enable If you want to limit the number of cross-connects at a data rate, double-click the Limit column and type the maximum number
Page 114
In this example, any number of SDH VC-11 cross-connects are allowed, plus 4 VC3 cross-connects:
Click Apply.
About the WAM Parameters Tab

In the Equipment Editor, on the WAM Parameters tab for a WAM, you can edit the following details:
Property User Plane Aal2 Vccs Number of Iub NBAP-C Connections Number of Iub NBAP-D Connections Number of Iub AAL2 Signalling Connections Description The number of AAL2 VCCs that this WAM supports on the user plane. The number of Iub NBAP-C connections that this WAM can support. The number of Iub NBAP-D connections that this WAM can support. The number of Iub AAL2 signalling connections that this WAM can support.
Creating Physical Element Types

In the DIRECT Equipment Editor, you can create physical element types, such as cards and subracks. To do this: 1 2 3 4 5 1 2 3 Select the Physical Element Types folder or sub-folder in which you want to add your equipment. Right-click, and from the menu that appears, click Add new type. In the dialog box that appears, select the required element type and click OK. On the General tab, type the name of the element type and other general properties as appropriate. To finish creating your element type, see the relevant section below. Set the traffic and transport functionality. Set the transport interface compatibility. Configure the ports.
Page 115
To create a card type:
To create a subrack type: 1 2 1 2 3 Set the traffic and transport functionality. Configure the slots. Set the traffic and transport functionality. Set the transport interface compatibility. Configure the ports. Configure the subracks. To create a passive equipment type (either a distribution frame or a patch panel): Configure the passive equipment parameters. To create a cabinet type: Create a cabinet template. Rather than creating a completely new element type, you may want to use an existing element type as the basis for a new one. To do this: 1 2 3 4 Select the existing element type. Right-click and from the menu that appears, click Copy. Select the folder into which you want to add the new equipment. Right-click and from the menu that appears, click Paste.
To create an equipment unit type:
To create a multi-subrack type:
Setting the General Properties for Physical Element Types

On the General tab for a physical element type, you can set the general properties as described in the following table:
Item Name Manufacturer Part number Cost Size Description The name of the physical element type. The equipment manufacturer. The equipment part number. The equipment cost. The size of the equipment, which relates to: Cards - the number of slots required on a rack Subracks and Passive Equipment - the conceptual size, in units Cabinets - the amount of equipment that can be placed inside Maximum number of racks (cabinets only) Colour Text The maximum number of racks that can be contained within the cabinet. The colour of the symbol. To edit this, click the Change button and select the required colour from the palette that appears. The text that will be displayed with the symbol.
Page 116
Setting the Traffic/Transport Functionality for Physical Element Types

When you add a physical element type in the Equipment Editor, you can set the logical traffic and transport equipment functionality that it will carry. To do this: 1 2 Click the Traffic Functionality tab. Expand the traffic equipment types, and the select the functionality you want to give the element type:
Tip : To view a summary of a particular traffic equipment type, right-click it and from the menu that appears, click Summary, or to browse to it in the Equipment Editor, click Go To. When you select an equipment type, it appears in the Selected Transport Functionalities pane. Important : For certain network scenarios, you must set particular logical functionality on specific physical element types. For information on these, please see Setting Traffic/Transport Functionality for Particular Network Scenarios on page 117. Tip : To quickly remove an equipment functionality, select it in the Selected Transport Functionalities pane, and click Remove. 3 Click the Transport Functionality tab. Expand the transport equipment types, and select the functionality you want to give the element type in the same way. 4 Click Apply.
Setting Traffic/Transport Functionality for Particular Network Scenarios

For particular network scenarios, you need to set the traffic/transport functionality in a specific way on the physical element type. This table describes these requirements:
For This Network Type Interswitch Signalling You need to set this logical functionality GSW SSP On this physical element type MSC, WMSC, CS-MGW MSC, WMSC, CS-MGW
Page 117
Setting the Transport Interface (Edge) Compatibility for Physical Element Types
When you add a physical element type in the Equipment Editor, you can select which transport interfaces (edges) it is compatible with. To do this: 1 2 3 Click the Transport Interface tab. Select the edge types which you want to make compatible with the element type. If you want to limit the number of edges of a particular type that can be utilised by the element type, double-click the No. allowed column and type the number:
Click Apply.
Defining Ports for Physical Element Types

On the Ports tab for a piece of equipment, you can set the number of ports for physical element types, define the maximum available bandwidth for each port and the media type of the physical link connecting each port. To define the ports for the physical element types: 1 2 3 4 Click the Add port button. A new port is added. To name the port, double-click the Name column for the port, and type in the required name. To set the maximum available bandwidth for the port, double-click the Capacity column for the port, and select the preferred bandwidth. To set the media type for the physical link connecting each port, double-click the Media column for the port, and select the preferred media type. Important : You cannot edit the media type of a port that is in use. 5 6 To specify the number of wires per port, double-click the Wires per port column for the port, and type in the required number. Add more ports in this way, as required. Tip : To add an identical port, select the original port and click the Duplicate port button. 7 8
Page 118
Ensure that your ports are in the correct order. Move them up and down the order, using the Move down port and Move up port buttons. Click Apply.
If you are defining ports for interface cards, the next step in the suggested process is to create racks to place the cards on.
Configuring Slots for Subrack Types

When you are creating a subrack type, you can configure a number of slots on it, which can contain equipment cards. To do this: 1 2 3 Click the Slots tab. Click Add new slot. A new slot appears. In the list of available cards, select the cards you want to insert into the slot. Tip : To view a summary of a particular card, right-click it and from the menu that appears, click Summary, or to browse to it in the Equipment Editor, click Go To. To quickly remove a card from a slot, in the Selected Cards pane, select the card and click Remove Card. 4 5 6 Continue adding slots and cards as required. When you have added all of the required slots, place them in the correct order by using the Move up and down buttons. Click Apply.
Configuring Subracks for Multi-subrack Types

When you are creating a multi-subrack type, you can add a number of subracks to it. To do this: 1 2 Click the Sub-equipment tab. In the list of available subracks, select the subracks you want to insert into the multi-subrack type. The chosen subrack appears in the Selected Subracks pane. Tip : To quickly remove a subrack from the multi-subrack, in the Selected Subracks pane, select the subrack and click Remove. 3 By default, there is no limit on the number of subracks of the chosen type allowed on the multi-subrack. However, if you want to limit the number, double-click the number column and type the maximum allowable number of subracks. Click Apply.
Page 119
Configuring Passive Equipment Parameters

When you are creating a piece of passive equipment, you can configure a number of parameters:
Item Connections type Number of wires/fibres per port Number of ports Description The type of cross connections that the Passive Equipment will hold, either coaxial or optical fibre. The number of coaxial wires or optical fibres carried by each port. The number of ports contained in the Passive Equipment. Note : For a Distribution Frame, you must specify the number of eastbound and westbound ports.
When you have set your parameters, click Apply.
Creating Cabinet Templates

In the Equipment Editor, you can create cabinet templates. With these, you can quickly create new cabinets that contain specific types of subracks or EUs. To create a cabinet template: 1 2 3 4 Right-click the cabinet that you want to model and from the menu that appears, click Add template. Type the name of your template in the appropriate box. In the Number of racks box, type the maximum number of racks allowed in the cabinet. You can add equipment to your cabinet in the following ways: Add a type, subrack, multisubrack or template to the cabinet template by selecting it from the list of Available Types, Racks and templates, and then clicking the Add to Cabinet button. Add a shelf to the cabinet template by clicking the Add Shelf button. Edit the shelf in the following ways:
Do this Double-click the current name, and type the new one. Select the shelf, and click the Change Rack button. Double-click the current size, and type the new one.
To change its Name Position on the rack Size
Add an equipment unit or template to the shelf by selecting it from the list of Available Units and templates, and then clicking the Add to Shelf button. Add a subrack to the multisubrack by selecting it and clicking the Add Subrack button. Note : You cannot exceed the total number of racks allowed in the cabinet, and additionally at least one instance of each subrack within the multisubrack must be included.
Tip : You can alter the position of a subrack or shelf or EU by selecting it, and clicking the Move Up or Move Down button as appropriate.
When you are satisfied with the cabinet contents and configuration, click Apply.
Creating SubRack Templates

In the Equipment Editor, you can create subrack templates. With these, you can quickly create new subracks without having to repeatedly allocate slots. To create a subrack template: 1 2 3 Right-click the subrack that you want to model and from the menu that appears, click Add template. Type the name of your template in the appropriate box. To allocate a card to one of the slots, double-click the Card or Port column for the slot, and select the required card. Note : The number of slots on the template will be the same as the number of slots on the original subrack. 4 5 Optionally, click on the + sign for a slot to display all of its ports, double-click the port name and then enter the new port name. Click the Crossconnection Setup tab, and define the crossconnections by: 6 In the Ports Incoming pane, select the incoming port for the crossconnection In the Ports Outgoing pane, select the outgoing port for the crossconnection Click the Add Crossconnection button to create the crossconnection.
The new crossconnection appears in the lower pane. Click Apply.
Creating MultiSubRack Templates

In the Equipment Editor, you can create multisubrack templates. With these, you can quickly create new multisubracks without having to repeatedly define the subracks within them. To create a multisubrack template: 1 2 3 4 5 Right-click the multisubrack that you want to model, and from the menu that appears, click Add template. Type the name of your template in the appropriate box. To add a subrack to the template, click Add subrack. A new subrack appears in the list. If you want to change the subrack type, double-click it, and select the required subrack type. Click the Crossconnection Setup tab, and define the crossconnections as follows: In the Ports Incoming pane, select the incoming port for the crossconnection In the Ports Outgoing pane, select the outgoing port for the crossconnection Click the Add Crossconnection button to create the crossconnection.
The new crossconnection appears in the lower pane.

Click Apply.
Making Global Changes to Equipment

Changing information for a large number of equipment nodes can be a very lengthy process when performed manually. To avoid this, you can use the Global Equipment Editor to change a number of equipment nodes simultaneously. To do this: 1 2 3 Ensure you are in the Transmission module view. Right-click anywhere in the module view window, and from the menu that appears, point to Select Nodes and click By Equipment Type. In the dialog box that appears, select the equipment type that you want to edit and click OK. All instances of that equipment type are selected and highlighted in the module view window. Tip : To select equipment manually, in the module view window, hold down Ctrl and click each equipment node individually. 4 From the Edit menu, click Global Equipment Editor. - or Right-click one of the selected nodes, and from the menu that appears, click Global Equipment Editor. 5 6 7 In the dialog box that appears, select the equipment type/template that you want to use for the nodes, and then click Next. If the type/template has subracks with slots, select the required cards for the slots. Click Next.
Page 122
A summary appears of the changes that you want to make.
In this example, all of the BTSs which are currently of the BTS 16K type will be changed to the BTS 32K type. If the Equipment ID is selected and the Functionality Check column for a particular node is marked with a Yes, the change is valid. If the Equipment ID is not selected and the Functionality Check column for a particular node is marked with a No, the change is not valid. To view the changes that need to be made to make the change valid, expand the plus sign beneath the node:
Ensure that the required equipment nodes are selected, and click Apply. Warning : If any of the selected nodes require functionality changes (for example edge deletions), these are automatically performed.
Page 123
Using the Equipment Browser

To open the Equipment Browser, click the Equipment tab pane. in the left-hand
Equipment Browser
Viewing Equipment in the Equipment Browser

You can use the DIRECT Equipment Browser to view all folders of available equipment, and select which particular equipment you want to use in your network. You can display the attributes of a particular equipment type by clicking it. The attributes appear in the right hand pane. You cannot edit these attributes in the Equipment Browser, as all editing is done in the Equipment Editor. For information on using the Equipment Editor, see About DIRECT Equipment on page 107. You can also use the Equipment Browser to add equipment to your network view.
Adding Equipment to a Network Using the Equipment Browser

You can use the DIRECT Equipment Browser to add equipment directly to your network plan. To do this: 1 In the Equipment Browser, select the required equipment. Note : Only the equipment that is compatible with the network view that you are using will be available. For example, you cannot see PDH equipment when you are trying to add equipment to the SDH module view window. 2
Page 124
From the DIRECT global toolbar, click the Add Node button
3 1 2 3
Click the required location to place the equipment. Click on the required equipment type in the Equipment Browser, and hold down the left mouse button. Move the cursor to the required location for the equipment. Release the mouse button to place the equipment in position.
- or -
Locating Equipment
You can use the search function of the Equipment Browser or Editor to find a particular piece of equipment quickly. To do this: 1 2 3 Click Search. In the dialog box that appears, in the Type box, select the type of element you want to search for. Enter the name of the element(s) as appropriate. You can search based on exact string (for example, BTS_3), substring (for example, BTS_) or regular expression. For information on searching by regular expression, see Examples of Using Regular Expre on page 79ssions in DIRECT. Tip : You can also search for exact names by selecting the Match Case checkbox. A list of the equipment matching your search is displayed, along with their location:
To go to the equipment in the Equipment Browser or Editor, select the equipment in the search list, right-click and from the menu that appears, click Select.
Page 125
Page 126
CHAPTER 5
Creating the Transmission Network

In the Transmission module of DIRECT, you can plan: Overall connectivity (physical Property-to-Property and logical connectivity) Detail port connectivity Detailed link connectivity You do this in the three separate module views, the Property view, the Equipment view, and the Detail view.
In This Section
Overview of the Transmission Module 128 Using the Equipment View of the Transmission Module133 Using the Property View of the Transmission Module 143 Using the Detail View of the Transmission Module 149 Creating the Optical Network 151
Page 127
Overview of the Transmission Module

The Transmission module focuses entirely on the physical side of the transmission network, and combines the Conduit, Transmission and Detail connectivity functionality. The module is split into three views: In the Property view, you can: View Property information, such as the coordinates and address, the detailed equipment configuration (including cabinet layout, node information and so on), the total cost, and the physical site-to-site connectivity (including the media free and used between Properties). This picture shows an equipment summary in the Property view:
Page 128
In the Equipment view, you can: Display the individual node-to-node connectivity and provides circuit information on each media type, enabling you to track down all traffic requirements in detail. This picture shows an example:
Page 129
Configure the equipment according to your requirements. This picture shows an example:
Page 130
Display the connection and port usage for each equipment in the view, based on the number of edges ports that have been defined for that equipment in the Equipment Editor. This picture shows an example:
Colour code the different media or connection types according to any colour convention that you require:
Page 131
In the Detail view, you can: Display the port-to-port connectivity, and view detailed link information on a link-by-link basis Produce detailed schematic diagrams for the network configuration, along with in-depth information on circuit routing. This picture shows an example:
Automatically create CAD-type schematics or arrange equipment in star or ring conventions, by using improved display layout algorithms Create a detailed layout of a Property directly from the Property view, using a site layout algorithm Create detailed views of a circuit route, from either the module view or the Network Browser
Page 132
Using the Equipment View of the Transmission Module

The Equipment view of the Transmission module: Displays the individual node to node connectivity Provides circuit information on each media type, enabling you to analyse the traffic requirements in detail Displays the equipment nodes within a Property or multiple Properties Below are the suggested steps you could follow when creating your physical network: 1 2 3 4 5 6 If required, create a new Transmission module Equipment view window. Using the Equipment Editor, add the required equipment. Edit the equipment properties. Add the network edges. Edit the network edges. Route the transmission network.
Viewing and Editing the Transmission Properties of Equipment

You can view and edit equipment transmission properties in two ways: Using the Transmission module display Using the Network browser display To do this using the Transmission module display, double-click the required equipment.
Page 133
This picture shows an example Equipment properties dialog box.
Transmission Equipment properties dialog box
Configuring Transmission Equipment

In the Equipment view of the Transmission module, on the Equipment Configuration tab of the Equipment properties dialog box, you can view a summary of the equipment's internal structure, and edit the equipment type, card type, port name and serial number. To do this: 1 2 3 4 5 Select the required equipment type from the equipment Type list. In the Card or Port column, click the type of card and select the required type from the list. Optionally, click on the + sign of the slot to display all of its ports, double-click a port name and enter the new name. Optionally, double-click the serial number box, and type the new serial number. Click Apply.
Page 134
Adding Crossconnections in Transmission Equipment

In the Equipment view or Detail view of the Transmission module, on the Crossconnection Setup tab of the Equipment properties dialog box, you can add and delete internal node crossconnections. To do this: 1 2 Click Add. In the Ports Incoming pane, select the first port of the crossconnection. Note : Any ports that already have crossconnections defined and do not have any free frames will be greyed out. Tip : To define more than one crossconnection, select multiple ports in both directions. 3 4 5 In the Ports Outgoing pane, select the second port of the crossconnection. Click Crossconnect .
In the dialog box that appears, select the correct granularity from the list. Note : If only one crossconnection is possible for the pair of ports, and the granularity is the same as the capacity of the ports, this dialog box will not appear. The In and Out panes display the break down of the frame's constituent parts, based on the granularity. Note : Any ports that already have crossconnections defined and do not have any free frames will be greyed out.
In the In pane, click the timeslot in which you want to place the traffic. Tip : To define more than one crossconnection, select multiple timeslots in both directions.
7 8
In the Out pane, click the timeslot in which you want to place the traffic. Click OK. The new crossconnection appears in the Defined Crossconnections list. For each crossconnection, the list displays the subracks, cards, port and timeslot position.
Editing the Costs of Transmission Equipment

In the Equipment view of the Transmission module, on the Costs tab of the Equipment properties dialog box, you can add any additional costs that you think may be relevant to the equipment. This includes costs such as the initial setup costs and the estimated annual maintenance costs. Note : The actual cost of the equipment type (defined in the Equipment Editor) will already be included in the total cost. DIRECT will then automatically calculate the final total cost of the equipment.
Page 135
Adding Hyperlinks to Transmission Equipment

In the Equipment view of the Transmission module, on the Hyperlinks tab of the Equipment properties dialog box, you can add a hyperlink to a piece of equipment. This is useful, for example, if you want to link an important document (for example, a manufacturer's specification or a user reference guide) to a particular piece of equipment.
Hyperlinks on equipment
To do this: 1 2 On the Hyperlinks tab, click Add. In the dialog box that appears, enter the details of the hyperlink:
Item Type Address Comments Description The type of item it is linking to - you can select from a file, an email or a web page or one of a number of formats. The path to the linked item - either type this yourself, or click Browse to locate the item. Any additional comments you may want to include. Tip : You may want to use this for a descriptive name.
Click OK. The new hyperlink appears in the list.
To open a hyperlink that you have created: On the Hyperlinks tab either select it and click Open, or double-click it.
Page 136
Viewing Connection/Port Usage for Equipment

In the Equipment view of the Transmission module, on the Connection Usage tab of the Equipment properties dialog box, you can view connection and port usage statistics for the different types of connection you may have in your network. You can view the following information:
Item Connection Type Connection Usage Description The type of connection - SDH, PDH or IP, logical or physical - and the name of the connection. Available The total number of connections of that type that have been set on the equipment, either added to the equipment itself or via cards on a subrack. Note : If on the Equipment Editor you have set the number of connections as Any, this is displayed in the Available column. Used (%) For logical connections, if a circuit is created on this equipment, one connection of that type is designated as Used, therefore Used (%) is: Number of circuits / Available * 100 For physical connections, if a circuit is terminated on this equipment, one port of that type is designated as Used, therefore Used (%) is: Number of connected ports / Available * 100 Unused (%) The difference between used and available, or: Available - Used / Available * 100 Note : If on the Equipment Editor you have set the number of connections as Any, N/A is displayed in the Unused (%) column. Ports Usage Available The total number of ports that have been set on the equipment, either added to the equipment itself or via cards on a subrack. Used (%) If a circuit is terminated on this equipment, one port of that type is designated as Used, therefore Used (%) is: Number of connected ports / Available * 100 Unused (%) The difference between used and available, or: Available - Used / Available * 100 Surplus (+)/Deficit (-) (Used ports - Used Connections) + Unused ports If this is a positive value, there is a surplus number of ports. However, if it is a negative value, there is a deficit in the number of ports required.
You can also view this information in a report. For more information, see Creating Reports in DIRECT on page 94.
Page 137
Editing Edges in the Transmission Module

In the Transmission module, as you connect your transmission equipment with edges, the edges will have the default attributes of its connection type. You can edit edges in three different ways: Add or edit a connection type template Edit the attributes of a selected edge group Edit the attributes of a selected edge Note : If you change the default attributes of a connection type, the new values will only apply to any edges added subsequently. Therefore, it is recommended that you ensure that the connection types are configured properly before you start to add edges.
Adding and Editing Connection Type Templates in the Transmission Module

In the Transmission module of DIRECT, the attributes of the connection types are given a set of default values. You can add new connection type templates to match your requirements, and/or edit existing ones. To add a connection type template: 1 2 3 From the Transmission menu, click Connection Types. In the dialog box, click with the right mouse button on the type of connection you wish to add, for example, Leased Line. From the menu that appears, click Add New Type.
A new connection type is added, and appears in the list. The attributes of the new connection type will have the same values as the default, so if you wish to set your own values, you must edit them on the appropriate tabs. To edit these values: 1 2 3 From the Transmission menu, click Connection Types. In the dialog box that appears, in the left pane select the connection type that you wish to edit. In the right pane, edit the attributes as required. Tip : You can make a connection type the default by selecting it, clicking the right mouse button and then clicking Set As Default.
Page 138
Editing Optical Fibre Connections This table shows the attributes of an optical fibre connection that you can edit in the Connection Types dialog box:
Tab General Item Name (ID) Manufacturer Comments Fibre Number of Fibres Cost Per Metre Attenuator Loss Per Metre Delay (msec/Km) Link Budget Single Fibre/(D)WDM Maximum Number of Wavelengths per Fibre Description The name of the optical fibre, used for identification purposes. The name of the manufacturer of the optical fibre. Any additional planning comments you may wish to include. The number of fibres contained in the single optical fibre. The cost of the optical fibre per metre. The attenuation loss per metre for each fibre used in the connection edge. The traffic delay caused by the optical fibre. The link budget value to be placed on the connection. Type of wavelength optical fibre, either single or multiple (DWDM is Dense Wavelength Division Multiplexing). The maximum number of wavelengths allowed per optical fibre (used for DWDM optical fibres only).
Editing Coaxial Connections This table shows the attributes of a coaxial connection that you can edit in the Connection Types dialog box:
Tab General Item Name (ID) Manufacturer Comments Coaxial Loss Per Metre Cost Per Metre Delay (msec/Km) Description The name of the coaxial connection, used for identification purposes. The name of the manufacturer of the coaxial cable. Any additional planning comments you may wish to include. The loss per metre of the coaxial connection. The cost of the coaxial connection per metre. The traffic delay caused by the coaxial connection.
Editing Twisted Pair Connections This table shows the attributes of a twisted pair connection that you can edit in the Connection Types dialog box:
Tab General Item Name (ID) Manufacturer Comments Twisted Pair Number of Pairs Loss Per Metre Cost Per Metre Description The name of the twisted pair, used for identification purposes. The name of the manufacturer of the twisted pair connection. Any additional planning comments you may wish to include. The total number of twisted pairs used for each twisted pair connection. The loss per metre of the twisted pair connection. The cost of the twisted pair per metre.
Page 139
Tab
Item Delay (msec/Km)
Description The traffic delay caused by the twisted pair connection.
Editing Radio Connections This table shows the attributes of a radio connection that you can edit in the Connection Types dialog box:
Tab General Item Name (ID) Manufacturer Comments Radio Delay (msec/Km) Description The name of the radio connection, used for identification purposes. The name of the manufacturer of the radio connection. Any additional planning comments you may wish to include. The traffic delay caused by the radio connection.
Editing Leased Line Connections This table shows the attributes of a leased line connection that you can edit in the Connection Types dialog box:
Tab General Item Name (ID) Manufacturer Comments Leased Line Leasing Company Contact Details Description The name of the leased line connection, used for identification purposes. The name of the manufacturer of the leased line. Any additional planning comments you may wish to include. The name of the company leasing the line. The address and contact details of the line-leasing company.
Editing Satellite Connections This table shows the attributes of a satellite connection that you can edit in the Connection Types dialog box:
Tab General Item Name (ID) Manufacturer Comments Description The name of the satellite connection, used for identification purposes. The name of the manufacturer of the satellite connection. Any additional planning comments you may wish to include.
Editing Selected Segment Groups in the Transmission Module

You can edit the properties of a segment group by manually altering the details in the Segment Group dialog box. To do this: 1 2 Double-link one of the segments in the segment group. The Segment Group dialog box opens. You can edit the attributes of the segment group on these tabs:
Page 140
General Details
Routing Properties Hyperlinks
Editing the Physical Details of the Segment Group On the Details tab of the Segment Group dialog box, you can edit the physical details of a connection group. The following table describes the details that you can edit:
Item Quantity Description You can edit the capacity of the connection group. Each media type has a different connection media capacity - Optical Fibre = 10 per connection, Coaxial = 1 per connection, Twisted Pair = 20 per connection, Radio = 1 per connection, Leased Line = 1 per connection. So if, for example, if you type a quantity of 3 for an optical fibre connection group, you will have an overall media capacity of 30. Type Length You can edit the media type that is used for this connection group. by selecting from the Type box. The length of the connection group in kilometres.
You can also view the connections (or circuits) contained in the connection group, as well as the number of total, used and free media.
Editing Selected Segments in the Transmission Module

You can edit the properties of any segment(s) by manually altering the details in the Segment Group dialog box. To do this: 1 2 3 In the Transmission module view, double-click the group containing the segment. In the dialog box that appears, in the left-hand tree pane, click the segment that you want to edit. You can view and edit the attributes of the segment on these tabs: General Traffic - Defines the traffic routed onto this segment Capacity Costs Routing Properties Hyperlinks
Editing the Costs of Transmission Segments In the Equipment view of the Transmission module, on the Costs tab for a particular transmission segment, you can add any additional costs that you think may be relevant to the equipment. This could include installation costs for example. Note : The cost of the connection type (defined in the Connection Types dialog box) will already be included in the total cost. DIRECT then automatically calculates the final total cost of the segment.
Page 141
Adding Hyperlinks to Segment Groups and Segments

In the Equipment view of the Transmission module, on the Hyperlinks tab of a segment group or segment dialog box, you can add a hyperlink. This is useful, for example, if you want to link an important document (for example a link fault report) to a particular edge. To do this: 1 2 On the Hyperlinks tab, click Add. In the dialog box that appears, type the details of the hyperlink:
Page 142
Using the Property View of the Transmission Module

The Property view of the Transmission module represents the physical locations of equipment nodes on a map. The Property view stores Property information, such as co-ordinates, address, cost, detailed equipment configuration and physical Property to Property connectivity. This picture shows an example Property view window.
Example Property view window
Below are the suggested steps you could follow when creating your physical network: 1 2 Create a new Property window. Add or import Properties. Important : If you want to create your Property view after your Equipment view, you can set the Preferences so that Properties are added automatically as you create your Equipment view. 3 4 5 Add conduit pits. Add or import conduits. Edit the Properties.
Page 143
6 7 8
Edit the conduit pits. Edit the conduits. Route the transmission layer to conduit layer.
Adding Properties
A Property in DIRECT corresponds to the same network element in ENTERPRISE. A Property is a location containing any number of network elements. You can add Properties both automatically and manually. To add a Property automatically: 1 2 3 From the Project menu, click Preferences. In the Preferences dialog box that appears, in the When Adding Equipment pane, select the Create a New Property and a New Cabinet option. Click OK. From now onwards, a new Property is added to the Property view every time you add a piece of equipment in the Equipment view. To add a Property manually: 1 2 From the Property view window toolbar, click the Add Property button Click the required location for the new Property on the Property view. A new, empty Property is created. You can now edit the attributes of Properties. .
Adding Conduit Pits

A conduit pit represents a physical hole in the ground, and can be used as a junction point for a number of conduits linking a number of Properties:
Conduits meeting at a pit
Page 144
To add a conduit pit: 1 2 From the Property view window toolbar, click the Add Pit button Click the required location for the conduit pit on the Property view. A new pit is created. You can now edit the attributes of conduit pits. .
About Conduits
A conduit in DIRECT corresponds to a link in ENTERPRISE. A conduit typically consists of an inner conduit, cable, fibres, free space for an additional inner conduit, free space for an additional inner cable and free fibres. They are the actual physical links between Properties, and the type of conduit is determined by the connection type of the edge:
Connection type of edge Radio Optical Fibre Twisted Pair Coaxial Leased Line Satellite Type of conduit Radio Ground Ground Ground Leased Line Radio
You can add conduits both automatically and manually.
Adding Conduits
Adding conduits automatically You can also connect Properties together with conduits using one of the automatically generated network topologies. To do this: 1 2 Select the Properties that you want to connect with conduits. From the Conduit menu, point to Connect Selected Sites and click the required topology.
Function Adds edges, creating a minimum spanning tree type topology among the selected equipment. Adds edges, creating a star type topology among the selected equipment. Adds edges, creating a ring type topology among the selected equipment.
This table explains how the topologies are created:

Model name Tree Topology Star Topology Ring Topology
Page 145
Adding conduits manually To add a conduit manually: 1 2 3 4 In the Property view, click one of the toolbar buttons to select the type of conduit that you want to add - Radio, Duct or Leased Line. Click the Property that you want to start the conduit link from. Move the cursor to the Property to which you want to link. Click the Property to anchor the link.
Editing Properties
In the Property view of the Transmission module in DIRECT, you can edit the attributes of a Property. To do this: 1 2 Double-click the required Property. You can view and edit the properties of the Property on a number of tabs. The following table describes these tabs:
On this tab General You can Edit the Property ID, Code, the Location (in LL, DLL or Grid format), planning Comments. View the date and time that the Property was created, and if applicable, last edited. Address Equipment Summary Costs Specify a postal address for the Property. View the cabinets and equipment stored on this Property. Edit the Property Costs - the initial cost and the annual cost. View the Total cost, including the equipment and internal connection cost. Hyperlinks Create hyperlinks to Property-related documents and so on. For more information, see Adding Hyperlinks to Properties, Cabinets and Equipment on page 147.
Click Apply.
You can also edit the equipment and cabinets on a Property.
Editing Cabinets on a Property

In the Property view of the Transmission module, you can edit the cabinets contained on a Property. To do this: 1 2 3 4 5 Double-click the Property containing the cabinet. In the dialog box that appears, double-click the cabinet in the left-hand pane. On the General tab, edit the cabinet name and any planning comments. Click the Cabinet Summary tab, and change the cabinet type if you require. To change the rack on which a card is positioned, select the card, and click the Change Rack button.
Page 146
6 7 8 9
To move the position of a card on a rack, select the card, and then click the Move Up or Move Down buttons as appropriate. Click the Costs tab, and edit the initial and/or annual costs of the cabinet. Click the Hyperlinks tab, and add any required links. For more information on this, see Adding Hyperlinks to Properties, Cabinets and Equipment on page 147. Click Apply.
Editing Equipment on a Property

In the Property view of the Transmission module, you can edit the equipment contained on a Property. To do this: 1 2 3 4 5 6 7 8 9 Double-click the Property containing the equipment. In the dialog box that appears, double-click the equipment in the left-hand pane. On the General tab, edit the equipment ID, names and any planning comments. Click the Equipment Configuration tab, and change the equipment type if you require. To change the card on a particular slot of the equipment, double click the card, and select the new one. To change the serial number of a card, double click the appropriate row and type the new serial number. Click the Costs tab, and edit any initial and/or annual additional costs. Click the Hyperlinks tab, and add any required links. For more information on this, see Adding Hyperlinks to Properties, Cabinets and Equipment on page 147. Click Apply.
Adding Hyperlinks to Properties, Cabinets and Equipment

In the Property view of the Transmission module, on the Hyperlinks tab of a Property, cabinet or equipment dialog box, you can add a hyperlink. This is useful, for example, if you want to link an important document (for example, a site photo or a staff report) to a particular network element.
Hyperlinks on a Property
Page 147
To do this: 1 2 On the Hyperlinks tab, click Add. In the dialog box that appears, type the details of the hyperlink:
Editing Conduit Pits

In the Property view of the Transmission module in DIRECT, you can view and edit the properties of a conduit pit. To do this: 1 2 Double-click the required conduit pit. You can view and edit the properties of the conduit pit on two tabs:
On this tab General You can Edit the pit ID, the Location (in LL, DLL or Grid format), planning comments. View the date and time that the pit was created, and if applicable, last edited. Address Specify a postal address for the conduit pit.
Click Apply.
Editing Conduits
In the Property view of the Transmission module in DIRECT, you can view and edit the properties of a conduit. To do this: 1 2 Double-click the required conduit. You can view and edit the properties of the conduit on three tabs. The following table describes these tabs:
On this tab General You can Edit the name of the conduit, and add any planning comments. View the date and the time that the conduit was created, and if applicable, last edited. Details Edit the length, by selecting the override option, and entering your own value. View the conduit type, the connection group, and the associated parameters. Costs Enter the initial and annual Property costs. View the Total cost, including the equipment and internal connection costs.
Page 148
Click Apply.
Using the Detail View of the Transmission Module

The Detail view provides a detailed perspective of the equipment that is used in your plan. You can select a link and expand it in the equipment view, and enlarge it to enable you to specify the port connectivity. The Detail view displays port to port connectivity, and provides detailed link information on a link by link basis. You can also view detailed schematic diagrams for the network configuration, and detailed information on circuit routing.
Creating Detail Views Based on Properties

You can create detail views based on existing Properties, either in the Property module or in the Region View of the Network Browser. The detail view displays the connections (both internal and external) of all the equipment located Properties. To create a detailed view: In the module window, right-click on the required Property, and from the menu that appears, click Create Detail View. - or In the Network Browser, in Region View, right-click on the required Property, and from the menu that appears, click Create Detail View. A detail view is created in the Views Browser, within the Transmission module. By default, the detail view will display all cabinets with equipment, the Property ID, cabinet ID and equipment ID. For more information on how to edit these display settings, see About Displaying Data in Module Views on page 84.
About Equipment in the Detail View of the Transmission Module

For each supported equipment in the Equipment view, you can display a block diagram of it in the Detail view. The diagram models the equipment's physical appearance, and if you edit such details as the node capacity or equipment type display colour, the block diagram will also change in appearance. By default, the Detail view displays only ports and slots that are unutilised, to enable you to quickly see what is free, but you can change this to display what you require.
Page 149
To do this: 1 2 In the Detail view, select the required node. Click with the right mouse button, and from the menu that appears, point to Show Ports and then click the required option:
To do this Display both used and unused ports Display used ports only, in order to quickly see how the ports are currently used Hide both used and unused ports Choose this option Show All Show Utilised Hide All
This picture shows an example where only the unused ports for a node are displayed and then all ports are displayed instead.
Connecting Detail Equipment Nodes

In the Detail view of the Transmission module, you can connect the equipment ports together, based on the edges that you have created in the Equipment view. Important : Only physical ports of the same transmission technology type should be connected together. For example, an SDH port and a PDH port cannot be connected together. To connect detail equipment ports: 1 2 3 Click the Add Edge button Click the terminating port. Important : The media type of the outgoing edge for each port should be the same as the media type of the connection group. You can set the media type of the outgoing edge for a port in the Equipment Editor. .
In the Detail view, click the originating port.
Page 150
Viewing and Editing Detail Equipment Nodes

In the Detail view of the Transmission module, you can view and edit the properties of equipment nodes on these tabs: General tab Crossconnection Setup tab Cross Connections tab
Creating the Optical Network

If you are new to DIRECT, it is recommended that you follow the work order set out below when planning your first few optical networks: 1 2 3 4 5 6 In the Equipment Editor, ensure that you have created equipment with optical cards. In the Transmission module, add the required equipment. Connect the equipment using the required optical link type. Open the ATG, and add the required number of optical link edges to each edge group. In the Transmission module, edit the properties of the optical link edges. Create any protection loops that you need.
Page 151
Page 152
CHAPTER 6
Creating the Traffic Network

You can use the Traffic module to generate and distribute all of the traffic for your network. You can create the traffic for a number of technologies, all related to transmission network planning: Generic Cellular GSM (2g), GPRS/HSCSD(2.5g) and UMTS (3g) PSTN IP Signalling SS7 Interswitch TETRA This module also stores the logical connections and requirements in order that the service layer can distribute traffic.
In This Section
Overview of the Traffic Module Cellular Layer 154 Setting Default Parameters for Traffic 156 Adding Traffic Services and Types 172 Adding Traffic to DIRECT Equipment 177 Viewing and Editing the Traffic Properties of Equipment181 Overview of the Traffic Module Signalling Layer 198 Overview of the Traffic Module Interswitch Layer 215 Creating a 3GPP Network 224 Creating the TETRA Traffic Network 225 Using Protocol Stacks 226 Planning a GPRS Network Using DIRECT 237 Planning a Prepay Network Using DIRECT 238
Page 153
Overview of the Traffic Module Cellular Layer

In the cellular layer of the Traffic module, for all technologies you can: Import the RF planned network from ASSET3G View parenting information between network elements, which was defined during the RF planning in ASSET3G Add or edit parenting information between network elements, either automatically or manually Add additional network elements In addition, for 2g and 2.5g networks you can: Set the TRX count for each cell on a node. Route traffic based on TRX, Erl or number of subscribers. Add the forecasted TRX count. Set 2g and 2.5g network parameters (for blocking, and so on). Define GPRS and EGPRS traffic. Calculate the EDAP pool size for EGPRS traffic. View a network summary per BSC detailing the number of TRXs, BTSs and traffic channels.
Page 154
This picture shows an example:
In addition, for 3g networks you can: Set the traffic service type and number of subscribers. Route traffic based on service and number of subscribers. Set 3g network parameters per service type (for example, blocking, bit rate and so on). Provide SHO between node B elements.
Page 155
This picture shows cells in node B:
Setting Default Parameters for Traffic

You can set different default parameters for different types of traffic: Cellular traffic PSTN traffic TETRA traffic Interswitch traffic Signalling traffic You can also set default parameters for the different traffic edge interfaces.
Page 156
Setting Cellular Traffic Parameters

DIRECT creates the Cellular network traffic according to certain defined parameters. These have default values, but during planning, you may need to set your own values in the Cellular Parameters dialog box. To open this dialog box: In the Traffic module, from the Traffic menu, point to Cellular and click Default Parameters. The parameters are divided onto these tabs: 2G parameters Bts parameters 3g parameters
Defining the 2G Parameters

On the 2G Parameters tab of the Cellular Parameters dialog box, you can edit the following parameters:
Name Default Air-interface Blocking Probability (%) Default Ater-interface Blocking Probability (%) 2G Voice Traffic Per Subscriber (mErl) EDGE GPRS Channel Utilisation (%) Description The probability value for the blocking of any incoming switched radio circuits signals. The probability value for the blocking of any incoming switched Ater circuits signals. The average 2G voice traffic per subscriber in mErl. The extent to which the GPRS channel(s) is(are) utilised.
On this tab, you can also select if the logical connections and interswitch traffic are calculated from the actual or forecasted traffic.
Defining the Bts Parameters

On the Bts Parameters tab of the Cellular Parameters dialog box, you can edit the following parameters:
Name Title Trx Signalling Bts Signalling Trx User Bitrate 1stTrx User Channels 1stTrx Air Interface Channels Other Trx User Channels Other Trx Air Interface Description The different name for each of the signalling rate types associated with the default network BTSs. The default Trx signalling bitrate. The default Bts signalling bitrate. The default Trx user bitrate. Number of user channels for the 1st Trx in a cell. Number of air interface channels for the 1st Trx in a cell. Number of user channels available for the other Trxs in a cell. Number of air interface channels available for the other Trxs in a cell.
Tip : To revert back to the default values for all of the signalling rate types, click the Restore Default Values button.
Defining the 3g Parameters

On the 3g Parameters tab of the Cellular Parameters dialog box, you can edit the following parameters:
Name 3g Voice Traffic per Subscriber (mErl) Description The average 3g voice traffic per subscriber in mErl.
3g RT data Traffic per Subscriber (mErl) The 3g real-time traffic per subscriber in mErl. Default Iub Interface Blocking Probability % 3g Overbooking for NRT Traffic 3g Iub NBAP-C Traffic (% of total user plane traffic) 3g Iub NBAP-D Traffic (% of total user plane traffic) 3g Iur RNSAP Signalling Traffic (% of total user plane traffic) 3g Iu-CS RANAP Signalling Traffic (% of total user plane traffic) 3g Iu-CP RANAP Signalling Traffic (% of total user plane traffic) Default % of blocking probability on the Iub interface. 3g overbooking ratio for non real-time traffic. Percentage of total user plane traffic that is used for 3g Iub NBAP-C traffic. Percentage of total user plane traffic that is used for 3g Iub NBAP-D traffic. Percentage of total user plane traffic that is used for 3g Iur RNSAP signalling traffic. Percentage of total user plane traffic that is used for 3g Iu-CS RANAP signalling traffic. Percentage of total user plane traffic that is used for 3g Iu-CP RANAP signalling traffic.
On this tab, you can also set the conditions for using simulated traffic in Node Bs. You can select to calculate the dedicated number of AAL2s based on either: The maximum number of subscribers The average number of subscribers, plus the standard deviation
Page 158
Setting PSTN Traffic Parameters

DIRECT creates the PSTN network traffic according to certain defined parameters. These have default values, but during planning, you may need to set your own values in the PSTN Parameters dialog box.
PSTN Default Parameters dialog box
To open this dialog box: In the Traffic module, from the Traffic menu, point to PSTN and click Default Parameters. The PSTN Parameters dialog box appears. You can define subscriber traffic, blocking requirement and the type of logical connections that the access network generates. You can edit the following parameters:
Parameter name Subscriber Traffic Description The default traffic values (in number of lines) for the 3 different subscriber types (Home, Business, PABX) and for the 2 network types (POTS and ISDN). The blocking probability percentage for the incoming switched circuit signals. The default granularity of the link used (either 2M, 1.5M or 64k) and the number of traffic channels it contains.
Blocking Probability Edge Multiplexing
Page 159
Setting the TETRA Traffic Parameters

DIRECT creates the TETRA network traffic according to certain defined parameters. These have default values, but during planning, you may need to set your own values in the TETRA Parameters dialog box. To open this dialog box: In the Traffic module, from the Traffic menu, point to TETRA and click Default Parameters. The parameters are divided onto these tabs: Traffic Parameters Network Parameters Dispatcher Parameters
Defining the TETRA Traffic Parameters

On the TETRA Traffic Parameters tab of the TETRA Parameters dialog box, you can edit the following parameters:
Parameter Erlang B or Erlang C Default Air-interface Queuing Prob. (%) Default Air-interface Blocking Prob. (%) Traffic per Subscriber (mErl) Description The formula used - either based on Blocking (B) or Queuing (C). The percentage probability value for the queuing of any incoming switched radio circuits signals. The percentage probability value for the blocking of any incoming switched radio circuits signals. The average amount of traffic per subscriber.
Defining the TETRA Network Parameters

On the TETRA Network Parameters tab of the TETRA Parameters dialog box, you can edit the following parameters:
Parameter TRX Signalling TBS Signalling TRX User Bitrate 1st TRX User Channels 1st TRX Air Interface Other TRX User Channels Other TRX Air Interface Description The data rate for signalling data per TRX. The data rate for signalling data per TBS. The data rate for user traffic data per TRX. The default number of user traffic channels for the first TRX in a cell. The default number of air interface traffic channels for the first TRX in a cell. The default number of user traffic channels for the other TRXs in a cell. The default number of air interface traffic channels for the other TRXs in a cell.
Page 160
Defining the TETRA Dispatcher Parameters

On the TETRA Dispatcher Parameters tab of the TETRA Parameters dialog box, you can edit the following parameters:
Parameter Monitored Channels 64k Timeslots Needed between DSC and DXT Description The ranges for the number of 64k Timeslots required between DSC and DXT. The number of timeslots required in the DSC-DXT connections.
Setting the Interswitch Traffic Default Parameters

DIRECT creates the Interswitch network traffic according to certain defined parameters. These have default values, but during planning, you may need to set your own values in the Interswitch Parameters dialog box.
Example Interswitch Parameters dialog box
To open this dialog box: In the Traffic module, from the Traffic menu, point to Interswitch and click Default Parameters.
Editing Interswitch Network Parameters

On the Network Parameters tab of the Interswitch Parameters dialog box you can edit the blocking factor parameter. The blocking factor is the allowed call blocking percentage (Grade of service) for trunks. This figure is set by the operator and is used to convert Erlangs to 64k channels with the Erlang B formula.
Editing Interswitch Voice or Data Traffic Parameters

On the Voice Traffic Parameters and the Data Traffic Parameters tabs of the Interswitch Parameters dialog box you can edit the main parameters used to model voice and data interswitch traffic. The following table shows the parameters:
Item Halving Distance, Calling Halving Distance, Moving Traffic/Subscriber (Fixed or Mobile Traffic) Description The halving distance for the calling interest of fixed and mobile subscribers in its own network. The halving distance for the moving interest of mobile subscribers in its own network. The amount of traffic (in miliErlangs) per fixed/mobile network subscriber. Multiplied by the number of subscribers to give the total amount of traffic in Erlangs. The average length of voice calls made by fixed/mobile network subscribers. Used to create the Busy Hour Call Attempts. Indicates which codec will be used for CS Data Traffic in the cellular and interswitch network.
Call Length (Fixed or Mobile Traffic) Data Traffic Codec
Defining Routing Strategies for Interswitch Traffic

On the Routing tab of the Interswitch Parameters dialog box, you can: Choose to route using routing tables or using the end-to-end shortest path algorithm Edit the default routing strategies used when routing the interswitch traffic Share loads in different proportions Define an RTP (real-time transport protocol) overhead for IP routing Select a link fault case that will be used by default when routing the interswitch traffic A routing strategy specifies the number of routes between a switch pair, and for each route the percentage of total traffic in one direction. The sum of percentage values can be over 100% if spare capacity is allocated for recovering from failures. Typical values are 100% for primary routes and 20% for secondary routes.
Page 162
To define the routing strategies: 1 Choose whether you want to route using routing tables or using the end-to-end shortest path algorithm. Tip : Shortest path routing would normally be used to plan unknown areas of your network. You can use it with the Update Routing Tables option to create initial routing tables, and then edit/refine them later on. After you have finalised your routing tables in this way, you can the use these to model the actual network routing. If you chose to use routing tables, go to step 6. If you chose to use the shortest path algorithm, go to step 2. 2 Choose whether to retain or update the routing tables on routing: If you choose to update the routing tables on routing, DIRECT routes the traffic based on the Shortest Path First (SPF) algorithm and constructs new routing tables for all the nodes on the new routes. Note : This option is only available if you are creating single routes, with just 1 alternative. 3 4 If you choose to retain existing routing tables, DIRECT uses any existing routing tables to route the traffic.
In the row containing the required network type, double-click the No. of Routes column, and type the number of routes that you want. As the Load Sharing is set to Normal by default, the 100% traffic will be divided equally between the routes (for example, if there are 4 routes, each will take 25% of the traffic, whereas if there were 5, each would take 20%). To edit the load sharing, select the load sharing type from the following options:
Item None Normal Description Only one route is constructed, which carries 100% of the traffic. The 100% traffic is divided equally between the routes (for example, if there are 4 routes, each will take 25% of the traffic). Note : With Normal load sharing, you cannot plan for more than 100% traffic load. User Defined Enables you to divide the percentages as you wish, by double-clicking on the percentage for each route and typing in your own value. Note : With User Defined load sharing, you can plan for traffic loads above and below 100%.
Note : When using load sharing, the SPF algorithm will not duplicate routes, but will instead redistribute the share across the available routes. For example, if you chose a strategy of 3 routes with traffic split 33%-33%-33% and only 2 routes were available, DIRECT would divide the 3rd portion between the two, creating a final split of 50%-50%. This also works for unevenly shared percentages as well; if you had specified 3 routes with a 50%-30%-20% split and only 2 routes were found, the final split would become 62.5%-37.5%. 6 If you are using the IP module, set the RTP Overhead (bits) for IP routing.
Page 163
Select which link fault case will be used by default when routing the interswitch traffic - zero fault, 1 link, 1 node or worst case. The capacity/64k equivalent values for these will be based on those defined on the Edge Traffic tab of the interswitch interface edge.
You can also specify separate routing strategies and default link fault cases for particular interswitch requirement edges. For information on this, see Defining Routing Strategies for Interswitch Edges on page 211.
Adding and Removing Known External Networks for Interswitch Traffic

As well as the existing network you have created, you can add external networks to your interswitch network plan in the Interswitch module. This enables you to model the traffic for other operators' networks in your plan. To add a network to the interswitch plan: 1 2 In the Interswitch Parameters dialog box, click the Known External Networks tab. Click with the right mouse button, and in the menu that appears, click Add Network. DIRECT adds an external network. A number is assigned to the external network. You can assign external nodes to these external networks, and also add traffic to them as well. To remove an external network, click with the right hand mouse button on the network you want to remove, and from the menu that appears, click Remove Network.
Setting Codecs Conversion Rules

A codec is a software component that translates video or audio between its uncompressed form and compressed form. A codec is used to compress digital audio files by discarding redundant data. DIRECT uses 2 types of codec: Voice Codecs - you can create these by defining a Voice (Conversational) traffic type Data Codecs - you have to define the data codec to use in the Interswitch Default Parameters Different nodes may use different codecs, and in this state they are usable. As well as this, different codecs offer different QoS, so you must be able to choose the correct one for the network conditions. Therefore, you have to define how one codec will be converted for use with another.
Page 164
In the Traffic module, on the Codecs tab of the Interswitch Parameters dialog box, you can define the conversion rules between the different codecs. The tab shows a grid which cross-references all of the codecs used on the transmitting node and all of the codecs used on the receiving node:
Setting Codecs Conversion Rules
In the grid: The left hand (vertical) column represents the codecs used on the transmitting node The right hand (horizontal) row represents the codecs used on the receiving node The boxes in the grid represent the codec that will be used In the example, if the transmitting node is using an AMR7.4 codec and the receiving node is using an AMR12.2 codec, then an AMR12.2 codec will be used to convert between the two. To edit these rules: 1 2 Double-click on the conversion rule that you want to edit. From the list that appears, selected the required codec.
Example of Using Codec Conversion Tables This section describes a typical use case for codec conversion tables. Consider the following network:
Page 165
The network traffic distribution and codec assignment is described in the following table:
Traffic Direction MSC_1 to BSC_2 MGW_1 to MSC_1 MGW_1 to RNC_3 MGW_2 to RNC_4 MGW_3 to POI_1 Traffic Amount (Erl) 500 500 500 500 1200 Codec Assignment 100% EFR 100% EFR 80% AMR0, 10% EFR, 10% AMR7.4 70% AMR0, 20% EFR, 10% AMR7.4 100% G.711
Therefore, MGW_1 has a mix of traffic between MSC_1 and RNC_3 - 55% EFR (550 Erl), 40% AMR0 (400Erl) and 5% AMR7.4 (50Erl). The following codecs conversion table is used:
AMR0 AMR0 (12.2kps) AMR7.4 (7.4kbps) G.711 (64kbps) EFR (12.2kbps) FR (13kbps) AMR0 AMR0 AMR0 AMR0 AMR0 AMR7.4 AMR0 AMR7.4 AMR0 AMR0 AMR0 G.711 AMR0 AMR7.4 G.711 EFR FR EFR EFR EFR EFR EFR EFR FR FR FR FR FR FR
The TrMod interswitch traffic calculation is performed, and the traffic mix in Erlangs is produced as follows:
MSC_1 MSC_1 MGW_1 MGW_2 POI 25 50 25 100 MGW_1 50 100 50 200 MGW_2 25 50 25 100 POI 200 400 200 0
Calculating Traffic between MSC_1 and MGW_1 From MSC_1 to MGW_1, there is 50 Erl of traffic, which has come 100% from EFR and is going to 55% EFR, 40% AMR0 and 5% AMR7.4. Based on the conversion table, this is converted to 55% EFR and 45% AMR0 (EFR to AMR7.4 becomes AMR0). Based on a blocking rate of 0.1%, 50 Erl = 71 circuits. The traffic in the core network interconnections can now be calculated as follows: (EFR% x Number of circuits required for 50 Erl x EFR bit rate) + (AMR0% x Number of circuits x AMR0 bit rate)= Total traffic in kbps (0.55 x 71 x 12.2) + (0.45 x 71 x 12.2) = 866.2 kbps Calculating Traffic between MGW_1 and MGW_2 From MGW_1 to MGW_2, there is 50 Erl of traffic, which has come 55% from EFR, 40% from AMR0 and 5% from AMR7.4 and is going to 20% EFR, 70% AMR0 and 10% AMR7.4. Based on the conversion table, this is converted to 79.5% AMR0, 0.5% AMR7.4 and 20% EFR.
Based on a blocking rate of 0.1%, 50 Erl = 71 circuits. The traffic in the core network interconnections can now be calculated as follows: (EFR% x Number of circuits required for 50 Erl x EFR bit rate) + (AMR0% x Number of circuits x AMR0 bit rate)= Total traffic in kbps (0.795 x 71 x 12.2) + (0.005 x 71 x 7.4)+(0.2 x 71 x 12.2) = 864.5 kbps
Setting the Signalling Traffic Parameters

DIRECT creates the Signalling network traffic according to certain defined parameters. These have default values, but during planning, you may need to set your own values in the Signalling Parameters dialog box.
Signalling Parameters dialog box
You can view and edit the parameters on these tabs: Global Signalling Network Parameters Global VLR Parameters SS7 Location Area Update Matrix
Routing HO % Matrix If you want to restore the default values on all of the tabs at any time, click Restore. You can also define parameters for individual signalling traffic services.
Setting the Global Signalling Network Parameters

In the Traffic module, on the Global Signalling Network Parameters tab of the Signalling Parameters dialog box, you can edit the following parameters:
Item Holding Time of Short Calls (s) Short Calls (%) Unsuccessful Calls (%) SM Success Rate (%) Authentication SMS MO Authentication SMS MT IMSI Attaches / Subs / BH default LU / Subs / BH default Description Average duration of short calls. Percentage of short calls. Percentage of unsuccessful calls. The percentage of successful signalling rate. The number of mobile originating signalling messages per subscriber in the busy hour. This value is used in the Authentication Service calculations. The number of mobile terminating signalling messages per subscriber in the busy hour. This value is used in the Authentication Service calculations. The number of International Mobile Subscriber Identity attaches (mobile logging on/off) per subscriber during the busy hour The number of Local Updates per subscriber during the busy hour.
You can also make a particular set of values the default parameters, by clicking Set As Default. If you later want to revert back to the default settings, click Restore Defaults.
Setting the Global VLR Parameters

In the Traffic module, on the Global VLR Parameters tab of the Signalling Parameters dialog box, you can edit the following parameters, which are used for authentication and IMEI checking: Note : All of the values represent the required number of occurrences before a procedure is activated.
Item LOC UP NEW VIS IMSI ATTACH MT CALL MO CALL MT SMS MO SMS TRIPLETS Description Location Update New Visitor - an Authentication usage frequency counter that measures the authentication on LU of a new visitor. The number of events belonging to an IMSI attach. Mobile terminating a call. Mobile originating a call. Mobile terminating an SMS. Mobile originating an SMS. Normally in a GSM network, the VLR stores five different authentication triplets per mobile subscriber. These triplets consist of the SRES (Signal Response), RAND (Random Number), and the KE (Encryption Key).
Page 168
Creating the SS7 Location Area Update Matrix

In the Traffic module, on the SS7 Location Area Update Matrix tab of the Signalling Parameters dialog box, you can define a Location Area Update matrix. The values represent the number of times the subscriber will be requested to update its location during the busy hour, with different values for different areas to provide more accurate signalling traffic calculations. To set the LU values: 1 2 3 Ensure you have created and configured the required number of MSCs. From the Traffic menu, point to Signalling and click Default Parameters. Click the SS7 Location Area Update Matrix tab. This matrix displays the number of location area updates that are performed between the MSC equipments.
In the example above, Equipment 2 checks the location of Equipment 3 8 times per subscriber per busy hour, whereas Equipment 3 checks the location of Equipment 2 only 5 times. To begin with, all of the values are marked with an asterisk (*) indicating they are at the default value. The default LU/Subs/BH value is set in the Global Signalling Network Parameters. 4 To change a value, double-click on the required box and enter the new value (the x axis represents the equipment doing the location area update, while the y axis represents the equipment whose location area is being updated. When you have set the correct values for all of the equipment, click Apply.
Page 169
Setting the Signalling Traffic Routing Parameters

In the Traffic module, on the Routing tab of the Signalling Parameters dialog box, you can set the routing parameters for the signalling traffic. This table describes the parameters that you can set.
Parameter Required Nr of Routes Routing Options Description The minimum number of routes required for signalling traffic. You can select either: Update any existing routing tables each time you route. If you choose this option, any manual changes you made to the routing of the traffic will be lost next time that you route. - or Retain any existing routing tables each time you route. If you choose this option, any manual changes you made to the routing of the traffic will be used next time that you route. ATM Overhead IP Overhead TDM Overhead SLS Field Length Link Utilization (%) The amount of overhead added to the signalling interface edge traffic load on the ATM network. The amount of overhead added to the signalling interface edge traffic load on the IP network. The amount of overhead added to the signalling interface edge traffic load on the SDH and/or PDH network. The Signalling Link Selection field length - part of the required routing information added to the signal in the overhead stack. The percentage of the link capacity utilised by signalling traffic, assuming no link faults, but allowing for unexpected fluctuations in the load. Important : You must set a value between 1 and 100. Link Utilization - 1 Link Fault (%) The percentage of the link capacity utilised by sighalling traffic, assuming one link in the network. Important : You must set a value between 1 and 100. Linkfault case to be routed The link fault case that will be used by default to route the signalling traffic, either zero fault, one link, one node or worst case.
Page 170
Setting the Handover Percentage Matrix

In the Traffic module, on the HO % Matrix tab of the Signalling Parameters dialog box, you can set the percentage of traffic that is handed over between specific MSCs. To do this: 1 2 3 Ensure you have created and configured the required number of MSCs. From the Traffic menu, point to Signalling and click Default Parameters. Click the HO % Matrix tab.
This matrix displays the percentage of signalling traffic that is handed over between the MSC equipments. In the example above, Equipment 2 hands over 20% of the signalling traffic to Equipment 1, whereas Equipment 1 hands over 30% of the signalling traffic to Equipment 2. To begin with, all of the values are marked with an asterisk (*) indicating they are at the default value. The default value is either 0% or a calculated value based on the LU values, using the formula:
Where H is the percentage of total calls which are handed over to the target node j from source node i E is the traffic per mobile subscriber (in Erlangs), either the Local Traffic/Subs Mobile value (defined on the Isw Voice and/or Isw Data Parameters tab(s) of an interswitch node dialog box) or the Mobile Traffic Traffic/Subscribers value/1000 (defined on the Voice Traffic Parameters tab of the Interswitch Parameters dialog box) L is the Location Update value from node i to node j as defined in the LU matrix
To change a value, double-click on the required box and enter the new value (the x axis represents the equipment handing the traffic over, while the y axis represents the equipment receiving the handover traffic. When you have set the correct values for all of the equipment, click Apply.
Page 171
Tip : If you edit one of the values yourself, and want to revert it back to be based on one of the defaults, click Reset to Default.
Setting the Default Parameters for Traffic Interface Edges

In the Traffic module, you can define default parameters for the different traffic interface edges, such as which protocol stacks are used, which traffic generation mode will be used and so on. To define these defaults: 1 2 From the Traffic menu, point to Traffic Interface Default Parameters. In the dialog box appears, you can define the following parameters for the different edge types: Warning: These parameters are not saved to the database, but are written to the registry of your local machine, so will be used on all projects by all users using the local machine.
Parameter Default Target Layer RAN Uplink Stack RAN Downlink Stack Transport Stack Trunk Type Traffic Generation Option (GSM interface edge types only) - or Full - Defines traffic for each individual traffic channel Important : The Full traffic generation can take a long time to calculate if you are using a large network. Channels Per Trunk The number of ch.annels in each trunk that are used for user traffic. Description The layer onto which the traffic edge will be routed. Specifies the protocol stack for the RAN uplink. Specifies the protocol stack for the RAN downlink. Specifies the protocol stack for the Transport interface. The granularity of the edge trunks, which is used for inverse multiplexing. Defines how traffic will be generated, either: Approximate - Defines an overall traffic figure
Adding Traffic Services and Types

In the Traffic module, you can create your own traffic services, and from these create your own traffic types. This enables you to closely model the traffic conditions within your individual networks. To add a traffic service: 1 2 3 4 5
Page 172
From the Traffic menu, click Traffic Types. In the dialog box that appears, click on the plus sign to expand the list of available traffic service templates. Select the template that most closely matches your requirements, and click with the right mouse button. From the menu that appears, click Add Service. A new service is created, based on the template values. Select the new service and edit the default values on the tabs:
6 7 8 9
General Traffic QoS Requirements Traffic CoS Requirements Delay Budget UMTS
Select the new service again, and click with the right mouse button. From the menu that appears, click Add Traffic Type. Select the new traffic type and edit the default values on the tabs. Click Apply when you have added all services and traffic types.
Editing Traffic Services

In the Traffic module, when you have created a traffic service, you can edit the values that it inherits from its template, in order to more closely match the conditions of your own traffic network. To do this: 1 2 3 Select the service that you want to edit. Edit the service properties on each tab. Click Apply.
Tip : To quickly edit the properties of a traffic service, select the traffic service template that it is based on, and on the Services tab edit the details of the required service.
Editing General Traffic Service Properties

In the Traffic module, on the General tab for a traffic service, you can edit the general properties of the traffic service. This table shows the properties that you can edit:
Item Name Traffic Model Description The name of the traffic service. This can be set to GTM (General Traffic Model) or left as Unspecified. The GTM contains further parameters defining your traffic, which you can define yourself. This can be set to Background, Conversational, Streaming or Interactive. This can be set to RT (Real-Time), NRT (Non Real Time) or Voice. The time interval between packets within the traffic stream. The average number of data packets that make up a call. Defines the activeness of one direction of traffic service connection. The default value 0.65 means that there is overlapping (0.15) of up and down links. Any additional planning comments you may want to make regarding the service. Information on when the traffic service was created and last edited.
Class Type Average Reading Time (sec) Average Number of Packets Activity Probability
Comments Change History
Page 173
Defining the General Traffic Model Parameters The GTM (General Traffic Model) enables you to define the properties of your traffic service to even greater detail. It describes the behaviour of your traffic inputs into the network model you have generated. The GTM models a bursty source of traffic, which has an on and off period. The source node transmits packets during the on period and stops transmitting in the off period. To define the GTM: 1 2 3 In the Traffic Types dialog box, on the General tab for the traffic service, ensure GTM is the selected Model. Click the Parameters button. In the dialog box that appears, set the following parameters:
Parameter Stack (User Header) Description The name of the header/overhead associated with a particular traffic service. This is used during Header Compression. You can choose from any header that you have defined in the Header Types dialog box. Packet Length Packet Interarrival Time Number of Packets in Packet Call The average number of octets that make up a packet within the traffic stream. The length of time between two packets during the on period. The average number of packets that make up a call. Discrete - Values change based on a fixed number. Deterministic - Values change by a rate based on a fixed number. Exponential - The rate of increase which becomes greater and greater as time progresses. Geometrical - An ordered set of numbers, where each number in turn is multiplied by a fixed amount to produce the next. Log Normal - Values change according to the log curve. Possible distribution model N/A
Packet Call Interarrival Time The length of time between two packets during the on period.
After you have set a distribution type, type a value for each parameter which will be used as the input into the distribution model.
Editing the QoS Requirements for Traffic Services

In the Traffic module, on the Traffic QoS Requirements tab for a traffic service, you can set the following Quality of Service requirements:
Item Max Delay (ms) Description The maximum acceptable end to end delay for the traffic service. This is the value used for the delay budgets on the Delay Budgets tab. The allowed probability of the queue extending, thus resulting in lower QoS packets being dropped. The percentage of packets that can be lost.
Tail Probability Loss
Page 174
Editing the CoS Requirements for Traffic Services

In the Traffic module, on the Traffic CoS Requirements tab for a traffic service, you can set the following Class of Service requirements:
Item Importance Description The importance factor, based on the packet delivery priority - the lower the number, the greater the priority. This determines the place in the queue. The urgency factor, based on the packet transfer delay - the lower the number, the greater the urgency. This determines the queue it will be placed in. The defined Class of Service.
Urgency
CoS Class
Creating Delay Budgets for Traffic Services

In the Traffic module, on the Delay Budget tab for a traffic service, you can edit the delay budgets for that service. The delay budgets specify the QoS requirements for traffic across your network, and are linked to routing parameters. You need to create the delay budget in order to calculate the traffic capacities correctly. Note : Before editing the delay budgets, ensure that you have set the traffic QoS requirements. To create a delay budget: 1 2 3 4 Select the layer that you want to create a budget for (for example, the IP module). Type the maximum required E2E (end-to-end) delay and loss, in ms. Click Add Budget. Click OK. The new budget appears in the list:
5 6 7 8 9
In the Budget Layer column, double-click the budget, and select the interface type from the drop-down list. In the Delay box, type the delay (in ms) for that element. In the Loss box, type the delay (in ms) for that element. Define the delay for a layer by double-clicking the appropriate column and typing the delay value in ms. If you want to further define the different delays for this budget, click Define Budget. The dialog box that appears lists all of the delay elements that make up that layer of your budget.
Page 175
Note : In the capacity calculation, even if the traffic meets the overall budget requirement but fails to meet one or more delay elements, it will still be considered to have succeeded in meeting the requirements. Therefore defining delays to this level is only recommended for detailed planning. 10 Click OK when you have defined the delay elements correctly. 11 Click Apply.
Defining the Service Direction for Traffic Services

In the Traffic module, on the UMTS tab for a traffic service, you can set the direction of the traffic flow: Bi-directional - the traffic flows in both ways Uplink - the traffic flows on the uplink channel only Downlink - the traffic flows on the downlink channel only Note : If you set a traffic service to uplink or downlink, you must also create a similar service in the opposite direction.
Editing Traffic Types

After you have created a traffic type, you can edit its properties. This table shows the properties that you can edit for any traffic type:
Tab General Property Name Service Bit Rate (Kbps) TTI Channel Mapping Comments Description The name of the traffic type. The service used by the traffic type. You can select any of the services that you have created. The bit rate for the traffic type. The transmission time interval, or interarrival time. The channel(s) that the traffic type uses - Logical and Transport. Any additional planning comments you may want to make regarding the traffic type.
Page 176
Adding Traffic to DIRECT Equipment

In the Traffic module, you can add traffic directly onto the equipment in your network. This is done slightly differently, depending on which equipment you are adding it to.
Adding Traffic to BSCs

In the Traffic module, on the BSC tab of a BSC equipment node dialog box, you can add and edit traffic (both actual and forecasted) to a BSC. To add a set amount of traffic: Select the first Override with Estimated Values dialog box, and type in the estimated traffic value in Erlangs. To add a calculated amount of traffic: 1 2 Select the second Override with Estimated Values dialog box. Type the following values: Number of supported BTSs Number of supported Cells Number of supported Trxs BTS parameter set used for the traffic
Based on these values, an estimated traffic value is calculated, and displayed in the Traffic (Erl) box. For a BSC equipment node, you can also view the GPRS results, both forecasted and actual.
Adding Traffic to BTSs

In the Traffic module, you can add the traffic demands directly onto a BTS, by manually configuring its cells, cell layers and TRXs. To do this: 1 2 3 4 5 Double-click on the BTS to which you want to add traffic. Click the BTS tab. If required, set the node parameters - the BCF ID for the BTS and any additional GPRS Overhead you wish to add to the traffic. Select the set of BTS default parameters to use. You can define these parameters on the BTS Parameters tab of the Cellular Parameters dialog box. If you want to add actual traffic, select Actual Cell Based, whereas if you want to add forecasted traffic, select Forecasted Cell Based. By default, the traffic is displayed in the number of Erlangs, but you can change this to display the number of subscribers by double-clicking on Erlangs in the Erl/Subs column and selecting Subscribers. 6 Add a cell by clicking the Add Cell button.
Page 177
7 8
Edit the cells LAC by double-clicking the existing one and then typing in the new code. To add a cell layer to the cell, select the cell and click the Add Cell Layer button. To change the Cell Layer type, double-click the current type and select the new one from the list that appears.
To add a TRX to a cell layer, select the cell layer and click the Add Trx button. Tip : To repeat an element, select the element you want to replicate and click the Duplicate button.
10 For the TRXs, you can edit the following values: Trx Sig - The amount of bits reserved for signalling User Tch in Trx - Number of spare traffic channels available for you to use
11 You can also configure (E)GPRS traffic requirements on the BTS tab. For information on how to do this, see Adding (E)GPRS Traffic to BTSs on page 178. This picture shows an example, where traffic has been added to BTS 3 in a 1+1 configuration.
Adding traffic to a BTS
Adding (E)GPRS Traffic to BTSs

In the Traffic module, you can add (E)GPRS traffic demands directly onto a BTS. Important : If you have created (E)GPRS traffic in ASSET3G and you synchronise ENTERPRISE with DIRECT, the traffic demands will be added automatically. To add them manually: 1 2
Page 178
Ensure you have added the required cells, cell layers and TRXs. For information on how to do this, see Adding Traffic to BTSs on page 177. Select the Show GPRS checkbox.
3 4
In the GPRS Enabled column for the required TRX, select the required technology type, either GPRS or EGPRS. In the Max. CS column, choose the required Coding Scheme. The Coding Scheme is used to protect the data from errors when crossing the radio path interface, and different coding schemes provide different data rates. This table describes the options:
Technology GPRS Coding Scheme CS-1 CS-2 CS-3 CS-4 EGPRS MCS-1 MCS-2 MCS-3 MCS-4 MCS-5 MCS-6 MCS-7 MCS-8 MCS-9 Data Rate (kbps) 9.05 13.4 15.6 21.4 8.8 11.2 14.8 17.6 22.4 29.6 44.8 54.4 59.2
In the appropriate columns, set the Default and Dedicated number of traffic channels (#TCH), where: The Default #TCH represents the number of traffic channels that can be shared between voice and (E)GPRS traffic depending on demand The Dedicated #TCH represents the number of traffic channels specifically reserved for (E)GPRS traffic only
In the GPRS Traffic (kbps) column, enter the total amount of (E)GPRS traffic throughput for the BTS. The maximum value will be determined by the coding scheme and number of available traffic channels.
Page 179
Adding Traffic to Node Bs

In the Traffic module, you can directly place traffic demands onto node Bs, by manually configuring its cells. To do this: 1 2 3 4 In the Traffic module view window, double-click the Node B to which you want to add traffic. Click the Node B User Plane tab. Click the Add Traffic button. In the dialog box that appears, enter the following information:
Item Uplink Traffic Type Downlink Traffic Type Dedicated AAL2s Description The type of traffic carried on the uplink. The type of traffic carried on the downlink. The number of AAL2 connections dedicated to this traffic.
5 6
Click OK. In the dialog box that appears, edit the traffic values. The following table describes the values:
Item Type of traffic Uplink and Downlink Traffic Types Dedicated AAL2s Description The use for the traffic - either primary or HO node traffic. The traffic types carried on the uplink and downlink. You can choose from all of the traffic types that you have created. The number of AAL2s dedicated to this traffic.
7 8
Click OK. The new traffic will appear in the list. You can optionally edit the number of offered subscribers in the All Subs column, which also has an effect on the total traffic (in Erl) and the number of dedicated AAL2s. Tip : You can edit the other properties for the Node B traffic (except the traffic value) by double-clicking the appropriate column.
Click Apply.
Page 180
Viewing and Editing the Traffic Properties of Equipment

In the Traffic module, you can view and edit the traffic properties of your network equipment. To do this, double-click the equipment that you want to edit. This section describes the different ways that you can edit the traffic properties.
Adding Cells to Node Bs

In the Traffic module, on the Node B tab of the Node B equipment properties dialog box, you can add UMTS cells to Node Bs. To do this: 1 2 3 Click Add cell. A new UMTS cell is added. Double-click the name of the cell to edit it. To remove a cell, select it and then click Remove cell.
Allocating Subscribers to SMSCs

In the Traffic module, on the SMSC Parameters tab of the SMSC Equipment properties dialog box, you can allocate the required number of subscribers to an SMSC. To do this: 1 2 3 4 In the Traffic module, double-click the SMSC node. Click the SMSC Parameters tab. Type the number of subscribers that you want to allocate to this equipment. Click Apply.
Assigning Codec Usage Percentages to Equipment

In the Traffic module, on the Codecs tab of the Equipment properties dialog box, you can assign codec usage percentages to nodes. In DIRECT, a codec is a method of compression used when transmitting voice traffic across a network. You can assign codecs to BSCs, MSCs, RNCs, WMSCs and CSMGWs. To assign a codec usage percentage to an equipment node: 1 2 If you want to send the codec usage percentages on to the cellular network, ensure that you have defined the traffic on the BSC. Ensure you have created your codec. To create a codec, you must create a voice (conversational) traffic type with the appropriate codec characteristics: Codec name Bitrate (in Kbps) TTI (Transmission Time Interval)
For more information on creating (codec) traffic types, see Adding Traffic Services and Types on page 172.
Page 181
3 4
Double-click the equipment node, and in the dialog box that appears, click the Codecs tab. Depending on the type of node you are assigning codec usage percentages to, you assign the percentage in a different way. The following topics describe what to do in each case. After you have assigned all of your percentages, you should set up your conversion rules. These rules specify how different codecs are converted in order to be compatible with each other when you are passing interswitch traffic between nodes.
Assigning Codec Usage Percentages to BSCs

You can assign a codec usage percentage to a BSC, which will be used to compress traffic sent from the BSC. To do this: 1 2 3 4 Double-click the equipment node, and in the dialog box that appears, click the Codecs tab. Select whether you wish to assign the percentage to the actual or forecasted traffic on the BSC. Click the Add/Remove Codec(s) button. In the dialog box that appears, select the checkboxes of the codecs that you want to add, and then click OK. Tip : To add all codecs, select the checkbox at the top of the list:
5 6
To allocate a percentage of voice traffic to use that codec, click on the % of Total Voice Traffic column for the required codec, and type the percentage. In the CS Data Traffic pane, set the percentage of the traffic from the BSC that is CS Data traffic. The rest of the traffic (up to 100%) is used for the voice traffic. Note : You can only do this if you have defined a Data Traffic codec, and specified this as the data traffic codec to use in the Interswitch Data Traffic Parameters.
Click Apply.
Page 182
Assigning Codec Usage Percentages to MSCs

You can assign codec user percentages to an MSC, to either: Define how received BSC traffic is compressed without having to define the underlying cellular network Define how received interswitch traffic from an EXT node is compressed Note : You do not need to define a data codec percentage on the MSC, because the interswitch voice and data traffic are generated separately. To define the percentages, you should set different values for the interswitch voice and data parameters in the MSC equipment properties dialog box. To do this: 1 Double-click the equipment node, and in the dialog box that appears, click the Codecs tab. In the Codec Distribution in Voice Traffic pane, you can view the accumulated percentages of codecs coming from the network under the node. 2 If you want to define how BSC traffic is compressed without defining the underlying cellular network, select the Show Internal Distribution option, and then select the Use User Defined Codec Distribution checkbox. - or If you want to define how received interswitch traffic is compressed, select the Show External Distribution option. 3 4 Click the Add/Remove Codec(s) button. In the dialog box that appears, select the checkboxes of the codecs that you want to add, and then click OK. Tip : To add all codecs, select the checkbox at the top of the list:
5 6
To allocate a percentage of voice traffic to use that codec, click on the % of Total Voice Traffic column for the required codec, and type the percentage. Click Apply.
Assigning Codec Usage Percentages to Node Bs

You can assign codec usage percentages for the traffic transmitted from Node Bs, in order to define the way that it is compressed. To do this: When you add traffic to a Node B, ensure that the traffic type you define for the uplink and downlink is a codec traffic type. For information on how to add traffic to a Node B, see Adding Traffic to Node Bs on page 180.
Page 183
Assigning Codec Usage Percentages to RNCs

You can assign codec user percentages to an RNC, to redefine how received Node B traffic is compressed. By default, it has some Node B codec usage assigned to it (and the % of voice traffic) but you may want to use another. To do this: 1 Double-click the equipment node, and in the dialog box that appears, click the Codecs tab. In the Codec Distribution in Voice Traffic pane, you can view the accumulated percentages of codecs coming from the network under the node. 2 3 4 Select the Use User Defined Codec Distribution checkbox. Click the Add/Remove Codec(s) button. In the dialog box that appears, select the checkboxes of the codecs that you want to add, and then click OK. Tip : To add all codecs, select the checkbox at the top of the list:
5 6
Assigning Codec Usage Percentages to CSMGWs

You can assign a codec usage percentage to a CSMGW, to redefine how received RNC traffic is compressed. By default, it has the RNC's codec usage percentages assigned to it (and the % of voice traffic) but you may want to use another. To do this: 1 Double-click the equipment node, and in the dialog box that appears, click the Codecs tab. In the Codec Distribution in Voice Traffic pane, you can view the accumulated percentages of codecs coming from the network under the node. 2 3 4 Select the Use User Defined Codec Distribution checkbox. Click the Add/Remove Codec(s) button. In the dialog box that appears, select the checkboxes of the codecs that you want to add, and then click OK.
Page 184
Tip : To add all codecs, select the checkbox at the top of the list:
5 6
Assigning Served External Networks

To assign the external networks that will be served by a node: 1 Ensure that you have defined the required external networks. For information on how to do this, see Adding and Removing Known External Networks for Interswitch Traffic on page 164. Important : If you intend to assign external networks to non-EXT nodes, you must assign the external networks to the EXT node first. 2 3 4 Ensure that you are in the Traffic module. Double-click the required node. In the dialog box that appears, on the Served Networks tab, select the checkboxes for the external networks you want to assign:
Assigning external networks
Creating EDAP Pools for GPRS Data

In the Traffic module, on the EDAP Pools tab of the equipment node dialog box , you can create EDAP (Enhanced Dynamic Abis Pool) pools. In EDGE networks, each Air-traffic channel can transmit data using a different modulation scheme, and therefore a different bit rate. For example, the highest modulation scheme is MCS-9, which has a bit rate of 59.2 Kbit/s. However, the higher the bit rate the more sub-timeslots per traffic channel you will need to allocate on the Abis interface. For example, MSC-9 requires 5 sub-timeslots. You can use EDAP pools to reduce the required number of timeslots that need to be reserved for EGPRS data. In an EDAP pool, a group of timeslots is reserved to be shared between all of the EGPRS-enabled traffic channels, on the basis that not all of them will be required at once.
Page 185
To create an EDAP pool: 1 2 3 4 Double-click the required BTS, and then click on the EDAP pools tab. Select whether to use the actual or the forecasted configuration. This indicates whether the pool will be created based on the actual or forecasted EGPRS traffic. In the Select EDAP Pool pane, enter a name for the new pool and click the New EDAP Pool button. Choose which Trxes you want to include in the pool by selecting them in the Available list and clicking the Add button. Note : Only unassigned Trxes that have been EGPRS-enabled are displayed in the Available list. 5 6 Set the Pool overflow probability to the correct value. This is the probability of the traffic load exceeding the pool capacity. Ensure that the throughput target of Air TCH is set to the correct value. This figure is calculated by dividing the total EGPRS traffic for the TRXs in the pool by the total number of EGPRS enabled Air TCHs. You can set your own target by selecting the Override checkbox, and entering your own value. Note : Currently the Used MCS rate is set to MCS-9, and cannot be changed, as the calculation model is based on this rate. Based on the inputs set in the EDAP Pool Settings pane, DIRECT calculates the Air-traffic channel throughput for different EDAP pool sizes, and then displays them at the bottom of the dialog box:
For example, if the pool has 5 64kb/s timeslots, then the throughput per channel would be 21.279 kb/s. 7 Based on these calculations, you can edit the EDAP Pool Values. By default it displays: The calculated EDAP pool size - This is calculated by DIRECT automatically, by cross-referencing the Throughput target of Air TCH (kb/s) with the Pool Size Calculations, and choosing the minimum allowable pool size. For example, based on the pool size calculation table above, if the throughput target was 15.34, then the calculated EDAP would be 5. However, you may want to override this value (for example, if you expect a high rate of failure or know that the actual traffic throughput will be low for a particular period). To do this, select the Override Pool Size checkbox and type the required number (up to a maximum size of 12).
Page 186
Total EGPRS Traffic - This is calculated by DIRECT automatically, by multiplying the Total EGPRS enabled Air TCH by the throughput value corresponding to the calculated EDAP Pool size (kb/s). You can override the total traffic value by entering your own value. In the example below, the total EGPRS traffic value of 0.124 is calculated by multiplying the throughput for a pool size of 1 (0.0062) by 20.
Click Apply. Tip: To edit an EDAP pool, select the required pool and click the Edit EDAP Pool button. You can then edit the parameters and recalculate the EDAP pool sizes.
To delete an EDAP pool and un-assign any TRXs allocated to it, select the required pool and click the Delete EDAP Pool button.
Defining and Using Your Own Interswitch Traffic Values

In the Traffic module, you can define your own interswitch traffic values, rather than have the Traffic Generator create them for you. This would be useful, for example, if you have added a single MSC, and want to generate traffic for it without regenerating all interswitch traffic again. To define the new traffic values: 1 2 Add the traffic on the interswitch requirement edge. For information on how to do this, see Adding Traffic To Requirement Edges on page 212. Generate interswitch traffic, using the Generate traffic and update existing requirements that are not user-defined option. In Microsoft Excel, open the results file. By default, it is located in the ENTERPRISE folder of your software installation, but you may have defined another path when you originally generated traffic. Click the Measured tab. In the Measured Interswitch Traffic section, enter the traffic values on a node-bynode basis. From the File menu, click Save As.
Page 187
- or 1
2 3 4
5 6 7
In the dialog box that appears, type a new name for the modified results file. Click Save. Generate interswitch traffic in the usual way, but at step 5, select the modified Excel file that you have created.
After you have used your own interswitch traffic values to generate traffic, you can view and edit the interswitch requirements. For more information on how to do this, see Viewing and Editing Requirements for Interswitch Nodes on page 219.
Defining Preferred Nodes for Interswitch and Signalling Traffic

In the Traffic module, you can define the Points of Interconnection (POI) from network switch nodes (for example, MSCs) to external networks and also preferred internal network connections. When you subsequently generate interswitch and/or signalling traffic, it will be distributed to this preferred POI node. To define a preferred POI in an internal network: 1 2 3 Ensure that you have created and configured the node correctly. Double-click the required switch node. In the dialog box that appears, on the Network Connections tab: In the Internal Network Connections pane, click the Add Distribution Type button Right-click in the blank space of the Internal Network Connections pane, and from the menu that appears, click Add Distribution type
- or 4
Select the equipment type of the internal node and click OK. A list of the available nodes of that type appears. You can select logical equipment types if required.
5 6
Select the one(s) that you want to connect to. In the Traffic% column, double-click the appropriate figure and type the percentage of traffic to assign to the connection.
If you want to generate VMS, IVR or Prepay traffic for a particular switch node, you must define specific connections for it. To do this: 1 2
Page 188
Ensure that you have created and configured the node correctly. Double-click the required switch node.
3 4
In the dialog box that appears, on the Network Connections tab, select the VMS/IVR/Prepay nodes that you want to connect to. In the Traffic% column, double-click the appropriate figure and type the percentage of traffic to assign to the connection. For signalling traffic, the internal connection that you define is used in parallel with the node that you have defined as the preferred distribution type for the signalling message flows in the Signalling Service Editor.
To define preferred POIs for an external network: 1 2 3 4 Ensure that you have created an external network in the Interswitch Parameters dialog box and that the external network has been assigned to an external node. In the External Network Connections pane, expand the list of external networks of each type. Select the external network that you want to link to. In the POI column, the Default setting looks for EXT equipment nodes which serve the selected network and selects the closest one that is connected with an interswitch interface. If none exist, the tool will select one node serving the network. If you want to define a specific equipment node or nodes to distribute the traffic to the selected network, right-click the external network and from the menu that appears, click Add POI.
- or Select the external network, and click the Add POI button. A new POI appears in the list. 6 In the POI column, select the required equipment node, and (if required) in the Traffic % column set the required percentage of traffic to assign to the connection. The percentage you set here will affect the Traffic % distributed to any other POIs for the same external network. To set different percentages for incoming and outgoing traffic: Right-click the POI and from the menu that appears, click Toggle Symmetric - or Select the POI and click the Toggle Symmetric button
Type the required incoming and outgoing values in the In/Out columns.
Page 189
Creating Supported Services

In the Traffic module, you can create logical traffic equipment for specific supported services (for example, football updates or weather updates), and then assign this functionality to physical SMS equipment. To do this: 1 In the Equipment Editor, create a logical SMSC equipment that represents the required SMS service:
Locate the physical SMS equipment that you want to add this SMS service to, and on the Traffic Functionality tab, select the service:
The SMS service is now supported within any SMSC1 equipment that is created in the module view window. 3 Create the signalling service, and ensure that it is assigned to the logical SMSC equipment that you have defined here.
Page 190
Viewing and Editing Dispatcher Systems on a DSC

In the Traffic module, on the DSC tab of a DSC equipment node dialog box, you can view and edit the dispatcher workstations on the DSC. You can set the number of DWSs on the DXT, and the number of channels each DWS monitors. To do this: 1 In the Dispatcher System pane, click with the right mouse button:
2 3 4
From the menu that appears, click Add Workstation. A new DWS is added to the list. To edit the number of monitored channels, double-click the current number and enter the new one. Click Apply.
Note : The number of DWSs that you can add to a number of DSCs is limited to the value set in the Equipment Editor on the DXT Parameters tab. Deleting DWSs To delete a DWS: 1 2 Select the DWS that you want to delete. Click with the right mouse button, and from the menu that appears, click Remove Workstation. The DWS is deleted. Copying DWSs on DSCs To add a duplicate DWS to the same DSC: 1 2 Select the DWS that you want to copy. Click with the right mouse button, and from the menu that appears, click Duplicate Workstation. A duplicate DWS is added to the list.
Page 191
Viewing and Editing ISW Node Parameters

In the Traffic module, on the ISW Node Parameters tab of an equipment node dialog box, you can edit the interswitch node parameters. The following table describes the parameters:
Item Gravity Center Description Indicates whether or nor the gravity centre is used. Gravity centre co-ordinates move the point of the subscriber location away from the physical location of the switch to the population concentration centre point. The gravity center co-ordinates give a more accurate distance value for the Traffic Generator to use when calculating the halving factor. If you have selected the Gravity Center option, you must enter the x and y co-ordinates. If the Gravity Center option is not chosen, the physical co-ordinates are used. Transit Export Routing Table Indicates whether or not the node can be used as a conduit to transfer traffic between networks. This option is usually disabled for external nodes assigned to an external network. Whether the export function is enabled or disabled. The route in which this node is contained the nodes linked to this one are listed, as well as information on whether it is a direct link or one that uses hopping. You can edit the routing tables to define the routes for your network. For information on how to do this, see Creating Routing Tables on page 261.
Viewing and Editing Isw Voice Traffic Parameters

In the Traffic module, on the Isw Voice Traffic Parameters tab of the equipment node dialog box, you can set the parameters that will be used for interswitch voice traffic. The following table describes the properties:
Item Traffic (Erl) Number of Trunks Traffic/Subs - Fixed (mErl) Description The total traffic (in Erlangs) relative to the number of subscribers to the node. If required, you can select to Use Estimated Traffic and type your own value. Total number of trunks required in the node. The traffic per fixed subscriber, using either the global value defined in the Interswitch Default Parameters or the value local to this node that you can set yourself. This property is reflected in the Traffic (Erl) value in the traffic model. The traffic per mobile subscriber, using either the global value defined in the Interswitch Default Parameters or the value local to this node that you can set yourself. This property is reflected in the Traffic (Erl) value in the traffic model. The number of subscribers served by the node. This is multiplied by the traffic per subscriber value to give an estimated traffic value. The percentage value of subscriber originating traffic in relation to the total subscriber traffic. The percentage value of originating traffic to its own network in relation to the total subscriber originating traffic. The percentage value of traffic diverted back to the external network in relation to the total incoming traffic from other networks. The percentage value of mobile subscribers - 0 if the switch is a local exchange with fixed subscribers or 100 if the switch served only mobile subscribers. Number of calls attempted during the busiest hour of the day. This figure can be compared to switch limits. The average length of calls to the Voice Mail Server in seconds.
Traffic/Subs - Mobile (mErl)
Number of Subscribers Subscribers Originating (%) Subs Orig to Own Network (%) Loop Back of Incoming (%) Mobile Subscribers (%) BHCA VMS Call Length (s)
Page 192
Terminating calls rerouted to VMS (%) Calls to VMS/Left Message IVR Call Length (s) IVR Calls/Subscriber/Hour Prepaid Calls Percentage (%)
The percentage value of terminating calls forwarded to the VMS. The average number of calls made to the VMS per left message. The average length of calls to Interactive Voice Response mode. The average number of calls to the IVR per subscriber in the busy hours. The percentage of prepaid calls from this node.
Viewing and Editing Prepay Parameters

In the Traffic module, on the Prepay Parameters tab of an equipment node dialog box, you can view and edit the following details:
Property Successful Prepay Call Percent (%) Description The percentage of successful calls to this PP equipment. This value is applied to the incoming traffic to calculate the value of the outgoing traffic.
Viewing and Editing MSC Traffic Properties

In the Traffic module, on the MSC tab of an MSC equipment node dialog box, you can view and edit the traffic properties of the MSC. The following table describes the properties:
Item Traffic (Erl) A Interface Capacity (Trunk) Ater Interface Capacity (Trunk) 3g A Interface Capacity (Trunk) Description The amount of traffic (actual and forecasted) at the MSC. This can be originating, terminating or throughgoing traffic. The MSC capacity for traffic across the A interface. The MSC capacity for traffic across the Ater interface. The MSC capacity for traffic across the 3g A interface.
You can also view and edit MSC traffic properties on the following tabs: Isw Node Parameters Isw Voice Traffic Parameters Network Connections Signalling Traffic Parameters Signalling Node Parameters
Page 193
Viewing and Editing PSTN Traffic Properties

In the Traffic module, on the PSTN Parameters tab of the PSTN equipment node dialog box, you can view and edit the PSTN traffic properties of the node. The following table describes the properties that you can edit:
Item Concentration Description Designates whether or not the node is concentrated. ETSI v5.2 defines the standard for concentration between the access and local exchange. The maximum number of 2Mb links the standard allows is 16 (DIRECT also supports v5.1). Note : In the chain of access nodes, only one is allowed to have concentration. Subscriber lines Number of lines for each available line type: - POTS (64k) - a 64k telephone line - ISDN (2B+D) - a 2B channel ISDN connection - ISDN (30B+D) - a 30B channel ISDN connection These can be specified for 3 groups - Home, Business and PABX Multihoming Weight (PSTN Access nodes only) Specifies the amount of traffic routed to the node. The lower the weight value, the less traffic routed to the node.
Viewing and Editing RNC User Plane Traffic

In the Traffic module, on the RNC User Plane tab of an RNC equipment node dialog box, you can view the calculated RNC user plane traffic and edit the estimated RNC user plane traffic. To edit the estimated RNC user plane traffic: 1 2 Select the Estimated traffic option. In the pane corresponding to the required type of user plane traffic, click with the right mouse button, and from the menu that appears, click Add estimated traffic. A traffic type is added to the pane. 3 To add traffic values for uplink and downlink served connections, double-click the appropriate column for the traffic type and type the value.
To delete a traffic estimate, click with the right mouse button on the estimate and from the menu that appears, click Delete estimated traffic.
Page 194
Viewing and Editing Signalling Node Parameters

In the Traffic module, on the Sig Node Parameters tab of an equipment node dialog box, you can view and edit the parameters used for signalling purposes. The following table describes these parameters:
Item STP Functionality Number of Links Relative Size Description Indicates whether or not Signalling Transfer Protocol functionality is enabled or disabled. The number of links in the cases of 0 faults, 1 link fault and 1 node fault in the signalling network. These values are calculated by DIRECT. The relative size of the node compared with other nodes of the same type this determines how the traffic capacity a node that is twice the relative size of another will have twice as much traffic sent to it. The route in which this node is contained the nodes linked to this one are listed, as well as information on whether it is a direct link or one that uses hopping.
Routing Table
Viewing and Editing Signalling Traffic Parameters

To set the node parameters for signalling traffic: 1 2 3 4 Ensure that you are in the Traffic module. Double-click the required signalling node. In the dialog box that appears, click the Sig Traffic Parameters tab. On this tab, choose from these options:
Item SSP Functionality Description SSP is the Service Switch Point functionality. Choose to either: Have SSP functionality built into this node - or Have SSP functionality provided by another node in the signalling network of your choosing Preferred SCP Set the preferred Service Control Point manually. - or Leave it as None, for DIRECT to select the closest one according to routing. IMSI Attaches The number of International Mobile Subscriber Identity attaches per subscriber per busy hour. The number of times a subscriber will have to send an activate/deactivate message during the busy hour.
Viewing and Editing TETRA Cells and TRXs

In the Traffic module, on the TBS tab of a TBS equipment node dialog box, you can view and edit TETRA TRXs and define their capacities. To do this: 1 Ensure you have selected the Cell Based option:
Page 195
You can only create individual TRXs if you have selected this option. 2 Click the Add Trx button. A new TRX is created, and given default traffic values based on the TETRA network parameters. 3 Choose to view the traffic information for this TRX as Cell Based (by default), Erlang based or Subscriber based. 4 If you select Erlang based, you can define the quantity of traffic, and this automatically generates the correct number of TRXs If you select Subscriber based, you can define the number of subscribers, and this automatically generates the correct number of TRXs
Click Apply.
Viewing DXT Node Information

In the Traffic module, on the DXT tab of an equipment node dialog box, you can view the node information for a DXT. The following table describes the information shown:
Item Number of TBSs Number of TRXs Number of DSCs Number of DWSs Traffic Description The number of TBSs connected to the DXT. The number of TRXs connected to the DXT. The number of DSCs connected to the DXT. The number of DWSs connected to the DXT. The total traffic at the DXT (in Erlangs).
Viewing (E)GPRS Traffic Results

In the Traffic module, on the GPRS Results tab of an equipment node dialog box, you can view traffic statistics, based on GPRS and EGPRS, and on actual and forecasted values. This table describes the statistics that you can view:
Item Traffic (kbit/s) Used capacity (#'TCH) Reserved capacity (#TCH) Enabled TRXs (#TRXs) Enabled Cells (#Cells) Description Amount of traffic at the parent node - for example, the BTS for a BSC, the BSC for an SGSN. Average number of traffic channels in use at a given time. Number of traffic channels permanently or semi-permanently reserved for the selected type of traffic. Number of TRXs enabled for the selected type of traffic. Number of cells enabled for the selected type of traffic.
Page 196
Viewing MGW Served Connections

In the Traffic module, on the MGW tab of a MGW equipment node dialog box, you can view the served connections of the MGW. The following table describes the properties:
Item Service Served Connections Description The type of service, uplink or downlink. The connections that use this service.
Viewing SGSN-3G Served Connections

In the Traffic module, on the SGSN-3g tab of an SGSN-3g equipment node dialog box, you can view the served connections of the SGSN-3G. The following table describes the properties displayed:
Viewing the Routing Table for Traffic

In the Traffic module, on the Routing Table tab of an equipment node dialog box, you can view the routing tables for the MSC traffic. You can view the following details:
Item Destination/Hop Description The route in which this node is contained the nodes linked to this one are listed, as well as information on whether it is a direct link or one that uses hopping.
Viewing WMSC Served Connections

In the Traffic module, on the WMSC tab of a WMSC equipment node dialog box, you can view the served connections of the WMSC. The following table describes the properties:
Page 197
Overview of the Traffic Module Signalling Layer

In the Signalling layer of the Traffic module, you can: See all the network elements that have been created or imported into the Interswitch module Add additional signalling elements in order to create the full network signalling network requirements needed to create the inter-node traffic requirements, in other words the ability to add SMSC, STP, SCP and HLR Set each node to allow STP or SSP functionality Calculate the routing table for each network element and then manually edit it to create your preferred routing option Define parameters for global signalling, VLR messages, signal message length and the location area update matrix, which are required for use by the Signalling Traffic Generation program.
Creating the Signalling Traffic Network

In the Traffic module, you can create the SS7 Signalling network. If you are new to DIRECT, it is recommended that you follow the work order set out below when planning your first few signalling networks. 1 2 3 4 5 Set the signalling traffic parameters. Create signalling protocols, fields, messages and services. Generate signalling traffic for the entire signalling network, or add traffic individually to signalling edges. Route the signalling traffic. Analyse the results, change the topology if necessary, and route again in order to meet the optimum network.
Defining Signalling Traffic Services and Protocols

The Signalling Service Editor enables you to add any new signalling protocol to the Signalling Module, making it easier for you as a planner to cope with new situations. You can model all kinds of signalling messages, including 3g messages. You can: Manually add and edit the fields of signalling messages in the Signalling Field Editor (SFE). Message fields belonging to a certain protocol are grouped together.
Page 198
Edit the messages belonging to a service. You can group together message fields to form a signalling message, with messages belonging to a certain protocol being grouped together. You can do this in the Signalling Message Editor (SME).
Page 199
Create the message flow between elements for a certain service. This is done through the Signalling Service Editor (SSE).
Tip : You can import a set of default services, messages and protocols that are supplied with DIRECT as an XML file, DirectSignallingServiceSamples.xml. For information on importing, see Exporting and Importing in DIRECT on page 91.
Adding and Editing Signalling Protocols

In the Traffic module, you can create and edit signalling protocols, to which you can further add fields and messages. To do this: 1 2 3 4 From the Traffic menu, point to Signalling and click Service Editor. In the list in the left-hand pane, click with the right mouse button on the Protocols heading. From the menu that appears, click Add Protocol. On the General tab, type the name of the protocol. If required, you can add your own planning comments too.
After you have created protocols, you can create fields and messages.
Page 200
Adding and Editing Signalling Fields

In the Traffic module, you can create and edit the fields that signalling messages contain, for example, the TCAP, the SCCP or the MTP. For a given protocol, you can define any number of fields, their length (in order that you can calculate what proportion of the entire message length they occupy), plus any planning notes you may want to include. To create a field for a protocol: 1 2 3 From the Traffic menu, point to Signalling and click Service Editor. From the list in the left-hand pane, double-click the required protocol. On the Fields heading, click with the right mouse button, and from the menu that appears, click Add Field. A new field is added to the list. 4 5 On the General tab, you can edit the field name, length (in bytes) and notes. Click Apply.
After you have created fields, you can then create messages.
Adding and Editing Signalling Messages

In the Traffic module, you can create and edit the signalling messages for a given protocol, configuring the signalling length and content. To do this: 1 2 3 From the Traffic menu, point to Signalling and click Service Editor. From the list in the left-hand pane, double-click the required protocol. On the Messages heading, click with the right mouse button, and from the menu that appears, click Add Message. A new message is added to the list. 4 5 6 7 On the General tab, you can edit the message name and any planning comments. Click the Message tab. To add a field to the message, click the name of the field in the Fields pane, and drag it onto the message pane. Edit the field length by double-clicking the current length, and typing the new value. Edit the field notes by double-clicking the current notes, and typing the new notes. Note : Editing the field length or notes here will only change the value for this message only. You can change the default field length and notes in the Fields section of the Signalling Editor. 8 Click Apply. After you have created messages, you can create message flows within signalling services.
Page 201
Adding and Editing Signalling Services

In the Traffic module, you can create signalling services. Services and message flows differ between operators, who have differing demands for the signalling network. To create a signalling service: 1 2 3 Ensure you have created the required signalling messages, with appropriate fields. From the Traffic menu, point to Signalling and click Service Editor. Double-click Services, and then select either All Projects or Current Projects, depending on whether you want the service to be available globally to all projects or just this one. Note : Later on, if you want to make a project service available to other projects, you can do this by cutting and pasting the service from the Project Services folder to the Global Services folder. 4 Click with the right mouse button, and from the menu that appears, click Add Service. A new service is added to the list. 5 6 7 Select the new service from the list. On the General tab, you can edit the service name and choose the type of service. Click the Service Parameters tab, and set: 8 Overheads for signalling traffic in the IP, ATM, SDH/PDH networks The required number of transactions per subscriber in the busy hour The type of traffic (either Voice or Data) that this service can generate
Click the Message Flow tab to view the message flows. Message flows are shown as a series of vertical lines representing the equipment types of nodes in the flow, and horizontal arrows representing messages going between nodes.
To place a node on the message flow, either: In the flow pane, click the Add Equipment button - or In the flow pane, click with the right mouse button at the point in the flow at which you want to place the equipment, and from the menu that appears, click Add Equipment:
10 In the dialog box that appears, select the required logical equipment type, group or detailed type and choose one of these options for the node:
Item Send to All Preferred Node of
Description If there is more than one instance of this node type in the network, the full amount of traffic is sent to each node. If there is more than one instance of this node type in the network, you can choose to send the traffic to a selected node. Note : To use this option, you must define the preferred type in the equipment properties dialog box, on the Network Connections tab.
11 Continue adding equipment as required. You need at least two pieces of equipment to create a message flow. Tip : To increase or decrease the font size used, use the Font Size up and down arrow buttons on the toolbar:
12 To add a message to the equipment in the flow, either: Click the Add Message button - or Click with the right mouse button, and from the menu that appears, click Add Message
13 In the dialog box that appears, from the Origin and Termination drop-down lists, select the start and finish nodes. 14 From the list of signalling messages, select the required message:
15 Click OK.
Page 203
A new message is added to the signalling flow:
The vertical name along the length of the node indicates whether it will distribute to all or a preferred node. Tip: To change the direction of the flow of the message, on the message in the flow pane, either: Click the Reverse Direction button - or Select the message, click with the right mouse button, and from the menu that appears, click Reverse Direction
To change the message type, select the message, right-click and then click Change Message. To delete a message, select the message, and then click the Delete Message button . 16 Continue to add nodes and messages to complete your message flows. Tip : If your message flow is becoming too cluttered, click the Space Flows button to evenly spread the nodes and messages. 17 Click Apply.
Page 204
This picture shows an example message flow.
Example Signalling Message Flow
Tips : You can also create and edit signalling services using keyboard shortcuts. For a list of these, see Using Keyboard Shortcuts to Add and Edit Signalling Services on page 205. To use an existing signalling service as a template, copy and paste it into the required folder. Using Keyboard Shortcuts to Add and Edit Signalling Services When you are adding and editing signalling services, you can use a number of keyboard shortcuts instead of the toolbar provided on the user interface. This table describes the available shortcuts:
Use This Shortcut ALT + L ALT + M ALT + S Tab ALT + D ALT + R ALT + left/right arrow ALT + up/down arrow To Add a node to the message flow. Add a message to the flow. Space the nodes and messages equally. Move through and select nodes and messages. Delete a selected node or message. Reverse the direction of a selected message. Move the selected node left and right. Move the selected message up or down.
Page 205
Viewing and Editing Requirement and Interface Edges

In the Traffic module of DIRECT, you can view and edit requirement and interface edges. This table describes what you can do with each different type of edge:
On this edge Cellular You can View the traffic generated in the cellular equipment on the following tabs: General Edge Traffic Cellular Edge Route Properties Routes Interswitch or Signalling Requirement View the traffic generated in Trmod.xls, on the following tabs: General Traffic (Signalling Requirement edge only) Edge Traffic (Interswitch Requirement edge only) Route Properties (Interswitch Requirement edge only) Routing (interswitch Requirement edge only) Codec Distribution (Interswitch Requirement edge only) Routes (Signalling Requirement edge only) Interswitch or Signalling Interface Define interswitch or signalling traffic, on the following tabs: General Traffic (Signalling Interface edge only) Edge Traffic (Interswitch Interface edge only) Route Properties Routing Properties Codec Distribution (Interswitch Interface edge only) Routes
To view or edit edge information: Double-click the required edge.
Page 206
The edge dialog box opens. The appearance of this will vary, according to the edge type.
Viewing GSM Interface Traffic On the Cellular Edge tab of a GSM interface edge dialog box, you can view the GSM interface traffic generated by the equipment connected to the edge. To do this: 1 2 3 Double-click the required GSM interface edge. In the GSM Interface Edge dialog box, click the Cellular Traffic tab. This tab displays the actual and forecasted traffic values for the edge. Depending on the Traffic Generation mode that you select, the traffic will be defined in a different way: If you select the Full option, the traffic is defined for each individual channel, according to the traffic defined at the connecting equipment. For example, if the Default BTS parameter set on the BTS is set at FR32K, then the traffic is defined per 32K traffic channel. If you select the Approximate value, the traffic requirement from the equipment is summed together, and based on the defined granularity and the number of 64k channels per trunk, the number of required trunks/edges is calculated.
Page 207
The dialog box also displays the load per edge percentage - the traffic load is spread evenly across the edges, then the load is calculated as a percentage of the edge's total capacity.
Tip : You can set the traffic generation mode automatically in the Traffic Interface Edge Defaults. Adding and Removing Logical Connection Traffic On the Edge Traffic tab of a dialog box, you can add, remove and edit the logical connection traffic in the Traffic module. Note : You can only add traffic to a traffic edge, except for cellular traffic, which is added to the cellular interface edges.
Example Edge Traffic tab
To add traffic to a logical connection edge: 1 2 3

Page 208
On the Edge Traffic tab, click the Add Traffic button. A new piece of traffic is added to the list. Double-click the YX column for the new traffic, and select the type of traffic (for example, WWW 16k). Double-click the Subscribers column for the new traffic, and type the number of subscribers to this traffic.
The YX Total will be automatically calculated, based on the rate for the type of traffic (shown in the XY Rate column). 4 1 2 Click Apply to save this traffic. Select the traffic, and click the Remove Traffic button. The traffic will be removed from the list, and the Total Capacity on the Edge updated accordingly. To remove traffic from any type of traffic edge:
Viewing and Editing ISW Interface Traffic To view and edit the interswitch traffic demand for an edge: 1 Ensure that you are in the Traffic module, and that you are displaying interswitch interface edges. Tip : To display these edges, click 2 3 4
Item Link Capacity and Equivalent # 64ks - Zero Link Fault Case, One Link Fault Case, One Node Fault Case, Worst Case
Double-click the required interswitch interface edge. In the dialog box that appears, double-click the Edge Traffic tab. You can view and edit the following traffic values:
Description The amount of edge capacity used in the zero link, one link, one node and worst case conditions. These values are calculated when you calculate link and node fault values, and are defined in either Erlangs or 64k Equivalents (except for worst case, which is the highest of the other three values in 64k Equivalents). You can also select to route your interswitch interface traffic based on any of these fault cases.
Routing Requirements - Granularity, 64k Ch Per Trunk, Number of Channels/Trunks, Load Per Edge (%)
You can define routing requirements for traffic using this edge, specifically: The routing granularity of the (interswitch) interface edges. Selecting the most appropriate granularity can greatly reduce the time taken to route the traffic; for example, if the interswitch traffic will not share the PDH frame with any other traffic, then you can set the granularity to 2Mb or 1.5Mb and greatly reduce routing time. Important : If you are routing onto IP or ATM, you must set the granularity as none. The 64k Ch Per Trunk value is based on the granularity: for 64k, it is set automatically to 1, but for 2Mb and 1.5Mb, you can set it manually within certain ranges (between 1 and 32 and between 1 and 24 respectively). The Number of Channels/Trunks is calculated automatically by default (based on the granularity and the number of channels per trunk), but you can override this value with your own if you want to test certain network conditions. For 64k granularity this value represents the number of channels, but for the other two granularity options this value represents the number of trunks. Load Per Edge is the required % load for each edge. Indicates the equipment connected. Indicates the type of traffic (voice or data), the direction (X to Y is uplink, Y to X is downlink) and the traffic name. Indicates the node whose subscribers have generated the traffic. The amount of traffic for a particular named traffic, in Erlangs.
Connections Traffic Origin Node Erlangs
Page 209
Item Total Erlangs (Traffic Type and Direction)
Description Displays the total traffic for the different types and directions, in Erlangs.
Viewing and Editing Signalling Interface Traffic To view and edit the signalling traffic demand for an edge: 1 2 3 4
Item Load with ATM Overhead Load with IP Overhead Zero Fault Case Utilisation Percentage
Ensure that you are in the Traffic module. Double-click the required signalling edge. In the dialog box that appears, click the Traffic tab. You can view and edit the following values:
Description The total traffic load including the ATM overhead. The total traffic load including the IP overhead. The percentage of the edge capacity used in the zero fault condition. You can use either the Global value (set on the Routing tab of the Signalling Parameters dialog box) or a Local value, defined here. Important : You must set a value between 1 and 100.
One Fault Case Utilisation Percentage
The percentage of the edge capacity used in the one link fault, one node fault and worst case conditions. You can use either the Global value (set on the Routing tab of the Signalling Parameters dialog box) or a Local value, defined here. Important : You must set a value between 1 and 100.
Link Capacity and Equivalent # 64ks - Zero Link Fault Case, One Link Fault Case, One Node Fault Case, Worst Case
The amount of edge capacity used in the zero link, one link, one node and worst case conditions. These values are calculated when you calculate link and node fault values, and are defined in 64k Equivalents (except for worst case, which is the highest of the other three values defined in 64k Equivalents). You can also select to route your signalling interface traffic based on any of these fault cases.
Routing Requirements - Granularity, 64k Ch Per Trunk, Number of Channels/Trunks, Load Per Edge (%)
You can define routing requirements for traffic using this edge, specifically: The routing granularity of the (signalling) interface edges. Selecting the most appropriate granularity can greatly reduce the time taken to route the traffic; for example, if the interswitch traffic will not share the PDH frame with any other traffic, then you can set the granularity to 2Mb or 1.5Mb and greatly reduce routing time. Important : If you are routing onto IP or ATM, you must set the granularity as none. The 64k Ch Per Trunk value is based on the granularity: for 64k it is set automatically to 1, but for 2Mb and 1.5Mb you can set it manually within certain ranges (between 1 and 32 and between 1 and 24 respectively). The Number of Channels/Trunks is calculated automatically by default (based on the granularity and the number of channels per trunk), but you can override this value with your own if you want to test certain network conditions. For 64k granularity this value represents the number of channels, but for the other two granularity options this value represents the number of trunks. Load Per Edge is the required % load for each edge.
Page 210
Item Connections Traffic
Description Indicates the equipment connected, with node x being the originating node, and node y the terminating node. Displays information for all of the traffic routed through this edge, including the traffic name, direction (the nodes involved), traffic type, any signalling messages attached and the rate in Kbps.
Viewing the Codecs Distributed on an Edge In the EdgeGroup dialog box for an Interswitch edge (either requirement or interface), on the Codec Distribution tab, you can view the codecs that will be used to carry the traffic on this edge. This is based on the codecs that you have assigned to the nodes at either end of the edge. The name of the codec is displayed, as well as the percentage of the total voice traffic that uses this codec. Defining Routing Strategies for Interswitch Edges On the Routing tab of the Interswitch Requirement edge dialog box, you can: Select which routing strategy the edge will use Edit the routing strategies used when routing the interswitch traffic over this particular edge Select a link fault case that will be used by default when routing this edge A routing strategy specifies the number of routes between a switch pair, and for each route the percentage of total traffic in one direction. The sum of percentage values can be over 100% if spare capacity is allocated for recovering from failures. Typical values are 100% for primary routes and 20% for secondary routes. To define the routing strategy for an edge: 1 On the Routing tab, select either Use Global strategies or Use local strategies. This table describes the options:
Select This Option Use Global strategies Use local strategies If You Want To Use the global routing strategy defined in the Interswitch Default Parameters dialog box. Use a specific routing strategy for this edge alone. When you select this option, you can edit the routing strategy: In the row containing the required network type, double-click the No. of Routes column, and type the number of routes that you want. As the Load Sharing is set to Normal by default, the 100% traffic will be divided equally between the routes (for example, if there are 4 routes, each will take 25% of the traffic, whereas if there were 5, each would take 20%).
In the Interface Default Routing Value pane, select the linkfault case you want to use when routing this edge - zero fault, one link fault, one node fault or worst case. The capacity/64k equivalent values for these will be based on those defined on the Edge Traffic tab of the interswitch interface edge.
Page 211
Click Apply to save your changes locally, or Commit to make them available to other users.
Adding Traffic To Requirement Edges In the Traffic module, you can add traffic directly onto individual requirement (interswitch or signalling) edges. To do this: 1 2 3 Double-click on the required requirement edge. In the dialog box that appears, click the Edge Traffic tab. If you are adding interswitch traffic, double-click the type of traffic you want to add (either Voice or Data) and then the direction (either X to Y or Y to X):
- or If you are adding signalling traffic, you can either select a service now, or not select anything and define the service in the next step. 4 5 Click the Add Traffic button. If you are adding interswitch traffic, in the dialog box that appears, select the traffic type. - or If you are adding signalling traffic, in the dialog box that appears, define the traffic you want to add by selecting the service type, service, originating node, destination node, bitrate and message. Then click OK. A line of traffic is added to the edge. If you are adding interswitch traffic, the line of traffic will be marked [U] to indicate that is user-defined rather than generated by DIRECT. 6 7 To edit the amount of traffic in Erlangs, click the current value and type the new value. Click Apply.
Viewing the Routes for Requirement and Interface Edges On the Routes tab for requirement and interface edges, you can view the following routing information for that particular edge:
Item Required No of Routes Description The required number of routes for the edge. If you have chosen to use the global routing strategies, this number is defined in the Interswitch Default Parameters dialog box. However, if you have chosen to use the local routing strategies, you can define this number yourself. The actual number of routes found or created for the edge during routing. Specifies the edge-by-edge path of the route, describing share % for the route, the layer it is using at each point, and the originating/terminating equipment used.
Actual No of Routes Route
Page 212
Deleting Messages in Signalling Message Flows

In the Service Editor of the Traffic module, you can remove signalling messages contained in a particular message flow. To do this: 1 2 In the message flow, click with the right mouse button on the message that you want to delete. From the menu that appears, click Delete Message. The selected message is removed.
Generating Signalling Traffic

After you have created signalling protocols and services, you can generate the signalling traffic based on these. The signalling traffic generation program enables you to: Set the type and length of ISAP, INAP and MAP signalling messages Calculate traffic requirements between all the signalling elements within a network based on the signalling messages and the global default parameters set To do this: 1 2 3 In the Traffic module, ensure that you have created the required signalling message flows. From the Traffic menu, point to Signalling and click Generate Traffic. In the dialog box that appears, select the signalling services that you want to create traffic for. Tip : Click the + sign to expand a service category and see the services beneath it. 4 5 6 Ensure that the signalling service parameters in the right hand pane are correct for each service. When all of the services have been selected, click Accept Selection(s). In the dialog box that appears, select the required traffic generation option: 7 8 Remove all existing signalling traffic before generating the new traffic for the selected services Leave the existing signalling traffic, and merge any that corresponds to the new traffic Leave the existing signalling traffic, and overwrite any that corresponds to the new traffic
Click Generate Traffic. The traffic is generated and placed on the network. You can view this traffic by selecting the appropriate network labels. When you have created your signalling traffic, you can test it under certain fault conditions: Link Fault
Page 213
Node Fault
Editing Signalling Service Parameters

In the Traffic module, as well as editing the global default parameters for the entire signalling network you can edit the parameters used for the individual services that you have created. You can edit parameters for the following service types: General Service related INAP ISUP-TUP Map SM and SM Failure related
Editing General Service-Related Parameters

If you are generating service-related signalling traffic, you can set the following parameters:
Item Transactions/Subscriber/BH Description The number of transactions performed per subscriber in the busy hour.
Editing INAP Service Parameters

If you are generating INAP service signalling traffic, you can set the following parameters:
Item Penetration (%) Trigger Traffic Description The required service penetration rate. Select whether this service is an originating or terminating trigger point. Select whether this service is for fixed or mobile traffic: If it is for fixed traffic, the average holding time of the ISUP services is taken as the holding time If it is for mobile traffic, the holding time is taken from the map parameters
Editing ISUP-TUP Service Parameters

If you are generating ISUP-TUP service signalling traffic, you can set the following parameters:
Item Penetration (%) Description The required service penetration rate.
Editing Map SM and SM Failure Related Service Parameters

If you are generating Map SM or SM Failure related service signalling traffic, you can set the following parameters:
Item SM MO SM MT Description The number of mobile originating signalling messages per subscriber in the busy hour. The number of mobile terminating signalling messages per subscriber in the busy hour.
Page 214
Calculating Link Fault Values

After you have generated the signalling or interswitch traffic, you can test the traffic under various conditions. For links carrying traffic, you can examine how your network would allocate the traffic when: No links are at fault 1 link is at fault To do this: From the Interswitch or Signalling (as appropriate) menu, click Calculate Link Fault Values. DIRECT will calculate the traffic loading for each link in the network, assuming that one link has failed. It will do this for each link in turn, and display the worst case scenario on the Traffic tab for the interface edge.
Calculating Node Fault Values

After you have generated the signalling or interswitch traffic, you can test the traffic under various conditions. For nodes carrying traffic, you can examine how your network would allocate the traffic when: No nodes are at fault 1 node is at fault To do this: From the Signalling menu, click Calculate Node Fault Values. DIRECT will calculate the traffic loading for each node in the network, assuming that one node has failed. It will do this for each node in turn, and display the worst case scenario on the Node Parameters tab for the node.
Overview of the Traffic Module Interswitch Layer

In the Interswitch layer of the Traffic module, you can: See all of the MSC network elements created in the RF plan and shown in the cellular layer. Provide subscriber numbers based on the actual TRX count set in the cellular module for each MSC. Add extra core elements to allow for future planning scenarios, for example, MSCs, TMSCs and LEs. Add fixed network Local Exchange elements to the network. Set traffic distribution percentages on an MSC-by-MSC basis. This means that you can set the traffic percentage to your own network, an external network and to be looked back to your own BSCs Specify external networks and POIs (Points Of Interconnect).
Page 215
Calculate the traffic between MSCs and Interactive/Voice messaging services. Set the global parameters for network elements (for example, activity factors, blocking and so on) to enable the traffic generation function to create a traffic matrix between network elements. This picture shows an example set of parameters for MSC voice traffic:
Select the speech circuits' throughputs from different codecs. When calculating the loads in the voice circuits during routing, the selected type and combination of codecs is taken into account, so that (currently) for 3g 8 different codecs - with throughputs ranging from 4.75 to 12.2 kbit/s - can be used.
Page 216
This picture shows an example set of codecs:
Creating the Interswitch Traffic Network

In the Traffic module, you can create the Interswitch network. If you are new to DIRECT, it is recommended that you follow the work order set out below when planning your first few interswitch networks. 1 2 3 Set the global interswitch traffic parameters. Create your network topology, and then set the interswitch parameters for your equipment. Add traffic to the interswitch traffic edges. - or Generate interswitch traffic. 4 5 Route the interswitch traffic. Analyse the results, change the topology if necessary, and route again in order to meet the optimum network.
Page 217
Defining Interswitch Traffic for Equipment Nodes

In the Traffic module, on the Isw Data and Isw Voice Traffic Parameters tabs of the Equipment properties dialog box, you can define the interswitch traffic for MSCs, CSMGWs, PSTN LEs and DXTs. The values are used by the Traffic Generator (Trmod.xls) to create interswitch traffic. To add a set amount of traffic: Select the Override with Estimated Values tab, and type in the estimated traffic value in Erlangs. The traffic value will be multiplied by the Traffic/Subs value (either Global or Local, depending on which one is selected) to calculate the number of subscribers. Tip : You can define the global value in the Interswitch Default Parameters dialog box. To add a calculated amount of traffic, based on the number of subscribers you have: 1 Ensure that the Traffic/Subs value (either Global or Local, depending on which one is selected) is correct. This is the multiplier for the number of subscribers, based on the amount of traffic per subscriber. Select the Override with Estimated Values dialog box, and type in the Number of Subscribers. The traffic value is automatically calculated, by multiplying the number of subscribers by the traffic/subs. 3
Item Number of Trunks (for Fixed traffic only) (Read-only) Subscribers Originating (%) Subs Orig to Own Network (%) Loop Back of Incoming (%) Mobile Subscribers (%) BHCA (for Fixed traffic only)(Read-only) Plus additionally for MSCs VMS Call Length (s) Terminated Calls rerouted to VMS Calls to VMS/Left Message IVR Call Length (s)) IVR Calls/Subscriber/Hour The average length of calls to the Voice Mail Server in seconds. The percentage value of terminating calls forwarded to the VMS. The average number of calls made to the VMS per left message. The average length of calls to Interactive Voice Response mode in seconds. The average number of calls to the IVR per subscriber in the busy hours.
You can additionally view or define the following parameters for this traffic:
Description Total number of trunks required in the node. The percentage value of subscriber originating traffic in relation to the total subscriber traffic. The percentage value of originating traffic to its own network in relation to the total subscriber originating traffic. The percentage value of traffic diverted back to the external network in relation to the total incoming traffic from other networks. The percentage value of mobile subscribers - 0 if the switch is a local exchange with fixed subscribers or 100 if the switch served only mobile subscribers. Number of calls attempted during the busiest hour of the day. This figure can be compared to switch limits.
Page 218
Viewing and Editing Requirements for Interswitch Nodes

After you have defined and used your own interswitch traffic values, you can view and edit the requirements that have been generated for a particular node. Internal switch traffic corresponds one-to-one with actual traffic, but for ToExternal, FromExternal, LoopExternal, VMR and IVR traffic, the requirement defines a total value which is distributed to one or more traffic types according to the percentages that you have defined on the Network Connections tab. To do this: 1 2 3 Double-click the required interswitch node. In the dialog box that appears, click the Isw Traffic Requirements tab. On this tab, the generated requirements are displayed: The following table describes the requirement information that is shown:
Item Type Source Destination Erlang value Description The type of traffic for the requirement. The originating node for the requirement. The terminating node for the requirement. The traffic value of the requirement, in Erlangs.
Note : Automatically generated requirements are displayed in light blue. To add a new requirement to the interswitch node: 1 2 3 Click Add Requirement. Set the traffic type, source node, destination node and Erlang value for the new requirement. Click Apply.
For information on generating traffic based on these requirements, see Generating Interswitch Traffic on page 220. To remove a requirement from the interswitch node: 1 2 Select the requirement. Click Remove requirement.
Page 219
Generating Interswitch Traffic

To generate interswitch traffic: 1 From the Traffic menu, point to Interswitch and click Generate Traffic. In the dialog box that appears, you can view the current generation settings.
If you want to use these settings, click Finish, and then click Generate. - or If you want to edit these settings, click Next.
3 4 5
Choose which traffic type you want to generate, either Voice or Cs Core Data. Click Next. Select which equipment types you want to select nodes from:
6 7
Click Next. Select which nodes with interswitch functionality you want to generate traffic for:
Click Next.
Page 220
Choose the required halving distance. You can use the Network Global Parameters, or set your own values by selecting the Override Global Defaults option and typing them in. The following table describes these parameters:
Item Halving Distance, Calling Halving Distance, Moving Description The halving distance for the calling interest of fixed and mobile subscribers in its own network. The halving distance for the moving interest of mobile subscribers in its own network.
10 Click Next. 11 Choose how you want to generate traffic. The following table describes the options:
This option Generate traffic and update existing requirements Generate traffic and add to existing requirements Generate traffic and update existing requirements that are not user defined Generates traffic this way Deletes all existing interswitch traffic (including all user-defined traffic) and then generates new traffic. Retains existing interswitch traffic and adds the new traffic that it generates. Writes the existing interswitch traffic to the Measured sheet of the results file, and then generates the traffic with this file. This means that user-defined traffic is retained, and the rest of the traffic is newly generated. Enables you to redirect existing traffic based on changes to equipment that you have made. For example, if you change the traffic allocation to a particular external network from 100% to 75%, you can regenerate the relevant traffic without having to generate all of the interswitch traffic again.
Relocate previously generated External, VMS and IVR traffic
12 Click Next. 13 Choose to view the traffic results in the default TrMod.xls a new Excel file, or one you have already created. 14 Choose whether you want to save the traffic results or not, and if so, in which file. 15 Click Finish. 16 Click Generate.
Page 221
About the Information Displayed in the Traffic Generator The following table shows the tables that are produced by the Traffic Generator, and the data that they display:
This table Input Displays this information A breakdown of the traffic in % for each node contained in the interswitch network. This is displayed numerically, and also diagrammatically in the traffic model. You can view the diagram for each node by clicking the left and right arrow buttons. Distance Call_Int The distance between nodes or gravity centres, depending on the co-ordinates set on the Isw Node tab for the equipment. The calling interest statistics for nodes, based on the distance between nodes (or gravity centres). 1 is the maximum amount of interswitch traffic, 0 indicates that there is no interswitch traffic. Move_Int The moving interest statistics for nodes, based on the distance between nodes (or gravity centres). 1 is the maximum amount of interswitch traffic, 0 indicates that there is no interswitch traffic. Originating Incoming Multipliers Modeled Interim Total Measured The values for traffic originating within this network. These are calculated by the traffic generator. The values for traffic coming into this network from external networks. These are calculated by the traffic generator. Figures inputted into the traffic generation calculation, by adding traffic to cell while taking it away from cells of the same row and column. The sum of the originating and incoming traffic values. The total value of traffic, after the multipliers have been applied. The amount of measured traffic between interswitch nodes. You type the traffic values on the Measured tab yourself, instead of using the traffic values that the results file generates. For information on how to do this, see Defining and Using Your Own Interswitch Traffic Values on page 187. NW_Total Model The sum total of the interswitch traffic and the measured traffic. A diagram of the traffic model used by the Traffic Generator.
You can edit any of the values in the Traffic Generator by clicking on the required cell and typing the new value.
Page 222
About the Traffic Model Used to Generate Interswitch Traffic This picture shows the traffic model used to generate interswitch traffic in the Traffic module.
Interswitch traffic model
The top half of the model shows: How the subscriber originating and other network incoming traffic are inputted into the switching network node, to produce subscriber terminating traffic or traffic outgoing to other networks In some cases, this can be own network internal traffic (subscriber originating/subscriber terminating) or loopback traffic (other network incoming/other network outgoing) How nodes pass traffic between themselves, regardless of where it has come from or where it is going The second half of the model shows the path of calls depending on their origin: For all calls originating from the node (whether mobile or non-mobile), the calls are distributed to the subscribers to their own network proportional to the amount of subscriber terminating traffic and multiplied by the calling interest and moving interest factors
Page 223
For all incoming mobile calls, the calls are distributed to the mobiles in their own network, proportional to the amount of subscriber terminating traffic and multiplied by the moving interest factor For all non-mobile incoming calls, the calls remain in the receiver exchange, and they are not regarded as interswitch traffic In the Input table, you can view the inputs for the traffic model on a node-by-node basis.
Creating a 3GPP Network

In DIRECT, you can create a 3GPP interswitch and signalling network. In the 3GPP network, the role of the MSC is divided between CS-MGW nodes (for interswitch traffic) and MSC Server (for signalling traffic) nodes. To create a 3GPP network: 1 2 Create the required network topology, including all of the CS-MGWs and MSCSs. For the CS-MGWs, define which MSCSs they are served by. You can define either one MSCS for a CS-MGW, or several, with different percentages of signalling traffic distributed to each. In the Signalling Services editor, define the signalling services and message flows, using the MSCS nodes. Generate signalling and interswitch traffic. The traffic values generated will be based on the number of subscribers in the CS-MGW nodes which each MSCS serves.
3 4
In 3GPP networks, you can also use IWF nodes to help transport data traffic to external networks. For information on how to do this, see Using IWFs in 3GPP Networks on page 224.
Using IWFs in 3GPP Networks

If you have created a 3GPP network, you can use an IWF node to help transport traffic to external networks. IWFs convert data traffic into a format compatible with the external network, therefore data traffic sent to and from external nodes must first be sent to the IWF for conversion. In a standard network, the IWF is situated in the Gateway node, but in DIRECT you can model it as a separate equipment node. To do this: 1 2 3 Create the IWF equipment, either as an individual piece of equipment or as subequipment to the CS-MGW node. On the CS-MGW node, add the IWF to the list of preferred nodes for point of interconnect, and assign the appropriate traffic percentage to this. Generate interswitch traffic. For each CS-MGW, DIRECT generates additional IWF traffic.
Page 224
Creating the TETRA Traffic Network

In the Traffic module, you can create TETRA access networks. TETRA planning is based on cellular network planning, and is also supported in the interswitch network. If you are new to DIRECT, it is recommended that you follow the work order set out below when planning your first few interswitch networks. 1 2 3 4 5 Set the default TETRA traffic parameters. Create your network topology, and then set the TETRA parameters for your equipment. Generate TETRA traffic. Route the TETRA traffic. Analyse the results, change the topology if necessary, and route again in order to meet the optimum network.
About the TETRA Network Architecture

A TETRA network is comprised of five types of equipment: TETRA Base Station (TBS) A TBS consists of TBC (Base Station Controller), TRUA (Transmission Unit), cabinet and cabling. TBSs are housed in an indoor cabinet for up to 4 carriers (16 channels or timeslots), and can have an extension cabinet for an extra 4 carriers. Each radio carrier consists of 4 logical channels (or timeslots). Digital Exchange for TETRA (DXT) You can use DXTs primarily as the switching element between TBSs, but other TETRA equipment can be connected to them as well. DXTs have an interfacing capacity, which determines how many other pieces of equipment can be attached to a single DXT. The following table defines the interfacing capacity scale, based on number of radio carriers:
Number of radio carriers (number of channels) 16 (64) 32 (128) 48 (192) 64 (256) Number of Dispatcher Workstations (DWSs) 16 32 48 64
Page 225
DXTs also have a subscriber capacity, which defines how many subscribers can be in the area of that exchange. If several DXTs are used, duplicates of subscriber databases will be kept on the different DXTs. For DXTs, the two subscriber databases are scaled as follows: Home Location Register (HLR) 1000, 3000, 6000, 10000 subscribers Visitor Location Register (VLR) 50% of HLR subscribers (for example, 1000 HLR subscribers may have 500 VLR subscribers) Central Digital Exchange for TETRA (DXTc) DXTs can also be used as a central exchange or DXTc. DXTcs have different capacity limits to regular DXTs:
Number of radio carriers (number of channels) 32 (128) Number of Dispatcher Workstations (DWSs) 32
The subscriber database supports 1000, 3000 or 6000 subscribers. DXTcs also support up to 32 inter-exchange signalling links, which have up to 960 inter-exchange traffic channels. Dispatcher System Controller (DSC) Contains 1 to 6 Dispatcher Workstations (DWS) with Dispatcher Interface Audio Adaptors (DIAAs) and related voice communications equipment. DSCs are used to manage and communicate within the TETRA network. Network Management System (NMS) This picture shows the relationship between the equipment types.
Using Protocol Stacks

Protocol stacks are a set of connected interfaces or functions that provide the necessary shaping information and overhead to route traffic from one layer to another. Protocol stacks are comprised of: Entry points - The starting point of the traffic as it enters the protocol stack. At the entry point, you can define the route of the traffic and the type of traffic that will use this entry point. Connections - Provide a link between layers of the protocol stack. Service Access Point (SAP) - A logical grouping which replicates the function of port, enabling you to join layers together with connections. Layers - Contain operation sets, which are the groupings of primitives (or functions) that are applied to the traffic passing through the protocol stack. In DIRECT, you can build your own protocol stacks, by defining some or all of these components, or use the default ones created for you.
To use protocol stacks, you will also need to: Create header types Correctly configure the user stack on the traffic service This picture shows a model of a protocol stack, and how it may look in DIRECT:
Protocol stacks in DIRECT
Creating a Protocol Stack

In DIRECT, you can create your own protocol stacks, which provide the necessary shaping information and overhead to route traffic from one layer to another. To create a protocol stack: 1 Ensure you have: 2 3 Created header types with the correct length Specified on the traffic service which header name it will use
From the Traffic menu, point to Protocol Stacks and click Protocol Stacks. In Protocol Stacks dialog box, click Add. - or -
Page 227
Select Protocol Stacks, click with the right mouse button and from the menu that appears, click Add Protocol Stack. A new empty protocol stack is created. 4 5 6 7 To rename the stack, select it, and in the Name box, type the required name. On entry point(s), set the destinations. Define your protocol stack layers. Click Close. You can now assign your stack to particular traffic interface edges, and/or assign stacks by default to traffic interface edge types.
Setting Destinations on Protocol Stack Entry Points

After you have created a protocol stack, you must set the destinations for its entry point. The entry point is the starting point of the traffic as it enters the protocol stack. At the entry point, you must specify the route of the traffic and the type of traffic that will use this entry point. To do this: 1 2 3 4 5 In the Protocol Stacks dialog box, select the protocol stack for which you want to define the entry point. Click the Protocol Stacks tab. Select the Entry Point and click Details. In the Entry Point Details dialog box, click Add. A new traffic entry appears in the dialog box. From the drop down lists, choose:
Item Traffic Service Traffic Type Description The traffic service using this entry point. The traffic type that this service uses.
Note : You cannot define the target SAP or the target layer until you have created a target layer and an SAP. 6 Click OK. You can now add a layer.
Defining Layers for Protocol Stacks

After you have created an empty protocol stack and an entry point for the stack, you can define layers to include in the stack. Layers contain operation sets, which are the groupings of primitives (or functions) that are applied to the traffic passing through the protocol stack. You can either define new layers, or copy any existing ones that you have created.
Page 228
To define a new layer: 1 In the Protocol Stacks dialog box, click Add Layer. A new layer is added. Tip : To rename a layer, SAP or operation set, double click it and type the new name. 2 Select the layer, and click Details. In the dialog box that appears, you can define the components of the protocol layers (SAPs and Operation Sets), and set how the traffic services are mapped onto them. 3 4 5 6 7 Beneath the Service Access Points pane, click Add. A new SAP is created. Beneath the Operation Sets pane, click Add. A new operation set is added. To define the properties of the operation set, click Details. For more information, see Defining Operation Sets for Protocol Stack Layers on page 230. When you have created the required SAPs and Operation Sets, in the Operation Set Distribution pane, click Add. You can specify the following, in order to set which traffic uses which SAP and operation set on this layer:
Item SAP Traffic Service Traffic Type Operation Set Description The SAP for the layer. The traffic service that will use the layer. The traffic type that will use the layer. The operation set that will be used on this layer.
Tip : You can choose to use an SAP and Operation Set on all traffic services and types by selecting the ALL options. 8 1 2 3 Click OK. Click Insert Layer. Select the protocol stack, and then the layer within that stack. Click OK. The selected layer is added to the stack that you are creating. To copy an existing layer:
Page 229
Defining Operation Sets for Protocol Stack Layers After you have created a layer for a protocol stack, you can define operation sets for that layer. An operation set is a grouping of primitives (or functions) that are applied to the traffic passing through the protocol stack. To define an operation set: 1 2 3 In the Operation Sets pane of the Protocol Layer Details dialog box, select the required operation set and click Details. On the Primitives tab, click Add. In the dialog box that appears, select the required primitive type for the function and click Add. For information on the different primitive types, see About the Primitive Types for Protocol Stack Operation Sets on page 230. 4 To define the properties of the function, beneath the right hand pane, click Add. You can now edit the function by selecting options from the drop down boxes that appear. For more information on these, see Setting the Primitive Parameters in Operation Sets on page 233. 5 6 7 8 Add more functions to the primitive type as required. Add more primitive types and functions for these as required. Click the Destination tab, and set the traffic service(s) and type(s) that will use this operation set, as well as the target SAP and layer. When you are satisfied with the primitive types and functions that you have created, click OK. Tip : You can change the order in which the primitive types will be processed by using the Move Up and Move Down buttons. You can now define which traffic uses which SAP and operation set on a layer. About the Primitive Types for Protocol Stack Operation Sets When you are defining the operation sets for a protocol stack, you can use a number of primitive (or function) types. This section describes these types. For information on the parameters you can set for each primitive, see Setting the Primitive Parameters in Operation Sets on page 233. Fragmentation (IP Traffic only) The Fragmentation primitive models the effect of limitation on the maximum packet size allowed at the lower layer. When an IP packet is fragmented in two individual packets, each packet is given the full IP header of the original packet.
Page 230
This picture shows the fragmentation process:
Protocol Layer Fragmentation Process
Buffering The Buffering primitive models the buffers in the protocol layer, where the G/G/1 queuing model is used. You should use this primitive whenever a traffic flow is buffered separately. This picture shows the buffering process:
Protocol Layer Buffering Process
Encapsulation The Encapsulation primitive adds a header to the incoming packet. You can define the name of this header in the Primitive Parameters. Padding The Padding primitive pads any incoming undersized packets up to a pre-defined packet size. Segmentation The Segmentation primitive models the buffer that is added when compression, segmentation, padding and encapsulation are performed.
Page 231
This picture shows the segmentation process:
Protocol Layer Segmentation Process
Header Compression The Header Compression primitive removes, compresses and then re-adds the header of incoming packets. This picture shows the Header Compression process:
Protocol Layer Header Compression
During Header Compression, DIRECT: 1 2 3 Locates the name of the header defined in the Primitive Parameters. Uses this to find the parameters for the traffic service, which will be the one that matches the header label defined in the General Traffic Model. Matches these parameters with the defined header types, in order to work out the default values. These values are then used to compress the header.
Page 232
Setting the Primitive Parameters in Operation Sets When you are creating operation sets on page 230 for layers in protocol stacks, you can set specific parameters related to the primitive type that you are using. This section describes the parameters for each primitive type. Fragmentation
Item SAP Traffic Service Traffic Type Distribution Function Type Description The SAP using this primitive. The traffic service this primitive will be used on. The traffic type this primitive will be used on. The distribution model that will be used: Discrete - values change based on a fixed number Deterministic - value change by a rate based on a fixed number Exponential - The rate of increase which becomes greater and greater as time progresses Geometrical - an ordered set of numbers, where each number in turn is multiplied by a fixed amount to produce the next. Log Normal - values change according to the log curve Encapsulation Value Max PDU Size The length of the header (bits). The maximum PDU size. For each fragment, the header and payload must not exceed the Max PDH size.
Buffering
Item SAP Traffic Service Traffic Type Mean Service Time (s) Scv Service Time TTI (ms) Processor Capacity (bps) Queuing Model Description The SAP using this primitive. The traffic service this primitive will be used on. The traffic type this primitive will be used on. The mean time taken to service a packet (in seconds). The squared coefficient of the Mean Service Time. The interval between the transmission of packets (ms). The capacity of the processing equipment (bits per second). The queuing model used to queue the packets.
Encapsulation
Item SAP Traffic Service Traffic Type Distribution Function Type Description The SAP using this primitive. The traffic service this primitive will be used on. The traffic type this primitive will be used on. The distribution model that will be used: Discrete - values change based on a fixed number Deterministic - value change by a rate based on a fixed number Exponential - The rate of increase which becomes greater and greater as time progresses Geometrical - an ordered set of numbers, where each number in turn is multiplied by a fixed amount to produce the next. Log Normal - values change according to the log curve
Page 233
Item Encapsulation Value
Description For the Deterministic distribution function, this is the header length in bits. For the Discrete distribution function, you must set two comma-separated values the first is the header length, and the second is the probability of that header length.
Pad to Byte
Select this option if you want to round up any bit values to the nearest byte (for example, 20 bits equal 2.5 bytes, which would be rounded up to 3 bytes or 24 bits). This will improve processing speed.
Padding
Item SAP Traffic Service Traffic Type Padding Header Name Description The SAP using this primitive. The traffic service this primitive will be used on. The traffic type this primitive will be used on. The size of the outgoing packet (bits). The name of the header whose packets will be padded.
Segmentation
Item SAP Traffic Service Traffic Type TTI (ms) Segmentation Length Segments Per TTI Description The SAP using this primitive. The traffic service this primitive will be used on. The traffic type this primitive will be used on. The interval between the transmission of packets (microseconds). The length of each segment to be created. The number of segments to be transmitted between intervals.
Header Compression
Item SAP Traffic Service Traffic Type Distribution Function Type Description The SAP using this primitive. The traffic service this primitive will be used on. The traffic type this primitive will be used on. The distribution model that will be used: Discrete - values change based on a fixed number Deterministic - value change by a rate based on a fixed number Exponential - The rate of increase which becomes greater and greater as time progresses Geometrical - an ordered set of numbers, where each number in turn is multiplied by a fixed amount to produce the next. Log Normal - values change according to the log curve Header Name New Length The name of the header that you want to compress. The length that you want the compressed header to be.
Page 234
Creating Header Types

To be able to use protocol stacks, you need to create header types that determine the header size. To create a header type: 1 2 3 4 From the Traffic menu, point to Protocol Stacks and click User Stack Header Types. In the dialog box that appears, click Add. A new header type is added to the list. To rename the header type, double click the name and type the required name. Double click the distribution type row, and select the required distribution type:
Distribution Type Discrete Deterministic Exponential Deterministic Log Normal Description Values change based on a fixed number, set in the Distribution Value column. Values change by a rate based on a fixed number, set in the Distribution Value column. The rate of increase which becomes greater and greater as time progresses. An ordered set of numbers, where each number in turn is multiplied by a fixed amount to produce the next. Values change according to the log curve.
5 6
Double click the Distribution Value row, and type the number that will be used by the distribution type. Click OK. Your new header type can now be used in protocol stacks.
Assigning Protocol Stacks to Traffic Interfaces

After you have created protocol stacks, you can assign them to the following traffic interfaces - RAN Uplink, RAN Downlink and Transport. To do this: 1 2 3 From the Traffic menu, click Traffic Interface Defaults. In the dialog box that appears, you can choose a default protocol stack to use with the different interface edge types. Click Apply, and then click Close.
Page 235
Testing Protocol Stacks

After you have created a protocol stack, you can test it with some dummy traffic. This enables you to ensure that your stack performs correctly before you use it across your entire network. To do this: 1 2 3 4 From the Traffic menu, point to Protocol Stacks and click Protocol Stack Tester. In the dialog box that appears, select the required protocol stack and the traffic type that you want to test. Click Run Stack. The dummy traffic of the selected type is passed through the selected protocol stack, and the results are displayed in the Results pane. This table describes the information you can view:
Item History Description Each entry represents a function run on the traffic, based on the operation sets contained in the protocol layer. 0 represents the original state of the traffic, before it has passed into the protocol stack. Header Changes Each entry indicates a change to the header, based on the primitive operating on it: <> indicates header compression has been performed A new header name indicates encapsulation has been performed For other primitives, an abbreviated form of the name is displayed - for example, seg will indicate that segmentation has been performed The final entry represents the final string of all header changes Packet Length Interarrival Time No. Packets in Call Packet Interarrival Time No. Segments Processor Primitives Arrival Rate Arrival Scv Mean Delay Scv Delay Queue Usage On Time Off Time TTI Queuing Model The average number of octets that make up a packet within the traffic stream. The length of time between the transmission of packets. The average number of packets that make up a call. The length of time between two packets during the on period. If a segmentation primitive has been used, this indicates the number of segments that have been created. Indicates the primitive operating on the traffic. The rate at which packets are received, in bits/second. The squared coefficient of the arrival rate. The average delay. The square coefficient of the delay. The % of time during which the buffer size grows over the specified length. The number of milliseconds during which packets of traffic are transmitted. The number of milliseconds during which no packets of traffic are transmitted. The interval between transmission of packets (ms). The queuing model used for the traffic.
Page 236
Planning a GPRS Network Using DIRECT

You can use the Traffic module to plan a GPRS network, either in conjunction with the ASSET tool or standalone. This diagram shows a simple planning scenario using both tools:
GPRS Planning using ASSET and DIRECT
For more information on using ASSET, see the ASSET User Reference Guide.
Page 237
During synchronisation, the traffic data in ASSET3G is transferred into DIRECT onto the cell layer of the BTS. This traffic is the Average Busy Hour traffic, that is the maximum traffic throughput requirement that the cell could handle due to the blocking effects of the Air Interface. In DIRECT, you must manually configure the TRX layout to match that of your ASSET3G TRXs, setting the number of dedicated and default channels required for the TRX to serve the required traffic throughput. For information on how to do this, see Adding (E)GPRS Traffic to BTSs on page 178.
Planning a Prepay Network Using DIRECT

In DIRECT, you can model the redistribution of interswitch voice traffic for subscribers using prepaid mobile phones. Calls made by prepaid subscribers are redirected to a Prepaid Platform (PP) equipment, where the subscriber's account details are checked. If everything is in order, the call is forwarded to a designated Transit MSC equipment, which may be part of a normal MSC or located in a transit MSC. Finally, the call is forwarded to its destination. This picture shows a simple network with normal interswitch traffic of 100 Erl between 2 MSCs:
Simple interswitch network
This picture shows the same network supporting 20% prepaid customers, using the type of configuration described above:
Interswitch network supporting prepaid traffic
Page 238
If you want to model this in your DIRECT network, you must: 1 2 3 4 5 Create an equipment node that supports the ISW PP (prepaid) equipment type. On the Network Connections tab for the node, designate one or more Transit MSCs as available for traffic from this node. On the Isw Voice Traffic Parameters tab for each MSC, specify the percentage of traffic that originates from prepaid subscribers. On the Network Connections tab for each MSC, select its preferred Prepay Platform. Generate new interswitch traffic. When this traffic is generated, the prepaid traffic will be created automatically as a percentage of the normal internal and ToExtenal traffic.
Page 239
Page 240
CHAPTER 7
Routing The Network in DIRECT

Routing is the process by which you can connect together the different network layers from the various DIRECT modules, and so create the complete hierarchy of your transmission network. To route a network, DIRECT has to find a route in a lower layer for each edge, defining a means for traffic to pass from one node to another. Routing is an iterative process, and can be performed at many different times and in many different ways, depending on the unique characteristics of your planning project. Routing in DIRECT gives you the ability to target the routing to specific layers, starting from the traffic layer.
Routing targeted to user-defined layers
Page 241
In addition, you can: Perform manual routing. Increase routing customisation by choosing no balancing, balanced capacity or balanced fill ratio routing. Based on the chosen option, the routing algorithm will then try to spread the traffic evenly across the network and therefore find routes that optimise the load or fill ratio of the segments. Choose to use shortest path first routing. The SPF algorithm unambiguously finds the shortest path between two endpoints in the network. Choose to use diversity routing. In this routing mode, the logical routes of the traffic requirements must always be diverse or protected at the conduit level. Conduit diverse routing should be able to change the routes in such a way that all the logical routes become conduit diverse. Make routes either protected or unprotected. If you leave the edge as unprotected, the routing algorithm finds just a single route, whereas if you choose to designate the edge as protected, the routing algorithm tries to find a second diverse route. This protects the first one, by minimising the number of commonly used segments. Different kinds of protection are taken into consideration, for example path protection is handled differently to MS-SPRing protection. Display the routes for a selected edge on demand.
In This Section
About the DIRECT Routing Model About Network Routing Setting the Routing Parameters Using Automatic Routing in DIRECT Using Manual Routing in DIRECT Creating Routing Tables Defining Routes for Individual Traffic Viewing Routes Viewing the Routing Summary Routing Protection Loops Removing Under-Utilised Edges Automatically 243 244 253 255 259 261 263 265 267 268 268
Page 242
About the DIRECT Routing Model

The transmission network as modelled in DIRECT can be thought of in terms of layers, with each layer receiving services from the layer below and in turn providing services to the layer above. You can decide on your own order of layers, depending on the requirements of your own network. In the layer model, the flow of services is from layer-to-adjacent layer only; intermediate layers are not bypassed if the modules have been used in the model.
Layer diagram of the DIRECT functional modules
The relationship between the layers is as follows:

This layer: Traffic 2Mb (PDH) VC-4 (SDH) Transmission Is used to: Define the logical connections (also done in the Cellular module). These are carried by the next granularity layer models. Carry low order granularity connections. VC-12 paths are created from 2Mb paths, as they have the same granularity. Carry the VC-12s and VC-3s. Carry the virtual containers (VC-4s) which form the SDH high-order paths. Each VC-4 must have a transmission route. Protected VC-4s have both a primary and secondary transmission route. Carry the transmission segments that are defined in the Transmission layer. A conduit can carry a number of transmission segments, or none at all. A conduit may have several transmission segments or none at all. Every transmission segment must be assigned a conduit route, and every transmission node must be located at a Property.
Conduit
In summary, a typical order of routing could be, from lowest layer to highest: Logical traffic (from the Traffic module) Logical 2Mb paths (from the PDH module) Logical VC-4 paths (from the SDH module) Physical STM paths (from the SDH module)
Coaxial cables (from the Transmission module) Conduit pipes (from the Transmission module) Note : The optical segments are in the same hierarchical level as the transmission segments, and the lightpath segments are between the VC-4 and transmission layer. This means that when the VC-4 paths are routed, both the lightpath and transmission layers are included, and so the routes can be partly in both layers.
About Network Routing

There are a number of different types of routing that you can perform in DIRECT, depending on your planning requirements.
About Shortest Path First Routing

One of the simplest types of routing is shortest path first, which is based on the Dijkstra shortest path first (SPF) algorithm. This method defines the length of a path as the sum of all of the edge weights along it, and then finds the shortest (in other words, lowest total weight) path between two endpoints. For example, this picture shows two possible paths from node A to node D, with differing lengths (the shortest path is marked in red).
Shortest Path First routing
As a planner, you can define which will be the shortest path by adding additional weights to certain edges, to make that route less attractive to the SPF algorithm. For example, in this picture an additional weight of 4 has been added to path A-D, meaning that the shortest path is now A-B-C-D.
Weighting routes in SPF routing
Page 244
Note : The additional routing weight can be of any value, providing it exceeds the sum of the default routing weights of all of the edges.
About Double Path Routing

You can protect routes in DIRECT by creating disjoint secondary routes, that is, routes that do not share any edges in common. In this way, if one edge fails, it will only affect one route and the other can be used. In the context of the SPF algorithm, you can create a disjoint secondary route by adding a specific routing weight to a particular edge in the primary route, which is called the common link penalty. By placing this common link penalty on an edge, you ensure that it is less attractive to the SPF algorithm and therefore unlikely to be used in any secondary route. In this example planning scenario, by placing a large routing weight on the primary route A-D (marked in red), another now shorter route (A-B-C-D, marked in green) is chosen:
Using a common link penalty
However, if you are searching for more than one two disjoint routes (known as double path routing), you have to apply the common link penalty to each new route once you have found it using the SPF algorithm. This means that routing is iterative process.
Page 245
Example of Double Path Routing

Consider this example network.
Unprotected double path routing
The SPF algorithm has found the primary route between nodes A and H to be A-B-GH (marked in red). The second time routing is performed, two possible secondary routes are found, A-C-E-G-H (marked in green) and A-B-D-F-H (marked in turquoise). However, both of these routes share an edge with the primary route, A-B and G-H respectively, so protection is not possible.
Page 246
Two disjoint routes are possible, however: A-C-E-G-H and A-B-D-F-H. Therefore, some common link penalties are required, to make A-C-E-G-H a more attractive primary route to the SPF algorithm than A-B-G-H and A-B-D-F-H, and furthermore, A-B-D-F-H a more attractive secondary route than A-B-G-H. This can be done by adding the common link penalties, as shown in this diagram.
Applying common link penalties to find disjoint routes
The routing weights for each route are now as follows:

Route A-B-G-H A-C-E-G-H A-B-D-F-H Routing Weight 2003 4 1004
Page 247
About Balanced Capacity Routing

While basic SPF and double path routing use generally arbitrary routing weights to achieve the required effects, you can also set specific routing weights to reflect the traffic needs of your network. In this way you can include basic capacity considerations in your planning. Consider the following network:
Non-balanced capacity routing
The network has two traffic loads (of 10kbits each) that must be routed over the network from A to B. Using the SPF algorithm means that both will traffic loads will use the same (shortest and alphabetically first) route, A-C-B. This means that the two edges A-C and C-B are heavily loaded, while A-D and D-B are empty, which is an inefficient use of resources.
Page 248
However, if the actual traffic loads are reflected in the routing weights you can force the traffic to use both routes. After the routing of the first load, you should place an additional weighting equal to the traffic load (10) on each used in the route. Then as you try to route the second load, the SPF algorithm finds that the primary route (A-CD) is now greatly weighted (to a value of 22), and so routes the second traffic load across the lesser weighted (a value of 2) route A-D-B. This picture shows the updated network.
Balanced capacity routing
Tip : When routing multiple loads, route the traffic loads in size order starting with the highest, to ensure the most even balance of traffic possible.
About Balanced Fill Ratio Routing

Balanced fill ratio routing is very similar to balanced capacity routing, but whereas balanced capacity routing is based on load weights, balanced fill ratio routing is based on load/capacity ratios. For example, you may have two traffic requirements, one of 5kbits and one of 10 kbits. In balanced capacity routing these figures (5 and 10) would be the weights added to the edges, and so the edge carrying the 10kbits would have a greater routing weight. However, in balanced fill ratio routing, the 5kbits traffic could be routed across an edge with a capacity of 5kbits (1:1 fill ratio) and the 10kbits traffic across an edge with a capacity of 30kbits (1:3 fill ratio) and in this case, the 5kbits edge would have a greater route weighting.
Page 249
The routing weight for balanced fill ratio is calculated as follows:
About Nominal and Detailed Capacity Routing

Nominal routing is performed during the nominal planning stage, when only rough estimates for capacity requirements are sufficient. During nominal planning it is acceptable for traffic to be routed over segments which have insufficient capacity for this. Conversely, detailed capacity routing is performed during the detailed planning stage, when the planner is attempting to allocate traffic into traffic containers based on their exact structure and constraints. The purpose of this stage of planning is to produce a viable network solution, which can be approved and later implemented. Therefore, the routing weights have to be manipulated in order that the traffic loads for each segment do not exceed that edge's stated traffic capacity.
Page 250
About Conduit Diverse Routing

While you can protect routes by providing a secondary disjoint route on one layer, it is sometimes difficult to ensure disjoint routes across a number of layers. Often primary and secondary routes at a higher level will share the same physical conduits at a lower level. This picture shows an example.
Primary and secondary routes sharing conduits
The traffic load across A-B is protected on the Transmission layer through routes A-CB (marked in red) and A-D-B (marked in green). However, at the physical conduit level, both of these routes share the same conduit (A-C-B, marked in red and green) and so the protection is no longer effective.
Page 251
However, through manipulating the routing weights you can overcome this problem, and ensure that conduit diverse routing is achieved. In this example, the transmission layer should be re-routed, but with a common link penalty and a non-diverse conduit penalty on the secondary route A-D-B. This will make A-E-B the more attractive route to the SPF algorithm, and this will therefore become the secondary route (marked in green). This picture shows the altered network.
Conduit diverse routes
Page 252
Setting the Routing Parameters

Routing in DIRECT is based on the routing parameters. The routing parameters determine which layers are routed onto which, and which routing weights are used on each layer. The parameters that are set affect the way that the routing algorithms route the traffic through the edges in your network. To open the Routing Parameters dialog box: From the Routing menu, click Routing Parameters. The Routing Parameters dialog box appears.
Setting the Routing Target Module Layers

In the Routing Parameters dialog box, you can set the target module layers for each module prior to routing. To do this: 1 2 3 4 In the left-hand pane, select the name of the module that you want to route onto the target layer. On the target Layers tab in the right hand pane, select the checkbox for each target module. Click on the + sign to expand the list of target layers, and select the checkboxes for the required target layers. Click Apply.
Page 253
Setting the Target Layer Routing Weights

You can set the routing weights for the edges and edge groups on a per module layer or per edge group basis. To do this per module layer: 1 2 3 From the Routing menu, click Routing Parameters. In the left-hand pane, click the network layer for which you want to edit the routing properties. You can edit the following routing properties for each network layer, for all of the edges or all of the edge groups:
Item Weight Common link penalty Non-diverse conduit penalty Load balancing penalty Fill-ratio balancing penalty Create new edge penalty Description The weight added to the edge in order to modify its routing qualities for the SPF routing algorithm. The weight added to an edge that is shared between the primary and secondary route during Double Path routing. The weight added to an edge that shares the same conduit in the primary and secondary route. The weight added to an edge in order that a traffic load may be evenly balanced across a number of edges. The weight added to an edge in order that a traffic load may be evenly balanced across the capacities of a number of edges. The weight added to an edge when a primary route it is loaded with traffic over its capacity, and either an alternative path has to be found or a new edge has to be created. This penalty may be used, for example, in detailed capacity routing.
4 1 2 3 4
When you have finished editing, click Apply. In the module window, double-click the edge group. Click the Routing tab. Edit the routing properties as shown in the table above. Click Apply.
To do this per edge or edge group:
Page 254
Using Automatic Routing in DIRECT

A number of routing options are available during automatic routing, enabling you to route the network in accordance to your requirements. All of the automatic routing commands use the routing properties for the particular edge(s), and these will affect the routing results. Automatic routing is performed in the Main Routing dialog box.
Main Routing dialog box
To open this: From the Routing menu, click Route. In the Main Routing dialog box, you can follow this basic automatic routing procedure: 1 2 3 4 Ensure you have set the Routing parameters correctly. If you wish to route a selected number of edges only, select these edges. Open the Main Routing dialog box. From the Routing Stack list, select the modules that you wish to route. Tip : You can rearrange the order in which the modules are routed onto each other, by editing the order of the routing stack. To do this, select the module you want to move, and use the Move Up and Move Down buttons to reposition it.
If you want include or exclude specific layers within the modules, expand the module and select or clear the checkboxes as required:
On the Routing Options tab, for each module, you can either use the default Global settings for routing, which are defined at the Global settings level, or define your own by selecting the Override Global Settings checkbox, and choosing the following options:
Item Which edges in the enabled layers would you like routed? Description You can select to route all edges on all selected layers, or only selected edges. Note : To use the selected edges option, you must have selected the edges in the required module windows. Existing Routes For existing routes, you can choose to: Leave edges with existing routes as they are Delete any existing routes that have not been frozen Delete all existing routes Target Layers Considered You can choose to route by either: Considering all routes over all layers and selecting the best one. This may take a considerable amount of time over large networks, and should only be used over a small number of edges. - or Searching for routes on a layer by layer, incremental basis. This is quicker, but may not always find the optimal route. Freeze successful routes You can choose to automatically freeze any successful routes found during routing.
You can also define this on a layer-by-layer basis, on the Routing Options tab for the selected layer. 7 On the Targets tab, select the target modules for this module. This indicates which module the selected module will be routed onto. You can also define this on a layer-by-layer basis, by selecting the target layer on the Targets tab for a selected layer.
Page 256
On the Receive Settings tab, select how you want traffic routed onto the selected module to be treated. This table describes the options:
Item Override Global Settings Planning mode Description Select this checkbox if you want to edit the routing settings yourself. Otherwise, those set at the Global Settings level will be used. You can select nominal or detailed capacity planning mode. For nominal planning, the edge groups are routed, and if the traffic demand exceeds the available capacity, additional edge groups are added to ensure the routing is successful. For detailed capacity planning, the edge groups are routed, and if the traffic demand exceeds the available capacity, the routing will fail. Traffic balancing Diverse conduit penalty You can select to use one of the traffic balancing types, balanced capacity or balanced fill ratio, or choose to use no balancing at all. You can select to use the diverse conduit penalty, which will be the one set in the global routing parameters.
Select whether to perform Top Down or Bottom Up routing, by selecting the appropriate option from the bottom of the Routing Stack pane. The routing algorithm will try to route the entire network according to the settings and parameters that you have defined. A routing summary appears in the Message Log, summarising the routing results in terms of how many edges were routed successfully and how many failed.
10 Click the Route button.
Defining Global Routing Settings

In DIRECT, in the Main Routing dialog box, you can define global settings for modules and layers, which can be used as the defaults during automatic routing. To do this: From the Routing menu, click Route. 1 2 In the Main Routing dialog box, in the left hand pane, select Global Settings. On the Routing Options tab, for each module, choose from the following options:
Item Which edges in the enabled layers would you like routed? Description You can select to route all edges on all selected layers, or only selected edges. Note : To use the selected edges option, you must have selected the edges in the required module windows. Existing Routes For existing routes, you can choose to: Leave edges with existing routes as they are Delete any existing routes that have not been frozen Delete all existing routes
Page 257
Item Target Layers Considered
Description You can choose to route by either: Considering all routes over all layers and selecting the best one. This may take a considerable amount of time over large networks, and should only be used over a small number of edges. - or Searching for routes on a layer by layer, incremental basis. This is quicker, but may not always find the optimal route.
Freeze successful routes
You can choose to automatically freeze any successful routes found during routing.
Click the Receive Settings tab, and choose from the following options to define how you want traffic routed onto the module(s) to be treated:
Item Override Global Settings Planning mode Description Select this checkbox if you want to edit the routing settings yourself. Otherwise, those set at the Global Settings level will be used. You can select nominal or detailed capacity planning mode: For nominal planning, the edge groups are routed, and if the traffic demand exceeds the available capacity, additional edge groups are added to ensure the routing is successful. For detailed capacity planning, the edge groups are routed, and if the traffic demand exceeds the available capacity, the routing will fail. Traffic balancing Diverse conduit penalty You can select to use one of the traffic balancing types, balanced capacity or balanced fill ratio, or choose to use no balancing at all. You can select to use the diverse conduit penalty, which will be the one set in the global routing parameters.
If you have overridden the Global Settings in any individual modules, you can reset them all to match the Global Settings again by clicking the Clear All Overrides button. Click Close to save your settings.
Editing Route Properties for Individual Edges

Automatic routing is based upon the route properties, and so you can set these in order to make the routing perform as you want it to. To edit the route properties of a particular edge: 1 2 Double-click on the edge. On the Route Properties tab, you can set the properties that determine how this edge will be routed onto lower layers. This table explains the properties that you can set:
Item Protect route Description When routing is performed, the routing algorithm tries to find both a primary and secondary route to route the traffic, and allocate two separate connection groups for each. When re-routing is performed, the routing algorithm will not route any traffic for the selected connection group. The connection group can only be used to route traffic of a particular class.
Freeze route Use class separation
Page 258
Item Force same route Overridden RAN Uplink / RAN Downlink / Transport Protocol Stack
Description When re-routing is performed, any traffic passing through this connection group will be forced to follow the same route as previously. Depending on the edge type, default protocol stack(s) will be assigned to this edge. To choose a different one, select it from the drop-down list.
Overridden target layer
Traffic will be routed on the selected layer, bypassing the routing settings already defined on the Routing tab. For example, if you specify to route the Traffic module over the PDH module, and the PDH module over the Transmission module, then you can use this option to create exceptions for specific links and routes.
You can only freeze the route on interswitch interface edges. 3 When you have finished editing, click Apply.
Using Manual Routing in DIRECT

After you have used automatic routing, you can manually edit the routing results to fit your specific requirements. You can replace any route that has been generated with one of your own. To do this: 1 2 Ensure you have set the Routing/Route properties correctly. If you are routing the interswitch traffic layer, ensure you have configured the routing strategies correctly on the interswitch requirement edges and the interswitch nodes. If you are routing the ATM and/or IP traffic layers, ensure that you have configured the required delay budgets. Select all of the edges in the network that you wish to consider for the new route. From the Routing menu, click Manual Routing.
3 4 5
Page 259
The Manual Routing dialog box appears.
To define the source edge, click on the required edge in the Selected edges pane, and then click the Select source edge button. The name of the source edge appears in the Source edge pane. Tip : To change the source edge, click the Unselect source edge button and choose another.
7 8 9
To add another edge to the route, click it in the selected edges pane, and then click Add to route. Add edges in this way, until you have reached the destination node. Click Route. The new route will be added to the routing scheme.
Page 260
Creating Routing Tables

You can create tables for interswitch and signalling routing, which enable you to: Define your route hop by hop Specify alternative hops in the case of failure To create a routing table: 1 2 Double-click the source node. Click the Isw Node or Sig Node Parameters tab, as appropriate. The Routing table pane lists all of the possible destination nodes for this source node. 3 4 Select the destination node. Click the Add Option button. - or Click with the right mouse button, and from the menu that appears, click Add Route Option. Note : To remove a route option, select the option and click Remove Option, or right-click the option and click Remove Route Option. 5 6 Double-click in the Hop column for the route option, and select the node you want to hop to. If you are creating an interswitch routing table, you can add more than one hop to a route option, in the case of failure. To add another hop: Select the route option. Click the Add Hop button, or right-click and from the menu that appears, click Add Hop.
Note : To remove a hop, select the hop and click Remove Hop, or to remove all hops, right-click the required route option and click Clear Hops. 7 If you have more than one hop for a routing option, to adjust the percentage share of traffic double-click the Share Percent value and type the required value. This will affect the percentage share of traffic to the other hops as well. 8 9 Click Apply, and then Close. Repeat steps 1-8 for each node in the route.
To see a step-by-step example of creating a routing table, see Example of Creating Routing Tables on page 262.
Page 261
Example of Creating Routing Tables

This topic describes the creation of a routing table, based on this basic network:
To define a route from MSC1 to MSC6, using a routing table: 1 2 3 4 5 6 1 2 3 4 5 6 Double-click MSC1, and on the Isw Node Parameters tab, click with the right mouse button on MSC6. From the menu that appears, click Add Route Option, and in the Hop column select MSC4. Click Apply, and then Close. Double-click MSC4, and on the Isw Node Parameters tab, click with the right mouse button on MSC6. From the menu that appears, click Add Route Option, and in the Hop column select MSC6. Click Apply, and then Close. Double-click MSC1, and on the Isw Node Parameters tab, click with the right mouse button on MSC6. From the menu that appears, click Add Route Option, and in the Hop column select MSC2. Click Apply, and then Close. Double-click MSC2, and on the Isw Node Parameters tab, click with the right mouse button on MSC6. From the menu that appears, click Add Route Option, and in the Hop column select MSC3. Click Apply, and then Close.
You could also define an alternative route:
Page 262
7 8 9
Double-click MSC2, and on the Isw Node Parameters tab, click with the right mouse button on MSC6. From the menu that appears, click Add Route Option, and in the Hop column select MSC6. Click Apply, and then Close.
Defining Routes for Individual Traffic

In DIRECT, you can use the Assisted Routing wizard to define the route for an individual section of traffic across the Transport network (for example, ATM, PDH, SDH) right down to the physical layer. This enables you to route the traffic more quickly, and gives you more control over the routing process. To do this: 1 2 3 Ensure you have created your required network topology. Select the edge group(s) that you want to route. From the Routing menu, click Routing Wizard. - or On the Routing toolbar, click Wiz. - or Click with the right mouse button, and from the menu that appears, click Assisted Routing. 4 Select the edges from the group that you want to route. Tip : You can select or deselect all of the edges by clicking Select All and Select None respectively. The status pane describes the current routing status of the edge, which will be one of these:
This status Not needed for sub-edges Same route forced Means that The route of the sub-edges does not depend on the route of the edge group. Because the edge group has the Force Same Route option selected in its Route Properties, this edge will use the same route as the main edge group. You do not need to route this edge, for example, if it is forecasted traffic on an Abis edge group. Because the edge had the Force Same Route option selected in its Route Properties, it has used the same route as the main edge group. You do not need to route it individually.
Same route forced, not necessary Already has route
Click Next. Warning : Clicking Next at any stage will Apply any choices that you make, and clicking Cancel does not undo any previously applied changes - it only closes the Assisted Routing wizard.
Page 263
Select the required routing method. The methods are described in the following table:
If you want to Let DIRECT search for the most likely routes for your edge, based on the supporting topology that you have defined Define the route for your traffic in detail, step by step Tip : Choose this option if you want to save time, rather than letting DIRECT find all possible routes Stop routing any further down, if for example, you only want to Don't route any further route down to the SDH layer and not route down to the physical layer at this point Choose this routing method List possible likely routes Define the route manually
Click Next. Depending on the routing method you have chosen, the following table describes what to do next:
If you chose this routing method List possible likely routes Do this next 1. In the left-hand pane, select the route that you want to use. Tip : You can check the route hop-by-hop in the selected route details pane, or see the whole route highlighted in the module window. 2. If no suitable route is displayed, click Define another, and create a new route following the instructions under for defining the route manually. 3. Click Next. Define the route manually 1. In the left-hand pane, select the next element in the route and click Add this element to route. Add more elements to the route in the same way. 2. When you have defined the entire route click Accept. 3. In the left-hand pane, select the route that you want to use. 4. Click Next. Don't route any further 1. Click Next, and then click Finish. 2. No more routing will be planned.
Repeat steps 6 and 7 for each edge group or layer that you want to route the traffic over. Include any unrouted edges which are part of the route for an edge that you have routed using the Assisted Routing wizard. You can continue doing this as far down as the physical layer if required. Click Finish.
Page 264
Viewing Routes
After you have routed your network, you can view the routes in both the module window and the edge group dialog box. To do this: 1 2 In the module window, click on the two endpoints, while holding down the shift key. To view the primary route, from the Routing menu, click Show Single Route. By default, the primary route is displayed in red, but you can change this in the Plan Preferences dialog box.
Page 265
To view the secondary route, from the Routing menu, click Show Double Route. By default, the secondary route is displayed in dark blue, but you can change this in the Plan Preferences dialog box.
To view specific edge details, double click one of the highlighted edges. In the edge group dialog box that appears, the actual edge on which the source edge is routed onto will be highlighted as well. On the Traffic and Frame Layout tabs for this edge, you can view how the source edge is routed onto it.
- or 1 2 Click on the edge for which you want to display routes. From the Routing menu, click Highlight Route. The primary and secondary (if applicable) routes are highlighted. You can change the colour used to highlight routes.
Page 266
This picture shows an example of highlighted routes, in this case for edge A-D:
Edge A-D : unhighlighted (left) and highlighted routes (right)
Viewing the Routing Summary

After you have routing your network, you can view the routes that have been created in a summary report. To open this: 1 2 From the Routing menu, click Routing Summary. The Routing Summary dialog box appears.
To view the data for a specific module, click the name in the left-hand pane. You can then view the information for both routed and unrouted edges on the two tabs. The following table shows the data that is displayed for each route:
Item Edge Route Type Layer From Node To Node Description The name of the edge group. Expand this to display the separate routes and connections. The type of route. The network layer on which the edges are routed. The source node for the route. The destination node for the route.
Page 267
Routing Protection Loops

After you have created a PDH protection loop in the PDH module, you can route the loop to ensure that the traffic that is routed over the edges is protected. To do this: 1 2 In the Traffic module, from the Routing menu, click Routing Parameters. In the left hand tree list, select the Traffic module, and then in the right hand pane select the PDH1 Module checkbox to designate the PDH1 layer as the TARGET layer for the Traffic module. Click Apply. In the left hand tree list, select the PDH1 module, and then in the right hand pane select the Transmission Module checkbox to designate the transmission layer as the TARGET layer for the PDH module. Click Apply, and then Close. From the Routing menu, click Route. In the dialog box that appears, click Route.
3 4
5 6 7
Removing Under-Utilised Edges Automatically

When you have routed the network, some of your edges may be under-utilised, that is, do not have any circuits routed over them. In DIRECT, you can search for these edges automatically and remove any unwanted ones - you may wish to keep those on which you have selected the fixed capacity option. To locate and/or remove under-utilised edges: 1 If you want to locate the under-utilised edges within a group of specific edges, select the required edges. Important : You cannot select Traffic module edges. 2 3 4 From the Routing menu, click Edge Removal. In the dialog box that appears, click Next. Select which edge category you want to analyse for under-utilised edges. The following table describes the options:
Category All edges Selected edge(s) Select layers(s) Description Will analyse all edges in your network (except for those in the Traffic module). Will only analyse those edges that you have selected prior to clicking Edge Removal. Will only analyse edges on the layers that you select in the dialog box that appears.
Click Next.
Page 268
A summary of all under-utilised edges appears. This picture shows an example:
Select the edges that you want to delete. Warning : The summary will include edges that have the fixed capacity option selected, so you should be careful when you select the edges to delete.
Click Delete. The selected edges will be removed, and sent to the Wastebasket. A summary of the deleted edges is displayed. Tip : To view the summary as an Excel report, click the Report button.
Click Finish.
Page 269
Page 270
CHAPTER 8
Creating the SDH Network

You can use DIRECT's SDH module to route traffic onto SDH paths (VC-4, VC-4-4c, VC-3) and subsequently route those paths onto the physical STM-n network. To protect the SDH paths in the physical STM-n network, you can use path or MS-SPring (Multiplex Section Shared Protection ring) protection. By using protection, you either allocate pre-assigned spare capacity in the rings (MS-SPring) or duplicate traffic when a traffic tributary enters the ring (Path Protection). You can also set up and monitor the link connectivity and node interfaces, and assign KLM values to traffic tributaries. The SDH module also enables you to display the mapping of virtual channels, showing all of the traffic tributaries served on the SDH layer. You can also see the virtual containers that get multiplexed into administrative units and STM-n frames, either in a tree structure or a frame layout diagram. The frame layout diagram can be edited, to re-assign positions. As a further part of SDH planning, you can assign KLM and J values to traffic tributaries. The J-KLM number of the add/drop and through tributaries indicates the traffic's position within the STM container and the VC-4 frame, and therefore identifies the payload unit. You can view nodes in the SDH module, displaying cross-connection details and information related to traffic originating or terminating in the node.
In This Section
Overview of the SDH/SONET Module About Planning the SDH VC-4 Network About the SDH and SONET Multiplexing Structures About J-KLM Numbering in DIRECT Using Protection in the SDH Module 272 274 276 277 277
Page 271
Overview of the SDH/SONET Module

In the SDH/SONET module, you can: Perform automatic detailed SDH planning. Display the Virtual Channel (VC) mapping, including the multiplexing of administrative units into an STM-N frame and the mapping of tributaries into VCn. This picture shows an example:
Page 272
View detailed cross connection information, and see how traffic tributaries are added, dropped and passed through the node. This picture shows an example:
Page 273
View the position of traffic tributaries based on KLM and J values, as well as the traffic utilization of each SDH segment:
Produce the traffic circuit utilisation for all edges as a Microsoft Excel report. Support the path and MS-SPRing protection mechanisms Create a database of protection rings, in which you can store information on the spared and used capacity of a protection ring and an STM-N in general The module supports both SDH and SONET.
About Planning the SDH VC-4 Network

Prior to planning a SDH VC-4 path network, you can typically face such planning problems as: What is the cumulative logical connection matrix in the network? Should the network cross connection concept be flat and fully distributed, strictly layered, logically layered or centralised?
Page 274
This diagram illustrates the main steps involved in SDH VC-4 network modelling.
Main steps in SDH VC-4 network modelling
If you are new to DIRECT, it is recommended that you follow the work order set out below when planning your first few transmission networks: 1 2 3 4 5 In the Traffic module, create your GSM network. Ensure that you configure the traffic requirements of the network, and the logical connections between the network elements. In the PDH module, create your PDH network, and route the cellular traffic over it. This will assemble the GSM traffic 2M tributaries. In the SDH module, create the SDH network, including all of the protection that you want to include. Route the traffic across the protected SDH network.
Page 275
About the SDH and SONET Multiplexing Structures

In the SDH network, lower order signals are mapped and multiplexed into the STM (Synchronous Transport Module) signals according to an ETSI standard in the ITU-T Recommendations. This picture shows the SDH multiplexing structure:
SDH Multiplexing Structure
This picture shows the SONET multiplexing structure:
SONET multiplexing structure
Page 276
About J-KLM Numbering in DIRECT

In DIRECT, to identify tributaries and aggregate tributaries in the STM-n frame, the JKLM numbering scheme is used. This is in accordance with ITU-T(G.707). The following table explains the scheme:
This number 1st (if used) 1st (or 2nd if J value is used) 2nd (or 3rd if J value is used) 3rd (or 4th if J value is used) Represents this value J K L M Which gives this The AUG that the STM-n belongs to. The TUG-3 that the tributary belongs to. The TUG-2 that the tributary belongs to. The TU-12 that the tributary belongs to.
For example, a KLM of 200 indicates that the tributary belongs to TUG-3 number 2, without any lower layer multiplexing, whereas a KLM of 261 indicates that the tributary belongs to TUG-3 number 2, TUG-2 number L, TU-12 number 1. In this way, the KLM scheme also signifies the level of multiplexing, so that you can distinguish between, for example, a single TUG-3 containing a TU-3 and a TUG-3 containing 7 TU-3s, or a VC-3 signal (34/45 Mbit/s) and a VC-12 signal (2 Mbit/s).
Using Protection in the SDH Module

In the SDH module, you can use a number of different protection types to increase the availability of your network, and make it less prone to failure. There are three types of SDH protection: Path protection MS-SPring protection SNC protection
About Path Protection

A path protection loop can be any number of continuously connected edges, from 1 upwards. Double the required capacity needs to be installed in the loop so that one half is used for working traffic, while the other half is for protection.
Page 277
If the protection loop is just 1 edge, then you can use basic protected routing.
Single edge SDH protection
The shortest path from A to D on the transmission layer is A to D, so this is the primary route (marked in red). The secondary route is therefore A-B-C-D (marked in green).
Page 278
However, if the protection loop is made up of more than 1 edge, multiple edge protection is required. Each edge can only be routed along its primary route, and this must be disjoint from the routes of the other loop edges.
Multiple edge SDH protection
In this example, the following edge routes are used:

SDG Path Route A-B B-C A-C Transmission Route A-B B-C A-D-C Colour Red Green Turquoise
For the path route A-C, a directly corresponding transmission route is not possible, so the routing algorithm can theoretically opt for either A-B-C or A-D-C. However, A-BC includes other edges in the protection loop, and so if this option were chosen the protection would no longer be effective. Therefore A-D-C as a disjoint route is the correct option.
Page 279
Creating SDH Path Protection Loops

In the SDH module of DIRECT, you can create a path protection loop. To do this: 1 2 3 1 2 3 Ensure that the nodes that you want to use in the loop are connected. Select the nodes for the loop. From the PDH menu, click Create Protection Loop. In the Traffic module, double-click one of the protected edges. Click the Route Properties tab, and select the Protect Route checkbox. Click Apply. This route is now protected, and so DIRECT will allocate a primary and secondary route to the corresponding traffic.
The protection loop is now created, but to protect the traffic flowing into it:
About MS-SPring Protection

Whereas path protection is normally used on low capacity links, MS-SPring is better for high capacity links, as there is no need to provide double the required capacity. Nodes that require protection are grouped together in a closed loop. They are connected together using two or more separate fibres, each carrying signals in opposite directions. With two separate paths connecting each pair of nodes, all traffic is protected against any single failure, and some multiple failures as well. In MS-SPring protection loops, the total payload per section in the multiplex is divided equally into working and protection capacity. When there is a failure in the ring (caused by either a node or edge), any of the multiplex sections can access the ring protection capacity. For MS-SPrings, working channels carry the normal traffic that needs to be protected, while protection channels are kept empty in reserve to carry protected traffic in the case of network failure. The traffic (working and protected) is transmitting bidirectionally over spans: incoming and outgoing tributaries travel over the same spans, in opposite directions. This means that during network planning, you only need to route the traffic onto the working path, and any secondary route should use the same route within the loop as the primary path. You can do this by routing for the first time, then removing any common link penalties on the MS-SPring loop edges, and then re-routing for the secondary route. Based on the SPF algorithm, the same route as the primary route will be calculated as the secondary route.
Page 280
This picture shows an example network:
Using MS-Spring Loop Protection
In this example, the traffic is routed from A to B. It firstly passes from A to C, where it is not MS-SPring protected, and therefore is spread across the primary (marked in red) and secondary (marked in green) routes, which are A-D-C and A-F-C respectively. It then passes from C to B, where it is MS-SPring protected, and only route C-E-B is used (marked red and green, since it is both the primary and secondary route).
Creating SDH MS-SPring Protection Loops

In the SDH module, you can create an MS-SPring protection loop. To do this: 1 2 3 Ensure that the nodes that you want to include in the loop are connected with VC4 connection groups. Ensure that each VC-4 connection group contains 4 VC-4 edges. From the SDH menu, click Create MS-SPring loop. An MS-SPring loop is created, and DIRECT allocates half of the capacity of the loop for protection. For example, if the loop is an STM-4 loop, then 2 VC-4s will be reserved for protection. To do this, DIRECT automatically assigns them the maximum possible routing weight, which becomes read-only.
Page 281
About SNC Protection

SNCP is Sub-Network Connection Protection. It is used at the interconnection between SDH rings, so that single or even multiple failures will not prevent traffic passed between networks.
Using Protection Topologies in the SDH Module

This picture shows an example 3g network, seen at the SDH level.
Example 3g network (SDH layer)
All of the traffic has been routed onto the ATM layer, and then the ATM cells are carried on top of the SDH layer. When part of a SDH topology, SDH protection loops can be one of three types: access, local and backbone. The following table describes the function of each loop:
Item Access loop Local loop Backbone loop Description Connect Node Bs to RNCs. May use STM-1 or STM-4 path protection. Requires a fibre network in the ground. Use either path protection if the capacity is STM-16 or less, or if the capacity is STM16 or more, use MS-SPring protection. Used to connect together the trunk side of MSCs and SGSNs to other MSCs and SGSNs, GGSNs, ISPs and PTOs. Typically used on high capacity links, such as STM-16 or STM-64. MS-SPring protection is normally used in backbone loops.
Page 282
Viewing SDH Protection Loops

Both SDH path protection and MS-SPring protection loops are stored in the same database, and you can view them in the Loops dialog box. To view an SDH loop: 1 2 3 From the SDH module, click Show Loops. In the left-hand tree pane, click the SDH/SONET Module. Expand the list of loops, and click the loop that you want to view. The Loops dialog box has two tabs, General and Loop.
Viewing and Editing the General Properties of SDH Protection Loops

On the General tab of the Loops dialog box, you can view and edit the general properties of an SDH protection loop. This table shows the properties that you can view/edit:
Item Name (ID) Comments Change History Description The ID code for the protection loop. Any additional planning comments. Details of when the protection loop was created and last edited.
Viewing the Edges of SDH Protection Loops

On the Loop tab of the Loops dialog box, you can view a list of the edges that comprise the SDH protection loops.
Example SDH protection loop
Page 283
Page 284
CHAPTER 9
Creating the PDH Network

You can use the PDH module to plan your PDH (Plesiosynchronous Digital Hierarchy) network, modelling both ETSI and ANSI standard networks. This involves: 1 2 Planning the primary rate path structure for 1.5 or 2 Mb links Managing the timeslot allocation of the 1.5 or 2 Mb frames
Planning the Primary Rate Path Structure The primary rate path references the first level in the PDH hierarchy, as either a 1.5 Mb (ANSI) or 2 Mb (ETSI) frame. In the PDH module view window, you can view the connections at the primary rate level. Each connection in the PDH module represents the data flowing in one consistent frame from the source node to the destination node. In this way, a frame could pass through a number of nodes, but the traffic positions within the frame must remain the same, and the frame should not be cross-connected with a lower granularity than the primary rate. You can also identify protection loops and define them in the PDH module view.
In This Section
Overview of the PDH Module Managing Timeslot Allocation Planning the PDH Network 286 288 289
Page 285
Overview of the PDH Module

In the PDH module, you can: Provide primary rate path planning. You can see the cross connections on the primary rate level, down to 8k level where required. View all traffic originating and terminating in a node. This picture shows an example:
Create user-defined timeslot allocation templates. View the positioning of traffic within the frame, and conduct timeslot allocation planning.
Page 286
This picture shows an example frame:
Use an automated process that allocates traffic into the appropriate positions according to a predefined timeslot allocation template:
Display traffic circuit utilisation for all of the edges in an Microsoft Excel report.
Page 287
Allocate a specific channel for signalling in the 1.5M/2M frame, or reserve timeslots for signalling traffic based on the maximum payload. This picture shows an example:
Create PDH multiplexing hierarchies. Plan within both the ETSI and ANSI standards. Identify protection loops and then define them within your DIRECT plan. Produce a generic reusable model for PDH path planning, which supports any PDH multiplexing level and can be used outside GSM planning. Route PDH logical connections over the specified target layer. Define PDH radio links (nx2M connections).
Managing Timeslot Allocation

Timeslot allocation is the positioning of the traffic within the frame. In the PDH module, you can view the timeslot allocation for a primary rate frame and make changes to it. You can also use DIRECT to automatically allocate traffic into the correct timeslots of the frame, based on a predefined template. As an alternative to this, you can define your frames as unstructured, which means DIRECT will treat the frame as a single whole, without any division into timeslots. You can use this when you wish to fill the frame with high-level traffic with a constant bitrate.
Page 288
This section covers the following topics: Creating a PDH network Creating PDH path protection loops Defining timeslot allocation templates Assigning timeslot allocation templates Viewing timeslot allocations
Planning the PDH Network

In the PDH module of DIRECT, you can create the PDH network topology. If you are new to network planning, it is recommended that you follow these steps: 1 Set the display filters to show the correct network layers. This table shows the options available:
Click this button To enable this network layer PDH Multiplexing Level 0 (64k) PDH Multiplexing Level 1 (1.5M, 2M) PDH Multiplexing Level 2 (6M, 8M) PDH Multiplexing Level 3 (32M, 34M, 45M) PDH Multiplexing Level 4 (98M, 140M, 274M) PDH Multiplexing Level 5 (397M, 565M) PDH Physical Level (E0 - E5, T0-T4, J1-J5, x E1, x T1, x T3)
2 3 4 5
Ensure you have created the required equipment in the Equipment Editor, along with the accompanying PDH cards. Add this equipment to the PDH module view as required. Set the PDH module parameters, to specify what channels will be reserved on 1.5M and 2M frames. Connect the equipment using the required PDH module edge types. Note : If you choose one of the multiple edge groups (for example x E1), then you are prompted to choose which ports (if any) you want to use.
Define the number of edges within the edge group. To do this, in the PDH module view, double-click the edge group. In the dialog box that appears, on the Edges tab, click the Add Edge button, until you have created the required number of edges. Click Apply to save the edges. Tip : You can also do this using the Automatic Topology Generator, located on the ATG tab of the Task Pane.
Page 289
Click on the Traffic Structure tab, and select whether the edges in the edge group will have a structured or unstructured frame structure. This table explains the options:
Item Unstructured Structured Description The edge has no frame structure, and therefore the traffic is not allocated specific timeslots. This makes routing more simple, but less precise. The edge has a detailed edge structure, whereby the traffic is allocated specific timeslots. This makes routing more complex, but more precise.
Edit the other link properties as required.
Setting the PDH Default Parameters

DIRECT creates the PDH element of your network according to certain defined parameters. These may have certain default values, but during planning you may need to set your own values in the PDH Module Default Parameters dialog box. The PDH module default parameters are related to channel reservation. When reserving specific channels or a percentage of channel capacity, consider the following points: When routing onto 2M/1.5M structured edges, traffic will only be routed onto unreserved edges When routing onto 2M/1.5M unstructured edges, DIRECT will only fill up an edge with traffic to the maximum payload value When DIRECT calculates circuit and channel utilisation, reserved channels will be classed as utilised When DIRECT calculates traffic utilisation, reserved channels will be included in the calculation, which is Routed Traffic/(Edge Capacity - Reserved Channels) There are also further routing considerations related specifically to 2M frames. For more information, see Routing Using the Entire 2M Frame on page 292.
Page 290
To set the PDH module default parameters: 1 In the PDH module, from the PDH menu, click Default Parameters. The PDH Module Default Parameters dialog box appears:
To specify how capacity will be reserved on any 2M or 1.5M structured frames, on the appropriate tab, in the Structured pane, select the channels that you want to reserve. Note : On the 2M Channel Reservation tab, Channel 0 is selected by default, with a reserved percentage of 3.125% and a maximum payload of 1984Kbps.
To specify how capacity will be reserved on any unstructured frames, on the appropriate tab, in the Unstructured pane, type either the percentage that you want to reserve or the maximum payload in Kbps. The other value is calculated automatically. Click Apply.
Page 291
Routing Using the Entire 2M Frame

When reserving channels on 2M frames, you should bear in mind that in some circumstances routing requires the whole of a 2M frame to be available, and not just the unreserved channels. For example, the granularity for interswitch or signalling interfaces is set to 2M, GSM cellular edges are approximated to 2M, or a VPT is targeted to 2M. Therefore, in certain conditions, the reserved channels that you have specified may have an impact on routing: If you are routing an ATM VPT set to 2M onto a 2M circuit, you must have 2 reserved channels or less on the 2M circuit If you are routing a GSM Interface approximated to 2M onto a 2M circuit, the total number of reserved channels plus the 64K channels per link value on the interface has to be 32 or less If you are routing an Interswitch or Signalling Interface with a granularity of 2M onto a 2M circuit, the total number of reserved channels plus the 64K channels per link value on the interface has to be 32 or less In all cases, the traffic utilisation on the 2M circuit must be the same as the Load per Edge on the GSM/Interswitch/Signalling interface or the VPT edge that is routed onto it
Page 292
About PDH Protection Loops

A PDH protection loop operates on the PDH primary rate path level (2M). A loop can be any number of continuously connected edges, from 1 upwards. If the PDH protection loop is just 1 edge, then you can use basic protected routing.
Single Edge PDH Protection
The shortest path from A to D on the transmission layer is A to D, so this is the primary route (marked in red). The secondary route is therefore A-B-C-D (marked in green).
Page 293
However, if the PDH protection loop is made up of more than 1 edge, multiple edge protection is required. Each edge can only be routed along its primary route, and this must be disjoint from the routes of the other loop edges.
Multiple PDH Edge Protection
In this example, the following edge routes are used:

PDH 2M Path Route A-B B-C A-C Transmission Route A-B B-C A-D-C Colour Red Green Turquoise
For the PDH 2M path route A-C, a directly corresponding transmission route is not possible, so the routing algorithm can theoretically opt for either A-B-C or A-D-C. However, A-B-C includes other edges in the protection loop, and so if this option were chosen the protection would no longer be effective. Therefore A-D-C as a disjoint route is the correct option.
Page 294
Creating PDH Protection Loops

In the PDH module, you can create protection loops, which can be used in routing later on. To create a PDH path protection loops: 1 2 In the PDH module view, select the edges that will form the loop. From the PDH menu, click Create Protection Loop. The selected edges are designated as a loop. You can now route this loop in the Traffic module. To remove a PDH path protection loop: 1 In the PDH module view, select one of the edges contained in the loop. Tip : To view a table of all of the protection loops in your network, from the PDH menu, click Show loops. 2 From the PDH menu, click Remove Protection Loop.
About Timeslot Allocation in the PDH Module

As a transmission planner, an important consideration when you are planning your PDH network is the number of 2 Mbit/s connections you need to link your network elements. The main factors determining this are traffic amount, grooming, your network topology and the spare capacity for future traffic demands. The PDH module can be used to plan any generic primary rate PDH networks, and is not limited to just mobile network applications. However, a typical transmission scenario is the timeslot capacity and 2 Mbit/s planning of the A-bis interface in a GSM network.
Dimensioning the A-bis Interface

The A-bis interface is between the BSC and the BTS(s). Traffic can be generated by a BTS or a BSC and then passed across in both directions. The amount of traffic that can be generated by, for example, a BTS, depends on the equipment configuration (the number of cells and TRXs it supports). Based on the FDMA/TDMA concept in GSM networks, one TRX can support up to 8 simultaneous connections or up to 8 traffic channels (TCHs). This table describes the traffic demands for TRXs and BTSs:
Network Element TRX Traffic Demand 2x64 kbit/s timeslots for Air Interface traffic 0.25x64 kbit/s connections for TRXSIG BTS 0.25x64 kbit/s connections for BCFSIG
Note : Capacity is generally referred to in 64 kbit/s blocks, as it is the basic building block of primary rate 2 Mbit/s connections.
Page 295
The objective of dimensioning the A-bis interface is to determine how the traffic generated by each TRX and BTS in the GSM network (the Cellular layer of the Traffic module) is passed onto the 32-timeslot primary rate frame in the PDH network (PDH module). In this picture, every multi-frame timeslot (from TS0 to TS31) corresponds to a data rate of 64 kbit/s (based on sampling at a rate of 8Hz at a resolution of 8 bits per sample).
GSM timeslot to standard 2M TDM traffic mapping
Planning A-bis Timeslot Allocation

You should plan A-bis timeslot allocation during the detailed planning phase, prior to any installation and commissioning. The timeslot allocation planning is based on timeslot allocation tables, which define 8 kbit/s level cross connections. A cross connection node is used between the BSC and BTS.
Using cross connection nodes for the A-bis interface
You can use cross connection nodes to 'groom' the incoming BTS primary rate data streams into a single primary rate data stream. If this is not done, and 2 Mbit/s is the lowest transmission capacity used between the BTS and BSC, then only a few timeslots will be used on each separate link for most of time, and so will not be used efficiently. The internal structure of a 2Mbit/s link for the A-bis interface is defined in a timeslot allocation table. A timeslot allocation table maps the air interface traffic and the signalling timeslots onto the timeslots of the primary rate multi-frame.
How the timeslots are allocated affects: Future upgrades of transmission capacities Minimising potential changes to cross connection tables Future upgrades from full rate (16 kbit/s) to half rate (8 kbit/s) signalling
About the Timeslot Allocation Table

This picture shows an example timeslot allocation table:
Example timeslot allocation table
In the timeslot allocation table: Rows represent the timeslots of the primary rate 2Mbit/s frame. Columns represent the 8 kbit/s cross connections at the cross connection (grooming) node. Each TCH occupies 16 kbit/s (2x8 kbit/s) of the 64 kbit/s primary rate timeslot. Each TRX requires up to 8 TCHs, corresponding to the 8 timeslots of the GSM frame. If the primary rate frame is fully utilised it can support up to 2 BTSs, each consisting of 6 TRXs plus the TRXSIG and BCFSIG traffic requirements. However, normally BTSs incorporate less than 6 TRXs in order to leave spare capacity for more BTSs or future capacity expansion.
Page 297
Selecting a Timeslot Allocation Strategy

The configuration of a timeslot allocation table is dependent on: Traffic requirements The way that the timeslots are grouped (outlined during the detailed planning phase) There are two basic timeslot allocation strategies, described in the following table:
Timeslot Allocation Strategy Linear Block model Description Advantages Disadvantages
The next free timeslot is used whenever required The 2 MBit/s capacity is divided into standard blocks.
Simple
Difficult to maintain after changes to the allocation table
Convenient way to upgrade the Spare capacity is fragmented, timeslot allocation table making it difficult to add another BTS to the allocation table
Selecting a Timeslot Grouping Strategy The configuration of a timeslot allocation table is dependent on the way that the timeslots are grouped, and this is an important consideration during the detailed planning phase. There are three standard timeslot grouping strategies, described in the following table:
Item Grouping by TRX Grouping by Usage Grouping by BTS Description Both the traffic and the signalling timeslots for each TRX are kept together. Traffic and signalling timeslots are allocated separately. Both the traffic and the signalling timeslots for each BTS are kept together.
Defining Timeslot Allocation Templates

The PDH module uses timeslot allocation templates to position traffic within the 1.5M or 2M frame. You can create your own templates, meaning that rather than having to define the timeslot allocation for each connection separately you can use the same allocation pattern across as many frames as you wish. Important : Because DIRECT routes the traffic in a flexible way, templates do not have to exactly match the node configuration, providing that the template has sufficient space for the traffic from that node. For example, you can assign a 2+2+2 template to an edge to carry the traffic of a 1+1+1 BTS. To define your own timeslot allocation template: 1 2 3 4 From the PDH menu, click Timeslot Allocation Templates. On the Timeslot Allocation Templates tab, click Add Timeslot Allocation Template. Click Apply to save. The new template appears in the left-hand tree view. In the left-hand tree pane, select the new template.
Page 298
You can now define the template on two tabs: General tab Timeslot Allocation Template tab
Defining the Basic Properties of Timeslot Allocation Templates

On the General tab of the Timeslot Allocation Template dialog box, you can define the basic properties of the template. To do this: 1 2 3 4 5 Type a name for the template. You could include the number of nodes and their configuration, for example, TS Template 3 BTSs 1+1. Select the number of nodes that the template will support by clicking the up and down buttons. Select the frame type - 1.5 Mb, 2 Mb, or unspecified. Add any further description and planning notes. Click Apply.
After you have defined the general properties of the template, you can allocate the traffic to the timeslots within the frame.
Allocating the Timeslots on Timeslot Allocation Templates

On the Timeslot Allocation Template tab of the Timeslot Allocation Templates dialog box, you can allocate the traffic to the timeslots within the frame.
Timeslot Allocation Template tab
Page 299
A 2M frame is represented by an 8 x 32 grid (8 columns for the cross connections at the grooming point, 32 timeslots in the primary rate 2 Mbit/s frame), while a 1.5M frame is represented by an 8 x 24 grid. To allocate traffic to the template frame: 1 2 Select the node containing the traffic from the node list. To allocate a type of traffic to a slot (or slots), select the traffic type in the list of available traffic types and then drag it to the required slot position on the grid. Release the mouse button to place the traffic type in the slot(s). You can move traffic types within the grid, by clicking and dragging to another position. Similarly, you can remove traffic types from the grid by clicking and dragging back onto the list of available traffic types. To add more than one traffic type, click each traffic type while holding down the Shift or Ctrl key, and then (still holding down the Shift or Ctrl key) drag the group onto the grid. Important : It is recommended that you first designate certain slots/channels as reserved, using the Reserved traffic types. You can then add regular traffic types to the rest of the frame. If you do not reserve any slots/channels, traffic can be routed into any part of the frame and there will will no space available for necessary signalling. 3 4 If you are adding a TRX, in the dialog box that appears select the number of separate channels that you want to add and then click OK. Continue to add and move traffic types around the different slots, until you have filled the entire template as required. Tip : You can empty the grid at any time by clicking Clear Grid. 5 Click Apply to save the template.
Page 300
This picture shows an example template, 2BTS 1+1, which supports traffic generated by 2 BTSs each incorporating 2 TRXs:
Example timeslot allocation template
Viewing Traffic Allocation In A Timeslot Allocation Template

In a timeslot allocation template, you can view the traffic allocated to each timeslot. To do this, hover the cursor over the traffic you wish to view:
Viewing traffic allocation
For the selected traffic, DIRECT will display the source node, the source TRX and which channel it is mapped onto. For example, in the picture above, the traffic generated by TRX2 on Node 2 is carried over Channel 3 of the 2Mbit/s primary rate frame.
Page 301
Viewing and Editing PDH Edges

You can view and edit PDH links in the PDH EdgeGroups dialog box. To do this: 1 In the PDH module view, double-click the edge group that contains the PDH link. The PDH Edge Group dialog box appears.This picture shows an example.
Expand the edge group tree to show all of the edges contained in the group, and then select the edge. You can view and edit the edge properties on a number of tabs: General Reserved Capacity (unstructured edges only) Traffic Frame Layout (structured edges only) Timeslot Allocation Template (structured edges only) Routes Route Properties Routing Properties
Page 302
Viewing and Editing the Reserved Capacity for Unstructured Edges

On the Reserved Capacity tab for a PDH edge, you can view and edit the reserved capacity and maximum payload for the unstructured frame on that edge.
Setting the reserved capacity for an unstructured frame on a PDH edge
By default, an edge will be given the reserved capacity and maximum payload specified in the PDH Module Default Parameters. However, you can set your own values here - whichever value you specify, the other is calculated automatically.
Viewing the Traffic for a PDH Edge

On the Traffic tab for a PDH edge, you can view the traffic carried by the edge. This picture shows an example:
Page 303
The following details are shown:

Item Traffic Position Bitrate (Kbps) Traffic Utilisation (%) Circuit Utilisation (%) Channel Utilisation (Used/Total, %) Description The name of the traffic. The (timeslot) position of the traffic in the frame. The speed of the traffic in kbits per second. The percentage of this traffic using the edge (100 if routed, 0 if not). The percentage of the used traffic channels against the maximum available traffic channels. The number of traffic channels that are used divided by the total number of traffic channels.
Viewing and Editing the Frame Layout of a PDH Edge

On the Frame Layout tab for a PDH edge, you can view and edit the organisation of the structured frame on that edge. The frame is divided into 8 columns, representing the 8 kbit/s cross connections at the grooming point or cross connection point, and 32 rows, representing the timeslots of the primary rate 2Mbit/s frame. If you have assigned a timeslot allocation template to the edge, the traffic allocation will appear in this dialog box, with any reserved channels marked in grey. If you have not assigned a timeslot allocation template to the edge, the reserved channels will be those specified in the PDH Module Default Parameters:
To reserve and unreserve channels: 1 2 Select the required channel. Note : You can only reserve unoccupied channels. Click the Reserve button to reserve a channel, or the Unreserve button to unreserve a channel that is currently reserved. Warning : If you subsequently apply a timeslot allocation template to this edge, any changes to the reserved/unreserved channels are overwritten.
Page 304
Assigning Timeslot Allocation Templates

On the Timeslot Allocation Template tab for a PDH edge, you can choose to assign a particular timeslot allocation template to the node. Note : You can only do this for structured PDH edges. After you have created a timeslot allocation template, you can assign it to one or more edges in the PDH module. This means that any traffic routed onto this primary rate edge will be allocated timeslots according to the template assigned. Important : Because DIRECT routes the traffic in a flexible way, the template does not have to match the node configuration exactly, providing that the template has sufficient space for the traffic. For example, you can assign a 2+2+2 template to an edge to carry the traffic of a 1+1+1 BTS. To assign a template: 1 2 3 In the PDH module view window, double-click the connection group to which you want to assign the template. In the dialog box that appears, select the individual PDH edge to which you want to assign the template. Click the Timeslot Allocation Template tab.
4 5
From the box at the top of the pane, select the template that you want to use on the edge. You must then define the actual network elements that will correspond to the notional nodes in the template. To do this, select a node from the list, select the network element from the list below it, and then click the Assign Node button.
Page 305
Viewing the Routes of PDH Edges

On the Routes tab for a PDH edge, you can view the routes for a particular edge. The following details are shown:
Item Required No of Routes (Req) Actual No of Routes (Act) Edge/Route Req/Act Route Share Layer From/To Description The required number of routes that need to use the edge. The actual number of routes that use the edge. The edge that is being routed and the route it is part of. Indicates if the route is required or actual. Indicates how the route is shared. The layer onto which the edge is routed. The originating and destination nodes for the route.
Page 306
CHAPTER 10
Creating the ATM Network

In the ATM module, you can model the ATM network used in UMTS (Release 99), generic ATM networks and IP over ATM networks. ATM networks can be designed using PDH or SDH as the underlying transport technology, by creating networks in those respective modules. This picture shows an example ATM network view.
Example ATM network
To open a new ATM module: In the Views Browser, click the Create Planning Module button and from the menu that appears, click ATM module.
In This Section
About Planning The ATM Network Displaying Paths in the ATM Module Setting the ATM Default Parameters Calculating QoS and Capacity Over ATM Networks About ATM Service Categories Creating VCI Numbering Templates Viewing and Editing VCC Group Properties Viewing and Editing VPC Group Properties Viewing and Editing VPT Group Properties Viewing and Editing AAL Group Properties 308 308 310 312 324 324 326 330 331 333
Page 307
About Planning The ATM Network

If you are new to DIRECT, it is recommended that you follow the work order set out below when planning your first few ATM networks: 1 2 If it is not open already, open the Traffic module. If you have created a UMTS network in the ASSET3G tool, synchronise DIRECT with ASSET3G/CONNECT. Otherwise, create your UMTS network on the Cellular layer in the Traffic module. Ensure that your core ATM network nodes are connected with bi-directional traffic edges. 3 4 Open a new ATM module. Manually create the required number of AAL edges to connect nodes together. AAL edges are used to transport traffic onto the ATM layer, where it can then be routed onto your VCCs, VPCs and VPTs. Manually create the required number of VCCs to connect nodes together. Manually create the VPCs. Create VPTs between RNCs and Node Bs. Route all of the edges. If required, add SDH or PDH segments between the RNCs and 3G-BTSs.
5 6 7 8 9
10 Route any segments that you have created in the transmission module, and then route the logical connections. The ATM physical connections are now routed inside the transmission segments. 11 In the ATM module, calculate the QoS and capacities over the ATM network.
Displaying Paths in the ATM Module

In the ATM module, you can view each path type separately. To do this: 1 On the ATM module toolbar, ensure that the required path type is enabled. Enabled path types are greyed out, as shown here filled as shown here 2 . . Disabled path types are
On the ATM module toolbar, click the corresponding view button for the type of path you want to view.
Page 308
This picture shows three separate ATM link displays:
Step 1: Create VCCs
Step 2: Create VPCs
Page 309
Step 3: Create VPTs
Setting the ATM Default Parameters

DIRECT creates the ATM network according to certain defined parameters. These have certain default values, but during planning, you may need to set your own values in the ATM Default Parameters dialog box. To open the dialog box, from the ATM menu, click Default Parameters. The ATM Parameters dialog box appears.
ATM Default Parameters
Page 310
About the ATM Atm Default Parameters Tab

In the ATM module, on the Atm Default Parameters tab, you can edit the following ATM parameters:
Item Minimum VCI Minimum VPI IMA delay Description The minimum number at which the Virtual Channel Identifier number will start from, when routing ATM traffic. The minimum number at which the Virtual Path Identifier number will start from, when routing ATM traffic. The delay due to inverse multiplexing.
About the ATM Capacity Calculation Parameters Tab

In the ATM module, on the Capacity Calculation Parameters tab, you can edit the following parameters:
Item Maximum packet loss on Iub Maximum packet loss on Iu-CS Max. allowed AAL2 queuing delay on Iub (ms) Description Input for the CAC (Call Admission Control) - the effect can be seen in Iub and Iu-CS calculations. Input for the CAC (Call Admission Control) - the effect can be seen in Iub and Iu-CS calculations. Input for the CAC (Call Admission Control) - the effect can be seen in Iub and Iu-CS calculations.
Max allowed AAL2 queuing delay on Iu-CS Input for the CAC (Call Admission Control) the effect can be seen in Iub and (ms) Iu-CS calculations. Iur percentage of total Iu traffic (%) Used for the Iur capacity calculation the formula is: Percentage (Iu-CS of RNC1 + Iu-PS of RNC1 + Iu-CS of RNC2 + Iu-PS of RNC2). Slice Size to use in CAC calculation Used to adjust the CAC calculation, in order to model the hardware that you are using.
About the ATM Signalling Parameters Tab

In the ATM module, on the Signalling Parameters tab, you can edit the following parameters:
Item 3g Iub AAL2 Signalling traffic (% of total user plane traffic) 3g Iur AAL2 Signalling traffic (% of total user plane traffic) Description Percentage of total user plane traffic that is used as 3g Iub AAL2 signalling traffic. Percentage of total user plane traffic that is used as 3g Iur AAL2 signalling traffic.
3g Iu-CS AAL2 Signalling traffic (% of total user Percentage of total user plane traffic that is used as 3g Iu-CS signalling plane traffic) traffic.
Page 311
About the ATM Node B Defaults Parameters Tab

In the ATM module, on the Node B Defaults parameters tab, you can edit the following parameters: Number of AAL2 VCCs on the User Plane Number of Iub NBAP-C connections Number of Iub NBAP-D connections Number of Iub AAL2 Signalling connections
About the ATM AAL2 Calc Options Tab

In the ATM module, on the AAL2 Calc Options tab, you can edit the following parameters:
Item Data Unit (Byte) Speedup factor Accuracy (kbps) Description The Byte size that is used in the CAC calculation. The number of iterations for the calculations. The allowed range of accuracy for the calculation - for example, a value of 6 will mean that the calculation must be accurate to at least 6 kbps. The maximum number of times you want to iterate the capacity calculation. The higher the number, the more accurate the calculations will be, but also the longer the calculation will take.
Max Iterations
Calculating QoS and Capacity Over ATM Networks

QoS (Quality of Service) is a key factor in transmission network planning, and is a principal determinant of the capacity requirements of your network connections, and therefore your costs. In the ATM module, you can specify your QoS (Quality of Service) requirements for different ATM-related traffic types. You can then use these to calculate the amount of traffic capacity that meets the required QoS in your network. For more information, see Modelling ATM Quality of Service. To do this automatically, use the Capacity Wizard. To manually calculate capacity using the Method 1 calculation: 1 2 3 Ensure that you have set the ATM Default and Capacity Calculation parameters. Calculate capacities for the VCCs. Calculate the QNM delays. To do this, from the ATM menu, point to Method 1 Calculations and click Calculate QNM Delays. The end-to-end delay is calculated, based on the Queuing Network Model. - or -
Page 312
To manually calculate QoS and capacity using a Method 2 calculation: 1 2 Ensure you have created and routed your traffic. Create an ATM Delay Budget for each element in the connection. For more information on how to do this, see Creating Delay Budgets for Traffic Services on page 175. Define the QoS queuing and scheduling mechanisms, then assign them. If you wish to set up your ATM port controllers manually, do it now. Run the multiplexer requirements allocation, in order to specify the requirements for all of the ATM user plane traffic on the network edges. Calculate capacities for the VCCs, based on the allocated requirements and the configured port controllers.
3 4 5 6
If you have calculated capacity using Method 2b Nominal, you do not need to do anything else. If however you used Method 2a CAC2 or Method 2b Full, continue with the following steps: Run the AAL Analysis. To do this: From the ATM menu, point to Method 2 Calculations, Run AAL Analysis, and then either Selected or All (depending on which edges you want to calculate for). If you calculated capacity using Method 2a CAC2, you do not need to do anything else. If however you used Method 2b Full, continue with the following steps: 1 2 3 4 If you have not set up your ATM port controllers manually, do it now automatically. Run the VPT requirements calculation, in order to specify the requirements for all of the VPT network edges. Calculate capacities for the VPTs, based on the allocated requirements and the configured port controllers. Run the ATM analysis, which analyses all the delay and QoS requirements, and checks them against the calculated capacities.
Page 313
Defining the ATM CAC Parameters Used in Capacity Calculations

The calculations used to determine capacity in the ATM module are based on a series of CAC parameters. In the CAC Parameters Table, you can define different values for these parameters for the different traffic types that you have created. To open this: From the ATM menu, click CAC Parameter Table. The CAC Parameters Table opens. To define the parameters that will be used when calculating using Method 1: 1 2 Click the CAC1 Parameter Table tab. Expand the list of services, and locate the required traffic type:
You can type values for the following parameters:

Parameter Frame Period Length (ms) Bits Per Frame Bits Per Frame Active Bits Per Frame Silent Description Length of the Iub interface frame protocol. The total number of bits in each frame. The number of bits in a frame when the switch is considered to be 'On'. The number of bits in a frame when the switch is considered to be 'Off'.
4 1 2
Click Apply. Click the CAC2 Parameter Table tab. Click Add. A new parameter line is added.
To define the CAC2 parameters:
Page 314
3 4
Select the required traffic service, budget and traffic type. You can type values for the following parameters:
Parameter Alc Max Size (byte) Alc Max Rate (bit/s 64) Alc Avg Size (byte) Alc Avg Rate (bit/s 64) Ctrl # of Sources Ctrl Avg Rate (bit/s) Ctrl Avg Freq (bit/s) Ctrl Pkt Size (bit) Description AAL2 link characteristic - Maximum size of packet. AAL2 link characteristic - Maximum rate of connection. AAL2 link characteristic - Average size of packet. AAL2 link characteristic - Average rate of connection. The number of control connections belonging to the payload traffic. The average data rate of control connections. The average frequency of the control packets. The average size of the control packets.
Click Apply.
Using the Capacity Wizard to Calculate QoS and Capacity

In the ATM module, you can use the Capacity Wizard to automatically calculate the QoS and capacity for your ATM network. This replaces the manual method. To use the Capacity Wizard: 1 2 3 If you want to calculate the QoS and capacity for a specific number of edges, ensure that you have selected them in the module window. From the ATM menu, click Capacity Wizard. Select the required capacity calculation method. This table describes the options:
Method 1 2a 2b Algorithm Used CAC1 CAC2 More advanced Description Calculates capacity and runs the QNM. Allocates AAL QoS requirements, calculates capacity and runs the AAL analysis. As with Method 2a, plus sets up APC ports, allocates ATM QoS requirements, calculates ATM capacity and runs the ATM analysis.
Important : The method you choose should be based on the specific needs of your network. 4 5 6 Click Next. Select whether you want to calculate QoS and capacity for a number of selected edges or for all edges, and then click Next. Select which of the calculations you want to run. The options will vary, according to the method that you have chosen.
Page 315
This table describes the options:

Calculation Calculate Capacity Run QNM Analysis Allocate AAL QoS Requirements Run AAL Analysis VCC Capacity Calculation (Full or Nominal) Description Calculates the capacity for the VCCs and VPTs, based on the scheduling mechanisms and allocated QoS requirements. Calculates the end-to-end delay, based on the Queuing Network Model. Allocates the QoS requirements for VPTs in the ATM network. Calculates the CPS delay, which includes the AAL2 multiplexing, frame and segmentation delays. Calculates the capacity for the VCCs, based on all of the requirements and delay parameters (Full) or just the PCR (Peak Cell Rate) and the estimated overhead. Assigns QoS queuing scheduling mechanisms to VPCs and VCCs. Allocates the QoS multiplexing requirements for the ATM network. Calculates the capacities of the VPTs in the ATM network based on the scheduling mechanisms and the allocated QoS requirements. Runs the Queuing Network Model on the basis of a fixed capacity value, and checks all of the delays and QoS requirements against the new calculated capacities.
Setup APC Ports Allocate ATM QoS Requirements ATM Capacity Calculation (Full or Nominal) Run ATM Analysis
If you are using either Method 2a or 2b, click Next, and check that the AAL2 Calc Options are correctly configured. This table describes the values:
Item Data Unit (Byte) Speedup factor Accuracy (kbps) Max Iterations Description The Byte size that is used in the CAC calculation. The number of iterations for the calculations. The allowed range of accuracy for the calculation - for example, a value of 6 will mean that the calculation must be accurate to at least 6 kbps. The maximum number of times you want to iterate the capacity calculation. The higher the number, the more accurate the calculations will be, but also the longer the calculation will take.
If you are using Method 2b, click Next, and check that the APC Parameters are correctly configured. This table describes the values:
Item Flow queue rate-granularity (cells/s) Flow queue size-granularity (cells) Maximum # of CBR flow queues to use Maximum # of RT-VBR flow queues to use Description The rate at which the scheduled queues will be processed, in cells per second. The size of each scheduled queue, in cells. The maximum number of Constant Bit Rate flow queues that you want to use. The maximum number of Real Time Variable Bit Rate flow queues that you want to use.
Click Next, and check that all of the required calculations are displayed. Tip : You can click each calculation to see which edges the calculation will be run on. If it has already been done for a particular edge (for example, by calculating manually), the edge will be marked with a green tick.
10 Click Generate. The capacity calculations are performed.

Tip : Successful calculations are marked with a green tick, whereas unsuccessful calculations are marked with a red tick. To see which edges were successful or unsuccessful, click the green or red tick as appropriate.
Allocating ATM Multiplexer Requirements

In the ATM module, you can automatically allocate the QoS multiplexing requirements for the ATM network. This will enable you to calculate the VCC and VPT capacities later on. To do this: 1 2 3 Select the VCC edge(s). From the ATM menu, point to Method 2 Calculations and click Multiplexer Requirements Allocation. In the dialog box that appears, select the required Delay Budget and click Allocate Requirements. The TN1 delay (defined in the Delay Budget) and the Tail Probability (defined on the QoS Requirements tab for a traffic service) are evenly allocated across the network. 4 Click Close. You can view the delay requirements that have been allocated on the Method 2 QoS and Transport QoS tabs for an AAL edge, in the Allocated Requirement columns.
Defining QoS Queuing Schedules

In the ATM module, on the ATM Port Controller tab for a VPT, you can define the QoS queues that are used to pass packets of traffic around the ATM network. You can then assign these queues to VPCs and VCCs in order to control the traffic using these connections. To do this: 1 2 3 Click Add Queue. A new queue is created in the Flow Queue pane. In the Scheduling Type column, select which scheduling mechanism will be used for this queue, either Type 1 or Type 2. In the Category column, select which ATM service type scheduler will be used for this queue, either CBR (Constant Bit Rate) or RT-VBR (Real-Time Variable Bit Rate).
Page 317
The following table describes the service type schedulers:

Scheduler Name Flow Queues Rates CBR RT-VBR 32 16 32 CBR 16 RT-VBR Scheduler Type Shaped Virtual Clock (ShVC) Starting Potential Fair Queueing (SPFQ) Number of VCs in Flow Queue Unlimited Unlimited Additional Information N/A Receives service via Guaranteed Traffic Scheduler (GTS) and Excess Bandwidth Scheduler (EBS)
If you have selected a Type 1 scheduling mechanism and a CBR scheduler: In the Rate column, define the traffic rate (cells/s) at which the queue will service the cells In the Buffer Size column, define the buffer between packets (number of cells) In the Weight pane, define the weighting you want to assign to the EBS. This weight is used in Weighted Fair Queuing (WFQ) to assign priorities, with a higher weight signifying a lower priority. By default, a lower priority is assigned to the EBS. In the Rate (SPS/GTS) pane, define the traffic rate of the GTS.
If you have selected a Type 1 scheduling mechanism and a RT-VBR scheduler:
6 7
If you have selected a Type 2 scheduling mechanism and a RT-VBR service type, in the Rate (SPS/GTS) pane, define the traffic rate of the Sub Port Scheduler (SPS). After you have created your queues, you can assign them to the VPCs and/or VCCs in your network.
About the QoS Queue Scheduling Type 1

In QoS Queue Scheduling Type 1 scheduling, predefined data rates are assigned to VCs, based on 3 priority levels, which are (in descending order of priority): CBR Traffic Guaranteed Traffic Scheduler Services (RT-VBR) Excess Bandwidth Scheduler Services (RT-VBR)
Page 318
These 3 groups of VCs are then serviced and scheduled in 3 stages: 1 VCs in the same priority level are serviced, based on the weights assigned to them, in a round robin fashion. Both CBR and RT-VBR VCs are grouped into flow queues based on their rate. The following diagram describes how flow queuing is organised.
The flow queues S1, S2 and Sn are scheduled by S to serve the VCs in the corresponding flow queues in such a way that each receives service at rate r1, r2 and rn. 2 3 Service categories in the same priority level are scheduled. All 3 priorities are merged. The Sub Port Scheduler (SPS) is applied.
About the QoS Queue Scheduling Type 2

For QoS Queue Scheduling Type 2, predefined weights are assigned to VC queues. There are 2 separate sets of queues - CBR and RT-VBR - and each queue contains 1 VC. The number of queues is not limited. The queues are serviced and scheduled in 2 stages: 1 A VC scheduler services the queues, using a Weighted Round Robin (WRR) algorithm. The frequency of servicing these queues is set by its weight. 2 The serviced queues output by the VC scheduler are scheduled by the Sub Port Scheduler (SPS). The SPS uses the Self Clocked Fair Queuing (SCFQ) algorithm.
Page 319
The following diagram describes Type 2 scheduling:
QoS Queue Scheduling Type 2
Allocating VPT Requirements

In the ATM module, after you have defined and assigned the QoS scheduling mechanisms, you can automatically allocate the QoS requirements for VPTs in the ATM network. To do this: 1 2 If you are allocating VPT requirements for a specific number of VCCs and VPTs, ensure you have selected them in the module window. From the ATM menu, point to Method 2 Calculations, then ATM VPT Requirements Allocation, and then click either Selected Edges or All Edges. The Tail Probability, Loss Probability (both defined on the QoS Parameters tab for a traffic service) and the TN4 queuing delay (defined in the Delay Budget) are evenly allocated across the network. You can view the delay requirements that have been allocated on the QoS and Transport QoS tabs for an AAL edge, in the Allocated Requirement columns.
Calculating VCC Capacities

You can calculate the capacities of the VCCs in the ATM network using either Method 1 or Method 2 Calculations. To do this: 1 2 If you only want to calculate VCC capacities for a specific set of edges, ensure you have selected these edges in the module view. If you want to use Method 1 calculations, from the ATM menu, point to Method 1 Calculations, Calculate VCC Capacities and then click either All Edges or Selected Edges. - or -
Page 320
If you want to use Method 2 calculations, from the ATM menu, point to Method 2 Calculations, Calculated VCC Capacities, the required method (Method 2a CAC2, Method 2b Nominal or Method 2b Full), and then click either All Edges or Selected Edges. The following table describes these options:
Use this option Nominal Full To do this Calculate VCC capacity based on the PCR (Peak Cell Rate) and the estimated overhead only. Calculate VCC capacity based on all of the requirements and delay parameters.
VCC capacities are calculated. You can view these on the Capacity tab for a VCC.
Viewing and Selecting VCC Capacities

After you have calculated VCC capacities, on the Capacity tab for a VCC, you can view the capacity (in kbp/s and Peak Cell Rate) based on different calculations: The traffic payload Method 1 CAC1 Method 2a CAC2 Method 2b Nominal Method 2b Full You can select which of these values will be used when routing traffic through the VCC by selecting the appropriate Use option:
Alternatively, you can set a different capacity value to be used, by selecting the Use Override option and typing your own values.
Calculating VPT Capacities Based on QoS Requirements

After you have calculated VCC capacities, you can calculate the capacities of the VPTs in the ATM network based on the scheduling mechanisms and the allocated QoS requirements. To do this: 1 2 If you want to calculate the VPT capacities for a specific number of edges, ensure that you have selected them in the module view window. From the ATM menu, point to Method 2 Calculations, Calculate VPT Capacities, either Nominal (without using the Queuing Network Model) or Full (using the Queuing Network Model), and then click either Selected Edges or All Edges. You can view the results of this calculation on the Type tab for a VPT.
Page 321
Viewing and Selecting VPT Capacities

After you have calculated VPT capacities, on the Type tab for a VPT, you can view the capacity in kbp/s based on different calculations: Nominal Method 1 Nominal Capacity Method 2 Full Capacity Method 2 You can select which of these values will be used when routing traffic through the VPT by selecting the appropriate Use option:
Alternatively, you can set a different capacity value to be used, by selecting the Use Override option and typing your own values.
Assigning QoS Queuing Scheduling Mechanisms to VPCs and VCCs

After you have defined QoS queuing scheduling mechanisms, you can assign them to the VPCs and/or VCCs in your network, as appropriate. You can do this either automatically or manually. Assigning Queuing Scheduling Mechanisms Automatically From the ATM menu, click Run ATM Port Setup. DIRECT creates a single flow queue, and assigns all of the VCCs in a VPT to this queue. To view this queue: 1 2 In the VPT Group dialog box, select the VPT Click the ATM Port Controller tab.
Assigning Queuing Scheduling Mechanisms Manually If you assign queuing scheduling mechanisms manually, you can either: Assign a scheduling mechanism to the VPC, which will also assign it to the underlying VCCs as well - or Assign scheduling mechanisms to individual VCCs Warning : If you assign a scheduling mechanism to an individual VCC after you have assigned a different one to the VPC as whole, or vice versa, it will overwrite the original setting.
Page 322
To assign a scheduling mechanism to the entire VPC: 1 2 3 4 In the VPT Group dialog box, select the VPT. Click the ATM port controller tab, and in the Direction pane, select the direction of the traffic, based on the source and destination. In the VC Setup pane, select the VPC. Double-click the queue column, and select the required queue from the list. Note : The queue's ATM service type (category) must match that of the VPC. To assign a scheduling mechanism to an individual VCC: 1 2 3 4 5 In the VPT Group dialog box, select the VPT. Click the ATM port controller tab, and in the Direction pane, select the direction of the traffic, based on the source and destination. In the VC Setup pane, select the VPC. If the underlying VCCs are not shown, double-click the + sign next to the VPC. For the required VCC, double-click the Queue ID column, and select the required queue from the list. Note : The queue's ATM service type (category) must match that of the VCC.
Performing the ATM Analysis

After you have calculated the VPT capacities for the ATM network, you can perform the ATM analysis. This runs the Queuing Network Model on the basis of a fixed capacity value, and checks all of the delays and QoS requirements against the new calculated capacities. To perform the ATM analysis and view the results: 1 2 3 4 5 If you want to perform the ATM analysis for a specific number of links, ensure that you have selected them in the module view window. From the ATM menu, point to Method 2 Calculations, Run ATM Analysis and then click Selected Edges or All Edges. Double-click the required VPT group edge. In the dialog box that appears, select the required VPT. Click the VC Information tab to view the following values calculated by the ATM Analysis:
Value Analysis CTD Analysis CDV Analysis CLR Analysis Tail Probability Description Cell Transfer Delay - the time taken to transfer packets between nodes, after ATM analysis. Cell Delay Variation - the deviation from the mean CTD, after ATM analysis. Cell Loss Ratio - the number of packets lost per unit of time, after ATM Analysis. Tail Probability - the probability that the buffer will extend past the specified limit, after ATM Analysis.
Compare these values to the Allocated Requirement values to measure the calculated capacities against the QoS requirements.
Page 323
About ATM Service Categories

Cross-connections in the ATM module can use a number of categories of service. This table describes each category:
Service Category Name CBR Description AAL Layer Used Used for connections that depend on precise clocking to ensure undistorted AAL1 delivery. After virtual channel set up, these services require information to be transferred at a constant bit rate between source and destination. Traffic (e.g. voice) is delay sensitive, so end-to-end timing is required. Typical applications for CBR are videoconferencing, interactive audio (telephony), audio/video distribution (television, distance learning, pay-per-view) and audio/video retrieval (video-on-demand, audio library). Used for connections where timing is necessary between source and destination, but here each source can operate at a variable rate. The RT-VBR traffic sources are video and compressed voice. Used to transmit data that is sensitive to loss, but not to delay. Typical applications for this service are data transfers for transaction processing applications such as airline reservation, banking transactions and process monitoring. AAL2
RT-VBR
NRT-VBR
AAL3/4
ABR
Used for connections that do not require timing relationships between source AAL3/4 and AAL5 and destination. A minimum rate per connection is specified, but the network will attempt to provide a higher rate when it is needed. There is no guarantee of getting the higher rate. In this service, the network provides as much bandwidth as is available at the AAL5 time, by utilizing any unused capacity from other connections. No minimum rate is guaranteed, and this is often called 'best effort' service. It can be used for text/data/image transfers, remote terminal (telecommuting), e-mail, store-andforward networks, LAN interconnection, LAN emulation, supercomputer applications, remote procedure call, distributed file services and computer process swapping/paging.
UBR
This table cross-references the classes of service and their characteristics:

Class A Timing Between Source and Destination Bit Rate Connection Mode ATM Adaptation Layer AAL1 Constant Class B Required Variable Connection Oriented AAL2 AAL3/4AAL5 Connectionless AAL3/4, AAL5 Class C Class D Not required
Creating VCI Numbering Templates

In the ATM module, you can create VCI numbering templates, which enables you to reserve specific sets of VCI numbers for different types of traffic - User Plane, NBAPC and so on. By using a VCI numbering template, you do not have to edit the VCI numbers for each individual VPC edge group. To create a VCI numbering template: 1 2 3 4
Page 324
From the ATM menu, click VCI Number Template. In the dialog box that appears, click Add Template. On the General tab, in the Identification pane, type a name for the template. Click the VCI Templates tab.
For each VCC type, you can set the following values:
Item No of Reserved VCIs per cycle No of VCIs created per cycle Sequence Starting No Description The number of VCIs that will be allocated sequentially per cycle of VCI numbering performed when routing the VCCs. The number of VCIs that will be created per cycle of VCI numbering performed when routing the VCCs. The position of the VCC type in the cycle sequence. For example, a VCC type assigned as '3' would be 3rd in the cycle sequence. The number from which the VCI numbering for this VCC type will begin.
Note : When VCI numbering begins, if there is no VCC available for a particular VCI number, then the VCI number is reserved, and not allocated. The VCI numbering continues by moving onto the next number. After you have created your template, you can now assign it to a VPC.
Assigning VCI Numbering Templates to VPCs

In the ATM module, if you have created a VCI numbering template, you can assign it to a VPC. This enables you to reserve specific sets of VCI numbers for different types of traffic - User Plane, NBAP-C and so on. By using a VCI numbering template, you do not have to edit the VCI numbers for each individual VPC edge group. To assign a numbering template to a VPC: 1 2 3 4 5 In the ATM module window, double-click the VPC group containing the VPC. In the dialog box that appears, select the VPC from the list in the left-hand pane. Click the Template Selection Page tab. Select the required template from the list. Click Apply.
Page 325
Viewing and Editing VCC Group Properties

You can view and edit the properties of a VCC group in the VCC Group dialog box.
ATM VCC Group dialog box
The VCC group provides: A detailed and editable virtual channel/virtual path breakdown Service rate and service category details, which you can edit You can also manually edit and freeze individual routes end-to-end across the ATM network.
Page 326
Adding and Editing VCCs in a VCC Group

On the All VCCs tab for a selected VCC group, you can add new VCCs to the group and edit the traffic for all of the VCCs contained in the group. To add a new VCC to the group: 1 2 3 To open this dialog box, double-click the VCC group in the module view window. Click the Add Edge button. A new VCC appears, with an uplink and a downlink. For each VCC, you can edit the following properties:
Item AAL Type Service Category Description The type of ATM Adaptation Layer used. The service category for the virtual circuit connections. The following options are available: CBR (Constant Bit Rate) RT-VBR (Real Time Variable Bit Rate) NRT-VBR (Non-Real Time Variable Bit Rate) ABR (Available Bit Rate) UBR (Unspecified Bit Rate)
To set the total capacity for the VCC group, select the User Defined Total Capacity checkbox, and type the value in the right hand box.
Description The type of traffic using the VCC. The number of connections using this VCC. The bit rate (in kbit/second at Peak Cell Rate) required to provide the service for the number of connections.
Note : You can also view the following properties for the uplink and downlink:
Item Traffic Type No of Connections Total Service Rate kbs/PCR
On this tab, you can also distribute traffic across a group of VCCs
Page 327
Distributing Traffic Across a VCC Group

If there is any unassigned traffic in your ATM network (when you have deleted a VCC, for example), you can distribute this on the All VCCs tab of the VCC Group dialog box. To distribute unassigned traffic: 1 Click the Distribute button. The Traffic Distribution dialog box appears.
2 3 4 5
Select the AAL type and service type of the traffic. Select the checkbox of the VCC over which you want to distribute the traffic. Select the checkbox of the unassigned traffic that you want to distribute over the VCC. Click the Distribute button.
About the AAL/Service Category Tabs for a VCC Group

The VCC Group dialog box has four tabs, corresponding to four AAL type/Service category combinations: AAL2/CBR VCCs AAL5/CBR VCCs AAL5/UBR VCCs AAL1/CBR VCCs AAL5/RT-VBR VCCs AAL5/NRT-VBR VCCs
Each of these tabs contains similar information as the All VCCs tab, but is specifically related to the VCCs within that category. For information on how to add and edit VCCs, see Adding and Editing VCCs in a VCC Group on page 327. For the AAL2/CBR VCCs, you can use the CAC algorithm to calculate the 'effective' bandwidth (capacity) for a VCC. To do this, on the AAL2/CBR VCCs tab, click the Calculate CAC button. Tip : A message pane in the centre of the tab indicates whether or not the CAC has been calculated since changes were made. If it says it has not, click the Calculate CAC button to update the values.
About the VCIs Tab for a VCC Group

On the VCIs tab for a selected VCC Group, you can view the individual VCI numbering that the VCC has over each hop of its route.
VCIs tab on an Edge Group
On this tab, you can also select to freeze selected VCIs, and also indicate which VCI numbers to freeze. In this way, you can freeze specific sections of a route. To freeze a VCI: 1 2 Click on the appropriate row in the Freeze VCI column, and select Yes. Double-click on the appropriate row the VCI Number to Freeze, and type in the VCI number.
About the Delay Parameters Tab for a VCC Group

In the ATM module, DIRECT calculates the delays for Iub and Iu-CS User Plane delays connections. You can view these on the Delay Parameters tab of the VCC Group dialog box. The Delay parameters tab displays the following properties:
Property VCC Capacity (kb/s) ATM Queuing delay (ms) Deviation of ATM Queuing delay (ms) Physical delay (ms) Traffic type Service type Description The name of the VCC for example, if there are 4 VCCs, they will be named VCC1, VCC2 and so on. The capacity of the VCC. The amount of ATM queuing delay. The standard deviation of the ATM Queuing delay figure. The sum of the IMA delay, the ATM switch delay, the queuing delay and the transmission (logical connection) delay. The type of traffic carried by the VCC experiencing delay. The type of service carried by the VCC experiencing delay.
Page 329
Property Connections (#) AAL2 delay (ms) Deviation of AAL2 delay (ms) Total delay (ms) Standard deviation of total delay (ms)
Description The number connections contained in the VCC experiencing delay. The amount of delay caused by the ATM Adaptation Layer 2. The standard deviation of the AAL2 delay figure. The total delay in the VCC. The standard deviation of the total delay figure.
Viewing and Editing VPC Group Properties

You can view and edit the properties of a VPC group in the ATM VPC EdgeGroup dialog box. To open this dialog box, double-click the VPC.
ATM VPC dialog box
Viewing VPCs and VCCs in a VPC Group

On the VCCs tab of a VPC group, you can view the VPCs and VCCs in a VPC group. The following table shows the properties that you can view:
Item VPC->VCC VCI AAL Type Description The name of the VPC, the VCCs routed through it, and the traffic type on those VCCs. The Virtual Channel Identifier, which marks its place in the traffic sequence. The ATM Adaption Layer that this traffic is transported across.
Page 330
Item Service Category
Description The service category for the virtual circuit connection. The following options are available: CBR (Constant Bit Rate) RT-VBR (Real Time Variable Bit Rate) NRT-VBR (Non-Real Time Variable Bit Rate) ABR (Available Bit Rate) UBR (Unspecified Bit Rate) For more information on the categories available, see About ATM Service Categories on page 324.
Traffic Type Total Service Rate kbs/PCR
The type of traffic on the VPC/VCC. The bit rate (in kbit/second at Peak Cell Rate) required to provide the service for the number of connections.
About the VPIs Tab of the ATM VPC Group Dialog Box
On the VPIs tab for a selected VPC Group, you can view the individual VPI numbering that the VPC has over each hop of its route.
On this tab, you can also select to freeze selected VPIs, and also indicate which VPI numbers to freeze. In this way, you can freeze specific sections of a route. To freeze a VPI: 1 2 Click on the appropriate row in the Freeze VPI column, and select Yes. Double-click on the appropriate row the VPI Number to Freeze, and type in the VPI number.
Viewing and Editing VPT Group Properties

You can view and edit the properties of a VPT in the appropriate ATM VPT Group dialog box. To open this dialog box, double-click a VPT.
About the VCCs & VPCs Tab of the ATM VPT Group Dialog Box
On the VCCs & VPCs tab of the VPT group dialog box, you can view the VCCs and VPCs routed through the VPT. The following information is displayed:
Item VPT VPI VCI Description The name of the VPT, and beneath it the VCCs that are routed through it. The Virtual Path Identifier. The Virtual Channel Identifier.
Page 331
Viewing and Editing VPT Properties

Individual VPTs in a VPT group have their own properties, which you can view and edit. To view a VPT: In the ATM module view, double-click the VPT group that contains the VPT. In the dialog box that appears, in the left-hand pane, select the VPT.
Viewing the Delay Parameters for Physical Links

In the ATM module, you can view the delay parameters for a specific VPT. To do this: 1 2 Select the required VPT. Click the Delays tab.
Description The amount of delay caused by ATM queuing. The standard deviation of the AT queuing delay figure. The amount of delay caused by processing. The total of the transmission, IMA and interface delays, for both primary and secondary routes.
On this tab, you can view the following properties:

Property ATM queuing delay (ms) Standard deviation of ATM queuing delay (ms) Processing delay (ms) Transmission, IMA and interface delays (ms)
Defining IMA Groupings for Physical Links

In the ATM module, You can set the VPTs to contain IMA (Inverse Multiplexing on ATM) groupings. In this way you can significantly increase the capacity of the link. Important : You can only use IMA on primary rate (1.5M or 2M) connections. Furthermore, the PDH module must have equivalent edges on the edge group to support the IMA group. For example, if IMA is enabled on a VPT with 4 x E1s, then the underlying PDH module should have 4 edges defined in the edge group to enable the routing to occur. To do this: 1 2 3 4 5 Double-click the VPT group that you want to change to an IMA link. The ATM VPT GroupEdge dialog box appears. Select the required VPT Edge from the VPT Group. On the Type tab, ensure that the connection is set to a primary rate (1.5M or 2M). Select the Use IMA checkbox. Edit the following IMA parameters:
Parameter IMA connections M parameters IMA group ID Description The number of cables used. The frame length, used for capacity calculations. The ID name you want to assign to the IMA group.
Page 332
Note : You can also view the load (how much traffic is carried in relation to the overall capacity) as a percentage. 6 Click Apply.
Viewing and Editing the VPT Information for Physical Links

In the ATM module, you can view and edit the results of the VPT Capacity Calculation. To do this: 1 2 3 4 In the ATM module view window, double-click the VPT Group that contains the required VPT. In the VPT Group list pane, select the VPT. Click the Vpt Information tab. You can view and edit the following information for both the uplink (Direction A) and the downlink (Direction B):
Item Queuing Delay Queuing Delay Variation Calculated Nominal Capacity Calculated Full Capacity Description The queuing delay on this individual VPT. The deviation from the mean queuing delay. The capacity for the VPT generated when you perform the Nominal capacity calculation (without the QNM model). The capacity for the VPT generated when you perform the Full capacity calculation (with the QNM model).
Tip : The calculated nominal and full capacities for both the uplink and downlink can also be edited on the Type tab.
Viewing and Editing AAL Group Properties

You can view and edit the properties of an AAL in the appropriate ATM AAL Group dialog box. To open this dialog box, double-click an AAL.
Setting the AAL Layer for ATM Traffic

In the AAL Edge Group dialog box, on the AAL Parameters tab, you can view traffic that passes through the edges in the group, and also set which AAL the traffic will use. The AAL is the ATM Adaptive Layer, and is the first layer in the ATM network that traffic will arrive on from the layer above. On the AAL, you can apply packet schedulers and shaping, in preparation for routing on the other ATM layers. To do this: 1 2 3 Ensuring that you are selecting the right traffic direction (indicated by the source and destination nodes), click the required edge. In the AAL Type column, select the required AAL layer. For more information, see About the AAL Edge Types Used in DIRECT on page 334. Click Apply.
Page 333
About the AAL Edge Types Used in DIRECT

The AAL edges types used in DIRECT are described in the following table:
Item AAL2 AAL5 Description Used for all BTS to RNC and RNC to RNC connections (Iub, Iur) and for the CS traffic between the RNC and the Core network (Iu-CS). Used for the PS traffic between the RNC and the Core network (Iu-PS). AAL5 multiplexing is modelled with an infinite G/G/1 queue.
Viewing and Editing AAL Edge Properties

Individual AAL edges in an AAL edge group have their own properties, which you can view and edit. To view an AAL edge: In the ATM module view, double-click the AAL edge group that contains the AAL edge. In the dialog box that appears, in the left-hand pane, select the AAL edge.
Viewing Traffic on AAL Edges

In the AAL Edge Group dialog box, on the Traffic tab for an AAL edge, you can view the traffic for this AAL edge. The following table describes the traffic details that you can view:
Item Traffic Position Edge Bitrate (Kbps) Traffic Utilisation Circuit Utilisation Channel Utilisation Description The traffic type using the edge. Indicates whether this is uplink (0) or downlink (1) traffic. The edge that the traffic is routed onto from here. The speed of the traffic in kbits per second. The percentage of this traffic using the edge (100 if routed, 0 if not). The percentage of the used traffic channels against the maximum available traffic channels. The number of traffic channels that are used divided by the total number of traffic channels.
Viewing Delays on AAL Edges

In the AAL Edge Group dialog box, on the Method 2 Delays tab for an AAL edge, you can view: Mean Delay (ms) - The mean delay per AAL edge Delay Standard Deviation (ms) - The standard deviation of the delay per AAL edge
Page 334
Viewing Calculated QoS for AAL Edges

In the AAL Edge Group dialog box, on the Method 2 QoS tab for an AAL edge, you can view the QoS for the traffic using this AAL edge. You can view the values in 3 different states: Requirement - The values set in the ATM QoS default parameters Allocated Requirement - The results of the Multiplexer Requirements Allocation and VPT Requirements Allocation calculations Analysis - The results of the ATM Analysis calculation The following table describes the values that you can view:
Item Tail Probability AAL Mux Delay (ms) Segmentation Delay ATM Delay (ms) Description The probability that the buffer will not grow past its limit The delay taken to fill a VCC with traffic. The delay taken to segment the traffic. The delay taken based on: The media type used (T2) The time taken to process the packets (T3) The time taken in queuing the packets (T4) Total Delay (ms) The total end-to-end delay for the AAL edge.
Viewing Calculated Transport QoS for AAL Edges

In the AAL Edge Group dialog box, on the Method 2 Transport QoS tab for an AAL edge, you can view the calculated transport QoS for the traffic using this AAL edge. The following table describes the values that you can view for each of Requirement, Allocated Requirement and Analysis:
Item TN Delay Multiplexing Delay (ms) Media Delay (ms) Processing Delay (ms) Forwarding Delay (ms) Total Delay (ms) Description Maximum allowable CPS delay for each traffic type multiplexed in the VCC. Delay due to multiplexing (T1). Delay due to the media type used (T2). The time taken to service the packets (T3). The time taken to transport the processed packets across the layers (T4). The total end to end delay for the AAL edge.
Page 335
Page 336
CHAPTER 11
Creating the IP Network

You can use the IP module to model packet switched networks. You can also perform transmission capacity dimensioning for GPRS networks. In the IP Module, you can calculate the transmission capacities of the IP network according to the estimated traffic demand. The IP module also provides equipment capacities and network usage estimates. You can also use the IP module to estimate packet throughputs and packet loads of equipment, and you can include protocol overheads in the capacity calculations to give more realistic results.
In This Section
Overview of the IP Module About Planning The IP Network Setting the IP Network Default Parameters Using IP Addresses in DIRECT Calculating QoS and Capacity Over IP Networks 337 339 340 343 348
Overview of the IP Module

In the IP module, you can: Display all IP nodes created within the cellular and/or RF plans within ASSET3G (in other words, SGSN). Create new core network elements. Distribute traffic created within the cellular/RF network plan to network elements within the core network. Allocate and distribute IPv4 and IPv6 network addresses to node and sub-network elements.
Page 337
This picture shows an example of IP network address distribution:
Create segments within an IP network Add overhead requirements for traffic, and then target the traffic to a specific network layer (for example, Ethernet, ATM, SDH and so on) Model IP nodes with the following parameters: Queuing scheme Forwarding scheme Routing table Total load
Calculate capacity based on an iteration algorithm. First, the capacity is estimated with an M/M/1/K queuing model, and then the iteration is performed. You can set the maximum number of iterations and the accuracy. The approximation is performed for each traffic type aggregate mapped to a given I and U class separately.
Page 338
As a planner, you can see if the traffic meets its end-to-end QoS requirement and identify the individual network elements in the end-to-end path where the traffic failed to meet the set requirement. You can then decide to either plan round the problem or increase the capacity. This picture shows an example of the QoS results for an IP edge:
About Planning The IP Network

If you are new to DIRECT, it is recommended that you follow the work order set out below when planning your first few IP networks: 1 2 3 4 5 6 7 8 9 Set the IP network default parameters, for example the default QoS scheme. In the Traffic module, ensure you have configured your cellular nodes correctly and added the appropriate amounts of traffic to the connections. In the Traffic module, create IP core network elements, and connect cellular network nodes and IP network nodes using bi-directional traffic links. Add traffic to this link. This is done because at this stage traffic from the cellular network node cannot be directly distributed to the required parts of the network. In the IP module, ensure that the IP nodes are correctly configured. Add or distribute the required IPv4 and IPv6 addresses. Create the required connections between the IP nodes. Configure the connections, and assign any overheads. Route the layers in the following order, as appropriate: IP ATM SDH Transmission
Page 339
10 In the IP module, calculate the QoS and capacities over the IP network.
Setting the IP Network Default Parameters

DIRECT creates the IP network according to certain defined parameters. These have default values, but during planning you may need to set your own values in the IP Default Parameters dialog box. 1 To open the dialog box, from the IP menu, click IP Default Parameters. This picture shows an example IP Default Parameters dialog box.
Page 340
You can edit the following parameters:

Parameter QoS Scheme Description Used with the Queuing Network Model to calculate the capacity of the IP physical edges and perform the network analysis. The following QoS schemes are available: Best Effort - One queue is used, and the queue services packets based on the first in, first out principle. Therefore, no QoS can be guaranteed. DS - Differentiated Services scheme - The CoS considers the I (Importance of Packet Delivery) and U (Urgency of Packet Transfer) to determine how the packets are treated. Multimode DS - Multimode Differentiated Services scheme - The WFQ (Weighted Fair Queuing) system is used with the I, U parameters. For more information, see About the QoS Schemes in the IP Module on page 342. Maximum Urgency The maximum allowable Urgency factor, based on the packet transfer delay - the lower the number, the greater the urgency. This determines the queue it will be placed in. The maximum allowable Importance factor, based on the packet delivery priority - the lower the number, the greater the priority. This determines the place in the queue. The type of queue, determined by the drop function used. The drop function reduces the traffic load at the node by dropping lower importance class packets before higher importance ones. The following types of queue are available: Own Queue - The drop function for each queue is calculated separately, and the load in one queue does not affect that of other queues. Sum of Queues - The drop function calculates the cumulative load of all the queues. Maximum of Queues - The drop function calculates the maximum loads of all the queues. Squared Maximum of Queues - The drop function calculates the squared maximum loads of all the queues. Break Point The break point is the buffer load above which the drop function begins to take effect. Note : You cannot edit this if you are using a Best Effort QoS scheme. Use Restrictions for Class of Service Multimode Use Routing Tables If you select this option, you will only be able to choose the CoS classes that are available for the selected traffic type. Select this option if you want to use the existing routing tables when routing the IP traffic. Otherwise, the routing tables will contain the values generated when you route the network. Queue Count The number of queues required at the node. Note : You can only edit this if you are using a DS QoS scheme Forwarding Delay Queue Length Link Delay Link Capacity Loss Probability The time taken to transport the processed packets across the layers (T4). The length of each queue in packets. The end-to-end delay on a link. You can set an existing capacity for links. Links using this capacity will not be included in the IP capacity calculation, but will be included in the PQNA analysis. The probability that packets will be lost.
Maximum Importance Drop Function Type
Page 341
About the QoS Schemes in the IP Module

In the IP module of DIRECT, you can use a number of different QoS schemes: Best Effort - The node contains 1 buffer, so the only Class of Service provided by the router is Best Effort Differentiated Services (DS) - There is no limitation on the number of buffers, and there are multiple buffers (queues) of different priority. The services provided by the router are those defined at the network level, in the Traffic module. This picture shows an example of an IP Router supporting DS:
Multimode DS - The number of buffers is fixed between 6 and 8, and the traffic leaving the buffers is scheduled by the combination of Weighted Fair Queuing (WFQ) and of strict priority. Before entering the buffers, the traffic is expressed in AF and EF PHB categories and is mapped into Urgency (U) and Importance (I) classes. The index of the buffer indicates the urgency class - for example, traffic with an urgency class of 7 is mapped to buffer U7 (this has the highest priority). At the input of U5, U6 and U7, rate limiters are applied, which work on the base of the Token Bucket algorithm and are used to prevent the high priority traffic from occupying the full bandwidth.
Page 342
This picture shows an example of an IP Router supporting Multimode DS:
Using IP Addresses in DIRECT

An IP address refers to a network interface on a device such as a router and gateway. A router or gateway can have more than one IP address. DIRECT supports IP v4 and IP v6 addressing. For more information on how IP addressing works, see About the IP Addressing Concept on page 344. There are two ways to add IP addresses to equipment: Add individual addresses to separate pieces of equipment Distribute a pool of addresses across a group of equipment Important : If you choose to distribute a pool of addresses, they will only be distributed to the equipment, and not any separate ports within that equipment. To add an IP address to a port, you must add it individually.
Page 343
About the IP Addressing Concept

DIRECT supports IP v4 and v6 addressing, which are the address interactions between host terminals and devices. An IP address can be defined as a network interface on a device, for example a router or gateway, but an interface can have more than one IP address. IP v4 addressing is divided into five address classes, to provide sufficient flexibility for different sized networks. The three most popular classes are A, B and C, and their general properties are summarised in this table:
Class A 1 Bit(s)
st
Class B 10 14 16 16384 65536 128.191.x.x.x
Class C 110 21 8 2 million 254 192.223.x.x.x
0 7 24 128 16.8 million 0.128.x.x.x
Network ID identified by next (bits) Host address defined by last (bits) Max number of networks Approximate number of hosts on each network Address range
Additionally: Class D addresses have their leading 4 bits set to 1 1 1 0 and are used to support IP multicasting Class E addresses have their leading 4 bits set to 1-1-1-1 and are reserved for experimental use
About the Sub-netting and Bit Mask Concept

To increase the Class C domain without having to replace software (and routing tables) in all routers, the concepts of sub-netting and bit masks were introduced. This enables you to use existing addressing schemes. A bit mask is composed of: Binary 1s in the bit positions that contain a network address including the net ID and sub-net ID Binary 0s in the bit positions that contain the host ID For example, in a bit mask of 11111111 11111111 11111111 00000000 the first three bytes contain the network and subnet identifier, and the fourth byte contains the host identifier bits. In decimal, this bit mask is expressed as 255.255.255.0. Tip : In shorthand notation, IP addresses with bit masks can be written in address/prefix-length format. For example, an IP address of 172.168.6.9 with a mask of 255.255.255.224 can be written as 172.168.6.9/27.
Page 344
Adding IP Addresses to Equipment

IP networks are based on delivering packets of data end-to-end across a number of virtual links, and to perform this delivery, the endpoints need addresses. IP protocols define globally unique addresses for the host computers and routers. IP addresses are organised hierarchically, in clusters called IP subnets. Based on the IP address of a computer, you can determine its IP subnet. In the IP module of DIRECT, you can add IP addresses to equipment. To do this: 1 2 Double-click on the equipment to which you want to add addresses. In the Equipment Properties dialog box, click the IP Addresses tab.
3 4 5 6 7 8
Select the equipment in the left-hand list. Click the Add Address button. A new row is added to the address table. Type the new address and mask details in the new row. Choose to display the address in decimal (Dec) or hexi-decimal (Hex) format, by selecting one of the checkboxes. Choose to make the mask style class-based (Decimal) or not (Prefix), by selecting one of the checkboxes. Click Apply.
Page 345
Distributing IP Addresses
As well as adding IP addresses to equipment, you can distribute a pool of addresses across equipment. To do this: 1 2 3 4 5 In the IP module view, select the node for which you want to allocate IP addresses. From the IP menu, click Start IP Address Distribution Wizard. Select the name of the root node equipment and the distribution type, either IPv4 or IPv6. Click Next. On the IPvx Address Distribution page, enter the details as shown in the following table:
In this box Network Address Do this Type in the base address for the pool of addresses that you want to distribute. Description The starting address for distribution.
From the drop-down box, select a network The number of bits used to identify the network. The prefix length remaining bits represent the number of hosts available. Note : For a Network Prefix Length (or NPL) of 27, 32 host addresses are available. Of these, the first (.0) and the last (.255) are used as the subnet identifier and the broadcast address respectively, leaving 30 hosts available for use. Subnet Mask (IPv4 From the drop-down box, select the addresses only) required subnet mask. Note : The NPL will automatically calculate and display the default, but you can choose another. This represents the range of addresses that can be distributed.
Page 346
Tip : Once you have completed these details, a range of additional information about this address pool is displayed, such as its class and number of available addresses. This picture shows an example:
6 7
Select the equipment that you want to distribute on. Click Distribute. An IP address is assigned to each connected node that you have selected. The subnet mask determines how many addresses are available, and the addresses will be based on the starting address that you have defined. The assigned address for a particular node is displayed under the name of the equipment. Tip : To remove an address from a node, select the address, and click Clear.
Distribute more addresses as required, and when you are satisfied, click Finish.
Page 347
About the IP Address Distribution Types

DIRECT uses two types of address distribution, IPv4 and IPv6. The following table gives a brief description of them:
Item IPv4 Description Uses a 32-bit address, which is assigned to the host computer. An IPv4 address is 1 of 5 classes (ranging from A to E), and is written as 4 octets, each separated by a period. The address can range from 0.0.0.0 to 255.255.255.255. This address is made up of: A network number - used for routing A subnetwork number (optional) - used for routing A host number - used to address an individual host within a network or subnetwork IPv6 A replacement for IPv4, IPv6 was previously known as IPng. Includes support for flow identity in the packet header, which can be used to identify flows in and improve QoS.
Calculating QoS and Capacity Over IP Networks

QoS (Quality of Service) and CoS (Class of Service) are key factors in transmission network planning, and are principal determinants of the capacity requirements of your network connections, and therefore your costs. In the IP module, you can specify your QoS and CoS requirements for different IPrelated traffic types. You can then use these to calculate the amount of traffic capacity that meets the required QoS/CoS in your network. Important : You cannot calculate capacity calculations until you have allocated the QoS requirements. To do this: 1 2 3 4 5 6 In the IP module, in the IP Default Parameters dialog box, select the required QoS scheme and define the parameters for the IP router. Set the QoS requirements, CoS requirements and Delay Budgets for the traffic service(s) used in the network. Route the traffic onto the IP layer. Run the QoS Requirements Allocation calculation, in order to specify the requirements for the IP physical edges. Calculate capacities for the IP physical edges, based on the allocated requirements. Run the PQNA analysis, which analyses all the delay and QoS/CoS requirements, and checks them against the calculated capacities.
Page 348
Allocating QoS Requirements

In the IP module, you can automatically allocate the QoS requirements for the IP network. This will enable you to calculate the IP edge capacities later on. To do this: From the IP menu, click QoS Requirements Allocation. The Maximum Delay, the Tail Probability and the Loss (defined on the QoS Parameters tab for a traffic service) are evenly allocated across the network. You can view the delay requirements that have been allocated on the QoS tab for an IP edge, in the Allocated Requirement row for the traffic type. Note : Only IP edges that have been correctly routed are displayed.
Setting the Router Capabilities for IP Traffic Edges

If you are using IP routers to forward traffic between nodes in your IP network, you can set the router capabilities for individual traffic edges. This enables you select what queuing scheme will be used on the edge, what QoS parameters will be selected and so on. To do this: 1 2 3 4 In the IP module view, double-click on the required edge group. In the dialog box that appears, select the required edge. Click the Router tab. Select the Queuing scheme that will be used by the router when handling traffic on this edge. You can choose either Best Effort or the scheme set in the IP Default Parameters. If you choose Best Effort, one queue is used and the queue services packets based on the first in, first out principle. Therefore, no QoS can be guaranteed. 5 6 If you select the DS queuing scheme, select whether to apply the scheme to core (internal) edges or (external) edges, by choosing the appropriate checkboxes. In the port controller pane, select the traffic direction you want to define by choosing the source-destination port controllers. You can now define the router settings for the traffic direction you have selected. For information on how to do this, see Defining Router Settings for IP Traffic Edges on page 350.
Page 349
Defining Router Settings for IP Traffic Edges

After you have set the general router capabilities for an IP traffic edge, you can define the specific settings for the IP Router. The IP router is used to pass packets of traffic onto the IP logical layer. To do this manually: 1 Select the drop function type that you want to use. Note : If you are using the Best Effort queuing scheme, the drop function will be set by default to Own Queue, as this is the only one to calculate for individual queues. The following types of queue are available: 2 Own Queue - The drop function for each queue is calculated separately, and the load in one queue does not affect that of other queues Sum of Queues - The drop function calculates the cumulative load of all the queues Maximum of Queues - The drop function calculates the maximum loads of all the queues Squared Maximum of Queues - The drop function calculates the squared maximum loads of all the queues
Set the break point for the selected drop function type. The break point is the buffer load for the scheduling scheme, above which the drop function will take effect. Note : If you are using the Best Effort queuing scheme, the Own Queue drop function does not have a break point.
Set the number of queues for the router on the edge by clicking the up and down arrow buttons. Note : If you are using the Best Effort queuing scheme, the number of queues is fixed at 1.
For each queue, you can set the queue length (in number of packets) and the percentage of the queue used for IP traffic.
Calculating the IP Capacities Based on QoS/CoS Requirements

After you have configured the IP routers on the IP edges, you can calculate the capacities of the edges in the IP network based on the schedules and allocated QoS requirements. To do this: From the IP menu, point to Calculate Capacities and click either Nominal or Full. The following table describes these options:
Use this option Nominal Full To do this Calculates the capacities, but only takes into account the protocol overheads. Calculates the capacities, based on the end-to-end delay specified in the Delay Budget.
Page 350
You can view the results of the calculation in the IP Physical Edge Group dialog box, on the selected IP physical edge, on the Load tab. It displays the calculated capacity in kbps using either calculation, on the uplink (Direction A) and downlink (Direction B).
Setting the Overheads for IP Edges

In the IP module, you can define the IP overheads for IP layers 2, 3 and 4 of an edge. These are used to calculate the nominal IP capacity. To do this: 1 2 3 4 In the IP module view, double-click on the required edge group. In the dialog box that appears, select the required edge. Click the Overhead tab. You can view and edit the following overhead values:
Item Description The Overhead is the percentage overhead value used to estimate the effect of different traffic protocols to traffic requirements. Layer 3 Payload Capacity, IP The Payload Capacity is the amount of payload that is transported in this link, in Kbit/s. Packet Size, IP Packet IP Packet size is the size of the packet of IP data in bytes. Header, Frames/s IP Packet header is the size of the frame header for each packet, in bytes. Frames/s is the number of frames in the link per second. Layer 4 Cellular Overhead and GTP Overhead You can select to add additional layer overheads. GTP overhead is the GPRS Tunnelling Protocol over head. The GPRS tunnelling protocol is a 3GPP standard protocol used to deliver packets between the RNC and the core network (SGSNs and GGSNs). It is only used for PS user plane traffic. The UDP/IP packets are encapsulated in GTP packets, so you must add the extra header introduced by this protocol. The total capacity that the IP edge has, in kbit/s. Layer 2 Header and Overhead The Header is the average frame header size in the link, in bytes.
Total Capacity
Performing the PQNA Analysis

After you have calculated the physical edge capacities for the IP network, you can perform the PQNA analysis. This uses the calculated capacities to test the network and produce results which can be directly compared to the specified requirements. To perform the PQNA analysis, and view the results: 1 2 3 4 From the IP menu, click PQNA. Double-click the required IP Physical group edge. In the dialog box that appears, select the required IP physical edge. Click the QoS tab to view the following values calculated per U,I pair. For more information, see Viewing the Calculated QoS on IP Traffic Edges on page 352.
Page 351
Viewing the Calculated QoS on IP Traffic Edges

In the IP Edge Group dialog box, on the QoS tab for an IP edge, you can view the calculated QoS for the traffic using this IP edge. You van view the values in 3 different states: Requirement - The values set on the Traffic QoS Requirements tab for a traffic service Allocated Requirement - The results of the QoS Requirements Allocation calculations Analysis - The results of the PQNA calculation The following table describes the values that you can view:
Item Max Delay Tail Probability Loss Description The total end-to-end delay for the IP traffic edge. The probability that the buffer will not grow past its limit. The percentage of packets that can be lost.
Page 352
CHAPTER 12
Creating the Lightpath Network

In the Lightpath module (when used in conjunction with the Transmission and Traffic modules), you can route traffic onto lightpaths and route these lightpaths onto the optical transmission edges. The physical optical network is comprised of point-to-point connections and protection rings created in the Transmission module, while the lightpath network provides the logical view of data transport with WDM SPRing protection. This picture shows a conceptual diagram of lightpaths and optical layers.
Conceptual diagram of the lightpath and optical layers
In This Section
Overview of the Lightpath Module About the Lightpath Edge Types Planning the Lightpath Network Editing Lightpath Edge Groups Editing Lightpath Edges 354 355 355 356 357
Page 353
Overview of the Lightpath Module

In the Lightpath module, you can: Create logical lightpath connections between WDM network elements. Set the capacity of the lightpath for 2.5 or 10G. This picture shows an example of defining the capacity on lightpath segments:
Calculate the required number of lightpaths between the WDM elements, based on the traffic requirements from the upper layers. Display traffic routed across the lightpath segment. Set the requirement for protection on the lightpath, so that it will find alternative primary and secondary routes if possible. Provide the path length of the lightpath segment, based on the fibre route set within the Transmission module Property view.
Page 354
About the Lightpath Edge Types

Lightpaths represent the logical transfer of data across an optical network. Lightpath edges are defined on a separate layer so that they can be routed onto optical edges. However, separate lightpath layers based on their technology (such as OC-12, OC-48 and so on) are not needed, since they will not be multiplexed together. Instead this will be performed by the SDH technologies. This table shows the different lightpath data capacities available in the Lightpath module:
Lightpath OC-1 OC-3 OC-12 OC-48 OC-192 OC-768 SONET Signals STS-1 STS-3 STS-12 STS-48 STS-192 STS-768 SDH Equivalent STM-0 STM-1 STM-4 STM-16 STM-64 STM-256 Bit Rates (Mbit/s) 51.84 155.52 622.08 2488.32 9953.28 39812120
Planning the Lightpath Network

If you are new to DIRECT, it is recommended that you follow the work order set out below when planning your first few lightpath networks: 1 2 3 4 5 In the Equipment Editor, ensure that you have created equipment containing optical cards. Open a new Lightpath module. In the Transmission module, add the necessary equipment. The relevant equipment will also appear in the Lightpath module. Edit the General properties of the lightpath equipment. In the Lightpath module, connect the equipment using the required wavelength link type (for example, OC-12). You can connect the equipment manually, or automatically based on transmission segments. 6 7 8 9 Open the ATG, and add the required number of wavelength link edges to each edge group. Configure the properties of the wavelength link edges. Add any WDM SPRing protection that you need. Configure the routing properties of the lightpath nodes and then route the lightpath layer.
Page 355
Editing Lightpath Edge Groups

You can edit an edge group in the lightpath network by changing its properties in the Lightpath EdgeGroups dialog box. To open this: In the Lightpath module view, double-click the required edge group. The Lightpath EdgeGroups dialog box opens.
Lightpath Group Dialog Box
You can edit the properties of a lightpath edge group on four tabs: General tab Edges tab Route Properties tab Routing Properties tab
Page 356
Editing Lightpath Edges

You can edit a segment in the lightpath network by manually changing its properties in the Lightpath EdgeGroups dialog box. To open this dialog box: 1 2 3 Double-click the edge group that contains the lightpath edge. The Lightpath EdgeGroup dialog box opens. Ensure the list of edges is expanded. If it is not, click the plus sign to display all of the edges in the edge group. Double-click the edge that you want to edit. You can now edit the properties of this lightpath edge on the following tabs: General tab Traffic tab Route Properties tab Routing Properties tab
Page 357
Page 358
APPENDIX A
Synchronisation Data
This section describes the data for each object that is synchronised between DIRECT and ENTERPRISE.
In This Section
Synchronising 3g Service Types Synchronising 3g Traffic Types Synchronising Connection Types Synchronising Cell Layer Types Synchronising Properties Synchronising Nodes Synchronising GSM Cellular Links Synchronising Links Synchronising GSM Cells Synchronising GSM Cell Layers Synchronising UMTS Cells Synchronising UMTS Traffic 359 360 360 360 361 361 361 361 362 362 362 362
Synchronising 3g Service Types

The following table summarises the 3g service type data synchronised between ENTERPRISE and DIRECT:
ENTERPRISE Name Name CS Activity Factor ENTERPRISE Location UMTS Services Types dialog box UMTS Services Types dialog box (General tab) UMTS Services Types dialog box (Packet switched tab) DIRECT Name Name Activity Probability DIRECT Location Traffic Types dialog box (Services option, General tab) Traffic Types dialog box (Services option, Voice Parameters tab)
Reading Time Between Calls (seconds)
Average Reading Time Traffic Types dialog box Between Packet Calls (sec) (Services option, NRT Parameters tab) Average Number of Packets Traffic Types dialog box per Call (Services option, NRT Parameters tab) Average Data Packet Length Traffic Types dialog box (Services option, NRT Parameters tab)
Mean # Packets in a Call UMTS Services Types dialog box (Packet switched tab) Mean Packet Size (bytes) UMTS Services Types dialog box (Packet switched tab)
Page 359
Note : 3g Service Types can only be transferred from ENTERPRISE to DIRECT, and not vice versa.
Synchronising 3g Traffic Types

The following table summarises the 3g traffic type data synchronised between ENTERPRISE and DIRECT:
ENTERPRISE Name Name Supported UL Bearer Activity(%) ENTERPRISE Location UMTS Services Types dialog box UMTS Services Types dialog box (UL Bearers tab) UMTS Services Types dialog box (UL Bearers tab) DIRECT Name Name Service Bit Rate DIRECT Location Traffic Types dialog box (Services option, General tab) Traffic Types dialog box (Services option, General tab) Traffic Types dialog box (Services option, General tab)
Note : 3g Traffic Types can only be transferred from ENTERPRISE to DIRECT, and not vice versa.
Synchronising Connection Types

The following table summarises the link type data synchronised between ENTERPRISE and DIRECT:
ENTERPRISE Name ID Comments Manufacturer Number of Fibres, Number of Pairs (depending on type) ENTERPRISE Location Link Types Dialog Box Link Types Dialog Box Link Types Dialog Box Link Types Dialog Box DIRECT Name Name (ID) Comments Manufacturer DIRECT Location Connection Types Dialog Box (General tab) Connection Types Dialog Box (General tab) Connection Types Dialog Box (General tab)
Number of Fibres, Connection Types Dialog Box (Fibre Number of Pairs tab or Twisted Pair tab, depending on (depending on type) type)
Synchronising Cell Layer Types

The following table summarises the cell layer type data synchronised between ENTERPRISE and DIRECT:
ENTERPRISE Name Name ENTERPRISE Location Cell Layer Configuration dialog box (General tab) DIRECT Name Name DIRECT Location Cell Layer Types dialog box (General tab)
Page 360
Synchronising Properties
The following table summarises the Property data synchronised between ENTERPRISE and DIRECT:
ENTERPRISE Name ENTERPRISE Location DIRECT Name DIRECT Location Property ID and Property Site Database (General tab) Code Longitude and Latitude Co-ordinates Property Identification Information Comments Site Database (General tab) Site Database (Contacts tab) Site Database (Search Area) Property ID and Property Code Property Dialog Box (General tab) Longitude and Latitude Coordinates Property Address Information Comments Property Dialog Box (General tab) Property Dialog Box (Address tab) Property Dialog Box (General tab)
Synchronising Nodes
The following table summarises the node data synchronised between ENTERPRISE and DIRECT:
ENTERPRISE Name Name 1st Name 2nd Name Parent Property ID ENTERPRISE Location Site Database (General tab) Site Database (General tab) Site Database (General tab) Site Database (Hierarchy) DIRECT Name ID 1st Name 2nd Name Type DIRECT Location Equipment dialog box (General tab) Equipment dialog box (General tab) Equipment dialog box (General tab) Property dialog box (Equipment Summary tab)
Synchronising GSM Cellular Links

For GSM cellular links, ENTERPRISE and DIRECT synchronise the IDs of the two nodes that are connected by the link.
Synchronising Links
The following table summarises the link data synchronised between ENTERPRISE and DIRECT:
ENTERPRISE Name Link ID, 1 Name, 2 Name
st nd
ENTERPRISE Location Link Database (General tab, Info subtab) Link Database (General tab, Type subtab)
DIRECT Name Name ID Type
DIRECT Location Connection dialog box (General tab) Connection Group dialog box (Details tab) Connection dialog box (Radio tab)
Type Band and Channel
Link Database (Linkend Settings tab, Frequency Band and Channel Frequency subtab)
Page 361
Synchronising GSM Cells

The following table summarises the GSM cell data synchronised between ENTERPRISE and DIRECT:
ENTERPRISE Name Identity Parent BTS ID ENTERPRISE Location Site Database (General tab) Site Database (Hierarchy) DIRECT Name Cell ID DIRECT Location (BTS)Equipment dialog box (BTS tab) (BTS)Equipment dialog box (General tab)
Synchronising GSM Cell Layers

The following table summarises the GSM cell layer data synchronised between ENTERPRISE and DIRECT:
ENTERPRISE Name SubCell ID Cell Layer Type Total TRX Reqd ENTERPRISE Location Site Database (General tab) Site Database (Hierarchy) Site Database (Carriers tab) DIRECT Name Cell Layer Cell Layer Type Trx Count DIRECT Location (BTS)Equipment dialog box (BTS tab) (BTS)Equipment dialog box (BTS tab) (BTS)Equipment dialog box (BTS tab)
Important : You can only transfer the Cell Layer Type and Total TRX Reqd values from ENTERPRISE to DIRECT, and not vice versa.
Synchronising UMTS Cells

The following table summarises the GSM cell data synchronised between ENTERPRISE and DIRECT:
ENTERPRISE Name Identity Parent BTS ID ENTERPRISE Location Site Database (General tab) Site Database (Hierarchy) DIRECT Name Cell ID DIRECT Location (BTS)Equipment dialog box (BTS tab) (BTS)Equipment dialog box (General tab)
Synchronising UMTS Traffic

The following table summarises the UMTS traffic data synchronised between ENTERPRISE and DIRECT:
ENTERPRISE Name Type SD ENTERPRISE Location Site Database (Sim Traffic tab) Site Database (Sim Traffic tab) DIRECT Name UpLink Type and Downlink Type All Subs DIRECT Location Equipment dialog box (Node B User Plane tab) Equipment dialog box (Node B User Plane tab)
Page 362
Important : You can only transfer the UMTS traffic values from ENTERPRISE to DIRECT, and not vice versa.
Page 363
Page 364
APPENDIX B
About DIRECT Network Labels

As you plan your network using DIRECT, you can display a variety of information related to your different network views, by using network labels. Network labels can be used for nodes, segments (edges) or sites. For example, this picture shows a traffic network view, where the edge labels are used to display the traffic load in kbits per second.
Traffic module edge labels showing traffic load in kbit/s
All modules use some generic labels for Properties and cabinets, and most modules have their own labels for edge groups. You can add network labels in a number of modules.
In This Section
Generic Module Labels Transmission Module Labels Traffic Module Labels SDH/SONET and PDH Module Labels ATM Module Labels IP Module Labels Lightpath Module Labels 366 366 367 368 368 369 369
Page 365
Generic Module Labels

All or most of the modules use the equipment, cabinet and Property labels. The following tables describe these labels. Equipment Labels
This Label No Label Equipment ID First Equipment Name Second Equipment Name Displays Nothing the equipment is left blank. The identification code of the equipment. The first additional name for the equipment. The second additional name for the equipment.
Cabinet Labels
This Label No Label Cabinet ID Displays Nothing the cabinet is left blank. The identification code of the cabinet.
Property Labels
This Label No Label Property ID Displays Nothing the Property is left blank. The identification code of the Property.
Transmission Module Labels

In the Transmission module, you can use the following labels to display information about edge groups, conduits and detail edge groups: Edge Group Labels
This Label No Label All Labels Edge Count Edge Name Edge Load Media Count Displays Nothing the edge group is left blank. All of the labels listed below. The number of edges on the edge group. The name of the edge group. The traffic load on the edge group. The number of media that are used by the edge group.
Conduit Group Labels

This Label No Label All Labels Conduit Name Displays Nothing the conduit group is left blank. All of the labels listed below. The name of the conduit.
Page 366
This Label Segment Count Media Count
Displays The number of segments that are contained in the conduit. The number of media that are used by the conduit group.
Detail Edge Group Labels

This Label No Label All Labels Edge Name Edge Load Traffic Utilisation Displays The name of the detail edge group. All of the labels listed below. The name of the detail edge group. The traffic load on the detail edge group, in kbs. The percentage of the edge used for traffic.
Traffic Module Labels

In the Traffic module, you can use the following labels to display information about edge groups: Edge Group Labels
This Label No Label All labels Edge Name Edge Type Edge Load (kbps) Edge Load (Erl, Actual) Edge Load (Erl, Forecasted) Edge Load (64k TCH, Actual) Edge Load (64k TCH, Forecasted) Edge Load (2Mb TCH, Actual) Edge Load (2Mb TCH, Forecasted) Edge Load (0 Link Fault) Edge Load (1 Link Fault) Edge Load (1 Node Fault) Displays Nothing the edge is left blank. All of the labels listed below. The name of the edge group. The type of the edge group. The traffic load on the edge group (in Kbits per second) The actual traffic load on the edge group (in Erlangs) The forecasted traffic load on the edge group (in Erlangs) The actual traffic load on the edge group (in 64kbit traffic channels) The forecasted traffic load on the edge group (in 64kbit traffic channels) The actual traffic load on the edge group (in 2Mb traffic channels) The forecasted traffic load on the edge group (in 2Mb traffic channels) The traffic load for the edge group in the case of 0 link faults. The traffic load for the edge group in the case of 1 link fault. The traffic load for the edge group in the case of 1 node fault.
Page 367
SDH/SONET and PDH Module Labels

In the SDH/SONET and PDH modules, you can use the following labels to display information about edge groups: Edge Group Labels
This Label No Label All Labels Edge Count Edge Name Edge Type Edge Load Edge Capacity Edge Fill Ratio Displays Nothing the edge group is left blank. All of the labels listed below. The number of edges on this edge group. The name of the edge group. The type of edge in the edge group. The traffic load on the edge group. The traffic capacity on the edge group. The load/capacity ratio on the edge group.
ATM Module Labels

In the ATM module, you can use the following labels to display information about edge groups: Edge Group Labels
This Label No Label All Labels Edge Count Edge Name Edge Type Edge Load Displays Nothing the edge group is left blank. All of the edges listed below. The number of edges in the edge group. The name of the edge group. The type of edge in the edge group. The traffic load on the edge group.
Page 368
IP Module Labels
In the IP module, you can use the following labels to display information about edge groups: Edge Group Labels
This Label No Label All Labels Edge Count Edge Name Edge Type Edge Load Displays Nothing the edge group is left blank. All of the labels listed below. The number of edges in the edge group. The name of the edge group. The type of edge in the edge group. The traffic load on the edge group.
Lightpath Module Labels

In the Lightpath module, you can use the following labels to display information about edge groups: Edge Group Labels
This Label No Label All Labels Edge Count Edge Name Edge Type Edge Load Displays Nothing the edge group is left blank. All of the labels listed below. The number of edges in the edge group. The name of the edge group. The type of edge in the edge group. The traffic load on the edge group.
Page 369
Page 370
APPENDIX C
About the Traffic Utilisation Calculations

This section describes the calculations performed in DIRECT in order to model traffic utilisation.
In This Section
Traffic Utilisation Calculations Circuit Utilisation Calculations Channel Utilisation Calculations 371 372 374
Traffic Utilisation Calculations

To calculate traffic utilisation, DIRECT uses the following equation: Traffic Utilisation (%) = (Traffic Load/Max Payload)*100% Where: Traffic load is the amount of traffic transported by the traffic element Maximum payload is equal to the total bit rate for ATM traffic elements, but for PDH/SDH traffic elements the overheads are subtracted. This table describes the maximum payloads:
Module PDH Layer 64k/E0 2M/E1 Max Payload (kbps) 64 2048 Comments The traffic load routed on the 64k channel from the layer above. Based on the traffic load, and any reserved traffic channels in kbps. E1 load is taken from the 2M routed onto it. Total load allowed on to 8M structured. E2 load is taken from the 8M routed onto it. 34M/E3 32768 Total load allowed on to 34M structured. E3 load is taken from the 34M routed onto it. n x 2M/E1 n x 2048 The value is taken from the edge type. The physical n x E1 takes its load from the logical connection routed onto it.
8M/E2
8192
Page 371
Module SDH
Layer VC1.1/VC2 VC2 (TUG-2) VC3 (TUG-3)
Max Payload (kbps) 1544/2048 3 x 2048 or 4 x 1544 21 x 2048 or 28 x 1544
Comments Maximum traffic load of these layers, as defined by the ITU. Based on the traffic routed onto the edge. Based on whether the edge is SONET or SDH. If a full 34M load is added to the VC3, then this is taken as 21 x VC1.2 or 28 x VC1.1 accordingly.
VC4/STM1 (AUG)
63 x 2048
The VC4 is shown as a percentage, based on the number of VC1.2 channels available. For example, if a VC4 is filled with 1 VC3 and 21 x VC1.2 then this is equal to VC3 (21 x VC1.2 equivalents) + 12 x VC1.2, so the load is 42 x VC1.2 equivalents. This is calculated as (42/63)*100 = 66.67%. STM-1 load is taken from the VC4 routed onto it.
VC4-4c/STM-4 4 x 63 x 2048 (AUG-4)
4 x VC4 channels can be utilized on the edges, so the utilisation will increase in 25% increments. STM-16 load is taken from the VC4s loaded onto it. If a VC4-4c has been loaded onto it, it is regarded as 100% full.
VC-416c/STM-16 (AUG-16)
16 x 63 x 2048
16 x VC4 channels can be utilized on the edges, so the utilisation will increase in 6.25% increments. If a VC4-16c has been loaded onto it, it is regarded as 100% full.
Note : The same methodology is applied to the corresponding ANSI and Japanese standards.
Circuit Utilisation Calculations

To calculate circuit utilisation, DIRECT uses the following equation: Circuit Utilisation (%) = (Traffic Load in Channels/Max Payload in Channels)*100% Where the traffic load in channels and maximum payload in channels are measured based on one particular layer above. Note : For 64k/E0, bit rates are taken instead, and for VC1.2/VC1.1, the circuit utilisation is either 0% or 100%. This table describes the traffic load limits for each layer:
Module PDH Layer 64k/E0 2M/E1 Traffic Load (Channels) Up to 64k Up to 32 channels Measured in 64k channels 8M/E2 Measured in 2M channels Comments The traffic load routed on the 64k channel from the layer above. Calculated based on the number of 64k channels used, either fully or partially occupied by the traffic routed onto it. E1 load is taken from the 2M routed onto it. A maximum of 4 x 2M channels can be utilized on the edges, so the utilisation will increase in 25% increments. E2 load is taken from the 8M routed onto it.
Page 372
Module
Layer 34M/E3
Traffic Load (Channels) Measured in 8M channels
Comments A maximum of 4 x 8M channels can be utilized on the edges, so the utilisation will increase in 25% increments. E2 load is taken from the 34M routed onto it.
N x 2M/E1
Measured in 2M channels
Taken as the number of 2M links partially or fully utilised. Physical N x E1 takes its load from the logical connection routed onto it.
SDH
VC1.1/VC1.2 Measured in 1.5M/2M (in use or not) VC2 (TUG-2) Measured in VC1.2 Measured in VC1.1 VC3 (TUG-3) Measured in VC1.2 Measured in VC1.1 VC4/STM-1 (AUG) Measured in VC1.2 Measured in VC1.1
Maximum traffic load of these layers, as defined by the ITU. Based on the traffic routed onto the edge.
Based on whether the edge is SONET or SDH. If a full 34M load is added to the VC3, then this is taken as 21 x VC1.2 or 28 x VC1.1 accordingly. The VC4 is shown as a percentage, based on the number of VC1.2 channels available. For example, if a VC4 is filled with 1 VC3 and 21 x VC1.2 then this is equal to VC3 (21 x VC1.2 equivalents) + 12 x VC1.2, so the load is 42 x VC1.2 equivalents. This is calculated as (42/63)*100 = 66.67%. STM-1 load is taken from the VC4 routed onto it.
VC44c/STM-4 (AUG-4)
Measured in VC-4
A maximum of 4 x VC4 channels can be utilised on the edges, so the utilisation will increase in 25% increments. STM-16 load is taken from the VC4s loaded onto it. If a VC4-4c has been loaded onto it, it is regarded as 100% full.
VC416c/STM-16 (AUG-16)
Measured in VC-4
A maximum of 16 x VC4 channels can be utilised on the edges, so the utilisation will increase in 6.25% increments. If a VC4-16c has been loaded onto it, it is regarded as 100% full.
Note : The same methodology is applied to the corresponding ANSI and Japanese standards. This table shows the maximum payloads for each layer:
Module PDH Layer 64k/E0 2M/E1 8M/E2 34M/E3 N x 2M/E1 SDH Maximum Payload 64k N x 64k channels 4 x 2M 4 x 8M N x 2M/E1 Default payload is 32 channels. This will always be a 4 x 2M payload, therefore the utilisation will increase in 25% increments. This will always be a 4 x 8M payload, therefore the utilisation will increase in 25% increments. Dependent on the number of channels in use. Maximum payload of these layers, as defined by the ITU. Comments
VC1.1/VC1.2 1.5/2M
VC2 (TUG-2) 3 x VC1.2 or 4 x VC1.1 Based on the traffic routed onto the edge. VC3 (TUG-3) 21 x VC1.2 or 28 x VC1.1 Based on whether the edge is SONET or SDH. If a full 34M load is added to the VC3, then this is taken as 21 x VC1.2 equivalents or 28 x VC1.1 equivalents accordingly.
Page 373
VC4/STM-1 (AUG) VC44c/STM-4 (AUG-4) VC416c/STM-16 (AUG-16)
63 x VC1.2 or 84 x VC1.1 4 x VC4
Based on whether the edge is SONET or SDH. 4 x VC4 channels can be utilised on the edges, so the utilisation will increase in 25% increments. 16 x VC4 channels can be utilised on the edges, so the utilisation will increase in 6.25% increments. If a VC4-16c has been loaded onto it, it is regarded as 100% full.
16 x VC4
Channel Utilisation Calculations

The circuit utilisation calculations provide information about the number of channels used compared to the maximum channels available as a percentage. However, you can use the channel utilisation calculation to work out the exact number of channels and the maximum payload in traffic channels separately. This table describes the calculations:
Module PDH Layer 64k/E0 2M/E1 8M/E2 34M/E3 N x 2M/E1 SDH VC1.1/VC1.2 VC2 (TUG-2) Maximum Payload in channels 64k N x 64k channels 4 x 2M 4 x 8M N x 2M/E1 1.5/2M 3 x VC1.2 or 4 x VC1.1 Comments Not applicable Maximum number of channels is 32. Maximum number of channels is 4. Maximum number of channels is 4. Dependant on the number of channels in use. Maximum number of channels is 1, in use or not. The maximum numbers of channels are 3 x VC1.2 for SDH or 4 x VC1.1 for SONET, based on the traffic routed onto the edge. The maximum numbers of channels are 21 x VC1.2 for SDH or 28 x VC1.1 for SONET. The maximum numbers of channels are 63 x VC1.2 for SDH or 84 x VC1.1 for US standard edge. 4 x VC4 channels. 16 x VC4 channels.
VC3 (TUG-3)
21 x VC1.2 or 28 x VC1.1
VC4/STM-1 VC4-4c/STM-4 (AUG-4) VC4-16c/STM-16 (AUG-16)
63 x VC1.2 or 84 x VC1.1 4 x VC4 16 x VC4
Page 374
Glossary of Terms
3GPP Third Generation Partnership Project. A group of previously separate telecommunication standards bodies, responsible for producing technical specifications for 3g systems and maintaining GSM standards.
A
AAL ATM Adaptation Layer. User data is compartmentalised into separate segments (or AALs), which can be packaged into ATM cells. The first segment (or AAL1) is usually reserved for traffic with a constant bit rate (for example voice and real time video), while the fifth segment (or AAL5) is usually reserved for traffic with a variable bit rate (for example 'bursty' LAN data). ABR Available Bit Rate. Supports VBR traffic with average and peak traffic parameters - it is best-effort, and does not guarantee any level of CLR or CDV. Typically used for connections that do not require timing relationships between the source and the destination, for example distributed file services or remote procedure calls. ADM Add/Drop Multiplexer. A piece of equipment used in SDH/SONET networks to add and remove signal components without having to demultiplex the entire transmission stream. It works by converting lower-level signals (for example T-1 or E-1) to/from the optical carrier levels. ANSI American National Standards Institute. An ISO-affiliated organisation responsible for standards within the telecommunications industry, for things such as transmission protocols and media. ETSI is the European equivalent. ATG Automatic Topology Generator. You can use the ATG tab in DIRECT to create your network topology automatically.
ATM Asynchronous Transfer Mode. This is a method of switching and multiplexing voice, data, image and video traffic, based on transporting cells containing 53 octets of data each. It is a fast packet technology, and can operate with low error rates, low costs but at high speeds, and provide a measurable QoS. AXC ATM Cross Connect.
B
BH Busy Hour. Defined as the 60-minute period of the 24-hour time frame containing the largest amount of network traffic. BSC Base Station Controller. A piece of equipment that controls one or more BTS (Base Station Transceivers). BTS Base Transceiver Station.
C
CAC Connection Admission Control. An ATM procedure, used to ensure that data for a network connection meets the agreement between customer and network provider. CBR Constant Bit Rate. Provides a guaranteed rate to RT applications such as video and speech, providing continuous bandwidth. This is the highest ATM service class. CDV Cell Delay Variation. The acceptable time difference between cells arriving at the receiver. CLR Cell Loss Ratio. The total number of lost cells divided by the total number of transmitted cells. This is usually an objective specified over the lifetime of a connection.
Page 376
CoS Class of Service. A means of categorising traffic/subscribers based on priority levels; the greater the CoS, the more resources that are allocated. CSMGW Circuit-Switched Media GateWay. CTD Cell Transfer Delay. The elapsed time between a cell exit event at the source and destination for a particular connection. The CTD is the sum of the total inter-ATM node transmission delay and the total ATM node processing delay.
D
DIAA Dispatcher Interface Audio Adaptors. Along with DWSs and related voice communications equipment, DIAAs are used to create DSCs. DSC Dispatcher System Controller. DSCs are used to manage and communicate within the TETRA network. They contain 1 to 6 Dispatcher Workstations (DWS) with Dispatcher Interface Audio Adaptors (DIAAs), as well as related voice communications equipment. DWDM Dense Wavelength Division Multiplexing. This effectively creates multiple optical fibres from a fibre, by combining and transmitting multiple signals at different wavelengths on the same fibre. In this way, bandwidth can be increased. Such a system typically operates in the L-band (1625 nm), using channels spaced 50-100 GHz apart. DWS Dispatcher WorkStation. A piece of equipment used in DSCs. DXT Digital Exchange for TETRA. A piece of equipment primarily used as a switching element between TBSs. DXTc Central Digital Exchange for TETRA. Similar to DXTs, but with different capacity limits and support for up to 32 inter-exchange signalling links.
Page 377
E
EDAP Enhanced Dynamic Abis Pool. You can use the EDAP pool to reduce the required number of timeslots on the Abis frame reserved for EGPRS data. ETSI European Telecommunication Standards Institute. An organisation responsible for telecoms standards. ANSI is the US equivalent.
F
FDMA Frequency Division Multiple Access. A technique used in analogue AMPS cellular systems, in which each user is designated a different frequency.
G
GPRS General Packet Radio Service. This is a non-voice service, which allows you to send and receive data across a mobile telephone network via GSM telephones. The typical data transmission rate is 20-30 Kbps, and there is continuous connection to the network. GSM Global System for Mobile Communications. A global 2g wireless digital communications standard covering cellular telephony, two-way radio and paging, and short messaging. It is a TDM system, operating on 3 frequency bands - GSM 900 (900 MHz), DCS 1800 (1.8 GHz) and PCS 1900 (1.9 GHz). GTM General Traffic Model. You can use this model to define the properties of traffic services in detail.
H
HLR Home Location Register. A database that provides routing information for MT calls and SMS, and maintains subscription data. It distributes this data to the relevant VLR or SGSN.
Page 378
HSCSD High-Speed Circuit-Switched Data. A high-speed technology that allows data to be sent and retrieved over GSM networks at a rate of 14.4 (1 timeslot), 28.8 (2 timeslots), or 57.6 Kbps (4 timeslots).
I
IMA Inverse Multiplexing over ATM. This protocol allows the grouping of multiple E1 links, creating a combined bandwidth. IMSI International Mobile Subscriber Identity. A unique number (comprised of an MCC, MNC and an MSIN) that identifies each mobile subscriber in a GSM and UMTS network. INAP Intelligent Network Application Part. A protocol which can provide communication between IN (Intelligent Network) elements. IP Internet Protocol. This defines the format for all data travelling through a TCP/IP network, performs the routing functions and provides a mechanism for processing unreliable data. ISUP-TUP ISDN User Part-Telephone User Part. ISUP is part of the SS7 protocol layer and is used to configure, manage and release trunks carrying voice and data. TUP was an earlier version, without support for data type applications. ISW Interswitch. Can refer to interswitch traffic or the interswitch layer. DIRECT models interswitch traffic in the Traffic module. IWF InterWorking Function. A piece of equipment containing rate adapters, modems and fax adapters. When connecting a cellular network to a PSTN, IWFs are used to provide switched data services.
M
MO Mobile Originated. Refers to any communication starting at the mobile.
MSC Mobile Switching Centre. In a cellular network, this is a switch or exchange that interworks with location databases. MT Mobile Terminated. Refers to any communication ending at the mobile. MTP Message Transfer Part. A component of the SS7 protocol stack, providing routing within a network. MUX Multiplexer. A piece of equipment which combines a number of inputs and transmits them over a single high-speed channel, to be demultiplexed at the other end. By using a MUX, you can reduce the requirement for additional transmission facilities.
N
NBAP-D Node B Application Part. An application protocol for Node Bs and RNCs. NRT Non-Real Time. Non-real time traffic is that which does not have to be received within any specified time limit. An example is IP traffic, like an image via email or web. The opposite is Real Time (RT), where the reception of the traffic is time-bound for example, voice.
P
PABX Private Automatic Branch Exchange. Sometimes known as just PBX (Private Branch Exchange), this is a telephone switch based on a company's premises, which transmits calls between individual users (extensions) and the public telephone network. It also provides switching internally (between extensions) and other services like call-detail recording. PDH Plesiosynchronous Digital Hierarchy. Plesiosynchronous means almost synchronised, and so PDH differs from SDH in that it accounts for how different traffic sources can lead to slightly different phase characteristics. PDH is implemented across the world, according to 3 standards - T-carrier (North America), E-carrier (ITU-T countries), Jcarrier (Japan).
Page 380
POI Point of Interconnection. This is usually a preferred external node used with network switch nodes (for example, MSCs). POTS Plain Old Telephone Service. A general term for the regular 'household' analogue telephone service. It does not include more advanced services like Call Waiting or Call Forwarding. PSTN Public Switched Telephone Network. This is the traditional public telephone system, comprised of telephones, local and interexchange trunks, transport equipment and exchanges.
Q
QoS Quality of Service. A performance requirement that is defined prior to the transmission of data. Depending on the network type, it can be measured in terms of bit error rate, cell loss ratio, cell transfer delay and so on.
R
RAN Radio Access Network. The connection to the core network, providing the radio functionality. A typical RAN is made up of a controller (such as an RNC or BSC) and a number of transmitting/receiving elements (such as Node Bs or BTSs). RANAP Radio Access Network Application Part. A protocol used in a UMTS system on the Iu interface. It is used to set up a bearer between a core network and an RNC. RNC Radio Network Controller. RNSAP Radio Network Subsystem Application Part. A protocol used for signalling traffic on the Iur interface in a UMTS system.
Page 381
RTP Real-Time Transport Protocol. An internet protocol used to transmit RT multimedia data, such as video and audio. It can be used to send and receive applications to support streaming data as it is received, but cannot provide RT delivery of data in itself.
S
SAP Service Access Point. A virtual point at which one protocol layer makes its services available to another protocol layer (either above or below). SCCP Signalling Connection Control Part. This is used to transfer messages between two signalling points in the same or different SS7 networks. SDH Synchronous Digital Hierarchy. An ITU-T standard for digital broadband communications, used to transmit digital information in time-synchronised containers. This allows relatively simple modulation and demodulation of the optical signals at the transmitting and receiving end, and can be used to carry high capacity information over long distances. SGSN Serving GPRS Support Node. A piece of equipment that monitors an MS and performs security functions and access control. It can also be used in a UMTS network to connect an RNC over the Iu-PS interface. SMS Short Message Service. The text messaging system, enabling messages to be sent to/from GSM phones and to external systems (for example, email or voicemail). Messages that cannot be delivered straight away (due to the receiver's mobile being switched off or out of range) are stored, and delivered as soon as possible. SONET Synchronous Optical Network. This is a US multiplexing standard for defining a line rate hierarchy and the frame formats for high-speed (50.84 Mbps to 2.488 Gbps) optical fibre transmissions systems. The European equivalent is SDH.
Page 382
SPF Shortest Path First. A type of routing, based on the Dijkstra Shortest Path First algorithm. This method defines the length of a path as the sum of all of the edge weights along it, and then finds the shortest (in other words, lowest total weight) path between two endpoints. STM Synchronous Transmission Module. A basic building block of SDH networks. The first level, STM-1,has 9 rows of 270 bytes, the first 9 columns of which contain section and line overhead for the STS-3s. The remaining 261 columns contain the combined capacity of the STS-1s. The rates for basic STM levels are 155Mbps (STM-1), 622Mbps (STM-4), 2.5Gbps (STM-16) and 10Gbps (STM-64). STP Signalling Transfer Point. A switch responsible for translating SS7 messages, and then routing them between network nodes and databases. STS Synchronous Transport Signal. A basic building block of SONET network. The basic signalling rate is STS-1, at 51.8 million bits per second. Other STS rates are STS-3, STS12, STS-48, STS-192 and STS-768. STS is the electrical equivalent of OC.
T
TBC TETRA Base Station Controller. Along with a TRUA, cabinet and cabling, a TBC forms a TBS. TBS TETRA Base Station. Consists of a TBC, a TRUA, a cabinet and cabling. Each cabinet can hold up to 4 carriers (16 channels or timeslots), and have an extension cabinet of up to 4 more carriers. TCAP Transaction Capabilities Applications Part. Enables the exchange of noncircuit-related information between different signalling points/nodes, by using the SCCP connectionless service. TCH Traffic channel. This is a logical channel used to transport data.
Page 383
TDMA Time Division Multiple Access. In this technique, multiple users can be carried along one channel, each one using a different timeslot. TETRA Terrestrial Trunked Radio. A digital cellular land mobile radio system used in Europe. Uses portable, mobile, base station, and dispatch console radios. Typical examples are the radio systems used by police forces and fire brigades. The technology is similar to Tetrapol and iDEN. TRUA Transmission Unit. Along with a TBC, cabinet and cabling, a TRUA forms a TBS. TTI Transmission Time Interval. The inter-arrival time of a transport block set, as it is transferred by the physical layer on the radio interface. TUG Tributary Unit Group.
U
UBR Unspecified Bit Rate. A best effort service with no guaranteed CLR or CDV. Typically used for non-time-critical data, such as text data or image transfer. UMTS Universal Mobile Telecommunications System. A 3g mobile telecommunications standard, which can deliver broadband data at speeds of 2Mbps. A defining feature of the UMTS standard is the support for different services such as Voice, Internet and Video.
V
VBR Variable Bit Rate. A rate that is varied (unlike CBR), which is used for 'bursty' or NRT data applications, but offers guaranteed service delivery.
Page 384
VCC Virtual Circuit Connection. A virtual circuit is a circuit or path between points in a network where ATM users access the ATM layer. Rather than a single path, a VCC is actually a group of circuits from which specific circuits are selected and allocated as required by the specific traffic demands. VCI Virtual Channel Identifier. Part of a cell header in the ATM that identifies the virtual channel associated with the cell. The VCIs may be different for each data link hop of an ATM virtual connection. VLR Visitor Location Register. A temporary database storing information on the mobile subscribers within the VLR's specific area. This data is used to handle calls and manage the subscribers' mobility. VPC Virtual Path Connection. A unidirectional group of virtual path links between VPTs. They are identified using Virtual Path Identifiers. VPI Virtual Path Identifier. Part of a cell header in the ATM that identifies the virtual path associated with the cell. Virtual paths are used to manage groups of virtual channels as if they were a single channel. VPT Virtual Path Terminator. A system that divides the VCs within a VP, so that they can be processed individually.
X
XC Cross Connect. A piece of equipment used to patch between two groups of cables (for example, horizontal to backbone).
Page 385
Page 386
Index
2
2G parameters, editing 157
3
3g parameters, editing 158 3GPP networks 3GPP networks using IWFs 224 creating 224
Assigning Properties and pits 103 served external networks 185 timeslot allocation templates 305 Assisted routing, using 263 ATM module about 41 calculating capacity 312 labels 368 numbering VCIs 324, 325 planning 308 service categories 324 toolbar 42 view window 41 viewing paths 308 ATM parameters AALT 112 ATM AXC 112 editing 310 WAM 112 ATM paths displaying 308 viewing 308 ATM services, categories 324 Automatic routing, using 255
A
AAL edges editing 334 editing groups 333 setting the layer 333 viewing QoS 335 AAL1/CBR VCCs, editing 328 AAL2/CBR VCCs, editing 328 AAL5/CBR VCCs, editing 328 AAL5/UBR VCCs, editing 328 A-bis interface, dimensioning 295 Access networks, planning 91 Adding BTS traffic 177 conduit pits 144 conduits 145 detail edge preferences 64 edge groups 71 edge preferences 65 edges 73 edges to an edge group 90 equipment 46, 68 external networks 164 module view windows 47, 66, 67 modules 66 nodes 68 pits 144 Properties 144 service types 172 supported services 190 traffic services 172 traffic to Node Bs 180 VCCs to a VCC group 327 VPCs 330 Allocating subscribers on SMSCs 181 timeslots 288, 295, 296, 298 timeslots in a template 299 timeslots with templates 305
B
Balanced capacity routing, about 248 Balanced fill ratio routing, about 249 BSC networks, planning 91 BSC parameters, editing 110 BSC traffic editing 177 viewing 177 BTSs adding traffic 177 parameters 157, 177
C
Cabinets creating 115, 120 creating templates 120 displaying 81 editing 146 hyperlinks 147 showing and hiding 81 Capacity calculating ATM 312 calculating IP 350 reserving 303 Cellular traffic parameters, editing 157 Channels reserving 290, 304 Class of Service, requirements 175 Coaxial connections, editing 139 Codecs assigning usage 181 conversion rules 164 viewing distribution 211 Committing changes 101, 102 networks 47 Compatibility, between connections and conduits 76 Conduit diverse routing, about 251
Page 387
Conduit pits adding 144 regions 103 Conduits about 145 adding 145 committing 101 compatibility with connection groups 76 editing 148 viewing 148 Configurations, equipment 134 Configuring 3GPP networks 224 plan preferences 61 Pre-pay networks 238 TETRA networks 225 Connection groups, compatibility with conduits 76 Connection types, adding 138 Connections adding cross connections 135 compatibility with conduits 76 creating network topologies with 87 defining 71 detail equipment 150 editing coaxial 139 editing leased line 140 editing optical fibre 139 editing PDH 302 editing radio 140 editing satellite 140 editing twisted pair 139 types 138 viewing MGW served 197 viewing SGSN-3g served 197 viewing usage 137 viewing WMSC served 197 Co-ordinates setting 79 Copying edges 90 equipment 70 CoS requirements, editing 175 Costs Costs, editing equipment 135 Creating 3GPP networks 224 cabinet templates 120 logical equipment 109, 110, 111 MS-SPring protection 281 network topologies 87 PDH network 289 PDH protection loops 295 Pre-pay networks 238 routing summary reports 267 subrack templates 121 TETRA networks 225 timeslot allocation templates 298 transmission networks 127 Cross connections creating 135 viewing 70 Customising, module view window 77
Defining connections 71 equipment parameters 110 IMA groupings 332 interswitch traffic 187, 219 Points of Interconnection 188 ports 118 routes for traffic 263 timeslot allocation templates 298 Delay budgets, defining 175 Delay parameters editing 332 viewing 329, 332 Deleting edges 268 equipment 70 module view windows 67 modules 47, 66, 102 Detail edges, setting how they are added 64 Detail equipment connecting 150 editing 151 viewing 151 Detail view creating 149 Detail view, using 149 Detailed capacity routing, about 250 Dimensioning, A-bis interface 295 DIRECT about getting started 51 about the modules 53 DIRECT data exporting 91 importing 91 Dispatcher Work Stations, adding 191 Display customising 77 editing 77 Displaying ATM paths 308 cabinets 81, 86 edges 65, 81, 82 preferences 65 Properties 81, 86 regions 104 routes 65 selected items 65 separate edges 81 Distributing IP addresses 346, 348 traffic across a VCC group 328 Double path routing about 245 example 246 DSCs, setting DWSs 191 DSWs, setting 191 Duplicating, edges 90 DXT networks, planning 91
E
EDAP pools creating 185 deleting 185 editing 185 Edge group properties
D
Data categories, importing and exporting 93
Page 388
editing 76 viewing 76 Edge groups adding 71 adding edges to 73, 90 committing 101 displaying 81 editing 77 hyperlinks 142 viewing 77 viewing properties 76 Edge properties editing 76 viewing 76 EDGE traffic, EDAP pools 185 Edges adding to an edge group 90 adding to edge groups 73 arranging 81 calculating signalling faults 215 committing 101 copying 90 deleting 268 display preferences 65 displaying 81, 82 displaying separately 81 duplicating 90 editing 138, 141 editing AAL 334 editing lightpath 357 editing PDH 302 hyperlinks 142 preferences 64 setting IP overheads 351 setting type 65 types 65 viewing properties 76 Editing 2g parameters 157 3g parameters 158 AAL1/CBR VCCs 328 AAL2/CBR VCCs 328 AAL5/CBR VCCs 328 AAL5/UBR VCCs 328 ATM parameters 310 BSC traffic properties 177 BTS parameters 157, 177 cabinets 146 cellular traffic parameters 157 coaxial connections 139 conduits 148 delay parameters 332 detail equipment 151 display 77 edge group properties 76 edge groups 77 edge properties 76 edges 138, 141 equipment 46, 70, 122, 133, 147 equipment costs 135 equipment properties 69 Global VLR parameters 168 globally 122 interswitch node parameters 192 interswitch routing strategies 162 interswitch traffic parameters 161, 192
leased line connections 140 lightpath edges 357 MSC traffic 193 node properties 69 optical fibre connections 139 PDH connections 302 PDH edges 302 physical details of segment groups 141 Properties 146 protection loops 283 PSTN traffic 159 PSTN traffic properties 194 radio connections 140 RNC user plane traffic 194 routing parameters 253 satellite connections 140 segment groups 140 signalling traffic parameters 167 TETRA traffic parameters 160 traffic services 173 traffic types 176 twisted pair connections 139 VCC group properties 326 VCCs in a group 327 VPC groups 330 VPCs 330 VPTs 332 EGPRS Traffic, viewing results 196 ENTERPRISE synchronising with 54 Equipment about 107 adding 46, 68, 105 aligning 80 arranging 79 assigning codec usage 181 committing 101 configuring 109, 111, 115, 122 connecting 71 connecting detail ports 150 copying 70 creating 109, 110, 111, 115 creation work order 108 cutting and pasting 70 deleting 70 editing 46, 70, 122, 133, 147 editing costs 135 hyperlinks 136, 147 locating 78, 125 logical 46, 110, 112 moving 79, 80 parameters 110, 112 passive 120 PDH 113 physical 115 removing 70 SDH 114 searching 125 setting how it is added 62 slots 119 viewing 124, 133 viewing configuration 134 viewing connection usage 137 viewing cross connections 70 viewing properties 69 Equipment Browser
Page 389
opening 124 viewing equipment in 124 Equipment Editor, about 46 Equipment properties editing 69 viewing 69 Equipment types, creating 109, 111, 115 Exporting data categories 93 DIRECT data 91 External networks, assigning 185
viewing QoS 352
J
J-KLM numbering, about 277
L
Labels about 365 ATM 368 cabinet 365 equipment 365 IP 369 lightpath 369 PDH 368 Property 365 SDH 368 traffic 365 transmission 366 Leased line connections, editing 140 Lightpath edges, editing 357 Lightpath module about 45 data types 355 labels 369 toolbar 45 view window 45 Locating equipment 78, 125 network elements 78 nodes 78 Logical Logical equipment 46, 109, 110, 111, 112 Loops about MS-SPring 280 creating PDH protection 295 protection 268 viewing 283 viewing protection edges 283
F
Filters Filters module views 67 Frames, PDH edges 304
G
General Traffic Model, using 174 Generating interswitch traffic 220 network topologies 87 signalling traffic 213 Global VLR parameters, editing 168
H
Hiding Cabinets 86 Properties 86 regions 104 Hyperlinks cabinets 147 edges 142 equipment 136, 147 Properties 147
I
IMA groupings defining 332 setting 332 Importing data categories 93 DIRECT data 91 Interswitch networks, adding external networks to 164 Interswitch node parameters, editing 192 Interswitch traffic defining 187, 218 generating 217, 220, 223 Interswitch traffic editing 209 model 223 parameters 161, 192 IP addresses distributing 346 distribution types 348 IP module about 337, 339 distributing addresses 346 labels 369 planning 339
M
Manual routing, using 259 Module windows adding 47, 66, 67 ATM 41 customising display 77 deleting 67 IP 337 Lightpath 45 Module windows creating based on routes 87 filtering 67 PDH 38, 285 SDH 36 selecting items 77 Traffic 28 Transmission 24 Transmission module 128 Transmission module detail view 149 Transmission module Property view 143 viewing 68 viewing routes 265 Modules
Page 390
about the ATM 41 about the DIRECT 53 about the IP 337 about the Lightpath 45 about the PDH 38, 285 about the SDH 36 about the Traffic 28 about the Transmission 24 adding 47, 66 committing 102 deleting 47, 66, 102 using the Transmission 127 view windows 67, 68 Moving equipment 79, 80 MSC traffic editing 193 viewing 193 MS-SPring protection, creating 281 Multiplexing, SDH structure 276
Equipment Browser 124 Optical fibre connections, editing 139 Optical networks, planning 151 Originating ports, selecting 64
P
Parameters 2G 157 3G 158 ATM 310 BTS 157, 177 cellular traffic 157 equipment 110 General Traffic Model 174 Global VLR 168 interswitch node 192 interswitch traffic 161, 192 logical equipment 110, 112 PDH default 290 PDH Equipment 113 PSTN traffic 159 routing 253 signalling traffic 167 TETRA traffic 160 viewing delay 329 Passive equipment, creating 120 Pasting, equipment 70 Path protection about 277 about SNC 282 creating 280 MS-SPring 280 using topologies 282 viewing loops 283 PDH connections, editing 302 PDH edge frame layout, viewing 304 PDH edges editing 302 frame layout 304 reserving capacity 303 routing 292, 306 viewing traffic 303 PDH module about 38, 285 default parameters 290 labels 368 PDH Mux parameters 113 PDH XC parameters 113 planning 289 timeslot allocation 295 toolbar 39 view window 38, 285 viewing edge traffic 303 PDH network, creating 289 PDH protection loops, creating 295 Physical details, editing for segment groups 141 Physical element types, creating 115, 116, 117, 118 Pits adding 144 assigning 103 Plan preferences detail edges 64 display 65 edge types 65 equipment 62
N
Network Browser, about 47 Network elements locating 78 Network plans, printing 100 Network topologies, creating 87 Networks about labels 365 about the Browser 47 adding external 164 committing 47, 102 Networks 3GPP 224 planning 100 planning access 91 planning IP 339 planning optical 151 planning pre-pay 238 planning primary rate 285 planning process 52 planning SDH VC-4 274 planning the lightpath 355 planning Traffic 153 restoring 47 routing 241 viewing 47 Node Bs adding traffic 180 ATM parameters 312 Node properties editing 69 viewing 69 Nodes adding 68 calculating signalling faults 215 committing 101 connecting 71 viewing cross connections 70 viewing properties 69 Nominal routing, about 250
O
Opening
Page 391
setting 61 Planning A-bis timeslot allocation 296 access networks 91 ATM networks 308 lightpath networks 355 networks 52 optical networks 151 PDH module 289 pre-pay networks 238 primary rate paths 285 SDH VC-4 network 274 timeslot allocation 288 Plans setting co-ordinates 79 Point of Interconnection, defining 188 Pooling, EDAP timeslots 185 Ports connecting detail equipment 150 defining 118 selecting 64 viewing 149 viewing usage 137 Preferences detail edges 64 display 65 edge types 65 equipment 62 setting 61 Preferred nodes, defining 188 Pre-pay networks, planning 238 Primary rate paths, planning 285 Printing network plans 100 Producing, reports 94 Properties adding 144 assigning 103 committing 101 displaying 81 editing 146 hyperlinks 147 in the Property view 143 showing and hiding 81 viewing 143 Property view, about 143 Protection about MS-SPring 280 about SNC 282 creating PDH loops 295 editing 283 routing loops 268 using topologies 282 viewing 283 viewing loop edges 283 Protection loops editing 283 viewing 283 PSTN traffic parameters, editing 159
queuing 317 queuing types 318, 319 viewing 335, 352 viewing transport 335 Quality of Service requirements, editing 174 Queuing, defining 317
R
Radio connections, editing 140 Regions assigning 103 showing and hiding 104 Removing edges 268 equipment 70 Reports creating routing summary 267 producing 94 viewing routing summary 267 Reserving channels 290 EDAP timeslots 185 Restoring networks 47 RNC networks, planning 91 RNC parameters, setting 111 RNC traffic, editing 194 RNC user plane traffic, viewing 194 Routers, defining 349, 350 Routes creating module views based on 87 display preferences 65 viewing for VPCs 331 viewing VCC 329 Routing 2M Frames 292 about 241 assisted 263 balanced capacity 248 balanced fill ratio 249 conduit diverse 251 creating summary reports 267 defining individual routes 263 detailed capacity 250 double path 245 double path example 246 interswitch traffic 162 model 243 nominal 250 parameters 253 protection loops 268 setting TARGET module layers 253 setting weights 254 shortest path first (SPF) 244 types 244 using automatic 255 using manual 259 viewing 265 viewing MSC traffic tables 197 Routing parameters, editing 253 Routing tables, viewing 197 Routing weights, setting 254
Q
QoS allocating requirements 317, 320 calculating 312, 348 editing requirements 174
Page 392
S
Satellite connections, editing 140 SDH module about 36 labels 368 multiplexing 276 multiplexing structure 276 SDH parameters 114 toolbar 37 view window 36 Searching equipment 78 network elements 78 nodes 78 Segment groups (Root) editing 140 editing physical details 141 Selecting items 77 Served connections, viewing 197 Served networks, assigning 185 Service Editor, using 198 Services adding supported 190 Setting 2G parameters 157 3g parameters 158 ATM parameters 310 BTS parameters 157, 177 cellular traffic parameters 157 co-ordinates 79 edge preferences 65 equipment preferences 62 IMA groupings 332 interswitch node parameters 192 interswitch traffic parameters 161, 192 plan preferences 61 PSTN traffic parameters 159 routing parameters 253 routing weights 254 signalling LU values 169 signalling traffic parameters 167 synchronisation options 58 TARGET module layers for routing 253 TETRA traffic parameters 160 SGSNs parameters 110 Shortest path first algorithm, about 244 Showing cabinets 81, 86 edges 81, 82 Properties 81, 86 regions 104 Signalling calculating faults 215 calculating link faults 215 service parameters 214 Signalling fields adding 198 creating 201 editing 198, 200, 201 Signalling LU values, setting 169 Signalling messages adding 198
creating 201 editing 198, 201 Signalling networks, creating 198 Signalling protocols adding 198 creating 200 editing 198 Signalling service parameters, editing 214 Signalling services adding 198, 202, 205 creating 190, 202, 205 editing 198, 202, 205 Signalling traffic editing 210 generating 213 Signalling traffic parameters, editing 167, 170, 311 Slots configuring 119 SMSCs, allocating subscribers 181 SPF algorithm, about 244 Strategies timeslot allocation 298 timeslot grouping 298 Subracks configuring 119 creating templates 121 subracks configuring slots 119 Subscribers, allocating to SMSCs 181 Synchronisation options 58 Synchronising DIRECT 54
T
Templates allocating timeslots in 299 assigning timeslot allocation 305 creating cabinet 120 creating subrack 121 timeslot allocation 298 viewing traffic allocation 301 TETRA DXT parameters 111 editing traffic parameters 160 editing TRXs 195 traffic parameters 160 Timeslot allocation A-bis 296 about 295 assigning templates 305 managing 288 planning 288 tables 295, 296 Timeslot allocation strategies, selecting 298 Timeslot allocation tables, about 295, 296 Timeslot allocation templates creating 299 defining 298, 299 reserving channels 299 Timeslots allocating 296 allocation strategies 298 EDAP pooling 185 grouping strategies 298
Page 393
planning allocation 288 reserving channels 299 Toolbars ATM module 42 Global 22 Lightpath module 45 PDH module 39 SDH module 37 Traffic module 35 Transmission module 27 Topologies, creating 87 Traffic adding to BTS 177 adding to Node Bs 180 defining interswitch 187, 218, 219 distributing across a VCC group 328 editing 177 editing PSTN 194 General Traffic Model 174 generating interswitch 217, 220, 223 interswitch routing 162 MGW served connections 197 MSC 193, 197 PSTN 194 RNC user plane 194 routing 263 signalling 213 TETRA parameters 160 viewing PDH edge 303 viewing results 196 Traffic allocation, viewing 301 Traffic module about 28, 153 layers 28 toolbar 35 Traffic module labels 367 using 153 view window 28 Traffic services adding 172 CoS requirements 175 delay budgets 175 editing 173 QoS requirements 174 Traffic types adding 172 editing 176 Transmission about 24 detail view 149 equipment view 128 labels 366 toolbar 27 using 127 using the Property view 143 view window 24, 128 Transmission edges, editing 138 Transmission networks creating 127 work order 133, 143 Twisted pair connections, editing 139
the Traffic module 153 the Views Browser 66
V
VCC group properties editing 326 viewing 326 VCC groups adding VCCs to 327 distributing traffic 328 VCCs adding to a VCC group 327 editing 327 VCI templates 324, 325 viewing routes 329 Viewing ATM paths 308 BSC traffic properties 177 codec distribution 211 conduits 148 cross connections 70 delay parameters 329, 332 detail equipment 151 edge group properties 76 edge groups 77 edge properties 76 equipment 124, 133 equipment configuration 134 equipment properties 69 general properties of edge groups and edges 76 general properties of nodes 69 module view windows 68 MSC traffic 193 MSC traffic routing tables 197 node properties 69 PDH edge frame layout 304 PDH edge traffic 303 Properties 143 protection loop edges 283 protection loops 283 RNC user plane traffic 194 routes 265 routing summary reports 267 SGSN-3G served connections 197 timeslot allocation tables 295, 296 traffic allocation 301 traffic results 196 VCC group properties 326 VCC routes 329 VPC groups 330 VPC routes 331 VPTs 332 WMSC served connections 197 Views about the Browser 47, 66 Views Browser about 47, 66 adding modules 47, 66 deleting modules 47, 66 using 66 VPC groups adding VPCs to 330 editing 330 viewing 330 VPCs
U
Using
Page 394
adding 330 editing 330 viewing groups 330 viewing routes 331 VPTs delay parameters 332 editing 331, 332 viewing 331, 332
W
WAM parameters, setting 115 Work orders ATM network 308 equipment 108 IP network 337 lightpath network 355 optical network 151 physical network 133, 143 TETRA network 225
Page 395
Page 396

DIRECT User Reference Guide

Uploaded by

Document Information

Original Description:

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

DIRECT User Reference Guide

Uploaded by

Copyright:

Available Formats

DIRECT User Reference Guide

Software Version 6.0 Reference Guide Edition 1

Chapter 2 About the DIRECT User Interface

Chapter 3 Getting Started in DIRECT

About the Network Planning Process ............................................................... 52

Synchronising DIRECT with ASSET3G/CONNECT ......................................... 54

Using the Views Browser ................................................................................. 66

Viewing Module Windows .......................................................................................... 68

Adding Equipment Nodes in the Module Window............................................. 68

Adding Connecting Edges ............................................................................... 71

Controlling the Display ..................................................................................... 77

About Displaying Data in Module Views ........................................................... 84

About Using the Task Pane ............................................................................. 87

Chapter 4 Creating and Using Equipment

Creating Logical Transport Equipment Types ................................................ 111

Creating Physical Element Types .................................................................. 115

Locating Equipment ....................................................................................... 125

Chapter 5 Creating the Transmission Network 127

Using the Property View of the Transmission Module .................................... 143

Using the Detail View of the Transmission Module ........................................ 149

Creating the Optical Network ......................................................................... 151

Chapter 6 Creating the Traffic Network 153

Adding Traffic Services and Types ................................................................ 172

Adding Traffic to DIRECT Equipment............................................................. 177

Viewing and Editing the Traffic Properties of Equipment ................................ 181

Overview of the Traffic Module Signalling Layer ............................................ 198

Overview of the Traffic Module Interswitch Layer ........................................... 215

Creating a 3GPP Network .............................................................................. 224

Creating the TETRA Traffic Network .............................................................. 225

Using Protocol Stacks .................................................................................... 226

Chapter 7 Routing The Network in DIRECT

Setting the Routing Parameters ..................................................................... 253

Using Automatic Routing in DIRECT.............................................................. 255

Chapter 8 Creating the SDH Network

Chapter 9 Creating the PDH Network

Chapter 10 Creating the ATM Network 307

Calculating QoS and Capacity Over ATM Networks ...................................... 312

Viewing and Editing VCC Group Properties ................................................... 326

Viewing and Editing VPC Group Properties ................................................... 330

Viewing and Editing VPT Group Properties.................................................... 331

Viewing and Editing AAL Group Properties .................................................... 333

Chapter 11 Creating the IP Network

Using IP Addresses in DIRECT ..................................................................... 343

Calculating QoS and Capacity Over IP Networks........................................... 348

DIRECT User Reference Guide Version 6.0

Chapter 12 Creating the Lightpath Network

Appendix A Synchronisation Data

Appendix B About DIRECT Network Labels

DIRECT User Reference Guide Version 6.0

Appendix C About the Traffic Utilisation Calculations 371

Glossary of Terms 375 Index 387

DIRECT User Reference Guide Version 6.0

DIRECT User Reference Guide Version 6.0

Obtaining User Assistance

DIRECT User Reference Guide Version 6.0

Who is This User Reference Guide For?

About the ENTERPRISE User Reference Guides

ARRAYWIZARD User Reference

ASSET3G User Reference

DIRECT User Reference Guide Version 6.0

This Guide CONNECT User Reference

DATASAFE User Reference DIRECT User Reference

NEPTUNE User Reference