Post on 15-Sep-2018
Event SponsorsSeminar Series Sponsor
Daniel Bar-LevDirector Certification and Strategic Programs
MEF
Orchestrated Network Services with LSO, SDN and NFV
2
Service: NFV Fora perspective
Orchestrator
Application
Public Internet
3
Service: “Open” Fora perspective
Telstra PCCW Global HKTTelstra
International
ControllerController ControllerController
Orchestrator
Application
4
TelstraInternational HKTPCCW GlobalTelstra
Controller Controller Controller Controller
Orchestrator
Application
OrchestratorOrchestrator Orchestrator
Service: SPs’ perspective - Federation
5
Customer perspective
Desire: Click to Activate
Reality: Either… Or…
Facetime, Skype, GotoMeeting, WebEx, Lync, Zoom etc…
6
Service Operations Problem Definition
Infrastructure Layer
Control & Management Layer
Application Layer Business Application
Network Services
Infrastructure Layer
Management & Control Layer
Network Services
Northbound API
Eastbound API
ENNI
Southbound API
BSS/OSSBSS/OSS
Southbound API
CEN Operator 1CEN Operator 2
7
LSO and Programmatic Control
To programmatically control a service, one needs to know:
1. What it is– Abstraction to standard basic components
– Formal information model defining service constructs
2. What is the Architecture– Topology, Federated Orchestration Framework
3. What Products are available– Product Catalog, Availability, Feasibility, Commercials
4. What can I do– APIs to operate the service: Activate, Modify, Monitor, Cease
8
The Three Fundamental Vectors
Orchestration Architecture (LSO)The “WHO & WHERE”
Pro
cess
Lif
ecyc
le
The
“H
OW
” E-LAN
IP-V
PN
Clo
ud
E-Line
Inquiry
Ordering
Provisioning
SOAM
Billing
USE CASES
BUSINESS
PROCESSES
INFORMATION
MODELS
DATA
MODELS
APPLICATION
PROGRAMMING
INTERFACES
TE
RM
IN
OL
OG
Y
EX
TE
RN
AL
C
OL
LA
BO
RA
TIO
N
Project Methodology
PROOF OF
CONCEPT
BUSINESS REQUIREMENTS
MULTI–DOMAIN
ETHERNET
SERVICES
Service Assurance
Service Orchestration
Service Agility
Architecture
Services
Management
Process
Do
mai
ns
of
Exp
ert
ise
10
LSO Reference Architecture
Network Infrastructure
CustomerApplication Coordinator
Element Control and Management
Infrastructure Control and Management
Service Orchestration Functionality
PRESTO(SOF:ICM)
ALLEGRO(CUS:SOF)
LEGATO(BUS:SOF)
CANTATA(CUS:BUS)
Element Control and Management
Infrastructure Control and Management
ADAGIO (ICM:ECM)
LEGATO(BUS:SOF)
PRESTO(SOF:ICM)
ADAGIO (ICM:ECM)
INTERLUDE (SOF:SOF)
SONATA(BUS:BUS)
Business Applications
Business Applications
Service Orchestration Functionality
11
Generic Service Lifecycle Process
MEF 50
Process model for the generic Carrier Ethernet service lifecycle
• Service Operations Lifecycle management
• Product Lifecycle management
• Based on TM Forum SID
12
Service Operations Areas and Projects
• Lifecycle Service Orchestration Reference Arch.• Ethernet Service Lifecycle Process Model (MEF 50)
• Ethernet Product Catalog• Ethernet Ordering• Ethernet Network Resource Provisioning• Ethernet Performance Reporting Framework
(MEF 52)
• Ethernet Service Qualification Questionnaire (MEF 53)
• Ethernet Serviceability• Ethernet Interconnect Point
Bold text indicates published MEF spec.
Service OperationsCommittee
Lifecycle Management Partnership Management
13
Performance Reporting Framework (MEF 52)
• Real-Time vs. Ticket based
• Multi-Level/Multi-Domain
• Different views for Customer/SP/Operator
Steps for achieving transparent management
Agreement on what to measure
Agreement on how to measure
Agreement on how to present
Agreement on how to share
1
2
3
4
36.1
35.1
52
Steps for achieving transparent management
Agreement on what to measure
Agreement on how to measure
Agreement on how to present
Agreement on how to share
“Dial-tone” for the Third Network
1
2
3
4
36.1
35.1
52
16
Project Mapping
Orchestration Architecture (LSO)The “WHO & WHERE”
Pro
cess
Lif
ecyc
le
The
“H
OW
” E-LAN
IP-V
PN
Clo
ud
E-Line
Inquiry
Ordering
Provisioning
SOAM
Billing
MEF 5236.1
36.1
17
Network Resource Provisioning APIs: Single Operator
• Service– EVC: EVPL
• Decomposition– EVC segments
• Flow domains– Forwarding groups
• Network– Technology group
18
Network Resource Provisioning APIs: Multi-Operator
• Service– EVC: EVPL
• Decomposition– Multi-operator
• Flow domains– Forwarding groups
• Network– Technology groups
– Multi-operator
• First OpenSource project – Agile Development
19
Information Model – LEGO ™
20
Service Abstraction (E-Line)
21
Information Model – Meccano ™
22
Common Information Model
• LEGO parts do not fit Meccano models (and vice versa).
• Makes integration cumbersome/impossible.
• You can buy Meccano parts in Lego stores.
• But you can’t mix the parts together.
We need an Industry-Wide Common-Information-Model (MEF CIM project)
23
LSO – Multi-Domain Reference Architecture
OM
CustomerApplication Coordinator
Element Control and Management
Infrastructure Control
and Management
Service Orchestration Functionality
PRESTO(SOF:ICM)
ALLEGRO(CUS:SOF)
LEGATO(BUS:SOF)
CANTATA(CUS:BUS)
Element Control and Management
Infrastructure Control
and Management
ADAGIO (ICM:ECM)
LEGATO(BUS:SOF)
PRESTO(SOF:ICM)
ADAGIO (ICM:ECM)
INTERLUDE (SOF:SOF)
SONATA(BUS:BUS)
Business Applications
Business Applications
Service Orchestration Functionality
T-API(ONF)
OpenFlow (ONF)
Intent (ONF)
NRP/SCA(MEF)
Ordering(MEF)
Performance Reporting
(MEF)
ODL/ONOS
TOSCA
TIP(TMF)
(IETF)(OPNFV)
(ETSI)
OCC
24
Industry Wide Alignment
OM
CustomerApplication Coordinator
Element Control and Management
Infrastructure Control
and Management
Service Orchestration Functionality
PRESTO(SOF:ICM)
ALLEGRO(CUS:SOF)
LEGATO(BUS:SOF)
CANTATA(CUS:BUS)
Element Control and Management
Infrastructure Control
and Management
ADAGIO (ICM:ECM)
LEGATO(BUS:SOF)
PRESTO(SOF:ICM)
ADAGIO (ICM:ECM)
INTERLUDE (SOF:SOF)
SONATA(BUS:BUS)
Business Applications
Business Applications
Service Orchestration Functionality
Information Model and Specifications
Reference Architecture
Process Flows
25
Service Operations Committee Future Projects
• Partner Relationship management– Automation of services
• Industry Standards Alignment– Ethernet service billing specifications
• Future Technology– SDN
– NFV
– On-Demand Services (e.g. Dynamic Responsive Ethernet)
• Interaction with other MEF committees– Provide contributions to the technical, marketing, and certification committees
Q&A
Event SponsorsSeminar Series Sponsor
Daniel Bar-LevDirector Certification and Strategic Programs
MEF
Orchestrated Network Services with LSO, SDN and NFV