Value Call Release
Cause Description Collection Time
DEC HEX 256 0X0100 S1AP_CauseRadio Network_ unspecified A failure occurs in GW during the handover, or the handover preparation fails if the MME cannot process the handover.
When the target eNB receives the Handover Cancel message from the source eNB.
283 0x011B S1AP_invalid_qos_ combination
The action fails due to invalid QoS combination.
- When gbrType of QCI received within
E_RABLevelQoSParameters IE of the Initial Context Setup Request message is GBR but
gbrQosInformation received is not present.
- When gbrType of QCI received within
E_RABLevelQoSParameters IE of the E_RAB Setup Request message is GBR but
gbrQosInformation received is not present.
- When gbrType of QCI received within
E_RABLevelQoSParameters IE of the E_RAB Modify Request message is GBR but
gbrQosInformation received is not present.
307 0x0133 S1AP_authenticatio n_failure
The action occurs due to the authentication failure.
Used in the UE context release when the call fails due to the authentication failure.
566 0X0236 X2AP_CauseMisc_ unspecified
Default X2 cause in the eNB.
When the target eNB receives the Handover Cancel message from the source eNB.
768 0X0300 RRC_TMOUT_ rrcConnectionSetu p The RRC Connection Setup Complete message is not received after the RRC
Connection Setup message is sent to the UE.
When timRrcConnectionSetup message is received because the timer is ended that waits until the RRC Connection Setup Complete message is received after sending the RRC Connection Setup message to the UE
Value Call Release
Cause Description Collection Time
DEC HEX 769 0X0301 RRC_TMOUT_ rrcConnectionReco nfig The RRC Connection Reconfiguration
Complete message is not received after the RRC Connection
Reconfiguration message is sent to the UE.
When timRrcConnectionReconfig message is received due to the timer termination while waiting to receive the RRC Connection Reconfiguration Complete message after the RRC Connection Reconfiguration message is sent to the UE - SB2DB State: sending
Initial Context Setup Failure
- SB2DB state: Initial Context Setup Failure
- Other State: sending UE Context Release Request
- INCELLue state: UE Context Release Request
- REESTue2 state: UE Context Release Request
- GAPprepare state: UE Context Release Request
- ANRprepare state: UE Context Release Request 770 0X0302 RRC_TMOUT_ rrcConnectionReEs tablish The RRC Connection Reestablishment
Complete message is not received after the RRC Connection
Reestablishment message is sent to the UE.
When
timRrcConnectionReEstablish message is received due to the timer termination while waiting to receive the RRC Connection Reestablishment Complete message after the RRC Connection Reestablishment message is sent to the UE
771 0X0303
RRC_TMOUT_ rrcSecurityModeCo mmand
The Security Mode Complete message is not received after the Security Mode Command message is sent to the UE.
When the
timRrcSecurityModeCommand message is received due to the timer termination while waiting to receive Security Mode Complete message after the Security Mode Command message is sent to the UE 772 0X0304 RRC_TMOUT_ rrcUeCapabilityEnq uiry The UE Capability Information message is not received after the UE Capability Enquiry message is sent to the UE.
When the
timRrcUeCapabilityEnquiry message is received due to the timer termination while waiting to receive the UE Capability Information message after the UE Capability Enquiry message is sent to the UE 775 0X0307 RRC_TMOUT_intra _ HandoverCmdCom plete The RRC Connection Reconfiguration
Complete message is not received after the RRC Connection
Reconfiguration message is sent to the UE during the Intra handover.
When the timer ends while waiting to receive the RRC Connection Reconfiguration Complete message after the RRC Connection Reconfiguration message is sent to the UE during the intra eNB handover
Value Call Release
Cause Description Collection Time
DEC HEX 776 0X0308 RRC_TMOUT_inter _ X2HandoverCmdC omplete The RRC Connection Reconfiguration
Complete message is not received after the RRC Connection
Reconfiguration message is sent to the UE during the X2 handover.
When the timer ends while waiting to receive the RRC Connection Reconfiguration Complete message after the RRC Connection Reconfiguration message is sent to the UE during the intra X2 handover
777 0X0309 RRC_TMOUT_inter _ S1HandoverCmdC omplete The RRC Connection Reconfiguration
Complete message is not received after the RRC Connection
Reconfiguration message is sent to the UE during the S1 handover.
When the timer ends while waiting to receive the RRC Connection Reconfiguration Complete message after the RRC Connection Reconfiguration message is sent to the UE during the intra S1 handover
787 0X0313
S1AP_TMOUT_ s1InitialContextSet up
The Initial Context Setup Request message is not received after the Initial UE message is sent to the MME.
When the
timS1InitialContextSetup message is received due to the timer termination while waiting to receive the Initial Context Setup Request message after the Initial UE message is sent to the MME
790 0X0316
S1AP_TMOUT_ The Path Switch Request Acknowledge message is not received after the Path Switch Request message is sent to the MME.
When the timS1PathSwitch message is received due to the timer termination while waiting to receive the Path Switch Request Acknowledge message after the Path Switch Request message is sent to the MME
s1PathSwitch
792 0X0318
S1AP_TMOUT_ The UE Context Release Command message from the MME is not received because the handover is complete after the Handover Command message is received from the MME.
When the timS1RelocOverall message is received due to the timer termination while waiting to receive the UE Context Release Command message from the MME after the Handover Command message is received from the MME
s1RelocOverall
794 0x031A
S1AP_TMOUT_ s1MMEStatusTrans fer
The MME Status Transfer message is not received after the eNB Status Transfer message is sent to the MME.
When the timer ends while waiting for the MME Status Transfer message after the eNB Status Transfer message is sent to the MME
804 0x0324
X2AP_TMOUT_ The UE Context Release message is not received from the Target eNB because the handover is complete after the Handover Acknowledge message is received from the Target eNB.
When the timX2RelocOverall message is received due to the timer termination while waiting to receive the UE Context Release message after the Handover Acknowledge message is received from the target eNB x2RelocOverall
805 0x0325
X2AP_TMOUT_ x2SNStatusTransfe r
The MME Status Transfer message is not received after the eNB Status Transfer message is sent to the MME.
When the timer ends while waiting for the MME Status Transfer message after the eNB Status Transfer message is sent to the MME
Value Call Release
Cause Description Collection Time
DEC HEX
816 0X0330
RRC_TMOUT_ internalResourceSe tup
The response message is not received after the SetupReqe message is sent for setting the resource for the internal protocol blocks of the eNB.
When the
timInternalResourceSetup message is received due to the timer termination while waiting to receive the response after the SetupReq message is sent to assign resources to the protocol blocks within the eNB
- SB2DB state: Initial Context Setup Failure
- DB2DBScomplete state: UE Context Release Request, E_RAB Setup Response
- DB2DBMcomplete state: UE Context Release Request, E_RAB Modify Response
- DB2DBRfail state: E_RAB Release Response
- PHYREcomplete state: UE Context Release Request - INTERprepare_T state: Handover Failure 818 0X0332 RRC_TMOUT_ internalSecurityCon trol
After sending the msgCpdcpSecurityContr ol message to the PDCB, cannot receive the msgCpdcpSecurityContr olSuccess message
When receiving the timInternalSecurityControl message because the timer is ended that waits until the msgCpdcpSecurityControlSucces s message is received after sending the
msgCpdcpSecurityControl message to the PDCB
- SB2DBint state-SB2DBciph state
820 0X0334
RRC_TMOUT_ internalForwarding PathSetup
During Handover, after sending the
msgCgtpSetupReq message to the GTPB for setting uplink and downlink path, cannot receive the
msgCgtpSetupCnf message
During Handover, when the timInternalForwardingPathSetup message is received because the timer is ended that waits until the msgCgtpSetupCnf message is received after sending the msgCgtpSetupReq message to GTPB for setting the uplink, downlink path 821 0X0335 RRC_TMOUT_ internalReestablish Control The msgCrlcControlSuccess or msgCpdcpControlSucces s is not received after the msgCrlcControl,
msgCpdcpControl message is sent for RLC, PDCP reestablishment during inter eNB HO.
When the
timInternalReestablishControl message is received due to the timer termination while waiting to receive the
msgCrlcControlSuccess or msgCpdcpControlSuccess message after the msgCrlcControl or msgCpdcpControl message is sent for RLC, PDCP
reestablishment during inter eNB HO
Value Call Release
Cause Description Collection Time
DEC HEX 822 0X0336 RRC_TMOUT_ internalBufferFlush The msgCpdcpBufferFlushCn f message is not received after the msgCpdcpBufferFlush message is sent to the PDCB during handover.
When the timInternalBufferFlush message is received due to the timer termination while waiting to receive the
msgCpdcpBufferFlushCnf message after the
msgCpdcpBufferFlush message is sent to the PDCB during handover
823 0X0337 RRC_TMOUT_ internalDataTransfe rStart The msgCpdcpControlSucces s message is not received after the msgCpdcpControl message is sent.
When the
timInternalDataTransferStart message is received due to the timer termination while waiting to receive the
msgCpdcpControlSuccess message after the
msgCpdcpControl message is sent
- INCELLresume state: key refreshing
- INTRAresume state: Intra Cell handover
- INTERstart_T state: Inter eNB handover
- REESTresume1 state: Reestablish
833 0X0341 RRC_USER_INAC
TIVITY UE is in inactive status.
When the
msgCmacPhyUserInactivityInd message is received from the MACB.
834 0X0342
RRC_ARQ_MAX_ RE_
TRANSMISSION
After sending only as much as the RLC Max retransmission count, the UE status does not become active for a certain period of time.
When the timer ends while running the
timInternaReestablshTimeToWait timer after the
msgCrlcMaxRetransInd message is received from the RLCB 835 0X0343 RRC_RADIO_LINK
_ FAILURE
The radio link with the UE failed.
The MAC notifies the ECCB of the possible release of the uplink
Value Call Release
Cause Description Collection Time
DEC HEX
The MAC notifies the ECCB of the possible release of the uplink radio link with the UE if it fails to receive the HARQ-ACK/NACK 200 times or more
consecutively for the downlink data. If the ECCB is notified by the MAC of being InSync again (HARQ- ACK/NACK received 20 times), or if it fails to receive the RRC Connection Re- establishment Request from the UE, the call is released after a time-out (default: 5 seconds).
radio link with the UE if it fails to receive the HARQ-ACK/NACK 200 times or more consecutively for the downlink data
(msgCmacPhyOutOfSynchInd). If the ECCB is notified by the MAC of being InSync again (HARQ- ACK/NACK received 20 times), or if it fails to receive the RRC Connection Re-establishment Request from the UE, the call is released after a time-out (default: 5 seconds, timInternaReestablshTimeToWait) . 838 0X0346 RRC_REEST_FAIL _ INVALID_ STATE The RRC Connection Reestablishment Request message is received in the invalid state.
When the RRC Connection Reestablishment Request message is received by the incorrect state (SB2DB state), then the RRC Connection Reestablishment Reject message is sent 840 0X0348 S1AP_RCV_S1_ UECTXTRELEASE CMD_ ABNORMAL_STAT E
The UE Context Release Command is received in the unexpected abnormal state (the cause in the message: normal release, detach, successful handover). The eNB triggers the cause when it receives the UE Context Release Command message including ‘normal release’ in a state that does not involve the Initial Context Setup procedure.
When the cause of the UE Context Release Command received from the MME is: normal_release, detach or successful_handover while the procedure with the MME is not complete 841 0X0349 RRC_RCV_RESET _ REQUEST_FROM _ECMB
The call is released after the Reset Request message is received from the ECMB block.
When the Reset Request message is received from the ECMB block.
842 0X034A
S1AP_RCV_S1_R ESET_
FROM_MME
The call is released by receiving the Reset message from the MME.
When the Reset message is received from the MME
844 0X034C
S1AP_S1_SCTP_ OUT_OF_SERVIC E
The call is released after the S1 Association changes to ‘out of service.’
When the S1 status in the msgCsctpStatusInd message received from the SCTP is ‘out_of_service’
845 0X034D
RRC_RCV_CELL_ RELEASE_IND_FR OM_ ECMB
The call is released after the Cell Release Ind message is received
- When the Cell Release Ind is received from the ECMB block due to the CPRI failure
Value Call Release
Cause Description Collection Time
DEC HEX
from the ECMB block. - When the Cell Release Ind is received from the ECMB block due to the DSP failure
846 0x34E
RRC_DSP_AUDIT _RLC_
CALL_RELEASE
The call remains in the ECCB and MAC, but not in the RLC. This creates a resource mismatch and the call is released.
When the call remains in the ECCB and MAC, but not in the RLC when the msgCdspResourceNotification message is received 847 0x34F RRC_DSP_AUDIT _MAC_ CALL_RELEASE
The call remains in the ECCB and RLC, but not in the MAC. This creates a resource mismatch and the call is released.
When the call remains in the ECCB and RLC, but not in the MAC when the
msgCdspResourceNotification message is received 848 0x350 RRC_DSP_AUDIT _RLC_ MAC_CALL_RELE ASE
The call is cancelled due to the resource
mismatch, because the ECCB has remaining calls but the RLC and the MAC have no call remaining.
When the call remains in the ECCB, but not in the RLC and MAC when the
msgCdspResourceNotification message is received 849 0x351 RRC_SEC_ALGO RITHMS_COMBIN ATION_INVALID
The security algorithm value is received in the Initial Context Setup Request, S1 Handover Request, X2 Handover Request, and S1 UE Context Modification message. The ciphering algorithm should have the null algorithm value if the integrity algorithm supports the null
algorithm. Otherwise, the call is released.
When the ciphering algorithm does not have the null algorithm value even if the integrity algorithm supports the null algorithm 851 0x353 ECCB_RELEASE_ DUE_ TO_ENB_GENERA TED_ REASON
The call is released due to the internal cause of the eNB.
When the relcallall command is executed
875 0X036B RRM_MAX_DRB_ COUNT_ OVER
If calls are generated more than the number of DRB that can be accommodated by cell, they are rejected by CAC.
When DRB ID and LOCH ID are assigned after the Initial Context Setup Request or E-RAB Setup Request message is received
876 0X036C RRM_QOSCAC_F AIL
If calls with the QoS that cannot be
accommodated by cell, they are rejected by CAC.
When the permission is checked to allow new calls after the Rrc Connection Request or Handover Request message is received.
880 0X0370 RRM_RBID_FULL
If DRB is generated exceeding the MAX_DRB or MAX_LOGH per call, DRB ID and LOCH ID cannot be assigned.
When DRB ID and LOCH ID are assigned after the Initial Context Setup Request or E-RAB Setup Request message is received
Value Call Release
Cause Description Collection Time
DEC HEX
881 0x0371 ECCB_ERRM_BH CAC_FAIL
Occurs when the BH link usage by the QoS (GBR Bearer) exceeds the threshold defined in the PLD.
When the permission is checked to allow new calls after the Rrc Connection Request or Handover Request message is received.
888 0X0378 RRM_SRS_MUST _BE_ ASSIGNED
If a new call supports both SRS and DRX, the SRS resources need to assigned in advance to assign the DRX resources but cannot assign the DRX resources because the SRS resource is not assigned.
When assigning the DRX resources if a new call supports both SRS and DRX
892 0X037C RRM_CQIPMI_DB _ ABNORMAL
The database in the CQI/PMI is abnormal.
When assigning CQI/PMI resources CQI/PMI resources cannot be assigned to new calls. 893 0X037D RRM_CQIPMI_DB _FULL
CQI/PMI resources are all assigned and not available any more.
When assigning CQI/PMI resources 898 0X0382 RRM_SPS_DB_AB NORMAL During SPS resource assignment and cancellation, the SPS resource search is not allowed to exceed the Max value of the SPS resource DB.
- When SPS resources are assigned for the QCI 1 existing in the DRB after the Initial Context Setup Request or E-RAB Setup Request message is received, or the SPS resources are cleared following the DRB release of the QCI 1 - When fnELIB_DecisionDrxSpsConfig is called. 899 0X0383 RRM_SPS_DB_FU LL
SPS resources are all assigned and not available any more.
- When SPS resources are assigned for the QCI 1 existing in the DRB after the Initial Context Setup Request or E-RAB Setup Request message is received - When fnELIB_DecisionDrxSpsConfig is called. 900 0X0384 RRM_SPS_ALREA DY_ ASSIGNED Assigning duplicate resources is not allowed since the SPS resources are already assigned.
- When SPS resources are assigned for the QCI 1 existing in the DRB after the Initial Context Setup Request or E-RAB Setup Request message is received - When
fnELIB_DecisionDrxSpsConfig is called.
Value Call Release
Cause Description Collection Time
DEC HEX
901 0X0385 RRM_SPS_RNTI_ FULL
RNTIs used for the SPS purpose are all assigned and not available any more.
- When SPS resources are assigned for the QCI 1 existing in the DRB after the Initial Context Setup Request or E-RAB Setup Request message is received - When fnELIB_DecisionDrxSpsConfig is called. 903 0X0387 RRM_N1PUCCHA N_REP_ DB_ABNORMAL n1PucchAnRep resources are all assigned and not available any more.
n1PucchAnRep resources are assigned after the Rrc Connection Request or Handover Request message is received. 905 0X0389 RRM_N1PUCCHA N_REP_ ALREADY_ASSIG NED
Since there are already assigned resources regarding the
N1PUCCHAN_REP on the call, it is not assigned.
When assigning N1PUCCHAN REP resources
907 0X038B
RRM_N1PUCCH_ DB_
INSUFFICIENT
Cannot initialize because the capacity of
N1PUCCH internal resource DB is too small.
When the database for
N1PUCCHAN REP resources is initialized 908 0X038C RRM_SR_DB_ABN ORMAL During SR resource assignment and cancellation, the SR resource search is not allowed to exceed the Max value of the SPS resource DB.
When SR resources are assigned after the Rrc Connection Request or Handover Request message is received, or the SR resources are cleared following the call release
909 0X038D RRM_SR_DB_FUL L
SR resources are all assigned and not available any more.
When SR resources are assigned after the Rrc Connection Request or Handover Request message is received
910 0X038E RRM_SR_ALREAD Y_ ASSIGNED
Since there are already assigned resources regarding the SR on the call, it is not assigned.
When assigning SR resources
919 0X0397 RRM_SRS_DB_ ABNORMAL
During SR resource assignment and cancellation, a database search for the SRS resource exceeds the range of resources secured.
When SRS resources are
assigned after the Rrc Connection Request or Handover Request message is received, or the SRS resources are cleared following the call release
920 0X0398 RRM_SRS_DB_FU LL
SRS resources are all assigned.
When SRS resources are
assigned after the Rrc Connection Request or Handover Request message is received
921 0X0399 RRM_SRS_ALREA DY_ ASSIGNED
Since there are already assigned resources regarding the SRS on the call, it is not assigned.
Value Call Release
Cause Description Collection Time
DEC HEX 923 0X039B RRM_TPC_PUCC H_ RNTI_DB_ABNOR MAL During TPC PUCCH RNTI resource assignment and cancellation, the TPC PUCCH resource search is not allowed to exceed the Max value of TPC PUCCH resource DB.