Dave thorne

422 views
201 views

Published on

FTTH Conference 2013 Workshop New Trends

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
422
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
14
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Dave thorne

  1. 1. Multi-Service Broadband Network Architecture FTTH Technology Workshop London, February 2013 David Thorne BBF E2EA Chair1
  2. 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 models BBF TR’s have played a critical role in helping the industry face the new challenges Interoperability testing and certification programs are helping to promote a multi-vendor environment2
  3. 3. Access and Network Evolution at the Broadband Forum1999 TR-25 ADSL ATM Aggregation BAS Internet Internet2003 TR-59 ADSL ATM Aggregation BRAS & QoS ADSL Internet VOIP & QoS2006 TR-101 ADSL2+ BNG VDSL Ethernet Aggregation / Video BNG IPTV Distributed AN2008 TR-156 PON NG- Internet BNG VOIP & QoS VDSL MPLS or Carrier Ethernet Aggregation2009+ WT-145 FTTx NG IPTV Other PON / Video BNG Distributed AN
  4. 4. Challenges faced by Network Operators New Business Providing Multi-Service Requirements & support service models Augmenting xDSL with Fibre access Multi-Service Broadband ArchitectureMoving from ATMto Ethernet based Access Providing Cloud services Introducing Fixed- Mobile convergence4
  5. 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 path Multi technology Access support: xDSL, Ethernet, xPON, Microwave wireless, legacy voice, wavelength access for business customers, TDM circuits Multi-Edge support: the ability to source traffic to a given subscriber from multiple, different, Service Edges Enhanced Scalability: moving IP Edge Nodes closer to customers allows the connection of more customers to the aggregation network5
  6. 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 networks Operational enhancements: the migration to a converged packet based access and aggregation network can improve the end-to-end provisioning process by minimizing the provisioning points Enhanced support for Wholesale services: to meet regulatory requirements (e.g. Active Line Access) and support non-vertical business models Fixed-Mobile Convergence (FMC): allows a user to use a single handheld device for both fixed and mobile access6
  7. 7. Roles played by BBF Reports New Business Providing Multi-Service Requirements & support service models Augmenting xDSL TR-101 TR-221 with Fibre access TR-144 Multi-Service TR-156 TR-167 TR-145 Broadband WT-178 ArchitectureMoving from ATMto Ethernet based Providing Cloud Access services TR-203 WT-291 TR-101 MR-275 WT-302 Introducing Fixed- Mobile convergence WT-3007
  8. 8. TR-101 Scope and ContentMigration from ATM to Ethernet Broadband Aggregation VLAN architecture Multicast options Use of a video-optimised Service Router (next to a ‘traditional’ TR-59 type BRAS) Resilience in the Ethernet Aggregation Network QoS in the Ethernet Aggregation Network Ethernet OAM Support for PPPoA and IPoA (aka interworking between XoA and XoE)Note: TR-101 introduces the term Broadband Network Gateway (BNG) todifferentiate this from the legacy ‘BRAS’ term
  9. 9. VLAN Architecture:VLAN per User (1:1) VLAN use similar to ATM, i.e. connection- oriented IEEE802.1ad—Inner Tag = Port Identifier, Outer Tag = DSLAM Identifier Multicast replication inside a Single BNG, not inside the Ethernet Aggregation Network Multi-homing to two BNGs is complex
  10. 10. VLAN Architecture:VLAN per Service/SP (N:1) Single tagged 802.1ad S- VLANs - double tagging not needed Access Node inserts Line ID (DHCP Opt 82 , PPPoE Intermediate Agent) as now connectionless Network Elements take care of subscriber MAC isolation through ‘split horizon forwarding’ Multiple injection points per VLAN (BRAS and Video Service Router) possible Multicast replication within access/aggregation
  11. 11. 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 Va BNG Agg. Node AN U IP AggregationA10 L3F Ethernet Ethernet Ethernet IP/MPLS MPLS Aggregation L2A‐E L2F‐E L2F‐E Aggregation L2F‐E Aggregation L2A‐E Aggregation Core L2A‐M (optional) L2A = Layer 2 Adaption L2F = Layer 3 Forwarding L3F = Layer 3 Forwarding Ethernet (E) and MPLS (M) Options
  12. 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 requirements12
  13. 13. BBF TR-178 architectures - 1Supporting TR-101 Service Model + Mobile Backhaul +Business/Wholesale Ethernet Service Layer support same 1:1 and N:1 VLAN constructs as TR-101, as well as IP Services MPLS is the ‘Supporting Aggregation Layer for Ethernet (and IP)
  14. 14. BBF TR-178 architectures - 2 TR-101 over MPLS Aggregation (centralized BNG) BNG BAG EAN (Service Specific) IP Aggregation L3F Ethernet Ethernet Ethernet IP/MPLS Aggregation Aggregation Aggregation L2F‐E L2A‐E L2F‐E L2A‐E Core L2A‐E L2F‐E MPLS Aggregation MPLS Aggregation L2A‐M L2F‐M L2F‐M L2A‐MA10 L2A = Layer 2 Adaption L2F = Layer 3 Forwarding U1 L3F = Layer 3 Forwarding Ethernet (E) and MPLS (M) Options U1 and A10 representation the same as TR-101: Ethernet Service Layer TR-101 / Ethernet Access Nodes connect to MPLS Aggregation Network (Broadband Aggregation Gateways /BAGs) H-QOS and Ethernet Sessions (Dynamic Ethernet Service Activation) on BAG MPLS pseudowires terminate inside BNG (pseudowire headend) 14
  15. 15. BBF TR-178 architectures - 3 MPLS in the Access Node BNG BAG MAN (Service Specific) IP Aggregation Ethernet L3F Ethernet IP/MPLS L2A‐E L2F‐E Aggregation Aggregation L2F‐E L2A‐E Core MPLS Aggregation MPLS Aggregation MPLS Aggregation L2A‐M L2F‐M L2F‐M L2F‐M L2A‐MA10 L2A = Layer 2 Adaption U1 L2F = Layer 3 Forwarding L3F = Layer 3 Forwarding Ethernet (E) and MPLS (M) Options U1 and A10 representation the same as TR-101: Ethernet Service Layer MPLS enabled Access Node deploy Seamless/Unified MPLS MPLS pseudowires terminate inside BNG (pseudowire headend) 15
  16. 16. BBF TR-178 architectures - 4BNG Hierarchies with TR-101/Ethernet Access Node BNGS BNGE EAN (Service IP Aggregation Specific) L3F L3F Aggregation IP Ethernet Ethernet Ethernet IP/MPLS Aggregation L2A‐E L2F‐E Aggregation L2F‐E L2A‐E Aggregation L2F‐E L2A‐E MPLS MPLS Core Aggregation Aggregation L2A‐M L2F‐M L2F‐M L2A‐MA10 L2A = Layer 2 Adaption L2F = Layer 3 Forwarding U1 L3F = Layer 3 Forwarding Ethernet (E) and MPLS (M) Options U1 and A10 representation the same as TR-101 : Ethernet Service Layer TR-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 services MPLS pseudowires terminate inside Service BNG (BNGS) (pseudowire headend) 16
  17. 17. BBF TR-178 architectures - 5BNG Hierarchies with Access BNGs BNGS BAG BNGA (Service Specific) IP Aggregation IP Aggregation L3F L3F MPLS Ethernet Ethernet Aggregation IP/MPLS Aggregation Aggregation L2F‐E L2A‐E L2A‐E L2F‐E Core MPLS Aggregation MPLS Aggregation L2A‐M L2F‐M L2F‐M L2F‐M L2A‐M A10 L2A = Layer 2 Adaption L2F = Layer 3 Forwarding U1 L3F = Layer 3 Forwarding Ethernet (E) and MPLS (M) Options U1 and A10 representation the same as TR-101: Ethernet Service Layer TR-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 services MPLS pseudowires terminate inside Service BNG (BNGS) (pseudowire headend) 17
  18. 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- 101 TR-167 : GPON-fed TR-101 Ethernet Access Node18
  19. 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/ONTs19
  20. 20. TR-156 Network Architecture 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’ deployments20 Introduction of GPON access into a TR-101 Network
  21. 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 system21
  22. 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 device22
  23. 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-23 VPN, PBB-EVPN) to provide Datacenter Interconnect
  24. 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 versa24
  25. 25. FMC – BBF - 3GPP Interworking WT-291 builds on TR-203 and provides the nodal requirements for solutions associated with the TR-203 architecture and use casesBusiness Service Business Service Business Service Business Servicesupport systems layer support systems layer support systems layer support systems layer Control Plane PCRF BPCF PCRF BPCF User Plane SGSN GGSN DPI Router DPI SGSN GGSN DPI Router DPI MME PGW MME PGW SGW SGW BSC, RNC BRAS / BNG BSC, RNC BRAS / BNG or eNodeB or eNodeB Mobile access Wireline access Mobile access Wireline access Evolving from completely separated networks to an interworking architecture25
  26. 26. FMC – Policy Convergence Summarizing WT-300 reference architectures Business support Service systems layer Common functions: • Access control • Fair usage policies BPCF / • Re-directions PCRF •…OR SGSN GGSN DPI Router DPI MME PGW SGW BSC, RNC BNG / BRAS or eNodeB Mobile access Wireline access26
  27. 27. Conclusions The BBF has a long and successful history in Broadband Network architecture The 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 smooth27 migration
  28. 28. Thank You28

×