System Overview

Siemens

System Overview

Contents
1
1.1
1.2
1.3
1.4
2
2.1
2.2
3
3.1
3.2
3.3
3.4
4
4.1
5
6

Introduction
Management Levels
The Network Element Hardware
The Principle of an Operations System
The Idea of Q3 and SNMP
Switch Commander Configurations
OS Network Configuration
OS Single Machine Configuration
Connection to the DCN
X.25 Network (NEs without MP)
TCP/IP Network (NEs with MP)
Remote Access to Switch Commander
Advanced Switch Commander Configuration
The Switch Commander for GPRS and UMTS
The Switch Commander and the GPRS Support Node (GSN)
OEM Hardware Products
Switch Commander Documentation

MN1225EU09MN_0001

3
4
6
8
10
15
16
21
23
24
26
28
32
33
34
42
43

Siemens

System Overview

MN1225EU09MN_0001

System Overview

Siemens

Introduction

Fig. 1

MN1225EU09MN_0001

Siemens

1.1

System Overview

Management Levels

Switch Commander (SC) introduces, for the first time, a homogeneous client/server
architecture based on the Windows NT operating system for realizing an operations
system (OS) to manage the GSM network elements, such as MSC/VLR, HLR/AC,
EIR and GSN.
Network management systems for operating a telecommunications network can be
hierarchically structured. The ITU-T recommendations M.3010* for the architecture of
a telecommunications management network (TMN) distinguish between four
management levels:
Business Management Level
Supports the planning and definition of the strategies of a company, which provides
services within the telecommunications network.
Service Management Level
Supports the realization of a service providers strategy, for example by providing
services and billing services provided.
Network Management Level
Provides a global view of the telecommunications network used by a service
provider. The representation of the network depends on how it is presented by the
element managers of the underlying level: the network elements can be shown
individually or are already grouped in larger groups. This level supports the central
management of all network elements.
Element Management Level
Offers a detailed view of a group of network elements for which a separate element
manager is responsible. This level assists in the monitoring, control, and coordination
of the network elements, and in the collection of data about the network elements,
i.e., the operation and maintenance of the network elements on an individual basis.
The Switch Commander system belongs to the Element Management level. Switch
Commander is therefore also known as an element manager. In the context of
network management, an exchange is known as a network element (NE), and an
operating center is known as an operations system (OS). Both are connected to a
data communications network (DCN). The DCN is used for bothway data transfer.
Switch Commander uses an X.25 data network or a TCP/IP network as DCN. The
DCN itself is not an integral component of the Switch Commander.

MN1225EU09MN_0001

Siemens

System Overview

Business Management

Service Mg.

Network Management

Element Management

Fig. 2 Management layer

MN1225EU09MN_0001

Siemens

1.2

System Overview

The Network Element Hardware

One of the reasons for the introduction of the Switch Commander system is the new
Network Element (NE) component SSNC and its derivatives.
The SSNC (Signaling System Network Control) is responsible for SS7 signaling. If
the SSNC is integrated in an MSC / EWSD exchange, it can work as a more powerful
substitute of the CCNC (Common Channel Network Control).

SSNC and its derivatives

The SSNC also is used in some slightly modified versions:
SSNC

Integrated component of MSC/EWSD exchange for SS7 signaling

STP

Signaling Transfer Point - SSNC derivative which operates in the stand

alone mode (without additional MSC / EWSD components)

GSN

A slightly modified SSNC system is also used as the central component

of the GPRS Support Node

UMSC

The NE used for the UMTS core network - UMTS MSC consists of
classical MSC components, a modified SSNC and a 36140 router for the
access to the packet switched networks

The different SSNC components

AMXE

ATM Multiplexer

LIC

Line Interface Card

MP

Main Processor

The Main Processor Operation & Maintenance

The most important Main Processor also known as "The MP" is the MP number 1
which is responsible for operation & maintenance. It is the component of the SSNC
which provides the interface to the Switch Commander system.

TIP
The Switch Commander system is very similar to the NetManager system which is
used in wireline networks.

MN1225EU09MN_0001

Siemens

System Overview

Net Element HW Structure

LTG

E1 - PCM 30

LTG

LIC

E1- PCM 30 /
STM 1 (ATM)

200Mb/s
ATM

LIC

SSNC

1
DLU

AMXE
cluster

16

LTG
LTG
SN
A/B

MP/SLT
MP/SLT

NetM / SC

Ethernet

X25

M
B
D
A

MB D

MP/SM
MP/OAM
200Mb/s ATM
AMPC
IOP:MB
CP113C

Fig. 3 Net element hardware structure

MN1225EU09MN_0001

Siemens

1.3

System Overview

The Principle of an Operations System

The biggest innovation for the operation and administration of the new NE
components is the fact that the MML (Man Machine Language) is not used any
longer for these components.
Instead of MML the SSNC and its derivatives are managed via the so called Q3
Interface.
The components to access the IP world are managed via the so called SNMP
interface. (SNMP - Simple Network Management Protocol).

MML Interface
The classical MSC / EWSD components are still handled via the MML interface. The
3 different communication forms for MML are:
l

Command

Response

spontaneous output (e.g. alarms)

Q3 Interface
At Q3 specific expressions are used for the different elements:
l

Request

Confirmation

Notification

SNMP
Simple Network Management Protocol again uses different specific expressions:

Request

Response

Trap

MN1225EU09MN_0001

Siemens

System Overview

OS

NE

Operations
System

Network
Element

Fig. 4 Principle of an operations system

MN1225EU09MN_0001

Siemens

1.4
1.4.1

System Overview

The Idea of Q3 and SNMP

The Principle

The basic idea for the principle is the same for Q3 and SNMP.
The difference comes from the organizations who specified the standards:
l

Q3 has been standardized by organizations and companies who work traditionally

at the telephone world

SNMP is the de facto standard at the IP world

Common Properties
l

Standardized, manufacturer and technology independent

usage of very few basic commands (Q3: 6, SNMP: 3)

Object Model
Because of these two properties additional information about the database structure
has to be provided to the operating system.
This information is provided in form of a so called object model.
In this context the object model is a hierarchical description of the network element's
database structure.
It is stored at the network element itself and at the operating system.
Very often the object model is also called MIB, which is short for "Management
Information Base".
The MIB is provided to the Switch Commander or NetManager system with the
installation of the so called Task Database (TaskDB): One main part of the TaskDB
is the so called Metafile, which contains all the object model information.
Managed Object Classes and Instances
The database elements of the object model are called Managed Object Classes
(MOCs). An MOC e.g. contains the description of all existing Line Interface Cards
(LICs).
One individual object in such an MOC (e.g. one specific LIC) is called Instance.

10

MN1225EU09MN_0001

Siemens

System Overview

MOC

Instance

Operating
System
(SC / NetM)

Net Element
(SSNC,
STP,...)

Fig. 5 Object model

TIP
In contrast to MML / MMI (Man Machine Interface) Q3 and SNMP are so called
Machine Machine interfaces.
This means that the commands are not sent directly to the network element when
they are entered by the operator but a certain preparation at the operating system is
done before. (For example: Retrieving of additional information from the object
model.)

MN1225EU09MN_0001

11

Siemens

1.4.2

System Overview

Q3 Requests and Scripts

The communication between the Switch Commander / NetManager and the network
element takes place in form of the so called CMISE communication.
CMISE (Common Management Information Service Elements) is the common
expression for:
l

Requests

tasks sent to the network element

Confirmations

responses from the network element

Notifications

spontaneous outputs from the network element

The problem at the direct execution of Q3 requests is that Q3 is a so called Machine

Machine interface - as already mentioned before.
This means theoretically it is possible to execute Q3 requests directly but it is very
uncomfortable for the operator because:
l

it is very cryptically

it is not intuitive

detailed knowledge on Q3 and the object model is necessary

...

SUMMARY
This means: Direct execution of Q3 requests is only done by service personal.

Ordinary operators usually don't execute Q3 requests but they work with so called Q3
scripts.
A Q3 script is built out of one or more requests and can provide a more intuitive
interface to the operator.
Q3 scripts are part of the database delivery which has to be installed at the
NetManager or Switch Commander system.

12

MN1225EU09MN_0001

Siemens

System Overview

Request

Operating
System
(NetM / SC)

Confirmation

Net Element
(MP)

Notification

CMISE
Request
Request
Request

Q3 Script (File)

Request

Fig. 6 Q3 requests and scripts

MN1225EU09MN_0001

13

Siemens

14

System Overview

MN1225EU09MN_0001

System Overview

Siemens

Switch Commander Configurations

MN1225EU09MN_0001

15

Siemens

System Overview

The Switch Commander OS can be scaled modularly from a small expansion unit up
to a large OS for operating many network elements. The basic OS configurations of
the Switch Commander are:
l

OS network configuration

OS single machine configuration

2.1

OS Network Configuration

The OS network configuration of the Switch Commander consists of a number of

computers that are connected to each other via a local area network (LAN). Special
functions of the Switch Commander are provided by specially equipped, Intel-based
Windows NT computers (servers), and used by the rest of the computers (clients).
The software is modular and distributed among the individual computers in the
network according to client/server architecture.
There are different entities in the Switch Commander environment, as:
The host types that are realized through the Switch Commander software installation
have the following tasks:
Communication server (CS)
Controls the connection to the DCN and sets up the communication relationships to
the connected GSM network elements. At least one communication server is required
in an OS; two of them are needed to establish redundancy.
File server (FS)
Used for the central storage of large data volumes. In particular, the communication
database is stored of the file server, and the NE specific data on the communications
servers are replicated on the file server, so that in the event of a communication
server failure, its functions can be taken over by other servers (warm stand-by).
Each OS has exactly one file server.
Primary domain controller (PDC)
Holds the common information needed by all domain computers.
Each domain has exactly one PDC. It is highly recommended to install no SC
software on the PDC, i.e. the PDC should not be part of the OS.

16

MN1225EU09MN_0001

Siemens

System Overview

Backup domain controller (BDC)

Handles backup of data on the primary domain controller. A BDC is not required in a
domain; but it is recommended to configure at least one BDC. The computer which
acts as BDC can be part of the OS. Both the PDC and the BDC have a kind of load
sharing serving all other domain members the necessary information.
Craft terminal (CT)
Used as workplace for the operation and maintenance of the network elements.

Abbreviation

Function

FS

File Server

The server where the SC database is

stored (ORACLE). Among other
things the SC database contains
information about authorization, NE
addressing or object models.

CS

Communication Server

Provides the communication interface

to the network elements

AS

Application Server

The seperate server where the

additional applications like
"Autopatch" are running

PDC

Primary Domain Controller

Hosts the user and user groups

database.
Mandatory entity but not a part of the
SC system

BDC

Backup Domain Controller

Backup System of the PDC

Optional entity, not a part of the SC
system

CT

Craft Terminal

Operation Terminal

Fig. 7 Different SC host types

MN1225EU09MN_0001

17

Siemens

2.1.1

System Overview

Multi Server Configuration

In a multi server configuration every logical server actually is running on its own
physical platform. The specific number of the individual servers depends on the
number of connected network elements, the number of installed craft terminals and
on the number of used applications.
The SC configured in a multi server configuration gives a flexible scalability for
administration, operating and maintaining a large number of network elements.
About 40 to 60 CTs can be installed. The administration of about 70 NEs is possible.

DCN

PDC

FS

AS

CS

CT

CT

CT

Fig. 8 OS network configuration

18

MN1225EU09MN_0001

Siemens

System Overview

2.1.2

Single Server Configuration

The SC configured in a single server configuration integrates all the SC functions of

PDC, file server (FS), communication server (CS), application server (AS) and craft
terminal (CT) on one single physical server.
Maximally 8 CTs can be installed. The administration of about 20 NEs is possible.

DCN

PDC / FS / AS / CS

CT

CT

CT

Fig. 9 SC single server configuration

MN1225EU09MN_0001

19

Siemens

2.1.3

System Overview

Double Server Configuration

The SC configured in a double server configuration provides a redundancy for the

integrated file servers. During normal operation the primary FS (FS1) is active. Max.
16 CTs can be installed. In case of a crash of the primary FS the backup FS (FS2)
takes over.
For optional applications separate CS and AS are recommended. The administration
of about 40 NEs is possible.

DCN

PDC / FS / AS / CS
1

PDC / FS / AS / CS
2

CT

CT

CT

Fig. 10 SC double server configuration

TIP
Unfortunately the redundancy feature will not be released within SCR9.1

20

MN1225EU09MN_0001

Siemens

System Overview

2.2

OS Single Machine Configuration

The Switch Commander can also be configured to consist of a single computer,

which integrates all the OS functions of communication server, file server and craft
terminal. The smallest possible configuration is sometimes also known as craft
terminal (CT).

DCN

FS / CS / AS / CT

Fig. 11 OS single machine configuration

MN1225EU09MN_0001

21

Siemens

22

System Overview

MN1225EU09MN_0001

System Overview

Siemens

Connection to the DCN

MN1225EU09MN_0001

23

Siemens

3.1

System Overview

X.25 Network (NEs without MP)

The connection from the communication server to network elements without an

SSNC or any derivative is established with an X.25 network.
In this case the connection is done to the CP which just has got an X.25 interface.
The X.25 network handles the routing of packets to their destinations. To implement
the connection, every communication server is equipped with up to four X.25 cards
(Eicon Card). Each X.25 card provides two interfaces which means you can have up
to 8 individual X.25 interfaces per communication server. Several network elements
can be operated via the X.25 network connection.
With X.25 DCN connection the CP of a network element can be accessed for dialog
via the print and dialog protocol (MML interface) and for file transfer via FTAM and
FTNEA.

24

MN1225EU09MN_0001

Siemens

System Overview

CP
CP

CP
CP

CP
CP

X.25

PDC

FS

AS

CS

CT

CT

CT

Fig. 12 X.25 network (NEs without MP)

MN1225EU09MN_0001

25

Siemens

3.2

System Overview

TCP/IP Network (NEs with MP)

If the network element contains an SSNC or one of its derivatives, the used data
communication network is not an X.25 network but a TCP/IP based network.
The TCP/IP connection from the communication server to the SSNC is done to the
main processor number 1 (the MP for O&M or just "The MP").
For redundancy the MP provides two 10BaseT Ethernet interfaces - at the two MP
sides.
The communication to the coordination processor (CP) of a network element is done
via the main processor (MP).
With the TCP/IP connection the MP of an network element can be accessed for
dialog via the Q3 interface and for file transfer via FTP; the CP can be accessed for
dialog via the print and dialog protocol (MML interface) and for file transfer via FTAM.
(MML and FTAM data is forwarded transparently to the CP by the MP.)

TIP
Theoretically it was possible to have a TCP/IP connection to the MP and additionally
an X.25 connection to the CP.

26

MN1225EU09MN_0001

Siemens

System Overview

CP
CP

MP
MP
MP
MP

MP
MP
ATM Bridge

TCP/IP

PDC

FS

AS

CS

CT

CT

CT

Fig. 13 TCP/IP network

MN1225EU09MN_0001

27

Siemens

3.3

System Overview

Remote Access to Switch Commander

Users working on computers outside the Switch Commander OS (other WinNT

Domain or other operating system) can access the graphical user interface of the
Switch Commander. The remote access to the Switch Commander OS will be
realized by installing, administering and using the OEM software product CITRIX
Metaframe.
After installing the Metaframe software on one or more OS computers, these
computers act as Metaframe servers. To achieve the remote access to the Switch
Commander OS, the craft terminal (CT) software package should be installed on the
Metaframe server.
Then, a number of different Metaframe clients can remotely access the Switch
Commander applications via the Metaframe server Metaframe client users can
access the Switch Commander applications directly or via a WWW browser.
The Metaframe client software enables users of Microsoft Windows products to
access existing and future Windows programs over the public Internet and corporate
Intranets without downloading the software. In short, Metaframe receives Windows
graphic application programming interface (API) calls and displays the information on
the screen, so that you can run the program very effectively over a slow link such as
a modem line.

28

MN1225EU09MN_0001

Siemens

System Overview

Metaframe
Client

Metaframe
Client

PLMN/PSTN

DCN

Metaframe
Client

RAS

PDC

FS

AS

CS

Metaframe
Server /
CT

CT

CT

Fig. 14 Accessing the OS remote from metaframe clients

MN1225EU09MN_0001

29

Siemens

System Overview

Metaframe Server and Clients

Metaframe is an application which takes place between the operating system
(Windows NT 4.0) and all applications running a system.
Every application which likes to interact with the graphical user interface (GUI) is
using an interface to do so. The other way round, if the operating system likes to
interact with an application there is an standardized interface, too.
The Metaframe software takes these messages and forwards them to a client, all
user input taken at the client is then forwarded to the Metaframe Server and so
forwarded to the application.
The application - the Switch Commander - is executed at the Metaframe Server.
Therefore every Client contacting the Metaframe Server will increase the load of the
Metaframe Server.

TIP
Per Metaframe Server you can have up to 15 clients (license restriction).

30

MN1225EU09MN_0001

Siemens

System Overview

Application Output

Metaframe Client

Switch Commander
Application

Metaframe Server

Windows NT API

Windows NT API

User Input
Metaframe
Client

Metaframe Server
/CT

Fig. 15 Metaframe function

MN1225EU09MN_0001

31

Siemens

System Overview

3.4

Advanced Switch Commander Configuration

Due the Client Server architecture of the Switch Commander application the system
is open to implement some more server functionality adding some systems.
Some examples for additional applications are:
l

Network Configuration Management NCM

AutoPatch

SPOTS

Citrix Metaframe

Legato Backup Server

These systems need not be individual physical servers but are at least logical ones.

DCN
PSTN /
ISDN

RAS /
BDC

FS 1

PDC

FS 2

CS 1

AS
Backup

AS
Autopatch

CS 2

Metaframe

CT

CT

CT

Fig. 16 Switch commander configuration example

32

MN1225EU09MN_0001

System Overview

Siemens

The Switch Commander for GPRS and

UMTS

MN1225EU09MN_0001

33

Siemens

4.1

4.1.1

System Overview

The Switch Commander and the

GPRS Support Node (GSN)
Devices of the GPRS Support Node (GSN) Release 1

As already mentioned above, the Switch Commander is used to operate the General
Packet Radio System (GPRS) Support Node (GSN). In release 1 the system consists
of four different devices. All devices together make up the GSN.
l

FR/ATM Switch Newbridge 36170 (new name: Alcatel 74170)

Siemens SSNC, GSN core system

Kentrox DSU/CSU

Cisco Router 4500

The Newbridge 170 (Alcatel 74170) is used to build up the connection to the Base
Station Subsystem (BSS), esp. to the Packet Control Unit (PCU) in the Base Station
Controller (BSC).
The Siemens SSNC (an adapted version) provides the real GSN functionality, like
subscriber handling, billing, packet switching and so on.
The Kentrox DSU/CSU adapts the ATM interface protocol of the SSNC to the ATM
interface protocol used by the router
The Cisco Router builds up the connection to the Internet Service Provider (ISP),
therefore to the Internet.
Per ISP one individual Kentrox - Cisco pair is necessary. One GSN (one 36170 and
one SSNC) can contain up to eight of these pairs.

34

MN1225EU09MN_0001

Siemens

System Overview

GSN
Release 1

SSNC
Newbridge 36170 /
Alcatel 74170
Kentrox DSU/CSU
Converter

BSS

Router
Cisco 4500

ISP

Fig. 17 GSN configuration

MN1225EU09MN_0001

35

Siemens

4.1.2

System Overview

Operation and Maintenance of the GPRS Support Node

(GSN)

The Operation and Maintenance of the GSN can be divided into two parts:
First the so-called OEM-Devices used to connect the SSNC to the environment. The
Switch Commander using the Simple Network Management Protocol (SNMP)
supervises these devices, only.
HP Openview Network Node Manager
The SNMP interface for the alarm surveillance is not provided by the SC software
itself but by an additional software product, the HP Openview Network Node
Manager.
The configuration of the OEM devices is either done locally or via a telnet session
(Application OEM device manager).or by parameter files transferred to the
components via file transfer (ftp).
SSNC
The SSNC is the central part of the GSN and therefore it is not enough just to have
alarm surveillance only.
Therefor we are using the standardized management protocol Q3. All commands, all
alarms and notifications are sent as Q3 messages between the SSNC and the Switch
Commander.

36

MN1225EU09MN_0001

Siemens

System Overview

GSN
Release 1

SSNC
Newbridge 36170 /
Alcatel 74170
Kentrox DSU/CSU
Converter

Router
Cisco 4500

Q3
SNMP (Traps)
Switch Commander (Q3)
HP Openview (SNMP)

Fig. 18 Access of the switch commander platform to the GSN

MN1225EU09MN_0001

37

Siemens

4.1.3

System Overview

GSN Release 2

The two main modifications for GPRS support node release 2 are the following:
Seabridge 36140
At GPRS release 2 the Newbridge 36170 and the Kentrox - Cisco pair is replaced by
the Seabridge 140 Router.

SGSN and GGSN

The functionality of the GPRS Support Node is separated in the Serving and the
Gateway functionality.
One Gateway GSN can support several Serving GSNs.

38

MN1225EU09MN_0001

Siemens

System Overview

GSN Release 2
SGSN

SSNC
Seabridge
36140

BSS

GGSN
36140

ISP

Fig. 19 GSN Release 2

MN1225EU09MN_0001

39

Siemens

System Overview

4.1.4

UMSC

The UMTS MSC integrates components which are administrated via the MML, via the
Q3 and via the SNMP interface.

Interfaces
The UMSC provides different specific interfaces to the various networks:

40

Gn

The Gn interface (ATM) is the interface between the 36140 which is part of
the SGSN functionality and the one which provides the GGSN functionality.

Gi

The interface to the Internet. This interface can be realized with different
transport technologies like 100BaseT, ATM, FR,...

Gb

The Gb interface is based on FR technology and provides the packet

connection to the GPRS based radio network. GPRS technology is used
when the subscriber is not located in an UMTS cell.

Gr

The Gr Interface leads to the HLRI

Iu

The Iu interface is an ATM STM1 interface leading to the UTRAN part of the
UMTS network. It is used for voice, packet date and SS7 signaling

MN1225EU09MN_0001

Siemens

System Overview

U-MSC

Gateway MSC

HLR Innovation
UTRAN

Gr
LTG

GSM /
GPRS
Gb

Iu

36140
(SGSN)

LTG

LTG

Gn
SN
SSNC

LTG

36140
(GGSN)

CP

LTG

Gi
MB

MML

Internet

Q3

SNMP

Fig. 20 UMTS MSC

The SSNC together with one 36140 make up the SGSN functionality.
The other 36140 makes up the GGSN functionality.

MN1225EU09MN_0001

41

Siemens

System Overview

OEM Hardware Products

The following OEM hardware (with the exception of LAN components) is qualified for
use in Switch Commander:

42

Personal Computer by Siemens and Primergy especially equipped to fulfill the

function as part of the Switch Commander OS configuration with: processor type,
RAM capacity, hard disc capacity, floppy drive, and optional CD-ROM drive (for
software installation), DAT drive (as backup device), and LAN card (optional for
OS single machine configuration).

X.25 card from Eicon

LAN card needed for every computer in an OS configuration

Uninterruptible power supply (UPS) by American Power Conversion for bridging

brief power outages. For secure emergency operation, at least the communication
server and the file server with their connected devices (e.g., external hard disks)
plus the LAN component between the two computers must be connected to the
UPS. In the case of longer outages, the UPS enable a controlled shutdown of the
connected hosts.

MN1225EU09MN_0001

System Overview

Siemens

Switch Commander Documentation

The Switch Commander documentation consists of the following parts:

Switch Commander manuals document the Switch Commander system and provide
the information necessary for its operation.
These are:
l

System Description addresses anyone who wants to get an overview of the

structure and functional scope of the Switch Commander.

User Manual addresses users who operate and maintain network elements and
gives an outline of the procedures of the applications for operation. The details of
operation are provided in the help system of the applications.

Administration Manual addresses administrators of the OS and describes the

tasks, which must be performed in order to guarantee trouble-free and secure
operation of the network elements.

Installation Manual addresses the administrator and those who install the Switch
Commander and describes how to install the product.

Manuals for the additional applications like "Autopatch" or "Q3 Upload

Scheduler".

Abbreviations contains all the abbreviations used in the Switch Commander

manuals.

Glossary contains important Switch Commander terms.

MN1225EU09MN_0001

43

Siemens

44

System Overview

MN1225EU09MN_0001