W-RNO AnalysisMate - V1.0

Developed By: Aumpika Viun (Ice)
Contact: aumpikav@yahoo.com
W-RNO AnalysisMate Ver1.0 Convention
0. UTRAN Network Architecture and Protocols Underline Text
1.1 UMTS Network Architecture MML Command
1.2 UTRAN Protocols Click to return to main page

1. RRC,RB and UE Measurement Procedures Value=
1.1 Mapping of UE state to 3GPP Specifications Comments
1.2 RRC Tasks and Functions
1.3 RRC Modes and State Transitions including GSM Tool Version
1.3 RRC Mode Description Ver1.0
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 Tool Version

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 related information
Underline Text
e.g. signalling procedure, signalling measages,parameter description, features algorithm etc.
MML Command All bold texts with highlighted in "Orange" are MML command
ick 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
Release Date Genex Probe Version RAN Version RNC Version
Version
V100R005C01B040 V100R005C01B040
25-Jun-09 10.0 V200R010C01B061
(V1.51 20090210 ) (V1.52 20090210 )
Change Type Change History 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) dom
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 rad
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 call
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 broadc
Examples of USIM data and procedures,
1.Data: International Mobile Subscriber Identity,Packet Switched Location Information,Security Information for authentication and chiphering
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 UE‘s ac
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 and
interface and to the PS domain via Iu(PS) interface. Signalling and data transfer to other RNCs are possible via Iur interface and to the conn
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-RN
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 R
handles all higher layer functions related to radio access and information transport through UTRAN. The S-RNC performs the following func
- 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 or
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 sign
(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 t
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 no
- 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 or
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 sign
(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 t
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 no
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 S
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 usag
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 combinin
,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 implementing a UMTS radio tran
serviced by a Node B. Generally,up to six cells are serviced by
A Node B can be used for Frequency Division Duplex (Uplin

Downlink in different timeslots) or dual mode operation. A No
interface,and in the opposite direction. Node Bs are involved in
the value with a predefined one and instructs the UE to contro
determines the Frame Error Rate (FER). The following are ex
- Radio Channel functions: Transport to physical channel ma

- Air Interface management. Controlling Uplink and Downlink
Intra NodeB SofterHO,Power Control,Quality and signal streng
- O&M Processing,Interfacing with M2000 and RNC for alarm
- Cellular Transmission management. Managing ATM switch
of the physical transmission interfaces – E1, PDH, SDH or mi
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 Na
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 Na
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 Natio
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 is
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)
ITU-T E212.
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 Routing
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
length of the IMSI is less than 15 digits
- 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
VLR. The TMSI consists of 4 bytes, which are operator-dependent.
- 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) consis
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 ch
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 us
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 us
UTRAN Protocols
The communication between the different dom
links between UE and UTRAN and transport of
of signalling between UE,UTRAN and CN as fo
1. Access Stratum(AS) : The Access Stratum

messages occur between UE and UTRAN and
UTRAN and UTRAN-CN is ,that the UTRAN-C
enables the CN to support several different rad
2. Transport Stratum: The Transport Stratum

and user data. Because UTRAN has the task t
messages between UE and UTRAN and betwe
3. Non-Access Stratum (NAS) : The Non-Acc

access or transport tasks.This cover pure appli
,handling of subscription data and subscriber s
UTRAN Protocol Architecture

The UMTS network is split into the CN,UTRAN and the UE. CN
(radio access bearer services) and control information (includin
between the CN and the UEs using the Radio protocols and th
The higher layer protocols of the Non-Access Stratum(NAS) h

Session Manangement (SM) tasks. The NAS procedures (of R
procedures. The radio and Iu protocols contain mechanism for
used in the Iu and radio protocols for these these transparent N
UTRAN Interface Protocol Structure

Horizontal Layer The protocol structures of the UTRAN interfaces are designed
planes as logically independent of each other. The modularity
parts remain intact.
The transport system used within UTRAN is ATM. There is diff

different types of bearer service labelled AAL type 1,AAL type
AAL type2 can be set up with explicit signalling. This means be
corresponding ATM switches. This behavior results in a new pr
Horizontal Layer:
The general protocol model consists of two main horizontal lay
are visible in the Radio Network Layer only.The Transport Netw
specific requirements.
- Transport Network Layer : The Transport Network Layer co
layer and its transport frame layer,also the bearer service proto
- Radio Network Layer : The Radio Network Layer contains a
streams, to be transported through UTRAN, belong to this laye
Vertical Plane:
There is also a vertical structure, the elements of this vertical s
next to eachother. The general protocol model consists of thre
Plane.
Vertical Layer -User Plane: The user plane supports the data streams for us
protocols will be transmitted via data bearers. In contrast to the
explicit signalling.
-Control Plane: The control plane consists of all application p
application protocol,one or several signaling bearers,provided
signaling,which is UMTS-specific. It includes the Application P
Application Protocol messages.
-Transport Network Control Plane: The transport network co
protocols are used to set up and release the data bearers of th
not necessary to use the ALCAP for all data bearers. Expecial
are used. The Transport Network Control Plane is used for all
information.
The Transport Network Control Plane acts as plane between th

to be total independent of the technology selected for data bea
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 bea
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
messages. It contains of following important protocol layer as follows;
-Physical Layer (PHY) : The physical layer (Layer1) on the air interface provides access to the WCDMA radio interface. Therefore it perfor
-Medium Access Control (MAC) : The MAC protocol belongs to Layer 2. The tasks of MAC are the control of random access and the mult
-Radio Link Control (RLC) : As MAC also the RLC protocol is a Layer 2 protocol. RLC provides three reliabilty modes for every radio bear
-Radio Resource Control (RRC) : The RRC protocol is the first protocol of Layer 3. The RRC protocol performs all higher layer tasks relat
-NAS Protocols : On top of RRC there are the control protocols for the non-access stratum (NAS). For the CS service these are: MM (Mob
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.
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
messages. It contains of following important protocol layer as follows;
-Physical Layer (PHY) : The physical layer (Layer1) on the air interface provides access to the WCDMA radio interface. Therefore it perfor
-Medium Access Control (MAC) : The MAC protocol belongs to Layer 2. The tasks of MAC are the control of random access and the mult
-Radio Link Control (RLC) : As MAC also the RLC protocol is a Layer 2 protocol. RLC provides three reliabilty modes for every radio bear
-Radio Resource Control (RRC) : The RRC protocol is the first protocol of Layer 3. The RRC protocol performs all higher layer tasks relat
-NAS Protocols : On top of RRC there are the control protocols for the non-access stratum (NAS). For the CS service these are: MM (Mob
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 user
following protocols involved into the user data transport,
-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 used
-User data stream : The user data streams are generated by the applications using the CS core network services (switched channels). The
-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 chann
channel includes time stamps in the transport frames. This allows 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 stream
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 User 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
CS services.
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 desig
- 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 the
- NAS protocols : The only special protocols for the packet switched service are the non-access stratum protocols. Because there are esse
network has its own mobility managment GMM ( GPRS Mobility Management). To set up a data session the SM (Session Management) pro
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 netw
network this only data. But because of its special role, the network protocol of the external network is called Packet Data Protocol (PDP). I
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 addressing
-UDP/IP : To route from RNC to SGSN the standard UDP/IP protocol stack is used. This is a connection less unreliable transport service. In
-AAL5 /ATM : The UDP/IP datagrams (packets) are transmitted on ATM using the adaptaiton layer 5.
UTRAN Interface Protocol -Uu (UE-UTRAN)

Uu interface is the interface between User E
important interface in the UMTS system.
The radio interface (Uu) is layered into three

-the physical layer (L1)
-the data link layer (L2)
-the network layer (L3).
The layer 1 supports all functions required for

function consisting in indicating to higher layers
transmit power, … It is basically composed of a
“physical channel” entity.
The layer 2 protocol is responsible for providin

sublayers: MAC (Medium Access Control), RLC
Control).
The layer 3 is split into 2 parts: the access stra

Resource Control)” entity and “duplication avoi
L3 are implemented by RNC, and the MM and
The protocol layers are located in the UE an
Physical Layer (L1) Functions

Transport Channel Processing for FDD Uplink Transport
Transport Format
Format Combinations
Combinations
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 ca
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
performed afterwards
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 cha
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. Th
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
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 cha
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. Th
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 fas
3. Random Access Procedures : Like all known mobile radio access technologies also WCDMA has to use random access mechanism to
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 s
ratio,interference power,signal power). These measurment are used as criteria for the cell reselection or handover procedures. For the mea
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 Packet Data 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 channels
8. Switching of the transport channel type for a radio berarer(controlled by RRC),means several transport channel types
can be assigned to one radio bearer
9.Traffic volume measurement
10.Ciphering/de-chipering for transparent mode RLC
11. Control of random access and CPCH access (e.g. priority classes)
8. Switching of the transport channel type for a radio berarer(controlled by RRC),means several transport channel types
can be assigned to one radio bearer
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 contains the followin
-NBAP (NodeB Application Part) : The NBAP protocol is the

(e.g. code allocation,transceiver configuration).
-SAAL,AAL 5, ATM : These protocols constitute the signalling
The user plane of the Iub interface has to transfer the dow
way as on the Iur interface. The user plane consists of:
-Frame Protocols : The Frame Protocols encapsulate the UE

-AAL 2 ,ATM : The frame protocol,that encapsulate the UE da
up first
-AAL type 2 signaling protocol : The AAL type 2 SP provides
-STC, SAAL,AAL 5,ATM : The STC (Signaling Transport Con
The physical layer is not standardized. it is up to the opera
UTRAN Interface Protocol - Iur ( RNC-RNC)

The control plane of the Iur interface contains the followin
-RNSAP (Radio Network Subsystem Application Part) : The

covers resource allocation for a UE in a cell of the D-RNC,soft
(SRNS relocation)
- SCCP (Signaling Connection Control Part) : The SCCP is
the S-RNC sets up one SCCP signaling connection for every
signaling messages
-MTP 3B,SAAL,AAL5,ATM : These protocols form the signal
The user plane of the Iur interface has the tasks to transpo
following protocols
-Frame Protocols : The data to and from the UE will be encap

protocols allow traffic management with in-band signaling
-AAL 2 ,ATM : The frame protocol packets are transmitted via
-AAL type 2 signaling protocol : The AAL type 2 SP provides
-STC,MTP3B, SAAL,AAL 5,ATM : These protocols provide th
Converter) provides functionality for congestion handling and l
signaling bearer of RNSAP of Control Plane
UTRAN Interface Protocol - Iu ( UTRAN-CN)

The following protocol model is applied to the UTRAN interface
the PS-core network domain.
Iu-CS Protocol Stack
1. Iu-CS protocol stack
The control plane for Iu-CS is formed out of the following prot
-RANAP ( Radio Access Network Application Part) : The R
application protocol of the Iu-CS interface
-SCCP (Signaling Connection Control Part) : The SCCP is u
connection UTRAN-MSC for every IE using CS service.
-MTP 3B,SAAL,AAL5,ATM : Theses protocols provide the sig
The user plane on Iu-CS has to support the transfer of real tim
-Iu UP (User Plane) protocol : The Iu UP protocol is used to p
control,data rate control,backward error conrrection.
-AAL2,ATM : For the data bearer to transport the data stream
The transport network control plane is necessary ,because

network control plane consisting of:
-AAL type 2 signaling protocol : used to setup ,modify and r
-STC,MTP 3B,SAAL,AAL5,ATM : These protocols provide the
2. Iu-PS protocol stack
The Iu-PS interface is the interface between RNC and SGSN.
Iu-PS control plane
Iu-PS Protocol Stack -RANAP : The application protocol for Iu-CS and Iu-PS
-SCCP : Provides signaling connection on Iu-PS. There will be
service. SCCP connections on Iu-PS and Iu-CS do not affect e
-MTP 3B,SAAL,AAL5,ATM : The signaling bearer for SCCP/R
The user plane on Iu-PS is competely different to the user pla

necessary. The UTRAN provides the following protocols on the
-Iu UP protocol : As for Iu-CS the Iu UP protocol can provide
-GTP-U (GPRS Tunneling Protocol-User Plane): GTP-U pro
the PDP context and sequence numbers for the data are conta
-UDP/IP : The UDP/IP protocol suite is used as network layer
vice versa.
-AAL 5,ATM : The ATM adaptation layer of type 5 is used as b
The AAL 5 virtual channels do not need to be set up in a dynam
for the packet transfer. Therefore on Iu-PS there is no need fo
UMTS Protocol Stacks -> Application Part

RANAP
UMTS system has different application parts depending on interface being used and each application part controls signaling information for
signaling format, consisting each message of mandatory fixed 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 contr
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 broa
-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 log
management
-Dedicated NBAP : Sequence related to a specific UE signaling in the NodeB. Upon radio link setup procedure,the NodeB assigns a traffic
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 informa
2.Common Transport Channel Management,this function gives the CRNC the possibility to manage the configuration of common transpo
3.System Information Management, this function gives the CRNC the ability to manage the scheduling of System Information to be broad
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 sam
6.Measurements on Common Resources,this function allows the NodeB to initiate measurements in the NodeB. The function also allows
-Common NBAP : Defines the signaling sequence across the common signaling link. Common NBAP defines all the procedures for the log
management
-Dedicated NBAP : Sequence related to a specific UE signaling in the NodeB. Upon radio link setup procedure,the NodeB assigns a traffic
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 informa
2.Common Transport Channel Management,this function gives the CRNC the possibility to manage the configuration of common transpo
3.System Information Management, this function gives the CRNC the ability to manage the scheduling of System Information to be broad
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 sam
6.Measurements on Common Resources,this function allows the NodeB to initiate measurements in the NodeB. The function also allows
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 allow
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 signalin
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 be
-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 typ
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 man
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 (Bear
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 procedure
successful bearer setup, the application protocol procedure can be finished, and the application can be informed to start the data stream tra
er Equipment UE.
Switched PS (i.e. GPRS) domain
esponsible for serving the radio interface. Some of the tasks of the Mobile Equipment ares CDMA coding and
,Ciphering and authorization,Mobility management and equipment identification.
al equipment. It supports call handling,contains security parameters,user-specific data e.g. telephone directory
d e.g. via SMS or cell broadcasting.
authentication and chiphering for circuit and packet switched applications,PLMN selector and HPLMN search
c.
hich is labelled Iu-PS, and to the cs domain, which is called Iu-CS. In both cases, ATM is used as transmission
ce.
er situations, where a UE‘s active cells are under the control of more than one RNC. One RNC is responsible for
information.
M) and the control of itself and the connected NodeB (O&M functionality). It is connected to the CN , CS domain via Iu(CS)
a Iur interface and to the connected Node Bs via Iub interface.
connected with the NodeB serving the cell. The tasks of the C-RNC covers the following areas:
odeB).This means the C-RNC of a cell is responsible for all lower layer funcions related to the radio technology
).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
C performs the following functions:
n/modification or release of radio resources,for Outer Loop Power Control and for Handover decisions/initiation.
d the CN. It decides to add or remove cells in the Soft Handover. The S-RNC is in most cases (but not always)
an be re-allocated to another RNC with the S-RNS reallocation procedure.
corresponding RANAP signalling to/from the core network per UE. The S-RNC terminates the RRC signalling
a cell, that does not belong to the S-RNC. This means the UE is connected with a cell controlled by a RNC different
UE is connected to, but its not the S-RNC.Therefore D-RNC performs the C-RNC functions for the cells not
lementing a UMTS radio transmission. Depending on the sectoring of the cells ,one (omni) cell or multiple (sector) cells can be
up to six cells are serviced by a Node B in UMTS.
ency Division Duplex (Uplink and Downlink separated by different frequency bands),Time division Duplex (Uplink and
dual mode operation. A Node B converts user and signalling information received from the RNC for transport via the radio
ction. Node Bs are involved in power control,NodeB measures the signal to noise ratio (SIR) of the User Equipment ,compares
nd instructs the UE to control its transmission power. The NodeB also measures the quality and strength of the links and
(FER). The following are examples of NodeB functions:
nsport to physical channel mappings. Encoding/Decoding – Spreading/De-spreading user traffic and signalling.
ntrolling Uplink and Downlink radio paths on the Uu Air Interface,Baseband to RF conversion,Antenna multi-coupling,
ntrol,Quality and signal strength measurements
th M2000 and RNC for alarm and control (Operations and Maintenance) functions.
ement. Managing ATM switching and multiplexing over the Iub interface. Control of AAL2/AAL5 connections. Control
faces – E1, PDH, SDH or microwave.
possible,is sub-divided into National Service Areas.
d Country Code (CC). The National Service Area is sub-divided into one or more PLMN Service Areas.
Country Code (CC). The National Service Area is sub-divided into one or more MSC and SGSN Service Areas.
N (PS-domain). MSC and SGSN Service Area may differ, but they are on the same hierachical level. The MSCs and
) of UMTS. A Location Area is world-wide uniquely identified by its Location Area Identity LAI
ocation Area i.e. one LA may contain one or more RAs. The RA is the most precise UE information, which is
ty. The RA is sub-divided into the Cell-Areas.
LMN (in the RNC). The cell is world-wide uniquely identified by the Cell Global Identity (CGI)
raphical and physical entities of UTRAN are described as follow,
a MCC(mobile country code) and a MNC(mobile network code). MCC and MNC are allocated by ITU-T and are specified within
CS and the concept of Routing Area for PS.
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
RNC-ID the Cell-ID forms the UTRAN cell ID
o local cell identifier
a SAI(service area id):

types of identifiers according to the point of generation of the identifier:
core network. In detail there are IMSI,TMSI and P-TMSI (and IMEI)
). This means they are allocated to the UE for the time of the need. After the last procedure the identifiers are released.
ntry Code,MCC (3 digits) + Mobile Network Code,MNC (2-3 digits)+Mobile Subscriber Identification Number,MSIN. The total
his 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
U-SIM. The P-TMSI consists of 3 bytes,which are operator-dependent.
R. The IMEI(15 digits) consists of a Type Approval Code TAC (6 digits),the Final Assembly Code FAC(2 digits)which
e RNCs. Fours RNTI types exists:
s 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
the first cell access (at cell change) at existing RRC connection and for UTRAN originating Paging including
an in-band UE identifier in all DCCH/DTCH common channel messages on Uu despite the first access
E to the D-RNC. It is never used on Uu.

on between the different domains can be divided according to their functions. The UTRAN has the functions to provide access
and UTRAN and transport of signalling messages and user data between UE and CN. Therefore we can distiguish three types
een UE,UTRAN and CN as follows,
m(AS) : The Access Stratum covers all signalling exchange used to control the access of an UE to the network. Access Stratum
between UE and UTRAN and between UTRAN and CN. The difference between the access stratum UE-
AN-CN is ,that the UTRAN-CN access stratum shall be independent of the radio technology used in UTRAN. This
o support several different radio access technologies.
tum: The Transport Stratum protocols and messages have the task to transport higher layer PDUs (Protocol Data Unit)
cause UTRAN has the task to transparently transport data between UE and CN,there will be transport stratum
en UE and UTRAN and between UTRAN and CN.
tratum (NAS) : The Non-Access-Stratum covers all messages of higher layers and user data, that do not deal with
rt tasks.This cover pure application control (application stratum), service request and control (serving stratum)
cription data and subscriber specific services (home stratum).
e CN,UTRAN and the UE. CN and UTRAN are connected via Iu interface,UTRAN and the UE via Uu(radio) interface. User data
d control information (including requesting the service,controlling different transmission resources,handover etc) are exchanged
ng the Radio protocols and the Iu protocols of the Access Stratum (AS).
Non-Access Stratum(NAS) handle control aspects e.g. (GPRS)Mobility Management (G)MM,Connection Management (CM) or
s. The NAS procedures (of Rel. '99) are in most cases unchanged compared to the GSM Phase 2+
tocols contain mechanism for transparent NAS message transfer. So-called Direct Transfer (DT) procedures are
for these these transparent NAS message transfer.
RAN interfaces are designed in horizontal layers and vertical planes. The general protocol model describes these layers and
f each other. The modularity of this model allows changing parts of the protocol structure in the future,if neccessary,while other
UTRAN is ATM. There is difference between the usage of ATM and the use PCM lines in a GSM-BSS. ATM supports
abelled 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
licit signalling. This means before a AAL type 2 virtual channel can be used,there might be signalling between the
s behavior results in a new protocol model, where protocols for user bearer set up and release occur.
sts of two main horizontal layers- the Radio Network Layer and Transport Network Layer.All UTRAN related issues
Layer only.The Transport Network Layer is used for UTRAN,offering transport technologies.It is without any UTRAN
e Transport Network Layer consists of all protocols used for the transport network solution. This includes the physical
r,also the bearer service protocols are included.
dio Network Layer contains all protocols,that are specific to the radio access and transport stratum. Also all other data
h UTRAN, belong to this layer.
the elements of this vertical structure are planes. A plane principle is protocol stack,more than one plane can coexist
otocol model consists of three vertical planes- the Control Plane,the User Plane and the Transport Network Control
ports the data streams for user data. Therefore the data streams are packed into frame protocols. These frame
ata bearers. In contrast to the signalling bearers of the control plane,the data bearer can require to be set up with
e consists of all application protocols that are used for radio network controlling. To transport the messages of an
al signaling bearers,provided by the transport network are neccesary. The Control Plane is used for all control
. It includes the Application Protocols (i.e. RANAP,RNSAP and NBAP) and the signaling bearer for transport the
ne: The transport network control plane contains the ALCAP (Access Link Control Application Part). The ALCAP
release the data bearers of the user plane. Also ALCAP messages require a signaling bearer for transmission. It is
for all data bearers. Expecially the transport network control plane is not necessary when pre-configured bearers only
Control Plane is used for all control signaling within the Transport Layer. It contains no Radio Network Layer
lane acts as plane between the Control Plane and User Plane, it enables the Application Protocol in the Control Plane
hnology selected for data bearer in the User Plane.
Control Plane
ane is the setup of a data bearer for the user plane
ition ,the CS control plane is used for controlling supplementary services and it can be used for the exchange of short
interface. Therefore it performs spreading,scrambling.modulation,channel conding,rate matching etc.

random access and the multiplexing/de-multiplexing of different UEs onto shared radio resources.
y modes for every radio bearer. These modes are : Acknowledge (AM),Unacknowledge(UM) and Transparent (TM).
ms all higher layer tasks related to the access stratum on the air interface (e.g. radio bearer setup)
S service these are: MM (Mobility Management),CC (Call Control),SS(Supplementary Services) and SMS (Short
ks related to transport stratum for control signaling and access stratum between UTRAN and CN. It is the
singling connection for a UE. So the UE can then be identified by the signaling connection and not by an explicit
protocols supporting the user data transfer. In the lowest layers there are the same protocols as for the control plane. The
The same basic stack is used for the user plane.

ices (switched channels). These data streams are directly input to the RLC
ayer provides a bearer channel (virtual channel of AAL type 2) with certain QOS gurantees. Additonally the AAL 2 cirtual
sender and receiver.
ent stages of user data stream support.
interface (<>NBAP). On the other hand, the real time AAL 2 is used for relaying UE- data and UE-signaling
d MSC.
User Plane -PS
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
nd CS. UMTS has been designed to support both types of services, so that there are no special protocols.
interface towards the MSC.
onenction to the SGSN in the core network. RANAP handles all signaling transport and access related tasks.
ocols. Because there are essential differences how to handle a packet switched service request, the PS core
M (Session Management) protocol is used. The SMS is in fact the same as for CS.
ferences.
t). These external data network have their own special network protocols ( e.g. internet) . These external data
ted with such an external network, the UE has to send packets of this special network protocol, for the UMTS
acket Data Protocol (PDP). It is the task of the UMTS network to provide a tunnel (PDP context) for transparent
et header. This shall increase the efficiency of the air interface usage.
GTP-U organizes addressing and identification of the originator and destination of the data between RNC and SGSN.
nreliable transport service. In principle only routing is performed with UDP/IP
he interface between User Equipment (UE) and UMTS Terrestrial Radio Access Network (UTRAN) and it is the most
ce in the UMTS system.
ce (Uu) is layered into three protocol layers:

r (L1)
r (L2)
(L3).
orts all functions required for the transmission of bit streams on the physical medium. It is also in charge of measurements
g in indicating to higher layers, for example, Frame Error Rate (FER), Signal to Interference Ratio (SIR),interference power,
… It is basically composed of a “layer 1 management” entity, a “transport channel” entity, and a
” entity.
col is responsible for providing functions such as mapping, ciphering, retransmission and segmentation. It is made of four
Medium Access Control), RLC (Radio Link Control), PDCP (Packet Data Convergence Protocol) and BMC (Broadcast/Multicast
it into 2 parts: the access stratum and the non access stratum. The access stratum part is made of “RRC (Radio
)” entity and “duplication avoidance” entity. The non access stratum part is made of CC, MM parts.The RRC functions of
ted by RNC, and the MM and CC functions of L3 are implemented by CN.
ers are located in the UE and the peer entities are in the node B or the RNC.
Combinations
Combinations
has the following steps,that can be identified with the presented functional blocks:
or error detection
er the CRC is appended. if the resulting data block is too long (e.g does not fit into one radio frame) a segmentation is
rence.UTRAN FDD and TDD offer four different channel coding schemes as FEC(Forward Error Correction). These
e physical layer gets matching parameters from RRC layer

ding bits are appended
ng and interference of the channel
e Transport Channels)
smission) bits are inserted. This is only for downlink

o several radio frames
eral physical channels if neccesary
ansmitted in physical channels,there has to be an indication which transport formats are used for every transport
ransmission power)
procedures are triggered and mastered by higher layers like MAC and RRC. The procedures can be devided into
p synchronization to physical channels. In the TDD mode also timing advance procedures are used to synchronize
e solution for this is a very fast power control mechanism,using a closed control loop ( UE<>NodeB<>UE)
andom access mechanism to establish a radio connection between an UE and the Network. BNut also for
form measurements of radio signal quality (bit error rate) and radio signal strength (signal interference
over procedures. For the measurments the UE physical layer has uses so called compressed mode mode radio
hen performed.
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 respectively
2.Transfer of packet oriented user data using RLC transparent,unackowledge or acknowledged mode
3.Forwarding of PDCP-SDUs from NAS to RLC, and multiplexing of different RBs to the same RLC entity
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)
erface contains the following protocols:
t) : The NBAP protocol is the application protocol of the Iub interface. It organizes all controlling tasks between RNC and NodeB
configuration).
ocols constitute the signalling bearer for the NBAP messages.
ace has to transfer the downlink and uplink data to and from the UE. Therefore different frames are defined in the same
e user plane consists of:
Protocols encapsulate the UE data (UL&DL) on the Iub interface

ol,that encapsulate the UE data,are transported over AAL 2 virtual channels of ATM. These AAL 2 virtual channels have to be set
: The AAL type 2 SP provides the messages and functions to setup, release and modify AAL 2 virtual channels.
TC (Signaling Transport Converter),SAAL,AAL 5 and ATM provide the signaling bearer for AAL type 2 signaling protocol.
ardized. it is up to the operator and verndor to choose an appropiate physical transmission system.
erface contains the following protocols:
stem Application Part) : The RNSAP protocol is responsible for the communication between S-RNC and D-RNC. This
UE in a cell of the D-RNC,soft handover procedures and procedures to transfer the S-RNC functionality to a D-RNC
Control Part) : The SCCP is used to set up a signaling connection between S-RNC and D-RNC for the UE. This means
gnaling connection for every D-RNC and UE. The signaling connection will be used for fast identification of the UE in
ese protocols form the signaling bearer used for the RNSAP protocol messages.
ace has the tasks to transport uplink and downlink data for the UE connected to a D-RNC. This tasks requires the
and from the UE will be encapsulated into frame. These frames are defined by so called frame protocols. These frame
nt with in-band signaling
ol packets are transmitted via Iub using AAL 2 virtual channels. So AAL 2 ,ATM form the data bearer on the Iub interface.
: The AAL type 2 SP provides the messages and functions to setup, release and modify AAL 2 virtual channels.
: These protocols provide the signaling bearer for the AAL type2 signaling protocol. The STC(Signaling Transport
for congestion handling and load control. The protocol suite MTP3B,SAAL,AAL5 and ATM can be shared with the
ntrol Plane
pplied to the UTRAN interfaces Iu, there are differences between Iu-CS toward the CS-core network domain and Iu-PS towards
rmed out of the following protocols:

rk Application Part) : The RANAP protocol is responsible for all access and signaling transport related tasks. It is the
nterface
Control Part) : The SCCP is used to setup signaling connection between RNC and MSC. There will be one and only one SCCP
y IE using CS service.
eses protocols provide the signaling bearer for RANAP/SCCP messages
support the transfer of real time CS data streams. Therefore the Iu-CS plane has the following protocols:
he Iu UP protocol is used to provide additional support functions for CS data streams on Iu. These functions can be : timing
d error conrrection.
to transport the data streams the AAL 2 virtual channels are used.
plane is necessary ,because AAL2 virtual channels need to be setup and released. The protocol suite on the transport
of:
: used to setup ,modify and release AAL 2 virtual channels.
: These protocols provide the signaling bearer for the AAL type 2 signalling protocol messages.
ce between RNC and SGSN. The control plane of Iu-PS is similar to the Iu-CS plane. It consists of:
ol for Iu-CS and Iu-PS

ection on Iu-PS. There will be one and only one SCCP connection between RNC and SGSN for every UE using PS
-PS and Iu-CS do not affect each other.
e signaling bearer for SCCP/RANAP
petely different to the user plane of Iu-CS. This is because the traffic to and from SGSN is PS, so routing layer are
the following protocols on the Iu-PS user plane:
e Iu UP protocol can provide additional support functions for the data stream.
col-User Plane): GTP-U provides a frame for the user data to be transported. In a GTP-U frame a reference number for
umbers for the data are contained.
uite is used as network layer between RNC and SGSN. The task of these protocols is to route from RNC to SGSN and
on layer of type 5 is used as bearer for the packets of IP/UDP/GTP-U.

t 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 on Iu-PS there is no need for a transport network control plane. no bearer set up with explicit signalling is necessary.
RANAP NBAP
trols signaling information for the call setup between nodes. Basically these applications message structure is similar to the SS7
ng for the control plane and one application part (ALCAP) to set up the transport bearer for the user plane.
ocol that contains all the control information specified for the Radio Network Layer. The fucntions of RANAP are
more EP.
nected RAB
eted by UTRAN, such as broadcast information,direct transfer etc.

radio interface
to two procedures :
all the procedures for the logical operation and maintenance of the Node-B, such as configuration and fault
e,the NodeB assigns a traffic termination point to control UE signaling. All of the subsequent signaling related to
the cell configuration information in a NodeB.

figuration of common transport channels in a NodeB.
stem Information to be broadcast in a cell.
us of NodeB resources.
that both nodes have the same information on the configuration of the radio resources.
deB. The function also allows the NodeB to report the result of the measurements.
protocol that controls signaling transfer between two RNC (SRNC and DRNC) in order to support the inter RNC soft
to avoid DL power drifting between radio links

CCH controlled by the DRNS
es the signaling capability to establish,release and maintain AAL2 connections by a series of ATM VCCs. In other
UTRAN. The transport bearer in the User Plane are setup first sending signals by the Application Protocol in the
LCAP is dependent on the type of bearer to be used. The signaling bearers are usually pre-configured. This means
etup runs in the following manner:

a single transport system, the application protocols shall not be specific to a certain transport solution. Therefore
s the same as for BICC (Bearer Independent Call Control). to trigger the set up of a bearer first the application
orms all necessary procedures to configure the bearer. When the application part receives the notification of a
ed to start the data stream transmission.
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 divided into 4 service states,which deﬁne what kind of physical channels a UE is using. The mapping of UE state to 3GPP
speciafication is shown below:
UE Switch on
GSM GSM Packet

UE Idle UE Connected Transfer
3GPP TS 25.304 3GPP TS 25.331 Connected
GSM TS 04.18 GSM TS 04.50
GSM Idle UE Idle

3GPP TS 25.304 Cell_DCH
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 responsibi
-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 b
the higher layer control plane protocol messages.
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 transparent
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 trans
-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 channe
For RRC messages the protocol specified which RLC mode and with this which radio bearer can be chosen for transport of t
RRC Modes and State Transitions including GSM
UTRA RRC Connected Mode

GSM-UMTS Handov
URA_PCH CELL_PCH
UTRA: Inter-RAT Handover
CELL_DCH CELL_FACH GPRS Packet

Cell Transfer
Reselection Mode
Release
Release RRC Release RRC of a TBF
Connection Connection
Establish RRC Establish RRC

Connection Connection
(UE camps on UTRAN cell) (MS in GPRS Packet Idle
Idle Mode
(MS camps on a GS
The RRC protocol is an application part (Radio Resource Management) and transport protocol (NAS message transport). Therefore the RR
between states.
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 have
The RRC protocol is an application part (Radio Resource Management) and transport protocol (NAS message transport). Therefore the RR
between states.
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 have
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 c
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 sta
mobile phone can be:
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 camp
2. GSM conected mode : In GSM the RR (Radio Resource Layer) performs the radio management. This protocol can setup a RR connect
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 ca
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).Therefore
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 between
UEs in the RRC idle mode. If UTRAN wants to address 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 Requ
used to exchange messages and data between the UE and UTRAN, the UE is identified by a Radio Network Temporary Identity (RNTI). As
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 le
transport channels depend also on the sub-states. For instance, the DCHs are not available in the sub-states CELL_PCH and CELL_URA.
mode when sending the RRC Connection Request message to UTRAN. When UTRAN accepts the UE‘s 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 k
the UE. UTRAN can know any UE either on cell level (cell state) or on URA level (URA state). On the other hand any UE can have a DCH o
exchange. Therefore the four connected states are introduced:
CELL_DCH
In this sub-state, dedicated physical channels are allocated to the UE. DCCH and – if configured – DTCH information can be transmitted. T
because the physical channels are exclusively allocated to this UE. UTRAN knows the active set cells for the radio links and thus the locati
allocated to the UE. In this state, the UE is capable to receive RRC messages on the DCCH (and BCCH, if it owns specific capabilities). Th
The UE reads the cell system information and acts accordingly. For instance, it determines the measurement quality and the reporting even
be entered from Cell_FACH by setting up a DCH. When the last DCH is released the UE enters Cell_FACH,Cell_PCH,URA_PCH or idle m
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
amount of user data (e.g. SMS messages) have to be transmitted. In this case, an exclusive allocation of one physical channel to the UE w
transport channel FACH can be used by the UE to transmit higher layer data, which it has to share with other UEs. Each UE must be expli
monitor the FACH permanently in the downlink, not to miss user data for it. The UE‘s FACH is mapped on one S-CCPCH.
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 thi
soft handover takes place in this sub-state. The UE is responsible for cell re-selection. By listening to the cell system information from the B
threshold values, neighbourhood lists to perform the cell re-selection process. Other relevant information is also learned from the BCCH. Th
RRC messages on the BCCH, CCCH and DCCH channels. Due to the discontinuous type of traffic, UTRAN can command the UE to perfo
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
transport channel FACH can be used by the UE to transmit higher layer data, which it has to share with other UEs. Each UE must be expli
monitor the FACH permanently in the downlink, not to miss user data for it. The UE‘s FACH is mapped on one S-CCPCH.
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 thi
soft handover takes place in this sub-state. The UE is responsible for cell re-selection. By listening to the cell system information from the B
threshold values, neighbourhood lists to perform the cell re-selection process. Other relevant information is also learned from the BCCH. Th
RRC messages on the BCCH, CCCH and DCCH channels. Due to the discontinuous type of traffic, UTRAN can command the UE to perfo
In the CELL_FACH state the UE shall perform the following actions:

- DCCH and DTCH are available
- 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":
- 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, who
work with the data, and for a longer time, no transmission takes place. If this is the case, access stratum resources can be released when m
nor DTCH is allocated to the UE. No exchange of data is possible between the UE and UTRAN. If the UE wants to transmit something, it m
The UE listens to the cell system information, broadcasted on the BCCH. It performs measurements accordingly, and is responsible for cell
PLMN with a higher priority. When UTRAN wants to transmit data to the UE, it must be paged first. Therefore, the UE has to monitor pagin
both on the BCCH and the PCCH.
CELL_PCH In this sub-state, the UE‘s current cell is known to the RNC. If the RNC wants to exchange data with the UE, it only needs to pa
must perform a cell update. Also periodical cell updates can be requested by UTRAN. To perform updates, the UE must change to the CEL
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 u
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 respons
URA – and periodic URA updates – when required by UTRAN.
In the URA_PCH or CELL_PCH state the UE shall perform the following actions:
- maintain up-to-date system information as broadcast by the serving cell
- perform a periodic search for higher priority PLMNs
- monitor the paging occasions according to the DRX cycle and receive paging information on the PCH
- 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":
- 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 o
state and send the RRC message Cell Update or URA Update.
Depending on the UE‘s RRC message, UTRAN returns the RRC message Cell Update Confirm or URA Update Confirm – if it accepts the U
Connection Release message.
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 sta
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 UE‘s 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 U
transmitted uplink.
- The UE is in the CELL_DCH and a radio link failed.
Connection Release message.
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 sta
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 UE‘s 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 U
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 UE‘s URA. An URA Update is then triggered by the UE to get a ne
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 Co
If no confirmation message arrived within this time period, the UE retransmits the original message. The number of Cell Update or URA Up
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
but also, when the UE is in the CELL_FACH sub-state. A periodic update is a supervision mechanism, which can be used by the mobile op
was performed, a UE in the CELL_FACH sub-state may transit to the sub-states CELL_DCH, CELL_PCH or URA_PCH, or in the RRC mod
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 t
UE moves into the idle mode and releases all 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 t
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 ser
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 n
the timer T317 is stopped. Also timer T307 is stopped, when it was active. The UE has to transmit the RRC Cell Update message to UTRAN
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 n
the timer T317 is stopped. Also timer T307 is stopped, when it was active. The UE has to transmit the RRC Cell Update message to UTRAN
cell update: re-entering service area. If the timer T317 expires, the UE moves to the idle mode. It releases all dedicated resources.
connected mode can be

ping of UE state to 3GPP
GSM Packet
Transfer
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
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.

can be chosen for transport of this message.
GSM-UMTS Handover
GSM
Connected
Mode
Inter-RAT Handover
Release RR
Connection
GPRS Packet
Transfer
Mode
Release
of a TBF
Initiation
of a TBF Establish RR
Connection
(MS in GPRS Packet Idle Mode)
(MS camps on a GSM/GPRS cell)
ssage transport). Therefore the RRC protocol requires state definition with transitions
states are defined:

ase the idle mode procedures have to be applied. This means as soon as the
n the access stratum level between the UE and UTRAN. UTRAN has no information about
s, such as IMSI or TMSI and LAI.
aging occasions on its PICH.
ending the "RRC Connection Request" message to UTRAN. If common transport channels
work Temporary Identity (RNTI). As can be seen in the
tates depend on the connectivity level between the UE and UTRAN. The set of usable
ates CELL_PCH and CELL_URA. The UE leaves the RRC idle
s 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
er hand any UE can have a DCH or a FACH or no transport channel for control message
H information can be transmitted. There no need to identify the UE on a dedicated channel,

r the radio links and thus the location of the the UE. Also downlink shared channels can be
H, if it owns specific capabilities). The cell system information is broadcasted on the FACH.
ment quality and the reporting events from the cell system information. This state can only
CH,Cell_PCH,URA_PCH or idle mode
ping on FDD cells);
This is the case when only higher layer signalling information (NAS signalling) or small
f one physical channel to the UE would result in a waste of resources. Only common
other UEs. Each UE must be explicitly addressed, for instance by the RNTI. It has to
n one S-CCPCH.
only connected to one cell, and this is the location information, known within UTRAN. No
cell system information from the BCCH, it gains all relevant measurement qualities,
is also learned from the BCCH. The UE receives
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
resources can be released when moving in one of the two states. In both states, no DCCH
E wants to transmit something, it must move first internally to the sub-state CELL_FACH.
ordingly, and is responsible for cell-reselection. In addition to that, it periodically looks for a
efore, the UE has to monitor paging occasions on its PICH, i.e. it receives RRC messages
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
hat 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
Update Confirm – if it accepts the UE‘s update request. Otherwise, it return the RRC
e UE moves to the CELL_FACH state and notifies UTRAN.

H and URA_PCH.
it.
H transition is an indication by the UE‘s 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,
hich can be used by the mobile operator to keep track of the UE. If a cell or URA update
H or URA_PCH, or in the RRC mode idle.
or URA updates.
07 is activated, and the UE starts the cell selection process. If the timer T307 expires, the
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
has 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,
RC Cell Update message to UTRAN, indicating the cause of the
es all dedicated resources.
>>State Transistions Parameters Description (Module II)

>>UE&NodeB Timer and constant Parameters Description (Module II)
RRC Procedures
Between the UE and the RNC, the Radio Resource Control (RRC) protocol is used to exchange signalling and control data to establish, ma
the transport channel configurations, and the physical layer settings. With that, the UE knows how to receive and transmit data via the WCD
Node B about the radio interface configuration.
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 connection
information transfer, etc.
-Radio Bearer Control Procedures :These procedures for radio bearer establishment, transport channel and physical channel reconfigura
-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 capab
-Radio Bearer information elements: These information elements mostly describe the characteristics of a radio bearer, such as RB inform
-Transport Channel information elements: Here, mainly the transport channel characteristics are described, such as the description of TF
-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
establishment is always initiated by the UE. It is transmitted via the logical channel CCCH.
UTRAN returns a response. If UTRAN accepts the UE‘s RRC Connection Request, it returns the message RRC Connection Setup messag
and physical channels.
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 pa
interface and Uu-interface. Before the RNC returns the RRC Connection Setup message to the UE, it uses the UTRAN specific signalling p
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 th
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 th
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 r
the operator, but it is an option. If set by the operator, it is broadcasted as cell system information. The cells, listed in the measurement resu
with the best one in the beginning of the list.
RRC Connection Setup Message

2.RRC Connection Setup message
If the S-RNC accepts the UE‘s RRC C
link connection over the interface Iub.
configuration parameters for uplink an
prepared to serve as intermediate mo
parameters with the RRC Connection
establish signalling radio bearers betw
The RRC Connection Setup message

characteristics both in the UL and dow
to the RRC layer in the UE. The UE‘s
-If only the physical layer characte
modification may affect scrambling an
has no impact to the higher layers. Th
change measurement quantities or th
-If the transport channels are modi
PHY layer. The MAC layer is respons
resources, ciphering and de-ciphering
-If a radio bearer is established, or
(RLC) layer – for each radio bearer, a
Broadcast/Multicast Control (BMC) la
the RRC Connection Setup message
PDCP layer and BMC layer relevant
has no impact to the higher layers. Th
change measurement quantities or th
-If the transport channels are modi
PHY layer. The MAC layer is respons
resources, ciphering and de-ciphering
-If a radio bearer is established, or
(RLC) layer – for each radio bearer, a
Broadcast/Multicast Control (BMC) la
the RRC Connection Setup message
PDCP layer and BMC layer relevant
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 physica
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 part
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, whic
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 holds relevant information to identify the receiver of the RLC PDU. For instance, if two DTCHs are multiplexed on one DCH, then field
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 Ph
established. As can be seen, a UE can be immediately re-directed to another frequency band for the signalling bearer setup. Also the avail
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 closer
following FDD-mode specific information elements:
1. DPCH compressed mode If a UE has only one receiver, it can‘t 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 M
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 UE‘s si
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 rate
are sent on four timeslots to the Node B.
RRC Connection Setup Complete message

inter-system message from the UE CAPABILITY INFORMATION message and transfer it to
After the UE transmits RRC CONNECTION REQUEST message, the T300 timer will be started, and the timer will be stopped after the UE r
CONNECTION REQUEST message is retransmitted less than the number of times specified by the constant N300, the UE repeats RRC C
unsuccessful. The procedures in details are as follows:
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 the
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 upli
A UE Layer1 shall check the synchronisation status of every radio frame of downlink and uplink dedicated channels in order to detect a loss
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 not
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 incor
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 wi
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 usin
At least one TB in the last radio

frame with correct CRC transmitted
last TBs transmitted 20
UE Sycnchronization Status with incorrect CRC transmitted
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 ind
DPCCH quality or CRC checks. One example would be to have the 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 upli
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 ind
DPCCH quality or CRC checks. One example would be to have the 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 upli
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 d
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 notified
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 wo
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 th
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 t
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 l
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 w
the UE. Simultaneously, UTRAN establishes uplink chip and frame synchronisation of the new radio link. Frame synchronisation can be con
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 synch
layers every radio frame.
Radio Link Monitoring
Downlink Direction
Uplink Direction
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
after receiving N313 consecutive "out of sync" indications from layer 1 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
after receiving N313 consecutive "out of sync" indications from layer 1 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
after a cell or URA update. T314 is controlling transparent and unacknowledged mode(UM) bearers. T315 is controlling acknowledged(AM)
->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 c
If T314 expires and T305 is not running, then all radio bearers associated with radio bearers with T314 value are locally released. If addition
If T315 expires and T305 is not running, then all radio bearers associated with radio bearers with T315 value are locally released. If addition
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 UPDAT
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 to
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-o
receiving successive N_INSYNC_IND in-sync indications. If T_RLFAILURE expires, Node B shall trigger the RL Failure procedure and indic
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 synchroniz
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 R
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 N
After the BTS has established the frame synchronization to the uplink DPCH, the transmission power of the downlink DPCH is controlled ba
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 from
setup has failed.
->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 –m
->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
alling and control data to establish, maintain, and release connections. The UE gets informed about the radio bearer characteristics,
receive and transmit data via the WCDMA radio interface. The RNC uses the NodeB Application Part (NBAP) protocol to inform the
1 V3.12.0:
m information, paging, RRC connection establishment and release, UE capability inquiry, security mode control, Inter-RAT handover
annel and physical channel reconfiguration, physical channel failure, etc. can be found here.
mobility information, active set update, and various handover procedures are covered here.
omain identity.
tities are examples of data, associated with these IEs.
equirements, PDCP and FDD RF capabilities, radio access capabilities, cell update causes,etc.
cs of a radio bearer, such as RB information to setup.
described, such as the description of TFCs and TFCSs.
uch as the description of CCTrCHs or compressed mode information.
e exchanged here.
en the UE and UTRAN.
idle mode, and higher layer protocols in the UE request a signalling connection to UTRAN. Please note, that an RRC connection
ssage RRC Connection Setup message. The UE gets all relevant parameters regarding the signalling bearers, transport channels,
he Node B must also get all relevant parameters to serve the UE on the radio interface adequately, and to relay data between the Iub-
t uses the UTRAN specific signalling protocol NBAP to send these parameters to the Node B.
are returned to the UE via a FACH.
omplete message to the RNC, using the transport channel DCH. Beforehand it performed a L1 Synchronization.
s can be found in this message:
ce one of the UE identity to use
he RACH, because the measurement results are transmitted via the transport channel RACH. The measured quantity can be set by
e cells, listed in the measurement result list, are ordered in accordance to the measurement results,
2.RRC Connection Setup message

If the S-RNC accepts the UE‘s RRC Connection Establishment request. It starts an interaction with the Node B to establish a radio
link connection over the interface Iub. 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 used to
establish signalling radio bearers 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 channel
characteristics both in the UL and downlink directions. The RRC Connection Setup message is sent from the RRC layer in the RNC
to the RRC layer in the UE. The UE‘s RRC uses management 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 won‘t 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 won‘t see the
PDCP layer and BMC layer relevant parameters.
ers, which are established with this RRC message.

racteristics, in other words the TFCS.
t for 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, whether the
RRC message is for them. For 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 L2
synchronisation. The network has to 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 allocates
a S-RNTI to the UE to address the UE. When the UE accesses a new cell, the C-RNC allocates aC-RNTI to the
UE, with which it addresses the UE. The U-RNTI is a concatenation of the S-RNTI and the S-RNC‘s 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 to.
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 UE and the
RNC. The RRC layer also takes 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 Radio
Link Control layer(RLC) has to 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 distinguished:
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 other
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 optional.
This is indicated with the IE Signalling RB to Setup List. Given the number, either 3 or 4 descriptions of radio bearers
follow. They contain information, 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 get
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 are
also logical channel identities.
or two logical channels. This was part of the RB setup information. The information carried on radio bearers must be
ransmitted? How can higher layer information be segmented? This is described with the information elements for
ent 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
are multiplexed on one DCH, then field C/T is added in the MAC header to identify the logical channel, to which
H, CPCH, DSCH.
e the physical channels. One of the PhyCH IEs is the carrier frequency band, where the signalling connection is
signalling bearer setup. Also the available UL and DL radio resources have to be described.
etup message. When we have a closer look to the IE „Downlink information common for all radio links“, we detect
AT measurements on neighbouring cells and at the same time receive data from the active set cells. If this is the case,
fore, this mode is often called Slotted Mode. In order to transmit still the user data with a given data rate, more
a short while.
e all active set cells receive the UE‘s signals, only one is making a transmission downlink. The UE tells the active set
Node B, so that this device can decide, how to set the weighting to the individual antennas. There are two different so-
a. 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 message
to the S-RNC. This message is transmitted via the logical channel DCCH on the radio signalling bearer, which offers
acknowledged mode of operation (RB2). The information elements in 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 handover
control entity
-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 capability
has the value "FDD" or "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.
has the value "FDD" or "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.
message and transfer it to the handover control entity.
the timer will be stopped after the UE receives RRC CONNECTION SETUP message. Once the timer times out, if RRC
constant N300, the UE repeats RRC CONNECTION REQUEST; otherwise it will be in the idle mode,consider the procedure to be
al UE identity" equal to the value of the variable INITIAL_UE_IDENTITY; and if cell re-selection or expiry of timer T300 occurs;
nk CCCH;
on status of radio links, both in uplink and downlink.
cated channels in order to detect a loss of the signal on Layer 1, as specified in TS 25.214. The synchronization state of
BER is the relation of the incorrectly detected pilot bits to the total number of pilot bits in a radio frame),the thresholds
turn its power on respectively. The synchronisation status is reported to the higher layer.
fter the downlink dedicated channel is considered established by higher layers
e following criterion is fulfilled:

in. This criterion shall be assumed not to be fulfilled before 40 ms of DPCCH quality measurements have been
values to the actual physical channel BER is given in 3GPP TS 25.133)
n-sync status
ng criteria are fulfilled:

d Qout. Qout is defined implicitly by the relevant tests(def. 15% BER)
ng CRC, have been received with incorrect CRC. In addition, over the previous 160 ms, all transport blocks with a CRC
nsidered only for TrCHs using CRC in all transport formats.
re fulfilled:
Qin. Qin is defined implicitly by the relevant tests(def.20% BER)
in a TTI ending in the current frame with correct CRC. If no transport blocks are received, or no transport block has a
shall 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 Out-of-sync
state state
RL Restore
NodeB Radio Link Set States and Transistions
chronisation status is indicated to the RL Failure/Restored triggering function using either the CPHY-Sync-IND or
r 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
synchronisation status primitives.
nd one uplink dedicated physical channel are to be set up;

cal channel is to be set up and an uplink dedicated physical channel already exists.
Downlink Direction
Uplink Direction
ink failure detection in DL is based on counter N313 (counting “out of sync” indicator) and timer T313 in UE. In CELL_DCH State,
hysical channel in FDD the UE
. Once the radio link sets have been established, they will be in the in-sync or out-of-sync states. Transitions between
Sync-IND and CPHY-Out-of-Sync-IND, indicating in-sync and out-of-sync respectively. Note that only one
dio link is moved from the initial state to an In-sync state. L1 informs BTS L3 about the established synchronization and
g N_OUTSYNC_IND consecutive out-of-sync indications. Node B shall stop and reset timer T_RLFAILURE upon
gger the RL Failure procedure and indicate which radio link set is out-of-sync. When the RL Failure procedure is
L1 keeps on searching the synchronization as long as the synchronization has been re-established or the radio link is
c indications Node B shall trigger the RL Restore procedure and indicate which radio link set has re-established
o the in-sync state. BTS L3 sends the NBAP:SYNCHRONIZATION INDICATION message to the RNC
r of the downlink DPCH is controlled based on the TPC bits transmitted by the UE. Also, the TPC bits transmitted in the
he parameters Qin and Qout and N_INSYNC_IND, N_OUTSYNC_IND, T_RLFAILURE are given by the RNC to the BTS
s N312 synchronization indications from L1, it will stop the T312 timer. Once the timer times out, it means that the physical channel
Successful Synchronization on UL and DL
Downlink Direction
Uplink Direction
2 and wait for layer 1 to indicate N312 "in sync" indications
mer 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
tion –message to RNC

ink Deletion -message
ULSynchronization failed because of

no DL synchronization
Downlink Direction
Uplink Direction
ge to RNC
message to RNC
ching for the synchronization
>>See More details of 1,2,3
>>Synchronization Parameters Description (Module II)

Radio Bearer(RB) Procedures

The RB control procedures are used to establish additional radio bearers, modify them, or release them.
RB Setup, Reconfigu
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 parameters have 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 transport channel modification always has an impact on the physical channel setting. A
transport channel reconfiguration is triggered with the RRC 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 Transport Ch

RB Setup, Reconfiguration, and Release
Transport Channel Reconfiguration-on existing RBs

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 the acti
- Inter-RAT measurements: measurements on downlink physical channels belonging to another radio access technology than UTRAN, e
- 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 controlled and
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 involved in s
2. Cells, which are not included in the active set, but are monitored according to a neighbour list assigned by the UTRAN belong t
3. Cells detected by the UE, which are neither included in the active set nor in the monitored set belong to the detected set. Repor
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 parameters fo
control information to the UE for the serving cell. SIB 3 and SIB 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 cell se
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 in the
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 type
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 message i
measurement command links a measurement with a measurement identity, quantity, objects, reporting quantities, reporting criteria, type,
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 contain in
system information, may be included in the SIB 11. If they are included, the UE can send a measurement report, when a measurement re
Control message including one of the above mentioned measurement types, it replaces its internal stored data based on the SIB11 by th
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 parameters.
valid, as long as there was no Measurement Control message, which replaces the parameters. But what happens, if the UE was in the C
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 control p
CELL_DCH sub-state, the UE resumes with the measurements and associated reporting, as they they were stored before the transition to
In the RRC idle state, the UE retrieved the measurement control parameters from the SIB type 11. Information Elements, which contain in
system information, may be included in the SIB 11. If they are included, the UE can send a measurement report, when a measurement re
Control message including one of the above mentioned measurement types, it replaces its internal stored data based on the SIB11 by th
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 parameters.
valid, as long as there was no Measurement Control message, which replaces the parameters. But what happens, if the UE was in the C
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 control p
CELL_DCH sub-state, the UE resumes with the measurements and associated reporting, as they they were stored before the transition to
The Measurement Control is

The UE gets all relevant inform
conducted periodically or drive
Control message is transmitte
the RRC connected sub-state
the RRC message Measurem
mode.
The RRC message Measurem

(RNC). This message is trans
mode. The RLC entity mode is
transmitted in the CELL_DCH
- CELL_DCH: If a reporting cr
identifies the measurement as
measurement event.
-CELL_FACH: In this sub-sta
UE. Intra-frequency measurem
SIB12) the maximum numbers
-CELL_PCH or URA_PCH: U
they are in the CELL_FACH s
holds traffic volume measurem
Measurement Control Contents
UTRAN may control a measurement in the UE either by broadcast system information and/or by transmitting a MEASUREMENT
control information:
1. Measurement identity: A reference number that should be used by the UTRAN when setting up, modifying or releasing the measurem
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 control
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.
UTRAN may control a measurement in the UE either by broadcast system information and/or by transmitting a MEASUREMENT
control information:
1. Measurement identity: A reference number that should be used by the UTRAN when setting up, modifying or releasing the measurem
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 control
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 for the
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 measurement re
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, whi
capabilities into account when a measurement is assigned to the UE.
When a new measurement is initiated, UTRAN should set the IE "Measurement identity" to a value, which is not used for other measurem
In case of setting several "Measurement identity" within a same "Measurement type", "Measurement object" can be set differently for eac
When a current measurement is modified or released, UTRAN should set the IE "Measurement identity" to the value, which is used for th
identity", it is not needed for UTRAN to indicate the IEs other than modifying IEs, and the UE continues to use the current values of the IE
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 compressed mod
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 measure
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 IE "m
--> 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_IDENTIT
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 sequence a
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 status fl
-->begin the inter-frequency and/or inter-RAT measurements corresponding to the pattern sequence measurement purpose of each activ
-->if the values of IE "TGPS reconfiguration CFN" and IE "TGCFN" are equal:start the concerned pattern sequence immediately at that C
- 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 UTRAN.
Initiation:
In CELL_DCH state, the UE shall transmit a MEASUREMENT REPORT message on the uplink DCCH when the reporting
measurements that are being performed in the UE.
The purpose of the measurement reporting procedure is to transfer measurement results from the UE to UTRAN.
Initiation:
In CELL_DCH state, the UE shall transmit a MEASUREMENT REPORT message on the uplink DCCH when the reporting
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 reporting
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 transm
MEASUREMENT REPORT message on the uplink DCCH when the reporting criteria stored in variable MEASUREMENT_I
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 transm
- an event in stored IE "Measurement reporting criteria" was triggered. Events and triggering of reports for different measure
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 MEA
- set the IE "measured results" to include measurements according to the IE "reporting quantity" of that measurement store
--> 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 measur
"additional measurements" stored in variable MEASUREMENT_IDENTITY of the measurement that triggered the measurem
--> if more than one additional measured results are to be included:sort them in ascending order according to their IE "mea
- if the MEASUREMENT REPORT message was triggered by an event (i.e. not a periodical report):set the IE "Event results
The UE shall:
- transmit the MEASUREMENT REPORT message on the uplink DCCH using either AM or UM RLC according to the stored
that triggered the report.
When the MEASUREMENT REPORT message has been submitted to lower layers for transmission:
-The procedure ends.
ure. (TS 25.331-360)
he active set.
om the frequency of the active set.
s technology than UTRAN, e.g. PDC or GSM.
asurement is controlled and reported independently of every other measurement.
erent categories:
e active set are involved in soft handover.
gned by the UTRAN belong to the monitored set.
RLFailure
g to the detected set. Reporting of measurements of the detected set is only required for intra-frequency
pe 3 contains parameters for cell selection and re-selection. In parallel, the SIB type 11 is used to deliver measurement
ly and responsible for cell selection and re-selection. It retrieves the parameters for cell selection from SIB
d valid, when the UE is in the CELL_FACH, CELL_PCH and URA_PCH sub-state. If SIB 4 resp. SIB 12 is
is not reading the SIB type 3/4 and 11/12. The parameters of SIB 12 (SIB 11, if SIB is not available) can
d to the UE. This message informs the UE about the type of measurement, which has to be conducted. Each
ties, reporting criteria, type, etc.
e distinguished:
n Elements, which contain intra-frequency, inter-frequency, inter-RAT and traffic volume measurement
ort, when a measurement reporting criteria is fulfilled. As soon as the UE receives a Measurement
ta based on the SIB11 by the parameters delivered with the Measurement Control message.
urement control parameters. If the UE transits to the CELL_DCH sub-state, the system information stays
pens, if the UE was in the CELL_DCH sub-state, it has received Measurement Control messages, and
d its measurement control parameters become valid. But when the UE then transits back to the
stored before the transition to the CELL_FACH (or any other RRC connected) sub-state.
In-sync Out-ofsync
he Measurement Control is used to setup, to modify, and to release a measurement in the UE.
he UE gets all relevant information, how to perform a specific type of measurements. A measurement is either
onducted periodically or driven by an event. Then, the UE returns a measurement report. The Measurement
ontrol message is transmitted on a DCCH via an RLC entity in the acknowledged mode. I.e. the UE is either in
stae stae
e RRC connected sub-state CELL_DCH or CELL_FACH. If the setup of a measurement fails, the UE returns
e RRC message Measurement Control Failure. It is transmitted on an UL DCCH via an RLC entity in the acknowledged
ode.
he 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
ode. The RLC entity mode is set by the RRC message Measurement Control. Measurement results can be only
ansmitted 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
entifies the measurement as specified by UTRAN. It includes measurement quantities and identifies the
easurement event.
CELL_FACH: In this sub-state, traffic volume measurements and positioning measurements are reported by the
E. Intra-frequency measurements are reported via the RACH, whereby the UE learns from the BCCH (SIB11 or
B12) 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
ey are in the CELL_FACH state, where the Measurement Report can be sent. The measurement report either
olds 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 measurements
simultaneously. Each type of measurement is identified by an allocated „Measurement
Identity“. Some measurements are not conducted continuously.
UTRAN tells the UE once, how to perform a type of measurements. Whenever necessary, it
just informs the UE to conduct the measurements of a measurement type by just telling it
RLRestore
the associated measurement identity.
In the RRC message Measurement Control, the is an PhyCH information elements, where
the UE can gain DPCH compressed mode status information
mitting a MEASUREMENT CONTROL message. The latter message includes the following measurement
g or releasing the measurement and by the UE in the measurement report.
ence of the following control information depends on the measurement type
ments.
RLRestore
T CONTROL message, which is transmitted on the downlink DCCH using AM RLC.The UTRAN should take the UE
not used for other measurements. UTRAN may use several "Measurement identity" for the same "Measurement type".
can be set differently for each measurement with different "Measurement identity ".
e value, which is used for the measurement being modified or released. In case of modifying IEs within a "Measurement
e the current values of the IEs that are not modified.
tity";
ents and a compressed mode pattern sequence with an appropriate measurement purpose is
easurements: begin measurements according to the stored control information for this measurement
easurement identity.
entity indicated by the IE "measurement identity";
MEASUREMENT_IDENTITY.
vate this pattern sequence at the beginning of the frame indicated by IE "TGPS reconfiguration CFN"
or which the "TGPS status flag" is set to "active" at the time indicated by IE "TGCFN"; and
ement purpose of each activated pattern sequence;
uence immediately at that CFN;
able TRANSACTIONS;
om the UE to UTRAN.
DCCH when the reporting criteria stored in variable MEASUREMENT_IDENTITY are met for any ongoing
-ofsync
s ta e
Paging
Paging includes CN orignated paging and UT
The CN originated paging precedure: is used

and non co-ordination paging. The CN indicates
perform the UTRAN co-ordination paging
-Co-ordination paging, the RNC shall check w
besides the paging domain connection. If so an
message shall be transmitted on the already co
URA_PCH state,the paging message shall be tr
shall be transmitted on the PCCH.
-Non-co-ordinating paging, the RNC need not
besides the paging domain connection but direc
specified paging area.
The UTRAN orignated paing : The UTRAN ma

a cell update procedure to enable the transition
a UE to trigger reading of updated system inform
For a UE in idle mode or in CELL_PCH or URA_

a PAGING TYPE 1 message on the PCCH. For
paging procedure by transmitting a PAGING TY
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 R
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 connect
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 information
The UE monitors the paging channels (S-CCPCHs carrying PCCH) on all paging occasions. If the UE receives a paging message, it reads
message. If so, it returns a paging response. The UTRAN may repeat the transmission of a PAGING TYPE 1 message to a UE on several
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 contro
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 is
message to all RNCs, which participate in the LA where the UE is registered. This paging message is received by a RNC, which is current
paging request to the UE. Therefore, Paging Type 2 is often called dedicated paging.
Paging Message Type 1 Click to return to main page

"Or"
Paging Message Type 2 Click to return to main page

>>Paging Procedure and Parameters Description (M
s CN orignated paging and UTRAN originated paging
ed paging precedure: is used to establish a signaling connection. It is divided into co-ordination paging
nation paging. The CN indicates in the RANAP paging message whether the RNC shall
AN co-ordination paging
paging, the RNC shall check whether the UE has other CN domain signaling connections
ng domain connection. If so and the UE is in Cell_DCH or Cell_FACH state, the paging
e transmitted on the already connected DCCH on the radio interface. if so and the UE is in Cell_PCH or
,the paging message shall be transmitted on the PCCH on the radio interface. If no, the paging message
ted on the PCCH.
ting paging, the RNC need not check whether the UE has other CN domain signaling connections
ng domain connection but directly transmit the paging message on the PCCH in the CN
area.
gnated paing : The UTRAN may initiate paging for a UE in Cell_PCH or URA_PCH state to trgiger
cedure to enable the transition to Cell_FACH state. In additon,the UTRAN may initiate paging for
eading of updated system information.
mode or in CELL_PCH or URA_PCH state, the RNC initiates the paging procedure by transmitting
E 1 message on the PCCH. For a UE in CELL_FACH or CELL_DCH state, the RNC initiates the
e by transmitting a PAGING TYPE 2 message on the DCCH
ction between UE and UTRAN.
to a UE, which is either in the RRC idle mode, or in the RRC connected mode sub-states
message from the CN has to be forwarded to the UE. . In this case, the UE adds the IE Paging
mitted on an existing ps connection (PMM-IDLE or PMM-CONNECTED). UTRAN has to page the
a.
_PCH about system information changes.
ives 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.
e DDCH and one DCCH to the user. Consequently, a connection between the UE and the 3G-
he 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
e and Parameters Description (Module II)
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)

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
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 (SIB1–SIB6, SIB10–SIB13, 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 13.1 Cell

System information block type 15.3 PLMN
System information block type 16 PLMN

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
references and scheduling information about the SIBs. The MIB is transmitted in every 8th radio frame on the P-CCPCH (on position SFN mo
most of the SIBs used within the system, the MIB may carry a value tag. The only exceptions are SIB 15.2, SIB 15.3 and SIB 16. If a value tag
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. SIB7,
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 transmi
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-M
- 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
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-M
- 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 informa
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 accordin
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, including their scheduling information and type. A MIB is valid in one cell. If a UE changes the cell, is must read the new cell‘s MIB. 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 and scheduling information for additional system information blocks. (The SBs are applied when the scheduling resources of MIB are
insufficient) Scheduling information for a system information block may only be included 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 and counters, which have to be 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 the RRC connected , if SIB 4 is 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 information lists. It is read and valid in the RRC connected mode , if SIB 6 is not available.
includes rapidly changed parameters (UL interference and dynamic persistence level. This SIB holds fast changing parameters. Therefore no value
tag is used for it. The UE has to read its 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 valid in the RRC sub-state CELL_DCH, as long as the UE did not get a Measurement Control message from UTRAN and SIB 12 is not
broadcasted
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 used when UE is switched to UTRAN. RB, The parameters are used during a handover to UTRAN. Consequently, these parameters stay
valid, when the UE is connected to GSM and GPRS.
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
dification Notification
ich have to be read by the UE. This requires a lot of battery power. Therefore, a Master Information Block (MIB) was introduced, which gives
on about the SIBs. The MIB is transmitted in every 8th radio frame on the P-CCPCH (on position SFN mod 8 = 0, and with a TTI of 20 ms). For
stem, the MIB may carry a value tag. The only exceptions are SIB 15.2, SIB 15.3 and SIB 16. If a value tag is unchanged, the corresponding
odified. Thus, there is no need for the UE to read the SIB. For the SIBs which have no value tag e.g. SIB7, It changes with each occurrence (based
used to inform the UE, where and when a specific system information is transmitted.
UE of system information modification: by a value tag and by a timer
should notify the new value tag for the MIB to the UE.
L_PCH state or URA_PCH state, UTRAN send a PAGING TYPE 1 message on the PCCH on all paging occasions in the cell to
ate, UTRAN sends a SYSTEM INFORMATION CHANGE INDICATION message on the BCCH to transmit the new MIB value tag.
YPE 1 message or SYSTEM INFORMATCHANGE INDICATION message from UTRAN, the UE shall read the changed information
ag.
pectively. When the timer expires, the UE shall consider the stored system information content invalid,start the timer, and re-acquire
a Timer consider the stored system information content invalid, start the timer, and re-acquire new SIB information. The UE may
ontent is needed
L_DCH sub-state are addressed directly by the RNC via the Measurement Control message
ster Information Block and Scheduling Block(s):
hall read the master information block. The UE may use the pre-defined scheduling information to locate the master information
ter information block, the UE shall:
SELECTED_PLMN has the value "GSM-MAP" and the IE "PLMN Type" has the value "GSM-MAP" or "GSM-MAP and ANSI-41",:
e master information block and verify that it is the selected PLMN, stored as "PLMN identity" in the variable SELECTED_PLMN.
SELECTED_PLMN has the value "ANSI-41 "and the IE "PLMN Type" has the value "ANSI-41" or "GSM-MAP and ANSI-41",:
er information block with the value tag stored for this cell and this PLMN in the variable VALUE_TAG.
for the master information block are stored: store the value tag into the variable VALUE_TAG for the master information block; read
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,
Idle
URA_PCH,CELL_DCH
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, Idle mode, (CELL_FACH, CELL_PCH, URA_PCH,
CELL_DCH (TDD only)) CELL_DCH (TDD only))
CELL_FACH, CELL_PCH, URA_PCH, CELL_DCH CELL_FACH, CELL_PCH, URA_PCH, CELL_DCH
(TDD only) (TDD only)
Idle mode, CELL_FACH, CELL_PCH, URA_PCH, Idle mode, CELL_FACH, CELL_PCH, URA_PCH,
CELL_DCH (TDD only) CELL_DCH (TDD only)
CELL_DCH CELL_DCH
Idle mode (CELL_FACH, CELL_PCH, URA_PCH,

Idle mode (CELL_FACH, CELL_PCH, URA_PCH)
CELL_DCH)
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,
CELL_DCH CELL_DCH
CELL_FACH, CELL_PCH, URA_PCH, CELL_DCH CELL_FACH, CELL_PCH, URA_PCH, CELL_DCH
Idle mode, CELL_FACH, CELL_PCH, URA_PCH,

Idle mode, CELL_FACH, CELL_PCH, URA_PCH
CELL_DCH

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

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

Expiration timer = MAX([320

Specified by the IE "Scheduling information" ms], SIB_REP *
ExpirationTimeFactor)


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

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 11(SIB 11)

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

>>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
value=hex2dec(0065)=101
Cell Identity=RNCid(12bits)+Cellid(16bits)
value=0000000010110111011110010010 => RNCid=bin2dec(000000001011)=11 and Cellid=bin2dec(0111011110010010)=30610
>>>Cell Selection and Reselection Algorithm and parameters description (Module II)
value=2dB(step of 2 dB)
value=-18dBm
value= ((-58*2)+1)= –115 dBm e.g. –57 means –113 dBm; …; –13 means -25 dBm
value=1s(step of 1s)
value=24dBm
>>>Cell Access Restriction parameters description (Module II)
>>>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=20attempts
value=8attempts
value=
value=-105dBm
>>>see "Parameters description"
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
0010010)=30610
L3 Messages - Location Update Proced

UE NodeB S-RNC
1.RRC: RRC Connection Request (RACH)
2.NBAP:Radio Link Setup Req

Start Rx
3.NBAP:Radio Link Setup Resp.
5.ALCAP: Iub User Plane Setup

RRC Connection Establishment Timing
Start Tx
6.RRC: RRC Connection Setup (FACH)
L1 Synchonization
NBAP:Synchonization Indicator
7.RRC: RRC Connection Setup Completed (DCH)
1.RRC: Initial Direct Transfer (MM: Location Update Request)
Optional : Authentication and Securitty Mode Control may exist depends on Operator's settin
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
3.NBAP: Radio Link Deletion

Request

Response
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 as an example.
2 If IP transport is applied to the Iub interface, no ALCAP procedure is performed on the Iub interface
after radio links are set up or deleted.
ion Update Procedure
S-RNC CN
RRC Connection Setup
>>RRC Procedure description
2.RANAP: Initial UE Message (MM: Location Update Request)
depends on Operator's setting (refer to signaling in AMR call precedures)

Location Update
3.RANAP: Direct Transfer (MM: Location Update Accept)
6.RANAP: Direct Transfer
1.RANAP: Iu Release Command
ALCAP: Iu User Plane Release Iu release
2..RANAP: Iu Release Complete

RRC connection Release
RRC connection setup procedure is performed for the UE to set up a signaling connection t
Triggering Conditions : The UE in idle mode intitiates the RRC connection setup procedure wh
When the SRNC receives an RRC CONNECTION REQUEST message from the UE, the Radio Re
algorithm. If accepting the request, the RRM module further determines whether to set up the 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 SRNC through the uplink CC
2.Based on the cause in the RRC connection request and the system resource status, the SRNC d
resources, and L1 and L2 resources. Then the SRNC sends a RADIO LINK SETUP REQUEST me
resources required for an RRC connection.
3.The NodeB responds with a RADIO LINK SETUP RESPONSE message to the SRNC after succ
RRC Connection Setup 4.The SRNC uses the ALCAP protocol to set up the Iub user plane transport bearer and performs
for the ATM-based Iub interface only.
5.The SRNC sends an RRC CONNECTION SETUP message to the UE through the downlink CCC
>>RRC Procedure description 6. UE and NodeB initiate L1 Synchronization. NodeB sends NBAP:Synchonization Indicator mess
7. The UE sends an RRC CONNECTION SETUP COMPLETE message to the SRNC through the
RRC connection setup procedure ends.
If the RNC judges that the RRC connection request cannot be set up (for instance, due to insufficie
indicates the reject reason in the message
The location update procedure is performed to update the location of a UE.
Triggering Conditions : An RRC connection is set up between the UE and the Serving RNC (SRN
Location Update The procedure is described as follows:
1.The UE sends an INITIAL DIRECT TRANSFER message to the SRNC through the RRC connec
2.The SRNC sends an INITIAL UE MESSAGE to the CS service domain of the CN through the Iu
Mobile Subscriber Identity (TMSI),International Mobile Subscriber Identity (IMSI), and Location Are
routing area update. The message indicates ATTACH REQUEST and contains the Routing Area Id
3.The CN updates the location area information of the UE and saves the new LAI. The CN might a
indicates LOCATION UPDATE ACCEPT and contains the TMSI that is assigned to the UE.For rou
authentication and ciphering. Then, the CN sendsa DIRECT TRANSFER message to the SRNC. T
4.The SRNC transparently sends the contents of the DIRECT TRANSFER message to the UE thro
5.The UE receives the LOCATION UPDATE ACCEPT information and sends an UPLINK DIRECT
area update, it is the ATTACH ACCEPT information that the UE receives.
6.The SRNC transparently sends the contents of the UPLINK DIRECT TRANSFER messageto the
Iu release
For routing area update, it is ATTACH COMPLETE that the DIRECT TRANSFER message ind
The Iu release procedure is performed for the CN to release an Iu connection and all the UTR
Triggering Conditions: The Iu release procedure can be triggered in one of the following conditio
for example,sending an IU RELEASE REQUEST message,The Serving Radio Network Subsystem
RRC connection Release
1.The CN sends an IU RELEASE COMMAND message to the SRNC to initiate the Iu release proc
NOTE After sending the IU RELEASE COMMAND message, the CN will not send further RANAP
2.The SRNC releases the related UTRAN resources and then sends an IU RELEASE COMPLETE
The RRC Connection Release procedure is performed to release the signaling connection and a
Triggering Conditions: After a n RAB is released,the SRNC judges whether the RRC connection
connection release procedure.
The procedure shown is described as follows: based on the resouce occupied by the RRC con
connection from DCH and release of an RRC connection from CCH (If an RRC connection needs
RRC connection on the CCH is released)
1.The SRNC sends an RRC CONNECTION RELEASE message to the UE through the DCCH.
(NOTE: The SRNC may send the RRC CONNECTION RELEASE message several times to incre
retransmissions and the transmission intervals are determined by the SRNC. If the SRNC does no
COMPLETE message from the UE after sending the RRC CONNECTION RELEASE message for
2.The UE sends an RRC CONNECTION RELEASE COMPLETE message to the SRNC.
3.The SRNC sends a RADIO LINK DELETION REQUEST message to the NodeB,requesting the N
4.After releasing the resources, the NodeB sends a RADIO LINK DELETION RESPONSE messag
5.(Optional; required for the ATM-based Iub interface only) The SRNC uses the ALCAP protocol to
ends.
up a signaling connection to the SRNC. RRC connection setup is always initiated by the UE. One UE has a maximum of one RRC connect
nection setup procedure when the NAS of the UE requests the establishment of a signaling connection
e from the UE, the Radio Resource Management (RRM) module of the RNC determines whether to accept or reject theRRC connection req
s whether to set up the RRC connection on a Dedicated Channel (DCH)or on a Common Channel (CCH), based on a specific RRM algorith
RNC through the uplink CCCH(RACH), requesting the establishment of an RRC connection.
esource status, the SRNC determines to set up the RRC connection on a DCH and allocates the Radio NetworkTemporary Identity(RNTI),r
LINK SETUP REQUEST message to the NodeB, requesting the NodeB to allocate the specific radio link
age to the SRNC after successfully preparing the resources.

nsport bearer and performs the synchronization between the SRNC and the NodeB. This procedure is optional. It is required
E through the downlink CCCH (FACH). The message contains the information about the DCH allocated by the SRNC.
chonization Indicator message to SRNC when the uplink enter "In-Sync" state
e to the SRNC through the uplink Dedicated Control Channel (DCCH) that is just set up. The message indicates that the
or instance, due to insufficient resources), it directly sends an RRC CONNECTION REJECT message to the UE, and
n of a UE.
and the Serving RNC (SRNC)
C through the RRC connection. The message contains the Non Access Stratum (NAS) information to be sent to the CN by the UE.
in of the CN through the Iu interface. The message indicates LOCATION UPDATE REQUEST and containsthe UE information, such as the
tity (IMSI), and Location Area Identity (LAI).The SRNC sends an INITIAL UE MESSAGE to the PS service domain of the CN throughthe Iu i
ontains the Routing Area Identity (RAI)
he new LAI. The CN might also perform authentication and ciphering. Then, the CN sends a DIRECT TRANSFER message to the SRNC. T
assigned to the UE.For routing area update, the CN updates the routing area information of the UE and savesthe new RAI. The CN might a
ER message to the SRNC. The message indicates ATTACH ACCEPTand contains the TMSI that is assigned to the UE
FER message to the UE through a DOWNLINK DIRECT TRANSFER message.

sends an UPLINK DIRECT TRANSFER message to the SRNC. The message contains the information suchas the NAS information and the
s.
TRANSFER messageto the CN through a DIRECT TRANSFER message. The DIRECT TRANSFER messageindicates TMSI REALLOCAT
TRANSFER message indicates.

connection and all the UTRAN resources related only to that Iu connection.
one of the following conditions: The transaction between the UE and the CN is complete,The UTRAN requests the CN to release the resour
g Radio Network Subsystem (SRNS) is relocated.4.The SRNS relocation is canceled after a relocation resource allocation procedure iscom
o initiate the Iu release procedure. The message indicates the cause for the release of the signaling connection.
ill not send further RANAP connection-oriented messages on this particular connection.
n IU RELEASE COMPLETE message to the CN.
e signaling connection and all radio bearers between UE and the UTRAN
hether the RRC connection carries any other RAB or the UE. If judging that the RRC connection does not carry other RAB of the UE,the SR
e occupied by the RRC connection,there are two types of RRC connection release procedure: release of an RRC
an RRC connection needs to be released after a successful outgoing call,, the RRC connection on the DCH is released and if a radio beare
e UE through the DCCH.

sage several times to increase the probability of proper reception of the message by the UE. The RRC SNs of these messages are the sam
SRNC. If the SRNC does not receive an RRC CONNECTION RELEASE
ON RELEASE message for four times, the SRNC judges that the UE has released the RRC connection.)
age to the SRNC.
the NodeB,requesting the NodeB to delete the radio link resources in the NodeB.
ETION RESPONSE message to the SRNC.
uses the ALCAP protocol to initiate an Iub user plane transport bearer release procedure. Then, the RRC connection release procedure
E has a maximum of one RRC connection at a time.
ion
accept or reject theRRC connection request, based on a specific

CCH), based on a specific RRM algorithm. Typically, an RRC
dio NetworkTemporary Identity(RNTI),radio

link
s optional. It is required
ted by the SRNC.
ge indicates that the
ge to the UE, and
o be sent to the CN by the UE.

ontainsthe UE information, such as the Temporary
ervice domain of the CN throughthe Iu interface for
TRANSFER message to the SRNC. The message

and savesthe new RAI. The CN might also perform
ssigned to the UE
on suchas the NAS information and the CN ID.For routing
R messageindicates TMSI REALLOCATION COMPLETE.

N requests the CN to release the resources on the Iu interface by,
on resource allocation procedure iscomplete.
connection.
es not carry other RAB of the UE,the SRNC initiates an RRC
se of an RRC
he DCH is released and if a radio bearers fails to be setup ,the
RC SNs of these messages are the same. The number of
ion.)
RRC connection release procedure

RRC:RRC Connection Request (RACH) >>"RRC Connection Request Descriptio
>>"Geographical and UTRAN Entity Iden
value=hex2dec(4)=4 , hex2dec(5)=5
value=hex2dec(75 AA)= 30122
value= registration(Location update
value=(-24+ (36/2))= -6 dB (Serving c
value=hex2dec(91)=145 (Neighbour'
value=CPICH Ec/Io invalid
RRC:RRC Connection Setup (FACH) >>"RRC Connection Setup Description"

value=UE capable to support FDD ,
value=UE capable to support GSM
value=Signaling Radio Bearer Inform
value=Radio Bearer Mapping

value=BLER Target= -20 dB
value=MaxAllowedULTxPower=24 d
value=(-37*2)= -74 dBm (step of 2 d

value= use Closed Loop Power Con
value= use long SC on Uplink
value=Spreading Factor 64 (Uplink)
value=Spreading Factor 128 (Downl

value=Primary Scrambling code=38
Cell Identity=RNCid(12bits)+Cellid(1
value=0000000000010101101011001
RRC:RRC Connection Setup Complete (DCCH) >>"RRC Connection Setup Complete De

value= UE (Powerclass3) maximum
value= support GSM (Dual Mode UM
value= Chipering Algorithm A5/3
value= support Compressed Mode (

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= registration(Location update)
value=(-24+ (36/2))= -6 dB (Serving cell's CPICH Ec/No)
value=hex2dec(91)=145 (Neighbour's Primary Scrambling Code)

>>"RRC Connection Setup Description"
>>"Geographical and UTRAN Entity Identifiers"

value=UE capable to support FDD , not TDD
value=Signaling Radio Bearer Information Setup ,RB-1

value=MaxAllowedULTxPower=24 dBm
value=(-37*2)= -74 dBm (step of 2 dB) Default Constant DPCCH_Power_offset CPICH_RSCP

-22 -74 -80
-22 -74 -70
Note :DPCCH_Power_offset is configured by RNC and delivered to UE in RRC Connection Set
value= use Closed Loop Power Control Algorithm1
value=Spreading Factor 128 (Downlink)

value=Spreading Factor 128 (Downlink)
>>"RRC Connection Setup Complete Description"

value= UE (Powerclass3) maximum transmitted power =24 dBm
value= support GSM (Dual Mode UMTS<>GSM)
value= support Compressed Mode (CM) uplink and downlink

value= MCC=456
value= MNC=02
value=hex2dec(75AA)=30122
PCPICH Power UL Interference UL DPCCH Initial Power
33 -85 6
33 -85 -4
d delivered to UE in RRC Connection Setup.
1011110010010)=23242
L3 Messages - AMR Voice (MOC) Call Proce

UE NodeB S-RNC

Start Rx
RRC Connection Establishment Timing Start Tx
L1 Synchonization
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)
3.NBAP: Radio Link

Reconfiguration Prepare
4.NBAP: Radio Link

Reconfiguration Ready
6.RRC: Radio Bearer Setup
7.NBAP: Radio Link

Reconfiguration Commit
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 Established
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)
2.RRC:RRC Connection Release Complete

Request

Response
5,.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 as 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
ce (MOC) Call Procedure
S-RNC CN
>>RRC Procedure Description
1.RRC Connection Setup
SCCP: CR (Connection Request)

2.Signalling Connection Setup
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)

&Authentication.3
RANAP: Common ID (IMSI) Security Mode Control
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. 5
4.Call 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)
ablished
6.Conversation
2.RANAP: Direct Transfer (CC: Disconnect)
3.RANAP: Direct Transfer (CC: Release)
7.Call Release
6.RANAP: Direct Transfer (CC: Release Complete)
8.ALCAP: Iu User Plane Release
9.RANAP: Iu Release Complete
8.RRC Connection Release

RRC connection setup procedure is performed for the UE to set up a signaling connection to the SRNC
connection at a time.
Triggering Conditions : The UE in idle mode intitiates the RRC connection setup procedure when the NA
CONNECTION REQUEST message from the UE, the Radio Resource Management (RRM) module of the RN
algorithm. If accepting the request, the RRM module further determines whether to set up the RRC connectio
algorithm. Typically, an RRC connection is set up on the DCH.

1.The UE sends an RRC CONNECTION REQUEST message to the SRNC through the uplink CCCH(RACH
edure Description 2.Based on the cause in the RRC connection request and the system resource status, the SRNC determines
Identity(RNTI),radio resources, and L1 and L2 resources. Then the SRNC sends a RADIO LINK SETUP REQ
required for an RRC connection.
nnection Setup
3.The NodeB responds with a RADIO LINK SETUP RESPONSE message to the SRNC after successfully pr
4.The SRNC uses the ALCAP protocol to set up the Iub user plane transport bearer and performs the synchr
5.The SRNC sends an RRC CONNECTION SETUP message to the UE through the downlink CCCH (FACH)
6. UE and NodeB initiate L1 Synchronization. NodeB sends NBAP:Synchonization Indicator message to SRN
7. The UE sends an RRC CONNECTION SETUP COMPLETE message to the SRNC through the uplink Ded
RRC connection setup procedure ends.
If the RNC judges that the RRC connection request cannot be set up (for instance, due to insufficient resourc
reason in the message
The signaling connection setup procedure is performed to exchange the NAS (Non Access Stratum)
ng Connection Setup Triggering Conditons: The UE sends a direct transfer message to initiate the signaling connection setup pr

1.The UE sends an INITIAL DIRECT TRANSFER message to the SRNC through the RRC connection. The m
2.The SRNC receives the INITIAL DIRECT TRANSFER message from the UE and sends an INITIAL UE ME
to be sent to the CN by the UE. The content of the NAS information is CM SERVICE REQUEST.
3.The CN sends a response message to the SRNC.
-If accepting the request, the CN sends a CONNECTION CONFIRM (CC) message to the SRNC. The mes
confirms that the signaling connection is set up.
-If rejecting the request, the CN sends a CONNECTION REJECT (CJ) message to the SRNC. The messag
confirms that the signaling connection fails to be setup and then initiates the RRC release procedure.
tication.3
Mode Control
The authentication and security mode control procedure is performed for the UE and the network t
algorithm and ciphering algorithm. This procedure ensures integrity and correctness of signaling
Triggerring Conditions: The UE and the CN exchange signaling. The network initiates the authentication an

1.The CN sends a DIRECT TRANSFER message to the SRNC. The message indicates AUTHENTICATION
2.The SRNC transparently sends the contents of the DIRECT TRANSFER message to the UE through a DO
3.The UE sends an UPLINK DIRECT TRANSFER message to the SRNC.
4.The SRNC transparently sends the contents of the UPLINK DIRECT TRANSFER messageto the CN throu
Subscriber Identity Module (USIM) judges that the authentication is successful, the UE returns a message wi
5.The CN sends a SECURITY MODE COMMAND message to the SRNC to initiate the security mode contro
protection algorithms.
6.The SRNC sends a SECURITY MODE COMMAND message to the UE to inform the UE of the integrity pro

Subscriber Identity Module (USIM) judges that the authentication is successful, the UE returns a message wi
protection algorithms.
7.The UE sends a response message to the SRNC.
-If the integrity protection and ciphering algorithms are configured successfully, the UE sends a SECU
MODE COMMAND COMPLETE message to the CN.The message contains the information about the integri
-If the UE does not support the integrity protection and ciphering algorithms, the UE sends a SECURIT
information and the reason for the failure. The SRNC then sends a SECURITY MODE COMMAND REJECT
The RANAP:Common ID message is used to transport the permanent UE Identity(IMSI) to SRNC
The call setup procedure is performed to set up a call.

r Setup. 5 Triggering Conditions: The UE initiates a call

1.The UE sends an UPLINK DIRECT TRANSFER message to the SRNC. The message contains the numbe
3.The CN sends a DIRECT TRANSFER message to the SRNC. The message indicates CALL PROCEEDING
5. A Radio Access Bearer (RAB) is set up. (see more details in RAB Setup Procedure below)
6. When the called terminal rings, the CN sends a DIRECT TRANSFER message to the SRNC. The messag
8.The CN sends a DIRECT TRANSFER message to the SRNC. The message indicates CONNECT, which m
11.The SRNC transparently sends the contents of the UPLINK DIRECT TRANSFER message to the CN thro
The Radio Bearer Setup procedure shown is described as follows:

1.The CN sends an RAB ASSIGNMENT REQUEST message to the SRNC to initiate the RAB setup procedu
2.(Optional; applicable to the ATM-based Iu-CS interface only) The SRNC maps the Quality of Service (QoS)
characteristic parameters. Based on the AAL2 link characteristic parameters,the ALCAP on the Iu interface in
3.The SRNC sends a RADIO LINK RECONFIGURATION PREPARE message to the NodeB, requesting the
4.The NodeB allocates the associated resources and then sends a RADIO LINKRECONFIGURATION READ
5.(Optional; required for the ATM-based Iub interface only) The Iub ALCAP at the SRNC initiates an Iub user
by exchanging 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 message to theNodeB.
8.After performing the radio bearer setup, the UE sends a RADIO BEARER SETUP COMPLETE message to
9.The SRNC sends an RAB ASSIGNMENT RESPONSE message to the CN. The RAB isset up.
The procedure when RAB Setup Failure shown is described as follows:
2.The SRNC sends an RAB ASSIGNMENT RESPONSE message to the CN. The message indicates the ID
The call release procedure is performed to release services and resources after a call ends.
Triggering Conditions : A call ends and the calling party hangs up

hanged up.

hanged up.
3.The CN sends a DIRECT TRANSFER message to the SRNC. The message indicates RELEASE to reques
7.The CN sends an IU RELEASE COMMAND message to the SRNC to request call release on the Iu interfa
8.(Optional; applicable to the ATM-based Iu-CS interface only) The ALCAP protocol on the Iu interface initiate
9.The SRNC sends an IU RELEASE COMPLETE message to the CN.
The RRC Connection Release procedure is performed to release the signaling connection and all radio be
Triggering Conditions: After a n RAB is released,the SRNC judges whether the RRC connection carries an
initiates an RRC connection release procedure.
The procedure shown is described as follows: based on the resouce occupied by the RRC connection,th
of an RRC connection from CCH (If an RRC connection needs to be released after a successful outgoing cal
fails to be setup ,the RRC connection on the CCH is released)
(NOTE: The SRNC may send the RRC CONNECTION RELEASE message several times to increase the pro
the same. The number of retransmissions and the transmission intervals are determined by the SRNC. If the
UE after sending the RRC CONNECTION RELEASE message for four times, the SRNC judges that the UE
onnection Release
3.The SRNC sends a RADIO LINK DELETION REQUEST message to the NodeB,requesting the NodeB to d
4.After releasing the resources, the NodeB sends a RADIO LINK DELETION RESPONSE message to the S
5.(Optional; required for the ATM-based Iub interface only) The SRNC uses the ALCAP protocol to initiate an
procedure ends.
signaling connection to the SRNC. RRC connection setup is always initiated by the UE. One UE has a maximum of one RRC
ion setup procedure when the NAS of the UE requests the establishment of a signaling connection When the SRNC receives an RRC
agement (RRM) module of the RNC determines whether to accept or reject theRRC connection request, based on a specific
ether to set up the RRC connection on a Dedicated Channel (DCH)or on a Common Channel (CCH),based on a specific RRM
through the uplink CCCH(RACH), requesting the establishment of an RRC connection.

rce status, the SRNC determines to set up the RRC connection on a DCH and allocates the Radio NetworkTemporary
ends a RADIO LINK SETUP REQUEST message to the NodeB, requesting the NodeB to allocate the specific radio link resources
o the SRNC after successfully preparing the resources.

t bearer and performs the synchronization between the SRNC and the NodeB. This procedure is optional. It is required
ough the downlink CCCH (FACH). The message contains the information about the DCH allocated by the SRNC.
nization Indicator message to SRNC when the uplink enter "In-Sync" state
the SRNC through the uplink Dedicated Control Channel (DCCH) that is just set up. The message indicates that the
stance, due to insufficient resources), it directly sends an RRC CONNECTION REJECT message to the UE, and indicates the reject
e the NAS (Non Access Stratum) information between the UE and the CN.
he signaling connection setup procedure.
rough the RRC connection. The message contains the initial NAS information to be sent to the CN by the UE.
UE and sends an INITIAL UE MESSAGE to the CN over the Iu interface. The INITIAL UE MESSAGE contains the NAS information
SERVICE REQUEST.
message to the SRNC. The message indicates that the SCCP connection is set up. After receivingthe message, the SRNC
ssage to the SRNC. The message indicates that the SCCP connection fails to be set up. After receiving the message, the SRNC
e RRC release procedure.
med for the UE and the network to implement bi-directional authentication and to negotiate and configure the integrity protection
rectness of signaling
work initiates the authentication and securitymode control procedure
ge indicates AUTHENTICATION REQUEST.

message to the UE through a DOWNLINK DIRECT TRANSFER message.
NSFER messageto the CN through a DIRECT TRANSFER message, indicating AUTHENTICATION RESPONSE. If the UMTS
sful, the UE returns a message with an XRES IE.
o initiate the security mode control procedure. The message contains the information about the supported ciphering and integrity
inform the UE of the integrity protection and ciphering algorithms that the UTRAN selects.
he message contains the number of the called party and the information about the bearer capability of the call.
NSFER messageto the CN through a DIRECT TRANSFER message.
ge indicates CALL PROCEEDING and contains the information about the negotiated bearer capability of the call.
Procedure below)
ssage to the SRNC. The message indicates ALERTING.
ge indicates CONNECT, which means that the called party has answered the call.
ANSFER message to the CN through a DIRECT TRANSFER message, indicating CONNECT ACKNOWLEDGE.
to initiate the RAB setup procedure.

maps the Quality of Service (QoS) parameters for the RAB to the AAL2 link characteristic parameters and radio resource
s,the ALCAP on the Iu interface initiates an Iu user plane transport bearer setup procedure.
age to the NodeB, requesting the NodeB to prepare for adding one or more DCHs to the existing radio links for carrying the RAB.
LINKRECONFIGURATION READY message to the SRNC.
at the SRNC initiates an Iub user plane transport bearer setup procedure. The NodeB and the SRNC perform synchronization
e protocol.
e to theNodeB.
SETUP COMPLETE message to the SRNC.
N. The RAB isset up.
:
N. The message indicates the ID of the RAB that fails to be set up and the reason for the failure.
ces after a call ends.
NSFER messageto the CN through a DIRECT TRANSFER message, indicating DISCONNECT. This content informs the CN that the UE ha
naling connection and all radio bearers between UE and the UTRAN
er the RRC connection carries any other RAB or the UE. If judging that the RRC connection does not carry other RAB of the UE,the SRNC
cupied by the RRC connection,there are two types of RRC connection release procedure: release of an RRC connection from DCH and rele
ed after a successful outgoing call,, the RRC connection on the DCH is released and if a radio bearers
through the DCCH.

several times to increase the probability of proper reception of the message by the UE. The RRC SNs of these messages are
e determined by the SRNC. If the SRNC does not receive an RRC CONNECTION RELEASE COMPLETE message from the
es, the SRNC judges that the UE has released the RRC connection.)
to the SRNC.
NodeB,requesting the NodeB to delete the radio link resources in the NodeB.
N RESPONSE message to the SRNC.
the ALCAP protocol to initiate an Iub user plane transport bearer release procedure. Then, the RRC connection release
a maximum of one RRC
hen the SRNC receives an RRC

st, based on a specific
ased on a specific RRM
tworkTemporary
specific radio link resources
nal. It is required
the SRNC.
cates that the
e UE, and indicates the reject
he UE.
ontains the NAS information
message, the SRNC
g the message, the SRNC
ure the integrity protection
ESPONSE. If the UMTS
ed ciphering and integrity

the call.
of the call.
WLEDGE.
nd radio resource
links for carrying the RAB.
perform synchronization
ontent informs the CN that the UE has

carry other RAB of the UE,the SRNC
n RRC connection from DCH and release
s of these messages are

ETE message from the
onnection release
value=hex2dec(2908)= 10504
value= OriginatingConversationalca
value=(-24+ (43/2))=-2.5 dB
value=hex2dec(60)=96(Neighbour's


value=00000000101101110111100100

value= not support GSM (Locked UM
value= UE support Band fdd2100 M


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)

value= Call B-Party number =
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)

RC Connection Request Description"
eographical and UTRAN Entity Identifiers"
e=hex2dec(5)=5 , hex2dec(2)=2 ,hex2dec(0)=0 --> MCC=520
e=hex2dec(0)=0 , hex2dec(1)=1 --> MNC=01
e=hex2dec(2908)= 10504
e= OriginatingConversationalcall (CS MOC)
e=(-24+ (43/2))=-2.5 dB
e=hex2dec(60)=96(Neighbour's Primary Scrambling Code)

e=CPICH Ec/Io invalid
RC Connection Setup Description"
e=hex2dec(2908)= 10504
e=UE capable to support FDD , not TDD
e=UE capable to support GSM
e=Signaling Radio Bearer Information Setup ,RB-1
e=Radio Bearer Mapping

e=BLER Target= -20 dB
e=MaxAllowedULTxPower=24 dBm
e=(-47*2)= -94 dBm (step of 2 dB) 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.
e= use Closed Loop Power Control Algorithm1
e= use long SC on Uplink
e=Spreading Factor 64 (Uplink)
e=Spreading Factor 128 (Downlink)

e=Primary Scrambling code=97
Identity=RNCid(12bits)+Cellid(16bits)
e=0000000010110111011110010010 => RNCid=bin2dec(000000001011)=11 and Cellid=bin2dec(0111011110010010)=30610
RC Connection Setup Complete Description"

e= not support GSM (Locked UMTS Mode)
e= Chipering Algorithm A5/3
e= UE support Band fdd2100 MHz

e= UE (Powerclass3) maximum transmitted power =24 dBm
e= support Compressed Mode (CM) uplink and downlink

value= Call B-Party number = 0812713339
>>"Radio Bearer Description"
value= SF64(uplink)-> AMR 12.2
value= SF128(downlink)-> AMR 12.2
UL Interference UL DPCCH Initial Power
-105 -14
-105 -24
E in RRC Connection Setup.
11110010010)=30610
L3 Messages -AMR Voice Call (MTC) Call Proc
UE NodeB S-RNC
*** 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 Setup
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 (CC: Setup)
3. RRC: Uplink Direct Transfer (CC: Call Confirmed)
3. NBAP: Radio Link

4. NBAP: Radio Link

5. ALCAP: Iub User Plane Setup
6. RRC: Radio Bearer Setup
7. NBAP: Radio Link

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 Established
RRC: Downlink Direct Transfer (CC: Disconnect)

RRC: Uplink Direct Transfer (CC: Release)
RRC: Downlink Direct Transfer (CC: Release Complete)
NBAP: Radio Link Deletion

Request

Response
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 theIu-CS
interface after an RAB is set up or a call is released
Call (MTC) Call Procedure
S-RNC CN
1. RANAP: Paging Paging.1
2.RRC ConnectionSetup
2.SCCP: CR (Connection Request)
3.Signalling Connection Setu

2. RANAP: Initial UE Message (MM: Paging Response)
RANAP: Common ID (IMSI) Authentication & Security.4

Mode Control
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 Setup.5
4.Call Setup
7. RANAP: Direct Transfer (CC: Alerting)
9. RANAP: Direct Transfer (CC: Connect)
10. RANAP: Direct Transfer (CC: Connect Acknowledge)
ablished
6.Conversation

RANAP: Direct Transfer (CC: Release Complete) 7.Call Release
RANAP: Iu Release Command
ALCAP: Iur User Plane Release
RANAP: Iu Release Complete

Paging Procedure The paging procedure is performed when the CN calls a UE.
Triggering Conditions: A Terminal calls the UE
The Paging Procedure in Idle, Cell_PCH and URA-PCH modes is described as follows;
1.The CN sends a PAGING message to the SRNC.
2.The SRNC initiates the paging procedure by sending a PAGING TYPE 1 message to the UE th
paging occasion is related to the International Mobile Subscriber Identity (IMSI) of the UE. The U
proper receptionof the paging message by the UE.)
3.The UE in idle mode or in PCH state monitors the paging and receives the paging message fro
The Paging Procedure in Cell_DCH and Cell_FACH mode is described as follows;

1.The CN sends a PAGING message to the SRNC.
2.The SRNC initiates the paging procedure by sending a PAGING TYPE 2 message to the UE th
3.The UE receives the PAGNG TPYE 2 message, reads it, and then reports to the NAS the infor
procedure ends
ConnectionSetup
ocedure Description
RRC connection setup procedure is performed for the UE to set up a signaling connection
maximum of one RRC connection at a time.
Triggering Conditions: The UE in idle mode intitiates the RRC connection setup procedure w
When the SRNC receives an RRC CONNECTION REQUEST message from the UE, the Radio R
reject theRRC connection request, based on a specific algorithm. If accepting the request, the R
Channel (DCH)or on a Common Channel (CCH), based on a specific RRM algorithm. Typically, a

1.The UE sends an RRC CONNECTION REQUEST message to the SRNC through the uplink C
2.Based on the cause in the RRC connection request and the system resource status, the SRNC
nalling Connection Setup NetworkTemporary Identity (RNTI), radio resources, and L1 and L2 resources. Then the SRNC s
NodeB to allocate the specific radio link resources required for an RRC connection.
3.The NodeB responds with a RADIO LINK SETUP RESPONSE message to the SRNC after suc
4.The SRNC uses the ALCAP protocol to set up the Iub user plane transport bearer and perform
It is required for the ATM-based Iub interface only.
5.The SRNC sends an RRC CONNECTION SETUP message to the UE through the downlink CC
SRNC.
6. UE and NodeB initiate L1 Synchronization. NodeB sends NBAP:Synchonization Indicator mes
7. The UE sends an RRC CONNECTION SETUP COMPLETE message to the SRNC through th
indicates that the RRC connection setup procedure ends.
If the RNC judges that the RRC connection request cannot be set up (for instance, due to insuffic
UE, and indicates the reject reason in the message
ntication & Security.4

Control
The signaling connection setup procedure is performed to exchange the NAS (Non Acce
Triggering Conditions: The UE sends a direct transfer message to initiate the signaling

1.The UE sends an INITIAL DIRECT TRANSFER message to the SRNC through the RRC conne
UE.
2.The SRNC receives the INITIAL DIRECT TRANSFER message from the UE and sendsan INIT
The signaling connection setup procedure is performed to exchange the NAS (Non Acce
Triggering Conditions: The UE sends a direct transfer message to initiate the signaling

1.The UE sends an INITIAL DIRECT TRANSFER message to the SRNC through the RRC conne
UE.
2.The SRNC receives the INITIAL DIRECT TRANSFER message from the UE and sendsan INIT
contains the NAS information to be sent to the CN by the UE. The content ofthe NAS information
-If accepting the request, the CN sends a CONNECTION CONFIRM (CC) message tothe SRN
message, the SRNC confirms that the signaling connection is set up.
-lf rejecting the request, the CN sends a CONNECTION REJECT (CJ) message to the SRNC.
message, the SRNC confirms that the signaling connection fails to be setup and then initiates th
The authentication and security mode control procedure is performed for the UE and t
integrity protection algorithm and ciphering algorithm. This procedure ensures integrity and corre
Triggerring Conditions: The UE and the CN exchange signaling. The network initiates the auth
Bearer Setup.5 The procedure shown is described as follows:

1.The CN sends a DIRECT TRANSFER message to the SRNC. The message indicates AUTHEN
2.The SRNC transparently sends the contents of the DIRECT TRANSFER message to the UE th
Call Setup 3.The UE sends an UPLINK DIRECT TRANSFER message to the SRNC.
4.The SRNC transparently sends the contents of the UPLINK DIRECT TRANSFER messageto t
RESPONSE. If the UMTS Subscriber Identity Module (USIM) judges that the authentication is su
5.The CN sends a SECURITY MODE COMMAND message to the SRNC to initiate the security m
ciphering and integrity protection algorithms.
6.The SRNC sends a SECURITY MODE COMMAND message to the UE to inform the UE of the
-If the integrity protection and ciphering algorithms are configured successfully, the UE se
then sends a SECURITY MODE COMMAND COMPLETE message to the CN.The message co
UE uses.
-If the UE does not support the integrity protection and ciphering algorithms, the UE sends
contains the error information and the reason for the failure. The SRNC then sends a SECURITY
The RANAP:Common ID message is used to transport the permanent UE Identity(IMSI) to
Call Setup Procedure(Incoming Call) is performed to setup a call.
Triggering Conditions : A UE receiveds a call from the CN

1.The CN sends a DIRECT TRANSFER message to the SRNC. The message indicates SETUP
versation 4.The SRNC transparently sends the contents of the UPLINK DIRECT TRANSFER messageto t
messageindicates CALL CONFIRM and contains the information about the negotiated bearer ca
6. The UE sends an UPLINK DIRECT TRANSFER message to the SRNC.
called terminal to ring.
meansthat the called party has answered the call.
10.The CN sends a DIRECT TRANSFER message to the SRNC. The message indicatesCONNE
11.The SRNC transparently sends the contents of the DIRECT TRANSFER message to the UE t

6. The UE sends an UPLINK DIRECT TRANSFER message to the SRNC.
called terminal to ring.
meansthat the called party has answered the call.
10.The CN sends a DIRECT TRANSFER message to the SRNC. The message indicatesCONNE
11.The SRNC transparently sends the contents of the DIRECT TRANSFER message to the UE t

1.The CN sends an RAB ASSIGNMENT REQUEST message to the SRNC to initiate the RAB se
2.(Optional; applicable to the ATM-based Iu-CS interface only) The SRNC maps the Quality of S
radio resource characteristic parameters. Based on the AAL2 link characteristic parameters,the A
3.The SRNC sends a RADIO LINK RECONFIGURATION PREPARE message to the NodeB, req
4.The NodeB allocates the associated resources and then sends a RADIO LINKRECONFIGURA
5.(Optional; required for the ATM-based Iub interface only) The Iub ALCAP at the SRNC initiates
perform synchronization by exchanging uplink and downlink synchronization frames in the DCH
7.The SRNC sends a RADIO LINK RECONFIGURATION COMMIT message to the NodeB.
8.After performing the radio bearer setup, the UE sends a RADIO BEARER SETUP COMPLETE

2.The SRNC sends an RAB ASSIGNMENT RESPONSE message to the CN. The message indic
Connection Release
The Call Release procedure is performed to release services and resources after a ca
Triggering Conditions: A call ends and the calling party hangs up.

1.The CN sends a DIRECT TRANSFER message to the SRNC. The message indicates DISCON
RELEASE which requests release of the call.
5.The CN sends a DIRECT TRANSFER message to the SRNC. The message indicatesRELEAS
6.The SRNC transparently sends the contents of the DIRECT TRANSFER message to theUE th
7.The CN sends an IU RELEASE COMMAND message to the SRNC to request call releaseon th
8.(Optional; applicable to the ATM-based Iu-CS interface only) The ALCAP protocol on theIu inte
The RRC Connection Release procedure is performed to release the signaling connection and
Triggering Conditions: After a n RAB is released,the SRNC judges whether the RRC connectio
other RAB of the UE,the SRNC initiates an RRC connection release procedure.
The procedure shown is described as follows: based on the resouce occupied by the RRC co
connection from DCH and release of an RRC connection from CCH (If an RRC connection need
and if a radio bearers fails to be setup ,the RRC connection on the CCH is released)
(NOTE: The SRNC may send the RRC CONNECTION RELEASE message several times to incr
these messages are the same. The number of retransmissions and the transmission intervals are
RELEASE COMPLETE message from the UE after sending the RRC CONNECTION RELEASE
connection.)
The procedure shown is described as follows: based on the resouce occupied by the RRC co
and if a radio bearers fails to be setup ,the RRC connection on the CCH is released)
these messages are the same. The number of retransmissions and the transmission intervals are
RELEASE COMPLETE message from the UE after sending the RRC CONNECTION RELEASE
connection.)

3.The SRNC sends a RADIO LINK DELETION REQUEST message to the NodeB,requesting the
4.After releasing the resources, the NodeB sends a RADIO LINK DELETION RESPONSE messa
5.(Optional; required for the ATM-based Iub interface only) The SRNC uses the ALCAP protocol
connection release procedure ends.
he CN calls a UE.
s is described as follows;
G TYPE 1 message to the UE through the Paging Control Channel (PCCH) on an appropriate occasion. (NOTE The
dentity (IMSI) of the UE. The UTRAN may page the same UE on several occasions to increase the probability of
eceives the paging message from the network layer.The paging procedure ends.
escribed as follows;
G TYPE 2 message to the UE through the DCCH.

en reports to the NAS the information such as the paging cause and the paging record type identifier.The paging
o set up a signaling connection to the SRNC. RRC connection setup is always initiated by the UE. One UE has a
C connection setup procedure when the NAS of the UE requests the establishment of a signaling connection
ssage from the UE, the Radio Resource Management (RRM) module of the RNC determines whether to accept or
If accepting the request, the RRM module further determines whether to set up the RRC connection on a Dedicated
cific RRM algorithm. Typically, an RRC connection is set up on the DCH.
the SRNC through the uplink CCCH(RACH), requesting the establishment of an RRC connection.
stem resource status, the SRNC determines to set up the RRC connection on a DCH and allocates the Radio
2 resources. Then the SRNC sends a RADIO LINK SETUP REQUEST message to the NodeB, requesting the
RRC connection.
message to the SRNC after successfully preparing the resources.
e transport bearer and performs the synchronization between the SRNC and the NodeB. This procedure is optional.
the UE through the downlink CCCH (FACH). The message contains the information about the DCH allocated by the
P:Synchonization Indicator message to SRNC when the uplink enter "In-Sync" state
essage to the SRNC through the uplink Dedicated Control Channel (DCCH) that is just set up. The message
up (for instance, due to insufficient resources), it directly sends an RRC CONNECTION REJECT message to the
o exchange the NAS (Non Access Stratum) information between the UE and the CN.
ssage to initiate the signaling connection setup procedure.
SRNC through the RRC connection. The message contains the initial NAS information to be sent to the CN by the
from the UE and sendsan INITIAL UE MESSAGE to the CN through the Iu interface. The INITIAL UEMESSAGE
e is performed for the UE and the network to implement bi-directional authentication and to negotiate and configure the
ure ensures integrity and correctness of signaling.
. The network initiates the authentication and securitymode control procedure
The message indicates AUTHENTICATION REQUEST.

ANSFER message to the UE through a DOWNLINK DIRECT TRANSFER message.
e SRNC.
RECT TRANSFER messageto the CN through a DIRECT TRANSFER message, indicating AUTHENTICATION
ges that the authentication is successful, the UE returns a message with an XRES IE.
e SRNC to initiate the security mode control procedure. The message contains the information about the supported
o the UE to inform the UE of the integrity protection and ciphering algorithms that the UTRAN selects.
gured successfully, the UE sends a SECURITY MODE COMMAND COMPLETE message to the SRNC. The SRNC
age to the CN.The message contains the information about the integrity protection and ciphering algorithms that the
ring algorithms, the UE sends a SECURITY MODE COMMAND FAILURE message to the SRNC. The message
SRNC then sends a SECURITY MODE COMMAND REJECT message to the CN
rmanent UE Identity(IMSI) to SRNC
a call.
The message indicates SETUP and contains the number of the calling party and the bearer capability of the call.
e SRNC.
RECT TRANSFER messageto the CN through a DIRECT TRANSFER message. The DIRECT TRANSFER
about the negotiated bearer capability of the call.
AB Setup Procedure below)
e SRNC.
RECT TRANSFER messageto the CN through a DIRECT TRANSFER message, indicating ALERTING to request the
e SRNC.
RECT TRANSFER messageto the CN through a DIRECT TRANSFER message, indicating CONNECT. This
The message indicatesCONNECT ACKNOWLEDGE.

RANSFER message to the UE through a DOWNLINK DIRECT TRANSFER message.
lows:
ces and resources after a call ends.
angs up.
The message indicates DISCONNECT to inform the UE that the calling party has hanged up.
e SRNC.
RECT TRANSFER messageto the CN through a DIRECT TRANSFER message. The DIRECT TRANSFER messageindicates
The message indicatesRELEASE COMPLETE.

ANSFER message to theUE through a DOWNLINK DIRECT TRANSFER message.
RNC to request call releaseon the Iu interface. The message indicates the reason for the Iu release.
e ALCAP protocol on theIu interface initiates an Iu data transport bearer release procedure.
e CN.
se the signaling connection and all radio bearers between UE and the UTRAN
ges whether the RRC connection carries any other RAB or the UE. If judging that the RRC connection does not carry
se procedure.
esouce occupied by the RRC connection,there are two types of RRC connection release procedure: release of an RRC
CH (If an RRC connection needs to be released after a successful outgoing call,, the RRC connection on the DCH is released
e CCH is released)
to the UE through the DCCH.

E message several times to increase the probability of proper reception of the message by the UE. The RRC SNs of
nd the transmission intervals are determined by the SRNC. If the SRNC does not receive an RRC CONNECTION
RRC CONNECTION RELEASE message for four times, the SRNC judges that the UE has released the RRC
(NOTE The
bability of
he paging
UE has a
ction
o accept or
n a Dedicated
Radio
ting the
e is optional.
cated by the
sage
sage to the
e CN by the
MESSAGE
nd configure the
ATION
e supported
NC. The SRNC

hms that the
e message
the call.
ER
o request the
This
ER messageindicates
oes not carry
ease of an RRC
n the DCH is released
RRC SNs of
NECTION
RRC
RRC: Paging Type 1
RRC: RRC Connection Request (RACH) >>"RRC Connection Request Descrip
>>"Geographical and UTRAN Entity I
value=hex2dec(5)=5 , hex2dec(2)
value= terminatingConversationa
value=(-24+ (44/2))=-2.0 dB
value=hex2dec(6d)=109(Neighbo
RRC: RRC Connection Setup (FACH) >>"RRC Connection Setup Descriptio

>>"Geographical and UTRAN Entity I
value=UE capable to support FDD
value=Signaling Radio Bearer Inf

value=MaxAllowedULTxPower=2
value=(-48*2)= -96 dBm (step of 2
value= use Closed Loop Power C
value=Spreading Factor 64 (Uplin

value=Spreading Factor 128 (Dow
value=Primary Scrambling code=

value=Spreading Factor 128 (Dow
Cell Identity=RNCid(12bits)+Celli
value=000000001011011101111001
RRC:RRC Connection Setup Complete (DCCH) >>"RRC Connection Setup Complete

value= not support GSM (Locked

value= UE support Band fdd2100
value= UE (Powerclass3) maximu
value= support Compressed Mod

RANAP: Initial UE Message (MM: Paging Response)
RRC: Initial Direct Transfer (MM: Paging Response)

RRC: Downlink Direct Transfer (CC: Setup)

RANAP: Direct Transfer (CC: Call Confirmed)

RRC: Uplink Direct Transfer (CC: Call Confirmed)
RRC: Radio Bearer Setup >>"Radio Bearer Description"

value= SF64(uplink)-> AMR 12.2
value=Primary Scrambling code=
value= SF128(downlink)-> AMR 1

Cell Identity=RNCid(12bits)+Celli
value=000000001011011101111001
RRC: Uplink Direct Transfer (CC: Alerting)

RRC: Uplink Direct Transfer (CC: Connect)

RRC:Downlink Direct Transfer (CC: Connect Acknowledge)


RRC: Downlink Direct Transfer (CC: Disconnect)
RRC: Uplink Direct Transfer (CC: Release)


RRC: Uplink Direct Transfer (CC: RRC Connection Release)
=hex2dec(5)=5 , hex2dec(2)=2 ,hex2dec(0)=0 --> MCC=520
=hex2dec(0)=0 , hex2dec(1)=1 --> MNC=01
=hex2dec(2908)= 10504
= terminatingConversationalcall (CS MTC)
=(-24+ (44/2))=-2.0 dB
=hex2dec(6d)=109(Neighbour's Primary Scrambling Code)
=CPICH Ec/Io invalid

=hex2dec(5)=5 , hex2dec(2)=2 ,hex2dec(0)=0 --> MCC=520
=hex2dec(0)=0 , hex2dec(1)=1 --> MNC=01
=hex2dec(2908)= 10504
=UE capable to support FDD , not TDD
=UE capable to support GSM
=Signaling Radio Bearer Information Setup ,RB-1

=Radio Bearer Mapping
=BLER Target= -20 dB
=MaxAllowedULTxPower=24 dBm
=(-48*2)= -96 dBm (step of 2 dB) Default Constant DPCCH_Power_offset CPICH_RSCP PCPICH Power
-22 -96 -80 33
-22 -96 -70 33
= use Closed Loop Power Control Algorithm1 Note :DPCCH_Power_offset is configured by RNC and delivered to UE in RRC Con
= use long SC on Uplink
=Spreading Factor 64 (Uplink)

=Spreading Factor 128 (Downlink)
=Primary Scrambling code=97

=Spreading Factor 128 (Downlink)
dentity=RNCid(12bits)+Cellid(16bits)
=0000000010110111011110010010 => RNCid=bin2dec(000000001011)=11 and Cellid=bin2dec(0111011110010010)=30610

= not support GSM (Locked UMTS Mode)
= Chipering Algorithm A5/3

= UE support Band fdd2100 MHz
= UE (Powerclass3) maximum transmitted power =24 dBm
= support Compressed Mode (CM) uplink and downlink

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

dentity=RNCid(12bits)+Cellid(16bits)
=0000000010110111011110010010 => RNCid=bin2dec(000000001011)=11 and Cellid=bin2dec(0111011110010010)=30610
UL Interference
UL DPCCH Initial Power
-107 -16
-107 -26
and delivered to UE in RRC Connection Setup.

L3 Messages - Video Call (CS64) Call Proce

UE NodeB S-RNC

Start Rx
L1 Synchonization
1.RRC: Initial Direct Transfer (MM: CM Service Request)

1.RRC: Uplink Direct Transfer (CC: Setup)
4.RRC: Downlink Direct Transfer (CC: Call Proceeding)
3.NBAP: Radio Link

4.NBAP: Radio Link

6.RRC: Radio Bearer Setup
7.NBAP: Radio Link

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 Established
1.RRC: Uplink Direct Transfer (CC: Disconnect)
4.RRC: Downlink Direct Transfer (CC: Release)
5.RRC: Uplink Direct Transfer (CC: Release Complete)
2.RRC:RRC Connection Release Complete

Request

Response
5,.ALCAP: Iub User Plane Release
2. If IP transport is applied to the Iub interface, no ALCAP procedure is
ll (CS64) Call Procedure
S-RNC CN
1.RRC Connection Setup
SCCP: CR (Connection Request)

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

&Authentication.3
RANAP: Common ID (IMSI) Security Mode Control

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. 5
4.Call Setup
6.RANAP: Direct Transfer (CC: Alerting)
8.RANAP: Direct Transfer (CC: Connect)
11.RANAP: Direct Transfer (CC: Connect Acknowledge)
ablished
6.Conversation
2.RANAP: Direct Transfer (CC: Disconnect)
3.RANAP: Direct Transfer (CC: Release)
7.Call Release
6.RANAP: Direct Transfer (CC: Release Complete)
8.ALCAP: Iu User Plane Release
9.RANAP: Iu Release Complete

RRC connection setup procedure is performed for the UE to set up a signaling connection to the SRNC
Triggering Conditions : The UE in idle mode intitiates the RRC connection setup procedure when the NA
receives an RRC CONNECTION REQUEST message from the UE, the Radio Resource Management (RRM
request, based on a specific algorithm. If accepting the request, the RRM module further determines whethe
Dedicated Channel (DCH)or on a Common Channel (CCH),based on a specific RRM algorithm. Typically, an

1.The UE sends an RRC CONNECTION REQUEST message to the SRNC through the uplink CCCH(RACH
edure Description 2.Based on the cause in the RRC connection request and the system resource status, the SRNC determines
resources, and L1 and L2 resources. Then the SRNC sends a RADIO LINK SETUP REQUEST message to t
connection.
nnection Setup
3.The NodeB responds with a RADIO LINK SETUP RESPONSE message to the SRNC after successfully pr
4.The SRNC uses the ALCAP protocol to set up the Iub user plane transport bearer and performs the synchr
5.The SRNC sends an RRC CONNECTION SETUP message to the UE through the downlink CCCH (FACH)
6. UE and NodeB initiate L1 Synchronization. NodeB sends NBAP:Synchonization Indicator message to SRN
7. The UE sends an RRC CONNECTION SETUP COMPLETE message to the SRNC through the uplink Ded
If the RNC judges that the RRC connection request cannot be set up (for instance, due to insufficient resourc
theUE, and indicates the reject reason in the message
The signaling connection setup procedure is performed to exchange the NAS (Non Access Stratum)
ng Connection Setup Triggering Conditons: The UE sends a direct transfer message to initiate the signaling connection setup pr

1.The UE sends an INITIAL DIRECT TRANSFER message to the SRNC through the RRC connection. The m
2.The SRNC receives the INITIAL DIRECT TRANSFER message from the UE and sends an INITIAL UE ME
sent to the
CN by the UE. The content of the NAS information is CM SERVICE REQUEST.
-If accepting the request, the CN sends a CONNECTION CONFIRM (CC) message to the SRNC. The mes
SRNC confirms that the signaling connection is set up.
-If rejecting the request, the CN sends a CONNECTION REJECT (CJ) message to the SRNC. The messag
the SRNC confirms that the signaling connection fails to be setup and then initiates the RRC release proced
tication.3
Mode Control
The authentication and security mode control procedure is performed for the UE and the network t
the integrity protection algorithm and ciphering algorithm. This procedure ensures integrity and correctness o

Identity
Module (USIM) judges that the authentication is successful, the UE returns a message with an XRES IE.
protection

Identity
Module (USIM) judges that the authentication is successful, the UE returns a message with an XRES IE.
protection
algorithms.
-If the integrity protection and ciphering algorithms are configured successfully, the UE sends a SECU
then sends a SECURITY MODE COMMAND COMPLETE message to the CN.The message contains the in
-If the UE does not support the integrity protection and ciphering algorithms, the UE sends a SECURIT
contains the error information and the reason for the failure. The SRNC then sends a SECURITY MODE CO
The RANAP:Common ID message is used to transport the permanent UE Identity(IMSI) to SRNC
The call setup procedure is performed to set up a call.

r Setup. 5 Triggering Conditions: The UE initiates a call

1.The UE sends an UPLINK DIRECT TRANSFER message to the SRNC. The message contains the numbe
3.The CN sends a DIRECT TRANSFER message to the SRNC. The message indicates CALL PROCEEDING
6. When the called terminal rings, the CN sends a DIRECT TRANSFER message to the SRNC. The messag
8.The CN sends a DIRECT TRANSFER message to the SRNC. The message indicates CONNECT, which m
11.The SRNC transparently sends the contents of the UPLINK DIRECT TRANSFER message to the CN thro

2.(Optional; applicable to the ATM-based Iu-CS interface only) The SRNC maps the Quality of Service (QoS)
parameters. Based on the AAL2 link characteristic parameters,the ALCAP on the Iu interface initiates an Iu u
3.The SRNC sends a RADIO LINK RECONFIGURATION PREPARE message to the NodeB, requesting the
4.The NodeB allocates the associated resources and then sends a RADIO LINKRECONFIGURATION READ
5.(Optional; required for the ATM-based Iub interface only) The Iub ALCAP at the SRNC initiates an Iub user
exchanging
uplink and downlink synchronization frames in the DCH frame protocol.
8.After performing the radio bearer setup, the UE sends a RADIO BEARER SETUP COMPLETE message to
2.The SRNC sends an RAB ASSIGNMENT RESPONSE message to the CN. The message indicates the ID

has hanged
up.

has hanged
up.
3.The CN sends a DIRECT TRANSFER message to the SRNC. The message indicates RELEASE to reques
7.The CN sends an IU RELEASE COMMAND message to the SRNC to request call release on the Iu interfa
8.(Optional; applicable to the ATM-based Iu-CS interface only) The ALCAP protocol on the Iu interface initiate
The RRC Connection Release procedure is performed to release the signaling connection and all radio be
Triggering Conditions: After a n RAB is released,the SRNC judges whether the RRC connection carries an
UE,the SRNC initiates an RRC connection release procedure.
The procedure shown is described as follows: based on the resouce occupied by the RRC connection,th
release of an RRC connection from CCH (If an RRC connection needs to be released after a successful outg
bearers fails to be setup ,the RRC connection on the CCH is released)
(NOTE: The SRNC may send the RRC CONNECTION RELEASE message several times to increase the pro
The number of retransmissions and the transmission intervals are determined by the SRNC. If the SRNC doe
COMPLETE message from the UE after sending the RRC CONNECTION RELEASE message for four times
onnection Release
3.The SRNC sends a RADIO LINK DELETION REQUEST message to the NodeB,requesting the NodeB to d
4.After releasing the resources, the NodeB sends a RADIO LINK DELETION RESPONSE message to the S
5.(Optional; required for the ATM-based Iub interface only) The SRNC uses the ALCAP protocol to initiate an
signaling connection to the SRNC. RRC connection setup is always initiated by the UE. One UE has a
ion setup procedure when the NAS of the UE requests the establishment of a signaling connection When the SRNC
dio Resource Management (RRM) module of the RNC determines whether to accept or reject theRRC connection
module further determines whether to set up the RRC connection on a
cific RRM algorithm. Typically, an RRC connection is set up on the DCH.
through the uplink CCCH(RACH), requesting the establishment of an RRC connection.

rce status, the SRNC determines to set up the RRC connection on a DCH and allocates the Radio NetworkTemporary Identity(RNTI),radio
SETUP REQUEST message to the NodeB, requesting the NodeB to allocate the specific radio link resources required for an RRC
o the SRNC after successfully preparing the resources.

t bearer and performs the synchronization between the SRNC and the NodeB. This procedure is optional. It is required
ough the downlink CCCH (FACH). The message contains the information about the DCH allocated by the SRNC.
nization Indicator message to SRNC when the uplink enter "In-Sync" state
the SRNC through the uplink Dedicated Control Channel (DCCH) that is just set up. The message
stance, due to insufficient resources), it directly sends an RRC CONNECTION REJECT message to
e the NAS (Non Access Stratum) information between the UE and the CN.
he signaling connection setup procedure.
rough the RRC connection. The message contains the initial NAS information to be sent to the CN by the UE.
UE and sends an INITIAL UE MESSAGE to the CN over the Iu interface. The INITIAL UE MESSAGE contains the NAS information to be
EST.
message to the SRNC. The message indicates that the SCCP connection is set up. After receivingthe message, the
ssage to the SRNC. The message indicates that the SCCP connection fails to be set up. After receiving the message,
initiates the RRC release procedure.
med for the UE and the network to implement bi-directional authentication and to negotiate and configure
nsures integrity and correctness of signaling
work initiates the authentication and securitymode control procedure
ge indicates AUTHENTICATION REQUEST.

NSFER messageto the CN through a DIRECT TRANSFER message, indicating AUTHENTICATION RESPONSE. If the UMTS Subscriber
a message with an XRES IE.

o initiate the security mode control procedure. The message contains the information about the supported ciphering and integrity
he message contains the number of the called party and the information about the bearer capability of the call.
NSFER messageto the CN through a DIRECT TRANSFER message.
ge indicates CALL PROCEEDING and contains the information about the negotiated bearer capability of the call.
Procedure below)
ssage to the SRNC. The message indicates ALERTING.
ge indicates CONNECT, which means that the called party has answered the call.
ANSFER message to the CN through a DIRECT TRANSFER message, indicating CONNECT ACKNOWLEDGE.

maps the Quality of Service (QoS) parameters for the RAB to the AAL2 link characteristic parameters and radio resource characteristic
n the Iu interface initiates an Iu user plane transport bearer setup procedure.
age to the NodeB, requesting the NodeB to prepare for adding one or more DCHs to the existing radio links for carrying the RAB.
LINKRECONFIGURATION READY message to the SRNC.
at the SRNC initiates an Iub user plane transport bearer setup procedure. The NodeB and the SRNC perform synchronization by
e to theNodeB.
SETUP COMPLETE message to the SRNC.
N. The RAB isset up.
:
N. The message indicates the ID of the RAB that fails to be set up and the reason for the failure.
ces after a call ends.
NSFER messageto the CN through a DIRECT TRANSFER message, indicating DISCONNECT. This content informs the CN that the UE
naling connection and all radio bearers between UE and the UTRAN
er the RRC connection carries any other RAB or the UE. If judging that the RRC connection does not carry other RAB of the
cupied by the RRC connection,there are two types of RRC connection release procedure: release of an RRC connection from DCH and
e released after a successful outgoing call,, the RRC connection on the DCH is released and if a radio
through the DCCH.

several times to increase the probability of proper reception of the message by the UE. The RRC SNs of these messages are the same.
ed by the SRNC. If the SRNC does not receive an RRC CONNECTION RELEASE
RELEASE message for four times, the SRNC judges that the UE has released the RRC connection.)
to the SRNC.
NodeB,requesting the NodeB to delete the radio link resources in the NodeB.
N RESPONSE message to the SRNC.
the ALCAP protocol to initiate an Iub user plane transport bearer release procedure. Then, the RRC connection release procedure ends.
a
hen the SRNC

connection
tworkTemporary Identity(RNTI),radio
sources required for an RRC
nal. It is required
the SRNC.
he UE.
ontains the NAS information to be
message, the
g the message,
ure
ESPONSE. If the UMTS Subscriber
ed ciphering and integrity

the call.
of the call.
WLEDGE.
nd radio resource characteristic
perform synchronization by
ontent informs the CN that the UE

carry other RAB of the
n RRC connection from DCH and
s of these messages are the same.
onnection release procedure ends.

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




value=00000000101101110111100100

value= not support GSM (Locked UM


RRC: Initial Direct Transfer (MM: CM Service Request)
RANAP:Initial UE Message (MM: CM Service Request)


value= Call B-Party number =
RRC: Uplink Direct Transfer (CC: Setup)

RRC: Downlink Direct Transfer (CC: Call Proceeding)
RANAP: Direct Transfer (CC: Call Proceeding)

RRC: Downlink Direct Transfer (CC: Alerting)

RRC: Downlink Direct Transfer (CC: Connect)
RRC: Uplink Direct Transfer (CC: Connect Acknowledge)

RRC: Uplink Direct Transfer (CC: Disconnect)

RRC: Downlink Direct Transfer (CC: Release)


e=hex2dec(2908)= 10504
e= OriginatingConversationalcall (CS MOC)
e=(-24+ (44/2))=-2.0 dB
e=hex2dec(2908)= 10504
e=UE capable to support FDD , not TDD

e=UE capable to support GSM
e=Radio Bearer Mapping

e=BLER Target= -20 dB
e=MaxAllowedULTxPower=24 dBm
e=(-48*2)= -96 dBm (step of 2 dB) Default Constant DPCCH_Power_offset CPICH_RSCP PCPICH Power
-22 -96 -80 33
-22 -96 -70 33
e= use Closed Loop Power Control Algorithm1
e= use long SC on Uplink
e=Spreading Factor 64 (Uplink)

e=Primary Scrambling code=97
Identity=RNCid(12bits)+Cellid(16bits)
e=0000000010110111011110010010 => RNCid=bin2dec(000000001011)=11 and Cellid=bin2dec(0111011110010010)=30610

e= not support GSM (Locked UMTS Mode)
e= Chipering Algorithm A5/3

e= UE (Powerclass3) maximum transmitted power =24 dBm
e= support Compressed Mode (CM) uplink and downlink

value= SF16(uplink)-> CS64 (VP)
value= SF32(downlink)-> CS64 (VP)
-107 -16
-107 -26
11110010010)=30610
L3 Messages - PS(R99) C
UE NodeB
Start Rx
L1 Synchonization
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 Request)
message to
N/W
RRC: Uplink Direct Transfer (GMM: GPRS Identity Response)
RRC: Downlink Direct Transfer (MM: Authentication & Ciphering Request)
RRC: Uplink Direct Transfer (MM: Authentication & Ciphering Response)
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 Request)
ALCAP: Iub User Plane Setup
RRC: Downlink Direct Transfer (SM: Activate PDP Context Accept)
PS Session Establ

RRC: Radio Bearer Reconfiguration
RRC: Radio Bearer Reconfiguration Complete
RRC: Uplink Direct Transfer (SM: Deactivate PDP Context Request)
RRC: Downlink Direct Transfer (SM: Deactivate PDP Context Accept)
RRC: Uplink Direct Transfer (MM: Detach Request)
RRC: Radio Bearer Release
RRC: Downlink Direct Transfer (MM: Detach Accept)
RRC: Radio Bearer Release Completed

L3 Messages - PS(R99) Call Procedure
S-RNC
tion Request (RACH)
ection Setup (FACH)
7.NBAP:Synchonization Indicator
Setup Completed (DCH)
er (GMM: Attach Request)
(GMM: GPRS Identity Request)
MM: GPRS Identity Response)
Authentication & Ciphering Request)
uthentication & Ciphering Response)
Mode Command
Mode Completed
nsfer (MM: Attach Accept)
er (MM: Attach Completed)
: Activate PDP Context Request)
NBAP: Radio Link Reconfiguration

Prepare

Ready
Bearer Setup

Commit
er Setup Complete
ement Control
SM: Activate PDP Context Accept)
PS Session Established
ement Report

Prepare

Ready

Commit
er Reconfiguration
configuration Complete
Deactivate PDP Context Request)
M: Deactivate PDP Context Accept)

Prepare

Ready

Commit
fer (MM: Detach Request)
earer Release
nsfer (MM: Detach Accept)
ALCAP: Iu User Plane Release
Release Completed
(CC: RRC Connection Release)
RRC Connection Release Complete)
RC Connection Release Complete)

Request
Response

) Call Procedure
CN
1.RRC Connection Establishment
RANAP: Initial UE Message GMM: (Attach Request)
RANAP: GMM: GPRS Identity Request GPRS Attach.2

Procedure
RANAP: GMM: GPRS Identity Response
RANAP: MM: Authentication & Ciphering Request
RANAP:MM: Authentication&Ciphering Response
RANAP: Security Mode Command 3.Authentication & Security Mode
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 Setup
Radio Bearer. 5
Setup
RANAP: RAB Assignment Response
RANAP: SM: Activate PDP Context Accept
ablished
6.Downlink and Uplink Data Tran

Radio Bearer Reconfiguration
to Upgrade/Downgrade Bit
Rate
RANAP: SM: Deactivate PDP Context Request
RANAP: SM: Deactivate PDP Context Accept
PS Session Release.7
RANAP: MM: Detach Request
RANAP: MM: Detach Accept

Triggering Conditions : The UE in idle mode intitiates the RRC connection setup procedure
SRNC receives an RRC CONNECTION REQUEST message from the UE, the Radio Resource
connection request, based on a specific algorithm. If accepting the request, the RRM module fu
(DCH)or on a Common Channel (CCH),based on a specific RRM algorithm. Typically, an RRC co

NetworkTemporary Identity(RNTI),radio resources, and L1 and L2 resources. Then the SRNC se
ocedure Description allocate the specific radio link resources required for an RRC connection.
3.The NodeB responds with a RADIO LINK SETUP RESPONSE message to the SRNC after su
Connection Establishment 4.The SRNC uses the ALCAP protocol to set up the Iub user plane transport bearer and perform
is required for the ATM-based Iub interface only.
If the RNC judges that the RRC connection request cannot be set up (for instance, due to insuffi
The GPRS Attach procedure is performed in order to make UE presence known to the netw
SMS over PS data paging via the SGSN, and notification of incoming PS Data.In the attach proc
executed.
PS attach and combined PS / CS attach.The identity provided to the network shall be the UE's P
Triggering Conditons: The UE sends a GPRS Attach Request message to initiate the signaling
Attach.2 The procedure shown is described as follows:

ure 1.UE initiates the attach procedure by the transmission of an Attach Request message to the RN
available. RNC opens an SCCP (Signalling Connection Control Part) connection and sends the A
2.If the UE identifies itself with P-TMSI and the SGSN has changed since detach, the new SGSN
to
request the IMSI. The old SGSN responds with Identification Response (IMSI, Authentication vec
3.If the UE is unknown in both the old and new SGSN, the SGSN sends an Identity Request (Ide
4. The new SGSN asks the HLR to authenticate the UE. HLR sends back to SGSN the Authentic
WCDMA
subscriber information The SGSN sends the Authentication and Ciphering Request to the UE. At
and AUTN (Authentication Token) to the UE. At reception of this message, the UE (USIM, WCDM
Authentication and Ciphering response (RES) message to the SGSN. During generation of authe
Integrity Key, IK. These keys are stored together with the CKSN (Ciphering key sequence numbe
transmission security. A known bit stream is encrypted and decrypted in SGSN and UE.
5. If the SGSN number has changed since the GPRS detach, or if it is the very first attach, then t
ntication & Security Mode Control -The SGSN sends an Update Location (SGSN Number, SGSN Address, IMSI) to the HLR.
-The HLR sends Cancel Location (IMSI, Cancellation Type) to the old SGSN with Cancellation T
-The old SGSN acknowledges with Cancel Location Ack (IMSI). If there are any ongoing procedu
removing
the MM (Mobility Management) and PDP contexts
-The HLR sends Insert Subscriber Data (IMSI, GPRS subscription data) to the new SGSN.
-The new SGSN validates the UE's presence in the (new) RA (Routing Area). If all checks are su
Subscriber Data Ack (IMSI) message to the HLR.
-The HLR acknowledges the Update Location message by sending an Update Location Ack to th
finished.
If the Update Location is rejected by the HLR, the SGSN rejects the Attach Request from the UE
6. If Attach Type in step 1 indicated PS Attach while already CS attached, or combined PS/CS at
The
removing
the MM (Mobility Management) and PDP contexts
-The HLR sends Insert Subscriber Data (IMSI, GPRS subscription data) to the new SGSN.
-The new SGSN validates the UE's presence in the (new) RA (Routing Area). If all checks are su
Subscriber Data Ack (IMSI) message to the HLR.
-The HLR acknowledges the Update Location message by sending an Update Location Ack to th
finished.
If the Update Location is rejected by the HLR, the SGSN rejects the Attach Request from the UE
6. If Attach Type in step 1 indicated PS Attach while already CS attached, or combined PS/CS at
The
SGSN starts the location update procedure towards the new MSC/VLR upon receipt of the first I
attached in
the VLR.
a. The SGSN sends a Location Update Request (new LAI, IMSI, SGSN Number, Location Updat
indicated combined PS / CS attach. Otherwise, Location Update Type shall indicate normal locat
b. If the LA update is inter-MSC, the new VLR sends Update Location (IMSI, new VLR) to the HL
c. If the LA update is inter-MSC, the HLR sends a Cancel Location (IMSI) to the old VLR.
d. The old VLR acknowledges with Cancel Location Ack (IMSI). If there are any ongoing procedu
removing the MM and PDP contexts.
e. If the LA update is inter-MSC, the HLR sends Insert Subscriber Data (IMSI, GSM subscriber d
f. The VLR acknowledges with Insert Subscriber Data Ack (IMSI).
g. After finishing the inter-MSC location update procedures, the HLR responds with Update Loca
h. The VLR responds with Location Update Accept (VLR TMSI) to the SGSN.
7. The SGSN sends an Attach Accept (P-TMSI, VLR TMSI, P-TMSI Signature, Radio Priority SM
Attach
Request cannot be accepted, the SGSN returns an Attach Reject (IMSI, Cause) message to the
ession Setup 8. If P-TMSI or VLR TMSI was changed, the UE acknowledges the received TMSI(s) with Attach
9. If VLR TMSI was changed, the SGSN confirms the VLR TMSI re-allocation by sending TMSI R
10. Iu (Iu Interface) and SCCP signalling connections are released

arer. 5
The authentication and security mode control procedure is performed for the UE and
the integrity protection algorithm and ciphering algorithm. This procedure ensures integrity and c
Triggerring Conditions: The UE and the CN exchange signaling. The network initiates the auth
1.The CN sends a DIRECT TRANSFER message to the SRNC. The message indicates AUTHEN
RESPONSE. If the
UMTS Subscriber Identity Module (USIM) judges that the authentication is successful, the UE re
5.The CN sends a SECURITY MODE COMMAND message to the SRNC to initiate the security
ciphering
and integrity protection algorithms.
6.The SRNC sends a SECURITY MODE COMMAND message to the UE to inform the UE of the
-If the integrity protection and ciphering algorithms are configured successfully, the UE se
then sends a SECURITY MODE COMMAND COMPLETE message to the CN.The message co
uses.
-If the UE does not support the integrity protection and ciphering algorithms, the UE sends
contains the error information and the reason for the failure. The SRNC then sends a SECURIT
The RANAP:Common ID message is used to transport the permanent UE Identity(IMSI) to
The PS Session Setup procedure is performed to set up a PS session

nlink and Uplink Data Transfer Triggering Conditions: The UE send Activate PDP context request message to RNC. PDP Con
Packet
Mobility Management Connected that enables the user to transmitt and receive data while movin
remove a
virtual data channel between a terminal connected to a UE and a GGSN. PDP contexts deal with
Access
bearer establishes on request of the SGSN in order to realize the air interface connection. At the
TLLI
Triggering Conditions: The UE send Activate PDP context request message to RNC. PDP Con
Packet
remove a
Access
TLLI
earer Reconfiguration (Temporary Logical Link Identity) associated to IMSI.
de/Downgrade Bit
IP addresses can be allocated dynamically or statistically. If allocated dynamically, this significan
address allocation enables subscribers to provide their own IP addresses. This can be useful wh
The support of
QoS enables the operator to differentiate GPRS services.
When dynamic addressing from the home PLMN or the Visitor PLMN is used, it is the responsibi

1.The UE sends an Activate PDP Context Request (NSAPI, TI(Teardown Indication), PDP Type,
Configuration
Options) message to the SGSN The UE shall use PDP Address to indicate whether it requires th
2. The SGSN sends a RAB Assignment Request message to the RNC to establish a RABs
3.The RNC establishes the appropriate radio bearer In WCDMA, RAB setup is done by the RAB
4.The RNC returns a RAB Assignment Response message to the SGSN
5. The SGSN validates the active PDP Context Request using PDP Type (optional), PDP Addres
subscription
records.The SGSN sends a Create PDP Context Request message to the affected GGSN. Acce
Point
Name to find an external network and optionally to activate a service for this APN
6. The GGSN creates a new entry in its PDP context table and generates a Charging Id. The new
between
ssion Release.7 the SGSN and the external PDP network, and to start charging
7.The SGSN inserts the Network layer Service Access Point Identifier, NSAPI along with the GG
Accepted. The
SGSN selects Radio Priority and Packet flow Id based on QoS Negotiated, and returns an Activa
between
theGGSN and the UE and to start charging

resource
characteristic parameters. Based on the AAL2 link characteristic parameters,the ALCAP on the I
carrying the
RAB.
synchronization by exchanging uplink and downlink synchronization frames in the DCH frame pr
The
9.ThePS session
SRNC sendsrelease
an RAB procedure
ASSIGNMENT is performed
RESPONSE to release
message services and The
to the CN. resources afterup.
RAB isset a
Triggering Conditions
1.The CN sends an RAB: ASSIGNMENT
The UE send Deactivate
REQUESTPDP context
message to request
the SRNC message to RNC.
to initiate A PD
the RAB se
deactivation,the
2.The SRNC sends UE an
hasRAB
the state Active. After
ASSIGNMENT the PDP Context
RESPONSE messagedeactivation
to the CN.procedure
The messagethe state
indic
other
PDP contexts activated.PDP Deactivation may be initiated by a:UE procedure,SGSN procedure,

C Connection Release 1.The UE sends a Deactivate PDP Context Request (TI, Teardown Indication) message to the S
2.The SGSN sends a Delete PDP Context Request (TEID, NSAPI, Teardown Indication) messag
Context Request message, then the SGSN deactivates all PDP contexts associated with this PD
3.The GGSN removes the PDP context(s) and returns a delete PDP Context Response (TEID) m
network
4.The SGSN returns a Deactivate PDP Context Accept (TI) message to the UE via the RNC
5. In Iu mode, radio access bearer release is done by the RAB Assignment procedure
6. The SCCP connection between RNC and SGSN is released. At GPRS detach, all PDP contex
1.The UE sends a Deactivate PDP Context Request (TI, Teardown Indication) message to the S
3.The GGSN removes the PDP context(s) and returns a delete PDP Context Response (TEID) m
network
RAB
of the UE,the SRNC initiates an RRC connection release procedure.
The procedure shown is described as follows: based on the resouce occupied by the RRC c
released and if
a radio bearers fails to be setup ,the RRC connection on the CCH is released)
messages are the same. The number of retransmissions and the transmission intervals are dete
COMPLETE message from the UE after sending the RRC CONNECTION RELEASE message f

4.After releasing the resources, the NodeB sends a RADIO LINK DELETION RESPONSE mess
release
procedure ends.
C connection setup procedure when the NAS of the UE requests the establishment of a signaling connection When the
m the UE, the Radio Resource Management (RRM) module of the RNC determines whether to accept or reject the RRC
e request, the RRM module further determines whether to set up the RRC connection on a Dedicated Channel
tem resource status, the SRNC determines to set up the RRC connection on a DCH and allocates the Radio
resources. Then the SRNC sends a RADIO LINK SETUP REQUEST message to the NodeB, requesting the NodeB to
nection.
e transport bearer and performs the synchronization between the SRNC and the NodeB. This procedure is optional. It
he UE through the downlink CCCH (FACH). The message contains the information about the DCH allocated by the SRNC.
up (for instance, due to insufficient resources), it directly sends an RRC CONNECTION REJECT message to
UE presence known to the network by performing a Packet Service Attach (GPRS attach). This makes the UE available for
ming PS Data.In the attach procedure, the UE shall provide its identity and an indication of which type of attach that is to be
he network shall be the UE's Packet TMSI (P-TMSI) or IMSI
message to initiate the signaling connection setup procedure.
ch Request message to the RNC. IMSI shall be included if the UE does not have a valid P-TMSI (Packet Temporary IMSI)
art) connection and sends the Attach request to SGSN
ed since detach, the new SGSN sends an Identification Request (P-TMSI, old RAI, old P-TMSI Signature) to the old SGSN
ponse (IMSI, Authentication vector). The old SGSN also validates the old P-TMSI
sends an Identity Request (Identity Type = IMSI) to the UE. The UE responds with Identity Response (IMSI).
ds back to SGSN the Authentication data received from AUC (Authentication Center). The HLR contains GSM and
Ciphering Request to the UE. At authentication of a WCDMA subscriber, the SGSN transmitts the RAND (Random Number)
message, the UE (USIM, WCDMA Subscriber Identity module in the UE) verifies AUTN and if accepted the UE returns an
GSN. During generation of authentication vectors, the USIM in the UE also computes a new Ciphering Key. CK, and a new
Ciphering key sequence number of Kc) until CKSN is updated at the next authentication. The SGSN verifies the
pted in SGSN and UE.
it is the very first attach, then the SGSN informs the HLR:
ddress, IMSI) to the HLR.

old SGSN with Cancellation Type set to Update Procedure.
there are any ongoing procedures for that UE, the old SGSN shall wait until these procedures are finished before
n data) to the new SGSN.

uting Area). If all checks are successful then the SGSN constructs an MM context for the UE and returns an Insert
ng an Update Location Ack to the SGSN after the canceling of old MM context and insertion of new MM context are
he Attach Request from the UE with an appropriate cause code

ttached, or combined PS/CS attach, then the VLR shall be updated. The VLR number is received from the RA information.
e is performed for the UE and the network to implement bi-directional authentication and to negotiate and configure
ocedure ensures integrity and correctness of signaling
. The network initiates the authentication and securitymode control procedure
he message indicates AUTHENTICATION REQUEST.

e SRNC.
RECT TRANSFER messageto the CN through a DIRECT TRANSFER message, indicating AUTHENTICATION
tication is successful, the UE returns a message with an XRES IE.

e SRNC to initiate the security mode control procedure. The message contains the information about the supported
the UE to inform the UE of the integrity protection and ciphering algorithms that the UTRAN selects.
gured successfully, the UE sends a SECURITY MODE COMMAND COMPLETE message to the SRNC. The SRNC
age to the CN.The message contains the information about the integrity protection and ciphering algorithms that the UE
ring algorithms, the UE sends a SECURITY MODE COMMAND FAILURE message to the SRNC. The message
SRNC then sends a SECURITY MODE COMMAND REJECT message to the CN
rmanent UE Identity(IMSI) to SRNC
PS session
est message to RNC. PDP Context Activation is performed when the UE initiates a packet call setup. The UE has the state
tt and receive data while moving within a PLMN. and starts the PDP context activation procedure used to set up and
GGSN. PDP contexts deal with allocation of IP addresses to the UE and Quality of Service, QoS, parameters. A Radio
air interface connection. At the end the UE has an IP address NSAPI (Network layer Service Access Point Identifier) and a
services and resources after a session ends.
equest message to RNC. A PDP Context Deactivation is performed when the UE terminates a packet call. Before the
eactivation procedure the state becomes Packet Mobility Management Connected.The RAB will be released if there are no
E procedure,SGSN procedure,GGSN procedure
n Indication) message to the SGSN via the RNC

I, Teardown Indication) message to the GGSN. If Teardown Indication was included by the UE in the Deactivate PDP
ontexts associated with this PDP address by including Teardown Indication in the Delete PDP Context Request message
DP Context Response (TEID) message to the SGSN. The Delete PDP Context messages are sent over the backbone
age to the UE via the RNC

signment procedure
t GPRS detach, all PDP contexts for the UE are implicitly deactivated
ges whether the RRC connection carries any other RAB or the UE. If judging that the RRC connection does not carry other
re.
CH (If an RRC connection needs to be released after a successful outgoing call,, the RRC connection on the DCH is
H is released)

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

ge to the NodeB,requesting the NodeB to delete the radio link resources in the NodeB.
DELETION RESPONSE message to the SRNC.
RNC uses the ALCAP protocol to initiate an Iub user plane transport bearer release procedure. Then, the RRC connection
RRC:RRC Connection Request (RACH) >>"RRC Connection Request Description"
>>"Geographical and UTRAN Entity Identi
value=hex2dec(5)=5 , hex2dec(2)=2 ,h
value=hex2dec(0)=0 , hex2dec(1)=1 -->
value= OriginatingBackgroundCall (P
value=(-24+ (33/2))=-7.5 dB
value=UE capable to support FDD , no
value=Signaling Radio Bearer Informa

value=(-48*2)= -96 dBm (step of 2 dB)
value= use Closed Loop Power Contr
value=Spreading Factor 128 (Downlin

Cell Identity=RNCid(12bits)+Cellid(16b
value=000000001011011101111001001
RRC:RRC Connection Setup Complete (DCCH) >>"RRC Connection Setup Complete Desc
value= not support GSM (Locked UMT
value= UE support Band fdd2100 MHz

value= UE (Powerclass3) maximum tr
value= support Compressed Mode (C

value= UE support Band fdd1800 MHz
value= not support HSDPA
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

RANAP: MM: Attach Accept

RRC: Downlink Direct Transfer (MM: Attach Accept)
RRC: Uplink Direct Transfer (MM: Attach Completed)

RANAP: MM: Attach Completed


RRC: Radio Bearer Reconfiguration
RRC: Radio Bearer Reconfiguration 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"
alue=hex2dec(5)=5 , hex2dec(2)=2 ,hex2dec(0)=0 --> MCC=520
alue=hex2dec(0)=0 , hex2dec(1)=1 --> MNC=01
alue=hex2dec(2908)= 10504
alue= OriginatingBackgroundCall (PS MOC)
alue=(-24+ (33/2))=-7.5 dB
>"RRC Connection Setup Description"
>"Geographical and UTRAN Entity Identifiers"
alue=hex2dec(5)=5 , hex2dec(2)=2 ,hex2dec(0)=0 --> MCC=520
alue=hex2dec(0)=0 , hex2dec(1)=1 --> MNC=01
alue=hex2dec(2908)= 10504
alue=UE capable to support FDD , not TDD
alue=UE capable to support GSM
alue=Signaling Radio Bearer Information Setup ,RB-1
alue=Radio Bearer Mapping

alue=BLER Target= -20 dB
alue=MaxAllowedULTxPower=24 dBm
alue=(-48*2)= -96 dBm (step of 2 dB) Default Constant DPCCH_Power_offset CPICH_RSCP PCPICH Power
-22 -96 -80 33
-22 -96 -70 33
alue= use Closed Loop Power Control Algorithm1
alue= use long SC on Uplink
alue=Spreading Factor 64 (Uplink)
alue=Spreading Factor 128 (Downlink)

alue=Primary Scrambling code=97
alue=Spreading Factor 128 (Downlink)
ell Identity=RNCid(12bits)+Cellid(16bits)
alue=0000000010110111011110010010 => RNCid=bin2dec(000000001011)=11 and Cellid=bin2dec(0111011110010010)=30610
>"RRC Connection Setup Complete Description"

alue= not support GSM (Locked UMTS Mode)
alue= Chipering Algorithm A5/3
alue= UE support Band fdd2100 MHz

alue= UE (Powerclass3) maximum transmitted power =24 dBm
alue= support Compressed Mode (CM) uplink and downlink

alue= UE support Band fdd1800 MHz
alue= not support HSDPA
value= SF16(uplink)-> PS64
value= SF32(downlink)-> PS64
value= SF16(downlink)-> PS128
-107 -16
-107 -26
10010010)=30610
L3 Messages - PS(HSDPA) Call Proced

UE NodeB S-RNC

Start Rx
L1 Synchonization
RRC: Initial Direct Transfer (GMM: Service Request)

Prepare
Ready

Commit
RRC:Measurement Report (e1d)

Prepare

Ready

Commit
RRC: Physical Channel Reconfiguration (DCCH)
RRC:Physical Channel Reconfiguration Complete (DCCH)

Prepare

Ready

Commit

Request

Response

SDPA) Call Procedure
S-RNC CN
1.RRC Connection Establishm
RANAP: GMM:Service Request
RANAP: Security Mode Command
ALCAP : Iu User Plane Setup PS Session Setup.2

Radio Bearer. 3
Setup
Established
Downlink and Uplink Data Tra
HSDPA's Serving Cell Change

RRC Connection Release.6


Packet
remove a
Access
TLLI
(Temporary Logical Link Identity) associated to IMSI.

The support of
1. The UE initiates the PS Session by using the Service Request (Service Type=Data) message.
RNC
sets-up an SCCP connection with the SGSN and transfers the initial service request (Authentica
Configuration
ession Setup.2 3. The SGSN sends a RAB Assignment Request message to the RNC to establish a RABs
subscription
Point
subscription
Point
earer. 3 between
the SGSN and the external PDP network, and to start charging
Accepted. The
between

resource
carrying the
RAB.
7.The
The PS SRNC sendsrelease
session a RADIOprocedure
LINK RECONFIGURATION COMMIT
is performed to release message
services andto theNodeB.
resources after a
9.The SRNC
Triggering sends an RAB
Conditions : TheASSIGNMENT RESPONSE
UE send Deactivate message
PDP context to themessage
request CN. The RAB isset
to RNC. A up.
PD
deactivation,the UE has the state Active. After the PDP Context deactivation procedure the state
1.The
other CN sends an RAB ASSIGNMENT REQUEST message to the SRNC to initiate the RAB se
2.The SRNC sends
PDP contexts an RAB ASSIGNMENT
activated.PDP Deactivation mayRESPONSE
be initiatedmessage
by a:UE to the CN. The message
procedure,SGSN indic
procedure,

nk and Uplink Data Transfer. 4 3.The GGSN removes the PDP context(s) and returns a delete PDP Context Response (TEID) m
network
s Serving Cell Change
RAB
released and if

released and if

ssion Release.5 4.After releasing the resources, the NodeB sends a RADIO LINK DELETION RESPONSE mess
release
procedure ends.
Connection Release.6
nection.
PS session
ated dynamically, this significantly reduces the total number of IP addresses required per PLMN. Support of static IP
dresses. This can be useful when accesing secure networks that use the calling IP address as a form of security check.
MN is used, it is the responsibility of the GGSN to allocate and release the dynamic PDP address.
(Service Type=Data) message. After the RR setup completion the UE asks for initial direct transfer to the serving node. The
tial service request (Authentication and ciphering may performed depends on operator's setting)
ardown Indication), PDP Type, Address, APN (Access Point Name), QoS (Quality of Service) Requested, PDP
o indicate whether it requires the use of a static PDP address or whether it requires the use of a dynamic PDP address.
RNC to establish a RABs
RAB setup is done by the RAB Assignment procedure
SGSN
DP Type (optional), PDP Address, APN (Access Point Name (optional) provided by the UE and the PDP context
ge to the affected GGSN. Access Point Name shall be the APN Network Identifier of the APN. The GGSN may use Access
ice for this APN

nerates a Charging Id. The new entry allows the GGSN to route PDP PDUs (Policy Decision Point Protocol Data Units)


signment procedure
re.
H is released)


value=(-24+ (37/2))=-5.5 dB
value= HSDPA Release5


value=000000000001000101010010111
RRC:RRC Connection Setup Complete (DCCH) >>"RRC Connection Setup Complete Desc
value=support GSM (Dual Mode GSM<

value= support HSDPA, UE Category






C Connection Request Description"
graphical and UTRAN Entity Identifiers"
hex2dec(4)=4 , hex2dec(1)=1 ,hex2dec(3)=3 --> MCC=413
hex2dec(0)=0 , hex2dec(1)=1 --> MNC=01
hex2dec(7594)= 30100
OriginatingBackgroundCall (PS MOC)
(-24+ (37/2))=-5.5 dB
HSDPA Release5
C Connection Setup Description"
hex2dec(7594)= 30100
UE capable to support FDD , not TDD
UE capable to support GSM
Signaling Radio Bearer Information Setup ,RB-1
Radio Bearer Mapping

BLER Target= -20 dB
MaxAllowedULTxPower=24 dBm
(-48*2)= -96 dBm (step of 2 dB)

Default Constant DPCCH_Power_offset CPICH_RSCP PCPICH Power
-22 -96 -80 33
-22 -96 -70 33
use Closed Loop Power Control Algorithm1
use long SC on Uplink
Spreading Factor 64 (Uplink)
Spreading Factor 128 (Downlink)

Primary Scrambling code=30
entity=RNCid(12bits)+Cellid(16bits)
0000000000010001010100101111 => RNCid=bin2dec(000000000001)=1 and Cellid=bin2dec(0001010100101111)=5423
C Connection Setup Complete Description"

support GSM (Dual Mode GSM<>UMTS)
Chipering Algorithm A5/3
support Compressed Mode (CM) uplink and downlink

support HSDPA, UE Category 6
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 HS-SCCH channels simultane
value= SF256(downlink)
value= HSDPA Serving Cell's Primary SC = 30
value= SF256(downlink)
value= PrimarySC=30, no longer a HSDPA serving cell ( HSDPA Serving Cell Change)
(Old HSDPA's Serving Cell)

value= PrimarySC=9 is a new HSDPA serving cell ( HSDPA Serving Cell Change)
(New HSDPA's Serving Cell)
value=0000000000010001000111011100=> RNCid=bin2dec(000000000001)=1 and Cellid=bin2dec(0001000111011100)=4572
-107 -16
-107 -26
SCCH channels simultaneously. So one cell only configure up to 4 HS-SCCH channels
100101111)=5423
100101111)=5423
11011100)=4572
L3 Messages - PS(HSUPA) Call Proced

UE NodeB S-RNC

Start Rx
L1 Synchonization

Prepare
Ready

Commit

Prepare

Ready

Commit

Prepare

Ready

Commit

Request

Response

SUPA) Call Procedure
S-RNC CN
1.RRC Connection Establishm
RANAP: Security Mode Command
ALCAP : Iu User Plane Setup PS Session Setup.2

Radio Bearer. 3
Setup
Established
Downlink and Uplink Data Tra
HSPA's Serving Cell Change

RRC Connection Release.6


Packet
remove a
Access
TLLI
(Temporary Logical Link Identity) associated to IMSI.

The support of
1. The UE initiates the PS Session by using the Service Request (Service Type=Data) message.
RNC
sets-up an SCCP connection with the SGSN and transfers the initial service request (Authentica
Configuration
ession Setup.2 3. The SGSN sends a RAB Assignment Request message to the RNC to establish a RABs
subscription
Point
subscription
Point
earer. 3 between
the SGSN and the external PDP network, and to start charging
Accepted. The
between

resource
carrying the
RAB.
7.The
The PS SRNC sendsrelease
session a RADIOprocedure
LINK RECONFIGURATION COMMIT
is performed to release message
services andto theNodeB.
resources after a
9.The SRNC
Triggering sends an RAB
Conditions : TheASSIGNMENT RESPONSE
UE send Deactivate message
PDP context to themessage
request CN. The RAB isset
to RNC. A up.
PD
deactivation,the UE has the state Active. After the PDP Context deactivation procedure the state
1.The
other CN sends an RAB ASSIGNMENT REQUEST message to the SRNC to initiate the RAB se
2.The SRNC sends
PDP contexts an RAB ASSIGNMENT
activated.PDP Deactivation mayRESPONSE
be initiatedmessage
by a:UE to the CN. The message
procedure,SGSN indic
procedure,

nk and Uplink Data Transfer. 4 3.The GGSN removes the PDP context(s) and returns a delete PDP Context Response (TEID) m
network
Serving Cell Change
RAB
released and if

released and if

ssion Release.5 4.After releasing the resources, the NodeB sends a RADIO LINK DELETION RESPONSE mess
release
procedure ends.
Connection Release.6
nection.
PS session
ated dynamically, this significantly reduces the total number of IP addresses required per PLMN. Support of static IP
dresses. This can be useful when accesing secure networks that use the calling IP address as a form of security check.
MN is used, it is the responsibility of the GGSN to allocate and release the dynamic PDP address.
(Service Type=Data) message. After the RR setup completion the UE asks for initial direct transfer to the serving node. The
tial service request (Authentication and ciphering may performed depends on operator's setting)
ardown Indication), PDP Type, Address, APN (Access Point Name), QoS (Quality of Service) Requested, PDP
o indicate whether it requires the use of a static PDP address or whether it requires the use of a dynamic PDP address.
RNC to establish a RABs
RAB setup is done by the RAB Assignment procedure
SGSN
DP Type (optional), PDP Address, APN (Access Point Name (optional) provided by the UE and the PDP context
ge to the affected GGSN. Access Point Name shall be the APN Network Identifier of the APN. The GGSN may use Access
ice for this APN

nerates a Charging Id. The new entry allows the GGSN to route PDP PDUs (Policy Decision Point Protocol Data Units)


signment procedure
re.
H is released)


value=hex2dec(03EA)= 1002
value=(-24+ (39/2))=-4.5 dB
value=Primary Scrambling Code=60 (

value=(-24+ (37/2))=-5.5 dB
value= HSPA Release6
value= UE support HSDPA and E-DCH
value=hex2dec(03EA)= 1002


value=000001100110000001010010100
RRC:RRC Connection Setup Complete (DCCH) >>"RRC Connection Setup Co

value= not support GSM (Locked UMT

value= support HSDPA, UE Category









C Connection Request Description"
hex2dec(03EA)= 1002
OriginatingBackgroundCall (PS MOC)
(-24+ (39/2))=-4.5 dB
Primary Scrambling Code=60 ( Neighbour's SC)

(-24+ (37/2))=-5.5 dB
HSPA Release6
UE support HSDPA and E-DCH (HSUPA)
C Connection Setup Description"
hex2dec(03EA)= 1002
UE capable to support FDD , not TDD
Radio Bearer Mapping

BLER Target= -20 dB
MaxAllowedULTxPower=24 dBm
(-47*2)= -94 dBm (step of 2 dB)
Default Constant DPCCH_Power_offsetCPICH_RSCP

use Closed Loop Power Control Algorithm1 -22 -94 -80
-22 -94 -70
Note :DPCCH_Power_offset is configured by RNC and delivered to UE in RRC Connectio
use long SC on Uplink
Spreading Factor 64 (Uplink)

Primary Scrambling code=60
entity=RNCid(12bits)+Cellid(16bits)
0000011001100000010100101001 => RNCid=bin2dec(000001100110)=102 and Cellid=bin2dec(0000010100101001)=1321
>>"RRC Connection Setup Complete Description"

not support GSM (Locked UMTS Mode)
Chipering Algorithm A5/3

support Compressed Mode (CM) uplink and downlink
support HSDPA, UE Category 8
value= Uplink e-DPDCH (HSUPA) channel information
value= Downlink HS-PDSCH channel information
value= HSDPA and HSUPA Serving Cell's Primary SC = 68
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)
PCPICH Power UL InterferenceUL DPCCH Initial Power
33 -105 -14
33 -105 -24
NC and delivered to UE in RRC Connection Setup.
01001)=1321
L3 Messages - Intra-Frequency Soft Handover Procedure

UE NodeB1
Intra-Frequency Soft Handover within NodeB(Softer-HO)
RRC:Measurement Report (e1a)

"or"
RRC:Measurement Report (e1c)
1.RRC: Active Set Update (DCCH)
2. RRC: Active Set Update Complete (DCCH)
RRC:Measurement Report (e1b)

L3 Messages - Intra-Frequency Soft Handover Procedure
UE NodeB1 *Source NodeB2
Intra-Frequency Soft Handover between NodeBs in a RNC

"or"
ALCAP: Iub U

ALCAP: Iub Us
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 are set up or deleted.
L3 Messages - Intra-Frequency Soft Handov

UE NodeB2 *Target D-RNC
Intra-Frequency Soft Handover between

"or"
2.NBAP:Radio Link Setup Request
3.NBAP:Radio Link Setup Response
1.QAAL2 Establish Request
2.QAAL2 Establish Confirm
1.NBAP:Radio Link Restore Indication
2.RRC: Active Set Update Complete (DCCH)
2. RRC: Active Set Update Complete (DCCH
NBAP:Radio Link Deletion Req
NBAP:Radio Link Deletion Resp

QAAL2 Release Request
QAAL2 Release Confirm
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 are 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 set up or deleted.
>>Intra-Frequency SHO Algorithm and related parameters (Module II)
dover Procedure
S-RNC
Measurement Control: is u
are changed, the RNC notifi
eB(Softer-HO)
Measurement Report: the U
reports the results to the RN
Measurement Control
& Measurement Report
Decision to
setup new Radio Link Addition Proce
radio link
Triggering Conditions: The
Radio Link Addition The procedure of radio lin
2.NBAP:Radio Link Setup Resp 1.The CRNC sends a RADIO
configures the new radio link
2.The NodeB sends a respo
-If all the requested radio l
Active Set Update message andsends a RADIO
-If any radio link fails to be
CCH)
Measurement Control
The active set update pr
The procedure is describe
1.The SRNC sends an ACTI
Decision to be deleted, themessage ind
delete old 2.The UE adds or deletes th
radio link
message.
3.The UE sends a response
-lf adding or deleting the r
Active Set Update (AM)Radio Link Control (RL
CH) -If the ACTIVE SET UPDAT
the Radio Link Removal In
1.NBAP:Radio Link Deletion Req

Radio Link Deletion
2.NBAP:Radio Link Deletion Resp
Radio Link Deletion Pro

The procedure of radio lin
1.The CRNC sends a RADIO
message
-If the radio link are delete
-If the radio link fails to be
message
dover Procedure Click to return to main page

Measurement Control: is u
*Target S-RNC are changed, the RNC notifi
Measurement Report: the U

deBs in a RNC reports the results to the RN
Measurement Control
Decision to
setup new The radio link setup proce
radio link
1.NBAP:Radio Link Setup Req The procedure of radio lin
Radio Link Setup
configures the new radio link
2.NBAP:Radio Link Setup Resp 2.The NodeB sends a respo
-If the radio link is set up,
RADIOLINK SETUP RESPO
ALCAP: Iub User Plane Setup -If the radio link fails to be
QAAL2 Establish Request Iub user plane Setup
QAAL2 Establish Confirm

The Iub user plane setup p

NBAP:Radio Link Restore Indication Iub radio link restore Indication 1. The common transport ch
2. The dedicated transport c
1.The CRNC uses the ALCA
2.The NodeB uses the ALCA
Active Set Update -If the Iub data transport b
-If an Iub data transport be
CH)
The radio link restoration

Measurement Control synchronization of one or m
Decision to After performing UL synchro

delete old
radio link
Active Set Update The active set update pr

CH) Triggering Conditions: The
1.The SRNC sends an ACTI
be deleted, themessage ind
2.The UE adds or deletes th
message.
The active set update pr

1.NBAP:Radio Link Deletion Req 1.The SRNC sends an ACTI
Radio Link Deletion be deleted, themessage ind
2.The UE adds or deletes th
2.NBAP:Radio Link Deletion Resp message.
3.The UE sends a response
-lf adding or deleting the r
ALCAP: Iub User Plane Release (AM)Radio Link Control (RL
-If the ACTIVE SET UPDAT
the Radio Link Removal In
QAAL2 Release Request Iub user plane release
Radio Link Deletion Pro

The procedure of radio lin
message
The Iub user plane relea

1.The CRNC uses the ALCA
2.The NodeB uses the ALCA
-If the Iub data transport b
-lf an Iub data transport be
quency Soft Handover Procedure Click to return to main page

*Target NodeB1 *Source S-RNC
oft Handover between RNCs
Measurement Control
Measurement Control
asurement Report (e1a)
Decision
to setup
asurement Report (e1c) 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
ALCAP: Iur User Plane Setup
1.QAAL2 Establish Request Iur user plane Setup
2.RNSAP:Radio Link Restore Indication Iur Radio Link Restore In
tive Set Update (DCCH)

Active Set Update
et Update Complete (DCCH)
Measurement Control Measurement Control

asurement Report (e1b)
Decision
to delete
old radio
link
tive Set Update (DCCH)
Active Set Update
Set Update Complete (DCCH)
1.RNSAP:Radio Link Deletion Req

Radio Link Deletion
Iub user plane

release
QAAL2 Release Request Iur user plane release

meters (Module II)
Measurement Control: is used to notify the UE of the objects to be measured, neighbor cell list, report method, and event parameters.Wh
are changed, the RNC notifies the UE of new conditions.
Measurement Report: the UE continue measure the radio link condition of serving and neighbour cell and when the measurement report
reports the results to the RNC as an event. The Measurement report is also can be sent in periodic mode.
Radio Link Addition Procedure is performed to add one or more radio links towards a UE.
Triggering Conditions: The CRNC sends a RADIO LINK ADDITION REQUEST message.
The procedure of radio link setup is described as follows:

1.The CRNC sends a RADIO LINK ADDITION REQUEST message to the NodeB. After receiving the message, the NodeB reserves the n
configures the new radio link or links according to the parameters given in the message.
2.The NodeB sends a response message to the CRNC.
-If all the requested radio links are added, the NodeB saves the value of the Configuration Generation ID IE contained in the RADIO LIN
message andsends a RADIO LINK ADDITION RESPONSE message.
-If any radio link fails to be added, the NodeB sends a RADIO LINK ADDITION FAILURE message. The message contains the failure c
The active set update procedure is performed to update the active set of radio links between theUE and the UTRAN.
Triggering Conditions: The active set update procedure can be triggered in either of the following conditions: Radio link addition or Radio
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 added, the message indicates radio link addi
be deleted, themessage indicates radio link deletion.
2.The UE adds or deletes the radio links according to the Radio Link Addition Informationor Radio Link Removal Information IE contained
message.
-lf adding or deleting the radio links successfully, the UE sends an ACTIVE SETUPDATE COMPLETE message on the DCCH by usin
(AM)Radio Link Control (RLC).
-If the ACTIVE SET UPDATE message contains the configuration not supported by the UE or if the active set does not contain the
the Radio Link Removal Information IE, the UE sends an ACTIVE SET UPDATE FAILURE message.
Radio Link Deletion Procedure is performed to release resources in a NodeB for one or more established radio links towards a UE
Triggering Conditions: The CRNC sends a RADIO LINK DELETION REQUEST message.
The procedure of radio link deletion is described as follows:
1.The CRNC sends a RADIO LINK SETUP REQUEST message to the NodeB. After receiving the message, the NodeB deletes the radio
message
-If the radio link are deleted, the NodeB sends a RADIO LINK DELETION RESPONSE message.
-If the radio link fails to be deleted, the NodeB sends a RADIO LINK DELETION RESPONSE message. The message contains the failu
message
Measurement Control: is used to notify the UE of the objects to be measured, neighbor cell list, report method, and event parameters.Wh
are changed, the RNC notifies the UE of new conditions.
Measurement Report: the UE continue measure the radio link condition of serving and neighbour cell and when the measurement report
reports the results to the RNC as an event. The Measurement report is also can be sent in periodic mode.
The radio link setup procedure (intra-RNC handover or GSM to WCDMA CS handover) is performed to set up a radio link in an SRNC
Triggering Conditions: The CRNC sends a RADIO LINK SETUP REQUEST message.
1.The CRNC sends a RADIO LINK SETUP REQUEST message to the NodeB. After receiving the message, the NodeB reserves the nece
configures the new radio link according to the parameters given in the message.
-If the radio link is set up, the NodeB saves the value of the Configuration Generation ID IE contained in the RADIO LINK SETUP REQU
RADIOLINK SETUP RESPONSE message.
-If the radio link fails to be set up, the NodeB sends a RADIO LINK SETUP FAILURE message. The message contains the failure caus
The Iub user plane setup procedure is performed to set up bearers for data transmission on the Iub interface
Triggering Conditions: The Iub user plane setup procedure can be triggered in one of the following conditions:
1. The common transport channels are setup
2. The dedicated transport channels are setup
1.The CRNC uses the ALCAP protocol to send a QAAL2 ESTABLISH REQUEST messageto the NodeB.
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 CONFIRM message.
-If an Iub data transport bearer fails to be set up, the NodeB sends a QAAL2 ESTABLISH RELEASE CONFIRM message.
The radio link restoration procedure (intra-RNC handover or GSM to WCDMA CS handover) is performed for a NodeB to notify the
synchronization of one or more radio links is achieved or re-achieved
Triggering Conditions: The nodeB detect UL signals from the UE. That is ,the NodeB finishs UL synchronization with the UE
After performing UL synchronization with the UE, the NodeB sends a RADIO LINK RESTORE INDICATION message to the CRNC.
message.
message.
-lf adding or deleting the radio links successfully, the UE sends an ACTIVE SETUPDATE COMPLETE message on the DCCH by usin
-If the ACTIVE SET UPDATE message contains the configuration not supported by the UE or if the active set does not contain the
the Radio Link Removal Information IE, the UE sends an ACTIVE SET UPDATE FAILURE message.
Radio Link Deletion Procedure is performed to release resources in a NodeB for one or more established radio links towards a UE
The procedure of radio link deletion is described as follows:
message
The Iub user plane release procedure is performed to release data transport bearers from the Iub interface.
Triggering Conditions: The transport channels on the Iub user plane need to be removed
1.The CRNC uses the ALCAP protocol to send a QAAL2 RELEASE REQUEST messageto the NodeB.
-If the Iub data transport bearers are released, the NodeB sends a QAAL2 RELEASE CONFIRM message to confirm the release.
-lf an Iub data transport bearer fails to be released, the NodeB sends a QAAL2 RELEASECONFIRM message that indicates the failure
Measurement Control: is used to notify the UE of the objects to be measured, neighbor cel
changed, the RNC notifies the UE of new conditions.
Measurement Report: the UE continue measure the radio link condition of serving and neig
reports the results to the RNC as an event. The Measurement report is also can be sent in p
Measurement Control
The radio link setup procedure for inter-RNC handover is performed to set up a radio link
Triggering Conditions: The SRNC sends a RADIO LINK SETUP REQUEST message
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.
The radio link setup procedure for inter-RNC handover is performed to set up a radio link
Triggering Conditions: The SRNC sends a RADIO LINK SETUP REQUEST message
3.The NodeB reserves the necessary resources and configures the new radio link according
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
-If the radio link fails to be set up, the NodeB sends a RADIO LINK SETUP FAILURE mes
Radio Link Setup 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.
Iub user plane Setup -If the radio link fails to be set up, the DRNC sends a RADIO LINK SETUP FAILUREmess
The Iub user plane setup procedure is performed to set up bearers for data transmission o
Iub Radio Link Restore Indication
Triggering Conditions: The Iub user plane setup procedure can be triggered in one of
1. The common transport channels are setup
2. The dedicated transport channels are setup
Iur user plane Setup The procedure is described as follows:

1.The CRNC uses the ALCAP protocol to send a QAAL2 ESTABLISH REQUEST messageto
-If the Iub data transport bearers are set up, the NodeB sends a QAAL2 ESTABLISH CON
-If an Iub data transport bearer fails to be set up, the NodeB sends a QAAL2 ESTABLISH
Iur Radio Link Restore Indication
Active Set Update The radio link restoration procedure for inter-RNC handover is performed for a NodeB to
achieved or re-achieved.
Triggering Conditons: The NodeB detects UL signals from the UE. That is, the NodeB finis

Measurement Control 1.After performing UL synchronization with the UE, the NodeB sends a RADIO LINKRESTOR
& Measurement Report 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 transmission o
Triggering Conditons: The DCHs are set up

Active Set Update
1.The SRNC uses the ALCAP protocol to send a QAAL2 ESTABLISH REQUEST messageto
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 ESTABLISHCONF
-If an Iur data transport bearer fails to be set up, the DRNC sends a QAAL2 ESTABLISHR
The active set update procedure is performed to update the active set of radio links betwe
Radio Link Deletion
Triggering Conditions: The active set update procedure can be triggered in either of the fol
Iub user plane
release 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
deleted, themessage indicates radio link deletion.
2.The UE adds or deletes the radio links according to the Radio Link Addition Informationor R
message.
-lf adding or deleting the radio links successfully, the UE sends an ACTIVE SETUPDATE
-If the ACTIVE SET UPDATE message contains the configuration not supported by the
Radio Link Removal Information IE, the UE sends an ACTIVE SET UPDATE FAILURE me
Iur user plane release
The radio link deletion procedure is performed to release resources in a NodeB for one or
1.The CRNC sends a RADIO LINK DELETION REQUEST message to the NodeB. After rece
message.
-If all the radio links are deleted, the NodeB sends a RADIO LINK DELETION RESPONSE
-If any radio link fails to be deleted, the NodeB sends a RADIO LINK DELETIONRESPON
failure cause.
The Iub user plane release procedure is performed to release data transport bearers from
Triggering Conditions: The transport channels on the Iub user plane need to be removed.
1.The CRNC uses the ALCAP protocol to send a QAAL2 RELEASE REQUEST messageto t
-If the Iub data transport bearers are released, the NodeB sends a QAAL2 RELEASECON
-If an Iub data transport bearer fails to be released, the NodeB sends a QAAL2 RELEAS
The Iur user plane release procedure is performed to releaseto release data transport bea
Triggering Conditions: The transport channels on the Iub user plane need to be removed.
1.The CRNC uses the ALCAP protocol to send a QAAL2 RELEASE REQUEST messageto t
-If the Iub data transport bearers are released, the NodeB sends a QAAL2 RELEASECON
-If an Iub data transport bearer fails to be released, the NodeB sends a QAAL2 RELEAS
ethod, and event parameters.When measurement conditions
d when the measurement reporting criterias are met, the UE
sage, the NodeB reserves the necessary resources and
D IE contained in the RADIO LINK ADDITION REQUEST
e message contains the failure cause in the Cause IE.
and the UTRAN.
ions: Radio link addition or Radio link deletion
message indicates radio link addition. If a radio link needs to
moval Information IE contained in the ACTIVE SET UPDATE
E message on the DCCH by using Acknowledged Mode
active set does not contain the radio links specified by
shed radio links towards a UE
ge, the NodeB deletes the radio links specified by the
. The message contains the failure cause.

ethod, and event parameters.When measurement conditions
d when the measurement reporting criterias are met, the UE
to set up a radio link in an SRNC-controlled NodeB for a UE
ge, the NodeB reserves the necessary resources and
the RADIO LINK SETUP REQUEST message and sends a
essage contains the failure cause.
rface
itions:
age.
CONFIRM message.
ormed for a NodeB to notify the CRNC that the uplink
nization with the UE
N message to the CRNC.
and the UTRAN.
ions: Radio link addition or Radio link deletion
message indicates radio link addition. If a radio link needs to
moval Information IE contained in the ACTIVE SET UPDATE

shed radio links towards a UE
ge, the NodeB deletes the radio links specified by the
. The message contains the failure cause.
terface.
age to confirm the release.

message that indicates the failure cause
ts to be measured, neighbor cell list, report method, and event parameters.When measurement conditions are
nk condition of serving and neighbour cell and when the measurement reporting criterias are met, the UE
nt report is also can be sent in periodic mode.
s performed to set up a radio link in a DRNC-controlled NodeB for a UE
ETUP REQUEST message
age to the DRNC.

sage to the target NodeB.
p bearers for data transmission on the Iub interface
ure can be triggered in one of the following conditions:
TABLISH REQUEST messageto the NodeB.

message to the CRNC.
ends a QAAL2 ESTABLISH CONFIRM message.
eB sends a QAAL2 ESTABLISH RELEASE CONFIRM message.
over is performed for a NodeB to notify the SRNC that the uplink synchronization of one or more radio links is
the UE. That is, the NodeB finishes UL synchronizationwith the UE.
eB sends a RADIO LINKRESTORE INDICATION message to the DRNC.

bearers for data transmission on the Iur interface
TABLISH REQUEST messageto the DRNC.

nds a QAAL2 ESTABLISHCONFIRM message.
NC sends a QAAL2 ESTABLISHRELEASE CONFIRM message.
he active set of radio links between the UE and the UTRAN.
n be triggered in either of the following conditions: Radio link addition or Radio link deletion
he UE. If a radio link needs to be added, the message indicates radio link addition. If a radio link needs to be
adio Link Addition Informationor Radio Link Removal Information IE contained in the ACTIVE SET UPDATE
E sends an ACTIVE SETUPDATE COMPLETE message on the DCCH by using Acknowledged Mode
guration not supported by the UE or if the active set does not contain the radio links specified by the
IVE SET UPDATE FAILURE message.
resources in a NodeB for one or more established radio links towards a UE.
ELETION REQUEST message.
message to the NodeB. After receiving the message, the NodeB deletes the radio links specified by the
O LINK DELETION RESPONSE message

ADIO LINK DELETIONRESPONSE message. The Criticality Diagnostics field in the message indicates the
ase data transport bearers from the Iub interface.
user plane need to be removed.
LEASE REQUEST messageto the NodeB.

B sends a QAAL2 RELEASECONFIRM message to confirm the release.
NodeB sends a QAAL2 RELEASECONFIRM message that indicates the failure cause.
aseto release data transport bearers from the Iur interface.
user plane need to be removed.
LEASE REQUEST messageto the NodeB.

B sends a QAAL2 RELEASECONFIRM message to confirm the release.
NodeB sends a QAAL2 RELEASECONFIRM message that indicates the failure cause.
value=intraFrequencyMea
value=intraFrequencyCell
value=IntraFreqCellID of S
value=Primary Scrambling
value=IntraFreqCellID of S
value=CIO=0 (No offset on
value=Primary Scrambling
value=Intra-freq meas L3 f
value=Intra-freq Measure Q
>>Intra-Frequency SHO Al
value=event1a triggered b
value=3 dB (IntraRelThdFo
value=0
value=Maximum active se
value=16
value=4000ms
value=0
value=320ms
value=UE report All Active
value=event1b triggered b
value=6 dB (IntraRelThdFo
value=0
value=0
value=640ms
value=UE report All 3 Activ
value=event1C triggered w
value=16
value=4000ms
value=4 dB (1C hysteresis
value=640ms
value=4dB (1D hysteresis)

value=640ms
value=event1f triggered by
value= 1F event absolute E

value= 4 dB,step: 0.5
value=640ms
value=UE report All 3 Activ

value=CPICH Ec/No= -24+
value=CPICH RSCP= -115+
value=Event1a is triggered
value=To add neighbour P


value=Event1b is triggered
value=To delete neighbou


value=Event1c is triggered
value=To replace Cell Prim

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 and DETSET_RPRT_SWITCH is "Active")
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 e1a)
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=Event1b is triggered
value=To delete neighbour Primary Scrambling Code=74 from Active Set
value=CPICH Ec/No= -24+(20/2) = -14 dB
value=CPICH Ec/No= -24+(8/2) = -20 dB

value=Event1c is triggered
value=To replace Cell Primary Scrambling Code=56 by Cell Primary Scrambling Code=106
d DETSET_RPRT_SWITCH is "Active")
L3 Messages - Intra-Frequency Hard Handover Procedure

Intra-Frequency Hard Handover between NodeBs in a RNC
Start Rx
ALCAP: Iub
Start Tx
1.RRC: Physical Channel Reconfiguration (DCCH)
2. RRC:Physical Channel Reconfiguration Complete (DCCH)
Stop Rx/Tx
1.QAAL2 Release Request
2.QAAL2 Release Confirm
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
L3 Messages - Intra-Frequency Hard Hando

Intra-Frequency Hard Handover between
Start Rx
Start Tx
1. RRC:Physical Channel Reconfiguration (DCC
2. RRC:Physical Channel Reconfiguration Complete

3.If IP transport is applied to the Iur interface, no ALCAP procedure is performed on the Iurinterface
>>Intra-Frequency HHO Algorithm and related parameters
dover Procedure
*Target S-RNC
Measurement C
measurement co
deBs in a RNC
Measurement R
criterias are met,
Measurement Control
Decision to
setup new
radio link The radio link se
controlled NodeB
The procedure o
1.The CRNC sen

Radio Link Setup resources and co
2.NBAP:Radio Link Setup Resp 2.The NodeB sen
IE contained in th
set up, the NodeB
1.QAAL2 Establish Request Iub user plane Setup
2.QAAL2 Establish Confirm The Iub user pla
The procedure i
1.The CRNC use
NBAP:Radio Link Restore Indication Iub radio link restore Indication 2.The NodeB use
a QAAL2 ESTAB
CONFIRM messa
DCCH)
Physical Reconfiguration
ete (DCCH)
The radio link re
the uplink synchr
Decision to
delete old After performing
radio link
adio Link Deletion Req The physical ch

The procedure i
Radio Link Deletion 1.The SRNC sen
2.The UE saves
SRNC.
->If successfully
PHYSICAL CHAN
->If failing to reco
configuration to t
DCCH by using A
The physical ch
The procedure i
1.The SRNC sen
2.The UE saves
adio Link Deletion Resp SRNC.
->If successfully
PHYSICAL CHAN
b User Plane Release ->If failing to reco
configuration to t
Iub user plane release DCCH by using A
2 Release Request "physical channe
L2 Release Confirm
The radio link de

The procedure i
1.The CRNC sen
links specified by
2.The NodeB sen
message.
3. lf any radio link
message indicate
The Iub user pla

The procedure i
1.The CRNC use
2.The NodeB use
->If the Iub data t
->lf an Iub data tr
uency Hard Handover Procedure Click to return to

*Target NodeB1 *Source S-RNC *Source
rd Handover between RNCs

>>Measurement Control&R
easurement Control
Measurement Cont
& Measurement Re
urement Report (e1d)
Decision to
setup new
radio link

Radio Link Setup
Iub Radio Link Resto
2.RNSAP:Radio Link Setup Response
1.QAAL2 Establish Request Iur user plane Setup
Iur Radio Link Resto

2.RNSAP:Radio Link Restore Indication
annel Reconfiguration (DCCH)

Physical Reconfigu
Reconfiguration Complete (DCCH)
Decision to
delete old
radio link

Radio Link Deletion
Stop
Rx/Tx
1.QAAL2 Release Request Iub user plane relea

1.QAAL2 Release Request Iur user plane rele

Measurement Control is used to notify the UE of the objects to be measured, neighbor cell list, report method, and event paramete
measurement conditions are changed, the RNC notifies the UE of new conditions.
Measurement Report, the UE continue measure the radio link condition of serving and neighbour cell and when the measurement r
criterias are met, the UE reports the results to the RNC as an event. The Measurement report is also can be sent in periodic mode.
The radio link setup procedure (intra-RNC handover or GSM to WCDMA CS handover) is performed to set up a radio link in an SR
controlled NodeB for a UE
1.The CRNC sends a RADIO LINK SETUP REQUEST message to the NodeB. After receiving the message, the NodeB reserves the
resources and configures the new radio link according to the parameters 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 Ge
IE contained in the RADIO LINK SETUP REQUEST message and sends a RADIOLINK SETUP RESPONSE message.If the radio li
set up, the NodeB sends a RADIO LINK SETUP FAILURE message. The message contains the failure cause.

2.The NodeB uses the ALCAP protocol to send a response message to the CRNC.lIf the Iub data transport bearers are set up, the N
a QAAL2 ESTABLISH CONFIRM message.If an Iub data transport bearer fails to be set up, the NodeB sends a QAAL2 ESTABLISH
CONFIRM message.
The radio link restoration procedure (intra-RNC handover or GSM to WCDMA CS handover)is performed for a NodeB to notify the
the uplink synchronization of one or more radio links is achieved or re-achieved
After performing UL synchronization with the UE, the NodeB sends a RADIO LINK RESTOREINDICATION message to the CRNC.
The physical channel reconfiguration procedure is performed to set up, reconfigure, or releasea physical channel
1.The SRNC sends a PHYSICAL CHANNEL RECONFIGURATION message to the UE to request reconfiguration of a physical chan
2.The UE saves the IEs of the UE, Radio Bearer (RB), transport channel, and physical channel.The UE sends a response message
SRNC.
->If successfully reconfiguring the physical channels specified by the PHYSICALCHANNEL RECONFIGURATION message, the UE
PHYSICAL CHANNELRECONFIGURATION COMPLETE message on the uplink DCCH by using AM RLC
->If failing to reconfigure the physical channels specified by the PHYSICAL CHANNELRECONFIGURATION message, the UE resto
configuration to the old physicalchannel configuration and sends a PHYSICAL CHANNEL RECONFIGURATION FAILURE message
DCCH by using AM RLC. The value of the Failure cause IE contained in the PHYSICAL CHANNEL RECONFIGURATION FAILURE
1.The SRNC sends a PHYSICAL CHANNEL RECONFIGURATION message to the UE to request reconfiguration of a physical chan
2.The UE saves the IEs of the UE, Radio Bearer (RB), transport channel, and physical channel.The UE sends a response message
SRNC.
->If successfully reconfiguring the physical channels specified by the PHYSICALCHANNEL RECONFIGURATION message, the UE
->If failing to reconfigure the physical channels specified by the PHYSICAL CHANNELRECONFIGURATION message, the UE resto
configuration to the old physicalchannel configuration and sends a PHYSICAL CHANNEL RECONFIGURATION FAILURE message
DCCH by using AM RLC. The value of the Failure cause IE contained in the PHYSICAL CHANNEL RECONFIGURATION FAILURE
"physical channel failure".
The radio link deletion procedure is performed to release resources in a NodeB for one or more established radio links towards a U
1.The CRNC sends a RADIO LINK DELETION REQUEST message to the NodeB. After receiving the message, the NodeB deletes
links specified by the message.
2.The NodeB sends a response message to the CRNC.lf all the radio links are deleted, the NodeB sends a RADIO LINK DELETION
message.
3. lf any radio link fails to be deleted, the NodeB sends a RADIO LINK DELETION RESPONSE message. The Criticality Diagnostics
message indicates the failure cause.
The Iub user plane release procedure is performed to release data transport bearers from the Iubinterface.
->If the Iub data transport bearers are released, the NodeB sends a QAAL2 RELEASE CONFIRM message to confirm the release.
->lf an Iub data transport bearer fails to be released, the NodeB sends a QAAL2 RELEASECONFIRM message that indicates the fa
Measurement Control is used to notify the UE of the objects to be measured, neighb

changed, the RNC notifies the UE of new conditions.
Measurement Control&Report Description
Measurement Report, the UE continue measure the radio link condition of serving an
Measurement Control the results to the RNC as an event. The Measurement report is also can be sent in pe
The radio link setup procedure for inter-RNC handover is performed to set up a radio l
3.The NodeB reserves the necessary resources and configures the new radio link acc
result to the DRNC.
->If the radio link is set up, the NodeB saves the value of the Configuration Generation
->If the radio link fails to be set up, the NodeB sends a RADIO LINK SETUP FAILURE
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 RESPONSEmess
->If the radio link fails to be set up, the DRNC sends a RADIO LINK SETUP FAILURE
3.The NodeB reserves the necessary resources and configures the new radio link acc
result to the DRNC.
->If the radio link is set up, the NodeB saves the value of the Configuration Generation
->If the radio link fails to be set up, the NodeB sends a RADIO LINK SETUP FAILURE
->If the radio link is set up, the DRNC sends a RADIO LINK SETUP RESPONSEmess
Radio Link Setup ->If the radio link fails to be set up, the DRNC sends a RADIO LINK SETUP FAILURE
The Iub user plane setup procedure is performed to set up bearers for data transmis
Iub Radio Link Restore Indication The procedure is described as follows:
1.The CRNC uses the ALCAP protocol to send a QAAL2 ESTABLISH REQUEST mes
->If the Iub data transport bearers are set up, the NodeB sends a QAAL2 ESTABLISH
->If an Iub data transport bearer fails to be set up, the NodeB sends a QAAL2 ESTAB
Iur user plane Setup
The radio link restoration procedure for inter-RNC handover is performed for a Node
1.After performing UL synchronization with the UE, the NodeB sends a RADIO LINKR
Iur 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 transmiss
1.The SRNC uses the ALCAP protocol to send a QAAL2 ESTABLISH REQUEST mes
->If the Iur data transport bearers are set up, the DRNC sends a QAAL2 ESTABLISHC
->If an Iur data transport bearer fails to be set up, the DRNC sends a QAAL2 ESTABL
The physical channel reconfiguration procedure is performed to set up, reconfigure

1.The SRNC sends a PHYSICAL CHANNEL RECONFIGURATION message to the UE
2.The UE saves the IEs of the UE, Radio Bearer (RB), transport channel, and physica
Radio Link Deletion ->If successfully reconfiguring the physical channels specified by the PHYSICALCHAN
CHANNELRECONFIGURATION COMPLETE message on the uplink DCCH by using
->If failing to reconfigure the physical channels specified by the PHYSICAL CHANNEL
physicalchannel configuration and sends a PHYSICAL CHANNEL RECONFIGURATIO
IE contained in the PHYSICAL CHANNEL RECONFIGURATION FAILURE message is
Iub user plane release

The radio link deletion procedure is performed to release resources in a NodeB for o

1.The CRNC sends a RADIO LINK DELETION REQUEST message to the NodeB. Aft
->lf all the radio links are deleted, the NodeB sends a RADIO LINK DELETION RESPO
->lf any radio link fails to be deleted, the NodeB sends a RADIO LINK DELETION RES
cause.
The radio link deletion procedure is performed to release resources in a NodeB for o

1.The CRNC sends a RADIO LINK DELETION REQUEST message to the NodeB. Aft
->lf all the radio links are deleted, the NodeB sends a RADIO LINK DELETION RESPO
->lf any radio link fails to be deleted, the NodeB sends a RADIO LINK DELETION RES
cause.
Iur user plane release
The Iub user plane release procedure is performed to release data transport bearers

1.The CRNC uses the ALCAP protocol to send a QAAL2 RELEASE REQUEST messa
->If the Iub data transport bearers are released, the NodeB sends a QAAL2 RELEASE
->lf an Iub data transport bearer fails to be released, the NodeB sends a QAAL2 RELE
The Iur user plane release procedure is performed to release data transport bearers

1.The SRNC uses the ALCAP protocol to send a QAAL2 RELEASE REQUEST messa
->If the Iur data transport bearers are released, the DRNC sends a QAAL2 RELEASE
->If an Iur data transport bearer fails to be released, the DRNC sends a QAAL2 RELE
port method, and event parameters.When
cell and when the measurement reporting

so can be sent in periodic mode.
med to set up a radio link in an SRNC-
message, the NodeB reserves the necessary
the value of the Configuration Generation ID

ESPONSE message.If the radio link fails to be
ailure cause.
ub interface
NodeB.
transport bearers are set up, the NodeB sends
odeB sends a QAAL2 ESTABLISH RELEASE
erformed for a NodeB to notify the CRNC that
CATION message to the CRNC.
a physical channel
reconfiguration of a physical channel.

e UE sends a response message to the
NFIGURATION message, the UE sends a

AM RLC
URATION message, the UE restores the
FIGURATION FAILURE message on the
L RECONFIGURATION FAILURE message is
established radio links towards a UE.
the message, the NodeB deletes the radio
sends a RADIO LINK DELETION RESPONSE
essage. The Criticality Diagnostics field in the
binterface.
deB.
message to confirm the release.

RM message that indicates the failure cause
e objects to be measured, neighbor cell list, report method, and event parameters.When measurement conditions are
.
e radio link condition of serving and neighbour cell and when the measurement reporting criterias are met, the UE reports
nt report is also can be sent in periodic mode.
ver is performed to set up a radio link in a DRNC-controlled NodeB for a UE
ST message to the DRNC.

ST message to the target NodeB.
configures the new radio link according to the parameters given in the message.The NodeB reports the radio link setup
ue of the Configuration GenerationID IE contained in the RADIO LINK SETUP REQUEST message and sends a
s a RADIO LINK SETUP FAILUREmessage.

e SRNC.
O LINK SETUP RESPONSEmessage.
a RADIO LINK SETUP FAILURE message, indicating the failure cause.
o set up bearers for data transmission on the Iub interface
AAL2 ESTABLISH REQUEST messageto the NodeB.

sponse message to the CRNC.
odeB sends a QAAL2 ESTABLISH CONFIRM message.
e NodeB sends a QAAL2 ESTABLISH RELEASE CONFIRM message
handover is performed for a NodeB to notify the SRNC that the uplink synchronization of one or more radio links is
he NodeB sends a RADIO LINKRESTORE INDICATION message to the DRNC.

CATION message to the SRNC.
o set up bearers for data transmission on the Iur interface
AAL2 ESTABLISH REQUEST message to the DRNC.

sponse message to the SRNC.
NC sends a QAAL2 ESTABLISHCONFIRM message.
e DRNC sends a QAAL2 ESTABLISHRELEASE CONFIRM message.
s performed to set up, reconfigure, or releasea physical channel
NFIGURATION message to the UE to request reconfiguration of a physical channel.

B), transport channel, and physical channel.The UE sends a response message to the SRNC.
specified by the PHYSICALCHANNEL RECONFIGURATION message, the UE sends a PHYSICAL
age on the uplink DCCH by using AM RLC
ified by the PHYSICAL CHANNELRECONFIGURATION message, the UE restores the configuration to the old
AL CHANNEL RECONFIGURATION FAILURE message on the DCCH by using AM RLC. The value of the Failure cause
IGURATION FAILURE message is "physical channel failure".
elease resources in a NodeB for one or more established radio links towards a UE.
QUEST message to the NodeB. After receiving the message, the NodeB deletes the radio links specified by the message.
NC.
a RADIO LINK DELETION RESPONSE message.
ds a RADIO LINK DELETION RESPONSE message. The Criticality Diagnostics field in the message indicates the failure
d to release data transport bearers from the Iubinterface.
AAL2 RELEASE REQUEST messageto the NodeB.

NodeB sends a QAAL2 RELEASE CONFIRM message to confirm the release.
the NodeB sends a QAAL2 RELEASECONFIRM message that indicates the failure cause
to release data transport bearers from the Iur interface
AAL2 RELEASE REQUEST messageto the DRNC.

DRNC sends a QAAL2 RELEASECONFIRM message to confirm the release.
the DRNC sends a QAAL2 RELEASECONFIRM message that indicates the failure cause.
L3 Messages - Inter-Frequency Hard Handover Procedure

Inter-Frequency Hard Handover between NodeBs in a RNC
NBAP: Radio Link Reconfiguration Prepare
NBAP: Radio Link Reconfiguration Ready
NBAP: Radio Link Reconfiguration Commit
RRC:Physical Channel Reconfiguration (DCCH)
NBAP: Compressed Mode Command
Start Rx
ALCAP: Iub
Start Tx
1.RRC: Physical Channel Reconfiguration (DCCH)
2. RRC:Physical Channel Reconfiguration Complete (DCCH)
Stop Rx/Tx
1.The radio link setup procedure shown in the figure applies when the source and target cellsof the
handover are controlled by different NodeBs. If the source and target cells arecontrolled by the
same NodeB, the radio link setup procedure should be replaced by theradio link addition
procedure, and the radio link restoration procedure is excluded.
3.If IP transport is applied to the Iub interface, no ALCAP procedure is performed on the Iub
L3 Messages - Inter-Frequency Hard Hando

Inter-Frequency Hard Handover between
Start Rx
Start Tx
1. RRC:Physical Channel Reconfiguration (DCC

3.If IP transport is applied to the Iur interface, no ALCAP procedure is performed on the Iurinterface
>>Intrer-Frequency HHO Algorithm and related parameters
dover Procedure
*Target S-RNC
deBs in a RNC
Measurement Control
nk Reconfiguration Prepare
ink Reconfiguration Ready

>>Compressed Mode Description Module II
nk Reconfiguration Commit
Initial Compressed Mode Configuration
CCH)
e (DCCH)
pressed Mode Command
Inter-Freq Neighbour cells measurement
Decision to
setup new
radio link
Radio Link Setup

2.NBAP:Radio Link Setup Resp
1.QAAL2 Establish Request Iub user plane Setup
Iub radio link restore Indication

NBAP:Radio Link Restore Indication Iub radio link restore Indication
DCCH)
ete (DCCH)
Decision to
delete old
radio link
adio Link Deletion Req

Radio Link Deletion
adio Link Deletion Resp
b User Plane Release
Iub user plane release

2 Release Request
L2 Release Confirm
uency Hard Handover Procedure Click to return to

*Target NodeB1 *Source S-RNC *Source
rd Handover between RNCs
Decision to
setup new
radio link
Radio Link Setup
Iub Radio Link Resto
2.RNSAP:Radio Link Setup Response
1.QAAL2 Establish Request Iur user plan
2.RNSAP:Radio Link Restore Indication Iur Radio Link Restore Ind
annel Reconfiguration (DCCH)

Physical Reconfigura
l Reconfiguration Complete (DCCH)
Decision to
delete old
radio link
Stop Radio Link Deletion
Rx/Tx
1.QAAL2 Release Request Iub user plane relea

Iur user plane releas

Measurement Control is used to notify the UE of the objects to be measured, neighbor cell list, report method, and event para
measurement conditions are changed, the RNC notifies the UE of new conditions.
Measurement Report, the UE continue measure the radio link condition of serving and neighbour cell and when the measurem
are met, the UE reports the results to the RNC as an event. The Measurement report is also can be sent in periodic mode.
Compressed Mode was introduced to WCDMA to allow inter-frequency and Inter-RAT Handovers. It is used to create idle perio
transmission during which neighbour cells measurements on another frequency can be made.
The radio link setup procedure (intra-RNC handover or GSM to WCDMA CS handover) is performed to set up a radio link in a
NodeB for a UE
1.The CRNC sends a RADIO LINK SETUP REQUEST message to the NodeB. After receiving the message, the NodeB reserve
resources and configures the new radio link according to the parameters 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 Configuratio
contained in the RADIO LINK SETUP REQUEST message and sends a RADIOLINK SETUP RESPONSE message.If the radio
the NodeB sends a RADIO LINK SETUP FAILURE message. The message contains the failure cause.

2.The NodeB uses the ALCAP protocol to send a response message to the CRNC.lIf the Iub data transport bearers are set up,
QAAL2 ESTABLISH CONFIRM message.If an Iub data transport bearer fails to be set up, the NodeB sends a QAAL2 ESTABL
CONFIRM message.
The radio link restoration procedure (intra-RNC handover or GSM to WCDMA CS handover)is performed for a NodeB to notif
uplink synchronization of one or more radio links is achieved or re-achieved
After performing UL synchronization with the UE, the NodeB sends a RADIO LINK RESTOREINDICATION message to the CRN
1.The SRNC sends a PHYSICAL CHANNEL RECONFIGURATION message to the UE to request reconfiguration of a physical
2.The UE saves the IEs of the UE, Radio Bearer (RB), transport channel, and physical channel.The UE sends a response mess
->If successfully reconfiguring the physical channels specified by the PHYSICALCHANNEL RECONFIGURATION message, the
->If failing to reconfigure the physical channels specified by the PHYSICAL CHANNELRECONFIGURATION message, the UE
configuration to the old physicalchannel configuration and sends a PHYSICAL CHANNEL RECONFIGURATION FAILURE mes
using AM RLC. The value of the Failure cause IE contained in the PHYSICAL CHANNEL RECONFIGURATION FAILURE mess
channel failure".
The radio link deletion procedure is performed to release resources in a NodeB for one or more established radio links toward
1.The CRNC sends a RADIO LINK DELETION REQUEST message to the NodeB. After receiving the message, the NodeB del
specified by the message.
2.The NodeB sends a response message to the CRNC.lf all the radio links are deleted, the NodeB sends a RADIO LINK DELE
message.
3. lf any radio link fails to be deleted, the NodeB sends a RADIO LINK DELETION RESPONSE message. The Criticality Diagno
message indicates the failure cause.
The Iub user plane release procedure is performed to release data transport bearers from the Iubinterface.
->If the Iub data transport bearers are released, the NodeB sends a QAAL2 RELEASE CONFIRM message to confirm the relea
->lf an Iub data transport bearer fails to be released, the NodeB sends a QAAL2 RELEASECONFIRM message that indicates t

The radio link setup procedure for inter-RNC handover is performed to set u
1.The SRNC sends a RADIO LINK SETUP REQUEST message to the DRN
2.The DRNC sends a RADIO LINK SETUP REQUEST message to the targe
3.The NodeB reserves the necessary resources and configures the new rad
result to the DRNC.
->If the radio link is set up, the NodeB saves the value of the Configuration G
->If the radio link fails to be set up, the NodeB sends a RADIO LINK SETUP
->If the radio link is set up, the DRNC sends a RADIO LINK SETUP RESPO
->If the radio link fails to be set up, the DRNC sends a RADIO LINK SETUP
Radio Link Setup

The Iub user plane setup procedure is performed to set up bearers for data
1.The CRNC uses the ALCAP protocol to send a QAAL2 ESTABLISH REQU
2.The NodeB uses the ALCAP protocol to send a response message to the
->If the Iub data transport bearers are set up, the NodeB sends a QAAL2 ES
Iub Radio Link Restore Indication ->If an Iub data transport bearer fails to be set up, the NodeB sends a QAAL
The radio link restoration procedure for inter-RNC handover is performed

Iur user plane Setup
1.After performing UL synchronization with the UE, the NodeB sends a RAD
2.The DRNC sends a RADIO LINK RESTORE INDICATION message to the
The Iur user plane setup procedure is performed to set up bearers for data
r Radio Link Restore Indication
1.The SRNC uses the ALCAP protocol to send a QAAL2 ESTABLISH REQU
2.The DRNC uses the ALCAP protocol to send a response message to the S
->If the Iur data transport bearers are set up, the DRNC sends a QAAL2 ES
->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, re

1.The SRNC sends a PHYSICAL CHANNEL RECONFIGURATION messag
2.The UE saves the IEs of the UE, Radio Bearer (RB), transport channel, an
->If successfully reconfiguring the physical channels specified by the PHYSI
CHANNELRECONFIGURATION COMPLETE message on the uplink DCCH
->If failing to reconfigure the physical channels specified by the PHYSICAL C
physicalchannel configuration and sends a PHYSICAL CHANNEL RECONF
IE contained in the PHYSICAL CHANNEL RECONFIGURATION FAILURE m
2.The UE saves the IEs of the UE, Radio Bearer (RB), transport channel, an
->If successfully reconfiguring the physical channels specified by the PHYSI
CHANNELRECONFIGURATION COMPLETE message on the uplink DCCH
->If failing to reconfigure the physical channels specified by the PHYSICAL C
physicalchannel configuration and sends a PHYSICAL CHANNEL RECONF
IE contained in the PHYSICAL CHANNEL RECONFIGURATION FAILURE m
Radio Link Deletion
The radio link deletion procedure is performed to release resources in a N

1.The CRNC sends a RADIO LINK DELETION REQUEST message to the N
Iub user plane release 2.The NodeB sends a response message to the CRNC.
->lf all the radio links are deleted, the NodeB sends a RADIO LINK DELETIO
->lf any radio link fails to be deleted, the NodeB sends a RADIO LINK DELE
cause.
The Iub user plane release procedure is performed to release data transpo
Iur user plane release The procedure is described as follows:

1.The CRNC uses the ALCAP protocol to send a QAAL2 RELEASE REQUE
2.The NodeB uses the ALCAP protocol to send a response message to the
->If the Iub data transport bearers are released, the NodeB sends a QAAL2
->lf an Iub data transport bearer fails to be released, the NodeB sends a QA
The Iur user plane release procedure is performed to release data transpo

1.The SRNC uses the ALCAP protocol to send a QAAL2 RELEASE REQUE
2.The DRNC uses the ALCAP protocol to send a response message to the S
->If the Iur data transport bearers are released, the DRNC sends a QAAL2 R
->If an Iur data transport bearer fails to be released, the DRNC sends a QAA
method, and event parameters.When
and when the measurement reporting criterias

nt in periodic mode.
used to create idle periods (gaps) in the
to set up a radio link in an SRNC-controlled
sage, the NodeB reserves the necessary
value of the Configuration Generation ID IE

SE message.If the radio link fails to be set up,
terface
B.
port bearers are set up, the NodeB sends a
ends a QAAL2 ESTABLISH RELEASE
med for a NodeB to notify the CRNC that the
ON message to the CRNC.

sical channel
nfiguration of a physical channel.

sends a response message to the SRNC.
GURATION message, the UE sends a
LC
TION message, the UE restores the
RATION FAILURE message on the DCCH by
RATION FAILURE message is "physical
lished radio links towards a UE.
message, the NodeB deletes the radio links
ds a RADIO LINK DELETION RESPONSE
ge. The Criticality Diagnostics field in the
face.
sage to confirm the release.

message that indicates the failure cause
ver is performed to set up a radio link in a DRNC-controlled NodeB for a UE
ST message to the DRNC.

ST message to the target NodeB.
configures the new radio link according to the parameters given in the message.The NodeB reports the radio link setup
ue of the Configuration GenerationID IE contained in the RADIO LINK SETUP REQUEST message and sends a
s a RADIO LINK SETUP FAILUREmessage.

e SRNC.
O LINK SETUP RESPONSEmessage.
a RADIO LINK SETUP FAILURE message, indicating the failure cause.
o set up bearers for data transmission on the Iub interface
AAL2 ESTABLISH REQUEST messageto the NodeB.

odeB sends a QAAL2 ESTABLISH CONFIRM message.
e NodeB sends a QAAL2 ESTABLISH RELEASE CONFIRM message
handover is performed for a NodeB to notify the SRNC that the uplink synchronization of one or more radio links is
he NodeB sends a RADIO LINKRESTORE INDICATION message to the DRNC.

CATION message to the SRNC.
o set up bearers for data transmission on the Iur interface
AAL2 ESTABLISH REQUEST message to the DRNC.

NC sends a QAAL2 ESTABLISHCONFIRM message.
e DRNC sends a QAAL2 ESTABLISHRELEASE CONFIRM message.
s performed to set up, reconfigure, or releasea physical channel
NFIGURATION message to the UE to request reconfiguration of a physical channel.

B), transport channel, and physical channel.The UE sends a response message to the SRNC.
specified by the PHYSICALCHANNEL RECONFIGURATION message, the UE sends a PHYSICAL
age on the uplink DCCH by using AM RLC
ified by the PHYSICAL CHANNELRECONFIGURATION message, the UE restores the configuration to the old
AL CHANNEL RECONFIGURATION FAILURE message on the DCCH by using AM RLC. The value of the Failure cause
IGURATION FAILURE message is "physical channel failure".
elease resources in a NodeB for one or more established radio links towards a UE.
QUEST message to the NodeB. After receiving the message, the NodeB deletes the radio links specified by the message.
NC.
a RADIO LINK DELETION RESPONSE message.
ds a RADIO LINK DELETION RESPONSE message. The Criticality Diagnostics field in the message indicates the failure
d to release data transport bearers from the Iubinterface.
AAL2 RELEASE REQUEST messageto the NodeB.

NodeB sends a QAAL2 RELEASE CONFIRM message to confirm the release.
the NodeB sends a QAAL2 RELEASECONFIRM message that indicates the failure cause
to release data transport bearers from the Iur interface
AAL2 RELEASE REQUEST messageto the DRNC.

DRNC sends a QAAL2 RELEASECONFIRM message to confirm the release.
the DRNC sends a QAAL2 RELEASECONFIRM message that indicates the failure cause.
L3 Messages - Inter-RAT Hando

UE NodeB S-RNC
Inter-RAT CS Handover from WC
RRC:Measurement Report (e2f)
NBAP: Radio Link Reconfiguration Prepare
NBAP: Radio Link Reconfiguration Ready
NBAP: Radio Link Reconfiguration Commit
1. RRC:Physical Channel Reconfiguration (DCCH)
2. RRC: Physical Channel Reconfiguration Complete (DCCH)
NBAP: Compressed Mode Command
Decision
to HO to
GSM cell
7.RRC: Handover from UTRAN Command
9.Handover Completed
NBAP:Radio Link Deletion Request
NBAP:Radio Link Deletion Response
1.This figure presents only a brief of the signaling between the MSC server and the MSC(GSM)
and that between the MSC (GSM) and the BSC (GSM).
2.The SRNC sends a HANDOVER FROM UTRAN COMMAND message to the UE. The
message contains the RAB ID, the activation time, the GSM frequency, and the GSM
information in bit strings.
L3 Messages - Inter-RAT Hando

UE NodeB S-RNC
Inter-RAT CS Handover from GS
5.NBAP:Radio Link setup Response

9.Inter-System to UTRAN Handover
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)
1.This figure presents only a brief of the signaling between the MSC server and the MSC(GSM)
and that between the MSC (GSM) and the BSC (GSM).
2.After receiving a RADIO LINK RESTORE INDICATION message, the RNC sends a
RELOCATION DETECT message to 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 fails, the UE reports the failure to the GSM system.
4.After receiving a HANDOVER TO UTRAN COMPLETE message, the RNC sends a
RELOCATION COMPLETE message 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
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 fails, the UE reports the failure to the GSM system.
4.After receiving a HANDOVER TO UTRAN COMPLETE message, the RNC sends a
RELOCATION COMPLETE message 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
es - Inter-RAT Handover Procedure
MSC BSC
MSC 3G
2G 2G
T CS Handover from WCDMA to GSM
1.RANAP: Relocation Required

2.Prepare Handover
3.Handover Request
4.Handover Request
Acknowledge
5.Prepare Handover
Response
6.RANAP:Relocation Command
8.Handover Detect
9.Handover Completed
10.Handover Complete
11.Send End Signal
Request
12.RANAP: IU Release Command
13.RANAP: IU Release Complete

14.Send End Signal
Response
es - Inter-RAT Handover Procedure

BSC
MSC-3G MSC-2G
2G
T CS Handover from GSM to WCDMA
1.Handover Required
2.Prepare Handover
3.RANAP: Relocation Request
6.RANAP:Relocation Request
Acknowledge
7.Prepare Handover
Response
8.Handover Command
9.Handover Complete
r-System to UTRAN Handover Command
11.RANAP:Relocation Detect
18.RANAP:Relocation
Complete
19.Send End Signal
Request
20.Clear Command
21.Clear Complete
22.Send End Signal
Response
>>Inter-RAT HO Algorithm and related parameters
BSC
2G
Measurement Control is used to notify the UE of the o

conditions are changed, the RNC notifies the UE of new
>>Measurement Control&Report (Inter-RAT) Description
Measurement Report, the UE continue measure the ra
the UE reports the results to the RNC as an event. The
Measurement Control
Compressed Mode was introduced to WCDMA to allow

during which neighbour cells measurements on another
>>Compressed Mode Description
Initial Compressed Mode Configuration The relocation preparation procedure is performed to
1.The SRNC sends a RELOCATION REQUIRED messa

source PLMN, source LAC,source SAC, target PLMN, a
2.The CN interacts with the target RNC or the target net
->If the target RNC or the target network system prepar
preparation is complete. The message contains the L3 i
the target network system.
->If the resources partially or totally fail to be allocated,
GSM RSSI Measurement
and BSIC Verification
The Inter-RAT Handover procedure is described as fol
1. The SRNC sends the 3G MSC a RANAP message "R

2. As indicated in the received message,the 3G MSC fo
Handover"
3. The 2G MSC forwards the request to the BSC. The m
4. The BSC responds to this request. The message sho
5. Once the initial procedures are completed in the 2G M
6. The 3G MSC sends the SRNC a RANAP message "R
Relocation Preparation 7. The SRNC send the UE and RRC message "Handov
or
several other systems
8. The BSC performs handover detection. The figure do
reference and is subject to the actual conditon of GSM
9. The UE send the BSC a "Handover Complete" messa
10. The BSC sends the MSC a 'Handover Complete" m
GSM
11. After detecting the UE in the coverage area of the G
12. The CN sends the former SRNC and "Iu Release Co
13. After the bearer resource is related in the UMTS, the
or
several other systems
8. The BSC performs handover detection. The figure do
reference and is subject to the actual conditon of GSM
9. The UE send the BSC a "Handover Complete" messa
10. The BSC sends the MSC a 'Handover Complete" m
GSM
11. After detecting the UE in the coverage area of the G
12. The CN sends the former SRNC and "Iu Release Co
Handover 13. After the bearer resource is related in the UMTS, the
14. After the call ends, the CN sends the MSC a MAP/E
Iu release
The Iu release procedure is performed for the CN to rel

1.The CN sends an IU RELEASE COMMAND message
signaling connection.
NOTE: After sending the IU RELEASE COMMAND mes
Radio Link Deletion 2.The SRNC releases the related UTRAN resources an
The radio link deletion procedure is performed to relea

1.The CRNC sends a RADIO LINK DELETION REQUE
the message.
->If all the radio links are deleted, the NodeB sends a R
->If any radio link fails to be deleted, the NodeB sends a
indicates the failure cause.
BSC
2G
The relocation resource allocation procedure is perfo

The relocation resource allocation procedure can be trig
1. During an SRNS relocation, the CN applies for resou
2. During an inter-RAT CS handover from GSM to WCD

1.The CN sends a RELOCATION REQUEST message
indicator, target cell identifier, encryption, integrity protec
2.The target RNC allocates radio resources for the reloc
Relocation Resource allocation 3.The target RNC sends a response message to the CN
->If the resources are allocated, the target RNC sends a
other parameters allocated to the UE. The parameters in
information,chosen encryption algorithm, and chosen in
->If the resources partially or totally fail to be allocated o
FAILURE message,indicating the failure cause
1.The CN sends a RELOCATION REQUEST message
indicator, target cell identifier, encryption, integrity protec
2.The target RNC allocates radio resources for the reloc
Relocation Resource allocation 3.The target RNC sends a response message to the CN
->If the resources are allocated, the target RNC sends a
other parameters allocated to the UE. The parameters in
information,chosen encryption algorithm, and chosen in
->If the resources partially or totally fail to be allocated o
FAILURE message,indicating the failure cause
The radio link setup procedure (intra-RNC handover o

UE
Radio Link Restoration The procedure is described as follows:

1.The CRNC sends a RADIO LINK SETUP REQUEST m
configures the new radio link according to the paramete
->If the radio link is set up, the NodeB saves the value o
sends a RADIO LINK SETUP RESPONSE message.
->If the radio link fails to be set up, the NodeB sends a R
UE Capability Enquiry
The radio link restoration procedure (intra-RNC hando

synchronization of one or moreradio links is achieved or
After performing UL synchronization with the UE, the No

Security Mode Control
The UE capability enquiry procedure is performed to r

can perform data configuration based on the UE capabi

1.The SRNC sends a UE CAPABILITY ENQUIRY mess
2.The UE sends a UE CAPABILITY INFORMATION me
information about UE capabilities.
3.The SRNC reads the UE capability information and th
AM or UMRLC.
UTRAN Mobility Information
The security mode control procedure is performed to

UE. The triggered conditon is when the ciphering algorit
1.Through a SECURITY MODE COMMAND message s
configurations for theRBs or one CN domain and for all
->If the UE completes configuring or reconfiguring the re
SECURITYMODE COMPLETE message to inform the S
->If the SECURITY MODE COMMAND message contai
inconsistent information, the UE sends a SECURITY MO
failure cause.
The UTRAN mobility information procedure is perform
Network TemporaryIdentifier (C-RNTI) to a UE or to info
1.The SRNC sends a UTRAN MOBILITY INFORMATIO

2.The UE starts to update the related fields according to
->If the UE succeeds in conducting the operations spec
INFORMATION CONFIRM message.
->If the UE fails to conduct the operations specified by t
INFORMATIONFAILURE message, indicating the failure
to notify the UE of the objects to be measured, neighbor cell list, report method, and event parameters.When measurement
NC notifies the UE of new conditions.
continue measure the radio link condition of serving and neighbour cell and when the measurement reporting criterias are met,
e RNC as an event. The Measurement report is also can be sent in periodic mode.
duced to WCDMA to allow inter-frequency and Inter-RAT Handovers. It is used to create idle periods (gaps) in the transmission
measurements on another frequency can be made.
rocedure is performed to prepare resources for relocation of the SRNS
as follows:
ATION REQUIRED message to the CN. The message contains certain information such as relocation type, relocation cause,
urce SAC, target PLMN, and target CI,LAC.
get RNC or the target network system, such as the GSM system, to prepare relevant resources.
essage to the SRNC.
et network system prepares the relevant resources successfully, the CN sends a RELOCATION COMMAND message when the
message contains the L3 information IE, which carries the information about the relevant resources allocated by the target RNC or
otally fail to be allocated, the CN sends a RELOCATIONPREPARATION FAILURE message.
edure is described as follows:
SC a RANAP message "Relocation Required" if the condition of Inter-RAT Outgoing HO is met

message,the 3G MSC forwards this request to the 2G MSC on the MAP/E interface through a MAP message "Prepare
equest to the BSC. The message shown in the figure is for reference only and is subject to the actual conditon of the GSM
quest. The message shown in the figure is for reference only and is subject to the actual conditon of the GSM
are completed in the 2G MSC/BSS,the 2G MSC returns a MAP/E message 'Prepare Handover Response"
NC a RANAP message "Relocation Command"
RRC message "Handover from UTRAN" through the existing RRC connection. This message may include information from one
r detection. The figure does not show such procedures as GSM BSS synchronization. The message shown in the figure is for
actual conditon of GSM
ndover Complete" message
'Handover Complete" message. The message shown in the figure for reference only and is subject to the actual condition of the
e coverage area of the GSM,the MSC sends the CN a MAP/E message "Send End Signal Request"
SRNC and "Iu Release Command" message , requesting the former SRNC to release the allocated resource
s related in the UMTS, the former SRNC sends the CN an "Iu Release Complete" message
erformed for the CN to release an Iu connection and all the UTRANresources related only to that Iu connection
as follows:
SE COMMAND message to the SRNC to initiate the Iu release procedure. The message indicates the cause for the release of the
ELEASE COMMAND message, the CN will not send further RANAP connection-oriented messages on this particular connection.
ed UTRAN resources and then sends an IU RELEASE COMPLETE message to the CN.
dure is performed to release resources in a NodeB for one or more established radio links towards a UE.
as follows:
LINK DELETION REQUEST message to the NodeB. After receiving the message, the NodeB deletes the radio links specified by
e message to the CRNC.

ed, the NodeB sends a RADIO LINK DELETION RESPONSE message.
leted, the NodeB sends a RADIO LINK DELETIONRESPONSE message. The Criticality Diagnostics field in the message
cation procedure is performed to allocate resources from the targetRNS for an SRNS relocation.
ion procedure can be triggered in either of the followingconditions:
the CN applies for resources from the target RNC
dover from GSM to WCDMA, the CN applies for resources from the target RNC
as follows:
ON REQUEST message to the target RNC. The message contains certain information, such as the IMSI of the UE, CN domain
ncryption, integrity protection, Iu signaling connection ID, handover cause, andRAB parameters.
dio resources for the relocation.
ponse message to the CN.
d, the target RNC sends a RELOCATION REQUEST ACKNOWLEDGE message. The message contains the radio resources and
he UE. The parameters include the UTRAN Radio NetworkTemporary Identifier (U-RNTI), RAB, transport layer and physical layer
algorithm, and chosen integrity protection algorithm.
otally fail to be allocated or the target RNC rejects the SRNS relocation for some reason, the target RNC sends a RELOCATION
he failure cause
e (intra-RNC handover or GSM to WCDMA CS handover) isperformed to set up a radio link in an SRNC-controlled NodeB for a
as follows:
LINK SETUP REQUEST message to the NodeB. Afterr eceiving the message, the NodeB reserves the necessary resources and
ccording to the parameters given in the message.
e message to the CRNC.
NodeB saves the value of the Configuration GenerationID IE contained in the RADIO LINK SETUP REQUEST message and
RESPONSE message.
up, the NodeB sends a RADIO LINK SETUP FAILURE message. The message contains the failure cause.
cedure (intra-RNC handover or GSM to WCDMA CS handover)is performed for a NodeB to notify the CRNC that the uplink
eradio links is achieved or re-achieved
zation with the UE, the NodeB sends a RADIO LINK RESTOREINDICATION message to the CRNC
ocedure is performed to request a UE to transmit its capability information related to any radio access network so that the network
based on the UE capability
as follows:
ABILITY ENQUIRY message to the UE through the downlink DCCH using AM RLC.
LITY INFORMATION message to the SRNC through the uplink DCCH using AM or UM RLC. The message contains the
es.
ability information and then sends a UE CAPABILITYINFORMA CONFIRM message to the UE through the downlink DCCH using
ocedure is performed to configure or reconfigure one or both of the ciphering algorithm and the integrity protection algorithm for a
when the ciphering algorithm or the integrity protection algorithm has changed
as follows:
E COMMAND message sent to the UE, the SRNC starts or reconfigures one or both of the ciphering and integrity protection
ne CN domain and for all Signaling Radio Bearers (SRBs).
essage to the SRNC.
ng or reconfiguring the relevant parameters for one orboth of the ciphering and integrity protection algorithms, the UE sends a
E message to inform the SRNC of the completion.
MMAND message contains neither Ciphering mode info IE nor Integrity protection mode info IE or if each of the two IEs has
E sends a SECURITY MODE FAILURE message, indicating the failure of the security mode control procedure as well as the
tion procedure is performed for the network to allocate a newUTRAN Radio Network Temporary Identifier (U-RNTI) or Cell Radio
C-RNTI) to a UE or to inform the UE of mobility-related information such as timervalues and CN domain–related information
MOBILITY INFORMATION message to the UE.

elated fields according to the values of the IEs carried in themessage.
essage to the SRNC.
cting the operations specified by the UTRAN MOBILITYINFORMATION message, the UE sends a UTRAN MOBILITY
ssage.
operations specified by the UTRAN MOBILITYINFORMATION message, the UE sends a UTRAN MOBILITY
age, indicating the failure cause.
easurement
iterias are met,
e transmission
ation cause,
sage when the

he target RNC or
repare
the GSM
mation from one
e figure is for
l condition of the
the release of the
ular connection.
nks specified by
message
E, CN domain
io resources and
nd physical layer
RELOCATION
ed NodeB for a
y resources and
message and
t the uplink
o that the network
ains the
nlink DCCH using
on algorithm for a
y protection
he UE sends a
two IEs has

s well as the
TI) or Cell Radio
nformation
ILITY
value=interFrequencyMe
parameter CoexistMeas
value=Inter-freq meas L
value=Inter-freq meas b
value=Event2D ( Start C
value= InterFreqCSThd2
value= 0
value=2 dB ,Step: 0.5
value=320ms
value=Event2f ( Stop Co
value= InterFreqCSThd2
value= 0
value=320ms

value=UE trigger Event2
RRC:Measurement Report (e2f)
value=UE trigger Event2
RRC:Physical Channel Reconfiguration (DCCH)

value=Compressed Mod
RRC: Physical Channel Reconfiguration Complete (DCCH)
value=interRATMeasure
value=InterRAT cell list
value=InterRAT cell Inde
value=InterRATCIO=0
value=NCC=6
value=BCC=4
value=GSM900 ( GSM18
value=BCCH=64
value=UE measure on G
value=InterRATFilterCoe
value=UE need to verify
value=InterRATPeriodRe
value=UE report 6 InterR

value=RSSI= -110 + hex
value=BSIC=35 ( BCCH=
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=320ms
value=Event2f ( Stop Compressed Mode)
value= InterFreqCSThd2FEcN0=-12 dB

value=320ms
value=UE trigger Event2D to start Compressed Mode
value=UE trigger Event2f to stop Compressed Mode

value=Compressed Mode Inforamtion
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)

L3 Mes
SGSN-
UE BSS S-RNC
2G
Inte
The procedure in this

( "RRC: Handover from UTRAN C
1.RRC:Cell Change Order from UTRAN
2.Routing Area Update Request

UE Connected
4.SRNS Context Request
4.SRNS Context Response
6.Secur
UE Connected
8.SRNS Data Forward Command
8.Forward Packets
UE Connected
13.Iu Release Command
13. Iu Release Complete

19.Routing Area Update Accept
20.Routing Area Update Complete
22. BSS Packet Flow Context Procedure
1.When the PS data volume is low, the UE may be in CELL_PCH, URA_PCH, or Cell_FACH state or when UE in I
information, the UE can initiate cell reselection to perform a handover to GSM. The cell reselection is initiated with
the SGSN to SRNC.
When the UE in Idle ,URA_PCH.Cell_PCH or Cell_FACH states, the cell reselection procedure does not include th
Connected)
2.After cell reselection to a GSM cell, the NodeB sends a RADIO LINK FAILURE INDICATION message because t
cell.This message, however, is unnecessary to 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 the SRNC
not need to be transferred.
4.The SRNS context transfer is unnecessary to the procedure of inter-RAT PS handover from WCDMA to GSM.
L3 Mes
SGSN-
UE BSC S-RNC
3G
Inte
1. Inter-RAT Handover
Decision
2.Routing Area Update Request
5.Security Functions
C2
16.Routing Area Update Accept
C3
17.Routing Area Update Complete
19.Service Request
20. RAB Assignement Request

Setup Radio Resources
20. RAB Assignement Response
L3 Messages - Inter-RAT Handover Procedure
SGSN- SGSN- MSC-
GGSN
2G 3G 2G
Inter-RAT PS Handover from WCDMA to GSM
The procedure in this stage is simiilar to Inter-RAT CS Handover from WCDMA to GSM
Handover from UTRAN Command " message is equivalent to "RRC:Cell Change Order from UTRAN" )
3.SGSN Context Request
SRNS Context Request
RNS Context Response
5.SGSN Context Response
6.Security Functions
7.SGSN Context Acknowledge
C1
S Data Forward Command
8.Forward Packets
9. Forward Packets
10. Update PDP Context Request
10. Update PDP Context Response
11. Update GPRS Location
12. Cancel Location
.Iu Release Command
. Iu Release Complete
12. Cancel Location Acknowledge
14. Insert Subscriber Data
14. Insert Subscriber Data Acknowledge
15. Update GPRS Location Acknowledge
16. Location Update Request

17.
18 Location Update Accept
21. TMSI Reallocation Complete
ACH state or when UE in Idle state. Based on the parameters in the system
reselection is initiated with an SRNS CONTEXT REQUEST message sent from
cedure does not include the sub-procedires which marked with "UE
ATION message because the UE stops the transmission towards the WCDMA
from WCDMA to GSM.
AND message to the SRNC, if the Packet Data Protocol (PDP) context does
r from WCDMA to GSM.

SGSN- SGSN- MSC-
GGSN
3G 2G 3G
Inter-RAT PS Handover from GSM to WCDMA
3.SGSN Context Request
4.SGSN Context Response
ecurity Functions
6.SGSN Context Acknowledge
C1
7. Forward Packets
8. Update PDP Context Request
8 Update PDP Context 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
13. Location Update Request

15 Location Update Accept
C2
C3
18. TMSI Reallocation Complete

>>Inter-RAT HO Algorithm and
MSC
HLR
-3G
GSM
from UTRAN" )
SRNS Context Transfer
Cancel Location
Iu release
el Location Acknowledge
edge
edge
17. Update Location
>>Inter-RAT HO Algorithm and

MSC
HLR
-2G
Cancel Location
el Location Acknowledge
edge
edge
14a. Update Location

14b.Cancel Location
14c. Cancel Location Ack

14d. Insert Subscriber Data
14e. Insert Subscriber Data Ack

14f. Update Location Ack
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
cell and stop the data transmission between the UE and the network
2. The UE sends a "Routing Area Update Request" message to the 2G SGSN. The update type in th
with IMSI attach. The BSS adds the CGI including the RAC and LAC of the cell to the received mess
3. The new 2G SGSN sends an "SGSN Context Request" message to the old 3G SGSN to obtain th
P-TMSI Signature is valid, the old 3G SGSN starts a timer. Otherwise, the old 3G SGSN respons wit
4. If the UE stay in connected mode before handover, the old 3G SGSN sends an "SRNS Context R
sending the PDUs to the UE, and send an "SRNS Context Response" message to the old 3G SGSN
SRNS Context Transfer 5. The old 3G SGSN sends an "SGSN Context Response" message to the 2G SGSN including the M
6. The security functions can be excuted
7. The new 2G SGSN sends an 'SGSN Context Acknowledge" message to the old 3G SGSN. This in
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
the old 3G SGSN
9. The old 3G SGSN tunnels the GTP PDUs to the new 2G SGSN. In the PDUs, the sequence numb
10. the new 2G SGSN sends an "Update PDP Context Request" message to each related GGSN. E
message after updating it's PDP Context fields
11. The new 2G SGSN sends an "Update GPRS Location" message ,requesting the HLR to modify t
12. The HLR sends a "Cancel Location" message to the old 3G SGSN. the old 3G SGSN responds w
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
Release complete"
14. The HLR sends an "Insert Subscriber Data" message to the new 2G SGSN. The 2G SGSN cons
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" m
number for creating or updating the association
Iu release
17. If the subscriber data in VLR is marked as not confirmed by the HLR. the new VLR informs the H
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" mes
16. If the association has to be established, the new 2G SGSN sens a 'Location Update Request" m
number for creating or updating the association
subscriber data in the new VLR
- 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 t
19. The new 2G SGSN checks the presence of the MS in the new RA. If all checks area successful,t
established between the new 2G SGSN and the UE. The 2G SGSN responds to the UE with a "Rou
20. The UE acknowledge the new P-TMSI by returning a "Routing Area Update Complete" message
21. The new 2G SGSN sends a "TMSI Reallocation Complete" message to the new VLR if the UE co
22. The 2G SGSN and the BSS perform the "BSS Packet Flow Context" procedure

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 transmissio
2. The UE sends a "Routing Area Update Request" message to the 3G SGSN. The update type in th
update with IMSI attach. The SRNC adds the the RAC and LAC of the cell to the received message
3. The new 3G SGSN obtain the address of the old 2G SGSN, and then sends an 'SGSN Context R
the UE. The old 2G SGSN validates the old P-TMSI signature. If the old P-TMSI Signature is valid, t
cause.
4. The old 2G SGSN response with an "SGSN Context Response" message to the 3G SGSN includi
5. The security functions can be excuted

6. The new 3G SGSN sends an 'SGSN Context Acknowledge" message to the old 2G SGSN. This in
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
and sends them to the 3G SGSN. After the timer expires,the 2G SGSN does not send N-PDUs to th
8.The new 3G SGSN sends an "Update PDP Context Request" message to each related GGSN. Ea
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 SG
Location Ack" message
11.The HLR sens an "Insert Subscriber Data" message to the 3G SGSN. The 3G SGSN constructs a
12. The HLR sends "Update GPRS Location" by returning an "Update GPRS Location Ack" message
13. If the association has to be establilshed, that is . if the Update Type parameter indicates a combi
update, the 2G SGSN sends a "Location update request" message to the VLR. The VLR stores the

- The HLR responds with an "Update Location Ack" message to the new VLR
17. The UE sends a "Routing Area Update Complete" message to confirm the allocated P-TMSI
19. If the UE has uplink data or signalling to send, the UE sends a "Service Request" message to the
20. The 3G SGSN sends a "RAB Assignment Request" message to the SRNS. The SRNS sens a 'R
17. The UE sends a "Routing Area Update Complete" message to confirm the allocated P-TMSI
19. If the UE has uplink data or signalling to send, the UE sends a "Service Request" message to the
20. The 3G SGSN sends a "RAB Assignment Request" message to the SRNS. The SRNS sens a 'R
Setup Complete" message. The SRNS sends a 'RAB assignment Response" message to the SGSN
nter-RAT handover in the PS domain be sending "Cell Change Order from UTRAN' messge to UE to handover to a new GSM
work
the 2G SGSN. The update type in the message indicates RA update, combined RA/LA update, or combined RA/LA update
LAC of the cell to the received message before forwarding the message to a new 2G SGSN
age to the old 3G SGSN to obtain the MM and PDP contexts. The old 3G SGSN validates the old P-TMSI signature. If the old
rwise, the old 3G SGSN respons with an error cause.
G SGSN sends an "SRNS Context Request" message. After receiving this message, the SRNS buffers the PDUs, stops
onse" message to the old 3G SGSN
age to the 2G SGSN including the MM and PDP context
message to the old 3G SGSN. This inform the old 3G SGSN that the new 2G SGSN is
ge to the SRNS. The SRNS starts a data-forwarding timer and sends the buffers PDUs to
N. In the PDUs, the sequence number in the GTP hearder remain unchange
message to each related GGSN. Each GGSN sends an "Update PDP Context Response"
sage ,requesting the HLR to modify the SGSN number

SGSN. the old 3G SGSN responds with a "Cancel Location AcK" message. After the
exts.
to the SRNS. After data-forwarding timer expires,the SRNS responds with an "Iu
new 2G SGSN. The 2G SGSN constructs an MM context and PDP context for the UE and
o the new 2G SGSN

ens a 'Location Update Request" message to the VLR. The VLR stores the SGSN
he HLR. the new VLR informs the HLP. The HLR cancel the old VLR and inserts
R
l Location" message to the old VLR
"Cancel Location ACK" message
ew VLR
n "Insert Subscriber Data ACK" message
manin and stops the data transmission between the UE and the network
the 3G SGSN. The update type in the message indicates RA update, combined RA/LA update, or combined RA/LA
of the cell to the received message before forwarding the message to a new 3G SGSN
nd then sends an 'SGSN Context Request" message to the old 2G SGSN to construct the MM and PDP contects for
f the old P-TMSI Signature is valid, the old 2G SGSN starts a timer. Otherwise, the old 2G SGSN respons with an error
e" message to the 3G SGSN including the MM and PDP context
message to the old 2G SGSN. This inform the old 2G SGSN that the new 3G SGSN is ready to receive PDUs
s them to the 3G SGSN. Before the timer expires ,if there are other N-PDUs from the GGSN,the 2G SGSN compies
SGSN does not send N-PDUs to the 3G SGSN anymore
message to each related GGSN. Each GGSN sends an "Update PDP Context Response" message after updating it's
age to the HLR
SN. After the timer expires,the 2G SGSN removes the MM and PDP contexts. The 2G SGSN response with a 'Cancel
G SGSN. The 3G SGSN constructs an MM context and sends an "Insert Subscriber Data Ack" message to the HLR
pdate GPRS Location Ack" message to the 3G SGSN
e Type parameter indicates a combined RA/LA update with IMSI attach requested, or if the LA changed with the RA
age to the VLR. The VLR stores the SGSN number for creating or updating the association
he HLR. the new VLR informs the HLP. The HLR cancel the old VLR and inserts subscriber data in the new VLR
R
l Location" message to the old VLR
"Cancel Location ACK" message
ew VLR
n "Insert Subscriber Data ACK" message
the new VLR
cation Update Accept" message to the 3G SGSN

w RA. If all checks area successful,the new 3G SGSN constructs the MM and PDP contexts for the MS. A logical link is
GSN responds to the UE with a "Routing Area Update Accept" message
to confirm the allocated P-TMSI

message to the new VLR if the UE confirms the VLR TMSI
a "Service Request" message to the SGSN. The service type indicates the required service
e to the SRNS. The SRNS sens a 'Radion Beare Setup Request" message to the UE. The UE responds with a 'Radio Bearer

2G/3G
UE BSS
SGSN
Inter-RAT CS&PS Handover from WCDMA to GSM (Intra-SGSN)
2.Suspend
3.Suspend
3. Suspend Ack
4. Resume
4. Resume NAck
5.Channel Release
6. Routing Area Update Request

2G
UE BSS
SGSN
Inter-RAT CS&PS Handover from WCDMA to GSM (Inter-SGSN)
2.Suspend
3.Suspend
3. Suspend Ack
4. Resume
4. Resume NAck
5.Channel Release
6. Routing Area Update Request

>>Inter-RAT HO Algorithm and related paramete
er-RAT Handover Procedure
MSC
SRNS /VL
R For a UE in Cell_DCH state using
UE but is initiated from the UTRA
UE sends a handover complete m
ver from WCDMA to GSM (Intra-SGSN) services. After the CS domain se
handover is completed.
nter-RAT Handover
if the inter-RAT handover from UT
whether the UE inititates a TBF to
Mode and re-establish the conne
The signalling procedures are de

1. The UE in connection with both
3. SRNS Context Request
2. The UE sends a suspend mes
3. SRNS Context Response 3. The BSS forwards the 'Suspen

to stop sending downlink PDUs. A
Response" messge. The SGSN r
4. When the CS connection is ter

system has changed. Therefore,t
5. The BSS sens an RR message

UE
6. The UE sends a 'Routing Area

operation mode in use.
>>Inter-RAT HO Algorithm and related paramete

er-RAT Handover Procedure
MSC
3G SGSN SRNS /VL
R
For a UE in Cell_DCH state using
UE but is initiated from the UTRA
ver from WCDMA to GSM (Inter-SGSN) UE sends a handover complete m
services. After the CS domain se
handover is completed.
nter-RAT Handover
if the inter-RAT handover from UT

3. The BSS forwards the 'Suspen


3. The BSS forwards the 'Suspen
4. When the CS connection is ter

system has changed. Therefore,t
5. The BSS sens an RR message

UE
6. The UE sends a 'Routing Area

operation mode in use.
m and related parameters
in Cell_DCH state using both CS and PS domain services,the inter-RAT handover procedure is based on the measurement reports from th
initiated from the UTRAN. The UE performs the inter-RAT handover from UTRA RRC Connected Mode to GSM Connected Mode first. Afte
s a handover complete message to the GSM/BSS, the UE initiates a temporary block flow (TBF) towards the GPRS to suspend the GPRS
After the CS domain services are released on the GSM side, the inter-RAT handover in the PS domain resumes, which indicates that the
is completed.
r-RAT handover from UTRA RCC Conencted Mode to GSM Connected Mode succeeds,the handover is regards as successful.no matter
he UE inititates a TBF towards the GPRS or not. In case of inter-RAT handover failure, the UE may go back to the UTRA RRC Connected
d re-establish the connection in the original state.
alling procedures are described as follows,

E in connection with both CS and PS domain perrforms the UMTS to GSM handover during which the CS service is handed over to the GSM
E sends a suspend message to the BSS
SS forwards the 'Suspend" message to the SGSN. The SGSN sends a "SRNS Context Request" message to the SRNS, requesting the SRN
ending downlink PDUs. After receiving the message, the SRNS buffers downlink PDUs and respons to the SGSN with an 'SRNS Context
e" messge. The SGSN returns a "Suspend Ack" message to the BSS
he CS connection is terminated , the BSS may send a 'Resume" message to the SGSN. However,resume is impossible since the radio acc
as changed. Therefore,the SGSN acknowledge the resume through a 'Resume NACK"
SS sens an RR message 'Channel Release" to the UE, indicating that the BSS fails to request the SGSN to resume the GPRS service for th
E sends a 'Routing Area Update Request" message to the SGSN to resume the GPRS service. The update mode depends on the network
mode in use.
m and related parameters
in Cell_DCH state using both CS and PS domain services,the inter-RAT handover procedure is based on the measurement reports from th
initiated from the UTRAN. The UE performs the inter-RAT handover from UTRA RRC Connected Mode to GSM Connected Mode first. Afte
s a handover complete message to the GSM/BSS, the UE initiates a temporary block flow (TBF) towards the GPRS to suspend the GPRS
After the CS domain services are released on the GSM side, the inter-RAT handover in the PS domain resumes, which indicates that the
is completed.
r-RAT handover from UTRA RCC Conencted Mode to GSM Connected Mode succeeds,the handover is regards as successful.no matter
he UE inititates a TBF towards the GPRS or not. In case of inter-RAT handover failure, the UE may go back to the UTRA RRC Connected
d re-establish the connection in the original state.
alling procedures are described as follows,

E in connection with both CS and PS domain perrforms the UMTS to GSM handover during which the CS service is handed over to the GSM
E sends a suspend message to the BSS
SS forwards the 'Suspend" message to the SGSN. The SGSN returns a "Suspend Ack" message to the BSS
measurement reports from the
Connected Mode first. After the
PRS to suspend the GPRS
s, which indicates that the
s as successful.no matter
he UTRA RRC Connected
e is handed over to the GSM
e SRNS, requesting the SRNS

N with an 'SRNS Context
possible since the radio access
ume the GPRS service for the
de depends on the network
measurement reports from the

Connected Mode first. After the
PRS to suspend the GPRS
s, which indicates that the
s as successful.no matter
he UTRA RRC Connected
e is handed over to the GSM

L3 Messages - Intra-Frequency Hard Handover Proced

UE SRNC DRNC
SRNS Static Relocation (UE not-involved relocation)
4.RANAP: Relocation Command
5. RNSAP: Relocation Commit
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)
13. RANAP: Iu Release Command
14. RANAP: Iu Release Complete


UE SRNC DRNC
SRNS Relocation with Cell/URA Update (UE not-involved reloca
1. Cell Update/URA Update

2. RNSAP: Signalling Transfer
Indication
3RANAP: Relocation Required
Cell
Update/
URA
Update
7. RNSAP: Relocation Commit
9. RRC:Cell Update Confirm/URA Update Confirm
10. RRC:Physical Channel Reconfiguration Complete/UTRAN Mobility

Information Confirm

1.The DRNC acquires the SRNC ID of the UE from the URNTI IE in the CELL UPDATEmessage and then
SIGNALLING TRANSFER INDICATION messageto the SRNC to indicate that the UE requests a cell upd
2.To initiate a cell update, the UE sends a CELL UPDATE message to the DRNC. To initiate a URA updat
URA UPDATE message to the DRNC.
3.After a successful cell update, the DRNC sends a CELL UPDATE CONFIRM message tothe UE. After a
update, the DRNC sends a URA UPDATE CONFIRM message to the UE.
4.After receiving the CELL UPDATE CONFIRM or URA UPDATE CONFIRM messagefrom the DRNC, the
PHYSICAL CHANNEL RECONFIGURATION COMPLETE message (for the cell update) or a UTRAN MO
INFORMATION CONFIRM message (for the URA update) to the DRNC. This response from the UE is op
4.After receiving the CELL UPDATE CONFIRM or URA UPDATE CONFIRM messagefrom the DRNC, the
PHYSICAL CHANNEL RECONFIGURATION COMPLETE message (for the cell update) or a UTRAN MO
INFORMATION CONFIRM message (for the URA update) to the DRNC. This response from the UE is op

UE SRNC DRNC
SRNS Relocation with Hard Handover(UE involved relocatio
5.RANAP: Forward SRNS Context
7.RRC:Physical Channel
Channel
Reconfig


1.During the relocation with hard handover, if an RAB supporting lossless SRNS relocation is avail
the SRNC sends the GTP-U and PDCP sequence numbers to the DRNC through the FORWARD S
The sequence numbers are required for data forwarding.
2.After receiving a RADIO LINK RESTORE INDICATION message from the NodeB, theDRNC sen
message to the CN.
3.If the DRNC does not obtain the information about the UE capability, the DRNC initiatesa UE cap
>>SRNC Relocation Algorithm and related parameters
Handover Procedure
CN The relocation preparation proce
->During an SRNS relocation, the
->During an inter-RAT CS handove
volved relocation)
The procedure is described as f
1.The SRNC sends a RELOCATIO
P: Relocation Required cause, source PLMN, source LAC
2.The CN interacts with the target
3.The CN sends a response mess
2.RANAP Relocation Request CN sends a RELOCATION COMM
Relocation Preparation
theinformation about the relevant r
3.RANAP Relocation Request Ack Relocation Resource Allocation to be allocated, the CN sends a R
P: Relocation Command
The relocation resource allocati

6. RANAP:Relocation Detect
1.The CN sends a RELOCATION
domain indicator, target cellidentifi
UTRAN mobility information 2.The target RNC allocates radio r
Relocation Commit 3.The target RNC sends a respon
REQUESTACKNOWLEDGE mess
the UTRAN Radio NetworkTempor
chosen integrity protection algorith
some reason, the target RNC send
UE capability enquiry
12. Relocation Complete

The relocation commit procedur
AP: Iu Release Command
Iu release The procedure is described as f
AP: Iu Release Complete interface, the RELOCATION COM
initiates data forwarding.
2.The DRNC sends a RELOCATIO
3.The original DRNC sends a REL
The UTRAN mobility information

Cell Radio Network TemporaryIden
related information.

1.The SRNC sends a UTRAN MO
2.The UE starts to update the rela
3.The UE sends a response mess
->If the UE succeeds in conducting



INFORMATIONCONFIRM messag
->If the UE fails to conduct the ope
INFORMATIONFAILURE message
The UE capability enquiry proce

the network can perform dataconfi

1.The SRNC sends a UE CAPABI
2.The UE sends a UE CAPABILIT
the information about UE capabilit
3.The SRNC reads the UE capabi
DCCH using AM or UMRLC.
The Iu release procedure can be

->The transaction between the UE
->The UTRAN requests the CN to
->The Serving Radio Network Sub
->The SRNS relocation is cancele

1.The CN sends an IU RELEASE
release of the signaling connection
oriented messages on this particu
2.The SRNC releases the related
Handover Procedure Click to return to main page

CN
The relocation preparation proce
E not-involved relocation) ->During an inter-RAT CS handove

cause, source PLMN, source LAC
CN sends a RELOCATION COMM
allocated, the CN sends a RELOC

cause, source PLMN, source LAC
CN sends a RELOCATION COMM
allocated, the CN sends a RELOC
P: Relocation Required
4.RANAP Relocation Request Relocation Preparation
5.RANAP Relocation Request Ack Relocation Resource Allocation

P: Relocation Command ->During an inter-RAT CS handove

domain indicator, target cellidentifi
8. RANAP:Relocation Detect 2.The target RNC allocates radio r
3.The target RNC sends a respon
REQUESTACKNOWLEDGE mess
include the UTRAN Radio Networ
, and chosen integrity protection a
some reason, the target RNC sen
Relocation Commit
UE capability enquiry The cell update procedure is perf

cell update procedure takes the ro
information
14. Relocation Complete The cell update procedure can be

updatelRadio link failure,Paging re
AP: Iu Release Command The procedure is described as f

Iu release 1.The UE sends a CELL UPDATE
Identifier (S-RNTI) andthe SRNC I
AP: Iu Release Complete 2.The RNC sends a CELL UPDAT
transport channels, physicalchann
3.According to related IEs in the re
following messages:
->UTRAN MOBILITY INFORMATI
->PHYSICAL CHANNEL RECONF
UPDATEmessage and then sends an UPLINK ->TRANSPORT CHANNEL RECO
the UE requests a cell update. ->RADIO BEARER RECONFIGUR
->RADIO BEARER RELEASE CO
NC. To initiate a URA update, the UE sends a
message tothe UE. After a successful URA
essagefrom the DRNC, the UE can send a

ell update) or a UTRAN MOBILITY The URA update procedure is per
esponse from the UE is optional. URA update procedure can be trig

1.The UE sends a URA UPDATE m
such as the U-RNTI.
2.The RNC sends a URA UPDATE
new ciphering and integrityprotect
The URA update procedure is per
URA update procedure can be trig

1.The UE sends a URA UPDATE m
such as the U-RNTI.
2.The RNC sends a URA UPDATE
new ciphering and integrityprotect
3.The UE responds optionally. If th
the new parameters intoeffect.
The relocation commit procedur

interface, the RELOCATION COM
initiates data forwarding.
2.The DRNC sends a RELOCATIO



INFORMATIONCONFIRM messag
->If the UE fails to conduct the ope
INFORMATIONFAILURE message




Handover Procedure Click to return to main page

CN The relocation preparation proce
UE involved relocation)
P: Relocation Required cause, source PLMN, source LAC
2.RANAP: Relocation Request 3.The CN sends a response mess
Relocation Preparation CN sends a RELOCATION COMM
3.RANAP: Relocation Request Ack Relocation Resource Allocation allocated, the CN sends a RELOC
P: Relocation Command
: Forward SRNS Context

6.RANAP: Forward SRNS Context ->During an inter-RAT CS handove

8. RANAP:Relocation Detect CN domain indicator, target cellide
2.The target RNC allocates radio r
3.The target RNC sends a respon
Relocation Commit REQUESTACKNOWLEDGE mess
include the UTRAN Radio Networ
and chosen integrity protection alg
some reason, the target RNC send
UE capability enquiry
12. Relocation Complete

The relocation commit procedure
The procedure is described as

1.When an RAB supporting lossle
The relocation commit procedure
AP: Iu Release Command
Iu release The procedure is described as
1.When an RAB supporting lossle
AP: Iu Release Complete message to the SGSN to ask the S
data forwarding.
2.After receiving the FORWARD S
3.The UE is handed over from the
RESTORE INDICATIONmessage
ss SRNS relocation is available on the Iu-PS interface,
C through the FORWARD SRNS CONTEXT message.
the NodeB, theDRNC sends a RELOCATION DETECT
The physical channel reconfigur

he DRNC initiatesa UE capability enquiry procedure.
The procedure is described as
1.The SRNC sends a PHYSICAL C
2.The UE saves the IEs of the UE
->If successfully reconfiguring the
PHYSICAL CHANNELRE CONFIG
->If failing to reconfigure the physi
configuration to the old physicalch
using AM RLC. The value of the F
channel failure".






location preparation procedure can be triggered in either of the following conditions:
ng an SRNS relocation, the SRNC sends a RELOCATION REQUIRED message.
ng an inter-RAT CS handover from WCDMA to GSM, the SRNC sends aRELOCATION REQUIRED message.
ocedure is described as follows:

SRNC sends a RELOCATION REQUIRED message to the CN. The message containscertain information such as relocation type, relocation
, source PLMN, source LAC,source SAC, target PLMN, and target LAC
CN interacts with the target RNC or the target network system, such as the GSMsystem, to prepare relevant resources.
CN sends a response message to the SRNC.lIf the target RNC or the target network system prepares the relevant resourcessuccessfully, th
nds a RELOCATION COMMAND message when thepreparation is complete. The message contains the L3 information IE, which carries
rmation about the relevant resources allocated by the target RNC or the targetnetwork system.lIf the resources partially or totally fail
llocated, the CN sends a RELOCATIONPREPARATION FAILURE message.
location resource allocation procedure can be triggered in either of the following conditions:
ng an SRNS relocation, the CN applies for resources from the target RNC
ng an inter-RAT CS handover from GSM to WCDMA, the CN applies for resourcesfrom the target RNC

CN sends a RELOCATION REQUEST message to the target RNC. The messagecontains certain information, such as the IMSI of the UE, C
n indicator, target cellidentifier, encryption, integrity protection, Iu signaling connection ID, handover cause, and RAB parameters.
arget RNC allocates radio resources for the relocation.
arget RNC sends a response message to the CN.lIf the resources are allocated, the target RNC sends a RELOCATION
ESTACKNOWLEDGE message. The message contains the radio resources and otherparameters allocated to the UE. The parameters inclu
RAN Radio NetworkTemporary Identifier (U-RNTI), RAB, transport layer and physical layer information,chosen encryption algorithm, and
n integrity protection algorithm.lIf the resources partially or totally fail to be allocated or the target RNC rejects the SRNSrelocation for
eason, the target RNC sends a RELOCATION FAILURE message,indicating the failure cause.
location commit procedure is performed to execute the change of control from the SRNCof a UE to the DRNC

SRNC sends a RELOCATION COMMIT message to the DRNC. If an RAB supportinglossless SRNS relocation is available on the Iu-PS
ce, the RELOCATION COMMITmessage carries the GTP-U and PDCP sequence numbers required for data forwarding.Then, the SRNC
s data forwarding.
DRNC sends a RELOCATION DETECT message to the CN to notify the CN of thedetection of the relocation commitment.
original DRNC sends a RELOCATION COMPLETE message to the CN to notify thatthe relocation is successful.
TRAN mobility information procedure is performed for the network to allocate a newUTRAN Radio Network Temporary Identifier (U-RNTI)
adio Network TemporaryIdentifier (C-RNTI) to a UE or to inform the UE of mobility-related information such as timer values and CN domain–
information.

SRNC sends a UTRAN MOBILITY INFORMATION message to the UE
UE starts to update the related fields according to the values of the IEs carried in themessage.
UE sends a response message to the SRNC.
UE succeeds in conducting the operations specified by the UTRAN MOBILITYI NFORMATION message, the UE sends a UTRAN MOBILI
E capability enquiry procedure is performed to request a UE to transmit its capabilityinformation related to any radio access network so tha
work can perform dataconfiguration based on the UE capability.

SRNC sends a UE CAPABILITY ENQUIRY message to the UE through the downlink DCCH using AM RLC.
UE sends a UE CAPABILITY INFORMATION message to the SRNC through theuplink DCCH using AM or UM RLC. The message contains
ormation about UE capabilities.
SRNC reads the UE capability information and then sends a UE CAPABILITYINFORMA CONFIRM message to the UE through the downlin
using AM or UMRLC.
release procedure can be triggered in one of the following conditions:

transaction between the UE and the CN is complete.
UTRAN requests the CN to release the resources on the Iu interface by, for example,sending an IU RELEASE REQUEST message.
Serving Radio Network Subsystem (SRNS) is relocated.
SRNS relocation is canceled after a relocation resource allocation procedure iscomplete.

CN sends an IU RELEASE COMMAND message to the SRNC to initiate the Iu releaseprocedure. The message indicates the cause for the
e of the signaling connection.NOTE After sending the IU RELEASE COMMAND message, the CN will not send further RANAPconnection-
d messages on this particular connection.
SRNC releases the related UTRAN resources and then sends an IU RELEASE COMPLETE message to the CN.


source PLMN, source LAC,source SAC, target PLMN, and target LAC
rmation about the relevant resources allocated by the target RNC or the targetnetwork system.lIf the resources partially or totally fail to be
ed, the CN sends a RELOCATIONPREPARATION FAILURE message.

CN sends a RELOCATION REQUEST message to the target RNC. The messagecontains certain information, such as the IMSI of the UE, C
n indicator, target cellidentifier, encryption, integrity protection, Iu signaling connection ID, handover cause, and RAB parameters.
ESTACKNOWLEDGE message. The message contains the radio resources and otherparameters allocated to the UE. The parameters
e the UTRAN Radio NetworkTemporary Identifier (U-RNTI), RAB, transport layer and physical layer information,chosen encryption algorithm
hosen integrity protection algorithm.lIf the resources partially or totally fail to be allocated or the target RNC rejects the SRNSrelocation for
reason, the target RNC sends a RELOCATION FAILURE message,indicating the failure cause.
ll update procedure is performed to update the UE-related information on the UTRANside when the location of a UE changes. In addition,
date procedure takes the role ofmonitoring the RRC connection, switching the status of the RRC connection, reporting errors,and transferrin
ation
ll update procedure can be triggered in one of the following conditions:Cell reselection,Re-entering the service area,Periodical cell
lRadio link failure,Paging response,Uplink data transmission and RLC unrecoverable error

UE sends a CELL UPDATE message to the RNC. The message contains the information such as the Serving RNC Radio Network Tempora
er (S-RNTI) andthe SRNC ID.
RNC sends a CELL UPDATE CONFIRM message to the UE. The message containsthe information such as the U-RNTI and the IEs about t
ort channels, physicalchannels, and radio bearers.
rding to related IEs in the received message, the UE may respond with messages ornot. If the UE responds, the message can be one of th
ng messages:
AN MOBILITY INFORMATION CONFIRM
SICAL CHANNEL RECONFIGURATION COMPLETE
NSPORT CHANNEL RECONFIGURATION COMPLETE
IO BEARER RECONFIGURATION COMPLETE
IO BEARER RELEASE COMPLETE
RA update procedure is performed to update the URA-related location information on thenetwork side when the location of a UE changes. T
pdate procedure can be triggered in either of the following conditions:URA reselection or Periodical URA update

UE sends a URA UPDATE message to the RNC to initiate the URA update. The message contains the cause for the URA update and the IE
s the U-RNTI.
RNC sends a URA UPDATE CONFIRM message to the UE. The message containsthe new C-RNTI and U-RNTI or the information about th
phering and integrityprotection modes.
location commit procedure is performed to execute the change of control from the SRNCof a UE to the DRNC

SRNC sends a RELOCATION COMMIT message to the DRNC. If an RAB supportinglossless SRNS relocation is available on the Iu-PS
ce, the RELOCATION COMMITmessage carries the GTP-U and PDCP sequence numbers required for data forwarding.Then, the SRNC
s data forwarding.
DRNC sends a RELOCATION DETECT message to the CN to notify the CN of thedetection of the relocation commitment.
original DRNC sends a RELOCATION COMPLETE message to the CN to notify thatthe relocation is successful.
TRAN mobility information procedure is performed for the network to allocate a newUTRAN Radio Network Temporary Identifier (U-RNTI)
adio Network TemporaryIdentifier (C-RNTI) to a UE or to inform the UE of mobility-related information such as timer values and CN domain–
information.

SRNC sends a UTRAN MOBILITY INFORMATION message to the UE
UE starts to update the related fields according to the values of the IEs carried in themessage.
UE succeeds in conducting the operations specified by the UTRAN MOBILITYI NFORMATION message, the UE sends a UTRAN MOBILI
MATIONCONFIRM message.
UE fails to conduct the operations specified by the UTRAN MOBILITYINFORMATION message, the UE sends a UTRAN MOBILITY
MATIONFAILURE message, indicating the failure cause.

using AM or UMRLC.


source PLMN, source LAC,source SAC, target PLMN, and target LAC
rmation about the relevant resources allocated by the target RNC or the targetnetwork system.lIf the resources partially or totally fail to be
ed, the CN sends a RELOCATIONPREPARATION FAILURE message.

CN sends a RELOCATION REQUEST message to the target RNC. The messagecontains certain information, such as the IMSI of the UE,
main indicator, target cellidentifier, encryption, integrity protection, Iu signaling connection ID, handover cause, and RAB parameters.
ESTACKNOWLEDGE message. The message contains the radio resources and otherparameters allocated to the UE. The parameters
e the UTRAN Radio NetworkTemporary Identifier (U-RNTI), RAB, transport layer and physical layer information,chosen encryption algorithm
osen integrity protection algorithm.lIf the resources partially or totally fail to be allocated or the target RNC rejects the SRNSrelocation for
eason, the target RNC sends a RELOCATION FAILURE message,indicating the failure cause.
ocation commit procedure is performed to execute the change of control from the SRNCof a UE to the DRNC.

n an RAB supporting lossless SRNS relocation is available on the Iu-PS interface, theSRNC sends a FORWARD SRNS CONTEXT
hysical channel reconfiguration procedure is performed to set up, reconfigure, or releasea physical channel.

SRNC sends a PHYSICAL CHANNEL RECONFIGURATION message to the UE to request reconfiguration of a physical channel.
UE saves the IEs of the UE, Radio Bearer (RB), transport channel, and physical channel.
ccessfully reconfiguring the physical channels specified by the PHYSICALCHANNEL RECONFIGURATION message, the UE sends a
CAL CHANNELRE CONFIGURATION COMPLETE message on the uplink DCCH by using AM RLC.
ing to reconfigure the physical channels specified by the PHYSICAL CHANNELRECONFIGURATION message, the UE restores the
uration to the old physicalchannel configuration and sends a PHYSICAL CHANNEL RECONFIGURATION FAILURE message on the DCCH
AM RLC. The value of the Failure causeIE contained in the PHYSICAL CHANNEL RECONFIGURATION FAILURE message is "physical
el failure".

using AM or UMRLC.

SRNS relocation is canceled after a relocation resource allocation procedure iscomplete.

CN sends an IU RELEASE COMMAND message to the SRNC to initiate the Iu releaseprocedure. The message indicates the cause for the
e of the signaling connection.NOTE After sending the IU RELEASE COMMAND message, the CN will not send further RANAPconnection-
d messages on this particular connection.
SRNC releases the related UTRAN resources and then sends an IU RELEASE COMPLETE message to the CN.
ge.
uch as relocation type, relocation
t resources.
elevant resourcessuccessfully, the
information IE, which carries
rces partially or totally fail
on, such as the IMSI of the UE, CN

and RAB parameters.
ELOCATION
to the UE. The parameters include
sen encryption algorithm, and
ts the SRNSrelocation for
DRNC
tion is available on the Iu-PS

a forwarding.Then, the SRNC
n commitment.
ssful.
rk Temporary Identifier (U-RNTI) or

as timer values and CN domain–
the UE sends a UTRAN MOBILITY

any radio access network so that
UM RLC. The message contains
ge to the UE through the downlink
SE REQUEST message.
sage indicates the cause for the

end further RANAPconnection-
e CN.
ge.
t resources.
rces partially or totally fail to be
on, such as the IMSI of the UE, CN
and RAB parameters.
ELOCATION
to the UE. The parameters
tion,chosen encryption algorithm
rejects the SRNSrelocation for
>>Cell Update Description
on of a UE changes. In addition, the

n, reporting errors,and transferring
vice area,Periodical cell
ng RNC Radio Network Temporary
s the U-RNTI and the IEs about the
s, the message can be one of the
n the location of a UE changes. The

date
se for the URA update and the IEs
RNTI or the information about the

DRNC
tion is available on the Iu-PS

a forwarding.Then, the SRNC
n commitment.
ssful.
rk Temporary Identifier (U-RNTI) or

as timer values and CN domain–
the UE sends a UTRAN MOBILITY
ends a UTRAN MOBILITY
SE REQUEST message.
ge.
t resources.
rces partially or totally fail to be
on, such as the IMSI of the UE,

se, and RAB parameters.
ELOCATION
to the UE. The parameters
tion,chosen encryption algorithm,
ejects the SRNSrelocation for
RNC.
WARD SRNS CONTEXT

nel.
of a physical channel.
message, the UE sends a
sage, the UE restores the

FAILURE message on the DCCH by
AILURE message is "physical
SE REQUEST message.
sage indicates the cause for the

end further RANAPconnection-
e CN.

W-RNO AnalysisMate - V1.0

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

W-RNO AnalysisMate - V1.0

Încărcat de

Drepturi de autor:

Formate disponibile

Developed By: Aumpika Viun (Ice)

W-RNO AnalysisMate Ver1.0 Convention

0. UTRAN Network Architecture and Protocols Underline Text

1.1 UMTS Network Architecture MML Command

1.2 UTRAN Protocols Click to return to main page

1.2 RRC Tasks and Functions

1.3 RRC Mode Description Ver1.0

1.4 RRC Connection Mobility Management and RRC Modes

1.5 RRC Procedures

1.7 UE Measurement Procedures

2.1 Paging Message Type 1

2.2 Paging Message Type 2 Tool Version

4. Location Update Procedure & L3-messages

5. Call Procedure & L3-messages

5.2 CS64/ Video Call

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.2 Inter-RAT CS 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)

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

Change Type Change History Change Date Remark

The User Equipment(UE) consists of,

With UTRAN, four new interfaces were specified:

2. Serving RNC (S-RNC) :

A Node B can be used for Frequency Division Duplex (Uplin

- Radio Channel functions: Transport to physical channel ma

Geographical and UTRAN Entity Identifiers

1. PLMN Id = MCC +MNC

UTRAN Identifiers for UE

- International Mobile Subscriber Identity (IMSI)

1. Access Stratum(AS) : The Access Stratum

2. Transport Stratum: The Transport Stratum

3. Non-Access Stratum (NAS) : The Non-Acc

UTRAN Protocol Architecture

The higher layer protocols of the Non-Access Stratum(NAS) h

UTRAN Interface Protocol Structure

The transport system used within UTRAN is ATM. There is diff

The Transport Network Control Plane acts as plane between th

UTRAN Interface Protocol Overview

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

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

UTRAN Interface Protocol -Uu (UE-UTRAN)

The radio interface (Uu) is layered into three

The layer 1 supports all functions required for

The layer 2 protocol is responsible for providin

The layer 3 is split into 2 parts: the access stra

The protocol layers are located in the UE an

Physical Layer (L1) Functions

Transport Format Combinations

Transport Format Combinations

Physical Layer Procedures

I. MAC, The functions of MAC include:

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

-NBAP (NodeB Application Part) : The NBAP protocol is the

-Frame Protocols : The Frame Protocols encapsulate the UE