3. • Globalizations and Deregulation
• End-to-end service involves multiple
providers
• Demand for standards based
network and service management
(interoperability)
• Merge of telecom and datacom
• Need for Inter-working between
management protocols to provide end-
to-end management
• Evolution in protocols
o Need for flexible management
architecture
• Competition
• Time-to market for new services
• Need for sound (flexible)
architecture
• Focus on customer care (i.e., service
quality)
• Decreasing margins (do more with
less)
• Increase revenue (providing
high quality services) while
minimizing network operation
costs
TRENDS IN TELECOMMUNIATION
5. TMN supplies a model of logical layers that define or suggest the management level for
specific functionality.
• Business Management Layer
• Service Management Layer (CUCM, VSM)
• Network Management Layer (EPNM)
• Element Management Layer (EPNM)
• Network Element Layer (Switches, Routers, Servers)
TMN Logical Layer Model
6. Definition :
A TMN is a Protocol model defined by ITU-T for managing open systems in a
communication network. It forms a support network that interfaces to the
telecommunications (data) network to provide the means for transporting and
processing Operations, Administration, Maintenance, Provisioning, and
Management (OAM&P) information.
Telecommunication Management Network
Background :
Address the interoperability of multi-vendor equipment used by different service
providers and define standard interfaces
Provide a framework for telecommunications network and service management
Management goes beyond networks and network element to include managing
services provided by service providers as well as business management
7. • NEL
The NEL presents the TMN-manageable information in an individual NE.
Both the Q-Adapter, which adapts between TMN and non-TMN information, and the NE
are located in the NEL.
TMN LAYERS
• EML
Manages each network element.
EML element managers, or OSs, are responsible for the TMN-manageable
information in certain network elements.
• NML
NML has visibility of the entire network, based on the NE information presented by
the EML OSs.
The NML manages individual NEs and all NEs as a group.
The NML coordinates all network activities and supports the demands of the SML.
8. • SML
• Uses information presented by NML to manage contracted service to existing and
potential customers.
• This is the basic point of contact with customers for provisioning, accounts, quality of
service, and fault management.
• The key point for interaction with service providers and with other administrative
domains.
• BML
• High-level planning, budgeting, goal setting, executive decisions, business level
agreements (BLAs), etc
TMN LAYERS (Contd.)
12. • Fault Management – Set of functions that enable detection, isolation and correction
of abnormal operation of telecom network.
• RAS quality assurance
• Alarm Surveillance
• Fault Localization
• Fault correction
• Testing
• Configuration Management- Provides functions to identify, collect configuration
data, exercise control over and provide configuration to network elements.
• Installation
• Service Planning and Negotiation
• Provisioning
• status and Control
• Accounting Management- Lets you measure the use of network resources,
determines cost to the service provider and charges to the customer.
FCAPS on OSI Management
13. • Performance Management – Provides functions to evaluate and report on
the behaviour of the equipment and effectiveness of the network and
network element.
• Performance quality assurance
• Performance monitoring
• Performance analysis
• Security management- Provides authentication, Access data
confidentiality, data integrity and non-repudiation.
FCAPS on OSI Management
16. 16
• IP routing can be partitioned into two broad categories:
• Static routing
• Dynamic routing
• Static routing (forwarding table is created before the system starts to forward
packets)
• and does not change entries, unless manually altering them
• In dynamic routing route propagation software runs on the system and
continuously updates the forwarding table
• to insure that each datagram follows an optimum route
• the software communicates with other systems to learn optimum routes to each
destination
• it continually checks for network failures that cause routes to change
• dynamic routing begins exactly like static routing
• by loading an initial set of routes into a forwarding table when the system boots
Static vs Dynamic Routing
18. • Metric based: There will be a segment underutilized
as you can see from the link cost. Traffic for the
different networks attached for E will always take
the same path. The bigger the network the more
the impact.
• Pattern unaware: Traffic patterns on the network
are not taken into account when the IGP calculates
it's forwarding table. Networks have different
custom needs which demand 'smarter' approaches.
• Lack of control: All traffic goes over the IGP path,
and if you change the metrics to adjust traffic over a
different route, you have just moved the problem to
another section of the network.
•Faster: This is more as a historical fact as
hardware and software have evolved greatly and
will continue to do. MPLS was originally designed to
make IP routers as fast as ATM switches for
handling traffic.
•Scalability: Service Providers can offer different
technologies like ATM, Frame Relay, Ethernet and
IPsec over the same infrastructure. Imagine the
nightware of the operational costs involved in
maintaining 4 different infrastructures.
•Traffic Engineering: MPLS uses signaling
protocols to distribute labels, and with RSVP you
can have more control on the information that is
accounted to route traffic and therefore have more
OSPF vs MPLS
19. Typical IGP Design in RVPNL Network
In a multiple-area IS-IS setup, IS-IS routers are classified as follows:
Level 1: L1 routers learn about paths within areas they connect to (Intra-area paths). L1 routers store L1 link state database (L1
LSDB). L1 routers use L1 / L2 routers (ABRs) to reach Inter-area routes. This is done via a default route injected by the ABR into L1
area.
Level 2: L2 routers learn about paths among areas (Inter-area paths). L2 routers store L2 link stat database (L2 LSDB).
Level 1 / Level 2 (like an OSPF ABR): L1 / 2 routers learn about paths both within and between areas. L1 / 2 routers store both L1
and L2 databases (L1 and L2 LSDBs). L1/L2 routers act as the gateway for L1 routers to reach Inter-area routes.
24. Video Management System
• The main objective of VMS is to implement surveilance solution to
monitor and manage mulitple locations from central location
• Cameras will be installed at DC, CCC, Backup CCC, Sub CCC & substation
connected to the CCTV network by the appropriate feasible last mile
connectivity media. These cameras will be connected to an aggregation
switch which will be housed in a weather proof junction box with power
backup.
25. Video Management System
• The datacenter infrastructure design consists of Video Management
Systems which will operate, monitor, control, record video from different
CCTV cameras from location site and remote substations. The system
consists of 2 nos. of video management Systems with adequate storage.
• Total No. of Cameras-
• Fixed cameras- 118; PTZ cameras- 83
• Storage configured with following parameters:
• Bit Rate- 7 Mbps ; FPS- 30 ; 30 days , 24 Hours continuous recording
S.no
Camera
Quantity
No of days
recording
Recording
hours per day
Compression
mode
Resolution FPS
Total Storage in
TB
1 118 30 24 H 264 1080 P 30 248.3
2 83 30 24 H 264 1080 P 30 174.6
Total Storage 423
27. MULTICAST
Source transmits one stream of data
for n receivers
Replication happens inside routers
and switches
WAN links only need one copy of the
data, not n copies.
VMS- Communication Overview (MULTICAST)
• Same data sent to multiple receivers
• To use the bandwidth efficiently
• Reduce routing processing
• Sender doesn’t get receiver’s address
28. Why Multicast required
ConferenceXP: An Example of Multicast application
Video Conference
Distance Learning
• Video/audio conference
• IP TV, Video on Demand
• Advertisement, Stock, Distance learning
30. • The Business edition 7000M
consists 2 nos. of Call
Managers for High availability.
All the IP phones are
registered with Call manager.
• Primary line (E1) terminate in
voice gateway, need to create
a sip trunk between gateway
and call manager.
• External incoming and
outgoing call are routed to sip
trunk, outgoing calls will
restricted to particular users.
UCM Solution Deployment
