Content for  TS 38.300  Word version:  16.3.0

Top   Top   Up   Prev   Next
1…   4…   4.7…   5…   5.3…   5.4…   6…   6.2…   6.6…   7…   8…   9…   9.2.2…   9.2.3……   9.2.4…   9.2.6…   9.3…   10…   11…   15…   15.5…   16…   16.3   16.4…   17…   A…   B…


16.3  Network Slicing

16.3.1  General Principles and Requirements

In this clause, the general principles and requirements related to the realization of network slicing in the NG-RAN for NR connected to 5GC and for E-UTRA connected to 5GC are given.
A network slice always consists of a RAN part and a CN part. The support of network slicing relies on the principle that traffic for different slices is handled by different PDU sessions. Network can realise the different network slices by scheduling and also by providing different L1/L2 configurations.
Each network slice is uniquely identified by a S-NSSAI, as defined in TS 23.501. NSSAI (Network Slice Selection Assistance Information) includes one or a list of S-NSSAIs (Single NSSAI) where a S-NSSAI is a combination of:
  • mandatory SST (Slice/Service Type) field, which identifies the slice type and consists of 8 bits (with range is 0-255);
  • optional SD (Slice Differentiator) field, which differentiates among Slices with same SST field and consist of 24 bits.
The list includes at most 8 S-NSSAI(s).
The UE provides NSSAI (Network Slice Selection Assistance Information) for network slice selection in RRCSetupComplete, if it has been provided by NAS (see clause While the network can support large number of slices (hundreds), the UE need not support more than 8 slices simultaneously. A BL UE or a NB-IoT UE supports a maximum of 8 slices simultaneously.
Network Slicing is a concept to allow differentiated treatment depending on each customer requirements. With slicing, it is possible for Mobile Network Operators (MNO) to consider customers as belonging to different tenant types with each having different service requirements that govern in terms of what slice types each tenant is eligible to use based on Service Level Agreement (SLA) and subscriptions.
The following key principles apply for support of Network Slicing in NG-RAN:
RAN awareness of slices
  • NG-RAN supports a differentiated handling of traffic for different network slices which have been pre-configured. How NG-RAN supports the slice enabling in terms of NG-RAN functions (i.e. the set of network functions that comprise each slice) is implementation dependent.
Selection of RAN part of the network slice
  • NG-RAN supports the selection of the RAN part of the network slice, by NSSAI provided by the UE or the 5GC which unambiguously identifies one or more of the pre-configured network slices in the PLMN.
Resource management between slices
  • NG-RAN supports policy enforcement between slices as per service level agreements. It should be possible for a single NG-RAN node to support multiple slices. The NG-RAN should be free to apply the best RRM policy for the SLA in place to each supported slice.
    Support of QoS
  • NG-RAN supports QoS differentiation within a slice.
RAN selection of CN entity
  • For initial attach, the UE may provide NSSAI to support the selection of an AMF. If available, NG-RAN uses this information for routing the initial NAS to an AMF. If the NG-RAN is unable to select an AMF using this information or the UE does not provide any such information the NG-RAN sends the NAS signalling to one of the default AMFs.
  • For subsequent accesses, the UE provides a Temp ID, which is assigned to the UE by the 5GC, to enable the NG-RAN to route the NAS message to the appropriate AMF as long as the Temp ID is valid (NG-RAN is aware of and can reach the AMF which is associated with the Temp ID). Otherwise, the methods for initial attach applies.
Resource isolation between slices
  • The NG-RAN supports resource isolation between slices. NG-RAN resource isolation may be achieved by means of RRM policies and protection mechanisms that should avoid that shortage of shared resources in one slice breaks the service level agreement for another slice. It should be possible to fully dedicate NG-RAN resources to a certain slice. How NG-RAN supports resource isolation is implementation dependent.
Access control
  • By means of the unified access control (see clause 7.4), operator-defined access categories can be used to enable differentiated handling for different slices. NG-RAN may broadcast barring control information (i.e. a list of barring parameters associated with operator-defined access categories) to minimize the impact of congested slices.
Slice Availability
  • Some slices may be available only in part of the network. The NG-RAN supported S-NSSAI(s) is configured by OAM. Awareness in the NG-RAN of the slices supported in the cells of its neighbours may be beneficial for inter-frequency mobility in connected mode. It is assumed that the slice availability does not change within the UE's registration area.
  • The NG-RAN and the 5GC are responsible to handle a service request for a slice that may or may not be available in a given area. Admission or rejection of access to a slice may depend by factors such as support for the slice, availability of resources, support of the requested service by NG-RAN.
Support for UE associating with multiple network slices simultaneously
  • In case a UE is associated with multiple slices simultaneously, only one signalling connection is maintained and for intra-frequency cell reselection, the UE always tries to camp on the best cell. For inter-frequency cell reselection, dedicated priorities can be used to control the frequency on which the UE camps.
Granularity of slice awareness
  • Slice awareness in NG-RAN is introduced at PDU session level, by indicating the S-NSSAI corresponding to the PDU Session, in all signalling containing PDU session resource information.
Validation of the UE rights to access a network slice
  • It is the responsibility of the 5GC to validate that the UE has the rights to access a network slice. Prior to receiving the Initial Context Setup Request message, the NG-RAN may be allowed to apply some provisional/local policies, based on awareness of which slice the UE is requesting access to. During the initial context setup, the NG-RAN is informed of the slice for which resources are being requested.

16.3.2  AMF and NW Slice SelectionWord‑p. 120  CN-RAN interaction and internal RAN aspects

NG-RAN selects AMF based on a Temp ID or NSSAI provided by the UE over RRC. The mechanisms used in the RRC protocol are described in the next clause.
Temp ID
AMF Selection by NG-RAN

not available or invalid
not available
One of the default AMFs is selected (NOTE)
not available or invalid
Selects AMF which supports UE requested slices
not available, or present
Selects AMF per CN identity information in Temp ID  Radio Interface Aspects

When triggered by the upper layer, the UE conveys the NSSAI over RRC in the format explicitly indicated by the upper layer.

16.3.3  Resource Isolation and Management

Resource isolation enables specialized customization and avoids one slice affecting another slice.
Hardware/software resource isolation is up to implementation. Each slice may be assigned with either shared or dedicated radio resource up to RRM implementation and SLA.
To enable differentiated handling of traffic for network slices with different SLA:
  • NG-RAN is configured with a set of different configurations for different network slices by OAM;
  • To select the appropriate configuration for the traffic for each network slice, NG-RAN receives relevant information indicating which of the configurations applies for this specific network slice.

16.3.4  Signalling Aspects  General

In this clause, signalling flows related to the realization of network slicing in the NG-RAN are given.  AMF and NW Slice Selection

RAN selects the AMF based on a Temp ID or NSSAI provided by the UE.
Reproduction of 3GPP TS 38.300, Figure AMF selection
In case a Temp ID is not available, the NG-RAN uses the NSSAI provided by the UE at RRC connection establishment to select the appropriate AMF (the information is provided after MSG3 of the random access procedure). If such information is also not available, the NG-RAN routes the UE to one of the configured default AMF(s).
The NG-RAN uses the list of supported S-NSSAI(s) previously received in the NG Setup Response message when selecting the AMF with the NSSAI. This list may be updated via the AMF Configuration Update message.
Up  UE Context HandlingWord‑p. 121
Following the initial access, the establishment of the RRC connection and the selection of the correct AMF, the AMF establishes the complete UE context by sending the Initial Context Setup Request message to the NG-RAN over NG-C. The message contains the Allowed NSSAI and additionally contains the S-NSSAI(s) as part of the PDU session(s) resource description when present in the message. Upon successful establishment of the UE context and allocation of PDU session resources to the relevant network slice(s) when present, the NG-RAN responds with the Initial Context Setup Response message.
Reproduction of 3GPP TS 38.300, Figure Network Slice-aware Initial Context Setup
Up  PDU Session Setup Handling

When new PDU sessions need to be established, the 5GC requests the NG-RAN to allocate/ resources relative to the relevant PDU sessions by means of the PDU Session Resource Setup procedures over NG-C. One S-NSSAI is added per PDU session to be established, so NG-RAN is enabled to apply policies at PDU session level according to the SLA represented by the network slice, while still being able to apply (for example) differentiated QoS within the slice.
NG-RAN confirms the establishment of the resources for a PDU session associated to a certain network slice by responding with the PDU Session Resource Setup Response message over the NG-C interface.
Reproduction of 3GPP TS 38.300, Figure Network Slice-aware PDU Session Resource Setup
Up  MobilityWord‑p. 122
To make mobility slice-aware in case of Network Slicing, S-NSSAI is introduced as part of the PDU session information that is transferred during mobility signalling. This enables slice-aware admission and congestion control.
Both NG and Xn handovers are allowed regardless of the slice support of the target NG-RAN node i.e. even if the target NG-RAN node does not support the same slices as the source NG-RAN node. An example for the case of connected mode mobility across different Registration Areas is shown in Figure for the case of NG based handover and in Figure for the case of Xn based handover.
Reproduction of 3GPP TS 38.300, Figure NG based mobility across different Registration Areas
Reproduction of 3GPP TS 38.300, Figure Xn based mobility across different Registration Areas

Up   Top   ToC