4.5.2.

6 Delivering the RRC Connection Reject Message

 After receiving RRC Connection Request message, the eNodeB delivers the
RRC Connection Reject message to the UE. When finding the RRC
Connection Reject message, you need to check the specific cause value:

 Congestion: In this case, you need to check the network usage.

 Unspecified: In this case, you need to check the log information.

 When receiving the RRC Connection Setup message, the UE fails to deliver
the RRC Connection Setup Complete message. If the signals in the downlink
are normal, you can infer that this problem may be caused by a handset fault.

 When the UE delivers the RRC Connection Setup Complete message, the
eNodeB fails to receive the RRC Connection Setup Complete message. There
is a very small probability that this problem will occur because the transmit
power of the UE will be increased through the initial uplink power control.
Temporarily, no good solution is readily available to this problem.

4.5.3 Authentication and Encryption Failures

 When an authentication failure occurs, you need to analyze potential factors,

depending on the cause value (MAC Failure or Synch Failure) carried in the
Authentication Failure message that is sent from the UE to the MME.

4.5.3.1 MAC Failure

 During the authentication procedure, the UE checks the AUTN parameter

carried in the Authentication Request message that is sent from the MME.
When finding incorrect MAC information, the UE delivers the Authentication
Failure message that carries the cause value (MAC Failure) to the MME, as
shown in Figure 4-71.