CCVPN use case proposal Cross Domain and Cross

CCVPN use case proposal (Cross Domain and Cross Layer VPN) CMCC, Vodafone, Huawei

Agenda • Use. Case introduction • architecture impact • modeling proposals 2

CCVPN Use. Case proposal https: //wiki. onap. org/display/DW/CCVPN%28 Cross+Domain+and+Cross+Layer+VPN%29+USE+CASE

SOTN Consideration Flexible Networking by area CMCC Basic Network Capability Electrical Crossconnection Matrix The largest scale OTN network Super High-speed plane Northeast high -speed ring West highspeed ring • East highspeed ring Set up 1 Super High-speed+3 high-speed 100 G OTN planes • Realizing fast deployment and • services flexible networking for services in single domain • ASON has been deployed on ITMC and Super High-speed plane Flexible access of any rates of • Efficient 100 G pipe utilization • Protection and restoration for any services • The number of OTN equipment: ~100 thousands • The number of 100 G transceiver: ~ 150 thousands 4

SOTN Consideration CMCC plans to build a new network based on SDN which provides high rate, survivable and flexible service, for high-value customers. International Bureau Overseas transmission International Private Network Metro Network CMRI has completed • SOTN functional specification. • Northbound interface information model. SOTN use cases include • Real-time resource update. • OTN equipment operation and scheduling for different vendors. • Multi-constrained end-to-end route computation. • Multi-domain end-to-end service providing. • Multi-domain network end-to-end survivability. Application ONAP OTN Super Controller (Multi-domain cooperation) We suggest to realize Super controller as a module of ONAP (SDN -C). Northbound Interface Domain Controller A Domain controllers have been developed by OTN vendors OTN Domain A Domain Controller B Domain controller is provided by OTN equipment vendor. OTN Domain B 5

SD-WAN Consideration CMCC plan to provide instant, flexible VPN service for SMB companies. VCPE Overseas transmission VCPE Customer CPE CMCC SD-WAN use cases include • Supply SMB companies with VPN service on demand, instantly, flexibly • Deploy VPN service by overlay mode , untouch carrier network • “One-click open”and “One-stop”, automatically deploy enterprise VPN service • Self-service order for client-side CPE, self-delivery client-side CPE • Provide various value-added service on client-side SD-CPE and cloud side Application/Portal CMCC has completed • SD-WAN system and devices specification. • Several POC sites on pilot network. ONAP Northbound Interface ONAP is reponsible for both VNF orchestration and network orchestration SD-WAN Controller This year CMCC will deploy SDWAN case to carry a few real customer sites Customer CPE v. CPE 6

Priorities: FIRST Priority: Single Domain Orchestration ONAP SOTN Controller In this phase, only a single domain is considered to be orchestrated by ONAP. Main sub-usecases include: Service onboarding, Service design, Service deployment and Self-service. Intel Confidential

Second Priority: Overlay Third-party CPE Addition ONAP SOTN Controller SD-WAN Controller u. CPE SD-WAN controller is added in this phase to realize cross Layer VPN services. Central network can be abstracted into a node from the ONAP view, A scenario example is, to build a connection from an enterprise to DC. v. CPE Intel Confidential

t. HIRD Priority: Cross-domain E 2 E Orchestration ONAP Controller Herein, we take different domains into account. Different domains may be owned by different vendors or for different usage by the same vendor. ONAP should have the ability to orchestrator and automate resource and services from different domain. OTN Network 1 Controller OTN Network 2 Intel Confidential

FOURTH Priority: ONAP Peering Orchestration Between SPs ONAP (CMCC) SOTN Controller ONAP (VDF) SD-WAN Controller v. CPE u. CPE Site SOTN Controller UNI Connection（ E-Line） UNI Site Internet SD-WAN Controller v. CPE Site CPE UNI Connection（ E-Line） The Final Goal of CCVPN use case is to realize connections between different ONAPs. We plan to demo Joint CCVPN Po. C in ONS-EU in Sep. Intel Confidential UNI Site

Service Scenerios Self-service Portal 2 Service BPLM Automatic Discovery Build DG on SDNC by Designer 5 3 Resource 1 Create Topo Instance on A&AI by SDNC Topo Instance 2 Design Service Automation Load Site/VPN YAML to SDC 1 Resource DG Composite Site & VPN to SOTN Service Topo DG Design SOTN workflow Design Resource DG Controller Huawei NCE-T 4 5 Vendor Forward Plane Self-Service portal(To be added) 3 Automatic Deployment Input Parameter from UUI or Portal Cross-Carrier API （To be confirmed）(stretch goal) Automatic BPLM/DG Execution Other Stretch Goals: Auto scaling Fault detection and auto healing Update Instance to A&AI Intel Confidential

Phase 1: network and proposal UUI/Portal SDC ONAP ❷ Client Service Controller for PHY Netconf/Yang DM/API Via APPC/VFC SO ❸ SDNC APPC /VFC External API MEF (Stretch Goal) A&AI ❶ Controller for PHY Netconf/Yang CPE v. CPE In DC CPE v. CPE

Phase II: network and proposal BSS (VDF) BSS (CCMC) ONAP (VDF) ONAP (CCMC) SO-to-SO Interface SO SDC SDNC SO SDNC A&AI Adapter Yang/Netconf 3 rd-Party Controller Service orchestration CPE v. CPE NNI (CMCC) (VDF) SDC

Agenda • Use. Case introduction • architecture impact • modeling proposals 14

Projects may be impacted by CCVPN UUI&Portal: Selfservice Portal External API: ONAP peer orchestration between SPs A&AI: Model for SDC: Physical network resource model& service model, service monitoring and strategy design DCAE: Event POLICY: end to end rerouting from PNFs, end to end rerouting SO&OOF: service PNF and abstract topo, end to end rerouting Orchestration(based on abstract topology), global routing computing SDN-C: resource model for Physical network APPC/VFC: v. CPE deployment &LCM

Agenda • Use. Case introduction • architecture impact • modeling proposals 16

CCVPN ONAP IM proposal service composite into a E 2 E service CCVPN service Service components Site_Enterprise Service CPE VPN_Infra Service Site_DC Service v. CPE

SOTN JSON Sample： VPN_Infra service provision(ACTN Based) URL： http: //x. x: 8181/restconf/data/ietf-eth-tran-service: etht-svc

s 19