The VFC You Dont Know Yang VFC PTL

The VF-C You Don’t Know Yang VF-C PTL June 20 th , 2018

Architecture Facts – Overall Positioning VF-C in ONAP Beijing Architecture 2

Architecture Facts – Overall Positioning VF-C mapping to ETSI NFV-MANO Architecture VF-C provides an ETSI NFV compliant NFV-O function, generic VNFM , NS/VNF Catalog, NFV Instances DB NFV Orchestrator(NFVO) 3

Architecture Facts – SVNFM Integration for Vo. LTE Use Case In Vo. LTE Use Case, VF-C integrated with three vendor’s VNFMs NFVO VNFM Driver A VNFM Driver B Define the VNFM Driver Northbound APIs VNFM X VNFM B Vendor VNFM Driver x VIM Vendor VNF 4

Architecture Facts – GVNFM Integration for CPE Use Case GVNFM Driver layer to make the design flexible NFVO GVNFM Driver GVNFM simple VNF Simple VNF Opensource VNF VIM 5

Architecture Facts – Direct Mode VIM Integration Support direct mode via Multi. Cloud NFVO 1 Grant Request GVNFM 2 Grant Response 3 Resource Request Multi. Cloud Open. Source VNF Opensource VNF Siimple VNF VIM VIM 6

Architecture Facts – Indirect Mode VIM Integration Support indirect mode via VIM-Proxy NFVO VIM-Proxy 1 Grant Request 4 Resource Request 2 Grant Response VNFM A 3 Resource Request Multi. Cloud VNFM B VNFM C Vendor VNF VIM VIM 7

Architecture Facts – Close Loop Integration DCAE Onset Clear DMaa. P ③ ④ Holmes Policy DMaa. P VNF Fault VES Collector VM Fault ⑤ Restart VNF Fault Correlation ② EMS Driver does: 1. Collect VNF FCAPs from vendor EMS 2. Translate FCAPS data into VES format 3. Report Data to VES Collector 8 Action Execution VF-C NS LCM EMS Driver Integration with Policy to execute policy action ⑥ VNF Fault ① Vendor EMS 7 VNF VNF 8

Inside View of VF-C Architecture Network service life cycle management Unified NS/VNF package storage Indirect Mode Vim Proxy Unified Workflow APIs EMS FCAPS collection VNF life cycle management 9

Modeling Facts – Unique RT Project Supporting R 2 VNFD UUI VNF Requirements R 2 ONAP VNF CSAR VNFSDK VVP VNF CSAR Heat Template Simple REST APIs HOT Flow TOSCA Flow VID SO A&AI SDC VNF CSAR VF-C APP-C Multi. Vim SDN-C

Modeling Facts – Providing Flexibility in VNFD for SVNFM topology_template: node_templates: VNF: type: tosca. nodes. nfv. VNF properties: descriptor_id: cscf_si_onap cscf: type: tosca. nodes. nfv. Vdu. Compute properties: name: cscf description: . . oam. Cpdeth 1: type: tosca. nodes. nfv. Vdu. Cp properties: layer_protocol: [ ipv 4 ] description: External connection point requirements: lb. Cpdeth 1: type: tosca. nodes. nfv. Vdu. Cp properties: layer_protocol: [ ipv 4 ] description: External connection point requirements: ………… Unified VNFD VNFM Driver A VNFM A SVNFD VNFM Driver B VNFM B SVNFD Vendor VNFM Driver x VNFM X SVNFD VIM Vendor VNFSDK

Relations to Other ONAP Project ONAP A&AI Common services SO Inventory UUI Inventory Data CURD SDC Policy NS LCM NFVO NS/VNF package VNFM Driver GVNFM Report. FCAPS DCAE Create/Del/. . VL Multi-VIMl Create/Del/. . Virtural resource Opensource VNF EMS Driver Simple VNF Create/Del/. . VNF Vendor’s VNFM Vendor VNF Collect. FCAPS VNF Vendor’s EMS Opensource VNF VIMs Vendor VNF 12

Relations to Other ONAP Project – Overlapping? Complementing! SO (Heat ) VF-C (Tosca) Function VNF Creation VNF Instantiation VNF Termination VNF Deletion SO APP-C (Heat) VNF Scaling Note: Different template VF-C Service Orchestration E 2 E Service Orchestration Network Service Orchestration Function APPC VF-C Resource Configuration Ansible、Chef、Rest. Conf etc Rely on third-party EMS to do service configuration Note: Different Orchestration Scope Note: Different configuration solution 13

Relations to Other ONAP Project – Overlapping? Complementing! VF-C Integrates with APPC solution VNF Life Cycle Management Service Configuration Invoke APPC VF-C Pass Conf Para APPC DG VNF LCM Telnet Vendor VNFM Vendor EMS VNF VNF configuration VNF 14

Commercial Solution on the way 15

Use Case：Vo. LTE Deployment based on ONAP Amsterdam Preparation 1、Resources： City. A-Core DC 01 v. TAS v. I/SCSCF v. PCRF v. HSS v. MME • Hardware/VIM software ready； • 4 logical VIMs ready • DC interconnection ready; 2、VNF Commercial Products： City. B-Edge DC 01 City. C-Edge DC 01 City. D-Edge DC 01 v. SBC v. SPGW • 华为：PCRF, HSS, SBC • 中兴：MME, SPGW • 诺基亚：I/S-CSCF, TAS 3、Network Planing： • Core DC deploy control plane NE: CSCF、TAS、 PCRF、HSS、MME； • v. IMS v. EPC 3 Edge DC deploy data plane NE: SBC、SPGW；

Main Features For Vo. LTE Case Demo – Overview Key features: Model Design, Service Deployment, Control-loop (Auto-healing)、Fault/Performance Collection。 Model Design Service Deployment • • • VNF Onboarding NS Design • • Instantiation Termination • • Alarm Correlation Policy Mapping Triger Healing Vo. LTE v. SBC v. PCSCF v. I/SCSCF v. TAS IMS Vo. LTE v. SPGW v. EPDG v. PCRF v. HSS v. MME EPC VNF Instantiation VNF Destruction FCAPS Control-loop Auto Healing • • Fault Collection Performance KPI collection

s Thanks

VF-C APIs SO Policy UUI Os-Ma-nfvo NFVO Package NSVNF Package ( VNFD) ( NSD) Instantiate Terminate NFVO Northbound APIs • Reference ETSI SOL 005 Os-Ma-nfvo • Currently, NFVO Support NS Lifecycle Management including NS instantiate, scale, heal, query and terminate Scale Operate Heal Or- Vnfm Driver SVNFM Vi-Vnfm Or-Vi VNF Package ( VNFD) GVNFM Driver EMS Multi-Cloud Vi-Vnfm NFVI&VIM NFVO southbound APIs • Reference ETSI SOL 003 Or-Vnfm • Currently, support VNF lifecycle Management including VNF deploy, scale, heal, query and terminate Note: GVNFM only supports VNF deploy and terminate, will support more operation in future release 19