|
|
article page | 1
| 2 | 3 |
introduced and updated beneath
it; yet all the while ensuring
the entire system still works together.
Standards bodies, primarily the
TMF, are helping to solve the problem
by providing interface standards
for EMSs such as MTNM (Multi-Technology
Network Management) and MTOSI (Multi-Technology
Operation System Interface). However,
we termed this a “NOS”
and not just an “EMS”,
“interface” or “API”,
because it not only provides a
stable environment and single point
of integration that uses these
standards-based Northbound interfaces
into the upper layer OSS/BSS systems;
but it also touches the NEs directly
Southbound and includes key applications
such as auto-discovery of their
physical and logical topology,
inventory, and fault information.
|
|
...The
NOS must have the ability to work
with multiple vendors’ network
equipment, to incorporate EMS functionality,
and to be customizable to incorporate
new network types or vendor-specific
features. |
|
market share and bring in
the new revenues that are
critical to success. In the
new world beyond Quad Play,
where product marketing creates
innovative and complex "blended"services
in which voice, TV, mobile,
and data services start to
interact with each other,
the risks and costs of delays
greatly increase. Having
separate "stove-piped" management
systems for each service and network
element is no longer financially
viable, and may not even be technically
possible to continue. The introduction
of a NOS into a service provider
enables incremental services
|
|
|
| |
To accomplish this, the NOS must have
some key characteristics that include
the ability to: work with multiple
vendors’ network equipment, to
incorporate EMS functionality (through
tool kits or standard interfaces such
TL1, SNMP, MTOSI) and to be customizable
to incorporate new network types or
vendor-specific features. Like any
OS at the heart of a system, it must
work reliably and –
importantly for CSPs, it must also
be able to grow and scale over
time and conform to open standards
initiatives such as the TMF’s
NGOSS, eTOM, and SID. With a NOS
in place, a Service Provider is
better equipped to retain and build
a differentiated service offering
in the market and will be ready
for their move beyond Quad Play,
keeping services affordable over
time, while deriving the follow
three key benefits:
1. Speed to market – roll
out new services faster
How often have new service launches been delayed or not worked as predicted?
CSPs need to launch new services at least as fast as their competitors do in
order to gain
|
|
and network equipment to be added
much more easily. It overcomes the
issue of deploying new NEs each with
their own vendors’ EMS, which
then need to be integrated to the
OSS to deliver new services. If the
NOS is already aware of the NE and
has an “adaptor” or
“driver” for it, then
there may even be no integration
required at all.
2. Reduced Opex Costs
Critical to long-term viability of
any service is that there is a
constant reduction in the costs
of running and maintaining it.
This applies even more so to Quad
Play and beyond as unit prices of
services are reduced. Tier-one
service providers estimate that
it normally takes several months
and costs $1-3 million to integrate
each new network element type or
EMS into their back office systems.
As discussed,
a NOS would not only reduce the amount
of time it takes to deploy new
NEs, but it could also reduce or
eliminate
|
article page | 1 |
2 | 3 |
|
|
|
