原文：http://www.sharetechnote.com/html/5G/5G_NetworkSlicing.html

Data between UE and Network (or another UE) go through various components on the data path. In most case, the resource allocation and the data path is configured statically or semi-statically. We cannot say all those components are optimized for each individual user or each individual use case (e.g, rush time traffic, regular hour traffic, eMBB, IoT etc). However, in ideal case where you can configure resource allocation and parameters of the components along the data path dynamically (by automation), we may define a set of parameters of all the components on the data path in most optimal way for specific UEs or specific use cases. The specific set of parameters assigned for the UEs or use cases is called a ‘Slice’ of the network. Network Slice is a logical concept of splitting all the resources along the data path into multiple sets, each of which is optimized for specific UEs or use cases.

Implementation Requirement

I don’t think there is any specification which explicitely defines all the details on how to implement these slices. But by the nature of dynamic configuration changes, we would easily guess that all the network elements along the data path should be constructed in such a way to change the configuration by remote control and automation. That’s why the concept of network slicing can easily be achievable in 5G where most of the network components are designed for virtualization and the components along the transport (e.g, routers) is designed as SDN (Software Defined Network).

Slicing vs 5QI(QoS) vs DNN(APN)

Network Slicing vs Private Network

Signaling for Network Slicing

Identification of Network Slice