Telecommunications / Systems Development

SATHYAN
Fundamentals of EMS,
NMS, and OSS/BSS
JITHESH SATHYAN

Fundamentals of EMS, NMS, and OSS/BSS

In this era when data and voice services are available at a push of a button, service
providers have virtually limitless options for reaching their customers with value-
added services. The changes in services and underlying networks that this always-
on culture creates make it essential for service providers to understand the evolving
business logic and appropriate support systems for service delivery, billing, and
revenue assurance.

Supplying an end-to-end understanding of telecom management layers,

Fundamentals of EMS, NMS, and OSS/BSS is a complete guide to telecom
resource and service management basics. Divided into four sections: Element
Management System, Network Management System, Operation/Business Support
Systems, and Implementation Guidelines, the book examines standards, best
practices, and the industries developing these systems. Each section starts with
basics, details how the system fits into the telecom management framework, and
concludes by introducing more complex concepts.

From the initial efforts in managing elements to the latest management standards,
the text:
• Covers the basics of network management, including legacy systems,
management protocols, and popular products
• Deals with OSS/BSS—covering processes, applications, and interfaces
in the service/business management layers
• Includes implementation guidelines for developing customized
management solutions

The book includes chapters devoted to popular market products and contains case
studies that illustrate real-life implementations as well as the interaction between
management layers. Complete with detailed references and lists of Web resources
to keep you current, this valuable resource supplies you with the fundamental
understanding and the tools required to begin developing telecom management
solutions tailored to your customers’ needs.

AU8573
ISBN: 978-1-4200-8573-0
90000
w w w. c rc p r e s s . c o m

9 781420 085730
www.auerbach-publications.com

AU8573 cvr mech.indd 1 5/20/10 3:08 PM

Fundamentals
of EMS, NMS,
and OSS/BSS
Fundamentals
of EMS, NMS,
and OSS/BSS

Jithesh Sathyan
 OTHER TELECOMMUNICATIONS BOOKS FROM AUERBACH

3D Television (3DTV) Technology, Systems, Mobile Opportunistic Networks: Architectures,

and Deployment Protocols and Applications
Daniel Minoli Edited by Mieso K. Denko
ISBN 978-1-4398-4066-5 ISBN 978-1-4200-8812-0

Applied Aspects of Optical Communication Orthogonal Frequency Division Multiple Access

and LIDAR Fundamentals and Applications
Nathan Blaunstein, Shlomi Arnon, Natan Kopeika, Edited by Tao Jiang, Lingyang Song,
and Arkadi Zilberman and Yan Zhang,
ISBN 978-1-4200-9040-6 ISBN 978-1-4200-8824-3

Cloud Computing and Software Services: Overlay Networks: Toward Information

Theory and Techniques Networking
Edited by Syed A. Ahson and Mohammad Ilyas Sasu Tarkoma
ISBN 978-1-4398-0315-8 ISBN 978-1-4398-1371-3

Cognitive Radio Networks: Architectures, RFID and Sensor Networks: Architectures,

Protocols, and Standards Protocols, Security, and Integrations
Edited by Yan Zhang, Jun Zheng, Edited by Yan Zhang, Laurence T. Yang,
and Hsiao-Hwa Chen and Jiming Chen
ISBN 978-1-4200-7775-9 ISBN 978-1-4200-7777-3

Cooperative Wireless Communications Security of Self-Organizing Networks:

Edited by Yan Zhang, Hsiao-Hwa Chen, MANET, WSN, WMN, VANET
and Mohsen Guizani Edited by Al-Sakib Khan Pathan
ISBN 978-14200-6469-8 ISBN 978-1-4398-1919-7

Evolved Cellular Network Planning and Security of Mobile Communications

Optimization for UMTS and LTE Noureddine Boudriga
Lingyang Song and Jia Shen ISBN 978-0-8493-7941-3
ISBN 978-1-4398-0649-4
Socio-Technical Networks: Science and
Fundamentals of EMS, NMS and OSS/BSS Engineering Design
Jithesh Sathyan Edited by Fei Hu, Ali Mostashari, and Jiang Xie
ISBN 978-1-4200-8573-0 ISBN 978-1-4398-0980-8

Handbook on Mobile Ad Hoc and Pervasive Transmission Techniques for Emergent Multicast
Communications and Broadcast Systems
Edited by Mieso K. Denko and Laurence T. Yang Mario Marques da Silva, Americo Correia, Rui Dinis,
ISBN 978-1-4398-4616-2 Nuno Suoto, and Joao Carlos Silva
ISBN 978-1-4398-1593-9
HSDPA/HSUPA Handbook
Edited by Borko Furht and Syed A. Ahson Underwater Acoustic Sensor Networks
ISBN 978-1-4200-7863-3 Edited by Yang Xiao
ISBN 978-1-4200-6711-8
IP Communications and Services for NGN
Johnson I. Agbinya Wireless Sensor Networks: Principles
ISBN 978-1-4200-7090-3 and Practice
Fei Hu and Xiaojun Cao
Mobile Device Security: A Comprehensive ISBN 978-1-4200-9215-8
Guide to Securing Your Information in a
Moving World ZigBee Network Protocols and Applications
Stephen Fried Chonggang Wang, Tao Jiang, and Qian Zhang
ISBN 978-1-4398-2016-2 ISBN 978-1-4398-1601-1

AUERBACH PUBLICATIONS
www.auerbach-publications.com
5P
0SEFS
$BMM

r

'BY


E-mail: orders@crcpress.com
Auerbach Publications
Taylor & Francis Group
6000 Broken Sound Parkway NW, Suite 300
Boca Raton, FL 33487-2742

© 2010 by Taylor and Francis Group, LLC

Auerbach Publications is an imprint of Taylor & Francis Group, an Informa business

No claim to original U.S. Government works

Printed in the United States of America on acid-free paper

10 9 8 7 6 5 4 3 2 1

International Standard Book Number-13: 978-1-4200-8574-7 (Ebook-PDF)

This book contains information obtained from authentic and highly regarded sources. Reasonable efforts
have been made to publish reliable data and information, but the author and publisher cannot assume
responsibility for the validity of all materials or the consequences of their use. The authors and publishers
have attempted to trace the copyright holders of all material reproduced in this publication and apologize to
copyright holders if permission to publish in this form has not been obtained. If any copyright material has
not been acknowledged please write and let us know so we may rectify in any future reprint.

Except as permitted under U.S. Copyright Law, no part of this book may be reprinted, reproduced, transmit-
ted, or utilized in any form by any electronic, mechanical, or other means, now known or hereafter invented,
including photocopying, microfilming, and recording, or in any information storage or retrieval system,
without written permission from the publishers.

For permission to photocopy or use material electronically from this work, please access www.copyright.
com (http://www.copyright.com/) or contact the Copyright Clearance Center, Inc. (CCC), 222 Rosewood
Drive, Danvers, MA 01923, 978-750-8400. CCC is a not-for-profit organization that provides licenses and
registration for a variety of users. For organizations that have been granted a photocopy license by the CCC,
a separate system of payment has been arranged.

Trademark Notice: Product or corporate names may be trademarks or registered trademarks, and are used
only for identification and explanation without intent to infringe.
Visit the Taylor & Francis Web site at
http://www.taylorandfrancis.com

and the Auerbach Web site at

http://www.auerbach-publications.com
Contents

Foreword............................................................................................................xv
Preface............................................................................................................ xvii
About the Author............................................................................................. xix

SEcTiON I ELEMENT MANAGEMENT SYsTEM (EMS)

1. What Is EMS?..........................................................................................3
1.1 Introduction.......................................................................................3
1.2 EMS in Telecom.................................................................................4
1.3 EMS Architecture...............................................................................5
1.4 Need for EMS....................................................................................6
1.5 Characteristics Required in EMS.......................................................7
1.6 Popular EMS Products.......................................................................8
1.7 Conclusion.........................................................................................8
Additional Reading.....................................................................................19
2. TMN Model..........................................................................................21
2.1 Introduction.....................................................................................21
2.2 What Is TMN?.................................................................................22
2.3 Functional Architecture....................................................................24
2.4 Physical Architecture........................................................................26
2.5 Information Architecture..................................................................28
2.6 Logical Architecture.........................................................................28
2.7 Conclusion.......................................................................................31
Additional Reading.....................................................................................31
3. ITU-T FCAPS........................................................................................33
3.1 Introduction.....................................................................................33
3.2 Fault Management.......................................................................... 34
3.3 Configuration Management.............................................................37
3.4 Accounting Management.................................................................38

v
vi  ◾  Contents

3.5 Performance Management............................................................... 40

3.6 Security Management...................................................................... 42
3.7 Conclusion...................................................................................... 44
Additional Reading.................................................................................... 44
4. EMS Functions......................................................................................45
4.1 Introduction.....................................................................................45
4.2 Network/Service Provisioning......................................................... 46
4.3 Network/Service Development and Planning...................................47
4.4 Inventory Management....................................................................49
4.5 Integrated Multivendor Environment...............................................50
4.6 Service Assurance.............................................................................51
4.7 Network Operations Support...........................................................54
4.8 Network/Service Monitoring and Control........................................55
4.9 Conclusion.......................................................................................56
Additional Reading.....................................................................................56
5. OSI Network Management....................................................................57
5.1 Introduction.....................................................................................57
5.2 OSI Organizational Model...............................................................58
5.3 OSI Information Model...................................................................62
5.3.1 Structure of Management Information (SMI).....................62
5.3.2 Management Information Base (MIB)................................63
5.4 OSI Communication Model........................................................... 64
5.5 OSI Functional Model.....................................................................67
5.6 OAM................................................................................................67
5.7 TMN and OSI Management............................................................68
5.8 Conclusion.......................................................................................68
Additional Reading.....................................................................................69
6. Management Protocols..........................................................................71
6.1 Introduction.....................................................................................71
6.2 Overview of SNMP (Simple Network Management Protocol).........72
6.3 Overview of TL1 (Transaction Language 1).....................................73
6.4 Overview of CMIP (Common Management
Information Protocol).......................................................................75
6.5 Overview of CLP (Command Line Protocol)...................................76
6.6 Overview of XMLP (XML Protocol)...............................................78
6.7 Overview of SOAP (Simple Object Access Protocol)........................79
6.8 Overview of NETCONF (Network Configuration)....................80
6.9 Overview of IIOP (Internet Inter-ORB Protocol).............................82
6.10 Conclusion.......................................................................................83
Additional Reading.................................................................................... 84
 Contents  ◾  vii

7. Standardizing Bodies............................................................................85
7.1 Introduction.....................................................................................85
7.2 ITU (International Telecommunication Union)...............................85
7.3 TMF (TeleManagement Forum)......................................................87
7.4 DMTF (Distributed Management Task Force).................................88
7.5 3GPP (Third Generation Partnership Project)................................. 90
7.6 ETSI (European Telecommunications Standards Institute)..............91
7.7 MEF (Metro Ethernet Forum).........................................................93
7.8 ATIS (Alliance for Telecommunications Industry Solutions)............94
7.9 OASIS (Organization for the Advancement of Structured
Information Standards)....................................................................95
7.10 OMA (Open Mobile Alliance).........................................................96
7.11 SNIA (Storage Networking Industry Association)............................96
7.12 Conclusion.......................................................................................97
Additional Reading.....................................................................................97

8. MTNM Compliant EMS.......................................................................99

8.1 Introduction.....................................................................................99
8.2 About MTNM...............................................................................100
8.3 MTNM Business Agreement (TMF 513).......................................102
8.4 MTNM Information Agreement (TMF 608).................................104
8.5 MTNM Solution Set (TMF 814)...................................................106
8.6 MTNM Implementation Statement and
Guidelines (TMF 814A).................................................................109
8.7 Conclusion..................................................................................... 111
Additional Reading................................................................................... 111

SEcTiON II NETWORK MANAGEMENT SYSTEM (NMS)

9. Communication Networks..................................................................115
9.1 Introduction................................................................................... 115
9.2 ATM Network............................................................................... 116
9.3 GSM Network................................................................................ 117
9.4 GPRS Network.............................................................................. 119
9.5 UMTS Network.............................................................................121
9.6 MPLS Network..............................................................................122
9.7 IMS................................................................................................123
9.8 CDMA Network............................................................................125
9.9 WiMAX.........................................................................................127
9.10 Recent Initiatives like LTE and SAE..............................................128
9.11 Conclusion.....................................................................................129
Additional Reading...................................................................................130
viii  ◾  Contents

10. Seven-Layer Communication Model................................................131

10.1 Introduction..............................................................................131
10.2 Physical Layer............................................................................132
10.3 Data Link Layer........................................................................133
10.4 Network Layer...........................................................................135
10.5 Transport Layer.........................................................................136
10.6 Session Layer.............................................................................137
10.7 Presentation Layer.....................................................................138
10.8 Application Layer......................................................................140
10.9 TCP/IP Model and OSI Model................................................. 141
10.10 Conclusion................................................................................143
Additional Reading................................................................................144
11. What Is NMS?..................................................................................145
11.1 Introduction.............................................................................. 145
11.2 Network Management System...................................................146
11.3 Legacy NMS Architecture.........................................................148
11.4 Data Collection Components....................................................149
11.5 Platform Components...............................................................150
11.6 Management Function Components......................................... 151
11.7 GUI Components...................................................................... 153
11.8 NBI (North Bound Interface) Components............................... 155
11.9 Design Considerations...............................................................156
11.10 Conclusion................................................................................ 157
Additional Reading................................................................................ 158
12. NMS Functions................................................................................159
12.1 Introduction.............................................................................. 159
12.2 Resource Provisioning...............................................................160
12.3 Resource Data Collection and Processing..................................163
12.4 Resource Trouble Management.................................................166
12.5 Resource Performance Management..........................................169
12.6 Resource Management and Operation
Support and Readiness.........................................................171
12.7 Conclusion................................................................................172
Additional Reading................................................................................172
13. NMS Products..................................................................................173
13.1 Introduction..............................................................................173
13.2 OpenNMS................................................................................ 174
13.3 AdventNet Web NMS...............................................................177
13.4 HP OpenView...........................................................................179
13.5 IBM Tivoli................................................................................182
13.6 Telecom Network Management Products..................................185
 Contents  ◾  ix

13.7 Conclusion................................................................................185
Additional Reading................................................................................186
14. SNMP...............................................................................................187
14.1 Introduction..............................................................................187
14.2 SNMPv1...................................................................................188
14.3 SNMPv2...................................................................................192
14.4 SNMPv3...................................................................................196
14.5 Conclusion............................................................................... 200
Additional Reading................................................................................201
15. Information Handling.....................................................................203
15.1 Introduction..............................................................................203
15.2 ASN.1....................................................................................... 204
15.2.1. ASN.1 Simple Types.................................................... 204
15.2.2. ASN.1 Structured Type.................................................207
15.3 BER.......................................................................................... 208
15.4 SMI...........................................................................................210
15.5 Conclusion................................................................................ 215
Additional Reading................................................................................216
16. Management Information Base (MIB).............................................217
16.1 Introduction.............................................................................. 217
16.2 Types of MIB............................................................................ 218
16.3 MIB-II..................................................................................... 220
16.4 SNMPv1 MIB...........................................................................227
16.5 SNMPv2 MIB...........................................................................227
16.6 SNMPv3 MIB...........................................................................229
16.7 Conclusion................................................................................230
Additional Reading................................................................................230
  17. Next Generation Network Management (NGNM)..........................231
17.1 Introduction..............................................................................231
17.2 NGNM Basics...........................................................................232
17.3 TR133.......................................................................................236
17.4 M.3060.....................................................................................240
17.5 Conclusion................................................................................243
Additional Reading............................................................................... 244
18. XML-Based Protocols......................................................................245
18.1 Introduction..............................................................................245
18.2 XMLP Overview...................................................................... 246
18.3 XML Protocol Message Envelope..............................................248
18.4 XML Protocol Binding..............................................................248
x  ◾  Contents

18.5 Mapping with SNMP................................................................249

18.5.1. Messaging.....................................................................250
18.5.2. Transfer of Message......................................................252
18.5.3. XMLP-Based Management Framework........................253
18.6 SOAP........................................................................................256
18.7 NETCONF.............................................................................. 260
18.8 Conclusion................................................................................263
Additional Reading................................................................................263

SEcTiON III OPERATION/BUSINESS SUPPORT

SYSTEMS (OSS/BSS)
19. What Is OSS and BSS?.....................................................................267
19.1 Introduction..............................................................................267
19.2 Service Providers....................................................................... 268
19.3 Drivers for Support Systems......................................................270
19.4 What Do Support Systems Offer?..............................................271
19.4.1. Support Systems to Manage the Customers..................271
19.4.2. Support Systems to Manage Service..............................272
19.4.3. Support Systems to Manage Resources.........................273
19.5 Defining OSS and BSS..............................................................273
19.6 From TMN to eTOM...............................................................275
19.7 Few OSS/BSS Processes.............................................................276
19.8 Conclusion................................................................................279
Additional Reading................................................................................279

20. OSS/BSS Functions..........................................................................281

20.1 Introduction..............................................................................281
20.2 Fulfillment Process....................................................................281
20.3 Assurance Process......................................................................294
20.4 Billing Process...........................................................................307
20.5 Conclusion................................................................................323
Additional Reading................................................................................324

21. NGOSS.............................................................................................325
21.1 Introduction..............................................................................325
21.2 NGOSS Overview.....................................................................326
21.3 NGOSS Lifecycle......................................................................327
21.4 SANRR Methodology...............................................................330
21.5 eTOM Model............................................................................331
21.6 SID............................................................................................333
21.7 TNA..........................................................................................334
21.8 TAM.........................................................................................335
 Contents  ◾  xi

21.9 Conclusion................................................................................336
Additional Reading................................................................................337

22. Telecom Processes............................................................................339

22.1 Introduction..............................................................................339
22.2 eTOM...................................................................................... 340
22.3 ITIL..........................................................................................341
22.4 Integrated Approach................................................................. 343
22.5 eTOM and ITIL in ICT........................................................... 344
22.6 ITIL Processes Implemented with eTOM................................. 346
22.7 Business Process Flow Modeling............................................... 348
22.8 Conclusion................................................................................ 351
Additional Reading................................................................................ 351

23. Management Applications...............................................................353

23.1 Introduction..............................................................................353
23.2 Overview of Applications..........................................................354
23.3 Conclusion................................................................................376
Additional Reading................................................................................377
24. Information Models.........................................................................379
24.1 Introduction..............................................................................379
24.2 Shared Information/Data Model (SID).....................................380
24.3 Common Information Model (CIM)........................................384
24.4 Conclusion................................................................................389
Additional Reading................................................................................389
25. Standard Interfaces..........................................................................391
25.1 Introduction..............................................................................391
25.2 MTOSI Overview.....................................................................392
25.3 MTOSI Notifications................................................................395
25.4 OSS/J Overview........................................................................396
25.5 MTOSI and OSS/J....................................................................399
25.6 Conclusion............................................................................... 400
Additional Reading................................................................................401

SEcTiON IV IMPLEMENTATION GUIDELINES

26. Socket Communication....................................................................405
26.1 Introduction..............................................................................405
26.2 Application Layer..................................................................... 406
26.3 Monitoring............................................................................... 408
26.4 Client–Server Model................................................................ 409
26.5 Socket Interface.........................................................................410
xii  ◾  Contents

26.6 Basic Socket System Calls..........................................................412

26.7 Client Server Implementation for Connection
Oriented Communication.........................................................416
26.8 Client Server Implementation for Connectionless
Protocol Communication.......................................................... 419
26.9 Conclusion............................................................................... 423
Additional Reading............................................................................... 423
27. RPC Programming..........................................................................425
27.1 Introduction..............................................................................425
27.2 RPC Overview......................................................................... 426
27.3 RPC Concepts...........................................................................427
27.3.1. Transport......................................................................427
27.3.2. Presentation................................................................. 428
27.3.3. RPCGEN Compiler.....................................................429
27.3.4. RPC Procedure Identification...................................... 430
27.3.5. Port Mappers................................................................431
27.3.6. Broadcasting.................................................................431
27.3.7. Batching........................................................................432
27.3.8. Authentication..............................................................432
27.4 Defining the Protocol................................................................433
27.5 Interface Routines.................................................................... 434
27.6 RPC Implementation............................................................... 434
27.7 Conclusion................................................................................437
Additional Reading................................................................................438
28. Web Communication.......................................................................439
28.1 Introduction..............................................................................439
28.2 Hypertext Transfer Protocol (HTTP)....................................... 440
28.3 Web Client and Server.............................................................. 444
28.4 Implementing Web Server........................................................ 448
28.5 Conclusion................................................................................450
Additional Reading................................................................................ 451
29. Mail Communication.......................................................................453
29.1 Introduction..............................................................................453
29.2 Mail Delivery Process................................................................454
29.3 Mail Protocols...........................................................................456
29.4 User Agent.................................................................................456
29.5 Multipurpose Internet Mail Extensions.....................................458
29.6 Implementation.........................................................................461
29.7 Conclusion................................................................................463
Additional Reading................................................................................463
 Contents  ◾  xiii

30. File Handling...................................................................................465

30.1 Introduction..............................................................................465
30.2 Communication with FTP....................................................... 466
30.3 File Transfer with FTP..............................................................469
30.4 File Commands.........................................................................470
30.5 File Sharing...............................................................................472
30.6 Implementation.........................................................................472
30.7 Conclusion................................................................................474
Additional Reading................................................................................475

31. Secure Communication....................................................................477

31.1 Introduction..............................................................................477
31.2 Symmetric Key Cryptography...................................................478
31.3 Public Key Cryptography......................................................... 480
31.4 Message Security.......................................................................482
31.5 Key Management......................................................................483
31.6 Security Protocols..................................................................... 484
31.7 Implementation Example...........................................................485
31.8 Conclusion................................................................................487
Additional Reading................................................................................487

32. Application Layer.............................................................................489

32.1 Introduction..............................................................................489
32.2 NETCONF...............................................................................490
32.3 RPC Elements in NETCONF..................................................491
32.4 NETCONF Operations............................................................492
32.5 MIB Event to XML...................................................................498
32.6 Conclusion................................................................................502
Additional Reading................................................................................502

33. OSS Design Patterns........................................................................503

33.1 Introduction..............................................................................503
33.2 Singleton Design Pattern.......................................................... 504
33.3 Chain of Responsibility Design Pattern.................................... 506
33.4 Observer Design Pattern............................................................509
33.5 Factory Design Pattern..............................................................512
33.6 Adapter Design Pattern............................................................. 516
33.7 Iterator Design Pattern.............................................................. 516
33.8 Mediator Design Pattern........................................................... 519
33.9 Conclusion................................................................................522
Additional Reading................................................................................522

34. Report: NGNM Framework and Adoption Strategy........................523

34.1 Report Overview.......................................................................523
xiv  ◾  Contents

34.2 Introduction..............................................................................524
34.3 Legacy NMS.............................................................................525
34.4 Issues with Legacy NMS...........................................................526
34.5 NGNM Solution.......................................................................527
34.5.1. NGNM Framework......................................................527
34.5.2. Generic Functionalities for NGNM..............................530
34.5.3. Specialized Functions....................................................531
34.5.4. Customization for a Specific Network...........................532
34.6 Adoption Strategy......................................................................532
34.6.1. Using Mediation Layer.................................................532
34.6.2. Staged Migration..........................................................533
34.6.3. Combining Mediation and Migration...........................539
34.7 Analysis of NGNM Framework.................................................539
34.8 Conclusion............................................................................... 540
Supporting Publications........................................................................ 540
References..............................................................................................541
Index............................................................................................................543
Foreword

In the telecommunications industry, the rapidly evolving technologies and their

changes make it very difficult to develop efficient support systems. In the past,
different vertical networks addressing different needs and distinctive networks
with definite management strategy were the easiest approaches taken by operators.
However, in a world where operators need to find ways to differentiate their offer-
ings and keep the margins healthy, the above “stovepipe” approach is no longer
sufficient and could hamper good business practice.
With advances in technology, the communications network and its manage-
ment are becoming more complex as well as more dynamic and fluid in nature. As
with any other field of study involving the term management, the world of telecom-
munications management also tends to be opaque and filled with jargon and ter-
minology. It is a field that would benefit immensely from literature that demystifies
and simplifies all its various aspects.
Fundamentals of EMS, NMS, and OSS/BSS has excellent coverage of the basics
of telecom management, from legacy management systems to the next generation
systems. In this book, Jithesh introduces the principles of EMS, NMS, and OSS/
BSS and goes in-depth on implementation guidelines including the most com-
mon design patterns in use. This book makes two important contributions. First,
it shows the roles that EMS, NMS, and OSS/BSS can play in the telecom environ-
ment with complex real-time systems. Second, it provides a very realistic view of
use cases and implementation examples illustrating how the aspects covered in the
first three sections of the book can be put into practice.
With his experience in delivering telecom projects, Jithesh has explained ele-
ment management systems (EMS), network management systems (NMS), and
operation/business support systems (OSS/BSS) through concepts, functionality
descriptions, applicable protocols, and implementation guidelines. Each section
touches upon definitions and models, explaining the complex concepts without
losing simplicity or introducing technical jargon, and finally directing the user to
further reading material to enable a better, more detailed understanding.
I am honored to have had the opportunity to work directly with Jithesh in
architectural design efforts for the telecom support systems and I am sure this

xv
xvi  ◾  Foreword

book will be a valuable asset for academicians and professionals. It is with great
pleasure that I introduce this book. I wish Jithesh all the success in this and future
endeavors.

Manesh Sadasivan
Principal Architect, Product Engineering
Infosys Technologies Limited (www.infosys.com)
Preface

The communication service industry is moving toward a converged world where

services like data, voice, and value-added services are available anytime and any-
where. The services are “always on,” without the hassle of waiting or moving
between locations to be connected or for continuity in services. The facilities offer
easy and effortless communications, based on mobility and personalized services
that increase quality of life and lead to more customer satisfaction. Service provid-
ers will have much more effective channels to reach the customer base with new
services and applications. With changes in services and underlying networks, the
ease in managing the operations becomes critically important. The major chal-
lenge is changing business logic and appropriate support systems for service deliv-
ery, assurance, and billing. Even after much maturity of IMS technology, there has
been a lag in the adoption of this service because of the absence of a well-defined
OSS/BSS stack that could manage the IMS and proper billing system to get busi-
ness value to service providers to move to IMS. This makes operations support
systems a topic of considerable interest in today’s ICT industry.
Operations support systems (OSS) as a whole includes the systems used to
support the daily operations of the service provider. These include business sup-
port systems (BSS) such as billing and customer management, service operations
such as service provisioning and management, element management, and network
management applications. In the layered management approach, BSS corresponds
to business management and OSS corresponds to service management, while the
network level operation support is done using a network management system and
individual resources are managed with an element management system. The same
terminology is used in the title of the book to explain the different layers of telecom
management that are covered in this book.
Fundamentals of EMS, NMS, and OSS/BSS completely covers on the basics
of telecom resource and service management. This book is designed to teach all
you need to understand to get a good theoretical base on telecom management.
The book has four sections: Element Management System, Network Management
System, Operation/Business Support Systems, and Implementation Guidelines.
The first section covers element management system in detail. Initial efforts in

xvii
xviii  ◾  Preface

managing elements to the latest management standards are covered in this part.
The second section deals with the basics of network management; legacy systems,
management protocols, standards, and popular products are all handled in this
part. The third section deals with OSS/BSS, covering the process, applications, and
interfaces in the service/business management layers in detail. The final section
gives the reader implementation guidelines to start developing telecom manage-
ment solutions.
This book is dedicated to my beloved wife for her patience and consistent sup-
port that helped me a lot in completing this book. I would like to thank the product
engineering team at Infosys for giving me numerous engagements in EMS, NMS,
and OSS/BSS space with a variety of telecom clients in multiple countries that went
a long way in giving me the knowledge to write this book. Writing this book has
been a very good experience and I hope you enjoy reading it as much as I enjoyed
writing it.
Jithesh Sathyan
Technical Architect
Infosys Technologies Limited
About the Author

Jithesh Sathyan is a technical architect at Infosys Technologies Limited (NASDAQ:

INFY). He is the sole inventor of the first granted patent of Infosys at the U.S. Patent
and Trademark Office. He has to his credit multiple international papers in the
telecom domain, specifically on EMS, NMS, and OSS/BSS. He is a gold medalist in
electronics and communication engineering.
The author has been working on multiple projects involving design and develop-
ment of telecom management solutions for a variety of telecom clients in OEM and
service provider space. He has multiple filed patents in the telecom domain. Jithesh
has published several white papers in standardizing forums, such as TeleManagement
Forum that specializes in defining standards on telecom management. He is an active
member of many telecom management standardizing forums. He has also contrib-
uted a chapter entitled “Role of OSS/BSS in Success of IMS” in IMS Handbook:
Concepts, Technologies, and Services published by CRC Press.

xix
ELEMENT I
MANAGEMENT
SYsTEM (EMS)
Chapter 1

What Is EMS?

This chapter is intended to provide the reader with a basic understanding of Element
Management System. At the end of this chapter you will have a good understand-
ing of what is a network element, the need for managing a network element, how an
element management system fits into telecom architecture, and some of the major
vendors involved in the development of EMS.

1.1  Introduction
Industries are highly dependent on their networking services for day-to-day activi-
ties from sending mail to conducting an audio/video conference. Keeping services
running on the resource is synonymous with keeping the business running. Any
service is offered by a process or set of processes running on some hardware. A set
of hardware makes up the inventory required for keeping a service up and running.
If the hardware goes down or when there is some malfunction with the hardware,
this would in turn affect the service. This leads to the need to monitor the hardware
and ensure its proper functioning in order to offer a service to a customer. This
hardware being discussed is the element and an application to monitor the same
constitutes the element management system. Since the element is part of a network,
it is usually referred to as network element or NE.

A network element is the hardware on which a process or set of processes

is executed to offer a service or plurality of services to the customer.
EMS is an application that manages a telecom network element.

3
4  ◾  Fundamentals of EMS, NMS and OSS/BSS

Most element management systems are available in the market support man-
agement data collection from multiple network elements though they cannot be
called a network management system. Hence an application is not necessarily a
network management system just because it supports data collection from mul-
tiple NEs. The functionalities offered by the systems decide whether it is a network
management system (NMS) or an element management system (EMS). Let us
make this point clear with an example. A topology diagram in an EMS would
have the nodes configured in the element while a topology diagram in an NMS
will show all the configured network elements managed by the NMS. Again a fault
management window on an EMS would show only the logs and alarms generated
on the network element it is managing. The functionalities like fault correlation
and decision handling based on events from various NEs are shown in an NMS.
The functionalities of an EMS are covered in detail in the chapters to follow.
This introduction is intended to only give the reader a feel of what a network ele-
ment and EMS is in telecom domain. In the sections to follow we will explore the
architecture of EMS and take some sample EMS products to gain familiarity with
EMS applications available in the market.

1.2 EMS in Telecom
As shown in Figure 1.1, an element manager (EM) collects data from the network
elements (NE). An ideal scenario would involve one element manager to collect
data from a single network element as in EM-2 and NE-n. It can be seen that this is
not the case for an actual EMS product. Almost all the EMS products available in
the market support management of a set of elements as shown for element manag-
ers other than EM-2 in Figure 1.1.

Even when data is collected from multiple NEs, the management

­system is still an element manager when data collection and processing

NMS server

EM-1 EM-2 EM-n

NE-a NE-b NE-n NE-x NE-y

Figure 1.1 Layered view of an element management system.

 What Is EMS?  ◾  5

is handled on a per NE basis and functionalities offered by the EM

does not include any function that represents processed output from an
aggregate of data collected from different NEs.

It is seen that while enhancing an EMS product or to make the product com-
petitive in the market, many EMS solution developers offer some of the NMS
related functionalities that involve processing of collected data from multiple NEs
to display network representation of data. This point needs to be carefully noted by
the reader to avoid getting confused when handling an actual EMS product that
might include some NMS features as part of the product suite.
Figure 1.1 showing layered views closely resembles the TMN model with the
network elements in the lowest layer, above which is the element management layer
followed by network management layer. The TMN model is handled in much
detail in Chapter 2.
The NMS server may not be the only feed that collects data from an EMS
server. The EMS architecture is handled in more detail in the next section where
the various feeds from an EMS sever are depicted pictorially and explained.

1.3 EMS Architecture
The element management system in Figure 1.2 is the EMS server that provides
FCAPS functionality. The FCAPS is short for Fault, Configuration, Accounting,
Performance, and Security. Basic FCAPS functionality at element level is offered
in EMS layer. The FCAPS is also referred in conjunction with the NMS layer as an
enhanced version of these functionalities come up in the NMS layer. While EMS
looks at fault data from a single element perspective, an NMS processes an aggre-
gate of fault data from various NEs and performs operations using this data.

Interface for NMS EMS

web client Server Client DB

EMS Server (FCAPS)

NE-1 NE-2 NE-n

Figure 1.2 Element management system architecture.

6  ◾  Fundamentals of EMS, NMS and OSS/BSS

Data collected by the EMS from the network elements are utilized by:

◾◾ NMS Server: The NMS uses collected as well as processed data from the
EMS to consolidate and provide useful information and functionalities at a
network management level.
◾◾ EMS Client: If data from EMS needs to be represented in GUI or as console
output to a user then an EMS client is usually implemented for the same.
The EMS client would provide help in representing the data in a user-friendly
manner. One of the functions in ‘F “C” APS’ is configuring the network
elements. The EMS client can be used to give a user-friendly interface for
configuring the elements.
◾◾ Database (DB): Historical data is a key component in element management.
It could be used to study event/fault scenarios, evaluate performance of the
network elements, and so on. Relevant data collected by EMS needs to be
stored in a database.
◾◾ Interface for web client: Rather than an EMS client, most users prefer a light-
weight, web-based interface to be a replacement for the web client. This func-
tionality is supported by most EMS solutions.
◾◾ The EMS output could also be feed to other vendor applications. These exter-
nal applications might work on part or whole of the data from the EMS.

1.4 Need for EMS

The complexity of new services and the underlying network is increasing exponen-
tially. At the same time there is a lot of competition among service providers offer-
ing new and compelling services. This leads to the need for minimizing the cost of
network operations. This can only be achieved if the elements in the network are
well managed. The increase in complexity can be handled cost effectively only by
providing good user interface for managing the service and network thus hiding
complexity. The other option of having more trained professionals is both expensive
and risky.
Let us try to list the major issues in telecom industry that necessitates the need
for a user-friendly and functionality-rich EMS:

◾◾ There are an increasing variety of NEs: New network elements are being
developed to provide new services. In the network itself there are mul-
tiple telecom networks like GSM, GPRS, CDMA, IMS, and so on with
independent work being carried out in the development of access and core
network.
◾◾ Need to support elements from different vendors: Mergers and acquisitions
are inevitable in the telecom industry. So a single EMS product might be
required to collect data from a family of network elements.
 What Is EMS?  ◾  7

◾◾ Increase in complexity of managing NEs: With advances in telecom indus-

try there is a major trend to combine functionalities performed by multiple
elements to a single element. For example, most vendors now have a single
SGSN performing functionality of U-SGSN and G-SGSN and a media gate-
way is embedded with functionality to handle signaling protocols.
◾◾ Shortage of trained telecommunications technicians: Telecom industry is
evolving so rapidly that telecom technicians are not able to keep pace with
the same. This leads to a shortage of trained professionals in maintaining the
network. With a functionality rich and user-friendly EMS solution, the effort
to train technicians is reduced.
◾◾ Need to reduce cost of managing network and high-quality innovative ser-
vices: Cost of managing the network and service is one major area where
companies want to cut down cost as they do not directly generate revenue,
unlike customer management and research activities that could help to get
and retain business.

Meeting these challenges requires element management systems (not just EMS but
good NMS, OSS, and BSS also) with the maximum efficiency and flexibility with
respect to accomplishing tasks.

1.5  Characteristics Required in EMS

The characteristics required in an EMS solution are:

◾◾ User-friendly interface: The interface to work with the EMS (EMS client
or web client) needs to be an intuitive, task-oriented GUI to allow opera-
tions functions to be performed in the shortest possible time with minimal
training.
◾◾ Quick launch: This would enable a user working at the NML, SML, or BML
to launch any EMS desired (when multiple EMS are involved).
◾◾ Troubleshoot NE: It should be possible for a technician to directly log into
any NE from the EMS that manages it for ease in troubleshooting an issue.
Single-sign-on is a popular capability that allows the same user id and pass-
word to be used when logging into the applications involved in different ­layers
of TMN model that will be discussed in the next chapter.
◾◾ Low-cost operations platform: This would help in minimizing the total cost
to own and operate the computing platform on which the EMS runs.
◾◾ Ease of enhancement: New features need to be added to an EMS product and
the product might require easy integration and work with another product.
Some of the techniques currently adopted in the design of such systems is
to make it based on service oriented architecture (SOA), comply to COTS
software standards, and so on.
8  ◾  Fundamentals of EMS, NMS and OSS/BSS

◾◾ Context-sensitive help: This reduces the training required for technicians.

Context-sensitive help can be associated with any functionality in EMS GUI.
With event/fault, a context-sensitive help would involve a quick launch link for
information on that fault. Another usual feature in applications is a “?” icon
that can be dragged and dropped to any part of the application and a help is
launched on how to work on the specific part where the icon is dropped.
◾◾ Access anywhere: This would require a person in any remote location to access
the EMS. As already discussed most EMS now provide a web-based interface
so that with secure connection technique the internet can be used to access
company intranet and launch the web-based EMS.
◾◾ Effective database: All possible data collected from NE needs to be stored
into the EMS database. This will improve service, save time, and save money.
There should also be a functionality to generate standard reports and the
ability to export data to other application tools that specialize in analysis and
reporting.

Above all, the key to being a leader in EMS development is to make the product
functionality rich and to ensure that there are key features that differentiate the
product from its competitors.

1.6  Popular EMS Products

The data sheet below is a list of popular EMS products available in the market.
Some or most of the product has capabilities that span outside the element manage-
ment layer and might involve some level of network and service management. The
information is compiled from data in the World Wide Web and does not present
the authors opinion about a specific product. The products are listed in alphabetical
order (see Table 1.1).
Some other EMS products from popular network equipment manufacturers are:

◾◾ Nortel’s Integrated Element Management System

◾◾ Aveon Element Management Software
◾◾ Fujitsu’s NETSMART Element Management System
◾◾ LineView Element Management System from Alcatel-Lucent
◾◾ NMC-RX EMS from Juniper Networks

1.7  Conclusion
This chapter thus provides a basic understanding of an element management system
(EMS) and what a network element is from the perspective of EMS. The chapter
also helps to understand the role of EMS in the telecom layered view and the EMS
 What Is EMS?  ◾  9

Table 1.1  Some Popular EMS Products

No Product Key Features

1 AdventNet Web • Fault management

NMS • Configuration management
• Discovery
• Performance management
• Security
• Inventory management

2 AirWave: • User and device monitoring

Wireless • Automated device discovery
Network
Management • Group-based policy definition
Software • Centralized configuration and firmware management
• Automated compliance management
• Historical trend reports
• Automated diagnostics and alarms
• Automated RF management
• Multivendor management
• Multiarchitecture support

3 AudioCodes’ • Client /Server architecture

Element • Java-based architecture
Management
System • API–OEM ready
• Audit logging
• Multi–language support ready
• Open solutions environment
• Operator individual views and profiles
• Supports gradual network deployment

4 BroadWorks • Auto-discovery
Element • Configuration management
Management
System • Centralized administrator management
• Fault management
• Performance management
• Capacity management
• Multirelease Support

(Continued)
10  ◾  Fundamentals of EMS, NMS and OSS/BSS

Table 1.1  Some Popular EMS Products (Continued)

No Product Key Features

5 CABLEwatch • Visualization of the HFC network

EMS • Network location tree view—hierarchy viewer
• Network location map view—topology viewer
• Alarm log view that displays the alarms in a table
• Integrated remote LMT viewer
• Alarm management

6 CatenaView • Full FCAPS and OAM&P functionality

EMS • Scalable architecture
• OSS and NMS integration
• Remote service activation
• Templates for simplified provisioning
• Unified management of broadband
• Access systems

7 Cisco Element • Map viewer

Management • Deployment wizard
System
• Auto-discovery
• Event browser
• Object group manager
• Performance manager
• User access control

8 Convergent • Advanced multilayer GUI’s for all processes

Element • Terminal and browser-based client architecture
Management
System from • Integrated with a wide range of databases
Vertel • Integration over a wide range of network devices
• A fully distributed architecture
• Mapping of protocol specific information to CIM
• Off-the-shelf standards-based management
services
• Topology discovery and management
• Configuration and provisioning
 What Is EMS?  ◾  11

Table 1.1  Some Popular EMS Products (Continued)

No Product Key Features

• Software administration
• Fault monitoring and management
• Performance monitoring and management
• Interfaces that can be changed, added, and deleted
• Off-the-shelf system services for distribution
• Security
• Database integration and database persistence

9 ENvision • Intuitive graphical interface

Element • Advanced network mapping
Management
System • Automatic device discovery
• Distributed architecture
• Color-coded alerting
• Flexible MIB tools
• Multiple login consoles

10 EdgeView • Data collection, monitoring, and management

Element • Fault management including trip data, multiple
Management outstanding events, and summary alerts
System

11 expandsl • Java-based N-tier software architecture

Element • Automatic synchronization between EMS and NEs
Management
System • Web browser-based user interface
• Highly portable

12 MetaSwitch • Details of all installed hardware components

Element • Ability to configure the MetaSwitch call agent,
Management signaling gateway, and media gateway components,
System as well as other
• MetaSwitch-managed devices (such as IADs)
• List of alarms currently raised on MetaSwitch
network elements and managed devices, with
correlation between primary and subsidiary alarms
• Interactive, context-sensitive help

(Continued)
12  ◾  Fundamentals of EMS, NMS and OSS/BSS

Table 1.1  Some Popular EMS Products (Continued)

No Product Key Features

13 MBW Element • Network device discovery and mapping

& Network • Device configuration and management
Management
• Fault and alarm management/notification
• Element and network performance management
• Security management

14 Motorola’s HFC • FCAPS support

Manager • Easy-to-use graphical user interface (GUI)
• Device auto-discovery
• Remote access
• Customizable maps and containers
• Local language capability

15 NetAtlas from • Auto-discovery and device viewer

ZyXEL • Templates provisioning for efficient configuration
• Traffic/performance monitoring and management
• Alarm and event management
• Batch Firmware upgrade
• Feature-rich Layer2 and Layer3 configuration
• Tight access control and log management
• Allow up to 10 concurrent users

16 NetBeacon • FCAPS model

Element • Service provisioning
Management
System • End-to-end service assurance
• MEF-defined services support
• Secure access

17 NetBoss • Java J2SE object-oriented technology

Element • Cross-platform compatibility
Management
System • Uniform and consistent look and feel across GUIs
• Client/server implementation
• Managed-object database compliant with
DMTF CIM
 What Is EMS?  ◾  13

Table 1.1  Some Popular EMS Products (Continued)

No Product Key Features

• Custom and standard external interfaces

• Textual presentation
• Explorer presentation
• Console control panel
• Online help

18 NetConductor • Equipment configuration

Element • Secure operating software downloading
Management
System • Alarm logging
• Configuration backup/restore
• Audit logging
• User access control
• Statistics collection
• Inventory reporting
• High availability
• Line diagnostic tests

19 NetConsul EMS • Management of all device features

• Network-level alarm status by site
• Graphical alarm views
• Device templates for easy provisioning
• Drag-and-drop configuration
• Autonomous alarm monitoring via SNMP
• Security features including role-based
permission hierarchy
• Context-sensitive online help

20 Netcool/Impact • Event enrichment with business and service context

from Tivoli • Real-time business activity monitoring
(IBM)
• Automated service impact analysis
• Advanced problem correlation, notification, and
actions
• Advanced data visualization and metric calculation

(Continued)
14  ◾  Fundamentals of EMS, NMS and OSS/BSS

Table 1.1  Some Popular EMS Products (Continued)

No Product Key Features

21 NetOp EMS • Intuitive graphical user interface (GUI)

• Sophisticated user security
• Efficient inventory management
• Configuration management
• Superior fault management
• Auto node discovery
• Sophisticated alarm interface
• BGP attribute-based accounting

22 Net–Net EMS • Enables efficient deployment, configuration,

by Acme Packet and upgrade
• Monitors real-time SBC fault and performance status
• Delivers bulk performance data for capacity
planning
• Control access for both individual users and
user groups
• Provides interface to integrate with OSS
applications

23 Nuera Element • Client/server architecture

Management • Java-based architecture
System
• API-OEM ready
• Audit logging
• Multilanguage support ready
• Open solutions environment
• Operator individual views and profiles
• Supports gradual network deployment

24 OccamView • Carrier class management

Element • Fault management
Management
System • Event management
• Configuration management
• Performance monitoring
• Inventory management
• Root cause analysis
 What Is EMS?  ◾  15

Table 1.1  Some Popular EMS Products (Continued)

No Product Key Features

• Security
• Service activation
• Service level agreements

25 Prizm Element • Radio-level authorization and authentication

Management • Bandwidth management
System
• Tiered services
• Standards-based system integration

26 ProVision • Supports multiple devices

Element • Choice of Windows or Unix hardware platform
Management
System • Easy to install, learn, use, and administer
• Seamless integration with radio software and
onboard craft tools
• Circuit visualization and diagnostics
• Bulk software downloads
• License management
• Network inventory reporting
• Ethernet performance monitoring

27 RADview-EMS • Scalable management system

• Interface for integration with third-party NMS and
systems
• Enhanced fault management capabilities
• Advanced security management functions
• Multiplatform, distributed element management
system

28 ROSA • Manages scientific Atlanta and third-party

EM—Element equipment
Management • Translates proprietary protocols to SNMP
System
• Highly reliable hardware and software solution
• Alarm notification with e-mail, pager, or SMS
• Easy to use, intuitive web browser interface

(Continued)
16  ◾  Fundamentals of EMS, NMS and OSS/BSS

Table 1.1  Some Popular EMS Products (Continued)

No Product Key Features

• Provides easy integration with multiple client

options
• Open standards-based interfaces
• Delivered with software already installed
• Software can be upgraded remotely over LAN/WAN
• Automatic remote backup and restore
• Dual temperature probes available as option

30 RetroVue • Status “Dashboard” UI

Element • Allows drilling down for detail
Management
System • Configuration management
• Web-based UI

31 SafariView • High availability

Element • Advanced functionality
Management
System • Fault management
• Configuration management
• Accounting management
• Performance management
• Security management
• Service/subscriber management

32 SkyPilot • Fault management

SkyControl • Configuration management
Element
Management • Performance management
System (EMS) • Security management

33 Sonus Insight • Ease-of-use for rapid service

Element • Provisioning
Management
System • User-friendly features
• Maintaining carrier-class reliability
• Advanced system security
• Seamless system integration
• Unlimited scalability.
 What Is EMS?  ◾  17

Table 1.1  Some Popular EMS Products (Continued)

No Product Key Features

34 StarGazer • Configuration and provisioning

Element • Integrated fault management
Management
System • Security
• Performance and usage data

35 StarMAX EMS • Fault management

• Configuration management
• Performance management
• Security management
• Bulk management operations support
• Service provisioning
• Telsima RMI bulk provisioning adapter

36 T-View Element • Field proven scalability

Management • Point-and-click graphical user interface
System
• Multilayer visibility
• Easy OSS integration
• Powerful bulk functions
• Secure operation
• Multiplatform support

37 TNMS from • High capacity and scalability

Siemens • Ergonomically optimized graphical user interface
• Integrated management for transport equipment
based on the technologies DWDM, SDH MSPP,
SAN, and IP
• Seamless integration of element-layer and
network-layer functionality
• Centralized monitoring and configuration of the
whole network
• End-to-end configuration management
• Automatic, manual, and hybrid routing
• Management of protected connections and
segments

(Continued)
18  ◾  Fundamentals of EMS, NMS and OSS/BSS

Table 1.1  Some Popular EMS Products (Continued)

No Product Key Features

• Subscriber management
• Scheduled data in-/export via XML-files
• Scheduled export of all logfiles
• Data export in standard SDF formatted file
• Standby-solution for the whole system CORBA-
based NML–EML interface (according MTNM
Model) for integration in umbrella management

38 Tekelec Element • Reliable, centralized solution

Management • Reduced operating costs
System
• Scalable
• Automated alarm system
• Customized event viewing
• Advanced network mapping
• Smart agents
• Custom interfaces

39 Tellabs 1190 • Simplified provisioning through a graphical user

Narrowband interface
Element • Auto-discovery of network inventory
Management
System • Complete fault detection, isolation, and correction
• Performance monitoring
• Configuration, alerts, collection, and storage
• Remote software download and remote backup
and restore

40 Total Access • Intuitive, user-friendly configuration and

Element management GUI
Management • Automatically discovers ADTRAN devices
System from
ADTRAN • Stores performance information
• Real-time and historical trend analysis and reporting
• Scalable architecture, multiuser system

41 Tropos Control • Configuration

Element • Network monitoring
Management
System • Network health
 What Is EMS?  ◾  19

Table 1.1  Some Popular EMS Products (Continued)

No Product Key Features

42 Verso Clarent • Browser-based easy configuration

Element • Configuration and process management
Management
System • Real-time command center and call control
monitoring
• Supports C5CM associations with third-party edge
devices
• Multiple levels of user access permissions
• Subscriber portal providing subscribers
• Secure socket layer encryption
• Standardized interfaces: SNMP, XML, JDBC

43 Visual Guardian • Fault management

Element • Service provisioning
Management
System • Manufacturing
• Performance management
• Preventive maintenance

architecture. The need for element management systems and the characteristics
of an ideal EMS is covered. To give the reader familiarity with the EMS products
and functionalities, a data sheet is also provided that shows some of the leading
EMS products and their features. The information provided in the data sheet can
be obtained from the company Web site that will give more information on the
products.

Additional Reading
1. Vinayshil Gautam. Understanding Telecom Management. New Delhi: Concept
Publishing Company, 2004.
2. James Harry Green. The Irwin Handbook of Telecommunications Management. New
York: McGraw-Hill, 2001.
3. Kundan Misra. OSS for Telecom Networks: An Introduction to Network Management.
New York: Springer, 2004.
References

34 Chapter 34 Report: NGNM Framework and

Adoption Strategy

1. ITU-T SG4: M.3060 (Principles for the Management of Next

Generation Networks).

2. 3GPP specification 3gpp TS 32.111-2: Telecommunication

management; Fault Management; Part 2: Alarm Integration
Reference Point: Information Service (IS).

3. 3GPP specification 3gpp TS 32.409: Telecommunication

management; Performance Management (PM); Performance
measurements IP Multimedia Subsystem (IMS).

4. TR133-NGN Management Strategy: Policy Paper and

associated Addenda, Release 1.0 of TeleManagement Forum.

5. Venkatesan Krishnamoorthy, Naveen Krishnan Unni, and V.

Niranjan. Event-Driven Service Oriented Architecture for
an Agile and Scalable Network Management System. In
Proceedings of the 1st International Conference of Next
Generation Web Services Practices. Seoul, Korea, August
2005.

6. Matt Welsh, David Culler, and Eric Brewer. SEDA:

Architecture for Well-Conditioned Scalable Internet
Services. In Proceedings of the 18th Symposium on Operating
Systems Principle, Alberta, Canada, October 2001, pp
230–45.

7. Andreas Hanemann, Martin Sailer, and David Schmitz.

2004. Assured Service Quality by Improved Fault
Management. In Proceedings of the 2nd International
Conference on Service Oriented Computing, New York, 2004.

8. Boris Gruschke. Integrated Event Management: Event

Correlation Using Dependency Graphs. Proceedings of the
9th IFIP/IEEE International Workshop on Distributed
Systems: Operations and Management, Newark, DE, October
1998, pp 130–41.

9. Zeng Bin, Hu Tao, Wang Wei, and Li ZiTan. A Model of

Scalable Distributed Network Performance Management. In
Proceedings of the International Symposium on Parallel
Architectures, Algorithms and Networks (ISPAN 2004).

10. Jean Phillippe Martin Flatin, Pierre Alain Doffoel, and

Mario Jeckle. Web Services for Integrated Management: A
Case Study. In Proceedings of the European Conference on
Web Services, September 27–30, 2004.