CT2K User Manual

Wireless Service Provider Solutions
CT2000 User Reference Manual

PE/DCL/DD/0137 14.12/EN Standard July 2004
411--9001--137
< 137 > : CT2000 User Reference Manual

Document number: PE/DCL/DD/0137
411--9001--137
Document status: Standard
Document issue: 14.12/EN
Product release: GSM/BSS V14.3
Date: July 2004
Copyright 2001--2004 Nortel Networks, All Rights Reserved
Originated in France
NORTEL NETWORKS CONFIDENTIAL:
The information contained in this document is the property of Nortel Networks. Except as specifically authorized in
writing by Nortel Networks, the holder of this document shall keep the information contained herein confidential and
shall protect same in whole or in part from disclosure and dissemination to third parties and use for evaluation,
operation and maintenance purposes only.
You may not reproduce, represent, or download through any means, the information contained herein in any way or in
any form without prior written consent of Nortel Networks.
The following are trademarks of Nortel Networks: *NORTEL NETWORKS, the NORTEL NETWORKS corporate logo,
the NORTEL Globemark, S2000, S4000, S12000. GSM is a trademark of France Telecom.
Sybase is a registered trademark of Sybase, Inc. Windows is a U.S. registered trademark of Microsoft Corp.
All other brand and product names are trademarks or registered trademarks of their respective holders.
Nortel Networks Confidential Publication History iii
PUBLICATION HISTORY
System release: GSM/BSS V14.3
CT 2000 V2.1
July 2004
Issue 14.12 /EN V14.3 Standard
Final cleanup and publication activities.
December 2003
For CR Q00758757, added SME comments for the following parameters:
DefaultReservedBitForRSM
DefaultRSMModeComput
DefaultAbisMask
November 2003
Issue 14.10 /EN V14.3 Preliminary
For CR Q00767311, added caution to TRXHardwareRef
For CR Q00719599, added paragraphs to 1.4.6.2 CT--File loader.
For CR Q00716750--01, lapdTerminalNumber parameter paragraph was added.
August 2003
Minor editorial update
April 2003
Minor editorial update
April 2003
Copyright E 2001--2004 Nortel Networks CT2000 User Reference Manual

iv Publication History Nortel Networks Confidential
The following changes were made:

Chapter 2 CT2000 Basis:
Update in the procedure 2--1 Installing the CT2000 using Windows NT4.0
Update in the procedure 2--4 Installing the CT2000 using Window 2000
January 2003
Features taken into account:
V14.3 Compliancy
Update in paragraph 1.4.12 Generation of command file
Update in paragraph 3.1.2.3 Interfaces menus
Update in paragraph 3.2.1.4 PCU editor
Update in paragraph 3.2.1.5 PCUSN editor
Update in paragraph 3.2.1.7 BSC editor
Update in paragraph 3.2.1.8 TCU editor
Update in paragraph 3.2.1.9 Aint editor
Update in paragraph 3.2.1.10 Site editor
Update in paragraph 3.2.1.11 Cell editor
Update in paragraph 3.2.1.12 HOV editor
Update in paragraph 3.2.1.13 PWC editor
Update in paragraph 3.2.1.14 TRX editor
Update in paragraph 3.2.1.15 TDMA editor
Update in paragraph 3.2.1.16 TSZ editor
Update in paragraph 3.2.1.17 NEI editor
Update in paragraph 3.2.2.3 PCU template editor
Update in paragraph 3.2.2.4 BSC template editor
Update in paragraph 3.2.2.5 Site template editor
Update in paragraph 3.2.2.6 Cell template editor
Update in paragraph 3.2.2.7 HOV template editor
PE/DCL/DD/0137 Standard 14.12/EN July 2004 Copyright E 2001--2004 Nortel Networks

411--9001--137
Nortel Networks Confidential Publication History v
Update in paragraph 3.2.1.8 PWC template editor

Update in paragraph 3.2.2.9 TRX template editor
Update in paragraph 3.2.2.10 TDMA template editor
Update in paragraph 3.2.2.11 NEI template editor
Update in paragraph 3.2.2.12 Aint template editor
Update in paragraph 3.2.2.13 TCU template editor
Update in paragraph 3.2.2.1 TSZ template editor
Update in paragraph 3.2.2.15 PCUSN template editor
January 2003
Issue 14.05/EN Preliminary
Audits reports
HW&SW Reference Management
Automatic Exchange with OMC
Chapter 1 CT2000 general presentation
Update in paragraph 1.6.3.2 Class2 modification plug--in as answer to CR
Q00570166
Update in the following paragraphs to take account V14 parameters:
3.2.1.7 BSC editor
3.2.1.9 Aint editor
3.2.1.10 Site editor
3.2.1.11Cell editor
3.2.1.12 HOV editor
3.2.1.15 TDMA editor
3.2.1.17 NEI editor
3.2.2.4 BSC template editor
3.2.2.5 Site template editor
3.2.2.6 Cell template editor
3.2.2.7 HOV template editor

vi Publication History Nortel Networks Confidential
3.2.2.8 PWC template editor

3.2.2.10 TDMA template editor
November 2002
Update for V14.3 BSS release
V14.3 Compliancy
Checks for AMR
Checks for V14.2 BSS features
DRF format
Checks for V14.3 BSS features
DRF template Files Import
Support of S12000
The CR Q00519507 chapter 2 has no effect (updated in the previous edition).
October 2002
Split of the CT 2000 User Manual in two volumes:
CT2000 User Reference Manual NTP 137 (Chapter 1 to 3 of the CT2000 User
Manual)
CT2000 User Procedures Manual NTP 148 (Chapter 4 to 8 and Appendixs of the
CT2000 User Manual)
October 2002
Feature taken into account:
Windows 2000 compliancy
Update after Internal review.
Chapter 1 CT2000 general presentation
Update in paragraph 1.1

411--9001--137
Nortel Networks Confidential Publication History vii
Chapter 2 CT2000 basics

Update in paragraph 2.2.2, 2.2.3, 2.2.4.
Created paragraph 2.2.5 Warning about renaming PC or modifying network
domain
Update in procedures 2--1, 2--2, 2--3, 2--4, 2--5.
Update in procedure 2--9
October 2002
Issue 14.01/EN Draft
Chapter 2 CT2000 Basis:
Added procedures 2--2, 2--3, 2--4 about installing CT2000 using Windows
2000.
System release: GSM/BSS V13
July 2002
Issue 13.09/EN Standard
Issue compliant with:
General Availability of the BSS system release V13.02/V12.4
CT2000 tool release V13.02.12
July 2002
July 2002
Update after internal review.

viii Publication History Nortel Networks Confidential

July 2002
June 2002
The following changes were made in individuals chapters:
Chapter 2 CT2000 Basics:
Answer to the Services Request SR 30373937 and SR 30373519 : update
Procedure 2--1 Installing the CT2000
Created procedure 2--3 Loading the default templates as answer to CR
Q00425757
December 2001
General Availability of the BSS system release V13.02
V13.02 release update after internal review.
The following changes were made in individual chapters:
Chapter 1 CT2000 general presentation:
Update in Paragraph 1.6.3.2 Parameter classes
Update in Paragraph 2.2.2 Software required

411--9001--137
Nortel Networks Confidential Publication History ix
November 2001
General Availability of the BSS system release V13.02
Patch level 20011016_01
The following changes were made in individual chapters:
About this document:
Update in Paragraph Applicability
Chapter 1 CT2000 general presentation:
Update in Figure 1--8 : OMC--R plug--in interface
Created new Paragraph 1.6.4 A Interface Management plug--in
Update in Paragraph 2
Chapter 3 CT2000 PC--Part Human Machine Interface:
Updare in Figure 3--2 : Menu bar
Update in Figure 3--36 : About the CT2000 Application window
August 2001
Modification after review
August 2001
Update for V13 release of CT2000
System release: GSM/BSS V12
June 2001
Modification after review
March 2001
Creation.

x Table of contents Nortel Networks Confidential
About this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 0-- 1

Applicability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 0--1
Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 0--1
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 0--1
Related documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 0--1
How this document is organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 0--1
Typographic conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 0--2
Acronyms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 0--3
Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 0--4
1 CT2000 general presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-- 1

1.1 Product overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1--1
1.2 Product definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1--1
1.3 CT2000 architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1--4
1.3.1 General architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1--4
1.3.2 Hardware platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1--6
1.3.3 Software required using Windows NT4.0 . . . . . . . . . . . . . . . . . . . . . . . . . 1--6
1.3.4 Software required using Windows 2000 . . . . . . . . . . . . . . . . . . . . . . . . . . 1--6
1.3.5 Example of CT2000 network architecture . . . . . . . . . . . . . . . . . . . . . . . . . 1--7
1.4 CT2000 functionalities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1--9
1.4.1 Creation and management of workspace . . . . . . . . . . . . . . . . . . . . . . . . . 1--11
1.4.2 Template management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1--11
1.4.3 TDMA frame and mapping model management . . . . . . . . . . . . . . . . . . . 1--12
1.4.4 Network editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1--12
1.4.5 Network element list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1--12
1.4.6 Database DRF loader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1--12
1.4.7 Graphic network tree viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1--14
1.4.8 BSS object editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1--14
1.4.9 Neighboring editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1--14
1.4.10 Database network checker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1--15
1.4.11 Data base export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1--15
1.4.12 Generation of command files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1--16
1.5 CT2000 interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1--18
1.5.1 CT2000 engineering interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1--18
1.5.2 CT2000 to OMC--R interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1--23
1.5.3 CT2000 PC to GPRS Passport provisioning tool plug--in . . . . . . . . . . . . 1--24

411--9001--137
Nortel Networks Confidential Table of contents xi
1.5.4 CT2000 to CT2000 OMC--R plug--ins . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1--26

1.6 OMC--R plug--ins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1--27
1.6.1 ODB retrieve plug--in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1--28
1.6.2 NRP/Command File generation plug--in . . . . . . . . . . . . . . . . . . . . . . . . . . 1--28
1.6.3 Class 2 modification plug--in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1--28
1.6.4 A Interface management plug--in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1--30
1.7 CT2000 administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1--35
2 CT2000 basics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2--1

2.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2--1
2.2 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2--1
2.2.1 Operating System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2--1
2.2.2 Software required using Windows NT4.0 . . . . . . . . . . . . . . . . . . . . . . . . . 2--1
2.2.3 Software required using Windows 2000 . . . . . . . . . . . . . . . . . . . . . . . . . . 2--1
2.2.4 User privilege requirement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2--1
2.2.5 Warning about renaming PC or modifying network domain . . . . . . . . . . 2--1
3 CT2000 PC-- Part Main Human Machine Interface . . . . . . . . . . . . . 3--1

3.1 CT2000 Main Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--1
3.1.1 Title bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--2
3.1.2 Menu bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--2
3.1.3 ToolBar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--88
3.1.4 Network Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--90
3.1.5 Menu area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--90
3.1.6 Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--97
3.1.7 Operation traces area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--97
3.1.8 Status bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--98
3.2 Objects Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--99
3.2.1 Object Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--99
3.2.2 Template editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--137
3.2.3 Network checker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--163

xii List of figures Nortel Networks Confidential
Figure 1--1 CT2000 position in an operator network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1--2

Figure 1--2 Input/Output data of the CT2000 -- Functional view . . . . . . . . . . . . . . . . . . . . . 1--3
Figure 1--3 CT2000 general architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1--5
Figure 1--4 CT2000 network architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1--8
Figure 1--5 Example of CT2000 object dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1--10
Figure 1--6 CT2000 Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1--19
Figure 1--7 CT2000--GPRS interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1--25
Figure 1--8 OMC--R plug--in interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1--27
Figure 1--9 A Interface management plug--in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1--31
Figure 2--1 CT2000 Main Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2--23
Figure 3--1 CT2000 Main window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--1
Figure 3--2 Menu bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--2
Figure 3--3 Setup window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--4
Figure 3--4 Network Editor window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--6
Figure 3--5 Import DRFs window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--22
Figure 3--6 Import DRF Report window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--25
Figure 3--7 Export DRF window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--28
Figure 3--8 Load CT Files window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--31
Figure 3--9 Export CTSDO window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--33
Figure 3--10 Import Template window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--35
Figure 3--11 Export Template window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--38
Figure 3--12 Network Element Template Manager window . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--40
Figure 3--13 Global update Manager window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--45
Figure 3--14 Network Checker window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--46
Figure 3--15 Network Checker -- Report window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--50
Figure 3--16 Network Checker -- Edition window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--51
Figure 3--17 Network Checker -- new profile window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--52
Figure 3--18 Network Checker -- Save window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--54
Figure 3--19 Network Checker -- Modify window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--55
Figure 3--20 Network Checker -- Copy window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--56
Figure 3--21 Datafill Rules window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--57
Figure 3--22 Datafill Rules -- Report window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--61
Figure 3--23 Datafill Rules -- Edition window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--63
Figure 3--24 Datafill Rules -- New Profile window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--64
Figure 3--25 Datafill Rules -- Save window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--66

411--9001--137
Nortel Networks Confidential List of figures xiii
Figure 3--26 Datafill Rules -- Modify window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--67

Figure 3--27 Datafill Rule -- Copy window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--68
Figure 3--28 Log session editor window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--70
Figure 3--29 Rules Session Editor window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--71
Figure 3--30 Network Element List Manager window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--72
Figure 3--31 Network Tree window -- Hierarchical TV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--74
Figure 3--32 Network Tree window -- Topological TV window . . . . . . . . . . . . . . . . . . . . . . . . . 3--76
Figure 3--33 Network Tree window -- Template TV window . . . . . . . . . . . . . . . . . . . . . . . . . . 3--77
Figure 3--34 Menu window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--82
Figure 3--35 Operation traces window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--83
Figure 3--36 About CT 2000 Application window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--86
Figure 3--37 Microsoft System Information window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--87
Figure 3--38 Alternative editor window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--100
Figure 3--39 OMC editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--101
Figure 3--40 PCU editor window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--103
Figure 3--41 PCUSN editor window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--104
Figure 3--42 MSC editor window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--105
Figure 3--43 BSC editor window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--106
Figure 3--44 TCU editor window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--108
Figure 3--45 AINT editor window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--110
Figure 3--46 SITE editor window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--112
Figure 3--47 CELL editor window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--115
Figure 3--48 HOV editor window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--121
Figure 3--49 PWC editor window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--123
Figure 3--50 TRX editor window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--125
Figure 3--51 TDMA editor window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--126
Figure 3--52 TSZ editor window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--128
Figure 3--53 NEI object editor window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--129
Figure 3--54 Neighboring editor window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--131
Figure 3--55 Network template editor window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--139
Figure 3--56 OMC template editor window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--141
Figure 3--57 PCU template editor window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--142
Figure 3--58 BSC template editor window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--143
Figure 3--59 SITE template editor window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--145
Figure 3--60 CELL template editor window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--146

xiv List of figures Nortel Networks Confidential
Figure 3--61 HOV template editor window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--151

Figure 3--62 PWC template editor window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--154
Figure 3--63 TRX template editor window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--156
Figure 3--64 TDMA template editor window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--157
Figure 3--65 NEI template editor window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--158
Figure 3--66 AINT template editor window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--159
Figure 3--67 TCU template editor window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--161
Figure 3--68 TSZ template editor window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--162

411--9001--137
Nortel Networks Confidential List of tables xv
Table 1--1 DRF Files and modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1--13

Table 1--2 File extensions for BSS DRF tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1--20
Table 1--3 File extensions for templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1--22
Table 1--4 File extensions for mapping/TDMA models . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1--23
Table 1--5 File extension for PCUSN DRF tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1--24

xvi List of procedures Nortel Networks Confidential
Procedure 2--1
Installing the CT2000 using Windows NT4.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2--2
Procedure 2--2
Installing the CT2000 using Windows 2000 preliminary: Modifying the local security policies 2--8
Procedure 2--3
Installing the CT2000 using Windows 2000 preliminary: Modifying Windows 2000 user profile
security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2--11
Procedure 2--4
Installing the CT2000 using Windows 2000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2--13
Procedure 2--5
Creating Shorcut in Startup Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2--21
Procedure 2--6
Starting the CT2000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2--23
Procedure 2--7
Loading the Default Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2--25
Procedure 2--8
Quitting the CT2000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2--26
Procedure 2--9
Uninstalling the CT2000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2--27

411--9001--137
Nortel Networks Confidential About this document 0--1
ABOUT THIS DOCUMENT

This document is the User Reference Manual for the CT2000, one of the BSS
network Configuration Tools developed by Nortel Networks.
Applicability
This manual applies to version V2.1 of the CT2000 which is compliant with BSS
releases from V12 to V14.3.
Audience
This manual is for users in charge of:
configuring BSS networks based on GSM/GPRS recommendations and built
upon the Nortel Networks BSS
BSS datafill (which involves the creation of command files for an OMC--R)
Prerequisites
A good knowledge of BSS configuration principles as well as Microsoft Windows
NT 4.0 or Windows 2000 are required before reading this manual.
Related documents
< 01 > : BSS Overview
< 06 > : OMC--R Architecture and Reference Manual
< 07 > : BSS Operating Principles
< 124 > : BSS Parameter Dictionary
< 148 > : CT2000 User Procedures Manual
How this document is organized

Chapter 1 is the CT2000 general presentation. It describes the product and its
functionality. It gives the CT2000 network and software description.
Chapter 2 gives the CT2000 basics: Installing, starting and quitting the CT2000.
Chapter 3 describes the CT2000 Human Machine Interface. It explains how to use
the CT2000 menus.

0--2 About this document Nortel Networks Confidential
Typographic conventions
The selection of a command from the CT2000 HMI is indicated by the succession
of menus or commands, followed by -->.
Example
Selecting the Import command of the DRF Objects menu (submenu of DRF Tree)
is indicated by:
DRF Tree - > DRF Objects - > Import

411--9001--137
Acronyms
ASCII American Standard Code for Information Interchange
BCF Base Common Functions (common BTS control and switching unit)
BPM BSS Parenting Menu
BSC Base Station Controller
BSS Base Station Subsystem
BTS Base Transceiver Station
CD--ROM Compact Disk Read Only Memory
CIC Terrestrial Circuit Identification Code (on A interface)
CM Configuration Management function of the OMC--R
CP Cell Planning (CT3100 tool)
CT--SDO CT Operational Data Server of OMC--R (Serveur de Donnees
Operationnelles in French)
DBMS DataBase Management System
DCS Digital Cellular System (Radio Cellular Network standard adapted for the
1800MHz frequency band)
DDTI Dual Digital Trunk Interface
DF Datafill ( Activity used for the configuration of a BSS network)
DRF Data Request Form
DSR Data Service Request
GPRS General Packet Radio Service
GSM Global System for Mobile communication
GSM--R GSM--Railway
GUI Graphical User Interface
HMI Human Machine Interface
HO Handover
LAC Location Area Code
MA Mobile Allocation
MSC Mobile Switching Center
MSDE MicroSoft Database Engine
NE Network Element
NEL Network Element List
NRP Network Reconfiguration Procedure
ODB Operational Data Base of OMC--R (BDE in French)
OS Operating System
OMC--R Operation & Maintenance Center -- Radio Part
PC Personal Computer
PCM Pulse Code Modulation
PCU Packet Control Unit
PCU--OAM PCUSN Operation Administration and Maintenance
PCUSN PCU Support Node

SICD Serial Interface Controller LapD Protocol

SMS--CB Short Message Service Cell Broadcast
SQL Structured Query Language
TC Terrestrial Circuit
TCH Traffic Channel
TCU TransCoder Unit
TDMA Time Division Multiple Access
TEI Terminal Equipment Identification
TRX Transmitter/Receiver
TS Time Slot
Definitions
Alien cell Cell external to the network managed by the CT2000 tool. Such cells can be
cells from another equipment supplier or managed by another CT2000.
These cells are only known for neighboring definition of our cells.
Alternative An alternative is a database view, which represents a given view of the
managed BSS elements.
BSS A BSS consists of a set of OMC--R(s), its (their) connected BSC(s), TCU(s)
and BTS(s) and eventually its (their) PCUSN(s).
Carried Erlangs Erlangs on the Air Interface (Erlang B law) taking into account the SDCCH
and TCH blocking rates.
CAS command Component Administration System: Plug--in located on OMC--R WS and
file generator PCU OAM that takes PCUSN DRFs as an input and generates CAS
command files. Those CAS command files are a customer--supported
format. Two different types of CAS command files are generated: one type
deals with Hardware datafill aspects (HW) and the other one with
Engineering datafill aspects (SW).
CGI Cell Global Identifier = Set of 4 parameters that identifies a cell in a network:
MobileCountryCode, MobileNetworkCode, CellIdentifier, LocationAreaCode
CIQ Customer Input Questionary: Access--based tool that provides a GUI to
assist customers in providing to Nortel Networks mandatory information for
a PCUSN cabinet installation and/or datafill. This is a customer--supported
external format. This tool generates CIQ files.
CIQ files ASCII files that contain all the information entered by Nortel Networks
customers through the CIQ. Those files indeed contain all the PCUSN node
details (Hardware, Engineering, and commissioning information?) required
by both I&C and/or Engineering teams. Those files format are not
customer--supported. There is a set of CIQ files per PCUSN cabinet.
Congestion The whole capacity of a given resource is used. For example the congestion
on TCH in a cell is characterized by the time during which all configured
TCH in the cell are allocated.
Datum Correction according to the earth model for LAT/LONG coordinates
DB Decibel=10*log(Power1/Power2).
DBm 10*log(Power expressed in milliWatts).

411--9001--137
DRF ASCII files describing networks elements and their interfaces. These files
can be produced by any spread--sheet tool like Excel.
log window Sub--window of a main window in which information will be displayed during
an action execution.
NRP A NRP is a Network Reconfiguration Procedure eventually linked with a tool
(shell script running on the OMC--R) to execute a given configuration
change on an operational network.
Offered Erlangs Erlangs on the Air interface (Erlang B law) offered by the TRX without taking
into account the blocking rates.
Offered Erl = Carried Erl / (( 1 -- TCH blocking rate) * ( 1 -- SDCCH blocking
rate))
ODB object CT2000 object directly used by the DATAFILL function to generate OMC--R
command and NRP files or to retrieve an ODB. It is sometimes called Q3
object
ODS OMC--R Data Server, English acronym for SDO: Serveur de Donnes
OMC--R.
Orphan Network object the parent connectivity of which has not yet been allocated
RadioSite A radioSite is an OMC--R graphical object which is a set of btsSiteManager
belonging to the same BSC.
It could be used when you have drop and insert configurations.
This object has no relation to the CT3100 radio site.
Selection or A set of objects selected from a list, the browser, the network tree, the
current selection internal views

PAGE INTENTIONALLY LEFT BLANK

411--9001--137
Nortel Networks Confidential CT2000 general presentation 1--1
1 CT2000 GENERAL PRESENTATION
1.1 Product overview

The CT2000 is the Nortel Networks GSM/GPRS BSS configuration tool.
This product is part of a new generation of products, which are external applications
of the Nortel Networks OMC--R. The CT2000 offers a centralized configuration of
all Nortel Networks BSSs (multiple OMC--Rs) and a graphic representation of all
BSS network elements and links.
It also provides a centralized view of all BSS network parameters (frequency plans,
hand--over, power control and radio resource management).
The CT2000 is compliant with Nortel Networks BSS and telecommunication
systems:
GSM 850, GSM 900, GSM 1800, GSM 1900
GSM--R
GPRS
The position of the CT2000 in an operator network is illustrated in Figure 1--1.
1.2 Product definition

The CT2000 is a high--performance tool that will help you design and configure
(BSS datafill) a BSS network, based on GSM/GPRS recommendations.
The main objective of the CT2000 is to allow you to:
perform the initial configuration of a BSS network
extend and optimize the configuration of an existing BSS network.
To perform these operations, the CT2000 manages BSS data coming from various
sources (see Figure 1--2):
input data such as DRF Data Request Forms (BSS network parameters in ASCII
file format) issued by Customer BSS Network Design tools, and database import
coming from the OMC--R
output data such as formatted DRF, NRP (Network Reconfiguration Procedure)
files, and command files to be executed on the OMC--R.

1--2 CT2000 general presentation Nortel Networks Confidential
Customer
BSS
Design Cell planning Optimization Densification Network
Design
Tools
CT2000
Creation Modification Audit
OMC--R
BSS
Network
Figure 1--1 CT2000 position in an operator network

411--9001--137
Customer BSS Network

Design Tools
DRF files
CT2000
Network Configuration Tool
OMC--R PLUG--INS
CT--SDO NRP &

files Command files
OMC--R
Figure 1--2 Input/Output data of the CT2000 -- Functional view

1.3 CT2000 architecture
1.3.1 General architecture

The CT2000 is composed of two main parts (see Figure 1--3):
the PC--client engineering part
the OMC--implementation part
1.3.1.1 PC--client engineering part

This part is the off--line module developed on a desktop PC.
The aim of this part is to manage a database designed for core engineering:
load/export of files in DRF format, CT--Files format, datafill assistant, network
checks, equipment model management, template management, audit ...
Five functional levels are defined on the PC part to perform the CT2000 engineering
part:
Database level: to provide database services (database management, checks,
loaders, etc ...) based on the Microsoft MSDE software.
Core mechanism level: to provide configuration mechanisms (templates,
equipment models, session log, default values and datafill rules, etc ...).
Graphical network operation level: to provide network operation services
(network tree explorer, site creation, parenting management, internal views,
neighboring plan editor, etc ...).
Audit and report level: to provide audits on a full network or nodes and offer an
open access to the CT2000 database. The extracted information can be treated
with Microsoft Office facilities like Excel.
PCUSN datafill: to produce the PCUSN DRFs files needed for the
configuration and/or the datafill of a PCUSN. This is an external tool based on
Access software.
1.3.1.2 OMC--implementation part

For communication between the PC--part database and the OMC--R one, some
plug--ins have been developed.
The following plug--ins are accessible through an OMC--R DATAEXP workstation:
ODB retrieve
CT--SDO to CT--File conversion
NRP/CMD files generation
Class2 modification
A Interface management
The purpose of this part is to translate the operational needs of the network.2

411--9001--137
DRF files
English
OMC--R Unix station DATA EXP CT2000

server (OMC--R plug--in part) (PC part)
Load
DRF
Export
CT--SDO
CT
ODB ODB files
CT--SDO
to CT ftp Load
converter CT
CT--SDO
A--Interface files ODB
management (*) Export
plug--in CT--SDO ftp Export
CT--SDO
CMD files
and/or NRP DRF
NRP input filles files
input
files CMD/NRP English
Server Export
file
plug--in DRF
generation
CMD
files
CMD file Class 2

manager modification
Figure 1--3 CT2000 general architecture
Note: (*) For more details see Figure 1--9

1.3.2 Hardware platform

The CT2000 is a standalone tool running on a standard office PC computer (OS
Windows NT4.0 or Windows 2000).
Nortel Networks recommends the following hardware.
ITEMS CT2000 PC
Processor Pentium III 933MHz

SDram 512 Mb
Hard disk space 10 Gb
KEYBOARD INTERNATIONAL
CD--ROM drive yes
Floppy disk drive yes
Monitor 21 inch
The CT2000 application can be installed either on a Windows NT4.0 PC or a

Windows 2000 PC.
1.3.3 Software required using Windows NT4.0

Using a PC Windows NT4.0, the following softwares must be installed before the
CT2000 installation.
ITEMS CT2000 PC
OPERATING SYSTEM MICROSOFT WINDOWS NT 4.0 + SERVICE
PACK 6a (SP6A)
INTERNET EXPLORER 5.0
SOFTWARE SYSTEM MICROSOFT OFFICE PREMIUM 2000 SR1
(INCLUDING MICROSOFT ACCESS 2000
SR1, MICROSOFT WORD 2000 SR1,
MICROSOFT EXCEL 2000 SR1)
Note: The MICROSOFT MSDE software is delivered with the install shield.
Note: To ensure the execution of the automatic exchange with an OMC Solaris 8,
you must download a microsoft fix on WinNT from the following link:
http://support.microsoft.com/default.aspx?scid=KB;EN--US;Q24383
5&
1.3.4 Software required using Windows 2000

Using a PC Windows 2000, the following softwares must be installed before the
CT2000 installation.

411--9001--137
Note: If some other non--compatible application has been installed this process
may not work.
ITEMS CT2000 PC
OPERATING SYSTEM MICROSOFT WINDOWS 2000 +SERVICE
PACK 2 FOR WINDOWS 2000
INTERNET EXPLORER 5.0
SOFTWARE SYSTEM MICROSOFT OFFICE PREMIUM 2000 SR1
(INCLUDING MICROSOFT ACCESS 2000
SR1, MICROSOFT WORD 2000 SR1,
MICROSOFT EXCEL 2000 SR1)
Note: The MICROSOFT MSDE software is delivered with the install shield.
1.3.5 Example of CT2000 network architecture

Figure 1--4 shows an example of global network architecture for the CT2000.
A TCP/IP connection with the OMC--R is mandatory in order to emulate an OMC--R
session or to launch an OMC--R plug--in on the PC.

OMC--R SERVERS E4500
X Term Alarm relay

PCU OA&M
Alarm relay
Filtering
CT 2000 bridge
L
Plug--ins
A
OMC--R
N
Workstation A5200
Router
X.25 network
or switch
Terminal Server
BSS
Figure 1--4 CT2000 network architecture

411--9001--137
1.4 CT2000 functionalities

Network management is based on two notions: Network and Alternatives.
The diagam below represents object dependencies in the CT2000 PC application.
The following process is an example of the available ones.

CT 2000
Engineering datafill
Equipment model
rules
Network 1 Network 2
Mapping & Mapping &

Template Template
TDMA TDMA
OMC--R OMC--R
Alternative 1 Alternative 2 Alternative 1 Alternative 2
OMC OMC OMC OMC

objects objects objects objects
BSS BSS BSS BSS

objects objects objects objects
NEL NEL NEL NEL
Rules Rules Rules Rules
Figure 1--5 Example of CT2000 object dependencies

411--9001--137
1.4.1 Creation and management of workspace

The database contains as many Nortel Networks BSS networks as the user wants.
The only limitation is database size (see the following notes). Each BSS network
is identified by a network ID. For a given BSS network, users can create as many
alternatives as they require.
The number of alternatives is limited to 255. This is an MSDE limitation.
Note: The database size is limited to 2Gb (Microsoft MSDE limitation) and this
upper limit should not be reached in standard use of the tool. One cell needs
less than 10Kb, so 200K cells can be stored in the database (shared by all
networks and alternatives).
A given version of the same network is represented by an alternative which

represents the state of the network.
1.4.2 Template management

All template and model objects are specific to one CT2000 network workspace.
The following functions are linked to the templates:
assign a template to an object
propagate a template to a set of objects
propagate parameter modifications in a template to objects
import and export templates in an ASCII format
edit/delete/clone/modify templates through editors
In the case of a template modification, new values can be propagated to:
all ODB objects already created
a subset of objects
The only way of propagation is to apply the modification systematically.
The template editor allows you to browse through available templates relating to
a given object class. You can list all the available templates for a given object class.

1.4.3 TDMA frame and mapping model management

Time slot allocation within a given TDMA and TDMA allocation within a given cell
depend on the cell architecture (number of TRXs, mono or dual band, ...) and the
corresponding TDMA role within the cell (carried traffic, signaling). As a matter
of fact, different TS and TDMA dedications can be performed.
A given TDMA combination is called a mapping model.
Some default TDMA and Mapping models are delivered with the tool.
The CT2000 uses the TDMA and Mapping models editors to describe stored TDMA
and Mapping models. It enables you to create, delete and update them. It allows you
to list all the available TDMA and Mapping models.
Note: You cannot delete TDMA and Mapping models if they are still in use.
1.4.4 Network editor

This function allows you to update and visualize the default parameters. These
default values will be used for future creation of object for all networks and
alternatives.
1.4.5 Network element list

The Network Element List (NEL) is a list containing several Network Elements
(NE) selected by the user. A NEL can contain different classes of objects.
The user can:
create/delete/clone/edit an NEL
insert/remove an object or a selection of objects inside an NEL
1.4.6 Database DRF loader
1.4.6.1 DRF loader

This function is used to load DRF files in different modes:
Create Update, which includes the following basic modes:
create
parameter update
site reparenting
expand (add a cell or a TRX)
new neighboring plan (Create Update)
Create/Update/Remove the two following elements:
adjacent cell handover
adjacent cell reselection
Remove elements

411--9001--137
The CT2000 user has to indicate which mode to use when loading DRF files.
Not every mode is available for all DRF files and DRF files are managed by groups
as shown in the following table.
Create Update
DRF tables Create Update Remove
(new NEI plan)
OMC Y N Y
BSC TRANSCODER Y N Y
A INTERFACE Y N Y
PCU / PCUSN Y N Y
SITE Y N Y
CELL/TRX/TDMA Y N Y
HANDOVER Y N Y
POWER CONTROL Y N Y
TRANSCEIVERZONE y N Y
NEIGHBORE CELL Y Y Y
GEOGRAPHICAL Y N Y
COORDINATES
Table 1--1 DRF Files and modes
1.4.6.2 CT--File loader
The OMC--R(s) operational network is loaded into the CT2000 database, this
operation can be done after the configuration data has been extracted from the
OMC--R and converted into CT--Files.
This loader is optimized for a network creation. The CT--File format is a Nortel
Networks proprietary one.
During Sdo2CT process, there are several types of files generated in directory
/home/users/data/ExportCT on the station with DATAEXP role. These are:
CTFILESwhich is the format of files which allow you to load the OMC--R
database on the CT2000 PC Part.
CTFileInfo.ctd (CTFILE info descriptor)it contains the list of CTFILES
generated by the conversion.

LOG.log (log file of Sdo2CT)This allows the user to know if

TDMAMODEL.tmm and MAPPINGMODEL.map files have been generated in
addition to CTFILES. This file also contains some unknown Equipment Models
on the OMC--R Database.
MAPPINGMODEL.map and TDMAMODEL.tmmthese files are generated
only if on OMC--R database, some customer sites are using MAPPINGMODEL
and TDMAMODEL different from the default reference one. Reference files can
be found in /CMN/base/plugins/Sdo2CT/DrfInputModel/ directory. These files
have to be retrieved on the PC PART and to be loaded as Template/Import to
ensure coherency of the CT2000 PC Database.
Once produced, these files are loaded from OMC--R to the CT2000 PC using FTP.
Since the files, MAPPINGMODEL.map and TDMAMODEL.tmm contain
information about models missing in default templates, these files need to be
imported (interfaces--templates--import (select the two model files)) before
performing CT files import. Failure to do so will result in cells having a Mapping
Model nonexistent in the database and exportCTSDO will have difficulty to map
the channel type.
1.4.7 Graphic network tree viewer

The network tree viewer provides the following graphic views:
BSS Object Tree Explorer which displays the hierarchical architecture of the
BSS network.
Topological Network Tree Explorer which displays the topological
architecture of the network.
1.4.8 BSS object editor

The Object Editor allows the user to consult BSS object instances and to modify all
attributes of each BSS object instance.
1.4.9 Neighboring editor

The neighboring editor provides functionalities to create, modify and correct the
neighboring plan easily.
The neighboring editor allows you to:
display the neighboring plan of any serving cell
create and delete a neighboring link
display errors from the checker with graphical color codes
create an NEL including all the NEs of all listed serving cells

411--9001--137
1.4.10 Database network checker

Parameter checks generate reports in ASCII files. The checks can be set by groups.
The user can specify his own checks and families of check. The Network Checker
detects errors and can apply an auto--correction for some checks. Those corrections
are based on engineering rules.
All the OMC--R checks are provided by the CT2000:
ODB group check tests if the data included in the database are correct according
to release requirements (existing parameter or not, type, range, ...).
Dimensioning group check tests the maximum number of sub--objects per
object, according to the static constants defined in the OMC.
The CT2000 provides specific checks:
Neighboring group check is dedicated to neighboring issues detection.
Engineering group check tests if mandatory or recommended engineering rules
are respected. An error is raised when a mandatory rules is not respected and a
warning when a recommended rules is not respected.
Completeness group check tests if nodes, interfaces and their inter--connections
are consistent all together. This group includes all the checks that are related to
the network topology.
Listing group check tests the list of objects (neighboring size lists all the cell(s)
having a number of adjacent declared to be out of a chosen range).
Template group check tests that the attribute values of the object are equal to the
templates ones (for example template field comparison).
Models check tests that the attribute values of the object are equal to the models.
GSM--R group check tests the presence of ASCII mode parameters
(VoiceGroupCallService, VoiceBroadcastService, PreemptionAuthor,
emlppThreshold, NCHPosition attribute).
PCUSN group check tests PCUSN engineering parameters, such as the range
values, type constraints imposed and engineering rules.
Parenting group checks if an element of an upper level in the hierarchy exists as
well. All elements except for the site need to have an upper level element
existing. The site can be loaded without a BSC existing in order to allow orphan
sites to be loaded.
1.4.11 Data base export
1.4.11.1 Through DRF
The DRF export is used to extract DRF tables from:

a full network/alternative
a current selection
an NEL in a given network/alternative
Users can select the directory where the extracted tables are stored.
These files can be updated by the user.
This function also allows you to export ENGLISH DRF files.
1.4.11.2 Through CT--SDO
The export CT--SDO deals with the extraction of configuration data of the CT2000
database in the CT--SDO format. These files are used as input to the CMD/NRP file
generation plug--in.
1.4.12 Generation of command files

The CT2000 OMC--R plug--in implementation part allows you to generate OMC--R
command files or NRP input files.
OMC--R command files
These command files allow you to create an OMC--R database, and modify OMC--R
parameters.
Delta command files can be generated for new objects in an existing network.
NRP input files
These input files are generated for modification of parameters in an operational

network:
TEI reparenting
BTS reparenting
Concentric cell activation
Frequency Plan Change
Synthetized frequency hopping Activation
Frequency hopping Activation
Location Area Code reconfiguration
The user can also generate command files by delta. This generation compares
CT--SDO data from the OMC database with data from the CT2000 database.
The CT--SDO files are generated directly from the ODB via an export CT--SDO.

411--9001--137
The user can generate some or all NRP input files.

Generated NRPs input files and command files are stored in a specific directory.

1.5 CT2000 interfaces

The CT2000 consists of a standalone PC application which interacts with its
dedicated plug--ins at the OMC--R level. This couple uses ASCII files to exchange
configuration data between each other, with OMC--Rs and any other engineering
tool. The CT2000 provides the following interfaces:
CT2000 engineering interface
CT2000 to OMC--R interfaces
CT2000 PC to GPRS Passport provisioning tool plug--in
CT2000 PC to CT2000 OMC--R plug--ins
1.5.1 CT2000 engineering interface

An ASCII interface (DRF) ensures compatibility with other Nortel Networks tools
(CT3100 and CT5100) and customer engineering tools (cell planning, topology...)
(see the following figure).

411--9001--137
CT3100 CT5100
RF & Cell Network

Optimization Planning &
Tool Optimization
Site definition BSS topology

RF parameters LAC definition
CT2000
Network Configuration
Tool
ASCII Download
Datafill Get
Reports configuration
configuration
OMC--R
Customer BSS Network
Design Tools
Figure 1--6 CT2000 Interfaces

1.5.1.1 Data Request Forms
DRFs are ASCII files that contain the different information items (Object
identifiers, Network Topology and OMC--R parameters) required by the CT2000
to create OMC--R BSS objects.
There are different DRF tables, each one corresponding to a specific OMC--R BSS
logical object (or group of OMC--R BSS logical objects). Table 1--2 lists the file
extension and corresponding OMC--R BSS object for each of the DRF tables.
DRF tables Extension OMC--R BSS objects
A INTERFACE .ain signallingPoint, signallingLinkSet,

signallingLink, pcmCircuit
BSC .bsc bsc, bscMdInterface, coo
CELL .cel cell
HANDOVER .hov handovercontrol
NEIGHBOUR .nei adjacentCellHandOver,

CELL adjacentCellReselection
adjacentCellHandOverAndReselection
OMC .omc omc
PCU .pcu pcu
PCUSN .psn pcusn
PWC .pwc powercontrol
SITE .sit Site, coo, pcmCircuitAbis, lapdLink
TRANSCODER .tcu transcoder, transcoderBoard, pcmCircuitA,

pcmCircuitAter, lapdLink
TDMA .tdm channel, transceiver,

frequencyHoppingSystem
TRX .trx lapdLink, transceiverEquipment
TSZ .tsz transceiverZone
GEOGRAPHICAL .coo coo

COORDINATES
Table 1--2 File extensions for BSS DRF tables

411--9001--137
Description of DRFs
A DRF is an ASCII file made up of several fields separated by the TAB character
and presented in table form. These fields contain the minimum information
necessary to create the OMC--R BSS objects of your network automatically.
Any DRF file is made of two sections:
a header section (always the first line of the file) describing the parameters
present in the DRF file.
a data section containing the configuration values.
DRFs are structured as follows:
identification: First fields contain parameters used to identify objects (for
instance bscId, bscName, cellName...).
specific parameters: Other fields contain either OMC--R BSS parameters or
CT2000 parameters.
generic parameters: Fields following the Template xxx field contain
parameters defined in the reference template.
You will find a complete description of the different DRF tables in NTP 148.
The CT2000 allows you to import datafill values from DRFs and to export datafill
values in DRF format.
The CT2000 also allows you to import/export templates by ASCII files.
1.5.1.2 Templates
The templates are frames for object construction. When you are building a new
network object, using a template enables you to have to set consistent values for all
the parameters.
Templates are used to define common parameters (parameters whose values can
be applied to several OMC--R BSS objects of the same type). These parameters are
mainly optimization parameters.
Templates relative to the same OMC--R BSS object are used by load DRFs so that
when loading the DRF, some of the object parameters will be filled in automatically
with the values defined in the Template.
There are different template types, each one corresponding to a specific OMC--R
BSS object or group of OMC--R BSS objects and then to a particular DRF. You can
find default templates with values set by Nortel, which are loaded into the CT2000
database.
You cannot delete these templates but you can create your own templates with
values matching your requirements. If you decide to create customized templates
out of the CT2000 (using a speadsheet program for instance), you will be required
to load them into the CT2000 database before using them.

If you decide to use templates other than the default ones proposed by Nortel
Networks, you have to set their names in the Network Table.
If you decide to create your own templates out of the CT2000 (with a spreadsheet
program for instance) you must give them one of the extensions described in
Table 1--3. These extensions allow the CT2000 to identify the objects it is dealing
with, while loading.
The following table gives, for each template:

the file extension
the template class

the OMC--R objects
Extension Template class OMC--R BSS objects
signallingLinkSet, signallingPoint,
.tai A Interface
pcmCircuit
.tbs BSC bsc, bscMdInterface
.tce CELL bts
.tho HOV handoverControl
adjacentCellHandover,
.tne NEI adjacentCellReselectionadjacentCell
HandOverAndReselection
.tom OMC --
.tpc PCU --
.tps PCUSN --
.tpw PWC powerControl
.tsi SITE Site, coo, pcmCircuitAbis, lapdLink
transcoder, transcoderBoard,
.ttc TCU pcmCircuitA, pcmCircuitAter, xtp,
lapdLink
channel, transceiver,
.ttd TDMA
frequencyHoppingSystem
.ttr TRX lapdLink, transceiverEquipment
.tts TSZ transceiverZone
Table 1--3 File extensions for templates

411--9001--137
Mapping Models
Two templates have been added for the Mapping models, described in the following
table.
Extension Template class
.tmm tdmamodels
.map mappingmodels
Table 1--4 File extensions for mapping/TDMA models
1.5.1.3 Models
Models contain information defining BSC and site equipment for hardware
(capacity, number of links, hardware reference) and software domains.
They provide different levels of information:
Logical level: The logical model describes an equipment in terms of the
functionalities it may have. For example, an S3444 BTS model is described as
3 cabinets with 4 TRXs per cell. Logical functions are implemented in the
database using ODB objects. Associating an equipment with a model will
automatically copy the model substructure into the equipment.
Equipment level: The equipment model describes the physical aspect of the
equipment in terms of hardware/software references and factory parameters.
Variables may be used to define hardware/software references.
1.5.2 CT2000 to OMC-- R interface

The CT2000 interfaces with the OMC--R by a Nortel Networks proprietary
CT--SDO format.
1.5.2.1 CT2000 to OMC--R interface

In order to implement at OMC--R level the modification designed at CT2000 level,
a plug--in generates either Command files or NRP input files depending on the
operation to be performed. NRP input files are indeed necessary to perform some
specific datafill operations.
1.5.2.2 OMC--R to CT2000 interface

The CT2000 can fully extract an operational database from the OMC--R using the
DATAEXP mechanism installed on a dedicated OMC--R workstation. Extracted
data are then processed by the CT2000 plug--ins and PC part to fully or partially
retrieve the view of the BSS network. The extraction is performed so as not to
disturb OMC--R real--time operations.

1.5.3 CT2000 PC to GPRS Passport provisioning tool plug-- in

This plug--in allows the exchange between the CT2000 engineering part and the
GPRS Passport provisioning tool using the PCUSN Component Administration
System (CAS) command files (see Figure 1--7).
Users can generate GPRS DRFs from the Customer Input Questionary (CIQ) or
another customer tool. These DRF files allow you to implement and modify the
PCUSN hardware and software configuration of an existing network.
The GPRS Passport provisioning tool is also accessible through the OMC--R
workstation MMI. The following table illustrates the file extension for the PCUSN
DRF tables.
DRF tables Extension GPRS objects
Gb Interface hardware .egb BSC connection (Gb interface)
PCU .epc BSC connection to a PCUSN (Agprs and Gb

interface)
Agprs .agi BSS connections
Gb interface .gbi Gb interface (Frame Relay inter--connection)

engineering
CARDS .crd Cards inside a PCUSN node
PCUSN .hps PCUSN
USERS .usr PCUSN nodes (users)
Table 1--5 File extension for PCUSN DRF tables

411--9001--137
CIQ
PCUSN OMC--R
DRFs Work Station
Plug_in
PCUSN
CT2000
Generation
PC Part CAS Cmds
Cross--Checks
Checks
Engineering
rules CT2000 OMC--R
CT--SDO files
OMC Part
Cmds
Models
Templates
Generation
Conversion
Compare
CT--files Conversion
GPRS
OMC
DRFs
Figure 1--7 CT2000--GPRS interface

1.5.4 CT2000 to CT2000 OMC-- R plug-- ins
1.5.4.1 CT2000 PC to CT2000 OMC--R plug--in
The CT2000 engineering part (installed on a PC) interfaces with the CT2000
implementation part (installed as a plug--in at the OMC--R workstation level)
through Nortel Networks proprietary DATAEXP format.
For creations, changes or extensions of an existing network, the CT2000
engineering part can partially or fully download the configuration changes to the
impacted OMC--R through their CT2000 plug--ins.
1.5.4.2 CT2000 OMC--R plug--in to CT2000 PC
The CT2000 implementation part (installed as a plug--in at OMC--R workstation

level) interfaces with the CT2000 engineering part (installed on a PC) through
DRFs.
For changes or extensions of an existing network, the CT2000 engineering part can
partially or fully upload the configuration from the plug--in.
In both cases the OMC--R extraction mechanism exports the full OMC--R
configuration on each of the connected OMC--Rs.
Nevertheless you can post--process data on an OMC--R, either at the CT2000
plug--in level or at the CT2000 PC level, and at the BSC level.

411--9001--137
1.6 OMC--R plug--ins

To provide the communication services between the PC--client engineering part and
the OMC--R, some plug--ins are implemented in the OMC--R workstation
CT2000 PC platform OMC--R platform

Engineering part Implementation part
Files OMC--R OMC--R

Station Server
Plug--in DATA EXP Plug--in
CMD &
NRP Files
CT2000 CT--SDO CT--SDO Delta Directory
Modules files format files Generator
generator Plug--in Class2
module Modif.
Plug--in
DRF ODB
files MS SQL DRF files
Server
Real Time
(MSDE)
Database
CT--SDO SDO
DRF tables ODB LIGHT
Load CT to CT files
Templates retriever
module converter
Eg. models Plug--in
module MMI
A Inter- CMD,
face DATA &
Mana-- LOG
gement Files
Plug--In Directory
Figure 1--8 OMC--R plug--in interface

1.6.1 ODB retrieve plug--in

This plug--in extracts the OMC--R ODB in a CT--SDO file using the SDO light
module and retrieves any extra configuration not included in the CT--SDO files but
required by the CT2000. The OMC--R configuration is retrieved in CT--File.
The CT--SDO--to--CT--File converter extracts data directly from the OMC--R before
converting them. CT--Files resulting from the conversion can be extracted for full
OMC--R.
1.6.2 NRP/Command File generation plug-- in

The targeted configuration changes are represented in CT--SDO files downloaded
by the CT2000 engineering part.
It generates suitable OMC--R NRP inputs and/or Command files which correspond
to the configuration changes provided by the CT2000 engineering part and which
have to be implemented on the network.
Before running generation you can modify all the default directories, select only
NRP/Command File or both. You can also select the generation to be done from an
existing OMC--R configuration extraction or select the plug--in to request a new
extraction.
Generated NRP input files, command files and their reverse files are stored in a
specific directory on the corresponding OMC--R(s) server(s).
During generation, a log window indicates that the process is running, describes
processed actions and displays potential errors or warnings. If a fatal error occurs
during comparison, the plug--in stops and error messages are displayed in the log
window.
This plug--in is only accessible at the OMC--R workstation level.
1.6.3 Class 2 modification plug--in

This plug--in generates command files to modify a class 2 parameter and to manage
the administrative state of impacted objects.
1.6.3.1 Parameter classes
Each OMC--R attribute belongs to one of the following classes only:

Class 0: used for object classes, a change means that the object has to be deleted
and then recreated.
Class 1: a build of the BSC BDA must be performed after any modification in
order for changes to take effects.

411--9001--137
Class 2: the modification must be done after putting an object or an associated

object Out of service.
Class 3: the modification can be done on line.
1.6.3.2 Class 2 modification plug--in
The CT2000 class2 generation plugin takes into account the current administrative
state of one or several objects. This plugin can be used after the generation of
CmdFiles in delta mode where some set2 commands can be found (presence of a
global.set2 file in the CmdFile directory).
The plug--in has two operating modes:
Simulation only: It is an off line mode. The plugin considers that all objects are in
service and commands of locked/unlocked will be executed according to this
rule.
Later Execution: the plugin interrogates the OMC--R database to get the current
administrative states. A new Result File is generated containing the relevant
locked/unlocked commands. Command files are not executed.
A log window indicates that a process is running, describes processed actions and
impacted objects, and displays potential errors and warnings.
This plug--in is only accessible at the OMC--R workstation level.

1.6.4 A Interface management plug--in

The purpose of this plug--in is to manage the process of the A Interface offline
configuration.
This plug--in is used to:
provide a graphical, user--friendly view of TS (and their parameters) of all the
PCM A links under selected BSC
export the parameters of all the TSs under selected BSC to data file and import
from data file
calculate the ideal CIC--to--XTP mapping according to the one of two possible
rules and check--up the current CIC--to--XTP mapping vs the ideal one
generate a set of MMI command files, which can be used in order to apply the
changed CIC--to--XTP mapping or to rollback the changes
export data files and generate MMI command files automatically for the whole
OMC or the selected part
manually reserve the timeslots on A Interface for X.25 protocol
The operator using the A interface management plug--in in order to configure PCM
A links and corresponding TS, has to perform the usual following sequence of
actions (see the following figure):
Load the TS data from the ODB (BDE) into the view or import the TS data from
the data file
Export the TS data to the data file in order to be able to restore the saved
configuration
Check--up the loaded data by means of check--up feature
Recalculation of CIC--to--XTP mapping, if the current mapping differs from the
ideal one or if the current TS allocation does not correspond to some A Interface
engineering rules
Generate MMI command files, which can be executed by one of existent MMI
tools in order to apply (or revert) the changed CIC--to--XTP mapping into the
ODB (BDE)

411--9001--137
Figure 1--9 A Interface management plug--in
1.6.4.1 GUI views
The GUI views provide a user with global graphical representation of E1/T1 PCM
A links and corresponding TS. The view also visualizes differences between the
current CIC--to--XTP mapping and the ideal one, and indicates violations of A
Interface engineering rules.
The views consist of the TS allocation table with one line per one PCM A link and
one column per one TS number. All the PCM A links are grouped by TCU. Each
element of the TS allocation table contains a label and can be highlighted by a color.
There are two types of views:
View by categories: All the TS are labeled and highlighted according to their use
(by default: ss7 for signaling, x25 for X25 packet data, xtp for voice, nu for not
used TS and tfc for TS which are free for traffic).

View by identifiers: Only xtp TS are labeled and highlighted by their xtpId and
cic numbers. Empty fields label other TS.
The TS colors provide an information about the differences between the real
CIC--to--XTP mapping and the ideal one and violations of A Interface engineering
rules. The labels of categories and colors of TS are configurable by means of the
configuration file.
1.6.4.2 Data files

Data files are tab--separated ASCII text files of the predefined format. They
represent the TS allocation and configuration information. Each data file contains
the configuration information of all the TS under a BSC. This information directly
corresponds to the one, which can be retrieved by direct access to the ODB.
The default directory, where all the data files are placed into, is specified in the
configuration file. By default, the names of the data files are as follows (<datetime>
means date and time of the creation):
omc<omcName>_pcm<pcmKind>_bsc<bscId>_<datetime>.dat
A data file consists of:
Header of the file, which contains the version number, OMC name, PCM type,
BSC name and BSC identifier
Header of the table, which contains tab--separated column names
Table of TS configuration data. Each line of this table represents the
configuration and allocation information of one TS of one PCM A link of one
TCU under a BSC
Note: For more details, refer to Paragraph E3 of the NTP 148.
1.6.4.3 Retrieving the data

The TS configuration data is retrieved as an output of direct SQL commands to the
ODB or by means of the import feature.
When the TS configuration information is absent in the ODB (for example, if TS
allocation has not been configured yet, but bsc, transcoder and related objects have
been created), A Interface Management plug--in loads (depending on the real
situation) nothing into the view or denotes all the timeslots as free for traffic (tfc).
1.6.4.4 Import of data files

This feature is used to read the previously saved TS configuration from the
particular data file. The format of the data file is strongly checked.
Note: An import feature allows to load the TS configuration of any BSC, even if
this BSC does not exist in the ODB. But in this case, there is a restriction about the
MMI command files generation.

411--9001--137
1.6.4.5 Export of data files
This feature is used to save the current (loaded into the view) configuration of TS
to the particular data file.
Note: There are no restrictions to export the TS configuration. The TS
configuration can be exported even if it is empty.
1.6.4.6 Check--up of CIC--TO--XTP mapping
When automatic check--up of the current CIC--to--XTP mapping is switched on, all
the TS having non--ideal mapping are highlighted with the corresponding color. All
the TS that violate some A Interface engineering rules are highlighted too. So, an
operator is able to see the differences and estimate if the current CIC--to--XTP
mapping and TS configuration need to be changed.
1.6.4.7 Recalculation of CIC--TO--XTP mapping
A user is able to recalculate current CIC--to--XTP mapping, change it to the ideal

one and eliminate all the A Interface engineering rules violations.
Note: The recalculation of CIC--to--XTP mapping does not directly affect the
ODB (BDE). The real creation and deletion of the objects is performed by
executing the generated MMI command files.
1.6.4.8 Generation of command files
This feature is used to generate a set of MMI command files which allow to perform
the BDE modifications after TS configuration (including CIC--to--XTP mapping)
is changed. This set consists of 12 files, 4 files for the direct change procedure, 4
files for the rollback procedure and 4 common files, whose destination is to
consequently execute the files for direct change and rollback procedures (direct
change and rollback control files). All the files can be executed by MMI Command
File Manager or other MMI tools (For more details, refer to Paragraph E4 of the
NTP 148)
1.6.4.9 Generation of Log files
This feature is used to generate the Log file which is the text file, and which contains
information about the plug--in execution, descriptions of errors having occurred etc.
1.6.4.10 Automatic export of configuration data
This feature allows to perform an automatic export of configuration data from the
ODB to a set of data files with predefined names.

1.6.4.11 Automatic generation of command files
This feature allows to generate an automatic MMI command files. For this
operation, the plug--in imports the data from the data files and then generates a set
of MMI command files according to the imported and real--stored in the BDE data.

411--9001--137
1.7 CT2000 administration

In the Administration mode, users can perform the following non--engineering utili-
ties necessary to configure and maintain the CT2000 product:
installation, setup, and restart
All the database administration capabilities of Microsoft MSDE can be used with
the administrator user access level.
Administrators can access all the configuration features and some of the features
that are specific to database administration:
Full access to database objects
Database management (backup/restore)
A patch administration manager available on the CT2000 provides the following
facilities:
patch list view with patch name, patch kind, patch date
patch loading
software saving with new patches


411--9001--137
Nortel Networks Confidential CT2000 basics 2--1
2 CT2000 BASICS
2.1 Introduction
This chapter explains how to install, start, quit and uninstall the CT2000 V2.0
application.
2.2 Installation
2.2.1 Operating System

The CT2000 requires Microsoft Windows NT 4.0 or Microsoft Windows 2000. If
the check on OS existence fails, the application will not be installed.
2.2.2 Software required using Windows NT4.0

For details about software required with Windows NT 4.0, see paragraph 1.3.3.
For the installation of the NT Service Pack 6a refer to the Microsoft Documentation.
2.2.3 Software required using Windows 2000

For details about software required with Windows 2000, see paragraph 1.3.4.
For the installation of the Service Pack 2 refer to the Microsoft Documentation.
2.2.4 User privilege requirement

The user who installs the Nortel Networks CT2000 products must be declared in the
group of local administrators of the PC. This is a mandatory condition in order to
perform a successful installation.
2.2.5 Warning about renaming PC or modifying network domain

Once the CT2000 application is installed, take care to never rename the PC or
modify the network domain.
If such a modification must be applied, the user must:
uninstall the CT2000,
uninstall MSDE
modify the PC name or network domain
reinstall MSDE
reinstall the CT2000.

2--2 CT2000 basics Nortel Networks Confidential
Procedure 2--1
Installing the CT2000 using Windows NT4.0
This procedure describes how to install the CT2000 tool for the first time in your PC.
Note: The user must be logged on as administrator to perform the CT2000 installation.
The first step of the installation procedure consists of the MSDE installation (if not already
present on the PC). The presence or not of MSDE is detected by the INSTALL SHIELD.
If present, the installation directly begins with the CT2000 installation.
Note: The installation of the MSDE database requires the user to enter a path for the
location of the database. The path (whithout spaces and containing only
numerical or alphabetical characters) must end with /Mssql7. Example of path:
D:/CT2000/Mssql7.
Step Action
1 Insert the CT2000 CD--ROM.
2 Double click on the Setup.exe file located in the INSTALL SHIELD directory. The
following dialog box opens.
Click on the button. The following screen will ask you where you want
to install CT2000, to have no problem the selected disk must have at least two
gigabytes of free space. After setting the right disk (avoid sytem disk C:\) if there
are no many spaced on this disk.

411--9001--137
Step Action (Continued)
At the end of this first part of the installation, the installer will inform the user that
it needs to reboot. The installation of the database engine MSDE is finished.
3 When the reboot is finished, double click on the Setup.exe file located in the
INSTALL SHIELD directory. The following dialog box opens.
4 Click on the button.
The following dialog box opens.

5 In the Destination Folder area, click on the button if you want to

change the predefined destination folder.

411--9001--137
In the Path area, enter the new path destination directory (for example: D:\Program
Files\Nortel Networks\CT2000).
6 Click on the button to validate you choice.
The user returns to the updated CT2000 Setup dialog box (see the following figure).

7 Click on the button. The following dialog box opens.

411--9001--137
8 Choose directories wher you want to add icons.
11 At the end of the process, restart the computer.

Procedure 2--2
Installing the CT2000 using Windows 2000 preliminary: Modifying
the local security policies
Before installing the CT2000, the Local Policy Settings of Windows 2000 have to be
modified.
1 Open the local Policy Security Tool, available in the start menu at the following
place: Start program/Administratives Tools/ Local security Policy.
2 Open the Password Policy folder (Path: Local Security Settings\Account

Policies\Password Policy)

411--9001--137
3 Set the policy in the following manner: Minimum password to 0 days, Minimum
password lenght to 0.
4 Set Password must meet complexity requirements to disabled.

5 In Security Settings/Local Policies/User Rights Assignement, log on locally to
PcName\Guest, Users, Power Users, Backup Operator, Administrators.

Note: The followings steps have to be applied only in the case where Nortel Networks
applications have already been installed on the PC.
6 Access to the registry editor: In the start menu Windows select Run.... Item. In the
next Window type regedt32 to launch the editor for registry.
Note: If you are unable to access to this tool see the user manual of Windows
2000 to get the procedure allowing the access to this tool.
Note: In case of unavailability of this tool contact your local Windows 2000
support.
7 Select HKEY_LOCAL_MACHINE on Local Machine Windows.
8 Open the following path in the tree

HKEY_LOCAL_MACHINE/SOFTWARE/NortelNetworks.
9 Select Nortel Networks item in the tree and select permission item in the Security
menu.
10 Check that the user everyone is present and is allowed to read and to have full
control on the registry key and sub keys.
11 Check that for this user everyone, the check box: Allow inheritable permissions
from parent to propagate to this object. is checked.

411--9001--137
Procedure 2--3
Installing the CT2000 using Windows 2000 preliminary: Modifying
Windows 2000 user profile security
This procedure describes how to modify the user profile security so that shortcuts may be
installed on the deskstop and in the startup menu.
1 Locate the directory where user profile are stored on your PC (in a standard
configuration in C:\ Documents and setting folders).
2 Verify that the administrators group has full control on this directory and all sub
directories.

3 Shutdown the PC.
4 Unplug the network cable (the cable must stay unplugged till the end of the
installation).
5 Restart the PC. The Windows 2000 configuration has been modified so that the
CT2000 installation is possible.

411--9001--137
Procedure 2--4
Installing the CT2000 using Windows 2000
This procedure describes how to install the CT2000 tool for the first time in your PC
Windows 2000.
Note: The user must be declared in the group of local administrator of the PC Windows
2000 to perform the CT2000 installation.
The first step of the installation procedure consists of the MSDE installation (if not already
present on the PC). The presence or not of MSDE is detected by the INSTALL SHIELD.
If present, the installation directly begins with the CT2000 installation.
Note: The installation of the MSDE database requires the user to enter a path for the
location of the database. The path (without spaces and containing only
numerical or alphabetical characters) must end with /Mssql7. Example of path:
D:/CT2000/Mssql7.
Prerequisites
The configuration of Windows 2000 has been modified to allow the CT2000 installation.
The PC is unplugged from the network.
Step Action
1 Insert the CT2000 CD--ROM.
2 Double click on the Setup.exe file located in the INSTALL SHIELD directory. The
following dialog box opens.

Click on the button. The following screen will ask you where you want
to install CT2000, to have no problem the selected disk must have at least two
gigabytes of free space. After setting the right disk (avoid sytem disk C:\) if there
are no many spaced on this disk.
At the end of this first part of the installation, the installer will inform the user that
it needs to reboot. The installation of the database engine MSDE is finished.
3 When the reboot is finished, double click on the Setup.exe file located in the
INSTALL SHIELD directory. The following dialog box opens.

411--9001--137

5 In the Destination Folder area, click on the button if you want to

change the predefined destination folder.

411--9001--137
In the Path area, enter the new path destination directory. The selected disk must
have 2 gigabyte free (for example: D:\Program Files\Nortel Networks\CT2000).
6 Click on the button to validate you choice. The following dialog box
open.
The user returns to the updated CT2000 Setup dialog box (see the following figure).

7 Click on the button. The following windows opens.

411--9001--137
8 Click on the button. The following windows opens.

9 Choose directories where you want to add icons.
12 Click on the button. The PC reboots.
13 At the end of the process, restart the computer.
14 Log on the PC using the same user.
15 Restart the PC. The CT2000 is installed and ready to be used.
16 Plug the network cable

411--9001--137
Procedure 2--5
Creating Shorcut in Startup Menu
During the installation of the CT2000 an error can occur on file Generic shorcut.vbs, if your
Windows configuration doesnt allow the installation of desktop or startup shorcut. In this
case you have to create manually shortcuts.
This procedure describes how to create shorcut.
1 Locate the profile directory normally on C:\Documents and Setting folder.
2 Open the All Users/StartMenu/Programs folder.
3 In this directory create a folder named Nortel Networks and in this folder a folder
named CT2000.
4 In this folder repeat the following procedure for all CT 2000 application (Admin, CIQ,
CIQviewer, CT2000, DRFCompare, PCU).
Right click with the mouse inside the folder and select item new....shorcut.
Type in the location of the item:
PathToYourCT2000InstallationFolder\Bin\CT2000_GSM.exe for CT2000
as exemple.
In the next window type the name of the shorcut: CT2000.

The short cut is created, right click on the shorcut, select properties and tab
shorcut in properties Windows.

Click Change Icon and type pathToCT2000InstallationFolderShortcut.ico,

click OK, select the globemark icon and close the properties Windows.
The next table give the name of the binaries, of shorcut and the name of the icon
file.
Binaries name Shortcut Name Icon file Name
BIN\CT2000_GSM.exe CT2000 BIN\Nortel\Shorcut.ico
BIN\AdmTool.exe Admin BIN\NortelShortcut.ico
DRFCompare\DRF.exe DRFCompare No Icon File
PCU--CIQ\CIQ.mde CIQ No Icon File
PCU--CIQ\CIQViewer.mde CIQViewer No Icon File
PCU--CIQ\PCU PCU No Icon File

411--9001--137
Procedure 2--6
Starting the CT2000
This procedure describes how to:
start the CT2000
select a network and an alternative
Step Action
1 There are two different ways to start the CT2000.
a. Select
--> -->
--> --> .
b. or click twice on a shortcut you have created on your Desktop, to access to the
CT2000 application.
The following CT2000 Main window opens.
Figure 2--1 CT2000 Main Window

2 In the Network Name list, select a network or refer to NTP 148 for a network
creation.
3 In the Alternative Name list, select an alternative or refer to NTP 148 for an
alternative creation.

411--9001--137
Procedure 2--7
Loading the Default Templates
Once the CT2000 has been installed, the Default Templates must be loaded. This
procedure describes how to load default templates just after CT2000 installation.
Step Action
1 Open the Import Template window (refer to NTP 148).
2 In the Import Template window, select the partition disk ( for example c: ) where the
CT2000 application has been installed, then the folder containing Default
Templates (path: C:\Program Files\ Nortels Networks\CT2000\Default Templates)
3 Load the Default Templates Files (refer to NTP 148).

Procedure 2--8
Quitting the CT2000
This procedure desribes how to quit the CT2000.
Before applying this procedure, you have to wait the completion of the current operation.
Step Action
1 There are two different ways to quit the CT2000.
a. In the Menu Bar, select: Preferences --> Quit.
b. Click on the icon (located in the top right--hand corner) of the CT2000 title
bar.
Note: Make sure that the CT2000 is really closed.

411--9001--137
Procedure 2--9
Uninstalling the CT2000
This procedure desribes how to uninstall the CT2000.
Prerequisites
The user must be administrator for realize the de--install procedure.
Make sure that the CT2000 application is really closed.
Step Action
1 Stop the MSSQLServer.

2 Click right on the SQL server icon found on the right of the Windows task bar.

The following updated dialog box appears.

6 Close this dialog box.

411--9001--137
7 Click twice on the Setup.exe file located in the INSTALL SHIELD directory.
At the end of the previous process, the following dialog box opens.

9 If not used by an another application uninstall MSDE (see Microsoft

Documentation).
10 restart the computer

411--9001--137
Nortel Networks Confidential CT2000 PC--Part Main Human Machine Interface 3--1
3 CT2000 PC--PART MAIN HUMAN MACHINE

INTERFACE
This chapter explains how to use the CT2000 menus and commands. It also
describes how to use the CT2000 editors.
3.1 CT2000 Main Window

When you open a CT2000 session, the first window called CT2000 opens.
The following figure illustrates an example of the CT2000 window.
Figure 3--1 CT2000 Main window
From the CT2000 Main window (see the previous figure), you can run the different
commands. You also get different views of the OMC--R BSS objects in your
network.

3--2 CT2000 PC--Part Main Human Machine Interface Nortel Networks Confidential
The CT2000 Main window consists of the following fields:

the title bar (see the following paragraph)
the menu bar (see Paragraph 3.1.2)
the toolbar (see Paragraph 3.1.3)
the workspace (see Paragraph 3.1.6)
the status bar (see Paragraph 3.1.8)
3.1.1 Title bar

The Title bar indicates the title of the application.
In the CT2000 Main window this title is CT2000.
The following commands are used to reduce completely ( ), to extend ( ), to

reduce ( ) and to close ( ) the active window.
These commands are available for all the following windows.
3.1.2 Menu bar
Figure 3--2 Menu bar
This menu bar contains the following menus:

Preferences (see the following paragraph)
Network Setting (see Paragraph 3.1.2.2)
Interfaces (see Paragraph 3.1.2.3)
Configuration (see Paragraph 3.1.2.4)
Edition (see Paragraph 3.1.2.5)
Workspace (see Paragraph 3.1.2.6)
Window (see Paragraph 3.1.2.7)
View (see Paragraph 3.1.2.8)
These different menus, sub--menus, commands and sub--commands of the CT2000
are presented in the following paragraphs.

411--9001--137
3.1.2.1 Preference menu
In the Preference menu, two sub--menus are available (see the previous figure):
Setup which is used to load networks and alternatives.
This command opens the Setup window (see Figure 3--3).
Quit which is used to exit the CT2000 session.

Figure 3--3 Setup window
The Setup window (see the previous window) is composed of the following parts:
A Network list area which gives the information (NetworkName, Net ID)
concerning the networks already loaded.
Two buttons are available.
The button is used to create a network.
The button is used to delete a network.

An Alternative list area which gives the information (Alternative Name, Alt ID)
concerning the alternatives already loaded.
Three buttons are available.
The button is used to copy an alternative.
The button is used to create an alternative.
The button is used to delete an alternative.

411--9001--137
A comment area which gives information concerning the commands already

executed.
Two action buttons
The button is used to validate the network and alternative load.
The button is used to cancel the load.
3.1.2.2 Network Setting menu
Only one sub--menu (Network Editor--Default) is available in this menu

This sub--menu allows you to set and modify the default parameters of your
network.

The Network Editor--Default command opens the Network window

Figure 3--4 Network Editor window
The Network Editor--Default command allows you to define or modify the default
parameters used in the CT2000. Default parameters are stored in a file in the Data
directory.
They will be applied in all the alternatives.
Note: The following description is applicable for all the editor and template
windows.
The Network editor (see the previous figure) is composed of:

a title bar
a menu bar
a tool bar
two parameters description areas
status bar

411--9001--137
Title bar
The Title bar indicates the title of the application.
The following commands are used to reduce completely ( ), to extend ( ), to

reduce ( ) and to close ( ) the active window.
These commands are available for all the editor and template windows.
Menu bar
This menu bar contains the following menus:

File
View
Tools
Operations
File menu
In the File menu, three sub--menus are available (see the following figure):
Apply
This command is used to apply changes.
Refresh
This command is used to refresh displayed values.
Quit
This command is used to close the Network editor window.

View menu
In the View menu, two sub--menus are available (see the following figure):
Toolbar
This command is used to hide or visualize the tool bar
Status Bar
This command is used to hide or visualize the status bar
Tools menu
In the Tools menu, only one sub--menus is available (see the following figure).
This command is used to customize the tool bar.

411--9001--137
The following window opens when the user selects this command.
The three following check marks are available:

Show Tooltips
Cool Look
Large buttons
The user can with these ones modify the tool bar aspect.
The following tool bar appears when no check mark are selected.
The following tool bar appears when only the Large buttons check mark is
selected.

The following tool bar appears when only the Cool Look check mark is
selected.
The following buttons are also available:
The button is used to confirm the modifications.
The button is used to quit the Customize window without

validating the modifications.
Operations
On the Network editor window, no sub--menu is available.
Tool bar
The following tool bar is composed of four active buttons:
The button is used to apply the modifications.

Then the Modified parameter list window opens (see the following figure).

411--9001--137
The grid contains the following informations concerning the modified

parameters:
Parameter
SubParameter
Family
OP
NewValue
OldValue
The following buttons are also available:
The button is used to confirm the modifications and save it in the

Database.
The button is used to quit the Modified parameter list window

without validating the modifications.
The button is used to locate the element. The Network Tree opens.
The button is used to refresh the window.
The button is used to quit the Network editor.

Parameters areas
This area (see the following figure) is composed of two sub--areas.
The first area (see the following figure) is composed of two thumbnails:
Contents
Search

411--9001--137
Contents thumbnail
This area represents a tree of parameters. It displays parameters for each family.

Search thumbnail
The Search area is composed of two fields that are used to find parameters. The user
can enter, in the Parameter to find field, the name of the parameter or the first
letters.
All parameters of any family that begin with this letter appear in the other field.
Note: You can enter the star character * at the begining instead of any group of
character.

411--9001--137
The second area (see the previous figure) gives the following information:
Parameter name
Parameter type (numerical, string, structure, list, vectot set, ...)
This area is composed of the default network parameters which are (in order):
CellNameRule
This parameter specifies the default rule used to define cellName for network
checking or when creating a BTS if no cellName is defined.
Possible values are:
siteName_ABisCellNumber
siteName_BtsId
siteName_sector
cellIdentity
cellIdentity--LAC
cellIdentity--LAC--MCC--MNC
or unset if you do not want to use any rule

CrossConnectChains
This parameter specifies the modes of the PCM links for the cross connect
chains.
The two modes are:
auto
Multisite
DefaultReservedBitForRSM
This parameter (integer) permits to reserve some time slots on the radioSiteMask
for further use in case of site extension strategy.
DefaultOmcVersion
This parameter specifies the default OMC--R version used for network checking
or creation of a new OMC--R by DRF. This version is also used to translate the
labels and the field values in many menus and editors.
The value must be a version supported by the CT2000.
DefaultPCMA0Mask
Not available for this release.
DefaultPCMA1Mask
DefaultPCMA2Mask
DefaultPCMA3Mask
DefaultPcmKind
This parameter specifies the default type of PCM. Possible values are E1 or T1.
DefaultRSMModeComput
Engineering method:
If the same PCM includes several sites, time slots are exclusive.
The RadioSiteMask of all sites on the same PCM are computed.
The system allocates time slots (from highest to smallest TS id) according to
the final priorities:
1 Traffic time slots
2 Time slots reserved for RadioSiteMask (see DefaultReservedBitForRSM)
3 Secondary LAPD time slots
RSM computation includes time slots of the AbisMask (see
DefaultAbisMask).

411--9001--137
LsbSecondaryLapd method:
If the same PCM includes several sites, time slots are exclusive.
The RadioSiteMask of all sites on the same PCM are computed.
The system allocates time slots (from highest to smallest TS id) according to
the final priorities:
1 Traffic time slots
2 Time slots reserved for RadioSiteMask (see DefaultReservedBitForRSM)

Secondary LAPD time slots are allocated (from smallest to highest TS id),
starting from the last primary LAPD TS.
RSM computation includes time slots of the AbisMask (see
DefaultAbisMask).
Engineering lock method:
Time slots are exclusive.
No reserved time slots for RadioSiteMask anymore.
If a site has been updated, the system includes all of the sites on the same PCM
to compute its RadioSiteMask. The system allocates time slots from highest to
smallest TS id taking into account that other sites, however, keep their
previous RadioSiteMask.
DMSPresent
MCCMNCToBsc
This parameter specifies whether the MobileCountryCode and
MobileNetworkCode of the BSC must be filled and updated during the
DoConsistency (option of the Network Object editor).
Possible values are True or False (used at the end of DRF loading).
Cyphering
NbPCMAPerTCU
This parameter specifies the number of pcmCircuit A generated when you create
a TCU.
Value is an integer from 1 to 4.
networkId
This parameter specifies the identifier of the network.
networkName

This parameter specifies the name of the network.

primBand
SDOXtpldAlgo
secBand
ServingBCCHInReselection
SS7IdMethod
This parameter specifies the method used to define the pcmCircuitId of the
pcmCircuit on A interface when creating a transcoder if no pcmCircuitId is
specified.
Possible values are Incremental or SS7 id = slc.
TCBHardwareRef
This parameter specifies the variable used for the hardwareRef parameter if not
defined when creating a transcoderBoard.
TCBSoftwareRef
This parameter specifies the variable used for the sWVersionRunning parameter
when creating a transcoderBoard.
DefaultAbisMask
To define all the available time slots to carry traffic and secondary lapd (string of
1 and 0). Only time slot filled by 1 are used for RSM computation.
TCULapdTerminalNumber
This parameter specifies the lapdTerminal number used by default when creating
a transcoder if none is set.
Value must be an integer from 0 to 39.
All the transcoders belonging to the same 2G bsc should have the same
lapdLinkterminalNumber.
DefaultBscArchitecture
This parameter specifies the default BSC architecture used for network checking
or BSC creation.
Possible values are bsc6000 and bsc12000.
TRXHardwareRef

411--9001--137
CAUTION
DO NOT SET TRX HARDWARE REFERENCE FOR AN E--CELL TO 9
INSTEAD OF 0. DOING SO WILL RESULT IN LOSS OF GPRS SER-
VICE.
DefaultBscMmiVersion
This parameter specifies the default BSC version used for network checking or
creation of command files if not specified in DRF.
Possible values are 8 to 12.
DefaultBscType
This parameter specifies the default BSC type used for network checking or
creation of a BSC if not specified in DRF.
Possible values are type1 to type5.
Note: The parameters DefaultbscMmiVersion, DefaultbSMMmiVersion,
DefaultbscArchitecture, DefaultbscType must be compliant with
DefaultomcVersion.
DefaultBSMMiVersion
This parameter specifies the default btsSiteManager Mmi Version used for
dimensionning checks if there is no sWVersionRunning defined in the
corresponding btsSiteManager object.
Value must be an integer from 6 to 12.
DefaultLanguage
This parameter specifies the default OMC--R language used when creating an
OMC--R. It is also used when translating the labels and the field values in the
menus and the editors.
Default value is English.
DefaultMicroCellAlgorithm
This parameter specifies the default microCellAlgorithm type used when
creating an OMC--R.
Possible values are:
none
AlgoA
AlgoB
Config

MAPPING MODEL
This parameter specifies the model of TDMA, the cabinet identity and the
priority for each TRX.
plmn Permitted
List of NCC of the PLMNs on which MSs are allowed to take measurements
for handovers. Listening to the PLMN to which the cell belongs must be
authorized.
Identification
Comment
Additional information (such as creation date).
MobileCountryCode
Specifies the code of the PLMN home country.
mobileNetworkCode
Specifies the code of the PLMN in the country.
network Colour Code
The templates are defined for one network and can be created or modified.
Remark: Value must be an existing template name (loaded in CT2000).
For the list of parameters for each template, refer to Appendices A and B of the NTP
148.
Status bar
The Status bar (see the previous figure) indicates the following informations
concerning parameters:
Type
Min Value
Max Value

411--9001--137
3.1.2.3 Interfaces menu
The Interfaces menu deals with the different interfaces of the CT2000. It allows
you to perform different operations relative to the DRFs, CTFiles, CTSDOs and
template (see the following figure).
The Interfaces menu proposes five commands:

DRFs Import
DRFs Export
CT Import
CTSDOs Export
Template

Interfaces --> DRFs Import
The DRFs Import command allows you to load the DRF tables of the different
OMC--R BSS objects, in order to create these objects in your CT2000 database.
The DRFs Import command opens the Import DRF Files window
Figure 3--5 Import DRFs window
This window is composed of different parts.

An Import in a Network element list which allows you to load the DRF table in
a specific NEL. This list displays all the NELs that are available in the
alternative.

411--9001--137
An button.
After clicking on this button, the following Options window opens.
This window is composed of the following parts:

A Rules area which gives information (Profile Name, Type) concerning the
profiles already loaded.
a button used to load the selected profile rule.
a button used to deselect the profile rule.

A Language area used to select the DRFs language.
The user can choose the language of the DRF. The language must be:
ENGLISH (default value).
Two action buttons are available:
the button allows you to validate the selected options. Then the
user returns to the Import DRF Files window (see Figure 3--5)

the button allows you to close the active window without

validating the selected options. Then the user returns to the Import DRF Files
window (see Figure 3--5)
A Files area which is composed of four parts.
The first part allows you to select the name partition.
The second part allows you to select the name of the directory where are
located the DRF files.
The third part displays the files that are located in the selected directory.
The fourth part allows you to select the files name or the extension type.
A central part which is composed of three action buttons.
The button allows you to load, in the Selected files area, one/or a list of
selected files.
The button allows you to remove, from the Selected files area, one/or a
list of files.
The button allows you to load, in the Selected files area, all the files
located in the Files area.
A Selected files area contains informations (File name, Path) concerning the
files which are loaded.
An Operation list which contains the following options:
Create_Update
Create_Update (new NEI plan)
Remove
Two action buttons
The button is used to validate the selection. Then the Import Report
window opens (see the following figure).
The button is used to cancel the selection. The user returns to the
CT2000 Main window (see Figure 3--1).

411--9001--137
Figure 3--6 Import DRF Report window

the button allows the user to save, in the desktop, a file (Report.txt) which
contains all the information about the previous process.
the Error messages part which displays the following information concerning
the error and warning messages:
Level
Identification cause
Rejection cause
two checks marks (Error messages and Warning messages) which allows the
user to visualize on the previous area only the selected messages
the button allows the user to open the Report window

(see the following figure)
three buttons ( , , ) which allows the user to start or stop the DRF
import process

a process bar allows the user to follow the status of the DRF import
an area which displays the actions during the process
the button which is used to return to the Import DRFs window

(see Figure 3--5)
This window consists of three parts:

the Session part which displays the session report when the user click on the
previous window button.

For each session report, the following is indicated:
Profile Name
Begin Date
End Date
Comment

411--9001--137
the Result part displays the errors for the session

For each error, the following is indicated:
Severity
Message
the third part is composed of the Close button which is used to return to the
Import DRF Report window (see Figure 3--6)
Interfaces --> DRFs Export
The DRFs Export command allows you to extract some of the data that have been
used to create OMC--R BSS objects from the CT2000 database. These data are
recovered in ASCII files which allow you to process them with an external
application (any spreadsheet program). For instance you can export the DRFs
relative to the network you have loaded from an ODB (OMC--R database) to
perform modifications, additions, checking.
Note: If the exported object has no Model Id, the DRF Export automatically
associates one.
ASCII files produced

The different ASCII files produced are the following (for further details, please
refer to NTP 148 ):
DRFFiles.ain
DRFFiles.bsc
DRFFiles.cel
DRFFiles.coo
DRFFiles.hov
DRFFiles.nei
DRFFiles.psn
DRFFiles.pcu
DRFFiles.pwc
DRFFiles.sit
DRFFiles.tcu
DRFFiles.tdm
DRFFiles.trx
DRFFiles.tsz

The DRFs Export command opens the Export DRF window

Figure 3--7 Export DRF window
A Set Option area which contains the button.

After clicking on this button, the following Export Option window opens.

411--9001--137

A check mark (Export from NEL) allows you to export the DRF table in a
specific NEL. A list displays all the NELs that are available.
A list which contains different extensions for each NEL
The different extensions are:
Without extension
Children
Parents
Linked objects
This choice is also available if a NEL is selected.
Two action buttons are available:
The button allows you to validate the selected options. Then you
will return to the Export DRF window (see Figure 3--7).
The button allows you to close the active window without

validating the selected options. Then you will return to the Export DRF
window (see Figure 3--6).
A Set Working Folder area which is composed of three parts and one action
button (Create Folder).
The first part (Drives) allows you to select the name partition.
The second part (Name) allows you to enter the name of the folder where the
DRF files will be exported.
The third part (Folder) allows you to select the name of the folder where the
The Create Folder button is used to create a new folder.
Two action buttons:
The button is used to validate the selection. Then the Export

Report window opens (see the following figure).

Level
Rejection cause
three buttons ( , , ) which allows the user to start or stop the DRF
export process
a process bar allows the user to follow the status of the DRF export
the button which is used to return to the Export DRF window

(see Figure 3--7)

411--9001--137
Interfaces --> CT Import
The Load CT Files command allows you to load the CT Files, generated by the
CTSDOtoCTFiles OMC--R plug--in, in order to create your CT2000 database.
The Load CT Files command opens the Load CT Files window (see the
following figure).
Figure 3--8 Load CT Files window

A Set Working Folder area which is composed of three parts.
CT files are located.
Two action buttons:
The button is used to validate the selection. Then the Load CT

Files Report window opens (see the following figure).

Level
Rejection cause
three buttons ( , , ) which allows the user to start or stop the CT files
import process
a process bar allows the user to follow the status of the CT files import
the button which is used to return to the Load CT files window

(see Figure 3--8)

411--9001--137
Interfaces --> CTSDOs Export

The CTSDOs export command allows you to export files under database
alternatives in CTSDO files.
The CTSDOs Export command opens the Export CTSDO window
Figure 3--9 Export CTSDO window

CT--SDO files will be exported.
CT--SDO files will be exported.
The button is used to create a new folder.

Two action buttons:
The button is used to validate the selection. Then the Export SDO
Report window opens (see the following figure).

Level
Rejection cause
three buttons ( , , ) which allows the user to start or stop the CT--SDO
export process
a process bar allows the user to follow the status of the CT--SDO export
the button which is used to return to the Export SDO window

(see Figure 3--9)

411--9001--137
Interfaces --> Template

The Template sub--menu proposes three commands relative to the templates:
Import
Export
Manager
Interfaces --> Template --> Import
The Import command allows you to load the templates or mapping models you
have created or modified into the CT2000.
The Import command opens the Import Template window
Figure 3--10 Import Template window

A Files area which is composed of four parts.
The first part allows you to select the partition name.
The second part allows you to select the name of the directory where the
templates are located.
The third part displays the file that are located in the selected directory.
The fourth part allows you to select the files name or the extension type.

A central part which is composed of three action buttons.
The button allows you to load, in the Selected files area, one/or a list of
selected files.
The button allows you to remove, from the Selected files area, one/or a
list of files.
The button allows you to load, in the Selected files area, all the files
located in the Files area.
A Selected files area contains informations (File name, Path) concerning the
files which are loaded.
Two action buttons
The button is used to validate the selection. Then the Import

Template Report window opens (see the following figure).

411--9001--137
Level
Rejection cause
three buttons ( , , ) which allows the user to start or stop the Template
import process
a process bar allows the user to follow the status of the Template import
the button which is used to return to the Import Template window

(see Figure 3--10)

Interfaces --> Template --> Export

The Export command allows you to extract the content of templates from the
CT2000 database. The templates are recovered under ASCII files which allow you
to process them with an external application (any spreadsheet program).
The Export command opens the Export Template window
Figure 3--11 Export Template window

template files will be exported.
template files will be exported.
The button is used to create a new folder.

Two action buttons:


411--9001--137
Level
Rejection cause
three buttons ( , , ) which allows the user to start or stop the Template
export process
a process bar allows the user to follow the status of the Template export
the button which is used to return to the Export Template window

(see Figure 3--11)

Interfaces --> Template --> Manager
The Manager command allows you to assign a template to a network element and
to propagate parameter modifications to objects (all the objects or a selection of
objects).
The Manager command opens the Network Element Template Manager window
Figure 3--12 Network Element Template Manager window

A Source area
A Target area
A central part which is composed of three actions buttons.
The button allows you to add, in the Script area, the selected
NE.
The button allows you to remove, from the Script area, one/or a
list of NEs.
The button allows you to remove, in the Script area, all the
NEs.

411--9001--137
A Script area
An button.
After clicking on the button, the following Parameters window

opens.


a Template Class field which indicates the class of the parameters
a Select the parameters to propagate area which contains the Parameters
list.
A check mark is locate beside the parameter name. These check marks
allow the user to select one or more parameters to propagate.
A Select All ckeck mark allows the user to select all the parameters.
two action button
The button is used to validate the selection.
The button allows you to close the active window without

validating the selected options. Then you will return to the Network
Element Template Manager window (see Figure 3--12).
Two action buttons:


411--9001--137

an area which displays the complete actions
the button which allows the user to start the propagation process
a process bar allows the user to follow the status of the propagation process
the button is used to return to the Network Element Template

Manager window (see Figure 3--12)

3.1.2.4 Configuration menu
The Configuration menu proposes three commands (see the following figure):
Global Update
Network checker
Datafill Rule

411--9001--137
Configuration --> Global Update
The Global update editor allows you to modify parameters for a set of existing
objects by using a propagation mechanism. The attribute values for the currently
selected object can be propagated over all or part of the network object, thus
enhancing datafill efficiency by reducing manual repetition and possible sources of
error.
The Global Update command opens the Global update Manager window
Figure 3--13 Global update Manager window

Configuration --> Network checker
The Network checker command enables you to run different tests that will check
the coherency of the CT2000 database from an OMC--R point of view.
We recommend using this command after creating new objects, in order to check
that they have been created with respect to the design and equipment dimensioning
rules.
The Network checker command opens the Network Checker window

Figure 3--14 Network Checker window
This window is composed of the following functional blocks:

Profile Management
Targets
Action buttons
Session reports

411--9001--137
Profile Management
The Profile Management block (see the previous figure) is composed of the
following elements:
a check profiles List
The check profiles list shows all the profiles recorded in the database and for each
check profile:
a Profile Name column which contains the check profile names
a Id column which indicates the identifier
Five action buttons:
the button which is used to edit a selected check profile
the button which is used to create a new check profile
the button which is used to modify a selected check profile
the button which is used to copy a selected check profile
the button which is used to delete a selected check profile

Targets
The Targets block (see the previous figure) allows the user to choose the target on
which the selected check profile is applied. The target can be:
All NE of alternative
NEL
Current selection
For the NEL selection, the user can choose one of the stored NELs (in the Select
NEL list) and select one of the extension in the Extend To list (see the following
figure):
Without extension
Children
Parents
Linked objects
For the current selection target, the user chooses only the extension (see the previous
figure).

411--9001--137
Action buttons
This block is composed of:
the button which is used to launch the selected check profiles in the
selected target. This button is enabled only if at least one check profile and one
target is selected.
the button which is used to exit from the check operation
the button which is used to open the Report window

(see Figure 3--15)
Process bar
This process bar allows you to follow the status of the check. This process bar is as
follows at the end of the check.
Report window
The Report window (see the following window) displays the session report. One
session report is attached to one check profile, so when the user launches more than
one check profile to one target, all the sessions attached to check profiles are listed.
This window is composed of :
the Session block, which indicates the following information concerning the
check:
Profile Name
Begin Date
End Date
Comment
the Result block, which displays the check error for one given session. For each
check error, the following is indicated:
the Severity of the error (Information message, Warning, error)
the description of the error (Error Message)
Note: For more explanations about error messages, refer to NTP 148.
the button which allows you to close the Report window and to
return to the Network Checker window (see Figure 3--14).

After clicking on one of the errors, the following part allows you to determine which
network element is in fault.
Figure 3--15 Network Checker -- Report window
Check Profile Edition
The Edition window (see the following window) allows you to visualize the
corresponding profile.
The Edition window (see the following figure) is composed of the following parts:
a check profile display device which allows you to select one item to see all the
checks belonging to the selected item
a filtering device which allows you to choose the filter to apply to the check
display device. The filters are by check type (ODB, engineering, ...)
the Check display device which shows all checks depending on the selected item
in the Check profile display device and the selected filter

411--9001--137
For each displayed check, the following is indicated:

one check mark which indicates if the auto--correction is selected.
the check name
the four parameters values of the check
the button which allows you to exit from the edition window and to
return to the Network Checker window (see Figure 3--14)
Figure 3--16 Network Checker -- Edition window

Check Profile creation
The New Profile window (see the following window) allows you to create a new
check profile.
Figure 3--17 Network Checker -- new profile window
This window is composed of four parts.
Profile display
Check profile displaying device (left side)
This device shows all checks which contain no other check as reference. A check
can be referenced for more than one profile.
Reference area
The button allows you to add a check profile by reference.
The button allows you to remove a check profile by reference.

Check profile displaying device (right side)
This device shows all the check profiles referenced by the current check profile.

411--9001--137
Filtering devices
The two devices allow you to choose the filter to apply to the check display device.
The filters are by check type (ODB, engineering, ...).
Check display
check display devices
The two devices show all checks depending on the selected check profile and the
selected filter.
For each displayed check, the following is indicated:
One check mark which allows you to select the auto correction flag when it is
available, otherwise the check mark is not enabled.
On the left part of the window (display of all available checks):
check WITH check mark in the auto correction flag means that an auto
correction is available for this check
check WITH NO check mark in the auto correction flag means that NO
auto correction is available for this check
On the right part of the window (display of all selected checks for your new
profile):
check WITH check mark in the auto correction flag means that the auto
correction is actived for this check (if you launch the created profile, the
auto correction will be performed if an error occur for this check)
check WITH NO check mark in the auto correction flag means that NO
auto correction is not actived for this check
The check name.
The four parameters values of the check.
Copy area
The button allows you to add a check by copy.
The button allows you to remove all checks by copy.
The button allows you to remove a check by copy.

Action buttons
The button is used to validate the creation. The Save window opens (see
the following windows).
The button is used to exit from the check creation window.
Figure 3--18 Network Checker -- Save window
The Save window is used to enter the following information concerning the new
check profile:
Profile Name
Profile Description
The button is used to validate, in the database, the new check profile
creation.
The button is used to cancel the save and return to the new profile
window.

411--9001--137
Check Profile modification
Refer to the previous paragraph for explanations concerning the following Modify
windows.
Figure 3--19 Network Checker -- Modify window
The button allows you to exit from the Modify window, and write the
modifications in the database.
The button is used to cancel the modification operation.

Check Profile copy
The Copy window (see the following figure) allows you to make a copy of the
selected profile.
Figure 3--20 Network Checker -- Copy window
This window is composed of:

the Profile Name field used to enter the name of the profile
the Profile Description field used to enter comments concerning the profile
the button used to validate the new profile name
the button used to cancel the copy operation

411--9001--137
Configuration --> Datafill Rule
The Datafill rule command enables you to apply given engineering rules to datafill
some BSS network resources.
The Datafill rule command opens the Datafill Rules window (see the following
figure).
Figure 3--21 Datafill Rules window
This window is composed of the following functional blocks:

Profile Management
Targets
Action buttons
Session reports

Profile Management
The Profile Management block (see the previous figure) is composed of the
following elements:
a check Profiles List
The check profiles list shows all the profiles recorded in the database and for each
datafill rule profile:
a Profile Name column which contains the datafill rule profile names
a Id column which indicates the identifier
five action buttons
the button which allows you to edit a selected datafill rule profile
the button which allows you to create a new datafill rule profile
the button which allows you to modify a selected datafill rule

profile
the button which allows you to copy a selected datafill rule profile
the button which allows you to delete a selected datafill rule

profile

411--9001--137
Targets
The Targets block (see the previous figure) allows the user to choose the target on
which the selected datafill rule profile is applied. The target can be:
All NE of alternative
NEL
Current selection (from the network tree)
For NELs, the user must to select:
the NEL in the select NEL list
one of the extensions in the Extend To list (see the following figure):
Without extension
Children
Parents
Linked objects
For the current selection target, the user chooses only the extension (see the previous
figure).

Action buttons
This block is composed of:
the button which is used to launch the selected check profiles in the
selected target. This button is enabled only if at least one check profile and one
target is selected.
the button which is used to exit from the check operation
the button which is used to open the Report window
Process bar
This process bar allows you to follow the status of the check. This process bar is as
follows at the end of the datafill rule.
Report window
The Report window (see the following window) displays the session report. One
session report is attached to one datafill rule profile, so when the user launches more
than one datafill rule profile for one target, all the sessions attached to datafill rule
profiles are listed.
the Session block, which indicates the following information concerning the
datafill rule:
Profile Name
Begin Date
End Date
Comment
the Result block, which displays the check error for one given session. For each
check error, the following is indicated:
the Severity of the error (Information message, Warning, no fatal error, fatal
error)
the description of the error (Error Message)
the button which allows you to return to the Datafill Rules window

411--9001--137
Figure 3--22 Datafill Rules -- Report window

Datafill Rules Profile edition
The Edition window (see the following figure) is composed of the following parts:
a datafill rule profile displaying device which allows the user to select one item to
see all the datafill rules belonging to the selected item.
The items can be:
a referenced datafill rule profile
the current datafill rule profile
or all datafill rules
This last item allows you to list all the datafill rules of the reference datafill rule
profile and of the current datafill rule profile.
a filtering device which allows the user to choose the filter to apply to the rule
displaying device.
the datafill rule displaying device which shows all datafill rules depending on the
selected item in the datafill rule profiles displaying device and the selected filter.
For each displayed datafill rule, the following is indicated:
one datafill rule mark which allows you to select the auto correction flag when
it is available, otherwise the datafill rule mark is not enabled
the datafill rule name
the four parameters values of the datafill rule
the button which allows you to exit from the edition window.

411--9001--137
Figure 3--23 Datafill Rules -- Edition window

Datafill Rules Profile creation

The New Profile window (see the following window) allows you to create a new
datafill rule profile.
Figure 3--24 Datafill Rules -- New Profile window
This window is composed of four parts.
Profile display
Datafill rule profile displaying device (left side)
This device shows all the datafill rule profiles available in the database that are
not already referenced.
Reference area
The button allows you to add a datafill rule profile by reference.
The button allows you to remove a datafill rule profile by

reference.
Datafill rule profile displaying device (right side)
This device shows all the datafill rule profiles referenced by the current datafill
rule profile.

411--9001--137
Filtering devices
The two devices allow the user to choose the filter to apply to the datafill rule
displaying device.
Datafill rule display

Datafill rule displaying devices
The two devices shows all datafill rules depending on the selected datafill rule
profile and the selected filter.
For each displayed datafill rule, the following is indicated:
one datafill rule mark which allows to select the auto correction flag when it is
available, otherwise the datafill rule mark is not enabled
the datafill rule name
the four parameters values of the datafill rule
Copy area
The button allows to add a datafill rule by copy.
The button allows to remove all datafill rules by copy.
The button allows to remove a datafill rule by copy.

Action buttons
The button allows you to validate the creation. The Save window
opens (see the following windows).
The button is used to exit from the datafill rule creation.
Figure 3--25 Datafill Rules -- Save window
The Save window is used to enter the following informations concerning the new
datafill rule profile:
Profile Name
Profile Description
The button allows you to validate, in the database, the new datafill rule
profile creation.
The button is used to cancel the save.

411--9001--137
Datafill Rules Profile modification
Refer to the previous paragraph for explanations concerning the following Modify
windows.
Figure 3--26 Datafill Rules -- Modify window
The button allows you to exit from the Modify window, and write the
modifications on the database.
The button is used to cancel the modification operation.

Datafill Rules Profile copy
The Copy window (see the following figure) allows you to make a copy of the
selected profile.
Figure 3--27 Datafill Rule -- Copy window

the Profile Name field used to enter the name of the profile
the Profile Description field used to enter comments concerning the profile
the button used to validate the new profile name
the button used to cancel the copy operation

411--9001--137
3.1.2.5 Edition menu
The Edition menu allows you to display the Network Element List and the Network
Tree (see the following figure).
The Edition menu proposes three commands:
Log session
Rules session Log
Network Element List
Network Tree

Edition --> Log session
The Log session command gives access to the Log session editor which allows the
user to follow all modifications of the database and all commands requested per user
The log session command opens the Log session editor window (see the following
figure).
The log session information items are start time, a command number, the user name,
the alternative and the command.
Figure 3--28 Log session editor window

411--9001--137
Edition --> Rules session Log
The Rules session Log command opens the Rules session Editor window
Figure 3--29 Rules Session Editor window

Edition --> Network Element List

The Network Element List command gives access to the object browser which
allows you to display the list of the instances matching an object type in tabular
form.
The Network Element List command opens the Network Element List Manager
window (see the following figure).
Figure 3--30 Network Element List Manager window

The Network Element List Manager window (see the previous window) is
composed of the following parts:
A Network Element list area which gives the name of the NEL already defined in
the current alternative.
Four buttons are available:
The button is used to create a NEL.
The button is used to copy a NEL which already exist.
The button is used to delete a NEL.
The button is used to convert a given NEL by any NE class.

411--9001--137
A Network Elements area which gives informations (path, class) concerning the
NE loaded in the selected NEL.
Two buttons are available:
The button is used to remove one/or a list of selected NE.
The button is used to remove all the NE of the selected NEL.
The button is used to close this window.
Edition --> Network Tree
The Network Tree command allows you to access to the objects of the Network as
they are represented in the Q3 hierarchy. The tree structure represents the Network
of the current alternative.
The Network Tree command opens the Network Tree window
This Network Tree displays all the Network objects in a graphical view.
From this Network tree, the user can access three type of informations:
Hierarchical TV (see Figure 3--31)
Topological TV (see Figure 3--32)
Template TV (see Figure 3--33)

Figure 3--31 Network Tree window -- Hierarchical TV

411--9001--137
Hierarchical TV
The tree structure is a graphical representation of the network.

The description of these icons is the following:
represents the Alternative
represents the OMC object
represents the MSC object
represents the BSC object
represents the TCU object
represents the A--interface object
represents the PCU object
represents the site object
represents the cell object
represents the TDMA object
represents the handOverControl object
represents the powerControl object
represents the TRX object
represents the neighboring cell object
represents the PCUSN object
represents the TSZ object

Topological TV
The following figure allows you to determine the following informations site
informations:
PCM #
Tei
Ts
Multi Site Name
Site Information
Figure 3--32 Network Tree window -- Topological TV window

411--9001--137
Template TV
The following figure allows you to determine templates associated to each network
element type.
Figure 3--33 Network Tree window -- Template TV window

How to use the Network Tree
You can navigate in the Network Tree view by simply using your mouse.
To display the sub--tree, you can:
Click in the icon which allows you to see the other objects. Then this icon
changes ( ).
Click twice in the object that allows you to see the other objects. A blue line
appears on the selected object.
Note: The editor concerning the selected object opens too.
To perform the principal commands available from the selected object:

Select an object by clicking on its name.
With the right button of your mouse, display the available editor list from the
object.
Different commands are available depending of the object selected.
From the alternative object, the Generic Editor command is available (see the
following figure).
From the OMC object, the following commands are available (see the following
figure):
Add to list
BSC creation
Delete
Generic Editor
Reverse Creation

411--9001--137
From the HOV, PWC, TRX, TDMA and TSZ objects, the following commands
are available (see the following figure):
Add to list
Generic Editor
Reverse Creation
From the MSC, the following commands are available (see the following figure):
Add to list
Generic Editor
From the BSC object, the following commands are available (see the following
figure):
Add to list
Delete
Generic Editor
Internal View
Reverse Creation
Site creation
TCU creation

From the PCUSN, PCU, AINT, TCU and NEI objects, the following commands
are available (see the following figure):
Add to list
Delete
Generic Editor
Reverse Creation
From the CELL object, the following commands are available (see the following
figure):
Add to list
Generic Editor
NEI Editor
Reverse Creation
From the SITE object, the following commands are available (see the following
figure):
Add to list
Delete
Generic Editor
Internal View
Reverse Creation

411--9001--137
From the NEI set object, the NEI editor command is available (see the following
figure).
Click on the selected command, the appropriate editor opens.
To close the Network Tree window, click on the toolbar icon.
3.1.2.6 WorkSpace menu
The WorkSpace menu allows you to display the MenuBar and the Operation traces
The WorkSpace menu proposes two commands:

MenuBar
Operation traces

Workspace --> MenuBar
This command allows you to display the menus of the network configuration in the
Main Window.
The MenuBar command opens the Menu window (see the following figure).
Figure 3--34 Menu window
To reduce the Menu window, click once on the bar.
To close the Menu window:
click on the corner icon located on the top
or click on the toolbar icon

411--9001--137
Workspace --> Operation traces
This area shows the result of the current operation.

The Operation traces command opens the Operation traces window
Figure 3--35 Operation traces window
To reduce the Operation traces window, click once on the

bar.
To close the Operation traces window:
click on the corner icon located on the top
or click on the toolbar icon

3.1.2.7 Window menu
The Window menu allows you to display a set of windows (see the following
figure):
Cascade
Tile horizontal
Tile verticale

411--9001--137
3.1.2.8 View menu
The View menu proposes three commands (see the following figure):
ToolBar
StatusBar
About...
View --> ToolBar
This command allows you to display the toolbar icons in the CT2000 Main window
(see Paragraph 3.1.3).
View --> StatusBar
This command allows you to display the status information in the CT2000 Main
window (see Paragraph 3.1.8).
View --> About...
This command allows you to display the information about the CT2000.

The About... command opens the About CT2000 Application window

Figure 3--36 About CT 2000 Application window
The system Info... command opens the Microsoft System Information window

411--9001--137
Figure 3--37 Microsoft System Information window

3.1.3 ToolBar
The toolbar consists of the following icons (from left to right).
Menu Bar
Click on the icon (the first from the left) to display the Menu area
(see Figure 3--34) in the Main window.
For instance:
Preferences
Checks/Rules
DRF Objects
Templates
CTSDO
Global Update
Network Element
Operation traces
Click on the icon (the second from the left) to display the Operation traces
Setup
Click on the icon (the third from the left) to display the Setup window (see
Figure 3--3).
Network Tree
Click on the icon (the fourth from the left) to display the Network tree
within the Tree Explorer area of the CT2000 Main window (see Figure 3--31).
Network Checker
Click on the icon (the fifth from the left). The Network Checker window
opens (see Figure 3--14).
Datafill Rules
Click on the icon (the sixth from the left). The Datafill Rules window opens
(see Figure 3--21).

411--9001--137
Rules session editor
Click on the icon (the seventh from the left). The Rules session editor
window opens (see Figure 3--29).
Import DRF
Click on the icon (the eighth from the left) to display the Import DRF Files
Load CT--Files
Click on the icon (the eighth from the right) to display the Load CT Files
Export DRF
Click on the icon (the seventh from the right) to display the Export DRF
Import Template
Click on the icon (the sixth from the right) to display the Import Template
Export Template
Click on the icon (the fifth from the right) to display the Export Template
CTSDO export
Click on the icon (the fourth from the right) to display the Export SDO
Template Manager
Click on the icon (the third from the right) to display the Network Element
Template Manager window (see Figure 3--12).
Global Update
Click on the icon (the second from the right) to display the Global Update
Click on the icon (the first from the right) to display the Global Update

3.1.4 Network Tree

The Network Tree area (see Figure 3--31) is the zone in which you can get the
graphical Network tree of your network.
3.1.5 Menu area

The Menu area (see Figure 3--34) is the zone in which you can get a global menu
of your network. In this area, you can have the following menus:
Preferences
Checks/Rules
DRF objects
Templates
CTSDO
Global Update
Network Element

411--9001--137
3.1.5.1 Preferences
The Preferences menu groups the following icons (see the following figure).
Setup
Click on the icon to display a Setup window (see Figure 3--3).

Network
Click on the icon to display a Network Editor window

(see Figure 3--4).

3.1.5.2 Checks/Rules
The Checks/Rules menu groups the following icons (see the following figure).
Network Checker
Click on the icon to display the Network Checker window

(see Figure 3--14).
Datafill Rules
Click on the icon to display the Datafill Rules window

(see Figure 3--21).
Rules session log
Click on the icon to display the Rules Session Editor window

(see Figure 3--29).

411--9001--137
3.1.5.3 DRF Objects
The DRF Objects menu groups the following icons (see the following figure).
DRFs Import
Click on the icon to display the Import DRF Files window

(see Figure 3--5).
DRFs Export
Click on the icon to display the Export DRF window (see

Figure 3--7).
CT Import
Click on the icon to display the Load CT Files window

(see Figure 3--8).

3.1.5.4 Templates
The Templates menu groups the following icons (see the following figure).
Import
Click on the icon to display the Import Template window

(see Figure 3--10).
Export
Click on the icon to display the Export Template window

(see Figure 3--11).
Manager
Click on the icon to display the Network Element Template Manager


411--9001--137
3.1.5.5 CTSDO
The CTSDO menu groups the following icon (see the following figure).
CTSDOs Export
Click on the icon to display the Export CTSDO window

(see Figure 3--9).

3.1.5.6 Global Update
The Global Update menu groups the following icon (see the following figure).
Global Update
Click on the icon to display the Global Update Manger window

(see Figure 3--13).

411--9001--137
3.1.5.7 Network Element
The Network Element menu groups the following icon (see the following figure).
Click on the icon to display the Network Element List

Manger window (see Figure 3--18).
3.1.6 Workspace
The workspace displays the working pop--up menu. All the windows open in this
area.
3.1.7 Operation traces area

This area (see Figure 3--35) shows the result of the current operation.

3.1.8 Status bar

The status bar either displays some attributes of the object under selection in the
menu or provides information about a process under way.
The status bar contains:

the status
the current network name
the current alternative name
the current network element with its localization in the network
the date
the time

411--9001--137
3.2 Objects Management

The following paragraphs describe the different editors that you use within the
CT2000:
Object Editor (see the following paragraph)
Template Editor (see Paragraph 3.2.2)
Network Checker Editor (see Paragraph 3.2.3)
3.2.1 Object Editor
3.2.1.1 Description of the Object Editor
Each object type defined in the CT2000 database has an editor from which you can
run several actions. You will find object editors for the BSS objects and the
templates.
How to run the Object Editor
There are different ways to run the Object Editor. You can:
select an object in the Network Tree (see Figure 3--31) and click twice on it.
select an object in the Network Tree and select the Generic Editor command
from the right button of your mouse (see Paragraph 3.1.2.5).
select an object in the Network Tree (see Figure 3--31) and click twice on the
button located on the toop of the network
tree.
In all these cases, one of the following Object Editor menu opens.

3.2.1.2 Alternative editor
Refer to Paragraph 3.1.2.2 for explanations concerning the global design.

Note: The following global design of the editor is available for all the other ones
(except for the Operation menu).
Figure 3--38 Alternative editor window
Parameter description area
The parameter description allows you to know:

Parameter name
Parameter type (numerical, string, structure, list, vector set, ...)
Min Max value
The Alternative parameters are classified in the following families:
altName
creationDate
lastModifDate
Identification
Comment

411--9001--137
3.2.1.3 OMC editor
Note: The following design of the Operation menu is available for all the other
editors.
In the Operation menu, two sub--menus are available (see the previous figure):
Add to list which is used to add the selected object to a list.
Reverse Creation which is used to create a new template associated to the
selected object.
Figure 3--39 OMC editor
The OMC parameters are classified in the following families:

Algo&protocol
Algo A
GSM Protocol
MICRO ALGO TYPE
SS7 Protocol

Config
Architecture
Language
version
PCM Kind
TEMPLATE
Coordinates
Deg Lat
Deg Lon
Direction Lon
Sec Lat
Sec Lon
Label
Min Lat
Min Lon
Direction Lat
Comment
Feature Flags
ASCI Mode
cellTiering
GPRS
Identification
Comment
Coordinate
OMC
omcId

411--9001--137
3.2.1.4 PCU editor

The PCU editor (see the following figure) opens when the user selects a PCU object.
Figure 3--40 PCU editor window

The PCU parameters are classified in the following families:
Algo&protocol
cRC
Config
administrativeState
TEMPLATE
Coordinates
Min Lat
Min Lon
Direction Lat
Comment
DegLat
Deg Lon
Direction Lon
Sec Lat
Sec Lon
Label
Identification
Comment

3.2.1.5 PCUSN editor
The PCUSN editor (see the following figure) opens when the user selects a PCUSN
object.
Figure 3--41 PCUSN editor window
The PCUSN parameters are classified in the following families:

Identification
pcusn
pcusnName
TEMPLATE
Comment
Config
operattionalState
BSCRefList
MuxNumber
pcuSNReserved1
pcuSNreserved2
Coordinates
Label

411--9001--137
Min Lon
Direction Lat
Deg Lat
Min Lat
Sec Lat
Direction Lon
Deg Lon
Sec Lon
Comment
3.2.1.6 MSC editor

The MSC editor (see the following figure) opens when the user selects a MSC
object.
Figure 3--42 MSC editor window

The MSC parameters are classified in the following families:
Identification
MSC POINT CODE
MSC NAME
Others
List of LACs

3.2.1.7 BSC editor
The BSC editor (see the following figure) opens when the user selects a BSC object.
Figure 3--43 BSC editor window
The BSC parameters are classified in the following families:

Identification
bsc Name
bsc
TEMPLATE
comment
Config
administrativeState
bsc Architecture
bsc Version
MainNetworkBand
NB OF LSA
NB OF TMU
portChosen
bscCounterList
Features

411--9001--137
bsc Hop Reconf Use

bscGprsActivation
pcusnName
bsc Ms Acces class Barring Function
bscCapacityReduction
multiple Vocoders
encryption Algor Supported
lcsType
uplinkMappingProcessingMode
HO
bss Map Tchoke
HO Second Best Cell Configuration
time Between HO Configuration
ho Traffic
inter Bsc Directed Retry
intra Bsc Directed Retry
mode Modify Mandatory
Network addresses
ProtocolUsed
bsc IP First Adr
bsc IP Second Adr
bsc X25 Pref Adr
bsc X25 Sec Adr
X25 administrativeState
X25VIA A interface
Timers
bss Map T1
bss Map T4
bss Map T7
bss Map T8
bss Map T12
bss Map T13

bss Map T19

bss Map T20
rad Res Sup Busy Timer
rad Res Sup Free Timer
Coordinates
Label
Direction Lat
Min Lat
Sec Lat
DegLat
Direction Lon
Deg Lon
Min Lon
Sec Lon
Comment
HW&SW
software reference
3.2.1.8 TCU editor

The TCU editor (see the following figure) opens when the user selects a TCU
object.
Figure 3--44 TCU editor window

411--9001--137
The TCU parameters are classified in the following families:

Identification
transcoder
Cabinet Number
Shelf Number
transcoderArchitecture
Template
Comment
Config
administrativeState
TCBoard administrativeState List
transcoderAlarmMask
Algo&protocol
algo Id
data mode 14.4 kbit/s
Lapd Signaling
lapd Terminal Number
lapd link
PCM links
pcm Circuit Id
PCM Ater AdministrativeState
pcmA
pcmaAdministrativeState
cRC
Coordinates
Label
Direction Lat
Min Lat
Sec Lat
DegLat
Direction Lon
Deg Lon
Min Lon

Sec Lon
Comment
HW&SW
software reference
hardware reference
3.2.1.9 Aint editor
The Aint editor (see the following figure) opens when the user selects a Aint object.
Figure 3--45 AINT editor window
The Aint parameters are classified in the following families:

Identification
template
Comment
Config
administrativeState
preemptionConfiguration
Algo&protocol
bsc Queueing Option
data non transparent mode
data transparent mode

411--9001--137
speech mode
errorCorrectionMethod
cRC
Messages
circuit Group Block
confusion
cypher Mode Reject
layer3 Msg Cyph Mod Comp
reset Circuit Repeat
unequipped Circuit
SignalingLink
BSC POINT CODE
MSC POINT CODE
MSC NAME
ccs7 Local SubSystemNumber
ccs7 Remote Subsystem Number
sigLink
signalling Point Type
SCCPRoutingIndicator
sigPReserved2
Speech & Channel
chosen Channel Ass Comp
chosen Channel Comp L3Info
chosen Channel Ho Perf
chosen Channel Ho Req
currentChannelHorqd
encryp Algo Ass Comp
encryp Algo Ciph Mod Comp
encryp Algo Ho Perf
encryp Algo Ho Req
speechVersionAsscomp
speechVersionHoperf

speechVersionHoreq
speechVersionHorqd
Timers
bss Sccp ConnEst
bss Sccp Inact Rx
bss Sccp Inact Tx
bss Sccp Release
bss Sccp Sub Sys Test
3.2.1.10 Site editor
The Site editor (see the following figure) opens when the user selects a site object.
Figure 3--46 SITE editor window
The Site parameters are classified in the following families:

Identification
site Name
bts site Manager
tei Bts Site Manager
Radio Site Name
Template
Comment

411--9001--137
Config
administrativeState
BTSSM Version
Configuration
model Id
BTS PRODUCT
CBCF
configRef
COUPLING SYSTEM
DUAL BAND SYSTEM
MAX CONFIGURATION
NB OF CABINETS
Attenuation
cpueNumber
siteGsmFctList
Alarms & Optional equipments
external alarm configuration
additional unmasked users alarms
external battery cabinet
lightning protection
smoke detector
TFH or RWM
VSWR meter
GSM--R
additional supervised PCM
unmasked user alarms
Interface
BTS PCM administrativeState
BTS PCM
cRC
redundant Pcm Presence
pcm Time Slot Number

Radio Site Mask

Radio Site Mask Offset
Lapd Signaling
lapd Link
Coordinates
Label
Direction Lat
Min Lat
Sec Lat
DegLat
Direction Lon
Deg Lon
Min Lon
Sec Lon
Comment
HW & SW
software reference
hardware reference

411--9001--137
3.2.1.11 Cell editor
The Cell editor (see the following figure) opens when the user selects a cell object.
Figure 3--47 CELL editor window

The cell parameters are classified in the following families:

The Cell template parameters are classified in the following families:
Identification
cell Name
bts
cell identity
location Area Code
routingArea
base Colour Code
network Color Code
standardIndicator
plmPermitted
gprsPermittedAccess
TEMPLATE
Comment
Config
administrativeState
MAPPING MODEL
bcch Frequency

411--9001--137
cell Allocation
bts ls Hopping
bts Hop Reconf Restart
bts Threshold Hop Reconf
Data14_4OnNoHoppingTs
concentric cell
abis Spy
BTS with Cavity
cell DTx Down Link
diversity
early classmark sending
error concealment unit
interferer cancel algo usage
power Control Indicator
sms CB
unknown N Cell Warning
btsLockedReserved2
btsReserved3
btsReserved4
Algo&protocol
cell Deletion Count
Dtx Mode
pcmErrorCorrection
rad Res Supervision
rnd Acc Tim Adv Threshold
run Call Clear
speech Mode
GPRS
bsCvMax
btsSensitivity

drxTimerMax
gprsAvgParam
gprsBtsExtendedConf
gprsBtsLockExtendedConf
gprsCellActivation
gprsTimerWaitPUAM
gprsTimerWaitRLC
maxRACH
pan
t3122
silverAgprsBandSwidtch
bronzeAgprsBandSwidtch
HO
bts time between HO configuration
cell Type
directedRetryModeUsed
directedRetryPrio
hoMarginBeg
ho Traffic
inter BSC Directed Retry From Cell
intra BSC Directed Retry From Cell
intra Cell Queueing
ms TX Pwr Max
run Handover
Measurement
multi band reporting
uplinkMappingChannelNumber
uplinkMappingFreq
uplinkMappingMeasurementMode
Paging
delay Between Retrans
max number Retransmission

411--9001--137
nb Of Reapeat
no Of Blocks For Access Grant
no Of Multiframes Between Paging
number Of Slots Spread Trans
paging On Cell
retrans Duration
Pwr Ctl & Selection
bs Ms mt Processing Mode
call Clearing
cell Reselect Hysteresis
cell Reselect Offset
cell Resel Ind
msTxPwrMax2ndBand
ms TX Pwr Max CCH
new power control algorithm
penalty Time
run Pwr Control
rx Lev Access Min
temporary Offset
Ressource Allocation
access Class Congestion

all Other Cases Priority

alloc Priority Table
alloc Priority Threshold
alloc Priority Timers
alloc Wait Threshold
answer Paging Priority
assign Request Priority
bts Ms Access Class Barring Function
call Reestablishment
call Reestablishment Priority
cell Bar Qualify
cell Barred
emergency Call
emergency Call Priority
iMSI Attach Detach
inter Cell HO Ext Priority
inter Cell HO Int Priority
intra Cell HO Int Priority
min Nb of TDMA
not Allowed Access Classes
number Of TCH Free Before Congestion
number Of TCH Queued Before Congestion
number Of TCH Free To End Congestion
number Of TCH Queued To End Congestion
other services Priority
radio Link Time Out
rlf1
rlf2
rlf3
rtf3
Timers
timer Periodic Update MS

411--9001--137
t3101
t3103
t3107
t3109
t3111
3.2.1.12 HOV editor
The HOV editor (see the following figure) opens when the user selects a HOV
object.
Figure 3--48 HOV editor window
The HOV parameters are classified in the following families:

Identification
templateName
templateVersion
contextCode
Distance--Level--Quality
dist Hreqt
dist Wts List
miss Dist Wt
miss Rx Lev Wt
miss Rx Qual Wt

ms Range Max
rx Lev Hreqave
rxLevHredaveBeg
rx Lev Hreqt
rx Lev Wts List
rx NCell Hreqave
rx QUAL Hreqave
rx QUAL Hreqt
rx QUAL Wts List
HO
Handover from signalling channel
lRx Qual DLH
lRX Qual ULH
ms Bts Distance Inter Cell
power Budget Inter Cell
rxLevNCellHreqaveBeg
concent Algo Ext Ms Range
concent Algo Ext Rx Lev
concent Algo Int Ms Range
concent Algo Int Rx Lev
lRx Lev DLH
lRX Lev ULH
intra Cell
intra Cell SDCCH
rx Lev DLIH
rx Lev ULIH
rxQualDLIH
rxQualULIH
Interference
averaging Period
rad Chan Set Int Threshold
threshold Interference

411--9001--137
Other features
incoming Handover
small to large zone HO priority
bi zone Power Offset
3.2.1.13 PWC editor
The PWC editor (see the following figure) opens when the user selects a PWC
object.
Figure 3--49 PWC editor window
The PWC parameters are classified in the following families:

Identification
Template
Comment
AMR
power Incr Step Size
power Red Step Size
GPRS Qos
dwQoScriterion
upQoSCriterion
admissionCtrlGold

admissionCtrlSilver
admissionCtrlBronze
peakThroughputLimitation
minThroughputGold
minThroughputSilver
minThroughputBronze
preemptionRatioGold
preemptionRatioSilver
voicePreemptionGold
voicePreemptionSilver
voicePreemptionBronze
Power Control
bs Power Control
bs Tx Pwr Max
uplink Power Control
IRx Lev DLP
uRx Lev DLP
lRx Lev ULP
uRx Lev ULP
IRx Qual DLP
uRx Qual DLP
IRx Qual ULP
uRx Qual ULP
UMTS interworking
umtsAccessMinLevel
umtsReselectionARFCN
umtsReselectionOffset
umtsSearchMinLevel

411--9001--137
3.2.1.14 TRX editor
The TRX editor (see the following figure) opens when the user selects a TRX
object.
Figure 3--50 TRX editor window
The TRX parameters are classified in the following families:

Identification
transceiverEquipment
TEMPLATE
Comment
Config
administrativeState
teiTransceiverEqpt
hardware configuration
transceiver equipment class
Lapd Signaling
OML lapdLink
RSL lapdLink
HW & SW

software reference
hardware reference
3.2.1.15 TDMA editor
The TDMA editor (see the following figure) opens when the user selects a TDMA
object.
Figure 3--51 TDMA editor window
The TDMA parameters are classified in the following families:

Identification
transceiver
template
comment
Config
powerClass
traffic PCM allocation priority
transceiver zone Ref
txPwrMaxreduction
Frequency Hopping
hoppingSequenceNumberTs0

411--9001--137
maioTs0
maioTs1
maioTs2
maioTs3
maioTs4
maioTs5
maioTs6
maioTs7
Frequency Lists
Freq List 0
Freq List 1
Freq List 2
Freq List 3
Freq List 4
Freq List 5
Freq List 6
Freq List 7
GPRS
allocBitmap
codingScheme
dLPwrValue
gprsTranscvLockExtendedConf
packetAckTime

3.2.1.16 TSZ editor
The TSZ editor (see the following figure) opens when the user selects a TSZ object.
Figure 3--52 TSZ editor window
The TSZ parameters are classified in the following families:

Config
TEMPLATE
transceiver equipment class
Identification
Comment
Zone
TransceiverZoneType
zone frequency hopping
zone frequency threshold
zone Tx power max reduction

411--9001--137
3.2.1.17 NEI object editor
The NEI object editor (see the following figure) opens when the user selects a NEI
set object.
Figure 3--53 NEI object editor window
The NEI parameters are classified in the following families:

Identification
adjacentCellHOIdInfo
adjacentCellRESIdInfo
MobileCountryCode
mobileNetworkCode
Network Colour Code
location Area Code
cell Identity
baseColourCode
bcch Frequency
TEMPLATE
Comment
Config
NEIGHBOUR TYPE
No Reciprocity Wanted

HO
cell Type
forced handover algo
hoCombinaison
HOPingpongTimeRejection
ho Margin
ho Margin Dist
ho Margin Rx Lev
ho Margin Rx Qual
micro Cell Capture Timer
micro Cell Stability
hoMarginTrafficOffset
ms TX Pwr Max Cell
rxLevDLPBGT
rx Lev Min Cell
synchronised
preSynchroTimingAdvance
PREFERED UMBRELLA
bizone Power Offset
directed Retry
offsetLoad
offsetPriority
adjCHOReserved3
adjCHOReserved4

411--9001--137
3.2.1.18 Neighboring editor
The Neighboring editor (see the following figure) opens when the user selects a
NEI object.
Figure 3--54 Neighboring editor window
This windows is composed of three parts.
Function buttons
Identification button
The button allows you to choose parameters that you would like
to see for each list.

The following window opens when the user clicks on this button.
The following parameters can be chosen to display the serving cells:

Cell name
Cell Id
BCCH
LAC
BCC
MNC
MCC
Standard Indicator
BTS
By default, all parameters are selected.
The button is used to validate modifications.
The button is used to return to the Neighboring editor without

validating the modifications.
Default template button
The button displays a dialog where the user can assign the default
neighboring link template used during the creation of any link. A different default
template is assigned according to:
the serving cell standard indicator
the target cell standard indicator

411--9001--137
The user has the possibility of choosing a specific default NEL template for each
of the following cases:
GSM to GSM
GSM to DCS
DCS to GSM
DCS to DCS
Extended GSM to Extended GSM
GSM--R to GSM--R
PCS to PCS
E--GSM to E--GSM
PCS 1900 to PCS 1900
Update Reciprocity button
The button creates missing reciprocity links on the neighbouring

plan including all listed serving cells, except a link having a not reciprocal wanted
flag.
Parameters of created neighboring objects are filled in with default templates.
Default templates are previously declared using the Default templates button.
Serving Cell List
The serving cell list is initialized with the active set or an NEL. This list contains
the list of serving cells of the current alternative.
A double click sets the serving cell, drags and drops to the neighboring list to add
a new neighboring link.

Current Serving Cell
The current Serving Cell (see the previous figure) is divided into the following
parts:
Current Serving Cell
This list contains the parameters defined with the Identification window.
The yellow area, located here above the LAC column (see the previous figure),
opens the Generic Editor for the current serving cell. This area is enabled only if
the object is already saved in the Database.
NEI
The parameters showed for each NEI are, in the order:
Cell Name
Cell Id
Bcch Frequency
Location Area Code
Mobile Network Code
Mobile Country Code
Standard Indicator
BTS

411--9001--137
Out Status & Inc Status

Characteristics of neighbor cell
Column A: Checked if it is an alien cell
Column T: Type of cell (N = Normal, M = Micro, U = Umbrella)
Column R: Checked if the Non Reciprocity Wanted flag is set
OUTGOING & INCOMING
The yellow button opens the Generic Editor for the selected Neighbor object.
The template name of the relative Neighbor object.
The HO and RES check marks allow to modify the kind of the neighboring
link (only HO, only RES, or HO + RES).
Action buttons
Refresh button
The button performs an update of the current serving cell and its
neighboring links; this button erases all modifications (return to the loaded
configuration).
Quit button
The button allows you to quit the Neighboring Editor.

The following window opens if some of the modifications have not been saved.
The Yes button validates the modifications.

The No button allows you to quit the Neighboring editor without validating the
modifications.
The Cancel button allows you to return to the Neighboring Editor.

Apply button
The button opens a window (see the following figure) that contains
a list of all the last modifications to be saved.
The grid, inside the Operation List window, contains the last modifications made
to the neighbor plans of all the serving cells.
The information items are:
the operation type
the serving cell
the Nei object
the Nei type
The button validates all the modifications that are saved in the
Database.
The button returns to the Neighboring editor without validating the

change.

411--9001--137
3.2.2 Template editor

The template editor allows the user to consult, clone, create from scratch templates
and to modify all the attributes of each template instance.

There are different ways to run the Template Editor. You can:
Select a template associated with an object in the Template TV Tree (see the
previous figure) and click twice on it.
Select a template associated with an object in the Template TV Tree and click
twice on the button.
Select a template associated with an object in the Template TV Tree and select
the Generic Editor command from the right button of your mouse.
The following commands are available (see the following figure):
Clone Template
Generic Editor
In all these cases, one of the following Template Editor windows opens.
Note: The global design of the following template editors is based on the Object
editor architecture.
The Clone Template command (see the previous figure) is used to clone the
selected template.
From the Network object, the following commands are available (see the following
figure):
Create Template
Generic Editor
Mapping Editor
TDMA Editor
See Paragraph 3.1.2.2 for explanations concerning the global design of the template
window.

411--9001--137
3.2.2.1 Network Template editor
Figure 3--55 Network template editor window
The Network template parameters are classified in the following families:

CellNameRule
CrossConnect Chains
DefaultnReservedBitForRSM
DefaultOmcVersion
DefaultPCMA0Mask
DefaultPCMA1Mask
DefaultPCMA2Mask
DefaultPCMA3Mask
DefaultPcmKind
DefaultRSMModeCompute
DMSPresent
MCCMNCToBsc
Cyphering
NbPCMAPerTCU
MobileCountryCode

MobileNetworkCode
networkId
networlName
primBand
SDOXtpldAlgo
secBand
ServingBCCHInReselection
SS7IdMethod
DefaultAbisMask
TCBHardwareRef
TCBSoftwareRef
TCULapdTerminalNumber
templateAINT
templateBSC
templateCELL
templateHOV
template NEI
template OMC
template PCU
DefaultBscArchitecture
template PCUSN
template PWC
template SITE
template TCU
template TDMA
template TRX
template TSZ
TRXHardwareRef
DefaultBscMniVersion
DefaultBscType
DefaultBSMMiVersion
DefaultLanguage
DefaultMicroCellAlgorithm

411--9001--137
Config
MAPPING MODEL
plmn permitted
Identification
Comment
network Colour Code
3.2.2.2 OMC template editor
Figure 3--56 OMC template editor window
The OMC template parameters are classified in the following families:

Identification
templateName
templateVersion
context code

Config
Architecture
version
Language
Algo&protocol
AlgoA
MICRO ALGO TYPE
SS7 Protocol
Feature Flags
ASCIMode
cellTiering
GPRS
3.2.2.3 PCU template editor
Figure 3--57 PCU template editor window
The PCU template parameters are classified in the following families:

Identification
templateName
templateVersion

411--9001--137
contextCode
Config
GprsPcuLockExtendedConf
AgprsMinTimeAfterUp
cRC
3.2.2.4 BSC template editor
Figure 3--58 BSC template editor window
The BSC template parameters are classified in the following families:

Identification
templateName
templateVersion
contextCode
Config
bsc Version
xSCB Configuration
portChosen
bsc Alarm Mask
bscCounterList
Features

bsc Hop Reconf Use

bscGprsActivation
bsc Ms Acces class Barring Function
bscCapacityReduction
processor Load Sup Conf
encryption Algor Supported
lcsType
uplinkMappingProcessingMode
HO
bss Map Tchoke
HO Second Best Cell Configuration
time Between HO Configuration
ho Traffic
inter Bsc Directed Retry
intra Bsc Directed Retry
mode Modify Mandatory
Network addresses
ProtocolUsed
X25VIaA interface
Timers
bss Map T1
bss Map T4
bss Map T7
bss Map T8
bss Map T12
bss Map T13
bss Map T19
bss Map T20
rad Res Sup Busy Timer
rad Res Sup Free Timer

411--9001--137
3.2.2.5 Site template editor
Figure 3--59 SITE template editor window
The Site template parameters are classified in the following families:

Identification
templateName
templateVersion
contextCode
Config
cpueNumber
siteGsmFctList
Alarms & Optional equipments
external alarm configuration
Interface
cRC
Radio Site Mask Offset

3.2.2.6 Cell template editor
Figure 3--60 CELL template editor window
The Cell template parameters are classified in the following families:

Identification
templateName
templateVersion
contextCode

411--9001--137
Config
bts ls Hopping
bts Hop Reconf Restart
bts Threshold Hop Reconf
Data14_4OnNoHoppingTs
concentric cell
abis Spy
cell DTx Down Link
diversity
early classmark sending
error concealment unit
interferer cancel algo usage
power Control Indicator
sms CB
unknown N Cell Warning
btsLockedReserved2
btsReserved3
btsReserved4
Algo&protocol
amrAdaptationSet
cell Deletion Count
Dtx Mode
extended Cell
ferThreshold
hrCellLoadEnd
hrCellLoadStart
nbOFramesForFer
pcmErrorCorrection
rad Res Supervision
rnd Acc Tim Adv Threshold
run Call Clear
speech Mode
GPRS

bsCvMax
btsSensitivity
drxTimerMax
gprsAvgParam
gprsBtsExtendedConf
gprsBtsLockExtendedConf
gprsCellActivation
gprsTimerWaitPUAM
gprsTimerWaitRLC
maxRACH
pan
t3122
silverAgprsBandSwidtch
bronzeAgprsBandSwidtch
HO
bts time between HO configuration
cell Type
directedRetryModeUsed
directedRetryPrio
hoMarginBeg
ho Traffic
inter BSC Directed Retry From Cell
intra BSC Directed Retry From Cell
intra Cell Queueing
micro Cell inStability timer
ms TX Pwr Max
NCHPosition
pBGTerNeighDistributionActivation
run Handover
rxLevRxQualDistributionActivation
rxQualThresholdDistribution

411--9001--137
selfAdaptationActivation
Measurement
measurementProcAlgorithm
multi band reporting
uplinkMappingChannelNumber
uplinkMappingFreq
uplinkMappingMeasurementMode
Paging
delay Between Retrans
max number Retransmission
nb Of Reapeat
no Of Blocks For Access Grant
no Of Multiframes Between Paging
number Of Slots Spread Trans
paging On Cell
retrans Duration
Pwr Ctl & Selection
bs Ms mt Processing Mode
call Clearing
cell Reselect Hysteresis
cell Reselect Offset
cell Resel Ind
msTxPwrMax2ndBand
ms TX Pwr Max CCH
new power control algorithm
penalty Time
run Pwr Control
rx Lev Access Min
temporary Offset
Ressource Allocation
access Class Congestion

all Other Cases Priority

alloc Priority Table
alloc Priority Threshold
alloc Priority Timers
alloc Wait Threshold
answer Paging Priority
assign Request Priority
bts Ms Access Class Barring Function
call Reestablishment
call Reestablishment Priority
cell Bar Qualify
cell Barred
emergency Call
emergency Call Priority
iMSI Attach Detach
inter Cell HO Ext Priority
inter Cell HO Int Priority
intra Cell HO Int Priority
min Nb of TDMA
not Allowed Access Classes
number Of TCH Free Before Congestion
number Of TCH Queued Before Congestion
number Of TCH Free To End Congestion
number Of TCH Queued To End Congestion
other services Priority
radio Link Time Out
rlf1
rlf2
rlf3
rtf3
Timers
timer Periodic Update MS

411--9001--137
t3101
t3103
t3107
t3109
t3111
3.2.2.7 HOV template editor
Figure 3--61 HOV template editor window
The HOV template parameters are classified in the following families:

Identification
templateName
templateVersion
contextCode
AMR
amrDirectAllocIntRxLevDL
amrDirectAllocIntRxLevUL
amrDirectAllocRxLevDL
amrDirectAllocRxLevUL
amrFRintercellCodecMode

amrFRintracellCodecMode
amrHRintercellCodecMode
amrHRTofFRintrarcellCodecMode
amriRxLevDLH
amriRxLevULH
amrReserved1
nCapacityFrRequestedCodec
nFRRequestedCodec
nHRRequestedCodec
pRequestedCodec
Distance--Level--Quality
dist Hreqt
dist Wts List
miss Dist Wt
miss Rx Lev Wt
miss Rx Qual Wt
ms Range Max
rx Lev Hreqave
rxLevHredaveBeg
rx Lev Hreqt
rx Lev Wts List
rx NCell Hreqave
rx QUAL Hreqave
rx QUAL Hreqt
rx QUAL Wts List
HO
Handover from signalling channel
lRx Qual DLH
lRX Qual ULH
ms Bts Distance Inter Cell
power Budget Inter Cell
rxLevNCellHreqaveBeg

411--9001--137
concent Algo Ext Ms Range

concent Algo Ext Rx Lev
concent Algo Int Ms Range
concent Algo Int Rx Lev
lRx Lev DLH
lRX Lev ULH
intra Cell
intra Cell SDCCH
rx Lev DLIH
rx Lev ULIH
rxQualDLIH
rxQualULIH
offsetNeighbouringCell
rxQualAveBeg
servingFactorOffset
Interference
averaging Period
rad Chan Set Int Threshold
threshold Interference
Other features
incoming Handover
small to large zone HO priority
bi zone Power Offset
Cell Tiering Configuration
capacityTimeRejection
minTimeQualityIntracellHO

3.2.2.8 PWC template editor
Figure 3--62 PWC template editor window
The PWC template parameters are classified in the following families:

Identification
templateName
templateVersion
contextCode
AMR
frPowerControlTargetMode
hrPowerControlTargetMode
power Incr Step Size
power Red Step Size
powerIncrStepSizeDownLink
powerRedStepSizeDownLink
powerIncrStepSizeUplink
powerRedStepSizeUpLink
GPRS Qos
dwQoScriterion

411--9001--137
upQoSCriterion
admissionCtrlGold
admissionCtrlSilver
admissionCtrlBronze
peakThroughputLimitation
minThroughputGold
minThroughputSilver
minThroughputBronze
preemptionRatioGold
preemptionRatioSilver
voicePreemptionGold
voicePreemptionSilver
voicePreemptionBronze
Power Control
bs Power Control
bs Tx Pwr Max
uplink Power Control
IRx Lev DLP
uRx Lev DLP
lRx Lev ULP
uRx Lev ULP
IRx Qual DLP
uRx Qual DLP
IRx Qual ULP
uRx Qual ULP
UMTS interworking
umtsAccessMinLevel
umtsReselectionARFCN
umtsReselectionOffset
umtsSearchMinLevel

3.2.2.9 TRX template editor
Figure 3--63 TRX template editor window
The TRX template parameters are classified in the following families:

Identification
templateName
templateVersion
contextCode
Config
hardware configuration

411--9001--137
3.2.2.10 TDMA template editor
Figure 3--64 TDMA template editor window
The TDMA template parameters are classified in the following families:

Identification
templateName
templateVersion
contextCode
Config
powerClass
traffic PCM allocation priority
txPwrMaxReduction
FRAmrPriority
HRAmrPriority
GPRS Parameters
allocBitmap
codingScheme
dLPwrValue
gprsTranscvLockExtendedConf
packetAckTime

3.2.2.11 NEI template editor
Figure 3--65 NEI template editor window
The NEI template parameters are classified in the following families:

Identification
templateName
templateVersion
contextCode
Config
No Reciprocity Wanted
HO
cell Type
micro Cell Capture Timer
forced handover algo
hoCombinaison
HOPingpongTimeRejection
ho Margin
ho Margin AMR
ho Margin Dist
ho Margin Rx Lev

411--9001--137
ho Margin Rx Qual
hoMarginTrafficOffset
ms TX Pwr Max Cell
rxLevDLPBGT
rx Lev Min Cell
preSynchroTimingAdvance
bizone Power Offset
directed Retry
interference Type
offsetLoad
offsetPriority
adjCHOReserved3
adjCHOReserved4
3.2.2.12 AINT template editor
Figure 3--66 AINT template editor window
The AINT template parameters are classified in the following families:

Identification
templateName

templateVersion
contextCode
Config
advancedSpeechCallItems
preemptionConfiguration
Algo&protocol
bsc Queuing Option
speech mode
errorCorrectionMethod
cRC
Messages
circuit Group Block
confusion
cypher Mode Reject
layer3 Msg Cyph Mod Comp
reset Circuit Repeat
unequipped Circuit
SignalingLink
networkIndicator
signalling Point Type
sigPReserved1
sigPReserved2
Speech & Channel
chosen Channel Ass Comp
chosen Channel Comp L3Info
chosen Channel Ho Perf
chosen Channel Ho Req
currentChannelHorqd
encryp Algo Ass Comp
encryp Algo Ciph Mod Comp

411--9001--137
encryp Algo Ho Perf

encryp Algo Ho Req
speechVersionAsscomp
speechVersionHoperf
speechVersionHoreq
speechVersionHorqd
Timers
bss Sccp ConnEst
bss Sccp Inact Rx
bss Sccp Inact Tx
bss Sccp Release
bss Sccp Sub Sys Test
3.2.2.13 TCU template editor
Figure 3--67 TCU template editor window
The TCU template parameters are classified in the following families:

Identification
templateName
templateVersion
contextCode

Config
transcoderAlarmMask
Algo&protocol
algo Id
CoderPoolConfiguration
data mode 14.4 kbit/s
PCM links
cRC
3.2.2.14 TSZ template editor
Figure 3--68 TSZ template editor window
The TSZ template parameters are classified in the following families:

Identification
templateName
templateVersion
contextCode
Zone
zone frequency hopping
zone frequency threshold

411--9001--137
zone Tx power max reduction
3.2.2.15 PCUSN template editor

The PCUSN template parameters are classified in the following families:
The PCUSN template parameters are classified in the following families:

Identification
templateName
templateVersion
Contextcode
Config
pcuSNReserved1
pcuSNreserved2
3.2.3 Network checker

The Network Checker enables you to run different tests which check the coherency
of the CT2000 database from an OMC--R point of view.
The user can specify his own checks and families of checks. The network Checker
detects errors and can in some situations apply an auto--correction. These
corrections are based on engineering rules.
CT2000 offers consistency checks according to engineering rules on the whole
network:
Neighborhood,

Operation Data Base,

Engineering,
To run the network checker, use one of the following selections:
In the CT2000 Main window (see Figure 3--1), select
Configuration --> Network Checker.
In the Menu window (see Figure 3--34), click on the Network checker icon
(see Paragraph 3.1.5.2).
In the Tool Bar (see Paragraph 3.1.3), click on the icon (the fifth from the
left).
The Network Checker menu opens (see Figure 3--14).
Refer to Paragraph 3.1.2.4 for explanations concerning the Network Checker
window.

411--9001--137

Nortel Networks Confidential Index i
A
A Interface management plug--in, 1--29
About..., 3--84
Aint editor, 3--109
AINT template editor, 3--158
Alternative editor, 3--99
B
BSC editor, 3--105
BSC template editor, 3--142
BSS object editor, 1--14
C
Cell editor, 3--114
Cell template editor, 3--145
Check Profile copy, 3--55
Check Profile creation, 3--51
Check Profile Edition, 3--49
Check Profile modification, 3--54
Class 2 modification plug--in , 1--27
Configuration menu, 3--43
CT Import, 3--30
CT2000 architecture, 1--4
CT2000 general presentation, 1--1
CT2000 interfaces, 1--17
CT2000 Main Window, 3--1
CTSDOs Export, 3--32
D
Data base export, 1--15
Data Request Forms , 1--19
Database DRF loader, 1--12
Database network checker, 1--14
Datafill Rule, 3--56
Datafill Rules Profile copy, 3--67
Datafill Rules Profile creation, 3--63

ii Index Nortel Networks Confidential
Datafill Rules Profile edition, 3--61

Datafill Rules Profile modification, 3--66
DRFs Export, 3--26
DRFs Import, 3--21
E
Edition menu, 3--68
G
Generation of command files, 1--16
Global Update, 3--44
H
Hardware, 1--6
Hierarchical TV, 3--74
HOV editor, 3--120
HOV template editor, 3--150
I
Installation, 2--1
Interfaces menu, 3--20
L
Log session, 3--69
M
mapping model, 1--12
Mapping Models, 1--22
Menu area, 3--89
Menu bar, 3--2
MenuBar, 3--81
MSC editor, 3--104
N
NEI object editor, 3--128

411--9001--137
Nortel Networks Confidential Index iii
NEI template editor, 3--157

Neighboring editor, 1--14 , 3--130
Network checker, 3--45 , 3--162
Network editor, 1--12
Network Editor--Default, 3--5
Network Element List, 3--71
Network element list, 1--12
Network Setting menu, 3--5
Network Template editor, 3--138
Network Tree, 3--72 , 3--89
NRP input files, 1--16
NRP/Command File generation plug--in, 1--27
O
Object Editor, 3--98
ODB retrieve plug--in, 1--27
OMC template editor, 3--140
OMC--implementation part, 1--4
OMC--R command files, 1--16
OMC--R plug--ins , 1--26
Operation traces, 3--82
Operation traces area, 3--96
P
PC--client engineering part, 1--4
PCU editor, 3--102
PCU template editor, 3--141
PCUSN editor, 3--103
Preference menu, 3--3
Product definition, 1--1
Product overview, 1--1
PWC editor, 3--122
PWC template editor, 3--153
Q
Quitting the CT2000, 2--26
R
Rules session Log, 3--70

iv Index Nortel Networks Confidential
S
Site editor, 3--111
Site template editor, 3--144
Starting the CT2000, 2--23
Status bar, 3--97
StatusBar, 3--84
T
TCU editor, 3--107
TCU template editor, 3--160
TDMA editor, 3--125
TDMA frame, 1--12
TDMA template editor, 3--156
Template, 3--34
Template editor, 3--136
Template management, 1--11
Template TV, 3--76
Templates , 1--20
Title bar, 3--2
ToolBar, 3--84 , 3--87
Topological TV, 3--75
TRX editor, 3--124
TRX template editor, 3--155
TSZ editor, 3--127
TSZ template editor, 3--161
U
Uninstalling the CT2000, 2--27
V
View menu, 3--84
W
Window menu, 3--83
Workspace, 3--96
WorkSpace menu, 3--80

411--9001--137
Copyright 2001--2004 Nortel Networks, All Rights Reserved
NORTEL NETWORKS CONFIDENTIAL:
The information contained in this document is the property of Nortel

Networks. Except as specifically authorized in writing by Nortel
Networks, the holder of this document shall keep the information
contained herein confidential and shall protect same in whole or in part
from disclosure and dissemination to third parties and use for evaluation,
operation and maintenance purposes only.
For more information, please contact:
You may not reproduce, represent, or download through any means, the
information contained herein in any way or in any form without prior
For all countries, except USA:
written consent of Nortel Networks.
The following are trademarks of Nortel Networks: *NORTEL Documentation Department
NETWORKS, the NORTEL NETWORKS corporate logo, the NORTEL Parc dactivit de Magny--Chateaufort
Globemark, S2000, S4000, S12000. CHATEAUFORT
GSM is a trademark of France Telecom. 78928 YVELINES CEDEX 9
Sybase is a registered trademark of Sybase, Inc. FRANCE
Windows is a U.S. registered trademark of Microsoft Corp. Email : umts--gsm.ntp@nortelnetworks.com
All other brand and product names are trademarks or registered Fax : (33) (1) 39--44--50--29
trademarks of their respective holders.
In the USA:
Publication Reference
PE/DCL/DD/0137 411--9001--137 2221 Lakeside Boulevard
14.12/EN Richardson TX 75082
July 2004 USA
Originated in France Tel: 1--800--4 NORTEL
1--800--466--7838 or (972) 684--5935
Internet Address:
http://www.nortelnetworks.com

CT2K User Manual

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

CT2K User Manual

Caricato da

Copyright:

Formati disponibili

Wireless Service Provider Solutions

CT2000 User Reference Manual

Wireless Service Provider Solutions

Copyright 2001--2004 Nortel Networks, All Rights Reserved

NORTEL NETWORKS CONFIDENTIAL:

System release: GSM/BSS V14.3

Copyright E 2001--2004 Nortel Networks CT2000 User Reference Manual

The following changes were made:

PE/DCL/DD/0137 Standard 14.12/EN July 2004 Copyright E 2001--2004 Nortel Networks

Update in paragraph 3.2.1.8 PWC template editor

Copyright E 2001--2004 Nortel Networks CT2000 User Reference Manual

3.2.2.8 PWC template editor

PE/DCL/DD/0137 Standard 14.12/EN July 2004 Copyright E 2001--2004 Nortel Networks

Chapter 2 CT2000 basics

System release: GSM/BSS V13

Copyright E 2001--2004 Nortel Networks CT2000 User Reference Manual

General Availability of the BSS system release V13.02/V12.4

PE/DCL/DD/0137 Standard 14.12/EN July 2004 Copyright E 2001--2004 Nortel Networks

System release: GSM/BSS V12

Copyright E 2001--2004 Nortel Networks CT2000 User Reference Manual

About this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 0-- 1

1 CT2000 general presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-- 1

PE/DCL/DD/0137 Standard 14.12/EN July 2004 Copyright E 2001--2004 Nortel Networks

1.5.4 CT2000 to CT2000 OMC--R plug--ins . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1--26

2 CT2000 basics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2--1

3 CT2000 PC-- Part Main Human Machine Interface . . . . . . . . . . . . . 3--1

Copyright E 2001--2004 Nortel Networks CT2000 User Reference Manual

Figure 1--1 CT2000 position in an operator network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1--2

PE/DCL/DD/0137 Standard 14.12/EN July 2004 Copyright E 2001--2004 Nortel Networks

Figure 3--26 Datafill Rules -- Modify window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--67

Copyright E 2001--2004 Nortel Networks CT2000 User Reference Manual

Figure 3--61 HOV template editor window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3--151

PE/DCL/DD/0137 Standard 14.12/EN July 2004 Copyright E 2001--2004 Nortel Networks

Table 1--1 DRF Files and modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1--13

Copyright E 2001--2004 Nortel Networks CT2000 User Reference Manual

PE/DCL/DD/0137 Standard 14.12/EN July 2004 Copyright E 2001--2004 Nortel Networks

ABOUT THIS DOCUMENT

How this document is organized

Copyright E 2001--2004 Nortel Networks CT2000 User Reference Manual

PE/DCL/DD/0137 Standard 14.12/EN July 2004 Copyright E 2001--2004 Nortel Networks

Copyright E 2001--2004 Nortel Networks CT2000 User Reference Manual

SICD Serial Interface Controller LapD Protocol

PE/DCL/DD/0137 Standard 14.12/EN July 2004 Copyright E 2001--2004 Nortel Networks

Copyright E 2001--2004 Nortel Networks CT2000 User Reference Manual

PAGE INTENTIONALLY LEFT BLANK

PE/DCL/DD/0137 Standard 14.12/EN July 2004 Copyright E 2001--2004 Nortel Networks

1 CT2000 GENERAL PRESENTATION

1.1 Product overview

1.2 Product definition

Copyright E 2001--2004 Nortel Networks CT2000 User Reference Manual

Figure 1--1 CT2000 position in an operator network

PE/DCL/DD/0137 Standard 14.12/EN July 2004 Copyright E 2001--2004 Nortel Networks

Customer BSS Network

CT--SDO NRP &

Figure 1--2 Input/Output data of the CT2000 -- Functional view

Copyright E 2001--2004 Nortel Networks CT2000 User Reference Manual

1.3 CT2000 architecture

1.3.1 General architecture

1.3.1.1 PC--client engineering part

1.3.1.2 OMC--implementation part

PE/DCL/DD/0137 Standard 14.12/EN July 2004 Copyright E 2001--2004 Nortel Networks

OMC--R Unix station DATA EXP CT2000

CMD file Class 2

Figure 1--3 CT2000 general architecture