Tmo18262d0sgdeni1 0

9352 WiPS
TMO18262 9352 WPS UAO7

UTRAN Configuration
TMO18262 D0 SG DEN I1.0
STUDENT GUIDE
All Rights Reserved Alcatel-Lucent 2010
All rights reserved Alcatel-Lucent @@YEAR

Passing on and copying of this document, use and communication of its
contents not permitted without written authorization from Alcatel-Lucent

9352 WPS UAO7 UTRAN Configuration - Page 1
Empty page
Switch to notes view!
9352 WiPS
9352 WPS UAO7 UTRAN Configuration
This page is left blank intentionally

Terms of Use and Legal Notices

1. Safetyto
Warning
Switch
notes view!
Both lethal and dangerous voltages may be present within the products used herein. The user is strongly advised not to
wear conductive jewelry while working on the products. Always observe all safety precautions and do not work on the
equipment alone.
The equipment used during this course may be electrostatic sensitive. Please observe correct anti-static precautions.
2. Trade Marks
Alcatel-Lucent and MainStreet are trademarks of Alcatel-Lucent.
All other trademarks, service marks and logos (Marks) are the property of their respective holders, including AlcatelLucent. Users are not permitted to use these Marks without the prior consent of Alcatel-Lucent or such third party owning
the Mark. The absence of a Mark identifier is not a representation that a particular product or service name is not a Mark.
Alcatel-Lucent assumes no responsibility for the accuracy of the information presented herein, which may be subject to
change without notice.
3. Copyright
This document contains information that is proprietary to Alcatel-Lucent and may be used for training purposes only. No
other use or transmission of all or any part of this document is permitted without Alcatel-Lucents written permission, and
must include all copyright and other proprietary notices. No other use or transmission of all or any part of its contents may
be used, copied, disclosed or conveyed to any party in any manner whatsoever without prior written permission from
Alcatel-Lucent.
Use or transmission of all or any part of this document in violation of any applicable legislation is hereby expressly
prohibited.
User obtains no rights in the information or in any product, process, technology or trademark which it includes or
describes, and is expressly prohibited from modifying the information or creating derivative works without the express
3written consent of Alcatel-Lucent.
9352 WiPS
4. Disclaimer
In no event will Alcatel-Lucent be liable for any direct, indirect, special, incidental or consequential damages, including
lost profits, lost business or lost data, resulting from the use of or reliance upon the information, whether or not AlcatelLucent has been advised of the possibility of such damages.
Mention of non-Alcatel-Lucent products or services is for information purposes only and constitutes neither an
endorsement, nor a recommendation.
This course is intended to train the student about the overall look, feel, and use of Alcatel-Lucent products. The
information contained herein is representational only. In the interest of file size, simplicity, and compatibility and, in some
cases, due to contractual limitations, certain compromises have been made and therefore some features are not entirely
accurate.
Please refer to technical practices supplied by Alcatel-Lucent for current information concerning Alcatel-Lucent equipment
and its operation, or contact your nearest Alcatel-Lucent representative for more information.
The Alcatel-Lucent products described or used herein are presented for demonstration and training purposes only. AlcatelLucent disclaims any warranties in connection with the products as used and described in the courses or the related
documentation, whether express, implied, or statutory. Alcatel-Lucent specifically disclaims all implied warranties,
including warranties of merchantability, non-infringement and fitness for a particular purpose, or arising from a course of
dealing, usage or trade practice.
Alcatel-Lucent is not responsible for any failures caused by: server errors, misdirected or redirected transmissions, failed
internet connections, interruptions, any computer virus or any other technical defect, whether human or technical in
nature
5. Governing Law
The products, documentation and information contained herein, as well as these Terms of Use and Legal Notices are
governed by the laws of France, excluding its conflict of law rules. If any provision of these Terms of Use and Legal
Notices, or the application thereof to any person or circumstances, is held invalid for any reason, unenforceable including,
but not limited to, the warranty disclaimers and liability limitations, then such provision shall be deemed superseded by a
valid, enforceable provision that matches, as closely as possible, the original provision, and the other provisions of these
Terms of Use and Legal Notices shall remain in full force and effect.

Blank Page
9352 WiPS

Course Outline
Section
UTRAN Configuration
About
This1.Course
4. Topic/Section is Positioned Here
Course outline
Module 1. UTRAN Configuration TMO18262 D0 SG DEN I1.0
Technical
support
Section 2. WiPS
Environment
Course objectives
Module 1. WiPS Environment TMO18262 D0 SG DEN I1.0
Section 3. Parameters
& Objects
1. Topic/Section
is Positioned
Here
Module
1.
Parameters
&
Objects
TMO18262
D0 SG DEN I1.0
Xxx
Xxx
Section
4. WiPS Tools
Xxx
Module 1. WiPS Tools TMO18262 D0 SG DEN I1.0
Section 5. WiPS Wizards for UTRAN Creation and Modification
Module 1. WiPS Wizards for UTRAN Creation and Modification TMO18262 D0 SG DEN I1.0
Section 6. RNC Wizard

Module 1. RNC Wizard TMO18262 D0 SG DEN I1.0
Section 7. NodeB Wizard
Module 1. NodeB Wizard TMO18262 D0 SG DEN I1.0
Section 8. Interface Wizards
Module 1. Interface Wizards TMO18262 D0 SG DEN I1.0
9352 WiPS

Course Outline [cont.]

6
9352 WiPS

Course Objectives
Welcome to TMO18262 9352 WPS UAO7 UTRAN Configuration
Upon completion of this course, you should be able to:
describe the physical architecture of the RNC for UMTS network

describe HW modules functions
describe Defense Mechanisms
describe O&M architecture
9352 WiPS

Course Objectives [cont.]

8
9352 WiPS

About this Student Guide

Conventions
used
in this guide
Switch
to notes
view!
Note
Provides you with additional information about the topic being discussed.
Although this information is not required knowledge, you might find it useful
or interesting.
Technical Reference
(1) 24.348.98 Points you to the exact section of Alcatel-Lucent Technical
Practices where you can find more information on the topic being discussed.
Warning
Alerts you to instances where non-compliance could result in equipment
damage or personal injury.
Where you can get further information
9352 WiPS
If you want further information you can refer to the following:

Technical Practices for the specific product
Technical support page on the Alcatel website: http://www.alcatel-lucent.com

About this Student Guide [cont.]

10
9352 WiPS

Self-assessment of Objectives
Contract number :
At the end of each section you will be asked to fill this questionnaire
Course title : 9370 RNC Hardware Description
Please, return this sheet to the trainer at the end of the training
Client (Company, Centre) :
Language
:
Switch
Dates from :
to notes view!
Number of trainees :
to :
Location :
Surname, First name :

Did you meet the following objectives ?
Tick the corresponding box
Please, return this sheet to the trainer at the end of the training
Yes (or
globally
yes)
Instructional objectives
No (or
globally
no)
1 To be able to describe the physical architecture

of the RNC for UMTS network
2 To be able to describe HW modules functions

11
9352 WiPS
3 To be able to describe Defense Mechanisms
4 To be able to describe O&M architecture

Comments
Self-assessment of Objectives [cont.]

Instructional objectives
12
Yes (or
Globally
yes)
No (or
globally
no)
Comments
9352 WiPS
Other comments
Thank you for your answers to this questionnaire

Do not delete this graphic elements in here:
11
Section 1
UTRAN Configuration
Module 1
UTRAN Configuration
9352 WiPS

Section 1 Module 1 Page 1
Blank Page
112
UTRAN Configuration UTRAN Configuration

9352 WiPS 9352 WPS UAO7 UTRAN Configuration
Document History
Edition
Date
Author
Remarks
01
2008-04-08
GOMEZ Cline
First edition

Module Objectives
Upon completion of this module, you should be able to:

Describe
List
Explain
Identify ...
113


Module Objectives [cont.]
114

Table of Contents
Page

1 Configuration Overview
1.1 Main Steps of Wireless Networks Evolution
1.2 UTRAN CM Solution Overview
2 Configuration Process
2.1 CM Global Process
2.2 Main Parameter Types
2.3 Customer Input Questionnaire
3 Off-line Configuration Characteristics
3.1 Position in the Configuration Process
3.2 Off-line Configuration Scope
3.3 WPS Main Roles
3.4 WPS Main Features
3.5 Off-line Provisioning Prerequisites
3.6 Off-line Outputs
4 On-line Configuration Characteristics
4.2 Configuration Activation
4.3 Network Configuration Upload
115


7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
Table of Contents [cont.]

116

117


1.1 Main Steps of Wireless Networks Evolution
Network
Initial implementation
Network
optimization
implementation
Configuration audits
Network
optimization
implementation
Configuration
audits
Network Reconfiguration
Network Expansion
Configuration audits
118
Network optimization
implementation

This slide gives a broad view of the Network lifecycle:

Network initial implementation, it is the first step of Network creation.

It mainly consists of: radio frequency survey, cell planning, network design, transmission plan,
hardware and software engineering, physical installation and radio site verification.
Network reconfiguration refers to modifications applied on the Network configuration to adapt or

optimize the network after a period of use.
It consists of frequency plan optimization, RNC, BTS re-parenting, LAC modification, network
architecture optimization and transmission plan optimization.
Network expansion usually means addition of equipment to an existing network in order to increase
its capacity in terms of traffic management.

1.2 UTRAN CM Solution Overview
Wireless Network Management System

OffOff-line
OnOn-line
WPS Access
Main Server
XML
XML Files
Engineering Tools
Open
Interface
RNC
Provisioning
119
NodeB
OA&M

For the UMTS Access Network, Wireless-Network Management System provides two complementary sets
of configuration tools:
off-line configuration tool to support network engineering
on-line configuration tool to support network operations.
These two toolkits fully inter-work and provide a consistent user environment for engineering and
operations staff.
Off-line Configuration is designed to support efficient bulk configuration of the UTRAN by

engineering staff. Users can import, modify and export data, both from the UMTS access network
and from 3 rd party engineering tools (such as iPlanner). Off-line Configuration delivers a seamless
network-engineering environment from initial network design through to actual network
configuration.
On-line Configuration has been designed to change the configuration of the UTRAN in real-time.
Not adapted to bulk configuration, the On-line configuration mainly concerns specific operations,
such as extending the network, adding NEs,

1 1 10


2.1 CM Global Process

Planning
Activities
ATM
RF
ND
IP
Provisioning
Activities
WPS
WPS
WPS
OA&M
Activities
Configuration Data
Main Server
1 1 11

This process describes how to configure UTRAN Network Elements (NEs) during a deployment phase. The
main steps are the following:
Planning Activities
Check UTRAN CIQs consistency
Provide neighboring XML files for cell planning
Provide last WPS templates and ATM Profile
Provisioning Activities
Generate full configuration with WPS
Export XML files from WPS
Operation Administration & Maintenance Activities

Load configuration data into their respective NEs
Build the database (MIB) of the RNS and make sure all the local information are up-to-date
Perform real-time adjustments to the initial network configuration.
Note
These steps do not necessarily apply to other contexts, such as introduction of new features, addition of
new NEs, network optimization,

2.2 Main Parameter Types

WMS
IP
CN
136.147.129.17
POC
10.10.20.1
IN
10.10.10.1
RF
RNC
ATM
ATM
WPS Access
RRM
I&C
1 1 12

The slide above shows the main inputs required by the datafill engineer before launching WPS.
Here are the main files to be consolidated at the configuration level:
Engineering files collect RF parameters, technical specifications of the site configuration related to
the I&C values and transport network recommendations.
IP address plan describes the architecture of the IP layer of the network. It takes into account
the addressing rules dedicated to the network design.
ATM parameters describe the architecture of the ATM layer of the access network. They take
into account the ATM engineering rules.
I&C values give practical information about the NEs, such as the serial numbers of the BTS
equipment.
RRM files define parameters such as measurement conditions, allocation of resources and radio
services (based on Call Admission Control & Radio Access Bearers assignment).

2.3 Customer Input Questionnaire
Network Requirements
Deployment Constraints
...
Network System Definition

Engineering rules
Addressing rules
...
A
T
RRM Parameters
A M Para
T
m
RRM Parameters
A M Para eters
T
m
M
n
s
r
RRM Parameters
g n Para eters
ete i
met
Param etDeerss sig n
ers
P
g
m
I
e
s
i
a
ar rketeDr es
P
o
IP Patrwamork D eters
k
IP Ne etw oPr aram eters
. N RtF
.
w
.
ram
NeRF Pa

Operator
Teams
1 1 13
CIQ
Engineering
Teams
(Core, Local)

The Customer Input Questionnaire is a repository where are stored all parameter values and
configuration data required for the later datafill of the UTRAN subsystem.
As mentioned in the document header: "The CIQ is used by the Wireless Network Engineering team,
Regional Engineering and deployment personnel to better understand the customer requirements.
Each manager of a Local Engineering team (in relation with the other activity groups) is in charge of
filling his own part of the CIQ along with the operator:
Radio Frequency (RF) staff fills RF parameters. RF team can also provide XML files coming from any
cell planning tool, such as iPlanner
IP engineering staff fills the IP addresses
ATM engineering staff fills the ATM parameters
The UTRAN CIQ template highlights for each parameter to which domain it belongs (Design, IP, ATM).
At WPS level, the UTRAN datafill engineer is in charge of checking the consistency and completeness of
the UTRAN CIQs.

1 1 14



Main Server
WPS Access
/cmXML
workorder
XML Files
OffOff-line
Schedule export
Import
XML
OnOn-line
W-NMS Desktop
GUI (NSP client)
Engineering Tools
Activation des
workorders
Activation des
workorders
NodeB
Provisioning
RNC
NodeB
1 1 15

WPS is the configuration management tool allowing you to precisely define your Radio Access Network
and to configure Passport NEs.
It is the solution for Off-Line Configuration of an UMTS Access Network.
This product is an external application which is the suite of OA&M Access software modules. It ensures a
seamless configuration stream, from Engineering design to site implementation.
WPS offers a centralized configuration facility for all elements belonging to the RNS (multiple OA&M
Access).
WPS also provides a centralized view of all UMTS Access Network parameters (frequency plans, handover,
power control and radio resource management).

3.2 Off-line Configuration Scope
RNC
RNC
NodeBs
Core Network
1 1 16

WPS allows the user to configure both UTRAN nodes and interfaces:
Nodes
BTS & NodeB
RNC: Control Node, Interface Node, PCM Access Node
Interfaces
Iub interface (Interface UMTS NodeB) is defined between RNC and NodeB. It allows to connect
RNC and NodeB from different manufacturers.
Iu interface (Interface UMTS) is defined between Core Network and Access Network. The Core
Network can be connected to different Access Networks.
Iur interface (Interface UMTS RNCs): this interface between two RNCs, has been defined to
support specific functions such as handover without involving the Core Network.

3.3 WPS Main Roles
Bulk Deployment
Densification
Reparenting
WPS
Synchronization
Audit
Reconfiguration
Global Update
Optimization
WPS plays a key role in each phase of networks lifecycle

1 1 17

The following tasks can be carried out with WPS:

UTRAN Cell Planning Implementation
Neighboring plan changes
Scrambling Code plan changes
Boundaries with other UTRAN equipment suppliers management
UTRAN Topology Implementation

Centralized UTRAN repository
Network Elements creation (NodeBs, RNCs)
Network Reconfiguration (including Reparenting)
Network coverage expansion (Densification, Extension (e.g. New site allocation)
WPS also provides sophisticated features, such as last minute consistency check and synchronization with
live network.

3.4 WPS Main Features

Templates
Wizards
Assisted
Tasks
Checks
Rules
WPS
combined use of templates and engineering rules sets 60% to 90% of parameters
1 1 18

The slide above lists the main internal features of WPS designed to help the datafiller complete his
network creation.
These features bring the following benefits:
Assistance,
Consolidated data,
Efficiency & security.
When properly taking advantage of these features, the datafiller doesnt have to enter all parameters of
the objects on his own. His contribution in terms of keyboarding is reduced to the minimum.

3.5 Off-line Provisioning Prerequisites

Planning
Activities
ATM
Profiles
RRM
Templates
CIQ
RAN
Templates
Site Configuration
RF Parameters
Network Design
Addressing Plans
NEs parenting
PP
Templates
Provisioning
Activities
WPS
1 1 19
WPS
WPS

The following inputs must be provided beforehand to the datafill engineer to help him create the Access
Network with WPS:
RF parameters are collected from the cell planning tool. They also provide architecture, site
configuration, and specific values, such as scrambling code or identifiers of the cells.
Templates are files containing parameter names and values applicable to various NEs of the
network.
ATM profiles mentions the ATM parameters to be used at the nodeB level for the Iub interface.
Addressing Plans (IP, ATM, SS7) are based on addressing rules dedicated to the network design.
RRM (Radio Resource Management) files must be created before entering WPS.
While entering these parameters in WPS, the UTRAN datafill engineer must check the consistency and
completeness of the input coming from the initial engineering teams.

3.6 Off-line Outputs

Configuration
Activities
W
WPS
XML
XML
WPS
XML
WPS
W orking Sessions (Workspace)
S tatic Configuration (XML Snapshot)

D elta Configuration (XML Workorder)
T emplates (XML Template)

Main Server
1 1 20

WPS is able to provide its interlocutors with lots of information. By comparison with UA V3.1 release, the
files sharing function of WPS has been enhanced to avoid discrepancy between WPS platforms and OA&M
servers.
Towards other WPS platforms, WPS can send the following types of files:
Static Configuration of the network
Delta Configuration, i.e. modifications brought to the network
Templates used internally by WPS
Complete WPS Working Sessions.
Towards the WMS main server, WPS can send only 1 type of files:
Modifications brought to the network.
The storage of Configuration Management files can take place in the repository of the main server.

1 1 21



Main Server
WPS Access
/cmXML
workorder
XML Files
OffOff-line
Schedule export
Import
XML
OnOn-line
W-NMS Desktop
GUI (NSP client)
Engineering Tools
Activation des
workorders
Activation des
workorders
NodeB
Provisioning
RNC
NodeB
1 1 22

One of the functional roles of the OA&M platform consists in interfacing the Live Network with the Offline Configuration tools. It allows various exchanges between entities, at different stages of the network
lifecycle.
Two categories of files can be exchanged on the CM XML interface:
Workorder files that define evolutions to be applied on the configuration,
Snapshot files used to exchange views of the configuration.
WMS is likely to interact directly or indirectly with one or several WPS applications. It supports the
workorder import and snapshot export operations:
Towards WPS, WMS sends the data coming from the network. It can be either the initial view of
the network or the updated view in case of modifications.
Towards the network, WMS retrieves the configuration data processed by the WPS team. It can be
either the first resulting CM files or the delta configuration in case of evolution.

4.2 Configuration Activation
D
XML
WPS Access
Activation
Main Server
Live Network
1 1 23

The workorder import can be directly performed from WMS GUI.

The import operation updates WMS and runs the activation on the impacted passport based devices.
The potential fallback operation will be performed by importing in WMS a reverse workorder prepared
ahead of the activation phase. It is to be noted that this reverse workorder is processed by WMS in the
exact same way as a standard workorder.
Note
For passport based devices, when requesting the deletion of the EM subtree, the deletion is completed
at WMS level but no operation is send to the passport. Consequently, the reverse of a workorder that
requested the creation of an EM subtree will not delete the sub-components on the passport itself.

4.3 Network Configuration Upload
S
XML
WPS Access
Main Server
Live Network
1 1 24

This operation consists in exporting a snapshot from WMS towards WPS.

The purpose of this operation is to make sure that the configuration description stored in the WPS files is
consistent with the live network, including evolutions brought lately by the OA&M staff.
Two modes of export are available from WMS:
Automatic Daily export: a snapshot file relevant of the live network configuration is automatically
generated by PWI on a daily basis.
Triggered export: the user can launch the export directly from WMS GUI. The generated snapshot
file can be complete or partial according to filtering criteria selected by the user.

End of Module
UTRAN Configuration
1 1 25


21
Section 2
WiPS Environment
Module 1
WiPS Environment
9352 WiPS

Blank Page
212
WiPS Environment WiPS Environment

Document History
Edition
Date
Author
Remarks
01
2010-04-08
GOMEZ Cline
First edition

Objectives
This section will enable you to

Describe the main characteristics of the platform

recommended for WPS, including hardware
& software requirements.
Perform the various administrative tasks related to the product
installation.
Identify the main containers provided by the tool in order to handle the
configuration data.
Navigate between WPS windows and select the appropriate option
(menus, tabs, panels, ) to perform specific operation.
213


214

Table of Contents
Page

1 Platform Administration
1.1 System Requirements
1.2 WPS / W-NMS Co-residence
1.3 WPS for Access Installation on PC
1.4 WPS Load Contents
1.5 Session Starting / Quitting
2 WPS Containers
2.1 WPS Access Architecture
2.2 Snapshot
2.3 Workorders
2.4 Workorders Management
2.5 Initial Snapshot
2.6 Current Workorder
2.7 Workspace
2.8 Multi-user Collaboration
2.9 Data Sharing
3 GUI Overview
3.1 Main Window
3.2 Setting WPS Properties
3.3 Network Tab
3.3.1 Overview Panel
3.3.2 Edition Panel: by instance
3.3.3 Edition Panel: by type
3.3.4 Smart Tables Filters
215
3.3.5 Find / Right-click Menu / Navigator
9352 WiPS 9352
WPS UAO7Network
UTRAN Configuration
3.3.6
tree display by NE Type grouping
3.3.7 Help on Object Types
3.4 Workorders Tab
3.5 Templates Tab
3.6 Datasets Tab
3.7 Checks Tab

7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
32
33
34
35
36
37
38

216

217


1.1 System Requirements

1 CPU Pentium IV 2.8 GHz

2 Gb RAM (recommended)
40 Gb disk
1 CD-ROM drive
Ethernet connection
WPS
Windows Vista
Windows 2000 professional
Windows XP professional
218

WPS is a standalone tool running on PCs with the following recommendations:

1.2 WPS / W-NMS Co-residence
WPS Package
Client Stations
W-NMS
PC
client (Windows)
SUN
Ultra 5
W-NMS
client
OA&M LAN
Main
Server
219

Starting from OAM04.1 release, the 9352 WPS applications can be installed in co-residence on PC clients
connected to the WMS server.
To support WPS, these clients must run either Microsoft Windows 2000, Windows Vista or Windows XP.
The introduction of the 9352 WPS application on a WMS PC client provides increased flexibility and
reliability in the End-to-End Configuration Chain.
This co-residence allows:
Easy consolidation of multiple contributors work prior to activation
Last minute consistency check and synchronization with live network
Efficient and secured solution for fast parameter update (network optimization) thanks to the
excellent performance of the tool.
Hardware Requirements
The recommended hardware for the PC client hosting WPS is Pentium IV, 2.5 GHz or more, 1Go RAM or
more.

1.3 WPS for Access Installation on PC
WPS
for
Access
2 1 10

Installing
The procedure to follow is very simple, here are the basic steps to perform:
start the WPS setup wizard by double-clicking on the WPS_UMTS_Access-V6_0-NNYYYYWWVV_windows.exe file,
select the destination directory for the WPS installation,
select the WPS installation directory from which user data (atm rules, check profiles, templates)
should be retrieved.
Select the plugin file (UMTS_Access_V6.0_NNN-20082801.wipsar) to install it in WPS directory.
Upgrading
In fact there is no upgrade of the WPS existing files, an installation of the new WPS version has to be
performed. The new version takes the place of the previous one. During the procedure, you just have to
indicate a different root folder from where you start the installation steps.
Note
If you decide to keep different versions of WPS, be careful about the compatibility of the resources you
share: workspace files (.wps) are not compatible between versions.

1.4 WPS Load Contents
WPS
for
Access
transfer
2 1 11

The WPS for Access Network CD-ROM contains the following main components:
the WPS software,
the mapping files,
the configuration models.
The WPS for Access Network CD-ROM contains other directories, mainly:
the assistants,
the default templates.

1.5 Session Starting / Quitting
2 1 12

Launching the Application

On your desktop, double click on the WPS icon.
An alternate solution to start WPS for Access Network is to select the option
Start->Programs->WPS V6.0#>WPS V6.0 on the WPS PC.
Quitting the Application

There are two different ways to quit WPS:

select in the Menu Bar File -> Exit,
click the close icon (X located in the top right-hand corner) of the header bar.

2 WPS Containers
2 1 13


2 WPS Containers
2.1 WPS Access Architecture

WPS Access
Specific Services
Wizards
Generic Services
Editing
Modifying
Comparing
Workspace
Operations
Templates
Navigators
Check Sessions
Checks
Datasets
Models
Configuration Data
Rules
Import/Export
Open/Save
Snapshot
Import/Export
Workorders
Import/Export
W
S
Audit
Local
Persistence
2 1 14
D

WPS for Access is based on a kernel platform on top of which specific plug-ins are added. The general
structure of the tool can therefore be subdivided into two types of internal components:
The generic services listed above belong to the WPS platform. They include all the containers
handled by the datafillers during provisioning sessions as well as the files management.
The specific services gather all the plug-ins, such as wizards, navigators, These services include
all the tools surrounding the configuration data and helping the datafiller accomplish his work
during provisioning sessions.
The local persistence item means the information is kept in memory (RAM) during the WPS session.

2 WPS Containers
2.2 Snapshot
Workspace
Templates
Check Sessions
S tatic Configuration
Datasets
Configuration Data
Snapshot
WPS
Workorders
Network State
2 1 15

Snapshot
A snapshot gives the image of a network configuration at a given time. It does not include the
operations performed upon the objects, unlike the work order.
The initial snapshot comes from the OMC. It is the base to which new coming operations will be
applied.
Base State / Current State

The current network state results from the interpretation of the workorders on top of a reference
snapshot, defined as the base state.
The base state refers to the initial set of network Managed Object Instances (MOIs) on which the
modifications apply. The base state is never modified by the application.
The result of the modifications performed on the base state is available in the current state.

2 WPS Containers
2.3 Workorders
Workspace
Templates
Check Sessions
D elta Configuration
Datasets
Configuration Data
Initial Snapshot
CREATE
WorkOrder #1
DELETE
WorkOrder #2
UPDATE
WorkOrder #3
2 1 16

Workorder Definition
It consists of a recorded sequence of elementary operations:

creation,
deletion,
update.
These operations are based on XML commands: create, delete, set.

A workorder defines the transition from an initial configuration to a final configuration. In between, it
allows simulation of sub-networks, combination of various scripts, etc..
The workorders created within WPS are built upon the initial snapshot.
The current workorder refers to the active workorder that is currently recording the configuration
evolutions performed through the application.
In the following slide, we can see that the current workorder is not necessarily the most recent one.

2 WPS Containers
2.4 Workorders Management

Workspace
Templates
Check Sessions
Datasets
Resulting
Network Views
Configuration Data
Initial Snapshot
Create RNC
Workorder #1
Create NodeB
Workorder #2
Create Iub
Workorder #3
2 1 17

Workorder Management
WPS manages a workorder stack containing all the workorders created or imported by the
datafiller within his workspace.
The different workorders are stored according to the chronology. They are executed by the tool
from the first in up to the last in.
At any time during the session, the datafiller can select one workorder among the others to be
set workorder as current.
In terms of storage, the current workorder refers to the one in the stack in charge of recording the
modifications of the configuration, for the time being.

2 WPS Containers
2.5 Initial Snapshot

Creation
Modification / Update
Workspace
Workspace
Check Sessions
Datasets
Templates
Templates
Check Sessions
Configuration Data
Datasets
Initial Snapshot
Configuration Data
Workorder #1
Initial Snapshot
Import
Workorder #2
Workorder #1
Workorder #3
2 1 18

Snapshot
A snapshot gives the image of a network configuration at a given time. It doesnt include the
operations performed upon the objects, unlike the work order.
The initial snapshot comes from the OMC. It is the base to which new coming operations will be
applied.
Base State / Current State

The current network state results from the interpretation of the workorders on top of a reference
snapshot, defined as the base state.
The base state refers to the initial set of network Managed Object Instances (MOIs) on which the
modifications apply. The base state is never modified by the application.
The result of the modifications performed on the base state is available in the current state.

2 WPS Containers
2.6 Current Workorder

Workspace
Templates
Datasets
Check Sessions
Configuration Data
Initial Snapshot
Current = WO#1
Resulting Network View
Workorder #1
Current = WO#2
Resulting Network View
Workorder #2
2 1 19

WPS manages a workorder stack containing all the workorders created or imported by the datafiller
within his workspace.
The different workorders are stored according to the chronology. They are executed by the tool from the
first in up to the last in.
At any time during the session, the datafiller can select one workorder among the others to be set
workorder as current.
In terms of storage, the current workorder refers to the one in the stack in charge of collecting the
modifications of the configuration, for the time being.

2 WPS Containers
2.7 Workspace
Workspace
Templates
Check Sessions
Datasets
Audit
W ork Session/Environment
Configuration Data
Snapshot
Workorders
2 1 20

Workspace Definition
This is the working area where all the workorders are stored. In other words, the workspace contains all
the data that can be managed through the application: the Network Managed Object Instances (MOIs).
It also contains other components of the toolkit:
templates,
datasets,
check sessions,
etc.
The current workspace refers to the workspace currently loaded in memory while the WPS application is
running. The application is able to handle one and only one workspace at a time.

2 WPS Containers
2.8 Multi-user Collaboration
Copyright 1996 Northern Telecom
RF
Transport
I&C
Initial
Snapshot
2 1 21

The introduction of XML format, workorders and task-oriented wizards allows easy multi-user
collaboration.
Several users from different functional teams (RF, transmission, etc) can work on relevant aspects of the
provisioning thanks to the task-oriented approach of the wizards. This allows the completion of a set of
tasks. All contributions can then be merged together to create an unique Workorder representative of
the changes to apply.
Furthermore, the corresponding XML workorder can be generated and posted to a repository (using the
Windows file transfer). This workorder is available to other users.
Upload of this workorder into another WPS automatically completes the corresponding task. The two WPS
applications have the same reference snapshot, which can also be stored in the repository.
A centralized storage of snapshots and workorders on a repository thus enables multi-user collaboration.
Individual contributions can be accessed and shared among several users.

2 WPS Containers
2.9 Data Sharing
2 1 22

Data sharing enables several WPS users to collaborate simultaneously on a common project. They are
using a common workspace repository.
The users store locally individual contributions within WPS. Then the users can publish these
contributions on the workspace repository.
The users can also retrieve contributions of other team members from the workspace repository.
In this environment, several versions of the same data can cohabit:
the shared version: managed by the workspace repository
one or several local versions
WPS manages the potential conflicts on the shared data, as follows:
The users are allowed to access to the same data simultaneously.
WPS detects and reports potential conflicts.
The users manage the conflict resolution within the environment.

3 GUI Overview
2 1 23


3 GUI Overview
3.1 Main Window

Menu Bar / Tool Bar
Tabs
2 1 24
Panels

WPS main window shows the major options the datafiller can access during his work sessions, when
building his network.
These options which are displayed in the menu bar are the following ones: File, Edit, Windows,
Templates, Datasets, Check & Help. They are discussed later on in this section.
From this main window, the datafiller can monitor his own work, displaying the appropriate components
of the network under construction, according to his own needs.
Here are the subparts of the WPS main window:
Menu bar
Tabs
Panels
All these subparts are going to be discussed in the following pages.

3 GUI Overview
3.2 Setting WPS Properties
2 1 25

Setting WPS properties is one of the very first task the user should perform. This operation serves four
purposes:
defining the Main Server IP address and the login/password to be used in order to benefit from the Data
Sharing capabilities of the CM tool suite,

- setting the Template Source to identify WPS user,
- defining the Main Server IP address and the login/password to be used in order to benefit from the
Workorder file transfer capabilities of the CM tool suite.

-Defining the threshold for auto-grouping by NE type

3 GUI Overview
3.3 Network Tab

Overview Panel
Edition Panel: by instance
Tab/Edition Panel: by type
Tab/Smart Tables Filters
Tab/Smart Tables Filters [cont.]
Find / Right-click Menu / Navigator
Help on Object Types
2 1 26


3.3 Network Tab
3.3.1 Overview Panel
2 1 27

All the tabs available in the bar provide a graphical representation of the selected structure.
The Network tab shows the entire UTRAN network in a tree diagram.
It displays all the MOIs (Managed Object Instances). It enables the user to navigate among the different
instances.
From the Network tab, you can perform the following operations:
create new workorders,
handle network changes,
launch check sessions,
add (create) datasets,
manage templates, including the creation of new templates, the propagation of existing templates
as well as the comparison with other templates,
invoke the navigators.
Launch audit checks (Comparisons between objects and corresponding templates)

3.3 Network Tab
3.3.2 Edition Panel: by instance
2 1 28

The Network tab also allows the data filler to choose the Edition display instead of the Overview one.
This powerful display function provides a spreadsheet-like visualization where several instances of the
same object are displayed on different rows.
Here are the main benefits of this display mode:
The parameters of each object are ordered by column.
The selection of one or more parameter enables immediate settings, in other words, multi-value
modification from the tabular editor.
The highlight differences with option compares the current values with either the default
values or the template ones.
The filtering option (right click) offers various types of filter based on the chosen criteria in order
to sort or to limit the display of objects.

3.3 Network Tab
3.3.3 Edition Panel: by type
2 1 29

The Network tab also allows the data filler to choose the Edition display instead of the Overview one.
This powerful display function provides a spreadsheet-like visualization where several instances of the
same object are displayed on different rows.
Here are the main benefits of this display mode:
The parameters of each object are ordered by column
The selection of one or more parameter enables immediate settings, in other words, multi-value
modification from the tabular editor.
The highlight differences with option compares the current values with either the default
values or the template ones.
The filtering option (right click) offers various types of filter based on the chosen criteria in order to
sort or to limit the display of objects.

3.3 Network Tab
3.3.4 Smart Tables Filters
2 1 30

The progressive generalization of the commonly named Smart Tables within the application brings
functional improvements to the WPS toolkit.
A Smart Table is an advanced tabular display that provides additional functionalities such as row sorting
and filtering capabilities.
To access to the smart table capabilities, the user must select the Edition tab in the Object Editor.
New functionalities benefit all editors including the check report, the datasets edition, the comparison
report, and the workorder editor. This excludes the tables related to the wizards.
Cell auto-size auto-size and manual resizing is available for all smart tables.
HTML export tables can be exported in HTML. The initial format is kept.
Work-order enhancement the tabular edition of work-orders is enriched with three new columns:
Method provides the operation (create/delete/update)
Model provides parameter default model value
Template provides parameter default template value
The model & template columns are optionally displayed by clicking the show model/template values
checkbox.

3.3 Network Tab
3.3.4 Smart Tables Filters [cont.]
2 1 31

The progressive generalization of the commonly named Smart Tables within the application brings
functional improvements to the WPS toolkit.
A Smart Table is an advanced tabular display that provides additional functionalities such as row sorting
and filtering capabilities.
To access to the smart table capabilities, the user must select the Edition tab in the Object Editor.
New functionalities benefit all editors including the check report, the datasets edition, the comparison
report, and the workorder editor. This excludes the tables related to the wizards.
Cell auto-size auto-size and manual resizing is available for all smart tables.
HTML export tables can be exported in HTML. The initial format is kept.
Workorder enhancement the tabular edition of workorders is enriched with three new columns:
Method provides the operation (create/delete/update)
Model provides parameter default model value
Template provides parameter default template value
The model & template columns are optionally displayed by clicking the show model/template values
checkbox.

3.3 Network Tab
3.3.5 Find / Right-click Menu / Navigator
2 1 32

Navigators enable the datafiller to jump from a selected MOI of the network instance browser to another
logically associated MOI.
To perform navigation, the datafiller must use the right click of the mouse and select Navigate to.
Examples of available navigators:
NodeB > POC
NodeB > BTS
NodeB > Interface Node
NodeB > RNC
FDDCell > BTSCell
BTSCell > FDDCell
The Find in tab panel enables the datafiller to search for a specific object belonging to the tree diagram.
It applies to all tabs (workspace, network, templates, datasets).
As semantic checks, operations, wizards and rules, navigators are business-specific plug-ins. They are not
directly issued from the UTRAN models.

3.3 Network Tab
3.3.6 Network tree display by NE Type grouping
Group icon
Instance number of the

group
2 1 33

WPS provides instance browsers in order to navigate across the different MOIs and the goal of this feature is
to allow customer working quickly and easily with it even with a large amount of NEs.
Until WPS V5.2,all NE's were displayed in one continuous Network tree. However, when managing networks
with lots of NEs (in particular NodeB) this display is very large and difficult to work with.
So this feature requires creating grouping folders for each object, sub tree included. This number of
elements shall be indicated at related folder level.
Default setting shall be the following: as soon as the number of instances reaches 10 then the grouping
shall be performed. This minimum number of instances shall be configurable through WPS Settings
defined in Change Properties menu.
By double-clicking on a grouping folder it shall be possible to group/un-group it and a contextual menu
shall allow grouping/un-grouping folders.

3.3 Network Tab
3.3.7 Help on Object Types
2 1 34

WPS include a comprehensive and interactive RAN Model description tull providing help information
about any type of objects. The help window also features a search tool working both on the Network
Tree and RAN Model.

3 GUI Overview
3.4 Workorders Tab
2 1 35

All the tabs available in the bar provide a graphical representation of the selected structure:
The Workorders tab contains:
the initial snapshot (initial reference),
a subtree representing the list of created work orders, with the current work order in bold,
another subtree representing the list of check sessions.
From the Workorders tab, you can also perform the following operations: rerun check sessions, create
new templates & invoke the navigators.
The Workorder description panel is available from the Workorders tab only, when one workorder is
selected. It enables the datafiller to look at all the network changes recorded in the current workorder.

3 GUI Overview
3.5 Templates Tab
2 1 36

All the tabs available in the bar provide a graphical representation of the selected structure.
The Templates tab enables the user to navigate among the different instances of a template.
From the Templates tab, you can also perform the following operations:
manage the templates, including cloning, exporting and setting / unsetting default template,

3 GUI Overview
3.6 Datasets Tab
2 1 37

All the tabs available in the bar provide a graphical representation of the selected structure:
Within the Datasets tab, each dataset is displayed as a subtree containing a set of heterogeneous
managed objects. It enables the user to navigate among the different instances.
From the Datasets tab, you can also perform the following operations:
launch check sessions,
manage datasets, including adding (creating) & removing datasets,
create new templates,

3 GUI Overview
3.7 Checks Tab
2 1 38

The Check profiles and the checks sessions panel are now available from the Checks tab only.
This subpart of WPS displays detailed information about a selected check session:
objects,
date,
list of errors,
list of checks.
It can be performed again, if required (re-run check session).

Self-assessment on the Objectives

Please be reminded to fill in the form

Self-Assessment on the Objectives
for this module
The form can be found in the first part
of this course documentation
2 1 39


End of Module
WiPS Environment
2 1 40


31
Section 3
Parameters & Objects
Module 1
9352 WiPS

Blank Page
312
Parameters & Objects Parameters & Objects

Document History
Edition
Date
Author
Remarks
01
2010-04-08
GOMEZ Cline
First edition

Module Objectives

Describe
List
Explain
Identify ...
313


314

Table of Contents
Page

1 UTRAN Parameters
1.1 UTRAN Parameters Organization
1.2 UTRAN Parameter Domain
1.3 RAN Parameter Activation Classes
1.4 RAN Object Activation Classes
1.5 UTRAN Objects Mapping
1.6 RRM Parameters Organization
1.7 FDDCell Configuration Classes Instantiation
2 WPS Objects Introduction
2.1 MOC / MOI
2.2 Templates
3 CM XML Description
3.1 CM XML Interface Overview
3.2 CM XML File Types
3.3 CM XML File Structure Introduction
3.4 Snapshot Description
3.5 Workorder Description
3.6 Template Description
315


7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24

316

1 UTRAN Parameters
317


1 UTRAN Parameters
1.1 UTRAN Parameters Organization
UTRAN Parameters
Static Parameters
Configuration Parameters
Customer
System Constants
(Manufacturer)
318
Restricted

In order to understand the definition and the role of the different parameters, lets see how these
parameters are linked together and grouped within the RAN model.
There are 2 main kinds of parameters in the UTRAN subsystem, the static and configuration parameters.
The static parameters have the following characteristics:
They have a fixed value and cannot be modified by the customer at the OA&M client.
They are part of the network element load.
A new network element needs to be reloaded and built in order to change their values.
The configuration parameters have the following characteristics:

They are contained in the Access OA&M database.
They are subdivided in 2 main types: Customer / System Constants.

Customer: Can be modified by the customer (at W-NMS level) or with CM files (thanks to WPS).
System Constants (Manufacturer) are defined by the manufacturer. They cannot be modified
through CM files.

1 UTRAN Parameters
1.2 UTRAN Parameter Domain
MIB
RAN Model
Based
NodeB
Control
Node
WPS
W-NMS
MIB
Passport
Based
POC
319
Interface
Node

Two different types of parameters are designed to configure a UMTS Access Network:
Control Node, NodeB and RAN parameters.
Interface Node, Access Node and Passport parameters.
Changing parameters value may impact the behavior of the live network.
For RAN parameters the impact triggered by a parameter modification is strongly linked with the
parameter classes (see next slide).
For Passport parameters it is not always easy to predict the impact of a parameter modification. Possible
consequences are:
nothing,
reset of an interface,
reset of a module,
reset of a node.

1 UTRAN Parameters
1.3 RAN Parameter Activation Classes

Class 0
activation classes apply to
customer and manufacturer parameters
MIB
Class 2
Class 3
MIB build required

(most common case)
lock/unlock required
on-line modification allowed
3 1 10

The Parameter activation class defines the behavior of the parameter with respect to the set online
operation:
Class 0
The parameter can not be directly modified online. The modification can be performed either by a MIB
build or by a deletion and re-creation online of the object it belongs to (when allowed).
Class 2
The parameter can be modified online but the operation requires to prior lock the object it belongs to or
one of its ancestors.
Class 3
The parameter can be directly modified online.
Note: Classes do not apply to Passport parameters.

1 UTRAN Parameters
1.4 RAN Object Activation Classes

Not Allowed
on-line creation / deletion behavior
MIB
Allowed With Lock

MIB build required
lock/unlock required
Allowed
on-line modification allowed
3 1 11

The object activation class defines the object behavior with respect to the create online and delete
online operations.
Not Allowed:
The object can not be created/deleted online, a build is required.
Allowed With Lock:
The object can be created/deleted online but the operation requires locking the object or one of its
ancestors in the containment tree.
Allowed:
The object can be created/deleted online.

1 UTRAN Parameters
1.5 UTRAN Objects Mapping
FDDCell0
BTSCell0
NodeB
BTSEquipment
FDDCell1
BTSCell1
RNCEquipment
RNC
PP15K
Logical Configuration
3 1 12
Physical Configuration

The RAN model is split into two parts:

Hardware Equipment: This part groups all elements (parameters) that defines the equipment (BTS)
and the Passport module (Pmod). It is the physical part of that model.
Software Configuration: This other part groups all elements that defines the NodeB and RNC logical
configuration. It is called logical part because it defines the software for logical radio sectors and
logical RNC nodes.
To perform a link between the Hardware Equipment (physical part) and the Software Configuration
(logical part), it is necessary to link several elements from both parts. For example to link the logical
sectors to the physical equipment, the user has to attach a BTSCell (physical part) to one FddCell (logical
part). This specific operation is called Mapping.

1 UTRAN Parameters
1.6 RRM Parameters Organization

RNC
RadioAccessService
ConfigurationClassX
InstanceN
ConfigurationClassY
InstanceN
Instance...
ConfigurationClassZ
InstanceN
Instance...
Instance...
Instance...
Instance3
Instance3
Instance2
Instance2
Instance1
3 1 13
Instance1
Instance2
Instance1

Each of these configuration classes can have several instances where each instance will have its own
parameter settings.
Once all the configuration classes are defined, each cell belonging to the RNC will have a pointer,
defined by the following parameters:
powerConfId,
powerPartId,
powerCtrlConfId,
hoConfId,
CacConfId,
MeasurementConfId.
These parameters are designed to identify which instance of configuration class the cell is using.

1 UTRAN Parameters
1.7 FDDCell Configuration Classes Instantiation

RNC
NodeB
RadioAccessService
FDDCell
DedicatedConf
Example
FDDCell
powerPartId
CacConfClass
CallEstabCauseConfClass
HoConfClass
MeasurementConfClass
PowerConfClass
PowerCtrlConfClass
PowerPartConfClass
Sib11MeasReportingUsHoConfClass
3 1 14

In the example above, we can see that each instance of PowerPartConfClass includes a set of predefined
parameters.
Each parameter belonging to the PowerPartConfClass object can take a different value under each
instance.
For example, the minSpeechPowerRatio can take values from 60% to 80% according to the selected
instance.
The case above applies to the minSpeechPowerRatio, that equals to 60%.
These parameters will be taken into account when the FDD cells are datafilled during WPS sessions.

3 1 15


2.1 MOC / MOI

MOC Tree
MOI
(example)
(example)
instance of
RNC
contains
RNC
identifiers
contains
versioning
routing
NodeB
contains
attributes
FDDCell
NeighbouringRNC
CONFIGURATION RESOURCE MODEL
3 1 16
CONFIGURATION
DATA

Definitions
The model consists in a descriptive construction based on a set identified elements.
The MOC (Managed Object Class) is an abstract description of an object.
The MOI (Managed Object Instance) is managed by the application. When not explicitly specified,
the MOI refers to Network MOI standing for managed network objects.
The NOM (Network Object Model) defines the set of MOCs and their interdependencies. The
Network Model is dependent of the technology.

2.2 Templates
MOI
User Input
Template
Identifiers
Identifiers
Identifiers
Id1
Id2..
Id1
Id2..
Tuned Parameters
Param1
Param2...
Generic Parameters
Tuned Parameters
Param1
Param2...
Generic Parameters
Tuned Parameters
Param3
Param4
Param5
.....
.....
Param20...
Generic Parameters
Param3
Param4
Param5
.....
.....
Param20...
combined use of templates and engineering rules sets 60% to 90% of parameters
3 1 17

Definition
A template is a particular kind of object dedicated to the management of values likely to be shared
among several objects.
Templates are used during the instantiation of Managed Objects in order to minimize the number of
parameters to be manually initialized by the datafiller.
A template contains generic parameters applying to a large number of objects. All templates have
been designed to ease the provisioning activities of the datafiller.
Several templates can be designed by the operator in order to configure the network with
parameters matching specific requirements.
Engineering templates are provided with recommended generic parameter values. They must be
imported before generating/importing CM XML files. After template import, some parameter values
must be filled by the datafiller to customize the templates according to his configuration.

3 1 18


3.1 CM XML Interface Overview

What are CM XML files?
eXtensible Markup Language files describing configuration resources
Open exchange format allowing easy interaction with third party tools
Planning
Activities
Provisioning
Activities
WPS
CM XML Files
OA&M
Activities
Configuration Data
Main Server
3 1 19

The interface format for Configuration Management files is based on the Extensible Markup Language
(XML). This standardized format allows display & transmission of data through Internet applications.
The CM XML format is an XML file format used to describe the configuration of network element
resources. This file format is used to import/export to/from the OAM system in order to set/retrieve the
configuration data.
This description is made under the form of managed object tree description. This tree description can be
complete or partial.
The CM XML file format has two declinations:
The XML Snapshot
The XML Workorder
The characteristics of these file formats are described later on in this section.
The XML interface conveys configuration parameters and supports data exchange between WPS and
planning tools on the northbound interface side.

3.2 CM XML File Types

Workspace
Container Type
XML
Binary
Usual File
Extension
Snapshot
.xcm
Check Sessions
Workorder
.xwo
Datasets
Template
.xtpl
Audit Sessions
Template key
Key mask

.xtplm
Key masks

.wps
Templates
Templates mask
Workspace
.xkm
Configuration Data
Snapshot
Workorders
3 1 20

Starting from UA V3.2 release, a new import / export feature: the XML interface is introduced in all
the OAM subsystem entities, including the OSS design tools (cell planning, transmission, CIQs, ) and the
WPS tool.
According to the interface in use, the format of the files handled are different.
Basically, all files generated by the new version of the WPS tool are XML-like files that can be read both
by any Internet Browser and by any XML editor (such as Epic).
The table above lists all the types of files that can be handled within the WPS tool by the range of
containers and other software components.
In UA6.0, 2 new containers are available:
Template mask: allows to choose only a part of the templates parameters when comparing it with a
MOI, during an audit

Key mask: allows to select for audit only certain MOIs of a MOC
MOI=Managed Object Instance

MOC=Managed Object Class

3.3 CM XML File Structure Introduction
RNC
RNC Paris
NodeB
Training
FDDCell
NeighbouringRNC
Training_Cell_1
RNC Versailles
3 1 21

Objects are organized in a tree; the hierarchical relationship between a parent and children is called
containment. The containment links the life cycle of parent and children. A Child can not be created if
its parent were not created before. Whenever the parent is deleted its entire descendant subtree is
deleted.
CM XML files are structured according to the network element organization and follow the containment
tree of network elements from root to leaves.
The mandatory parts of any CM XML source file are:
Object identifiers
Each object instance is identified by its full Distinguished Name (DN).
Attributes and data type
The attributes are the minimum configuration units that can be transmitted between a Network
Element and the OAM platform. Each attribute is associated with a data type, which can be either
a simple atomic type or a complex type.
The main atomic types are: Integer, Decimal, Hexadecimal, String,
Complex types are: List, Table, Sequence, Set, Choice.
Object versioning
A CM XML file may include objects of different versions. Each root object must indicate its version,
which applies by default to the whole nested objects. Cluster object.
The cluster information gives the list of clusters that support the unshared / shared resources
instantiated in the CM XML. This information is used by applications that have to deploy theses
resources on several ROCs.

3.4 Snapshot Description
WPS
3 1 22

A snapshot is an image of a network configuration at a given time.

The snapshot gives the list of the raw data that build the objects of the configuration.
For example, the RNC parameters, including the different nodes of the RNC, are described in the
snapshot.
Among other components, the following ones are described in the standard snapshot:
the BTS parameters,
the ATM profile,
UTRAN interfaces.
The general characteristics of the operator are also included.

3.5 Workorder Description
3 1 23

The XML workorder format (*.xwo) is used to express the delta between two snapshots. This format
embeds the XML elements common to the snapshot format, excepted the specific elements showing the
differences between two snapshot trees. It is the container required for importing data to low-level
applications or between end-users applications.
The XML workorder file, may contain multiples work-orders, thus a super container is used to
encapsulate them. It is the root element of this file, as like the snapshot root element.
The XML workorder file embeds both object instances and associated operations. The operations allowed
by the workorder are:
Create
Delete
Reset
Change Version
Modify
The current network state is obtained by the interpretation of the workorders on top of a reference
snapshot, defined as the initial state.

3.6 Template Description
3 1 24

Apart from the mandatory parts common to all CM XML files, there are few generic items that can be
described when looking at a template source file.
As we have said earlier, a template contains generic parameters applying to a large number of objects
and/or sub-objects.
The template structure mainly depends on the type of objects the template refers to:
ATM profile
RAN templates
Passport templates
RRM templates.



for this module
3 1 25


End of Module
3 1 26


41
Section 4
WiPS Tools
Module 1
WiPS Tools
9352 WiPS

Blank Page
412
WiPS Tools WiPS Tools

Document History
Edition
Date
Author
Remarks
01
2010-04-08
GOMEZ Cline
First edition

Module Objectives

Describe
List
Explain
Identify ...
413


414

Table of Contents
Page

1 Checks
1.1 Checks Overview
1.2 Running Checks
1.3 Check Profiles
1.4 Check Sessions
1.5 Correcting Errors
2 Template Management
2.1 Templates Types
2.2 Templates Creation
2.3 Templates Import
2.4 Templates Global Management
2.5 Templates Individual Management
2.6 Template Propagation
2.7 Templates Migration
3 Datasets
3.1 Datasets Definition
3.2 Network Tab/Datasets Creation
3.3 Workorders Tab/Datasets Creation
3.4 Checks Tab/Datasets Creation
3.5 Datasets Conversion
3.6 Dataset Based Operations
3.7 Datasets Elements Edition
4 Workspace Management
4.1 New Workspace
4 1 5 4.2 Workspace Contents
9352 WiPS 4.3
9352 WPS
UAO7 UTRAN
Configuration
Saving
the
Workspace
5 Snapshot Management
5.1 Snapshot Management Overview
5.2 Snapshot Import Modes - Overview
5.2.1 Dumping Previous Network
5.2.2 Merging Networks
5.2.3 Changing Initial Snapshot
5.2.4 Rebasing
5.2.5 Delete Mode
5.2.6 Snapshot Import Report
5.3 Snapshot Export Mode
5.3.1 Full Network Configuration Export
5.3.2 Partial Network Configuration Export
6 Workorder Management
6.1 Workorder Import
6.2 Workorder Import Report
6.3 Workorder Basic Operations
6.4 Workorder Changes Inhibition
6.5 Clearing Inhibition Tags
6.6 Recomputing Planning View
6.7 Purging Inhibition Tags
6.8 Merging Misaligned Network Changes
6.9 Merging Aligned Network Changes
6.10 Merging Consecutive Workorders
6.11 Workorders Export
7 Data Sharing
7.1 Shared Workspace Management
7.2 Synchronization Status
7.3 Synchronization Management
7.4 Publish Resource

7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61

Page

7.5 Retrieve Resource
7.6 Conflicts Management
7.7 Live Server Repository
8 Neighboring Management
8.1 End-to-End CM XML Interface
8.2 Cell Planning Import Wizard
8.3 3G-2G Neighboring Management
8.5 3G-3G Neighboring Management Features
8.6 3G-3G Neighboring Management/FDDCell Deletion
8.7 UMTS-CDMA Neighboring Management
9 Audit Reporting Automation
9.1 Running Audit
9.2 Audit Profiles
9.3 Audit Sessions
9.4 Audit/Key Mask and Template mask
9.5 Audit Report
416


62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
1 Checks
417


1 Checks
1.1 Checks Overview
Report
Checks
Network
Configuration
Engineering Checks
Model Checks
418

WPS provides a powerful integrated tool that offers a wide range of consistency checks to ensure the
integrity of the configuration data prior to activation on the live network.
These checks reduce the risk of service impacts from incorrect configuration data being downloaded into
the live network.
Two main types of checks are available:
Model Checks verify that parameter values are of the correct type and fall into allowed value
ranges. These checks are automatically done during the edition step.
Engineering Checks verify that configuration data follow built-in engineering rules. The rules cover
both internal NE configuration and connections between NEs. These checks can be launched from
any network element.
The network checker detects errors and can apply automatic correction in some cases. These corrections
are based on underlying engineering rules.

1 Checks
1.2 Running Checks
419

Checks are directly launched from the Network Tree. They can be launched on the whole network or on
objects priory gathered by the user in an objects set (via multiple selection in the network tree).
The check session is dynamically initialized with the list of checks relevant to the selected objects set.
By default all the relevant checks are selected as part of the new check session and they all will be
launched.
In the Check Window, all the custom checks to perform are displayed. This is where they can be
selected/unselected and where the Autofix feature can be activated or not whenever applicable.
After validation, the check session is performed, check by check.
Check sessions are stored in the Workspace Tab, below the Workorders stack.

1 Checks
1.3 Check Profiles
4 1 10

Datafillers can define their own check profiles.

These profiles can be edited, modified, deleted and selected before launching a check session.
At the creation, a check profile contains all the checks available in the system. Some of them can be
removed from the profile.
The check profile offers the Smart Table functions, such as filter, sort and export profiles as HTML files.
The check profile allows the following operations:
enable/disable a check
enable/disable all the checks
activate/deactivate the autofix characteristic for a check
filter on cell value for a check.

1 Checks
1.4 Check Sessions
4 1 11

Once the check session has been performed, the check sessions list available in the Checks tab is
updated.
The check session summarizes all the information relative to the checks that have been selected and
launched:
NEs on which the checks have been performed
date and time
list of selected checks (available under the checks tab)
results of the checks (available under the errors tab).
Any check session that have been created earlier can be deleted or re-launched. The corresponding
report can be saved as an XML file.
Under the errors tab, browsing the errors list gives information about:
erroneous objects and associated error severity (Error or Warning)
checks description and associated error message
hints on corrective action to be performed.

1 Checks
1.5 Correcting Errors
Set the attribute
4 1 12

Double clicking on any of the errors message displayed under the Errors tab leads directly to the
incriminated object in the Network Tree. It is then possible to jump back and forth from the Check
Session to the Network Tree in order to progressively fix all the detected errors.
Once some corrective actions have been performed in the Network Tree, the whole Check Session can
then be re-launched in order to analyze what are the results of the parameters modifications and if the
detected errors have been successfully corrected.

4 1 13


2.1 Templates Types
Explicit
Templates
Implicit
Templates
4 1 14

Creating templates is based on the existing Network Element organization. A Managed Object Instance
(MOI) must be chosen as the root object for building a new template. Two types of templates are
available: Templates subtree & Unitary templates.
Unitary templates apply to one and only one instance.
Template subtrees apply to an instance and one or more of its children. For example, a template
subtree may capture a NodeB and its children as shown on the above slide.
Identifiers are part of the template definition in the case of a subtree template, except for the root of
the subtree. The identifiers of the children are in the template subtree, whereas the identifiers of the
root object are not.
Default Templates
Some templates are automatically proposed at MOI creation. In the current workspace, there is only
one single default template per MOC type & version.
Implicit/Explicit Templates
While Explicit Templates are user selectable and appear in the Wizards GUI, Implicit Templates are
automatically called by the Wizards with no control from the user. Therefore Implicit Templates
names should not be deleted and their names should not be changed.

2.2 Templates Creation
4 1 15

Thanks to the WPS tool, the datafiller can perform the following operations:
create new templates from a selected MOI (instance only or instance and subtree),
modify the existing templates,
set a template as the default template to be used during Managed Object (MO) instantiation,
duplicate templates (cloning),
import/export templates in XML format.
Creation
Creating templates is based on the existing Network Element organization. A Managed Object Instance
(MOI) must be chosen as the root object for building a new template.
From the WPS main window, select the Network tab.
Select the element to be referred to as root object.
Select Create template : the Template Creation window opens.
If the root object includes sub-components, click the Capture subtree box to make sure the subcomponents description will be associated with the new created template.

4 1 16

Thanks to the WPS tool, the datafiller can perform the following operations:
create new templates from a selected MOI (instance only or instance and subtree),
modify the existing templates,
set a template as the default template to be used during Managed Object (MO) instantiation,
duplicate templates (cloning),
import/export templates in XML format.
Import templates
User has the possibility to import one or several template files just by retrieveing thel via the browse
facility of the import/export wizard.
For each new template file import WPS performs an analyse of the templates to be imported,
allowing the user the to filter some unwanted templates.

2.4 Templates Global Management
4 1 17

Templates Current Source.

When a template is imported/created/updated, a source is associated to each template instance and to
each template attribute. Below are described the main steps to follow in order to set the default source.
Select the Templates object then select Set current source... from the contextual menu (right
click),
The Set current source window opens. Fill the current source then OK.
Distilling template
In order to minimize template file size, template attribute set to model default value can be discarded.
The main steps to perform template distillation are described below:
Select the templates to be distilled.
Either from the contextual menu (right click) or from the Templates menu, select the Distill...
operation.
In the Distill templates window Tick/untick the Purge empty templates, then Yes.

2.5 Templates Individual Management
4 1 18

Modifying templates means changing the values of one (or more) attribute(s) for one specific template at
a time.
Here are the main steps of the procedure to be performed:
1. From the WPS main window, select the Templates tab.
2. From the templates tree, select the template to be modified.
3. From the Template panel (right part of the window), select the attribute to be modified within the
table.
4. Fill in the new value, according to its type (integer, string, link, ) Open the Description box to
get more information about the attribute characteristics.
5. Validate your modification by clicking the appropriate button (either the Set or Unset).
Default templates
Some templates are automatically proposed at MOI creation. In the current workspace, there is
only one single default template per template type/version.

2.6 Template Propagation
4 1 19

This procedure allows the datafiller to propagate a set of parameters towards a given network object
(MOI). The set of parameters is based on a template. The target MOI inherits the attributes & values of
the Template.
Propagation relies on the existing Network Element organization. A Managed Object Instance (MOI) must
be chosen as the root object for propagation purposes.
Here are the main steps of the procedure to be followed:
1. From the WPS main window, select the Network tab.
2. Select the network object to be referred to during template propagation.
3. Select Propagate template in the Templates menu.
4. Choose a template among the Available templates list.
5. Select the parameters values to be applied among the list of parameters.
6. Click the Propagate button to launch the operation.

2.7 Templates Migration
4 1 20

A template is always associated with an object type and the version of this object. The below procedure
describes the main steps to create a template applying to another version of the same object type.
From the WPS main window select Templates tab.
From the templates tree, select the templates to be migrated (belonging to a unique version).
Either from the contextual menu (right click) or from the Templates menu, select the Migrate...
operation.
In the Migrate templates window fill the Target version, then Apply.
A Migrate templates from 'source version' to 'target version' window opens with a progress bar.
When completed the new template appears in the templates tree.

3 Datasets
4 1 21


3 Datasets
3.1 Datasets Definition

Dataset
MOI
MOI
...
MOI
Network Tree
Partial Deletion
Dataset
MOI
MOI
...
MOI
Partial Export
Checks
Dataset
MOI
MOI
...
MOI
4 1 22
Global Update

Instead of performing the same operations on similar objects, datasets can be defined as lists of objects
that are going to be used in the same way.
WPS provides the opportunity to create lists of objects, which can be manipulated together all at one go,
once they have been gathered into a single Dataset.
The datafiller can perform various operations upon datasets:
create a new dataset from one or several object(s) selected from the network tree
append one or several object(s) to an existing dataset
remove one or several object(s) from an existing dataset
delete a dataset
convert a dataset into another dataset, in order to add more objects to the new dataset
...

3 Datasets
3.2 Network Tab/Datasets Creation
4 1 23

You can choose either part of the network (multiple selection of MOIs) or one existing dataset when you
want to create a new one.
Here is the procedure to be performed when starting from a MOI:
1. From the WPS main window, select the Network tab.
2. In the network tree, select the object to become part of the data set.
3. From the Datasets menu, select Add dataset > new Dataset
4.
Fill in the Dataset Name and validate by clicking OK.
5.
The new data set is displayed in the datasets tree.
Datasets contents can be modified the same way, adding some MOIs selected in the Network Tree to
already existing datasets.
The procedure used to create a new dataset when starting from an existing dataset is explained in the
next slide.

3 Datasets
3.3 Workorders Tab/Datasets Creation
4 1 24

Datasets can also be created directly from the Workorders tab by selecting all the Network Elements
modified in any of the Workorders.

3 Datasets
3.4 Checks Tab/Datasets Creation
4 1 25

Datasets can also be created directly from the Workorders tab by selecting all the Network Elements
modified in any of the Workorders.

3 Datasets
3.5 Datasets Conversion
4 1 26

Here is the procedure to create a new Dataset when starting from an existing dataset:
1. From the WPS main window, select the Dataset tab.
2. In the datasets tree, select the object to be converted.
3. From the Datasets conversion panel (right part of the window), select the different mandatory
items:

Input type (type of object from which the navigation starts)

Navigators (at which level the conversion must start in the tree-structure: children,
ancestors, )
Output type (the type of object to keep in the output data set)
Output dataset (the target dataset where the object(s) will be added).
The data set list is updated in the Datasets tree.

Datasets contents can be modified the same way, adding the result of the Dataset Conversion to already
existing datasets.

3 Datasets
3.6 Dataset Based Operations
4 1 27

This procedure allows the datafiller to propagate a set of parameters towards MOIs previously gathered
into a dataset. The set of parameters to be propagated is based on a template. The target MOIs inherit
the attributes & values of the Template.
Here are the main steps of the procedure to be followed:
1. From the WPS main window, select the Dataset tab.
2. Select the Dataset to be referred to during template propagation.
3. Select Propagate template in the right-click menu.
4. Choose a template among the Available templates list.
5. Select the parameters values to be applied among the list of parameters.
6. Click the Propagate button to launch the operation.

3 Datasets
3.7 Datasets Elements Edition
4 1 28

All the MOIs of the Datasets can be edited in the exact same way as they are edited in the Network Tree,
the Object Editor which is displayed in the right part of the window being the same as the one which is
available while browsing the Network Tree.
Sorting the attributes of the various MOIs offers the opportunity to perform global parameters
modifications.

4 1 29


4.1 New Workspace
.wps format is release dependent

4 1 30

WPS handles only one single Workspace at a time. Creating a new Workspace or opening an existing
Workspace therefore erases the contents of the current Workspace.
To work on a new Workspace the two possible actions are:
The Open option which allows the datafiller to download a new workspace into the memory of his
WPS workstation.
The New Workspace option which allows the datafiller to start working in a new empty
Workspace.
Note
In order to be downloaded, a Workspace must have been created with the exact same WPS release as the
one of the tool which is currently used as the .wps format is not compatible between different WPS
releases.

4.2 Workspace Contents
4 1 31

The workspace can be seen as a set of configuration data and working environment data gathered into
one global container. It contains all the data that can be managed within WPS:
MOIs of the Network Tree,
Snapshot and Workorders,
Templates,
Datasets,
Check Sessions,
Check Profiles.
Note
Creating a New Workspace or Opening an existing Workspace does not erase the contents of the Network
Tab and the Check Profiles. That is, the loaded Templates and the existing Check Profiles are kept
independently of the current Workspace.

4.3 Saving the Workspace
4 1 32

Saving the Workspace allows to store all its components (including current Templates) into a .wps file.
There are several ways to save the Workspace depending mostly on how the Workspace was created.
If the current Workspace is a New Workspace the Save option must be used.
If the current Workspace was opened using an existing .wps file, it can be overwritten using the Save
option or renamed using the Save as option.

4 1 33


5.1 Snapshot Management Overview
4 1 34

Snapshot management is achieved with the help of the WPS Import/Export Wizard. This specific Wizard
handles all the CM XML files import export functionalities.

4 1 35

Using the Import/Export Wizard, Snapshot import is necessarily performed using one of the four following
modes:
Replace initial snapshot and keep existing workorders,
Replace initial snapshot and discard existing workorders,
Merge with planned network,
Resynchronize the planned configuration with new snapshot.
The Edit Filter window offers the possibility to run a top-level objects analysis before performing the
Snapshot import. This way the user can have a first look at the contents of the CM XML file and possibly
unselect non-wanted subtrees.

5.2.1 Dumping Previous Network
Initial
Snapshot
Network
Tree
Initial
Snapshot
Network
Tree
A
B
C
C
Workorders
Workorders
A
A
E
B
C
4 1 36
New Snapshot

Replace initial snapshot and discard existing workorders

This mode creates a workspace with a new initial snapshot and no workorder at all.
In other words, it builds a new network view resulting from the new snapshot with no workorder in
the stack.
Typically, this situation can occur at the very beginning of the datafilling tasks. No network is
loaded yet in WPS. This method is convenient to start with the actual initial snapshot.
Case

5.2.2 Merging Networks
Initial
Snapshot
Network
Tree
Initial
Snapshot
E B F H
Workorders
Workorders
A
A
H
B
C
4 1 37
C
C
Network
Tree
New snapshot
A
E
A
B

Merge with planned network

This mode automatically creates a new workorder containing the modifications (creation and
update commands) generated by the imported file (snapshot).
The initial snapshot is not modified. The current view of the network shows the results of the
merger.
The delete operations are not mentioned in the new workorder.
This load mode is helpful to add some separate modular datafilling parts to the existing network
under construction. For instance, this case can apply to the addition of a neighboring plan
resulting from the CIQ.
Case

5.2.3 Changing Initial Snapshot
Initial
Snapshot
Network
Tree
Initial
Snapshot
A
B
A
E
C
C
Workorders
H
Workorders
A
A
E
Network
Tree
New Snapshot
4 1 38
A
E
B
C

Replace initial snapshot and keep existing workorders

This mode replaces the initial snapshot by the new imported one (swapping).
It does not modify the workorders stack of the workspace. The current view is updated according
to the new configuration data.
If some operations described in the workorders cannot be applied to the new snapshot, such as
the creation of a NE, these operations are set to disabled and an error message is raised during
the snapshot load.
A disabled modification means the result of the operations in question is not displayed in the tree
view.
Up to some extends, this load mode can be used when updating the initial snapshot with a new
one coming from the OMC (NMS). It can also be useful when the initial snapshot must be
customized to meet future evolutions.
Case

5.2.4 Rebasing
Initial
Snapshot
Network
Tree
Initial
Snapshot
B H
C
C
New Workorder
A
E F B
Workorders
A
C
C
Network
Tree
E F B
C
B
F
New Snapshot
4 1 39

Resynchronize the planned configuration with new snapshot

This load mode (also called rebasing) replaces the initial snapshot by the new imported one
(coming from the main server) and discards all the existing workorders.
It also generates a new workorder designed to be synchronized with the new configuration.
This new workorder does not contain the cumulative list of operations performed by the previous
workorders.
The synchronization workorder only encompasses all the operations required to describe the
differences between the initial snapshot and the new one.
Afterwards, the current view of the network is unchanged.
The objective of this mode is to ensure a synchronization of configuration data between W-NMS
and WPS platforms. In other words, the planning view handled by the datafillers must match the
updated view handled by OA&M staff members at the OMC.
Case

5.2.5 Delete Mode
Initial
Snapshot
Network
Tree
Initial
Snapshot
Workorders
Workorders
A
A
B
C
4 1 40
C
C
Network
Tree
A
B
New snapshot
A
B

From the Import and export wizard, when the user selects the Import snapshot action, a new mode "delete
with planned network" is now available. All objects present in the snapshot will be deleted from
Network and WPS will generate the appropriate Workorder.
If an object in the snapshot has children in Network, they are deleted as well.
For deletion are taken in account only the objects from the imported snapshot that dont have children. All
the remaining objects will be ignored.
This feature is used because third party Design Tools are able to work only with snapshots, and not with
workorders.

5.2.6 Snapshot Import Report
4 1 41

Once the Snapshot import is started, you can follow its progress in upper part of the report window.
During the import, WPS performs error checks and three kinds of messages may appear as shown in the
Report window shown above.
Severity
Information messages
Warning Messages
Error Messages
When the Snapshot Import is over, a report can be saved (XML format).

4 1 42

(Snapshot management is achieved with the help of the WPS Import/Export Wizard. This specific Wizard
handles all the CM XML files import export functionalities.)
Exporting snapshots is a very simple operation. The .xcm file generated by the snapshot export includes
the description of all the objects of the network. It gives the picture of all the NEs created in the Access
Network, without mentioning the commands of the workorders.

5.3.1 Full Network Configuration Export
4 1 43

Exporting snapshots is a very simple operation. The .xcm file generated by the snapshot export includes
the description of all the objects of the network. It gives the picture of all the NEs created in the Access
Network, without mentioning the commands of the workorders.

5.3.2 Partial Network Configuration Export
4 1 44

Partial export can also be performed.

Selection of the NEs to be included in the exported Snapshot can either be performed in the Network
Tree or using some previously defined Datasets.
In our example above, only one BTS equipment is going to be exported as a snapshot, under the *.xcm
format.

4 1 45


6.1 Workorder Import
4 1 46

Within WPS, the workorder import operation allows to add new workorders on top of the current
workorder.
As soon as the operation has been performed, the new imported file automatically becomes the current
workorder and the current view takes into account the changes due to the addition of this new
Workorder inside of the Workorders Stack.
There are two modes of workorder import:
-
from local file system,
from live server repository.
In short, the CM XML interface is dedicated to the exchange of workorders between applications:
WPS to WPS platform: in use during multi-user collaboration
WPS to W-NMS: in use during activation phase.

6.2 Workorder Import Report
4 1 47

Once the Workorder import is started, you can follow its progress in the upper part of the report
window.
During the import, WPS performs error checks and 3 kinds of messages may appear as shown in the
Report window shown above.
Severity
Information messages
Warning Messages
Error Messages
When the Workorder Import is over, a report can be saved (XML format).

6.3 Workorder Basic Operations
4 1 48

The Export the Workorders Stack is displayed under the Workorders tab. This is where the Workorders
management basic operations can be performed.
Right-clicking on any of the Workorders offers the opportunity to:
Set the selected Workorder as Current Workorder,
Insert a new Workorder before the selected one,
Delete the selected Workorder,
selected Workorder.

6.4 Workorder Changes Inhibition
4 1 49

It is possible to inhibit MOI changes contained in a workorder. An inhibited change is not applied during
the network configuration computation dynamically performed by the system.
By default, changes are not inhibited.
The system manages an inhibition status on MOI changes and also an inhibition status on attribute
changes.
For attribute value changes, the inhibition status can be true or false.
For MOI changes, the inhibition status supports three states:
true: all changes are inhibited
false: no change inhibited
partial: some attribute changes inhibited
When some changes are inhibited the resulting current view is not anymore representative of the
Workorders contribution to the Initial Snapshot modification.
The Workspace is then said to be Unsynchronized with the Network Tree.
Note
Inhibited changes are not exported in the XML workorder export operation.

6.5 Clearing Inhibition Tags
4 1 50

The simplest way to get rid of all the inhibited changes is to use the Clear Inhibition Tags command from
the right-click menu of the Workorders Stack. This will disinhibit all the MOIs changes and attributes
changes that have been inhibited in the various Workorders of the stack.
After completion of this operation the original state of all the Workorders of the stack is restored but the
Workspace remains tagged as unsynchronized.

6.6 Recomputing Planning View
Initial
Snapshot
Network
Tree
Initial
Snapshot
E
D
C
C
E B D
Workorders
Workorders
A
H
A
B
A
D
4 1 51
Network
Tree
A
B

Selecting the Recompute Planning View command forces WPS to take into account all the inhibition tags
spread among the various Workorders of the Workorders Stack.
After completion of this operation, the Workorders Stack remains unchanged and all the inhibition tags
stay untouched.
In most of the cases recomputing the planning view is a prerequisite operation to be performed prior to
any Workorders Merging operation.

6.7 Purging Inhibition Tags
Initial
Snapshot
Network
Tree
Initial
Snapshot
E
D
A
H
C
C
Workorders
A
B
A
D
B H
C
Workorders
Network
Tree
4 1 52

Selecting the Purging Inhibition Tags command delete all the change that have been tagged in the
various Workorders of the stack.
After completion of this operation the original content of the Workorders is modified according to their
respective inhibited changes but the global structure of the Workorders Stack remains unchanged; same
Workorders number, naming and ordering.
The resulting Workspace remains unsynchronized awaiting for the Recomputing Planning View operation.

6.8 Merging Misaligned Network Changes
Initial
Snapshot
Network
Tree
Initial
Snapshot
E
D
Workorder
A
H
A
B
A
D
4 1 53
B H
Workorders
C
C
Network
Tree

Merging the network changes aims at finalizing a new Workorder before exporting it towards W-NMS in
order to handle as few files as possible when activating the change on the live network.
The purpose of this operation is to take into account all the changes of all the Workorders belonging to
the Workspace in order to recompute one single finalized Workorder.
After completion of this operation the entire Workorders Stack collapses and is replaced by the merged
Workorder.
The Merging Network Changes operation does not take care of the inhibition tags. Therefore the new
merged Workorder only embeds the changes needed to reach a network state represented by the current
view starting from the view corresponding to the Initial Snapshot. This is the reason why, in most cases,
recomputing the planning view is a prerequisite operation to be performed prior to any Workorders
Merging operation.

6.9 Merging Aligned Network Changes
Initial
Snapshot
Network
Tree
A
B
E
D
Initial
Snapshot
D
B H
E B D
C
C
C
Workorders
Workorder
A
H
Network
Tree
A
B
A
D
4 1 54

As explained in the previous slide, merging unsynchronized network changes may lead to inconsistent
results.
The four main steps of the procedure recommended to finalize a workorder before exporting it towards
W-NMS are the following:
1. Purge the inhibition tags if any
2. Recompute the planning view
3. Merge the network changes
4. Export the new merged Workorder.

6.10 Merging Consecutive Workorders
Initial
Snapshot
Network
Tree
Initial
Snapshot
E
D
H
D
C
C
C
E B D
Workorders
A
A
E
Workorder
A
4 1 55
Network
Tree

This feature offres the possibility to merge not only all network changes into a single work-order but also to
merge changes of several selected consecutive work orders.
WPS users have a better control of changes granularity which important in particular in activation manager
context (one session one work-order).
Again, merging unsynchronized workorders may lead to inconsistent results.

6.11 Workorders Export
4 1 56

The objective of the workorder is to record all the modifications performed on the configuration data
during a session. Exporting a workorder means gathering a set of preliminary operations into one single
file.
The datafiller can choose between 2 types of operations:
- export all the workorders built on top of the snapshot so far,
- export one specific workorder (whether current or not) among others.
On single Workorder export, a reverse Workorder is systematically created. It contains all the elementary
operations required to step back to the original configuration once the original Workorder has been
activated. In other words, it acts as the undo option regarding the network building in progress.
On multiple Workorder export no Reverse Workorder is created.
Note
Inhibited changes occurring in the network are not exported through the XML workorder export
operation.

7 Data Sharing
4 1 57


7 Data Sharing
7.1 Shared Workspace Management
4 1 58

Data Sharing requires the connection properties of the Main Server to have been previously set in WPS. If
so, Shared Workspaces can be simultaneously accessed and possibly modified by several WPS users.
WPS user has the ability to create, delete or open the Shared Workspaces that are stored at the Main
Server level.
Opening or creating a Shared Workspace deletes the contents of the local Workspace and replaces it with
the contents of the Shared Workspace.
Making a local copy of the Shared Workspace retrieves the files from the server and ends the sharing
between WPS and the Main Server.

7 Data Sharing
7.2 Synchronization Status
4 1 59

WPS dynamically handles the synchronization state of each resource (Snapshot and Workorders) of the
Workspace.
WPS displays on the top right of the window the last refresh date or the synchronization / desynchronization status, based on the notifications received from MS, plus a link to the log table, which
contains a list of all the actions performed on the shared workspace by all the users.
In the log table, 2 actions are available to the user:
Purge: remove one or more entries from the table
Retrieve: by selecting one or more lines and right click, the user will be able to retrieve the
resource(s) from the shared workspace and synchronize its local workspace partially or completely.
In workorder view, when the shared workspace is modified by an user,the synchronization status is
automatically updated as follows:
Synchronized: the resource is aligned with the workspace repository
Modified in repository: a new version of the resource is available on the repository
WPS also provides at the bottom of the Workorder Stack the Synchronization Status of currently selected
Workspace resource.

7 Data Sharing
7.3 Synchronization Management
4 1 60

Modifying a Workorder locally directly updates the resource Syncronization status only on the WPS station
that has been used to modify the Workorder. It means that the Main Server is not aware of the changes
as long as the WPS user has not been published.
The refresh Synchronization Status enables to know if some changes have been performed on the Server
Repository while WPS Workspace was open.
Running the Synchronize Shared Workspace operation forces the publishing of the changes on the Main
Server and eventually updates the contents of the local version of the Shared Workspace.

7 Data Sharing
7.4 Publish Resource
4 1 61

Publishing Resource sends the changes to the Main Server so that the Shared Workspace is updated for all
the WPS users that may used it later. When all resources have been published, and if no other conflict is
detected, the synchronization is restored between WPS and the Main Server.

7 Data Sharing
7.5 Retrieve Resource
Data Sharing
4 1 62

Retrieving the resource from the Main Server enables to refresh the local version of the Shared
Workspace using the last version of the resource stored at the Main Server level.

7 Data Sharing
7.6 Conflicts Management
4 1 63

When several WPS users are simultaneously making changes on the same resource, some conflicts may
then be detected when WPS user tries to publish its own contribution.
In such a case WPS rises a warning to prevent from any overwriting of changes.
To be able to solve any changes conflict problems, WPS user has the possibility to confirm changes
publishing once they have been detected by the tool.

7 Data Sharing
7.7 Live Server Repository
4 1 64

The Main Server can also be used as a file server repository.

This allows WPS users to save locally their Workspaces on their own machine while directly exporting
their Workorders to the Main Server.
The Workorders stored in the Live Server Repository are managed independently from the Shared
Workspaces also stored on the Main Server.

4 1 65


8.1 End-to-End CM XML Interface
CP XML
CM XML
WPS Access
Main Server
Cell Planning Tool

Activation
Live Network
4 1 66

Radio configuration is done by the mean of a Cell-Planning Tool. Once the planning operations are
completed, the resulting plans, described in a CP XML format, are imported into WPS using the Cell
Planning Import Wizard available at the top level of the WPS network tree.
Checks could be run, and manual modifications could be done in WPS for coherency/consistency issues.
Workorders resulting of the WPS processing are loaded into W-NMS in order to apply the new plans on the
managed network.
WPS Cell Planning Import Wizard simplifies the integration of WPS with Cell Planning Tools by allowing
flexible identification of radio objects.
Working with this interface, identification of cells & neighbors is independent from network topology but
rather relies on standard identifiers commonly used in cell planning tools (cell name, localCellId,...).
This interface addresses both 2G & 3G radio links & parameters.
Besides, new loading modes have been defined for WPS, thus allowing fast neighboring plan definition
and optimization.

8.2 Cell Planning Import Wizard
4 1 67

This operation allows to import a Cell Planning file, and to update WPS Network view according to the
content of this file. In the Cell Planning file, Objects are sorted in two categories:
1. The serving objects
They cannot be created nor deleted through a cell planning import, they are only updated if they
are present previously in the system.
The serving objects are: BTSCell, FDDCell, AntennaAccess, Site and GSMCell.
Note
GSMCell has a special behavior: even if it is considered as a serving object, it can be created
during the creation of a new GSMNeighbouringCell.
2. The children objects

They can be updated deleted and created through Cell planning import.
The children objects are: UMTSFDDNeighbouringCell, GSMNeighbouringCell, Sector and

AntennaSystem. The CellPlanning file is supposed error free, thus it will not be checked before
the load.

4 1 68

This operation allows the creation of neighboring links between a serving FDDCell and one or more
GSMCells.
The operation shows, the serving FDDCell, by displaying some parameters that can be useful for the
creation of the neighboring link.
Thereafter, the operation displays a table listing all already existing Gsm Neighboring Cells (a row
corresponds to one GSM Cell), and a middle section which serve to add new GSM Neighboring Cells.
To select a GSM Cell that will be added to the neighboring list the user can select one of the gsmCell cgi
that are defined in the selected RNC/userlabel gsmNeighbor/0 if the serving FDDCell is parented by a
Serving RNC. The selection can also be done in a network level; the user can select one of the GSM Cell
cgi that are defined in all RNC/userlabel gsmNeighbor/0. if no RNC is selected the user should enter
(edit) the GSM Cell cgi of the GSM Cell that will be added to the neighboring list.
After selecting the GSM Cell, the user should enter the parameters needed for the creation of the new
GSM neighboring link and select the OK button from the Add column.

4 1 69

This operation allows the creation of neighboring links between a serving FDDCell and one or more target
FDDCells that are already defined in the network and that are parented by existing RNCs or alien
FDDCells.
The operation window displays a table listing all already existing Neighboring FDDCells (a row
corresponds to one FDD Neighboring Cell), and a middle section which serves to add new FDD Neighboring
Cells (target FDDCells). A FDDCell to be added to the table can be chosen by two methods:
By selecting the RNC/userlabel, the NodeB/userlabel (that parents the target FDDCell) and the
target FDDCell/userlabel,
By entering the rncid of the RNC parenting the target FDDCell and the target CellId
When using one of the above methods, the parameters corresponding to the other method are set
accordingly by the operation,
After selecting the target FDDCell the user should enter the parameters needed for the creation of
the new neighboring link and for the creation of the reciprocal neighboring link if needed.

8.5 3G-3G Neighboring Management Features
4 1 70

An alien FDDCell is added by manually editing the fields labeled RncId, CellId, MCC and MNC, and
after that by filling all the mandatory fields.
Also, the 3G-3G Neighboring Management offers the following features:
Delete/modify already existing 3G-3G neighboring links capabilities
Double window to display outgoing/incoming links
Check and provide visual indicators for model errors (filling up mandatory parameters)

8.6 3G-3G Neighboring Management/FDDCell Deletion
4 1 71

The new operation Delete One FDDCell provides an easy way to delete a FDDCell, with taking in account
the existing neighbours, providing a consistent network (without non-reciprocities because of cell
deletion).

8.7 UMTS-CDMA Neighboring Management
4 1 72

This operation allows the creation of neighboring links between a serving FDDCell and one or more 1xRTT
cells.
1xRTT cells are identified by the following IDs which ensure their uniqueness in the network: cellId, MNC,
MCC, nId, sId
CellId have two formats: bscId, BtsId, SectorId (format1) or Cdma1xCellId, SectorId (format2).
Depending on the coding scheme (if set for RadioAccessService or if not set) depending on the cellId
format, only one of the two identification formats is taken into account.
The input parameter Select cdma1xCell is displayed as follow:
For format1:
Cdma1xCell/<rdnId> (BscId/<cdma1xCell.cellId_format1_bscId>, BtsId/<cdma1xCell.
cellId_format1_btsId>, sectorId/<cdma1xCell.cellId_format1_sectorId>),
MCC/<cdma1xCell.MobileCountryCode>, MNC/<cdma1xCell.MobileNetworkCode>,
sId/<cdma1xCell.sId>, nId/<cdma1xCell.nId>
For format2:
Cdma1xCell/<rdnId> (Cdma1xCellId/<cdma1xCell.cellId_format2_Cdma1xCellId>,
sectorId/<cdma1xCell.cellId_format2_sectorId>), MCC/<cdma1xCell.MobileCountryCode>,
MNC/<cdma1xCell.MobileNetworkCode>, sid/<cdma1xCell.sId>, nId/<cdma1xCell.nId>
Note that this operation will deal only with RNC UA5.0 for the serving RNC as well as for the other RNCs
present in the snapshot.
DummyUmtsNeiFddCellList:
Dummy Umts Neighbouring links (0-16 links) can reference up to 10 Cdma1xCell.
A Cdma1xCell can be referenced by more than one dummy Umts Neighbouring Fdd Cell List, in the
operation the user can select this list by setting the input DummyUmtsNeiFddCellList.

4 1 73


9.1 Running Audit
4 1 74

This feature provides a new operation to perform an automated comparison between a snapshot and a set
of templates on an object by object basis. This would be similar to what can be carried out manually
using the compare with template and tabular editor function, but this is fully automated. So an automatic
report is
generated describing the discrepancies between a standard configuration and the actual configuration on
the network.
The Audit management is implemented in WPS in a similar approach as the check session management:
Audit Sessions and Audit Profiles are managed in the new Audit tab
Audit on a selected list of objects is launched by a new command Audit
Audit Report is available in the new Audit tab. it can be saved into a set of html pages, for publication or
archival purpose.

9.2 Audit Profiles
4 1 75

An audit profile is a set of MOC from the current view of the network refined by filters and associated with
a series of templates they will compare to.
The filter allows to remove instances on a per MOC basis, in the later case the filter will be applied on the
initial selection of MOI, the profile is included in.
These profiles can be edited,modified, deleted and selected before launching an audit session.
The audit profile offers the Smart Table functions, such as filter, sort and export as HTML files.
The audit profile allows the following operations:
Select/deselect MOCs
Select key mask and/or template mask
Select the template used for comparation

9.3 Audit Sessions
4 1 76

An audit session is made of an Audit profile and an initial selection of MOI. The Audit Session will be
materialized as an additional tab in WPS and will have the same management than Check Session.
The audit session summarizes all the information relative to the audits that have been selected and
launched.
Any audit session that have been created earlier can be re-launched or deleted. There is also the possibility
to add the audited objects to a dataset, for further processing.

9.4 Audit/Key Mask and Template mask
4 1 77

Template mask is a way to filter at template level a set of parameters or instances to exclude from the
comparison to that template.
The template mask must allow excluding:
a set of attributes
a set of MOC/MOI
That template mask can be established with a GUI similar to the current template editor.
The key mask provides a way to filter the MOIs that will be audited, based on filtering capabilities similar
with the ones provided by Smart Table functions.

9.5 Audit Report
4 1 78

An audit report is the result of the Audit Session, it captures:

The name of the session
The date and time at which the session was performed
The Initial Selection (**)
The audited MOIs (**)
A synthetic status of the differences between MOIs and templates
The detailed deltas between Templates and MOIs



for this module
4 1 79


End of Module
WiPS Tools
4 1 80


Section 5
WiPS Wizards for UTRAN Creation
and Modification
51
Module 1
WiPS Wizards for UTRAN Creation and Modification
9352 WiPS

Blank Page
512

Document History
Edition
Date
Author
Remarks
01
2010-04-08
GOMEZ Cline
First edition

Module Objectives

Describe
List
Explain
Identify ...
513


514

Table of Contents
Page

1 General Flow of Operations
1.1 WPS WNMS Interface Flows
1.2 Network creation Main Tasks
1.1 NodeB transport Option
1.1 IuPS transport Option
2 Initial OAM Data Setup
2.1 Creating OAM Shared Objects
2.2 Importing Initial Snapshot
3 WPS Workspace Preparation
3.1 Creating a New Workspace
3.3 Creating a New Workorder
4 Configuration Wizards
4.1 Wizards Overview
4.2 Task Oriented Wizards
4.3 Task Status
4.4 Task Tree
4.5 Wizard operation editor
515
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25



516

517


1.1 WPS WNMS Interface Flows

WPS
WNMS
Initial OAM Data

Setup
Common OAM Data
OAM Data
Import
Common OAM Data
Provisioning
Preparation
Configuration Data
Configuration Data
Live Data
Export
Configuration Data
Live Network Data
Activation
Preparation
Activation Data
Import
Activation Data
W orking Sessions
518
S tatic Configuration
D elta Configuration

The general flow of operations associated to the WPS WNMS interface is described in the above
diagram.
Two main constraints have to be verified in this flow:
predefinition of common OAM objects in WPS and WNMS
consolidation of the prepared workorders before import and activation on WNMS.
Additional information about each operation is provided in the following sections.

1.2 Network creation Main Tasks

Network
Cluster, PMcluster Creation
OAM Creation
Operator Creation
NodeB and RNC common

parameters
RNC Creation
NodeB Creation
IuB Creation
IuCS Creation
IuPS Creation
519

Streams Definition: 1 number of IP stream to be added with QoS of 3.

BTS IP Configuration :
1. Local Lan Presence and Dchp Used must equal false.
2. VLan Id must have no value or remain blank.
3. Ip Ran NodeB Address: <operator specific>
4. Gateway:: <operator specific>
UDP port number (heartbeat) equals 65535 unless it is changed under Rnc object.

1.1 NodeB transport Option
5 1 10

From UA07 Alcatel-Lucent shall support the following Node B transport options
ATM only Node B
Hybrid Iub Node B
IP Pseudowire Node B i.e. ATM Iub over a IP MPLS Tunnel (aka Pseudowire). This is supported using
external 7705 SAR at Node B and 7x50 SR at RNC

Native IP Node B (new in UA07)

5 1 11

RNC Iu-PS transport feature has the following benefits:

IP Carrier Grade support
OPEX savings through use of cheaper IP transport.
RNC can be upgraded to IP transport in the field through the addition of two 4ptGigE cards.
RNC natively supports segmentation of the Iu-PS IP domains to ensure support of customer security policies requiring isolation of
these domains
The Alcatel-Lucent RNC today supports ATM only on Iu and Iur interfaces.
This features introduces support for IP interfaces on the Iu-PS interface through a software upgrade and the addition of two
(1+1) 4ptGigE Cards on the RNC.
The following is an overview of this feature
3GPP compliant IP User and Control stacks on the RNC
Investment protection: IP transport is supported by addition of two 4ptGigE cards i.e.
No forklift
o Co-existence of ATM and IP control/user plane stacks on Iu-Ps
Support for IP transport Carrier Grade features
IP network engineering & security
Ability to segment the Iu-PS domains into isolated IP routing domains thanks
to the implementation of dedicated IP virtual routers.
Introduces support for IP on the Iu-PS interface through a software upgrade and the addition of two (1+1) 4ptGigE Cards on the RNC

IP Iu-PS provides:
Co-existence of ATM and IP control/user plane stacks on Iu-PS (via Iu-flex)
Ability to segment the Iu-PS domains into isolated IP routing domains via dedicated
IP virtual routers Protected static routing resiliency on GE/Vlan interfaces IP QOS
capabilities DSCP marking
No IP CAC on Iu-PS

5 1 12

RNC Iu-PS transport feature has the following benefits:

IP Carrier Grade support
OPEX savings through use of cheaper IP transport.
RNC can be upgraded to IP transport in the field through the addition of two 4ptGigE cards.
RNC natively supports segmentation of the Iu-PS IP domains to ensure support of customer security policies requiring isolation of
these domains
The Alcatel-Lucent RNC today supports ATM only on Iu and Iur interfaces.
This features introduces support for IP interfaces on the Iu-PS interface through a software upgrade and the addition of two
(1+1) 4ptGigE Cards on the RNC.
The following is an overview of this feature
Investment protection: IP transport is supported by addition of two 4ptGigE cards i.e.
No forklift
o Co-existence of ATM and IP control/user plane stacks on Iu-Ps
Support for IP transport Carrier Grade features
IP network engineering & security
Ability to segment the Iu-PS domains into isolated IP routing domains thanks
to the implementation of dedicated IP virtual routers.
Introduces support for IP on the Iu-PS interface through a software upgrade and the addition of two (1+1) 4ptGigE Cards on the RNC

IP Iu-PS provides:
Co-existence of ATM and IP control/user plane stacks on Iu-PS (via Iu-flex)
Ability to segment the Iu-PS domains into isolated IP routing domains via dedicated
IP virtual routers Protected static routing resiliency on GE/Vlan interfaces IP QOS
capabilities DSCP marking
No IP CAC on Iu-PS

5 1 13


2.1 Creating OAM Shared Objects
<<BTS>>
BTSEquipment
0..*
0..*
<<RNC>>
RNC
0..*
0..*
Main Server
0..*
0..*
Operator
0..1
RNCCommonParam
Performance Server
5 1 14
0..1
NodeBCommonParam

Here are the objects to be created first:

The 2 clusters stand for the identification of the servers of the OAM platform:
Cluster for the main server
PMCluster for the performance one.
Note
Unlike most network objects, these 2 objects are created without any parameter.
The Operator describes the frequency Band (either UMTS standard or 1900 MHz, for the American
operators), the mobile country code and the mobile network code.
The RNCCommonParameter describes the GSM band used in the network.
The NodeBCommonParameter indicates the list of downlink & uplink frequencies used by the
equipment.

2.2 Importing Initial Snapshot
Main Server
5 1 15


5 1 16


3.1 Creating a New Workspace
5 1 17

Before starting any new datafilling a new workspace should be created to store all the relevant files and
operations relevant to he requested provisioning operations.

5 1 18

Before starting the datafilling operations with WPS, the standard templates delivered by Nortel must be
completed with local engineering parameters.
Once these templates have been downloaded by the datafiller, they remain available for further WPS
sessions, through the Template tab.
Four different types of templates are supplied: RAN templates, Passport templates, RRM templates and
ATM profiles templates.

3.3 Creating a New Workorder
5 1 19

Before starting any datafilling operation, the engineer must create a workorder to welcome the first
mandatory parameters.
This first workorder will only incorporate basic objects prior to any further network building.
In other words, this workorder wont include all new coming operations such as NEs creation thanks to
wizards. These dedicated operations will be associated with specific workorders.
Files Format Declaration
Before creating CM XML files, the engineer must make sure that all types of CM files are known by the
Operating System of his computer.
More precisely, the files management system of Windows must identify the following files as XML files:
workorders (*..XWO),
snapshots (*..XCM),
templates (*.XTPL).
To declare these 3 types as XML types, the engineer must select in Windows Explorer the following
options: Tools => Folder Option => File types => New.

5 1 20


4.1 Wizards Overview

Core
Network
Creation
Modification/Update
IuCS
IuPS
RNC
Iur
Iub
Node dedicated
Interface dedicated
5 1 21
NodeB

WPS wizards have been designed to meet a task-oriented approach.

Definition
A task oriented wizard is a hierarchical composition of tasks designed to guide the user through a
sequence of configuration steps.
For initial creation or heavy reconfiguration, configuration wizards have to be used instead of
object editors. They can also be launched for minor reconfiguration or tuning.
The Configuration wizards guide the user through the process of creation / reconfiguration at a high
level. They deal with a limited number of parameters necessary for the creation / reconfiguration
of the NE.
Configuration wizards simplify the task of provisioning by leading the user through the steps
required to configure the UTRAN subsystem.
They provide automatic datafill where appropriate.

4.2 Task Oriented Wizards

Example
5 1 22
complete/partial creation
non-sequential task navigation
on-the-fly checks
templates assistance
rules guidance

As we have seen earlier, task-oriented wizards provide embedded engineering rules for automatic
parameter allocation.
Syntaxic checks are available in the wizards, thus reducing the risk of errors.
The dedicated WPS wizards are:
RNC assistant
NodeB assistant
Iub assistant
Iur assistant
IuCS assistant
IuPS assistant.

4.3 Task Status

Example
5 1 23

The above slide shows the current status of one of the tasks listed in the RNC Wizard while building a
new RNC.
As the other wizards, the RNC Wizard gives explicit indications to the datafiller in order to let him know
what he has to do next.
In order to properly guide the datafiller through a sequence of configuration steps, the wizard divides
the remaining tasks into two types of operations:
the remaining operations that the datafiller can perform right now because they are fully available
(shown in green in the above slide),
the remaining operations that the datafiller cannot perform yet for some reasons (shown in red in
the above slide). Usually, other specific tasks must be performed prior to the launch of these
operations.

4.4 Task Tree

Example
task complete and OK

(compliant with recommendations)
OR
task not started but optional
available task
(not yet started)
OR
task started but not complete
(errors remaining)
task complete and NOK

(not compliant with recommendations)
non-available task
5 1 24

The task tree can be seen as the instrument panel for a pilot: it permanently lists all the operations in
progress during the construction of the NE and associates a task status to each of them.
As shown in the slide above, four levels of statuses can be assigned to a task:
Green circle 2 cases:

either the task is ok. It has been properly performed. It is over,
or the task is optional, there is no need to start it.
Red exclamation mark - 2 cases:

either the task has been performed but there are still some errors,
or the task has not been started yet.
Yellow exclamation mark - although the task has been performed, there is still declaration not
compliant with the engineering rules (non blocking error).
Crossed circle at this stage, the task cannot be performed.

4.5 Wizard operation editor
5 1 25

Wizard operation editor is enhanced to provide filtering, sorting and export capabilities similar to the WPS
tabular editor capabilities.
Warning management: If there is a warning on parameter validation, the parameter will be highlighted in
yellow (instead of red for error) and user can run the operation.



for this module
5 1 26


End of Module
5 1 27


61
Section 6
RNC Wizard
Module 1
RNC Wizard
9352 WiPS

Blank Page
612
RNC Wizard RNC Wizard

Document History
Edition
Date
Author
Remarks
01
2010-04-08
GOMEZ Cline
First edition

Module Objectives

Describe
List
Explain
Identify ...
613


614

Table of Contents
Page

1 RNC Types and Wizard Tasks
1.3 Main Tasks
1.3 Main Tasks
2 RNC Definition
2.1 RNC Definition
3 RNC HW Configuration
3.1 9370 RNC Market Models
2.3 RNC Market Model Selection
2.5 9370 RNC CN HW Configuration
2.6 CN Capacity
2.8 IN Modules Selection
3 RNC Optical Connections
3.1 Optical Modules Interfaces Provisioning
3.2 Hairpin Configuration for SPVC/PNNI
3.3 Traffic Shaping
3.4 Hairpin Configuration for Traffic Shaping
3.5 RNC Connection Model Selection
3.6 IN Optical Connection Configuration
3.7 IN Optical Connection Creation
4 RNC Time Synchronization
4.1 IN Time Synchronization
5 RNC Addressing Definition
5.1 RNC External Addressing Needs
5.2 NSAP Addressing Overview
6 1 5 5.3 NSAP Addresses Definition
9352 WiPS 5.4
9352 WPS
UAO7 Internal
UTRAN Configuration
RNC
Addressing Needs
5.5 RNC Internal IP Plan Configuration
5.6 RNC Hybrid Iub IP Configuration
5.7 SS7 Stack Configuration
6 RNC OAM Streams
6.1 Full Out-Band OAM Configuration
6.2 Full In-Band OAM Configuration
6.5 RNC 1500 CN/IN OAM Streams
7 RRM Subtree Creation
7.1 RRM Model Propagation
8 RNC Wizard Exit
8.1 RNC Creation Results

7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43

616

617


1.3 Main Tasks

RNC
Name, Id, Version, Nb freq, Etsi/Ansi,
ClusterId, RNC Family
RNC Definition
Atm/Atm+IP/IP,PSFP/DCPS,16pOC3 PQC/MS3,
Market Model, Board configuration
HW Configuration
IP Plan configuration internal

traffic and vr
IP Plane Configuration
Connection model, optical

connection definition
Connections configuration
Local/External, slot 8/9/14/15,

port eth/sdh
Clock synchronisation
OAM stream configuration
Inband/Outband configuration and

OMU IP adress configuration
SS7 Protocol, OPC dfinition, NSAP

address
SS7 Stack configuration

RRM Subtree Creation
618
Radio Access Service and Location

services Template definition

This procedure sets the NodeBCapability under the RNC, NodeB object. If the NodeBCapability is equal to
1, this means the NodeB is capable of IP and ATM transport. If the NodeBCapability is set to 0, the NodeB
is capable of ATM transport only.

1.3 Main Tasks

RNC
619

The main steps of the RNC wizard are displayed in the left part of the wizard window shown above.
Here are the main steps of the procedure to be performed when proceeding the network construction:
1. From the main window, select the Network tab.
2. From the network tree, select where the wizard is going to apply.
3. From the Wizards & Operations panel (right part of the window), select the RNC Wizard and
then run it.
4. In the RNC wizard tree, choose the element to be configured.
5. In the Current Status window, choose the operation to be launched.
Once the operation is completed, Close the RNC wizard to go back to the main window.
Note
The RNC wizard is launched every time a new RNC is created. It is also invoked when a significant RNC
modification has to be carried out.

2 RNC Definition
6 1 10


2 RNC Definition
2.1 RNC Definition
6 1 11

The goal of the RNC definition is the following:

Definition of identifiers.
Selection of the RNC type, managed frequency band.
Selection of one of the standard Hardware configuration.

6 1 12


3.1 9370 RNC Market Models
w/ DCPS&CP4
4 PS
6 PS
8 PS
10 PS
12 PS
Erlangs
2940
4800
7200
9900
12 000
Iu Application Mbps
132
219
315
441
528
Node Bs
720
1200
1600
2000
2400
Cells
720
1200
1600
2000
2400
6 1 13

The number of BTSs can at a maximum be equal to number of sectors. For example, 9370 RNC can
support
2400 1 carrier 1 sector (O1) BTS with 12 DCPS
400 STSR1 BTS and 200 STSR2 BTS with 12 DCPS
The CP3 module can support a maximum of 1200 cells or BTSs. The CP4 module, available in UA06.0
is required to increase dimensioning greater than 1200 cells or 1200 BTS.

2.3 RNC Market Model Selection
6 1 14

In UA6.0, there are 2 ways of implementing Iub interface from RNC side:
Using only ATM (maximum 12 Packet Server boards available)
Using ATM and IP (maximum 10 Packet Server boards available, because 2 slots are used for 4pGigE
boards, that are providing IP over Ethernet for Iub interface)

Also from UA5.1, there are 2 types of Packet Server boards:
Packet Server 1, with 6 available market models (for different processing capacities)
Dual Core Packet Server. With only 5 available market models
and 2 types of 16p OC3/STM1 boards:

PQC: supports up to 310 Mbps IP forwarding Iu DL Throughput
MS3: supports up to ~2.5 Gbps IP forwarding Iu DL Throughput (from UA05 S/W release)

2.5 9370 RNC CN HW Configuration

Up
Up
Up
Up
Up
to 12 PMC-PC per RNC

to 40 PMC-RAB per RNC
to 2 PMC-NI per RNC
to 14 PMC-TMU per RNC
to 2 PMC-OMU per RNC
Packet Server FP #01
PMC PMC
PMC
PMC
Master PC
PC
Master
PMC PMC
PMC
PMC
Master PC
PC
Master
PMC
PMC
RAB
RAB
PMC
PMC
RAB
RAB
PMC
PMC
TMU
TMU
PMC
PMC
RAB
RAB
Fabric
Interface
PMC
PMC
RAB
RAB
PMC
PMC
RAB
RAB
PMC
PMC
TMU
TMU
PMC
PMC
PC
PC
PMC
PMC
OMU
OMU
PMC
PMC
NI
NI
PMC
PMC
PC
PC
PMC
PMC
TMU
TMU
PMC
PMC
TMU
TMU
PMC
PMC
RAB
RAB
PMC
PMC
RAB
RAB
PMC
PMC
RAB
RAB
PMC
PMC
RAB
RAB
PMC
PMC
RAB
RAB
PMC
PMC
RAB
RAB
PMC
PMC
RAB
RAB
Fabric
Interface
2 master PS-FP modules

6 1 15
Fabric
Interface
Fabric
Interface
Up to 10 PS-FP modules

Each Packet Server FP module houses six PMC (PCI Mezzanine Cards) boards.
The PMCs are spared as load shared nodes within each PS-FP module so that the failure of a single
computing element could not break off an entire PS-FP module.
Two PS-FP modules are selected as master:
one PMC on each master PS-FP module is dedicated to Master function,
while one PS-FP operates as the active module, the second one operates in warm standby mode
with duplicated information to provide high availability.
The PMC boards on the twelve PS-FP modules are split up as follows:
on the two master PS-FP modules: one PMCM (Master): active or passive, one PMCPC, three PMC
RAB and one PMC-TMU,
on the other PS-FP modules (up to ten): one PMCPC, up to four PMCRAB, one or two PMC-TMU,
zero or one PMC-NI and zero or one PMC-OMU.
Same functional architecture is valid for the case when DCPS boards are used. A DCPS has 3 dualcore processors, so each core will have assigned a function, similar with a PMC.

2.6 CN Capacity
6 1 16


2.8 IN Modules Selection
6 1 17

Datafilling
This window consists in declaring the number of modules of the Interface Node as well as their locations
in the slots of the Node.

6 1 18


3.1 Optical Modules Interfaces Provisioning
Slot 8
Slot 9
STM1
Iur
POC
STM1
Iur
15
15
14
14
13
13
12
12
11
11
10
10
Iu
POC
Iu
LAPS
4pGigE for IuB, IuPs,IuCs and

Iur over IP
6 1 19
IN 16pOC3/STM1 Modules

The slide above shows a standard physical interface configuration for the INode and ANode optical
modules.
The INode may be configured with LAPS optical protection.
Several types of connection may be defined:
Iub connection defines ports used to communicate with the POC
Iur connection defines ports used to interact with a neighbor RNC.
Iu connection defines ports used to communicate with the Core Network.

3.2 Hairpin Configuration for SPVC/PNNI
Hairpin
POC
UNI User(Rx)
UNI
Interface
RNCRNC-IN
PVC
UNI Network(Tx)
SVC
dynamic
PVC
UNI
Interface
UNI Network
UNI User
NodeB
PNNI domain
6 1 20

PNNI is optional in case of optical RNC.

PNNI is a routing and signaling protocol which uses Soft PVC as the dynamic ATM connections established
between 2 points of an ATM network using PNNI. SPVC are like PVC but there is only the need to provision
end points (not intermediate ones). So in case of STM1 board failure in POC, the SPVC are dynamically
rerouted.
SPVC must originate on network side of the UNI. But Iub AAL2 VCC originate on UNI user side and
terminate on UNI user side. So hairpins are used on 16pOC3/STM1 card to implement network side of the
UNI interface.
As a consequence when PNNI is used, hairpins are needed on the Interface Node 16 pOC3/STM1 board as
shown in the slide above.

3.3 Traffic Shaping
Public ATM Network: Mandatory

Private ATM network: Optional
Iub Interface
RNC
Control
Node
Remote ATM
Concentrator
VCC Control Plane
Public
ATM Network
VCC User Plane
RNC
Interface
Node
VCC OAM
VPC
Traffic shaped
NodeB
VPT
6 1 21
VPT

In certain configurations, when connecting NodeB to RNC across a public ATM backbone, a VPC may be
used on the POC / RNC interface.
All VCCs on NodeB E1 with exception of OAM VCC will be carried on this VPC.
As all E1 traffic is carried on VPC, this VPC is equivalent to a single leased line. Resulting VPC is linearly
shaped.

3.4 Hairpin Configuration for Traffic Shaping
Traffic Shaping:
RNCRNC-IN
16pOC3/STM1
Tx
VPC / 1
VPC
Rx
Public
ATM
Backbone
Emission priorities shaping
Hairpin
Ep2 Ep2 Ep3 Ep4 Ep4 Ep7
VPT
Tx
Rx
VCC1
Ep2
Ep4
Ep3
Ep2
Ep7
Ep4
VCC2
VCC2
VP connection/ 1
6 1 22

Hairpins are used in the RNC to provide VPT shaping when interfacing ASP policed network.
In case of public ATM backbone between the RNC and the NodeBs, VPC is used (traffic shaping). For this
reason, traffic management is mandatory in order to control the bandwidth.
But the 16pOC3/STM1 module on I-Node can not do traffic management (emission priority ...) and traffic
shaping at the same time.
Traffic shaping can only be done at VPC level and at EP0.
Hairpin is a way to do emission priorities on one port and then recover the VPC on another port in order
to do traffic shaping.

3.5 RNC Connection Model Selection
6 1 23


3.6 IN Optical Connection Configuration
6 1 24

IN optical connection configuration can be reviewed and modified at any time.

IN optical configuration management task provide a summary of the current connections settings. For
each optical port of the Passport modules there is mention of:
port allocation
LAPS activation
connection type
AtmIf Template.
AtmIf Template fields do not need to be completed except in case of configuration modification.

3.7 IN Optical Connection Creation
6 1 25

IN optical connection configuration can be reviewed and modified at any time.

To create a new connections, all its attributes have to be defined:
port allocation
LAPS activation
connection type
AtmIf Template
connection role.

6 1 26


4.1 IN Time Synchronization
6 1 27

This window allows to configure the passport synchronization.

Two options are available:
Local: The passport uses its internal clock. In this case all the information in grid related to
external are disabled and nothing else needs to be filled in.
External: It means that the synchronization is provided by another node physically linked to the INode. These links must be declared as a possible synchronization source. In addition of the
primary source, a secondary and a tertiary source can be defined for redundancy purpose. In such
a case you have to set the board type and slot number, the port number and the connection type
(SDH/SONET, PCM) of each source in the grid.

6 1 28


5.1 RNC External Addressing Needs
RNC
NSAP @
Iur
ATM
Backbone
DPCs
NSAP @
Uu
Iur
Iub
ATM
Backbone
Core Network
OPC
Iub
RNC
ATM
Backbone
Iu
(CS & PS)
NodeB
(BTS)
OAM IP @
OAM
Main Server
6 1 29

The RNC deals with the various interface type and the associated protocol layer. An addressing plan
needs to be set for each of them:
OPC (Originating Point Code) for SS7 communication (mainly used with the core network).
NSAP address for ATM routing, especially used over the Iur.
Identification for OAM purposes. A set of parameters are required:

UserLabel
Node Id
OAM IP address
PerfServId (optional: in case of Performance Management).

5.2 NSAP Addressing Overview

NSAP address = 20 bytes
1
10
11
12
13
14
Network Prefix
15
16
17
18
19
ESI (End System Identifier)
Node Address
20
Bytes
SEL
Interface Address
Network Prefix = 26 hexadecimal characters
47 0000 FFFF FFFF FFFF FFF1 7010
NSAP Prefix Examples:
IN
AN
Peer Group 1
39 0000 9999 9999 9999 9999 0010
POC
ATM
Backbone
45 0000 FFFF FFFF FFFF FFFF 1020
POC_1
47 0000 FFFF FFFF FFFF FFF2 9AA0
POC_2
47 0000 FFFF FFFF FFFF FFF2 9A90
Peer Group 2
AN
Peer Group Id
Supported Passport
format indicators
IN
Node Id
Domain
indentificator
(public / private)
6 1 30

According to the ATM interface provisions on I-Node (UNI, NNI, PNNI) a NSAP prefix may be required.
UNI interface and PNNI required ATM addresses called AESA (ATM End System Address). AESA is structured
according to NSAP format (Network Service Access Point).
To establish SPVC and SVC across the network, ATM source and destination points need to be uniquely
identified with ATM addresses.
NSAP General Definition
NSAP is a 20 bytes length address.
The NSAP address format consists of three main parts:

a 26 hexadecimal digits known as the network prefix
a 12 hexadecimal digits known as the end system identifier (ESI)
a 2 hexadecimal digits known as selector (SEL).

5.3 NSAP Addresses Definition
6 1 31

Definition of ATM addresses (Network Service Access Point) of RNC nodes. RNC-CN NSAP address is
required for Iu and Iur interfaces.
RNC-IN addresse is used for advanced routing features such as PNNI.
ITU-T references: X213, E191 and Q2630.
1 RNC NSAP Address used for Iur (3GPP 25.426).
NSAP: Network Service Access Point.

5.4 RNC Internal Addressing Needs
VR/0 - Management Virtual Router

IP@
16pSTM1/OC3
IP@
Eth
CP3
VR/1 - Operational Virtual Router

IP@
IP@
16pSTM1/OC3
IP@
Local media
IP @
IP @
PMC-RAB
PMC-RAB
IP @
IP @
PMC-RAB
PMC-RAB
IP @
VR/2
Internal Virtuall Router
IP@
Local media
IP @
CP3
PMC-M
PMC-PC
PSFP x 12
Interface Node
6 1 32

At RNC level, there are three kinds of IP traffic:

OAM traffic
User Traffic (Iu PS)
Internal IP traffic.
Internal IP addresses are not provisionable.

Each OMU and TMU PMC has also one internal IP address to ensure the control node functionality.
Each PMC has an internal IP address used by the other PMCs.
These addresses are also used for external communication with the Core Network.
PMC modules IP addresses follow pre-defined engineering rules using Local Media IP address as an input.

5.5 RNC Internal IP Plan Configuration
6 1 33

In the IP Plan Configuration screen, you need to specify the IP address of the LocalMedia and the
corresponding IP mask.
Note On RNC-IN, in case the IP flows are selected as separated, up to four VR may be needed.

5.6 RNC Hybrid Iub IP Configuration
6 1 34

If Hybrid Iub feature is used, then is necessary to define the IP configuration: the Virtual Router responsible
for Iub traffic over IP, the IP address of the virtual routers port and the corresponding mask.

5.7 SS7 Stack Configuration
6 1 35

At RNC level, SS7 identifiers definition only requires the input of one RNC Point Code.

6 RNC OAM Streams
6 1 36


6 RNC OAM Streams
6.1 Full Out-Band OAM Configuration
Main Server
NodeB OAM
OAM
LAN
OAM
Gateway
IN OAM
OMU
OAM
B&B
Ethernet
Links
Core
Network
CP3
Optical
Links
ATM
Backbone
Vcc 0.32
6 1 37
I-Node

The following OAM configurations are available:

Out of band OAM: The OAM messaging uses a separate Ethernet network.
In-band OAM: The OAM messaging uses the same physical links than the traffic.
Out-Band OAM
The CP3 module of Interface Node provide an Ethernet connection to an OAM LAN.This LAN
provides a connection to the Access OAM server.
Notes
The NodeB OAM is always considered In-Band.

6 RNC OAM Streams
6.2 Full In-Band OAM Configuration
NodeB OAM
Main Server
IN OAM
OMU
OAM
B&B
CP3
ATM
Backbone
ATM
Backbone
Vcc 0.32
6 1 38
Core
Network
I-Node

In-Band OAM
This configuration allows to use the traffic bandwidth and the traffic links to transfer the OAM
messaging:
I-Node switches OAM messaging from the various nodes in a dedicated VCC over the Iu interface.
The Wireless Gateway provides the Ethernet connection the OAM server LAN.

6 RNC OAM Streams
6.5 RNC 1500 CN/IN OAM Streams
6 1 39

Here are the definitions of the Internet addresses which are enclosed in the attribute description
provided by WPS.
CNode IP Address
A 32-bit address assigned to hosts using TCP/IP.
The syntactic representation for a 32-bit integer consists of four 8-bit numbers written in base 10
with periods (dots) separating them.
Used to represent IP addresses in the Internet as in: 192.67.67.20.
IP Address of the OMUs.
CNode Secondary Address

Alternative IP Address of the second OMU in the Control Node.
The syntactic representation for a 32-bit integer consists of four 8-bit numbers written in base 10
with periods/dots separating them.
Used to represent IP addresses in the Internet as in: 192.67.67.20
Used by NodeB in order to communicate with OMC-B.

6 1 40


7.1 RRM Model Propagation
6 1 41

At this stage, the datafiller has to select the relevant template to be referred as the Radio Resource
Management Model during the WPS sessions. This operation leads to the creation of an empty RRM
subtree.
The RNC must have been defined prior to this task.
The datafiller also selects the Location Services Template for propagation purposes.

8 RNC Wizard Exit
6 1 42


8 RNC Wizard Exit
8.1 RNC Creation Results
6 1 43

Once all the required tasks belonging to the RNC creation have been properly carried out, the datafiller
can exit & jump to another part of the Access Network construction.
For example NodeB could be the next task to be performed by the datafiller during his WPS sessions.



for this module
6 1 44


End of Module
RNC Wizard
6 1 45


71
Section 7
NodeB Wizard
Module 1
NodeB Wizard
9352 WiPS

Blank Page
712
NodeB Wizard NodeB Wizard

Document History
Edition
Date
Author
Remarks
01
2010-04-08
GOMEZ Cline
First edition

Module Objectives

Describe
List
Explain
Identify ...
713


714

Table of Contents
Page

1 Node B Wizard
1.1 Main Tasks
1.1 Main Tasks
1 BTS Equipment Definition
1.1 BTS Configurations
1.2 RRH Configurations
1.3 Configurations Denomination in WPS (1/2)
1.4 D-BBU Resource Pooling
1.5 BTS Equipment Creation
1 BTS Cells Configuration
1.1 BTSCell Identifiers
1.2 BTSCell Parameters
1.3 BTS Rx Chain Configuration
1.4 HSxPA Resources
1.5 BTSCells Configuration
1 Site Creation
1.1 BTS Site Creation
1.2 Antenna System Definition
1 Node B Configuration
1.1 NodeB Creation
1.2 FDDCell Mapping on BTSCell
1.3 FDDCell Parameters
1.4 iMCTA Mode
7 1 5 1.5 FDDCell Radio Configuration
9352 WiPS 1.6
9352 WPS
UAO7 UTRAN Configuration
FDDCells
Features Activation
1.7 Twin Cell Handover Settings
1.8 FDDCells Mobility Configuration
1.9 FDDCell Location Services Parameters
1.10 FDDCell Localization Configuration
1.11 Multiple S-CCPCH Options
1.12 FDDCell Channels Model Propagation
1 NodeB Wizard Exit
1.1 NodeB Creation Results

7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40

716

1 Node B Wizard
717


1 Node B Wizard
1.1 Main Tasks

NodeB
Name, NeId, Version, Model
BTSequipment Configuration
Template, azimut, local cell id, PaRatio,
iCEM/xCEM
BTS cell configuration
Name, Version
NodeB Configuration
Cellid, SC, LAC, RAC, SAC,

iMCTA Mode
FDDcell Definition
Feature list
FDDcell feature Activation
Latitude, latitude sign,

longitude, azimut
Localization configuration
Propagation model
Model Propagation
Altitude, latitude, longitude
Site creation
Antenna system definition
718
Azimut, downtilt, electrical tilt,

height, type

This procedure sets the NodeBCapability under the RNC, NodeB object. If the NodeBCapability is equal to
1, this means the NodeB is capable of IP and ATM transport. If the NodeBCapability is set to 0, the NodeB
is capable of ATM transport only.

1 Node B Wizard
1.1 Main Tasks

NodeB
719

The main steps of the NodeB wizard are displayed in the left part of the wizard window shown above.
The NodeB configuration assistant provides a fast & easy way to create and re-configure NodeB.
Depending on the kind of operation to perform, it can be initialized with a graphical selection from
Network Tree or be started empty.
The following operations can be performed:
initial NodeB creation
NodeB reconfiguration.

7 1 10


1.1 BTS Configurations

coupler
Transmit Path
coupler
Power Split
RF
PA
Tx / Rx
coupler
3 Sectors
1 Scrambling Code
OTSR
STSR
coupler
coupler
RF
PA
coupler
7 1 11
RF
PA
Tx / Rx
3 Sectors
3 Scrambling Codes
RF
PA
Transmit Path

OTSR is downlink limited because of its single MCPA. Once downlink power is exhausted, two MCPAs may
be added and the transmit splitter removed to move to a standard sectorized configuration (STSR).
Sectorial Transmit Sectorial Receive (STSR) is the typical iBTS configuration for a multi-sector
configuration.
The STSR is logically declared at the RNC as 3 cells (in case of 3-sector configuration). The mobile reports
measurements for the 3 sectors and softer handovers are controlled by the network.
STSR configuration requires a full RF configuration (three DDMs and three MCPAs or six MCPAs for Tx
diversity), this allows a higher downlink capacity.

1.2 RRH Configurations
No Softer HO
Sector C
localCellGroup 1
Se
cto
rD
RRH
BTS
local
site
RRH
cto
Se
Se
cto
rA
localCellGroup 0
7 1 12
remote
site
Sector F
RRH
rB
Sector E

RRH is designed for Macro layer coverage, in particular when the site acquisition is complex. For
example, with only one NodeB, operator is able to deploy outdoor coverage and simultaneously hot-spot,
remote or indoor coverage.
When RRH is used, the BTS supports 2 kind of cells:
Local cells that are managed by RF modules inside the BTS (TRM/PA/DDM). The RF interface of
local cells is at BTS bulkhead level.
Remote cells that are managed by RRH. The RF interface of remote cells is at RRH bulkhead level.
In this configuration cells are divided into two clusters distinguished by their localCellGroupid:
inside each cluster, Softer Handover is allowed,
between the two clusters, only Soft Handover is available.


xTxRa-b-c(1+1)_RRHd
x: O=Omnidirectional, S=Sectorial
(1+1): 2 carriers, 1 MCPA per carrier
a: number of local carriers
b: number of local antennas
c: number of local power amplifiers
d: number of remote carriers
Supported BTS Configurations
BTS Type
OTSR
1 Sector
STSR1
STSR2
STSR2(1+1)
STSR1-2-1
STSR2-2-1
STSR2-2-1
2 Sectors
OTSR1-4-1
STSR1-4-2
STSR2-4-2
STSR2-4-2
3 Sectors
OTSR1-6-1
STSR1-6-3
STSR2-6-3
STSR2-6-3
4 Sectors
STSR1-8-4
STSR2-8-4
5 Sectors
STSR1-10-5
STSR2-10-5
6 Sectors
STSR1-12-6
STSR2-12-6
7 1 13

The BTSEquipment configuration is characterized by:

Number of local carriers
Number of local antennas (RxMain + RxDiv)
Number of MCPAs,
NUmber or remote carriers.


Supported BTS Configurations
BTS Type
STSR3
STSR3(2+1)
STSR4(2+2)
1 sector
STSR3-2-1
STSR3-2-1
STSR4-2-1
2 sectors
STSR3-4-2
STSR3-4-2
STSR4-4-2
3 sectors
STSR3-6-3
STSR3-6-3
STSR4-6-3
7 1 14


1.4 D-BBU Resource Pooling

F0
F1
D-BBU
D-BBU
codec0
codec0
codec1
codec1
codec2
codec2
iCEM64
iCEM128
D-BBU
D-BBU
D-BBU
D-BBU
codec0
codec0
codec0
codec0
codec1
codec1
codec1
codec1
codec2
codec2
codec2
codec2
Separated Pool
7 1 15
Shared Pool

D-BBU resource polling provides means toshare D-BBU capacity between carriers.
It is applicable to all R99 RABs. This D-BBU frequency pooling feature is applicable independently from
the way the D-BBUs are distributed on the CEM board.
This feature allows optimising BBU capacity utilisation, for configurations with strictly more than one
frequency.
It is not applicable to HSDPA (H-BBUs) or HSUPA (E-BBUs).

1.5 BTS Equipment Creation
7 1 16

The NodeB creation includes 3 main steps:

BTS Equipment configuration
NodeB Configuration
Site Configuration.
The window above allows performing the first step.

7 1 17


1.1 BTSCell Identifiers

localCellGroupId = 0
priority = 1
localCellId = 1000
rdnId = 0
rdnId = 2
localCellId = 1002
7 1 18
rdnId = 1
localCellId = 1001

LocalCellId RdnId (= sector Id)

LocalCellId is used to uniquely identify the set of radio resources required to support a cell.
Nortel recommends that the LocalCellId remains unique within the UTRAN (range: [0, 268 435 455])
RdnId identifies the BTS cell within the BTSEquipment
RdnId allocation
RdnId = 0 is allocated to the upper north sector
Consecutive RdnId are allocated clockwise
Other RULES
Rule1: NodeB.UserLabel = BTSEquipment.UserLabel = Site.Name
Rule2: FddCell.UserLabel = NodeB.UserLabel_FddCell.RdnId
Rule3: (3GPP recommendations set cellIdentity unique per RNC) FddCell.cellIdentity is unique
within RNS.
Rules are implemented in both WPS Access & iPlanner.

1.2 BTSCell Parameters

maxPowerAmplification
MCPA
STSR-1
BtsCell
STSR-2
F1
localCellId = 1000
F1
F1
paRatio = 50%
localCellId
=
1013
paRatio = 100%
e
lSiz
cel
F2
BtsCell
BtsCell
localCellId = 1001
paRatio = 50%
localCellId
=
1010
ce
llS
ize
BtsCell
7 1 19

BTSCell Object Parameters

localCellGroup: indicates which frequency layer is managed by the BTSCell.
Max power Amp: indicate the maximum power amplification of the BTSequipment PA (30 W or 45 W).
paRatio: indicates the static percentage of power dedicated to the BTSCell.
paRatio (BTSCell sharing same PA) 100%
CellSize: gives a rough approximation of the search window size for the initial access to the NodeB.

1.3 BTS Rx Chain Configuration

RF cables
(2 per sector)
BTS
Masthead
equipment
DDM
TMA
TMA
TMA
Alarm/DC
LNA
TMA
DDM
(main)
Antenna
(main)
Main
Alarm/DC
LNA
Antenna
(diversity)
DDM
(diversity)
Diversity
7 1 20

The main purpose of the Tower Mounted Amplifier (or TMA) is to decrease the overall noise of the system
by amplifying the receive signal.
This amplifier may also be known as the Tower Mast Head Amplifier - MHA or Tower Top Amplifier TTA.
The advantages of placing an amplifier on the tower (mast), are:
an increase in uplink budget (at iBTS level),
a better coverage in rural areas (at cell level),
increased battery life (at UE level).
The TMA is a Low Noise Amplifier (LNA) designed to be mounted as close as possible to the antenna
system. It compensates for the feeder loss on the receiving path by amplifying the received signal at the
top of the mast.
The TMA is typically used at sites with high masts.
The TMA has a 1.6 dB noise figure and a gain of 12 dB.
The transmit path insertion loss is assumed to be around 1 dB.
The LNAs are powered from the iBTS (DDM) through the RF coaxial cable.
LNA monitoring is integrated in the iBTS cabinet. Alarms are monitored by the DDMs and are reported to
the Digital shelf through the connection between DDMs and TRMs.

1.4 HSxPA Resources

MAC-e
HARQ decoding
E-DSC(s) scheduling
UL Link demodulation/decoding
DL scheduling PhCH(s)
MAC-hs
HARQ
HS-DSCH scheduling
Link Adaptation (adaptive coding & modulation)
UL
DPCCH(s)
HS-DPCCH(s)
DL
HS-PDSCH(s)
HS-SCCH(s)
UL
DPCCH(s)
E-DPCCH(s)
E-DPDCH(s)
DL
E-HICH
E-AGCH
E-RGCH
UL
Associated/R99 DPDCH(s)
Associated/R99 DPCCH(s)
CCH(s)
DL
Associated/R99
DPDCH/DPCCH(s)
CCH(s)
Alcatel-Lucent BTS
iCEM128
iCEM128
E-BBU
iCEM128
iTRM
MCPA
DDM
iTRM
MCPA
DDM
iTRM
MCPA
DDM
D-BBU
D-BBU
H-BBU
iCEM64
CEMa
H-BBU
iCCM
D-BBU
D-BBU
D-BBU
D-BBU
7 1 21
Digital Shelf
Radio Shelf

This slide shows the repartition of the roles between BBUs within the CEM boards.
It indicates where the radio links (physical channels) and retransmissions mechanisms (HARQ,
scheduling,) are managed.
Here is the NodeB HSxPA software mapping architecture:
iCEM BBU (H-BBU) with HSDPA software to handle HSDPA radio links
iCEM BBU (E-BBU) with HSUPA software to handle E-DCH radio links
iCEM BBU (D-BBU) with classical UMTS L1 software to handle the DCHs, the associated HSDPA DCH
and the Cell CCHs.
iCEM 64 has 1 BBUs that can be used as any of the above types
iCEM 128 has 2 BBUs that can be used as any of the above types
The CEM alpha can only be used for R99.

1.5 BTSCells Configuration
7 1 22

Here are the definitions enclosed in the attribute description provided by WPS:
localCellGroup: is a group of local cells of an iBTS associated with the same carrier.
Local cell Id: used to uniquely identify the set of resources within a nodeB required to support a cell
(as identified by a CellId). It supports uniqueness within the UTRAN for management system
purposes. The LocalCellId is used for the initial configuration of a NodeB when no CellId is defined.
The LocalCellId is defined by the operator and set in both NodeB and its C-RNC via O&M.
Cell size: represents the size of the cell.
Pa Ratio: Percentage of PA power associated with this BTS cell. The maximum power declared for
each BTS Cell to the RNC will be: Max DL power capability = (PaRatio /100 * PA Max power
capability) + Tx losses. This max power will be shared between all BTS cells with same frequency
group in one sector
Max power Amp: maximum power amplification of the PA (30 W/45 W/60W).

1 Site Creation
7 1 23


1 Site Creation
1.1 BTS Site Creation
7 1 24

Creating a BTS Site is an optional task.

The relationship is one site per BTS.
Two types of information are required: the BTS identification and geographical coordinates, and the
characteristics of each Antenna Access of the BTS.

1 Site Creation
1.2 Antenna System Definition
7 1 25

Creating a BTS Site is an optional task.

The relationship is one site per BTS.
Two types of information are required: the BTS identification and geographical coordinates, and the
characteristics of each Antenna Access of the BTS.

1 Node B Configuration
7 1 26


1 NodeB Configuration
1.1 NodeB Creation
7 1 27

When performed after BTSEquipment creation, NodeB creation is by default started with the same label
as the one used for the BTS.
Three types of Node B are possible:
iBTS (Macro, Compact or Distributed NodeB)
OneBTS (for the american market)
Micro_picoBTS

1.2 FDDCell Mapping on BTSCell
F2
F2
localCellId = 1011
CellId = 3
localCellId = 1010
CellId = 2
FDDCell
BTSCell
NodeB
F1
F1
CellId = 1
CellId = 0
locallCellId = 1000
locallCellId = 1001
localCellId = 1011
localCellId = 1010
F2
F2
locallCellId = 1000
locallCellGroupId = 0
locallCellId = 1001
locallCellGroupId = 0
F1
F1
BTSEquipment
7 1 28

The standardization of the Iub interface has defined an object based model on a logical part and a
physical part in order to cope with the multi-vendors configuration.
The logical part of the equipment is managed by the OMC-R.
The physical part of the equipment (iBTS) is managed by the OMC-B.
The mapping between the 2 parts (1-to-1 mapping between BTSCell & FddCell) is performed by the
localCellId parameter, coded on 28 bits, found under both the FddCell and the BtsCell objects.

1.3 FDDCell Parameters
scramblingCode = 0
scramblingCode = 511
dlFrequencyNumber = 10500
ulFrequencyNumber = 9550
LAC = 10 ; RAC = 20 ; SAC = 31
LAC = 10 ; RAC = 20 ; SAC = 32
uraIdentityList = 51, 52
NodeB
tCell = 0
tCell = 5
scramblingCode = 0
scramblingCode = 511
LAC = 10 ; RAC = 20 ; SAC = 31
LAC = 10 ; RAC = 20 ; SAC = 32
tCell = 0
tCell = 5
7 1 29

The frequency of a carrier if defined:

in uplink by the ulFrequencyNumber parameter,
in downlink by the dlFrequencyNumber parameter.
Both parameters correspond to the UARFCN (UTRA Absolute Radio Frequency Channel Number)
tCell parameter avoids to have overlapping P-SCHs in different sectors of a same NodeB. It represents the
timing delay relative to BFN used for defining start of SCH, CPICH and DL scrambling code in a cell.
The location area is used by the Core Network CS domain to determine the UE location in idle mode. A
location area contains a group of cells. Each cell belongs to only one LA.
The routing area is used by the PS Core Network to determine the UE location in idle mode. A routing
area contains a group of cells. Each cell belongs to only one RA.
The Service Area is used by the Core Network to determine the UE location in connected mode. A service
area contains a group of cells. Each cell belongs to only one SA.
The URA Identity list is an optional parameter only needed when URA_PCH is enabled.

1.4 iMCTA Mode

Alarm Table
Service Table
CAC Table
CS
PS
CS+PS
Access1: FDD
P2
P1
P1
Access2: 2G
P1
P2
P2
CS
PS
CS+PS
Access1: FDD
P2
P1
P1
Access2: 2G
P1
P2
P2
CS
PS
CS+PS
FDD1
P2
P1
P2
FDD2
P1
P2
P1
2G
P3
P3
P3
2G
FDD2
FDD1
7 1 30

The objective of intelligent Multi-Carrier Allocation (iMCTA) is to optimize the traffic distribution both
between layers and cells. iMCTA is managed by the RNC.
For a given call, the carrier is selected by the RNC according to the Operator strategy which may want to
take into account the service type, the mobile type (i.e. HSDPA, HSUPA capable or not), redirection
triggers and the cells load.
The iMCTA function only applies to call in connected mode (Cell DCH, E-DCH and HS-DSCH).
Call in Cell FACH (signaling or traffic), Cell PCH or URA PCH are not managed.
The iMCTA function manages HHO handovers which may be triggered for several reasons: Alarm, CAC,
Service.
The feature may be activated through four modes:
Alarm only: Alarm trigger applies,
Alarm and CAC : Alarm and CAC triggers apply,
Alarm and Service : Alarm and Service triggers apply,
All : All iMCTA triggers apply.

1.5 FDDCell Radio Configuration
7 1 31

At this stage, the datafiller must associate the relevant templates (FDDCell & CellSelectionIndo) with the
other radio parameters of the FDD cells.
Mapping between logical and physical cells must be defined as well, together with FDDCells access
settings.

1.6 FDDCells Features Activation
7 1 32

At this stage, the datafiller must define the activation of the features of each FDDCells.
The task used to manage the Links Settings between FDDCells and the various Configuration Classes
instances needed remains unavailable as long as the NodeB is not parented to an RNC.
The task used to define FDDcell mobility between Twin Cells may also remain unavailable depending on
the BTS configuration.

1.7 Twin Cell Handover Settings

RNC
F1
F2
NodeB
F1
F1
F2
FDDCell
F2
F1
F2
F1
InterFreqHhoFDDCell
F1
F2
F2
twinCellId
F2
F1
F2
F1
7 1 33

The purpose of inter-frequency handover between twin cells is to provide a mean to manage bi-carrier
sites in order to bring additional capacity.
The inter-frequency handover is performed between two cells on the same sector, which are called twin
cells, as shown in the figure above.

1.8 FDDCells Mobility Configuration
7 1 34

At this stage, the datafiller must associate the relevant HHO templates with the other Intra-NodeB Blind
Handover activation parameters of the FDD cells.

1.9 FDDCell Location Services Parameters

antennaAngleOfOpening
FDDCell
azimuthAntennaAngle
cellIdPositioningMethodAccuracy
minCellRadius
APP
GAICoord
lattitude
lattitude
latitudeSign
latitudeSign
longitude
longitude
Requested Report Area = Geographical Area
Point With Uncertainty
Point With Uncertainty
7 1 35
Polygon

In the cell ID based (i.e. cell coverage) method, the position of an UE is estimated with the knowledge of
its serving NodeB and cell.
When geographical coordinates are used as the position information, the estimated position of the UE
can be a fixed geographical position within the serving cell (e.g. geographical position of the serving
NodeB) or a geographical position computed by combining information on the cell specific fixed
geographical position with other available information (e.g. additional cell provisioned information).
Geographical information can also take the form of a polygonal area defined with the help of provisioned
geographical points.
The UE position is estimated on following provisioned information basis (if requested report area is
Geographical Area).
Per FDDCell provisioned data:
UTRAN transmitter position (Access Point Position)
Antenna azimuth
Antenna angle of opening
Mean cell radius (minCellRadius)
Accuracy code (cellIdPositioningMethodAccuracy)
Polygonal shape (optional).

1.10 FDDCell Localization Configuration
7 1 36

Here are the definitions of the parameters used by WPS:

Latitude Sign: Position of a site on a map of the world in relation to the North or South of the
equator (cardinal points).
Latitude: Position of a site on a map of the world measured as the distance to the North or South of
the equator. The expected coded value is calculated from a formula allowing the conversion
between the latitude given in degree X and the corresponding integer N: N= X*2^(23)/90
Longitude: Position of a site on a map of the world measured as the distance to the East or West of
a set line. The expected coded value is calculated from a formula allowing the conversion between
the longitude given in degree X (between -180 and 180) and the corresponding integer N: N=
X*2^(24)/360

1.11 Multiple S-CCPCH Options

Two S-CCPCH Configuration
Logical
Channels
Transport
Channels
Physical
Channels
PCCH
DTCH
FACH #1
PCH
S-CCPCH #0
SF 128
4x DCCH CCCH
BCCH
FACH #0
S-CCPCH #1
SF 64
only for
Paging messages
Three S-CCPCH configuration

Logical
Channels
Transport
Channels
Physical
Channels
PCCH
DTCH
PCH
S-CCPCH #0
SF 128
4x DCCH CCCH
FACH #1
FACH #0
S-CCPCH #1
SF 64
S-CCPCH dedicated
to Paging traffic
7 1 37
BCCH
BCCH
FACH #0
CCCH
CTCH
FACH #1
S-CCPCH #2
SF 128
only for CBS traffic

The support of Multiple SCCPCH channels configuration allows to efficiently accommodate services which
make use of FACH Transport Channels (e.g. Always On, CBS, etc. ) while maintaining a good level of
paging reliability and robustness.
In addition to the mono S-CCPCH configuration supported in the previous releases, two other options are
introduced in UA5.0:
Two S-CCPCH when CBS is not used:
one S-CCPCH to carry the PCH
the other S-CCPCH to carry FACH channels
Three S-CCPCH when CBS is used:

two S-CCPCH carrying the traffic as described in previous case,
the additional one to carry FACH channels for support of the CTCH, BCCH
and CCCH traffic.
The description of the SCCPCH configuration is provided to UE via the SIB type 5 and the SIB type 6.

1.12 FDDCell Channels Model Propagation
7 1 38

At this stage, the datafiller must associate the relevant templates of the Common Channels (RACH and
S-CCPCH) to all the FDD cells.

1 NodeB Wizard Exit
7 1 39


1 NodeB Wizard Exit
1.1 NodeB Creation Results
7 1 40

Once all the required tasks belonging to the NodeB creation have been properly carried out, the
datafiller can exit & jump to another part of the Access Network construction.



for this module
7 1 41


End of Module
NodeB Wizard
7 1 42


81
Section 8
Interface Wizards
Module 1
Interface Wizards
9352 WiPS

Blank Page
812
Interface Wizards Interface Wizards

Document History
Edition
Date
Author
Remarks
01
2010-04-08
GOMEZ Cline
First edition

Module Objectives

Describe
List
Explain
Identify ...
813


814

Table of Contents
Page

1 Iub Wizard
1.1 Iub Wizard Introduction
1.3 Main Tasks
1.3 Iub Wizard - Main Tasks
1.3.1 NodeB Parenting
1.3.2 Iub Interface Parameters
1.3.3 Streams Definition
1.3.4 AAL2 CAC Configuration
1.3.5 BTS PCM and ATM Configuration
1.3.6 NodeB OAM IP Flows Configuration
2 Iu Wizards
2.1 Iu Topologies
2.2 IuFlex
2.3 IuCS Wizard - Main Tasks
2.4 IuCS Definition
2.5 IuCS Control Plane
2.5.1 RouteSets and LinkSets Configuration
2.5.2 Signaling Links ATM Switching
2.6 IuCS User Plane
2.6.1 AAL2 Paths
2.6.2 IuCS User Plane Definition
2.6.3 IuCS User Plane ATM Switching
2.7 IuCS with IuFlex Service Configuration
2.8 IuPS Wizard - Main Tasks
8 1 5 2.9 IuPS Definition
9352 WiPS 2.10
9352 WPS
UAO7 UTRAN
Configuration
IuPS
Control
Plane
2.11 IuPS User Plane
2.11.1 IP Routing Configuration
2.11.2 IP Subnet Configuration
2.11.3 IP Streams ATM Switching
2.11.4 DSCP IP CoS to ATM VCC Mapping
2.11.5 DSCP Configuration
2.11.6 IuPS with IuFlex Service Configuration
3 Iur Wizard
3.1 Iur Wizard - Introduction
3.2 Iur Wizard - Main Tasks
3.3 Iur Creation
3.3.1 Iur RouteSets Definition
3.3.2 Iur Creation
3.3.3 Wizards Switch for Alcatel-Lucent Iur
3.4 Iur Control Plane
3.4.1 Alcatel-Lucent Iur Routesets Definition
3.4.2 Alien Iur RouteSets Definition
3.5 Iur User Plane
3.5.1 Traffic Links Definition
3.5.2 Alcatel-Lucent Iur AAL2 Paths Definition
3.5.3 Alien Iur AAL2 Paths Definition
3.5.4 AAL2 Path ATM Switching

7
8
9
10
11
12
13
14
15
16
17
18
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59

816

1 Iub Wizard
817


1 Iub Wizard
1.1 Iub Wizard Introduction
818

The Iub assistant helps the user to create and configure an Iub interface between a RNC and an
unparented NodeB.
However, it is possible to select a parented NodeB (a NodeB belonging to a RNC subtree), in this case 3
kinds of operation can be done:
The RNC is unchanged: the user re-configures an existing Iub Interface between the NodeB and the
RNC.
Another RNC is selected: the user performs a re-parenting between an existing NodeB and a new
selected RNC.
No RNC is selected: the user deletes the current interface.

1 Iub Wizard
1.3 Main Tasks

IuB
RNC, IubIf, ServicegroupId, Atm/Atm+IP, Iub
transport type.
NodeB Parenting
CP, CCP, AAL2 stream, Signaling bearer, Pathid,

QoS definition, cac method, Uplane stream
definition
Streams Definition
BTS configuration
PCM and ATM configuration
BTS IP configuration
BTS IP adress, mask, gateway,

Udp port number
ATM switching
IN Configuration
Agregation point, DHCP
configuration
IP subnet management
Ip Subnet configuration
RNC IuB IP configuration
819

Streams Definition: 1 number of IP stream to be added with QoS of 3.

BTS IP Configuration :
1. Local Lan Presence and Dchp Used must equal false.
2. VLan Id must have no value or remain blank.
3. Ip Ran NodeB Address: <operator specific>
4. Gateway:: <operator specific>
UDP port number (heartbeat) equals 65535 unless it is changed under Rnc object.

1 Iub Wizard

Iub
8 1 10

Here are the main steps of the procedure to be performed when building the Iub interface configuration:
2. From the network tree, select where the wizard is going to apply (NodeB element).
3. From the Wizards & Operations panel (right part of the window), select the Iub Wizard and then
run it.
4. In the Iub wizard tree, choose the element to be configured.
5. In the Current Status window, choose the operation to be launched. Fill in the required parameter
value and validate.
To complete the operation, repeat the 2 last steps as many times as required.
Once the operation is completed, Close the Iub wizard and go back to the main window.

1.3.1 NodeB Parenting
s
ier
tif ness
n
Ide ique
Un
CellId m
CellId n
INVccGroup i
INVccGroup j
8 1 11
IN
INVccGroup k
CellId p

The goal of this operation is to chose the target RNC for NodeB parenting,define the associated
InVccGroup and to specify the transport solution used.
The bottom part of the window reminds the current CellId allocation for the selected NodeB and
offers the opportunity to change it whenever needed.

1.3.2 Iub Interface Parameters

INVccGroup
VCC OAM
VPi/VCi
VCC NodeBCP
VPi/VCi
VCC CCP
VPi/VCi
RNC
VCC DS traffic
VPi/VCi/PathId/QoSId
VCC NDS traffic
VCC HSPA traffic

OAM
CP
CCP

DS
NDS
HSPA
AAL5
AAL2/IP
PCM link (full ATM) or PCM

link and Ethernet link (hybrid)
ATM/ETH
PCM
8 1 12

Physical NodeB Connection

The NodeB allows PCM connections only (1 up to 8 links)
VCC Control Plane

The signaling VCC can be of the following types:

OAM VCC (only 1 link with a fixed VP/VC value: 0.32),
NodeB CP (only 1 link),
CCP (up to 6 CCP, one per CEM board).
ALCAP (Only 1 link)
VCC User Plane

The AAL2 bearer VCC can be of the following types:

DS (Delay Sensitive),
NDS (Non Delay Sensitive),
HSPA (HSDPA and HSUPA flows).
There can be up to 16 AAL2 bearers.

1.3.3 Streams Definition
8 1 13

This screen is used to define the number of Control Ports and AAL2 bearers to be added to the current
ATM flows definition.
At first launch, by default, there is no ALL2 bearers, no CCP and no ALCAP bearers. Based on the number
of streams that are added, rows will appear below in order to fill the requested parameters.
After a first ATM streams definition, NodeBCP addition is disabled, only CCP and AAL2 bearers can be
added.

1.3.4 AAL2 CAC Configuration
QoS0
ACR(QoS0) x qoS0BWReservation (aal2If)
SHARED
CacMethod (aal2If)
8 1 14
ACR(aal2If)
QoS1
ACR(QoS1) x qoS1BWReservation (aal2If)

qos
aal2If
aal2if

AAL2 CAC ensures that the admission of new calls does not cause traffic to exceed the provisioned ATM
bandwidth in either UL or DL. AAL2 CAC can be done per aal2If or per QoS according to the CacMethod
chosen.
Each RB has a cost called Equivalent Bit Rate that represents the bandwidth to be reserved. Available
bandwidth (called Available Cell Rate) is estimated by the RNC based on the ATM Traffic Descriptors
(PCR, SCR).
The new connection is accepted when:
If CACMethod=aal2If:
EBR(new connection on aal2If) + EBR(current connections on aal2If) ACR(aal2If)
If CACMethod=QoS (example of new DS connection):

If EBR(current NDS) < qos1BwReservation x ACR(NDS)

EBR(new DS) + EBR(current DS) < ACR(DS) + (1-qos1BwReservation)ACR(NDS)
Else:
EBR(new DS) + EBR(current DS) + EBR(current NDS) < ACR(DS) + ACR(NDS)

1.3.5 BTS PCM and ATM Configuration
RNC
8 1 15

The purpose of this task is to define the physical configuration of the Iub at BTS end.
First the PCM configuration must be defined selecting the number of PCM to be used.
Then the ATM layer characteristics at BTS side have to be specified. For each VCC type the appropriate
ATMProfile must be selected. The VP/VC settings are automatically computed by WPS.

1.3.6 NodeB OAM IP Flows Configuration
8 1 16

NodeB Aggregation
All the NodeB OAM VCCs are aggregated in the RNC-IN. Aggregated OAM traffic flow is then routed
to the OAM platform through CP3 Ethernet port (In-band or Out-band).
NodeB OAM configuration requires first the aggregation point to be defined (if not already created
before), and then to be selected.
DHCP Configuration
In addition, a NodeB IP address may be allocated statically or dynamically. If Dynamic allocation is

required, a DHCP server is inserted in the network. The bottom window of the above slide is
dedicated to this feature.

2 Iu Wizards
8 1 17


2 Iu Wizards
2.1 Iu Topologies
RANAP CS & PS
SCCP
RNC
RouteSet OPC x /DPC y
ALCAP
3G-MSC
PC y
AAL2 & AAL5 VCCs
PC
PC xx
8 1 18

The CoreNetwork is identified by means of one Destination Point Code per domain, one for CS and one
for PS. Alcatel-Lucent Core Network allows defining one common DPC for both domains.
Core Network identified by one common PC for both domains:
The common linkset carries SCCP/RANAP CS, ALCAP and SCCP/RANAP PS. At the RANAP layer, a
field indicates if the message is applicable to PS or CS domain.

2 Iu Wizards
2.1 Iu Topologies [cont.]

RANAP CS
SCCP
RNC
ALCAP
3G-MSC
PC y
AAL2 VCCs
MGw
MGw
PC
PC xx
RANAP PS
SCCP
SGSN
PC z
RouteSet OPC x /DPC z
8 1 19

Core Network identified by two PCs, one per Domain:

For a non Alcatel-Lucent Core Network , or a Alcatel-Lucent Core Network with USGSN and/or
UMGW configurations, two CN PCs will be configured to separately address CS and PS domains. The
CS linkset carries ALCAP and SCCP/RANAP and the PS linkset carries SCCP/RANAP PS.

2 Iu Wizards
2.1 Iu Topologies [cont.]

RANAP CS
SCCP
RNC
ALCAP
3G-MSC
PC y
AAL2 VCCs
MGw
MGw
ALCAP
PC
PC xx
RouteSet OPC x /DPC a
MGw
PC a
AAL2 VCCs
RANAP PS
SCCP
SGSN
PC z
8 1 20

Core Network identified by more than two PCs, one per domain, and other(s) for ALCAP:
Several CS coreNetwork pointCodes may be defined in the future to separate RANAP CS from
ALCAP. One PC identifies the CallServer, its routeSet carries RANAP CS. One or several PCs identify
one or several MediaGateways. Their routeSets carry ALCAP messages. One PC remains allocated
to PS domain; a routeSet dedicated to PS Signaling is configured based on RNC PC and
coreNetwork PS CP.

2 Iu Wizards
2.2 IuFlex
MSC
MSC
Pool
MSC
MSC
MSC
NodeB
MSC
MSC
CsCoreNetworkAcess/0
CsCoreNetworkAcess/1
RNC
PsCoreNetworkAcess/1
NodeB
SGSN
PsCoreNetworkAcess/0
SGSN
SGSN
SGSN
NodeB
SGSN
Pool
SGSN
SGSN
8 1 21

Without IuFlex the RNC can be connected to only one Core Network (CN) node within each CN domain
i.e. one MSC server (through up to 10 MGW) and one SGSN.
This hierarchical network topology lead to some limitations for instance in case of CN node failure, the
geographical coverage of several RNCs would be lost.
The IuFlex feature allows the connection of a RNC to several CN nodes (for a given operator) within each
CN domain. This network structure gives more flexibility to the network and increases its performance as
well as capacity and scalability.
The various CN nodes are grouped into pools and inside a given pool a UE is always attached to the same
CN node. An RNC could be connected to several pool areas for a same domain.
It is the responsibility of the RAN to find the CN node where the UE is attached or to choose a CN node
for the UE in case of first attachment or of a UE entering the pool area. A UE will always be served by
the CN node it has been attached to.
In the case of a CN node failure, new RAN connections are directed to another CN node in the pool.

2 Iu Wizards
2.3 IuCS Wizard - Main Tasks

IuCS
8 1 22

Here are the main steps of the procedure to be performed when building the IuCS interface
configuration:
2. From the network tree, select where the Wizard is going to apply (RNC element).
3. From the Wizards & Operations panel (right part of the window), select the IuCS Wizard and then
run it.
4. In the IuCS Wizard tree, choose the task to be performed.
value and validate.
Once the operation is completed, Close the IuCS Wizard and go back to the main window.

2 Iu Wizards
2.4 IuCS Definition
RANAP CS
SCCP
RNC
ALCAP
3G-MSC
PC y
MGw
AAL2 VCCs
PC x
RANAP PS
SCCP
8 1 23
SGSN
PC z

IuCS definition starts with the definition of the number of ALCAP distant signaling entities which value
depends on the type of Iu topology to be used.
If the IuCS is created from scratch, at this stage there is no RouteSet available to handle RANAP CS and
ALCAP. They are going to be created in the following tasks.
Otherwise some already defined RouteSets can be directly assigned in this first screen.

2 Iu Wizards

IuCS Control Plane RouteSets and LinkSets Configuration

IuCS Signaling Links ATM Switching
8 1 24


8 1 25

IuCS Control Plane configurations relies on the definition of IuCS RouteSets. These RouteSets are defined
setting the value of Core Network DPC and associated Network Indicator.
Multiple Control Plane IuCS links of the same RNC are aggregated into a IuCS linkset for greater signaling
reliability and capacity.
A linkset forms a logical connection between the RNC and the Core Network. One linkset is composed of
one or more IuCS links (up to 16). Multiple links can be provisioned to provide greater capacity and
reliability.
Once the IuCS Routesets are defined, the contents of their associated LinkSets has to be defined.

8 1 26

Once the IuCS RouteSet Definition task is complete, IuCS Wizard updates and displays a summary of all
the defined RouteSets and Associated LinkSets.
Next step consists in defining the ATM Switching characteristics of the signaling links of the IuCS LinkSet.

2 Iu Wizards
2.6 IuCS User Plane

IuCS AAL2 Paths

IuCS User Plane Definition
IuCS User Plane ATM Switching
IuCS with IuFlex Service Configuration
8 1 27


2.6 IuCS User Plane
2.6.1 AAL2 Paths
PS-FP 2
AAL2 Path
AAL2 Path
VPi
PS-FP 0
VSP board 1
AAL2 Path
PS-FP 1
Aggregation Node
Public
ATM
Backbone
PS-FP 3
VSP board 2
WG
RNC
ath
AAL2 P
aal2If / PathIds
1 aal2If per ALCAP DPC

8 1 28
1 A2EA @ per VSP2 board

AAL2 Paths Definition

A PathId is used to identify a Path within AAL2. The PathId value is unique in UTRAN (Iu, Iur and
Iub interfaces):
For a non Alcatel-Lucent Core Network case, the Core Network is identified by a DPC at MTP
layer and by an aal2If in the RNC. Within the aal2If, Pathids allow to reach this Core Network
(ALCAP DPC).
For Alcatel-Lucent Core Network case, the RNC PS-FP cards are connected to WG VSP2 cards
by means of aal2 paths. Each VSP2 card is identified by its A2EA. Within the aal2If, Pathids
allow to reach this VSP board (see the slide above).
ALCAP Signaling Definition

Each configured aal2If on the RNC side is associated with a pool of A2EA addresses of the Core
Network:
For Alcatel-Lucent Core Network case, you must configure 1 A2EA address for each VSP2
cards in the Wireless Gateway (only 1 aal2If).
For a non Alcatel-Lucent Core Network case, you must configure 1 A2EA address for each
ALCAP DPC (and 1 aal2If per DPC).

2.6 IuCS User Plane
2.6.2 IuCS User Plane Definition
8 1 29

IuCS User Plane configuration needs the three following steps to be performed:
Adding one A2EA to identify the target remote AAL2 Core Network Node.
Populating the interface with the appropriate number of AAL2 bearers.
Defining the ATM switching characteristics of the IuCS paths.

2.6 IuCS User Plane
2.6.3 IuCS User Plane ATM Switching
8 1 30

IuCS User Plane configuration needs the three following steps to be performed:
Adding one A2EA to identify the target remote AAL2 Core Network Node.
Populating the interface with the appropriate number of AAL2 bearers.
Defining the ATM switching characteristics of the IuCS paths.

2 Iu Wizards
2.7 IuCS with IuFlex Service Configuration
8 1 31

IuFlex uses a routing parameter (10 bits bit string) that is normally derived from the TMSI or P-TMSI if
these are available or from the IMSI or IMEI otherwise:
when derived from TMSI or P-TMSI the routing parameter is a Network Resource Identifyer (NRI),
when derived from IMSI or IMEI the routing parameter has a value V in the range 0 to 999.
Per configuration in the RAN node, this [0;999] range is split between provisioned CN nodes so that one
value V corresponds to a single CN node for a given domain.
NRI has a flexible length between 0 and 10 bits. A length of 0 indicates that the feature is not applied.
A Null-NRI has a very specific meaning: a 'null-NRI' indicates to the RNC that the NAS Node Selection
Function shall be used for selecting a CN node to receive a message. There is one unique 'null-NRI' in a
PLMN supporting pool functionality: it is a specific value defined by the operator for the network (not
necessarily composed of zeros).
The Null-NRI is part of core network node off-loading and load-redistribution feature.

2 Iu Wizards
2.8 IuPS Wizard - Main Tasks

IuPS
8 1 32

Here are the main steps of the procedure to be performed when building the IuPS interface
configuration:
3. From the Wizards & Operations panel (right part of the window), select the IuCS Wizard and then
run it.
4. In the IuPS Wizard tree, choose the task to be performed.
value and validate.
Once the operation is completed, Close the IuPS Wizard and go back to the main window.

2 Iu Wizards
2.9 IuPS Definition
RANAP CS
SCCP
RNC
ALCAP
3G-MSC
PC y
MGw
AAL2 VCCs
PC x
RANAP PS
SCCP
8 1 33
SGSN
PC z

IuPS definition starts with the selection of Iu topology to be used.

If the IuPS is created from scratch, at this stage there is no RouteSet available to handle RANAP PS. It is
going to be created in the following tasks.
Otherwise some already defined RouteSets can be directly assigned in this first screen.
For example, this may be the case if the IuCS has already been defined and if IuCS and IuPS are sharing
the same RouteSet.

2 Iu Wizards
2.10 IuPS Control Plane

RouteSets and LinkSets Configuration

Signaling Links ATM Switching
8 1 34


8 1 35

IuPS Control Plane configurations relies on the definition of IuPS RouteSets. These RouteSets are defined
setting the value of Core Network DPC and associated Network Indicator.
Multiple Control Plane IuPS links of the same RNC are aggregated into a IuPS linkset for greater signaling
reliability and capacity.
A linkset forms a logical connection between the RNC and the Core Network. One linkset is composed of
one or more IuPS links (up to 16). Multiple links can be provisioned to provide greater capacity and
reliability.
Once the IuPS Routesets are defined, the contents of their associated LinkSets has to be defined.

8 1 36

Once the IuPS RouteSet Definition task is complete, IuPS Wizard updates and displays a summary of all
the defined RouteSets and Associated LinkSets.
Next step consists in defining the ATM Switching characteristics of the signaling links of the IuPS LinkSet.

2 Iu Wizards

IP Routing Configuration
IP Subnet Configuration
IP Streams ATM Switching
DSCP IP CoS to ATM VCC Mapping
DSCP Configuration
8 1 37


2.11.1 IP Routing Configuration
IP Network
172.253.0.0/20
IN
Layer 3
IuPS
VR/1
172.253.3.2
Port/15
Slot/8
Layer 2
RNC
8 1 38
IuPS
172.253.3.3
Conversational VCC: 2.51 IpCoS3

Streaming VCC: 2.50 IpCoS2
Interactive VCC: 2.49 IpCoS1
Background VCC: 2.48 IpCoS0
ATM Backbone
SGSN

The slide above illustrates the Layer 3 and Layer 2 configuration between the RNC and the next Core
Network Node (Aggregation node and SGSN). A virtual router (VR/4) is used in the Aggregation Node to
route GTP-U traffic from/to the SGSN to/from one RNC.
Layer 2 (ATM) Configuration
The following data traffic VCCs for Packet Switched are defined
AAL5 VCCs with a CBR QoS carrying IP PDU CoS 3 (higher priority)
AAL5 VCCs with a rtVBR QoS carrying IP PDU CoS 2
AAL5 VCCs with a nrtVBR QoS carrying IP PDU CoS 1
AAL5 VCCs with a UBR QoS carrying IP PDU CoS 0 (lower priority)
Note QoS correspond to the Class Of Service.
Layer 3 (IP) Configuration

The following IP addresses are required on Iu interface:

IP address and subnet mask of the I-Node interface.

IP address of the Core Network gateway. (In a Alcatel-Lucent implementation it corresponds
to the Aggregation node IP address).

2.11.2 IP Subnet Configuration
8 1 39

The first step of the IuPS User Plane configuration consist in setting its Layer 2 and the Layer 3
attributes.
Layer3: defining the IP addressing plan on IuPS interface:
Setting the RNC IP address and subnet mask for.
Setting the CN Gateway IP Address used to reach the SGSN.

2.11.3 IP Streams ATM Switching
8 1 40

The first step of the IuPS User Plane configuration consist in setting its Layer 2 and the Layer 2 attributes
with the defining the IP Streams ATM Switching:
Defining a traffic VCC for each packet switching class of service: set VP Switching, I-Node
Slot/port number and VP/VC values.
Setting the associated Class of Service for each VCC (at least, one Vcc is allocated per traffic
class):
Conversational (CoS 3)
Streaming (CoS 2)
Interactive (CoS 1)
Background (CoS 0).

2.11.4 DSCP IP CoS to ATM VCC Mapping

Traffic Class: AF (Assured Forwarding):
AF 4: Conversational
AF 3: Streaming
A/R: Drop Priority

DP 1: Gold
DP 2: Silver
DP 3: Bronze
AF 2: Interactive
AF 1: Background
Subscriber type
Gold
Silver
ATM VCC mapping
Bronze
Traffic Class
Conversational
Streaming
Interactive
Background
IpCos3
AF 4 -DP1
AF 4 DP2
AF 4 DP3
VC 51
AF 3 -DP1
AF 3 DP2
AF 3 DP3
VC 50
AF 2 -DP1
AF 2 DP2
AF 2 DP3
VC 49
nrtVBR
AF 1 -DP1
AF 1 DP2
AF 1 DP3
VC 48
UBR
CBR
rtVBR
VP
Physical
Port
IpCos0
Iu
8 1 41

The 3G-SGSN supports PS traffic routing using QoS parameters. UMTS is required to support the use of
multiple applications on the UE which will have various QoS requirements. To make efficient use of
resources, a QoS specific to each application class needs to be provided: it is called DSCP (Diff-Serv
Code Point) or Diff-Serv marking.
UMTS nodes allocate a subscriber QoS by marking the IP packet. This QoS is obtained with 2 parameters:
Traffic Class (type of traffic: 4 levels of Assured Forwarding)
A/R (Allocation/Retention: drop priority of the user, 3 levels).
The traffic flow of the service layer is mapped on the ATM VCC thanks to the DSCP marking:
A service is identified with a Traffic class and a drop priority.

For example a conversational traffic for a gold user (service with the higher priority) is
identified by AF-4 and DP-1 (AF41).
Each couple Traffic Class/Drop Priority is mapped on one VCC according to the IPCoS associated to
this VCC.

2.11.5 DSCP Configuration
8 1 42

The second main step of the IuPS User Plane configuration consist in defining the mapping between the
Diff-Serv Code Points and the IPcos links.
Service to Layer 3 mapping
The right-most screen shown in the above slide allows to mark a service identified by its traffic
class (conversational, streaming, interactive, background) and its subscriber priority (gold, silver,
bronze) with a DSCP value (AF and DP).
Layer 3 to Layer 2 mapping

Then each DSCP has to be mapped on a IPCoS link (at least one VCC for each IPCoS has to be
defined).

2.11.6 IuPS with IuFlex Service Configuration
8 1 43

IuFlex uses a routing parameter (10 bits bit string) that is normally derived from the TMSI or P-TMSI if
these are available or from the IMSI or IMEI otherwise:
when derived from TMSI or P-TMSI the routing parameter is a Network Resource Identifyer (NRI),
when derived from IMSI or IMEI the routing parameter has a value V in the range 0 to 999.
Per configuration in the RAN node, this [0;999] range is split between provisioned CN nodes so that one
value V corresponds to a single CN node for a given domain.
NRI has a flexible length between 0 and 10 bits. A length of 0 indicates that the feature is not applied.
A Null-NRI has a very specific meaning: a 'null-NRI' indicates to the RNC that the NAS Node Selection
Function shall be used for selecting a CN node to receive a message. There is one unique 'null-NRI' in a
PLMN supporting pool functionality: it is a specific value defined by the operator for the network (not
necessarily composed of zeros).
The Null-NRI is part of core network node off-loading and load-redistribution feature.

3 Iur Wizard
8 1 44


3 Iur Wizard
3.1 Iur Wizard - Introduction

Alcatel-Lucent
Alcatel-Lucent RNC
Alcatel-Lucent RNC
OAM
Cluster
Alien RNC
Alcatel-Lucent RNC
8 1 45

The Iur Wizard is used to configure several interfaces between a selected RNC (viewed as the Serving
RNC) and other RNCs (viewed as potential Drift RNCs).
The Drift RNCs can either be managed by the same OAM server or managed by others OAM platforms,
they can be part of Alcatel-Lucent products or of other manufacturers. In the last case, the Drift RNC
will be declared as alien RNC.

3 Iur Wizard
3.2 Iur Wizard - Main Tasks

Iur
8 1 46

Here are the main steps of the procedure to be performed when building the Iur interface configuration:
3. From the Wizards & Operations panel (right part of the window), select the Iur Wizard and then run
it.
4. In the Iur Wizard tree, choose the task to be performed.
value and validate.
Once the operation is completed, Close the Iur Wizard and go back to the main window.
For an Alien Iur this procedure is only performed once.
For a Alcatel-Lucent Iur this procedure has to be applied on the two ends of the interface.

3 Iur Wizard
3.3 Iur Creation

Iur RouteSets Definition

Iur Creation
Wizards Switch for Alcatel-Lucent Iur
8 1 47


3.3 Iur Creation
3.3.1 Iur RouteSets Definition

Alcatel-Lucent Iur:
only 1 RouteSet (ALCAP/SCCP)
Alcatel-Lucent RNC
Neighboring RNC
OPC
DPC
DPC: 123
Alcatel-Lucent RNC
Alien Iur:
1 SCCP RouteSet
1 ALCAP RouteSet
DPC
DPC
SCCP DPC: 236
Alcap DPC: 235

Alien RNC
8 1 48

Drift RNC Point Code and Iur RouteSet Definition

The Drift RNC is identified by means of at least one Point Code.
Usually, a single Point Code on the Drift RNC is used to setup a (SCCP/ALCAP) RouteSet which
carries both RNSAP and ALCAP.
This is the implementation done in case of a Alcatel-Lucent Drift RNC.
It is also possible (alien Drift RNC case) to have one or more distinct ALCAP Point Codes on the
Drift RNC. In this case one (ALCAP) RouteSet is setup for each ALCAP Point Code in order to carry
ALCAP messages.

3.3 Iur Creation
3.3.2 Iur Creation
8 1 49

The first step of Iur creation consists in identifying the Drift RNC by means of RNCId.
In case of Alcatel-Lucent Iur, by default only one Routeset is defined carrying both ALCAP and RNSAP
messages.
For an Alien Iur, the number of ALCAP RouteSets has to be defined.

3.3 Iur Creation
3.3.3 Wizards Switch for Alcatel-Lucent Iur
8 1 50

In case of Alcatel-Lucent Iur, WPS wizards offers the possibility to alternatively jump from one end of the
Iur to the other, so that the global setting of the Iur can follow the exact same evolution steps on the 2
RNCs involved.

3 Iur Wizard

Alcatel-Lucent Iur Routesets Definition

Alien Iur RouteSets Definition
Signaling Links ATM Switching
8 1 51


3.4.1 Alcatel-Lucent Iur Routesets Definition
8 1 52

When building a Alcatel-Lucent Iur, WPS has already the knowledge of the Drift RNC PC. Therefore after
the completion of the Iur Definition task, all the mandatory attributes of the Alcatel-Lucent Iur Routeset
are completely setup.
At this stage of the Iur configuration, WPS updates and displays the various RouteSets already defined for
the current Serving RNC.
This is also the place where the configuration of the various LinkSets can be adjusted to the operator
needs adding or removing Signaling Links.

3.4.2 Alien Iur RouteSets Definition
8 1 53

In case of Alien Iur configuration, one Routeset is defined for SCCP and one RouteSet is defined per
ALCAP DPC.
The definition of these various RouteSets only requires the appropriate DPC and Network Indicator to be
entered in the tool.
Then each RouteSet must be assigned to its type of message i.e. RNSAP or ALCAP.

8 1 54

In order to complete the configuration of the Iur Control Plane, the ATM switching characteristics of all
the Signaling links must be defined.
This operation is done RouteSet per RouteSet.
As usual the VP/VC settings are automatically computed by the tool.

3 Iur Wizard
3.5 Iur User Plane

Traffic Links Definition

Alcatel-Lucent Iur AAL2 Paths Definition
Alien Iur AAL2 Paths Definition
AAL2 Path ATM Switching
8 1 55


3.5 Iur User Plane
3.5.1 Traffic Links Definition

QoS 0
Alcatel-Lucent RNC
VPi / VCi
DS
ATM
Backbone
PathId / 1
OPC
DPC
VPi / VCi
NDS
Alcap
DPC: 126
PathId / 4
Alcatel-Lucent RNC
QoS 1
Slot / Port nb
1 A2EA per ALCAP DPC

DPC
DPC
ALCAP DPC: 103

Alien RNC
8 1 56

Iur A2EA Definition

For all dynamically established connections, each source and destination interface needs a unique
ATM address. AAL2 transport layer addressing (called A2EA) is based on the NSAP addressing
format (ITU E191). A2EA address is used within the message RAB establishment Request.

If a Alcatel-Lucent Drift RNC is used, one A2EA address is configured per Drift RNC.
If a non Alcatel-Lucent Drift RNC is used, AAL2 addressing depends on other vendor
implementation. Usually there is 1 A2EA address configured per ALCAP DPC.
Traffic Link Definition

The number of Iur AAL2 paths is the result of dimensioning activity. Usually up to 2 AAL2
connections for DelaySensitive traffic and up to 2 AAL2 connections for NonDelaySensitive traffic
are provisioned.
An AAL2 connection is identified by a pathId and carry DelaySensitive traffic and

NonDelaySensitive traffic.
One QoS value is allocated to each kind of traffic. The following QoS parameters are associated to
the PathIds:
For AAL2 connections carrying DS traffic, Pathid/Qos = 0
For AAL2 connections carrying NDS traffic, Pathid/Qos = 1

3.5 Iur User Plane
3.5.2 Alcatel-Lucent Iur AAL2 Paths Definition
8 1 57

When building a Alcatel-Lucent Iur, WPS has already the knowledge of the Drift RNC NSAP address.
Therefore after the completion of the Iur Definition task, the Iur User Plane is already setup except for
the number and characteristics of AAL2 bearers.
After the number of AAL2 paths has been defined (upper part of the window) three types of parameters
have to be defined at this stage:
PathId
QoSId
RNC Path Owner.
At this stage of the Iur configuration, WPS offers the possibility to review and modify the configuration of
all the Iur AAL2 bearers (see rightmost screen in the above slide).

3.5 Iur User Plane
3.5.3 Alien Iur AAL2 Paths Definition
8 1 58

When building a Alien Iur, WPS needs to know the Drift RNC NSAP address. Defining this NSAP address is
the purpose of the top screen shown in the above slide.
Then the number of AAL2 paths has to be defined (upper part of the rightmost window) and their
characteristics have to be set. Three types of parameters have to be defined at this stage:
PathId
QoSId
RNC Path Owner.
At this stage of the Iur configuration, WPS offers the possibility to review and modify the configuration of
all the Iur AAL2 bearers (see bottom screen in the above slide).

3.5 Iur User Plane
3.5.4 AAL2 Path ATM Switching
8 1 59

The last step to perform is to define the ATM switching characteristics of the Iur AAL2 bearers.
As usual the VP/VC settings are automatically computed by the tool.



for this module
8 1 60


End of Module
Interface Wizards
8 1 61


Last But One Page

1
@@PRODUCT
@@COURSENAME
All Rights Reserved Alcatel-Lucent @@YEAR

@@COURSENAME - Page 1

Passing on and copying of this document, use and communication of its
contents not permitted without written authorization from Alcatel-Lucent
@@COURSENAME - Page 2

Tmo18262d0sgdeni1 0

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Tmo18262d0sgdeni1 0

Uploaded by

Copyright:

Available Formats

9352 WiPS

TMO18262 9352 WPS UAO7

All Rights Reserved Alcatel-Lucent 2010

All rights reserved Alcatel-Lucent @@YEAR

All Rights Reserved Alcatel-Lucent 2010

All Rights Reserved Alcatel-Lucent 2010

This page is left blank intentionally

All Rights Reserved Alcatel-Lucent 2010

Terms of Use and Legal Notices

All rights reserved Alcatel-Lucent @@YEAR

All Rights Reserved Alcatel-Lucent 2010

All Rights Reserved Alcatel-Lucent 2010

This page is left blank intentionally

All Rights Reserved Alcatel-Lucent 2010

4. Topic/Section is Positioned Here

Module 1. WiPS Environment TMO18262 D0 SG DEN I1.0

2. Topic/Section is Positioned Here

Section 6. RNC Wizard

3. Topic/Section is Positioned Here

All Rights Reserved Alcatel-Lucent 2010

All Rights Reserved Alcatel-Lucent 2010

Course Outline [cont.]

All Rights Reserved Alcatel-Lucent 2010

This page is left blank intentionally

All Rights Reserved Alcatel-Lucent 2010

Welcome to TMO18262 9352 WPS UAO7 UTRAN Configuration

Upon completion of this course, you should be able to:

describe the physical architecture of the RNC for UMTS network

All Rights Reserved Alcatel-Lucent 2010

All Rights Reserved Alcatel-Lucent 2010

Course Objectives [cont.]

All Rights Reserved Alcatel-Lucent 2010

This page is left blank intentionally

All Rights Reserved Alcatel-Lucent 2010

About this Student Guide

All Rights Reserved Alcatel-Lucent 2010

Where you can get further information

If you want further information you can refer to the following:

All Rights Reserved Alcatel-Lucent 2010

About this Student Guide [cont.]

Switch to notes view!

All Rights Reserved Alcatel-Lucent 2010

This page is left blank intentionally

All Rights Reserved Alcatel-Lucent 2010

Surname, First name :

1 To be able to describe the physical architecture

2 To be able to describe HW modules functions

All Rights Reserved Alcatel-Lucent 2010

3 To be able to describe Defense Mechanisms

4 To be able to describe O&M architecture

All Rights Reserved Alcatel-Lucent 2010

Self-assessment of Objectives [cont.]

All Rights Reserved Alcatel-Lucent 2010

Thank you for your answers to this questionnaire

All Rights Reserved Alcatel-Lucent 2010

Do not delete this graphic elements in here:

All Rights Reserved Alcatel-Lucent 2010

All Rights Reserved Alcatel-Lucent 2010

All Rights Reserved Alcatel-Lucent 2010

UTRAN Configuration UTRAN Configuration

This page is left blank intentionally

All Rights Reserved Alcatel-Lucent 2010

All Rights Reserved Alcatel-Lucent 2010