**4.2 5G network slicing implementation**

An End-to-End (E2E) Network Slice consists of RU, RAN and Core Transport subnets. Basically, we have to designed Slice Profiles (for RAN, Core and Transport subnets) including the slice characteristics and requirements needed to support the service requested by the UE. Procedure for slicing is as follows:

1.Create slice profile:

The customer will provide their service requirements they want to run on a network slice including bandwidth, capacity, and latency. The operator creates a service level agreement, and allocates the necessary capacity and bandwidth for the slice by NSSAI (Network Slice Selection Assistance Information). NSSAI consists of up to 8 S-NSSAI (Single –NSSAI). The S-NSSAI contains two components: the SST (Slice/Service Type) and an optional SD (Slice Differentiator).

2.UE gathers information for slices when registering for the network:

The UE gathers information for the available slices when registering for the network via NAS signaling. A single UE may be assigned up to eight difference slices [31].

3.Determines the candidate AMF(s) or AMF Set to be used to serve the UE:

Once a PDU session is set up, the UE is then signaled to the NSSAI, assuming this has been provided earlier to the UE.

4. Selects which slices the UE can connect:

Based on required NSSAI and registered information, the network will select the appropriate slice instance and related resources, with the AMF coordinating the actions in the 5G core network. There is one AMF that is common for all the slices a single UE has.
