5G Authentication Type Selection for Non-3GPP UE Registration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing 5G UEs that are non-5G capable over non-3GPP access networks face registration failures due to the inability to support 5G NAS protocols, leading to incorrect authentication method selection by the UDM based solely on SUPI, which results in unsupported authentication methods.
Innovation Solution
Enhanced authentication method selection process involving the TWIF and AMF to derive or include an Authentication Request Type in the NAS Registration Request, ensuring the UDM selects the appropriate EAP-AKA' method for non-5G capable UEs accessing the 5G network via non-3GPP access networks.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If the UDM selects authentication method based solely on SUPI, then the authentication process is simple, but non-5G capable UEs experience registration failures due to incorrect authentication method selection
Solution Approach 1:
The AMF determines the authentication request type (5G-AKA or EAP-AKA') before forwarding the authentication request to the UDM. This preliminary determination ensures that the UDM receives the correct authentication type information and selects the appropriate authentication vector, preventing registration failures for non-5G capable UEs while maintaining a relatively simple overall process
Solution Approach 2:
The AMF acts as an intermediary between the UDM and the authentication process. It receives the authentication type determination from the TWIF or derives it itself, then communicates this information to the UDM in the authentication request message. This intermediary role ensures that the UDM has the necessary context to select the correct authentication method without complicating the UDM's own logic
2Adaptability or versatility
If the system supports both 5G-AKA and EAP-AKA' authentication methods, then compatibility with different UE types is improved, but the authentication method selection complexity increases
Solution Approach 1:
The authentication method selection is segmented into distinct responsibilities: the TWIF determines the authentication request type based on UE capabilities, the AMF receives and processes this determination (or derives it itself), and the UDM selects the specific authentication vector based on the provided authentication type. This segmentation allows each component to remain relatively simple while supporting multiple authentication methods
Solution Approach 2:
The authentication type determination is performed locally at the AMF based on the access network type (3GPP or non-3GPP) and UE capabilities. This local determination ensures that each UE receives the appropriate authentication method tailored to its specific capabilities and the access network being used, without requiring complex centralized decision-making logic
Data Source
AI summary
Apparatuses, methods, and systems are disclosed for selecting an authentication type in a 5G network. One apparatus includes a processor and a network interface that receives a first message requesting to register a remote unit to the mobile communication network, where the remote unit is connected to a non-3GPP access network and the remote unit does not support the NAS protocol. The processor determines an authentication request type for the remote unit, where the authentication request type is not based on the NAS protocol. The processor creates a NAS registration message on behalf of the remote unit and sends a second message to an access management function in the mobile communication network, where the second message contains the NAS registration message and the determined authentication request type.