N3IWF Registration Signaling for Accurate Non-3GPP Authentication
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing 3GPP specification does not support direct access to the 3GPP network via a non-3GPP access network, leading to inaccurate authentication when terminals access the 3GPP network through untrusted non-3GPP networks.
Innovation Solution
A method and apparatus for accessing a 3GPP network via a non-3GPP access network, involving a terminal sending registration type, user identifier, and non-public network identifier to a non-3GPP interworking function (N3IWF), and subsequent communication with an access and mobility management function (AMF) to enhance authentication accuracy.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a vendor-specific EAP method (EAP-5G) is used for authentication, then the terminal can access the 3GPP network via non-3GPP access network, but the authentication accuracy deteriorates because the registration operation is not performed by the terminal
Solution Approach 1:
The terminal performs the registration operation itself rather than relying on network-side automatic registration. The terminal sends registration type, user identifier, and non-public network identifier to the N3IWF, enabling self-service registration that improves authentication accuracy by ensuring the terminal's registration intentions are accurately recorded.
Solution Approach 2:
The system establishes a feedback loop where the terminal's registration information is sent to the N3IWF, which then forwards it to the AMF. This feedback mechanism ensures that the authentication system has accurate, real-time information about the terminal's registration status and intentions, improving authentication accuracy.
2Measurement precision
If the terminal does not perform registration operation, then the authentication process is simplified, but the authentication accuracy deteriorates due to lack of accurate registration information
Solution Approach 1:
The terminal autonomously performs registration by sending its registration type, user identifier, and non-public network identifier to the N3IWF. This self-service approach ensures high measurement precision in registration information accuracy while the automated handling of the information reduces the actual operational burden on the terminal.
Solution Approach 2:
The N3IWF acts as an intermediary that receives registration information from the terminal and forwards it to the AMF. This intermediary mechanism ensures accurate registration information is captured and transmitted without requiring the terminal to directly interact with complex authentication systems, maintaining ease of operation.
3Adaptability or versatility
If direct access to 3GPP network via non-3GPP access network is supported, then network accessibility is improved, but authentication reliability deteriorates due to untrusted network environment
Solution Approach 1:
The N3IWF serves as a trusted intermediary between the non-3GPP access network and the 3GPP core network. It receives registration information from the terminal, validates it, and forwards it to the AMF. This intermediary ensures that even though the access network is untrusted, the authentication process maintains high reliability through proper information handling and validation.
Solution Approach 2:
The system implements feedback mechanisms where the terminal's registration information is continuously monitored and validated. The N3IWF and AMF ensure that only valid and authorized registration information is processed, maintaining authentication reliability even in untrusted network environments.
Data Source
AI summary
An authentication method for accessing a 3rd generation partnership project (3GPP) network via a non-3GPP access network, is performed by a terminal, and includes: in a case that the terminal accesses the 3GPP network via an untrusted non-3GPP access network, according to a performed registration operation, sending at least one of a registration type, a user identifier and an identifier of a non-public network, that the terminal needs to register with, corresponding to the registration operation to a non-3GPP interworking function (N3IWF).