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

2. VoLTE Use Case (Approved)

3. VoLTE Use Case (Approved) Sequence Diagram

4. Basic VoLTE Model for Alternative Proposed Flow

5. Alternative Proposal Release 1 Design Time Model for VoLTE
VNF Level
(TOSCA or HEAT)
Service Level
(TOSCA)
vSBC VNF:
VoLTE is modeled as a flat Service structure, comprised of VNFs.
vPCSCF VNF:
VoLTE_Edge Service:
topology_template:
node_templates:
vSBC (VNF):
vPCSCF (VNF):
vSPGW (VNF):
vEPDG (VNF):
groups:
vIMS [vSBC, vPCSCF]
vEPC [vSPGW, vPEDG]
vSPGW VNF:
vPEDG VNF:
Service Level
(TOSCA)
VNF Level
(TOSCA or HEAT)
Allotted Resource Level
Key:
Use a TOSCA grouping to capture the vIMS and vEPC constructs. Need to determine if and how this would manifest itself in A&AI (TBD).

6. Alternative Proposal Release 2 Design Time: Construction Proposal
Service Level
(TOSCA)
VNF Level
(TOSCA or HEAT)
vIMS_Edge Service:
topology_template:
node_templates:
vSBC (VNF):
vPCSCF (VNF):
VoLTE_Edge Service:
topology_template:
node_templates:
vEPC (Service):
vIMS (Service):
“Compile Time” Nesting
(For Service Designer
Reuse Purposes)
vSBC VNF:
vPCSCF VNF:
“Compile Time” Nesting
(For Service Designer
Reuse Purposes)
vSPGW VNF:
Service Level
(TOSCA)
VNF Level
(TOSCA or HEAT)
Allotted Resource Level
Key:
vEPC_Edge Service:
topology_template:
node_templates:
vSPGW (VNF):
vEPDG (VNF):
vPEDG VNF:
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.

7. Alternative Proposal Release 2 Design Time: Distribution Proposal
VNF Level
(TOSCA or HEAT)
Service Level
(TOSCA)
vIMS_Edge Service:
topology_template:
node_templates:
vSBC (VNF):
vPCSCF (VNF):
vSBC VNF:
vPCSCF VNF:
VoLTE_Edge Service:
topology_template:
node_templates:
vSBC (VNF):
vPCSCF (VNF):
vSPGW (VNF):
vEPDG (VNF):
groups:
vIMS [vSBC, vPCSCF]
vEPC [vSPGW, vPEDG]
vSPGW VNF:
vPEDG VNF:
vEPC_Edge Service:
topology_template:
node_templates:
vSPGW (VNF):
vEPDG (VNF):
“Compile time nesting” results in a substitution mapping at the time of model distribution. At that point the VoLTE_Edge Service no longer has a modeling relationship with the vIMS_Edge or vEPC_Edge services, but is rather “flattened”. All appropriate model constructs of vIMS and vEPC are inherited by VoLTE. Note that the vIMS and vEPC VNF grouping does remain in the VoLTE Model.

8. 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.
vSBC VNF Instance
Instance “X”
vIMS Group
vPCSCF VNF Instance
Instance “X”
VoLTE_Edge Service Instance
Instance “A”
vSPGW VNF Instance
Instance “X”
vEPC Group
vEPDG VNF Instance
Instance “X”

9. Service Level VNF Level (TOSCA) (TOSCA or HEAT) VoLTE_Edge Service:
Alternative Proposal VoLTE_Edge Instantiation Sequencing Model (Assumed)
Service Level
(TOSCA)
VNF Level
(TOSCA or HEAT)
VoLTE_Edge Service:
topology_template:
node_templates:
vSBC (VNF):
vPCSCF (VNF):
vSPGW (VNF):
vEPDG (VNF): 1
vSBC VNF: 2
vPCSCF VNF:
Depends On 3
vSPGW VNF:
Depends On
Depends On 4
vPEDG 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 VoLTE workflow would be created that orchestrates the VoLTE_Edge VNFs in the proper sequence.

10. Alternative Proposal VoLTE_Edge Data Mapping (TBD)
vSBC VNF:
Input Attributes:
TBD
Assignable Attributes:
Configuration Attributes:
This is certainly not the complete set of Input data required by VoLTE_Edge, vSBC, vPCSCF, vSPGW, and vEPDG. This slide is provided for illustrative purposes only.
vPCSCF VNF:
Input Attributes:
TBD
Assignable Attributes:
Configuration Attributes:
VoLTE_Edge Service:
topology_template:
node_templates:
vSBC (VNF):
vPCSCF (VNF):
vSPGW (VNF):
vEPDG (VNF):
Input Attributes:
Homing_Solution.vSBC_Cloud_Zone
Homing_Solution.vPCSCF_Cloud_Zone
Homing_Solution.vSPGW_Cloud_Zone
Homing_Solution.vEPDG_Cloud_Zone
Homing Attributes:
In Release 1 if SO cannot perform generalized model-driven “Service-Level” data mapping, then a custom VoLTE workflow would be created that “just knows” the data mappings that must be performed for each VNF type.
vSPGW VNF:
Input Attributes:
TBD
Assignable Attributes:
Configuration Attributes:
vEPDG VNF:
Input Attributes:
TBD
Assignable Attributes:
Configuration Attributes:
In Release 1 ONAP there is no automated SNIRO homing, so the user must input the “homing solution” as part of the VoLTE_Edge Service instantiation request.

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

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

13. Alternative Proposal Release 1 Sequence Diagram (Resource Level)
Designate VF-C to perform the Resource-Level orchestration function in the Release 1 timeframe for VoLTE. Because of the “flattened” VoLTE 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 vIMS and vEPC. This is a change from the sequence diagram on the Approved VoLTE Use Case wiki.

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

15. Backup Slides

16. A&AI Instance Model - vIMS
vSBC VNF Instance
Instance “X”
vIMS_Edge Service Instance
Instance “A”
vPCSCF VNF Instance
Instance “X”

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

18. VoLTE_Edge Data Mapping (Partial) Inheritence Through Compile Time Nesting
vIMS_Edge Service:
topology_template:
node_templates:
vSBC (VNF):
vPCSCF (VNF):
Input Attributes:
Homing_Solution.vSBC_Cloud_Zone
Homing_Solution.vPCSCF_Cloud_Zone
Homing Attributes:
VoLTE_Edge Service:
topology_template:
node_templates:
vEPC (Service):
vIMS (Service):
VoLTE_Edge Service definition inherits the Data Model of vIMS and vEPC through “Compile Time” Nesting
vEPC_Edge Service:
topology_template:
node_templates:
vSPGW (VNF):
vEPDG (VNF):
Input Attributes:
Homing_Solution.vSPGW_Cloud_Zone
Homing_Solution.vEPDG_Cloud_Zone
Homing Attributes: