Professional Documents
Culture Documents
08 LZT123 3641
08 LZT123 3641
Chapter 8
OBJECTIVES:
Upon completion of this chapter the student will be able to:
t io na
en
lly
t
In
B n
la
k
8 Network Management
Table of Contents
Topic Page
INTRODUCTION .........................................................................................111
TMOS .............................................................................................................112
TELECOMMUNICATIONS MANAGEMENT NETWORK (TMN) ................................ 112
TMOS STRUCTURE AND FUNCTIONS ................................................................. 113
t io na
en
I nt
lly
B n
la
k
INTRODUCTION
Mobile networks require an efficient and easy-to-use operation and
maintenance (O&M) system because:
TMOS
• Centralized
• Separate from the telecommunications network
• Connected to the telecommunications network via standardized
interfaces
• Configuration management
• Fault management
• Performance management
• Security management
• Accounting management
OSS
Network
Management
Network Management
Center (NMC)
Network
Element
Management
OMC A OMC B
Network
Elements
AUC
In OSS, the OMC and NMC functions can be combined in the same
physical installation or implemented at different sites.
The figure below shows the wide range of applications available with
the OSS.
OSS APPLICATIONS
Command Fault Integrated
File Handling
Handling Management Document Tool
Utility (FMU)
Application (CHA) (FM) (IDT)
Operation
Electronic Log Specified Alarm DXX Alarm
Procedure
Book (ELB) Interface (SPAI) Interface (DAI)
Support (OPS)
Statistical Performance
Neighboring Frequency Measurement
Measurement Management
Cell Support Allocation Result
Initiation and Traffic
Administration(SMIA) (NCS) Support (FAS) Recording (MRR)
Recording (PMR)
SOG FUNCTIONS
F Did you know? A network operator requires administrative systems to analyze and
manage network information such as customer subscriptions, billing
One of Ericssons information and for fraud detection. An operators administrative
SOGs is capable of systems are normally called Customer Administration Systems
handling networks
with up to 750,000 (CAS). They are often complex systems that are inflexible and costly
subscribers and can to adapt to the specific needs of individual network operators.
add up to 100,000
new subscriptions The Service Order Gateway (SOG) is an Ericsson product that
each day. enables CASs to exchange information with network elements such
as the HLR, which contains service information.
Customer
OS
SSS // O
OMMC
C Adm.
System
SOG
SOG IMPLEMENTATION
In Ericssons GSM systems the SOG is Unix-based. It contains a
user-friendly GUI to enable access to the required network nodes
and CASs. It can be connected to a maximum of 8 different CASs.
For operation and maintenance of the SOG, it can be connected to
OSS.
BGW FUNCTIONS
A Billing GateWay (BGW) collects billing information or Call Data
Record (CDR) files from network elements such as MSCs and
forwards them to post-processing systems that use the files as input.
A BGW acts as a billing interface to the network elements in any
network and its flexible interface supports adaptation to any new
types of network elements.
MSC
Stockholm Non-Roaming
Non-Roaming
isRoaming
MSC isBillable
Malmö
Roaming
Roaming
Unbillable
BGW IMPLEMENTATION
In Ericssons GSM systems the BGW is implemented using Unix.
Like the SOG, it contains a GUI enabling simple management of the
billing information. It can also be connected to OSS for operation
and maintenance purposes.
t io
e n na
I nt
lly
B n
la
k