© 2017 TM Forum | 1

TM Forum Live!

2017

Using Future OSS

Orchestration to Enhance

Operations and Service Agility

© 2017 TM Forum | 2

Presenters

Roberto KungSenior Vice President, Network Operations & Performance

Orange

Pierre MullerVice President, OSS & Operations Processes

Orange

Tom ArcherSolution Architect, Future OSS Technical Director

Huawei

© 2017 TM Forum | 3

Future OSS Concepts and Architecture2

1 Orange Strategy and Expectations

Content

Take Away and Benefits3

© 2017 TM Forum | 4

Orange digital transformation strategy plan

Essentials2020

To be always responsive and

in touch with what is essential

for the customer

This implies overall

transformation, in particular for

Operation Agility

A digital, efficient and responsible company

© 2017 TM Forum | 5

Orange expectations

1. Fast adaptation

2. Full automation

3. Openness

Agility

© 2017 TM Forum | 6

1. Fast adaptation

Design

systems

Vendor Software

Product

Incubation

Validation

Collaboration

From 18 months to 6

days

Recipes

Policies

Operator Operation

Package

Recipes

Policies

Design systems:

DesignOps, Model-driven Processes and Catalogue-based Definition

© 2017 TM Forum | 7

2. Full automation

Control Loops, Knowledge Plane, Real-time Analytics, Policy-based Decision

Real-time

Policy

Telemetry

Product Service

ResourceReceipts

Policies

IaaS

controller

Network

controller

Application

controller

Master Service

Orchestrator

Orchestration

Fulfillment Assurance

© 2017 TM Forum | 8

3. Openness

Openness through APIs & Adaptation layer: legacy OSS, Infra, partners

© 2017 TM Forum | 9

Future OSS Concepts and Architecture2

1 Orange Strategy and Expectations

Content

Take Away and Benefits3

© 2017 TM Forum | 10

Future OSS - Achieving the Goals of OSS Agility

Low Agility Features Future OSS Features

Agi

lity

Enab

lers

Rapid Development

Processes

Separated Design, Development, Operations

Hard wired code based processesand definitions

Model-driven processes

DevOps – DesignOps

Open Ecosystem

Proprietary/static APIs

Technology/business based silos

Open APIs Federation of systems

Everything-as-a-Service (XaaS)

OSS Automation

andAutonomics

Limited, low level rule base

Siloed, completely open-loop systems

End to EndClosed Loop Orchestration

AnalyticsPolicy-based decision making

OSS Adaptability

Monolithic systems

Multiple Incompatible Views

Common Information Model/Model Transformation Cloud-based platform

Microservice-based –FMO architecture

“Providing the AGILITY to support digital operations transformation of hybrid networks”

© 2017 TM Forum | 11

Cloud / PaaS

Design Systems

Service Design

Resource Design

Policy Design

Analytics Design

Support SystemsAdaptation

Catalogue Policy Management

Dynamic Inventory

Future OSS High Level Functional Architecture

“Providing the AGILITY to support digital operations transformation of hybrid networks”

• Design Systems enables DevOps and

DesignOps using a Visual Design Studio to

support integrated model development

• Support Systems provide multi-domain

catalogue, dynamic inventory and policy

management, acting as a bridge between

design-time and run-time

• Fulfillment interacts with external order

processes – performing order lifecycle

management and status tracking

• Assurance provides automation tools, and

guides manual operations in the event of fall

out from Orchestration.

• Orchestration leverages the models, policies,

and metadata required to support end-to-end

closed loop fulfillment and assurance.

• Cloud/PaaS provides the cloud-based platform

of the Future OSS

Fulfillment

Pre-Ordering

Order Management

Assurance

Visualization

Operations

OrchestrationData Collection

Analytics

Decision

Implementation

© 2017 TM Forum | 12

Achieving Automation and Autonomics: Closed Loop Operation

Hybrid Network (Cloud, Physical/Virtual Devices and Connectivity)

External Events and

Information

Feed Forward Process

• Data Collection reacts to new

events

• Analytics gathers and generates

context - develops understanding

using knowledge-based

techniques

• Decision adopts one or more

possible courses of action

• Implementation carries out the

action

Based on the OODA Principle

(Observe, Orient, Decide, Act)

Cloud / PaaS

Design Systems

Fulfillment Assurance

Orchestration

Support Systems

Orchestration

Analytics

Decision

Data Collection

Implementation

Observe

Orient(Context Based

Analysis)

Decide(Plan)

Act

Feedback Process

• Analytics, Decision and Implementation may generate direct

feedback/guidance that changes the way that the system reacts to data

• More complex internal loops may be necessary e.g. for self-configuring,

self-healing, self-optimising, and self-protecting behaviour

Policy provides guidance at

each stage

© 2017 TM Forum | 13

Decision

Achieving Automation and Autonomics: Full Automation

Resource State A

Resource State B

Resource State C

Resource State D

Utility = 3

Utility = 2

Utility = 1

Data Collection Analytics Implementation

Orchestration

Resource DType Y State

A

Resource D Type Y State B

Service CType x Goal Policy

Service type x Response Time is < 5s

Goal Policy -resource type y utilisation is < 60%

Event Based Policy – handle resource performance events

Utility Function Policy – Utility (goodness) of state transition A-B = (……..) etc.

Goal Policy - Increase Resource Capacity (change state)

Predictive

Service/ Resource

Performance

Analysis

Resource Performance

Events

dependency

Design and

Configure resource

changes

Test Changes and

Verify associated

policies

Data Collection receives

a series of resource

performance events

Analytics uses event and goal based

policy plus predictive analysis to

anticipate future service issues

Decision creates new goal

and determines optimum

course of action based on

utility function policy and

analysis

Implementation

configures the changes,

and tests and verifies all

related policies

© 2017 TM Forum | 14

Assurance

VisualizationOperations

Analytic Notebooks

Flexible View

PresentationConfiguration

Data Orientation

ProblemManagement

Test & Diagnosis

Incident Management

Orchestration

Data Collection

Analytics

Decision

Implementation

Cloud / PaaS

Design Systems

Fulfillment Assurance

Orchestration

Support Systems

.

.

.

Orchestration loops may need closing through human intervention with progressive automation

1

1. Data Collection and Analytics find a novel situation for which there is no policy based resolution

2

3

2,3. Decision falls out to Operations for human investigation

6

5

4,5,6. Operations applications including Incident and Problem Management, and Test and Diagnostics may be used by teams to address both incident resolution and root cause analysis

4

7. Visualization supports current and historical views and collaborative problem solving

7

8. Design Systems receives updates to policy/analytics

8

Then Orchestration responds to future similar events in an autonomic way based on new policy/historical resolution details

Achieving Automation and Autonomics: Blending Human and Machine Operations

© 2017 TM Forum | 15

Achieving an Open Ecosystem

Co-ordinated knowledge plane distribution supporting control plane interaction

Interface Management

Cloud / PaaS

Design

Systems

Fulfillment Assurance

Orchestration

Support Systems

Cloud / PaaS

Design

Systems

Fulfillment Assurance

Orchestration

Support Systems

Domain 1 Future OSS

Domain 2 Legacy OSSDomain 3 Future OSS

Control Plane

Knowledge Plane

Resource

ManagementFault

Management

Service

Management

Adaptation

Adaptation

▪ Orchestration of multi

domain environment,

between & within CSPs:

▪ Hierarchy of

closed/open loops with

delegation

▪ Intent based processes

▪ Co-ordinated distribution of

the knowledge plane via

▪ Open APIs

▪ Data federation

▪ Common Event Bus

▪ The Knowledge Plane is

formed by the Support

Systems: federated

Catalogue, Inventory, Policy

and cognitive data

© 2017 TM Forum | 16

Future OSS Concepts and Architecture2

1 Orange Strategy and Expectations

Content

Take Away and Benefits3

© 2017 TM Forum | 17

Future OSS in a Nutshell

1. Common Digital Platform for Hybrid Networks and Services

2. Framework Architecture to Enable AGILITY in Digital Operations Transformation

DESIGN SYSTEMSEnabling DevOps & DesignOps

through Model-Driven Design

FULFILLMENTTransforming business requests into

agile and cost effective solutions

ASSURANCEAssuring Service Quality through

a combination of manual and

automated operations

ORCHESTRATIONThe Automation and Autonomics

Engine of hybrid end-to-end

Service Management

SUPPORT SYSTEMSThe bridge supporting hybrid

end-to-end Service Design

(Think, Build) and Service

Operations (Run)

CLOUD / PaaSProviding a Cloud-native,

Dynamic , Secured, Open and

Extensible OSS environment

© 2017 TM Forum | 18

Future OSS key Concepts

• Provides a blueprint from which CSPs can begin

their digital operations transformation

• Enables agility by creating an operating model for

CSPs with intelligent and progressive operational

automation, self-management, and self-

configuration

• Provides a holistic approach that defines the

management of hybrid networks (virtual, physical

and legacy)

• Is a truly cloud-native and resilient platform to

achieve “OSS-as-a-Service”

© 2017 TM Forum | 19

Future OSS White Paper Take Away - Orange

From NetOps to DesignOps

▪ Operations will focus on closing loops with DesignOps utilizing the

Future OSS Design Systems.

▪ Network Operations Teams need to develop new skills with the ability

and appropriate model-driven tools to work on design.

Implementation path

▪ Future OSS provides flexible paths for its own introduction.

▪ To protect existing investments, Future OSS allows current systems

(e.g. Inventory, etc.) to be incorporated through federation.

© 2017 TM Forum | 20

Future OSS Benefits - Orange

For Orange, the Future OSS acts as a standardized

framework that can be adopted by the whole industry,

including CSPs and Open Source communities.

Orange believe ONAP is a good example of an

implementation of part of the Future OSS for

SDN/NFVhttp://carrier-

back.huawei.com/~/media/CNBG/Downloads/Services/SolutionTopic

/oss/OrangeHuaweiFutureOSSWhitePaperfinal.pdf

© 2017 TM Forum | 21

Thank You

Copyright © 2016-17 Orange S.A. and Huawei Technologies Co., Ltd. All rights reserved.No part of this document may be reproduced or transmitted in any form or by any means without prior written consent of Orange S.A.

and Huawei Technologies Co., Ltd.