 be concurrently connected to multiple network slices with the only limitation that RAN and AMF are shared across those network slices. In contrast to EPS where the SGW was shared across all sessions of a UE, 5GC enables operators to deploy fully isolated sets of session-related network functions (SMF, UPF, PCF) for different PDU sessions of a UE as shown in Figure 3.2.12. To facilitate this, the UE provides assistance information (referred to as Single Network Slice Selection Assistance Information [S-NSSAI]) to the network during PDU session establishment. The network uses S-NSSAI as additional input for selection of session-related network functions (SMF, UPF, PCF) within the network slice as requested by the UE. Support for RAN slicing: the UE informs the RAN about the network slices the UE intends to access by sending Requested NSSAI. Like DCN-IDs in the Release-14 enhancements to 3.2 5G Core Network Core network slice A Data network (1) Requested NSSAI (2) RAN selects an AMF that supports network slices identified by Requested NSSAI Data network (3) AMF selects SMF based on S-NSSAI and Data Network Name (DNN) Core network slice B provided by the UE Figure 3.2.12 Release-15 enables UEs to concurrently access multiple network slices with independent sets of session-related functions (SMF, UPF, PCF), AMF and UDM are shared across the network slices. DECOR, Requested NSSAI enables RAN to select a serving AMF for the UE that supports the set of network slices requested by the UE, i.e. avoids unnecessary redirections. The core network also makes RAN aware of the network slice that a given PDU session of a UE belongs to by passing the S-NSSAI requested by the UE for a new PDU session to RAN. The latter enables RAN to perform resource isolation and differentiated handling of traffic of PDU sessions that belongs to different slices. Network slice selection policies for the UE: the fact that the UE can access multiple slices at the same time raises the question of how to determine which network slice to request for w