Automatic RRC State Transitions

Last updated: October 30, 2013

This section is only applicable to the lab application.

The automatic RRC state transitions are driven by a set of triggers as below:

2. Inactivity timer based. These triggers fire after a certain amount of time has elapsed since the network received or transmitted to/from the UE. You can set the amount of time as in RRC State Trans Setup .
3. UE reported measurement report. This trigger fires when a measurement report indicating a particular event-based measurement has occurred in the UE.
   • E4A fires when the network receives a Measurement Report indicating that Event 4A ("Transport Channel Traffic Volume becomes larger than an absolute threshold") has occurred in the UE. When the network receives the E4A Measurement Report, the UE will be transit to CELL_DCH if it is in CELL_FACH'
   • E4B trigger fires when the network receives a Measurement Report indicating that Event 4B ("Transport Channel Traffic Volume becomes larger than an absolute threshold") has occurred in the UE. When the network receives the E4B Measurement Report, the UE will be transit to CELL_FACH if it is in CELL_DCH.
4. Network buffer threshold. This trigger fires when an RLC buffer in the test set associated with a traffic plane radio bearer is above or below a threshold for a period of time. You can set the threshold and period of time as in RRC State Trans Setup .
5. Downlink IP data arrival.

   The downlink data trigger fires when an IP packet arrives at the 8960 for the UE and it is in CELL_PCH, URA_PCH or Idle if both the top levelAutomatic RRC State Transitions setting is On and the Automatic Transition Upon Downlink IP Data setting is On .When this trigger fires the UE will be transit to CELL_FACH if it is in CELL_PCH or URA_PCH or the RRC state indicated in the Initial PS Data RRC State setting if it is in Idle.

6. UE-reported Signalling Connection Release Indication (SCRI).

   This trigger fires when an SCRI is received and allows transition from CELL_DCH, CELL_FACH, CELL_PCH or URA_PCH to an efficient battery consumption RRC state IDLE, CELL_PCH, URA_PCH, or CELL_FACH State, or drops the PDP context directly.

   • RRC Idle with SCRI

     If UE is on a PDP Context in CELL_DCH or CELL_FACH and an SCRI with "psdomain" identity is received from the UE, and if SCRI With Fast Dormancy State is set to Off , you have two choices: 1), If you want to maintain the active PDP Context when the SCRI is received and only drop the RRC Connection (RRC Idle With SCRI is set to On ), then the test set will initiate the RRC Connection Release procedure and the UE will be transit to RRC Idle; 2), If you want to drop the active PDP Context when the SCRI is received (RRC Idle With SCRI is set to Off ), then the test set will transit the UE to Idle.

   • SCRI with Fast Dormancy

     If UE is on a PDP Context in CELL_DCH or CELL_FACH and an SCRI is received from the UE, if the IE "Signalling Connection Release Indication Cause" indicates "UE requested PS Data session end", you have two choices: 1), if you want to maintain the activate PDP Context and move the UE to an efficient battery consumption RRC State (set the SCRI With Fast Dormancy State to On , then the test set will initiate a state transition to efficient battery consumption RRC State (called Fast Dormancy); 2), if you do not want to initiate the Fast Dormancy procedure when the SCRI is received (SCRI With Fast Dormancy State is set to Off ), then test set will behave the same as in RRC Idle with SCRI .

     If UE is on a PDP Context in CELL_PCH or URA_PCH and an SCRI is received from the UE, if the IE "Signalling Connection Release Indication Cause" indicates "UE requested PS Data session end", and if SCRI With Fast Dormancy State is set to On , the UE will be put back to CELL_PCH or URA_PCH state.