Carrier Ethernet Transport in Metro and Core Network T7_Gruber_Autenrieth

8/3/2019 Carrier Ethernet Transport in Metro and Core Network T7_Gruber_Autenrieth

1/130

1 Nokia Siemens Networks

Carrier Ethernet Transportin Metro and Core Networks

Tutorial by

Claus G. Gruber and Achim AutenriethNokia Siemens Networks

13th International Telecommunications Network Strategy and PlanningSymposium - Convergence in Progress Networks 2008

September 28 October 2, 2008Budapest, Hungary


2/130

Claus G. Gruber, Achim Autenrieth, {claus.gruber,achim.autenrieth}@nsn.com2 Nokia Siemens Networks 2008/09/29

Networks 2008 - Carrier Ethernet Transport in Metro and Core Networks

About Us

Dr.-Ing. Claus G. GruberClaus Gruber is senior consultant and project manager at Nokia Siemens Networks, Munich,

Germany. Division: Research Technology and Platforms, Network Technology, Network Control and

Transport (RTP NT NCT). His main area of research focuses on next generation packet network

architectures including Carrier Grade Ethernet and IP/MPLS over WDM. He is mainly interested in

networking concepts, total cost of ownership, multilayer traffic engineering and resilience, control

plane, and network management and configuration of ubiquitous communication technologies.Prior to his work at Nokia Siemens Networks he was a member of the research and teaching staff at

Technische Universitt Mnchen (TUM), Germany, where he received his Dr.-Ing. and Dipl.-Ing.

degree in electrical engineering and information technology.

Claus published about 30 articles in journals and conference proceedings and submitted about 20

invention reports in the area of routing, resilience, network planning, optimization and management

that are currently under review at EU and US patent offices.

Dr.-Ing. Achim AutenriethAchim Autenrieth is Head of IP Transport R&D Management Innovation (IPT RD Innovation) at Nokia

Siemens Networks, Munich, Germany. Focus areas of his work are multilayer transport networks

(OTN/DWDM, SDH/SONET, Ethernet/MPLS-TP, IP/MPLS), control plane protocols (ASON/GMPLS),

network architecture evaluation, multilayer resilience and multilayer network design, routing and

grooming.

Prior to his current responsibility he was working as project manager and senior research scientist in

internal innovation projects and funded research projects at Siemens AG, Corporate Technology and

Siemens AG, Fixed Networks.

Achim studied Electrical Engineering and Information Technology at the Technische Universitt

Mnchen (TUM) and received his Dipl.-Ing. and Dr.-Ing. degree in 1996 and 2003, respectively. From

1996 to 2003 he was member of the research and teaching staff at the Institute of Communication

Networks at TUM.


3/130



General Information

Schedule

9:00 10:30 Tutorial Part I

10:30 11:00 Coffee Break

11:00 12:30 Tutorial Part II To ensure proper knowledge transfer to the audience, some basic behavior

rules should be strictly obeyed during the tutorial

Q&A After each main section


4/130



Contents

1. Introduction

2. Operator Requirements for Transport Networks

3. Ethernet Basics

4. Carrier Ethernet Evolution

5. Carrier Ethernet Transport Technologies

6. Carrier Ethernet Transport Network Architecture & Solutions

7. Outlook Towards Future Internet Architectures

8. Conclusion


5/130



Networks get run over by a huge traffic growth -

Technology innovation is a must on the way forward

The fastest and most costefficient access technologies

are not sufficient on their own

Huge traffic volumes have tobe transported throughout

the network

Data super highways and anoptimized end-to-endtransport are needed toconnect 5bn people

5 billion peopleconnected


6/130



Challenges and Opportunities

100x trafficgrowth

User serviceexperience

Add valuebeyond bit-pipe

Reinventing theconnected world

EnvironmentalPerformance

Internet for

the next billion

5 Bn people

connected


7/130



Tomorrow's communication world

5 Bn Peopleconnected

Main growth in mobilesubscriptions from newgrowth markets

Majority can be alwaysonline via mobilehigh-speed Internetaccess technologies

Wireline Broadband willfacilitate usage ofapplications like TVand/or video streaming.

4 Bn mobileusers

2 Bn fixedbroadband users

Source: Nokia Siemens Networks estimations based external forecasts (Ovum, Strategy Analytics)

xDSL

FTTx

cable

20152005 2010

0.2 Bn

0.4 Bn

0.6 Bn

0.8 Bn

fixedWiMAX

* Broadband subscriptions are typically shared by 2-3 people

5 Bn

4 Bn

3 Bn

2 Bn

2 Bn

20152005 2010

Voice and

high-speedInternet enabled(EDGE, HSPA, ... ,

LTE, WiMAX)

Voice andlow-speed Internet enabled

Mobile Users Worldwide

Fixed Broadband Subscriptions* Worldwide


8/130



Broadband services drive transport network

evolution

Cost of data transportmust go down

Optical Metro

Rural connectivity

Photonic core

Operators investinto the whole network

Enable next generation ofconnectivity

Transport investment

worldwide

ConsumersQuality of lifefor citizens

BusinessGrowth andefficiency

GovernmentProductivity

Source:ConnectivitySco

recard

Higher network efficiency

One technology

Leased Line OPEX

Profitable self builtRevenues

Traffic

VoiceDominant

DataDominant

2007 2011

CAGR7,7%

Broadband enabled network


9/130



In the year 2012, there will be more than500 million Broadband subscribers worldwide

Most subscribers will use a DSL connection

Fiber access subscription is expected to grow inline with IPTV subscription

2006 2008 20102012

100

200

300

400

500

600Million

subscriptions

(world)

Fiber to the building/homesubscription

DSL Subscriptions

IPTV/VoD Subscriptions

Cablemodem Subscriptions

Total Broadband Subscriptions

Demand for fixed broadband will increase

over the next years

Source: internal research based on several analyst forecasts

Total Broadband Access Market World[bn ]

1,1 0,9 0,9 0,8

2,9 2,8 2,9 3 3,1

1,0 1,5 1,82,1

2,3

1

5,0 5,3

6,25,95,6

2006 2007 2008 2009 2010

5.0%

6.4%

DSL is the dominant broadband market and willremain

Driven by high bandwidth demand, fiber basedaccess revenue will double in the next 10 years

Narrowband revenue will decrease

Source: internal research based on several analyst forecasts

total

Fiber access

DSLAM

Narrowband

5 billion peopleconnected


10/130



100x traffic growth within 5 years means

a growing need for scalable networks

Growing #of customers

Business

New services at

lower cost

Growing #of services

Consumer

Consumer


11/130


12/130



Video and TV services as main driver

Video Services will driveexponential growth in residentialwireline traffic, ... with most growthfrom IPTV

20100

10 ExaByte

20 ExaByte

30 ExaByte

40 ExaByte

50 ExaByte

60 ExaByte

70 ExaByte

2008

230%230%

2009

530%530%

2007

100%

100%

100%

100%

2011

1600%

220%

1500%

1600%

220%

1500%

1100%

820%

200%

1100%

820%

200%

TV Services

(unicast&broadcast)

P2P Video*

Streaming Video Clips

US residentialWireline Video related Traffic

Source:

Heavy Reading, June 2007, Internet TV, OTT Video & Future of IPTV

* excluding P2P video andmusic exchange whichdominate currently the Internettraffic


13/130



Increasing bandwidth demands require asimplified and more efficient infrastructure

Technology goes highestscalability and flexibility

Operators go Ethernet

Source:Conferences;Lightreading

2007

Up to 100Gbit/s channelsin the core

Flexible Gigabit services &

multi-Gigabit wavelength

switching

Ethernet switching @ all

transport technologies

Microwave Radio, NG SDH,

DWDM, Carrier Ethernet

Level 3:Ethernet is becoming a

preferred enabler for leading

applications, e.g. Internet,

Content delivery, utility

services, IP video,

FT, Telefonica:IP does not scale enough,

Ethernet is an alternative


14/130



The broadband telecommunication environment

is enabled by next generation connectivity

Megabit applications -Gigabit services

Broadband accesseverywhere

Reliable and securetraffic control

Flexible bandwidths

from access to core

Optimized connectivityin fixed and mobile environment

Solutions to balance networks

and ensure Quality of Service

Carrier Ethernet Transport


15/130



Contents

1. Introduction


3. Ethernet Basics





8. Conclusion


16/130



What is Carrier Ethernet Transport ?

In a sentence Ethernet with Carrier Grade qualitiesfor Transport Networks

But seriously

Taking the simple, well known and widely deployedEthernet service and extending it to the metro and

core of public networks thus maintaining the

simplicity, flexibility and cost effectiveness of the

protocol and components on an end-to-end basis


17/130



Carrier Ethernet Transport technology

is defined by six key attributesEnd to End Ethernet

Seamless Ethernet across portfolio of

IP Transport/Nokia Siemens Network

Differentiated service creation

Resiliency Connection Oriented Ethernet

50ms protection

Resilient IP (ResIP)

certification

Simple Management Automation of network

Point and click provisioning

Standard Operation and

Maintenance

Optimized Deployment Scalable architecture with

end to end portfolio

Technology agnostic multi-

layer optimization

Flexible Solutions Integrated Solution for

Mobile Backhaul, Business

and residential services

Shared best practices

Scalability Standardized platforms

Prove worldwide

deployment

Over 20,000 service and

support personnel


18/130



Connection

Oriented

Packet Based Service

Transparent

Deterministic Controlled

Carrier Ethernet Transport Defined

Architecture Goals and Building Blocks

Enable IP Services over a Converged Carrier Class Transport Architecture

Add Scalability, Resiliency, and Manageability to Ethernet

Multi-Service

Convergence

Static

Managed

Isolated

Secure

Predictable

Protected

Guaranteed

SLA

Point-and-Click Provisioning

Carrier Grade OAM High Reliability

Hard QoSStratum Quality Sync

Integrated TDMHigh Scalability


19/130



Unified Architecture for Cost-Effective

Transport of High-Speed Packet Services

Carrier Ethernet Transport Defined

Fundamental Requirements

Connection

Oriented

Provisioned

Deterministic

Predictable

L3 Service

Transparency

Guaranteed

SLAs

Carrier Class

Resiliency

Multi-Layer

Service

Management

L2 ClientEncapsulation

SecureTransport

L3 Proxy

Provisioned

Strict QoS

ConnectionAdmission

Control

NE Quality

SW Stability

NetworkProtection

End-to-End

Pt-and-Click

Control Plane

Robust OAM

Reporting

Ethernet

Economics

Scalable

Multi-Service

Single UNI

Synchronous

Cost-Effective


20/130



Contents

1. Introduction


3. Ethernet Basics





8. Conclusion


21/130



Contents

1. Introduction


3. Ethernet Basics

Network Basics





8. Conclusion


22/130



Going Back to Where It Began

We have to go back to 1984


23/130



Network Hierarchy ConceptThe OSI Reference Model

Layer

Layer

Layern-1

n

n+1

Provides services to higher layers

with standardized interfaces

Uses services of lower layers

with standardized interfaces

The concept of layers

It is a simple and efficient way of communication


24/130




Application

Presentation

Session

Transport

Network

Data Link

Physical1

2

3

4

5

6

7 The OSI reference model provides:

Standardized interfaces

(compatibility, interoperability and competition)

Simplifies network technology development

considerably

(just trust and use the functionality of the lower layer)

Why seven layers?

Is an often discussed question

(e.g. Three layer approach of Future Internet projects)


25/130




Application

Presentation

Session

Transport

Network

Data Link

Physical1

2

3

4

5

6

7

Binary transmission on a physical linkElectrical, mechanical, procedural, and functional specification

Access to media

Defines the data format and how the access to the media is controlled(includes bit-error correction)

Data deliveryProvides routes between two host systems (might be at different locations)

(includes network discovery and routing decision)

End-to-end connection

Ensures data transport reliability, information flow(includes maintaining of virtual circuits between hosts)

Interapplication communicationMaintains sessions between applications

Data presentation

Presents data in the right format to the application layer(includes encryption, reformating, restructuring of data)

Network service part of applicationsProvides network services to applications

(e.g. protocols to applications such as snmp)

What we call applicatione.g. email client such as Thunderbird RealApplication8

The User9


26/130



Network Hierarchy ConceptData Encapsulation

Application

Presentation

Session

Transport

Network

Data Link

Physical1

2

3

4

5

6

7

HeaderHeaderHeaderHeaderHeaderHeader

HeaderHeaderHeaderHeaderHeader

HeaderHeaderHeaderHeader

HeaderHeaderHeader

HeaderHeader

Header

DataHeader

DataHeader

DataHeader

DataHeader

DataHeader

DataHeader

DataHeader


27/130



Network Hierarchy ConceptCommunication

G

F

E

D

C

B1

A11

2

3

4

5

6

7 G

F

E

D

C

B2

A21

2

3

4

5

6

7

C

B1

A11

2

3

B2

A2

Only instances

of the same layer

can talk to each other!

IntermediateSystem (IS)

End System 2End System 1


28/130



Sample OSI Layer Protocols and Services

SDH, OTH,

optical frames

Bits Bits1Physical

SDH, OTH

optical frames

SDH, OTH

optical frames

Frames

Packets

Frames2Data Link

IP3

Network

TCP / UDP4

Transport

5

Session

Services e.g.:

MIDI, HTML, GIF

JPG, ASCII

Services e.g.:

MIDI, HTML, GIF

JPG, ASCII

6

Presentation

End SystemServices e.g.:

FTP, HTTP,

Telnet

Services e.g.:

FTP, HTTP,

Telnet

OSI Layer

7

Application

Ethernet

(IEEE 802.1),

LLC, MAC, ATM

Ethernet

(IEEE 802.1),

LLC, MAC, ATM

Ethernet

& IEEE 802.3,

LLC, MAC, ATM

Packets

Packets

IPIP

Datagram

Datagram

Transit System

Messages / Data

TCP / UDP

Services e.g.:

MIDI, HTML, GIF

JPG, ASCII

Services e.g.:

MIDI, HTML, GIF

JPG, ASCII

End SystemServices e.g.:

FTP, HTTP,

Telnet

Services e.g.:

FTP, HTTP,

Telnet

Transceiver

Repeater

Hub, Cable

Bridge

Switch

Router

Gateway

Gateway

Gateway

Equipment

Gateway

e.g. Security

(Firewall, Proxy)

e.g. Security

(Firewall, Proxy)

Servic

es

Protocols

Information unit Information unit

Specification


29/130



Network HierarchyAccording to OSI Reference Model

NSN Location

Munich

NSN LocationEspoo

Routers are used to connect networks

Switches are used to connect hosts

Backbone Network A

Backbone Network B


30/130



Fixed Transport Network Structure

Optical

Transport

FixedServices

Access

IP

Edge CoreAggregation

Routing

Applications

CES

CLS

IP/MPLS

Core

Residential

Layer 2 VPN,

Ethernet /TDMLeasedLine

Business

Layer 1Optical/

WavelengthLeased Line

OTN/DWDM

Metro

OTN/DW

DM Core

HSI: High Speed Internet CIS: Customer IP service CES: Customer Ethernet Service COS: Customer Optical Service

MSAN: Multiservice access node (PON, DSLAM) CLS: Customer Legacy Services

Business

Voice,

Video,HSI MSAN

L3 VPN

Server

VoIP, VoD, IPTV,IMSIMS

L2 switch

BRAS

COS

CIS

CIS

L2

Transport

Carrier Ethernet /

SDH/SONETCarrier Ethernet /

SDH/SONET


31/130



Contents

1. Introduction


3. Ethernet Basics

Ethernet Standards





8. Conclusion


32/130



The original Ethernet

by Bob Metcalf

Bob Metcalf, 1973

The original format for Ethernet was developed in Xerox Palo Alto Research Centre (PARC), California in 1972

and called Alto Aloha. Using Carrier Sense Multiple Access with Collision Detection (CSMA/CD) it had a

transmission rate of 2.94Mb/s and could support 256 devices over cable stretching for 1km. The two inventors

were Robert Metcalf and David Boggs


33/130



Advantages of Packet and Ethernet Networks

Packet Almost 100% of traffic generated by applications is packet based Multiplex gain Control plane often deployed in combination with packet services (restoration)

Advantages of Ethernet Widely deployed The standard for LAN equipment (10M, 100M, 1G, 10G, 100G)) available in

almost every computing device Chipsets are very cheap and high numbers

Plug and play Very simple technology to operate

Combines data link layer and switching layer

Drawbacks of Ethernet:

MAC addressing scheme Different protocols (STP, RSTP, MSTP) Limited traffic-engineering and slow failure recovery Operation Administration and Maintenance


34/130



IEEE 802 Standards

IEEE 802.1 Architecture, management, switching

802.1D MAC layer bridges 802.1Q Virtual LANs 802.1p Quality-of-Service & Multicast support 802.1d Spanning Tree Protocol (STP) 802.1s/w Multiple STP / Rapid STP

IEEE 802.3 CSMA/CD (Ethernet) standards

802.3u Fast Ethernet (100Base-TX, 100Base-FX) 802.3x Full-duplex Ethernet over LAN

802.3z Gigabit Ethernet over fiber (1000Base-X) 802.3ab Gigabit Ethernet over copper (1000Base-T) 802.3ad Aggregation of multiple link segments (LAG)


35/130



Ethernet BasicsIEEE 802.3 Ethernet Interfaces

Older Ethernet Implementations:

10 Base 5 yellow cable / 10 Base 2 cheapernet

R

Typical Implementation:Busses / Segments

Disadvantage:Collisions

multiply when data loadIncreases

Current Implementations with electrical Interfaces:

10 Base T

100 Base T Fast Ethernet

1000 Base T Gigabit Ethernet

100 Base FX Fast Ethernet

Current Implementations with optical Interfaces:

1000 Base SX Gigabit Ethernet

1000 Base LX

10 Gigabit-Ethernet In optical Ethernets,Collision detection is not possible

Data Link

Network

Transport

Session

Presentation

Application

Physical

Typical Implementation:

Point-to-PointAdvantage:

Collisions can be minimized

with a switch


36/130


37/130

Eth t B i


38/130



Ethernet BasicsEthernet Switching (1)

A B C D E F

1 2 3 4 5 6

FCAddress

Port 6Port 5Port 4Port 3Port 2Port 1MAC-Table

A C

C ?

A

MAC-Learning

Eth t B i


39/130



Ethernet BasicsEthernet Switching (2)

A B C D E F

1 2 3 4 5 6

FCAddress


A C

D ?

A

F D

Flooding

Eth t B i


40/130



In Ethernet networks loops are strictly forbidden because otherwise broadcast storms would

bring down the network performance. With Spanning tree protocol loops are avoided in an

Ethernet network: All links that would built up a loop are blocked by the Switches. So STP can

be used for protection: If the working link fails, the protection link (i.e. a blocked link) is activated.

Path 1 (working)

Ethernet Basics802.1d Spanning Tree (1)

active links

blocked links

Ethernet Basics


41/130



If the working link fails, the protection link (i.e. a blocked link) is activated. RSTP (Rapid

spanning tree protocoll) improves the switching time from several seconds to approximately

one second.

Path 2 (unblocked)

Path 1 (broken)

Ethernet Basics802.1d Spanning Tree (2)

802.1w Rapid Spanning Tree Protocol (RSTP)


42/130



802.1w Rapid Spanning Tree Protocol (RSTP)

1s~60sWorst Case

RSTPSTPTiming

Spanning Tree was designed for Enterprise. Recovery Time is not

acceptable for Carrier Grade.

Rapid Spanning Tree Protocol is identical to STP, except:

STP Learns the backup route after failure

RSTP Learns the backup route before failure

The convergence time is significantly shortened:

802.1s Multiple Spanning Tree Protocol (MSTP)


43/130



802.1s Multiple Spanning Tree Protocol (MSTP)

MSTP enables the use ofdifferent paths for differentVLANs (or groups of VLANs)

Traffic can be organized to useall possible links, optimisingtraffic distribution

If a link fails, only the MSTIs(MSTP Instances individualtrees) using that link areaffected

MSTP only works together withRSTP

Up to 32+1 instances per node

VLAN 10

VLAN 20

Advantages

Efficient VLAN Paths(e.g. SW 1 => SW 4)

Load-sharing

SW 3

SW 2 SW 4

SW 1

Ethernet Basics


44/130



CFI

16 bit

TAG Protocol Identifier TPID0x8100

1 bit 12 bit3 bit

Priority VLAN ID

IEEE 802.3 Frame without VLAN Tag Header

Destinationaddress

Sourceaddress

Type /Length

Data CRC

IEEE 802.3 with 802.1Q 4-Byte VLAN Tag Header

TCITag Control Identifier

TPIDTAG Protocol Identifier

2 bytes2 bytes

Destinationaddress

Sourceaddress

TagType/8100

Data CRC

4 bytes

Ethernet Basics802.1Q VLAN support

802 1Q Highlights


45/130



802.1Q HighlightsCustomer separation by VLAN

Physical view

Logical view

S S

SR

R

VLAN Functionality Highlights

Up to 4096 VLAN

Priority 802.1p associated with VLAN

VLAN-based priority take precedence

Allows Spanning Tree per VLAN

Allows overlapping VLANs

VLAN Advantages

Better security

Solve the broadcast problem

Solve the physical location issue

Ethernet Basics


46/130



A B C D E F

Ethernet BasicsEthernet VLANs (1)

A DB D

A

EDBVLAN 1

FECVLAN 2


1 2 3 4 5 6

?

Ethernet Basics


47/130



Ethernet BasicsEthernet VLANs (2)

A B C D E F

1 2 3 4 5 6

EDBVLAN 1

FECVLAN 2


A

X

A DB D

Contents


48/130



Contents

1. Introduction


3. Ethernet Basics





8. Conclusion

Evolution of Ethernet Hierarchy


49/130



Evolution of Ethernet Hierarchy

DA

SA

Pay

load

802.1D

DA

SA

Pay

load

VID

802.1Q

SA: Source MAC Address

DA: Destination MAC AddressVID: VLAN ID

C-VID: Customer VID

S-VID: Service VID

VID: VLAN ID

B-SA: Backbone SA

B-DA: Backbone DA

B-VID: Backbone VID

B-TAG: a Provider Bridge S-TAG

I-SID: 24 bit Service ID

I-TAG: allocated for 802.1Q service instance

B-VID VLAN identifies per destination

alternate path

B-DA MAC identifies destination node

B-SA MAC identifies source node

DA

SA

Pay

load

S-VID

C-VID

802.1ad

Q-in-Q

DA

SA

Pay

load

S-VID

C-VID

B-DA

B-SA

B-VIDI-SID

802.1ah

Mac-in-Mac

Service IDBackbone VID

Backbone MAC

Provider

Backbone

Bridges

PBB

Standard

Ethernet

Frame

acc.

IEE 802.3

Inner VLAN ID

Outer VLAN ID

Customer MAC

Contains IP

packet

VLAN

PBB-TE

Provider

Bridges

VLAN XC:

based on

VLAN ID

802 1ad Provider Bridge (Q-in-Q)


50/130



Frame with double VLAN tag header 802.1ad

The Concept Adding another layer of 802.1Q

The purpose - expanding the VLAN space by tagging the tagged packets

The expanded VLAN space allows the service provider to provide certain services, such as

Internet access on specific VLANs for specific customers, and yet still allows the service

provider to provide other types of services for their other customers on other VLANs.

802.1ad Provider Bridge (Q-in-Q)

S-VLAN

Frame without VLAN Tag HeaderDestination

addressSourceaddress

Type /Length Data CRC

Frame with single VLAN tag header 802.1QDestination

addressSourceaddress C-VLAN


Destinationaddress

Sourceaddress C-VLAN


Support of 4K S-VLAN x 4K C-VLAN = theoretical 16 Mill VLAN

Transport of Ethernet Services


51/130



Transport NetworkTransport Network

pIssues with Flat Ethernet Architecture

Full transparency ?

Use ofclient information as forwarding decision ?

Learning of all client MAC addresses in all transport nodes ?

Known issues with STPissues with STP (resilience and traffic engineering)

TPI

D

S-

VID

S-

VID

TP

IDC-DA C-SA L/T User Data FCS

802.1ad

Frame

6 octets 6 octets 2 2 2 2 2 4 octets46 1500 octets

S-TAG C-TAG

C-DA

802.1ah Provider Backbone Bridging (PBB)


52/130




Adding a Transport Hierarchy

Source: D. Allen, N.Bragg, A. McGuire, A. Reid, Ethernet as Carrier Transport Infrastructure, IEEECommunications Magazine, Feb. 2006

TPI

D

S-

VID

S-

VID

TP


802.1ad

Frame


S-TAG C-TAG

TPID

B-TAG

ES-VIDB-DA B-SA B-VID L/T 802.1ad Frame(/w or /wo FCS) FCS

Backbone

ProviderBridge

Frame 6 octets 6 octets 2 2 2 4 octets60 1526 octets

Add a transport hierarchy MAC in MAC encapsulation No learning of customer MAC addresses in the middle of the network Transport spanning TREESTREES instead Use globalglobal meaning of tag (B-DA (48 bit) and B-VID (12 bit))

C-DAB-DA

802.1ah Provider Backbone Bridging


53/130



PBB, MAC in MAC

Interconnect Provider Bridge networksthrough a highly scalable Ethernet

backbone

MAC in MAC encapsulation Encapsulation at the backbone edge Providers MAC and VLAN space, isolates

provider from customer broadcast domains

Core is agnostic to customer MAC andcustomer services

MAC tables are learned automatically,xSTP prevents loops

Drawbacks Lack of carrier grade protection

(xSTP based) Lack of effective traffic engineering

Provider Bridging nw

Customer networks

Provider Backbone Bridging network

Provider Bridging nw

PayloadC-VID

S-VID

SA

DA

802.1ad

Payload

C-VID

S-VIDSA

DA

I-SID

B-VID

B-SA

B-DA802.1ah

Q-in-Q

Customer MAC

OAM for Carrier Grade Switches


54/130



OAM is the carrier tool kit for the network management functions suchas fault indication, performance monitoring, security management,

diagnostic functions and configuration

An advanced management tool kit contains:

Transport link level

Network & Service

Level

OAM management

802.3ah802.3ah EFMEFM

(Ethernet at the first mile)(Ethernet at the first mile)

802.1ag802.1agConnectivity Fault ManagementConnectivity Fault Management

VLAN OAMVLAN OAMMEF recommendationMEF recommendation

Element Manager SystemElement Manager System

MPLS OAMMPLS OAM

Advanced Ethernet Features


55/130



QoS allows to guarantee parameters like

- Bandwidth

- Packet loss rate

- Maximum delay

- Maximum jitter

Examples of typical service class definitions:

- Gold: Guaranteed Bandwidth, very low packet loss rate,Minimum jitter suitable for VoIP and Video Boadcast

- Bronze: No guarantees suitable for Data transmission(data packets can be re-transmitted in case of loss)

- Network Most important traffic, highest priority

Control:

Quality of Service - QoS (1)



56/130



CIR: Committed information rate

PIR: Peak information rate CBS: Committed burst size

PBS: Peak burst size

Service End-to-End

CIREIR

t

Bandwidth available to other services

at time t

Link Capacity

Quality of Service - QoS (2)



57/130



Waste

Packet stream (one direction)

High priority packet

Medium priority packet

Low priority packet

Egress buffersFor one egress port

Many Low priority packets aredropped,Few medium priority,None high priority.

+

The critical point in the packet flow

is the summarization of several ingress portsto one egress port.Therefore one egress buffer per service classis required. In this buffers high priority packetscan overtake low priority packets.

Packet classification Packet scheduling

Ingress ports Egress port

SLA Guarantees for all Services

Contents


58/130



1. Introduction


3. Ethernet Basics




7. Outlook Towards Future Internet Architectures8. Conclusion

Connectionless and Connection Oriented Transport


59/130



Connection oriented

A predetermined path is used between

two end nodes for packets of the same

service

Bandwidth reserved End-to-End to

ensure quality

Protection paths are preset and

available for immediate usage

BW for protection can be reserved in

advance

Known path allows more E2E OAM

capabilities

The OSI 7-layer model specifies two methods for packet transport:

Connectionless

Every packet can be taken at any path

as long as it gets to its final destination

Service BW can not be guaranteed

In case of failure nodes are required to

re-calculated path which may take longtime

No constant End-2-End monitoring

Primary path

Backup path

Carrier Ethernet (cl) vs.Carrier Ethernet Transport (co)


60/130



Carrier Ethernet

Forwarding based on Spanning TreeSpanning Tree Inefficient use of resources

LimitedLimited traffic engineering possibilities

Very complex optimizationcomplex optimization tasks when using multiple trees SlowSlow restoration upon failures (seconds)

FlatFlat switching hierarchy (broadcastbroadcast if unknown)


Forwarding based on transport labeltransport label not on customer MAC address

Establishment ofvirtual tunnelsvirtual tunnels (paths)

Packets are tagged and switched accordingly

Broadcast if unknown is disabled (hierarchyhierarchy)

Centralized management ordistributed control planecontrol plane

(e.g. GMPLS)

Carrier Ethernet Transport (co)

Carrier Ethernet TransportTraffic Engineering and Resilience


61/130



Traffic Engineering and Resilience

Traffic Engineering can be done by applying tunnel characteristics

Route of tunnel can be optimized

MultipleMultiple tunnelstunnels and traffic distribution

Intermediate grooming and merging of tunnels

MultiMulti--layer traffic engineeringlayer traffic engineering especiallybetween Ethernet and WDM

Resilience mechanisms can be based on tunnels

A large number ofpathpath--basedbased resiliencemechanisms can be applied for Carrier Ethernet

ProtectionProtection and restorationrestoration

MultiMulti--layer resiliencelayer resilience optimization

Carrier Ethernet switches with c/o EthernetBenefits and features for packet transport


62/130



Benefits and features for packet transport

Features and Benefits

Advanced connection oriented Ethernet mechanisms

Well determined and predictable network operation

Advanded resilience mechanisms possible

Traffic engineering (Traffic separation per VLAN, Classification per port andport+VLAN ++, Policing, QoS (basic- , Diffserv-, Enhanced-mode),

horizontal split)

efficient use of fibers, balancing of the traffic load on various links in the

network

Challenges

Multicast: Interworking of IGMP and PBB-TE still to be verified

Synchronization and clock provisioning in mobile backhaul

Interworking with DWDM

Increased scalability and cost-efficient long-distance transport(Grey interfaces up to 80 km)

Contents


63/130



1. Introduction


3. Ethernet Basics



Ethernet Label Switching

6. Carrier Ethernet Transport Network Architecture & Solutions7. Outlook Towards Future Internet Architectures

8. Conclusion

Ethernet Label Switching (ELS) aka VLAN Cross-ConnectQ in Q Tunnelling (IEEE 802 1Q IEEE802 1ad)


64/130



Q in Q Tunnelling (IEEE 802.1Q, IEEE802.1ad)

Idea: Use the existing Ethernet header(802.1ad) but forward according toingress port and VLAN-ID, not MACaddress

Add tags if required (label stacking) Forwarding decision based on

single VLAN-ID (12 bit) ordouble VLAN-ID (24 bit) with local linkscope (16M connections per port)

Replacing Flooding and MAC Learningwith configuration of VLAN-Switching

Cross Connect1

2

4

3

Bridge

5VID = 10

7

8

6VID = 10

VID = 50

VID = 10

VID = 50

VID = 11

VID = 20

VID = 17

VID = 17

VID = 50

VID = 10

VID = 72

VID = 50

TPI

DVIDVID

TP

IDDA SA L/T User Data FCS

6 octets 6 octets 2 2 2 2 2 4 octets

TAG1 TAG2

VIDTP


802.1Q

Frame

6 octets 6 octets 2 2 2 4 octets

TAG

802.1ad

Frame

Single Tag

Double Tag

Contents


65/130

Claus G. Gruber, Achim Autenrieth, {claus.gruber,achim.autenrieth}@nsn.com65 Nokia Siemens Networks 2008/09/29Networks 2008 - Carrier Ethernet Transport in Metro and Core Networks

1. Introduction


3. Ethernet Basics



PBB-TE

6. Carrier Ethernet Transport Network Architecture & Solutions7. Outlook Towards Future Internet Architectures

8. Conclusion

802.1ah Provider Backbone Bridging (PBB)Adding a Transport Hierarchy


66/130



g p y


TPI

D

S-

VID

S-

VID

TP


802.1ad

Frame


S-TAG C-TAG

TP

ID

B-TAG

ES-VIDB-DA B-SAB-

VID L/T802.1ad Frame

(/w or /wo FCS) FCS

Backbone

Provider

BridgeFrame 6 octets 6 octets 2 2 2 4 octets60 1526 octets

Add a transport hierarchy MAC in MAC encapsulation No learning of customer MAC addresses in the middle of the network Transport spanning TREESTREES instead Use globalglobal meaning of tag (B-DA (48 bit) and B-VID (12 bit))

C-DA

B-DA

802.1Qay Provider Backbone BridgingTrafficEngineering (PBB-TE)


67/130



g ee g ( )

Transparent Tunneling of Ethernet ServicesC-DA

B-DA


TPI

D

S-

VID

S-

VID

TP


802.1ad

Frame


S-TAG C-TAG

TP

ID

B-TAG

ES-VIDB-DA B-SAB-

VID L/T802.1ad Frame

(/w or /wo FCS) FCS

Backbone

Provider

BridgeFrame 6 octets 6 octets 2 2 2 4 octets60 1526 octets

Add a transport hierarchy MAC in MAC encapsulation No learning of customer MAC addresses in the middle of the network Transport PATHSPATHS instead GMPLS or NMS configured Use globalglobal meaning of tag (B-DA (48 bit) and B-VID (12 bit))


68/130


69/130


70/130


71/130


72/130

MPLS BasicsAcronyms


73/130


LER

LSR

Non-MPLS

access network

Label

LSP: Switched

Path

MPLS Backbone

Label

Edge

Router

Label

Switching

Router

c o y s

MPLS BasicsShim Header Structure


74/130


TTLLabel (20 bits) CoS S

IP PacketIP Packet

32 bits

L2 HeaderL2 Header MPLS Header

MPLS header consist of four fields

Labelused to associate packet with an LSP

Experimental bitscarry packet queuing priority (CoS)

Stacking bit

Time to livelimits packet lifetime within LSP In most cases, the IP TTL is copied into the MPLS TTL

Some label values are reserved

MPLS Principles


75/130


Virtual connections in a connectionless network

Add a label to an IP packet that encodes a predefined tunnel

Traffic towards different destinations can be separated or aggregated andforwarded along a pre-defined path using only small labels as routing

decision

Label stacking is possible

Efficient Traffic Engineering due to source routing

Fast resilience mechanisms

Label Edge

Router

(LER)

Label

SwitchRouter

(LSR)

3: Routing

according to IP

header1: The edge router

classifies packets

and adds an MLPS

header, see tablebelow to them

2: Small tables,

fast routing

IP Packet Label IP Packet Label

MPLS Major Tasks


76/130


Information distribution (network topology and capacity)

Based on existing IP protocols (OSPF, IS-IS, EIGRP)- inband

Path calculation What are the best paths?

Constraint Based Routing (CBR)

Path setup, label distribution and exchange Label Distribution Protocol (LDP)

Reservation Protocol (RSVP-TE)

Forwarding of traffic along the MPLS path


77/130

Path Setup with RSVP


78/130


The Ingress LSR (I-LSR) sends a PATH message along the calculatedroute (source routing).

Each intermediate router checks if the required bandwidth is available andforwards the message to the tail of the path (last router).

The Egress LSR (E-LSR) sends a RESV message back along the samepath. On the way back, the resources are reserved and labels are selected

and signaled to the upstream LSR

Paths are updated / refreshed via a soft-state mechanisms

E-LSRI-LSR

RESV message

PATH message

Pros and Cons of MPLS Switching


79/130


Advantages:

+Aggregation of traffic

+Reduction of routing entries+Efficient traffic engineering

possibilities

(source routing)

+Fast and efficient resiliencemechanisms+VPN support+GMPLS support

Disadvantages:

- Additional technology below

the IP Layer- Handling of MPLS paths

(number, soft state)

- Complexity of Network

Configuration- Tight interelation of IP and

MPLS makes it quite complex

to handle

Challenge: Is MPLS ready to replace SDH/SONET?

Carrier Ethernet will replace SDH/SONET infrastructure over time


80/130


Transport teams mentality Long term statically provisionedpaths, pre-determined backup paths

Highly automated operation

environment

Strong reliance on automated OAM

and fault management systems

Simple static control plane scores

well over complex dynamic control

plane

Transport teams view on IP/MPLS

Believe IP/MPLS is not suitable for

transport applications

Consider it to be very complex (LDP, IS-

IS, OSPF, MPLS-TE, CSPF, FRR,..)

Do not need dynamic routing protocols,and recovery times too slow

IP/MPLS OAM tools not consistent with

transport OAM requirements

SONET/SDH infrastructure traditionally designed and managed by transportdepartments

Contents


81/130


1. Introduction


3. Ethernet Basics



T-MPLS



8. Conclusion

T-MPLS (Transport Multi Protocol Label Switching)


82/130


Idea: Use the MPLS concept known from IP and adapt it for forwarding issuesdefined in ITU-T G8110.1

Operate independently of its clients and its associated control networks(Management and Signaling Network).

IP/MPLS IP + SDH MPLS with a few changes:

Use of Penultimate Hop Popping is prohibited

Uni-directional and bi-directional LSPs can be defined

Use of global or per interface label space

Three types of Signalling Communication Channels (in-band via native IPpackets, in-band via dedicated LSP, out-of band)

OAM based on Y.1711 and Y.1731

Protection switching (ITU-T Y.1720)

Merging and ECMP is prohibited Multicasting in alignment to on-going work in IETFTPI

D

S-

VID

S-

VID

TP



S-TAG C-TAG

T-MPLSGFP or Ethernet

Contents


83/130


1. Introduction


3. Ethernet Basics



MPLS-TP



8. Conclusion

MPLS-TP standardization process and timeline


84/130


MPLS-TPMPLS-TP

Timeline:

ITU-T - IETF Joint Working Team (JWT)

was setup in March 2008

Agreement reached on

recommendations: End of April 2008

First draft: July 2008

Expected final agreements: E 2009

Joint Working Team

Technologies comparison


85/130


/~ /~/~Multipoint

support

~

IP/MPLS

~Standardized or

in process ofstandardization

~Scalable

Transport

oriented

MPLS-TPPBB-TET-MPLSELS

Terminated

by ITU-T

Market shift from PBB-TE to MPLS-TP


86/130


NSN focus

Mature but not transport orientedIP/MPLS

Transport oriented

Terminated by ITU-TT-MPLS

ELS

In standardization process

Not matureNo Control plane

No multipoint support

PBB-TE

In standardization process

Based on MPLS maturity

Enhanced for Transport

T-MPLS

MPLS-TP

The options

Standardized partly (single tagging)

Double use of VID for user-traffic

separation and routing

MPLS-TP MPLS Transport Profile

IP/MPLS & L2 MPLS can be categories as IETF MPLS

Nokia Siemens Networks is a major player in MPLS-TP standardization

MPLS Connection Oriented Lacks some

t t

T-MPLS A subset of MPLS plus additional

capabilities providing packet transport

Uses the same Ether type as MPLS but

h i t tibl

JWT


87/130



transportcapabilities some mechanisms are not compatiblewith MPLS

Nokia Siemens Networks has participants in the Joint Working Team

Nokia Siemens Networks acts as author and co-author forrequirements, framework and solution documents

3. Frameworks

3.1 MPLS-TP3.2 3.3 OAM

3.4 Survivability

3.4.1 for LSPs

3.4.2 for PWs

3.6 Control Plane3.7 Network

Management

2. Requirements

2.1 MPLS-TP2.2 OAM

2.3 Networkmanagement

4. Solution Documents

4.1 Generic ACH Alert Label Definition4.2 ACH definition

4.3 OAM Procedure document

4.3.1 OAM Analysis document

4.3.2 OAM Tool documents

4.4 Survivability4.4.1 Linear Protection

4.4.2 Ring Protection

4.5 Control Plane protocols

What is MPLS-TP?

A new standard focused on extending MPLS as a viable transport

ti t h l b ildi th t ti k t t t t k


88/130



option to help building the next generation packet transport networkBeing developed by IETF as a result of a collaboration between IETF and ITU-T via joint

working team (JWT)

Objective:

To bring transport requirements into IETF MPLS and extend IETF MPLS

forwarding, OAM survivability, network management and control plane

protocols to meet those requirements through IETF standard process

The JWT is divided into multiple sub-groups focused on:

Forwarding plane

OAM

Protection

Control plane

Management

MPLS-TP defines a profile of MPLS targeted at Transport applications.

This addresses specific MPLS characteristics and extensions


89/130



MPLS-TP foundation

The architecture for a transport profile of MPLS (MPLS-TP)is based on IETF MPLS (RFC 3031) & IETF PWE3 (RFC 3985)

OAM

extensions

Management

extensions

Control Planeextensions

Survivability

extensions

Alert LabelDefinition

extensions

MPLS-TP profile

required to meet transport requirements.

Desire: To make MPLS more Transport Oriented

NMS Point & Click

LSP d PWE

Configuration of

LSPs & PWEs via NMS

LSPs, PWEs

nesting i il t


90/130



Data plane: Data, OAM, protection congruent within architecture

Control plane: Optional and separated from data plane

Management plane: Configuration of LSP, PWE with point & click

MPLS-TP

LSP and PWE

management via external

LSP s & PWE s via NMS

and later dynamic control

plane

nesting similar toSONET/SDH

environments

LSP, PWE, OAMworks independent of control

plane

OAM and Data pathmust be congruent (use

the same path)

Protection and OAMmechanism works

within the MPLS

architecture

The Goal for the MPLS-TP technology

MPLS-TP will enable the migration of SONET/SDH networks to a packet-based network that will easilyscale to support packet services in a simple and cost effective way.


91/130



MPLS-TP forConnection Oriented

services, scalability andflexibility

End-to-End monitoringand control of customer services

Preserve thelook-and-feel towhich carriers have become

accustomed to deploying

SDH/Sonet networks

Efficient support ofpacket based services onthe transport network

Control anddeterministic usageof network resources

EthernetEconomicsUtilisation

Sonet/SDHcomparable Reliability andOperational Simplicity

Main characteristics of MPLS-TP

No modification of MPLS forwarding/data plane architecture

Current Standards for LSPs and PWEs construct


92/130



Current Standards for LSP s and PWE s construct

Configure LSPs and PWEs via Management plane

Bidirectional and congruent point-to-point LSPs

Framework supporting transport OAM capabilities for PWEs, LSPs

Complete Fault,

Configuration,

Accounting,

Performance and

Security (FCAPS)

Ability for LSPs and PWEs to be managed at different nested levels (path,

segment, multiple segments)

Interoperability with existing control and forwarding plane

MPLS Transport Profile - Terminology

Emulated Service


93/130



Definition of an MPLS Transport Profile (TP) within IETF MPLS standards

Based on PWE3 and LSP forwarding architecture

IETF MPLS architecture concepts

The major construct of the transport profile for MPLS are LSPs

Multi-node LSP network

Pseudo-wire (PWE)

PW1

Attachment

Circuit

PE1 PE2CE1 CE2

Attachment

Circuit

End to End LSP operations

LSP OAMLFIB:AB-BCLFIB:CD-DE

DE, PW-L


94/130



Path diversity is not part of the OAM process.

It is the responsibility of the Control Plane

OAM function uses GAL with Generic Channel Association

Pre-provisioned primary and backup paths

LSP OAM running on primary and back-up paths

OAM failure on backup path Alert NMS

OAM failure on primary path A and E updating LFIB

to send and receive PW-L traffic over backup path

LSP OAM

LFIB:BC-CDPW-L, AB

LFIB:AW-WXLFIB:WX-XY

LFIB:XY-YZA

EPrimary Path

Backup Path

PW-L, AW

YZ, PW-L

BA DC FE

Overview: OAM hierarchy and mechanisms


95/130



L0/L1:

Loss of Light; G.709, SONET/SDH LoS, LoF, ES, SES (NOT DISCUSSED)Non MPLS L2 connectivity: Native L2 solution 802.1ag (Not Discussed) , Non IP BFD

Failure propagation across layers is supported by this architecture

General LSPs :

Generic Exception Label and Generic Associated Channel Includes End to End and segment LSPs

Used to carry a variety of OAM, Mgmt, signalling protocols.

Pseudo-wires : PWE3 Associated Channel

L1/L2 L1/L2 L1/L2 L1/L2L1/L2

Segment LSP

End to End LSP

Pseudo-wire

Midpoint

LSP example- end to end and per carrier monitoring

Carrier 1 C i 2

PE

PEPE

PE


96/130

96 Nokia Siemens Networks

PP PP

MEP MIP MIP MEP

MEP MEPMEP MEP MEP MEP MIPMIP

A segment is between MEPs

OAM is end to end or per segment In SDH/OTN and Ethernet segment OAM is implemented using Tandem Connection Monitoring (TCM)

The OAM in each segment is independent of any other segment

Recovery actions (Protection or restoration) are always between MEPs i.e. per segment or end to end

Carrier 1 Carrier 2

NNI

MEP: Maintenance End PointMIP: Maintenance Intermediate Point

end to end LSP OAMend to end LSP OAM

segment LSPOAM

(inter carrier)

segment LSPOAM

(inter carrier)

PEPEPEPE

segment LSP OAM(carrier 2)

segment LSP OAM

(carrier 2)segment LSP OAM

(carrier 1)

segment LSP OAM

(carrier 1)

PEPE PP

MIP

NNI NNIPEPEPEPE PEPE

MIPMIP

Contents

1 I t d ti


97/130



1. Introduction


3. Ethernet Basics


5. Carrier Ethernet Transport Technologies6. Carrier Ethernet Transport Network Architecture & Solutions


8. Conclusion


98/130

The migration to CET covers all IPT business linesand is key IPT strategy

f G S


99/130



Migration from NG-SDH installed base

Evolution to hybrid platform with CET connectivityFrom TDM to

Packet

From existingbase to optimized

networks

From currentswitches to NG

portfolio Migration from existing non-Connection oriented L2aggregation

Multilayer optimization: L1 to L3

Greenfield overlay with Carrier Ethernet Transport

Interworking with customer edge (L2, L3) and provideredge (L3) as well as with 3rd party L2


Multi-reach DWDMMicrowavePacket Radio

CET SwitchesHybrid NG

Metro NMS

Migration towards Carrier Ethernet TransportEvolution of Ethernet in all network technologies

IP/MPLS IP


100/130



SDH/SONET

CarrierSwitches

WDM/OTNROADM/PXC

Ethernet ADMwith GFP-T/F

Ethernet ADM

with L2 Switch Integration of

Ethernet functionality

Integration of

Ethernet/ODU-Switching

Classical EthernetClassical Ethernet

Classical IP/MPLS

MPLSMPLS--TPTP

TT--MPLSMPLS

PBBPBB

PBBPBB--TETE

Integration ofEthernet functionality

ELSELS

Microwave

TDMHybrid Packet/TDM

CET Migration Scenarios

A. Replacement of TDM by Packet TransportPl tf b d / Eth t


101/130



Platform based on c/o Ethernet

Deployment of a new Packet Transport platformto replace SDH/SONET TDM platform.

B. Hybrid (TDM/Packet) scenario Hybrid platform deployment for all new traffic

(packet and TDM) in a jointly network with an

existing NG-SDH platform for TDM traffic

C. Integration of Ethernet in DWDM GbE add/drop cards or L2 switch cards allows

cost-efficient and scalable DSLAM aggregation /

mobile backhaul in metro aggregation networks

TDM

Packet+

Rethinking the Role of the Layers


102/130



IP/MPLSIP/MPLS

ETHERNET

Including Aggregation, Metro and CoreETHERNET

Including Aggregation, Metro and Core

OTN/WDMOTN/WDM

SONET/SDHSONET/SDH Transition

Service-awarenessHigh-touchnetworking

Efficient end-to-endcarrier-grade packet transportpt-pt, pt-mpt, mpt-pt, mpt-mpt

ServicesLayer 3

Layer 2

Functionsplit

IPIP is the convergence platform forapplicationsapplications and servicesservices.

EthernetEthernet and OTN/WDMOTN/WDM will be the convergence platform fortransporttransport.

Common OTN/WDMinfrastructure

Layer 1

Carrier Ethernet Transport in a Multilayer NetworkOptimized Transport based on Packet, TDM and Optics

Functionality onlyFunctionality only

where neededwhere neededMi i i i t di t


103/130



Subscriber/Service

Aggregation Core

Layer 3 / IP

Edge

LER LSR

LSR

Access

GPON

FTTH

Layer 2 / Carrier Ethernet TransportDSLAM

Access Switch

Metro DWDM Core DWDML2 VPN

Leased Line,E-Line

Business

Residential

IP, Voice,Video

Service AwarenessService AwarenessPacket routing

Traffic EngineeringRobust network

(Restoration)

Packet switchingPacket switchingTraffic Engineering

Robust network

Native layer 2Native layer 2PredictablePredictable behaviorCarrier Grade OAMCarrier Grade OAM

Cost efficientCost efficient2.5Gbps, 10Gbps,40Gbps, 100Gbps100Gbps

Native transportNative transport

of services onof services on

the lowest possible layerthe lowest possible layer

dependent on servicedependent on service

requirements and costrequirements and cost

Optimal mixOptimal mix of intermediategrooming and routing and

transparent bypass

(Ethernet + WDMEthernet + WDM)

Minimize intermediaterouting - offload routers

Contents

1 Introduction


104/130



1. Introduction


3. Ethernet Basics


5. Carrier Ethernet Transport Technologies6. Carrier Ethernet Transport Network Architecture & Solutions

Applications


8. Conclusion

Customer

HQ

High SpeedInternet Access

VPLS or VPLS-TE ServiceVideo conference, Ethernet PMP,Intranet access

Inter-LAN or Inter-PABXEthernet, Storage,Video (surveillance)

Carrier Ethernet enables service providers to deliver awide range of mission-critical applications


105/130



High Speed Access to IP-VPN

Low cost access combinedwith centralized router

to offer IP VPN

Customer

HQ

Customer site

Customer

site

CarrierEthernet

CustomerHQ Customer

site

Customer site

IP VPN

Network

Carrier

Ethernet

Q

Customer

site

CarrierEthernet

Carrier

Ethernet

Customer

HQ

Customer

site

Customer

site

r

Multi-Service Access

VPLS

Group

Customer HQ

Customer

site

T1/E1

OC-3/STM1

or NxT1/E1

Intranet accessVideo (surveillance)

VPLS: Virtual Private LAN Services VPN: Virtual Private Network

www

IP VPN

CET Solution Focus addresses three mainoperator broadband challenges

R id i l d b db d


106/130



Residential and broadband

High Speed Internet (HSI)

IPTV, VoD

Voice

Mobile Backhauling

TDM PWE3 (CESoP) for 2G backhaul

Ethernet backhaul for 3G, I-HSPA, LTE & WiMAX Synchronous Ethernet