Is Authentication Result always present in 5G?
No. It is mainly associated with EAP-based authentication result delivery rather than every basic 5G AKA flow.
| Protocol | nas | Network | 5g |
|---|---|---|---|
| Spec | 3GPP TS 24.501 | Spec Section | 8.2.3 |
| Direction | AMF to UE | Message Type | 5GMM signaling |
| Full message name | 5G NAS - Authentication Result |
|---|---|
| Protocol | NAS |
| Technology | 5G |
| Direction | AMF to UE |
| Interface | N1 |
| Signaling bearer / channel | NAS signaling / Dedicated NAS message, commonly via DL Information Transfer |
| Typical trigger | Sent when the network must deliver EAP-based primary authentication result to the UE. |
| Main purpose | Carries the EAP success or failure result in EAP-based primary authentication. |
| Main specification | 3GPP TS 24.501, 8.2.3 |
| Release added | Release 15 |
| Procedures where used | 5G Authentication Procedure, 5G Initial Registration |
Authentication Result is the NAS message used to transport the final EAP authentication result from the network to the UE.
Carries the EAP success or failure result in EAP-based primary authentication.
Authentication Result tells the UE the final EAP-based authentication outcome.
Call flow position: Network result message in the EAP-based authentication branch.
Typical state: UE has already answered an EAP-based authentication request.
Preconditions:
Next likely message: Security Mode Command, Registration continuation, or termination depending on result
Previous message(s): Authentication Response
Next message(s): Security Mode Command, Registration Accept, Procedure termination
Security context: Used in the EAP-based authentication branch; protection depends on the exact procedure stage.
This message is not typically analyzed as ASN.1 on the wire. It is usually read as a NAS or protocol field structure instead.
Authentication Result is a NAS 24.501 message, not an ASN.1 message.
Authentication Result
Extended Protocol Discriminator: 5G Mobility Management
Security Header Type: Plain NAS
Message Type: Authentication Result
ngKSI: 3
EAP Message: Success
| IE | Required | Description |
|---|---|---|
ngKSI | Yes | Identifies the NAS key set context selected with the EAP result. |
EAP message | Yes | Carries the EAP success or EAP failure message delivered to the UE. |
ngKSIIdentifies the NAS key set context selected with the EAP result.
Presence: Required
In practice: In practice, compare this field with the original request and with any later release-dependent optional fields so you can see whether the network accepted the same service model the UE asked for.
EAP messageCarries the EAP success or EAP failure message delivered to the UE.
Presence: Required
In practice: If present, it reflects the external DN authentication result. It is worth checking when the session succeeds on NAS but service access still depends on an external authentication flow.
Likely cause: The EAP result may indicate failure or the next NAS step may not have been triggered correctly.
What to inspect: Check the EAP result contents and the next AMF action.
Next step: Verify whether the registration path continues into Security Mode Command or terminates.
No. It is mainly associated with EAP-based authentication result delivery rather than every basic 5G AKA flow.
Decode this message with the 3GPP Decoder, inspect the related message database, or open the matching call flow to see where this signaling step fits in the full procedure.