idnits 2.17.1 draft-flinck-slicing-management-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The abstract seems to contain references ([NS-Framework]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (July 3, 2017) is 2488 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Outdated reference: A later version (-15) exists of draft-ietf-teas-actn-framework-06 == Outdated reference: A later version (-02) exists of draft-geng-netslices-architecture-01 Summary: 1 error (**), 0 flaws (~~), 3 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Engineering Task Force H. Flinck 3 Internet-Draft C. Sartori 4 Intended status: Informational A. Andrianov 5 Expires: January 4, 2018 C. Mannweiler 6 N. Sprecher 7 Nokia 8 July 3, 2017 10 Network Slicing Management and Orchestration 11 draft-flinck-slicing-management-00 13 Abstract 15 Network Slicing is worked in multiple SDOs from different view 16 points. As network slicing is an end-to-end topic, this draft 17 proposes that network slices architecture [NS-Framework] aligns with 18 the work done in NGMN, 3GPP and ETSI with relation to management and 19 orchestration. The key aspect that this draft makes is the rational 20 for role and need for Network Slice Management Function (NSMF) entity 21 that operates above Network Virtualization Function Orchestrator and 22 PNFs Management Functions. NSMF needs to support different 23 abstractions of resources and to offer access to different management 24 entities. 26 Status of This Memo 28 This Internet-Draft is submitted in full conformance with the 29 provisions of BCP 78 and BCP 79. 31 Internet-Drafts are working documents of the Internet Engineering 32 Task Force (IETF). Note that other groups may also distribute 33 working documents as Internet-Drafts. The list of current Internet- 34 Drafts is at http://datatracker.ietf.org/drafts/current/. 36 Internet-Drafts are draft documents valid for a maximum of six months 37 and may be updated, replaced, or obsoleted by other documents at any 38 time. It is inappropriate to use Internet-Drafts as reference 39 material or to cite them other than as "work in progress." 41 This Internet-Draft will expire on January 4, 2018. 43 Copyright Notice 45 Copyright (c) 2017 IETF Trust and the persons identified as the 46 document authors. All rights reserved. 48 This document is subject to BCP 78 and the IETF Trust's Legal 49 Provisions Relating to IETF Documents 50 (http://trustee.ietf.org/license-info) in effect on the date of 51 publication of this document. Please review these documents 52 carefully, as they describe your rights and restrictions with respect 53 to this document. Code Components extracted from this document must 54 include Simplified BSD License text as described in Section 4.e of 55 the Trust Legal Provisions and are provided without warranty as 56 described in the Simplified BSD License. 58 Table of Contents 60 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 61 1.1. Acronyms and Abbreviations . . . . . . . . . . . . . . . 5 62 2. Different levels of Network Slice Control exposure . . . . . 5 63 3. Network Slice Management Function (NSMF) . . . . . . . . . . 6 64 4. IANA considerations . . . . . . . . . . . . . . . . . . . . . 8 65 5. Security considerations . . . . . . . . . . . . . . . . . . . 8 66 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 8 67 7. Informative References . . . . . . . . . . . . . . . . . . . 8 68 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 9 70 1. Introduction 72 The purpose of this draft is to highlight the essential aspects of 73 network slice management from 3GPP, NGMN and ETSI relevant for the 74 network slices architecture as described in [NS-Framework] and to 75 propose a minimal alignment between these works to ensure 76 compatibility between them. NGMN documents 77 "161010_NGMN_Network_Slicing_framework_v1.0.8" [NGMN_NS] and "5G 78 Network and Service Management including Orchestration" [NGMN_NSMN] 79 define Network Slicing and how it relates to overall Service and 80 Network Management architecture. The NGMN documents define as well 81 the terminology adopted later by 3GPP and reflected in 3GPP 82 [TR28.801]. In this paper, for sake of simplicity, only an 83 "executive summary" of network slicing is given, while relying on 84 both terminology and complete descriptions on the above mentioned 85 documents. 87 Network Slicing provides multiple logical networks on top of a 88 partially shared network infrastructure as described in 89 [NS-Framework]. Each instance of a network slice represents an 90 independent end-to-end network that allows deployment of different 91 architectural flavors in parallel slices. These slices may be 92 deployed and/or operated by the slice provider, or by the tenant who 93 requested the slice. 95 A network slice can span across different administrative domains. 96 NGMN Network slicing white paper [NS-Framework] defines various 97 forward-looking business models engaging multiple administrative 98 domains that may be envisioned in the industry. An administrative 99 domain refers to the scope of jurisdiction of a provider. A provider 100 may obtain services from 3rd parties (i.e. sub-providers) to enrich 101 the services it provides to its end customers. A provider could also 102 benefit from offering its spare capabilities or resources to other 103 providers becoming itself a sub-provider. A network service can be a 104 single user connectivity service, NaaS (Network as a Service) such as 105 a service instance, a network slice instance or a subnetwork slice 106 (note NGMN and 3GPP use a different terminology for what IETF 107 netslices drafts call for "network slice segment") instance offering 108 for a business vertical that utilizes forward-looking business 109 models, or IaaS (Infra structure as a Service). 111 Depending on the use cases and type of services for which the end-to- 112 end slice has been instantiated multiple levels of control may be 113 exposed to the tenants by the slice provider. On the lowest level of 114 the exposed control the network slice provider grants only access to 115 use the slice and means to monitor its performance. At second level 116 a control exposure is to allow tenants to change the configuration of 117 the network functions associated to the tenant's network slice. At 118 the highest level of control tenants can compose network slices and 119 manage them with their own management system. These different levels 120 of control exposure require that the network slice management must 121 work on multiple levels of abstractions where highest level is at the 122 Service Management & Orchestration (M&O) and lowest level at the 123 network functions. The slice provider must be able to isolate these 124 control functions of different tenants to match the "Slice Provider" 125 - "Slice Consumer" -relationship. 127 A network slice instance can contain virtualized network functions as 128 well as physical network functions. Virtualized network functions 129 (VNF) are decoupled from physical network equipment by a 130 virtualization layer. Both the lifecycle of the types of the network 131 functions can span beyond the lifecycle of a Network Slice and they 132 need their own life cycle management functions. The life cycle 133 management of these two types of network functions differ. The 134 environment in which VNFs are deployed is called Network Functions 135 Virtualisation Infrastructure (NFVI) and is managed by Virtualised 136 Infrastructure Manager (VIM) according to ETSI NFV-MANO [MANO] 137 reference architecture. VNFs are instantiated by requests of NFV 138 Orchestrator (NFVO). In the MANO architecture NFV Orchestrator 139 (NFVO) uses VNF Managers for the lifecycle management of VNF 140 instances and the VIM allocates the needed virtualized resources as 141 requested by the NFVO into the NFVI. However, the same approach 142 cannot be applied to network functions of dedicated hardware 143 (Physical Network Functions, PNF) as their resources are not 144 controlled by NFVO nor VIMs. Network Functions (whether PNF or VNF) 145 require their function specific management, as well as their resource 146 management. 148 When adding support for the virtualized version of the PNFs their 149 management systems will evolve to either extend their capability with 150 an embedded VNF management functionality or will delegate their 151 virtual resource management to an external VNF manager. In either 152 case, the VNF management function interacts with the NFVO and the VIM 153 through the MANO defined interfaces and provides the cloud resource 154 FCAPS management for the network functions. Another key issue for 155 provisioning of network slices is the identification, design, and 156 management of network functions which can be shared by multiple end- 157 to-end slices [Rost]. 159 For Network slice management function (NSMF), which is a slice- 160 dedicated function with slice-specific view on any FCAPS data and 161 management procedures, such sharing or common usage should be 162 transparent, i.e., the multiplexing of multiple network slices to a 163 commonly used function/element is done by EMS/NMS. NSMF operates 164 above NFVO and PNFs Management Functions in the Service M&O. In view 165 of 3GPP as well as ETSI NFV, NSMF belongs to OSS/BSS. When a network 166 slice contains PNFs the NSMF instructs the PNFs Management Functions 167 to configure the physical network components to deliver the required 168 slice characteristics. 170 This draft introduces the role of NSMF in the context of 3GPP 171 [TR28.801], [TS28.530] and ETSI [MANO] work and reflects that back to 172 netslices-architecture presented in [NS-Framework]. We argue that 173 the NSMF is at the Service M&O level, even at a tenant. This is 174 because of several reasons: 176 o Need for exposing different levels of network slice control to the 177 tenants. 179 o Different life cycle management approaches for PNFs and VNFs. 180 NSMF must have interfaces both to NFVO and to PNFs Management and 181 is therefore above of the NFVO and PNF management and it should 182 support service level abstractions. 184 Network slicing is end-to-end concept, thus including several network 185 components, (Network Slice Subnetwork Functions according to 3GPP 186 terminology). Often those components belong to different 187 administrative domains (e.g. RAN, Core Network, Transport) and 188 therefore the need for a higher level of abstraction. Transport 189 network [ACTN] is a subnetwork slice in the 3GPP model and recursion 190 can be applied to slices as well as to subnetwork slices. 192 1.1. Acronyms and Abbreviations 194 This document uses the following acronyms: 196 3GPP 3rd Generation Partnership Project 197 BSS/OSS Business Support Systems/Operations Support Systems 198 EMS Element Management System 199 ETSI European Telecommunications Standards Institute 200 FCAPS Fault, Configuration, Accounting, Performance, Security 201 IaaS Infra structure as a Service 202 KPI Key Performance Indicator 203 MANO ETSI Management and Orchestration 204 LCM Life Cycle Management 205 MNO Mobile Network Operator 206 M&O Management & Orchestration 207 NaaS Network as a Service 208 NGMN Next Generation Mobile Networks 209 NMS Network Management System 210 NSMF Network Slice Subnet Management Functions 211 NSSMF Network Slice Management Function 212 NFVI Network Functions Virtualisation Infrastructure 213 NVFO Network Virtualization Function Orchestrator 214 PNF Physical Network Function 215 RAN Radio Access Network 216 SLA Service Level Agreement 217 VIM Virtualised Infrastructure Manager 218 VNF Virtualised Network Function 220 2. Different levels of Network Slice Control exposure 222 Depending on the "Slice Provider" - "Slice Consumer" -relationship 223 the Slice Provider can offer various levels of control to the Slice 224 Consumers. Roughly speaking levels of control can be categorized 225 onto follow cases: 227 1. Monitoring only. The Slice Provider offers only means to monitor 228 the slice KPIs as agreed in the contract. Network slice 229 configuration is chosen from a catalogue of readymade slice 230 templates. Accesses via dashboard-like web service and/or north 231 bound interfaces provided by the Slice Provider. 233 2. Limited control to Slice Consumer to perform design and 234 composition of network slice. Slice Consumer can change 235 configuration of deployed network functions and /or onboard own 236 certified network functions into Slice Provider's repository 237 using interfaces provided by the Slice Provider. 239 3. Extended Control. In this case the Slice Consumer deploys and 240 operates the network slice using its own MANO stack and NMS. The 241 Slice consumer has tight control over its own network functions 242 and services while has limited control over MNO network 243 functions. 245 Because of these varying levels of network slice control, the NSMF 246 needs to support different abstractions of resources and to offer 247 access to different management entities (e.g. PNFs management 248 functions, NFV-MANO). Consequently, the logical place for NSMF 249 function in the network slice management architecture is at the 250 Service Management & Orchestration (M&O). 252 3. Network Slice Management Function (NSMF) 254 Network slicing concept of NGMN consists of 3 layers: Service 255 Instance Layer, Network Slice Instance Layer, and Resource layer 256 [NGMN_NS]. The Service Instance Layer is managed by service 257 orchestrator that is considered to be part of BSS/OSS according to 258 the 3GPP view [TR28.801]. Network Slicing Instance Layer is a 259 Business to Business service and may pass across multiple 260 administrative domains. Network Slice Management Function resides at 261 this layer and is consequently part of Service Orchestration and BSS/ 262 OSS. 264 The end-to-end network slice management (NSMF) can use different 265 technology domains and their segments to create an end-to-end slice. 266 It has full visibility and control to the end-to-end slice and its 267 performance. It resides above the Network Slice Subnet Management 268 Functions (NSSMF). It monitors slice specific FCAPS to maintain and 269 to expose the overall SLAs of the end-to-end slices to the tenant. 271 NSMF interfaces domain specific Network Management and Element 272 Management Systems through Network Slice Subnet Management Functions 273 (NSSMF). In addition, NSMF also interfaces NFV-MANO to manage 274 virtualization aspects (through "OS-Ma-nfvo"-interface). 276 NSSMF manages Network Slice Subnet (3GPP defined management 277 abstraction) composed of Network Functions (virtualized or not) and 278 other Network Slice Subnets (recursion principle). NM/EM could play 279 the role of NSSMF. For management of virtualization aspects (such as 280 NS and VNF LCM) and TN, NSSMF interacts with NFV-MANO (through "Os- 281 Ma-nfvo"-interface). The 3GPP defined Network Slice Subnets 282 correspond to ETSI NFV defined NSs composed from either network 283 functions and/or nested network slices (recursion principle). 285 +------------------------------------+ 286 | BSS/OSS | 287 | +-----------------------+ | 288 | | Service M&O | | 289 | | | | 290 | | +-------------+ | | 291 | | | NSMF +--------------------------+ 292 | | ++------------+ | | | 293 | +---|-------------------+ | | 294 +------------|-----------------------+ | 295 | | 296 | | 297 +----------|-----+ | 298 | NM/EM | | | 299 | +------+-----+ +-----+------+ 300 | | | | | 301 | | | | NFV | 302 | | NSSMF +---------------------------+ MANO | 303 | | | | | 304 | | +------------+ | | 305 +---+------+-----+ | +-----+------+ 306 | | | 307 | | | 308 +-----+-----+ | +----+------+ 309 | | | | | 310 | PNFs | +---------------+ VNFs | 311 | | | | 312 +-----+-----+ +----+------+ 313 | | 314 | | 315 | | 316 +---------+---------------------------------------+-------------+ 317 | Slice with shared and dedicated network functions | 318 +---------------------------------------------------------------+ 320 Network Slice Management functional architecture. 322 Figure 1 324 Based on the above reasoning we propose to replace the "Figure 2: E2E 325 Slice Orchestration"-figure of the section of Management and 326 Orchestration of Network Slicing in [NS-Framework] with the following 327 figure with the above stated reasoning. 329 + ------------------------------------------------+ 330 | NSMF | 331 +-------------------------------------------------+ 332 | | | 333 +-----------+ +-----------+ +----------+ 334 | Network | | Network | | Network | 335 | Slice | | Slice | | Slice | 336 | Subnet | | Subnet | | Subnet | 337 | Management| | Management| |Management| 338 | Function |------| Function |------ ... -- |Function | 339 +----------+ +-----------+ +----------+ 340 | | | 341 +-------------------------------------------------------------+ 342 | P/VNF FCAPS Management / NFV-MANO: VNF LCM management | 343 +-------------------------------------------------------------+ 344 | | | | 345 +--------+ : +--------+ : +--------+ : +--------+ 346 | PNF 1 |----- | PNF n |----- | VNF 1 |----...-- | VNF n | 347 +--------+ : +--------+ : +--------+ : +--------+ 349 Network Slice Management Function (Network Slice segment term 350 corresponds roughly to Network Slice subnetwork term used by 3GPP/ 351 NGMN) 353 Figure 2 355 4. IANA considerations 357 This document makes no request of IANA. 359 5. Security considerations 361 Each element and their interface of the proposed management 362 architecture needs to address their security requirements. 364 6. Acknowledgements 366 7. Informative References 368 [ACTN] Ceccarelli, D. and Lee, Y., "Framework for Abstraction and 369 Control of Traffic Engineered Networks", draft-ietf-teas- 370 actn-framework-06 (work in progress), June 2017. 372 [MANO] ETSI, "ETSI GS NFV-MAN 001: Network Functions 373 Virtualization (NFV); Management and Orchestration", 2014. 375 [NGMN_NS] NGMN Alliance, "Description of Network Slicing Concept", 376 https://www.ngmn.org/uploads/ 377 media/161010_NGMN_Network_Slicing_framework_v1.0.8.pdf , 378 2016. 380 [NGMN_NSMN] 381 NGMN Alliance, "5G Network and Service Management 382 including Orchestration", 383 https://www.ngmn.org/publications/all-downloads/ 384 article/5g-network-and-service-management-including- 385 orchestration.html , 2017. 387 [NS-Framework] 388 Geng, L., Dong, J., Bryant, S., Makhijani, K., Galis, A., 389 De Foy, X., and Kuklinsk, S., "Network Slicing 390 Architecture", draft-geng-netslices-architecture-01 (work 391 in progress), June 2017. 393 [Rost] Rost, P., Mannweiler, C., Diomidis, M., Sartori, C., 394 Sciancalepore, V., Sastry, N., Holland, O., Tayade, S., 395 Han, B, Bega, D., Aziz, D., Bakker, H., and IEEE 396 Communications Magazine, Volume: 55 Issue: 5,, "Network 397 Slicing to Enable Scalability and Flexibility in 5G Mobile 398 Networks", May 2017. 400 [TR28.801] 401 3GPP, "Study on management and orchestration of network 402 slicing for next generation network, Release 14)3GPP TR 403 28.801 V1.2.0", 404 https://portal.3gpp.org/desktopmodules/Specifications/ 405 SpecificationDetails.aspx?specificationId=3091 , 2017. 407 [TS28.530] 408 3GPP, "Management of network slicing in mobile networks; 409 Concepts, use cases and requirements. Technical 410 specification. Release 15. 3GPP TR 28.530.", 411 https://portal.3gpp.org/desktopmodules/Specifications/ 412 SpecificationDetails.aspx?specificationId=3091 , 2017. 414 Authors' Addresses 416 Hannu Flinck 417 Nokia 418 Espoo 419 FI 421 Phone: +358504839522 422 Email: hannu.flinck@nokia.com 423 Cinzia Sartori 424 Nokia 425 Munich 426 DE 428 Phone: +491713008990 429 Email: cinzia.sartori@nokia-bell-labs.com 431 Anatoly Andriannov 432 Nokia 433 Arlington Heights, IL 434 US 436 Phone: +1-847-668-0394 437 Email: anatoly.andrianov@nokia.com 439 Christian Mannweiler 440 Nokia 441 Munich 442 DE 444 Phone: +491715581581 445 Email: christian.mannweiler@nokia-bell-labs.com 447 Nurit Sprecher 448 Nokia 449 Hod HaSharon 450 IL 452 Phone: +97297751229 453 Email: nurit.sprecher@nokia.com