Developed By: Aumpika Viun (Ice)

Contact: aumpikav@yahoo.com

W-RNO AnalysisMate Ver1.0

0. UTRAN Network Architecture and Protocols

1.1 UMTS Network Architecture

1.2 UTRAN Protocols

1. RRC,RB and UE Measurement Procedures
1.1 Mapping of UE state to 3GPP Specifications

1.2 RRC Tasks and Functions

1.3 RRC Modes and State Transitions including GSM

1.3 RRC Mode Description

1.4 RRC Connection Mobility Management and RRC Modes

1.5 RRC Procedures

1.6 RB Procedures

1.7 UE Measurement Procedures

2. Paging Messages

2.1 Paging Message Type 1

2.2 Paging Message Type 2

3. System Information Block (SIB)

4. Location Update Procedure & L3-messages

5. Call Procedure & L3-messages

5.1 AMR Voice (MOC)
5.1 AMR Voice (MTC)

5.2 CS64/ Video Call

5.3 PS-R99

5.4 PS-HSDPA

5.5 PS-HSUPA
6. HO Procedure & L3-messages (Intra-Freq HO)
6.1 Intra-Frequency Soft Handover within a NodeB(Softer-HO)
6.2 Intra-Frequency Soft Handover between NodeBs in an RNC
6.3 Intra-Frequency Soft Handover between RNCs

6.4 Intra-Frequency Hard Handover Between NodeBs in an RNC

6.5 Intra-Frequency Hard Handover Between RNCs

7.HO Procedure & L3-messages (Inter-Freq HO)

7.1 Inter-Frequency Hard Handover Between NodeBs in an RNC

7.2 Inter-Frequency Hard Handover Between RNCs

8. HO Procedure & L3-messages (Inter-RAT HO)
8.1 Inter-RAT CS Handover from WCDMA to GSM (Coveraged Based)

8.2 Inter-RAT CS Handover from GSM to WCDMA(Coveraged Based)

8.3 Inter-RAT PS Handover from WCDMA to GSM(Coveraged Based)
8.4 Inter-RAT PS Handover from GSM to WCDMA(Coveraged Based)

8.5 Inter-RAT CS&PS Handover from WCDMA to GSM (Intra-SGSN)

8.6 Inter-RAT CS&PS Handover from WCDMA to GSM (Inter-SGSN)

9.SRNS Relocation Procedure & L3-messages

9.1 Static Relocation(UE not-involved relocation)

9.2 Relocation with Cell/URA Update (UE not-involved relocation)

9.3 Relocation with Hard Handover (UE involved relocation)

 Convention Description
All texts with an Underline has a hyperlink function which link to other rela
Underline Text
procedure, signalling measages,parameter description, features algorithm

MML Command All bold texts with highlighted in "Orange" are MML command

Click to return to main page Click here to return to root topic

Value= Give an acutal value includes the conversion schemes
Comments Extra comments for some topics

Genex Assistant
Tool Version Release Date Genex Probe Version
Version
V100R005C01B040 (V1.51 V100R005C01B040
Ver1.0 25-Jun-09
20090210 ) (V1.52 20090210 )

Tool Version Change Type Change History

;
 Description
unction which link to other related information e.g. signalling
escription, features algorithm etc.

are MML command

schemes

RAN Version RNC Version

10.0 V200R010C01B061

Change Date Remark

Change Type

Correction
Addition
Remove
Click to return to main page
UMTS Network Architecture (Rel'99)

The UMTS PLMN is logically divided into a Core Network (CN), a Radio Access Network (RAN) and the User Equipment UE.

The Core Network(CN) consists of an enhanced GSM Phase2+ with a Circuit Switched CS and Packet Switched PS (i.e. GPRS) do
The most important network elements of these GSM Phase 2+ CN are:
- Mobile Service Switching Center(MSC)
- Gateway Mobile Service Switching Center (GMSC)
- Visitor Location Register (VLR)
- Home Location Register (HLR)
- Authentication Center (AuC)
- Equipment Identity Register (EIR)
- Serving GPRS Support Node (SGSN)
- Gateway GPRS Support Node (GGSN)

The RAN of UMTS is the UMTS Terrestrial Radio Access Network (UTRAN) consists of,
- Radio Network Controller (RNC), which is controlling a Radio Network Subsystem (RNS)
- Node B, which is the physical entity to serve on or several cells

The User Equipment(UE) consists of,

- Mobile Equipment (ME), The Mobile Equipment represents the partner of the NodeB and of the RNC. It is responsible for serving the ra
encoding,Modulation and demodulation on the carrier,Power control,Quality and field strenght measurements,Ciphering and authorization

- UMTS Subscriber Identity Module (USIM), The USIM functions to save data and procedures in ther terminal equipment. It supports cal
entries, etc. The installed USIM is made available to the customer by the network operator and can be updated e.g. via SMS or cell broad
Examples of USIM data and procedures,
1.Data: International Mobile Subscriber Identity,Packet Switched Location Information,Security Information for authentication and chipherin
period,Call meters,Display Languages,Telephone directory,Forbidden PLMNs,Emergency Call Codes etc.
2.Procedures: Application related procedures,Security related procedures,Subscription related procedures etc.

With UTRAN, four new interfaces were specified:

- Iu, Iu connects UTRAN with the CN. A distinguishing is drawn between the Iu connection to the ps domain, which is labelled Iu-PS, and to
network solution. Please note, that there are differences in the protocol stacks on the Iu-CS and Iu-PS interface.
- Iub, this interface is used between the Node B and its controlling RNC.
- Iur, this is an inter-RNS interface, connecting two neighbouring RNC. It is used among others in soft handover situations, where a UEs a
the UE; it is called S-RNC. The remaining RNCs are called D-RNC.
- Uu, Uu is the acronym for the WCDMA radio interface.
On the interfaces Iu, Iur, and Iub, ATM is used for the transport of user data and higher layer signalling information.
Radio Network Controller(RNC) Functionality

The RNC has many different tasks in the UTRAN. It is responsible for e.g. Radio Resource Management (RRM) and the control of itself an
transfer to other RNCs are possible via Iur interface and to the connected Node Bs via Iub interface.
The following are examples of RNC functions:
- Power Control
- Handover
- Ciphering/Deciphering
- Protocol conversion
- Admission Control/Load Control
- Macro Diversity
- Geographical Coordinates

Logically,the RNC can be divided into different types, according to its current functionality as follows,
1. Controlling RNC (C-RNC) : Every cell has only one C-RNC. The C-RNC of a cell is exactly the RNC that is connected with the NodeB s
- Admission Control based on UL interference and DL transmission power level
- System Information Broadcasting
- allocation/de-allocation of radio bearers
- data transmission and reception
- Congestion control in its own cell
- Power control
- Resource allocation and admission control for new radio links to be established in those cells

Summary: The C-RNC is the RNC controlling a Node B ( i.e. terminating the Iub interface towards the NodeB).This means the C-R

2. Serving RNC (S-RNC) :

An UE that is attached to an UTRAN is served by only one RNC. This RNC is called the serving RNC (S-RNC).The existence of a serving
information transport through UTRAN. The S-RNC performs the following functions:
- the S-RNC handles the Iu interface towards the CN for this UE
- the S-RNC handles the completed Radio Resoruce Control (RRC) for this UE
- Location/Mobility handling
- Ciphering
- Backward Error Correction (BEC, layer 2 functionality)
- Radio bearer control
- Handover decision
- Power Control

The S-RNC is responsible for the handling of all decisions for the connection with the UE e.g. for the allocation/modification or release of ra
In the case of Soft Handover,S-RNC performs data splitting toward the different NodeBs and combining toward the CN. It decides to add o
the C-RNC of some NodeBs used for the connection toward an UE. The S-RNC is no anchor functionality. It can be re-allocated to another

Summary: The S-RNC for one UE is the RNC that terminates both Iu link for transport of user data and corresponding RANAP sig
(signalling protocol between UE and UTRAN)

3. Drift RNC (D-RNC): In UMTS it is possible that one UE is connected to more than one cell, or connected to a cell, that does not belong
- Handover decision
- Power Control

The S-RNC is responsible for the handling of all decisions for the connection with the UE e.g. for the allocation/modification or release of ra
In the case of Soft Handover,S-RNC performs data splitting toward the different NodeBs and combining toward the CN. It decides to add o
the C-RNC of some NodeBs used for the connection toward an UE. The S-RNC is no anchor functionality. It can be re-allocated to another

Summary: The S-RNC for one UE is the RNC that terminates both Iu link for transport of user data and corresponding RANAP sig
(signalling protocol between UE and UTRAN)

3. Drift RNC (D-RNC): In UMTS it is possible that one UE is connected to more than one cell, or connected to a cell, that does not belong
to the S-RNC.This foreign RNC is called drift RNC ,D-RNC. In principle the D-RNC is the C-RNC of a cell the UE is connected to, but its n
controlled by S-RNC.

When a D-RNC is involved for a UE, then the data streams between UE-UTRAN and UE-CN always pass the S-RNC. In the downlink the
The UE receives all the data streams from the cells,it is connected to and adds them together (RAKE Receiver, Maximum Ratio Combining
the S-RNC takes only the data frame with the smallest bit error rate, all other data frames will be discarded (Selective combining). The usa
Because the implementation of Iur interface is optional,i's matter of network planning, whether the usage of D-RNCs is allowed or not.

Summary: D-RNC is any RNC, other than SRNC that controls cells used by the UE. The D-RNC performs macro-diversity combini
,but routes the data transparently between the Iub and Iur interfaces.The UE can be connected to 0 ,one or more DRNCs. ( Macro
more UTRAN access points.

Node B Functionality
A nodeB is a physical unit for implemen
are serviced by a Node B in UMTS.

A Node B can be used for Frequency D

operation. A Node B converts user and
the signal to noise ratio (SIR) of the Use
the links and determines the Frame Err

- Radio Channel functions: Transport

- Air Interface management. Controllin
Intra NodeB SofterHO,Power Control,Q
- O&M Processing,Interfacing with M20
- Cellular Transmission management
of the physical transmission interfaces

Geographical and UTRAN Entity Identifiers

1.International UMTS/GSM Service Area
International UMTS/GSM Service Area, i.e. the world-wide area where access to GSM and UMTS network is possible,is sub-divided into N
2.National Service Area
National Service Area is the area of on country or region. It is identified by the Mobile Country Code (MCC) and Country Code (CC). The N
3. PLMN Service Area
PLMN Service Area is the service area of a single PLMN. It identified by the Mobile Country Code(MCC) and Country Code (CC). The Nati
4. MSC/SGSN Service Area
An MSC or SGSN Service Area is the area, which is served by a single MSC (CS-domain) or by a single SGSN (PS-domain). MSC and SG
SGSNs have their own identifiers/addresses for singalling and user data transfer.
5. Location Area (LA)
A Location Area (LA) is the most precise UE location information,which is stored in the CS-domain (in the VLR) of UMTS. A Location Area
6. Routing Area (RA)
The SGSN Service Area is sub-divided into one or more Routing Areas. A Routing Area (RA) is a subset of a Location Area i.e. one LA may
stored in the PS-domain (in the SGSN) of UMTS. It is world-wide uniquely identified by the Routing Area Identity. The RA is sub-divided into
7. Cell Area
The Cell is the area, where the UE is located. It is the most precise information which might be stored in the PLMN (in the RNC). The cell is

It is also essential to address different physical,geographical or logical entities within UMTS. The geographical and physical entit

1. PLMN Id = MCC +MNC

The PLMN-ID is used to address a PLMN in a world-wide unique manner. As in GSM the PLMN-ID consist of a MCC(mobile country code)
2. CN-Domain Id:
CS- and PS core network introduce their own regional area concept. This is the concept of Location Area for CS and the concept of Routin
LAI= PLMN-ID + LAC (Location Area Identity Code)
RAI= PLMN-ID + LAC +RAC ( Rotuing Area Identity Code)
3. Cell Global Identity (CGI)
The Cell Global Identity (CGI) is composed by the CGI=LAI+CellID.
4. RNC Id:
Every RNC node has to be uniquely identified within UTRAN. Therefore every RNC gets a RNC-ID. Together with the PLMN-ID the RNC-ID
interface. The RNC identifier is allocated by O&M.
Global RNC-ID= PLMN-ID + RNC-ID
5. Cell Id and UTRAN Cell Id:
The cell-ID is used to address a cell within a RNS. The cell-ID is set by O&M in the C-RNC. Together with the RNC-ID the Cell-ID forms the
UTRAN Cell-ID= RNC-ID + Cell-ID
6. Local Cell Identifier
The local cell identifier is used in the Node B to identify resources. There is a unique relation UTRAN Cell-ID to local cell identifier
7. Service Area Id:
Serveral cells of one location area can be defined to form a service area. Such a service area is identified with a SAI(service area id):
SAI= PLMN-ID+LAC+SAC
8. URA ID:
The UTRAN introduces its own area concept next to LA and RA. This is the UTRAN Registration Area (URA)
UTRAN Cell-ID= RNC-ID + Cell-ID
6. Local Cell Identifier
The local cell identifier is used in the Node B to identify resources. There is a unique relation UTRAN Cell-ID to local cell identifier
7. Service Area Id:
Serveral cells of one location area can be defined to form a service area. Such a service area is identified with a SAI(service area id):
SAI= PLMN-ID+LAC+SAC
8. URA ID:
The UTRAN introduces its own area concept next to LA and RA. This is the UTRAN Registration Area (URA)

UTRAN Identifiers for UE

The UE and the Subscriber can have several identifiers for the PLMN. Typically we can distinguish two types of identifiers accord

1. Core Network Identities or NAS (Non Access Stratum) Identifiers: These identifiers are allocated by the core network. In detail there
2. UTRAN identifiers : UTRAN identifiers are always temporary (Radio Network Temporary Identifiers ,RNTIs). This means they are alloca

- International Mobile Subscriber Identity (IMSI)

The IMSI is the quasi-permanent subscriber identity in GSM/UMTS. The IMSI is composed by the Mobile Country Code,MCC (3 digits) + M
- Temporary Mobile Subscriber Identity (TMSI)
The TMSI is used as temporary user identity instead of the IMSI to support subscriber identity confidentiality. This TMSI is allocated to an U
- Packet Temporary Mobile Subscriber Identity (P-TMSI)
The P-TMSI is used as temporary packet user identity. It is allocated to an UE b y an SGSN and stored in the U-SIM. The P-TMSI consists
- International Mobile Equipment Identity (IMEI)
The IMEI is used as Mobile Equipment Identity. The IMEI can be checked at the start of a connection by the EIR. The IMEI(15 digits) consi
identifiers the place of manufacture or final assemblym,the Serial Number (6 digits) and a Spare digit.
- Radio Network Temporary Identifiers (RNTI)
The RNTIs are temporary UE identifier within UTRAN and between UE and UTRAN. They are generated by the RNCs. Fours RNTI types

1. Serving RNC RNTI (S-RNTI) : The S-RNTI is allocated by the S-RNC,after every S-RNC Reallocation it has to be reallocation,too.The S
S-RNC and by the UE to identify itself ot the S-RNC
2. UTRAN RNTI (U-RNTI): The U-RNTI is composed by the S-RNTI and the S-RNC-id. It is used as UE Id for the first cell access (at cell c
associated response messages.
3. Cell RNTI (C-RNTI): The C-RNTI is allocated by the C-RNC,when the UE accesses a new cell. It is used as an in-band UE identifier in a
(see U-RNTI)
4. Drift RNC RNTI (D-RNTI): The D-RNTI is allocated by the D-RNC. It is used by the S-RNC to identify the UE to the D-RNC. It is never u
UTRAN Protocols

UTRAN Protocol Architecture

The UMTS network is split into the CN,U

information (including requesting the se
Access Stratum (AS).

The higher layer protocols of the Non-A

procedures (of Rel. '99) are in most cas
procedures. The radio and Iu protocols
used in the Iu and radio protocols for th

UTRAN Interface Protocol Structure

 Horizontal Layer The protocol structures of the UTRAN in
The modularity of this model allows cha

The transport system used within UTRA

different types of bearer service labelled
This means before a AAL type 2 virtual
set up and release occur.

Horizontal Layer:
The general protocol model consists of
are visible in the Radio Network Layer o
specific requirements.
- Transport Network Layer : The Trans
layer and its transport frame layer,also t
- Radio Network Layer : The Radio Ne
streams, to be transported through UTR

Vertical Plane:
There is also a vertical structure, the ele
next to eachother. The general protocol
Plane.
-User Plane: The user plane supports t
Vertical Layer protocols will be transmitted via data be
explicit signalling.
-Control Plane: The control plane cons
application protocol,one or several sign
signaling,which is UMTS-specific. It incl
Application Protocol messages.
-Transport Network Control Plane: Th
protocols are used to set up and release
not necessary to use the ALCAP for all
are used. The Transport Network Contro
information.

The Transport Network Control Plane a

to be total independent of the technolog

UTRAN Interface Protocol Overview

The protocols can be divided into the following part according to the functions:

1. User Plane : User Plane protocol stacks for transport of the user information on the different interfaces.
- Iu Interface : IuCS for Voice and Data and IuPS for Data
- Iub Interface: Frame Protocols (DCH and CCH)
- Radio Interface Uu: User Data Streams and Application
2. Control Plane : Control can be subdivided into:
-Control Plane for interface signaling (used for NE configuration)
-Control Plane for radio signaling
3. Transport Plane : Between user plance and control plane exist the transport plane. The task of transport plane is the setup of a data be

UMTS Protocol Stacks -> UE-UTRAN-CN for CS domain

Control Plane - CS

The CS control plane is used for the exchange of control information which are related to CS services. In addition ,the CS control plane is
-Physical Layer (PHY) : The physical layer (Layer1) on the air interface provides access to the WCDMA radio interface. Therefore it perfo
-Medium Access Control (MAC) : The MAC protocol belongs to Layer 2. The tasks of MAC are the control of random access and the mu
-Radio Link Control (RLC) : As MAC also the RLC protocol is a Layer 2 protocol. RLC provides three reliabilty modes for every radio bea
-Radio Resource Control (RRC) : The RRC protocol is the first protocol of Layer 3. The RRC protocol performs all higher layer tasks rela
-NAS Protocols : On top of RRC there are the control protocols for the non-access stratum (NAS). For the CS service these are: MM (Mo
Message Service), if it is not provided by the Packet Switched Protocol Stack.
-Radio Access Network Application Part (RANAP) : RANAP is between UTRAN and CN. It performs all tasks related to transport stratum
counterpart to RRC
-Signaling Connection Control Part (SCCP): The SCCP has mainlu transport tasks. It is used to establish a singling connection for a UE
identifier.
The CS control plane is used for the exchange of control information which are related to CS services. In addition ,the CS control plane is
-Physical Layer (PHY) : The physical layer (Layer1) on the air interface provides access to the WCDMA radio interface. Therefore it perfo
-Medium Access Control (MAC) : The MAC protocol belongs to Layer 2. The tasks of MAC are the control of random access and the mu
-Radio Link Control (RLC) : As MAC also the RLC protocol is a Layer 2 protocol. RLC provides three reliabilty modes for every radio bea
-Radio Resource Control (RRC) : The RRC protocol is the first protocol of Layer 3. The RRC protocol performs all higher layer tasks rela
-NAS Protocols : On top of RRC there are the control protocols for the non-access stratum (NAS). For the CS service these are: MM (Mo
Message Service), if it is not provided by the Packet Switched Protocol Stack.
-Radio Access Network Application Part (RANAP) : RANAP is between UTRAN and CN. It performs all tasks related to transport stratum
counterpart to RRC
-Signaling Connection Control Part (SCCP): The SCCP has mainlu transport tasks. It is used to establish a singling connection for a UE
identifier.
-MTP 3B,SAAL,AAL5, ATM : These protocols belong to transport network (ATM). They provide a signaling bearer to transport SCCP and R

User Plane- CS

UMTS transports the control signaling and the user data over the same transport network. So,there are some protocols supporting the use
-PHY,MAC,RLC : The air interface transport system is built out of PHY,MAC and RLC as for the control plane. The same basic stack is use
-User data stream : The user data streams are generated by the applications using the CS core network services (switched channels). Th
-ATM : The transport system for the Iu interface between UTRAN and CN is ATM
-AAL 2 : To provide a circuit switched like transport bearer on Iu, The AAL 2 protocol is used. This adaptation layer provides a bearer chan
synchronization and timing control between sender and receiver.
-Iu User Plane protocol (Iu UP) : The Iu user Plane protocl is on top of AAL2. This protocal can provide different stages of user data strea

Please note that AAL 5 is used for all control functions on the Iu-CS interface ( <> RANAP) and the Iub interface (<>NBAP). On the
messages (<> Iub-FP) between NodeB and RNC and for user data on Iu-CS interface between RNC and MSC.

UMTS Protocol Stacks -> UE-UTRAN-CN for PS domain

 Control Plane - PS

For Packet Switched (PS) service,there are different procedures. So there is a need for special proctocols for PS services. In fact these sp
The Packet Switched control plane consists of:
- PHY,MAC,RLC,RRC : The transport and access stratum protocols on the air interface are the same for PS and CS. UMTS has been des
- ATM,AAL 5, SAAL,MTP 3B : Also the transport and access stratum on the Iu-PS interface is similar to the Iu interface towards the MSC.
- SCCP,RANAP : SCCP and RANAP are the same as for CS. The SCCP is mainlu used to setup a signaling conenction to the SGSN in th
- NAS protocols : The only special protocols for the packet switched service are the non-access stratum protocols. Because there are ess
network has its own mobility managment GMM ( GPRS Mobility Management). To set up a data session the SM (Session Management) pr

In contrast to the control planes, that look very similar for PS and CS, the user plane has important differences.
The Packet Switched User Plane consists of:
- User data : The user data for PS services is usually dedicated to external packet data networks (e.g. internet). These external data netwo
network have their own special network protocols (e.g .TCP/IP). When a UMTS user wants want to be connected with such an external ne
network this only data. But because of its special role, the network protocol of the external network is called Packet Data Protocol (PDP).
transport of the PDP packets.
-Packet Data Convergence Protocol (PDCP) : This protocol performs header compression of the PDP packet header. This shall increase
-RLC,MAC,PHY : The transport layers are the same as for control plane
-GPRS Tunneling Protocol User Plane (GTP-U): The PDP packets are transported in a GTP-U frame on Iu. GTP-U organizes addressin
-UDP/IP : To route from RNC to SGSN the standard UDP/IP protocol stack is used. This is a connection less unreliable transport service. I
-AAL5 /ATM : The UDP/IP datagrams (packets) are transmitted on ATM using the adaptaiton layer 5.

UTRAN Interface Protocol -Uu (UE-UTRAN)

Physical Layer (L1) Functions
Transport
Transport Channel
Channel Processing
Processing for
for FDD
FDD Uplink
Uplink Transport
Transport Format
Format

L1 Functions
The functions of L1 (physical layer) mainly includes:

A) Transport Channel Processing: The processing of the transport channels that come from the MAC layer has the following steps,that c
1. CRC attachement (error detection) : Every transport block of a transport block set get its own CRC,used for error detection
2. Transport Block concatenation & code block segmentation : The transport blocks are concatenated after the CRC is appended. if th
3. Channel Coding : Channel coding can enhance symbol correlation to recover signals in the case of interference.UTRAN FDD and TDD
are : no coding,Convolutional coder 1:2,Convolutionalcoder 1:3,Turbo coder 1:3.
4. Rate matching (pucturing) : The physical layer can perform a puncturing of bits to reduce the data rate. the physical layer gets matchin
5. Radio Frame Equalization : If the data block after rate matching is too short for one radio frame,some padding bits are appended
6. Interleaving : Interleaving is used to damage symbol correlation and reduce the impact caused by fast fading and interference of the ch
7. TrCH Multiplexing : This function multiplexes several transport channels to one CCTrCH (Code Composite Transport Channels)
8. Physical Channel Segmentation : The CCTrCH are split to several physical channels,it there are any
9. DTX bit insertion : If no information is to be transmitted by the network, so called DTX (Discontinuous transmission) bits are inserted. T
10. Radio Frame segmentation : When a data block is too long for one radio frame(10ms), it is segmented to several radio frames
11. Physial Channel Mapping : The data has to be mapped to the slot format of a physical channel or to several physical channels if necc

Transport Format Combinations

When multiple transport channels are multiplexed to CCTrCH (Coded Composite Transport Channel) and transmitted in physical channe
channel. Therefore the so called "Transport Format Combination Identifier (TFCI)" is used. In UE and NodeB the value of the TFCI can
4. Rate matching (pucturing) : The physical layer can perform a puncturing of bits to reduce the data rate. the physical layer gets matchin
5. Radio Frame Equalization : If the data block after rate matching is too short for one radio frame,some padding bits are appended
6. Interleaving : Interleaving is used to damage symbol correlation and reduce the impact caused by fast fading and interference of the ch
7. TrCH Multiplexing : This function multiplexes several transport channels to one CCTrCH (Code Composite Transport Channels)
8. Physical Channel Segmentation : The CCTrCH are split to several physical channels,it there are any
9. DTX bit insertion : If no information is to be transmitted by the network, so called DTX (Discontinuous transmission) bits are inserted. T
10. Radio Frame segmentation : When a data block is too long for one radio frame(10ms), it is segmented to several radio frames
11. Physial Channel Mapping : The data has to be mapped to the slot format of a physical channel or to several physical channels if necc

Transport Format Combinations

When multiple transport channels are multiplexed to CCTrCH (Coded Composite Transport Channel) and transmitted in physical channe
channel. Therefore the so called "Transport Format Combination Identifier (TFCI)" is used. In UE and NodeB the value of the TFCI can
- the number of transport channels
- the transport format for every transport block of every transport channel in the combination
This allows the de-multiplexing of CCTrCHs. the TFCI values and the assignment of transport format combination is signaled by RRC durin
The definition of TFCIs runs in the following way.
1. During radio bearer setup or reconfiguration the transport channels to be multiplexed are defined
2. Now each transport channel has its transport format set. One transport format from each transport channel's transport format set build a
care,taking UE radio capabilities into account.
3. Several transport format combinations from a so called "transport format combination set" .Every transport format combination in the
combination identifier TFCI.

B) Radio Tasks:
1. Provision for higher layers with measurements and indications (such as FER, SIR, interference power, and transmission power)
2. Macro-diversity distribution/combination and soft handover execution
3. Frequency and time (chip, bit, slot, frame) synchronization
4. Closed-loop power control
5. Power weighting and multiplexing of physical channels
6. Modulation,spreading,scrambling
7. Scrambling and modualtion

Physical Layer Procedures

The physical layer defines several procedures to control the radio interface on the lowest level. Most of these procedures are triggered and
the following categories:
1. Synchonization procedures : These types of procedures are used for cell search,radio frame/slot and chip synchronization to physical
the UE to the cell timing.
2. Power Control Procedures : One of the most critical issues for CDMA systems is the near-far problem. The solution for this is a very fa
3. Random Access Procedures : Like all known mobile radio access technologies also WCDMA has to use random access mechanism t
shared resources between several UEs an access mechanism with collision risk is used.
4. Radio Measurment : For the mobility handling within the radio network the UE and the Node B have to perform measurements of radio
ratio,interference power,signal power). These measurment are used as criteria for the cell reselection or handover procedures. For the me
frames. In such radio frames some slots are not used for transmission/reception,rather the measuement are then performed.
L2 Functions
L2 includes four sublayers, Medium Access Control (MAC), Radio Link Control (RLC), Broadcast/Multicast Control (BMC) and Pac
Convergence Protocol (PDCP).

I. MAC, The functions of MAC include:

1.Mapping between logical channels and transport channels
2.Selection of appropriate transport format for each transport channel
3.Priority handling between data flows of one UE
4.Priority handling between UEs by means of dynamic scheduling
5.Priority handling between data flows of several UEs on FACH
6.Identification of UEs on common transport channels
7.Multiplexing/demultiplexing of upper layer PDUs into/from transport blocks delivered to/from the physical layer on common transport cha
8. Switching of the transport channel type for a radio berarer(controlled by RRC),means several transport channel types can be assigned t
9.Traffic volume measurement
10.Ciphering/de-chipering for transparent mode RLC
11. Control of random access and CPCH access (e.g. priority classes)
9.Traffic volume measurement
10.Ciphering/de-chipering for transparent mode RLC
11. Control of random access and CPCH access (e.g. priority classes)

L3 Functions
The RRC performs the functions listed below:

1.Broadcast of information related to the non-access stratum (NAS:Core Network)

2.Broadcast of information related to the access stratum (AS)
3.Establishment, maintenance and release of an RRC connection between the UE and UTRAN
4.Establishment, reconfiguration and release of Radio Bearers
5.Assignment, reconfiguration and release of radio resources for the RRC connection
6.RRC connection mobility functions
7.Route selection for the Protocol Data Unit (PDU) of upper layers
6.Control of requested QoS
7.UE measurement reporting and control of the reporting
8.Outer loop power control
9. Security Control
10. Paging
11. Initial cell selection and cell re-selection
12. Arbitration of radio resources on uplink DCH
13. RRC message integrity protection
14. CBS control
UTRAN Interface Protocol - Iub ( RNC-NodeB)
The control plane of the Iub interface

-NBAP (NodeB Application Part) : The

configuration).
-SAAL,AAL 5, ATM : These protocols c

The user plane of the Iub interface ha

plane consists of:

-Frame Protocols : The Frame Protoco

-AAL 2 ,ATM : The frame protocol,that e
-AAL type 2 signaling protocol : The A
-STC, SAAL,AAL 5,ATM : The STC (Si

The physical layer is not standardize

UTRAN Interface Protocol - Iur ( RNC-RNC)

 The control plane of the Iur interface

-RNSAP (Radio Network Subsystem A

covers resource allocation for a UE in a
(SRNS relocation)
- SCCP (Signaling Connection Contro
the S-RNC sets up one SCCP signaling
signaling messages
-MTP 3B,SAAL,AAL5,ATM : These pro

The user plane of the Iur interface ha

-Frame Protocols : The data to and fro

protocols allow traffic management with
-AAL 2 ,ATM : The frame protocol pack
-AAL type 2 signaling protocol : The A
-STC,MTP3B, SAAL,AAL 5,ATM : Thes
Converter) provides functionality for con
signaling bearer of RNSAP of Control P

UTRAN Interface Protocol - Iu ( UTRAN-CN)

The following protocol model is applied

Iu-CS Protocol Stack 1. Iu-CS protocol stack

The control plane for Iu-CS is formed o
-RANAP ( Radio Access Network App
-SCCP (Signaling Connection Contro
CS service.
-MTP 3B,SAAL,AAL5,ATM : Theses pr

The user plane on Iu-CS has to suppor

-Iu UP (User Plane) protocol : The Iu U
conrrection.
-AAL2,ATM : For the data bearer to tran

The transport network control plane

network control plane consisting of:
-AAL type 2 signaling protocol : used
-STC,MTP 3B,SAAL,AAL5,ATM : Thes
 2. Iu-PS protocol stack
The Iu-PS interface is the interface betw
Iu-PS control plane
Iu-PS Protocol Stack -RANAP : The application protocol for I
-SCCP : Provides signaling connection
service. SCCP connections on Iu-PS an
-MTP 3B,SAAL,AAL5,ATM : The signa

The user plane on Iu-PS is competely d

necessary. The UTRAN provides the fol
-Iu UP protocol : As for Iu-CS the Iu UP
-GTP-U (GPRS Tunneling Protocol-Us
the PDP context and sequence number
-UDP/IP : The UDP/IP protocol suite is
vice versa.
-AAL 5,ATM : The ATM adaptation laye
The AAL 5 virtual channels do not need
for the packet transfer. Therefore on Iu

UMTS Protocol Stacks -> Application Part

UMTS system has different application parts depending on interface being used and each application part controls signaling information fo
part,variable fixed part and optional part.
Between nodes, there are three application parts (NBAP,RANAP and RNSAP) to convert and transmit signaling for the control plane and o

1. RANAP (Radio Access Network Applciation Part) : This application part is the Iu interface signaling protocol that contains all the cont
implemented by various Elementatry Procedures (EP). Each RANAP function requires the execution of one or more EP.
The following RANAP functions are defined:
-Relocation & Handover Control : Handles the relocation of RNC for soft handover and hard handover
-RAB Management: Handles the RAB setup,modification characteristic of an existing RAB and clearing a connected RAB
-Iu Release Control : Connected signaling link and the U-Plane resources will be released.
-Paging : Sends paging messages from CN to an idle UE
-UE-CN signaling Transfer : Provides transparent transfer of UE-CN signaling messages that are not interpreted by UTRAN, such as bro
-Security Mode Control : Sets the ciphering on or off by encrypting signaling and user data connection in the radio interface

2. NBAP (NodeB Application Part): This application part is the Iub interface signaling protocol. It is divided into two procedures :
-Common NBAP : Defines the signaling sequence across the common signaling link. Common NBAP defines all the procedures for the lo
management
-Dedicated NBAP : Sequence related to a specific UE signaling in the NodeB. Upon radio link setup procedure,the NodeB assigns a traffi
this mobile is exchanged by Dedicated NBAP function by the dedicated control channel.
The following NBAP functions are defined:
1.Cell Configuration Management ,this function gives the controlling RNC (CRNC) the possibility to manage the cell configuration inform
2.Common Transport Channel Management,this function gives the CRNC the possibility to manage the configuration of common transp
3.System Information Management, this function gives the CRNC the ability to manage the scheduling of System Information to be broa
4.Resource Event Management, this function gives the NodeB the ability to inform the CRNC about the status of NodeB resources.
5.Configuration Alignment ,this function gives the CRNC and the NodeB the possibility to verify and enforce that both nodes have the sa
6.Measurements on Common Resources,this function allows the NodeB to initiate measurements in the NodeB. The function also allow
-Common NBAP : Defines the signaling sequence across the common signaling link. Common NBAP defines all the procedures for the lo
management
-Dedicated NBAP : Sequence related to a specific UE signaling in the NodeB. Upon radio link setup procedure,the NodeB assigns a traffi
this mobile is exchanged by Dedicated NBAP function by the dedicated control channel.
The following NBAP functions are defined:
1.Cell Configuration Management ,this function gives the controlling RNC (CRNC) the possibility to manage the cell configuration inform
2.Common Transport Channel Management,this function gives the CRNC the possibility to manage the configuration of common transp
3.System Information Management, this function gives the CRNC the ability to manage the scheduling of System Information to be broa
4.Resource Event Management, this function gives the NodeB the ability to inform the CRNC about the status of NodeB resources.
5.Configuration Alignment ,this function gives the CRNC and the NodeB the possibility to verify and enforce that both nodes have the sa
6.Measurements on Common Resources,this function allows the NodeB to initiate measurements in the NodeB. The function also allow
7.Radio Link Management, this function allows the CRNC to manage radio links using dedicated resources in a NodeB.
8.Radio Link Supervision ,this function allows the CRNC to report failures and restorations of a radio link.
9.Compressed Mode Control,this function allows the CRNC to control the usage of compressed mode in a NodeB.
10.Measurements on Dedicated Resources,this function allows the CRNC to initiate measurements in the NodeB. The function also allo
11.DL Power Drifting Correction, this function allows the CRNC to adjust the DL power level of one or more radio links in order to avoid D
12.Reporting of General Error Situations, this function allows reporting of general error situations.

3. RNSAP (Radio Network Subsystem Application Part) : This application part is the Iur interface signaling protocol that controls signali
handover. The RNSAP protocol has the following functions:
-Radio Link Management : Allows the SRNC to manage radio links using dedicated resoruces in a DRNC.
-Physical Channel Reconfiguration : DRNC reallocates the physical channel resources for a radio link
-Radio Link Supervision: Allows DRNC to report failures and restoration of a radio link
-DL Power Drifting Correction : Allows SRNC to adjust the DL power level of one or more radio links in order to avoid DL power drifting b
-CCCH Signaling Transfer : Allows the SRNC and DRNC to pass information between UE and SRNC on a CCCH controlled by the DRNS
-Paging : Allows the SRNC to page a UE in a URA
-Relocation Execution: Allows the SRNC to finalize a relocation previously prepared via other interfaces.

4. ALCAP (Access Link Control Application Part) : This application part is the signaling protocol that provides the signaling capability to
words, ALCAP setup transport bearer such as AAL2 path between different nodes interfaces (Iu,Iur,Iub) in the UTRAN. The transport beare
Control Plane (NBAP,RANAP,RNSAP). And then,data bearer is setup by the ALCAP protocol.The use of the ALCAP is dependent on the ty
there is no dynamical setup and release for signaling bearers.

Data bearers have to be setup and released with ALCAP, when they are not pre-configured. In this case the setup runs in the following ma
The setup or release of a bearer is always controlled by an application protocol. But to avoid the restriction to a single transport system, the
the application protocol can control the bearer via abstract parameters (QOS parameters) only. This principle is the same as for BICC (Bea
protocol starts a procedure to the destination node.

After the application protocol triggered the procedure,the ALCAP, that is specific to the bearer to be setup ,performs all necessary procedu
successful bearer setup, the application protocol procedure can be finished, and the application can be informed to start the data stream tr
e User Equipment UE.

ket Switched PS (i.e. GPRS) domain

t is responsible for serving the radio interface. Some of the tasks of the Mobile Equipment ares CDMA coding and
ents,Ciphering and authorization,Mobility management and equipment identification.

rminal equipment. It supports call handling,contains security parameters,user-specific data e.g. telephone directory
pdated e.g. via SMS or cell broadcasting.

n for authentication and chiphering for circuit and packet switched applications,PLMN selector and HPLMN search
.
es etc.

in, which is labelled Iu-PS, and to the cs domain, which is called Iu-CS. In both cases, ATM is used as transmission
erface.

ndover situations, where a UEs active cells are under the control of more than one RNC. One RNC is responsible for

lling information.
(RRM) and the control of itself and the connected NodeB (O&M functionality). It is connected to the CN , CS domain via Iu(CS) interface and to the PS dom

ws,
hat is connected with the NodeB serving the cell. The tasks of the C-RNC covers the following areas:

he NodeB).This means the C-RNC of a cell is responsible for all lower layer funcions related to the radio technology

RNC).The existence of a serving RNC does not imply that the UE is camped on a cell belonging to the S-RNC.The serving RNC handles all higher layer fun

ation/modification or release of radio resources,for Outer Loop Power Control and for Handover decisions/initiation.
oward the CN. It decides to add or remove cells in the Soft Handover. The S-RNC is in most cases (but not always)
. It can be re-allocated to another RNC with the S-RNS reallocation procedure.

and corresponding RANAP signalling to/from the core network per UE. The S-RNC terminates the RRC signalling

ed to a cell, that does not belong to the S-RNC. This means the UE is connected with a cell controlled by a RNC different
eB is a physical unit for implementing a UMTS radio transmission. Depending on the sectoring of the cells ,one (omni) cell or multiple (sector) cells can be s
rviced by a Node B in UMTS.

e B can be used for Frequency Division Duplex (Uplink and Downlink separated by different frequency bands),Time division Duplex (Uplink and Downlin
ion. A Node B converts user and signalling information received from the RNC for transport via the radio interface,and in the opposite direction. Node Bs a
nal to noise ratio (SIR) of the User Equipment ,compares the value with a predefined one and instructs the UE to control its transmission power. The NodeB
ks and determines the Frame Error Rate (FER). The following are examples of NodeB functions:

o Channel functions: Transport to physical channel mappings. Encoding/Decoding Spreading/De-spreading user traffic and signalling.
nterface management. Controlling Uplink and Downlink radio paths on the Uu Air Interface,Baseband to RF conversion,Antenna multi-coupling,
odeB SofterHO,Power Control,Quality and signal strength measurements
Processing,Interfacing with M2000 and RNC for alarm and control (Operations and Maintenance) functions.
lar Transmission management. Managing ATM switching and multiplexing over the Iub interface. Control of AAL2/AAL5 connections. Control
physical transmission interfaces E1, PDH, SDH or microwave.
k is possible,is sub-divided into National Service Areas.

C) and Country Code (CC). The National Service Area is sub-divided into one or more PLMN Service Areas.

and Country Code (CC). The National Service Area is sub-divided into one or more MSC and SGSN Service Areas.

SGSN (PS-domain). MSC and SGSN Service Area may differ, but they are on the same hierachical level. The MSCs and

VLR) of UMTS. A Location Area is world-wide uniquely identified by its Location Area Identity LAI

of a Location Area i.e. one LA may contain one or more RAs. The RA is the most precise UE information, which is
dentity. The RA is sub-divided into the Cell-Areas.

he PLMN (in the RNC). The cell is world-wide uniquely identified by the Cell Global Identity (CGI)

geographical and physical entities of UTRAN are described as follow,

t of a MCC(mobile country code) and a MNC(mobile network code). MCC and MNC are allocated by ITU-T and are specified within ITU-T E212.

for CS and the concept of Routing Area for PS.

her with the PLMN-ID the RNC-ID is unique world wide. The RNC-ID will be used to address a RNC via Iu,Iur and Iub

the RNC-ID the Cell-ID forms the UTRAN cell ID

l-ID to local cell identifier

with a SAI(service area id):

RA)
 two types of identifiers according to the point of generation of the identifier:

y the core network. In detail there are IMSI,TMSI and P-TMSI (and IMEI)
NTIs). This means they are allocated to the UE for the time of the need. After the last procedure the identifiers are released.

Country Code,MCC (3 digits) + Mobile Network Code,MNC (2-3 digits)+Mobile Subscriber Identification Number,MSIN. The total length of the IMSI is less t

ity. This TMSI is allocated to an UE by VLR and stored in the U-SIM. It has only local significance i.e. within the area controlled by a VLR. The TMSI consist

the U-SIM. The P-TMSI consists of 3 bytes,which are operator-dependent.

he EIR. The IMEI(15 digits) consists of a Type Approval Code TAC (6 digits),the Final Assembly Code FAC(2 digits)which

by the RNCs. Fours RNTI types exists:

it has to be reallocation,too.The S-RNTI is used by the S-RNC to address the UE, by the D-RNC to identify the UE to the

d for the first cell access (at cell change) at existing RRC connection and for UTRAN originating Paging including

ed as an in-band UE identifier in all DCCH/DTCH common channel messages on Uu despite the first access

he UE to the D-RNC. It is never used on Uu.

 The communication between the different domains can be divided according to their functions. The UTRAN has the functions to provide acces
transport of signalling messages and user data between UE and CN. Therefore we can distiguish three types of signalling between UE,UTRA

1. Access Stratum(AS) : The Access Stratum covers all signalling exchange used to control the access of an UE to the network. Access Stra
UTRAN and between UTRAN and CN. The difference between the access stratum UE-
UTRAN and UTRAN-CN is ,that the UTRAN-CN access stratum shall be independent of the radio technology used in UTRAN. This
enables the CN to support several different radio access technologies.

2. Transport Stratum: The Transport Stratum protocols and messages have the task to transport higher layer PDUs (Protocol Data Unit)
and user data. Because UTRAN has the task to transparently transport data between UE and CN,there will be transport stratum
messages between UE and UTRAN and between UTRAN and CN.

3. Non-Access Stratum (NAS) : The Non-Access-Stratum covers all messages of higher layers and user data, that do not deal with
access or transport tasks.This cover pure application control (application stratum), service request and control (serving stratum)
,handling of subscription data and subscriber specific services (home stratum).

MTS network is split into the CN,UTRAN and the UE. CN and UTRAN are connected via Iu interface,UTRAN and the UE via Uu(radio) interface. User data
ation (including requesting the service,controlling different transmission resources,handover etc) are exchanged between the CN and the UEs using the Ra
s Stratum (AS).

gher layer protocols of the Non-Access Stratum(NAS) handle control aspects e.g. (GPRS)Mobility Management (G)MM,Connection Management (CM) or S
ures (of Rel. '99) are in most cases unchanged compared to the GSM Phase 2+
ures. The radio and Iu protocols contain mechanism for transparent NAS message transfer. So-called Direct Transfer (DT) procedures are
n the Iu and radio protocols for these these transparent NAS message transfer.
otocol structures of the UTRAN interfaces are designed in horizontal layers and vertical planes. The general protocol model describes these layers and p
odularity of this model allows changing parts of the protocol structure in the future,if neccessary,while other parts remain intact.

ansport system used within UTRAN is ATM. There is difference between the usage of ATM and the use PCM lines in a GSM-BSS. ATM supports
nt types of bearer service labelled AAL type 1,AAL type 2, AAL type 3/4 and AAL type 5. In UTRAN only AAL type 2 and AAL Type 5 are used. Bearers of AA
eans before a AAL type 2 virtual channel can be used,there might be signalling between the corresponding ATM switches. This behavior results in a new pr
and release occur.

ontal Layer:
eneral protocol model consists of two main horizontal layers- the Radio Network Layer and Transport Network Layer.All UTRAN related issues
ible in the Radio Network Layer only.The Transport Network Layer is used for UTRAN,offering transport technologies.It is without any UTRAN
c requirements.
sport Network Layer : The Transport Network Layer consists of all protocols used for the transport network solution. This includes the physical
nd its transport frame layer,also the bearer service protocols are included.
o Network Layer : The Radio Network Layer contains all protocols,that are specific to the radio access and transport stratum. Also all other data
s, to be transported through UTRAN, belong to this layer.

al Plane:
is also a vertical structure, the elements of this vertical structure are planes. A plane principle is protocol stack,more than one plane can coexist
eachother. The general protocol model consists of three vertical planes- the Control Plane,the User Plane and the Transport Network Control

Plane: The user plane supports the data streams for user data. Therefore the data streams are packed into frame protocols. These frame
ols will be transmitted via data bearers. In contrast to the signalling bearers of the control plane,the data bearer can require to be set up with
signalling.
ol Plane: The control plane consists of all application protocols that are used for radio network controlling. To transport the messages of an
ation protocol,one or several signaling bearers,provided by the transport network are neccesary. The Control Plane is used for all control
ng,which is UMTS-specific. It includes the Application Protocols (i.e. RANAP,RNSAP and NBAP) and the signaling bearer for transport the
ation Protocol messages.
port Network Control Plane: The transport network control plane contains the ALCAP (Access Link Control Application Part). The ALCAP
ols are used to set up and release the data bearers of the user plane. Also ALCAP messages require a signaling bearer for transmission. It is
cessary to use the ALCAP for all data bearers. Expecially the transport network control plane is not necessary when pre-configured bearers only
ed. The Transport Network Control Plane is used for all control signaling within the Transport Layer. It contains no Radio Network Layer
ation.

ansport Network Control Plane acts as plane between the Control Plane and User Plane, it enables the Application Protocol in the Control Plane
otal independent of the technology selected for data bearer in the User Plane.
 Control Plane

ort plane is the setup of a data bearer for the user plane

n addition ,the CS control plane is used for controlling supplementary services and it can be used for the exchange of short messages. It contains of followin
radio interface. Therefore it performs spreading,scrambling.modulation,channel conding,rate matching etc.
rol of random access and the multiplexing/de-multiplexing of different UEs onto shared radio resources.
iabilty modes for every radio bearer. These modes are : Acknowledge (AM),Unacknowledge(UM) and Transparent (TM).
erforms all higher layer tasks related to the access stratum on the air interface (e.g. radio bearer setup)
e CS service these are: MM (Mobility Management),CC (Call Control),SS(Supplementary Services) and SMS (Short

l tasks related to transport stratum for control signaling and access stratum between UTRAN and CN. It is the

sh a singling connection for a UE. So the UE can then be identified by the signaling connection and not by an explicit
ome protocols supporting the user data transfer. In the lowest layers there are the same protocols as for the control plane. The following protocols involved
ane. The same basic stack is used for the user plane.
services (switched channels). These data streams are directly input to the RLC

tion layer provides a bearer channel (virtual channel of AAL type 2) with certain QOS gurantees. Additonally the AAL 2 cirtual channel includes time stamps

different stages of user data stream support.

Iub interface (<>NBAP). On the other hand, the real time AAL 2 is used for relaying UE- data and UE-signaling
C and MSC.
 User Plane -PS

s for PS services. In fact these special protocols are on the higher layers,so that the lower layer will prove to be the same as for the CS services.

PS and CS. UMTS has been designed to support both types of services, so that there are no special protocols.
he Iu interface towards the MSC.
ng conenction to the SGSN in the core network. RANAP handles all signaling transport and access related tasks.
protocols. Because there are essential differences how to handle a packet switched service request, the PS core
he SM (Session Management) protocol is used. The SMS is in fact the same as for CS.

t differences.

ernet). These external data network have their own special network protocols ( e.g. internet) . These external data
nnected with such an external network, the UE has to send packets of this special network protocol, for the UMTS
ed Packet Data Protocol (PDP). It is the task of the UMTS network to provide a tunnel (PDP context) for transparent

packet header. This shall increase the efficiency of the air interface usage.

n Iu. GTP-U organizes addressing and identification of the originator and destination of the data between RNC and SGSN.
ess unreliable transport service. In principle only routing is performed with UDP/IP
 Uu interface is the interface between User Equipment (UE) and UMTS Terrestrial Radio Access Network (UTRAN) and it is the most i

The radio interface (Uu) is layered into three protocol layers:

-the physical layer (L1)
-the data link layer (L2)
-the network layer (L3).

The layer 1 supports all functions required for the transmission of bit streams on the physical medium. It is also in charge of measurements fu
layers, for example, Frame Error Rate (FER), Signal to Interference Ratio (SIR),interference power, transmit power, It is basically compose
transport channel entity, and a
physical channel entity.

The layer 2 protocol is responsible for providing functions such as mapping, ciphering, retransmission and segmentation. It is made of four s
RLC (Radio Link Control), PDCP (Packet Data Convergence Protocol) and BMC (Broadcast/Multicast Control).

The layer 3 is split into 2 parts: the access stratum and the non access stratum. The access stratum part is made of RRC (Radio
Resource Control) entity and duplication avoidance entity. The non access stratum part is made of CC, MM parts.The RRC functions of
L3 are implemented by RNC, and the MM and CC functions of L3 are implemented by CN.

The protocol layers are located in the UE and the peer entities are in the node B or the RNC.

Transport
Transport Format
Format Combinations
Combinations

ayer has the following steps,that can be identified with the presented functional blocks:
sed for error detection
d after the CRC is appended. if the resulting data block is too long (e.g does not fit into one radio frame) a segmentation is performed afterwards
terference.UTRAN FDD and TDD offer four different channel coding schemes as FEC(Forward Error Correction). These

e. the physical layer gets matching parameters from RRC layer

padding bits are appended
fading and interference of the channel
posite Transport Channels)

transmission) bits are inserted. This is only for downlink

ed to several radio frames
several physical channels if neccesary

nd transmitted in physical channels,there has to be an indication which transport formats are used for every transport
NodeB the value of the TFCI can be translated into:
 and transmission power)

ese procedures are triggered and mastered by higher layers like MAC and RRC. The procedures can be devided into

d chip synchronization to physical channels. In the TDD mode also timing advance procedures are used to synchronize

m. The solution for this is a very fast power control mechanism,using a closed control loop ( UE<>NodeB<>UE)
use random access mechanism to establish a radio connection between an UE and the Network. BNut also for

o perform measurements of radio signal quality (bit error rate) and radio signal strength (signal interference
andover procedures. For the measurments the UE physical layer has uses so called compressed mode mode radio
are then performed.

Multicast Control (BMC) and Packet Data
II. RLC, The functions of RLC include:
1. Segmentation, reassembly, concatenation, padding and transfer of user data
2. Flow control Error correction, in-sequence delivery of upper layer PDUs and duplicate detection
3. Sequence numbers check
4. Protocol error detection and recovery
5. Ciphering
6. Suspend/resume function

III. PDCP, The functions of PDCP include:

1.Header compression and decompression of IP data streams at the transmit and receive entities resp
al layer on common transport channels 2.Transfer of packet oriented user data using RLC transparent,unackowledge or acknowledged mode
channel types can be assigned to one radio bearer 3.Forwarding of PDCP-SDUs from NAS to RLC, and multiplexing of different RBs to the same RLC en

IV. BMC ,The functions of BMC include:

1.Storage of cell broadcast messages
2.Traffic volume monitoring and radio resource request for CBS
3.Scheduling of BMC messages
4.Transmission of BMC messages to UE
5. Delivery of cell broadcast messages to upper layer (NAS)
 IV. BMC ,The functions of BMC include:
1.Storage of cell broadcast messages
2.Traffic volume monitoring and radio resource request for CBS
3.Scheduling of BMC messages
4.Transmission of BMC messages to UE
5. Delivery of cell broadcast messages to upper layer (NAS)

ontrol plane of the Iub interface contains the following protocols:

P (NodeB Application Part) : The NBAP protocol is the application protocol of the Iub interface. It organizes all controlling tasks between RNC and NodeB
uration).
,AAL 5, ATM : These protocols constitute the signalling bearer for the NBAP messages.

ser plane of the Iub interface has to transfer the downlink and uplink data to and from the UE. Therefore different frames are defined in the same
consists of:

e Protocols : The Frame Protocols encapsulate the UE data (UL&DL) on the Iub interface
2 ,ATM : The frame protocol,that encapsulate the UE data,are transported over AAL 2 virtual channels of ATM. These AAL 2 virtual channels have to be set
ype 2 signaling protocol : The AAL type 2 SP provides the messages and functions to setup, release and modify AAL 2 virtual channels.
SAAL,AAL 5,ATM : The STC (Signaling Transport Converter),SAAL,AAL 5 and ATM provide the signaling bearer for AAL type 2 signaling protocol.

hysical layer is not standardized. it is up to the operator and verndor to choose an appropiate physical transmission system.
ontrol plane of the Iur interface contains the following protocols:

AP (Radio Network Subsystem Application Part) : The RNSAP protocol is responsible for the communication between S-RNC and D-RNC. This
resource allocation for a UE in a cell of the D-RNC,soft handover procedures and procedures to transfer the S-RNC functionality to a D-RNC
S relocation)
P (Signaling Connection Control Part) : The SCCP is used to set up a signaling connection between S-RNC and D-RNC for the UE. This means
RNC sets up one SCCP signaling connection for every D-RNC and UE. The signaling connection will be used for fast identification of the UE in
ng messages
3B,SAAL,AAL5,ATM : These protocols form the signaling bearer used for the RNSAP protocol messages.

ser plane of the Iur interface has the tasks to transport uplink and downlink data for the UE connected to a D-RNC. This tasks requires the follow

e Protocols : The data to and from the UE will be encapsulated into frame. These frames are defined by so called frame protocols. These frame
ols allow traffic management with in-band signaling
2 ,ATM : The frame protocol packets are transmitted via Iub using AAL 2 virtual channels. So AAL 2 ,ATM form the data bearer on the Iub interface.
ype 2 signaling protocol : The AAL type 2 SP provides the messages and functions to setup, release and modify AAL 2 virtual channels.
MTP3B, SAAL,AAL 5,ATM : These protocols provide the signaling bearer for the AAL type2 signaling protocol. The STC(Signaling Transport
rter) provides functionality for congestion handling and load control. The protocol suite MTP3B,SAAL,AAL5 and ATM can be shared with the
ng bearer of RNSAP of Control Plane

lowing protocol model is applied to the UTRAN interfaces Iu, there are differences between Iu-CS toward the CS-core network domain and Iu-PS towards t

S protocol stack
ontrol plane for Iu-CS is formed out of the following protocols:
AP ( Radio Access Network Application Part) : The RANAP protocol is responsible for all access and signaling transport related tasks. It is the application
P (Signaling Connection Control Part) : The SCCP is used to setup signaling connection between RNC and MSC. There will be one and only one SCCP c
vice.
3B,SAAL,AAL5,ATM : Theses protocols provide the signaling bearer for RANAP/SCCP messages

ser plane on Iu-CS has to support the transfer of real time CS data streams. Therefore the Iu-CS plane has the following protocols:
(User Plane) protocol : The Iu UP protocol is used to provide additional support functions for CS data streams on Iu. These functions can be : timing cont
ction.
,ATM : For the data bearer to transport the data streams the AAL 2 virtual channels are used.

ansport network control plane is necessary ,because AAL2 virtual channels need to be setup and released. The protocol suite on the transport
k control plane consisting of:
ype 2 signaling protocol : used to setup ,modify and release AAL 2 virtual channels.
MTP 3B,SAAL,AAL5,ATM : These protocols provide the signaling bearer for the AAL type 2 signalling protocol messages.
 S protocol stack
-PS interface is the interface between RNC and SGSN. The control plane of Iu-PS is similar to the Iu-CS plane. It consists of:
control plane
AP : The application protocol for Iu-CS and Iu-PS
P : Provides signaling connection on Iu-PS. There will be one and only one SCCP connection between RNC and SGSN for every UE using PS
e. SCCP connections on Iu-PS and Iu-CS do not affect each other.
3B,SAAL,AAL5,ATM : The signaling bearer for SCCP/RANAP

ser plane on Iu-PS is competely different to the user plane of Iu-CS. This is because the traffic to and from SGSN is PS, so routing layer are
sary. The UTRAN provides the following protocols on the Iu-PS user plane:
protocol : As for Iu-CS the Iu UP protocol can provide additional support functions for the data stream.
U (GPRS Tunneling Protocol-User Plane): GTP-U provides a frame for the user data to be transported. In a GTP-U frame a reference number for
P context and sequence numbers for the data are contained.
P : The UDP/IP protocol suite is used as network layer between RNC and SGSN. The task of these protocols is to route from RNC to SGSN and
ersa.
5,ATM : The ATM adaptation layer of type 5 is used as bearer for the packets of IP/UDP/GTP-U.
AL 5 virtual channels do not need to be set up in a dynamic manner. Rather the operator is expected to pre-configure the AAL 5 bearer to be used
e packet transfer. Therefore on Iu-PS there is no need for a transport network control plane. no bearer set up with explicit signalling is necessary.

RANAP
RANAP

t controls signaling information for the call setup between nodes. Basically these applications message structure is similar to the SS7 signaling format, cons

gnaling for the control plane and one application part (ALCAP) to set up the transport bearer for the user plane.

protocol that contains all the control information specified for the Radio Network Layer. The fucntions of RANAP are
ne or more EP.

a connected RAB

erpreted by UTRAN, such as broadcast information,direct transfer etc.

n the radio interface

ed into two procedures :

fines all the procedures for the logical operation and maintenance of the Node-B, such as configuration and fault

edure,the NodeB assigns a traffic termination point to control UE signaling. All of the subsequent signaling related to

nage the cell configuration information in a NodeB.

e configuration of common transport channels in a NodeB.
of System Information to be broadcast in a cell.
status of NodeB resources.
orce that both nodes have the same information on the configuration of the radio resources.
e NodeB. The function also allows the NodeB to report the result of the measurements.
aling protocol that controls signaling transfer between two RNC (SRNC and DRNC) in order to support the inter RNC soft

C.

order to avoid DL power drifting between radio links

n a CCCH controlled by the DRNS

ovides the signaling capability to establish,release and maintain AAL2 connections by a series of ATM VCCs. In other
the UTRAN. The transport bearer in the User Plane are setup first sending signals by the Application Protocol in the
he ALCAP is dependent on the type of bearer to be used. The signaling bearers are usually pre-configured. This means

he setup runs in the following manner:

n to a single transport system, the application protocols shall not be specific to a certain transport solution. Therefore
ple is the same as for BICC (Bearer Independent Call Control). to trigger the set up of a bearer first the application

,performs all necessary procedures to configure the bearer. When the application part receives the notification of a
formed to start the data stream transmission.
via Iu(CS) interface and to the PS domain via Iu(PS) interface. Signalling and data

nology

rving RNC handles all higher layer functions related to radio access and

ling

ent
cell or multiple (sector) cells can be serviced by a Node B. Generally,up to six cells

division Duplex (Uplink and Downlink in different timeslots) or dual mode

d in the opposite direction. Node Bs are involved in power control,NodeB measures
rol its transmission power. The NodeB also measures the quality and strength of

raffic and signalling.

on,Antenna multi-coupling,

AL5 connections. Control

nd

pecified within ITU-T E212.

eased.

N. The total length of the IMSI is less than 15 digits

controlled by a VLR. The TMSI consists of 4 bytes, which are operator-dependent.

ich

the
AN has the functions to provide access links between UE and UTRAN and
ypes of signalling between UE,UTRAN and CN as follows,

of an UE to the network. Access Stratum messages occur between UE and

ology used in UTRAN. This

r layer PDUs (Protocol Data Unit)

will be transport stratum

er data, that do not deal with

ontrol (serving stratum)

UE via Uu(radio) interface. User data (radio access bearer services) and control
een the CN and the UEs using the Radio protocols and the Iu protocols of the

M,Connection Management (CM) or Session Manangement (SM) tasks. The NAS

(DT) procedures are

 ol model describes these layers and planes as logically independent of each other.
ain intact.

GSM-BSS. ATM supports

d AAL Type 5 are used. Bearers of AAL type2 can be set up with explicit signalling.
hes. This behavior results in a new protocol model, where protocols for user bearer

ll UTRAN related issues

It is without any UTRAN

This includes the physical

stratum. Also all other data

han one plane can coexist

ansport Network Control

tocols. These frame

quire to be set up with

rt the messages of an
used for all control
arer for transport the

ion Part). The ALCAP

er for transmission. It is
re-configured bearers only
dio Network Layer

otocol in the Control Plane

short messages. It contains of following important protocol layer as follows;

M).
ane. The following protocols involved into the user data transport,

cirtual channel includes time stamps in the transport frames. This allows

g
me as for the CS services.

GSN.
etwork (UTRAN) and it is the most important interface in the UMTS system.

is also in charge of measurements function consisting in indicating to higher

smit power, It is basically composed of a layer 1 management entity, a

nd segmentation. It is made of four sublayers: MAC (Medium Access Control),

ontrol).

t is made of RRC (Radio

, MM parts.The RRC functions of

on is performed afterwards
se
e

er of user data
ayer PDUs and duplicate detection

t the transmit and receive entities respectively

nackowledge or acknowledged mode
g of different RBs to the same RLC entity
lling tasks between RNC and NodeB (e.g. code allocation,transceiver

ent frames are defined in the same way as on the Iur interface. The user

AAL 2 virtual channels have to be set up first

L 2 virtual channels.
AAL type 2 signaling protocol.

ission system.
 en S-RNC and D-RNC. This
unctionality to a D-RNC

RNC for the UE. This means

identification of the UE in

RNC. This tasks requires the following protocols

me protocols. These frame

a bearer on the Iub interface.

L 2 virtual channels.
TC(Signaling Transport
can be shared with the

e network domain and Iu-PS towards the PS-core network domain.

sport related tasks. It is the application protocol of the Iu-CS interface

here will be one and only one SCCP connection UTRAN-MSC for every IE using

ing protocols:
. These functions can be : timing control,data rate control,backward error

otocol suite on the transport

ges.
sists of:

N for every UE using PS

S, so routing layer are

frame a reference number for

ute from RNC to SGSN and

he AAL 5 bearer to be used

icit signalling is necessary.

NBAP

milar to the SS7 signaling format, consisting each message of mandatory fixed
soft

ns
Mapping of UE state to 3GPP Specifications
After UE switch on, there are two basic operational modes of a UE, idle mode and connected mode.The connected mode can be further d
states,which dene what kind of physical channels a UE is using. The mapping of UE state to 3GPP speciafication is shown below:

UE Switch on

UE Idle UE Connected GSM Connected

3GPP TS 25.304 3GPP TS 25.331 GSM TS 04.18

UE Idle
GSM Idle Cell_DCH
3GPP TS 25.304
GSM TS 05.08 3GPP TS 25.331
3GPP TS 25.331

Cell_FACH
3GPP TS 25.304
3GPP TS 25.331

Cell_PCH
3GPP TS 25.304
3GPP TS 25.331

URA_PCH
3GPP TS 25.304
3GPP TS 25.331

RRC Tasks and Functions

The RRC protocol is the application part for the UMTS radio access technology. This means all controlling radio tasks are in the responsib
-broadcasting of system information for NAS stratum
-establishment,maintenance and release of RRC signaling between UE and UTRAN connections
-establishment,reconfiguration and release of radio bearers
-RRC connection mobility functions
-Quality of Service (QOS) control
-UE measurement reports
-outer loop power control
-security control
-paging
-Initial cell selection and reselection
-transport of NAS stratum control messages

With all these tasks the RRC protocol belongs to the access stratum when the radio oriented control tasks are performed and it
Usage of Radio Bearer by the RRC protocol
The RRC protocol uses the radio bearer service provided by the layer 1 and layer 2 of the UMTS radio interface. The radio b
The radio bearers 0,1,2,3,4 are pre-assigned for exclusive RRC usage. The following is speified:
-RB0 : The radio bearer 0 shall be used for all CCCHs. The CCH in the uplink is mapped to the RACH with RLC transparen
FACH with RLC unacknowledged mode.
-RB1 : The radio bearer 1 is for all DCCH messages with RLC unacknowledged mode
-RB2 : The radio bearer 2 is used for all DCCH messages in RLC acknowledged mode, but not for RRC messages that tran
-RB3 and optional RB4 : These two radio bearers shall be used for RRC messages carrying NAS messages on DCCH in R

The radio bearers 5,...,31 can be used with explicit radio bearer set up for all purposes, e.g. traffic channels or control chann
For RRC messages the protocol specified which RLC mode and with this which radio bearer can be chosen for transport of

RRC Modes and State Transitions including GSM

UTRA RRC Connected Mode

URA_PCH CELL_PCH

CELL_DCH CELL_FACH

Release RRC Release RRC

Connection Connection

Establish RRC Establish RRC

Connection Connection

(UE camps on UTRAN cell)

Idle Mode

The RRC protocol is an application part (Radio Resource Management) and transport protocol (NAS message transport). Therefore the R
The RRC state definiton describes the RRC protocol behavior as a nested set of stated. Two main states are defined:
The RRC protocol is an application part (Radio Resource Management) and transport protocol (NAS message transport). Therefore the R
The RRC state definiton describes the RRC protocol behavior as a nested set of stated. Two main states are defined:
1. UTRA Idle Mode : In UTRA idle mode, the UE has no signaling relationship with the UTRAN. In this case the idle mode procedures hav
UE is switched on, it searches for PLMNs and cells and listen to the broadcasted system information of selected cells

2. UTRA RRC Connected Mode : In the connected mode the UE has a signaling connection with the UTRAN. The setup of this signaling
connection set up). This procedure is the transistion from idle to connected mode. When the RRC connection is released, the connected m

For multi-mode mobile phones (e.g. UMTS,GSM/GPRS) the RRC states can be combined with the radio resource management st
1. Idle Mode : The idle mode of GSM/GPRS has the same meaning as the idle mode of UMTS. The only difference is, that the UE is cam
2. GSM conected mode : In GSM the RR (Radio Resource Layer) performs the radio management. This protocol can setup a RR connec
When such a connection exist,the UE is in GSM connected mode. A GSM-DCCH is allocated for the UE in this case.
3. GPRS packet transfer mode : In GPRS the radio resources are allocated for a mobile temporary only. Such a temporary resource is c
mobile is granted a temporary block flow ,the mobile is in GPRS packet transfer mode (GPRS-RLC state)

With a multi-mode UE it shall be possible to perform in-service-transitions between the different Radio Access Technology (RAT).Therefor
handover from UTRA connected mode to GSM connected mode and vice versa. A transistion from UTRA connected mode to GPRS packe
packet transfer in UMTS, making a cell reselection to a GPRS cell and getting a GPRS temporary block flow.

RRC Mode Description

RRC Idle Mode
When a UE is switched on, it enters the RRC idle mode. In the RRC idle mode, there is no connection on the access stratum level betwee
the UE, it must use non-access stratum identifiers, such as IMSI or TMSI and LAI.

In the RRC idle mode, the UE monitors the BCCH, and when it is registered to the CN, it also listens to paging occasions on its PICH.

The transition from the RRC idle mode to the RRC connected mode can only be initiated by the UE by sending the "RRC Connection Req
UE and UTRAN, the UE is identified by a Radio Network Temporary Identity (RNTI). As can be seen in the
figure above, the UE can be in one of four sub-states, when it is in the RRC connected mode. The sub-states depend on the connectivity l
instance, the DCHs are not available in the sub-states CELL_PCH and CELL_URA. The UE leaves the RRC idle
mode when sending the RRC Connection Request message to UTRAN. When UTRAN accepts the UEs request, the UE enters either the

RRC Connected Mode

The RRC connected Mode can be further decomposed into four different states. These four sub-states describe, on which level the UE is
(cell state) or on URA level (URA state). On the other hand any UE can have a DCH or a FACH or no transport channel for control messag

CELL_DCH
In this sub-state, dedicated physical channels are allocated to the UE. DCCH and if configured DTCH information can be transmitted.
allocated to this UE. UTRAN knows the active set cells for the radio links and thus the location of the the UE. Also downlink shared channe
BCCH, if it owns specific capabilities). The cell system information is broadcasted on the FACH. The UE reads the cell system information
system information. This state can only be entered from Cell_FACH by setting up a DCH. When the last DCH is released the UE enters C

In the CELL_DCH state the UE shall perform the following actions:

if DCCH and DTCH are available:
- read system information broadcast on FACH (applicable only to UEs with certain capabilities and camping on FDD cells);
- perform measurements process according to measurement control information

CELL_FACH
This state was introduced for traffic situations, where only small amounts of data have to be transmitted. This is the case when only higher
transmitted. In this case, an exclusive allocation of one physical channel to the UE would result in a waste of resources. Only common tran
Each UE must be explicitly addressed, for instance by the RNTI. It has to monitor the FACH permanently in the downlink, not to miss user

In the uplink, it uses the shared transport channels for user data transfer, such as the RACH. The UE is only connected to one cell, and th
responsible for cell re-selection. By listening to the cell system information from the BCCH, it gains all relevant measurement qualities, thr
learned from the BCCH. The UE receives
RRC messages on the BCCH, CCCH and DCCH channels. Due to the discontinuous type of traffic, UTRAN can command the UE to perf

In the CELL_FACH state the UE shall perform the following actions:

if the UE is "in service area":
- DCCH and DTCH are available
- perform cell reselection process
Each UE must be explicitly addressed, for instance by the RNTI. It has to monitor the FACH permanently in the downlink, not to miss user

In the uplink, it uses the shared transport channels for user data transfer, such as the RACH. The UE is only connected to one cell, and th
responsible for cell re-selection. By listening to the cell system information from the BCCH, it gains all relevant measurement qualities, thr
learned from the BCCH. The UE receives
RRC messages on the BCCH, CCCH and DCCH channels. Due to the discontinuous type of traffic, UTRAN can command the UE to perf

In the CELL_FACH state the UE shall perform the following actions:

if the UE is "in service area":
- DCCH and DTCH are available
- perform cell reselection process
- perform measurements process according to measurement control information
- run timer T305 (periodical cell update)
- listen to all FACH transport channels mapped on S-CCPCH assigned to this UE
if the UE is "out of service area":
- perform cell reselection process
- run timers T305 (periodical cell update), and T317 (cell update when re-entering "in service") or T307 (transition to Idle mode)

CELL_PCH and URA_PCH

The remaining two sub-states CELL_PCH and URA_PCH were introduced to cope with inactive data users. Just think about users, wh
transmission takes place. If this is the case, access stratum resources can be released when moving in one of the two states. In both state
the UE wants to transmit something, it must move first internally to the sub-state CELL_FACH.

The UE listens to the cell system information, broadcasted on the BCCH. It performs measurements accordingly, and is responsible for ce
transmit data to the UE, it must be paged first. Therefore, the UE has to monitor paging occasions on its PICH, i.e. it receives RRC messa

CELL_PCH In this sub-state, the UEs current cell is known to the RNC. If the RNC wants to exchange data with the UE, it only needs to p
must perform a cell update. Also periodical cell updates can be requested by UTRAN. To perform updates, the UE must change to the CE
uplink transmission is allowed in CELL_PCH/URA_PCH.)

URA_PCH URA stands for UTRAN Registration Area. This state is comparable to the Cell_PCH,only that the UTRAN knows the UE on U
If the UE is in the CELL_PCH and moving fast, a lot of cell updates have to be performed. URAs are a combination of one or several cells
cell may belong to several URAs. If UTRAN wants to transmit something to the UE, it must page the UE within the URA. The UE is respon
URA and periodic URA updates when required by UTRAN.

In the URA_PCH or CELL_PCH state the UE shall perform the following actions:
if the UE is "in service area":
- maintain up-to-date system information as broadcast by the serving cell
- perform cell reselection process
- perform a periodic search for higher priority PLMNs
- monitor the paging occasions according to the DRX cycle and receive paging information on the PCH
- perform measurements process according to measurement control information
- maintain up-to-date BMC data if it supports Cell Broadcast Service (CBS)
- run timer T305 for periodical URA update if the UE is in URA_PCH or for periodical cell update if the UE is in CELL_PCH
if the UE is "out of service area":
- perform cell reselection process
- run timer T316;
- run timer T305

RRC Connection Mobility Management and RRC Modes

If the UE is in the RRC connected mode, but not in the CELL_DCH sub-state, it is responsible to inform UTRAN about a detected change
URA Update.

Depending on the UEs RRC message, UTRAN returns the RRC message Cell Update Confirm or URA Update Confirm if it accepts the

The cell or URA update are conducted for several reasons:

1. The UE is in the CELL_PCH or URA_PCH sub-state and re-entering the UMTS service area. Then the UE moves to the CELL_FACH s
2. Periodical updates can be enforced by the operator for UEs in the sub-states CELL_FACH, CELL_PCH and URA_PCH.
3. There is an unrecoverable error at the UEs RLC-entity, used for acknowledge mode of operation.
4. A cell update is additionally triggered for several reasons:
- The UE has performed cell-reselection. It is camping on a new cell, and UTRAN must be notified about it.
- The UE was paged in the sub-states URA_PCH or CELL_PCH.
- The UE informs UTRAN about its transition to the CELL_FACH state. Another reason for a CELL_FACH transition is an indication by the
transmitted uplink.
- The UE is in the CELL_DCH and a radio link failed.
- The UE was not capable to transmit the RRC message UE Capability Information.
The cell or URA update are conducted for several reasons:
1. The UE is in the CELL_PCH or URA_PCH sub-state and re-entering the UMTS service area. Then the UE moves to the CELL_FACH s
2. Periodical updates can be enforced by the operator for UEs in the sub-states CELL_FACH, CELL_PCH and URA_PCH.
3. There is an unrecoverable error at the UEs RLC-entity, used for acknowledge mode of operation.
4. A cell update is additionally triggered for several reasons:
- The UE has performed cell-reselection. It is camping on a new cell, and UTRAN must be notified about it.
- The UE was paged in the sub-states URA_PCH or CELL_PCH.
- The UE informs UTRAN about its transition to the CELL_FACH state. Another reason for a CELL_FACH transition is an indication by the
transmitted uplink.
- The UE is in the CELL_DCH and a radio link failed.
- The UE was not capable to transmit the RRC message UE Capability Information.

If a cell update takes place, the UE may be requested to modify its RB configuration, TrCH configuration, etc. This must be confirmed by th
establishments of RLC-entities in the acknowledged mode as figures below.

URA Update is conducted next to re-entering the UMTS service area, due to an RRC acknowledged mode unrecoverable error and beca
UE performs cell re-selection, and the new cell does not belong the the UEs URA. An URA Update is then triggered by the UE to get a n

When a UE transmits a Cell Update or URA Update message, it starts the timer T302. It waits for the T302 period to get the Cell Update C
If no confirmation message arrived within this time period, the UE retransmits the original message. The number of Cell Update or URA U
send, it hereby limited to N302. The retransmission is of course only possible, when the UE is in the service area; if not, it must continue to

Cell and URA updates performed according to the causes in the figure below. As you can see, a periodic update can be done not only, whe
periodic update is a supervision mechanism, which can be used by the mobile operator to keep track of the UE. If a cell or URA update wa
URA_PCH, or in the RRC mode idle.
UE Tasks in the CELL_FACH Sub-state
In the CELL_FACH, but also in the CELL_PCH and URA_PCH, the timer T305 is used for periodical cell or URA updates.
It is still active, when the UE is out of the service area. What happens, if this timer expires? The timer T307 is activated, and the UE starts
resources.

The timers can be broadcasted with the System Information Block 1 (or as part of the UTRAN Mobility Information message):

Out-of-Service Area Timing

If the UE is out of service area, it runs the cell selection process. It keeps the timers T305 running and starts timer T316. The UE attempts
and the UE is in the service area again, the UE stops timer T316. It also stops timer T307, in case this timer is active. Being back in the se
by the same cell or URA, and no update is required. If the UE is in the service area, but the cell or URA has changed, the cell or URA upda
happens, if the timer T316 expires? If the UE is still out of service area, it moves to the sub-state CELL_FACH and starts timer T317. If the
the Cell Update with cause re-entering service area.

In the CELL_FACH state, the UE acts like this:

If the UE is in the service area and the timer T305 has expired, it performs a periodical cell update.

If the UE is out of service area, it performs the cell selection process. The timers T305 is still active, and the UE starts timer T317, if it was
when it was active. The UE has to transmit the RRC Cell Update message to UTRAN, indicating the cause of the
cell update: re-entering service area. If the timer T317 expires, the UE moves to the idle mode. It releases all dedicated resources.
If the UE is in the service area and the timer T305 has expired, it performs a periodical cell update.

If the UE is out of service area, it performs the cell selection process. The timers T305 is still active, and the UE starts timer T317, if it was
when it was active. The UE has to transmit the RRC Cell Update message to UTRAN, indicating the cause of the
cell update: re-entering service area. If the timer T317 expires, the UE moves to the idle mode. It releases all dedicated resources.
 Click to return to main page

connected mode can be further divided into 4 service

ciafication is shown below:

GSM Packet
nnected Transfer
S 04.18 GSM TS 04.50

g radio tasks are in the responsibility of RRC. The RRC has following functions:

trol tasks are performed and it belongs to the transport stratum,because it carriers the higher layer control plane protocol messages.
TS radio interface. The radio bearers in an UE will be numbered from 0 to 31.
ed:
e RACH with RLC transparent mode, the downlink CCCH is mapped to the

ot for RRC messages that transport NAS messages inside.

NAS messages on DCCH in RLC acknowledged mode.

affic channels or control channels.

an be chosen for transport of this message.

GSM-UMTS Handover
GSM
Connected
Mode
UTRA: Inter-RAT Handover

Release RR
Connection

GPRS Packet
Cell Transfer
Reselection Mode

Release
of a TBF

Initiation
Establish RRC of a TBF Establish RR
Connection Connection

(MS in GPRS Packet Idle Mode)

Idle Mode
(MS camps on a GSM/GPRS cell)

ssage transport). Therefore the RRC protocol requires state definition with transitions between states.
states are defined:
n the access stratum level between the UE and UTRAN. UTRAN has no information about UEs in the RRC idle mode. If UTRAN wants to address

aging occasions on its PICH.

ending the "RRC Connection Request" message to UTRAN. If common transport channels used to exchange messages and data between the
e
ates depend on the connectivity level between the UE and UTRAN. The set of usable transport channels depend also on the sub-states. For
RRC idle
request, the UE enters either the sub-state CELL_DCH or CELL_FACH.

escribe, on which level the UE is known by UTRAN and which resources are allocated by the UE. UTRAN can know any UE either on cell level
nsport channel for control message exchange. Therefore the four connected states are introduced:

H information can be transmitted. There no need to identify the UE on a dedicated channel, because the physical channels are exclusively
UE. Also downlink shared channels can be allocated to the UE. In this state, the UE is capable to receive RRC messages on the DCCH (and
reads the cell system information and acts accordingly. For instance, it determines the measurement quality and the reporting events from the cell
DCH is released the UE enters Cell_FACH,Cell_PCH,URA_PCH or idle mode

ing on FDD cells);

This is the case when only higher layer signalling information (NAS signalling) or small amount of user data (e.g. SMS messages) have to be
e of resources. Only common transport channel FACH can be used by the UE to transmit higher layer data, which it has to share with other UEs.
in the downlink, not to miss user data for it. The UEs FACH is mapped on one S-CCPCH.

only connected to one cell, and this is the location information, known within UTRAN. No soft handover takes place in this sub-state. The UE is
evant measurement qualities, threshold values, neighbourhood lists to perform the cell re-selection process. Other relevant information is also

RAN can command the UE to perform periodic cell updates.

 users. Just think about users, who surf in the Internet. After downloading some files, they work with the data, and for a longer time, no
one of the two states. In both states, no DCCH nor DTCH is allocated to the UE. No exchange of data is possible between the UE and UTRAN. If

ordingly, and is responsible for cell-reselection. In addition to that, it periodically looks for a PLMN with a higher priority. When UTRAN wants to
PICH, i.e. it receives RRC messages both on the BCCH and the PCCH.

ata with the UE, it only needs to page the UE there. If the UE changes the cell, it
s, the UE must change to the CELL_FACH sub-state. (Please note, that no

at the UTRAN knows the UE on URA level.

ombination of one or several cells under one S-RNC. URAs may overlap, i.e. a
within the URA. The UE is responsible for URA updates when it changes the

E is in CELL_PCH

UTRAN about a detected change of location. The UE then moves (or is) in the CELL_FACH state and send the RRC message Cell Update or

Update Confirm if it accepts the UEs update request. Otherwise, it return the RRC Connection Release message.

UE moves to the CELL_FACH state and notifies UTRAN.

H and URA_PCH.

it.

H transition is an indication by the UEs higher layers, that data has to be

update can be done not only, when the UE is in the CELL_PCH or URA_PCH sub-state, but also, when the UE is in the CELL_FACH sub-state. A
he UE. If a cell or URA update was performed, a UE in the CELL_FACH sub-state may transit to the sub-states CELL_DCH, CELL_PCH or
or URA updates.
07 is activated, and the UE starts the cell selection process. If the timer T307 expires, the UE moves into the idle mode and releases all

formation message):

arts timer T316. The UE attempts to find a serving cell again. If it is successful,
mer is active. Being back in the service area can mean, that the UE is served
as changed, the cell or URA update has to be initiated by the UE. But what
FACH and starts timer T317. If the UE is back in the service area, it performs

the UE starts timer T317, if it was not yet active. If the UE enters the service area again, the timer T317 is stopped. Also timer T307 is stopped,
se of the
es all dedicated resources.
 Click to return to main page

rotocol messages.
Click to return to main page
>>State Transistions Parameters Description (Module II)
 Click to return to main page

RAN wants to address

d data between the

e sub-states. For

Click to return to main page

E either on cell level

are exclusively
on the DCCH (and
ng events from the cell

sages) have to be
share with other UEs.

ub-state. The UE is
information is also
er time, no
he UE and UTRAN. If

en UTRAN wants to

Click to return to main page

>>UE&NodeB Timer and constant Parameters Description (Module II)
ge Cell Update or
LL_FACH sub-state. A
, CELL_PCH or
releases all

er T307 is stopped,
Click to return to main page

RRC Procedures
Between the UE and the RNC, the Radio Resource Control (RRC) protocol is used to exchange signalling and control data to establish, m
settings. With that, the UE knows how to receive and transmit data via the WCDMA radio interface. The RNC uses the NodeB Application

Following RRC procedures can be identified in accordance to the ETSI specification TS 25.331 V3.12.0:
-RRC Connection Management Procedures :These procedures include the broadcasting of system information, paging, RRC connectio
-Radio Bearer Control Procedures :These procedures for radio bearer establishment, transport channel and physical channel reconfigur
-RRC Connection Mobility Procedures :These procedures such as cell and URA updates, UTRAN mobility information, active set update
-Measurement Procedures Measurement control and report, etc. is managed here.

Radio Resource Control message contains of following groups of information elements :

-CN information elements : NAS specific information is transmitted, such as the CN type and CN domain identity.
-UTRAN mobility management information elements : Cell access restrictions, cell and URA identities are examples of data, associated
-UE information elements: UE related information is exchanged here, including capability update requirements, PDCP and FDD RF capa
-Radio Bearer information elements: These information elements mostly describe the characteristics of a radio bearer, such as RB infor
-Transport Channel information elements: Here, mainly the transport channel characteristics are described, such as the description of T
-Physical Channel information elements: Here, everything relevant for the PHY-layer is covered, such as the description of CCTrCHs or
-Measurement information elements: Cell measured results, event results, filter coefficients etc. are exchanged here.
-Other information elements

RRC Connection Establishment

The purpose of the RRC Connection Establishment procedure is to create a RRC connection between the UE and UTRAN.

To do so, the UE sends the RRC Connection Request message to the RNC. The UE was in the RRC idle mode, and higher layer protocols
logical channel CCCH.

UTRAN returns a response. If UTRAN accepts the UEs RRC Connection Request, it returns the message RRC Connection Setup messag

From the RNC point of view, it is not just sufficient to inform the UE about the signalling resources. The Node B must also get all relevant p
Connection Setup message to the UE, it uses the UTRAN specific signalling protocol NBAP to send these parameters to the Node B.

If UTRAN denies access to the UE, it returns the message RRC Connection Reject. Both messages are returned to the UE via a FACH.

If the UE has received the message RRC Connection Setup, it returns the RRC Connection Setup Complete message to the RNC, using t
If UTRAN denies access to the UE, it returns the message RRC Connection Reject. Both messages are returned to the UE via a FACH.

If the UE has received the message RRC Connection Setup, it returns the RRC Connection Setup Complete message to the RNC, using t

RRC Connection Request Message

1. RRC Connection Request message

It is initiated by the UE and transmitted via the uplink CCCH. Two types of information element groups can be found in this message:
-UE information elements and
-Measurement information elements.

Following data about the UE is sent in this message:

-Initial UE identity:
The UE identities contains of 4 options- IMSI,IMEI,P-TMSI&RAI or TMSI&LAI. The operator can choice one of the UE identity to use

-Establishment cause :
There is a huge list of causes for a connection request

-Protocol error indicator :

This message can also indicate, whether a protocol error occurred.
If so, this value is set to TRUE. The default value is FALSE.

The UE also delivers measurement results; the corresponding IE is called Measured Results on the RACH, because the measurement
broadcasted as cell system information. The cells, listed in the measurement result list, are ordered in accordance to the measurement res
with the best one in the beginning of the list.

RRC Connection Setup Message

The message itself holds 4 information elements groups:
1. UE information elements to identify the UE (UE IEs)
2. Radio bearer information elements (RB IEs), which specify the properties of the signalling bearers, which are established with this RR
3. Transport channel information elements(TrCH IEs: UL/DL) to define the transport channel characteristics, in other words the TFCS.
4. Physical Channel information elements(PhyCH IEs: UL/DL), which specify parameters relevant for the PHY layer to make the physic
3. RRC Connection Setup message: TrCH IEs (UL/DL):
Each RB set between a UE and UTRAN has a unique number. Each of them can be mapped on one or two logical channels. This was par
mapped on transport channels. But on which transport channels can the higher layer information be transmitted? How can higher layer info
TrCH UL/DL. This information is used by the RRC to configure the RLC-, MAC, and PHY layer.

A very important IE is the Transport Format Set (TFC). The Transport Format Set information element describes the the allowed TFs, whi
which logical channels are mapped on this TrCH.

The MAC layer is responsible to take the RLC PDUs (which hold the TBs), and to send them to their peer entity. RLC PDUs from several R
PDU. For instance, if two DTCHs are multiplexed on one DCH, then field C/T is added in the MAC header to identify the logical channel, to
the RLC PDU has to be delivered to.
Please note, that three different MAC entities exist:
-MAC-b: This entity controls the BCH. It is located in the Node B.
-MAC-c/sh : This MAC-entity controls the access to the common control channels PCH, FACH, RACH, CPCH, DSCH.
-MAC-d: This MAC-entity control the access to the dedicated transport
4.RRC Connection Setup message: PhyCH IEs (UL/DL):

The Physical Channel information elements deliver relevant information for the PHY layer to configure the physical channels. One of the P
established. As can be seen, a UE can be immediately re-directed to another frequency band for the signalling bearer setup. Also the avai

The Uplink DPCH info is an optional information element in the RRC Connection Setup message.

The UE can be informed about the downlink radio resources, when receiving the RRC Connection Setup message. When we have a close
following FDD-mode specific information elements:
1. DPCH compressed mode If a UE has only one receiver, it cant make inter-frequency or inter-RAT measurements on neighbouring ce
the downlink transmission must be interrupted to give the UE time to make its measurements. Therefore, this mode is often called Slotted
puncturing is done if the required link quality can be kept up or the spreading factor is halved for a short while.
2. Site Selection Diversity Transmit (SSDT) ,The UE is served by several active set cells. But while all active set cells receive the UEs s
cells, which one shall serve it in the downlink.
3.Transmit Diversity Two-transmitter diversity is applied. The UE sends a feedback (FBI) to the Node B, so that this device can decide
called closed loop modes: - closed loop mode 1: A phase adjustment is done with one antenna. Hereby, the feedback command ra
are sent on four timeslots to the Node B.

RRC Connection Setup Complete message

CAPABILITY INFORMATION message and transfer it to the handover control entity.

After the UE transmits RRC CONNECTION REQUEST message, the T300 timer will be started, and the timer will be stopped after the UE
times specified by the constant N300, the UE repeats RRC CONNECTION REQUEST; otherwise it will be in the idle mode,consider the pro

if the UE has not yet received an RRC CONNECTION SETUP message with the value of the IE "Initial UE identity" equal to the value of th
the UE shall:
- check the value of V300; and
if V300 is equal to or smaller than N300:
- if cell re-selection occurred: set CFN in relation to SFN of current cell
- set the IEs in the RRC CONNECTION REQUEST message
- perform the mapping of the Access Class to an Access Service Class and
- apply the given Access Service Class when accessing the RACH;
- submit a new RRC CONNECTION REQUEST message to lower layers for transmission on the uplink CCCH;
- increment counter V300;
- restart timer T300 when the MAC layer indicates success or failure to transmit the message;
if V300 is greater than N300:
- enter idle mode.
- consider the procedure to be unsuccessful;
- Other actions the UE shall perform when entering idle mode from connected mode
- The procedure ends.

L1 Synchonization on DPCCH and DPDCH (UL and DL)

Downlink synchronisation primitives
For the dedicated channels, synchronisation primitives are used to indicate the synchronisation status of radio links, both in upl
A UE Layer1 shall check the synchronisation status of every radio frame of downlink and uplink dedicated channels in order to detect a los
a radio link is determined based on the physical channel BER of the DPCCH (The physical channel BER is the relation of the incorrectly de
Qout and Qin specify at what DPCCH quality levels the UE shall shut its power off and when it shall turn its power on respectively. The syn

The criteria for reporting synchronisation status are defined in two different phases.
Phase 1:
-Starts when higher layers initiate physical dedicated channel establishment and lasts until 160 ms after the downlink dedicated channel is
-During this time the Out-of-sync status shall not exist
-During this time the In-sync status shall be reported using the CPHY-Sync-IND primitive if the following criterion is fulfilled:
The UE estimates the DPCCH quality over the previous 40 ms period to be better than a threshold Qin. This criterion shall be assumed no
collected. Qin is defined implicitly by the relevant tests. (def. 20% BER) . (The mapping of the Q_IN values to the actual physical channel B

Phase 2:
-Starts 160 ms after the downlink dedicated channel is considered established by higher layers with In-sync status
-During this phase the criteria for the Out-of-sync and In-sync status are as follows
Out-of-sync shall be reported using the CPHY-Out-of-Sync-IND primitive if either of the following criteria are fulfilled:
- The UE estimates the DPCCH quality over the previous 160 ms period to be worse than a threshold Qout. Qout is defined implicitly by the
- The 20 most recently received transport blocks with a CRC attached, as observed on all TrCHs using CRC, have been received with inco
attached have been received with incorrect CRC. In case of no TFCI is used this criterion shall be considered only for TrCHs using CRC in

In-sync shall be reported using the CPHY-Sync-IND primitive if both of the following criteria are fulfilled:
- The UE estimates the DPCCH quality over the previous 160 ms period to be better than a threshold Qin. Qin is defined implicitly by the re
- At least one transport block with a CRC attached, as observed on all TrCHs using CRC, is received in a TTI ending in the current frame w
CRC attached, this criterion shall be assumed to be fulfilled. In case of no TFCI is used this criterion shall be considered only for TrCHs us

At least one TB in the last radio

frame with correct CRC transmitted

UE Sycnchronization Status

Uplink synchronisation primitives

Layer 1 in the Node B shall every radio frame check synchronisation status of all radio link sets. Synchronisation status is indicated to the R
CPHY-Out-of Sync IND primitive. Hence, only one synchronisation status indication shall be given per radio link set.The exact criteria for in
same criteria as for the downlink synchronisation status primitives.

The establishment of a radio link can be divided into two cases:

- when there is no existing radio link, i.e. when at least one downlink dedicated physical channel and one uplink dedicated physical chan
- or when one or several radio links already exist, i.e. when at least one downlink dedicated physical channel is to be set up and an upl
Layer 1 in the Node B shall every radio frame check synchronisation status of all radio link sets. Synchronisation status is indicated to the R
CPHY-Out-of Sync IND primitive. Hence, only one synchronisation status indication shall be given per radio link set.The exact criteria for in
same criteria as for the downlink synchronisation status primitives.

The establishment of a radio link can be divided into two cases:

- when there is no existing radio link, i.e. when at least one downlink dedicated physical channel and one uplink dedicated physical chan
- or when one or several radio links already exist, i.e. when at least one downlink dedicated physical channel is to be set up and an upl

In Node B, each radio link set can be in three different states: initial state, out-of-sync state and in-sync state. Transitions between the
explain more details below.
1. No existing radio link
When one or several radio links are to be established and there is no existing radio link for the UE already, a dedicated physical channel is
in downlink. This corresponds to the case when a dedicated physical channel is initially set up on a frequency.
The radio link establishment is as follows:
a) Node B considers the radio link sets which are to be set up to be in the initial state. UTRAN shall start the transmission of the downlink D
transmitted.The initial downlink DPCCH transmit power is set by higher layers.Downlink TPC commands are generated.
b) The UE establishes downlink chip and frame synchronisation of DPCCH, using the P-CCPCH timing and timing offset information notifie
synchronisation word. Downlink synchronisation status is reported to higher layers every radio frame.
c) If no activation time for uplink DPCCH has been signalled to the UE, uplink DPCCH transmission shall start when higher layers consider
uplink DPCCH transmission shall not start before the downlink physical channel has been established and the activation time has been rea
d) UTRAN establishes uplink chip and frame synchronisation. Frame synchronisation can be confirmed using the frame synchronisation w
in-sync indications are received from layer 1, when Node B shall trigger the RL Restore procedure indicating which radio link set has obtain
shall be considered to be in the in-sync state.The RL Restore procedure may be triggered several times, indicating when synchronisation is

2. One or several existing radio links

When one or several radio links are to be established and one or several radio links already exist, there is an existing DPCCH/DPDCH in t
set up in the downlink. This corresponds to the case when new radio links are added to the active set and downlink transmission starts for

a) Node B considers new radio link sets to be set up to be in initial state. If a radio link is to be added to an existing radio link set this radio
addition of the radio link, i.e. if the radio link set was in the in-sync state before the addition of the radio link it shall remain in that state.
b) UTRAN starts the transmission of the downlink DPCCH/DPDCH at a frame timing such that the frame timing received at the UE will be
the UE. Simultaneously, UTRAN establishes uplink chip and frame synchronisation of the new radio link. Frame synchronisation can be co
in the initial state shall remain in the initial state until N_INSYNC_IND successive in-sync indications are received from layer 1, when Node
obtained synchronisation. When RL Restore is triggered the radio link set shall be considered to be in the in-sync state.The RL Restore pro
obtained for different radio link sets.
c) The UE establishes chip and frame synchronisation of the new radio link. Frame synchronisation can be confirmed using the frame sync
layers every radio frame.

Radio Link Monitoring

Downlink radio link failure/restore

The downlink radio links shall be monitored by the UE, to trigger radio link failure procedures. Radio link failure detection in DL is based on
for the established DPCCH physical channel in FDD the UE
->start timer T313
->upon receiving N315 successive "in sync" indications from layer 1 and upon change of UE state:
Downlink radio link failure/restore
The downlink radio links shall be monitored by the UE, to trigger radio link failure procedures. Radio link failure detection in DL is based on
for the established DPCCH physical channel in FDD the UE
->start timer T313
->upon receiving N315 successive "in sync" indications from layer 1 and upon change of UE state:
->stop and reset timer T313

In case of the expiry of T313 which means Radio Link Failure, how much time UE can re-establish a bearer. A bearer can be associated w
unacknowledged mode(UM) bearers. T315 is controlling acknowledged(AM) mode bearers
->Timer T314 is started if radio bearer(s) that are associated with T314 exist or if only RRC connection exists, and stopped when the Cell U
->Timer T315 is started only if radio bearer(s) that are associated with T315 exist, and stopped when the Cell Update procedure has been

If T314 expires and T305 is not running, then all radio bearers associated with radio bearers with T314 value are locally released. If additio

If T315 expires and T305 is not running, then all radio bearers associated with radio bearers with T315 value are locally released. If additio

In case of the expiry of T314 (T315), the corresponding service Radio Bearers will be removed.

For UE in CELL_DCH state, In case of Radio link failure, if the Radio link cannot be successfully reconfigured by CELL UPDATE CONFIRM
resent for Radio link reconfiguration (this operation relates to T302 and N302). T314(T315) should be set greater than T302*N302

The timer T302 is started when UE transmits CELL UPDATE/URA UPDATE, and stopped when UE receives a CELL UPDATE CONFIRM/U
UPDATE/URA UPDATE if the counter V302 is no bigger than the Maximum number of retransmissions of the CELL UPDATE / URA UPDA

Uplink radio link failure/restore

The uplink radio link sets are monitored by the Node B, to trigger radio link failure/restore procedures. Once the radio link sets have been e
those two states are described below.
-The uplink radio link failure/restore criteria is based on the synchronisation status primitives CPHY-Sync-IND and CPHY-Out-of-Sync-IND,
synchronisation status indication shall be given per radio link set.

-When the BTS L1 has detected N_INSYNC_IND consecutive indications with In-sync status, the radio link is moved from the initial state t
BTS L3 sends the NBAP:SYNCHRONIZATION INDICATION message to the RNC

-When the radio link set is in the in-sync state, Node B shall start timer T_RLFAILURE after receiving N_OUTSYNC_IND consecutive out-
receiving successive N_INSYNC_IND in-sync indications. If T_RLFAILURE expires, Node B shall trigger the RL Failure procedure and indi
triggered, the state of the radio link set change to the out-of-sync state. During the Out-of-sync state, L1 keeps on searching the synchroni
released by the RNC with the NBAP:RADIO LINK DELETION message

-When the radio link set is in the out-of-sync state, after receiving N_INSYNC_IND successive in-sync indications Node B shall trigger the
synchronisation. When the RL Restore procedure is triggered, the state of the radio link set change to the in-sync state. BTS L3 sends the

After the BTS has established the frame synchronization to the uplink DPCH, the transmission power of the downlink DPCH is controlled b
downlink dedicated physical channel are based on the SIR measurements from the uplink DPCH. (The parameters Qin and Qout and N_IN
in the NBAP: CONFIGURATION DATA message)

Example of 3 common cases of L1 Synchonization

When the UE starts to set up the dedicated channel, it starts the T312 timer, and after the UE detects N312 synchronization indications fro
->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
->On receiving N312 "in sync" indications, the physical channel is considered established and the timer T312 is stopped and reset
->On the BTS side after receiving N_INSYNC_IND synchronization indicators the BTS sends NBAP: SYNCHRONIZATION INDICATION

->In case UE is not able to establish synchronization within timer T312 it stops TX on the DCH
->In case BTS is not able to establish synchronization it does not send NBAP:Synchronization Indication message to RNC
The BTS tries to establish synchronization until timer in RNC expires and RNC sends NBAP:Radio Link Deletion -message

->In case BTS is able to establish synchronization it sends NBAP:Synchronization Indication message to RNC
->In case UE is not able to establish synchronization within timer T312 it stops TX on the DCH
->As the UE TX is off the BTS looses the L1 synchronization and sends NPAB: Radio Link Failure message to RNC
After Timer expires in RNC the RNC sends NPAB: Radio Link Deletion to BTS which then stops searching for the synchronization
 ling and control data to establish, maintain, and release connections. The UE gets informed about the radio bearer characteristics, the transport channel co
e RNC uses the NodeB Application Part (NBAP) protocol to inform the Node B about the radio interface configuration.

V3.12.0:
information, paging, RRC connection establishment and release, UE capability inquiry, security mode control, Inter-RAT handover information transfer, etc.
nnel and physical channel reconfiguration, physical channel failure, etc. can be found here.
mobility information, active set update, and various handover procedures are covered here.

main identity.
ies are examples of data, associated with these IEs.
uirements, PDCP and FDD RF capabilities, radio access capabilities, cell update causes,etc.
s of a radio bearer, such as RB information to setup.
escribed, such as the description of TFCs and TFCSs.
ch as the description of CCTrCHs or compressed mode information.
exchanged here.

the UE and UTRAN.

dle mode, and higher layer protocols in the UE request a signalling connection to UTRAN. Please note, that an RRC connection establishment is always ini

sage RRC Connection Setup message. The UE gets all relevant parameters regarding the signalling bearers, transport channels, and physical channels.

e Node B must also get all relevant parameters to serve the UE on the radio interface adequately, and to relay data between the Iub-interface and Uu-interfa
ese parameters to the Node B.

are returned to the UE via a FACH.

mplete message to the RNC, using the transport channel DCH. Beforehand it performed a L1 Synchronization.
can be found in this message:

e one of the UE identity to use

RACH, because the measurement results are transmitted via the transport channel RACH. The measured quantity can be set by the operator, but it is an o
accordance to the measurement results,

2.RRC Connection Setup message

If the S-RNC accepts the UEs RRC Connection Establishment request. It starts an interaction with the Node B to establish a r
This interaction is also used to inform the Node B about the radio link
configuration parameters for uplink and downlink transmission via the interface Uu. In other words, the Node B is fully
prepared to serve as intermediate mode between the mobile phone and the RNC. The UE gets the radio link configuration
parameters with the RRC Connection Setup message, which is transmitted in the transport channel FACH. This message is us
between the UE and the RNC.

The RRC Connection Setup message is used to specify the (signalling) radio bearer, the transport channel and the physical ch
downlink directions. The RRC Connection Setup message is sent from the RRC layer in the RNC to the RRC layer in the UE.
interfaces to the configure the lower layers accordingly.
-If only the physical layer characteristics are modified, then the RRC layer only has to interact with the PHY layer. A
modification may affect scrambling and modulation. A new channelisation code may be deployed for the connection, which
has no impact to the higher layers. The PHY layer is for instance responsible for radio measurements, and the RNC can
change measurement quantities or threshold values. Again, this has no impact on the higher layers.
-If the transport channels are modified, then this has an effect both on the MAC (Medium Access Control) layer and the
PHY layer. The MAC layer is responsible for Transport Format selection, identification of UEs on the common and shared
resources, ciphering and de-ciphering, random access control, etc.
-If a radio bearer is established, or modified, then following layer instances may receive parameters: - Radio Link Control
(RLC) layer for each radio bearer, an RLC instance is established - , - Packet Data Convergence Protocol (PDCP) layer, -
Broadcast/Multicast Control (BMC) layer instances, - Medium Access Control (MAC) layer instances, and - PHY layer. With
the RRC Connection Setup message, we establish several signalling radio bearers for the UE, so that we wont see the
PDCP layer and BMC layer relevant parameters.
 has no impact to the higher layers. The PHY layer is for instance responsible for radio measurements, and the RNC can
change measurement quantities or threshold values. Again, this has no impact on the higher layers.
-If the transport channels are modified, then this has an effect both on the MAC (Medium Access Control) layer and the
PHY layer. The MAC layer is responsible for Transport Format selection, identification of UEs on the common and shared
resources, ciphering and de-ciphering, random access control, etc.
-If a radio bearer is established, or modified, then following layer instances may receive parameters: - Radio Link Control
(RLC) layer for each radio bearer, an RLC instance is established - , - Packet Data Convergence Protocol (PDCP) layer, -
Broadcast/Multicast Control (BMC) layer instances, - Medium Access Control (MAC) layer instances, and - PHY layer. With
the RRC Connection Setup message, we establish several signalling radio bearers for the UE, so that we wont see the
PDCP layer and BMC layer relevant parameters.

s, which are established with this RRC message.

acteristics, in other words the TFCS.
or the PHY layer to make the physical channels available.

1. RRC Connection Setup message: UE IEs:

1. Initial UE ID: The common transport channel FACH is used to send the RRC Connection Setup message
from the RNC to the UE. All UEs listening to the same FACH bearing S-CCPCH must be capable to detect, wh
UE identification, the IMSI or TMSI and LAI can be used.
RRC Transaction ID: Several RRC transactions can run in parallel. This number associates the message to
one transaction.
2. Activation Time: The transmission of transport channel frames has to be synchronised between the UE and
the S-RNC. This is also called L2 synchronisation. The Connection Frame Number (CFN) is an element of the
make sure, that the UE gets a radio frame with a specific CFN
(approximately) To = 1024 chips before is starts to send a radio frame with the same CFN. The Activation Time
indicates, when the UE can expect the transmission to start.
3. New U-RNTI and New C-RNTI: Common transport channels are shared resources, which can be used by
several UEs. The MAC-layer will add the required addressing information U-RNTI and C-RNTI. UE, S-RNC, C-
RNC and Node B identify each other by called Radio Network Temporary Identifiers (RNTI). The S-RNC alloca
a S-RNTI to the UE to address the UE. When the UE accesses a new cell, the C-RNC allocates aC-RNTI to th
UE, with which it addresses the UE. The U-RNTI is a concatenation of the S-RNTI and the S-RNCs RNC-ID.
The U-RNTI is unique worldwide, and is used by the S-RNC to address the UE on common radio channels,
during paging, etc.
4. RRC State Indicator: This indicator tells the UE, in which internal RRC connected sub-state is has to move
5. Capability Update Requirement:

2.RRC Connection Setup message: RB IEs:

Radio Bearer (RB) services are offered to the higher layers. Higher layers are:
-RRC layer, which uses signalling radio bearers to exchange radio link management messages between the U
NAS-signalling information to guarantee its transport in signalling radio bearers.
-NAS layers for user SDU transfer.

When the RRC Connection Setup message is sent from the RNC to the UE, then the RB IEs describe, how the
make the radio bearer service available to the RRC layer.

RLC sub-layer's tasks: For each RB, and RLC instance is established. Three different types are distinguishe
1.Transparent Mode (TrM) RLC entities In this mode, data is buffered, when it arrives in the RLC entity.
Segmentation at the transmitting RLC entity and re-assembly at the receiving RLC entity may occur, if being
configured by higher layers and the RLC SDU is larger than required by the lower layers, given the TTI. No oth
service is offered.
2. Unacknowledged Mode (UM) RLC entities Data transfer, segmentation and reassembly is done like in the
TrM. But higher layer data is transmitted without guaranteeing its delivery. Sequence control and ciphering are.
3.Acknowledged Mode (AM) RLC entities A reliable bearer is offered in this mode. Its features can be seen in
the figure on the right hand side.
 Signalling radio bearers have to be set up. Three signalling radio bearers must be set up, the 4th one is opt
This is indicated with the IE Signalling RB to Setup List. Given the number, either 3 or 4 descriptions of radio b
which must be made available for the RLC sub-layer.

-RB identity: Each RB has a unique identity. The identities for signalling radio bearers are ranging from 1 to 4.
The total number of RBs, the UE can establish on command of the RNC, is 32. RB0 parameters are not
transmitted,because there are fixed rules how to determine its RLC parameters.
-Choice RLC info type: a RB is described: This is the case with the IE RLC info. Or its parameters are copied
from an existing one, where only the RB identity has to be delivered to the UE.
-RB mapping info Uplink, following transport channel types can be identified: DCH, RACH, and CPCH The
mapping information describes, on which Transport Channels the given RB can be mapped to. UL DCH are ge
an identity (number). This number is used to describe, to which UL DCHs the RB can be mapped. Downlink,
we can identify following transport channel types: DCH, FACH, DSCH and DCH + DSCH. DSCH and DCH
receive an identity. There can be one or two logical channels per radio bearer or RLC entity. Therefore, there a
also logical channel identities.

r two logical channels. This was part of the RB setup information. The information carried on radio bearers must be
ansmitted? How can higher layer information be segmented? This is described with the information elements for

t describes the the allowed TFs, which can be transmitted via this TrCH.This information element also describes,

peer entity. RLC PDUs from several RBs (RLC layers) can be multiplexed on one transport channel. The MAC header of a MAC PDU holds relevant informa
der to identify the logical channel, to which

, CPCH, DSCH.
 the physical channels. One of the PhyCH IEs is the carrier frequency band, where the signalling connection is
ignalling bearer setup. Also the available UL and DL radio resources have to be described.

up message. When we have a closer look to the IE Downlink information common for all radio links, we detect

T measurements on neighbouring cells and at the same time receive data from the active set cells. If this is the case,
ore, this mode is often called Slotted Mode. In order to transmit still the user data with a given data rate, more
short while.
all active set cells receive the UEs signals, only one is making a transmission downlink. The UE tells the active set

ode B, so that this device can decide, how to set the weighting to the individual antennas. There are two different so-
Hereby, the feedback command rate is 1 bit per timeslot. - closed loop mode 2: Phase and amplitude adjustments

3. RRC Connection Setup Complete message

The UE has received the RRC Connection Setup message and returns the RRC Connection Setup Complete
transmitted via the logical channel DCCH on the radio signalling bearer, which offers acknowledged mode of o
the RRC Connection Setup Complete message can be grouped into
-UE information elements and
-Other information elements.

The UE can return its capabilities to the S-RNC with the IE Radio Access Capability, which contains
-Transport channel capability: is distributed to the resource manager and to the admission control entity
-RF capability: the RF capability is distributed to the resource manager, the power control entity and to the han
-Physical channel entity: is distributed to resource manager
-UE multi-mode/multi-RAT capability
-Security capability
-LCS capability
-Measurement capability: is distributed to the handover control entity. Presence is mandatory if IE Multi-mode c
"FDD/TDD" and a FDD capability update has been requested in a previous
message. Otherwise this field is not needed in the message.

Among the optional other information elements, we find the Inter_RAT UE access capability. The RNC shall
extract the inter-system message from the UE CAPABILITY INFORMATION message and transfer it to the
handover control entity.
 Among the optional other information elements, we find the Inter_RAT UE access capability. The RNC shall
extract the inter-system message from the UE CAPABILITY INFORMATION message and transfer it to the
handover control entity.

ver control entity.

he timer will be stopped after the UE receives RRC CONNECTION SETUP message. Once the timer times out, if RRC CONNECTION REQUEST message
l be in the idle mode,consider the procedure to be unsuccessful. The procedures in details are as follows:

UE identity" equal to the value of the variable INITIAL_UE_IDENTITY; and if cell re-selection or expiry of timer T300 occurs;

k CCCH;
n status of radio links, both in uplink and downlink.
ted channels in order to detect a loss of the signal on Layer 1, as specified in TS 25.214. The synchronization state of
ER is the relation of the incorrectly detected pilot bits to the total number of pilot bits in a radio frame),the thresholds
rn its power on respectively. The synchronisation status is reported to the higher layer.

er the downlink dedicated channel is considered established by higher layers

following criterion is fulfilled:

n. This criterion shall be assumed not to be fulfilled before 40 ms of DPCCH quality measurements have been
lues to the actual physical channel BER is given in 3GPP TS 25.133)

-sync status

g criteria are fulfilled:

Qout. Qout is defined implicitly by the relevant tests(def. 15% BER)
CRC, have been received with incorrect CRC. In addition, over the previous 160 ms, all transport blocks with a CRC
sidered only for TrCHs using CRC in all transport formats.

fulfilled:
Qin. Qin is defined implicitly by the relevant tests(def.20% BER)
n a TTI ending in the current frame with correct CRC. If no transport blocks are received, or no transport block has a
hall be considered only for TrCHs using CRC in all transport formats.

last TBs transmitted 20

with incorrect CRC transmitted
Initial
state
RL Restore

RL Failure

In-sync
state

RL Restore

NodeB Radio Link Set States and Transistions

ronisation status is indicated to the RL Failure/Restored triggering function using either the CPHY-Sync-IND or
radio link set.The exact criteria for indicating in-sync/out-of-sync is not subject to specification, but could e.g. be based on received DPCCH quality or CRC

d one uplink dedicated physical channel are to be set up;

al channel is to be set up and an uplink dedicated physical channel already exists.
 Downlink Direction

Uplink Direction

nk failure detection in DL is based on counter N313 (counting out of sync indicator) and timer T313 in UE. In CELL_DCH State, after receiving N313 conse
Once the radio link sets have been established, they will be in the in-sync or out-of-sync states. Transitions between

nc-IND and CPHY-Out-of-Sync-IND, indicating in-sync and out-of-sync respectively. Note that only one

o link is moved from the initial state to an In-sync state. L1 informs BTS L3 about the established synchronization and

N_OUTSYNC_IND consecutive out-of-sync indications. Node B shall stop and reset timer T_RLFAILURE upon
er the RL Failure procedure and indicate which radio link set is out-of-sync. When the RL Failure procedure is
1 keeps on searching the synchronization as long as the synchronization has been re-established or the radio link is

indications Node B shall trigger the RL Restore procedure and indicate which radio link set has re-established
the in-sync state. BTS L3 sends the NBAP:SYNCHRONIZATION INDICATION message to the RNC

of the downlink DPCH is controlled based on the TPC bits transmitted by the UE. Also, the TPC bits transmitted in the
e parameters Qin and Qout and N_INSYNC_IND, N_OUTSYNC_IND, T_RLFAILURE are given by the RNC to the BTS

N312 synchronization indications from L1, it will stop the T312 timer. Once the timer times out, it means that the physical channel setup has failed.

Successful Synchronization on UL and DL

Downlink Direction

Uplink Direction
 and wait for layer 1 to indicate N312 "in sync" indications
r T312 is stopped and reset
SYNCHRONIZATION INDICATION message to RNC after which the closed loop and outer loop PC start to control the powers

Failed Synchronization on UL and DL

Downlink Direction

Uplink Direction

on message to RNC
k Deletion -message

ULSynchronization failed because of

no DL synchronization

Downlink Direction

Uplink Direction

e to RNC

essage to RNC
hing for the synchronization
 characteristics, the transport channel configurations, and the physical layer
ation.

RAT handover information transfer, etc.

C connection establishment is always initiated by the UE. It is transmitted via the

port channels, and physical channels.

between the Iub-interface and Uu-interface. Before the RNC returns the RRC
 can be set by the operator, but it is an option. If set by the operator, it is

eraction with the Node B to establish a radio link connection over the interface Iub.

other words, the Node B is fully

e UE gets the radio link configuration
sport channel FACH. This message is used to establish signalling radio bearers

he transport channel and the physical channel characteristics both in the UL and
n the RNC to the RRC layer in the UE. The UEs RRC uses management

s to interact with the PHY layer. A

e deployed for the connection, which
measurements, and the RNC can
higher layers.
edium Access Control) layer and the
of UEs on the common and shared

eive parameters: - Radio Link Control

onvergence Protocol (PDCP) layer, -
yer instances, and - PHY layer. With
the UE, so that we wont see the
the RRC Connection Setup message
-CCPCH must be capable to detect, whether the RRC message is for them. For

s number associates the message to

to be synchronised between the UE and

me Number (CFN) is an element of the L2 synchronisation. The network has to

with the same CFN. The Activation Time

ared resources, which can be used by

on U-RNTI and C-RNTI. UE, S-RNC, C-
ry Identifiers (RNTI). The S-RNC allocates
cell, the C-RNC allocates aC-RNTI to the
the S-RNTI and the S-RNCs RNC-ID.
the UE on common radio channels,

RC connected sub-state is has to move to.

ers are:
management messages between the UE and the RNC. The RRC layer also takes
bearers.

e UE, then the RB IEs describe, how the Radio Link Control layer(RLC) has to

d. Three different types are distinguished:

when it arrives in the RLC entity.
ceiving RLC entity may occur, if being
y the lower layers, given the TTI. No other

ation and reassembly is done like in the

ery. Sequence control and ciphering are.
n this mode. Its features can be seen in
arers must be set up, the 4th one is optional.
ber, either 3 or 4 descriptions of radio bearers follow. They contain information,

g radio bearers are ranging from 1 to 4.

C, is 32. RB0 parameters are not
ameters.
RLC info. Or its parameters are copied
the UE.
entified: DCH, RACH, and CPCH The
n RB can be mapped to. UL DCH are get
Hs the RB can be mapped. Downlink,
and DCH + DSCH. DSCH and DCH
bearer or RLC entity. Therefore, there are

er of a MAC PDU holds relevant information to identify the receiver of the RLC
e,

-
ts

the RRC Connection Setup Complete message to the S-RNC. This message is
, which offers acknowledged mode of operation (RB2). The information elements in

ss Capability, which contains

nd to the admission control entity
the power control entity and to the handover control entity

resence is mandatory if IE Multi-mode capability has the value "FDD" or

ous

UE access capability. The RNC shall

TION message and transfer it to the
RC CONNECTION REQUEST message is retransmitted less than the number of

0 occurs;
of

Initial
state

RL Failure

Out-of-sync
state

RL Restore

k Set States and Transistions

ed on received DPCCH quality or CRC checks. One example would be to have the
_DCH State, after receiving N313 consecutive "out of sync" indications from layer 1
n

he
BTS

sical channel setup has failed.

the powers
Click to return to main page

>>See More details of 1,2,3

>>Synchronization Parameters Description (Module II)

Click to return to main page

Radio Bearer(RB) Procedures

The RB control procedures are used to establish additional radio bearers, modify them, or release them.

Radio Bearer is established, modified, and released with following RRC messages:
1.Radio Bearer Setup,
2.Radio Bearer Reconfiguration, and
3.Radio Bearer Release.

If a radio bearer is setup or reconfigured, not only the RB parameters, but also the transport channel and physical channel parameter
to be set or modified.
It is possible to modify the transport channel configuration. If this is done, the accessory RB parameters are not affected. But a transp
channel modification always has an impact on the physical channel setting. A transport channel reconfiguration is triggered with the R
message.

4. Transport Channel Reconfiguration

It is also possible to modify the physical channel characteristics of a radio bearer only. One example
is a channelisation code re-allocation. This is done with the RRC message
5. Physical Channel Reconfiguration.

Every RRC request, which is mentioned above, can be conducted successfully or fail.

Physical Channel Reconfiguration-on existing RBs

lease them. RB Setup, Reconfiguration, and Release

channel and physical channel parameters have

parameters are not affected. But a transport

nel reconfiguration is triggered with the RRC

xample

Transport Channel Reconfiguration-on existing RBs

Bs
Click to return to main page

Measurement procedures
The UE measurements are grouped into 7 different categories, according to what the UE should measure. (TS 25.331-360)
The different types of measurements are:
- Intra-frequency measurements: measurements on downlink physical channels at the same frequency as the active set.
- Inter-frequency measurements: measurements on downlink physical channels at frequencies that differ from the frequency of th
- Inter-RAT measurements: measurements on downlink physical channels belonging to another radio access technology than UTR
- Traffic volume measurements: measurements on uplink traffic volume.
- Quality measurements: Measurements of quality parameters, e.g. downlink transport block error rate.
- UE-internal measurements: Measurements of UE transmission power and UE received signal level.
- UE positioning measurements: Measurements of UE position.

The UE shall support a number of measurements running in parallel. The UE shall also support that each measurement is controlle

Cells that the UE is monitoring (e.g. for handover measurements) are grouped in the UE into three different categories:
1. Cells, which belong to the active set: User information is sent from all these cells. In FDD, the cells in the active set are involve
2. Cells, which are not included in the active set, but are monitored according to a neighbour list assigned by the UTRAN be
3. Cells detected by the UE, which are neither included in the active set nor in the monitored set belong to the detected set. R
measurements made by UEs in CELL_DCH state.

Measurement Control and Measurement Report

UTRAN controls the measurements in the UE, either by :

-broadcasting system information on the BCCH, and/or by
-transmitting a Measurement Control message on the DCCH.

If the UE is in the RRC idle mode, it receives relevant measurement information from the BCCH. The SIB type 3 contains parame
11are read and valid in the RRC idle state.

If the UE is in the RRC sub-states CELL_FACH, CELL_PCH and URA_PCH, it is connected to one cell only and responsible for
type 4. The measurement control information is broadcasted with SIB type 12. SIB 4 and SIB 12 are read and valid, when the UE is
not broadcasted, then SIB 3 resp. SIB 11 parameters are used instead. In the sub-state CELL_DCH, the UE is not reading the SIB
be still valid in this state.

If the UE is in the RRC sub state CELL_DCH ,the RRC message Measurement Control can be transmitted to the UE. This mess
measurement command links a measurement with a measurement identity, quantity, objects, reporting quantities, reporting criteria,

How does a UE perform measurements after a transition in the CELL_DCH state. Two cases have to be distinguished:
1. Transition from the RRC idle state to the CELL_DCH sub-state
In the RRC idle state, the UE retrieved the measurement control parameters from the SIB type 11. Information Elements, which con
system information, may be included in the SIB 11. If they are included, the UE can send a measurement report, when a measurem
Control message including one of the above mentioned measurement types, it replaces its internal stored data based on the SIB11

2.Transition from the CELL_FACH to the CELL_DCH sub-state.

In the CELL_FACH sub-state, the SIB 12 (or SIB 11, if there is no SIB 12) is valid including all relevant measurement control param
valid, as long as there was no Measurement Control message, which replaces the parameters. But what happens, if the UE was in
it then transits to the CELL_FACH sub-state. In the CELL_FACH sub-state, the UE reads SIB 12 (SIB 11), and its measurement con
CELL_DCH sub-state, the UE resumes with the measurements and associated reporting, as they they were stored before the transi
2.Transition from the CELL_FACH to the CELL_DCH sub-state.
In the CELL_FACH sub-state, the SIB 12 (or SIB 11, if there is no SIB 12) is valid including all relevant measurement control param
valid, as long as there was no Measurement Control message, which replaces the parameters. But what happens, if the UE was in
it then transits to the CELL_FACH sub-state. In the CELL_FACH sub-state, the UE reads SIB 12 (SIB 11), and its measurement con
CELL_DCH sub-state, the UE resumes with the measurements and associated reporting, as they they were stored before the transi

Measurement Control Contents

UTRAN may control a measurement in the UE either by broadcast system information and/or by transmitting a MEASUREM

1. Measurement identity: A reference number that should be used by the UTRAN when setting up, modifying or releasing the mea
2. Measurement command: One out of three different measurement commands.
- Setup: Setup a new measurement.
- Modify: Modify a previously defined measurement, e.g. to change the reporting criteria.
- Release: Stop a measurement and clear all information in the UE that are related to that measurement.
3. Measurement type: One of the types listed above describing what the UE shall measure.Presence or absence of the following c
4. Measurement objects: The objects the UE shall measure, and corresponding object information.
5. Measurement quantity: The quantity the UE shall measure. This also includes the filtering of the measurements.
6. Reporting quantities: The quantities the UE shall include in the report in addition to the quantities that are mandatory to report fo
7. Measurement reporting criteria: The triggering of the measurement report, e.g. periodical or event-triggered reporting.
8. Measurement Validity: Defines in which UE states the measurement is valid.
9. Measurement reporting mode: This specifies whether the UE shall transmit the measurement report using AM or UM RLC.
10. Additional measurement identities: A list of references to other measurements. When this measurement triggers a measurem
referenced by the additional measurement identities.
5. Measurement quantity: The quantity the UE shall measure. This also includes the filtering of the measurements.
6. Reporting quantities: The quantities the UE shall include in the report in addition to the quantities that are mandatory to report fo
7. Measurement reporting criteria: The triggering of the measurement report, e.g. periodical or event-triggered reporting.
8. Measurement Validity: Defines in which UE states the measurement is valid.
9. Measurement reporting mode: This specifies whether the UE shall transmit the measurement report using AM or UM RLC.
10. Additional measurement identities: A list of references to other measurements. When this measurement triggers a measurem
referenced by the additional measurement identities.

Reception of Measurement Control by the UE

The UTRAN may request a measurement by the UE to be setup, modified or released with a MEASUREMENT CONTROL message
UE.

When a new measurement is initiated, UTRAN should set the IE "Measurement identity" to a value, which is not used for other mea
"Measurement type", "Measurement object" can be set differently for each measurement with different "Measurement identity ".
When a current measurement is modified or released, UTRAN should set the IE "Measurement identity" to the value, which is used
than modifying IEs, and the UE continues to use the current values of the IEs that are not modified.

Upon reception of a MEASUREMENT CONTROL message the UE shall perform following actions :
The UE shall:
- read the IE "Measurement command";
if the IE "measurement command" has the value "setup":
- store this measurement in the variable MEASUREMENT_IDENTITY according to the IE "measurement identity";
- for measurement types "inter-RAT measurement" or "inter-frequency measurement":
-->if, according to its measurement capabilities, the UE requires compressed mode to perform the measurements and a compresse
simultaneously activated by the IE "DPCH compressed mode status info"; or
-->if, according to its measurement capabilities, the UE does not require compressed mode to perform the measurements: begin m
identity;
- for any other measurement type: begin measurements according to the stored control information for this measurement identity.
if the IE "Measurement command" has the value "modify":
- for all measurement control present in the MEASUREMENT CONTROL message:
--> replace the corresponding information stored in variable MEASUREMENT_IDENTITY associated to the identity indicated by the
--> resume the measurements according to the new stored measurement control information.
if the IE "measurement command" has the value "release":
- terminate the measurement associated with the identity given in the IE "measurement identity";
- clear all stored measurement control information related associated to this measurement identity in variable MEASUREMENT_IDE
if the IE "DPCH Compressed Mode Status Info" is present, the UE shall:
- if pattern sequence corresponding to IE "TGPSI" is already active (according to "TGPS Status Flag"): deactivate this pattern seque
received in the message;
- after the time indicated by IE "TGPS reconfiguration CFN" has elapsed:
-->activate the pattern sequence stored in the variable TGPS_IDENTITY corresponding to each IE "TGPSI" for which the "TGPS sta
-->begin the inter-frequency and/or inter-RAT measurements corresponding to the pattern sequence measurement purpose of each
-->if the values of IE "TGPS reconfiguration CFN" and IE "TGCFN" are equal:start the concerned pattern sequence immediately at t

- not alter pattern sequences stored in variable TGPS_IDENTITY, but not identitifed in IE "TGPSI"
- clear the entry for the MEASUREMENT CONTROL message in the table "Accepted transactions" in the variable TRANSACTIONS
- And the procedure ends.

Measurement Report Procedures

The purpose of the measurement reporting procedure is to transfer measurement results from the UE to UTRA
Initiation:
In CELL_DCH state, the UE shall transmit a MEASUREMENT REPORT message on the uplink DCCH when the repo
measurements that are being performed in the UE.

In CELL_FACH state, the UE shall transmit a MEASUREMENT REPORT message on the uplink DCCH when the rep
traffic volume measurement that is being performed in the UE.

In CELL_PCH or URA_PCH state, the UE shall first perform the cell update procedure, using the cause "uplink data t
MEASUREMENT REPORT message on the uplink DCCH when the reporting criteria stored in variable MEASUREME
performed in the UE.

The reporting criteria are fulfilled if either:

- the first measurement has been completed for a newly initiated measurement with periodic reporting; or
- the time period indicated in the stored IE "Periodical reporting" has elapsed since the last measurement report was tr
- an event in stored IE "Measurement reporting criteria" was triggered. Events and triggering of reports for different me
For the measurement, which triggered the MEASUREMENT REPORT message, the UE shall:
- set the IE "measurement identity" to the measurement identity, which is associated with that measurement in variable
In CELL_PCH or URA_PCH state, the UE shall first perform the cell update procedure, using the cause "uplink data t
MEASUREMENT REPORT message on the uplink DCCH when the reporting criteria stored in variable MEASUREME
performed in the UE.

The reporting criteria are fulfilled if either:

- the first measurement has been completed for a newly initiated measurement with periodic reporting; or
- the time period indicated in the stored IE "Periodical reporting" has elapsed since the last measurement report was tr
- an event in stored IE "Measurement reporting criteria" was triggered. Events and triggering of reports for different me
For the measurement, which triggered the MEASUREMENT REPORT message, the UE shall:
- set the IE "measurement identity" to the measurement identity, which is associated with that measurement in variable
- set the IE "measured results" to include measurements according to the IE "reporting quantity" of that measurement
--> if all the reporting quantities are set to "false": not set the IE "measured results";
- set the IE "Measured results" in the IE "Additional measured results" according to the IE "reporting quantity" for all m
"additional measurements" stored in variable MEASUREMENT_IDENTITY of the measurement that triggered the mea
--> if more than one additional measured results are to be included:sort them in ascending order according to their IE "
- if the MEASUREMENT REPORT message was triggered by an event (i.e. not a periodical report):set the IE "Event re
The UE shall:
- transmit the MEASUREMENT REPORT message on the uplink DCCH using either AM or UM RLC according to the s
that triggered the report.
When the MEASUREMENT REPORT message has been submitted to lower layers for transmission:
-The procedure ends.
measure. (TS 25.331-360)

as the active set.

er from the frequency of the active set.
ccess technology than UTRAN, e.g. PDC or GSM.

h measurement is controlled and reported independently of every other measurement.

e different categories:
in the active set are involved in soft handover.
assigned by the UTRAN belong to the monitored set.

RLFail
elong to the detected set. Reporting of measurements of the detected set is only required for intra-frequency

SIB type 3 contains parameters for cell selection and re-selection. In parallel, the SIB type 11 is used to deliver measurement control information to the U

ll only and responsible for cell selection and re-selection. It retrieves the parameters for cell selection from SIB
d and valid, when the UE is in the CELL_FACH, CELL_PCH and URA_PCH sub-state. If SIB 4 resp. SIB 12 is
e UE is not reading the SIB type 3/4 and 11/12. The parameters of SIB 12 (SIB 11, if SIB is not available) can

mitted to the UE. This message informs the UE about the type of measurement, which has to be conducted. Each
uantities, reporting criteria, type, etc.

to be distinguished:

In-sync
mation Elements, which contain intra-frequency, inter-frequency, inter-RAT and traffic volume measurement
t report, when a measurement reporting criteria is fulfilled. As soon as the UE receives a Measurement
ed data based on the SIB11 by the parameters delivered with the Measurement Control message.

easurement control parameters. If the UE transits to the CELL_DCH sub-state, the system information stays
happens, if the UE was in the CELL_DCH sub-state, it has received Measurement Control messages, and
), and its measurement control parameters become valid. But when the UE then transits back to the
ere stored before the transition to the CELL_FACH (or any other RRC connected) sub-state.
 In-sync
The Measurement Control is used to setup, to modify, and to release a measurement in the UE.
The UE gets all relevant information, how to perform a specific type of measurements. A measurement is either
conducted periodically or driven by an event. Then, the UE returns a measurement report. The Measurement
Control message is transmitted on a DCCH via an RLC entity in the acknowledged mode. I.e. the UE is either in

s ta e
the RRC connected sub-state CELL_DCH or CELL_FACH. If the setup of a measurement fails, the UE returns
the RRC message Measurement Control Failure. It is transmitted on an UL DCCH via an RLC entity in the acknowled

The RRC message Measurement Report was specified to deliver measurement results from the UE to UTRAN
(RNC). This message is transmitted on a DCCH. The RLC entity can be in the acknowledged or unacknowledged
mode. The RLC entity mode is set by the RRC message Measurement Control. Measurement results can be only
transmitted in the CELL_DCH or CELL_FACH sub-state.

- CELL_DCH: If a reporting criterion is met, the UE transmits a Measurement Report. A measurement identity
identifies the measurement as specified by UTRAN. It includes measurement quantities and identifies the
measurement event.
-CELL_FACH: In this sub-state, traffic volume measurements and positioning measurements are reported by the
UE. Intra-frequency measurements are reported via the RACH, whereby the UE learns from the BCCH (SIB11 or
SIB12) the maximum numbers of cells, it can report.
-CELL_PCH or URA_PCH: UE must perform a cell update. Cell update cause is uplink data transmission. Then
they are in the CELL_FACH state, where the Measurement Report can be sent. The measurement report either
holds traffic volume measurements or positioning measurements.

There is a set of different types of measurements, which can be conducted:

-Intra-Frequency Measurements
-Inter-Frequency Measurements
-Inter-RAT Measurements
-UE-Internal Measurements
-Traffic Volume Measurements
-Quality Measurements
-UE Positioning Methods
As a consequence, a UE may be forced to conduct several different types of measurem
measurement is identified by an allocated Measurement Identity. Some measureme
continuously.
UTRAN tells the UE once, how to perform a type of measurements. Whenever necessa
the measurements of a measurement type by just telling it

RLRes
the associated measurement identity.

In the RRC message Measurement Control, the is an PhyCH information elements, whe
the UE can gain DPCH compressed mode status information

ansmitting a MEASUREMENT CONTROL message. The latter message includes the following measurement control information:

ifying or releasing the measurement and by the UE in the measurement report.

absence of the following control information depends on the measurement type

surements.
t are mandatory to report for the specific event.
riggered reporting.

using AM or UM RLC.
ement triggers a measurement report, the UE shall also include the reporting quantities for the measurements
MENT CONTROL message, which is transmitted on the downlink DCCH using AM RLC.The UTRAN should take the UE capabilities into account when

h is not used for other measurements. UTRAN may use several "Measurement identity" for the same "Measurement type". In case of setting several "M
Measurement identity ".
to the value, which is used for the measurement being modified or released. In case of modifying IEs within a "Measurement identity", it is not needed

identity";

urements and a compressed mode pattern sequence with an appropriate measurement purpose is

e measurements: begin measurements according to the stored control information for this measurement

is measurement identity.

he identity indicated by the IE "measurement identity";

able MEASUREMENT_IDENTITY.

eactivate this pattern sequence at the beginning of the frame indicated by IE "TGPS reconfiguration CFN"

SI" for which the "TGPS status flag" is set to "active" at the time indicated by IE "TGCFN"; and
asurement purpose of each activated pattern sequence;
sequence immediately at that CFN;

variable TRANSACTIONS;

ts from the UE to UTRAN.

nk DCCH when the reporting criteria stored in variable MEASUREMENT_IDENTITY are met for any ongoing

link DCCH when the reporting criteria stored in variable MEASUREMENT_IDENTITY are met for any ongoing

the cause "uplink data transmission", in order to transit to CELL_FACH state and then transmit a
variable MEASUREMENT_IDENTITY are fulfilled for any ongoing traffic volume measurement which is being

eporting; or
easurement report was transmitted for a given measurement; or
f reports for different measurement types
hall:
measurement in variable MEASUREMENT_IDENTITY;
 RLFailure
ement control information to the UE for the serving cell. SIB 3 and SIB

ync Out-of-sync
 ync Out-of-sync
nt in the UE.
s. A measurement is either
eport. The Measurement
ode. I.e. the UE is either in

ate stae
ement fails, the UE returns
a an RLC entity in the acknowledged mode.

lts from the UE to UTRAN

wledged or unacknowledged
surement results can be only

. A measurement identity
es and identifies the

rements are reported by the

ns from the BCCH (SIB11 or

link data transmission. Then

measurement report either

ch can be conducted:

l different types of measurements simultaneously. Each type of

Identity. Some measurements are not conducted

rements. Whenever necessary, it just informs the UE to conduct

RLRestore
CH information elements, where
on

ontrol information:
UE capabilities into account when a measurement is assigned to the

ype". In case of setting several "Measurement identity" within a same

ement identity", it is not needed for UTRAN to indicate the IEs other

ng

oing

eing
Click to return to main page

Paging

In UTRAN, we distinguish two different types of paging, depending on the existence of a RL connection between UE and UTRAN

Paging Type 1 -The RRC message Paging Type 1 is used, when a paging message has to be transmitted to a UE, which is either in the
CELL_PCH or URA_PCH. There are several reasons, why this paging message type is initiated.

-Upper layers request the setup of an RRC signalling connection. This may be the cause, when a paging message from the CN has to be
Cause to the the paging message. Higher layers may also initiate paging, when user data has to be transmitted on an existing ps connec
UEs in the CELL_PCH and URA_PCH sub-states to establish a connection before forwarding the user data.

-UTRAN wants to trigger a cell update for UEs in the CELL_PCH or URA_PCH sub-state.
-UTRAN wants to notify UEs in the RRC idle mode and in the RRC connected mode CELL_PCH and URA_PCH about system informatio

The UE monitors the paging channels (S-CCPCHs carrying PCCH) on all paging occasions. If the UE receives a paging message, it read
message. If so, it returns a paging response. The UTRAN may repeat the transmission of a PAGING TYPE 1 message to a UE on sever
occasion on the to increase the probability of proper reception of a page

Paging Type 2- This RRC message is used, when the UE is in the CELL_DCH or CELL_FACH state, i.e., when at least dedicated contr
One example: The user is serving in the Internet, and due to the high download, the RNC has allocated one DDCH and one DCCH to the
SGSN exists, and between the two network elements, dedicated transmission resources are available for the user. While the subscriber
message to all RNCs, which participate in the LA where the UE is registered. This paging message is received by a RNC, which is curren
paging request to the UE. Therefore, Paging Type 2 is often called dedicated paging.

Paging Message Type 1

Paging Message Type 2
 Paging includes CN orignated paging and UTRAN originated paging

The CN originated paging precedure: is used to establish a signaling connection. It is divided into co-ordination paging and non co-ordinatio
CN indicates in the RANAP paging message whether the RNC shall
perform the UTRAN co-ordination paging
-Co-ordination paging, the RNC shall check whether the UE has other CN domain signaling connections
besides the paging domain connection. If so and the UE is in Cell_DCH or Cell_FACH state, the paging
message shall be transmitted on the already connected DCCH on the radio interface. if so and the UE is in Cell_PCH or URA_PCH state,the
message shall be transmitted on the PCCH on the radio interface. If no, the paging message shall be transmitted on the PCCH.
-Non-co-ordinating paging, the RNC need not check whether the UE has other CN domain signaling connections
besides the paging domain connection but directly transmit the paging message on the PCCH in the CN
specified paging area.

The UTRAN orignated paing : The UTRAN may initiate paging for a UE in Cell_PCH or URA_PCH state to trgiger
a cell update procedure to enable the transition to Cell_FACH state. In additon,the UTRAN may initiate paging for
a UE to trigger reading of updated system information.

For a UE in idle mode or in CELL_PCH or URA_PCH state, the RNC initiates the paging procedure by transmitting
a PAGING TYPE 1 message on the PCCH. For a UE in CELL_FACH or CELL_DCH state, the RNC initiates the
paging procedure by transmitting a PAGING TYPE 2 message on the DCCH

tion between UE and UTRAN.

o a UE, which is either in the RRC idle mode, or in the RRC connected mode sub-states

essage from the CN has to be forwarded to the UE. . In this case, the UE adds the IE Paging
tted on an existing ps connection (PMM-IDLE or PMM-CONNECTED). UTRAN has to page the
.

PCH about system information changes.

ves a paging message, it reads the UE identity to check, whether it is the receiver of the
1 message to a UE on several paging occasions message on an appropriate paging

when at least dedicated control channel resources were allocated to the UE.
DDCH and one DCCH to the user. Consequently, a connection between the UE and the 3G-
e user. While the subscriber is serving, he receives a call. The 3G-MSC is sending a paging
ved by a RNC, which is currently serving the UE. It then uses the existing DCCH to forward the

Click to return to main page

"Or"

Click to return to main page

 >>Paging Procedure and Parameters Description (Module II)

o-ordination paging and non co-ordination paging. The

ions
ng
E is in Cell_PCH or URA_PCH state,the paging
transmitted on the PCCH.
g connections
CN

tate to trgiger
e paging for

y transmitting
nitiates the
Click to return to main page

System Information (3GPP-25.331)

1 Master Information Block (MIB)

2 Scheduling Block (SB)

1. System Scheduling Block 1 (SB1)

2. System Scheduling Block 2 (SB2)

3 System Information Block (SIB)
1. System Information Block 1 (SIB1)

2. System Information Block 2 (SIB2)

3. System Information Block 3 (SIB3)

4. System Information Block 5 (SIB5)

5. System Information Block 7 (SIB7)

6. System Information Block 11 (SIB11)

According to 3GPP,there are total 18 SIBs , however in Huawei RAN 10, the SIBs 1, 3, 5, 6, 7, 11 are
support. The optional SIBs-2,4,12 and 18 can be added by cell parameter "SIB switch". Below show
example of MML commaned,

CELLSIBSWITCH:CELLID=X, SIBCFGBITMAP=SIB2-1&SIB4-1&SIB12-1&SIB18-1;
(The SIB switch is only valid for SIB2,SIB4,SIB12 and SIB18)

System Information Structure

The system information is organised as a tree. A Master

Information Block(MIB) gives references and scheduling information to a number of
system information blocks in a cell. The System Information Blocks (SIBs) contain the
actual system information. The master information block may optionally also contain
reference and scheduling information to one or two scheduling blocks(SBs), which give
references and scheduling information for additional system information blocks. Scheduling
information for a system information block may only be included in either the master
information block or one of the scheduling blocks.
The system information is organised as a tree. A Master
Information Block(MIB) gives references and scheduling information to a number of
system information blocks in a cell. The System Information Blocks (SIBs) contain the
actual system information. The master information block may optionally also contain
reference and scheduling information to one or two scheduling blocks(SBs), which give
references and scheduling information for additional system information blocks. Scheduling
information for a system information block may only be included in either the master
information block or one of the scheduling blocks.

System Information Monitor Mechanism

1. For a SIB containing dynamic parameters (SIB7, SIB8, SIB9, SIB14, and SIB17), the scheduling
occasion information is described in the scheduling information included in MIB or SB. The UE
regularly reads the SIB on each occasion based on Timer
2. For a SIB containing static parameters (SIB1SIB6, SIB10SIB13, SIB15, SIB16, and SIB18) is
identified by a value tag. A value tag is included in MIB or SB as a part of the scheduling information.
The UE checks whether the value tag for a SIB is different from that for the SIB the UE last reads.If
so, the UE shall re-read the SIB. Therefore, the UE can know by monitoring the MIB whether a SIB
containing static parameters is updated

System Information Broadcast

( ) System Information
UTRAN

NBAP: BCCH RNC

Information
Node B
UE

UTRAN sends a SYSTEM INFORMATION message to UE . The message contain the scheduling
information, area scope, system information content and so on.

The RRC layer in UTRAN performs segmentation and concatenation of encoded system information
blocks. If the encoded system information blocks is larger than the size of a SYSTEM INFORMATION
message,
it will be segmented and transmitted in several messages.

If the encoded system information blocks is smaller than the size of a SYSTEM INFORMATION
message, UTRAN may concatenate several system information blocks, or the first segment or the last
segment into the same message

The UE shall read SYSTEM INFORMATION messages broadcast on a

BCH transport channel in idle mode and in the connected mode in states
CELL_FACH, CELL_PCH, URA_PCH and CELL_DCH (TDD only).
In addition, UEs which support simultaneous reception of one SCCPCH and one DPCH shall read
system information on a FACH transport channel when in CELL_DCH state.
In Idle mode and connected mode different combinations of SIBs are valid. The UE may store SIBs for
different cells and different PLMNs for
later use when the UE returns to these cells or PLMNs

System Information Update

Each step is explained as follows:
1) The RNC sends a NBAP: SYSTEM INFORMATION UPDATE REQUEST message to the
associated NodeB, requesting for system information broadcst.
2) The NodeB returns a NBAP:SYSTEM INFORMATION UPDATE RESPONSE message to the
RNC,confirming the system information broadcast
3) 4) 5) The NodeB sends SYSTEM INFORMATION messages on the air interface
 System information block Area scope

Master information block Cell

Scheduling block 1
Cell
Scheduling block 2

System information block type 1 PLMN

System information block type 2 Cell

System information block type 3 Cell

System information block type 4 Cell

System information block type 5 Cell

System information block type 6 Cell

System information block type 7 Cell

System information block type 8 Cell

System information block type 9 Cell

System information block type 10 Cell

System information block type 11 Cell

System information block type 12 Cell

System information block type 13 Cell

System information block type 13.1 Cell
System information block type 13.2 Cell
System information block type 13.3 Cell

System information block type 13.4 Cell

System information block type 14 Cell

System information block type 15 Cell

System information block type 15.1 Cell

System information block type 15.2 Cell

System information block type 15.3 PLMN

System information block type 15.4 Cell

System information block type 16 PLMN

System information block type 17 Cell

System Information Block type 18 Cell

System Information Modification Notification

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
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
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
occurrence (based on Timer). Scheduling information is used to inform the UE, where and when a specific system information is transmitted.

There are two ways of notifying a UE of system information modification: by a value tag and by a timer

1) Notification by a Value Tag

For SIBs using value tags, UTRAN should notify the new value tag for the MIB to the UE.
- To notify a UE in idle mode, CELL_PCH state or URA_PCH state, UTRAN send a PAGING TYPE 1 message on the PCCH on all paging o
transmit the new MIB value tag.
- To notify a UE in CELL_FACH state, UTRAN sends a SYSTEM INFORMATION CHANGE INDICATION message on the BCCH to transmit
Upon reception of the PAGING TYPE 1 message or SYSTEM INFORMATCHANGE INDICATION message from UTRAN, the UE shall re
according to the new MIB value tag.

2) Notification by a Timer

Other types of SIBs have timers respectively. When the timer expires, the UE shall consider the stored system information content invalid,star
new SIB information. Notification by a Timer consider the stored system information content invalid, start the timer, and re-acquire new SIB inf
postpone reading the SIB until the content is needed

Please note, that UEs in the CELL_DCH sub-state are addressed directly by the RNC via the Measurement Control message

Additonal Information

Actions upon reception of the Master Information Block and Scheduling Block(s):

When selecting a new cell, the UE shall read the master information block. The UE may use the pre-defined scheduling information to locate t
block in the cell.

Action upon reception of the master information block, the UE shall:

1. if the "PLMN type" in the variable SELECTED_PLMN has the value "GSM-MAP" and the IE "PLMN Type" has the value "GSM-MAP" or "GS
- check the IE "PLMN identity" in the master information block and verify that it is the selected PLMN, stored as "PLMN identity" in the variable
- if the "PLMN type" in the variable SELECTED_PLMN has the value "ANSI-41 "and the IE "PLMN Type" has the value "ANSI-41" or "GSM-MA
- store the ANSI-41 Information
2.compare the value tag in the master information block with the value tag stored for this cell and this PLMN in the variable VALUE_TAG.
3.if the value tags differ, or if no IEs for the master information block are stored: store the value tag into the variable VALUE_TAG for the mast
and store scheduling information included in the master information block;
When selecting a new cell, the UE shall read the master information block. The UE may use the pre-defined scheduling information to locate t
block in the cell.

Action upon reception of the master information block, the UE shall:

1. if the "PLMN type" in the variable SELECTED_PLMN has the value "GSM-MAP" and the IE "PLMN Type" has the value "GSM-MAP" or "GS
- check the IE "PLMN identity" in the master information block and verify that it is the selected PLMN, stored as "PLMN identity" in the variable
- if the "PLMN type" in the variable SELECTED_PLMN has the value "ANSI-41 "and the IE "PLMN Type" has the value "ANSI-41" or "GSM-MA
- store the ANSI-41 Information
2.compare the value tag in the master information block with the value tag stored for this cell and this PLMN in the variable VALUE_TAG.
3.if the value tags differ, or if no IEs for the master information block are stored: store the value tag into the variable VALUE_TAG for the mast
and store scheduling information included in the master information block;
4. if the value tags are the same the UE may use stored system information blocks and scheduling blocks using value tag that were stored in
valid system information.

For all system information blocks or scheduling blocks that are supported by the UE referenced in the master information block or t
shall perform the following actions:

1.for all system information blocks with area scope PLMN that use value tags:
->compare the value tag read in scheduling information for that system information block with the value stored within the variable VALUE_TAG
information block;
- if the value tags differ, or if no IEs for the corresponding system information block are stored,:store the value tag read in scheduling inform
information block into the variable VALUE_TAG; read and store the IEs of that system information block.
- if the value tags are the same ,the UE may use stored system information blocks using value tag that were stored in this PLMN as valid sy
2 for all system information blocks or scheduling blocks with area scope cell that use value tags:
-> compare the value tag read in scheduling information for that system information block or scheduling block with the value stored within the
that system information block or scheduling block;
- if the value tags differ, or if no IEs for the corresponding system information block or scheduling block are stored,store the value tag read in
that system information block or scheduling block into the variable VALUE_TAG; read and store the IEs of that system information block or sc
- if the value tags are the same, the UE may use stored system information blocks using value tags that were stored in this cell and this PLM
information.

For system information blocks, not supported by the UE, but referenced either in the master information block or in the scheduling blocks, th
- skip reading this system information block;
- skip monitoring changes to this system information block

Actions upon reception of system information blocks:

The UE may use the scheduling information included within the master information block and the scheduling blocks to locate each system info
acquired.
The UE should only expect one occurrence of the scheduling information for a system information block in the master information block and a
However, to enable future introduction of new system information blocks, the UE shall also be able to receive system information blocks other
within the scheduling information. The UE may ignore contents of such system information block.
If the UE
- receives a system information block in a position according to the scheduling information for the system information block; and
- this system information block uses a value tag according to the system information block type
the UE shall:
- store the content of the system information block together with the value of its value tag in the scheduling information for the system informa
- consider the content of the system information block valid until, if used, the value tag in the scheduling information for the system information
most for 6 hours after reception.
If the UE
- receives a system information block in a position according to the scheduling information for the system information block; and
- this system information block does not use a value tag according to the system information block type
the UE shall:
- store the content of the system information block; and
- start an expiration timer for that system information block type; and
- consider the content of the system information block valid until, the expiration timer expires.
If the UE
- receives a system information block at a position different from its position according to the scheduling information for the system information
- receives a system information block for which scheduling information has not been received; and
- this system information block uses a value tag according to the system information block type
the UE may:
- store the content of the system information block with a value tag set to the value NULL; and
- consider the content of the system information block as valid until it receives the same type of system information block in a position accordi
information or at most for 6 hours after reception.

If the UE does not find a scheduling block in a position where it should be according to its scheduling information, but a transport block with
at that position, the UE shall read the scheduling information for this scheduling block.

If the UE does not find the master information block in a position fulfilling (SFN mod (MIB_REP*4) = 0),(but a transport block with correct
the UE shall,
- consider the master information block as not found.
- consider the cell to be barred according to [4] and
- consider the barred cell as using the value "allowed" in the IE "Intra-frequency cell re-selection indicator", and the maximum value in the IE "
If the UE does not find a scheduling block in a position where it should be according to its scheduling information, but a transport block with
at that position, the UE shall read the scheduling information for this scheduling block.

If the UE does not find the master information block in a position fulfilling (SFN mod (MIB_REP*4) = 0),(but a transport block with correct
the UE shall,
- consider the master information block as not found.
- consider the cell to be barred according to [4] and
- consider the barred cell as using the value "allowed" in the IE "Intra-frequency cell re-selection indicator", and the maximum value in the IE "
 Main Functions

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, includin
and type. A MIB is valid in one cell. If a UE changes the cell, is must read the new cells MIB. A change of the MIB information is indicated by a value tag.

The master information block may optionally also contain reference and scheduling information to one or two scheduling blocks (SBs), which give references a
additional system information blocks. (The SBs are applied when the scheduling resources of MIB are insufficient) Scheduling information for a system informa
in either the master information block or one of the scheduling blocks

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 a
used by the UE in the RRC idle and RRC connected mode
includes URA information.
includes 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 valid in th
not broadcasted.

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

includes the configuration of physical channels. The parameters cover the PICH power offset, the AICH power offset, P-CCPCH, S-CCPCH and PRACH system
valid in the RRC connected mode , if SIB 6 is not available.

This SIB holds mostly the same data fields as SIB 5, but it is read and valid only, when the UE is in the RRC connected mode

includes rapidly changed parameters (UL interference and dynamic persistence level. This SIB holds fast changing parameters. Therefore no value tag is used
parameters periodically

includes static CPCH information of cell. Only in used FDD

includes CPCH information of cell. Only used in FDD

includes UE DCH information controlled by DRAC process. Only used in FDD

includes measurement control information of cell. The UE gets here the relevant date for traffic measurement, intra-frequency measurements, etc. It is also val
CELL_DCH, as long as the UE did not get a Measurement Control message from UTRAN and SIB 12 is not broadcasted

This SIB holds mostly the same data fields as SIB 11, but it is read and valid only, when the UE is in the RRC connected mode

includes ANSI-41 relevant information

includes UL outer loop control parameters of common and dedicated physical channels. Only used in TDD

includes information on UE-based or UE-assisted positioning method

includes parameters of radio bearer, transport channel and physical channel. These parameters are stored in UE (either in idle mode or connected mode). It u
UTRAN. RB, The parameters are used during a handover to UTRAN. Consequently, these parameters stay valid, when the UE is connected to GSM and GPR
 includes the rapid changed parameters used to configure the shared physical channel in connected mode. Only used in TDD.

includes PLMN identity of neighbor cell

n Notification
e read by the UE. This requires a lot of battery power. Therefore, a Master Information Block (MIB) was introduced, which gives references and scheduling i
n 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 onl
the corresponding system information has not been modified. Thus, there is no need for the UE to read the SIB. For the SIBs which have no value tag e.g.
tion is used to inform the UE, where and when a specific system information is transmitted.

m information modification: by a value tag and by a timer

he new value tag for the MIB to the UE.

or URA_PCH state, UTRAN send a PAGING TYPE 1 message on the PCCH on all paging occasions in the cell to

ends a SYSTEM INFORMATION CHANGE INDICATION message on the BCCH to transmit the new MIB value tag.
ge or SYSTEM INFORMATCHANGE INDICATION message from UTRAN, the UE shall read the changed information

en the timer expires, the UE shall consider the stored system information content invalid,start the timer, and re-acquire
ider the stored system information content invalid, start the timer, and re-acquire new SIB information. The UE may
ded

tate are addressed directly by the RNC via the Measurement Control message

ion Block and Scheduling Block(s):

master information block. The UE may use the pre-defined scheduling information to locate the master information

on block, the UE shall:

PLMN has the value "GSM-MAP" and the IE "PLMN Type" has the value "GSM-MAP" or "GSM-MAP and ANSI-41",:
mation block and verify that it is the selected PLMN, stored as "PLMN identity" in the variable SELECTED_PLMN.
PLMN has the value "ANSI-41 "and the IE "PLMN Type" has the value "ANSI-41" or "GSM-MAP and ANSI-41",:

n block with the value tag stored for this cell and this PLMN in the variable VALUE_TAG.
r information block are stored: store the value tag into the variable VALUE_TAG for the master information block; read
master information block;
 UE mode/state when block is valid UE mode/state when block is read

Idle mode,CELL_FACH,CELL_PCH, URA_PCH Idle mode,CELL_FACH,CELL_PCH, URA_PCH

Idle mode,CELL_FACH,CELL_PCH, URA_PCH Idle mode,CELL_FACH,CELL_PCH, URA_PCH

Idle mode,CELL_FACH,CELL_PCH, URA_PCH Idle mode,CELL_FACH,CELL_PCH, URA_PCH

Idle mode,CELL_FACH,CELL_PCH, URA_PCH,CELL_DCH Idle

URA_PCH URA_PCH

Idle mode, (CELL_FACH, CELL_PCH, URA_PCH) Idle mode, (CELL_FACH, CELL_PCH, URA_PCH)

CELL_FACH, CELL_PCH, URA_PCH CELL_FACH, CELL_PCH, URA_PCH

Idle mode, (CELL_FACH, CELL_PCH, URA_PCH, CELL_DCH Idle mode, (CELL_FACH, CELL_PCH, URA_PCH, CELL_DCH (TDD
(TDD only)) only))

CELL_FACH, CELL_PCH, URA_PCH, CELL_DCH (TDD only) CELL_FACH, CELL_PCH, URA_PCH, CELL_DCH (TDD only)

Idle mode, CELL_FACH, CELL_PCH, URA_PCH, CELL_DCH Idle mode, CELL_FACH, CELL_PCH, URA_PCH, CELL_DCH (TDD
(TDD only) only)

CELL_FACH, CELL_PCH, URA_PCH CELL_FACH, CELL_PCH, URA_PCH

CELL_FACH, CELL_PCH, URA_PCH CELL_FACH, CELL_PCH, URA_PCH

CELL_DCH CELL_DCH

Idle mode (CELL_FACH, CELL_PCH, URA_PCH, CELL_DCH) Idle mode (CELL_FACH, CELL_PCH, URA_PCH)

CELL_FACH, CELL_PCH, URA_PCH, CELL_DCH CELL_FACH, CELL_PCH, URA_PCH

Idle Mode, CELL_FACH, CELL_PCH, URA_PCH Idle Mode, CELL_FACH, CELL_PCH, URA_PCH
Idle Mode, CELL_FACH, CELL_PCH, URA_PCH Idle Mode, CELL_FACH, CELL_PCH, URA_PCH
Idle Mode, CELL_FACH, CELL_PCH, URA_PCH Idle Mode, CELL_FACH, CELL_PCH, URA_PCH
Idle Mode, CELL_FACH, CELL_PCH, URA_PCH Idle Mode, CELL_FACH, CELL_PCH, URA_PCH

Idle Mode, CELL_FACH, CELL_PCH, URA_PCH Idle Mode, CELL_FACH, CELL_PCH, URA_PCH

Idle Mode, CELL_FACH, CELL_PCH, URA_PCH, CELL_DCH Idle Mode, CELL_FACH, CELL_PCH, URA_PCH, CELL_DCH

Idle Mode, CELL_FACH, CELL_PCH, URA_PCH Idle Mode, CELL_FACH, CELL_PCH, URA_PCH
Idle Mode, CELL_FACH, CELL_PCH, URA_PCH Idle Mode, CELL_FACH, CELL_PCH, URA_PCH

Idle Mode, CELL_FACH, CELL_PCH, URA_PCH Idle Mode, CELL_FACH, CELL_PCH, URA_PCH

Idle Mode, CELL_FACH, CELL_PCH, URA_PCH Idle Mode, CELL_FACH, CELL_PCH, URA_PCH

Idle Mode, CELL_FACH, CELL_PCH, URA_PCH Idle Mode, CELL_FACH, CELL_PCH, URA_PCH

Idle Mode, CELL_FACH, CELL_PCH, URA_PCH Idle Mode, CELL_FACH, CELL_PCH, URA_PCH
CELL_FACH, CELL_PCH, URA_PCH, CELL_DCH CELL_FACH, CELL_PCH, URA_PCH, CELL_DCH

Idle mode, CELL_FACH, CELL_PCH, URA_PCH, CELL_DCH Idle mode, CELL_FACH, CELL_PCH, URA_PCH

Click to return to main page

 Modification of system
Scheduling information
information

SIB_POS = 0,SIB_REP = 8 (FDD),SIB_REP = 8, 16, 32

Value tag
(TDD),SIB_OFF=2

Specified by the IE "Scheduling information" in MIB Value tag

Specified by the IE "Scheduling information" in MIB Value tag

Specified by the IE "Scheduling information" Value tag

Specified by the IE "Scheduling information" Value tag

Specified by the IE "Scheduling information" Value tag

Specified by the IE "Scheduling information" Value tag

Specified by the IE "Scheduling information" Value tag

Specified by the IE "Scheduling information" Value tag

Expiration timer = MAX([320
Specified by the IE "Scheduling information" ms],SIB_REP *
ExpirationTimeFactor)
Specified by the IE "Scheduling information" Value tag

Specified by the IE "Scheduling information" Expiration timer = SIB_REP

Specified by the IE "Scheduling information" Expiration timer = SIB_REP

Specified by the IE "Scheduling information" Value tag

Specified by the IE "Scheduling information" Value tag

Specified by the IE "Scheduling information" Value tag

Specified by the IE "Scheduling information" Value tag
Specified by the IE "Scheduling information" Value tag
Specified by the IE "Scheduling information" Value tag

Specified by the IE "Scheduling information" Value tag

Expiration timer = MAX([320 ms],

Specified by the IE "Scheduling information"
SIB_REP * ExpirationTimeFactor)

Specified by the IE "Scheduling information" Value tag

Specified by the IE "Scheduling information" Value tag

Specified by the IE "Scheduling information" Value tag

Specified by the IE "Scheduling information" Value tag

Specified by the IE "Scheduling information" Value tag

Specified by the IE "Scheduling information" Value tag

Specified by the IE "Scheduling information" Expiration timer = SIB_REP

Specified by the IE "Scheduling information" Value tag

 Additional comment

If System information block type 4 is not broadcast in a cell, the connected mode UE shall
read System information block type 3

If system information block type 6 is not broadcast in a cell, the connected mode UE shall
read System information block type 5.
In TDD mode system information block type 7 shall only be read in CELL_DCH if shared
transport channels are assigned to the UE.

If some of the optional IEs are not included in System information block type 12, the UE
shall read the corresponding IEs in System information block type 11.

This system information block is used in TDD mode only.

For this system information block there may be multiple occurrences

For this system information block there may be multiple occurrences

For this system information block there may be multiple occurrences

This system information block is used in TDD mode only.
Master Information Block (MIB)
System Scheduling Block 1 (SB1)
System Information Block 1 (SIB1)
System Information Block 2 (SIB 2)

System Information Block 3 (SIB 3)

System Information Block 5 (SIB 5)
System Information Block 7 (SIB 7)

System Information Block 11(SIB 11)

Click to return to main page

value=hex2dec(5)=5 , hex2dec(2)=2 ,hex2dec(0)=0 --> MCC=520

value=hex2dec(0)=0 , hex2dec(1)=1 --> MNC=01

Click to return to main page
Click to return to main page

>>Paging Procedure and Parameters Description (Module II)

value=3000ms
value=3
value=40ms
value=40ms
value=0
value=250ms
value=6s
value=50
value=20s
value=30s
value=infinity

value=2000ms
value=3

value=6s
value=1

Click to return to main page

value=hex2dec(0065)=101

Click to return to main page

Cell Identity=RNCid(12bits)+Cellid(16bits)
value=0000000010110111011110010010 => RNCid=bin2dec(000000001011)=11 and Cellid=bin2dec(0111011110010

>>>Cell Selection and Reselection Algorithm and parameters description (Module II)

value=2dB(step of 2 dB)

value=10dB(step of 2 dB)
value=8dB(step of 2 dB)
value=4dB(step of 2 dB)

value=-18dBm

value= ((-58*2)+1)= 115 dBm e.g. 57 means 113 dBm; ; 13 means -25 dBm
value=4dB(step of 2 dB)

value=1s(step of 1s)

value=24dBm
>>>Cell Access Restriction parameters description (Module II)

Click to return to main page

>>>Cell Channel Power Configuration Parameters (Module II)

value=-7dB (relative to the PCPICH)

value=-6dB (relative to the PCPICH)

>>>Access Precedures and parameters description (Module II)

>>>Open Loop Power Control Algorithm and parameters description (Module II)

value=33dBm

value=-20dBm
value=2dB(step of 1 dB)
value=20attempts

value=8attempts

value=
Click to return to main page

value=-105dBm

>>>see "Parameters description"

Click to return to main page

Value= InterFreqMeasurement is unavailable

Value= IntraFreqMeasurement is based on CPICH Ec/No

>>> IntrafreqMeasurement description (Module II)

value=hex2dec(3b)=59 (Serving Cell's Primary Scrambling Code)

value=hex2dec(43)=67(Neighbour Cell's Primary Scrambling Code)

Value= InterRATMeasurement

value=0dB

value= ((-50*2)+1)= 99 dBm e.g. 57 means 113 dBm; ; 13 means -25 dBm

value=BSIC=32

value=GSM1800

value=BCCH=516
=11 and Cellid=bin2dec(0111011110010010)=30610

II)
Click to return to main page

L3 Messages - Locat
UE NodeB

1.RRC: RRC Connection Request (RACH)

Start Rx

5.ALCAP: Iub User Plane Setup

RRC Connection Establishment Timing
Start Tx

6.RRC: RRC Connection Setup (FACH)

L1 Synchonization

7.RRC: RRC Connection Setup Completed (DCH)

1.RRC: Initial Direct Transfer (MM: Location Update Request)

Optional : Authentication and Securitty Mode Control may exis

4.RRC: Downlink Direct Transfer (MM: Location Update Accept)

5.RRC: Uplink Direct Transfer

1.RRC: RRC Connection Release

 2.RRC: RRC Connection Release Complete

2.RRC: RRC Connection Release Complete

ALCAP: Iub User Plane Release

Note the following information about the procedure :

1.The RRC connection can be set up on a DCH or a CCH. This procedure takes the RRC connection set up on the DCH
example.

2 If IP transport is applied to the Iub interface, no ALCAP procedure is performed on the Iub interface after radio links ar
deleted.
 L3 Messages - Location Update Procedure
S-RNC

n Request (RACH)

2.NBAP:Radio Link Setup Req

3.NBAP:Radio Link Setup Resp.

4.NBAP:Radio Link Setup Req

5.ALCAP: Iub User Plane Setup

on Setup (FACH)

NBAP:Synchonization Indicator

etup Completed (DCH)

: Location Update Request)

Authentication and Securitty Mode Control may exist depends on Operator's setting (refer to signaling in AMR call precedures)

MM: Location Update Accept)

ect Transfer

ALCAP: Iu User Plane Release

ction Release
 Release Complete

Release Complete

3.NBAP: Radio Link Deletion

Request

4.NBAP: Radio Link Deletion

Response

ALCAP: Iub User Plane Release

edure takes the RRC connection set up on the DCH as an

s performed on the Iub interface after radio links are set up or

pdate Procedure
CN

RRC Connec

2.RANAP: Initial UE Message (MM: Location Update Request)

on Operator's setting (refer to signaling in AMR call precedures)

3.RANAP: Direct Transfer (MM: Location Update Accept)

6.RANAP: Direct Transfer

1.RANAP: Iu Release Command

ALCAP: Iu User Plane Release

2..RANAP: Iu Release Complete

RRC connec

RRC Connection Setup
>>RRC Procedure description
Location Update
Iu release
RRC connection setup procedure is performed for the UE to set up a
Triggering Conditions : The UE in idle mode intitiates the RRC connec
When the SRNC receives an RRC CONNECTION REQUEST message fro
determines whether to set up the RRC connection on a Dedicated Channe
The procedure shown is described as follows:
1.The UE sends an RRC CONNECTION REQUEST message to the SRNC
2.Based on the cause in the RRC connection request and the system reso
resources, and L1 and L2 resources. Then the SRNC sends a RADIO LINK
resources required for an RRC connection.
3.The NodeB responds with a RADIO LINK SETUP RESPONSE message
4.The SRNC uses the ALCAP protocol to set up the Iub user plane transpo
for the ATM-based Iub interface only.
5.The SRNC sends an RRC CONNECTION SETUP message to the UE th
6. UE and NodeB initiate L1 Synchronization. NodeB sends NBAP:Syncho
7. The UE sends an RRC CONNECTION SETUP COMPLETE message to
RRC connection setup procedure ends.
If the RNC judges that the RRC connection request cannot be set up (for in
indicates the reject reason in the message
The location update procedure is performed to update the location of
Triggering Conditions : An RRC connection is set up between the UE and
The procedure is described as follows:
1.The UE sends an INITIAL DIRECT TRANSFER message to the SRNC th
2.The SRNC sends an INITIAL UE MESSAGE to the CS service domain o
Mobile Subscriber Identity (TMSI),International Mobile Subscriber Identity (
routing area update. The message indicates ATTACH REQUEST and conta
3.The CN updates the location area information of the UE and saves the n
indicates LOCATION UPDATE ACCEPT and contains the TMSI that is ass
authentication and ciphering. Then, the CN sendsa DIRECT TRANSFER m
4.The SRNC transparently sends the contents of the DIRECT TRANSFER
5.The UE receives the LOCATION UPDATE ACCEPT information and sen
area update, it is the ATTACH ACCEPT information that the UE receives.
6.The SRNC transparently sends the contents of the UPLINK DIRECT TRA
For routing area update, it is ATTACH COMPLETE that the DIRECT TR
 The Iu release procedure is performed for the CN to release an Iu conn

Triggering Conditions: The Iu release procedure can be triggered in one

Serving Radio Network Subsystem (SRNS) is relocated.4.The SRNS reloc
RRC connection Release
The procedure shown is described as follows:
1.The CN sends an IU RELEASE COMMAND message to the SRNC to ini
NOTE After sending the IU RELEASE COMMAND message, the CN will no
2.The SRNC releases the related UTRAN resources and then sends an IU

The RRC Connection Release procedure is performed to release the sig

Triggering Conditions: After a n RAB is released,the SRNC judges wheth

The procedure shown is described as follows: based on the resouce oc

connection from DCH and release of an RRC connection from CCH (If an R

1.The SRNC sends an RRC CONNECTION RELEASE message to the UE

(NOTE: The SRNC may send the RRC CONNECTION RELEASE messag
SRNC. If the SRNC does not receive an RRC CONNECTION RELEASE
COMPLETE message from the UE after sending the RRC CONNECTION
2.The UE sends an RRC CONNECTION RELEASE COMPLETE message
3.The SRNC sends a RADIO LINK DELETION REQUEST message to the
4.After releasing the resources, the NodeB sends a RADIO LINK DELETIO
5.(Optional; required for the ATM-based Iub interface only) The SRNC uses
ends.
 ocedure is performed for the UE to set up a signaling connection to the SRNC. RRC connection setup is always initiated by the UE. One

he UE in idle mode intitiates the RRC connection setup procedure when the NAS of the UE requests the establishment of a signaling conne

RRC CONNECTION REQUEST message from the UE, the Radio Resource Management (RRM) module of the RNC determines whether t
the RRC connection on a Dedicated Channel (DCH)or on a Common Channel (CCH), based on a specific RRM algorithm. Typically, an RR

scribed as follows:
NNECTION REQUEST message to the SRNC through the uplink CCCH(RACH), requesting the establishment of an RRC connection.
RRC connection request and the system resource status, the SRNC determines to set up the RRC connection on a DCH and allocates the R
ources. Then the SRNC sends a RADIO LINK SETUP REQUEST message to the NodeB, requesting the NodeB to allocate the specific rad
C connection.
RADIO LINK SETUP RESPONSE message to the SRNC after successfully preparing the resources.
P protocol to set up the Iub user plane transport bearer and performs the synchronization between the SRNC and the NodeB. This procedur
ce only.
CONNECTION SETUP message to the UE through the downlink CCCH (FACH). The message contains the information about the DCH allo
Synchronization. NodeB sends NBAP:Synchonization Indicator message to SRNC when the uplink enter "In-Sync" state
NNECTION SETUP COMPLETE message to the SRNC through the uplink Dedicated Control Channel (DCCH) that is just set up. The mes
dure ends.
RC connection request cannot be set up (for instance, due to insufficient resources), it directly sends an RRC CONNECTION REJECT mess
the message

edure is performed to update the location of a UE.

RRC connection is set up between the UE and the Serving RNC (SRNC)

as follows:
IRECT TRANSFER message to the SRNC through the RRC connection. The message contains the Non Access Stratum (NAS) information
L UE MESSAGE to the CS service domain of the CN through the Iu interface. The message indicates LOCATION UPDATE REQUEST and
MSI),International Mobile Subscriber Identity (IMSI), and Location Area Identity (LAI).The SRNC sends an INITIAL UE MESSAGE to the PS
sage indicates ATTACH REQUEST and contains the Routing Area Identity (RAI)
n area information of the UE and saves the new LAI. The CN might also perform authentication and ciphering. Then, the CN sends a DIREC
E ACCEPT and contains the TMSI that is assigned to the UE.For routing area update, the CN updates the routing area information of the UE
Then, the CN sendsa DIRECT TRANSFER message to the SRNC. The message indicates ATTACH ACCEPTand contains the TMSI that is

nds the contents of the DIRECT TRANSFER message to the UE through a DOWNLINK DIRECT TRANSFER message.
TION UPDATE ACCEPT information and sends an UPLINK DIRECT TRANSFER message to the SRNC. The message contains the inform
ACCEPT information that the UE receives.
nds the contents of the UPLINK DIRECT TRANSFER messageto the CN through a DIRECT TRANSFER message. The DIRECT TRANSFE

s ATTACH COMPLETE that the DIRECT TRANSFER message indicates.

 is performed for the CN to release an Iu connection and all the UTRAN resources related only to that Iu connection.

Iu release procedure can be triggered in one of the following conditions: The transaction between the UE and the CN is complete,The UTRA
ystem (SRNS) is relocated.4.The SRNS relocation is canceled after a relocation resource allocation procedure iscomplete.

scribed as follows:
ASE COMMAND message to the SRNC to initiate the Iu release procedure. The message indicates the cause for the release of the signalin
ELEASE COMMAND message, the CN will not send further RANAP connection-oriented messages on this particular connection.
ated UTRAN resources and then sends an IU RELEASE COMPLETE message to the CN.

se procedure is performed to release the signaling connection and all radio bearers between UE and the UTRAN

a n RAB is released,the SRNC judges whether the RRC connection carries any other RAB or the UE. If judging that the RRC connection d

scribed as follows: based on the resouce occupied by the RRC connection,there are two types of RRC connection release procedure: rele
ease of an RRC connection from CCH (If an RRC connection needs to be released after a successful outgoing call,, the RRC connection on

CONNECTION RELEASE message to the UE through the DCCH.

the RRC CONNECTION RELEASE message several times to increase the probability of proper reception of the message by the UE. The
receive an RRC CONNECTION RELEASE
he UE after sending the RRC CONNECTION RELEASE message for four times, the SRNC judges that the UE has released the RRC conne
NNECTION RELEASE COMPLETE message to the SRNC.
LINK DELETION REQUEST message to the NodeB,requesting the NodeB to delete the radio link resources in the NodeB.
s, the NodeB sends a RADIO LINK DELETION RESPONSE message to the SRNC.
TM-based Iub interface only) The SRNC uses the ALCAP protocol to initiate an Iub user plane transport bearer release procedure. Then, th
ways initiated by the UE. One UE has a maximum of one RRC connection at a time.

lishment of a signaling connection

e RNC determines whether to accept or reject theRRC connection request, based on a specific algorithm. If accepting the request, the RRM
M algorithm. Typically, an RRC connection is set up on the DCH.

of an RRC connection.
on a DCH and allocates the Radio NetworkTemporary Identity(RNTI),radio
eB to allocate the specific radio link

nd the NodeB. This procedure is optional. It is required

ormation about the DCH allocated by the SRNC.

nc" state
H) that is just set up. The message indicates that the

ONNECTION REJECT message to the UE, and

ss Stratum (NAS) information to be sent to the CN by the UE.

ON UPDATE REQUEST and containsthe UE information, such as the Temporary
IAL UE MESSAGE to the PS service domain of the CN throughthe Iu interface for

Then, the CN sends a DIRECT TRANSFER message to the SRNC. The message
ing area information of the UE and savesthe new RAI. The CN might also perform
and contains the TMSI that is assigned to the UE

message.
message contains the information suchas the NAS information and the CN ID.For routing

sage. The DIRECT TRANSFER messageindicates TMSI REALLOCATION COMPLETE.

ection.

he CN is complete,The UTRAN requests the CN to release the resources on the Iu interface by, for example,sending an IU RELEASE REQ
iscomplete.

for the release of the signaling connection.

ticular connection.

AN

ng that the RRC connection does not carry other RAB of the UE,the SRNC initiates an RRC connection release procedure.

ection release procedure: release of an RRC

g call,, the RRC connection on the DCH is released and if a radio bearers fails to be setup ,the RRC connection on the CCH is released)

he message by the UE. The RRC SNs of these messages are the same. The number of retransmissions and the transmission intervals are

has released the RRC connection.)

n the NodeB.

r release procedure. Then, the RRC connection release procedure

. If accepting the request, the RRM module further
ple,sending an IU RELEASE REQUEST message,The

ease procedure.

ection on the CCH is released)

and the transmission intervals are determined by the

Click to return to main page
RRC:RRC Connection Request (RACH)
RRC:RRC Connection Setup (FACH)
RRC:RRC Connection Setup Complete (DCCH)
RANAP: Initial UE Message (MM: Location Update Request)
RRC: Initial Direct Transfer (MM: Location Update Request)
RANAP: Direct Transfer (MM: Location Update Accept)

RRC: Downlink Direct Transfer (MM: Location Update Accept)

 RRC: RRC Connection Release

.RRC: RRC Connection Release Complete

>>"RRC Connection Request Description"

>>"Geographical and UTRAN Entity Identifiers"

value=hex2dec(4)=4 , hex2dec(5)=5 ,hex2dec(6)=6 --> MCC=456

value=hex2dec(0)=0 , hex2dec(2)=2 --> MNC=02

value=hex2dec(75 AA)= 30122

value= registration(Location update)

value=(-24+ (36/2))= -6 dB (Serving cell's CPICH Ec/No)

value=hex2dec(91)=145 (Neighbour's Primary Scrambling Code)

value=CPICH Ec/Io invalid

>>"RRC Connection Setup Description"

>>"Geographical and UTRAN Entity Identifiers"

value=hex2dec(4)=4 , hex2dec(5)=5 ,hex2dec(6)=6 --> MCC=456

value=hex2dec(0)=0 , hex2dec(2)=2 --> MNC=02

value=hex2dec(75 AA)= 30122

value=UE capable to support FDD , not TDD

value=UE capable to support GSM

value=Signaling Radio Bearer Information Setup ,RB-1

value=Radio Bearer Mapping

value=Signaling Radio Bearer Information Setup ,RB-2
value=Signaling Radio Bearer Information Setup ,RB-3
value=Signaling Radio Bearer Information Setup ,RB-4
value=BLER Target= -20 dB

value=MaxAllowedULTxPower=24 dBm

value=(-37*2)= -74 dBm (step of 2 dB) Default Constant

 -22
-22
Note :DPCCH_Power_offset is configured by R

value= use Closed Loop Power Control Algorithm1

value= use long SC on Uplink

value=Spreading Factor 64 (Uplink)

value=Spreading Factor 128 (Downlink)

 value=Primary Scrambling code=385

value=Spreading Factor 128 (Downlink)

Cell Identity=RNCid(12bits)+Cellid(16bits)
value=0000000000010101101011001010 => RNCid=bin2dec(000000000001)=1 and Cellid=bin2dec(01110111100

H) >>"RRC Connection Setup Complete Description"

value= UE (Powerclass3) maximum transmitted power =24 dBm
value= support GSM (Dual Mode UMTS<>GSM)

value= Chipering Algorithm A5/3

value= support Compressed Mode (CM) uplink and downlink

pdate Request)

value= MCC=456
value= MNC=02
value=hex2dec(75AA)=30122
e Request)
Accept)

Update Accept)
e

mplete
DPCCH_Power_offset CPICH_RSCP PCPICH Power UL Interference
 -74 -80 33 -85
-74 -70 33 -85
Power_offset is configured by RNC and delivered to UE in RRC Connection Setup.
d Cellid=bin2dec(0111011110010010)=23242
UL DPCCH Initial Power
6
-4
Click to return to main page

L3 Messages - AMR Voic

UE NodeB

1.RRC: RRC Connection Request (RACH)

Start Rx

4.ALCAP: Iub User Plane Setup

RRC Connection Establishment Timing Start Tx

5.RRC: RRC Connection Setup (FACH)

L1 Synchonization

6.RRC: RRC Connection Setup Completed (DCH)

1.RRC: Initial Direct Transfer (MM: CM Service Request)

2.RRC: Downlink Direct Transfer (MM: Authentication Request)

3.RRC: Uplink Direct Transfer (MM: Authentication Response)

6.RRC: Security Mode Command

7.RRC: Security Mode Completed

 1.RRC: Uplink Direct Transfer (CC: Setup)

4.RRC: Downlink Direct Transfer (CC: Call Proceeding)

5.ALCAP: Iub User Plane Setup

6.RRC: Radio Bearer Setup

Apply new transport format set

8.RRC: Radio Bearer Setup Complete

7.RRC: Downlink Direct Transfer (CC: Alerting)

9.RRC: Downlink Direct Transfer (CC: Connect)

10.RRC: Uplink Direct Transfer (CC: Connect Acknowledge)

Call Esta

RRC:Measurement Control

RRC:Measurement Report

Intra-Frequency Soft Handover

Inter-Frequency Hard Handover

 Inter-RAT Hard Handover

1.RRC: Uplink Direct Transfer (CC: Disconnect)

4.RRC: Downlink Direct Transfer (CC: Release)

5.RRC: Uplink Direct Transfer (CC: Release Complete)

1.RRC: RRC Connection Release

2.RRC: RRC Connection Release Complete

2.RRC:RRC Connection Release Complete

5,.ALCAP: Iub User Plane Releas

Note the following information about the procedure ,

1.The RRC connection can be set up on a DCH or a CCH. This procedure takes the RRC connection set up on the DCH
an example.
2. If IP transport is applied to the Iub interface, no ALCAP procedure is performed on the
Iubinterface after radio links are set up, reconfigured, or deleted.
3. If IP transport is applied to the Iu-CS interface, no ALCAP procedure is performed on the
Iu-CS interface after an RAB is set up or a call is released
 L3 Messages - AMR Voice (MOC) Call Procedure
S-RNC

n Request (RACH)

2.NBAP:Radio Link Setup Req

3.NBAP:Radio Link Setup Resp.

4.ALCAP: Iub User Plane Setup

on Setup (FACH)

NBAP:Synchonization Indicator

etup Completed (DCH)

MM: CM Service Request)

MM: Authentication Request)

M: Authentication Response)

de Command

de Completed
ansfer (CC: Setup)

fer (CC: Call Proceeding)

3.NBAP: Radio Link Reconfiguration Prepare

4.NBAP: Radio Link Reconfiguration Ready

5.ALCAP: Iub User Plane Setup

earer Setup

7.NBAP: Radio Link Reconfiguration

Commit

Apply new transport format set

Setup Complete

ansfer (CC: Alerting)

ansfer (CC: Connect)

CC: Connect Acknowledge)

Call Established

ent Control

ent Report

oft Handover

ard Handover
Handover

sfer (CC: Disconnect)

ansfer (CC: Release)

(CC: Release Complete)

8.ALCAP: Iu User Plane Release

ction Release

Release Complete

Release Complete

3.NBAP: Radio Link Deletion

Request

4.NBAP: Radio Link Deletion

Response

5,.ALCAP: Iub User Plane Release

edure takes the RRC connection set up on the DCH as

s performed on the

re is performed on the
C) Call Procedure
CN

SCCP: CR (Connection Request)

2.RANAP: Initial UE Message (MM: CM Service Request)

3.SCCP: CC (Connection Confirm)

1.RANAP: Direct Transfer (MM: Authentication Request)

4.RANAP: Direct Transfer (MM: Authentication Response)

RANAP: Common ID (IMSI)

5.RANAP: Security Mode Command

8.RANAP: Security Mode Complete

 2.RANAP: Direct Transfer (CC: Setup)

3.RANAP: Direct Transfer (CC: Call Proceeding)

1.RANAP: RAB Assignment Request

2.ALCAP : Iu User Plane Setup

Radio Bearer Setup

9.RANAP: RAB Assignment Response

6.RANAP: Direct Transfer (CC: Alerting)

8.RANAP: Direct Transfer (CC: Connect)

11.RANAP: Direct Transfer (CC: Connect Acknowledge)

6.Conversation
 2.RANAP: Direct Transfer (CC: Disconnect)

3.RANAP: Direct Transfer (CC: Release)

6.RANAP: Direct Transfer (CC: Release Complete)

7.RANAP: Iu Release Command

8.ALCAP: Iu User Plane Release

9.RANAP: Iu Release Complete


>>RRC Procedure Description
1.RRC Connection Setup
2.Signalling Connection Setup
&Authentication.3
Security Mode Control
RRC connection setup procedure is performed for the UE to set u
connection at a time.
Triggering Conditions : The UE in idle mode intitiates the RRC conn
Management (RRM) module of the RNC determines whether to accept
algorithm. If accepting the request, the RRM module further determines
algorithm. Typically, an RRC connection is set up on the DCH.
The procedure shown is described as follows:
1.The UE sends an RRC CONNECTION REQUEST message to the SR
2.Based on the cause in the RRC connection request and the system re
Identity(RNTI),radio resources, and L1 and L2 resources. Then the SRN
required for an RRC connection.
3.The NodeB responds with a RADIO LINK SETUP RESPONSE messa
4.The SRNC uses the ALCAP protocol to set up the Iub user plane tran
for the ATM-based Iub interface only.
5.The SRNC sends an RRC CONNECTION SETUP message to the UE
6. UE and NodeB initiate L1 Synchronization. NodeB sends NBAP:Sync
7. The UE sends an RRC CONNECTION SETUP COMPLETE messag
RRC connection setup procedure ends.
If the RNC judges that the RRC connection request cannot be set up (fo
reason in the message
The signaling connection setup procedure is performed to exch
Triggering Conditons: The UE sends a direct transfer message to initi
The procedure shown is described as follows:
1.The UE sends an INITIAL DIRECT TRANSFER message to the SRNC
2.The SRNC receives the INITIAL DIRECT TRANSFER message from
to be sent to the CN by the UE. The content of the NAS information is C
3.The CN sends a response message to the SRNC.
-If accepting the request, the CN sends a CONNECTION CONFIRM (
confirms that the signaling connection is set up.
-If rejecting the request, the CN sends a CONNECTION REJECT (CJ
confirms that the signaling connection fails to be setup and then initiate
The authentication and security mode control procedure is pe
algorithm and ciphering algorithm. This procedure ensures integrity and
Triggerring Conditions: The UE and the CN exchange signaling. The
The procedure shown is described as follows:
1.The CN sends a DIRECT TRANSFER message to the SRNC. The me
2.The SRNC transparently sends the contents of the DIRECT TRANSF
3.The UE sends an UPLINK DIRECT TRANSFER message to the SRN
4.The SRNC transparently sends the contents of the UPLINK DIRECT T
Subscriber Identity Module (USIM) judges that the authentication is suc
5.The CN sends a SECURITY MODE COMMAND message to the SRN
protection algorithms.
6.The SRNC sends a SECURITY MODE COMMAND message to the U
 Triggerring Conditions: The UE and the CN exchange signaling. The

The procedure shown is described as follows:

1.The CN sends a DIRECT TRANSFER message to the SRNC. The me
2.The SRNC transparently sends the contents of the DIRECT TRANSF
3.The UE sends an UPLINK DIRECT TRANSFER message to the SRN
4.The SRNC transparently sends the contents of the UPLINK DIRECT T
Subscriber Identity Module (USIM) judges that the authentication is suc
5.The CN sends a SECURITY MODE COMMAND message to the SRN
protection algorithms.
6.The SRNC sends a SECURITY MODE COMMAND message to the U
7.The UE sends a response message to the SRNC.
-If the integrity protection and ciphering algorithms are configured
MODE COMMAND COMPLETE message to the CN.The message cont
-If the UE does not support the integrity protection and ciphering a
information and the reason for the failure. The SRNC then sends a SEC
The RANAP:Common ID message is used to transport the permane

The call setup procedure is performed to set up a call.

Radio Bearer Setup. 5 Triggering Conditions: The UE initiates a call

The procedure shown is described as follows:

4.Call Setup 1.The UE sends an UPLINK DIRECT TRANSFER message to the SRN
2.The SRNC transparently sends the contents of the UPLINK DIRECT T
3.The CN sends a DIRECT TRANSFER message to the SRNC. The me
4.The SRNC transparently sends the contents of the DIRECT TRANSF
5. A Radio Access Bearer (RAB) is set up. (see more details in RAB Se
6. When the called terminal rings, the CN sends a DIRECT TRANSFER
7.The SRNC transparently sends the contents of the DIRECT TRANSF
8.The CN sends a DIRECT TRANSFER message to the SRNC. The me
9.The SRNC transparently sends the contents of the DIRECT TRANSF
10.The UE sends an UPLINK DIRECT TRANSFER message to the SR
11.The SRNC transparently sends the contents of the UPLINK DIRECT

The Radio Bearer Setup procedure shown is described as follows:

1.The CN sends an RAB ASSIGNMENT REQUEST message to the SR
2.(Optional; applicable to the ATM-based Iu-CS interface only) The SRN
characteristic parameters. Based on the AAL2 link characteristic param
3.The SRNC sends a RADIO LINK RECONFIGURATION PREPARE m
4.The NodeB allocates the associated resources and then sends a RAD
5.(Optional; required for the ATM-based Iub interface only) The Iub ALC
by exchanging uplink and downlink synchronization frames in the DCH
6.The SRNC sends a RADIO BEARER SETUP message to the UE.
7.The SRNC sends a RADIO LINK RECONFIGURATION COMMIT mes
8.After performing the radio bearer setup, the UE sends a RADIO BEAR
9.The SRNC sends an RAB ASSIGNMENT RESPONSE message to th
The procedure when RAB Setup Failure shown is described as foll
1.The CN sends an RAB ASSIGNMENT REQUEST message to the SR
2.The SRNC sends an RAB ASSIGNMENT RESPONSE message to th

6.Conversation

The call release procedure is performed to release services and re

Triggering Conditions : A call ends and the calling party hangs up

The procedure shown is described as follows:

1.The UE sends an UPLINK DIRECT TRANSFER message to the SRN
2.The SRNC transparently sends the contents of the UPLINK DIRECT T
3.The CN sends a DIRECT TRANSFER message to the SRNC. The me
 The call release procedure is performed to release services and re

Triggering Conditions : A call ends and the calling party hangs up

The procedure shown is described as follows:

1.The UE sends an UPLINK DIRECT TRANSFER message to the SRN
2.The SRNC transparently sends the contents of the UPLINK DIRECT T
3.The CN sends a DIRECT TRANSFER message to the SRNC. The me
4.The SRNC transparently sends the contents of the DIRECT TRANSF
5.The UE sends an UPLINK DIRECT TRANSFER message to the SRN
6.The SRNC transparently sends the contents of the UPLINK DIRECT T
7.The CN sends an IU RELEASE COMMAND message to the SRNC to
8.(Optional; applicable to the ATM-based Iu-CS interface only) The ALC
9.The SRNC sends an IU RELEASE COMPLETE message to the CN.

7.Call Release

The RRC Connection Release procedure is performed to release the

Triggering Conditions: After a n RAB is released,the SRNC judges wh

The procedure shown is described as follows: based on the resouce

to be released after a successful outgoing call,, the RRC connection on
fails to be setup ,the RRC connection on the CCH is released)

1.The SRNC sends an RRC CONNECTION RELEASE message to the

(NOTE: The SRNC may send the RRC CONNECTION RELEASE mess
the same. The number of retransmissions and the transmission interva
UE after sending the RRC CONNECTION RELEASE message for four
8.RRC Connection Release
2.The UE sends an RRC CONNECTION RELEASE COMPLETE messa
3.The SRNC sends a RADIO LINK DELETION REQUEST message to
4.After releasing the resources, the NodeB sends a RADIO LINK DELE
5.(Optional; required for the ATM-based Iub interface only) The SRNC u
procedure ends.
erformed for the UE to set up a signaling connection to the SRNC. RRC connection setup is always initiated by the UE. One UE has a maxi

mode intitiates the RRC connection setup procedure when the NAS of the UE requests the establishment of a signaling connection When th
ermines whether to accept or reject theRRC connection request, based on a specific
module further determines whether to set up the RRC connection on a Dedicated Channel (DCH)or on a Common Channel (CCH),based o
et up on the DCH.

ows:
QUEST message to the SRNC through the uplink CCCH(RACH), requesting the establishment of an RRC connection.
n request and the system resource status, the SRNC determines to set up the RRC connection on a DCH and allocates the Radio NetworkT
L2 resources. Then the SRNC sends a RADIO LINK SETUP REQUEST message to the NodeB, requesting the NodeB to allocate the speci

SETUP RESPONSE message to the SRNC after successfully preparing the resources.
t up the Iub user plane transport bearer and performs the synchronization between the SRNC and the NodeB. This procedure is optional. It

SETUP message to the UE through the downlink CCCH (FACH). The message contains the information about the DCH allocated by the SR
n. NodeB sends NBAP:Synchonization Indicator message to SRNC when the uplink enter "In-Sync" state
ETUP COMPLETE message to the SRNC through the uplink Dedicated Control Channel (DCCH) that is just set up. The message indicates

equest cannot be set up (for instance, due to insufficient resources), it directly sends an RRC CONNECTION REJECT message to the UE,

edure is performed to exchange the NAS (Non Access Stratum) information between the UE and the CN.

ect transfer message to initiate the signaling connection setup procedure.

ows:
SFER message to the SRNC through the RRC connection. The message contains the initial NAS information to be sent to the CN by the UE
TRANSFER message from the UE and sends an INITIAL UE MESSAGE to the CN over the Iu interface. The INITIAL UE MESSAGE contain
of the NAS information is CM SERVICE REQUEST.
SRNC.
CONNECTION CONFIRM (CC) message to the SRNC. The message indicates that the SCCP connection is set up. After receivingthe mess
up.
ONNECTION REJECT (CJ) message to the SRNC. The message indicates that the SCCP connection fails to be set up. After receiving the
o be setup and then initiates the RRC release procedure.

e control procedure is performed for the UE and the network to implement bi-directional authentication and to negotiate and configure th
edure ensures integrity and correctness of signaling

N exchange signaling. The network initiates the authentication and securitymode control procedure

ows:
ssage to the SRNC. The message indicates AUTHENTICATION REQUEST.
ts of the DIRECT TRANSFER message to the UE through a DOWNLINK DIRECT TRANSFER message.
SFER message to the SRNC.
ts of the UPLINK DIRECT TRANSFER messageto the CN through a DIRECT TRANSFER message, indicating AUTHENTICATION RESPO
at the authentication is successful, the UE returns a message with an XRES IE.
MAND message to the SRNC to initiate the security mode control procedure. The message contains the information about the supported cip

OMMAND message to the UE to inform the UE of the integrity protection and ciphering algorithms that the UTRAN selects.
o set up a call.

all

ows:
SFER message to the SRNC. The message contains the number of the called party and the information about the bearer capability of the c
ts of the UPLINK DIRECT TRANSFER messageto the CN through a DIRECT TRANSFER message.
ssage to the SRNC. The message indicates CALL PROCEEDING and contains the information about the negotiated bearer capability of the
ts of the DIRECT TRANSFER message to the UE through a DOWNLINK DIRECT TRANSFER message.
ee more details in RAB Setup Procedure below)
nds a DIRECT TRANSFER message to the SRNC. The message indicates ALERTING.
ts of the DIRECT TRANSFER message to the UE through a DOWNLINK DIRECT TRANSFER message.
ssage to the SRNC. The message indicates CONNECT, which means that the called party has answered the call.
ts of the DIRECT TRANSFER message to the UE through a DOWNLINK DIRECT TRANSFER message.
NSFER message to the SRNC.
nts of the UPLINK DIRECT TRANSFER message to the CN through a DIRECT TRANSFER message, indicating CONNECT ACKNOWLED

n is described as follows:
QUEST message to the SRNC to initiate the RAB setup procedure.
CS interface only) The SRNC maps the Quality of Service (QoS) parameters for the RAB to the AAL2 link characteristic parameters and rad
L2 link characteristic parameters,the ALCAP on the Iu interface initiates an Iu user plane transport bearer setup procedure.
FIGURATION PREPARE message to the NodeB, requesting the NodeB to prepare for adding one or more DCHs to the existing radio links f
rces and then sends a RADIO LINKRECONFIGURATION READY message to the SRNC.
interface only) The Iub ALCAP at the SRNC initiates an Iub user plane transport bearer setup procedure. The NodeB and the SRNC perform
nization frames in the DCH frame protocol.
UP message to the UE.
FIGURATION COMMIT message to theNodeB.
e UE sends a RADIO BEARER SETUP COMPLETE message to the SRNC.
RESPONSE message to the CN. The RAB isset up.
hown is described as follows:
QUEST message to the SRNC to initiate the RAB setup procedure.
RESPONSE message to the CN. The message indicates the ID of the RAB that fails to be set up and the reason for the failure.

to release services and resources after a call ends.

e calling party hangs up

ows:
SFER message to the SRNC.
ts of the UPLINK DIRECT TRANSFER messageto the CN through a DIRECT TRANSFER message, indicating DISCONNECT. This conten
ssage to the SRNC. The message indicates RELEASE to request release of the call.
is performed to release the signaling connection and all radio bearers between UE and the UTRAN

eased,the SRNC judges whether the RRC connection carries any other RAB or the UE. If judging that the RRC connection does not carry o

ows: based on the resouce occupied by the RRC connection,there are two types of RRC connection release procedure: release of an RRC
all,, the RRC connection on the DCH is released and if a radio bearers
CCH is released)

RELEASE message to the UE through the DCCH.

NNECTION RELEASE message several times to increase the probability of proper reception of the message by the UE. The RRC SNs of th
nd the transmission intervals are determined by the SRNC. If the SRNC does not receive an RRC CONNECTION RELEASE COMPLETE m
RELEASE message for four times, the SRNC judges that the UE has released the RRC connection.)

LEASE COMPLETE message to the SRNC.

ON REQUEST message to the NodeB,requesting the NodeB to delete the radio link resources in the NodeB.
ends a RADIO LINK DELETION RESPONSE message to the SRNC.
interface only) The SRNC uses the ALCAP protocol to initiate an Iub user plane transport bearer release procedure. Then, the RRC connec
he UE. One UE has a maximum of one RRC

naling connection When the SRNC receives an RRC CONNECTION REQUEST message from the UE, the Radio Resource

on Channel (CCH),based on a specific RRM

ection.
ocates the Radio NetworkTemporary
odeB to allocate the specific radio link resources

his procedure is optional. It is required

he DCH allocated by the SRNC.

up. The message indicates that the

JECT message to the UE, and indicates the reject

e sent to the CN by the UE.

TIAL UE MESSAGE contains the NAS information

up. After receivingthe message, the SRNC

set up. After receiving the message, the SRNC

negotiate and configure the integrity protection

AUTHENTICATION RESPONSE. If the UMTS

on about the supported ciphering and integrity

N selects.
e bearer capability of the call.

ted bearer capability of the call.

CONNECT ACKNOWLEDGE.

teristic parameters and radio resource

rocedure.
to the existing radio links for carrying the RAB.

deB and the SRNC perform synchronization

for the failure.

DISCONNECT. This content informs the CN that the UE has hanged up.
onnection does not carry other RAB of the UE,the SRNC initiates an RRC connection release procedure.

ocedure: release of an RRC connection from DCH and release of an RRC connection from CCH (If an RRC connection needs

he UE. The RRC SNs of these messages are

N RELEASE COMPLETE message from the

re. Then, the RRC connection release

Click to return to main page
RRC:RRC Connection Request (RACH)
RRC:RRC Connection Setup (FACH)
RRC:RRC Connection Setup Complete (DCCH)
RRC: Initial Direct Transfer (MM: CM Service Request)
RANAP:Initial UE Message (MM: CM Service Request)

RANAP: Direct Transfer (MM: Authentication Request)

RRC: Downlink Direct Transfer (MM: Authentication Request)

RRC: Uplink Direct Transfer (MM: Authentication Response)

RANAP: Direct Transfer (MM: Authentication Response)

RRC: Security Mode Command

 RRC: Security Mode Complete

RANAP: Direct Transfer (CC: Setup)

RRC: Uplink Direct Transfer (CC: Setup)
RRC: Downlink Direct Transfer (CC: Call Proceeding)

RANAP: Direct Transfer (CC: Call Proceeding)

RRC: Radio Bearer Setup

RRC: Radio Bearer Setup Complete
 RANAP: Direct Transfer (CC: Alerting)

RRC: Downlink Direct Transfer (CC: Alerting)

 RANAP: Direct Transfer (CC: Connect)

RRC: Downlink Direct Transfer (CC: Connect)

RANAP: Direct Transfer (CC: Connect Acknowledge)

RRC: Uplink Direct Transfer (CC: Connect Acknowledge)

RANAP: Direct Transfer (CC: Disconnect)

RRC: Uplink Direct Transfer (CC: Disconnect)

 RANAP: Direct Transfer (CC: Release)

RRC: Downlink Direct Transfer (CC: Release)

 RANAP: Direct Transfer (CC: Release Complete)

RRC: Uplink Direct Transfer (CC: Release Complete)

 RRC: Downlink Direct Transfer (CC: RRC Connection Release)

RRC: Uplink Direct Transfer (CC: RRC Connection Release Complete)

>>"RRC Connection Request Description"

>>"Geographical and UTRAN Entity Identifiers"

value=hex2dec(5)=5 , hex2dec(2)=2 ,hex2dec(0)=0 --> MCC=520

value=hex2dec(0)=0 , hex2dec(1)=1 --> MNC=01

value=hex2dec(2908)= 10504

value= OriginatingConversationalcall (CS MOC)

value=(-24+ (43/2))=-2.5 dB

value=hex2dec(60)=96(Neighbour's Primary Scrambling Code)

value=CPICH Ec/Io invalid

>>"RRC Connection Setup Description"

>>"Geographical and UTRAN Entity Identifiers"

value=hex2dec(5)=5 , hex2dec(2)=2 ,hex2dec(0)=0 --> MCC=520

value=hex2dec(0)=0 , hex2dec(1)=1 --> MNC=01

value=hex2dec(2908)= 10504
value=UE capable to support FDD , not TDD

value=UE capable to support GSM

value=Signaling Radio Bearer Information Setup ,RB-1

value=Radio Bearer Mapping

value=Signaling Radio Bearer Information Setup ,RB-2
value=Signaling Radio Bearer Information Setup ,RB-3
value=Signaling Radio Bearer Information Setup ,RB-4
value=BLER Target= -20 dB

value=MaxAllowedULTxPower=24 dBm

value=(-47*2)= -94 dBm (step of 2 dB) Default Constant

-22
-22
Note :DPCCH_Power_offset is configured by RNC

value= use Closed Loop Power Control Algorithm1

value= use long SC on Uplink

value=Spreading Factor 64 (Uplink)

value=Spreading Factor 128 (Downlink)

value=Primary Scrambling code=97

value=Spreading Factor 128 (Downlink)

Cell Identity=RNCid(12bits)+Cellid(16bits)
value=0000000010110111011110010010 => RNCid=bin2dec(000000001011)=11 and Cellid=bin2dec(0111011110010010)=3

>>"RRC Connection Setup Complete Description"

value= not support GSM (Locked UMTS Mode)

value= Chipering Algorithm A5/3

value= UE support Band fdd2100 MHz

value= UE (Powerclass3) maximum transmitted power =24 dBm

value= support Compressed Mode (CM) uplink and downlink

value= UE support Band fdd1800 MHz
 st)

est)
 quest)

ponse)
nse)
value= Call B-Party number = 0812713339
ng)

>>"Radio Bearer Description"

value= SF64(uplink)-> AMR 12.2
value=Primary Scrambling code=97

value= SF128(downlink)-> AMR 12.2

Cell Identity=RNCid(12bits)+Cellid(16bits)
value=0000000010110111011110010010 => RNCid=bin2dec(000000001011)=11 and Cellid=bin2dec
ge)
dge)
e)
elease)

Complete)
 DPCCH_Power_offset CPICH_RSCP PCPICH Power UL Interference
-94 -80 33 -105
-94 -70 33 -105
_Power_offset is configured by RNC and delivered to UE in RRC Connection Setup.
llid=bin2dec(0111011110010010)=30610
000001011)=11 and Cellid=bin2dec(0111011110010010)=30610
UL DPCCH Initial Power
-14
-24
 Click to return to main page
L3 Messages -AMR Voice
UE NodeB
*** The different messages between MOC & MTC are highlighted in "Red" color

2. RRC: Paging Type 1

1. RRC: RRC Connection Request (RACH)

Start Rx

4. ALCAP: Iub User Plane Setu

RRC Connection Establishment Timing Start Tx

5. RRC: RRC Connection Setup (FACH)

L1 Synchonization

6. RRC: RRC Connection Setup Completed (DCH)

1.RRC: Initial Direct Transfer (MM: Paging Response)

2.RRC: Downlink Direct Transfer (MM: Authentication Request)

3.RRC: Uplink Direct Transfer (MM: Authentication Response)

6.RRC: Security Mode Command

7.RRC: Security Mode Completed

 2. RRC: Downlink Direct Transfer (CC: Setup)

3. RRC: Uplink Direct Transfer (CC: Call Confirmed)

5. ALCAP: Iub User Plane Setu

6. RRC: Radio Bearer Setup

Apply new transport format se

8. RRC: Radio Bearer Setup Complete

6. RRC: Uplink Direct Transfer (CC: Alerting)

8.RRC: Uplink Direct Transfer (CC: Connect)

11. RRC: Downlink Direct Transfer (CC: Connect Acknowledge)

Call Est

RRC:Measurement Control

RRC:Measurement Report

RRC: Downlink Direct Transfer (CC: Disconnect)

 RRC: Uplink Direct Transfer (CC: Release)

RRC: Downlink Direct Transfer (CC: Release Complete)

RRC: Downlink Direct Transfer (CC: RRC Connection Release)

RRC: Uplink Direct Transfer (CC: RRC Connection Release Complete)

RRC: Uplink Direct Transfer (CC: RRC Connection Release Complete)

ALCAP: Iub User Plane Releas

Note the following information about the procedure ,

1.The RRC connection can be set up on a DCH or a CCH. This procedure takes the RRC connection set up on the DC
an example.
2. If IP transport is applied to the Iub interface, no ALCAP procedure is performed on the Iubinterface after radio links a
up, reconfigured, or deleted.
3. If IP transport is applied to the Iu-CS interface, no ALCAP procedure is performed on theIu-CS interface after an RAB
up or a call is released
 L3 Messages -AMR Voice Call (MTC) Call Procedure
S-RNC
ed in "Red" color

g Type 1

n Request (RACH)

2.NBAP:Radio Link Setup Req

3.NBAP:Radio Link Setup Resp.

4. ALCAP: Iub User Plane Setup

on Setup (FACH)

NBAP:Synchonization Indicator

etup Completed (DCH)

(MM: Paging Response)

MM: Authentication Request)

M: Authentication Response)

de Command

de Completed
Transfer (CC: Setup)

er (CC: Call Confirmed)

3. NBAP: Radio Link Reconfiguration

Prepare

4. NBAP: Radio Link Reconfiguration Ready

5. ALCAP: Iub User Plane Setup

earer Setup

7. NBAP: Radio Link Reconfiguration

Commit

Apply new transport format set

Setup Complete

nsfer (CC: Alerting)

nsfer (CC: Connect)

(CC: Connect Acknowledge)

Call Established

ent Control

ent Report

sfer (CC: Disconnect)

 sfer (CC: Release)

r (CC: Release Complete)

ALCAP: Iur User Plane Release

C: RRC Connection Release)

C Connection Release Complete)

C Connection Release Complete)

NBAP: Radio Link Deletion

Request

NBAP: Radio Link Deletion

Response

ALCAP: Iub User Plane Release

edure takes the RRC connection set up on the DCH as

s performed on the Iubinterface after radio links are set

re is performed on theIu-CS interface after an RAB is set

TC) Call Procedure
CN

1. RANAP: Paging Paging.1

2.RRC Connec

2.SCCP: CR (Connection Request)

3.Signalling C
2. RANAP: Initial UE Message (MM: Paging Response)

3.SCCP: CC (Connection Confirm)

1.RANAP: Direct Transfer (MM: Authentication Request)

4.RANAP: Direct Transfer (MM: Authentication Response)

RANAP: Common ID (IMSI)

5.RANAP: Security Mode Command

 7.RANAP: Security Mode Complete

1. RANAP: Direct Transfer (CC: Setup)

4. RANAP: Direct Transfer (CC: Call Confirmed)

1. RANAP: RAB Assignment Request

2. ALCAP: Iur User Plane Setup

Radio Bearer Se

9.RANAP: RAB Assignment Response

7. RANAP: Direct Transfer (CC: Alerting)

9. RANAP: Direct Transfer (CC: Connect)

10. RANAP: Direct Transfer (CC: Connect Acknowledge)

RANAP: Direct Transfer (CC: Disconnect)

 RANAP: Direct Transfer (CC: Release)

RANAP: Direct Transfer (CC: Release Complete)

RANAP: Iu Release Command

ALCAP: Iur User Plane Release

RANAP: Iu Release Complete


Paging.1
2.RRC ConnectionSetup
>>RRC Procedure Description
3.Signalling Connection Setup
Authentication & Security Mode.4
Control
Paging Procedure The paging procedure is performed
Triggering Conditions: A Terminal calls the UE
The Paging Procedure in Idle, Cell_PCH and URA-PCH
1.The CN sends a PAGING message to the SRNC.
2.The SRNC initiates the paging procedure by sending a P
paging occasion is related to the International Mobile Subs
proper receptionof the paging message by the UE.)
3.The UE in idle mode or in PCH state monitors the pagin
The Paging Procedure in Cell_DCH and Cell_FACH mo
1.The CN sends a PAGING message to the SRNC.
2.The SRNC initiates the paging procedure by sending a P
3.The UE receives the PAGNG TPYE 2 message, reads it
procedure ends
RRC connection setup procedure is performed for th
maximum of one RRC connection at a time.
Triggering Conditions: The UE in idle mode intitiates t
When the SRNC receives an RRC CONNECTION REQUE
reject theRRC connection request, based on a specific alg
Channel (DCH)or on a Common Channel (CCH), based o
The procedure shown is described as follows:
1.The UE sends an RRC CONNECTION REQUEST mess
2.Based on the cause in the RRC connection request and
NetworkTemporary Identity (RNTI), radio resources, and L
NodeB to allocate the specific radio link resources require
3.The NodeB responds with a RADIO LINK SETUP RESP
4.The SRNC uses the ALCAP protocol to set up the Iub us
It is required for the ATM-based Iub interface only.
5.The SRNC sends an RRC CONNECTION SETUP mess
SRNC.
6. UE and NodeB initiate L1 Synchronization. NodeB send
7. The UE sends an RRC CONNECTION SETUP COMPL
indicates that the RRC connection setup procedure ends.
If the RNC judges that the RRC connection request canno
UE, and indicates the reject reason in the message
The signaling connection setup procedure is perfo
Triggering Conditions: The UE sends a direct trans
The procedure shown is described as follows:
1.The UE sends an INITIAL DIRECT TRANSFER messag
UE.
2.The SRNC receives the INITIAL DIRECT TRANSFER m
 The signaling connection setup procedure is perfo

Triggering Conditions: The UE sends a direct trans

The procedure shown is described as follows:

1.The UE sends an INITIAL DIRECT TRANSFER messag
UE.
2.The SRNC receives the INITIAL DIRECT TRANSFER m
contains the NAS information to be sent to the CN by the
3.The CN sends a response message to the SRNC.
-If accepting the request, the CN sends a CONNECTION
message, the SRNC confirms that the signaling connectio
-lf rejecting the request, the CN sends a CONNECTION
message, the SRNC confirms that the signaling connectio

The authentication and security mode control pro

procedure ensures integrity and correctness of signaling.

Triggerring Conditions: The UE and the CN exchange s

Radio Bearer Setup.5 The procedure shown is described as follows:

1.The CN sends a DIRECT TRANSFER message to the S
4.Call Setup 2.The SRNC transparently sends the contents of the DIRE
3.The UE sends an UPLINK DIRECT TRANSFER messag
4.The SRNC transparently sends the contents of the UPL
RESPONSE. If the UMTS Subscriber Identity Module (US
5.The CN sends a SECURITY MODE COMMAND messag
ciphering and integrity protection algorithms.
6.The SRNC sends a SECURITY MODE COMMAND mes
7.The UE sends a response message to the SRNC.
-If the integrity protection and ciphering algorithms ar
then sends a SECURITY MODE COMMAND COMPLETE
UE uses.
-If the UE does not support the integrity protection and
contains the error information and the reason for the failur

The RANAP:Common ID message is used to transport

Call Setup Procedure(Incoming Call) is performed t

Triggering Conditions : A UE receiveds a call from

The procedure shown is described as follows:

1.The CN sends a DIRECT TRANSFER message to the S
2.The SRNC transparently sends the contents of the DIRE
3.The UE sends an UPLINK DIRECT TRANSFER messag
6.Conversation 4.The SRNC transparently sends the contents of the UPL
messageindicates CALL CONFIRM and contains the infor
5. A Radio Access Bearer (RAB) is set up. (see more deta
6. The UE sends an UPLINK DIRECT TRANSFER messa
7.The SRNC transparently sends the contents of the UPL
called terminal to ring.
8.The UE sends an UPLINK DIRECT TRANSFER messag
9.The SRNC transparently sends the contents of the UPL
meansthat the called party has answered the call.
10.The CN sends a DIRECT TRANSFER message to the
11.The SRNC transparently sends the contents of the DIR

The Radio Bearer Setup procedure shown is describe

 6. The UE sends an UPLINK DIRECT TRANSFER messa
7.The SRNC transparently sends the contents of the UPL
called terminal to ring.
8.The UE sends an UPLINK DIRECT TRANSFER messag
9.The SRNC transparently sends the contents of the UPL
meansthat the called party has answered the call.
10.The CN sends a DIRECT TRANSFER message to the
11.The SRNC transparently sends the contents of the DIR

The Radio Bearer Setup procedure shown is describe

7.Call Release 1.The CN sends an RAB ASSIGNMENT REQUEST mess
2.(Optional; applicable to the ATM-based Iu-CS interface o
radio resource characteristic parameters. Based on the AA
3.The SRNC sends a RADIO LINK RECONFIGURATION
links for carrying the RAB.
4.The NodeB allocates the associated resources and then
5.(Optional; required for the ATM-based Iub interface only
perform synchronization by exchanging uplink and downlin
6.The SRNC sends a RADIO BEARER SETUP message
7.The SRNC sends a RADIO LINK RECONFIGURATION
8.After performing the radio bearer setup, the UE sends a
9.The SRNC sends an RAB ASSIGNMENT RESPONSE m

The procedure when RAB Setup Failure shown is desc

1.The CN sends an RAB ASSIGNMENT REQUEST mess
2.The SRNC sends an RAB ASSIGNMENT RESPONSE m

8.RRC Connection Release

The Call Release procedure is performed to release

Triggering Conditions: A call ends and the calling p

The procedure shown is described as follows:

1.The CN sends a DIRECT TRANSFER message to the S
2.The SRNC transparently sends the contents of the DIRE
3.The UE sends an UPLINK DIRECT TRANSFER messag
4.The SRNC transparently sends the contents of the UPL
5.The CN sends a DIRECT TRANSFER message to the S
6.The SRNC transparently sends the contents of the DIRE
7.The CN sends an IU RELEASE COMMAND message to
8.(Optional; applicable to the ATM-based Iu-CS interface o
9.The SRNC sends an IU RELEASE COMPLETE messag

The RRC Connection Release procedure is performed t

Triggering Conditions: After a n RAB is released,the SR

other RAB of the UE,the SRNC initiates an RRC connectio

The procedure shown is described as follows: based o

from CCH (If an RRC connection needs to be released aft

1.The SRNC sends an RRC CONNECTION RELEASE m

(NOTE: The SRNC may send the RRC CONNECTION RE
these messages are the same. The number of retransmis
RELEASE COMPLETE message from the UE after sendin
connection.)

2.The UE sends an RRC CONNECTION RELEASE COM

The procedure shown is described as follows: based o
from CCH (If an RRC connection needs to be released aft

1.The SRNC sends an RRC CONNECTION RELEASE m

(NOTE: The SRNC may send the RRC CONNECTION RE
these messages are the same. The number of retransmis
RELEASE COMPLETE message from the UE after sendin
connection.)

2.The UE sends an RRC CONNECTION RELEASE COM

3.The SRNC sends a RADIO LINK DELETION REQUEST
4.After releasing the resources, the NodeB sends a RADIO
5.(Optional; required for the ATM-based Iub interface only
connection release procedure ends.
 The paging procedure is performed when the CN calls a UE.

ons: A Terminal calls the UE

ure in Idle, Cell_PCH and URA-PCH modes is described as follows;

AGING message to the SRNC.
the paging procedure by sending a PAGING TYPE 1 message to the UE through the Paging Control Channel (PCCH) on an appropriate o
lated to the International Mobile Subscriber Identity (IMSI) of the UE. The UTRAN may page the same UE on several occasions to increase
e paging message by the UE.)
e or in PCH state monitors the paging and receives the paging message from the network layer.The paging procedure ends.

ure in Cell_DCH and Cell_FACH mode is described as follows;

AGING message to the SRNC.
the paging procedure by sending a PAGING TYPE 2 message to the UE through the DCCH.
e PAGNG TPYE 2 message, reads it, and then reports to the NAS the information such as the paging cause and the paging record type ide

etup procedure is performed for the UE to set up a signaling connection to the SRNC. RRC connection setup is always initiated by the U
C connection at a time.

ons: The UE in idle mode intitiates the RRC connection setup procedure when the NAS of the UE requests the establishment of a signalin

eives an RRC CONNECTION REQUEST message from the UE, the Radio Resource Management (RRM) module of the RNC determines w
ction request, based on a specific algorithm. If accepting the request, the RRM module further determines whether to set up the RRC conne
a Common Channel (CCH), based on a specific RRM algorithm. Typically, an RRC connection is set up on the DCH.

wn is described as follows:
RRC CONNECTION REQUEST message to the SRNC through the uplink CCCH(RACH), requesting the establishment of an RRC connectio
e in the RRC connection request and the system resource status, the SRNC determines to set up the RRC connection on a DCH and alloca
dentity (RNTI), radio resources, and L1 and L2 resources. Then the SRNC sends a RADIO LINK SETUP REQUEST message to the NodeB
e specific radio link resources required for an RRC connection.
ds with a RADIO LINK SETUP RESPONSE message to the SRNC after successfully preparing the resources.
e ALCAP protocol to set up the Iub user plane transport bearer and performs the synchronization between the SRNC and the NodeB. This p
ATM-based Iub interface only.
an RRC CONNECTION SETUP message to the UE through the downlink CCCH (FACH). The message contains the information about the D

iate L1 Synchronization. NodeB sends NBAP:Synchonization Indicator message to SRNC when the uplink enter "In-Sync" state
RRC CONNECTION SETUP COMPLETE message to the SRNC through the uplink Dedicated Control Channel (DCCH) that is just set up.
C connection setup procedure ends.
at the RRC connection request cannot be set up (for instance, due to insufficient resources), it directly sends an RRC CONNECTION REJE
e reject reason in the message

nection setup procedure is performed to exchange the NAS (Non Access Stratum) information between the UE and the CN.

ons: The UE sends a direct transfer message to initiate the signaling connection setup procedure.

own is described as follows:

NITIAL DIRECT TRANSFER message to the SRNC through the RRC connection. The message contains the initial NAS information to be s

s the INITIAL DIRECT TRANSFER message from the UE and sendsan INITIAL UE MESSAGE to the CN through the Iu interface. The INIT
n and security mode control procedure is performed for the UE and the network to implement bi-directional authentication and to neg
tegrity and correctness of signaling.

ons: The UE and the CN exchange signaling. The network initiates the authentication and securitymode control procedure

wn is described as follows:
RECT TRANSFER message to the SRNC. The message indicates AUTHENTICATION REQUEST.
rently sends the contents of the DIRECT TRANSFER message to the UE through a DOWNLINK DIRECT TRANSFER message.
UPLINK DIRECT TRANSFER message to the SRNC.
rently sends the contents of the UPLINK DIRECT TRANSFER messageto the CN through a DIRECT TRANSFER message, indicating AUT
MTS Subscriber Identity Module (USIM) judges that the authentication is successful, the UE returns a message with an XRES IE.
ECURITY MODE COMMAND message to the SRNC to initiate the security mode control procedure. The message contains the information
y protection algorithms.
a SECURITY MODE COMMAND message to the UE to inform the UE of the integrity protection and ciphering algorithms that the UTRAN se
sponse message to the SRNC.
ection and ciphering algorithms are configured successfully, the UE sends a SECURITY MODE COMMAND COMPLETE message to
RITY MODE COMMAND COMPLETE message to the CN.The message contains the information about the integrity protection and cipherin

support the integrity protection and ciphering algorithms, the UE sends a SECURITY MODE COMMAND FAILURE message to the SR
ormation and the reason for the failure. The SRNC then sends a SECURITY MODE COMMAND REJECT message to the CN

on ID message is used to transport the permanent UE Identity(IMSI) to SRNC

ure(Incoming Call) is performed to setup a call.

ons : A UE receiveds a call from the CN

own is described as follows:

RECT TRANSFER message to the SRNC. The message indicates SETUP and contains the number of the calling party and the bearer cap
rently sends the contents of the DIRECT TRANSFER message to the UE through a DOWNLINK DIRECT TRANSFER message.
UPLINK DIRECT TRANSFER message to the SRNC.
rently sends the contents of the UPLINK DIRECT TRANSFER messageto the CN through a DIRECT TRANSFER message. The DIRECT T
ALL CONFIRM and contains the information about the negotiated bearer capability of the call.
earer (RAB) is set up. (see more details in RAB Setup Procedure below)
UPLINK DIRECT TRANSFER message to the SRNC.
rently sends the contents of the UPLINK DIRECT TRANSFER messageto the CN through a DIRECT TRANSFER message, indicating ALE
g.
UPLINK DIRECT TRANSFER message to the SRNC.
rently sends the contents of the UPLINK DIRECT TRANSFER messageto the CN through a DIRECT TRANSFER message, indicating CON
party has answered the call.
DIRECT TRANSFER message to the SRNC. The message indicatesCONNECT ACKNOWLEDGE.
arently sends the contents of the DIRECT TRANSFER message to the UE through a DOWNLINK DIRECT TRANSFER message.

etup procedure shown is described as follows:

procedure is performed to release services and resources after a call ends.

ons: A call ends and the calling party hangs up.

own is described as follows:

RECT TRANSFER message to the SRNC. The message indicates DISCONNECT to inform the UE that the calling party has hanged up.
rently sends the contents of the DIRECT TRANSFER message to the UE through a DOWNLINK DIRECT TRANSFER message.
UPLINK DIRECT TRANSFER message to the SRNC.
rently sends the contents of the UPLINK DIRECT TRANSFER messageto the CN through a DIRECT TRANSFER message. The DIRECT T
RECT TRANSFER message to the SRNC. The message indicatesRELEASE COMPLETE.
rently sends the contents of the DIRECT TRANSFER message to theUE through a DOWNLINK DIRECT TRANSFER message.
U RELEASE COMMAND message to the SRNC to request call releaseon the Iu interface. The message indicates the reason for the Iu rele
e to the ATM-based Iu-CS interface only) The ALCAP protocol on theIu interface initiates an Iu data transport bearer release procedure.
an IU RELEASE COMPLETE message to the CN.

n Release procedure is performed to release the signaling connection and all radio bearers between UE and the UTRAN

ns: After a n RAB is released,the SRNC judges whether the RRC connection carries any other RAB or the UE. If judging that the RRC conn
the SRNC initiates an RRC connection release procedure.

wn is described as follows: based on the resouce occupied by the RRC connection,there are two types of RRC connection release proced
C connection needs to be released after a successful outgoing call,, the RRC connection on the DCH is released and if a radio bearers fails

an RRC CONNECTION RELEASE message to the UE through the DCCH.

may send the RRC CONNECTION RELEASE message several times to increase the probability of proper reception of the message by the U
the same. The number of retransmissions and the transmission intervals are determined by the SRNC. If the SRNC does not receive an RR
TE message from the UE after sending the RRC CONNECTION RELEASE message for four times, the SRNC judges that the UE has relea

RRC CONNECTION RELEASE COMPLETE message to the SRNC.

CH) on an appropriate occasion. (NOTE The
al occasions to increase the probability of

ure ends.

e paging record type identifier.The paging

always initiated by the UE. One UE has a

ablishment of a signaling connection

f the RNC determines whether to accept or

o set up the RRC connection on a Dedicated
H.

ent of an RRC connection.

on on a DCH and allocates the Radio
message to the NodeB, requesting the

C and the NodeB. This procedure is optional.

information about the DCH allocated by the

-Sync" state
CCH) that is just set up. The message

C CONNECTION REJECT message to the

and the CN.

NAS information to be sent to the CN by the

e Iu interface. The INITIAL UEMESSAGE

 uthentication and to negotiate and configure the integrity protection algorithm and ciphering algorithm. This

cedure

ER message.

message, indicating AUTHENTICATION

h an XRES IE.
ontains the information about the supported

hms that the UTRAN selects.

OMPLETE message to the SRNC. The SRNC

protection and ciphering algorithms that the

URE message to the SRNC. The message

to the CN

arty and the bearer capability of the call.

ER message.

message. The DIRECT TRANSFER

message, indicating ALERTING to request the

message, indicating CONNECT. This

FER message.
party has hanged up.
ER message.

message. The DIRECT TRANSFER messageindicates RELEASE which requests release of the call.

ER message.
he reason for the Iu release.
r release procedure.

UTRAN

dging that the RRC connection does not carry

nnection release procedure: release of an RRC connection from DCH and release of an RRC connection
d if a radio bearers fails to be setup ,the RRC connection on the CCH is released)

of the message by the UE. The RRC SNs of

does not receive an RRC CONNECTION
es that the UE has released the RRC
Click to return to main page
RRC: Paging Type 1

RRC: RRC Connection Request (RACH)

RRC: RRC Connection Setup (FACH)
RRC:RRC Connection Setup Complete (DCCH)
RANAP: Initial UE Message (MM: Paging Response)
RRC: Initial Direct Transfer (MM: Paging Response)

RRC: Security Mode Command

RRC: Security Mode Complete
RRC: Downlink Direct Transfer (CC: Setup)

RANAP: Direct Transfer (CC: Setup)

RANAP: Direct Transfer (CC: Call Confirmed)
RRC: Uplink Direct Transfer (CC: Call Confirmed)

RRC: Radio Bearer Setup

 RRC: Radio Bearer Setup Complete

RANAP: Direct Transfer (CC: Alerting)

RRC: Uplink Direct Transfer (CC: Alerting)

 RANAP: Direct Transfer (CC: Connect)

RRC: Uplink Direct Transfer (CC: Connect)

RANAP: Direct Transfer (CC: Connect Acknowledge)

RRC:Downlink Direct Transfer (CC: Connect Acknowledge)

RANAP: Direct Transfer (MM: Authentication Request)

RRC: Downlink Direct Transfer (MM: Authentication Request)

RRC: Uplink Direct Transfer (MM: Authentication Response)

RANAP: Direct Transfer (MM: Authentication Response)

RANAP: Direct Transfer (CC: Disconnect)

RRC: Downlink Direct Transfer (CC: Disconnect)

RRC: Uplink Direct Transfer (CC: Release)

RANAP: Direct Transfer (CC: Release)

 RANAP: Direct Transfer (CC: Release Complete)

RRC: Uplink Direct Transfer (CC: Release Complete)

RRC: Downlink Direct Transfer (CC: RRC Connection Release)

RRC: Uplink Direct Transfer (CC: RRC Connection Release)
>>"RRC Connection Request Description"

>>"Geographical and UTRAN Entity Identifiers"

value=hex2dec(5)=5 , hex2dec(2)=2 ,hex2dec(0)=0 --> MCC=520

value=hex2dec(0)=0 , hex2dec(1)=1 --> MNC=01

value=hex2dec(2908)= 10504
value= terminatingConversationalcall (CS MTC)

value=(-24+ (44/2))=-2.0 dB

value=hex2dec(6d)=109(Neighbour's Primary Scrambling Code)

value=CPICH Ec/Io invalid

>>"RRC Connection Setup Description"

>>"Geographical and UTRAN Entity Identifiers"

value=hex2dec(5)=5 , hex2dec(2)=2 ,hex2dec(0)=0 --> MCC=520

value=hex2dec(0)=0 , hex2dec(1)=1 --> MNC=01

value=hex2dec(2908)= 10504

value=UE capable to support FDD , not TDD

value=UE capable to support GSM

value=Signaling Radio Bearer Information Setup ,RB-1

value=Radio Bearer Mapping
value=Signaling Radio Bearer Information Setup ,RB-2
value=Signaling Radio Bearer Information Setup ,RB-3
value=Signaling Radio Bearer Information Setup ,RB-4
value=BLER Target= -20 dB

value=MaxAllowedULTxPower=24 dBm

value=(-48*2)= -96 dBm (step of 2 dB) Default Constant

-22

-22

value= use Closed Loop Power Control Algorithm1

value= use long SC on Uplink

value=Spreading Factor 64 (Uplink)

value=Spreading Factor 128 (Downlink)

value=Primary Scrambling code=97

value=Spreading Factor 128 (Downlink)

Cell Identity=RNCid(12bits)+Cellid(16bits)

value=0000000010110111011110010010 => RNCid=bin2dec(000000001011)=11 and Cellid=bin2dec(01110111100100

>>"RRC Connection Setup Complete Description"

value= not support GSM (Locked UMTS Mode)

value= Chipering Algorithm A5/3

value= UE support Band fdd2100 MHz
value= UE (Powerclass3) maximum transmitted power =24 dBm

value= support Compressed Mode (CM) uplink and downlink

value= Call B-Party number = 0813713339
>>"Radio Bearer Description"
value= SF64(uplink)-> AMR 12.2
value=Primary Scrambling code=97

value= SF128(downlink)-> AMR 12.2

Cell Identity=RNCid(12bits)+Cellid(16bits)
value=0000000010110111011110010010 => RNCid=bin2dec(000000001011)=11 and Cellid=bin2dec(01110111100100
)

est)
se)

)
ase)
se)
 DPCCH_Power_offset CPICH_RSCP PCPICH Power UL Interference

-96 -80 33 -107

-96 -70 33 -107

Note :DPCCH_Power_offset is configured by RNC and delivered to UE in RRC Connection Setup.

nd Cellid=bin2dec(0111011110010010)=30610
nd Cellid=bin2dec(0111011110010010)=30610
UL DPCCH Initial Power

-16

-26
Click to return to main page

L3 Messages - Video Cal

UE NodeB

1.RRC: RRC Connection Request (RACH)

Start Rx

4.ALCAP: Iub User Plane Setup

RRC Connection Establishment Timing Start Tx

5.RRC: RRC Connection Setup (FACH)

L1 Synchonization

6.RRC: RRC Connection Setup Completed (DCH)

1.RRC: Initial Direct Transfer (MM: CM Service Request)

2.RRC: Downlink Direct Transfer (MM: Authentication Request)

3.RRC: Uplink Direct Transfer (MM: Authentication Response)

6.RRC: Security Mode Command

7.RRC: Security Mode Completed

 1.RRC: Uplink Direct Transfer (CC: Setup)

4.RRC: Downlink Direct Transfer (CC: Call Proceeding)

5.ALCAP: Iub User Plane Setup

6.RRC: Radio Bearer Setup

Apply new transport format set

8.RRC: Radio Bearer Setup Complete

7.RRC: Downlink Direct Transfer (CC: Alerting)

9.RRC: Downlink Direct Transfer (CC: Connect)

10.RRC: Uplink Direct Transfer (CC: Connect Acknowledge)

Call Esta

RRC:Measurement Control

RRC:Measurement Report
 1.RRC: Uplink Direct Transfer (CC: Disconnect)

4.RRC: Downlink Direct Transfer (CC: Release)

5.RRC: Uplink Direct Transfer (CC: Release Complete)

1.RRC: RRC Connection Release

2.RRC: RRC Connection Release Complete

2.RRC:RRC Connection Release Complete

5,.ALCAP: Iub User Plane Releas

Note the following information about the procedure ,

1.The RRC connection can be set up on a DCH or a CCH. This procedure takes the RRC connection set up on the DCH
an example.
2. If IP transport is applied to the Iub interface, no ALCAP procedure is
 L3 Messages - Video Call (CS64) Call Procedure
S-RNC

n Request (RACH)

2.NBAP:Radio Link Setup Req

3.NBAP:Radio Link Setup Resp.

4.ALCAP: Iub User Plane Setup

on Setup (FACH)

NBAP:Synchonization Indicator

etup Completed (DCH)

MM: CM Service Request)

MM: Authentication Request)

M: Authentication Response)

de Command

de Completed
ansfer (CC: Setup)

fer (CC: Call Proceeding)

3.NBAP: Radio Link Reconfiguration Prepare

4.NBAP: Radio Link Reconfiguration Ready

5.ALCAP: Iub User Plane Setup

earer Setup

7.NBAP: Radio Link Reconfiguration

Commit

Apply new transport format set

Setup Complete

ansfer (CC: Alerting)

ansfer (CC: Connect)

CC: Connect Acknowledge)

Call Established

ent Control

ent Report
sfer (CC: Disconnect)

ansfer (CC: Release)

(CC: Release Complete)

8.ALCAP: Iu User Plane Release

ction Release

Release Complete

Release Complete

3.NBAP: Radio Link Deletion

Request

4.NBAP: Radio Link Deletion

Response

5,.ALCAP: Iub User Plane Release

edure takes the RRC connection set up on the DCH as

s
4) Call Procedure
CN

SCCP: CR (Connection Request)

2.RANAP: Initial UE Message (MM: CM Service Request)

3.SCCP: CC (Connection Confirm)

1.RANAP: Direct Transfer (MM: Authentication Request)

4.RANAP: Direct Transfer (MM: Authentication Response)

RANAP: Common ID (IMSI)

5.RANAP: Security Mode Command

8.RANAP: Security Mode Complete

 2.RANAP: Direct Transfer (CC: Setup)

3.RANAP: Direct Transfer (CC: Call Proceeding)

1.RANAP: RAB Assignment Request

2.ALCAP : Iu User Plane Setup

Radio Bearer Setup

9.RANAP: RAB Assignment Response

6.RANAP: Direct Transfer (CC: Alerting)

8.RANAP: Direct Transfer (CC: Connect)

11.RANAP: Direct Transfer (CC: Connect Acknowledge)

6.Conversation
 2.RANAP: Direct Transfer (CC: Disconnect)

3.RANAP: Direct Transfer (CC: Release)

6.RANAP: Direct Transfer (CC: Release Complete)

7.RANAP: Iu Release Command

8.ALCAP: Iu User Plane Release

9.RANAP: Iu Release Complete


>>RRC Procedure Description
1.RRC Connection Setup
2.Signalling Connection Setup
&Authentication.3
Security Mode Control
RRC connection setup procedure is performed for the UE to set u
maximum of one RRC connection at a time.
Triggering Conditions : The UE in idle mode intitiates the RRC conn
receives an RRC CONNECTION REQUEST message from the UE, the
request, based on a specific algorithm. If accepting the request, the RR
Dedicated Channel (DCH)or on a Common Channel (CCH),based on a
The procedure shown is described as follows:
1.The UE sends an RRC CONNECTION REQUEST message to the SR
2.Based on the cause in the RRC connection request and the system re
resources, and L1 and L2 resources. Then the SRNC sends a RADIO L
3.The NodeB responds with a RADIO LINK SETUP RESPONSE messa
4.The SRNC uses the ALCAP protocol to set up the Iub user plane tran
for the ATM-based Iub interface only.
5.The SRNC sends an RRC CONNECTION SETUP message to the UE
6. UE and NodeB initiate L1 Synchronization. NodeB sends NBAP:Sync
7. The UE sends an RRC CONNECTION SETUP COMPLETE messag
indicates that the RRC connection setup procedure ends.
If the RNC judges that the RRC connection request cannot be set up (fo
theUE, and indicates the reject reason in the message
The signaling connection setup procedure is performed to exch
Triggering Conditons: The UE sends a direct transfer message to initi
The procedure shown is described as follows:
1.The UE sends an INITIAL DIRECT TRANSFER message to the SRNC
2.The SRNC receives the INITIAL DIRECT TRANSFER message from
CN by the UE. The content of the NAS information is CM SERVICE RE
3.The CN sends a response message to the SRNC.
-If accepting the request, the CN sends a CONNECTION CONFIRM (
SRNC confirms that the signaling connection is set up.
-If rejecting the request, the CN sends a CONNECTION REJECT (CJ
the SRNC confirms that the signaling connection fails to be setup and t
The authentication and security mode control procedure is pe
the integrity protection algorithm and ciphering algorithm. This procedu
Triggerring Conditions: The UE and the CN exchange signaling. The
The procedure shown is described as follows:
1.The CN sends a DIRECT TRANSFER message to the SRNC. The me
2.The SRNC transparently sends the contents of the DIRECT TRANSF
3.The UE sends an UPLINK DIRECT TRANSFER message to the SRN
4.The SRNC transparently sends the contents of the UPLINK DIRECT T
Module (USIM) judges that the authentication is successful, the UE retu
5.The CN sends a SECURITY MODE COMMAND message to the SRN
algorithms.
6.The SRNC sends a SECURITY MODE COMMAND message to the U
 Triggerring Conditions: The UE and the CN exchange signaling. The

The procedure shown is described as follows:

1.The CN sends a DIRECT TRANSFER message to the SRNC. The me
2.The SRNC transparently sends the contents of the DIRECT TRANSF
3.The UE sends an UPLINK DIRECT TRANSFER message to the SRN
4.The SRNC transparently sends the contents of the UPLINK DIRECT T
Module (USIM) judges that the authentication is successful, the UE retu
5.The CN sends a SECURITY MODE COMMAND message to the SRN
algorithms.
6.The SRNC sends a SECURITY MODE COMMAND message to the U
7.The UE sends a response message to the SRNC.
-If the integrity protection and ciphering algorithms are configured
then sends a SECURITY MODE COMMAND COMPLETE message to
-If the UE does not support the integrity protection and ciphering a
contains the error information and the reason for the failure. The SRNC
The RANAP:Common ID message is used to transport the permane

The call setup procedure is performed to set up a call.

Radio Bearer Setup. 5 Triggering Conditions: The UE initiates a call

The procedure shown is described as follows:

4.Call Setup 1.The UE sends an UPLINK DIRECT TRANSFER message to the SRN
2.The SRNC transparently sends the contents of the UPLINK DIRECT T
3.The CN sends a DIRECT TRANSFER message to the SRNC. The me
4.The SRNC transparently sends the contents of the DIRECT TRANSF
5. A Radio Access Bearer (RAB) is set up. (see more details in RAB Se
6. When the called terminal rings, the CN sends a DIRECT TRANSFER
7.The SRNC transparently sends the contents of the DIRECT TRANSF
8.The CN sends a DIRECT TRANSFER message to the SRNC. The me
9.The SRNC transparently sends the contents of the DIRECT TRANSF
10.The UE sends an UPLINK DIRECT TRANSFER message to the SR
11.The SRNC transparently sends the contents of the UPLINK DIRECT

The Radio Bearer Setup procedure shown is described as follows:

1.The CN sends an RAB ASSIGNMENT REQUEST message to the SR
2.(Optional; applicable to the ATM-based Iu-CS interface only) The SRN
parameters. Based on the AAL2 link characteristic parameters,the ALCA
3.The SRNC sends a RADIO LINK RECONFIGURATION PREPARE m
4.The NodeB allocates the associated resources and then sends a RAD
5.(Optional; required for the ATM-based Iub interface only) The Iub ALC
uplink and downlink synchronization frames in the DCH frame protocol.
6.The SRNC sends a RADIO BEARER SETUP message to the UE.
7.The SRNC sends a RADIO LINK RECONFIGURATION COMMIT mes
8.After performing the radio bearer setup, the UE sends a RADIO BEAR
9.The SRNC sends an RAB ASSIGNMENT RESPONSE message to th
The procedure when RAB Setup Failure shown is described as foll
1.The CN sends an RAB ASSIGNMENT REQUEST message to the SR
2.The SRNC sends an RAB ASSIGNMENT RESPONSE message to th

6.Conversation

The call release procedure is performed to release services and re

Triggering Conditions : A call ends and the calling party hangs up

The procedure shown is described as follows:

1.The UE sends an UPLINK DIRECT TRANSFER message to the SRN
2.The SRNC transparently sends the contents of the UPLINK DIRECT T
up.
3.The CN sends a DIRECT TRANSFER message to the SRNC. The me
 The call release procedure is performed to release services and re

Triggering Conditions : A call ends and the calling party hangs up

The procedure shown is described as follows:

1.The UE sends an UPLINK DIRECT TRANSFER message to the SRN
2.The SRNC transparently sends the contents of the UPLINK DIRECT T
up.
3.The CN sends a DIRECT TRANSFER message to the SRNC. The me
4.The SRNC transparently sends the contents of the DIRECT TRANSF
5.The UE sends an UPLINK DIRECT TRANSFER message to the SRN
6.The SRNC transparently sends the contents of the UPLINK DIRECT T
7.The CN sends an IU RELEASE COMMAND message to the SRNC to
8.(Optional; applicable to the ATM-based Iu-CS interface only) The ALC
9.The SRNC sends an IU RELEASE COMPLETE message to the CN.
7.Call Release

The RRC Connection Release procedure is performed to release the

Triggering Conditions: After a n RAB is released,the SRNC judges wh

UE,the SRNC initiates an RRC connection release procedure.

The procedure shown is described as follows: based on the resouce

needs to be released after a successful outgoing call,, the RRC connec
bearers fails to be setup ,the RRC connection on the CCH is released)

1.The SRNC sends an RRC CONNECTION RELEASE message to the

(NOTE: The SRNC may send the RRC CONNECTION RELEASE mess
are determined by the SRNC. If the SRNC does not receive an RRC CO
COMPLETE message from the UE after sending the RRC CONNECTIO
8.RRC Connection Release
2.The UE sends an RRC CONNECTION RELEASE COMPLETE messa
3.The SRNC sends a RADIO LINK DELETION REQUEST message to
4.After releasing the resources, the NodeB sends a RADIO LINK DELE
5.(Optional; required for the ATM-based Iub interface only) The SRNC u
erformed for the UE to set up a signaling connection to the SRNC. RRC connection setup is always initiated by the UE. One UE has a

mode intitiates the RRC connection setup procedure when the NAS of the UE requests the establishment of a signaling connection When th
message from the UE, the Radio Resource Management (RRM) module of the RNC determines whether to accept or reject theRRC conne
cepting the request, the RRM module further determines whether to set up the RRC connection on a
Channel (CCH),based on a specific RRM algorithm. Typically, an RRC connection is set up on the DCH.

ows:
QUEST message to the SRNC through the uplink CCCH(RACH), requesting the establishment of an RRC connection.
n request and the system resource status, the SRNC determines to set up the RRC connection on a DCH and allocates the Radio NetworkT
he SRNC sends a RADIO LINK SETUP REQUEST message to the NodeB, requesting the NodeB to allocate the specific radio link resource
SETUP RESPONSE message to the SRNC after successfully preparing the resources.
t up the Iub user plane transport bearer and performs the synchronization between the SRNC and the NodeB. This procedure is optional. It

SETUP message to the UE through the downlink CCCH (FACH). The message contains the information about the DCH allocated by the SR
n. NodeB sends NBAP:Synchonization Indicator message to SRNC when the uplink enter "In-Sync" state
ETUP COMPLETE message to the SRNC through the uplink Dedicated Control Channel (DCCH) that is just set up. The message
cedure ends.
equest cannot be set up (for instance, due to insufficient resources), it directly sends an RRC CONNECTION REJECT message to
e message

edure is performed to exchange the NAS (Non Access Stratum) information between the UE and the CN.

ect transfer message to initiate the signaling connection setup procedure.

ows:
SFER message to the SRNC through the RRC connection. The message contains the initial NAS information to be sent to the CN by the UE
TRANSFER message from the UE and sends an INITIAL UE MESSAGE to the CN over the Iu interface. The INITIAL UE MESSAGE contain
mation is CM SERVICE REQUEST.
SRNC.
CONNECTION CONFIRM (CC) message to the SRNC. The message indicates that the SCCP connection is set up. After receivingthe mess
n is set up.
ONNECTION REJECT (CJ) message to the SRNC. The message indicates that the SCCP connection fails to be set up. After receiving the
ction fails to be setup and then initiates the RRC release procedure.

e control procedure is performed for the UE and the network to implement bi-directional authentication and to negotiate and configure
ng algorithm. This procedure ensures integrity and correctness of signaling

N exchange signaling. The network initiates the authentication and securitymode control procedure

ows:
ssage to the SRNC. The message indicates AUTHENTICATION REQUEST.
ts of the DIRECT TRANSFER message to the UE through a DOWNLINK DIRECT TRANSFER message.
SFER message to the SRNC.
ts of the UPLINK DIRECT TRANSFER messageto the CN through a DIRECT TRANSFER message, indicating AUTHENTICATION RESPO
n is successful, the UE returns a message with an XRES IE.
MAND message to the SRNC to initiate the security mode control procedure. The message contains the information about the supported cip

OMMAND message to the UE to inform the UE of the integrity protection and ciphering algorithms that the UTRAN selects.
o set up a call.

all

ows:
SFER message to the SRNC. The message contains the number of the called party and the information about the bearer capability of the c
ts of the UPLINK DIRECT TRANSFER messageto the CN through a DIRECT TRANSFER message.
ssage to the SRNC. The message indicates CALL PROCEEDING and contains the information about the negotiated bearer capability of the
ts of the DIRECT TRANSFER message to the UE through a DOWNLINK DIRECT TRANSFER message.
ee more details in RAB Setup Procedure below)
nds a DIRECT TRANSFER message to the SRNC. The message indicates ALERTING.
ts of the DIRECT TRANSFER message to the UE through a DOWNLINK DIRECT TRANSFER message.
ssage to the SRNC. The message indicates CONNECT, which means that the called party has answered the call.
ts of the DIRECT TRANSFER message to the UE through a DOWNLINK DIRECT TRANSFER message.
NSFER message to the SRNC.
nts of the UPLINK DIRECT TRANSFER message to the CN through a DIRECT TRANSFER message, indicating CONNECT ACKNOWLED

n is described as follows:
QUEST message to the SRNC to initiate the RAB setup procedure.
CS interface only) The SRNC maps the Quality of Service (QoS) parameters for the RAB to the AAL2 link characteristic parameters and rad
eristic parameters,the ALCAP on the Iu interface initiates an Iu user plane transport bearer setup procedure.
FIGURATION PREPARE message to the NodeB, requesting the NodeB to prepare for adding one or more DCHs to the existing radio links f
rces and then sends a RADIO LINKRECONFIGURATION READY message to the SRNC.
interface only) The Iub ALCAP at the SRNC initiates an Iub user plane transport bearer setup procedure. The NodeB and the SRNC perform
in the DCH frame protocol.
UP message to the UE.
FIGURATION COMMIT message to theNodeB.
e UE sends a RADIO BEARER SETUP COMPLETE message to the SRNC.
RESPONSE message to the CN. The RAB isset up.
hown is described as follows:
QUEST message to the SRNC to initiate the RAB setup procedure.
RESPONSE message to the CN. The message indicates the ID of the RAB that fails to be set up and the reason for the failure.

to release services and resources after a call ends.

e calling party hangs up

ows:
SFER message to the SRNC.
ts of the UPLINK DIRECT TRANSFER messageto the CN through a DIRECT TRANSFER message, indicating DISCONNECT. This conten

ssage to the SRNC. The message indicates RELEASE to request release of the call.
is performed to release the signaling connection and all radio bearers between UE and the UTRAN

eased,the SRNC judges whether the RRC connection carries any other RAB or the UE. If judging that the RRC connection does not carry o
elease procedure.

ows: based on the resouce occupied by the RRC connection,there are two types of RRC connection release procedure: release of an RRC
oing call,, the RRC connection on the DCH is released and if a radio
on on the CCH is released)

RELEASE message to the UE through the DCCH.

NNECTION RELEASE message several times to increase the probability of proper reception of the message by the UE. The RRC SNs of th
oes not receive an RRC CONNECTION RELEASE
ding the RRC CONNECTION RELEASE message for four times, the SRNC judges that the UE has released the RRC connection.)

LEASE COMPLETE message to the SRNC.

ON REQUEST message to the NodeB,requesting the NodeB to delete the radio link resources in the NodeB.
ends a RADIO LINK DELETION RESPONSE message to the SRNC.
interface only) The SRNC uses the ALCAP protocol to initiate an Iub user plane transport bearer release procedure. Then, the RRC connec
he UE. One UE has a

naling connection When the SRNC

ept or reject theRRC connection

ection.
ocates the Radio NetworkTemporary Identity(RNTI),radio
specific radio link resources required for an RRC connection.

his procedure is optional. It is required

he DCH allocated by the SRNC.

up. The message

JECT message to

e sent to the CN by the UE.

TIAL UE MESSAGE contains the NAS information to be sent to the

up. After receivingthe message, the

set up. After receiving the message,

negotiate and configure

AUTHENTICATION RESPONSE. If the UMTS Subscriber Identity

on about the supported ciphering and integrity protection

N selects.
e bearer capability of the call.

ted bearer capability of the call.

CONNECT ACKNOWLEDGE.

teristic parameters and radio resource characteristic

to the existing radio links for carrying the RAB.

deB and the SRNC perform synchronization by exchanging

for the failure.

DISCONNECT. This content informs the CN that the UE has hanged

onnection does not carry other RAB of the

ocedure: release of an RRC connection from DCH and release of an RRC connection from CCH (If an RRC connection

he UE. The RRC SNs of these messages are the same. The number of retransmissions and the transmission intervals

RRC connection.)

re. Then, the RRC connection release procedure ends.

Click to return to main page
RRC:RRC Connection Request (RACH)
RRC:RRC Connection Setup (FACH)
RRC:RRC Connection Setup Complete (DCCH)
RRC: Initial Direct Transfer (MM: CM Service Request)
 RANAP:Initial UE Message (MM: CM Service Request)

RANAP: Direct Transfer (MM: Authentication Request)

RRC: Downlink Direct Transfer (MM: Authentication Request)

RRC: Uplink Direct Transfer (MM: Authentication Response)

RANAP: Direct Transfer (MM: Authentication Response)

RRC: Security Mode Command

RRC: Security Mode Complete
RANAP: Direct Transfer (CC: Setup)
RRC: Uplink Direct Transfer (CC: Setup)
RRC: Downlink Direct Transfer (CC: Call Proceeding)

RANAP: Direct Transfer (CC: Call Proceeding)

RRC: Radio Bearer Setup

RRC: Radio Bearer Setup Complete
 RANAP: Direct Transfer (CC: Alerting)

RRC: Downlink Direct Transfer (CC: Alerting)

RANAP: Direct Transfer (CC: Connect)

 RRC: Downlink Direct Transfer (CC: Connect)

RANAP: Direct Transfer (CC: Connect Acknowledge)

RRC: Uplink Direct Transfer (CC: Connect Acknowledge)

 RANAP: Direct Transfer (CC: Disconnect)

RRC: Uplink Direct Transfer (CC: Disconnect)

 RANAP: Direct Transfer (CC: Release)

RRC: Downlink Direct Transfer (CC: Release)

 RANAP: Direct Transfer (CC: Release Complete)

RRC: Uplink Direct Transfer (CC: Release Complete)

RRC: Downlink Direct Transfer (CC: RRC Connection Release)

RRC: Uplink Direct Transfer (CC: RRC Connection Release Complete)
>>"RRC Connection Request Description"

>>"Geographical and UTRAN Entity Identifiers"

value=hex2dec(5)=5 , hex2dec(2)=2 ,hex2dec(0)=0 --> MCC=520

value=hex2dec(0)=0 , hex2dec(1)=1 --> MNC=01

value=hex2dec(2908)= 10504

value= OriginatingConversationalcall (CS MOC)

value=(-24+ (44/2))=-2.0 dB
>>"RRC Connection Setup Description"

>>"Geographical and UTRAN Entity Identifiers"

value=hex2dec(5)=5 , hex2dec(2)=2 ,hex2dec(0)=0 --> MCC=520

value=hex2dec(0)=0 , hex2dec(1)=1 --> MNC=01

value=hex2dec(2908)= 10504

value=UE capable to support FDD , not TDD

value=UE capable to support GSM

value=Signaling Radio Bearer Information Setup ,RB-1

value=Radio Bearer Mapping

value=Signaling Radio Bearer Information Setup ,RB-2
value=Signaling Radio Bearer Information Setup ,RB-3
value=Signaling Radio Bearer Information Setup ,RB-4
value=BLER Target= -20 dB

value=MaxAllowedULTxPower=24 dBm

value=(-48*2)= -96 dBm (step of 2 dB) Default Constant

-22
-22
Note :DPCCH_Power_offset is configured by RNC
value= use Closed Loop Power Control Algorithm1

value= use long SC on Uplink

value=Spreading Factor 64 (Uplink)

value=Spreading Factor 128 (Downlink)

value=Primary Scrambling code=97

value=Spreading Factor 128 (Downlink)

Cell Identity=RNCid(12bits)+Cellid(16bits)
value=0000000010110111011110010010 => RNCid=bin2dec(000000001011)=11 and Cellid=bin2dec(0111011110010010)=3

>>"RRC Connection Setup Complete Description"

value= not support GSM (Locked UMTS Mode)
value= Chipering Algorithm A5/3

value= UE support Band fdd2100 MHz

value= UE (Powerclass3) maximum transmitted power =24 dBm

value= support Compressed Mode (CM) uplink and downlink

value= UE support Band fdd1800 MHz

 st)

est)

quest)
ponse)

nse)
value= Call B-Party number = 0812713339
ng)

>>"Radio Bearer Description"

value= SF16(uplink)-> CS64 (VP)
value=Primary Scrambling code=97

value= SF32(downlink)-> CS64 (VP)

Cell Identity=RNCid(12bits)+Cellid(16bits)
value=0000000010110111011110010010 => RNCid=bin2dec(000000001011)=11 and Cellid=bin2dec
ge)

dge)
e)

elease)
Complete)
 DPCCH_Power_offset CPICH_RSCP PCPICH Power UL Interference
-96 -80 33 -107
-96 -70 33 -107
_Power_offset is configured by RNC and delivered to UE in RRC Connection Setup.
llid=bin2dec(0111011110010010)=30610
000001011)=11 and Cellid=bin2dec(0111011110010010)=30610
UL DPCCH Initial Power
-16
-26
 Click to return to main page

L3
UE NodeB

1.RRC: RRC Connection Request (RACH)

Start Rx

4.ALCA

RRC Connection Establishment Timing Start Tx

5.RRC: RRC Connection Setup (FACH)

L1 Synchonization

8.RRC: RRC Connection Setup Completed (DCH)

If UE already RRC: Initial Direct Transfer (GMM: Attach Request)

attached to
GPRS CN, the
UE will only
send
"GMM:Service
Request" RRC: Downlink Direct Transfer (GMM: GPRS Identity Reque
message to
N/W
RRC: Uplink Direct Transfer (GMM: GPRS Identity Respons

RRC: Downlink Direct Transfer (MM: Authentication & Ciphering

RRC: Uplink Direct Transfer (MM: Authentication & Ciphering R

RRC: Security Mode Command

RRC: Security Mode Completed

 RRC: Downlink Direct Transfer (MM: Attach Accept)

RRC: Uplink Direct Transfer (MM: Attach Completed)

RRC: Uplink Direct Transfer (SM: Activate PDP Context Req

ALCA

RRC: Radio Bearer Setup

Apply

RRC: Radio Bearer Setup Complete

RRC:Measurement Control

RRC: Downlink Direct Transfer (SM: Activate PDP Context A

RRC:Measurement Report

ALCA
 RRC: Radio Bearer Reconfiguration

RRC: Radio Bearer Reconfiguration Complete

RRC: Uplink Direct Transfer (SM: Deactivate PDP Context Re

RRC: Downlink Direct Transfer (SM: Deactivate PDP Context

ALCA

RRC: Uplink Direct Transfer (MM: Detach Request)

RRC: Radio Bearer Release

RRC: Downlink Direct Transfer (MM: Detach Accept)

RRC: Radio Bearer Release Completed

RRC: Downlink Direct Transfer (CC: RRC Connection Rele

RRC: Uplink Direct Transfer (CC: RRC Connection Release Co

RRC: Uplink Direct Transfer (CC: RRC Connection Release Com

ALCAP
 L3 Messages - PS(R99) Call Procedure
S-RNC

n Request (RACH)

2.NBAP:Radio Link Setup Req

3.NBAP:Radio Link Setup Resp.

4.ALCAP: Iub User Plane Setup

on Setup (FACH)

7.NBAP:Synchonization Indicator

etup Completed (DCH)

GMM: Attach Request)

MM: GPRS Identity Request)

M: GPRS Identity Response)

thentication & Ciphering Request)

entication & Ciphering Response)

de Command

de Completed
 er (MM: Attach Accept)

MM: Attach Completed)

ctivate PDP Context Request)

NBAP: Radio Link Reconfiguration Prepare

NBAP: Radio Link Reconfiguration Ready

ALCAP: Iub User Plane Setup

arer Setup

NBAP: Radio Link Reconfiguration Commit

Apply new transport format set

Setup Complete

ent Control

Activate PDP Context Accept)

PS Session Established

ent Report

NBAP: Radio Link Reconfiguration Prepare

NBAP: Radio Link Reconfiguration Ready

ALCAP: Iub User Plane Setup

 NBAP: Radio Link Reconfiguration Commit

Reconfiguration

figuration Complete

activate PDP Context Request)

Deactivate PDP Context Accept)

NBAP: Radio Link Reconfiguration Prepare

NBAP: Radio Link Reconfiguration Ready

ALCAP: Iub User Plane Setup

NBAP: Radio Link Reconfiguration Commit

(MM: Detach Request)

rer Release

er (MM: Detach Accept)

ALCAP: Iu User Plane Release

lease Completed

C: RRC Connection Release)

C Connection Release Complete)

Connection Release Complete)

NBAP: Radio Link Deletion

Request
 NBAP: Radio Link Deletion
Response

ALCAP: Iub User Plane Release

all Procedure
CN

1.RRC Connecti

RANAP: Initial UE Message GMM: (Attach Request)

RANAP: GMM: GPRS Identity Request GPRS Attach P

RANAP: GMM: GPRS Identity Response

RANAP: MM: Authentication & Ciphering Request

RANAP:MM: Authentication&Ciphering Response

RANAP: Security Mode Command 3.Authentication

RANAP: Security Mode Complete

 RANAP: Common ID(IMSI)

RANAP: MM: Attach Accept

RANAP: MM: Attach Completed

RANAP: SM: Activate PDP Context Request

RANAP: RAB Assignment Request

ALCAP : Iu User Plane Setup

4.PS Session S

Radio Bearer Set

RANAP: RAB Assignment Response

RANAP: SM: Activate PDP Context Accept

shed
 Radio Bearer Re
Upgrade/Downg

RANAP: SM: Deactivate PDP Context Request

RANAP: SM: Deactivate PDP Context Accept

RANAP: MM: Detach Request

RANAP: MM: Detach Accept

RANAP: Iu Release Command

ALCAP: Iu User Plane Release

RANAP: Iu Release Complete


>>RRC Procedure Description
1.RRC Connection Establishment
GPRS Attach Procedure.2
3.Authentication & Security Mode Control
RRC connection setup procedure is performed for th
maximum of one RRC connection at a time.
Triggering Conditions : The UE in idle mode intitiates
SRNC receives an RRC CONNECTION REQUEST mess
connection request, based on a specific algorithm. If acce
(DCH)or on a Common Channel (CCH),based on a specif
The procedure shown is described as follows:
1.The UE sends an RRC CONNECTION REQUEST mess
2.Based on the cause in the RRC connection request and
NetworkTemporary Identity(RNTI),radio resources, and L1
allocate the specific radio link resources required for an R
3.The NodeB responds with a RADIO LINK SETUP RESP
4.The SRNC uses the ALCAP protocol to set up the Iub u
is required for the ATM-based Iub interface only.
5.The SRNC sends an RRC CONNECTION SETUP mess
6. UE and NodeB initiate L1 Synchronization. NodeB send
7. The UE sends an RRC CONNECTION SETUP COMPL
indicates that the RRC connection setup procedure ends.
If the RNC judges that the RRC connection request canno
theUE, and indicates the reject reason in the message
The GPRS Attach procedure is performed in order to
incoming PS Data.In the attach procedure, the UE shall p
PS attach and combined PS / CS attach.The identity prov
Triggering Conditons: The UE sends a GPRS Attach Re
The procedure shown is described as follows:
1.UE initiates the attach procedure by the transmission of
available. RNC opens an SCCP (Signalling Connection C
2.If the UE identifies itself with P-TMSI and the SGSN has
request the IMSI. The old SGSN responds with Identificat
3.If the UE is unknown in both the old and new SGSN, the
4. The new SGSN asks the HLR to authenticate the UE. H
subscriber information The SGSN sends the Authenticatio
and AUTN (Authentication Token) to the UE. At reception
Authentication and Ciphering response (RES) message to
Integrity Key, IK. These keys are stored together with the
transmission security. A known bit stream is encrypted and
5. If the SGSN number has changed since the GPRS deta
-The SGSN sends an Update Location (SGSN Number, S
-The HLR sends Cancel Location (IMSI, Cancellation Typ
-The old SGSN acknowledges with Cancel Location Ack (
the MM (Mobility Management) and PDP contexts
-The HLR sends Insert Subscriber Data (IMSI, GPRS sub
-The new SGSN validates the UE's presence in the (new)
Subscriber Data Ack (IMSI) message to the HLR.
-The HLR acknowledges the Update Location message b
If the Update Location is rejected by the HLR, the SGSN r
6. If Attach Type in step 1 indicated PS Attach while alread
SGSN starts the location update procedure towards the n
the VLR.

4.PS Session Setup
Radio Bearer Setup. 5
6.Downlink and Uplink Data Transfer
-The old SGSN acknowledges with Cancel Location Ack (
the MM (Mobility Management) and PDP contexts
-The HLR sends Insert Subscriber Data (IMSI, GPRS sub
-The new SGSN validates the UE's presence in the (new)
Subscriber Data Ack (IMSI) message to the HLR.
-The HLR acknowledges the Update Location message b
If the Update Location is rejected by the HLR, the SGSN r
6. If Attach Type in step 1 indicated PS Attach while alread
SGSN starts the location update procedure towards the n
the VLR.
a. The SGSN sends a Location Update Request (new LAI
indicated combined PS / CS attach. Otherwise, Location U
b. If the LA update is inter-MSC, the new VLR sends Upda
c. If the LA update is inter-MSC, the HLR sends a Cancel
d. The old VLR acknowledges with Cancel Location Ack (I
removing the MM and PDP contexts.
e. If the LA update is inter-MSC, the HLR sends Insert Su
f. The VLR acknowledges with Insert Subscriber Data Ack
g. After finishing the inter-MSC location update procedure
h. The VLR responds with Location Update Accept (VLR T
7. The SGSN sends an Attach Accept (P-TMSI, VLR TMS
Request cannot be accepted, the SGSN returns an Attac
8. If P-TMSI or VLR TMSI was changed, the UE acknowle
9. If VLR TMSI was changed, the SGSN confirms the VLR
10. Iu (Iu Interface) and SCCP signalling connections are
The authentication and security mode control pro
the integrity protection algorithm and ciphering algorithm.
Triggerring Conditions: The UE and the CN exchange s
The procedure shown is described as follows:
1.The CN sends a DIRECT TRANSFER message to the S
2.The SRNC transparently sends the contents of the DIRE
3.The UE sends an UPLINK DIRECT TRANSFER messa
4.The SRNC transparently sends the contents of the UPL
UMTS Subscriber Identity Module (USIM) judges that the
5.The CN sends a SECURITY MODE COMMAND messa
and integrity protection algorithms.
6.The SRNC sends a SECURITY MODE COMMAND mes
7.The UE sends a response message to the SRNC.
-If the integrity protection and ciphering algorithms ar
then sends a SECURITY MODE COMMAND COMPLETE
-If the UE does not support the integrity protection an
contains the error information and the reason for the failu
The RANAP:Common ID message is used to transport
The PS Session Setup procedure is performed to se
Triggering Conditions: The UE send Activate PDP conte
Mobility Management Connected that enables the user to
virtual data channel between a terminal connected to a UE
bearer establishes on request of the SGSN in order to rea
(Temporary Logical Link Identity) associated to IMSI.
IP addresses can be allocated dynamically or statistically.
addresses. This can be useful when accesing secure netw

Radio Bearer Reconfiguration to
Upgrade/Downgrade Bit Rate
PS Session Release.7
8.RRC Connection Release
The PS Session Setup procedure is performed to se
Triggering Conditions: The UE send Activate PDP conte
Mobility Management Connected that enables the user to
virtual data channel between a terminal connected to a UE
bearer establishes on request of the SGSN in order to rea
(Temporary Logical Link Identity) associated to IMSI.
IP addresses can be allocated dynamically or statistically.
addresses. This can be useful when accesing secure netw
QoS enables the operator to differentiate GPRS services.
When dynamic addressing from the home PLMN or the V
The procedure shown is described as follows:
1.The UE sends an Activate PDP Context Request (NSAP
Options) message to the SGSN The UE shall use PDP Ad
2. The SGSN sends a RAB Assignment Request message
3.The RNC establishes the appropriate radio bearer In W
4.The RNC returns a RAB Assignment Response messag
5. The SGSN validates the active PDP Context Request u
records.The SGSN sends a Create PDP Context Request
Name to find an external network and optionally to activat
6. The GGSN creates a new entry in its PDP context table
the SGSN and the external PDP network, and to start cha
7.The SGSN inserts the Network layer Service Access Po
SGSN selects Radio Priority and Packet flow Id based on
theGGSN and the UE and to start charging
The Radio Bearer Setup procedure shown is describe
1.The CN sends an RAB ASSIGNMENT REQUEST mess
2.(Optional; applicable to the ATM-based Iu-CS interface o
characteristic parameters. Based on the AAL2 link charac
3.The SRNC sends a RADIO LINK RECONFIGURATION
RAB.
4.The NodeB allocates the associated resources and then
5.(Optional; required for the ATM-based Iub interface only
synchronization by exchanging uplink and downlink synch
6.The SRNC sends a RADIO BEARER SETUP message
7.The SRNC sends a RADIO LINK RECONFIGURATION
8.After performing the radio bearer setup, the UE sends a
9.The SRNC sends an RAB ASSIGNMENT RESPONSE m
The procedure when RAB Setup Failure shown is des
1.The CN sends an RAB ASSIGNMENT REQUEST mess
2.The SRNC sends an RAB ASSIGNMENT RESPONSE m
The PS session release procedure is performed to r
Triggering Conditions : The UE send Deactivate PDP c
deactivation,the UE has the state Active. After the PDP Co
PDP contexts activated.PDP Deactivation may be initiated
The procedure shown is described as follows:
1.The UE sends a Deactivate PDP Context Request (TI, T
2.The SGSN sends a Delete PDP Context Request (TEID
contexts associated with this PDP address by including Te
3.The GGSN removes the PDP context(s) and returns a d
4.The SGSN returns a Deactivate PDP Context Accept (T
5. In Iu mode, radio access bearer release is done by the
6. The SCCP connection between RNC and SGSN is rele
The procedure shown is described as follows:
1.The UE sends a Deactivate PDP Context Request (TI, T
2.The SGSN sends a Delete PDP Context Request (TEID
contexts associated with this PDP address by including Te
3.The GGSN removes the PDP context(s) and returns a d
4.The SGSN returns a Deactivate PDP Context Accept (T
5. In Iu mode, radio access bearer release is done by the
6. The SCCP connection between RNC and SGSN is rele

The RRC Connection Release procedure is performed

Triggering Conditions: After a n RAB is released,the SR

of the UE,the SRNC initiates an RRC connection release

The procedure shown is described as follows: based o

CCH (If an RRC connection needs to be released after a
a radio bearers fails to be setup ,the RRC connection on

1.The SRNC sends an RRC CONNECTION RELEASE m

(NOTE: The SRNC may send the RRC CONNECTION RE
the transmission intervals are determined by the SRNC. If
COMPLETE message from the UE after sending the RRC

2.The UE sends an RRC CONNECTION RELEASE COM

3.The SRNC sends a RADIO LINK DELETION REQUEST
4.After releasing the resources, the NodeB sends a RADI
5.(Optional; required for the ATM-based Iub interface only
procedure ends.
edure is performed for the UE to set up a signaling connection to the SRNC. RRC connection setup is always initiated by the UE. One UE
n at a time.

UE in idle mode intitiates the RRC connection setup procedure when the NAS of the UE requests the establishment of a signaling connectio
CTION REQUEST message from the UE, the Radio Resource Management (RRM) module of the RNC determines whether to accept or rej
pecific algorithm. If accepting the request, the RRM module further determines whether to set up the RRC connection on a Dedicated Chan
CCH),based on a specific RRM algorithm. Typically, an RRC connection is set up on the DCH.

bed as follows:
CTION REQUEST message to the SRNC through the uplink CCCH(RACH), requesting the establishment of an RRC connection.
connection request and the system resource status, the SRNC determines to set up the RRC connection on a DCH and allocates the Rad
,radio resources, and L1 and L2 resources. Then the SRNC sends a RADIO LINK SETUP REQUEST message to the NodeB, requesting th
ources required for an RRC connection.
DIO LINK SETUP RESPONSE message to the SRNC after successfully preparing the resources.
otocol to set up the Iub user plane transport bearer and performs the synchronization between the SRNC and the NodeB. This procedure is
interface only.
NNECTION SETUP message to the UE through the downlink CCCH (FACH). The message contains the information about the DCH allocate
hronization. NodeB sends NBAP:Synchonization Indicator message to SRNC when the uplink enter "In-Sync" state
ECTION SETUP COMPLETE message to the SRNC through the uplink Dedicated Control Channel (DCCH) that is just set up. The messag
n setup procedure ends.
onnection request cannot be set up (for instance, due to insufficient resources), it directly sends an RRC CONNECTION REJECT message
eason in the message

is performed in order to make UE presence known to the network by performing a Packet Service Attach (GPRS attach). This makes the U
rocedure, the UE shall provide its identity and an indication of which type of attach that is to be executed.
attach.The identity provided to the network shall be the UE's Packet TMSI (P-TMSI) or IMSI

ends a GPRS Attach Request message to initiate the signaling connection setup procedure.

bed as follows:
e by the transmission of an Attach Request message to the RNC. IMSI shall be included if the UE does not have a valid P-TMSI (Packet Te
Signalling Connection Control Part) connection and sends the Attach request to SGSN
TMSI and the SGSN has changed since detach, the new SGSN sends an Identification Request (P-TMSI, old RAI, old P-TMSI Signature) to
responds with Identification Response (IMSI, Authentication vector). The old SGSN also validates the old P-TMSI
e old and new SGSN, the SGSN sends an Identity Request (Identity Type = IMSI) to the UE. The UE responds with Identity Response (IMSI
o authenticate the UE. HLR sends back to SGSN the Authentication data received from AUC (Authentication Center). The HLR contains GS
N sends the Authentication and Ciphering Request to the UE. At authentication of a WCDMA subscriber, the SGSN transmitts the RAND (Ra
to the UE. At reception of this message, the UE (USIM, WCDMA Subscriber Identity module in the UE) verifies AUTN and if accepted the U
ponse (RES) message to the SGSN. During generation of authentication vectors, the USIM in the UE also computes a new Ciphering Key. C
stored together with the CKSN (Ciphering key sequence number of Kc) until CKSN is updated at the next authentication. The SGSN verifies
stream is encrypted and decrypted in SGSN and UE.
ged since the GPRS detach, or if it is the very first attach, then the SGSN informs the HLR:

cation (SGSN Number, SGSN Address, IMSI) to the HLR.

(IMSI, Cancellation Type) to the old SGSN with Cancellation Type set to Update Procedure.
h Cancel Location Ack (IMSI). If there are any ongoing procedures for that UE, the old SGSN shall wait until these procedures are finished
nd PDP contexts
r Data (IMSI, GPRS subscription data) to the new SGSN.
's presence in the (new) RA (Routing Area). If all checks are successful then the SGSN constructs an MM context for the UE and returns an
age to the HLR.
ate Location message by sending an Update Location Ack to the SGSN after the canceling of old MM context and insertion of new MM con
by the HLR, the SGSN rejects the Attach Request from the UE with an appropriate cause code
ed PS Attach while already CS attached, or combined PS/CS attach, then the VLR shall be updated. The VLR number is received from the R
procedure towards the new MSC/VLR upon receipt of the first Insert Subscriber Data message from the HLR. This operation marks the UE
 rity mode control procedure is performed for the UE and the network to implement bi-directional authentication and to negotiate and c
and ciphering algorithm. This procedure ensures integrity and correctness of signaling

and the CN exchange signaling. The network initiates the authentication and securitymode control procedure
bed as follows:
NSFER message to the SRNC. The message indicates AUTHENTICATION REQUEST.
the contents of the DIRECT TRANSFER message to the UE through a DOWNLINK DIRECT TRANSFER message.
ECT TRANSFER message to the SRNC.
the contents of the UPLINK DIRECT TRANSFER messageto the CN through a DIRECT TRANSFER message, indicating AUTHENTICATIO
e (USIM) judges that the authentication is successful, the UE returns a message with an XRES IE.
ODE COMMAND message to the SRNC to initiate the security mode control procedure. The message contains the information about the su
ms.
MODE COMMAND message to the UE to inform the UE of the integrity protection and ciphering algorithms that the UTRAN selects.
sage to the SRNC.
ciphering algorithms are configured successfully, the UE sends a SECURITY MODE COMMAND COMPLETE message to the SRNC. T
COMMAND COMPLETE message to the CN.The message contains the information about the integrity protection and ciphering algorithms
integrity protection and ciphering algorithms, the UE sends a SECURITY MODE COMMAND FAILURE message to the SRNC. The me
d the reason for the failure. The SRNC then sends a SECURITY MODE COMMAND REJECT message to the CN
ge is used to transport the permanent UE Identity(IMSI) to SRNC

dure is performed to set up a PS session

send Activate PDP context request message to RNC. PDP Context Activation is performed when the UE initiates a packet call setup. The U
that enables the user to transmitt and receive data while moving within a PLMN. and starts the PDP context activation procedure used to se
rminal connected to a UE and a GGSN. PDP contexts deal with allocation of IP addresses to the UE and Quality of Service, QoS, paramete
he SGSN in order to realize the air interface connection. At the end the UE has an IP address NSAPI (Network layer Service Access Point I
associated to IMSI.

namically or statistically. If allocated dynamically, this significantly reduces the total number of IP addresses required per PLMN. Support of
en accesing secure networks that use the calling IP address as a form of security check. The support of
 edure is performed to release services and resources after a session ends.

send Deactivate PDP context request message to RNC. A PDP Context Deactivation is performed when the UE terminates a packet call. B
Active. After the PDP Context deactivation procedure the state becomes Packet Mobility Management Connected.The RAB will be released
ctivation may be initiated by a:UE procedure,SGSN procedure,GGSN procedure

bed as follows:
P Context Request (TI, Teardown Indication) message to the SGSN via the RNC
P Context Request (TEID, NSAPI, Teardown Indication) message to the GGSN. If Teardown Indication was included by the UE in the Deacti
P address by including Teardown Indication in the Delete PDP Context Request message
ontext(s) and returns a delete PDP Context Response (TEID) message to the SGSN. The Delete PDP Context messages are sent over the
PDP Context Accept (TI) message to the UE via the RNC
r release is done by the RAB Assignment procedure
n RNC and SGSN is released. At GPRS detach, all PDP contexts for the UE are implicitly deactivated
 rocedure is performed to release the signaling connection and all radio bearers between UE and the UTRAN

RAB is released,the SRNC judges whether the RRC connection carries any other RAB or the UE. If judging that the RRC connection does
RRC connection release procedure.

bed as follows: based on the resouce occupied by the RRC connection,there are two types of RRC connection release procedure: release
s to be released after a successful outgoing call,, the RRC connection on the DCH is released and if
the RRC connection on the CCH is released)

NNECTION RELEASE message to the UE through the DCCH.

RRC CONNECTION RELEASE message several times to increase the probability of proper reception of the message by the UE. The RRC
ermined by the SRNC. If the SRNC does not receive an RRC CONNECTION RELEASE
E after sending the RRC CONNECTION RELEASE message for four times, the SRNC judges that the UE has released the RRC connectio

CTION RELEASE COMPLETE message to the SRNC.

K DELETION REQUEST message to the NodeB,requesting the NodeB to delete the radio link resources in the NodeB.
he NodeB sends a RADIO LINK DELETION RESPONSE message to the SRNC.
based Iub interface only) The SRNC uses the ALCAP protocol to initiate an Iub user plane transport bearer release procedure. Then, the R
 s always initiated by the UE. One UE has a

establishment of a signaling connection When the

C determines whether to accept or reject the RRC
RRC connection on a Dedicated Channel

ment of an RRC connection.

ction on a DCH and allocates the Radio
T message to the NodeB, requesting the NodeB to

NC and the NodeB. This procedure is optional. It

he information about the DCH allocated by the SRNC.

In-Sync" state
DCCH) that is just set up. The message

RC CONNECTION REJECT message to

ach (GPRS attach). This makes the UE available for SMS over PS data paging via the SGSN, and notification of
ed.

es not have a valid P-TMSI (Packet Temporary IMSI)

MSI, old RAI, old P-TMSI Signature) to the old SGSN to

old P-TMSI
esponds with Identity Response (IMSI).
tication Center). The HLR contains GSM and WCDMA
er, the SGSN transmitts the RAND (Random Number)
E) verifies AUTN and if accepted the UE returns an
also computes a new Ciphering Key. CK, and a new
next authentication. The SGSN verifies the

ait until these procedures are finished before removing

MM context for the UE and returns an Insert

context and insertion of new MM context are finished.

he VLR number is received from the RA information. The

he HLR. This operation marks the UE as GPRS-attached in
 authentication and to negotiate and configure

ocedure

FER message.

message, indicating AUTHENTICATION RESPONSE. If the

contains the information about the supported ciphering

rithms that the UTRAN selects.

COMPLETE message to the SRNC. The SRNC

ty protection and ciphering algorithms that the UE uses.
LURE message to the SRNC. The message
ge to the CN

UE initiates a packet call setup. The UE has the state Packet

ontext activation procedure used to set up and remove a
and Quality of Service, QoS, parameters. A Radio Access
(Network layer Service Access Point Identifier) and a TLLI

esses required per PLMN. Support of static IP address allocation enables subscribers to provide their own IP
of
 hen the UE terminates a packet call. Before the
nt Connected.The RAB will be released if there are no other

was included by the UE in the Deactivate PDP Context Request message, then the SGSN deactivates all PDP

P Context messages are sent over the backbone network

UTRAN

udging that the RRC connection does not carry other RAB

connection release procedure: release of an RRC connection from DCH and release of an RRC connection from

n of the message by the UE. The RRC SNs of these messages are the same. The number of retransmissions and

e UE has released the RRC connection.)

ces in the NodeB.

earer release procedure. Then, the RRC connection release

Click to return to main page
RRC:RRC Connection Request (RACH)
RRC:RRC Connection Setup (FACH)
RRC:RRC Connection Setup Complete (DCCH)
RANAP: Initial UE Message GMM: (Attach Request)
RRC: Initial Direct Transfer (GMM: Attach Request)

RANAP: MM: Authentication & Ciphering Request

RRC: Downlink Direct Transfer (MM: Authentication & Ciphering Request)

RRC: Uplink Direct Transfer (MM: Authentication & Ciphering Response)

RANAP:MM: Authentication&Ciphering Response

RRC: Security Mode Command
RRC: Security Mode Complete

RANAP: MM: Attach Accept

RRC: Downlink Direct Transfer (MM: Attach Accept)

RRC: Uplink Direct Transfer (MM: Attach Completed)

 RANAP: MM: Attach Completed

RRC: Uplink Direct Transfer (SM: Activate PDP Context Request)

RANAP: SM: Activate PDP Context Request

RRC: Radio Bearer Setup
RRC: Radio Bearer Setup Complete
 RANAP: SM: Activate PDP Context Accept

RRC: Downlink Direct Transfer (SM: Activate PDP Context Accept)

RRC: Radio Bearer Reconfiguration
RRC: Radio Bearer Reconfiguration Complete
RRC: Uplink Direct Transfer (SM: Deactivate PDP Context Request)

RANAP: SM: Deactivate PDP Context Request

RANAP: SM: Deactivate PDP Context Accept

RRC: Downlink Direct Transfer (SM: Deactivate PDP Context Accept)

RRC: Radio Bearer Release

RRC: Radio Bearer Release Completed
 RRC: Downlink Direct Transfer (CC: RRC Connection Release)

RRC: Uplink Direct Transfer (CC: RRC Connection Release Complete)

RRC: Uplink Direct Transfer (MM: Detach Request)

RANAP: MM: Detach Request

 RANAP: MM: Detach Accept

RRC: Downlink Direct Transfer (MM: Detach Accept)

>>"RRC Connection Request Description"

>>"Geographical and UTRAN Entity Identifiers"

value=hex2dec(5)=5 , hex2dec(2)=2 ,hex2dec(0)=0 --> MCC=520

value=hex2dec(0)=0 , hex2dec(1)=1 --> MNC=01

value=hex2dec(2908)= 10504

value= OriginatingBackgroundCall (PS MOC)

value=(-24+ (33/2))=-7.5 dB
>>"RRC Connection Setup Description"

>>"Geographical and UTRAN Entity Identifiers"

value=hex2dec(5)=5 , hex2dec(2)=2 ,hex2dec(0)=0 --> MCC=520

value=hex2dec(0)=0 , hex2dec(1)=1 --> MNC=01

value=hex2dec(2908)= 10504
value=UE capable to support FDD , not TDD

value=UE capable to support GSM

value=Signaling Radio Bearer Information Setup ,RB-1

value=Radio Bearer Mapping

value=Signaling Radio Bearer Information Setup ,RB-2
value=Signaling Radio Bearer Information Setup ,RB-3
value=Signaling Radio Bearer Information Setup ,RB-4
value=BLER Target= -20 dB
value=MaxAllowedULTxPower=24 dBm

value=(-48*2)= -96 dBm (step of 2 dB) Default Constant

-22
-22
Note :DPCCH_Power_offset is configured by RNC and deliv

value= use Closed Loop Power Control Algorithm1

value= use long SC on Uplink

value=Spreading Factor 64 (Uplink)

value=Spreading Factor 128 (Downlink)

value=Primary Scrambling code=97

value=Spreading Factor 128 (Downlink)

Cell Identity=RNCid(12bits)+Cellid(16bits)
value=0000000010110111011110010010 => RNCid=bin2dec(000000001011)=11 and Cellid=bin2dec(0111011110010010)=30610

>>"RRC Connection Setup Complete Description"

value= not support GSM (Locked UMTS Mode)

value= Chipering Algorithm A5/3

value= UE support Band fdd2100 MHz

value= UE (Powerclass3) maximum transmitted power =24 dBm

value= support Compressed Mode (CM) uplink and downlink

value= UE support Band fdd1800 MHz
value= not support HSDPA
ng Request)

Response)
)
equest)
>>"Radio Bearer Description"
value= SF16(uplink)-> PS64
value=Primary Scrambling code=97

value= SF32(downlink)-> PS64

Cell Identity=RNCid(12bits)+Cellid(16bits)
value=0000000010110111011110010010 => RNCid=bin2dec(000000001011)=11 and Cellid=bin2dec(0111011110
Accept)
value= SF16(uplink)-> PS64
value= SF16(downlink)-> PS128
Request)
t Accept)
lease)

Complete)
)
 DPCCH_Power_offset CPICH_RSCP PCPICH Power UL Interference
-96 -80 33 -107
-96 -70 33 -107
_Power_offset is configured by RNC and delivered to UE in RRC Connection Setup.
llid=bin2dec(0111011110010010)=30610
001011)=11 and Cellid=bin2dec(0111011110010010)=30610
UL DPCCH Initial Power
-16
-26
Click to return to main page

L3 Messages - PS(H
UE NodeB

1.RRC: RRC Connection Request (RACH)

Start Rx

4.ALCAP: Iub User Plane Set

RRC Connection Establishment Timing Start Tx

5.RRC: RRC Connection Setup (FACH)

L1 Synchonization

8.RRC: RRC Connection Setup Completed (DCH)

RRC: Initial Direct Transfer (GMM: Service Request)

RRC: Security Mode Command

RRC: Security Mode Completed

RRC: Uplink Direct Transfer (SM: Activate PDP Context Request)

 ALCAP: Iub User Plane Setu

RRC: Radio Bearer Setup

Apply new transport format s

RRC: Radio Bearer Setup Complete

RRC:Measurement Control

RRC: Downlink Direct Transfer (SM: Activate PDP Context Accept)

PS Sessio

RRC:Measurement Report (e1d)

ALCAP: Iub User Plane Setu

RRC: Physical Channel Reconfiguration (DCCH)

RRC:Physical Channel Reconfiguration Complete (DCCH)

RRC: Uplink Direct Transfer (SM: Deactivate PDP Context Request)

RRC: Downlink Direct Transfer (SM: Deactivate PDP Context Accept)

 ALCAP: Iub User Plane Setu

RRC: Radio Bearer Release

RRC: Radio Bearer Release Completed

RRC: Downlink Direct Transfer (CC: RRC Connection Release)

RRC: Uplink Direct Transfer (CC: RRC Connection Release Complete)

RRC: Uplink Direct Transfer (CC: RRC Connection Release Complete)

ALCAP: Iub User Plane Relea

 L3 Messages - PS(HSDPA) Call Procedure
S-RNC

n Request (RACH)

2.NBAP:Radio Link Setup Req

3.NBAP:Radio Link Setup Resp.

4.ALCAP: Iub User Plane Setup

on Setup (FACH)

7.NBAP:Synchonization Indicator

etup Completed (DCH)

GMM: Service Request)

de Command

de Completed

ctivate PDP Context Request)

NBAP: Radio Link Reconfiguration Prepare

 NBAP: Radio Link Reconfiguration Ready

ALCAP: Iub User Plane Setup

arer Setup

NBAP: Radio Link Reconfiguration Commit

Apply new transport format set

Setup Complete

ent Control

Activate PDP Context Accept)

PS Session Established

Report (e1d)

NBAP: Radio Link Reconfiguration Prepare

NBAP: Radio Link Reconfiguration Ready

ALCAP: Iub User Plane Setup

NBAP: Radio Link Reconfiguration Commit

configuration (DCCH)

guration Complete (DCCH)

activate PDP Context Request)

Deactivate PDP Context Accept)

 NBAP: Radio Link Reconfiguration Prepare

NBAP: Radio Link Reconfiguration Ready

ALCAP: Iub User Plane Setup

NBAP: Radio Link Reconfiguration Commit

rer Release

ALCAP: Iu User Plane Release

lease Completed

C: RRC Connection Release)

C Connection Release Complete)

Connection Release Complete)

NBAP: Radio Link Deletion

Request

NBAP: Radio Link Deletion

Response

ALCAP: Iub User Plane Release

Call Procedure
CN

1.RRC Connecti

RANAP: GMM:Service Request

RANAP: Security Mode Command

RANAP: Security Mode Complete

RANAP: Common ID(IMSI)

RANAP: SM: Activate PDP Context Request

RANAP: RAB Assignment Request

ALCAP : Iu User Plane Setup

 Radio Bearer Se

RANAP: RAB Assignment Response

RANAP: SM: Activate PDP Context Accept

shed

Downlink and U

HSDPA's Serving

RANAP: SM: Deactivate PDP Context Request

RANAP: SM: Deactivate PDP Context Accept

RANAP: Iu Release Command

ALCAP: Iu User Plane Release

RANAP: Iu Release Complete


>>RRC Procedure Description
1.RRC Connection Establishment
PS Session Setup.2
RRC connection setup procedure is performed for th
maximum of one RRC connection at a time.
Triggering Conditions : The UE in idle mode intitiates
SRNC receives an RRC CONNECTION REQUEST mess
connection request, based on a specific algorithm. If acce
(DCH)or on a Common Channel (CCH),based on a specif
The procedure shown is described as follows:
1.The UE sends an RRC CONNECTION REQUEST mess
2.Based on the cause in the RRC connection request and
NetworkTemporary Identity(RNTI),radio resources, and L1
allocate the specific radio link resources required for an R
3.The NodeB responds with a RADIO LINK SETUP RESP
4.The SRNC uses the ALCAP protocol to set up the Iub u
is required for the ATM-based Iub interface only.
5.The SRNC sends an RRC CONNECTION SETUP mess
6. UE and NodeB initiate L1 Synchronization. NodeB send
7. The UE sends an RRC CONNECTION SETUP COMPL
indicates that the RRC connection setup procedure ends.
If the RNC judges that the RRC connection request canno
theUE, and indicates the reject reason in the message
The PS Session Setup procedure is performed to se
Triggering Conditions: The UE send Activate PDP conte
Mobility Management Connected that enables the user to
virtual data channel between a terminal connected to a UE
bearer establishes on request of the SGSN in order to rea
(Temporary Logical Link Identity) associated to IMSI.
IP addresses can be allocated dynamically or statistically.
addresses. This can be useful when accesing secure netw
QoS enables the operator to differentiate GPRS services.
When dynamic addressing from the home PLMN or the V
The procedure shown is described as follows:
1. The UE initiates the PS Session by using the Service R
sets-up an SCCP connection with the SGSN and transfer
2.The UE sends an Activate PDP Context Request (NSAP
Options) message to the SGSN The UE shall use PDP Ad
3. The SGSN sends a RAB Assignment Request message
4.The RNC establishes the appropriate radio bearer In W
5.The RNC returns a RAB Assignment Response messag
6. The SGSN validates the active PDP Context Request u
records.The SGSN sends a Create PDP Context Request
Name to find an external network and optionally to activat
7. The GGSN creates a new entry in its PDP context table
the SGSN and the external PDP network, and to start cha
8.The SGSN inserts the Network layer Service Access Po
SGSN selects Radio Priority and Packet flow Id based on
theGGSN and the UE and to start charging
The Radio Bearer Setup procedure shown is describe
1.The CN sends an RAB ASSIGNMENT REQUEST mess
2.(Optional; applicable to the ATM-based Iu-CS interface o
characteristic parameters. Based on the AAL2 link charac

Radio Bearer Setup. 3
Downlink and Uplink Data Transfer. 4
HSDPA's Serving Cell Change
7. The GGSN creates a new entry in its PDP context table
the SGSN and the external PDP network, and to start cha
8.The SGSN inserts the Network layer Service Access Po
SGSN selects Radio Priority and Packet flow Id based on
theGGSN and the UE and to start charging
The Radio Bearer Setup procedure shown is describe
1.The CN sends an RAB ASSIGNMENT REQUEST mess
2.(Optional; applicable to the ATM-based Iu-CS interface o
characteristic parameters. Based on the AAL2 link charac
3.The SRNC sends a RADIO LINK RECONFIGURATION
RAB.
4.The NodeB allocates the associated resources and then
5.(Optional; required for the ATM-based Iub interface only
synchronization by exchanging uplink and downlink synch
6.The SRNC sends a RADIO BEARER SETUP message
7.The SRNC sends a RADIO LINK RECONFIGURATION
8.After performing the radio bearer setup, the UE sends a
9.The SRNC sends an RAB ASSIGNMENT RESPONSE m
The procedure when RAB Setup Failure shown is des
1.The CN sends an RAB ASSIGNMENT REQUEST mess
2.The SRNC sends an RAB ASSIGNMENT RESPONSE m
The PS session release procedure is performed to r
Triggering Conditions : The UE send Deactivate PDP c
deactivation,the UE has the state Active. After the PDP Co
PDP contexts activated.PDP Deactivation may be initiated
The procedure shown is described as follows:
1.The UE sends a Deactivate PDP Context Request (TI, T
2.The SGSN sends a Delete PDP Context Request (TEID
contexts associated with this PDP address by including Te
3.The GGSN removes the PDP context(s) and returns a d
4.The SGSN returns a Deactivate PDP Context Accept (T
5. In Iu mode, radio access bearer release is done by the
6. The SCCP connection between RNC and SGSN is rele
The RRC Connection Release procedure is performed
Triggering Conditions: After a n RAB is released,the SR
of the UE,the SRNC initiates an RRC connection release
The procedure shown is described as follows: based o
CCH (If an RRC connection needs to be released after a
a radio bearers fails to be setup ,the RRC connection on
1.The SRNC sends an RRC CONNECTION RELEASE m
(NOTE: The SRNC may send the RRC CONNECTION RE
the transmission intervals are determined by the SRNC. If
COMPLETE message from the UE after sending the RRC
2.The UE sends an RRC CONNECTION RELEASE COM
3.The SRNC sends a RADIO LINK DELETION REQUEST
4.After releasing the resources, the NodeB sends a RADI
5.(Optional; required for the ATM-based Iub interface only
 CCH (If an RRC connection needs to be released after a
a radio bearers fails to be setup ,the RRC connection on

1.The SRNC sends an RRC CONNECTION RELEASE m

(NOTE: The SRNC may send the RRC CONNECTION RE
the transmission intervals are determined by the SRNC. If
COMPLETE message from the UE after sending the RRC

2.The UE sends an RRC CONNECTION RELEASE COM

3.The SRNC sends a RADIO LINK DELETION REQUEST
4.After releasing the resources, the NodeB sends a RADI
5.(Optional; required for the ATM-based Iub interface only
PS Session Release.5 procedure ends.

RRC Connection Release.6

edure is performed for the UE to set up a signaling connection to the SRNC. RRC connection setup is always initiated by the UE. One UE
n at a time.

UE in idle mode intitiates the RRC connection setup procedure when the NAS of the UE requests the establishment of a signaling connectio
CTION REQUEST message from the UE, the Radio Resource Management (RRM) module of the RNC determines whether to accept or rej
pecific algorithm. If accepting the request, the RRM module further determines whether to set up the RRC connection on a Dedicated Chan
CCH),based on a specific RRM algorithm. Typically, an RRC connection is set up on the DCH.

bed as follows:
CTION REQUEST message to the SRNC through the uplink CCCH(RACH), requesting the establishment of an RRC connection.
connection request and the system resource status, the SRNC determines to set up the RRC connection on a DCH and allocates the Rad
,radio resources, and L1 and L2 resources. Then the SRNC sends a RADIO LINK SETUP REQUEST message to the NodeB, requesting th
ources required for an RRC connection.
DIO LINK SETUP RESPONSE message to the SRNC after successfully preparing the resources.
otocol to set up the Iub user plane transport bearer and performs the synchronization between the SRNC and the NodeB. This procedure is
interface only.
NNECTION SETUP message to the UE through the downlink CCCH (FACH). The message contains the information about the DCH allocate
hronization. NodeB sends NBAP:Synchonization Indicator message to SRNC when the uplink enter "In-Sync" state
ECTION SETUP COMPLETE message to the SRNC through the uplink Dedicated Control Channel (DCCH) that is just set up. The messag
n setup procedure ends.
onnection request cannot be set up (for instance, due to insufficient resources), it directly sends an RRC CONNECTION REJECT message
eason in the message

dure is performed to set up a PS session

send Activate PDP context request message to RNC. PDP Context Activation is performed when the UE initiates a packet call setup. The U
that enables the user to transmitt and receive data while moving within a PLMN. and starts the PDP context activation procedure used to se
rminal connected to a UE and a GGSN. PDP contexts deal with allocation of IP addresses to the UE and Quality of Service, QoS, paramete
he SGSN in order to realize the air interface connection. At the end the UE has an IP address NSAPI (Network layer Service Access Point I
associated to IMSI.

namically or statistically. If allocated dynamically, this significantly reduces the total number of IP addresses required per PLMN. Support of
en accesing secure networks that use the calling IP address as a form of security check. The support of
rentiate GPRS services.

he home PLMN or the Visitor PLMN is used, it is the responsibility of the GGSN to allocate and release the dynamic PDP address.
bed as follows:
n by using the Service Request (Service Type=Data) message. After the RR setup completion the UE asks for initial direct transfer to the se
h the SGSN and transfers the initial service request (Authentication and ciphering may performed depends on operator's setting)
Context Request (NSAPI, TI(Teardown Indication), PDP Type, Address, APN (Access Point Name), QoS (Quality of Service) Requested, P
he UE shall use PDP Address to indicate whether it requires the use of a static PDP address or whether it requires the use of a dynamic PD
nment Request message to the RNC to establish a RABs
priate radio bearer In WCDMA, RAB setup is done by the RAB Assignment procedure
ment Response message to the SGSN
PDP Context Request using PDP Type (optional), PDP Address, APN (Access Point Name (optional) provided by the UE and the PDP cont
te PDP Context Request message to the affected GGSN. Access Point Name shall be the APN Network Identifier of the APN. The GGSN m
and optionally to activate a service for this APN
y in its PDP context table and generates a Charging Id. The new entry allows the GGSN to route PDP PDUs (Policy Decision Point Protocol
network, and to start charging
layer Service Access Point Identifier, NSAPI along with the GGSN address in its PDP context and informs the UE via RNC that the PDP Co
Packet flow Id based on QoS Negotiated, and returns an Activate PDP Context Accept message to the UE. The SGSN is now able to route
charging

dure shown is described as follows:

NMENT REQUEST message to the SRNC to initiate the RAB setup procedure.
M-based Iu-CS interface only) The SRNC maps the Quality of Service (QoS) parameters for the RAB to the AAL2 link characteristic paramet
on the AAL2 link characteristic parameters,the ALCAP on the Iu interface initiates an Iu user plane transport bearer setup procedure.
 edure is performed to release services and resources after a session ends.

send Deactivate PDP context request message to RNC. A PDP Context Deactivation is performed when the UE terminates a packet call. B
Active. After the PDP Context deactivation procedure the state becomes Packet Mobility Management Connected.The RAB will be released
ctivation may be initiated by a:UE procedure,SGSN procedure,GGSN procedure

bed as follows:
P Context Request (TI, Teardown Indication) message to the SGSN via the RNC
P Context Request (TEID, NSAPI, Teardown Indication) message to the GGSN. If Teardown Indication was included by the UE in the Deacti
P address by including Teardown Indication in the Delete PDP Context Request message
ontext(s) and returns a delete PDP Context Response (TEID) message to the SGSN. The Delete PDP Context messages are sent over the
PDP Context Accept (TI) message to the UE via the RNC
r release is done by the RAB Assignment procedure
n RNC and SGSN is released. At GPRS detach, all PDP contexts for the UE are implicitly deactivated

rocedure is performed to release the signaling connection and all radio bearers between UE and the UTRAN

RAB is released,the SRNC judges whether the RRC connection carries any other RAB or the UE. If judging that the RRC connection does
RRC connection release procedure.

bed as follows: based on the resouce occupied by the RRC connection,there are two types of RRC connection release procedure: release
s to be released after a successful outgoing call,, the RRC connection on the DCH is released and if
the RRC connection on the CCH is released)

NNECTION RELEASE message to the UE through the DCCH.

RRC CONNECTION RELEASE message several times to increase the probability of proper reception of the message by the UE. The RRC
ermined by the SRNC. If the SRNC does not receive an RRC CONNECTION RELEASE
E after sending the RRC CONNECTION RELEASE message for four times, the SRNC judges that the UE has released the RRC connectio

CTION RELEASE COMPLETE message to the SRNC.

K DELETION REQUEST message to the NodeB,requesting the NodeB to delete the radio link resources in the NodeB.
he NodeB sends a RADIO LINK DELETION RESPONSE message to the SRNC.
based Iub interface only) The SRNC uses the ALCAP protocol to initiate an Iub user plane transport bearer release procedure. Then, the R
 s always initiated by the UE. One UE has a

establishment of a signaling connection When the

C determines whether to accept or reject the RRC
RRC connection on a Dedicated Channel

ment of an RRC connection.

ction on a DCH and allocates the Radio
T message to the NodeB, requesting the NodeB to

NC and the NodeB. This procedure is optional. It

he information about the DCH allocated by the SRNC.

In-Sync" state
DCCH) that is just set up. The message

RC CONNECTION REJECT message to

UE initiates a packet call setup. The UE has the state Packet

ontext activation procedure used to set up and remove a
and Quality of Service, QoS, parameters. A Radio Access
(Network layer Service Access Point Identifier) and a TLLI

esses required per PLMN. Support of static IP address allocation enables subscribers to provide their own IP
of

e the dynamic PDP address.

asks for initial direct transfer to the serving node. The RNC
ends on operator's setting)
QoS (Quality of Service) Requested, PDP Configuration
her it requires the use of a dynamic PDP address.

provided by the UE and the PDP context subscription

ork Identifier of the APN. The GGSN may use Access Point

PDUs (Policy Decision Point Protocol Data Units) between

orms the UE via RNC that the PDP Context is Accepted. The
e UE. The SGSN is now able to route PDP PDUs between

o the AAL2 link characteristic parameters and radio resource

ansport bearer setup procedure.
 hen the UE terminates a packet call. Before the
nt Connected.The RAB will be released if there are no other

was included by the UE in the Deactivate PDP Context Request message, then the SGSN deactivates all PDP

P Context messages are sent over the backbone network

UTRAN

udging that the RRC connection does not carry other RAB

connection release procedure: release of an RRC connection from DCH and release of an RRC connection from

n of the message by the UE. The RRC SNs of these messages are the same. The number of retransmissions and

e UE has released the RRC connection.)

ces in the NodeB.

earer release procedure. Then, the RRC connection release

Click to return to main page
RRC:RRC Connection Request (RACH)
RRC:RRC Connection Setup (FACH)
RRC:RRC Connection Setup Complete (DCCH)
RRC: Initial Direct Transfer (GMM: Service Request)

RANAP: GMM:Service Request

RRC: Security Mode Command
 RRC: Security Mode Complete

RRC: Uplink Direct Transfer (SM: Activate PDP Context Request)

RANAP: SM: Activate PDP Context Request

RRC: Radio Bearer Setup
RRC: Radio Bearer Setup Complete
 RANAP: SM: Activate PDP Context Accept

RRC: Downlink Direct Transfer (SM: Activate PDP Context Accept)

RRC: Physical Channel Reconfiguration (DCCH)
 RRC:Physical Channel Reconfiguration Complete (DCCH)

RRC: Uplink Direct Transfer (SM: Deactivate PDP Context Request)

 RANAP: SM: Deactivate PDP Context Request

RANAP: SM: Deactivate PDP Context Accept

RRC: Downlink Direct Transfer (SM: Deactivate PDP Context Accept)

RRC: Radio Bearer Release

RRC: Radio Bearer Release Completed
 RRC: Downlink Direct Transfer (CC: RRC Connection Release)

RRC: Uplink Direct Transfer (CC: RRC Connection Release Complete)

>>"RRC Connection Request Description"

>>"Geographical and UTRAN Entity Identifiers"

value=hex2dec(4)=4 , hex2dec(1)=1 ,hex2dec(3)=3 --> MCC=413

value=hex2dec(0)=0 , hex2dec(1)=1 --> MNC=01

value=hex2dec(7594)= 30100

value= OriginatingBackgroundCall (PS MOC)

value=(-24+ (37/2))=-5.5 dB
value= HSDPA Release5

>>"RRC Connection Setup Description"

>>"Geographical and UTRAN Entity Identifiers"

value=hex2dec(4)=4 , hex2dec(1)=1 ,hex2dec(3)=3 --> MCC=413

value=hex2dec(0)=0 , hex2dec(1)=1 --> MNC=01

value=hex2dec(7594)= 30100
value=UE capable to support FDD , not TDD

value=UE capable to support GSM

value=Signaling Radio Bearer Information Setup ,RB-1

value=Radio Bearer Mapping

value=Signaling Radio Bearer Information Setup ,RB-2
value=Signaling Radio Bearer Information Setup ,RB-3
value=Signaling Radio Bearer Information Setup ,RB-4
value=BLER Target= -20 dB
value=MaxAllowedULTxPower=24 dBm

value=(-48*2)= -96 dBm (step of 2 dB)

Default Constant
-22
-22
Note :DPCCH_Power_offset is configured by RNC an
value= use Closed Loop Power Control Algorithm1

value= use long SC on Uplink

value=Spreading Factor 64 (Uplink)

value=Spreading Factor 128 (Downlink)

value=Primary Scrambling code=30

value=Spreading Factor 128 (Downlink)

Cell Identity=RNCid(12bits)+Cellid(16bits)
value=0000000000010001010100101111 => RNCid=bin2dec(000000000001)=1 and Cellid=bin2dec(0001010100101111)=5423

>>"RRC Connection Setup Complete Description"

value=support GSM (Dual Mode GSM<>UMTS)

value= Chipering Algorithm A5/3

value= support Compressed Mode (CM) uplink and downlink

value= support HSDPA, UE Category 6
uest)
>>"Radio Bearer Description"
value= SF16(uplink)-> PS64
 value= HSDPA Channel Information

value= hs-SCCH , Fixed SF 128 , Code No=4,5,6,7

In theory, one cell can configure up to 15 HS-SCCH. But now commercial UE can only monitor up to 4

value= SF256(downlink)
value= HSDPA Serving Cell's Primary SC = 30

value= SF256(downlink)

Cell Identity=RNCid(12bits)+Cellid(16bits)
value=0000000000010001010100101111 => RNCid=bin2dec(000000000001)=1 and Cellid=bin2dec(00010
ccept)
value= PrimarySC=30, no longer a HSDPA serving cell ( HSDPA Serving Cell Change)

(Old HSDPA's Serving Cell)

Cell Identity=RNCid(12bits)+Cellid(16bits)
value=0000000000010001010100101111 => RNCid=bin2dec(000000000001)=1 and Cellid=bin2dec(00010

value= PrimarySC=9 is a new HSDPA serving cell ( HSDPA Serving Cell Change)
 (New HSDPA's Serving Cell)
Cell Identity=RNCid(12bits)+Cellid(16bits)
value=0000000000010001000111011100=> RNCid=bin2dec(000000000001)=1 and Cellid=bin2dec(00010

H)

quest)
Accept)
ase)

mplete)
 DPCCH_Power_offset CPICH_RSCP PCPICH Power UL Interference
-96 -80 33 -107
-96 -70 33 -107
_Power_offset is configured by RNC and delivered to UE in RRC Connection Setup.
n2dec(0001010100101111)=5423
mercial UE can only monitor up to 4 HS-SCCH channels simultaneously. So one cell only configure up to 4 HS-SCCH channels
0000001)=1 and Cellid=bin2dec(0001010100101111)=5423
erving Cell Change)

0000001)=1 and Cellid=bin2dec(0001010100101111)=5423

g Cell Change)
000001)=1 and Cellid=bin2dec(0001000111011100)=4572
UL DPCCH Initial Power
-16
-26
gure up to 4 HS-SCCH channels
Click to return to main page

L3 Messages - PS(H
UE NodeB

1.RRC: RRC Connection Request (RACH)

Start Rx

4.ALCAP: Iub User Plane Set

RRC Connection Establishment Timing Start Tx

5.RRC: RRC Connection Setup (FACH)

L1 Synchonization

8.RRC: RRC Connection Setup Completed (DCH)

RRC: Initial Direct Transfer (GMM: Service Request)

RRC: Security Mode Command

RRC: Security Mode Completed

RRC: Uplink Direct Transfer (SM: Activate PDP Context Request)

 ALCAP: Iub User Plane Setu

RRC: Radio Bearer Setup

Apply new transport format s

RRC: Radio Bearer Setup Complete

RRC:Measurement Control

RRC: Downlink Direct Transfer (SM: Activate PDP Context Accept)

PS Sessio

RRC:Measurement Report (e1d)

ALCAP: Iub User Plane Setu

RRC: Physical Channel Reconfiguration (DCCH)

RRC:Physical Channel Reconfiguration Complete (DCCH)

RRC: Uplink Direct Transfer (SM: Deactivate PDP Context Request)

RRC: Downlink Direct Transfer (SM: Deactivate PDP Context Accept)

 ALCAP: Iub User Plane Setu

RRC: Radio Bearer Release

RRC: Radio Bearer Release Completed

RRC: Downlink Direct Transfer (CC: RRC Connection Release)

RRC: Uplink Direct Transfer (CC: RRC Connection Release Complete)

RRC: Uplink Direct Transfer (CC: RRC Connection Release Complete)

ALCAP: Iub User Plane Relea

 L3 Messages - PS(HSUPA) Call Procedure
S-RNC

n Request (RACH)

2.NBAP:Radio Link Setup Req

3.NBAP:Radio Link Setup Resp.

4.ALCAP: Iub User Plane Setup

on Setup (FACH)

7.NBAP:Synchonization Indicator

etup Completed (DCH)

GMM: Service Request)

de Command

de Completed

ctivate PDP Context Request)

NBAP: Radio Link Reconfiguration Prepare

 NBAP: Radio Link Reconfiguration Ready

ALCAP: Iub User Plane Setup

arer Setup

NBAP: Radio Link Reconfiguration Commit

Apply new transport format set

Setup Complete

ent Control

Activate PDP Context Accept)

PS Session Established

Report (e1d)

NBAP: Radio Link Reconfiguration Prepare

NBAP: Radio Link Reconfiguration Ready

ALCAP: Iub User Plane Setup

NBAP: Radio Link Reconfiguration Commit

configuration (DCCH)

guration Complete (DCCH)

activate PDP Context Request)

Deactivate PDP Context Accept)

 NBAP: Radio Link Reconfiguration Prepare

NBAP: Radio Link Reconfiguration Ready

ALCAP: Iub User Plane Setup

NBAP: Radio Link Reconfiguration Commit

rer Release

ALCAP: Iu User Plane Release

lease Completed

C: RRC Connection Release)

C Connection Release Complete)

Connection Release Complete)

NBAP: Radio Link Deletion

Request

NBAP: Radio Link Deletion

Response

ALCAP: Iub User Plane Release

Call Procedure
CN

1.RRC Connecti

RANAP: GMM:Service Request

RANAP: Security Mode Command

RANAP: Security Mode Complete

RANAP: Common ID(IMSI)

RANAP: SM: Activate PDP Context Request

RANAP: RAB Assignment Request

ALCAP : Iu User Plane Setup

 Radio Bearer Se

RANAP: RAB Assignment Response

RANAP: SM: Activate PDP Context Accept

shed

Downlink and U

HSPA's Serving C

RANAP: SM: Deactivate PDP Context Request

RANAP: SM: Deactivate PDP Context Accept

RANAP: Iu Release Command

ALCAP: Iu User Plane Release

RANAP: Iu Release Complete


>>RRC Procedure Description
1.RRC Connection Establishment
PS Session Setup.2
RRC connection setup procedure is performed for th
maximum of one RRC connection at a time.
Triggering Conditions : The UE in idle mode intitiates
SRNC receives an RRC CONNECTION REQUEST mess
connection request, based on a specific algorithm. If acce
(DCH)or on a Common Channel (CCH),based on a specif
The procedure shown is described as follows:
1.The UE sends an RRC CONNECTION REQUEST mess
2.Based on the cause in the RRC connection request and
NetworkTemporary Identity(RNTI),radio resources, and L1
allocate the specific radio link resources required for an R
3.The NodeB responds with a RADIO LINK SETUP RESP
4.The SRNC uses the ALCAP protocol to set up the Iub u
is required for the ATM-based Iub interface only.
5.The SRNC sends an RRC CONNECTION SETUP mess
6. UE and NodeB initiate L1 Synchronization. NodeB send
7. The UE sends an RRC CONNECTION SETUP COMPL
indicates that the RRC connection setup procedure ends.
If the RNC judges that the RRC connection request canno
theUE, and indicates the reject reason in the message
The PS Session Setup procedure is performed to se
Triggering Conditions: The UE send Activate PDP conte
Mobility Management Connected that enables the user to
virtual data channel between a terminal connected to a UE
bearer establishes on request of the SGSN in order to rea
(Temporary Logical Link Identity) associated to IMSI.
IP addresses can be allocated dynamically or statistically.
addresses. This can be useful when accesing secure netw
QoS enables the operator to differentiate GPRS services.
When dynamic addressing from the home PLMN or the V
The procedure shown is described as follows:
1. The UE initiates the PS Session by using the Service R
sets-up an SCCP connection with the SGSN and transfer
2.The UE sends an Activate PDP Context Request (NSAP
Options) message to the SGSN The UE shall use PDP Ad
3. The SGSN sends a RAB Assignment Request message
4.The RNC establishes the appropriate radio bearer In W
5.The RNC returns a RAB Assignment Response messag
6. The SGSN validates the active PDP Context Request u
records.The SGSN sends a Create PDP Context Request
Name to find an external network and optionally to activat
7. The GGSN creates a new entry in its PDP context table
the SGSN and the external PDP network, and to start cha
8.The SGSN inserts the Network layer Service Access Po
SGSN selects Radio Priority and Packet flow Id based on
theGGSN and the UE and to start charging
The Radio Bearer Setup procedure shown is describe
1.The CN sends an RAB ASSIGNMENT REQUEST mess
2.(Optional; applicable to the ATM-based Iu-CS interface o
characteristic parameters. Based on the AAL2 link charac

Radio Bearer Setup. 3
Downlink and Uplink Data Transfer. 4
HSPA's Serving Cell Change
7. The GGSN creates a new entry in its PDP context table
the SGSN and the external PDP network, and to start cha
8.The SGSN inserts the Network layer Service Access Po
SGSN selects Radio Priority and Packet flow Id based on
theGGSN and the UE and to start charging
The Radio Bearer Setup procedure shown is describe
1.The CN sends an RAB ASSIGNMENT REQUEST mess
2.(Optional; applicable to the ATM-based Iu-CS interface o
characteristic parameters. Based on the AAL2 link charac
3.The SRNC sends a RADIO LINK RECONFIGURATION
RAB.
4.The NodeB allocates the associated resources and then
5.(Optional; required for the ATM-based Iub interface only
synchronization by exchanging uplink and downlink synch
6.The SRNC sends a RADIO BEARER SETUP message
7.The SRNC sends a RADIO LINK RECONFIGURATION
8.After performing the radio bearer setup, the UE sends a
9.The SRNC sends an RAB ASSIGNMENT RESPONSE m
The procedure when RAB Setup Failure shown is des
1.The CN sends an RAB ASSIGNMENT REQUEST mess
2.The SRNC sends an RAB ASSIGNMENT RESPONSE m
The PS session release procedure is performed to r
Triggering Conditions : The UE send Deactivate PDP c
deactivation,the UE has the state Active. After the PDP Co
PDP contexts activated.PDP Deactivation may be initiated
The procedure shown is described as follows:
1.The UE sends a Deactivate PDP Context Request (TI, T
2.The SGSN sends a Delete PDP Context Request (TEID
contexts associated with this PDP address by including Te
3.The GGSN removes the PDP context(s) and returns a d
4.The SGSN returns a Deactivate PDP Context Accept (T
5. In Iu mode, radio access bearer release is done by the
6. The SCCP connection between RNC and SGSN is rele
The RRC Connection Release procedure is performed
Triggering Conditions: After a n RAB is released,the SR
of the UE,the SRNC initiates an RRC connection release
The procedure shown is described as follows: based o
CCH (If an RRC connection needs to be released after a
a radio bearers fails to be setup ,the RRC connection on
1.The SRNC sends an RRC CONNECTION RELEASE m
(NOTE: The SRNC may send the RRC CONNECTION RE
the transmission intervals are determined by the SRNC. If
COMPLETE message from the UE after sending the RRC
2.The UE sends an RRC CONNECTION RELEASE COM
3.The SRNC sends a RADIO LINK DELETION REQUEST
4.After releasing the resources, the NodeB sends a RADI
5.(Optional; required for the ATM-based Iub interface only
 CCH (If an RRC connection needs to be released after a
a radio bearers fails to be setup ,the RRC connection on

1.The SRNC sends an RRC CONNECTION RELEASE m

(NOTE: The SRNC may send the RRC CONNECTION RE
the transmission intervals are determined by the SRNC. If
COMPLETE message from the UE after sending the RRC

2.The UE sends an RRC CONNECTION RELEASE COM

3.The SRNC sends a RADIO LINK DELETION REQUEST
4.After releasing the resources, the NodeB sends a RADI
5.(Optional; required for the ATM-based Iub interface only
PS Session Release.5 procedure ends.

RRC Connection Release.6

edure is performed for the UE to set up a signaling connection to the SRNC. RRC connection setup is always initiated by the UE. One UE
n at a time.

UE in idle mode intitiates the RRC connection setup procedure when the NAS of the UE requests the establishment of a signaling connectio
CTION REQUEST message from the UE, the Radio Resource Management (RRM) module of the RNC determines whether to accept or rej
pecific algorithm. If accepting the request, the RRM module further determines whether to set up the RRC connection on a Dedicated Chan
CCH),based on a specific RRM algorithm. Typically, an RRC connection is set up on the DCH.

bed as follows:
CTION REQUEST message to the SRNC through the uplink CCCH(RACH), requesting the establishment of an RRC connection.
connection request and the system resource status, the SRNC determines to set up the RRC connection on a DCH and allocates the Rad
,radio resources, and L1 and L2 resources. Then the SRNC sends a RADIO LINK SETUP REQUEST message to the NodeB, requesting th
ources required for an RRC connection.
DIO LINK SETUP RESPONSE message to the SRNC after successfully preparing the resources.
otocol to set up the Iub user plane transport bearer and performs the synchronization between the SRNC and the NodeB. This procedure is
interface only.
NNECTION SETUP message to the UE through the downlink CCCH (FACH). The message contains the information about the DCH allocate
hronization. NodeB sends NBAP:Synchonization Indicator message to SRNC when the uplink enter "In-Sync" state
ECTION SETUP COMPLETE message to the SRNC through the uplink Dedicated Control Channel (DCCH) that is just set up. The messag
n setup procedure ends.
onnection request cannot be set up (for instance, due to insufficient resources), it directly sends an RRC CONNECTION REJECT message
eason in the message

dure is performed to set up a PS session

send Activate PDP context request message to RNC. PDP Context Activation is performed when the UE initiates a packet call setup. The U
that enables the user to transmitt and receive data while moving within a PLMN. and starts the PDP context activation procedure used to se
rminal connected to a UE and a GGSN. PDP contexts deal with allocation of IP addresses to the UE and Quality of Service, QoS, paramete
he SGSN in order to realize the air interface connection. At the end the UE has an IP address NSAPI (Network layer Service Access Point I
associated to IMSI.

namically or statistically. If allocated dynamically, this significantly reduces the total number of IP addresses required per PLMN. Support of
en accesing secure networks that use the calling IP address as a form of security check. The support of
rentiate GPRS services.

he home PLMN or the Visitor PLMN is used, it is the responsibility of the GGSN to allocate and release the dynamic PDP address.
bed as follows:
n by using the Service Request (Service Type=Data) message. After the RR setup completion the UE asks for initial direct transfer to the se
h the SGSN and transfers the initial service request (Authentication and ciphering may performed depends on operator's setting)
Context Request (NSAPI, TI(Teardown Indication), PDP Type, Address, APN (Access Point Name), QoS (Quality of Service) Requested, P
he UE shall use PDP Address to indicate whether it requires the use of a static PDP address or whether it requires the use of a dynamic PD
nment Request message to the RNC to establish a RABs
priate radio bearer In WCDMA, RAB setup is done by the RAB Assignment procedure
ment Response message to the SGSN
PDP Context Request using PDP Type (optional), PDP Address, APN (Access Point Name (optional) provided by the UE and the PDP cont
te PDP Context Request message to the affected GGSN. Access Point Name shall be the APN Network Identifier of the APN. The GGSN m
and optionally to activate a service for this APN
y in its PDP context table and generates a Charging Id. The new entry allows the GGSN to route PDP PDUs (Policy Decision Point Protocol
network, and to start charging
layer Service Access Point Identifier, NSAPI along with the GGSN address in its PDP context and informs the UE via RNC that the PDP Co
Packet flow Id based on QoS Negotiated, and returns an Activate PDP Context Accept message to the UE. The SGSN is now able to route
charging

dure shown is described as follows:

NMENT REQUEST message to the SRNC to initiate the RAB setup procedure.
M-based Iu-CS interface only) The SRNC maps the Quality of Service (QoS) parameters for the RAB to the AAL2 link characteristic paramet
on the AAL2 link characteristic parameters,the ALCAP on the Iu interface initiates an Iu user plane transport bearer setup procedure.
 edure is performed to release services and resources after a session ends.

send Deactivate PDP context request message to RNC. A PDP Context Deactivation is performed when the UE terminates a packet call. B
Active. After the PDP Context deactivation procedure the state becomes Packet Mobility Management Connected.The RAB will be released
ctivation may be initiated by a:UE procedure,SGSN procedure,GGSN procedure

bed as follows:
P Context Request (TI, Teardown Indication) message to the SGSN via the RNC
P Context Request (TEID, NSAPI, Teardown Indication) message to the GGSN. If Teardown Indication was included by the UE in the Deacti
P address by including Teardown Indication in the Delete PDP Context Request message
ontext(s) and returns a delete PDP Context Response (TEID) message to the SGSN. The Delete PDP Context messages are sent over the
PDP Context Accept (TI) message to the UE via the RNC
r release is done by the RAB Assignment procedure
n RNC and SGSN is released. At GPRS detach, all PDP contexts for the UE are implicitly deactivated

rocedure is performed to release the signaling connection and all radio bearers between UE and the UTRAN

RAB is released,the SRNC judges whether the RRC connection carries any other RAB or the UE. If judging that the RRC connection does
RRC connection release procedure.

bed as follows: based on the resouce occupied by the RRC connection,there are two types of RRC connection release procedure: release
s to be released after a successful outgoing call,, the RRC connection on the DCH is released and if
the RRC connection on the CCH is released)

NNECTION RELEASE message to the UE through the DCCH.

RRC CONNECTION RELEASE message several times to increase the probability of proper reception of the message by the UE. The RRC
ermined by the SRNC. If the SRNC does not receive an RRC CONNECTION RELEASE
E after sending the RRC CONNECTION RELEASE message for four times, the SRNC judges that the UE has released the RRC connectio

CTION RELEASE COMPLETE message to the SRNC.

K DELETION REQUEST message to the NodeB,requesting the NodeB to delete the radio link resources in the NodeB.
he NodeB sends a RADIO LINK DELETION RESPONSE message to the SRNC.
based Iub interface only) The SRNC uses the ALCAP protocol to initiate an Iub user plane transport bearer release procedure. Then, the R
 s always initiated by the UE. One UE has a

establishment of a signaling connection When the

C determines whether to accept or reject the RRC
RRC connection on a Dedicated Channel

ment of an RRC connection.

ction on a DCH and allocates the Radio
T message to the NodeB, requesting the NodeB to

NC and the NodeB. This procedure is optional. It

he information about the DCH allocated by the SRNC.

In-Sync" state
DCCH) that is just set up. The message

RC CONNECTION REJECT message to

UE initiates a packet call setup. The UE has the state Packet

ontext activation procedure used to set up and remove a
and Quality of Service, QoS, parameters. A Radio Access
(Network layer Service Access Point Identifier) and a TLLI

esses required per PLMN. Support of static IP address allocation enables subscribers to provide their own IP
of

e the dynamic PDP address.

asks for initial direct transfer to the serving node. The RNC
ends on operator's setting)
QoS (Quality of Service) Requested, PDP Configuration
her it requires the use of a dynamic PDP address.

provided by the UE and the PDP context subscription

ork Identifier of the APN. The GGSN may use Access Point

PDUs (Policy Decision Point Protocol Data Units) between

orms the UE via RNC that the PDP Context is Accepted. The
e UE. The SGSN is now able to route PDP PDUs between

o the AAL2 link characteristic parameters and radio resource

ansport bearer setup procedure.
 hen the UE terminates a packet call. Before the
nt Connected.The RAB will be released if there are no other

was included by the UE in the Deactivate PDP Context Request message, then the SGSN deactivates all PDP

P Context messages are sent over the backbone network

UTRAN

udging that the RRC connection does not carry other RAB

connection release procedure: release of an RRC connection from DCH and release of an RRC connection from

n of the message by the UE. The RRC SNs of these messages are the same. The number of retransmissions and

e UE has released the RRC connection.)

ces in the NodeB.

earer release procedure. Then, the RRC connection release

Click to return to main page
RRC:RRC Connection Request (RACH)
RRC:RRC Connection Setup (FACH)
RRC:RRC Connection Setup Complete (DCCH)
RRC: Initial Direct Transfer (GMM: Service Request)
RANAP: GMM:Service Request

RRC: Security Mode Command

RRC: Security Mode Complete
RRC: Uplink Direct Transfer (SM: Activate PDP Context Request)
RANAP: SM: Activate PDP Context Request

RRC: Radio Bearer Setup

 RRC: Radio Bearer Setup Complete

RANAP: SM: Activate PDP Context Accept

RRC: Downlink Direct Transfer (SM: Activate PDP Context Accept)

RRC: Physical Channel Reconfiguration (DCCH)

RRC:Physical Channel Reconfiguration Complete (DCCH)
RRC: Uplink Direct Transfer (SM: Deactivate PDP Context Request)

RANAP: SM: Deactivate PDP Context Request

RANAP: SM: Deactivate PDP Context Accept

RRC: Downlink Direct Transfer (SM: Deactivate PDP Context Accept)

RRC: Radio Bearer Release

 RRC: Radio Bearer Release Completed

RRC: Downlink Direct Transfer (CC: RRC Connection Release)

RRC: Uplink Direct Transfer (CC: RRC Connection Release Complete)

RRC:Measurement Report (e1d)

RRC:Measurement Control
>>"RRC Connection Request Description"

>>"Geographical and UTRAN Entity Identifiers"

value=hex2dec(5)=5 , hex2dec(2)=2 ,hex2dec(0)=0 --> MCC=520

value=hex2dec(9)=9 , hex2dec(9)=9 --> MNC=99

value=hex2dec(03EA)= 1002

value= OriginatingBackgroundCall (PS MOC)

value=(-24+ (39/2))=-4.5 dB

value=Primary Scrambling Code=60 ( Neighbour's SC)

value=(-24+ (37/2))=-5.5 dB

value= HSPA Release6

value= UE support HSDPA and E-DCH (HSUPA)

>>"RRC Connection Setup Description"

>>"Geographical and UTRAN Entity Identifiers"

value=hex2dec(5)=5 , hex2dec(2)=2 ,hex2dec(0)=0 --> MCC=520

value=hex2dec(9)=9 , hex2dec(9)=9 --> MNC=99

value=hex2dec(03EA)= 1002
value=UE capable to support FDD , not TDD

value=Signaling Radio Bearer Information Setup ,RB-1

value=Radio Bearer Mapping

value=Signaling Radio Bearer Information Setup ,RB-2
value=Signaling Radio Bearer Information Setup ,RB-3
value=Signaling Radio Bearer Information Setup ,RB-4
value=BLER Target= -20 dB

value=MaxAllowedULTxPower=24 dBm

value=(-47*2)= -94 dBm (step of 2 dB)

value= use Closed Loop Power Control Algorithm1

value= use long SC on Uplink

value=Spreading Factor 64 (Uplink)

value=Spreading Factor 128 (Downlink)

value=Primary Scrambling code=60

value=Spreading Factor 128 (Downlink)

Cell Identity=RNCid(12bits)+Cellid(16bits)
value=0000011001100000010100101001 => RNCid=bin2dec(000001100110)=102 and Cellid=bin2dec(0000010100101001)=1321

>>"RRC Connection Setup Complete Description"

value= not support GSM (Locked UMTS Mode)

value= Chipering Algorithm A5/3

value= support Compressed Mode (CM) uplink and downlink
value= support HSDPA, UE Category 8
uest)
>>"Radio Bearer Description"
value= Uplink e-DPDCH (HSUPA) channel information
value= Downlink HS-PDSCH channel information
value= HSDPA and HSUPA Serving Cell's Primary SC = 68
ccept)
value= PrimarySC=68, no longer a HSDPA & HSUPA serving cell ( HSPA Serving Cell Change)
 value= PrimarySC=60 is a new HSDPA&HSUPA serving cell ( HSPA Serving Cell Change)

H)
quest)
Accept)
ase)
mplete)
 Default Constant DPCCH_Power_offset CPICH_RSCP PCPICH Power
-22 -94 -80 33
-22 -94 -70 33
Note :DPCCH_Power_offset is configured by RNC and delivered to UE in RRC Connection Setup.
=102 and Cellid=bin2dec(0000010100101001)=1321
PA serving cell ( HSPA Serving Cell Change)
rving cell ( HSPA Serving Cell Change)
UL Interference UL DPCCH Initial Power
-105 -14
-105 -24
Click to return to main page

L3 Messages - Intra-Frequency Soft Handove

UE

Intra-Frequency Soft Handover within NodeB(So

RRC:Measurement Control

RRC:Measurement Report (e1a)

"or"
RRC:Measurement Report (e1c)

1.RRC: Active Set Update (DCCH)

2. RRC: Active Set Update Complete (DCCH)

RRC:Measurement Control

RRC:Measurement Report (e1b)

1.RRC: Active Set Update (DCCH)

2. RRC: Active Set Update Complete (DCCH)

 L3 Messages - Intra-Frequency Soft Handove
UE NodeB1

Intra-Frequency Soft Handover between NodeBs

RRC:Measurement Control

RRC:Measurement Report (e1a)

"or"
RRC:Measurement Report (e1c)

1.RRC: Active Set Update (DCCH)

2. RRC: Active Set Update Complete (DCCH)

RRC:Measurement Control

RRC:Measurement Report (e1b)

1.RRC: Active Set Update (DCCH)

2. RRC: Active Set Update Complete (DCCH)

Note: the following information about the procedure ,

1. During the handover, NodeB 1 is the source NodeB and NodeB 2 is the target NodeB.

2.If IP transport is applied to the Iub interface, no ALCAP procedure is performed on the Iubinterface after radio links a
up or deleted.

L3 Messages - Intra-Fre
UE NodeB2

Intra-Frequency S

RRC:M

RRC:Me
"or"
RRC:Me
ALCAP: Iub User Plane Setup

1.RRC: A

2.RRC: Active S

RRC:M

RRC:Me

1.RRC: A

2. RRC: Active
 ALCAP: Iub User Plane Release

Note :the following information about the procedure ,

1.During the handover, NodeB 1 is the source NodeB and NodeB 2 is the target NodeB.
2. If IP transport is applied to the Iub interface, no ALCAP procedure is performed on the Iub interface after radio links ar
set up or deleted.
3.If IP transport is applied to the Iur interface, no ALCAP procedure is performed on the Iurinterface after radio links are
up or deleted.
essages - Intra-Frequency Soft Handover Procedure
NodeB1

ntra-Frequency Soft Handover within NodeB(Softer-HO)

RRC:Measurement Control

RRC:Measurement Report (e1a)

RRC:Measurement Report (e1c)

1.NBAP:Radio Link Setup Req

2.NBAP:Radio Link Setup Resp

1.RRC: Active Set Update (DCCH)

2. RRC: Active Set Update Complete (DCCH)

RRC:Measurement Control

RRC:Measurement Report (e1b)

1.RRC: Active Set Update (DCCH)

2. RRC: Active Set Update Complete (DCCH)

1.NBAP:Radio Link Deletion Req

2.NBAP:Radio Link Deletion Resp

essages - Intra-Frequency Soft Handover Procedure
*Source NodeB2 *Target

tra-Frequency Soft Handover between NodeBs in a RNC

RRC:Measurement Control

RRC:Measurement Report (e1a)

RRC:Measurement Report (e1c)

1.NBAP:Radio Link Setup Req

2.NBAP:Radio Link Setup Resp

ALCAP: Iub User Plane Setup

QAAL2 Establish Request

QAAL2 Establish Confirm

NBAP:Radio Link Restore Indication

1.RRC: Active Set Update (DCCH)

2. RRC: Active Set Update Complete (DCCH)

RRC:Measurement Control

RRC:Measurement Report (e1b)

1.RRC: Active Set Update (DCCH)

2. RRC: Active Set Update Complete (DCCH)

 1.NBAP:Radio Link Deletion Req

2.NBAP:Radio Link Deletion Resp

ALCAP: Iub User Plane Release

QAAL2 Release Request

QAAL2 Release Confirm

d NodeB 2 is the target NodeB.

procedure is performed on the Iubinterface after radio links are set

L3 Messages - Intra-Frequency Soft Handover Procedure

*Target D-RNC *Target

Intra-Frequency Soft Handover between RNCs

RRC:Measurement Control

RRC:Measurement Report (e1a)

RRC:Measurement Report (e1c)

 1.RNSAP:Radio Link Setup

2.NBAP:Radio Link Setup Request

3.NBAP:Radio Link Setup Response

ALCAP: Iub User Plane Setup

1.QAAL2 Establish Request

2.QAAL2 Establish Confirm

1.NBAP:Radio Link Restore Indication

4.RNSAP:Radio Link Setup

ALCAP: Iur User Plane

1.QAAL2 Establish Re

2.QAAL2 Establish Co

2.RNSAP:Radio Link Restor

1.RRC: Active Set Update (DCCH)

2.RRC: Active Set Update Complete (DCCH)

RRC:Measurement Control

RRC:Measurement Report (e1b)

1.RRC: Active Set Update (DCCH)

2. RRC: Active Set Update Complete (DCCH)

1.RNSAP:Radio Link Dele

NBAP:Radio Link Deletion Req

NBAP:Radio Link Deletion Resp

 ALCAP: Iub User Plane Release

QAAL2 Release Request

QAAL2 Release Confirm

2.NBAP:Radio Link Deleti

ALCAP: Iur User Plane R

QAAL2 Release Req

QAAL2 Release Con

odeB 2 is the target NodeB.

ocedure is performed on the Iub interface after radio links are

cedure is performed on the Iurinterface after radio links are set

 >>Intra-Frequency SHO Algorithm and related parameters (Module
II)

S-RNC
Measurement Control: is used to notify the UE o
conditions.

Measurement Report: the UE continue measure

Measurement report is also can be sent in period
Measurement Control
& Measurement Report

Decision to
setup new Radio Link Addition Procedure is performed to
radio link
Triggering Conditions: The CRNC sends a RAD
Radio Link Addition The procedure of radio link setup is described
1.The CRNC sends a RADIO LINK ADDITION RE
the parameters given in the message.
2.The NodeB sends a response message to the C
-If all the requested radio links are added, the
Active Set Update RESPONSE message.
-If any radio link fails to be added, the NodeB s

Measurement Control The active set update procedure is perform

& Measurement Report
Triggering Conditions: The active set update pr
The procedure is described as follows:
1.The SRNC sends an ACTIVE SET UPDATE me
Decision to deletion.
delete old radio 2.The UE adds or deletes the radio links accordin
link
3.The UE sends a response message to the SRN
-lf adding or deleting the radio links successfu
-If the ACTIVE SET UPDATE message contains
Active Set Update
sends an ACTIVE SET UPDATE FAILURE messa

Radio Link Deletion

Radio Link Deletion Procedure is performed

Triggering Conditions: The CRNC sends a RAD

The procedure of radio link deletion is describ
1.The CRNC sends a RADIO LINK SETUP REQU
2.The NodeB sends a response message to the C
-If the radio link are deleted, the NodeB sends
-If the radio link fails to be deleted, the NodeB
 1.The CRNC sends a RADIO LINK SETUP REQU
2.The NodeB sends a response message to the C
-If the radio link are deleted, the NodeB sends
-If the radio link fails to be deleted, the NodeB

Click to return to main page

Measurement Control: is used to notify the UE o
S-RNC conditions.

Measurement Report: the UE continue measure

Measurement report is also can be sent in period

Measurement Control
& Measurement Report

Decision to
setup new The radio link setup procedure (intra-RNC han
radio link
Triggering Conditions: The CRNC sends a RAD
The procedure of radio link setup is described
Radio Link Setup 1.The CRNC sends a RADIO LINK SETUP REQU
parameters given in the message.
2.The NodeB sends a response message to the C
-If the radio link is set up, the NodeB saves the
up -If the radio link fails to be set up, the NodeB s

Iub user plane Setup

The Iub user plane setup procedure is perform

Triggering Conditions: The Iub user plane setup

Iub radio link restore Indication
Active Set Update
1. The common transport channels are setup
2. The dedicated transport channels are setup
The procedure is described as follows:
1.The CRNC uses the ALCAP protocol to send a
2.The NodeB uses the ALCAP protocol to send a
-If the Iub data transport bearers are set up, th
-If an Iub data transport bearer fails to be set u

The radio link restoration procedure (intra-RN

Measurement Control or re-achieved
& Measurement Report
Triggering Conditions: The nodeB detect UL sig

Decision to After performing UL synchronization with the UE,

delete old radio
link

Active Set Update The active set update procedure is perform

Triggering Conditions: The active set update pr

The procedure is described as follows:
1.The SRNC sends an ACTIVE SET UPDATE me
deletion.
2.The UE adds or deletes the radio links accordin
3.The UE sends a response message to the SRN
 The active set update procedure is perform

Triggering Conditions: The active set update pr

The procedure is described as follows:
1.The SRNC sends an ACTIVE SET UPDATE me
Radio Link Deletion deletion.
2.The UE adds or deletes the radio links accordin
3.The UE sends a response message to the SRN
-lf adding or deleting the radio links successfu
-If the ACTIVE SET UPDATE message contains
ase sends an ACTIVE SET UPDATE FAILURE messa

Iub user plane release

Radio Link Deletion Procedure is performed

Triggering Conditions: The CRNC sends a RAD

The procedure of radio link deletion is describ
1.The CRNC sends a RADIO LINK SETUP REQU
2.The NodeB sends a response message to the C
-If the radio link are deleted, the NodeB sends
-If the radio link fails to be deleted, the NodeB

The Iub user plane release procedure is pe

Triggering Conditions: The transport channels o

The procedure is described as follows:
1.The CRNC uses the ALCAP protocol to send a
2.The NodeB uses the ALCAP protocol to send a
-If the Iub data transport bearers are released,
-lf an Iub data transport bearer fails to be relea

Click to return to main page

NodeB1 *Source S-RNC

Measurement Control
& Measurement Report

Decision to
setup new
radio link
 Decision to
setup new
radio link

1.RNSAP:Radio Link Setup Request

Radio Link Setup

Iub user plane Setup

4.RNSAP:Radio Link Setup Response Iub Radio Link Restore Indication

ALCAP: Iur User Plane Setup

1.QAAL2 Establish Request Iur user plane Setup

2.QAAL2 Establish Confirm

2.RNSAP:Radio Link Restore Indication Iur Radio Link Restore Indication

Active Set Update

Measurement Control
& Measurement Report

Decision to
delete old
radio link

Active Set Update

1.RNSAP:Radio Link Deletion Req

 Radio Link Deletion

Iub user plane

release

2.NBAP:Radio Link Deletion Resp

ALCAP: Iur User Plane Release

QAAL2 Release Request Iur user plane release

QAAL2 Release Confirm

Control: is used to notify the UE of the objects to be measured, neighbor cell list, report method, and event parameters.When measuremen

Report: the UE continue measure the radio link condition of serving and neighbour cell and when the measurement reporting criterias are m
port is also can be sent in periodic mode.

ition Procedure is performed to add one or more radio links towards a UE.

ditions: The CRNC sends a RADIO LINK ADDITION REQUEST message.

of radio link setup is described as follows:

nds a RADIO LINK ADDITION REQUEST message to the NodeB. After receiving the message, the NodeB reserves the necessary resource
given in the message.
nds a response message to the CRNC.
sted radio links are added, the NodeB saves the value of the Configuration Generation ID IE contained in the RADIO LINK ADDITION RE
ssage.
k fails to be added, the NodeB sends a RADIO LINK ADDITION FAILURE message. The message contains the failure cause in the Cause

update procedure is performed to update the active set of radio links between theUE and the UTRAN.

ditions: The active set update procedure can be triggered in either of the following conditions: Radio link addition or Radio link deletion
is described as follows:
nds an ACTIVE SET UPDATE message to the UE. If a radio link needs to be added, the message indicates radio link addition. If a radio link

or deletes the radio links according to the Radio Link Addition Informationor Radio Link Removal Information IE contained in the ACTIVE SE
a response message to the SRNC.
leting the radio links successfully, the UE sends an ACTIVE SETUPDATE COMPLETE message on the DCCH by using Acknowledged
SET UPDATE message contains the configuration not supported by the UE or if the active set does not contain the radio links spec
E SET UPDATE FAILURE message.

letion Procedure is performed to release resources in a NodeB for one or more established radio links towards a UE

ditions: The CRNC sends a RADIO LINK DELETION REQUEST message.

of radio link deletion is described as follows:
nds a RADIO LINK SETUP REQUEST message to the NodeB. After receiving the message, the NodeB deletes the radio links specified by
nds a response message to the CRNC.
k are deleted, the NodeB sends a RADIO LINK DELETION RESPONSE message.
k fails to be deleted, the NodeB sends a RADIO LINK DELETION RESPONSE message. The message contains the failure cause.
Control: is used to notify the UE of the objects to be measured, neighbor cell list, report method, and event parameters.When measuremen

Report: the UE continue measure the radio link condition of serving and neighbour cell and when the measurement reporting criterias are m
port is also can be sent in periodic mode.

etup procedure (intra-RNC handover or GSM to WCDMA CS handover) is performed to set up a radio link in an SRNC-controlled Node

ditions: The CRNC sends a RADIO LINK SETUP REQUEST message.

of radio link setup is described as follows:
nds a RADIO LINK SETUP REQUEST message to the NodeB. After receiving the message, the NodeB reserves the necessary resources a
n in the message.
nds a response message to the CRNC.
k is set up, the NodeB saves the value of the Configuration Generation ID IE contained in the RADIO LINK SETUP REQUEST message an
k fails to be set up, the NodeB sends a RADIO LINK SETUP FAILURE message. The message contains the failure cause.

ane setup procedure is performed to set up bearers for data transmission on the Iub interface

ditions: The Iub user plane setup procedure can be triggered in one of the following conditions:
transport channels are setup
d transport channels are setup
is described as follows:
es the ALCAP protocol to send a QAAL2 ESTABLISH REQUEST messageto the NodeB.
es the ALCAP protocol to send a response message to the CRNC.
transport bearers are set up, the NodeB sends a QAAL2 ESTABLISH CONFIRM message.
ransport bearer fails to be set up, the NodeB sends a QAAL2 ESTABLISH RELEASE CONFIRM message.

estoration procedure (intra-RNC handover or GSM to WCDMA CS handover) is performed for a NodeB to notify the CRNC that the up

ditions: The nodeB detect UL signals from the UE. That is ,the NodeB finishs UL synchronization with the UE

UL synchronization with the UE, the NodeB sends a RADIO LINK RESTORE INDICATION message to the CRNC.

update procedure is performed to update the active set of radio links between theUE and the UTRAN.

ditions: The active set update procedure can be triggered in either of the following conditions: Radio link addition or Radio link deletion
is described as follows:
nds an ACTIVE SET UPDATE message to the UE. If a radio link needs to be added, the message indicates radio link addition. If a radio link

or deletes the radio links according to the Radio Link Addition Informationor Radio Link Removal Information IE contained in the ACTIVE SE
a response message to the SRNC.
 letion Procedure is performed to release resources in a NodeB for one or more established radio links towards a UE

ditions: The CRNC sends a RADIO LINK DELETION REQUEST message.

of radio link deletion is described as follows:
nds a RADIO LINK SETUP REQUEST message to the NodeB. After receiving the message, the NodeB deletes the radio links specified by
nds a response message to the CRNC.
k are deleted, the NodeB sends a RADIO LINK DELETION RESPONSE message.
k fails to be deleted, the NodeB sends a RADIO LINK DELETION RESPONSE message. The message contains the failure cause.

plane release procedure is performed to release data transport bearers from the Iub interface.

ditions: The transport channels on the Iub user plane need to be removed
is described as follows:
es the ALCAP protocol to send a QAAL2 RELEASE REQUEST messageto the NodeB.
es the ALCAP protocol to send a response message to the CRNC.
transport bearers are released, the NodeB sends a QAAL2 RELEASE CONFIRM message to confirm the release.
ransport bearer fails to be released, the NodeB sends a QAAL2 RELEASECONFIRM message that indicates the failure cause

Measurement Control: is used to notify the UE of the objects to be measured, neighbor cell list
conditions.

Measurement Report: the UE continue measure the radio link condition of serving and neighbo
Measurement report is also can be sent in periodic mode.
ent Control
ment Report

The radio link setup procedure for inter-RNC handover is performed to set up a radio link in a

Triggering Conditions: The SRNC sends a RADIO LINK SETUP REQUEST message
The procedure is described as follows:
1.The SRNC sends a RADIO LINK SETUP REQUEST message to the DRNC.
 The radio link setup procedure for inter-RNC handover is performed to set up a radio link in a

Triggering Conditions: The SRNC sends a RADIO LINK SETUP REQUEST message
The procedure is described as follows:
1.The SRNC sends a RADIO LINK SETUP REQUEST message to the DRNC.
2.The DRNC sends a RADIO LINK SETUP REQUEST message to the target NodeB.
3.The NodeB reserves the necessary resources and configures the new radio link accordingto th
4.The NodeB reports the radio link setup result to the DRNC
-If the radio link is set up, the NodeB saves the value of the Configuration GenerationID IE con
-If the radio link fails to be set up, the NodeB sends a RADIO LINK SETUP FAILURE messag
5.The DRNC reports the radio link setup result to the SRNC
-If the radio link is set up, the DRNC sends a RADIO LINK SETUP RESPONSEmessage.
-If the radio link fails to be set up, the DRNC sends a RADIO LINK SETUP FAILUREmessage

nk Restore Indication The Iub user plane setup procedure is performed to set up bearers for data transmission on th

Triggering Conditions: The Iub user plane setup procedure can be triggered in one of the
1. The common transport channels are setup
2. The dedicated transport channels are setup

The procedure is described as follows:

1.The CRNC uses the ALCAP protocol to send a QAAL2 ESTABLISH REQUEST messageto the
2.The NodeB uses the ALCAP protocol to send a response message to the CRNC.
-If the Iub data transport bearers are set up, the NodeB sends a QAAL2 ESTABLISH CONFIR
-If an Iub data transport bearer fails to be set up, the NodeB sends a QAAL2 ESTABLISH RE

Restore Indication

The radio link restoration procedure for inter-RNC handover is performed for a NodeB to no

Triggering Conditons: The NodeB detects UL signals from the UE. That is, the NodeB finishes

The procedure is described as follows:

1.After performing UL synchronization with the UE, the NodeB sends a RADIO LINKRESTORE I
ent Control 2.The DRNC sends a RADIO LINK RESTORE INDICATION message to the SRNC.
ment Report

The Iur user plane setup procedure is performed to set up bearers for data transmission on th

Triggering Conditons: The DCHs are set up

The procedure is described as follows:

1.The SRNC uses the ALCAP protocol to send a QAAL2 ESTABLISH REQUEST messageto the
2.The DRNC uses the ALCAP protocol to send a response message to the SRNC.
-If the Iur data transport bearers are set up, the DRNC sends a QAAL2 ESTABLISHCONFIRM
-If an Iur data transport bearer fails to be set up, the DRNC sends a QAAL2 ESTABLISHREL
 The active set update procedure is performed to update the active set of radio links between th
nk Deletion
Triggering Conditions: The active set update procedure can be triggered in either of the followi

The procedure is described as follows:

1.The SRNC sends an ACTIVE SET UPDATE message to the UE. If a radio link needs to be add
2.The UE adds or deletes the radio links according to the Radio Link Addition Informationor Radi
3.The UE sends a response message to the SRNC.
-lf adding or deleting the radio links successfully, the UE sends an ACTIVE SETUPDATE CO
-If the ACTIVE SET UPDATE message contains the configuration not supported by the UE
sends an ACTIVE SET UPDATE FAILURE message.

ne release

The radio link deletion procedure is performed to release resources in a NodeB for one or mo

Triggering Conditions: The CRNC sends a RADIO LINK DELETION REQUEST message.
The procedure is described as follows:
1.The CRNC sends a RADIO LINK DELETION REQUEST message to the NodeB. After receivin
2.The NodeB sends a response message to the CRNC.
-If all the radio links are deleted, the NodeB sends a RADIO LINK DELETION RESPONSE me
-If any radio link fails to be deleted, the NodeB sends a RADIO LINK DELETIONRESPONSE

The Iub user plane release procedure is performed to release data transport bearers from the

Triggering Conditions: The transport channels on the Iub user plane need to be removed.
The procedure is described as follows:
1.The CRNC uses the ALCAP protocol to send a QAAL2 RELEASE REQUEST messageto the N
2.The NodeB uses the ALCAP protocol to send a response message to the CRNC.
-If the Iub data transport bearers are released, the NodeB sends a QAAL2 RELEASECONFIR
-If an Iub data transport bearer fails to be released, the NodeB sends a QAAL2 RELEASECO

The Iur user plane release procedure is performed to releaseto release data transport bearers

Triggering Conditions: The transport channels on the Iub user plane need to be removed.
The procedure is described as follows:
1.The CRNC uses the ALCAP protocol to send a QAAL2 RELEASE REQUEST messageto the N
2.The NodeB uses the ALCAP protocol to send a response message to the CRNC.
-If the Iub data transport bearers are released, the NodeB sends a QAAL2 RELEASECONFIR
-If an Iub data transport bearer fails to be released, the NodeB sends a QAAL2 RELEASECO
parameters.When measurement conditions are changed, the RNC notifies the UE of new

rement reporting criterias are met, the UE reports the results to the RNC as an event. The

eserves the necessary resources and configures the new radio link or links according to

the RADIO LINK ADDITION REQUEST message andsends a RADIO LINK ADDITION

s the failure cause in the Cause IE.

dition or Radio link deletion

radio link addition. If a radio link needs to be deleted, themessage indicates radio link

IE contained in the ACTIVE SET UPDATE message.

DCCH by using Acknowledged Mode (AM)Radio Link Control (RLC).

ot contain the radio links specified by the Radio Link Removal Information IE , the UE

wards a UE

etes the radio links specified by the message

ntains the failure cause.

parameters.When measurement conditions are changed, the RNC notifies the UE of new

rement reporting criterias are met, the UE reports the results to the RNC as an event. The

nk in an SRNC-controlled NodeB for a UE

erves the necessary resources and configures the new radio link according to the

SETUP REQUEST message and sends a RADIOLINK SETUP RESPONSE message.

e failure cause.

e.

B to notify the CRNC that the uplink synchronization of one or more radio links is achieved

CRNC.

dition or Radio link deletion

radio link addition. If a radio link needs to be deleted, themessage indicates radio link

IE contained in the ACTIVE SET UPDATE message.

wards a UE

etes the radio links specified by the message

ntains the failure cause.

release.
ates the failure cause

be measured, neighbor cell list, report method, and event parameters.When measurement conditions are changed, the RNC notifies the U

ondition of serving and neighbour cell and when the measurement reporting criterias are met, the UE reports the results to the RNC as an e

formed to set up a radio link in a DRNC-controlled NodeB for a UE

P REQUEST message

to the DRNC.
arers for data transmission on the Iub interface

an be triggered in one of the following conditions:

LISH REQUEST messageto the NodeB.

age to the CRNC.
a QAAL2 ESTABLISH CONFIRM message.
ends a QAAL2 ESTABLISH RELEASE CONFIRM message.

is performed for a NodeB to notify the SRNC that the uplink synchronization of one or more radio links is achieved or re-achieved.

UE. That is, the NodeB finishes UL synchronizationwith the UE.

nds a RADIO LINKRESTORE INDICATION message to the DRNC.

sage to the SRNC.

rers for data transmission on the Iur interface

LISH REQUEST messageto the DRNC.

age to the SRNC.
a QAAL2 ESTABLISHCONFIRM message.
ends a QAAL2 ESTABLISHRELEASE CONFIRM message.
 tive set of radio links between the UE and the UTRAN.

triggered in either of the following conditions: Radio link addition or Radio link deletion

E. If a radio link needs to be added, the message indicates radio link addition. If a radio link needs to be deleted, themessage indicates radi
Link Addition Informationor Radio Link Removal Information IE contained in the ACTIVE SET UPDATE message.

ds an ACTIVE SETUPDATE COMPLETE message on the DCCH by using Acknowledged Mode (AM)Radio Link Control (RLC).
tion not supported by the UE or if the active set does not contain the radio links specified by the Radio Link Removal Information

urces in a NodeB for one or more established radio links towards a UE.

TION REQUEST message.

age to the NodeB. After receiving the message, the NodeB deletes the radio links specified by the message.

NK DELETION RESPONSE message

O LINK DELETIONRESPONSE message. The Criticality Diagnostics field in the message indicates the failure cause.

data transport bearers from the Iub interface.

plane need to be removed.

SE REQUEST messageto the NodeB.

age to the CRNC.
ds a QAAL2 RELEASECONFIRM message to confirm the release.
B sends a QAAL2 RELEASECONFIRM message that indicates the failure cause.

o release data transport bearers from the Iur interface.

plane need to be removed.

SE REQUEST messageto the NodeB.

age to the CRNC.
ds a QAAL2 RELEASECONFIRM message to confirm the release.
B sends a QAAL2 RELEASECONFIRM message that indicates the failure cause.
s
 the RNC notifies the UE of new

sults to the RNC as an event. The

or re-achieved.
emessage indicates radio link deletion.

ntrol (RLC).
Removal Information IE, the UE

.
Click to return to main page
RRC:Measurement Control
RRC:Measurement Report (e1a)
RRC:Measurement Report (e1b)
RRC:Measurement Report (e1c)
RRC: Active Set Update (DCCH)
RRC: Active Set Update Complete (DCCH)
RRC: Active Set Update (DCCH)
RRC: Active Set Update Complete (DCCH)
 >>"Measurement Control and Measurement Report"

value=intraFrequencyMeasurement

value=intraFrequencyCell List

value=IntraFreqCellID of Serving Cell=0

value=Primary Scrambling Code of Serving Cell=74

value=IntraFreqCellID of Serving 1st neighbourCell=1

value=CIO=0 (No offset on this neighbour cell)

value=Primary Scrambling Code of 1st Neighbour Cell=106

value=Intra-freq meas L3 filter coeff=3

value=Intra-freq Measure Quantity use CPICH Ec/No

>>Intra-Frequency SHO Algorithm and related parameters (Module II)

value=event1a triggered by detected and MonitorSet Cells ( DETSET_ADD_TO_ACTSET_SWITCH a

value=3 dB (IntraRelThdFor1A),step: 0.5

value=0
value=Maximum active set size =3 ( if number of cell in Active Set more than 2 then cannot trigger e
value=16
value=4000ms
value=0
value=320ms

value=UE report All Active Set Cells + 6 Monitor/Detected Set Cells

value=event1b triggered by Active Set Cells Only

value=6 dB (IntraRelThdFor1B) ,step: 0.5
value=0
value=0
value=640ms

value=UE report All 3 Active Set Cells

value=event1C triggered when Active Set is full (Maximum 3 cells in Active Set)
value=16

value=4000ms
value=4 dB (1C hysteresis),step: 0.5
value=640ms

value=UE report All Active Set Cells + 6 Monitor/Detected Set Cells

value=4dB (1D hysteresis),step: 0.5

value=640ms

value=UE report All Active Set Cells +3 Monitor Set Cells

value=event1f triggered by Active Set Cells Only

value= 1F event absolute EcNo threshold = -24 dB

value= 4 dB,step: 0.5
value=640ms

value=UE report All 3 Active Set Cells

 >>"Measurement Report"

value=CPICH Ec/No= -24+(25/2) = -11.5 dB

value=CPICH RSCP= -115+32= -83 dBm
value=Event1a is triggered
value=To add neighbour Primary Scrambling Code=13 into Active Set
value=CPICH Ec/No= -24+(31/2) = -8.5 dB
value=CPICH RSCP= -115+34= -81 dBm

value=CPICH Ec/No= -24+(7/2) = -20.5 dB

value=CPICH RSCP= -115+22= -93 dBm

value=Event1b is triggered

value=To delete neighbour Primary Scrambling Code=74 from Active Set

value=CPICH Ec/No= -24+(23/2) = -12.5 dB
value=CPICH RSCP= -115+30= -85 dBm

value=CPICH Ec/No= -24+(20/2) = -14 dB

value=CPICH RSCP= -115+29= -86 dBm
value=CPICH Ec/No= -24+(8/2) = -20 dB
value=CPICH RSCP= -115+23= -92 dBm

value=Event1c is triggered

value=To replace Cell Primary Scrambling Code=56 by Cell Primary Scrambling Code=106
H)
H)
 II)

ET_ADD_TO_ACTSET_SWITCH and DETSET_RPRT_SWITCH is "Active")

more than 2 then cannot trigger e1a)

y Scrambling Code=106
 Click to return to main page

L3 Messages - Intra-Frequency Hard Hand

UE NodeB1

Intra-Frequency Hard Handover between Nod

RRC:Measurement Control

RRC:Measurement Report (e1d)

1.RRC: Physical Channel Reconfiguration (D

2. RRC:Physical Channel Reconfiguration Comple

Stop Rx/Tx

ALC
Note: the following information about the procedure ,

1. During the handover, NodeB 1 is the source NodeB and NodeB 2 is the target NodeB.

2.If IP transport is applied to the Iub interface, no ALCAP procedure is performed on the Iub interface after radio li
up or deleted.

L3 Messages - Intra-F
UE NodeB2

Intra-Frequenc

RRC

Start Rx

ALCAP: Iub User Plane Setup

Start Tx

1. RRC:Physi

2. RRC:Physical C
Note :the following information about the procedure ,

1.During the handover, NodeB 1 is the source NodeB and NodeB 2 is the target NodeB.
2. If IP transport is applied to the Iub interface, no ALCAP procedure is performed on the Iub interface after radio link
up or deleted.
3.If IP transport is applied to the Iur interface, no ALCAP procedure is performed on the Iurinterface after radio links
or deleted.
essages - Intra-Frequency Hard Handover Procedure
*Source NodeB2

ntra-Frequency Hard Handover between NodeBs in a RNC

RRC:Measurement Control

RRC:Measurement Report (e1d)

Start Rx

ALCAP: Iub User Plane Setup

Start Tx

1.RRC: Physical Channel Reconfiguration (DCCH)

2. RRC:Physical Channel Reconfiguration Complete (DCCH)

1.NBAP:Radio Link Deletion Req

2.NBAP:Radio Link Deletion Resp

ALCAP: Iub User Plane Release

 1.QAAL2 Release Request

2.QAAL2 Release Confirm

d NodeB 2 is the target NodeB.

procedure is performed on the Iub interface after radio links are set

L3 Messages - Intra-Frequency Hard Handover Procedure

*Target D-RNC

Intra-Frequency Hard Handover between RNCs

RRC:Measurement Control

RRC:Measurement Report (e1d)

2.NBAP:Radio Link Setup Request

3.NBAP:Radio Link Setup Response

ALCAP: Iub User Plane Setup

1.QAAL2 Establish Request

2.QAAL2 Establish Confirm

1.NBAP:Radio Link Restore Indication

ALCAP: Iur User P

1. RRC:Physical Channel Reconfiguration (DCCH)

2. RRC:Physical Channel Reconfiguration Complete (DCCH)

ALCAP: Iur User Pl

odeB 2 is the target NodeB.
ocedure is performed on the Iub interface after radio links are set

cedure is performed on the Iurinterface after radio links are set up

 >>Intra-Frequency HHO Algorithm and related p
Procedure
*Target S-RNC

n a RNC

Decision to
setup new
radio link

1.NBAP:Radio Link Setup Req

2.NBAP:Radio Link Setup Resp

ALCAP: Iub User Plane Setup

1.QAAL2 Establish Request

2.QAAL2 Establish Confirm

NBAP:Radio Link Restore Indication

H)

Decision to
delete old radio
link

io Link Deletion Req

dio Link Deletion Resp

User Plane Release

Release Request

Release Confirm

ency Hard Handover Procedure

*Target NodeB1

d Handover between RNCs

surement Control

rement Report (e1d)

1.RNSAP:Radio Link Setup Request

 2.RNSAP:Radio Link Setup Response

ALCAP: Iur User Plane Setup

1.QAAL2 Establish Request

2.QAAL2 Establish Confirm

2.RNSAP:Radio Link Restore Indication

nnel Reconfiguration (DCCH)

Reconfiguration Complete (DCCH)

Stop Rx/Tx

ALCAP: Iub User Plane Release

ALCAP: Iur User Plane Release

1.QAAL2 Release Request

2.QAAL2 Release Confirm

>>Intra-Frequency HHO Algorithm and related parameters

Measurement Control is used to notify the U

notifies the UE of new conditions.

Measurement Report, the UE continue meas

RNC as an event. The Measurement report is
Measurement Control
& Measurement Report

The radio link setup procedure (intra-RNC h

The procedure of radio link setup is descri

1.The CRNC sends a RADIO LINK SETUP R

according to the parameters given in the mes
Radio Link Setup 2.The NodeB sends a response message to t
REQUEST message and sends a RADIOLINK
contains the failure cause.

Iub user plane Setup

The Iub user plane setup procedure is perfo

The procedure is described as follows:

1.The CRNC uses the ALCAP protocol to sen
Iub radio link restore Indication 2.The NodeB uses the ALCAP protocol to sen
an Iub data transport bearer fails to be set up

Physical Reconfiguration

The radio link restoration procedure (intra-R

links is achieved or re-achieved

After performing UL synchronization with the U

The physical channel reconfiguration proce

The procedure is described as follows:
Radio Link Deletion 1.The SRNC sends a PHYSICAL CHANNEL
2.The UE saves the IEs of the UE, Radio Bea
->If successfully reconfiguring the physical ch
COMPLETE message on the uplink DCCH by
->If failing to reconfigure the physical channel
and sends a PHYSICAL CHANNEL RECONF
RECONFIGURATION FAILURE message is "
Iub user plane release
 ->If successfully reconfiguring the physical ch
COMPLETE message on the uplink DCCH by
->If failing to reconfigure the physical channel
and sends a PHYSICAL CHANNEL RECONF
RECONFIGURATION FAILURE message is "
Iub user plane release

The radio link deletion procedure is perform

The procedure is described as follows:
1.The CRNC sends a RADIO LINK DELETIO
2.The NodeB sends a response message to t
3. lf any radio link fails to be deleted, the Nod

The Iub user plane release procedure is per

The procedure is described as follows:
1.The CRNC uses the ALCAP protocol to sen
2.The NodeB uses the ALCAP protocol to sen
->If the Iub data transport bearers are release
->lf an Iub data transport bearer fails to be rel

Click to return to main page

*Source S-RNC *Source

>>Measurement Control&Report Descript

Measurement Control
& Measurement Report

Decision to
setup new radio
link

dio Link Setup Request

Radio Link Setup

Iub user plane Setup

 Iub Radio Link Restore Indication

o Link Setup Response

r User Plane Setup

Establish Request Iur user plane Setup

Establish Confirm

Iur Radio Link Restore Indication

o Link Restore Indication

Physical Reconfiguration

Decision to
delete old radio
link

1.NBAP:Radio Link Deletion Req

Radio Link Deletion

2.NBAP:Radio Link Deletion Resp

ALCAP: Iub User Plane Release

1.QAAL2 Release Request Iub user plane release

2.QAAL2 Release Confirm

User Plane Release

Release Request Iur user plane release

Release Confirm
ement Control is used to notify the UE of the objects to be measured, neighbor cell list, report method, and event parameters.When me
he UE of new conditions.

ement Report, the UE continue measure the radio link condition of serving and neighbour cell and when the measurement reporting crit
an event. The Measurement report is also can be sent in periodic mode.

o link setup procedure (intra-RNC handover or GSM to WCDMA CS handover) is performed to set up a radio link in an SRNC-control

cedure of radio link setup is described as follows:

RNC sends a RADIO LINK SETUP REQUEST message to the NodeB. After receiving the message, the NodeB reserves the necessary
g to the parameters given in the message.
odeB sends a response message to the CRNC.If the radio link is set up, the NodeB saves the value of the Configuration Generation ID
ST message and sends a RADIOLINK SETUP RESPONSE message.If the radio link fails to be set up, the NodeB sends a RADIO LINK
the failure cause.

user plane setup procedure is performed to set up bearers for data transmission on the Iub interface

cedure is described as follows:

RNC uses the ALCAP protocol to send a QAAL2 ESTABLISH REQUEST messageto the NodeB.
odeB uses the ALCAP protocol to send a response message to the CRNC.lIf the Iub data transport bearers are set up, the NodeB sends
ata transport bearer fails to be set up, the NodeB sends a QAAL2 ESTABLISH RELEASE CONFIRM message.

o link restoration procedure (intra-RNC handover or GSM to WCDMA CS handover)is performed for a NodeB to notify the CRNC that
chieved or re-achieved

forming UL synchronization with the UE, the NodeB sends a RADIO LINK RESTOREINDICATION message to the CRNC.

sical channel reconfiguration procedure is performed to set up, reconfigure, or releasea physical channel
cedure is described as follows:
RNC sends a PHYSICAL CHANNEL RECONFIGURATION message to the UE to request reconfiguration of a physical channel.
E saves the IEs of the UE, Radio Bearer (RB), transport channel, and physical channel.The UE sends a response message to the SRNC
essfully reconfiguring the physical channels specified by the PHYSICALCHANNEL RECONFIGURATION message, the UE sends a PH
ETE message on the uplink DCCH by using AM RLC
g to reconfigure the physical channels specified by the PHYSICAL CHANNELRECONFIGURATION message, the UE restores the confi
ds a PHYSICAL CHANNEL RECONFIGURATION FAILURE message on the DCCH by using AM RLC. The value of the Failure cause IE
FIGURATION FAILURE message is "physical channel failure".
o link deletion procedure is performed to release resources in a NodeB for one or more established radio links towards a UE.
cedure is described as follows:
RNC sends a RADIO LINK DELETION REQUEST message to the NodeB. After receiving the message, the NodeB deletes the radio lin
odeB sends a response message to the CRNC.lf all the radio links are deleted, the NodeB sends a RADIO LINK DELETION RESPONS
radio link fails to be deleted, the NodeB sends a RADIO LINK DELETION RESPONSE message. The Criticality Diagnostics field in the

user plane release procedure is performed to release data transport bearers from the Iubinterface.
cedure is described as follows:
RNC uses the ALCAP protocol to send a QAAL2 RELEASE REQUEST messageto the NodeB.
odeB uses the ALCAP protocol to send a response message to the CRNC.
ub data transport bearers are released, the NodeB sends a QAAL2 RELEASE CONFIRM message to confirm the release.
b data transport bearer fails to be released, the NodeB sends a QAAL2 RELEASECONFIRM message that indicates the failure cause

eturn to main page

Measurement Control is used to notify the UE of the objects to be measured, neigh

t Control&Report Description Measurement Report, the UE continue measure the radio link condition of serving a
report is also can be sent in periodic mode.
nt Control
ent Report

The radio link setup procedure for inter-RNC handover is performed to set up a radio
The procedure is described as follows:
1.The SRNC sends a RADIO LINK SETUP REQUEST message to the DRNC.
2.The DRNC sends a RADIO LINK SETUP REQUEST message to the target NodeB
3.The NodeB reserves the necessary resources and configures the new radio link ac
->If the radio link is set up, the NodeB saves the value of the Configuration Generati
->If the radio link fails to be set up, the NodeB sends a RADIO LINK SETUP FAILUR
4.The DRNC reports the radio link setup result to the SRNC.
->If the radio link is set up, the DRNC sends a RADIO LINK SETUP RESPONSEme
->If the radio link fails to be set up, the DRNC sends a RADIO LINK SETUP FAILUR
 The Iub user plane setup procedure is performed to set up bearers for data transm
Restore Indication The procedure is described as follows:

1.The CRNC uses the ALCAP protocol to send a QAAL2 ESTABLISH REQUEST me
2.The NodeB uses the ALCAP protocol to send a response message to the CRNC.
->If the Iub data transport bearers are set up, the NodeB sends a QAAL2 ESTABLIS
->If an Iub data transport bearer fails to be set up, the NodeB sends a QAAL2 ESTA

The radio link restoration procedure for inter-RNC handover is performed for a Nod

1.After performing UL synchronization with the UE, the NodeB sends a RADIO LINK
Restore Indication 2.The DRNC sends a RADIO LINK RESTORE INDICATION message to the SRNC.

The Iur user plane setup procedure is performed to set up bearers for data transmi
The procedure is described as follows:
onfiguration
1.The SRNC uses the ALCAP protocol to send a QAAL2 ESTABLISH REQUEST me
2.The DRNC uses the ALCAP protocol to send a response message to the SRNC.
->If the Iur data transport bearers are set up, the DRNC sends a QAAL2 ESTABLISH
->If an Iur data transport bearer fails to be set up, the DRNC sends a QAAL2 ESTAB

The physical channel reconfiguration procedure is performed to set up, reconfigu

The procedure is described as follows:

1.The SRNC sends a PHYSICAL CHANNEL RECONFIGURATION message to the
2.The UE saves the IEs of the UE, Radio Bearer (RB), transport channel, and physic
->If successfully reconfiguring the physical channels specified by the PHYSICALCHA
using AM RLC
->If failing to reconfigure the physical channels specified by the PHYSICAL CHANNE
RECONFIGURATION FAILURE message on the DCCH by using AM RLC. The valu

e release
The radio link deletion procedure is performed to release resources in a NodeB for

The procedure is described as follows:

1.The CRNC sends a RADIO LINK DELETION REQUEST message to the NodeB. A
2.The NodeB sends a response message to the CRNC.
->lf all the radio links are deleted, the NodeB sends a RADIO LINK DELETION RES
->lf any radio link fails to be deleted, the NodeB sends a RADIO LINK DELETION R

ne release

The Iub user plane release procedure is performed to release data transport beare

The procedure is described as follows:

1.The CRNC uses the ALCAP protocol to send a QAAL2 RELEASE REQUEST mes
2.The NodeB uses the ALCAP protocol to send a response message to the CRNC.
->If the Iub data transport bearers are released, the NodeB sends a QAAL2 RELEAS
->lf an Iub data transport bearer fails to be released, the NodeB sends a QAAL2 RE
The procedure is described as follows:
1.The CRNC uses the ALCAP protocol to send a QAAL2 RELEASE REQUEST mes
2.The NodeB uses the ALCAP protocol to send a response message to the CRNC.
->If the Iub data transport bearers are released, the NodeB sends a QAAL2 RELEAS
->lf an Iub data transport bearer fails to be released, the NodeB sends a QAAL2 RE

The Iur user plane release procedure is performed to release data transport bearer

The procedure is described as follows:

1.The SRNC uses the ALCAP protocol to send a QAAL2 RELEASE REQUEST mes
2.The DRNC uses the ALCAP protocol to send a response message to the SRNC.
->If the Iur data transport bearers are released, the DRNC sends a QAAL2 RELEAS
->If an Iur data transport bearer fails to be released, the DRNC sends a QAAL2 REL
nt parameters.When measurement conditions are changed, the RNC

asurement reporting criterias are met, the UE reports the results to the

link in an SRNC-controlled NodeB for a UE

reserves the necessary resources and configures the new radio link

guration Generation ID IE contained in the RADIO LINK SETUP

eB sends a RADIO LINK SETUP FAILURE message. The message

set up, the NodeB sends a QAAL2 ESTABLISH CONFIRM message.If

to notify the CRNC that the uplink synchronization of one or more radio

he CRNC.

hysical channel.
e message to the SRNC.
age, the UE sends a PHYSICAL CHANNELRECONFIGURATION

he UE restores the configuration to the old physicalchannel configuration

e of the Failure cause IE contained in the PHYSICAL CHANNEL
 towards a UE.

deB deletes the radio links specified by the message.

K DELETION RESPONSE message.
Diagnostics field in the message indicates the failure cause.

he release.
cates the failure cause

s to be measured, neighbor cell list, report method, and event parameters.When measurement conditions are changed, the RNC notifie

nk condition of serving and neighbour cell and when the measurement reporting criterias are met, the UE reports the results to the RNC

rformed to set up a radio link in a DRNC-controlled NodeB for a UE

age to the DRNC.

sage to the target NodeB.
res the new radio link according to the parameters given in the message.The NodeB reports the radio link setup result to the DRNC.
Configuration GenerationID IE contained in the RADIO LINK SETUP REQUEST message and sends a RADIOLINK SETUP RESPON
O LINK SETUP FAILUREmessage.

SETUP RESPONSEmessage.
O LINK SETUP FAILURE message, indicating the failure cause.
 bearers for data transmission on the Iub interface

TABLISH REQUEST messageto the NodeB.

message to the CRNC.
nds a QAAL2 ESTABLISH CONFIRM message.
B sends a QAAL2 ESTABLISH RELEASE CONFIRM message

er is performed for a NodeB to notify the SRNC that the uplink synchronization of one or more radio links is achieved or re-achieved.

B sends a RADIO LINKRESTORE INDICATION message to the DRNC.

message to the SRNC.

bearers for data transmission on the Iur interface

TABLISH REQUEST message to the DRNC.

message to the SRNC.
ds a QAAL2 ESTABLISHCONFIRM message.
sends a QAAL2 ESTABLISHRELEASE CONFIRM message.

med to set up, reconfigure, or releasea physical channel

ATION message to the UE to request reconfiguration of a physical channel.

port channel, and physical channel.The UE sends a response message to the SRNC.
d by the PHYSICALCHANNEL RECONFIGURATION message, the UE sends a PHYSICAL CHANNELRECONFIGURATION COMPLE

he PHYSICAL CHANNELRECONFIGURATION message, the UE restores the configuration to the old physicalchannel configuration an
using AM RLC. The value of the Failure cause IE contained in the PHYSICAL CHANNEL RECONFIGURATION FAILURE message is "p

esources in a NodeB for one or more established radio links towards a UE.

message to the NodeB. After receiving the message, the NodeB deletes the radio links specified by the message.

O LINK DELETION RESPONSE message.

DIO LINK DELETION RESPONSE message. The Criticality Diagnostics field in the message indicates the failure cause.

se data transport bearers from the Iubinterface.

LEASE REQUEST messageto the NodeB.

message to the CRNC.
sends a QAAL2 RELEASE CONFIRM message to confirm the release.
deB sends a QAAL2 RELEASECONFIRM message that indicates the failure cause
se data transport bearers from the Iur interface

LEASE REQUEST messageto the DRNC.

message to the SRNC.
ends a QAAL2 RELEASECONFIRM message to confirm the release.
NC sends a QAAL2 RELEASECONFIRM message that indicates the failure cause.
s are changed, the RNC notifies the UE of new conditions.

reports the results to the RNC as an event. The Measurement

k setup result to the DRNC.

RADIOLINK SETUP RESPONSE message.
is achieved or re-achieved.

ECONFIGURATION COMPLETE message on the uplink DCCH by

ysicalchannel configuration and sends a PHYSICAL CHANNEL

TION FAILURE message is "physical channel failure".

essage.

e failure cause.
 Click to return to main page

L3 Messages - Inter-Frequency Hard Hand

UE NodeB1

Inter-Frequency Hard Handover between Nod

RRC:Measurement Control

RRC:Measurement Report (e2d)

RRC:Physical Channel Reconfiguration (DC

RRC:Physical Channel Reconfiguration Complete

RRC:Measurement Control

RRC:Measurement Report

RRC:Measurement Report
 1.RRC: Physical Channel Reconfiguration (DC

2. RRC:Physical Channel Reconfiguration Complet

Stop Rx/Tx

ALC

Note: the following information about the procedure ,

1.The radio link setup procedure shown in the figure applies when the source and target cellsof the handover are c
different NodeBs. If the source and target cells arecontrolled by the same NodeB, the radio link setup procedure s
replaced by theradio link addition procedure, and the radio link restoration procedure is excluded.
2.During the handover, NodeB 1 is the source NodeB and NodeB 2 is the target NodeB.
3.If IP transport is applied to the Iub interface, no ALCAP procedure is performed on the Iub interface after radio lin
up or deleted.

L3 Messages - Inter-F
UE NodeB2

Inter-Frequenc
Start Rx

ALCAP: Iub User Plane Setup

Start Tx

1. RRC:Physi

2. RRC:Physical C
Note :the following information about the procedure ,

1.During the handover, NodeB 1 is the source NodeB and NodeB 2 is the target NodeB.
2. If IP transport is applied to the Iub interface, no ALCAP procedure is performed on the Iub interface after radio link
up or deleted.
3.If IP transport is applied to the Iur interface, no ALCAP procedure is performed on the Iurinterface after radio links
or deleted.
essages - Inter-Frequency Hard Handover Procedure
*Source NodeB2

nter-Frequency Hard Handover between NodeBs in a RNC

RRC:Measurement Control

RRC:Measurement Report (e2d)

NBAP: Radio Link Reconfiguration Prepare

NBAP: Radio Link Reconfiguration Ready

NBAP: Radio Link Reconfiguration Commit

RRC:Physical Channel Reconfiguration (DCCH)

RRC:Physical Channel Reconfiguration Complete (DCCH)

NBAP: Compressed Mode Command

RRC:Measurement Control

RRC:Measurement Report

RRC:Measurement Report

Start Rx

ALCAP: Iub User Plane Setup

Start Tx
 1.RRC: Physical Channel Reconfiguration (DCCH)

2. RRC:Physical Channel Reconfiguration Complete (DCCH)

1.NBAP:Radio Link Deletion Req

2.NBAP:Radio Link Deletion Resp

ALCAP: Iub User Plane Release

1.QAAL2 Release Request

2.QAAL2 Release Confirm

es when the source and target cellsof the handover are controlled by
ed by the same NodeB, the radio link setup procedure should be
o link restoration procedure is excluded.
NodeB 2 is the target NodeB.
procedure is performed on the Iub interface after radio links are set

L3 Messages - Inter-Frequency Hard Handover Procedure

*Target D-RNC

Inter-Frequency Hard Handover between RNCs

 2.NBAP:Radio Link Setup Request

3.NBAP:Radio Link Setup Response

ALCAP: Iub User Plane Setup

1.QAAL2 Establish Request

2.QAAL2 Establish Confirm

1.NBAP:Radio Link Restore Indication

ALCAP: Iur User P

1. RRC:Physical Channel Reconfiguration (DCCH)

2. RRC:Physical Channel Reconfiguration Complete (DCCH)

 ALCAP: Iur User Pl

odeB 2 is the target NodeB.

ocedure is performed on the Iub interface after radio links are set

cedure is performed on the Iurinterface after radio links are set up

 >>Intrer-Frequency HHO Algorithm and related
Procedure
*Target S-RNC

n a RNC

k Reconfiguration Prepare

k Reconfiguration Ready

k Reconfiguration Commit

essed Mode Command

Decision to
setup new
radio link

1.NBAP:Radio Link Setup Req

2.NBAP:Radio Link Setup Resp

ALCAP: Iub User Plane Setup

1.QAAL2 Establish Request

2.QAAL2 Establish Confirm

NBAP:Radio Link Restore Indication

H)

Decision to
delete old radio
link

io Link Deletion Req

dio Link Deletion Resp

User Plane Release

Release Request

Release Confirm

ency Hard Handover Procedure

*Target NodeB1

d Handover between RNCs

 1.RNSAP:Radio Link Setup Request

2.RNSAP:Radio Link Setup Response

ALCAP: Iur User Plane Setup

1.QAAL2 Establish Request

2.QAAL2 Establish Confirm

2.RNSAP:Radio Link Restore Indication

nnel Reconfiguration (DCCH)

Reconfiguration Complete (DCCH)

Stop Rx/Tx

ALCAP: Iub User Plane Release

ALCAP: Iur User Plane Release

1.QAAL2 Release Request

2.QAAL2 Release Confirm

>>Intrer-Frequency HHO Algorithm and related parameters

Measurement Control is used to notify th

the UE of new conditions.

Measurement Report, the UE continue m

an event. The Measurement report is also
Measurement Control
& Measurement Report

Compressed Mode was introduced to WC

measurements on another frequency can

>>Compressed Mode Description Module II

Initial Compressed Mode Configuration

The radio link setup procedure (intra-RN

The procedure of radio link setup is des

1.The CRNC sends a RADIO LINK SETUP

to the parameters given in the message.
2.The NodeB sends a response message
message and sends a RADIOLINK SETUP
Inter-Freq Neighbour cells measurement cause.

The Iub user plane setup procedure is pe

The procedure is described as follows:

1.The CRNC uses the ALCAP protocol to
2.The NodeB uses the ALCAP protocol to
data transport bearer fails to be set up, the

Radio Link Setup

The radio link restoration procedure (intr

Iub user plane Setup achieved or re-achieved

After performing UL synchronization with t

Iub radio link restore Indication The physical channel reconfiguration p

The procedure is described as follows:
1.The SRNC sends a PHYSICAL CHANN
2.The UE saves the IEs of the UE, Radio B
->If successfully reconfiguring the physica
message on the uplink DCCH by using AM
->If failing to reconfigure the physical chan
sends a PHYSICAL CHANNEL RECONFI
RECONFIGURATION FAILURE message
 The physical channel reconfiguration p
The procedure is described as follows:
1.The SRNC sends a PHYSICAL CHANN
2.The UE saves the IEs of the UE, Radio B
->If successfully reconfiguring the physica
message on the uplink DCCH by using AM
->If failing to reconfigure the physical chan
Physical Reconfiguration sends a PHYSICAL CHANNEL RECONFI
RECONFIGURATION FAILURE message

The radio link deletion procedure is perfo

The procedure is described as follows:
1.The CRNC sends a RADIO LINK DELET
Radio Link Deletion
2.The NodeB sends a response message
3. lf any radio link fails to be deleted, the N

Iub user plane release

The Iub user plane release procedure is

The procedure is described as follows:
1.The CRNC uses the ALCAP protocol to
2.The NodeB uses the ALCAP protocol to
->If the Iub data transport bearers are rele
->lf an Iub data transport bearer fails to be

Click to return to main page

*Source S-RNC *Source

Decision to setup
new radio link
 Decision to setup
new radio link

dio Link Setup Request

Radio Link Setup

Iub user plane Setup

Iub Radio Link Restore Indication

io Link Setup Response

r User Plane Setup

Establish Request Iur user plane Setup

Establish Confirm

o Link Restore Indication Iur Radio Link Restore Indication

Physical Reconfiguration

Decision to
delete old radio
link

1.NBAP:Radio Link Deletion Req

Radio Link Deletion

2.NBAP:Radio Link Deletion Resp

ALCAP: Iub User Plane Release

1.QAAL2 Release Request Iub user plane release

 2.QAAL2 Release Confirm

User Plane Release

Release Request
Iur user plane release

2 Release Confirm
ement Control is used to notify the UE of the objects to be measured, neighbor cell list, report method, and event parameters.When me
f new conditions.

ement Report, the UE continue measure the radio link condition of serving and neighbour cell and when the measurement reporting crit
. The Measurement report is also can be sent in periodic mode.

ssed Mode was introduced to WCDMA to allow inter-frequency and Inter-RAT Handovers. It is used to create idle periods (gaps) in the
ments on another frequency can be made.

o link setup procedure (intra-RNC handover or GSM to WCDMA CS handover) is performed to set up a radio link in an SRNC-control

cedure of radio link setup is described as follows:

RNC sends a RADIO LINK SETUP REQUEST message to the NodeB. After receiving the message, the NodeB reserves the necessary
rameters given in the message.
odeB sends a response message to the CRNC.If the radio link is set up, the NodeB saves the value of the Configuration Generation ID
e and sends a RADIOLINK SETUP RESPONSE message.If the radio link fails to be set up, the NodeB sends a RADIO LINK SETUP FA

user plane setup procedure is performed to set up bearers for data transmission on the Iub interface

cedure is described as follows:

RNC uses the ALCAP protocol to send a QAAL2 ESTABLISH REQUEST messageto the NodeB.
odeB uses the ALCAP protocol to send a response message to the CRNC.lIf the Iub data transport bearers are set up, the NodeB sends
sport bearer fails to be set up, the NodeB sends a QAAL2 ESTABLISH RELEASE CONFIRM message.

o link restoration procedure (intra-RNC handover or GSM to WCDMA CS handover)is performed for a NodeB to notify the CRNC that
or re-achieved

forming UL synchronization with the UE, the NodeB sends a RADIO LINK RESTOREINDICATION message to the CRNC.

sical channel reconfiguration procedure is performed to set up, reconfigure, or releasea physical channel
cedure is described as follows:
RNC sends a PHYSICAL CHANNEL RECONFIGURATION message to the UE to request reconfiguration of a physical channel.
E saves the IEs of the UE, Radio Bearer (RB), transport channel, and physical channel.The UE sends a response message to the SRNC
essfully reconfiguring the physical channels specified by the PHYSICALCHANNEL RECONFIGURATION message, the UE sends a PH
e on the uplink DCCH by using AM RLC
g to reconfigure the physical channels specified by the PHYSICAL CHANNELRECONFIGURATION message, the UE restores the confi
PHYSICAL CHANNEL RECONFIGURATION FAILURE message on the DCCH by using AM RLC. The value of the Failure cause IE con
FIGURATION FAILURE message is "physical channel failure".
o link deletion procedure is performed to release resources in a NodeB for one or more established radio links towards a UE.
cedure is described as follows:
RNC sends a RADIO LINK DELETION REQUEST message to the NodeB. After receiving the message, the NodeB deletes the radio lin
odeB sends a response message to the CRNC.lf all the radio links are deleted, the NodeB sends a RADIO LINK DELETION RESPONS
radio link fails to be deleted, the NodeB sends a RADIO LINK DELETION RESPONSE message. The Criticality Diagnostics field in the

user plane release procedure is performed to release data transport bearers from the Iubinterface.
cedure is described as follows:
RNC uses the ALCAP protocol to send a QAAL2 RELEASE REQUEST messageto the NodeB.
odeB uses the ALCAP protocol to send a response message to the CRNC.
ub data transport bearers are released, the NodeB sends a QAAL2 RELEASE CONFIRM message to confirm the release.
b data transport bearer fails to be released, the NodeB sends a QAAL2 RELEASECONFIRM message that indicates the failure cause

urn to main page

The radio link setup procedure for inter-RNC handover is performed to set up
The procedure is described as follows:
1.The SRNC sends a RADIO LINK SETUP REQUEST message to the DRNC
2.The DRNC sends a RADIO LINK SETUP REQUEST message to the target
3.The NodeB reserves the necessary resources and configures the new radio
->If the radio link is set up, the NodeB saves the value of the Configuration Ge
->If the radio link fails to be set up, the NodeB sends a RADIO LINK SETUP F
4.The DRNC reports the radio link setup result to the SRNC.
 The radio link setup procedure for inter-RNC handover is performed to set up
The procedure is described as follows:
1.The SRNC sends a RADIO LINK SETUP REQUEST message to the DRNC
2.The DRNC sends a RADIO LINK SETUP REQUEST message to the target
3.The NodeB reserves the necessary resources and configures the new radio
->If the radio link is set up, the NodeB saves the value of the Configuration Ge
->If the radio link fails to be set up, the NodeB sends a RADIO LINK SETUP F
4.The DRNC reports the radio link setup result to the SRNC.
->If the radio link is set up, the DRNC sends a RADIO LINK SETUP RESPON
->If the radio link fails to be set up, the DRNC sends a RADIO LINK SETUP F

The Iub user plane setup procedure is performed to set up bearers for data
The procedure is described as follows:

1.The CRNC uses the ALCAP protocol to send a QAAL2 ESTABLISH REQUE
2.The NodeB uses the ALCAP protocol to send a response message to the C
->If the Iub data transport bearers are set up, the NodeB sends a QAAL2 EST
estore Indication ->If an Iub data transport bearer fails to be set up, the NodeB sends a QAAL2

The radio link restoration procedure for inter-RNC handover is performed fo

er plane Setup 1.After performing UL synchronization with the UE, the NodeB sends a RADIO
2.The DRNC sends a RADIO LINK RESTORE INDICATION message to the S

The Iur user plane setup procedure is performed to set up bearers for data t
The procedure is described as follows:

1.The SRNC uses the ALCAP protocol to send a QAAL2 ESTABLISH REQUE
2.The DRNC uses the ALCAP protocol to send a response message to the SR
->If the Iur data transport bearers are set up, the DRNC sends a QAAL2 ESTA
->If an Iur data transport bearer fails to be set up, the DRNC sends a QAAL2

The physical channel reconfiguration procedure is performed to set up, rec

The procedure is described as follows:

1.The SRNC sends a PHYSICAL CHANNEL RECONFIGURATION message
2.The UE saves the IEs of the UE, Radio Bearer (RB), transport channel, and
->If successfully reconfiguring the physical channels specified by the PHYSIC
using AM RLC
->If failing to reconfigure the physical channels specified by the PHYSICAL CH
RECONFIGURATION FAILURE message on the DCCH by using AM RLC. Th

The radio link deletion procedure is performed to release resources in a Nod

The procedure is described as follows:

1.The CRNC sends a RADIO LINK DELETION REQUEST message to the No
2.The NodeB sends a response message to the CRNC.
->lf all the radio links are deleted, the NodeB sends a RADIO LINK DELETION
->lf any radio link fails to be deleted, the NodeB sends a RADIO LINK DELET
The procedure is described as follows:
1.The CRNC sends a RADIO LINK DELETION REQUEST message to the No
2.The NodeB sends a response message to the CRNC.
->lf all the radio links are deleted, the NodeB sends a RADIO LINK DELETION
->lf any radio link fails to be deleted, the NodeB sends a RADIO LINK DELET

The Iub user plane release procedure is performed to release data transport

The procedure is described as follows:

1.The CRNC uses the ALCAP protocol to send a QAAL2 RELEASE REQUES
2.The NodeB uses the ALCAP protocol to send a response message to the C
->If the Iub data transport bearers are released, the NodeB sends a QAAL2 R
->lf an Iub data transport bearer fails to be released, the NodeB sends a QAA

The Iur user plane release procedure is performed to release data transport

The procedure is described as follows:

1.The SRNC uses the ALCAP protocol to send a QAAL2 RELEASE REQUES
2.The DRNC uses the ALCAP protocol to send a response message to the SR
->If the Iur data transport bearers are released, the DRNC sends a QAAL2 RE
->If an Iur data transport bearer fails to be released, the DRNC sends a QAAL
and event parameters.When measurement conditions are changed, the RNC notifies

the measurement reporting criterias are met, the UE reports the results to the RNC as

create idle periods (gaps) in the transmission during which neighbour cells

a radio link in an SRNC-controlled NodeB for a UE

NodeB reserves the necessary resources and configures the new radio link according

he Configuration Generation ID IE contained in the RADIO LINK SETUP REQUEST

ends a RADIO LINK SETUP FAILURE message. The message contains the failure

ers are set up, the NodeB sends a QAAL2 ESTABLISH CONFIRM message.If an Iub

NodeB to notify the CRNC that the uplink synchronization of one or more radio links is

sage to the CRNC.

nnel

n of a physical channel.
response message to the SRNC.
N message, the UE sends a PHYSICAL CHANNELRECONFIGURATION COMPLETE

ssage, the UE restores the configuration to the old physicalchannel configuration and
alue of the Failure cause IE contained in the PHYSICAL CHANNEL
dio links towards a UE.

the NodeB deletes the radio links specified by the message.

IO LINK DELETION RESPONSE message.
riticality Diagnostics field in the message indicates the failure cause.

onfirm the release.

that indicates the failure cause

handover is performed to set up a radio link in a DRNC-controlled NodeB for a UE

EQUEST message to the DRNC.

EQUEST message to the target NodeB.
es and configures the new radio link according to the parameters given in the message.The NodeB reports the radio link setup result to
he value of the Configuration GenerationID IE contained in the RADIO LINK SETUP REQUEST message and sends a RADIOLINK SET
sends a RADIO LINK SETUP FAILUREmessage.
t to the SRNC.
rmed to set up bearers for data transmission on the Iub interface

d a QAAL2 ESTABLISH REQUEST messageto the NodeB.

d a response message to the CRNC.
the NodeB sends a QAAL2 ESTABLISH CONFIRM message.
up, the NodeB sends a QAAL2 ESTABLISH RELEASE CONFIRM message

-RNC handover is performed for a NodeB to notify the SRNC that the uplink synchronization of one or more radio links is achieved or re

e UE, the NodeB sends a RADIO LINKRESTORE INDICATION message to the DRNC.
E INDICATION message to the SRNC.

med to set up bearers for data transmission on the Iur interface

d a QAAL2 ESTABLISH REQUEST message to the DRNC.

d a response message to the SRNC.
he DRNC sends a QAAL2 ESTABLISHCONFIRM message.
up, the DRNC sends a QAAL2 ESTABLISHRELEASE CONFIRM message.

edure is performed to set up, reconfigure, or releasea physical channel

RECONFIGURATION message to the UE to request reconfiguration of a physical channel.

rer (RB), transport channel, and physical channel.The UE sends a response message to the SRNC.
annels specified by the PHYSICALCHANNEL RECONFIGURATION message, the UE sends a PHYSICAL CHANNELRECONFIGURAT

s specified by the PHYSICAL CHANNELRECONFIGURATION message, the UE restores the configuration to the old physicalchannel c
he DCCH by using AM RLC. The value of the Failure cause IE contained in the PHYSICAL CHANNEL RECONFIGURATION FAILURE

ed to release resources in a NodeB for one or more established radio links towards a UE.

N REQUEST message to the NodeB. After receiving the message, the NodeB deletes the radio links specified by the message.
he CRNC.
sends a RADIO LINK DELETION RESPONSE message.
B sends a RADIO LINK DELETION RESPONSE message. The Criticality Diagnostics field in the message indicates the failure cause.
ormed to release data transport bearers from the Iubinterface.

d a QAAL2 RELEASE REQUEST messageto the NodeB.

d a response message to the CRNC.
d, the NodeB sends a QAAL2 RELEASE CONFIRM message to confirm the release.
eased, the NodeB sends a QAAL2 RELEASECONFIRM message that indicates the failure cause

ormed to release data transport bearers from the Iur interface

d a QAAL2 RELEASE REQUEST messageto the DRNC.

d a response message to the SRNC.
d, the DRNC sends a QAAL2 RELEASECONFIRM message to confirm the release.
eased, the DRNC sends a QAAL2 RELEASECONFIRM message that indicates the failure cause.
 ts the radio link setup result to the DRNC.
e and sends a RADIOLINK SETUP RESPONSE message.
ore radio links is achieved or re-achieved.

L CHANNELRECONFIGURATION COMPLETE message on the uplink DCCH by

n to the old physicalchannel configuration and sends a PHYSICAL CHANNEL

ECONFIGURATION FAILURE message is "physical channel failure".

cified by the message.

ge indicates the failure cause.

 Click to return to main page

L3 Messag
UE NodeB

Inter-R

RRC:Measurement Control

RRC:Measurement Report (e2d)

RRC:Measurement Report (e2f)

RRC:Measurement Report (e2d)

1. RRC:Physical Channel Reconfiguration (DCCH)

2. RRC: Physical Channel Reconfiguration Complete (DCCH)

RRC:Measurement Control

RRC:Measurement Report

RRC:Measurement Report
 7.RRC: Handover from UTRAN Command

Note: the following information about the procedure ,

1.This figure presents only a brief of the signaling between the MSC server and the MSC(GSM) and that between the M
(GSM) and the BSC (GSM).

2.The SRNC sends a HANDOVER FROM UTRAN COMMAND message to the UE. The message contains the RAB ID,
activation time, the GSM frequency, and the GSM information in bit strings.

Click to return to main page

L3 Messag
UE NodeB

Inter-R
 9.In

12.RRC: Handover to UTRAN Complete(DCCH)

13.RRC: UE Capability Enquiry(DCCH)

14.RRC: UE Capability Information (DCCH)

15.RRC: UE Capability Information Confirm (DCCH)

16.RRC: Security Mode Command(DCCH)

17.RRC: Security Mode Complete(DCCH)

23.RRC: UTRAN Mobility Information (DCCH)

24.RRC: UTRAN Mobility Information Confirm (DCCH)

Note: the following information about the procedure ,

1.This figure presents only a brief of the signaling between the MSC server and the MSC(GSM) and that between the M
(GSM) and the BSC (GSM).
2.After receiving a RADIO LINK RESTORE INDICATION message, the RNC sends a RELOCATION DETECT message
the MSC server to inform the MSC server that the UE has been handed over from GSM to WCDMA.
3.After the UE is handed over, it sends a HANDOVER TO UTRAN COMPLETE message to the RNC. If the handover fa
the UE reports the failure to the GSM system.
4.After receiving a HANDOVER TO UTRAN COMPLETE message, the RNC sends a RELOCATION COMPLETE mess
to the MSC server. In addition, the RNC controls the UE to perform the UTRAN mobility information procedure, the UE
capability enquiry procedure, and the security mode control procedure.
5.In practice, the signaling messages traced may differ from the signaling message shown inthe figure in terms of the
sequence
3.After the UE is handed over, it sends a HANDOVER TO UTRAN COMPLETE message to the RNC. If the handover fa
the UE reports the failure to the GSM system.
4.After receiving a HANDOVER TO UTRAN COMPLETE message, the RNC sends a RELOCATION COMPLETE mess
to the MSC server. In addition, the RNC controls the UE to perform the UTRAN mobility information procedure, the UE
capability enquiry procedure, and the security mode control procedure.
5.In practice, the signaling messages traced may differ from the signaling message shown inthe figure in terms of the
sequence
 L3 Messages - Inter-RAT Handover Procedure
S-RNC

Inter-RAT CS Handover from WCDMA to GSM

RRC:Measurement Control

RRC:Measurement Report (e2d)

RRC:Measurement Report (e2f)

RRC:Measurement Report (e2d)

NBAP: Radio Link Reconfiguration Prepare

NBAP: Radio Link Reconfiguration Ready

NBAP: Radio Link Reconfiguration Commit

ysical Channel Reconfiguration (DCCH)

al Channel Reconfiguration Complete (DCCH)

NBAP: Compressed Mode Command

RRC:Measurement Control

RRC:Measurement Report

RRC:Measurement Report
Decision to
HO to GSM
cell
C: Handover from UTRAN Command

9.Handover Completed

NBAP:Radio Link Deletion Request

NBAP:Radio Link Deletion Response

dure ,

ng between the MSC server and the MSC(GSM) and that between the MSC

RAN COMMAND message to the UE. The message contains the RAB ID, the
SM information in bit strings.

L3 Messages - Inter-RAT Handover Procedure

S-RNC

Inter-RAT CS Handover from GSM to WCDMA

4.NBAP:Radio Link Setup Request

5.NBAP:Radio Link setup Response

 9.Inter-System to UTRAN Handover Command

10.NBAP:Radio Link Restore Indication

: Handover to UTRAN Complete(DCCH)

RRC: UE Capability Enquiry(DCCH)

RC: UE Capability Information (DCCH)

UE Capability Information Confirm (DCCH)

RC: Security Mode Command(DCCH)

RC: Security Mode Complete(DCCH)

C: UTRAN Mobility Information (DCCH)

TRAN Mobility Information Confirm (DCCH)

dure ,

ng between the MSC server and the MSC(GSM) and that between the MSC

DICATION message, the RNC sends a RELOCATION DETECT message to

he UE has been handed over from GSM to WCDMA.
DOVER TO UTRAN COMPLETE message to the RNC. If the handover fails,

OMPLETE message, the RNC sends a RELOCATION COMPLETE message

s the UE to perform the UTRAN mobility information procedure, the UE
mode control procedure.
ay differ from the signaling message shown inthe figure in terms of the
ges - Inter-RAT Handover Procedure
MSC 3G MSC 2G

AT CS Handover from WCDMA to GSM

1.RANAP: Relocation Required

2.Prepare Handover

5.Prepare Handover
Response
6.RANAP:Relocation Command
 9.Handover Completed

11.Send End Signal

Request

12.RANAP: IU Release Command

13.RANAP: IU Release Complete

14.Send End Signal
Response

ges - Inter-RAT Handover Procedure

MSC-3G MSC-2G

AT CS Handover from GSM to WCDMA

2.Prepare Handover
3.RANAP: Relocation Request
 6.RANAP:Relocation Request Acknowledge
7.Prepare Handover
Response

er-System to UTRAN Handover Command

11.RANAP:Relocation Detect

18.RANAP:Relocation
Complete
19.Send End Signal
Request

22.Send End Signal

Response
 >>Inter-RAT HO Algorithm and related parameters

BSC2
G

>>Measurement Control&Report (Inter-RAT)

Description

Measurement Control
& Measurement Report

>>Compressed Mode Description

Initial Compressed Mode Configuration

GSM RSSI Measurement

and BSIC Verification

3.Handover Request

4.Handover Request Relocation Preparation

Acknowledge
 8.Handover Detect
Handover

10.Handover Complete

Iu release

Radio Link Deletion

>>Inter-RAT HO Algorithm and related parameters

BSC2
G

1.Handover Required

Relocation Resource allocation

 Relocation Resource allocation

8.Handover Command

9.Handover Complete

Radio Link Restoration

UE Capability Enquiry

Security Mode Control

20.Clear Command

21.Clear Complete

UTRAN Mobility Information

m and related parameters

Measurement Control is used to notify the UE of the objects to be measured, neighbor cell lis
Report (Inter-RAT) conditions.

Measurement Report, the UE continue measure the radio link condition of serving and neighb
Measurement report is also can be sent in periodic mode.

Compressed Mode was introduced to WCDMA to allow inter-frequency and Inter-RAT Hando
frequency can be made.

The relocation preparation procedure is performed to prepare resources for relocation of the

The procedure is described as follows:

1.The SRNC sends a RELOCATION REQUIRED message to the CN. The message contains
target CI,LAC.
2.The CN interacts with the target RNC or the target network system, such as the GSM system
3.The CN sends a response message to the SRNC.
->If the target RNC or the target network system prepares the relevant resources successfully,
information IE, which carries the information about the relevant resources allocated by the targ
->If the resources partially or totally fail to be allocated, the CN sends a RELOCATIONPREPA

The Inter-RAT Handover procedure is described as follows:

1. The SRNC sends the 3G MSC a RANAP message "Relocation Required" if the condition of
2. As indicated in the received message,the 3G MSC forwards this request to the 2G MSC on
Handover"
3. The 2G MSC forwards the request to the BSC. The message shown in the figure is for refer
4. The BSC responds to this request. The message shown in the figure is for reference only an
5. Once the initial procedures are completed in the 2G MSC/BSS,the 2G MSC returns a MAP/
6. The 3G MSC sends the SRNC a RANAP message "Relocation Command"
7. The SRNC send the UE and RRC message "Handover from UTRAN" through the existing R
several other systems
8. The BSC performs handover detection. The figure does not show such procedures as GSM
reference and is subject to the actual conditon of GSM
9. The UE send the BSC a "Handover Complete" message
10. The BSC sends the MSC a 'Handover Complete" message. The message shown in the fig
GSM
11. After detecting the UE in the coverage area of the GSM,the MSC sends the CN a MAP/E m
12. The CN sends the former SRNC and "Iu Release Command" message , requesting the for
13. After the bearer resource is related in the UMTS, the former SRNC sends the CN an "Iu Re
 several other systems
8. The BSC performs handover detection. The figure does not show such procedures as GSM
reference and is subject to the actual conditon of GSM
9. The UE send the BSC a "Handover Complete" message
10. The BSC sends the MSC a 'Handover Complete" message. The message shown in the fig
GSM
11. After detecting the UE in the coverage area of the GSM,the MSC sends the CN a MAP/E m
12. The CN sends the former SRNC and "Iu Release Command" message , requesting the for
13. After the bearer resource is related in the UMTS, the former SRNC sends the CN an "Iu Re
14. After the call ends, the CN sends the MSC a MAP/E message "Send End Signal Response

The Iu release procedure is performed for the CN to release an Iu connection and all the UTR

The procedure is described as follows:

1.The CN sends an IU RELEASE COMMAND message to the SRNC to initiate the Iu release
NOTE: After sending the IU RELEASE COMMAND message, the CN will not send further RAN

2.The SRNC releases the related UTRAN resources and then sends an IU RELEASE COMPL

The radio link deletion procedure is performed to release resources in a NodeB for one or m
The procedure is described as follows:
1.The CRNC sends a RADIO LINK DELETION REQUEST message to the NodeB. After receiv
2.The NodeB sends a response message to the CRNC.
->If all the radio links are deleted, the NodeB sends a RADIO LINK DELETION RESPONSE m
->If any radio link fails to be deleted, the NodeB sends a RADIO LINK DELETIONRESPONSE

m and related parameters

The relocation resource allocation procedure is performed to allocate resources from the ta
The relocation resource allocation procedure can be triggered in either of the followingconditio
1. During an SRNS relocation, the CN applies for resources from the target RNC
2. During an inter-RAT CS handover from GSM to WCDMA, the CN applies for resources from

The procedure is described as follows:

1.The CN sends a RELOCATION REQUEST message to the target RNC. The message conta
protection, Iu signaling connection ID, handover cause, andRAB parameters.
2.The target RNC allocates radio resources for the relocation.
3.The target RNC sends a response message to the CN.
->If the resources are allocated, the target RNC sends a RELOCATION REQUEST ACKNOWL
include the UTRAN Radio NetworkTemporary Identifier (U-RNTI), RAB, transport layer and ph
->If the resources partially or totally fail to be allocated or the target RNC rejects the SRNS relo
FAILURE message,indicating the failure cause
The procedure is described as follows:
1.The CN sends a RELOCATION REQUEST message to the target RNC. The message conta
protection, Iu signaling connection ID, handover cause, andRAB parameters.
2.The target RNC allocates radio resources for the relocation.
3.The target RNC sends a response message to the CN.
->If the resources are allocated, the target RNC sends a RELOCATION REQUEST ACKNOWL
include the UTRAN Radio NetworkTemporary Identifier (U-RNTI), RAB, transport layer and ph
->If the resources partially or totally fail to be allocated or the target RNC rejects the SRNS relo
FAILURE message,indicating the failure cause

The radio link setup procedure (intra-RNC handover or GSM to WCDMA CS handover) isper

The procedure is described as follows:

1.The CRNC sends a RADIO LINK SETUP REQUEST message to the NodeB. Afterr eceiving
given in the message.
2.The NodeB sends a response message to the CRNC.
->If the radio link is set up, the NodeB saves the value of the Configuration GenerationID IE co
->If the radio link fails to be set up, the NodeB sends a RADIO LINK SETUP FAILURE messag

The radio link restoration procedure (intra-RNC handover or GSM to WCDMA CS handover)
achieved

After performing UL synchronization with the UE, the NodeB sends a RADIO LINK RESTORE

The UE capability enquiry procedure is performed to request a UE to transmit its capability in

capability

The procedure is described as follows:

1.The SRNC sends a UE CAPABILITY ENQUIRY message to the UE through the downlink DC
2.The UE sends a UE CAPABILITY INFORMATION message to the SRNC through the uplink
3.The SRNC reads the UE capability information and then sends a UE CAPABILITYINFORMA

The security mode control procedure is performed to configure or reconfigure one or both of
algorithm or the integrity protection algorithm has changed
The procedure is described as follows:
1.Through a SECURITY MODE COMMAND message sent to the UE, the SRNC starts or reco
Signaling Radio Bearers (SRBs).
2.The UE sends a response message to the SRNC.
->If the UE completes configuring or reconfiguring the relevant parameters for one orboth of th
SRNC of the completion.
->If the SECURITY MODE COMMAND message contains neither Ciphering mode info IE nor
FAILURE message, indicating the failure of the security mode control procedure as well as the
The UTRAN mobility information procedure is performed for the network to allocate a newU
inform the UE of mobility-related information such as timervalues and CN domainrelated info

1.The SRNC sends a UTRAN MOBILITY INFORMATION message to the UE.

2.The UE starts to update the related fields according to the values of the IEs carried in theme
3.The UE sends a response message to the SRNC.
->If the UE succeeds in conducting the operations specified by the UTRAN MOBILITYINFORM
->If the UE fails to conduct the operations specified by the UTRAN MOBILITYINFORMATION
s to be measured, neighbor cell list, report method, and event parameters.When measurement conditions are changed, the RNC notifies th

nk condition of serving and neighbour cell and when the measurement reporting criterias are met, the UE reports the results to the RNC as

r-frequency and Inter-RAT Handovers. It is used to create idle periods (gaps) in the transmission during which neighbour cells measuremen

are resources for relocation of the SRNS

o the CN. The message contains certain information such as relocation type, relocation cause, source PLMN, source LAC,source SAC, targ

system, such as the GSM system, to prepare relevant resources.

e relevant resources successfully, the CN sends a RELOCATION COMMAND message when the preparation is complete. The message co
ant resources allocated by the target RNC or the target network system.
CN sends a RELOCATIONPREPARATION FAILURE message.

ation Required" if the condition of Inter-RAT Outgoing HO is met

ds this request to the 2G MSC on the MAP/E interface through a MAP message "Prepare

age shown in the figure is for reference only and is subject to the actual conditon of the GSM
n the figure is for reference only and is subject to the actual conditon of the GSM
BSS,the 2G MSC returns a MAP/E message 'Prepare Handover Response"
ation Command"
om UTRAN" through the existing RRC connection. This message may include information from one or

ot show such procedures as GSM BSS synchronization. The message shown in the figure is for

ge. The message shown in the figure for reference only and is subject to the actual condition of the

he MSC sends the CN a MAP/E message "Send End Signal Request"

and" message , requesting the former SRNC to release the allocated resource
mer SRNC sends the CN an "Iu Release Complete" message
 an Iu connection and all the UTRANresources related only to that Iu connection

he SRNC to initiate the Iu release procedure. The message indicates the cause for the release of the signaling connection.
e, the CN will not send further RANAP connection-oriented messages on this particular connection.

n sends an IU RELEASE COMPLETE message to the CN.

esources in a NodeB for one or more established radio links towards a UE.

message to the NodeB. After receiving the message, the NodeB deletes the radio links specified by the message.

O LINK DELETION RESPONSE message.

DIO LINK DELETIONRESPONSE message. The Criticality Diagnostics field in the message indicates the failure cause.

d to allocate resources from the targetRNS for an SRNS relocation.

d in either of the followingconditions:
from the target RNC
the CN applies for resources from the target RNC

e target RNC. The message contains certain information, such as the IMSI of the UE, CN domain indicator, target cell identifier, encryption,
RAB parameters.
n.

LOCATION REQUEST ACKNOWLEDGE message. The message contains the radio resources and other parameters allocated to the UE. T
NTI), RAB, transport layer and physical layer information,chosen encryption algorithm, and chosen integrity protection algorithm.
target RNC rejects the SRNS relocation for some reason, the target RNC sends a RELOCATION
M to WCDMA CS handover) isperformed to set up a radio link in an SRNC-controlled NodeB for a UE

sage to the NodeB. Afterr eceiving the message, the NodeB reserves the necessary resources and configures the new radio link according t

Configuration GenerationID IE contained in the RADIO LINK SETUP REQUEST message and sends a RADIO LINK SETUP RESPONSE
O LINK SETUP FAILURE message. The message contains the failure cause.

or GSM to WCDMA CS handover)is performed for a NodeB to notify the CRNC that the uplink synchronization of one or moreradio links is a

sends a RADIO LINK RESTOREINDICATION message to the CRNC

st a UE to transmit its capability information related to any radio access network so that the network can perform data configuration based o

o the UE through the downlink DCCH using AM RLC.

e to the SRNC through the uplink DCCH using AM or UM RLC. The message contains the information about UE capabilities.
ends a UE CAPABILITYINFORMA CONFIRM message to the UE through the downlink DCCH using AM or UMRLC.

gure or reconfigure one or both of the ciphering algorithm and the integrity protection algorithm for a UE. The triggered conditon is when the

o the UE, the SRNC starts or reconfigures one or both of the ciphering and integrity protection configurations for theRBs or one CN domain

nt parameters for one orboth of the ciphering and integrity protection algorithms, the UE sends a SECURITYMODE COMPLETE message

either Ciphering mode info IE nor Integrity protection mode info IE or if each of the two IEs has inconsistent information, the UE sends a SE
e control procedure as well as the failure cause.
 or the network to allocate a newUTRAN Radio Network Temporary Identifier (U-RNTI) or Cell Radio Network TemporaryIdentifier (C-RNTI) t
alues and CN domainrelated information

essage to the UE.

values of the IEs carried in themessage.

by the UTRAN MOBILITYINFORMATION message, the UE sends a UTRAN MOBILITY INFORMATION CONFIRM message.
TRAN MOBILITYINFORMATION message, the UE sends a UTRAN MOBILITY INFORMATIONFAILURE message, indicating the failure ca
are changed, the RNC notifies the UE of new

eports the results to the RNC as an event. The

ch neighbour cells measurements on another

N, source LAC,source SAC, target PLMN, and

on is complete. The message contains the L3

ng connection.

sage.

ailure cause.

target cell identifier, encryption, integrity

arameters allocated to the UE. The parameters

protection algorithm.
es the new radio link according to the parameters

ADIO LINK SETUP RESPONSE message.

on of one or moreradio links is achieved or re-

rform data configuration based on the UE

ut UE capabilities.
UMRLC.

e triggered conditon is when the ciphering

s for theRBs or one CN domain and for all

YMODE COMPLETE message to inform the

information, the UE sends a SECURITY MODE

k TemporaryIdentifier (C-RNTI) to a UE or to

ONFIRM message.
essage, indicating the failure cause.
Click to return to main page
RRC:Measurement Control
RRC:Measurement Report (e2d)
 RRC:Measurement Report (e2f)

RRC:Physical Channel Reconfiguration (DCCH)

RRC: Physical Channel Reconfiguration Complete (DCCH)

RRC:Measurement Control
RRC:Measurement Report
RRC: Handover from UTRAN Command
Handover Completed
 >>"Measurement Control and Measurement Report"

value=interFrequencyMeasurement (RNC send mearuement control of InterFrequency because

parameter CoexistMeasThdChoice="COEXIST_MEAS_THD_CHOICE_INTERFREQ")

value=Inter-freq meas L3 filter coeff=3

value=Inter-freq meas based on CPICH Ec/No

value=Event2D ( Start Compressed Mode)

value= InterFreqCSThd2DEcN0=-14 dB

value= 0
value=2 dB ,Step: 0.5
value=320ms

value=Event2f ( Stop Compressed Mode)

value= InterFreqCSThd2FEcN0=-12 dB

value= 0
value=2 dB ,Step: 0.5
value=320ms
 value=UE trigger Event2D to start Compressed Mode

value=UE trigger Event2f to stop Compressed Mode

CCH)
value=Compressed Mode Inforamtion
te (DCCH)
value=interRATMeasurement (RNC send mearuement control of InterRAT after enter Compressed Mode)

value=InterRAT cell list

value=InterRAT cell Index

value=InterRATCIO=0
value=NCC=6
value=BCC=4
value=GSM900 ( GSM1800 not used)

value=BCCH=64
value=UE measure on GSM RSSI
value=InterRATFilterCoef=3
value=UE need to verify BSIC

value=InterRATPeriodReportInterval= 1000ms

value=UE report 6 InterRATcells to RNC

 value=RSSI= -110 + hex2dec(1E) = -80 dBm

value=BSIC=35 ( BCCH=112) refer to InterRAT CellID=7 in Measurement Control (GSM900)

d
InterFrequency because
NTERFREQ")
AT after enter Compressed Mode)
t Control (GSM900)
 Click to return to main page

UE BSS S-RNC

1.RRC:Cell Change Order from UTRAN

2.Routing Area Update Request

UE Connected

UE Connected

UE Connected
 19.Routing Area Update Accept

20.Routing Area Update Complete

22. BSS Packet Flow Context Procedure

Note: the following information about the procedure ,

1.When the PS data volume is low, the UE may be in CELL_PCH, URA_PCH, or Cell_FACH state or when
perform a handover to GSM. The cell reselection is initiated with an SRNS CONTEXT REQUEST messag

When the UE in Idle ,URA_PCH.Cell_PCH or Cell_FACH states, the cell reselection procedure does not in

2.After cell reselection to a GSM cell, the NodeB sends a RADIO LINK FAILURE INDICATION message b
the procedure of inter-RAT PS handover from WCDMA to GSM.
3. After the UE accesses a GSM cell, the SGSN directly sends an IU RELEASE COMMAND message to t
4.The SRNS context transfer is unnecessary to the procedure of inter-RAT PS handover from WCDMA to

Click to return to main page

UE BSC S-RNC

1. Inter-RAT Handover
Decision
 2.Routing Area Update Request

16.Routing Area Update Accept

17.Routing Area Update Complete

 19.Service Request

Setup Radio Resources

 L3 Messages - Inter-RAT Handover P
SGSN-2G SGSN-3G

Inter-RAT PS Handover from WCDMA

The procedure in this stage is simiilar to Inter-RAT CS Handov

( "RRC: Handover from UTRAN Command " message is equivalent to "RR

Update Request
UE Connected 3.SGSN Context Request

4.SRNS Context Request

4.SRNS Context Response

5.SGSN Context Response

6.Security Functions

7.SGSN Context Acknowledge

UE Connected C1

8.SRNS Data Forward Command

8.Forward Packets

9. Forward Packets

10. Update PDP Context Request

10. Update PDP Context Response

UE Connected

13.Iu Release Command

13. Iu Release Complete

 14

15.

16. Location Update Reque

18 Location Update Accep

a Update Accept

Update Complete

2. BSS Packet Flow Context Procedure

PCH, URA_PCH, or Cell_FACH state or when UE in Idle state. Based on the parameters in the system information, the UE can initiate c
ith an SRNS CONTEXT REQUEST message sent from the SGSN to SRNC.

es, the cell reselection procedure does not include the sub-procedires which marked with "UE Connected)

DIO LINK FAILURE INDICATION message because the UE stops the transmission towards the WCDMA cell.This message, however, is
M.
s an IU RELEASE COMMAND message to the SRNC, if the Packet Data Protocol (PDP) context does not need to be transferred.
of inter-RAT PS handover from WCDMA to GSM.

L3 Messages - Inter-RAT Handover P

SGSN-3G SGSN-2G

Inter-RAT PS Handover from GSM to W

Update Request
3.SGSN Context Request

4.SGSN Context Response

5.Security Functions

6.SGSN Context Acknowledge

C1

7. Forward Packets

8. Update PDP Context Request

8 Update PDP Context Response

11.

12.

13. Location Update Reque

15 Location Update Accep

C2

a Update Accept

C3

Update Complete
 18. TMSI Reallocation Comp

ce Request

20. RAB Assignement Request

20. RAB Assignement Response

-RAT Handover Procedure
SGSN-3G GGSN MSC-2G

dover from WCDMA to GSM

Inter-RAT CS Handover from WCDMA to GSM

ge is equivalent to "RRC:Cell Change Order from UTRAN" )

C1

ontext Request

ntext Response

11. Update GPRS Location

12. Cancel Location

12. Cancel Location Acknowledge

14. Insert Subscriber Data

 14. Insert Subscriber Data Acknowledge

15. Update GPRS Location Acknowledge

. Location Update Request

17. Update Locati
8 Location Update Accept

21. TMSI Reallocation Complete

ion, the UE can initiate cell reselection to

his message, however, is unnecessary to

d to be transferred.

-RAT Handover Procedure

SGSN-2G GGSN MSC-3G

over from GSM to WCDMA

 C1

ontext Request

ntext Response

9. Update GPRS Location

10. Cancel Location

10. Cancel Location Acknowledge

11. Insert Subscriber Data

11. Insert Subscriber Data Acknowledge

12. Update GPRS Location Acknowledge

. Location Update Request

14a. Update Location

14d. Insert Subscriber Data

14e. Insert Subscriber Data Ack

14f. Update Location Ack

5 Location Update Accept

TMSI Reallocation Complete
 >>Inter-RAT HO Algorithm and r
MSC-
HLR
3G

SRNS Context Transfer

Iu release
17. Update Location

>>Inter-RAT HO Algorithm and r

MSC-
HLR
2G
14b.Cancel Location

14c. Cancel Location Ack

HO Algorithm and related parameters

The Inter-RAT PS handover from WCDMA to GSM procedure is described as follows:

1.The UE in Cell_DCH state, the UTRAN decides to initiate an inter-RAT handover in the PS domain b
and the network

2. The UE sends a "Routing Area Update Request" message to the 2G SGSN. The update type in the
RAC and LAC of the cell to the received message before forwarding the message to a new 2G SGSN

3. The new 2G SGSN sends an "SGSN Context Request" message to the old 3G SGSN to obtain the M
timer. Otherwise, the old 3G SGSN respons with an error cause.

4. If the UE stay in connected mode before handover, the old 3G SGSN sends an "SRNS Context Req
Response" message to the old 3G SGSN

5. The old 3G SGSN sends an "SGSN Context Response" message to the 2G SGSN including the MM
6. The security functions can be excuted
7. The new 2G SGSN sends an 'SGSN Context Acknowledge" message to the old 3G SGSN. This info
ready to receive PDUs belonging to the activated PDP contexts

8. The old 3G SGSN sends a "Data Forward Command" message to the SRNS. The SRNS starts a da
the old 3G SGSN

9. The old 3G SGSN tunnels the GTP PDUs to the new 2G SGSN. In the PDUs, the sequence number

10. the new 2G SGSN sends an "Update PDP Context Request" message to each related GGSN. Eac
message after updating it's PDP Context fields

11. The new 2G SGSN sends an "Update GPRS Location" message ,requesting the HLR to modify the
12. The HLR sends a "Cancel Location" message to the old 3G SGSN. the old 3G SGSN responds wit
timer expires,the old 3G SGSN removes the MM and PDP contexts.

13. The old 3G SGSN sends an "Iu release command" message to the SRNS. After data-forwarding tim
Release complete"

14. The HLR sends an "Insert Subscriber Data" message to the new 2G SGSN. The 2G SGSN constru
returen an "Insert Subscriber Data Ack" message to the HLR

15.The HLR sends an "Update GPRS Location ACK" message to the new 2G SGSN
16. If the association has to be established, the new 2G SGSN sens a 'Location Update Request" mes
number for creating or updating the association

17. If the subscriber data in VLR is marked as not confirmed by the HLR. the new VLR informs the HLP
subscriber data in the new VLR
- The new VLR sends an "Update Location" message to the HLR
- The HLR cancels the data in the old VLR by sending a "Cancel Location" message to the old VLR
- The old VLR acknowledge the message by responding with a "Cancel Location ACK" message
- The HLR sends an "Insert Subscriber Data" message to the new VLR
- The new VLR acknowledge the message by responding with an "Insert Subscriber Data ACK" messa
- The HLR responds with an "Update Location Ack" message to the new VLR

18. The new VLR allocates a new TMSI and responds with a "Location Update Accept" message to the
19. The new 2G SGSN checks the presence of the MS in the new RA. If all checks area successful,the
established between the new 2G SGSN and the UE. The 2G SGSN responds to the UE with a "Routin
 subscriber data in the new VLR
- The new VLR sends an "Update Location" message to the HLR
- The HLR cancels the data in the old VLR by sending a "Cancel Location" message to the old VLR
- The old VLR acknowledge the message by responding with a "Cancel Location ACK" message
- The HLR sends an "Insert Subscriber Data" message to the new VLR
- The new VLR acknowledge the message by responding with an "Insert Subscriber Data ACK" messa
- The HLR responds with an "Update Location Ack" message to the new VLR

18. The new VLR allocates a new TMSI and responds with a "Location Update Accept" message to the
19. The new 2G SGSN checks the presence of the MS in the new RA. If all checks area successful,the
established between the new 2G SGSN and the UE. The 2G SGSN responds to the UE with a "Routin

20. The UE acknowledge the new P-TMSI by returning a "Routing Area Update Complete" message, in
21. The new 2G SGSN sends a "TMSI Reallocation Complete" message to the new VLR if the UE con
22. The 2G SGSN and the BSS perform the "BSS Packet Flow Context" procedure

HO Algorithm and related parameters

The Inter-RAT PS handover from GSM to WCDMA procedure is described as follows:

The Inter-RAT PS handover from GSM to WCDMA procedure is described as follows:

1.The GSM decides to perform an inter-RAT handover in PS domanin and stops the data transmission

2. The UE sends a "Routing Area Update Request" message to the 3G SGSN. The update type in the
update with IMSI attach. The SRNC adds the the RAC and LAC of the cell to the received message be

3. The new 3G SGSN obtain the address of the old 2G SGSN, and then sends an 'SGSN Context Req
the UE. The old 2G SGSN validates the old P-TMSI signature. If the old P-TMSI Signature is valid, the
cause.

4. The old 2G SGSN response with an "SGSN Context Response" message to the 3G SGSN including

5. The security functions can be excuted

6. The new 3G SGSN sends an 'SGSN Context Acknowledge" message to the old 2G SGSN. This info
belonging to the activated PDP contexts

7. The old 2G SGSN copied and buffers N-PDUs, and then sends them to the 3G SGSN. Before the tim
and sends them to the 3G SGSN. After the timer expires,the 2G SGSN does not send N-PDUs to the

8.The new 3G SGSN sends an "Update PDP Context Request" message to each related GGSN. Each
PDP Context fields

9. The new3G SGSN tsends an "Update GPRS Location" message to the HLR

10. The HLR sends a 'Cancel Location" message to the 2G SGSN. After the timer expires,the 2G SGS
Location Ack" message

11.The HLR sens an "Insert Subscriber Data" message to the 3G SGSN. The 3G SGSN constructs an

12. The HLR sends "Update GPRS Location" by returning an "Update GPRS Location Ack" message to

13. If the association has to be establilshed, that is . if the Update Type parameter indicates a combine
update, the 2G SGSN sends a "Location update request" message to the VLR. The VLR stores the SG

14. If the subscriber data in VLR is marked as not confirmed by the HLR. the new VLR informs the HLP

- The new VLR sends an "Update Location" message to the HLR

- The HLR cancels the data in the old VLR by sending a "Cancel Location" message to the old VLR
- The old VLR acknowledge the message by responding with a "Cancel Location ACK" message
- The HLR sends an "Insert Subscriber Data" message to the new VLR
- The new VLR acknowledge the message by responding with an "Insert Subscriber Data ACK" messa
- The HLR responds with an "Update Location Ack" message to the new VLR

15. The new VLR allocates a new TMSI and responds with a "Location Update Accept" message to the
16. The new 3G SGSN checks the presence of the MS in the new RA. If all checks area successful,the
established between the new 3G SGSN and the UE. The 3G SGSN responds to the UE with a "Routin

17. The UE sends a "Routing Area Update Complete" message to confirm the allocated P-TMSI
18. The new 3G SGSN sends a "TMSI Reallocation Complete" message to the new VLR if the UE con
19. If the UE has uplink data or signalling to send, the UE sends a "Service Request" message to the S

20. The 3G SGSN sends a "RAB Assignment Request" message to the SRNS. The SRNS sens a 'Rad
Setup Complete" message. The SRNS sends a 'RAB assignment Response" message to the SGSN. T
e is described as follows:

AT handover in the PS domain be sending "Cell Change Order from UTRAN' messge to UE to handover to a new GSM cell and stop th

G SGSN. The update type in the message indicates RA update, combined RA/LA update, or combined RA/LA update with IMSI attach.
he message to a new 2G SGSN

o the old 3G SGSN to obtain the MM and PDP contexts. The old 3G SGSN validates the old P-TMSI signature. If the old P-TMSI Signat

SN sends an "SRNS Context Request" message. After receiving this message, the SRNS buffers the PDUs, stops sending the PDUs to

o the 2G SGSN including the MM and PDP context

ge to the old 3G SGSN. This inform the old 3G SGSN that the new 2G SGSN is

the SRNS. The SRNS starts a data-forwarding timer and sends the buffers PDUs to

the PDUs, the sequence number in the GTP hearder remain unchange

sage to each related GGSN. Each GGSN sends an "Update PDP Context Response"

requesting the HLR to modify the SGSN number

N. the old 3G SGSN responds with a "Cancel Location AcK" message. After the

e SRNS. After data-forwarding timer expires,the SRNS responds with an "Iu

2G SGSN. The 2G SGSN constructs an MM context and PDP context for the UE and

new 2G SGSN
a 'Location Update Request" message to the VLR. The VLR stores the SGSN

LR. the new VLR informs the HLP. The HLR cancel the old VLR and inserts

ation" message to the old VLR

cel Location ACK" message
LR
sert Subscriber Data ACK" message
new VLR

n Update Accept" message to the 2G SGSN

. If all checks area successful,the new 2G SGSN constructs the MM and PDP contexts for the MS. A logical link is
esponds to the UE with a "Routing Area Update Accept" message
e is described as follows:
ndover to a new GSM cell and stop the data transmission between the UE

bined RA/LA update with IMSI attach. The BSS adds the CGI including the

SI signature. If the old P-TMSI Signature is valid, the old 3G SGSN starts a

he PDUs, stops sending the PDUs to the UE, and send an "SRNS Context

. A logical link is
 Click to return to main page

L3 Messages - Inter-RAT Hando

2G/3G
UE BSS
SGSN

Inter-RAT CS&PS Handover from WCDMA

1. Inter-RAT Handover

2.Suspend

3.Suspend

3. Suspend Ack

4. Resume

4. Resume NAck

5.Channel Release

6. Routing Area Update Request

Click to return to main page

L3 Messages - Inter-RAT Hando

2G
UE BSS
SGSN

Inter-RAT CS&PS Handover from WCDMA

1. Inter-RAT Handover

2.Suspend

3.Suspend

3. Suspend Ack
 4. Resume

4. Resume NAck

5.Channel Release

6. Routing Area Update Request

Inter-RAT Handover Procedure
2G/3G MSC/
SRNS
SGSN VLR

dover from WCDMA to GSM (Intra-SGSN)

1. Inter-RAT Handover

3. SRNS Context Request

3. SRNS Context Response

Inter-RAT Handover Procedure

2G MSC/
3G SGSN SRNS
SGSN VLR

dover from WCDMA to GSM (Inter-SGSN)

1. Inter-RAT Handover
>>Inter-RAT HO Algorithm and related
parameters

For a UE in Cell_DCH state using both CS and PS domain services,the inter-RAT handover procedu
the inter-RAT handover from UTRA RRC Connected Mode to GSM Connected Mode first. After the U
towards the GPRS to suspend the GPRS services. After the CS domain services are released on the
completed.

if the inter-RAT handover from UTRA RCC Conencted Mode to GSM Connected Mode succeeds,the
case of inter-RAT handover failure, the UE may go back to the UTRA RRC Connected Mode and re-e

The signalling procedures are described as follows,

1. The UE in connection with both CS and PS domain perrforms the UMTS to GSM handover during

2. The UE sends a suspend message to the BSS

3. The BSS forwards the 'Suspend" message to the SGSN. The SGSN sends a "SRNS Context Req
message, the SRNS buffers downlink PDUs and respons to the SGSN with an 'SRNS Context Respo

4. When the CS connection is terminated , the BSS may send a 'Resume" message to the SGSN. Ho
acknowledge the resume through a 'Resume NACK"

5. The BSS sens an RR message 'Channel Release" to the UE, indicating that the BSS fails to reque

6. The UE sends a 'Routing Area Update Request" message to the SGSN to resume the GPRS serv

>>Inter-RAT HO Algorithm and related

parameters

For a UE in Cell_DCH state using both CS and PS domain services,the inter-RAT handover procedu
the inter-RAT handover from UTRA RRC Connected Mode to GSM Connected Mode first. After the U
towards the GPRS to suspend the GPRS services. After the CS domain services are released on the
completed.

if the inter-RAT handover from UTRA RCC Conencted Mode to GSM Connected Mode succeeds,the
case of inter-RAT handover failure, the UE may go back to the UTRA RRC Connected Mode and re-e

The signalling procedures are described as follows,

1. The UE in connection with both CS and PS domain perrforms the UMTS to GSM handover during

2. The UE sends a suspend message to the BSS

3. The BSS forwards the 'Suspend" message to the SGSN. The SGSN returns a "Suspend Ack" mes

4. When the CS connection is terminated , the BSS may send a 'Resume" message to the SGSN. Ho
acknowledge the resume through a 'Resume NACK"

5. The BSS sens an RR message 'Channel Release" to the UE, indicating that the BSS fails to reque
1. The UE in connection with both CS and PS domain perrforms the UMTS to GSM handover during

2. The UE sends a suspend message to the BSS

3. The BSS forwards the 'Suspend" message to the SGSN. The SGSN returns a "Suspend Ack" mes

4. When the CS connection is terminated , the BSS may send a 'Resume" message to the SGSN. Ho
acknowledge the resume through a 'Resume NACK"

5. The BSS sens an RR message 'Channel Release" to the UE, indicating that the BSS fails to reque

6. The UE sends a 'Routing Area Update Request" message to the SGSN to resume the GPRS serv
es,the inter-RAT handover procedure is based on the measurement reports from the UE but is initiated from the UTRAN. The UE perform
M Connected Mode first. After the UE sends a handover complete message to the GSM/BSS, the UE initiates a temporary block flow (TB
omain services are released on the GSM side, the inter-RAT handover in the PS domain resumes, which indicates that the handover is

SM Connected Mode succeeds,the handover is regards as successful.no matter whether the UE inititates a TBF towards the GPRS or n
RA RRC Connected Mode and re-establish the connection in the original state.

he UMTS to GSM handover during which the CS service is handed over to the GSM

GSN sends a "SRNS Context Request" message to the SRNS, requesting the SRNS to stop sending downlink PDUs. After receiving th
GSN with an 'SRNS Context Response" messge. The SGSN returns a "Suspend Ack" message to the BSS

Resume" message to the SGSN. However,resume is impossible since the radio access system has changed. Therefore,the SGSN

dicating that the BSS fails to request the SGSN to resume the GPRS service for the UE

e SGSN to resume the GPRS service. The update mode depends on the network operation mode in use.

es,the inter-RAT handover procedure is based on the measurement reports from the UE but is initiated from the UTRAN. The UE perform
M Connected Mode first. After the UE sends a handover complete message to the GSM/BSS, the UE initiates a temporary block flow (TB
omain services are released on the GSM side, the inter-RAT handover in the PS domain resumes, which indicates that the handover is

SM Connected Mode succeeds,the handover is regards as successful.no matter whether the UE inititates a TBF towards the GPRS or n
RA RRC Connected Mode and re-establish the connection in the original state.

he UMTS to GSM handover during which the CS service is handed over to the GSM

GSN returns a "Suspend Ack" message to the BSS

Resume" message to the SGSN. However,resume is impossible since the radio access system has changed. Therefore,the SGSN

dicating that the BSS fails to request the SGSN to resume the GPRS service for the UE
d from the UTRAN. The UE performs
nitiates a temporary block flow (TBF)
ich indicates that the handover is

ates a TBF towards the GPRS or not. In

downlink PDUs. After receiving the

e BSS

anged. Therefore,the SGSN

use.

d from the UTRAN. The UE performs

nitiates a temporary block flow (TBF)
ich indicates that the handover is

ates a TBF towards the GPRS or not. In

anged. Therefore,the SGSN

Click to return to main page

L3 Messages - Intra-Frequency Har

UE SRNC

SRNS Static Relocation (UE not-i

7. RRC:UTRAN Mobility Information

8. RRC:UTRAN Mobility Information Confirm

9. RRC:UE Capability Enquiry (DCCH)

10. RRC:UE Capability Information (DCCH)

11. RRC:UE Capability Information Confirm (DCCH)

 Click to return to main page

L3 Messages - Intra-Frequency Har

UE SRNC

SRNS Relocation with Cell/URA Update (U

1. Cell Update/URA Update

Cell
Update/
URA
Update
Cell
Update/
URA
Update

9. RRC:Cell Update Confirm/URA Update Confirm

10. RRC:Physical Channel Reconfiguration Complete/UTRAN Mobility Information Co

11. RRC:UE Capability Enquiry (DCCH)

12. RRC:UE Capability Information (DCCH)

13. RRC:UE Capability Information Confirm (DCCH)

Note the following information about the procedure :

1.The DRNC acquires the SRNC ID of the UE from the URNTI IE in the CELL UPDATEmessag
INDICATION messageto the SRNC to indicate that the UE requests a cell update.

2.To initiate a cell update, the UE sends a CELL UPDATE message to the DRNC. To initiate a U

3.After a successful cell update, the DRNC sends a CELL UPDATE CONFIRM message tothe
UPDATE CONFIRM message to the UE.

4.After receiving the CELL UPDATE CONFIRM or URA UPDATE CONFIRM messagefrom the
RECONFIGURATION COMPLETE message (for the cell update) or a UTRAN MOBILITY INFO
This response from the UE is optional.
 Click to return to main page

L3 Messages - Intra-Frequency Har

UE SRNC

SRNS Relocation with Hard Handover

7.RRC:Physical Channel
Physical Reconfiguration
Channel
Reconfig

9. RRC:Physical Channel Reconfiguration Complete

9. RRC:UE Capability Enquiry (DCCH)

10. RRC:UE Capability Information (DCCH)

11. RRC:UE Capability Information Confirm (DCCH)

Note the following information about the procedure :

1.During the relocation with hard handover, if an RAB supporting lossless SRNS reloca
PDCP sequence numbers to the DRNC through the FORWARD SRNS CONTEXT me

2.After receiving a RADIO LINK RESTORE INDICATION message from the NodeB, th

3.If the DRNC does not obtain the information about the UE capability, the DRNC initia
3 Messages - Intra-Frequency Hard Handover Procedure
DRNC

SRNS Static Relocation (UE not-involved relocation)

1.RANAP: Relocation Required

2.RANAP Relocation Request

3.RANAP Relocation Request Ack

4.RANAP: Relocation Command

5. RNSAP: Relocation Commit

6. RANAP:Relocation Detect

UTRAN Mobility Information

UTRAN mobility information
AN Mobility Information Confirm

E Capability Enquiry (DCCH)

E Capability Information (DCCH) UE capability enquiry

pability Information Confirm (DCCH)

12. Relocation Complete

13. RANAP: Iu Release Command

14. RANAP: Iu Release Complete

3 Messages - Intra-Frequency Hard Handover Procedure
DRNC

RNS Relocation with Cell/URA Update (UE not-involved relocation)

ell Update/URA Update

2. RNSAP: Signalling Transfer Indication

3RANAP: Relocation Required

 4.RANAP Relocation Request

5.RANAP Relocation Request Ack

6.RANAP: Relocation Command

7. RNSAP: Relocation Commit

8. RANAP:Relocation Detect

date Confirm/URA Update Confirm

guration Complete/UTRAN Mobility Information Confirm

UE Capability Enquiry (DCCH)

E Capability Information (DCCH) UE capability enquiry

pability Information Confirm (DCCH)

14. Relocation Complete

15. RANAP: Iu Release Command

16. RANAP: Iu Release Complete

rocedure :
E from the URNTI IE in the CELL UPDATEmessage and then sends an UPLINK SIGNALLING TRANSFER
e that the UE requests a cell update.

LL UPDATE message to the DRNC. To initiate a URA update, the UE sends a URA UPDATE message to the DRNC.

ends a CELL UPDATE CONFIRM message tothe UE. After a successful URA update, the DRNC sends a URA

M or URA UPDATE CONFIRM messagefrom the DRNC, the UE can send a PHYSICAL CHANNEL
(for the cell update) or a UTRAN MOBILITY INFORMATION CONFIRM message (for the URA update) to the DRNC.
3 Messages - Intra-Frequency Hard Handover Procedure
DRNC

SRNS Relocation with Hard Handover(UE involved relocation)

1.RANAP: Relocation Required

2.RANAP: Relocation Request

3.RANAP: Relocation Request Ack

4.RANAP: Relocation Command

5.RANAP: Forward SRNS Context

6.RANAP: Forward SRNS Context

8. RANAP:Relocation Detect

Channel Reconfiguration Complete

E Capability Enquiry (DCCH)

E Capability Information (DCCH) UE capability enquiry

pability Information Confirm (DCCH)

12. Relocation Complete

13. RANAP: Iu Release Command

14. RANAP: Iu Release Complete

out the procedure :

ndover, if an RAB supporting lossless SRNS relocation is available on the Iu-PS interface, the SRNC sends the GTP-U and
NC through the FORWARD SRNS CONTEXT message. The sequence numbers are required for data forwarding.

TORE INDICATION message from the NodeB, theDRNC sends a RELOCATION DETECT message to the CN.

formation about the UE capability, the DRNC initiatesa UE capability enquiry procedure.
 >>SRNC Relocation Algorithm and related
parameters

CN The relocation preparation procedure can be trig

->During an SRNS relocation, the SRNC sends a
->During an inter-RAT CS handover from WCDMA

The procedure is described as follows:

Relocation Preparation
Relocation Resource Allocation
1.The SRNC sends a RELOCATION REQUIRED
cause, source PLMN, source LAC,source SAC, ta
2.The CN interacts with the target RNC or the targ
3.The CN sends a response message to the SRN
when thepreparation is complete. The message c
the resources partially or totally fail
to be allocated, the CN sends a RELOCATIONPR

The relocation resource allocation procedure ca

->During an SRNS relocation, the CN applies for r
->During an inter-RAT CS handover from GSM to

The procedure is described as follows:

1.The CN sends a RELOCATION REQUEST mes
integrity protection, Iu signaling connection ID, han
2.The target RNC allocates radio resources for the
Relocation Commit
3.The target RNC sends a response message to t
resources and otherparameters allocated to the U
encryption algorithm, and chosen integrity protecti
some reason, the target RNC sends a RELOCATI

The relocation commit procedure is performed

Iu release The procedure is described as follows:

1.The SRNC sends a RELOCATION COMMIT me
the GTP-U and PDCP sequence numbers require
2.The DRNC sends a RELOCATION DETECT me
3.The original DRNC sends a RELOCATION COM

The UTRAN mobility information procedure is p

to a UE or to inform the UE of mobility-related info

The procedure is described as follows:

1.The SRNC sends a UTRAN MOBILITY INFORM
2.The UE starts to update the related fields accord
3.The UE sends a response message to the SRN

->If the UE succeeds in conducting the operations

->If the UE fails to conduct the operations specifie
cause.
 The procedure is described as follows:
1.The SRNC sends a UTRAN MOBILITY INFORM
2.The UE starts to update the related fields accord
3.The UE sends a response message to the SRN

->If the UE succeeds in conducting the operations

->If the UE fails to conduct the operations specifie
cause.

The UE capability enquiry procedure is performe

on the UE capability.

The procedure is described as follows:

1.The SRNC sends a UE CAPABILITY ENQUIRY
2.The UE sends a UE CAPABILITY INFORMATIO
3.The SRNC reads the UE capability information a

The Iu release procedure can be triggered in one

->The transaction between the UE and the CN is c
->The UTRAN requests the CN to release the res
->The Serving Radio Network Subsystem (SRNS)
->The SRNS relocation is canceled after a relocat

The procedure is described as follows:

1.The CN sends an IU RELEASE COMMAND me
sending the IU RELEASE COMMAND message, t

2.The SRNC releases the related UTRAN resourc

Click to return to main page

CN
The relocation preparation procedure can be trig
->During an SRNS relocation, the SRNC sends a
->During an inter-RAT CS handover from WCDMA

The procedure is described as follows:

1.The SRNC sends a RELOCATION REQUIRED
target PLMN, and target LAC
2.The CN interacts with the target RNC or the targ
3.The CN sends a response message to the SRN
when thepreparation is complete. The message c
the resources partially or totally fail to be allocated
 Relocation Preparation

Relocation Resource Allocation

The relocation resource allocation procedure ca
->During an SRNS relocation, the CN applies for r
->During an inter-RAT CS handover from GSM to

The procedure is described as follows:

1.The CN sends a RELOCATION REQUEST mes
integrity protection, Iu signaling connection ID, han
2.The target RNC allocates radio resources for the
3.The target RNC sends a response message to t
resources and otherparameters allocated to the U
include the UTRAN Radio NetworkTemporary Ide
, and chosen integrity protection algorithm.lIf the r
some reason, the target RNC sends a RELOCAT
Relocation Commit

The cell update procedure is performed to update

the RRC connection, switching the status of the R

The cell update procedure can be triggered in one

transmission and RLC unrecoverable error

Iu release The procedure is described as follows:

1.The UE sends a CELL UPDATE message to the
2.The RNC sends a CELL UPDATE CONFIRM m
bearers.
3.According to related IEs in the received messag
->UTRAN MOBILITY INFORMATION CONFIRM
->PHYSICAL CHANNEL RECONFIGURATION CO
->TRANSPORT CHANNEL RECONFIGURATION
->RADIO BEARER RECONFIGURATION COMPL
->RADIO BEARER RELEASE COMPLETE

The URA update procedure is performed to upda

of the following conditions:URA reselection or Per

The procedure is described as follows:

1.The UE sends a URA UPDATE message to the
2.The RNC sends a URA UPDATE CONFIRM me
3.The UE responds optionally. If there is a respon

The relocation commit procedure is performed

The procedure is described as follows:

The relocation commit procedure is performed

The procedure is described as follows:

1.The SRNC sends a RELOCATION COMMIT me
the GTP-U and PDCP sequence numbers require
2.The DRNC sends a RELOCATION DETECT me
3.The original DRNC sends a RELOCATION COM

The UTRAN mobility information procedure is p

to a UE or to inform the UE of mobility-related info

The procedure is described as follows:

1.The SRNC sends a UTRAN MOBILITY INFORM
2.The UE starts to update the related fields accord
3.The UE sends a response message to the SRN

->If the UE succeeds in conducting the operations

->If the UE fails to conduct the operations specifie
cause.

The UE capability enquiry procedure is performe

on the UE capability.

The procedure is described as follows:

1.The SRNC sends a UE CAPABILITY ENQUIRY
2.The UE sends a UE CAPABILITY INFORMATIO
3.The SRNC reads the UE capability information a

The Iu release procedure can be triggered in one

->The transaction between the UE and the CN is c
->The UTRAN requests the CN to release the res
->The Serving Radio Network Subsystem (SRNS)
->The SRNS relocation is canceled after a relocat

The procedure is described as follows:

1.The CN sends an IU RELEASE COMMAND me
sending the IU RELEASE COMMAND message, t

2.The SRNC releases the related UTRAN resourc

 Click to return to main page
CN The relocation preparation procedure can be trig
->During an SRNS relocation, the SRNC sends a
->During an inter-RAT CS handover from WCDMA

The procedure is described as follows:

Relocation Preparation
Relocation Resource Allocation
1.The SRNC sends a RELOCATION REQUIRED
target PLMN, and target LAC
2.The CN interacts with the target RNC or the targ
3.The CN sends a response message to the SRN
when thepreparation is complete. The message c
the resources partially or totally fail to be allocated

The relocation resource allocation procedure ca

->During an SRNS relocation, the CN applies for r
->During an inter-RAT CS handover from GSM to

The procedure is described as follows:

1.The CN sends a RELOCATION REQUEST mes
CN domain indicator, target cellidentifier, encryptio
2.The target RNC allocates radio resources for the
3.The target RNC sends a response message to t
Relocation Commit
REQUESTACKNOWLEDGE message. The mess
include the UTRAN Radio NetworkTemporary Ide
and chosen integrity protection algorithm.lIf the re
some reason, the target RNC sends a RELOCATI

The relocation commit procedure is performed to

Iu release
The procedure is described as follows:
1.When an RAB supporting lossless SRNS reloca
message to the SGSN to ask the SGSN totransfe
2.After receiving the FORWARD SRNS CONTEXT
3.The UE is handed over from the SRNC to the D
RESTORE INDICATIONmessage from the NodeB
4.The original DRNC sends a RELOCATION COM
the GTP-U and
arding.

CN.

The physical channel reconfiguration procedur

The procedure is described as follows:

1.The SRNC sends a PHYSICAL CHANNEL REC
2.The UE saves the IEs of the UE, Radio Bearer (
3.The UE sends a response message to the SRN
->If successfully reconfiguring the physical channe
message on the uplink DCCH by using AM RLC.
->If failing to reconfigure the physical channels sp
The physical channel reconfiguration procedur

The procedure is described as follows:

1.The SRNC sends a PHYSICAL CHANNEL REC
2.The UE saves the IEs of the UE, Radio Bearer (
3.The UE sends a response message to the SRN
->If successfully reconfiguring the physical channe
message on the uplink DCCH by using AM RLC.
->If failing to reconfigure the physical channels sp
sends a PHYSICAL CHANNEL RECONFIGURAT
RECONFIGURATION FAILURE message is "phys

The UE capability enquiry procedure is performe

on the UE capability.

The procedure is described as follows:

1.The SRNC sends a UE CAPABILITY ENQUIRY
2.The UE sends a UE CAPABILITY INFORMATIO
3.The SRNC reads the UE capability information a

The Iu release procedure can be triggered in one

->The transaction between the UE and the CN is c
->The UTRAN requests the CN to release the res
->The Serving Radio Network Subsystem (SRNS)
->The SRNS relocation is canceled after a relocat

The procedure is described as follows:

1.The CN sends an IU RELEASE COMMAND me
sending the IU RELEASE COMMAND message, t

2.The SRNC releases the related UTRAN resourc

on preparation procedure can be triggered in either of the following conditions:
SRNS relocation, the SRNC sends a RELOCATION REQUIRED message.
nter-RAT CS handover from WCDMA to GSM, the SRNC sends aRELOCATION REQUIRED message.

ure is described as follows:

sends a RELOCATION REQUIRED message to the CN. The message containscertain information such as relocation type, relocation
ce PLMN, source LAC,source SAC, target PLMN, and target LAC
eracts with the target RNC or the target network system, such as the GSMsystem, to prepare relevant resources.
nds a response message to the SRNC.lIf the target RNC or the target network system prepares the relevant resourcessuccessfully, the
paration is complete. The message contains the L3 information IE, which carries theinformation about the relevant resources allocated b
s partially or totally fail
ed, the CN sends a RELOCATIONPREPARATION FAILURE message.

on resource allocation procedure can be triggered in either of the following conditions:

SRNS relocation, the CN applies for resources from the target RNC
nter-RAT CS handover from GSM to WCDMA, the CN applies for resourcesfrom the target RNC

ure is described as follows:

nds a RELOCATION REQUEST message to the target RNC. The messagecontains certain information, such as the IMSI of the UE, CN
ection, Iu signaling connection ID, handover cause, and RAB parameters.
RNC allocates radio resources for the relocation.
RNC sends a response message to the CN.lIf the resources are allocated, the target RNC sends a RELOCATION REQUESTACKNOW
d otherparameters allocated to the UE. The parameters include the UTRAN Radio NetworkTemporary Identifier (U-RNTI), RAB, transpo
gorithm, and chosen integrity protection algorithm.lIf the resources partially or totally fail to be allocated or the target RNC rejects the SR
, the target RNC sends a RELOCATION FAILURE message,indicating the failure cause.

on commit procedure is performed to execute the change of control from the SRNCof a UE to the DRNC

ure is described as follows:

sends a RELOCATION COMMIT message to the DRNC. If an RAB supportinglossless SRNS relocation is available on the Iu-PS interf
nd PDCP sequence numbers required for data forwarding.Then, the SRNC initiates data forwarding.
sends a RELOCATION DETECT message to the CN to notify the CN of thedetection of the relocation commitment.
l DRNC sends a RELOCATION COMPLETE message to the CN to notify thatthe relocation is successful.

mobility information procedure is performed for the network to allocate a newUTRAN Radio Network Temporary Identifier (U-RNTI) or
inform the UE of mobility-related information such as timer values and CN domainrelated information.

ure is described as follows:

sends a UTRAN MOBILITY INFORMATION message to the UE
rts to update the related fields according to the values of the IEs carried in themessage.
nds a response message to the SRNC.

ucceeds in conducting the operations specified by the UTRAN MOBILITYI NFORMATION message, the UE sends a UTRAN MOBILITY
ails to conduct the operations specified by the UTRAN MOBILITYINFORMATION message, the UE sends a UTRAN MOBILITY INFORM
ability enquiry procedure is performed to request a UE to transmit its capabilityinformation related to any radio access network so that
pability.

ure is described as follows:

sends a UE CAPABILITY ENQUIRY message to the UE through the downlink DCCH using AM RLC.
nds a UE CAPABILITY INFORMATION message to the SRNC through theuplink DCCH using AM or UM RLC. The message contains th
reads the UE capability information and then sends a UE CAPABILITYINFORMA CONFIRM message to the UE through the downlink D

se procedure can be triggered in one of the following conditions:

ction between the UE and the CN is complete.
N requests the CN to release the resources on the Iu interface by, for example,sending an IU RELEASE REQUEST message.
g Radio Network Subsystem (SRNS) is relocated.
relocation is canceled after a relocation resource allocation procedure iscomplete.

ure is described as follows:

nds an IU RELEASE COMMAND message to the SRNC to initiate the Iu releaseprocedure. The message indicates the cause for the re
U RELEASE COMMAND message, the CN will not send further RANAPconnection-oriented messages on this particular connection.

releases the related UTRAN resources and then sends an IU RELEASE COMPLETE message to the CN.

on preparation procedure can be triggered in either of the following conditions:

SRNS relocation, the SRNC sends a RELOCATION REQUIRED message.
nter-RAT CS handover from WCDMA to GSM, the SRNC sends aRELOCATION REQUIRED message.

ure is described as follows:

sends a RELOCATION REQUIRED message to the CN. The message containscertain information such as relocation type, relocation c
, and target LAC
eracts with the target RNC or the target network system, such as the GSMsystem, to prepare relevant resources.
nds a response message to the SRNC.lIf the target RNC or the target network system prepares the relevant resourcessuccessfully, the
paration is complete. The message contains the L3 information IE, which carries theinformation about the relevant resources allocated b
s partially or totally fail to be allocated, the CN sends a RELOCATIONPREPARATION FAILURE message.
on resource allocation procedure can be triggered in either of the following conditions:
SRNS relocation, the CN applies for resources from the target RNC
nter-RAT CS handover from GSM to WCDMA, the CN applies for resourcesfrom the target RNC

ure is described as follows:

nds a RELOCATION REQUEST message to the target RNC. The messagecontains certain information, such as the IMSI of the UE, CN
ection, Iu signaling connection ID, handover cause, and RAB parameters.
RNC allocates radio resources for the relocation.
RNC sends a response message to the CN.lIf the resources are allocated, the target RNC sends a RELOCATION REQUESTACKNOW
d otherparameters allocated to the UE. The parameters
UTRAN Radio NetworkTemporary Identifier (U-RNTI), RAB, transport layer and physical layer information,chosen encryption algorithm
integrity protection algorithm.lIf the resources partially or totally fail to be allocated or the target RNC rejects the SRNSrelocation for
n, the target RNC sends a RELOCATION FAILURE message,indicating the failure cause.

ate procedure is performed to update the UE-related information on the UTRANside when the location of a UE changes. In addition, th
nection, switching the status of the RRC connection, reporting errors,and transferring information

ate procedure can be triggered in one of the following conditions:Cell reselection,Re-entering the service area,Periodical cell updatelRad
and RLC unrecoverable error

ure is described as follows:

nds a CELL UPDATE message to the RNC. The message contains the information such as the Serving RNC Radio Network Temporary
ends a CELL UPDATE CONFIRM message to the UE. The message containsthe information such as the U-RNTI and the IEs about the

o related IEs in the received message, the UE may respond with messages ornot. If the UE responds, the message can be one of the f
OBILITY INFORMATION CONFIRM
CHANNEL RECONFIGURATION COMPLETE
RT CHANNEL RECONFIGURATION COMPLETE
ARER RECONFIGURATION COMPLETE
ARER RELEASE COMPLETE

date procedure is performed to update the URA-related location information on thenetwork side when the location of a UE changes. Th
ng conditions:URA reselection or Periodical URA update

ure is described as follows:

nds a URA UPDATE message to the RNC to initiate the URA update. The message contains the cause for the URA update and the IEs
ends a URA UPDATE CONFIRM message to the UE. The message containsthe new C-RNTI and U-RNTI or the information about the
sponds optionally. If there is a response, the UE sends a UTRAN MOBILITY INFORMATION CONFIRM message to the RNC after takin

on commit procedure is performed to execute the change of control from the SRNCof a UE to the DRNC

ure is described as follows:

mobility information procedure is performed for the network to allocate a newUTRAN Radio Network Temporary Identifier (U-RNTI) or
inform the UE of mobility-related information such as timer values and CN domainrelated information.

ure is described as follows:

sends a UTRAN MOBILITY INFORMATION message to the UE
rts to update the related fields according to the values of the IEs carried in themessage.
nds a response message to the SRNC.

ucceeds in conducting the operations specified by the UTRAN MOBILITYI NFORMATION message, the UE sends a UTRAN MOBILITY
ails to conduct the operations specified by the UTRAN MOBILITYINFORMATION message, the UE sends a UTRAN MOBILITY INFORM

ability enquiry procedure is performed to request a UE to transmit its capabilityinformation related to any radio access network so that
pability.

ure is described as follows:

sends a UE CAPABILITY ENQUIRY message to the UE through the downlink DCCH using AM RLC.
nds a UE CAPABILITY INFORMATION message to the SRNC through theuplink DCCH using AM or UM RLC. The message contains th
reads the UE capability information and then sends a UE CAPABILITYINFORMA CONFIRM message to the UE through the downlink D

se procedure can be triggered in one of the following conditions:

ction between the UE and the CN is complete.
N requests the CN to release the resources on the Iu interface by, for example,sending an IU RELEASE REQUEST message.
g Radio Network Subsystem (SRNS) is relocated.
relocation is canceled after a relocation resource allocation procedure iscomplete.

ure is described as follows:

nds an IU RELEASE COMMAND message to the SRNC to initiate the Iu releaseprocedure. The message indicates the cause for the re
U RELEASE COMMAND message, the CN will not send further RANAPconnection-oriented messages on this particular connection.

releases the related UTRAN resources and then sends an IU RELEASE COMPLETE message to the CN.
on preparation procedure can be triggered in either of the following conditions:
SRNS relocation, the SRNC sends a RELOCATION REQUIRED message.
nter-RAT CS handover from WCDMA to GSM, the SRNC sends aRELOCATION REQUIRED message.

ure is described as follows:

sends a RELOCATION REQUIRED message to the CN. The message containscertain information such as relocation type, relocation c
, and target LAC
eracts with the target RNC or the target network system, such as the GSMsystem, to prepare relevant resources.
nds a response message to the SRNC.lIf the target RNC or the target network system prepares the relevant resourcessuccessfully, the
paration is complete. The message contains the L3 information IE, which carries theinformation about the relevant resources allocated b
s partially or totally fail to be allocated, the CN sends a RELOCATIONPREPARATION FAILURE message.

on resource allocation procedure can be triggered in either of the following conditions:

SRNS relocation, the CN applies for resources from the target RNC
nter-RAT CS handover from GSM to WCDMA, the CN applies for resourcesfrom the target RNC

ure is described as follows:

nds a RELOCATION REQUEST message to the target RNC. The messagecontains certain information, such as the IMSI of the UE,
ndicator, target cellidentifier, encryption, integrity protection, Iu signaling connection ID, handover cause, and RAB parameters.
RNC allocates radio resources for the relocation.
RNC sends a response message to the CN.lIf the resources are allocated, the target RNC sends a RELOCATION
CKNOWLEDGE message. The message contains the radio resources and otherparameters allocated to the UE. The parameters
UTRAN Radio NetworkTemporary Identifier (U-RNTI), RAB, transport layer and physical layer information,chosen encryption algorithm,
ntegrity protection algorithm.lIf the resources partially or totally fail to be allocated or the target RNC rejects the SRNSrelocation for
, the target RNC sends a RELOCATION FAILURE message,indicating the failure cause.

on commit procedure is performed to execute the change of control from the SRNCof a UE to the DRNC.

ure is described as follows:

RAB supporting lossless SRNS relocation is available on the Iu-PS interface, theSRNC sends a FORWARD SRNS CONTEXT
he SGSN to ask the SGSN totransfer the GTP-U and PDCP sequence numbers to the DRNC. The sequence numbers arerequired for d
ving the FORWARD SRNS CONTEXT message, the SGSN forwards themessage to the DRNC.
handed over from the SRNC to the DRNC through a physical channelreconfiguration procedure. After receiving a RADIO LINK
NDICATIONmessage from the NodeB, the DRNC sends a RELOCATION DETECT message to theCN.
l DRNC sends a RELOCATION COMPLETE message to the CN to notify thatthe relocation is successful.

l channel reconfiguration procedure is performed to set up, reconfigure, or releasea physical channel.

ure is described as follows:

sends a PHYSICAL CHANNEL RECONFIGURATION message to the UE to request reconfiguration of a physical channel.
ves the IEs of the UE, Radio Bearer (RB), transport channel, and physical channel.
nds a response message to the SRNC.
ully reconfiguring the physical channels specified by the PHYSICALCHANNEL RECONFIGURATION message, the UE sends a PHYSIC
the uplink DCCH by using AM RLC.
reconfigure the physical channels specified by the PHYSICAL CHANNELRECONFIGURATION message, the UE restores the configura
ability enquiry procedure is performed to request a UE to transmit its capabilityinformation related to any radio access network so that
pability.

ure is described as follows:

sends a UE CAPABILITY ENQUIRY message to the UE through the downlink DCCH using AM RLC.
nds a UE CAPABILITY INFORMATION message to the SRNC through theuplink DCCH using AM or UM RLC. The message contains th
reads the UE capability information and then sends a UE CAPABILITYINFORMA CONFIRM message to the UE through the downlink D

se procedure can be triggered in one of the following conditions:

ction between the UE and the CN is complete.
N requests the CN to release the resources on the Iu interface by, for example,sending an IU RELEASE REQUEST message.
g Radio Network Subsystem (SRNS) is relocated.
relocation is canceled after a relocation resource allocation procedure iscomplete.

ure is described as follows:

nds an IU RELEASE COMMAND message to the SRNC to initiate the Iu releaseprocedure. The message indicates the cause for the re
U RELEASE COMMAND message, the CN will not send further RANAPconnection-oriented messages on this particular connection.

releases the related UTRAN resources and then sends an IU RELEASE COMPLETE message to the CN.
 e.

uch as relocation type, relocation

resources.
elevant resourcessuccessfully, the CN sends a RELOCATION COMMAND message
the relevant resources allocated by the target RNC or the targetnetwork system.lIf

on, such as the IMSI of the UE, CN domain indicator, target cellidentifier, encryption,

ELOCATION REQUESTACKNOWLEDGE message. The message contains the radio

y Identifier (U-RNTI), RAB, transport layer and physical layer information,chosen
d or the target RNC rejects the SRNSrelocation for

RNC

ion is available on the Iu-PS interface, the RELOCATION COMMITmessage carries

n commitment.
sful.

k Temporary Identifier (U-RNTI) or Cell Radio Network TemporaryIdentifier (C-RNTI)

n.

he UE sends a UTRAN MOBILITY INFORMATIONCONFIRM message.

nds a UTRAN MOBILITY INFORMATIONFAILURE message, indicating the failure
any radio access network so that the network can perform dataconfiguration based

UM RLC. The message contains the information about UE capabilities.

e to the UE through the downlink DCCH using AM or UMRLC.

SE REQUEST message.

sage indicates the cause for the release of the signaling connection. NOTE After
es on this particular connection.

e CN.

e.

uch as relocation type, relocation cause, source PLMN, source LAC,source SAC,

resources.
elevant resourcessuccessfully, the CN sends a RELOCATION COMMAND message
the relevant resources allocated by the target RNC or the targetnetwork system.lIf
age.
on, such as the IMSI of the UE, CN domain indicator, target cellidentifier, encryption,

ELOCATION REQUESTACKNOWLEDGE message. The message contains the radio

ion,chosen encryption algorithm

rejects the SRNSrelocation for

n of a UE changes. In addition, the cell update procedure takes the role ofmonitoring

ce area,Periodical cell updatelRadio link failure,Paging response,Uplink data

ng RNC Radio Network Temporary Identifier (S-RNTI) andthe SRNC ID.

the U-RNTI and the IEs about the transport channels, physicalchannels, and radio

, the message can be one of the following messages:

the location of a UE changes. The URA update procedure can be triggered in either

e for the URA update and the IEs such as the U-RNTI.
RNTI or the information about the new ciphering and integrityprotection modes.
M message to the RNC after taking the new parameters intoeffect.

RNC
k Temporary Identifier (U-RNTI) or Cell Radio Network TemporaryIdentifier (C-RNTI)
n.

he UE sends a UTRAN MOBILITY INFORMATIONCONFIRM message.

nds a UTRAN MOBILITY INFORMATIONFAILURE message, indicating the failure

any radio access network so that the network can perform dataconfiguration based

UM RLC. The message contains the information about UE capabilities.

e to the UE through the downlink DCCH using AM or UMRLC.

SE REQUEST message.

sage indicates the cause for the release of the signaling connection. NOTE After
es on this particular connection.

e CN.
 e.

uch as relocation type, relocation cause, source PLMN, source LAC,source SAC,

resources.
elevant resourcessuccessfully, the CN sends a RELOCATION COMMAND message
the relevant resources allocated by the target RNC or the targetnetwork system.lIf
age.

on, such as the IMSI of the UE,

se, and RAB parameters.

ELOCATION
to the UE. The parameters
ion,chosen encryption algorithm,
ejects the SRNSrelocation for

RNC.

WARD SRNS CONTEXT

equence numbers arerequired for data forwarding.

receiving a RADIO LINK

N.
sful.

el.

of a physical channel.

message, the UE sends a PHYSICAL CHANNELRE CONFIGURATION COMPLETE

age, the UE restores the configuration to the old physicalchannel configuration and
any radio access network so that the network can perform dataconfiguration based

UM RLC. The message contains the information about UE capabilities.

e to the UE through the downlink DCCH using AM or UMRLC.

SE REQUEST message.

sage indicates the cause for the release of the signaling connection. NOTE After
es on this particular connection.

e CN.
>>Cell Update Description