Vo LTE Use Case Approved Proposal Alternative Proposed

Vo. LTE Use Case (Approved) Proposal Alternative Proposed Release 1 Approach and Model Gil Bullard – AT&T

Vo. LTE Use Case (Approved) 2

Vo. LTE Use Case (Approved) Sequence Diagram 3

Basic Vo. LTE Model for Alternative Proposed Flow 4

Alternative Proposal Release 1 Design Time Model for Vo. LTE VNF Level (TOSCA or HEAT) Service Level (TOSCA) Vo. LTE is modeled as a flat Service structure, comprised of VNFs. Vo. LTE_Edge Service: topology_template: node_templates: v. SBC (VNF): v. PCSCF (VNF): v. SPGW (VNF): v. EPDG (VNF): groups: v. IMS [v. SBC, v. PCSCF] v. EPC [v. SPGW, v. PEDG] 5 v. SBC VNF: v. PCSCF VNF: v. SPGW VNF: v. PEDG VNF: Key: Use a TOSCA grouping to capture the v. IMS and v. EPC constructs. Need to determine if and how this would manifest itself in A&AI (TBD). Service Level (TOSCA) VNF Level (TOSCA or HEAT) Allotted Resource Level (TOSCA)

Alternative Proposal Release 2 Design Time: Construction Proposal Service Level (TOSCA) Vo. LTE_Edge Service: topology_template: node_templates: v. EPC (Service): v. IMS (Service): Key: Service Level (TOSCA) VNF Level (TOSCA or HEAT) “Compile Time” Nesting (For Service Designer Reuse Purposes) v. IMS_Edge Service: topology_template: node_templates: v. SBC (VNF): v. PCSCF (VNF): v. PCSCF VNF: v. SPGW VNF: v. EPC_Edge Service: topology_template: node_templates: v. SPGW (VNF): v. EPDG (VNF): Allotted Resource Level (TOSCA) SDC would support the ability to construct an “upper” Service Definition from other Services definitions. One approach to this would be to use “compile time nesting”. See the next slide for the “distribution time” structure which would be distributed from such a design approach. 6 v. SBC VNF: v. PEDG VNF:

Alternative Proposal Release 2 Design Time: Distribution Proposal Service Level (TOSCA) v. IMS_Edge Service: topology_template: node_templates: v. SBC (VNF): v. PCSCF (VNF): Vo. LTE_Edge Service: topology_template: node_templates: v. SBC (VNF): v. PCSCF (VNF): v. SPGW (VNF): v. EPDG (VNF): groups: v. IMS [v. SBC, v. PCSCF] v. EPC [v. SPGW, v. PEDG] 7 VNF Level (TOSCA or HEAT) v. SBC VNF: v. PCSCF VNF: v. SPGW VNF: v. PEDG VNF: v. EPC_Edge Service: topology_template: node_templates: v. SPGW (VNF): v. EPDG (VNF): “Compile time nesting” results in a substitution mapping at the time of model distribution. At that point the Vo. LTE_Edge Service no longer has a modeling relationship with the v. IMS_Edge or v. EPC_Edge services, but is rather “flattened”. All appropriate model constructs of v. IMS and v. EPC are inherited by Vo. LTE. Note that the v. IMS and v. EPC VNF grouping does remain in the Vo. LTE Model.

Alternative Proposal Release 1 A&AI Instance Model A discussion is needed with A&AI to determine how to model a “group” object, and with SO to verify that it could create such instances in A&AI based on the TOSCA model. If either cannot support, we could perhaps defer the group A&AI instances out of Release 1. v. SBC VNF Instance “X” Vo. LTE_Edge Service Instance “A” v. IMS Group v. PCSCF VNF Instance “X” v. SPGW VNF Instance “X” v. EPC Group v. EPDG VNF Instance “X” 8

Alternative Proposal Vo. LTE_Edge Instantiation Sequencing Model (Assumed) Service Level (TOSCA) Vo. LTE_Edge Service: topology_template: node_templates: v. SBC (VNF): Depends On v. PCSCF (VNF): Depends On v. SPGW (VNF): Depends On v. EPDG (VNF): VNF Level (TOSCA or HEAT) 1 v. SBC VNF: 2 v. PCSCF VNF: 3 v. SPGW VNF: 4 v. PEDG VNF: This is no more than an assumed sequencing, and needs verification. In Release 1 if SO cannot perform generalized model-driven “Service-Level” orchestration, then a custom Vo. LTE workflow would be created that orchestrates the Vo. LTE_Edge VNFs in the proper sequence. 9

Alternative Proposal Vo. LTE_Edge Data Mapping (TBD) This is certainly not the complete set of Input data required by Vo. LTE_Edge, v. SBC, v. PCSCF, v. SPGW, and v. EPDG. This slide is provided for illustrative purposes only. Vo. LTE_Edge Service: topology_template: node_templates: v. SBC (VNF): v. PCSCF (VNF): v. SPGW (VNF): v. EPDG (VNF): Input Attributes: Homing_Solution. v. SBC_Cloud_Zone Homing_Solution. v. PCSCF_Cloud_Zone Homing_Solution. v. SPGW_Cloud_Zone Homing_Solution. v. EPDG_Cloud_Zone Homing Attributes: Homing_Solution. v. SBC_Cloud_Zone Homing_Solution. v. PCSCF_Cloud_Zone Homing_Solution. v. SPGW_Cloud_Zone Homing_Solution. v. EPDG_Cloud_Zone 10 v. SBC VNF: Input Attributes: TBD Assignable Attributes: TBD Configuration Attributes: TBD In Release 1 if SO cannot perform generalized model-driven “Service-Level” data mapping, then a custom Vo. LTE workflow would be created that “just knows” the data mappings that must be performed for each VNF type. v. SPGW VNF: Input Attributes: TBD Assignable Attributes: TBD Configuration Attributes: TBD In Release 1 ONAP there is no automated SNIRO homing, so the user must input the “homing solution” as part of the Vo. LTE_Edge Service instantiation request. v. PCSCF VNF: Input Attributes: TBD Assignable Attributes: TBD Configuration Attributes: TBD v. EPDG VNF: Input Attributes: TBD Assignable Attributes: TBD Configuration Attributes: TBD

Alternative Proposal Release 1 Sequence Diagram (Service Level) - Page 1 11

Alternative Proposal Release 1 Sequence Diagram (Service Level) - Page 2 12

Alternative Proposal Release 1 Sequence Diagram (Resource Level) Designate VF-C to perform the Resource-Level orchestration function in the Release 1 timeframe for Vo. LTE. Because of the “flattened” Vo. LTE model, SO Service-Level Flow in would hand off to the VF-C on a per-VNF basis, and not hand off at the level of v. IMS and v. EPC. This is a change from the sequence diagram on the Approved Vo. LTE Use Case wiki. 13

Alternative Proposal Release 2 Sequence Diagram (Resource Level) Migrate the “Resource Level” runtime functionality from VFC into SO. This should require no additional SO work since the SO “Resource Level” flow is a “generic” model-driven flow. 14

Backup Slides

A&AI Instance Model - v. IMS_Edge Service Instance “A” v. SBC VNF Instance “X” v. PCSCF VNF Instance “X” 16

v. IMS_Edge Instantiation Sequencing (Assumed) Service Level (TOSCA) v. IMS_Edge Service: topology_template: node_templates: v. SBC (VNF): Depends On v. PCSCF (VNF): VNF Level (TOSCA or HEAT) 1 v. SBC VNF: 2 v. PCSCF VNF: This sequencing is no more than an assumed approach, and needs verification. 17

Vo. LTE_Edge Data Mapping (Partial) Inheritence Through Compile Time Nesting Vo. LTE_Edge Service: topology_template: node_templates: v. EPC (Service): v. IMS (Service): 18 Vo. LTE_Edge Service definition inherits the Data Model of v. IMS and v. EPC through “Compile Time” Nesting v. IMS_Edge Service: topology_template: node_templates: v. SBC (VNF): v. PCSCF (VNF): Input Attributes: Homing_Solution. v. SBC_Cloud_Zone Homing_Solution. v. PCSCF_Cloud_Zone Homing Attributes: Homing_Solution. v. SBC_Cloud_Zone Homing_Solution. v. PCSCF_Cloud_Zone v. EPC_Edge Service: topology_template: node_templates: v. SPGW (VNF): v. EPDG (VNF): Input Attributes: Homing_Solution. v. SPGW_Cloud_Zone Homing_Solution. v. EPDG_Cloud_Zone Homing Attributes: Homing_Solution. v. SPGW_Cloud_Zone Homing_Solution. v. EPDG_Cloud_Zone