More Related Content


Similar to T-NOVA: Developing a platform for NFaaS(20)

Recently uploaded(20)


T-NOVA: Developing a platform for NFaaS

  1. T-­‐NOVA Consor-um Presenter: Eleni Trouva -­‐ NCSR Demokritos, Greece
  2. • ICT Call 11 (FP7-­‐ICT-­‐2013-­‐11) • Objec6ve ICT-­‐2013.1.1.: Future Networks • Project Coordinator: Dr. Anastasios Kour6s (NCSRD) • Dura6on: 36 Months • Star6ng Date: 1.1.2014 • Budget: 10,027,115 • EU contribu6on : 6,743,000 • Total PM : 1,035.5 • Consor6um comprises of 18 partners 2
  3. 3
  4. • Consolida6on of hardware resources, leading to reduced equipment investment and maintenance costs (reduc6on of both CAPEX and OPEX) and power consump6on • Sharing of resources among different network func6ons and users • Up/Down and In/Out -­‐scaling of resources assigned to each func6on • Increased automa=on and real-­‐=me monitoring through the use of standard IT technologies • Rapid introduc=on of novel network func=ons (including upgrading of exis6ng ones) at much lower cost and lower risk, leading to significant decrease of Time-­‐To-­‐Market (TTM) for new solu6ons. New experimental services can co-­‐exist in the same infrastructure with “produc6on” ones. • Promo6on of innova6on, by opening a part of the networking market and transforming it to a novel virtual appliance market, facilita6ng the involvement of so_ware entrants, including SMEs and even academia 4
  5. • The simultaneous, joint management of network and IT resources for instan6a6ng the Virtual Network Func6ons (VNFs) – an implementa6on of a Network Func6on that can be deployed over a Network Func6on Virtualiza6on Infrastructure (NFVI) -­‐ and steering the desired por6on of the traffic through them • The availability and fault resilience of VNFs • The performance of VNFs, compared to the corresponding hardware-­‐ based versions • The compa=bility of virtual NFs with exis6ng network management pladorms 5
  6. • Presents an integrated solu=on for the offering, deployment and management of Virtualized Network Func6ons over composite (Network/IT) infrastructures. • Implements Network Func=on as-­‐a-­‐Service (NFaaS) concept: offering of Network Func6ons to operators’ customers, as value-­‐added services. (ETSI NFV ISG Use Case #2) – Implements an Integrated Management architecture, including an Orchestrator Pladorm – Leverages Cloud compu6ng management – Exploits and extends SDN aspects, focusing on the OpenFlow standard, for efficient management of network resources 6
  7. • The NFaaS service offered by T-­‐NOVA comprises: – A connec6vity Service: transport network links interconnec6ng NFVI-­‐PoPs also including the per-­‐case establishment of vNETs – A set of associated Network Func6ons, ranging from flow handling and control mechanisms to in-­‐network packet payload processing, according to customer needs 7
  8. • Implements all the func6onali6es of a complete NFVI-­‐PoP, as envisaged by ETSI • Introduces an innova=ve “Network Func=on Store”, following the paradigm of already successful OS-­‐ specific “App Stores” • Establishes a Novel Brokerage Pla+orm, allowing customers to transact with the T-­‐NOVA Service Provider and mul6ple third-­‐party Func6on Developers • Ιntroduces 8 and promotes a novel Marketplace for VNF’s, introducing new business cases and considerably expanding market opportuni6es by alrac6ng new entrants to the networking market
  9. 9
  10. Realiza6on of a NFV marketplace to: • allow network services and func6ons by a variety of developers to be published and brokered/traded • Allow customers to browse the marketplace and select the services and virtual appliances that best match their needs, as well nego6a6ng the associated SLAs and billing models Key feature of the MarketPlace is the ability to nego6ate and acquire SLAs Main Marketplace Func6ons : • Publica-on of resources and NF adver-sement • VNF discovery, resource trading and service matching • Customer-­‐side monitoring and configura-on of the offered services and func-ons 10
  11. • Service 11 Provider (SP) provides the service to the customer making alliances with FPs and with the B, sharing revenue with both. • Customer (C) purchases and pays for a service provided by the SP. The customer might be involved in bargaining or auc6oning processes in order to nego6ate a final provider and terms (price and SLA) for the service purchased. The Customer agrees on a SLA with the SP. • Func=on Provider (FP) is interested in providing as many func6ons as possible or in having their func6ons used or purchased as much as possible. The FP commercialises NFs through the Broker to the T-­‐NOVA SP. The rela6onship with the SP and B is a revenue sharing scenario, since the SP has to grant a share to the FP for the NF included in a service. • Broker (B) The broker business model as third party might be to be granted a commission per finalised trade and, thus, shares revenue with SPs or FPs. A broker might priori6se offerings depending on the business terms nego6ated with the SP or FP. • End User (EU) will be in business scenarios such as a SP being a reseller. In this case, the EU would pay for services provided by the SP. In other contexts, this actor will not be present. • Service Integrator (SI) The SI’s customer is the SP. Among different SI, the SP might choose the most trusted one, or the SP offering the best condi6ons (price, etc.) for the same service. • Cloud Infrastructure Provider (CIP) has a commercial rela6onship with the SI (in case it exists) or, otherwise, with the SP (in the case where they are not played by the same business en6ty, e.g. a Cloud Service Provider (CSP)). • Network Infrastructure Provider (NIP) has a commercial rela6onship with the SI (in case it exists) or, otherwise, with the SP (in case they are not played by the same business en6ty, e.g. a CSP).
  12. 12
  13. 13
  14. 14 Ques6ons ? www.t-­‐ @fp7tnova