文档介绍：Contents 1 Introduction 5Service Capability of Network Slicing in 5G device 5
Typical Use Cases and Scenarios of Networ should construct a Requested NSSAI based on its existing Configured NSSAI and Allowed NSSAI (if the device has saved a previous Allowed NSSAI before this procedure). After receiving the Requested NSSAI, the network will determine the set of network slices in which to register the UE and return it to the device as Allowed NSSAI.
If some S-NSSAIs in the Allowed NSSAI need authentication and authorization before they can be used, then the network will inform the device that the S-NSSAIs should be kept in Pending NSSAI before the authentication and authorization procedure is completed.
If some S-NSSAIs are not supported by the network or cannot be used temporarily, then the network will inform the device that the S-NSSAIs are kept in Rejected NSSAI. When applying a network slice for its application service flow, the device should not use the S-NSSAIs in Rejected NSSAI.
To match an application service flow with a network slice, devices use URSP that are either locally configured or configured by the network.
The network can use standard UCU (UE configuration Update) procedure to update URSP and NSSAI in the UE.
Setting up PDU sessions over a network sliceWhen a network application service flow needs communication service, the device will initiate the PDU session setup procedure. According to URSP, the device can indicate its desired S-NSSAI during the PDU session setup procedure, or the network can assign a network slice to be used for the PDU session.
Generally, if a network application service flow needs to use a dedicated network slice, then the operator should configure a corresponding network slice for the service flow in URSP. When setting up a PDU session, the device should carry the corresponding S-NSSAI to request the network to select the related slice.
Maintaining PDU sessions over a network sliceNetwork slicing is managed by each PLM