VoLTE remaining requirements Auto & manual Scaling

Slides:



Advertisements
Similar presentations
ETSI NFV Management and Orchestration - An Overview
Advertisements

DPACC Management Aspects
Open Source and Info Models 17 Dec 2015 Bryan Sullivan, AT&T.
Project Tacker Open Platform for NFV Orchestration OPNFV Design Summit.
OPEN-O Approach 1, 2, 3 and 1.5 Discussion in Beijing.
Open-O GS-O Project Proposal
SDN-O LCM for Mercury Release Key Points and Overview
Open-O SFC.Mgr Proposal
ONAP Management Requirements
ARC: Definitions and requirements for SO/APP-C/VF-C discussion including call notes Chris Donley July 5, 2017.
Orchestration and Controller Architecture Alignment Vimal Begwani AT&T
Rationalizing ONAP Architecture for R2 and Beyond Vimal Begwani – AT&T
Open Network Automation Platform (ONAP) Controller Architecture Proposal DRAFT.
Usecase Subcommittee Meeting
Defining ONAP APIs With BSS/OSS
ONAP Architecture Meeting 8/8
Mapping between NFV model and TOSCA
Enterprise vCPE September 27, 2017.
ONAP SDC VoLTE Model Support
Orchestration and Controller Alignment for ONAP Release 1
ONAP Architecture Slides Current Plan of Record
ONAP Multi-VIM/Cloud Long Term Architecture and Use Cases (Under Community Discussion across Use Case, Optimization Framework, OOM,
OPEN-O Modeling Directions (DRAFT 0.6)
Tina Tsou, Bryan Sullivan,
ETSI NFV: IFA & SOL specifications list
VNF Package CSAR for ONAP Release 2 – adding Telco grade features Andrei Kojukhov, PhD, Amdocs Oct 6, 2017.
Change Log VNF Package Model Business Compute Req.
VoLTE VNF Descriptor gaps
ONAP and SD-WAN Integration Proposal
Alla Goldner (outcomes from brainstorming meetings) Sept, 2017
ARC: Definitions and requirements for SO/APP-C/VF-C discussion Chris Donley Date , 2017.
ONAP Architecture Meeting 8/8
OPEN-O Modeling Directions (DRAFT 0)
ONAP SDC TOSCA Import Gap Analysis
VoLTE Use Case (Approved) Proposal Alternative Proposed Release 1 Approach and Model Gil Bullard – AT&T.
17 Dec 2015 Bryan Sullivan, AT&T
ONAP Optimization Framework - HAS Shankar Narayanan - AT&T Labs Research 08/15/2017.
Enterprise vCPE use case requirement
Beijing Release use cases/requirements for endorsement/approval
Enterprise vCPE use case requirement
Deployment Flavor Model – Challenges and Emerging trends for ONAP adaptation Priya TG, NetCracker Technology.
Enhanced Platform Awareness (EPA) Alex Vul Intel Corporation
VF-C R2 Feature Planning & Implementation Yan Yang
Enterprise vCPE use case requirement
Usecase 1 – Upgrade Image
Nov, 2015 Howard Huang, Huawei Julien Zhang, ZTE
ONAP Amsterdam Architecture
Christopher Donley Prakash Ramchandran Ulas Kozat
Scaling Use Case Proposal.
Documenting ONAP components (functional)
DPACC Management Aspects
Casablanca Platform Enhancements to Support 5G Use Case Summary of Planned Enhancement Areas 5G Use Case Team May 16, 2018.
Multi-VIM/Cloud High Level Architecture
Management and Orchestration in Complex and Dynamic Environment
Casablanca Platform Enhancements to Support 5G Use Case Summary of Planned Enhancement Areas (TSC Review) 5G Use Case Team May 10, 2018.
Defining ONAP VNF Package Model
ONAP Architecture for Rel 1
VNF Package Model Per ETSI NFV SOL001, SOL004, SOL005
IFA007: VNF LCM The Or-Vnfm reference point is used for exchanges between Network Functions Virtualization Orchestrator (NFVO) and Virtualized Network.
Casablanca Platform Enhancements to Support 5G Use Case Summary of Planned Enhancement Areas (TSC Review) 5G Use Case Team May 10, 2018.
Open Source MANO (OSM) develop an Open Source MANO software stack aligned with ETSI NFV ISG
Open Source Projects Collaborations with ONAP
Casablanca Platform Enhancements to Support 5G Use Case Summary of Planned Enhancement Areas (TSC Review) 5G Use Case Team May 10, 2018.
SOL003 Adapter Architecture, Technical Debt and Roadmap
GNFC Architecture and Interfaces
ONAP Optimization Framework (OOF) POC for Physical CellID (PCI) Optimization July 30, 2018.
Latest Update on Gap Analysis of Openstack for DPACC
Casablanca Platform Enhancements to Support 5G Use Case Summary of Planned Enhancement Areas 5G Use Case Team May 10, 2018.
Casablanca Platform Enhancements to Support 5G Use Case Summary of Planned Enhancement Areas 5G Use Case Team May 10, 2018.
Proposed Approach for ONAP Runtime Support of Network Service Onboarding Gil Bullard, AT&T.
Presentation transcript:

VoLTE remaining requirements Auto & manual Scaling Proposal

General This proposal is to suggest the feature auto & manual scaling to be implemented in R2. Missing features which were not implemented in R1. R46: VNF auto scaling is merged from Capacity based scaling and Policy driven scaling. R47: VNF manual scaling (in/out) is a new feature. Other Reqs are existed in R1 (stretch goal), but not implemented yet. Req Id Functional Requirement Priority as initially submitted Source / Use Case New Component / Enhancement Comments R46 VNF autoscaling (in/out) 3 VoLTE Enhancement Merged from Capacity based scaling and Policy driven scaling. R47 VNF manual scaling (in/out) Manual scaling triggered from portal. R48 Configuration audit R49 Resource dedication This came out of one of the other use cases. It’s the capability to specify constrains on VNFs (e.g. this VNF needs to be on it’s own dedicated server) R50 Policy driven/optimal VNF placement R51 Framework for integration with OSS/BSS

R46: VNF auto scaling (in/out) – Description, Flow Description: VNF auto scaling is based on policies. The input of the policy can be either application aspect events/conditions (e.g. subscriber capabilities ,call loss rate) or non-application aspect events/conditions (e.g. CPU usage). The ONAP platform should be able to perform scaling of any VNF that supports scaling, in all flavors/levels supported by the VNF Portal SDC/CLAMP DCAE/Holms/Policy/VF-C EMS/VNF VIM&NFVI 1. Policy design, distribute and activation. 2.1. Report/collect application aspect data 2.2. Report/collect non-application aspect data 3. Trigger VNF auto scaling

R46: VNF auto scaling (in/out) – VNF capabilities Any dependencies on specific VNF capabilities VNF should support scaling in different flavors/levels VNF/EMS should support the monitoring of the metrics which are used by auto-scaling policies VNFs that we would use to test the use cases VNFs in VoLTE usecase: MME, SAE-GW, CSCF, AS Companies willing to contribute China Mobile, ZTE, Huawei

R47: VNF manual scaling (in/out) – Description, Flow Auto-scaling can trigger the scaling operation based on the real-time state of a VNF instance. But it cannot cover all operators’ requirements of scaling. For example, on holidays or in large activities, auto-scaling cannot provide an immediate response to the huge growth of traffic. Manual scaling provide the capability of VNF scale in/out triggered by operators based on predicted demand. the ONAP platform should be able to perform scaling of any VNF that supports scaling, in all flavors/levels supported by the VNF Portal SO VF-C 3rd VNFM VIM/NFVI 3rd EMS/VNF 1. Manually trigger scaling operation 2. Scaling in/out 3. Operate scaling in/out

R47: VNF manual scaling (in/out) – VNF capabilities Any dependencies on specific VNF capabilities VNF should support scaling in different flavors/levels VNFs that we would use to test the use cases VNFs in VoLTE usecase: MME, SAE-GW, CSCF, AS Companies willing to contribute China Mobile, ZTE, Huawei

References ETSI GS NFV-MAN 001 —— “B.4 VNF instance scaling flows” describes flows of scaling. The scaling use case is grouped in 3 categories, auto-scaling, on-demand scaling and scaling based on management request. Auto-scaling and on-demand scaling refer to the scaling triggered by VNFM/EMS/VNF automatically, related to R46. Scaling based on management request refers to the scaling triggered by some senders (OSS/BSS/operators) manually, related to R47. http://www.etsi.org/deliver/etsi_gs/NFV-MAN/001_099/001/01.01.01_60/gs_NFV-MAN001v010101p.pdf ETSI IFA 005, 006, 007 define the stage 2 specifications of Or-Vnfm, Or-Vi, Vnfm-Vi interfaces; ETSI SOL 003 defines the stage 3 specifications of Or-Vnfm interface; http://www.etsi.org/standards, http://www.etsi.org/deliver, Openstack defines the VIM NBI APIs; https://developer.openstack.org/api-guide/quick-start/ OASIS TOSCA defines the VNF Descriptor in TOSCA Format VoLTE use case support EPA capabilities

Thanks