Presentation is loading. Please wait.

Presentation is loading. Please wait.

Building Model-Driven Service Orchestration via a FMO Architecture –Phase II: Traffic-Driven On-Demand Orchestration.

Similar presentations

Presentation on theme: "Building Model-Driven Service Orchestration via a FMO Architecture –Phase II: Traffic-Driven On-Demand Orchestration."— Presentation transcript:

1 Building Model-Driven Service Orchestration via a FMO Architecture –Phase II: Traffic-Driven On-Demand Orchestration

Inspur not a TMF Member; Action: find another Vendor: Rob & Miles--NetScout, Empirix, JDSU, Teoco CEG

3 Scenario: Flash Sale Event, Cloud & Network Capabilities Scaling Synchronously
Global DC1 Global DCn Virtual DC1 vMultiVAS In multi-Data Center deployment of VNFs/ VAS/ Applications context: When Flash Sale Event Creates a temporary spike from APP traffic VNFs/vMultiVAS/Video Apps etc. Scaling Dynamically How Traffic Model Drive to optimize Network capacity accordingly? Virtual DCn Video Apps APP Traffic: 60%? 70%? 80% … APP Traffic: 40%? 20%? 20% … IP Core Video Cache Local Local DC Edge PoP Edge PoP vEPC vEPC vMME vMME

4 Topic 1: Modeling & Model-Driven
Business Case & Requirements Short Time To Market Elasticity /Scalability Shared /Slice Infra for Higher resource utilization OPEN API for ecosystem innovation Business-Service Model BC Model(SLA/Cost/Value) TTM Model Elasticity Model Product Catalog Service Context Model Service Catalog Service Topology Traffic Model Capacity Model Policy Model Service Resource Model Service CFS/RFS Resource Catalog Resource Topology Logical Resource Virtual Resource IT/Cloud Resource Physical Resource Templates & Scripts CloudFormation YANG TOSCA ICT-Formation Resource Model Device Model

5 Topic 1: Modeling & Model-Driven --Traffic Drive Dynamic Orchestration
Traffic Model Capacity Model Elasticity Model Resource Model Business Case Model Templates & Scripts YANG TOSCA Cloud Formation ICT-Formation Policy Model Business Case Model(BC Model) Business Value for Dynamic Service Orchestration Traffic increased and its Financial value Cost Modeling for business planning: Cloud Resource, Network, Power/Location OPEX savings When and how to scale in/out the traffic Capacity across Access, Local DC, Global DC Applicable Time Period, Geographic Place, Capacity Amount... Policy for traffic scaling/steering/reshaping… Policy Rules, Policy Conditions, Policy Action... What/How many Cloud/Network Resource Resource Specification; Resource Options Service/Resource Topology, Business Requirements Modeling Device Model Traffic Pattern/Profile: peak hours, traffic profile of OTT Application Traffic consumption Model: End-User behavior and how the Traffic be consumed by OTT APP. Traffic Generation Model: How the traffic generated by OTT Application for example Traffic Distribution Model: How the traffic distributed across the global network, DC, & Cloud

6 Topic 1: Modeling & Model-Driven -- Traffic to Capability
Stream 1: Traffic to Capability (Long-Term: Forecast/Planning to Capability Ready) Traffic Pattern & Traffic Profile Resource Model Define Traffic Generation Model Micro-Service Orchestrating Behavior End-use App Behavior Policy Model Capacity Model Load Time Traffic Pattern: peak hours, traffic profile… Traffic: 30% Traffic: 50% Traffic: 20% IP Core Traffic Generation Model & Distribution Model Capacity Model: Applicable Time Period, Geographic Place, Capacity Amount... capacity Model Service Topology, Service-resource model…. Service-Resource Model Policy Model: PolicyRules, PolicyConditions, Policy Action...

7 Topic 1: Modeling & Model-Driven -- On-Demand Orchestration
Stream 2: On-Demand Orchestration (Short-Term: Real-time analysis to on-demand orchestrate): Dynamic Orchestrating Cloud DCI Bandwidth & Resource Orchestration for Flash Sale Event Scenarios Traffic Monitoring Traffic Distribution Model Capacity Model Resource Model Define OTT Application Monitoring (APM) Micro-Service Orchestrating Behavior Policy Model Active Monitoring Stream 2 (Dynamic Orchestration) : 6) PM Traffic Monitoring; 7) Digital Service OTT Application Monitoring(APM) 8) Traffic Distribution Model; 9) Service Resource Model; 9) Service Orchestration; 11) Cloud DCI Bandwidth & Resource Orchestration

8 Topic 2: Micro-Service Architecture Practice
FMO component APIs/Interfaces Definitions Application Functions (AFs): Build APIs/Interfaces to support functional composition that allows building bigger applications from other component Application Functions, possibly re-used from a catalog. MCC Functions (MFs) : Build APIs/Interfaces to support for managing the lifecycle processes for the component Security Functions (SFs) : APIs/Interfaces to provide the security features for the component, e.g. to protect the component from malicious access and to ensure the component has the necessary credentials to operate in the system. Environment Functions (EFs):APIs/Interfaces used by the component to access to the infrastructure resources that it needs to support its operation and to realize its functionality Micro-Service Chaining Approach: How to compose micro services for specific business scenarios

9 Topic 2: Micro-Service Architecture Practice --Micro-Services Chaining for Traffic Orchestration Scenarios(1/2) Reference from AT&T: SDN Control & Orchestration Framework 1 Receive order 2 Allocate resources 3 Configure virtual resources 4 Configure network 5 Configure cloud underlay 6 & 7 Configure overlay or forwarding 8 & 9 Configure E2E connectivity 10 Configure info for apps 11 & 12 Configure app

10 Micro-Service Chaining for Traffic Orchestration Scenarios
Topic 2: Micro-Service Architecture Practice -- Micro-Services Chaining for Traffic Orchestration Scenarios(2/2) Dashboard Services Topology View Active Monitoring View Assurance View SSO Micro-Service Chaining for Traffic Orchestration Scenarios E2E ORCH Topology Build Cloud ORCH NFVO SDN ORCH App. ORCH E2E ORCH Service Orchestration Active Monitoring Analytics Based Assurance E2E Service Orchestration Test Controller Real-time Analysis Micro-Service Layer Policy vProbe Forecast & Planning NFVO Application ORCH Catalog vAppProbe Root Cause Analysis SDN ORCH Cloud ORCH Dynamic Inventory Performance mgmt. & Fault management

11 Requirements From Orange

12 Model-driven Hybrid Service Orchestration (TMF ZOOM Project catalyst): Orange use cases

13 Has been delivered in Phase I Catalyst
EPC + dedicated vPGW Use-case description Deployment of vPGW in addition to an existing physical EPC network. The objective is to instantiate a dedicated vPGW as an enrichment of existing dedicated APN offers. Orchestration would fulfill vPGW instantiation, EPC (MME)+Network configuration for a given APN. Benefits and drivers Ensure traffic isolation enhanced per-partner/per-customer vPGW customization Self-parameterization capabilities for the customer requirements/ challenges Limited technical complexity as far as contained traffic to be sustained per vPGW (that can be centralized as well) Compact vPGW to be in the product portfolio of EPC suppliers End-to-end integration to be managed Has been delivered in Phase I Catalyst Orange Labs - Research & Development - presentation title – date

14 Virtualized multiVAS in a multi-country context
Use-case description The use case is focusing on the interworking of physical legacy network elements (MSS, MSC, HLR) with a virtualized multiVAS platform. Use case consists in: the instantiation of vMVAS, the E2E network configuration ensuring 2G/3G VAS features. It includes the virtualization of multi-service platform (SMS GW, MMS GW, voic , WAP GW, USSD GW) and resources sharing between functions according to the traffic workload. At target: Shared Multi-country MultiVAS that offers capacity extension capabilities to several countries Benefits and drivers Hardware savings, dynamic license management requirements/ challenges MVAS to be hosted in shared IT environment at target to maximize benefits To manage the interconnection of the multiVAS platform with peering points associated to legacy mobile circuit & packet core networks + overall E2E configuration. Will be delivered in Phase II Catalyst 2016) Orange Labs - Research & Development - presentation title – date

15 Project Plan Milestone / Deliverables Expected Date of Delivery
Approval from TM Forum 12/22/2015 Face-Face Lisbon TAW on project scope & Plan 2/5/2016 Catalyst Project (Demo) High Level Design 2/29/2016 Catalyst Project Low Level Design 3/20/2016 Demonstration Development 4/15/2016 Demonstration Integration & Release 4/25/2016 ShowCase Presentation SLIDES Release Nice 2016 5/9/2016

16 Thank You



Download ppt "Building Model-Driven Service Orchestration via a FMO Architecture –Phase II: Traffic-Driven On-Demand Orchestration."

Similar presentations

Ads by Google