Service Design Onboarding Amdocs Open Network Alla Goldner

Service Design & Onboarding Amdocs Open Network Alla Goldner Director, Technology, Strategy and Standardization, Amdocs

Service Lifecycle Management DESIGN—ONBOARDING 2 ORCHESTRATE OFFLINE IN LAB CONTINUOUS REAL-TIME FULFILMENT OPERATE REAL-TIME IN PRODUCTION REAL TIME OPERATION

Identifying the critical path Design time Real time Service Delivery Service onboarding process today Service Development 3 Months 6 Months 9 Months Analysis Service Design Test & De-bug Packaging Instantiate & configure Service development is constrained by the speed of the Network Engineering create, test and debug cycle – typically a very manual, document-based and time-consuming process 3

Identifying the critical path Design time Real time Service Delivery Service onboarding automation Service onboarding process today Service Development 4 3 Months 6 Months 9 Months Analysis Service Design Test & De-bug Packaging Instantiate & configure Analysis Vendor VNF Onboarding Service Design Test & Debug Packaging Instantiate & configure ONAP Service Design and Create (SDC) will address the service development agility : • Highly Automated design of new and updated services and virtual resources • Auto-readiness for rapid service launch

ONAP Architecture E – Services ONAP Portal Operational Functions External Data Movement & APIs Dashboard OA&M Operation Administration & Maintenance Design Functions Ordering Channels Active & Available Inventory Service Orchestrator Common Services, Data Movement, Access Control & APIs Recipe/Engineering Rules & Policy Distribution Data Collection & Analytics Service Design & Creation Policy Creation Analytic Application Design ONAP Controller Storage Compute Networking VNFs / Applications 5 Integration API OSS Controllers Engineering Rules & Inventory Big Data

Service Development life cycle VNF 1 Onboarding 2 Design VNF Endpoint VNF Workflow VNF 6 Operations 5 Distribution Policies Debug and re -design Packaging Testing 3 4 ISSUE Debug and redesign ISSUE 6 VNF Self Service Portal Service Orchestrator Active & Available Inventory VNF EP READ Y EP VNF Policies / Workflow

What's the challenge A development toolset for non-developers Reusable Multiple users Collaborate and build Model Release and distribute Different Systems Tested Service Orchestrator Active & Available Inventory 7

What needs to be modeled Model ( metadata ) for: • Composition of service including its topology – that an orchestrator will process and enrich by details of placement, IP Address allocation, number of VMs per VNF etc. • Life cycles such as instantiate, configure, delete, test, heal (reboot, recreate, migrate), scale, backup, restore, patch / upgrade, snapshot - a description of workflows, monitoring( KPIs, Events) and policies required by orchestrators or other components to fulfil, repair or manage a service or resource • Policies - Decisions made during the planning or deployment of services or resources 8 Connecting two branch offices through corporate VPN

ONAP 9

ONAP 10

ONAP 11

ONAP 12

ONAP 13

ONAP 14

ONAP 15

ONAP 16

ONAP 17

ONAP 18

ONAP Portal ONAP 19

ONAP Portal ONAP 20

ONAP Portal ONAP 21

ONAP Portal ONAP 22

ONAP 23

ONAP 24

ONAP 25

ONAP 26

ONAP Portal 27

ONAP 28

ONAP 29

ONAP 30

ONAP 31

ONAP 32

ONAP 33

Summary - Service Design and Create (SDC) ONAP - service development automation Business challenges • Today’s systems cannot define new services in hours • Service design is time consuming (9 -12 months typical) and costly with low levels of automation Solution – service development automation • Simplify and accelerate service composition with intuitive drag-and-drop interface • Lower design costs through re-use of modular components • De-risk service introduction and adaptation through automated test and debug loop 34

Thank you