Radio Network Layer Cause

Download as xlsx, pdf, or txt
Download as xlsx, pdf, or txt
You are on page 1of 6

Radio Network Layer cause

Unspecified
TX2RELOCOverall Expiry
Successful Handover
Release due to E-UTRAN generated reason
Handover Cancelled

Partial Handover

Handover Failure In Target EPC/eNB Or Target System


Handover Target not allowed
TS1RELOCoverall Expiry
TS1RELOCprep Expiry
Cell not available
Unknown Target ID
No radio resources available in target cell

Unknown or already allocated MME UE S1AP ID

Unknown or already allocated eNB UE S1AP ID

Unknown or inconsistent pair of UE S1AP ID

Handover Desirable for Radio Reasons

Time Critical Handover

Resource Optimisation Handover

Reduce Load in Serving Cell

User Inactivity

Radio Connection With UE Lost


Load Balancing TAU Required
CS Fallback triggered
UE Not Available for PS Service
Radio resources not available
Invalid QoS combination
Inter-RAT Redirection
Failure in the Radio Interface Procedure
Interaction with other procedure
Unknown E-RAB ID

Multiple E-RAB ID Instances

Encryption and/or integrity protection algorithms not supported


S1 Intra system Handover triggered
S1 Inter system Handover triggered
X2 Handover triggered
Redirection towards 1xRTT
Not supported QCI Value

Transport Layer cause


Transport Resource Unavailable

Unspecified

NAS cause
Normal Release
Authentication Failure
Detach

Unspecified

Protocol cause
Transfer Syntax Error

Abstract Syntax Error (Reject)

Abstract Syntax Error (Ignore And Notify)

Message Not Compatible With Receiver State


Semantic Error

Abstract Syntax Error (Falsely Constructed Message)

Unspecified

Miscellaneous cause
Control Processing Overload
Not Enough User Plane Processing Resources Available
Hardware Failure
O&M Intervention

Unspecified Failure

Unknown PLMN
adio Network Layer cause
The action is due to a S1 intra system handover that has been triggered.
The action is due to a S1 inter system handover that has been triggered.
The action is due to a X2 handover that has been triggered.
The release is requested due to redirection towards a 1xRTT system.
The E-RAB setup failed because the requested QCI is not supported.

Meaning
The required transport resources are not available
Sent when none of the above cause values applies but still the cause is Transport Network
Layer related

Meaning
The release is normal
The action is due to authentication failure.
The action is due to detach.

Sent when none of the above cause values applies but still the cause is NAS related

Meaning
The received message included a transfer syntax error.
The received message included an abstract syntax error and the concerning criticality
indicated "reject".
The received message included an abstract syntax error and the concerning criticality
indicated "ignore and notify".

The received message was not compatible with the receiver state.
The received message included a semantic error.
The received message contained IEs or IE groups in wrong order or with too many
occurrences.

Sent when none of the above cause values applies but still the cause is Protocol related

Meaning
Control processing overload
No enough resources are available related to user plane processing.
Action related to hardware failure
The action is due to O&M intervention.

Sent when none of the above cause values applies and the cause is not related to any of the
categories Radio Network Layer, Transport Network Layer, NAS or Protocol.

The MME doesn’t identify any of the PLMN provided by the eNB
Meaning
Sent for radio network layer cause when none of the specified cause values applies
The timer guarding the handover that takes place over X2 has abnormally expired.
Successful handover.
Release is initiated due to E-UTRAN generated reason.
The reason for the action is cancellation of Handover
Provides a reason for the handover cancellation. The HANDOVER COMMAND message
from MME contained E-RABs to Release List IE and the source eNB estimated service
continuity for the UE would be better by not proceeding with handover towards this particular
target eNB.
The handover failed due to a failure in target EPC/eNB or target system.
Handover to the indicated target cell is not allowed for the UE in question.
The reason for the action is expiry of timer TS1RELOCoverall.
Handover Preparation procedure is cancelled when timer TS1RELOCprep expires.
The concerned cell is not available.
Handover rejected because the target ID is not known to the EPC.
Load on target cell is too high.

The action failed because the MME UE S1AP ID is either unknown, or (for a first message
received at the eNB) is known and already allocated to an existing context.

The action failed because the eNB UE S1AP ID is either unknown, or (for a first message
received at the MME) is known and already allocated to an existing context.

The action failed because both UE S1AP IDs are unknown, or are known but do not define a
single UE context.
The reason for requesting handover is radio related.

handover is requested for time critical reason i.e. this cause value is reserved to represent all
critical cases where the connection is likely to be dropped if handover is not performed.

The reason for requesting handover is to improve the load distribution with the neighbour
cells.
Load on serving cell needs to be reduced.
The action is requested due to user inactivity on all E-RABs e.g. S1 is requested to be
released in order to optimise the radio resources.
The action is requested due to loosing the radio connection to the UE.
The action is requested for all load balancing and offload cases in the MME.
The action is due to a CS fallback that has been triggered
The action is requested due to a Cell Change Order that has been triggered
No requested radio resources are available
The action was failed because of invalid QoS combination.
The release is requested due to inter-RAT redirection.
Radio interface procedure has failed
The action is due to an ongoing interaction with another procedure
The action failed because the E-RAB ID is unknown in the eNB
The action failed because multiple instance of the same E-RAB had been provided to the
eNB
The eNB is unable to support any of the encryption and/or integrity protection algorithms
supported by the UE.

You might also like