OSS Description

1555-58/AOM 201 02 Uen C

Introduction to GSM OSS

Copyright
Ericsson AB 2002 - All Rights Reserved
Disclaimer
The contents of this document are subject to revision without notice due to continued
progress in methodology, design and manufacturing.
Ericsson shall have no liability for any errors or damages of any kind resulting from the
use of this document.
Contents
1
1.1

Introduction
OSS Documentation Structure

2
2.1
2.2

GSM Overview
The Ericsson GSM System
Operations Support System (OSS)

3
3.1
3.2
3.3
3.4
3.5
3.6

GSM OSS Overview

Main Concept
Radio Network Management
AXE10 Management
Non AXE10 Management
General Operation and Maintenance Functions (OSS Platform)
Tools

4
4.1

Radio Network Management

Radio Network Management Applications

5
5.1

AXE10 Management
AXE10 Management Applications

6
6.1

Non AXE10 Management

Non AXE10 Management Applications

7
7.1
7.2

General Operation and Maintenance Functions

Command Handling Applications
File Handling

7.3
7.4
7.5
7.6
7.7

External Access Manager (EAM)

The Information Model Handler (IMH)
OSS Client Solution (OCS)
Security Concept
High Availability (HA)

8
8.1
8.2

Tools
Tools Applications
Adminserver

9
9.1
9.2
9.3

Customer Documentation
The OSS Documentation Strategy
User Documents
Customer Library Structure

10

Glossary

1 Introduction
The increasing number of digital switching systems must operate parallel to "old"
analogue networks. For example, the introduction of cellular radio has stressed the need
of a management system to solve problems in this area. When a public switched
telephone network and a digital ISDN work side-by-side, other complications arise,
which put pressure on the network management staff.
Within the field of public land mobile networks, the support system is called OSS
(Operations Support System).
Ericsson's OSS offers an improved series of tools as an answer to all these matters.
This document is intended for users of GSM OSS R9.1.

1.1 OSS Documentation Structure

The OSS Customer Library includes the following types of user documents:

Descriptions
Functional Specifications
User Guides
Procedure Manuals
System Administrator's Guides
Function Verifications
Installation Documents

A description of the OSS Customer Library is found in Chapter 9 .

2 GSM Overview
2.1 The Ericsson GSM System
2.1.1 General
The Ericsson GSM System is a mobile communications system built around the latest
technology of Ericsson's AXE switching system. This means that all the well-proven
features and services implemented in AXE over the years are standard in the Ericsson
GSM System. It also means that the Ericsson GSM System will take full advantage of
future development of AXE.

2.1.2 Switching System and Base Station System

The system architecture of the Ericsson GSM System is shown in Figure 1 .
The Ericsson GSM System is basically divided into the Switching System (SS) and the
Base Station System (BSS).
Each of these contains a number of functional units, where all system functions are
realized. The functional units are implemented in various equipment (hardware).
The Switching System (SS) includes the following functional units:

Mobile services Switching Centre (MSC)

Home Location Register (HLR)
Authentication Centre (AUC)
Visitor Location Register (VLR)
Equipment Identity Register (EIR)

The Base Station System (BSS) includes:

Base Station Controller (BSC)

Base Transceiver Station (BTS)

The Packet-Switched System includes:

GPRS Support Nodes (GSN)

Mobile Positioning Centre (MPC)

The system is realized as a network of neighboring radio cells, together providing

complete coverage of the Service Area.
All these units, mentioned above, are involved in carrying speech connections between a
Mobile Station (MS) and, for example, a subscriber in the Public Switched Telephone
Network (PSTN).

Figure 1 Overview of the Ericsson GSM System

2.1.3 Mobile services Switching Centre (MSC)

The Mobile services Switching Centre (MSC) serves a number of Base Station
Controllers. MSC controls calls to and from the Public Switched Telephone Network
(PSTN) and the Public Land Mobile Network (PLMN).

2.1.4 Home Location Register (HLR)

A number of database are needed in the network to keep track of the MS. The most
important of these database is the Home Location Register (HLR). When someone buys a

subscription from one of the network operators, he will be registered in the HLR of that
network operator. The HLR contains subscriber information, such as supplementary
services and authentication parameters. Furthermore there will be information about the
location of the MS, that is in which MSC area the MS resides for the moment.
This information changes as the MS moves around. The MS will send location
information (through the MSC/VLR) to its HLR, thus providing means to receive a call.

2.1.5 Authentication Centre (AUC)

A unit called Authentication Centre (AUC) is connected to the HLR. The function of
AUC is to provide the HLR with authentication parameters and ciphering keys, both used
for security reasons.

2.1.6 Visitor Location Register (VLR)

The Visitor Location Register (VLR) is a database containing information about all the
MSs currently located in the MSC area. As soon as an MS roams into a new MSC area,
the VLR connected to that MSC will request data about the MS from the HLR.
At the same time the HLR will be informed of which MSC area the MS resides in. If,
later on, the MS wants to make a call, the VLR will have the information needed for the
call setup without having to ask the HLR each time. The VLR can be seen as a distributed
HLR. The VLR will also contain more exact information about the location of the MS in
the MSC area.

2.1.7 Equipment Identity Register (EIR)

There is a difference between the physical equipment and the subscription. The MS is a
piece of equipment, which can be installed in a vehicle or is hand-portable.
There is a small unit called the Subscriber Identity Module (SIM) which is a separate
physical entity, for example, an IC-card, also called a smart card. SIM and the mobile
equipment together make up the MS. Without SIM, the MS cannot get access to the
network, except for emergency traffic.
Since the SIM-card is connected to the subscription and not to the MS, the subscriber can
use another MS as well as his own. This presents a problem with stolen MSs, since it is
no use barring the subscription if the equipment is stolen.
A database containing the unique hardware identity of the equipment is needed. This
database is called the Equipment Identity Register (EIR). The EIR is connected to the
MSC over a signalling link. This enables the MSC to check the validity of the equipment.

2.1.8 Base Station Controller (BSC)

The Base Station Controller (BSC) controls a group of Base Transceiver Stations (BTS).
BSC also controls such functions as handover and power control.

2.1.9 Base Transceiver Station (BTS)

Each cell has a Base Transceiver Station (BTS) operating on a set of radio channels.
These are different from the channels used in neighboring cells to avoid interference.

2.1.10 GPRS Support Nodes (GSN)

General Packet Radio Service (GPRS) is an additional service to the Global System for
Mobile communications (GSM) . It provides a basic solution for Internet Protocol (IP)
communication between Mobile Stations (MS) and the Internet or corporate Local Area
Networks (LAN).
The GSN consists of the Serving GPRS Support Node (SGSN) and the Gateway GPRS
Support Node (GGSN). The SGSN provides mobility for the MSs. The GGSN is the
gateway to external IP networks

2.1.11 Mobile Positioning Centre (MPC)

The Mobile Positioning Centre (MPC) is a gateway that enables applications to access
location information in a simple way, independent of the location technology used.

2.1.12 Operation and Maintenance Centre (OMC), Network Management

Centre (NMC)
Each network element has built-in functions for operation and maintenance, that is
functions for supervising and reporting the status.
These functions can be centralized to a single location, an OMC (Operation and
Maintenance Centre), which is handled by the OSS (Operations Support System).
The applications in the OSS offer a user-friendly graphical user interface.
The AXE10 Management provides the network operator with the necessary software to
build OMC (Operation and Maintenance Centres) and NMC (Network Management
Centres). Figure 2 shows the OMC/NMC concept. The OMC represents the physical
implementation of an Operations Support System handling the element level. The NMC
represents the physical implementation of an operation support system handling the
network level.

Figure 2 The OMC/NMC Concept

2.2 Operations Support System (OSS)

The object of the GSM OSS is to offer the customer cost-effective support for
centralized, regional, and local operational and maintenance activities required for a
cellular network. The main purposes of the GSM OSS are to provide a network overview
and support the maintenance activities of different operation and maintenance
organizations.

3 GSM OSS Overview

3.1 Main Concept
Ericsson's Operations Support System OSS is based on Ericsson's broad market
experience and unique telecom and mobile radio know-how. OSS offers an open and
flexible system based on hardware and software standards.
The system architecture of OSS is based on internationally accepted standards, and
employs products available on the world market. Its operating system is UNIX. Some
applications for Performance Management are also available as PC clients.

The concept matches CCITT's Telecommunications Management Network (TMN),

regarding both the architecture and the standardization. The system can, in addition to
being used for Ericsson's digital switching system AXE, also accommodate equipment
from other suppliers.
The communication with the different elements in the network uses X.25 or TCP/IP
standards.

Figure 3 The OSS Open System Architecture

OSS is designed to offer support to the network management and provide solutions to all
the management tasks in mobile networks. The OSS concept consists of a number of
products to be used by a network operator or service provider.
Flexibility is one of the main features of OSS. It is achieved through having a standardsbased computing and communications platform as the base. Figure 4 illustrates this in
simple terms.
Part of OSS is the Radio Network Management, which is used to manage the cellular
mobile telephone system.
Another part of OSS is the AXE10 Management (which is used to communicate with the
exchange). The AXE10 Management contains for example Performance Measurement,
Fault Management and AXE10 Software Management.
The non AXE10 Management contains support for non AXE10 Network Elements,
typically alarm handling functions.
The General Operation and Maintenance Functions (OSS Platform) contains the basic
operating software of the system, which is based on industry standards and
telecommunication-specific functions, for example, routines for handling alarm messages
from network elements.

Self-contained, modular programs are also included in the platform, which allow it to
communicate with each type of equipment in the network.
Tools contain applications which make the daily operation of the network easier.

Figure 4 The OSS Architecture

The basic principles of the OSS system architecture are founded on a network model
concept; the physical network elements (for example, AXE exchanges) are represented as
a network model, which is mapped into a database. The network model consists of data
describing the different network elements in an object-oriented way. Consequently, the
database contains a picture of the data loaded into the exchanges. The database also
contains a definition of the network configuration, which means that a graphic
representation of the network is always at hand.
The user performs different tasks in the network through the Network Model by using
graphical interfaces. The Network Model, after having been updated, executes these tasks
in the physical network.

Figure 5 Example of the OSS Network Model

The network model/database concept is the basis of the overall flexibility of the system.
Operating companies can design their own applications creating advanced operations
support functions, which can handle different types of network elements in a common
way.
The open end properties of OSS enable an operating company to:

Communicate with all network elements in the network

Send/handle messages and commands to remote systems
Store data in a database
Communicate with the system by means of menu-driven user interfaces
Continuously develop the system by means of computer-aided software
engineering and object-oriented programming

This means that users can configure the system, make adaptations, add applications, add
third party software, and interface other systems.

3.2 Radio Network Management

The main features of the Radio Network Management are:

Central administration to optimize the use of skilled personnel

Supervision of network operation for planning purposes
Network performance measurement
Traffic recording and analysis of measurement and event data
Cellular network configuration

OSS maximizes service quality in cellular networks by providing a centralized facility for
network configuration, administration, performance measurement, and maintenance of
the network components.

This is achieved through the following different applications:

Basic OSS-Node Administration (BOA)

Cellular Network Administration (CNA)
Cellular Network Administration Interface (CNAI)
CNA / Move BSC
Radio Network Recording Functions (RNR)
Network Statistics, Analyser (NWSA)
Network Statistics, Statistical Measurement Initiator and Administration (SMIA)
Network Statistics, Statistical Gateway (SGw)
Network Statistics, Statistical Data Mart (SDM)
Network Statistics, Performance Alarms (PSA)
Real-Time Performance Monitoring (R-PMO)
Subnetwork Access Interface (SNAI)
BTS Configuration Management (BCM)
BTS Hardware Management (BHW)
BTS Alarm Management (BAM)
Frequency Allocation Support (FAS)
Frequency Optimization Expert (FOX)
Neighbouring Cell Support (NCS)
Neighbouring Cell List Optimization Expert (NOX)
Measurement Result Recording (MRR)
Traffic Estimation Tool (TET)

For more information on Radio Network Management, see Chapter 4 .

3.3 AXE10 Management

The AXE10 Management provides functions to manage all AXE10 based Network
Elements.
This is done by:

Software Management Organizer (SMO)

Network Inventory Organizer (NIO)
Fault Management (FM)
AST Manager
AXE Number Analysis Manager (NAM)

For more information on AXE10 Management, see Chapter 5 .

3.4 Non AXE10 Management

Support for non AXE10 Network Elements, typically alarm handling functions, is
provided by the following applications:

Multivendor Support (MVS)

Sema AUC/EIR Alarm Handling (AEH)
MXE Alarm and Command Interface (MAC)
DXX Alarm Interface (DAI)
Specified Alarm Interface (SPAI) (no longer sold, only for upgrade)
SPAI Verification Program (VERP) (no longer sold, only for upgrade)
Q3 Access
Basic Network Surveillance Interface (BNSI)
SNMP Supervision Manager Toolkit (SNMP SMT)
GSN Configuration Manager (GSN-CM)

For more information on Non AXE10 Management, see Chapter 6 .

3.5 General Operation and Maintenance Functions

(OSS Platform)
This platform is a multi-computer system based on open industry standards, for example,
CAE, OSI, ISO/CCITT and SQL. It incorporates hardware, basic application software,
I/O functions and an operating system. The platform concept can be seen as divided into
two parts, one run-time part and one development part.
The run-time part consists of subsystems - such as the standard applications package handling data communication, database functions, user interface, and operation and
maintenance.
The development part contains system development functions, that is, computer-aided
software engineering through which the operating company can enhance and modify an
OSS system.
The OSS application is based on the Management Framework defined by Open Systems
Interconnection (OSI) principles for the Telecommunications Management Network
(TMN). OSS functions and applications are categorized in a number of functional areas
according to these standards or recommendations.
The OSS platform consists of the following applications:

Command Handling
WinFiol
File Handling
External Access Manager (EAM)
Information Model Handler
OSS Client Solution (OCS)

Figure 6 OSS Applications Supported by the Platform

For more information on General Operation and Maintenance Functions, see Chapter 7

3.6 Tools
The following applications are provided to make the daily operation of the network
easier:

Cellular Network Activity Manager (CNAM)

Operations Procedure Support (OPS)
Active Library Explorer (ALEX)
Geographical and Logical Network Information Presentation (GNIP)
OMC Flashboard (OFB)

For more information on Tools, see Chapter 8 .

4 Radio Network Management

Cellular telecommunication is one of the fastest-growing and most demanded
telecommunications applications ever. Today, it represents a large percentage of all new
telephone subscriptions all around the world, and its spectacular growth continues.
In the long-term perspective, cellular radio, using digital technology, will turn into the
universal way of communication for virtually everybody.

By means of cellular networks offering economical and reliable high-capacity mobile

communication services, network operators can meet demanding customers'
requirements.
Due to the quick implementation, the high growth rate, and the frequent use, cellular
radio has manifested itself as very profitable to network operators.
A broad outline of a GSM system, is illustrated in the figure below.

Figure 7 The Fundamentals of a GSM System

The system is built by a number of radio base transceiver stations communicating with
the mobile telephones. The traffic through the radio base transceiver stations is controlled
by a Base Station Controller (BSC). The BSCs are controlled by a switching system
consisting of a number of exchanges (MSCs). The system is supervised, supported and

maintained by OSS. OSS provides total management and operations support for cellular
communications.

4.1 Radio Network Management Applications

Figure 8 Radio Network Management areas

The Radio Network Management consists of the following applications:

4.1.1 Basic OSS-Node Administration (BOA)

BOA consists of two parts. The first part NAD (Network Administration), is used to
handle network elements and other managed objects common to several applications in
OSS. It can create, change and delete objects in the Information Model as well as set up
heartbeat surveillance for them. It is built upon IMH (Information Model Handler) in the
OSS platform.
The second part, RAH (Radio Alarm Handling), contains functions to handle radiorelated alarms from the network elements as defined in NAD. It includes functions to
receive, process and store alarms.

4.1.2 Cellular Network Administration (CNA)

CNA manages cell and cell-related data. The application database contains an internal
representation of the actual Network in the Valid Area.
This information can be adjusted when the Network has been changed. All changes in the
Network are performed in a Planned Area in which the user can create, modify and delete
objects like cells, sites etc. The changes are planned off-line without affecting the real
Network.
Before the Valid Area and the Network are updated, it is possible to perform Consistency
Checks of the changes made in order to avoid implementing errors in the Network.
The operator can edit cell parameters in a table mode, in a menu mode and in a
geographical mode. The latter displays cell shapes and cell parameters on top of a map.

4.1.3 Cellular Network Administration Interface (CNAI)

CNAI serves as an import and export interface to the CNA application. It provides easy
exchange of information between the OSS and an external system.
For example, CNAI could be used to transfer a file of cell parameter data from the
external cell planning application EET, into the OSS.

4.1.4 CNA / Move BSC

Cellular mobile radio networks are currently growing very fast, and the operators
therefore continuously need to make changes in the network configuration. Cells are
moved between Base Station Controllers (BSCs), and a BSC may be moved between two
Mobile Services Switching Centres (MSCs).
After moving a BSC in the network, which has to be done outside the OSS system, the
operators must configure the cells in the affected MSCs to make the Network consistent
again.
The CNA Move BSC application is designed to facilitate the cell configuration part of the
operation. The "move_bsc" program moves a BSC from one MSC to another MSC within
the OSS, and also, in combination with the Update function in the CNA application,
provides a way of configuring the MSCs after the move operation.

4.1.5 Radio Network Recording Functions (RNR)

The application unit RNR consists of Performance Management - Traffic Recording
(PMR). PMR provides a tool for detailed analysis of radio network performance. The
observed performance is related to traffic behaviour, such as setup of connections, handovers, and release of connections.
In essence, PMR can be seen as a debugging and tuning tool in the performance
management process.
PMR includes functions for:

Initiating recordings in the network element (NE)

mobile traffic recordings (MTR)
cell traffic recordings (CTR)
channel event recordings (CER)
Processing the recorded information
Presenting data in a number of reports and graphs
Importing recording files stored in the UNIX file system
Exporting recording data to file in tabular form

4.1.6 Network Statistics

The Network Statistics consists of the following integrated applications:

Network Statistics, Analyser

Networks Statistics, Statistical Measurement Initiation and Administration
(SMIA)
Network Statistics, Statistical Gateway (SGw)
Network Statistics, Statistical Data Mart (SDM)
Network Statistics, Performance Alarms

The Network Statistics helps the operator with the following important tasks:

Planning and dimensioning the network

Monitoring and optimizing the network, regarding network performance or
improvement of the quality of service
Maintaining and improving the quality in the network
Operating the network cost-effectively

4.1.6.1 Network Statistics, Analyser

The NWS, Analyser provides the user with a number of pre-defined reports that supports
the operator in analysing the behaviour and performance of the network. The reports are
based on data collected from the network and stored in the SDM Application database
(ASD/BSD/CSD).
The reports are divided into groups:

Overview Reports, used to get a quick overview of the network performance

Planning Reports, used for dimensioning the network
Handover Reports, used to get information about the handover performance in the
network
Dropped Calls Reports, used to get information about where calls are dropped and
the reason for the drops
Management Reports, used to get a quick overview of the whole network in an
easily understandable and non technical way from the managers perspective
Speech Quality Supervision Reports, used to locate problem areas in the network
caused by bad cell planning or low radio network quality

The reports are created and presented using the BusinessObjects user module.
BusinessObjects is a software tool to integrate querying, reporting and analysis. It enables
the user to create reports to find answers to questions on a business situation. With
BusinessObjects it is possible to:

Create reports that contain data from the corporate database, without knowledge
of SQL. It is possible to combine data from several data sources.

Perform multidimensional analysis on the data in the reports, using slice-and-dice

mode and drill-mode.
Organize, format and print the reports.
Refresh report data, and export it to other applications.
Schedule reports to be refreshed, printed, sent to other users or posted as HTML
documents on web servers.

When using the pre-defined reports a user has the possibility to, for example:

Add or remove columns

Change order of the columns
Create graphs of tabular information and vice versa
Sort tables and graphs
Add or change thresholds and conditions that marks certain data

4.1.6.2 Networks Statistics, Statistical Measurement Initiation and Administration

(SMIA)
The SMIA application is used to administer, create, modify and delete statistical
measurements in different AXE-10 type network elements supported by the GSM OSS.
The application will support the statistical measurement functions for all Object Types in
STS and the following measurements in OMS:

Traffic Measurement on Routes (TRAR)

Traffic Measurement on Traffic Types (TRART)
Traffic Dispersion Measurement (TRDIP)

The SMIA provides Graphical User Interface (GUI) for the administration of the STS and
the OMS measurements. The GUI runs in a Java enabled Web browser.
4.1.6.3 Network Statistics, Statistical Gateway (SGw)
The Statistical Gateway makes the collection and handling of statistical data simple and
efficient. The Performance Report Systems are provided with one uniform and stable
standard interface for all statistical data collection.
This gives a less complex network for statistical data collection and cuts costs for
integration of new network elements, new data formats or post processing systems. The
Statistical Gateway collects statistical data files automatically and on-line from various
types of network elements. The data files can be processed in the SGw before delivery to
their final destination.
Using the Graphical User Interface provided for the SGw it is simple for the operator to
supervise the parsing process in SGw. The Statistical Gateway supports a simultaneous
access to different network elements from different product lines, releases and vendors.
This provides the performance report systems with one stable, flexible, and uniform

interface for statistical data collection, even when the network consists of several
different systems and of equipment from different vendors.
4.1.6.4 Network Statistics, Statistical Data Mart (SDM)
SDM is used to store raw data and processed data. Daily operation, network planning and
optimization in a radio network require data as a basis for decisions. To make this data
available to the operator, performance measurements are made in the network elements.
SDM consists of two database for storage of performance data; the Basic Statistical
Database (BSD) and the Complementary Statistical Database (CSD).
The Basic Statistical Database (BSD) is structured for fast retrieval of performance data,
which can be presented in reports.
The Complementary Statistical Database (CSD) is used to store user-specific data.
The Administrative Database (ASD) is used to store parameters to control activities in
SDM. ASD also contains information about object types to be loaded into BSD.
4.1.6.5 Network Statistics, Performance Alarms
The Performance Statistical Alarms are defined for a set of pre-defined performance
indicators. Performance alarms are used to find out traffic related problems within a
network which cannot initiate the process of generating alarms. For example, "Sleeping
cell" , "Congestion" , "Dropped cell rate" .
A Performance Alarm is built up by:

Selecting a performance indicator

Setting threshold or floating threshold window and the valid event times for
different thresholds
Selecting measurement object(s) to apply to the performance alarm
Select event(s) for the performance alarm to trigger

Performance statistical alarms will produce real alarms to the Fault Manager system.
These alarms can either be set on thresholds or on floating values, such as +/- 10% with
valid time periods, or a combination of these values. The time period give the user the
possibility to exclude time periods when the performance alarm is active. The floating
performance alarm is based on history information in the database so the values in the
performance alarm can follow the normal traffic profile.
4.1.6.6 Real-Time Performance Monitoring (R-PMO)

R-PMO provides the user with a presentation of 12 quality and traffic monitors. These are
presented in real-time with down to minute resolution. The value for the user is the
instant feedback to network changes or problems investigated.
R-PMO presents real-time performance indicators that give the user:

A visualized network
Instant feedback of network changes gives a better understanding of the current
radio network behaviour, and enables accurate planning.

Fast reaction to problems and trouble-shooting

Instant indications of quality problems or congestion, makes it possible to solve
the problems quickly. R-PMO also helps while trouble-shooting, thanks to
hightime resolution and easily correlated data.

The implementation of real-time data from the Base Station System (BSS) affects both
the Base Station Controller (BSC) and the OSS. The BSC implementation of the feature
enables reporting of certain BSC events, as they occur, and the OSS implementation of
the feature handels the flow of events and displays it to the user. The R-PMO application
presents monitors regarding quality and traffic level. This is collected in two table
reports, Traffic report and Quality report, and each monitor is presented in sliding graphs.
The table report provides an overview of the included cells. For each cell the current
values of the monitors are visible. The user can also choose to view information or data
for specific cells and monitors in a sliding graph window, where the data for the past hour
(the last 60 minutes) is presented.
4.1.6.7 Subnetwork Access Interface (SNAI)
The SNAI application gathers statistics from subnetworks and sends this to the NMS.

4.1.7 Base Station Management Family

4.1.7.1 Base Station Configuration Management (BCM)
The BCM application provides the network operator with an application to handle the
BTS configuration. It combines functionality for the configuration of BTS parameters
with support for introduction and modification of BTS.
By using the Planning Wizard the user gets support in changing BTS configurations. It
makes sure that the user creates complete configurations and ensures consistency for the
data planned with the Planning Wizard.

The effort to change the state of base stations can be reduced by using the state changing
functions in BCM. The functions work on different Managed Objects (MO) levels and
include commands and scripts for blocking/deblocking as well as for in service/out of
service operations.
4.1.7.2 Base Station Hardware Management (BHW)
The BHW application provides the operator with a hardware register of the installed BTS
Replacement Units (RU).
By using the BHW application, the user can easily identify RUs, their revisions and serial
numbers installed on a site.
4.1.7.3 Base Station Alarm Management (BAM)
The BAM application provides the user with a functionality to restrict the amount of
alarms and to define which kind of alarms to be presented. This feature enables the user
to filter alarms according to certain criteria, which depend on the current situation and
makes it easier to concentrate on important alarms. BAM offers the possibility of viewing
the complete suppressed alarm information.
Furthermore, BAM provides the user with a more efficient fault-finding process by
presenting interpreted fault and status information on the BTS managed objects.
External Alarm Objects for RBS can be configured as well as re-configured. The user can
retrieve as well as reset the BSCs Error Log for the Managed Objects (MOs).

4.1.8 Radio Network Optimization Family

4.1.8.1 Frequency Allocation Support (FAS)
The FAS application is a tool that supports frequency planning in order to minimize the
interference level in the radio network.
The user can order FAS to perform recordings of the uplink interference level on up to
150 frequencies in at least 2000 cells handled by one OSS. After the recording is
completed, the result values are reported to OSS where they are processed and presented
in reports and in a map. The result can also be exported.
The information from FAS can be used as a complement to the frequency planning tool
where FAS also supports updating of a Planned Area in CNA with frequency changes.
Employment areas are:

To improve the frequency plan due to quality problems (optimization)

To find frequencies in order to add or expand a cell (planning)

To supervise the interference levels in a certain area (supervision)

To verify improvement after a frequency change (verification)

FAS also supports the evaluation of new frequency allocations by supporting presentation
of quality-related traffic statistics and certain statistical reports. The user can then
compare recordings, in a comparison report, and statistical reports from before and after a
frequency reallocation.
4.1.8.2 Frequency Optimization Expert (FOX)
The FAS application can be sold and installed on two different functional levels:

Report Level (FAS)

The application supports recording definitions and scheduling, report handling
and presentation, update of planned area, and creating and exporting ICDM.

Expert Level (FOX)

FOX Recommendation, where FOX recordings support recommendations of
frequency reallocations of the network that the user has to confirm.
FOX Automatic, where FOX recordings support evaluation and automatically
updates the frequency reallocations in the network.

An Expert level installation includes two different recording types besides the FAS
recording: Recommendation type and Automatic type. For each type, the interference
measurements and the evaluation of data run repeatedly according to the recording
definition. During the time, the user will be notified by a status change in the list when
modification of the network is recommended or has been made. In FOX
Recommendation type, each suggested change in the network must be approved or
rejected by the user before it is implemented, whereas in Automatic type, all changes
found are also implemented. In addition to suggested changes, all recorded data can also
be presented in reports.
The following functions are included in FOX:

Proposing Frequency Changes in a Change Order Recommendation Report

Executing Frequency Changes. The changes are listed in a Change Order
Evaluation Report
Reallocation Log
Reallocation Search which creates a Change Order Recommendation Report, to
which it is possible to make modifications, if the recording has been started as a
Recommendation type

Reallocation Execution, which executes the reallocations in the Change Order

Recommendation Report, if the recording has been started as a Recommendation
or Automatic type

4.1.8.3 Neighbouring Cell Support (NCS)

The NCS application is a tool that helps the user to specify adequate neighbouring cell
relations for each cell in the radio network. Thus, the handover decisions will be more
reliable and correct, which leads to increased speech quality and less dropped calls.
The user can order NCS to perform recordings on up to 150 Broadcast Control Channel
(BCCH) frequencies in at least 2000 cells handled by one OSS. After the recording is
completed, the result values are reported to OSS where they are processed and presented
in reports and in a map. The result can also be exported.
The information from NCS can be used as a basis for the neighbouring cell relation
planning where NCS also supports updating of a Planned Area in CNA with new
neighbouring cell relations.
Employment areas are:

To find missing neighbouring cell relations (optimization)

To find neighbouring cell relations to a new cell (planning)

4.1.8.4 Neighbouring Cell List Optimization Expert (NOX)

The NOX application is an addition to NCS enhanced with more intelligence.
It is possible to run NOX in an automatic mode. NOX then not only measures the signal
strengths on the extended BA list's frequencies and evaluates the result, but also updates
the network with the proposed changes (via CNA).
It is also possible to run NOX in a recommendation mode, when NOX measures the
signal strengths on the extended BA list's frequencies, evaluates the result and presents
the proposed changes to the user. The user can then decide to update the network with the
changes, alter them or discard them.
4.1.8.5 Measurement Result Recording (MRR)
When running a GSM network, radio network supervision and tuning are essential
activities in order to obtain high quality.
The MRR application supports these activities by collecting and analyzing radio network
statistics based on measurement results containing different radio characteristics
continuously measured by mobile stations and base stations.

By using a map, an overview of the network quality on cell level will be easily available
to the user. A decrease in the network quality can be detected at an early stage, allowing
the user to take immediate action and do the necessary measurements in order to solve
the problem as fast as possible. The same data can be viewed in reports and the result can
be exported.
Employment areas are:

To analyze radio characteristics for problematic cells (optimization)

To supervise radio characteristics in a certain area (supervision)
To verify improvement after a change (verification)

4.1.8.6 Traffic Estimation Tool (TET)

TET is a tool for finding the most suitable location for a hot spot cell. It makes it possible
to measure how much traffic the future cell will take, and how much it will off-load the
surrounding cells.
After the recording is completed, the result values are reported to OSS where they are
processed and presented in reports. The result can also be exported. Employment areas
are:

To find the most suitable location for a hot spot cell (planning)
To give indications on dimensioning, output power and suitable neighbouring
cells for the future cell (planning)

5 AXE10 Management
The AXE10 Management contains a set of functions which enables the network operator
to manage a switched network in a centralized and efficient manner. It primarily supports
NEs (Network Elements) of the AXE types but can also be adapted, by using various
alarm adaptation functions, to support equipment of non Ericsson manufacture.

5.1 AXE10 Management Applications

5.1.1 Software Management Organizer (SMO)
Software Management Organizer (SMO) is a common application for remote software
handling activities towards different types of network elements.
SMO provides a process oriented working environment for the operator, and uniform
software handling for different network element types. With the graphical user interface

of SMO, the operator may supervise parallel activation jobs towards multiple network
elements from a single terminal.
SMO provides the following functions for the operator:

Software inventory, including compare between network elements.

Software distribution from OSS to network elements.
Remote software upgrade.
Monitor upgrade jobs towards multiple network elements in parallel.
Backup administration, including transfer of backups to OSS.
Automatic Correction Deployment from Ericsson.
Uniform handling of different network element types.

5.1.2 Network Inventory Organizer (NIO)

The NIO functionality (hardware inventory) is also available from the SMO GUI. This
functionality may be used to perform hardware to software compliance checks during
upgrade.
NIO provides the following functions for the operator:

Collection of hardware data from the network.

Export of hardware data to external inventory management systems.

5.1.3 Fault Management Family

5.1.3.1 Basic FM Applications
Fault Management is the all-inclusive name of the different alarm-handling functions
(Alarm Handling). The figure below illustrates the primary features of Alarm Handling.
Events reported from NEs (Network Elements), as well as datalink faults, external alarms
and OSS internal errors are processed and distributed to the following end-user services:

Alarm Viewer
Alarm Status Viewer

The user can view the alarms with the Alarm Viewer, which consists of three applications
with graphical user interfaces: the Alarm List Viewer, the Alarm Log Browser and the
Alarm Status Matrix. Commands for searching alarms are also available.
With Alarm List Viewer, the user can view details of the current alarms, and also handle
these alarms.
With the Alarm Log Browser, the user can search for specific alarms in the alarm log and
view details and statistics of these alarms.

With the Alarm Status Matrix, the user can overview the current alarm situation in the
network in a compressed view.
The Alarm Status Viewer presents the current alarm in the Geographical and Logical
Network Information Presentation (GNIP) framework. This provides both maps showing
each supervised object at it's geographical position and views showing the logical relation
between supervised objects.
The Alarm Viewer can also be displayed by a Windows NT workstation, but the main
process is still executed in the Unix server.
The routing of alarm messages to different output devices is also provided.
An important feature of Alarm Handling is the capability of other Operations Support
Systems to subscribe to specific alarms handled by OSS.

Figure 9 Alarm Handling

Alarm Handling has features for:

Mapping of AXE alarms to a normalized alarm-record format

Indication of equipment within the NE
Surveillance of the AXE heartbeat signal
Surveillance of the datalinks used for communication with the NEs

When recovery has been achieved from a heartbeat or datalink failure, it is possible to
perform an alarm synchronization by updating the Alarm List through a new collection of
alarm lists from the affected NEs.

Alarm Handling uses the Network Model in OSS, in which each NE and its related alarm
status are regarded as a managed object with associated attributes. For practical reasons
in facilitating network surveillance, it is possible to form logical groups of NEs into socalled MGs (Management Groups).
Alarm Handling is designed according to the ANSI draft standards, which means that
NEs following applicable parts of these standards can be supervised.
For AXE this means that the alarm classes are converted into five perceived severity
values: Critical, Major, Minor, Warning, and Indeterminate. The AXE alarm categories
are converted to probable cause values, for example, Processor, Subscriber lines, Power
etc.
It should be noted that no alarm information is lost regardless of whether there has been a
conversion of alarms before they are presented to the user. The complete original alarm
information can always be found in the Alarm List and the Alarm Log.
It is possible to define criteria for sending alarms to one of the following output devices;
printers, mail, file, or a workstation console window.
5.1.3.2 External Alarm Handling
External Alarm Handling has two purposes: to collect and present external alarms (for
example, environmental or fire alarms) at the OSS site and to present the alarm situation
on external devices, such as an alarm panel or alarm bell. It is also possible to provide
alarm signals to other alarm-collecting systems. The following features are included:

An interface for connecting external alarm sensors to OSS and transforming of

external alarms into OSS alarms. This means that external alarms may be
presented to the user in the same manner as other alarms received in OSS.
Output of the current alarm situation in OSS over an electric interface to other
alarm- collecting systems.

5.1.3.3 Fault Management Expert (FMX)

FMX is an expert system with support for alarm filtering, alarm correlation and automatic
invocation of actions in response to alarms.
FMX comprises functionality to embody expert knowledge within Fault Management in
order to provide users with a clear and accurate understanding of the status of the
managed network.
FMX is divided into one runtime part (FMXR) and one delvelopment part (FMXD).
FMX provides functions to:

Receive relevant alarms from a managed network by using Fault Management.

Perform sophisticated real-time alarm correlation and filtering by using a high
level graphical editor. The rules support automatic invoking of actions and further
analysis of the response.
Divide the definitions made (for instance rules) into different FMX Modules.
Such modules can be installed in other TMOS systems.

5.1.4 AST Manager

AST Manager is a software system devoted to the management of the duplication
functionality implemented in the AST-DR devices located in the AXE 10 exchanges.
The purpose of AST Manager is as follows:

Providing the operator with a tool to manage the recordable phrases stored in the
announcement terminals.
Updating the announcement terminals with new speech files distributed from AST
Manager.
Duplicating already existent announcement from one announcement terminal to
other locations in the network.
Importing into the AST Manager speech files contained in other applications
(APSS support tools) performing the necessary data conversions.

5.1.5 AXE Number Analysis Manager

The design, implementation and maintenance of B-number Analysis data are complex
and time-consuming tasks that must be frequently performed into today's rapidly growing
networks.
The AXE Number Analysis Manager provides a sophisticated, task-oriented graphical
interface to optimize the administration of B-number Analysis, Pre-analysis and Routing
Case tables. The Consistency Check feature and automatic generation of MML
commands support error-free data generation. The Manager can also be used to trace call
setup faults.
The AXE Number Analysis Manager offers the following benefits:

Improved network performance. Fewer unsuccessful call attempts will improve

revenue.
Higher end-user satisfaction. Fewer errors in the B-number tables will reduce
unsuccessful call attempts.
Greater utilization of technical staff. The Manager significantly enhances
efficiency in handling analysis tables.
Faster response to customer complaints. The Trace Call Setup function may be
used to rapidly identify and remedy complaints raised by the end-user.

Faster introduction of new network services. Shorter time for updates to

numbering plans and DT will reduce Time To Customer.
Reduced in-house development. The operator can spend the time and cost for
maintaining own tools on other activities in the core business.

6 Non AXE10 Management

6.1 Non AXE10 Management Applications
Support for non AXE10 Network Elements, typically alarm-handling functions, is
provided by the following applications.

6.1.1 Multivendor Support (MVS)

This application provides the ability to read text files, to transform the text to TMOS
alarm records, and to send the records to the Fault Management for further treatment.
MVS can maintain the size of the file to which alarms are written to make sure that there
is always space available in the file system for new alarms.
MVS provides the following functions:

Alarms are received by reading from regular files or named pipes

Alarms are transformed into TMOS alarm records, and alarm records are
forwarded to Fault Management
The size of the file for incoming alarms can be supervised
The list of known alarms can be updated in runtime without shutdown or restart
The NEs are indicated by a logical view in GNIP

6.1.2 Sema AUC/EIR Alarm Handling (AEH)

This application contains functions to adapt AUC/EIR alarms to OSS Fault Management
format. It translates alarms received from AUC/EIR in MIP (Management Interface
Protocol) format into the format expected by Fault Management.

6.1.3 MXE Alarm and Command Interface (MAC)

The MXE Alarm and Command Handling (MAC) provides alarm integration in OSS and
access to the MXE from OSS for Operating and Maintenance purposes.
MXE is a multimedia messaging network element. It provides services based on voice,
text, data, and fax.

MAC is a product which contains two main parts:

Alarm handling
Remote login from UNIX

The alarm handling supports the following functions:

Alarm reception
Alarm forwarding to FM
Alarm conversion
Alarm synchronization
Order response
Heartbeat supervision

The main function of MXE Alarm Adaptation is to interpret the spontaneous printouts,
which are classified as events, alarm printouts, and alarm cease printouts from the MXE
network element, into TMOS Alarm Format. The MXE Alarm Adaptation function also
supports heartbeat supervision and synchronization of the MXE.

6.1.4 DXX Alarm Interface (DAI)

The DAI application integrates alarm management of the DXX nodes into OSS so that
alarm handling of the entire cellular network can be managed from the same set of OSS
applications.

6.1.5 Specified Alarm Interface (SPAI)

The SPAI application integrates alarm management of the External System and its
equipment into OSS so that alarm handling of the entire cellular network can be managed
from the same set of OSS applications. SPAI is no longer sold, but customers who have
bought it will get an updated version.

6.1.6 SPAI Verification Program (VERP)

The purpose of VERP is to facilitate the verification of the customer-adapted interface
between an External System and OSS, without having to connect the two systems. The
effort to build up a test environment for the communication interface of the External
System can be minimized in this way. VERP is no longer sold, but customers who have
bought it will get an updated version.

6.1.7 Q3 Access
Q3 is a standard TMN interface covering both protocol and data.
6.1.7.1 Q3 Alarm Surveillance Manager

The Q3 Alarm Surveillance Manager consists of two application units:

Q3 Alarm Adaptation Unit

Event Forwarding Discriminator (EFD) Manager

The Q3 Alarm Adaptation Unit provides standard TMOS Fault Management with the
necessary complements to perform alarm surveillance of network elements of the Q3 type
(according to Q.821). Q3 network elements are referred to as Managed Elements (ME).
The application unit also supports heartbeat supervision and synchronization of the ME.
The purpose of the EFD Manager is to provide management of EFDs in MEs according
to Q.821. The application unit facilitates setting up and changing destinations for alarm
reporting, and switching alarm reporting on or off.
6.1.7.2 Q3 Alarm Surveillance Agent
The Q3 Alarm Surveillance Agent offers a Q3 interface to TMOS. This interface supports
alarm surveillance in conformance to ITU-T standard Q.821.
The application forwards alarms to external operations systems (OSs). These alarms are
either received by TMOS from the managed elements, or generated internally by TMOS.
In addition the application supports control of alarm reporting by the OSs, and gives
access to the alarm log, through the Q3 interface.

6.1.8 Basic Network Surveillance Interface (BNSI) Manager

The purpose of BNSI Manager is to collect and present alarms from different types of
Network Elements (NE) via their Element Managers (EM). BNSI Manager uses a
common alarm surveillance interface, which must be supported by the EMs and the NEs
which are connected directly to the FM system. Using an interface protocol makes it
easier to integrate new types of EMs and NEs into the Fault Management system.
This allows an operator to supervise all NEs in a network from one screen or work place,
where the alarms are presented in a uniform way.
BNSI Manager supports GSN nodes for GPRS.

6.1.9 Basic Network Surveillance Interface (BNSI) Agent

The purpose of BNSI Agent is to provide a communication link between a TMOS system
serving as Element Manager in a network supervised by a Network Surveillance system.
Using BNSI Agent, a TMOS system serving as an Element Manager can send alarms to,
and receive instructions from, a supervising Network Surveillance (NS) system. The
BNSI Agent in the EM communicates with a BNSI manager in the NS system. The NS
system can be a TMOS system, or a BNSI compliant NS system from another vendor

than Ericsson. BNSI Agent is implemented as a set of commands using a command line
interface. Under normal operation, these commands are run remotely by a BNSI manager.

6.1.10 SNMP Supervision Manager Toolkit (SNMP SMT)

SNMP Supervision Manager Toolkit is a generic alarm manager conforming to the
Simple Network Management Protocol (SNMP).
The SNMP SMT provides a framework to facilitate the connection and alarm supervision
of various SNMP-based equipment. The toolkit provides the tools needed to develop
customer adaptations according to a specific operator's need or according to a specific
event-generating source.
If no adaptations are made, a default behavior is provided by the supervision manager.

6.1.11 GSN Configuration Manager (GSN-CM)

General Packet Radio Service (GPRS) is an additional service to the Global System for
Mobile communications (GSM) . It provides a basic solution for Internet Protocol (IP)
communication between Mobile Stations (MS) and the Internet or corporate Local Area
Networks (LAN).
The GSN consists of the Serving GPRS Support Node (SGSN) and the Gateway GPRS
Support Node (GGSN). The SGSN provides mobility for the MSs. The GGSN is the
gateway to external IP networks
The GSN Configuration Manager is used for both long-term configuration planning as
well as day-to-day changes of the GSN network.

7 General Operation and Maintenance

Functions
7.1 Command Handling Applications
7.1.1 Command Handling (CHA)
Network elements are designed to be controlled by commands sent one by one from a
terminal in real time. For more intricate operations or when the same command must be
sent to a number of NEs, this becomes a tedious and time-consuming task. The Command
Handling provides tools for combining commands into long strings and storing them as
command files. These files can be retrieved and sent to specified NEs by the creator or by

other users, if given the proper authority. Command files can be set to be automatically
invoked at a given date and time, for example, outside office hours or at a given weekday.
All commands issued are stored in the Command Log and can be retrieved and redisplayed, re-edited, and re-issued.
7.1.1.1 Command Files
There are two types of command files:

The "Command file" which has limited functions and can be created by any user
The "System command file" which can include more sophisticated statements and
can be created by the system administrator for execution by authorized users

In addition to the usual commands included in the basic file function, the system
command file may also contain procedural control statements, wait statements, and errorhandling functions.
7.1.1.2 Command and Response Log
All commands that are sent to an NE and all received responses and spontaneous reports
are logged in the command and response log.
CHA provides a function for searching for and retrieving information from the command
and response log. The following search criteria can be used:

NE name
Host name
User ID
NE command (part of a command can also be used)
Application information (for example command file name)
Search string for text, matching responses or spontaneous reports
Start and stop date and time

7.1.2 WinFIOL
WinFIOL (File transfer and on-line program for Windows) is a man-machine
communications program, designed for operation and maintenance, installation, testing of
customer exchanges.
WinFIOL includes a powerful editor for command files and log files, a script language
and a macro language. WinFIOL also includes the functions:

Schedule for command and script files

Support for dangerous commands
Several logging functions for commands and printouts

7.2 File Handling

The File handling (FHA) Server and Client provides the user with functions to perform
file transfers, scheduling, administration, management of file stores, and subscription to
files received from external systems.

Figure 10 File Transfer and Management

The functions apply both to the internal OSS File Store and to the files stored in external
systems.

7.2.1 File Transfer

Three cases apply for file transfer between OSS and the external systems:

OSS or the external system can send a file spontaneously

OSS or the external system can request a file to be sent
OSS or the external system can send notification that a file is ready to be
transferred

The user can specify immediate transfer, delayed transfer, or periodic transfer of the files.
Scheduled transfer can also be ordered.
Note:
There is no support for APG40 in FHA. Instead a procedure manual is provided
for ftp usage.

7.2.2 File Administration and Management

Each file stored in OSS is assigned a storage retention time, which will
normally be a default value. The default storage retention time is
configurable. It is possible to override the retention time manually.
Files that have exceeded their retention time are automatically deleted.
Management functions include create, copy, list, import, change of file
attributes and others.

7.2.3 File Subscription

The user can set up subscriptions so that external Operations Support
Systems automatically receive certain files when they become available in
OSS.

7.3 External Access Manager (EAM)

A central part of the OSS Platform is the External Access. The purpose of
the External Access is to give a unified interface to external systems, NEs,
and Operating Systems.
The External Access is NE/OS-type independent and includes a Command
Log and an Event Log.

7.3.1 AXE 10 Handler

From an application's point of view, the AXE 10 is an External System
(ES).
The AXE 10 handlers are External Access Handler Text (EHT), External
Access Handler MTP (EHM) and External Access Handler TCP/IP (EHIP).
EHT provides X.29 access by means of command sending and response
reception. Functions for event logging and command and response logging
are also provided. EHT is essentially to be used with AXE 10 but can be
used to transfer messages to any compatible destination that uses the X.29
protocol.
EHM provides MTP (Message Transfer Protocol) access.
EHIP provides TCP/IP access for APG40.

7.4 The Information Model Handler (IMH)

The IMH contains the Network Model and is the heart of the higher-level
applications.
The concept by which it works is that an application defines a model of the
network resources it manages, that is, the set of MOs (Managed Objects),
and provides a framework to implement an MO view.

7.5 OSS Client Solution (OCS)

The OSS Client Solution is the client feature which replaces the OSS Xterminal feature especially for remote access. A UNIX Application Server
(UAS) (or multiple UNIX Application Servers for many simultaneous
clients) replaces the former X-terminal Server and instead of using Xterminals or PCs emulating X-terminal, Citrix MetaFrame will be used in
both Application Servers and UNIX or PC clients.
This will reduce the need for bandwidth for Java based OSS applications,
which will gain better performance and response times compared to Xterminals and PCs emulating X-terminals.
By using OCS, the need for large investments in LAN/WAN network
bandwidth and UNIX workstations is reduced. Furthermore, the security for
remote clients is essentially increased compared to using X-terminals.
However, to secure investments already done in X-terminals or X-terminal
emulators, the X11 protocol is also supported in the UNIX Application
Server for local X-terminals.
When using the OCS feature, all OSS client application software are
executed in the UNIX Application Server(s) except for the Performance
Measurement clients using Business Objects which will require an
additional Windows Application Server (WAS).
The WAS should be configured as a Windows Terminal Server. The WAS
has the Business Objects products, for example BO Reports Module, BO
Designer and BO Supervisor installed on it. There is also Citrix MetaFrame
installed on the WAS and the ICA client on the UAS is configured to
connect to it.
In a configuration with only OSS Unix workstations (for example no UAS),
access to the WAS is done through a locally installed ICA client in the OSS
Unix workstation. Access to WAS from a remote client is always done via
the UAS.

In the physical client hardware, that is a PC or UNIX workstation, the

MetaFrame ICA protocol software is the only required software to run OSS.
These clients are referred to as "thin" clients.
Note:
The traditional "thick" client based on a UNIX workstation is supported in
parallel to OCS.
The Broascast Agent Server (BAS) is a Windows 2000 Server
machine hosting the Broadcast Agent (BCA). The BAS must
be a separate machine that is not the WAS or the Windows
2000 workstation.

Figure 11 OSS Client Solution (OCS)

7.6 Security Concept

Fundamentals for security in GSM OSS R9.1 are:

Secure node, which means that the system is located

within a locked building.
MetaFrame concept. The main way to connect to GSM
OSS through a firewall is using the ICA protocol,
which is a part of the MetaFrame concept.

The X25 protocol is considered secure and is used for

MML communication with IOG11/20.
GSM OSS communicates with APG40 via AP
commands. Secure Shell (SSH) and Virtual Private
Network (VPN) is used to protect AP commands sent
towards APG40 via TCP/IP. SSH is included in OSS.
VPN is not included in OSS. It is a recommendation to
use VPN.
External communication on the NMS level via TCP/IP
will be secured via a firewall and VPN.

7.7 High Availability (HA)

GSM OSS High Availability consists of the Cluster Solution
and the Replication Solution. These solutions offer:

Decreased down time in production, both planned and

unplanned.
Increased phyical security, distance between the nodes
Balanced load sharing
Upgrade with very limited down time

7.7.1 High Availability Cluster Solution

The Cluster configuration consists of two identical servers.
Both nodes are configured for load sharing which means that
both servers are working during normal operation and if one
server goes down, the other will automatically in 1-4 minutes
take over defined services with reduced capacity.
The distance between the servers can be up to 10 kilometers
using long distance fibre interfaces/cables and fibre channel
disks.

7.7.2 High Availability Replication Solution

The Replication Solutions hardware configuration consists of
two similar servers. Both servers have separate storage per
node which is synchronized over a LAN/WAN communication
link, Replication Link.
The primary node is taking care of normal production. The
secondary node is during normal operating conditions building
up a copy of the volumes of the primary node via the
replication function.

The disaster fail over between the nodes is done manually and
will take about 10 minutes.

8 Tools
8.1 Tools Applications
The following applications are provided to make the daily
operation of the network easier.

8.1.1 Cellular Network Activity Manager (CNAM)

CNAM contains functions to manage background activities
initiated in cellular applications. The user can view
information on scheduled and ongoing activities as well as
abort activities.

8.1.2 Operations Procedure Support (OPS)

OPS provides support for development and runtime control of
MML command files. Also other activities related to the user's
work, such as UNIX file handling, may be performed by
means of control features that can be embedded in the MML
command files. In this way the application provides support
for automation and control of the network operator's
processes.
The application unit includes the following functions:

Command File Developer

CHA Command File Language

The Command File Developer is an editor and debugger for

Command Files using CHA Command File Language
supported by the TMOS system.
The CHA Command File Language is a programming
language that allows advanced command files to be created.

8.1.3 Active Library Explorer (ALEX)

The Active Library Explorer allows a user to browse

document database with a standard web browser, for example
Netscape Navigator. The document database can reside either
on a web server, in which case the documents are accessible
from all workstations connected to the intranet, or on a local
hard disk or CD-ROM in which case no network connections
are needed at all.
The Active Library Explorer makes complete document
libraries electronically available. When the database are
produced, documents are converted to HTML format including graphics and pictures. Documents in unusual
formats are converted to PDF (Portable Document Format)
and can be viewed with the web browser using the Adobe
Acrobat Reader plug-in.

8.1.4 Geographical and Logical Network

Information Presentation (GNIP)
GNIP is a common geographical and logical presentation tool
which can be utilized by several applications. It provides the
possibility to show network information from several
applications in one user interface simultaneously.
Alarm Status Viewer (ASV) is an information gateway from
Fault Management (FM) to GNIP. Geographical Cell
Configuration (GCC) is an information gateway from CNA to
GNIP.
It is also possible to present recording results from FAS, NCS
and MRR on the GNIP map.
The network information is displayed by means of dynamic
real time symbols on top of maps or in logical views. GNIP
(together with ASV, GCC, FAS, NCS, MRR) provides a clear
and accurate view of the managed network.

8.1.5 OMC Flashboard (OFB)

OFB provides a graphical user interface for monitoring the use
of certain OSS resources and tracking the active OSS
applications.
Some OSS features are heavy resource consumers. This, in
combination with a large number of concurrent users, effects
the performance of the OSS system.

OFB gives the operator the possibility to better use the

available resources in order to get maximum performance.

8.2 Adminserver
The purpose of the Adminserver is to provide general UNIX
services on a central server. Especially in case the OSS master
server is down (for example software upgrade) the
Adminserver is able to provide services to the workstations
and other connected equipment.
The following services are included in the Adminserver.

Domain Name Service (DNS)

NIS Slave Server
Print Service
Mail Service

9 Customer Documentation
This chapter describes the OSS documentation strategy and
the contents of the Customer Library. It explains the principles
on which the strategy is built, and contains information about
how the manual set for each OSS function is designed and
structured. Also included are the audience definitions on
which the document definitions are based.

9.1 The OSS Documentation Strategy

Two groups of people need information about the OSS. One
group consists of users, people who will spend many hours
each week working with the system. The other consists of
dependants, people whose work in some way is involved with
the system but who do not interact with it themselves.
The information needs of these two groups vary not only in
degree but in type. The information need of users is greater.
They obtain information about the system primarily through
their workstations, but they usually also need some
information about the structure and internal workings of the
system.

For some groups of semi-skilled users, this is not true. Their

interest begins and ends with the windows in front of them,
and their tasks include such things as batch entry of subscriber
data, handling directory enquiry queries, and so forth.
While managers, administrators and others need to be aware
of the OSS and its capabilities, they do not need to know how
to use it. Skilled users need at least some information to be
able to decide how to use the system, but they also need to
know how to operate the controls presented in the user
interface.
The System Administrator's tasks do not fit in either of these
categories, as a rule. The System Administrator's greatest
interest is in the hardware and the operating system that
support the OSS, and in the interfaces between the OSS and
these supporting elements.
There are also some repetitive jobs (routine maintenance)
which must be performed by the System Administrator, as
well as complex tasks (installation and configuration) which
are carried out only infrequently. Procedural descriptions,
supported by manual pages (UNIX command "man" ) in the
system, help to ensure that no important details are forgotten.

9.2 User Documents

9.2.1 Document Description
9.2.1.1 Introduction to OSS
The Introduction to OSS is a general document and is not
specific to a function. It contains a description of the system
and its interfaces with other systems. The main purpose of the
introduction is to explain what the system does and describe
how it functions without undue technical detail. It is not a
complete description of the OSS, but rather provides the
general and background information any reader needs to be
able to understand the more specific user documents.
9.2.1.2 Functional Specification/Function Description
The Functional Specification/Function Description is an
introduction with general and context information about a
particular application. It explains the purpose and operation of
an Application Unit, and specifies functionality and

characteristics that the Application Unit supplies. It also

describes why the functions are needed and their connections
of the functionality to other functions.
9.2.1.3 Functional Verification
The Functional Verification contains instructions on how the
customer can perform acceptance tests of the system. This
involves verifying that all functions are delivered according to
the contract.
9.2.1.4 Installation Instruction
The Installation Instruction contains instructions on how to
install the software. There is one general Initial Installation
document which covers most of the OSS applications.
9.2.1.5 System Administrator's Guide
The System Administrator's Guide includes reference
information and procedures for installation, routine
maintenance, corrective maintenance and any other
information required by OSS system personnel.
9.2.1.6 User Guide
The User Guide gives the part of the user information that is
specific to one OSS function. It contains detailed descriptions
and illustrations of how to use each window or window group.
9.2.1.7 Procedure Manual
The Procedure Manual describes the applications' most
important workflows and ensures that absolutely complete
information is presented when appropriate (for example, in
training of staff).
9.2.1.8 Programmer's Guide
The Programmer's Guide contains information on the
application interfaces (API) needed for developing new
functions or for altering of existing functions.
9.2.1.9 Help Text

In addition to the manuals and guides described above, the

Help Text is available to users where applicable. This is onscreen information consisting of short explanations and hints
presented directly on the screen. Help texts are available for
windows and the items in the windows.

9.2.2 User Categories

The following staff categories have been identified:

Senior Manager
Line Manager
System Administrator
Skilled Technician
Semi-skilled Technician
Programmer
anybody

The OSS user documentation is directed towards all

employees of a cellular network company who operate an OSS
system.

Figure 12 Information Access Path

9.3 Customer Library Structure

The structure of the Customer Library (and the documents
therein) is determined by two main considerations:

The audience
The purpose

9.3.1 The Customer Library

The Customer Library consists of an electronic document
database (ALEX). The Active Library Explorer allows a user
to browse the ALEX database with a standard web browser,
for example Netscape Navigator. When the database is
produced, documents are converted to HTML format including graphics and pictures. Documents in unusual
formats are converted to PDF (Portable Document Format)
and can be viewed inside the web browser using the Adobe
Acrobat Reader plug-in.
The whole GSM Library now uses a new generic structure for
Customer Product Information. The following subsections are
used in the OSS Customer Library.
9.3.1.1 Description
The Reference Manual is placed under the heading
Description. The Reference Manual contains product
description documents such as the Functional
Specifications/Function Descriptions and the Introduction to
OSS.
9.3.1.2 Installation
The Installation Manual is placed under the heading
Installation and it contains Installation Instructions and
Configuration Directions.
9.3.1.3 Verification
The Function Verification Manual is placed under the heading
Verification and it contains Function Verifications.
9.3.1.4 Operation and Maintenance Information

The Systems Administrator's Manual and the User Manual are

placed under the heading Operation and Maintenance
Information.
The Systems Administrator's Manual contains information for
the system administration, and instructions for hardware and
software maintenance. These documents (System
Administrator's Guides) include information on administrative
routines, routine maintenance, action on alarms, system start,
hardware handling etc.
The User Manual contains User Guides and Procedure
Manuals, the directive documents for normal system
operations.
9.3.1.5 Interface
The Programmer's Manual is placed under the heading
Interface and it contains information on application interfaces
(APIs) needed for the development of new, or modification of
existing functions.

10 Glossary
AEH
Sema AUC/EIR Alarm Handling
AI
Application Information
ALEX
Active Library Explorer
ANSI
American National Standards Institute
ASD
Administrative Statistical Database
AST
Announcement Service Terminal

ASV
Alarm Status Viewer
AUC
Authentication Centre
AXE
An identification code used for a line of Ericsson exchanges
AXS-OPS
AXS-OPS Integration
BAM
BTS Alarm Management
BAS
Broadcast Agent Server
BCA
Broadcast Agent
BCCH
Broadcast Control Channel
BCM
BTS Configuration Management
BHW
BTS Hardware Management
BOA
Basic OSS-Node Administration
BSC
Base Station Controller
BSD
Basic Statistical Database
BSM
Base Station Management

BSS
Base Station System
BTS
Base Transceiver Station
CCITT
International Telegraph & Telephone Consultative Committee
CER
Channel Event Recording
CF
Central Function
CHA
Command Handling
CISE
Command Interface Service Element
CNA
Cellular Network Administration
CNAI
Cellular Network Administration Interface
CNAM
Cellular Network Activity Management
COD
Command Description
CSD
Customer Statistical Database
CTR
Cell Traffic Recording
DAI
DXX Alarm Interface

EFD
Event Forwarding Discriminator
EHIP
External Access Handler TCP/IP
EHM
External Access Handler MTP
EHT
External Access Handler Text
EIR
Equipment Identity Register
FAS
Frequency Allocation Support
FMX
Fault Management Expert
FOX
Frequency Optimization Expert
GCC
Geographical Cell Configuration
GGSN
Gateway GPRS Support Node
GNIP
Geographical and Logical Network Information Presentation
GPRS
General Packet Radio Service
GSM
Global System for Mobile Communication
GSN
GPRS Support Node

GSN-CM
GSN Configuration Manager
GUI
Graphical User Interface
HA
High Availability
HLR
Home Location Register
IMH
Information Model Handler
ISO
International Standards Organization
ITU-T
International Telecommunication Union, Telecommunication
Standardization Sector.
MAC
MXE Alarm and Command Interface
ME
Managed Element
MG
Management Group
MIP
Management Interface Protocol
MML
Man Machine Language, according to the CCITT.
MO
Managed Object
MPC

Mobile Positioning Centre

MRR
Measurement Result Recording
MS
Mobile Station
MSC
Mobile Services Switching Centre
MTP
Message Transfer Protocol
MTR
Mobile Traffic Recording
MVS
Multivendor Support
MXE
Computer platform implementing an MC
NAM
AXE Number Analysis Manager
NCS
Neighbouring Cell Support
NE
Network Element
NMC
Network Management Centre
NMS
Network Management System
NOX
Neighbouring Cell List Optimization Expert
NWS

Network Statistics
OCS
OSS Client Solution
OFB
OMC Flashboard
O&M
Operation and Maintenance
OMC
Operation & Maintenance Centre
OPI
Operational Instruction
OPS
Operations Procedure Support
OSI
Open System Interconnection
OSS
Operations Support System
PAD
Packet Assembler and Disassembler
PLMN
Public Land Mobile Network
PMR
Performance Management, traffic Recording
POD
Printout Descriptions
PSTN
Public Switched Telephone Network
Q.821

Stage 2 and Stage 3 Description for the Q3 Interface - Alarm

Surveillance.
Q3
Standard TMN interface covering both protocol and data.
RNR
Radio Network Recording Functions
R-PMO
Real-Time Performance Monitoring
SDM
Statistical Data Mart
SGSN
Serving GPRS Support Node
SGW
Statistical Gateway
SIM
Subscriber Identity Module
SMIA
Statistical Measurement Initiation and Administration
SMO
Software Management Organizer
SNAI
SubNetwork Access Interface
SNMP
Simple Network Management Protocol
SNMP SMT
SNMP Supervision Manager Toolkit
SPAI
Specified Alarm Interface

SQL
Structured Query Language
SS
Switching System
TET
Traffic Estimation Tool
TMN
Telecommunications Management Network
TMOS
Telecommunications Management and Operations Support
TRX
Transceiver
UAS
UNIX Application Server
UNIX
Registered Trademark of UNIX System Laboratories, Inc.
UNIX is a multiuser, multi-tasking operating system.
VERP
SPAI Verification Program
WAS
Windows Application Server
VLR
Visitor Location Register
X.29
Communication Protocol

Add Note...
Show Notes Inline
Hide Inline Notes
List all Notes in this Document...
List all Notes in this Library...

Export all Notes in this Library...

Search for Documents Using Advanced Options

Show Document Info

<CTRL + Right-click> to open browser menu

Refresh all Notes

Bookmark this Document...
Bookmark this Section...
Copy Link to Document (clipboard)
Copy Link to Section (clipboard)

Search for Documents in Library Collection

Find in Document Frame...

Print Document...
Save Document as PDF...
Show Document as PDF
Open in New Window...