the amf doesnt reroute the registration to another amf when it cant handle the NSSAI , and the amf doesn't check the NSSAi parameter rather it accept everything and authenticate the UE,
the normal behavior is :
During Registration, the initial AMF using the information, e.g. Requested NSAAI and subscribed NSSAI received from the device and UDM respectively and as well as inquiry from NSSF (Network Slice Selection Function) is able to check whether it can handle the registration process or it should re-route the registration request to another AMF (target AMF) for the further action. The target AMF then prepares the allowed and configured NSAAI and delivers it to the device via NAS-5GMM Registration Accept message.
the amf doesnt reroute the registration to another amf when it cant handle the NSSAI , and the amf doesn't check the NSSAi parameter rather it accept everything and authenticate the UE,
the normal behavior is :
During Registration, the initial AMF using the information, e.g. Requested NSAAI and subscribed NSSAI received from the device and UDM respectively and as well as inquiry from NSSF (Network Slice Selection Function) is able to check whether it can handle the registration process or it should re-route the registration request to another AMF (target AMF) for the further action. The target AMF then prepares the allowed and configured NSAAI and delivers it to the device via NAS-5GMM Registration Accept message.