411-0930-001 12 03

Course 930
GSM
DMS-MSC/HLR
Student Guide
GSM12 Standard 12.03 February 2001

GSM
DMS-MSC/HLR
Student Guide
Course number: Course 930

Product release: GSM12
Document version: Standard 12.03
Date: February 2001
Copyright Country of printing Confidentiality Legal statements Trademarks
Copyright  1996–2001 Nortel Networks, All Rights Reserved

Printed in the United States of America
NORTEL NETWORKS CONFIDENTIAL

The information contained herein is the property of Nortel Networks and is strictly confidential. Except as expressly authorized in
writing by Nortel Networks, the holder shall keep all information contained herein confidential, shall disclose it only to its employees
with a need to know, and shall protect it, in whole or in part, from disclosure and dissemination to third parties with the same degree
of care it uses to protect its own confidential information, but with no less than reasonable care. Except as expressly authorized in
writing by Nortel Networks, the holder is granted no rights to use the information contained herein.
Information is subject to change without notice. Nortel Networks reserves the right to make changes in design or components as
progress in engineering and manufacturing may warrant.
Trademarks are acknowledged with an asterisk (*) at their first appearance in the document.
Nortel Networks Confidential v
Publication history
July 1999 0
Issue 08.01
• This issue is in accordance with the Nortel templates and incorporates
review comments.
• It contains information up to release GSM10.
December 1999 0
Issue 10.03
review comments.
• This issue is the standard version after reviews. It contains information up
to release GSM10.
December 2000 0
Issue 12.02
review comments.
• This issue is the standard version after reviews. It contains information up
to release GSM12.
February 2001 0
Issue 12.03
• This issue is the standard version after additional review comments have
been incorporated. It contains information up through release GSM12.
GSM GSM DMS Overview Student Guide GSM12

vi Publication history Nortel Networks Confidential
Course 930 Standard 12.03 February 2001 For training purposes only
Nortel Networks Confidential vii
Contents 1
About this course xvii
Course objectives xvii
NSS training curriculum xviii
IntraNet address xix
GSM DMS engineer (beginner) xix
GSM DMS engineer (expert) xix
GSM MSC/VLR datafill engineer xx
GSM HLR datafill engineer xx
GSM subscriber service provisioning engineer xxi
Additional GSM NSS application courses xxii
Lesson 1
Introduction 1-1
Objectives 1-1
Basic telecommunications concepts 1-3
Switching system evolution 1-4
Analog signals and digital concepts 1-6
PCM concept 1-7
Sampling 1-8
Quantization 1-8
Coding 1-10
Nortel switching systems 1-12
Nortel DMS SuperNode 1-13
Public applications 1-13
GSM applications 1-14
DMS-MSC functions 1-15
DMS-MSC mobile call handling 1-15
DMS-MSC mobile voice call handling 1-15
DMS-MSC mobile data call handling 1-15
DMS-MSC emergency call handling 1-16
DMS-MSC supplementary services 1-16
DMS-MSC enhanced services 1-17
Intelligent Network (IN) 1-17
DMS-MSC external interfaces 1-17
DMS-MSC gateway function 1-19
DMS-MSC support of Primary Rate Interface (PRI) 1-20
DMS-HLR functions 1-20
DMS-MSC/HLR functions 1-21

viii Contents Nortel Networks Confidential
Lesson 2
GSM DMS overview 2-1
Objectives 2-1
DMS 2-2
DMS family attributes 2-2
Distributed processing 2-2
Stored program control 2-2
Digital network 2-2
Trunk input 2-3
DMS-MSC hardware architecture 2-4
Service processing hardware layer 2-4
Messaging and connectivity hardware layer 2-5
Physical access hardware layer 2-5
Functional hardware layers 2-5
Service processing hardware 2-5
Messaging and connectivity hardware 2-5
Physical access hardware 2-5
Duplication for reliability 2-6
DMS-Core 2-7
DMS-Core functions 2-8
System Load Module (SLM) 2-8
File Processor (FP) 2-8
DMS-Bus (or Message Switch) 2-9
Enhanced NETwork (ENET) 2-11
DMS internal speech and message links 2-13
DMS-MSC internal speech links 2-13
DMS-MSC internal message links 2-14
P-side and C-side 2-15
Peripheral Modules (or PMs) 2-16
Input/output Controller (IOC) 2-18
SuperNode Data Manager (SDM) 2-20
Hardware packaging 2-21
GSM DMS architectures 2-22
DMS SuperNodeLineup 2-23
SuperNode Size Enhanced Lineup (SNSE) 2-25
MicroNode lineup 2-27
DMS system limitations 2-28
E1 limitations 2-28
C7 link limitations 2-29
Equipment labelling 2-31
Cards and paddleboards 2-33
Product Engineering Code Identifier (PEC) 2-34
DMS-MSC software architecture overview 2-35
DMS-MSC software structure 2-35
GSM-based product layer and markets 2-36
GSM services 2-37
GSM base 2-37
Shared layer 2-37
Telecom layer 2-37
Nortel Networks Confidential Contents ix
Base layer 2-37
Lesson 3
DMS-Core and DMS-Bus 3-1
Objectives 3-1
DMS-Core 3-2
Computing module 3-3
Control processor 3-3
Memory 3-4
DMS-Bus interfaces 3-4
System Load Module (SLM) 3-5
SLMs 3-5
Interfaces 3-5
DMS-Bus 3-7
MS functional subsystems 3-7
Control processor 3-7
Transaction bus 3-7
Processor bus 3-8
System clock 3-8
MS connectivity 3-9
Operation of DMS hardware components 3-10
Plane 3-10
Operation of the DMS-Core in duplex mode 3-10
Fault recovery of the DMS-Core 3-10
Operation of the DMS-Core in simplex mode 3-10
DMS base cabinets 3-11
SuperNode base cabinet 3-11
SNSE & MicroNode base cabinet 3-13
Office image and journal file 3-14
Office image 3-14
Journal file 3-15
Device Independent Recording Package (DIRP) 3-16
DIRP subsystems 3-17
GSM Call Detail Records (GCDR) 3-17
Journal file 3-17
Operational Measurements (OM) 3-18
DLOG 3-18
Lesson 4
Input/Output Device (IOD) 4-1
Objectives 4-1
Input/Output Devices (IODs) 4-2
Cabinetized Input/Output Equipment (CIOE) 4-3
Device controller cards 4-5
Devices 4-6
Maintenance and Administration Position (MAP) terminal 4-6
Disk drive unit 4-6
Magnetic tape drive 4-8
IOD cards, ports, and circuits 4-9
Input/Output Module (IOM) 4-10

x Contents Nortel Networks Confidential
Lesson 5
Enhanced Network (ENET) 5-1
Objectives 5-1
Enhanced network 5-2
Hardware configuration 5-5
ENET cabinets 5-5
ENET shelf layout 5-8
Control and messaging 5-9
Interface to PMs 5-9
Interface to MS 5-9
PM synchronization 5-9
Shelf communication (V-Bus & H-Bus) 5-10
ENET operation 5-11
ENET crosspoint cards & I/F paddleboards 5-12
ENET switching examples 5-13
Lesson 6
Peripheral Modules (PMs) 6-1
Objectives 6-1
Peripheral modules 6-2
PM network interface 6-4
Voice access PMs 6-5
PCM-30 Digital Trunk Controller (PDTC) 6-6
PDTC to ENET message links 6-8
Digital Trunk Controller ISDN (DTCi) 6-8
Other PMs 6-9
Maintenance Trunk Module (MTM) 6-9
Integrated Service Module (ISM) 6-10
Digital Recorded Announcement Machine (DRAM) 6-13
Enhanced Digital Recorded Announcement Machine (EDRAM) 6-13
Common Channel Signaling # 7 (CCS7) networks 6-14
Link Peripheral Processor (LPP) 6-14
Link Interface Unit #7 (LIU7) 6-17
Mobility management unit (MMU) 6-22
Check out 6-23
Lesson 7
SuperNode Data Manager/Fault Tolerant (SDM/FT) 7-1
Objectives 7-1
SDM/FT cabinet 7-2
SDM/FT overview 7-3
General Description 7-3
Fault tolerant architecture 7-5
SDM/FT main chassis 7-7
OMC-S application overview 7-8
OMC-S software architecture 7-9
OMC-S element manager application 7-10
HLR-PS functionality 7-12
Nortel Networks Confidential Contents xi
Call Intercept System (CIS) 7-14

CIS functions 7-15
CIS architecture 7-15
CIS capacity 7-17
Lesson 8
Using MAP terminal 8-1
Objectives 8-1
Introduction to the Visual Display Unit 8-2
Terminal setup procedures 8-2
Command system tasks 8-4
Syntax conventions 8-5
Keyboard commands 8-6
Editing command lines 8-6
Line editing commands 8-6
Changing output displays 8-7
MAP commands 8-8
Command name: LOGIN 8-8
Command name: LOGOUT 8-8
Command name: QUSER 8-9
Command name: DATE 8-9
Command name: TIME 8-9
Command name: COMMAND 8-10
Command name: MSG 8-12
Command name: SETLOGMSG 8-13
Command name: SHOW USERS 8-13
Command name: PRINT 8-14
Command name: PERMIT 8-15
Command name: UNPERMIT 8-17
Command name: RECORD 8-18
Command name: REPEAT 8-19
Command name: SEND 8-20
CI menu hierarchy 8-21
MAPCI display areas 8-22
MAP Command Interpreter menu level 8-24
Maintenance level menu 8-25
Alarm indicator display 8-26
Command menu display 8-27
MAP level command types 8-28
Entering commands 8-28
Commands from other menus 8-30
Instructions 8-34
Instructions 8-40
Instructions 8-43
Lesson 9
Table editor 9-1
Objectives 9-1
Table editor 9-2
Table and subtable structure 9-5

xii Contents Nortel Networks Confidential
Fields 9-5
Tuples 9-5
Subfields 9-5
Subtables 9-7
Selectors 9-8
Input prompter 9-8
Table editor commands 9-12
Command name: ADD 9-14
Command name: BOTTOM (BOT) 9-14
Command name: CHANGE (CHA) 9-14
Command name: COUNT 9-14
Command name: DELETE (DEL) 9-15
Command name: DOWN (DOW) 9-15
Command name: FORMAT PACK / FORMAT UNPACK 9-16
Command name: HELP 9-16
Command name: LIST (LIS) 9-17
Command name: POSITION (POS) 9-17
Command name: QUIT (QUI) 9-18
Command name: RANGE (RAN) 9-18
Command name: REPLACE (REP) 9-18
Command name: SUBTABLE (SUB) 9-19
Command name: TABLE 9-20
Command name: TOP 9-20
Command name: UP 9-20
Command name: VERIFY (VER) 9-20
Command name: FINDTAB 9-21
Other commands 9-21
Table editor - quick command reference list 9-23
Instructions 9-26
Instructions 9-28
Self check 9-29
Instructions 9-30
Instructions 9-31
Lesson 10
Universal Translations (UXLA) 10-1
Objectives 10-1
DMS-MSC translations 10-2
Stages of translations 10-2
Translations Verification (TRAVER) tool 10-4
Land to MS call 10-5
Lesson 11
Operational measurements & log reports 11-1
Objectives 11-1
Operational Measurements (OMs) and OMSHOW 11-2
Operational Measurement system 11-4
OM register data collection 11-8
Accumulating OM data 11-12
Log reports and LOGUTIL 11-15
Nortel Networks Confidential Contents xiii
Log report system 11-15

Report format 11-19
LOGUTIL 11-21
Functions of LOGUTIL commands 11-21
Lesson 12
NTPs and Helmsman 12-1
Objectives 12-1
NTPs and Helmsman 12-2
NTPs 12-2
DMS-MSC/HLR documentation listing 12-4
Helmsman CD-ROM 12-5
Instructions 12-8
Questions 12-8
Instructions 12-13
Questions 12-13
Lesson 13
DMS-MSC call processing 13-1
Objectives 13-1
Call processing 13-2
Call processing architecture 13-3
PSTN to mobile call progression 13-4
Call progress description 13-5
Glossary A-1
List of figures
Figure 0-1 NSS training curriculum xvi
Figure 1-1 Lines and trunks in a Nortel DMS network 1-3
Figure 1-2 A/D conversion 1-6
Figure 1-3 Steps to produce PCM samples 1-7
Figure 1-4 Quantization 1-9
Figure 1-5 Multiplexing channels 1-10
Figure 1-6 PCM Frame 1-11
Figure 1-7 Typical network using Nortel DMS switch family components 1-12
Figure 1-8 Typical network subsystem 1-19
Figure 2-1 DMS-MSC hardware architecture 2-4
Figure 2-2 Duplications for reliability 2-6
Figure 2-3 DMS-Core 2-7
Figure 2-4 DMS-Bus plane 2-10
Figure 2-5 Network connections 2-12
Figure 2-6 P-Side and C-Side 2-15
Figure 2-7 Typical DMS-MSC PM connections 2-17
Figure 2-8 Input/output controller and devices 2-19
Figure 2-9 SuperNode Data Manager/Fault Tolerant 2-20
Figure 2-10 Hardware packaging 2-21
Figure 2-11 DMS cabinet lineup with DMS SuperNode Base 2-23
Figure 2-12 DMS cabinet lineup with SNSE Base 2-25
Figure 2-13 MicroNode cabinet lineup 2-27

xiv Contents Nortel Networks Confidential
Figure 2-14 C7 link limitations 2-30

Figure 2-15 Equipment labels for 42” cabinet 2-32
Figure 2-16 Cards and paddleboards 2-33
Figure 2-17 DMS-MSC software structure 2-36
Figure 3-1 SuperNode DMS-Core 3-2
Figure 3-2 SuperNode DMS-Bus 3-8
Figure 3-3 Inter-MS link configuration 3-9
Figure 3-4 DPCC Cabinet 3-11
Figure 3-5 DMS SuperNode SE (SNSE) configuration 3-13
Figure 3-6 Office image dump and manual bootstrap load 3-14
Figure 3-7 Journal file 3-15
Figure 3-8 DIRP block diagram 3-17
Figure 4-1 Input/output controller and devices 4-2
Figure 4-2 CIOE cabinet 4-3
Figure 4-3 Input/Output controller 4-4
Figure 4-4 Disk drive unit shelf 4-7
Figure 4-5 Magnetic tape drive 4-8
Figure 4-6 IOC cards, ports, and circuits 4-9
Figure 4-7 ISM shelf and IOM circuit pack 4-11
Figure 5-1 Duplicated switching network 5-2
Figure 5-2 Enhanced network reduces footprint 5-3
Figure 5-3 ENET in system architecture 5-4
Figure 5-4 ENET cabinet for SuperNode (one plane shown) 5-5
Figure 5-5 ENET shelf for SNSE or MicroNode 5-6
Figure 5-6 ENET configurations 5-7
Figure 5-7 ENET shelf layout 5-8
Figure 5-8 Block diagram of ENET architecture 5-10
Figure 5-9 ENET single-stage switch 5-11
Figure 5-10 ENET crosspoint cards & I/F paddleboards 5-12
Figure 5-11 ENET switching example 1 5-13
Figure 5-12 ENET switching example 2 5-14
Figure 6-1 Typical PMs cabinets 6-2
Figure 6-2 PM connections 6-4
Figure 6-3 PDTC dual shelf 6-7
Figure 6-4 PDTC to ENET message links 6-8
Figure 6-5 Integrated Service Module 6-10
Figure 6-6 ISM cabinet & IOM 6-12
Figure 6-7 LPP cabinet 6-15
Figure 6-8 Link Peripheral Processor interconnections 6-16
Figure 6-9 Link Interface Unit 6-17
Figure 6-10 Link interface shelf in a SNSE cabinet 6-18
Figure 6-11 Entering an LIU7 via channelized access 6-20
Figure 6-12 NIU and LIU7 connections in the LPP 6-21
Figure 6-13 MMU functionality 6-22
Figure 6-14 MMU simplified functions. location, and flow 6-23
Figure 6-15 Hardware configuration with MMUs 6-24
Figure 7-1 OAMP platform software 7-2
Figure 7-2 SDM/FT cabinet 7-4
Figure 7-3 SDM-FT architecture 7-5
Figure 7-4 SDM/FT main chassis 7-7
Figure 7-5 OMC-S application overview 7-8
Nortel Networks Confidential Contents xv
Figure 7-6 OMC-S software architecture 7-9

Figure 7-7 Configuration management application 7-10
Figure 7-8 Fault management application 7-11
Figure 7-9 Performance management application 7-12
Figure 7-10 HLR-PS general architecture 7-13
Figure 7-11 Call intercept 7-14
Figure 7-12 CIS architecture 7-16
Figure 8-1 CI level tasks 8-4
Figure 8-2 Explanation of mycommand definition 8-11
Figure 8-3 CI menu hierarchy 8-21
Figure 8-4 MAPCI display areas 8-22
Figure 8-5 MAPCI display 8-24
Figure 8-6 Maintenance MAP display 8-25
Figure 8-7 Command menu display 8-27
Figure 8-8 Command entry 8-29
Figure 9-1 Table editor 9-3
Figure 9-2 Table structure 9-6
Figure 9-3 Accessing subtables 9-7
Figure 9-4 Example MAP display of prompt mode 9-10
Figure 9-5 Example MAP display of nonprompt mode 9-11
Figure 10-1 Translations area processing 10-2
Figure 10-2 DMS-MSC translation picture 10-3
Figure 10-3 TRAVER for MO call 10-4
Figure 10-4 Typical TRAVER output 10-5
Figure 11-1 OM counters and groups 11-3
Figure 11-2 OM peg register monitoring seizure trunks 11-4
Figure 11-3 Monitoring trunk seizure 2/2 11-5
Figure 11-4 High watermark registers 11-6
Figure 11-5 OM example 11-7
Figure 11-6 OM flow showing active, holding, and accumulating registers 11-9
Figure 11-7 OM flow showing active and holding extension registers 11-10
Figure 11-8 Relationship between an OM class, group, and register 11-11
Figure 11-9 OM class, group, and register relationship 11-12
Figure 11-10 Example of OM log 11-14
Figure 11-11 Log buffers in CM memory 11-16
Figure 11-12 Log buffer 11-17
Figure 11-13 Log report example 11-18
Figure 11-14 Report format 11-20
Figure 11-15 LOGUTIL command functions 11-21
Figure 12-1 Components of an NTP number 12-2
Figure 13-1 DMS-MSC call processing architecture 13-3
Figure 13-2 PSTN to mobile call: IAM message 13-5
Figure 13-3 PSTN to mobile call: SRI message 13-6
Figure 13-4 PSTN to mobile call: PRN message 13-7
Figure 13-5 PSTN to mobile call: PRN Ack message 13-8
Figure 13-6 PSTN to mobile call: SRI Ack message 13-9
Figure 13-7 PSTN to mobile call: paging message 13-10

xvi Contents Nortel Networks Confidential
List of tables
Table 2-1 Commonly used GSM peripheral modules 2-16
Table 2-2 DMS architectures 2-22
Table 2-3 PCM limitations 2-28
Table 3-1 SNSE memory card configurations 3-4
Table 3-2 SLM configurations 3-5
Table 6-1 MTM PEC codes to ISM codesTable 6-1 6-11
Table 7-1 SDM-FT parts 7-5
Table 7-2 CIS functions 7-15
Table 8-1 VDU configuration 8-3
Table 8-2 Line editing command functions 8-6
Table 8-3 Changing output display commands 8-7
Table 8-4 Alarm indicator display alarm codes 8-26
Table 9-1 Table editor commands 9-12
Table 11-1 Searching log buffers associated with each subsystem 11-23
Table 12-1 Division and layer number 12-3
Table 12-2 Group number 12-3
Table 12-3 DMS-MSC/HLR documentation 12-4
Nortel Networks Confidential xvii
About this course

This course provides the participant with a basic understanding of the Nortel
Networks Digital Multiplex Switch (DMS). It is an excellent way to become
familiar with DMS switching terminology, components, and concepts, as
used in the GSM network.
Course objectives 0
Upon completion of this course, you will be able to:
• describe basic telecommunication concepts
• describe the basic components of a DMS system
• describe the DMS-Core and DMS-Bus
• describe the Input/Output Devices (IOD)
• describe the Enhanced Network (ENET)
• describe the Peripheral Modules (PM)
• describe the SuperNode products
• use the MAP terminal
• use Table Editor
• describe what translations are and how they work
• describe Operational Measurement (OM) and Log Reports (LOG)
• use LOGUTIL and OMSHOW commands
• explain the Nortel documentation structure
• explain GSM call processing

xviii About this course Nortel Networks Confidential
NSS training curriculum 0

Figure 0-1 illustrates the NSS recommended training paths to acquire skills
for each job.
Figure 0-1
NSS training curriculum
NSS Training Curriculum

931 / 2 Days
GSM NSS Overview
930 / 3 Days
974 / 5 Days
GSM DMS Overview
GSM CCS7 Translations
& Operations Additional GSM Application Courses
950 / 5 Days
GSM DMS 900 / 3 Days 938 / 5 Days
970 / 10 Days
Maintenance Part 1
GSM MSC/VLR GSM Intelligent GSM IWF
Translations Networks
GSM DMS Engineer

Beginner
GSM MSC/VLR
Datafill Engineer
951 / 10 Days
GSM DMS 972 / 5 Days
Maintenance Part 2
GSM HLR
Service & Datafill
955 / 2 Days GSM HLR
Datafill Engineer
SDM/FT Maintenance 935 / 3 Days
& Administration
G S M H L R-P S
937 / 2 Days
O M C -S GSM Subscriber
Overview & Operation Service Provisioning
Engineer
GSM DMS Engineer

Expert
Nortel Networks Confidential About this course xix
IntraNet address 0
http://136.147.68.68/training/index.html
Most of GSM NSS Engineering curricula start with the following overview
course:
• GSM NSS Overview (931/2 days)

• GSM DMS Overview (930/3 days)
The overview course provides the student with a basic understanding of a

GSM Network Switching Subsystem (NSS) and DMS switch.
GSM DMS engineer (beginner)

This training is designed for anyone involved as a team member in the
maintenance of any GSM DMS switch. This training contains the GSM NSS
Overview (931) and the GSM DMS Overview (930) and the following
course:
• GSM DMS Maintenance Part 1 (950/5 days)

The GSM DMS Maintenance Part 1 course provides the generic skills required
to maintain any DMS switch in a GSM network. A particular focus is on:
• PMs (Peripheral Modules)
• IOD (Input/Output Device)
• ISM (Integrated Service Module)
GSM DMS engineer (expert)

This training is designed for anyone, acting as an expert, who performs the
complete maintenance of any GSM DMS switch. This training contains the
GSM NSS Overview (931) and the GSM DMS Overview (930) and the
following courses:

The GSM DMS Maintenance Part 1 course provides the generic skills
required to maintain any DMS switch in a GSM network.

The GSM DMS Maintenance Part 2 course provides the generic skills
required to maintain any DMS switch in a GSM network. A particular
focus is on the DMS core.
• SDM/FT Maintenance and Administration (955/2 days)

xx About this course Nortel Networks Confidential
The SDM/FT Maintenance and Administration course provides skills for

maintaining the SuperNode Data Manager and Fault Tolerance
administration.
• OMC-S Overview & Operation (937/2 days)

The OMC-S Overview and Operation course provides the key
information on tasks necessary for network operation and administration,
using the OMC-S (Operation and Administration Center for the GSM
Network Switching Subsystem ).
GSM MSC/VLR datafill engineer

This training is designed for anyone setting up and maintaining the datafill of
the GSM MSC/VLR translations according to a predefined dialing plan. This
training contains the GSM NSS Overview (931) and the GSM DMS
Overview (930) and the following courses:
• GSM CCS7 Translations & Operations (974/5 days)

The GSM CCS7 Translations and Operations course is designed for
anyone implementing and maintaining CCS7 for GSM on a DMS switch.
• GSM MSC/VLR Translations (970/10 days)

The GSM MSC/VLR Translations course provides the practical
experience in planning and setting up a DMS-MSC to perform digit
translations related to any call.
GSM HLR datafill engineer

This training is designed for anyone setting up and maintaining HLR tables to
create and manage subscriber profiles and services. This training contains the
GSM NSS Overview (931) and the GSM DMS Overview (930) and the
following courses:


• GSM HLR Translations (972/5 days)

The GSM HLR Translations course provides practical experience in
datafilling DMS-HLR tables to create and manage subscriber profiles and
services.
Nortel Networks Confidential About this course xxi
GSM subscriber service provisioning engineer

This training is designed for anyone in charge of subscriber management.
This training contains the GSM NSS Overview (931) and the GSM DMS
Overview (930) and the following courses:


• GSM HLR Translations (972/5 days)

The GSM HLR Translations course provides practical experience in
datafilling DMS-HLR tables to create and manage subscriber profiles and
services.
• GSM HLR-PS (935/3 days)

The GSM HLR-PS course provides key information about tasks
necessary for subscriber and service provisioning with the Home
Location Register-Provisioning Server (HLR-PS).

xxii About this course Nortel Networks Confidential
Additional GSM NSS application courses

The Delta Release Courses (96x/2 days) cover and describe the main new
features of the following NSS releases:
• GSM11 Release Delta (963/2 days)

• GSM12 Release Delta (961/1 day)
• GSM13 Release Delta (962/1 day)
• GSM Intelligent Networks (900/3 days)
The GSM Intelligent Networks course provides key information and
knowledge to setup and maintain tables required to implement Intelligent
Networks (IN) services and register subscribers.
• GSM IWF (938/5 days)

The GSM IWF course provides the information about the IWF
(Interworking Function).
Nortel Networks Confidential 1-1
Lesson 1
Introduction
Objectives 1
Given student lesson, instructor lecture and appropriate documentation, you
will be able to:
• describe the term switching in the telecommunications industry
• explain the function of a line and a trunk as interconnecting mediums
• differentiate between digital and analog transmission
• explain a PCM
• briefly describe the Nortel DMS-type switch family products
• describe the major functions of the Nortel DMS for GSM

1-2 Introduction Nortel Networks Confidential
Nortel Networks Confidential Introduction 1-3
Basic telecommunications concepts 1

In telecommunications, switching is the ability to connect one user to another
from a central point for the purpose of transmitting information. A switch is a
device that opens or closes electrical circuits between users equipment. The
switching process is what enables the user to originate a call from a telephone
and for that call to be routed through local, regional and global networks. A
Private Branch Exchange (PBX) is an example of a switch that is usually
located on a subscriber property.
The switching process, in a landline system, begins by lifting the telephone

handset. This action completes an electrical path to a switch and allows the
user to dial a telephone number, as shown in Figure 1-1. This process is
handled at the Central Office (CO).
Figure 1-1
Lines and trunks in a Nortel DMS network
Role of Various Nortel Switches

Nortel Digital Multiplex Switch (DMS)
LONDON DMS 250 Trunks DMS PARIS

DMS 250
250
Trunks
Trunks
Central DMS 100 Line Residential Line DMS 100
Central
Office DMS 200 sets DMS 200 Office
Trunks
Trunks
Line Business
PBX sets Line PBX
SL100 SL100
PBX :Private Branch eXchange
411-0930-001 12.03 February, 2001 Lesson 1 Introduction 1-3
The lines connect users to switches; a trunk is a transmission channel

connecting two switching devices as shown in Figure 1-1.
A telephone line is how a user is connected to a switch. Typically, users are

located no more than five miles (about 7.5 Km) from a central office switch.
Many calls a user makes are to locations more than five miles away. To
complete these calls, COs are connected to each other. A call may go through

several central offices before reaching its destination. COs are connected via
trunks.
Switching system evolution 1

The main types of switching systems, in order of development, are:
• manual control
• direct control
• common control
• stored program control
— electromechanical
— digital
Manual switching involved operators wearing headsets manually switching

lines on the switchboard. The operator would patch cables into jacks,
manually making the connections between subscribers.
Direct control switching used machines that made connections via

electromechanical switches. Connections were made by machines that were
controlled by the calling party. The switching equipment activated and
controlled directly by the pulse signals of the dial.
Common control switching involved the cross-crossing of metal bars, that

otherwise have no contact with each other except at the intersection.
A stored program control system is one in which control of switching

network operations is handled by a program stored in the memory of a
computer. This programmable computer senses the status of lines and trunks
and monitors information about dialed numbers. This system utilizes high
speed electronic devices and is sometimes referred to as an electronic
switching system.
The two types of stored program control systems are:

• electromechanical
• digital
In electromechanical systems, control was performed by a computer and the

actual switching network interconnections within the system are made by
reed relays. These relays have contacts enclosed in glass capsules that come
together to complete a circuit when they come in contact with each other.
Digital switching uses computer technology and stored program control. This
phase of development replaces reed relays with solid-state switching
(switches with no moving parts).
Digital switching systems advantages are:

• sending many voice signals over the same path reduces the amount of
equipment required so it is more economical
• solid-state switches can be operated quicker than other systems, thereby
facilitating quicker connections
• digital switching is physically and electrically quieter (no moving parts)
• reconstructed digital signals are cleaner and noiseless compared to analog
signals which can be affected by noise
• digital signals can be mixed with data from computers and other sources,
making more efficient use of mediums
• digital equipment can be used with present analog equipment, making it
possible to upgrade or add to equipment without having to replace it
• digital equipment is physically smaller and consumes less electricity to
operate

Analog signals and digital concepts 1

In analog transmission, normal speech varies in tone and volume. Analog
signals reflect these variations. These signals are represented by analog wave
forms. The information is generally carried by a fluctuating electric current.
Figure 1-2
A/D conversion
A/D Conversion
Analog Digital
A/DConversion
A/D Conversion
Digital transmission involves sending a series of digital signals from one

point to another. The term digital refers to a signal represented by the digits 0
and 1. Because speech is analog signal, it must be converted in digital signals
before it can be transmitted to digital components. This process is called
Analog to Digital conversion (A/D conversion).
The A/D conversion is performed by using a process called Pulse Coded

Modulation (PCM).
PCM concept 1
The PCM concept is a common method used in telecommunication systems.
The PCM signal can be transmitted by a/an:
• copper twisted pair
• coaxial pair
• optical fiber
• microwave
• satellite
There are three main steps to produce a PCM:

• sampling
• quantization
• coding
Figure 1-3 shows the sequence of operations from speech.
Figure 1-3
Steps to produce PCM samples
Steps to Produce PCM Samples

Speech Filter
Sampling Quantization Line Coding
A Law
... 0 0 1 1 0 ...
8 kHz µ Law
411-0930-001 12.02/EN December, 2000 Lesson 1 Introduction 1-5

Sampling
Sampling involves measuring the analog signal at specific time intervals.
Each measurement is called a sample and the sampling time interval is
defined as Time Slot (s) (TS).
According to the Nyquist Theorem

To reproduce an analog signal without distortion, the signal must be sampled
with at least twice the frequency of the highest analog signal frequency.
Applying the sampling principle when sampling analog speech the sampling
frequency should be 2*4kHz=8kHz. It means, that you have 8000 samples
per second (125µsec/sample) from a 4kHz bandwidth.
Quantization
To limit the number of values transmitted, the amplitude levels divided into a
finite set of levels. Each sample within a certain interval is represented by one
of levels. In most cases, 256 levels are used to quantify samples.
For example the Public Switch Telephone Network (PSTN) uses A law or µ
law for logarithmic quantization.
Figure 1-4
Quantization
A-Law & µ-Law Quantization
10
1010110001011
Sampling Coder
10
10100101100010110001

Coding
As described above, quantified value is represented by a binary code. To
obtain the 256 levels, 8 bits are used (28=256).
The PCM process includes sampling at 8 kHz and performs quantization and
coding using 8 bits. It produces a bit rate of 8000 x 8 = 64 Kbit/s. This digital
signal coded onto 8 bits and transmitted at 64 kbit/s is called a Time Slot
(TS).
These 32 TSs or channels are multiplexed onto the one PCM link. The
technique used to multiplex channels in a same link is called Time Division
Multiple Access (TDMA).
Figure 1-5
Multiplexing channels
Multiplexing Channels
A/D
A/D
Conversion
Conversion
00
10
11
01
. .
A/D
A/D 00 1 01 1 0 1 2 3 3
9 0 1
0 1 2 3 .
2. 3 3 0
9. 0 1 1 2
.
Conversion
Conversion MUX
MUX
1
1 10
10
A/D
A/D 00
Conversion
Conversion
There are two kinds of PCM links:

• PCM E1: the bit rate on the E1PCM is 32 x 8 x 8000 = 2048 kbit/s
• PCM T1: the bit rate on the T1 PCM is 24 x 8 x 8000 = 1544 kbit/s
Figure 1-6
PCM Frame
PCM Structure
PCM E1
a E1 PCM • A law
32 TSs • 1 TS 64kbit/s
• 8 bits per TS
29 30 31 0 1 2 3 ... ... 30 31 0
29 1 2 • 32 TSs
• 2048 kbit/s per PCM frame
PCM T1
• µ law
• 1 TS 64kbit/s
0 0 1 0 1 1 0 1 • 8 bits per TS
a time slot • 24 TSs
8 bits • 1544 kbit/s per PCM frame

Nortel switching systems 1

When Nortel began developing the idea of the DMS family (Digital
Multiplex Switch), its developers researched the functional and aesthetic
requirement that customers demanded in a digital switching system. As a
result, the Nortel family switching system has advantages applicable to today
and in preparation for tomorrow.
Figure 1-7 shows a typical Nortel DMS network.
Figure 1-7
Typical network using Nortel DMS switch family components
Nortel DMS Switches

End Office Tandem Office Long Distance
Line DMS 100 Trunks DMS 200 Trunks DMS 250

Trunks
PBX
Trunks
Trunks
Trunks
SL100
GSM Switch
DMS-MSC
DMS-MSC
International
Gateway
DMS 250
BSS
The following are some advantages of the Nortel DMS switch family:
• high digital transmission quality virtually eliminates noise
• system modularity allows the easy addition of optional features which
generate revenue
• plug-in provisioning allows customers to plug-in trunk cards up to the
maximum engineered hardware and software capacity available
Nortel DMS SuperNode 1

The DMS SuperNode is the Nortel state-of-the-art switch that supports
advanced network services as well as customers’ needs for customized
network management functions. The DMS SuperNode switch is easily
adaptable to new and more powerful microprocessors as technology evolves.
This ability to expand increases processing and call-handling capacity.
The DMS SuperNode technology significantly increases the processing

power and enables the switch to expand revenue opportunities and lower
operating costs through the consolidation of switching entities. The DMS
SuperNode switch provides an interface with fiber transmission systems and
establishes the technology platforms upon which a host of advanced network
services and applications can be deployed.
The cabinet modules of a DMS switch are fully factory assembled and tested,
requiring minimal on-site installation or commissioning. To order a complete
DMS switch is simple. It is a one-step process that involves selecting the
appropriate Product Engineering Codes (PECs).
Public applications
These DMS-type switches are purchased by long distance and wireless
carriers and are FCC regulated in the North American market.
The following is a brief description of the switches:

• DMS-100
A local central office serving 1,000 to 100,000 subscriber lines.
• DMS-200
A toll central or tandem office that provides the first stage of collection
from offices serving subscribers and the final stage of distribution to
offices serving subscribers. The DMS-200 is capable of handling 400 to
60,000 trunks of various types.
• DMS-100/200
A local and toll central office handling combinations of subscriber lines
and trunks, with the ranges of the DMS-100 and DMS-200, as specified
by the customer. The DMS-100/200 is utilized in systems needing to
expand in either or both local/toll service. After installation, the DMS-
100/200 can add (without major system changes) specialized services, as
needs arise.

• DMS-250
A specialized common carrier system capable of handling from 960 to
30,000 trunks. The DMS-250 is designed for special and resale carrier
applications. The system's flexible configurations allow for a broad range
of capabilities, including multiple tenant groups and integrated data
service.
• DMS-300
An international (gateway) switching center capable of handling up to
27,000 international trunks. The DMS-300 serves as an interface to both
domestic and international networks.
• DMS-500
A local and long distance switch SuperNode application that combines
local services of the DMS-100 switch, and long distance services of the
DMS-250 switch.
GSM applications
The following DMS type switches are supporting GSM standard:
• DMS-MSC
Digital Multiplex System Mobile-services Switching Center. A Northern
Telecom product that offers all of the functionality of a Mobile-services
Switching Center (MSC) in a PLMN. DMS-MSC also contains an
integrated Visitor Location Register (VLR).
• DMS-HLR
Digital Multiplex System Home Location Register. A Northern Telecom
product that offers all of the functionality of a Home Location Register
(HLR) in a PLMN. DMS-HLR also contains an integrated Authentication
Center (AUC).
The DMS system supports mated pair HLR disaster standby

functions.Geographically separate (mated) HLRs each have a copy of
data for all subscribers, but the responsibility for processing the requests
for the subscribers is split between the nodes.
• DMS-MSC/HLR
A Northern Telecom product that offers all of the functionality of a
Mobile-services Switching Center (MSC) and a Home Location Register
(HLR) in a PLMN. It also includes an integrated Visitor Location Register
and Authentication Center.
DMS-MSC functions 1
The Nortel DMS-MSC performs the following functions:
• basic switching function of the Network and Switching Subsystem (NSS)
within a GSM PLMN
• mobile voice call handling
• mobile data call handling
• emergency call handling
• supplementary services
• enhanced services
• intelligent networks
• external interfaces
• Gateway MSC function
DMS-MSC mobile call handling 1

The DMS-MSC performs voice and data call switching functions for all
mobile stations (MSs) located in the geographical area of the DMS-MSC,
known as its serving area. The switching functions occur between mobile
subscribers in a PLMN or between mobile subscribers and telephones and
services in the public switched telephone network (PSTN) or Integrated
Services Digital Network (ISDN). To perform its switching and call
processing functions, the MSC interacts with other nodes in the PLMN and
with land networks.
DMS-MSC mobile voice call handling 1

The DMS-MSC supports the following voice call features:
• full rate speech
• enhanced emergency call features
• DTMF signalling from a mobile station
• multiple vocoders
• transcoder pool handling
DMS-MSC mobile data call handling 1

The DMS-MSC supports the following data call features:
• fax and data services
• alternate speech and data services
• V42BIS data compression
• 14.4 Kbps to the mobile station

DMS-MSC emergency call handling 1

The DMS-MSC provides the following services for type 1 emergency calls:
• allows an optional check to determine the mobile station’s service
registration before accepting and routing the call to the emergency center
• provides the flexibility to determine if the call should be service validated,
authenticated, ciphered, and/or International Mobile Equipment Identity
(IMEI) checked
• allows a mobile subscriber to conference in an emergency call and allows
a three-way call establishment after an inter-MSC handover
• supports Multi Frequency (MF) and Signaling System 7 (SS7) signaling
to transfer location and calling number information to the emergency call
center
• upports call re-establishment in the event of loss of radio.
• supports type 1 emergency data calls
DMS-MSC supplementary services 1

A supplementary service modifies or supplements a basic telecommunication
service. It cannot be offered to a subscriber as a stand-alone product.
The DMS-MSC supports the following supplementary services:

• call forwarding services
• call hold
• call waiting
• call barring services
— password control of supplementary services
• advice of charge
• line identification services
• three-way voice calls
• closed user groups
• operator determined barring
• operator determined barring of conditional call forwarding
• local calls only
• unstructured supplementary service data
• explicit call transfer
• private numbering plans
• alternate line service (dual numbering)
• subscriber account code

• service invocation using dialed digits
• extension services
• calling name display
• malicious call trace
DMS-MSC enhanced services 1

Enhanced services are services that:
• employ computer processing applications that act on the format, content,
code, protocol, or similar aspects of a subscriber transmitted information
• provide the subscriber additional, different, or restructured information
• involve subscriber interaction with stored information
The DMS-MSC supports the following enhanced services:
• equal access/carrier selection
• local number portability
Intelligent Network (IN) 1
The DMS-MSC can be equipped with an integrated Service Switching Point
(SSP) function. This function supports ETSI Intelligent Network Application
Part (INAP) procedures and protocols for signaling between IN defined
functions. The integration of the SSP into the DMS-MSC (referred to as the
DMS-MSC/SSP) provides a close coupling of the IN triggering mechanism
with the GSM call processing function.
DMS-MSC external interfaces 1

The DMS-MSC has external interfaces with:
• other network nodes, including the:
— DMS-HLR
— Equipment Identity Register (EIR)
— Short Message Services Service Center (SMS-SC)
— Interworking Function (IWF)
— Operations and Maintenance Center Switching (OMC-S) using a Q3
interface
— Base Station Subsystem (BSS)
— Intelligent Peripherals (IP)
— other MSCs
• other networks, including:

— Public Switched Telephone Network (PSTN)

— Packet Switching Data Network (PSDN)
— Integrated Services Digital Network (ISDN)
DMS-MSC gateway function 1

In addition to the above functions, any DMS-MSC in a PLMN may be
configured as a GMSC.
A GMSC is capable of interrogating a mobile subscriber Home Location

Register (HLR) to obtain the information required to terminate calls to that
mobile subscriber. A GMSC may serve as an interface between PLMNs or
between a PLMN and a PSTN for incoming calls.
Figure 1-8
Typical network subsystem
Network and Switching System
EIR HLR
SMS-SC
AuC
PSTN DMS-MSC DMS-MSC

Gateway
VLR VLR
Another GSM
Network, or ISDN
Intelligent BSS
Networks

DMS-MSC support of Primary Rate Interface (PRI) 1

PRI is an ISDN protocol that provides end-to-end digital connectivity, thus
allowing support of a wide range of user services including voice, data, and
wideband.
The DMS-MSC supports both variants of PRI: ANSI PRI and ETSI PRI.
The DMS-MSC supports:

• basic ETSI and ANSI call establishment and release
• PRI specific features including;
— user-to-user signaling
— called/calling party subaddressing transport
— disconnect with tones
— priority class of service
PRI has several key benefits including:
• allowing the network operator to provide access to end users that are
connected to corporate PBXs
• providing an alternative to SS7 for connectivity to network applications
including voice mail systems, intelligent peripherals, etc.
• providing an evolutionary path to deploy low tier wireless technologies
(e.g., DECT, CT2)
DMS-HLR functions 1
The Digital Multiplex System-Home Location Register (DMS-HLR)
performs all of the functions required of an HLR in a GSM PLMN NSS. In
addition, DMS-HLR includes an integrated Authentication Center (AUC).
The AUC helps to ensure that only authorized users have access to the
network. The DMS-HLR integrated AUC performs all of the functions
required of an AUC in an NSS.
Note: Although the DMS-HLR contains an integrated AUC, the two are
separate functional entities within the NSS.
DMS-MSC/HLR functions 1
The Mobile-services Switching Center (MSC) performs all of the switching
functions needed for the Mobile Stations located in its geographical area,
known as its Serving Area.
To perform its switching and call processing functions, the MSC must interact
with other components in the network. The MSC may be paired with a Visitor
Location Register (VLR). Following is a list of major MSC functions:
• mobile subscriber call establishment and routing
• dialed digits translation
• call control and signaling
• billing data capture and formatting
• authentication and ciphering
• locating and contacting mobile stations for call termination
• handover of call from one cell to another
• management of facilities for calls
• echo control
• Short Message Service support
• Supplementary Services support

Exercise 1-1 Review Questions

1. What is switching?
2. What is the role of a central office?
3. What is the function of a line and a trunk?
4. What is the difference between analog and digital transmission?
5. Which DMS switch is used in GSM applications?
6. Name four supplementary and/or enhanced services the DMS-MSC

supports.

Lesson 2
GSM DMS overview
Objectives 2
Given student lesson, instructor lecture, and appropriate documentation, you
will be able to:
• describe the main hardware layers of the GSM DMS
• describe the main hardware components of the GSM DMS
• describe the hardware architecture of the GSM DMS
• describe the GSM DMS cabinets
• describe the SuperNode, SNSE, and MicroNode architecture
• identify the layers of the GSM software

2-2 GSM DMS overview Nortel Networks Confidential
DMS 2
The DMS is a software-controlled, large-scale switching system that is
capable of handling up to 58,000 trunks with the SuperNode processor. For
more information about DMS system limitations, refer to “DMS system
limitations”
The DMS distributed architecture and processing capacity provides an

infrastructure for the development of new features and services. The DMS
SuperNode also provides an interface to fiber transmission systems.
The DMS system is based on a family or series concept and provides a wide
range of digital switching and networking functions. Modular design
techniques have been applied to various DMS family products that serve the
market, such as local, toll, cellular, and military network switches and provide
special business services.
DMS family attributes 2

Distributed processing
The architecture of the DMS uses modular concepts in both hardware and
software. Each hardware module has its own microprocessor. By distributing
microprocessor controlled modules throughout the DMS, the master Central
Processing Unit (CPU) is relieved of many time-consuming functions and
thus can perform higher level functions.
Stored program control

The DMS system is controlled by stored programs, and is capable of serving
virtually any local, toll, or combination of applications. The stored programs
required for call processing reside in the processors and various distributed
processors. These distributed processors are controlled by a master CPU. The
master CPU controls all operations of the DMS by referencing and executing
the stored programs as needed.
Digital network
All facilities entering and leaving the network carry digital information. The
DMS switches voice and data using a fully digital network. The ability to
implement time division switching in a digital network greatly enhances the
flexibility of the switching matrix and eliminates network blocking and
crosstalk.
Nortel Networks Confidential GSM DMS overview 2-3
Trunk input
Depending on how the DMS is used, trunk information must be made available
to the system.
• when processing a call, the system utilizes customer-related data
including directory numbers
• to serve trunk group types
• to start dial signals

DMS-MSC hardware architecture 2

The DMS-MSC hardware is modular and is divided into functional hardware
layers. Figure 2-1 shows the three layers and the hardware entities that
comprise the three layers.
Figure 2-1
DMS-MSC hardware architecture
DMS-MSC Hardware Architecture
Service
Processing DMS-Core
DMS-Core File
File Processor
Processor SDM
SDM
Hardware
DMS-Bus
DMS-Bus
Messaging/
Connectivity
Hardware
Enhanced
Enhanced Network
Network
Physical Link
Link
Peripheral
Peripheral Modules
Modules
Access Peripheral
Peripheral IOC
(PDTCs,
(PDTCs, MTM,
MTM, etc.)
etc.)
Hardware Processor
Processor
To/From To/From a To/From

Trunks CCS7 Network, etc. IODs
411-0930-001 12.03 February, 2001 Lesson 2 DMS-MSC Overview 2-3
Service processing hardware layer 2

This layer contains the processing for central call handling, DMS system
control, DMS system management, the File Processor, and the SDM. The
service processing layer also provides the higher-level functions associated
with the wide variety of telecommunications services provided by the DMS.
As shown in Figure 2-1, the hardware components of this layer are
interconnected by the DMS-Bus.
The service processing layer supports the following:
• high-level call processing for trunks terminating on the DMS
• central Operation, Administration, Maintenance, and Provisioning
(OAM&P)
• some Operations Support Systems (OSS) interfaces (an OSS is an
external computer system used to configure and administer a network)
• Advanced Intelligent Network (AIN) services which use the CCS7
protocol
Messaging and connectivity hardware layer 2

The messaging and connectivity layer contains the major internal messaging
component and the call switching fabric. This layer carries and connects
digital traffic across the switch. This layer uses the Enhanced Network
(ENET) switch fabric for DS0-based service connections. (DS0 is a protocol
for digital transmission that represents one 64 Kbits/channel.)
This layer also includes the DMS-Bus, which is a packet switch that routes
messages between the various nodes in the switch.
Physical access hardware layer 2

This layer provides terminations, signal processing, service-specific protocol
handling, and multiplexing. It also provides interfaces and processors having
access to external signaling and data networks, and allows trunks carrying
voice or data traffic to connect to the DMS.
Functional hardware layers 2

As shown in Figure 2-1, the functional hardware entities that make up the
three layers of the DMS-MSC hardware architecture are:
Service processing hardware
• DMS-Core
— Computing Module (CM)
— System Load Module (SLM)
• File Processor (FP)
• SuperNode Data Manager (SDM)
Messaging and connectivity hardware
• DMS-Bus (also called Message Switch or MS)
• Enhanced NETwork (ENET)
Physical access hardware
• Peripheral Modules (PMs)
• Link Peripheral Processors (LPPs)
• Input/Output Controllers (IOCs)
Each of these entities is explained later in this lesson.

Duplication for reliability 2

For reliability, the SuperNode has duplicated elements. The control elements
operate in synchronism, and the message elements operate in load-sharing
mode.
As outlined in Figure 2-2, duplication offers hardware fault protection as well

as the ability to carry out office extensions and software updates without
disrupting service.
Figure 2-2
Duplications for reliability
Duplications for Reliability
DMS-Bus (load sharing)

1
0
DMS ENET
SDM IOC
Core (Active/Active mode) 1 FP
1
0 0
(Hot/
01
Active PMs
Standby
Mode) PDTC 1
0
1 MTM
0
(Hot/Active Standby Mode)
DMS-Core 2
The DMS-Core:
• is a part of the service processing hardware layer of the DMS-MSC and is
the computing engine for the entire DMS-MSC
• consists of a duplicated, high-capacity, single-chip microprocessor with
duplicated memory, communications buses, and interfaces to the DMS-
Bus (see Figure 2-3)
• controls all events on the switch, including call processing, call
accounting, and switch performance
• contains a dedicated operating system known as the Support Operating
System (SOS)
In some systems, File Processors (FPs) are deployed in support of the DMS-
Core to provide enhanced DMS-MSC functions.
The DMS-Bus provides the clock to the DMS-Core (and to all other DMS-
MSC components as well). It is the central clock for the entire DMS-MSC,
and can be synchronized to a network clock source.
Figure 2-3
DMS-Core
SuperNode DMS-Core
Unit 0 Unit 1
CPU 0 CPU 1
Memory MEB Memory
SCSI SCSI
Crossover
Disk
POWER
Disk
Disk
POWER
LOAD
ON LINE
REWIND
FORWARD
Buses Disk LOAD
ON LINE
REWIND
FORWARD
REVERSE
WRITE
ENABLE
REVERSE
WRITE
ENABLE
Tape SLM 1 Tape

SLM 0

DMS-Core functions 2
The specific functions of the DMS-Core include the following:
• operations, administration, and maintenance
• translation of call address digits (telephone numbers)
• selection of outgoing trunks
• call feature processing
• call supervision (monitoring and control functions associated with a call)
• ENET connection control
• subset of ISDN User Part (User Part is a portion of the ISDN protocol)
• maintenance of the DMS-Core and its links
• loading of switch software and monitoring of processor sanity
• loading of peripheral software
System Load Module (SLM)

As shown in Figure 2-3, the DMS-Core contains a System Load Module
(SLM). The SLM stores the switch software loads, switch data, office images
(an image of the software and data for a particular customer switch), and
Peripheral Processor software loads. The SLM includes a cartridge magnetic
tape drive and a high-capacity disk drive, along with controllers for both
storage devices.
The SLM is connected to the DMS-Core by an extension of the DMS-Core

processor bus. The active CPU has read and write access to both SLMs, and
the inactive CPU has read access only.
File Processor (FP)

The File Processor (FP) enhances the data management capabilities of the
DMS-MSC. The FP provides secondary storage and archive functions, and
allows both file and database access to the stored data.
The FP may function as a billing server. Capabilities of the FP include the
following:
• industry-standard serial device interface
• fault-tolerant file system (FTFS)
• redundant data storage devices with automatic disk shadowing
• high-performance methods for relational database access
The FP hardware is similar to the SYNC-matched DMS-Core computing

hardware. The FP has three memory cards, a Small Computer Serial Interface
(SCSI) card, and fiber-optic links to the DMS-Bus. The FP supports
redundant 600 Mb hard disks and 1.3 Gb digital tape drives. As the CM, the
FP uses the SOS operating system.
DMS-Bus (or Message Switch) 2
The DMS-Bus is part of the DMS-MSC messaging/connectivity hardware
layer. The DMS-Bus:
• is a dual high speed transaction bus that provides message transport for
the distributed processors of the DMS on a peer-to-peer basis
• supports equal access to all ports
The DMS-bus access ports can be configured as DS-30 copper interfaces
and/or DS-512 fiber-optic interfaces.
• houses the system clock. The system clock provides synchronization for
the entire DMS-MSC and can serve as a network master clock source to
allow an entire network to run with the same time reference.
The DMS-Bus and the DMS-Core use the system clock to carry out
general clocking and timing functions.
Figure 2-4 shows that the DMS-Bus consists of two load-sharing planes, each
plane being an independent DMS-Bus (duplicated hardware). Each load-
sharing plane has a CPU, memory, and a set of interfaces to all other DMS-
Bus components.

Figure 2-4
DMS-Bus plane
SuperNode DMS-Bus
Message Switch 1 has:
• CPU
• Memory
• Set of interfaces
Slave Clock Plane 1
Message Switch 0 has:

• CPU
• Memory
• Set of interfaces
Master Clock Plane 0

• Provides synchronization
• Is the network master clock
Load Sharing Mode
Enhanced NETwork (ENET) 2

The ENET is a part of the messaging/connectivity hardware layer of the
DMS-MSC. The ENET functions primarily to make speech connections
between peripheral module nodes, and to make message connections between
the DMS-Core and peripheral modules.
The ENET is a single-stage switch, meaning that connections are established

at a single cross point rather than through a series of switching stages. This
single cross point allows any input channel to connect to any output channel
in one stage. The ENET is also non-blocking—any channel may connect to
any other channel.
The ENET imparts a consistent delay to all connections, but its performance
is unaffected by voice or data mix or by traffic load. In addition, it switches
multiple DS0 channels together for higher bandwidth connections.
Increasing the ENET channel capacity does not require re-cabling or re-
engineering: rather it requires only adding or upgrading some network circuit
packs.
The ENET contains duplicated planes. Each plane consists of one or more
shelves, where each shelf is paired with a shelf in the other plane. Each ENET
plane shelf is connected to both DMS-Bus planes as shown in .
For network reliability, the ENET redundant planes operate using

simultaneous independent duplication. With simultaneous independent
duplication, all processing tasks are performed by each plane, and each plane
issues identical instructions which are received by the other DMS
components (such as PMs or the DMS-Core). If one of the ENET planes
develops a fault, processing is not interrupted, because the instructions from
the other ENET plane are used.
Figure 2-5 is a simplified block diagram that shows how the voice, data, and
message signals flow into and out of the ENET.

Figure 2-5
Network connections
Network Connections
DMS
DMS -- Bus
Bus
Message Links
to/from PMs
DMS
DMS -- Core
Core
ENET
ENET
PM
PM PM
PM PM
PM PM
PM
Speech, Data, and
Message Links
DMS internal speech and message links 2

The DMS-MSC uses internal speech and message links that connect the
various functional hardware areas to each other.
DMS-MSC internal speech links 2

Speech links connect the PMs and the ENET.
The speech link connects the peripheral module area with components of the
DMS-MSC through the ENET. Each link provides a two-way (four-wire)
transmission path for 32 channels of time division multiplexed data.
The speech links have 30 channels allotted for transmission of pulse code
modulated (PCM) speech samples and two channels (signaling channels) for
control messages. Signaling channels 0 and 16 (currently only 0 is used) serve
to pass messages (using the network), to and from the DMS-MSC. The
transmission format on a speech link is designated DS-30. For this reason,
speech links and DS-30 links are often used interchangeably.
The DS-30 format is:

• 10 bits per channel
• 32 channels per frame
• 2.560 Mb/s transmission rate

DMS-MSC internal message links 2

The message link connects the MAP area and the network area to the central
control area. Each link provides a two-way (four-wire) transmission path for
32 channels of time division multiplexed data. The message links allocate all
32 channels for the transmission of message data. The message links are for
internal messaging only.
Using either DS-30 (32-channel copper wire) or DS-512 (512-channel fiber

optic cable), message links connect the following:
• CM to the MS
• IOC to the MS
• ENET to the MS
• PMs to the ENET
The DS-512 protocol was introduced to maximize fiber optic usage in DMS
SuperNode-based systems. DS-512 links connect the CM and the MS in the
SuperNode and SNSE systems. DS-512 links are also used to connect the
ENET to the MS and the ENET to some PMs.
The DS-512 format is equivalent to 16 DS-30 links, with:

• 12 bits per channel
• 512 channels per frame
• 125 µsec framing
• 49.152 Mb/s transmission rate
P-side and C-side 2

Two terms used to identify the side of a hardware subsystem are P-side and
C-side.
P-side refers to the peripheral side. It identifies that side of a subsystem

which interfaces closest with the peripherals, that is, the input/output
controllers and peripheral modules, etc.
C-side refers to the central control side. It identifies that side of a subsystem
which interfaces closest with the central control.
Figure 2-6 illustrates that the P-side of all the subsystems is facing out toward
the peripherals, while the C-side is facing the opposite direction.
Figure 2-6
P-Side and C-Side
P-Side and C-Side
MS
MS (Central
(Central Control)
Control)
P-side
P-side
C-side
C-side
C-side
C-side C-side
C-side
ENET
ENET
CM
CM IOC
IOC
Switching Matrix
P-side
P-side P-side
P-side
P-side
P-side
C-side
C-side
PM
P-side
P-side
411-0930-001 12.02/EN December, 2000 Lesson 2 DMS-MSC Overview 2-11

Peripheral Modules (or PMs) 2

PMs are the interface between the switching fabric in the DMS messaging/
connectivity layer and the telephony trunks, which in GSM networks, are
digital trunks. The PMs provide real-time intensive call processing and
service-specific protocol handling functions. Figure 2-7 is a simplified block
diagram showing how PMs interface the DMS-MSC to external network
components.
The PMs are controlled by the DMS-Core, and reduce the DMS-Core
processing load by doing much of the processing required for call handling,
as well as trunk interfaces. For example, once the DMS-Core has established
digital connections among PMs, the PMs can pass voice, data, signaling, and
control messages among themselves without supervision from the DMS-
Core.
There are numerous types of PMs that are used in all the various DMS switch
types.
The PMs used most commonly in the DSM-MSC are listed and explained in
Table 2-1.
Table 2-1
Commonly used GSM peripheral modules
NAME ACRONYM DESCRIPTION

PCM30 Digital PDTC Connects DS30 links from the switching
Trunk Controller network to PCM30 digital trunks
Digital Trunk DTCI Provides processing for ISDN services
Controller ISDN
Integrated ISM A single shelf that contains up to 18 test and
Service Module service packs used in switch and facility
maintenance. Using special circuit packs, an
alarm cross connect shelf and Office Alarm
Unit (OAU) can be integrated into an ISM.
Office Alarm Unit OAU Similar to the MTM, equipped with circuit
cards that interface various office alarm
circuits
Link Interface Unit LIU7 Processes messages entering and leaving an
for Common LPP through an individual signaling data link.
Channel Signaling Each LIU7 consists of a set of cards and a
7 (CCS7) paddleboard provisioned in one of the Link
Interface Shelves (LISs).
Network Interface NIU Provides the EIU and LIU7 with channelized
Unit access interface in a Link Interface Shelf (LIS)
Ethernet Interface EIU Provides the DMS-MSC with the

Unit communications interface to the Billing Center
(if used)
Link Interface LIM LIM shelf housed in LPP cabinet
Module
Maintenance MTM Supports test and service circuits. Examples
Trunk Module of service circuits are:
• recorded announcement devices

• tone receivers
• tone generator
PMs are usually composed of two redundant units working in active/inactive

mode, however some PMs use no redundancy.
Figure 2-7
Typical DMS-MSC PM connections
Peripheral Module Connections

ENET
ENET
Switching
Switching Matrix
Matrix
Peripheral
Peripheral Peripheral
Peripheral
Module
Module Module
Module Module
Module Module
Module
Trunks to BSS
Trunks to Another
DMS-MSC
Connections to Trunks to
CCS7 Network PSTN BSS
BSS
DMS-MSC
DMS-MSC

Input/output Controller (IOC) 2

The IOC as shown in Figure 2-8:
• is a part of the physical access hardware layer of the DMS-MSC
• is the interface from the DMS-Bus to a variety of serial devices including:
— video display terminals
— magnetic tape drives
— disk drives
— data units
— modems
— printers
• houses the cards that control the activity of each I/O device
• controls the communication links between the internal DMS-MSC
hardware components and the I/O devices
Video display terminals:
• used for the Maintenance and Administration Position (MAP) user
interface
Magnetic tape drives:
• provide removable mass storage
• used for storage and retrieval of DMS software and data such as the
following:
— data for billing records
— Journal File (JF) data modification records
— switch Operational Measurement (OM) data
Disk drives:
• also supported by the IOC
• can be used to store the same types of software and data stored by
magnetic tape drives
Figure 2-8
Input/output controller and devices
Input/Output Controller and Devices

IODs
I/O
I/O
Device
Device Disk Drive Unit
Controller
Controller
IOC
I/O
I/O I/O
Central
Central I/O POWER
Message
Message Device
LOAD
ON LINE
REWIND
Device
FORWARD
Control
Control REVERSE
WRITE
ENABLE
Processor
Processor Controller
Controller
Tape Drive
I/O
I/O
Device
Device
Controller
Controller
MAP Terminal

SuperNode Data Manager (SDM) 2

The SuperNode Data Manager (SDM) is a dedicated, high performance,
multi-application computing platform providing nodal OAM&P services for
the DMS-MSC. The SDM is housed in a C28 cabinet and consists of two
shelves, the Main Chassis (SDMM), and the Input/Output Expansion Chassis
(SDME).
SDM is fault tolerant; no single hardware failure can cause a system outage or
service failure.
To provide fault tolerance capability, the SDM/FT:

• operates in full synchronism
• communicates through four sets of DS-512 fiber links
The SDM configuration is shown in Figure 2-9. The supervisory console is a

VT100 like terminal.
Figure 2-9
SuperNode Data Manager/Fault Tolerant
SDM/FT & OAMP Applications
SDM Console MAPCI Terminal

SDM/FT
SDM/FT DMS Messages
DMS-
DMS- MSC/HLR
MSC/HLR
By DS 512 Links
Reset Terminal Interface

(RTIF)
LAN
OMC-S
HLR-PS CIS
Operation Administrative Maintenance & Provisioning Applications
Hardware packaging 2
As shown in Figure 2-10, the hardware components include the following:
• cards are pieces of rigid material on which electronic components are
mounted and connected. Cards, also known as circuit packs, are held in
shelves.
• shelves hold the cards which make up a particular function. For example,
a network module shelf holds all the network module cards.
• cabinets, also known as bays or frames, are enclosed metal framework
structures that hold up to four shelves of equipment. Cabinets are always
72 inches tall, 28 inches deep, and either 42 inches or 28 inches wide.
• a DMS-MSC consists of a combination of cabinets
The external distribution cables, their associated protective devices, and the
internal cables to the central office line units terminate on the main
distribution frame (MDF).
Figure 2-10
Hardware packaging
Hardware Packaging
Frame Supervisory Panel Frame Supervisory Panel
Cards within
39 a Shelf 47
26
33
72” Four
Shelves
13
19
0 5
Cooling unit Cooling unit
42” Cabinet 28” Cabinet

GSM DMS architectures 2

Table 2-2 summarizes the three possible lines of DMS-MSC cabinets.
Table 2-2
DMS architectures
SuperNode SuperNode Size MicroNode

Enhanced
Dual Plane Combined SNSE Combined Core SNSE Combined Core
Core Cabinet Cabinet
Enhanced Network Meridan Cabinet Global
Equipment Switch
Link Peripheral Processor Meridian Cabinet Interface
& Power
Cabinetized Digital Trunk Cabinetized Digital Trunk
Controller fo Offshore Controller fo Offshore
Cabinetized I/O Cabinetized I/O
Equipment Equipment
Cabinetized Digital Trunk Cabinetized Digital Trunk
Module Equipment Module Equipment
SuperNode Data SuperNode Data
Manager/Fault Tolerant Manager/Fault Tolerant
Application Processor Application Processor
Cabinet Cabinet
Cabinetized Power
Distribution Center
DMS SuperNodeLineup 2
The following are typical examples of how DMS-MSC cabinet lineups are
combined together (as a system). Refer to Figure 2-11.
Figure 2-11
DMS cabinet lineup with DMS SuperNode Base
SuperNode Lineup
FSP FSP FSP FSP
P P P P P P P P PP PP PP PP PP PP
S S S S S S S S SS MS 0 SS SS ENET 0.0 SS SS LMS 0 LMS1 S S
U U U U U U U U UU UU UU UU UU UU
S S S S S S S S SS MS 1 SS SS ENET 0.1 SS SS LIS SS
S S S S S S S S SS CPU 0 CPU 1 SS SS ENET 1.0 SS SS LIS SS
S S S S S S S S SS SLM 0 SLM 1 SS SS ENET 1.1 SS SS LIS SS
COOLING UNIT COOLING UNIT COOLING UNIT COOLING UNIT
CPDC DPCC ENET LPP

Cabinetized Dual Plane Combined Core Enhanced Network Equipment Link Peripheral Processor
Power Distribution Center (up 2 cabinets)

SuperNode Lineup (cont.)

FSP FSP FSP FSP
MTD
PP
SS
PP
SS
P P Billing Server P P
UU UU S S S S
U U File Processor U U
PCM30 Digital
Trunk Controller
PDTC 1 POWER
LOAD
ON LINE
REWIND
FORWARD
PP PP REVERSE
PP P
SS SS
WRITE
ENABLE P P P
UU UU SS S
S S S
UUU U U
PP
SS
PP
SS
PP
SS
PP
SS
PP Storage
16 PCM30s P P
IOC UU Expansion I/O S S S S
UU UU UU
UU Devices U U
PCM30 Digital
Trunk Controller
PDTC 0
PP
SS
PP
SS
PP
SS
PP
SS
P P Storage P P
UU DDU SDM/FT S S S S
UU UU UU
U U
Devices U U
16 PCM30s
CPTO CIOE SDM/FT APC

Cabinetized Cabinetized SuperNode Data Manager Application Processor Cabinet
Digital Trunk for Offshore Input/Output Equipment Fault Tolerant
SuperNode Size Enhanced Lineup (SNSE) 2

Figure 2-12 shows the DMS-MSC with DMS SuperNode SE (SNSE) as its
base.
Figure 2-12
DMS cabinet lineup with SNSE Base
SNSE Cabinet Lineup

FSP FSP FSP FSP
MTD
P P P P P P P P PP PP PP PP
SS SS
S S S S S S S S SS MS 0 MS 1 SS UU UU
U U U U U U U U UU UU
PCM30 Digital
Trunk Controller
POWER
LOAD
ON LINE
PDTC 1
REWIND
FORWARD
P P P P P P P P PP PP REVERSE
WRITE
ENABLE
PP PP
SS SS
S S S S S S S S SS LIS SS UU UU
ENET
SS SS SS SS
S S S S S S S S SS SS UU IOC UU UU UU
Plane 0 Plane 1
PCM30 Digital
Trunk Controller
PDTC 0
SS SS SS SS
S S S S S S S S S S SLM CPU 0 CPU 1 SLM S S UU DDU UU UU UU
U U U U U U U U UU 0 1 UU

CPDC SCC CIOE CDTO
Cabinetized SuperNode Size Enhanced (SNSE) Cabinetized Cabinetized
Power Distribution Center Combined Core Input/Output Equipment Digital Trunk for Offshore

SNSE Cabinet Lineup (cont.)

FSP FSP FSP
PP
SS Maintenance
PP
SS
P P Billing Server P P
UU UU S S S S
Trunk Module U U File Processor U U
PP PP P
SS Maintenance SS P P P P
UU UU S
S S
S S S
Trunk Module U
U U U U
PP PP P P Storage
16 PCM30s P P
SS Maintenance SS
Expansion I/O S S S S
UU
Trunk Module
UU
UU Devices U U
PP
SS Maintenance
PP
SS
P P Storage P P
UU SDM/FT S S S S
UU
Trunk Module U U
Devices U U
16 PCM30s
COOLING UNIT COOLING UNIT COOLING UNIT
CTME SDM/FT APC

Cabinetized Trunk Module SuperNode Data Manager Application Processor Cabinet
Equipment Fault Tolerant
MicroNode lineup 2
The GSM Integrated MicroNode is the newest addition to the Nortel DMS-
MSC product portfolio. It is a pre-engineered DMS-MSC/HLR/STP based
on the SNSE (SuperNode Size Enhanced) platform with a reduced hardware
configuration. This configuration allows reduced engineering and installation
costs while offering the same feature rich portfolio as a regular DMS-MSC
switch.
The GSM integrated MicroNode uses the standard DMS-MSC/HLR/STP

software loads.
Figure 2-13
MicroNode cabinet lineup
MicroNode Cabinet Lineup

FSP MSP MSP
PP PP
SS MS 0 MS 1 SS PDTC 0 unit 1 DSX
UU UU
PP PP
SS LIS SS PDTC 0 unit 0 Echo Cancellor
UU UU
ENET
PP PP
SS SS AC/DC Rectifier
Plane 0 Plane 1 ISM 1
UU UU
PP PP
S S SLM Battery Backup
CPU 0 CPU 1 SLM S S SDM/FT
ISM 0
UU 0 1 UU
COOLING UNIT COOLING UNIT COOLING UNIT

SCC MCGS MCIP
SuperNode Size Enhanced (SNSE) Meridian Cabinet Meridian Cabinet
Combined Core Global Switch Interface & Power

DMS system limitations 2

This section provides the following limitations of the DMS Systems:
• E1 limitations
• C7 Link limitations
E1 limitations
In a DMS-MSC system for the global markets, PDTCs (PCM Digital Trunk
Controller) is used to terminate E1 trunks that come into the system. Each
PDTC can terminate a maximum number of 16 E1 trunks. From the PDTC
limitations, the maximum number of CDTO cabinets and Time Slots are
shown in the following table.
Table 2-3
PCM limitations
PCM (E1) Limitations
Platform Number of Number of CDTO Time

PCMs PDTC Cabinets Slots
SuperNode 21
656 41 20992
with STP
SNSE 432 27 14 13824
MicroNode 48 3 1 + 1 MCGMI 1536
Note: The values listed above are examples given for

illustration only.
C7 link limitations
The MSC uses C7 Links as a signaling system to communicate with other
nodes in the network.
The C7 links are used to:

• transport the signaling messages
A C7 link is terminated by an LIU7 (Link Interface Unit for SS7) at the
MSC.
• communicate over the A-Interface; that is, the communication between

the MSC and the BSCs
C7 links between BSC and MSC use channelized access LIU7s, which
depend on NIUs (Network Interface Unit) for the physical connection
between a BSC and the MSC.
Since each C7 link requires an LIU7 to terminate on the MSC side, the
number of C7 links that an MSC can support depends on the number of
LIU7s that the system can support.
Figure 2-14 summarizes the maximum C7 Links in the DMS and their related
limitations.

Figure 2-14
C7 link limitations
C7 Link Limitations
PLATFORM SN SOFTWARE LIMITS SNSE SOFTWARE LIMITS HARDWARE LIMITS

GSM10 and C7 C7 TOTAL
NIU LIU-CBI EIU NIU LIU-CBI EIU ASU LPP FLIS
Beyond Link Link LIS
SN with STP 180 18 180 8 252 7 0 21
SNSE with 11
134 3 1
APC
SNSE without
122 3 0 10
APC
MicroNode 120 10 100 8 26 0 1 2
Note: A SNSE by itself can include 14 ASUs, including the two on the ENET shelf.
The same is true for the MicroNode.
Equipment labelling 2
The equipment labels are made up of the following discriminators: function
references, discrimination numbers, and location identifiers.
A function reference is an abbreviation which designates the function a

particular component performs. For example, the function reference for a
Central Control Complex component is CCC.
In most cases, more than one cabinet of equipment is required to perform an

assigned function. (The number of frames depends on the size of the system.)
A discrimination number consists of two to three digits and is added to the
shelf label of a cabinet. (The first digit identifies the cabinet number while the
last two digits identify the frame number.) For example, the duplicated MDC
shelves have discrimination numbers of MDC 0:00 and MDC 1:00.
The location identifier consists of two characters each. The location

identifiers are equipment row identifiers (one or two letters) and the cabinet
position identifiers (two digits).
The following is a description of the various labels found on the DMS-MSC

equipment:
• Cabinet labels—include the row identifier, the cabinet position number
(a two-digit number), and the frame function reference with
discrimination number. The cabinet labels are located on the FSP of each
cabinet.
• Shelf labels—on the FSP indicate what type of hardware modules occupy
the shelves in a cabinet. The top shelf label identifies the hardware
module in shelf position 47. The second shelf label identifies the
hardware module in shelf position 33. The third shelf label identifies the
hardware module in shelf position 19 and the last shelf label identifies the
hardware module in shelf position 05.
• Card position and circuit labelling—the card position number gives the
slot location of a particular card in the shelf. This card position number is
located on the lower rail of the shelf cage. The circuit reference and
product engineering code (PEC) are marked on a similar preprinted strip
on the upper rail of the shelf cage.
• Base mounting position—of a shelf or panel in a cabinet is based on the
mounting screw holes in the upright cabinet. Each upright cabinet has 67
holes whose centers are spaced one inch apart (see Figure 2-15).

Figure 2-15
Equipment labels for 42” cabinet
Equipment Labels for 42” Cabinet

Location Identifier
Row
1 MS 0.0 Identifier Cabinet Position Base
MS 1.0 A 01 Frame
Shelf Mounting
2 LIS 01 Supervisory
Labels Positions
3 ENI 00 SCC 00 Panel
ENI 10
4 CM 0.0
CM 1.0
52
Discriminator
Numbers
Discriminator
Numbers 39
N
PEC T
0
Reference X
5
0
A
Card 26
01
Position or
Slot Number
13
00
Cooling Unit
Cards and paddleboards 2

The DMS-MSC system uses two types of circuit packs: cards and
paddleboards. Cards are accessed from the front of a cabinet, while
paddleboards are accessed from the rear of a cabinet. As illustrated in Figure
2-16, cards connect to paddleboards through the backplane of the cabinet.
Typically, cards have complex circuits and functions while paddleboards
control information flow to the card. The paddleboard also provides the
physical connections for interconnection to other paddleboards, shelves and
cabinets.
Figure 2-16
Cards and paddleboards
Card and Paddleboard
P
a
d
d
l
Front Rear
Card e
b
o
a
r
d
Backplane

Product Engineering Code Identifier (PEC)

Each hardware product of the DMS 100 Family is identified by a unique
product engineering code (PEC). A PEC consists of eight characters and has a
specific structure:
(Prefix) (Base) (Suffix)

NT XXNN AA
Where:
NT is Nortel Networks
N is numeric
A is alphabetic
X is either numeric or alphabetic
Examples of PECs are NTFX42AA and NT6X24AC.
Prefix The prefix NT is assigned to all codes, thereby
identifying this item as a Nortel Netowrks product.
Base Code Group Uniquely identifies the function of a card.
Suffix A 2-character suffix identifies each version of
products. It is assigned in sequence: AA, AB, AC.
DMS-MSC software architecture overview 2

The DMS-MSC uses software to control hardware. The DMS-MSC software
system is designed for flexibility and efficiency. The basic language for the
DMS-MSC system is PROTEL (Procedure Oriented Type Enforcing
Language), a high-level computer language designed for use in switching
systems. PROTEL contains many features that create a reliable and
maintainable software system.
The DMS-MSC software system is divided into the following areas:

• operating system program manages the execution of the system
• call processing program directs and monitors a call's progression
through the system.
• administrative program includes database management tools that allow
the database to be changed
• maintenance program monitors system hardware performance and
provides manual and automatic test capabilities
DMS-MSC software structure 2

The DMS-MSC software is developed on the communications software
platform (CSP) architectural layer for deployment to all GSM markets. The
DMS-MSC software is developed in discrete functional units that provide for
the operation of different functions within the MSC.
The following is a list of MSC functions explained in later lessons:

• GSM interfaces
• call processing/protocol interworking
• mobility procedures
• handover
• data services
• supplementary and enhanced services
• short message services
• PSTN interworking
• VLR
These units combine to create the complete function package of the DMS-
MSC, as shown in Figure 2-17. Note that the structures do not necessarily
imply interrelationships.

GSM-based product layer and markets 2

The GSM-based product layer contains software specific to a particular
DMS-MSC product. This layer contains software specific to GSM markets.
GSM maintains North American services and global services. These markets
are supported with software specific to that particular market. For example,
the global services layer contains the software applicable to global (non-
North American) GSM markets. This layer includes country specific features
and signaling.
The separation of platform software from application software (DRUs=

Delivery Release Units) in the product layers allows specific DMS Supernode
products, including GSM software applications, to be enhanced
independently.
Figure 2-17
DMS-MSC software structure
DMS-MSC Software Structure

GSM Based Product Layer GSM Interfaces
GSM-1900 ESMR GSM 900/1800 ANSI7+
(iDEN)
MF
163TR8
NT ETSI ISUP
GSM Market Specification
GSM DRUs
ATUP
North American Services Global Services
BTUP
CTUP
Chinese R1
GSM Services
Taiwan R1
Short Message Supplementary Global R2

Data Services Services
Service ST ISUP
GSM Call-Processing Base
Mobility Translations
MAP Base &
Mgmt.
Routing
Handover
A-Interface VLR
Shared Layer
CSP
Telecom Layer
Base Layer
GSM services 2
This layer contains the software related to GSM-defined services including:
• supplementary services
• short message service
• data service
GSM base 2
This layer contains the software related to the basic GSM functions including:
• mobility management
• visitor location register
• handover
• A-interface
• MAP base
Shared layer 2
Shared layer contents are obtained from the shared library. This library is a
central repository for storage of software features and frameworks for
multiple products. This centralized database provides the means for the
management of common software allowing market and product
independence, the evolution of services and a cost-effective structure for
software reuse.
GSM uses selected elements of the shared library including portions of the
CCS7 base, equal access, and data services.
Telecom layer 2
The telecom layer includes general purpose utilities such as call processing
and communications protocols and maintenance systems for DMS
telecommunications products. These utilities include CCS7, call processing
base, run-time support, ENET maintenance, and basic translations. This layer
does not necessarily contain all the functionality required to place calls.
Base layer 2
The base layer contains resource management for system resources,
maintenance systems for general purpose computing devices and operations,
administration and maintenance for the system.

1. List the hardware components of the DMS-MSC.
2. What is the function of the IOC?
3. What is the difference between a speech link and a message link?
4. Define the terms P-Side and C-Side.
5. What is the software language of the DMS-MSC?
6. What is a DRU?
7. What are the two sizes of cabinets used in a DMS?
8. Describe the various labels used on DMS-MSC equipment.

Lesson 3
DMS-Core and DMS-Bus
Objectives 3
will be able to:
• describe the DMS-Core architecture
• describe the DMS-Bus architecture
• describe the base cabinet for the DMS SuperNode
• describe the base cabinet for SuperNode Size Enhanced (SNSE)
• explain the importance of taking an office image and Journal File (JF)
• describe the purpose of the Device Independent Recording Package
(DIRP)

3-2 DMS-Core and DMS-Bus Nortel Networks Confidential
DMS-Core 3
The DMS-Core (Figure 3-1) provides the processing power for the DMS
SuperNode. Using high-performance processors, the DMS-Core manages and
controls calls as they move through the system. The DMS-Core also handles
system integrity, maintenance and software loading and downloading.
The DMS-Core contains the two following major hardware components:

• Computing Module (CM)
• System Load Module (SLM)
Two synchronized CM planes in the DMS-Core manage high-level call

processing functions. The CM planes are connected by the Mate Exchange
Bus (MEB), which allows the processor on each plane to compare
computations to ensure system integrity between the active and inactive
planes. DS-512 links connect the DMS-Core to the DMS-Bus.
Two high-speed SLMs are used for software loading, office images and PM
loads. Each SLM consists of one Magnetic Tape Drive (MTD) and one high-
capacity Disk Drive Unit (DDU). The SLMs are configured as extensions of
the DMS-Core.
Figure 3-1
SuperNode DMS-Core
SuperNode DMS-Core
DMS-Core
CM Processor Bus 0
Processor Bus 1
DMS-Bus System Load

Control Processor Memory
Interface Module
MEB
DMS-Bus 0
DMS-Bus 1
411-0930-001 12.02/EN December, 2000 Lesson 3 DMS Core & DMS Bus 3-3
Nortel Networks Confidential DMS-Core and DMS-Bus 3-3
Computing module 3
The fully duplicated and synchronized CM processor performs the actual
system processing functions of the DMS SuperNode. The CM is based on a
32-bit processor with a built-in instruction cache facility and an on-board
high-speed data cache.
The CM has the following features:

• 32-bit RISC CPU
• integrated program and data store with error correction
• high-speed duplicated Message Controllers (MCs)
• distributed control reset system
• direct access to both SLM disk or tape
• both planes on the same CM shelf
• integrated inventory management for on-line identification of product
type and vintage for individual cards and paddleboards
The CM has up to 960 Mbytes of memory for each plane. A single shelf holds
both planes. The CM shelf is equipped with cards on the front of the shelf and
corresponding paddleboards on the rear. The cards share a common bus with
the paddleboards.
The CM contains the following functional subsystems:

• control processor
• memory
• DMS-Bus interface
Control processor
The control processor is responsible for call processing as well as the
configuration and maintenance of the other systems.
The control processor engine consists of:

• CPU cards
• memory cards
The memory cards provide storage for the CPU and two Reset Terminal
Interface (RTIF) paddleboards.
RTIF paddleboard
The RTIF paddleboard:
• monitors and decodes commands from the local terminal
• passes these commands to the CPU as control signals

• monitors processor signals and relays them to the local terminal or remote
scanning system
The RTIF paddleboard has one interface port connected to the RTIF terminal.
The RTIF paddleboard has two versions:

• RTIF terminal connected to the card by an RS-232 interface
• RTIF terminal connected to the card by either an RS-232 interface or a 20
MA current loop interface
In both versions, the RTIF terminal can be configured as either RS-232 or
E2A to handle transmission rates of 110 to 9600 baud.
RTIF terminal
The RTIF terminal:
• displays processor state information
• provides a facility for local resetting of the CM
Mate exchange bus
The Mate Exchange Bus (MEB) is the medium by which the two CPUs
maintain their operation of redundancy (or duplication). This medium allows
the two CPUs to routinely check each others modes of operation.
Memory
Memory cards store data used internally by the processor for call data and
program store. CM shelf is equipped with as many memory cards as needed (a
SNSE can have up to five cards per plane and a SuperNode can have up to ten
cards per plane). At any time, memory cards can be added. The need is
determined by:
• feature upgrades and software loads
• size of the office also determines how many memory cards are needed
Table 3-1
SNSE memory card configurations
Name Processor type Memory card type PEC

BRISC 50 88100 24 or NT9X14DB
96 Mb NT9X14EA
BRISC 60 88100 96 Mb NT9X14EA
BRISC 70 88110 96 Mb NT9X14EA
DMS-Bus interfaces
The transmission subsystem controls in-band data communication with the
MSs and provides the crossover for links. It consists of a CPU port card and
DS-512 interface paddleboards.
The CPU port card provides serial message communications between the CM
and the MS. The DS-512 paddleboard provides the transmission interface for
a single, bi-directional, two-fiber DS-512 format.
System Load Module (SLM) 3

The SLM is made of two provisionable SLMs that connect directly to the CM
system bus, their power supplies and interface circuitry. The SLM is
configured as an extension of the DMS-Core.
The SLM is also equipped with cards on the front and corresponding
paddleboards on the rear. The cards share a common bus with the
paddleboards.
The SLM shelf contains the following functional subsystems:

• SLMs
• interfaces
SLMs
The SLMs are the software image storage and loading devices for the CM.
An SLM performs the following tasks:

• boots the CM and the MS from disk or tape
• loads an office image into the inactive CPU
• dumps an image to disk
• performs off-line transfers from tape to disk or disk to tape
Either CPU of the CM can be loaded from either SLM through the crossover
bus.
Table 3-2 lists SLM configurations.
Table 3-2
SLM configurations
SLM Configuraton Hard drive Tape

capacity capacity
SLM 2 SN 600 Mb 250 Mb
SLM 3 SNSE & SN 1.0 Gb 500 Mb
Interfaces
The transmission system controls in-band data communication with the CM
and MS and provides the crossover for links. It consists of a CPU port card
and two parallel port interface paddleboards.

The CPU port card provides serial message communications between the
SLM and the CM. The parallel port interface paddleboards connect the
synchronous bus on the CPU card to the SLM with the aid of an interconnect
cable.
DMS-Bus 3
The DMS-Bus (see Figure 3-2) is the messaging component of the DMS
SuperNode. For reliability, the DMS-Bus consists of two MSs.
Each MS controls messaging and allows direct communications between

modules of a DMS SuperNode and contains two internal busses:
• transaction bus
• processor bus
MS functional subsystems 3
The MS shelf is equipped with cards on the front and corresponding
paddleboards on the rear. The cards share a common bus with the
paddleboards.
The MS consists of the following functional subsystems:

• processor and memory subsystem—configures and maintains the other
MS subsystems. The subsystem consists of a CPU card, a memory card,
the RTIF paddleboard and the T-bus access card.
• system clock—provides the clock source for the DMS SuperNode. It
consists of the MS system clock card and the MS subsystem clock
paddleboard.
• mapper—performs logical-to-physical address translation for messages
routed between ports.
• port interface—consists of the four-port DS-30 paddleboards, 16-port
DS-30 paddleboards, the DS-512 paddleboards, subrate DS-512
paddleboards and the MS port cards.
Control processor
A control processor circuit pack manages each MS plane. The control
processor is a 32-bit processor that contains one memory card. The MS
software resides on this memory card.
Transaction bus
The transaction bus carries payload messages, the actual traffic sent from one
module to another over the DMS-Bus.
The DMS-Bus can support multiple computers with a high-speed

interprocessor. This high-powered transaction bus runs at 28 megabytes per
second, has up to 1,400 ports and has a maximum port bit rate of 32
megabytes per second. The DMS-Bus can handle more than 125,000 interport
transactions per second with a delay of less than 100 microseconds per
transaction.

The DMS-Bus access ports can be configured as DS-30 copper interfaces or

DS-512 fiber-optic interfaces. To ensure maximum reliability, each MS is
connected to each CM plane in the DMS-Core by DS-512 links.
Processor bus
The processor bus supervises and controls the transaction bus and port
interfaces. The processor bus carries only the control messages required for
DMS-Bus operation.
System clock
The DMS-Bus also houses the system clock, used by both the bus and the
core to carry out general clocking and timing functions.
The system clock provides synchronization for the DMS SuperNode and can
serve as a network master clock source to allow the entire network to run at
the same frequency.
Figure 3-2
SuperNode DMS-Bus
SuperNode DMS-Bus
DMS-Core
DMS-Bus
DMS-Bus
Port
Interface
Transaction Bus Processor/
Transaction
Bus
Processor Bus
Control
Processor
Bus
Port … Port Port System
Address
Interface Interface Interface Clock
Mapper
Link
Link Input/
Input/
Enhanced
Enhanced …
Peripheral
Peripheral Output
Output
Network
Network
Processor
Controller
Note: Only one plane is shown. The other plane is identical.
411-0930-001 12.03/EN February, 2001 Lesson 3 DMS Core & DMS Bus 3-4
MS connectivity 3
The MS concentrates and distributes messages in the DMS SuperNode and
allows other components to communicate directly with each other.
The MS provides the following capabilities:

• port-to-port message switching
• 240,000 messages per second with 64-byte message length
• independence among ports
• self-maintaining and self-diagnosing processor
The DMS-Bus can be configured with up to two inter-MS links, which can be
connected to any interface card in the MS shelf. As shown in Figure 3-3, the
DMS-Bus (message switch 0 and 1) concentrates and distributes messages to
and from the various nodes (CM, ENET, IOCs, and application processors)
connected to its ports. Access ports on the DMS-Bus can be configured as
DS-30 copper interfaces or as DS-512 fiber optic interfaces.
Figure 3-3
Inter-MS link configuration
MS Connectivity Inter Message Switch

Message Switch 1 Links (IMLs):
DMS DS-512 or DS-30
Bus
Message Switch 0
DS-512 DS-512 DS-30 DS-30

Fiber Fiber
D-S30
CM
LPP IOCs
ENET
SLM
RTIF
Modems
MTD
CCS7 DDU
Terminals
DS-512 Fiber
or DS-30 Copper
PM PM
411-0930-001 12.03/EN February, 2001 Lesson 3 DMS Core & DMS Bus 3-5

Operation of DMS hardware components 3

Generally, the duplicated control components of the service processing layer
operate in instruction synchronism (also known as SYNC-matched hardware
operation), with both units executing the same instructions in parallel. This is
also referred to as active/inactive redundancy.
In contrast, the Message Switch (MS) operates in load-sharing redundancy,

with the network making all connections in both planes. PMs come in many
variations, and use either active/inactive, load sharing, or no redundancy.
Plane
The term plane refers to a single side of a SYNC-matched node. Each plane
includes a single processor, memory, link interface circuitry, application
hardware, and power.
Operation of the DMS-Core in duplex mode

The DMS-Core uses SYNC-matched hardware operating in duplex mode. A
node operating in duplex mode is termed in-SYNC when the two CPU
processors operate in step, executing identical instructions based on the same
but physically separate data. One of the CPUs is designated as active, with
read and write access to the DMS-Bus interfaces. The other CPU operates in
hot-standby and has read access only to the DMS-Bus. Matcher hardware
compares information on the two processors’ buses. Any deviation, called a
mismatch, results in a mismatch interrupt.
Fault recovery of the DMS-Core

When operating in duplex mode and a mismatch interrupt occurs, the
Mismatch Handler executes a thorough diagnostic to determine which CPU
should be active and if duplex mode can be maintained. When the active unit
fails, a Switch of Activity (SWACT) occurs, meaning the inactive CPU
becomes active. In most cases, the node is stabilized within 50 milliseconds.
Applications are unaware that a fault has occurred, and recovery is
completely transparent.
Operation of the DMS-Core in simplex mode

In the DMS-Core, the two control processors can operate independently.
During this mode of operation (known as simplex), the DMS-Core that is
operating in hot-standby will be made inactive and taken off-line. When
inactive and off-line, this DMS-Core can then be used to execute software
upgrades and perform other maintenance activities without interrupting
services running on the active unit. The protective features of operating in
duplex mode (explained above) are not available in simplex mode. In the
simplex mode, the active CPU uses a self-checking maintenance system to
check for software or hardware faults.
DMS base cabinets 3

The DMS-Core and the DMS-Bus are housed in the following base cabinets:
• Dual Plane Combined Core (DPCC) for the SuperNode base
• Simple Combined Core (SCC) for the SNSE
SuperNode base cabinet
Figure 3-4 illustrates the SuperNode base cabinet also called Dual Plane
Combined Core (DPCC).
Figure 3-4
DPCC Cabinet
DPCC Cabinet for SuperNode

Configuration
FSP Frame Supervisory Panel
PP P P
SS MS 0 S S
Self 39
UU UU
PP P P
SS MS1 S S
Self 26 UU UU
PP P P
Self 13 SS CM0 CM1 S S
UU UU
PP PP
Self 00 SS SLM 0 SLM 1 SS
UU UU
COOLING UNIT
The DPCC cabinet consists of the following components:

• Frame Supervisory Panel (FSP)—located at the top of the DPCC
cabinet in shelf position 52. It contains alarm circuits and alarm indicators
and performs alarm monitoring functions and the reset control of power
converters. Power from the power distribution center comes into the FSP
and is distributed to the power converters within the cabinet.
• Message Switch (MS) shelves—constitute the DMS-Bus. They occupy
two shelves in the upper half of the DPCC cabinet. MS 0 resides in shelf
position 39 and MS 1 resides in shelf position 26. Each MS shelf is
equipped with cards on the front of the shelf and paddleboards on the rear.
The cards and paddleboards share a common bus.

• Computing Module (CM) shelf—resides in shelf position 13 in the

lower half of the DPCC cabinet and consists of a pair of synchronous
matched CPUs on two separate planes (CPU 0 and CPU 1). A mate
exchange bus connects the two planes, allowing the processors to
compare computations. The CM shelf is equipped with cards on the front
of the shelf and paddleboards on the rear.
• System Load Module (SLM) shelf—located at the bottom of the DPCC
cabinet, in shelf position 00. The SLM shelf houses redundant SLMs on
the front of the shelf, one for each of the CPU planes. A port crossover
bus provides both CPUs with access to either of the SLMs. In addition to
the SLMs, the SLM shelf is equipped with cards on the front of the shelf
and paddleboards on the rear.
• Cabinet Cooling Unit (CU)—provides forced air ventilation equipment
housed in the DPCC cabinet. The cooling unit contains three individually
replaceable blowers and is situated at the bottom of the cabinet.
The shelves are numbered from bottom to top starting with 00 at the bottom
and ending with 39 at the top. An explanation of each DPCC component
follows Figure 3-4.
SNSE & MicroNode base cabinet

As an alternative provisioning option, the SNSE gives network providers
greater flexibility in deploying advanced DMS SuperNode capabilities in
small offices. The DMS SuperNode processing and messaging platform, the
ENET and the LPP platform, which previously required three or four
cabinets, are combined into a compact, economical, single-cabinet
configuration.
As shown in Figure 3-5, the SNSE cabinet is composed of six sections:

• Frame Supervisor Panel (FSP)
• DMS-Bus shelf
• Link Interface Shelf (LIS)
• ENET shelf
• DMS-Core shelf
• cooling unit
Figure 3-5
DMS SuperNode SE (SNSE) configuration
SNSE & MicroNode Base Cabinet

PP P P
Self 39 SS MS 0 MS 1 S S
UU U U
PP P P
SS LIS S S
Self 26
UU U U
ENET
PP P P
Self 13
SS
Plane 0 Plane 1
S S Enhanced Network
UU U U
PP P P Computing Module
S S SLM CPU 0 CPU 1 SLM S S
Self 00 UU 0 1 U U System Load Module
COOLING UNIT

Office image and journal file 3

Before moving any further into the various DMS software levels, it is
important to understand the office image and Journal File (JF).
Office image
An office image is a copy, stored on Magnetic Tape Drive (MTD) or disk
drive unit (DDU) of the information in the CPU, program store, and data
store. This includes customer data tables, call processing programs, etc.
Office images are taken to protect the DMS in the event of a switch failure
which could corrupt the data base. If a failure does occur, the image needs to
be put back into memory.
To take an image, use the DUMP command. We recommend to take an image

on a daily basis and during a low traffic period. In case of switch failure, keep
the office image current since it is that information which will be booted back
into the data base (Figure 3-6). The Reboot procedure is performed from the
RTIF terminals.
Figure 3-6
Office image dump and manual bootstrap load
Office Image Dump & Reboot

TAPE/DISK
PROGRAM
STORE CPU "DUMP"
IMAGE
DATA STORE
TAPE/DISK
PROGRAM
STORE CPU "REBOOT"
IMAGE
DATA STORE
Journal file
If it is necessary to reboot the office from an image, all data changes made
since the date/time of that image could be lost (Figure 3-7). However, the
journal file feature provides a means of saving any modifications to the data
tables that may occur after an image dump. Therefore, the database always
has a current backup, in case of a system failure.
Figure 3-7
Journal file
Journal File
Map Table Editor Journal File
Data BUFFERS
Modifications
DIRP
Disk
Disk
Through the journal file, all data modifications are collected in buffers and
sent to a dedicated storage device (tape or disk) by DIRP (Device
Independent Recording Package).

Device Independent Recording Package (DIRP) 3

There are many different systems in the DMS-MSC/HLR that generate a
large amount of data that is stored on disk or tape. All of these systems are
competing for the same shared storage resources. DIRP manages and controls
the recording devices, protects data and efficiently uses the storage space.
1. Data originating from the subsystems are delivered to DIRP.

2. DIRP directs the data to the appropriate storage device.
By interacting with the remote data polling system (XFER) and a data
link, DIRP makes data available to other locations.
DIRP coordinates the allocation of recording resources and handles requests

for storage and retrieval of information.
Figure 3-8 illustrates the relationships between DIRP, the contributing

subsystems, the recording devices and the XFER.
XFER:
• allows an operating company to transfer information, such as billing data

or Operational Measurements (OM) data, to a remote data processing
center
• uses X.25 protocol for data transfer
For more information on this system, refer to NTP Remote Data Polling
System Description, 297-1001-524.
• an optional component of the DMS-MSC and is not part of the DMS-

MSC normal operation
Figure 3-8
DIRP block diagram
DIRP Block Diagram

Data Modification Call Processing
Other Events
Orders (DMO) Center
GSM Call
Operational
Other Journal File (JF) Detail Records
Measurements
Subsystems Subsystem (GCDRs)
(OM) Subsystem
Subsystem
XFER Device Independent Recording Package (DIRP)
Data Link
Administration
Center Disk
POWER
Disk LOAD
ON LINE
REWIND
FORWARD
REVERSE
WRITE
ENABLE
Recording Devices
DIRP subsystems
As shown in Figure 3-8, DIRP directs data originating from the subsystems to
an appropriate storage device, such as magnetic tape or disk. By interacting
with the remote data polling system and a data link, the DIRP utility makes
data available to other locations. Although Figure 3-8 only shows three
subsystems, namely the JF, GCDR, and OM subsystems, other subsystems
are also available.
GSM Call Detail Records (GCDR)

The GCDR system is an automated accounting system that collects and
records call information. The recorded information is used for billing
purposes and can be processed locally or remotely.
Journal file
The JF is a facility that preserves, on a recording device, changes made to the
data tables of the DMS-100 family systems. The JF provides a means of
restoring tables should a reload of office software from a backup image be
required.

Operational Measurements (OM)

OMs involve utilizing the hardware and software resources of the DMS-100
family systems that control the collection and display of measurements taken
on an operating system. OMs organize the measurement data and manage
their transfer to displays and records on which maintenance, traffic,
accounting, and provisioning decisions are based.
DLOG
DLOG is a log retrieval facility for Emergency One Condition records.
DLOG records raw data before it is structured into reports. DLOG data is
intended for use by Emergency Technical Assistance (ETAS) and field
support personnel.

1. List three major components found in the DMS SuperNode cabinet.
2. What is the function of the DMS-Core?
3. What is the function of the DMS-Bus?
4. What components are contained in a SNSE cabinet?
5. Why is it important to keep the office image current?
6. What is the purpose of DIRP?

Lesson 4
Input/Output Device (IOD)
Objectives 4
will be able to:
• identify the Input/Output Device (IOD) used in the DMS-MSC/HLR

• describe the Cabinetized Input/Output Equipment (CIOE) cabinet
• explain the purpose and function of the Input/Output Controller (IOC)
• explain the purpose of the Maintenance and Administration Position
(MAP) terminal
• describe the purpose of the Magnetic Tape Drive (MTD) and the Disk
Drive Unit (DDU)
• describe the Input/Output Module (IOM)

4-2 Input/Output Device (IOD) Nortel Networks Confidential
Input/Output Devices (IODs) 4

IODs (such as MTD, DDU, Visual Display Unit (VDU), printer, and modem)
are interfaced to the DMS using an IOC. The Input/Output Controller (IOC)
controls transfer of data to/from the IODs and the DMS-Bus.
The VDUs connected to the IOC are used as a Maintenance and

Administration Position (MAP) workstation. The MAP terminals provide a
Human-Machine Interface (HMI) to the DMS-MSC.
• Input /Output equipment consists of devices and controllers.

The IOD area provides an interface to the various devices used for
maintenance and administration tasks. These devices include DDU, MTP,
and MAP terminals.
• Information flow to and from these devices is controlled by the IOC, as

shown in Figure 4-1.
Figure 4-1
Input/output controller and devices
Input/Output Controller and Devices

IOC
I/O
I/O
Device
Device
Controller
Controller Disk Drive Unit (DDU)
I/O
I/O I/O
I/O
DMS-BUS Message
Message Device
POWER
Device LOAD
ON LINE
REWIND
FORWARD
Processor
REVERSE
WRITE
ENABLE
Controller
Tape Drive (MTD)
I/O
I/O
Device
Device
Controller
Controller
MAP Terminal
411-0930-001 12.02/EN December, 2000 Lesson 4 Input/Output Devices (IODs) 4-3
Nortel Networks Confidential Input/Output Device (IOD) 4-3
Cabinetized Input/Output Equipment (CIOE) 4

The Cabinetized Input/Output Equipment (CIOE) cabinet shown in Figure 4-
2 contains one IOC with IODs and storage devices.
Figure 4-2
CIOE cabinet
CIOE Cabinet
FSP
CIOE
MTD Cabinetized Input/Output Equipment
POWER
LOAD
ON LINE
REWIND
FORWARD
REVERSE
WRITE
ENABLE
P P P P
S S S S
U U IOC U U
P P P P
S S S S
U U DDU U U
COOLING UNIT
An IOC occupies a single shelf and can be equipped with up to nine device
controllers.

As shown in Figure 4-3, the minimum configuration for a DMS-MSC is made

of 2 IOCs. The maximum number of IOCs is 12.
Figure 4-3
Input/Output controller
Input/Output Controller (IOC)

Message
Links
NT1x62
Max.
0
CPU DDU 1
IOC 1
(act) MS 0 2
DDU
0
CM 0
...
8 Max.
MTD 1
MTD
CPU m
MS 1 a Modem
(inact) x
CM 1 TC 4
d Printer
e VDU
0 v
…….
IOC
m Modem
1 a
x
8 TC 4 Printer
d
...
e VDU
v
Device controller cards 4

Device controllers are provisionable cards that are physically located in the
IOC shelf. Five types of device controller cards are available with the DMS-
MSC/HLR: the Terminal Controller (TC) card, the Magnetic Tape Controller
(MTD) card, the Disk Drive Unit (CDDU) controller card, the MPC card, and
the EMPC card.
• Terminal Controller (TC) card

The terminal controller card (NT1X67) interfaces the IOC with up to four
single-port I/0 devices such as consoles, modems, and teleprinters. The
IOC shelf positions the terminal controller card in one card position. The
number of terminals per card depends on the terminal data rate.
• Magnetic Tape Controller (MTD) card

The MTD card (NT1X68) interfaces the IOC with one nine-track
magnetic tape drive. The MTD receives and returns messages to and from
the IOC and changes the messages to data transfer and control operations
for the tape drive. The IOC shelf positions the MTD in one card position.
• Disk Drive Unit (DDU) controller card

The DDU controller card (NT1X55FA) interfaces the IOC with one 14"
Winchester disk drive unit. The controller receives and returns messages
to and from the IOC and changes the messages to data transfer and control
operations for the disk drive. The IOC shelf positions the DDU controller
in one card position.
• X.25 Datapooling Card (Bit Synchronous Controllers)

The MultiProtocol Controller (MPC) card (NT1X89AB) allows data
communication between a DMS-MSC and an external computer (for
example, between a central office billing computer and the DMS-MSC
switch). The MPC card supports software routines for Data Packet
Network (DPN) communications. The MPC interfaces to data
communications equipment (modems or datasets) using asynchronous,
X.25, or BX.25 protocols. MPC links can transmit data using RS232 at a
maximum rate of 19.2 kbits/second.
• The Enhanced Multi-Protocol Controller (EMPC)

Enhanced Multi-Protocol Controller (EMPC) card (NT1X89BB) is
identical to the MPC except that the EMPC also provides a 56/64 kbits/
second V .35 link.

Devices 4
Several types of devices, including consoles, Magnetic Tape Drives (MTDs),
and Disk Drive Units (DDUs) can be connected to the DMS-MSC.
Maintenance and Administration Position (MAP) terminal

The MAP terminal is used for maintenance, testing, and administration
functions. It performs all visual displays including status indications and test
results and allows an operator to enter the DMS-MSC through the VDU
keyboard. Nortel uses a terminal controller to interface the VDU to the
system. A typical VDU is the VT100.
Disk drive unit

As shown in Figure 4-4, the DDU is located in the bottom shelf of the CIOE
cabinet. Two 8-inch or 5.25-inch 340 Mbyte DDUs are equipped per shelf,
each with a dedicated power converter (NT1X78).
The DDU is used for the storage and retrieval of information. The storage
capacity of the DDU is greater than that of the magnetic tape drive and data is
accessed faster. Because of this storage capacity and speed, the DDU is used
to store large amounts of information from different sources.
The disk stores automatic message accounting GCDR, OM, JF.... Recording
of information from these subsystems is conducted by DIRP.
Figure 4-4
Disk drive unit shelf
Disk Drive Unit (DDU) Shelf

DDU:00/01
DDU 0 DDU 1
NT1X78AA
NT1X78AA

Magnetic tape drive

The MTD (Figure 4-5) is a 9-track tape unit used for storage of data.
The MTD stores data for several applications including the following:
• OM
• DLOG
• GCDR
• JF
Figure 4-5
Magnetic tape drive
Magnetic Tape Drive (MTD) Shelf
POWER
LOAD
ON LINE
REWIND
FORWARD
REVERSE
WRITE
ENABLE
IOD cards, ports, and circuits

As shown in Figure 4-6, an IOC shelf supports a maximum of nine device
controller cards (numbered 0-8). Each card has four ports (numbered 0-3).
This means that each IOC can support up to 36 ports.
In the table associated with IOD/IOC configuration, the system refers to these
ports as circuits and numbers them from 0-35. For example, if a VDU is
connected to card 2 on port #1, then this VDU is on card 2, circuit #9.
Figure 4-6
IOC cards, ports, and circuits
Single Shelf IOC Cards, Ports,

and Circuits
…
Card 0 1 2 3 8
To To
MS0 MS1
Ckt Port Ckt Port Ckt Port Ckt Port Ckt Port
3 3 7 3 11 3 15 3 35 3
2 2 6 2 10 2 14 2 34 2
…
1 1 5 1 9 1 13 1 33 1
0 0 4 0 8 0 12 0 32 0
1x62 1x55 1x68 1x67 1x89 1x67 0x67

IOC SCSI MTD Terminal MPC Terminal Bus
Controller DDU Controller Controller Terminator

Input/Output Module (IOM)

The IOM is a circuit pack housed in an ISM shelf that replaces the
functionality of the IOC, disk drive, tape drive units, which was provided by
various components in the IOC shelf.
To provide redundancy, a second IOM can be provisioned in a different ISM

shelf. Figure 4-7 shows an ISM shelf and IOM circuit pack.
The IOM controller card (NTFX30AA) and its associated paddleboard

(NTFX31AA) form the nucleus of the IOM. The IOM pack provides the DMS
with 16 communication ports:
• RS 232 C ports
• Current Loop 20 mA
• V.35 (up to 64 Kbps)
The IOM storage media card (NTFX32AA) holds a:
• DDU: 3.5 inch SCSI module (NTFX32BA) of 1.0 Gbyte capacity
• DAT: SCSI module (NTFX32CA) of 1.3 Gbytes uncompressed capacity
With these units installed in the storage media card, the IOM becomes
functionally equivalent to the IOC. This configuration can be used in all
applications that require an IOC.
Note: The ISM shelf is presented later in this document. For more
information, refer to Peripheral Modules (PMs) section.
Figure 4-7
ISM shelf and IOM circuit pack
ISM Shelf and IOM Circuit Pack
ISM Shelf F
X
3
1
Rear View
F FX32AA (Frame Card)

X
3
0 FX32BA (Disk)
Front View A
A
FX32CA (Tape)
Slots 3 4 5


1. What are the two main functions of IOCs and IODs?
2. What is the purpose of the MTD and DDU?
3. What are the four types of device controllers?
4. What is the advantage of the IOM compared to the standard IOC?

Lesson 5
Enhanced Network (ENET)
Objectives 5
will be able to:
• explain the purpose and advantages of the Enhanced NETwork (ENET)

• describe ENET cabinets for SuperNode
• describe ENET shelf for SNSE and MicroNode
• describe the ENET speech path
• define key terms in relation to the ENET area, including:
— circuit packs
— crosspoints
— H-bus and V-bus

5-2 Enhanced Network (ENET) Nortel Networks Confidential
Enhanced network 5
The ENET provides the following:
• dedicated path for calls and data between the various Peripheral Modules
(PMs)
• communication links via MS to PMs
The network area establishes and maintains full duplex (four-wire) speech
and message paths between the PMs and the central control. Since ENET is
fully duplicated, every active connection is backed up by a corresponding
inactive connection. If any connection fails, the backup automatically
becomes active.
Figure 5-1 shows a call with a parallel connection set up through both planes
0 and 1.
Figure 5-1
Duplicated switching network
Duplicated Switching Network
ENET
Originating Terminating
PM Plane 0 PM
Unit 1 Unit 1
Plane 1
Unit 0 Unit 0
411-0930-001 12.02/EN December, 2000 Lesson 5 Enhanced Network (ENET) 5-3
The ENET is a single-stage, non-blocking, time switching system. In most

conventional switching configurations, some calls can be temporarily
blocked.
With ENET, the single-stage architecture guarantees a dedicated path for each
call.
Nortel Networks Confidential Enhanced Network (ENET) 5-3
As shown in Figure 5-2, the ENET produces a dramatic reduction in the

footprint of the central office.
Figure 5-2
Enhanced network reduces footprint
Enhanced Network Reduces Footprint

ENET 2 Cabinets 1990
9x05BA
8x11
16
Frames
1986
5x13
32
Frames
1983
0x48
64
Frames
1979
The advantages of ENET are as follows:

• enables multiple 64 Kbps connections for wideband services
• 0X E-12 bit-error-ratio delivers the reliability and performance for high-
bandwidth services and improved data-grooming effectiveness.
• reduces circuit pack requirements. Fewer connections promote enhanced
reliability and performance
If an existing office needs to expand, growth is accommodated by easy, plug-

in provisioning.
The ENET is designed for modular growth:

• can be expanded from 4000 channels to 128,000 channels in 2000-
channel increments for the peripheral-link paddleboards
For the crosspoint circuit packs, the ENET can be expanded in 4000-
channel increments for the first 32,000 channels and in 16,000-channel
increments thereafter.
To ensure reliability, duplicated ENET planes are configured.

The single-cabinet ENET is equipped with a minimum of one shelf per plane
and is expandable to two shelves per plane.
In the dual-cabinet configuration, each cabinet is equipped with one to four

shelves with one plane per cabinet.
When required, and with no down time, a single-cabinet ENET can be

upgraded to a dual-cabinet ENET.
For a clearer understanding of ENET purpose within the system, look at

ENET and the system architecture. As a key signalling/connectivity
component for services, ENET interfaces with the DMS-Core (via the DMS-
Bus) and the peripheral processors (Figure 5-3).
Figure 5-3
ENET in system architecture
ENET in System Architecture
Service
Processing DMS-Core
DMS-Core File
File Processor(s)
Processor(s)
Hardware
DMS-Bus
DMS-Bus
Messaging/
Connectivity
Hardware
Enhanced
Enhanced Network
Network (ENET)
(ENET)
Physical Link
Link
Peripheral
Peripheral Modules
Modules
Access Peripheral
Peripheral IOC
(PDTCs,
(PDTCs, DTCi,
DTCi, etc.)
etc.)
Hardware Processor
Processor
To/From To/From a To/From

Trunks CCS7 Network, etc. IODs
411-0930-001 12.03/EN February, 2001 Lesson 5 Enhanced Network (ENET) 5-5
Hardware configuration 5
ENET cabinets
A single cabinet configuration supports up to 64K channels, both planes are
housed in one cabinet. The dual cabinet supports up to 128K channels and
each plane is housed in a separate cabinet. Each ENET cabinet comes
equipped with a frame supervisory panel (FSP), a cooling unit and one ENET
shelf assembly. Up to four ENET shelves can be provisioned per cabinet
(Figure 5-4).
Figure 5-4
ENET cabinet for SuperNode (one plane shown)
ENET Cabinet for SuperNode

PP PP
SS ENET 0.0 SS
UU UU
PP PP
SS ENET 0.1 SS
UU UU Enhanced Network Shelves
PP PP
SS ENET 1.0 SS
UU UU
PP PP
SS ENET 1.1 SS
UU UU
COOLING UNIT
64 K configuration (one cabinet)


Figure 5-5 illustrates the ENET shelf for the SNSE & MicroNode switches.
Figure 5-5
ENET shelf for SNSE or MicroNode
ENET Shelf for SNSE & MicroNode

FSP
P P P P
S S MS 0 MS 1 S S DMS-Bus
U U U U
P P P P
S S LIS S S LIS
U U U U
ENET
P P P P
ENET
S S S S
Plane 0 Plane 1
U U U U
P P P P
S S CPU 0 CPU 1 S S DMS-Core
SLM SLM
U U 0 1 U U
COOLING UNIT
Figure 5-6 shows the various ENET configurations.
Figure 5-6
ENET configurations
ENET Configurations
SuperNode 128K Channels
Plane 0 Cabinet Plane 1 Cabinet
Shelf 0 Shelf 0
Shelf 1 Shelf 1
Shelf 2 Shelf 2
SuperNode Shelf 3 Shelf 3 SNSE

64K Channels 16K Channels
Shelf 0 MS MS
Plane 0 LIS
Shelf 1
Plane Plane
Shelf 0
Plane 1 ENET shelf 0 1
Shelf 1 CM/SLM CM/SLM

ENET shelf layout 5

The ENET shelf, is the basic building block of ENET. Each ENET shelf
supports a 128K-by-32K time switch. Four shelves provide two planes of a
64K channel switching matrix or one plane of a 128K channel switching
matrix.
As shown in Figure 5-7, each shelf consists of the following:

• set of standard provisioned circuit packs that provide a shelf processor, its
associated shelf Reset/remote Terminal Interface (RTIF), paddleboard, a
message/clock pack and shelf power supplies.
• provisionable packs, including packs to interface peripherals, crosspoints
circuit packs to accomplish the actual switching of the signal and
associated paddleboards to provide interface to switch peripherals. The
crosspoint circuit packs and their paddleboards are provisioned according
to the capacity needs of the individual application; however, there is a
minimum requirement of four crosspoint packs.
Figure 5-7
ENET shelf layout
ENET Shelf Layout

REAR
07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32
R I F I I I I I I I F F F F F F F F I I I I I I I I
T / i / / / / / / / i i i i i i i i / / / / / / / /
I F l F F F F F F F l l l l l l l l F F F F F F F F
F l l l l l l l l l
e e e e e e e e e
r r r r r r r r r
B A C K P L A N E
P P P C X X X X X X X X F F F F F F F F X X X X X X X X P P
o o r l p p p p p p p p i i i i i i i i p p p p p p p p o o
w w o o t t t t t t t t l l l l l l l l t t t t t t t t w w
e e c c l l l l l l l l e e
r r e k t t e e e e e e e e t t r r
s & e e r r r r r r r r e e
C C s M r r r r C C
o o o s m m m m o o
n n r g n n
v v v v
01 14 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 36
Circuit Pack FRONT
Control and messaging 5

Each ENET shelf has a local processor card that is responsible for control and
maintenance of the shelf. This processor is directed by messages from the
DMS-Core that are routed through the DMS-Bus.
The processor card communicates with the crosspoint cards using a 16-bit
address bus and an 8-bit data bus. Up to 64 fibers terminate on an ENET
shelf. Two of these fibers are reserved for messaging to the DMS-Bus. One
link is connected to the DMS-Bus plane 0 and the other to plane 1.
Interface to PMs 5
ENET supports the option of interfacing PMs through the DS-30 copper
interface. However, to make full use of ENET capacity and performance, a
DS-512 fiber optic interface is typically provisioned for extended peripheral
modules (XPMs), such as PDTCs.
Interface to MS 5
Two major enhancements to the DMS-Bus have been introduced with the
ENET:
• The physical communication links between MS and ENET are DS-512
fiber optic connections. PMs connected to ENET are assigned
independent MS ports on each plane.
• Each ENET shelf is independently synchronized to the MS. The message/
clock card is responsible for synchronization and clock timing for the
ENET shelf. The message/clock card connects a DS-512 fiber link from
each plane of the message switch. The fiber link provides the connection
for the timing and control signals to be sent between the ENET and the
MS.
PM synchronization 5
PMs attached to ENET are also synchronized via the fiber links between the
ENET and the PMs.

Shelf communication (V-Bus & H-Bus) 5

Incoming data is passed between shelves in the ENET over the vertical bus
(V-Bus) connected to each of the crosspoint cards.
Outgoing data is passed within a shelf on the horizontal bus (H-Bus)

connected to each of the crosspoint cards.
As shown in Figure 5-8, traffic enters ENET from PMs by way of fiber DS-
512 or copper DS-30 links. Under the control of the CM and the local ENET
processor, crosspoint circuits switch the signal to the appropriate PM.
Figure 5-8
Block diagram of ENET architecture
Block Diagram of ENET Architecture

To DMS-Core
64-port Card
DMS-Bus DS-512 Interface
Plane 1
H-Bus
DS-512 I/F RTIF
Crosspoint Up to 16 Crosspoint ENET

Card Message/ Processor
Card Per Shelf
Clock Card
•••
Memory
Copper ENET Shelf

DS-512 I/F
DS-30 I/F
Plane 0
V-Bus To PMs To PMs

to Other
ENET
Shelves
ENET operation 5
ENET performs the actual switching of channels in the crosspoint circuit
pack. The switching process can be visualized (Figure 5-9) as a grid or a
squared matrix, formed by the vertical and horizontal buses in the ENET
cabinet. The H-Buses run between and connect the crosspoint cards on each
shelf. V-Buses run between and connect the ENET shelves in an ENET
cabinet.
Unswitched channels enter through the ENET paddleboards onto the ENET
V-Bus. The unswitched channels on the V-Bus are written into a double-
buffered memory in each crosspoint card. (The connection-memory control
on the crosspoint card itself manages this read-process at the core of the
single-stage time switch. The connection-memory control is updated by
messages from the CM, which are in turn interpreted by the local ENET
processor). From this memory, the appropriate crosspoint circuit pack takes
unswitched channels from the V-Bus and feeds them to the appropriate H-
Bus in the appropriate time slot. From the H-Bus, it goes back through the V-
Bus, where it is transmitted through the paddleboards to the appropriate
terminating PM.
Figure 5-9
ENET single-stage switch
ENET Single-Stage Switch

H-Bus
Paddleboards
Fiber Links
Crosspoint V-Bus
Circuit Packs
ENET Shelves Fiber Links

ENET crosspoint cards & I/F paddleboards 5

Figure 5-10 is a block diagram of one plane of a four shelf ENET switching
matrix showing the:
• crosspoint circuit cards and their shelf and slot position
• H-Busses and V-Busses that connect the crosspoint cards
• quad interface paddleboards connecting each crosspoint circuit card to its
associated PM
Figure 5-10
ENET crosspoint cards & I/F paddleboards
ENET CrossPoint Cards & I/F

2K I/F 2K I/F
Paddleboards 2K I/F
Sh 0 HBUS 0
9 10 11 12 13 14 15 16 25 26 27 28 29 30 31 32 HBUS 1
Sh 1 HBUS 2
HBUS 3
Sh 2
HBUS 4
HBUS 5
Sh 3 HBUS 6
9 10 11 12 13 14 15 16 25 26 27 28 29 30 31 32 HBUS 7
VBUS 0 VBUS 1 VBUS 2 VBUS 7
ENET switching examples 5

Figure 5-11 shows PDTC 3 connecting to PDTC 5 using shelf 3 slot 9 as the
switching card.
Figure 5-11
ENET switching example 1
ENET: Shelf 3 Slot 9 Switching Card

PDTC 5
Sh 0 HBUS 0
9 10 31 32 HBUS 1
Sh 1
Sh 2
PDTC 3
Sh 3 HBUS 6
9 10 31 32 HBUS 7
VBUS 0 VBUS 7

Figure 5-12 shows PDTC 3 connecting to PDTC 5 using shelf 0 slot 32 as the
switching card.
Figure 5-12
ENET switching example 2
ENET: Shelf 0 Slot 32 Switching Card

PDTC 5
Sh 0 HBUS 0
9 10 31 32 HBUS 1
Sh 1
Sh 2
PDTC 3
Sh 3 HBUS 6
9 10 31 32 HBUS 7
VBUS 0 VBUS 7

1. What is the purpose of the ENET?
2. What is the maximum number of channels that a single ENET cabinet

configuration can support?
3. What is the function of the H-Bus and the V-Bus?
4. What is the purpose of the crosspoint card?
5. What are the advantages of ENET?
6. What is the maximum number of DTCs that can physically be connected

to a 16K SNSE ENET?

Lesson 6
Peripheral Modules (PMs)
Objectives 6
will be able to:
• identify the Peripheral Modules (PMs) commonly found in Nortel DMS-

MSC/HLR
• define a DTCO
• define the functions of the PCM-30 Digital Trunk controller (PDTC),
PCM-24 Digital Trunk controller (DTC) and Digital Trunk controller
ISDN (DTCi)
• describe the function of the following PMs:
— Link Peripheral Processor (LPP)
— Maintenance Trunk Module (MTM)
— Office Alarm Unit (OAU)
— Digital Recorded Announcement Machine (DRAM) or Digital Trunk
Module (DTM)
— Integrated Service Module (ISM)

6-2 Peripheral Modules (PMs) Nortel Networks Confidential
Peripheral modules 6
The DMS-MSC/HLR family of PMs is the basic access vehicle for most
services.
In general, PMs provide low level scanning, signaling, call processing, and
maintenance functions in support of the higher level processing done by the
CM. The PMs used in the GSM network include the following equipment:
• PCM-30 Digital Trunk Controller (PDTC), PCM-24 Digital Trunk
controller (DTC), Digital Trunk controller ISDN (DTCi)
• Link Peripheral Processor (LPP)
• Maintenance Trunk Module (MTM)
• Office Alarm Unit (OAU)
• Digital Recorded Announcement Machine (DRAM) or Digital Trunk
Module (DTM)
• Integrated Service Module (ISM)
Examples of these PMs are shown in Figure 6-1.
Figure 6-1
Typical PMs cabinets
Typical PM Cabinets
CDTCO Cabinetized CTME Cabinetized
Digital Trunk Controller for Offshore Trunk Module Equipment
FSP FSP
P P PP P P P P
S S SS S S Maintenance S S
UU UU U U U U
Trunk Module
PCM30 Digital
Trunk Controller
PDTC 1
PP PP P P P P
SS SS S S Maintenance S S
UU UU U U
U U Trunk Module
PP PP P P P P
UU UU U U U U
Trunk Module
PCM30 Digital
Trunk Controller
PDTC 0
PP PP P P P P
UU UU U U U U
Trunk Module
COOLING UNIT COOLING UNIT
411-0930-001 12.02/EN December, 2000 Lesson 6 Peripheral Modules (PMs) 6-3
Nortel Networks Confidential Peripheral Modules (PMs) 6-3
Each PM has a Peripheral Processor (PP). The PP performs local processing

actions within its PM and controls the flow of messages between the PMs and
the DMS-Core.

PM network interface 6
As shown in Figure 6-2, all PMs connect to the rest of the switch via the
ENET shelf, by duplicated links (that is, one link to plane 0 and another to
plane 1).
These links are either DS-30 or DS-512 and carry both speech and message
channels. Each channel connection between a PM and the network consists of
separate transmit and receive paths.
Figure 6-2
PM connections
PM Connections to ENET
MS
CM ENET ENET
Plane 0 Plane 1
PM PM
Unit 0 Unit 1
411-0930-001 12.03 February, 2001 Lesson 6 Peripheral Modules (PMs) 6-4
Voice access PMs 6

Several PMs are available in GSM for use in providing voice trunk access to
the DMS-MSC. These PMs are:
• PCM-30 Digital Trunk Controller (PDTC)
• PCM-24 Digital Trunk controller (DTC)
• Digital Trunk controller ISDN (DTCI)
The PMs adapt the various characteristics of the trunks to the DS-30 format
used by the DMS-MSC. DS-30 is a 32-channel, 2.56-Mbps, Time-Division
Multiplex (TDM) format.
The DMS-MSC uses 30 of the 32 channels for speech paths between the PM
and the network. The remaining two channels provide paths for an internal
message system (PM to PM or CM) and an external C7 messaging system.
The two message channels provide control and communication interfaces
between the PM and the Front-end.
Each 32-channel connection between a PM and the network consists of

separate transmit and receive paths. Each path is made up of two wires. One
32-channel connection has four wires (two transmit wires and two receive
wires). Each set of 32-channel, four-wire, transmit and receive paths is
referred to as a speech link. A port connects the speech link to the PM or the
Network. Individual microprocessors control the PMs.
These microprocessors, also known as peripheral processors, are responsible

for the following actions:
• generating tones
• collecting digits
• scanning trunks
• messaging to and from the front-end

PCM-30 Digital Trunk Controller (PDTC)

The PDTC is a dual-shelf digital trunk access peripheral, designed to provide
the necessary functions for supporting trunk terminations to the outside
world. The two PDTC shelves are referred to as Unit 0 and Unit 1. The dual
shelves operate in hot standby mode. One shelf's processor is active,
providing the necessary processing and control functions, while the adjacent
shelf processor is in a hot standby mode and is able to takeover if a fault
occurs to the active shelf's processor.
The PDTC provides interfaces for a maximum of 16 peripheral side ports

from PCM-30 links to one DS-512 speech links. The PCM-30s interface with
direct digital links to digital trunks, FX, PBX/CO or special service lines.
Communication to the network module is accomplished with two message
channels, one channel on each of the two network port pairs to a PDTC (both
planes). In the PDTC, the interface cards to the PCM-30 links are not fully
duplicated; they are provided on a per-shelf basis, each shelf controlling up to
eight PCM-30 interface cards. (Each interface card has two ports.) In the
event of a power converter failure, the mate power converter supplies power
to all the PCM-30 cards in its mate shelf (Figure 6-3).
8 PCM-30 ports x 30 channels = 240 channels per unit
2 units per PDTC = 480 channels
Unit 0
Unit 1
Nortel Networks Confidential
Figure 6-3
0X50AA NIL 0X50AA NIL
1 2
1 2
6X27BB NIL 6X27BB NIL
PDTC dual shelf
3 4
3 4
5 6
5 6
411-0930-001
7 8
7 8

12.03
GSM
MX77AA NIL MX77AA NIL
6X44EA NIL 6X44EA NIL
6X92CA NIL 6X92CA NIL
February, 2001
0X50AA NIL BX01BA NIL
6X69LB NIL 6X69LB NIL
PDTC Dual Shelf
6X41AB NIL 6X41AB NIL

6X40FB 6X40GA 6X40FB 6X40GA
NIL NIL
2X70AF NIL 2X70AF NIL
Lesson 6 Peripheral Modules (PMs)
9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27
9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27
NIL NIL
GSM DMS Overview Student Guide

6-5
FRONT
FRONT
REAR
REAR
Peripheral Modules (PMs)
GSM12
6-7
PDTC to ENET message links

Figure 6-4 illustrates the PDTC to ENET message links.
Figure 6-4
PDTC to ENET message links
PDTC to ENET Message Links

P Side C Side 1 DS512 =
16 DS30
1
15 11 7 3
3
ENET 1
14 10 6 2 5
13 9 5 1 4
ENET 0
2
12 8 4 0 0
1 DS512 =
16 DS30
PCMs
Digital Trunk Controller ISDN (DTCi)

The DTCi is identical to the PDTC. The DTCi peripheral integrates into the
DMS-MSC in the same manner.
The DTCi:
• interfaces to all incoming and outgoing ISDN PRI trunks
• is configured as an XPM with a Unified Processor (UP) and an enhanced
ISDN signaling preprocessor (EISP) card (NTBX01AB)
• uses the EISP to provide D-channel processing for ISDN PRI and the
6X44EA Time Switch (TS) for data and A-law/µ−law PCM voice
conversions
The Universal Tone Receiver (UTR) is used for inband digit collection.
Provisioning of trunks other than ISDN PRI is not supported on the DTCi.
Other PMs 6
Several PMs are available in GSM for use with the DMS-MSC for functions
other than voice trunk access:
• MTM
• ISM
• DRAM, EDRAM or DTM
• IOM
Maintenance Trunk Module (MTM)

The MTM provides an interface between the switch and the test and service
equipment.
In addition, the MTM acts as a switching center for control messages

exchanged between the central control complex and individual test or service
circuit cards. It connects as many as 28 service circuits including alarms,
tones, MF and DTMF receivers and test facilities. Test facilities consist of
trunks and built-in test equipment that measures loss and noise and detects
tones and voltage.
Because of the special test and service circuit cards used, the MTM requires
two extra buses for directing data exchange between the test circuit cards and
two power converter cards. The DMS-MSC supports the Cabinetized Trunk
Module Equipment (CTME) with up to four MTMs (Figure 6-5).
Office Alarm Unit (OAU)

An OAU is similar to the MTM in that it is equipped with circuit cards that
provide an interface between various types of office alarm circuits. The OAU
converts analogue trunk speech and signalling information to or from a digital
stream. Also, the OAU connects as many as 28 analog trunks to network ports
by means of a DS30 link to network.

Integrated Service Module (ISM)

The ISM is a DMS shelf that replaces the MTM.
Figure 6-5
Integrated Service Module
Typical ISM Configuration
NIL
NIL
NIL
NIL
NIL
NIL
NIL
NIL
NIL
NIL
NIL
NIL
NIL
NIL
NIL
NIL
NIL
NIL
NIL
NIL
REAR
2X75BA
0X50AC
0X50AC
0X50AC
2X71AA
2X71AA
0X50AC
0X10AA
0X50AC
0X10AA
3X83AC
0X50AC
3X83AJ
FX42AA
1X80AA
2X57AA
5X30BA
0X10AA
4X45AA
FX43AA
FRONT
1 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21
Transmission termination trunk
Transmission termination trunk
Blank Card
OAU alarm transfer card

Enhanced digital test unit card
Controller card
ISM DC Converter
Blank Card
Blank Card
Blank Card
Blank Card
Up to 14 scan point/card
Scan point card
Scan point card
Signal distributor card

Loop around test
Blank Card
OAU dead system card

EDRAM
HSET
The ISM is designed to provide one-to-one shelf replacement of the MTM

shelves. The ISM increases capacity for service circuit utilization per shelf by
25 percent or higher. The ISM processor pack provides a super set
functionality for the MTM four circuit packs: NT0X70, NT2X45, NT2X53,
NT2X59. The ISM processor also combines the functionality of NT2X59 and
NT4X65 circuit packs.
ISMs are available in a cabinetized ISM (CISM) with an NTFX40AA card,

consists of three ISM shelves, one Modular Supervisory Panel (MSP) shelf and
one cooling unit shelf as shown in Figure 6-6.
The ISM back panel provides 21 slots, of which 16 slots are functionally
compatible with the slots in the MTM for supporting service circuits and PM
type service circuits, two slots dedicated for PM service circuits, two slots
dedicated for the ISM DC converter and one slot dedicated for the ISM
processor. In the ISM shelf, the cards are configured from right to left, which
is opposite from the MTM configuration.
Table 6-1 lists the existing MTM PEC codes to the corresponding new ISM
codes.
Table 6-1
MTM PEC codes to ISM codesTable 6-1
Original Card Name changed to

Multiline test unit analog card-NT2X10BA NT2X10BB
Metallic test unit analog card-NT4X98BB NT4X98BC
Office alarm unit dead system with common audibles NT3X82AF, AG, AH, AJ &
card-NT3X82AA, AB, AC, AD, AE AK respectively
Office alarm unit alarm transfer card-NT3X83AA, AB NT3X83AC & AD
respectively
Office alarm unit alarm sending card-NT3X84AA NT3X84AB
Office alarm unit alarm group card-NT3X85AA NT3X85AB
The IOM controller card (NTFX30AA) resides in slot 3 (or 3 and 4) of the
ISM shelf.
The IOM paddle board (NTFX31AA) is mounted in slot 3 of the backplane in

the rear of the ISM shelf. The storage media card (NTFX32AA), if provided,
resides in slot 4 and 5 of the ISM shelf.
The storage media card provides the interface to the DAT and DDU plug-in
units.

Figure 6-6
ISM cabinet & IOM
ISM Cabinet, ISM Shelf, and the IOM
F
FS P X
3
1
ISM Shelf Rear
F FX32AA (Frame Card)

X
3
0 FX32BA (Disk)
Front A
A
ISM FX32CA (Tape)
Cabinet
Slots 3 4 5
FX30AA
+ FX32AA
IOM Packs =
+ FX32BA
+ FX32CA
Digital Recorded Announcement Machine (DRAM)

A DRAM is a PM in an MTM configured as a DRAM shelf (NT2X58AG).
The DRAM consists of one controller card (NT1X75BA) and from one to
eight memory cards (NT1X76xx or NT1X77AA).
The DRAM provides up to 64 recorded announcements that are stored in

digital format. The DRAM provides recorded announcements, stored in
digital format, that can be used on a stand alone basis or in conjunction with
other announcement machines. The programmable read only memory
(PROM) stores standard announcements, while the random access memory
(RAM) stores customer-specified announcements.
Enhanced Digital Recorded Announcement Machine (EDRAM)

An EDRAM is a stand alone PM that can coexist in an office already
equipped with DRAM. The EDRAM card can be plugged into any slot of an
MTM shelf or ISM. The EDRAM does not require an additional card.
The EDRAM card provides voice messages to the user.
• NT1X80AA provides 4.3 minutes of announcement time and 30

announcement channels
The EDRAM offers the flexibility of a DRAM shelf in a single circuit
pack.
• NT1X80BA offers four (4) times the capacity of the NT1X80AA

Note: An EDRAM is also known as Digital Trunk Module (DTM).

Common Channel Signaling # 7 (CCS7) networks 6

CCS7 is a message-based signaling system that supports greater volumes of
customer information and provides network intelligence to offer services on a
network-wide basis. As a result, CCS7 plays an important role in system
integration and integrity.
CCS7 link expansion and NIU is supported by GSM. It increases the number
of NIUs in a GSM office datafillable from 9 to 18. It also increases the number
of CCS7 links datafillable in a GSM office from 108 to 180. This is only possible
when:
• node is a World Trade Product
• switch is datafilled exclusively SSP (there is not INode datafill)
• T1-DTCs are not datafilled in the office
European customers should have end offices with a higher NIU and CCS7
link limit. The European network architecture is primarily fully associated
and an increased link-limit would allow a single end-office to connect to a
greater portion of the network via associated links.
The PM used to interface with the CCS7 network is the Link Interface Unit #
7 (LIU7). The LIU7 circuit packs are mounted in specific cabinets called Link
Peripheral Processor (LPP)
Link Peripheral Processor (LPP)

The LPP is an MS-based peripheral that provides the signaling interface
between the DMS-Core and the CCS7 signaling network.
Figure 6-7 shows the LPP cabinet.
Figure 6-7
LPP cabinet
LPP Cabinet
Frame Supervisory
Panel
Local Local
Message Message Local
Switch Switch Message Switch
0 1 Shelf 0
Link Interface
Shelf 1
Link Interface Units
Link Interface
Link Interface Units
Shelf 2
Link Interface
Link Interface Units Shelf 3
Cooling Unit
The LPP cabinet provides the following interconnections:

• CCS7 signaling links:
— to the other nodes that compose the GSM network
— to the PSTN
— to the Base Station Controllers (BSC)
• TCP/IP link
— to the InterWorking Function (IWF) via a Local Area Network (LAN)
Note: The PM used to interface with the LAN is the Ethernet Interface
Unit (EIU).

Figure 6-8
Link Peripheral Processor interconnections
LPP Interconnections
DMS-MSC
DMS-core AP I/O Equip
MS
Signaling
ENET
TCP/IP on Ethernet
IWF
CCS7 on V.35
DMS-HLR LPP
CCS7 on V.35 MTM
DMS-MSC CCS7 on a PCM
CCS7 on a PCM PDTC

BSC
Link Interface Unit #7 (LIU7)

Figure 6-9 shows the Link Interface Unit.
Figure 6-9
Link Interface Unit
Link Interface Unit
Rear Part PB
MTP1
Front Part
ST IPF
MTP2 MTP3
The LIU7 is a two-slot configuration, meaning that each LIU7 is composed of

two cards in front and one card in back. These three cards are as follows:
• Integrated F-Bus/processor (IPF) (NTEX22)
Provides both message processing for its associated signaling data link
and an interface to each of the two F-Buses. Both F-Bus interfaces are
duplicated and fully independent. This duplication ensures that, in the
event of an F-Bus failure, the IPF card can still access the other F-Bus and
operation is not interrupted.
• Signaling Terminal (NT9X76)
Provides error detection and correction and various alignment and flow
control function. This card has two processors and performs all of the
level 2 functions of the MTP.
• Paddleboard (either the NTEX26AA or the NT9X77AA)
Provides the physical interface to the signaling data links. The two cards
are for the following configurations:

— NTEX26AA - used for channelized access

— NT9X77AA - used for V.35 connectivity
Note: A channelized access LIU7 needs an additional PM to operate
correctly. The PM is called Network interface Unit (NIU) and provdes
connectivity to ENET.
LIS shelf in a SNSE cabinet

As shown in Figure 6-10, a Link Interface Shelf (LIS) is located in shelf
position 26 of the SNSE cabinet. In addition to this shelf, six card slots of the
ENET shelf located in shelf position 13 are considered an extension of the
LIS shelf.
Figure 6-10
Link interface shelf in a SNSE cabinet
Link Interface Shelf in a SNSE

FSP
PP P P
SS MS 0 MS 1 S S
UU UU
PP P P
SS Link Interface Shelf S S
UU UU
PP L L P P
I ENET 0 ENET 1 I
SS U U S S
UU 0 16K 16K 1 U U
PP P P
S S SLM CPU 0 CPU 1 SLM S S
UU 0 1 UU
COOLING UNIT
Note: The LIUs on the ENET shelf cannot support channelized access
only V.35 or can be replaced by EIU.
LIS shelf description

The LPP consists of two types of modules, the Link Interface Module (LIM)
(or Local Message Switches (LMS)) and Application Specific Units (ASU).
The SNSE integrates the LIM functions and the message switch functions on
the same DMS-bus hardware.
The SNSE LIS is a Link Interface Shelf (LIS) provisioned in one shelf of the
DMS SNSE core cabinet. A resident rate adapter in each message switch
enables the link peripheral processor functionality to be provided in the DMS
SNSE configuration, without using separate Local Message Switches (LMS).
No redundant access is provided between the MSs and the F-Bus; Inter-
Message Switch Links (IMLs) are used for this function. Otherwise, the
functionality of the LPP in the SNSE configuration is the same as the regular
LPP.
The SNSE LIS can be equipped with up to 12 LUI7 or EIUs.
Frame transport bus (F-Bus)

The F-Bus is an 8 bit wide version of the MS Transaction Bus (T-Bus). The
F-Bus is used to provide communication between a LMS and the 3 LIS
cabinets where it reaches the provisioned LIU7. For reliability reasons, there
are two F-Buses (1 per LMS) which are used in loadsharing mode.
Network Interface Unit (NIU)

The NIU transfers data between the network and the Channel bus (C-Bus).
NIUs reside on the same shelves as the LIU7s, and one NIU is allowed on
each shelf. NIUs are located in the middle of each shelf and are composed of
three cards per unit, two in the front and one in the back.
Note: When NIUs are installed, the maximum number of LIU7s available
drops from 12 ro 10 on a LIS and from 36 to 30 overall within one LPP
cabinet.
Channelized Access
Channelized access is the name given to CCS7 signaling using NIUs to
transfer signaling links to LIU7s.
Figure 6-11 shows how messages enter an LIU7 via an NIU: this method of
entering an LIU7 is channelized access.
A signaling message goes through the following steps to reach an LIU7 via
channelized access:
1. signaling message enters switch via a PDTC
2. signaling message enters both network planes
3. signaling message enters an NIU from one network plan
4. signaling message uses both C-Bus links to enter an LIU7

5. LIU7 chooses one of the C-Bus links (the other remains on stand-by)
Note: The BSCs do not support V.35, 50. Channelized access must be
used for the A-interface connection.
Figure 6-11
Entering an LIU7 via channelized access
Entering an LIU7 via Channelized Access

DMS CORE (CM)
DMS BUS (MS)
LPP ENET
LMS 0 LMS 1
DS30, DS512
LIS 1 DS30
PDTC
LIS 2
LIS 3 N N L LL
I I I I I
U U U UU
0 1
LIU7s which use the NIU must be equipped with the NTEX25 C-Bus
interface paddleboard. The LIU7 puts data on the C-Bus which the NIU
transfers to the network through one to four DS-30 links on its channel bus
controller paddleboard.
As shown in Figure 6-12, the NIUs and the LIU7s share the F-Bus and the C-
Bus. However, where the F-Bus is common to all shelves in a LPP, each shelf
has its own C-Bus. The C-Bus is used by LIU7s and NIUs for data only. Note
that NIU 0 only connects to C-Bus 0, and NIU 1 only connects to C-Bus 1.
LIU7s use the F-Bus for both data and maintenance messaging, but the NIUs
only use the F-Bus for maintenance messaging.
Figure 6-12
NIU and LIU7 connections in the LPP
NIU and LIU7 Connections in the LPP

LMS 0 LMS 1
FBUS 0
FBUS 1
LIU7 . . . LIU7 NIU NIU LIU7 ... LIU7

Unit 0 Unit 1
CBUS 0
CBUS 1
NIU cards
The three cards which comprise an NIU (one unit) are as follows:
• NIU Processor - NTEX22
• C-Bus interface - NTEX25
• paddleboard - NTEX28
Note: NIUs are always deployed in pairs. A fully provisioned NIU pair
consists of two of each card listed above, for a total of six cards.

Mobility management unit (MMU) 6

The MMU system enables the DMS-MSC to achieve scalable Mobility
Management capacity. The MMU program enhances the overall system
performance by migrating events, not directly related to the establishment of
voice calls, to an auxiliary scalable bank of Application Specific Units
(ASUs). Both the mobility management functionality and the VLR database
are moved to the ASUs, offloading work from the Computing Module (CM)
processor. This frees up processing resources on the CM, permitting the MSC
to process more calls, thus increasing its capacity.
Figure 6-13
MMU functionality
MMU Functionality
DMS
DMS BUS
BUS (MS)
(MS)
VLR
VLR Mobility
Mobility Mgmt.
Mgmt.
LPP
DMS-CM
Trunk Call Trunk Call M+N
MMUs
Processing Processing
Connector Management
Distribute this
Work to MMUs
An MMU consists of a hardware component and assoicated software. the first

release is the DMS 128 Mb ASU, NTEX22FA. The software load consists of
necessary components for CallP, MDM, and MAP runtime systems.
A Mobility Environment Locator (MEL) provides control and routing

capability to the distributed VLR database located on the ASUs. A new call
processing protocol supports new messaging needs imposed by the nature of
distributed call processing.
Figure 6-14
MMU simplified functions. location, and flow
Functions, Locations, and Flow
CM
MS Call
MAP / MM
MEL
Sub to MMU
VLR
Virtual MMU
LIM
MAP / MM
Router
MEL VLR
VLR
SCCP
SCCP
MTP LIU7 MMU
LPP
Software components related to MAP message encoding and decoding are

also moved to the ASUs. Efficiencies to transaction handling are realized by
locating upper layer protocols encoding/decoding to the VLR database.
The MMU is an optional element, not mandatory for DMS-MSC call

processing. Once MMUs are activated in the system, MM and MAP
transaction processing must be entirely MMU based. The CM is not intended
to participate in the mobility aspects of any transactions started after the
activation of MMUs.
Check out
Each MMU possesses a local VLR. Active subscribers are assigned, or
checked out, from the CM VLR to an MMU VLR for mobility management
and call processing. While a copy of the VLR tuple is retained on the CM, it
is considered stale and not used to process any transaction requests.
Subscribers are checked out to the least busy MMU. As a result no fixed
partitioning of the VLR database to MMUs exists. A VLR tuple is checked
out to a single MMU at any one time, and once a tuple has been checked out,
all subsequent requests for the corresponsing subscriber will be forwarded to
that MMU. Any request received at the CM for a subscriber whose VLR tuple

has not been checked out to an MMU, an MMU is selected, the VLR data is
copied to the MMU VLR, and the corresponding request is processed.
The MSC capacity gain from the MMU program is directly driven by the
amount of work offloaded from the CM processor. The amount of offloaded
work is a function of the amount of mobility management work performed on
the MSC, which is dependent upon the site’s call profile. As a result, multiple
MMUs are required to realize capacity gains. The number of MMUs required
is a function of VLR size and the mobility profile of the site. MMUs should
be provisioned for M+N sparing. Physically, a minimum of two MMUs per
system and a maximum of 14 are supported.
Figure 6-15
Hardware configuration with MMUs
Hardware Configuration with MMUs
SLM CM
MS
LMS ENET
ENET
NIU LMS
MMU-1
LIU7-1
MMU-2
NIU
MMU-1
LIU7-2
MMU-3 XPMs
XPMs
LIU7-1
LIU7-3 MMU-2
MMU-4
LIU7-2
. . MMU-3
CBUS
FBUS
. .
. LIU7-3 . MMU-4
. .
CBUS
FBUS
LIU7-n
.MMU-m .
. .
LPP1
. LIU7-n
MMU-m
.
. LPPn
1. How is the DTCO linked to the rest of the subsystems within the switch?
2. What is the purpose of the PDTC?
3. What is the purpose of the LPP?
4. What is the purpose of the OAU?
5. What is the purpose of the MTM?
6. By how much does the ISM increase capacity for service circuit
utilization per shelf?
7. List the tables associated with GSM peripherals.
8. List and briefly explain the two available ISMs.

Lesson 7
SuperNode Data Manager/Fault Tolerant
(SDM/FT)
Objectives 7
will be able to:
• describe the purpose of the SDM/FT
• describe the platform hardware of the SDM/FT
• explain OAMP
• describe the OMC-S applications
• describe the HLR-Provisioning Server (HLR-PS) application
• describe the Call Intercept System application

7-2 SuperNode Data Manager/Fault Tolerant (SDM/FT) Nortel Networks Confidential
SDM/FT cabinet 7
The SDM/FT cabinet supports the following software:
• operating system services
Operating system services include system kernel, data reliability, and
process control services.
• SDM-internal software
The internal services include fault detection, system administration, and
maintenance services.
Figure 7-1 shows the software layers of the Operation Administration

Maintenance and Provisioning (OAMP) applications.
Figure 7-1
OAMP platform software
OAMP Platform Software

OMC-S Application HLR-PS Application CIS Application
OMC-S Base HLR PS Base CIS Base
SDM Software Layer (UTL)
SDM Software Layer (Base)
Logical Volume Manager
AIX
FTFX Unix Kernel

411-0930-001 12.03 February, 2001 Lesson 7 SDM-FT Cabinet 7-3
The SDM/FT can support the following OAMP services:

• OMC-S (DMS-MSC, DMS-HLR, DMS-MSC/HLR)
• HLR-PS (DMS-HLR, DMS-MSC/HLR)
• Call Intercept (DMS-MSC)
In a future release, the DMS/FT will support the Billing Server Application:
SBA SDM Billing Application (DMS-MSC)
Nortel Networks Confidential SuperNode Data Manager/Fault Tolerant (SDM/FT) 7-3
SDM/FT overview 7
The SDM/FT is a UNIX-based computing platform on which a variety of
services and applications can be hosted to provide OAMP services.
The SDM/FT primary advantages are its continuously available computing

resources and improved connection to the DMS-Core.
The Fault Tolerant architecture implemented in the SDM/FT assures a

reduced risk of hardware failure and, a lower risk of OAMP data and service
loss.
General Description
The SDM/FT is based on a Motorola PowerPC-based dual-processor system.
System I/O is achieved using fault tolerant I/O buses, mirrored disk storage,
and redundant communications links.
SDM/FT hardware is mounted in a C28 Model B DMS Streamlined Cabinet.

Cabinet mounting is required due to the depth of the SDM/FT.
The following are key features of the SDM/FT hardware platform:

• redundant, master-checker CPU modules that run in lock-step to provide
fault tolerance
• three available DRAM memory configurations: 128 Mbytes (baseline),
256 Mbytes, and 512 Mbytes
• redundant multi-function input/output (MFIO) hardware in separate I/O
domains assures continuously available disk storage, DAT drive access,
and Ethernet connectivity to the operating company LAN
• CPU modules communicate with I/O domains via independent I/O buses
• expandable mirrored disk storage from 2.0 to 22.0 GBytes on each I/O
domain
• redundant DS512-based hardware for SDM-CM communications
• system-wide in-service FRU replacement
• redundant individually powered fan trays
• redundant powering for CPU modules and, independent powering for all
I/O domains

Figure 7-2 illustrates the SDM/FT cabinet.
Figure 7-2
SDM/FT cabinet
SDM-FT Platform
MSP
Shelf 2
I/O Expansion Chassis
(optional)
1 2 3 4 5 6 7 8 9 10111213141516
Shelf 1
Main Chassis
1 2 3 4 56 78 10
9 11
1213141516
Cooling Unit
Fault tolerant architecture

Fault tolerance is achieved by assuring that no single hardware failure can
cause an SDM/FT system outage or the failure of an intended service. The
SDM/FT is equipped with redundant hardware components.
Figure 7-3
SDM-FT architecture
SDM-FT Fault Tolerant Architecture

- 48 V dc Maintenance and Power Bus A
A Feed
I/O Domain 0
Computing Core
Disk
Comm & I/O
Subsystem
CPU 0
Dual Fault Tolerant I/O Buses
CPU 1
Disk Comm & I/O
Subsystem
I/O Domain 1
- 48 V dc
B Feed
Maintenance and Power Bus B
Table 7-1 lists the SDM-FT parts.
Table 7-1
SDM-FT parts
Part Description
Computing Core consists of two CPU modules which operate in full

synchronization, with one unit as master and the other in
standby. If the master CPU fails or is removed from service,
the standby CPU automatically takes over operation. When
the out-of-service CPU is returned to service, it is
automatically re-synchronized with the other CPU. In both
cases, the transition occurs without service interruption and is
transparent to application users.

Part Description
DAT Drives Two digital audio tape (DAT drives) are provided on the SDM/
FT for software/data loading and backup. One DAT drive is
located in each I/O domain for reliability. Both DAT drives are
accessible by either CPU.
Dual-bus The SDM/FT employs dual fault tolerant maintenance, power,
Architecture and I/O buses to provide uninterrupted service in the event of
any single hardware failure on the system.
Hard Disk Storage These disks are mirrored: all data is written to and available
from both disks.
• In normal operation (mirrored storage) all system data is
written simultaneously to both disks. Reads from disk are
alternated between the two disks.
• When one disk fails, it is manually removed from service,
or is unavailable due to loss of one power feed. All system
software and data are available from, and written to, the
remaining disk. When the out-of-service disk is returned to
service, all data is automatically synchronized between
the two disks and mirrored operation resumes.
LAN Connectivity provides connectivity to the operating company LAN and is
Hardware also duplicated. These modules operate in active-standby
mode.
• If the active Ethernet link fails or becomes unavailable for
any reason, Ethernet traffic is automatically switched to
the standby link. The transition occurs without service
interruption and is transparent to application users. There
is no loss of data packets during the switchover.
DS512 provides DS512 connectivity to the DMS Message Switch
Connectivity (MS). It is fully duplicated on the MS and SDM sides of the
Hardware four links.
• In normal operation, traffic is shared across the four
DS512 links.
• In the event of failed or unavailable hardware on the MS,
the SDM, or the physical links themselves, full CM-SDM
communications can continue without service interruption
or impact to application users with a minimum of one in-
service DS512 link.
Power The SDM/FT is powered by two -48Vdc power feeds. The
system is capable of full operation on a single feed. While
operating on a single power feed, the computing core
operates in duplex mode; one input-output (I/O) domain
remains fully operational in simplex mode. The transition to
single-feed operation, and back to dual-feed operation, occurs
without service interruption or impact to application users.
Part Description
Cooling Each SDM/FT chassis is cooled by two fan modules which are
both active during normal operation. Each fan module
contains 3 fans. If either fan module in a chassis fails, is
removed from service, or is unoperational due to loss of one
power feed, the chassis can operate on a single fan module
without impact.
SDM/FT main chassis 7

The SDM/FT chassis assembly consists of a mid-mount backplane 16 one-
inch (25.4mm) front module slots, and 16 one-inch rear (personality) module
slots.
All modules are 6U (10.5 in.) in height. Modules requiring more than one slot
are multiples of one inch. The middle six slots are dedicated for three double
slot wide CPU modules. The center CPU position is not used on the SDM/FT
and is provisioned with filler plates. The five remaining slots on either side
from the two I/O domains. Figure 7-4 shows the SDM/FT main chassis
populated with its baseline module set.
Figure 7-4
SDM/FT main chassis
SDM-FT Main Chassis

Status
LEDs
Upper
Fan Tray
Module
MFIO controller modules

Lower
DS512 controller modules Fan Tray
Module
ESD Grounding
Point
CPU modules
Filler Plates

OMC-S application overview 7

Figure 7-5
OMC-S application overview
OMC-S Application Overview
OMC-S provides efficient Operations

and Maintenance capabilities via:
Q3
» Centralized management of
multiple network elements
» Powerful Fault and Performance
Management toolsets
» Easy to use GUI and pop-up on-
line help menus
FM agent FM agent
» PC-based platform utilizing Java PM agent PM agent
» Open Q3 interface
NES
411-0930-001 12.02/EN December, 2000 Lesson 7 SDM-FT Cabinet 7-7
The Nortel OMC-S product is designed to offer efficient operations and

maintenance capabilities.
Within a customer NSS, the OMC-S:

• allows a centralized management of multiple DMSs
• provides Operators with the following toolsets:
— Configuration Management
— Fault Management
— Performance Management
• takes advantage of the secure and powerful hardware, based on a SDM/FT
platform
OMC-S software architecture

The OMC-S Element Manager is composed of the following pieces of software:
• OMC-S Element Manager Application installed on a PC workstation
Also known as OMC-S Browser or OMC-S Client.
• SDM/FT agents installed on the SDM/FT

The OMC-S agents are also called OMC-S server.
Figure 7-6 shows the OMC-S Element Manager software location.
Figure 7-6
OMC-S software architecture
OMC-S Software Architecture
Workstation SDM-FT
Fault Mgt FM/PM/CIS
Configuration Mgt
SDM Agents
DMS
Performance Mgt
Windows NT
AIX Operating
System

OMC-S element manager application

The GSM OMC-S Element Manager manages the administrative and
maintenance operations within a Public Land Mobile Network (PLMN).
PLMNs consist of switching and radio subsystems.
This manual focuses on the OMC-S network that manages the GSM Network
and Switching Subsystem (NSS).
The OMC-S Element Manager application manages the network elements

and performs the following functions:
Configuration Management (CM) also known as Resource Discovery

application uses information available in tables and displays existing
elements in any managed DMS as shown in Figure 7-7. Fault Management
(FM) uses information available in Log Reports about alarms and displays
alarms and status on any managed DMS-MOI as shown in Figure 7-8.
Performance Management (PM) uses information available in Operational
Measurements (OMs) and displays performance metrics of any managed
DMS as shown in Figure 7-9.
Figure 7-7
Configuration management application
Configuration Management Application

The CM application maintains consistency between the switch
and the Managed Object Instances (MOIs).
Workstation
Configuration
Manager DMS-MSC/VLR
SDM-FT DMS-HLR/AuC
MOIs
MOI EM Server
Identification Application
Switch Elements
Containment Tree
Administrative & Availability status
Figure 7-8
Fault management application
Fault Management Application

The FM application monitors alarm states of the DMS elements,
using the Log Reports available in the DMS.
Workstation
Fault
Manager DMS-MSC/VLR
SDM-FT DMS-HLR/AuC
MOIs
Log Reports EM Server

Application
Switch Elements
Containment Tree
Administrative & Availability status

Figure 7-9
Performance management application
Performance Management Application

» Displays Operational Measurements (OMS) groups and
counters available in the DMS
» Proposes 2 levels for Performance Monitoring:
– Beginner with predefined studies
– Advanced with access to OM groups and counters
Workstation
Performance
DMS-MSC/VLR
Manager SDM-FT DMS-HLR/AuC
MOIs
OM groups EM Server
& counters Application
Switch Elements
Containment Tree
Elements with OMs
In addition, the OMC-S Element Manager application:

• serves as Graphical User Interface (GUI) to the SDM/FT and the switch
• provides Access to the elements from a Maintenance and Administration
Position (MAP) pass-through
HLR-PS functionality 7
The HLR-PS:
• provides access to the DMS-HLR database allowing subscribers and
subscriber data to be queried, added, modified and deleted
• provides provisioning operations related to Subscribers and Services can
be performed via the datafill of the DMS tables
• uses the powerful UNIX tools (NFS, scripts, FTP) to datafill tables
• allows the operating company to create simple text files complying the
MSP format (Mobile Subscriber Provisioning)
The HLR-PS automatically updates the DMS-HLR tables each time a

MSP file is found in the Input Directory.
Figure 7-10
HLR-PS general architecture
HLR-PS General Architecture
Customer Care Center (OSS

(OSS))
X.25
X.25
Network Transfer Network
Network PSTN
NFS Manual Transfer
TCP/IP 32 Links RS-232 or
X.25 TERMINAL FTP
GATEWAY SERVER
LAN
TCP/IP
Console DAT Tape

HLR PS
Service Provisioning Subscriber Creation
AUC
• Per-sub service provisioning • SIM Personalization
• Bulk service provisioning • Supports DES decryption of Ki
• Supports up to 32 links DMS-HLR • Batch creation and deletion of
subscribers
The HLR-PS supports the following provisioning interfaces and functions:

• provisioning interfaces
— non-Nortel Administration Center (AdC)
— Bulk Service Provisioning (BSP)
• provisioning functions
— Virtual HLR (VHLR)
— Provisioning Gateway (PG)
— MSP Audit

Call Intercept System (CIS) 7

The Call Intercept System (CIS) allows authorized police and other
government security agencies to establish surveillance and record the
communications activities of target mobile subscribers within a GSM
network.
The CIS provides the ability to monitor communications events of the target
MS from a remote surveillance facility, or from within the Mobile Switching
Centers (MSCs).
The target subscriber activities can be monitored even if the subscriber roams
to a different MSC within the home PLMN. Subscribers who roam
internationally are selected for call interception by the monitoring agency in
the visiting PLMN.
Note: Calls in progress before provisioning is initiated cannot be

monitored.
Figure 7-11
Call intercept
Call Intercept
Multiple Monitoring Provisioning Center
Center(s)
Feature Overview
Call Monitoring Features:
» MSISDN and IMSI Provisioning

Separate
» Simultaneous Monitoring by
Channels for Target Provisioning Multiple Agencies
Transmit and
Receive Paths
Using MSISDN » Data/Fax Monitoring
» SMS/CISS Monitoring
» Separated Call Content
PSTN LAN/WAN
Channel
» PRI Trunk Monitoring
SDM-FT ... SDM-FT
» IN Call Monitoring
VLR VLR
DMS-MSC DMS-MSC
GSM Data
Services Services
IN PRI
Services Services
CIS functions
The CIS performs the following functions:
• call monitoring performed at the Monitoring Centers
• call intercept provisioning performed at the CIPC
• nodal security
• configuration management
Table 7-2 gives a short description of each function in the CIS.
Table 7-2
CIS functions
CIS Functions Description
Call Monitoring Every voice call that either originates from or terminates to
a targeted subscriber, and every non-call mobility event, is
intercepted at the DMS-MSC, and routed to the
authorized agency monitoring center. Both the call
contents and the call associated data are intercepted and
routed to the monitoring center.
Call Intercept The CIS allows either an authorized security agency, or
Provisioning the service provider on behalf of an authorized security
agency, to provision mobile subscribers for call
interception.
Nodal Security Nodal security is accomplished on the CIS by enforcing
use of passwords.
Configuration The Configuration Management function allows the
Management provisioning operator to assign Security Agency IDs and
monitoring center IDs. If the CIS configuration is
centralized, the provisioning operator can act on behalf of
multiple security agencies.
CIS architecture
The CIS architecture includes three major hardware/software components that
can be connected in either a centralized or a decentralized configuration:
• DMS-MSC switch is a Network Element (NE) in the PLMN
• each DMS-MSC has its own SDM/FT which acts as a mediation device. It
is connected to the CIPC over a LAN/WAN in the GSM network
• monitoring center(s), where targeted mobile subscribers are monitored

Figure 7-12
CIS architecture
Third Party Equipment

Legend: Security Agency A
Call Contents Security Agency B
Provisioning MONITORING MONITORING
CADR/NCADR &/or CENTERS CENTERS
Provisioning
Service Provider Site

CALL INTERCEPT
PROVISIONING
CENTER
CADRs/ CADRs/
NCADRs NCADRs
only only
Provisioning X.25 or Ethernet Network

TCP/ IP LAN
LAN Call
Contents
ANSI/
Note: ETSI-ISUP
The Monitoring
Centers are not Call
provided by Contents
NORTEL.
ANSI/
ETSI-ISUP
FTAM/X.25
TCP/IP -
TCP/IP TCP/IP
Ethernet
TCP/IP-Ethernet
FTAM/X.25 LAN
ANSI/ ANSI/
ETSI ISUP SDM/FT
ETSI ISUP
SDM/FT DMS-MSC
DMS-MSC (PET7)
(PET7)
PLMN
.CADR (Call Associated Data Record), call setup, Handover...

NCADR (NonCall Associated Data Record), Location Update...
Call Content, voice call interception, supplementary services (CFU, CW)
The following events may invoke a Call interception at a DMS-MSC:

• call setup within DMS-MSC
• IMSI Detach/Attach
• call barring
• call related supplementary services
• handover
• intercepted call failure
• short message services
• call independent supplementary services
• location update
CIS capacity 7
The CIS capacity is based on agencies. It can be:
• up to 5 agencies
• up to 2048 target subscribers per agency
• multiple operators
• up to 32 parallel interceptions at MSC level
• up to 20 MSCs per CIPC

1. Describe the purpose of the SDM.
2. Describe the platform hardware of the SDM.
3. Describe the HLR-PS role.
4. Describe the OMC-S applications.
5. What is CIPC?

Lesson 8
Using MAP terminal
Objectives 8
Given student lesson, instructor lecture and appropriate documentation, the
student will be able to:
• configure the Visual Display Unit (VDU) within the DMS-MSC/HLR

system parameters
• log in and log out of the DMS-MSC/HLR system
• use basic Command Interpreter (CI) commands
• access the maintenance level of the Maintenance and Administration
Position (MAP)
• interpret the MAP status and alarm screen display
• recognize critical, major, and minor alarms Introduction to the MAP
The MAP provides an interface between the operating company personnel
and the DMS-MSC/HLR. The MAP is used to perform general operation,
administration and maintenance functions. The MAP includes a VDU and
testing facilities.

8-2 Using MAP terminal Nortel Networks Confidential
Introduction to the Visual Display Unit 8

The VDU terminal is the primary interface for the DMS-MSC/HLR system. It
consists of a display monitor and a keyboard.
The DMS-MSC/HLR is configured to work with a simple computer terminal

that can be obtained from a number of different manufacturers. To be
compatible with the DMS-MSC/HLR, a terminal must use ASCII (American
Standard Code for Information Interchange) character code, operate in
VT100 mode and provide either a current loop or an EIA RS-232-C electrical
interface.
Terminal setup procedures 8

The following terminal setup procedures are for a DEC VT100 or VT200
VDU terminal. Other manufacturers’ terminal setups are similar. Refer to the
specific owners manual.
To setup your terminal, complete the following steps:

1. turn on the power to the VDU
2. set the brightness and contrast controls
3. set the terminal defaults, shown in Table 8-1, by doing the following:
a. press the setup key (F3) located at the top left section of the keyboard
to display the setup directory on the screen
b. use the arrow keys to move the field cursor to the default field. The
selected field is highlighted
c. press the ENTER key in the numeric keypad situated at the lower
right corner of the keyboard. This action puts the terminal into the
factory setting. Always use this ENTER key to change field values to
the desired settings
Confirmation “Done” appears on the bottom of the screen.
Nortel Networks Confidential Using MAP terminal 8-3
Table 8-1
VDU configuration
Setup screen Setup options

Setup directory (1) on line
(2) setup = english
(3) north american keyboard

Display setup (1) interpret control
General setup (1) VT100 mode
(2) VT100 ID or VT220 ID

Communication SETUP (1) transmit = 2400
(2) receive = 2400 or receive = transmit
(3) XOFF at 64
(4) 8 bits, no parity
(5) 1 stop bit
(6) no local echo
(7) EIA port, data leads only

Keyboard setup (1) break
(2) no key click
(3) no margin bell

Command system tasks 8

The Command Interpreter (CI) is the highest level of the command system.
This utility is accessed immediately upon login and then interprets and
executes a limited, specific set of commands entered by the user. The CI
utility is also the gateway for accessing various other software utilities such
as LOGUTIL, MAPCI, TABLE EDITOR, etc.
Figure 8-1
CI level tasks
CI Level Tasks
LOGIN
CI LEVEL
DISKUT Table
DSKUT MAPCI LOGUTIL
Editor
MTC
411-0930-001 12.02/EN December, 2000 Lesson 8 Using a MAP Terminal 8-3
Syntax conventions
Use the following syntax conventions when inputting MAP commands:
• text displayed in capital letters indicates a literal string to be entered, as

follows:
LOGUTIL
• angle brackets surround parameters required to be entered:

For example: <my_password>
You must enter the appropriate parameter. Text indicating a parameter but
not providing a literal string is displayed in lower case. Unless explicitly
told to do so, do not enter angle brackets.
• square brackets surround optional parameters to be entered, as follows:

[optional_parameter]
Enter the appropriate parameter if desired. Text indicating a parameter but

not providing a literal string is displayed in lower case. Unless explicitly
told to do so, do not enter square brackets.
• a vertical bar indicates a choice between two or more parameters. These

can be optional or required parameters; only one may be selected. Text
indicating a parameter but not providing a literal string is displayed in
lower case. Text indicating a choice between literal strings is displayed in
upper case, as follows:
CURRENT | PREVIOUS

Keyboard commands 8
The following keyboard commands are essential for effective MAP
operation.
Editing command lines

Commands and parameters which are typed and displayed in the input echo
display area can be edited before the RETURN key is pressed. The input echo
display area reflects the command last entered. The editing function includes
inserting and deleting characters and lines and changing the horizontal
position of the cursor.
Line editing commands

The line editing commands shown in table 8-2 can be used when a typed line
needs to be modified before it is committed in the system. The line editing
commands are activated by depressing the CONTROL key and F, U, E, I, X,
S, Q or H. In addition to these commands, the backspace and delete keys
perform the same function as they would on a normal keyboard or typewriter.
Table 8-2
Line editing command functions
Command Explanation
? The user may recall one of the LAST THREE lines which were
entered. (Timesaver - allows you to repeat a part or an entire
command without retyping it.)
CTRL F moves the cursor one position to the right
CTRL U deletes the entire line
CTRL E deletes all typed in characters from the cursor position to the end
of the line
CTRL I places the terminal mode to insert; subsequently typed characters
are placed into the line. As each inserted character is typed, all
characters from the cursor position moves one position to the
right.
CTRL X exits from the character insert mode
CTRL S stops scroll
CTRL Q begins scroll
CTRL H backspace
BACK SPACE moves the cursor to the left
DELETE or deletes the character at the cursor position
CTRL 8
Changing output displays 8

The processes invoked by MAP commands can be started, stopped or
changed by depressing the BREAK key (F5) and entering any of the
commands described in Table 8-3.
Table 8-3
Changing output display commands
Command Explanation
HT Halt typing (HT). The display of responses stops, but the process
continues unseen.

MAP commands 8
The MAP commands allow you to operate, maintain and provision the
switch.
The following commands provide basic functions needed to access and use
the DMS-MSC/HLR.
Command name: LOGIN

Before users can execute commands within the DMS-MSC/HLR, they must
gain access to the system by logging in. Login procedures may vary
depending on security features in effect on the switch. There are two types of
login procedures: manual or automatic.
The manual procedure provides security against unauthorized users by

prompting for a valid user name and password, whereas the automatic
procedure merely requires a user to enter LOGIN. The manual method is
most common, so it is described in the following example.
Input: press BREAK key (F5)

Response: ? or ?? and an audible beep
Input: LOGIN
Response: Enter user name
Input: enter USER NAME
Response: Enter password
Input: enter PASSWORD
Response: login message followed by a flashing cursor indicating the
command interpreter (CI) level
Command name: LOGOUT

The LOGOUT command allows the users to log out from any level of the
DMS-MSC/HLR switch. Upon LOGOUT, the system closes all related files,
releases all related resources, rewinds and demounts all attached tape devices.
Input: LOGOUT
Response: The system responds with BYE BYE and a flashing cursor.
Command name: QUSER

Use the QUSER command to display the logged-on user(s) plus the device
name of the terminal being used.
Example
Input: QUSER
Response: The list of logged-on users and their associated terminal.
Command name: DATE

The DATE command is used to display the date and time of the system clock.
Example
Input: DATE
Response: Date is WED. 15/MAY/1996 15:30:10
Command name: TIME

Use the TIME command to display the current time of the system clock.
Example
Input TIME
Response: Time is 15:29:22
Where: Hours (15)
Minutes (29)
Seconds (22)

Command name: COMMAND

Use the command COMMAND to create new commands to simplify
repetitive routines which need to be performed over and over again. The new
command name is entered by the system into the user directory.
To see the contents of your directory:
Input PRINT <USERNAME>
The command will be removed automatically when the user logs out.
The contents of command(s) cannot be displayed without being executed.
Example: Input: COMMAND T TIME

Response: >
Input: T
Note: The user created a new command called T. When T is entered, the
command TIME will be executed by the system.
The COMMAND command allows you to create a customized command.

The customized command is similar to a macro in a PC, and is constructed by
creating a sequence of existing commands and assigning a new command
name to this sequence. The entire sequence can then be performed by
executing only the custom command (again, just like a PC macro). This
technique is useful for performing commonly used commands all at once thus
reducing keystrokes, etc.
For example, to create a customized command named mycommand:
1. Enter a definition. For instance:

>command mycommand (table @1; format pack; lis all)
This definition line:
— states that a format pack and a lis all commands will be performed on
the Table named “@1”.
— creates the new command with the following parameters:
– table @1 - “@1” determines which Table the remaining two parts
of the sequence will be performed on. Entering the variable “@1”
in the definition line allows you to perform mycommand on any
Table.
– format pack - performs a format pack on Table @1 (removes

extraneous spaces from Table @1).
– lis all - lists the entire contents of Table “@1”.
Figure 8-2
Explanation of mycommand definition
mycommand Definition
Table “@1” determines which

Table to perform format pack and
lis all on. Where ” @1” is the Table Displays Table @1.
name.
command mycommand (table @1, format pack, lis all)
Removes extraneous
spaces from Table @1.
411-0930-001 12.03 February, 2001 Lesson 8 Using a MAP Terminal 8-4
2. At the command prompt, specify mycommand and a Table name. For

example, enter:
>mycommand C7link
This customized command format pack Table C7link, and display the
entire contents of table C7link.

Command name: MSG

Use the MSG command to send messages from a logged-in user to a
receiving user’s terminal.
Example
To send a message to a specific user.
Input: MSG <username> ‘message string’

Response: >MSG from <user name>: <message string>
Note: The message must be enclosed in single quotes and cannot exceed
one line in length.
Example
To send a message to ALL logged in users.
Input: MSG ALL ‘message string’

Response: >Message from <user name> <message string>
Command name: SETLOGMSG

Use the SETLOGMSG command to change the office header message which
is displayed following a successful login. The office header message is a
statement put on the software load when it is built. This message can be
displayed by depressing the RETURN key twice on your keyboard, when
logged in.
The office header message helps lab personnel to know what BCS load is in
the switch. It usually contains the: COEO number, Office name, BCS load,
BCS release and BCS release date.
An example follows: COEO: H04849-00, DMS-MSC_TRNG_RCH, BCS36

RTM 94 08 05. It can be altered or changed with the command
SETLOGMSG by typing:
SETLOGMSG ‘<string of message>‘
The new message will override the previous office header. To verify, hit the
RETURN key twice.
Note: The message MUST be in single quotes and cannot exceed one line
in length.
Command name: SHOW USERS

The SHOW USERS command is used to display the current valid DMS-
MSC/HLR users.
Example
Input: SHOW USERS

Response: The list of DMS-MSC/HLR users and their attributes
are displayed.

Command name: PRINT

Use the PRINT command to display the following on the VDU:
• contents of a file
• content of a directory
• all current logged in users
• parameters of a command
Parameter <character_string> STRING

<file_name> FILE name
<directory_name> DIRECTORY name
Example
Input: PRINT SYSDIR

Response: The content of the system directory is listed. This
directory provides a list of commands common to all
DMS switches.
Example
Input: PRINT USERS

Response: Prints a list of the currently logged in users. This list
provides the same information as the QUSERS
command, but in a different screen layout.
Command name: PERMIT

Use the PERMIT command to define a new valid user and its attributes to the
DMS-MSC/HLR system software. The command may also be used to change
or alter attributes for an existing user. The changed attributes become
effective immediately if the user is not logged in. Otherwise, the user must
log out of the system and then LOGIN before the new attributes take effect.
Choice of User Attributes for PERMIT

Priority
The level at which the user software commands are executed.
Value range between 1 and 4, where 4 is the highest priority. In emergencies,
users with priority of 4 have top priority and their commands are executed by
the switch first, then priority 3 through 1. (Default = 4).
Stack size
The size of memory (bytes) allocated to run switch software processes. If the
memory is not set large enough, the user cannot run all software systems in
the switch. A value between 2000 and 10000 is recommended.
The larger value gives the user more memory. (Default = 7000)
Language
The language for the system output messages and input commands. Value can
be DEFAULT, ENGLISH, FRENCH or SPANISH.
(Default = ENGLISH)
Command class
Two options are available. ALL or a number in the range 0–30.
(Default = ALL)
ALL gives the user access to all DMS-MSC/HLR terminal commands. If a

number is entered, the user is restricted to commands only in that class.
Command classes allow the operating company to give users various levels of
command access.
For example, a terminal assigned to service orders does not need to have
access to the commands used by network management; thus, they would be
assigned different classes associated with different commands.
Note: To override the default ALL, enter PERMIT, followed by all the
desired attributes, before the RETURN key is pressed.

Example
Input: PERMIT <new username>

Response: Enter new password.
Input: Enter new PASSWORD
Response: Please enter new password again to verify.
Input: Enter new PASSWORD
Response: >Enter priority, stacksize, language and command
classes.
Input: Enter the various attributes in non-prompt mode
(example parameters) 2 4000 english 0 1 2 3 6 9
Note: Verify the proper data was entered by logging in as the new user.
Command name: UNPERMIT

Use the UNPERMIT command to delete users from the current DMS-MSC/
HLR users list.
Any user having the command class ALL can delete another user, but only if
you know the other user password. This restriction limits the ability to do
UNPERMIT to the ADMIN user. Remember, ADMIN has the power to
assign a new password to any user.
Input: UNPERMIT <username>

Response: Enter password of user.
Input: enter PASSWORD
Response: UNPERMIT ____ has been deleted.
Note: A logged in user cannot be unpermitted.

Command name: RECORD

Use the RECORD command to set up, take down or query recording links
between devices.
When two devices are linked, all input and output on the FROM device are
echoed on the ONTO device. Device parameters default to INPUT and
OUTPUT.
Note: The RECORD command displays the contents of the rerouted

information on the originating device.
Parameters
<Function> {START,STOP,QUERY}
[<FromDevice> {FROM <Device> DEVICE name}]
[<OntoDevice> {ONTO <Device> DEVICE name}]
The following examples use three devices:

• R324U1 (the initiating terminal and user TOM is logged in)
• R324U2 (user name of a terminal device)
• D010MISC (volume on DISK 1)
Example 1
Query status of any record links
.
Input: RECORD QUERY

Response: No record links started
Example 2
Start a recording link from the initiating terminal R324U1 onto PRT0, and
then QUERY the recording link
.
Input: RECORD START ONTO PRT0

Response: Done
Input: RECORD QUERY
Response: FROM R324U1 ONTO PRT0 STARTED BY TOM
Example 3
Start a recording link from R324U2 onto disk volume D010MISC. Recording
link started by user TOM from the R324U1 terminal.
Stop recording onto PRT0 from R324U1.
Input: RECORD START FROM R324U2 ONTO D010MISC

Response: Done
Input: RECORD STOP ONTO PRT0
Response: Done
Input: RECORD QUERY
Response: FROM R324U2 ONTO D010MISC STARTED BY
TOM
These events occur:

• logging out automatically cancels recording links started by the user
• for recording link started to an alternate device (except Printer), the data is
collected in a file called RECORDFILE on the device
• the user cannot stop recording links started by another user
Command name: REPEAT
Use the REPEAT command to repeat any CI command or expression a
specified number of times.
Parameters
<number> <expression>
<number> A numerical value (1 TO 32767) representing
the number of times the CI command or
expression is to be executed repeatedly.
<expression> Any valid CI command or expression
Example
Input: REPEAT 2 (TIME)

Time is 15:30:45

Command name: SEND

Use the SEND command to reroute the user terminal response to an alternate
device, such as Magnetic Tape Drive (MTD), Disk (DDU or SLM), Printer,
Data Memory (Sfdev), etc.
The same command is also used to reinstate the user terminal response to the
originating device.
When initiating the SEND command to an alternate device (except Printer),

the sent data will be collected in a system allocated file under the name of
CONSOLE, unless a file name is specified by the user. This file will be closed
when the sending process is stopped or, the initiating user logs out.
Note: The SEND command will not display the contents of the rerouted
information on the originating device.
Parameters
{devname [tapefilename] ,
systemfilename
PREVIOUS} Cancels the SEND command previously entered. The
PREVIOUS parameter is to the SEND command as
the STOP parameter is to the RECORD command.
CI menu hierarchy 8
As shown in Figure 8-3, the CI menu system is developed in a layered or
hierarchical manner. This means you must enter a menu level at a higher level
before you can access a lower level.
EXAMPLE: After successfully logging on the DMS, to gain access to the PM

sublevel:
1. enter CI
2. enter MAPCI
3. enter MTC
4. enter PM
The PM level is entered.
Figure 8-3
CI menu hierarchy
CI Menu Hierarchy
CI
Table LOGUTIL
MAPCI DSKUT DISKUT
Editor
MTC
CM MS IOD Net PM CCS Lns Trks Ext APPL
To Lower Menu Levels

MAPCI display areas

The MAPCI display format was designed to present an overview of the
system while telescoping into the other levels. The general layout of a
MAPCI level display is shown in Figure 8-4.
Figure 8-4
MAPCI display areas
MAPCI Display Areas
Alarm System Status Display Area
Level Level Status Display Area
Command
Menu
Display
Command Interpreter
Output Display Area
Area
User ID
Time Input Echo Display Area
Following is a description of each of the areas of the MAP display:

• Alarm system status display area
Reflects the overall system status. When the automatic maintenance
system detects a fault, the alarm system indicates the fault severity and the
general area affected. The alarm system status display is present at all
system levels. Dots under the major system areas indicate these
subsystems are in normal, trouble-free condition or they are off-line.
• Level command menu display area

Is the location in which the commands for a particular level are listed. The
menu has numbers ranging from 0 to 18 listed, but not all have commands
beside them. With the exception of the QUIT command (0), the
commands associated with numbers vary from level to level.
• Level status display area

Reflects the status of the physical subsystem associated with the level.
Depending on the menu, the options can include shelf, plane or card level
status information.
• User ID area
Indicates the identification of the terminal to the I/O system.
• Time area
Indicates the time of day.
• Input echo display area
Reflects the command last entered.

MAP Command Interpreter menu level

The MAP command interpreter (MAPCI) is the entry level of the
maintenance and administration levels. To enter this level, enter MAPCI at
the CI prompt. This produces the display shown in Figure 8-5.
The following MAPCI level menu commands are frequently used by

maintenance technicians:
• QUIT
Leaves the MAPCI level and returns the user to the CI level.
• MTC
Enters the maintenance menu level.
The commands in any menu can be executed by typing the command

abbreviation as shown on the menu or the menu number.
For example, the Quit command can be executed by typing quit or 0

followed by the Enter key.
Figure 8-5
MAPCI display
MAPCI Display
MAPCI MAPCI
0 Quit
2 MTC
3 SASelect
4 NWM
5 CPSys
6
7
8 To move from the MAPCI level to the MTC level, enter
9 the command MTC or 2, followed by the RETURN key.
10
11
12
13
14
15
16
17
18
OPERATOR
Time 10:15 >
Maintenance level menu

The maintenance level (MTC or 2) is the gateway to the maintenance
subsystem levels that are directly related to the physical DMS-MSC/HLR
modules, including CM, MS, NET, IOD. The maintenance level is shown in
Figure 8-6.
The MTC menu displays all the major maintenance levels available to the
user. Through this level, the maintenance sublevels can be accessed to
perform specific functions, that are directly related to the physical modules.
Figure 8-6
Maintenance MAP display
Maintenance MAP Display

CM MS IOD Net PM CCS LNS Trks Ext APPL
• • 2 CkOS • 1 PDTC • • 2 GC • •
M *C*
MTC
0 Quit
2
3 MTCNA
4 MTRsys
5 BERP
6 CPstatus
7
8
9 CM
10 MS
11 IOD
12 Net
13 PM
14 CCS
15 LNS
16 Trks
17 Ext
18 APPL
OPERATOR
Time 09:09 >

Alarm indicator display

The systems audible and visual alarms alert maintenance personnel of a
trouble condition. Faults are classified according to the severity of the
problem and assigned to the critical, major, or minor alarm class.
When a failure is detected by the system, the alarm system status display area
is updated to indicate the fault. When more than one alarm condition exists on
a subsystem, only the most severe alarm status displays. The three alarm
codes are shown in Table 8-4.
Table 8-4
Alarm indicator display alarm codes
Code Alarm class

*C* Critical alarm
M Major alarm
(Blank) Minor alarm if a system fault is displayed; no alarm
otherwise.
. No alarm
The alarm code flashes when the failure is detected.
The alarm code stops flashing when the:

• silence (SIL) command is entered
• alarm reset key on the alarm control panel is operated
• alarm condition is corrected
If an additional alarm is reported to the MAP, the appropriate alarm class code
flashes for that fault. The additional alarm also requires corrective action to
be silenced.
Command menu display 8

The MAP level area displays valid command and parameter codes ranging 0
to 18. These commands are abbreviations of one or more words that describe
the function. For example, Figure 8-7 shows the computing module (CM)
menu level. In this menu, the command to test the CM is abbreviated and
displays as Tst. The command to switch activity between the two CPUs
displays as SwAct.
Commands and parameters in the menu indicate the following qualifications

for their use:
• Locate_
Requires a parameter after the command. This requirement is indicated by
the “_” after the command.
• Quit
May accept, but does not require, a nonmenu parameter. An example of
this is the QUIT ALL command.
Figure 8-7
Command menu display
Command Menu Display

• • • • • • • • • •
CM
0 Quit
2 CMMnt CM Sync Act CPU 0 CPU 1 Jam Memory CMMnt MC PMC
0 • CPU 0 • • • • • •
3 Memory
4 MC
5 PMC
6 Tst
7
8
9
10
11
12 REXTst
13 SwAct
14 Sync
15 DpSync
16 MtcChk_
17
18 Locate_
OPERATOR
Time 12:48 >

MAP level command types

Every MAP level has a directory associated with its commands. The directory
ties the level software process to other processes that are responsible for
executing the commands or obtaining data from a table.
An explanation of any MAP level command can be obtained by entering

Q <command name>.
Not all commands available to a level are shown on the command menu
display. Infrequently used hidden commands are available for advanced
maintenance procedures. The hidden commands for each menu level can be
accessed by entering the LISTST command at the MAPCI prompt. This
command lists a group of directories. When the top directory listed is printed
using PRINT <directory name>, all the commands that can be entered at the
current MAP level, including the hidden commands, displays.
Entering commands
To enter and activate commands, press the Return key on the keyboard.
If the command requires a parameter and the parameter code displayed on the
menu:
1. enter the parameter
To do this, you can enter the menu number or parameter code.
2. enter the parameter code
When replying to a prompt for parameters, the first character you type at the
prompt must always be a space, followed by the required parameter.
Example
In the following example, three command entry options are shown. These
options perform the same function, (see Figure 8-8.)
Valid entries for testing MS 0
enter 60 or 6 0 or TST 0
Commands entered with incorrect characters or spacing are interpreted as

nonexistent commands. They generate an UNDEFINED COMMAND output,
indicating there is no such command.
Figure 8-8
Command entry
Command Entry
• • • • • • • • • •
MS
0 Quit
2
3 Message Switch Clock Shelf 0 Inter-MS link 0 1
4 MS 0 • FREE • • •
5 MS 1 • SLAVE • • •
6 Tst_
7 Bsy_
8 RTS_
9
10 LoadMS_
11
12 SwMast
13 Shelf
14 QueryMS
15
16 MtcChk_
17 InterMS_
18 Clock
OPERATOR
Time 10:30 >
Multiple command entries

A series of commands, each separated by a semicolon (;), can be typed and
activated in one step. Such a series is known as a string or chain of
commands. They can be used within a subsystem or to move to other
subsystems. Command strings are comprised of letters, numbers and
punctuation symbols (including spaces) or a combination.
EXAMPLE MAPCI;MTC;MS; SHELF; CARD 8;TST 0; PM
In this example, the following actions occur:

1. MS subsystem is accessed by the MAPCI and MTC levels
2. shelf level of MS subsystem is accessed
3. card 8 sublevel of SHELF level is accessed
4. card 8 is tested
5. system exits the MS subsystem and enters the PM subsystem

Commands from other menus

You can access commands and parameters from menus other than the one
displayed, if:
• entered commands and parameters reside in higher level menus than the
one displayed
• commands and parameter codes are typed in full (not using the command
display numbers associated with a command)
• the command code does not appear on the displayed menu. Otherwise it is
invoked at the displayed menu
Example
The following example is entered from the SHELF level of the MS
subsystem.
Input
PM; POST DTC 0; BSY UNIT 0; TST UNIT 0
In this example, the following actions occur:

1. PM subsystem is accessed
2. DTC 0 is posted
3. Unit 0 of DTC 0 is manually busied
4. Unit 0 is tested
Recording menu and hidden commands

Both menu level commands and hidden commands may be recorded as a soft
copy or a hard copy. The following examples will show you how to perform
this task.
EXAMPLE
To record a soft copy of menu level and hidden commands, use the following
procedure:
At the CI prompt:
Input record start onto <device>

example d010mtce
Input mapci nodisp
The menu will not display.
Input mtc;pm;post dtc 0
Input listst
The list of directories is shown.
Input print lgcdir
All the commands (both menu-level and hidden) are
shown for that directory.
Input record stop onto d010mtce
A file is created <recordfile>.
Input dskut
Input liv d010mtce all
Input print <recordfile>
The soft copy of the file is now printed.

Example
To print a hard copy of the menu level and hidden commands:
1. select the <device> (example: printer) to which you send your file
2. complete with the following steps
Input record start onto <device>

enter printer name
Input dskut
Input liv d010mtce all
Input print <filename>
Input record stop onto <device>
1. What is MAP used for?
2. What do MAP commands allow the user to do?
3. What is the purpose of the MAPCI menu level?
4. What is the maintenance level menu?

Exercise 8-2 Self Check Review Questions

Instructions 8
Using this lesson and notes taken during the instructor lecture, answer the
following questions. Review them with the instructor and with the Self check
following this exercise.
1. What command provides a list of all users that have access to a switch?
Which commands show the users currently logged in?
2. If you are about to do something on the switch that would knock all
current users off the switch, what command (and its parameters) allows
you to notify logged in users that this is about to happen?
3. If you wanted to record some screen information from a user named Joe
onto a printer called PRT0, what command (and its parameters) must be
entered?
4. If a person had a user name and password assigned and then left the
company, what command allows you to remove this person’s user name
from the switch?
Note: Assume the user password is known.
Use the following graphic to answer questions 5–8.
ALARM SYSTEM STATUS DISPLAY AREA
First Subsystem
Command
Menu
Display
Command Interpreter
Area Output Display Area
User ID
5. Which area of the screen provides a numbered list of commands?
6. If the screen shows the shelf level of message switch 0 and a card failure
occurred, what area would provide a CARD level indicator of the failure?
7. If a command was entered that queried the system for information to be

displayed on the user VDU, in what area would the information display?

8. If the screen shows the shelf level of message switch 0 and a failure
occurs in the ENET shelf, what area provides corresponding alarm
information?
9. If entered at the CI prompt, what would the following command string

do? MAPCI;MTC;MS;BSY 0;TST 0;RTS 0
Answers
Check your answers to the review questions with the following. Review any
questions for which the answer was missed with the information in this lesson
and with your instructor.
1. What command provides a list of all users that have access to a switch?
Which commands shows the users currently logged in?
SHOW USERS lists all the users who can log into a switch. QUSER or
PRINT USERS shows those users currently logged in to the switch.
2. If you were about to do something on the switch that would knock all the
logged-in users off the switch, what command (and its parameters) allows
you notify them this is about to happen?
MSG ALL ‘message string’
3. If you wanted to record some screen information from a user named Joe
onto a printer called PRT0, what command (and its parameters) must be
entered?
RECORD START FROM JOE ONTO PRT0
4. If a person had a user name and password assigned and then left the
company, what command allows you to remove this person’s user name
from the switch?
Note: Assume the user password is known.
UNPERMIT <username>; then enter the user’s password when

prompted
Use the following graphic to answer questions 5–8.

ALARM SYSTEM STATUS DISPLAY AREA
First Subsystem
Command
Menu
Display
Command Interpreter
Area Output Display Area
User ID
5. Which area of the screen provides a numbered list of commands which

can be entered at the current menu level?
command menu level display
6. If the screen was showing the shelf level of message switch 0 and a card
failure occurred, what area would provide a CARD level indicator of the
failure?
level status display area
7. If a command was entered which queried the system for information to be

displayed on the users’ VDU, in what area would the information be
displayed?
command interpreter output display area
8. If the screen was showing the shelf level of message switch 0 and a failure
occurred in the ENET shelf, what area would provide corresponding
alarm information?
alarm system status display area
9. If entered at the CI prompt, what would the following command string

do? MAPCI;MTC;MS;BSY 0;TST 0;RTS 0
this command string would enter the message switch (MS) maintenance
menu (MAPCI:MTC:MS), manually busy MS 0 (BSY 0), test it (TST 0),
then return it to service (RTS 0).

Exercise 8-3 VDU login and logout

Instructions 8
1. The instructor will assign each student a user name and password. Log in
to the switch using the following example:
Example
Input: press the BREAK key (F5)

Response: ? ?? and an audible beep
Input: LOGIN
Response: Enter user name
Input: enter <USER NAME>
Response: Enter password
Input: enter <PASSWORD>
Response: login message followed by a flashing cursor
indicating the CI level
2. After the login procedure is completed successfully, follow the logging

out procedure below:
Example
Input: LOGOUT
The system responds with BYE BYE and a flashing cursor. Each student
should practice logging in and out until confident with the procedure.
Exercise 8-4 Exercise 3: Using CI commands

1. Perform the following SHOW command:
Example
Input: SHOW USERS

Response: The list of DMS-MSC/HLR users and their attributes
display.
2. Perform the following QUSER command:

Example
Input: QUSER
Response: The list of logged-on users and their associated
terminal.
3. Use the MSG command to send a message to another group.

Example
Input: MSG <username> ‘message string’

Response: MSG from <user name>: <message string>
Note: The message must be enclosed in single quotes and cannot exceed
one line in length.
4. Use the following three RECORD command examples:
Example
Query status of record links.
Input: RECORD QUERY

Response: No record links started

Example
Start a recording link from the initiating terminal R324U1 onto PRT0 and
QUERY the recording link
Input: RECORD START ONTO PRT0

Response: Done
Input: RECORD QUERY
Response: FROM R324U1 ONTO PRT0 STARTED BY TOM
Disable all record links you have started and query status.
Exercise 8-5 Maintenance level commands

Instructions 8
From a MAP terminal, practice querying the DMS-MSC/HLR system for
equipment location and status by performing the following commands:
1. Enter MAPCI;MTC;IOD
Enters the IOD level.
2. Enter LISTDEV CONS

Displays the status and location of all console type I/O devices such as
VDUs, printers and modems.
3. Enter TRNSL PRT0

Identifies the device and its physical location.
4. Enter IOC 0
Enters the IOC level and displays the status of each equipped controller
card on IOC 0.
5. Enter TRNSL
Displays the MS port assigned on both MSs and connects to IOC 0.
6. Enter IOC 1
Enters IOC 1 level and displays the status of each equipped controller
card.
7. Enter LISTDEV DDU

Provides the disk drive unit status and location.
8. Enter CARD 1
Displays the status and state of card 1, IOC 1.
9. Enter ALLOC
Displays the disk volume names, volume size, address and status of files.
10. Enter MS; SHELF; TRNSL 0 10 PORT 0

Displays physical card information for cards associated with MS shelf 0,
CARD 10, PORT 0.

Lesson 9
Table editor
Objectives 9
will be able to:
• describe the function of the Table Editor

• describe a table
• explain how tuples are structured in a table
• explain the purpose of pointers
• explain the purpose of selectors

9-2 Table editor Nortel Networks Confidential
Table editor 9
In the DMS-MSC/HLR system, the data for a given office is located within a
software structure known as tables. An office has requirements for different
types of data such as trunks, routing, translation, screening and hardware
inventory which are entered into associated tables within the DMS-MSC/
HLR.
Table editor is a software subsystem in the MAP that is used to read and
manipulate the data tables contained in the system. The user has access to the
information already contained in the database as well as the ability to
customize the data tables to support the specific telecommunication needs of
each site. The table names and formats are hardcoded and cannot be changed
by the customer. However, the entries into these tables are customer-
definable.
The number of tuples in a table is limited only by the table size and the
memory allocation engineered for the system.
Each table in the DMS-MSC/HLR has a unique table structure and contains
information relative to its function. For example, table TERMDEV (terminal
device) contains all of the input for VDUs, printers and modems.
Nortel Networks Confidential Table editor 9-3
Figure 9-1
Table editor
CI Level Tasks
LOGIN
CI LEVEL
Table
DSKUT DISKUT MAPCI LOGUTIL
Editor
MTC
411-0930-001 12.02/EN December, 2000 Lesson 9 Using Table Editor 9-3
To access Table Editor, complete the following steps:

• Enter TABLE
• Enter the table name from the CI level

Use the table editor commands to perform the following:

• add, delete, or change tuples (Table UPdate Line Entries) or fields within
a table or subtable
• list one or more tuples of a table or subtable
• move the software pointer to display any tuple within a table or subtable
• display specified field values
• search for tuples containing specified field values
• verify table changes before activating them
• modify the subtables of a table
• change a default field value for any specified field
• display the number of used and allocated tuples of a table
• alter data when the CPUs are out of sync
Table and subtable structure 9

The table and subtable structures within the DMS-MSC/HLR are two-
dimensional.
A table consists of:

• horizontal rows referred to as tuples
• vertical columns called fields
As shown in Figure 9-2, the information in the fields makes up the tuples.
Subtables contain data relative to the field of which they are a part. The
names of the fields listed across the top of the table are referred to as the
heading.
Fields
The fields in a table or subtable have the following properties:
• each field has a unique identifier called a field name or a field number by
which the field may be accessed
• fields are consecutively numbered from left to right, starting at number 1
• number of fields varies from table to table
• field data enclosed by brackets (x) are pointers to a subtable
• contents of a field may contain one or more elements of data
• field data may consist of letters, numbers or alphanumeric characters
Tuples
The tuples in a table or subtable have the following properties:
• each tuple has a unique identifier called a key. The key field for each tuple
in most cases is field number 1 and is known as the key field name. Some
tables have more than one key field.
• all of the data (fields) making up a tuple contain information about the
key
• tuples are referenced either by their key or by the table editor cursor. The
cursor is an internal pointer to a tuple within a table. The cursor pointer
can be positioned by utilizing the table editor commands.The tuple to
which the cursor points at any given time is called the current tuple.
• tuples are consecutively numbered from top to bottom, with number 0 at
the top
Subfields
A field may be composed of two or more pieces of information called
subfields. In this case, it is necessary to enter all of the subfield information to
equal one field. Subfields are usually found in the key field when extra
information is needed to make each tuple unique.

The example below shows a key field (XLAKEY) that is composed of three
subfields: XLANAME, FROMD and TOD.
XLAKEY
XLANAME FROMD TOD XLASEL OSEL
GSMOBILE 214 214 RTE DEST 2
The combination of the three subfields allow the use of GSMOBILE as a

translator name for all three tuples, while the translations point to different
destinations based on the FROMD and TOD fields. (See Figure 9-2).
Figure 9-2
Table structure
Table Structure
TABLE Fields
1 2 3 .... N
Field Field Field Field
Name Name Name Name
Top 0 Key Data (Data) Data
Tuples 1 Key Data (Data) Data

...
Bottom N Key Data (Data) Data
SUBTABLE Fields
1 2 3 .... N
Field Field Field Field
Name Name Name Name
Top 0 Key Data Data Data
Tuples 1 Key Data Data Data

...
Bottom N Key Data Data Data

Subtables
Some fields within a table contain more information than can be displayed in
the actual space allocated for it in the main table. When this situation occurs,
the software allocates space in another area of memory and creates a subtable
entry for that particular field. A subtable is denoted in the main table by a
number with parentheses around it under a specific field name.
To view the data in a subtable, position on the tuple with the desired subtable.
If the cursor is not positioned on a specific tuple, the first tuple in a table is
indexed by default.
The example given in Figure 9-3 shows the structure of a subtable within a
table. Note the parentheses around a number in the field titled TREAT; these
parentheses indicate a subtable. In this example, the CELL1 tuple has six
entries in its subtable. If a zero is in the parentheses, no tuples exist in a
subtable.
Figure 9-3
Accessing subtables
Accessing Subtables
TABLE TMTCNTL
EXTTMNM TREAT
MSTREAT (6)
The example following shows the six tuples in subtable TREAT.
SUBTABLE TREAT
TREATMT LOG FSTRTE
UNDT Y S ANN1B
PDIL Y S ANN1A
PSIG Y S ANN1B
VACT Y S VACT
RODR Y T OFRT 1
GNCT Y T OFRT 2

Selectors
Selectors are specific data choices which are placed in a field in a table. The
field may have several selectors. The chosen selector may have additional
prompts associated with it or may reference additional fields in a later table
during the software trace of the call. Choosing the wrong selector could create
call processing problems in later tables. Translations are used to define the
various selectors and their impact on the call type associated with it.
Perhaps an easier way of describing a selector is through cause-and- effect

statements such as the examples below.
• If the first digit that a subscriber dials is a 0, then the call is routed to an
operator.
• If the first three digits that the subscriber dials are 011, then the call is
routed as an international call.
The following are some of the selectors used for the DMS-MSC:
• S directly connects to a terminating trunk
• T routes calls from one table to another
• CND indicates a special condition is to be used, such as time of day
routing
• N indicates digit manipulation (deleting, prefixing digits)
• D routes a call directly to a treatment
Subtable TREAT uses both the S and the T selectors.
Subtable TREAT
TREATMT LOG FSTRTE
UNDT Y S ANN1B
PDIL Y S ANN1A
PSIG Y S ANN1B
VACT Y S VACT
RODR Y T OFRT 1
GNCT Y T OFRT 2
Input prompter
A prompter tells the user that the data has been entered incorrectly or not all
the mandatory data has been entered. The table editor commands may be
executed in a prompt or a non-prompt mode.
Prompt mode
The prompt mode is a method of entering data in which the system prompts
the user for each piece of information needed. The user enters the command
in the prompt mode, followed by a return. If all the required data is not
entered, the system guides the user through each field. See Figure 9-4 for an
example.
When in the prompt mode, the following environment is present:

• name of the required field or parameter is displayed
• user must input the correct data for each field or parameter as it is
displayed
• if the data that is input is incorrect, the system responds with an error
message and the field or parameter prompt is displayed. If data is entered
incorrectly again, the system responds with an error message and a brief
description of what is needed for that field or parameter.
• at any time while in the prompt mode, the user may enter ABORT, which
stops the execution of the original command.
• when a field or parameter contains subfields, these subfields are included
in the system prompts. When the user is prompted for a list of items, the
prompts continue until the user enters a dollar sign ($) or until the
maximum number of entries for the list is reached.

Figure 9-4
Example MAP display of prompt mode
Example MAP Display of Prompt Mode
CI:
>table pmloads
TABLE:PMLOADS
>add
>y
LOADNAME:
>enc36cj
ACTFILE:
>enc36cj
ACTVOL:
>s010dmisc
BKPFILE:
>enc36cj
BKPVOL:
>s000dmisc
UPDACT:
>n
TUPLE TO BE ADDED:
ENC36CJ
ENC36CJ S010DMISC
ENC36CJ S000DMISC N
ENTER Y TO CONFIRM, N TO REJECT OR E TO EDIT.
>Y
Nonprompt mode
Once the user is familiar with input for a particular activity, he or she may
enter commands more efficiently by using the nonprompt mode. In the
nonprompt mode, the user simply enters the command and all the information
for each field in a continuous line of data with spaces between information.
See Figure 9-5 for an example.
When the nonprompt mode is used, the following environment is present:

• plus sign (+) is used when the full information for one tuple exceeds one
input line. When + is used as the last character on a line, the contents of
that line and any following lines are processed as a single input.
• after the system recognizes a valid command, one field value is processed
at a time until the end of the input line is reached or an error is found.
After identifying an error, the system reverts to the prompt mode at the
point of the incorrect field.
• when the system processes a list, subsequent fields are assumed to be part
of the list until a field value of $ is encountered, the maximum list length
is reached or the end of the input line is reached.
Figure 9-5
Example MAP display of nonprompt mode
Example MAP Display of

Nonprompt Mode
CI:
>table pmloads
TABLE: PMLOADS
>add enc36cj enc36cj s010dmisc enc36cj s00dmisc n
TUPLE TO BE ADDED
ENC36CJ
ENC36CJ S010DMISC
ENC36CJ S000DMISC N
ENTER Y TO CONFIRM, N TO REJECT OR E TO EDIT.

>Y
TUPLE ADDED
WRITTEN TO JOURNAL FILE AS JF NUMBER 233
>
411-0930-001 12.03 February, 2001 Lesson 9 Using Table Editor 9-7

Table editor commands 9

To access the table editor, enter the TABLE command followed by the name
of the desired table to go to the CI (Command Interpreter) level of the MAP.
If you enter only the TABLE command and do not provide a table name, the
system prompts you for the table name: enter the table name
Various commands and their appropriate parameters are available.
After a command string is entered, press the carriage return. On most

keyboards, the carriage return is designated as Enter, Return, or CR. After
you have entered a command followed by a carriage return, the system
displays the prompt character (>) to indicate it is ready for another command.
The commands in Table 9-1 show the common table editor commands
grouped together by function.
Table 9-1
Table editor commands
Function Commands
Access tables TABLE, SUBtable
Exit From tables QUit, QUit ALL, RETurn, LEAVE
Modify tables ADD, CHAnge, DELete, REPlace
Display table contents LISt, DISplay
Move cursor POSition, TOP, BOTtom, UP, DOWn
Obtain table information COUNT, RANge, HEADING, INForm
Other FINDTAB
COMMAND
The information provided for each command includes:

• brief explanation of each command
• brief description of all optional and/or mandatory parameters for each
command
• default values and valid range values for each parameter
Note: The table editor command functions are identical in both tables and
subtables. the commands that have capitalized prefixes will work by
entering the prefix (for example, SUB for subtable).
The ABORT command is used to cancel a command or input that has been
entered by accident or incorrectly.
When a command contains incorrect parameters, the system repeatedly

prompts you for the correct field value.
Use the ABORT command to cancel the previous command and permit you
to try again. If the system continues to prompt the user for the correct field
value:
• enter the ABORT command

• try the LIST and RANGE commands to determine the resident table and
the parameters the system is expecting

Command name: ADD

Use the ADD command to add tuples to a table.
Depending upon the table, the tuple is automatically placed on the bottom of
the table or in a specific location within the table. Therefore, the ADD
command can be executed from any location within the table.
Parms: <FIELD 1> <FIELD 2>. ..<FIELD N>

FIELD 1 Defines the desired value of the KEY FIELD (first field) of
the tuple being added.
FIELD 2 Defines the desired value of the second field of the tuple
being added.
FIELD N Defines the desired value of the remaining fields of the
tuple being added.
Command name: BOTTOM (BOT)

Use the BOTTOM command to position the internal pointer on the last or
bottom-most tuple in the table and display the tuple entry.
Parms: none
Command name: CHANGE (CHA)

Use the CHANGE command to change the value of existing field data for a
given tuple.
The command is executed on the current tuple only. More than one field
value may be changed in a single command, providing that the field values
are separated with a semicolon.
Parms: <FIELD NAME> <FIELD NO.> <FIELD VALUE>

FIELD NAME The name of the field for which the data is to be changed.
FIELD NO. The number of the field for which the data is to be changed.
FIELD VALUE The new value for the field being changed.
Command name: COUNT

Use the COUNT command to display a count of the number of tuples within a
table.
The tuples searched and counted will be determined by the parameters which
follow the command. The number of subtable entries for a subtable pointer in
a main table is also updated.
Parms: <CONDITION> Display the count of all tuples within a table which meet
the defined conditions. The conditions and their
meanings are as follows:
& AND
EQ Equal to
GE Greater than or equal to
GT Greater than
LE Less than or equal to
LT Less than
NE Not equal to
| OR
No parameter = a count of ALL tuples in the
table.
Command name: DELETE (DEL)

Use the DELETE command to delete one or more tuples from a table or
subtable.
The tables or subtables may require certain prerequisites to be met before

deletions can be made. When this command is entered without parameters,
the current tuple is deleted. The cursor is always positioned to the tuple
immediately below the deleted tuple. When the tuple deleted is the last tuple
in the table or subtable, the cursor is left unpositioned.
Parms: <KEY FIELD 1> <KEY FIELD 2>... <KEY FIELD 3>]
The KEY name of the tuple or tuples to be deleted from the table or subtable.
DEFAULT: CURRENT TUPLE
Command name: DOWN (DOW)

Use the DOWN command to position the internal pointer on a tuple which is
below the current tuple and display the tuple entry.
The number of tuples below the current tuple must be specified unless the
number is 1, which is the default value.

Parms: <COUNT >
The number of tuples (0-32767) below the current tuple to which the internal
pointer is to be positioned.
Default value = 1.
Command name: FORMAT PACK / FORMAT UNPACK

Use the FORMAT PACK command to reduce the spacing format of a table or
subtable.
Some tables or subtables by structure, are widely spaced between tuple

entries; hence, a fewer number of entries can be viewed simultaneously. By
packing the format, up to 22 tuples can be listed on a single screen. It can also
save paper when recording contents of a table to a printer.
Command name: HELP

Use the HELP command to obtain an explanation of what a command does
and how it may be executed. It also provides the user with a list of all
available table editor commands.
Parms: < COMMAND NAME>

The name of the command for which the system is
to display information.
Command name: LIST (LIS)

Use the LIST command to display tuples within a table.
A header (field names) is displayed first, followed by the tuple entries. The
number and type of tuples displayed is determined by the parameters which
follow the command.
Parms: [<COUNT> or ALL] <CONDITION>

COUNT The number of tuples to be displayed beginning with the current
tuple.
ALL Display all tuples within the table beginning with tuple 0 which is
the uppermost tuple in the table.
CONDITION Display the specified number of tuples (COUNT | ALL) which
meet the defined conditions. The condition and their meaning are
as follows:
& AND
EQ Equal to
GE Greater than or equal to
GT Greater than
LE Less than or equal to
LT Less than
NE Not equal to
| OR
If no parameter is specified the default value is 1.
Command name: POSITION (POS)

Use the POSITION command to position the internal pointer on a specific
tuple and display the tuple entry.
Parms: <KEY FLD1> <KEY FLD2>... <KEY FLD3>

KEY field identifies a specific tuple within a
table. Some tables have multiple data within the
KEY field.

Command name: QUIT (QUI)

Use the QUIT command to quit one or all levels.
A QUIT command executed within a subtable results in an exit from the

subtable and the main table.
• If the user is two or more levels deep in tables, the QUIT command exits
the current table and indexes into the previous table.
The cursor will be positioned on the exact tuple on which it was originally
located.
A QUIT ALL command quits all levels.
Parms: [NLEVELS or INCRNAME or ALL]

NLEVELS The number of levels to quit.
INCRNAME The name of a valid level. The system will quit all
levels up to and including the specified level.
ALL Quit all levels and return to the CI level.
Command name: RANGE (RAN)

Use the RANGE command to display table field(s) by field number and field
name. In addition, the parameter type and valid inputs for each field are also
displayed.
Parms: <FIELD NAME> or < FIELD NO.>

FIELD NAME The name of the field that the RANGE command is to
display.
FIELD NO. The number of the field that the RANGE command is to
display.
If no parameter is specified the command lists all the fields.
Command name: REPLACE (REP)

Use the REPLACE command to replace a specified tuple with a new tuple.
Since the tuple to be replaced is specified by the KEY, the command can be
entered from any location within the table. All data field values for the tuple
must be entered.
Parms: <FIELD 1> <FIELD 2>........<FIELD N>

FIELD 1 KEY field for the tuple being replaced.
FIELD 2 Second field for the tuple being replaced.

FIELD N Remaining fields for the tuple being replaced.
Command name: SUBTABLE (SUB)

Use the SUBTABLE command to enter a subtable from the main table.
The main table must be entered via the table command before the subtable
can be accessed.
Parms: <FIELD NAME> or <FIELD NO.>

FIELD NAME The name of the table field which is the pointer to a
subtable.
FIELD NO. The field number of the table which is a pointer to a
subtable.
Note 1: These are optional parameters and would only be used when a
table has pointers to more than one subtable for each tuple entry.
Note 2: A table structure with only one subtable pointer per tuple entry
does not require the use of optional parameters. Use caution prior to
editing a subtable. Always verify the internal pointer position to ensure
that the targeted subtable will be changed. Failing to do this may
introduce a potential problem which could negatively impact the system
operation.
To verify the subtable, use one of the following procedures:

• press the RETURN key twice
• use the INFORM (INF) command

Command name: TABLE

Use the TABLE command to enter the table editor subsystem for the specified
table name.
The system allocates a TABDIR to the user's symbol table which provides
access to the table editor commands.
Upon successful access to a table, the following events will be automatically

performed by the system:
• internal pointer (table editor cursor) is positioned on tuple 0, which is the
first entry within the table
• OVERRIDE mode is set to OFF. (Disables the JOURNAL FILE)
• VERIFY mode is set to ON
Parms: <TABLE NAME>

The name of the table to be edited.
Command name: TOP

Use the TOP command to position the internal pointer on tuple 0, which is the
first entry in the table and display the tuple entry.
Parms:none
Command name: UP
Use the UP command to position the internal pointer on a tuple which is
above the current tuple and display the tuple entry.
The number of tuples above the current tuple must be specified unless the
number is one, which is the default value.
Parms:<COUNT>
Command name: VERIFY (VER)

Use the VERIFY command to turn ON or OFF the system prompt for
verification and confirmation when altering data within a table or subtable.
The default value is reinstated each time you QUIT a table or subtable.
Parms: < ON > or <OFF>

ON The system is to prompt the user to verify and confirm
that the data is correct.
OFF The system executes the command as input, without

confirmation. Commands must be executed in the
non-prompt mode.
Command name: FINDTAB

Use the FINDTAB command to display a list of tables whose names begin
with the same characters.
• Specify the first two characters of the tables to display. For example, the
command:
>FINDTAB C7
a list of all table names beginning with the characters “C7” is displayed.
Therefore Tables C7network, C7link, etc. would be displayed.
Parms: <BEGINNING CHARACTERS OF VALID TABLE NAMES>
Other commands
In addition to the table editor commands, there are two additional commands
which provide useful information about tables: SHOWUSERS and
SHOWUSES. These commands are entered at the CI prompt and provide the
following information.
SHOWUSERS
Use the SHOWUSERS command to display a list of tables which are
dependent upon the datafill in the specified table. The listed tables require a
tuple be created in the specified table before they will work properly.
Parameters <TABLE NAME>

At the CI prompt, enter: SHOWUSERS TERMDEV
MAP response: Table TERMDEV is being used by:
(a list of tables is displayed)
The tables listed are dependent upon Table TERMDEV for an input.
Note: The SHOWUSERS command under MAPCI is not the same

command as the one presented here.

SHOWUSES
Use the SHOWUSES command to display a list of tables on which the
specified table is dependent for datafill. The specified table requires a tuple be
created in at least one of the listed tables before it will work properly.
Parms: <TABLE NAME>

At the CI prompt, enter: SHOWUSES TERMDEV
MAP response: Table TERMDEV dependencies:
IOC
Data in Table IOC is used by tuples in Table TERMDEV.
Table editor - quick command reference list

Following is a list of basic table access commands and their functions:
Command Function
ADD adds a tuple to the current table or subtable
BOTTOM (BOT) positions the internal pointer on the last tuple in the table
and displays the tuple entry
CHANGE (CHA) changes the value of a specified field in the current tuple
COUNT displays a count of the number of tuples within the table
DELETE (DEL) deletes one or more tuples from the current tuple
DISPLAY (DIS) displays the tuple entry for the current tuple
DOWN (DOW) positions the internal pointer on the tuple that is below the
current tuple and displays the tuple entry
FIRST positions the cursor on the first tuple in the table or in the
subtable. No display appears.
FORMAT PACK packs the spacing format of a table or subtable
FORMAT UNPACK reverts to normal spacing format
HEADING displays the header (field names) for a given table
HELP displays an explanation of what a command does and how
it may be executed
LAST positions the cursor on the last tuple in the table or
subtable. No display appears.
LIST (LIS) displays tuples within a table
LOCATE (LOC) positions the cursor on a specified tuple. No display
appears.
NEXT positions the cursor on the tuple following the current tuple.
No display appears.
OVERRIDE (OVE) cancels the prompt that occurs when the CPUs are out of
sync or when the Journal File is not available
POSITION (POS) positions the internal pointer on a specific tuple and
displays the tuple entry
PREV positions the cursor on the tuple previous to the current
tuple. No display appears.
QUIT (QUI) exits the user from one table editor level. The command
QUIT ALL returns the user to the CI level.
RANGE (RAN) displays table field (s) by field number and field name
REPLACE (REP) replaces a specified tuple with a new tuple

RETURN (RET) returns the user from a subtable to the main table
SUBTABLE (SUB) permits entry to a subtable from a main table
TABLE enters the table editor subsystem for a specific table name
TOP positions the internal pointer on tuple 0 which is the first
entry in a table or subtable and displays the tuple entry
UP positions the internal pointer on the tuple which is above
the current tuple and displays the tuple
VERIFY (VER) turns verification on or off
Other associated table commands
SHOWUSES displays a list of tables on which the specified table is
dependant for datafill
SHOWUSERS displays a list of tables which are dependant upon the
datafill in the specified table

1. What is the function of Table Editor?
2. How are tuples structured in a table?
3. Explain the purpose of pointers.
4. Explain the purpose of selectors.

Exercise 9-2 Cursor positioning commands

Instructions 9
Match each function with its table editor command. Compare your answers to
the self check on the following page.
A. BOTtom ___ Moves the cursor out of a subtable and back to

the parent table.
B. DOWn ___ Moves the cursor up a specified number of
tuples.
C. FIRST ___ These two commands place the cursor at the
beginning of the table. What is the difference between
the two?
D. LAST ___ Enters a subtable.

E. NEXT ___These commands place the cursor at the end of
the table. What is the difference between the two?
F. POSition
G. QUIt
H. RETurn ___ Moves the cursor down a specific number of
tuples.
I. SUBtable ___ This command places the cursor on a specific
tuple.
J. TOP ___ Positions the cursor one tuple below the current
tuple.
K. UP ___ Takes you to the CI level from a table or any of its
subtables.
Answers
questions for which the answer was missed with the information in this
lesson, and with your instructor.
A. BOTtom _H_ Moves the cursor out of a subtable back to the

parent table.
B. DOWn _K_ Moves the cursor up a specified number of
tuples.
C. FIRST C&J These two commands place the cursor at the
beginning of the table. What is the difference between
the two?
Both FIRST and TOP position the cursor on the first
tuple. TOP also displays the tuple
D. LAST _I_ Enters a subtable.

E. NEXT A&D These commands place the cursor at the end of
the table. What is the difference between the two?
Both BOTtom and LAST position the cursor on the
last tuple. BOTtom displays the tuple whereas LAST
does not.
F. POSition
G. QUIt
H. RETurn _B_ Moves the cursor down a specific number of
tuples.
I. SUBtable _F_ This command places the cursor on a specific
tuple.
J. TOP _E_ Positions the cursor one tuple below the current
tuple.
K. UP _G_ Takes you to the CI level from a table or any of its
subtables.

Answers—editing and other commands

Instructions 9
Match each function with its table editor command. Compare your answers to
the self check on the following page.
A. ABORT ___ Displays the table heading.

B. ADD ___ These two commands print tuples to the screen.
What is the difference between the two?
C. CHAnge
D. COUNT ___ Displays the available table editor commands or
gives details about a specific command.
E. DELete
___ Edits tables.
F. DISPLAY ___ Removes tuples.
G. HEADING ___ Inputs a new tuple.
H. HELP ___ Tells how many total tuples there are or how
many tuples there are that fit a given condition.
I. LISt ___ Prints the fields in a table or subtable and gives a

brief description of each. Also prints a more detailed
description of each field within a table including the
legal values for the field.
J. RANge ___ Cancels a command or input that has been
entered accidentally or incorrectly.
Self check 9
questions for which the answer was missed with the information in this lesson
and with your instructor.
A. ABORT _G_ Displays the table heading.

B. ADD F&I These two commands print tuples to the screen.
What is the difference between the two?
The DISPLAY command displays the
current tuple without a heading. LISt can
display multiple tuples and shows the
heading as well.
C. CHAnge
D. COUNT _H_ Displays the available table editor commands or
gives details about a specific command.
E. DELete
_C_ Edits tables.
F. DISPLAY _E_ Removes tuples.
G. HEADING _B_ Inputs a new tuple.
H. HELP _D_ Tells how many total tuples there are or how
many tuples there are that fit a given condition.
I. LISt _J_ Prints the fields in a table or subtable and gives a

brief description of each. Also prints a more detailed
description of each field within a table including the
legal values for the field.
J. RANge _A_ Cancels a command or input that has been
entered accidentally or incorrectly.

Exercise 9-3 Understanding table layouts

Instructions 9
Go to CI level and enter the table editor commands shown. After entering the
commands complete the questions below:
Input: >Table Tmtcntl

Response: TABLE: TMTCNTL
Input: >LIST ALL
1. How many fields are in this table?______________

2. What is the name of the KEY for tuple number 1?______________
3. How many entries are in the subtable of tuple 1?___________
4. What field is associated with the subtables?____________________
5. How many tuples are in this table?_____________
Input: >Quit
Response: CI:
Input: >Table Tmtcntl
Response: TABLE: TMTCNTL
Input: >LIST
Response: The first tuple of this table is displayed.
To enter subtable TREAT:
Input: >SUB TREAT; LIST 5

Response: The first 5 subtable tuples are displayed for tuple 1.
1. Which field name has multiple data entries?____________

2. On what tuple number is the internal pointer placed if the command up 2
is entered?____________
3. What is the field number for the field name LOG?__________
4. How many fields are in this subtable?____________
Input:>QUIT to get back to CI level.
Exercise 9-4 Using table editor commands

Instructions 9
Log into a terminal if you are not already logged in. Follow the steps below to
familiarize yourself with the Table Editor commands.
Enter in a table
1. Enter TABLE CUSTHEAD
2. Enter LIS. The system lists the table header and the tuple to which the
cursor is currently positioned.
3. Enter RAN. The system displays fields for Table CUSTHEAD. Notice
that it shows the field number, field name and general description. If the
description for a field is TABLE_OWNERSHIP, it means this field has a
sub-table.
4. Enter RAN 1. The system displays parameters for field 1 of Table
CUSTHEAD.
5. Enter TOP. The system positions the cursor at the top tuple and displays
its contents.
6. Enter Q BOTTOM. The system displays parameters associated with the
BOTTOM command.
7. Enter BOTTOM. The system positions the cursor on the bottom tuple
and displays its contents.
8. Enter Q POSITION. The system displays parameters associated with the
POSITION command.
9. Enter POS EXAMPLE. The system displays the contents for tuple
EXAMPLE.
10. Enter LISt. The system lists the table header and the tuple the cursor is
currently positioned on EXAMPLE.
11. Enter LEAVE. The system returns to the CI level.

Enter in a subtable
1. Enter TABLE TMTCNTL
2. Enter POS OFFTREAT
3. Enter SUB TREAT. No display of the table contents will appear. So,
depress the carriage return three times and the system will show TABLE:
TMTCNTL OFFTREAT: TREAT. This means that you are in Table
TMTCNTL positioned on OFFTREAT and specifically in Subtable
TREAT.
4. Enter Q SUB. The system displays the parameters of the command
“subtable.” Notice that you can use either the field name or the field
number to enter a subtable.
5. Enter LIS 5. The system lists 5 of the tuples in this subtable. (The
commands are the same in the subtables as in the tables.)
6. Enter RET. The system returns from subtable 5 to the main table and
displays the tuple on which you entered a subtable. (Depress CR three
times to show you that you are in the main table).
7. Enter LEAVE
Adding tuples
1. Enter TABLE CUSTENG
2. Enter ADD. At each prompt, enter the following information.
3. Enter CUST <assigned student position number> at the CUSTNAME
prompt.
EXAMPLE: CUST2 for the student in position 2.
4. Enter 10 at the NONCOS prompt

5. Enter 63 at the NOIBNTMT prompt
6. Enter N at the CONSOLES prompt
7. Enter N at the MASCON prompt
8. Enter PUBLIC at the CUSTTYPE prompt
9. Enter Ø at the GROUPID prompt
10. Enter $ at the OPTIONS prompt
11. Enter Y when the system asks if you are sure you want to add that tuple
12. Enter CHA
13. Enter (CR) until you reach the NOIBNTMT prompt
14. Enter 40
15. Enter (CR) until you reach the OPTION prompt
16. Enter $ at the OPTION prompt
17. Enter Y when the system asks if you are sure you want to change that
tuple
18. Enter DEL
19. Verify that the tuple that appears is the tuple you added
20. Enter Y when the system asks if you are sure you want to delete that tuple
21. Enter QUI to exit the table and return to the CI level

Lesson 10
Universal Translations (UXLA)
Objectives 10
will be able to:
• describe the function of Nortel Universal Translations (UXLA)

• describe the main tables associated with UXLA
• explain a TRAVER and how to interpret its results

10-2 Universal Translations (UXLA) Nortel Networks Confidential
DMS-MSC translations 10
Stages of translations
The following is a description of the two main stages of translations:
• screening involves the analysis of dialed digits in selected data tables to
determine if correct rules were followed. For instance, the table verifies
that the leading digits of a number were for a call going outside the
system.
• routing involves certain data tables determining appropriate routes a call
should take. For example, the table selects a long-distance trunk group for
a call or sends a call to a recorded announcement.
Figure 10-1
Translations area processing
Translations Area Processing
OUTPULSED
INCOMING DIGITS DIGITS
TRANSLATIONS
AREA
(UXLA)
ACTION
TRANSLATOR
NAME • Routing
• Database query (DBQ)
• Treatment (Tone or
Announcement)
• Activation of a feature
(Handover Number, Paging)
• Activation of an IN trigger
411-0930-001 12.02/EN December, 2000 Lesson 10 Translations 10-3
Nortel Networks Confidential Universal Translations (UXLA) 10-3
Figure 10-2 illustrates the DMS-MSC translations.
Figure 10-2
DMS-MSC translation picture
Overall Picture of DMS-MSC Translations

Universal translation system
PXHEAD PXCODE PXRTE
Translations continue
CTHEAD CTCODE CTRTE in the UXLA tables...
Where
does call
FAHEAD FACODE FARTE terminate?
OFCHEAD OFCCODE OFCRTE
AMHEAD AMCODE
ACHEAD ACCODE ACRTE
NO NO NO
Table Trunk Treatment Feature
YES YES
YES YES
OFRT ** Appropriate RTE table in
universal translations table Launch Feature
Terminates to treatment
** This table is not part of UXLA and cannot be used to manipulate digits

Translations Verification (TRAVER) tool

The TRAVER tool is used to examine the path a call takes through the system
data tables. The DMS-MSC runs a TRAVER for a call and displays a report
on the VDU screen. This report lists the data tables and related tuples that the
call uses in the DMS-MSC.
The TRAVER command line uses the following format:
Traver <origin> <dialed digits> <type of traver>
Parameters Description
origin MS indicates that the originator is a Mobile Station.
TR indicates that the originator is a Trunk.
Figure 10-3
TRAVER for MO call
Sample TRAVER
TRAVER MS 2224900 LAC 1 CID 1 6842930 b
TABLE LAC
1 1 MSC_BSS_RS UNRSTRCT 0 0 0 ( 20) $ $
TABLE XLAENTRY
20 PX GSMOBILE
TABLE PXHEAD
GSMOBILE SDFLT NODFOP CON 9
THE DIGITS USED TO INDEX THE NEXT TABLE ARE:6842930
TABLE PXCODE
GSMOBILE 684 684 CONT ( CONSUME 3) ( XLT OFC GSMOBILE) $
TABLE OFCHEAD
GSMOBILE SDFLT NODFOP NOCON 9
THE DIGITS USED TO INDEX THE NEXT TABLE ARE: 2930
TABLE OFCCODE
GSMOBILE 2930 2930 RTE ( DEST 12) $
TABLE: OFCRTE
KEY: GSMOBILE 12
. T OFRT 12
. . TABLE OFRT
. . 12 S D GSM1900_2W
. . EXIT TABLE OFRT
EXIT TABLE OFCRTE
+++ TRAVER: SUCCESSFUL CALL TRACE +++
DIGIT TRANSLATION ROUTES
1 GSM1900_2W 6842930 ST
BILL 2224900 ST
Land to MS call
Figure 10-4 shows the output of a typical TRAVER for a PET scenario.
Figure 10-4
Typical TRAVER output
Typical TRAVER Output

>traver tr PET_TRK 5446123123 b
TABLE TRKGRP
PET_TRK PET 0 NPDGP NCRT 0 MIDL PX PETXLA NILLATA MSC N 5 0 NOCONT UNDT
NEVER
NEVER N 9 $
TABLE PXHEAD
PETXLA SDFLT NODFOP CON STD
TABLE PXCODE
PETXLA 544 544 CONT ( MM 10 10) ( CONSUME 3) ( XLT FA PETXLA)$
TABLE FAHEAD
PETXLA SDFLT NODFOP CON STD
TABLE FACODE
PETXLA 61 61 DBQ ( NSC GSMSRI) ( GSMIDX SRINATL)$
TABLE GSMDEFS
SRINATL (MODIFY ( NOA NOA_NATL) (NPI NPI_ISDN) (TIMEOUT 20) $)$
+++ CALL WILL QUERY GSM DATABASE FOR TRANSLATION INFORMATION
+++ TRAVER: SUCCESSFUL CALL TRACE +++
+++ TRANSLATION ROUTES TO SRI QUERY FEATURE +++


1. What is the function of TRAVER?
2. On what type of software does the DMS-MSC rely to process (translate)

calls?
3. What are the two stages of translation?

Lesson 11
Operational measurements & log
reports
Objectives 11
will be able to:
• describe an OM group and counters
• describe how OMs are generated
• use OMSHOW to access OM counters
• understand how to use OMs
• describe a log report
• use LOGUTIL to access log reports
• understand how to use log reports

11-2 Operational measurements & log reports Nortel Networks Confidential
Operational Measurements (OMs) and OMSHOW 11

OMs are created by the DMS-MSC hardware and software components.
These measurements provide indications of the overall efficiency of the
system components and validate the engineering and provisioning of the
DMS-MSC office. OMs measure feature usage, feature paths, switching
equipment usage and traffic loads.
The OM system provides the operating company information on the following:

• switch performance
• grade of service being offered
• connecting facilities
• performance and traffic levels of various elements integral to and
connected to the switch
OMs are used for:
• traffic provisioning
• maintenance
• service monitoring
• accounting allocations
• commissioning and acceptance testing
• services to TELCO customers
OMs are counters and OM counters are called registers. Measurement groups
are used to organize registers in a logical manner. For example, all OM
registers related to GSM call processing are under a group called MSCCP,
also known as MSC call processing.
Nortel Networks Confidential Operational measurements & log reports 11-3
Figure 11-1 shows the OM groups and counters organization in the CM

memory.
Figure 11-1
OM counters and groups
OM Counters and Groups

CM Memory OM Group OM Group
OM Group
OM Counter
Counter OM Counter OM Counter
OM Counter
Counter
OM Counter
OM Counter OM Counter
OM Group
OM Group
OM Group OM Counter
OM
OM Counter
OM Counter OM
OM Counter OM Counter OM Counter
OM Counter
OM Counter
OM Counter
Counter
OM Counter
OM Counter
411-0930-001 12.02/EN December, 2000 Lesson 11 Introducing OMS & Log Reports 11-3

Operational Measurement system

The OM system monitors certain events in the DMS-MSC and enters the
results into memory registers. There are three types of registers: peg counters,
usage counters, and watermark counters.
Peg counters (or event counters)

A peg counter is a register that counts, or pegs, every time a particular kind of
event occurs. An example of such a register is the INCATOT (INcoming Call
Attempt TOTal) register. This register is pegged every time the incoming
trunks (in a specific trunk group) are seized for incoming calls.
In , the OM register INCATOT monitored and recorded each time the trunks
were seized. The four trunks were seized seven times.
Note: Peg counters answer the question: How many times?

Figure 11-2
OM peg register monitoring seizure trunks
Monitoring Trunk Seizure (1/2)

10:00 a.m. - Beginning of Accumulation Period
10:30 - End of Accumulation Period

Usage Sample (found 2 in use)



100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100 100
sec sec sec sec sec sec sec sec sec sec sec sec sec sec sec sec sec sec
Trunk #1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
Trunk #2 2 2 2 2 2 1 2 2 2 2 2 2 1
Trunk #3 2 3 3 3 3 3 2 3 3 3 3 3 2 2
Trunk #4 3 4 4 4 4 4 3 1 2 3 4 4 4 4 4 3 3 1
Figure 11-3
Monitoring trunk seizure 2/2
Monitoring Trunk Seizure (2/2)

LEGEND: X = seizure of trunk.
_ = trunk in use.
¦ = end of trunk usage
¦ = usage scans (samples)
TRK = TRunK report
OM REPORT:
START: 1987/02/13 10:00:00 FRI; STOP: 1987/02/13 10:30:00 FRI;
SLOWSAMPLES: 18; (FASTSAMPLES: 180)

INCATOT . . . TRU
TRKGRPIC (with 4 trunks): 7 . . . 59
411-0930-001 12.03 February, 2001 Lesson 11 Introducing OMS & Log Reports 11-5
Usage counters
Some registers do not peg how many times an event happens, but rather how
long these events lasts. These registers are known as usage registers. Usage
registers do not actually count the exact number of seconds that an event lasts.
Instead, usage registers take “snapshots” (samples) on a regular basis to see if
the event is continuing.
Usage registers measure how long an event lasts in hundreds of call

completion seconds (CCS), or erlangs.
Note: Usage registers answer the question: How much time?
To determine the length of time the trunks in were used, the user must rely on
the usage counter called traffic usage (TRU). This OM register monitors
trunks by taking a “snapshot” of how many trunks in each trunk group are
used every 100 seconds.
High watermark counters

Numerous registers are set up to reflect the highest use of specific resources
within the transfer period. These resources are continually monitored and
compared with the current contents of the active register, the highest value
becomes the new value in the active register. These values are known as High
Watermark registers.

The OMs and especially the high watermark OMs can be used as a
benchmark of the levels of traffic-dependent activity in the switch during the
current interval. The high watermark OMs display the highest level of
simultaneous usage reached in critical office parameters for the collection
period. Overflow OMs display the number of times that the parameter was
required but no resources were available.
High watermark registers such as: CPLHI, CCBHI, CPHI, OUTBHI,

MULTHI, WAKEHI, and INLBHI count call processing letters, call condense
blocks, call processes, outgoing buffers, multiblocks, wakeup blocks, and
long buffers in simultaneous use during the preceding OM transfer period.
These registers can be used to verify and adjust the engineered quantities of
the resources in question.
True peak utilization can be predicted by taking the maximum value of all the
high watermarks observed during individual transfer periods, during the
busiest days of the year. An additional amount should be added to this value
to ensure that the target 80% peak utilization of software resources is not
exceeded, even during the busiest times.
Figure 11-4
High watermark registers
High Watermark Counters

Current Usage
Largest Value
Active Counters
Figure 11-5
OM example
OM Example
>o m s h o w c 7 m t p h o l d i n g
CLASS: HOLDING
START:1998/06/17 15:30:00 WED; STOP: 1998/06/17 16:00:00 WED;
SLOWSAMPLES: 18 ; FASTSAMPLES: 180 ;
C7MSIDPC C7MSISIO C7XSDYWT C7XSDYNT
C7PHDYWT C7PHDYNT C7GTT95 C7NGTT95
C7SMPWT1 C7SMPWT2 C7SMPNT1 C7SMPNT2
0 0 0 0
0 0 0 0
0 0 0 0
Variables related to usage counters

The usage of the trunks in trunk group TRKGRPIC is 59 hundred call
seconds (abbreviated CCS where the first “C” stands for centum which
means hundred in Latin).
To interpret the reading of a usage counter, the following questions must be

answered:
• What is the scan rate of the register?
• What is the length of time covered by the register total?
• How many entities/trunks is the register monitoring?
• Is usage measured in CCS or Erlangs?
Scan rates
A scan rate determines how often a register takes a snapshot (sample). Two
scan rates are available. Scan rates can be;
• every 10 seconds
• every 100 seconds one CCS
Scans taken every 10 seconds are called fast scans; their snapshots are called
fast samples. Scans taken every 100 seconds are called slow scans; their

snapshots are called slow samples. When a snapshot is taken, it is assumed

the entity being observed is in use for the entire scan time. Not all events in
the switch move at the same pace; receivers are used and released at a much
faster pace than trunks.
Accumulation period
The second important variable for a usage counter is the length of time during
which the counter is to take snapshots. This length of time is the accumulation
period. The accumulation period determines the number of fast or slow scans
that can be gathered.
Number of monitored entities

The last important variable for usage counters is the number of entities/trunks
monitored during an accumulation period. The more entities the OM register
snapshots, the more likely usage will take place and be sampled, resulting in a
higher register value at the end of the accumulation period.
Erlangs
An erlang is a unit of measurement. One erlang represents the same value as
36 CCS, which equals one hour.
Example:
To convert 72 CCS to erlangs, divide 72 by 36. The result is 2 erlangs. To
convert 3 erlangs to CCS, multiply 3 by 36. The result is 108 CCS.
OM register data collection

OM data is useful only if it relates to a consistent time period. All
measurements are collected in the following three time intervals: active,
holding, and accumulating. Contained within each of these time intervals are
various OM registers that record how often an event occurs or how long an
event lasts.
Active register
Active registers store peg and usage counts as they occur. Data cannot be
routed directly from the active registers to an output device. Instead, the data
must first be transferred to the holding registers and the active registers
cleared.
Holding register
Holding registers temporarily retain data for display or transmission prior to
the next active/holding transfer. The holding register sends data to the
accumulating register or output device. Data held in a holding register is
eventually overwritten by incoming data from an active register.
Data can be transferred between the active and holding registers either every
15 or every 30 minutes. No other transfer periods are available.
Figure 11-6
OM flow showing active, holding, and accumulating registers
Active, Holding, and Accumulation Registers

Event, usage or High watermark counters
Active Register
Available through
OMSHOW
command
Holding Register
Available through
OM Studies
Accumulating Register (out of scope of
this course)
Accumulating register
Accumulating registers gather the data from the holding registers for a user-
defined time period. For example, the active-to-holding transfer occurs every
15 minutes and the busy hour of the day must be determined. The
accumulating registers must be set up so that data is gathered for an hour’s
worth of data from the holding registers every hour at 15-minute intervals.
Every time a new transfer period of data is sent to the accumulating registers,
it is added to the registers’ current count value.
In the active and holding registers, all registers gather data continuously.
None of these registers can be turned off.
Not all accumulating registers must be turned on. The service provider
decides which registers gather data and which registers do not. This is
accomplished by setting up OM classes; the registers that are members of an
OM class are always accumulating registers.
Extension registers
When there is a possibility that the active count may exceed 65,535 in the
maximum count period (30 mins), an extension register will be allocated. If

an extension register exists, its name will normally be similar to that of the
basic register (i.e. CCBSZ2 is an extension for CCBSZ).
Figure 11-7
OM flow showing active and holding extension registers
Active and Holding Extension Registers

Event,usage count,
or High watermark
Extension
Active Register Active Register
Overflow
Holding Register Holding Register
Figure 11-8
Relationship between an OM class, group, and register
OM Class, Group, and Register

Relationship (1/2)
OM class
CALL PROCESSING
OM groups
MSCCP
…/...
INCATOT
MMBID,MMBID2, MLBID,MLBID2, MMSUCC, MMSUCC2, MLSUCC, LMBID,

LMBID2, LMSUCC, LMSUCC2, MMESTAB, MMESTAB2, MLESTAB, MLESTAB2,
LMESTAB, LMESTAB2, MMRESAUD, MSRESAUD, MSANN, MSANNTRT, OM counters
MEESTAB, TAIMSIC, TAIMSIC2, TATMSIC, TATMSIC2

Figure 11-9
OM class, group, and register relationship
OM Class, Group, and Register

Relationship (2/2)
Registers
Description examples:
MEESTAB: Number of mobile emergency call establishments
LMESTAB: Established land-to-mobile calls
MSANN: Number of calls from/ to announcement reached
through normal routing
LMBID: Number of bids originated from the fixed network
and destined to the Mobile Stations of a Mobile-
services Switching Center
LMSUCC: Number of bids destined to the Mobile Stations
(of a Mobile-services Switching Center) which
have replied to the paging request and
completed a traffic channel seizure
MLBID: Number of mobile-to-land bids
MLESTAB: Established mobile-to-land calls
MLSUCC: Number of successful mobile-to-land bids
MMBID: Number of mobile-to-mobile calls
MMESTAB: Established mobile-to-mobile calls
MMRESAUD: Number of recovered calls by logical resource
audit for mobility management trunk ID
MMSUCC: Number of successful mobile-to-mobile bids
MSANN: Number of calls from mobile-to-announcement
reached through normal routing
MSANNTRT: Number of calls from mobile-to-announcement
reached through treatment in the MSTREAT
table
MSRESAUD: Number of recovered calls by logical resource
audit for Mobile Station trunk ID
Accumulating OM data
OM groups
An OM group is made up of a cluster of OM registers that all pertain to the
same structure in the DMS-MSC. Since registers INCATOT and TRU relate
to trunks, they are assigned to the OM group called trunks (TRK). There are
other OM registers such as PRERTEAB, INFAIL, etc. that also monitor the
activity of trunks; consequently, these registers are also assigned to OM group
TRK.
To determine all OM registers that monitor trunks, registers must be assigned

to the OM group TRK. The same is true with other registers in the switch. For
example, the individual registers that monitor the activity of receivers
(RCVTRU, RCVSZRS, RCVOVFL, etc.) are assigned to the OM group
RCVR.
Viewing OM groups
To view OM groups, enter the following at the CI prompt:
EXAMPLE: >
OMSHOW <group>
For a list of possible <groups>, do the following:

EXAMPLE: >
Q OMSHOW
OM classes or studies
An OM class is a customer-defined set of registers and OM groups all placed
under one name. For example, the cellular service provider wants to gather
data on mobile originations on a cell site controller (CSC) and an intelligent
cellular peripheral (ICP). Two groups of registers are involved. To make it
simpler, these two OM groups are combined into one class named Mobile
Organizations.
Also, it is important to note that not all registers within an OM group must be
members of a class. A class is created by the user. Those registers not
applicable can be deleted from the OM class. Registers cannot be defined
within an OM group, because these groups are predefined by Nortel.
The service provider defines the class. The service provider also decides what
groups and what registers within those groups make up a particular class. For
example, the provider wants to study the events related only to incoming
traffic on a trunk. To do this, an OM class made up of the OM group TRK is
set up; however, some of the registers within group TRK relate to outgoing
traffic events; it is then necessary to determine which registers deal with
outgoing traffic and delete these registers from the class.
OM class usage
Time and data relevance are two reasons to combine OM groups into classes:
• Time. OM classes are customized to meet specific needs. By combining
OM groups into classes, the service provider can quickly obtain relevant
data. The sooner information is gathered about the system, the faster any
maintenance trouble can be fixed, traffic can be balanced, or equipment
can be provisioned.
• Data relevance. The service provider is the creator of the OM class. The
provider decides what combination of groups and registers provide the
relevant data.
Example of OM group and counters

Figure 11-10 illustrates a typical OM and includes, the following data:
• Class is the customer-defined measurement or type of register displayed.
• Start/Stop is the time that the measurement or registers collected data.
• Samples are the number of SLOWSAMPLES (100 second scans) and
FASTSAMPLES (10 second scans) incurred during the measurement.
Fastsample and slowsample scans are used for usage counts.

• Groups consist of the selected groups that accumulated data.

• Fields include the specific registers selected for accumulation.
Figure 11-10
Example of OM log
Example of OM Group & Counters
>o m s h o w c7mtp holding
CLASS: HOLDING
START:1998/06/17 15:30:00 WED; STOP: 1998/06/17 16:00:00 WED;
SLOWSAMPLES: 18 ; FASTSAMPLES: 180 ;
C7MSIDPC C7MSISIO C7XSDYWT C7XSDYNT
C7PHDYWT C7PHDYNT C7GTT95 C7NGTT95
C7SMPWT1 C7SMPWT2 C7SMPNT1 C7SMPNT2
0 0 0 0
0 0 0 0
0 0 0 0
Log reports and LOGUTIL 11

Logs are records of subsystem messages that are the result of activities; such
as software errors, fan failures and equipment diagnostics. Logs allow
operating personnel to better identify the exact location of a problem.
Log report system

The DMS-MSC generates reports on activities/events within the system
components; such as software errors, hardware faults, system tc. These output
reports are Log Reports and are collected within Log Buffers.
The log report system:

• is composed of several subsystem log buffers
• groups and stores the reports in different log buffers by the originating
subsystem, (such as the CM, MS, TRKS, PM) which generates the log
report.
The log buffers can hold several hours of reports and are stored in the order
they arrive at the buffer. Once the buffer is full, the next report generated
displaces the oldest report. The displaced report is purged, unless it has been
previously routed to a permanent storage device (for example a disk).
Logs may be lost by a cold switch restart.
As operating company personnel, to assist in performing system diagnosis

and maintenance activities, you can access these logs.

Figure 11-11 illustrates the Log Buffer organization in CM memory.
Figure 11-11
Log buffers in CM memory
Log Buffers in CM Memory

CM Memory
MS CM
PM TRKS
Log Buffer
Figure 11-12 illustrates the FIFO Log buffer.
Figure 11-12
Log buffer
Log Buffer (FIFO)
Oldest Log Report Latest generated Log Report
First Last
Log Buffer
Log Reports
Forward Back
Log reports
A log report is a record of an event that provides information for maintenance
and administrative purposes. An event can be an equipment fault, a test, a
change in state of a piece of equipment, a software error, etc. The record of
the event identifies the date and time the event occurred, the type of event
(fault, test, software error, etc.), the equipment which caused the report to be
generated, the subsystem which detected or caused the report and the
particular event itself (type of faults, tests, software error etc.).

Figure 11-13
Log report example
Log Report Example
TRAININGCNTR NET120 DEC31 14:38:50 7000 FAIL NET LINK NET 1- 0 LINK27 SPEECH TEST FAILED
Sequence Number or Log Report Number

Log Report type or name
Date
& Equipment ID
Event ID, Equipment Type
Information:
Time
Site
Event Type
Report format
Each report is printed in a standard format containing the following data:
• site is where the log is generated
• alarm type—every report type generated is assigned an output report
class. The class governs where (output device) the report is routed. Table
LOGCLASS assigns the output report classes (0-31). The level of alarm is
defined as follows:
— blank - status indicator or non-service affecting change of state
— * - minor alarm
— ** - major alarm
— *** - critical alarm
• report name (ID) is an identifier consisting of two parts:
— logname is a two-to eight-character name that identifies the
subsystem that generated the report.
— report number is a three-character number that specifically identifies
a report within the subsystem. A number is not assigned to all log
reports.
• date is the date in month/day on which the event occurred
• time is the time in hours/minutes/seconds (12:15:43) that the event
occurred
• sequence number is a four-digit number indicating the number of times a
report is generated since the switch was commissioned. This number will
reset to 0000 after reaching the count of 9999.
• event type is the type of event that caused the report to be generated
• event ID is the identity of the event that caused the report to be generated
• equipment type is the type of equipment to which the report corresponds
• equipment ID is the identity of the equipment to which the report
corresponds

Figure 11-14
Report format
Log Report Example (2)
LAST TRAININGCNTR TRK103

** APR01 12:00:00 2100 FLT GROUP ALARM N5LOOP 75% BUSY
(MOST RECENT)
BACK TRAININGCNTR TRK105

** APR01 11:59:00 2200 FLT GROUP ALARM N5LOOP 55% BUSY
(IN TIME)
FORWARD TRAININGCNTR TRK110 APR01 11:59:30 2300 SBSY LOCKOUT ON

(IN TIME)
CKT OGTOCARR1 2001
NILC
FIRST TRAININGCNTR TRK103 APR01 11:55:50 2400 FLT GROUP ALARM N5LOOP 75% BUSY
(OLDEST)
REPORT NAME
SEQUENCE #
EVENT TYPE
DATE
SITE
ALARM
TIME
EQUIP TYPE
& EQUIP ID
EVENT ID,
105065
060289
Accessing a log
The OPEN command under LOGUTIL allows a user to access a particular
Log Buffer and display its most recent Log Report.
After entering this command, a user can access any report which has been
generated by entering the following commands: FIRST, LAST, BACK,
FORWARD and WHILE (BACK) ().
For more information, see “LOGUTIL”.
LOGUTIL 11
LOGUTIL allows you to look in any log buffer and examine the contents (log
reports) for information concerning switch operations.
LOGUTIL is a software utility that temporarily controls the routing,

classification and collection of log reports. Through the use of the commands
found in LOGUTIL, a user manipulates the reports and the devices that
collect and print log reports. LOGUTIL also controls the output printing of
operational measurement accumulation reports.
To enter the LOGUTIL system, enter the following command line:

LOGUTIL
Functions of LOGUTIL commands

LOGUTIL commands are grouped into five different functions. LOGUTIL
functions and associated commands are defined in the following pages. See
Figure 11-15.
Figure 11-15
LOGUTIL command functions
LOGUTIL Functions & Commands
FUNCTION COMMANDS
Browsing OPEN, FORMAT, TYPE, CLEAR, FIRST, LAST, BACK, FORWARD
Information LISTLOGS, LISTREPS, LISTROUTE, LISTDEVS, LISTTIME

Browsing the logs

These LOGUTIL commands are used to search log buffers associated with
each subsystem.
The following is a list of these commands:
• To access a particular log buffer and display its most recent report, enter:
OPEN <Log name>
You can access a particular log report by entering FIRST, LAST, BACK,
FORWARD or TYPE.
Example
> OPEN TRK
> DONE
> TRK106 MAR10 12:36:44 5000 FAIL CKT

RCVRDGT 8 DIAGNOSTIC RESULT FUNCTIONAL
TEST FAIL ACTION REQUIRED REPLACE CARD
CARD TYPE 2X48AB
To change the format of output reports, enter:
FORMAT
The options are short and normal. The short option provides a less
detailed description of the log reports when they are displayed.
Note: Do not use this command during class unless instructed to do so by

the instructor.
To move within an open log buffer, use one of the following command:
• FIRST
Moves the cursor to the first (oldest) report in the current LOG buffer. No
display is given. Before entering this command, you must first OPEN a
log.
• LAST
Moves the cursor to the most recent report in the current LOG buffer. No
display is given. Before entering this command, you must first OPEN a
log.
• BACK
Displays the previous report in the current log. If there is not a report
which matches this condition, BACK returns a NOT FOUND.
Before entering this command, you must first OPEN a log. The command
OPEN displays the most recent report in the log.
Example
> BACK
> (The next most recent report is displayed.)
CI> Logutil; open CM; BACK
> NOT FOUND
• FORWARD
Displays the next report in the current log. If there is no report which fits
this condition, a NOT FOUND is displayed.
Before entering this command, you must first OPEN a log.
Example
> FORWARD
> (The next report is displayed)
CI> Logutil; open CM; FORWARD
> NOT FOUND
Table 11-1 provides examples and descriptions of the browsing commands,

along with some of the parameters which may be used with them. The
instructor will explain the function of these parameters.
Table 11-1
Searching log buffers associated with each subsystem
Command Parm example Description

FORMAT >FORMAT NORMAL Sets the output format for all reports.
>FORMAT SHORT
CLEAR >CLEAR PM Erases ALL log reports from the PM
buffer.
OPEN >OPEN PM Displays most recent log report in the PM
subsystem.

Command Parm example Description

BACK >BACK Shows the log generated before the
current log report.
>BACK ALL, or
Displays ALL logs in a buffer.
>WHILE BACK ( )
FORWARD >FORWARD Shows the log generated after the current
log report.
>FORWARD ALL, or
>WHILE FORWARD ( )
FIRST >FIRST Displays the first (oldest) log report in a
buffer.
LAST >LAST Displays the last (most recent) log report
in a buffer.
TYPE >TYPE Prints the current report entry.
Getting information about logs

Use the following command to get information about logs:
• LISTLOGS prints a list of all the log names defined in the switch.
• LISTREPS lists the following for each log report name in the switch:
— report I.D
— output report class
— report event type
— report event I.D
— I/O device to which the report is routed
— an indication of whether or not the report I.D. is suppressed
— whether or not the report has a threshold
1. What is the difference between a peg counter and a usage counter?
2. What is LOGUTIL?
3. What is a log report?
4. What command do you use to display the latest Log Report in Log Buffer
CM?.
5. Name the five LOGUTIL functions.

Lesson 12
NTPs and Helmsman
Objectives 12
will be able to:
• describe how Nortel Networks Technical Publications (NTPs) are

organized
• describe the NTP numbering scheme
• use Helmsman to access NTPs
• search information in NTPs

12-2 NTPs and Helmsman Nortel Networks Confidential
NTPs and Helmsman 12

The amount of Nortel product documentation can be overwhelming.
Developing an understanding of how the documentation is organized and
structured will help you find information in a timely manner.
This lesson provides an overview of the NTP documentation structure. In

particular, it emphasizes the DMS-MSC and DMS-HLR publications. This
lesson also covers the Helmsman software, which is used to view NTPs
provided on the GSM CD-ROM and other Nortel CD-ROMs.
NTPs
NTPs are a series of documents that follow a specific numbering pattern and
provide information on DMS products. The numbering system is composed
of a ten digit format that has three functional parts: division number, layer
number, and group number. An example of the format is shown in Figure 12-
1.
Figure 12-1
Components of an NTP number
Components of an NTP Number
Layer Number
411-2231-001
Division Number Group Number
411-0930-001 12.02/EN December, 2000 Lesson 12 NTPs and Helmsman 12-3
Nortel Networks Confidential NTPs and Helmsman 12-3
Division number
The first 3 digits identify the broad subject matter of the publication. These
numbers are generally associated with a family of switches or products, all
having a common function or design. For example, NTPs with a 411 division
number contains information about Nortel’s wireless/cellular systems. Also,
NTPs with a 297 division number contain information common to all DMS
switches. These two division numbers are commonly used by DMS-MSC/
HLR technicians.
Layer number
The next four digits of the ten digit number define the contents of a particular
NTP within the series. It provides details on a specific switch within the broad
category. For example, 2231 indicates a manual that deals specifically with
the DMS-MSC.
Group number
The last three digits of the ten digit number identify a specific area of that
switch, and are known as group numbers. The group numbers range from
000-899 and have the same function for each switch type. For example, 510 is
a Logs reference manual NTP for any digital switching system.
DMS-MSC/HLR documentation
DMS-MSC/HLR publications use particular division and layer numbers as
shown in Table 12-1.
Table 12-1
Division and layer number
Division number Layer number

411 --Wireless Family 2831 ---DMS-MSC
All layer numbers
297-- DMS-100 Family
The group number categorizes information by function. Group categories are

divided into subgroups to indicate specific information contained within each
group. Refer to Table 12-2.
Table 12-2
Group number
Group number Description

000 to 099 Index and product guide
100 to 199 Planning and engineering.

Group number Description

200 to 299 Installation
300 to 399 Administration
400 to 499 Administration/reference
publications
500 to 599 Operation and maintenance
600 to 699 Reserved for future use
800 to 899 Reference publications
DMS-MSC/HLR product documentation directory

The Product Documentation Directory (NTP 411-2231-001 for the MSC and
HLR) provides a listing of all NTPs required for operating and maintaining
the DMS-MSC and DMS-HLR. This information is contained in numerical
and alphabetical tables. It lists the NTP title followed by the NTP ten digit
number.
NTPs and other Nortel documents usually exist in more than one version. Use
the DMS-MSC/HLR Product Documentation Directory to determine the
correct release code for a specific software release.
DMS-MSC/HLR documentation listing

Table 12-3 numerically lists documentation specific to the DMS-MSC and
DMS-HLR.
Table 12-3
DMS-MSC/HLR documentation
DMS-MSC/HLR Product Documentation Directory 411-2231-001

DMS-MSC Product Guide 411-2231-010
DMS-MSC Software Delta 411-2231-199
One Night Process 411-2231-303
CCS7 Family Application Guide 411-2231-310
DMS-MSC Customer Data Schema 411-2231-451
DMS-MSC Office Parameters 411-2231-455
DMS-MSC Output Reports (logs reference manual) 411-2231-510
DMS-MSC Maintenance Administration Position 411-2231-809
Commands Reference Manual
DMS-MSC Operational Measurements Reference Manual 411-2231-814
DMS-MSC IWF Interconnection Guide 411-2231-927
DMS-HLR Product Guide 411-2831-010

DMS-HLR Software Delta for Planners 411-2831-199
DMS-HLR Customer Data Schema Reference Manual 411-2831-451
DMS-HLR Office Parameters Reference Manual 411-2831-455
DMS-HLR Output Reports (logs reference manual) 411-2831-510
DMS-HLR Maintenance Administration Position 411-2831-809
Commands Reference Manual
DMS-HLR Operational Measurements Reference Manual 411-2831-814
Helmsman CD-ROM
Helmsman is a software tool that provides access to the latest NTPs stored on
CD-ROM (Compact Disk - Read Only Memory).
There are several advantages to CD-ROM formatted documentation including:

• requiring less physical storage space one CD-ROM compared to a whole
library)
• providing quick and easy access to information by the use of search tools
• allowing the user to make annotations, bookmarks, and hyperlinks in the
software for quick future access of information
The instructor and the exercises in this lesson demonstrate the advantages of
this software program.
GSM CD-ROMs
All NTPs that are GSM specific (specifically, those that are listed in
Table 12-3) are included on one CD-ROM part number HLM-2231-001. In
addition to the GSM NTPs, numerous other NTPs needed for operating and
maintaining the various GSM network components are contained on this CD-
ROM.

1. Describe the purpose of Nortel’s customer support and technical service

departments.
2. Name three advantages of the CD-ROM format documentation system.
3. What is the purpose of the NTP numbering scheme?

Exercise 12-2 Explain Helmsman Features

Instructions 12
Use the Helmsman user’s guide to answer the following questions. If you
have any questions, you may ask a colleague or the instructor for assistance.
Questions 12
1. Docubase browser window:
a. Explain the “Document Selection” window.
b. Explain the “Page Selection” window.
2. Search Editor window:

a. Explain the “Search in” pull-down menu.
b. Explain the “Search term (or phrase history)” window.
c. Explain the “Search proximity” function.
Located across the top of the screen are several menus.
3. Window menu.
a. Explain the window menu.
4. Annotate menu:
a. Contrast annotations vs. bookmarks.
b. Explain the “Marks List”.
5. Navigate menu:
a. Explain “Next Occurrence and Previous Occurrence”.
6. Search menu:
a. Explain “Limiting by Category”.

Answers
1. Docubase browser window:
The document selection window lists all of the documents in which the
search terms were found.
The page selection window lists the page numbers and the number of
occurrences per page in each document in which the search terms were
found. You can go directly to the page by double-clicking on the page
number.
2. Search Editor window:

The Search in pull-down menu allows you to search the docubase in all of
the document text, document numbers, or document titles. You can also
search in a specific document.
The Search term window lists all of the search terms that pertain to a
particular search.
The Search proximity function allows you to control the size of the
Search Set. It has to do with how many words separate terms in the
Search Term window that are connected by the boolean operator AND.
The larger the proximity, the more likely it is to find occurrences of the
terms linked by the AND operator.
3. Window menu.
The window menu lists all of the viewer windows that are open. A check
mark indicates the current active window. You can make a window in
the list active by selecting it. The CASCADE and TILE options affect
how the windows are placed on the screen in relation to each other. Try
these options and see if you have a preference for a configuration.
4. Annotate menu:
Annotations are marks you can place on documents for later reference.
You can also enter notes to clarify or explain the part of the text it marks.
Bookmarks only allow you to mark the text for later reference.
The Marks List shows the bookmarks and annotations you have made
for the document, along with the page on which the mark is found. It can
be used as a table of contents for your marks and as a quick way to open
a document to references you use regularly.
5. Navigate menu:

Next occurrence allows you to go to the next occurrence of the search

term within a document while previous occurrence goes back to the prior
occurrence.
6. Search menu:
The Expand Plurals box allows Helmsman to search for the singular as
well as the plural form of the search term.
Limiting by category reduces the number of documents before you run a

search. It creates a subset of documents that fall into specific categories
and classifications. Helmsman groups classifications into 3 categories.
Keep in mind that the categories and classifications may differ from one
library to another.
Exercise 12-3 Helmsman sample session

Instructions 12
Complete this exercise. You may practice as many times as you like. If you
have any questions, ask the instructor for assistance. Then compare your
answers with the self check at the end of the lesson.
Questions 12
Work through Appendix D of the Helmsman user’s guide at a Helmsman
workstation. When you arrive at the section on Search Proximity, use a value
of 10 instead of 1.
Note: Since Nortel produces hundreds of different CD-ROMs for its

various product lines, the docubase used in Appendix D differs from the
ones used in this exercise. This results in different documents being found
in the searches performed. If this happens, disregard these differences and
continue to the next step.

Exercise 12-4 Using Helmsman

Use the Helmsman user guide and Helmsman CD-ROM system to answer the
following questions:
Note: Be sure to check the search term window before every search and
verify that the search terms and Boolean operators (and/or) are the ones
you want. Delete any search terms that do not apply.
1. Locate and open NTP 297-1001-592. Using the Search Editor, locate the
beginning of the section on clearing sysb faults and place a bookmark
there (Name it “SYSBfault”).
2. Using the Search Editor, go to point in the book which talks about the
Ethernet interface unit and troubleshooting a critical alarm. Use the
boolean expression “and” to search for all three words highlighted above.
Place a bookmark at this point. (Name it “EIUcritical”).
3. Close the document.
4. You have just started as a new technician and want to find the NTP on
how to perform routine maintenance.
a. Using Helmsman locate the NTP that contains information on
peripheral module maintenance. What is the NTP name and number?
b. Open the peripheral module maintenance and use the Search Editor to
locate the procedure on inspecting cooling unit filters. Use the Search
Editor and key words cooling unit filters. How often should the filter
be replaced?
5. What feature in Helmsman allows you to get a list of all of the bookmarks
and the page numbers they are on? Delete the bookmarks.
6. As a maintenance technician, the Table LTCINV is used quite often. What
is the description of this table? HINT: Customer Data Schema NTPs
usually define this type of information.
Answers
1. No question asked at this step.
4.
a. Peripheral Modules Maintenance Guide NTP 297-1001-592
b. every 3 months
5. Under the Annotate menu, the Marks list... selection will display all the
bookmarks and/or annotations in the open NTP.
6. Table LTCINV contains the inventory data, except the P-side link
assignment, for various peripheral module (PM) types.
Note: This information was found in NTP 297-1001-451, Customer Data

Schema Reference Manual.

Lesson 13
DMS-MSC call processing
Objectives 13
will be able to:
• describe the function of the DMS-MSC/HLR call processing software
• describe the progress of a typical call setup through the DMS-MSC and
DMS-HLR components

13-2 DMS-MSC call processing Nortel Networks Confidential
Call processing 13
The DMS-MSC call processing software consists of the code and data
necessary for advancing a call from setup to tear down. A call consists of a
series of information exchanges between the SuperNode and the peripheral
modules. The software is designed to provide a flexible system capable of
supporting a number of features and call types. The DMS-MSC is used in all
examples in this lesson.
Note: Other DMS family switches handle some call processing functions
in slightly different ways than the DMS-MSC.
Call processing begins when the SuperNode receives a message indicating an

event occurred, such as a trunk seizure, disconnect, etc. A peripheral processor
informs the SuperNode whenever such an event occurs. The SuperNode
computing module then starts up the appropriate call processing software. The
call processing action taken by the SuperNode depends on the following:
• type of message received (origination, digit)
• call state (dialing, talking)
• call processing characteristics of the terminal on which the event was
detected, such as idle, busy, etc.
• call processing characteristics of the call, including dialing plan, features,
etc.
Nortel Networks Confidential DMS-MSC call processing 13-3
Call processing architecture

The DMS-MSC is the heart of the wireless system. It performs all the
switching functions needed for the MSs located in its geographical area.
Specifically, its functions include the following:

• resource management during a call
• call establishment and routing
• echo suppression
• call control and signaling
The DMS-MSC must charge subscribers for the services it provides. It is

expected that service providers individually construct sophisticated billing
arrangements. Service invocation, internetwork roaming and local and long-
distance usage all have complicated billing beyond what is normally needed
in the fixed network. Thus, billing data must be taken into account when
provisioning signaling links and the DMS-MSC processing load. Often the
load on a DMS-MSC is large enough that a separate billing server is deployed
as shown in Figure 13-1.
Figure 13-1
DMS-MSC call processing architecture
Call Processing Architecture

CCC
MS 0
1
S 0
1 Application
L CM
M Processor
RTIFs
Message Links
ENET 0
1
M&A 0
IOC 1
Voice and Message Links
MTD
PMs
VDU VDU LPP PDTC PDTC
PTR
DDU
BSS
PSTN
SMS CCS7 V.35
411-0930-001 12.03 February, 2001 Lesson 13 DMS-MSC Call Processing 13-4
Note: DS30 and DS512 are industry standards of DS1 signals.

PSTN to mobile call progression

This section shows the progression of a call through a DMS-MSC switch.
The steps are explained using the following events:

1. A call enters the switch from the PSTN.
2. Data is sent to the ENET, through the LPP, through the MS, to the CM.
3. Translations are performed on the dialed digits by the CM.
4. Data is sent to the LPP.
5. A send routing information (SRI) request is sent to the HLR.
6. Routing information is sent to the DMS-MSC.
7. The MSRN is translated to route call.
8. The call leaves the switch.
Note: The sample call progression is for a land-to-mobile call

terminating on the same switch (intra-MSC).
Call progress description

Figure 13-2 illustrates the call progressing between the PSTN and the mobile.
Figure 13-2
PSTN to mobile call: IAM message
PSTN to Mobile Call Process

PSTN to Mobile Call: IAM Message
DMS-MSC
VLR
CM MS DMS-HLR
CM
MS
LPP
LMS 1 LMS 0 LMS 1

LMS 0
L L
I N ENET I ENET
I U
U
7 U 7
L V 35 Link
I
U
7
L L
I N
I I
U PDTC PDTC U
U
7 7
PDTC PDTC
1. IAM [MSISDN] C7
PCM 30
PSTN
1. An originator incoming call is picked up by a PCM-30 digital trunk

controller (PDTC).
For this example, the PDTC connection to the ENET is a DS30
connection. The ENET sends the incoming call to the LPP cabinet for C7
signaling management.
— The MSISDN is sent to ENET and on to the MS.

The LIU7 decapsulates the CCS7 message flow and passes the
message to the MS.
— Translations are performed at the CM level.

The data is sent to the CM where translations are performed on the
incoming digits.

— Data is sent back to the LPP.

The CM delivers a DBQ SRI in the MAP message through the MS to
the LPP.
2. The SRI Request is sent to the DMS-HLR.

An SRI request is sent to the HLR via the CCS7 network. The LPP sends
the message through the CCS7 network to the HLR.
Figure 13-3
PSTN to mobile call: SRI message
PSTN to Mobile Call Process (cont.)

PSTN to Mobile Call: SRI Message
DMS-MSC
VLR
CM MS
DMS-HLR
CM
MS
LPP
LMS 0 LMS 1
LMS 0 LMS 1
L
I N
I L
U I N
U ENET
7 2. SRI [MSISDN] U I
L 7 U
I
V 35
U ENET
7
L
I L
U PDTC PDTC I
7 U
7
PDTC PDTC
PCM 30
PSTN
3. The Routing Information Sent to the DMS-MSC

The HLR returns routing information, including PRN to the DMS-MSC.
The HLR returns:

a. PRN message to the LPP within the PRN-ACK message.
b. LPP transmits it to the CM.
Figure 13-4
PSTN to mobile call: PRN message

PSTN to Mobile Call: PRN Message
DMS-MSC
VLR
CM MS
DMS-HLR
CM
MS
LPP
LMS 0 LMS 1
LMS 0 LMS 1
L
I N
I L
U I N
U ENET
7 3. PRN [IMSI] U I
L 7 U
I L
V 35
U ENET I
7 U
L 7
I L
U PDTC PDTC I
7 U
7
PDTC PDTC
PCM 30
PSTN

4. PRN-ACK is translated to route the call.

The PRN-ACK is sent to the CM where it is translated.
Figure 13-5
PSTN to mobile call: PRN Ack message

PSTN to Mobile Call: PRN Ack Message
DMS-MSC
VLR
CM MS
DMS-HLR
CM
MS
LPP
LMS 0 LMS 1
LMS 0 LMS 1
L
I N
I L
U I N
7 U
4. PRN_ACK [MSRN] U I ENET
L 7 U
I L
U V 35 ENET I
7 U
L 7
I L
U PDTC PDTC I
7 U
7
PDTC PDTC
PCM 30
PSTN
5. The HLR sends an SRI_ACK message to the MSC. The following figure
illustrates the message passthrough the HLR and MSC.
Figure 13-6
PSTN to mobile call: SRI Ack message

PSTN to Mobile Call: SRI Ack Message
DMS-MSC
VLR
CM MS
DMS-HLR
CM
MS
LPP
LMS 0 LMS 1
LMS 0 LMS 1
L
I N
I L
U I N
U ENET
7 5. SRI_ACK [MSRN] U I
L 7 U
I L
U V 35
I
7 ENET U
L 7
I L
U PDTC
7 PDTC I
U
7
PDTC PDTC
PCM 30
PSTN

6. After the translation, the MSC decides to page the MS:

• The translation results in a paging message to the mobile station through
the LPP, ENET (using channelized access), and to the BSS.
Figure 13-7 illustrates the message through the MSC elements to the MS.
Figure 13-7
PSTN to mobile call: paging message

PSTN to Mobile Call: Paging Message
DMS-MSC
VLR
CM MS
DMS-HLR
CM
MS
LPP
LMS 0 LMS 1
LMS 0 LMS 1
L
I N ENET L
U I
U I N
7 U I ENET
6. Paging U
L 7
I L
U I
7 U
N L 7
I I L
U U PDTC PDTC I
7 U
7
PDTC PDTC
PCM 30
PSTN
A-1 Glossary Nortel Networks Confidential
Glossary A
A
AIN
Advanced Intelligent Network
ANSI
American National Standard Institute
ASCII
American Standard Code for Information Interchange
ASU
Application Specific Unit
B
BSS
Base Station Subsystem
C
CADR
Call Associated Data Record
CISM
Cabinetized ISM
CCS7
Common Channel Signaling 7
CDR
Call Detail Recording
CIOE
Cabinetised Input/Output Equipment
CM
Computing Module
CM
Configuration Management; Core Module
CO
Central Office
CPU
Central Processing Unit
CTM
Conference Trunk Module
D
DAT
Digital Audio Tape
DDU
Disk Drive Unit
DIRP
Device Independent Recording Package
DMS-MSC
Digital Multiplex System-Mobile Service Switching Center
DNI
Digital Network Interconnecting
DPCC
Dual Plane Combined Core
DPN
Data Packet Network
DRAM
Digital Recorded Announcement Machine
DTCI
Digital Trunk Controller ISDN
DTCO
Digital Trunk Controller For Offshore
Nortel Networks Confidential Glossary A-3
E
EDRAM
Enhanced Digital Recorded Announcement Machine
EIR
Equipment Identity Register
EIU
Ethernet Interface Unit
EIU
Ethernet Interface Units
EMPC
Enhanced Multi-Protocol Controller
ENET
Enhanced NETwork
ETSI
European Telecommunication Standard Institute
F
FLIS
Fiberized Link Interface Shelf
FM
Fault Management
FP
File Processor
ISME
Frame ISM
FRU
Field Replaceable Unit
FSP
Frame Supervisor Panel
FTFS
fault-tolerant file system

G
GCDR
GSM Call Data Record
GMSC
DMS-MSC Gateway
GUI
Graphical User Interface
H
HLR
Home Location Register
HLR-PS
HLR-Provisioning Server
HMI
Human-Machine Interface
HLR-PS
Home Location Register Provisioning Server
I
IMEI
International Mobile Equipment Identity
INAP
Intelligent Network Application Part
IN
Intelligent Networks
IOC
Input/Output Controller
IOD
Input/Output Device
IOE
Input /Output Equipment
IOM
Input/Output Module
IP
Intelligent Peripherals
ISDN
Integrated Services Digital Network
ISM
Integrated Service Module
IWF
Interworking Function
J
JF
Journal File
L
LIS
Link Interface Shelf
LIU7
Link Interface Unit for CCS7
LIU
Link Interface Unit
LMS
Local Message Switch
LPP
Link Peripheral Processor 2

M
MAP
Maintenance and Administration Position
MC
Message Controller
MEB
Mate Exchange Bus
MF
Multi Frequency
MPC
MultiProtocol Controller
MS
Message Switch
MTD
Magnetic Tape Drive
MTM
Maintenance Trunk Module
N
NCAR
Non Call Associated Data Record
NIU
Network Interface Units
NSS
Network and Switching Subsystem
O
OAM&P
Operation, Administration, Maintenance, and Provisioning
OAU
Office Alarm Unit
OAU
Office Alarm Unit
OMC-S
Operations And Maintenance Center Switching
OM
Operational Measurement
OSS
Operations Support Systems
P
PBX
Private Branch Exchange
PCM
Pulse Coded Modulation
PDTC
PCM30 Digital Trunk Controller
PEC
Product Engineering Code
PM
Performance Management
PRI
Primary Rate Interface
PSDN
Packet Switching Data Network
PSTN
Public Switch Telephone Network
PSU
Power Supply Unit

R
RTIF
Remote Terminal Interface
S
SCC
Simple Combined Core
SCP
Service Control Point
SCSI
Small Computer Serial Interface
SDM/FT
SDM/Fault Tolerant
SDM
SuperNode Data Manager
SLM
System Load Module
SMS-SC
Short Message Services Service Center
SNSE
SuperNode Size Enhanced
SS7
Signaling System 7
SSP
Service Switching Point
T
TC
Terminal Controller
TDMA
Time Division Multiple Access
TDM
Time Division Multiplexed
TS
Time Slot
TUPLE
V
VDU
Visual Display Unit
VME
Virtual Machine Engine
X
XFER
Remote Data Polling System

Family Product Manual Contacts Copyright
GSM
DMS-MSC/HLR
Student Guide
To order Wireless Solutions documentation, call

1-800-NTI-CARE (1-800-684-2273)
To report a problem in Wireless Solutions documentation, call
1-800-NTI-CARE (1-800-684-2273)
or send e-mail from the Wireless Solutions Training and Documentation World Wide Web site at
http://www1.nortelnetworks.com/wireless/DocuTrain/
Copyright  1996–2001 Nortel Networks, All Rights Reserved
NORTEL NETWORKS CONFIDENTIAL

The information contained herein is the property of Nortel Networks and is strictly confidential. Except as expressly authorized in
writing by Nortel Networks, the holder shall keep all information contained herein confidential, shall disclose it only to its
employees with a need to know, and shall protect it, in whole or in part, from disclosure and dissemination to third parties with the
same degree of care it uses to protect its own confidential information, but with no less than reasonable care. Except as expressly
authorized in writing by Nortel Networks, the holder is granted no rights to use the information contained herein.
Information is subject to change without notice. Nortel Networks reserves the right to make changes in design or components as
progress in engineering and manufacturing may warrant.
Trademarks are acknowledged with an asterisk (*) at their first appearance in the document.
Course number: Course 930
Product release: GSM12
Document version: Standard 12.03
Date: February 2001
Printed in the United States of America

411-0930-001 12 03

Загружено:

Сведения о документе

Исходное описание:

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

411-0930-001 12 03

Загружено:

Авторское право:

Доступные форматы

Course 930

GSM12 Standard 12.03 February 2001

Course number: Course 930

Copyright Country of printing Confidentiality Legal statements Trademarks

Copyright  1996–2001 Nortel Networks, All Rights Reserved

NORTEL NETWORKS CONFIDENTIAL

GSM GSM DMS Overview Student Guide GSM12

GSM GSM DMS Overview Student Guide GSM12

Base layer 2-37

GSM GSM DMS Overview Student Guide GSM12

Call Intercept System (CIS) 7-14

GSM GSM DMS Overview Student Guide GSM12

Log report system 11-15

GSM GSM DMS Overview Student Guide GSM12

Figure 2-14 C7 link limitations 2-30

Figure 7-6 OMC-S software architecture 7-9

GSM GSM DMS Overview Student Guide GSM12

About this course

GSM GSM DMS Overview Student Guide GSM12

NSS training curriculum 0

NSS Training Curriculum

GSM DMS Engineer

GSM DMS Engineer

• GSM NSS Overview (931/2 days)

The overview course provides the student with a basic understanding of a

GSM DMS engineer (beginner)

• GSM DMS Maintenance Part 1 (950/5 days)

GSM DMS engineer (expert)

• GSM DMS Maintenance Part 1 (950/5 days)

• GSM DMS Maintenance Part 2 (951/10 days)

• SDM/FT Maintenance and Administration (955/2 days)

GSM GSM DMS Overview Student Guide GSM12

The SDM/FT Maintenance and Administration course provides skills for

• OMC-S Overview & Operation (937/2 days)

GSM MSC/VLR datafill engineer

• GSM CCS7 Translations & Operations (974/5 days)

• GSM MSC/VLR Translations (970/10 days)

GSM HLR datafill engineer

• GSM CCS7 Translations & Operations (974/5 days)

• GSM MSC/VLR Translations (970/10 days)

• GSM HLR Translations (972/5 days)

GSM subscriber service provisioning engineer

• GSM CCS7 Translations & Operations (974/5 days)

• GSM MSC/VLR Translations (970/10 days)

• GSM HLR Translations (972/5 days)

• GSM HLR-PS (935/3 days)

GSM GSM DMS Overview Student Guide GSM12

Additional GSM NSS application courses

• GSM11 Release Delta (963/2 days)

• GSM IWF (938/5 days)

GSM GSM DMS Overview Student Guide GSM12

Basic telecommunications concepts 1

The switching process, in a landline system, begins by lifting the telephone

Role of Various Nortel Switches

LONDON DMS 250 Trunks DMS PARIS

PBX :Private Branch eXchange

411-0930-001 12.03 February, 2001 Lesson 1 Introduction 1-3

The lines connect users to switches; a trunk is a transmission channel

A telephone line is how a user is connected to a switch. Typically, users are

GSM GSM DMS Overview Student Guide GSM12

Switching system evolution 1

Manual switching involved operators wearing headsets manually switching