KPN's ision on and stept to reach fully programmable telco ......Sep 04, 2019 · 11 MC location MC...
Transcript of KPN's ision on and stept to reach fully programmable telco ......Sep 04, 2019 · 11 MC location MC...
-
KPN's Vision On and Steps to Reach On a Fully Programmable Telco Network
Michel GeensenKPN
-
2
Future vision on the network infrastructure architecture
A programmable network architecture
Lower costs
Higher capacity
Realtimefunctionality
Enhanced circularity
Increased continuity
Ambitions
Impactlesschanges
Technology
Bu
sin
ess
& O
pe
rati
on
s
SoftwareDefined
Open
DistributedDisaggregate
-
3
The programmable network architecture vision
Fully automated
▪ Intent driven, model based, closed loop
Virtualised functions
▪ Network and application functions
Programmable infrastructure
▪ VNF offload
Software Defined
-
4
The programmable network architecture vision
Content and services
▪ CDN, 3rd party
Network and application functions
▪ Flexible placement towards the edge
Topology
▪ Leaf-spine
Distributed
-
5
The programmable network architecture vision
Hardware and Software
▪ Decoupled lifecycles
Forwarding and Control
▪ Independent scaling and placement
Network hardware / software
▪ Modularity and flexibility
Disaggregated
-
6
The programmable network architecture vision
Open interfaces
▪ All layers
▪ Standardised, public specifications
Open source
▪ Software and hardware
▪ Leverage communities
Open
-
7
Building blocks for an open programmable network architecture
▪ CORD and NG-SDN are key building blocks for an open programmable network architecture
▪ CORD: datacenter concepts applied to central office, flexibility in service and function placement / creation
▪ NG-SDN: programmable network layer introduced => VNF off-loading and flexible data plane
▪ Not only applicable to CO(RD)
CORD / NG-SDN (Open Networking Foundation)
www.opennetworking.org/cord/
CORD NG-SDN
www.opennetworking.org/ng-sdn/
https://www.opennetworking.org/cord/https://www.opennetworking.org/ng-sdn/
-
8
Building blocks for an open programmable network architecture
Stratum (Open Networking Foundation)
-
9
Building blocks for an open programmable network architecture
P4 (Open Networking Foundation / P4.org)
-
10
A Programmable Network Architecture
Overview
Residential
Business
Mobile
@
wholesale
Voice
TV
Internet
Mobile
BBU
DSLAM
FIBER
Open, automated, programmable network resource layer
End-to-end automation of network services and operation
-
11
MC location
MC area
CORE
A programmable ‘Central Office’ architecture
▪ Programmable, disaggregate ‘CO’
▪ Combines CORD and NG-SDN
▪ Leaf – Spine topology (local and remote leaves)
▪ Spines are service agnostic
▪ Multi-homed access nodes (edge resilience)
▪ Separation of control and forwarding
▪ ONOS controller
▪ Programmable forwarding plane (VNF off-loading)
▪ STRATUM / P4
▪ Fixed – Mobile convergence
▪ Data plane: transport efficiency
▪ Control plane: reduction of functions
leaf leaf
leaf
services
compute
storage
spine spine
leaf leaf
leafleaf
Fixedaccess
Mobile access
Mobile access
Fixedaccess
Mobile access
redundancy
ONOS
BNG
VPN-C
PGW
L2XC-C SRV6
SRv6
STRATUM
SRv6
STRATUM
SRv6
SRV6
STRATUM
SRV6
STRATUM
SRV6
STRATUM
SRV6
STRATUM
STRATUMSTRATUM
SRV6 SRV6
SRV6
STRATUM
HAG
HAG-C
VPN L2XCBNG HAG
VPN L2XC
PGW
BNG HAG
VPN L2XC
PGW
BNG-C PGW-C
-
12
Use cases under development
▪ Programmable traffic filtering & replication
▪ Network traffic received via optical splitters
▪ Specific filtering functions (L3 … L7 headers)
▪ Specific forwarding functions (tagging, replication)
▪ interested and authorized receivers
Intercept & Monitoring
Tofino
gRPC (P4 pipeline)REPLICATEFILTER
Intercept
Mon.1
Mon.2
Mon.3
simplecontroller
-
13
Use cases under development
▪ IP VPN: baseline functionality for central office
▪ Multi-vendor / multi-chip setup: Barefoot Tofino + Broadcom
▪ Two approaches: custom pipeline + predefined pipeline
▪ Separate ONOS instances to avoid conflict
▪ Custom pipeline: custom app for pipeline control
▪ Predefine pipeline: modified version of segment routing app
▪ Separate app for configuration of NOS based border leaf
▪ NetConf
Programmable ‘central-office’: IP VPN
BF TOFINO
STRATUM
VPN KPN
MPLS
CORE
ONOScontroller
SR+app
BLapp
ONOScontroller
KPNVPN
BF TOFINO
STRATUM
BRCM
NOS
VPN
BRCM
OFDPA
VPN
BF TOFINO
STRATUM
VPN
leaf
leaf
leaf
spine
p4rt
gNMIgNMI
p4rt
netconf
openflow
p4rt MPLS
KPN
-
14
Use cases under development
Programmable ‘central-office’: Hybrid Access
BF TOFINOBF TOFINO
STRATUM
GTP
µONOScontroller
HAGapp
P4
RT
P4
RT
F/M Session
mgmr
PPP
LB
‘P4
’ Sig
na
llng
RADIUS
InternetRG
▪ Hybrid: fixed and mobile access
▪ Programmable forwarding plane
▪ Barefoot Tofino (initial development on Tofino model)
▪ STRATUM: P4RT to control pipeline
▪ ONOS based control plane
▪ HAG app to program forwarding state
▪ Separate session manager application to avoid session signalling impact on ONOS
▪ CUPS – like architecture
▪ In band ‘P4’ signalling channel (to be used for both fixed and mobile)
▪ State control interface (using P4RT interface of STRATUM)
▪ In development on Tofino model, porting to HW planned
▪ SW model key in development
STRATUM
P4
RT
P4
RT
LB Sessionmgmr
‘P4
’ Sig
na
llng
gN
MI
gN
OI
gN
MI
gN
OI
Development and Testing in Virtual
Environment
Acceptation Tests and Production in Hardware
Environment
-
15
KPN Fabric Simulation for Fabric & Function development
Based on similar ONF developments within for example µONOS, Atomix etc
FabricFrameworkController
FabricFrameworkController API
FabricFrameworkController Service
resources
Fabric ServiceFabric Service
FabricSet
1
1
1
2
2
2
3
3
3
deploy
Fabric Service
Controller
FabricSwitchSet ServiceFabricSwitchSet Service
FabricSwitchSet
deploy
1
1
1
2
2
2
3
3
3
FabricSwitchSet Service
Controller
µONOSSet ServiceµONOSSet Service
µONOSSet
deploy
1
1
1
2
2
2
3
3
3
µONOSSet Service
Controller
µONOSSet ServiceµONOSSet Service
ControlAppSet
deploy
1
1
1
2
2
2
3
3
3
Control Application Service
Controller
Kubernetes Controller(s)
Test execution Client
-
16
The programmable network architecture
The programmable network architecture is software defined, distributed, disaggregate and open in nature.
Open interfaces and open (source) specifications are key building blocks
▪ ONF CORD, ONOS, NG-SDN, STRATUM
▪ OCP
Development started on different of use cases
▪ Research / PoC stage, baseline for next steps
Further development through community effort
-
Thank You