v CPE Use Case Deep Dive Integration Project

v. CPE Use Case Deep Dive Integration Project and Use Case Subcommittee Sept, 2017

Agenda • Use case overview (Yoav) • Development tasks and test plan (Kang) • Service model and call flows (Gil) 2

Use case overview

Network Enhanced Residential Gateway (NERG) • TR-317 specifies the NERG architecture – in which some of the functionality of a residential gateway (RG) is relocated to the operator's cloud - NERG facilitates simplified operations, as well as additional service offerings, such as personalized services, Smart Home and enhanced multimedia services • With NERG, the functions provided traditionally by the RG are now distributed between an on-site device called a BRG (Bridged Residential Gateway) and a cloud based component, called a v. G (virtual Gateway)

High level architecture • BRG: Bridged Residential Gateway – this is the CPE still located at the residential customer premises, configured as a managed bridge connecting its LAN interfaces and the BRG-LSL interface. • v. G: virtual Gateway – The set of networking and service related Network Functions that are hosted in the NSP network; the v. G is the default IP gateway for the LAN devices. At a minimum, the v. G provides Network Functions for: - The termination of the LSL in the NSP’s network IP address management – DHCP service IP forwarding and IPv 4 NAT capabilities the termination of the WAN interface • v. G-WAN interface: Logical interface(s) on the v. G to one or more IP networks. • LSL: Logical Subscriber Link – the subscriber specific logical point-to-point layer 2 connection between the BRG and the v. G.

NERG-Enabled Services/Capabilities • Enhanced management and troubleshooting • Security services as VAS - Implemented by the activation of a new function in the v. G and traffic steering of relevant traffic to the service chain that has this security function • Automatic access to media content - Extended DLNA • Specific services on a per home-device basis • Smart Home M 2 M • IPv 6 migration

v. CPE Use Case – Amsterdam DCAE (collector) DMaa. P SDNC Control Data + Control Infrastructure Per Customer ONAP OAM Neutron Network v. AAA v. DHCP v. DNS + v. PDHCP Authorization, Authentication, Accounting Dynamic Host Config Protocol 192. 168. 1. 0/24 192. 168. 1. 1 BRG Home Network 1 Home Network 2 192. 168. 1. 0/24 Emulator 1 (VPP) BRG Emulator 2 (VPP) v. G 1 (VPP) v. BNG (VPP) v. G MUX (VPP) 192. 168. 1. 1 v. G 2 (VPP) CPE_PUBLIC Neutron Network Web Server

v. CPE Use Case VNFs Free. Radius ISC BIND https: //freeradius. org/ https: //www. isc. org/downloads/dhcp/ https: //www. isc. org/downloads/bind/ v. AAA v. DHCP v. DNS Authorization, Authentication, Accounting Dynamic Host Config Protocol Vector Packet Processing (VPP) + modifications https: //fd. io/technology/ BRG Emulator (VPP) v. BNG (VPP) v. G MUX (VPP) Apache Web Server 2 v. G (VPP) • All VNFs are open source, no physical components • HEAT Templates produced for all VNFs • TOSCA Templates produced for v. DHCP, v. AAA, and v. DNS Web Server

Multiple ONAP Services Construct the Use Case Control Data + Control Authorization, Authentication, Accounting Dynamic Host Config Protocol v. BNG (VPP) BNG_MUX Neutron Network v. G MUX (VPP) MUX_GW Neutron Network BRG_BNG Neutron Network BRG Emulator 2 (VPP) Per Customer v. DNS + v. PDHCP CPE_SIGNAL Neutron Network BRG Emulator 1 (VPP) Gen. Infra Service v. AAA v. DHCP Infrastructure v. G 1 (VPP) v. G 2 (VPP) CPE_PUBLIC Neutron Network Web Server

Multiple ONAP Services Construct the Use Case Control Data + Control v. AAA v. DHCP CPE_SIGNAL Neutron Network BRG BNG_MUX Service v. BNG (VPP) BNG_MUX Neutron Network v. G MUX (VPP) MUX_GW Neutron Network BRG Emulator 2 (VPP) BRG_BNG Neutron Network Emulator 1 (VPP) Per Customer v. DNS + v. PDHCP Authorization, Authentication, Accounting Dynamic Host Config Protocol Infrastructure v. G 1 (VPP) v. G 2 (VPP) CPE_PUBLIC Neutron Network Web Server

Multiple ONAP Services Construct the Use Case Control Data + Control v. AAA v. DHCP CPE_SIGNAL Neutron Network BRG v. BNG (VPP) v. G_MUX Service BNG_MUX Neutron Network v. G MUX (VPP) MUX_GW Neutron Network BRG Emulator 2 (VPP) BRG_BNG Neutron Network Emulator 1 (VPP) Per Customer v. DNS + v. PDHCP Authorization, Authentication, Accounting Dynamic Host Config Protocol Infrastructure v. G 1 (VPP) v. G 2 (VPP) CPE_PUBLIC Neutron Network Web Server

Multiple ONAP Services Construct the Use Case Control Data + Control v. AAA v. DHCP CPE_SIGNAL Neutron Network BRG v. BNG (VPP) BNG Service BNG_MUX Neutron Network v. G MUX (VPP) MUX_GW Neutron Network BRG Emulator 2 (VPP) BRG_BNG Neutron Network Emulator 1 (VPP) Per Customer v. DNS + v. PDHCP Authorization, Authentication, Accounting Dynamic Host Config Protocol Infrastructure v. G 1 (VPP) v. G 2 (VPP) CPE_PUBLIC Neutron Network Web Server

Multiple ONAP Services Construct the Use Case Control Data + Control v. AAA v. DHCP BRG_EMU Service CPE_SIGNAL Neutron Network BRG v. BNG (VPP) BNG_MUX Neutron Network v. G MUX (VPP) MUX_GW Neutron Network BRG Emulator 2 (VPP) BRG_BNG Neutron Network Emulator 1 (VPP) Per Customer v. DNS + v. PDHCP Authorization, Authentication, Accounting Dynamic Host Config Protocol Infrastructure v. G 1 (VPP) v. G 2 (VPP) CPE_PUBLIC Neutron Network Web Server

Multiple ONAP Services Construct the Use Case Control Data + Control v. AAA v. DHCP CPE_SIGNAL Neutron Network BRG v. BNG (VPP) ONAP configures the Tunnel XC BNG_MUX Neutron Network v. G MUX (VPP) Tunnel. XC Emulator 2 (VPP) ONAP configures the v. G_MUX left IP Address and the VNI for the Vx. LAN tunneling v. CPECust Service ONAP configures the v. G_MUX right IP Address and the VNI for the Vx. LAN tunneling MUX_GW Neutron Network BRG_BNG Neutron Network Emulator PNF 1 (VPP) Per Customer v. DNS + v. PDHCP Authorization, Authentication, Accounting Dynamic Host Config Protocol Infrastructure v. G 1 (VPP) v. G 2 (VPP) CPE_PUBLIC Neutron Network Web Server

Development tasks and test plan

Development Tasks • VNF development • SDC: VNF onboarding and service design • SO: Generic workflows and custom workflows • A&AI: Data schema • DCAE: VES collector and analytics app • CLAMP/DCAE/Policy: Closed loop control • SDNC: Generic and custom APIs • Robot: Emulators and automated test suite 16

Development Tasks Service Modeling and Call Flow Design 17

Development Tasks VPP-based VNF Development (v. BRG, v. BNG, v. GMUX, v. G) Service Modeling and Call Flow Design 18

Development Tasks VNF Onboarding & Service Design in SDC VPP-based VNF Development (v. BRG, v. BNG, v. GMUX, v. G) HEAT/TOSCA Templates Service Modeling and Call Flow Design 19

Development Tasks VNF Onboarding & Service Design in SDC VPP-based VNF Development (v. BRG, v. BNG, v. GMUX, v. G) HEAT/TOSCA Templates DCAE Analytics App DCAE VES Collector Service Modeling and Call Flow Design 20

Development Tasks Closed Loop Design using CLAMP Output: policy + DCAE template VNF Onboarding & Service Design in SDC VPP-based VNF Development (v. BRG, v. BNG, v. GMUX, v. G) HEAT/TOSCA Templates DCAE Analytics App DCAE VES Collector Service Modeling and Call Flow Design 21

Development Tasks BSS Emulator Closed Loop Design using CLAMP Output: policy + DCAE template VNF Onboarding & Service Design in SDC VPP-based VNF Development (v. BRG, v. BNG, v. GMUX, v. G) HEAT/TOSCA Templates Homing Emulator DCAE Analytics App DCAE VES Collector Service Modeling and Call Flow Design 22

Development Tasks Generic & Custom Workflows for SO Update of A&AI Data Schema BSS Emulator Generic & Custom SDNC APIs (Yang & DGs) Closed Loop Design using CLAMP Output: policy + DCAE template VNF Onboarding & Service Design in SDC VPP-based VNF Development (v. BRG, v. BNG, v. GMUX, v. G) HEAT/TOSCA Templates Homing Emulator DCAE Analytics App DCAE VES Collector Service Modeling and Call Flow Design 23

Development Tasks Robot Test Suite Generic & Custom Workflows for SO Update of A&AI Data Schema BSS Emulator Generic & Custom SDNC APIs (Yang & DGs) Closed Loop Design using CLAMP Output: policy + DCAE template VNF Onboarding & Service Design in SDC VPP-based VNF Development (v. BRG, v. BNG, v. GMUX, v. G) HEAT/TOSCA Templates Homing Emulator DCAE Analytics App DCAE VES Collector Service Modeling and Call Flow Design 24

Development Progress • All development tasks are on track to meet M 4 • Tracked in Jira and on wiki https: //wiki. onap. org/display/DW /v. CPE+Design+and+Test+Case s 25

Integration Test Plan Category Test Cases External System Registration T 101: Wind. River Open. Stack VIM Registration VNF Onboarding and Service Creation T 201: Onboard v. DHCP, v. AAA, v. DNS, Web. Server, v. BRG, v. BNG, v. GMux, v. G T 202: v. CPE Service Creation T 203: Closed Loop Configuration T 204: Closed Loop Deployment Service Instantiation and Monitoring T 301: v. CPE Infrastructure Service Instantiation T 302: v. CPE Customer Service Instantiation Closed Loop T 401: v. CPE Auto-healing Service Termination T 501: v. CPE Service Termination • Please give feedback: https: //wiki. onap. org/display/DW/v. CPE+Integration+Test+Case

Service model and call flows

v. CPE Use Case Mapping of SDC Resources to Services Key An “Allotted Resource” is the modeling representation of a “higher order” Service consuming a configuration/capacity allotment (instance) of a “lower order” Service. Resource PNF Network X 6 VNF The mapping of Resources into Services was made such that the Resources associated with a particular Service are those that would naturally be instantiated with the corresponding Service Instantiation request. v. Cpe. Res. Cust Service Allotted Resource Natural order of instantiation, driven in the “real world” by a BSS and/or human intelligence, emulated in the use case by Robot. 1 CPE_SIGNAL BRG_BNG BNG_MUX 5 v. BRG_EMU Service 4 v. Bng. Infra Service MUX_GW Not managed by ONAP in the “real world”, so not modeled in the use case. v. Cpe. Gen. Infra_X Service BNG_MUX Service 2 3 v. GMux. Infra Service 28

v. CPE Use Case Model: v. Cpe. Res. Cust Design & Instance View A more natural modeling of the BRG would be via a “PNF” object type which is supported in SDC but not through model-driven automation in SO and SDC. A proposed Release 2 ONAP feature would support such automation. In such a case, the BRG PNF would have no direct association in the model with the BRG_EMU Service; ONAP would manage the network function as a PNF and not as a VNF. SD CD esi gn /M od el V A& AI/ iew Ins tan ce Vie w The association between an Allotted Resource and its “underlying service” is via a Requirements/Capabilities approach. 29

v. CPE Use Case Model: Supporting Services Design View The BRG_EMU Service is an artificial construct to leverage ONAP to instantiate the BRG Emulator, which is implemented as a VNF in this Use Case. This Service would have no analogue in the “real world”. 30

v. CPE Use Case Model: Supporting Services Design View Main track: Leverage HEAT orchestration to interact with Open. Stack to instantiate the individual VMs, networks, ports, etc. Stretch Goal: Incorporate ARIA into SO to provide TOSCA-driven orchestration to interact with Open. Stack to instantiate the individual VMs, networks, ports, etc. 31

Generic ONAP Processing – VF Module Example Currently in existence in SO are Service-level, Network-level, VNF-level, and VF Modulelevel “generic” orchestration flows. This slide represents the VF Module-level processing flow “Cr. Vf. Module. Infra” and its associated subflow “Do. Create. Vf. Mod. ” The “Client” can be either a manual interaction (via VID) or the SO “generic service-level” workflow. For the v. CPE use case it is the former via Robot. This is referred to as the “a la carte” approach. As a “stretch” goal in Release 1, we want to incorporate ARIA to perform cloud-resource-level orchestration that could alternately be done by HEAT. In this approach, the “VNF Adaptor” determines from the Catalog whether the VF Module is represented as a HEAT or a TOSCA. If the former, the Adaptor maps and passes the parameters to HEAT for processing. If the latter, the Adaptor maps and passes to ARIA for processing based on the corresponding Blueprint. 32

v. CPE Use Case: Automation Support and Data Service 1 Resource 1 a SDNC Northbound API SDNC DG SDNC Inputs SDNC Assignments Pre. Load? SDNC Configuration Cr. Gen. Svc. Instance (A La Carte) -> Do. Create. Service. Instance N/A N/A N/A CPE_PUBLIC (Network) Create. Network. Infra (A La Carte) -> Do. Create. Network VNF-API Generic DG NULL Set cpe_public_net_cidr, cpe_ public_net_id Yes NULL Set “ 1 b CPE_SIGNAL (Network) Create. Network. Infra (A La Carte) -> Do. Create. Network VNF-API Generic DG NULL Set cpe_signal_net_cidr, cpe_signal_net_id Yes NULL Set “ 1 c v. Cpe. Gen. Infra. Vnfs_HEAT (VNF) Create. Vnf. Infra (A La Carte) -> Do. Create. Vnf N/A N/A N/A “ 1 d v. Cpe. Gen. Infra. Vnfs_X (VF Module) Cr. Vf. Module. Infra (A La Carte) -> Do. Create. Vf. Mod VNF-API Generic DG NULL Set cpe_public_net_id, cpe_signal_net_id, onap_private_net_id, vdhcp_name_0, vaaa_name_0, vdns_name_0, vweb_name_0, vdns_private_ip_0 (cpe_public), vdns_private_ip_1 (onap_private), vweb_private_ip_0 (cpe_public), vweb_private_ip_1 (onap_private), vdhcp_private_ip_0 (cpe_signal), vdhcp_private_ip_1 (onap_private), vaaa_private_ip_0 (cpe_signal), vaaa_private_ip_1 (onap_private), Etc…. . (see HEAT) Yes NULL Set We would have preferred to have used the SO “generic service-level” flow, which, triggered by a Service-Level instantiation request from Robot for a given Service (e. g. , v. Cpe. Gen. Infra_X), would automatically decompose it into its component Resources, and orchestrate instantiation of the same. However, in Release 1 we used “pre-load” assignments, which currently isn’t a supported option for this “generic service” approach. In R 2 we would like to extend this use case to leverage dynamic resource assignment along with this “generic service” approach to demonstrate model-driven servicelevel automation for the v. Cpe. Gen. Infra_X, BNG_MUX, v. GMux. Infra, v. Bng. Infra, and BRG_EMU Services. 2 X Order in which Robot will call SO to instantiate the desired Service or Resource. SO Flow v. Cpe. Gen. Infra_X “ Key BNG_MUX “ 2 a BNG_MUX (Network) Cr. Gen. Svc. Instance (A La Carte) -> Do. Create. Service. Instance N/A N/A N/A Create. Network. Infra (A La Carte) -> Do. Create. Network VNF-API Generic DG NULL Set bng_gmux_private_net_cidr, bng_gmux_private_net_id Yes NULL Set 33

Key v. CPE Use Case: Automation Support and Data Service 3 4 Resource v. GMux. Infra X Order in which Robot will call SO to instantiate the desired Service or Resource. SO Flow SDNC Northbound API SDNC DG SDNC Inputs SDNC Assignments Pre. Load? SDNC Configuration Cr. Gen. Svc. Instance (A La Carte) -> Do. Create. Service. Instance N/A N/A N/A “ 3 a MUX_GW (Network) Create. Network. Infra (A La Carte) -> Do. Create. Network VNF-API Generic DG NULL Set mux_gw_private_net_cidr, bng_gmux_private_net_id Yes NULL Set “ 3 b v. GMUX (VNF) Create. Vnf. Infra (A La Carte) -> Do. Create. Vnf N/A N/A N/A “ 3 c Cr. Vf. Module. Infra (A La Carte) -> Do. Create. Vf. Mod VNF-API Generic DG NULL Set bng_gmux_private_net_id, mux_gw_private_net_id, onap_private_net_id, VNI_POOL, vgmux_name_0, vgmux_private_ip_0 (bng_gmux), vgmux_private_ip_1 (onap_private), vgmux_private_ip_2 (mux_gw), Etc… Yes NULL Set Cr. Gen. Svc. Instance (A La Carte) -> Do. Create. Service. Instance N/A N/A N/A v. GMUX (VF Module) v. Bng. Infra “ 4 a BRG_BNG (Network) Create. Network. Infra (A La Carte) -> Do. Create. Network VNF-API Generic DG NULL Set brgemu_bng_private_net_cidr, brgemu_bng_private_net_id Yes NULL Set “ 4 b v. BNG (VNF) Create. Vnf. Infra (A La Carte) -> Do. Create. Vnf N/A N/A N/A “ 4 c v. BNG (VF Module) Cr. Vf. Module. Infra (A La Carte) -> Do. Create. Vf. Mod VNF-API Generic DG NULL Set cpe_signal_net_id, bng_gmux_private_net_id, brgemu_bng_private_net_id, onap_private_net_id, vbng_name_0, vbng_private_ip_0 (brgemu_bng), vbng_private_ip_1 (onap_private), vbng_private_ip_2 (cpe_signal), vbng_private_ip_3 (bng_gmux), Etc…. Yes NULL Set 34

v. CPE Use Case: Automation Support and Data Key X X Service Resource BRG_EMU 5 SO Flow SDNC Northbound API SDNC DG SDNC Inputs SDNC Assignments Pre. Load? SDNC Configuration Cr. Gen. Svc. Instance (A La Carte) -> Do. Create. Service. Instance N/A N/A N/A “ 5 a BRG_EMU (VNF) Create. Vnf. Infra (A La Carte) -> Do. Create. Vnf N/A N/A N/A “ 5 b BRG_EMU (VF Module) Cr. Vf. Module. Infra (A La Carte) -> Do. Create. Vf. Mod VNF-API Generic DG NULL Set vbrgemu_bng_private_net_id, vbrgemu_name_0, Etc… N/A NULL Set BRG_EMU (VNF) [Event Handling] N/A Custom Process [Event Handling; New] N/A N/A Custom_v. Cpe. Res. Cust GENERICRESOURCE Generic DG NULL Set N/A NULL Set Custom_v. Cpe. Res. Cust -> Custom_Tunnel. XConn GENERICRESOURCE Custom Sub-DG [New] [On “Assign”] BRG_WAN_MAC_Address VNI, vgmux_private_ip_2 (mux_gw), vgmux_private_ip_0 (bng_gmux) Yes [On “Create”] Xconn: {vbrgemu_private_ip_0 (vbrgemu_bng), VNI} Custom_v. Cpe. Res. Cust -> Do. Create. Vnf. And. Module -> Do. Create. Vnf GENERICRESOURCE Custom Sub-DG [New] [On “Assign”] VNI, vgmux_private_ip_2 (mux_gw) cpe_public_net_id, mux_gw_private_net_id, onap_private_net_id, Etc… No [On “Activate”] vgw_private_ip_0 (mux_gw), VNI, vgmux_private_ip_2 (mux_gw) Custom_v. Cpe. Res. Cust -> Do. Create. Vnf. And. Module -> Do. Create. Vf. Mod GENERICRESOURCE Custom Sub-DG [New] NULL Set vgw_private_ip_0 (mux_gw), vgw_private_ip_1 (onap_private), vgw_name_0, Etc… Yes NULL Set Custom_v. Cpe. Res. Cust -> Custom_BRG GENERICRESOURCE Custom Sub-DG [New] [On “Assign”] vgmux_private_ip_0 (bng_gmux), VNI, BRG_WAN_MAC_Address NULL Set N/A [On “Activate”] BRG_BNG_IP, VNI, VGMUX_BNG_MUX_IP “ v. Cpe. Res. Cust 6 Order in which Robot will call SO to instantiate the desired Service or Resource. Order in which the custom SO service-level flow instantiates the desired Resource. “ Tunnel. XConn (AR) 6 a “ v. G (VNF) 6 b “ v. G (VF Module) 6 c “ BRG (AR) 6 d The “generic service-level” SO flow currently does not support Allotted Resources or PNFs. In a future release we would like to add this support. 35

s Thank You!