UE Timers & Constants In RRC Ideal Mode & Connected Mode

UE Timer and Constant:

The following settings can only be changed when call status is Idle .

T300 RRC Conn Req Retransmit Timer

This setting determines how long the UE waits for the RRC Connection Setup after sending an RRC Connection Setup Request. T300 can be set to one of the following values: 400, 600, 800, 1000, 1200, 1400, 1600, 1800, 2000, 3000, 4000, 6000, 8000 ms.

N300 RRC Conn Req Max Retransmits

This setting specifies the maximum number of retransmissions of the RRC Connection Request message. N300 can be set to any integer value from 0 to 7.

T312 Link Establishment Timer (Idle)

This setting determines how long the UE waits for an N312 "in-sync" indication from layer 1 when establishing a dedicated channel and the connection status is Idle. T312 can be set to any integer value from 1 to 15.

T312 Link Establishment Timer (Connected)

This setting determines how long the UE waits for an N312 "in-sync" indication from layer 1 when establishing a dedicated channel in connected status. The value 0 is not used.

N312 Link Establishment In-Sync Count (Idle)

This setting specifies the number of " in-syncs" required when establishing a dedicated channel when the connection status is Idle. N312 can be set to one of the following values: 1, 2, 4, 10, 20, 50, 100, 200, 400, 600, 800, 1000.

N312 Link Establishment In-Sync Count (Conn.)

This setting specifies the number of " in-syncs" required when establishing a dedicated channel in connected status. N312 can be set to one of the following values: 1, 2, 4, 10, 20, 50, 100, 200, 400, 600, 800, 1000.

T313 Out-of-Sync Reception Timer

3GPP TS 25.331 8.5.6 states that after receiving N313 consecutive "out of sync" indications from layer, the UE shall start the T313 timer. Upon receiving N315 successive "in sync"

indications from layer 1, the UE shall stop and reset the T313 timer. If T313 expires, a "Radio Link failure" has occurred, and the UE shall drop the call.

N313 Successive Out-Of-Sync Reception Max

N313 specifies the maximum number of successive "out of sync" received from L1. N313 can be set to one of the following integer values: 1, 2, 4, 10, 20, 50, 100, 200.

N315 Successive In-Sync Reception Counter

N315 specifies the maximum number of successive "in sync" received from L1 during T313 is activated. N315 can be set to one of the following integer values: 1, 2, 4, 10, 20, 50, 100, 200, 400, 600, 800, 1000.

T308 RRC Conn Release Comp Retransmit Timer

T308 specifies the time between the transmissions of RRC Connection Release Complete message.

N308 RRC Conn Release Comp Max Retransmits

N308 specifies the maximum number of retransmissions of the RRC CONNECTION RELEASE COMPLETE message.

T3212 Periodic Location Update Timer

T3212 specifies how often the UE will perform the periodic location update procedure. It is signaled in SIB1. When T3212 is set to zero, the UE will regard the timer to be infinite.

Show

UE Timer and Constant Parms

Last updated: January 14, 2013

Description
The following settings can only be changed when call status is Idle . If BCCH Update Page is set to Auto and you change these settings while your UE is camped to the test set, the test set performs a Broadcast Channel (BCCH) Update Procedure (SIB Contents). If BCCH Update Page is set to Inhibit (the default value) and you change these settings while your UE is camped to the test set, you must force your UE to re-read the BCCH to observe the change.

T300 RRC Conn Req Retransmit Timer

This setting determines how long the UE waits for the RRC Connection Setup after sending an RRC Connection Setup Request. T300 can be set to one of the following values: 400, 600, 800, 1000, 1200, 1400, 1600, 1800, 2000, 3000, 4000, 6000, 8000 ms. GPIB Command: CALL[:CELL]:BCCHannel:T300

N300 RRC Conn Req Max Retransmits This setting specifies the maximum number of retransmissions of the RRC Connection Request message. N300 can be set to any integer value from 0 to 7. GPIB Command: CALL[:CELL]:BCCHannel:N300

T312 Link Establishment Timer (Idle) This setting determines how long the UE waits for an N312 "in-sync" indication from layer 1 when establishing a dedicated channel and the connection status is Idle. According to 3GPP TS 25.331 table 10.3.3.44, The value 0 is not used. T312 can be set to any integer value from 1 to 15. GPIB Command: CALL[:CELL]:BCCHannel:T312[:IDLE]

T312 Link Establishment Timer (Connected)

This setting determines how long the UE waits for an N312 "in-sync" indication from layer 1 when establishing a dedicated channel in connected status. According to 3GPP TS 25.331 table 10.3.3.43, The value 0 is not used. GPIB Command: CALL[:CELL]:BCCHannel:T312:CONNected

N312 Link Establishment In-Sync Count (Idle) This setting specifies the number of " in-syncs" required when establishing a dedicated channel when the connection status is Idle. N312 can be set to one of the following values: 1, 2, 4, 10, 20, 50, 100, 200, 400, 600, 800, 1000. GPIB Command: CALL[:CELL]:BCCHannel:N312[:IDLE]

N312 Link Establishment In-Sync Count (Conn.)

This setting specifies the number of " in-syncs" required when establishing a dedicated channel in connected status. N312 can be set to one of the following values: 1, 2, 4, 10, 20, 50, 100, 200, 400, 600, 800, 1000. GPIB Command: CALL[:CELL]:BCCHannel:N312:CONNected

T313 Out-of-Sync Reception Timer 3GPP TS 25.331 8.5.6 states that after receiving N313 consecutive "out of sync" indications from layer 1 (see N313 Successive Out-Of-Sync Reception Max ), the UE shall start the T313 timer. Upon receiving N315 successive "in sync" indications from layer 1 ( N315 Successive In-Sync Reception Counter ), the UE shall stop and reset the T313 timer. If T313 expires, a "Radio Link failure" has occurred, and the UE shall drop the call. GPIB Command: CALL[:CELL]:BCCHannel:T313

N313 Successive Out-Of-Sync Reception Max N313 specifies the maximum number of successive "out of sync" received from L1. N313 can be set to one of the following integer values: 1, 2, 4, 10, 20, 50, 100, 200. GPIB Command: CALL[:CELL]:BCCHannel:N313

N315 Successive In-Sync Reception Counter N315 specifies the maximum number of successive "in sync" received from L1 during T313 is activated.

N315 can be set to one of the following integer values: 1, 2, 4, 10, 20, 50, 100, 200, 400, 600, 800, 1000. GPIB Command: CALL[:CELL]:BCCHannel:N315

T308 RRC Conn Release Comp Retransmit Timer

T308 specifies the time between the transmissions of RRC Connection Release Complete message. GPIB Command: CALL[:CELL]:BCCHannel:T308

N308 RRC Conn Release Comp Max Retransmits

N308 specifies the maximum number of retransmissions of the RRC CONNECTION RELEASE COMPLETE message. GPIB Command: CALL[:CELL]:RRC:CRELease:N308

T3212 Periodic Location Update Timer

T3212 specifies how often the UE will perform the periodic location update procedure. It is signaled in SIB1. When T3212 is set to zero, the UE will regard the timer to be infinite. GPIB Command: CALL[:CELL]:BCCHannel:T3212

ahmi 2012-06-27, 04:29 AM Hello experts, I have read that both T312 and N312 were broadcast to the UE in SIB 1 and that the T312 was started when UE initiated the establishment of the DPCH i.e. when the RRC Connection Request message was sent. Here I have some confusion, when the UE get the T312 value from the RNC (consedering that the RRC Connection Request is the first message between the UE and the RNC) ? Could you please explain to me the chronological steps and the relation between T312 and N312. BR, Fahmi. tukangoptim 2012-06-28, 06:04 PM hi Fahmi, pls see attached, hope it helps usama0795 2012-06-29, 08:39 PM There are actually 2 types of T312 and N312 (N312 / N312 for connected mode / T312 / T312 for connected mode. N312: This parameter defines the maximum number of "in sync" indications received from L1 during the establishment of a physical channel (UE counter used in idle mode). When a physical dedicated channel establishment is initiated by the UE, the UE starts a timer T312 and wait for layer 1 to indicate N312 "in sync" indications. On receiving N312 "in sync" indications, the physical channel is considered established and the timer T312 is stopped and reset. If the timer T312 expires before the physical channel is established, the UE considers this as a "physical channel failure". N312 for connected mode: This parameter defines the maximum number of "in sync" indications received from L1 during the establishment of a physical channel (UE counter used in connected mode). When a physical dedicated channel establishment is initiated by the UE, the UE shall start a timer T312 and wait for layer 1 to indicate N312 "in sync" indications. On receiving N312 "in sync" indications, the physical channel is considered established and the timer T312 is stopped and reset. If the timer T312 expires before the physical channel is established, the UE considers this as a "physical channel failure". T312:The parameter defines the timer for supervising successful establishment of a physical channel (UE timer used in idle mode). When a physical dedicated channel establishment is initiated by the UE, the UE should start a timer T312 and wait for layer 1 to indicate N312 "in sync" indications. On receiving N312 "in sync" indications, the physical channel is considered as established and the timer T312 is stopped and reset. If the timer T312 expires before the physical channel is established, the UE should consider this as a "physical channel failure". T312 for connected mode: The parameter defines the timer for supervising successful establishment of a physical channel (this UE timer is used in connected mode). When a physical dedicated channel establishment is initiated by the UE, the UE should start a timer T312 and wait for layer 1 to indicate N312 "in sync" indications. On receiving N312 "in sync" indications, the physical channel is considered as established and the timer T312 is stopped and reset. If the timer T312 expires before the physical channel is established, the UE should consider this as a "physical channel failure".

nupong 2012-06-29, 09:21 PM As I understood, even UE in idle mode (no need RRC Connection Request), UE could listen SIB from network fahmi 2012-06-30, 03:39 AM Yes, In fact SIB1 is broadcasted on BCH. So that even in idle, the UE gets the T312 and N312 values from the RNC and use them.

THURSDAY, 12 JANUARY 2012

UE Timers & Constants In RRC Ideal Mode & Connected Mode

UE Timer and Constant:

The following settings can only be changed when call status is Idle .

T300 RRC Conn Req Retransmit Timer

This setting determines how long the UE waits for the RRC Connection Setup after sending an RRC Connection Setup Request. T300 can be set to one of the following values: 400, 600, 800, 1000, 1200, 1400, 1600, 1800, 2000, 3000, 4000, 6000, 8000 ms.

N300 RRC Conn Req Max Retransmits

This setting specifies the maximum number of retransmissions of the RRC Connection Request message. N300 can be set to any integer value from 0 to 7.

T312 Link Establishment Timer (Idle)

This setting determines how long the UE waits for an N312 "in-sync" indication from layer 1 when establishing a dedicated channel and the connection status is Idle. T312 can be set to any integer value from 1 to 15. T312 Link Establishment Timer (Connected) This setting determines how long the UE waits for an N312 "in-sync" indication from layer 1 when establishing a dedicated channel in connected status. The value 0 is not used. N312 Link Establishment In-Sync Count (Idle) This setting specifies the number of " in-syncs" required when establishing a dedicated channel when the connection status is Idle. N312 can be set to one of the following values: 1, 2, 4, 10, 20, 50, 100, 200, 400, 600, 800, 1000.

N312 Link Establishment In-Sync Count (Conn.)

This setting specifies the number of " in-syncs" required when establishing a dedicated channel in connected status. N312 can be set to one of the following values: 1, 2, 4, 10, 20, 50, 100, 200, 400, 600, 800, 1000.

T313 Out-of-Sync Reception Timer

3GPP TS 25.331 8.5.6 states that after receiving N313 consecutive "out of sync" indications from layer, the UE shall start the T313 timer. Upon receiving N315 successive "in sync" indications from layer 1, the UE shall stop and reset the T313 timer. If T313 expires, a "Radio Link failure" has occurred, and the UE shall drop the call. N313 Successive Out-Of-Sync Reception Max N313 specifies the maximum number of successive "out of sync" received from L1. N313 can be set to one of the following integer values: 1, 2, 4, 10, 20, 50, 100, 200.

N315 Successive In-Sync Reception Counter

N315 specifies the maximum number of successive "in sync" received from L1 during T313 is activated. N315 can be set to one of the following integer values: 1, 2, 4, 10, 20, 50, 100, 200, 400, 600, 800, 1000.

T308 RRC Conn Release Comp Retransmit Timer

T308 specifies the time between the transmissions of RRC Connection Release Complete message. N308 RRC Conn Release Comp Max Retransmits N308 specifies the maximum number of retransmissions of the RRC CONNECTION RELEASE COMPLETE message. T3212 Periodic Location Update Timer T3212 specifies how often the UE will perform the periodic location update procedure. It is signaled in SIB1. When T3212 is set to zero, the UE will regard the timer to be infinite.

Posted by LTE HSPA at 23:36 No comments: Email ThisBlogThis!Share to TwitterShare to Facebook Labels: 3G / WCDMA / UMTS / T300 / N300

Interview Question & Answer For 3G / WCDMA / UMTS UMTS interview questions: 1) What are the RRC states? a. Cell DCH b. Cell FACH c. Cell PCH d. URA PCH 2) Describe different RRC States?

a. Cell DCH: When UE is switched ON, it assumes the CELL_DCH State by default. It exists when UE really requires UL/DL dedicated resource. UE is characterized at cell level according to its current Active set. Logical channels DCCH+DTCH are mapped to transport channel DCH. E.g. Voice call(CS), Video telephony(CS+PS) b. Cell FACH: This happens when, (1) UE doesnt require continuous circuit connection with n/w, but DL packets will work . (2) UE is forced to release the n/w resources to decrease the congestion problems (flipflop between DCH and FACH). (3) Eventual location updates to support CELL_PCH and URA_PCH states (flip-flop between FACH and PCH). E.g. Call on hold(CS), File downloading(PS) No dedicated UL/DL is provided. However, UE will keep monitoring to DL common transport channel FACH continuously and receives packet data meant for UE itself. When UL transmission is required, it uses RACH for 1-2 frames or CPCH for few more frames, depending on common access procedures; still UL transmission will be discontinuous. UE is known on cell level, but this time its based on the last cell update it made. c. Cell PCH: This happens when UE doesnt require an active conn ection(common/dedicated). But still needs to be connected, as its expecting a n/w initiated or terminated call(CS or PS) in future. So, no UL transmission is allowed. Selects a PCH(based on algo.) and keep monitoring (receiving) it in discontinuous mode(DRX). Can commute only into CELL_FACH state. E.g. No outgoing call or data receive for long time UE is still identified on cell level, but now in the cell where UE made its last update, when it was in CELL_FACH state. At regular time interval, UE would have to move in CELL_FACH state to update the location area. If UE is traveling, this update will become frequent because of changing cells.

 In some cases UE can have the transition from CELL_DCH to CELL_PCH, but not vice versa; it has to go via CELL_FACH. d. URA PCH: This can be considered as a general case of CELL_PCH state. Because all the characteristics are same except one. That is, UE is known on URA(UTRAN Registration Area) level rather than cell level. It listens to PCH(and updates URA when required). If UE is traveling continuously from one cell to another. It would have to transit multiple time to CELL_FACH state for location update. By assigning URA_PCH state, this condition is avoided, since 1 URA contains one or more cells and vice versa. 3) In which conditions UE will be in Cell FACH state? This happens when, UE doesnt require continuous circuit connection with n/w, but DL packets will work. UE is forced to release the n/w resources to decrease the congestion problems (flip-flop between DCH and FACH). Eventual location updates to support CELL_PCH and URA_PCH states (flip-flop between FACH and PCH). E.g. Call on hold(CS), File downloading(PS) 4) What is the difference between Cell PCH and URA PCH state? UE is known on URA(UTRAN Registration Area) level rather than cell level If UE is traveling continuously from one cell to another. It would have to transit multiple time to CELL_FACH state for location update. By assigning URA_PCH state, this condition is avoided, since 1 URA contains one or more cells and vice versa 5) What is U-RNTI? URNTI is a 32bit identity. SRNC identifier + SRNTI makes URNTI 6) Describe the CELL search procedure? The Cell Search procedure can be summarised into the following steps: a. Cell Selection: Determine the cell whose received carrier power is the strongest b. Slot Synchronisation: the UE reads the P-SCH of the strongest carrier and feeds the received signal through a matched filter (that is matched to the Primary Synchronisation Code). The slot timing is detected via detection of peaks in the output of the matched filter.

c. Frame Synchronisation and Scrambling Code Group Identification: the UE reads the S-SCH of the strongest carrier, and correlates the received signal with all the possible 64 Secondary Synchronisation Codes. The output that gives maximum correlation gives the group of the Primary Scrambling Code used in the cell. This process also gives the frame timing since the Secondary Synchronisation Code is different for each slot and the group tells the mapping between slots and SSCs. d. Scrambling Code Identification: The UE attempts then to read the P-CPICH so as to extract the Primary Scrambling Code used in the cell. The P-CPICH is always scrambled by the Primary Scrambling Code of the cell and is spread a factor 256 and an OVSF whose index is zero. Since the Primary Scrambling Codes are grouped into 64 groups of 8 Scrambling Codes and the S-SCH has given the Scrambling Code group only 8 possibilities remain. So the P-CPICH is unscrambled separately withevery possible Scrambling Code (8) in the group and only one output will produce correct results and the Primary Scrambling Code of the cell is determined. e. Read Broadcast Information: Since the P-CCPCH is always scrambled by the Primary Scrambling Code of the cell (which has now been determined) and is always spread using SF=256 with OVSF index=1, The UE can read the P-CCPCH without any problem. The PCCPCH carries the BCH where system information blocks are broadcast throughout the entire cell. The UE can acquire at this stage various information (e.g. Spreading Factors, OVSF indexes and Scrambling Codes used in other downlink channels, important parameters for PRACH transmission, Measurement Parameters, Transport Formats etc.) and can then decodeother downlink channels, initiate a PRACH procedure, performs some specific measurements etc. 7) Radio bearer configuration mappings? Signalling radio bearer RB0 shall be used for all messages sent on the CCCH (UL: RLC-TM, DL: RLC-UM). Signalling radio bearer RB1 shall be used for all messages sent on the DCCH, when using RLC unacknowledged mode (RLC-UM). Signalling radio bearer RB2 shall be used for all messages sent on the DCCH, when using RLC acknowledged mode (RLC-AM), except for the RRC messages carrying higher layer (NAS) signalling. Signalling radio bearer RB3 and optionally Signalling radio bearer RB4 shall be used for the RRC messages carrying higher layer (NAS) signalling and sent on the DCCH in RLC acknowledged mode (RLC-AM). Additionally, RBs whose identities shall be set between 5 and 32 may be used as signalling radio bearer for the RRC messages on the DCCH sent in RLC transparent mode (RLC-TM). 8) What are the types of hand over?

Here are following categories of handover (also referred to as handoff): Hard HandoverHard handover means that all the old radio links in the UE are removed before the new radio links are established. Hard handover can be seamless or nonseamless. Seamless hard handover means that the handover is not perceptible to the user. In practice a handover that requires a change of the carrier frequency (inter-frequency handover) is always performed as hard handover. Soft Handover Soft handover means that the radio links are added and removed in a way that the UE always keeps at least one radio link to the UTRAN. Soft handover is performed by means of macro diversity, which refers to the condition that several radio links are active at the same time. Normally soft handover can be used when cells operated on the same frequency are changed. Softer handoverSofter handover is a special case of soft handover where the radio links that are added and removed belong to the same Node B (i.e. the site of co-located base stations from which several sector-cells are served. In softer handover, macro diversity with maximum ratio combining can be performed in the Node B, whereas generally in soft handover on the downlink, macro diversity with selection combining is applied. Generally we can distinguish between intra-cell handover and inter-cell handover. For UMTS the following types of handover are specified: Handover 3G -3G (i.e. between UMTS and other 3G systems) FDD soft/softer handover FDD inter-frequency hard handover FDD/TDD handover (change of cell) TDD/FDD handover (change of cell) TDD/TDD handover Handover 3G - 2G (e.g. handover to GSM) Handover 2G - 3G (e.g. handover from GSM) The most obvious cause for performing a handover is that due to its movement a user can be served in another cell more efficiently (like less power emission, less interference). It may however also be performed for other reasons such as system load control. 9) What are types of measurements? Intra-frequency measurements: measurements on downlink physical channels at the same frequency as the active set. A measurement object corresponds to one cell.

 Inter-frequency measurements: measurements on downlink physical channels at frequencies that differ from the frequency of the active set and on downlink physical channels in the active set. A measurement object corresponds to one cell. Inter-RAT measurements: measurements on downlink physical channels belonging to another radio access technology than UTRAN, e.g. GSM. A measurement object corresponds to one cell. Traffic volume measurements: measurements on uplink traffic volume. A measurement object corresponds to one cell. Quality measurements: Measurements of downlink quality parameters, e.g. downlink transport block error rate. A measurement object corresponds to one transport channel in case of BLER. A measurement object corresponds to one timeslot in case of SIR (TDD only). UE-internal measurements: Measurements of UE transmission power and UE received signal level. UE positioning measurements: Measurements of UE position. 10) What is paging? Why paging is required? Paging: This procedure is used to transmit paging information to selected UEs in idle mode, CELL_PCH or URA_PCH state using the paging control channel (PCCH). Paging can be initiated : Upper layers in the network may request paging, to e.g. establish a signaling connection. UTRAN may initiate paging for UEs in CELL_PCH or URA_PCH state to trigger a cell update procedure. UTRAN may initiate paging for UEs in idle mode, CELL_PCH and URA_PCH state to trigger reading of updated system information. UTRAN may also initiate paging for UEs in CELL_PCH and URA_PCH state to release the RRC connection. 11) Type of Paging? Paging Type 1 Paging Type 2(UE dedicated paging) 12) When dedicated paging is used? a. This procedure is used to transmit dedicated paging information to one UE in connected mode in CELL_DCH , CELL_FACH or CELL_PCH (FDD only) state. Upper layers in the network may request initiation of paging.

b. For a UE in CELL_DCH, CELL_FACH or CELL_PCH (FDD only) state, UTRAN initiates the procedure by transmitting a PAGING TYPE 2 message on the DCCH using AM RLC. When not stated otherwise elsewhere, the UTRAN may initiate the UE dedicated paging procedure also when another RRC procedure is ongoing, and in that case the state of the latter procedure shall not be affected. c. UTRAN should set the IE "Paging cause" to the cause for paging received from upper layers. If no cause for paging is received from upper layers, UTRAN should set the value "Terminating cause unknown". 13) In what situation UE goes to CELL PCH and URA PCH states? a. Cell PCH: This happens when UE doesnt require an active Connection(common/dedicated). But still needs to be connected, as its expecting a n/w initiated or terminated call(CS or PS) in future b. URA PCH: In Cell PCH UE is still identified on cell level, but now in the cell where UE made its last update, when it was in CELL_FACH state.At regular time interval, UE would have to move in CELL_FACH state to update the location area. If UE is traveling, this update will become frequent because of changing cells. If UE is traveling continuously from one cell to another. It would have to transit multiple time to CELL_FACH state for location update. By assigning URA_PCH state, this condition is avoided, since 1 URA contains one or more cells and vice versa 14) What is Cell Update Procedure? What are various Cell Update causes?
Uplink data transmission: For FDD, if the variable H_RNTI is not set, and for TDD:

if the UE is in URA_PCH or CELL_PCH state; and if the UE has uplink RLC data PDU or uplink RLC control PDU on RB1 or upwards to transmit:
perform cell update using the cause "uplink data transmission". Paging response: if the criteria for performing cell update with the cause specified above. are not met; and if the UE in URA_PCH or CELL_PCH state, receives a PAGING TYPE 1 .message fulfilling the conditions for initiating a cell update procedure.

perform cell update using the cause "paging response".

Radio link failure:

if none of the criteria for performing cell update with the causes specified above in the current subclause is met:

if the UE is in CELL_DCH state and the criteria for radio link failure are ,or if the transmission of the UE CAPABILITY INFORMATION message fails.
perform cell update using the cause "radio link failure". MBMS ptp RB request: if none of the criteria for performing cell update with the causes specified above in the current subclause is met; and if the UE is in URA_PCH, Cell_PCH or Cell_FACH state; and if the UE should perform cell update for MBMS ptp radio bearer request, perform cell update using the cause "MBMS ptp RB request". Re-entering service area: if none of the criteria for performing cell update with the causes specified above in the current subclause is met; and if the UE is in CELL_FACH or CELL_PCH state; and 2> if the UE has been out of service area and re-enters service area before T307 or T317 expires:

3> perform cell update using the cause "re-entering service area".
RLC unrecoverable error: if none of the criteria for performing cell update with the causes specified above in the current subclause is met; and if the UE detects RLC unrecoverable error [16] in an AM RLC entity:

perform cell update using the cause "RLC unrecoverable error".

Cell reselection: if none of the criteria for performing cell update with the causes specified above in the current subclause is met:

if the UE is in CELL_FACH or CELL_PCH state and the UE performs cell re-selection; or if the UE is in CELL_FACH state and the variable C_RNTI is empty:
perform cell update using the cause "cell reselection". Periodical cell update: if none of the criteria for performing cell update with the causes specified above in the current subclause is met; and if the UE is in CELL_FACH or CELL_PCH state; and

if the timer T305 expires; and if the criteria for "in service area" and if periodic updating has been configured by T305 in the IE "UE Timers and constants in connected mode" set to any other value than "infinity":

perform cell update using the cause "periodical cell update".

MBMS reception: if none of the criteria for performing cell update with the causes specified above in the current subclause is met; and if the UE is in URA_PCH, Cell_PCH or Cell_FACH state; and if the UE should perform cell update for MBMS counting , perform cell update using the cause "MBMS reception".

15) What is Active set? Active Set is defined as the set of Node-Bs the UE is simultaneously connected to (i.e., the UTRA cells currently assigning a downlink DPCH to the UE constitute the active set). 16) What is Monitor set and detected set Cells? a. Cells, which are not included in the active set, but are included in the CELL_INFO_LIST belong to the Monitored Set. b. Cells detected by the UE, which are neither in the CELL_INFO_LIST nor in the active set belong to the Detected Set. Reporting of measurements of the detected set is only applicable to intra-frequency measurements made by UEs in CELL_DCH state. 17) What are the various types of RNC? a. Serving RNC b. Drift RNC c. Controlling RNC 18) What is the use and difference between CRNC, Drift RNC and SRNC? RNC from which the UE is currently getting Served or connected to is called SRNC or Serving RNC. During a soft handover procedure the RNC UE is moving to, is called Drift RNC. The RNC which controls the movement of UE from Serving RNC to the Drift RNC is called Controlling RNC. 19) What is initial direct transfer message? What is the use?

The initial direct transfer procedure is used in the uplink to establish a signaling connection. It is also used to carry an initial upper layer (NAS) message over the radio interface. 20) What is security mode command? Why it is used? Security mode command is a RRC Message, The purpose of this procedure : To trigger the start of ciphering or to command the restart of the ciphering with a new ciphering configuration, for the radio bearers of one CN domain and for all signalling radio bearers. It is also used to start integrity protection or to modify the integrity protection configuration for all signalling radio bearers 21) What is CCTrCH? A Coded Composite Transport Channel is the result of combining (multiplexing) several Transport Channels of the same type; i.e.: we can have a CCTrCh made up of one or several DCHs, a CCTrCh made up of DSCHs. One exception is that we can have one or several FACHs multiplexed with a PCH on the same CCTrCh. A better notation would be for example: CCTrCh4DCH: A CCTrCh consisting of 4 DCHs CCTrCh3FACH: A CCTrCh consisting of 3 FACHs CCTrChPCH,2FACH: A CCTrCh consisting of the PCH and 2 FACHs 22) What is compressed mode? Higher layers can request a UE to monitor cells on other frequencies (FDD, TDD), or other systems (GSM). This implies that the UE has to perform measurements, on the other frequencies/systems and thus higher layers command the UE to enter Compressed Mode. The UTRAN need to send to the UE all the parameters for the Compressed Mode. Compression Methods: When in Compressed Mode the information normally transmitted during a 10 ms frame is compressed in time sothat gaps of adequate length are created. To achieve this one of three mechanisms Puncturing
This method is NOT applicable to downlink.

Spread Factor Reduction Actually halving the Spread Factor. So with this method if SF is used in non-compressed frames then SF/2 is used in the compressed frames.

 Higher Layer Scheduling

Higher Layers set restrictions so that only a subset of allowed TFCs are used in Compressed Mode.

Compressed Mode Parameter: TGSN (Transmission Gap Starting Slot Number): A transmission gap pattern begins in a radio frame, called firstradio frame of the transmission gap pattern, containing at least one transmission gap slot. TGSN is the slot numberof the first transmission gap slot within the first radio frame of the transmission gap pattern; TGL1 (Transmission Gap Length 1): Duration of the first transmission gap within the transmission gap pattern, expressed in number of slots; TGL2 (Transmission Gap Length 2): Duration of the second transmission gap within the transmission gap pattern, expressed in number of slots. If this parameter is not explicitly set by higher layers, then TGL2 =TGL1; TGD (Transmission Gap Start Distance): Duration between the starting slots of two consecutive transmission gaps within a transmission gap pattern, expressed in number of slots. The resulting position of the second transmission gap within its radio frame(s) shall comply with the limitations of TS 25.101 (Ref [2]). If this parameter is not set by higher layers, then there is only one transmission gap in the transmission gap pattern; TGPL1 (Transmission Gap Pattern Length): Duration of transmission gap pattern 1; TGPL2 (Transmission Gap Pattern Length): Duration of transmission gap pattern 2. If this parameter is not explicitly set by higher layers, then TGPL2 = TGPL1. The following two parameters (integers) control the transmission gap pattern sequence start and repetition: TGPRC (Transmission Gap Pattern Repetition Count): Number of transmission gap patterns within the transmission gap pattern sequence; From Figure 10 it seems TGPRC is even, therefore the number of slots in TG Sequence is: 0.5*TGPRC (TGPL1+TGPL2) TGCFN (Transmission Gap Connection Frame Number): CFN of the first radio frame of the first pattern 1 within the transmission gap pattern sequence. 23) What is FACH measurement occasion? GAPs in S-CCPCH to perform measurement on Different Frequencies or Interrat resection. 24) MIB/SB/SIB details? MIB: The Scheduling of MIB is Static. 25) Why we perform Channelisation or spreading before scrambling? Before sending a data we need to identify the channel to send the data. A particular Channelisation code is the identity for the channel.

Hence we use Channelisation code to select the channel and then scramble it so as to send the identity of the UE over the channel 26) When TMSI , P- TMSI , IMSI , IMEI used? TMSI (GSM-MAP): The TMSI (GSM-MAP) shall be chosen if available. The IE "LAI" in the IE "Initial UE identity" shall also be present when TMSI (GSM-MAP) is used, for making it unique. P-TMSI (GSM-MAP): The P-TMSI (GSM-MAP) shall be chosen if available and no TMSI (GSMMAP) is available. The IE "RAI" in the IE "Initial UE identity" shall in this case also be present when P-TMSI (GSM-MAP) is used, for making it unique. IMSI (GSM-MAP): The IMSI (GSM-MAP) shall be chosen if available and no TMSI (GSM-MAP) or P-TMSI is available. IMEI: The IMEI shall be chosen when none of the above three conditions are fulfilled. 27) What is Auto attached?

Auto Attach When Power On

Enabled

Disabled

If MNO I It will perform a combined Attach If NMOII It will do a LAU and Attach.

If UE is Location updated i.e. SIM LAI is same as Cell LAI Then it will do nothing. If UE is not Location updated i.e. SIM LAI differs from the Cell LAI then UE will perform Location Area Update Will do a PS attach then the PS call.

PS Call

Same RRC connection can be used for the PS call.

28) Why we do a Combined Attach? If the network operates in Network Mode Of Operation I i.e. NMO I and GPRS MS that operates in Mode A or Mode B will do a simultaneous IMSI attach for GPRS and non GPRS services and shall use the Combined GPRS attach, combined and periodic routing area updating procedures instead of the corresponding MM specific procedures IMSI attach and normal and periodic Location area updating. 29) When UE triggers Event 3A Measurement Report?

Event 3A:The Estimated Quality of currently used UTRAN frequency is below a certain threshold and the estimated quality of the other system is above a certain threshold. 30) How many transport channels will be configured when a CSV and a PSD call is simultaneously going on? Five transport channels will be configured. 1 for 4 SRBs 3 for CSV 1 for PSD 31) When event 2A, 2B, 2C,2E occurs? Event 2a: Change of best frequency Event 2b: The estimated quality of the currently used frequency is below a certain threshold and the estimated quailty of a non-used frequency is above a certain threshold. Event 2c: The estimated quality of a non-used frequency is above a certain threshold Event 2d: The estimated quality of the currently used frequency is below a certain threshold Event 2e: The estimated quality of a non-used frequency is below a certain threshold 32) When event 1A 1F Event occurs? event 1A: A Primary CPICH enters the reporting range event 1B: A primary CPICH leaves the reporting range event 1C: A non-active primary CPICH becomes better than an active primary CPICH event 1D: Change of best cell event 1E: A Primary CPICH becomes better than an absolute threshold event 1F: A Primary CPICH becomes worse than an absolute threshold 33) Where CK and IK gets generated? In RRC CK and IK gets generated. 34) Where CK and IK gets stored? In USIM CK and IK will get stored. 35) Where the Security procedure will start?

Security Procedure will start in RRC but Ciphering will start for AM and UM data security procedure will start at RLC layer. And for TM mode security procedure start at MAC layer. 36) What are the mandatory SIBs which UE has to read before campign campaign? SIB 1, 3,5,7,11 37) What are the important RACH parameters and which SIB contains this information? SIB 7/5 38) Which SIB contains S criteria information? SIB 3