Telecom engineering reference for protocols, messages, call flows, troubleshooting, releases, and tools.
Menu
NASLTEUE to MME3GPP TS 24.301
LTE Authentication Response
Authentication Response is the EPS NAS message the UE sends after Authentication Request to return the calculated response parameter and let EPS authentication continue.
Message Fact Sheet
Protocol
nas
Network
lte
Spec
3GPP TS 24.301
Spec Section
5.4.2.3, 8.2.8
Direction
UE to MME
Message Type
EMM signaling
Full message name
LTE Authentication Response
Protocol
NAS
Technology
LTE
Direction
UE to MME
Interface
N1 over LTE access / S1-MME control path
Signaling bearer / channel
NAS signaling / Commonly carried in uplink NAS transport after the UE receives Authentication Request during attach, TAU, or service-request continuation
Typical trigger
Sent after the UE successfully validates Authentication Request and computes the response to the RAND and AUTN challenge.
Main purpose
Carries the UE-computed authentication response so the network can verify the subscriber challenge and decide whether attach, TAU, or service restoration may continue.
Main specification
3GPP TS 24.301, 5.4.2.3, 8.2.8
Release added
Release 8
Procedures where used
EPS NAS Authentication Procedure, LTE Attach Procedure, Tracking Area Updating Procedure, LTE Service Request Procedure
What is LTE Authentication Response in simple terms?
Authentication Response is the EPS NAS message the UE sends after Authentication Request to return the calculated response parameter and let EPS authentication continue.
Carries the UE-computed authentication response so the network can verify the subscriber challenge and decide whether attach, TAU, or service restoration may continue.
Why this message matters
Authentication Response is the UE answering the network's LTE/EPS authentication challenge so the procedure can continue.
Where this message appears in the call flow
Initial LTE attach authentication response
In the attach path, Authentication Response is the UE answer that allows the network to move from challenge handling into later security and attach continuation.
Call flow position: UE reply sent after Authentication Request in the attach procedure.
Typical state: The attach path is waiting for subscriber proof before the MME can continue into security mode or attach completion.
Preconditions:
The UE received Authentication Request during attach.
The UE validated the challenge and can compute the authentication response.
Next likely message: Security Mode Command, Attach Accept, or Authentication Reject
Tracking area update authentication response
In the TAU path, Authentication Response shows that the UE answered the subscriber challenge before the MME resumes the mobility-refresh branch.
Call flow position: UE reply sent after Authentication Request in the TAU path.
Typical state: The UE is trying to keep existing EPS registration context, but the network required authentication before TAU continuation.
Preconditions:
The UE received Authentication Request during tracking area update.
The UE can answer the authentication challenge.
Next likely message: Security Mode Command or later TAU continuation
Service restoration authentication response
In the service-restoration path, Authentication Response explains why the branch detoured through common NAS authentication before later service handling.
Call flow position: UE reply sent after Authentication Request in the service-request path.
Typical state: The UE is restoring service using existing EPS context, but the MME required subscriber verification before allowing the service branch to continue.
Preconditions:
The UE received Authentication Request after Service Request.
The UE accepted the challenge and produced the response.
Next likely message: Security Mode Command, Service Accept, Service Reject, or Authentication Reject
Interface: N1 over LTE access / S1-MME control path
Domain: Core-side EPS mobility management and security signaling used before later NAS security continuation
Signaling bearer: NAS signaling
Logical channel: Commonly carried in uplink NAS transport after the UE receives Authentication Request during attach, TAU, or service-request continuation
Transport / encapsulation: EPS NAS message sent by the UE and delivered to the MME through the eNodeB as part of the NAS authentication procedure
Security context: Authentication Response is sent while the authentication procedure is still in progress, so it sits in the transition between provisional context and trusted security continuation.
Message Structure Overview
Authentication Response is an EPS mobility-management message rather than an ASN.1 LTE RRC structure.
The practical reading path starts with the authentication response parameter and the higher-level procedure that triggered it.
In real traces, this message is the UE proof step that decides whether common NAS authentication can move into later security or acceptance handling.
ASN.1 Message Syntax for LTE Authentication Response
Authentication Response is a NAS layer-3 message, not an ASN.1 LTE RRC message. Read it together with the earlier Authentication Request because the response parameter only makes sense in the context of that challenge.
Start by confirming that the response follows the expected Authentication Request in the same procedure branch.
The key field is the authentication response parameter because it is the UE proof sent back to the network.
After this message, the most useful next check is whether the network continues into Security Mode Command or ends the branch.
Important Information Elements
IE
Required
Description
Authentication response parameter
Yes
Carries the UE-computed response to the authentication challenge so the network can verify the subscriber.
Detailed field explanation
Authentication response parameter
Carries the UE-computed response to the authentication challenge so the network can verify the subscriber.
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.
What to check in logs and traces
Confirm which higher-level NAS procedure triggered Authentication Response.
Correlate it with the exact Authentication Request that came before it.
Check whether the response appears promptly or only after abnormal delay.
Follow the trace immediately into Security Mode Command, Authentication Reject, or later accept handling.
If the response is missing, compare with Authentication Failure and lower-layer delivery problems.
Common Issues and Troubleshooting
Authentication Request is visible but the procedure does not continue cleanly.
Likely cause: Authentication Response may be missing, delayed, or not accepted by the network.
What to inspect: Check the uplink NAS delivery of Authentication Response and the next network message after it.
Next step: Decide first whether the problem is UE-side challenge handling, uplink delivery, or network-side authentication validation.
Attach or TAU pauses after the authentication challenge.
Likely cause: The network is still waiting for Authentication Response or did not accept the response it received.
What to inspect: Compare Authentication Request, Authentication Response, and the next Security Mode Command or reject branch.
Next step: Treat the trace as an authentication checkpoint issue before blaming later accept or reject messages.
Service restoration does not move into Service Accept even though Authentication Request was present.
Likely cause: The UE may have answered, but the network may still reject or terminate the procedure after validating the response.
What to inspect: Check Service Request, Authentication Request, Authentication Response, and the next network message as one combined sequence.
Next step: Read the whole branch as service request plus common NAS authentication rather than only as a resume failure.
LTE / 5G / Variant Comparison
Compared with Authentication Request
Authentication Request is the network challenge. Authentication Response is the UE answer to that challenge.
Compared with Authentication Failure
Authentication Response is sent when the UE can answer the challenge. Authentication Failure is sent when the UE detects a problem such as MAC failure or synch failure.
Compared with Security Mode Command
Authentication Response is still part of subscriber verification. Security Mode Command comes later when the network continues into security activation after successful authentication.
FAQ
What is Authentication Response in LTE?
It is the EPS NAS message the UE sends to answer Authentication Request and prove subscriber credentials.
What should I inspect first in Authentication Response?
Start with the higher-level procedure and the authentication response parameter, then move to the next network message.
What usually comes after Authentication Response?
The network usually continues with Security Mode Command, later accept handling, or ends the branch with Authentication Reject if authentication cannot continue.
Why is Authentication Response important in troubleshooting?
Because it shows that the UE answered the challenge, which helps separate missing-response problems from later network validation or security-continuation problems.
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.
