Path from CE 2.0 to Third Network Services Roadmap

Transcription

1 Sponsored by: Path from CE 2.0 to Third Network Services Roadmap Bruno Giguère Director, Product Marketing, MEF

2 Agenda 1 MEF s Carrier Ethernet and other Third Network Services 2 Lifecycle Service Orchestration (LSO) 3 From Technical Specifications to MEF Products 2

3 MEF Advancing the Industry 3

4 Third Network Services Third Network Services Orchestrated Services E-Line E-LAN E-Tree E-Access E-Transit Wavelength Internet Access L3 VPNs IP Transit SECaaS App Services 4

5 How the MEF Defines Connectivity Services Subscriber Services consist of: User to Network Interfaces (s) Demarcation between Service Provider and Subscriber Virtual Connections (VC) at or between s, VC, and VC End Point Service Attributes Operator Services consist of: (s) External Network to Network Interfaces (ENNIs) Demarcation between Operators VCs at or between the (s) or ENNI(s), ENNI, VC, and VC End Point Service Attributes EVC: Ethernet Virtual Connection OVC: Operator Virtual Connection VC Service Provider VC Service Provider For Ethernet Services, VCs are EVCs or OVCs ENNI VC Operator 5

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 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 6

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 OWS over OTN 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 Layer 1 transport EPL SONET/SDH Internet Access EVPL IEEE MEF standardizes the service model for each of the three network layers to facilitate automation and orchestration 7

8 Goal to Standardize and Unify Service Components to Simplify Modeling and APIs 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., or ENNI 8

9 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 10

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 CE 2.0 Class of Service Extensions Retail Provider s CE Network EVC 1 CoS 4 ENNI EVC 2 Wholesale Access Network CoS 6 CoS 2 CE Exchange 68Mbps for Internet Access Cloud ENNI 2 Mbps CIR for control 10 Mbps CIR for VoIP 20Mbps CIR for VPN data traffic 11

12 CE 2.0 Retail Services Types E-Line Ethernet Private Lines (EPL) Ethernet Virtual Private Lines (EVPL) Ethernet Internet Access Point-to-Point EVC E-LAN Multipoint L2 VPNs Transparent LAN Service Multicast Networks EP-LAN, EVP-LAN Multi-point to Multi-point EVC E-Tree Rooted Multi-Point L2 VPNs Traffic Segregation EP-Tree, EVP-Tree Rooted Multi-point EVC 12

13 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 Retail Service Provider The Buyer (Has relationship with end-customer) ON-NET CUSTOMER LOCATIONS Wholesale Access Service Provider The Seller (Provides Access to remote customer location) OFF-NET CUSTOMER LOCATIONS End User Subscriber Headquarters Carrier Ethernet Network ENNI Carrier Ethernet Network End User Subscriber Branch Site CE CE E-Access Service End-to-End Carrier Ethernet Service 14

15 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 ENNI CEN ENNI CEN CE End User Subscriber Headquarters Carrier Ethernet Network (CEN) E-Transit Service (E-Line) E-Access Service CE End User Subscriber Branch Site End-to-End Carrier Ethernet Service 16

16 MEF Layer 1 Services Project

17 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/ and OVC//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 19

18 MEF IP Project

19 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/ and OVC//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 23

20 Lifecycle Service Orchestration (LSO)

21 Service Lifecycle Process Model (MEF 50) Product Lifecycle Market Analysis & Product Strategy Service Operations Lifecycle Marketing Fulfillment Response Product Design Sales Proposal & Feasibility Serviceability Service & Resource Design Customer Order Product Launch Service Configuration & Activation Fulfillment MEF 50 leverages the TM Forum s Business Process Framework, also referred to as the enhanced Telecom Operations Map (etom). Fault Management Quality Management Service Termination Revenue Management Operation 31

22 LSO and Lifecycle Frameworks LSO Capabilities Fulfillment Performance Control Assurance Usage Analytics Security Policy Product Catalogue* Service Activation* Service Ordering* Performance Reporting (MEF 52) Service Qualification Questionnaire (MEF 53) Service Lifecycle Process Model (MEF 50) * Future MEF Framework Specification 32

23 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. 33

24 LSO Reference Architecture and Capabilities (MEF 55) FRAMEWORK FRAMEWORK Self-service Web Portal LSO Cantata LSO Allegro Business Applications LSO Legato SOF LSO Presto LSO Sonata LSO Interlude Business Applications LSO Legato SOF LSO Presto Fulfillment Performance Control Assurance Usage Analytics Security Policy User Service Endpoint NFV MANO LSO Adagio SDN Controller Operator Service Endpoint Packet SDN Controller Packet PNFs LSO Adagio Traditional EMS Packet PNFs User Service Endpoint Head Office SDN Switch Network Operator 1 ENNI Network Operator 2 Cloud Service Provider End-to-End Network-as-a-Service EMS: Element Management System PNF: Physical Network Function SOF: Service Orchestration Function 35

25 MEF 55 LSO Reference Architecture CANTATA (CUS:BUS) Business Applications SONATA (BUS:BUS) Business Applications Customer Application Coordinator LEGATO (BUS:SOF) LEGATO (BUS:SOF) ALLEGRO (CUS:SOF) Service Orchestration Functionality INTERLUDE (SOF:SOF) Service Orchestration Functionality PRESTO (SOF:ICM) PRESTO (SOF:ICM) Infrastructure Control and Management Infrastructure Control and Management ADAGIO (ICM:ECM) ADAGIO (ICM:ECM) Element Control and Management Element Control and Management Key CUS: Customer Application Coordinator BUS: Business Applications SOF: Service Orchestration Functionality ICM: Infrastructure Control and Management ECM: Element Control and Management Network Infrastructure

26 From Technical Specifications to MEF Products

27 LSO Engineering Methodology TOC: Product Catalog, Ordering, Performance Reporting, Serviceability API Implementations Certifications LSO Reference Architecture & Framework MEF LSO Reference Architecture & TE Common Information Models MEF 7.3, Common Model, Resource Model, Cloud Services NRP API Test Suite MEF Service Definitions (including virtualization) MEF 6.2, 33, 51, 10.3, 26.2, etc. LSO Hackathon, ODL project, OPNFV Reference Implementations Business Process Flows MEF 50.x JSON, SCA, YANG, etc. API Specifications & Data Models Interface Profiles Profiles for LSO Presto, LSO Legato, etc. 38

28 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 Presto respectively 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. 39

29 LSO Sonata R1 APIs

30 Inter-provider Open APIs LSO Sonata R1 FRAMEWORK FRAMEWORK Self-service Web Portal Customer Facing Open APIs Business Applications Service Orchestration Inter-Provider Open APIs Business Applications Service Orchestration Fulfillment Performance Control Assurance Usage Analytics Security Policy User Service Endpoint Technology Domains Open APIs Technology Domains Open APIs User Service Endpoint Network Operator 1 ENNI Network Operator 2 Cloud Service Provider Head Office End-to-End Network-as-a-Service

31 MEF LSO Ecosystem Capabilities E2E Fulfillment Orchestration Service delivery orchestration Testing orchestration and turn-up Coordination of all provisioning tasks Order and Request management and tracking Design of E2E services and assignment of resources 42

32 MEF TM Forum LSO APIs Collaboration Framework Open API Framework 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. Leveraging TM Forum s Open API framework, digital business architecture, industry standard Information Framework and tools for end-to-end service management and orchestration. 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 43

33 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. 44

34 MEF PR LSO Sonata R1 For more information click here 45

35 LSO Presto R1 APIs

36 Intra-provider Open APIs LSO Presto R1 FRAMEWORK Self-service Web Portal Customer Facing Open APIs Business Applications Service Orchestration Fulfillment Performance Control Assurance Usage Analytics Security Policy Technology Domains Open APIs User Service Endpoint User Service Endpoint Network Operator 1 Head Office Cloud Service Provider End-to-End Network-as-a-Service

37 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 48

38 MEF Development Model MEF Committees MEF Agile Development Lifecycle MEF Reference Implementations Technical and Operations Marketing Liaisons to SDOs Accelerator Services Operations Orchestration Certification Services Technologies Professionals Open Source Projects Collaboration MEF Dev. Community Platform 49

39 MEF s Inter-operator APIs and Open Initiatives Service Orchestration Inter-Operator Open APIs Serviceability Ordering Address Validation Others Service Orchestration Inter-Operator Open APIs Service Orchestration Technology Domain Technology Domain Technology Domain Orchestrated Services Services E-Line E-LAN E-Tree E-Access E-Transit Wavelength Internet Access L3 VPNs IP Transit SECaaS App Services AT&T Announcement MEF & TM Forum Announcement 50

40 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 51

41 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 interrelationships via the LSO sub-architecture Customer Application Coordinator Partner SOF 52

42 MEF s Intra-operator APIs and Open Initiatives Service Level Orchestration Open APIs Service Orchestration Fulfillment Performance Policy Control Assurance Usage Security Analytics Network Level Orchestration Open APIs Technology Domains Open APIs SD-WAN Data Center Packet WAN Optical Transport NFV Cloud Exchange 5G Wireless Orchestrated Services Services E-Line E-LAN E-Tree E-Access E-Transit Wavelength Internet Access L3 VPNs IP Transit SECaaS App Services 53

43 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 54

44 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 Load Bal. Service Orchestration) and integrated into multi-operator agile, assured and orchestrated end to end L2 and L3 services. Self-service Web Portal CPE Internet Presto APIs SD-WAN Controller NFV MANO Presto APIs Presto APIs SDN Controller SDN Switch SD-WAN RO - Resource Orchestrator GW - Gateway CPE - Customer Premise Equipment CE 2.0 / MPLS GW SD-WAN Central Office, Data Center or Head End SDN Switch 55

45 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

46 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 57

47 MEFnet Projects - Inter-carrier Orchestrated L3VPN 58

48 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 59

49 MEF TE 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 60

50 61 Industry White Paper of Third Network Services Third Network Services 61

51 OPERATE ORCHESTRATE INTERLUDE DISTRIBUTE DESIGN SONATA MEF and ONAP Collaboration 1 Service OnBoarding & design CANTATA PORTAL 2 Policies for Operations ORDER ORCHESTRATION LEGATO ONAP ALLEGRO 3 Service Distribution (Model) DESIGN ORCHESTRATE OPERATE 4 Customer Service order Service Design and Create (SDC) Master Service Orchestrator (MSO) Active & Available Inventory (A&AI) ANALYTICS 5 Service instantiation Policy designer Software Defined Network Controller (SDN-C) Application Controller (APP-C) Policy Engine Data Collection Analytics and Events (DCAE) 6 Operations & real-time monitoring PRESTO / ADAGIO PHYSICAL NETWORK / PRIVATE CLOUD 62

52 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 64

53 Sponsored by: Path from CE 2.0 to Third Network Services Roadmap Bruno Giguère Director, Product Marketing, MEF