Network Slicing Use Cases: Network Customization for Different Services
draft-qin-netslices-use-cases-00

Document Type Active Internet-Draft (individual)
Last updated 2017-03-13
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                             J. Qin
Internet-Draft                                              K. Makhijani
Intended status: Informational                                   J. Dong
Expires: September 14, 2017                                     L. Qiang
                                                                 S. Peng
                                                     Huawei Technologies
                                                          March 13, 2017

Network Slicing Use Cases: Network Customization for Different Services
                    draft-qin-netslices-use-cases-00

Abstract

   Network Slicing (NS) is widely discussed and considered in 5G
   communities and standard organizations as a key mechanism to meet
   diverse service requirements concurrently with the same physical
   network infrastructure.  NS enables the operator to provide isolated
   platform for service verticals, and deploy new services without
   causing or experiencing any disruption to other already deployed
   services in the same physical network infrastructure.  This document
   describes the typical use cases that could benefit from network
   slicing, to support each case, the corresponding requirements on 5G
   transport network will be analyzed.

Requirements Language

   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 RFC 2119 [RFC2119].

   Additionally, the key words "MIGHT", "COULD", "MAY WISH TO", "WOULD
   PROBABLY", "SHOULD CONSIDER", and "MUST (BUT WE KNOW YOU WON'T)" in
   this document are to interpreted as described in RFC 6919 [RFC6919].

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 http://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

Qin, et al.            Expires September 14, 2017               [Page 1]
Internet-Draft        Use Case for Network Slicing            March 2017

   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 September 14, 2017.

Copyright Notice

   Copyright (c) 2017 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
   (http://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  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Network Customization Requirement for Diverse Services  . . .   4
     2.1.  Overview  . . . . . . . . . . . . . . . . . . . . . . . .   4
     2.2.  Network Customization Concept . . . . . . . . . . . . . .   4
     2.3.  Service Requirements from Customized Networks . . . . . .   4
   3.  Use Cases Demanding NS  . . . . . . . . . . . . . . . . . . .   5
     3.1.  eMBB Type NS Use Case . . . . . . . . . . . . . . . . . .   5
       3.1.1.  HD Video  . . . . . . . . . . . . . . . . . . . . . .   5
       3.1.2.  Virtual Reality (VR)/Augmented Reality (AR) . . . . .   5
     3.2.  uRLLC Type NS Use Case  . . . . . . . . . . . . . . . . .   6
       3.2.1.  Industrial Operation and Inspection . . . . . . . . .   6
       3.2.2.  Remote Surgery  . . . . . . . . . . . . . . . . . . .   6
       3.2.3.  Vehicle-to-everything (V2X) . . . . . . . . . . . . .   6
     3.3.  mMTC Type NS use case . . . . . . . . . . . . . . . . . .   7
       3.3.1.  Smart City  . . . . . . . . . . . . . . . . . . . . .   7
       3.3.2.  Health Monitoring . . . . . . . . . . . . . . . . . .   7
     3.4.  Other Type NS Use Case  . . . . . . . . . . . . . . . . .   7
       3.4.1.  Use Cases Have Mixed Requirements . . . . . . . . . .   8
Show full document text