1. Content
Layer3 Message Analysis

2. - This page is intended to be blank -

3. AMR CS Call Phases BTS DRNC SRNC CN UE
1. Cell search, BCCH decoding & RACH access
DRNC
SRNC CN UE
2. RRC Connection Setup
3. UE <-> CS-CN signalling
4. RAB Set-up
5. UE <-> CS-CN signalling
6. Service Established
7. Branch addition/deletion & active set update
8. Service Released

4. RRC Connection Set-up Signalling FlowUE
WBTS
RNC
RRC: RRC CONNECTION REQUEST (RACH)
Admission Control
NBAP: RADIO LINK SETUP REQUEST
NBAP: RADIO LINK SETUP RESPONSE
ALCAP: ERQ
ALCAP: ECF
FP Downlink Sync
FP Uplink Sync
RRC: RRC CONNECTION SETUP (FACH)
L1 Sync
NBAP: SYNCH INDICATION
RRC: CONNECTION SETUP COMPLETE (DCH)

5. UE<–> CS_CN signalling
Location Update
Authentication
Security Mode Setup
Paging
Call Setup
1. Location Update Request
2. Authentication and Security Mode Setup
3. Location Update Accept
4. Paging
MSC / VLR
5. Call Setup UE
Location Updating
The location updating procedure is a general procedure which is used for the following purposes:
- normal location updating (described in this section);
- periodic updating;
- IMSI attach.
The normal location updating procedure is used to update the registration of the actual Location Area of a UE in the network. It shall also be started if the network indicates that the UE is unknown in the VLR as a response to MM connection establishment request.
To limit the number of location updating attempts made, where location updating is unsuccessful, an attempt counter is used. The attempt counter is reset when a UE is switched on or a SIM card is inserted.
Upon successful location updating the UE sets the update status to UPDATED in the SIM, and stores the received Location Area Identification in the SIM. The attempt counter shall be reset.
The location updating procedure is always initiated by the UE.
Authentication
The purpose of the authentication procedure is:
To permit the network to check whether the identity provided by the mobile station is acceptable or not.
To provide parameters enabling the mobile station to calculate a new UMTS ciphering key.
To provide parameters enabling the mobile station to calculate a new UMTS integrity key.
To permit the user equipment to authenticate the network.
The UMTS authentication procedure is always initiated and controlled by the network.
RNC
MGW
WBTS

6. PS Call Phase UE BTS DRNC SRNC CN
1. Cell search, BCCH decoding & RACH access
2. RRC Connection Setup
3. GPRS Attach
4. RAB Set-up
5. UE <-> PS-CN signalling (PDP context activation Accept)
6. Radio Bearer Reconfiguration
7. PS Data Session Established
8. State Transitions
Location Updating
The location updating procedure is a general procedure which is used for the following purposes:
- normal location updating (described in this section);
- periodic updating;
- IMSI attach.
The normal location updating procedure is used to update the registration of the actual Location Area of a UE in the network. It shall also be started if the network indicates that the UE is unknown in the VLR as a response to MM connection establishment request.
To limit the number of location updating attempts made, where location updating is unsuccessful, an attempt counter is used. The attempt counter is reset when a UE is switched on or a SIM card is inserted.
Upon successful location updating the UE sets the update status to UPDATED in the SIM, and stores the received Location Area Identification in the SIM. The attempt counter shall be reset.
The location updating procedure is always initiated by the UE.
Authentication
The purpose of the authentication procedure is:
To permit the network to check whether the identity provided by the mobile station is acceptable or not.
To provide parameters enabling the mobile station to calculate a new UMTS ciphering key.
To provide parameters enabling the mobile station to calculate a new UMTS integrity key.
To permit the user equipment to authenticate the network.
The UMTS authentication procedure is always initiated and controlled by the network.
9. Branch addition/deletion & active set update
10. PS Data Session Released

7. GPRS Attach
UE performs cell search and RRC Connection Establishment in the same way as for an AMR call
The UE registers with the PS-CN through the GPRS Attach procedure UE
Node B
RNC
SGSN
RRC Connection
Initial Direct Transfer: GPRS Attach Request (DCH)
SCCP: Connection Request
Initial UE message : GPRS Attach Request
SCCP: Connection Confirm
Downlink Direct Transfer: Authentication and Ciphering Request (DCH)
Direct Transfer: Authentication and Ciphering Request
Uplink Direct Transfer: Authenication and Ciphering Response (DCH)
Direct Transfer: Authentication and Ciphering Response
Security Mode Command (DCH)
Security Mode Command
Secuirty Mode Complete (DCH)
Common ID
Downlink Direct Transfer: Common ID (DCH)
Direct Transfer: Identity Request
Location Updating
The location updating procedure is a general procedure which is used for the following purposes:
- normal location updating (described in this section);
- periodic updating;
- IMSI attach.
The normal location updating procedure is used to update the registration of the actual Location Area of a UE in the network. It shall also be started if the network indicates that the UE is unknown in the VLR as a response to MM connection establishment request.
To limit the number of location updating attempts made, where location updating is unsuccessful, an attempt counter is used. The attempt counter is reset when a UE is switched on or a SIM card is inserted.
Upon successful location updating the UE sets the update status to UPDATED in the SIM, and stores the received Location Area Identification in the SIM. The attempt counter shall be reset.
The location updating procedure is always initiated by the UE.
Authentication
The purpose of the authentication procedure is:
To permit the network to check whether the identity provided by the mobile station is acceptable or not.
To provide parameters enabling the mobile station to calculate a new UMTS ciphering key.
To provide parameters enabling the mobile station to calculate a new UMTS integrity key.
To permit the user equipment to authenticate the network.
The UMTS authentication procedure is always initiated and controlled by the network.
Uplink Direct Transfer: Identity Response (DCH)
Direct Transfer: Identity Response
Downlink Direct Transfer: Location Attach Accept (DCH)
Direct Transfer: Attach Accept
Uplink Direct Transfer: Attach Complete (DCH)
Direct Transfer: Attach Complete

8. PDP Context Location UpdatingUE
Node B
RNC
SGSN
GPRS Attach
Uplink Direct Transfer : Activate PDP context request (DCH)
Direct Transfer : Activate PDP context request
RANAP: RAB Assignment Request
RRC: Radio Bearer Setup
Radio Bearer Setup Complete
RAB Assignment Response
Measurement Control
Measurement Control
Downlink Direct Transfer : Activate PDP Context Accept (DCH)
Direct Transfer: Activate PDP Context Accept
Call Established
Location Updating
The location updating procedure is a general procedure which is used for the following purposes:
- normal location updating (described in this section);
- periodic updating;
- IMSI attach.
The normal location updating procedure is used to update the registration of the actual Location Area of a UE in the network. It shall also be started if the network indicates that the UE is unknown in the VLR as a response to MM connection establishment request.
To limit the number of location updating attempts made, where location updating is unsuccessful, an attempt counter is used. The attempt counter is reset when a UE is switched on or a SIM card is inserted.
Upon successful location updating the UE sets the update status to UPDATED in the SIM, and stores the received Location Area Identification in the SIM. The attempt counter shall be reset.
The location updating procedure is always initiated by the UE.
Authentication
The purpose of the authentication procedure is:
To permit the network to check whether the identity provided by the mobile station is acceptable or not.
To provide parameters enabling the mobile station to calculate a new UMTS ciphering key.
To provide parameters enabling the mobile station to calculate a new UMTS integrity key.
To permit the user equipment to authenticate the network.
The UMTS authentication procedure is always initiated and controlled by the network.

9. Radio Bearer Setup/Complete & RAB Assignment Response
Once the RANAP: RAB Assignment Request message has been received from PS CN and RNC has resources to setup the 0/0 kbps RB the RNC sends a RRC: Radio Bearer Setup message to the UE
The UE acknowledges the RRC: Radio Bearer Setup message with a RRC: Radio Bearer Setup Complete message
Once the radio bearer establishment has been acknowledged, the RNC indicates to the PS core that the RAB has been established using the RANAP: RAB Assignment Response message UE
Node B
RNC
SGSN
GPRS Attach
Uplink Direct Transfer : Activate PDP context request (DCH)
Location Updating
The location updating procedure is a general procedure which is used for the following purposes:
- normal location updating (described in this section);
- periodic updating;
- IMSI attach.
The normal location updating procedure is used to update the registration of the actual Location Area of a UE in the network. It shall also be started if the network indicates that the UE is unknown in the VLR as a response to MM connection establishment request.
To limit the number of location updating attempts made, where location updating is unsuccessful, an attempt counter is used. The attempt counter is reset when a UE is switched on or a SIM card is inserted.
Upon successful location updating the UE sets the update status to UPDATED in the SIM, and stores the received Location Area Identification in the SIM. The attempt counter shall be reset.
The location updating procedure is always initiated by the UE.
Authentication
The purpose of the authentication procedure is:
To permit the network to check whether the identity provided by the mobile station is acceptable or not.
To provide parameters enabling the mobile station to calculate a new UMTS ciphering key.
To provide parameters enabling the mobile station to calculate a new UMTS integrity key.
To permit the user equipment to authenticate the network.
The UMTS authentication procedure is always initiated and controlled by the network.
Direct Transfer : Activate PDP context request
RANAP: RAB Assignment Request
RRC: Radio Bearer Setup
Radio Bearer Setup Complete
RAB Assignment Response

10. Radio Bearer ReconfigurationUE
Node B
RNC
SGSN
GPRS Attach
Uplink Direct Transfer : Activate PDP context request (DCH)
Direct Transfer : Activate PDP context request
RANAP: RAB Assignment Request
RRC: Radio Bearer Setup
Radio Bearer Setup Complete
RAB Assignment Response
Measurement Control
Measurement Control
Downlink Direct Transfer : Activate PDP Context Accept (DCH)
Direct Transfer: Activate PDP Context Accept
Call Established
Measurement Report : e4a
NBAP: Radio Link Reconfigure Prepare
Admission Control
Radio Link Reconfigure Ready
AAL2SIG:ERQ
AAL2SIG:ECF
FP: Downlink Sync
FP: Uplink Sync
Radio Link Reconfiguration Commit
RRC: Radio Bearer Reconfiguration (DCH)
RRC: Radio Bearer Reconfiguration Complete (DCH)
Measurement Control

11. HSPA Setup
HSUPA cannot be established without HSDPA, HSDPA UL return channel is HSUPA instead of R99
High level procedure is the same as that for an NRT DCH
RNC starts by allocation a 0/0kbps connection
Selection between DCH and E-DCH is then completed when RNC receives the uplink or downlink capacity request UE
Node B
RNC
SGSN
RRC Establishment
GPRS Attach
0/0 kbps DCH allocated
PDP Context Activation
Measurement Report : e4a
Uplink capacity request
RNC completes channel type selection procedure
HSUPA connection can be established
RRC Idle mode
directly from CELL_PCH (Cell Update with reason Uplink Capacity Request)

12. Radio Resource Control
RRC is located at Layer 3 in the control plane of the access stratum (AS). It resides in the UE and the UTRAN – at the Node B (UE in idle mode) or SRNC (UE in connected mode). RRC provides signalling transfer services to higher layers through service access points (SAP). Higher layer signalling messages are encapsulated within RRC messages for transmission over the radio interface. NAS higher layer entities using the services of RRC in this way are:
Call Control (CC), which deals with set-up, maintenance and clear-down of circuit switched
calls.
Session Management (SM), which deals with set-up, maintenance and clear-down
of pocket-switched sessions.
Mobility Management (MM), which deals with all mobility issues involving tracking of
UEs as they move from area to area. Related to this is GPRS Mobility Management
(GMM) which does the same for packet-mode operation.
Short Message Service (SMS), dealing with SMS message delivery.

13. RRC Services Broadcast services • Paging and Notification services
• Dedicated Control services
• Encapsulation of NAS signaling (CC, SM, MM, GMM, SMS)

14. RRC Function
Broadcasting Control Information • Paging and Notification • Establishment, maintenance and release of RRC Connection • Control of Transport and Physical Channel resources • Mobility functions • Cell selection and re-selection in Idle Mode • Downlink Outer and Open Loop power control • Radio Resource Arbitration between users • Radio Resource Management between cells • Routing Non-Access Stratum data • Control of RLC & MAC Security functions • Congestion Control • QoS Control • Integrity Protection of signaling messages • Control of terminal measurement reporting • Timing Advance in TDD mode

15. RRC States

16. RRC Procedure

17. RRC Connection Management
• System Information (SI) broadcast • RRC connection establishment • RRC connection release • RRC connection re-establishment • Paging and Notification • UE capability enquiry • Transmission of UE capability information • UE dedicated paging • Initial direct transfer • Uplink direct transfer • Downlink direct transfer • Security mode control • Signaling connection release request • Signaling connection release

18. Broadcast of System information
System Information in terms of static and dynamic parameters is organised into System Information Blocks (SIBs). To provide flexibility, information is disseminated amongst a “family tree” of 16 SIBs, each of which can be further subdivided. A specific SIB contains scheduling information for the main 16 blocks and they in turn contain information about scheduling of related sub-blocks.
SIBs are either segmented or concatenated as required into System Information messages lasting 20 ms (2 radio frames). Padding may be added to fill a message. SI messages are scheduled over a repetition period (SIB_REP). The position of the first message is defined by SIB_POS (0) and the offset between subsequent segments by SIB_OFF (i). The cell system frame number increments from 0 to 4094 in steps of 2 radio frames (20 ms) and is used to define these timings.

19. System Information
Within UTRAN system information is broadcasted with the help of the RRC messages
System Information,
Paging Type I, and
System Information Change Indication.
Most system information parameters are determined by the RNC. The Node B is informed about the parameters via the NBAP message BCCH Information. Some system parameters can be made available by the Node B, such as interference values, which change fast.
Given the system information, the UE is capable to decide, whether or how to access the PLMN via the existing cell.
System information is organised in System Information Blocks (SIBs).
System information is grouped into SIB 1 to SIB 18.
Each SIB is responsible to carry a specific content. For instance, SIB 12 holds measurement control information and parameters.
Depending on the UE‘s RRC state, is reads specific SIBs, and uses the transmitted parameters.
There is a huge amount of SIBs, which have to be read by the UE. This requires a lot of battery power. Therefore, a Master Information Block (MIB) was introduced, which gives references and scheduling information about the SIBs. The MIB is transmitted in every 8th radio frame on the P-CCPCH (on position SFN mod 8 = 0, and with a TTI of 20 ms). For most of the SIBs used within the system, the MIB may carry a value tag. The only exceptions are SIB 15.2, SIB 15.3 and SIB 16. If a value tag is unchanged, the corresponding system information has not been modified. Thus, there is no need for the UE to read the SIB. SIB 7 has no value tag. It changes with each occurrence. Scheduling information is used to inform the UE, where and when a specific system information is transmitted.

20. NBAP: BCCH Information 8.2.16 System Information Update
UTRAN
System Information ( )
NBAP: BCCH Information
RNC UE
Node B
TS : NBAP
System Information Update
MIB
value tag M
position on P-CCPCH: SFN mod 8* = 0 TTI: 20 ms value tag M: range 1..8
MIB: Master Information Block
SIB: System Information Block
SFN: System Frame Number SB
value tag N
SIB 1
value tag 1
SIB 2
value tag 2
SIB 3
value tag 3
SIB 18
value tag 18

21. System Information Blocks
For each SIB, following characteristics were specified:
Area scope: Where is the value tag valid: within one cell or within a PLMN/ equivalent PLMN?
UE RRC state: When the SIB is valid?
UE RRC state: When the SIB is read?
Scheduling information: At which position is the SIB transmitted and what is its repetition period?
Modification of system information: Is it indicated by a value tag, or is it timer based?
The UE receives all SIBs via the BCCH. There is only one exception: SIB 10. If a UE is capable to receive simultaneously on one S-CCPCH and on one DPCH, then it receives SIB 10 on a FACH.
Master Information Block (MIB):
The MIB informs the UE about the supported PLMN types and the PLMN identity.
The UE finds in the MIB also references to up to maxSIB (=32) SIBs, including their scheduling information and type.
A MIB is valid in one cell. If a UE changes the cell, is must read the new cell‘s MIB.
The MIB is read in the RRC modes/states RRC idle, CELL_FACH, CELL_PCH and URA PCH.
Its parameter are valid in the same states.
A change of the MIB information is indicated by a value tag.
In this course documentation, we only describe the System Information Blocks (SIBs), which are used in NSN‘s RAN, and SIB 4 and SIB16.

22. System Information Blocks
System Information Block 1 (SIB 1)
This SIB is used to inform the UE about NAS system information.
The NAS system information characterises the NAS domains.
SIB 1 also delivers UE timers and counters, which have to be used by the UE in the RRC idle and RRC connected mode.
For instance, a UE in the RRC connected mode uses the timer T305 for periodic cell and URA updates.
SIB 1 is valid in one PLMN.
The MIB is read in the RRC modes/states RRC idle, CELL_FACH, CELL_PCH and URA PCH. Its parameter are valid in the same states, and the the RRC sub-state CELL_DCH.
If the UE selects a new cell, and the SIB 1 value tag has the same number as in the preceding cell, the same content is transmitted in this SIB. There is then no necessity for the UE to read this SIB after cell re-selection.
System Information Block 2 (SIB 2)
This SIB contains an URA identity list.
SIB 2 is read and valid in the RRC sub-state URA_PCH. A change of the SIB 2 information is indicated by a value tag.
System Information Block 3 (SIB 3)
This SIB contains relevant parameters for cell selection and re-selection.
It also holds the cell identity and cell restriction data, such as „cell barred“ IEs.
SIB 3 must be read and is valid in the RRC idle mode. It is read and valid in the RRC connected mode sub-states CELL_FACH, CELL_PCH and URA_PCH, if SIB 4 is not broadcasted.
A change of the SIB 3 information is indicated by a value tag.

23. System Information Blocks
System Information Block 4 (SIB 4)
This SIB holds mostly the same data fields as SIB 3*, but it is read and valid only, when the UE is in the RRC connected mode. I.e, this optional SIB is read and valid in the CELL_FACH, CELL_PACH and URA_PCH sub-state.
A change of the SIB 4 information is indicated by a value tag.
System Information Block 5 (SIB 5)
The parameters for the configuration of physical channels are broadcasted in this SIB.
The parameters cover the PICH power offset, the AICH power offset, P-CCPCH, S-CCPCH and PRACH system information lists.
SIB 5 must be read and is valid in the RRC idle mode.
It is read and valid in the RRC connected mode sub-states CELL_FACH, CELL_PCH and URA_PCH, if SIB 6 is not available.
A change of the SIB 5 information is indicated by a value tag.
System Information Block 7 (SIB 7)
This SIB holds fast changing parameters. Therefore no value tag is used for it.
The UE has to read its parameters periodically.
For that, an expiration timer (Expiration Time Factor) is broadcasted with this message.
SIB 7 expires at max(32, 8 * Expiration Time Factor).
Expiration Time Factor can have the values 2times, 4 times, 8 times times. Its default value is 1.
The fast changing parameters transmitted with SIB 7 include the UL interference and dynamic persistence level.
It is read and valid in all states except for the CELL_DCH sub-state.

24. broadcasted information
System Information
SIB
broadcasted information
read
valid
scope/ modification
MIB
PLMN types & identities#
SIB Scheduling information
SIB references
RRC idle mode, CELL_FACH, CELL_PCH, URA_PCH
RRC idle mode, CELL_FACH, CELL_PCH, URA_PCH
cell/ value tag
SIB 1
NAS information
UE timers & counters
RRC idle mode, CELL_FACH, CELL_PCH, URA_PCH
RRC idle mode, CELL_DCH, CELL_FACH, CELL_PCH, URA_PCH
PLMN/ value tag
e.g. T305: Periodic Cell/URA Update
T301, 302, 304,
SIB 2
URA identity list
URA_PCH
URA_PCH
cell/ value tag
SIB 3*
Cell selection and re-selection parameters°
RRC idle mode, (CELL_FACH, CELL_PCH, URA_PCH)
RRC idle mode, (CELL_FACH, CELL_PCH, URA_PCH)
cell/ value tag
e.g. CPICH Ec/N0 or CPICH RSCP; Sintrasearch, Sintersearch, Ssearch,RAT, Qqualmin, Qrxlevmin,..
SIB 4*
Cell selection & re- selection parameters for UEs in the connected mode
CELL_FACH, CELL_PCH, URA_PCH
CELL_FACH, CELL_PCH, URA_PCH
cell/ value tag
SIB 5*
Parameters for common physical channel configuration
RRC idle mode, (CELL_FACH, CELL_PCH, URA_PCH)
RRC idle mode, (CELL_FACH, CELL_PCH, URA_PCH)
cell/ value tag
# GSM-MAP/ANSI41; MCC+MNC; ° + Cell Access Restrictions
* Read SIB 3 / 5 in Connected Mode if SIB4 / 6 (Connected Mode) not available

25. System Information Blocks
System Information Block 11 (SIB 11)
This SIB holds measurement control information.
The UE gets here the relevant date for traffic measurement, intra-frequency measurements, etc.
SIB 11 must be read and is valid in the RRC idle mode. It is read and valid in the RRC connected mode sub-states CELL_FACH, CELL_PCH and URA_PCH, if SIB 12 is not broadcasted.
It is also valid in the RRC sub-state CELL_DCH, as long as the UE did not get a Measurement Control message from UTRAN and SIB 12 is not broadcasted.
A change of the SIB 11 information is indicated by a value tag.
System Information Block 12 (SIB 12)
SIB 12 transmits measurement control information for UEs in the RRC connected mode.
If not transmitted, the UEs take the parameters broadcasted with SIB 11.
If available, SIB 12 is read and valid in the RRC connected mode sub-states CELL_FACH, CELL_PCH and URA_PCH.
It is also valid in the RRC sub-state CELL_DCH, as long as the UE did not get a Measurement Control message from UTRAN. A change of the SIB 12 information is indicated by a value tag.
System Information Block 16 (SIB 16)
RB, TrCH, and PhyCH parameters are broadcasted, which are stored by the UE both in the RRC idle and RRC connected mode.
The parameters are used during a handover to UTRAN. Consequently, these parameters stay valid, when the UE is connected to GSM and GPRS.
This SIB is valid in all RRC states, and read in all RRC states except for the CELL_DCH. The UE reads and stores the parameters. A change of the SIB 16 information is indicated by a value tag.

26. broadcasted information
System Information Blocks
SIB
broadcasted information
read
valid
scope/ modification
SIB 7
Fast changing parameters:
UL interference level
Dynamic persistence level
RRC idle mode, CELL_FACH, CELL_PCH, URA_PCH
RRC idle mode, CELL_FACH, CELL_PCH, URA_PCH
cell/ max(32, 8 * Expir-‘
ation Time Factor)
SIB 11
Measurement control information*
RRC idle mode, (CELL_FACH, CELL_PCH, URA_PCH)
RRC idle mode, (CELL_DCH, CELL_FACH, CELL_PCH, URA_PCH)
cell/ value tag
SIB 12
Measurement control information* for UEs in the RRC connected mode
CELL_FACH, CELL_PCH, URA_PCH
CELL_DCH, CELL_FACH, CELL_PCH, URA_PCH
cell/ value tag
SIB 16
RB, TrCH, and PhyCH parameters for a GSM/GPRS-UMTS HO
RRC idle mode, CELL_FACH, CELL_PCH, URA_PCH
RRC idle mode, CELL_FACH, CELL_PCH, URA_PCH)
cell/ value tag
Examples of other SIB’s:
SIB 13: ANSI-41 system information
SIB 14: Only for 3.84 Mcps TDD
SIB 15: useful for UE-based or UE-assisted positioning methods
SIB 17: only for TDD
SIB 18: contains PLMN identities of neighbouring cells to be considered
in idle mode as well as in connected mode.
* e.g. FMCx & HOPx par.; Use of HCS; Ec/N0 orRSCP; Intra-, Inter-Frequency, Inter-RAT meas. info; Traffic volume meas. Info (e.g. RLC buffer payload)
(adopted from TS RRC)

27. Radio Bearer Control
•Radio bearer setup •Radio bearer re-configuration •Radio bearer release •Transport channel re-configuration •Transport format combination control •Physical channel re-configuration •DL Outer loop power control •UL Physical channel control •Physical shared channel allocation (TDD) •PUSCH capacity request (TDD)
Radio Access Bearer (RAB) is the term used to describe the overall bearer service
between the Core Network node (MSC or SGSN) and the UE (user plane).
The Radio Bearer, RLC, MAC and the LI channels form part of the RAB and it is
the responsibility of RRC. At connection set up, RRC must provision an appropriate
RAB to suit the required QoS. Lower layers in the UE and UTRAN are responsible
for measuring traffic load and reporting to RRC to aid in the provision of appropriately
configured RABs. The Transport Channels between MAC and LI may also need
dynamic re-configuration during a connection for example from common (e.g. RACH)
to dedicated (DCH) and RRC needs to determine the need for, and implement,
such changes.

28. RRC Connection Mobility
•Cell update (basic, basic plus RNTI re-allocation, basic plus physical channel re-allocation) •URA update (basic, basic plus RNTI re-allocation) •Active set update (in soft handover) •Hard handover within UTRAN •Inter-system handover to/from UTRAN •Inter-system cell reselection to/from UTRAN •RNTI re-allocation

29. Measurement Control Message
• Measurement Command • Measurement Type • Measurement Identity Number • Measurement Objects • Measurement Quantity • Reporting Quantities • Reporting Mode • Measurement Reporting Criteria
Measurement Type:
•Intra frequency
•Inter frequency
•Inter system
•Downlink quality
•Uplink traffic volume
•LCS related
•Internal (UE)
UEs in any RRC state may be sent a Measurement Control message to set-up,
modify or terminate measurements. Various parameters define the action required.
The Measurement Command parameter indicates whether a set-up, modification or
termination is required and the Measurement Type defines the type of quantity to be
measured. A Measurement Identity Number identifies the measurement for future
reference (e.g. termination). Neighbour cell information is indicated by the
Measurement Objects parameter. Specific details of the quantities to be measured
are provided by the Measurement Quantity parameter, but the UE will only report
those quantities indicated by the Reporting Quantities parameter. Measurement
Reporting Criteria determine the conditions triggering a report and finally, Reporting
Mode indicates whether RLC AM or UM should be used.
The RRC Measurement Control message is used only for UEs in the DELL_DCH
State. In any other state, instructions about measurements to be made are sent on
the P-CCPH through SI messages.

30. General RRC Procedures
•Open-loop power control •Access service class management •Access class management •Physical channel establishment •Radio link failure •Integrity protection •Out-of-service area detection •Connected ----idle mode transitions •Selection of initial UE identity •Measurement timing
RRC deals with open loop power control by calculating appropriate initial power
levels for PRACH, PCPCH or DPCCH use. Access service classes are used to
manage and prioritise PRACH usage between UEs, and involves mapping the UE
Access Class to an Access Service Class.
To manage orderly physical channel establishment, RRC uses a timer (T312) to
determine successful establishment. Radio link failure is detected (for UEs in
CELL_DCH state) using two counters (N313 and N315) and the timer T313.
Integrity protection is carried out for the majority of RRC messages, using a
checksum.
RRC must also detect when it is out of its registered cell or URA and take appropriate
action, using counters and timers together with RRC mobility management
procedures.
When the UE is entering idle mode from connected mode, RRC manages the overall
selection of most appropriate PLMN and cell.
If a UE is about to commence RRC connection procedures, RRC must also select an
appropriate initial identity to use in the procedure. This could be IMSI, P-TMSI, TMSI
or IMEI.
UEs in the CELL_FACH state are required under some circumstances to make
measurements with a frequency determined by calculation by RRC.

31. - This page is intended to be blank -