1. vCPE Use Case Deep Dive Integration Project and Use Case Subcommittee
Sept, 2017

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

3. Use case overview

4. 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 vG (virtual Gateway)

5. 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.
vG: virtual Gateway – The set of networking and service related Network Functions that are hosted in the NSP network; the vG is the default IP gateway for the LAN devices. At a minimum, the vG provides Network Functions for:
The termination of the LSL in the NSP’s network
IP address management – DHCP service
IP forwarding and IPv4 NAT capabilities
the termination of the WAN interface
vG-WAN interface: Logical interface(s) on the vG 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 vG.
This bridge conforms to IEEE 802.1D [3] and 802.1Q [4] and consequently supports MAC learning.
Hence local traffic is switched locally, not hair-pinned to the vG.
BRG-LAN interface: Interface(s) on the BRG for connecting LAN devices (i.e. in the home).
BRG-LSL interface: Logical layer 2 interface on the BRG facing the vG.
vG-LSL interface: Logical layer 2 interface on the vG facing the BRG.

6. NERG-Enabled Services/Capabilities
Enhanced management and troubleshooting
Security services as VAS
Implemented by the activation of a new function in the vG 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 M2M
IPv6 migration

7. vCPE Use Case – Amsterdam
DCAE
(collector)
DMaaP
SDNC
Control
Infrastructure
Data + Control
Per Customer
ONAP OAM Neutron Network
vDHCP
Dynamic Host Config Protocol
vAAA
Authorization, Authentication, Accounting
vDNS + vPDHCP
/24
Home Network 1
BRG
Emulator 1 (VPP)
vG1
(VPP)
CPE_PUBLIC
Neutron Network
vBNG
(VPP)
vG MUX
(VPP)
Web Server
Home Network 2
BRG
Emulator 2
(VPP)
vG2
(VPP)
/24

8. vCPE Use Case VNFs All VNFs are open source, no physical components
ISC
FreeRadius
BIND
vDHCP
Dynamic Host Config Protocol
vAAA
Authorization, Authentication, Accounting
vDNS
Vector Packet Processing (VPP) + modifications
Apache Web Server 2
BRG
Emulator (VPP)
vBNG
(VPP)
vG MUX
(VPP)
vG (VPP)
Web Server
All VNFs are open source, no physical components
HEAT Templates produced for all VNFs
TOSCA Templates produced for vDHCP, vAAA, and vDNS

9. Multiple ONAP Services Construct the Use Case
Control
Infrastructure
Data + Control
Per Customer
GenInfra Service
vDHCP
Dynamic Host Config Protocol
vDHCP
Dynamic Host Config Protocol
vAAA
Authorization, Authentication, Accounting
vAAA
Authorization, Authentication, Accounting
vDNS + vPDHCP
vDNS + vPDHCP
CPE_SIGNAL
Neutron Network
CPE_SIGNAL
Neutron Network
BRG
Emulator 1 (VPP)
vG1
(VPP)
Neutron Network
BRG_BNG
Neutron Network
MUX_GW
CPE_PUBLIC
Neutron Network
CPE_PUBLIC
Neutron Network
vBNG
(VPP)
vG MUX
(VPP)
Web Server
Web Server
BNG_MUX
Neutron Network
BRG
Emulator 2
(VPP)
vG2
(VPP)

10. Multiple ONAP Services Construct the Use Case
Control
Infrastructure
Data + Control
Per Customer
vDHCP
Dynamic Host Config Protocol
vAAA
Authorization, Authentication, Accounting
vDNS + vPDHCP
CPE_SIGNAL
Neutron Network
BRG
Emulator 1 (VPP)
vG1
(VPP)
Neutron Network
BRG_BNG
Neutron Network
MUX_GW
BNG_MUX
Service
CPE_PUBLIC
Neutron Network
vBNG
(VPP)
vG MUX
(VPP)
Web Server
BNG_MUX
Neutron Network
BNG_MUX
Neutron Network
BRG
Emulator 2
(VPP)
vG2
(VPP)

11. Multiple ONAP Services Construct the Use Case
Control
Infrastructure
Data + Control
Per Customer
vDHCP
Dynamic Host Config Protocol
vAAA
Authorization, Authentication, Accounting
vDNS + vPDHCP
CPE_SIGNAL
Neutron Network
vG_MUX
Service
BRG
Emulator 1 (VPP)
vG1
(VPP)
Neutron Network
BRG_BNG
Neutron Network
MUX_GW
Neutron Network
MUX_GW
CPE_PUBLIC
Neutron Network
vBNG
(VPP)
vG MUX
(VPP)
vG MUX
(VPP)
Web Server
BNG_MUX
Neutron Network
BRG
Emulator 2
(VPP)
vG2
(VPP)

12. Multiple ONAP Services Construct the Use Case
Control
Infrastructure
Data + Control
Per Customer
vDHCP
Dynamic Host Config Protocol
vAAA
Authorization, Authentication, Accounting
vDNS + vPDHCP
CPE_SIGNAL
Neutron Network
BRG
Emulator 1 (VPP)
BNG
Service
vG1
(VPP)
Neutron Network
BRG_BNG
Neutron Network
BRG_BNG
Neutron Network
MUX_GW
CPE_PUBLIC
Neutron Network
vBNG
(VPP)
vBNG
(VPP)
vG MUX
(VPP)
Web Server
BNG_MUX
Neutron Network
BRG
Emulator 2
(VPP)
vG2
(VPP)

13. Multiple ONAP Services Construct the Use Case
Control
Infrastructure
Data + Control
Per Customer
vDHCP
Dynamic Host Config Protocol
vAAA
Authorization, Authentication, Accounting
vDNS + vPDHCP
BRG_EMU
Service
CPE_SIGNAL
Neutron Network
BRG
Emulator 1 (VPP)
BRG
Emulator 1 (VPP)
vG1
(VPP)
Neutron Network
BRG_BNG
Neutron Network
MUX_GW
CPE_PUBLIC
Neutron Network
vBNG
(VPP)
vG MUX
(VPP)
Web Server
BNG_MUX
Neutron Network
BRG
Emulator 2
(VPP)
vG2
(VPP)

14. Multiple ONAP Services Construct the Use Case
Control
Infrastructure
Data + Control
Per Customer
vDHCP
Dynamic Host Config Protocol
vAAA
Authorization, Authentication, Accounting
vDNS + vPDHCP
vCPECust
Service
ONAP configures the Tunnel XC
CPE_SIGNAL
Neutron Network
BRG
Emulator 1 (VPP)
PNF
vG1
(VPP)
vG1
(VPP)
Neutron Network
BRG_BNG
Neutron Network
MUX_GW
CPE_PUBLIC
Neutron Network
vBNG
(VPP)
vG MUX
(VPP)
Web Server
BNG_MUX
Neutron Network
TunnelXC
BRG
Emulator 2
(VPP)
vG2
(VPP)
ONAP configures the vG_MUX right IP Address and the VNI for the VxLAN tunneling
ONAP configures the vG_MUX left IP Address and the VNI for the VxLAN tunneling

15. Development tasks and test plan

16. 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

17. Service Modeling and Call Flow Design
Development Tasks
Service Modeling and Call Flow Design

18. Development Tasks VPP-based VNF Development (vBRG, vBNG, vGMUX, vG)
Service Modeling and Call Flow Design

19. Development Tasks VNF Onboarding & Service Design in SDC
VPP-based VNF Development (vBRG, vBNG, vGMUX, vG)
HEAT/TOSCA Templates
Service Modeling and Call Flow Design

20. Development Tasks VNF Onboarding & Service Design in SDC
VPP-based VNF Development (vBRG, vBNG, vGMUX, vG)
HEAT/TOSCA Templates
DCAE Analytics App
DCAE VES Collector
Service Modeling and Call Flow Design

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

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

23. Development Tasks Generic & Custom Workflows for SO BSS Emulator
Homing Emulator
Update of A&AI Data Schema
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 (vBRG, vBNG, vGMUX, vG)
HEAT/TOSCA Templates
DCAE Analytics App
DCAE VES Collector
Service Modeling and Call Flow Design

24. Development Tasks Robot Test Suite Generic & Custom Workflows for SO
BSS Emulator
Homing Emulator
Update of A&AI Data Schema
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 (vBRG, vBNG, vGMUX, vG)
HEAT/TOSCA Templates
DCAE Analytics App
DCAE VES Collector
Service Modeling and Call Flow Design

25. Development Progress All development tasks are on track to meet M4
Tracked in Jira and on wiki /vCPE+Design+and+Test+Case s

26. Integration Test Plan Category Test Cases External System Registration
T101: WindRiver OpenStack VIM Registration
VNF Onboarding and Service Creation
T201: Onboard vDHCP, vAAA, vDNS, WebServer, vBRG, vBNG, vGMux, vG
T202: vCPE Service Creation
T203: Closed Loop Configuration
T204: Closed Loop Deployment
Service Instantiation and Monitoring
T301: vCPE Infrastructure Service Instantiation
T302: vCPE Customer Service Instantiation
Closed Loop
T401: vCPE Auto-healing
Service Termination
T501: vCPE Service Termination
Please give feedback:

27. Service model and call flows

28. vCPE Use Case Mapping of SDC Resources to Services
VNF
Network
Allotted Resource
PNF X
Natural order of instantiation, driven in the “real world” by a BSS and/or human intelligence, emulated in the use case by Robot.
Key
An “Allotted Resource” is the modeling representation of a “higher order” Service consuming a configuration/capacity allotment (instance) of a “lower order” Service.
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. 6
vCpeResCust Service
BRG_BNG
BNG_MUX
MUX_GW
CPE_SIGNAL 1
vCpeGenInfra_X Service
Not managed by ONAP in the “real world”, so not modeled in the use case.
vBRG_EMU Service 5
BNG_MUX Service
vBngInfra Service 2 4
vGMuxInfra Service 3

29. vCPE Use Case Model: vCpeResCust 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.
SDC Design/Model View
A&AI/Instance View
The association between an Allotted Resource and its “underlying service” is via a Requirements/Capabilities approach.

30. vCPE 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”.

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

32. Generic ONAP Processing – VF Module Example
Currently in existence in SO are Service-level, Network-level, VNF-level, and VF Module-level “generic” orchestration flows. This slide represents the VF Module-level processing flow “CrVfModuleInfra” and its associated subflow “DoCreateVfMod.”
The “Client” can be either a manual interaction (via VID) or the SO “generic service-level” workflow. For the vCPE 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.

33. vCPE Use Case: Automation Support and DataX
Order in which Robot will call SO to instantiate the desired Service or Resource.
Key
vCPE Use Case: Automation Support and Data
Service
Resource
SO Flow
SDNC Northbound API
SDNC DG
SDNC Inputs
SDNC Assignments
Pre-Load?
SDNC Configuration
vCpeGenInfra_X
CrGenSvcInstance (A La Carte) -> DoCreateServiceInstance
N/A “
CPE_PUBLIC (Network)
CreateNetworkInfra (A La Carte) -> DoCreateNetwork
VNF-API
Generic DG
NULL Set
cpe_public_net_cidr,
cpe_ public_net_id
Yes
CPE_SIGNAL (Network)
cpe_signal_net_cidr,
cpe_signal_net_id
vCpeGenInfraVnfs_HEAT (VNF)
CreateVnfInfra (A La Carte) -> DoCreateVnf
vCpeGenInfraVnfs_X (VF Module)
CrVfModuleInfra (A La Carte) ->
DoCreateVfMod
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)
BNG_MUX
BNG_MUX (Network)
bng_gmux_private_net_cidr,
bng_gmux_private_net_id 1 1a 1b 1c 1d
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., vCpeGenInfra_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 R2 we would like to extend this use case to leverage dynamic resource assignment along with this “generic service” approach to demonstrate model-driven service-level automation for the vCpeGenInfra_X, BNG_MUX, vGMuxInfra, vBngInfra, and BRG_EMU Services. 2 2a

34. vCPE Use Case: Automation Support and DataX
Order in which Robot will call SO to instantiate the desired Service or Resource.
Key
vCPE Use Case: Automation Support and Data
Service
Resource
SO Flow
SDNC Northbound API
SDNC DG
SDNC Inputs
SDNC Assignments
Pre-Load?
SDNC Configuration
vGMuxInfra
CrGenSvcInstance (A La Carte) -> DoCreateServiceInstance
N/A “
MUX_GW (Network)
CreateNetworkInfra (A La Carte) -> DoCreateNetwork
VNF-API
Generic DG
NULL Set
mux_gw_private_net_cidr,
bng_gmux_private_net_id
Yes
vGMUX (VNF)
CreateVnfInfra (A La Carte) -> DoCreateVnf
vGMUX (VF Module)
CrVfModuleInfra (A La Carte) ->
DoCreateVfMod
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…
vBngInfra
BRG_BNG (Network)
brgemu_bng_private_net_cidr,
brgemu_bng_private_net_id
vBNG (VNF)
vBNG (VF Module)
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…. 3 3a 3b 3c 4 4a 4b 4c

35. vCPE Use Case: Automation Support and DataX
Order in which Robot will call SO to instantiate the desired Service or Resource.
Key
Order in which the custom SO service-level flow instantiates the desired Resource.
vCPE Use Case: Automation Support and Data
Service
Resource
SO Flow
SDNC Northbound API
SDNC DG
SDNC Inputs
SDNC Assignments
Pre-Load?
SDNC Configuration
BRG_EMU
CrGenSvcInstance (A La Carte) -> DoCreateServiceInstance
N/A “
BRG_EMU (VNF)
CreateVnfInfra (A La Carte) -> DoCreateVnf
BRG_EMU (VF Module)
CrVfModuleInfra (A La Carte) ->
DoCreateVfMod
VNF-API
Generic DG
NULL Set
vbrgemu_bng_private_net_id,
vbrgemu_name_0, Etc…
BRG_EMU (VNF) [Event Handling]
Custom Process [Event Handling; New]
vCpeResCust
Custom_vCpeResCust
GENERIC-RESOURCE
TunnelXConn (AR)
Custom_vCpeResCust -> Custom_TunnelXConn
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}
vG (VNF)
Custom_vCpeResCust -> DoCreateVnfAndModule -> DoCreateVnf
[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),
vgmux_private_ip_2 (mux_gw)
vG (VF Module)
Custom_vCpeResCust -> DoCreateVnfAndModule -> DoCreateVfMod
vgw_private_ip_0 (mux_gw),
vgw_private_ip_1 (onap_private),
vgw_name_0, Etc…
BRG (AR)
Custom_vCpeResCust -> Custom_BRG
vgmux_private_ip_0 (bng_gmux), VNI, BRG_WAN_MAC_Address
[On “Activate”] BRG_BRG_BNG_IP, VNI,
VGMUX_BNG_MUX_IP 5 5a 5b 6 6a 6b 6c 6d
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.

36. Thank You!