Isabelle Morency

MEF, Co-Chair Service Management WG

Veryx, VP of Engineering

The Third Network: LSO, SDN and NFV

2

Market Trends

• Subscribers want more control over their network service – On Demand, Self Service, Elastic, Pay as you Go, Ubiquitous

• Services not bounded to physical interface, single provider – Could begin on a mobile device and end on a VM

– Could begin at one provider and end at a data center

• NFV & SDN are changing how networks are being built – Physical Network Functions Virtual Network Functions

– Layered approach to separate control plane from data plane, software from hardware

3

We have Great Expectations!

I can discover new apps that are instantly available

… delivered with blinding speed over all networks, anywhere

When I need performance, I’ll pay a premium.

Perfect QoS … always on – no excuses

In the future …

4

Today’s Two Modern Data Networks

On-Demand & Ubiquitous Performance & Security

Internet

Lack of Agility No Service Assurance

Imagine a new type of network service combining the best of both worlds and removing the limitations …

5

A New Type of Network Service

• Agile – Delivery of new, dynamic, on-demand services

• Assured – Delivery of performance and security guarantees

• Orchestrated – Delivery of automated service across service providers

What could be the impact on our everyday lives?

6

A New Personal Network Experience

Hotel room At home From your hotel

room

IP-VPN

Home Wi-Fi Hotel Wi-Fi

Connecting . . .

Connect to Third Network

Connected Connecting . . .

Connect to Third Network

Connected

Lifecycle Service Orchestration with

CO/PoP CO/PoP

CO/PoP

In the office

Connecting . . .

Connect to Third Network

Connected

Internet

7

We have some great building blocks

… but separately and collectively they still don’t meet our stated expectations

Do we have anything else?

NFV SDN + +

So, that’s 20 megs for 6 months starting in June, Right?

No, my app needs 100 megs now for

the next 2 hours!!!!

We have an OSS/BSS chasm No standards for automation

Making it a Reality - The Challenge: “Why is it so hard to deliver it Today?”

10

Fulfillment Usage

Info Model

The Reason: Lack of Layered Abstraction

Traditional telecoms operations are often in functional silos

Analytics

Info Model

Assurance

Info Model

Multi-Vendor Ethernet/MPLS Network Domain

Multi-Vendor IP/MPLS Network Domain

Multi-Vendor Optical Transport Network Domain

Info Model

Control

Info Model

Performance

Info Model

What’s needed to deliver the Third Network?

11

Three Major Industry Initiatives

MEF is now standardizing Lifecycle Service Orchestration • With layered abstraction to automate Network as a Service per

layer, starting at Carrier Ethernet layer or domain

Collaborating SDOs

NFV and SDN • Concerned with infrastructure functions & control • Not concerned with network connectivity services businesses

or individuals actually purchase

Lifecycle Service Orchestration

Lifecycle Service Orchestration • This is where the MEF completes the picture …

Network Infrastructure

NFV SDN Existing WAN IP CE 2.0 OTN Existing WAN

Service Definitions, Information Model, APIs

12

Lifecycle Service Orchestration (LSO)

NFV SDN Existing WAN

Network Infrastructure

Service Definitions, Information Model, APIs

LSO

Initial work under way • Defining Lifecycle Service Orchestration functions

• Fulfillment, Performance, Control, Assurance, Usage, Analytics, Security, Policy

• Extending the Information Model: dynamic & protocol independent • Developing Service Orchestration APIs for portals or business

applications as well as for SDN, NFV, existing WAN, where needed

13

Network Operator3

(with User SLA)

Service Provider / Business Applications

Third Network Use Case: Service for Businesses

Head Office Regional Office 1

Data Center

Regional Office 2

Point-to-Point NaaS Multipoint NaaS

User Service Endpoint

User Service Endpoint

Network Operator 2

Self-Service Web Portal

End-to-End Lifecycle Service Orchestration

APIs APIs

Lifecycle Service Orchestration

APIs

Lifecycle Service Orchestration

APIs Lifecycle Service Orchestration

APIs

Network Operator 1

Operator Service

Endpoints

On demand connectivity services seamlessly across multiple providers

User Service Endpoint User Service

Endpoint

14

Third Network Use Case: Services for Cloud

Business Site

Operator Service

Endpoint

User Service

Endpoint

Operator Virtual Connection Operator Virtual Connection

VMs or VNFs

Virtual Service

Endpoint

APIs

APIs

End-to-End Lifecycle Service Orchestration

Lifecycle Service Orchestration

Lifecycle Service Orchestration

End-to-End Network as a Service

APIs

Orchestrated delivery of Cloud applications via on-demand, performance-assured, secure, MEF services

Network Operator (Wide Area Network Provider)

Network Operator (Data Center)

Self-Service Web Portal

Service Provider / Business Applications

APIs

15

MEF Third Network White Paper

http://tinyurl.com/nyhxdem

MEF is Defining

Lifecycle Service Orchestration, Information Models and APIs to deliver network as a service for existing networks, NFV & SDN

implementations enabling agile, assured and orchestrated services