Dave thorne

1

Multi-Service Broadband Network Architecture

FTTH Technology WorkshopLondon, February 2013David ThorneBBF E2EA Chair

2

Introduction

The BBF has been driving the evolution of Broadband Network Architecture for the last 12 years– this has involved all the major stakeholders in the industry

During this period network operators have faced evolving challenges and so different technical solutions have been introduced to support new services and business modelsBBF TR’s have played a critical role in helping the industry face the new challengesInteroperability testing and certification programs are helping to promote a multi-vendor environment

/Distributed AN

Access and Network Evolutionat the Broadband Forum

2003

2006

1999

2009+

TR-25

TR-59

TR-101

WT-145

InternetATM AggregationADSLBAS

Internet& QoSATM AggregationADSL BRAS

ADSL

Ethernet Aggregation

ADSL2+

VDSLVideoBNG

BNG

Internet& QoS

IPTV

VOIP

FTTx

VDSLMPLS or Carrier Ethernet Aggregation

Internet& QoS

IPTV

VOIP

OtherNG Video BNG

NG-BNG

PON2008 TR-156

PON/

Distributed AN

4

Introducing Fixed-Mobile

convergence

Augmenting xDSL with Fibre access

Providing Multi-Service support

Multi-Service Broadband Architecture

Providing Cloud services

Challenges faced by Network Operators

Moving from ATM to Ethernet based

Access

New Business Requirements & service models

5

Motivations for a Multi-Service Architecture - I

Support for different customer types, markets and services: residential, retail, business, wholesale, fixed, mobile, cloud/virtualized services over a common network architecture Simplification of network architecture: an end-to-end architecture based on IP/MPLS and Ethernet with a well-defined migration pathMulti technology Access support: xDSL, Ethernet, xPON, Microwave wireless, legacy voice, wavelength access for business customers, TDM circuitsMulti-Edge support: the ability to source traffic to a given subscriber from multiple, different, Service EdgesEnhanced Scalability: moving IP Edge Nodes closer to customers allows the connection of more customers to the aggregation network

6

Motivations for a Multi-Service Architecture - II

Enhanced availability: use of OAM and an appropriate control plane for automatic protection and/or restoration Seamless connectivity: integration of access, aggregation and core networksOperational enhancements: the migration to a converged packet based access and aggregation network can improve the end-to-end provisioning process by minimizing the provisioning pointsEnhanced support for Wholesale services: to meet regulatory requirements (e.g. Active Line Access) and support non-vertical business modelsFixed-Mobile Convergence (FMC): allows a user to use a single handheld device for both fixed and mobile access

7

Introducing Fixed-Mobile

convergence

Augmenting xDSL with Fibre access

Providing Multi-Service support

Multi-Service Broadband Architecture

Providing Cloud services

Roles played by BBF Reports

Moving from ATM to Ethernet based

Access

New Business Requirements & service models

TR-101 TR-221

TR-101

TR-156 TR-167

TR-144

WT-178TR-145

MR-275 WT-302TR-203 WT-291

WT-300

TR-101 Scope and Content

VLAN architectureMulticast optionsUse of a video-optimised Service Router (next to a ‘traditional’ TR-59 type BRAS)Resilience in the Ethernet Aggregation NetworkQoS in the Ethernet Aggregation NetworkEthernet OAMSupport for PPPoA and IPoA (aka interworking between XoA and XoE)

Migration from ATM to Ethernet Broadband Aggregation

Note: TR-101 introduces the term Broadband Network Gateway (BNG) to differentiate this from the legacy ‘BRAS’ term

VLAN Architecture: VLAN per User (1:1)

VLAN use similar to ATM, i.e. connection-orientedIEEE802.1ad—Inner Tag = Port Identifier, Outer Tag = DSLAM IdentifierMulticast replication inside a Single BNG, not inside the Ethernet Aggregation NetworkMulti-homing to two BNGs is complex

Single tagged 802.1ad S-VLANs - double tagging not neededAccess Node inserts Line ID (DHCP Opt 82 , PPPoE Intermediate Agent) as now connectionlessNetwork Elements take care of subscriber MAC isolation through ‘split horizon forwarding’ Multiple injection points per VLAN (BRAS andVideo Service Router) possibleMulticast replication within access/aggregation

VLAN Architecture: VLAN per Service/SP (N:1)

TR-101 Architecture

Multiple options for customer hand-off at the U interface:– Multiple VC DSL UNI (mostly deprecated)– Trunk UNI - Single VC DSL or Ethernet – Non-Trunk UNI - Single VC DSL or Ethernet

In the Single VC DSL and Ethernet UNI models, separate functions for QoS ( 802.1p COS) and forwarding (802.1Q S-VLANs)A10 Interface = Ethernet or IP handoff to the NSP/ASP

ANAgg. Node

EthernetAggregation

L2A‐EL2A‐EL2F‐EL2F‐E

EthernetAggregation

L2F‐EL2F‐E

BNG

EthernetAggregation

L2F‐EL2F‐EL2A‐EL2A‐E

L3FL3FIP Aggregation

MPLS Aggregation(optional)L2A‐ML2A‐M

U

IP/MPLSCore

A10

Va

L2A = Layer 2 AdaptionL2F = Layer 3 ForwardingL3F = Layer 3 ForwardingEthernet (E) and MPLS (M) Options

12

Multi-Service Architecture Suite

TR-144: Broadband Multi-Service Architecture & Framework Requirements:

describes business drivers and requirements TR-145: Multi-service Broadband Network Functional Modules and Architecture:

defines reference architectures and functional modules The functional module decomposition enables a variety of deployment options, i.e. different ‘boxing-up’

WT-178: Multi-service Broadband Network Architecture and Nodal Requirements:

describes a set of architectures, re-using the functional modules provided in TR-145, and specifies detailed nodal requirements

BBF TR-178 architectures - 1

Ethernet Service Layer support same 1:1 and N:1 VLAN constructs as TR-101, as well as IP ServicesMPLS is the ‘Supporting Aggregation Layerfor Ethernet (and IP)

Supporting TR-101 Service Model + Mobile Backhaul + Business/Wholesale


U1 and A10 representation the same as TR-101: Ethernet Service LayerTR-101 / Ethernet Access Nodes connect to MPLS Aggregation Network (Broadband Aggregation Gateways /BAGs)H-QOS and Ethernet Sessions (Dynamic Ethernet Service Activation) on BAGMPLS pseudowires terminate inside BNG (pseudowire headend)

TR-101 over MPLS Aggregation (centralized BNG)

14


A10

IP/MPLSCore

EANBAGBNG

EthernetAggregation

L2A‐EL2A‐EL2F‐EL2F‐EMPLS Aggregation

L2A‐ML2A‐ML2F‐ML2F‐M

(Service Specific) IP Aggregation

L3FL3F

L2A‐EL2A‐E

EthernetAggregation


L2F‐ML2F‐ML2A‐ML2A‐M

L2F‐EL2F‐E

EthernetAggregation

U1


U1 and A10 representation the same as TR-101: Ethernet Service LayerMPLS enabled Access Node deploy Seamless/Unified MPLSMPLS pseudowires terminate inside BNG (pseudowire headend)

MPLS in the Access Node

15


A10

IP/MPLSCore MPLS

AggregationL2A‐ML2A‐ML2F‐ML2F‐M

EthernetAggregation


L2F‐ML2F‐M

BNG

(Service Specific) IP Aggregation

L3FL3F

L2A‐EL2A‐EMPLS AggregationL2F‐ML2F‐ML2A‐ML2A‐M

L2F‐EL2F‐E

EthernetAggregation

U1

BAG MAN


U1 and A10 representation the same as TR-101 : Ethernet Service LayerTR-101 / Ethernet Access Nodes connect to MPLS Aggregation Network (Broadband Aggregation Gateways /BAGs)H-QOS and Ethernet Sessions (Dynamic Ethernet Service Activation) and IP/PPP Sessions on Edge BNG (BNGE) for some servicesMPLS pseudowires terminate inside Service BNG (BNGS) (pseudowire headend)

BNG Hierarchies with TR-101/Ethernet Access Node

16


A10

IP/MPLSCore

EAN

EthernetAggregation



MPLS Aggregation

L2A‐ML2A‐ML2F‐ML2F‐M

(Service Specific) IP AggregationL3FL3F


L2F‐EL2F‐E

EthernetAggregation

EthernetAggregation


U1

BNGS BNGE


U1 and A10 representation the same as TR-101: Ethernet Service LayerTR-101 / Ethernet Access Nodes connect to MPLS Aggregation Network (Broadband Aggregation Gateways /BAGs)Ethernet Sessions (Dynamic Ethernet Service Activation) and IP/PPP Sessions on Access BNG (BNGA)for some servicesMPLS pseudowires terminate inside Service BNG (BNGS) (pseudowire headend)

BNG Hierarchies with Access BNGs

17


A10

IP/MPLSCore

BNGABAG

MPLS Aggregation

L2F‐ML2F‐M

EthernetAggregation



MPLS AggregationL2A‐ML2A‐ML2F‐ML2F‐M

BNGS(Service Specific) IP Aggregation

L3FL3F


L2F‐EL2F‐E

EthernetAggregation

U1

18

From xDSL to Fiber Access

Want to support the introduction of deeper fiber, but without changing the basic architecture– allows a smooth migration/co-existence

TR-156 : Using GPON Access in the Context of TR-101TR-167 : GPON-fed TR-101 Ethernet Access Node

19

GPON in the Access Network: TR-156

TR-156 specifies the required capabilities of GPON OLTs, ONUs and ONTs– above the Physical, TC and OMCI layers, which are covered

by FSAN/ITU standards

Supports a variety of deployment scenarios with a converged technical solution– FTTH (Fiber To The Home), FITH (Fiber Into The Home),

FTTO (Fiber To The Office), MDU (Multi-Dwelling Unit), MTU (Multi-Tenant Unit)

Aims to ensure interoperability between GPON OLTs and ONUs/ONTs

20

TR-156 Network Architecture

Introduction of GPON access into a TR-101 Network

The entire GPON system performs the role of an Access Node as specified by TR-101– U and V reference points remain unchanged

Aims to integrate seamlessly into broadband service providers’ deployments

21

GPON in the Aggregation Network: TR-167

Defines the required capabilities for a GPON system (OLT/ONU) used to feed a TR-101 access node– the GPON system is performing the role of an aggregation

node as specified by TR-101 – no effect on the access node– does not define the physical layer attributes of the system

22

TR-167 Network Architecture

V Reference point resides downstream of the ONU (between the ONU and the AN)The ONU and AN may be in the same physical device

23

Cloud Services and Beyond

The Cloud is changing the way that businesses deliver and people consume services

– also enables IT to be delivered as a service Cloud Computing will play a key role in generating new business opportunities as Broadband Service Providers can move into the IT services market using their existing assets WT-302 provides a framework and requirements to support Cloud services in Multi-Service Broadband Networks TR-145/WT-178 already support some tools to address Cloud services such as:– capability to scale and grow on demand: nodes can be grouped in

virtual clusters and functions can be moved from centralized to distributed locations and potentially to new components/entities

– “on-demand” configuration and provisioning: supported for both Layer 2 and Layer3 services

MR-275 describes how to use enhanced IP/MPLS tools (E-VPN, PBB-EVPN) to provide Datacenter Interconnect

24

FMC – BBF - 3GPP Interworking

TR-203 describes Interworking use cases based on 3GPP UE devices moving between the 3GPP Mobile Network and the fixed broadband network and vice versa

25

WT-291 builds on TR-203 and provides the nodal requirements for solutions associated with the TR-203 architecture and use cases

Evolving from completely separated networks to an interworking architecture

DPI

PCRF

Business support systems

Service layer


Service layer

BPCF

Mobile access

MMESGSN

PGWSGW

GGSN DPI

BSC, RNC or eNodeB

Wireline access

BRAS / BNG

Router DPI

PCRF


Service layer


Service layer

BPCF

Mobile access

MMESGSN

PGWSGW

GGSN DPI

BSC, RNC or eNodeB

Wireline access

BRAS / BNG

Router

ControlPlane

UserPlane

FMC – BBF - 3GPP Interworking

26

Summarizing WT-300 reference architectures

BPCF / PCRF


Service layer

Mobile access

MME

SGSN

PGW

SGW

GGSN DPI

BSC, RNC or eNodeB

Wireline access

BNG / BRAS

Router DPI

Common functions:• Access control• Fair usage policies• Re-directions• …

OR

FMC – Policy Convergence

27

Conclusions

The BBF has a long and successful history in Broadband Network architectureThe initial focus on mass-market residential wireline services has now been greatly expanded to include business services, multiple edges, FMC and the Cloud– a true multi-purpose, multi-service, multi-edge network

This has led to a suite of architecture documents– necessary to support migration and a range of solutions

Including Fiber access has been a key part of this expansion– done in a way that allows co-existence and a smooth

migration

28

Thank You

Documents

Dave thorne