26.09.2012 Views

Triple-Play Service Deployment

Triple-Play Service Deployment

Triple-Play Service Deployment

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

16<br />

<strong>Triple</strong>-<strong>Play</strong> <strong>Service</strong> Delivery over Ethernet Networks<br />

Ethernet Networks: Carrier-grade requirements<br />

Ethernet is widely accepted as a cost-effective, resilient, and<br />

scalable switching and transport technology. It facilitates the<br />

availability of affordable bandwidth on demand and highly secure<br />

private network communication. Yet despite the lucrative and<br />

strategic advantages it brings, many providers are reluctant to<br />

embark on full implementation to bring carrier-grade Ethernet<br />

offerings, such as triple-play services, to market.This is due, in part,<br />

to the inherently greater complexity of maintaining carrier-class<br />

quality-of the services (e.g., 99.999% reliability/less than 6 minutes<br />

of downtime per year), at the node and network levels, as these<br />

offerings bring about a number of technical and operational<br />

challenges. These challenges include:<br />

– Ethernet aggregation networks support services that have different<br />

characteristics and place different burdens on the network<br />

due to CoS treatments<br />

– Customer’s quality of experience (QoE) and associated QoS metrics<br />

are drastically different than those depicted for the traditional voice<br />

services<br />

– <strong>Deployment</strong> of these services takes place over a multitude of new<br />

and existing networks, topologies and transport technologies<br />

– Providers need to account for associated changes in responsibilities<br />

for support personnel implementing these services

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!