IDR Working Group Internet-Draft Intended status: Informational W. Cheng Expires: February 25, 2022 W. Jiang China Mobile R. Chen ZTE Corporation L. Gong China Mobile C. F H3C Corporation Sh. Peng ZTE Corporation August 25, 2021 IETF Network Slice use cases draft-cheng-teas-network-slice-usecase-01 Abstract This draft supplements the usecase described in [I-D.ietf-teas-ietf-network-slice-definition] from the perspective of the operator.In specific,it mainly includes two types of the network slice customers from the perspective of operators: o End-to-end slicing cloud-network collaboration o The branch departments that use slices within the operator. Status of This Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at https://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." This Internet-Draft will expire on February 25, 2022. Cheng, et al. Expires February 25, 2022 [Page 1] Internet-Draft IETF Network Slice use cases August 2021 Copyright Notice Copyright (c) 2021 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 2. Requirements notation . . . . . . . . . . . . . . . . . . . . 3 3. Network Slice use cases . . . . . . . . . . . . . . . . . . . 3 3.1. cloud-network service for enterprise . . . . . . . . . . 3 3.2. The branch departments that use slices within the operator. . . . . . . . . . . . . . . . . . . . . . . . . 5 3.2.1. Network Slice resource management . . . . . . . . . . 5 3.2.2. Domain governance of network slice . . . . . . . . . 6 4. Security Considerations . . . . . . . . . . . . . . . . . . . 7 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7 6. Normative References . . . . . . . . . . . . . . . . . . . . 7 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7 1. Introduction [I-D.ietf-teas-ietf-network-slice-definition] defines the concept of IETF network slices that provide connectivity coupled with a set of specific commitments of network resources between a number of endpoints over a shared network infrastructure and describes a number of use-cases benefiting from network slicing including: o 5G network slicing o Network wholesale services o Network sharing among operators o NFV connectivity and Data Center Interconnect In the document also clearly stated services that might benefit from the network slices include but not limited to the above use-cases. Cheng, et al. Expires February 25, 2022 [Page 2] Internet-Draft IETF Network Slice use cases August 2021 This document supplements two use-cases from the perspective of operators. In specific, it mainly includes two types of the network slice customers from the perspective of operators: o End-to-end slicing cloud-network collaboration o The branch departments that use slices within the operator. 2. Requirements notation The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119]. 3. Network Slice use cases 3.1. cloud-network service for enterprise Cheng, et al. Expires February 25, 2022 [Page 3] Internet-Draft IETF Network Slice use cases August 2021 +------------------------------------------+ | Consumer higher level operation system | +----------------| (e.g E2E network slice orchestrator) |-------------+ | +------------------------------------------+ | | A A | | | | | | | | | | | | | V V V V |----------------| |-------------------| |-----------------| |-----------------| | MAN Slice | | Edge Cloud | | Backbone Slice | | DC Slice | | Controller | | Slice Controller | | Controller | | Controller | |----------------| |-------------------| |-----------------| |-----------------| | | | | | | | | V | V | ............... | .................. | : MAN : | : IP Backbone : V CPE PE PE : | PE PE .............. |----| |-----| |-----| | |-----| |-----| : DC Network : | NS1o---|o---o|.--- |o---o|-------|-------------|o---o|----------|o---o|-----o : | NS2o---|o---o|.\-- |o---o|-------|-------------|o---o|----------|o---o|-----o : |----| |-----| \\ |-----| | |-----| |-----| :............: : \\ : | : : :.......\\....: | :................: \\ V \\ ................. \ o Edge Cloud : \o : : : : : :...............: Figure 1 A cloud-network service for enterprise will involve several domains, each with its own controller. MAN, Edge Cloud, IP Backbone and DC domains need to be coordinated in order to deliver a cloud-network service for enterprise. In Figure 1, the network operator has created two E2E network slices, there are two types of traffic from the client, and each traffic is mapped to different slice, which is NS1 and NS2.Each NS with its own MAN, Edge Cloud, IP Backbone and DC network slices. The mechanism used to establish network slices in different domains and map the traffic to a network slice is outside the scope of this document. Cheng, et al. Expires February 25, 2022 [Page 4] Internet-Draft IETF Network Slice use cases August 2021 3.2. The branch departments that use slices within the operator. |---------------| |-----------------| |-------------| | A network | | Backbone Slice | | N network | | Controller | | Controller | | Controller | |---------------| |-----------------| |-------------| | | | |------------------------------------|--------------------------------| | | .---------------------------------------. | | | | / IP Backbone Network \ | | | | \ / | | | | `---------------------------------------' | | | -------| |--------| | | .-------------. .-------------. | | / sub-company A \ / sub-company N \ | | \ network / ...... \ network / | | `-------------' `-------------' | | Operator IP network | |---------------------------------------------------------------------| Figure 2 There are multiple sub-company network and IP Backbone network in an operator IP network, each with its own slice controller. Sub-company network can be the branches of the operator using slices. IP Backbone network slice is orchestrated by the IP Backbone network orchestrator, and the path is calculated through the IP Backbone network slice controller. For network slicing inside the local branch (sub-company network in the figure) is orchestrated through the orchestrator of the sub- company network. The sub-company network slice controller performs unified control and path calculation for the sub-company network. The path calculation and control of slices related to the IP Backbone are sent to the IP Backbone network slice controller through the eastbound and westbound interfaces, and the IP Backbone network slice controller controls and calculates the path. 3.2.1. Network Slice resource management Cheng, et al. Expires February 25, 2022 [Page 5] Internet-Draft IETF Network Slice use cases August 2021 |-----------------------------------------------------------------------------------------------| | Resource Type | Orchestrator resource management | |-----------------------------------------------------------------------------------------------| | Slice ID | Unified resource orchestration and planning, plan Slice ID by sub-company. | | | The orchestrator ensures that the IDs do not conflict with each other. | |-----------------------------------------------------------------------------------------------| | Node SID | Unified resource orchestration and planning. A unified coding mode is | | | recommended. | |-----------------------------------------------------------------------------------------------| |SR Policy Color| Unified resource orchestration and planning, and resource pool allocation. | |-----------------------------------------------------------------------------------------------| | VPN name | Unified resource orchestration and planning. Perform unified resource conflict| | | detection. VPN name within the same network element shall not be repeated. | |-----------------------------------------------------------------------------------------------| | VLAN sub-intf | Unified resource orchestration and planning: Resources are divided for VLAN | | | sub-interfaces under the same physical interface. | |-----------------------------------------------------------------------------------------------| 3.2.2. Domain governance of network slice |----------------------------------------------------------------------------------------------| | V | |-------------------| .--------. .--------. .---------. | V / Operation\ / Operation\ / Role \-------| . --------------------------. \ Set / \ Set / \ management/ . Security System . .--------. `--------' .--------. `--------' `---------' . administrator administrator . / Role Set \ ...... / Role Set \ A A | / \------> \ A / \ N / | | |--------| \ Maintainer Operator monitor / ` -------' ` -------' | | V . . /\ / | | .--------. .---------. ` --------------------------' / \ / | |--------/ Operation\ / User \ .------------------------. V V / V \ Set / \ management/---> . All user User Group . .-----. .-----. V .-----. `--------' `--------' / \--> / User \ / User \...... / User \ \ Current / \ A / \ B / \ N / . Login User Locked User . ` ----' ` ----' ` ----' `-----------------------' | / \ | V V \ V .-------------. V .-------------. / sub-company A \ ...... / sub-company N \ \ network / \ network / `-------------' `-------------' Cheng, et al. Expires February 25, 2022 [Page 6] Internet-Draft IETF Network Slice use cases August 2021 Role-based user rights management uses the role template to quickly allocate user rights, and provides network resources and sub-network slice resources for different users. 4. Security Considerations TBD 5. IANA Considerations This document does not have any requests for IANA allocation. This section may be removed before the publication of the draft. 6. Normative References [I-D.ietf-teas-ietf-network-slice-definition] Rokui, R., Homma, S., Makhijani, K., Contreras, L., and J. Tantsura, "Definition of IETF Network Slices", draft-ietf- teas-ietf-network-slice-definition-00 (work in progress), January 2021. [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, . Authors' Addresses Weiqiang Cheng China Mobile Beijing CN Email: chengweiqiang@chinamobile.com Wenying Jiang China Mobile Beijing CN Email: jiangwenying@chinamobile.com Cheng, et al. Expires February 25, 2022 [Page 7] Internet-Draft IETF Network Slice use cases August 2021 Ran Chen ZTE Corporation Email: chen.ran@zte.com.cn Liyan Gong China Mobile Beijing CN Email: gongliyan@chinamobile.com Chi Fan H3C Corporation Email: fanchi@h3c.com Shaofu Peng ZTE Corporation Email: peng.shaofu@zte.com.cn Cheng, et al. Expires February 25, 2022 [Page 8]