path from ce 2.0 to third network services roadmap - mef · transit wavelength internet access l3...
TRANSCRIPT
Sponsored by:
Bruno GiguèreDirector, Product Marketing, MEF
Path from CE 2.0 to Third Network Services Roadmap
60 min
2
Agenda
MEF’s Carrier Ethernet and other Third Network Services
1
Lifecycle Service Orchestration (LSO)
2
From Technical Specifications to MEF Products
3
3
MEF – Advancing the Industry
4
Third Network Services
Third NetworkServices
Orchestrated Services
E-Line E-LAN E-Tree E-AccessSECaaS
E-Transit
Internet Access L3 VPNs IP TransitWavelength
AppServices
5
How the MEF Defines Connectivity Services• Subscriber Services consist of:
– User to Network Interfaces (UNIs)
• Demarcation between Service Provider and Subscriber
– “Virtual Connections” (VC) at or between UNIs
– UNI, “VC”, and “VC End Point” Service Attributes
• Operator Services consist of:
– UNI(s)
– External Network to Network Interfaces (ENNIs)
• Demarcation between Operators
– “VCs” at or between the UNI(s) or ENNI(s)
– UNI, ENNI, “VC”, and “VC End Point” Service Attributes
Service ProviderUNI
“VC”
UNI
Service Provider
Operator
UNI
“VC” “VC”UNI
ENNI
For Ethernet Services, “VCs” are EVCs or OVCs
EVC: Ethernet Virtual Connection OVC: Operator Virtual Connection
6
The Journey to Third Network Services
• MEF’s initial focus on Ethernet “Layer 2” Services
– MEF Ethernet Services defined independently of the Layer 1 network used to transport them
• E.g., Ethernet Private Line can be transported over SONET/SDH, OTN, or IEEE 802.3 Layer 1 network
• Initial MEF work focused on automating and orchestrating MEF Ethernet services
– Info Models, YANG modules, LSO APIs, etc.
To offer agile, assured and orchestrated Third Network Services, MEF standardizes the service model for Layer 1 and Layer 3 services
7
Some Service Delivery Permutations
• Service Provider may deliver:– Layer 1 Service, e.g., Optical Wavelength Service (OWS)
• Delivered over an OTN Layer 1 transport
– MEF Layer 2 Ethernet Service, e.g., EPL
• Delivered over a SONET/SDH Layer 1 transport
– IP (Layer 3) Service, e.g., Internet Access
• Delivered over a Carrier Ethernet access network over IEEE 802.3 Layer 1 transport
OWS over OTN
MEF standardizes the service model for each of the three network layers to facilitate automation and orchestration
SONET/SDHEPL
IEEE 802.3EVPL
Internet Access
8
Goal to Standardize and Unify Service Components to Simplify Modeling and APIs
• UNI
– Service end point and demarcation between subscriber and service provider
– Model it using common attributes that different “values” depending whether it is for an IP Service, Ethernet Service or L1 Service
• ENNI
– Service end point and demarcation between operators
– Model it using common attributes that different “values” depending whether it is for an IP Service, Ethernet Service or L1 Service
• “VC”
– Term to describe the interconnection of two demarcation points
– EVC/OVC for Ethernet services, IPVC for IP Services, “L1VC” not yet created
• “VC End Point”
– Term to describe the “VC” capabilities at a particular service end point, e.g., UNI or ENNI
MEF Carrier Ethernet 2.0 Services
10
MEF Carrier Ethernet 2.0
• Current Generation of MEF Services
• Carrier Ethernet delivers 3 powerful features:
– Standardized Multi- Class of Service
– Interconnected CENs
– Manageability
• Globally adopted connectivity service framework
• Foundation for agile, assured and orchestrated connectivity services
11
CE 2.0 Attributes
CE 2.0 Multi-CoS• Industry’s first standardized Multi-CoS
application & distance-oriented Performance Objectives for Next Gen SLAs
• Enables new level of network efficiency, responsiveness for enterprises & MBH
CE 2.0 Interconnect• Integrates autonomous, CE networks, as a single
regional/global network
• Wholesale Service simplifies lowers costs, adds revenue
CE 2.0 Service Management• Automated management brings scalability
• 3 Recent/New Specs for SOAM, FM/PM
• New Metrics
UNI
EVC1
CoS 410 Mbps CIR for VoIP
CoS 2
20Mbps CIR for VPN data traffic
68Mbps for Internet AccessEVC2
CoS 62 Mbps CIR for control
CE 2.0 Class of Service Extensions
UNI
Retail Provider’s CE Network
UNI
Cloud
ENNI
WholesaleAccess Network
CE Exchange
ENNI
12
CE 2.0 Retail Services Types
E-Line
• Ethernet Private Lines (EPL)
• Ethernet Virtual Private Lines (EVPL)
• Ethernet Internet Access
E-LAN
• Multipoint L2 VPNs
• Transparent LAN Service
• Multicast Networks
• EP-LAN, EVP-LAN
E-Tree
• Rooted Multi-Point L2 VPNs
• Traffic Segregation
• EP-Tree, EVP-Tree
UNI
Point-to-Point EVC
UNI
Rooted Multi-point EVC
UNI
UNI
UNI
Multi-point to Multi-point EVC
UNI
UNIUNI UNI
MEF E-Access and E-Transit
The Wholesale Ethernet Game-Changer
14
What is an MEF E-Access Service?• Retail Service Provider buys E-Access services to reach off-net customer locations
• Wholesale Access Provider sells E-Access services to provide access to locations on its network
• ENNI is point of interconnection between Retail and Wholesale providers
End-to-End Carrier Ethernet Service
E-Access Service
CE
UNI
CE
ENNIUNIEnd User
Subscriber Headquarters
End User Subscriber Branch Site
Carrier Ethernet Network Carrier Ethernet Network
ON-NET CUSTOMER LOCATIONS
OFF-NET CUSTOMER LOCATIONS
Retail Service Provider – The Buyer(Has relationship with end-customer)
Wholesale Access Service Provider – The Seller(Provides Access to remote customer location)
16
New CE 2.0 E-Transit Services
• Key Characteristics of an E-Transit Service:
• Connects two or more CENs together using an Operator Virtual Connection (OVC)
• External Network Network Interfaces (ENNIs) at the CEN boundaries
• Point-to-Point or Multipoint-to-Multipoint OVCs provide the connectivity
• Can support all EVC-based services (i.e., ‘Private’ and ‘Virtual Private’)
• Multi-CoS capable
• Service OAM support
CE
UNI
CE
ENNIUNI
End User Subscriber
Headquarters
End User Subscriber Branch Site
Carrier Ethernet Network(CEN)
CENENNI
E-Access ServiceE-Transit Service
(E-Line)
End-to-End Carrier Ethernet Service
CEN
MEF Layer 1 Services Project
19
Layer 1 Service Definitions and Attributes Project
• Industry Challenge: No standard definition of Layer 1 Services
– Layer 1 services broadly available but lack standardized service attributes
– Lack of standardized ENNI results in ad hoc operator interconnects
• Project: Define Service Attributes for Managed Layer 1 Services
– End-to-end (subscriber) and inter-provider (operator) service attributes
• Analogous to EVC/UNI and OVC/UNI/ENNI attributes for Carrier Ethernet
• Why do this?
– Enable on-demand, dynamic Third Network Layer 1 services
• Requires standardized APIs and orchestration across network domains
– Enable on-demand, dynamic Layer 1 service creation and assurance
MEF IP Project
23
IP Service Attributes Project
• Industry Challenge: No standard definition of IP Services
– IETF defines a lot of control plane technology
– Little consideration of how to operationalize (particularly inter-provider)
• Project: Define Service Attributes for Managed IP Services
– IP VPNs and Internet Access
– End-to-end (subscriber) and inter-provider (operator) service attributes
• Analogous to EVC/UNI and OVC/UNI/ENNI attributes for CE
• Why do this?
– Enable on-demand, dynamic Third Network IP services
• Requires standardized APIs and orchestration across network domains
– Enable on-demand, dynamic IP service creation and service assurance
Lifecycle Service Orchestration (LSO)
31
Service Lifecycle Process Model (MEF 50)
Product Lifecycle Service Operations Lifecycle
Market Analysis & Product Strategy
Product Design
Service & Resource Design
Product Launch
Marketing Fulfillment Response
Sales Proposal & Feasibility
Customer Order
Service Configuration &
Activation
Fault Management
Quality Management
Revenue Management
Service Termination
Serviceability
Fulfillment
Operation
MEF 50 leverages the TM Forum’s Business Process Framework, also referred to as the enhanced Telecom Operations Map (eTOM).
32
Service Lifecycle Process Model (MEF 50)
Product Catalogue*
Service Ordering*
Service Activation*
Performance Reporting (MEF 52)
LSO and Lifecycle Frameworks
LSO CapabilitiesFulfillment | Performance | Control | Assurance
Usage | Analytics | Security | Policy
* Future MEF Framework Specification
Service Qualification Questionnaire (MEF 53)
33
MEF 53 Overview
• MEF 53 defines the use cases, process, and content for a standardized MEF Carrier Ethernet Services Qualification Questionnaire.
• The purpose of this questionnaire is to encourage service providers buying and/or selling Ethernet services to use MEF-standardized questions to reduce the time and effort required to obtain interconnect information from access or service provider partners.
35
LSO Reference Architecture and Capabilities (MEF 55)
Network Operator 2Network Operator 1
UserService
Endpoint
UserService
Endpoint
OperatorService Endpoint
End-to-End Network-as-a-Service
Cloud ServiceProvider
SDN Switch
Packet PNFs
UNIUNI ENNI
Packet PNFs
Traditional EMS
SDN Controller
NFV MANO
Packet SDN Controller
EMS: Element Management System PNF: Physical Network Function SOF: Service Orchestration Function
Head Office
FRAMEWORKFRAMEWORK
Self-serviceWeb Portal
LSO Interlude
LSO Presto
LSO SonataLSO Cantata
LSO Allegro LSO Legato
Business Applications
SOF SOF
LSO Legato
LSO Presto
Business Applications
LSO AdagioLSO Adagio
• Fulfillment• Performance• Control• Assurance
• Usage• Analytics• Security• Policy
MEF 55 LSO Reference Architecture
Network Infrastructure
CustomerApplication Coordinator
Element Control and Management
Infrastructure Control and Management
Service Orchestration Functionality
Service Orchestration Functionality
PRESTO(SOF:ICM)
LEGATO(BUS:SOF)
Element Control and Management
Infrastructure Control and Management
ADAGIO (ICM:ECM)
LEGATO(BUS:SOF)
PRESTO(SOF:ICM)
ADAGIO (ICM:ECM)
Business Applications
Business Applications
SONATA(BUS:BUS)
INTERLUDE (SOF:SOF)
CANTATA(CUS:BUS)
ALLEGRO(CUS:SOF)
KeyCUS: Customer Application CoordinatorBUS: Business ApplicationsSOF: Service Orchestration FunctionalityICM: Infrastructure Control and ManagementECM: Element Control and Management
From Technical Specifications to MEF Products
38
LSO Engineering Methodology
MEF Service Definitions(including virtualization)
Common Information Models
LSO ReferenceArchitecture & Framework
Business Process Flows
Interface ProfilesAPI Specifications& Data Models
ReferenceImplementations
API ImplementationsCertifications
MEF 7.3, Common Model, Resource
Model,Cloud Services
MEF 50.x
Profiles for LSO Presto, LSO Legato, etc.
JSON, SCA, YANG, etc.
LSO Hackathon,
ODL project, OPNFV
MEF LSO Reference
Architecture& UNITE
NRP API Test Suite
TOC: Product Catalog, Ordering, Performance
Reporting, Serviceability
MEF 6.2, 33, 51, 10.3, 26.2, etc.
39
LSO and Open API Initiatives
• To start the respective agile sprints to develop two sets of APIs to be used for orchestrating MEF-defined services (like E-Line, E-Access etc) at LSO Sonata and LSO Prestorespectively that will culminate in publication of these open APIs during the course of 2017, and to ensure that they enable certification of orchestrated MEF-defined services.
LSO Sonata R1 APIs
FRAMEWORK
Business Applications
Service Orchestration
FRAMEWORK
Network Operator 2Network Operator 1
UserService
Endpoint
UserService
Endpoint
End-to-End Network-as-a-Service
Self-service Web Portal
Cloud ServiceProvider
UNIUNI ENNI
Head Office
Customer Facing
Open APIs
Inter-Provider
Open APIs
Inter-provider Open APIs
Business Applications
Service Orchestration
Technology DomainsOpen APIs
Technology DomainsOpen APIs
LSO Sonata R1
• Fulfillment• Performance• Control• Assurance
• Usage• Analytics• Security• Policy
42
MEF LSO Ecosystem Capabilities
• E2E Fulfillment Orchestration
Design of E2E services and assignment of resources
Order and Request management and tracking
Coordination of all provisioning tasks
Testing orchestration and turn-up
Service delivery orchestration
43
MEF – TM Forum LSO APIs Collaboration
The inter-provider LSO API standardization work can be utilized in the future for
orchestrated optical and IP services being defined by MEF and to advance digital ecosystem
orchestration and management work being led by TM Forum.
Develop a complete suite of inter-provider LSO APIs that use the MEF LSO Framework enabling agile, assured, and orchestrated Third Network services over more automated, virtualized, and interconnected networks globally.
Framework
Leveraging TM Forum’s Open API framework, digital business architecture, industry standard Information Framework and tools for end-to-end service management and orchestration.
Open APIFramework
44
LSO Sonata R1 API Project• LSO Sonata R1 is the first set of APIs being developed in support of MEF's
agile specifications development of Interface Profile Specifications at LSO Sonata based on TM Forum’s Open API Framework
• R1 includes two Epics and three User Stories:
– Provide inter-carrier service availability capabilities
• As a Service Providers, we need to validate the address for the specific site associated with the service delivery location.
• As a Service Providers, we need the ability to determine if service can be delivered to a specific customer site within a Partner’s domain.
– Provide inter-carrier service ordering capabilities
• As a Service Provider, we need to place an order for a new Access EPL or an Access EVPL service at customer site(s) within my Partner’s domain.
45
MEF PR LSO Sonata R1
For more information click here
LSO Presto R1 APIs
FRAMEWORK
Business Applications
Service Orchestration
Network Operator 1
UserService
Endpoint
UserService
Endpoint
End-to-End Network-as-a-Service
Self-service Web Portal
Cloud ServiceProvider
UNIUNI
Head Office
Customer Facing
Open APIs
Intra-provider Open APIs
Technology DomainsOpen APIs
• Fulfillment• Performance• Control• Assurance
• Usage• Analytics• Security• Policy
LSO Presto R1
48
LSO Presto R1 APIs Project
• LSO Presto R1 is the first set of APIs being developed in support of MEF's agile specifications development of Interface Profile Specifications at LSO Presto.
• R1 includes one Epics and three User Stories:
– Provisioning a connectivity service for an EPL between two customer locations
• Use ICM to publish the topology of the network to select endpoints for the connectivity service.
• Send request to ICM to activate a pre-existing connectivity service.
• Send request to ICM to create a connectivity service.
ICM: Infrastructure Control and Management
49
MEF Development Model
Liaisons to SDOs
Open Source Projects
Collaboration
MEF Agile Development LifecycleMEF Committees
Accelerator
MEF ReferenceImplementations
PlatformMEF Dev.
Community
Marketing
ServicesOperations
Orchestration
Technical and Operations
ServicesTechnologiesProfessionals
Certification
50
MEF’s Inter-operator APIs and Open InitiativesInter-Operator
Open APIsService Orchestration
Service Orchestration
Service Orchestration
Inter-OperatorOpen APIs
ServiceabilityOrdering
Address Validation… Others
Technology Domain Technology Domain Technology Domain
Services
Orchestrated Services
E-Line E-LAN E-Tree E-AccessSECaaS
E-Transit
Internet Access L3 VPNs IP TransitWavelength
AppServices
AT&T Announcement
MEF & TM Forum Announcement
51
• Nature of OpenLSO:– A MEF-facilitated open service orchestration ecosystem– Collaboration environment for MEF member companies to maximize
the alignment of market implementations of LSO– Both Open Source and proprietary components using MEF-defined LSO
specifications to foster best-of-breed solutions
• Objectives– Simplify and accelerate adoption of LSO specs for orchestration of
Third Network services– Iterative work towards APIs that are standardized and open– Maximize alignment of LSO specifications and Open Source code for
consistency with LSO use cases and capabilities– Low-risk experience, rapid feedback, agile development
52
OpenLSO Capabilities – Analytics and Assurance Projects
• Reference implementation of LSO Analytics using the PNDA.io analytics platform
• To demonstrate analytics as part of Third Network services user stories
• Feed requirements into specifications work in MEF
• Supports other LSO capabilities such as LSO Assurance and LSO Performance
• Aims to demonstrate examples of these inter-relationships via the LSO sub-architecture
Customer Application Coordinator
PartnerSOF
53
Network Level Orchestration Open APIs
MEF’s Intra-operator APIs and Open Initiatives
Fulfillment Performance Policy
Control Assurance Usage
Security
Analytics
Service Orchestration
Technology Domains
Service Level Orchestration Open APIs
Open APIs
NFVData Center Packet WAN Optical TransportSD-WAN Cloud Exchange 5G Wireless
Services
Orchestrated Services
E-Line E-LAN E-Tree E-AccessSECaaS
E-Transit
Internet Access L3 VPNs IP TransitWavelength
AppServices
54
• Nature of OpenCS
– OpenCS is a MEF-facilitated ecosystem that provides reference implementations of MEF-defined connectivity services (e.g. E-Line)
– Uses combinations of open source and proprietary components and CE 2.0-certified network devices
• Objective
– Simplify and accelerate adoption of MEF specs to develop Third Network services based on any infrastructure
• Any combination of SDN controllers, NFV infrastructure, VNFs, white boxes and traditional PNFs
55
OpenCS – SD-WAN Use Case
• The OpenCS SD-WAN project is creating for service providers reference SD-WAN implementations that can be service orchestrated by LSO (MEF-defined Lifecycle Service Orchestration) and integrated into multi-operator agile, assured and orchestrated end to end L2 and L3 services.
Load Bal.
Central Office, Data Center or Head End
CPE
Presto APIs
SD-WANController
GW
UNI
SDNSwitch
CE 2.0 / MPLS
Self-serviceWeb Portal
SDNController SDN
SwitchNFV
MANO
UNI
SD-WAN
SD-WAN
Internet
RO - Resource OrchestratorGW - GatewayCPE - Customer Premise Equipment
Presto APIsPresto APIs
• LSO Hackathons:
– Accelerate the development of comprehensive OpenLSO and OpenCS instances as part of the MEF's Open Initiatives
– Provide feedback to ongoing MEF projects in support of the MEF's Agile Standards Development approach to MEF specification development
– Facilitate discussion, collaboration, and the development of ideas, sample code, and solutions
– Encourage interdepartmental collaboration and communications within MEF member companies
– Held several times a year
– Offer both learning & commercial value
57
What is MEFnet?
• A physical and virtual hosting environment for the hardware and software components of OpenLSO and OpenCS implementations
• Includes OpenLSO and OpenCS instances comprised of solutions from Open Source Projects and Closed Source industry products
• Supports distributed and interconnected member and partner labs, accessible for LSO Hackathons and ongoing MEF development and testing work
• Ample resources, 100+ VMs
58
MEFnet Projects - Inter-carrier Orchestrated L3VPN
59
MEF Software Development Community
• Internships for telecom university grad programs and their students
• Council of university professors to advise on program
• Special designation for interns in MEF branding for access to jobs
• Additional information to be available at official launch
60
MEF UNITE Program• To coordinate internal & external engagement with
Standards Development Organizations, Industry Consortia, & Open Source Projects
• To avoid duplication of effort
• To bring technology silos into a coherent whole
61
Industry White Paper of Third Network Services
61
Third Network Services
http://mef.net/tgn
62
Service OnBoarding & design
Policies for Operations
Service Distribution (Model)
Customer Service order
Service instantiation
Operations & real-time monitoring
DESIG
ND
ISTR
IBU
TEO
RC
HESTR
ATE
OP
ER
ATE
1
2
3
4
5
6
PORTAL
DESIGN ORCHESTRATE OPERATE
Service Design
and Create (SDC)
Policy designer
Master Service
Orchestrator
(MSO)
Software Defined Network
Controller (SDN-C)
Application Controller (APP-C)
Active & Available
Inventory (A&AI)
ANALYTICS
Policy Engine
Data Collection
Analytics and
Events (DCAE)
ONAP
PHYSICAL NETWORK / PRIVATE CLOUD
PRESTO / ADAGIO
INTE
RLU
DE
CANTATA
ORDER ORCHESTRATION
ALLEGROLEGATO
SO
NA
TA
MEF and ONAP Collaboration
64
In Summary
• MEF is not just Carrier Ethernet anymore.
– Defining and documenting all services to be automated
• Lifecycle Service Orchestration
– The key to Agile, Assured and Orchestrated Services
• From Technical Specifications to code
Sponsored by:
Bruno GiguèreDirector, Product Marketing, MEF
Path from CE 2.0 to Third Network Services Roadmap
60 min