iple that traffic for different slices is handled by different packet data unit (PDU) sessions [10]. A network can realize the different network slices by scheduling and providing different physical layer (PHY) and medium access control (MAC) layer configurations [11]. Each network slice is uniquely identified by a Single Network Slice Selection Assistance Information (S-NSSAI), as defined in [11]. The NSSAI includes one or a list of where an S-NSSAI is a combination of: Mandatory SST (slice/service type) field, which identifies the slice type and consists of 8 bits (with range 0-255); Optional SD (slice differentiator) field, which differentiates among slices with the same SST field and consists of 24 bits. The UE provides NSSAI for network slice selection by radio resource control (RRC), if it has been provided by non-access stratum (NAS). While the network can support a large number of slices, the UE does not need to support more than eight slices simultaneously. The following key principles in [11] apply for the support of network slicing in NG-RAN: RAN awareness of slices: - NG-RAN supports a differentiated handling of traffic for different network slices that have been preconfigured. How NG-RAN supports slice enabling in terms of NG-RAN functions is implementation dependent. Selection of RAN of the network slice: - NG-RAN supports the selection of the RAN part of the network slice, by NSSAI pro- vided by the UE or the 5G core network (5GC), which unambiguously identifies one or more of the preconfigured network slices in public land mobile network (PLMN). Resource management between slices: NG-RAN supports policy enforcement between slices as per SLAs. It should be possible for a single NG-RAN node to support multiple slices. The NG-RAN should be free to apply the best radio resource management (RRM) policy for the SLA in place to each supported slice. Support of quality of service (QoS): - NG-RAN supports QoS differentiation within a slice. 12 Service-Oriented RAN Support of Network Slicing RAN selection o