Académique Documents
Professionnel Documents
Culture Documents
When the RNC decides to reject the RRC connection request because the handover control entity
reports a failure. After this, the RNC sends an RRC: RRC CONNECTION REJECT message to the UE.
This counter is updated also in case of incoming SRNS relocations, inter-system handovers, and inter-
RNC hard handovers
When the RNC decides to reject the RRC connection request because the admission control entity
reports a failure (excluding frozen BTS reason).
After this, the RNC sends an RRC: RRC CONNECTION REJECT message to the UE. This counter is updated
also in case of incoming SRNS relocations, inter-system handovers, and inter-RNC hard handovers
When the RNC decides to reject the RRC connection request due to unsuccessful radio link setup. After
this, the RNC sends an RRC: RRC CONNECTION REJECT message to the UE.
This counter is updated also in case of incoming SRNS relocations, inter-system handovers, and inter-
RNC hard handovers
When the RNC decides to reject the RRC connection request due to transport failure. After this, the
RNC sends an RRC: RRC CONNECTION REJECT message to the UE.
This counter is updated also in case of incoming SRNS relocations, inter-system handovers, and inter-
RNC hard handovers
When the RNC decides to reject the RRC connection request due to RNC internal failure. After this, the
RNC sends an RRC: RRC CONNECTION REJECT message to the UE
This counter is updated also in case of incoming SRNS relocations, inter-system handovers, and inter-
RNC hard handovers
When the RNC decides to reject the RRC connection request, because the admission control entity
blocks the radio link establishment, to ensure the setup of high priority calls. After this, the RNC sends
an RRC: RRC CONNECTION REJECT message to the UE.
This counter is updated also in case of incoming SRNS relocations, inter-system handovers, and inter-
RNC hard handovers
When the RNC decides to reject the RRC connection request due to RNTI allocation failure caused by
RRMU overload. After this, the RNC sends an RRC: RRC CONNECTION REJECT message to the UE
When the RNC decides to reject the RRC connection request due to Iub transport resource shortage
between RNC and WBTS. After this the RNC sends an RRC: RRC CONNECTION REJECT message to the UE
This counter is updated also in case of inter-system handovers, and inter-RNC hard handover
When the RNC redirects an emergency call to the GSM network by sending an RRC CONNECTION REJECT
with redirection information to the UE
RRC CONN SETUP FAIL DUE TO ICSU OVERLOAD
When the RNC decides to reject the RRC connection request due to ICSU overload. After this, the RNC
sends an RRC: RRC CONNECTION REJECT message to the UE.
When the RNC does not receive the RRC: RRC CONNECTION SETUP COMPLETE message from the UE
within 6 seconds, and the RNC has not received the NBAP message which indicates that L1
synchronisation has been established between UE and BTS. This counter is updated also in case of
inter-system handovers and inter-RNC hard handovers
When the RNC does not receive the RRC: RRC CONNECTION SETUP COMPLETE message from the UE
within 6 seconds, and the RNC has received the NBAP message which indicates that L1 synchronisation
has been established between UE and BTS. This counter is updated also in case of incoming SRNS
relocations, inter-system handovers, and inter-RNC hard handovers
When an RNC internal failure occurs before receiving the RRC: RRC CONNECTION SETUP COMPLETE
message from the UE. This counter is updated also in case of incoming SRNS relocations, inter-system
handovers, and inter-RNC hard handovers
When an Iu interface failure occurs, and the failure causes the release of the RRC connection. After
this, the RNC sends an RANAP: IU RELEASE REQUEST to all involved CNs
When a radio interface failure occurs, and the failure causes the release of the RRC connection. After
this, the RNC sends an RANAP: IU RELEASE REQUEST to all involved CNs.
When a BTS failure occurs, and the failure causes the release of the RRC connection. After this, the
RNC sends an RANAP: IU RELEASE REQUEST to all involved CNs
When a procedure failure in drift RNC occurs, and the failure causes the release of the RRC connection.
After this, the RNC sends an RANAP: IU RELEASE REQUEST to all involved CNs
When the RNC releases the RRC connection after receiving RANAP: IU RELEASE COMMAND with cause
"Requested Ciphering and/or Integrity Protection Algorithms not Supported" from the core network.
When an RNC internal failure occurs, and the failure causes the release of the RRC connection. After
this, the RNC sends an RANAP: IU RELEASE REQUEST to all involved CNs. The possible failure reasons
updating this counter are for example RNC internal failure, transmission failure or loss of Frame
Protocol synchronization.
RRC ACTIVE FAIL DUE TO UE
When the RRC connection is released due to the UE not responding to an RRC message or responding
with such failure message that the connection must be released. After this, the RNC sends a RANAP: IU
RELEASE REQUEST to all involved CNs
When a standalone SRB is released due to some failure, i.e. when it is counted as RRC Active Failure in
the old Service Level counters. The counter is updated when the establishment cause in RRC: RRC
CONNECTION REQUEST is either Originating Conversational Call or Terminating Conversational Call.
When a standalone SRB is released due to some failure, i.e. when it is counted as RRC Active Failure in
the old Service Level counters. The counter is updated when the establishment cause in RRC: RRC
CONNECTION REQUEST is either Originating Streaming Call or Terminating Streaming Call.
When a standalone SRB is released due to some failure, i.e. when it is counted as RRC Active Failure in
the old Service Level counters. The counter is updated when the establishment cause in RRC: RRC
CONNECTION REQUEST is either Originating Interactive Call or Terminating Interactive Call.
When a standalone SRB is released due to some failure, i.e. when it is counted as RRC Active Failure in
the old Service Level counters. The counter is updated when the establishment cause in RRC: RRC
CONNECTION REQUEST is either Originating Background Call or Terminating Background Call.
SRB ACTIVE FAILURE OTHER
When a standalone SRB is released due to some failure, i.e. when it is counted as RRC Active Failure in
the old Service Level counters. The counter is updated when the establishment cause in RRC: RRC
CONNECTION REQUEST is some other cause not covered by counters M1001C635-M1001C638.