The Future State of the Network - portal.adtran.comportal.adtran.com/pub/Library/Webinars/BBSS_17_Goodson_Ko_Future... · ® Adtran, Inc. 2014 All rights reserved . ADTRAN Company

1 ADTRAN Company Confidential ® Adtran, Inc. 2014 All rights reserved

The Future State of the Network Richard Goodson

Ken Ko Office of the CTO

Date


Agenda

SDN and NFV

Copper Evolution: FTTdp

Copper Evolution: G.fast

PON Evolution


Understanding Board Level Vectoring

SDN and NFV


Separate the Control Plane from the Forwarding Plane Centralized SDN Controller

– Determines how network devices forward packets – Provides abstract, centralized view of network

Flow Switching – Network devices move packets according to policies/tables from

SDN Controllers – Packets that require special handling sent to SDN Controller for

processing

Benefits – Simplified, centralized management and control – Improved network efficiency – Rapidly deploy new applications & services – Reduce CAPEX & OPEX

Software Defined Networking (SDN)


SDN Architecture

Application Layer – Applications

communicate with network OS via APIs

Controller Layer – Network OS presents

logical network map to services and applications

– Translates application behaviors to control of infrastructure devices

Infrastructure Layer – Devices forward traffic based on flow table entries from controller

Source: ONF


Network Functions Virtualization (NFV)

NFV focuses on converting network functions (SBC, firewall, DPI, BRAS, etc.) to software applications on a virtual infrastructure

Source: ETSI


Virtualized Network Function – SW implementation of a

network function – May have an EMS – Corresponds to network node

NFV Infrastructure – Provides virtual resources to

support execution of the VNFs – COTS hardware – Accelerator components – Software layer virtualizes and

abstracts underlying hardware

NFV Management and Orchestration – Orchestration and management of infrastructure resources – Management of VNFs; Service Chaining/Network Forwarding

Graphs – Also interacts with (NFV external) OSS/BSS

NFV Architecture (ETSI)

Source: ETSI NVF M&O

VNF

NVFI

Hardware Resources

Orchestrator

Virtualized Infrastructure

Manager

OSS / BSS

Service, VNF & Infrastructure Description

EMS 1 EMS 2 EMS 3

VNF 1 VNF 2 VNF 3

Virtual Compute

Virtual Storage

Virtual Network

Virtualization Layer

Computing Hardware

Storage Hardware

Network Hardware

VNF Managers


SDN: Separation of control and forwarding planes – Silent on dedicated vs.

virtualized implementation

NFV: Virtualization of network functions – Silent on centralized vs. distributed

control

Two independent technologies – Either can be implemented without

the other, but … – Synergies derived from

using both technologies together

Common attributes – Increased use of SW functions – Increased use of COTS HW – Benefit from open interfaces and standards

SDN and NFV

Open Innovation

Software Defined

Networks

Network Functions

Virtualization

Creates competitive supply of innovative applications by third parties

Creates network abstractions to

enable faster innovation

Reduces CAPEX, OPEX, space and power

consumption Source: ETSI


Early Core Networks: IP Forwarding

IP Forwarding: All network elements exchange routing information across the data plane via dynamic

routing protocols (RIP, OSPF, BGP, IS-IS, etc) and make forwarding decisions on a per-hop basis.

Routing Protocols

Early Days of Core IP Networks


MPLS Switching in Core Networks

MPLS Switching: IP lookups performed at the edge, switching in the core. Introduced optional control and data

plane separation, but control plane still used mix of dynamic protocols (LDP, I-BGP, OSPF-TE, etc).

LER LER

LSR

Transition to MPLS Switching in Core Networks


Evolution to SDN in Core Networks

SDN Controller Controls how all network elements forward packets. Provides centralized, abstracted view of the overall network. Runs in high-compute data center.

Data Plane Control Plane

Open APIs for config (e.g., NETCONF) and forwarding

(e.g. OpenFlow)

Business and Network Applications (customer portals, topology views, network

applications – QoS monitoring, PM reporting, etc.)

Network Orchestration (coordinates and controls allocation of

all network resources)

Open APIs

Flexibility to introduce new services, reconfigure based on global policy; Global visibility; Reduced OPEX


SDN Programmable Networks

Nx10/100G DWDM Metro Transport

Enterprise Gateway

The Cloud

RG

CE NID

Service Orchestration


APIs = Path to Programmable Networks

Billing System

Network Orchestration Layer


Enterprise Gateway

The Cloud

RG

CE NID

Transport & Access NMS (AOE)

ACS Cloud NMS

Activate 1G w/ IPTV

1G w/ IPTV

Activate Home Wi-Fi & STBs

Activate 1G

Activate IGMP, EVCs, QoS,

Traffic Mgmt, etc.

Activate BNG, IPTV


NFV and the Value of Virtualization


RG

CE NID

WA IDS

FW BNG

CF

DPI

Openstack

Service Orchestration

Billing System

Activate Advanced Business Services

NFV Service Chaining

Enterprise Gateway

Virtualized Network Functions


Instant-On Service Activation

Real-Time Entertainment

Residential Internet

Enterprise Communications

Web Hosting

Small Cell Connectivity

Multi-Site Enterprise Communications

Provisioning Network Services: as Simple as Installing an App


Operator Interest

Key Trends: Operators looking for ways to extend the SDN and NFV benefits of data center technology to residential and enterprise while greatly simplifying the access network


Virtualization and Access Equipment

Virtualization Heat Map

Source: Ericsson

Industry view: NFV is less relevant in Access Expected access direction

– Primary: SDN-based control to support network automation and orchestration

– Secondary: functions that can be virtualized through NFV

Issues in the Access space – Outside plant (e.g., environmental,

power, accessibility) – HW-specific functions (e.g., FTTDP reverse powering) – PHY complexity (e.g., copper, vectoring)


Not a complete listing!

Open Source initiatives – OpenFlow, OpenDaylight, Open vSwitch, OpenStack, ONUG … – Standardization by Open Source Code

Vendor initiatives IETF

– Numerous projects (ForCES, Netconf, Service Chaining …) – SDN Research Group in IRTF

ETSI NFV ISG (Industry Specification Group) – Defined architectural framework, requirements, use cases – Gap analysis; standards recommendations

Broadband Forum – Working Drafts in E2E Architecture WG – Study Documents in SIMR

SDN & NFV Initiatives & Standards


Use Case: Virtualize the Home Environment

Virtualize functions in home devices – RG vRG (aka NERG, BBF WT-317); STB vSTB

Deploy new services & features via SW – Device visibility enables services like Parental Control

Minimize HW upgrades & support



Copper Evolution: FTTdp


The Evolution of Broadband Access

* FttDP from TNO and ITU Q4/SG15 11BM-023

< 20Mbps

< 200kbps

< 200 Mbps

> 1Gbps


Buried cable running down street or near rear

lot boundaries

25 pair binder 25 pair binder

NID NID NID

NID NID

MDU Environment

FTTdp Deployment Models (US)

Individual Drop Cables – Little Crosstalk Coupling

G.fast service unit

GPON or GbE OLT

NID NID

NID

(Partially) Shared Drop Cables – More Crosstalk Coupling

SFU Environment

Fiber cable

DP MDU


Reverse Powering

Deep deployment may mean difficulty getting utility power

In these cases, FTTdp will use “reverse powering” – Subscriber(s) power the DP over existing wires

Challenges: – Reverse powering not yet addressed by regulators – “Fairness” in powering between subscribers – DP must be powered even by single subscriber – DP management lost when all subscribers “off”

G.fast service unit

DP

NID

Power

Service


Provider-Install vs. Self-Install

DP

Ethernet

CPE

Self Install

Ethernet

Provider Install

CPE@ NID

VoIP

G.fast + POTS + rev. pwr.

Provider-install – Can isolate inside wiring from outside plant – Can isolate phone & data wiring – Higher performance – Higher cost (Truck roll)

Self-install – Mail equipment to premises – No-tools install (not even a screwdriver) RJ11-style plugs are allowed ADSL-style dongles are allowed

– Must operate over existing wiring May only have one pair No isolation of inside wiring from outside plant

– Lower performance Noise from existing wiring POTS +reverse powering Bridged taps

– Lower cost


FTTdp economics are very different than FTTnode or FTTcab – Few subscribers per DP – smaller pool of potential customers – FTTdp saves cost of laying fiber those last few hundred meters to

customer – Most cost effective for DPs to have fixed number of ports (not field

upgradeable) Technician installs DP once – no return visit Customer turn-up process without truck roll – “zero-touch” Self-install important aspect of FTTdp

Bottom line – DP must be very low cost for FTTdp to be economically viable – System must support “zero-touch” turn-up of customers and

customer self-install

Economics of FTTdp


FTTdp Standards

Broadband Forum – WT-301: Fiber to the Distribution point Use cases and architecture requirements Supports GPON, p2p Eth, and bonded copper backhaul

– WT-318: Management Architecture and Requirements for FttDP

ETSI TM6 – Reverse power spec. Phase 1 expected completion 2H2014. Includes POTS requirements



Copper Evolution: G.Fast


What is G.fast? Answer: Gigabit over Copper

FTTdp is part of an operators Gigabit services tool kit

FTTN / FTTCab

FTTB/ FTTdp

FTTH/ FTTP

Optical Fiber Metallic Cable

< 1,000m

< 150m $

$ $

$ $ $

DSL acceleration technology – DMT-based like VDSL2/ADSL2+ – Uses wider spectrum to achieve

higher rates (106 MHz or 212 MHz) – Very high rate requires very short

copper loops – FTTdp or FTTB

Gigabit service over Copper – Provisionable (a)symmetric rates

Operational considerations – Customer self-install saves cost – Cost per port sensitivity due to distributed, low density solution

(<16 ports; FTTdp deployed) – VDSL2 and G.fast co-existence consideration – Reverse power saves install cost


Two ways to divide total capacity between upstream and downstream:

– ADSL/VDSL: Frequency Division Duplexing (FDD) Each frequency band assigned to upstream or downstream (not both) Both directions transmit at same time

– G.fast: Time Division Duplexing (TDD) Full frequency band used in both directions Transmission alternates in time between upstream and downstream “Gbps rate” split between upstream and downstream

Duplexing

Frequency (MHz)

DS US DS US DS US DS US

Time (usec) 0 750 1500 2250 3000

… …


Crosstalk is a limiting factor in many DSL deployments – G.fast uses “vectoring” to cancel crosstalk – available on “day 1”

Upstream and downstream G.fast transmission times must be coordinated among all transceivers in binder – Otherwise, near end crosstalk from one transceiver would product

NEXT into another transceiver

G.fast spectrum should be separated from other services in binder – E.g. if VDSL2 from cabinet in same binder

Crosstalk increases at higher frequencies – efficiency of vectoring may be lower for G.fast than VDSL2 – G.fast has ability to do “crosstalk avoidance” or discontinuous

operation

Crosstalk and Spectral Compatibility


Spectral Compatibility

Node Exchange Home Distribution Point (dp)

VDSL2 &

G.fast

Vectored VDSL2

Launched Here

G.fast Launched

Here VDSL2

17 Frequency (MHz)

VDSL 17a Transmit Spectrum

Line 2

17 Frequency (MHz)

G.fast Transmit Spectrum

Line 3

106

Crosstalk 106 Crosstalk

17 Frequency (MHz)

VDSL 17a Transmit Spectrum

Line 1

106 Crosstalk

17 Frequency (MHz)

G.fast Transmit Spectrum

Line 4

106

Crosstalk


Single Line Performance


Standards and availability timeline

Commercial G.fast coming in 2016

Milestone Date Consented standard YE 2013 Approved standard 2H 2014 Proto chipset availability Mid 2014 Proto solution availability 2H 2014 GA chipset availability YE 2014 Field and inter-op trials 2015 Commercial deployment 2016

G.fast PSD (G.9700) approved G.fast PHY/TC (G.9701)

consented December 2013 – Functional, but not full features – Comment resolution should be

completed end of 2014



PON Evolution: XGPON1 & NGPON2


PON Evolution (GPON Family)

GPON – 2.5G downstream, 1.25G upstream – Widely deployed today

XGPON1 – 10G downstream, 2.5G upstream – Wavelength compatible with GPON – Only trial deployments to date – TDM-PON technology (same as GPON)

– NGPON2 – 4-8 λs of TDM-PON (TWDM) 10/10, 10/2.5, 2.5/2.5

– 40-60 km reach / 1:256 split ratio – ONTs require tunable receive filters and tunable

lasers – Standard finalized in 2014 – WDM overlay for special requirements (CPRI)

NGPON2

+

4-8 TDM PON λs

WDM Overlay λs

=


NGPON2 Example Use Case: Multiple service types on same fiber

Ethernet Service (pt2pt)

Residential SFU and MDU Solutions

(TWDM)

Mobile Fronthaul (pt2pt)

Dedicate wavelength to each high value business customer (pt2pt) All residential services could share same wavelength (TWDM)

Power Splitter

(color-less)

ADTRAN Company Confidential ® Adtran, Inc. 2014 All rights reserved